GC21 7620 6_IBM_System3_Communications Control Program System Reference Manual_Sep80 6 IBM System3 Communications Manual Sep80

aaaa aaaa

aaaaaaaaaaaaaaaaaa

aaaaaaaaaaaaoaaaaa

aaaaaaaaaaaaaaaaaa

aaaaaaaaaa

aoaaaaaaaaa

aaaaaaaaaaa

aaaoaaaaaaa

aaaaaaaaaa

aaaaaaaaaaaaaaaaaa

aaaa aaaa

IBM

System./3

Model

15

Communications

Control

Program

System

Reference

Manual

Program

Numbers:

5704-SC1

5704-SCz

Featu

res

60 1

1

160121

60331007

0

/GO7

1

GC21-7620-6

File

No.

33-36

aaaaaa

aaatao

aaaaaa

oaaa aaaa

aaaa aaaa

aaaaaaaaaaaoaaaaaa

a aa a a a a a

a a a a

a a a a a a

aaaaaaaaaaoaaaaaaa

aaaaaaaaaaaaaaaaaa

aaaa aaaa

aaa aaa

aaaaaa

aaaaa

aoaaa

aaaaaaa

aaaa

\

Seventh

Edition

(September

19801

This is

a major revision of

,

and obsoletes,GC2l-7620-5.

Changes or additions to the

text and illustrations

are

indicated

by a vertical line

to the left of the change

or

addition.

This edition

applies to the following IBM System/3 system control programs

and to all

subsequent versions and modifications

until otherwise

indicated in new editions

or

technical neursletters.

Version Modification Program Number System/3 Model

08 00

05 00

5704-5C1

5704-SC2

Model 15

A-B-C

Model 1 5D

Changes

are

periodically

made

to the information herein;

changes will be

reported in

technical

newsletters

or in new

editions of this oublication.

Use this publication only for the purposes

stated in the Preface.

Publications

are not stocked at the address

below. Requests for copies

of IBM publica-

tions

and

for technical information

about the system should

be

made

to Vour IBM

representative

or to the IBM branch office serving

your locality.

This

publication

could

contain technical

inaccuracies

or typographical

errors. Address

your comments

about this

publication

to IBM Corporation,

Publications,

Department

245, Rochester, Minnesota

55901. IBM may use and

distribute any of the information

you supply in

any way it believes appropriate without incurring any obligation

whatever.

You may, of course, continue to use

the information

you supply.

OCopyright International Business

Machines

Corporation 1973, 1974,1975,1976,1977, 1978,1979, 19BO

Preface

This

publication

describes

the

Communications

Control o tBM

System/3

Modet

l5 Operator,s

Guide,

GC21-5075.

Program

(CCP)

feature

of the IBM

System/3

Model

lS and

provides

information

to aid

the system installation

manager, . IBM System/3

Model lE System

Control

programmrng

IBM

systems

engineer,

and

application

programmers

in Reference

Manual,

GC21.SO77

(S704-SC1).

generating

the

CCP

system.

o IBM System/3

Model lS System

Control programming

The

generation

of the

CCP

system

is accomplished

by using Concepts

and Reference

Manual,

GC21-b162

(b704"SC2).

the facilities

of the: o IBM System/3

Model lS System

Cantrol programming

o f BM

System/3

Model

15

system

Control

programming Macros

Reference

Manual,

Gc21-7609.

(5704-SC1

and 5704-SC2) . IBM System/3 Overlay

Linkage

Editor Reference

a Programming

support for

the

communication

adapters: Manual,

GC21-7561.

Multiline/Multipoint

feature

Multiple

Line

Terminal

Adapter

feature

(PSHRPO

number

5799-WFK) . IBM System/3 Model l5 Scheduler

Logic

Manual,

sY21_0035.

Prerequisite

Knowledge t IBM System/3

Model 15

Supervisor

and IOS

Logic

Manual.

SY21-0033.

You

should

be

an experiencecl

System/3 Model

1b

user

familiar

with the basic

concepts

of teleprocessing. . IBM

System/3 Model

l5 Data

Management

Logic

Manual,

SY21-0034.

Devices

and

Programs

Supported

and Required . l9M Systeml3

Model 15 System

Data Areas

and Diag-

nostic

Aids.

SY21

-0032

(5704-SCl

).

The

terminal

devices,

system

devices,

and system

programs

requiredandsupportedbytheCCParelistedinAppendix

.lBMSystem/3Madet

lssystemDataAreasandDiag-

D. nostic

Aids,

Sy21_0052

(5704-SC2)"

y'y'oter

This

manual

follows

the

convention

thatre means . tBM System/3

Modet li Systent

Services

programs

he

or she. Logic

Manual,

Sy21-0036.

Refated

Publications . IBM System/3

Muttitine/Multipoint

Einary

Synchronous

Comm

un icati

on

s R

eference

Man

u al. GCZI

_7

57 3.

. I8M System/3 Communications

Control Program

Mes-

sages

Manual, GC21-5170. . l9M System/3

Multiple Line Terminal

Adapter Rpe

Program

Reference

and Component

Descriptiort

Manual,

. l8M System/3

Model l5 Communication

Control

pro- GC21-7560.

gram

System

Operator Guide, GC21-7619. . IBM 1050

Data Cornmunication

System

principles

af

. IBM System/3 Communication Control Program Terminal operation. GA24-3474.

O

perato

r's G

u

ide, GC21

-7

58O. . IBM 2740 Communicatiotts

Terminal

Models I and 2

. IBM System/3

Communications

Control Program Component

Description, GA24-3403.

Programmer's

Reference

Manual, GC21

-7

579. . IBM

2741 Communication

Terminal.

GA24-341S.

o IBM System/3

Communications

Control program System

Design

Guide,

GC21-5165. ' IBM System/7

Systems

Summary,

GA34-0002.

Preface iii

a

l.

I

I 8M SystemD B inary Synchronous Communications

Module (RPQ)

Pragramming

Guide

and Reference

Manual,

SC34-1510.

I

BM System/7 Teleprocessing

Multiplexor'"TPMM"

Programming

Guide and Reference Manual

Supporting

RPO DMAt /, SC34-1506.

IBM 3270 lnformation Display System Component

Description. GA2l 27 49.

l8M 3735 Programmer's

Guide, GC3O-3001.

IBM System/3 3735 Support Program Coding Manual,

GC2i-5096.

IBM 3741 Data

Station

Reference Manual.

G421-9183.

IBM System/3 Disk

Sort

Reference

Manual,

SC21-7522.

IBM System/3 Model | 5 User's Guide to Spooling,

cc21 7632.

IBM System/3 Sabsef American National Standard

CO BO L Reference Manual, GC28-6452.

IBM System/3

RPG ll Reference Manual,

SC21-7504.

l8M System/3

FORTRAN lV Reference Manual,

sc28-6874.

l8M System/3 Basic

Asrembler

Program Reference

Manual.

SC21-7509.

I

BM Systen/34 lnteractive Communications Feature

Reference

Manual

,

SC21"7751.

Contents

CHAPTER

1. INTRODUCTION

Terminal Operator

Facil ities

System

Operator Facilities .

Programming Facilities

.

Devices and Programs

Supported

Establishing and Operating

the

CCP

Generation

Stage

Assignment Stage

Operational Stage

CCP

Tasks

Relationship

to Other

Programs

Disk System

Management

(DSM)

Ex isting

Commun

ications

Programming

Support

Application Programs

System Programs

CHAPTER 2. USING

THE

CCP

FROM A TERMINAL

How

the

Terminal Operator Requests

a

Program

How the Terminal

Operator

Requests

System

Services .

Terminal

Modes

Initial Mode

Command

Mode

.

Data

Mode

Command Interrupt Mode .

Terminal

Operator

Commands

Sign-On Command

(/ON)

Oueue/No-Oueue Commands

(/O

and /NOOI

Command

Meaning

File

Specification Command

(/FlLEl .

Name Command

(/NAME) .

Program Request

Command

Data Mode Escape

Command

Release Command

(/RELEASE)

Message

Command

(/MSGI

.

Run

Command

(/RUNI

.

Sign-Of{ Command

(/OFF)

Planning

Considerations

CHAPTEB 3. SYSTEM OPERATOR CONTROL

OF

THE CCP

lnitiating

CCP

System

Operator Commands

Message Command

(MSG)

Display Terminal

Status

(D T) .

Display

Terminal

Assignments

(D A)

Display Users Command

(D U)

Cancel a User

Program

or the

CCP

Suspend

Requests/Execution/lnitiation

of User

Programs

Resume Requests/Execution/lnitiation

of User

Programs

Change the Status of a Terminal

(VARY)

Close/Ooen

the

BSCA

Line

(CLOSE/OPENI

Assign a Symbolic

Terminal Name

to a

Terminal

{ASSIGN)

Online Terminal

Test

(TEST)

Change the

Interval

Polling

Time

f POLTIME)

Recover

f

rom

Terminal Errors

(ERP)

.

Control

Automatic Retries of Terminals

During

Error Recovery

(AUTOERP)

{Program Number

5704-SC2 Onlv)

Save

Trace Table Information (TRACEI

Initiate

or Terminate the CCP

Trace

(TRACE)

(Program

Number

57O4-SC2 Onlv)

Using the

System Operator's Console

as

a

Requesting

Terminal

Closing and Opening Disk Files

Under CCP

Closing

and Opening Disk Files From

a Batch

Partition

(Program

Number 5704-SC2

Only)

Shutting Down CCP

System Operator Messages

CCP

Resoonses

Messages f rom Terminal

Operators

Messages f rom User

Programs

Planning

and

the System Operator

Operating Aids

CHAPTER 4. CCP SERVICES FOR THE APPLICATION

PROGRAMMER

Facilities

Off ered

by the CCP

Communications Management

F ile Management

Program Management

CHAPTER 5. DESIGNING YOUR COMMUNICATIONS.

BASED SYSTEM

Applications

Terminals

Data

F iles

Programs

Establ

ishing

the System

Operating the System

Startup

Operation

Shutdown

Updating the System

Total Equipment Needs

Disk

System Management

(DSM)

Considerations

Spooling

Considerations

(Program

Number

5704-SCl

)

Spooling

Considerations

(Program

Number

5704-SC2)

CCP Trace

Multiple Partition

Considerations

Sharing

Files

Between

Partitions

327O

Display Format Facility (DFF) Considerations

Using the Same

Terminal with DFF and

Non-DF F Programs

Terminal Security Considerations

CHAPTER 6. GENERATION STAGE

Procedure for Generation

Operational

Procedures for Generation

Generation Control Statements

Writing

Generation Control Statements

$EFAC-CCP

Facilities

$E

PLG

-Programming Languages

$ESEC-Terminal SignOn Security

$EF

lL-$CCPF ILE

Allocation

$EMLA-MLTA Support

$EMLD-MLTA Devices

$EBSC-BSC Support

$EBSD-BSC Devices

$ECSC-BSCC

Support (5704-SC2

only)

$ECSD-BSCC Devices

I

1

I

2

3

?

4

5

18

7

I

8

I

9

I

o

10

11

12

't2

12

15

16

't6

16

17

't7

17

18

19

an

20

21

22

zl

23

24

27

2a

28

29

30

JI

31

?2

34

35

36

37

38

40

6q

62

65

66

69

10

11

77

78

80

Contents v

$EGEN-CCP Generation

Stream 81 Additional Devices Supported 172

CCP

Programs

Used

in Generation 84 System

Programs

Required 112

Generation

Utilitv ($CCIPP) 84

SCP

Generator

($CGxxx) 84 APPENDIX E. GLOSSARY 173

Initialize Assignment

File

Build

($CCl

BFl U

Initialize

Trace/Dump

F

ile

($CCl

DP)

lProqram

Number

5704-SC2 onlyl 84 STORAGE

ESTIMATES AND PERFORMANCE

Source

Modules Used in Generation 85 CONSIDEBATIONS

Using

This Appendix 176

86 | Maximum CCP System Example

(5704-SC2

Only) 2O4

Disk Storage

Estimates

f

or the CCP 219

. 224

APPENOIX

F. CONFIGURATION

LIMITATIONS,

175

Generation Considerations 85 Conf

iguration

Limitations

and Main Storage

Estimates 175

Support

of the Display Adapter 85 Estimating

CCP

Conf

iguration

Limits 175

Support of BSCC

(Binary

Synchronous

Communications

Controller)

Support

of a Large Number of Terminals

(Program

Number 5704-SC2 only) 86 Tips

for lmproved

Performance

and

Main

Storage

Utilization 223

CHAPTER

7. ASSIGNMENT STAGE 87 CCP

User

Task

Priorities

Planning

for Assignment 87

Requirements

f

or Assignment a7 AppENDlx

c. tNsrALLATtoN

vERtFtcATroN

Assignment

Restrictions

(5704-SC2

only) 88 PROGRAM Z2g

Assignment

D iagnostics 88 Loading the CCP to Run CCPIVP 229

88 Procedure for Requesting CCPIVP 230

Assignment

File

($CCPFI

LE)

Assignment Statements

(Assignment

Build Program) 88 Operating Instructions

with CCPIVP 23O

Assignment Control Statements 91 Normal Operating

Messages 23O

Writing Assignment

Control Statsments 91 User

Error Messages 23O

SOURCP Statement

// SET Statement

// SYSTEM

Statement

User

Requirements

SUMMARY

CHART

APPENDIX C. MESSAGES

APPENOIX

D. DEVICES AND PROGRAMS

o?

93 tNDEx

94

151 IPL Initial

program

load

231

// TERMATTR Statement 100 L1ST OF ABBREVTATIONS

// BSCALINE Statement 103

// BSCATERM

Statement 106 ASCII American

National

Standard Code

for Inf

ormation

// MLTALINE Statement

// MLTATERM Statement

108 I ntercha nge

// PORTLINE Statement

(Program

Number 111 BSC Binary

synchronous

communication

BSCA Binary synchronouscommunicationsadapter

5704-SC2 only) 113 BSCC Binary

synchronous communications

controller

i/ TERMNAME Statement 116 CCP Communications

control prograrr!

// DISKFILE Statement '117 CPU Processing unit

// SYMFILE

Statement 122 CRT Cathode

rav tube

// PROGRAM Statement 126 DA Display adapter

Program

Find Routine (Program

Number

5704-SC2

only) 132 DFCR Display

format control routine

Format Find

Routine

(Program

Number 5704-SC2 only) 133 DFF Display

format

facitity

Disk

File

Close/Open

Facility 133 DFGR Display

format

generation

rourine

Assignment

List Program 134 DSM Disk system management

// LIST Statement 135 EBCDIC Extended Binary Coded

Decinral Interchange Code

Sample

Assignment

Build Execution 137 EOJ End of iob

Sample

Assignment

Set: Calculation

of Main EOT End of transmission

143 EXlo Execute

input/outputStorage

Sizes

User Security

Data

Program

($CCPAU) 149 t/O Input/output

I rCf Interactive Communications

Feature

CHAPTER

8. SYSTEM

HISTORY

AREA COPY

PROGRAM ' IOCS Input/output control system

(PROGRAM NUMBER 5704-SC2

ONLY) 151 IOS Input/output supervisor

Operating

Considerations 151 LRC Longitudinal

redundancy

check

APPENDIX

A. GENERAT

ION CONTROL STATEMENT MFCM Multi-f

unction card machine

MFCU Multi-function card

unit

153 MLMP Multiline/multiooint

MLTA Multiple line

terminal

adapter

MRT Multiple requesting terminal

159 NEP Never+nding

program

OCL Operation

control language

167 PAS Program

appended

storage

PCT Program

control table

PFGR Printer f

ormat

qenerator

routine

SUMMARY

CHART

APPENDIX

B. ASSIGNMENT CONTROL

STATEMENT

SUPPORTED

AND REOUIRED 169 PRUF Program request

under formal

Terminals

and Features Supported 169 RPO Request for price quotatron

System

Device and

Program Requirements 172 SCp System control program

172 SWA Scheduler work

area

TP Teleprocessing

VTOC Volume table of contenrs

Device

Requirements

The

communications

control

program

(CCp)

is

a sysrem

control

programming

feature

that

allows

the IBM System/3

Model

15

to support

an

online network

of terminals.

CCp

enables

terminals

to call application

programs

as needed

and permits

those

programs

to access

a common set

of disk

files. lf sufficient

main

storage

is

available,

the

CCp

permits

several

application

programs

to be executing

concurrently,

though

independently

of one

another;

that is

the

CCp

pro-

vides

for multiprogramming

within one

partition.

The CCP is designed

to make

a communications-based

sys-

tem

as

easy

and

inexpensive

as

possible

to establish

and

operate. The CCP

can be

tailored to suit diverse

oata pro-

cessing

environments

involving

batch

and

online

applica-

tions.

Note: lt you are

not acquainted

with the terms used

in

this introduction,

you can

find them

explained

either

in

Appendix E: Glossary, or in the Data processing

Glosnry,

GC20-1

699.

TERMINAL OPERATOR

FACI

LITIES

Under

control

of the

CCP,

the

operator

of a terminal

can:

Request

programs.

Specify

whether a program

request

should

be rejected

if

the

program

cannot

be executed

immediately,

or whether

the request

should be

placed

on a

queue.

Specify

the disk files

to be used

by a particular

program

or series of programs.

Change

the

symbolic name

of the

terminal.

send a message

to the system operator.

Release

the terminal

from a

program

in

order

to enter

another

program

request

or command.

Request

the operation

of a series

of tasks

via task

chain-

ing

(Program

N.umber

5704-SC2

onlv).

Request

sort

operations via

the

CCP/Disk

Sort Program.

(Program

Number

5799-ATH

is used

with SCP

5704-SC1;

5704-SM7

is used with SCP 5704-SC2.)

Find

new

or updated

programs

and

formats

(program

Number

5704-SC2

onlv).

Request

the

online

test

to determine

whether

the

termi_

nal

is

operating

correctly.

Chapter

1. Introduction

SYSTEM

OPERATOR FACI LITI ES

The

system

operator

initiates

and terminates

the

activity

of

the CCP

and controls

the operation

of the communications-

based

system. After the CCP is loaded

into main storage,

it asks

the system

operator

one or more

questions.

This

allows

the system

operator

to identif

y the

set of f iles,

programs.

terminals,

communication

lines,

and terminal

names

to be

used by the CCP

on the current run (one

or

more

of these

sets were

defined prior to the current run of

the CCP-see

index entry: assignment

stage). These

ques-

tions

also

allow the

system

operator to modify a selected

set

to adapt to a particular

run of the CCP.

During

the operation

of the CCP,

the system

operator

controls the system

through

the Console Keyboard.

The

operator

can:

o Monitor

the

status of the system at

any

moment.

o Determine

the unfulf illed

requests for programs

or sys-

tem operator replies

in

the

system at any time.

Send messages

to terminals.

Change the

status

of terminals

on

the

system.

Cancel,

suspend, and

resume activities

of programs.

Change the

actual terminal referred

to by a terminal

name.

Request

the

online

test of terminals

to determine

whether

they are

operating

correctly.

Close

CCP files.

Open the previously

closed CCP

files.

Shut

down CCP.

Change

interval

polling

times.

Recover from terminal

errors.

Save

trace

table information.

Activate or deactivate

automatic retries to terminals

in error recovery

and

control the frequency

of retries

(Program

Number

5704-SC2

only).

Initiate

or terminate the

CCP

loadable

trace.

O

o

a

I ntroduction

The

system operator

can

also

perf,rrm

some

of the

functions o Automatic translation of transmission data codes

of a terminal operator

such

as

request

programs,

enter com-

mands,

and,

for Program

Number

5704-SC2, find program5 o Dynamic,

program-controlled

allocation and

dealloca-

and

formats. tion of terminals

Because of the extent of the control exercised

by the sys- . Access

to communications l/O error or exception

tem operator, he

or she

must

be thoroughly

trained

in the information

operation

of the

CCP, application:;

of the

CCP

in

the

installation,

and the

specific tasks to perform

under

control o Interaction with external buffers

(Program

Number

of the ccP. 5704-SC2 ontv)

PROGRAMMING

FACILITlES

Prograrns

that run

under the CCP

can

be

written

in any of

four

programming

languages:

r RPG II

o COBOL

. Initiation of a task

(including

a

sort task)

from an

active

task

via

task chaining

(Program

Number

5704-SC2 only)

DEVICES AND PROGRAMS SUPPORTED

The

terminal devices, system

devices, and system

programs

required

and supported

by the CCP are

listed in Appendix

D.

o FORTRAN

lV

ESTABLISHING AND OPERATING

THE CCP

o Basic Assembler

The

CCP can

be

tailored

to suit each unique operating

en-

Although

the design

of programs

lvritten

for the CCP might vironment. Establishing

and

operating the

CCP in a

partr-

be different

from those the

programmer

has

been writing, cular environment is accomplished

in

three stages:

programming

statements

used for terminal input/output

are

already familiar

to programmers: a Generation

o In COtIOL

or FORTRAN:

the call

statement. . Assignmenl

. In RPG ll: either the exit

operation or a

special

file. . Operational system

startup

r In

Basic

Assembler:

macro instructions

that can

be

processed

by

the disk

system

rnanagement

macros" Generation

Stage

With each request for terminal l/O,

the

programmer provides CCP

generation

is the

process

by which a user creates

an

a

list of parameters

that

tell the CCP which

specif ic individual

version

of the CCP. The

purpose

of generation

rs

operation

to perform,

which

terminal

to use,

and what to create a set of CCP

object

modules and subroutines,

data

area to use. unique to that user's requirements, on the user's

disk

pack.

The

process

of qeneration

involves:

The CCP

allows the

programmer

to identify

terminals

by

symbolic

names. lf a particular

terminal is unavailable for 1. Describing the type of equipment to be used by the

any

reason,

the system operator

can

reassign

the

symbolic communications system

and

the

facilities

that should

name

to a different terminal. Thus,

the

program

need

not be included in

that system.

be

changed or recompiled

to address

a

di{ferent

terminal.

2. Creating a set of control routines

whose

specific

con-

Other facilities offered by the CCP

to the programmer

are: tent may

be unique to the user's installation.

o Access

to the name

of the terminal

that requested

the 3. Joining the routines by a

link-editing

process.

program

4. Copying appropriate additional

supporting

routines,

. Access to attributes of individural

terminals

5. Initializing the

assignment

f ile used by the assignment

. Support

for overlay

programs stage and

the

operational stage.

Assignment

Stage

Assignment

is

a special,

brief

CCP

run

during

which

the

user

specifies

one or more

sets

of specific

environments

in

which

the

CCP will run. Each

set includes:

a Specif

ic items

of information pertaining

to the entire

CCP,

such

as the current password.

o Programs

that can be

run under

the

CCp

and

the

resources

each

requires.

o Files

that are

accessible

to each

program

and how

they

are to be accessed.

o The

current

line/terminal

conf

iguration.

The

assignment

run

need

be repeated

only

when

the

user

wishes

to change

some

of the

specific

information

given

in

a

run.

Operational

Stage

The operational

stage

begins

with operational

startup,

when

the

CCP

is loaded

into

main

storage.

During

startup,

the

CCP routines

open

disk f iles,

a<lapters,

and

communica-

tion lines

and complete

various

tables

and control

blocks.

During

operation,

the CCP

performs

the functions

requesr-

ed by terminal operators

and

the svstem

operator,

executing

application

programs

as

rlirected

by those

ope

rators.

The

operational

stage

is concluded

by shutdown.

which is

initiatecl

by the

system operator. During

shutdown,

the

CCP allows

currently executing

programs

to complete

processing,

then

closes communica'tion

lines,

adapters,

and f iles.

CCP TASKS

Each

body of code.

such as an

application

program,

execur-

ing independently

irr

the CCP

program

partition

is consid-

ered

a task. lt is

possible

for two or more copies

of the

same

program

to be

executing

concurrenlly

and

independ-

ently under

the

CCP; in this

case,

each

copy is

considered

a

task.

Tasks

are identified

as

either user tasks

or system tasks

(see

CCP System Operator's Guide, for uses of the task

identification).

An example

of a

user task is

an

inquiry

program,

loaded into main

storage by request from

either

a terminal

operator

or the system

operator;

an

example

of a system task is

the CCP communications

manaqement

task,

which processes

requests for terminal l/O.

The

management

of tasks,

as

performed

by the CCp,

permits

tasks

to be initiated

and terminated

independently

and to

operate

concurrently.

When user

tasks run

concurrently,

results

are identical

to those

that would

occur had

each

task

run

alone. Under

CCP,

1-15 user tasks

can execure

concurrently;

tasks

can be

from

4K to 32K

bvtes.

RELATIONSHIP

TO

OTHER PROGRAMS

Figure

1 illustrates

the relationships

between

the

CCP and

disk

system management

and

between

the CCP

and

application

programs.

Disk

System

Management

(DSMI

The

CCP

operates

in conjunction

with DSM

and

uses

the

following

facilities

of DSM

wherever

possible:

. DSM

Supervisor:

Used for program

loading,

disk

and

unit record

physical

l/O

control

(lOS).

On

Program

Number

5704-SC2, use

enqueue

and dequeue.

Disk and Unit Record Data Management: Used for

logical control

cf

disk

and

unit record

l/O.

DSM

Console Management'

Certain CCP

display transi-

ents run

in the

DSM

transient area and interface directlv

with DSM

console

manaqement

transients.

MLTA and/or MLMP

/OCS: The

CCP incorporates

either or both

of these System/3

communications

l/O

programs,

depending

upon the line

conf

iguration

of

the system: the multiple

line terminal

adapter

(MLTA)

RPQ

(request

for

price quotation)

program

for

start-stop

terminal; the multiline/multipoint

(MLMP)

IOCS for

binary

synchronous

terminals attached to System/3

by

the

binary

synchronous

communications

adapter

(BSCA

lines

1

and

2). your

communications

programs

do not

(and

rnust

not)

use

the

communications

IOCS

directly;

the

CCP calls

the

appropriate

IOCS

when needed.

based

on the instructions

you

issue in

your

program.

BSCC

IOCS: The

CCP incorporates

this liO support if

BSC

lines

3 or4 are used.

This l/O

support

is

part

of

DSM

and

can

be

used

if BSCC

was specified

during

system

generation.

This

support is used

only

by CCP.

SIOC

IOCS: The

CCP incorporates

this l/O

support

if an

RPO

(request

for

price quotation)

for

SIOC

channel

connected

systems is

used.

For

additional

information,

see l8M System/3

Model l5D Channel

Connected

Systems Program

Reference

and Logic

Manual, GC21

5i99 (Program

Number

5704-SC2

only).

Introduction 3

Supervisor Area

User application

program

Communications

Control

Proqram

Commun

ication

control

program

under

control of System/3

disk

system management

User

application

programs

running

under

CCP

User

application

program

Program Partition

1

am

Partition

2

Program

Partition 3

(Program

Number

5704-SC2

only)

Figure 1. Relationships between System/3 Disk System Management,

the Communications Control Program,

and User Application programs

Existing

Communications

Programming

Support

The RPG ll telecommunications

ferature,

which provides

support

for batch

terminals in RPG

ll, is not a

part

of the

CCP

and cannot

be

used under

the

CCP. Application

prJgrams

using

these features

can,

however,

be executed

in

another

program

partition

from the CCP

as long

as

their use

of communication

lines does

not conf lict

with

the

CCP.

Application Programs

Application programs

can

execute

under

control of the

CCP

or, in

another

partition,

under

control

of DSM.

Telecommunication

application

programs

that execute

under

the CCP

are one step

removed

from control by DSM.

They

are

loaded

by the

CCP

and receive

control

from the

CCP. Requests

by these

programs

for system

services are

received

and scheduled by the CCP. Some requests

are

performed

by the CCP;

some

are

passed

from the CCP

to

DSIV1

to be performed.

A telecommunications

application

program

that executes in

a non-CCP

partition

must include

the communications

IOCS

routines

it requires. lts

use of communications

lines

must not conflict with the CCP.

Some noncommunications

application

programs

not

originally

written

to run under CCP

control can

be executed

under

the CCP. These

programs

can be requested

from the

svstem

operator's

console

or from a terminal if they do not

violate

any

of the restrictions

placu'd

upon

CCP

programs

and if they

are

defined

in an

assignment

set. lf such a

program

has not been rewritten

to release

the requesting

terminal,

then

the terminal

is not I'ree

to enter

another

command

or program

request

until

the requested

program

term i nates.

Noncornmunications

applicatiorr

programs

can

be executed

in

a

non-CCP

program

partition

wfrile

the

CCP is

operating

if they

do not

conflict

with the

CCP in

their use

of svstem

resources

(disk

files

and unit record

devices).

System Programs

System

program

facilitiesr

such

as

urilities,

compilers,

source library

Get/Put,

or SYSPRINT)

cannot

be run

under

CCP. Sorne

system

ltrograms

can Lrc run in the non-CCp

partitiort(s)

while

CCP is executing,

and

some

dedicated

system

programs

require

that

CCP be

shut down before

they

can be

executed. For

more

irrformation,

see the

appropriate

SCP reference

manual

listed

under Related

Publications in the Preface.

'The

spool

f

ile

copy

program

($OCOPY)

is

an exception.

$OCOPY

runs

under control of SCP and.

if its

name

rs

changed

so that

it

beEins with sonrething other than

$, $OCOPY

also

runs under

control

of CCP {Modet

15

5704"SC2 onlv).

I

ntroduction

To

the operator

of a

terminal,

the

system is

a resource

to

help

him accomplish

his

tasks" The

terminal

operator

rnight

think of the system

as belonging

to him

or her

alone,

unless

the

combined

demands

upon

the

system

are

great

enough

to cause delay

in its responsiveness.

All contention

among terminal

operators

for use

of the

system is

managed

by CCP.

The

CCP distinguishes

two

types

of terminals:

Command

terminals,

which

can request

services

of the

CCP including

the running

of application

programs.

Data

terminalq

which

cannot request

services,

and are

used only

as

directed

by

the application

programs.

In

order

to call

for

application

programs,

the

command

terminal

operator

must first

sign on

to the

CCP. A sign-on

request

is

a message initiated

by the terminal

operator

signifying

the wish

to request

services

of the CCP. lf the

system has

a

password

security feature

(an

option

selected

during

the

CCP

generation-see

index

entry initial model,

the terminal

operator

must

correctly

enter

a

password

with

the

sign-on request.

Once a terminal

operator is in

communication

with

the

requested

application

program.

he

or she

enters data

as

required by

the

program.

The

sequence

of operations at

the

terminal, and

the

format

of data

sent

to and from it,

are entirely directed

by the application

program.

The

terminal

operation

continues

to be

directed

by the applica-

tion

program

until

that

program

releases

it. However,

the

operator,

while

sending data from

the

terminal to

the appli-

cation

program,

can reestablish

cornmunication

with the

CCP in order

to:

a Send a message

to the system

operator

and then resume

sending data

to the

program.

o Release

his

terminal from

control

of the

program.

When

a terminal

operator

f

inishes

making a

series

of re-

quests

for services

of the

CCP. he

or she normally

signs off

the terminal.

This

action restores

the terminal

to an initial

status, such that it must be

signed on

again

(with

a

pass-

word,

if that

option was

chosen) before

it can request

services

of the CCP.

Cirapter 2. Using the CCP fnom

a Terminal

HOW

THE TERMINAL OPERATOR REOUESTS

A

PROGRAM

When

a

command

terminal is

not in use, it is

continually

monitored by the control prograrn

for a request. The

terminal

operator calls for an application

program

to

perform

a specific function by simply entering

the

program

name

at the terminal. The CCP

then atternots to load and

execute the program

and to put

that prcgram

in communr

cation with the terminal operator.

From

then until

the

completion of the program,

the interaction between

the

terminal operator and the system

is ijictatecl

by that

program.

When

the application

program

completes execution, it

yields

control of the terminal to the CCF. The

CCP

once

again monitors

the terminal

for a terminal

cornmanrl

such

as a program

request. The next program

request

does not

have to be for the same

program.

Each

terminal

operator

must

be trained in the functions he

or she can call upon and

in

the procedures

for interacting

with the

application

programs

that perform

those functions.

HOW

THE TERMINAL OPERATOR REOUESTS

SYSTEM

SERVICES

While

monitoring for program

requests, the CCP

can also

respond

to commands to perform services

f

or the ternrinal.

The operator can specify ahead of time what the systern's

response

should

be when it is

unable to cornply immediately

with his request for a program. The systenr might be

temporarily too busy with requests from other operators.

By command, he can

choose one

of the

{nllowing responses:

o The

system

denies

the

request

and allows

him to rnake

some other request.

o The system

holds

the request

and honors

it as soon as

possible.

Once the operator of a terminal has

specif

ied

one of these

requests. the CCP handles

all program

requests {rom that

terminal accclrdingly

until the

operator specif

ies

dif

ferently.

Using the CCP From a Terminal 7

A f

ile

specif ication

allows the

operator

to specify

the disk

data filt:s

that

are to be accessed

lcy

programs

he

or she

requests,

if those

programs

are

written

to accept the

specifi-

cation. V/ithin

the

inf<irmation

s,ystenl,

there may

be

several

f iles

containirrg

similar

data

in the same

format. A

school

system, for exarnple,

mighrt

have

a

separate

student

records

file for each

school,

An application

program

requeste(J

by the oper€tor

might have

been written to access

any

one of these

files,

but

the

program

must

be

told which

file

to use on a particular

run. A file

specification

conrmano

issued

by the terminal

operator

applies

to all

programs

requested

at that terminal

until

a

contradictory

commano

is issued.

Another

command

permits

the terrminal

operator to send

a

message

to the system

operator,

requesting

some action to

be taken.

The

commands discussed

so

far

are

issued

to thre

CCP while

it is

monitoring

a terrninal f<lr

rec;uests.

Once

a terminal

is

interactirrg

with an appiication

program,

however,

the

input

from that

terrninai

is nrcaningful

only to the application

program,

with one

exception. Tl-re

CCP

checks eacn

message

from a termininl

to a pro{lram

for a certain

string

of characters

def ined irr

your svslem.

When it detects

these

characters

in

a

message,

the

CCP interprets

the

rnessage

as

an

attempt by the terrninal

operator

to escape

frorrr

control

of the

application

program

and

communicate

directly

with the CCP. At this

poirrt,

the

CCP accepts

a

reque$t

from the operator

to releiese

the terminal

from the

control

of the

applicatron

prograrn,

or to send

a message

to

the

system

operator, lf the request

was

to send a message,

the

terminal

operator

can ask

the CCP

to resume

execution

of the

applicatiorr

program

after

the

message

is

sent.

.TERMINAL

MODES

Tl-rere

are

two classes

of terminals def

ined

previously,

based

on whether

or not the

terminals

are

capable

of entering

commanrls

to the CCP: commanrl

ternrinais

and data

ter-ntirtal:;

(ser

Anpendix

E. Glcx;aryl. Data

terminals

are

capable

only of transrnitting

or re,ceiving

data

under

control

of an

application

progranr;

they

are not capable

of cclm-

manding

CCP

services.

ly'Jhen

data

terminals

are nor

communicating

with an application

program.

they

are

in

a

standL)y mode

{rrct

polled

by the CCP

for input). Because

the

oprerator

of a rJata

terminal

does

not interact

with the

CCP,

this;

chapter deals

oniy with the

operation of command

Lermirrals;.

Atthnugh

there are

ofJef

ating

differerrces

aj-r.long

the various

termirral

tyFre$ that can be used

as

command

terminals,

the functions

that

can be

0erfornred

trv

thern

are the

same.

The

primary

function

of any command

terminal is to re-

quest

the execution

of application

programs.

All of the

activities a terminal

operator

performs

are related

to that

f unction.

lnitial Mode

When

a command

terrninal is

online,

it is

physically

at-

tached to the

system

and

logically

attached to the CCP.

The

CCP

monitors

it corrtinuously for program

requests

or

other commands. Before

a program

can

be requested,

the

operator

must

first

sign on at the terminal. Signing

on

involves

communication

between

the terminal

operator

and

the CCP. Before

and during

this communication,

the

terminal isin initial mode. Commands for CCP services

other than

system operator

commutlication cannot

be

issued from a terminal when it is

in initial

mo<Je.

The

end

of initial mode

occurs when

the terminal

operator

is

successfully

signed on.

From

the

point

of view

of the terminal

operator, signing

on

may be

as simple

as

entering

the sign-on command. How-

ever,

if access to the system from a

terminal

must be limited

to certain authorized

people,

the sign-on

procedure

can

involve

providing

additional

information

required

by a

security feature. The security feature

can be either

the

password

security option provided

by the CCP

(see

index

entry: pa$sword

security

aptionl or a routine written by

the user

to control access to the system

in some

other way.

Command Mode

After a terminal

operator

is

successf

ully signed

on, the

terminal is

in

command mode. This means

the operator

can

request

the CCP

to load

and execute

programs

and can

issue related

commands. Once a terminal is in

command

mode. it remains

in

command

nrode

until

a program

re-

quest

is made

from the terminal (see

Terminal

Operator

Commandsl,

the operator signs off, or the system

operator

varies the terminal

offline.

Data Mode

Once

the terminal operator

issues a command to load and

execute

a

user

application

program,

the CCP loads the

program

and

gives

it control. At that point,

the terminal

enters data

mode;

ll\at is, the

terminal is in communication

with the application

program

itself. The

nature of the

communication is,

of course,

determined by the

application

prograrn.

Nornrally.

the

terminal

remains

in data mode

until the application

prograrn

completes

processing

or

releases

the termirral. At that time. the terminal is again

placed

in

command rnode

and

is

able to issue

another

rrrogram

request.

Command

lnterrupt

Mode

The

operator

of a terminal

need

not

wait

until

a

program

completes

its

job in

order

to interrupt

it. By

entering

a

string

of six

characters

that

are

significant

to the

CCp

(determined

by

the

user

at

generation

time),

he

can

indicate

that

he

wants

to escape

from

data

mode

and

enter

command

interrupt

mode

(see

index

entry: data

mode

escape).

While

in

this

mode,

he

can

send

messages

to the

system

operator.

resume

execution

of the

program,

or release

his

terminal

completely

from

the

control

of the

program

(at

which

point

the

terminal

is

again

in

command

mode).

TERMINAL

OPERATOR

COMMANDS

Two logical groups

of terminal

operator

commands

can

be

issued

after

sign-on.

First,

while

the

terminal

is

in

command

mode,

before

a

program

request

is

actually

made,

the

terminal

operator

can issue

various

commands

pertain_

ing

to the

subsequent program

request:

Tell

the

CCP

how

to handle

his

request

if it cannot

be

honored

immediately (see

eueue/No_eueue

Commandsl.

lssue

commands

that

indicate

which

files

are

to be

accessed

by program

requests

(see

Fite

Specification

Commandl.

Tell

the

CCP

by

what

name,

of

a set

of names

defined

as

valid,

the

terminal

should

be

known

to the

prograrn

he

is

requesting

(see

Name

Commandl.

Send

a message

to the

system

operator

(see

Mesage

Commandl.

This

can

also

be

done

prior

to sign-on.

The

second group

of

commands

is used

during

command

interrupt

mode.

After

data

mode

escape,

the

terminal

operator

can:

o Send

one

or more

messages

to the

system

operator

(by

using

the message

command).

o Release

the terminal

from

control

of the

application

program (see

Release

Commandl

.

o Resume

execution

of the

program (see

Run

Commandl.

Sign-On

Command (/ON)

The

sign-on

command

notifies

the

CCp

that

the

terminal

operator

wishes

to begin

making

requests

of the system. lf

the system

uses

a security

feature,

the sign_on

command

must

be

accompanied

by one

of the

followinq:

1. The current password

required

by the CCp password

security

feature.

2. lnformation required

by a user-written

sign-on

rou_

tine.

The CCP

logs

every

sign-on

attempt on the system

opera-

tor's

console

and indicates

if sign-on

was

successful.

lf the

sign-on

was

successful,

the

CCP

notifies

the

terminal

operator

and

allows

him to enter

a

command. lf the

sign_on

was

not successful.

the CCP

allows

the terminal operator

to

attempt

to sign

on

again.

While

a terminal

is

in initial

mode.

the

name

of the

terminal

can be

changed.

The system

operator

can

change

the name

by using

the

assign

command. Sign

on restores

the original

name

of the

terminal.

Once

the

operator

signs

on at

the terminal,

he

can

make

any

number

of requests

without signing

on again.

However,

if the

terminal

operator

leaves

the

terminal

unattended

and

access

to the terminal is restricted

by a security

feature,

he

should

sign off when he leaves

(see

Sign-Off

Commandl. lt

he

signs off, he

must

sign

on again when

he

wants

to use

the

terminal

again.

Queue/No-Queue

Commands

(/e and /NOOI

The

queue

or no-queue

command

indicates

how the CCp

is

to handle

program

requests

from this

terminal

which

cannot

be honored

immediatelv:

Command Meaning

/O The operator

waits for the program

to start.

The

CCP

places

the

request

on a

queue

and

honors

it as

soon

as

possible.

/NOO The operator

does

not wait if the program

cannot start immediately. The CCp rejects

the

command

if it cannot

be honored

immediately

and

allows

the operator

to enter

another

request.

Using

the CCP From a Terminal 9

A queue

or no-queue

command

remains

in

effect

until

the

terminal

operator

enters

a different

queue

or

no-queue

command

or until

he

signs

off. lf neither

a

queue

nor

a

no-queue

command

is

entered

at the

terminal,

the

CCp

assumes

the no-queue

option. For

tasks

requested

via

task

chaining,

if the request

was

successful,

CCp

handles

the

request

the

same

as a

queued

terminal

program

requesr.

y't/ote.'

Once

a terminal has

a

program

request

queued,

the

request

cannot

be removed

from

the

queue

except

by

the

system

operator.

Oueued

chain

task

requests

cannot

be

canceled.

There

are

five

situations where

the

/O

command

is

effective

for program

requests:

A disk file

is

temporarily

not available

because

of file

shari

ng.

The

nrain

storage

for the

program

is not available.

A required

terminal

is

temporarily

in

use.

A multiple

requesting

terminal

(MRT) program

is active

and

already

has

the maximum

number

of requesters.

The nraximum

number

of programs

might

already

be

executinq.

File

Specification

Command

(/FlLEl

The

file

specification

command specifies which

of several

data files

to use

on a current

program

run. The

terminal

operator may use the file specification command to vary

the files

that

are used by the programs

he

requests. The

file

specification command

cannot

be used with multiole

requester

programs

and is not used

with a chain task

request.

Certain

application

programs

are written

to access any

of

several files

containing

similar

data

in

the same format by

referring

to a

symbolic file in the program. For the program

to actually

access

a

file,

the name

of the

symbolic file must

be

associated

with the

name

of a

file

that

actually

exists on

disk, a physical file.

Suppose,

for example,

a school

system

has

a separate

stu-

dent records file for each

school. A student report program

can

process

the student records

file from any of the schools,

but it must

be told.

by a

file

specification

command, which

of the files

to use on a

particular

run (Figure

2).

Symbolic file name

used in

the program.

File

specif

ication

command

says:

"For

this run,

SCHOOLX

is

SCHOOLl."

,

- - _ _ - /l

I

- - - -.,i

/l

I

(

I

t-

I

SCHOOLX

Figure

2. lllustration

of File

Specif ication

Command

10

SCHOOL3

Physical

f

iles to which

the

symbolic f ile name

can refer.

SCHOOL2

A f

ile

specif ication

command

is in

effect

for

all subsequent

program

requests

from

that

terminal

until

the terminal

operator

enters

a

new

file

command

for

the symbolic file

or

until he

signs

off f rom

the

terminal.

Thus,

the

f

ile

specif ica-

tion

command

can

apply

to

more

than

one

program.

lf

a terminal

operator

enters

a file

specification

command

without

naming

any files,

he

cancels

all

file

entries

currently

maintained

for

that

terminal

by

the

CCP.

lf he

enters

a file

specification

command

that

gives

only

a

symbolic

f ile name

with no

associated

physical

f

ile name,

that

symbolic f

ile

entry is

deleted

from

the list

of file

entries maintained

by

the

CCP for

that

terminal.

Signing

off from

the terminal

cancels

allfile

specifications

in

effect

for

that terminal.

The

CCP informs

the terminal

operator

if the file

specifica-

tion

command

he

entered

was invalid.

When

doing

task

chaining,

the

/FILE command is

valid

only for

the

first

task

(the

task

loaded

via

a terminal

or console).

The

sym-

bolic file

associations

are

not

considered

valid for other

tasks

in the chain.

Name

Command

(/NAME)

The

name

command

tells the

CCP

which

symbolic

name

to

use for

this

terminal. This

symbolic name

is

taken from

a

set of previously

assigned

symbolic

names.

The

CCP uses

this

name

for

this terminal

from

sign-on

to

sign-off,

or

until

another

name

command

is

entered.

The

CCP

passes

the

symbolic

name

to

any

program

this

terminal

requests

in order to identify the requester

lsee

IBM System/3

Com-

munications Control Program

Programmer's

Reference

Manual,

GC21-75791.

The

CCP

maintains

a list of symbolic

names

eligible for

each

terminal. These

names

are

associated

with

the terminal

during

the CCP

assignment. The

terminal

to which

they

apply can be

changed by the

system

operator. The

primary

purpose

of the name

command is

to allow

a

terminal

to

assume

(with

the

consent of the system

operator)

the name

of

another terminal

(of

a similar

type) that is

currently not

operable.

Program

Request

Command

The

terminal

operator requests

a

program

to execute by

entering

the name

of the

program.

lf a

program

allows,

input

data

can be

entered

with the

program

request.

Before

the operator

enters

a

program

request,

he

should

consider

whether

queue

or

no-queue, file,

and name

commands

are required for

that

program.

He

should

determine

this

from

a

document

such as a

program

run

sheet for that program

(see

Planning

Considerations),

if he

is

not

familiar

with

the requirements

of the

program.

The

CCP informs

the terminal

operator

by a

message

if it

rejects

the

program

request. For

a chain task request,

all

messages

are

directed

to the system

operator.

Data

Mode

Escape

Command

The

terminal

operator

can interrupt

an application

program

he

requested

(when

the terminal

is in

data mode,

under

control

of the

program).

To do

this, he

enters

a

predeter-

mined

set of six characters

when

the

program

attempts to

get

input from

the terminal. The

string can

consist

of any

six characters

previously

defined,

during

generation,

to the

CCP

as the data mode

escape characters. While

a

requesting

terminal

is in

data

mode.

the CCP continuously

monitors

input from

the

terminal for

these

characters as

the

first

six

input

characters.

After

the terminal

has

Interrupted

the

application

program,

the

terminal is

in command

interrupt

mode

and the

operator

can:

o Send

one or more

messages

to the

system operator

(see

Message

Commandl.

. Resume

execution

of the application

program

lsee

Run

Commandl.

o Belease

his

terminal

completely from

the

application

program

he interrupted

(see

Belease

Commandl.

Release

Command

(/RELEASE)

The

release

command

can only be issued while

the terminal

is

in

command interrupt

mode;

it is invalid

at any other

time.

The

release

command

releases

the

terminal from

the control

of the

application

program.

The

application

program

then

receives

a

return

code. This

return

code informs

the

application

program

of the terminal

operator's

action. The

terminal operator

is

then free

to enter

another

program

request

or

other commands.

Using the

CCP From a

Terminal 11

Message

Command (/MSG)

The terminal operator

uses

the message

command to send

a message

to the system

operator. The text of the message

follows on the same

line. The message

command can be

entered

when

the

terminal

is

in initial

mode.

command

mode,

or command

interrupt

mode.

Run

Command

(/RUN)

The run command causes

an application program

to resume

reading

input

data from a terminal. This

happens

after

the

terminal issued

a data mode

escape

command and, possibly

sent

one or more messages

to the system

operator. This

command returns

the terminal to data mode

from command

interrupt

mode.

Sign-Off

Command (/OFFI

The

sign-off

command

returns

the terminal

to initial

mode

or places

it offline. The sign-off

command can be

accom-

panied by either the word hold or the word drop.

Hold The

terminal

is returned

to initial

mode. The

CCP

accepts

only a sign-on

command or a

message

command from the terminal.

Drop lf the

terminal

is

connected

by a

switched

line,

the

line is

disconnected;

the

terminal

can re-

establish

the

connection

only by redialing

the

system. lf the

terminal

is

connected

by a non_

switched

line,

the

terminal

is

placed

offline;

that is,

the

CCP will accept

no commands

from

the

terminal

until it is

again

placed

online

by

the system operator (see

index entry'. change

the status

of a termina!). At that time, it enters

initial

mode.

lf neither

hold

nor drop is entered.

the

CCp

assumes

the

option that was

selected

during the CCP

assignment

stage

(see

index entries: MLTATERM statement

and BSCATERM

statementl. All sign-off

commands

are logged

on the system

operator's

console

with an indication

of whether

hold

or

drop

was used

as the

sign-off

option.

The sign-off

command can

be entered

anytime after the

sign-on

command,

while

the terminal

is in

command

mode.

It cannot be

entered following a data mode

escape

command

unless

the release

command

has

been

issued.

The

sign-off

command

clears

all

file

specification

entries

in

effect for this terminal (see

File Specification Commandl

and restores

the original

name

of the

terminal lsee

Name

Commandl.

12

PLANNING CONSIDERATIONS

Because

the

terminal operator

will probably

be

calling

pro-

grams

he did not write, he

must

have

access

to information

about the programs

(perhaps

a program

run sheet for each

program

he

can call). This

sheet

will be

unique

to each

installation,

but will probably

contain

answers

to the

follow_

ing

questions:

. What,

from the

terminal

operator's

point

of view,

is

the

function of the program?

r Should

the program

request

be

queued

if it cannot be

honored

immediately,

or should it be relected?

(Should

the terminal operator enter

a queue

or n.o-queue

command?)

o Does

the program

have

to be

told which files

to use?

(Should

the

terminal

operator

enter

one

or more file

specif

ication

commands?)

o Does

the program

expect

to be requested

by this

terminal? (Must

the

terminal

operator

enter

a name

command?)

o Should

the

terminal

operator

enter

input

data

for the

program

at the same time he makes

the program

request?

. What

kind

of input (and

in what

format)

does

the pro-

gram

expect

f rom the terminal operator?

a Are there

any exceptional

conditions

or special situa-

tions

that

can

arise from the

program?

(Must

the

terminal

operator

notify the system

operator in certain situations?

Does

the program

diagnose

error conditions,

what are

they, and what must the terminal operator

do?)

o What are the names

of follow-on programs

that might be

initiated

via

task chaining?

o ls

there

any file contention for files

being

used

(such

as

NOSHR

on Assignment

and

another

partition

using file)?

In

addition

to a program

run

sheet

for each

pr.ogram

he

can

call,

the terminal

operator

also

requires

some

current

information

about

the

system,

such

as:

o lf the password

security

option is in effect.

what is

the

current password

?

o lf the installation

has

its

own unique

sign-on

procedure,

what is

it?

a What

is

the

current

set of terminal

name

assignments

for

the

terminal?

o What are the data

mode escape

characters

for the svstem?

o Should

the

terminal

operator

specify

HOLD or DROp

when

signing

off

-what is

the current

default for the

terminal?

Perhaps

the operator

should

not sign

off until

the end

of the

day.

The

terminal

operator

might

also require

informatron

about

the

schedule

of work he

is

expected

to complete.

o Are

there

certain

programs

called

each

dav?

o Must

the

programs

be called

in

any

particular

order?

. ls

the use

of the

terminal

limited

in

any

way_to certain

hours

or to a

certain

amount

of time

per

use, for

example?

Using the

CCP

From

a

Terminal 13

The system

operator

has

the role

of exercising

final control

over

the

communications-based

system.

He

initiates

its

activity

by loading

and running

the

CCp. He

determines

when the system

should refuse

to accept

new requests

from

terrninal

operators.

While

the

system

is

operating.

he

may

initiate

certain

system

actions,

determine

the

system.s

status,

and

alter

the set

of terminals

permitted ro access

the

system.

He

must

also

make

decisions

when

exception

situations

(such

as error

conditions)

are

detected

by the

communications

control

program

or a

program

running

under

its

control.

Once

the

CCP

is

started,

all

communication

between

the

control

program

and

the

system

operator

is

through

the

console

keyboard.

Messages

from the system

are

displayed

on

the

CRT,

some

requiring

responses

from the

operaror.

His

response

also is keyed

on the

console

keyboard. At

any

point

during

the execution

of the

communications

control program,

the operator

can

command a svstem

action

via

the

console

keyboard.

In addition

to the

operational

control

of the CCp.

the

sys_

tem operator

can

take part in the generation

and assignment

stages

ofthe CCP. See

Chapter

6: Generation

Stage

and

Chapter

7: Assignment

Stage

for tfre required

proceoures

and statements"

INITIATING

CCP

The system

operator

starts

the CCp

by entering

UCL state-

ments

after IPL (initial

program

loarl).

The

OCL statements

load

the CCP

and

supply

OCL FILE statements

for

all

disk

files

usecl

by the programs

to be

run under

the

CCp.

After the

startup

routine

is

loaded.

it asks

questions

of the

system

operator

that

allow

him

to exercise

several

option..

o Select

the

assignment

set for this run.

. Change

the password

assigned

in the set.

. Suppress

access

to certain

disk

data files

that are nor_

mally

accessible

to programs

in this

set.

o Suppress

access

to certain

application

programs

normally

available

in this

set.

o Suppress

the use

of certain

communication

lines

in

the

se t.

o Supf:ress

the use

of certain

DFF r-.xternal

buffers

in

the

set

(Program

Number

S704-SC2

only).

Chapter

3. System Operator

Control

of the CCP

o Suppress

the

use of certain terminals in

the set"

a Change

the main

storage

allocation for cornnrunit;ations

buffer area

assigned in the set.

Changes

specified

to a

set

during

startup do not permarrently

alter the

assignments

in

the set. The

chan.c;es

appiy

only to

the current CCP

execution. To reply to prornrrts

issued

during

startup,

the

system operator

presses

the

PF12

kev,

types

in the response,

and

presses

ENTER.

SYSTEM

OPERATOR COMMANDS

After startup

of the CCP,

the

systern operator

can interact

with the system

in the following

various

ways:

o Communicate

with a remote

terminal

by telling

the

CCp

to send

a

message

to a specific or all available

terminals

and

by receiving

messages from the

terrninals.

Inquire

into

the

status

of the CCP

at anv time.

Modify the status

of the CCP.

Function

as

a remote

terminal

by entering

prograrn

requests

(see

Using the System Operator's Consale

as a

Request

i ng Term i na

|

(s)

l.

Open

and close

CCP f iles

using

open

and

close

prugrarns.

Find

formats

(Program

Number

5704-SC2

only).

Initiate

or terminate

the

CCP

trace

facility

(progranr

Number

5704-SC2

ontyr.

a Control

automatic

retries

of terminals

during

error

recovery

(Program

Number

5704-SC2

only)"

The

system

operator

sends messages,

makes

rnquirics.

arrrJ

modifies

the

status

of the

CCP

by entering

commarrcls

r,rsing

the console

keyboard. To enter

commands,

the sysrem

operator

presses

the PF10

key

and

is

prompted.

All commands

consist

of an operation

code

and

one

or

more

operands.

The

operation

codes

can be

usecl

in

either

their full-length

versions

or in

abbreviated

versiorrs.

In

some

cases,

operands

can

also

be abbreviated.

Specif

ic

opr:r ation

codes

and operands are given in the IBM Svstern/3 Mrtdet lb

Communications Control Program System Operator,s Guirle,

GC21.7619.

o

a

System Operator Control of the CCP 15

Message

Command

(MSG) o Suspended/active/al

locating/terminating/q

ueued i nd icator

The system operator uses

the message

command

to send a o User

program

area

main

storage size

message 1o

a

specific

or all available terminals.

The operator

designates which terminal{s) is

to receive

the message. He o User

program

area

main

storage address

does this by including:

either

the

symbolic terminal name,

the CCP':; terminal reference

identification

with the

message . NO TASKS ACTIVE if system

is inactive

text, or the

keyword

ALL indicating

all available terminals

to the current assignment set. O Size of largest

free

space

The

CCP notifies

the system operator when

the message . Size

of largest available

TP buffer

segment and

size

cannot

be

transmitted

because

the terminal

is

either offline. of total available

TP buffer

not colrnected,

not a command terminal, under

control

of

an appl

ication

program,

or not in

the system, when the

task

number of an

active

task

is entered'

a display

appears

containing

the:

Display Terminal

Status

(D T) o Names of all

attached

terminals

The following

information

about

a

specific

terminal or I t ,nO'".,ion

of terminal

waiting

for TP buffer

about all

terminals def ined to the CCP can be displayed: o Labels of all

allocated

f

iles

o Syrrrbolic

terminal

name' o Task

attributes

such

as

MRT (multiple

requesting

termr-

o ldentification

of the task usino the terminar. nal), SoRT,

CHAIN' DFF (display

format

facility)' or

NEP

(never-ending

program)

. Encocled attributes and status

of the terminal. This

includes

irrformation

about the

terminal ,u.h u, whether ' unit record

devices

allocated

to the task

it i:;

online or offline, signed on, or awaiting some event;

I tfr. operating

mode it is

in;or if

it is

waiting

for

a TP

I Cancel

a User

Program or the CCP

I buffer.

This command

can be used

by the

system operator

to stop

Display

Terminal Assignments

(D

Al processing

a particular

user

program

or to immediatelv

stop

the CCP.

The CCP informs

the

system

operator

if he

This command causes the

ccP to display the

symbolic enters an invalid task

identification and

program

name to

names

and

reference identification

of a specific

terminal or cancel a user

program'

of all

terminals

in

the system.

The

system operator

can use

this

command to display terminal

assignments when

he

wants to enter a command

to change,nu

rurr,nui *ni.n ,, suspend

Requests/Execution/lnitiation

of User

Programs

actually

addressed

by a

particular

symbolic

name

(see

4ssign

a Symbotic Name to a Terminall" This command allows

the system operator

to suspend

user

activity

in any of the following

ways:

Dispray users

command (D u) . suspend

the execution of ail

user

programs

currentry

running under control

of the

CCP.

This command

displays to the

CCP

systems

operator

the

status

of active

user tasks or the status of an

individual user ' suspend the execution

of a

particular

user

program

task. The CCP displays

o Task-id o Stop the

initiation of user

programs

under the CCP^

t Program name

o Requr.'sting terminal

name

to

o

a

Stop

the

initiation

of a

particular

user

program.

Do

not

allow additional

program

requests

from

request-

ing

terminals.

Do not

allow commands

from

command

terminals.

The CCP informs

the

system operator

if he

enters

an

invalid

task

identif ication

and

program

name

or if

suspen-

sion is

already

in

effect for

the

programs

he

specif ied.

A program

can be

canceled

after its operation is

suspended.

A program

can

also be canceled

while in wait (/O) state.

Oueued

chain

task requests

cannot be

canceled.

Resume

Requests/Execution/lnitiation

of User Programs

The resume

command allows

the system operator

to resume

user

program

activity after

a

as

follows:

o When

execution

of all user

programs

running

under

the

CCP

was

previously

suspended,

resume

the execution

of

all

programs.

o Resume

execution

of a previously-suspended

program.

. Allow the CCP

to resume

initiation

of pending

program

req uests.

a When

program

requests

from command

terminals

were

previously

suspended,

allow

command

terminals

to

resume

program

requests.

o Allow command

terminals

to resume

entering

commands.

The CCP informs

the system operator

if he

specified

an

invalid

task

identification

and

program

name

or if the

resumed

task was

never

suspended.

Change

the Status

of a Terminal (VARy)

This

command allows

the system

operator

to change

the

status

of a

terminal

to online

or offline. The command

may

be

given

for all

terminals

on a

given

line

or for a

specific

terminal. The

command

is

not allowed if the

terminal(s)

is currently

allocated

to a

program

or awaiting

a

queued

program

request.

The

CCP

informs

the

system

operator

of the status

of the

terminal

following

the command.

Close/Open

the BSCA Line (CLOSE/OPEN)

This command allows

the system

operator to close

or open

a BSCA

line under

CCP. The close command

closes

the

line under

CCP

for use

in a batch

partition. The

open

command reopens

the

line

for use

under CCP.

/Vote:

This command

applies only to BSCA line

1 or line

2;

it does not apply to BSCC.

Assign

a Symbolic

Terminal

Name

to a Terminal

(ASSIGN)

This

command

allows

the

system operator

to asstgn a

symbolic terminal

name

to a specific

terminal. This

command is

used, for example,

to assign

an alternate

ter-

minal

when

a particular

terminal is

inoperative.

This

command

is invalid

when:

a The

symbolic

terminal name

is

currently

being used

by a

program

running

under

the CCP.

. The

symbolic

terminal name is

the only name

assigned

to an online

terminal that is in

command or initial

mode.

or has

a

queued

program

request.

o Changing

the

assignment would cause a terminal

unit

allocation

conf lict with a current request for a never-

ending

program.

To change the name of a command

capable terminal, not in

initial mode, the

terminal

operator

must

also enter

a com-

mand (see

index entry: /NAME commandl.

Online Terminal Test (TESTI

The TEST

command

allows the

system operator to initiate

the

online test f

acility

for terminals

that are

supported by

either

the MLTA, BSCA IOCS

or BSCC

(see

index

entrv:

online terminal testingl. The operator can specify

that either

a single

or multiple

online tests

be

run for MLTA devices.

The

CCP informs

the system

operator either

when

the com-

mand

is invalid

for any

reason

or when

the test is

started

successfully.

For BSC,

online test results

are displaVed

on

the console.

fy'ofe.'

The system operator

can initiate a BSC online test

only to another

processing

unit or

to the BSCC attachment.

a

System Operator Control of the CCP 1-l

Online

terminal

test

can

also be

initiated

directly

by the

terminal

operator

if he

suspects

that his

terminal

is not

operating

correctly

or if he

wishes

to test it before

he

transmits

data. The

terminal

must

be

capable

of input

and

output. The

CCP

or the

application

program

are

not in-

formed

of a test

that is initiated

by

the

terminal

operator.

Certain

t,erminals

might

have restrictions

as

to what

online

tests

can

be

executed

from

the

central

system

or requested

by

the

terminal

operator.

Change

the lnterval

Polling

Time

(pOLTIME)

This

command

allows

the

system

operator

to change:

. The

arnount

of time

that

CCP

polls

terminals

before

waiting.

o The

arnount

of time

CCP waits

before

resuming

polling.

This

command

is

effective

only if the

interval

polling

option is

selected

during

CCP

generation.

Recover

ifrom

Terminal

Errors

(ERPI

This

command

allows

the

system

operator

to remove

one or

all of the

terminals

on

a

line

from

CCp error

recovery

after

the condition

that caused

the

ternrinal

error

has

been

cleared.

Control l\utomatic

Retries

of Terminals

During

Error

Recovery

(AUTOERP)

(Program

Number

5704-SC2

Only)

This

comrnand

allows the

system

operator to

enable or

disable

tl^re

automatic

error

recovery

facility if

that facility is

specified

by

the

assignment set

currently

in

use.

The

system

ol)erator can

also use

this command

to chanqe

the

frequenc,/

of retries.

Save Trace

Table Information

(TRACE)

This

command

allows

the

system

operator

to enable

or

disable

thre

SCP

trace

facility.

Initiate

or Terminate

the

CCP

Trace

(TRACE)

(program

Number

1i704-SC2

Onlyl

This

command

allows

the system

operator

to initiate

or

terminat€,

the

CCP

trace facilitv.

USING

THE SYSTEM

OPERATOR'S

CONSOLE

AS

A

REOUESTING

TERMINAL

The

CCP

allows the

system

operator

to request

programs

using the

console in

the same way

a terminal

operator re-

quests programs.

The

following

commands

are

available to

the

system

operator:

./a

o /NOO

O /FILE

o Program

request

The effect of these commands is

the same

as

described

for

the terminal operator (see

index entry'. terminal operator

commandsl.

Certain

restrictions

and

assumptions

apply to using

the

system

operator's

console to request

programs:

o The console

is

always assumed

to be

signed

on.

o The

console

cannot be in

data mode

or command

interrupt

mode. All requests

by the user

program

for

input data

from the

console must

be

made

by a

pur-

then-get

operation

issued to the

console.

o The PF9 key

on the

console keyboard

must

oe

pressed

to tell the CCP

to expect

a program

requesr.

o CCP

prompts

ENTER

PGM

NAME.

. Before

entering

the program

name,

the

pF12 kev

must

be

pressed.

o The

program

name

(and

data, if applicable)

must

be

entered.

o The ENTER key must be

pressed.

Closing

and

Opening

Disk

Files

Under

CCp

This

facility

allows the

system

operator

to logically

close

a

disk f

ile in

order to:

. Make

the f ile

unavailable

to CCP

programs

by inhibiting

program

requests

that require

the

file.

o Merge

added records

with existing

records

of add f iles

for subsequent

retrieval

or updating

by CCP

programs

or

by the other

partition,

then re-open

the disk file.

The

OPEN or

CLOSE request

is

entered

as a

program

request

from

the

system

operator's

console.

For

information

on

how

to use

OPEN

and

CLOSE,

see

the IBM

System/3

Model

lS

Communications

Control Program

System

Operator,s

Guide,

GC21

7619.

Closing

and

Opening

Disk

Files

From

a

Batch

partition

(Program

Number

5704-SC2

Onlyl

The

$CCPCO

utility

allows

the

system

operator

to logically

close

a

main

data

area

disk

file

fronr

a batch

partition

in

order

to:

. Make

the

f

ile

unavailable

to

CCP

programs

by inhibiting

program

requests

that require

that

file.

o Merge

added

records

with

existing

records

of update f

iles.

. Perform

f

ile

maintenance

such

as enlarging,

reorganizing,

or

deleting.

This f

ile

can

then

be reopened

to

continue

processing

in

CCP.

The

utility

($CCPCO)

is entered

by the

system

operator

from

an available

batch

partition.

For

information

on

how

to use

$CCPCO see the IBM System/3 MocJet

lS Communications

Control Program

System

Operator's

Guide,

GC21-7619.

SHUTTING

DOWN

CCP

When

it is time

for

the

system

operator

to stop the

CCp,

he issues

the

command.

SHUTDOWN.

The

shutdown

command

allows

all

programs

that

are currently

running

under

the

CCP

to continue

until

they

terminate

themselves.

Following

a shutdown

command,

the CCp

informs

the user

program,

via

a

return

code,

that

the

system

operaror

wants

the

program

to terminate

as

soon as

possible.

Each

user

program

executing

at that

time is

responsible

for recogniz-

ing

the

return

code

and

terminating.

Once

shutdown has

started,

only

commands

issued

by the

system

operator

are

accepted. No

new

program

requests

are

accepted.

However,

programs

currently

being

executed

or

queued

for

execution run

until

they

terminate.

Also

task

chaining

sequences

run until

completed.

The

system

operator

can

shut down

the

CCP without

allowing

all

programs

to continue

to completion

by issuing

a cancel

command (see

Cancel

a User Program

or the CCp).

The

CCP will

not

go

to

end

of

job

until

all

executing pro-

grams

have

gone

to end

of job

or have

been

canceled.

lf operating

under control of 5704-SC2,

the system

operator

can enter

a delay

time

with the

SHUTDOWN

commano.

When

a delay

time is entered

with the shutdown request,

the

terminal

operators

online

are

informed

that

shutdown

is

pending,

but actual

shutdown

does not begin

until

the

delay

time

has

elapsed.

SYSTEM

OPERATOR MESSAGES

The system

operator

can receive

messages from several

sources

while

monitoring the

CCP operation.

Some

of the

messages

require a response

(see

IBM System/3 Communi-

cations Control Program Messages

Manual

, GC21-5170).

CCP Responses

One

type of message

the system

operator

can receive

is

a

CCP response

to a

command

he has issued

(that

inquires

about

or modifies

the

status

of the CCP). These

responses

can be either

confirmations

from the CCP

that it has

carried

out a command or error messages

when the CCP

encounters

an error

in the

command. These

messages

contain

the

identification of the task that issued

the messaoe.

Messages

from Terminal Operators

The system

operator can

also receive

messages

sent by a

terminal

operator

using

the message

command. These

mes-

sages are

accompanied

by the reference

lD of the

terminal

that issued

the message.

These

messages

might ask

for the

system

operator

to return a message. lf a response

is

required,

the system

operator also issues

a message

command,

accompanied

by the symbolic

name

or CCP

reference

identif

ication

of the terminal

that is to recerve

the message.

Messages

from User Programs

The system

operator can

also

receive

messages

from user

programs. To respond

to a message

from a user

program,

the system operator

enters

the task identification given

in

the output message

and the appropriate

text.

When

a user

program

goes

to EOJ,

(end

of job)

all

messages

that the user

program

has written to the system consote

are

removed from the screen. This might cause

the message

to

disappear

from the screen before

the system

operator

notices

it or is

finished

with it. In

this

case, the

system

operator can refer

to the history file or a log

to review

all

the messages.

System

Operator

Control of the CCP 1

g

PLANNING AND THE SYSTEM

OPERATOR o System resources

used by the

program.

This

should

list

the files

used by the program,

the

terminals

used,

how

The

CCP system operator requires

a deeper understanding the terminals

are used,

and what names

the

program

uses

of the system

than the operator of a

batch

system.

The for the

terminals. The main

storage requirement

of the

operator must make

decisions alone and in a variety

of program

and its

typical

operating

time should

also

be

situations.

Many

of these decisions require

a

thorough given.

understanding

of the

CCP operation. The system

operator

can

display

and

modify the current status of the

CCP, and o Does

the

program

require

one or more

file

statements?

must

thoroughly understand

the effect

of actions

at the

console

on the

CCP and on the information

processing o What kind

of input

does

the program

expect-will input

systern

as a whole. data

be required

at the

same

time the

program

request

is made?

The system

operator

should be involved

as early

as

possible

in

planning

for installation

of the

CCP. Before

operating . Are

there

any

special considerations?

ls

the

use

of the

the system,

the system

operator

should become familiar program

restricted

in any way? Are there potential

with: problems

involved

in

suspending

or canceling

the

pro-

gram

before it has finished

its run?

. The

functions

of the

application

programs

in the

system.

a ls

the

program

a sort

program?

lf so, will it prevent

. The

{iles

used

by each

program. other

programs

from using

the

files

for a

long while?

o The configuration of the system. o What task

chain

sequences are defined

and what re-

sources

are

required for successful

execution of the

a The current status of the systL'm. entire

sequence?

' The

current

system

assignments' ln

addition

to.program

definitions,

the

system

operator

needs

other

information

about the

system. He

should have

To keep

the communicatron-based

system running

smoothly a copy

of the

current

CCP

assignments with information

when

the

system

operator

is

absent.

a backup

system about

the

terminals

attached

to the

system, the lines

operator

should

be

trained.

This

might

be the

system available

on the system,

the

files

available,

and

the programs

manager

or one

of the terminal

operators

or programmers. used under

the

CCP.

OPERATING

AIDS

The system

operator

also needs

current system information

like:

The

system

operator must

have

certain

current information o What

is the

current

password (or

other

securitv

informa-

about the

system

available

at all times. This

includes

such tion.

if the installation

has its

own security

procedures)?

things

as

descriptions

of CCP

programs

and

current system

assignments. a What are

the current data mode

escape

characters f

or

the system?

A program

description

sheet

for each

application

program

should include

at least

the following

information: . ls

there

a particular

schedule

of work to be completed?

. Syrnbolic

name

of the

program.

o Function

of the

program

(including

how it affects

the

files

it uses).

20

The

communications

control

program

aids

the

programmer

in

two

primary

ways:

o By relieving

him

of many

programming

concerns

inherent

in

an event-driven

system,

it lets

him

concentrate

on

ap_

plication

programs

that

do

the

processing

he requires.

. lt permits

him

to

write

application programs

that include

communications

input/output

in

a

high-level

ranguage.

Programs

that

run

under

the

communication

control

pro-

gram

can

be written

in

any

of four

ilanguages:

. RPG

II

o coBol

O FORTRAN

IV

o Basic

Assembler

By writing

in RPG

ll,

COBOL,

or FORTRAN,

tne

pro.

grammer

can

avoid

the strict

rules

required

when

using

Basic

Assembler

language.

In whatever

language

he

writes,

the

programmer

can ignore

the problems

that

arise from his

program

contending

with

others for system

resources.

Those

problems

are manageo

by the

CCP. The

programmer

is

assured

that

all

required

resources

are

available

to his

prograrn

each

time it is exe-

cuted. lf necessary,

the

CCP

defers

the

execution

of his

program

until

those

resources

are

available.

lf his

program

shares

access

to a disk

data file

with another

executing

pro_

gram,

the

CCP

and DSM

manage

the

contention. lt also

prevents

the two programs

causing

a wrong record update

tirrough

conf

licting reads

and

writes.

Programs

that execute

under

the

CCp

are written mucn

the

same

as

programs

in the

same

language

for a

system

witlrout

telecommunications.

That is,

the

statements

used

to process

data

and the

handling

of data files

are

identical.

Chapter

4. CCP

Services

for the

Application

programmer

The

standard

disk

data management

metirods

are supported

by the

control

program.

Only two elements

are likelv

to

differ

significantly:

o The overall

logic

of the

program.

o The means

of communicating

with terminals

or with the

syslem

operator.

Except for RPG

ll, the high-level

languages

do not offer

any

statements for accomplishing

terminal

input/output. Ter-

minals

cannot

be treated

as

data f

iles. Furthermore,

the

MLTA IOCS,

BSCA

IOCS,

and BSCC tOCS

do not permit

access

to their facilities

directly from a

high-level

progtam-

ming

language.

The

communications

control

program

incorporates

MLTA IOCS,

BSCC IOCS,

andlor

BSCA tOCS

and

offers

the

application

programmer

a

method

of usinq

these IOCS

facilities

to interact

with terminals.

The

application

program

indicates

terminal

actions to the

CCP by o,re

of the

following

statements:

o In

COBOL

or FORTRAN-call

statement

o In RPG ll-exit statement,

or

a special

file

o In Basic Assembler-a

supplied macro

instructiorr

Each

of these

statements

is

accornpanied

by parameters

to

indicate the specifics for the operator. See IBM System/3

Communications Control Program Programmer's Reference

Manual, GC21 7579.

Most

communication

by programs

running

under

the

CCP

is with the requesting

terminal. But the

ability

also

exists

to address other

terminals.

The

user chooses

a

natne

ro

address

a terminal in

the program.

This name

normally

applies

to one

particular

terminal. However,

if a

certarn

terminal

becomes

unavailable

during

a

run

of the

CCP,

the

system

operator

carr

reassign

the name

to another

terminal.

Any program

addressing

a terminal

by the reassigned

name

addresses

the new

terminal. For

the most

part,

the

applica-

tion program

need not be

concerned

with the type

of ter-

minal

with which it is

comrnunicatinq.

CCP

Services lor the Application

Programmer 21

An application

program

communicates

with the

system

operator

by addressirrC

the

systenr

operator,s

console

as

anolher

terrninal"

A name

(CONSOL)

is

always

used

tr

arJdress

the console.

The

only operations

available

here

ar rfl

o \tVrite

a message.

o \ltiritt:

a

message

ar-id wait for a

reply.

e r\r"cept

tnput

data

(only

data

entered

with a

program

request

commandi.

FAI]II-ITIES

OFFERED

BY THE

CCP

'the

CCP

performs

lhe

complex

control

program

services

that ntake

the

communications-based

system

easy

ro use

{or terminal

operators,

application

programmers,

and

the

systrlm

operator.

Tlre

CCP

performs

three

types

of control

program

services:

tl [ir:rnmi:nications

management

o f:ile

management

o Frro,;ram

management

Conrrnunications

Management

fli.lF'

communications

management

includes

all

services

re-

lati:rl

to requests

trom user

pror3rams

and CCp prograrns

for

terrninal

l/O. The

CCP does

not

actually

perform

the

phys-

ical

llO, bltt performs

services

for the

requester

that

simpli-

fy rhrer

use

of rhe MLTA IOCS,

MLMp BSCA

IOCS,

and

BSC:t.1.

iOCS

routirles

that

perfc,rm

the

physical

l/O. Among

ttr€

c{rrnmunications

management

services

performed

by the

CCF

are:

tr I-erminal monitoring

and

selection.

Euffer nranagement.

5\rnrbolir:

terrninal

naming.

L.rire

schetluling^

s lll;it,r

corJe translation.

-[errninal

testirrg.

f-ltfrer

services

that allow

the

application

programmer

to

bt,

larqely

independent

of differences

between

individual

ti-.1rnillals.

Terminal

Monitoring and Selection. Terminals

that are

designated

as

command termrnals during

CCP asiignrnerrt

are monitored

for commands

by CCP communications

management. For

multipoint lines,

the user specilies a

polling

list

during CCP assignment

(see

inciex enrnes:

BSCALINE statement and

MLTALINE srare/l)enr).

This

list

gives

the order in which the terminals

on a

lrne

are

to be

polled

(interrogated)

for data

and

commands

when

none

of the

terminals on the

line

are busv.

For BSCA

switched

lines, the user

can

speofy

a list

ot valrcl

switched

line identification

characters.

When

a connection

is established

to a

terminal

on

the line, the

identification

characters

of the

terminal

are

validated

aqainst the list.

Communications

managernent

also monitors

program

selected

terminals for input

and selects

them

for output.

Selection is

the

specific addressing

of a terminal

by com,

munications

management

to transmit

output data

to the

termina l.

(See

index entry terminal types for additional information

about command

terminals

and

program-selected

terminals.)

Symbolic Terminal

Naming: CCP

communications

manage"

ment

allows

application

programs

to refer

to terminals

by

six-character

symbolic names.

This

allows t,re

application

program

to be independent

of the

specif ic terminal

among

a

group

of like

terminals

(a!l

are 274O Model

1

;

all are

3270;...)with which

it is

communicating.

Communica-

tions management

associates the

symbolic name

with the

physical

address

of the terminal based

on the entries irr

an

internal

table.

This

table

is filled

in during

CCP

assignment

(see

index entry: TERMNAME statementl

. The actual

terminal

assigned

to a symbolic name

can be changed

by

the

system

operator during

the

running

of the

system

(see

irrdex entry: assign

a symbolic terminal narne to a terminal\

To change

the name

of a

command terminal,

the

terminal

operator must

also enter

a command

(see

index

entrv:

name commandl .

Communications Service Requests: The CCP provides a

subroutine

to application

programs

written in RPG

ll,

COBOL,

and

FORTRAN lV. These

programs

call this sub-

routine whenever

they

require

a communications

service

This

communications

service subroutine

puts

the usL'r's

request

into a standard format {independent

of the language

of the request)

that can be interpreted

by the CCP. See

Wri ti n

g C om m u n icat i ons P

rogram s-

..,

After encoding

the information

for a communications

service request,

CCP

communicaticlns

management

calls

the

IOCS routine

to perform

the

physical

l/O. The

CCp

schedules

l/O

operations,

determining

which

request

to

honor

chaining

the

parameter

lists

provided

by

the

various

requesters.

Data

Code

Translation:

CCP communications

managemer.

translates

the transmission

line data

code to the

internal

EBCDIC

code required for System/3

processing

and vice

versa.

However,

the user

can specify

that the translation

should

not be made

(see

index

entrv: translationl

.

Buffer Management'

In

addition

to the line

buffers

for

each

communications

line,

CCP maintains

and manages

a common

main

storage

TP

(teleprocessing)

buffer

(hold)

area.

This

aids

in

carrying

out

TP operations

requested

by both user

programs

and system

tasks.

CCP communica-

tions management

reserves

and releases

portions

of this

buffer

area

for input

and output

data. Because the

buffers

are allocated

on

an

as-required

basis,

a

program

can be

temporarily

suspended

if sufficient

main

storage

is

not

immediately

available

to satisfy

an

l/O request

to a ter-

minal.

The

program

is resumed

when

sufficient

main

stor-

age

becomes

available.

The

size of this

TP buffer

area

is

specified

by

the user

during

the

assignment run.

The

user

also

can change

the

size

of this

area

during CCP startup.

Online Terminal

Testing:

With CCP

communications

management,

the

terminal

operator

or system

operator

can initiate

MLTA,

BSCA,

and BSCC

online

terminal

testing.

(See

index

entryi start

and stop

online

terminal

test.) Results

from

the MLTA

online

test

appear

at

the terminal

for

the

terminal

operator

to analyze.

BSC

online

test results

can

appear

at

the

terminal

(depending

on

the terminal

type)

and

are also logged

on the

system

output

device

or in

the

system

history

area for the

system

operator

to analyze.

Note: The

system operator

can initiate

a BSC

online

test

only

to another

processing

unit

or

to the BSCC

attachment

(wrap

test).

File

Management

CCP file management

includes

all control

functions

pro-

vided

by

the

CCP related

to disk

and unit record files.

CCP

file

management

(DSM

with Program

Number

5704-SC2)

handles

the

scheduling

problems

rr..rhen

two or more

con-

currently-executing

programs

are trying to access

the

same

physical

file. In

addition, CCP file management

protects

data in

this

file

from

errors

that

could result from

conflict-

ing

operations

by contending

programs.

Opening

and

Closing Files: CCP begins its f

ile

managemenr

function

during

CCP

startup

(see

index

entry..

startup)

when

all

f

iles

available

to potential programs

are

opened.

The

CCP

retains

suff icient f

ile information

in main

storage;

there-

fore,

when a user

program

requests

the

f

ile,

minimum

time

is required

to perform

open

operations for the

program.

When

the requesting

program

is

finished

with

the

f

iles,

they

are closed by

CCP

file

management.

ln

reality,

they

are

not

finally

closed

(VTOC

updated) until

CCP initiates

shut-

down,

the system operator

enters a close request

using the

CCP

close

program

($CCPCL)

or the

system operator

speci-

fies

a KSORT

parameter

on the

PROGRAM

statement.

From

a batch

partition

the

system operator may

clo5e a

main

data area disk

f

ile with utility

($CCPCO).

The

operator

can

then

perform

file

maintenance

such as sort, delete,

enlarge,

and reorganize

without requiring

CCP

to shutdown.

This

f

ile may

then be

reopened

to continue

processing

in

CCP.

CCP

Services

for the Application Programmer 23

Sharing Access

to Disk

Files.' When

two or more

user

tasks

are executing

concurrently,

they

can share data files.

Shar-

ing

of data f iles is

managed

by CCP f

ile management.

(DSM

handles

file

sharing under Program

Number

5704-SC2.)

Some tasks can

share files

while

others

cannot, depending

on how

they

process

the file. The

general

rules for file

sharing

are explained

in

the

following

chart:

Method

of Processing Type of Sharing

Allowed

Program

Management

The

CCP

program

management

functions

include:

verifying

terminal

operator

requests for programs,

loading

programs,

allocating system resources

to

programs,

initiating

program

operation, deallocating system resources,

purging

programs

from

the

system,

maintaining

a

record

of the

number

of

requests for each

program,

task

chaining.

and setting

the

priority

of tasks.

Program

Bequests:

When a terminal

operator or the system

operator

requests

execution, the

CCP verifies

that the re-

quested

program

was defined

to the system

during assign-

ment

(see

index

entry: program

statementl

. lf the

pro-

gram

was defined,

main storage is

allocated for

the

requested

program.

lf

suff icient

contiguous

main storage

is

not

available,

the request is rejected

unless

the

requesting

terminal is

in

/O

status.

In this case,

the

program

is

placed

on a wait

queue

until main

storage space becomes

avail-

able. When

the

space is available,

the request

is

sent to

allocation.

Allocationlnitiation/Termination: When

a

pending pro.

gram

request reaches

allocation,

the

CCP

attempts to

allocate system

resources

to the

program

based on the

description of the

program

given

during the

CCP assignmerrt

stage. The CCP allocates system

resources

and

initiates

program

execution

when

all

the

required

resources

(mairr

storage space, disk and

unit record devices, and terminalsl

are available and

f

ile usage

requirements

can be

met. lf

a

program

requires

several

resources but some

are

not

available, the

resources that are available are

not

bound to

that

program

until all are available.

Unit

record

devices are allocated to only

one

program

at a

time

if this

was

specif ically

requested during

assignment

(see

index entry'.

program

statementl.

The

printer

can

be shared

by multiple

programs

if explicitly

permitted

by

a

program

statement.

Disk

f

iles

can

be shared if the

pro-

cessing

required

by the

programs

does not

preclude

sharing

(see

index

entry sharing

access to disk filesl.

When a

program

completes

processing,

the

CCP

releases

the

resources used by the

program

and

makes main storage

available

for

another

program.

Ordered indexed

load:

consecutive

output load;

consecutive

add

Unordered

indexed

load

Indexed

sequential

add

(lSAl;

indexed

sequential update

and

add

(ISUA)

All other methods

Serial sharing.'

the using

task

must

complete

before

another

task

can use

the

file.

Ordered

indexed

loading,

if used.

must

be the

first

access

of the

file

ancl

can

be done only

once

per

run

of CCP

Serial sharing.' file can

be

shared

only

by

programs

do-

ing

unordered

indexed

load.

Records

can be added,

using

one

of these methods.

only

once

per

run

of CCP

(unless

the file

is closed

and

re-

opened

by the

system oper-

ator). While

the

adding

pro-

gram

is in

progress.

sharing

is

not allowed.

After

the

add-

ing

program

is

completed,

normal

sharing of

the

file

is

allowed. Also, no

other in-

dexed

adds can

precede

ISA

or ISUA

(unless

the

file

is

closed

and

re-opened

by the

system

operator). However,

if a subsequent

program

accesses the newly

added

records,

it must

be coded

as

an indexed random

add

pro-

gram

even though

it does not

add

records.

Concurrent sharing is

allowed.

Managing Physical

and

Symbolic Files: CCP

file manage-

ment is

also

responsible

for

associating the

proper

physical

file

with a symbolic

file. This is

rlone

when

the rerminal

operator

enters a file specification

command

prior

to

the program

request.

(See

index

entryt filespecification

command for

a description

of symbolic

files.)

24

Program-Reque$ts

Count: lf this option is

selected

during

generation,

CCP

program

management

accumutates

a

record

of the number

of times

each

program

is

requested.

(Not

all

program

requests

cause

the

program

request

count

to be incremented.

The

exceptions

include

requests

for an

already

active

MRT

program

and

certain rejected

requests.l

However,

running

the assignment program

to update

or

delete

an

active

assignment

set

causes

program

counts

to be

lost.

Also,

the

count

in

$CCpFILE

is

updated

during

CCp

shutdown.

The

count

can

be

printed

and/or

reset

to 0 by

running

the

assignment

list

program

(see

index

entry:

assignment

Iist programl

.

Task

Chaining

(Program

Number

S704-SC2

only): When

a CCP

program

is ready

to request

initiation

of another

CCP

program,

the

requesting program

must

have

a chain

task

request

using

the

communications

service

subroutines.

The

requested

task

is

then

handled

by

the

CCp

program

request

function

and

is

executed

when

all required

resources

are

available.

Task

Priority: The

priority of user

tasks

under

CCp

is

handled

according

to the

program

type. A never-ending

program

(NEP)

is

given

the highest priority,

a multiple

requester program

(MRT)

is

given

the

ity,

and

a single

requesting

program (SRT)

rsss;yss

16.

lowest priority. Program

Number

5704-SC2

provides

for

selection

of a low

priority

on the

Assignment

PROGRAM

statement.

An NEP

with

this low

priority

has

a

priority

lower

than

NEPs

of normal

priority

but

higher

than

MRTs

or

SRTs.

An

SRT

or

MRT

with

low

priority

receives

a

priority

lower

than

SRTs

of normal

priority. The

estab-

lished

order

of

priority

is

as follows:

Highest

Lowest

NEP

MRT

SRT

MRT

or

SRT

normal

priority

low

priority

normal

priority

normal

priority

- low

priority

CCP

Services

for the Application Programmer 25

This

chapter

introduces

you

to the

factors

you

must

con-

sider

in designing

a

communications-based

information

processing

system

using

the

System/3 Model

1S

and the

CCP. For

more

information,

refer

to IBM

System/3

Co,m_

munications

Control Program

System

Design

Guide,

GC21

5165. You

should

regard

the

CCp

and the

communi-

cations

system

as a means

to an end,

the end

being increased

accuracy

and

faster

flow

of information,

greater

eff icierrcy

in

the

organization,

and

increased

volume

of work. During

the

preinstallation

activity,

define

the

overall

objectives

of

the

communications

system,

def

ine

the requirements

of

all

departments

that

will use

the system,

and

produce

a

detailed

plan

for

preinstallation

and

installation

activity.

You

should

plan

applications,

use

of

terminals,

data files,

programs,

and equipment

needs

before

installation

of tlre

CCP

to speed

the

installation

of the

CCp

and reduce

errors.

Publications

referred

to in

this chapter

and elsewhere

ii.r

this

manual

should

not

be

considered

a

complete

biblio-

graphy

for

designing

a communications-based

system.

Many

publications

are

available

to describe

in

detail

the

design factors

summarized

in this

chapter.

IBM

systems

engineers

and marketing

representatives

can help

obtain

these

publications

and

can

also assist

in

arranging

educa-

tion

classes

concerning

System/3

communications

system

design.

Although

marry

publications

currently

available

are for

larger

systems

and applications

(such

as airlines

reservations

systems),

the

basic

types

of applications

and

techniques

of data

communication

also

apply to

System/3

with the

ccP.

APPLICATIONS

The basic element

in

any

system

design

process

is

deter-

mining

what

the

applications

of

the

system will

be.

yor,r

probably

have

already

determined

that

you

need

to proc-

ess information

more

accurately

and efficiently.

For

ex-

ample.

perhaps

the

flow

of information

and the

processing

required

to perform

weekly

payroll

for a

growing

number

of employees

in

scattered

locations,

performing

different

jobs

has

become

inefficient.

An information

bottleneck

has

developed

in

the

central

payroll

office.

A network

of

Chapter 5. Designing

Your Communications-Based

System

terminals

communicating

the

payroll

information

to the

central

processor

in the

payroll

office

eliminates

tne

bottleneck. To do this, payroll data is sent

as

soon

as

it is

available,

and

processed

immediately.

Payroll

inquiries

from the remote locations

can

also be processed

immedi-

ately.

Assume

payroll

is identif

ied

as an application

for your com-

munications-based

system. The next step is

to determine

what related

applications

can be performed

by your sysrem.

Perhaps

you have

a need for more immediate

processing

of

personnel

information, which is closely related

to the pay-

roll information. Sorts on information

in

the

files

may

be

required.

Information

in the

personnel

files

maintained

by

the

central

processor

can

also be

made

available to inquiries

from the remote

terminals. Perhaps

you can use the produc-

tion totals for individuals

in the

separate work areas

in

pro-

duction accounting.

TERMINALS

When

you have

identif

ied

a

major

application

and

you can determine

preliminary

locations

for

terminals. Perhaps

you locate

separate terminals

in a

manu-

facturing

area,

an assembly area,

a

warehouse,

area, a ship-

ping

and receiving

area, a sales

office, and the central busi-

ness

off

ice. When

you have determined

the

preliminary

locations,

you can consider the

other

possible

uses

for the

terminal in each location. In the manufacturing

and assem-

bly areas,

perhaps

you have

a

need for parts

control; in the

warehouse

area

you may have

a need for inventory manage-

ment; in

the shipping

and receiving area,

a

need for a ship-

ping

order

and invoice

processing;

in the

sales off

ice,

a

need for purchase

order and service order processing

and

sales analysis; in the

central office.

accounts

receivable,

billing, and

general

accounting.

The

possibilities

for applications in any kind

of organization

are many. A terminal in

one

location

can serve more than

one application.

Desrgning YourCommunications-BesedSystem 27

In

choosing

terminals

for different

locations

and uses,

you

should consider

thc

lollowing:

. ls

the terminal

to be shared

by operators

with different

requirements?

lf so, the termirral

type must

be compati-

ble

yvith

all

requirements.

o ls

a

heavy

workload

expectedl'

li so,

perhaps

more

than one terrminal

is required

al the location

or a

faster

line

speed is required

(line

types

are

described in

IBM

General lnforntation Binary Synchronous Communi-

cations, GA27 3004).

. Will

a clisplay-type

terminal

(lBM 3270) or a typewriter

terminal

be needed

(all

terminals

on the

same multipoint

iine must

be

compatible)i

. Will

a

high

volume

of activity

of the

terminal

justify

special

features

on terminals,

such as the

buffer-receive

feature

on the

lBM2740,

Model

2?

/Vote.'

Uses for terminals

in

a communications-based

system

(data

entry,

inquiry, inquiry-with-update)

are

defined

and

described briefly in the General lnformation Manual,

GC21-7578.

DATA FILES

When

applications of the

communications-based

system

are deternrined,

plans

must

be macle for the data

f iles

to

support those applications. The biasic decisions

to be made

initially

are:

o What separale

f

iles

are

needed?

. How should the

f

iles

be organized

to best satisfy the

different uses to which

the

f

iles will be

put!'

o lf indexed fiiles

are

beirrg used,

are

records

to be added

during a

CC['runi Are

the added records

to be accessed

during the

same CCP

runl

. Will

tasks and batch

partitions

need

to share

f iles?

Many applications

require

separate

files

contairrrng

currenr

information,

arrd

to-date information. In

a

payroll

applica,

tion, for

example,

the

following

files

might

be

required:

o A f

ile of

daily inf ormation

(hours

worked,

production).

o A f

ile containing information

about each employee

and

the to-date inf

ormatron.

Other

ways of differentiating between

f iles

could

be:

. Separate

files

for separate branches of an

organization,

such as schools in a school svstem.

o Separate

files for different

products.

After you identif

y the

separate

f iles

you need,

you must

find the

best

file

organization

for each

file

according to its

use. For

example,

f

iles that are normally used

for online

processing

might be subject to batch

processing

when

the

f iles

are loaded. Analyzing the percentage

of online

pro-

cessing time

versus

the percentage

of batch

processing

time

aids in

selecting the

file

organization that is most efficient

overall.

For

example, if processing

is

90%

online and

10%

batch,

your choice

of f

ile organization should be

weighted

toward direct

organization-

That is,

you can

devise an

eff

icient method

of deriving relative

record numbers.

(See

IBM System/3 Disk Concepts and Planning Guide, GC21-

757 1,

f

or a

description

of direct

f

iles). lf processing

is 50%

online and 50%

batch,

indexed organization

is the best

compromise organization.

Perhaps

you will use the

f ile

for

online

processing

in

one

partition

and

for batch

processing

in the other

partition. In that case,

either

direct or indexed

organization

might

apply, since both can be

processed

either randomly or consecutively.

lf you are

going

to do a sort

operation on input files

(Pro-

gram

Number

5704-SC2

only),

you may want to specify

NOSHR in

the

FILES

parameter (of

the

PROGRAM

statement) at assignment

time to control the output of the

sort. However, by specifying

NOSHR

you prevent

access

to

the

input files

while sort

is running. Therefore, it is

impor-

tant

to plan

when

to perform your

sort

operations.

The IBM System/3 Disk Concepts and Planning Guide,

GC21-1571, contains

information that will

aid

you

in

choosing a

file

organization

and

planning

disk

files.

PROGRAMS

You must

also

plan

how your applications

are to be

per-

formed

by your communications

programs.

Programs

should be single

function

if possible.

You can debug

your

program

easier

and use

less main storage. lt also

provides

space for adding

new

applications.

You should consider the

provision

of the

CCP

for physical

files

and symbolic

files in

applications

that involve

process-

ing diff erent f iles

on different

runs

(see

index entry:

sym-

bolic filesl

. lf programs

are

to access

records added to an

indexed

f

ile during the

CCP

run,

the programs

must

be

written to include the

add

f

unction

(refer

to index

entry:

program assignment statententl even when the program

will r-rot

add anv records.

28

For

information

on program

structure

and overrays,

see

the following publications:

o IBM System/3 Overlay Linkage Editor Reference

Ma:tual, GC21-7561

. IBM System/3 Sabset American National Standard

COBOL Reference Manual. GC2A-6452

. IBM System/3 RpG ll Reference

Manual, SC2l-7504

. IBM System/3 FORTRAN lV Reference Martual.

sc28-6874

. IBM System/3 Basic

Assembler program Reference

Manual

. SC21

-7509

When

designing

a

program

to run

under the

CCp,

you must

consider

the

program's

use of terminals.

Should the pro-

gram

service

a request

from one

terminal

at a

time or from

multiple

terminals?

Should terminals

be selected

by the

program

or should individual

terminals

request

the program

when they need

it? Perhaps

there

are

security

considera-

tions that indicate

the program

should

have

a single

requester

or a limited

number

or requesters.

How long will the

pro-

gram

remain

in

main

storage?

ls it a brief inquiry

applica-

tion or a

more

time-consuming,

data-entry

applicationZ

lf

the

program

will be used frequently,

perhaps

multiple

requesters

should

be allowed,

or perhaps

the program

should be written

as

a

never-ending

program.

Program

de-

sign

under the CCP

is

described

in I

BM System

/3 Communi-

cations Control Program Programmer's Reference Manual .

GC21-7579.

lf you run

applications

under

the

CCp

concurrenfly,

you

must

plan

the

program

so they run

smoothly

togetner,

especially

during

peak

times. programs

running

togetner

cannot,

for example,

each

require

dedicated

use

of unit

record

devices.

Perhaps

you should

run batch programs

only

during

particular

times

of the

day. you must

plan

peak

processing

times

so that

system

resources

are

available

to the

programs

that

must execute.

You should

test individual

programs

and

the entire

svstem

in

advance

to ensure

that

all applications

execute

as

planned

and

to evaluate

the

performance

of the

system

against its

planned

performance.

lf the

system

does

not perform

as

planned,

review

your program

structures,

file

organizations,

and

placement

of files

and

programs

on disk.

ESTABLISH

ING THE SYSTEM

The

CCP is designed

to suit

diverse

data

processing

environ-

ments

involving

online

applications.

Telecommunications

line

and

terminal

configurations,

and

the

conf igurations

of

central

processors

that host

them, vary

greatly

among

the

users

of the

CCP. Different

users have

different

require-

ments

in functional

and

performance

characteristics

of

their

telecommunications

subsystem.

The

CCp.

as distri-

buted, consists

of a set of instructions

that can

be tailored

to the needs

of the user.

The

CCP is established

in

the

following

stages:

. Generation

o Assignment

a Operational

system

startup

Generation

of the CCP

by the user

is

the first

stage

in

tailor-

ing

the system

to his

needs.

This

stage requires

tne process_

ing

of a

number

of generatron

control

statements.

a series

of

link-edits,

and

a set

of disk

utility operations.

During

this

stage

a set

of the CCP

system is

created

that defines

the

functions

that

this version

of the

CCp can

perform.

Once

generated,

the CCP

is

still not bound

to a specific set

of user

programs,

data

files,

or terminal

assignments.

The

set of programs.

data files,

and terminals

of any

CCp sys-

tem will probably

vary

throughout

the life

of that version

of the

CCP,

even

as the required

f

unctional

abilities

remain

constant. Therefore,

a procedure

separate from generation.

called

assignment

is

provided

for the establishment

and

modif

ication

of these

def initions.

Like

generation,

the assignment

stage is

performed

as a

normal

System/3

operation: its

specific function

is

the

creation,

modification,

or replacement

of a set

of control

tables

used

by the

CCP to manipulate

user

programs,

f

iles,

and terminal

resources.

But urrlike

the

generation

process,

which

tends

to be

lengthy.

the

assignment

stage is rather

brief, requiring

only the reading,

interpretation,

and en-

coding

of straightforward

user

specifications,

and

the

writing

of these

to a

disk

data

f

ile.

Designing YourCommunications-BasedSystem 29

The

assignment stage identif ies

programs,

terminals,

disk Startup

f

iles, unit record

devices,

and symbolic terminal names

ro

be used in

a

particular

execution

set

for the CCP. As with In order to initiate the CCP startup

routine,

the operator

generation,

the

programs

necessary

to perform

the

assign- enters the

following

OCL cards

from the

reader:

ment stage

are supplied as

part

of the distributed

CCP

modules. The user

can

run the

assignment stage many // LOAD $CCP,unit

times in

the development

of his

telecommunications

appli-

cations.

For

example, he

might have.just

developed

a new ll FILE (one

file

statement

is required

for each

physical

application

program

that

he

now wishes

to incorporare ' user

file

accessed

during

the current CCP

run)

under the CCP. He

might

also

havr.'different

assignment

sets that can be used

for different runs

of the execution of

the

CCP.

// RUN

After he performs

the generation

and

assignment

stages, the

user is ready

to operate his CCP system. The system

oper- After the CCP

startup routine is loaded into main storage,

ator

now loads

the CCP, specifying the assignment

set the it asks

questions

of the

system

operator that allow

him to

svstem will execute

under. Certail additional elements for exercise several options. See

index entry'. initiating the

only the

current

run of the

CCP can be specified during CCP

for

a

description

of the

questions.

operati o na I system sta

rt up.

Startup

performs

the

following initialization

functions:

OPERATING THE SYSTEM o Loads the resident

CCP

After the

CCP

is tailored to the

user's

environment

and o Updates

various tables

from the current assignment set

needs

by the

generation

and assignment stages. it can be in

$CCPFILE.

put into

operation.

The

CCP

operational

stage

occurs in

three

parts: startup, operation,

and shutdown. o Builds

control tables

in main storage

for files

and

termrnars.

User

application programs

must be

placed

in an

object

library

before CCP startup. lf a

new

program

is

being added. o Verifies that adequate

main storage

is

available.

it must be placed

in the object library and the CCP

assign-

ment build

program

must

be

run

to update the

assignment 1l Allocates and

opens

the

f

iles that

will be

used during

file ($CCPFILE)

before CCP startup. the

current

run.

lf you are running under Program Number 5704-SC2, . Locates

all user

programs

that might be requested during

you can specify

EXECFIND-YES

{in

the PROGRAM

state- the current run (unless

EXECFIND-YES

is

specified

in

ment) in

the assignment set. With this

specified and the

PROGRAM

statement

at the assignment

time).

with cataloging to an

active

library allowed, a

new

or up-

dated

program

can be

found during

CCP execution without a Finds sort modules

if they

are

required.

an intervening shutdown.

o Loads

resident modules as

required.

Also, under Program Number 57O4-5C2, the program

CCPFMT

can

be

run

at CCP execution

time to find formats o Opens communications

adapters and

lines.

which have been added or updated since

startup, and to

update the DFFSFDT value

(in

the

PROGRAM

assignment Startup

issues

diagnostic

messages if the

system

require-

statement).

For

assignment statement

considerations,

see ments

for startup are

not met. if the user

entered invalid

// PROGRAM statement

in the As:signment

Stage

section instructions,

or if it cannot complete

its initialization

for

of this

manual. some

other reason.

30

Operation

During

its operation,

the

CCP manages

the environment

in

which

telecommunications

application

programs

run

and

provides

services upon

which

they

can

call. The manage-

ment

f

unctions

of the

CCP

are

of three

types: communica

tions

management,

file

management,

and

program

manage-

meirt.

Shutdown

CCP

shutdown is

initiated

by command

from the

system

operator (see

index entry'. shutdown command). After the

shutdown command. the CCP

goes

to EOJ

when programs

running

under

CCP

f

inish executing.

The

following

specif

ic operations

are

performed

at CCp

shutdown:

a Executing

programs

are notified

to go

to end

of job.

. Communication

lines

and adapters

are closed.

o Disk

data files

are closed.

lf the

program

request

count

option was

selected

during

generation,

the number

of requests

for each

user

pro-

gram

during

the

CCP run

are added

to the

count. For Program

Number

5704-SC2,

if

the set

has

been changed

since

startup,

the addition

will

not be

done.

a The

CCP sends

a closing

message

to the system

operaror.

o The CCP exits

to the

system end-of

-job

routine.

UPDATING

THE

SYSTEM

In time,

the

uses of the communications

system

might

change.

You must

plan

for possible

updating

and

addition-

al tailoring

of the

system

as

you gain

experience

with the

system.

You should make

allowance,

for example,

for the

turnpike

effect,

a phenomenon

observed

after

the first

modern

superhighways

were

planned

and built. Use

of the

new highways

was

greater

than

anticipated,

because

drivers

tended

to stop using

the

old routes

in favor

of the new

high

way. Overall

traffic

flow increased

beyond

expectations

because

of the

convenient

new highway. The turnpike

effect

has

been

observed

in

sys-

tems

and is

a

factor

to consider

in planning

for a System/3

communication-based

system.

TOTAL EOUIPMENT

NEEDS

When

you have

considered all

factors-applications,

use of

terminals,

data

f

iles.

programs,

and

provisions

for system

updating-you carr make decisions

concerning the total

equipment

needs

o{ your organization:

a What

are the

total

storage requirements

of the

super-

visor,

the

CCP, the

TP buffer,

and the

user

area?

. How much

disk

storage

is needed

and of what

type?

How much

space is needed for libraries,

how much for

f iles?

(For

detailed

storage estimates

f

or

the CCp.

see

Appendix F, Storage Estimates.l

Wlrat terminals

are neededl

What

communications

equipment

and

lines

are needed?

What is

the total

costi

When

can deliveries

be

madel

What unit record

devices

are

needed

and how fast

should

they

bel

. Are you spooling the unit record

device input

or output?

I nformation

concerning

teleprocessing equ

ipment

charac-

teristics

communications

concepts, common

carriers,

net-

work design,

and

other

useful

inforrnation

is contained

in

the following

publications:

IBM Data

Communications Primer.

C20-1668

I BM System/360 I

ntroduction to Teleprocessing,

c30-2007

DISK

SYSTEM

MANAGEMENT

(DSM)

CONSIDERATIONS

The

CCP operates in conjunction with DSM

and

uses

DSM

facilities

whenever

possible,

including the l/O supervisor

for disk and

unit record l/O devices.

Certain

constraints are

placed

on

the

existing

DSM

program-

ming support.

1. CCP user

programs

use

additional DSM task

control

blocks

in the DSM nucleus, which must

be requested

via CCPUT keyword

of DSM

generation.

2. Programs

nclt link-edited

for CCP cannot

run in

the

CCP

partition.

a

Designing

YourCommunications-BasedSvstem

31

aFor

program

partitions:

o CCP

can be used in only one

partition

at a time.

However,

when

CCP is

running

in

one

partition,

user

programs

not controlled by CCP can run con-

currentlV

in the other

partition(s).

o CCP

should

run in the highest

priority partition

to maximize

throughput.

o A program

running

in the non-CCP

partition

can

use

a

teleprocessing

adapter

(MLTA or BSCA)

concurrently

with the execution

of CCP. However,

this

adapter must not be

supported

by the

same

assignment

set currently used

by CCP. MLTA and

BSCC

are

mutually

exclusive features.

Multivolume

disk

data files

are not supported

by

Program

Number

5704-SC1.

Random

access to

multivolume

f iles is

supported

by Program

Number

5704,5C2.

To reduce

degradation

from disk access

contention,

consider

including more

than one

disk drive

in the

CCP

configuration of the system.

Spooling while running

CCP allows

multiple

CCP

user

programs

to use

spooled

devices.

Also, programs

are

not limited by the device speeds. lSee

Spooling

Considerations later in this chapter.)

For

disk

files:

All disk

f

iles

to be

processed

during a

CCP

run

must

be online, and

specif

ied

in

OCL

f

ile state-

ments

following

the OCL load

statement to load

CCP.

All disk

f

iles are normally

opened at CCP

startup

and closed at CCP shutdown. Because of this, no

indexed-f

ile, key-sort

occurs until

CCP shutdown.

Programs

wishing

to access

all

records

added

to an

indexed

f

ile should

include indexed

add data

management in

their

programs.

However, f

iles

can

be closed

and a key sort performed

via the system

operator

file

closing

facility

($CCPCL).

A file

may

also be closed through

the

use

of the KSORT

param-

eter on the PROGRAM

statement, assuming no

other

program

is

using the

file

at

end

of lob.

Records

added

prior

to the close

request

are

merged with existing records

and

available to all

programs

when

the

file

is reopened

($CCPOP).

(Program

Number 5704-SC2 only.) Main data

area

disk

f

iles may

also be closed

for f

ile

maintenance

from a

batch

partition

using a system operator

utility ($CCPCO).

$CCPCO

executes in a non-

CCP

partition.

After $CCPCO

has

been successf ully

executed,

the operator

can use other programs

to

enlarge

or sort the

file

and delete

records from the

file. $CCPCO

can then be

used

to reopen

the

file

for CCP

access.

. CCP

permits

concurrently

running

programs

to

update

the same

file

or to do indexed add

to the

f

ile. To do this,

CCP

(5704-SC1)

or the system

(5704-SC2)

protects

the block

of sectors contain-

ing

the

record

until

the

program

releases

the block

of sectors. The

block is released when

a never-

ending

program,

multiple requesting

terminal.

writes

the block to the disk, reads

another block,

goes

to end of job,

or issues an

accept

input

operation. However, a

possible

lock-out

condition

can occur

if the

program

never

releases

the block.

A unit record

device

cannot

be shared bV concurrent

programs

running under CCP. (Exception: the

printer

can be shared by concurrent

programs

run-

ning under CCP

if specified

by the assignment

con-

trol statement.) When a program

ends,

the device

is available to another

program.

Checkpoint/restart is

not supported

under

CCP, but

can be

used in the non-CCP

partition.

Inquiry (rollout/rollin)

is not supported under

CCP

but can be used in the

non-CCP

partition (for

Pro-

gram

Number

5704-SC1 only).

For

user

programs:

o User

programs

must be

def ined to CCP within an

assignment

set.

o Teleprocessing

must

be done

tirrough CCP.

. A terminal

requesting

a

program

is tied to that

program

until released by the program.

o User

programs

with names

beginning with $ are

not permitted

to run under CCP except

$CCPDD,

$CCPCL

and

$CCPOP

which

are

noncancel

programs.

. To use a console,

you must use CONSOL as

the

terminal

name.

4.

8.

tr

o.

9.

10.

11.

a

32

. Programs

cannot

be largc,r

than

32K including

DFF PAS;

for program

Number

5704-SC2,

the

32K does

not include

external

buffers

or any

area

for memory

resident

overlavs.

(32K is

the

maximum

size

because

each

program

can

onty

address

64K;

each

must

address

16K

of suoer-

visor,

and

16K

of CCp

leaving

32K for the user.)

o The

program

size

rs rounded

to a multiple

of 2K

with

a

minimum

of 4K.

. CCP

does

not support

tape

units.

. CCP

does

not support user

programs

accessing

the

3284 attached

to the processing

unit.

. User

programs

must

be link-edited

at

32K

(X'8000'). This

allows

faster program

load

and

reduces

the

load

on the DSM

transient

area.

. For Program

Number S7O4-5C2,

disk DTFs

(define

the

files),

lOBs

(input/output

blocks).

and internal

buffers

cannot

be

located

at an

address greater

than

logical

X.DFFF..

'12. The

assembler

user

cannot:

. Use a special

allocate.

o Do

a read

using

system

input.

. Write

to the

scheduler

work area

(SWA).

o Write

to the volume

table

of contents

(VTOC).

o Execute

privileged

instructions.

Spooling

Considerations

(program

Number 5704-SCl

l

For printing: lf the printer is

allocated

to only one subtask

and

a

//PRINTER control

statement

with a DEFER-NO

parameter

was

specified

at CCp

startup,

the spooling

routirres

close

the

spool

print

file

when

the

CCp

CLOSE

for a subtask

is

called.

For punching: lf DEFER-NO is

specified

on the // PUNCH

control statement.

each

subtask

which closes

a punch device

causes

the

spooling

routines

to close

the

spool

punch

file

at

the

same

time.

The

jobname

and

stepname

on

the

print and

punch

spool

queues

are the

same

as

the

partition

jobname

and

stepname.

Spooling

Considerations

(Program

Number 5704-SC2)

For reading: Only a nonspooled

partition can

read

data

directly

from the card

device

that is

the spool

reader.

To

read

data, the spool reader

must be

terminated and data

must

be ready

in

the card input

device.

A nonspooled partition

can indirectly

read

data f

rom the

spool

reader.

lf the

card input

device

for a spooled

parti_

tion is

not the spool reader,

requests

for data

from the spool

reader

by a

program

generate

an'Sp UT NR,message

(input

device

is

spool

reader)

. lf a

zero

option is

selected,

the

spooling routines

use as input

data the

job stream

of the

first

job on

the

reader

queue

scheduled for execution

in the

partition

requesting

data

from the

spool reader.

lf the

data includes

a

job card,

the

job card

will be

used

as

the

first

card

of data.

lf the card

input

device for a

partition

is

the

spool reader,

then the data

for a program

must be put behind tne

// RUN statement

of the

program

using

the data,

as

shown

in

the

following

example.

// SAMPLE

JOB

//CATL PROG,Fl

// RUN

data

(end

of data)

(end

of job)

For printing: lf the printer is

allocated

to only one CCp

task,

the spooling

routines

close

the

spool

print

file

at

the

completion

of that task, unless

CLOSE-NO

is

specified

on

the

PRINTER

OCL statement

at or before

CCp startuo.

For punching.' Each

task

that closes

a punch device

causes

the

spooling

routines

to close

the spool

punch

file

at the

same

time unless

CLOSE-NO

was

specified

on the pUNCH

OCL statement

before

or during startup.

When

the output on a spool print or punch queue

is

pro-

duced

by a

program

running

under

CCp, the

terminal

name

is used

as the jobname,

and the stepname

is

generated

by

taking

the

program

name

and

appending

a sequence

number

The sequence

number starts

at 0l and is

increased

by one

for each

jobstep

placed

on the queue. After g9 is used.

the

sequence

number is reset

to 00. A separate

counter is used

for the

print and

punch

queues.

Designing Your Communications-based

System 33

lf

a CLOSE-NO

parameter

is

specified

on

a

pRINTER

OCL

statement

at or before

CCP startup,

the

partition

jobname

and stepname

are used

to identify

tasks on

the

spool

queue.

lf

the 1403 is

the system log

device for

the

CCP

partition,

the

partition

jobname

and stepname

are

used

to identify

CCP

tasks on

the

print

queue;

after a

CCP task

causes

tne

spooling routines

to close the

printer,

terminal

name

and

program

name

are used

to identify

a CCP step

on the

queue.

lf

the

printer

is allocated

to more

than

one task

at a time,

the identification

on the

print

queue

will

be that of

the

first

task

to put

data

on the

queue.

CCP

Trace

TYPE-CCP

is

an

optional feature

of the DSM

system

trace.

which

provides

a log

of system

activity. This

trace

can

be useful

in

determining

the cause

of problems.

The

DSM

interrupt

trace

is a separately

loaded

program

that

must

be

executed

before

CCP

startup. Trace

TypE-CCp

is

invoked

by specifying

CCP

on

the

TYPE

parameter

of

the

trace

control

statement.

For

Program

Number

5704-SC2

only,

and

OCC

loadable

CCP trace

function

may

be

initiated

after

CCP

startup

and before

CCp shutdown.

This

CCP trace

facility

provides

trace

entries formatteo

like

those

created

by the

DSM

trace

(gTRACE)

with TypE-

CCP

and

TYPE-ALL.

For

further

information

on the CCp

trace facility,

see

the l8M System/3

Model I

S Communica-

tions Control Program

Data

Areas

and Diagnostic Aids,

SY21-0040.

For

a detailed

description

of

the

operation

and

trace table

formats,

see

the appropriate

data areas

and

diagnostic

aids or

program

logic

manual

listed

under

Related Publications in the

Preface.

MULTIPLE

PARTITION

CONSI

DERATIONS

The

CCP is

partially

inhibited in its

processing

when

the

non-CCP

partition(s)

is using

the DSM

system

transient

area

and the CCP

partition

also requires

the transient

area.

This

would most

commonly happen

wlren

the system input

trans.

ient

(SYSIN)

is in

the transient

area

for

the other

partition

(for

example,

for

job

initiation).

CCP

is

also

partially

in-

hibited

when the

screen is

used

for

the

display command

and the display is not immediatelv

canceled

or

when PF10

(OCC)

is keyed

and there is a

delay in entering

data.

The DSM

transient area is also

used when terminatinq

a

CCP user

program.

Sharing

Files

Between Partitions

For Program

Number

5704-SC1, CCP update

and add

files

can be

accessed and updated

by the non-CCP

partition if no

CCP

programs

are

currently updating

or adding to the same

file. However,

records

added to a f ile

by CCP

programs

cannot be accessed

by the other partition until shutdown,

or until the file is

closed by the system operator (see

the

index entry: Disk File Close/Open Facilityl .

For Program

Number 5704-SC2,

enhanced

f ile sharing is

ava ilable.

3270 DISPLAY

FORMAT FACILITY (DFF)

CONSIDERATIONS

The 3270 display

format

facility

(DFF) is

a

facility

of the

CCP

that is selected separately

during

the CCP

generation.

The

facility

allows

programs

written in RPG

ll, COBOL,

FORTRAN lV, and

Basic

Assembler

to control the display

or printer format for the 3270 information display system.

The DFF makes

it possible

to control the display or

printer format and perform operations

involving data

fields

in

the

format directly

from the application

program,

similar to performing

the

operation with any other

terminal supported under the CCP.

The

DFF is composed

of

: the

display

format

generator

routine

$CCPDF

(DFGR

for single or multiple format

builds),

the printer

format

generator

routine

$CCPPF

(PFGR

for

single

or

multiple

format

builds),

the

display

format

test

routine

$CCPDT

(DFTR),

and the

display

format

control

routine

(DFCR).

The DFGR or

PFGR,

which is

executed

prior to the CCP startup,

processes

special

DFF specif ications.

builds

display or printer

formats,

and stores the formats in an object library. The

DFTR is a stand-alone

program

executed

prior

to CCP

startup

which displays DFF formats

on a

3270 Information

Display System

for testing

the screen

or printer

layout.

DFTR cannot

be

used if BSCC is the onlv communications

interface in the system. The DFCR processes

requests for

DFF services

issued by application

programs

running under

the CCP.

The DFGR or PFGR

operates in either

program

partition

but not concurrently in both program partitions.

The

main

storage

required for execution

is

always

18K. The

DFGR

or PFGR

cannot

place

new formats

in

a

library if

the other

partition

is

using temporary

entries,

or doing

library

functions

on the same

pack.

lf DFGR

or

PFGR

is

running

with CCP

executing

in the other

partition,

the

format being

processed

by DFGR or PFGR

cannot be

placed

on the

pack

CCP was loaded

from. lf attempted,

an EO Fb PP halt

occurs.

tBM

3271

IBM

3274

rBM

3275

tBM

3276

rBM

3277

rBM

3278

rBM

3284

rBM

3284

rBM

3286

IBM

3287

tBM

3288

rBM

3289

Control

unit

Control

unit

Display

station

Control

unit

display

stat I on

Display

station

Display

station

Pri

nter

Pri

nter

Pri

nter

Pri

nter

Line

printer

Line

printer

For

Program

Number

5704-5C2,

the

SCp

SYSGEN

prompt

for

catalog

protection

determines

whether

the

format

being

processed

by DFGR

or PFGR

can

be

placed

on the

pack

CCP was

loaded from.

For

additional

discussion

of the DFGR

and DFCR,

see IBM

System

/3 Commun

ications Control Program

programmer's

Reference

Manual

, GC21

-7579.

Components

within

the

3270

system

that

are

supported

are

as

follows:

Component Function Model Numbers

Model

1

and Model

2

Model

1Ct

Model

1

and

Model

2

Model

2r

Model

1

and

Model

2

Model

2r

Model

1 and

Model

2

Model

32

Model

1 and

Model

2

Model

1

and Model

2

Model

2

Model

1

and Model

2r

Special

features

of the 3270 system

supported

are: tne

selector

pen,

the

audible

alarm,

and the

operator

identifi_

cation

card reader.

The 3270 is

supported

as a remote

attachment

to the

System/3

Model

15. Communications

between

the

Sys-

tem/3

and

the

3270

are maintained

using

the binary

syn-

chronous

communications

multipoint

data link mode of

operation. All operations

that can

be

performed

with the

327O

in the remote

operation

are supported

except for the

read-type

and

general

poll

commands.

polling

sequences

are used for remote

read

operations.

Using the

Same Terminal with DFF and Non-DFF Programs

A terminal

attributes

set

(defined

at

assignment

time

with

the

TERMATTR

assignment

control statement)

is in

effect when

a terminal

is

communicating with user's

pro-

gram

under the

CCP. There

are a number

of ways

of con-

trolling

the

attributes

set of a terminal:

1. The

first

TERMATTR

statement

assigned to a ter-

minal in

an assignment

set

is

the default

attributes

set

of a terminal. When

neither

of the

following

two

methods

are

used,

this is the

attributes

set in effect

for

the terminal.

The attributes

set of a required

terminal

can be

specified

for the

terminal during its

attachment

to

the

program

via the

program

assignment

control

statement,

TERMS

parameter.

When

the terminal

is

no

longer

attached to the

program

because

of an

end-of-job

condition

or a

release

terminal

operation

lsee

IBM System/3 Communications

Control Program

Programmer's

Reference

Manual

, GC21-7579),

the

default

attributes

set

is in effect.

The

attributes set

can be specified

for the terminal

during its

attachment

to the

program

via

the Acquire

Terminal

operation

lsee

IBM System/3 Communica-

tions Control Program Programmer's Reference

Manual

, GC21-75791

with the

set terminal

attribute

modifier.

A terminal

already attached

to a

program

with one

attributes

set can be re-acquired

to change

the

attributes

set. The

default

attributes set

is

in

effect

when

the terminal is no

longer

attached to the

program.

2.

3.

t

ln

3270

compatability

mode

only.

'3284 Model

3 attaches

to 3275 display

station

onlv

Designing Your Communications-Based

System 35

TERMI

NAL

SECU

RITY

CONSI

DERATIONS

lf you

have

no

terminal

security feature

built into

your

system,

each

command

terminal

can issue

program

requests

and other

commands

to the system

after

the

sign-on

com-

mand

has

been entered

at that

terminal.

lf you

are

concerned

with security

of access to the system,

you

can include

a

password

feature

in

the

CCP at

genera-

tion (see

index

entries:

$ESEC-terminal

sign-an

security

and

sysfem

assignment

control statementl.

In

a

system with password

protection,

no requests

are

accepted from

a terminal

until

its

operator

presents

the

current

password

and the

CCP verifies

it. Once an

operator

signs

on with

the

password.

he

can make

any number

of

requests

without

repeating

it. lf the

operator is

not

always

at his

terminal, he

can sign

off the

terminal

anytime

he

leaves

it. Once he has

signed

off. the

CCP requires

any

further

use of

the terminalto

be accompanied

by

the

pass-

word. Thus if other,

possibly

unauthorized,

persons

gain

access

to that terminal,

they

cannot

gain

access

to the

system.

The valid

password

for

the

current

run

is established

in

an

assignment

set,

but can

be

changed

by the

system

operaror

at startup

of the CCP

(see

Sfartup Procedure

in the IBM

System/3 Model 15

Communications

Control program

System Operator's

Guide,

GC21-7619).

The

password

can

change

at startup

on every

run,

or can

be retained

for

days

or even

weeks.

In any case,

only

terminal

operarors

who know

the

password

are

permitted

access

to the

system.

lf the user wishes

to write

his

own terminal

sign-on

security

routines

rather

than

use the

CCP

password

facility,

there

are

stringent

requirements

his

routines

must

observe

re-

garding

the interface

with

the

CCP

(see

index

entry:

$ESFC

*term i na I sig n

-o

n sec

u rityl.

All

sign-on

attempts

are

logged

on

the console.

36

CCP

generation

is

the process

whereby

the user

selects

the

portions

of the distributed

CCP

that provides

the

capabilities

he

wants

in

his version

of the

CCP. Generation

is

the first

stage in creating

the CCP,

when

the user

establishes

its

maximum

capability. Further

selection

is

done

at

assiqn_

ment

time

and

at operational

startup.

The

user

describes

his

system

configuration

and the func-

tions he

wants

by a

series

of statements

consisting

of key-

words

with associated

values.

Some

of these

statements

describe

the system

conf

iguration

(main

storage

size,

terminal

and line

capability)

within which

the

CCp

operates.

Other

generation

statements

specify

the

capabilities

of the

CCP

and whether

the CCP

is

to have

certain

optional

features

such

as

password

sign-on

and

user

program-request

counts.

Cliapter

6. Generation

Stage

Generation

creates

and initializes

an

assignment

f

ile

($CCPFILE),

whose

contents-the

specifications

of an

actual

terminal

configuration,

disk

files

to

access, ano

programs

to use-are f

illed

in at

assignment

time.

Generation

Stage 37

PROCEDURE

FOR

GENERATION

The

key

step

for the

user

in

the

generation

procedure

is

to

describe

the kind

of CCP

required

by modifying

the

sample

generation

statements. In order

to modify the statements,

the user must

know certain

facts

about

the

system

and about

the

capabilities

of the

CCP he

or she wants

to generate.

These

facts

are determined

during

the CC[,

system

design.

Design

considerations

are

given

in Chapter

5, Designing

Your Com-

munication-Based

System. The following is

a checklist

of

the

facts

a user must

know before

performing

generation:

Generation Check list

During

generation,

the user chooses the features for his

system. In doing

this, the

user

should carefully check

each

generation

option

and specification to see

if the

system

requires it. As

a reminder, most features increase

the

size

of the control

program

which, in

turn, lessens

storage

space

for application

programs

to execute

(see

Appendix F.

Storage

E stimatesl .

Maximum

number

of terminals

olanned

Space to be

reserved

in $CCPFILE

($CCPDUMP

for 5704-SC2)

for dynamic main

storage

dumps

Main storage

size

of processing

unit

Disk

unit

and

pack

name

on which

the

pack

to contain

$CCPFILE

will be mounted

during

generation

Disk

unit and

pack

name

on which

the

pack

to contain

$CCPDUMP will be nrounted

during

generation (5704-SC2

only)

Number

of tracks

in

the CCP

dump file

($CCPDUMP)

to be

used for writing

the

trace tables

if CCP trace is

active

(5704-

SC2

only)

Beginning

track location

for

$CCPF

ILE

Number

of MLTA lines

to be

supported

Whether

or not MLTA input

and

output

will always be

translated

to and from EBCDIC

MLTA terminal devices

to be

supported

M LTA line

transmission

codes

BSC

lines,

line

features,

and BSC

control

logic

to be included

in CCP

support

BSC

line

transmission

codes

BSC

terminal

devices

to Lre

supported

BSC

interval

polling

ls

the

display

adapter to be supported

ls

serial

l/O channel

to be

supported

(5704

SC2

only)

Disk

unit on which

disk

system

management

resides

(F1

or R1)

Disk

unit onto which

CCP will be

generated

Disk

unit(s)

and

pack

name(s)

where

work

file

space

can be found

during

generation

Disk

unit on which

the distribution

CCp

Modules

reside

Whether

or not

the

data

mode

escape

feature

is to be used,

and if so

the

six

user-specified

rJata

mode escape

characters

ls

a

program

request

count

to be

kept

ls

display format

facllity

(DFF)

to be

su

pported

ts

program

request

under

format (pRUF)

to be supported

ls resident

accept

inFjrut

to be

supportecJ

ls

resident

open/close

to be

supported

ls resident

program

request

to be supported

(5704-SC2

only)

ls DFF moveout

to be

implemented

(5704-SC2

only)

ls Terminal

Name

Table

(TNT) moveout

to

be implemented

(5704-SC2

only)

ls 328X printer

busy facility

to be

supported

(5704

SC2

only)

Are information

mes:;ages

(S

type)

to De

sent

to CPUs

Programming

language(s)

to be supported

by CCP

Which

544413340

Di:sk

Storage

Drive(s)

you will use

to mount the

packs

during

generation

that

will later

be

used for pre-

paring

programs

to br:

run by CCP

What

type

of sign-on

security

will be

used.

if

any

Length

of your security

comparison

infor-

mation,

if you use

your own

sign-on

secu-

rity checking

routine

Arrticipated

number

of assignment

sets to

be

placed

into $CCPF:lLE

Maximum

number

of programs

and files

in

an

assignment

set

Following

are

two methods

for

doing

the

CCp

generation.

The first

method

uses

cards

as

the

primary

input

medium.

The

second

method

is

cardless-oriented.

This

method

uses

the

source

and

procedure

libraries

as

the

primary

input

medium.

The

basic

procedure

for the

card-oriented

CCp

generation

is:

1. A sample

control

statement

deck

is

punched

from

the

source

library

of

the

distribution

pack.

2. The

sample

deck

is

modified

by the

user

to his

speci_

fications

and

entered

as

input

to the next

step

of

generation.

3. A full job

stream

to accomplish

the

necessary

func-

tions

is

punched

for

the

user.

4. The

job

stream

is

used

to generate

your

version

of

the CCP,

and

the

CCp

assignment

f

ile

($CCpF

I LE)

is

ready

for

the user's

initial

assignment

run.

The

basic

procedure

for the

cardless-oriented

CCp

genera-

tion

is:

1. Source

and

procedure

members

are

printed

from

the

distribution

pack.

2. The

user

modif

ies

the

sample

procedures

using

the

$MAINT modify

function

for the

system

configura-

tion

as input

to the

of generation.

The

user

enters

the

CCP

specifications

to create

source

and

procedure

members

used

to generate

your

version

of the

CCP

and

the

CCp

assignment

file

($CCPF

ILE}.

The function of the generation

stage

of the CCp, regardless

of the method used,

is

to:

o Generate

modules

that require

modifying

at

the

source

level.

o Link-edit the generated

modules

and certain

other re_

locatable

modules. This is done

to create

three load

modules: two are

the resident

control program

during

CCP

operations,

the

other

initializes

$CCpFlLE.

o CopV

these

and

other

load

modules

to the

designated

CCP

production pack. The production pack is

the pack

from which

the CCP

is loaded

for execution.

The

CCp

production pack

can be

any pack

other than the distri_

bution pack. lt might

be

a

DSM

system

pack

and

might

also be

the current system

pack

during the CCp

generati

on.

o Copy

additional

selected relocatable

modules

to the

program

preparation

packs

(packs

that will be

used for

compilations

and linkage

edits

of user

written

applica-

tion

programs

that

will execute

under

the

CCp).

. Allocate

and

initialize

(but

not fully

enter

information

into)

the

CCP

assignment

file

(gCCpFlLE)

on

the

designated

pack.

The

generation

stage

assumes:

. That

the DSM

is

properly

generated

on

the

system

pack,

including

the appropriate

MLTA,

BSC,A,

and/or

BSCC

l/O macros

and subroutines.

MLTA: The

MLTA microcode

deck

(obtained

from

the

service

representative)

must

be loaded

into

the

object

library

under

the narne

$MLMC1 on the

system

pack.

The BSCC

Microcode

Deck

(obtained

from

the

service

representative)

must

be loaded

into

the

object

library

under

the name

ggBSYD

on the

system

pack.

The MLTA

error

statistics

file

(MLTERFIL)

must

oe

created

and initialized

on

the

system

pack.

To

initialize

MLTERFIL,

the MLTA

feature

provides

module

$$tUlf

t

in the object

library. The

OCL

statements

required

to

initialize

M

LTERFI

L are:

8SC: lf BSCA or BSCC

lines

are

used.

a file on the system

pack

for logging

control station

terminal statistics

must be

provided.

To initialize

MLTERFIL,

the

MLMp (multi-

line/multipoint)

feature

provides

module

$$BSFI

in

the

object

library. The

OCL

statements

required

to initialize

MLTERFIL

are:

lOne track is normally specified,

but for BSCC.

two tracKs musl

be

specified.

3.

Generation

Stage 39

l/ote; MLTERFIL need

be initialized

only once

to

accornmodate

BSCC,

BSCA,

and MLTA statistics. part

of MLTERFIL comprises

the BSCC/BSCA

terminal

log

area

and is used for logging

the control

station

terminal

statistics.

Another

part

of MLTERFIL is

used for logging

MLTA statistics

if MLTA is

present.

Do not initialize

the file twice if you use

both BSC

and MLTA.

a That during generation

the copy of the macro processor

($MPXDV

and

all its

subsequent

load

modules)

and

the

overlay linkage

editor

that

exists

on the

CCp

pack

are

used

during

the

CCP

generation.

o That an

appropriate

sized object library and source

library were

allocated

on the production pack

15444/3340 only). See index entry: disk storage

estimates for the CCP.

. That the object library on the production pack

was

reorganized

and no modules

were

deleted

since reorgani-

zation.

.

All the CCP modules

should be

contiguous

on

the production pack

after the CCP

generation. (The

CCP has no

control over

where DSM

can

place

modules

if modules

were deleted.)

o That if SIOC is to be

supported

by CCP, the

appropriate

SIOC l/O modules

must

be

on the

system

pack. Refer to IBM System/3 Model l5D Channel

Connected Systems Program Reference and Logic

Manual,

GC21-5199.

o That

$CCP

is not running

during

generation.

Notes:

1. The

printed

output resulting

from generation

must

be

saved

in

case of required maintenance

by IBM Field

Engineering

personnel.

This

paper

is

the only documen-

tation of the user's unique system and the precise

se-

quence

of events

during this

particular

CCP

generation.

2. The user

should consider

backup procedures

(of his

own

design)

in

case

the

CCP

distribution

pack

or a

generated

pack

are

inadvertently destroyed.

3. Generation

can

be accomplishecl on a System/3

Model

15

other than the

one

using the

CCP

in

teleprocessing.

Operational Procedures

For Generation

The CCP

is

distributed on a pack-separate

from the distri-

bution of the other components

of the System/3 Disk

System Management.

lf you are

generating

both the basic

DSM

and the CCP,

you must

generate

the basic DSM first,

following the procedures

described

in IBM System/3 Model

l5 System Generation Reference Manual

. GC21-7616.

To

generate

the

CCP,

you

must mount

the CCP

distribution

pack

on a unit

separate from the

system

pack.

You

must

have

performed

an

IPL

(initial

program

load) from

the

sys-

tem

pack

at some

Unlike the

generation

of

DSM,

you

can

direct

the output from

the CCP

generation

to more

than

one

pack.

The

output

consists

of:

o Those

modules

required for

the

assignment

stage

and for

executing

the operational

CCP. These

modures

are

directed

to the CCP

production

pack.

o The

subroutines

to be used

on compiling

and link

edit-

ing

application

programs

to be run

under

the

CCp

(macros

in

the

case

of Basic

Assembler

language

pro-

gramming).

These

subroutines

are directed

to one or

more

program

preparation

packs.

Each

of the

above

might

be

a different

pack,

or could

be

the same

pack.

You

specify

the disk

unit

on which

each

of these

packs

is mounted.

The

CCP

generation

procedure

is

dependent

upon

the

presence

of the macros

and

subroutines

for BSCA,

BSCC,

and/or MLTA

(as

appropriate for

the

terminal

devices

to

be supported)

on the IPL

pack.

Figure

3 outlines

the

procedure

for generating

the

CCp.

The

procedure

assumes

that disk

system

managernent

was

generated

and

disk

system

IPL

was

performed

previously.

At this

point

the

user must

decide

whether

to use

card-

oriented

CCP

generation

or cardless-oriented

CCp

genera-

tion. Six

steps for the

card-oriented generation

are:

Step 1 (User,

Card Oriented):

The

user enters from

the system input device

(the

console

or the card device)

statements of the following

form:

y'Vote.'

dsunit on the /l LOAD statement

is the unit on

which

the DSM

system

pack

resides. The

diunit in

the

// COPY

statement is

the unit on which the CCP

distribu

tion pack

is mounted.

40

card device

or console

SYSIN

// Compile

Added to

$CG

1

G3

i&

II LOAD $IVIAINT,

dsunit

// RUN

I/COPY FROM.

diun it,TO-PR

lNT,

LIBRARY-S,

NAM

E.$CG

1,ALL

// COPY

FROM-

diun

it,TO-PR

lNT,

L IB

RAR

Y.P,

NAME.$CG

1-ALL

// END

IICOPY

FROI\4,

diunit,

TO-PRTPCH,

LIBRAR

Y-S,NAfV]E-

$CGSMP

$MA

I NT

Prepare

$E macro

controt

statements,

either modify the

supplied

source

member,

SCG i

GM

or create

a new

source member

$MA

INT

SOURCE Prints

CCP

genera-

tron

instruction

and

procedures

$CG1.ALL

$MAINT I n

stru

ctt

on

s

Sample

CCP Genera.

tron statements

Generati

on

Print

and

punches

the

CCP generation

sample

deck

Instructrons

to use

OC L cards

Sample CCP

genera-

tion statements

Generation utility

User

modif ies

gener-

atron

procedures

for

his

system

configur-

ation

Call procedure

$CG1G1 Sou rce

Member

Conlrol

Statements

User removes

the

Instructtons

cards

and

modifies

the sample

deck to de-

ribe h

is

ver- MACROS

Feature

Writes required

con-

trol

statements

on

the

$SOURCE

workf

ile

Generation state-

ments In the modt-

fred

deck specify

the

facilities

of the

users

CCP.

MACROS

Fealure

Writes required

con-

trol Statements

and

directions

for pro

ceding

with the f

inal

generation

operalaons

on the

$SOURCE

workf ile

Contrcl

S

tat

em en ts

SYSIN-

-Card

From

Part

2(scc

1G3)

To next

page

Figure

3 (Part

1

of 3). CCp

Generation

procedure

(Card

and

Cardlessl

Generation Stage 41

From

($cG

1G4)

To

Part

1

($cG

1c5)

SYSIN $CCPSA

To next

page

$SOURCE

Workf

ile

o SCP

source

statements

. ocl

a Overlay

Linkage

Editor

Control

Statements

a Disk

Utility

Control

Statements

Generation

Utility

$cc I

PP

Prints

users

specif ica-

tions f rom

$SOURCE

workf ile

Print

the input to

Step

6 and refor-

mat

the

$SOURCE

workf ile

Print

and

Punch

the

input to Step

6 from

$SOUBCE

workfile

$MAINT

Card

deck

containing

control statements

irnd

directions

f

or the

final

CCP

generarion

|fperatton

Using

contents

of

$SOURCE workf ile

create

the source

and

procedure

members

for

Step

6

42

Figure

3 (Part

2 of 31. CCP

Generation

procedure

(Card

and Cardless)

From

tr

i----l

|

,,

""r,

I

usER I

I Spec'fied

I

i."*""I

l__l

\4acros

Feature, SCP

Generator

and Overlal

L

inkage Editor D

istribution

Establish

contents ot

Tne buurF I Ltr ano

generate

a Load

module ($CCl

BF) to

initialize the file $cc1

BF

lenerator and Overla'

-inkage Editor oducilon pac

Create

execution

resident

module

\

/

$cc4

SMAINT

)ther CCP

-oad module

Copy startup, execute

transrenlS,

asSrgnment

shutdown Load $cc429

ards )z

Macros Feature,

SCP

Generator and Over-

lay Linkage Editor

Create

empty user

security information

modu le

r

I

Program

Preparation

Pac ks

SMAINT

Copy Language

Support modules

_)

Main data

area

pack

$CCPDUMP

Yes

$CC

I

DP

Create and

initialize

$CCPDIJMP

Card

onenteo No

$MAINT

Punch and Prinl

set

($CGSET)

and

puncn

oump

pro-

grams

$MA

I NT File

pack

Pftnt Sample assign

ment set ($CGSST)

$CCPFI

LE

$cc1 BF

Create

i nitial

SCCPFI

LE

END

Figure 3 (Part 3 of 31. CCP

Generation Procedure

(Card and Cardlessl

Generation

Stage z+J

Step 2 (System, Card-Oriented):

The

system retrieves

$CGSMP

(CCP

sample

generation

deck)

from the source library

on the

CCP distribution

pack,

and

then

prints

and

punches

the entire

member.

The sections to the

information

printed

and

punched

are:

Insl.ructions

to the user

for modifying

the punched

cleck.

OCL to call the macro

processor,

followed

by sample

$E

generation

control

statements

to generate

a CCP

system.

One card is

provided

for each operand

of a

generation

control

statement. The

card

generally

contains

the default value,

and

provides

a

comment

indicating

alternative values

for the

operand.

OCL to call

the

CCP

generation

utility program

($CC1PP}.

2.

For Program

Number

57O4-5C2,

all

l/ FILE

carcts

punched

during generation

will

specify

SHARE-NO.

An

exampte

of the

printout

that

accompanies

the

sample

generatton

deck

is:

gCGSMP

+t*l*n+*********l$:t**a'l**t********t**'t+**+:tt**+***+:i*t****+******t*+**a**+

* JNPUT

TO CCP

GENERATION *

+****l*****:B****t**+***+***+*t***ir****t**t**t+t**t*****:r****t*******r****

*t

IB

a

,F

+

i

+

a

tl

*

t

a

t

a

*

+

*

'l

I

*

t

*

:}

*

+

:|

*

+

*

rt

*

t

*

a

+

*

:t

$

*

rl

*

$

+

*

THESE

CARDS.- AFTER

H

ILL 8E THE II(PUT

DISCARD

THE

LEADTNG

EEGTNNING

THROUGH

DISCARD

ALSO

THE

//

YOU

HAVE

I{ODIFIED

THEH

TO

YOUR

SPECIFTCATIONS

--

TO THE

FIRST

PASS

OF CCP

GENERAIION

CARDS

OF THTS

DECK,

FROM

THE

// COPY

CARD

AT THE

THE

CARD

THAT I.,IARKS

*** END

OF INSTRUCTIONS

***

CEND

CARD

-- THE

LAST

CARD

OF THE

DECK

YOU MUST I4AKE

THREE

K

TNDS

OF IIODIFICATIONS

TO THE

REI,IAINING

CARDS

-_

I. I N THOSE

CARDS

THAT

ARE

I.tARKED ++ IN COLUI,,INS

74_75. REPLACE

ANY $$ OR il( IN THE

CARD t.IITH

THE

IOENTIFICATIT]N

OF A DISK

UNIT

--

IS HITH THE

UNI

## hITH THE

UNI

LOCATFD

TON

I{HICH

YOUR

SYSTEM PACK

IS LOCATED

HH

I

CH ThE CCP

D ISTR

IEUT

ION PACK

I

S

2. REPLACE

CARD

NUMEER

00299 I.iITH

A CARD

PUNCHED

/1 IN COLUI{NS

I-2

3. HOCIFY

T}.8

GENERATION

CONTROL

STAT€HENTS

*- THOSE

CARDS

FOLLOHING

CARD

NUMBER

OO206

_ TO SPECIFY THE RECUIREI.IENTS

OF

THE

CCP

YOU

I{ISH

TO GENERATE

IF YOU

DO NOT

HTSH TO

USE THE

DISTR,IBUTION

PACK

FOR THE

REQUTRED

$SOURCE

FILEr SPECIFY

THE

L0CATION

0F THAT

FtLE 8y CHANGING

THE

UNIT

AND

PACK

PARAI,!ETER5

IN cARDs

oo2o4 AND

oO306

* I{HEN You HAVE

HADE

THESE

cHANoEs, pLAcE THE t4ootFIF0 0EcK IN THE *

t HOPPER

OF THE

SYSTEI.I

INPUT

DEVICE AND

BEGIN PASS

I OF

CCP

GENERATION

*

*-+

****** END

0F INSTRUCTIONS

*+'i**,F't**$+*,rr****** END

OF INSTRUCIIONS

*,r**,Br

t

* 00 lo0

00200

:*'I* PROCESS

SPECIF

TCAT

IONS FOR

THE

CCP

TO 8E GENERATED OO2O1

+

ll LIAD $t,t

pxDvr## oo2o2

++

00203

II FILE AAME-tSOURCE,RETAtN-T,UNTT-##,PACK-PIDOOI,TRACKS-2Or ++QQ2O4

/ I L0CAT

rON-386 00205

Generation Stage 45

// RUN $EFAC

ESCAPE-NO, -- ICCCCCCI

/ XIXXXXXXXXXXXXI

PGNCTIT-NO

, -- YES --

PRUF-NO, -- YES

--

FORNAT-NO, -- YES

-_

ACCEPT-NO, -- YES

--

RESOPN-NO, -- YES

--

BSYPRT-NO, -- YES

--

I'IOVTNT-NO, -. YES

--

t4ovDFF-No, -- YES __

RESREQ-NO, -- YEs

--

5I0C-N0, -- YES

-_

OPPRUF-YES

, -- NO

--

CPUI'ISG-NO, _- YES

--

L0t^tcAS-No, -- PFl _ PFLZ

__

TTASK-NO -- YEs --

SEPLG

LANG- , _- COBOL

,/ RPGI I / FORTRAN / AS5EI.1

--

PPUNIT- -- Rl / FL / R2

/ F2 --

$EsEC

SECURE-NO, -- CCP / USER

--

LUSI-0 -- 1 - 4095 IF SECURE-USER

--

SEFIL

5ET5-1, -- 2 - 25 --

PR0G5-10, -- 1 - 999

--

DFILES-s, -- 1 - L92

--

TER|'15-1

, __ 2 _ 25q __

DUNPS-I, -- ? - 99 --

c0RE-96K

, -- L?BK/

16 0Kll 92K/22qK/?55K/38qK/5L?K

FLUNIT- , _- R1 / FL / R2 / F2 --

TRKLOC- , -- VALID TRACK

NUI.IBER

/ O}1ITTED

--

FLPACK- , -- NAI,IE

OF PACK

--

DPTRAC-6 -- 0 - 1000

--

$EI'1LA

LINES- , -- 0 - 8 --

XLATE-YES -- NO

--

SEI1LD

TYPE- , -- SEE SYSTEI,I REFERENCE

I,IANUAL

--

Xi'1CODE- -- 5EE SYSTET,l REFERENCE

IlANUAL

--

SEBSCBSCA-, --0-2--

DIAL-NO

, -- YES

--

PP-NO _ YES

--

HP-N0, __ YEs __

c5-N0

, -- YES

--

GETI'ISG-NO, -- YES _-

ITB-I.IO, -- YES

--

RECSEP-1E, -- TI,JO

HEX DIGITS --

ASC

I I

-NO, -- YES

--

EBCDIC-YES, -- N0

--

XPRNCY-NO

, -- YES

--

RESPOL-NO, -- YEs

--

AUToRS-N0

, -- YES

*-

INTPOL-NO, -_ YES

--

DA-NO

, .- YES

-.

PORT-NO -- YES

--

SEBSD

TYPE- -- SEE

5Y5TEI'1 REFERENCE

I'IANUAL

--

$EGEN

DSUNIT-$$, -- Rl / FI --

CCUNIT- , -- RI / FL / R2

/ F2 --

I,IKUNIT-

, -. UNIT,/ 'UNIT,UNIT,UNIT'

--

I.,IKPACK- , -- PACK

/ I

PACK,

PACK, PACK

I --

DiUNIT-SS, -- Rt / FI / R2

/ F2 --

r'1INRES*NO, -. YES.-

DPPACK- , -- PACK

NAME

--

DPUNIT- _- UI{IT

--

X/X -- REPLACE

THIS CARD

I.IITH

/X IN COLUI'INS T-2 --

XXX PRINT

RESULTS

OF

CCP

GENERATION

PASS

1

x

XXX IF NO

ERRORS,

PUNCH

INPUT

TO CCP

GENERATION

PA55 2

ta

// LOAD 9CC1PP,S*

/ / F

I L E N A il E

- 9 5 O U

R C E

, R

E T A I N

- S

, U N

I T

- * S

, P A C

K

- P

I D O O 1 , 5 H A R E

- N O

// RUN

I For Program

Number

5704-SC2

'$ECSC

and

$ECSD

are

available

onry.

to give

BSCC

support

(BSCA

lines

3 and 4) for Program

Number 57O4-SC2

only

00206

X FACOO

X FACOI

X FACOZ

X FACOS

X FACO4

X FACO5

X FACO6

X FACOT

X FACOS

X FACO

9

X FACIO

X FAC12

X FAC13

X FAC14

FACl5

X PLGOO

PLGOl

X SECOO

SECOI

X FILOO

X FI

L O

1

X FILO2

X FILOS

X FILO4

X FILO5

X FILO6

X FILOT

X FI

L 08

FILO9

x t'11A00

MLAOl

X NLDOO

NLDOl

x 85C00

X BSCO

l

X B5CO2

X BSCOS

X BSCO4

X BSCO5

X BSCO6

X BSCOT

x 85C08

x 85C09

X BSCTO

X BSCIl

x B5C12

X BSC13

x Bsc14

BSC15

BSDOO

x ++GEt{00

X GENOl

X GENOz

X GENO3

X ++GENO4

X GENO5

X GENO6

GENOT

00299

00300

00301

00302

00303

00304

++00305

++00106

00307

Step 3 (User, Card-Oriented):

The user

modifies

the sample

deck to reflect

the require-

ments

of his

system.

Specifically

the

user

can

modifv:

o The

unit parameter

on the LOAD $MpXDV, unit card

to

indicate

the

unit on

which

the

CCp

distribution

oack

resides.

o The

unit and

pack parameters

on the

//FILE of the

macro processor

OCL statements

to indicate

the unit

and

pack

on

which

the

work f

ile

$SOURCE

should

be

allocated

during

step

4.

o The

CCP

$E

generation

control

statements

and

their

operands

to indicate

the requirements

of the svstem.

r The *

l* card

following the $E control statements.

This

card is replaced

with a /* card.

o The unit parameter

on the l/ LOAD $CC1pp, unit card

to indicate

the

unit containing

the

CCp

distribution

pack ($CC1PP

is

the

CCp

supplied generation

utititv).

o The unit and

pack parameters

on the // FILE statement

generation

utility OCL statements

to indicate

the

unit

and

pack

where

the

work file

$SOURCE

is

to be

allo_

cated

during

step 4. The

$SOURCE

work file

will be

scratched

during

step

6 and

the

space

will be

available

for other

work files.

The

user

should

nrodify

the

punched

control

starements,

without inserting

any

additional

cards

in

the

deo<,

except

where

he

requires

more

than

one:

o $EPLG

statement-additional

$EpLG statements,

with

both the LANG and

ppUNlT parameters

present,

are

re-

quired

if more

than

one programming

language

rs

supported.

Note: lf any errors

are detected

in the user.s

specifications,

the utility program

$CC1PP

prints

them,

but ooes

not

permit the user

to proceed

to the next step

until those

errors

are corrected,

and the macro

processor

step repeated.

The

modified

deck,

with the initial

instruction

caros

removed,

must

be

placed

in

the

system

input

device

for the

next generation

step.

Step 4 (System, Card-Oriented):

The

system

calls

the macro

processor

to analyze

and

expand

the

CCP

generation

$E control

statements.

The

process

creates

records

in

the file

$SOURCE. lf anv

errors

are

detected

in the

user's

specifications,

only diag-

nostic

messages

from the CCp

generation

are written to the

file. lf there

are

no

specification

errors,

the

CCp

generation

writes

to $SOURCE the recoros

necessary

to create

the

specified

version

of the CCp.

Step 5 (System, Card-Oriented):

The

program

$CClPP reads

the

work file,

$SOURCE,

and

prints

what

was

generated

to that f ile. lf there

are

specif

i-

cation

errors.

only the

user,s

original

statements

and

the

error diagnostic

messages

are

printed. In order to proceed

further, the user

must correct

those

errors

and perform the

macro processor

step

again.

lf there

are

no

errors,

the

user's

original

statemenrs

are

printed. Then

the records,

which

are input

for step

6 to

create

the user's

version

of the CCp,

are

printed and punched.

$EMLD statement-additional

$EMLD statements,

with

both the TYPE

and

XMCODE parameters

present,

are

required

if morr-'than

one

type

of MLTA terminal

is

supported.

$EBSD

statement-additional

$EUSD

statements,

with

the TYPE par.ameter

present,

are

required

if more than

one

type

of BSC

terminal

is

supported.

Generation

Stage 47

Step 6 (System,

Card-Oriented).' S. Creating

an

initialized

module,

$CC4Z9,

if

SECURE-USER

operand

was specified

in the

$ESEC

The

user

places

the

punched

output from

the

previous generation

control

statement,

later to contain

tne

step.

without modification,

into

the

system input

device, user's

security

information.

and

begirrs

the malor

step of

the CCP

generation.

During

thissteptheuser'sCCPiscreated.

Thesequenceforthis 6. Initializing$CCPFlLE,

latertobefilledwithuser

step is: specif

ications

by an assrgnment

run.

1. Creating

a load

module

that

contains

the

initial 7. Copying

the

subroutines

and macros

used

in the

contents

of

$CCPFILE and

the instruction

code to compilation

and link-editing

of application

programs

initialize

that file

($CC1BF). to

run

under

the CCp.

2. Source

generating

of $CC4#1,

$CC4#2,

$CC4VT, and g. punching

the following

cards:

link-editing

of the two modules

($CC4#1

and

$CC4*p)

that

make

up the

resident

control

program

for CCP o OCL and

sample

generation

control

statements

operatlon' for

an

assignment

build run,

necessary

to execute

the installation

verification

program.

3. Link-editing

BSC

and/or

MLTA

trace routines. o OCL

statements for installation

verification

oro-

4. Copying

supporting

load modules

for

the

operational gram.

stagd, including

startup

and

shutdown.

and

for

the

assignment

stage. o CGEND.

9. Initializing

$CCPDUMP

file

to be

used for

trace

and

storage

dumps

for

5704-SC2

only

(optional).

Note: For

Program

Number

5704-SC2 only,

step

6

follows

step

8.

The following

is

an

example

of

the sample

assignment

input:

iCGS

E

T

XXXXXXxSAITIPLE

ASSIGNNENT

AND

5AI',IPLE

sTART-UP DEcKXxXXXXXX)<XxxxxxxXxxxxX

x

XXXXXXXXXSAMPLE

ASSIGNI.IENT

SET XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

X

XXXXXFILL

IN UNIT

X

// LOAD

$CCPAS,

X

XXXXXFILL

IN PACK

AND

UNIT

x

// FILE NAI.1E-SCCPFILE,RETAIN-P,UNIT-,PACK-

X

XXXXXFJLL

IN PACK

AND

UNIT

x

// FILE NAI'IE-SCCPl,,l0RK,

RETAIN-S,

TRACKS-J,UNIT-

// RUN

x

,

PACK-

00010000

00020000

00050000

00040000

00050000

00060000

00070000

00060000

00090000

00100000

00110000

00120000

00130000

00140000

00150000

00160000

00170000

00180000

00190000

00200000

00210000

00220000

00250000

00240000

00250000

00260000

00270000

00260000

00290000

00300000

00110000

0 0

52 0

0

0 0

00550000

0 0 34 0 0 0

0

00550000

0 0 36 0 0 0 0

00370000

003E0000

00390000

00400000

00410000

00420000

00430000

00440000

00450000

00460000

00470000

00480000

00490000

00500000

00510000

00520000

00530000

00540000

00550000

00570000

005E0000

xxxxxxxxxTHE

F0LL0l^tING

STATENENTS

CAN

BE T,lODIFIED

F0R

y0UR

XXXXXXXXXCONFIGURATION

BUT

SOME

NUST

BE

KEPT TO

RUN CCPIVP. 5EE THE

xxxxxxxxxc0MNENTs

IN 'lHI5

DECK.

x

// SEf ID-A,ACTION-CREATE,

DFLTEXEC-YEs,ANYSPECs-NO

,/,/ S Y5

T EI'I I'1

I N U P

A

-

2

2 K, I'1 I N

T P

B U F

-

28 4

O,

x

PASSI..IORD-FECD,

C OI'1I,IA

N D

L

- 5 O, D F FPA CK- P

R O GR AI'I, P

GMR EQ L

- 1

5

// TERI'IATTR

ATTRID-l,TRANSLAT-NO,BLKL-512,DATAFORM-HESSAGE,

// VERIFYID-NO,

DFF32TOIYES

x

XXXXXXXXXTHIS

STNNT

TYPE

REQD FOR

CCPIVP(OR

I.lLTALINE

STIINT)

x

// BSCALINE

TYPE-CS,

LINENUI,l-l,POLLLIST-rOO,O1,

10, 1I

t

// BscATERll

TERr'1ID*00,TYPE-3277N2,ATTRID-1,col'ltlAND-YES,0FFAcTN-HoLD,

/ / A D D R C

H A

R

- x 6 0 6 0

4 0 4 0

x , p

0 L L c H

A R

- x 4 0 4 0 4 0 4 0

x

// BScATERl'|

TERI'IID-01,TYPE-32771'I2,ATTRID-1,cot'lNAND-YEs,0FFAcTN-H0LD,

/ / A D

D R C H A

R

- x 5 0 6 0

C 1 C

I x , p

0 L L c H

A R

- x

4 0

4

0 c 1 c 1

x

// BSCATERM

TERNID-1O,TYPE-3277N2,

ATTRID-I,COI,IIIAND-NO,

// ADDRCHAR-x616l4040x,p0LLcHAR-xC1C14040x

// BSCATERI,I

TERI'IID-1I,

TYPE_3277N2,

ATTRID-1,

CONNAND-NO,

ADDRCHAR-x6

16 1C1C1x,

p0L

LcHAR-xC1C1C1C1x

x

// TERI',1NAI'IE

NAI'1E-CUODVO,

TERI'IID-OO

// TERMNAI'IE

NANE-CUODV1,

TERI'IID-O

1

// TERT4NANE

NANE-CU1DV(),

TERI"lID-IO

,/,/

TERNNANE

NAME-CUIDVl,

TERNID-I1

x

xxxxxxxxxTHls

sT1'lNT

TypE

REQD F0R

CCpIVp

x

// DISKFILE

NAl'1E*CGIVFILI,

ORG-C,RECL-16

x

xxxxxxxxxTHls

sTl'1NT

TypE

REQD

F0R

CCpIVp

x

// DISKFTLE

NAI.1E-CGIVFIL2,

ORG-C,

RECL-16

XXXXXXXXXNOTE

THAT ONE

DISKFILE

STATET.lENT

-CGIVFILE-

I.IOULD

BE NEEDED

xxxxxxxxxJF

sYt4B0LIc

FILES

ARE

N0T

BEING

USED.

x

X THE FOLLOI.IING

TI,IO

DISK

FILE STATEMENTS

ARE

FOR EXAI',IPLE

ONLY

AND

Generation Stage 49

f+*++****NtiTF THAT

ttfttL

DIsxF]LE :TATF],!INT

-cGIVFILF- rttrult)

Ft NFFDED

+f****+'r*JF SYf{t.f}LIC

FILFS AcL Nr}f EEIhG USFD-

*

+ THt Hltlorlhc rtao urlsK FtLE srArFHFNrs ARF FoR FxAliptF ntuly AND

* sH[.]ULtl

BF RFHOVET

pRIcR,

TO RUNN]N(

ThIS ASSIGN],tFNr

stf.

*

// LttsKFI

LF NArrt[-.t]uttHyl

roR(__trqtcL_2>6

// Dl

sr(F

ILt NAltt-DUirHy2

rok(.-I ,RFCL_64rKt

yL_8

"KEypt)s_1

:}

I*I*+{I5**THIS sT}tNr TYPE RFGD

Fbu ccPTYP IF SYI{BoLIc

+

// SYnFILE

NAHE-cGIVF

rLt'DIsKFIL[-.cGlvFrLrrcc.IvFI LZ

r

I

*rr+t++*r*'***rkrs sil{NT NEcESsAky F(JR ccpIVp,pAc}. AND FRrt\rrFr{ vAttrFs

******+x.>k***+cAN bE ChANGF-r FOR yJilR CONFIG.

+

// PRUGRAA

t\AF[tC pI Vp,pbhLATA-yFS,

f / FILI S-rCGI VFI L5

/C O./t{,]sHR

r ,

I

**'*v>i<>i'::*>:Nurt,

THAT ccPtrvp husr Bt JN coRREcr pACx AT sfAr.TLrp

t

I THE FI]LLUb,ING Th,U PRTIGRA!4

STArf''1[NTS AIiE FOR TXAHPLE ONLY

I SH'JULD eE PFr+ovLt PRI

oc To DUNNING TFrrs ASSIr-ili,rEi:r s5r.

I

/./ PROGRAIi NAttE-DlJHHyl rMx THAX-2, pcXfATA_yE S,

// Fi LLS-rDtrHt{Y

l/ftlt/SHR,Dus4My ?/lr.UA/Sht,r ,pACK-SySTf }r,DFFt{TI RH_4

r

/ / 0r FxrlF-2 TDFFSF

DT-l 0,J6

t

/ / Pa

aG

q

AA ltAt',t

E-ouh4v 2, t{R f HAX

_2, pcti DATA_yt,(,

// FItFS-tI\tAAYl/bU/SH(rDl.FlMyZ./IRA,/SbtRrrpACK-SySTtMrLFFi.IFRil_2,

lf oFFNttF-l,DFFSFur-196

*

a

*/* REPLACT IrITH /*

I

tt**+ + i')t'tF

wD oF S AHPL

E AS Si

(,NTHE

NT r)

tc K

**:i*T*; *+r *+*r+*+*+****+$+*r*)B**

I

r**::<>lt\:***SAtlpLt

sTAFr{Jp u!.L Fuk ccpl vp*****:+**+**********,;,+*r**r***,r

I

+ FILL IIti UNII

I

// LOLj tcct,,

I

+**FL,LLOI{II](' II.fJ /,/ }ILL sTATTl{ENTs CORRLSPoI\t) To SAPPI

f ASSlGNHINT

ftrDtcK sY'.tFOLIc F

I LF S.

*

P

AC K_[.ROGq

A'{, PR

IN Tr

q

-NC

,HSTRINT'X-YTS

I

FlLts Ar.t

usEDr

t'rF ccP-

ANt'

00

r.50000

ooi60000

OO

570Oo(|

t)O58OOOO

oo590000

0060f)ooo

oo6

loooo

oo620000

OO63oOOCl

OOc4O(XlO

oo650000

(io660000

oo670000

oo5800()0

oo6900c)0

oo700000

u07

loooo

o(i72u00c|

r'ro7300c)C)

oo740()0C'

oo7500()0

oo760000

oo770000

oo76()000

oo79o()oo

oo8(x)ooo

oo5.I oooo

oo

A

200()0

oo6

30000

ooa40000

008 5000()

OOF {,OOOO

ooF

70000

oo88()000

(rOt

9OOOO

OOe3OOOO

oo<i

I oooo

oo920000

oo9300()0

O0e4trOOO

ooe10000

ooe6f'0()0

ooe70000

OOeg

9666

Oolo66gg

OItroOO0O

Ol(,lOO0O

o

1r}20000

o

I o30 0()0

ol o4()0c)0

O

I

i,50OOO

O

I

OT OOOO

Ol07()OOo

ol otroooo

ol o9()0()f'

(r

I I OOOOO

olltoooo

// FILF NA|tft{GIvFIt-lrRFrAIN_TrTkACr.S_lrtrNlr_ rpAc.K_

// FILT NAhE-CGTVFIL2.RTTA]:t-T.TKACKS_t,UN]T-,PACK_

*

+**ANY 5444

+ t*ANY 5444

r*+AlUy 5444

'3**IF SYnttrLIC FILTS AR,t NOI USti/ 3f:PLACt IHt PRtCFf

t)IftG Tt{(r

STATFHFNIS

**rSIlfGLE // FILE STATEHLNIT**l*,1

+*!+sx.r+**,r*l**+*5yvf;***,:***r*+rl**+

*

// FILF NAlrt-t.GMItE TRETAtN-TrTkA6f.s_lluNIr_ rFAcK_

+

/ / RatN

***-i*r;i:>t+ft\r{r

tlF sAf.lpLt SrART_up octr** *+!*+,.,***++**.,8:*}**+*:+r*:}a*r+:

'Not applicable

for prograrn

Number

5704_SC2

50

To

verify

that

an operational

CCP

system

was

qenerated

the user

should: Step

2 (System,

Cardless-Oriented):

1. Modifv

the

parameters

necessarv

in

the

ocL

state- I.:;'f:":J:::::'j;::":::'JJ il#il l;ISillll;flt

ments

and sample

assignment

control

statements' ,ion pr"t. The

system

then

prints

these members.

Tnere

2. perform

an assignment

run

that

specifies

the necessary are three

sections

to the information

printed:

environmental

information

to

execute

the installation o ccp cardress

generation

instructions

to modify

the

verif

ication

program (optional)' suppried

procedures

to refrect

your

system

requirements

3. start

the ccp and

execute

the

installation

verification {member

name

$cG1Gl}.

program' o Sample

$E

macro

statements

entered

directly

from

the

source library

to generate

the CCp

system

(member

name

Step

1

(lJser,

Cardless-Oriented): $CGIGM) or via

the system

input device.

rhe

user

enters

the rorowins

statements

rrom

trre

system ' n:':ffi;[1tTEl[J,T.%.i.T:illl.JJffi*'

input

device:

/&

// LOAD

$MAlNT,dsunit

i/ RUN

/ / COPY

F ROM.diUNit,TO-PR

I

NT,LI

BRARY-S,

NAME.$CG1.ALL

/

/ COPY

F ROM-diuniI,TO-PR

I

NT,Lt

BRARy-p,

NAME-$CG1.ALL

// END

where

dsunit

in the

// LOAD

statement

is the

unit

on

which

DSM

resides.

The

diunit

in the

/l COpy

statement

is

the

unit

on which

the CCP

distribution

pack

resides.

Generation Stage 51

An example

of the

printed

source

and

procedure

members

is:

tcclGt

l*t******ft**t**'l****'}*f+********a**t***********+f*t************+t,*$rf***+ 00000

* CARDLESS

CCP

GENERATION

INSTRUCTTONS * OOOIO

*:i**tlll'+l*****+f****l***tt+****+++*******tfttl*********+*t**+at*t**+r**** oo02o

* * 00030

t THE CARDLESS

CCP

GENERATTCN

PROC€DURE

MAKES

THE FOLLOtrINc

ASSUttprIgNS:

* 00040

*

. . THAT

DSI,I RESIDES

ON

Fl * OOO5O

*

'\LJruLJ urr rL t 00060

* 00070

$ , THAT

CCP

DISTRIBUTION

PACK

IS ON

RT + OOOSO

* , ooogo

* . THAI THE

LAST 20 TRACKS

ON

THE

CCP DISTRIBUTION

PACK

ON RT ARE * OOI.OO

* FREE

FOR

THE $SOURCE

FILE USED

BY THE I.IACRO PROCESSOR r, oot

lO

* o ool2o

* . THAT

THE $E flAcRo srATEt{ENTs

|IILL BE READ

FRctt

rHE souRcE * ool3o

I LIBRARY M€M8ER,

$CGIGi,4,

ON THE CCP DISTRIBUTION

PACK r OO14O

* * ool5o

* TF ANY

OF IHE ABOVE

ASSUHPTIONS

ARE

NOT

TRUET

USE

THE MODTFY

FUNCTION * OOI6O

* OF !I{AINT TO CHANGE

TF€ SUPPLIED

GENERATTON PROCEOURES

TO R,EFLECT

THE * OO[?O

* REQUIREXENTS

OF YOUR

SYSTE}.!. * OOISO

t o 00190

* SUPPLIED

GENERATION

PROCEDURES: * OO2OO

t o oozlo

* $cclcl *** CARDLESS

GENERATIoN

CONTRoL * 00220

* 3CGIG3 *** pRocE

ss usER

spEctFIcATIONS * 00240

t $CGIG4 +I+ PRINT

RESULTS

OF GENERATION

SPECIFICATIONS * OO25O

* ICGI65 **} CREATE

SOURCE

AND PRCCEDURE

MEMEERS I 00260

* * oo27o

f YOU

I(AY 4AKE

FOUR

KINDS

OF MODIFICATIONS

TO THE

SUPPLIED

PROCEDURES: * OO28O

* * oo29o

* I. IN IHOSE

STATEHENTS

MARKED

++ IN PosITIoN 74-?5 YoU MAY

CHANGE * Oo3oO

I THE

DSf{

PACK

LOCATION

FROM

FI TO

RT. I OO3IO

* o oo320

+ 2. IN THOSE

STATEMENTS

MARKED

#I IN POSITION

72_?3 YOU

MAY

CHANGE t OO33O

* THE

CCP DISTR

IBUT

ION PACK

LOCAT

TON

FROI,I

Rt. TO FI, R2 OR F2. * OO3+O

. + 00350

* 3. IN rHOSE

STATEMENTS

llaRKE0

t$ tN p0sITIoN 74-75 yOU

HAy

CHANcE + 00360

* THE

iSOURCE

FILE LOCATION FROI.,I

RI TO FI, R2 OR F2. I OO37O

* r 00380

+ 4. fHE t

// CO!{PILE

I STATEMENT

HAY BE REI{OVED

FROM PROCEDURE

tCGlG3 :t 00390

+ TO SPECIFY THAT

THE

MACRO

PROCESSOR

I'ILL REAC

THE $E HACRO + OO4OO

+ STATEHENTS

FROH

THE

SYSTEM

INPUT

DEVICE. * OO4IO

r -- srarEHENT

03070 __ : oo420

| * oo43o

* NOTE

__ IF A SOURCE

MEI,IBER

is USED 1T MUST BE PREPARED

PRIoR TO * Oo44O

I CALLING'rHE

pROCEDURE

$cG1G1. :r oo45o

* * 00460

+ tfHEN

YOU HAVE flAllE

THESE

CHANGES; , OO47O

+ CALL PROCEDURE

$CGIGI 8Y ENTER

I NG THE FCLLCI.JI

NG

OCL FROI,I

THE + OO48O

:f

- SYSTEf,I

INPUT

oEV

ICE. * O0{r9O

* * 00500

* // CALL $CGIGITUNIT -_ CCP DISTRIB(JTION PACK

-- * OO5IO

i //RUN *00520

* * OO53O

aa:i*** END oF INSTRtTCTI0NS

***:r++*rrr*r****+*** END

OF INSTRUCTIONS

.***r* 00540

52

9EFAC

ESCAPE-t

//////t,

PGIICNT"YES,

FORIlAT_YES,

PRUF-NO,

ACCEPT-NO,

RESOPN_NO,

BSYPRT-NO,

MOVTNT-NO,

NOlJDFF-NO,

RESREQ-NO,

5I0C-N0,

OPPRUF-NO,

CPUi'1SG-NO,

L0ilcA5-N0,

TTASK_NO

9EPLG

LANG-RPGII,

PPUNIT-R2

9EPLG

LANG-COBOL,

PPUNIT-R2

SESEC

SECUREICCP

SEFIL

SETS-],

PROGS-15,

DFILES-5,

TtrPMC,-(

DUtlPS-2,

cllRE-96K,

FLPACK-R2R2R2,

FLUNIT_R2,

DPTRAC-6

SEBSC

BSCA_I,

DA-NO,

D]AL-NO,

PP-NO,

NP-NO,

cs-YE5,

JETPlSG_YE5,

]TB-NO,

ptraqtrp-rtr

ASCII-NO,

EBCDIC-YE5,

XPRNCY-NO,

RESPOL-NO,

Ii.lTP0t,-Y[5,

ALITOFIS-NO,

PCIRT.

NO

SEBSD

TYPE-,3?77N2

sEcsc

B5CC-i.,

cE:

TNSG-YE:5,

I]B-NO,

RECSEP-1E,

ASCI

I

-N0,

EBCDIC-YE5,

XPRIICY-NO,

INTPOL-Y85,

PORT*NO,

PP-NO,

CS-YES

9EC5D

rYPE-3277n2

SEGEN

DSUNIT-F1,

CCUNIT-R2,

I,IKUNIT-

'

R2,

R1,

R1'

t,]KPACK-'R2R2R2,

PI

DIUNIT-RI,

I-1I

NR

ES*NO,

C/rRD-N0,

DFPACK-D2D2D2,

DPUNIT-D2

ICCCCCCI

/ X'XXXXXXXXXXXXI

-- N0 --

-* N0 --

-_ YES

_-

-- rE5 --

-- YES

--

-- Yt5 --

-_ YES

_-

-- YES

--

-- YE5

--

-- YES

--

-- YE5

--

-- YE5

--

-- PFl - PF12

*-

-- YES

-*

-- c0B0L / RPGI

I / F0RTRAN

/ ASSEi,t

--

--Rl/FI/P.2/F2--

-- COBOL / RPGII / FORTRAN / ASSEI,I

--

--Rl/FL/R2/F2__

-- CCP,/

USER

_-

--1-25--

--1-999--

-*1-r92--

--2-254--

-'a - YY

--

-- 128K/

I60K/

L92K/224K/256K/3EqK/5LzK

-- NATlE

OF

PACK

--

--Rl/FI/R2/F2-_

-- 0 - 1000

--

-- 0 - 2 --

-- YES

--

-- YES

-_

*- YES

--

-- YEs

--

-- N0 --

-- YES

--

-- TI,]O

HEX

DIGIT5 -_

-- YES

--

-- N0 --

-- YES

_-

-- YE5 --

-- N0 --

*- YES

--

-- YES

--

-- 5EE SYSIEi'1

REFERENCE

I,lANUAL

--

-- 0 - 2 --

-- N0 --

-- YES

--

-- TI,JO

HEX

DIGITS --

*- YES

--

-- N0 --

-. YES

--

-- N0 --

-- YES

--

-- YES

--

-- N0 --

_- 5EE

SYSTEM

REFERENCE

I'lANUAL

--

-- R1

/ Ft --

*-Rl

/tI ./R2/F2--

'UNIT,

UNIT,

UNIT'

DOOI,PIDOOI

I, -- 'PACKJACK,PACK'

--Rl/FI/R2/F2--

-- YES

--

-* YE5

--

.- PACK

NANE

--

-- UNIT

_-

CCP-P

I D

x00010000

x00020000

x00030000

x00040000

x00050000

x00060000

x00051000

x00062000

x00063000

x00064000

x00065000

x00067000

x00068000

00069000

x00070000

00080000

x00090000

00100000

00110000

x00120000

x00130000

x00140000

x00150000

x0 016

0 0

x00170000

x001E0000

x00190000

00195000

x00200000

x00210000

x00220000

x00230000

x00240000

x00250000

x00260000

x00270000

x00260000

x00290000

x00300000

x00510000

x00520000

x00530000

x00340000

00345000

00t50000

x00560000

x00370000

x005E0000

x00390000

x00400000

x0

0 41c

0 0 0

x00420000

x00430000

x00432000

x00454000

00436000

00440000

x00450000

x00470000

x00480000

x00(90000

x00500000

x00510000

x0c5r0001

00510002

'Prograrr,

Number

5704-SC2

:nly

Generation

Stage 53

$cGlGl

/I LOG PRINTER

/,/ NOHILT

*

+*t CCP

GENER,ATION

CIRDLESS

PROCEDURE T**

t

/l CAI-I

$CGtG-:,,R1 sr+ PROCESS

LrSER

SpECtFICATI0NS

r*,

ll clLL $CGlG4,Rl *++ ?Rlr-li

RESULTS

CF SpEC'FICATtONS *++

I I ci.LL $cGt05rRt **+ cREaie sou*ce At,tc

pRccEDURt

HENBFRs

*4*

| | CALL $CCPSA'Rl +t+ COtrpLErE

rHE CCp GEN€F.ATJON

+s*

0 1000

01010

0102

0

0I 030

01040

** 01060

H CI070

,til 0 t 080

It* 01090

$cG

lG3

*** CCP

CARDLESS

GENFRATION

PROCEDURE

***

**+ EXPAND

USERS

CCP

SPECIFTCATIONS ***

*

// LOAN ${PXDV,RI

/ | F

ILE NAi{F-tsol'tRCErR

FTA

IN-Tr

uN

IT-R

r,pAcK-pIDc0r,

rRAcKs-20,

/

/ LOCATTON.3B6

/ / COITPILF

SNURCE*fCG

IGY,UNIT-RI

// RUN

*

* NOTE:

*

+ iE MACRO

STATEMENTS

ARE

FNTFRFD

VIA THE

SOURCE

LItsRARY

IlEMBER

$CGIGM

* ON THE

CCP

DISIRIEUTION

PACK

OR FRCP

ThE

SYSTEP

INPUT

CEVICE

IF THF

* IIl COI.'PTLE'

SIATFIIENT

IS RE'.IOVED

FROI.'

THIS PRCCEDURE.

$cG

I G4

*** CCP

CARDLESS

GENFRATINN

PROCECURE

*+*

*** PRINT

RESULTS

OF

CCP

GENERATION

SPECIFICAIIONS

,i

// LOAD tCClPPrRl

/ I FTLF

NAI.tE-$SoURCETUNIT-RII

PAcK-PIDOoT

// RUN

ri3C00

030

lo

03020

03030

{{ 03040

#{ $so3050

03060

t# 03070

03080

03090

J3

100

031t

0

03120

o3

130

03140

0?150

03

160

040

t0

c4020

04030

04040

04050

#* 04060

##$304070

04080

54

$ccl65

05 010

+{+ CCP

CARDLESS

GENERITION

PROCEDURE

*** O5O2O

t 05030

T** IF NC

ERRORS

IN GENERATION

SPECIFICATIONS,

LCAO $HAINT

TO

CREATE O5O4O

*** SOURCE

ANO PROCEDURE

MEI.IBERS

THAI

IIILL COMPLETE

THE

CCP

GENERATION O5O5O

+

tt L}AD ir',tAlNTrFl 05060

++0507

0

/, FI

LF NII{E-SSOURCE,UNIT_RII

PACK-PIDOOIT

RETAIN.S ##5S05O8O

// RUN _ o5o9o

/

/ copy FRof4-DISKrro-RI,RECL_95,RETAIN_RTFILE_jSOURCE 1#$r05loo

/

/ END o5llo

Generation Stage 55

Sfep

3 (User,

Cardless-Oriented):

The

user

modifies

the

sample

procedures

to reflect

the

requirements

of

the user's

system.

This

is

done

by using

the MODIFY

statement

in

the utility

program

$MAlNT.

(For

a description

of the MODIFY

starement

. see

the

IBM

System/3 Model l5 System

Control programming

Reference

Manual

, GC21-5O77

or IBM System/3 Model |

5 System

Control Program

Concepts

and Reference

Manual.

GC21-5162.I

Specifically

the

user

can modify:

o The DSM

pack

location.

o The

CCP distribution

pack

location.

o The

unit,

pack

and

location

for

the

$SOURCE

file

re-

quired

by the macro

processor.

o The

source

member

name

onlhe

//COMPILE statement

to reflect

which

source

member

contains

the

user,s

CCp

generation

specif ications.

o The

//COMPILE

statement

can

be removed

from oro-

cedure

$CG1G3 to specify

that,

during

step 4,

the macro

processor

reads

the user

specification

from

the

system

input

deviie instead

of from

a source

librarv

member.

Note: lf the

// COMPILE

statement

is used

in procedure

$CG1G3,

the source

member

described

must

be

prepared

prior

to calling

procedure

$CG1G1.

See

step

4 tor

a

descrip-

tion of entering

the

$E

control

statements.

Step 4 (

User/System, Cardless-Oriented

)

:

The

user calls

procedure

$CG1G1

from

the CCp

distribution

pack.

This

procedure

controls

the remaining

portion

of the

CCP

generation.

lt

does

this

by nraking

calls

to these

pro-

cedures:

$CGlG3,

$CG1c4,

$CG1GS, and

$CCpSA

res-

pectively.

Each

of these

procedures

performs

a

different

generation

process.

procedure

$CG1G3

is

described

in

this

step.

Procedures

gCG1G4

and

gCG1G5

are

described

in

step

5;

procedure

$CCPSA is

described

in

step

6. procedure

$CCPSA is

a

procedure

generated

during

step

5,

based

on

the user's

input,

that

controls

the

generation

of

the

user,s

CCP

pack.

Procedure

$CGlG3

loads

the macro

processor

and

allows

the user

to enter

the

$E

control

statements.

There

are

two

ways

the user

can do

this:

via

the system

input

device

or

from

a source

library

member.

However,

to enter

input

from

the

system

input

device,

the

user must

remove

the

/l COMPILE

statement from

this

procedure.

(For

a

descrio-

tion

of the

// COMPILE

statement,

see the

IBM

System/3

Model l5 System

Control Programming

Reference

Manual,

GC21-5077

or IBM System/3

Model l5 System

Control

Program

Concepts

and Reference

Manual

, GC21-51r62.\

The

source

member,

$CG1GM,

printed

in

step

1

can

be

used

as

a

guide

for entering

the

$E

control

statements.

This

module

can

also be modified

for use

as input

to the macro

processor

since

the

// COMPILE

statement

in

procedure

$CG1G3

specifies

$CGIGM

as the input

source

member.

The

user

should

enter

the control

statements

without

insert-

ing

any

additional

statements

except

where

more

than

one

is required:

o $EPLG

statement

- additional

$EPLG

statements,

with

both

the LANG

and

PPUNIT

parameters

presenr.

are

required

if more

than one

programming

language

is

to

be supported.

. $EMLD

statement

- additional

$EMLD statements,

with

both the

TYPE

and XMCODE

parameters

presenr,

are

required

if MLTA

terminals

are to be

supported.

o $EBSD

statement

- additional

$EBSD

statements,

with

the

parameter

TYPE

present,

are

required

if more

tnan

one

type

of BSCA

terminal is

to be supported.

. $ECSD

statement

(Program

Number

5704

SC2

only)

-

additional

$ECSD

statements,

with

the

parameter

TypE

present.

are reguired

if more

than

one type

of BSCC

terminal is

to be supported.

Step 5 (System

/User, Cardless-Oriented

)

:

Procedure

$CG1G4

prints

the results

of the

CCP

generation

specifications.

lf there

are specification

errors,

the

user's

statements

and

the error

diagnostic

messages

are

printed.

Before continuing,

the user must

restart

the CCP

generation

at

procedure

$CG1G1

and

provide

error free

specif ications.

lf there

are no

errors,

the user's

statements

are

printed.

Then

procedure

$CG1G5

is

called

and the records

which

will

be input

to

step

6

are

printed.

procedure

$CG1G5

loads

$MAINT

to create

the

source

and

procedure

members

that

will complete

the

CCP

generation.

Also

printed

is the

$SOURCE

file

setup for

the

$MAINT

file-to-library

run.

56

Step 6 (System,

Cardless-Oriented

)

;

The

system

calls

the

generated procedure

$CCpSA

from

the distribution

pack

and

begins

the major

step

of the

CCp

generation.

During

this

step the

user's

CCp

is created.

The

sequence for

this step is:

1. Creation

of a load module

which

contains

the initial

contents

of

$CCPFILE

and

the instruction

code

to

initialize

that

f

ite

($CC1BF).

2. Source

generation

and link

edit

of

the modules

$CC4#1

and

$CC4#2,

which

is

the resident

control

program

during

CCP operation.

3. Copying

of supporting

load

modules

for

the

opera-

tional

stage, including

startup,

shutdown,

and the

assrgnment stage.

4. Creation of an initialized

module

$CC429

if

SECURE-USER was

specified

in

the

$ESEC

statement;

this

module will contain

the

user's

securitv

information.

5. Initialization

of

$CCPFILE

and

$CCPDUMP

(5704-SC2

only)

later

to be filled

with user specif ica-

tions

by assignment runs.

6. Copying

of the subroutines

and macros used in

the

compilation

and

link

edit

of application

programs

to

run under

the CCP.

7. Print

the sample

control

statements for

an

assignment

build run

necessary

to execute

the installation

verifica-

tion

program.

On

the

following

page

is

an

example

of

the

sample

assignment input.

Note: For Program

Number

5704-SC2

only, step

5

follows

steo 7.

Generation

Stage 57

$CGSST

XXXXXX SAlIPLE

ASSIGNMENT

SET CONTROL

STATET'IENTS XXXXXX

*

xxxxxx THE

F0LL0l{ING

x,(xxxx c0NFIGURATI0N

STATEI'IENTS

CAN

BE

NODIFIED

FOR

YOUR

BUT

5OI.1E

I'IUsT

BE KEPT

TO

RUN

CCPi'P.

!EI ID-a,

AcTI0N*CREATE,DFLTEXEC_yEs,ANyspEC5_NO

!y9IEr4

mrNUpA-zZK,

NTNTnBUF_ialo,.

-

PASSI,IORD_FECD,

C

O NI'l

A

N D L

-

5

O, D F

FP

A C

K

- P

RO

GR AI,1,

P

GI,I

R

EQ L

- 1 5

T E Rl'lA

T T

R A

T T R

I D- 1, T

RA

NS

L AT

- N 0, B

L K

L

- 5 I 2, DA

T A F0Rr't-t'tEs sA G E,

VERI

FYID-NO,

DFF327

O-YE5

XXXXXX THIS

5TI'1NT

TYPE

REQD

FOR

CCPIVP(OR

MLTALINE

STMNT)

// bSCALINE TYPE-CS,

LINENUI,I-I,POLLLISi-,

OO,

Or,

iiJ,

ir,

,// BSCATERI,I

TERI'IID*O(l,TYPE-3277N2,ATTRID-i,COTINAHP-YES,OFFACTN-HOLD,

,/

/ A D

D R

C H A

R

- x

6 0

6 0 4

0 4

0

x , p

o

L L

c H A

R

_

x

q

o

q

o c o

q

o

x

// BScATERN

TERI'1ID-01,TYPE-3277t'tz,ATTRID-t,comt'iAND-yES,0FFAcTN-H0LD,

,/ / A

D D

R C H

A

R

- x 6

0 6 0

c I c I x , p

0 L

L c H A

R

_

x C

O

q o c t c r x

'// B 5 cA

T

ERI'I

r

ERr'l

I D-

1 0,

Typ

E-

i27

7Nz,

AT TR

I D-

I r

c0r'fi'rAND-N0,

,/,/

ADDRCHAR-x6

I 6

I 4

0 4 0

x,

P0L

L CHAR-xC1

C

I 4 04

0

x

/'/ B

5 cA T

ERI'I

T

ERt'lI

D-

1 1,

TYP

E-

J27 7l'tz,

AT TR

I D-

1, c0r'TNAND-N0,

/,/ ADDR9HAR-xo

I

6 1 ct

c1

x,

p0L

L cHAR_x6t

clct c1

x

/,/ TERNNAIT1E

NAI'IE-CUODVO,

TERMID-(}O

// TERI,lNAIIE

NAI'IE-CUODVI,

TERI,lID-01

,/,/ TERI.lNAI'1E

NAr'1E-CUlDVO,

TERI,IID-I

O

,// TERI'1NA14E

NAI'1E-CU1DV1,

TERf,IID-1t

*

XXXXXX THIS

STMNT

TYPE

REQD

FOR

CCPIVP

// DISKFI

LE NANE-CGIVFILE,

ORG-C,

RECL-15

x

XXXXXX THIS

STMNT

NECESSARY

FOR

CCPIVP

/,/ PROGRAI,I

NAI'1E-CCP

I VP,

PGI,IDATA_YES,

PR I NT

ER-5HR,

/ / FILES-

ICGIVFILE/COlNOSHRI,

// ?ACK-PROGRAM

00010000

00020000

00030000

000q0000

00050000

00060000

00070000

000E0000

00090000

00100000

00110000

00120000

00130000

00140000

00150000

00160000

00170000

001E0000

00190000

00200000

00210000

00220000

00230000

002q0000

00250000

00260000

00270000

00260000

00290000

00500000

00510000

0 0 32 0

0 0 0

00550000

0 0

34 0 0

0 0

00350000

00360000

00570000

x

X

To V e

r

i fy G en erat i o n (

U

ser, C a rd

I ess- O rien ted

)

To verify

that an operational

CCP

system

has

been

gener-

ated, the user

should:

1. Modify

the sample

assignment

set contained

in the

source library member

$CGSST

on

the CCP

produc-

tion

pack.

To do this, use

the

MODIFY

statement in

the utility

program

$MAlNT. {For

information

on

the

MODIFY

statement,

see

the

appropriate

SCP

reference manual

listed

under Related Publications

in the

Preface.)

Perform

an assignment run

which specifies

the

necessary environmental information

to execute

the

installation verif ication

program.

Start the CCP

and

execute

ther installation verifica-

tion program.

GENERATION

CONTROL

STATEMENTS

Each

CCP

generation

requires

a

set of generation

control

statements. lf the

required statements

are not

specified, no

generation

takes

place.

Some

generation

statements are

always required for CCP support,

and others

are required

only

if the user desires a

certain option.

Those

control

statements

always required

are:

All generation

control statements

the

following

order:

$EFAC

$EPLG

$ESEC

$EFIL

$EMLA'

$EMLD'

$EBSC

$EBSD

cpncc )

il;;; I szo+-scz ontv

$EGEN

2.

3.

(if present)

must be in

Optional

statements

must

be

present

to include

support for

MLTA,

BSCA.

or BSCC;

that is,

the

$EMLA

statement

and

at

least

one

gEMLD

statement

must

be

present

for MLTA

support,

the

$EBSC

statement

and

iat least

one

gEBSD

state-

ment

mLlst

be

present

for BSCA

support.

and the

$ECSC

statement

and at least

one

$ECSD

statement

must

be

present

for BSCC

support

(5704-SC2

only).

I

MLtA and BSCC are mutually exclusive.

Writing Generation Control Statements

Starting

in

Column

The

name

field

can contain

any

valid assembly language

symbolic name beginning in column 1. The name

is assigned

to the

first byte of generated

code.

Because the name is

optional, it is not shown.

;,;$$$fi

,:T*r*r

:I

The desired mnemonic

operation code

(corrtrol

statement

name) must

appear

as specif ied

in the control statement

description. The

operation

code

must

start in column

8.

I l:;'="1*'*.

Ifr"1"'ry1*l

'I

72

14

The

optional control

statements are:

CCP

facilities

Programming

langtuages

$CCPFILE

allocation

CCP

generation

stream

Terminal

sign-on

security

MLTA

support

MLTA devices

BSC

support

BSC

devices

::::::lr:l I szoa.scz

onrv

nsuu

supporr

I

$EFAC

$EP

LG

$EFIL

$EGEN

$ESEC

$EMLA

$EMLD

$EBSC

$EBSD

$ECSC

$ECSD

Name Operation Operands Continuation

Symbol

or blank

Statement

name

No operands

or one or more

separated

by

commas

Any nonblank

character if

continuation is

being used

Generation Stage 59

1.

The

operands

specify

available

services

and

options.

The

operands

must

start

in

column

14

and

are written

as

follows:

3. Commas

precede

all but

the first

operand.

I |

**'

|

"'"'"' I

*:"

{,

,",

r+r

,

I

4" The

parameter

part

of the

operand

must

immediately

follow

the

dash.

I l**l::-*tlffi"frtrer+r

' I

5. The

keyword

part

of each

operand

must

corresDond

to one

of the keywords

in

the

control

statement

description.

ilfiil

6, Some

operands

are

not

iequired-.

These

optional

operands

are indicated

by enclosing

the

operand

within

brackets

IKEyWORD-parameter]

. The

operand

enclosed

in

the braakets

can be

coded

if the

associated

option

is

desired.

The

bracket

symbols

[]

are used

to help

define

the

control

statements.

These

symbols

are not

coded;

they'

are

only used

to indicate

how

a control

statement

can

be

written.

I l*_."1,,=",",

lF:"t,,.,,

l+l

,

I

7. An option

list for a

keyworct

parameter

is

specified

as

follows:

Braces

( ) indicate

that

a

choice must

be

made.

One

of the

parameters

from

the vertical

stack

within

braces

must

be coded,

depending

on which

of the associated

services

is desired.

The

symbols

{ } .r. used

to help

define

the control

statements.

These

symbols

are not

coded;

they

are

only used

to indicate

how

a control

statement

can

be written.

fiiiffiril.l**r:

l

e, i

r.

:lir;

:i:::f

L The operands

can be written in any order. lf a key-

word is

not specified,

the default value

is used. A

default value

is selected

for optionai keywords that

are omitted. The default

value

is indicated

in the

macro

instruction

description

by a line under

the

default

option. For

example,

(a)

KEY-<

B

)

lcl

indicates

that option A is

the default

value.

I l,;.,,

1,._.,_*

li**

f

,,'.*,.1+l

,

I

L No

operands

can

be specified

beyond

column 71. lf

continuation

is required.

column 72 must

contain a

nonblank

character and

the lirst

operand must

be fol-

lowed

by

a

comma.

An

operirnd

cannot

be divided

and continued

on the next lirre. The

operands of the

continued

field

must

begin

in column

14. For

an

example

of continuation

coding,

see Figure

4.

10. Comments

must

be

separated from

the operand

or

comma

by at least

one

blank

space. Comments

can-

not be inserted

between

operlnds

on a one-line

con-

trol statement. Figure

5

shovrs examples

of com.

ments

used

with control

statements. On

tne assem-

bly

listing,

all comments

on

tlre

generated

code are

justified

by the macro

procesrior

to begin

in column

40. Any comments

too long to

be contained

in

columns 40

through 71

are trlncated f rom

the right.

{No I

<ccP I

(

usrn)

60

Figure

4, Continuation

Coding Examples

Figure

5. Comments

on Macro

Instructions

Most

operands

have

default

values.

The

user

can have

a

control

statement

present

and have

all operands

absent

if

he

accepts

the default varues.

In

all

cases

where YES

is appropriate,

the

single letter

y

can

be used. In

all

cases where

NO is appropriate,

the

single

letter N can be

useo.

In

the following generation

control

staternent

descriotions

the term object

system

refers

to the system

that execures

the

CCP

after

generation.

Generation

Stage 61

What You Must Know

Whether

the

data mode

escape facility

is

to

be

generated,

and

if so the

six user-specified

data

mode escape

characters.

Will

a

program-reque$t

count

be

kept?

ls

display format

facility

(DFF)supportedr

ls

program

request

under

format

(PRUF)

supported

?

ls

core resident

accept

input

supported?

ls resident

OPEN/CLOSE

supported?

ls

328X printer

busy

support

to be

included

?

ls DFF to be moved

out to support

more

terminals?

Are

the Terminal

Name

Tables

(TNT)

to be

moved

out to support

additional

terminals?

ls

resident

program

request

supported?

ls

the serial

l/O chanrrel

RPO

to be

supported?

ls

the Task-to-Task

facilitv

to be

supported?

\PI

1 cccccc | )

I

x'rr***"**"***'\

tYESI ,

'1ruo

f l

,YESI ,

i*o f r

/vesl r

INg

/

IYESI

i* t J(s704SC2onlv)

{ Y^ } r {5704.sc2 onry}

tYES'

l YES\ ,

lNo I

{ :- } | t57o4

SC2 onrv r

I rvu I

lves[ ]

lu.o J

(vrsl

1

,lp i I {5i04-SC2 onrv)

(vesI

'i

*o i I (5704

sc2 onrY)

lvesl

1

ryp

i l t57o4

-sc2

onry)

(ves)

1'

n I l(57o4sc2wrrh

/No \

\ PFr

I

< PF2 ) I (57o4-SC2

only)

l, \

\ PF12

)

( l:t I r

(5704.SC2

onrvr

lt\u I

[

,PGN4C

NT

[,FORMAT

[,PRUF.

[,OPPRUF-

[,ACCEPT-

L,R

ESOPN

[,BSYPRT.

[,MOVDF

F

IMOVTNT-

[,

R ESR

EO-

[,TTASK

$EFAC-CCP Facilities

The

$EFAC generation

control

statement indicates

options

that determine

the CCP facilities

to be

included durino

generat

ion.

This

statement is always

required

and must

be the first

of

the

generation

control

statements.

OnlV

one

$EFAC state-

ment

can be entered. All operands

of this

statement

are

opti

ona l.

(uq I

ESCAPE- \'cccccc' I

I X'**""""*""*r.*,)

The ESCAPE

operand

specifies

whether

data

mooe

escape

is

supported

and

if so.

the

six data

mode

escape

characters

to be

used.

The

data

mode

escape

function

is used

by

the

terminal

operator

to instruct

the

CCp

to accept

the

as

a

command

to

the

CCp

and

not

as data

for

the

program

with

which

the

terminal

had

been

communicating.

This

is

the

only

way

a terminal

can

interrupt

the

normal

course

of a

program

it requesterl.

The

CCp

checks

all

data

input

f

rom

a requesting

terminal

for

this

string

of

characters

as the

first

six

bytes.

Be

sure

this

string

is

not

a sequence

of

bytes

that

can

inadvertently

be

entered

as data. lt is

suggested

that

the

string

be

made

up

of

six

speciar

characters

such

as srash

(/).

EBCDIC

characters

or

hex

digitr;

can

be

used

for

this

value.

lf EBCDIC

characters

are used.

this

value

must

be

made

uo

of exactly

six

characters.

lt is

suggested

the

value

be

enclosed

in

apostrophes

as

shown.

because

certain

characters

chosen

for

this

string

might

be

considered

operand

delimiters

by

the

macro

processor.

lf the

apostrophe

(') is

to be

one

of the

characters

of the

string,

then

each

such

apostrophe

must

be

coded

as

four

successive

apostrophes,

and

the

parameter

must

be bounded

by apostrophes.

lf the

hex

form is

used,

the

pararneter

must

be

coded

as:

o The

letter

X

r A single

apostrophe

(')

o Exactly

12

hex

digits

o A single

apostrophe

(')

The

default

value

is NO,

indicating

no

terminal

can interrupt

a

program

and

communicate

directly

with

the

CCp. For

a

mininrum

system

this value

is NO.

PGMCNT-

The PGMCNT

operand

specif

ies

whether

a count

should

be

kept

of the number

of times

a user

program

was requested.

Not all requests

for a user

program

are

counted.

The

exceo_

tions

include

requests

for an

already

active

MRT and

certain

rejected

requests.

The count is

a request

count, not

an execution

count.

YES

indicates

these

counts

are

to be

accumulated

during

the

execution

of the

CCp,

and

are

to be

added

to previous

counts

in

$CCpFILE

during

the

CCp

shutdown.

The

default

is NO,

indicating program-request

counts

are not required.

These

counts

can be used

to design

or redesign

user

programs

to take advantage

of certain

CCp features

(such

as

reusability

or multiple

requesting

terminals)

affectinq

program

request

response

time.

For Program

Number 5704-5C2,

if the active

assrgnment

set

has

been

changed

since

startup.

the

counts

will not be

updated.

For

a minimum system

the

value

is

NO.

FORMAT-

The FORMAT

operand

specifies

whether

the dispray

format

facility

(DFF)

is

to be

included

in

the

CCp.

A value

of

YES

includes

DFF

support

in the

CCp.

The

default

value

is NO

indicating

a CCP

system

without

DFF

support

is to be

generated.

PRUF.

The PRUF

operand

specifies

whether

program

request

under

format

(PRUF)

is

supported.

yES

must

be

specified

if

using

the PRUFLNG parameter

in

the

pROGRAM

state-

ment

at assignment

time.

The

default

is

NO. For

more

information

on PRUF,

see

the lgM System/3

Communica-

tions Control Program

Programmer,s

Beference

Manual.

GC21.7579.

J

YESI

INO J

I YESI

tNo

,

lves I

tNo t

Generation

Stage 63

OPPR

UF (5704-SC2

onlv)

The

OPPRUF

operand specifies whether PRUF

is to

op-

timize the

TP

buffer

for PRUF

mode

terminals. lf YES

is

specified,

CCP will invite command

mode

PRUF

ter-

minals

only for the data

expected

from

that terminal.

(DFF

calculates

the amount of data that is

to be

received

from

a terminal.)

lf NO

is specif ied, the

command mode

PRUF

terminals

will

always be invited for

the maximum

PRUFLNG

specif ied in

the assignment

set.

This

function

may

be

needed

if

CCP is communicating

with

a System/7

or a

Series,/1

;for

example,

that is

supporting lines

in

addition to CCP. The

default

is

NO.

(NO

)

CPUMSG-

{- } (5704-SC2onty}

(YES'

The

CPUMSG

operand specifies

whether

information

messages

(S

type) are to be

sent to the

CPUs. YES

indicates

that messages

are

to be sent. YES

should be

specified if

the

CPU is

a System/34.

The

default is

NO.

ACCEPT-

The

ACCEPT

operand

specifies

whether

the

resident

code

will handle

the user

input

data

or whether

a transient

will

have

to be

called. YES

indicates

the resident

code will

handle

the

input;

NO

indicates

a transient

will have

to be

called. The

default

is NO.

RESOPN.

{Gt } ruroo.r.2

onry)

The RESOPN

operand

specifies

whr:ther

or not the resident

routine

is to be incorporated

to handle

the

pseudo

open/

close/allocate

functions

of CCP. YES

indicates

that the

resident

routine

handles

the

processing

and

occupies

10K

bytes

that would otherwise

be

allocated

to the user

program

area.

NO indicates

that

transients

are invoked

for this

function. The

default

is

NO. lf RESOPN

is

yes

for genera_

tion,

an external

pointer

list

(EpL)

is

built

during

start-up

time.

BSYPRT.

The

BSYPRT

operand

specifies

whether

the

code

to handle

a 328X printer

busy

condition

is

to be included

in

the CCp.

YES

indicates

that

the support

is

to be

included.

yES

allows

CCP

to detect

a printer

busy

condition,

retain

control

until

the

printer

has

completed

the

operation,

and

then

return

control

to the

application

program.

The

default

is

NO.

64

MOVDFF. (5704-SC2

only)

The

MOVDFF

operand

specifies

whether

the

resident

routine

that

supports

DFF

is

to be

moved

from

$CCp#2 to a

4K-byte

area

that

would

otherwise

be allocated

ro tne

user

program

area.

The

purpose

of this

move

is

to

enable

the

system

to support

additional

terminals.

yES

indicates

that

DFF

is

moved

out. The

default

is

NO. lf MOVDFF

is

YES,

DFF

must

also

be

yES.

(5704

SC2

only)

The

MOVTNT operand

specifies

whether

the Terminal

Name

Tables

(TNT) within resident

CCp

are

to be

moved

to a 2K

or 4K-byte area

that would otherwise

be

allocated

to the

user

program

area.

The

purpose

of this

move

is

to enable

the

system

to support

additional

terminals.

yES indicates

that the TNTs are

to be

moved

out. The default is

NO.

I

YES\

lruo l

l

ves\

INA

J

YES\

triro

J

fYESI

l lro

f

MovrNr.

{[']

YES\

NOJ

RESREo-

{

The RESREO

operand

specifies

whether

the resident

routine is

to be incorporated

to handle

the program

request

functions

of CCP. YES indicates

that the

resident

routine

handles

the

processing

and

occupies 4K-byte

area

that

would

otherwise

be allocated

to the user

program

area.

NO

indicates

that transients

are invoked

for this function.

The

default is

NO (5704-SC2

onlv).

SIOC

The

SIOC

operand

specifies

whether

support

for

channel

connected

systems

is

to be included

in

this

generation.

The

default

is NO. (See

l8M System/3

Model l5D

Channel

Connected

Systems

Program

Reference

and

Logic

Manual,

GC21

5199.)

LOWCAS- (5704-SC2

onlv)

The LOWCAS

operand

specif ies

the PF key to be used

to

indicate lower

case input

from a

terminal for program

request

data

only. NO indicates

that

all input

will be

upper

case. The

default is

NO.

(

YES)

i *o I (5704-sc2

with

57e9-wNK)

lHr t

{

;,,,1

TTASK i YES i

lNo

I

LANG

(5704

SCIZ

onlv)

The

TTASK operand

specifies

wl-rether

support for the

task_

to-task

communication

f

unction

is

to be included

in

this

generation.

The

def

ault is

NO. (See

tBM System/3

Com_

mun ications Control Program programmer,s Reference

Manuitl, GC21 7579.1

$EPLG

* Programming

Languages

Each

$EI,LG

generation

control

statement

indicates

a

pro-

gramminr]

language

for program

preparation

under

CCp.

The

fc,llowing

rules

apply

to this

:;tatement:

. At least

one

$EPLG statement

is

required.

o One

$EPL"G

staternent

is

required

for each

programming

lanquage

supported

by the

CCp. Only

one

$EpLG state_

mer)t

can be

entered

f or

any one

language.

. The,

f irst

$EPLG staternent

must

irnmediately

follow

a

$Ef:AC statement.

Multiple

$EpLG statemenrs

can

come

in any

order

after

the first.

a All opr:rands

on this

statement

are

required.

(coaoL ,

, AN,^ )io*i*o*{

LArN\r- )

assrna /

(ffi;' !

The LANG operand

specif

ies

a programming

language

tnat

is

to be

supported

by the

CCp. This

operand

indicates

the

language

that is

to be

included

in

the

CCp. ASSEM

is

the

abbreviation

for Basic

Assembler

language.

At least

one

of

the languages

is required.

There

is no

default.

PPUNIT.

The PPUNIT

operand

specifies

the disk

unit

containing

a

pack

used

for compiling

application

programs

for the CCp.

For

example,

this is

the

pack

containing

the RPG

ll

compiler. Use

this

operand

to specifV

the disk

unit for this

pack

during

generation.

There

is no default. Anv

5444

unit is valid,

except

the unit

on

which

the distribution

pack

is mounted.

The

assembler user

gets

the CCP

$N macros

copied into his

source library

on this

pack. He

must

designate

the PPUN

lT

as

a unit on

which

the Macro Processor

resides. The

CCP

$N macros

must

be

on

the same

pack

as the macro

processor

or the DSM

pack

from which

the user

will perform

initial

program

load

(lPL)

when

assembling

CCp

programs.

A // PAUSE

card

containing

comments

on

directions

for

proceeding

is

generated

into

the input

stream

for copying

and/or

renaming

data

management

modules.

This

allows

the user

to ensure

that

the correct

pack

is mounted

on the

correct unit. The

routines

copied

to the

pack

on this unit

a re:

LANG Parameter

COBOL

FORTRAN

ASSEM

What

is Copied

Communications

service

subroutine

CCPCIO

Communications

service

subroutine

CCPF lO

Communications

service

macros

$NCOM,

$NPLO,

$NOPV, $NRTV,

$NPL,

ANd

$NCrO

Communications

serv ice

subroutines

SUBR90,

SUB R91,

SUBR92, SUBR93,

and

SUB

R88

RPG II

I:;i

l:;l

i

COBO

L

.lronrnanril

]ASSEM I

'RPG

I i

,PPUN

IT.

l

Rlt

)"(

I:;J

What You

Must

Know

Programming

languages

to be

supported

by the

CCP.

Disk

unit on which

the

pack

used

to prepare

programs

wntten in

that language

is

mounted

during generation.

Generation

Stage 65

$ESEC*Terminal

Sign-On Security

What

You

Must

Know

What

type of sign-on

security

used, if any.

Length

of the user's

security

information,

if a

user written

sign-on

security routine

is

used.

The

$ESEC

generation

control

statement

indicates

the

type

of terminal

sign-on

security

used

(if any).

This

statement

is

optional. lt is

included

only if terminal

sigrr-on

security

is desired.

lf inclr_rded,

this

statement

must

immediately

follow

a $EPLG statement.

Only one

$ESEC

statement

can be

entered.

All operands

of this

sratement

are optional.

LUSI.

The LUSI operand

specifies

the length

(number

of bytes)

of the

user's

security information. lt should

be

omitted

unless

SECURE-USER

is

also

specified.

The

default value

is

0 and the maximum is 4096. However,

the value

of this

operand

must

not be

0 if SECURE-USER

was

specified.

lf the user

specifies

SECURE-USER,

at startup

this

number

of bytes is moved

from load module $CC4Z9 to the user,s

security

work area reserved

in the resident

CCp

supervisor

during

the

CCP

generation.

For

a

minimum

system, the value

is

0"

$E

F I

L-$CCPF I

LE Allocation

The

$EFIL

generation

control

statement

provides

inforrna

tion that

affects the

allocated

size and location

of

$CCPF

I

LE.

This

statement

is always

required.

Only one

$E

F

I

L state"

ment

can be

entered. This

statement must

irnmediately

follow

the

$ESEC

statement

(if

present)

or

the

$EFAC

statement

(if $ESEC

is not present).

All operands,

except the

FLUNI-t, FLPACK,

and

TRKLOC

operands, are used

by the CCP

generation

to estamate thr:

disk space required for

$CCPFILE

and

SCCPDUIMP

f

0 t

i;f

l*.,,.

|

,,,",..

l3::_t

, ,,.,.,{*}

, I

JtrLU I( t

The

SECURE

operand

specifies

whether

terminal

sign-on

security

support

is

wanted. The

dr-'fault

is NO. lf the

default

is used,

any command

terminal

can

sign

on to the

user's

system

without presenting

any

validation

informa-

tion.

CCP

indicates

that

the

CCP

password

security

routines

will

be

included

and used. Each

command

terminal

user musr

then

give

the proper

one-to-six

character

password

as

the

operand

of his

sign-on

command

before

he

can

address

the

system

to use further

facilities.

The

actual

password

is

specified in

an

assignment run.

USER indicates

that

the user

wishes

to include

his

own

srgn-on

seourity

routines

instead

oi using

those

of the CCp.

These

must follow the rules

specif ied for such

routines

(see

IBM System/3 Communications Control program program-

mer's

Reference

Manual

, GC21 75'19l.. In addition, at

startup

the user's

security information

must

exist

in

a

load

module

named

$CC4Zg.

For

a nrinimum

system,

the value

is NO-

{No )

( ccP

(

usen

I

What You Must Know

Anticipated

number

of assignment

sets to be

placed

into $CCPF

I

LE.

Anticipated

number

of programs

an<J

files

in

an

assignment set.

Anticipated

number

of terminals

in

your

con

fi

gu

ration.

Number

of main

storage

dumps

to be

retaincri

in

$CCPDUMP

during error situations.

Main

storage size

of pr

ocessing unil.

Disk

unit

and

pack

name

on which

$CCPFILE

is

to be created.

Beginning

track location for

$CCPF

lLE,

if you

wish

to position

the f ile

on the

pack.

ob

You

need not

be

overly concerned

about

allocating

too

little

space

for

$CCPFILE or

$CCPDUMp. lf later

you

find

that the

space

is too small for

your

requirements,

you

can

enlarge

the space

for

the f ile

by

doing

one

of the following:

Use the

$COPY

program

to copy

$CCPF

I

LE

to a

larger

space on disk.

Use the

program

$CC1BF,

which is

present

on

your

CCP Production

pack,

and

specify

a

FILE

OCL

state-

ment

to indicate

the number of tracks

required.

Run

$CC

l BF;

then rerun assiqnment

to reestablish

the con-

tents of

$CCPF

I

LE.

Use the

program

$CClDP,

which is

present

on

your

CCP

Production

pack,

and specify a

FILE

OCL state-

ment

to indicate

the

number

of tracks required for

thc

$CCPDUMP

fiIE, AS WCII AS A

// TRACE TRACKS-NN

statement

to allocate the trace area.

(5704-SC2

only.) lf

you

anticipate running

the

assign-

ment

build

program

($CCPAS)

while

CCP is in the execu

tion phase,

the number

of sets anticipated

should be

increased

by one. This will increase

the initial disk

space

allocation

of

$CCPFILE

allowing the

CCP startup

phase

enough

space to copy certain

tables to the end of the

file. These tables

are

needed

by the

CCP

execuilon

phase.

With this

arrangement, the

rest

of

$CCPFILE

is

available

for $CCPAS

to perform

its functions

on the

f

ile.

(r

l

i;i ,f

rol

i;/ ,ISETS.

[,TERMS.

,F

LUN IT- ,F

LPACK-pack

[.TRK

LOC-n]

I

Default

for Program

Number 5704-SC2.

"Available

as

options

for Program Number

57O4-SC2.

r,ourvres-

{l r

[,DFILES- lsl

i;i

48K

64K

96K

I

f

r

| ,

FT'

/R1r

)"(

):: i

\lz./

128K

160K

192K

224K

256K

384K2

512K2

Generation

Stage 67

SETS-

{1I

ln I

The

SETS

operand

indicates

the

maximum

number

of

assign_

ment

sets

that

the

user

anticipates placing

into

$CCpFlLE.

Only

one

assignment

set

need

be

defined.

lf

space

is

avail-

able

at assignment,

it is

possible

to place

more

sets into

$CCPFILE

than

the value given

here.

This

value

simply

serves

as

a

guideline

in

allocating

space

for

the

file.

The

default

value

is

1. For

a minimum

$CCpFILE

the

value

is

1;the

maximum

is

25.

(rn

)

PROGS.

{-l

lnl

The PROGS

operand

indicates

the number

of user

programs

anticipated

for

bach

assignment

set

in

$CCpFlLE.

The

minimLtm

value

is

1;

the maximum

for

8704_SC1

is

255.

for

5704-SC2

is

999. The

default

value

is

10.

The

value given

here

does

not

place

any

actual

restriction

on

the

number

of user

programs

in

an

assignment

set, but

simply

serves

as

a

guideline

to

the

CCp

generation

in

allocat-

ing

space

for

$CCPFILE.

The

DFILES

operand

indicates

the

average

number

of disk

files

anticipated

for

each

assignment

set

in

gCCpFlLE.

The

minimum

is

0. The

maximum

for

program

Numoer

5704-SC1

is

50;

the

maximum

for

program

Number

5704-SC2

is

192.

The

default

value

is

b.

The

value given

here

does

not

place

any

actual

restriction

on

the

number

of disk

files

in

an

assignment

set,

but

simply

serves

as

a

guideline

to

the

CCp

generation

in

allocating

space

for

$CCPFILE.

Another

factor

to be considered

in

determining

this

operand

value

is

the

number

o't

l/FILE cards

that

can

be

entered

at

the

CCP

startup

(the

maxrmum

number

of

files

that

can be

used

in

any

CCP

run).

The

DSM

allowable

maximum

is

40

for Program

Number

5704-SC1,

and

1g2 for program

Num-

ber

5704-SC2.

lf more

than

the

maximum

number

of

files

is

defined

for

an

assignment

set when

starting

up

the

CCP,

the

excess

must

be

suppressed,

during

startup

by

the

system

operator.

For

a

minimum

$CCPF

I

LE,

a

value

of

0

can

be

specified.

TERMS.l1I

lnl

This

optional

operand

indicates

the

number

of terminals

anticipated

for

each

assignment

set

in

$CCpFlLE. The

minimum

is

1

(the

default

value)

and the

maximum

is

254.

The

value given

here

does

not

place

any

actual

restriction

on

the number

of terminals

in

an

assignment

set, but

simply

serves

as a

guideline

to

the

CCp

generation

in

allocating

space

for

$CCPFILE.

For

a minimum

$CCPFILE this value

is

1.

Iat

DUMPS.

1 .!-

!

Inl

The

DUMPS

operand

indicates

space

is

to be

reserved

in

$CCPFILE

(or

$CCPDUMP

for 5704-SC2)

for this

number

of dynamic

main

storage

dumps.

The

default

value

is

1.

The

minimum

value

is

1,

and

the

maximum

value

is

9. For

Program

Number

5704-SC2,

the maximum

value

is

9g.

When

a

user

program

is

abnormally

terminated

bv the

CCp

and

space

is

avaitable

in

$CCpFtLE (or

gCCpDUMp

for

5704-SC2)

for dumps,

the

supervisor

and

the

program

partition

in

which

CCP

is running,

are

written

to disk. lf

space for a complete

dump is not

available,

no

dump is

made. For

a

discussion

of the

dump to disk

f rom

forcible

termination, see l8M System/3 Model lS Communicatiot--

Control Program System Operator,s Gui<Je,

GC2l-76,lg. lf

the non-CCP program

partition

size is

not equal

to zero,

more

than

the

specif

ied

number

of dumps

can

be

taken. lf

$CCPDD is included

in

the

assignment

set

(only

necessary

for 5704-SC2)

$CCPDD

can

be used

to dump the

dr.rmp

area

while

CCP is

executing,

thereby

making room

for more

main

storage

dumps.

DFILES

{

g

}

(nl

COR E-

The

CORE operand

indicates

processing

unit size. The

default

and

minimum

values

are 48K for Program

Number

5704-SC1,

and 96K for Program

Number

5704-SC2.

This

operand value

indicates

the total main storage

size,

not

the size of the anticipated CCP

program

partition.

$CCPFILE

(or

$CCPDUMP

for 5704-SC2)

dynamic

main

storage dump

space

allocation is

based on this value.

At

startup,

the DSM

configured

size

of the

processing

unit

running

the

CCP is used

to determine

how manv

core

dumps

can be

taken durinq

the

run.

F LUN IT-

The FLUNIT operand

specifies

the unit on which,

during

generation,

the unit where

$CCPFILE

is to be

allocated.

There is no default parameter.

The value

specified here

need not be the CCP

production

pacK.

During

the

second

pass

of the

CCP

generation,

when

the

space

for $CCPFILE

is about

to be allocated

and its con-

tents initialized,

a

/l PAUSE

statement,

which is

provided

in the input,

permits

the

system operator

to verify

that

the

correct

pack

is

mounted

on this unit and,

if not,

to mount

it.

F

LPACK-pack

The FLPACK operand

specifies

the

pack

name upon which

SCCPFILE is to be allocated.

Therre is no default value.

485'

64K

3

g6K

t

1 28K

1 60K

192 K

224K

256K

394

K2

512K2

'Default

for Program

Number

51O4-5C2.

'Available for Program

Number

5704-SC2.

"Available

for Program

Number

57O4-SC1

onlv

TRK

LOC-n

The

TRKLOC

operand

can

be

used

to specify

the beginning

track

location

for

the

allocation

of

$CCPFILE.

lf this

operand

is

omitted,

$CCPFILE

is

allocated

in the

location

determined

by

the DSM.

DPTRAC-n

This

optional

operand

indicates

the

number

of

tracks that

are

to be

allocated for the

CCP trace

area within

the

CCp

dump f

ile

($CCPDUMP).

The

default is

0; the maximum

is

1000

(5704-SC2

only). The

minimum

non-zero

vatue

that is allowed

for

trace is

6

tracks.

$EMLA-MLTA

Support

hat You Must Know

Number

of MLTA lines

to be

supported.

lf MLTA is

to be

supported,

whether all

pro-

grams

will use translated

(EBCD

lC) data,

or

whether

some

programs

will process

data in

line transmission code.

The

$EMLA generation

control statement indicates whether

the

Multiple

Line Terminal Adapter

(MLTA) is to be used

by the CCP and, if so, the number

of MLTA lines.

This

statement is optional. lt need be

included

only if the

MLTA is to be

supported.

Either

the

MLTA statements

{$EMLA and

$EMLD), the BSCA

statements

($EBSC

and

$EBSD),

or the BSCC

statements

($ECSC

and

$ECSD)

must

be included.

Both BSCA and

MLTA can be soecified.

How-

ever,

BSCC

and

MLTA are

mutually

exclusive. Only one

SEMLA statement can

be

entered. lf included:

This

statement must

immediatelv

follow the

$EFIL

statement.

At least one

$EMLD statement is

required

to immediate-

ly follow this

statement

if the value

of operand LINES is

not 0.

JFiI

t5l

l*.'.o

|

.,'.,

",,".o',

l#l , I

Generation

Stage 69

LIN ES-n

The

LINES

operand indicates

the number

of teleprocessing

lines on

the user's MLTA. The

minimum

is 0. and

the

maximum

is 8.

By

implication,

0 indicates

no MLTA

support

is to be

generated

into

the CCP

and thus

no

$EMLD

control state-

ments

are allowed.

lf this value

is not

0, at least

one

$EMLD

statement

is required.

{ vsc

XLATE- tNo

The

XLATE operand specif

ies whether

programs

always

require

translation

of line

transmission

code to EBCDIC

on

input

and

translation from EBCDIC

to line

transmission

code

on output.

The

default is YES

indicating

that

translation

is

arways

used

in

MLTA

communications

operations.

NO

indicates

that translation

can sometimes

be suppressed,

via

a

specification

in

the assignment

stage TERMATTR

statement.

Regardless

of the value

of

this operand,

the

forcing

of upper

case translation

of input

data

is always

allowed in

the

TERMATTR

statement.

The value

NO requires

more

CCP

resident

support

than

the

value

YES.

Note: That

portion

of the CCP

that

contains the MLTA

IOCS

and buffers

($CC4#2)

must

be loaded

below 128K.

$EMLD-MLTA Devices

What You Must Know

MLTA terminal

devices

to be

supported.

MLTA line

transmission

code

for

each

terminal

t\/ np

The

$EMLD

generation

control

statement

indicares

an

MLTA

terminal

type to be

supported with

its features.

the

type

of line

the terminal

is

on,

and the transmission

code

required

on

the

line.

This

statement

is optional. lt need

be included

only if

the

MLTA

is

supported.

lf

the MLTA

is supported:

o At least

one

$EMLD statement is reouired.

o One

$EMLD statement is required

for

each

unique

ter-

minal-type/transmission-code

combination

(not

one for

each terminal).

o The first

$EMLD

statement must

immediately

follow

a

$EMLA

statement. Other

$EMLD

statements

must

follow

the first.

o Both

operands

on this

statement

are required.

$EMLD TYPE

1

050

1050D

2740

27405

2740C

27405C

2740D

2740DT

2740DC

2740D1C

2740M25

2740M258

2740M25C

2740M2SCB

27 41

2741D

CMCSTD

SYSTC

SYSTSC

SYSTDC

,XMCODE

coRR I

PTTCEBCD

i

PTTCBCD

\

70

1

050

1050D

2740

2740C

2740D

2740DC

2740DT

2740DTC

2740M25

TYPE-/ 274OM2SB

Terminal

Type Description

2740DC

2740DT

2740DTC

2740M25

2740

Model

1 with

longitudinal

redun-

dancy

checkinS

(LRC)

feature

on

a

dial

(switched

)

line.

2740

Model

1 with

transmit

control fea-

ture

on a

dial

(switched)

line.

2740

Model

1

with

transmit

control

and

longitudinal

redundancy

checking

(LRC)

features

on

a dial

(switched)

line.

274O

Model

2 with station

control

feature

on

a nonswitched

line.

2740M25C

2740M2SCB

27405

27405C

2741

2741D

CMCSTD

SYSTC

SYSTDC

SYSTSC

The

TYPE

operand

indicates

the

type

of

terminal

and

its

features

on

a

switched

(dial)

line

or

nonswitched

(nondial)

line.

The

specif

ication

of a

particular

terminal

type

in

a

$EMLD

statement

causes

the

control

logib

support

for that

terminal

type

to be

included

in

the

CCp.

Omission

of a

terminal

type

among

the

user's

$EMLD statements

indicates

support

for

that

type

is not

desireo.

The

following

table

explains

the nreaning

of each

terminal

type

code:

Terminal

Type Description

274OM2SB 2740

Model

2 with station

control

and

buffer

receive

features

on

a nonswitched

line.

2740M25C 2740

Model

2

with

station

control

and

longitudinal

redundancy

checking

(

LRC)

features

on

a nonswitched

line.

274OMZSCB 2740 Model 2 with station

contror,

longitudinal

redundancy

checking

(LRC),

and buffer receive

features

on a non-

switched

line.

27405 274O Model

1

with station

control

fea-

ture

on a

nonswitched

line.

274O

Model

1 with station control

and

longitudinal

redundancy

checking

(LRC)

features

on

a

nonswitched

line.

27405C

1

050

1050D

2740

2740C

2740D

1050

on

a nonswitched

line.

1050

on

a dial

(switched)

line.

2740

Model

1

without

extra

features

on

a nonswitched

line.

274OModel

1

with

longitudinal

redun-

dancy

checkinS

(LRC)

feature

on a non-

switched

line.

274O

Model

I without

extra

features

on

a dial

(switched)

line.

Generation Stage 71

Terminal

Type

27

41

2741D

CMCSTD

SYSTC

SYSTDQ

SYSTSC

Description

2741

on a nonswitched

line.

2741

on

a dial

(switched)

line.

Communicating

Magnetic

Card SE

LEC-

TR

lC

@

Typewriter

on

a dial

(switched)

line. The

CMCST

is supported

to the

extent

that it functions

identically

to a

2741D.

System/7

functioning as

a 2740 with

longitudinal

redundancy

checking

(LCR

)

feature

on

a nonswitched

line. The

System/7

is

supported

to the extent that

it functions

identically

to a 274OC.

Systemf functioning

as a

2740

with

longitudinal

redundancy

checking

(LRC)

feature

on a dial (switched)

line. The

System/7

is supported

to the extent that

it functions

identically

to a 274ODC.

Systemf functioning

as a 2740

with

station

control

and

longitudinal

redun-

dancy

checkins

(LRC)

features

on a

nonswitched

line. The System/7

is

sup-

ported to the extent that it functions

identically

to a 2740SC.

(coRR )

XMCODE-

<

PTTCEBCD>

lprrceco !

The

XMCODE

operand indicates the

MLTA

line transmis-

sion code that the

terminal in

this

$EMLD

statement will

use.

CO R R indicates

correspondence

code

PTTCEBCD

indicates

paper

tape transmission

code

EBCDIC

PTTCBCD

indicates

paper

tape transmission

code

BCD

(binary

coded decimal)

Specifying

a

particular

code

causes

generation

to include

the

line-code-to-EBCDIC

(upper

and lower

case) and

EBCDIC-

to-line-code translation

modules when

copying modules

to

the

production pack.

The

following

table indicates

the

valid

values

of XMCODE

for each

terminal type

and

its features:

Terminal

1

050

1050D

2740

2740C

2740D

2740DC

2740DT

274ODTC

2740M25

2740M258

2740M25C

2740M2SCB

27405

27405C

2741

2741D

CMCSTD

SYSTC

SYSTDC

SYSTSC

Valid

Transmission

Code(s)

)

i PrrcEBcD

The

3767

terminal

can be

used

under

CCp

to simulate

the

following

MLTA terminals: 2740C,

274ODC,

2740M2SC8,

27405C,

2741, 2741D.

The

only restriction

on generation

is

that the

CORR

and

PTTCEBCD

operands

are

the only valid

transmission

codes

when

the 3767

is used

to simulate

one of the

terminals

listed

above.

(For

assignment,

see

the MLTATERM

statement under Assignment Stage.l

The

5100

portable

computer

can

be

used

under

CCp

to

samulate

the following

MLTA terminals: 2741 and 2741D.

The

only restriction

on

generation

is that the

CORR and

PTTCEBCD

operands

are the

only valid

transmission

codes

when

the

5100 is

used

to simulate

one

of the

terminals

listed

above.

(For

assignment,

see

the MLTATERM state-

ment under Assignment Stage.

)

CORR

PTTCEBCD

PTTCBCD

COR R

PTTCEBCD

PTTCBCD

CORR

PTTCEBCD

)

$EBSC-BSC

Support

The

$EBSC

generation

control

statement

indicates

general

specif

ications

concerning

binary

synchronous

communi-

cations

(BSC)

support.

This

statement

is

optional.

lt need

be included

only

if

the

Binary

Synchronous

Communications

Adapter

(BSCA)

is

supported.

The

BSCA

statements ($EBSC

and

gEBSD).

the

MLTA

statements ($EMLA

and

$EMLD),

or (for

Program

Number

5704-SC2

only)

the

BSCC

statements

(SECSC

and

$ECSD) must

be

inctuded.

Both

MLTA

and

BSCA

can

be

specified.

However,

BSCC

and

MLTA

are

mutually

exclusive.

Only

one

$EBSC

statement

can

be

entered.

lf included:

This

$EBSC

statement

follows

the

last

$EMLD

srare_

ment

if MLTA

support

is

included.

lf MLTA

support

is

not

included.

this

statement

immediately

follows

the

$EFIL

sitatement.

At least

one

gEBSD

statement

is

required

to immediately

follow this

statement

if the

value

of the

BSCA

operand

rs

other

than

zero.

hat You

Must

Know

BSCA

lines,

line

features,

and

BSC

control

logic

to

be included

in

the

CCp

support.

BSCA

line

transmission

code for

each

termina

-_ type.

ls

the

display

adapter

(DA)

supportedz

Generation

Stage 13

$EBSC

t,MP.

[,R

HCSEP-

[,EBCDIC-

[,XPRNCY

(q)

BSCA-(

1 )

(z)

The BSCA

operand

indicates

the number

of BSC

adapters

(lines)

the CCP

supports. The

minimum (and

default) is

0; the maximum

is 2.

A value

of 0 indicates

that BSC

support is not included,

in which case,

no

other operands

should be

specif

ied,

(if

specif ied,

they must

not have

other than defautt

values).

Also,

no $EBSD

statements

are

allowed.

A value

of 1

or 2 indicates

that BSC

control logic

support

is included

in

the CCP.

DA

{fi'l

The

DA operand indicates

whether

the

display

adapter is

supported by CCP. DA-YES

is valid

only if the value

of

operand BSCA

was

1 or 2. The default

is NO. (See

Support of the Display Adapter at the end of this chapter.)

DIAL

The DIAL operand

indicates whether

a

BSCA dial

(switched

line) network

is

to be supported

bV the CCP. The default

is NO.

{c'} ,r.D'|AL.

{['] '

{['] ,t,cs

{ff} ,

\ei

IBSCA-

11 >

I

f z !

,.rr-JYES\ i

tNO J

f

vesf

,

tNOJ'

f

vesl

,

1*o

i'

I

YESt

INO J

J

YESI

tNo

f

DIAL-YES is

valid

only if the

value

of operand

BSCA

was

1

or 2, ancl

the 3275,3735,37,41',

CpU or processing

units

are

su

pported.

YES

includes

the

support

ancl NO excludes

it.

PP I YES\

f

No I

The PP

operand

indicates

whether

a BSCA

point-to-point

(leased

or private)

network

between

a 3741

or processing

units is

supported

by the CCP.

PP YES

is valid

only if

BSCA-1

or

IISCA-2

was

specified.

YES

inclucles

the

support

anrl

NO

excludes

the supporr.

MP lYES\

tNo

(

The MP

operand

indicates

whether

a

BSCA

multipoint

tributary

(leased

or

private)

rretwork

is

supported

under

the

CCP.

This

means

the

System/3

with

the

CCp is

polled

and addressed

by

another

computer.

MP

YES

is valid

only if BSCA-1

or BSCA-2

was

specif ied.

YES

includes

the

support

anrJ NO

excludes

the support.

The

default

is NO.

The CS

operand

indicates

whether a BSCA control station

(leased

or private)

network

is supported

under

the

CCp.

This

means

the

System/3

with the CCp

polls

and

addresses

other

terminals.

CS-YES

is valid

only if BSCA-1

or BSCA-2

was

specified.

YES includes

the

support

and NO

excludes

tlre suppon.

CS-YES

must be

specif

ied when using

a 3271

control unit

to control

display

terminals

or when

using

a

3275

display

station

with nonswitched

lines.

The

default

is

NO.

cErMSG.[l5s]

The

GETMSG

operand

indicates

whether

the

BSCA

control

logic

to get

a message

should

be included

in the CCp (see

IBM System/3 Communications Control program program-

mer's Reference Manual . GC21

-7

STgl .

YES

includes

the

f

unctional

capability to read

(in

one user

requested

operation) f

rom start-of-message

to EOT. For

example,

one

could read f

rom many

separated

f

ields on

the display

screen

of the3277 and

receive

all

the oata

as

one

continuous

string. GETMSG

YES

is

required

if

FORMAT-YES

is

specified on the

$EFAC statement

or if

program

request under format is used. (See

the PRUFLNG

parameter

of the PROGRAM

statement

in

the assignment

stage.

)

The

default is NO and excludes the

support.

The ITB

operand

indicates whether BSC

intermecliate-

text-block

characters will be used in

communicatinq with

BSC

terminals.

YES

on this

operand is

valid

only if BSCA

1 or BSCA-2

was

specif

ied. YES includes

the control logic to hanclle

fixed

length block

records with intermediate

text-block

characters. This

control logic

is

used

primarily

for batch

transmission

devices,

such as CPUs.

The default

is NO and

excludes the

support.

R ECSEP-

The RECSEP

operand

specif

ies

the

hexadecinral

recoro

separator

byte

for BSC

transmission. This feature ts

useo

primarily

for batch

transmission

devices,

such as CPUs,

3741,

or

3735

terminals.

The

user can

specify

a

record

separator

byte

as any rwo

hexadecimal

digits. When

separator bytes

are used,

tl're

most

commonly

used byte is hexadecimal

1E which is

the

clefault

value. The

record

separator byte

specitred here is

the

character

used in

every instance

of variable

length

block records.

aqr'r- /YESI

"""" )

No

r

The

ASCII

operand

specifies whether

BSCA

line

1 andlor

line

2 uses

ASCII

transmission code.

YES

includes

the capability

of translating between

ASCII

transmission

code

and EBCDIC

code used

by programs

rn

the

system.

lf BSCA

is not 0,

either

ASCII-YES must

ne

specified,

or EBCDIC-NO

must rrot

be specified.

The default

is NO

and excludes

the translation

f

or ASCII

code.

" {il5'}

frei

i;/

.'{G'}

Generation Stage 75

EBCD'C{H}

The

EBCDIC

operand

specifies whether

BSCC

line

1

and/or

line

2

uses

EBCDIC

transmission

code.

When

no ASCII

or

EBCDIC

operand is

specif ied

and

BSCA

is not 0, EBCDIC-YES

is

assumeo.

The

default is YES.

R

ESPO

L

The RESPOL

operand

specifies

whether

BSC

polling

modules

are

main

storage

resident rather

than executed

as transients.

YES

makes

the

polling

routines

resident. NO

specif ies

polling

is done by transients. There

is no difference rn

function

in the two methods. Main

storage

resident

polling

is used

only for improved response

time. The user

can use this feature

(main

storage

resident

polling)

when

his

programs

can be interactive

with manV

terminals on

one line.

YES

is valid

only if BSCA-1

or BSCA-2

was

specified in

this same

control

statement.

lf RESPOL YES is

specif ied,

CS-YES must

be in effecr.

Specifying

NO

or allowing

this operand to default may

cause

performance

to degenerate in

the other

program

partitions

due

to disk

reads

of the

polling

transients.

The default

is

NO.

AUToRS

{J:s}

The

AUTORS operand

specifies whether the BSC

multi-

point

tributar.y

(non

control station)

support

to auto-

matically

send

a

negative

response

to polling

and

address-

ing sequences

is included

in the

CCP.

This

will be in effect

only after the

first

data

transfer has

completed

and

will

remain

in

effect until

a subsequent

BSCA l/O operation

or a

MLMP CLOSE

operation is

issued

to the line. This

allows the CCP to respond faster

and

avoid

possible

timeout

problems

on the

CPU that is

polling

or addressing

your system.

xPRNCY

{J5s}

YES

causes the

proper

module

to reside in main

storage.

NO means

that no response

is

given

to the POLL/ADDRESS

request

from the

control station

until

the

program

is

loaded under

CCP. Thus

timeouts can occur at the control

station.

The

user

should

specify

YES

if he

expects

serious timeout problems.

lf AUTORS-YES

is

specified,

MP-YES

must

be in effect.

TYPE-CPU

must be specified on a

$EBSD

generation

control

statement. The

default

for AUTORS is NO.

The XPRNCY

operand specif

ies whether

the

text trans-

parency

feature

is

used by application

programs

run

under

control of the CCP.

YES

includes

support

for text-transparency.

NO excludes

tne

support.

lf YES is

specified,

EBCDIC-NO Inust not

be

specified

in

this $EBSC statement.

The ciefault

is NO.

I VtrqI

rNrPoL

i N;"1

This keyword

specif

ies whether to include support

for

timer-initiated

interval

polling. The default

is NO. Interval

polling

allows

the processing

unit clock to stop

between

requests

to poll BSC

terminals

during

periods

of low

activity. All terminals are

polled

continuously

until

all

terminals on the line

have responded negatively

for the

time specified

in

the POLTIME

parameter

at the assignment

stage.

When

a positive

response is received

from any BSC

terminal,

interval

polling

is

suspended and

continuous

polling

is resumed

until another

specif

ied

period

of only

negauve responses.

Note: lnterval

polling

is not recommended

on a system

with MINRES-YES

(keyword

$EGEN). lt is not

recom-

mended because

the loading of the additional non

resident

r;ystem routines

causes

the

processing

unit clock to run

contanuouslv.

(5704-SC2

only)

The PORT

operand indicates

whether to include

the

facilitv.

YES

includes

the logic

to handle

programs

written

to com-

municate

over

BSCA

lines. Program

Number

5799-WNK

(Channel-Connected

Systems

RPO) is not needed

to support

this

facility.

The

default is NO

and

excludes

the

support.

fYES)

l*q

i

PoRr

{c'}

76

$EBSD-BSC

Devices

What You Must Know

BSCA

terminal

devices

to be

supported.

The

$EBSD

generation

controt

statement

indicates

a

BSC

device

type that the CCp is

to support.

This

statement

is

optional. lt need

be

included

onlv if

BSC

is to be

supported.

lf BSC

is to be

supported:

. At least

one

$EBSD statement

is required.

o One

$EBSD

statement

is

required

for each

unique

terminal

type.

. The

first

$EBSD statement

must

immediately

follow

a

$EBSC statement.

Other

$EBSD statements

immedi-

ately

follow the first. Multiple

$EBSD

statements

may

be

in

any

order.

o The 3275M1 and 3275M2 require

either

control station

or switched

line

support

(CS-YES

or DIAL-yES on the

$EBSC statement).

Other

3270

type

terminats

require

control station line

support (CS-yES

on the $EBSC

statement).

. The

operand

on this

statement

is

required.

3275M1

3277M1

3284M1

3286M

1

3275M2

321tM2

3244M2

3286M2

3141

CPU

The TYPE

operand

specif ies

a

particular

BSC

terminal

type

to be

supported.

Specif

ication

of a

terminal

type

causes

the necessary

control logic

to be included

into

the

CCp

to

support

that type. On individual

$EBSD

statements,

any

or all

of the

above

terminal

types

can be specif

ieo.

The 3272 is

not supported

by the CCP.

M1 indicates

a 480-byte

buffer

terminal

and M2 indicates

a 1920-byte

buffer

terminal

of the 3270

system

series.

3735

indicates

the

3735 programmable

terminal. For

a

description

on how to create

and

transmit forms

descriptor

program (FDP), see

l8M 3735 programmer's Guide,

GC30-3001 ; and IBM 3735 Support Program Coding

Manual.

GC21-5096.

CPU indicates

support

for all CPUs

capable

of receiving

or

transmitting in BSC (see

IBM System/3 Communications

Control Program Programmer's Reference Manual,

GC21-7579).

3741 indicates

the

3741 Data

Station Models

2 and

4 (see

IBM 3741 Data Station Reference Manual, G421-9183).

Note: Fhe following

terminals

are

supported

in

compatibility

mode. Specify

the

appropriate entry

for the

terminal

type

as

follows:

Terminal Type Entry

3276

3278

3287

3288

3289

5231-2

3277M2

3284M2

or 3286M2

3286M2

3741

1 3275M1

I szttrut

I szs+vrr

\ 3286M1

I 3275M2

rYPE-\ 3277M2

13284M2

I zzeavz

I 373s

\ 3741

\ CPU

qtraen TYPE.

\

Generation

Staqe 77

$ECSC-BSCC

Support

(5704-SC2

only)

What You Must Know

BSCC

lines, line features,

and BSCC

control

logic

to be included

in

the

CCp

support.

BSCC line

transmission

code for

eacn

terminal

type.

The

$ECSC

generation

control

statement indicates general

specif

ications

concern

ing

bi

nary

synchronous

communica-

tions

controller

(BSCC)

support.

This

statement

is

optional. lt need

be included

onlV if

the binary

synchronous

communications

controller

(BSCC)

is

supported.

BSCC

and MLTA are mutuallv

exclusive

within a single

generation.

Only one

$ECSC

statement

can

be entered.

lf included:

. The

$ECSC

statement follows

the last

$EBSD

statement

if BSCA support

is included.

lf BSCA

support

is not

included,

this statement

immediately

follows

the

gEFIL

statement.

o At least

one

$ECSD

statement

is required

to immediately

follow this statement

if the

value

of the BSCC

operand

is

other than zero.

'*t"- -,-.rber 5704-SC2

only

I6

BSCC

The

BSCC

operand indicates

the number

of BSCC

adapters

(lines)

that

CCP supports. The minimum

(and

the

default)

is

0; the maximum is

2.

A value

of 0 indicates

that BSCC

support is

not included.

In

this case,

no

other operand should

be

specified

(if they

are specif ied,

they must

not have

other

than

the

def

ault

value).

Also, no

$ECSD

statements

are allowed

A value

of 1 or 2 indicates

that BSCC

control

logic

support

is included

in

CCP.

GETMSG

{tr}

The

GETMSG operand indicates

whether

the BSCC

control

logic

to get

a message

should be included

in the CCP

(see

IBM System/3 Communications Control Program Program-

mer's Reference Manual

, GC21 7579).

YES

includes

the

functional

capability

to read

(in

one user

requested

operation) from start-of

-message

to EOT. For

example,

one could read

from many

separated

f ields

on

the display

screen of the3277 and

receive

all the

data as

one continuous

string. GETMSG YES

is required

if

FORMAT-YES

is specif ied

on the

$EFAC statement

or if

program

request

under

format is used.

(See

the

PRUFLNG

parameter

of the PROGRAM

statement

in

the assiqnment

stage.

)

The

default

is

NO and excludes the

support.

ITB-

The ITB operand indicates

whether BSCC

intermediate-

text-block

characters

will be used

in communicating

with

BSCC

terminals.

ITB-YES

cannot

be

specified

if

XPRNCY-YES

is specified.

YES

on this operand

is valid

only if BSCC-1

or BSCC-2

was

specified. YES includes

the control logic

to handle f ixed

length

block records

with intermediate

text-block

characters.

This

control

logic is

used

primarily

for batch

transmission

devices.

such

as

CPUs.

The

default is NO and

excludes

the support.

1+f

tz)

lYEs \

tNo ,

RECSEP.

The

RECSEP

operand

specifies

the hexadecimal

record

separator

byte

for BSCC

transmission.

A CCp

generated

to

support

BSCC

terminals

always

includes

code for

handling

variable

length

records.

This

code

is used

primarily

for

batch

transmission

devices,

such

as

CpUs,3741.

or

3735

terminals.

The

user

can

specify

a

record

separator

byte

as

any

rwo

hexadecimal

digits.

When

separator

bytes

are

used,

the

most

commonly

used

byte

is hexadecimal

1E

which is

the

default

value.

The

record

separator

byte

specified

here is

the character

used

in every

instance

of variable

length

block

records.

ASCI I

The

ASCII

operand

specifies

whethelr

any CCp

supported

BSCC

line

uses

ASCII

transmission

code.

YES

includes

the

capability

of

translating

between

ASCII

transmission

code

and EBCDIC

code

used

by

programs

in

the system.

lf BSCC

is not

0,

either

ASCII-yES

must

be

specified,

or EBCDIC-NO

must

not

be specified.

The

default

is NO

and excludes

the

translation

for

ASCII

code.

(vps)

EEcDrc

j ,o I

\/

The

EBCDIC

operand

specifies

whether

any

UCp supported

BSCC

line uses EBCDIC

transmission

code.

When

no

ASCII

or EBCDIC

operand

is

specified

and BSCC

is not

0,

EBCDIC-YES

is

assumed.

The

default

is YES.

The

XPRNCY

operand

specifies

whether

the text

transpar-

ency

feature

is used

by

application

programs

run under

conlrol

of

the CCP.

YES

includes

support

for

text-transparency.

NO

excludes

tne

support.

lf YES

is

specified,

EBCDIC-NO

must not

be

specified

in

this

$ECSC

statement.

The

default

is NO.

INTPOL.

This

keyword

specifies whether

to include

support for

timer-

initiated

interval

polling.

The default is NO. Interval

polling

allows the

processing

unit

clock to stop

between requests

to

poll

BSCC

terminals during

periods

of low

activity.

All

terminals

are

polled

continuously until

all terminals

on the

line have responded

negatively for

the time

specif ied

in the

CSPOLTIM

parameter

at the

assignment stage.

When

a

posi-

tive response

is received

from

any BSCC

terminal,

interval

polling

is suspended

and

continuous

polling

is resumed

until

another specified

period

of only

negative

responses.

(5704-SC2

only)

The PP

operand

indicates

whether

a BSCC

point-to-point

(leased

or private)

network between

a System/3

and a

processing

unit (or

3741)

is

supported

by CCp. pp-yES

is

valid

only if BSCC-1

or BSCC-2 was

specified.

yES includes

the

support

and

NO excludes

the support. The

default

is NO

(vrc t

cS-1* | (5704-SC2onty)

The CS operand

indicates

whether a BSCC control station

network

is

supported

under

CCP. This

means

that

tne

System/3

with CCP

polls

and

addresses

terminals.

CS

yES

is

valid

only if BSCC-1

or BSCC-2

was

specified.

CS

yES

must

be specified

when using

a3271control unit

to control

display

terminals

or when using

a 3275

display

station

with

nonswitched

lines.

YES includes

the

support

and

NO

excludes

the

support. The

default

is YES.

(5704-SC2

only

)

The PORT

operand

indicates

whether

BSCA

portline

facility

is to be

supported

by CCP. YES

includes

the logic

to handle

programs

written

to communicate

over

SIOC

lines.

Program

Number

5799 WNK (Channel-Connecreo

Systems

RPO)

is not needed

to support

this

facilitv. The

default is

NO

and excludes

the

support.

.r:g\

t"" J

lvrs\

tNo

,

JYES\

tNo

(

PP. 1

YES

\

tNo I

PoRr.{G'}

XPRNCY

{fi'}

Generation Stage 79

$FCSD-BSCC

Devices

What You Must Know

BSCC

terminal

devices

to be supported.

The

$ECSD

generation

control

statement

indicates

a

BSCC

device

type

that

the

CCp

is

to support.

This

statement

is

optional.

lt need

be included

only

if BSCC

is

to be

supported.

lf BSCC

is

to be

supported:

o At least

one

$ECSD statement

is

required.

o One

$ECSD statement

is required

for

each unique

terminal

type.

o The

f irst

$ECSD

statement

must

immediately

follow

a

$ECSC

statement.

Other

gECSD

statements

rmmediately

follow

the f irst.

Multiple

$ECSD

statements

mav

be in

anv

order.

. The

operand

on this

statement

is required.

(

'""

I

3275M1

3277M1

3284M1

3286M1

3275M2

3277M2

3284M2

3286M2

3735

3741

CPU

The

TYPE

operand

specifies

a

particular

BSCC

terminal

type

to be

supported.

Specification

of a

terminal

type

causes

the necessary

control logic

to be included

into

the

CCP

to support

that

type.

On individual

$ECSD

statements,

any

or all

of the

above

terminal

types

can

be specified.

The

3272

is not

supported

by the

CCp.

Ml indicates

a

480-byte

buffer

terminal

and M2

indicates

a

1920-byte

buffer

terminal

of the

3270 system

series.

3735

indicates

the 3735

programmatrle

terminal.

For

a

description

on how

to create

and transmit

forms

descriptor

program

(FDP),

see l8M 3735

Programmer's

Guide,

GC30-3001;

and IBM 3735 Support Program

Coding

Manual,

GC21-5096.

CPU indicates

support for

all

CPUs capable

of receiving

or

transmitting

in BSCC

(see

IBM System/3

Communications

Control Program

Programmer's

Reference

Manual,

GC21-75791.

3741

indicates

the 3741

Data

Station Models

2 and 4 (see

IBM 3741 Data Station Reference

Mitnual

, GA21-9193).

Note: The following

terminals

are supported

in compati-

bility mode.

Specify the

appropriate

entry

for

the terminal

type

as

follows:

Terminal

Type

3276

3278

3287

3288

3289

5231-2

Entry

3277M2

3284M2

or 3286M2

3286M2

3741

$ECSD

(

l

'""

I

3275M1

3217M1

3284M1

3286M1

3275M2

3277M2

32A4M2

3286M2

J /J5

3741

nDt I

80

What You

Must

Know

Disk unit

and

pack

name

on

which

disk

system management

resides

(F1

or R1).

Disk

unit

and

pack

name

on which

tne

CCP is

generated.

Disk

unit(s)

and

pack

name(s)

for

work

file

space

during

generation.

Disk

unit on

which

the macro

processor

and

the

distribution

CCP modules

reside.

$EG

EN-CCP

Generation

Stream

The

$EGEN

generation

control

statement

indicates

wnere

various

unit

and

pack

names

are

located

during

the

CCp

generation, permits

the user

to specify

the minimum

size

of resident

code,

and determines

the input

medium

used

during

step

6 of

generation.

This

statement

is

always

required.

lt must

be

the last

of

all

$E

generation

control

statements.

Only

one

$EGEN

statement

can

be entered.

The

disk units

used

in

a CCP

generation

are not fixed,

as

in

a

generation

of DSM.

Any

available

unit

can

be used

to

hold

any

pack

required,

if

:

o The

distribution

pack

remains

rnounted

on the

same

unit

throughout

generation.

. The

system

pack

remains

mounted

on

the same

unit

throughout

generation.

o The

distribution

pack

is

not

used

as

the receiving

pack

for

any relocatable

or load

modules

produced

bv

generati

on.

Generation

Stage 8l

$EG EN DSUN

IT

CCUN

IT.

WKUNIT-

WKPACK-

Ir\4tNRES- I [,cnno

D1

D2

D3

D31

D32

D33

D34

D4

D41

D42

D43

D44

[,DPPACK IPACK ll'

I D2D2D2\

J

'

For

Program

Number

S704-SC2

only

The DSiJNIT

operand

specifies

rvhich

disk

unit (F1 or R1)

contains

the DSM

during

the

CCP

generation.

This

is

the

unrt

trom which

the user

loads

the DSM

(performs

lpL).

It is

assurned

that

the DSM

is

properly

generated

on the

system

pack,

including

the

appropriate

MLTA and/or

BSCA l/O macros

and

subroutines.

Either

of the values

is

valid. There

is

no

default.

The

CCUNIT

operand

specifies

the

production

disk

unit

upon

which

the

generated

CCp

nrodules,

except

for those

wlrich

directly

support

application

program

preparatron

(specif

ied

in the

$EPLG

statement),

are to be

generated.

Any of the

values

is

valid. There

is no

default. This

unit

can

be the

same

as that

specified

for DSUNIT.

6l

I

\

(

The

WKUNIT operand

specif ies

the disk

unit(s)

upon

which

work files

are

to be

allocated

during

the

CCp

generation.

The

value

for

unit

can

be

R

j, F1

, R2, F2,

D1,

D2,

D3,

or D4; tor Program

Number

5704-SC2,

D3l, D32,

D33,

D34,

D41

, D42,

D43,

and D44 are

atso

vatid. There

is

no

default

value.

Either

the

single

unit form or the

triple

unit

form must

rre

used.

The

same form must be

used for the WKpACK

operand.

lf the single

unit form is

used,

$SOURCE,

$WORK, and

$WORK2

are allocated

on the

same

(specif

ied)

unit

whenever

they

are required.

{

F1

R1

F1

R1

F2

R2

unrt

'unit,unit,unit'

pack

'pack,pack,pack' I:rl

l;i)

,DIUNIT.

fYes )

i*-/ '

YES

NO

wr<ururt

I'nit \

(

'unit,unit,unit'J

DS.rNrrt'*1

)

..,^,I!]I

l

;;\

l{ the triple

unit form is used, the first

unit indicates

where

$SOURCE

is allocated

whenever

it is

required. The

second unit indicates where

$WORK is

allocated whenever

it is required.

The

third unit indicates

where

$WORK2 is

allocated

whenever it is required.

The

work space

required

is:

o For

$SOURCE: 170

tracks

. For

$WORK: 50

traq<s

o For

$WORK2: 50 tracks

The

time required for generation

can be

significantly

reduced if these f

iles

(particularly

$SOURCEI

can be

allocated

on a

pack

other than the

CCP distribution

pack,

especially

if that pack

can be on a unit served by a

separate

disk

arm.

wrpacr-{Pttk \

('nack,oack,pack'J

The WKPACK

operand specifies

the

pack

name(s) upon

which

the work files

are

allocated

during

the

CCP

genera-

tion. The

value for pack

is the

appropriate user's

pack

name. There

is no default value.

Either

the single

pack

form

or

the triple

pack

form

must be

used. The

same

form

must be

used

as

for

the

WKUNIT

operand.

lf the single

unit

form

was

used

for

WKUNIT,

then

the single

pack

form must be

used here. lf the triple

unit form

was used for WKUNIT,

then the

triple

pack

form

must

be

used here. lf the

single

pack

form is

used,

$SOURCE,

$WORK.

and

$WORK2

will

all be allocated

on

the

same

(specif

ied)

pack

whenever

they

are

required.

lf the triple

pack

form is used, the first

pack

indicates the

pack

name for

allocation of $SOURCE

whenever it is

required. The

second

pack

indicates the

pack

name

for

allocation

of $WORK

whenever it

is required.

The

third

pack

indicates

the

pack

name for allocation

of

$WORK2

whenever it is required.

The

DIUNIT operand

specifies the disk unit

which

contains

the macro

processor

and the distribution

CCP modules

as shipped

from

the IBM Program

Information

Department

(PlD).

The value

must

not

specify

a

unit

that is

the

same

as

that

specified

for CCUNIT, nor

the

same

as any specified

for PPUNIT

in

a

$EPLG statement.

The

MINRES operand specifies whether

the

size of the

resident

CCP control

routine is made

as small as

possible.

YES indicates

that the resident

control

routine is made

as

small

as

possible.

This

is done

by making

certain

communi-

ions handling

routines

transient rather

than resident.

y'y'ote.'

Interval

polling is not recommended

on a system

with MINRES-YES

(keyword

$EGEN). lt is not

recommended

because

the loading of the additional non-

resident

system routines causes the processing

unit clocl<

to run

continuously.

.ARD

{#}

The

card operand

specifies the input medium

to be

used

during

Step

6 of the

CCP

generation.

YES,

the

default

value,

indicates

a card-oriented

generation.

In this case,

the

complete

job

stream

is

punched

during

generation.

After

being

punched,

the

job

stream is

entered via

the card reader

to complete

the

generation.

NO indicates

a cardless-oriented

generation.

DPUN lT (5704-SC2

only

)

I

This

operand

specifies

the

unit

on which the

CCP dump

file

($CCPDUMP)

resides.

The

default is D2

(5704

SC2

only).

DPPACK

(5704-SC2

ontv)

t

This

operand specifies

the

pack

on which the

CCP

dump

file

($CCPDUMP)

resides. The

default is D2D2D2.

^

When running

a card

generation,

the

punched

cards

for DPUN lT

and DPPACK

from the

sample deck should

be

fitted

in. lf the

default is to be taken,

the cards

should be

pulled

from the

sample

deck and

left out for step 3 of the

generataon.

MTNRES.{ffi'}

DruNrr.l

(

F1

R1

F2

R2

)

Generation Stage 83

CCP

PROGRAMS

USED IN GENERATION

Generation

utility ($cc1PP)

The

generation

utility program

($CC1PP)

is used

in step 5

of the

CCP

generation

to print

any

error

messages,

or if

there

are

no

errors, to print

and

provide

the input

stream

for the second

pass

of generation.

For

a card-oriented

generation,

the

output

from $CCl

PP

can be

punched

on either

the MFCM, MFCU,

or the 1'442,

whichever

is the standard

punch

device

for the

system

on

which

generation

occurred.

SGP Generator

($CGxxx)

The system

control

program

generator

($CGDRV

and

phases)

is used in

the

second

pass

of

generation

{step

6)

to generate:

o The initialization

data for

$CCPFILE.

o The

execution

time

re$ident

load modules

($CC4#1

,

$CC4#2,

and,

if BSCC is

supported,

$CC4#M).

o A null

user security information module if

a user

security

routine

is userl.

o A vector table,

$CC4\'T.

Initialize

Assignment File Build

($CCIBF)

The

initialize assignment

file

build

program

($CC1

BF)

allocates

and initializes the

$CCPFILE

file in step

8 of the

CCP

generation

to prepare

the

$CCPFILE

file for the

assignment stage.

Reexecution

of $CC1

BF

(after

proper

scratching of

$CCPFILE)

reinitializes

$CCPFILE

to

the

state rt was

before

the

first

assignment

set

was entered.

By

changing

the unit

and

pack

name

on

the

l/FILE card

of $CClBF, $CCPFILE

can be initialized

on another unit

and

pack.

By

changing the

TRACKS

parameter

of

the

// FILE

card, the

size of the

new

$CCPFILE

can be

changed.

Multiple

$CCPFILEs

can

exist

if each is on

a

separate

pack.

Selection

of the unit for the appropriate

$CCPFILE

can be made €rt

startup.

Initialize Trace/Dump File

($CClDPl

(Program

Number

5704-SC2

only)

The initialize

CCP dump

file

program

($CC1DP)

allocates

and initializes the

$CCPDUMP

file

for trace and storage

dumps. The

$CCPDUMP

file consists of a directory,

a

trace

dump

area, and

a main storage

dump area.

The file

may

reside in

any

of the

main data

areas,

and

its location

may

be designated during

either

CCP

generation

by the

specification

of the

DPPACK

and DPUNIT operands

of the

$EGEN

macro or

CCP assignment

by the specif ication of

the

DUMPUNIT operand on the

// SYSTEM statement.

The

track

space

desired

for

the

trace

area

may be

specified

during

generation

by the

DPTRAC operand

on the

$EFIL

state-

ment.

During

the

generation

stage,

you

can

calculate

the

necessary

track space

for

storage dumps

by

analyzing

the

CORE and

DUMP

operands

of

the

$EFIL

statement.

CCP

generation

creates

and

executes the

proper

procedure

for

$CCPDUMP

initialization.

lf

the

user wishes to

generate

his

own

procedure,

he can use

the

following example:

II LOAD

$CClDP,R1

I I F I

LE NAM

E.$CCPD UM

P,

UN

I

T.D2,P ACK.D2D2D2,

R ETAIN-P,TRACKS-97

// RUN

//

TRACE TRACKS-10

The

// TRACE statement

identifies

to $CCPI

DP the

num'

ber

of

tracks desired

for trace.

The remaining

86

tracks

are

allocated

for

main

storage

dumps.

The

86

track

calculation is as

follows:

f/ \ I (512Ksystem, )

| | (512

x

4)

+llx 21148=86

{ }

L\'- - -/"1 - -- t2dumpsneededj

[(f

r.," storase

in K x

4)

+)x numuer ot ou.nll+a

Note: ln

addition to the

total

needed

for trace

and

storage

dumps,

the user

should

specify one

track on

his

// FILE

OCL

statement; this

specification

allocates

the necessary

space

for

$CCPDUMP

directory

information.

Note: To change the

size

of a

$CCPDUMP

f

ile, delete

it

and

recreate it using

$CC1DP

as

outlined

above,

SOURCE MODULES

USED

IN

GENERATION

In

addition to the

source library

modules

used

for generating

the execution time

resident

code

or supporting

transients,

the following

source library members

are

present

on

the

distribution

pack:

$CGSST Sample

assignment

control

statements

-

card less

$CG1G1 Cardless

CCP

generation

instructions

$CGIGG Sample

$E

macro

statements

- cardless

$CGlGl Cardless

CCP

generation procedure

$CG1G3 Cardless

CCP

generation procedure

$CG

1G4 Cardless CCP

generation procedure

$CGlG5 Cardless

CCP

generation procedure

$CGSMP CCP

sample

generation

deck

$CGEND Instructions

to the user at the end of

generation

$CGSET Sample assignment input deck

and sample

startup deck

for

the

installation verification

program

(CCPIVP)

GENERATION

CONSI

DERATIONS

One of three

versions

of BSC

support for CCP

can be

selected

during

the

CCP

generation process:

o Full

BSC support for all

line

configurations

and BSC

devices.

. 3270

only support

for all

line

configurations.

o Privileged

3270

only

support

for faster

response.

lf other than 3270

devices

are specified

by the

$EBSD

statements,

full BSC support is

generated.

lf only 3270

devices

are specified by the

$EBSD

statements, two versions

of BSC IOS

can be supported:

. 3270 only

support,

which

saves

approximately

1K bytes.

o Privileged

3270

only

support,

which

saves approximately

.75K

bytes

and

gains

faster

response

times

during heavy

usage.

Privileged

3270

only support is recognized

only

if MINRES-NO

($EGEN

statement),

RESPOL-YES

($EBSC

statement),

and

327O

only devices

($EBSD

statement)

are

requested,

Support

of the Display

Adapter

Support

of

the Display

Adapter

on

your

system requires

special

CCP

generation

and

assignment

considerations.

The

following

are the

generation

and

assignment

statements

that

have required

values

for

a system

that

supports

the

display

adapter

only

(PRUF

and DFF included).

The

underlined

parameters

are required

values for

the Display

Adapter.

lf

a

parameter

is not

given

or

not

underlined,

it is not

specif-

ically required

nor

has

any

effect

on

the display

adapter

support.

Some

of the

parameters

default

to the

value

shown

{for

example.

MP-NO).

Generation

$EBSC BSCA-11.OR.VCS.OIAL.NO,PPNO,MP-NO,

CS.YES,G

ETMSG-YES, ITB-NO,

EBCDIC-YES,AUTORS-NO, I NTPO L NO

$EBSD fYPE-3277Mx2

Assignment

// SYSTEM POLTIME.N

DF

FPACK-

//

TERMATTR

o,

/sYSrEM I

I

enocnnv

f

// BSCALINE

// BSCATERM

//

TERMNAME

//

PROGRAM

TRANSLAT-NO,SWITCH

ED-NO,

BLKL 51

2,DATAFORM MESSAGE,

ITB.NO,VAR L.NO,SPAN.NO,

D

F F3270.Y ES

TYPE.CS,LINENUM 2,

XMCODE-EBCDIC,POLLIST-termid

[,termid]

. . .

TE R

M I

D-term id,fY

PE-3277 Mxz,

(No

)

coMMAND

lves|,

(YES)

oNLtNE-

Iro l,

(

Hor-o

I

oFFACTN

lonop /,

ADDRCHAR-6060xxxx3,

PO

L LCHAR-4040xxxxl

NAM E-termname.TE

RM

I

D-termid

NAM

E-pgmname,M RTMAX-n,

PGMDATA YES,PR

UF$Z

formatname,

PRUFLNG-nnnn,DFFMTERM-n,

DFFNDF-n.DFFSFDT-n

'BSCA-2

is

also

valid.

23284M^ and 3286Mx are also

valid ( x = Model number)

"xxxx eouals

the device

address.

Generation Stage 85

Support

of BSCG

(Binary

Synchronous

Communications

Controllerl

BSCC is

the

same

as

BSC

lines 3

and/or 4. This

documenta-

tion refers

to BSCC

communications

scheduler

and to

$CC4#[M

(BSCC

resident

code).

'fhese

two terms

are

i nterchangeable.

To

provide

maximum flexibility,

CCP

generation

has

two

macros,

unique

to BSCC,

that

del'ine line

and

device

su

pport.

Macro

$ECSC

(BSCC

line

support)

and

gECSD

(BSCC

device

support)

produce

the

resident

BSCC module

$CC4#M

when used

during

CCP

generation.

$CC4lfM

serves

a

function

for

BSCC similar

to

the

function

that

$CC4f2

serves for BSCA.

// BSCALINE and

// BSCATERM

(5704-SC2)

assignment

statements

cause the BSCC interface

to CCP

assignment

stage to be implemented.

BSCC

lines

may

be either

control

station or

point-to-point.

Outboard

polling

may

be included

(BSCC

only) by specifying

OUTPOLL-YES

and TYPE-CS

(or

allowing the TYPE

to default

to YES)

in the

// BSCALINE statement. The

other

parameters

are

processed

the

same as they would have

been if

(r

)

LINENUM-

{ ^ }had been specified.

tzl

Support of a Large

Number of Terminals

(Program

Number

5704-SC2

only)

Because

of addressing considerations

within the resident

portion

of CCP, there are

limitations

placed

on the number

of terminals

that can be supported

by CCP. This

limitation

is

affected

by the

number

of programs.

the

size

of line

buffers,

whether

DFF is

supported,

and so

on. In order

to increase

the number

of terminals

that may

be supported

and

to free

some

additional space

in the resident

area,

two

generation

options may be selected;

these options

will

move

portions

of the resident

CCP

to the user

program

area

(UPA). lf more

than 50-60 terminals

are

to oe

supported

in

any one

assignment set,

the

following

options

(both

on the EFAC

statement) should

be

considered:

- (YES)I

l,MovrNr- { } |

. (NO

,t

Specifying MOVDFF-YES will move

the

DFF

control

routine

to the UPA, thereby

freeing

more than 3K

bytes of

resident

area and occupying

4K bytes

of the UPA.

Specifying MOVTNT-YES

will

cause

the Terminal Name

Table

to be built in the UPA, using either 2K or4K bytes

of UPA.

A 2K

Terminal Name Table

(TNT)

will support

184

terminal names. lf more

than

184

terminal names

are

specified at assignment time, 4K bytes of UPA will

be used.

Ir'rovorr.

{fit}]

86

Chapter 7. Assignment

Stage

During

the

CCP

generation

stage,

the user fixes

the

maxi- Information

from

the

assignment

file,

$CCPFILE.

is re-

mum

size

and

caprabilities

of the

CCP.

During

the

assign- quired

by

various

people.

The system manager

and the

ment

stage of the

CCP, he describes

the

CCP

operating

en- system

operator

must

be aware of all

current system

assign-

vironment

in more

dretail. ments

so they

can

properly

control

and

maintain

the

com-

munication-based

system.

The terminal

operator

should

be

During

assignment,

the user

defines

one or more

sefs

of ter- aware

of some

aspects of the

system

assignments,

including

minals, files,

programs,

and

system

environments

that

are which

symbolic names

are

assigned to his terminal

and what

available

to the

CCP.

These

assignment

sets

are recorded the

current

password

or other sign-on

security information

intheassignmentfiler

($CCPFILE)allocatedduringthe is. Programmersalsorequirecurrentinformationaboutthe

generation

stage

(see

Chapter

6. Generation

Sfage).

Each system

assignments,

such as the

symbolic

file

names

and the

time

the

CCP is run, it

operates

under

one of the

assignment actual

files

they

refer

to. In

order to make

this information

sets;

that

is, the

CCP has

access

to a

particular

group

of ter- available to those who need it, provisions

must

be

made

to

minals, files,

and

programs.

The

user

can restrict

the re- distribute

all or part

of the information from

the

assignment

sources

defined

by a

set during

operation

startup

(see

index file

whenever

it changes.

entryi

operational

stttrtupl.

This

allows

him, for example,

to control which

pro,grams

are eligible

to be

called

during

a

particular

CCP run

or

to restrict

certain

files

during

a

run. REOUIREMENTS

FOR

ASSIGNMENT

While

the range

of function

specified

during

the

CCP

gener- In order to execute

the

assignment stage of the CCP.

the

ation

will not

vary

by

assignment

set, the

specific

operating system must meet

minimum requirements.

These require-

environment

of tfre

CCP execution

might vary. ments

are

less

than

are needed

for the

CCP operational

stage. The requirements

are:

The information

plac,ed

in

an assignment

set

during

the

assignment

stage is valid

until

a terminal,

program,

or

f

ile . 22K

(Program

Number

5704-SC1), or 36K

(Program

must

be

added to or removed

from

the

set, or until

aspects Number

5704-SC2)

of main

storage available

for

the

of the

system environment

change.

When

the

system

en- CCP assignment

stage to execute.

vironment

changes,

tl'le

contents

of the

assignment f

ile

can

be modified

by repeating

the

assignment

run,

without

re- . One

5444

Model

2 disk

storage drive. or one

3340

(or

generating

the

CCP. 3340

simulation area).

o An

input

device.

PLANN

!NG FOR

ASSIGNMENT o A 1403

Printer.

The

assignment run

must

be repeated

each

time

a new

pro-

gram

or file

is

added to a set, each

time

the

group

of ter- The assignment

build

program.

$CCPAS,

and the

assign-

minals

available

to the

CCP

changer;.

or each

time

certain ment list

program,

$CCPAL,

operate

under

control

of the

otheraspectsoftheCCPconfigurationchange.

Theassign- System/3Model

l5disksystemmanagement.

Theuser

ment

stage

of the

CCIP

can be run frequently

or infrequently, must

provide

two OCL

file

statements

when loading

the

depending

upon how

often

the

CCP environment

changes. assignment build

program,

one

for

the

assignment file.

$CCPFILE,

and one

for

a

work file

($CCPWORK).

lf the

CCP is to run

under various

sets

of assignments

in

a

given period

of tinre.

more

than

one set

of assignments

can

be

placed

in the

assigrrment f

ile. For

example,

a certain

set of

terminals, files,

and

programs

can be available

during

the day. with

a restricted

set available

during

night-time

hours.

Or,

perhaps,

a certain

group

of

files,

terminals,

and

programs

are requirecl for

the weekend,

month-end,

or

year-end

operations.

Assignment Stage 87

ASSIGNMENT

RESTRICTIONS

(5704-SC2

ONLYI

The assignment

build

program ($CCPAS)

or asstgnmenr

list

program

($CCPAL)

can

be executed

after

the

$CCpFILE

build

program ($CC1BF)

has

been

run. Either

$CCpAS

or

$CCPAL

may be

executed

while

CCp

is

in

the

execution

phase

in

another

partition. The executing

assignment

set

can

be

modified

while

CCP is executing

in another

parti.

tion. However,

the modif

ication

will not be

observed

until CCP is shut

down and then

restarted

using

the modi-

f

ied

assignment

set. There

are,

however.

a few restrictions

involved

in

running

either

$CCPAS or $CCpAL. TheV

are

as

follows:

o $CCPAS

will only perform

diagnostics

and will not

update

$CCPFILE

if any

of the

following

conditions

occur:

- $CCP

is in

startup

phase

in

another

partition.

- $CCP

is

in

shutdown

phase (or

shutdown

is

pending)

in

another

partition

using

the same

$CCpFILE

that

$CCPAS

is

trying

to alter.

- $CCPAL

is

executing

in

another

partition.

- Another copy of $CCPAS

is

executing

in another

partition.

- CCPFMT

or CCPPGM is

updating

the same

$CCPF

ILE that

$CCPAS

is

trying

to alter.

. $CCPAL

will not start executing

if any

of the following

conditions

occur:

- $CCP

is

in startup

phase

in

another

partition.

- $CCP

is

in shutdown phase

(or shutdown is

pending

in

another

partition

using

the

same

$CCpFILE

that

$CCPAL

is trying

to list.

- $CCPAS

is executing

in

another

partition

- Another

copy

of $CCPAL

is executing

in

another

Partition.

- CCPFMT

or CCPPGM is

updating

the

same

$CCPFILE

that $CCPAL

is

trying

to list.

ASSIGNMENT

DIAGNOSTICS

The CCP assignment

stage,

$CCPAS,

analyzes each

of the

assignment statements for invalid

specifications. lf an

error is found in any statement

of a set, that set of state-

ments is not processed

by the assignment

stage; however,

the remaining

statements in

that

set are

also

analyzed f

or

syntax errors.

The

assignment

list

program,

$CCPAL,

analyzes the list

statement

for errors. Error messages

are

written to the

system

print device.

ASSIGNMENT

F

ILE

($CCPF

ILE}

During

an assignment

run,

the user

defines

a specific

CCP

run

environment

in

a set of tables

contained in

the CCP

assignment

file

on

disk. This

file,

allocated

and initialized

during

the

CCP

generation,

always has

the name,

$CCPFILE.

When

the user

starts

operating his

CCP,

the startup

routines

of the

CCP,

using

the information

in

$CCPFILE,

initialize

the

CCP

for

this

run

so

that only

a specific

set of

terminalg,

files,

and

programs

indicated

by the

user can be

used.

A set of specifications in

the

assignment

f

ile,

once

set by

the

user in

an assignment run. hold for

any number

of

operational runs

of the

user's

CCP. The assignment file

need

be changed

only when

one or more

sets of specifica-

tions require

change.

Assignment

allows the

user to have more

than

one

opera-

tional environment

to run

the

CCP.

He

might, for

example,

have

one set of terminals,

f

iles,

and

programs

to use during

the day, and

a different

(though

possible

overlapping)

set

for night. His requirements

might

even

be

for more

than

two such environments.

The

assignment

file

may,

if the

user desires,

contain

several different

sets of specifics.

The user

can have more than

one

$CCPFILE

but

only one

per

pack.

The CCP

system operator can. upon

any startup

of

an operational run

of the

CCP,

identify

the

unit contain-

ing the appropriate

$CCPFILE

and the set

of specifics that

shall apply to the

current run.

Note: The

maximum

number

of sets

allowed in

one assign-

ment

file

is

25.

ASSIGNMENT

STATEMENTS

(ASSIGNMENT

BU I LD

PROGRAM}

In

order to place

an assignment

set

in

the

assignment f

ile,

$CCPFILE,

the

user must run

the assignment

build

pro-

gram,

$CCPAS.

The

user's

input

to the

assignment

program

consists

of a series

of statements. similar to OCL

statements.

These

statements identify

the

programs,

files,

terminals,

and

certain system

options

that constitute

a CCP operating

environment.

The

assignment

statements are

printed

by

$CCPAS

on the

s.,stem

print

device.

The

assignment

build

program

analyzes

the

statements

to

ensure

that

they

are valid.

Following

successful

validation,

the

specifications

are encoded

by

$CCPAS

and written

irlto

the

assignrnent

f

ile

as

an assignment

set

(for

example,

a

group

of

tables

in

the

assignment

file,

gCCpF

lLE.

which

def

ines

one

CCP

operating

environment).

The

assignment

program

can be used

to create

new

assignment

sets,

delete

existing

assignment

sets,

or replace

existing

sets

with new

specif

ications.

Different

assignment

sets

can

be

created,

deleted,

and replaced

in

the

same

run

of

the

assignment

program.

A set of assignment

statements

begins

with a starement

identifying

the

assignment

set

and

indicates

whether

it is

to

be modified,

created,

deleted,

or replaced.

Only

this

statement

is

required

to delete

a

set.

Subsequenl

state-

ments

provide

the

specif ic information

to be

placed

in

the

assignment

set. When

an item

in

an

assignment

set

is re-

placed,

a complete

set of assignment

statements

must

be

entered

(except

for

the modification

of certain

control

inlormationl.

$CCPAS

may

be

run

in

any

of

four

execution

modes:

1. Create

a new

assignment

set.

2. Delete

an existing

assignment

set.

3. Replace

an

existing

assignment

set.

4. Modify

tl'te

system

environment

portion

of an exist-

ing

assignment

set.

The input for

$OCPAS

is

as

follows:

o The

assignment

file

$CCPFILE.

o The

OCL/FILE

statements

provided

by

the

user:

The

following

OCIL statements

are needed:

Notes:

i. The unit

parameter

,ior

SCCPAS

specifies

the toca-

tion

of

the

assignment

build

program.

2. The unit

parameter

for

SCCPFILE specifies

the loca-

tion

of the assignment

f

ile

to be used

and

must

be a

5444 unit.

3. $CCPWORK

should have

RETAIN-S

specified

to

af

low

deletion

and can be

on R

1,

F1,

R2,

or F2.

4. The

keyword

RECORDS

should not

be used

to

define

the

size of $CCPWOR

K; instead

the keyword

TRACKS

should

be used. Additionally,

the

size

must

be large enough

to contain

the largest

set to be

processed (see

Drbk

Storage

Estimates

for the CCp

in

Appendix

F.

The

assignment

control

statements

instructing

$CCPAS

of the

funaion(s)

to perform.

$CCPAS

reads

tlre

control

statements

from

the

system input

device

andlor

from

a

source

library. Each

group

of control

statemenrs,

grouped

together

by

the user to define

an operating

environment,

is

called

an assignmenf

sef. The

input

to

$CCPAS

can consist

of one or more

sets

of control

statements.

i/ SOURCE This optional

statement

indicates

that

control

statements

are read

from

a source librarv memoer.

One or

more

SOURCE

statements

can be included

anywhere

within

a set

of control

statements.

The

following

control statements def ine

an assignment

set and

must

be specified in the order

shown:

IISET This

required

statement identifies

the output

assignment set

oper-

ated on and the type of operation

to be

performed.

lf multiple

input

assignment sets are

provided

as

in-

put

to $CCPAS,

the

/l SET state-

ment

defines the beginning

of each

assignment

set.

This required

statement

def ines

certain operational

environment

options not directlv

minals,

f

iles,

or

programs

when

this set is used

for

execution

of the

ccP.

// SYSTEM

Assignnrent

Stage 89

// TERMATTR

// BSCALINE

// BSCATERM

//

MLTALINE

// MLTATERM

Each

of these

statements

defines

the

variabler

attributes

of a

terminal.

Each

terminal

statement

(BSCA-

TERM

and MLTATERM)

must

refer

to a

TERMATTR

statement.

Note: Any

BSCALINE

statement

with correspond

ing

BSCATE R

M

statements

(as

a

group)

can

appear

before

or

after

any

MLTALINE/

MLTATERM group.

The

order

of

input

lines

determines

the

priority

of service during

execution

of the

CCP. For

erxample,

the

order might

be:

MLTALINE

MLTATERM

(one

or more)

BSCALINE:

BSCATERM

(one

or more)

MLTALINE

MLTATERM

(one

or more)

Each

of these

optional

statements

identif

ies

a BSC

line, its

charac-

teristics,

and the

order

the

terminals

on that line

(if

there is more

than

one terminal)

shall be

polled.

At least

one

of these statements

must follow

a BSCALINE

state-

ment. Each

BSCATERM

state-

ment identifies

a terminal

on the

line,

its

operating

characteristics,

and whether

it can issue

commands

to the

CCP.

Note: The BSCATERM statement

must

f

ollow the

BSCALINE state-

ment

for

which

the

terminal

is

defined.

Each

of therse

optional

statements

identifies

a MLTA

line,

similar

to

the

BSCALINE

statement

At least

one

of these

statements

must follow

a MLTALINE

state-

ment. Each

MLTATERM

state-

ment identifies

a terminal

on the

line,

its

operating

characteristics,

and whether

it can

issue

commands

to the

CCP.

//

TERMNAME

//

DISKFILE

// SYMFILE

// PROGRAM

When creating

or replacing

an assignment

set, at least

one BSCALINE

and one BSCATERM statement,

or one

MLTALINE and

one MLTATERM statement must

be

in the control statements.

A /* statement

must

be

given

at

the end of all inpur

con.

trol statements

except

when the last

control

statement

is

from the

source library. In this

case, see the keyworo

END in

the

SOURCE

statement.

//

PORTLINE

(5704-SC2

only)

Note: The MLTATERM statement

must

follow the MLTALINE state-

ment

for which

the

terminal

is

defined.

The PORTLINE statement defines how

the BSCA, BSCC,

or SIOC

portline

is

to be

divided into ports

and

the size

of

the

line

buffers. The PORTLINE

statement

should be entered

after the

SYSTEM statement or after the last

TERMATTR statement.

One

PORT-

LINE statement may

be

entered for

each BSCA, BSCC

or SIOC

line

sup-

ported. For

SIOC support, Program

Number

5799

WNK is

also

required.

Each

of these required

statements

def

ines

a symbolic terminal

name

by which

a terminal

can be referred

to in an

application

program.

The

symbolic

terminal name

can oe

assigned to a physical

terminal

or

can

be left unassigned.

Each

of these optional statements

defines a user disk data file

and the

physical

attributes

of the

file.

Each

of these optional statements

defines a symbolic name

that can

be used to reference

one or more

disk

files

specif ied on

// DISKFILE

statements.

Each

of these

required

statements

identifies

a

user

program

that is

permitted

to execute

during a CCP

run

using

this

set. The statement

defines the program

resource re-

quirements

and

operational charac-

teristics.

90

The output for the

assignment

build program

is

as follows:

a A listing

of the

assignment

control

statements

on

the

pri

n

ter.

Appropriate diagnostics

on the printer and an error

halt,

at the end

of the run,

if necessary.

The

$CCPFILE containing

creared,

replaced,

or modif

ied

assignment

sets,

and no longer

containing

any sets

speci-

fied

to be deleted.

The

$CCPFILE is ready

for opera-

tional

startup.

An assiqnrnent

set will be

created

or replaced

in the assign_

ment file

only if the

complete

set,

as read

by the

assign-

ment

build

program,

is free

of errors.

The $CCPAS cannot run concurretrtly

in both partitions

nor

run

concurrently

with the

ccP in

the

other

partition.

($CCPF:lLE

cannot

be validly

altered

from both partitions

concurrently

or while

the

CCP

is

running.)

ASSIGNMENT

CONTROL STATEMENTS

Each

control statement

contains

arr identif

ier

and para-

meters. Tlre identif

ier is

a term that defines

the type of

control statement

and is

always

the first field of the state_

ment followingthe //. The parameters

are the control

information

being

supplied

to the

program. Each

param-

eter consists

of a keyword to identify the parameter,

a

hyphen,

and

the appropriate

control information

value.

Parameters

within any

single

control

statement

can

be

entered

in any

order.

Writing Assignment

Control Statements

The rules

for constructing

assignment

control statements

are

as

contained

in

the

following

paragraphs.

Statement ldentifier: // in columns 1 and 2 followed by

at least

rcne

blank preceding

the statement

identifier.

Blanks: One

or more blanks is required

between

the

l/and

the statement

identif

ier,

and between

the statement

identi-

fier

and the

f

irst

keyword. The

first

blank

following

a key-

word value

indicates

the end of the statement. A blank fol-

lowing a comma (which follows a value

given

for a keyword

parameter)

indicates

that the statement

is

continued on the

following input record (which must have

a /16

in the first

three

colurnns).

Keyword Parameters: These parameters

are separated

by

commas. A hyphen (-)

separates each keyword f

rom the

corresponding

value. Blanks

are not allowed

within or

between parameters.

Sublist: A sublist

is

a series

of values

given

for a single key-

word. Each

value

is

as

a series

of f

ilenames).

The

first

value

of a sublist

always has

an apostrophe

(,)

entered

before

the value.

succeeding

values

are

separated

by commas,

and the last value

has

an apostrophe

after it.

For

example: EXAMPLE-'value,

value,value'.

Split-Value: A split-value

is a group of values

that might

be

given

for a keyword parameter;

however,

each

has

a

separate

and distinct

relationship

to the keyword. These

split-values

are separated

by a slash

(ll. lt a series

of split-

values

is

given,

the

series

is

called

a split-value

sublist. lf a

split-value

is

not given

as a sublist,

then

apostrophes

need

not be entered

before

and after the complete

split-value.

o Split-value

example: KEYWORD-valuel

/value2/value3

o Split-value

sublist

example: KEYWORD-'valuel/value2.

valuel

lvalue2'

Special

Characters:

Slashes

(/), blanks,

commas

(,), l-ry-

phens

(-).

and

apostrophes

(') must

not appear

within the

bounding

apostrophes

if a keyword is def

ined

as

either

sub-

list or split-value.

Any of these

characters

can appear

with-

in the apostrophes

if the keyword is not def ined

as

either

sublist

or split-value.

In this

case, a single

apostrophe

(')

must be represented

by two successive

apostrophes

(

" ).

Statement

Length: Positions

1 through 7

j of a record

can

be used.

The

first

blank encountered

following

a keyword

parameter,

without indication

of continuation

to the

delimits

the statement.

Continuation.' Control statements

can be

continued on sub

sequent

input records

by placing

a comma immediately

after a keyword parameter

value

on a statement. The conr-

ma must

be

followed

by one

or more

blanks

prior

ro or tn-

cluding

column

72. (Thus

the

comma

can appear

in

col-

umn

7l and

a blank

in

column 72.1

A continuation

line

must

start with two slashes

(//) followed bv one or more

blanks, followed

by the remaining

values

(if part

of a sub-

list)

or the remaining

keyword

parameters.

Any numoer

of continuation records

can be used. See

Figure

6 for an

example

of coding.

Assignment Stage 91

Comments:

The

user can

include,

in

addition

to control

statements,

special

statements

that

contain

only comments.

A comment

statement

is

identif ied

by an

asterisk

(*)

in

column

1

and

can have

any combination

of characters.

Any

comments

too long

to be contained

in

88

columns

are

truncated from

the right.

In

addition.

comments

can

be

included

on

any record

of a

control

statement following

the last

parameter

on

that

record.

One or more

blanks

must

separate

the last

param-

eter

from

the

comments.

Special Meaning

of Capital Letters,

Numbers,

and Special

Characters:

Capitalized

words

and letters,

numbers,

and

special

characters have

special

meanings

in

control

state-

ment

descriptions:

In

control

statements,

capitalized

words

and letters

must

be written

as they

appear in

the

statement descrip-

tion. lf numbers

appear with

the

capitalized

informa-

tion,

they must

also

be

written

as shown.

Lower

case terms indicate

that

a

value

must

be

substi-

tuted

for each

term.

Figure 6. Continuation Control Statements

92

// SOURCE

Statement

The

SOURCE

statement

is

optional

and

specifies

that

con_

trol statements

supplied

to $CCpAS

are

read

from a source

library

member.

When

a source

library

is

specified,

one

or

more

complete

control

statements

must

come from

that

source

entry. After processing

the last

control

statement

in

the

specified

source

member,

control

statements

are

again

read

from

the

system

input

device.

lf the

parameter

END

is

specified

with the value

yES.

SCCPAS

goes

to EJ. One

or more

SOURCE

statements

can

be included

anywhere

within

a control

set

but

cannot

be

included

within

a source

member.

NAMEi-name

This

rerquired

parameter

specifies

the

name

of the

source

library

member

containing

the

control

statements

being

supplied

to

$CCPAS.

This

member

must

have

previously

been

built

using

gMAlNT.

UNIT-

This

required

parameter

specifies

the

source

library

location.

END-

This ogrtional

parameter

indicates

whether this source

member

contains

the last

control

statement

being

supplied

to $CCPAS.

The

defautt

is NO.

// SET

Statement

The

SET

statement

identif

ies

the

assignment

set

and the

operation

to be done:

create,

replace,

delete.

or modify.

This

is the

only

statement

required

to delete

an

assignment

set.

// sEr rro

.llf

r

r,AcrroN-

I ffdf. | ,

1cr

.-_

_. I3.,:rfl:J

T,DFLTEXEC-

|

I5tl, r,ANyspEcs-

J_t#l,'

rD.

Jlf

(cJ

The lD parameter

specifies

which assignment

set

is to be

affected.

Each

assignment

set in

$CCpFILE is identified

by a different single

character.

lf the

parameter

is

omitted,

the

default

value

is 1. Any

single

extended

alphameric

character

lO-9,

A-2,

#, $, @)

can

be used

to identify the assignment

set.

(

cneare

ACroN.lffi.

(SYSMOD

IF;i

tffJ

ftto )

l

vesi

The ACTION parameter

specif ies

what operation ts

to

occur. lf it is

omitted.

the

default

value

is

CREATE.

Note: lf the

set

being

deleted

or replaced

is

the

set

CCp

is executing

from in

another

partition,

the

program

use

count for that

execution

of CCP will be lost

(5704-SC2

only),

CREATE

lf CREATE is

used

and the

set lD does not exist

in

the

file,

the new

set is

added

to the file. lf the created

set cannot

fit, either

because

there

is not enough

room in

the

file

for

the tables

or not enough

room

for the

entry in

the

directory,

an error

message

is

given

and

the

request

is ignored.

A maxi-

mum of 25 sets

are

allowed in

the

control file.

'Applies

only to Program

Number

b704-SC2

// SOURCE NAME-name,

,-,t

{

R1r

rt(

::{

f z /

,,.'"

{H.} l

Assignment

Stages 93

REPLACE

lf REPLACE

is used

and

the

set exists

in the file,

the set

in

the f

ile is

entirely

replaced

with thr:

information

on

tne

statements

following

the

SET statement.

lf the value is

REPLACE

and the

set

cannot

be

found

in

$CCpFlLE.

a

warning

message

is

given

and

the action

defaults

to

CREATE.

DELETE

lf DELETE

is

used

and the

set

lD

is in the

gCCpFlLE,

the

set and its

table values

are deleted from

the

file. lf

the

value

is DELETE

and the

specified

set is not

in the file.

a

warning

diagnostic

is

given.

SYSMOD

The

SYSMOD

action indicates

that

onlV

the

SySTEM state-

ment.

the

execution

def

ault

set identif

ication,

the

any

specifications

identif

ication,

or all

are

to be

modif

ied

in

a

set. The

set must

already

be

in the file (for

further

definition, see index entry

SYSTEM Statementl.

i vrs)

DFLTEXEC-

i _; l

The

DFLTEXEC

parameter

specifies

whether

this control

set lD is

used as

a default if no

set lD is

given

at the start

of

execution

of the

CCP. lf the

parameter

is not

given,

the

default value

is NO. lf the value YES

is

given,

then

this set

is

used

as

the

default

at startup.

The last

processed

SET

statement

that

has

this

parameter

and

the value YES

speci-

fied

overrides

any

ANYSPECS

{m } ,rr.onr.urn

Number

5704,SC2

onty)

The

ANYSPECS

parameter

indicates

whether

the

,SU

01

ANY SPECIF ICATIONS?'

startup message

is

to be by.

passed

during

CCP startup.r

This

parameter

grves

the

ability

to

eliminate

a startup

prompt. lf

the

$CCpF

ILE is

located

on the

program

pack,

and a

$CCPDUMp

file

is

located

on the unit specified

during

generation

or on the

unit

specif ied

by the

DUMPUN

lT parameter

on

tne

SYSTEM

statement,

a

nonstop

startup

procedure

rs

permitted.

DFLTEXEC-YES

must

be

specified

on

the SET

statement

to allow the ANYSPECS

NO parameter

on the

SET statement.

The last

processed

SET statement

rnat nas

these

parameters

with the

value YES

specif ied

overrides

any

// SYSTEM Statement

The

system statement

defines several facts

about

the

system

environment

in

which

this assignment

set is

useo:

o Minimum

total main

storage

space required

f

or the user

programs

which must

execute

under

this

assignment

set.

o whether

the

printer,

MFcu, 2560,2501

,3741, and

1442

are

initially

allocated

to the

CCP

program

level.

o Password

for this set, if the

user

chose

the option

at

CCP

generation.

o The number

of bytes set

aside as the

CCP

dvnamrc

buffer

area

for communicating

with terminals.

a Maximum

length

of commands

and

program

requesrs

from terminals

other than

the console.

o Pack

on which

the

user's

DFF resides.

//sysrEM [r,rrnuca,l['lK]

MtNTpBuF-n

LPASSWORD-passwordl [,PRt

NT '-

lprf

'

/c \

\nef

r

{F )

('*)

t,MFcur.(3rl

r,N/Fcu2.

itoi

r,rlrFcM1.

(3r l , r,^/rFcM2-

ito'

r'c

\"'

(R

I tr"

a.,

"rl

R)

t-"

\

t.nzsor

l-!9^l t t,RP1442

{ I EJ 1

rRP i

ln I

[,N3741-i^ '.

]

l' I

INoI

t,PcMREoL.

)S

lr r.,,orro*ot-

[",,*"*

lil3l.J",.l]

20

l,

nl

['""'"

1;ili

f][,""

^""

lffi'11'

['*.

l*l]'

["o",,"o,^

l"f

]'

I l'No' il '

I,CSPOLTIM. l'trt,ww' ) |

1 fooo,1

ll

[.",,,u

lsf

]'

[o*r.or.

lHrl] '

[,DUMPUN

IT.

(

D1

D2

D3

D31

D32

D33

D34

D4

D41

D42

D43

DM

l'

'Default

fr:r

5704-SC2l is

8K.

2Dou,

not

apply to Program

Number

5704-SC2.

'Applies

only to Program

Number 57O4-$C2.

'For Program Number

57O4-5C2, these codes may

also be specif

ied

R1, F1, R2, t:2

D1A, D1B, D1C, D1D

D2A, D2B, D2C, D2D

D3A, D3B, D3C,

D3D

D3E, D3F, D3G,

D3H

D4A, D4B, D4C, D4D

D4E, D4F, D4G,

D4H

It is

possible

to modify

only the SYSTEM statement

for

a

set which

already

exists in the

$CCPF

lLE. lf ACTION-

SYSMOD

was

specified on

the

set statement. the system

statement must

be the only other statement

given

for this

set.

In this

case, only those

parameters

given

on

this state-

ment

are used

to modify the

parameters

that were

given

when the

set

was

created,

replaced, or last modif ied.

MINUPA-nnnK

The MINUPA

parameter

specifies the minimum

size of user

main

storage area

for executing

programs

in

an

operational

run

of the

CCP

for

this set. The size of user main

storage,

when

using DFF, must

be

large enough

to include

the size

of the work

space added to a DFF

program.

This size is

determined by the DFFSFDT, DFFMTERM,

and DFFNDF

parameters

in

the

program

statement. The sizes

associated

with the DFF

can be determined from

Disk

Storage

Estimates for CCP

in Appendix F.

lf less than nnnK

is

left

at the end of startup.

a message

is

issued

with the cancel ootion.

The value for this

parameter

must

be one

to three digits

and

must

end with the

letter K. K represents

1024

bytes.

The value must

be

a

multiple

of 2K. The

minimum

(and

default) values

are 6K

for Program Number

5704-SC1, and

8K for Program Number

5704-5C2. The maximum value

is

256K

(5704-SC1)

and

512K

(5704-SC2).

MINTPBU F-n

The MINTPBUF

parameter

specif

ies

the

number

of bytes

that must be set aside

for buffer work

area

for

teleprocess-

ing

communications.

For

an

example

of determining

the

size of the teleprocessing buffer, see index entry:

sample

assignment

set; calculation of main storage sr2es. The TP

buffer area

is

calculated

using the

formula

contained in

Appendix F.

Assignment

Stages 95

The

value

specified

for this

parameter

(or

changed

during

startup)

is rounded

up

to the

of 2K by start_

up. The

actual

value

depends

on the

size

of the internal

control

tables

built by startup. For

example:

where

MINTPBUF-290

is

specified

2K

Byte

Boundary

1

10

Bytes

.--\r_-/.v--\

1

80 Bytes

/-\--^--*\

Actual

size

of the

teleprocessing

buffer

at

the

end

of

startup

(21

bg

bytes)

PASSWO

R D.password

The

PASSWORD

parameter

specifies

the

system

password.

This

parameter

must

be

specified

i{

the

SECURE_CCp

op_

tion

was

selected

on

the

$ESEC control

statemenr

at

gener-

ation,

and must

not

be specified

if that

option

was

not

selected.

lf the

user

chooses

to use

his

own

security

system,

then

this

parameter

must

be omitted

(the

security

informa-

tion he

checks

a sign-on

against

is

set by using

the

program

SCCPAU).

lf

this

parameter

is

given,

the

value

must

contain

one

to

six

characters

specifying

the

system

password.

The

password

can

be

any

combination

of the

64-character

set with no

embedded

blanks.

lf the value

given

for

this

parameter

is

a

special

character,

it must

be

enclosed

in

apostrophes.

(Special

characters

are

any

characters

other

than

the

36

alphameric

characters.)

In

order

to code

an apostrophe

as

a character

in

the

pass_

word.

two successive

apostrophes

must

be coded.

The

PRINTER parameter

declares

whether

the printer

is

allocated

exclusively

to the program

partition

in

which

CCP is executing

at the

beginning

oj a

CCp run. lf tire

parameter

is

not given,

the

default

is

NO. lf yES is

speci_

f

ied,

the printer

must

not be

allocated

to the

other

parti_

tion after

the

beginning

of the

CCp run (unless

print

spool_

ing

is

used for both partitions).

lf NO is

specified

and

the

program

statement

has

declared

it as

a required

device,

CCP

allocate

attempts

to obtain the device

from DSM when

the

program

is requested.

96

MFCUl

MFCU2

MFCM1

-

MFCM2

These

optional

keywords

specify

whether

the

MFCU

and

MFCM

are

permanently

allocated

to the

partition

where

CCP

is executing.

In

addition,

these keywords

specify how

the MFCU

and

MFCM

hoppers

are

allocated

by

CCp

start-

up. The following

explanations

apply:

Parameter

Explanation

Combined

file: Specify

C if any

program

running

under

CCP

using

this

assignment

set references

this

hopper

as

a

combined

f

ile.

Rp Reader/punch:

Specify

Rp if combined

f

ile

does not apply

and

programs

running

under

CCP using

this set

use

this

hopper

for input

ano output.

R Reader

only: Specify

R if combined

f

ile

or

reader/punch

does

not apply and programs

running

under

CCP

using

this

set use

this

nopper

as

Input.

P Punch

only: Specify

p if combined

file

or

reader/punch

does not apply and programs

running

under

CCp

using

this set

use

this

hopper

as

output.

NO lf NO

is

specified

with MFCU1,

MFCU2,

MFCM1,

MFCM2,

or

omitted,

the MFCU

and MFCM

are not permanently

allocated

to the

CCP

partition. The

device

can

still

be

used

but contention

might

occur

with

the

other

partition.

Note: lf the specified

hopper is

not being

spooled

under

CCP.

the

device

might

not be available

to the

other

parti-

tion for spooling. For

spooling

consideration

s, see

IBM

System/3 Model l5 t-/ser's

Guide to Spooling, GC21_7632.

This parameter

declares

whether the 2501 is

permanentry

allocated

to the partition

where

CCp

is executing.

lf the

YES

option is

chosen,

the

2501 is

not available

to the other

partition. lf NO is

specif

ied

and the program

statement

has

declared

it as

a required

device,

CCp

allocate

attempts ro

obtain the device

from DSM when the program

is

requested.

c

r'/

R\

foI

2K Byte

Bou nda r

I

Bytes I

-l ---1-

pRrNrER.

1v:rI

R2501.

{}3r}

Teleprocessing

Buffer

RP1442-

This

optional keyword specif

ies

whether the 1442

is

to be

permanently

allocated

to the

partition

in

which

CCp

is

exe,

cuting. lf this

keyword

is

specified

as

NO

or omitted,

the

'1442

is

not permanently

allocaterl

to the

CCp

partition. ln

addition,

this

keyword

also

specif

ies how

the 1442

is allo-

cated

by CCP

startup.

The

follovving

explanations

apply:

Parameter Explanation

C Combined

file: Specify

C if any

program

running

under

CCp

using

this

assignment

set

reference

this

hopper

as a

combined

file.

RP Reader/punch:

Specify

Rp if combined

f ile

does

not apply

and

programs

running

under

CCP

using

this

set

use

this

hopper

for input

and

output.

R Reader

only: Specify

R if combined

file

or

reader/punch

does not apply and programs

running

under

CCp

using

this

set use

this

hopper

as input.

P Punch

only: Specify

p if combine

f

ile

or

reader/punch

does

not apply

and

programs

running

under

CCp

using

this

set

use

this

hopper

as

output.

NO lf NO is

specified,

the 1442

is nor perma-

nently

allocated

to the

CCp

partition.

Note: lf the 1442

is not being

spooled

under

CCp,

the

1442

might

not be

available

to the

other

partition

for

spooling. For spooling

consideration

s, see

IBM System/3

Model l5 lJser's

Guide to Spooling, GC21.7632.

This

optional

keyword

specifies

whether

the

3741

(as

a

unit

record

device)

is

to be

permanently

allocated

to the

partition

in

which

CCP

is executing.

lf this

keyword

is

specified

as NO

or

omitted,

the

3741

is

not

permanenuy

allocated

to the

CCP

partition.

In

addition,

this

keyword

also

specifies

how

the

3741

is

allocated

by CCp

startup.

The

following

explanations

apply:

Parameter Explanation

RP Input/Output:

Specify

Rp

if programs

running

under

CCp

using

this

set

this

device

for

input

and

output.

R Input

only: Specify

R if input/output

does

not

apply

and

programs

running

under

CCp

using

this

set

are using

a 3741

as

an input

device.

P Output

only: Specify

p

if input/output

does

not

apply

and

programs

running

under

CCp

using

this

set

are

using

a 3741

as

an output

device.

NO lf NO

is

specified,

the

3741

is

not

per-

manently

allocated

to the

CCp

partition.

Note: ll the

3741 is

not

being

spooled

under

CCp.

the

3741

might

not

be

available

to

the other

partition

for

spooling.

For

spooling

considerations,

see IBM

System/3

Model l5 User's

Guide to Spooling, GC21-7632.

N374'1

Ii,l

tC ,

\

t'/

iR )

/to)

Assignment

Stages 97

PGM

RE:QL

The PGMREOL

parameter

specifies

the

length,

in bytes,

of

the longest program

request

command

from any

terminal

used

in this

set

that does

not use

pRUF. (See

the

PRUF

LNG parameter

on

the

// PROGRAM

statement

for

PRUF

request.)

(CCP

might

allow

more

than

the

specified

value.)

This

length

includes program

name,

one intervening

blank,

and

the

data accompanying

the

program

request

if this

option is

used.

The

maximum

value

allowed

is

g0

bytes

for Program

Number 5704-SC1

and 255 bytes

for

Progranr

Number 5704 SC2. The nraximum of 255 bytes

for Prograrn

Number 5704-SC2

can be

used

with CpU_CpU

or MLTA applications,

but

the recommended

maximum

for

327O

and

other environments

is

80. lf this parameter

is

not given,

the

default

is

6 positions.

The

minimum

value

allowed

is

2 positions.

Note: l-he

BLKL parameter

of the TERMATTR must

be

greater

than

or equal

to PGMREOL..

COMMANDL

The

COMMANDL parameter

specif

ies

the length,

in

bytes,

of the longest

terminal

command,

erxcluding

the program

request

command,

that can

be

entered

from any command

terminal

used

in

this

set. (CCp

might

allow

more

than

the

specified

value.)

The

maximum

value

allowed

is

g0 charac-

ters. lf this

parameter

is

not given,

the

default

is

20 charac_

ters. The rninimum

value

allowed

is

zero

characters.

DFFPACK

I

SYSTEM'

I

PROGRAM','

The DFFPACK parameter

specifies

the pack

whose

object

library

contains

the

display

formats

for this

set. The

dis_

play formats must be previously

produced

through the dis_

play

format

generator

routine

($CCpDF).

lf this

parameter

is not specified,

the use

of the

display

format

facility

(DFF) is

not allowe<J for this

set. Allother

parameters

referring

to the DFF arer diagnosed

as invalid.

DF F

INDX {Program

Number

5704-SC2

only)

The DFFINDX parameter

specifies

whether

or not the DFF

index

resides

in main

storage.

lf YES is

specif ied.

an

external

pointer

list

(EPL)

is

built in main

storage

and the

DFF

indexr:s

built in

$CCPFILE arer moved

to the EpL.

POLTIME.

ttt =

total

time

to poll (in

seconds)

continuouslv

before

initiating

a wait.

vvw

= total

time

to wait (in

seconds)

before

resuminq

poll_

ing

(after

interval

polling

has

started).

POLTIME-NO

indicates

no interval

polling

for

this

assign-

ment

set. However,

this can

be

overridden

during executron

(if

the

CCP

was

generated

for interval

polling)

by the

POLTIME

command.

In

this case,

INTpOL

yES must

have

been

specified

on the

$EBSC

generation

statement.

The

default

for ttt is

060;

the default

for ww is

02.

(No )

CSPOLTIM-{ 'ttt,ww') (Program

Number

5704-SC2

onty)

(

ooo'g2

)

CSPOLTIM-NO

indicates

no interval

polling

for BSC

lines

3 and

4 (BSCC)

for this

assignment

set. However.

this can

be

overridden

during execution

(if

CCP

was

generated

for

interval

polling)

by the POLTIME

command. In this case,

INTPOL-YES

must have

been specif ied

on the

$ECSC

generation

statement.

ttt is total

time (in

seconds)

that CCP should

poll

before

initiating

a

wait. ww is

the time (in

seconds)

that CCP

should wait before resuming

polling

(after

interval

polling

has

started). The

default for ttt is

060;

for ww. it is

02.

I

For Program

Number

57O4-SC2

R1, F'|

, R2, F2

D1A,

D1B,

D1C,

D1D

D2A, D2B, D2C, D2D

D3A, D3B, D3C, D3D

D3E, D3F, D3G, D3H

D4A, D4B, D4C, D4D

D4E, D4F, D4G, D4H

these

codes

may also

be specrfred

161

j;i (ro )

( 'ttt,ww')

(ooooz

)

l 20l

i;l

lYES\

lNo f

oa

FSOE.

The FSOE parameter (Program

Number 5704-SCl only)

specif ies

the number

(n)

of file

sharing

queue

elements

to be

built by CCP

at startup

time. lf the

default

is

used,

CCp

(at

STARTUP

time)

calculates

ancl builds

the maximum

number

of elements

that

would

ever

be required

under

this

assignment

set. based

on the following

formula:

number of shared f

iles

x user

program

area

program

size

This is

calculated for each

program

in the assignment

set

and the maximum

product

is

used.

The maximum is

limited

by the following

formula:

MAXCHAIN-n

The

MAXCHAIN parameter

(for

Program

Number

5704-

SC2

only)

specifies

the number

(n)

of control

blocks

to be

built for task

chaining

and

can be

a

value

from I to 15.

The value

to specify for this parameter

is

the number of

concurrent

task

chain requests

that may be

queued. The

value

of n should

not be higher

than is

essential

because

unneeded

control

blocks

will be

built

and main

storage

space will be

wasted. lf this parameter

is

not entered,

the

task

chain

facility

is

not supported. In

this case, if a task

chain

operation is

attempted, the program

issuing

the

operation

is

canceled

with a 3F termination

code.

The

value

specified for this

parameter

plus

the number

of

TERMNAME statements in

this

assignment

set

cannor

exceed

254.

t0t

lNl

maximum

number

of

shared files

on any x

PROGRAM

statement

number

of

CCP

user

tasks

(SCP

generation

option)

To

prevent

the

possibility

of running

short

of FSeEs,

it is

recommended

that

the default

be used.

{s)

ERTIME 1Nt (Program

Nurnber

5704

SC2

onty)

The

ERTIME parameter (Program

Number

b704-SC2

only)

specif

ies

the time

interval

in minutes

between

retries

to

terminals

in

error recovery

if AUTOERP

is specified

for

that

terminal

on the BSCATERM

statement.

Valid

entries

are

between

1

and 99

minutes.

The

default

is 5 minutes.

(

YES)

PRUFOF- 1 ryp l (Prosram

Number

b704-SC2

onty)

The

PRUFOF

operand

specifies

whether

the terminal

on

which

PRUF

data was

entered

should

remain

in

pRUF

mode

until

the next

output

operation

or

should

be changed

to a non-PRUF

terminal

after

an ACCEPT

input

operation.

YES

indicates

the

terminal

will be

changed

to a non-pRUF

terminal

after

an accept input

operation.

NO

indicates

the

termirral

will

remain

in

PRUF

mode

until the

nexr

output

operation

is complete.

The

default

is NO.

D1

D2

D3

D31

D32

D33

D34

D4

D41

D42

D43

D44

(Program

Number

5704-SC2

onlv)

This

operand

specifies

the unit on

which

the

CCp dump

stor

age

file ($CCPDUMP)

resides.

The DUMPUNIT parameter

overrides

the DPUNIT keyword

specified

on the

$EGEN

statement

during

CCP

generation.

lf the DUMpUNIT

parameter

is not specified,

CCP

startup

searches

the

unit

specified

during

CCP

generation.

Assignment

Stages 99

// TERMATTR

Statement

Each

TERMATTR

statement

def

in€)s

certain

attnbutes

of

a

terminal

and

must lollow

the

system

statement.

The

number

of these

statements

required

depends

on the

num-

ber

and

type

of terminals

used

and

how

they

are

to perform

in

this

assignment

set. Each

TERM,ATTR

statement

defines

one

terminal

attributes

set.

One

user

program

can

refer

to

different

attributes

sets for the

samr-.

terminal

depending

on the

user

of

that

terminal.

Each

l.erminal

statemenr

(BSCATERM

and

MLTATERM)

must

refer

to

a TERM-

ATTR

statement.

One

TERMATTR

statement

can

provide

the

same

attributes

for

several

terminals

and

therefore

be

referred

to

by

several

terminals.

/i TERMATTR ATTR I D.attrid

The following parameters

can

MLTA and

BSCA terminals:

Lrnnr.rsur-

f

ffi|

(H)

[,SWITCHED-

<

MC

)

tm)

be specitied

for

both the

{YESl.

r r,urLArtr- 1frfO

iJ

l

The following parameters

can

be specif

ied for BSC

term inals

only

:

[,BLKL-n]

[,RECL-n]

I RECORD I

[,DATAFoRM

lBLocF ! r t,t"o** l*N^l

fvressncel

" - 'YESI

r,rrB.

l**rf

I

r,vARL-ll|rl,

r,sPAN-

l+3rf I

r,vERrFYrD

l$3rf

,

LDFF32io-lffit

t l

100

ATTRID-attrid

The ATTRID parameter

must

be specified.

lt is

a reference

lD number

used in

a BSCATERM

or MLTATERM

state-

ment

to associate

this

attributes

set with

a specif ic

terrninal.

The value

for

this

parameter

can

be

any value

between

1 to

255

inclusive.

At startup

time

an amount

of main

storage

(in

bytes) equal

to five

times

the highest

number

specified

by

any ATTRID

parameter

in

this

set

is reserved

for

the

entire

terminal

attributes

table.

'fhus,

the

ATTRID

values

should

be

chosen from

the

smallest

numbers

available.

For

5704-SC2

only, ATTRID-04

must

have

specific

attri-

butes

when

programs

such

as

CCPFMT,

CCppGM,

or

$OCOPY

are to be used.

Refer

to

the descriptions

of

tnese

programs.

(vrsr

TRANSLAT-

1 *i i

The

TRANSLAT

parameter

specif

ies whether

the

CCp

auto-

matically

translates

input

data from

line

code

to EBCDIC,

and output

data

from

EBCDIC

to line

code.

A yES

value

indicates

translatiorr

takes

place

for

MLTA

transmission,

and

for

BSC

transmission

using

ASCII

code.

A YES

value

is

also valid

if the

line

code

is

EBCDIC,

though

it causes no

actual

translation

to occur

unless

UpCASE-

YES

is

also

specif ied.

This

would

be

a consideration

when

def ining

attributes for

an EBCD

lC

3270 terminal

with

a

typewriter

keyboard.

TRANSLAT-YES

rnust

be specif ied

if using

DFF

with

ASCII

3270

terminals.

A value

of NO

indir:ates

the CCP

does

not do

the

transla-

tion;

either

the data

coming

in or

going

out is

EBCDIC

or

the user

handles

the responsibility

of

translation

to

and

from

the

appropria'te

line

code.

,PCASE.

{ 15'}

The UPCASE

pararneter

specif ies

whether lowercase

charac-

ters transmitted f rom the terminal are converted

to upper-

case characters

when presented

to the user

by the CCp.

The

YES

value

is valid

only if the

TRANSLAT parameter

has

the value YES;.

A value

of YES indicates

the

CCp

converts

lowercase

to uppercase

before

presenting

data

to the user

program.

A value

of NO indicates

the

CCP does

nor con-

vert lowercase

characl.ers

to uppercase

coming

f rom the

terminal lf not specif ied,

UPCASE

defaults

to tne

same

value

as TRANSLAT. All input

l'rom

terminals

in

command

mode is

translated

to uppercase.

SWITCHED-

The

SWITCHED

parameter

specif

ies the

options

available

on switched lines. This parameter

must be specified

in an

attributes

set used

with a terminal which is

on a switched

line. The value

AC is not valid for MLTA lines.

The de-

fault

is NO. The following

explanations

apply:

Parameter Explanation

NO Not a switched

line terminal.

AC Automatic

calling.

The

CCP calls

the ter-

minal

using

the telephone

number

provided

on the

TERMNAME statement.

MC Manual

calling.

The

system operator

calls

the terminal

using

the phone

number

print-

ed

by the CCP as

provided

on

the TERM-

NAME statement.

AA Automatic

answering.

The

CCP answers

calls from this

terminal.

MA Manual

answering.

The system operator

answers

the calls

from this

terminal.

MLTA, AA and MA are treated

the

same. For

a command

mode

switched line,

AC or MC must not be

specif ied.

B LK L-n

The BLKL parameter

def ines

the block length,

in bytes,

that is

used

for this

terminal. lt can be

specified

as 1 to 5

numeric

digits with a

valid range

of 1 tirrough

49152,

but

the

actual value is

limited

by available

main

storage. This

parameter

is required

when

specifying

attributes for any

BSC

terminal. The value used here must

be equal

to RECL

times the number

of records in

a block. Up to 255 records

can

be contained in one

block.

lf BSCA terminal online

tests are to be

run using this

attributes

set, a value of at lerast 300 must be specified

for BLKL. lf less space

is available,

the test

request

is

passed

as

data to the user

program

or

the CCP command

processo

r.

lf OUTPOLL-YES

is

specified,

the block length must be

large

enough to accommodate

the outboard

poll

list. Two

bytes

per poll

entry in POLI--LIST

are

required. lf there

are 127 entries, then

BLKL-254 would

be

the minimum

block

length.

Assignment Stages 101

/NO,

\*/

\MC>

1fii)

The

following

are

3270 display formatting

considerations:

o The

value for this

parameter

can vary from 1

to 5120

according

to the

performance

desired.

For

best

perform-

ance

this

size

should

be large

enough

to hold

the largest

output display format

that uses

this

terminal

attributes

set, the

size

of which is

printed

by the

display format

generation

routine. Performance

cannot be enhanced

bV

specifying

a larger

value.

o lf the value

is

less than

the largest

format,

display for-

mats

are

broken

into output blocks

and

performance

is

decreased.

With blocking,

the

minimum required

size is

512.

RECL-n

The RECL

parameter

defines

the record

length,

in

bytes,

that

is used for

this

BSCA terminal.

The value

must

be

specified

as 1

to 5 numeric

digits with

a valid

range

of 1

to

the value

given

for

the

BLKL

parameter.

This

parameter

is

valid

only if

the DATAFORM

pararneter

on

this

statement

has

the value

RECORD

specified.

r RECORD

)

DATAFORM { BLOCK

"

(

rvessecr

)

The DATAFORM

parameter

defines

the format

in

which

the

CCP

presents

terminal

input

dala

to the

user

program.

RECORD

indicates

the

CCP

presents

a

portion

of an

input

block as a complete

record

to

the

user

program.

BLOCK

indicates

a complete

block

(possibly

consisting

of multiple records)

is

presented

as a unit

of

data.

MESSAGE

indicates

that

all the

data

between

the

STX

and the EOT

is

presented

as one

unit

of data. MESSAGE

is required

if the

parameter,

DFF327!,

on this

statement

has

a

value

of YES.

The default value

is

RECOR

D.

TBANSP-

The TRANSP

parameter

specif

ies

whether

the EBCDIC

transparency

feature

is used in

transmission

to this terminal

The value YES

can be used onlv

for

a BSCA-LINE

state-

ment

with the XMCODE

parameter

value

of EBCDIC

(must

have

the transparency feature installed

on the

adapter).

The value YES

is valid

only

if XPRNCY'YES

was specified

in

the

$EBSC

or $ECSC

generation

control

statement. The

default, if the

parameter

is

omitted,

is

NO, indicating

EBCDIC

transparency

is not

to be

used

when

transmitting

to this terminal.

On transmissions from

a terminal,

the

line

control characters received

determine transparency.

lf a terminal sends transparent data,

the adapter must have

the transparency feature

and XPRNCY-YES must

be speci-

f

ied

on the

$EBSC

or $ECSC

generation

control

statement.

The

ITB

parameter

specif

ies whether

intermediate

text

blocks

are sent or

received

when

using

this

terminal.

The

value YES

is valid

only for

BSCA terminals.

lf ITB

is

speci-

fied

as

YES

(lTB-YES

must

also be specified

on

the

$EBSC

generation

control

statement)

then the

parameters

VARL

and

SPAN on this

statement must

have

the value

NO.

The

default value

is NO.

lNo I

vA,.L-

1

YES

i

The VARL parameter

specif ies

whether

variable

length

records

with record

separator

characters

are used

in

data transmission

to or from this terminal. The value YES

is valid

only for BSCA terminals.

The

value

YES is

not

valid

if the ITB parameter

on this statement

has

a value

of

YES. The

default

is NO.

SPAN.

The

SPAN

parameter

specif ies whether

input records

can

span input

blocks. The value YES

is valicl

only

for

BSCA

terminal

type

3735

or CPU. The value YES

is

not valid

if the ITB

parameter

on this

statement has

a value

of YES.

The

default is NO.

f

No

I

ivesl

,rB.

{}F,}

fNo

I

lYesf

VER

IFYID-

The VERIFYID

parameter

specifies

whether

the

CCp

veri-

fies

the

identification

bytes

sent

from

this terminal.

yES

indicates

the

CCP

will verify.

NO,

the

default

value,

indi-

cates the

CCP will not

verify

the lD

of this

terminal.

The

value YES

is

only valid

for

BSCA

terminals

on

switched

I ines.

Note: lf using lD

verif

ication,

all online

terminals

on a

BSCA

switched line

should have

VERIFyID-yES.

lf

one terminal

online

has

VERIFYID-NO,

anyone

can

con-

nect via

a telephone

call as the

non-verified

terminal.

DFF3270.

The

DFF3270

parameter

specifies

whether

the Display

Format

Facility

(DFFI

will be used

with

all terminals

ref-

erencing

this

terminal

attributes

set.

This

parameter

is

valid

only

for

3270 terminals

on a

BSCA line.

lf this

parameter

is

specified,

the

parameter

DATAFORM-MESSAGE

must

be specif ied

in

this statement,

and

the

SYSTEM

statement

in

the

assignment

set must

have

the

DFFPACK

parameter

specified.

The

default

value is

NO.

// BSCALINE

Statement

The BSCALINE

statement def ines the type

of BSC

line

to

be used and the features

of the line. A BSCALINE

state-

ment must

be

followed

by at least one

BSCATERM

state-

ment.

The BSCATERM

statement

defines

the terminals

that

are attached to that line. lf more than

one

communi-

cation

line

or

adapter is attached

to the

System/3, another

line

statement

can be

given

and

follows

the last

BSCA-

TERM

or

MLTATERM

statement

for

the

The order in

which

line statements

are entered

determines

the

order of priority

during

the CCP

execution.

At least

one line

statement must

be

given

for each

assignment

set,

either

BSCALINE or MLTALINE.

I Line numbers 1

and

2 are valid for System Control Program

Number

5704-SC1 . Line numbers 1

,2,3, and

4

are

valid for

^System

Control Program

Number 57O4-5C2.

"Program

Number 5704-SC2

only.

TYPE.

The TYPE

parameter

line is

used.

must

be

given

and

defines how

this

tNo )

iEsl

lYES\

(NO

J

J::l

t$;t

BSCA

l-pp I

I rvrp

I

Lt*J

(

LINE

TYPE

\

/ ^_.."_^ ^ _..^,,",^.Dr

{

,_,^,r-r,

1;1

}

I LTDEXSEND-EXcHNGrl

I

/ poLL

Lrsr-'TERMtDt,rERMt

D1 ...',

LTNENUM

I

\) - ,..-

,-l

i; [o,,,o,_,

1ffi't]j

t,xMcoDE-

l#f ,

[,POLLLIST-'termid [,termid]

.. .'l

i,NRETRY-

|

{f I f,,o."tEND-exchnsidl

lNo l. t18otl

lrss

i r

r'vvAr'

1i- t

JYESII'

lNo

U

[,DBLBUF.

[o"'u'

Assignment

Stages 103

One

of the following

values

must

be

specif

ied:

Parameter Explanation

PP Point-to-point.

Dedicated

communication

line

(leased

or private)

network

on this

line

between

processing

units is

supported

by

the

CCp. One,

and

only one,

BSCATERM

statement

must

follow ilris

statement.

CS Control

station. Multipoint

communication

line

(leased

or private)

network

on this line

is

supported

by the CCp. This processor

is

the control station. At least

one but not

more

than

45 BSCATERM

statements

must

follow this

statement.

The

pOLLLIST param-

eter

on this statement

must also

be used.

For

BSCC

support

(LINENUM-3

ano

LTNENUM-4)TypE_CS

or

TypE.pp

is

required.

SW Switched. This is

a telephone_connected

communication

line. One or more

terminals

can

be

specif ied

but only one

terminal

can

communicate

with the

CCp

at a time. One

or more

BSCATERM

statements

must fol-

low

this

statement.

MP Multipoint

tributarv

station. Multipoint

communication

line

(leased

or private)

net-

work on

this

line

is

supported

by the

CCp.

This

System/3

is

a tributary

to a controlling

processing

unit. One,

and

only one,

BSCA_

TERM statement

must

follow this

sratement

and

must

describe

this

System/3

as

a terminal.

LINENUM

The LINENUM parameter

identifies

which BSC

line

this

line

statement

defines.

The

numbers

1 and 2 identify

BSCA

adapter

numbers

1

and2, respectively.

The

numbers

3 and

4 identify

BSCC

lines

l andZ respectively

(program

Number

5704-SC2

only). tf not specified,

t_INENUM

defaults

to

line

1. Two BSCALINE

statements,

within one

set,

specify_

ing

the

same line

number

are not accepted.

lf this

BSCALINE

statement

is

defining

the display

adapter,

the LINENUM parameter

must

specify

line

2. BSCC

assign-

ment

support

(5704

SC2 only) is

implemented

wnen

LINENUM.3

or LINENUM-4

is

specified.

LTNENUM-4

requires

that BSCC-2

be

specif

ied

on the

$ECSC

generation

macro

statement

(support

for both lines).

104

xMcoDE.

{ ^*frr }

The XMCODE parameter

defines

the transmission

code

used

by

the

terminals

on this line.

lf not

specif ied,

XMCODE

defaults

to EBCDtC.

EBCDIC

is

BSCA EBCDTC

code.

ASCII

is

ASCII

code.

POLLLIST-'termid

[,termid]

. . .'

The

POLLLIST parameter

defir-res

the

order

the

terminals

attached

to this

line

are to be

polled.

This

parameter

is

valid

only for

TYPE-CS

lines.

The values

can

be

given

as

a

sublist: lDs

are separated

by

a single

comma

and

the

entire

parameter

value

is

enclosed

by apostrophes.

Any

value

within

the list

must

be a termid

of a terminal

speci-

f

ied

on a

BSCATERM

statement.

The

termid

given

in a

POLLLIST parameter

in

this

BSCALINE

statement

must

not

appear in

the POLLLIST

parameter.

of another

BSCA-

LINE

statement.

A terminal

lD

can

appear

more

than

once

in

the

same POLLLIST parameter.

The

maximum

number

of

all terminal

lDs

that can

appear

in

a

poll

list

is

127.

The

poll

list

must

be

given

for

all lines

with

TypE-CS.

Note: For

printers

attached

to a 327 1

control

unit,

the

termid

of the

terminals

must

appear

in

the values

for

POLLLIST

even

though

they

are not

input

devices.

The

printers

are

polled

for status

only when

the

CCp detects

an error

condition.

NRETRY.

The NRETRY

parameter

deflnes

the number

of retries

that

take

place

if there

is a transmission

error

on

the line

before

an error

condition

is

considered

to be uncorrectable.

A 1-

to

3-digit

value

up

to 255

is

acceptable.

lf the

param-

cter is

omitted.

the

derault

value

of 7

is

assumed.

lf

the

error

persists

after

the

specified

number

of retries,

the

error

is

logged

on the

system

console.

lf a

program

is in

control

of the

terminal,

then

an error

return

code

is return_

ed to the user

program.

lf the

terminal

is not

under

the

control

of a user

program,

the

CCp

permits

the system

operator

to bypass

or retry

the

operation.

l7I

i;i

\;l

l;\

IDEXSEN D-exchngid

The

IDEXSEND

parameter

specifies

identification

charac-

ters this CPU

(running

CCP)

sends

to

a

remote

terminal

(processing

units, 3741, or 3735 terminals). This

allows

the

remote

terminal to verify

that this

processing

unit is

the

one

the remote terminal wants to

comrnunicate

with. The

identification

characters can be specified as

any

1 to 15

extended

alphameric

characters

or any 2 to 30

hexadecimal

characters,

The

identification

characters

must

be

expressed

in the transmission code

(EBCDIC

or ASCII). lf tne

code is

ASCll, only the hexadecimal representation

can be

used. Two hexadecimal

characters represent

one byte,

and

therefore there must

be an even number of hexadecimal

characters specif ied.

The

value

is

identified

as being

hexa-

decimal by enclosing the value

in asterisks.

Example:

IDEXSEND-*C1

C2C3C4C5*

The

IDEXSEND

parameter

should

be specified only if

the

remote terminal expects to receive lD exchange

characters.

This

parameter

must

be

used if the

terminal(s)

on

this

switched line is

a 3735

terminal.

Also, this

parameter

is

valid only if the TYPE

parameter

is

SW.

DBLBUF.

The

DBLBUF

parameter

specifies

whether

terminals on

this

line

are double

line

buffered.

YES

indicates

double

buffering

is

provided

by

the

CCP;

the main

storage is re-

served

at

startup.

NO indicates

a single buffer is

provided

by

the CCP. The default

is NO. Double

buffering

gener-

ally

improves data

transmission time.

especially

in a

multiple

block

transmission

environment.

This specification refers

to

the line buffer,

not the buffer

work

area specified by the

MINTPBUF

parameter

on the system assignment statement.

WAIT-

The WAIT

parameter

specifies a

decimal delay

count. The

delay

count

is the number of seconds after

receiving

or

transmitting a block of data

that the CCP waits for the user

to receive

or transmit

another

block of data

for the same

file. The CCP

waits the

specified number

of seconds by

using the WACK ENO

and

TTD NAK

line

control

sequences

A 1- to 4-digit value up to

9999

is

accepted.

Except

when

the end of

f

ile is received

or

transmitted,

the

CCP terminates the transmission

and

posts

a completion

code if the

delay count is exhausted

between transmissions.

lf

a

value is

not

specified, a

18O-second

delay count

is

assumed.

lf a delay count

is

specif

ied. consider the time

that may be

required for such

items as device errors, halts,

and

ready l/O devices.

This

parameter

applies only

when user

programs

are com-

municating with

a

terminal on this

line.

DFFBUF-{Gt} (Prosram

Number 5704-SC2

onty)

The

DFFBUF

parameter

specif ies whether or

not

a separate

2K

buffer

is

to be

created for DFF user

PUTs. YES

indicates 2K of

main

storage

will

be

reserved

at

the startup

phase

of CCPfor this BSC

line. NO indicates

a

2K buffer

will not be reserved

and

all

PUTswill be done from the

TP

buffer.

The

default

is NO.

(Buffering

may

potentially

improve data

transmission time

and

response time by allowing

multiple user PUTs

to

be in

the

process

of transmission at any

given

time. No advantage

is

gained

if only one

BSC line is using DFF.)

lf performance

is

affected by

maximum utilization

of

the

TP

buffer. specifying

DFFBUF-YES may result in

some

perf

ormance

improvement.

ourPoLL-

{Gt} (Prosram

Number

5704-sc2

only)

The

OUTPOLL

parameter

specifies whether or

not

outboard

polling

is supported

for

BSCC. This

parameter

is

valid

only with LINENUM-3 or LINENUM-4

and only

if

TYPE-CS is specif

ied.

The outboard

polling

feature is

automatically

incorporated

at

execution

time

if

the active

terminals are 3270 only. Mixed

terminal

environments

require that

OUTPOLL-YES

be specified

in

order

to

incoroorate the feature at all times.

(

ruo

'l

1"rsi

1lse\

In

J

Assignment

Stages 105

I

// BSCATERM Statement

The BSCATERM

statement

defines

certain

attributes

of

the

terminals

on BSC lines.

lt also

references

terminal

attributes

sets

that complete

the terminal specif

ications.

The

BSCATERM

statements

must

follow the BSCALINE

statement

for which

the

terminals

are

defined.

The number

of BSCATERM

statements

allowed

depends

on the line

type;this is defined

by the

TypE parameter

on

the BSCALINE

statement"

The

maximum

number

of

terminals

allowed

in

a set is

120.

In addition,

the

maximum

number

of terminals

per

line

type is:

Control

station

line-45 terminals

Direct

attached

line-30 terminals

'Program

Number

57O4-SC2

onlv.

TE RMID-termid

The

TERMID parameter

assigns

permanent

(within

this set)

identification

characters

to the

terminal. The valid

entries

for this keyword

are two nonblank

extended

alphameric

characters

and

are the

terminal {D referred

to by the

system

operator.

There

is no

default for this

parameter.

The

value

giverr

must

be unique for each

tc'rminal

within this

set. The

value

must

not be the reserved

lD. $C.

TYPE-termtype

The TYPE parameter

specifies

the terminal

type

the

BSCATERM

statement

describes.

For

all lines,

except

BSCA

switched

lines,

all terminals

on a

line

must be

of the

same

type. (All components

of a 3270

system are con-

sidered

to be

of the same type.) Switched BSCA

lines

may have

CPU,3741,3275

switched,

and 3735 terminals

on

the same line. For Program

Number

5704-5C2

only,

terminal types

on BSCA/BSCC

control station lines may

have 327O,

CPU, and 3741 terminals

on the same

line.

CPU

indicates

all

processing

units

(5/360,

5/370,

S/7, S/3)

capable of receiving

or transmitting

over binary

syn-

chronous

communication lines,

with the

proper program

support.

There

is no default for this

parameter.

The

following

terminal

types

can

be specified:

3275M1

3277M1

3284M

i

3286Mi

3275M2

3277M2

3284M2

3286M2

3735

3741

CPU

Note: A BSCATERM

statement

is not allowed for the

3284 Model

3 attached to a3275. A 3735 tvpe

terminal

on a

nonswitched

point-to-point

line is

supported

as being

on a

control

station

line. The following

terminals

are

supported in

compatibility mode. Specify the appropriate

entry f

or the terminal type

as

follows:

Terminal Type Entry

3276

3278

3287

3288

3289

5231 2

3277M2

3284M2

or 3286M2

3286M2

3741

// BSCATERM TERMID-termid,TYPE-termtype,

ATTRID-'attrid[,attrid]

. .

.,

,coMMAND-

l)3,,t

'.o*,-rr.re

f

fff r

I,AUToERP. IEI.'

I YESI

[,TDEXRCV-exchnsidJ

[,oFFACrN-

153:3f ]

[,AD

DR

CHAR

-addnessing

characters]

[,POLLCHAR-

polling

charactersl

r,rcF-

ffi r

r06

ATTRID-'attrid

[.attrid]

. . .'

The ATTR

lD parameter

specif

ies which

terminal

attributes

sets

(def

ined

by

the TERMATTR

statement)

this

terminal

can

use.

The

f

irst

attributes

set

is ursed

in the following

cases:

. At startup.

. When

the terminal

requests

a

CCP user

program.

o When required

by a usbr

program

and

if the

attrid

speci-

fication

is

omitted in

the TERMS

parameter

on

the

assign-

ment

program

statement.

o lf no

other

specif ication

is

given

when

a user

program

acquires

this terminal

during

execution.

Attributes

sets

listed

after the first

are eligible

for assign-

ment

to this terminal

at the

followinq

times:

. When

the

terminal is required

by a user

program

and

attrid is

specified

in

the TERMS

parameter

in

the assign-

ment

program

statement.

o When

the user

program

acquires the

terminal

via

the

acquire

and set terminal

attributes

operation.

The values

given

must

correspond

with a

value

given

for the

ATTRID

parameter

on

a TERMA-|TR

statement. In

addi-

tion to the

specif ics

given

on this

statement,

the

terminal

attributes

set supply certain

other

specif ics

for this

terminal.

There is

no

default

for

this

parameter.

The ATTRID parameter

can

refer

to a maximum

of 32

attributes

sets. All the

sets

referenced

are considered in

calculating

the maximum

line

block

size

for

BSCA

lines.

coMMAND.{}3r}

The COMMAND parameter

specifies

whether this terminal

is

capable of requesting

programs. lf this parameter

is

given

with the value YES,

then

the

terminal

must have

both in-

put and output capability. Any terminal can be specified

as not being

command capable;

but, if the parameter

is

given

with the value YES and the terminal does not have

both input and output capability,

an error

diagnostic

is

given.

YES is invalid for 3735 or 3741

terminals.

There

is no

default for this parameter.

lf command terminals

are on a switched

line, the attributes

set must

specify either

automatic answering or manual

answering.

ONLINE-

The ONLINE

parameter

is used to specify

whether

the

terminal is

available

to be used at the beginning of a CCP

run.

The default

value for the

omitted

parameter

is

YES,

indicating it is

available.

A terminal

can be

connected to the system,

yet

not be

available

because

it is in the

procass

of being serviced,

or

because

no

authorized

person

is

presently

at the terminal

to use

it. A value

of NO indicates that this terminal should

be treated

by the CCP

as if it were

logically

offline at

startup.

This

specification

can be overridden

during the execution

of the CCP by the system operator.

AUTOERP (Program

Number

5704-SC2 only)

The AUTOERP parameter

selects the option of automatic

retries for terminals

in error

recovery.

The retries to the

terminal

will occur at the time interval selected via the

ERTIME parameter

on the

SYSTEM statement.

AUTOERP

requires f

ull timer support to be selected during SCP

generation.

YES

specif

ies

that automatic retries will be

done; NO specifies that they will not be done. The default

is

NO.

IDEX RCV-exchngid

The IDEXRCV parameter

specif

ies the verification charac-

ters the System/3 containing the CCP expects to receive

when communicating with the proper

remote switched

station.

The value

for this

parameter

can

be

1 to 15ex-

tended alphameric characters or 2 ro 30 hexadeci mal

char-

acters. The identification characters

must be expressed in

the transmission

code

(EBCDIC

or ASCII). lf the

code

is

ASCll, only the hexadecimal representation can

be

used.

Two characters represent one byte, therefore

there musl

be

an even number of hexadecimal characters specif ied.

The

value is identified

as being

hexadecimal

by enclosing

the value in asterisks.

Example: IDEXRCV-*C1 C2C3C4C5"

This parameter

should

only be specif ied if the remote

terminal will send lD exchange characters.

fYESI

iNo i

lNo I

lGs i

Assignment

Stages 1O1

OFFACTN.

The

OFFACTN parameter

applies

only to command

ter-

minals

(COMMAND-YES)

and

spercif

ies

the

action

to be

taken

with this terminal

when

the

terminal

operator

issues

the

sign-off

command. The

only two acceptable

values

are

HOLD

and DROP.

HOLD means

the line

continues

to be

monitored

by the

system

after

the

sign-off

commancl

is

given.

HOLD is

the

default

value for a nonswitched

lirre.

DROP

means

the

terminal

is

set in

off

line

status

after

the

sign-off

command

is

given.

The

terminal

is

no longer

monitorecl

for input

and,

if the terminal

is

connected

by a

switched

line,

the line

is

disconnected.

DROp is

the default

value for a switched

line.

The

terminal

operator

can

overridr-'

the

parameter

specified

when

using

the

sign-off

command.

ADD

R

CHAR,addressing

characters

The ADDRCHAR parameter

is the

hexadecimal

character

representation

of the

address

characters

in

the line

code

used

with

this

terminal

The value

for

this

paramerer

must

be 4 to 14

hexadecimal

characters.

The identification

characters

must

be expressed

in

the

transmission

cooe

(EBCDIC

or ASCI l). For

a

multipoint

line

(that

is,

this

processing

unit

is

a tributary

station),

this

parameter

refers

to

the

characters

by which

this

processing

unit

is

addressed

from

the host

processing

unit.

This

parameter

is

not valid

for

terminals

on a switched

line

or a

point-to-point

line.

The value

is identif

ied

as

being

hexadecimal

by enclosing

the value

in

asterisks.

For

a description

of

the valid

charac_

ters for System/3,

see

IBM System,/3

Multitine/Multipoint

Binary Synchronous

Communications

Beference

Manual,

GC21-7573.

The

terminal

address

and transmission

code

are

physically

wired

at each

terminal.

Consult

your

IBM

customer

engineer

for

the

exact

code

wired.l

'With BSC, no

two terminals

on the

sarne line

can have identical

polling

and addressing

characters.

With

the

display

adapter

(DA),

no two terminals

on the

same line

can

have identical

device

charac-

ters,

lf using

the

display

adapter

(DA-,/ES

in

the

gEBSC

genera-

tion

macro),

the

control

unit

addressing

characters

must

be

6060xxxx

and

polling

characters

must

be

4040xxxx.

PO

L LCHAR

-pol

I ing

characters

The

POLLCHAR

parameter

is the

hexadecimal

character

representation

of the

address

characters

in

the line

code

to

be

used

with

this

terminal.

The value

of this

parameter

must

be 4

to 14 hexadecimal

characters.

The

identification

characters

must

be

expressed

in

the

transmission

code

(EBCDIC

or

ASCIt).

For

multipoint

line

(that

is,

this

processing

unit

is

a tributary

station)

this

parameter

refers

to

the

characters

by

which

this

processing

unit

is

polled

from

the host

processing

unit. This

parameter

is

not

valid

for

terminals

on a

switched

line

or

point-to-point

line.

The

value

is identified

as being

hexadecimal

by enclosing

the

value

in

asterisks.

For

a

description

of

the valid

cnaracter

for System/3

, see IBM System/3

Multiline/Multipoint

Einary Synchronous

Communications

Reference

Manual,

GC21-7573.

General

poll

is not

supported

tor

327Otype

term

ina

ls.

f rrro

) ,^

lcF- 1 yES | (Prooram

Number

5704-SC2

only)

The ICF

parameter

is used

when

a

terminal is

a System/34

using

the ICF facility. Therefore,

specify

ICF-yES

if the

device is

a System/34

with the ICF facility. The

default is

NO. Refer to the Sysfem

/34 lnteractive Communication

Feature Reference Manual , 5C21.7751 .

// MLTALINE

Statement

The MLTALINE

statement is

used

to define

the

type of

communication

line

to be used

and

the

features

of

the line.

A MLTALINE

statement

must

be

followed

by at

teast

one

MLTATERM

statement.

The MLTATERM

statement de-

f

ines

the

terminals

that

are

attached to

that line.

lf more

than

one

communication

line

or adapter

is

attached

to the

System/3,

another

line

statement

can

be

given

and follows

the last

BSCATERM

or MLTATERM

statement

for

the

The

order in which

line

statements

are enter-

ed determines

the

order

of priority

during

the

CCp execu-

tion. At least

one line

statement

must

be

given

for

each

set,

either MLTALINE

or

BSCALINE.

/HoLD I

t

DROP

'

/i MLTALINE TYPE ,LIN

ENUIVI-

I:: l

t:frJ

1

2

4

o

7

8

\ PrrcEBcD/

,xMcoDE-

j PTTCBCD

i

I

conn '|

,MAXRECL-n

[,POLLLIST-'rermid[,termid]

. . .'l

.,DATARATE-

{ffi I r

r,Auropol,

lg"*f ,

lrzool

t,RcvrNr-

lo\9*t

, r,r.rnernv-f

Zf r

[,DELAY-n]

t,rlolr- lF | ,

Value

CW

Explanation

Switched

with

control station feature.

This

is

a

telephone-connected

commun ication

line

(valid

only

for

lines

supporting 1050D

terminals). One,

and only one,

MLTATERM

statement must follow

this statement.

TYPE.

The

TYPE

parameter

defines how

this line

is

used. There

is

no default.

The

following

values

can be specified:

LINENUM.

The

LINENUM

parameter

identifies

which MLTA

line

this

statement defines. The numbers 1 to 8 identify

the

MLTA line

numbers

1

to 8 respectively.

There

is no de-

fault

for

this

parameter.

Multiple

MLTALINE

statements.

within

one

set, specifying the

same line number

are

invalid.

(errceeco

)

xMcoDE-

<PTTCBCD )

(conn )

The XMCODE

parameter

defines the transmission

code

used

on this line. The value

given

must

correspond

to the

installed hardware feature

on the terminal(s)

to be used:

PTTCEBCD

indicates

paper

tape transmission

code

EBCDIC

PTTCBCD

indicates

paper

tape

transmission

code

BCD

COR R indicates

correspondence

code

43767

used as a274OM1 or 274OM2. and a 2741

uses

PTTCEBCD

or CORR.

A 5100 used as a2741 uses

PTTCEBCD or

CORR.

1

2

3

4

5

o

7

8

I:: l

Ew1

Value

PP

Explanation

Point-to-point. This is

a

dedicated com-

munication line

(leased

or private).

Orre,

and only one,

MLTATERM statement

must

follow

this

statement.

Control

station.

This

is a multipoint com-

munication line

(leased

or private).

This

processor

is

the control

station. All terminals

on this

line

must have

the station

control

hardware feature

regardless

of the number of

terminals

on the line. One or more

MLTA-

TERM statements must

follow this statement.

Switched. This is

a

telephone-connected

communication line. One.

and only one,

MLTATERM statement must

follow this

statement.

CS

SW

Assignment

Stages 109

MAXRECL-n

The

MAXRECL parameter

def ines

the

maximum

recoro

length,

in bytes,

that is

used

on

this line. lt must

be

speci-

fied

by

giving

one

to

three

numeric

digits.

The

specified

length

should

not include

room

for line

control

characters.

However,

it does

include

any

terminal

device

control

char-

acters

that

are

used.

For

example,

carriage

return

and idle

characters

inserted

by the

CCp in

output

to a typewriter

terminal

are included

in

the

record

(16

characters

at the

beginning

and/or

end

of the

message;

the

274O Model

2

with buffer receive

requires

one

character

at the

beginning

and/or

end

of the message).

The valid

range,

for noncom_

mand

terminals,

is

16

to 250

characters.

The

record

length

should

not

be less

than

the

size

of the largest

record

to be

sent

or received

from

an application

program.

lf

any

terminal

on

the line

is

a command

terminal

and that

terminaf

is

a 2740

Model

2, the

minimum

MAXR

ECL

value is

77. lf the

command

terminal

is

not

a 2740

Model

2,

the minimum

MAXRECL

value

ls

,l07.

ffofe.' Online tests initiated

by

the system

operator

require

a minimum

record

length

of 100

bvtes.

POLLLIST-'termid

l,termid]

.. .'

The POLLLIST parameter

defines

the

polling

order

for

the

terminals

attached

to this line. The values

can

be

given

as

a

sublist; for

example,

terminal

lDs

are

separated

by a single

comma

and

the entire

sublist

must

be lDs

of

terminals

speci.

fied

on MLTATERM

statements.

The

lDs

given

in the

POLLLIST parameter

must

be unique

for each

line

state-

ment.

(A

particular

lD

cannot

appear

in

the

pOLLLIST

parameter

of more

than

one

MLTALINE

statement

in

a

set.)

A terminal

lD

can appear

more

than

once in

the same

POLLLIST

parameter.

The maximum

total

number

of

ter-

minal

lDs

that

can

appear in

a

pOLLLIST

parameter

is 127.

For

terminaltypes

1050

or 1050D,

the

maximum

number

is

31.

The

poll

list

must

be

given

for

all lines

when

TypE-CS

is

specif

ied

on this

statement.

DATARATE.

The DATARATE

parameter

specifies

the data

rate

of trans-

mission

this line

is

capable

of handling;

,|34.5,600,

or

1200

bits

per

second

(bps),

A 1200

bps

data rate

is not

available

in

the U.S.A.

This

parameter.

if

omitted,

defaults

to 'l

34

(meaning

134.5 bits

per

second).

110

A 3767

used

as

a 274OM1

or a 2741

uses

300 bps. ln this

case,

specify DATARATE 134. A 3767 used

as

a 274OM2

uses DATARATE

600

or 1200.

A 5100 used

as

a

2741 uses

300 bps. In

this

case,

specify

DATARATE,I34.

AuropoLL.{}Pr}

The

AUTOPOLL

parameter

specif ies

whether

the

auro-

matic

polling

feature

is installed

in

the MLTA. Consult

the IBM

customer

engineer

to determine

if this

feature

was

instalf

ed. lt can

be

installed

it the

2740 Model

1

and

Model

2 terminals

have

the station

control feature,

or if

any terminals

in

the 1050

system

are used.

This

parameter

must

be specified for every

line

statement if the feature

is

installed

on the MLTA. lf the

parameter

is

omitted,

the

default is

NO.

RCVINT-

The

RCVINT

parameter

specif ies whether

the

receive

inter-

rupt feature

is installed

on the terminals.

The default

value

is

NO. The value YES

is

valid

only

for full

duplex

lines.

The

NRETRY

parameter

defines

the number

of retries

that

take

place

if there is

a

transmission

error

on

the line.

A 1-

to 3-digit

value

with

a

maximum

of 255 retrie:;

is

acceptable.

lf

the

parameter

is

omitted, the

default value

is 2.

lf the error

persists

after the

specif

ied number

of retries,

the error is logged

on

the system console. lf a

program

is

in

control

of the terminal,

an

error return

code is rr:turned

to the

user

program.

lf the terminal is not under

control

of a user

program,

an

error

message is sent

to the

system

operator.

f

No

I

1

Yesi

NRETRY.{*}

(pg )

(600 )

(

rzoo)

DELAY-n

The DELAY parameter

defines the

delay time

for control

station

type

MLTA lines

after the

poll

list is

used and be-

fore

polling

starts again.

This time is

given

in tenths of a

second. lf the

number

15 were

given,

this would mean

one

and a

half

seconds.

The maximum value

that can

be

given

is 256

(25.6

seconds).

lf this

parameter

is not

specif

ied,

there is no

delay.

(

ves'l

rruLr-

1 r'i- I

The

TIOLT parameter

specifies whether

the

terminals

on

this line are

allowed to request

an online

test. The default

is

YES. This

parameter

does not

affect the capability

of

the system

operator to initiate

an online test.

NO

should be specified only if

five

r:onsecutive

nines

(99999)

must

be

entered

as

data.

Notes:

1. No

additional

main

storage is

required

to utilize

the

online test

function.

2. Online test requires

a minimum record

length of 100

bytes.

// MLTATERM

Statement

The MLTATERM

statement

defines

certain

attributes of

the terminals

on

MLTA lines. lt also refers

to a terminal

attributes

set that

completes

the terminal

specif ications.

The MLTATERM

statements

must

follow

the MLTALINE

statement,

The

number

of MLTATERM

statements

allowed depends

on

the

line

type. This is

defined

by the TYPE

parameter

on the MLTALINE

statement. The

maximum

number

of

terminals

allowed in

a set is 100.

// MLTATERM TERMID-termid,TYPE-termtype,

,ATTRID-'attrid

[,attrid]

. . .' ,COMMAN" l]:rt

[,ADDR-xx]

t,oNLrNE-l,y$fi t,er'trcote-nt

t,PourcoMP-nl

[,oFFAC;rN

l3::?l t

TERMID-termid

The TERMID

parameter

assigns

permanent

(for

this

set)

identification to this

terminal The

valid entries for this

parameter

are any two (exactly

two) nonblank

extended

alphameric characters. There

is no default

for

this

param-

eter.

The

value

given

must

be

unique

for each

terminal

within thisset. The

value must not be the reserved lD,

$C.

TYPE-termtype

The TYPE

parameter

specif

ies

the

terminal type this

MLTATERM

statement describes.

All terminals on any

MLTA line

must

be

identical;

(for

example, 27405, or

274OSC, or 1050). lf a 1050 system

is

being

described,

refer to the

parameters

PINCOMP

and

POUTCOMP

on this

statement

for further

component description.

Any one of the following

terminal

types

can be specif ied:

Character

to

Specify

1050

1

050D

2740

2740C

2740D

2740DC

2740Dr

2740DTC

2740M25

Terminal and Features

1050

on a nonswitched line.

1050

on

a dial

(switched)

line.

2740

Model

1 without

additional

features

on

a nonswitched

line.

2740 Model

1 with longitudinal

re-

dundancy checking

(LRC)

feature

on

a

nonswitched

line

(see

note).

2740 Model 1

without additional

extra

features

on a dial

(switched)

line.

274OModel

1 with longitudinal

re-

dundancy

checking

(LRC)

feature

on

a dial

(switched)

line

(see

note).

2740

Model

1 with transmit

control

feature

on

a dial

(switched)

line.

2740 Model 1 with transmit control

and longitudinal redundancy

checking

(LRC)

features

on a

dial

(switched)

line.

274O

Model

2

with station control

feature on

a nonswitched line.

Assignment

Stages 1 11

Character

to Specify

2740M258

2740M25C

2740M25CB

27405

27405C

2741

2741D

CMCSTD

SYSTC

SYSTDC

SYSTSC

Terminal

and Features

2740 Model

2

with station

control

and

buffer receive

features

on a

non-

switched

line.

2740 Model

2 with

station

control

and longitudinal

redundancy

checking

(LRC)

features

on

a nonswitched

line.

2740

Model

2 with

station

control,

longitudinal

redundancy

checking

(LRC),

and

buffer

receive

features

on

a

nonswitched

line

(see

note).

274O

Model

1 with station

control

feature

on

a nonswitched

line.

274O Model

1 with station

control

and longitudinal

redundancy

check-

inS

(LRC)

features

on

a

nonswitched

line

(see

note).

2741

on a

nonswitched

line

(see

note).

2741

on

a

dial

(switched)

line

(see

note).

Communicating

Magnetic

Card

SELECTRIC@

Typewriter

on

a dial

(switched)

line.

The

CMCST is

sup-

ported

to the

extent

that

it functions

identically

to a

2741D.

System/7 functioning

as

a

2740 with

longitudinal

red

undancy

checking

(LRC)

feature

on

a nonswitched

line.

The

System/7

is

supported

to the

extent

that it functions

identically

to

a 274OC.

System/7 functioning

as a 2740

with

longitudinal

red

undancy

checking

(LRC)

feature

on

a

dial

(switched)

line.

The

System/7 is

supported

to

the extent

that it f

unctions

identicallv

to a 274ODC.

System/7 l'unctioning

as

a 2740

with

station

control

and longitudinal

re-

dundancy

checking

(LRC)

features

on a nonswitched

line. The

System/7

is

supported

to the extent

that it

func-

tions identically

to a

2740SC.

Note: 'fhe

3767

terminal

can be

used under

CCp

to

simulate

the

following

M

LTA

terminals:

274OC,

274ODC,

2740M2SC8,

274OSC,

2741,

2741D. Restrictions

on

assignment

when

using

the

3767

as one of these

terminals

are under

the

MCODE

and

DATARATE

parameters

of

the

M

LTALI NE

statement.

The

5100

portable

computer

can

be used

under

CCP to

simulate

the following

MLTA

terminals:

2741

and 2741D.

Restrictions

on assignment

when

using

the

5100

as

one

of

these

terminals

are listed under

the XMCODE

and

DATARATE

parameters

of the MLTALINE

starement.

ATTRID-',attrid

[,attrid]

. . .'

The

ATTRID parameter

specifies which

terminal

attributes

sets

(defined

by the TERMATTR

statement)

this

terminal

can use.

The first

attributes

set is

used in

the

following

cases:

o At startup.

o When required

by a user

program

and if the

attrid

speci-

fication

is

omitted in

the

TERMS

parameter

on the

assignment

program

statement.

o lf no

other

specification is

given

when

a user

program

acquires

this terminal

during execution.

Attributes

sets listed

after

the

f

irst

are eligible

for assign-

ment

to

this

terminal

at the

following

times:

o When

the terminal

is required

by a user

program

and

attrid

is

specified in

the TERMS

parameter

in

the

assignment

program

statement.

o When

the

user

program

acquires

the terminal

via

the

acquire

and

set

terminal

attributes operation.

The values

given

must

correspond

with

a value

given

for

the ATTRID

parameter

on a TERMATTR

statement.

ln

addition to the

specif ics

given

on this

statement,

the ter-

minal

attributes

set supplies

certain

other specif ics for this

terminal.

There is no

default for

this

parameter.

The ATTRID

parameter

nan

refer

to

a maximum

of 32

attributes

sets.

1'12

oNL'NE.{ffi}

6oMMAND.

{ }Pr}

The

COMMAND

parameter

specifies whether

this terminal

is

capable

of requesting

programs.

lf this

parameter

is

given

with

the

value YES.

then

the terminal must have

both input

and

output

capability. Any terminal

can be

specified as

not

being command

capable,

but

if

this

param-

eter is

given

with

the value

YES,

and the terminal

does not

have

both

input

and

output

capability,

an error

diagnostic

is

given.

There

is no

default for

this

parameter.

ADDR-xx

The

ADDR parameter

is

the

two-hex

character

represen-

tation

of the transmission

line

code

of

the

terminal

address.

The terminal

address and

transmission

code are

physically

wired

at each

terminal.

Consult

yorlr

IBM

customer

engi-

neer for the exact

code wired.

The ON LINE

parameter

is

used to specify whether

the

terminal is

available to be

used at the

beginning

of a CCP

run.

The default value for

the omitted

parameter

is

YES.

A value

of NO indicates

that this terminal

should be treat-

ed

by the CCP

as

if it were

logically

off

line

at

startup.

This

specification can

be overridden during

the execution

of the

CCP by the system

operator.

PINCOMP-n

The

PINCOMP

parameter

is used

only

for 1050

terminals.

This

parameter

specif ies the input

device

for

a 1050

system

specified as a command terminal

and indicates

the compon.

ent

from

which

the CCP receives

thL' terminal

operator's

input

commands. For

a noncommand

terminal,

either this

parameter

or the

POUTCOMP

parameter

is required.

Both

can be specif ied if

the. terminal has

both input

and output

capability.

The

following

numbers

apply

for

the 1050

system:

1

indicates keyboard

2 indicates reader 1

3 indicates reader 2

POUTCOMP-n

The

POUTCOMP

parameter

is

used only

for 1050 terminals.

and specifies the

principal

(or

only) output

device

of

that

terminal. This

parameter

is required

for

a

1050

system spec-

if ied

as a command terminal

and

indicates

the component

to which

the CCP sends messages to the terminal

operator.

For

a

noncommand

terminal,

either

this

parameter,

or the

PINCOMP

parameter

is required.

Both can

be

specified if

the terminal has

both input and output

capabilities:

The

following

numbers

apply

for

the 1050

system:

5 indicates

printer

1

6

indicates

printer

2

7 indicates

punch

1

8

indicates

punch

2

oFFAcrN

{39b3}

The OFFACTN parameter

is

used only for command ter-

minals

(COMMAND-YES).

This

parameter

specifies

the

action to be taken

with this

terminal when

the terminal

operator issues the

sign-off command. The

only two ac-

ceptable values

are

HOLD and DROP.

HOLD means

the line

continues to be

monitored

by the

system after the sign-off command

is

given.

HOLD is the

default value

for a nonswitched line.

DROP

means

that, when the sign-o{f command

is

given:

o lf the terminal is

connected

by a nonswitched

line, that

terminal's status is changed

from online to of

f

line.

o lf the terminal

is

connected

bV a switched

line, the line

is disconnected.

DROP

is

the default

{or a switched

line.

The terminal

operator can override

the parameter

specified

when using the

sign-off command.

// PORTLINE Statement

(Program

Number

5704-SC2 only)

The PORTLINE statement

def ines

how

the

BSCA.

BSCC,

or SIOC

portline

is to be divided

into ports

and the size of

the line

buffers. The PORTLINE statement should

be

entered

after the SYSTEM statement or after the last

TERMATTB statement. One

POR'f

LlNE statement

may

be

entered for each BSCA, BSCC or SIOC

line

supported.

Assignment Stages 1 13

The

PORTLINE statement

foll:ws this

format:

//

PoRTLTNE

MoDE-1

Primarv

!

I Secondary

J

TYPE-

sroc

S

LINE

1

LINE2

2

LINE3

3

LINE4

4

TTASK

T

TYPE.

BLKL-

.I

'I

l 252

MAXMSG

n

,AOPORT-N

,NAOPORT.N

[,PO

RTPR

F

X-portpref

ix]

[,rt.oor-J EBCDIc

I'l

r lAscil lJ

I

'BSC

linr:s

one

through

4 only.

r

lpRruanv

I

\;;"""'^"'I

I

MODE

IISECONDARY

I i '

rls t)

This

specif

ies

which

system

is

to be the

pR

IMARy and

whrch

system

is

to be

the

SECONDARy. lt is

the

user,s

responsibility

to ensure

that

one

system

is

defineo

as

PRIMARY and

the

other

system

is

defined

as

SECONDARy.

lf both systems

attempt to execute

a pUT instruction

simultaneously,

the PRIMARy system

will execute

its

PUT

instruction

f irst.

The TYPE parameter

must be

given

to define what type of

portline

is

being

used.

One of the following

values

must

be

specified:

I

i

[**,,*".{*}]

'

[or.rr,,.{Wr}]

'

Parameter

stoc

e

LINE

1

through

LINE4

1

through

4

TTASK

T

Explanation

Serial

input/output

channel.

Channel

connected

systems

communication

is

supported

by CCp. Allows CCp programs

to pass

information

over

an

SIOC

chan_

nel

from one

System/3

Model 15D to

another

System/3

Model 15D. See IBM

System/3 Model l5D Channel Connected

Systems Program Reference and Logic

Manual

,

GC21-5,|99. (program

Number

5799-WNK

is

also

required.)

Portline

over

BSC

lines.

Allows

CCp

programs

wratten

to communicate

over

an

SIOC

channel

to also

communtcate

over

a BSC

line.

Task-to-task.

Allows CCp

programs

to

pass

information from one CCp

task

to

another

ccP task

within the same

System/3

Model

15D. This

is tike

SIOC

tasks

passing

information

over

the

SIOC

channel

to another

SIOC

task

executino

in

another

system.

[*o,, lGq fl '

L In ,J

nr rr

-

J

n I

--''' )

zsz

(

The

BLKL parameter

def

ines

the

block

length,

in bytes,

for

the SIOC

channel

buffers. lt can

be

specified

as one

to

five

numeric

digits

with a valid

range

of 2'2to 49152 (all

necessary

lOBs

will be

added

to the length

to enable

the

block

to transmit).

The

parameter

defaults

to 252 if not

specif

ied. This

parameter

is

not used

for pORTLINE

operations

other

than

SIOC.

MAXMSG-rr

The

MAXMSG

parameter

specifies

the

maximum

number

of bytes

of the largest

message

to be received.

lt is speci-

fied

as a

number

from I to 4g152.

This

parameter

must

be

specified. For

PORTLINE

other

than

SIOC,

this

value

will

be

the block length.

AOPORT n

The

AOPORT

parameter

specif ies

the number

of acquirable

ports

for

this assignment

set. The

nraximum

number

is

4g;

the

default is

0.

NAOPORT-n

The

NAOPORT

parameter

specif

ies

the number

of non-

acquirable

ports

for

this

assignment

set. The

maximum

number

is

49;

the default

is

0.

At least

one acquirable

or one nonacquirable

port

must

be

specif ied. The

number

of acquir,able

ports

on the

pflmary

system

must

match

the number

of

nonacquirable

ports

on the

secondary

system.

The

number

of nonacquir_

able

ports

on the

primary

system must

also match

the

number

of acquirable

ports

on the

secondary

system.

When

TYPE-TTASK

is

specified

in

this PORTLINE

state-

ment,

the

number

of nonacquirable

and acquirable

ports

must

be equal.

PO

RTPR

F

X-portname

The

optional PORTPRFX parameter

def

ines

the f irst

characters

of the generated

portnames. The portprefix

must

be

one to four alphanumeric

characters.

The name

of each

logical

port is

generated

using

the

characters

given

on the

PORTPRFX

parameter

ano

appending

a two digit

port number. The

acquirable

port

will start

with the number

0l and

tl-re nonacquirable

ports

will start

with the number

51.

xMCoDE

.fft:i" i

The XMCODE parameter

defines

the transmission

code

used

by the terminals

on

this line. lf not specified,

XMCODE

defaults

to EBCDIC. This

parameter

is valid

only

for TYPE-LlNEn,

where

n-1

,21,3,

or

4.

NRETRY.

The

NRETRY parameter

def

ines

the

number

of retries

that

take

place

if there is a transmission error

on the line. lf

the error persists

after the specif

ied

number of retries,

the

error is logged

on the system console. lf a

program

is in

control of the terminal, an

error return code is returned

to the user

program. lf the

terminal is not under the con-

trol of a user

program,

CCP

permits

the system

operator

to bypass or retry the operation. A one to three

digit value

up to 255 is

acceptable. lf the parameter

is

omitted, the

default

value

of seven

is

assumed. This

parameter

is

valid

onfy

for TYPE-LlNEn,

where n=1, 2,

3, or

4.

DB

LBUF.

The

DBLBUF parameter

specifies whether

terrninals on

this line

are to be

double line buffered. YES indicates

double

buffering is

provided

by CCP; the main

storage

is

reserved

at startup. NO indicates

a single buffer is

provided

by CCP.

The

default is NO. Double buffering

generally

improves

data

transmission time, especially for multiple

block transmissions. This

specification refers to the

line

buffer, not the buffer work area specified by the

MINTPBUF parameter

on

the

system assignment

statement.

This

parameter

is

valid

only for TYPE-LlNEn,

where

n='l

,

2,3,or

4.

WAIT. ] lgq

I

(n )

The

WAIT parameter

specif

ies

a

decimal

delay count. The

delay

count

is

the number

of seconds, after

receiving or

transmitting a block of data, that CCP

waits for the user

to receive

or transmit

another block of data for the

same

file. CCP

waits

the specified

number

of seconds

by using

the WACK ENO

and

TTD NAK line

control seouences.

A one-

to four-digit value up through 9999 is

accepted.

lf the

delay count is exhausted

between transmissions,

CCP terminates the transmission and

posts

a completion

code

except when the end of file is

received

or transmitted.

lf a value

is not specified.

a 180-second delay

count is

assumed. lf a delay count is

specif

ied,

consider

the time

that may be required for such

items

as device

errors, halts,

and ready l/O devices.

This

parameter

applies only when

user

programs

are

com-

municating with a terminal on this

line. The

parameter

applies only

for PORTLINE TYPE-LlNEn, where n=l

,2,

3.

or

4.

l7l

t;r

Iil'l

tv"l

Assignment

Stages 1 15

// TERMNAME

Statement

The

TERMNAME

statement

defines

symbolic

names

associ-

ated with

terminals

and subterminals

(a

subterminal

is

a

component

of a 1050

system).

This

statement

can

also

associate

a

telephone

number

to a specif ic

terminal

con-

nec{ed

by

a switched

line.

A maximum

of 254

TERM-

NAME

statements

can

be

given

for one

assignment

set.

At assignment

time, every

terminal

must have

at least

one

symbolic

name

associated

with it. lf more

than

one

sym-

bolic name

is

associated

to a specific

terminal,

the f irst

one

given

is

called the

primary

name

and those f

ollowing

are secondary

names,

The

first

TERMNAME

statement

that has

both NAME

and

TERM lD

parameters

given

for

a

specif ic

terminal is

the

primary

name for

this terminal.

Additional

TERMNAME

statements

with

the same

TERMID

and

a

different

NAME

parameter

define names

that

can

be

given

to the

terminal

via

the

/NAME terminal

operator

command.

//TERMNAME NAME-termname[.TERMID-termid]

[,MSTRNAME-termname

j [,tNCOMp-n

]

[,OUTCOMP-n

] [,PHON

ENUM-number]

NAME-termname

The NAME

parameter

specifies

a symbolic

name

to be

associated

with

either

a terminal

or an input

and/or

output

subterminal.

lf the

parameter

TERMID

is

specified

on this

statement,

this NAME

is

associated with

a

specif ic

terminal

at the

beginning

of a

CCP

run. lf

the

parameter

MSTR-

NAME

is

specif ied, this NAME

is

the name

of an

input

and/or

output

subterminal.

The

value for

this

parameter

must

be

one to six

extended

alphameric

characters;

it

cannot

be all blanks,

CONSOL,

or

ALL. lt must

be different from

any other name

given

on

any other

TERMNAME

statement.

This

symbolic name

can be

given

and

not

associated

with a

terminal at

assignment time. In

this case it

could, during

a

CCP

run,

be assigned

to a terminal by the

system

operator.

Also,

if

this

symbolic name

is assigned to

a terminal,

by us-

ing

the TERMID

parameter

on

this

statement,

it can

be

re-

assigned

to another

like terminal

by the system

operator

during

a CCP run.

TERMID-termid

The TERMID

parameter

associates

the terminal

which has

this two-character lD with the

symbolic name

given

in

the

NAME

parameter.

Specifying this

parameter

implies

the

NAME

parameter

value is

a terminal name

and therefore

the

parameters

INCOMP,

OUTCOMP,

and

MSTRNAME

cannot

be

given

on

this statement. The

termid

value must

be a termid

given

for

a terminal

on a BSCATERM

or

MLTATERM

statement.

MSTR

NAME-termname

The MSTRNAME

parameter

is used

to associate

the sub-

terminal

with

a terminal

symbolic

name.

This

parameter

should only

be used

when

describing

subterminals

and

can.

not

be specified if the

TERMID

parameter

is

specified. lf

this

parameter

is

specified, either

the

INCOMP

andlor

OUTCOMP

parameters

must

also

be

specified.

The value

given

here

must match

a

value

given

as a terminal

symbolic

name

on a

statement.

When describing

a

1050 system,

this

parameter

will

associ-

ate

the

subterminal

specif

ied

on this statement

to a 1050

system symbolic

area.

INCOMP-n

The INCOMP

parameter

specifies an input

subterminal

(in-

put

component

of a multicomponent

terminal) and implies

the

name

given

in the NAME

parameter

is

the

symbolic

name

associated

with

this subterminal. lf this

parameter

is

specif

ied,

then the MSTRNAME

parameter

must

also be

specif ied

to associate

this

subterminal

to a terminal

svm-

bolic name.

116

The value for this

parameter

must

be a single

digit

number.

For

the 1050

system

the

following

numbers

apply:

1 indicates

keyboard

2 indicates

reader

1

3 indicates

reader

2

4 indicates

any

one input

component

of

the

polled

line

OUTCOMP-n

The

OUTCOMP

parameter

specifies

an

output

subterminal

(output

component

of a multicomponent

terminal)

and

implies

the name

given

in the NAME

parameter

is

the

sym-

bolic name

associated

with

this

subterminal.

lf

this

param-

eter

is

specified.

then

the

MSTRNAME

parameter

must

also

be specif ied

to associate

this

subterminal

to a terminal

sym-

bolic name.

The value

for

this

parameter

must

be

a

single-digit

number.

For

the 1050

system

the

following

numbers

apply:

5 indicates

orinter 1

6 indicates

printer

2

7

indicates

punch

1

8 indicates

punch

2

9 indicates

any or all output

components

of the

polled

system

PHONENUM-number

The

PHONENUM parameter

defines

the

telephone

number

for

this terminal.

A telephone

number

is

required for

switched

lines using

automatic

calling or manual

calling.

The value

given

must

be

a string

of numeric

digits repre-

senting the

exact telephone

number

needed

to place

the

call

to this

terminal. This

parameter

can

be specified

only

if

the TERMID

parameter

is

given

on this

statement.

A

maximum

of 25 digits

can be

given

for

any one telephone

number.

// DISKFILE Statement

The

DISKFILE statement

is used

to describe

the

disk

files

that are used

during

the execution

of this

set. The informa-

tion given

on this

statement

must

correspond

with the

actual

type

of f

ile

as

it is

def ined

in

the

program.

A DISKFILE statement

must

be

given

for each

disk file

used

by any

program

in

this

set, specifying

the name

oy

which programs

refer

to this

file. A maximum

of 50

DISKFILE statements

are

allowecl

within one

assignment

set

for

Program

Number

5704-SC1,

and 192

DISKF

ILE

statements

for Program

Number 5704-5C2. However,

the

DSM might restrict

the number of files

that can

be

opened

during

CCP startup.

When

Program

Number

5704-SC2

is

used

and

there

are

more

than

b0

files

specified

in

the

assign_

ment

set.

an external

pointer

tist

(EpL) is

built in

main

storage.

The

size

of this

EPL

can

be either

2K or 4K bytes.

It is

put in

the

user

program

area

at startup

time.

// DISKFILE NAME-f

ilename

Ic/

,oRG-i

D

l,REcL-n

[,KEyL-n]

1r!

t,KEYPog-nl

[,MSTRINDX

1]!t l r'

lNo

l'

l

t,MlXSlZE-nl [,EXTENTS-n]2

I

Not

applicable f

or

Program

Number

5704-SC2.

-Not

applicable for Program

Number

5704-SC1.

NAME-f

ilename

The

NAME parameter

specifies

the name

by which

a

pro-

gram

refers to the

file. This name

matches

the name

on an

OCL

//FILENAME-cccccccc,

. . . statement

to be included

at startup

(unless

that file

is

suppressed).

To define a

file

more

than once:

Assignment Statements

//

DISKFILE

NAME-x,ORG-D,

RECL n

// D

ISKF I

LE

NAM

E-y,O

R D- l, R ECL-n,K

EY

L-n,KEYPOS-n

Startup OCL

//FILE NAME-x,UNlT

Dl,PACK

D1D1D1

// FILE

NAME

y,UNlT

Dl,PACK-D1D1D1.LABEL-x

The

files

can

be two read files,

or one read file

ano

one

update file.

Assignment

Stages 117

ORG.

The

ORG

parameter

specifies

how

the file is

organized

on

disk.

There is no

default

for

this

parameter.

The

following

values

can

be specified:

C indicates

consecutive

(sequential

)

D indicates

direct

I indicates

indexed

To

use

this

parameter

most

effectively,

you

should match

the keyword

value in

this

parameter

with

the access value

for

the

FILES

keyword

in

the PROGRAM

assignment

statement.

That

is,

when

processing

a direct

file

or

consecutive

file

consecutively,

use

ORG-C. When

processing

a direct file

or consecutive

file

by direct

access,

specify

ORG-D.

When

the same file

is

accessed

by both

direct

and consecutive methods,

determine

the ORG

value

by specifying

the

access method

used most

often ro open

this

file.

When

running multivolume

files,

ORG-C

(sequential)

is

invalid.

When

running

CCP/Disk

Sort Programs,

ORG-C

must

be

specified for

the work file,

and the

output

file.

RECL-n

The RECL

parameter

specifies the record

length

of the file

on disk. The record

length

on disk and

the record length

for that file

in

a

program

must

be the sarrre.

The value

given

for this

parameter

can

be

from 1 to 4096.

For

a CCP/Disk

Sort

program,

the

work

file

requires

R ECL-256.

KEYL-n

The KEYL

parameter (required

for

indexed f

iles)

specif ies

the length

of

the key in

an

indexed

file.

The

values

can be

from 1 to 29

but must

correspond

to the key

length

as de-

fined

in the f

ile on disk.

KEYPOS-n

The KEYPOS

parameter

(required

for

indexed

file)

specifies

the location

of the key within

the record.

Specif ically,

the

position

given

must

be the

position

of the first

character

of

the

key

in

the

record.

This value is

not

a

displacement

value.

This

parameter

must

be

given

for

all indexed f

iles

and can be from 1 through

9999, but must

correspond

with

the

value used when

the file was

created.

MSTRINDX.

The MSTRINDX

parameter

(Program

Number

5704-SC1

only)

specifies whether

this

f

ile

should have

a

resident

master

index.

The

parameter

can be

omitted

and the

MIXSIZE

parameter

can be used to

specify

a master index

and the main

storage

allocation

for

it. Master

index

is not

supported for the

5445,3340, or 3344 disk

f

iles.

This

parameter

is valid

only

if

the ORG

parameter

has

a value

of

l.

The MSTRINDX-YES

is

specified

and the MIXSIZE

param-

eter is omitted,

a master index

of one entry

per

index

cyl-

inder

is

built

at startup.

Note: fhe disk track index of a5445,3340,

or 3344

index file

is used

by

programs

running

under

the

CCP

that

are

identical

to programs

running

under

disk

system

management.

The

default is NO, unless

MIXSIZE-n is

specified

with

a

nonzero value indicating

no master index within

the CCP.

This master index

is external to the user's

program

and

is

the only master

index used

for

this

file

when this

program

is

run

under the CCP.

Thus,

if space

for

a master index

was included in

the user

program,

it is

not used under the

ccP.

The

master index is a table containing

entries for

tracks

in

the index

portion

of an

indexed data

file. Each

entry con-

tains a track

address

and

the lowest

key field

associated

within

that

track. The

most

efficient

size

for the

master

index is equal to the key

f

ield length

plus

two multiplied

by

the number of tracks

in the

file

index. A master

index

can

significantly

reduce the amount of time

needed to process

an

indexed file on

a

5444.

{3f

t'J

IYES{

l*o f

118

MIXSIZE-n

The MIXSIZE

parameter (Program

Number

5704-SC1

only)

specifies the number

of bytes to be allocated

to the

resident

master index for this

file. The

user

can specify up

to 16,383

bytes

for the

master

index. However,

the largest

resident

master

index that

can

be

used

is

considerably less

than

this. The minimum

value

that

can

be specified is the

number

specified for KEYL plus

five. This

parameter

is

valid

only if the

ORG

parameter

has

a

value

of I

specified.

The

following

chart indicates

results

of various

combinations

of the

MSTRINDX

parameter

and the MIXSIZE

parameter:

MIXSIZE Parameter

Nonzero Omitted

MSTR INDX

Pa

ra mete

r

YES

NO

Omitted

Valid, the speci-

f ied

number of

bytes is used for

master index

Valid, one

en-

try per

cylinder

of index

lnvalid Valid. no mas-

ter index

Valid, the

speci-

fied number

of

bytes are used

for master in-

dex

Valid,

no mas-

ter index

EXTENTS-n

The EXTENTS

parameter

(Program

Number 5704-SC2

only) specifies

the number of extents

(volumes)

for a multi-

volume

file.

The

values

can

be 2,3,

or

4;

the

value

must

correspond to the

number of extents indicated within

the

corresponding

file OCL statement

at

startup'

Assignment

Stages 1 19

Disk File Names (Not tJsing

Symbolic File Facility)

The

filename

used in

theprogram.... Program

. . . , is the

name

that

musr

be specif

ied

in

a

DISKF

I

LE

statement

during

assignment

. . .

. and

is

the

name

that

must

appear

as

the

NAME

parameter

in

an

OCL

FILE

statement

at ihe

startup

of CCP.

Assignment

Set

OCL at

Startup

//FILE NAME_

120

Relationship of Filename lJed in program to Name of File on Disk

Program

Assignment

Set

,OCL

at Startup

// FILE NAME, LABEL,

ll L0AD $CCP,--

lf the LABEL

parameter

is

specified

in

the

OCL FILE

state-

ment,

the

actual file

referred

to is

the

file

that resides

on

disk

under

the name

specified

by

that LABEL

paramerer.

OC L at Startup

(no

LABEL

Parameter)

lt LOAD $CCP.--

lf no

LABEL

parameter

is

specified in

the

OCL FILE

state-

ment,

the

actual

file

referred

to is the

file

that resides

on disk

under

the name

specified

by the NAME

parameter.

// PROG

RAM FI

LES

_'

// DISKFILE NAME

-

// FILE NAME_

Assignment

Stages 121

// SYM

Fl

LE

Statement

The

SYMFILE

statement

defines

the

symbolic

disk

file

reference

name.

This

statement

specifies

the

set

of disk

f

iles

that

the

symbolic

name

can

be validly

associated

with

by the

terminal

operator

/FILE commands

(see

index

entry:

file

command).

A maximum

of 50

SyMFILE starements

are

allowed

within

one

control

set.

//SYMI-lLE NAME-cccccc,DtSKFtLE-,ccc...

[,ccc...]

NAME-cccccccc

The NAME

parameter

specifies

a symbolic

name

that

is

used

as

a

f ile

reference

name

within

one

or more

programs

in

this

assignment

set.

This

name

does not

identify

a

parti_

cular file

(as

a DISKFILE

statement

NAME

parameter

does).

A file

command frorn

the terminal

operator

is

required

to

specify

which

disk file

is

actually

referred

to in execution

of the

program.

The file

command

must

specify

one of

the

disk f

iles

identified

in this

statement.

lt cannot

dupli-

cate

any

name

on

a DISKFILE

statement

or

another

SyM-

F

I LE

statement.

D|SKFlLEjccc.

. . [,ccc.

. .]

The

DISKFILE parameter

specifres

one

or more

file names

previously

specified

by the NAME parameter

on a

DISK-

FILE

statement.

All files

referred

to in

the

DISKFILE

parameter

of the

SYMFILE statement

must have

identical

characteristics.

A symbolic

f

ile name

cannot

refer

to both

5444 and 5445 disk files. For Program

Number 5704-SC2

the maximum

number

of files

is

191

.t

SYMFILE statements

should

not be used

to overlay

input

data

with output data when running CCp/Disk

Sort because

unpredictable

results

may occur. Symbolic files

cannot be

validly defined

for programs

requested

via

the chain

task

process

because

there is

no line

of control between

the

requester

of a chain

task sequence

and the programs

in that

sequence.

lEach

SYMFILE

statement

in

the assignment

set takes

up

one fite

making

the maximum

number

of f iles

191

.

122

Symbolic Disk File Name

The assignment

set indicates

that this name might refer

to

any one of three different disk

files,

depending on

which one

the terminal

operator wants

ICr

USe.

Each

of the

possible

disk

f

ile

names

must

appear as

the NAME

parameter

of an

OCL

FILE

state-

ment

at the startup

of CCP.

Program

//

DISKFILE NAME

_

NAME

_

II FILE NAME

_

II FILE NAME

_

// LOAD $CCP.--

This

filename

used in a

program

is

a symbolic

filename.

Assignment

Set //

PROGRAM FILES-

//

SYMFILE NAME

_ {

XYZ,)DISKFILE

_

// DISKFILE

//

DISKFILE NAME

_

// FILE

Assignment Stages 123

Symbolic F i le Reference

Before

running

the

program;

the

terminal

operator

entered

this

command:

When

the

program

is requested

by

the terminal

operator,

the

program

accesses

the actual

disk

f

ile identified

by

the

disk f

ile

name

DEF.

// FILE NAME

_

// LOAD $CCP,--

Because

in

this

OCL. the

disk

file

identif

ied

by the

name

DEF is

specified

as

being

on

the

disk

under

the

name

ABC,

the f

ile

ABC is

the

actual

f ile

referred

to in

this

run

of the

program.

124

Program

Assignment

Set

OCL

at

Startup

of CCP

NAME

_

NAME

_

LABEL

_

lf the

terminal

operator

had

entered:

/FILE

XYZ,GHI

the

actual file

GHI would

be referred

to. lf the ter-

minal

operator

had

entered:

/FILE

XYZ.JKL

the

actual file

MNO would

.

be referred

to.

/

FILE XYZ,

DEF

// PROGRAM FILES_

//

SYMFILE NAME

- f

XYZ.)OISKFILE

-

// DISKFILE NAME

_

//

DISKFILE

//

DISKFILE NAME

-

// FILE

Two Filenam* Used

in a Program Refer to the Same

File

Before

running the

program,

the terminal operator

entered

this

command:

By

using a symbolic

file,

the same

file

is

used

under

two names,

perhaps

in order

to

orocess

the

f

ile in

two

different

ways

in the

program.

// DISKFILE NAME

_

IIFILE NAME

ll L0AD $CCP,--

Program

// PROGRAM FILES

-

FI

LE

Assignment

Set

OCL

at Startup of CCP

GHI,

JKL'

/FILE

XYZ,

DEF

Assignment Stages 125

// PROGRAM

Statement

The

PROGBAM

statement defines

the logical

structure

and the resource

requirements

of a

user

program.

One

PROGRAM

statement must

be

given

for each

program

that can

be requested

by

a

command

terminal

during

the

execution

of the

CCP

using

this assignment

set. A

maximum

of 255

program

statements2 can be entered

within

one

assignment

set. This restriction

does not

apply to Program

Number

5704-SC2;

therefore

the

maximum

number

of

programs

is limited

only

by other

application-dependent

variables.

For

additional

discussion

about

the

programming

languages

supported,

see IBM System/3 Communications

Control program

Programmer's

Reference

Manual

, GC21-7579.

lVote.'

Unit

record

devices

do not have

to be specified

onthe

//SYSTEM statement.

lt is

dynamically

allo-

cated from DSM. However,

if the device is

not

immediately

available,

the

requested

program

is

rejected.

lFor Program

Number 5704-SC2

only.

"For Program

Number 5704-SCl only.

'For Program

Number 57O4-SC2,

these codes may also

be specif ied

R1, F1, R2, F2

D1A, D1B,

D1C. DlD

D2A, D2B, D2C, D2D

D3A, D3B, D3C, D3D

D3E, D3F, D3G, D3H

D4A, D4B, D4C, D4D

D4E, D4F, D4G, D4H

IiPBOGRAM NAME-pgmnarne

[,MRTMAX

n I,NEVEREND

lH]

{sHR/

[,PRtNTER,

.'NO . ]

/ves\

\:' / (:,/

t,MFCUt-(R

) t[,MFCU2.(R

) l

(b) {b)

\:,) (t,/

[,MFCM1-(R

) l[,MFCM2-.1

R ) f

{to) {tot

\;') rl'r

LRP1442

1,R ) I 1N3741-\

^' l 1

lfo\ rl,o)

[,PGMDArA.l]9^\

l

t

]EJ

T.ENDMSG-

{}:r} , r,R25o1-{H}

,

[.TERMS-'termname[/attridl [.termname[/attrid]

I . . .,1

I risu- lr I

l,FlLES-'filename/access | /i NOSHR| 1,..., I

L L {rsonr}J J

[''o"".{w'1]

[,PR

UF$Z-format name]

[,PRUFLNG-nnnnl

[,DFFMTERM-n] [,DFFNDF-n] [,DFFSFDT-n]

[,MORCOR-n]

r,to*t-

l!9|I I [.ExEcF,n,.,..lNo

l.'

r

"--"' IYESI' "'"''VE31

r

r,r*,o",r"-Jfffi|,

I r,rasrsrze-n1'

r,pGMFrND-

l)3rl

,'

126

NAME-pgmname

The

NAME

parameter

def ines the name of a

program

that

resides

on a

user's

CCP

pack

specilied in

the

PACK

param-

eter. The name must be

one to sill

extended

alphameric

characters. However, it cannot

start with a

$

or a

numeric

character except as indicated

in

the

following

list:

$CCPDD

$CCPCL

$ccPoP

Exceptions:

$CCPDD

- can be included to dump all storage dumps

from

$CCPFILE

or

$CCPDUMP

(5704-SC2)

to

printer

while

CCP

is running.

Include the

following

statement.

// PROGRAM NAME.$CCPDD,PRINTER.YES,

PGMDATA-NO

For Program

Number

5704-SC2

only. the

$CCPDD

program

statement does not

need to be included in

the

assignment set; a standard entry is made by the system

program.

lf a

program

statement for $CCPDD

is en-

tered,

it is ignored.

This is

to assure that

$CCPDD

will

be available during

execution of CCP.

$CCPCL

and

$CCPOP

- can be

included

to dynamically

close and

reopen

disk

files.

Include

the following

statements:

// PROG RAM

NAME.$CCPCL,MRTMAX.l

// PROGRAM

NAME-$CCPOP

$FCOMP

cannot

move

or

back up data areas

if the

f

iles

have

been

opened or

closed by

$CCPCO, $CCPCL,

or

$ccPoP.

For

a

descrrption of dynamic close/re-open

, see

Disk File

Close/Open Facility.

o CCPFMT

- can be included to find formats

that

have

been

added

or updated since startup, and to update

the

DFFSFDT value

(in

the

PROGRAM

statement).

For

more

information

on CCPFMT

refer

to the

Format Find

Routine in

the

3270 Display

Format Facility

(DFF)

section of the

l8M System/3

Communications Control

Program Programmer's Reference Manual

, GC21-7579

or the IBM System/3

Model l5 Communications Control

Program

System

Operator's

Guide,

GC21-7619.

MRTMAX-n

The

MRTMAX

parameter

specifies

that the

program

is capa-

ble

of servicing

multiple

requesting

terminals, and the

num-

ber

of terminals

it is capable

of servicing

at

one time. For

a

discussion about

multiple requesting

terminals, see

IBM

System/3 Communications

Control Program

Programmer's

Reference

Manual

, GC21-7579.

lf this

parameter

is

omitted,

it indicates that this

program

(a

single

requester

program)

is not capable of servicing

multiple requesting

terminals.

The

valid range

of

numbers

for

this

parameter

is 1 to 239.

MRTMAX-1

must be specified

for

the dynamic

close

facility,

$CCPCL.

NEVEREND-

The

NE'/EREND

parameter

specifies

whether the

program

is never

ending. The

term never ending

defines a program

that, once

it is initiated and

loaded

into

main

storage. re-

mains

in

main

storage

for a

relatively long time. lf a re-

source

conflict occurs

and

either the

requester

or owner

is

a

never-ending

program,

the requester

is reiected.

The

PRINTER

parameter

specifies

whether the line

printer

is used in the

program.

The default

is NO. SHR indicates

the

program

uses the

printer

but

will share it with other

programs

running under CCP.

However, if

SHR is specified

the

output

can be

interleaved

with other

prbgram's

output.

R2501

-

fruo )

l"'si

tN9 r

PRINTER-{YESI

{sH

n}

tNo I

1"''i

This

parameter

specif

ies

whether

program.

The default

is NO.

the 2501

is

used

in

the

Assignment

Stages 127

MFCUl

MFCU2

MFCM1-

MFCM2

These

parameters

specify

how

the MFCU

and

MFCM

hop-

pers

are used

in

this

program.

The following

explanations

apply:

Parameter Explanation

Combined

file. Specify

C if this

program

uses

this hopper

for combined

input

and

output.

Reader/punch.

Specify

RP

if combined

does

not

apply

and this

program

uses

this

hopper

for both

input

and

output.

Reader

only. Specify

R if this

program

uses

this hopper

for input

only.

Punch

only. Specify P

if this

program

uses

this hopper

for output

only.

Default

value

if this hopper

is not

used

in

this

program.

RP1442-

This

parameter

specifies

how

the 1442

is

used

in

this

program.

The following

explanations

apply:

This

optional

keyword

specifies

whether

the

3741

(as

a

unit

record

device)

is

used

by this

program.

The

default

is

NO.

The following

explanations

apply:

Parameter Explanation

Specify

RP

if this

program

uses

the 3741

tor

both

input

and

output.

Specify

R if this

program

uses

the

374,l

as

input.

Specify

P

if this

program

uses

the 3741

as

output.

NO

is

the

default

value

if

the

3741

is not

used

by this

program.

N3741

li,l

{

fi'/

(R

)

/

i"\

RP

NO

\H,1

li,i

Parameter

c

Explanation

Combined

f

ile.

Specify

C if this

program

uses

this

hopper

for

combined

input

and

output.

Reader/punch.

Specify

Rp

if combined

does not

apply

and

this

program

uses

this

hopper

for both

input

and

output.

Reader

only.

Specify

R

if

this

program

uses

this

hopper

for

input

only.

Punch

only.

Specify

p

if

this

program

uses

this

hopper

for output

only.

Default

value

if the 1442

is

not used

in

this

program.

RP

PGMDATA.

{E}

The PGMDATA

parameter

specif

ies

whether

a

program

request

from

a terminal

can

have

data

entered

with it. The

default

value

if the

parameter

is

not

given

is

yES. lf a

terminal

operator gives

data with

the

program

request.

and

the value

in

this

parameter

is

NO,

then

the

terminal

opera-

tor receives

an error

message.

A program

specified

as

serv-

icing

multiple

requesting

terminals

(parameter

MRTMAX)

must

not

specify

PGMDATA-NO.

lf pGMDATA-yES

is

specified,

the

requesting

terminal

is

not

required

to enter

data. However,

the

program

must

be

able

to handle

zero

data

length

input.

lf PGMDATA-NO

is

specified,

any

program

requesr

con-

taining

data

is

rejected

by

the

CCp.

PGMDATA-YES

must

be

specified

for CCp/Disk

Sort

pro_

grams

to do

an

accept

input

operation

to free

the

console

if it was

the

requesting

device,

and

a release

terminal

operation

if the

requesting

device

was

a terminal.

ENDMSG.{E}

The ENDMSG parameter

specifies

whether the terminal

that requested

this program

will receive

a message

from

the

CCP

when:

The program

goes

to end-of-job

The program

releases

the terminal

128

NO

The

default, if

this

parameter

is

onritted,

is

YES,

indicating

that

a

message

is to be sent at these

times.

A sJ:ecification

ENDMSG-NO

indicates

that the following

four

messages

are not

to be sent to

the requesting

terminal:

S03 PROG

END-PROCEE:D

SO5 PROG

END_SHUTDOWN

SO1 PROG

REL_PROCEE:D

SO2 PROG

REL_SHUTDOWN

Use

of this

parameter

with

the

value

NO

might

be

particu-

larly

inrportant

if this

program

is requested

by 3270 type

terminals.

lf the

display

is to remain

intact

after the

program

releases

the terminal

or

goes

to encl

of

job,

ENDMSG-NO

must

be specif ied.

TERMS-'termnamel/attrid]

[.termname[/attrid]

I . .

.'

The TERMS

parameter

specif ies terminals

that

are

required

to be available

when

this

program

ls requested

to execute.

Terminal attributes sets can also be specified

f

or

these

term inals.

'The

values

for

tiris

parameter

can

be

entered

as split-values

and/or sublists.

The value

for

TERMNAME

is the

symbolic name

of a

required

terminal

and

must

correspond

to the NAME

parameter

on

a TERMNAME

statement.

Each

terminal

name

given

for

this

parameter

within

one

program

must

be

unique.

The terminal names

do

not

have

to be

assigned

to a

specif ic terminal

lD at

assignment

time. However,

tne

systern operator

must

assign

them

prior

to the execu-

tion

of

this

program.

No

two terminal

names

can be

assigned

to

the same

terminal lD.

The value

for

ATTRID

specifies a

terminal

attributes

set

to be

associated

with

this terminal

during execution

of

this

prograrn.

The value

must

be one

of the

attribute

set values

specif

ied

for

this terminal on

the EISCATERM

or

MLTA-

TERM

statement.

lf the attrid value is

omitted,

the

f

irst

attributes

set

given

on the BSCATERM

or

MLTATERM

statement apply.

The

requesting

terminal

is not normally

specif

ied

as a

re-

quired

terminal, but if it is,

the above

conditions apply.

The maximum

number

of required

terminals

allowed

with-

in

one

PROGRAM

statement is

80 or

fewer,

and the maxi-

nrum

number of specified files

allowed

within

one

PROGRAM

statement is 40

or

fewer.

depending

on the

following

formula:

where

F= the number

of

filenames

entered in

the FILES

parameter

on this statement

T= the maximum number

of required

terminals

allowed

on this statement

(s.n )

F ILES-'f

ilename/access

[/ r NOSH

R

) ]

(

rsonr)

[.filename/access,

. . .]'

The F

ILES

parameter

must

be

specif ied

if

disk

f

iles

are

used

in this

program.

The

values for

each

file

are

given

as

split-values

and if multiple

disk

f

iles

are

used,

the entire

value for

the FILES

parameter

is

a sublist.

The

value for

filename

is required

for

each

disk file

used

and must

be

a

disk file

name

as

specified in

the

program.

Each

filename

specif ied here

must

correspond

to

the

NAME

parameter

given

on a

DISKF

ILE statement

or

SYMFILE statement.

See

the formula

under the

"IERMS

parameter

for the

number

of f ilenames

that

can

be

entered.

The value for

access

is required

and describes

the

assumed

organization

and

mode

of access

of this

file

as used

by this

application

program.

For

additional

discussion

about the

value for access, see l8M System/3

Communications

Con-

trol Program

Programmer's Fleference

Manual

, GC21-7579.

T+2F<112

Assignment

Stages 129

(

SHR

] riosHn

(

rcsonr

The following

terms

can

be entered

for

the

access

value:

CO- Consecutive

output

CG- Consecutive

input

CU- Consecutive

update

CA- Consecutive

add

DG- Direct

input

DU-. Direct

input

and

update

DOt - Directoutput

lS- Indexed

sequential

input

only

ISA-- Indexed

sequential

input

and

add

ISL- Indexed

sequential

input

with

limits

ISU- Indexed

sequential

input

and

update

ISUL- Indexed

sequential

input

and update

with

limits

ISUA- Indexed

sequential

input,

update,

and

add

lA- Indexed

sequential

add

only

lR- Indexed

random

input

only

IRA-- lndexed

random

input

and

add

IRU- Indexed

random

input

and update

I

RUA- Indexed

random

input,

update,

and

add

lO- Ordered

indexed

load

IOU- Unordered

indexed

load.

This

optional parameter

specifies

whether this file can

be

shared with another

program

while this program

is

execut-

ing. The

CCP

allows

the

sharing

of disk files

in either

input

or update

mode but the sharing

of the same

record

at the

same

time is

prohibited

within the

CCp. SHR,

the

default

value

for input. update,

and add files

indicates

this file can

be

shared

with another

program.

NOSHR.

the

default

for

load files,

indicates

this

file

is

not shared

with any

other

program

during execution

of this

program. Files

that are

defined

more than once

within the same

program

cannot be

opened

as NOSHR. For Program

Number

5704-SC1,

SHR

must

not be specified

if the

access

is

CO, lO. lOU, CA, lSA,

or ISUA. For

Program

Number

5704-SC2,

SHR must

not

be specified

if access

is

CO, lO,

or lOU.

NOSHR must

be

specified

for CCp/Disk

Sort

work files

and

output

files.

'Notes: DO,

direct

output,

allows

the following:

1. The file

can

be

a new

file created

at CCp startup.

2. The file

is initialized

to blanks

at

CCp startup.

This elimin_

ates the need for the file to be

initialized

before

CCp

startup.

3. The user

can

code his

programs

as DU (to allow checking

for possible

synonyms

or updating

records)

but still specify

DO in

the

// PROGRAM

FILES

keyword

to

allow

steps

1

and

2 above.

130

KSORT

(Program

Number

5704-SC2)

This

optional

parameter

specifies whether

the keys

added

to an

indexed

file,

during

the execution

of the

task, should

be sorted

and merged

into

the existing

file

index.

KSORT

can

be specified

only if

the

access is lA,

lSA,

ISUA,

IRA

or IRUA. lf KSORT

is

specified,

the

file

cannot

be

shared.

^^ ^,- f

pRocRAM'

I

rAUK_.iSGiEili--

I

The PACK

parameter

specifies

the

disk

pack

that

contatns

this

program.

PROGRAM

is

the default

value

and indicates

this

program

resides

on the

pack

$CCP

was

loaded

from.

SYSTEM

indicates

this

program

resides

on

the

pack

from

which

the user loaded

DSM

(lPL).

PACK-R1

,F1,R2,F2

or D1A

through

D4H

(as

noted

above) indicates

the logical

unit

that

contains

a

program (Program

Number

5704-SC2

only).

The PACK

parameter

specif ied

for programs

$CCPCL,

$CCPOP,

and

$CCPDD

is restricted

to pROGRAM.

For

EXECFIND-YES

programs,

the

pack

parameter

specifi-

CAtiON

iS rcStriCtEd

tO

PACK.SYSTEM

Or

PACK.PROGRAM

(Program

Number

5704-SC2

only).

This

allows

CCp

to use

all 24 libraries

to contain

various

user

programs,

Placing

programs

or formats

in

a

library

designated

by

a

physical

unit may

cause

resident

CCP

to expand

bv 2K

Dytes.

PRUFLNG-nnn

The PRUFLNG

parameter

specifies

the size

of the

program

request

under format

(PRUF)

input

data

coming from

a

3270 screen. PRUF

allows data

with

the

program

requesr

to exceed

the restriction

of up

to 78

characters

normallv

associated

with non-PRUF

program

requests.

'For Program

Number

57O4-SC2,

the

following

codes

may

atso

be

specified:

Rl, F1, R2, F2

D.IA, D1B,

D1C,

D1D

D2A, D2B, D2C, D2O

D3A, D3B, D3C, D3D

D3E,

D3F, D3G,

D3H

D4A, D4B, D4C, D4D

D4E, D4F, D4G, D4H

Specifying this

keyword indicates that the

PRUF option

should be used during execution of

this set.

The

PRUF

option causes

all text

received with a 3270

program

request

to be

passed

to the

program.

(Without

PRUF,

only the

first

data

field

from

the

3270

screen

is

passed

to the user

program

as data with the

program

request.)

lf you

specify the

PRUFLNG

parameter, you

cannot specify

PGMDATA-NO.

For non-DFF

formats,

the length

you

specify indicates the

maximum number of text

characters that can

be received

from

the 3270 screen as

a result of the

program

request.

(This

includes

the 3270

text header

and all 3270

field

and

control characters.)

For DFF

for:"nats,

the

PRUFLNG

parameter

specifies the

maximum number of the text characters

(not

the size

of

the

program's

input record area) that can be received

from

t_!_e 3270

screen

for the

format

specified

for PRUF$2. For

more

information, see the IBM System/3

Communications

Control Program Programmer's Reference Manual,

GC21.7579.

PRUF$Z-format

name

The PRUF$Z

parameter

specifies the

format name

that

should be used by the Display

Format Facility

(DFF)

to

de-code the data received with the

program

request. When

this

parameter

is specified. the

PRUFLNG, DFFMTERM,

DFFSFDT,

and

DFFNDF

parameters

must

also

be

specified

on

this

statement.

For more

injormation,

see the

IBM

System

/3 Communications

Control Program Programmer's

R eference Manual, GC21

-7579.

DF FMTERM.n

The DFFMTERM

parameter

specifies the

number

of

terminals a

program

can be connected to;

therefoie,

when

MRT-programs are used this

parameter

must not

be

less

than the

MRTMAX-oarameter.

A 1- to 3-digit value from 1 through 239

can be specif ied.

lf this

parameter

is

omitted it is assumed

none of the ter-

minals serviced

by this

program

will

use DFF.

lf this

parameter

is specified, the

parameters

DFFNDF

and

DFFSFDT must

also be specified

on this statement.

DFFNDF-rr

The DFFNDF

parameter

specifies the maximum number

of display

format

names

that are

referred

to during

any

execution of this

program.

A 1-to 3digit

value from 1 through

255 can be

specified.

lf this

parameter

is omitted,

it is assumed

no terminals

serviced

by this

program

will use DFF.

lf this

parameter

is specified,

the

parameters

DFFMTERM

and

DFFSFDT

must

also

be specified

on this statement.

DFFSFDT-n

The DFFSFDT

parameter

specifies the

size of the largest

field

descriptor table of any

display

format used by this

program.

The value

for

this

parameter

can

be

fronn

1

thror-rgtr 3584

but must correspond to the largest

field descriptor

table

used, as

printed

by the display

format

generation

routine.

lf this

parameter

is

omitted,

it is

assumed

no terminals

serviced by.this

program

will use DFF.

lf this

parameter

is

given,

the

parameters

DFFMTERM

and

DFFNDF

must

also be

given

on this statement.

MORCOR-n

The

MORCOR

parameter

specif

ies additional

2K blocks

of

main storage

allocation

to the

program

for rnemory

residerlt

overlays

(MROs)

and

external buffers.

You can specify

a

one or two

digit value

from 1

through

99. lf the additional

storage

is not available at

program

execution time,

the

pro-

gram

is executed without

M

ROs. To

use the

M ROs

with

the

additional

storage,

the

program

must be

link-edited

with an

MRO option.

soFrr- J

q I'

}YES I

This optional

parameter

(used

for Program

Number

5704-SC2

only) specifies

whether this program

is

a CCP/

Disk

Sort

program.

When

SORT-YES

is

specified,

three

files must be specified

on

the FILES parameter

of the

PROGRAM statement:

o An input

file

with consecutive

input (CG)

access.

Note

that CG access

should be used

on direct and indexed

files

(maximum

of eight

input

f

iles).

o A work file with consecutive

add (CA) access and

RECL-256 specified

on the

DISKFILE statement

regardless

of the record

length of the input and output

files

(ORG-C

on the DISKFILE assignment

statement)'

o An output file with consecutive

output (CO)

access

(ORG-C

on the DISKFILE assignment

statemenl).

Assignment

Stages 131

Duplicate

filenames

between

the

three

file

accesses

are not

allowed.

These

names

must

reference

the

sort files

identi-

fied

on the

CCP/Disk

Sort

generation

OCL file

statements.

The

NOSHR parameter

must

be

specified

for

work

files

and

output

files.

Sharing

of input

files

is

allowed;

however,

unpredictable

results

may

occur

due

to updates

entered

by

sharing

tasks.

The

PGMDATA-YES

parameter

must

be

specified

so that

the

CCP/Disk

Sort

program

will

release

the requestino

terminal

when

the

program

is

loaded.

EXEcFrND.lHl

The

EXECFIND parameter

(for

program

Number

57O4-SC2

oniy)

allows

the

specification

of

execution

time

program

find

(YES),

or

program

find

during

startup

(NO).

The

default

is

NO.

Specifying

yES

forces

CCp

to locate

and

load

the

designated

program

every

time

it

is

callecl. Excessive

use

of EXECFIND

can

decrease

perrformance.

PACK-PROGRAM

or

PACK-SYSTEM

must

be specified

for

EXECF

I N

D-YES

programs.

PRtoRtrY-'l

gMA=L

t

tlow )

The

PRIORITY

parameter (for

Program

Number

S7O4-SC2

only)

specifies

the

priority

a

program

is

to have

as a CCp

task. The

default

is NORMAL.

TASKSIZE-n

(Program

Number

5704-SC2

only)

The

TASKSIZE parameter

specifies

the main

storage

size

(in

1K

blocks)

to be

allocated

by the

program,

This

size

overrides

the

program

size

(in

sectors)

contained

within

the

header

record

of the

object

program.

You

may

specify

a

value

f

rom 4

to 32. When

TASKSIZE

is specified,

EXECFIND-YES

cannot be

specified.

PROGRAM FIND

ROUTINE

(PROGRAM

NUMBER

s704-sc2

0NLY)

The

program

find

routine

(CCPPGM)

allows

a

user

ro access

a

new

or revised

version

of a

program

(on

the same or

different unit)

that was specif ied in

the assignment

set. The

use

of CCPPGM

is

governed

by the

EXECFIND

and

PGMF

IND

parameters

on

the

// PROG

RAM

statement.

The

program

find routine

is

executed under

CCP and

mav

be requested from

the console

or

from

any

command

capable

terminal.

lf EXECFIND-YES

had

been specified

on the

// PROGRAM

statement,

the

program

find

routine can

be used

to change

that status

to EXECFIND-NO,

thereby

decreasing

the

time

required

to

fetch

that

program.

PGMFTND.

{

YES

\

Not

The PGMFIND parameter (for

Program

Number

S7O4-SC2

only)

allows

the

location

of the

program

to be

changed

by

the

program

find

routine

(CCPPGM).

Refer

to

the follow-

ing

chart.

Specifying

PGMFIND-YES

allows

the

program

f ind

routine

to access

the

program

an unlimited

number

of

times.

Specifying PGMFIND-NO

prohibits

the

program

find

routine

from

accessing

the

program,

unless

EXECFIND-YES

is

atso

specified.

lf

pGMFtND-NO

and

EXECFIND-YES

are both

specifiecl.

the

program

f

ind

routine is

allowed

to access

the

program

only one

time.

lf PGMFIND

is

not

specified.

the

program

find

routine

can.

not

access

the

program,

unless

EXECFIND-yES

is

speci_

fied. In

this case,

the

prqgram

find

routine

has

access

to

the

program

an unlimited

number

of times.

The effects

of the PGMFIND paranreter

are

different

from

the

effects

of

the EXECFIND

parameter.

With

pGMFIND,

the system

performance

is not

impaired,

and

no restriction

is

placed

on

the

location

of the

application

programs.

PGMFIND

Not

specified

EXECFIND

CCPPGM

access

rs

not

allowed

132

EXECFIND

programs

must reside

on

the CCP

program

or

system

pack,

whereas

PFMFIND

programs

may reside

in

any simulation

area library.

The

program

find

routine

can

be applied to all versions

or copies

of a

program

in

any

simulation

area

to which

CCP

has

access,

assuming

that

the

program

had

been defined in

the assignment

set. (CCp

has

access

to the system

pack,

program

pack,

F1,

81, F2,

and

R2,

as well as

to any

physical

simulation

area

that contains

application

programs

or

DFF formats

that

are

currently

being used.)

The

use of CCPPGM may

cause

the assignment

set

being

executed

and its

assignment

set source

to be inconsistent.

When

programs

are

found,

the

assignment

set source

should

be updated

to reflect

the revised

status

of the

program.

and

updates

should

be

made

to the

PACK

parameter

if

necessary.

To use

CCPPGM,

make

the

following

entries

in

the assign-

ment

set:

i/ TE

RMATTR

ATTR

I D-O4,DATAFORM-MESSAG

E.

DFF3270.NO

// PROG

RAM NAME-CCPPCIVI.ru

CVC

N END-YES,

ENDMSG.NO

For

additional information

on the

use

of CCPPGM,

refer

to the IBM System/3 Model l5 Commttnications

Control

Program

System Operatar's

Guide,

GC21-7619.

y'Vote;

When

CCPPGM

is included

in an

assignment

set,

ATTRID-04

is

required

for Program

Find

but may

also be

used

for FORMAT

FIND

(CCPFMT).

FORMAT

FIND

ROUTINE

(PROGRAM

NUMBER

5704-SC2

0N

LY)

The format

f

ind

routine

(CCPFMT)

makes formats

that

have

been

created

or modified

by DFGR

or

pFGR

in

another

partition,

available

to

programs

in

the

current

assignment

set. The

routine

is executed

under

CCp and

performs

the following

functions:

o Places

the current

object library

C/S

(cylinder/sector)

location

of

the

format

into

the format

index

in

$CCPF

I

LE.

. Updates

the DFFSFDT

value

of the

pROGRAM

assiqn-

ment

statement.

To

use

CCPFMT, make

the

following

entries in

the

assign-

ment

set:

// TE RMATTR

ATTR ID-O4,DATAFORM.M

ESSAG

E.

DF

F3270-NO

// PROGRAM

NAME-CCPFMT,NEVEREND-YES,

ENDMSG-NO

The

routine is

invoked from

either

the system

operator's

console or

a

command

terminal.

For

additional informa-

tion on the use

of CCPFMT, refer

to the Model 15

CCP

System O

perator's

G uide,

GC2 1

-761

9.

y'Uofe.'

When

CCPFMT is included in

an

assignment

set,

ATTR

lD-04 is required

for format

f ind.

DISK FILE

CLOSE/OPEN

FACILITY

This facility

allows the system

operator to dynamically

close and re-open

disk

files

opened at startup. By

doing

this,

you

can merge

added

records

with existing records

in

add

files. By

closing and re-opening

an

indexed

add

file

you

can:

o lmprove

performance

for indexed random

add accesses

o Add

sequentially to an

indexed

file

more

than

once

per

execution

of CCP

/y'ote.'

Runnins

$CCPCL

will not

allow batch users

to use

SHARE-NO on any f ile

that opened at

CCP startup.

. Retrieve

added

records

without including

add data

management

in

CCP

programs

. Run

programs

in

the

non-CCP

partition

that

access the

added records

in

the closed

files for retrieval

or update

Records

loaded

to a

CCP output

f ile

remain unaccessable

to other

partitions

until

CCP

is

shutdown.

When

run

on a multivolume file. the Close/Open facility

will

close or

open the entire

file

while it is being

used in

the

current assignment set.

To

use the Disk File

Close/Open

facility,

you

must

specify

the

following

programs

in

the assignment set:

$CCPCL

and

$CCPOP.

For

a description

of the required

assignment

statements,

see the

l<eywords

NAME

and MRTMAX

of

the

PROG

RAM

statement.

Assignment

Stages 133

lf

the indexed

add

files

will

be closed,

the following

OCL

statements

should

be included

in

the

CCp

startup

OCL

to

reserve

space for

the following

files:

// FILE

NAME-$lNDEX44 (for

inctexed

add

f

ites

on 5444

drives,

Program

Number

5704-SCt

onty)

f$rruoex+o )

//FILE NAME-lStruoex+s1|

(tor

indexed

add files

on

' 5445,3340.

or 3344

drives)

llFlLE NAME-$lNDEX40

(for

indexed

add

fites

on 3340

or 3344

drives,

Program

Num-

ber

5704-SC2

onty)

ASSIGNMENT

LIST PROGRAM

The

assignment

list

program

($CCPAL)l

can

be executecr

after

the

assignment

file

build

program

(gCCl

BF)

is exe-

cuted.

$CCPAL

has

four

purposes:

1. List either

the contents

of all the

assignment

sets in

the

assignment f ile,

$CCPFILE,

or

the contents

of

any individual

set

in the f

ile,

to show

the

conrenrs

of the

set

or sets.

2. List the request

count for each

program

in

the

assign-

ment f

ile. if the

program

request

count

option

was

chosen

at

generation

time. The request

counts

can

be listed either

separately for each

set

or as

a total

for all sets.

The user

can

clear

the request

count

to 0

either

after listing

the

counts

or without

listing

the

counts.

3. List the

assignment file

direcl.ory.

4. List the

CCP configuration.

This

is

allowed

anytime

after

generation.

even before

an

assignment

run.

The

CCP assignment

list

program ($CCPAL),

can

be used

to

list

the

following

assignment f

ile

data:

o Assignment

file

configuration

record,

directory,

or

assignment

sets.

a An option

to list

and/or reset

the

program-request

count

(if request

count was

selected

at

generation).

'For more information concerning

the

execution

of $$CCPAL,

see Assignment Restrictions in this chapter (5704-SC2

onlv).

The

input for

the

assignment

list

program

is

as

follows:

. The

previously

built file

$CCPFILE.

o The

OCL

statement

provided

by the

user.

The

source

statements

must

be input from

the

system

input

device.

The

following

OCL

statements

are needed:

o The

assignment

control

statements

instructing

$CCPAL

of the

function(s)

it is to perform.

A combination

of parameters

on the

// LIST

control

statement

to def ine

the options

the

user wishes

to exer-

cise in

listing

the file,

$CCPFILE.

o The

/* statement

at

the end

of all

input

control

statements

The

output for the assignment

list

program

is as follows:

o A user selected

listing

of portions

of the

f

ile

$CCpFlLE.

o A user

selected

resetting

of the

program-request

count

within

the

file

(if

request

count was

selected

at

genera-

tion

).

All listings

are output

to

the

printer.

Keyword

parameters

are

listed

in the form used

by the

assignment

build

program

control

statements.

The

date

and time headers

of the

system information

table

(SlT)

denote

the date

and time of the

assignment

build

and do

not

represent

valid

assignment keywords.

134

// LIST

Statement

The

assignment

list

program

is controlled

by the list state-

ment, which the

user

enters from

the

system input device.

The list

statement specifies:

What is

to be

listed-an individual

set, all sets, only the

control

file

directory, or only

the CCP

configuration.

Whether

the

program-request

count should

be

printed

for

one

or all of the sets in the file.

Whether

the

program-request

count

should

be

reset

to

zero

for

one or all of the

sets

in

the file.

The statement identifier is the word lst Any number

of

list

statements can be

entered for a single execution

of

$CCPAL.

No

continuation statements are allowed. This

control statement

must

be

given

but no

parameters

are

re-

quired

on

the statement.

lf no

parameters

are

specif ied, the statement'@ntains the

following information only

:

// LtsT

All defaults

are assumed, the

contents of all the sets

in the

file

are

listed,

and

the

program-request

count

is left un-

tou ched.

SET.

The SET

parameter

specifies

which

parts

of the

$CCPFILE

to I ist.

The

value

id relers

to any

valid assignment set

that exists in

the

control

file

and

causes that set

to be

printed

provided

no

other

parameters

are included

in this statement. lf the

parameters

PGMSTAT

andlor

RESETPS

are included, the

id value refers to all

request counts

within that set.

The value ALL,the default

value, causes all assignment

sets

to be

listed

provided

no other

parameters

are

included

in the

statement. lf the

parameter

PGMSTAT

and/or

RESETPS

is

incf uded,

the value ALL reters to all

request counts with-

in all assignment sets

in

the

f

ile.

The

value D/8 causes tlre control

file

directory

(contains

the lDs of assignment

sets contained

in the

file)

to be

printed.

lf the value

SET-DlR

is

given,

no other

parameters

can be

given

on this statement.

The

value

CONFIG

indicates

the

CCP

configuration

record

should

be

printed.

lf the value SET-CONFIG

is

given,

no

other

parameters

can be

given

on this statement.

PGMSTAT.

The

PGMSTAT

parameter

states

whether the

program'

request counts should

be

printed.

The

program-request

counts

for all assignment

sets are

printed

if the

value for

the

SET

parameter

is

ALL or not

given,

the

value

YES is

given

for this

parameter,

and

the option

was chosen at

gen-

eration time. lf the

value

given

is

for

a

particular

valid

set

lD

and

the value

YES

is

given

for

this

parameter,

the

request

counts

for lust

that set are

printed.

The

default,

if

this

parameter

is omitted.

is

NO. lf the

value

YES

is

given

for

this

parameter.

and

the system

was

def ined at

generation

time as

not containing

request counts,

a

diagnostic message

is

given

and

this

statement

is

ignored.

Note: lf an assignment

build

is

run to replace the set

CCP

is

executing

from,

the

program

count

will be

reset

to zero

for

that

set.

lf an

assignment

build

is run to delete the

set

CCP

is executing

f rom, the

program

count

is lost

for that

ser.

fNo I

lvesi

tf,_.. I

l3f-,,.1

/id

l

o..

1

DrR

\

CONF

[,RESETPS-

)

\l

IGJ

fllo

lVEr;

fr.ro L

1*rl'

// LIST [SET. [,PGMSTAT-

l,

Assignment

Stages 135

RESETpS-

{ry^ | Combinations

of parameters

and their

associative

meaning

tYhS, for the LIST

statement

follows.

Whenever

a

parameter

is

omitted, the

same effect

would

occur if the

parameter

were

The RESETPS

parameter

states whether

the

program-re- given

with its

default

value.

quest

counts

should

be reset

to zero. lf tire value

yES is

given

and the value

ALL is

given

(or

defaulted)

for

the

SET // LIST

parameter

on

this statement,

the

program-request

counts List

all

sets in

the

file.

for

all sets

in the file

are reset

to zero.

// LIST

SET-id

lf

the value YES

is

given

and a valid

set

lD

is

given

for

the List

this

particular

set.

SET

parameter

on

this statement,

the

program-requesr

counts

are reset

to zero

for

just

that

set. lf the

program // LIST

SET-ALL

request

count

is reset

for the

set

CCP

is executing

from, List all

sets in

the

file.

the

program

request

count

will

be lost

for

that execution.

The

default,fortheomitted

parameter

is

No. lf

the

value // LlsrsET-DlR

YES

is

given

with

this

parameter,

and

the

system

was List

only

the directory.

defined

at

generation

time

as not

containing

request

counts.

a diagnostic

message

is

given

and

this

statement

is

ignored. // Llsr sET-coNFlG

List

only

the configuration

record

// LIST

PGMSTAT.YES

List the

program

reguest-counts

for all

sets.

// LIST

RESETPS.YES

Reset

the

program

request-counts

to zero for all

sets.

// LIST

SET-id,PGMSTAT-YES

List the

program

request-counts

for this

set only.

// LIST SET-id,R

ESETPS.YES

Reset

the

program

reguest-counts

for this set

only.

// L IST

PGMSTAT.YES.

R ESETPS.YES

List the

program

request-counts

for all sets

and

reset

them to zero.

// LIST

S

ET.id,PG

MSTAT.YES,R

ESETPS-YES

List

the

program

reguest-counts

for

this set

and reset

them

to zero

after

listing

them.

SAMPLE ASSIGNMENT BUILD EXECUTION

As

indicated in

the

sample assignment

set

for card-oriented

assignment,

the dummy 1

and

dummy

2

program,

and the

DISKFILE

statements should

be deleted

before runnino

this

assignment set.

T

/ LOG

PRINTER

/ / LOAD

$CCpAS,Rl

*'***FILL IN PACK

ANO

UNIT

*

/ | FtLE NAr{E-$CCpFI

LETRETAIN-prUN

IT-R1r

pACK-RlRlRl

*

*+***FILL IN PACK

AND

UNIT

*

/ / F

lL

E NtU

E-tCCPt{ORK

r

RETA

t N-S, TRACKS-3

rUNI

T-R

ITpACK-Rl

RtRl

/,/ R

UN

00070000

0 008000

0

o0090000

00100000

00t I

0000

00t20000

00r 30000

00140000

00150000

0 0r 60000

Assignment

Stages 137

a

*+t(******THE FoLLo''rING

sTATFMENTs

cAN BE H00IFIED FnR youR

IS***++:}*CONFIGURATION

BUT

SOHE

I{UST

BE KEPT

rO NUru

CCPIVP. SEE

THE

*r*f+****coMtlENTS IN THIS DECK.

*

/

/ SET I D-A,

ACT

ION-CREATE

r

DFLTEXEC-YES

/,/ SYSTEM

I.IINUPA-

TbK,

MI

NTPBUF-3090,

I

/ PASSWORO*FECD,

// COMHANDL-50rDFFpACK-pR0GRAM,pGt4REQL_15

/

/ T

ERMATTR

ATT

R

I D-

I' T R

ANsLAT-No'

BL

KL-5

l2 r

t-JATAFoR

H- r,rE

ssAG

E,

/

/ VERIFYID-NO,DFF327C-YES

*

***+:F***+THTS

STMNT

rYPE REQD

FOR

CCPIVP(OR

MLTALINE

STilNTI

*

// BSCAL

INF TypF-cs

rt tNENut4-l,poLLLI

ST_ro0r0l

rl0r ll I

// BscarERM

TERMID-00rTypE-327Tr',|2TATTRID-lrcorrilAND-yEsr0FFAcrN-HoLD,

/ / ADDRCHAR-*60604040*, polLcHAR_*40404040*

// BSCATERf'l

TERt'tID-01

fTYPE-3217M2tATTRlD-l'CoMMAND-yESr0FFAcTlFHoLDr

l/ ADDRCHAR-*606OCtClorpot_LcHAR_*4O4OClCl*

/,/ BScATERM

TERMID-Io,TypE-32

77MZ

TATTRI D-r

rcoHl,iAND-No,

t/ aDDRCHAR-*61614040+rpoLLcHAR_*ClCl4o4O*

// BSCATERH

TERMI

D-II rTYPE_3277I12,ATTRJ

D-I,cOIlI.,tAND-No,

// ADDRCHAR-*6l6lClclorpcLLCHaR-*ClClcLcl+

*

/

/ TE

RHNAME

NAHE-CUODVO,TERMID-OO

// TERt.INAI',IE

NAME_CUODVl,

fE

RTJI

D-OI

/ / TERI.,INAME

NAHE-cUTDvo,

TFRlJI

D-IO

// TERI{NAME

NAHE_CUTDVI

TTERMID-iI

t

***'I*t+**IHIS SrlINT

TYPE

REQD

FOR

CCPIVP

*

I / DISKFILE

I!AI,IE-CGIVFILI,ORG-C,RECL-I6

+t+***+**THI5 STMNT

TYPE

RFQD

FOR

CCPTVP

tl

/ / DTSKF

ILE NAME-CG

IVFIL2,ORG-C,RECL_

I6

*

*++*+*+*+NOTE THAT

ONE

DISKFILE STATEI{ENT

-CGIVFTLE_

HOULD

BF NEEDED

****T****IF SYHBOLIC

FILES ARF

NOI FEING

USEO.

+

* THE

FOLLOI{ING

II{O DISK FILF STATEMENTS

ARE

FOR

EXAMPLE

ONLY

AND

+ SHOULD

8E RFMOVED

PRIOR

TO RUNNING

THIS ASSIGNMENT

SET.

*

/ / DtSKFILE NAHE-DUpHyl

rGRG_DTRECL_256

I/ DISKFTLE

NAME-OUI.II.,IY2TORG-I,REC'-64,KEYL_SIKEYPOS_I,MSTRJNDX-YESI

*

*********THIS STMN'

TYPF

RFQD

FOR

CCPIVP

IF SYHEOLIC

FILES ARE

USED.

*

/ | sYMF

ILE NAME-CGM

IL Er

D

ISKF

ILE-

rcc

I vF

IL

I

r

CG

I VF

IL 2r

*

00

I

70000

00180000

o0t

90000

002

00000

00210000

00220000

00230000

00240000

00250000

00260000

00270000

00280000

00290000

00300000

003

1o000

00 320

000

0 03

3000

0

00 340000

0035000

0

00360000

00370000

00380

000

o

0 3e000

0

o0400000

004

10000

00420000

00430000

00440000

00450000

0

0460

000

004

70000

o04

80

000

00490

00 0

o05

00000

00510000

00520000

00530000

00540000

00550000

00560000

00570000

0 c5

80000

00590000

00600000

006

1o000

00620000

00630000

0 064000

0

00650000

00660000

00670000

00680000

00690000

007c0000

oo7t0000

o0

720000

00

730000

oo

?40

000

00

?50000

00

760000

**+***+***+*+THIS SIHNT

NECESSARy

FoR

+t**)F********CAN BE CHANGED

FCR

yOUR

// PROGRAI{

NAME-CCP

IVP, PGMDATA_YE

S,

/ / F

tLES-

|

CGlvFt

LE/Cg/

N0sHR

|,

/ / PAcK-PROGRAIt4,

PRINTER-No

*

****'t****NOTE THAT

CCplVp l.iUST

BE oN

CCPIVPTPACK

AND

PRINIER

VALUES

CONFIG.

CORRECT

PACK

AT STARTUP

OF

CCP.

I Not applicable

for Program

Number 57O4-SC2.

138

t THE FOLLOI{TNG

TI{O PROGRAH STATEIENTS

ARE FOR EXAI'IPLE

ONLY

AND

8 SHOULD

8E REMOVED PRIOR TO RUNNING

THIS ASSIGNIIENT

SET'

rl

// PROGR At,t NAI.!E.DUI{I{Y1,

URTt.lAX-2'

PGI{DATA-YE5r

| | FILES-rDUMtlYl/DU/SHR'DUtlftYzlIRUA/SHRr

rPACK-SYSTE14'DFFI{TERU-41

// DFFNDF-2

rDFF

SFDT-

1

I 5C

*

// PROGRAH NAME-DUHMY2IIIIRTI{AX_z

TPGMDATA-YEST

/ I F

I L

ES

- I

DUTII{Y

I/ DU/SHR

T

DIJAI4Y 2I I

RA/

SHR

I r

PACK-SY

ST EH'

OFF

HT

ERM-2'

// OFFNDF-I

rDFF

SFDT-396

rB

*

}IARNING

IIESSA6ES

TERI'I

INAT

ION I'IESSAGE

S

007?0000

00?80000

00790000

00800000

0

c8

l0

000

00820000

00830000

0 084000

0

0 08

50000

0 08

60 000

00870000

0

0880000

0 0B

90000

Assignment

Stages 1'lo

SIENI-ON

SECURITY

- CCP

?Bq!34^f

^4!r.lG

L

aNGUAGE

Srtpp0Ry

:B9gRA! 3EOuESr-C0uNr

srAirs

?_alq !nlE qscapE

cHaqncrEni-

32To

DIspLAy

trnRMATrt\rC

- -

SIEC

PNRT

LINF SUPPNRT

TASK-TO-TASK

FAC

ILI TY SUPPOR

!q !! E.c 6c !SCA L I

\tE

S AvA

I L AB

BSCA

L

I\E-TYPq

SUPPnRT iNiN

5W

I TC HED PCRTL

I NF

BSCA

trAC

IL IT IFS

E?!DIC asCrr AUrn-RES

- BSCA-TRA\!SD

DRUF

BSCA

DEV

ICE-TYPF

SUPPORT

327

5M

I

3211vil

3284i,t

1

3

28 6u

I

7275t42

3

2_7

7^4

2

7284^

2

32StM2

3175

c

pt,

374L

!u!!E.R_lll !scc LTNES

avArl_A8

llqE L INE-TypE

stJPpnRT

cnrui

BSCC FAC

IL

IT I

FS

,'.. 5?[?JE-'$;E'

{rolEliouo'

?275u

I

7211t41

3284M

I

3 28 6r,it

t

?2-7tr42-

3217^r2

3 244^4

2

3296t42

31i5

c

olJ

j

741

For

Program

Number

5704.SC2

For Program

Number

5704-SC2

$CCPFILE

CCNFI

GURATI CN

_--c!BnL FCRTRA\ ASSEUBLEP

TIC

S KE

DT

T

LE

TT

CCP 2

T-TC-PCINT I,tULTIPCtNT

CEilT

BEC!

n9-55p

AR AYoR-X

tr

t Etr

PONSE

RESIDFNT-PCLLING-_INT

LE

TC

CCp 2

RIL-STATTCt.I

PCINT-TC-PCINT

- R

ECN

RD-SEP

AR

ATOR-xE

I

Etr

-PCLLING

$CCPFTLE

DICECTNRY

LIST

ROL-STAT

INN

GET-MESSAGE

ERVAL-

FOLL

ING

00/00

/00

RPGIT

PNRTL

I NE

GET- IJE

S

AG

E

Nrt

MB

Ep nF

NU

MB

ER OF

EX

ECUT

ION

DATE

F

ILE

SEY

ID IN

lFIS !N rHrS CCP

FILF

ENTF

I ES AVA

ILABLE F0R

TI

UF DEFAUL T SET'

ID

LAST

UPNATEN

rPE FILE

SE

TS

WITH

NOS

TA

RTUP

PROMPTS

LENGTH

CF SET

00/00/00

I

24

*a*

00/00./00

IN SFCTORS

140

For

Program

Number

5704-SC1:

SET-A

M

I

NTPBUF

MINUPA PASSIORD

t8K 3090 F

ECD

ATTRID UPCASE

TRANSLAT

lNo\0

TCCPFILE

SYSTEI.I

INFORMATION TABLE

POLT

IHE PRINTER

For Program

Number

5704-SC2:

SET-A $CCPFILE

SYSTEI.!

INFORHATION

TABLE

MINTPBUF ,^^^POLTtME PRINTER RPI442 COI{MANDL

MINUPA PASSW0RD

- - -N374I MFCU R2r0t pGr{LNG

22K 2840 FECD 6Q,2 NO NO NC NC N0 50 15

DATE HAXCHA

I! -_^ _,

ER

rt r,1E DUf,tpuNI

T

TIUE c

spclTtr,r Fauror

o4/o7t8o oo 22 0 60,2 05 N0

SET-A TCCPFILE

TERHINAL

ATTRIBUTES

TAELE

N3741

60121 NO NO

DA TA F OR

t,I

SH

I

TCHE

D

\O I.IE

S SAGE

RPI442 COMMANDL DFFPACK

I,IFCU R25OI PGMLNG

NO NO N 5C 15 PROGRAI.,I

00/00/o0

DATE T I

ME

05/0L/76 04 t6

o4/cf /80

DFFPACKDFF

INDX

PROGRAIT NO

SPAN

8 LKL

RECL I

T8

,12 N0

TABLE

xf.rc

0DE

EBC0IC

r RA\S

P

VERIFYID

NO NO NO

VARL

NO

oFF

7270

YES

For Program

Number

5704-SC1 :

JL I-d

L I

i{ENUM DAT ARAT

E

TYP

E

ESCA-I CS

LINENUM DELAYI

POLLLOOP

TCCPFILE

LINE CONTROL

RCV

I

NT D8L8UF

AUTOPOLL T

T OLT

NO

IOEXSEND

oo/00/ 0o

NRETRY CALC

BSCA IIA I T

ELOCK

SIZE RECL

7 554 i80

POLLL

I ST

CJr0lrl.0rlI

)Et -d

L I NF

NJI{

BSCA-

It6

For

Program

Number

5704-SC2:

tCC PF

I

LE LI NE

DATARATF RCVINT

TYpE auToPOLL TIOLT

dscA-

I Cs

LINFNUH qELAY/ TDEXSEND

POTLLOOP

BSCA-I 5

For Program

Number

5704-SCl:

sEr-a

POLLT

ISI

00,01,t?,Il

iCCPF

ILE TERI,II

NAL USED TAELE

CONTROL TABLE

D 8L BUF xHc00E

NO EECDIC

CALCUTATED

BLOCK

SIZE

554

DF

F

8UF

NO

00/00/00

I.iA

I T

PFCL

180

NRETRY

L INE

T

ERH

Bl oo

8l 0l

Bl l0

Bl ll

rYPE ONL I

'TE

ID CO!.IMAND

3217/84/86-A2 YES YES

1277t84/86-A2 YES YES

3277/84/86-A2 N0 YES

)217/84/86-n2 {0 YES

ATTRID PI

NCOI,IP ADORCHAR

ADDR POUTCOIIIP

I

DEXRcV

60604040

6060ctcl

61614040

6l6lcrcl

OFFACTII

HOL

D

HOL

D

POL

L CHAR

40404040

4040c

lc I

clcI4040

clclclcl

Assignment

Stages 141

'For

Program

Number

5704-SC2:

SET-A TCCPFILE

TERI.IINAL

USED TAELE CCIOO/OO

LINE---..- TYPE ONLINE

---TERr.rID coilr.tAND-

- '''oFF!cTNATTRIDacPINc0!3ur33Ef.tt3rr.,u

PcLLcFiaR

oBIS

8l 00 3?17/ 84/.e6_\2 !E! yES l1-clp I 6060!040 4C404040 NO

Br 0t zzttrst,t.eo-v.2

iEa iEi Haib i oo6ocrcl {ro(oclcl No

BI l0 3277/B4te6-r.2 Na- iES i 616l{1040 CtCI.fg4O No

Bl ll 3277/84tt6_tt2 No iEs t e

t6lclcl clctclct Nc

SET-A $CCPFILE TERMINAL NAME TABLE

Nzui{E TERMID MSTRNAME INCOI4P OUTCOMP ID PHONENUM

CUODVO OO

CU

ODVI O ].

CU1DVO IO

CU]DVI 1I

For Program Number 57(X-SC1:

SET-A $CCPFILE FILE CONTROL TABLE

FILENAME ORG OPENED RECL KEYL KEYPOS I,ISTRINDX MIXSIZ

CGIVFILI C OUTPUT 16

CGIVFIL2 C OUTPU? 16

DUMMY1 D UPDATE 256

DUMMY2 I ADD 64 8 1 YES O

SYI,IBOLIC NA]4E DISKFILE NAME/S

CGIVFILE CGIVFIL]. CGTVFIL2

For Program

Number

5704-SC2:

SET-A SCCPFILE

F ILE

CCNTRCL TAELE CC/OO/OO

FILENAI.TE ORG CPETED voLUMES RECL KEYL KEYPCs

qEIvF

IL I c quIPUr 16

cGIv.E,rL2 c clTPUr ia

quMMYl D UPDATE 256

DUMHYz I ADO E4 8 [

SYI.IBOL

IC NAHE OISKF ILE NAME/S

CGIVFILE CGIVFILI CGIVFIL2

I

I For

Proqram Number

5704-SC1:

t-

SET- A $CCPF'ILE PROGRA^,I

CONTROL TABLE OA / OO

/ OO

PROG NEVEREND MFCU/I,{ R2501 PGI{DATA DFFSFDT PACK PROG

1

NAME MRTMAX N37iII PRINTER RPI442 ENDMSG DPFI.JKA SIZE PRUF$Z

CCPIVP NO NO NO NO NO NO YES YES P

DUMMYI 2 NO NO NO NO NO NO YES YES 1280 1192 S

DU}4MY2 2 NO NO NO NO NO NO YES YES 5I2 168 S

PROG FILES TERMS I4ORCOR

NAI!{E PILENAME ACCESS SHR TERMNAME ATTRID

CCPIVP CGIVFILE LOAD NO SORT

DUMMY] DUMMY1 UPDATE YES

DUMMY2 ADD YES

DUMI4Y2 DUI{MYI UPDATE YES

DUMMY2 ADD YES

IProgrurn

size

is not printed

by assignment

list

($CCPAL)

unless

Startup has been

executed

on the assignment

set.

For Program

Number 5704-SC2:

SET-A SCCPFILE

PROGRAU

CONTROL

TABLE

PROG NEVEREND ftIFCtJ/M R25OI PGI.IDAIA.. OFFSFOT - PACK

PROE

i'ltilE T.1RTMAX'-'-

- 'Nrf+r -- ' PRINTEC---

- RPl442 - ENO;,ISG DFFI{KA SIZE

iccPDD N0 NO NU YES NO N0 YE9 lqs ?

acFiVF No N0 Naj N0- N0 No YE! YEs ?

6ixnii 2 No 16 No No No No YES YEs tq?t ll3q 5

oUsui2 2 N0 Ho ruo No No N0 YEs YES sLz 768 s

PROG EX €CF

IND SORT

NAME PGqF I NO PRI

BR I

TY

'CCPDD YES NO NO NORMAL

ccP l

vP tio No No NoRr.lAL

DUI|IHY I NO NO NO NORUAL

OUI.|HY 2 NO NO NO NORMAL

PROG FILES TERf',ls l',loRcoR

ruatiE -- Fturnnur AccESs sHR KsoRT TERIINAME

ATTRIo

CCP

t

VP CG I

VF I LE LOAD NO NO

NIIHMYI DUI.tilYI UPDATE YES NO

DUMUY2 AOD YES NO

OUMMY2 DUI,II{YI UPDATE YES NC

OUMI{Yz ADD YES NO

+T****t}t*THE FOLLOhIING

STATEI{ENTS

CAN BE I,IODTFIED

FOR YI]UR

******t**coNFIGURAT ION 8UT SOME

l,lUST

BE KEPT rO RUN

CCPM. SEE THE

rt*+*+**tC0l'ltlENf S IN THI

S DECK.

ri

I

/ SET II.}-A' ACTION-CREAT5,I]FLTEXFC-YES

// sysTEM

r,rINUpA-l

gK.HL

rrPSUF-3090.

/ | _ PAssr{oR

rFFEcD,

'lEl IE

|

| E couxaHoL-50r

DFFeACK-eRocRAH-eGMREaL-r5

il

4

// rERilATTR

ATTRID-

L TRANSLAT-N0,ELKL-5l2

rDATAFORI.t-f{ESSAGE'

*vERTFY

ro-NO,DFF32?O-YES

III tr

rft***+r*THls STHNT

TYPE REQD FOR

CCPIVP OR

HLTALINE

STIINT

*

| / BSCAt INE TYPE-CS'

L INENUI{-trPOLLLl ST-trOO'Ol

rlOrlls

| | AS CAT ERH

TERI.{

lD-00' fYPE-3277n2'Af TRlD-l rCOtlttAND-YESTOFFACTN-HOLDT

A

D

DRCHAR-

*606 04040* ,

pOLLC

HAR-f 404

04

04 0*

ll SScATERH IERHID-01,TYPE-327?ft2rArrRlD-lrCOf,ifitAi{D-YESTOFFACTIFHOLOT

ADDRCHAR-r6050C lC l*, P0LLCHAR-*

4040C

tC

lr

04t07 t80

PRUF 3Z

SAMPLE

ASSIGNMENT SET: CALCULATIOru dT UAIru

STORAGE SIZES

I/ LOG

PRTNTER

***r*'nrsAt{PLE ASS IGNl.l€NT

AN0 SAI.IPLE

START-UP

DECK*tt*t'tf*f**ttt*lrrfrr* 000 10000

* 00020000

*rr**.r**SAMPLE ASS

IGNI{ENf

SET *!r**r**a*t*'}*****tttt++**tt*r*+**r*att*+ 00030000

+ 00040000

*r+rfFILL IN UNIT 00050000

* 00t)60000

/ / LOAD

icCPAS,

R2 0ol)7000o

* 00080000

*+ttrF ILL IN PACK

ANo

uNtf 00r)90000

0 0

I

00000

*

/ / FtLE NAHE-SCCPFIL

E,

R€TA

IN-P, uN I

T-R 2,PACK-CCPO8

J 001 loo00

* 00120000

f*r*rFIt_.L tN pACK

ANg

UNIT 0013000Q

* 00140000

| / FtLE Nil,tE-$cCpr,toRKrRETAIN-S,

TRACKS-3,

UNtI-R2'PACK-CCPOBJ 00150000

// RUN ool6oooo

r 00 170000

I sccnrrLE AssrGNt'IENT BUrLD

LISTING PAGE

()O1 00/00

/00

00180000

00 190000

00 200000

oo2 10000

0 0 220

000

00 230000

o0 240000

00250000

00

260000

00270000

00 280000

oo 290 00 0

00300000

oo3

10000

00 320000

00330000

0 0 340000

00350000

00360000

oo

37000

0

l\ssignment Stages

// BSCAT

ERM

T

ERI{ID_IOrTYPE-3217\2,ATTRIIFI,COI{HAND-NOr

143

// ADDRCHAR-*61614040*,polLCHAR_*ClCl4o4or

/ / BscAT

ERt{

T

ERt't

I}- ll, Typ

e- lztlil,arrRIo-l,c0rrFAND-No,

|

/ ADDRcHAR_*616Ic

rc

r*,pot_ldHAR_f

clc lclctr

*

// T

ERI.TNAIIE

NAI,IE-CUOOVO,

TERMI

I]-OO

// TERf{NAr{F

NAME_cuoDVl,

TERH

ro_oi

// TERHNAI,tE

NAtlE-CUIDVO,

f

enr.rtO-iO

// T

ERT.INAI.'E

NAM

FCU

IDV

Ir TER14

ID-

I i

'}

0

0 380000

00

39000

0

00400000

004

1o000

o0

4

20000

00

4 30

000

00440000

00450000

00460000

0047000

0

00480000

00490000

00500000

00

5

10000

00

5

20000

o0

5

30000

o0 540000

00550000

00560000

00570000

00

580000

00590000

oo600000

006

10000

00620000

00630000

00640000

oo650000

00660000

00670000

00680000

006eo000

00 700000

00

7

t0

000

0 0

720000

00

7 30

000

0 0

740

000

oo/oo/oo

00750000

00

760

000

00

77000

0

00780000

00

790000

00800

000

o0810000

00

I 20000

008

30000

008

40000

00

8 5000

0

00850000

008

70000

00880000

*f**fr*+*THIS STHNT

TYPE

I

I DISKFILE NAI,IE-CGTVFIL

*

f :ll******T H

lS STHNT Typ E

:l

/ / DISKFILF NAME_CGIVF

+

*r*** ++ *t**++T H

J

S

la**t *rtf***rcAN

RFQD

FOR

CCPIVP

l'0RG-C,RECL-

l6

REQD

FOR

CCPIVP

IL2IORG-C,RECL.I6

A'I+******NOTF THAT

O^IE

DISKFILE STATEMENT

-CGIVFILE. I{OULD

BE NEEDED

+'+****r*IF SY}I8OL

IC FILES ARE

NOT

BEING

USED.

rl

* THE FOLLOI'

ING TI{O

DISK FILE STATEMENTS

ARE FOR EXAT.IPLE

T]NLY

AND

* SHOULD

8E REIIOVED

PRIOR TO

RUNNIN6

THI

S ASSIGNI,IENT

SET.

*

/ / DIsKF

ItE NAHE_DUt!ilyIroRG_o,RECL_256

/./ DISKFILE NAI,IE-OUIIHY2,ORG_I,NiCr-64,KEYL-8,KEYPOS-I

,I{SrR.I

NDX-YES

1

*t******''rHls srf{NT TypF RFeD

FoR

ccprvp IF syf{BoLIc FItEs ARE

usED.

/ / SYAFTLE

NAt{E-CGM

ILETDISKFILE-oCGI

VFtLI TCGI

VFI

LZrl

*

STIINT

NECESSARY

FOR,

CCPTVP,PACK

AND

PRINTER

VALUES

BE CHANGED

FOR

YOUR

CONFIG.

:l

rl

PROGRAM

NAilE-CCP

IVP,PGHOATA-YE

S.

F

IL

ES-ECG

IV

F

tLE

/CO

/N0

sHR

Il,

PACK.PROGRAH,

PR

IN

TFR-NO

$CCPFI

LE ASSIGNIIENT

BUILD

I-ISTING

I{ARNING

HESSAGES

T

ERI.IINAT

TON

HESSA6ES

PAGE

OO2

+I****'I*NOTE rHAT CCPIVP I,!UST

BE ON

CORRECT

PACK

AT STARTUP

OF CCP.

* THE FOLLOI{IT{G

TTO PROGRAH

STATEI,TENTS

ARE FOR EXAI{PLE

ONLY

ANO

t sHouLD 8E REt'lovED

pR

IoR To RUNNING

rHt

s AsSIGNHENT

sET.

,l

/ / PROGR

AI.I

NAI.I

E-DUt{I,tY

I, MR

TH

AX-2, PGMDA

rA- YE

S,

_o t.t.

lll5l_rDuuuyl/DUlsHR,Duuuy2/rRUA/sHR,'rpAix_svsren,DFFf,rrERr,r_4,

o ,*, DFFNoF-z,

DFFsFrrr_l

l5o[ -.- ,d'

// PRUGRAtt

NAilE_DuHHy

2,MR

Tr.tAx_2,pcilDArA_yE

Sr

- II FILES-ET",I.'MYI/oulsHR,DJTI.IY2lIRA/sHRnIPACK-sYsrEilIoFFI(TERI,I-2,

U ,*, DFFNoF-I,

orrsror-rso !! - ' A

*

/*

'Not applicable

for program

Number

S704-SC2.

Il Program

request

length

is

equal

to length

of program

name

+ 1

blank

+

program

data for

non-pRUF

pro-

gram

requests.

For

example:

CCPIVP

Program

name

=

Blank

Data

Total

COMMANDL

assures

that

50 character

command

length

is

permitted.

DUMMYl

communicates

with two

requesting

terminals

and

when loaded,

issues

acquires

to two

additional

terminals.

While

DUMMYl

may

communicate

with

only

one

of the

two

requesting

terminals

at a time,

it

can run

with any

or

all

of the four

terminals

at

the

same

time. (Reference

f,l )

DUMMY2

communicates

with

up to two

requesting

terminals

at any

one

time. (Refer.n"u

f,l )

1 1 50 is

the

largest

field

descriptor

table

used

by this

program

(DUMMYl

uses format

$ZOREN

and

$2000g).

iFieference

f,l i

396

is

the

size

of the

field

descriptor

table for

the

onry

format

used

by this

program

(DUMMy2

uses

only for-

mat

$ZO0O9).

(Reference

f,l )

E ourvnrvl

uses

two

data forrnats.

(Reference

f,t )

El ouruvy2 uses

one

data format.

lReference Et )

us. Gl E E in

*,e formuta:

DFF

program

appended

storage

(PAS)

size

equals:

(DFF

PAS

base

size

is

124

bytes.)

o

1

8

15

E

tr

,-l*

l(124

+

(DFFMTERM

x

37)

+

(DFFNDF

x 18))l

+

DFFSFDT

For

example,

the DFF

PAS

size for DUMMyI:

-"-

=U124+

(4

x

37)

+

(2

x 18)l

+

[1150]

= 124

+ 148

+ 36 (rounded

to next

highest 2561

+ 12gO

=

308

(rounded

to next

highest

256)

+ 1280

= 512

+ 128O=

1792

Refer

to the following printout

of a

$CCPDF

run.

Rounded

to

256.

Assignment

Stages 145

3ZOREN

DISPLAY FORI{AT

TNFORI{ATION

EXECUTION

TIHE DATA - OUTPUT

AREA

FORI{AT

- EI{O POSITIONS FOR RPG

PROGRAI{S

*

FIELD

IrlAllE

OPCODE

$ZOREN 004

006

FIELO END * FIELO

LENGTH POSI

TION * T{A}IE

rl ______

0004 * LENGTH

0020 *

F

I ELO ENO

LENGTH POSITION

0008

*

{r

FIELO

llT__

Tl{NAl,lE

F

IELD

L ENGTH ENO I

POSITI

ON

T

-------- I

00lt 'l

INPUT AREA

FORI{AT

- ENO POSITIONS FOR RPG PROGRAI{S

F

IELD END *

LENGTH POSITION

*FIELO ENO T FTELO

LENGTH POSITION * IiIAHE

006

FIELD ENO *

LENGTH POSITION

*

't

*

+

:f

t

IB

+

*

FIELD

NAI'IE FIELD

NAI,IE

LENGTH

CUSNO

SADDR2

I TE

I,IN

1

QTY3

I TEI{N4

QTY6

I

TEHNT

RTCOOE

- AID-

SA DDR

I

QTY I

I

T

EI{N2

QTY4

I

TE',IN5

QTYT

-------- I

0004 *

0015 +

0065 *

Ol

13 *

0133 *

0149 *

0169 ,3

0r 85 't

004

001

o22

004

008

004

008

004

oo4

006

o22

008

004

008

004

008

* ------ -------- I

0008 * THNAXE 006 OOl4 ,r

o02l r sNAtlE O22 oo43 *

0087 * SAOoR3 O22 OlOg ,r

OI2l * QTY2 004 0lZ5 'r

0137 r' ITEl,lN3 008 Ol45 t

01.57 r QTY5 004 0t6l :r

0173 * lTEr{N6 008 otSl I

0193 *

LENGTH

OF OUTPUT

RECORD

AREA

REQUIREO

IN OFF PROGRAII

RPG

rsuBR92* - oo2o 0THER

_ OOl2

LEilGTH

OF INPUT RECORD

AREA

REQUIRED

IN OFF PROGRAT,I

RPG

ISUBR92* - 0193 OTHER

- OI85

INFORI{ATTON

FOR

USE DURING

CCP

ASSIGNITENT

STAGE

,tHE

THE

rHE

THE

DECIXAL

LENGTH

OF

DECIHAL

LENGTH

OF

OECII.IAL

LENGTH

OF

FIELD

DESCRIPTOR

TABLE

IS 1I5O

OUTPUT

TEXT IS 1146

INPUT TEXT IS O24O

ur" El O El ,o

catcutate

the

size

of the DFF

program

appended

storage. For example,

the DFF

PAS

size for DUMMY2:

124

+ (2

x 37)

+ 18

(rounded

to next

highest

+ 396

(rounded

to next

highest

256)

216

(rounded

to next highest

256l

+ 512

256+512=768

2561

Refer

to

the

following printout

of

a

$CCPDF

run:

iZOO09 DISPLAY

FORIIAT

TNFORIIATTON

:::yl1_:11:. ooto - ourpur

AREA

FoRr{Ar

_ END

posrrroNs

FoR

Rpc

pRocRAHs

,}

*

'l

*

FIELO

NAI,IE

oPco0E

tz 0009

F

I

ELD END :*

LENGTH POSITION

*

-------- *

0004 *

0020 *

004

006

FIELD

N AIIE

LE

NGTH

F

I

ELD ENo 'I

LENGTH POSI

TION *

00

08

FIELD END

::yt: :::II9t

006 0014

F

IELO END

LENGTH POSITI

ON

*

t

FIELD

NAT{E

TI,INAI,IE

'l

I

004

INPUT AREA

FORI{AT

- END POSITIONS FOR RPG PROGRAI,IS

*

t

*

+

,}

FIELO

NAI{E FIELD

vT-_

LENGTH

NAilEA

sEcoNa

FIFTHI

Tt{o

FIVE

FIELD

NAl.lE

TI{NAI,IE

NAHE#

TH

I

RD#

S

I XIHA

THREE

sIx

F

I

ELD END

LENGTH POSITION *

't

t

't

:}

,l'

,}

*

:}

*

,*

*

:}

*

'i

*

F

I

ELD END

LENGTH POSITION,|

'3

:tr

'l

:f

rat

:3

I

,*

RTCODE

- AIO-

F

I

RST*

FORTHA

ONE

FOUR

--;;;;--

o0l5

0093

o207

o327

0459

--;;;;--

0035

0l3l

o245

0371

0503

o0

14

0 055

0

169

o283

04 l5

0547

004

001

038

o44

044

004

020

038

o44

006

020

038

o44

LENGTH

OF OUTPUT

RECORD

AREA

RPG

rSu8R92+ - 0020

LENGTH

OF INPUT

RECORD

AREA

RPG

*SUBR92*

- 0547

REQUIREO

IN DFF PROGRAI,I

OTHER

- OO12

REQUIRED

.IN OFF PROGRAI'I

OTHER

- 0539

INFORIIATION

FOR

USE OURING

CCP ASSIGNI,IENT

STAGE

THE

DECIHAL

LENGTH

DECIIIAL

LENGTH

OEC

II.IAL

LENGTH

OF THE

FIELO DESCRIPTOR

TABLG

TS 0396

OUTPUT

TEXT IS 0463

INPUT

TEXT

IS 0579

Assignment Stages 147

l0 Assume

only

two tasks

(user

programs)

can

run

con-

currently

and

the largest

programs

(DUMMyl and

DUMMY2)

are

multiple

request

programs

(cannot

have

multiple

copies

in main

storage

concurrently),

the

worst

case for two concurrent

user

programs

is

calculated

for the followinq:

1. CCPIVP

main

storage

size

is 4096

bytes

(no

DFF).

DUMMYl

main

storage

size

is

8448

(8193

rounded

up to the

of 2561

(compiler

output, including

linkage

edit)

+ 1792

(for DFF

program

control

information)

or 1O,24O.

DUMMY2

main

storage

size is

6144

(6140

rounded

up

to the

of

256)

(com_

piler

output,

including

link-edit)

+

768

(for

DFF

program

control

information)

or 8,l92

(6912

rounded

up

to the

of

20/8t.

4. Using

the worst

case

of DUMMyI and

DUMMY2

in

core

concurrently,

the value

of

the MINUPA

parameter

would

be 10,240

+

8192

= 18,432

(18K).

Note: lt the

operating

environment

is such

that

DUMMY1

and

DUMMY2

would

never run

concur-

rently,

the

value

of parameter

MINUpA

could

be

reduced

(DUMMYI

and CCPIVp

run

concurrently,

DUMMY2

and

CCPIVP

run

concurrently).

The

size

of the

TP line

buffer for

a

BSCA

line

is

determined

from

the largest

of the

BLKL paramerers

on

the

TERMATTR

statement.

For

this line,

the

line

buffer

length

could

be

the

maximum

of 1290

(1146

length

of

output from

$ZOREN

rounded

up

to

the

of 256) for maximum

performance,

or

a minimum

of 512

to

siave main

storage.

The

size of

the TP

line

buffer for

an

MLTA

line

is

specified

in

the MAXRECL

parameter

specified

on

the

MLTALINE

statement.

y'y'ote.'

When

a

line

buffer

size

less

than

the

output

text

length

is

encounterecl

by DFF,

DFF

sends

the

text in

segments equal

to or less

than

the

line

buffer

size.

For

output

text lengths greater

than

256,

512

is

the

smallest

line

buffer

size

supported

by DFF.

The

largest

value

of the BLKL

parameter

(in

the

TERMATTR

statement)

or the MAXRECL

paramerer

(in

the MLTALINE

statement)

per

system

is

used by

$CCPAS.

$CCPAS

calculates

the main

storage

require-

ments

for

reserving

a minimum

PUT

buffer

in

the

MINTPBUF

area. The reserved

PUT

area is used

only

for

PUT

data

operations.

lf only

DFF

terminals

are

defined

in

the

system.

the minimum

reserved

pUT

data

area is

512 bytes.

For

a layout

of the

MINTPBUF,

see

step

@ .

The

MINTPBUF

parameter

specifies

the minimum

size of

the

dynamic

TP

buffer

area. This

size,

rounded

up

to the next

2K

boundary,

is

the Tp

buffer

area.

To

determine

a

value

for

MINTpBUF

to

get

maximum

performance

without

wasting

main

storage,

the following

considerations

apply:

TP Buffor Layout

e

@

Reserved

PUT

data

area

(See

@ )

TP PUT

or GET

(invite)

area

TP Invite

parameter

list

area

At CCP

Startup,

the TP

buffer

area is

automatically

allo-

cated into

three

areas

according

to the

following

algorithm:

Size

of (!)is either

A or B:

A is

516

(512

data

block

+

4

getmain

segment

list)

if

all terminal

attributes

are

DFF.

B

is the

greater

of MAXRECL

+

4 (MLTALINE

state-

ment

for

MLTA

terminals)

or BLKL

+

23

(TERMATTR

statement

for

BSCA

terminals)

if

all

terminal

attributes

in

the

assignment

set

are non-DFF.

lf DFF

and non-

DFF

terminal

attributes

are

mixed,

the size

ot (l) is

the

greater

of A or B. \-/

/-\

Size of (!r) is

(N

x 23)

+

4,

where

N equals

the number

of input

capable

terminals.

Size

of @ i, r..r.inder

of area.

CCP

requires

this

area

to be

large

enough

to

handle

the

largest

system

invite,

PRUF

lNVlTE,

or

program

requesr

from

the

system

operator

console.

The

area required

for

program

requests

from

the

system

operator,s

console

is

calculated

as follows:

= (104

+

pCT).

(The

pCT

is the

program

control

table.

)

2.

3.

tr

148

The largest

system

invite

to a terminal

is

calculated

as

the

maximum

of

one

of

the following:

1. PGMREOL +

PCT

+

4

2. Maximum

PRUFLNG +

pCT+

7

+4 (for

DFF)

3. Maximum

PRUFLNG

+

PCT

+

l5 +

4

(for

non-DFF)

4. COMMANDL +

4

Note: Add

eight

additional

characters

for a327}command

terminal

for items

1

and

4.

The

maximum

PCT

=

35t +

4 x (number

of

disk files

used

by

the

programl

+

2

x (number

of required

terminals).

The length

of a system

invite

issued

to a

terminal

in command

mode

for our

example

assignment

set is

calculated

as

follows:

Maximum

PCT

=

35' +

14

x 2l + (2

x

Ol

=

42

PGMREOL+PCT=

42+15=57

COMMANDL

=

50

Length

of largest

system

invite

= 57

+

4 = 61

lf 3270

command

terminal

61

+

8

=

69

For

the example

assignment

set

with

no

programs

running,

the

MINTPBUF

parameter

must

be large

enough

to handle

four

t9{ilr9!1 in

comrnand

mode.

Therefore,

the

sum

of

areas

(!), (0, and

(3) a'e:

Notes:

i. The

do not

consider

the

situation

where

the

system

operator

enters

program

requests

from

the

system

operator's

console.

lf the

system

operator is

allowed

to enter

program

requests,

the size

of area

@

must

be

increased

by

104

+

pCT

size:

2e44

+ 1o4

+ 42=

30e0 lEl

2. lf two or more

lines

are being used,

the consideration for

the worst

case in

the same environment makes

possible

additional

terrrinals

on the second

and succeeding

lines.

In this

case,

a ,drger

MINTPBUF parameter

value would

be required

for maximum

performance.

3. In

the

if the value

of the MINTpBUF

parameter

is

less

than 3090, the system

could run with-

out performance

degradation

if the largest

input format

(579)

is not used

at

all

four terminals

concurrenuy.

4. lf main

storage

is

critical,

varying

the

sizgqf

the

Tp

buffer at startup

adjusts

the size

of area

(f)to an

acceptable

size for speed

and

storage. A momentary

lockout

might

occur

until

an input

or output operation

is

completed allowing

a portion of the teleprocessing

buffer

to become

available.

5. The end main storage

address

of the Tp bufter area rs

always

rounded

up to a 2K value;

therefore

the size

of

the TP buffer area

allocated

at startup is

always

equar

to or larger

than

the MINTPBUF parameter

value.

6. lf MINTPBUF

is

not

avaitable

to handle

a DFF

pUT

operation,

automatic blocking is attempted. Under

automatic

blocking.

the next

smallest

multiple

of 256

(minimum

of 512l.

is

used

if available from Tp buffer.

In

this case,

a corresponding

TP line

buffer

is used

for

this

PUT

operation.

Therefore,

even

if a Tp line

buffer

o't 2O48

is

defined.

if TP buffer at this time has

only

768

available,

this

DFF PUT

operation

is

performed

using

a block length

of 768.

USER

SECURITY DATA PROGRAM ($CCPAU}

The intention of the user

security

data program ($CCPAU)

is

to take input from the system input device,

process

it,

and,

if correct,

write it out to the object module $CC4Z9

as

the user's

security

data. This

program

($CCpAU)

is

provided

only if SECURE-USER

was

specified

at

gener_

ation in the $ESEC

statement. The object module $CC4Z9

is

copied

to the

CCP

production

pack

only if SECURE-

USER

was

specified

at

generation

in

the

$ESEC sratement.

lf $CCPAU is loaded

and the module $CC4Z9 is not on tne

production

pack,

the

system issues

a

VF 4Sy halt.

516

o

516

+

(tx 69I+

((4

x 23],+

4l

@@

+ 276

+ 96 = 888 bytes

However,

with

this

value for

MINTPBUF,

DUMMyI and

DUMMY2

cannot

run

because

they use

$ZOREN and

$20009

which

require

24O

and

579

bytes

respectively

for invite

buffers,

plus

4 bytes for

the

GETMAIN

param_

eter

list. Therefore,

the

minimum

value

of Tp buffer size

selected

should

equal

516

+ (579

+4) +

96

= 1195

bytes.

To

get

maximum

performance

when

DUMMyI is

communi

cating

to

all four

terminals

and

the

console

is

being

used for

CCP

commands

only (no

program

requests),

the value

of

MINTPBUF

equals:

516

+

(4

x (579

+

4))

=

516

+ 2332+

96

= 2944

bytes

'For Program

Number

5704-SC1

the value is

35;

for Program

Number

5704-SC2

the

value

is

41.

@

231

+((4x +4)

Assignment

Stages 149

Input

is in

the form

of security

data

records

that

can

be

one

of seven

types.

The type

of record

is

specified

by

the

f irst

position

of the

input. The

type

indicator

can

De

any

of

the following:

C, Z,

X, l,

J,

K,

and

L. In

addition,

a

command

input

record

is

allowed

and

is

designated

by

an

asterisk

(*)

in

position

1. Comment

records

are

logged

to

the

system

log

device.

Each

type

of input

record

is

intended

to define

a unique

type

of data.

The following

apply

to

all input

data

types:

o Positions

2 and

3 define

the

number

of data

bytes

(in-

cluding

the

sign)

to'be

used

from

the

input

record

and

the data

must

begin

in position

5.

o Position

4 is expected

to be blank.

Some record

types

can

define

signed

(+

or

-) values.

In

this

case

the

sign,

if present,

is entered

in position

5 and the

data

begins

in position

6. The

position

occupied

by

the sign

in the

input

record

is

counted in

the

number

of input

data

characters

that is

specified

in positions

2 and

3.

Each

input

record defines

data

to be

placed

in

successive

locations

in the

object module

$CgZg.

The

following

input

data types

are

accepted

by

$CCPAU.

The data

type is signif ied

by the character

specified in pos-

tion 1

:

C Character

String

The data

can include

any

character from

the ex-

tended

character

set including

blanks. The out-

put

is

the characters

specified,

in

EBCDIC.

The

output length

is the number

of bytes

specified

in

positions

2 and

3.

Z Zoned Decimal

The data can include

any decimal

digits

and

can

be

preceeded

by

+

or -. The

output

is

a

signed

zoned-decimal

number.

The

output length

is

the

number

of digits entered

(that

is,

the number

of

bytes

specified in

positions

2 and

3,less

one

if a

sign was

specif ied).

Hexadecimal

Data

The

count in positions

2 and

3 must

be even. Every

character

of input

data must

be in

the range

0-g,

A-F. The output is a set of bit configurations

cbr-

responding

to the hexadecimal

input. The output

length

is half

the number

of bytes as were

specif ied

in

positions

2 and

3.

I One-Byte

Binary Integer

The input

data is limited

to

three

positions

plus

an

optional

sign.

The

numeric

value

must

nor exceed

255.

The

resultant

data

will

occupy

one

byte in

$CC4Z9,

and

be

represented

as

a binary

integer.

J Two-Byte

Binary

Integer

The input data is limited

to f ive

positions

plus

an

optional

sign. The

numeric

value

must

not

exceed

65535. The resultant

output will

occupy

two

bytes in

$CC4Z9,

and

be

represented

as a

binary

integer.

K Three-Byte

Binary

Integer

The input

data is limited

to eight

positions

plus

an optional

sign. The numeric

value

must not

exceed

16777215.

The resultant

output

will

occupy three

bytes

in

$cc4Z9.

and

be repre-

sented as

a binary

integer.

L Four-Byte

Binary Integer

The input

data is limited

to ten

positions

plus

an

optional

sign.

The

numeric

value must

not

ex-

ceed 4294967295.

The

resultant

output will oc-

cupy

four bytes in

$CCAZS,

and be represented

as a

binary integer.

$CCPAU

continues to accept input data from

the

system

input device until

a

/" is read,

or until enough

data

to

fill

$CO4Z9

is

accumulated. At this time the

data

to be written

to $CC4Z9

is

printed,

in hex,

on the

system log

device

so that

the data can

be

verified.

After printing

has finished,

a CPU-

A3 halt

occurs.

Option 0 as

a

reply

causes

the data

to be

written to $CC429.

Option

2

causes the

job

to be termin-

ated and

$CC4Z9

not

to be updated.

The

followins

OCL statements are needed:

For

a description

of writing

a

user

security

program,

see

IBM System/3 Communications

Control Program

Program-

mer's Reference

Manual

. GC21-7579.

Input Data

Records

Chapter

8. System History

Area Copy Program

(Program

Number

5704-SC2

Only)

The

System History

Area

Copy Program,

$HACCP,

is

used

to copy

the

current

portion

of the

System

History

Area

(SHA)

to

a

user-defined

disk f ile.

This

program

oniy

runs

under

control

of CCP.

$HACCP

is

designed

to be automatically

invoked

when

the SHA

is nearly full,

but it

can

also

be manually

invoked

by

the system

operator

at

any

time

(using

the

PFg

key).

$HACCP

cannot

be invoked

from

a terminal.

Note: The

$HIST

program

can

also be

used

to save

tne

contents

of the

SHA. However,

$HIST

requires

a batch

partition

and it cannot

be automatically

invoked.

USER REOUIREMENTS

On a main

data

area the

user must

define

a

file,

named

$SHAFILE,

with a record

length

of 128.

The format

of

the records

written

to $SHAF

ILE is the

same

as the

format

of the records

that

$H

IST

writes

to the

$H

ISTORy f

ile.

$SHAFILE

must

also

be defined

in the

CCP assignment

set as

having

consecutive

add

(CA)

data

management.

This

allows subsequent

executions

of the

program

to add new

records

to those

already existing

in the file. To access

the

information

in

$SHAFILE,

a user-written

pr.ogram

is

rerluired.

To use

$HACCP,

the

following

statements

must

be in

your

COP assignment set:

// DISKFI

LE NAME.$SHAFILE,ORG-C,RECL.128

// PROGRAM

NAME-$HACCP,PACK.PROG

RAM,

PGMDATA.NO,F

ILES.'$SHAF

I LE/CA'

lf

$HACCP

is

to be automatically invoked

when

the

history

area

is nearly

full,

then the

following

statement must

also

be in the

assignment

set:

// SYSTEM

MAXCHAIN-nn

$HACCP

requires

8K of the CCP

user

program

area.

OPERATlNG

CONSIDERATIONS

The

SHA

halt

status

can

be changed

by

using

the HALT

SHA

or NOHALT

SHA commands. lf $HACCP

is

to be

automatically invoked,

the

following

OCC must

be entered:

HALT

SHA,CCP

[,tracks]'

This

condition remains in effect

until IPL is

performed

or

until

a

HALT

SHA or NOHALT

SHA command is entered.

To

permanently

establish

automatic invocation,

the Con-

figuration

Record Program

($CNFIG)

can be used

to set

the automatic function with the following

statement:

// SHA

HALT-CCPAUTO

[,TRACKS-xx]

I

For further

information

on

how

to

establish

automatic

execution,

see

$CNFIG

in l8M System/3 Model

l5 System

Control Programming

Concep$ and Beference

Manual

,

GC21-5162.

After each execution

of $HACCP,

an

informational

message

will be issued

giving

the

number

of records

added to

$SHAF

ILE

and the number of records left in

$SHAF ILE

before it fills. lf $SHAFILE

should

fill while

the

program

is copying

to it,

a decision message will

be issued

and the

file

must be emptied

before

$HACCP

can

be

successfully

run

again.

lf CCP

terminates abnormally,

the

$SHAF

ILE

will

not

be

closed;

therefore, records could

be

lost. See

File Recovery

Procedures

in IBM System/3 CCP System Design

Guide,

GC21-5165

for

recovery

procedures.

'The tracks

parameter

can

be

any integer

value up to 1 0, but not

greatei

than half

the size of the SGA. This

parameter

is used to

set the

wraparound warning

point of the SHA, and it is not

required unless a warning

point of O is currently in effect.

System History

Area

Copy Program

(Program

Number 5704-SC2

Only) 151

't52

The

following

is

a

summary

chart

containing

all

valid

CCp

generation

control

statements.

The

statements

are listed

in

alphabetic

order.

Three

items

are

given

for each

statement:

o Name

o Format

of

the

statement

with

all valid

operands

o Synopsis

of the functional

description

For

more

detailed

information

on any

of the

CCp

genera-

tion control

statements,

see

index entryi generation

control

statements.

Appendix

A. Generation

Control

Statement

Summary

Chart

Generation

Control

Statement Summary

Chart 153

Generation

Control

Statement

Description

$EBSC

$EBSD

$ECSC2

$ECSD,

rBscA.)if

,

,,"*

{['] r

r,D,AL

{G'},

r.".

{15'},',"

{C'}r

r,",.{

G'},

r,GErMsc.

{U'}r t.,rB.

{G. }, r,REcsEp.

{X},

'.o'",,-{15'},

,,.r.o,..

{W },

rR

ESP.L-

{G' } r

r,AUroRs-

{ G'} ,

',*,*'u.".{lE

}

,

, ,,*',o..

{G'

},

,,,o"'

{[['],'

75M1

3271M1

3244M1

3286M1

3275M2

TYPE- ( 3271M2

3284M2

3286M2

3735

3741

aot I

I

ndicates

general

specificatrons

concerning

binary

synch ronous

communications

(BSCA)

support.

Indicates

a

BSC

device type

that

the CCP supports

(for

BSCA).

I nd

icates

general

specif ications

concerning

BSCC support.

Indicates

a

BSC device

type

that

CCP

supports.

(For

BSCC.)

',"..

ljl rrcErMsG

{U}

,,,,',

fiE}

l

r.REcsEp.

l*t 'r,Ascr.

{tr} r

r,EB.D,c.{C}

I

r,xPRNcY.

{U} rr,,NrpoL.

{U'} 1

'.*

{P},'',"{ffi'},,,,o",

{[!'],'

3275M

1

3277M1

3284M1

3286M

1

3275M2

3277M2

3284M2

3286M2

3735

3741

CPU

rUsed

with 57O4-SC1

onty.

-Used

with 57O4-SC2

only.

154

Generation

Control

Statement

Description

{rvo I

[,ESCAPE- {'cccccc' i' I

{ x'*""""rr**r' }

r,PGMcNr.

{::t }, r,BSypRr.

tNO

J'

r.FoRMAr.

{ Gt }r r,MovrNr.

fves L

r,r.HUF-

1NO lt [,MOVDFF-

\- /

r..PPRUF.

{[t]

' ,,"rr".o-

r.AccEPr- I "tt\ '

t

No

, I,stoc_

r,RES.PN.{U'}

),

T,.PUMSG-

{Hr} ,' r,ro*"or-

,,,,o,*

{lE },'

{['],

{fi'},'

lves \,,

tp t'

{['],'

(H,)

2

i

:i;,i'

'Default for Program

Number

5704-SC2.

-Program

Number

57O4-SC2

only.

"Default is

0. The non-zero

minimum varue for n is

6. The maximum varue

is 100o.

Indicates

options

that

determine

the CCP facilities

included

durino

generation.

Indicates user options

on sizes

of items that affect the allocated

size and location

of $CCPFILE.

$EFAC

$EFIL ''.''.{*},' ',r*oo, {p }r t,DF,LES.

r,rERMS.

{*}, ,,"r"' {*}, r,coRE.

(:;)

,FLUNrr.

1

?;1,'.'^cK.pack

fsL

i;i,

48K

64K

96r

I

128K

1

60K

192K

224K

256

K

38ar2

sl2r2

[,TRKLoC-n] t,DpTRAC-

Generation

Control Statement Summary

Chart 15b

lr

(

rr )

{

;t i [,DPUNrr-unit]

I

/ tr1

\ ;; I

( ;; ), [,DPPACK.pack

t;;

)

{ unit \

( 'unit,unit,unit'J

DSUN IT.

CCUN IT-

WKUNIT-

:i )

F2(

Ht/

L11,ou"n,o""-'l'"''-'

{

rM,NREs.{C'}r

r,cARD.

{V:r } ,

**ro"*- {

Name Generation

Control

Statement Description Function

$EGEN Indicates where

various

unit

and

pack

names

are

located

during

the CCP

generation.

$EM

LA Indicates whether the multiple

line terminal adapter

(MLTA)

is used by the CCP and,

if

so,

the

number of

MLTA lines.

Also indicates whether or not

line translation is used on all

MLTA

operations.

$EM

LD Indicates an

M LTA terminal

type

supported

with its f eatures and

the transmission

code

required

on the

line.

'Program Number

5704-SC2

only

fves l .

1ii6- I'

LINES-n

[,X

LATE-

TYPE.

1 050

1

050D

2740

27405

2740C

27405C

27 400

2740DT

27 40DC

27

40DTC

2140M25

2740M2S8

2740M2SC

2740M2SCB

27 41

2t 41D

CMCSTD

SYSTC

SYSTSC

SYSTDC

\ coRR I

,xMcoDE. { PTTCEBCD

t

I PrrcBcD

I

156

$EPLG

$ESEC

( coBol )

LANG.I

:?:lTo*l,rrrr,r_

) AssEM (

1

RPGII )

r Rl

r

)"(

I

:;J

(No I

[SECURE.

{CCP }

I

usen

\rr,LUSr-{*

},

Indicates

a

programming

language

the

user wishes

to use for program

preparation

under

the

CCP.

Indicates

the type

of

terminal

sign-on

security

to be

useo

(if

any).

Generation

Control

Statement

Summary

Chart 157

158

The following

is a summary

chart containing

all valid

CCp

assignment

control

statements. The

statements

are

listed

in alphabetic

order.

Three

items

are

given

for each

Statement:

a Name

o Format

of the

statement

with all

valid

parameters

o Synopsis

of the functional

description

For

more detailed

information

on any

of the

CCP

assign-

ment

control

statements,

see

index

entry: assignment

control statements.

Appendix

B. l\ssignment

Control Statement

Summary

Chart

Assignment

Control Statement

Summary Chart 159

Asignment

Control

Statement

Description

BSCALI

N E

BSCATERM

DISKF

ILE

,CoMMAND_

{}:r}

r,AUroERP.

{Gt }

[,IDEXRCV-exchngid

]

//BscALrNE

'"r.

{frf

,,.,r.*,,

{i,}

r,xMcoDE.

{tg;"} 1

[.POLLLIST-,termid

[,termid1

. .

., ]

[,NRErRy. {* },',,"."sEND-exchnsid]

T.DBLBUF.

{y8r}r r,wA,r.

{+},

r,ourpoll.

{H} r2

rorrsur.{H}''

Def

ines

the type

of BSC

line

to be

used

and

the features

of

the

line,

Defines

certain

attributes

of the

terminals

on BSCA

lines.

Describes

the disk file

that

will

be used during

the execution

of

this set.

// BSCATERM TERMTD-termid,TypE-termtype,

ATTRTD-,attrid

[,attrid]

.. .'

r,oNLrNE-{#}

,

I

r,oFFAcrN-

{;*l} ,

[,AD

DR

CHAR-addressi

ng characters]

[,POLLCHAR-polling characters]

NN

[,lcF-

t' ]

//DISKFILE NAME-filename

lc/

,oRG-

f

Dl .REcL.n[,KEYL-n]

r,KEypos.nt

r.MsrRrNDX-

{Ct } t,

[,MtxStZE-n]

t [,exTEttTS-n]

t

'Not applicable

for Program

Number

5704-SC2.

'Program

Number

5704-SC2

only, TYPE-CS

is required

'Program Number 5704-SC2

only.

160

Assignment

Control

Statement

Description

LIST

MLTALINE

MLTATERM

(id

)ar-r-

)

DrR

' coN

IR

ESETPS.

t

(

rtu./

Jnro t

lWsl

;ruo L

iF*/'

l/ LIST [SET- I IPGMSTAT. This

is

a control statement

for

$CCPAL

that defines

which

options

the user wishes

to exer-

cise in listing

the

contents

of

the file.

$ccPFtLE.

Def ines the

type of communi-

cation line

to be used

and the

features

of the line.

Defines

certain

attributes of the

terminals

on MLTA lines.

// MLTALINE TYPE.

IPP t

)"'f

lswl

!

cw/

(;)

,LTNENUM-

( : )

t:\

(

PrrcEBcD

i

,xMcoDE- {

prrceco I

lconn \

,MAXR

ECL-n

[,PO

LLLTST-'termid

[,termid]

(134

i

[,DATARATE-

{600 i I [,AUroPoLL-

frzoo)

r,RcvrNr-{+:r}

r

r,NRErRY.

{*} ,

[,DELAY-n]

[,rtoLr- {S},

INO J'

,1

*o/,

E'i

'

// MLTATERM TERMTD-termid,TypE-termtype,

,ATTRID-'attrid

[,attrid]

. . .',COMMAND. J*o L

tYEs J

[,ADDR-xx]

r,oNLrNE-

{w} I [,prNCoMp-n]

[,PourcoMP"n]

[,oFFACrN

{;:*} ,

Assignment Control Statement Summary

Chart '161

Assignment

Control

Statement

Description

PORTLINE

(

I/

PORTLINE

*"

I

stoc \

TTASK I

iiffit

/

L|NE3

I

LINE4 \

s /'

TI

1\

2l

il

PRIMARY

SECONDAR

MoDE.{ i

Yl',

"...-{b}

MAXMSG-n

,AQPORT.N

,NAQPORT-n

[,PORTPRFXport

pref

ixl

t.xMcoDE-{m},'.*".'"".{*},

T,DBLBUF-{y.,

} , ,rr^,'.{p},

Defines

the

type of PORTLINE

to be

used

and the features

of the

oort.

Name I Asignment Control

Statement Description Function

PROGRAM // PROGRAM NAME-pgmname

[,MRTMAX-n]

T,NEVEREND-

{W-},

IsHR/

[,PRtNrER- {No } I

lfes)

(:,) (:,)

[,MFcu1-1n

] tt,mrcuz.

1n ll

tu tto)

(:,) (:,)

[,MFCM1-

<R >

] LMFCM2-(R

)1

&) tt)

(:' )

t.RP1442.

i; l r T,PGMDATA

{}:r},

(r)

r,N374,-

{l' } ,

(p)

','*o"o{}3r} ,

,,*ruo,-

{}3J

,

[,TERMS-'termname[/attrid] [,termname[/attrid] I . . .'l

[.FrLES-'ritename/access[/

{H"-} ] t/KsoRrl

/PROGRAM \

\:l?'* 1

r,PAcK-1;i, ) 1

(r; )

[,PRUF$Z-format

namel [,PRUFLNG-nnn]

[,DFFMTERM-n] [,DFFNDF-n] [,DFFSFDT-n]

[,MORCOR-n]

r,sonr-

{gves}

r

I r,execr

r ru t {g },'

r,r^,o*,rt.{i#E},

'

[,rASKStZE.n]1

l,pcn,|rrruo

{wr} ,'

Defines

the logical

structure and

resouice

requirements

of a

user

program.

r

For Program

Number

5704-SC2 only.

Assignment

Control Statement Summary Chart 163

Assignment

Control

Statement

Description

SET

SOU

RCE

SYMFILE

,,sEr ,

" {*},

r,AC'oN.

{ll,tf.}

(;;*;; )

[,DFL

rEXEc.{U'}

r r,ANyspEcs

{p} ,'

Specifies

which

set is

to

oe

processed

and

what

opera-

tion

is

to occur.

Specif

ies

that

control

statements

supplied

to $CCPAS

are reao

from

a

source library

member.

Def ines a

symbolic

file

name

and

specif ies

the disk

files

with which

it can be validly

associateo.

NAME-name,U^,

t {ii}

t:if

\f z /

,rn,^ fvesl ,

,,-,"".1*o

.r

,

//

SOURCE

l:--

| ^For

Program

Number

5704-SC2

onlv.

Name I Assignment

Control

Statement Description Function

SYSTEM

^

For Program

Number

5704-SC1

only.

zFor

Program

Number

57O4-SC2

only.

JFor

Program

Number

5704-SC2,

the

following

codes

may

atso be

soecif ir:d:

R1, Fl, R2, F2

D1A,

D1B,

D1C.

DlD

D2A, D2B, D2C, DzO

D3A, D3B, D3C,

D3D

D3E,

D3F, D3G,

D3H

D4A, D4B, D4C, D4D

D4E, D4F, D4G. D4H

IMTNUPA.

1T'nf r

MTNTpBUF-n,

lbK I

l,PAsswoRD-paswordl

[,pRtNrER-

{Y?r},

(i'1 (

i'l

[.MFcur.

(R ) I t,MFcuz.{

R )l

lb\ (t)

(:,) (:,)

t.MFcMr

(R ) 1[,MFCM2.1R

)l

lil trl

'|^'^ ) (E'/

,,*ruo'lffirf

r[,RP1442.

{" },

(

-'' (t)

. FIP .

l; I [No I

LN374r

<; ) I t,polrrMe.(.trt.ww,)

I

l^^l loooz I

,,ro"".o.

.13,1,

',.o""o"ot

{#},

T,DFFPA.K

{;;::."1'". } , '.rro. {$} ,'

[,MAXCHAtN-n

j

2

,,or.,ro"

{lE.} ,'

t,.rro,-t,

{Sr} ,'

r,ER'ME.

{i},'

r.pRUFoF.

{HJ i

D1

D2

D3

D31

D32

It

t,DUMPUNIT.

( ;;;

D4

D41

D42

D43

o44

Def ines

parts

of the environment

in

which

the CCP will

execute.

Assignment

Control Statement

Summary Chart

Name I Assignment

Control

Statement

Description Function

TERMATTR

TERMNAME

// TER

MATTR ATTR I D-attrid

The following parameters

may be

specified

for both the

MLTA anrl BSCA terminals

r,rRANsLAr-t#l

I r,uPCAsE-

{Ji} '

(H)

I,SWITCHED-(

MC / ]

(m)

The

following

parameters

may be

specif

ied for BSCA

terminals

only

[,BLKL-n]

[,REcL-nj

IRECORD '

[,DATAFoRM tBLocK | 1

t,rnnrusp-

l

nressnc

r

I

[,rTB-

[,SPAN-

t*ol,

?"rri

'

{}?,}

, r,vARL.

{+9,}

,

{+:,}

I

t,vER,FY,D

{+:.}

,

t,DFF327o-

{Ut} ,

Defines certain attributes of a

term inal.

Defines

symbolic names associated

with terminals and

subterminals.

// TERMNAME NAME-termname[,TERMt

D-termid]

[,MSTRNAME-termname]

[,tNCOMP-n]

[,OUTCOMP-n

j [,PHONENUM-numberl

Af f

CCP

messages

are contained

in the

tBM System/S

Comm

u

n ications

Control

Prqram Mesages

Manu

al,

GC21-5170.

Appendix C. Messages

Messages 167

168

TERMINALS

AND FEATURES

SUPPORTED

The following

terminals

can be used

with

the

CCP.

Through

the multiple

line

terminal

adapter:

o 1050 Data

Communication

System

Multipoint

switched

Multipoint

nonswitched

. 2740

Communication

Terminal

Model

1

Basic

Checking

Dial

with

checking

Dial

with

transmit

control

Dial

with

transmit

control

and checking

Station

control

Station

control with

checking

. 2740

Communication

Terminal Model

2

Station

control

Station

control

with

checking

Station

control

with buffer receive

Station

control with buffer

receive

and

checking

. 2741

Communication

Terminal

Basic

Switched

. 3767 Communication

Terminal

(suoported

asa274Ol

Checking

(2740

Model

1)

Dial with

checking

(2740

Modet

1)

Station

control with

checking

(2740

Models

1

and

2)

. 3767 Communication

Terminal

(supported

asa2741l

Basic

Switched

o System 7 (supported

asa274O

Model

1)

Checki ng

Dial

with checking

Station

control

with checking

Appendix D. Devices and Programs

Supported and

Required

. Communicating Magnetic

Card SELECTRIC@

Typewriter

(supported

as a

2741ll

Poi

nt-to-poi

nt switched

o 5100

Portabler

Computer

(supported

as a27411

Basic

Switched

With

the binary :;ynchronous

communications

adapter:

. 3270 lnformation

Display

System

Multipoint

(System/3

is control

station)

See chalt for

configuration.

o 3735

Progranrmable

Terminal

Switched

Multipoint

(System/3

is control

station)

. 3741 Data

Station Models 2 and

4

Poi

nt-to-point

switched

Poi

nt-tc)-poi

nt nonswitched

Multipoint

(System/3

is control

station)

o 5230

Data

Collection

System

(supported

as a 3741

Model

2

or 4)

Poi

nt-to.

poi

nt switched

Poi

nt-to-poi

nt nonswitched

Multipc,int

tributary

. System/3

point.to.point

switched

Poi

nt-to.poi

nt nonswitched

Multipoi

nt control

station

Multipoint

tributary

o System/7

Point-to-point

switched

Po

i nt-to-point

nonswitched

Multipoint

(System/3

is

the

control

station)

o System/360,

System/370

Poi

nt-to.

poi

nt switched

Point-to.

point

nonswitched

Multipoint

(System/3

is

the tributary)

Devi<les

and Programs

Supported and Required l69

With

binary

synchronous

communications

controller:

. 3270

Information

Display

System

Multipoint

(System/3

is

control

stationl

See chart

for

configuration.

o 3735

Programmable

Terminal

Multipoint

(System/3

is

control

stationl

3741

Data

Stations

Models

2 and 4

Multipoint

(System/3

is control

station)

System/3

(BSCA)

Multipoint

tributary

System/7

Multipoint

(System/3

is

control

station)

Terminals

that

are

equivalent

to those explicitly

supported

can

also

function

satisfactorily.

The

customer

is responsible

for establishing

equivalency.

IBM

assumes

no

responsibility

for the

impact

that

any changes

to the

IBM-supplied

products

or programs

might

have

on such

terminals.

170

3270

Information

Display

System

Multipoint

Device Model Character CMax Speed Attached

Via

Max. Cable

Distance2

Displavs/Pnnters

G]l-l suooo^ua

Display Print Buffer Prinr Transmit I

3274 Control Unir 51C

9600

bps

BSC

32 71

.

3244, 32a6,

3247

,32aA

83262,

3278, 3219

,

3241

.3249

1C 3262,3271,3278,

3244, 3246,

32a1

.

3288, 32a9

, 3219

3271 Control

Unil

72OO bps

3211

1

,3284 1

3 286,1

23217

.3284,

3286,

32BB

3275 Display Station 480 3284 3

21920

3276 Control Unit

DasplaV

Station

2'1920 73262

,3218

2, 32A1

3289.3219

3278 Display Sration 21920 321 4,

3216

5000

3279

Color Display

Station 2A

3277 Display Station 480

3211,

3274,

Display

Adapter

2000

2I

920

3284 Printer 480

40 cps 2000

21920

3286 Printer I480

66 cps 2000

2r920

3287 Printei 1

1 920

80 cps 3271,

3274,

3276,

D

isplay

Adapter

5000/

2000

2I

20 cps

1C 80 cps 3274

3276 5000

2C |

20 cps

3288 Line Printer 21920 120

lpm3 3271,

321 4,

Display

Adapter

2000

3289 L'ne Printer

t9 20

'120

lpm3 321

4,

3216 5000

2300 lpm3

3262 L ne Prinrer 3

4096

465 lpm3 321

4.

3276 5000

IJ 230 lpm3

'Nonswitched. 3275 can also

transmit

at 12OO

bps

switched

2

In feet

from

control

unit.

"With 64-ch€racter

set.

Devices

and Programs

Supported and Required 171

SYSTEM

DEVICE

AND

PROGRAM

REOUIREMENTS

Device

Requirements

The

following

is

the

minimum

device

conf

iguration

necessary

for

a communications-based

system

using

the

CCp:

. 5415 Processing

Unit (CpU)

with 4gK (program

Num-

ber

5704-SC1)

or 96K (program

Number

S7O4_SC2]

bytes

of main

storage.

o 5444

Disk

Storage

Drive

Model

2 (program

Number

5704

SC1)

or

3340

Direct

Access

Storage

Facility

(pro-

gram

Number

S704-SC2).

. 3277

Display

Station

Model

1.

. 1403 Printer.

o An

input

device.

o Muitiple

Line

Terminal

Adapter

or

one

ginary

Synchronous

Communications

Adapter

(either

with

minimum

data

set,

line,

and

terminal

conf

iguration).

Notes:

At least

6K (Program

Number

5704-SC1)

or

gK (program

Number

5704-SC2)

main

storage

must

remain

available

in

the

CCP

partition

to perform

the

operation

starrup.

A partition

size

of at

least

4gK

(pnogram

Number

5704-SC2)

is

required

to

start

up

CCp.

During

CCP

generation

and

assignment,

the main

storage

available

to the

program

partition

in which

the function

is

being

performed

must

be

at least

22K

(program

Num-

ber

5704-SC1)

or 48K

(5704-SC2l.

During

CCP

generation

and

assignment,

the

communications

adapter

is

not

required.

Additional

Devices

Supported

The

following

device

facilities

are

supported

by the

CCp:

o 64K1,96K,

128K,

160K,

192K,

224K,256K,384K2.

or 512K2

bytes

of marn

srorage.

. 5444 Disk

Storage

Drive

- additional

Model

2

or Model

3 (Program

Number

5704-SC1

only).

. 5445 Disk

Storage

- 1

to 4 modules

for

data

srorage

(Program

Number

5704-SC1

onlv).

I

Progru. Number

5704-SCl

only.

'Program

Number

5704-SC2

only.

172

. 3344

Direct

Access

Storage

(program

Number

5704_SC2

only).

. 3340

Direct

Access

Storage

Facility

_ 2

to 4 drives,

. 5424

Multi-Function

Card

Unit.

. 2560

Multi-Function

Card Machine.

. 1442

Card

Read

Punch.

. 2501

Card

Reader.

o Multiple

Line Terminal

Adapter

with

up

to eight

lines.

o Binary

Synchronous

Communications

Adapters

(BSCA,

one

or

two adapters).

. Local

Communications

Adapter

(LCA).

o Display

Adapter

(DA).

. Binary

Synchronous

Communications

Controller

(BSCC)

with

Program

Number

5704-SC2

onlv.

o Serial

l/O

Channel

(SIOC)

with

program

Numoer

5704-SC2

only

(PRPQ

Number

b799.WNK).

Note: DA

and

BSCA-2

are

mutually

exclusive;

LCA

and

BSCA-1

are

mutually

exclusive.

CCP

operates

in

any

program

partition.

However,

CCp

will

not

operate

concurrently

in

all

partitions.

Nor

will

CCp

operate

concurrently

with

a

program

in

another

program

partition

that

requires

dedicated

use

of the

processing

unit.

System

Programs

Required

Execution

of

CCP

requires

IBM

System/3

Model

i5 Disk

System

Management,

including

all

transient

modules

for

the

appropriate

IOCS.

Generation

of

CCP requires

IBM

System/3

Model

15

System

Control

Programming

(5704-SC1

or

S704-SC2),

inctudino:

o Programming

support

for

the

desired

communrcatton

adapters:

MLMP

for

the BSCA;

Multiple

Line

Terminal

Adapter

Feature

(PSHRpO

number

S7g9_WFK).

o Programming

support

for

the

interval

timer required

if

using

interval

polling

or the Wait

operation

code.

No

special

systems

programming

requirements

exist for

the

running

of system

assignments.

For

the

preparation

of

application

programs,

an applicable

compiler

or

assembler

is required.

This glossary

contains

only terms that

have

a special

mean-

ing

Other

communications

and data

processing

terms

used in

this

publication

are defined in

l8M Data

Processing

Glossary,

GC20-1699.

command

interrupt

mode: The

operating mode

of a

terminal following

data mode

escape

until the

program

execution

is resumed

by

a run

command

(the

terminal

reenters

data

mode)

or until

the terminal

is released

by

a release command

(terminal

enters

command

mode).

command mode: The

operating mode

of a terminal

following

a successful

sign-on. up

to and including

the

program

request. Following

program

termination,

a

terminal

returns

to command mode

until another

proqram

request

is made

or until

sign-off.

command terminal: A terminal

that

is capable

of command-

ing

CCP

services related

to requesting

a

program.

Terminals

are designated

command

or data terminals

at assignment

time.

communications management:

A major

function

of the

CCP that controls

terminal

input/output.

communications

service subroutine: A relocatable

sub-

routine

provided

by the

CCP that is link-edited

to user

programs

written

in

RPG ll,

COBOL,

or FORTRAN lV.

The

subroutine

is called by

the user

program

whenever

the

program

requires

a communications

service, enabling

programmers

to request

communications

services in these

languages. A separate subroutine is

provided

for COBOL,

FORTRAN

lV,

and

RPG

ll;

a

macro

is

provided

for

Basic Assembler.

data

entry

application: A communications-based

system

application in

which terminals

are

in

continuous

operation

(as

opposed to the typical

inquiry

application). Data

entry

applications include

document

preparation

(such

as

invoice

writing)

and entering data

directly into

data f iles from

a

terminal,

such as in

creating files.

Appendix E. Glossary

data mode: The

operating mode

of a

terminal when it is

under control

of a user

program,

until

the program

terminates,

the terminal is released

by the

program,

or r'?

data

mode

escape characters

are entered.

While

in data

mode,

a terminal

is

not in direct communication with the CCP.

data mode escape: A special

CCP

command, consisting of a

unique

string of six characters entered at a

terminal while

the terminal

is in

data

mode. The

data

mode escaoe

command

interrupts

the execution of the application

program

and places

the terminal in command interrupt mode.

data

terminal: A terminal that is not capable of command-

ing

CCP services.

A data

terminal is

always

either

in

stand-

by mode (not polled

for input by the CCP) or in data mode

(under

control of an application

program). Also referred

to as a

noncommand terminal.

disk

system

managementr The group of system

programs

that control the operation of the IBM System/3

Model

15.

Disk System

management

performs

scheduling,

input/

output control, storage

assignment,

data management,

and related services.

external

pointer list: An area

in the user

program

area that

is

set

aside to hold FSBs,

XDTs,

share

DTF address

list

entries,

and

incore DFF index entries.

The

size of the

external

pointer

list

(EPL),

can be

2K or 4K bytes, depend-

ing on the

options

specified.

(See

Figure

7,

Section 5 in

Appendix F.) EPL is applicable

to Program Number

5704-SC2

only.

file management: A major function of CCp

that controls

the use

of data files

by programs

running under

the CCp.

format

find: A program

(CCPFMT)

that will find a

newly

created

or modified

format

while

running

under

CCp.

initial mode: The

operating mode

of a command terminal

before

a sign-on

at the terminal is

accepted by the CCP.

inquiry: A communications-based

system application in

which

a request

for information is

entered from a

terminal

and a response is

returned to the

terminal.

Glossary 173

inquiry-with-update:

A communications-based

system

application

in

which

records

of transactions

entered

from

termirrals

are used

to interrogate

and

update

one

or more

master

files

maintained

by

the

system

(synonymous

with

inquiry and transaction

processing').

multiple

requesting

terminal

(MRT)

program:

A type

of

application program

under

the CCp

that

can

process

requests

from

more

than

one requesting

terrninal

concurrenuV.

never-ending

program:

A user

application program

that

after

it is

requested,

remains

in main

storage

for a

relatively

long

time.

noncommand

terminal: See

data

terminal.

order

entry

application:

A form

of data

entry

application

in

which

transactions

(such

as sales

orders)

are entered

into

a data file

form

remote

terminals.

password

security

option: An optional

CCp feature,

selected

during

CCP

generation,

that

requires

a

terminal

operator

to enter

a

predetermined

password

before

the

CCP

will

accept

input

from

the

terminal.

physicaf

fife: See

symbotic

file.

program

management:

The

major

function

of the CCp

that

fetches

programs,

allocates

system

resources

to

programs,

purges

programs

from

main

storage,

and

option_

ally

maintains

a

count

of

the number

of

times

each

appli_

cation

program

is requested.

program

request:

A command.

consisting

of a

program

name

entered

at

a

terminal

or the

system

operator,s

console,

that

causes

the CCP

to initiate

execution

of

an

application

program.

program-request

count: The

optional

CCp

program

management

function

of maintaining

a

count

of

the

number

of

times

each

application

program

is requested.

program

request

under

format

(PRUF):

This function

allows

DFF

to process

program

request

data

of any

length.

lf non-DFF,

this function

allows

processing

of more

than

78 characters

(up

to the

maximum

screen

size)

of program

request

data.

program-selected

terminal: From

the

point

of view

of the

application

program,

a terminal

that

is

selected

by

an

application

program

for

input/output,

as

opposed

to a

terminal

that

requested

the

program

lsee

requesting

terminall.

Program-selected

terminals

can

be

either

required

(must

be

allocated

to the

program

before

rne

program

can

run)

or acquired

(allocated

dynamicallv

to

the

program

as

it is running).

requesting

terminal:

From

the

point

of view

of

the

application

program,

a

terminal

that

requested

tne

program,

as opposed

to

a terminal

that

is

selected

by

the

program

{see

program-selected

terminall. Requestino

terminals

are

always

command

terminals.

sign-on:

The

procedure

performed

at

a terminal

while

it is

in initial

mode.

This

procedure

may

include

entering

only

the

sign-on

command,

or entering

the

sign-on

command

with

a

password

or other user-specified

securitv

oata.

single requesting

terminal

program:

A type

of application

program

under

the

CCP

that

can

process

a

request

from

only

one requesting

terminal

at

a time.

symbolic

file: A symbolic

name

in

an

application

program

which

can,

on separate

executions

of a

program,

refer

to

different

files,

known

as

physical

files.

A symbolic

file

is

terminal

operator

to a

specific

physical

f

ile

by means

of a file

command.

system

task: A unit

of work

for

the

processing

unit from

the

standpoint

of the CCP,

consisting

of a CCp function

(as

opposed

to a user

application,

or uEer

task)

rr.ar must

be

performed

by

the CCP,

such

as communications

management.

task

chaining: The

process

of requesting

initiation

of a

CCP

task from

within

a currently

executing

CCp task,

without

requiring

system or operator

action.

task

identification: An identifying

character

associated

with

a

task

that differentiates

between that task

and other

tasks

running concurrently

under

the CCP or

DSM.

terminal

reference identification: A unique two-character

identifier,

assigned to each terminal during

the CCP

assignment

stage, that is used

by the CCP and the

system

operator

to refer

to a specif ic terminal.

user task: A unit

of work

for the

processing

unit, from

the

standpoint of

the CCP,

consisting of a user

program

(as

opposed to a

system

function,

ot

system task)

that must

be executed by

the CCP.

Appendix

F. configuration

Limitations,

storage

Estimates

and

Performance

Considerations

CONFIGURATION

LIMITATIONS

AND

MAIN

STORAGE

ESTIMATES

The following

information

can

be useful

in:

o Estimating

the maximum

nurnber

of programs,

files,

and

terminals

that

can

be supported

by

a

particular

CCp

conf

iguration.

o Estimating

the main

storage

required

for

the

clynamic

TP

buffer.

o Estimating

CCP startup

main

storage

requirements.

o Estimating

the

partition

size requirement

of

an executable

CCP installation.

Estimating

CCP Configuration

Limits

The maximum

number

of

programs,

files.

and

terminals

that

can

be

supported

during

a

CCp

startup

depends

on the

main

storage

requirements

of three

parts

of CCp.

These

parts

consist

of the following:

o Common

support

code

and control

tables.

o Communication

support

code.

o User

program

area

(UpA).

The

common

support

code

and

control

table

portion

of

resident

CCP

contain

two CCp

transient

areas.

gCC4#1

,

the

user

security

data

area,

the

display

format

control

routine,

and

various

control

blocks,

all

of which

depend

on

genera_

tion

and

assignment

options.

This

part

of

CCp must

be

no

greater

than

16K. Exceeding

this

limit

will cause

CCp

startup

to

terminate.

Figure

10

or Figure

12

can

be used

to

determine

the

size

of this

part

of CCp.

Should

the results

obtained

from

these

figures

exceed

the

above

limits,

the

number

of terminals.

command

terminals,

files,

and/or

pro_

grams

may

have

to

be reduced.

An

alternative

is

to elimi_

nate

CCP requirements

such

as

program

use

counts,

interval

polling,

and

resident

accept

input.

The

communication

support

code

within

resident

CCp

con-

tains

$CCP#2, TRACE

support,

MLMp

support,

M

LTA

support.

the

line

buffers,

and

the Tp buffer. Users

of pro_

gram

Number

5704-SC2

may

have

additional

CCp

resident

code

following

the TP

buffer. This

code

may

contain

the

resident pseudo

open/close

routine,

the

external pointer

list,

the resident program

request

routine,

the DFF

support

code,

and

the

BSCC

communication

support

code.

lf the

display

format

facility

is configured,

the last

byte

of

the

DFF

control

routine

($CC4DF)

must

not

exceed

a limit

of 18K. The

TP

buffer

places

two restrictions

on

the

CCp

configuration.

The

TP

buffer itself

cannot

exceed

1

gK

bytes,

and

the highest

address

of the Tp

buffer,

always

on

a

2K

boundary,

cannot

exceed

48K. Figure

9 is

a

guideline

for

approximating

the

size

of Tp

buffer.

This

value

should

be initially

used

for

the MINTpBUF

key

word

on

the

assign-

ment

system

statement,

but may

require

adjustment

after

various

CCP

startups

to obtain

the

best response

times for

all terminals.

Figure

11

or Figure

13

can

be

used

to deter-

mine

the

main

storage

requirements

for

CCp

communica-

tion

support

code.

The

total

storage

requirements

of CCp

common

code,

the

control

tables,

as

well

as

the communrca_

tion

support

code

make

up resident

CCp.

The user

program

area immediately

follows

the

CCp resident

code

and extends

to the end

of the CCP

partition.

The

user

program

area

contains

the

user's

programs,

any appropriate

DSM modules

included

when

link-editing

the

application

programs,

storage requirements

for memory

resident

over-

lays

and external

buffers,

and the

additional

storage

require-

ments

of the

display format

facility.

Additional

storage is

required

within

the user

program

area if

the display format

facility

(DFF)

is

used

to support

the

3270

terminal

system.

This

storage

is

called

program

appended

storage

(pAS).

The

size

of

the CCP

partition

and/or minimum

user

program

area

(MINUPA

parameter

within

the

assignment

set) mav

be

adjusted

to allow

the CCP

configuration

to fit.

Conf

iguration

Limitations,

Storage Estimates

and Performance

Considerations 175

Using

This

Appendix

The

figures

within

this

appendix

are useful

in making

storage

estimates

and checking

for

any limitations

of

CCp.

These

figures

are

constructed

as

a

list

of options

with

the

corres-

ponding

main

storage

(given

in

number

of

decimal

bytes)

needed

for that

option. The

option

so far

as

possible

is

given

as

a

keyword

with

a

reference

to

a

particutar

statement

for

CCP

generation

or

assignment.

lf any

part

of a

listed

option meets

the requirement

of the

desired

system

configur_

ation,

then

the

main

storage

on that line

in

the

table

should

be

added

to

the

system

size.

The

options

that

are indented

are to

be included

in

the

system

size

only if

the desired

system

configuration

also

includes

the

preceding

nonindented

option.

This

appendix

is

designed

to be used

top

down.

Main

storage

totals

obtained

in

the latter

f igures

depend

upon

totals

obtained

in

some

of

the

preceding

figures.

Users

of Program

Number

5704-SC1

will use

Figures

7,

9,

10,

11,

14,

and

15. Users

of program

Number

S704-SC2

wilf use

Figures

8,9,12,

13,14,

and

15.

A

general

explana_

tion

of each figure

follows:

- Figure

7 (5704-SC1

only)

is used

to estimate

the

sizes

of

two portions

of CCP resident

code

referred

to as common

support

code

and communication

support

code.

These

two

portions

are known

internally

as

$CC4#1

and

$CC4f2. Both

are

totally

dependent

upon

CCp

genera-

tion

specifications

and options.

The

common

supporr

code

($CC4#1

),

and

the

communication

support

code

($CC4#2)

are

loaded

into

storage

at separate

phases

of

CCP

startup.

Totals

obtained

from

this figure

will

be

used

in Figures

10

and

11.

- Figure

8 (5704-SC2

only) is

used

to estimate

the

sizes of

three

portions

of CCP resident

code

referred

ro as com_

mon

support

code,

communication

support

code,

BSCC

support

code.

These

three

portions

are known

internally

as

$CC4#1

,$CC4#2,

and

$CC4#M.

They

are

totaily

dependent

upon

CCP

generation

specifications

and

options.

The

common

support

code

(gCC4#1

),

the

communication

support

code

(gCC4#2),

and

the BSCC

support

code

($CC4#M)

are

loaded

into

storage

at

separate

phases

of CCP

startup.

Totals

obtained

from

this

figure

will

be used in

Figures

12

and

13.

- Figure

9 is

useful

in

estimating

the

size

of the

dynamic

TP

buffer

and verifying

that it

does

not

exceed

a

limit

of

18K.

The

calculated

size

of

thr: Tp

buffer

is used

in

Figure

11

(5704

SC1)

or

Figurr:

j2 (57O4-SCZ|.

- Figure

10

(5704-SC1

onlv) is used

to estimate

the

size of

CCP common

support

code

and

control

tables. This

portion

of CCP

resident

storage

contains

the transient

areas,

$CC4#1,

user

security

routine,

and control

blocks

all of which

depend

on

CCP

generation

and

assignment

options.

The

CCP components

listed

are, as near

as

possible,

in

the

same

sequence

as they

are

positioned

in

main

storage.

This

part

of CCP must

be no

greater

than

18K for

a DFF

system.

Exceeding

this limit

will

cause

startup

to terminate.

The

total

obtained

from

this

figure

is

used

in Figure

1 1.

- Figure

11

(5704-SC1

only)

is used

to estimate

the size

of

resident

CCP. The

total obtained

within

this figure

includes

all

of CCP resident

code,

all control

tables, line

buffers,

the

TP

buffer.

MLMP

and MLTA

support,

and

any trace

support.

This

total

cannot

exceed

4gK. The

CCP

components

listed

are,

as near

as

possible.

in

the

same sequence

as they

are

positioned

in main

storage.

The

total

obtained

can be used

in Figure

1b.

- Figure

12

(57O4-SC2

only) is used

to estimate

the

size of

CCP

common

support

control

tables.

This

figure

is

functionally

the same

as Figure

10

and

has

the

same

storage

limitation.

The

CCP

components

listed

are.

as

near

as

possible,

in

the same

sequence

as

they

are

posi-

tioned

in main

storage.

The

total

obtained

from

this

figure

is used

in Figure

13.

- Figure

13

(5704-SC2

only) is

used

to

estimate

the

size

of

resident

CCP. The

total

obtained

within

this figure

includes

all

of CCP resident

code,

all

control

tables. line

buffers,

the TP

buffer, MLMP

and

MLTA support,

trace

support,

resident

open/close, resident

program

request,

and

BSCC

communication

support.

The

CCP componenrs

listed

are,

as near

as

possible,

in the

same

sequence

as they

are

positioned

in main storage.

The

total

obtained

can be

used in

Figure

15.

- Figure

14 is

used

to estimate

the storage

within the

user

program

area required for DFF

program

appended

storage

(PAS).

- Figure

15 is

used

to determine the

total executable

CCP

partition

size. This includes

all of resident

CCP and the

user

program

area.

The specifications

made in

an assignment

set

represent

the

standard operating

environment for

a CCP run.

Certain

resources specif ied

in

an assignment

set as being

available to

the CCP

run

can, on

an

exception

basis, be

suppressed by

the system

operator

at the startup

of the

CCP

run. Such a

suppression

reduces

the control

block main

storage

require-

ments

as

defined in Figure

10

or Figure

12.

lto

Add

orrly

the items

below

that

pertain

to

your

CCp

generation

specif ications

and

options.

Common

to all

generations

. . .

Multiple

MLTA

and/or

BSCA

lines

(see

note

1)

ESCAPE-'YES'($EFAC)

ACCEPT.YES

($EFAC)

CPUMSG-NO

($EFAC}

MLTA

($EMLA)

XLATE.NO

($EMLA)

ESCAPE-YES

($EFAC)

TYPE-(dialed

feature

terminals)

($EMLD)

TYPE-(station

control

term irrals)

TYPE-(1050

terminals)

TYPE-(no

checking

basic

terminals)

TYPE-(checking

term inals)

TYPE-1050

or 1050D

TYPE

1OsOD

TYPE.1O5O

TYPE-1

050,

27 4OSC,

27 4ONI2SC

or 2740SCB

TYPE-2740SC,

2740M25C,

2740M25CB

or

SySTSC

TYPE-2740S,

27 40M25

or 27 4OM2SB

rYPE-2740

TYPE.274OD

TYPE-2740C

or

SYSTC

TYPE-2740DC

or SYSTDC

TYPE.274ODT

TYPE-274ODTC

TYPE"27

41,

27 41 D

or CMCSTD

TYPE.2741

TYPE-2741D

or

CMCSTDT

XMCODE-COR

R

($EMLD)

XMCODE

PTTCEBCD

XMCODE.PTTCBCD

BSCA

($EBSC)

FOBMAT.YES

($EFAC}

PRUF

YES

PR

U F.YES

BSYPRT.YES ($EFAC}

ESCAPE'YES'

TYPE.327O

($EBSD)

TYPE

CPU

($EBSD)

MLTA

($EMLA)

TYPE.(STATION

CONTROL

TE

RM

I NALS)

($EM

LD)

BSCA.2

($EBSC)

MULTIPLE

BSCA

and/or

Mt__TA

LTNES

MLTA

($EMLA}

CS

YES

or DIAL-YES

($EBSC)

PP-YES,

MP-YES

or DIAL-YES

CS.YES

RESPOL

YES

PP-YES,

MP-YES

or DIAL-YES

($EBSC)

MP.YES

PP.YES,

CS

YES

or DtAL-yES

AUTHORS,YES

$cc4#1

4753

II

272

33

124

4

I

146

1744

52

$cc4#2

2221

z5

18

$;

52

74

z6z

6ZJ

4

230

217

7')

54

51

54

40

54

zt35

3400

JC

B4

103

o

109

4

:203

97

J

:208

6

too

1i163

6

o

329

FigureT(Partlof 2). EstimatingstorageRequirementsforCCpCommonSupportCode($CC4#1

landCommunicationSupportCode

($CC4rtz)

- 5704-SC1

only

Conf iguration

Limitations,

Storage Estimates

and

Performance

Considerations 177

BSCA

($EBSC)

(continued)

DIAL-NO

DIAL.YES

MP-YES,

CS-YES

or

pp-yES

MP.YES

MLTA

($EMLA)

PP-YES

or

Mp-yES

($EBSC)

DA.YES

($EBSC)

DIAL"YES

DIAL

NO

3270

0NLY

MIN

RES-NO

and RESpOL_yES

GETMSG-YES

($EBSC)

ITB.YES

($EBSC)

XPRNCY

YES

($EBSC)

XPRNCY

YES

ASCII

YES

($EBSC)

TYPE.3270

($EBSD)

TYPE.CPU

INTPOL

YES

($EBSC)

TYPE

CPU

($EBSD)

TYPE-3270,

3741

or

3735

TYPE

3270

or

3741

TYPE

3741

ASCII.YES

TYPE

3270

or 3735

TYPE.3735

ASCII

YES

($EBSC)

TYPE

3270

($EBSD)

DIAL.YES

($EBSC)

CS

YES

CS.YES

($EBSC)

DIAL"YES

MLTA

($EMLA)

ESCAPE.'YES' ($E

FAC)

ASCII.YES

($EBSC)

TYPE

3741

($EBSD)

ESCAPE.'YES' ($E

FAC)

PRUF

YES

($EFAC)

MINRES.NO

($EGEN)

DIAL.YES

PP-YES,

Mp-yES

or

CS-yES

GETMSG.YES

($EBSC)

ITB.YES

($EBSC)

XPRNCY-YES

($EBSC)

MINRES

YES

($EGEN)

Totals

. . .

Notes:

1.

Include

if

number

of MLTA

lines

plus

number

of

BSCA

2. Also

enter

total

for

gCC4#1

in Figure

4,

Section

1.

3. Also

enter

total for

gCC4#2

in Figure

5,

Section

1.

$cc4#1

h

J

See note*- 2

$cc4#2

97

547

144

6

b

418

4400

33 14

341

91

'19

24

13

92

23

'184

32

59

29

2

23

14

353

't6

o

9

6

7

28

6

J

384

8

25

31

3

lines

is

greater

than

one.

Figure

7 (Part

2 of 21. Estimating

Storage

Requirements

for CCp

Common Support

Code

{$CC4#l }

and

Communication

Support

eode

($CC4#2) - 5704-SC1 only

178

Add

only

the items

below

that

pertain

to your

CCp

generation

specifications

and

options.

Common

to all

generations

. . ,

Multiple

M

LTA

and/or BSCA

lines

(see

note

l )

FORMAT.YES ($EFAC)

MOVTNT.YES

ACCEPT.YES

RESOPN.YES

RESREO-NO

ESCAPE-YES

MOVTNT.YES

BSCA

($EBSC)or

MLTA

($EMLA)

BSCC

($ECSC)

ESCAPE-YES

($EFAC)

MINRES.NO

($EGEN)

MLTA

($EMLA)

XLATE.NO

($EMLA}

ESCAPE-'YES'

($EFAC)

TYPE-(dialed

feature

terminals)

($EMLD)

TYPE-(station

control

term

inals)

TYPE-(1050

terminals)

TYPE-(no

checking

basic

terminals)

TYPE-(checking

terminals)

TYPE-(

buffered

receive

term

inals)

TYPE-1050

or

1050D

TYPE.1

O50D

TYPE-1050

MOVTNT.YES

TYPE-

1 050,

27 405C,

27 4OMZSC

or 2740SCB

TYPE-

2740SC,

27 40M2SC,

27

40M2SCB

or SySTSC

TYPE-27405,

274OM2S

or 2740M2SB

TYPE.2740

TYPE-2740D

TYPE-274OC

or SYSTC

TYPE-2740DC

or SYSTDC

TYPE-274ODT

TYPE-274ODTC

TYPE-27

41

.

27

41

D

or CMSTD

TYPE.2741

TYPE.2741or

CMSTD

BSCA

($EBSC)

MLTA

($EMLA)

BSCA-2

($EBSC)

DA-YES

($EBSC)

Multiple

BSCA

and/or

MLTA lines

(see

note

l)

INTPOL-YES

($EBSC)

XPRNCY.YES

ITB.YES

($EBSC}

XPRNCY-YES

BSYPRT.YES

$cc4#1

4732

1770

14

315

32

22

20

,u:

66

75

22

$cc4f2

575

,:

rc;

7

18

4

$Cc4#r\4

5342

56

80

282

827

4

230

217

39

72

il3

146

52

;3

il

54

u

il

v

il

40

g

5335

98

203

418

105

201

31

18

24

103

Figure 8 (Part 1 of 31. Estimating Storage Reqtrirements

for CCp Common Support Code ($CC4# l, Communication Support Code

($CC4#2), and BSCC

Support Code (gcc4*hrl - 5704-SC2 onty

conf iguration Limitations, storage Estimates

and performance considerations 17g

BSCA

($EBSC)

(continued)

ASCII-YES

($EBSC)

TYPE-3270

($EBSD)

TYPE.CPU

TYPE.3735

TYPE.374'I

MINRES.NO

($EGEN)

DIAL.YES

($EBSC)

PP-YES,

MP.YES

or

CS-yES

GETMSG-YES

($EBSC)

ITB-YES

($EBSC)

XPRNCY-YES

TYPE.3270,3741

or 3735

MLTA

($EMLA)

PRUF-YES

($EFAC)

RESPOL-YES

FORMAT.YES

($EFAC)

PRUF-YES

($EFAC)

GETMSG-YES

($EBSC)

ESCAPE.'YES'($EFAC}

TYPE.3270

($EBSD)

TYPE.CPU

($EBSD)

TYPE-3270,3741

or 373b

($EBSD)

TYPE.3270

or

3741

TYPE.3270

or

373b

TYPE-3270

or ESCAPE.'YES'

TYPE.3735

($EBSD)

TYPE-3741

TYPE-3270

DIAL-YES

($EBSC)

CS-YES

($EBSC}

DIAL.YES

MLTA

($EMLA)

ESCAPE-'YES'

or PRU

F-YES

ESCAPE.'YES'

($E

FAC)

PRUF.YES

DIAL-YES

or TYPE.3735,3741

or

CpU

MIN

RES-YES

or RESPOL-NO

TYPE-CPU

($EBSD)

CS-YES

or

DIAL-YES

($EBSC)

PP-YES,

MP-YES

or DtAL.yES

DIAL-YES

MP-YES,

CS-YES

or

PP.YES

MP.YES

MLTA

($EMLA)

CS.YES

PP-YES,

MP-YES

or DtAL.yES

($EBSC)

DIAL.YES

($EBSC)

R

ESPOL.YES

$cc4#1

3

o

$cc4#2

g4

tr1

1a

lz.

14

1a

375

6

at

22

26

F

16

337

3430

35

84

94

39

o

59

29

3

23

OU

350

16

18

I

J

5

3

l.+ z

337

5Z

208

6

587

42

J

o

172

18

o

1 893

$cc4#M

Figure

8 (Part

2

of 3)' Estimating

Storage Requirements

for

CCP

Common Support

CodE

{$CC4#1

),

Communication

Support

code

ISCC4#2].,

and BSCC

Support

Code

($CCa#M) - S704.SC2 onty

180

BSCA

($EBSC)

(continued)

PP-YES,

MP-YES

or CS-yES

($EBSC)

PP"YES,

MP.YES

or DtAL-yES

($EBSC)

PP-YES

or MP-YES

($EBSC)

MP-YES

PP-YES,

CS-YES

or

DtAL-YES

AUTORS-YES

BSCC

($ECSC)

FOBMAT-YES

($EFAC)

BSCC-2

($ECSC)

INTPOL-YES

($ECSC)

BSCC.2

($ECSC)

ESCAPE-'YES'($EFAC)

ASCII

YES

($ECSC}

GETMSG-YES

($ECSC)

BSYPRT.YES

itoc

BSCC-NO

MOVTNT-YES

$cc4#1 $cc4#2

u

6

18

6

329

52

$cc4#f\4

94

52

4

11105

65

56

43

10

73

38

13

111

1162

1r

105

4

Totals

. . .

Notes:

i. Include

if

number

of MLTA

lines

plus

number

of BSCA

lines is

greater

than

one.

2. Also

enter

total

for

gCC4#1

in

Figure

12,

Section

1.

3. Also

enter total

for

$CC4l2

in

Figure

13,

Section 1.

4. Also enter

total for

$CC4#M

in Figure

13,

Section 10.

Figure

8 (Part

3 of 3). Estimating

Storage

Requirements

for CCp

Common Support Code

($CC4#1

),

Communication

Support

Code

($CC4#2),

and BSCC

Support

Code

($CC4#M) _ 5704-SC2 onty

Conf

iguration

Limitations,

Storage Estimates

and Performance

Considerations 181

Follow

steps

one through

six

to estimate

the

size

of the dynamic

Tp

buffer.

Refer

to system,

TERMATTR,

PoRTLINE,

and

program

statements

within

the

CCP

assignment

set.

Put

Area

1 A lf

any

TERMATTR

statement

is

DFF

(DFF

3270-YES),

enter

516

B lf

any

TERMATTR

statement

is

NON-DFF

or if

Program

Number

5704-SC2

and

any BSC

line

has

an

optional

DFF

buffer,

enter

the

longer

of RECL+4

or BLKL+23.

Common

Area

2 Refer

to the

program

statements

and enter

the

maximum

result

of;

(2

x the

number

of terminals

allocated

to any

task)

+

(4

x the

number

of

disk files

allocated

to the same

task)

+

34.

3 Enter

the maximum

result

of A, B,

or

C

below.

A DFF

request

tength

(pRUFLNG)

+

l9

B Program

request

length

(pGMREOL)

+ 12

C Command

length

(COMMANDL)

+ 12

4 For

5704-SC2

with

SIOC

only

Enter

the

result

of

;

(value

of MAXMSG

specified

on

pORTLINE

statement)

+ 15

+

(the

value

calculated

in

step

2

above).

Invite

Area

5 Enter

the result

of A or B below.

A (number

of input

capable

terminals

x23l +

4

(5704.SC1)

B (number

of input

capable

terminals

x 2Ol

+

4

(5704-SC2)

TOTAI

TPBUFF

6 Add

items

1

through

5

above,

enter

result.

The

result

should

not exceed

18K

il8,432) and if pro_

gram

Number

5704"SC2

using

optional

DFF

buffer,

the

minimum

is

2K (2.048).

lf so, enter

result

in

Section

3 of Figure

1

1 (5704.SC1

)

or Section

4

of Fisure

13

(5704-SC2).

Figure 9. Estimating Storage Requiremants for the Dynamic Tp Buffer

182

ccP

Components

I nternal

Terminologv Details for Estimating

Storage Requirements

Section

1-General

Applies

to all

CCP configurations

Transient

areas

Common

CCP

code

Program

request

count

table

User

secu ri

ty

Terminal

attribute

set

Section

1

tota I

T1

&T2

$cc4#t

PCT

$cc4z9

TAS

Space reserved

for CCP transients.

Enter

$CC4#1

storage requirements

from Figure

7 here.

lf PGMCNT-YES

($EFAC),

enter

2

x (number

of

program

statements

in

assignment

set).

1024

lf

secure-user

is

used in

$ESEC

statement,

enter

size of

user's

security

information

(value

of LUSI keyword).

Enter

5

x (number

of TERMATTR

statements

in

assignment

set).

Add results

within

this section,

enter

total here

and in

Section

8 below.

Section 2-Control

information

for

MLTA

communications lines. lf no MLTALINE

statements

in

assignment

set, skip

to Section

3.

Def ine

f

ile/line

control

block

Terminal

stat i

sti cs

tables

Polling

list

(note

1)

DTF/LCB

TST

POLLLIST

Refer

to MLTALINE

and MLTATERM

statements within

assignment

set.

MLTA line

numbers

. . .

1234s678

Enter

1 26

bvtes for each

MLTALINE

statement.

EnterSx(numberof

MLTATERM

statements)

for each

MLTALINE

statement.

Enter

12 x (number

of 1050

terminal

entries

in POLLLIST)

for each MLTAI INF statemen

Also enter

6

+ (3

x number

of

non-1050

terminal entries

in

POLLLIST)

for

each

MI TAI INF statpment

Figurel0(Partlof 6). StorageRequirementsforCommonCodeandControl

Tables-5704-SC1

only

Conf

iguration

Limitations,

Storage Estimates

and Performance

Considerations 183

ccP

Components

I

nternal

Terminology Details

for Estimating

Storage

Requirements

Check

list

MLTA

line

buffers

(note

1

)

Line

tota

I

s

Adaptor

DTF

Section 2

total

DTF

MLTA

line numbers

. . .

_12345678

Enter

3

for each

MLTALINE

t

Enter

the

appropriate

values

as

calculated

below

for

each

terminal type

on

each

MLTA line.

2741 MAXRECL

+

15

=

1050 or 2740

automatic

polling: MAXRECL

+

14

=

1050 not

automatic

pollino: MAXRECL

+ l7

-

2740 control

station,

not

automatic

polling:

MAXRECL

+17

2740 transmit control:

MAXRECL

+17

All others terminal types:

MAXRECL

+

15

=

Add results

above

for each

MLTA, line.

Main

storage

requirement for

MLTA adaptor

DTF.

Add line

totals and

adaptor

requirements.

Enter result here

and

in

Section 8

below.

Note

1

- The MLTA POLLLIST

and

line

buffers are actually

located

just

before

$CC4#2.

+33

Figure 10 lPart 2 ot 6). Storage Requirements f

or Common Code and Control Tables

- 5704-SC1 only

1U

Details

for Estimating

Storage

Requirements

Section

3-Control

information

for

BSCA

communications

lines.

lf no

BSCALINE

statements

in

assrgnment

set,

skip

to

Section

4.

Def

ine

file/l

ine

control

block

Addressing

I ist

Terminal

stat i

sti

cs

tabl

es

Check

list

Line

tota I

s

Section

3

tota

I

DTF/LCB

ADDR

LIST

POLLLIST

Refer

to BSCALINE

and

BSCATERM

statements

within

assignment

set.

Enter

1

36

bytes

for

eacn

BSCALINE

statement.

lf TYPE.SW

within

BSCALINE

statement,

enter

4 for those

line numoers.

lf TYPE-CS

in

BSCALINE

statement,

enter

((number

of BSCATERM

statements)

x

(number

of ADDRCHAR

characters

+

3)

+

1)

for

each

line

statement.

lf TYPE-CS

in

BSCALINE

statement.

enter

((number

of

POLLLIST

entries)

x (number

of

POLLCHAR

characters

+

3)

+ 1l for

each

line

statement.

Enter

4 + ((number

of BSCATERM

statements)

x

2 x (number

of POLLCHAR

+

7)) for

each

line

statement.

Enter

3 for

each

BSCALINE

statement.

Add

results

above

for

each

BSCA

line.

Add

both

line

totals,

enter

result

here

and in

Section

g

below.

Figure

10 (Part

3 of 61. Storage

Requirements

for Common Code and

control Tabtes

- 5704.SC1

only

BSCA

line

number.

12

conf iguration

Limitations,

storage

Estimates

and performance

considerations lgs

Details

for Estimating

Storage Requirements

Section

4-Control information

for BSCA

and/or

MLTA

terminals.

Terminal

unit

block

Terminal

name

table

Section

4

total

Refer

to MLTATERM,

BSCATERM

and

TERMNAME

statements

within

assignment

set.

Enter

38

x (number

of MLTA

and BSCA

terminals).

Also

enter

19 x (number

of BSCA

switched

terminalsl

+ 1

Also

enter

19

x (number

of BSCA

command

terminals)

+ 1

Enter

23

+ (11

x number

of TERMNAME

statementsl.

Add

results

within

this

section,

enter

result

here

and in

Section

g

below.

lf no

SYMFILE

statements

within

section

S-control

information

for

symbolic

and

associated

symbolic

files.

assignment

set,

skip

to

Section

6.

F

ile

speci fi

ca-

tion blocks

Symbolic

file

table

bectton 5

total

Refer

to

SYMFILE,

BSCATERM

and

program

statements

within

assignment

set.

Enter

(number

of

SyMFILES)

x ((1

+

number

of command

terminals)

+ (number

of

user

programs

allowed

to run

concurrently

*

) ).

* |5 maximum

Calculate

the

size

of

one

XDT

for

each

SyMFILE

statement.

Each

table

=

9

+

number

of DISKFILE

references

within

SYMF

ILE

statement.

Enter

total for

all

SYMFILE

statements.

The

XDT

is

actually

located

following

the SDF

address list

below.

Add

results

within

this

section,

enter

total here

and in

Section

g

below.

Figure 10 (Part 4 of 6). Storage Requirements

for Common Code and control Tables

- 5704-SCl only

186

ccP

Components

I

nternal

Terminology Details for Estimating

Storage Requirements

Section

G-Control

information

for

disk

files.

lf no

diskfile

statements

*,*" .*n"rn.", *, *O a

Section

7.

Short

DTF

Short

DTF

address list

F

ile

shari ng

queue

element

CCP

master

i ndexes

Section

6

tota I

SDF

@

LIST

FSOE

SDF Choose

the

appropriate following

lines

according

to diskf ile

statement

organizations

in

the

assignment

set. The

control

blocks

are

positioned

in main

storage

in

the same

sequence

as

the

diskfile statements

in

the assignment

set.

Enter

20 X (number

of direct

diskfile

statements).

Enter

21 X (number

of consecutive

diskfile

statements).

Enter

30 X (number

of indexed load

diskfile

statements)

+ 2 x (the

key length

for each

indexed

file).

Enter

38 X (number

of indexed

random

diskfile

statements)

+

2 x (the

key length

for each indexed

file).

lf track index

exists,

enter

3 x (number

of indexed

add

files).

Enter

11

X (number

of physical

f

iles).

Enter

15

X

the number

of FSOE's

specified

in

the

assignment

set,

or

Calculate

the following

ratio for

each

program.

R = (number

of

shared

files)/(number

of 2K

blocks

required

bv

program

)

Use

the largest

calculated ratio for'R'below. Enter

15 X R

X (the

maximum

number

of

copies

of the

program

used

to obtain R

that can

fit into

the

user

program

area.

Calculate

one master

index

for

each diskfile

statement with

MSTR

I N DX-YES

specified.

Master

index

length

=

value

specified

for

MIXSIZE

keyword

within

diskfile

statement.

or

Master

index

length

= (KEYL

+

2)

x [(number

of

disk

cylinders

in

index)

+

3)l .

Enter

total

for all master indexes

here.

Add

results

within

this

section,

enter

total here

and

in

Section

8

below.

Figure 10 (Part 5 of 6). Storage Requirements

for Common Code

and Control Tables

- 5704-SCl only

Configuration

Limitations, Storage Estimates and

Performance

Considerations 181

ccP

Components I nternal

Terminology Details

for Estimating

Storage

Requirements

Section

7-Control

information

for

user

programs.

Program

cha racter-

istics

table

PCT Enter

6 X the number

of sectors

of PCT

in

$CCpFlLE,

or

as a rough

approximation,

enter

1.5 X number

of program

statements rounded

up

to the nearest

multiple

of

6. Also enter

value

in

Section

g

below.

Section

8-CCP

common

code

and

control

table

totals

Common

code

and

control

table

total

Enter

total

from

Section t here.

Enter

total

from

Section 2 here.

Enter

total from

Section

3

here.

Enter

total from

Section 4 here.

Enter

total from

Section

5

here.

Enter

total from

Section

6

here.

Enter

total from

Section 7 here.

Add

all lines

above.

Sum

represents

size of

all

CCP common code

and

control

tables. lt cannot

exceed

16K

(j6,384)

for

any CCp configura-

tion. lf DFF

is configurated,

the

above sum

cannot exceed

15,254

bytes.

lf DFF

and MLTA

is configured,

the

above sum cannot exceed

15,246

bytes less

3 bytes

for

each individual

tVpe of MLTA

terminal.

Figure

10 (Part

6 of 6). Storage

Requirements

for Common Code

and

Control Tables

_ S704-SC1

only

ccP

Components

I nternal

Terminology Details

for Estimating

Storage Requirements

Section

1-General

Applies

to all

CCP configurations

Common

code

&

control

tables

Communica-

tion

support

code

BSCA

trace

MLTA

trace

Section

total

$cc4#2

$cc$BS

$cc$M

L

Enter

the total from

Section 8 of Figure

4 here.

Enter

the

$CC4#2

storage requirements

from

Figure

t here.

lf

TRACEMLMP

will

lf

TRACEMLTA

will

be specified

at startup enter

650.

be specified

at startup enter

1 325.

Add results

within this

section, enter

total here

and in

Section 3 below.

Figure

11 (Part

1 of 2). Storage Requirementsfor

Resident

CCp

- 57O4-SC1

only

Con{iguration Limitations, Storage Estimates and Performance

Considerations 189

ccP

Components

I

nternal

Terminology Details for Estimating

Storage Requirements

Section

2-Line buffers

for

BSCA

communications

lines. lf no BSCALINE

statements in assignment

set,

skip

to

Section 3.

BSCA

line

buffers

Section 2

total

Refer

to

TERMATTR,

BSCALINE

and BSCATERM

statements within

assignment

set.

Calculate

the size

of each line buffer

as

follows:

1 Enter

(largest

BLKL value used

on

each

line)

+

42.

2 lf ITB-Y,

TRANSP-N

within

TERMATTR

statement,

enter

t here,

3 lf ITB-Y,

TRANSP-Y

within

TERMATTR

statement,

enter

7 here.

4 lf DBLBUF-YES

within BSCALINE

statement.

add lines

1,

2, and 3 and enter

total

here.

5 lf XMCODE-ASCll

specified in BSCALINE

statement,

add lines

1,

2,

and 3 and enter total here.

6 lf TYPE-SW within

BSCALINE

statement, enter number

of IDEXSEND

characters here.

7 lf TYPE-SW

within

BSCALINE

statement,

enter number

of IDEXRCV

characters within BSCATERM

statement

nere.

8 Add items

1 through 7

above

for each

BSCA line,

and

enter

totals here.

Add

totals

of both

BSCA lines. enter

result here

and in

Section

3

below.

Line Number

12

Section 3-Resident

CCPtotal

s.

Resident

CCP

total

Enter

total from

Section

t here.

Enter

total from

Section 2here.

Enter

the

size of the TP buffer

from Figure

3 here.

Add

the 3 lines

above,

and round up to the next

2K (2,048],

increment.

The

difference

is added

to the

size of TP buffer. The result represents

the

size of resident

CCP and cannot exceed

48K

(49,152).

Figure 11 lPart2 ot 2). Storage

Roquiremonts

for Resident

CCp-5704-SCl only

ccP

Components Internal

Terminology Details

for Estimating

Storage Requirements

Section

1-General

Applies

to all

CCP configurations

Transient

areas

Common

CCP

code

Program

request

count

table

User

security

Terminal

attribute

set

Section

1

total

T1

&T2

$cc4#1

PCT

$cc429

TAS

Space reserved

for CCP

transients.

Enter

$CC4#1

storage requirements

from Figure

8 here.

lf PGMCNT-YES

($EFAC),

enter

2 x (number

of pROGRAM

state-

ments

in

assignment

set).

r

536

lf

SECURE-USER

is used

in

$ESEC

statement,

enter

size of user,s

security

information

(value

of LUSI keyword).

Enter

5 x (high

sequence

number

specified

in the ATTRID param-

eter

of the TERMATTR

assignment

statement).

Add results

within

this section,

enter

total

here

and in section

10

below

Section

2-Control information

for MLTA communications

lines. lf no MLTALINE statements in

assionment

set,

skip to Section 3.

Def ine

f

ile/line

control

block

Terminal

stat i

sti cs

tables

Polling

list

(note

1)

CheckI ist

DTF/LCB

TST

POLLLIST

Refer

to MLTALINE

and

MLTATERM

statements

within

assignment

set.

MLTA

Line Numbers

. . .

12345678

Enter

1

26 bytes

for each

MLTALINE

statement.

Enter5x

(numberof

MLTATERM

statements)

for

each

MLTALINE

statement.

Enter

12

x (number

of 1050

terminal

entries

in POLLLIST)

for

each

MLTALINE

statement

Also enter

6

+ (3

x number

ol

non-1050

terminal

entries

in

POLLLIST)

for

each

MLTALINE statement

Enter

3 for

each

MLTALINE

statement.

Figure

12 (Pan

1 of 61. Storage

Requirementr for Common

Cod6 and

Comrol

Tables

- S7O4-SC2

onty

Configuration

Limitations, Storage Estimates and Performance

Considerations 191

ccP

Components

I nternal

Terminology Details

for Estimating

Storage

Requirements

MLTA

line

buffers

(note

1)

Line

totals

Adaptor

DTF

Section

2

tota

I

DTF

Enter

the

appropriate

values

calculated

below for

each

terminal

type

on

each

MLTA

line.

2741: MAXRECL

+

15

=

1050

or 2740

automatic

polling:

MAXRECL

+

14

=

1050

not

automatic

polling:

MAXRECL

+

17

=

2740

control

station,

not

automatic

polling:

MAXRECL +

17

=

2740

transmit

control :

MAXRECL

+

IZ

=

All

others

terminal

types:

MAXRECL

+

15

=

Add results

above

for each

MLTA

line.

Main

storage

requirement

for

MLTA

adaptor DTF.

Add line

totals

and

adaptor requirements.

Enter result

here

and in

Section 10

below.

Note

1-The

MLTA

POLLLIST

and

line

buffers

are actually

located

just

before

$CC4#2.

+33

Figure 12 lPart 2 ot 61. Storage Requirements

for Common code and Control Tabtes

- 5704-SC2 only

ccP

Components

I nternal

Terminology Details

for Estimating

Storage Bequirements

Section

3-Control inforrnation

for

BSCA

and

BSCC communications

lines. lf no

BSCALINE

statements

within

assignment set,

skip to

Section 4.

BSCA

line

con

trol

block

BSCC line

control

block

Check

list

Line

totals

Section

3

tota I

DTF/LCB

DTF CLB

Enter

137

bytes for each BSCALINE

1or2

lf TYPE-SW

within BSCALINE

statement,

enter 4 for

those line numbers.

Enter

132 bytes for each BSCALINE

3or4

Enter

3

for

each BSCALINE 1 or 2 statement.

Add

results

above for each

BSCA

line.

Line

Number

1234

Add all

line

totals, enter result here

and

in

Section

10 below.

Section

4-Control information

for the

serial l/O channel

and BSCA

or BSCC

PORTLINE. lf no

PORTLINE statement

within assignment

set,

skip

to Section 5.

SIOC

line

control block

BSCA

PORT

LI

N E

control block

BSCC

PORTLINE

control block

Check

list

Section 4

total

DTF/CLB

DTF/LCB

DTF/CLB

Enter

131 bytes for

each PORTLINE type SIOC.

Enter

137 bytes for

each

PORTLINE

type

line

1,

line

2, or

TTASK.

Enter

132 bytes for each PORTLINE

type

line

3 or

line

4.

Enter

3

for

each PORTLINE

type

line

1,

line

2,or TTASK.

Add all

line

totals; enter

result

here

and

in section 10

below.

Figure 12 (Part 3 of 61. Storage Requirements for Common Code and Control Tables

- 5704-SC2 only

Configuration Limitations,

Storage

Estimates and Performance Considerations 193

Details

for Estimating

Storage

Requirements

section

S--control

information

for BSCA,

BSCC

and MLTA terminals.

control

information

for

SIOC

ports.

Terminal

unit

block

Section

5 tota

Refer

to MLTATERM,

BSCATERM,

and

pORTL|NE

statements

within

assignment

set.

Enter

39

x (number

of MLTA and

BSCA

and

BSCC

term inals

).

Also

enter

19

x (number

of BSCA

switched

terminals)

+1.

Also

enter

19

x (number

of

command

terminals)

+

1.

Also enter

58 x (number

of acquirable

and

nonacquirable

BSCA

or BSCC

ports)

Also

enter

39

x (number

of

acquirable

and

non-

acquirable

SIOC

ports).

Also

enter

45

x (number

of

task chaining

terminals

as

specified

on

MAXCHAIN

parameter

in

the

SYSTE

M assignment

statement).

Add

results

within

this

section,

enter

total

here

and

in

Section

10

below.

Section

6-control informar.ion

for

BSCA,

BSCC,

and

MLTA

terminals.

control

infor-

mation

for

Sloc ports.

rf

terminar

name

tabre

MovEour (MovrNT) specif

ied,

skip to

Section 7.

Terminal

name

ta

ble

Section

6

total

Refer

to TERMNAME

and

PORTLINE

statements

within

assignment

set.

Enter

23

+

(1'l

x number

of TERMNAME

statements

).

Enter

11

+ (11

x number

of

SIOC

ports,

BSCA

ports,

and

BSCC

ports

specified).

Add

results

within

this

section,

enter

total here

and

in

Section

10

below.

Figure 12 (Part 4 of 61. Storage

Requirements

for Common Code and Control Tabtos

- 57o4-SC2 only

194

ccP

Components I nternal

Terminology Details for Estimating

Storage

Requirements

Section

7-Control information

for

symbolic

and associated symbolic files. lf

resident

open/close

(RESOPN)

specified

or more than

S0 disk

files

or resident

DFF

indexed

(DFFINDX)

specified,

skip

to Section

9. lf no

SYMFILE statements

within

assignment

set,

skip

to Section

8.

File

specif

ication

blocks

FSB

Refer

to SYMFILE, BSCATERM,

and

program

statements

within

assignment set.

Enter

(number

of SYMFILES) x (number

of

com-

mand

terminals)

+ (number

of user

programs

allowed

to run

concurrently").

* 15 maximum

Calculate

the

size

of one XDT for

each

SYMFILE

statement.

Each

table

=

9 + number

of diskfile

references

within

SYMFILE statement. Enter

total

for

all

SYMFILE

statements. The

XDT is acually

located

following

the SDF

address list below.

Add results

within

this section,

enter total here

and

in

Section

10

below.

Symbolic

file

table

Section

7

total

XDT

Section

8-Control

information

fordisk

files.

lf resident

open/close

(RESOPN)specified

or more

than

fifty

disk files

or resident

DFF

indexes

(DFFINDX)

specified, skip

to Section 9.

Share DTF

address list

SDF

@

List

Enter

12

x (number

of physical

disk

files).

Also enter value

in Section

10 below.

Section

9-Control information

for user

programs.

Program

character-

istics

table

PCT Enter

6 +

the

number

of sectors of PCT in

$CCPF

lLE, or as a rough

approximation, enter

1.5

x number

of program

statements

rounded

up to the nearest

multiple

of 6. Also enter value in

Section 10 below.

Figure 12 (Part 5 of 61. Storage Requirement3

for Common Code and Control Tables

- 57(t4-SC2 onty

Conf iguration Limitations, Storage

Estimates and Performance

Considerations 195

Details

for

Estimating

Storage

Requirements

Section

1O-CCP

common

code

and

control

table

totals.

Common

code

and

control

table

total

Enter

total

from

Section

t here.

Enter

total

from

Section

2 here,

Enter

total

from

Section

3 here.

Enter

total

from

Section

4

here.

Enter

total

from

Section

5 here.

Enter

total from

Section

6

here.

Enter

total from

Section

7 here.

Enter

total

from Section

8 here.

Enter

total

from

Section

9 here.

lf DFF

is

conf

igured

without

DFF

moved

out.

enter

3g00

here.

Enter

21 for

line

address holder.

Add all

lines

above.

Sum represents

size

of

all

CCp common

code

and control

tables.

lt cannot

exceed

l6K (16,394)

for

any

CCp

conf

iguration.

Figure

12 (Part

6 of 6l' storage

Requirement|

for common

code

and

control rabter

- 6204-sc2

only

196

ccP

Components

I nternal

Terminology Details

for Estimating

Storage Requirements

Section

1-General

Applies

to

all CCP

configurations

Common

code

&

control

tables

Communica-

tion

support

cooe

BSCA

trace

MLTA

trace

Section

1

total

$cc4#2

$CC$BS

$CC$M

L

Enter

the total from

Section 10

of Figure

12

here.

Enter

the

$CC4#2

storage

requirements from

Figure

8

here.

lf TRACEM

LMP may

be

specif ied

at startup

enter

650.

lf TRACEMLTA

may

be specified

at startup enter

1325.

Add results

within

this section; enter total

here and in

Section 3

below.

Section

2-Line

buffers

skip

to Section

3.

for BSCA

communications

lines. lf no BSCALINE

statements in

assiqnment

set.

BSCA

iine

buffers

Refer

to TERMATTR,

BSCALINE

and

BSCATERM

statements

within

assignment

stage.

Calculate

the

size

of

each

line

buffer

as

follows:

1 Enter

(largest

BLKL value used

on each line

rounded

up

to the nearest multiple

o't 256l.

+

42.

2 lf ITB-Y,

TRANSP-N

within

TERMATTR

statement.

enter

t here.

3 lf ITB-Y.

TRANSP-Y

within

TERMATTR

statement.

enter

7

here.

4 lf DBLBUF-YES

within

BSCALINE

statement.

add lines

1,2,

and 3

and enter total here.

5 lf

XMCODE-ASCIlspecified

in

BSCALINE

statement.

add

lines

1, 2,

and

3 and

enter

total here.

Line Number

12

Figure

13 (Part

1 of 61. storage

Requirements

for Resident

ccp - 5704-sc2

only

Conf iguration

Limitations,

Storage

Estimates

and Performance

Considerations 197

ccP

Components

I nternal

Terminology Details

for Estimating

Storage Requirements

Addressing

I isl

Polling

list

Terminal

statistics

tables

Section

2

total

ADDRLIST

POLLLIST

TST

6 lf

TYPE-SW

within

BSCALINE

statement,

enter

number

of

IDEXSEND

characters here.

7 lf

TYPE-SW

within

BSCALINE

statement, enter

number

of IDEXRCV

characters within

BSCATERM

statement

here.

I lf

TYPE-CS

in

BSCALINE

statement

enter

((number

of BSCATERM

statements)

x (number

of

ADDRCHAR

characters

+

3)

+ 1)

for

each line

statement.

I lf

TYPE-CS

in

BSCALINE

statement enter

((number

of POLLLIST

entries)

x (number

of POLLCHAR

characters

+

3)

+ 1)

for

each line

statement.

10 Enter

4 + ((number

of BSCATERM

statements)

x 2

x (number

of POLLCHAR +

7)) for

each line

statement.

11

Add items

1

through 10

above

for

each

BSCA line,

and

enter

totals

here-

Add

totals

of both

BSCA lines.

enter

result

here

and in

Section 3

below.

Section

3-Resident

CCP

sub-total.

Resident

CCP sub-total

Enter

total

from

Section t here.

Enter

total

from

Section 2 here.

Enter

the size of the

TP buffer

from Figure

t here.

Add

the 3 lines

above,

and

round

up

to the next 2K (2,0481

increment.

The

difference

is added

to the

size of TP

buffer. The result

cannot

exceed

48K

(49,152).

Enter

result here.

For

each

optional DFF

buffer

(maximum

of

one

per

BSCA

line),

add

2048 to total above. Enter

here

and

in

Section 12

below.

Figure 1 3 (Part

2 of 61. Storage Roquirements

for Rasident

CCp - 5704-SC2 onlv

ccP

Components

I nternal

Terminology Details

for Estimating

Storage

Requirements

Section

,

specif iec

-Moved out tern

skiP

to Section

5

nal

name

tables.

lf

terminal

name

table MOVEOUT

(MOVTNT)

not

Refer

to MLTATERM,

BSCATERM,

and TERMNAME

statements

within

assignment

set.

Enter

23

+ (11

x number

of TERMNAME

statements).

Enter

11

+ (t

t x number

of SIOC

ports

and BSCA

ports

or

BSCC

ports

specified.

Add results

in

this section;

enter

total

here

and

in

Section 12

below.

Terminal

name

table

TNT

Section

5-Resident

pseudo

OPEN/CLOSE

of disk files. lf resident

open/close

(RESOPN)

not specified,

skip

to Sectiorr

6.

Resident

open/close

$CCROC Resident

pseudo

OPEN-CLOSE requires

10K

(10,240).

Also

enter

value

in Section

12

below. 1O.24O

Section 6-Control

information

within the

external

pointer

list

(EPL).

lf residentopen/close

(RESOPN)

not

specified

and

not

more

than fifty

disk

files

(DISKFILE)

specified and

resident

DFF

indexes

(DFFINDX)

not specified,

skip

to Section

7.

Header

Symbolic

file

table

File

specifica-

tion blocks

Share DTF

address list

Object library

address

table

DFF

indexes

EPL

XDT

FSB

SDF

@

List

EP@OCS

Contains

four

2 byte

pointers.

Calculate

the

size of

one table

for

each SYMFILE

statement.

Each

table

=

$

+

number

of diskf ile

references

within

SYMFILE

statement.

Enter

total for

all SYMFILE statements. The

XDT is

actually

located

following

the

SDF address list below.

Enter

(number

of

SYMFILES)

x ((number

of command terminals)

+

(number

of user

programs

allowed

to run

concurrently)).

Enter

12 x (number

of

physical

disk files).

Contains

all referenced

O codes

and

their cylinder/sector

addresses

that

were

in

the

assignment set.

lf DFFINDX-YES

is specified. enter

6

x (number

of DFF formats

used

).

+8

Figure 13 (Part 3 of 61. Storage Requirements

for Resident

CCp - S704.SC2

onlv

Configuration

Limitations, Storage

Estimates and Performance

Considerations 199

ccP

Components

I nternal

Terminology Details

for Estimating

Storage Requirements

Section

6

total Add

results

within

this section,

and

round

up

to the next

2K (2,0481

increment.

lf result

is

greater

than 4K (4,096).

then

change it

to 4K.

Enter

result here

and in

Section 12

below.

The difference

between

the

space

used fordisk

files

and

the

final

result

is used for DFF

resident

indexes.

However

all of the

format

indbxes

may

not

be in main

storage

even

if DFFINDX-YES

is

specified.

Section

7-Resident

program

request.

rf

resident

program

request

(RESREo)

not

specified,

skip

to Section

8.

Resi

dent

program

req

uest

$CCRPR Resident

program

request

requires

4K (4,096).

Also

enter value

in

Section

12

below 4096

Section

8-Display Format

skip

to Section

9.

facility

MOVEOUT.

tf DFF

MOVEOUT

(MOVDFF)

not

specified,

DFF

MOVEOUT $CC4DF DFF

requires

4K (4,096).

Also

enter value in

Section 12

below. 4096

Section

9-control information

for

BSCC.

rf not

using Bscc (BSCA

rines

3 or 4),

skip

to

Section

i2.

Transient

area

Communica-

tion support

code

BSCC

trace

Addressing

I ist

Polling

list

Terminal

statistics

tabl

es

BSCC

worK

area

T3+

$cc4u0

$CC4#M

$$BSYT

ADDRLIST

POLLLIST

TST

Space

reserved

for BSCC

transients

and BSCC

system

message 2O4g

formattinq.

Enter

the

$CC4#1\4 storage requirements

from Figure

g

here

lf TRACEBSCC

will

be specified

at startup

enter

256 x (1

+

BSCCBLK)

lf TYPE-CS

in BSCALINE

statement,

enter Line Number

((number

of BSCATERM

statements)

x 3 4

(number

of

ADDRCHAR

characters

+

3)

+

1)

for

each

line

statement.

lf TYPE-CS

in BSCALINE

statement,

enter

[(number

of

POLLLIST

entries)

x (number

of POLLCHAR

characters

+

3)

+ 1l for

each

line

statement.

Enter

4 + ((number

of BSCATERM

statements)

x 2

x (number

of POLLCHAR +

7y; for

each .

line

statement.

BSCC

work

area requirements

enter

206 for

each

BSCC

line

used.

Add

totals

of both

BSCC lines.

enter

result

Figure

13 (Part

4 of 6).

200

Storage

Requirements

for Resident

CCp - S7O4-SC2 only

I

ccP

Components

I nternal

Terminology Details

for Estimating

Storage

Requirements

BSCC line

buffers

Section 9

total

Calculate

the size

of each line

buffer as

follows: Line Number

34

1 Enter

(largest

BLKL

value used

on

each

line

rounded

up

to the nearest multiple

of 256)

+

42.

2 lf ITB-Y,

TRANSP.N

within TERMATTR

statement,

enter

t here.

3 lf ITB-Y.

TRANSP-Y

within TERMATTB

statement, enter

7 here.

4 lf

DBLBUF-YES

within BSCALINE state-

ment,

add lines

'l

, 2, and

3 and enter

total

here.

5 lf TYPE-SW

within

BSCALINE statement,

enter number

of IDEXSEND

characters

here.

6 lf TYPE-SW

within

BSCALINE

statement.

enter

number

of IDEXRCV

characters within

BSCATERM

statement

here.

7 Add items

1

through 6 above

for

each

BSCC

line,

and enter

totals here.

Add

buffer

totals of both

BSCC lines.

and enter result.

Add

results

within

this section,

and round up

to

the next 2K 12,O48l

increment.

Enter

result here

and

in

Section 12.

'Sectionl0--Control

informationandsupportforSlOC.

lfSlOCnotspecified,skiptoSectionl2.

Communica"

tion support

code

$cc4#s SIOC requires 4K (4,096).

Also enter value

in Section 12

below. 4096

Section 1

1-Line

buffers fon

SIOC and BSCA

or

BSCC

POBTLINE

communications. lf no

PORTLINE

statement in

assignment

set, skip to

Section 12.

SIOC line

buffer

Refer

to the

PORTLINE

statement

within

assignment set.

Enter

(BLKL

value

used

on

PORTLINE

statement rounded up

to the nearest multiple

of 256)

+

42. Also

enter value

in

Section 12.

Figure 13 (Part 5 of 6). Storage Requirements

for Resident

CCp - 5704-SC2 ontv

Configuration Limitations,

Storage Estimates

and Performance Considerations 201

Details

for Estimating

Storage

Requirements

Section

12-Resident

CCp

totals.

llesident

CCP

total

Enter

resident

CCP

sub-total

from

Section

3 here.

Enter

total

from

Section 4 here.

Enter

total

from

Section

5

here.

Enter

total

from

Section

6 here.

Enter

total

from

Section 7 here.

Enter

total

from

Section

8 here.

Enter

total

from

Section

t here.

Enter

total

from

Section

1

0 here.

Enter

total from

Section 1 t here.

Add

the lines

above.

The

result

represents

the total

main

storage

requirement

of

resident

CCP.

Figure 13 (Part 6 of 6). Storage Requirements

for Resident

CCp - 57O4-SC2

onlv

202

For

any

currently

executing

user

program

using

DFF,

the following

storage

is

appended

to the user

oronrun1.

Program

Appended

Storage

Use

the following

to calculatr.'the

size

of the

terminal

table

and

the format

table.

Enter

37

x (value

of DFFMTERM

within PROGRAM

statement)

Enter

'l

8

x (value

of DFFNDF

within

pROGRAM

statement)

Add 127 + .t27

Add the

three

lines

above,

round

up

to the next

256

bytes

and enter

result

here.

The

rninimum

storage

size

of 256 for these

tables

will contain

enough

space for any

one

of the following

combinations

of terminals

and formats.

1

terminal

+ (1

to 5

formats)

or

2 terminals + (1

to 3 formats)

or

3terminals+lformat

Enter

the

size

specified

for the

field

descriptor

table

(DFFSFDT

within pRoGRAM statement)

rounded

up

to the next

256

byte

multiole.

The

decimal

length

of a

field

descriptor

table

can

be estimated

as 256

bytes for the f

irst

1

to 17

fields

defined

within the DFF format,

and

another

256

bytes for each

18

additional

fields

or

fraction

thereof.

Figure

14. DFF Storage

Requirements

Within the User

proqram

Area

Enter

the

size

of resident

CCP from Figure

1l or Figure

13

here.

Enter

your estimated

requirement

for the size

of the user

program

area here.

Take

into accounr

the DFF storage

requirements

from Figure

14

above. Take

into

account the storage requirements

for memory

resident

overlays

(MORCOR

paramdter

on

system

statement

at assignment).

Also

take

into

account

any

storage required

for use

to external

buffers. Use the value

obtained for

the value

of the

MINUPA parameter

within system

statement

at

assignment.

Add above figures

and enter

result

here. Result

represents

the

partition

size

required

for the

executable

CCP configuration.

Figure

15. Executable

CCP Partition

Size

Requirement

configuration Limitations,

storage

Estimates

and

performance

considerations 2o3

M,AXIMUM

CCP

SYSTEM EXAMPLE

(5704.SC2

ONLYI

This

section

shows

an

example

of a maximum

CCp system

in which

a512K

System/3

Model

15D

with 4 BSC

tines

is

used.

This

example

supports

120

terminals,

i92 files,

and

432

programs,

and it illustrates

how main

storage is

allocated

for

a large

configuration.

FirEure

16 shows

a detailed

listing

of the main

storage

requirements

for

this example.

The

resident

CCp

total

of

94,921

bytes

can

be

achieved

because

as manv routtnes

and buffers

as

possible

have

been

rnapped

out

to other

parts

of main

storage

via

generation

and

assignment

options;

normally,

resident

CCP

code is

limited

to 64K

byres.

As supporting

documentation,

Figure

17 shows

the

genera-

tion options

selected

for

this example

and

Figure

18

shows

the assignment

set.

2011

ccP

Components

lnternal

Terminology Details

for Estimating

Storage Requirement

Section

1-General

Transient

areas

Common

CCP code

Terminal

attribute

set

Section

1

total

T1&T2

$cc4#1

TAS

Space reserved

for CCP

transients.

Enter

$CC4#1 storage requirements.

Enter

5 x (high

ATTR lD

on

the TERMATTR

statement)

Add results

in

this section.

1 536

7

164

20

8720

Section

3-Control

information

for

BSCA

& BSCC

lines

BSCA

line

control

block

BSCC line

control block

Check list

Line totals

Section 3

total

DTF/LCB

DTF/CLB

Enter

137

bytes

for

each

BSCALINE

1 or 2. 137

132

3

272

137

Enter

1

32 bytes

for

each

BSCALI

NE

3 or 4. 132

Enter

3

for

each line

1 & 2.

Add results for

each line.

Add results

in

this section.

3

272

544

Section

S-Control

information

for

terminals

Terminal

unit block

Section

5

total

TUB Enter

39 x (number

of terminals).

Enter

19 x (number

of command

terminals).

Enter

45 x (number

of task-chaining

terminals)

Add results

in

this section.

4680

17

10

231

6621

Section 9-Control information

for user

programs

Program

control

table

PCT Enter

6 +

6 x (number

of PCT

sectors in

$CCPFILE) 462

Figure

16 (Part

1 of 51. Storage Requiremontsfor

Resident

CCp (Example)-5704-SC2

Only

configuration Limitations,

storage Estimates

and Performance

considerations 2os

ccP

Components

Internal

Terminology Details

for Estimating

Storage

Requirement

Section 1O-CCP

common

code

and control

table totals

Common

code

total

Enter

Section

1 total.

Enter

Section

3 total.

Enter

Section

5 total.

Enter

Section

9 total.

Enter

21

for

ADDR. holder

Add

all lines

above.

Cannot exceed

16K

(16,384).

8720

544

662 1

462

21

1 6368

Figure

16 (Part

2 of 51. Storage R€quirom€nts for Resident

CCp

(Examplel-5704-SC2

Onty

ccP

ComponenG

Internal

Terminology Details

for Estimating

Storage Requirement

Section

1-General

Common

code

total

Communica-

tion code

Section

1

total

$cc4#2

Enter

total from

Section

10. 1

6368

1 5678

32046

Enter

the

$CC4#2 storage

requirements.

Add

results

in

this

section.

Section

2-Line buffers for BSCA

lines

BSCA line

buffers

Addressing

I ist

Polling

list

Terminal

statistics

table

Line

totals

Section 2

total

ADDRLIST

POLLLIST

TST

Calculate

the

size of each line

buffer

as

follows:

1 Enter

(largest

BLKL used

on

each linel

+ 42.

Enter

((number

of BSCATERMS)

x (number

of

ADDRCHAR

+

3)

+

1)

for

each line.

2090 2090

211 211

Enter

((number

of POLLLIST

entries)

x (number

of POLLCHAR +

3)

+

1)

for

each tine. 211 211

Enter

4 +

((number

of BSCATERMS)

x

2 x (number

of

POLLCHAR

+

7)) for

each line. 664 664

Add

results for

each

line.

Add

results

in

this section.

3176 3176

6352

Section

3-Resident

CCP sub-total

Resident

ccP

sub-total

Enter

Section

1

total.

Enter

Section

2 total.

Enter

TP

buffer

size,

Add all lines

above.

Round

up

to the next

2K (2,O4gl

increment.

Difference

is added

to the

size of TP

buffer.

Cannot exceed

48K

(49.152).

32046

6352

1

0736

4913r'.

Figure 16 (Part 3 of 51. Storage

Requirements

for Rasidont

CCp (Example)_S704.SC2 Only

configuration Limitations.

storage Estimates

and performance

considerations 2o7

Details

for Estimating

Storage Requirement

Section 4-Moved

out

terminal

name

tables

Terminal

name

table Enter

23

+ (11

x number

TERMNAME

statements)

rounded

up

to next

2K. 2O4g

Section

5-Resident

pseudo

open/close

of disk f

iles

Resident

open/close

Resident

pseudo

open/close

requires

10K

(10,240).

Section

6-Control inf

ormation

within

the

external

pointer

list

Header

Symbolic

file

table

File

speci

ficati

on

blocks

Share DTF

address list

Obiect

I i

brary

address

table

DFF

i ndexes

Section

7

total

SDF@

I ist

EP@OCS

Contains

4 two byte

ptrs.

Enter

9

+ (number

of disk file

ref.

within

each

SyMFILE

statement).

Enter

(#of SYMFILES)

x ((#command

terminals)

+

(#

user

TCBS)) 94s

Enter

12 x (number

of physical

disk

files).

All referenced

O-codes

and

C/S addresses.

Enter

6 x (number

of DFF formats

used).

Add results

in

this

section.

Round

up to

next 2K (2,0481

increment.

Section 7-Resident

program

request

Resident

program

request requires

4K (4,096).

Section

8-Display format

facility

MOVEOUT

DFF

requires

4K (4,096).

Figure 16 (Part

4 of 51. Storage Requirements

for Resident

CCp {Example}-5704-SC2 Only

Details

for Estimating

Storage

Requirement

Section

9-Control

information

for

BSCC

Transient

area

Communica.

tion

support

area

Addressing

I

ist

Polling list

Terminal

sta

ti

sti cs

table

BSCC

work

area

BSCC

line

buffers

Line

totals

Section

10

total

T3&

$cc4u0

$cc4#M

ADD

R

LIST

POLLLIST

TST

Space

reserved

for BSCC

transients

2K (2,O49\.

Enter

the

$CC4+rM storage requirements.

Enter

(number

of BSCATERMS)

x (number

of

ADDRCHAR

+

3)

+

1

for

each line. 211 211

Enter

(number

of POLLLIST

entries)

x (number

of POLLCHAR +

3)

+ 1

for

each

line. 211 Z11|

Enter

4

+

((number

of BSCATERMS)

x 2 x (number

of POLLCHAR +

7)) for

each line. 664 664

Enter

206 for each

line.

Calculate

the

size

of each

BSCC

line

as

follows:

1 Enter

(largest

BLKL used

on

each

linel

+ 42.

Add results

for each

line.

Add results

in this

section.

1322 1322

2614 2614

2121 1

Section

12-Resident

CCP

totals

Resident

CCP total

Enter

resident

CCP

subtotal from

Section

3.

Enter

Section

4 total.

Enter

Section

5 total.

Enter

Section

6 total.

Enter

Section

7

total.

Enter

Section

8 total.

Enter

Section

9 total.

Add

the lines

above.

The result

represents

the

total main

storage

requirement

of resident

CCP.

49134

2048

10240

4096

2121

1

94921

Figure

16 {Part

5 of 5}. Storage

Requirements

for Resident

CCp (Examplel_S7o4_SC2

Only

configuration Limitations,

storage Estimates

and performance

considerations

GENERATION

USED

FOR

A MAXINUM

CCP

SYSTEII

(

57

04-5C2

0NLY)

):x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx*xxxxxx

0 0 010 0 0

0

}i GEN USED FOR A NAXII,IUI,I

SET X

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx*xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

00010000

// cALL

SCGtcl,Rl

,/,,/

RUN$EFAC

ESCAPE-

t,/,/

/

// /

PGI'lCNT-NO,

FORMAT-YES,

pnlltr-vEc

ACCEPT-YE5,

RESOPI{-YES,

B

SYPRT-YE5

,

I.iOVTNT-YE5,

I'IOVDFF-YES,

RESREQ-YE5,

cPUi'i5c-YE5,

TTASK-YES

SEPLG

LANG_COBOL,

PPUNIT-R2

SEPLG

LANG-FORTRAN,

PPUNIT-R2

$EPLG

LANG*A5SEN,

PPUNIT-R2

$EPLG

LANG-RPGII,

PPUI.IIT*R2

qFqtra qtrailotr-^^o

SEFIL

SETS-12,

PROGS_

I O

,

ur r

L l:5-5,

T ERI'IS

_8

,

DUIlPS-I,

c0RE-512K,

FLPACK_F2F2F2,

FLUNIT_F2,

DPTRAC-IO

sEBSC

BSCA-2,

DA_YE5,

LJ_IT>,

GETi'I5G_YES,

RESPOL-YES,

INTPOL

-YES,

EBCDIC.YES,

PORT-YES

$EBSD

TYPE-3275T'11

SEBsD

TYPE-3277I.1I

$EB5D

TYPE-3284il1

$EB5D

TYPE-3236I.11

$EBSD

TYPE_3275T12

$EBsD

TYPE-1277r,12

S

EBsD

TYPE-528qI12

$EBSD

TYPE-5286TI2

A-^.^

9CUJU D)UU-c '

GETNSG-YES,

RECSEP-1E,

IntP0L-YES,

PORT-YE5,

trA'NT'_VtrC

C5-YES

SECSD

TYPE-3275M1

sECSD

TYPE-5277fl1

$ECSD

TYPE*52B4NI

S

ECSD

TYPE_3286111

$ECSD

TYPE-3275II2

SECSD

TYPE_3277I.I2

$

ECS D TYP

E- 3

28 4r'12

$ECSD

TYPE-3285T12

$EGEN

DSUNIT-F1,

CCUNIT-R2,

!^JKUNIT-D.2,

NKPACK_D202D2,

DIUNIT*RI,

I'II NR

E5_NO

CARD-NO

DPPACK-D2D2D2

DPUNIT-02

"

-- NO ./ XIXXXXXXXXXXXXI

-- ESCAPE

I'IODEXOOO4OOO()

-- NO

-- PROGRAN

USE

COUNT XOOOsOOOO

-- NO

_- DFF SUPPORT XO

O 06 O O

O O

_- NO

-- PRUF

SUPPORT XOOOTOOOO

-. NO

_- RESIDENT

INPUT

DATA

HANDLER XOOOSOOOO

-_ NO

_- RESIDENT OPEN

CLOSE XOOOgOOOO

-- IIO

_- BUSY

PRINTER

HANDL]NG XOOlOOOOO

_- NO

-- TNT

I'IOVED

OUT

BY STARTUP XO

O 11O

O O O

-- NO

-- DFF NOD.

MOVED

OUT

BY STARTUP

XOOl2OOOO

-- NO

_- RESIDEIIT

PROGRAI'1

REQUEST XOOlSOOOO

-- N0

-- s TypE

ilsc,s (FOR

5/34 CpU) X00I60000

-- N0

-- TASK-T0-TAsK

SUpp0RT 00180000

-- RPGII

,/ FORTRAN / ASSEr,I

-_ XOOlgOOOO

-- RI / FI / F2 -- 00200000

-- c0B0L,/ RpcII / ASSET'I

-* x00210000

-- Rl / FI / F2

-- 00220000

-* COBOL,/

RPGII / FORTRAN

-- XOO2SOOOO

-- Rl / FI / F2

-- 00240000

-- c0B0L,/ F0RTRAN / ASSEtl

-- x00250000

-- RI ,/ FL

/ F2 -- 00260000

-_ NO./ USER

(REQUIRES

ILUSII PARI'l ) -- OO2TOOOO

-- I - 25 -- HAX

* 0F SETS

0N FILE X00280000

-- I - 999

-- $ 0F PR0GS/SET x00290000

-- 1 - t92 -- * 0F DISK

FILES/SET X00300000

-- 2 - 254

-- $ 0F TERMINALS/SET X00510000

-- 2 - 99 -- * 0F Dut'lp

AREAS

t{ANTED X00320000

-- 96K/128K/160K/t92K/22qK/256K/384K X00530000

-- NAIIE

OF

PACK

--SCCPFILEIS

PACK

NAT4E XO()S4COOO

-- RI / FI / R2

--SCCPFILEIS

UNIT NAIIE XOO35OOOO

-.- S OF

TRACE AREA

TRACKS

-_O*2--*OFBSCALINES

-- NO

-_ DISPLAY ADAPTER

SUPPORT

-- NO

_- BSCA CONTROL

STATION

SUPPORT

-- NO

-- GET A f'IESSAGE

-- TI.IO HEX

DIGITS -- RECORD

SEPARATER

-- NO

_- RESIDENT

BSCA POLLING

-- NO

*- INTERVAL

POL L ING

-- NO

_- EBCDIC

TRANST'IISSION

CODE

_- NO

_- BsCC

CONTROL

sTATION

SUPPORI

-- SEE

SYSTEl.l

REFERENCE

Mr\NUAL

--

-- 5EE

SYSTEN

REFERENCE

NANUAL

--

-- SEE

SYsTEN

REFERENCE

NANUAL

-_

-_ SEE

SYsTEN

REFERENCE

IlANUAL.-

*- SEE

SYSTEII

REFERENCE

NANUAL

--

-- SEE

SYSTEIl

REFERENCE

I'lANUAL

--

T- SEE SYSTEH

REFERENCE

I'iANUAL

--

-- SEE

SYsTET-I

REFERENCE

NANUAL

_-

-- R1

_- IPL UNIT

-- R1

/ FL / F2 _-EXECUTION

UNIT

-- TUNIT,UNIT,UNIT'

--UNIT F0R

t^t0RK

-- IPACK,PACK,PACKI

--PACKNAIIE

FOR I^JRK

-- FL / R? / F2 -- CCP PID

-- TlINII'1UM

RESIDENT

CODE

OPTION

-- YE5

--CARDLESS

CCP

GENERATION

-- $CCPDUI1P

FILEIS PACK

NANE

-- SCCPDUI'1P

FILEIS UNIT

NO

_- EBCDIC TRANSI'lI5SION

CODE

NO

-- BSCA PORTLINE

SUPPORT OO52OOOO

SEE

SYSTEN

REFERENCE

MAI{UAL

_- OO53OOOO

5EE

SYSTEI'I

REFERENCE I'lANUAL

_- OO54OOOO

SEE

SYSTEI'I

REFERENCE

I'IANUAL

-- OO55OOOO

SEE

SYSTEI.l

REFERENCE

NA}IUAL

-_

5EE

SYSTET'I REFERENCE

I.'IANUAL._ OO5TOOOO

SEE

SYSTEN REFERENCE

T,IANUAL

-_ OO53OOOO

SEE SYsTEI.I

REFERENCE

MANUAL

-_ OO5gCOOO

SEE

SYSTEM

REFERENCE I'lANUAL

_* OO6OOOOO

0 - 2 --* 0F BSCC

LINES X006q0000

NO

-- GET A MESSAGE X()O65OOOO

Tl,^10

HEX

DIGITS --REC0RD

SEPARAT0R X00670000

NTJ

-- INIERVAL POLLING XOOTIOOOC

NO

_- BSCC

PORTLINE

SUPPORT XOOT2OOOO

00740000

00750000

00760000

00770000

00790000

00600000

00810000

00820000

x00860000

x00870000

x00880000

x00890000

x00900000

x00920000

x00570000

x00J80000

x00420000

x00430000

x00q50000

x0c490000

x00500000

Figure 17" CCP Generation Listing Ussd for Example-5704-SC2 Onty

210

I EXANPLE. A55IGIIFNT SEI LI5]ING OF A ilAXIilUi CCP

SYSTET

/, 5EI TD T,ACIIOX-REPIACE

// SYSIEN

ilINUPA-60K,il!NTPBUF

IOOOO,PCilREQL*79,COBrANDL-60.

DA T A

FORN-TESSAGI

ilAXC

HA

I N.5, PO

! T ITE-NO

,

PASSIORD-SHAL

OT,

DF FPAC

K.PROGRAM

// TERXAT]R

A ITRID-OI,

IRAN5LAT-YE5,

UPCA5E-Y€S,

5IITCHED-NO,

BIKT.2O46,

DATAFORtr

ilESSACE,

DFF]270-YE5

// TERNATTR

ATTRID.O?,

TRAN5LAT-YE5,

UPCASE-YE5,

5!ITCHED-NO,BLXL.I

/9?,

// DAIAFART-NESSACE,DFF]270-NO

// TERflATIR

A:TRID.OJ,TRAISLAT-YES,UPCASE.YE5,SLKL.128O,

DATAFORil-iES5AGE,

DFF]27

O

-YES

// TERNATTR

ATIRID.Oq,TRAN5LAT-YE5,UPCA5E_YES,8LKL-EI7,

// BSCALINE TYPE-.C5,LINENUX.I,

// POLLLISI,IAO,AI,A2,A],A4,A5,A6,A7,AE,A9

80,BLB?,85,84,85,86,87,SA,89,

c0,cl,c2,cl,c(,c5,c6,C7,CE,C9i

// BSCATERX

TTRHID-AO

// BSCATERi TERMID

C4.

I)PE-i277I2,ATTRID.' I, 2" ONLINE.NO,COilTAND-YE5,

A

DDRCHAR-

I6 06 0 C

0

q

0

x

,

po

L t cSAR_*4

04

0

q

0 4

o

x

// BSCATERF

TERtsTD-AI,

// ADDRCHAR_r6060CICIr,pOLLCNAR-r(040C1c1*

// BSCATERI

TERMID-A2,

IYPE-lZ?7H2,ArTRID-'

1,2" 0NLINE_NO,

CotnaND_yE5,

// aDDRCHAR_*606oC2C2r,p0LtcHAR_x(0q0c2c2x

// BSCATERF

TERIID.AJ,

IYP

8.52 7 7ff2,

AT TR

ID- '

1

,2 I ,

OilL

I NE-NO,

COMilAND-YE5,

ADDRCNAR*r

6 0 6 0

C7C7

r ,

p0

L L cHAR_r4

0 4

0 C 7C7

r

// BSCATERM

T€RHID-A8,

TYP

E- 32 7 7MZ,

ATTR

I D.' 1

,2 ' , ONL

I NE-NO,

COHilAND.YES,

// ADDRCBAR-r606OC(C4r,

poLLcfaR-x4040(:4c4*

// BSCATERT

IERil]D-A5,

ADDRCHAR-*6060CACEx,

p0LLcNAR-xq040cacar

// BSCATERfr IERTID-A9,

// BSCAT€RF

TERfrID-89

// aDDRCHAR-r6060C1c5*,poLLcHAR-x4040CJClx

// ESCATERi

IERNID-AI,

rYPE-J277T2,

ATTRID.'

I, 2

"0!LINE-NO,

CONtrAND.YES,

IYPE-J277ff?,AITRID-

I

t, 2I, ONLINE-NO,

COfiTAND-YES.

TYPE-I277I2,

ATTRID-I

I, 2

I,ONtIilE-NO,

COilMAND-Y85,

TYP

E.]27 7fr2,

ATTR

I D-

I

I ,2' ,

ONI

INE-NO,

COTMAND-YES,

/t ADDRCHAR_x5060DlDlr,p0LLcHAR_xC0(ODlDtx

// 85CATERi TERTID.BI,

// t\pE-1?77ilz,AtTRtD-'l,2,,oNLINE_N0,COililAtD_yES,

// ADDRCHAR-X6O6OD2D2i,POLTCHAR-14O(OD2D2X

// BSCATERN

IERflID.B2,

TYPE-J27

782, AT TR

I D-

I

I ,2

"

ONT

I NE-NO,

COr[ATD.YE5,

A

DDRCHAR-I6

O6 ODJD]X,

POL

I CHAR.rq

O

qOD]D]I

// BSCATERi TERTID.BJ,

rYPE-J277T2,ATTRID.'

I,2" ON!INE-NO,

COdilAND-YE5,

ADDRCHAR_r6060c9c9i,

p0LtcNAR_i4040c9c9r

-// BSCATERT

T€RHID-EO,

IYPE.]277T2,ATTRID-I

I,2

"ONLIXE-NO,

GOfiilAXD-Y€S,

TYPE-J?77H2,AITRID-'

I, 2" ONLINE-NO,

COiFAND-YES,

// ADDRChAR-*6060DqD4I,pOtLCHAR_r4oq0D{04*

// BSCATERT

TERIID.B4.

// BSCATERX

TERXID.B5

TYPE']277M2,ATIRID.I

I,2I, ONLIdE.NO, I)OilXAND-YES,

ADDRCHAR.T5

O5 OD'D9I, PO L

L CHAR-X4 O 4O

D9D9I

TYP

E-327 7

N?, ATTRI

D-

'

I ,2 ' ,

ONt

I NE-TO,

:OflMAND-YE5,

A DDRCflAR-I6

O5 O

D6D6

X

, POL TCHAR-r{O4OD5

D6

r

// SSCATERT

TERilID-85

// ADDRCHAR-x6060D7D7r,p01!cHAR-i(040DZD7r

// BSCATERT

TERMID-87,

TYPE-]277H?,ATTRID-

I

I, 2I,OilLINE,NO,COililAND-YE5,

// aDDRCHAR-x6060D8Dax,poLLcHAR_r{04006D6r

// BSCATERil TERfrID-86,

// ADDRCNAR-T6O6OE2E2X,POLLCHAR-r4OqOE2E2I

// BSCATERH

TEFIID.CO,

// flpE-3277ilz,ATrRID-'l,2"0rLrNE-NO,CoXiAilD-yES,

// aDoRcBAR-x6060E3€Sx,potLcHAR_r4040EJE5r

// BSCATERF

]ERilID-CI,

// ADDRCHAR-X6O6OE(E4X,POLLCHAR.XqO(OE{E4t

// ESCATERi

TERNID-C2,

rYP

€_ 3266il2,

ATTR

I O-

I

I , Z' ,

ON

! IIE-NO, COiMAND-HO,

ADDRCHAR-x6

0 6 0 E5E5x,

pot L cHAR-rq

04

o €5E5r

// 8SCATERT

IERilID-C],

TYP€']266il2, AI

IR I D

-' I ,2 I ,

ONL

IIE-NO, COTNAND-XO,

ADDRCHAR-I6

O

6

O E6 E6

T

, POT

L CHAR-Xq

O {

O €6 E5

X

TYPE-3286T2,

ATTRI

D-

' I ,2 I

, ONL

I

TE-NO,

(:OililAHD-NO,

// ADDRCHAR*I6O6OETETX,POLLCHAR-X4O4OE7E7X

// BSCAIERil TERTID.C5,

TYPE-32A6H2,ATIRID-

I

I,2I, ONLIHE-NO,COfrTAND-TO,

// ADDRCHAR.T5O6OEEEAT,PO!LC8AR..i4OqOEAE6X

// BSCATERi TERMID-C6.

Figure 18 (Part 1 of gl. CCp Assignment

Sst Lisring for Example_5704-SC2 Only

-// BSCATERB

TERfrID-C7,

// TYPE-3266NZ,ATTRID-'I,Z"ONLINE-NO,COTilAHD-IO,

,/ ADDRCHAR.T6O6OFIFIX,POLLCHAR.T4OqOFIFIX

// BSCATERil T€RfrID.CE,

// TYPE-]286N2,ATTRID.'1,2I,ONLIN€-NO,COIilAND.NO,

ADDRCHAR-X6

O6 O F2F2T,

POL

LCHAR-X4

Oq

O

F2F2I

-// SSCATERil

TERilID-C9,

-// IYPE,JzE5T2,ATTRID-I1,2I,ONIINE-NO,COXilAND_NO,

aDDRCSAR-x6060FJFl*,

potLcraR-x4o4oF3Flr

// 85CATERil TERilID-fO

TYPq-327?M2,ATrRID-.'

l, 2

T,oNLINE-NO,C0HTAND_yE5

AD0RCHAR- x

6 06 04

04 0

t ,

p0L

LcHAR_r

q

0 4

0

q

0

(

0

\

// SSCA]ERN TERMID-HI,

IYPE-3277il2,

ATTRID-

I

1,

2i, ONLIIE-NO,

CONilAND-YE5

A!DRCNAR-{6060ClCl},p0LLcHAR

t40{Oc1cl*

// BSCATERM

TERfrID-h?,

// BSCATERN

TERTIID,IJ

IYPE-3?77S?,ATTRID-

I

1 2i, ONLINE-80,

COilffAND.YF5

aDDRCHAR-

r

6 0 6 0 CICJr ,

p0

L

L cHAR,

r

4 o 4

o C 5Cl*

// BSCAIERM

TERIID.B4,

TYPE.IZ77ts2,

AITRID-'

I, 2

I,ONLINE-NO,COilM4ND.YES.

ADDRCf

AR r6060C{C4*,p0LLCHAR-r{O40CcC(l

// ESCATERT

T€RflID-H5.

TYPE-]277H2,

AIIRID-' I, ?I,ONLINE.NO,COMilAND-Y[5

a DDRCHAR-

i 6 06 0C5C5

x

,

p

0

L t cHAR-i4 04 0c5c5x

// !SCATERT TERfrID*H6,

TYPE.]?77il?.

A]TRID-'

1, 2

"ONI

INE,NO,CONflAND-YES,

ADDRCHAR

*6060C6C6*,p0LLCHAR_t4040C6C6r

// BSCATERN

TERIlID-H7,

IYP

E-

J 27 7fr2, AITR

I D-

I

I , ?' ,

ONL

II E-NO, COhMAND.YE5,

// A0DRCHAR-r6060C7C7r,poLLCdAR_xq040c7c7*

// BSCA]ERM

TERflID-H6,

IYPE-]277il2,ATIRID-i

I, ?I, ONLINE-NO,COMHAND-YE5,

// ADDRCHAR-i6060C6CEi,poLtcHAR-x4oq0c8ca*

// O5CATERT ] ERTID.H9,

// BSCATERts

T:RflID-IO

// ADDRCHAR-I6O6OD1D1',POLLCHAR

X4OC!DIDIi

// B5CA]ERil TERIID-I1,

TYPE.]2}7fr?,ATIRID.'

T,

2', ONLINE_NO,

COiilAND-YES.

ADDRCHAR

T6O6ODZD2X,POLLCHAR-r(O4OD2D2i

// BSCATERil TERflID-I2,

IYP€-]277fl2, ATTRID-

I

1, 2

I,ONLIilE.NO,COiltsAND,YE5

ADDRCSAR-

*6

O6 O D]D]I, POL

L CHAR-I

(

O 4

O D5D3}

// ESCATERT TER[ID-I],

TYPE-]277i?,

ATTRiD-'

I, 2I, ONLINE-NO,

COililAND-YE5,

ADDRChAR.X6O6ODqD4X,

POLLCHAR_XqOqODtD4r

// SSCATERM TERilID_Iq,

rYPE-J277fl2, ATIRID i

I, 2

"ONLIN€-NO,COiliAHD-YE5

// ADDRCHAR-*6O6OD5D5},POLLCHAR.ICO4OD5D5i

// BSCATERtr TERMID.I5,

// BSCATERII

IERilID-I7,

TYPE_I277H2, ATTRID-'

1, 2I, ONLINE.NO,

COS(AND-YES

// ADDRCfrAR-x6060D8D6x,p0LtCBAR-r40q006D6*

// BSCATERi T€RXID-IE,

TYPE-J277il2, ATTRID-'

], 2

"

ONLIilE-NO,

COTTATD-YE5,

// ADDRCHAR-X6O6OD9D9*,POLLCHAR.I4O4OD9D9I

// SSCATERI TERTID-I9.

IYP E-J27 7frz, AT iRI D-

I

I ,

2

I

,

ONL

IN E-NO, COfriAND.YE5,

// ADDRCHAR-r6060E2E2x,p0tLC8aR-i{o4oE2E2x

// B5CAIERT IERiID.JO,

rYP€.327 /M2,

AITRIO-'

I, ZI, ONLINE-NO,COMXAND,YE5,

TYPE.]2E6ilz,ATTRID.I

t,2',OTLIIE.NO, COTNAND-NO,

// ADDRCXAR-i6O6OE5E5T,POLLCHAR-X4!4OE5E5X

// BSCAIERil

IERXID.J],

ADDRCflAR

-

{6 O6 O E] E]X, PO

L L CHAR-}4 O4 O

EJ E ]X

// ESCATERil TERXID-JI,

// TYPE-5277fr2,ATTRID-II,2I,ONTIN€-NO,COililAilD-YES

// ADDRCHAR-T6O6OE4E{T,POLLCHAR-T4O4OE(E4X

// BSCATERN TERilID-J2,

// BSCATERil IERhID-J4

// ADDRCHAR-I6C6OETETT,POLLCBAR-I(OqOE7E7I

// BSCATERM TERiID.J5,

TYPE-]286X2,

AITRID.

I

I, 2

I,ONIIHE-NO,COililAND-NO,

ADDRCHAR-

I6 O5 O E6 E6

i ,

POL

L CHAR.X( O 4

O E6 E5I

TYPE-J2E6N2,

ATTRID-'

1,

2

I,

ONLINE-NO, COTilAND-NO,

ADDRCHAR.X6

O

6

O E9E9X

,

PO L L CHAR-*4

Oq O E9E9X

TYPE*]2A6ilz,AT]RID-I

I, 2I,ONLINE.NO,COMilAND-NO

ADDRCHAR-I6

! 6 O F3 F]

T

, PO L L CHAR-

I

(

O { O F] F]X

// BSCATERts TERilID-JA,

// ADDRCHAR-T6O6OF2F2X,POLLCHAR.T4O4OFZF2X

// B5CATERfr TERIID-J9,

// BSCALINE

TYPE-CS,LINENUM']

configuration Limitations,

storage Estimates

and performance

considerations 211

// BSCATER[

T€RXID.ilO,

// \\?E-3277il2,ArTRID-'J,{l,oNLt!E_N0,CorilAND_yES,

// ADDRCBAR-r6060q0q0r,po!Lc8AR_r4040(0(Or

// I5CATERil TERdID-ilI,

TYPE-t277fr2,

ATTRID-'

1,4

" 0NL Iila-NO,C0rf

ArD-yEs,

--// AoDRChAR-x6060ClcIr,p0LLcHAR_)4040ClClr

// ESCATERN

TERIID-ilz,

IYPE.

]277il2,ATIRID.I

!, q

"ONLINE-NO,

COililAID.YES,

// ACDRCHAR-x6060C2C2r,p0LLCNAR_lq0(0c2c2x

// SSCATERn

TERftD-ilt,

IYPE-5277fr?,

ATTnID-'

J,

(

"OtLtf L-ho,

c0nrarD-yE5

-.// aDDRChAR-r6060Clctr,p0LLc8aR-rt04oc3c3x

..// ESCATERIl

I€RiID,fr4,

TYP€-127r[2,

ATTRID-'!,4'.0N1

IN€-t0,

C0iilatD-yEs,

// aDDRCSAR-r6060C4C4r,p0LLCBAR-r40q0c(c4r

// I3CATEIi TERillD-I!',

TYPE.J277h2,

ATTRID-'

3I 4

I' ONLINE-NO,COTiAXD'Y83,

// AD}NCXAR-r6050C5C!r,pOLLCHlR-r404oc!crr

// ISCATERil'ERilID-I'16,

rYPE-Jr77H2,

ATTRI0-'!,

{

l,otLltE-H0,

coltHAt0_yEs,

// IDDRCNai-r6060c6c6r,poLLcxAR-r(0{oc6c6r

// ISCAT€Ri

TERMID.hT,

TypE-J277i?,

ATTttD-' !, 4

l,0xLIXE_NO,

Coif,AND_yES

// ADDRCNAR-r6060C7C7r,p0LLc8AR_:(04!C7C7r

// t3cAtEflrl

TgRilI0-i6,

rYPE-t277[2,

IlTRID-.

],( i,

0tLtnE-xo,co[MANo_yES,

// aDD?CAAR-x6060CtCEr,pOLLCHAR-rq0(0C!cEr

// BSCAT€RT

]ERiID-N9,

I

YP

E-127 7f,2,

ATTR

I D

- '

l,

{

|,

CnL It

E-to,

coiiarD_yE5,

ADDRCX

AR-r6

06 0 C9C9r

,

p0t

L

cHAR-

r4

o( 0 c 9c

9f

// ISC TEIil TERilID.XO,

// TypE-r277F2,ATTRtD_'!,{|,ONLINE-NO,COdiAHD_ye9,

// ADDRCHAR.T5O6ODIDIX,POLLCHAR-I(O{ODtDlr

// ISCATENT

IERilID.N1,

TYPE-3277h2,

ATTiID-'

!,

("0tLtxt-N0, coilrAtD-y85,

IDDRCHAR- r6

0

6 0 D2D2r

,

p0L

i cHtR-

r

4

o

4

0 D2D2

|

// BSCAIERi

TERMID.T2,

TYPE-3277f

2' AITRID-,

5, {

i,0ttIrE-NO,C0frxAND-yEs,

ADDRCHAR-r6

06 0D!

DJr,

p0t

L cSAR-

x

4 04

oolDSr

lYP€-l277fr2,AlTRID-' l, 4|, 0xLINE-N0,CoiilAND_yES,

// ADDRCHAR.T6O5OD(D9I,POLLCNAR.T4O4OD4D4I

// BSCA]ERi TERffID.I4,

// ISCITEIi TERNID.NS,

// BSCATERil

]ERfrID.N6,

TYPE.JZ77T2,

ATTRID-'

], (" OITINE.RO,

COiNAHD_Y€S,

ADDRCHAR.X6O6OD6D5I,POLIChAR.TIOIOD6D6I

TYPE.J277i2,ATTRID.I

J, {

I,

ONLINE.NO,

COfrilAXD-YES,

ADDRCHAR-X6

O6 OD6DE

I, POT

L CHAR-

I{ O

4

O DED6

i

// SSCATERI IERMID-NA,

// 1YPE.3277H2,ATTRID.'3,{"ONLIflE.IO,CONTAND.YE5,

// ADDRCSAR.'5O5OD9D9X,POLLCXAR-rqO4OD9D9I

// ESCATERi TERflID-N9,

rYPE.J277T2,

ATTRID-I

J,

q

I,

CNIIXE-NO,

COiliAND-YES,

// ADDRCSAR-I6O6ODTDTT,POLLCIAR_X4O4OD7D7r

// BSCATERT

TERBID.NT,

TYPE-]277T2,

ATTRID-'

]I4 I' ONIIN:-NO,COXMAXD-YES,

// ADDRCHAR-I6O6OE2E2X,POLLCHAR.X4O4OE2E2I

// BSCATERN

TERiID-OO,

TYP

E- ]27 7il2,

ATT RI

D-

'

! ,4 I

, ONL

IN E-NO, COilFAND.YE5

rYPE.3277X2,

A'IRID- I

3,qI, ONL INE.fO,COHNANO.YES

// aDDRCHAR-x5060E5€5x,p0LLcflaR-r{o(085€5x

-// BSCATERT TERilID-05,

// ADDRCHAR-X6O5OEJESI,POLLCHAR-'IiO4OE5E]X

-// SSCATERh TERTID.OI,

// IYPE-5277N2,ATTRIO-I],4"OXLINE-NO,COflfrAND-YES,

// ADDRCNAR-X5O6OE4E4T,POLLC8AR-X,iOqOE4E4r

// BSCATERM

TERilID-02,

TYP

E-5266tr2, ATlRt

D-

'

!,4 ', 0iL

I

N

E-N0,

COXTAND-X0 .

// ADDRCNAR-r6060E6€6r,p0LtcB4R-f4o40E6E6r

// BSCATERi T€RMID.O4,

// I\PE-52E6trz,AITRID-'],(I,ONLINIi.NO,COilMAND.NC,

// AD0RCsAR-r6060E7E7r,p0LLCraR-x4040E7E7r

// BSCAIERfl

T€RT]D.05,

// TYPE,1266fr2,A]TRID-'],4i,ONLINE-NO,COfliAND-rO,

// ADDRCHAR-I5O6OE6E6X,POLLCHAR-I4O(OEEEET

// 85CAIqRts ]EPilID-06,

TYPE'

3266i?, ATIRID-

I

], 4

"

ONL IHi:- IO, COitrAXD-NO,

// ADDRCIAR-r6O6OE9E9r,POLLCHAR.r4O4OE9E9i

// DSCATERil TERffID-07,

// IYPE-J266il2,AITRID.'5,4I,OTLINE.TO,COMilANO-NO

// ADDRCHAR.I6O6OFIFI*,POLLCHAR.I4O4OFIFIi

// ESCATERfi

TERTID.OE,

TYPE-]286f,

2, ATTRID-

I

], 4

I,OTLIfl

E-NO, CONilAXD.NO,

/ / A

D D R C N A R

. r 6 O 6 O

F

2 F

2 r , P O L L C

H A

R

- X

( O

F

2 F

2 X

// BSCATERff

IERXID-09,

TYFE J:66M2,ATTRID-'

],4I,OTLINE-NO,COIflAND.NO

A0DRCHAR*r6

06 0Fl Flr, p0L

LcHIR-r(

o(

oFtf 3r

,,/ S5CALiHE TYPE-CS,LINEN!T,4,

,/ / P

O L L L i 1' T

. ' T O

, T ! , T

? , T 3 , T J , T

5 , T

6 , T 7 , ] 8 , 1 9 ,

,,/ UO,UI,U2,U3,U(,U5,U6,U7,UE,U9,

,t / v a , v L

, v 2 , v L v 4 , v 5 , v

6 , v 7 , v

E , v 9 '

// ESCATER! IERilID-IO,

,./ \YP'-3277il2,ATTRID.'],'"CNLIN€-ilO,COilrAND.YE5,

,, / A

D D R C N A

R

- r 6 0 6 0 q 0 ( 0 r , p 0 L L

c il a R

- | q 0 4 0 q 0 q o I

,// BSCAIERi ]ERfrID-II,

,,/ I\PE-3?77T',ATTRID-'3,4i,ONIINE-NO,COililAND.YES,

r' / A

D

D F

C

H A

R

- r 6 0 6 0 C

I C 1

x , p 0 L L C I A

R

- i q 0 4 o c I c I r

Figure

1

8 (Part

2 of 81. ccP Assignment

s€t Listing

for Exampre-s704-sc2

onry

212

// ADDRCNAR-i6060cJclx,pcLLcHAR_r4C40CtCJi

// 85CAT€RM

TERIIID.T(,

// 11pa-3277il2,ATTRID_'J,(|,ONLtrE_N0,cofiAN0-y!s,

// ADDRCfAR_r6060c5ctr..p0LLcfAR-r(0qoc5c5r

// SSCATERil

T€R[ID-T6,

// gSCATERE

TERNID.TT,

rYPE-

J277r?,

AliRID-' l, q

"

!N!

M_NO, CoXTAND-yEg,

// aDDRatAR-x6060c7c7i,p0LLcNAR-r(Oq0C7C7x

// BSCATERil

TERTID-T8,

rYPE-t277f2,ATrFI0-'

!,c

"0NtlNE_NO,

COnilArD-yE5,

// AoDFC8AR,i6060CEC8t,p0tLCNAR_r(040C!C6r

// BSCATEqT

TEAIJID.T9,

TYlt-J?77r2,ATTRID-'3.

4'.

0NLr!E-to,coi[AND-yE5,

TYPE-J277I2,

ATTRID-

I

3,

4

"

O!LINF-IO,COilIAND.YES

A

DDRCHA R

-

i 6 0 6 0 C6

C 6

r ,

p

0 L L c

tAR-

i 4

0 { 0 c6 c6

r

TYPE-t277f2,ATTRID-'l,4

"oNt1tE-N0,CoiltAND-\e5

ADDRCHAR-I6O6ODID:

t,POI

LCHAR-!40(ODIDIi

// aDDNCHAR-r6060C9car,p0tLcraR-r(0qoc9ctr

// 85CAIERil

TERilID.UO,

// ESCAI€Ril TERMID.UII

TYPE-!277il?,

ATTRID-'

t,

q,,

0NLlrt-N0,

c0iilaND-yEs

aDDRCSAE-r5060D2D2r,

p0t

!Cf

AR

-r4040D?!:l

// ESCATtRm

rtRfID-U?,

IYPF-J277frz,

ATTRID-'

]. 4

i, ONt INE.NO, COflTAND.Y€S,

AD0RCHAR- r

6 0 6 0 D5D!

r ,

P0

L L CNAR-

r

a

0

4

0 D JD I

t

// !5CATERil ]ERilID.UJ,

// IYPe-a277iZ,ATTR1D-'l,4"ONtItE.N0,C0ifiAND-yE5,

// ADDRCHAR-x60600(D4x.p0LlcBAn-t40(cuqD(r

// 83CATIRE TERhIO-U4,

TYPE-J277M2,

ATIRID.'

], 4

"OIL

INE-IO,

COFXAiD.YTS,

a DDRCHAR-r

6 0 6 0

0505

r ,

po

L L

cHAS

-

|

4

0

i,0

D! D5

x

// SSCAIERfr TERfrID.U',

// t1?E-327712,ATTRID-'5,r"0NLlXE-N0,COililAND-ytS,

/ / A D

D R C B A R

- | 6 0 6 0 D 5 D 6 x , p 0 L L C I I R

- ' 4 0 q C

0 6 D 6 r

// BSCATERfr

TERiID.U6,

// r\pE-t277fi2,ArTRID-'J,("ONLtt€_NO,COIilND_yES,

// ADDRCHAR-r6060D7D7r,pCL!CfAR-r(0q0DrD7r

// t!caTERi TEiftD-!7,

// fY?E.3277N2,ATTRID.'],4i,OILINE-NO,COfiIAflD.Y€S,

// IDDRCfAR-r6060D6D6r,p0LLCHAR-x4040DED6i

// E5CATTRi

TENfiID-!6,

/ / A D

D R C I A R - | 6 0 6 0 E

7 E 7 r , p 0 | i c ! A

R

. | ( 0 4 c E

7 E

/ r

7/ 85CAT€Ri TERilID-V5,

// 1\?E'328612,ArrRID-'l,4i,0tLINt-rc,confAND_N0,

// ADDRCHAR-r6060E8E6r,p0LLCfAR-i4040EEE6r

// ESCATERI

TERXID-V6,

// IYPE.32E5il2,ATTRID-'3,("ONLlNE-NO,COXilAilD.IO,

// ADDRCTAR-r606CE9Eti,p0LtCNAR-r(04CE9iti

// ESCATERI TERTID.V',

// 1\PE-326{fiz,ATTRID-'l,4"0NLir[-tO,CoilMAND-N0,

-// ADDRCSAR-x6060FiFlx,p0LLcfAR-r4!4CFlFli

// BSCATERtr IERIID-VE,

IYPE-327712,

ATTRID-'

l. 4

"ONL

tHE-N0, C0nMAtD-yE5

// AD0RCNAR-r6060D9D9!,p0LLC8AR

t40qOD9D9x

// DSCAIERM TERHID-U9,

TYPE.J27

7fl

2, ATTRID-'

J,

(

"

ONLINE,NO,

COItsAND.YE5,

// ADDRCHAR,T6O6OE2E?T,POLLCHAR.'40(OE?E2I

// 85CATERil IERiTD-VO,

TYPE-]277T2,

AIiRID.' J,

q

"

ONL

INE_N!, COEIA8D.YE5,

4DORCHAR-i6O6OEJE]*,

POLLCHAR.

X4O(OE:E1r

/ / A D D R C H A R

- ! 6 O 6 O E 4 E

< * , P O L L C H A R

- r ( O

( C E

4 E

( I

// BSCA]ERI IERNID.V2,

IYPE.J286fr2,

AI]RID.' J, 4

"

CNL INE.NC,

COTIAID-NO

ADDRCIAR-T6O6OE6E6I,

POLLCHAR.T(OqEE6E6i

TYPE-]?66X2, ATTRID-'

], 4

"

OII INE_NO,

COhfl AID-NO

// aDDRCIAR-r606!F2F2r,p0LLCHAR-x4C(OF2F?x

// B5CAIERil

I€RXID-V9,

// rypE-32E6fi2,AITRID-'J,4"0NLltE-NO,CorilAND-N0,

ADDRCHAR-r6

0 6

0

F

I

FJ

' ,

p0

!

L

CSAR-

r4

0

q

0

F

3

Fl i

// TERiTATE NAME.TERTIO,

TERHID-AO

// TERMNAfrE

NAilE-TERTAI, IERilID-A1

// TERilNA[€ NAfrE-TERilA2,I€RH]D-A2

// TIRhXAilE NAilE-TERNA], IERilID.A]

// IERfrilANE

dAhE-T€RMA4,T€RilID-A4

// TERXilAiE NAXE-TERtsA5,TERTID-A5

// IERN\ANE NAXE-TERNA6

,

TERTID-A6

// TERMNAilE

NAfrE.TERNA7,

]ERTID.A7

// TERfrNAiE NAilE-TERTA8,

TERilID,AA

// T€RNXAiE NAHE-T€RTA9I

IERXID-A9

// T€RiNAil' NAXE-T€RT8O,

TERTID.BO

// TERXNAHE NATE-T6RNBI,TERilID-BI

// TERiNAiE NAff

E-IERil82, TERiID-BZ

// TERilNAtsE

NAilE.TERNE],

TERfl

ID.B3

// TERiNAtsE

NAiE.TERfrB(,IERiID-B(

// TERfrTAi€ NAHE-TERfiBS,IERiID-85

// IERilNATE NANE.iERME6,iERI1D.86

// TERilNAilE NAHE-TERXBT,TERiID-87

// TERNff Ai! NAiE-TERM86,

IERhID-88

// T€RXhATE

NIilE-T5Ri!9,TERNID-89

// TERilIAiE NAfrE.TTRiCO,TERfrID-CO

// TERhNAX€

XAilE-IERHCI,TERN]0.C1

// TERf,NAME

NAilE-IERhC2,TERXID-C2

// TERNNAilE

ilAilE.TERflC3,IERTID-C]

// TERilNAfrE

NAilE-TERiC4,TERiID_Cq

// TERflNAiE NATE-TERNC5,TERiID-C5

// TERffNAME

NATE-TERilC6,IERfrID-C6

// TERTNAffE

NAXE-TERiCT,IERMID.CT

// T€RilIATE IAilE.TERilC8,TERHID-CE

// TERHNATE

NAXE-TERNCg,TERilID-C9

// TERHNAtrE

NAN€,]ERilHO,TERiID-HO

// IERilHAil€ NAilE-IERHHI,TERfrID.XI

// TERiNAME

NANE-]ERTH2,TERFIO.H2

// TERNIAilE NAilE.IERflNJ,TERTID.HJ

// IERiflANE TAflE-]ERilH4,TERXID-H4

// TERilNAilE

NATE.TERilH3,]ERHID.H5

// TERilNAfrE

NAfrE.IERNH6,TERdID-H6

// TERTNAHE

NANE-TERilHT,IERMID-H7

// TERilNAXE

{AilE-TERilHE,T€RiID-H6

// TERiNAflE TAfrE.TERilH9.]ERilIO-H9

// TERfrNAilE

TANE-TERIIO,TERXID-IO

// TERTNAXE

NAhE.TERiII, TERilID.II

// TERidAHE NAi€-IERdI2,TERflID I2

// IERNNAME

NAilE.TERMI],TERHID-I J

// TERilHAilE

fl ATE.TERNI4,

]ERIID.I4

// TERMNAfr

E NANE.IERNI5,

TERhID.I5

// TERilNATE

NAilE-TERNI6,TERXID-I6

// TERTNANE

IAfrE.IERXIT,TERTID-I7

// TERNNAfi

E NAdE-TERTIA,

TERdID-I6

// TERilNAfr

E NAilE-TERTI

g,TERMID-I,

-// TERHNAIE

XAtsE.TERTJO,TERilID.JO

// IERNNAilE

NAilE.TERTJI,TERilID-JI

// TERilNAME

NANE-TERMJ2,TERNID-J2

// TERXNAIE

fl

ATE-TERMJ3,

IERNID-J]

// TERidAIE NAME.IERiJ4, TERMID-J4

// TERilNAilE

flANE-IERilJ5,TERHID-J5

_// TERTTAME

NANE-TERNJ6,TERdID-J6

-// TERitAilE NAffE-TERrJ7,

TERmID-J7

// ]ERilNAiE XAME-TERilJ6,TERilID-JE

// TERITAilE NAXE.TERhJ

g,

TERfl

ID.J9

// TERNIAXE NAflE-IERSilO,]ERXID-iO

// TERilIAT€ NAT€.TERNfrI,TERTID.ilI

// TERTNAfrE NAilE-T€Rfiil2,TERilID-il2

// TERilflATE

NATE-TERilil3,IERXID-i]

// TERilNANE

NAiE-TER[tr4,TERNID-N{

// TERfrNAilE

NANE-TERilX5,TERilID-i5

// IERMIAilE NAM€-IERiH6,TERfrID-X6

// IERXNAEE

NAiE-TERiiT,TERiID-M7

// TERilXAf,E

NATE-TERTil8,TERMID.ilE

// TERilNATE

NAilE-TERilil9,TERilID-T9

// TERilNAiE NAilE-T€RiNO,TERilID-NO

// TERfrNAfrE

NAfrE-TERfrNI,IERTID-ilI

// TERilNAilE

NAXE.TERilN2,TERiID.N2

// TERiNATE IAIE-TERiNJ,TERMID.NJ

// TERTilAflE

NAilE-TERilN4,I[RilID.N4

// TERilXAXE

NASE-TERMT5,TERTID.N5

// T€RilNAiE fAiE-TERilN6,TERiID-N6

// TERINAilE NANE-TERENT,TERMID-N7

// TERMHAilE

NAilE-IERIN6,TERTID-NE

// TERMNANE

NAfr

E-IERilN', TERiIO-N9

// TERNTAXE

NAilE-TERilOO,TERilID-OO

// TERtrTAiE IAilE-I€RXOI,]ERHID.OT

// TERINAilE NAXE.IERNOz,TERHID-O?

/

/ IERNNANE

NATE-TERSOJ,TERilJD-05

// T€RiNAilE NAME-TERiO4,TERMID-O(

// TERTNATE

NAXE-TERfrO5,]ERXID

O5

// TERf,NANE

NAil€.TERNO6,TERilID.O6

// IERilNANE

NAffE-TERMOT,TERfrID-07

// IERfrTAME

NAilE-TERilO8,TERMID-08

// IERXNAff

E NAME.TERTO9,IERfr

ID-09

// TERXilAME

NAtsE*TERilTO,

TERMID-IO

// TERTNAtr€

NAXE_]ERMT1,

TERil]D-TI

// TERf,NATE

NATE.IERilT2,

TERXID-T2

// T€R[NAIE NAME-TERMTJ,TERilID.T]

// TERffflAME

NAME-TERXTq,TERTID.Tg

// TERilNAilE

NAilE-TERilT5,

I€Rff

ID-T5

// TERiXAfrE NATE-TERET6,TERfrID.T6

// TERilNAT€

NATE-TERMIT,TERTID.TT

// T€RMNAME

NAilE-TERXT6,TERTID-T6

// TERTXAiE NATE-TERfl]9,]ERHID.T9

// TERHflAXE

NANE-TERfrUO,TERTID.UO

// TERNNATE

XAME.TERilUI,TERMID.UI

/I TERTBAiE flAHE-TERTU2,TERiID.U2

// TERiNAiE NANE-]ERIIUS,IERXID.U]

// ]ERfiHATE XAilE.TERilU(,TERIID.U4

// TERflNATE

NAilE-TERiU5,

TERMID.U5

// TERTXAFE

NAME-TERffU6,TERiID.U5

// TERilNAilE

NAME-IERilUT,TERTID-U7

-// TERTIAiE NAEE-TERiU6,T€RrID-UA

// TERMNAXE

TAiE-TERiU9, TERXID-U9

// TERfrilAT€

NAME.TERiVO,TERMID-VO

// TERXNAME

NAiE-TERilVI, TERilID-VI

// TERNNAilE

NATE-TEROV2,TERflID.V2

// TERilflAtrE

NAM€-TERf,V],TERMID-VJ

-// TERXNAiE NAME-TERfrV4,TERMID.V4

-// TERMNAiE

NAFE-TERTV5,TERTID-V5

// IERXNAIE

NATE.IERilV6,TERNID.!6

// TERXilAfr

E NAIE-TERfl

V7,

TERilID.V/

. // ]ERhNATE NAXE-IERNVE,

TERilID-VE

// IERANAiE

NATE.TERIVg,

TERHID-V9

/

/ DISKF

IIE NAilE-FILOOO,

ORG-I,RECL-I6,(EYL.6,KIYPOS.II

// DI5KFILE N4NE.FILOOI,ORG-I,REC!-I6,K€YL-6,KE:YPOS-1I

// DTsKFILE

NABE-FILOO2,ORG-I,RECL-I6,KEYL-6,(EYPO5-II

// DISKFIL€

IAXE-FILOO],ORG-I,RECL.I6,(EYL

6,K€YPOS.I1

/ / D\5KF'TE NAHE-FILOO<,ORC.I,RECL-I6,KEY!-6,XEYPO5-I

T

// DISKFILE

NAXE

FILOO5,ORG-I,RECL.I5,XEYL-6,XEYPO5_II

/7 DISXFILE NAHE.FILOO6,OR6-I,RECL.I6,XEYL-6,K€YPO5-II

Figure 18 {Part 3 of 8). CCp Assignment Sst Listing for Example_S7O4_SC2

Onty

conf

iguration

Limitations,

Storage

Estimates

and Perf

ormance

considerations 213

ILE IAHE-F]LiI5,ORG-I,RECL.I6,KEYL,6,(EYPO5-II

ILE NAIT-i

ILII6,ORG-I,RECL-I5,KEYI.6,KEYPO5-II

ILE hAilE-FILIITIORG-I,RECI-I6,(EYL-6,KEYP05-II

II€ NAiE FILII6,ORG.I,AECI,I6,XEYL-6,(EYPO5,II

I L E NAME-FI

L

I I 9, ORG-

I, RECL.

I6, KEYL

-6,

KEYPO5.I

I

ItE fAdE-FITI2O,ORC-I,R€CL-I6,KEY!.6,(EYPO5-I1

ILE NANE.FILI2T,ORG-I,RECL.I6,KEYL-6,KEYPO5,1I

ILE IAhE_FILI22,

ORG-I,

RECL-I6,

KEY!-6,XEYPO5-II

ILE NAfrE-FILI2],ORG-I,RECL-I5,KEYL-6,(EYPOS,II

ILE NATE.FILI24,ORG.I,RECL.I6,KEYL-6,KEYPO5-II

ILE NAilE-FILI25,

ORC.I,RECL-r6,K€YL-6,

X€YPOS-II

ILE NAHE-FIIIz6,ORG-I,RECL-I6,KEYL.6,KEYPOS-II

ILE NAilE-FILI27,ORG-I,REC!-I6,XEYL,6,XEYPO5-II

ILE NAilE_FILI28,ORG.I,RECL.I5,XEYL-6,XEYPO5-II

ILE IATE.FILI29,ORG-I,RECL-I6,KTYT-6,K€YPOS-II

ILE NAiE-FIIIJO,ORC.I,RECL.I6,XE'L-6,XEYPOS-II

IL€ NATE_FILI3I,ORG-I,RECI-I6,KErL-6,KEYPO5-II

ILE flANE-FTLT]2,ORG-I,REC!-I6,XEYL.6.KEYPO5-I1

ILE IAtrE FILTJJ,ORG-I,RECL.16,KEYL-6.KEYPOS.II

ILE NAME-FILI]4,OR6.I,RECL-I6,K€YL_6,K€YPO5-I1

I!E IAIE.FIIIJ5,ORG-I,RECL-16,KEIT-6,KEYPO5-II

ILE NAME_FILI]6,ORG.I,RECL-I6,XE'/L-6,XEYPOS-II

IL€ NAIE-FILI]7,ORG.I,RECL.I6,(E'IL-5,KEYPOS.I

I

IL€ NAilE.FIL

1]E,ORG-I,RICL-I6,KE'rL-6,KEYPO5.II

ILE NAIE-FILI]9,ORG,I,RECL*I6,K€TL-6,KEYPO5,Ii

LE NANE-FIII(O,ORG.I,RECL-I6,KE'rL-6,XEYPOS-II

LE HAflE-FILI4I,ORG-I,R€CL-I6,KEYL.6,XEYPO5-II

ILE NAtrE-FIL142,ORG-I,RECI-I6,(EYL.6,(EYPO5-II

LE NAilE-FILI45,ORG.I,RECL-I5,K€YL-5,KEYPOS.II

LE NAME-FILI44,ORG.I,RECI-I6,KEY!-6,KEYPOS

II

LE dATE.FILI{5,ORG-1,RECL.16,KEYL.6,KEYPO5-II

LE

NAME'FILI46,ORG-I,RECL-I6,KEYL.5,KEYPOS-II

LE NAHE-FILI47,ORG,I,RECL-I6,KEYL-6,KEYPO5.rI

LE NAilE-FILl48,ORG,I,RECI-I5,(EYL-6,KEYPO5-II

L€ IAilE.FIL

I49,ORG-I,RECL-I6,KEYL-6,KEYPOS-1

I

LE NAhE-FIL!5O,ORG-I,RECL,I6,KEYL.6,XEYPO9_II

E NAfl€.FIII5I,ORG-I,RECL-16,KEYI-6,KEYPOS.It

E TAilE-FILl5Z,ORC-I,

RECL-I6, K€YL-6,XrYPO3.II

LE NAilE-FILI55,ORG-I,RECL-I6,KEYL-6,KEYPO5.TI

LE NAHE-FILT'C,ORG,I,RECL.I6,KEY!.6,KEYPO5-II

IATE-FIL

I55,ORG-I,RECL-I6,

KEYL-6,

KEYPOS.II

NAff

E-FILI56,ORG-I,RECT.I6,XEYL.6,

XEYPOS-II

NAME-FILI57,ORG-I,RECI.I6,KEYL-6,KEYPO5

II

NAIlE-FILI56,ORG-I,RECL-I6,(EYL-6,KEYPO5.I

I

NAM€'FIII59,ORG-I,RTCL-16,K€YL-6,XEYPOS-II

NANE.FILI6O,

ORC.I,

RECL_T6,

KEYI-6,KEYPO5-1I

NATE-FILI6I,

ORG'I,

R€C1.16,

KE)'1,

6, KEYPOs-II

NAilE.FIL

162,ORG-I,

RECL-I6,

KEYI-6,

KEYPOS-II

IANE-FILI6J,ORG*I,RECT.I6,

KEYL-6,XEYPO5-II

NATE.FILI64,ORG-I,RECI.I5,

KEYL-5,(EYPOS-tI

NAiE.FILt65,ORG-I,RtCL.I6 IKEYL-6

IKEYPOS-I1

NAHE-FI1166,

ORG-I,

RECL-T6,

KEII-6, KEYPOS-II

NA[E-FILI67,ORG-I,

RECI-I6,

KE)'L-6,XEYPO5-II

NAilE

-

FI

T 5I6 , DISKFI I" E- F

I L 026

NAilE'FI

L S I7 ,

DI

SKFI L E. FI

L 027

NAilE-

FI

L 51E

,

DI S

KFI L E- FI

T O 2E

NAtsE-

F

I L 5I9 ,

D

I

S(F

I L E-FI L O 2 9

NAffE-

F I

L S2O

,

DI

SK

FI

L E- FI

L O 5 O

NAiE- FI

L 52I ,

DI

SKFI L

E-

T

I L O ] I

TANE-

FI

T S22, DI

SKFI L E- FI

I O ]

2

ilAiE- FI

L S2 ], DI

SKFI L E- FI

T O 5]

NAiE-

F I

L 5 24

,

D I

SKFI L E- FI

T O ]4

E NAdE-FILI66,ORG-I,

RECL-16,(EYL.6,XEYPO5-II

E NAME-FIII69,ORG-I,RECL-I6,XEr

L-6,KEYPO5.II

E XAi€ FITITO,ORG-I,RECI_I6,XE\'1.6,

KEYPO5-II

E NAiE.FIL17I, ORG-I,RECL-I6,XE]'L.6,XEYPO5-II

E NATE-FII.I72,ORG-I,RECL.I6,KE!'T-6.KEYPOS.II

E TAtrE-FILI7],ORG_I,RECL-I6,

KE}!.6, K€YPO5-1I

E NAilE.FILIT{,ORG-I,RECI-I6,

XEIL-6,

KEYPO5-I1

€ NAilE-FILI75,ORG-I,RECL-I6,

KE}L.6,XEYPO5-II

€ NATE.FILIT6,ORG

I,RECI.I6,KEIL-6,KEYPO5-II

E NATE-FILI77,

ORG.I,RECL.I6,XEYL-5,KEYPOS.I

I

E NAilE-FILI78,ORG-I,RECL-I6,XEYL.6,XEYPOS-Ir

E NAME-FILI7',ORG.I,

RECI.I6,

KEYT-6,KEYPO5.II

E NAiE'FILl6O,ORG-I,RECL-I6,KEYL.6,(€YPO5-1I

€ NAilE-FILI8I,ORG-I,RECI-16,

KEYL.6,

KEYPOS-II

E TAiE.FILI62, ORG-I,RECL-I6,XEYL-6,

KEYPOS-IT

E NATE.FILIEJ,ORG-I,RECL_16,(EYL-6,

KEYPOS.II

E NAAE-FILI8q,ORG-I,RECL.I6,XEYL-5,KEYPOS.II

E NAilE-FILI85,ORG-I,

RECL-I6,KEYI-6,

XEYPOS.lI

E TANE-FIIIE6,ORG.I,RECT-I6,

KEYL-6,

KEYPOS-II

E dAHE-FIL

1E7,ORG-I,RECI-I5,(EYL-6,

KEYPOS-II

E NAME-FILI6A,ORG-I,RECL.16,KEYL-6,KEYPOS.I1

E NAilE.FIL

I69,ORG-I,RECL-I5,

KEYI-6,KEYPOS-r1

€ NAiE'FILI9O,ORG-I,

RECL-I6,KEYL-6,

KEYPOS-1I

E NAiE-FILI9I,ORG.I,RECI-I6,KEYL-5,KEYPO5.II

// PROORAi

ilAIE-DCPOOI,frRTTAX.T,DFFilTERM-7,

// DFFNDF-T,DFFSFDT-2'6,PACX-F2

// PROGRAil

NAilE-DCPOO2,ilRTXAX-7,DFFil]€RX-7,

DFFNDF- 7

,

DFF5FDT.2

56, PACK- F2

/ / ?ROG?AN

NATE-DCPOOJ,XRTiAX-7,DFFilTERr-7,

DFFIDF- 7

, DFFS FDT-

2 5E, PACK-F2

// PROGRAi

NAIE-DCPOOq,MRTilAX.T,DFFNTERil-7,

DFFTDF-7

, DFFS FDT.2

'A,P ACK-F2

// PROCRIil

NAilE-DCPOO5,iRTilAX.T,DFFXIERM.I

DFFNDF.

T

,

DFFS FDT

-25E, PACK.F2

// PROGRAT

TAiE.DCPOO6,iRTfAX.),DFFiTERr.Z,

DFFNDF. T

, DFFSFDT-258,

PACK- T2

// PROGRIil

NATE-DCPOOT,ilRTTAX-',DFFMTER[-I,

DFFNDF-

7

,

OFFSFD]-2

5A, PACK-

F2

// PROGRAtr

NATE-DCPOO6,NRTiAX-T,DrriTERi-7,

// DFFNDF.T,DFFSFDT-z5E,PACK-F2

..// PROGRAi

NAil€.DCPOO9,NRTiAX.7,DFFHTERfr-7,

DFFNDF-

7

, DFFSFDT-2

5A, PACK-

F2

Figure

l8 (Part

4 of 8). ccP Assignment

set Listing for Exampre-s7Ozt-sc2

onry

2t14

// PROGRAi

IAiE-DCPOII,f,ETTAX-T,DFFITEFI

7,

// IFTIDF-7,DFFsIOT 25E,PACK-F?

-// PROGRAi NAiE-DCPOI?,TRTJAX

I,DFFNlLRd 7,

DFFNDF.T , DFFSFDT

-256,

PACX f

2

/

/ ?ROCRAN NA{E-DCPOII,NRTNAX_7,

DFFITERi-7,

DF FNDF- 7

,

DF F 5 FDI

-

2 'E ,

P AC(

-

F2

// PROGRAi

NA!E-DCPOI4,ilRIiAX-7,DFFilIERA.7,

DFFNDF-

7

,

DF

F5

FDI

-

2 '6 ,

PAC K

-

F2

// PROGRAF NAHE-DCPOI5,iR]ilAX-T,DFFiIERE-7,

DFFNDF-7

, DFFSFDI-25E,

PACX-F2

// PROGRAN

NAiE-DCPOI6,IRIXAX.T,DFFEIERE

7,

DFFNDF 7,OFF5FD]-2'6,PAC(-F2

// PROGRAT

flAN€-DCPOIT,iRITAX-7,DTFNTERi.7,

DFFN9F

T.DFFSFDI

?56,PACX,f2

// PROGRAi

NAME-DCPOIE,FRTilAX.T,DFFiTERtr

7

DFFNDF-

7

, DFFSFD]

-

2 56

,

PACK

-

F

?

// PROGRAT

NAFE-DCPOI9,hRIIAX-7,DFFi]ERN-7

DFFIDF-

7,

DFF5FDT

-

25E, PAC(-F2

// ?ROGRA6

NATE-DCPO2O.TRTffAX-7,DFFFTtRtr

7

DF F N

DF-

) , DF F5 FDT

-

2 '8, PAC(

-

F?

// PROGRAil

XAiE-DCPO2I,ilRTTAX.7,DFF6]ERr-7,

OFFNDF-7,

DFFSFDI-25E,

PAC(-F2

// PROGiAN ilAFE-DCPO25INRIFAX.7'DFFHTERN-7

OFFNDF- 7

, Df

FSFDT

-25E,

PACK- F2

// PROGRAi NANE-DCPO25,TRIFAX-7,DFFMI€RN-7,

DF FNDF- 7

, OFFS FD I

-2

56, P ACK- F2

// PROGRAH

TAiE-DCPO27,ilRT[AX,T,DFFMTERi-7,

DFFNDF- 7

, DFFS

FD]

-

? 56 ,

PACX-

F2

DFFNDF. T

, DF FSFDI

-

2

5E ,

PACX

-

F2

// PROGRAI NAilE'DCPO2J,ilR]iAX-T,DFFiIERi-7

DF T N

OF- 7 , DF F

5 FD I - 2 56 , PACX - F 2

// PROGRAH NAilE-DCPO22,iRTfrAX,7,DFFilTERi-7

// PROGRAil

IAf,E-DCPO2(,iRTNAX.7,DFFTT€Rfr-7

// PROGRAfl

NANE-DCPOZE,TRTilAX-7,DFFilIERil-7

DF

F

HDF- 7 ,

DF

F

5

FDT,2

5I

,

P AC

K. F 2

DFFI

DF-

) , DF

F

5 FDI

-2

5E

I

PACX- F2

DFFNDF-7,

DFFSFDI-256,

PACK-F2

OFFNDF-7

,

DFFSF DT.258, PACK-

F?

DFFN DF.7 , DFFS FDT.258, PACK-

F2

DF FdDF- 7

, DFFS FDI-

2 58,

PACK

-

T2

// PROGRAi

TANE-DCPO29,iRIiAX-7,DFFiIERtr.7

DFFNDF.T

, DFFS FDT

'256, PACK. F2

// PROORAT

HAiE-DCPOSI,NRIiAX-T,DFFHIERT-7,

DF FN

DF-

7

, DFFS FDT

-

25A, PACR-

F2

// PROGRAT

IA[E.DCPOJJ,TRTtrAX_7,DFFilTERi-7,

DFFNDF_7,

DFFSFDI-256,

PAC(-F2

DFTNDF T,DFFSFDI

Z56,PAC(.F2

// PROGRAfr

NAiE.DCPO4E,TRTIAX-T,DFFiTERi-7

DFENDF.T

, DF FS FDT-

2 5E

,

PACX

-F2

// PROGRAT

NATE_DCPO'9,[RTSAX-T,DFFiIERM-7,

DFFNDF. T

, DFf SFDT_ ?5E, PACX-

F2

// PROGRAfi

IAiE-DCPO]O,ilRTilAX-7,DFFilTERi_7

// PROGRAT

ilAil€_DCPO]2,iRTilAX-7,DFFtr]ERr-7

// PROCRAi

NATE-DCPO5O,MRTTAX-7,DFFilTERi-7,

// PROGRAil f,ANE-DCPO55,frRTfiAX.7,DFFXTERil.?

DFFNDF 7,DFF5FDI

25E,PACX.F2

// PROGRAX NATE-DCPO]4,MRITAX-7,DFFilTERi

7,

DFFNDF-7

,

DF F5 FDI

-256, PACX-

F2

// PROGRAi

TAfr€-DCPO]5,TRIhAX-T,DFFiIERM-7

DF FNDF.7

, DFF S FDT.?5A,

PACK. FZ

// PROGR}X

NAME.DCPOJ6,ilRTNAX-7,DFFTTERtr-7,

DFFNDF- 7

,

DFF5 FDI

-

2 56

,

PACK- F2

// PROGRAN

flAiE.DCPOS',iRTFAX.7,DFF6TERF 7,

DFFiDF- 7

,

DFFs FDI

-

2 5E, PACX

-

F2

-// PROGRAM

NAME-DCPO]A,MRTiAX_T,DFFNTERM-7,

DFFNDT.7,

DFFSFDI,25E, PACX.F2

// PROGRAi

XANE-DCPO59,TRIilAX-7,DFFiTERM.7,

DFFNDF-7

,

DFFS FDI

-

2 5A, PACK- F2

// PROGRAi NANE-DCPO{O,iRIiAX-7,DFFiT€RX-7,

DFFNDF.7,

DFFSFDT-2'6,

PACK.F2

-// PROGRAT NAiE-DCPO4I,MRTtsAX'7,DFFMTERfl

7,

-// DFFNDF-7,DFF5FDT-256,PAC(-F2

// PROGRAM NANE-DCPO(2,iRTlAX-7,DFFHTlRil

7,

DFFNDF. T

, DT

F5 FDI

-25A,

PACX

-

F2

/ / PROGRAI

NAME-DCPO4J,NRIhAX.7,

DFFMIERil-7,

DFFNDF 7, DFFSFDT-256,PACX-F2

// PROGRAN NAiE-DCPO44,MRTfrAX

7,DFFNIERil.7,

DFFNDF. T

, DF

F5 FDT.25A,

PACK-

F2

// PROGRAi

NAFE-DCPOq5,iRTMAX.T,DFFTTERts-7,

DFFNDF. T

,

DFFS FDT

-

2

5E, PACX-

f

2

// ?ROCPAtr

NANE-DCPOC6,ilRINAX.T,DFFMIERX-7,

DFFilDF- 7

, DF

F5 FDI

-256 ,

PACK. F2

// PROGRAM

ilAME-DCPO47,TRTIAX,T,DFFMTERN

7,

D'FN DF'7 ,

DF F5 FDI

-25A, PACK-

F2

// PROGRAi NAME-DCPO51,iRTilAX.7,DFFflTERi-7,

DFFNDF- 7

, DF FS

FDT

_25E,

PACX-

f 2

// PROGRAM

TAilE.DCPO52,ilRITAX-T,DFFTTERX-7,

DFFNDF- 7

, DFF 5 FDT.Z5t , PACK-F2

// PROGRAT TAiE-DCPO5(,iRIilTX.7,DFFhTERi.7

/' TROGRAN NAX€-DCPO55,NRTilAX-7,

DFFTTERI*7,

// PROGRAi

TAilE-DCPO56,iRTtsAX-T,DFFNIERi-7.

// PROGRAT

iAfrE.DCPO57,NR]iAX.7,DFFilTERi-7,

// OFFNDF-7,DFF5FDI-258,PACK-F2

// PROGRAil

NATE-DCPOSE,TRTNAX-7,DFFil]ERff-7,

DFFNDF- 7

, DFF5

FDT

-256, PACK.

F2

// PROGRAM XAME.DCPOS9,iIIfrAX-T,OFFXTERI-7,

DFFNDF-7, DFF5FDI-25A,

P ACK-F

2

DFFNDF

-

7

,

DFFSF

DI

-2

56, PAC{-F2

// PROGRAN

TAME-DCPO6O,FRIiAX-7,DFFMTERts.7,

// DFFTDF.T,DFF5FDT-z5E,PACX-TZ

// PROGRAi

iATE.DCPO6I,tsRTMAX.T,DFFHTERi-7,

DFFTOF- 7

, DFFS

FDT

-256,

PACK. F2

// PROGRA! IAiE-DCPO62,trRTiAX-T,DFFTTER[-7,

DFFNDF-7

,

DFFS F DT.2

58,

PACK-

F2

// PROGRAi

NAT€'DCPO6],frRT6AX-T,DFFMTERN-7,

/' DFFNDF-T,DFFSFDT-256,PACK-F2

DFFNDF-

7

, DFFS FDT.2

5E,

PACK-

F2

// PROGRAi

XANE.DCPO65,iRTTAX.7,DFFTTERM.7.

DFFNDF-7,

DFFSFDT-2

58,

PACX-F2

// PROGRAN

N TE-DCPO66,rRIiAX-T,DFFTTERX-7,

/' DFFNDF-T,DFFSFDT-25E,PACr-F2

-// PROGRAi

NATE.DCPO67,

iR]rAX-7 , DFFTTERN.

r,

/' DFFIDF-7,DFFSFDT.25E,PACK-F2

// PROGRAi

XAiE-DCPO6E,TRIiAX-T,DFFTTERi-7,

'' DFFNDF.T,DFFSFDT-z5E,PACK-F2

7/ PROCRAT

TATE.DCPO6g,iRTTAX-7,DFFtrTERfr-7,

,/ DFFNDF-7,

DFFSTDT-25!,

PACX-F2

-// PROGRAil

NATE-DCPOTO,iRIiAX-T,DFFFIERN-],

'// DEFilDF-T,DFFSFDT-Z:,6,pAC(-F2

// PR0GnA||

illnE-Dcpott,nRtflAX-T,DFFnTERi-7,

/' DFFNDF-T,DFFSFDT-256,PACK-F2

// pR0GRli xltrE-Dcp072,nRTiAX_T,DFFITERn_?,

'' DFFADF-7,

DFFSFDT.z5E,

PACX-F2

// PROGRAi

XAiE.DCPOT5,NRTiAX-7,DFFts1ERi-7,

/' DFFXDF-7,DFFSFDI.25E.PACX-F2

// pt0oRAi tAxE-DCp074,nRriAX_T,DFFnTERn-7,

/' DFFNDF-7,DFFsFDT-z5S,PAC(.F2

/ / ?70GR^t xlrE-Dcp075,rRIiAX_7, DFFBTERm_7,

DFFNDF_7

,

DFFSFDT-25r,

PACX-F2

// PROGRAi

NINE-DCPOT6,rRTrAX-7,DFFilTERr-7,

OFFNDF-7

,

DFFSFDT-25A,

PACX-F2

// PRocRrn iriE-DcpoTT,iRrtlx_7,DFFit€Rfi_7.

" DFFXDF-T,DFFSFDI-z5E,PACX-F2

// PROGRAtr

TAiE.DCPO'E,TRTNAX.T,DFFtsIERT-7,

'/ DFFNDF-7,

DFFSFDT-25E,

PACX.F2

//, PROGIAI HAiE-DCPOTg,iRTrAX-T,DFFiIERE-7.

/t DFFNDF_T,DFFSFDT_Z5E,plCX_F2

// PROGRAi

iAiE.DCPOEO,iRIiAX-7,DFFITERF-7,

/' DFFNDF-7,DFFSFDT.25E,P CK-F2

// ?roea^n iAnE-Dcpott,hRInAx-7,DFFflIERr-7,

'/ DFFXDF-'

, DFFsFDT-25E,

PACX-Fz

// PR0cRAi xAnE-DCpOS2,iRnlx-7,DFFir€Ri_7,

/' DFFXDF-7,DFFSFDT.25E,PACX-F2

// PNOG?AN XAB€.DCPOES,IRTiAX-7,DFFiTERfr.7.

// DFFTDF-7,DFFsFDT-25E,P

CX.F?

// ?ROGRAA NAIE.DCPO!4,frRTiAX-7,DFFTIERr.7,

'' DFFNDF-',DFF5FDT-25E,PACX-F2

// ?ROGRA6 XANE-DCPOrS,rRTiAX-T,DFFNTERi-7,

/t DFFilDF-T,DFFsFDI-25a,plcX_fz

// ?ROc?^6 xliE-Dcp0!6,rRTilx-7 ,

DFFfrTERM_?

,

'. DFFXDF-T,DFFSFDT-25E,PIcx-F2

// PROGRAi

iAN€-DCPOET,iRITAX.T,DFFMIERH-7.

// DFFXDF-T,DFFSFDT-25!,PACT.F2

// PROGRAI

NAiE-DCPOEE,iRIiAX-7,D,FilTERN-7,

DFFNDF-

7,

DFFSFDT

-25A, PACK-F2

/ / ?ROGRAN

iAiE-DCPOE',NRT! X-7, DFF6TERi.7,

lt DFFNDF-T,DFFSFDT_25E,p^CI_F2

/T PNOGRAN

IAiE-DCPO9O,TRIiAX.7,DFFXTERT.7,

DFFTDF.7,

DFFSFDT.25S,PAC(-F2

// PROGRAi

IANE-DCPO'I,trRINAX-7,DFFTTERE.7,

ta DFFXOF-T,DFFSFDT-2SS,P^CX_F2

// pRoGRAn

XtiE-Dcp092,nRTilx-r,DFFnTERn_7,

// 0FFXDF-T,DFFSFDT-25a,pICX_F2

// pt0cRli rlnE-Dcp0gl,iRrnax_T,DFFirERr-7,

t. DFFXDF-7,

DFFSFDT_Z5!

,

pACK-F?

./ ?noca^n NArE-DCpO9(,frRlnlx_T,DFFnTERr_7,

lt DFFXDF_T,DFFSFDT_25!,pACX_Fz

// PROGRAN

iAIE-DCPO'5,NRIIAX-T,DFFHTERI-7,

/, DFFTDF-T,DFFSFDT-25E,,ACX-F2

-/ r ?eoci^A rAnE-DCp096,tRlilx_7, DFFTTERi_7,

DFFXDF-7,

DFTSFDT-2,E,

PACT-F2

// PROGIAi XAiE-DCPO'7,iRTI!AX.7,DFFiTERil.?,

'/ DFFXDF-7,DFFSFDI.25E,PACK-F2

/, p2063AF rAiE-DCp0 gE,rRTilx_7, DFFiTERI_7,

/' DFFNDF-7,

DFFSFDT-25E,

PACT-F2

=/ / ?ROG?^n NliE-Dcp099,frRTiAX-7, DFFTtERT_7,

-// DFFNDF-7,DFF5FDT-25s,PAC(-F2

// pR0cRAi N^iE-DCpl00,iRtrAx_T,DFFitEir_7,

/' DFFXDF-T,DFFSFDT-z5E,PACK.F2

r // pRocRli xliE-Dcpt0l,iRTrAX_T,DFFrTERn-7,

// DFFTDF-T,DFFSFDT-25a,PTCX-F2

// pR0GRli NltlE-Dcpl02,nRTiAX-T,DFFrTERr_7,

'/ OFFXDF-T,DFFSFDI-25A,PACR-F2

// PROGRAi

XAT€.DCPIOJ,iRIMAX.T,DFFfrTERi-7,

// DFFIDF-7,DFFSFDT.25E,PACT-F2

// PROGRAN

N TE-DCPl04,XRTXAX-7,DFF6TERil-7.

// DfFTDF.T,DFFSFDT-25s,PACX-F2

// PRO6RAi NATE-DCPIOS,iRTIAX-T,DFFiTERT-7,

// DFFTDF-T,DFFSFDT-25E,PACX-F2

// PROGRAi

NAiE.DCPIO6,iRTNAX-T,DFFNTERH-7.

/, DFFNDF.T,DFFSFDT-25E1PICK.F2

// PROGRAil

NATE.DCPIOT,TRTfrAX-T,DFFiIERr-7,

DFFNDF.7,

DFF5FDI.25!, PACK.F2

// PROGRIi XAiE.DCPIOE,iRTIAX.T,DFFiTERi-7,

lt DFFf,DF_T,DFFSFDT_25S,p^C(-F2

// PROGRAT

NAFE-DCPIO',ilR]fr

AX-?, DFFiIERi-7,

lt DFFNDF-T,DFFSFDT-Z56,PACX_F2

// PIOGRAi XATE-DCPIIO,iRTMAX.T,DFFT]ERT-7,

/, DFFTDF.T,DFFSFD]-25A,PACX.F2

// PRoGRlt xAiE-DCptt t,ilRTirx_7, DFFfr

TERi-7.

DFFXDF-7,

DFFSFDT.258,

PACX-F2

// PRocRAi tAiE-DCptt2,iRIrAx_7, DFFITERh_7,

// DFFXDF.T,DFFSFDT-256,PACK-F2

// PROGRAi

XANE-DCPI!5,NR]TAX.7,DFFiTERtr.7.

/' DFFToF-7,DFFSFD].?5E,PACX-F2

// PROGRIi HAfrE.DCPII4,XRTiAX.T,DFFilTERT-7.

DFFfl

DF-7, DFFSFDT-25E,

PTCX-F2

// PROGRAi

TAfrE-DCPtI5,XRTNAX.T,DFFilTER[-7.

/t DFFNDF-7,

DFFSFDT-25!,.P^CX_F2

// PROGIIi XAXE-DCPII6,BRTiAX.T,DFFITERT-7,

DFFNDF-7,

DFFS FDT.25E,

PACX.F2

Figure 18 (Part 5 of 81. CCP

Assignment Set Lining for Example_5704-SC2 Only

// PROGRIT

TAIE-DCFIT7,MRTilAX.7,DFFI'TERN-7.

,/ DFFIDF-T,DFFSFDT-25T,PACT-F2

/ / PXOGRAA

NAiE-DCPIIE,TRriAX.T,

DFFIIERi-7,

/. DFFNDF-T,DFFSFDT-256,PACX.F2

// PR0CRli

NIIE-0cpllg,xRriax-T,DFFnTEti_7,

DFFNDT-7,

OFFSFDT-25E,

PACX-F2

// pR0cRAt

taiE-Dcpt20,nRrnlx_T,DFFnTEti_7.

// DFFXDF-T,DFFSFDI-25E,PAcK-F?

// PTOGRAi

XANE|DCPI2I,NRIiAX-7,DFFBTERil-,,

DFFNDF-7,

DFFSFDI-25',PACX-F2

// PRocRln

xliE-Dcpl22,iRlilx-7, DFFiI€Ri-7,

/. DFFN0F_T,DFFSFDI_256,|^CX_F2

// pRocRAll

HAIIE-DCpl2t,nRTilx_?,

DFFiTERIi_7,

Il DFFXDF-T,DFFSFDT-25E,PACX-F2

// ptocRAtr

xlnE-Dcpl24,iRTilx_T,DFFiTEti_7.

/' DFFIDF.T,DFFSFDI-25E,PACT-F?

-// Pn0cRIt xtnE-Dcpl25,iltTilx-r,DFFltTEtt_r,

t. DFFNDF_T,DFFSFDT_25E,pIC(-F2

// PnocRAn

xtiE-Dcpt26,nRTilx-T,DFFftTERi_?.

DFFXDF-' , D'FSFDT.25E, PACX-F2

// PR0cRAt

tliE-Dcpl2T,iRrn^r-T,DFFirEtI_r,

// DFFNDF-?,DFFSFDT-25!,PACr-F?

-// ptocRlr ltl;€-DCpl2E,iRrt^X_r,DFFirERt_7,

'// DFFiDF-T,DFFSFDT-25!,plcx-F2

// PROCRAN

XAiE-DCPI29,iRTilAX.7,DFFilTERi-7,

DFFXDF-7

, DFFSFDT-25E,

PACX-F2

// PROGRAi NANE.DCPI5O

Ifr

RTiAX-7, DFFNTERi-7.

DFFXDF.T

, DFFSFDT-25t,

P CX-F2

// PROGRAIl

TATE-DCPI

JI,NRTIAX.7,DFFiIERil-7,

DFFNDF-7

, DFFSFDT-25E,

PACX.F2

// PROGRAi

XAtrE.DCPI

32,fl RTiAX.7, DFFNTESi-',

DFFNDF-7

,

DFFSFDT-25E,

PIC(-F2

// PROCRAtr

IAfiE-DCPt35,XRTiAX.7,DFFtsTERi-7,

DFFilDF-7

, DTFS FDI-25E, PACX.F2

// PROGRAtr

XAiE.DCPIS(,iRIiAX.T,DFFiTERi-7,

DFFNDF.T

, DFFSFDT-25I,

PACX.F2

// PROGRAT

NANE-DCPI55,trRTiAX-7,DFFNTERtr-7.

DFFXDF-7

, DFF5FDT.25E,

PACX-F2

// PROGRAi

ililE.DCPI5E,ffRTTAX.T,DFFNTERi-7.

DFFXDF-7,

DFFS FDT.25E,

PACK-F2

// P2O6RAN

XANE.DCPTS9,TRTTAX-7,DFFilT€Ril-7,

DFFIDF-7

,

DFF5FDT.25E,

PACT.F2

// PROGRAN

XAT€-DCPI(O,rRThAX-7,DFFiTERf,.7,

DFFIDF-7, DFFSFDI

-25t, PACX.F2

// PROGRAi

i NE-DCPI4I,MRTiAX-T,DFFNTERT-7,

DFFNDF-7

, DFFSFDT-256,

PACX-F2

// PROGRAi

XAXE.DCPT42,fi

R]ilAX.7, DFFiT€RT-7,

// DFFNDF.T,DFFSFD]-25E,PACK-F2

// PROGRIM

IAilE.DCPI4J,NRTilAX-7,DFFhTERi.7.

/. DFFNDF.T,DFFSFDT-256,PACX-F2

// PROGRAi

NAiE.DCPI4(, TRTIAX-7, DFFtrTERfl

-7,

DFFNDF.T

, DFFSFDT-25E,

PACX-F2

// PROGRAi

NINE.DCPI{5,iRIilAX.7,DFFrTERE-7.

DFFNDF-7,

DFf SFDT-25E,

PACK-F2

// PROGRAI

NAiE-DCPIJ6,TRIIIAX-7,DFFXIERi.',

DFFNDF.7,

DrF5FDT.25r,

PACX-F2

// PROGRAI

NAN€.DCP1]',TRTTAX-7,DFFiIERi.7.

// PROGRAA

XATE.DCPI46,TRTTAI-7,DFFiIERr.7,

DFFNDF.T

, DFFSFDI-25E,

PACX-F2

// PROGRAtr

TAIE.DCPI4T,trRTrAX-',DFFNTERi-7.

DFFf, DF.7, DFFSFDI.29A,? ACK-F2

DFFNDF-7,DFFSFDI-25t, PACX.F2

// PROGRAT

NANE-DCPI59,XRTTAX.7,DFFflTERX-7,

DFFTOF-7

,

DFFSFDT-25E,

PACX-F2

?'/ PRocRAi

NAiE-DCPl60,rRrilAX-T,DFFiTERr-r,

DFFXDF-7,

DFFSFDT.25A,

PACK-F2

// PROGRAT

TAiE.DCPI6 1,fr

RIrAX-7, DFFiTERil-7

DFFXDF-7

, DFFSFDT-25t,

PACK-F2

// PROGRAi

XAXE-DCPI62,rRTilAX.7,DFFiT€Rtr-7

DFFTDF.7,

DFF9FDT.25A,

PACK-F2

DFFXDF.7,

DFFSFDT-25E,

PACK-F2

DFFTDF-7

, DFFSFDT.25E,

PAC(-F2

// PROGRAT

NANE-DCPl4A,BRTNAX-7,DFFXIERtr-7,

DFFNDF-7,

DFFSFDT-25t,

PACX.F2

// PRO6RAi IATE-DCPtq9,ilRTiAX-7,DFFilTERil-7.

UFNOF.7, DFFSFDT-25!,

PACK-F2

// PROCRAN

NAfrE-DCPT5O,TRIiAX-7,DFFrTERil-7,

DFFNDF-'

, DFFSFDT-258,

PACX-F2

// PROGRAX

NAiE-DCPT5T,TRTTAX.T,DFFiT€Ril-7,

DFFNDF-7,

DFFSFDT.25E,PACK-F2

// PROGRAil

TAiE-DCPI52,frRTilAX-T,DFFNTER[.7,

DFFNOF.7,

DFFSFDT.25E,

PACK-F2

DFFTDF-7,

DFFSFDT-?5E,PAC(-F2

// PROGRAi

XAiE.DCPI55,ilRTiAX-T,DFFiTERN-7,

'' DFFNDF.T,DFFSFDT-A5!,P CX.F2

// PROGRAi

XA[E.DCPI55,iRTXAX-7,DFFNTERil.7,

DFFXDF.7

, DFFSFDT-25!,

PAC(-F2

-// PROGRAil

NAiE.DCPI5',fr RTMAX-7,

DFFSTERtr.7,

-// DFFTDF.T,DFFSFDI-25E,PACK-Fz

// PROGRAi

NAilE-DCPl5A,iRTi X-7,DFFilTERi-7,

/ / ?ROGRAN

NANE-DCPI55,trRTiAX.7,

DFFilTERN,I.

'/ DFFHDF-7,DFFsFDT.z5E,PAcx.F2

-// PSOGRAH

XAflE-DCI'T4,trRTiAX-7,DFFXIERr.7,

// PROGRAI

XAiE-DCPI63,TR]iAX-7,DFFiTERT.',

DFFXDF-7,

DFF5FDT-25T,PACK-F2

// PROGRAX

iAi€-OCPI64,iRTiAX-7, DFFTIERT-7.

/' DFFNDF.7,

DFFSFDT-2sE,

PACI(-Fz

// PROGRAN

NAfr

E.DCPI65,ilRTilAX.7, DFFNTERT-7,

// PROGRAi

TAiE-DCPI55,ilRTiAX-7,DFFfrTERil.7,

// DFFNDF-T,DFFSFDI-z5E,PACX-F2

// PROGRAi

TAilE.DCP167,TRTMAX.7,DFFtsTERr-7.

DFFilDF.7,

DFFSFDT.256,

PACX-F2

// PROGRAi

NAiE.DCPI6A,TRTiAX-7,DFFiTERil-7,

DFFNDF.7,

DFFSFDT-25E,

PACK.F2

// PROGRAi

NAilE.DCPI69,TRIMAX-T,DFFMTERi-7.

DFFNDF-7,

DFFSFDT-25E,

PACX-F2

configuration Limitations, storage Estimates

and performance considerations 215

DFFNDF-

7

,

DFFS

FDT

-25E, PACK-

F2

// PROGRAi

NAHE.DCPITl,MRTilAX-7,DFFfrTERfi-7,

DFFN

DF- 7, DFFSFD].25A,

PACK.f

2

// PROGRAI

NATE-DCPr'2,iRTMAX-7,DFFilTERts-7,

'' DFFNDF-T,DFFSFDI-25E,PACK-Fz

// PROGRAfr

NAdE-DCPI75,frRIilAX.7,DFFNTERX-7,

" DFFNDF-7,DFFsFDT.z5E,PACK.F2

// PROGRAI

ilAME-DCPI7(,flRIrAX.7,DFFilTERil-7,

DFFNDF,T

, DFFS FDT-256,

PACK.F2

7/ PROGRAN

flANE-DCPI75,MRTflAX-7,DFFfrTERfr-7,

DFFNDF-

7

,

DFFS

FDT-2

5E , PAC(.

F2

-// PROGRAh

NANE-DCPI6],rRTilAX.7,DFFMTERM.7,

DFf

ilDF.7

,

DFFS

FDT.25E.

PACK.F2

// PROGRAil

NAilE-DCPIE{,ilRTHAX.7,DFFrlERi-7,

DFFNDF-7,

DFFSFDT-25E,

PACK-F2

/./ PROGRAil

NANE.DCPI85,NRTfiAX.T,DFFTIERT-7.

DFFNDF.

T

,

DF F5

FD].256, PACK-

F2

_/,/ PROGRAN

NATE*DCPIA6,NRIXAX-7,DFFMTERtr-7,

-/:/

-- DFFflDF-T,DFFSFDT_Z56,pACK-F?

// pRoGRAil ilAilE-DcprET,ilRlraxalorrrrrnr_], - -

DFFNOF-7

, DFFS FDT.25E

,

PACK-F2

// PROGRAts

NAXE-DCPIE6,XRTilAX-7,DFFfrTERT.7,

// PROGRAT

XAME.DCPI76,iRTTAX.7,DFFfr]ERr_7.

DFFNDF-7

,

DFFS

FDT

-256, PACK-

F2

// PROGRAH

TAilE-DCPI77,ilRTTAX.7,DFFETERi-7.

DFFNDF.

T

, DrFS FDT-256,

PACK-

F2

// PROGRAtr

TAilE-DCPI76,rRTMAX,7,DFFil]ERT-7,

DFFIDF.7, DFFSFDT-256

,

PACK.F2

// PROGRAM

NA6E.DCPI79,MRTrAX

T,OFFNTERi-7,

DF FNDF_7

,

DFF5 FDT-25E

, PACX-F2

// PROGRAil

NAXE-DCPl6O,HRTNAX-T,DFFXTERM-7.

DFFNDF-7

,

DFFSFDT

*256 ,

PACK-F2

// PROGRAil

NATE-DCPI6I,ilRTTAX.T,DFFMIER[-7,

DFENDF.7,

DFFSFDT-258,

PACK-F2

// PROGRAfr

NAilE-DCPIA2,NRIiAX.T,DFFNTERI-7,

OFFNDF.T

, DFFSFDT.25E,

PACK.F2

DFFXDF-7

,

DFFSFDT-25A,

PACK-

F?

// PROGRAI

NATE-DCPIE',TRIilAX-7,DFFTTERfr.7,

DFFNDF.T

,

DFFSFDT-25E,

PACK.F2

// PROGRAT

NAME.DCPI9O,ilRTtrAX-7,DFFFTERM.7,

DFFXDF-7

,

DFFSFDT-25A,

PACK-

F2

// PROGRAi

NIiE-DCPI9I,TRIXAX-7,DFFilTERr.7,

DFFNDF-7,

DFFS FDT.25E,

PACK.F2

/,/ PROGRAT

NAiE-DCPr92,NRTMAX.7,DFFr]ERil.7,

DFFNDF

_2,

DF

F5f

DI_256, PACX_

F2

/., pR0GRAF

ilAME-Dcpr9J,[RTnAx{,DFFHIERil_7.

DFFNDF-7,

DFFSFDT-25E,

PACK-

F2

/,, PROGRAtr

NATE-DCPI9{,TRTTAX-7,DFFMTERil-7,

DFFiDF-7

, DFF5FDI.25E, PACK-F2

/,/ PROGRAM

XAiE.DCPI95,ilRTilAX.7,DFFTTERH-7.

DFFNDF.T

, DFFS FD]-25E, PACX-

F2

/r' PROGRAN

dATE-DCPI95,NRIfiAX.7,DFFMTER[-7,

/r' DFFNDF-T,DFFSFDT-256,PACX-Fz

/r' PROGRAT

NAiE-DCPI9',ilRTilAX.7,DFFilT€RI-7,

DFFXDF-

7,

DFFS FDT-256,

PACX-

F2

/r' PROGRAM

ilATE.DCPI98,TRTTAX.7,DFFilIERN-7,

DFFNDF-

I, DFFSFDT-258,

PACK-F2

// pR0cRAi NAiE-Dcprgg,iRTnAX-6,Drrnrttr-2,

DFFNDF-7

, DFF5FDT.25E,

PACK.

F2

// PROGRAil

NAiE-DCPZOO,iRTMAX-7,DFFXTERil.7,

/.' DFFNDF-T,DFFSFDT-256,PACK-F2

// PROGRAi

ilAiE-DCP2O1,ilRTilAX-7,DFFilIERT-7.

DFFNDF-7,

DFFSFDT-258,

PACK-F2

//' PROGRAtr

NATE-DCP2O2,trRIfrAX-7,DFFilTERr-7,

., DFFNDF-T,DFF5FD'_256,pACK-Fz

// PROGRAX

TAilE.DCP2OJ,TRTXAX.T,DFFilTERT-7,

lt DFFTDF-7,

DFFsFDT-?5E,

pACK_Fa

// PROGRAM

HATE.DCP2O4,NRTTAX-7,DFFITERM-7,

/' DFFNDF.TIDFFSFDT.25A,PACK-Fz

// PROGRAi

NAfrE-DCP2O5,NRTHAX-?,DFFNTERT-7,

DFFNDF-

7, DFFSFDT-25S,

PACK.F2

// PROGRAX

TAXE-DCPzO6,ilRTMAX-7,DFFrTERX.7

DFFNDF-7

, DFFSFDI-25A,

PACK-

F2

// PROGRAil

NANE-DCP2OT,TRTTAX-),DFFXTERN-7,

DFFNDF-

7

, DFFS

FDI-258, PACX-F2

// PROGRAX

NATE-DCPzOE,TRTMAX-7,DFFITERfr.7,

// DFFNDF-T,DFFSFDT-256,PACK-F2

// PROGRAM

NAiE-DCP2O9,ilRTilAX-T,DFFHTERN-7,

DFFNDF. T

,

DFF5 FDT.256,

PACK-F2

// PROGRAM

IAiE.DCP2IT,tsRIMAX.T,DFFHTERM-7,

DFFNDF_7

, OFFS FDT-?56,

PACX-FZ

// PROGRAT

NAXE-DCP2I8,TRTilAX-T,DFFMIERM-7,

DF FNDF-

7

,

DFF5FDT.25A,

PACK-

F2

// PROGRAT

IATE-DCP2I9,iRITAX-7,DFFMIERil-7,

DFFNDF-7

, DFFS FDT.25E.

PACK-F2

// PROGRAil

TAME_DCP22O,hRTMAX-7,DFFXTERM.7.

DFFNDF_7,

DFFSFDI-258,

P ACX.

F2

DFFNDF-7

,

DFFSFDT-25E,

PACK-F2

// PROGRAtr

NATE-DCP2IO,TRITAX-T,DFFTTERM-7,

DFFNDF-7,

DFFSFDT-25A,

PACK.F2

// PROGRAF

ilAMFDCP?tI,flRTiAX.),DFFXT€RT-7,

// DFFNDF-T,DFFSFDT-25E,PACK-F2

-// PROGRAE

NAilE-DCP2I2,NRTNAX-7,DFFiTERM.7.

DFFTDF-7

, DFFSFDI-25A,

PAC(_F2 O

// PROGRAi

XATE-DCPzIJ,TRTilAX.7,DFFflTERil-7

DFFNDF-7,

DFFSFDI-25E,

PAC(-F2

// PROGRAi

NABE-DCP?I4,ilRTtrAX-7,DFFiTERr,7.

DFFNDF-7,

DFFSFDT-25S,

PACK-

F2

-// PROGRAil

NAT€-DCP2I9,iRTtrAX-7, DFFilTERT-7.

DFFNDF-

7

, DFT5FDT

-25 ,

PACX-

F2

// PiOGRAM

NATE-DCP?I6,iRIMAX-7,DFFilT'Ril-',

// PROGRAil

NATE-DCP22I,rRTrAX-'IDFFMTERN-7,

DFFNDF-7

,

DFFS

FDT.Z5E,

PACK-F2

// PROGRAfr

NAME-DCP222,ilRIilAX-7,DFFTIERr.7,

DFFN DF_7,

DFFS

FDT-25E,

PACK.

F2

// PROGRAT

NAilE-DCP22],trRI[AX-7,DFFtriERX,',

DFFNDF-

7

, DF FSFDI-

25A,

PACX.

F2

Figure

18

(Pan

6 of 8). ccp Assignment

set Listing for Exampre-s7O4-sc2

onry

216

DFFNDF.T

I

DFFSFDT.256,

PACK

-

F2

// PROCRAM

NAI€-DCP225,ilRTrAX-T,DFFTTERH_7,

// DFFNDF-T,DFFSFDI-25E,PACK.F2

/ / ? ROGRAT

f AiE-DCP?25

Ifr

RTNAX-7,

DFFHTERi-7

-

./ DFFNOF-T,DFFSFDI-z5A,PACK-F2

// PROORAM

NAH€_DCP227,ilRIilAX.7,DFFXTERN-7,

DFFN DF-7, DFFSFDT-258,

PACX-

F2

// PROGRAil

NIflE-DCP226,iRTrAX-7,DFFiTERil-7,

DFFNDF-7,

DFFSFDT-258,

PACX-F2

// PROGRAX

NAXE.DCP229,TRITAX.7,DFFilIERM-7.

DFF{DF-', DFFS F0I.256, PAC(.FZ

// PROGRAN

NATE-DCP23O,MR]frAX-7,DFFiIERil-'.

DFFNDF-7

,

DFFS

FDT-258,

PACK-F2

// PROGRAi

NAiE-DCP2JT,trRTXAX-7,DFFfi]ERil-7.

// DFFNDF_T,DFFSFDT_258,pACX_Fz

// PROGRAT

NATE.DCP252,iRTTAX.7,DFFiTERil.7,

DF'NDF-7, DFFS FDT

-256, PACK-

F2

// PROGRAtr

NATE-DCP23],ffR]HAX,',DFFilTERil_7,

DFFNDF-

7

,

DFFSFDI-25E,

PACX.

F2

// PROCRAM

NAiE.DCP2Sq

, iRINAX-7 ,

DFFFI

ERr.7,

DFFNDF-7,

DFFSEDT

-258, PACX-

F2

// PROGRAil

NAilE-DCP2J5,XRTffAX.7,DFFMTERfl-7.

OFFNDF-7,

DFFS FDI

_?5E,

PAC(.

F2

// PROGRAfr

XAIE.DCP2]6,ilRIilAX.7,OFFNIERil.7,

. DFFNDF.7,DFF5FDT.25A,PACX-F2

// PROGRAts

NAi€.DCP2]7,rRIMAX-7,DFFr]ERX.7,

// PROGRAN

NAIE-DCP239,ilRTrAX.7,DFFiTERN,7,

DFFNDF.7,

DF FS FDT.25E,

PACK.

F2

// PROCRAH

XATE-DCP24O,ilRTilAX-7,DFFBTERil_7,

DFFNDF-

7,

DFFS FDT,25E,

PACX- F2

-// PROGRAM

TAME-DCP24I,rRTilAX-T,DFFFTERI-7.

// PROGRAi

NAilE.DCP2JE,TRTilAX-7,DFFNTERil.7,

DFFNDF-

7

, DFFS FDT-256,

PACK-F2

DFFilDF-7,

DFFSFDI

-258, PACK. F2

DFFNDF-

7

, DFFS FDT-25E

,

PACK-F2

DFFTDF-7

, DFF5 FDT-256,

PACK-F2

DFFNDF-7

, DFFS FDT.Z5A,

PACX.F2

DFFNDF- 7

, DFFSFDT-25A,

PACX-

F2

DFFNDF.T

, DFFSFDT-256,

PACX-F2

DFFNDF- 7

, DF F5 FDI-25A, PACK-F2

DFFNDF.T

,

DFF5FDT.25E,

PACK-

F2

DFFilDF- 7

,

DFFS FDT-25A,

PACK-F2

DFFNDF.7,

DFFS FDI

-256, PACX-

F2

DF FNDF-7

,

DFFSFDT-25E,

PACK- F2

DFFNDF-7

,

DT FSFDT-25E,

PACX.F2

DFFNOF.T

, DF FSFDI-25A, PACK-

F2

DFFNDF-7,

DFFS FD],256 ,

PACX-F2

DFFNDF-7

, DFFSFDT.256,

PACK-F2

// PROGRAM

IAtr€.DCP2{2,HRTMAX-7,DFFfrTERil-7,

DFFNDF-7,

DFFSFDT-25E,

PACK-

F2

// PROGRAT

NAtrE-DCP2qJ,TRTTAX-7,DFFilIERX-7,

DFFNDF.7,

DFFSFDI-25E,

PACK-

F2

DFFIDF-7

,

DFFSFDI.258, PACK-

F2

// PROGRAM

TAME.DCP246,ilRTilAX.7,DFFMTERil.7.

-// PROGRAT

TAfrE-DCP244,rR]XAX.7,DFFMTERM.7,

'// DFFN0F-7,DFF5FDT-258,pAc(_F2

// PROGRAH

NAil€.DCP245,iRTTAX.7,DFFflTERN-7,

// PROGRAi

NAiE_DCP24t,XRITAX.7,DFFilTERM.7.

/, DFFNDF*T,DFFSFDT-ZsA,PACK.Fz

// PROGRAi

NATE.DCPz49,XRTXAX-7,DFFrIERtr.7.

DFFNDF. T

, DFF5FDT.2

5B

,? ACX-F2

// PROGRAtr

NAXE-DCP247,ilRTilAX-7,OFFXTERil-7,

DFFNDF

-

7

,

DFFSFDI

-25E, PACX-

F2

// PROCRAi

flAXE.DCP25O,TRTilAX.7,DFFXTERi-7,

DFFNDF-7

, DFFSFDT-25E,

PACX-F2

// PROGRAi

NATE-DCP25I,ilRTTAX-7,DFFiT€Ril-7

DFFNDF- 7

,

DFFS FDT.29A,

PACK.

F2

// PROGRAM NAiE-DCP?52,

fiRTNAX-7

. DFFfrTERM.T ,

// PROGRAil

NAfrE.DCP?5J,XRTiAX-7,DFFrTERX.7,

// PROGRAM

HAiE.DCP254,iRTMAX.7,DFFilTERX-7,

DFFNDF.T

, DFFS FDT-?56,

PACK-F2

// PROGRAtr

NAil€-DCP255,XRTilAX-T,DFFNTERi-7,

// PROGRA[

TAME-DCP256,iRTTAX.7,DFFiTERil-7

// PROGRAT

TAiE.DCP25T,TRIXAX-7,DFFXT€RF-7,

// PROGRAil

NATE.DCP258,trRITAX-T,DFFMTERT-7,

// PROGRAN

NAilE-DCP259,TRIilAX.7,DFFrTERi.7,

// PROGRAI

NATE-DCP26O,MR]frAX-T,DFFiTERN-7.

// PROGRAM

TATE-DCP26I,XRTilAX-7,DFFNIERN.7

DFFNDF-7,

DFFS FDI

-256, PACK.F2

// PROGRAT NATE-DCP25Z,TRTilAX-T,DFFTTERT-7,

// PROGRAi NAiE-DCP265,ilRTFAX-7,DFFMTERil-7,

DFFIDF-7

, DFFS

FDT-25E,

PACK.F2

// PROGRAT

NAilE-DCP26',MRTilAX-T,DFFXTERT-7

// PROCRAT XANE.DCP265,iRTilAX-7,DFFilIERM.7,

// PROGRAX

NAHE-DCP256,TRTTAX-7,DFFXTERM.7.

DFFNDF-7

, DFFS

FDT-256,

PACK.

F2

DFFNDF-7,

DFFSFDT-258,

PAC(-F2

// PROGRAM

NATE.DCP269,XR]ilAX.7,DFFrIERr-7.

// PROGRAil

NAFE-DCPz67,iRTXAX-7,DFFiTERil-7,

DFTNDF-7,

DFFSFDT

-256, PACX-

F2

// PROGRAff

NAXE.DCP266,iR]XAX-',DFFilTERr.7,

DFFNDF-7

, DFFS FD].25E, PAC(-F2

// PROGRAM NAME-DCP2TI,XRTiAX-7,DFFrTERfr-7,

DFFNDF_7

, DFFSFDT

-25A, PACK-

F2

// PROGRAfr

flAiE.DCP272,ilRTTAX-T,OFFiTERi-'.

-// PROGRAT

NAfrE-DCP27O,MRTTAX.7,DFFilTERM-7,

DFFNDF-7

,

DF F5 FDT-258,

PACK-F2

-// PROGRAE

NAiE-DCP2'3,TRIiAX.7,DFFNTERr.7.

DFFNDF-

7

, Df FSFDI-

Z5E,

PACK-F2

DFFNDT-7

, OFFSFDT-256,

PACX-

F2

// PROGRAN XAXE-DCP275,TRTtrAX-T,DFFiTERi-7.

DFFIDF.-7

,

DFF5FDT.2

58,P ACX-F2

// PROGRAi

NAi€-DCP277,iRTXAX-7,DFFfrIERH-7

// PROGRAT

NAfr

E.DCPz74,ilRTTAX.7,

DFFNIERtr-7,

// DFFNDF-7,DFFSFoT_Z5E,pACK_F2

// PROGRAtr XAEE-DCP275,TRTiAX-T,DFFTIERX-7,

DFFNDF-7,

DFFSFDT-25E,

PACX.

F2

// PROGRAT

NAFE.DCP27E,[RTflAX.T,DFFiTERX-7,

,' DFFNDF.T,DFFSFDT-256,PACK_F2

// PROGRAM

XAIE-DCP279,iRTiAX-7,DFFITERil-7I

DFFXDF,7,

DFFSFDT-25E

,

PACK-

F2

// PROGRAtr

IANE-OCP2EO,iRTNAX-7,DFFXI€Ril-7,

// DFFIDF-7,DFFsFDI.z5E,

PACK-Fz

// PROGRAT

dAI€-DCP2EI,NRTfrAX.7,DFFXTERi.?,

// DFFXDF-/,

DFFSFDT-25E,

PACK.Fz

// PROORAT

NANE-DCP2E2,ilRTNAX-7,DFFrTERil-7,

DFFXDF-7

, DF FSFDT_25E,

PACX-

F?

// PROGRAT

dAilE-DCP2EJ,MRTXAX.T,OFFiIERT-7,

DFFHDF-7

,

DFFSFDT

-2 56

, PACK-

F2

// PROGRAil

XAilE.DCP2E4,TRTHAX-7,DFFfrIERT-7,

DF FNDF-7

, DFFS FDI-25E, PACK-

FZ

// PROGRAF

NAIE.DCP2E5,frRTiAX-T,DFFTTERE-7,

DFFNDF.T

, DFFS

FDI- ?5E,

PACK.

F2

// PROGRAM

NAME-DCP2E6,fiRTXAX-7,DFFXTERfr.7,

// DFFilDF-T,DFFSFDT-z58,PACX-F2

/,/ PROGRAT

NAtrE.DCP2ET,iRTTAX_7,DFFfrTERi,7,

// DFFTDF-7,DFF5FDT-?5E,pacK-Fz

// PROGRAtr

NATE.DCP28E,fiRTTAX-7,DFFillERi-7,

DFFNDF-

7

, DFFS

FDl_2

5E,

PACK-F2

// PROGRAil

IAilE-DCPzE9,frRTilAX-7,DFFilTERil-7,

DFFNDF-

7

, DFFs

FDT

-256, PACK-

F2

// PROERAN

NA'E.DCP29O,NRTfiAX.7,DFFrTERr-7,

OFFNDF-

7

, DFFS

FDI

-258, PACK-

F2

// PROGRAi

HAME.DCP2gI,ilRTiAX-T,DFFNTERI-7,

DFFHDF-7,

DFFSFDI-256, DACK-FZ

// PROGNAfl

NArE.DCP292,ilRTiAX*7,DFFi]€Ril-7,

,/ OFFNDF-T,DFFSFDT-256,pACX-F2

// PROCRAT

NAffE.DCP29J,TRTXAX.7,DFFilIERil..7,

./ DFFNDF-7,

DFFSFDT_256,

PACK_F?

// PROGRAF

IAilE-DCP294,trRTHAX.7,DFFNTERr-7,

// DFFNDF-T,DFFSFDT-25A,PACK.Fz

// PROGRAN

IAf,E-DCP295,FRIMAX.7,DFFrTERts.7.

DF FNDF-7

, DFFS

FDI

-25E, PACK-

F2

// PROCRAi

NArE-DCP296,iRTMAX-7,DFFITERi.7,

DFFNDF.7,

DFFS FDT-25E,

PACX-

F2

// PROGRAN

NIilE.DCP297,IlRTiAX-7,DFFN]ERil.7,

lr' DFFNDF-T,DFFSFDT-258,PACX.F2

7/ PRO6RAi NAFE.DCP29E,TRTTAX.7,DFFilTERil-7,

r. DFFTDF_?,DFFSFDT_256,F,ACK_F2

-// PROGRA!

IAilE.DCP299,XRTTAX-7.DFFTTERM.7,

DFFNOF-7

, DFFSFDT-256

, F ACK-

F2

// PROGIAtr

flA!E-DCP5OO,rRTXAX.7,OFFrTERil.7.

DFFNDF-7

,

DFFS

FD,

-25A, P

ACK-

F2

// PROCRAfr

IAME-DCPJO1,NRTilAX.7,DFTITrRX-7,

DF

FNDF.7

, DFFS

FDI

-25E, PA

CK.

F?

-// PROGRAM

iAME-DCP5O2,NRTNAX.7,DFFffTERT-7,

DFFTDF-7

, DFFsFDT-2

5A, PACK.

i2

// PROGRAil

NAilE.DCPJOJ,IRTFAX.T,DFFTTERff-7,

" DFFNDF_Z,DFfSFDI-Z5E,PACK_F2

// PROGRAil

NAilE-DCP]Oq,NRIfrAX-7,DFFTTERT.7,

DFFNDF-7,

DFF:FDT-256,

PACK-FZ

// PROGRAM

fArE-DCP]O5,TRTilAX-7.DFFITIRil.7,

// DFFNDF_T,DEFSFDT-25a,pACK_Fz

// PROGRAh

NAfrE-DCP3O5,ilRIrAX-7,DrFhr€Rfi.7,

DFFNDF-

7

,

DF FS FDT

-

258,

PACK.

F2

// PROORAE

NAfrE-DCP]O7,MRTilAX-7,DFF[rERF-7,

// DFFNDF-7,DFF5FDT-?5A,PACX.F2

// PROGRAT

NAHE-DCP5OE,fiRTfiAX-7,DFFfiTERil.7,

DF FIDr-

7

, DF F

5 FDI

-

256,

P

qCK_

F2

// PROCRAi

!AII-DCPJOg,NRTflAX-7,DFFNIIFil-7,

DF FN

DF-

7, DF F5

FDT-

256, PAC(

-F2

// PROGRAN

NANE-DCP]IO,ilRIfrAX-7,DFFil]EFil.7,

DFFI

DF-

7

, DFFs

f

DT_

2 5E

,

PACK-

F?

// PROGRAN

IAfl

E-DCP]II,XRTrAX-7,

DFFTTERh.T,

.. DTFNDF_7,Dff5FDT_?'6,PACK_FZ

// PROGRAfr

IAXE-DCPJl?,iRTTAX.7,DFFFIERil-/,

// DFFIDF-7,DFF5FDT-256,PACX

F2

// PRO6RAi

NAtsE-DCPJI],TRTHAX-7,DFFM]ERX.7,

// DFFNDF-7,DFF5FDT-258,?ACK

F2

// PROCRAil

NAfr€-DCPJI4,MRTHAX-7,DFFilTERM-7,

FFNDF-

7

, DFFS FDT

-256,

PI

CK

-

F2

// PRCGRA[

IAiE-DCP]I5,NRIilIX-7,DFFf;TERr.7,

FFNDF-

7

1

DF F5

FDT

-

I5E, PI

CX. F?

// PROGRA[

NATE-DCP316,ilRTTAX*T,DFFIItRH-7,

// DFFNDF-7,LIFF5FDT-256,p!qK

Fz

// PROCRAI

NAIE-DCPJIT,ilRTTAX-7,DIFITERr,7,

DFFilDF_7,

!'F5FIT-256, PACK-F2

// PROGRAN

NATE-DCPJI6,ilRITAX-7,DFFilTERX../,

'. DFFNDF,T,DFFSFDT-258,PACK

F2

// PROGRAff

NAIE_DCPJI9,ilRTilAX-T,DFFATERX-7,

" DFFRDF..7,DFFsFDT-?58,PAC(-F?

// PROGRAfr

NAilE-DCP]?O,IRTMAX-.TIDFFMTERX'7,

DFFNDF_

7

, D F FS

FDI. 2 5 6

,

P

ACK-

F2

// ?ROGRAT

NAffE-DCP3?I,rRTrAX-T,DFFrTERd

7.

,/ DFFNDF_7,oFFSFoT

_?56,

pACK

Fz

// PROGRAfr

NAilE-DCP]22,rRIilAX-7,DFFffIERX_7,

/, DFFNDF.TIDFF5FOT-25E,PA:K_F?

/,/ PROGRAts

NAHE-DCPS2JITRTiAX-7,DFFMTERX.7,

.. DFFNDF-7,OFF5|DI_25g,PA)K-F2

// PROGRAN

NAil€-DGPJ24,NRTIAX.7,DFFdTERil-7,

'/ DFFNOF-T,DFF5FDT-Z58,pAr)X_FZ

// PROGRAil

IAIE.DC?J?5,ilFTIAX,7,DFFiTERN-],

,. DFFNDF.T,DFFSFDT-256,PACK-F?

// PROGRAfi

IAts€-DCP526,ilRTIAX-7,DFFrIERil.7,

// DFFNDF.T

, DFFSFDI.?5E,

PACr-,2

// PRAGRAN

NAilE-DCP327,NRTTAX-7,DFFTTEPi.

/,

// DTFNDF-7,DFFsFDT-z5E,PA(J(_Fz

_// PROGRAM

IArE-DCP]28,dRTilAX-7,DFFilTERfi.7,

,. DFFNDF.T,DFT5FDT-256,PACK-F2

// PROGRAfr

NAfrE-DCP329,TRTilAX-T,DFFTTERT-7,

'. DFFNDF,T,DFFSFDT_Z58,pACK

Fz

// ?ROG?AB

NAilE.DCP]JO,TRTFAX.7

,

DFFNIERfr-

7,

Figure

18

lPartT

ol 81.

ccp Assignment

set Listing

for Exampre-s704-sc2

onry

-// t'RaGPA4

Niit.j)cpJlt Iiir,,i r,r-.ifraits /,

r/ DFftLF i,DFFlfDr 256,pAaK_F2

/,, FR0GRAil

Niii-ac9il2,{qTh/.x 7,!iFttEi4,l.

;/ :trFtDi 7.DFF5|ltl,?5s,PAc(-f:

// PR0GRAh

hAnt-Dcplll.xRitrax.r,DFthIEFt /,

IFFIDT 7,DFF5I

DT.:56,P

AC<,F?

// Pk0cRAfl

f;Ail€-Dirll4,iRlh4/ /,rF,f,itFr-)

0FFNDa..7,!i.3rDl 25Z,oACN.

F?

// PR0GRAil

NAn€.!cptl5,fr:t*rt T,trFriIEefi_,

// DFftuF_7,DFt5irT-2r3,tacK

F2

// PR0CRAH

NAt[-DCp]36,rRttit-/,!afErERr 7,

// PROGRAh

NAhE

DCPJ45,I?IEIX-],J]iIITERil-7,

// l)rfliF-l,Drrcall ?58,pAc( F?

// PR!GRAi NAhE,DCP]4b,IRi1A:./,D,

FTlFFE

r

tFtNDF-r,

f f i5iDl,?5a,f acK F?

// pR0cRAr

tAts !af1lr,!nrdix,7,!itiriifl 7.

/t r)rFNDi-7,Dtria:jl 216,tACK-r?

// PR0GRAX

fiAr5 taptlb,ilitft/-1,ltrttsr,aF r,

.. DFFNDF-7,tf

F:[|T_258,PAC(.F2

7/ PR!r.Rlx AAhE

f,aFttg,NFriax /,uaFf-Etr_r.

tr Ftlr-7,!r:s.DT :5e,r

Ac{ F:

// PROORAT

NAIi:.DCP](O,ilRIIA'-7,DFFITER4 ].

,, taFrli r.DtisFtl.253,P{CK-52

/ / P

RQGRAT NAXF-t)Cp

j4 i,ftrit tr,1 /, !i rrtf Fn 7.

// DFIIDF ].I]FFs[D].2,E,PACK-F2

// PR0CRAil

ttfE-DaFlq?,f1.r'f\)i T,iFFftlfRf 7,

,. Dalrr, 7,D[F5fU]_l5a,PAC(.F2

// PR0GPTN

NAfl[-ncp]4t,rRrilAl T.DrFfrLiix r,

., lrfFND; l,r)FFSrDr 258,PAC( F2

// PR0GRAf

NA(E DCpl4l,fninrX.t,DrimrtRF :,,

DF

FNDF,7

, !FI5f !T

-258,

PAC(.FZ

// PROCRAH

NAN[,LiCP](8,{RJNAX.7,DI

FtsTLRr

7,

// tFi:tDF,7,DFF5FDT

25B,PACK

FZ

// PR0GRAil

tLtrE-Dt_pl49,lRIXAX_7,!iFfiiRx_7,

Df f

NDF

-

t.

DrFSFtT 25t, PAa(-F2

// PP0$RAr

\AnE-0cpt17,rRiFAr, /,DFfdr[11 7

DFFNDF.T,D[':FDT

256,PACK.F2

DFtrt. 7,t

FF5rDt

-:5A,PACK

Fl

// PR0cRAr

NnilE

0Cplti!,rirxnr t,f,FFfiT!R1.7,

,. IIFNDI T,DFFS'Di.2,E,PAIK-F2

// PR0CRAt

NAtE DCrrl5L,{R

'tix 7,

!iiriatrrf;_7.

,. i)fltri-?.tff5Fli:]IE,PACK F2

// pR0aRAts

ttri.D^rt5?,!;ittA!t 7,0FtntFR!. 7,

// Dir!f,r r,DFFi:l)r -ti8 :Ct(_F2

// PR00RAd

NAit,DCpJ5l,ffkrr!x 7,t)ftntfRi r,

DF ! ri

!rF-

t , D

F

r

5

F

0i -:: S

,

pAC

K- F2

tlf \!F -l DFFSFDT

-25E,

PAC(.

iI

JFFNOF

7,D;F5FDI

256,PACX-RI

D

F

FNDF.7

, DF

F5

FD:.

?56

,

PACK-R

I

// PROGRAi

IAIE.DCP362,ilRiilAX./,DFf

flTERM.7

DFi

lDF-

l, Llf FSf

iT 258,

PAC{-Rl

// PRg6RAtr

NAtsI_!CP363,rRTXAX-7,DiFilIERi-7,

/.. a

'F|DF-r,DFFSrDT_?58,PiCK_Rl

// PR0GRAt

NAiE-DCp)64,mRInrX 7,!FriltEFd_7,

!aFrDF

r,!FF5!Dl-258,PrC(-Rl

// PROCRAil

NAflE.D'P365,TFJNAX.:,Di:FiJFRi.7

DFF{0F-r

, 0cFsrDr 25a, PAC(

,R1

/, pR0Gtlr fl

^r.. tcplr,6,

tRlhax-?, 0FFDt

FRfl

-7

DFINDF

/,DTFSFDI,25E,PAC(-R1

// PROCRAM

NAhE-OCPI67

ffRTf,4I-7,!FFNIERh,T

i]

F

FNDF

-

7

, DF

F5

FDT

-

2

5E

,

PA

C(-R I

// PROGRAfr

IAtrE

DCP]6A,IJRIrIX.7,DFrilIE!N-7

DFFNDI./,!IJFSFOI 2:3,PACK.R]

// PR0GRIil

NAiE-!Ctl69,rRT(4X-/,DFFilrIRt 7

DFFNDF-i

, DFFSFDT-?58,

TACK

RI

// PROORAil

NAilF

DCPITC,NRiilAX

i,DFIil]ERfi -

IFf !DF 7

, DCFSFDI

_256,

P!CK.R

// PROCRAH

NAfiE.9CP]]I,IRIMAX-;,DFFffrERH.7

i]T:FNDF

7,DFF5ID' ;]'8,PNC(,R1

// PR0GRAT

NAn[ 0cp]/2,hr||AX T,DFFriLRr-7,

I.FNDF-/,DrFSFDI

-?5t,PAC(,Ri

// PR0GRAn

{AD[-DCF37],tsNlrix t, lrFFtlTtRE

r

DFFIDF-'

, !I F5F

D

r ?5E, PACK-R]

// PROGRAN

NAilE-DCP374,ffRTiAX.7,,rFfrTEAi-7

!

F

d

tF- i , D. F

5

F

n t

-

? 5n

/

P

ACr_

E l

// PROCRAM

IAIE DCPJT5,TRI[AX-T,DFFMTIRI

7

DFFNDF.T

,

DI

F5 FDT.

258

,

P

ACK.

R I

// PROGRAN

IAflE-!CPJ76,ilRINrX-7,DFFNTERi.,,

DFFNDF-7,

DFF9FDI-?58,

PTCK

RT

/ ) tPockaN fl

aHE-DCp177,Hp

rFA/.

7,

Dtr1rtcil.7,

LrrF!0i 7,

!FF5fDI-?ta, PAC( Ri

// PROCRA[

NATE.DCP])6,ilRT[AX

7,!FFhIIPil 7

N'FSDF-7,DFF5TOi

;5E,PACK

R1

// PROGRAtr

NAil€-DCP579,FIRTilAX-7,DFFffTERT,]

DFENDF.;

, DFF5FDI.256,

PAC'

,

R

I

// PR00NAr

NAfrt

f,.p'51,f;jfia!,?.Dflf1t!iif, t,

" DFF{DF

7,lFi

5fUt z5a,PAaK

F?

.,/ PROGRAil

HAilE-DCE,15J',Mi1ilAX

7,'FFilTERC

7,

rif dDF-

i.

f;iF!rDT.2r8.

pAC(_Rl

// PR0GRrfr

tAiE ttpi56.flRTnrx,,,r.FFf; ,tEil',

-// PROGRAi

NAffE

DC'J57,MRifiAX

/,DFTMrERr,7,

,/ D|F\DF

T,DrFSrti Z5a,PAC(

Rl

// PROANAfr

NANE

OCP]5E,rRII'At 7-DT,HIERX-],

// PR0GRAT

NAne

D(i!l59,tirtAX 7,!FaniERT 7,

Il DfFNDF

7,DFFSFDI

Z5E,PACK

RI

-// PROGRAN

NANT

DCP]6O,TRTIAX

T,DFFhTTRi.7,

// pR0cRAn

NArt-Dcpl6l,MRTFAX-r,orrrritr:i,'- "''''^

// P(OGRAh

IAtsE-DCP]8O,HRTilAX.7,DFFMTEFT

7.

.' DFFNDE.T.DFFSFDI

?'6,PAC{_R]

// PROCRAN

ilAfiE-DC?5EI,tsR]frAX

T,DFFTIERd 7,

DFFNDF

TIDFF:FO1

256,PACK

R1

// PRA6RAN

NAME-DCP]A?,HRTffAX.7,Drril.rIRr-7

DFFNDT

7,DiF5FDT

256,PiC(-Ei

conf

iguratiorr

Limitations,

storage

Estrmates

and

perf

ormance

cons

jcerations 217

-// PROCRAM

NIiE-OCPI69,ilRTXAX-T,DFFTTERX 7,

-/r' DFFhDF,T,DFFsFDT_Z5E,PACK-RI

,,' fR0GRtil

!Af€ DCt'l90,fRrflax-7,oFFhTIRn 7,

// DFFNDF-7,DFF5[DT.258,PACK,RI

// PROCRAT

NAilT !'F]9I,I:RIAAY ',OFFflT!RM

7,

// DFFNDF-T,DFISFDT

256,PACK.Rl

.// PIICRTil IIil!-DCP]9?,fiFTXAI / DIFfllERH 7,

Df FNDF T,OFFSFDI-256,PACK,RI

,/ ?KI)"FIAT

N^TL'.D'f]9I,TRIIAX 7,!FFtsTEFil

7,

// DFFND[-7,DFF5iDT

256,PACK.RI

// ?PDCRAtr

N/INi,'CFJ'4,ilRTtrAX /,ITFilIERM,7,

// AFFNDi.i,DFI5FDT

Z56,PACK.RI

// P\ea?Af;

l;'f,i DCll95,rRiilAX-t,DFtrtERfl 7,

LF

FNDF

-

/

, DF i5 'DT.2

58, P ACK.R

i

// PqA'RAf NNNL.DCP]'6,TRIf;AX

],DFFilT€RN./,

DFFIOF.],'FF5FD1 256,PACK.RI

// PPNCRAT N].frE

D'P]97,NRIEAX-T,DFFHIERM

7,

-// PROGRAT

IAME-OCPJ86,ilRISAX-T,DFFTIERM-7,

// JFFNDF.7,DFF5TDI,256,PACK-RI

// PROGRAil NAME-DCP]37,TRIilAX.7,DFFHrERM-7,

// DFTNDF-7,DFF9FDI-258,PACK

RI

// PRAGRiil l/\nE-DCF368,fiRrHAX-/,DFFMTERfr-7,

// PROGRAM IAXE.DCP]Eq,iRIfrAX-./,DFFilTERil-7,

'' bFTNDf-7,DFFsFDT,z5A,PACK.RI

// PROGRAT

dAiE DCPJA5,NRITAX.T,DFFilTERi-7,

DF

FNDF.7

, DF F5 FOI.258

,

PACK_R

I

D F FNDF_

7

,

D F T

5 FDI.258, PACK,R

r

,I FNDf /,Di:F5FDT_25A,PACK_RI

FILO19/IS,

FILO2OlIS, FILO2I/I5,

FIt022/IS,FtL023/t5,FIL02(/IS,

F 11025/15,

F 11026/ t5, FrL 027lIS,

FIL02A/I5,FI1029/IS,FIL050/ls,

FI

L O ] I

/

I5, F I L I12l I

OUlNO5I

R ,

FtLllS/I0ulr05fr R, FlLll4/I0u/N05f R,

FILl 15/IOU/NOSHR,

FILI16/IOU/IO5HR,

FlLltT/I0u/N05HR, FtLl l6lI0U/N0sHR,

F

I I1I9/ I OUlNO5HR, F I

L

12 O/

I OUlNOS HR,

F

I L 12I

/

IOU/NO5HR

,

F I L I22l I OUlNO5HR,

F

I L I2Jl I OUl!OSHR, FI L

I24l I OUlNO5HR,

FIL125lIOU/NO5HR,

FILI26/IOU/NO5HR,

FILI27lIOU/TOSHR" PGilDAIA-dO

FIL0l5/I5,FIt0l6/15, FIL0J7/Is,

FIL0ta/I5,FIt0l9/I5, FIL040/IS,

FIL041/I5,FI1042/IS,

FIL0{l/IS,

f

It044/I5,FIt0(5/15, FlL046/I5,

F

t

L041

/ L5, Ftt t2a/ \ oulN05HR

,

alLl29lI0u/N05HR, FILll0/I0U/N05NR,

FILISI/IOU/NOSHR,

FILl]2/TOU/HOSHR,

FILtll/r0u/r05HR, FtLl3{/ r0u/il05HR,

FlLll5Tl0u/N05HR, FrL r l6ll0u/r05HR,

F

I L I J 7/ I0U/ d0 5NR,

F

I L I t6l t 0Ulr0sdR

,

FILII9/I0UlN05f R,

FIL

i40/l0U/!05HR,

Fltl4l/I0u/N0sHR. iILl42lI0u/r0sNR,

FI

L

T { ]/ I OUlNOSHR' ,

PCTDATA-

NO

FIL051/t5,

FIL052llS, FILC5I/Is,

F

!t054

/ 15,

F

It 055/ 15, FtL056/IS,

FIL057l!5, FIi05A/15,FI1059,15,

FIL060/I5,FIL06l/I5,F\1062/

t5,

FIL06l/I5, FIL

l4(/I0U/N05HR,

F

I

L

I45l I OU/IO5HR ,

F

I L !

4

6/ I OUl

N

O5HR

,

F

I L 1(

7/

I0U/r0 5HR,

FJ

I t

46/

I0U/

N05HR

,

FIL

i(9/IOU/NO5HR,

FILI5O/IOU/IO5NR,

FILI5I/I0U/H0SIR, FM52lI0 j/NC5|R,

FILl5l/l0u/N05BR. FtLl5(/t0U/N05f R,

FIL

155/I0U/N05HR, FILi55/t0U/N0Sf R,

FIL

t 57lI0U/N05HR, Fltl56/i0U/r0sHR,

FILI59/IOU/IO5HR"PGMDAIA-IO

FIL067/I5, FIL06E/I5,FI1069/15,

FIL070/I5,FIt0r1/I5,FIL0r?/15,

FIL07l/15,F1i074/t5,

FtL075lI5,

F

it01 6/

ts, r rlaT 1

/ ts, FlL078/rs,

FIr079lI5,FILl60/I0U/N05Hk,

FIL

l6l/I0U/N05HR, FILt62l I0U/N05f

q

FIL

I6]/IOU/NO5HR,

FILI6q/IOU/NO5IR

FILl65/t0U/!0SBR,FIt

166/I0U/NC5f

R

.ILI67,I0U/n0"hR,rII I6a I L/Nt5Fp

FILl69/l0u/N05HR, FlLll0/I0u/N0sHR

FItlTt/l0u/N05HR,

FtL172/I0!/N05HR

FlLt 7llI0uln058R, FIL

I

/4/ l0UlN05rR

FILI75lIOU/NO5HR',PGMDAIA-IO

FIt 06J/I5,FlL0Eq/lS, Flt085/tS,

FILO66/I5,FILOA7lI5,

FILO6E/I5,

FItC69/IS, FIt090/I5, FtL0rl/I5,

FIL092/I5, FlL093/IS, FlL09q/I5,

FILO95/I5,

FILI76/IOU/NOSHR,

FiL 177lI0U/NC5HR,FIL176/I0U/N05f

R,

Ftr

179lI0u/N0sfR,FILIE0/t0u/r0:8R,

FII i6I/IOU/NO5BR,FIL1E?/10!/NOSHR,

FlLt6l/I0u/N05HR, FiLla4/t0ul!0sHR,

FIt 165/I0U/N05HR,

FIL!86/l0U/r05HR,

FILlA7/I0U/N09ltR, FILlaa/l0U/!CSHF,

FJLI89/IOU/NO5HR, FILI9O/IOU7NO5HR,

F

I L I9Il I OUlNO 5HR

"

PGNDA

T A

_

N

O

// PROGRAM

ilAilE.FLI92C, FILE5.

I

FItOI2/I5, FITOI]/IS, FTLOJ(/I5

// PRCGR!f N;ffI-DCP]9A,f;RTFA']

7,9FTIiERil 7,

:/ aialDl./,DFF5rDT

?56,PqCK_Rl

// ?FaaRAh

tr.f;E DaFJr9,f;RTilrx-T,tFFmrtRr 7,

// DFFIDF-

', DFF5FDT.Z56,PACK,RI

,/ IROCRAT

N/flE-DCT(OC,MRTffNI.],DFFtsIiRd

7,

:/ DFFNDF.T,DFIsIDT

253,PAC(

RI

// rtLcRix Nnmt !cf(cl,MRTtsax,t,DFFItERn 7,

// DFIIIF /,IFFSFDT 258,PACK RI

// PRaCRAn

hrrmt

LjCr(02,hRihrX T,DFfnTERF

7,

1/ IFFID'.i,DFI5FDT-256,PACK-RI

// ?F'LPAT NNfri.DCi(O],iATTAX.T,DFFNTERF

/,

// PROGRAil HAXE.FLI92D, FILE5-

I

FiLO(6/I5, FILO(9/15, FILO5O/I5,

// PR0CRlr NtnE DCpqca,iltTrax, i,DFFilttRh./,

// )FFNDF 7,DTFsFDI 25E,PACK

RI

// ?RA'RAfr NAiE DCP4O9,T!IiIX T,IFFIIERil 7,

/ / tj F r N

! i - I , ! F F

5 | ! T

- 2 5 6 , P A C K

_ R 1

/7 PROiPAN NAfiE-DCI4lO,iRIilAX.?,DFFITLRN

7,

// DFFIDI 7,DFF5FDT

258,PACK,R1

// PR0aRrfr

tlffr,rcp(li,trtrnAt. T,DFrf;TtRn

7,

// DiFTDF-7,DFF5[D] 258,PACK_RI

// Pi\cRAr, !/,tsE DCp4l? tFtts^r 7,!t:FfllERn_7,

// bfINDF 7,DFFsFDT

?56,PACK

RI

// PR0lRli dnIE DiFqlJ,tttMAX T,DFFfTERil

7,

// IFFNDF.T,DFFSFDT-?56,PACK-RI

// iROORAI rinFE

Dap4l<,rR]fAX 7,!FFdTERM-7,

,/ DIFNDI 7,DFF5FDI-Z56,PACK-RI

_// PR0CRnt

trxi Dct{l5.rRrMAX /,ltFFfTERh-1,

)FFN!fr-

i,!F[5':Dt 25a,PACK-Rl

// PRi6RIM NNIE DCP4O4,IR]NAX

7,DFFM]IRfl-.7,

// 'FFIDF./,DiF5FOT.25E,PACK.RI

// tR!cRAm \nnt-Dcpq05,htItsAX-7,0aFxTERfr

7,

DIFIDI 7,3FF!FDI

?56,PACK,RI

,-/ PRCCPAn !,1n1

9ap406,Tqlilx /,!pFtrrERr t,

// f;cltDr-7,DFF5|DT

25a.PACK_RI

,// PR!CRlI fintsE

DCp40i.ilRTilix-T,DFFHTtk[ 7,

DFFNUI

7,DFF5FDI

25A,PACK.RI

DFFNDF 7,DFF5FDT-?56,PACK-RI

/r' ?PQlttn rrtilE Diplli,fRIrAX 7,0FfflTLRd 7,

,/ AFFNLF ],DFFsFDI

Z5E,PACK RI

// Pk0aRAr \nIr DCP.:17.tlRimrX

T,DFFfflLRm-7,

IF

FNDF.7

,

DF F

5 FDI

'25E

,

P

ACK.Rl

-// PR'CPAil NIfi! D'P(]A.ilRIIAX /,OFi:MTLRM

7,

i)FiNDF.I,

DFFSIJDT.25A,PACK-RI

// ?ROGRIT

NAHE-DCPqI9,ilRTilAX-),DFFil'ERM-7,

DFFNDF_ 7

,

DFFSFDI

-258,

PACX.

R I

,/ Pr0ca/h {rrr D,p.20,rpTildy

/,D,fMttRil./

9FF IDF.7

, DFFS

FDI'25A,

PACK

-R

1

// PP!CRAM

NITI.OCI42I,NRTtsAX.7,DFFflTEf;T

7

)FF!0F.7, DFFSIDT 258, PAcK..RT

// PRCGRAb

!AMi DCP422,NRIffAX-I,DFFITERM,/

DFFNDF- 7

, DF

FSFDT

.25A,

PA CX-R

I

Figure

l8 (Part

8 of 8).

// PR0CRAi NAmE-FLl92E,ftLES-tFIL064/I5, FIL065/I5, FIt066/lS

// PROGRAtr NAME-FTT92T, FILES-'FILOEO/I5,FILO6!/I5,

FILOA2/IS

// PROCRAIl

IAilE-DCIq2J,HRIHAx.T,DFFHIERtr

7,

// DFFIDF,T,DFFSFDT-256,PACK-RI

// PROGRAB

NAME DCP(2(,FRTfiAX.7,DFFhIERM.7,

// DFFNDF

7,0FfsFDl,Z56,pACX-Rl

// PROCRAI

NAII-DCPq25,iRIffAX.7,DFITTERM

7,

// DFFNDF-T,OFFSFDT

Zi6,pACK_Rt

// PN0GRTX

r;trri

-

5nL5t,FIits-' FIL5l7/15,FI1516/I5,FILSl6/I5,

/

/ FIlSt9/ \5 FIt

520/J5, f.11521/lS,

FILS22/t5,FIL5Zt/t5,FIL52q/75"

// PGhCAti-N0

// PR!5Rrh NAIt F(it2A,FILE5'FILC00/I5,FIL00I/I5,FIL002/IS,

FIL00l/IS,

FIL004/IS,FIt.005/IS,

FlL006/t5,Ft1007/I5t

FILO06/I5,

FIL

009/IS, FIL010/l5,FIt0ll/I5,

FlL0r?/I5,

FIL0ll/I5,FIt0l4/I5,

Fll

!15lI5,

F

I

L

0

97l I0Ul80SHi ,

F I t 0

96l I OUl NCSHR

,

FI

LO99/IOU/8O5HR,

FILIOO/IOU/NO5HR,

FIL

1 0tlI0u/N05H?, FM0Ult0U/NO5HR,

FI

L I 0l/I0U/N05hR,

FtLl 04lIOU/NOSHR,

FILI

O5lIOU/NO5HR,

FILIO6/ICU/NO5HR,

FILI

O7lIOU/NO5HR,

FlLIOA/IOU/NO5HR,

tIll09/I0u/N05Ht, FtLll0/I0u/N05HR,

FIL

ll l/l0u/105HR,, PGmDATA-NO

CCP Assignment Set Listing for Example-5704-SC2 Only

218

DISK

STORAGE

EST]MATES

FOR

THE

CCP

Space

occupied

on the production

pack

(pack

on'ccUNrl specified

in

$EGEN

generation

control

statement).

Ob

ject

Library:

Base

number

lf MLTA

supported,

add

lf BSCA

supported,

add

lf DFF

supported,

add

Source

Library:

Ca rd

less-generation

1 120

sectors

65

sectors

45

sectors

65

sectors

7

sectors

Total

Space

occ.tpied

on

a program

preparation

pack (pack

on ,ppUNlT,specified

in

$EPLG

generation

control

statement):

For

LANG-ASSEM,

198

sectors

in

source

library

For

LANG-RPGll,

g

sectors

in

object

library

For

LANG-COBOL.

2

sectors

in

ob.iect

library

For

LANG-FORTRAN,

2

sectors

in

object

librarv

Total

conf iguration

Limitations,

storage Estimates

and performance

considerations 21g

size

of

$ccPFlLE

(determined

from

specifications in

$EFIL

generation

control

statement

and

generation

statements

defining

lines and terminals):

Determine

the number

of sectors

per

assignment

set as

follows:

Start with one

sector

For

TERMS-n: 1

-

14 terminals.

add

3 sectors

15

-

22

terminals,

add

4

sectors

23

-

28 terminals,

add 5 sectors

29

-

42

terminals,

add

6 sectors

43

-

44

terminals,

add

7

sectors

45

-

51 terminals.

add 8 sectors

For

BSCA-n

($EBSC)

and

LINES-n

($EMLA):

Adcl

one

sector if the

sum

of BSCA-n

plus

LINES-n is

less

than

seven;

add two

sectors if the

sum of BSCA-n

plus

LINES-n

is

seven or

greater

lf

any

switched lines

are to be

supported,

add

one secror

For

DFILES-n,

add

one

sector

per

12 or

fraction

thereof

For PROGS-n,

add one

sector

per

5 or fraction

thereof

Total

I

220

Determine

the

space

for

a//

assignment

sets

by multiplying

the

total

above

by the

number

specified for

SETS-n.

To

this

product

add 39

sectors

for program

Number

S704-SC1

.

For

Program

Number

5704-SCl

only

Determine

the

number

of sectors

required

by each

storage

dump.

The

supervisor

and

the

CCp

partition

are wntten

to disk

whenever

a dump

occurs.

To

calculate

the

disk

soace

required,

1K

bytes

of main

storage require

four

sectors

of

disk

space):

1. Add

the

supervisor

size

to the

CCp

partition

st

ze.

2. Convert

to sectors.

3. Add

one

sector

to this

amount;

the

CCp requires

this

sector for the

header

record.

The

above

calculation

results

in the

number

of

sectors

needed

for

a dump.

For

Program

Number

5704-SC1

only

Multiply

the

above number

of

sectors

by the

number

of

dumps

specified

(DUMPS-n)

for

the total

number

of

sectors

allocated

for

main

storage

dump

space.

The

sum

is the

total

number

of

sectors allocated

for

$CCPF

I

LE,

conf iguration

Limitations,

Storage

Estimates

and performance

considerations 221

For

Program Number

5704-SC2 only

The storage

dump area

calculation for $CCPF

ILE

may

be

omitted for Program Number

5704-SC2.

The storage dumps

are

placed

in the main data

area file

($CCPDUMPI.

This

file

is

used

for tracing to disk

with the OCC

loadable CCP

trace; it is also used for storage dumps.

Note: Cardless-generation

procedures

as

supplied

require 20 tracks

for a

$SOURCE

workfile at

location 386 on

the CCP distribution

pack.

Size of $CCPDUMP

(determined

from specifications

an

$EF

lL generation

control

statement)

A.

B.

Determine the number of sectors

required by each

storage dump:

1. Multiply system size in K by

4. (This

yields

the

number

of records

per

dump.l

2. Add 1. (One

record/dump

is required as a

header

record.)

Multiply the

above

number

of records

by

the

number

of dumps

(DUMP$n)

specified

for the

total records

allocated

for the

main storage dump

space.

Convert the above

to tracks by

dividing

by 48 and

round up to the nearest number.

Add

the number of tracks

(DPTRAC)

designated

for use by trace.

Add

one track

(this

track

will be used

as directory

space).

c.

D.

E.

Work file

space

required

during

generation: Three work

files

are

used, the

filenames and the sectors

required

are:

For

$SOURCE.

4080

sectors

For

$WORK,

1200

sectors

For

$WORK2,

1200

sectors

Total

222

TIPS

FOR

IMPROVED

PERFORMANCE

AND

MAIN

STORAGE

UTILIZATION

This

discussion

is

intended

as

a

summary

of techniques

for

improving

CCP

performance

(response

time)

and

CCp

main

storage

utilization.

ln

some

cases,

techniques

for improving

CCP

performance

result

in increased

use

of main

storage.

On

the

other

hand,

techniques

for saving

main

storage

space

may

result

in somewhat

slower

performance.

The

proper

balancing

of these

two factors

for

a

particular

installation

depends

on

the

apprication

requirements

of the

instailation

and

the

hardware

resources

available

to the installation.

Analyzing

the

application

mix

of a

particular

installation

will help

determine

requirements

for performance

and

main

storage

utilization.

ln general,

applications

that

call

for

cpntinuous

and

prolonged

interaction

between

the

terminal

operator

and the

system,

such

as

order_entry

applications,

require

minimum

response

time

so

the

operator

can be

as

productive

as

possible.

lnquiry

applications,

on

the

other

hand,

might

not

require

such rapid

response,

because

operator

interaction

with the system

is

not likely to be

continuous,

and

operator

productivity

is not likely

to be

as

dependent

on

the

response

time

of the

system.

Thus,

when

the

predominant

type

of application

being

run

under

the

CCP

is

order-entry,

system

design

choices

can

be

weighted

in favor

of improving

response

time,

even

if it costs

main

storage

space.

When

the

predominant

type

of application

is inquiry,

system

design

choices

can favor

saving

main

storage

space.

Resident

Accept: The

ACCEpT

operand

of the $EFAC

generation

statement

specifies

whether

accept-input

operations

are

to be handled

by

code

resident

in

main

storage

or by

a

transient.

Resident

accept

(ACCEPT_YES)

'

reduces

transient

area

contention

and

provides

faster

access

to data. lt is

especially

effective

for single requesting

terminal

(SRT)

pregysm

type

operations.

Resident DFF Format lndex (5ZM-SC2 onty): The

DFFINDX

operand

of the

system

assignment

statement

specifies

whether

the DFF format

index

built

by startup

is

to be

resident

in

main

storage.

Resident

indexes

reduce

the

time required

to locate

a DFF format. lt is

especially

effective

for single

requesting

terminal

{SRT)

programs

that

use

DFF

type

operations

and

pRUF

type

programs.

lf DFFINDX-NO

is

specified,

a

partial

DFF

index

can

be

built in

main

storage

if the external

pointer

list

is

built

and

there

is room

for indexes.

Refer

to External

pointer List

for more

information.

Resident

OPEN/CLOSE: (57M-SC2 onty): The RESOpN

operand

of the

$EFAC

macro

for generation

causes

$CCROC

to be loaded

during startup.

This

eliminates

the

need

to call

transients

for

allocate

open and

close functions

under

CCP.

In

an RPG

ll program

with

card input

and

index

load

file

output,

the resident

module

saves

lg

transient

calls

for one

program

request.

For

sort

with

one

input

and one

output file,

the resident

module

saves

3g

transient

calls

for each

program

request.

However,

resident

open/close

requires

55

bytes

in

$CC4#1 and 10K

bytes

of

storage

to be

allocated

to the UpA.

Resident

Program

Requat (S704-SC2

only): The RESREO

operand

of the

$EFAC

macro

for

generation

causes

$CCRpR

to be loaded

during

startup.

This

eliminates

the

need

to call

transients

for CCP

program

request

functions.

For

an

SRT

program

request

or a nonactive

MRT

program

request,

four

transient

loads

are saved.

For

an

active

MRT

program

request,

three

transient

loads

are

saved.

Three

transient

roads

are

arso

saved

each

time the

system

operator

wants

a program

request

(PF9

key). Resident program

request

also

saves

two transient

loads

for each

system

or terminal

operator

command

that

is

entered.

lf RESREQ-yES

is

specified,

$CCRpR

occupies

4K bytes

of storage,

which

would

otherwise

have

been

allocated

to the

UPA.

The

following

system

design

considerations

and

techniques

can

be

used

to improve

CCp

performance

and/or

main

storage

utilization:

Resident

Polling: The RESPOL

operand

of the $FBSC

generation

statement

(see

index

entry)

specifies

whether

BSC

polling

modules

are to be

resident

in main

storage

rather

than

be

executed

as transients.

Resident

polling

(RESPOL-YES)

is

especially

important

when

both

DSM

partitions

are

active

to ensure

good

response

time. lf resi-

dent

polling

is

not used,

the

CCp

can be

prevented

from

polling

when

the non-CCP

program

partition

is

using

the

DSM

transient

area

(for

example,

for

disk

access).

Placement

of Files

and

programs

on Disk: CCp

performance

can be

improved

through

careful

arrangement

on disk

of

DSM

and

CCP

routines,

$CCPFlLE, user

application

pro-

grams,

3270

display

formats,

and

data files.

These

elements

of the

system

can

be

arranged

in such

a way

as

to keep

disk

access

mechanism

movement

at

a minimum

during

CCp'

operation,

thus

improving

disk

access

speed.

Dual

spindle

systems

or the

5445

allow

more

flexibility

in

arrangement

of

these

elements

than

single

spindle

systems.

DFF Buffer Support (5204-SC2

only): Specify

an optional

DFF buffer

for each

BSC

line

using

DFF

to improve

per_

formance

by

allowing

up to four

DFF

user

pUTs

to be

scheduled

in

various

stages

of transmission

at

any

given

time. See

l8M System/3

CCp

System

Design

Guide,

GC2l-

5165

for

additional

information.

Conf iguration Limitations, Storage Estimates

and Performance Considerations 223

Mintimizing

Disk Access

Mechanism

Contention: The ex_

amples

shown

in

Figure

16

for

a dedicated

system

illustrate

disl<.

arrangements

that minimize

disk

access

mechanism

contention.

These

arrangements

would

not

necessarily

be

best for all CCP

configurations.

For

example,

the location

of tiCCPF

ILE

is

critical

to performance

when

inquiry

programs

are

used frequently

or when

programs

use DFF

witlr

many

different

formats,

because

program

allocation

and initiation

occur

frequently

with frequent

accesses

of

$CCPF

ILE

by the CCP.

In

order-entry

applications,

on

the

other hand,

program

allocation

and initiation

occur

less frequently

and

the

placement

of

$CCpFILE

is

less

critical;

however,

placement

of data

f iles

become

critical

for

good

performance,

because

frequent

access

to disk

data

filer;

is likely.

Arranging

the

elements of the CCP

system

according

to

certain

general

guidelines

can improve

CCP

performance.

Sonre

guidelines

to follow

are:

r (lenerateCCP

on

a clean

(initializedldisk

volume

on

which

an

object library

was created

before

generation.

F

lace

compilers

on separate, removable

program

prepa-

ration

packs

to free

object library

space

that is

as close

ars

possible

to the beginning

of the library

on the DSM

pack

for user

programs

or 3270

display formats

(if used).

ttlace

user

programs

and display formats

into

the

object

library

that has

space

available nearest

the location

of

the CCP

transients

($CC4xx)

at the beginning

of the

library

to minimize

disk access mechanism

movement

for retrieval

of formats

and

programs.

F

lace

$CCPF

ILE next

to the

object library

on the disk

unit that has

the smallest

object library

or

as close as

possible

to the beginning

of the disk volume.

if no

object

library is

present

on that

volume.

This

provides

the

fastest

d isk

access to $CCPF

I

LE.

Eluild

packs

containing

data

files

evenly.

placing

the

most

frequently

used

files

in

the center. Then

put

the remain-

ing data files

on each

side of the center files

according

to

their usage. In

other words,

the more

often a

file

is used

the closer to center

it would

be;

the

less

often

a

file

is

used

the

farther from

center it would

be.

CCP

USER TASK

PRIORITIES

The

priority

of user tasks

under

CCp

is determined

by

the

program

type. An awareness

of the

priority

structure

can

help

to assure

that

the relative

priority

of user

tasks

meets

installation

needs.

The

following

list

shows

the

priority

structure

by program

type. FIFO

and

LIFO

refer

to first-

in-first-out

and last-in-first-out

respectively.

LOW

refers

to

the low

priority

option

on

the Assignment

pROGRAM

,

statement.

This

statement

is

only valid

under

program

Number

5704-SC2.

NEP

(FIFO}

NEP-LOW

(LIFO)

MRT

(FIFO)

SRT

(LIFO)

MRT

and

SRT

LOW

(LtFO)

lnterval polling: INTPOL

on

$EBSC

generation,

non-MLTA

systems,

can

significantly

reduce

metered

processing

unit

time

in low

activity

periods.

3284

Printer

Busy Timer: lf you are using

a remote

3284

printer

for output

and receive

numerous

printer

busy

condi-

tions,

consider

one of the

following

methods.

These

methods

decrease

the amount

of line

activity required

for CCp

to

process

your

request

for output

and

to return

the

code

indicating

the

printer

is

busy.

1. After

receiving

a printer

busy

return

code,

set the

interval

timer

via

the macro

$SlT.

This

stops

your

task for a specified

amount

of time

before

retrying

your put

operation.

Note

that this

method

requires

an

assembler.

2. Use the RPG

ll operation

code

TIME

to

get

the

time

of day. lssue

the time

operation

until

the

desired

time

period

elapses from

the initial

time request.

Then

reissue

the

put

operation

request.

3. Use the

CCP

operation

code

WAT

to wait for a

speci-

fied

time

before retrying

the

operation.

y'y'ote;

This

method

requires

a transient

to be

loaded

and

can 4ause

conflicts

involving

the

disk

drives.

0

Track

0

I

B

@

il

I

2

A

6

o

= $CCPFILE

= User Programs

= Data

Files

= Disk

System

Management

= CCP

= 3270

Display

Formats

(DFF)

CCP Transients

(gCC4xx)

Reserved

tracks;

source

library

$CCPFILE

shown in R1

because

Rl has

a

smaller

object

library

in

tfris example.

Least-used

data

f

i l,es.

Figure

16, Examples

of Disk

Arrangement for Good Access

spe6d. RESpoL-yES Assumed.

0

Y

Az

conf iguration

Limitations,

storage

Estimates

and performance

considerations 22s

Use of High-Speed

Hardware: BSC communication line

spe,ed

can be increased

through use

of BSCA high-speed

features

or EIA local

attachment

feature lsee

IBM SystemR

Mo'dels 8, 10, 72, and l5 Components Reference Manual ,

GA21 9236 for details).

Blor:king

327O data

causes

minimal degradation

in total

response

time. With blocking,

the

clisplay

format

actually

begins

to appear

sooner

than without blocking. The

screen

blinks

as it receives

each

block

of data.

Console

Activity: Excessive

communication with the con-

sole

by programs

running

under

the CCP

can

degrade

CCp

per{'ormance

by causing a backup

of unanswered

messages.

Act,ivity of the Non-CCP Program Partition: In dual parti-

tion systerrrs,

the type of activity in the non-CCP

program

parlition

can

affect CCP

performance.

For

example,

if the

pro{lram

in the non-CCP

partition

is doing

a

great

deal

of

disk

l/O,

contention for disk

access

can

cause

slower

CCp

perlormance.

Also

contention

for use

of the DSM

transient

area

between

partitions

causes

slower

CCP

performance.

Singls punrtion lnquiry Coding Technique: By entering

data

to inquiry

programs

with the program

request,

the

inquiry

program

needs

to perform

only

two communica-

tions

operations-an

accept input from the

terminal

and

a

put

to the

terminal. lf the

number

of disk

accesses

done

by

the

program

is

kept

to a minimum,

response

time for such

inquiry

programs

is minimal

and response

time for other

programs

currently in

storage is

improved.

Upatating Shared F/es.' When two or more programs are

updating

shared files

concurrently,

CCP

performance

can be

impaired

by two or more

programs

attempting

to update

recc,rds f

rom the

same disk

sector at the

same

time. For

example,

when

a

program

retrieves

a

record

but takes

no

actir)n, that record

is not updated

and the next record

is

not retrieved.

Using Get instead of lnvite and Accept lnput: ln suitable

applications,

such as simple inquiry

without 3270 DFF, use

of get instead

of invite input saves one data move

operation,

saves

CCP

task

switching,

and saves the accept input opera-

tion.

Using DFF Outputflnput Field Types 7 and I to ldentify

Screens.'

Output/input field types 7 and 8 are

protected,

alphameric, nondetectable

fields

with the

modified

data

tag

on. Type

7 fields

are nondisplay;

type 8 fields

are dis-

played

at normal intensity. See l8M System/3

Communi-

cations Control Program Programmer's Reference Manual ,

GC21-7579 for complete information

concerning

DFF field

types.

DFF output/input

field types 7 and 8 are

protected

and

cannot be

changed by the terminal

operator. These

two

f ield

types

can be overridden

to types

1,2, or 5.

DFF output/input field types 7 and

8 can be used to store

information

at the terminal. This information is retrieved

with the

or accept input operation as

long

as the

modified data tags are

not set off by the program. These

f

ield

types can be used

(by placing

information

in

them

with a

put message

or put override

operation) to determine

two different

things:

1. lf the program

uses multiple

formats

to perform

its

job,

these

fields

could be used to determine

which

display format

the terminal currently

is using.

2. lf the

program

has

a series of multiple

steps or opera-

tions to perform

with one

format,

these

field

types

could be used to tell the

program

which step was

performed

last with this terminal or which

step

should

be performed next.

The

put

override

operation

with reset modified data

GC21 7620 6_IBM_System3_Communications Control Program System Reference Manual_Sep80 6 IBM System3 Communications Manual Sep80

GC21-7620-6_IBM_System3_CommunicationsControlProgramSystemReferenceManual_Sep80 GC21-7620-6_IBM_System3_CommunicationsControlProgramSystemReferenceManual_Sep80

Navigation menu

Versions of this User Manual:

Views

Navigation