GC33 6048 01_DOS_VS_Installation_Guide_Rel_34_Mar78 01 DOS VS Installation Guide Rel 34 Mar78
GC33-6048-01_DOS_VS_Installation_Guide_Rel_34_Mar78 GC33-6048-01_DOS_VS_Installation_Guide_Rel_34_Mar78
User Manual: GC33-6048-01_DOS_VS_Installation_Guide_Rel_34_Mar78
Open the PDF directly: View PDF 
.
Page Count: 187
| Download | |
| Open PDF In Browser | View PDF |
GC33·6048-1
File No. S370·36
DOSNS POWERIVS
Systems
Installation Guide and Reference
Release 34
-
----- -- ---------- ---~--
_~_T_
~
Second Edition (March 1978)
This is a major revision of, and obsoletes, GC33-6048-0 and Technical Newsletter GN33-9233,
if installed. The sections "Job Accounting", "Intermediate Storage Requirements", and
Appendixes D and E have been added. All changes to the text and illustrations are indicated
by a vertical line to the left of the change.
This edition applies to version 5, release 34, of the Disk Operating System/Virtual Storage,
DOS/VS, and to all subsequent versions and releases until otherwise indicated in new
editions or Technical Newsletters. Changes are continually made to the information herein;
any such changes will be reported in subsequent revisions or Technical Newsletters.
Requests for copies of IBM publications should be made to your IBM representative or to
the IBM branch office serving your locality.
A form for readers' comments is provided at the back of this publication. If the form has
been removed, comments may be addressed to IBM Program Product Center, Publications
Department (0446), Schwertstrasse 58, D-7032 Sinde/fingen, Germany. Comments become
the property of IBM.
© Copyright International Business Machines Corporation 1977, 1978
Preface
This manual describes the functions of POWER/VS and their usage.
POWER/VS is a component program of the DOS/iS System control Program.
Executing jobs under POWER/VS has the following advantages:
•
Faster job throughput because the partition is only used for job
execution and needs not to wait for slow unit record (UR) devices.
•
Better utilization of UR devices.
partitions.
•
Support of the major BSC and SIA terminals.
They can be shared between
The manual is designed both as a guide to installing POWER/iS under your
DOS/VS supervisor and as a reference source in the day-to-day use of
POWER/VS as your input and output spooling facility for DOS/VS.
As a system programmer, you will find detailed information concerning:
•
The preparation of your DOS/iS supervisor for the installation of
POWER/VS.
•
The calculation of the real and virtual storage space for the
POWER/VS partition.
•
The macro instructions provided for the generation of POWER/VS.
I.
The layout of the POWER/VS account records.
As an application programmer, you will be informed about!
•
The use of POWER/VS in application programs, even though these
programs might be designed not to execute in a POWER/vs-controlled
partition.
•
The possibilities of controlling job accounting and output
segmentation within your application programs.
As a DOS/VS system operator, you will find detailed information on:
•
How to start, control, and terminate the execution of POWER/VS.
•
How to start, supervise, and terminate the execution of POWER/VS
tasks.
•
How to aanipulate the characteristics of POWER/VS jobs and to control
the processing of POWER/VS queues.
This manual consists of four chapters and five appendixes containing the
following information:
£h~E!~~_1
is an introduction to POWER/VS.
Chapter 2 describes how to plan the installation of POWER/VS, how to
calculate the POWER/VS storage requirements, and how to code the
POWER/VS generation macros. In addition, this chapter lists the
terminals that you may use with the POWER/VS RJE support.
Preface
iii
£hapt~-1
lists the POWBR/VS central operator com.ands, the statements
available with the POWER/VS Job Entry Control Language, and the
statements provided for the use of the POWER/VS AUTOSTART feature. This
cha~ter also describes the cross-partition communication macros and the
macros available for POWER/VS job accounting and output segmentation.
Chapt~~
describes, in many examples, the day-to-day use of POWER!VS
and POWER/VS PJE as seen from the central system operator's point of
view.
!EE~gix-A
is a detailed discussion of a POWER/VS function called data
compaction. This function, which is available with the POWER/VS RJ~,SNA
support, can be selected in the POWER/VS generation procedure.
~dix
B provides specific information concerning the data flows
between the central system and remote terminals in the POWER/VS RJE,SNA
environment.
~~~
summarizes the VTAK LOGON BIND requirements with respect to
the POWER/VS RJE,SNA support.
Appendix D shows tvo examples of a status report produced after issuing
the PDISPLAY command. These examples apply to the IBM 3800 Printer.
A£~dix
E provides information on coding and using reader exit
routines.
System and application programmers are expected to be familiar with
DOS/VS system generation procedures and with multiprogramming functions
under DOS/VS. Central system operators should be familiar with the
operating procedures in a DOS/VS multipartition environment.
Publications related to the information given in this manual are listed
in the BibliograFhy.
iv
POWER/VS Installation Guide and Reference
Contents
SU"KARY OF AMENDMENTS
ix
CHAPTER 1. INTRODUCTION TO POWER/VS.
Hardware Supported by POWER/VS.
Local Unit Record I/O Devices •
Direct Access Storage Devices •
Remote Job Entry Devices.
Concepts and Functions.
User Responsibilities
Input/Output Description.
Environmental Considerations.
Programming systems
system Requirements
Timing and Throughput Information
-
1
1
2
2
2
3
7
7
8
8
9
9
CHAPTER 2. INSTALLING POWER/VS •
Planning the System
Machine Requirements.
Intermediate Storage Requirements
Size of the Data File and Queue File.
Block Size of the Data File •
Number of Track Groups.
Size of the Account File.
Storage Requirements.
Storage Requirements Calculation.
DOS/VS Supervisor Generation Requirements •
Special Considerations for DOS/VS Functions •
VTAK and NCP Generation Requirements.
Generating POWER/VS
POWER/VS Generation Macros.
Conventions •
POWER Macro •
PLINE Macro •
PRMT Macro.
PCPTAB Macro.
POWER/VS Phases
POWER/VS Generation Procedure •
Terminals Supported by POWERJVS
IBft 2110 Data Communication System.
IBM 2780 Data Transmission Ter.inal (Model 1 or 2) •
IBM 3741 Data station (Model 2 or 4) •
IS! 3771 Comaunication Terminal •
IBM 3773 communication Terminal
IBM 3774 Com.unication Terminal
IBM 3775 ComMunication Terminal
IBM 3776 Comaunication Terminal
IBM 3780 Data Communication Terminal.
IBM 3790 Communication Systea •
POWER/VS support for other Devices.
IB" 2560 and 5425
IBft 3525.
ISII 3800.
24
24
25
32
33
38
41
42
44
44
45
46
46
46
47
47
47
48
49
49
49
50
50
CHAPTER 3. USING POWER/VS.
POWER/VS Central Operator Com.ands.
Coamand Descriptions.
PACCOUNT Command.
PALTER Comtland.
PBRDCST Command
51
51
53
53
54
57
10
10
10
11
11
12
13
13
13
18
22
22
23
24
Contents
v
PCANCEL Command
PDELETE Command
PDISPLAY Command.
PEND Command.
PFLUSH Command.
PGO Command
PINQUIRE Command.
PRELEASE Command.
PFESTART Command.
PSETUP Command.
PSTART Command.
PSTOP Command
POWER/VS Job Entry Control Language statements.
Functions of JECL Statements.
Format of JECL Statements •
Using JECL statements
* $$ CTL Statement.
* $$ DATA Statement
* $$ EOJ Statement.
* $$ JOB Statement.
* $$ LST (* $$ P~T) Statement
* $$ PUN statement.
* $$ RDR Statement.
* $$ SL! Statement.
JECL Delimiter Statements
Cross-Partition Communication ftacros.
Macro Descriptions.
SPL Macro
PUTSPOOL Macro.
GETSPOOL Macro.
CTLSPOOL Macro.
Return Codes from PUTSPOOL, GETSPOOL, and CTLSPOOL.
Job Accounting.
Reader Account Record
List Account Record
Punch Account Record.
Execution Account Record.
RJE Account Records
PUTACCT Macro •
output Segmentation
SEGMENT Macro •
POWER/VS AUTOSTART Statements
Statement Descriptions.
FORMAT Statement.
READE~ Statement.
PRINTERS statement.
PUNCHES Statement
.'
.'
CHAPTER 4. OPERATING A SYSTEM CONTROLLED BY POWER/VS
Assumptions
Initiating POWER/VS
Initiating POWER/VS without AUTOSTART •
Initiating POWER/VS with AUTOSTART.
Assigning Dummy Devices
Changing Partition Priorities •
Issuing POWER/VS Commands
starting and Stopping a User Partition.
Bringing a Partition Under the Control of POWER/iS.
Changing the Class Specification for a Partition.
stopping and Restarting a Partition
Task Control.
starting a POWER/VS Reader Task
Starting a POWER/VS writer (List or Punch) Task
Stopping POW'ER/VS Tasks •
Remote Job Entry - BSC Terminals.
vi
POWER/VS Installation Guide and Reference
58
58
59
63
64
65
66
67
68
69
70
73
75
77
77
79
81
81
82
82
85
95
100
101
105
106
107
107
109
111
112
114
116
116
117
119
120
121
123
124
124
126
126
126
127
127
128
129
129
129
130
134
135
136
136
138
138
138
139
139
139
140
140
142
starting an RJE,BSC Line. • • • •
• •••
Controlling RJE,BSC Operations. •
• ••••
Remote Job Entry - SMA Terminals. •
• ••••
Establishing the VTAM Interface for POWER/VS with RJE,SNA
Controlling RJE,SNA Operations.
• ••••
Stopping an RJE,SNA Session • •
• • • • • • • •
Termination of All RJE,SNI Sessions •
Terminating pow ER/VS. • • • • • • •
Noraal Ter.ination. • • • • • • •
Emergency Termination • • • • • • • • • •
Multipurpose Onit-Record Devices ••
Miscellaneous Devices • • • •
Using the IBM 3540 Diskette Input/output Unit •
The 3540 in SYSIN Mode.
The 3540 in Data Mode • •
APPEIDIX A.
DATA COMPACTION.
142
143
143
143
144
1411
145
145
145
146
146
147
147
147
148
151
157
APPENDII B. RJE,SNA I/O SPECIFICATIQNS •
Inbound Console Data • • • • •
Inbound Card Data •
Outbound Print Data • •
Outbound Punch Data • •
Outbound Console Data • • • • • • •
Data Flow Control (DFC) Requests.
Inbound DFC Requests. •
• • • •
Outbound DFC Request • •
157
157
159
161
161
161
161
162
..
APPENDIX C.
LOGON KODE TABLE AND BIND PARAMETER
APPENDIX D.
EXAMPLES OF STATUS REPORT OUTPUT
167
APPENDIX E.
READER EXIT ROUTINE.
169
REQUIRE~ENTS
165
BIBLIOGRAPHY.
171
INDEX • • • •
173
Contents
vii
Figures
The Major Functions of POWER/VS. ..
..
Structure of the Virtual Partition and Storage
Requirements
.. .. .. .. .. .. .. .. ..
Figure 2-2. Space Calculation for RJE,SNA Support Control
Blocks ..
..
..
.. .
.. ..
..
Base Values for the Storage Calculation for the
Figure 2-3.
POWER/VS Fixable Area (2 parts) ..
..
.. ..
Figure 2-4. Detailed Storage Calculation Example (2 parts)
POWER/VS Storage Calculation Summary
Figure 2-5.
..
Figure 2-6. POWER/VS Phase Naaes and Their Functions
..
Work Sheet for Coding POWER/VS Generation Placros
Figure 2-7.
..
(2 parts) •
.. .. .. ..
.. .. .. .. .. ..
Figure 3-1. POWER/VS Central Operator Commands
Figure 3-2. Examples of the Use of POWER/VS JECL
Figure 3-3. Format of JECL statements. ..
Figure 3-4. JECL Statements. . .. .. .
..
Figure 3-5. PUTSPOOL, GETSPOOL, and CTLSPOOL Return Codes.
.. .. ..
..
Figure 3-6. Reader Account Record.
.. ..
Figure 3-7. List Account Record. ..
..
Figure 3-8. Punch Account Record ..
Figure 3-9. Execution Account Record
Figure 3-10. RJE,BSC Line Account Record.
Figure 3-11. RJE,SNA Session A.ccount Record ..
Figure 4-1. Job Stream Example for POWER/VS Initiation ..
Example of a POWER/VS Status Report.
Figure 4-2.
Figure 4-3. POWER/VS Commands.
.. ..
Figure A-1. Numbers of Master Characters Related to Numbers of
Compact Code Characters.
.. ..
..
Example of Compact Code Set. ..
Figure A-2.
..
..
Figure A-3 .. Translate-and-Test Table for Compaction (TRTC)
Figure A-4oo Translate Table for Compaction (XLTC) •
Figure B-1. Inbound Card Data with DOS/VS JCL Job Delimiters ..
Inbound Card Data with POWER/VS JECL Job Delimiters.
Figure B-2.
.. ..
..
Figure B-3. DYC Request Support for SNAoo
..
..
Data Communication Facilities Supported by POWER/VS
Figure B-4.
..
RJE,SNA ..
.. ..
..
..
.. ..
Figure B-5. SCS Control Characters Supported by POWER/VS RJE,SNA
Data Interruptions Supported by POWEll/VS RJE,SNA
Figure B-6 ..
LOGON I10de Table Coding Example. .. .. .. ..
Figure C-l.
Figure C-2oo BIND Parameters for the Presentation Services. .. ..
Figure 1-1.
Figure 2-1.
····· ·
·
····
·· ····· ·
· ····
· ·· ·· · ·
···
·. · ·
. · ···
.·
·
·
· · · ··
·· ·· ·
· · ·· ·· ·
·
··
·
·····
····
·
.
··
···· ·
···· ·
····
· · · .. · ·
..···· ····· · ··
·
···
viii
·
POWER/VS Installation Guide and Reference
·
6
14
15
16
19
21
41
42
52
16
78
79
115
117
118
119
120
121
122
131
132
131
151
152
155
155
158
158
161
163
163
164
165
166
Summary of Amendments
Release 34
Edition GC33-6048-Q describes POWER/VS as a component
program of the DOS/VS SCP.
The following enhancements are documented:
•
Additional device support
•
Increased number of partitions
•
Library device independence
•
Extended support for RJE,SNA work stations.
!!1_2!JJ=~~33
documents changes to support the
independent component release (rCR) of the IBM 3800
Printer under POWER/VS.
Edition GC33-6048-1 includes corrections and enhance.ents
to the previous edition.
Changes resulting from the lCR for the IBa 3800 Printer
are included in this manual. The pertinent figures and
text portions are marked so that users who have not
installed the ICR can skip these changes.
-
The following enhancements are described:
"Job Accounting" in Chapter 3, "Assigning Dummy Devices"
and "Changing Partition Priorities" in Chapter 4,
"Examples of Status Report output" in Appendix D, and
"Reader Exit Routine" in Appendix E.
Summary of Amendments
ix
Chapter 1. Introduction to POWERIVS
POWER/VS is designed to improve the throughput of a computing system by
se?arating unit-record input and output operations (that is, reading
card or diskette input, punching cards, and printing reports) and
internal computing operations of application programs in a DOS/VS
multiprogramming environment. This process, which is called "spooling"
(an acronym derived from the term "Simultaneous Peripheral Operations
On-Linen), results in oVerlapping the unit-record I/O operations for all
controlled partitions with the execution of application programs in
these partitions. To achieve this, POWER/VS stores all unit-record
input and output in input and output queues on disk. When a unit-record
device is available to read input or to punch or print output, POWER/VS
either stores the input data in the input queue or retrieves list or
punch output from an output queue and transfers it to that device. When
an application program in a POWER/VS-controlled partition is ready to
accept input or is about to produce output, POWER/VS retrieves its input
from the queue associated with the application program's partition and
stores output in the associated output queue on disk.
Hardware Supported by POWERIVS
POWER/VS operates in virtual mode in one partition of the DOS/VS system.
The system dispatching priority of the POWER/VS partition must be higher
than the priorities of the partitions it is serving.
POWER/VS maintains input and output queues on direct access storage for
the card readers, diskette I/O units (input only), card punches, and
printers associated with the partitions under its control. These queues
are filled or emptied by the appropriate physical devices. When a
program in a POWEB/VS-controlled partition makes an input or output
request to one of these devices, POWER/VS provides the next record from
the appropriate input queue or collects the record and places it in the
appropriate output queue. These operations take place at main storage
or direct access storage speeds and are overlapped with the execution of
programs in other partitions; hence, programs execute faster and take
better advantage of the system environment. Application programs
executing in POWER/VS-controlled partitions do not require modifications
to take advantage of POWER/VS.
The POWER/VS queues are under optional operator control. This allows
the DOS/VS system operator to modify the order in which programs are
executed by manipulating the queues with POWER/VS commands. Because
POWER/VS allows job input and output also from and to remote terminals,
the possibility of manipulating queues is also available to terminal
operators. Further control is available to the application programmer
through the option of using Job Entry Control Language (JECL) statements
within the job input stream.
The user generates POWEF/VS through the assembly of the POWER/VS macros.
These macros allow the user to specify the options appropriate to his
system environment. Among the options that the user _ay select are
features such as the inclusion or suppression of job accounting
routines, of system network architecture (SNA) support, and others.
Details concerning the generation of POWE~/VS are described in
Chapter 2.
Chapter 1.
Introduction to POWER/VS
1
I
LOCAL UNIT RECORD I/O DEVICES
POWER/VS supports the following unit-record devices for peripheral input
and output:
IBM
IBM
IBM
IBM
IBM
IBM
IBM
IBM
IBM
IBM
1442 Card Read Punch
2501 Card Reader
2520 Card Read Punch
2540 Card Read Punch
2560 Multifunction Card Machine
3501 Card Reader
3504/3505 Card Reader
3521 Card Punch
3525 Card Punch
5425 Multifunction Card unit
IBM
IBM
IBM
IBM
IBM
IBM
IBM
1403
1443
3203
3211
3784
3800
5203
Printer
Printer
Printer
Printer
Line Printer
Printer
Printer
IBM 3540 Diskette Input/Output Unit
(input only) •
I DIRECT ACCESS STORAGE DEVICES
POWER/VS uses three types of files: the account file, the queue file,
and the data file. For these files, POWER/VS requires direct access
storage. Different POWER/VS files may reside on different direct access
storage devices, which may be any of the following:
IBM
IBM
IBM
IBM
IBM
IBM
2314
2319
3330
3333
3340
3350
Direct Access Storage Facility
Disk Storage
Disk Storage (including Model 11)
Disk storage and Control
Direct Access Storage
Direct Access storage.
I REMOTE JOB ENTRY DEVICES
To enter jobs into the system using remote terminals, and to obtain
output at such terminals, the POWER/VS remote job entry (RJE) feature
supports the following asc and SDLC terminals:
IBM
IBM
IBM
IBM
IBM
IBM
IBM
2770
2780
3741
3741
3770
3780
3790
Data Communication System
Data Transmission Terminal
Data Station (Model 2)
Programmable Work Station (Model 4)
Data Communication System in BSC or SNA mode
Data Communications Terminal
communication System.
liotes: In general, all BSC terminals and/or systems are supported that
emulate the 2770, 2780, or 3780 line discipline, and all SNA work
stations that follow the SNA rules defined for LUTYPE1. For details
refer to Appendix B, "RJE,SNA I/O Specifications".
2
POWER/VS Installation Guide and Reference
The following applies to 3770 terminals: In BSC mode, 3770s are
supported as 2770 or 3780 terminals, in SNA mode, LUTYPEl protocols must
be used.
op to 25 BSC terminals or up to 200 SDLC and BSC terminals can communicate concurrently with the central system via switched or nonswitched
lines. In noncuncurrent operation on switched lines, any number of BSC
terminals may be controlled by POWER/VS as long as the maximum number of
concurrently operating BSC terminals does not exceed 25.
For further information on POWER/VS RJE, refer to the
Work Station ~~-2uide, GC33-6049.
~Q~L!~_EQ!~BL!~
Concepts and Functions
The basic concept of POWER/VS has not changed since the first appearance
of its predecessor, POWER, when non-VS DOS allowed the guasisimUltaneous execution of two or three independent programs in different
partitions residing in the main storage of an IBM System/360. The
implementation of POWER/VS in DOS/VS maintains this spooling concept
mentioned earlier. In detail, POWER/VS operation includes the following
major activities:
•
!~E~!.
POWER/VS reads the job streams (job control statements,
programs, and data cards) for the individual partitions and stores
these in input queues on disk. The input may be entered from:
A local card reader device.
A local diskette device.
A remote BSC terminal.
A remote SNA (SDLC) work station with a console and an input
device (card reader or aO-column card-image disk or diskette
device) •
An outside partition not controlled by POWER/VS.
•
ExecutiQa. From the input queue on disk, the jobs are transferred by
POWER/VS to the designated partitions and executed. The jobs contain
all required input and may optionally contain JECL statements to
indicate individual job execution or I/O requirements.
•
QY!EY!.
Job output (printer and punch) of every job is stored in
output queues on disk (or tape) by POWER/VS before it is finally
processed as output:
For a local printer or punch device.
For a remote BSC terminal.
For a remote SNA (SDLC) work station where the output can either
be produced by an appropriate work station unit-record device or
where it can be temporarily stored on disk ~r diskette. In the
latter case, the user can perform remote spooling of his job
output.
For an outside partition not controlled by POWER/VS.
Chapter 1.
Introduction to POWER/VS
3
•
£2n!rol. Throughout the different steps of input, execution, and
output, the jobs running under POWER/VS are within the management of
the user through the following command language facilities:
Job Entry Control Language (JECL). Along with his input job
decks, the user may insert JECL commands to describe individual
job execution or I/O requirements.
Central operator commands. From the starting of input until the
final discharging of list and punch output, the central operator
may start and stop the job execution, display or alter execution
and I/O performance characteristics, or perform similar
functions.
Remote terminal operator commands. Similar to the central
operator, the remote terminal operator may perform many of the
functions as above for all jobs submitted by him or routed to
him.
Cross-partition communication macros. These macros enable an
application program not running under POWER/VS control to
supervise jobs running under POWER/VS control in the same way as
the central or remote terminal operator. However, this job
supervision from outside POWER/VS is restricted to the use of
five commands. For details, refer to the description of the
CTLSPOOL macro under "Cross-Partition communication Macros" in
Chapter 3.
Job input as well as job output may be held in the POWER/VS queues for
execution or printing/punching at a later time. This allows the user to
hold jobs that need, for example, two hours of execution or printing
time until the system is less occupied.
•
bgg2~D!iDg.
POWER/VS optionally creates accounting information for
each job running under its control.
•
§gg~~D1g1iQD.
Turnaround time for jobs with extensive printed or
punched output can be improved by segmenting the output, which means
that parts of the output are printed or punched before the entire job
is finished.
segmentation is always done on logical boundaries. For
a printer this is a page (skip to channel 1), for a punch this is a
card. The following types of output segmentation can be
distinguished, based on the event that initiates it:
£Qyn1=££!!gn_QY!EY1_segmentation. You can specify the number of
print pages and/or punched cards in the output file, after which
physical output should be initiated, by means of the RBS=
parameter of the POWER macro during POWER/VS generation.
Q21~~£!!~D-Q~1EY1_§eqmentation.
You may submit two or more
(* $$ PRT) statements within the boundaries of one
POWER/VS job. Each of these statements causes an individual list
queue entry to be created.
*
$$ LST
Pro~am-d~iven output segmentation.
In your application program
you may use either the SEGMENT macro to separate the output, or
the LFCB macro, which causes segmentation before loading the new
FCB. You may also issue the SETPRT macro requesting a printer
setup that requires operator intervention, changes copy grouping,
or specifies a copy number (CINDX) greater than one.
4
POWER/VS Installation Guide and Reference
I•
£In!..1_Q~!I!1Q'_~Qn!'21.
The execution of POWER/VS can be
controlle4 by the DOS/VS console operator. Using POWER/VS central
operator co•• ands, the operator can perform any of the following
functions:
Rearrange the order of job streams in input queues or the order
in which the output fro. differen\ jobs is to be printed and/o~
punched.
Delete input job streams or job output waiting in queues.
Hold job streams or job output in input or output queues for
later consideration or processing.
Interrupt printer or punch output, for example, to free a device
urgently required by soae other task.
Restart printer or punch output, either from the beginning or
fro. any desired point within the data stream.
Specify the number of copies to be printed or punched fro. any
data file.
input job streams in the queues even after processing of
the jobs has been completed, or retain printer and/or punch
output in the queues even after it has been printed or punched
completely.
~etain
I•
releprocessing la~1!11I. POWER/VS also offers a teleprocessing
facility, called Remote Job Entry (RJE). with RJE, jobs .ay be
submitted froa remote terminals. Once a job has been entered into
the input job queue, the execution proceeds under DOS/VS supervision.
All data files required by the job are subject to DOS/VS
specifications, just as if the job had been entered locally. RJE job
output aay be directed to the terminal from whieh tha job was
entered, to other terminals, or to the local output unit of the
system.
with these functions, POWER/yS ensures a maximum of flexibility for a
DOS/'S multiprogramming environment and achieves an optiaum usage of the
system resources available in any installation.
Pigure 1-1 gives an overview of the major functions of POWER/VS.
Reader/Writer task performs the read/write functions of a POWER/yS
job. The operator can call for concurrent execution of as aany
read/write tasks as he has physical I/O devices available.
A
An Execution Processor task provides simulated input/output support for
the execute function. An execution task is available for each partition
under POWER/VS control. An execution output task is automatically
initiated when required by a user job.
Por more information on POWER/VS tasks, refer to pos/VS POWER/YS
Part 1, SY33-8576.
Chapter 1.
~
Introduction to POWER/VS
5
INPUT
o
Diskette
Card
Input
Input
Local
Remote
Cross-Partition
CONTROL
JECL
Cards
---,
Intermediate
Storage
r
I
I
I
r
r
I
I
I
-1
I
I
I
I
I
I
I
EXECUTION
~+-~I
I
_.J
Operator's
Console
r
I
I
I
Cross-Partition
Commands
I
I
___ -l
Execution
Processor
Task
User's
Partition
I
I
!
I
I
I
r
I
Intermediate
Storage
I
I
I
,
I
I
Accounting
Task
L_
Writer
Task
+ __ .1
Listed
Output
ACCOUNTING
{:
Local
Remote
Cross-Partition
Punched
Output
- - Dataflow
- - - Operator communication
Figure 1-1.
6
The
~ajor
Functions of POWER/VS
POWER/VS Installation Guide and Reference
User Responsibilities
Before you can start to generate POWER/VS, you must tailor your
operating system (DOS/VS) to the requirements imposed by POWER/VS.
includes:
This
•
The definition of POWER/VS-specific parameters (one is required) in
the macro instructions for the DOS/VS system generation.
•
The preparation of POWER/VS generation macros. To tailor POWER/VS to
your needs, you can specify optional features of this system, such as
the job accounting support, the SNA support, and others in a
generation table which you then have to assemble, link-edit, and
catalog.
•
The allocation of both virtual and real storage space for the
POWER/VS partition.
•
The assignment of the highest system dispatching priority for the
POWER/VS partition over the user partitions assigned to run under
POWER/VS.
Details concerning the parameters required for the DOS/VS system
generation are contained in the publication DOS/VS System GeneratioR,
GC33-5377. For more information about the generation of POWER/VS, refer
to Chapter 2 of this manual.
Input/Output Description
POWER/VS intercepts input and output requests issued by application
programs that execute in independent DOS/VS partitions. As stated
before, these partitions have a lower priority in DOS/VS.than the
POWER/VS partition that controls them.
Each activity performed by POWER/VS receives input and produces output.
That is, to satisfy an input operation requested by an application
program, POWER/VS reads the input destined for this application and
writes it onto a data ftle,'from where the application program can
retrieve it later for processing. Inversely, to satisfy an output
request issued by an application program, POWER/VS, after having
collected the application program output in a data file, reads this file
and prints or punches the data at the appropriate unit-record output
device or sends it to the designated remote terminal or work station.
Concurrently with the production of data file entries, POWER/VS creates
an entry in a queue file giving summary information on the entries in
the data file. There are three types of queue entries corresponding to
the three types of data: reader queue, list queue, and punch queue
entries. The queue file gives POWER/VS a warm start capability in case
of a system breakdown.
In more detail, the input to and the output fro. POWER/VS consists of
one or more of the items listed below.
POWER/VS input can be:
•
Control information, which can be either POWER/VS job entry control
language (JECL) statements, central operator commands, POWER/VS
remote job entry (RJE) com.ands, or JECL commands contained in crosspartition communication macros.
Chapter 1.
Introduction to POWER/VS
1
•
DOS/VS job control statements.
•
Application-oriented data provided from a card or diskette reader or
from a remote terminal or work station.
•
DOS/VS source statement library books. These may be included in the
input job stream by using a special JECL command (Source Library
Include; see the description of the * $$ SLI command in Chapter 3).
In this case, the output consists of data stored in an input data file.
POWER/VS output consists of data stored in an output data file, and of
messages. In this case, the output can be:
•
Printer (list) output
•
Punch output.
This output can be directed to unit-record devices, to magnetic tape
devices, to remote terminals or work stations, or to other partitions
that do not execute under control of POWER/VS.
Environmental Considerations
This section contains information pertaining to the planning of a
POWER/VS installation and discusses installation-related alternatives
with respect to the use of POWER/VS.
PROGRAMMING SYSTEMS
The POWER/VS modules are written in IBM System/370 Assembler language.
The following programs are used in the support of POWER/VS:
1.
Required software support:
DOS/VS Release 34 (Program Number 5745-010)
2.
optional software support for RJE,SNA:
DOS/VS Virtual Telecom8unications Access Method (VTAM) Level 2
(Program Number 5745-010).
DOS/VS Network control Program (Nep) Version 5.0 (Program Number
5747-AS2) •
3.
Optional software support for the IBM 3800 Printer:
DOS/VS POWER/VS IBM 3800 Printing Subsystem Independent Component
Release (ICR).
POWER/VS also operates with the above systems in a virtual aachine
environ.ent under VM/370.
8
POWER/VS Installation Guide and Reference
System Requirements
In addition to the system requirements of DOS/VS with the necessary
features, of VTAM (optionally), and of user programs, POWER/VS has the
following additional hardware system requirements:
1.
Minimum storage requirements:
K bytes
(no RJ~
support)
K bytes
K bytes
(RJE,BSC
support)
(RJE ,SNA
support)
I
I
1
I
-------------------------------------------------------------1
Main storage
10
14
14
I
I (real)
I
I (virtual) *
I
I
I
1
I
I
1------------------1---------------1---------------1---------------1
I Main storage
1 152
I
174
I
210
I
(see note)
(see note)
I
t------------------------------------------------------------------1r
t *For the 3800 ICR support, add 4K bytes to each value.
I
I
RQ~:
For POWER/VS with RJE,SNA support, or when using an IBM 3800
Printer, you must specify the SIZE= parameter in the / / EXEC POWER job
control statement.
The minimum requirement may increase due to maintenance activity.
2.
Kaximum resource requirements:
Up to 25 Bse terminals concurrently. Through switched operation,
more terminals may be in the network nonconcurrent!y.
up to 200 BSC terminals and SNA work stations (SDLC)
(concurrently). This figure may include up to 25 BSC terminals.
Through switched operation, more Bse terminals may be in the
network nonconcurrently as long as 25 or less Bse terminals are
operating concurrently with POWER/VS.
Up to eight logical printers, eight logical punches, and one
logical reader may be assigned to all partitions under control of
POWER/VS.
To use the RJE,SNA capabilities of POWER/VS for the IBM 3190, the 3190
Communication System with RJE Facility Support is required.
Timing and Throughput Information
Although the execution time for a single' DOS/VS job may slightly
increase under the control of POWER/VS (.which is due to the strict
separation of input and output activities from the program execution),
the overall system performance increases considerably. By adding
further resources in terms of real and virtual storage and peripheral
equipment over and above the minimum system requirements for POWER/VS,
you can further improve the efficiency of your installed 1BK System/310.
Chapter 1.
Introduction to POWER/VS
9
Chapter 2. Installing POWERIVS
This chapter guides you in th~ installation of POWER/VS. Before you
start installing the system, you have to consider a number of topics
concerning requirements in the available hardware and software. These
considerations are discussed in the section "Planning the System". The
next section, "Generating POWER/VS", acquaints you with the macros
available to generate the system and with the steps to be executed until
POWER/VS is available in your DOS/VS environment.
The information in this chapter is supplemented by a summary of the
terminals supported with POWER/VS RJE and a discussion of some special
unit-record devices.
Planning the System
Before POWER/VS can be installed, you have to ensure the availability of
certain features in your computer installation environment. These
prerequisites fall into the following categories:
•
Machine requirements
•
Storage requirements
•
DOS/VS superVisor requirements
•
VTAM and NCP generation requirements (optionally).
The following sections contain detailed discussions of these topics.
MACHINE
REQUI~EMENTS
POWER/VS operates on any IBM System/370 CPU that is supported by DOS/VS
Release 34. It resides in a virtual partition with a priority higher
than that of the partitions it controls. POWER/VS supports programs
running in real and virtual mode.
POWER/VS supporting RJE,SNA requires a minimum of 210K virtual and 14K
real storage. POWER/VS with RJE,BSC requires a minimum of 174K virtual
and 14K real storage. without RJE support, 152K virtual and 10K real
storage are required. Included in these figures is sufficient real and
virtual storage for one active POWER/VS task. For performance reasons,
how~ver, and for the simultaneous operation of several POWER/VS tasks,
you should allocate more real and virtual storage. For details, refer
to the example given under "storage Requirements Calculation" later in
this chapter.
With the remote job entry (RJE) feature, POWER/VS accepts input from,
and routes output to, remote terminals or work stations. The attachment
of BSC terminals to a central system requires one of the following
minimum configurations:
10
POWER/VS Installation Guide and Reference
--
•
An IB~ 2701 Data Adapter Unit (DIU) with Synchronous Data Adapter,
Type II, equipped with EBCDIC or ASCII code and transparency, Q[
•
An IBM 2703 Transmission Control Unit (TCU) with Synchronou$
Attachment, Synchronous Base, Synchronous Terminal Control - EBCDIC
or ASCII and Synchronous Line Set, and 3104/3705 Communication
Controller in 270x emulation mode, ~
•
For a Model 115 CPU, an ICA with synchronous line group and
synchronous line medium speed (with or without clock) •
•
For a ~odel 125 CPU, an ICA either with synchronous line group and
synchronous line medium speed (with or without clock); or with
synchronous line low load.
•
For a Model 135 CPU, and Intaqrated Communications Adapter (ICA)
a Synchronous Data Adapter, Type II, and transparency.
with
The attachment of SNA work stations requires:
IB~
•
An
3704 Communications Controller, or
•
An IBM 3705 Coamunications Controller.
For a detailed list of the terminals supported by POWER/'S, refer to the
section "Terminals Supported by POWER/VS" later in this chapter.
INTERMEDIATE STORAGE REQUIREMENTS
Intermediate storage in POWER/VS is on disk (tape for output only) and
contains the queue file, the data file, and optionally t~e account file.
Generally, one IBM 2316 disk pack, 100 cylinders on an IBM 3336 disk
pack, or 200 cylinders on an IBM 3348 data module are sufficient for
POWER/'S. The POWER/'S files (queue file, data file, and account file)
need not be on units of the same type. However, if the data file is on
more than one extent or on more than one physical device, these devices
must be of the same type. For the 3340, all extents of the data file
must reside on the same type of 3348 module. Kultiple disk extents and
multiple disk volumes are supported to a maximum of five extents for the
data file.
POWER/'S data files should not reside on a volume containing
frequently used files. DASD space assigned must be sufficient to
contain both input and one segment of output for any POiER/VS job.
~ize
of the Data File and Queue File
The data file, which is made up of track groups, and the queue file,
which is primarily made up of queue records, are directly related. Each
track group has a corresponding queue record. The size of the data file
is defined by the total number of track groups, which in turn is limited
by the number of records in the queue file.
Chapter 2.
Installing POWER/VS
11
In estimating the size of the data file and queue file, you should
consider the following:
•
The maximum number of POWER/VS jobs in the system at anyone time
•
The largest volume of spooled I/O for any job
•
The fact whether or not output segmentation is used.
For the data file extents, estimate separately the total number of
input/output card images and the total number of line images spooled to
disk in a typical 8-hour shift. Choose a file size large enough to hold
half this amount of data. This should prevent POWER/VS from running out
of file space. File extents can be res?ecified if they prove to be too
large or too small (check the status report).
The queue file should be large enough to support the entire data file:
that is, there should be one queue record for each track group in the
data file.
It is good practice to allocate six additional queue file
records for internal POaER/vS usage.
The size of the physical records written to the data file is determined
by the DBLK parameter. This also influences the size of the data
buffers required for each POWER/VS task.
If not explicitly specified by
the user, the system chooses a default block size, which suits the
characteristics of the disk device assigned to the data file. The
default values for each device are shown below:
1
Device Type
IDefault Data
IBlock Size
IApprox. No. of
ICards per Block*
IApprox. No. of
ILines per Block**
I
1 3340
1 3350
I
I
1
I
1
I
I
I
1----------------------------------------------------------------------1
I 2314/2319
I
920
I
11
I
7
I
1 3330/3333 1 952
1
12
I
7
I
808
960
10
12
6
1
1----------------------------------------------------------------------1
POWER/VS suppresses trailing blanks; hence these figures represent I
1*
I
t
1** Based on 132 print positions per line.
I
I
I
I
I
the minimum values.
If you specify a value other than the default, it is possible to achieve
better performance. In general, the smaller the DBLK value is, the less
real storage is required to execute a given number of tasks.
Conversely, the larger the DBLK value is, the more real storage is
required; however, more efficient use is made of intermediate storage
because the larger the block size, the more spool records per track.
The more records in a block, the fewer the disk I/O operations to
perform. If the data buffer size, which can be increased by 32-byte
increments, is larger than 1000 bytes, only one.data buffer will fit
into a storage page. The largest buffer size is 2008 bytes, which is
one data buffer per page with its control information.
12
POWER/VS Installation Guide and Reference
Number of Track
G~Ups
After you know your DBLK size, you can determine the track group size.
You know the number of blocks per cylinder and approximately how many
records are in each block.
If the track group size is small (the smallest is 1), then one queue
record is needed for each track on the data file. This results in a
larger queue file and an overhead in queue record management, but best
utilizes the disk space available in the data file. If the track group
size is large (the largest number would be that equal to the number of
tracks per cylinder), then fewer queue records (one per cylinder) are
needed. However, because there can be only one POWER/VS job for each
track group, disk space is wasted on the data file whenever a job does
not fill a track group.
If you do not specify a track group size, the system will try to use all
of the data file. The system calculates the number of tracks within the
extents provided by the data file.
It then determines the number of
152-byte records it can write into the queue file.
From these two
figures it determines the number of track groups to allocate, by
calculating the smallest value possible for TRACKGP, which utilizes the
largest amount of the data file.
If during POWER/VS initialization, the TRACKGP specified conflicts with
the EXTENT information for the data file, the system changes the TRACKGP
value. You are informed of the Dew TRACKGP value by message 1Q09I.
Size of the Accouat Pile
To estimate the size of the account file, you should consider that each
POWER/VS job can create at least one reader, one list, and one punch
account record.
In addition, each DOS/VS job step within a POWER/VS job
creates one execution account record. Por example, for the 3330
approximately 170 jobs can be handled by one cylinder of the account
file. This figure is based on an average of five account records per
POWER/VS job.
STOR~GE
REQUIREMENTS
Virtual and real storage space must be a110cated for ,the POWER/VS
partition. Figure 2-1 shows the structure of the POWER/VS partition and
the types of information stored herein. Pigures 2-2 and 2-3 supplement
the storage space description given in Figure 2-1. An example how to
calculate the size of the POWER/VS partition and of its corresponding
storage areas is provided in the section "Storage Requirements
Calculation" later in this ~hapter.
Chapter 2.
Installing POWERjVS
13
i
1
Virtual Partition
--------------------------------------------------------------1
Area Dis- I
1Storage
1
position
1contents
I
1Requirements
I in Bytes
I
1
--------------------------------------------------------------~----~--
Required
IPermanent Area:
I
POWER/VS nucleus and control
I
tables
I
I
s
' I
I
I
' I
IFixable area
I
User area
,8K
I
r
iT
___________ !
,
IAccounting support
14K
I
I
I see note 1
I User RDREXIT phase
,
IRJE,BSC support
Z
E
I see Figure 2-3
__________l:~~:~~~_~~~~_~~~:~~_~~~~:~~~:~ ____l~~:~
optional
R
P
A
G
E
16K
I
v
s
A
,Spool manager support
I (cross-partition)
4K
ISL1 facility
2K
I
I
IRJE,SNA support
,- POWER/VS SNA support modules
,- GETV1S control storage
,- Remote control block storage
I- SNA unit control blocks storage
I- work area control blocks storage
,- LOGON storage
I- compaction table storage
,- Logical unit name storage
I
13800 Printing subsystem support
I- Work area for 3800 printer
I setup processing
36K
2K
}see
,
z
E
E
~
Figure 2-21
1
I
I
1
I
I
112K
,
Isee note 2
I
t
B
L
G
E
T
V
I
S
--------------------------------------------------------------~~----~-
Note 1: The size of the RDREXIT phase depends on the amount
of user code.
19te_2: The amount of 12K is required for each 3800 printer
Isetup concurrently being processed.
I
1*
Add 4K bytes if the 3800 ICR is installed.
,
Figure 2-1.
14
Structure of the Virtual Partition and Storage
Requirements. The size of the real partition equals the
size of the per.anent plus the size of the fixable area.
POWER/VS Installation Guide and Reference
Type of Storage or Control Block
Remote control block (RKCB) for
all work stations
I
IStorage Requirements in Bytes
RKCB + r*32
(see note)
5NA unit control blocks (SUCBs
and LUCBs) for all work stations
(SUCB+LUCB*SESSLlft(max»*WS
(see note)
Work area control blocks (WACBs)
(SESSLlft(max)+1)*WACB*WS (see note)
LOGON storage for all work
stations
1 page
Co.paction table storage for all
work stations
(0.5r + 2) *2K (see note)
Logical unit name storage
1 page
Legend:
RKCB
==
2K
r
==
Number of remote work stations (remote-IDs or number
of PRKT macros with TYPE==LUT1).
wscount
wscount value specified in POWER macro, SNA parameter.
SUCB
=
192
LUCB
==
160
SESSLIK (max)
==
Highest number of SESSLIM= specifications in all
PRMT macros.
LST
==
Number of logical printers.
station.
IPUN
==
Number of logical punches.
station.
=
lK
I
I
I
IWACB
I
liS
Maximum is 3 per work
Maximum is 1 per work
Number of work stations. Maximum is 200.
(wscount or number of PRKT macros) •
t
1---------------------------------------------------------------------I!Qte: Rounded to the next higher page boundary.
I
Figure 2-2.
Space Calculation for RJE,SNA Support Control Blocks
The virtual partition contains:
•
The Permanent Area. This area of 8K bytes contains the POWER/VS
nucleus-and-control tables.
•
~h~lixA~l~-A~~~.
This area requires a minimum of 2K space fo~
dynamic control blocks and a variable space for data buffers. The
size of the data buffer space depends on user specifications for the
execution processors, RJE lines, and reader and writer tasks. Refer
to Figure 2-3 for storage sizes and calculations.
Chapter 2.
Installing POWER/V5
15
Thg_f~g~~Qlg_!~g~.
This area contains a 142K space for the POWER/VS
basic functions,- plus space for a number of pageable options.
•
The pageable area is optional except for the above 142K which,
together with the permanent and fixable areas, must be part of the
virtual partition.
For POWER/VS with RJE,SNA, the pageable area contains:
A space of 142K bytes for the basic POWER/VS functions
The POWER/VS phases for RJE,SNA.
The GETVIS Area. This area must be provided for RJE,SNA support, or
when using the IBM 3800 Printer.
HQ~:
For RJE,SNA support, you must specify SIZE=192K (as a minimum)
This value is calculated from
the sizes of all required POWER/VS ~odules (RSIZE + basic function
modules + optional function modules).
in the / / EXEC job control statement.
Note:
If the 3800 ICR is installed, add 4K bytes to the base values.
The size of the real partition to be allocated for POWER/VS must
correspond to the size of the permanent area plus the size of the
fixable area.
In other words, the real partition size (RSIZE, see
Figure 2-1) equals 8K bytes plus the size of the fixable area.
POWER/VS does not require any storage from a userls application program
partition running under POWER/VS control.
POWER/VS Component or Task
(Fixable Area)
,storage
IRequirements
lin Bytes
Dynamic control blocks (l'lust always be considered)
2K
SNA control block for RJE,SNA support
192
Each local writer task
(one buffer)
608 1 + 2N + y
Each local writer task
(two buffers)
608 1 + 3N + y
Each local writer task
(four buffers)
640 1 + 4N + Y
Each local card reader task
(one buffer)
576 1 + 2N
Each local card reader task (two buffers)
516 1 + 3N'
Each BSC writer task
608 1 + N
Each SNA writer task
5441 + N
Bse
reader task
516 1 + N
Each SNA reader task
512 1 + N'
Each
Figure 2-3
16
(Part 1 of 2).
Base Values for the Storage Calculation for
the POWER/VS Fixable Area
POWER/VS Installation Guide and Reference
r--------------------------------------------------------------------------,
I storage
I Requirements
POWER/VS Component or Task (Fixable Area)
lin Bytes
Each card reader task (3540 connected)
168 1 + 21 + E
Each 3540 reader task
104 1 + 2N + E
Each execution reader (one per partition)
4q8 1 + N + X
Each execution writer (max. 16 per partition)
448 1 + 2N + Z
First RJE,BSC line
516 1 + P
Each additional RJE,BSC line
288 1 + P
1
If 3800 ICR is installed add 32 bytes.
,Explanation of variables
N
= 32 *
where
n,
DBLK+39
n = ------- (rounded to the next higher integer)
32
DBLK is the value specified in the DRLK parameter of the
POWER macro. The minimum is 544 bytes, the maximum 2088
bytes.
E
= 32 *
where
e,
e = -------- (rounded to the next higher integer)
32
R is the logical record length for the 3540, as specified
P = Terminal buffer size. To process the first SIGNON card,
P = 544 is used.
x
320
Y
= 160
if SLI statements are to be processed; otherwise
X
0 (applicable only for execution readers).
=
if a 3800 printer is being used; otherwise Y
= o.
IZ = 128
if the device to be spooled is a 3800 printer; otherwise
II
Z =
o.
Figure 2-3 (Part 2 of 2).
Base Values for the storage Calculation for
the POWER/VS Fixable Area
Chapter 2.
Installing POWER/VS
17
REQUIREMENTS CALCULATION
STOR~GE
The following example illustrates how to calculate the storage space
required for an individual POWER/VS installation. It is based on the
configuration assumptions given below:
Assumptions
POWE~/VS
1.
Local POWER/VS operation with:
•
•
•
•
•
•
•
2.
One physical reader
Two physical printers
One logical printer per partition
Three partitions controlled by POWERjVS
SLI facility
DBLK=544 bytes
No SPOOL manager support, no user RDREXIT routine, no accounting
support.
RJE,BSC with:
•
3.
is to support the following:
One Bse terminal, for example, an IBM 3780.
RJE,SNA with:
•
One IBM 3770 work station with:
One session (SESSLIM=l)
One logical printer
One logical punch
One logical console
One logical reader
Flow interruption allowed.
•
One IBM 3790 work station with:
Two sessions (SESSLIM=2)
Two logical printers
One logical console
One logical reader
Flow interruption allowed
Logical devices running concurrently.
•
One IBM 3790 work station with:
Five sessions (SESSLI~=5)
Three logical printers
One logical console
One logical reader
LU=(namel, ••• ,name5) specified in PRMT macro
Default compaction table specified in PRMT macro
Logical devices running concurrently.
Figure 2-4 shows the detailed storage calculation for the above
configuration:
18
POWER/VS Installation Guide and Reference
Ref.
,Description
IReal
I Storage
I (in bytes)
I
I
,,
IPageable
I Storage
I (in bytes)
11~-12£g!_fQWERL!~
I
1
I
Real storage:
Permanent area
81t
Fixable area
Dynamic control blocks
2
2K
------------------------------------------------------ -~--------------
1 local writer task with
one print buffer:
608+2*N,
where
544 + 39
N= 32* -------32
=
608
1 824
1 local reader task with
one buffer:
576 + 2
*
1 792
B
3 execution readers:
3 * (448 + 608 + 320)
3 execution writers:
3 * (448 + 2 * 608)
3
4 128
4 992
12 736
,Total for local tasks
Pageable storage:
4
POWER/VS basic modules
5
SLI support
,,
I".z EJEI.BSC
I
I
I
I
I
I
I
I
142K
2K
sug~ort
Real storage:
First RJE,BSC line:
1 120
516 + 544
1
Bse
writer task
608 + N
1 216
Total for BSC tasks
2 336
---------------------------------------------------------------------Pageable storage:
7
RJE,BSC module
Figure 2-4 (Part 1 of 2).
16K
Detailed Storage Calculation Example
Chapter 2.
Installing POWER/VS
19
Ref.
,
I Description
,Real
,Storage
I (in bytes)
1
IPageable
I Storage
I (in bytes)
Real storage:
SNA control block
192
3770:
SNA writer task
(printer, punch, or console)
SNA reader task (console)
1 152
1 120
3790 (2 sessions):
2 SNA writer tasks
(printers and/or console)
I
I
,
2 304
2 SNA reader tasks
(reader and/or console)
I
I
I
1
I
'I
I '
2 240
3790 (5 sessions):
4 SNA writer tasks
(printers and console)
1 SNA reader task
(reader)
4 608
1 120
1----------------------------------------------------------------------1
I
8
,
Total for SNA tasks
,
12 736
I
1---------------------------------------------------------------------I
r
Pageable storage:
r
I
,
I
9
I
I
I
SNA support
1
I
2K
GETVIS control
RMCB:
11712
+
36K
3
SUCB, LUCBs:
(192 + 160
1
* 321
*
5)
2K
*
31
4K
WACBS:
For 3770:
6K
For 3790 (2 sessions) 6K
For 3790 (5 sessions)_2!
118KI
10
2K
lunames (3790):
2K
compaction (1 default):
1«0.5 *3) + 2) * 21
8K
Total GETVIS storage
Figure 2-4 (Part 2 of 2).
20
18K
LOGON
Detailed storage Calculation Example
POWER/VS Installation Guide and Reference
38K
Figure 2-5 is a summary of the detailed storage calculation above.
It
is based on the reference numbers in the leftmost column of Figure 2-4.
Ref.
IDescription
IPageable
IReal
IGETVIS
---------------------------------------------------------------------I
1l!2g1_EQ!ER
1
Permanent
8K
2
Dynamic control blocks
2K
3
Local tasks (in bytes)
12 136
Basic modules
SLI support
5
RJE,BSC
6
BSC tasks (in bytes)
7
RJE,BSC module
2 336
RJE,SNA
8
9
I
I
I
SNA tasks (in bytes)
12 136
I
I
I
,
I
I
I
,
I
t
I
I
I
I
I
I
1
I
I
1
I.
I
1
I
I
SNA modules
I
I
I
GETVIS storage
I
142K
2K
16K
36K
I
38K
----------------------------------------------------------------------1
ITotal
I
38K (*) I
196K
I
38K
I
----------------------------------------------------------------------1
(*) Rounded to the next higher page boundary.
I
I
Figure 2-5.
POWER/VS Storage Calculation Summary
For the described example, you must provide the following storage
allocations for the POWER/VS partition:
ALLOC: 38K + 196K + 38K = 212K
ALLOCR: 38K
The value of the SIZE parameter in the / / EXEC job control statement is
calculated from the ALLOC value .inus the size of the GETVIS area;
hence, for this example, you would have to specify:
/ / EXEC POWER,SIZE=234K
in the POWER/VS start-up job stream.
Chapter 2.
Installing POWER/VS
21
DOS/VS SUPERVISOR GENERATION REQUIREMENTS
To include POWER/iS in DOS/iS, you should consider the following before
generating the DOS/VS supervisor:
•
POWER=YES must be specified in the SUPVR macro; it forces PHO=YES and
NPARTS=3 (if NPARTS was not specified or if NPARTS=1 was specified)
in the SUPVR macro, and PFIX=YES and ECPREAL=YES in the FOPT macro.
•
If POWER/VS accounting support is desired, JA=YES or JA=(n1,n2, ••• )
must be specified in the FOPT macro.
•
If POWER/VS cross-partition communication support is desired, XECB=n
or XECB=YES must be specified in the FOPT macro.
I·
If an IBM 3800 printer is being used, AP=YES must be specified in the
SUPVR macro.
•
If the POWER/VS RJE,SNA support is desired, AP=YES and TP=VTAM .ust
be specified in the SUPVR macro, and one partition aust be available
for VTAM (see the NPARTS= parameter in the SUPVR macro).
•
Both the ALLOC and the ALLOCR macros must be used to define the
POWER/VS partition. Refer to the section "storage Requirements" to
determine the appropriate real and virtual storage sizes.
•
For the POWER/VS partition, the number of LUB entries for programmer
logical units must be large enough to accommodate all reader and
writer tasks that may be running concurrently. The number of LUBs is
specified in the BGPGR or FnPGR parameter of the IOTAB macro. The
default value of 5 is not enough: SYSOOO through SYS006 are used for
POWER/VS system files. These system files must be assigned by the
user.
•
The IBM-supplied distribution medium contains a pre-generated
POWER/VS system that provides the generation parameter default
functions.
SPECIAL CONSIDERATIONS FOR DOS/VS FUNCTIONS
When using POWER/VS, you should be aware of different handling of some
of the DOS/VS functions:
•
In user-written channel command words (CCWs), the following flags are
not supported:
Chain data (CD) - X'80'
Indirect data addressing (IDA) - X·04'.
•
No support is provided for parameter EXCP=REAL.
•
Since POWER/VS is designed as an interface between DOS/VS operating
system and the user's partitions, some DOS/VS commands are affected
in their usefulness by POWER/iS:
ALLOC } Before using ALLoe or ALLOCR, the PSTOP command must be issued,
ALLOCR followed by UNBA~CH.
22
CANCEL
Not valid for the POWER/VS partition.
STOP
If STOP is used, a subsequent PSTOP or PEND command will not
be successful.
POWER/VS Installation Guide and Reference
PRTY
Cannot assign the same or a higher partition priority than
the one in the POWER/VS partition for any POWER/VS controlled
partition.
VTAM AND HCP GENERATION REQU1REftENTS
~he
DOS/VS Virtual Telecoamunications Access Kethod (VTAM) and the
DOS/VS Network Control Progra. (NCP) are required in your DOS/VS
environment if you plan to use POWER/VS with the optional RJE,SNA
support.
Por POWER/VS with RJE,SH1, your generated version of VTAM must meet the
following requirements:
•
osing the APPL definition statement, POWER/VS must be defined to 'TAM
as an application program. The program name must be the sa.e as
specified as the APPLID sub parameter in the 51A= parameter of the
pertinent POWER macro specification.
•
The password specified in the PRTCT= parameter of the APPL macro, if
included, must match the password specified in the SRA= parameter of
the POWER macro specification.
•
The names of the SNA logical units (luname) must be supplied to VTAM
through the LU macro instruction. The logical unit names must be the
same as provided in the PRKT macro as part of the LU= para.eter (if
specified) and in the POWER/VS RJE terminal commands whenever the
value "luname" is requested. !~:t~: Whenever you are requested to
specify the parameter "luna.ell or the LO macro, you must avoid the
use of the parameter values EOJ and ALL.
•
Your system programmer may use the facilities provided by the USS
tailoring services to support a si.plified LOGON procedure~ However,
the Use of U5S depends on the the type of work station: it is
possible for a 3770, but it is not allowed for a 3790. Complete
information concerning the VTAM generation requirements is contained
in the ~S VTAK System Proq~~~s Guide, GC27-6957.
Khen using VTAM, you should consider the following: If the buffer limit
defined for a logical unit has been exceeded, the session with that
logical unit is terminated i •• ediately without an error message.
However, this may only occur in an overloaded system. For details,
refer to the DOS/VS VTAM system Prog~mmer's Guide.
If you plan to use NCP/VS support in your VTAM network, four NCP modules
must be link-edited into the core image library. You can use the 1B8supplied calling book ISTLINK7 for this purpose. The following job
stream is necessary to perform this function:
// JOB LINKEDIT NCP MODULES
// OPTION CATAL
INCLUDE ISTLINK7
// EXEC LNKEDT
/&
This job should be executed after the NCP distribution tape has been
cataloged to your system.
Chapter 2.
Installing POWER/VS
23
Generating POWERIVS
To generate POWERjVS, you must specify parameters of the POWER/VS
generation macros and subsequently process these macros. This section
of the manual describes
•
I ••
The POWER/VS generation macros and their parameters
The POWER/VS phases and their functions
The steps required to generate the system.
POWER/VS GENERATION "ACROS
The following is a description of the three macro instructions that
allow you to generate POWER/VS for your particular installation. For
detailed information on the POWER/VS RJE support, refer also to the
~OWERL!S Work Station User's Guide, GC33-6049.
The three POWER/VS generation macros are:
POWER
for the selection of local support options and for the
inclusion of SNA support.
PLINE
for RJE,BSC support (in addition to the POWER and PRMT macros).
PRMT
for .RJE,BSC or RJE,SNA support (in ad"ition to the POWER and
PLINE macros, if applicable) •
Conventions
•
Uppercase letters, numbers, and punctuation marks must be coded
exactly as shown.
•
Operands can start in any column after the operation code and one
blank space. A card can contain more than one operand.
•
Lowercase letters and words represent information that must be
supplied by the program.er.
•
Options contained in braces {} represent alternatives, one of Which
must be chosen.
•
Brackets ( ] indicate that the element they enclose is optional.
stacked options contained within brackets
represent alternatives, one and only one of which may be chosen. The
brackets themselves are for descriptive purposes only, and must not
be coded.
•
Default values are underlined.
•
No comma is used before the first parameter specified.
•
Keyword parameters consist of a keyword, followed by one or more
values.
•
Positional parameters must appear in a specified location, relative
to other parameters.
24
POWER/VS Installation Guide and Reference
The POWER macro and its parameters are sufficient to generate a non-RJE
system. with the parameter SNA= (see below), this .acro also provides
support for an RJE,SNA system. For an RJE,BSC system, the PLINE and
PRMT macros are required additionally. In an RJE,SNA environment, the
PLINE macro does not apply; but the PRMT macro must be used. These
'
macros are described later.
,
IName
loperation
IOperands
Icol
I
I
I
172
I
n
I
If ,TRACKGP={Q}J
I
n
I
I
I
)---------------------------------------------------------------------POWER
I[ DBLK={Q}J
I[ *]
IEQ!~B
name
I[ *]
I[ ,LTAB=fJ10.00,02L~15,20,25,~~}
l(dO,d1,d2,d3,d4,d5,d6,d7,d8,d9,
!!.~50,56)
}]
d10,dl1,d12)
{
1[*]
I
[*]
['PJlI={~}]
[*]
( ,SUBLlB::: {!O}J
(*]
[ ,ACCOUNT:: {NO
YES
( ,STDLINE=
I
I
I
}l
[*]
{JQ.L.21}
]
(n ,m)
[*]
[*)
[ ,STDCARD={JQL2l}J
(n ,m)
f
I
I
I( ,JLOG={YE~}]
I
NO
I
I [ ,JSEP=
r
[* ]I
I
I
[*] I
{JQ.LQl}
]
(n ,
,
m)
I(II ,RBS= {~Ql}]
(n,m)
I
[*]
} J
name
[*]
I( ,RDREXIT={NO
I
I
I( ,PAUSE={!Q }]
I
YES
I
(*]
I[ ,SPOOL={HQ }l
I
[*)
YES
(continued on next page)
Chapter 2.
Installing POiER/VS
25
continued:
r-----------------------------------------------------------------------'---,
Name
IOperation
IOperands
I Col
I
172
1
![,SNA=([{'Wscount
J, ( password
,
no. PRKT with LUTl}
1
[ ,{apPlid}]) ]
r
fQll!
1
I [ ,FEED={YES}]
1
!ill
r
J
[*J
[*]
[*]
1[,MULT12={YES})
NO
[* ]
I[,COPYSEP={YE~}]
[*J
,
[*]
1
I
I
NO
I
r [ ,CLRPRT={YES}]
r
NO
1
I
I
1
I [ , PIRKFRK={YES})
I
tNO
~-------------------------------------------------------------------------~
name
specifies the phase name to be included in the PHASE card
generated as the first card in the object deck resulting
from this assembly.
The phase name consists of 1 to 7
alphameric characters, the first of which must be
alphabetic.
If no name is specified, the name POWER is assumed as
default.
DBLK=
specifies the block size of data file records (both disk
and tape) and, consequently, the size of each data
buffer. Data buffers are used as I/O areas by the
execution processors, readers/writers and RJE routines.
The value n must be an integer from 544 to 2008; however,
if you have IBPI 3211 printers installed and wish to use
the * $$ LST (* $$ PRT) statement with the UCS parameter
option, the value n must be an integer from 608 to 2008.
If DBLK is omitted or set to 0 and a cold start is
performed, the system assumes a block size appropriate to
the device type used for the data file, which is shown
below:
•
IDevice Type
•
IData Block Size
I
!
I
I
I
I
I
I
1-----------------------------------1
12314
!
920
I
13330
13330 Model 11
13340
13350
•
952
952
808
960
!2t~:
1
•
When you are generating two or more POWER/VS
systems and plan to transport disk or tape intermediate
storage between the systems, you must specify identical
block sizes in all these systems to avoid block size
incompatibility problems.
26
POMER/VS Installation Guide and Reference
TRACKGP=
specifies the number of tracks in a track group. A track
group is the amount of disk space that POWER/VS allocates
upon a request for space by any POWER/VS routine. The
value n may be any integer from 1 to the number of tracks
on a cylinder of the device assigned to the data file.
If the TRACKGP parameter is omitted or set to 0 (or if
conflicts are detected during initialization) and a cold
start of POWER/VS is performed, the system calculates a
suitahle track group size. When a warm start is
performed, the track group size estahlished at the
previous cold start is used.
!2!~:
The maximum numher of track groups is the number
of track groups per cylinder times the number of
cylinders. The numher of track groups per cylinder is
the numher of tracks per cylinder divided by the track
group number. The remainder is ignored.
LTAB=
describes the forms control tape or the forms control
buffer of the printers. If LTAB is specified, all
entries in the suhlist (dO through d12) must be present.
Each entry is specified as two digits. The sum of dO and
d12 is considered to be the page depth (= number of print
lines on each page). If channel 12 is not specified
(d12~OO), the value specified by dO is taken to be the
page depth.
!Q1~:
For FCB printers POWER/VS will load the default
FCB if none is specified. The LTAB used for the current
POWER/VS job will be updated by the FCB load routines,
but the value specified here will remain in effect as
long as POWER/VS is active.
PRI=
specifies the default priority of a job entry when a
priority is not specified in the * $$ JOB statement. The
value n may be any digit from 1 to 9, where 9 is the
highest priority. If PRI is not specified, the default
value is 3.
SUBLIB=
specifies the sublibrary of the source statement library
to be searched when the sublibrary is not specified in
the
$$ SLI statement.
The value s may be A through Z,
o through 9, $, I, or~. You should note, however, that
sublibraries A, C, D, E, F, and Z are already specialpurpose libraries in DOS/VS. If omitted or if SUBLIB=NO
is specified, SLI statements will be treated as data.
*
ACCOUNT=
specifies whether POWER/VS is to maintain accounting
information. If NO is speCified, no POWER/VS accounting
information is maintained. If YES is to be effective,
the DOS/VS supervisor must support the job accounting
interface (see the JA parameter in thePOPT macro). All
accounting information is stored in the POWER/VS account
file IJAFILE. If you want job accounting while POWERjVS
is active, you should specify ACCQUNT=YES in order to get
a correct SIO count.
Chapter 2.
Installing POWER/VS
27
STDLINE=
n specifies the number of list records that may be
printed for a job entry before a warning message is
issued to the operator. m specifies the additional
number of list records that may be printed before the
same message is reissued. Both nand m may be up to 6
digits.
A specification of 0 means that no warning will be given.
If one of the entries is omitted, the value provided is
used for both entries, as shown in the example below:
STDLINE=(,800)
generates STDLINE=(800,800)
STDLINE=(10000) generates STDLINE=(10000,10000)
STDLINE=12000
generates STDLINE=(12000,12000).
If STDLINE is omitted, (0,0) is assumed.
STDC~RD=
n specifies the number of records that each job entry may
punch before a warning message is issued to the operator.
m specifies the adJitional number of records that may be
punched before the same message is reissued. Both nand
m may be up to 6 digits.
A specification of 0 means that no warning will be gi~en.
If one of the entries is omitted, the value provided is
used for both entries in the same way as shown for
STDLINE. If STDCARD is omitted, (0,0) is assumed.
JLOG=
specifies whether POWER/VS is to display each jobname
together with the job number whenever a * $$ JOB
statement is read in a partition under POWER/VS control.
If YES is specified, all such statements will be logged
on the system console (SYSLOG). If NO is specified, no
such logging will take place. If this parameter is
omitted, JLOG=YES is assumed as default.
JSEP=
specifies that special pages or cards be included in the
output to separate job entries. n specifies the number
of separator pages. m specifies the number of separator
cards. nand m may be any digit from 0 to 9. The
minimum number of separator cards is 3. For print
output, one additional page as specified by n will be
printed. If JSEP is omitted, (0,0) is assumed.
The JSEP specification can be overwritten by a JECL
statement for a particular job.
!Q!~:
Stacker selection is ignored if job separation is
requested. The default stacker for the given device is
used instead.
Separator pages are printed with the line depth in effect
during job execution. The line depth is obtained from
either the printer forms control buffer (FeB) or from the
LTAB values in effect at that time. If the page size
differs from the line depth, the printout will not be in
the correct format.
28
POWER/VS Installation Guide and Reference
RBS=
specifies the nu.ber of list pages (n = number of skips
to channel 1) and the number of punch cards (m = number
of cards) that can be processed before the output is
segmented. This parameter is used only when spooling to
disk intermediate storage. nand m may be from one to
six digits. A specification of 0 means that no
segmentation will take place. If RBS is omitted, (0,0)
is assumed. This parameter is ignored when DISP=T is
specified in the * $$ LST (* $$ PRT) or * $$ PUN command.
For segmentation on a 3525, and when using print
co.mands, all segments must be punched in a row, or
separator cards must be specified. This avoids loss of
the last two print lines.
!Q~g:
RDREXIT=
specifies whether a user-written POWER/VS reader task is
supported. Upon initialization of POWER/VS, the phase
with the name specified in the RDREXIT parameter 1S
loaded into the POWER/VS partition. If this parameter is
omitted, it is assumed that no user-written reader task
exists.
For a detailed description of the reader exit routine
refer to Appendix E.
PAOSE=
specifies whether a punch writer task is to wait before
every punch job entry. If NO is specified, the punch
writer task will not wait. This is also the default
assumption if this parameter is omitted. If PAUSE=YES is
specified, the punch writer task will cause message 1Q40A
to be displayed before each job entry. Punched cards can
then be taken from the stacker of the punch device. To
reactivate the writer task, issue a PGO command.
SPOOL=
If YES is specified, the POWER/VS cross-partition
communication macros PUTSPOOL, GE~SPOOL, and CTLSPOOL are
supported. If NO is specified, no interface is
supported. This is the default assumption. If
SPOOL=YES, then XECB support must be specified in the
supervisor.
SNA=
specifies parameter values for the POWER/VS RJE,SNA
support. The meaning of the positional snbparameters is
as follows:
~§£2Yn!
allows you to optionally control the reservation
of the GETVIS pool size for SNA work station control
blocks (SUCBs, LUCBs). The GETVIS pool size is
calculated and the space reserved during POWER/VS
initialization.
Any value from 0 to 200 may be specified.
this operand, consider the following:
1.
When coding
A default value of 0 is assumed if this operand is
omitted or invalidly specified. In this case, the
GETVIS pool size is calculated from the total number
of SMA work stations and the largest SESSLIM= value
s~ecified in the PRMT macro.
The largest SESSLI!=
value is used to avoid fragmentation.
Chapter 2.
Installing POWER/VS
29
2.
If a value is specified that is smaller than the
total number of work stations defined in the PRMT
macro, this wscount value is taken during POWER/VS
initialization to calculate the GETVIS pool size for
SUCBs and LOCBs. This smaller wscount value can
limit the number of work stations and sessions that
can log on concurrently because the GETVIS pool size
is reduced. The limitation depends on momentary
system conditions.
3.
If a value greater than or equal to the number of
work stations defined in the PRMT macro is specified,
the information in the PRMT macro is used to
calculate the GETVIS pool size.
~s2§word
- This specifies the password (1 to 8
characters) to be used by POWER/VS when it issues an OPEN
call for a VTAK ACB. This password must be identical to
the password specified in the PRTCT operand of the VTAM
APPL statement. If no password was specified in the
PRTCT operand, the password specified in the SNA
parameter is ignored during POWER/VS execution.
~Dlid - This identifies the POWER/VS application name
used to establish the VTAM API. This name must be
identical to the name specified to VTAM during the VTAM
generation. If this subparameter is omitted, the name
POWER is assumed as default.
Note: If you want to omit subparameters of the SNA=
parameter, you must sUbstitute each omitted subparameter
by a comma unless the omission occurs at the end of the
parameter list.
nn21§:
SNA=(wscount"applid)
SNA= (, ,applid)
SNA= (wscount)
SNA~(wscount,password)
FEED=
determines the POWER/VS default to eject the previous and
feed a new 3540 diskette at end-of-file of the previous
one. This default may be overridden by a JECL statement.
MULT12=
provides the option for the repeated posting of the
printer channel 12 condition on each page to offer
compatibility for DOS/VS POWER users.
The repeated posting of channel 12 (also referred to as
multiple channel 12 posting) means that once channel 12
has been reached, each subsequent line being printed on
the same page will signal the channel 12 condition to the
user program until channell has been reached.
If KULT12=NO is specified explicitly or by default, the
channel 12 condition is indicated to the user program
only once when channel 12 has been reached, but not when
subsequent lines are printed on the same page.
~ultiple channel 12 punches may be specified in a FCB
phase, however only the last channel 12 location will be
recognized.
!Qte: If MULT12=YES is specified for an PCB-type printer
program output aay be different from that output,
received when running under DOS/VS, not using POWER/VS.
30
POWER/VS Installation Guide and Reference
COPYSEP=
specifies whether POWER/VS should produce separator
pages/cards between each copy of an output file. If NO
is specified, the separator pages/cards are suppressed.
If YES is specified, separator pages/cards are included
between each copy of an output file. However, copy
separation is done only for a nonzero JSEP specification,
defined either during POWER/VS generation or in a JECL
statement.
If this parameter is omitted, COPYSEP=YES is the default.
The COPYSEP specification can be overridden by a JECL
statement.
CLRPRT=
1
specifies whether POWER/VS is to clear the page buffer of
the IBM 3800 Printer at end of job and is to wait until
printing of the job is complete. If NO is specified,
POWER/VS begins to fill the page buffer with the next
job's output without waiting for completion of the
printing of the previous job. If YES is specified, the
page buffer of the 3800 is cleared at end-of-job. If
this parameter is omitted, CLRPRT=YES is the default.
HQte:
If you specify CLRPRT=NO, be aware that if an
error occurs on the 3800 while printing the previous job,
the result may be incomplete. The previous job would
already have been dequeued according to its disposition
and POWER/VS is not able to reprint any lost data.
However, if you define the disposition K in the * $$ LST
statement, the output remains in the LST queue after
processing. After verification that the output is
complete, the operator can then delete the output job
from the queue.
specifying CLRPRT=YES may degrade performance of the
3800, because the printer must wait for the page buffer
to be emptied.
MRKFRM=
1
specifies whether the Mark Form function ·of the IBM 3800
Printer is used when producing job separator pages. If
NO is specified, POWER/VS includes job separator pages
according to the number of separator pages specified
during POWER/VS generation or in the JECL statement. If
YES is specified, POWER/VS creates only one separator
page and then issues the Mark Form channel command, which
causes a row of dark marks to be printed on the
perforation between pages. The 3800 reproduces either
three or five copies of the separator page (depending on
the page size) with the black marks printed on the
perforations. The printer then produces a sufficient
number of blank pages to advance the last row of black
marks beyond the fuser station.
The MRKFRM option is activated only when job separator
pages are to be printed. If the parameter is omitted,
ftRKFRM=YES is the default.
POWER/VS uses the Mark Form function of the 3800 only
when producing start separator pages.
(The separator
pages between copies are also considered as start
separator pages.) When producing end separator pages,
POWER/VS reprints the separator page according to the
JSEP specification.
(1)
Operand is valid only for the IBM 3800 Printer.
Chapter 2.
Installing POWER/VS
31
The PLINE macro instruction and its parameters define the hardware
characteristics of an RJE,BSC line, that is, the integrated
communication adapter or the control unit. The PLINE macro(s) must
follow the POWER macro and precede the PRaT macro(s).
One PLINE macro must be specified for each line.
are supported by POWER/VS.
Op to 25 RJE,BSC lines
i
I
IName
loperation
IOperands
ICol1
I
I
I
172 I
1------------------------------------------------------------------I
PLINE
ADDR=X'cuu'
(*] I
I
[ ,SWITCH=/!Q }]
lIES
(*] ,
[ ,TIMEOUT= {~o}]
[*)
(,PSWRD=password)
[*)
,
I
'TRNSP={~~S})
[*J
[ ,CODE={EBCDIC}J
ASCII
[*]
[
![ '1I0DSE1'={!:})
I
I
BA
BB
ADDR=
specifies the line address (channel and unit number) of
the control unit. This address is the same as used to
identify the control unit to DOS/VS. This parameter is
required. Although hexadecimal notation is not required,
note that a decimal address will be converted to
hexadecimal (that is, 030 is assembled as X'OlE') •
SWITCH=
specifies whether a switched or leased line connection is
being used. A specification of 5WITCH=NO indicates
leased line operation, which is the default assumption.
SWITCH=IES indicates switched line operation.
TIMEOUT=
specifies the number of minutes the terminal is allowed
to remain idle before SIGNOFF is forced. The value n may
be any number from 0 to 255. If NO is specified or this
parameter is omitted, the terminal is allowed to remain
idle for three minutes. This parameter is useful to save
line charges on switched lines.
!2!~:
Forcing SIGNOFF to an inactive terminal is not
only desirable because the terminal may be keeping a
switched line busy, but also because the CPU is then
processing timeouts every three seconds. In such a case,
the user aay be charged for unused line or CPU tiae.
32
POWER/VS Installation Guide and Reference
PSiRD=
specifies the security password to be submitted by the
remote operator whenever he wants his terminal to be
connected to the central system. The password may be up
to 8 characters in length.
It may be overridden (until
the next PSTOP command) by the central operator via the
PSTART cOllmand.
TRNSP=
specifies the transparency feature on the integrated
communication adapter or the transmission control unit.
This feature is required for transmission of object
decks.
NO may be specified only if no object decks are to be
transmitted over the line. All data characters between
X'OO' and X'40' are then converted to zeros, when
transmitting to the terminal.
-...
CODE=
specifies the transmission code, which may be either
EBCDIC or ASCII.
MODSET=
Specify this parameter only when using a 2101 control
unit. The first character of the operand specifies
Interface A or B, when a dual communication interface is
used. The second character specifies code A or B, when
the Dual Code feature is installed. Refer to the
component description of the IBK 2701 Data Adapter Unit,
GA22-6864, for more details.
The PRKT macro and its narameters define the hardware characteristics of
an RJE terminal, identify the user, and describe where his output is to
be routed.
At least one PRMT macro must be supplied for each user, and
all PRMT macros must be supplied after the PLINE macro(s), if present.
The PRKT macros must be specified in ascending sequence according to
their remote-IDs (see the REMOTE= parameter below), and the definitions
for non-SNA remote-IDs must precede the definitions for SNA remote-IDs.
If any feature is specified for a terminal on Which the feature is not
supported, the parameter is ignored.
Chapter 2.
Installing POWER/VS
33
,
Name
rOperation
rOperands
I
I
Used in ICol
112
REftOTE=nnn,
SNA,BSC
*
2770}
2180
TYPE= 3741
{ 3780
LOTl
SNA,BSC
[*]
[,LSTROUT={remid}]
lUll!
SNA,BSC
[*)
[,PUNROUT={remid})
nnn
SNA,BSC I[ *]
[,REF=mllm)
SNA,BSe
(* )
( ,CONSOLE={~~S}J
SNA
[*]
[,PSWRD=password]
SNA
[*)
[ ,SESSLIM={i)]
SNA
[*]
(,eMPACT=name]
SNA
[*]
[ ,LU= (name,name,nalle, ••• ) ]
SNA
[name] PRftT
'LIST={l~~}]
J(
*]
Bse
[*]
[ ,TRNSP=={NO }]
I£;§
Bse
[*]
('BE={i~S)]
BSC
(*]
[ ,HFC={;~S})
Bse
[*)
I( ,SCE={YES}]
BSC
[* J
I[ ,ABE={YES}]
BSC
[*)
BSC
(*)
[
144
120
I
t
l'!Q
I
!!Q
I
I [ ,MRF={YES})
I
RQ
I
'[ ,CS={YES}]
NO
I
I
I[ 'T~ACE={YES}]
I
34
!2
POWER/VS Installation Guide and Reference
BSC I[ *)
I
I
BSC I
I
If the terminal characteristics of a given terminal or work station to
be described by a PRMT macro are identical to those specified in a
preceding PRftT macro instruction, a short form of this macro may be used
(see also the explanation for the REP parameter). The short form of the
PR~T .acro includes the following parameters:
r----------------------------------------------------------------------------,
Name
IOperation
,Operands
Used in IColl
I
,
I
I
I[ , LSTROUT={rellid1 ]
172
I
,
I
----------------------------------------------------------------------1
[ naae ) I PRMT
I REMOTE=nnn[ name]
SN A, BSC I[ * J I
I
,
I
I
,
I
I
SNA, BSC t[ *) I
I!!1!!!J
,
1( ,PUNROUT={remid \. ]
,
nDn J
,
,
,
SNA, BSC I[ *]'
I[ ,REF=mmm]
SNA, BSC,
1
I
I
,
,
I
I
~____________________________________________________________________________J
REMOTE=
specifies the remote-ID ("remid") identifying an RJE
terminal (BSC terminal or SMA work station) to which the
specifications apply. The value nnn is a decimal integer
in the range from 1 to 200. The first remote-ID should
be specified as 1; any succeeding remote-IDs must be
incremented by 1. The lowest SNA remote-ID must be
greater than the highest BSC remote-ID. All following
SNA remote-IDs must be in consecutive ascending order.
Note: If REMOTE=1 is specified, the parameter REF=
cannot be used.
I
TYPE=
specifies the type of terminal, which may be a 2770,
2780, 3741, 3780, or an SNA terminal. For 3110, specify
TYPE=2770 or 3780 depending on the buffer size. For SMA
support, the terminal .ust always be specified as LUT1.
LST"tOOT=
specifies where the list output from jobs submitted by
this remote-ID is to be routed by default. If this
parameter is omitted, the same remote-ID as specified in
the value nnn of the REMOTE parameter is assumed.
PUNROUT=
specifies where the punch output from jobs submitted by
this remote-ID is to be routed by default. If this
parameter is omitted, the same remote-ID as specified in
the value nnn of the REMOTE parameter is assumed.
REF=
specifies the remote-ID of another PRMT macro, which
describes the terminal or work station characteristics of
this PRMT macro. The value mmm can be any integer lower
than the value nnn used in the REMOTE parameter.
'mmm'
can therefore be in the range from 1 to 199.
Parameters other than REMOTE=, LSTROUT=, and PUNROUT are
ignored when specified in a PRMT macro with REF=mmm.
MNOTE statements in the Assembly listing inform you about
this fact.
Note: Check the referenced PRMT macro instruction for
correct assembly. No warning is issued in the referring
macro if the Deferenced macro is in error.
Chapter 2.
Installing POWER/VS
35
CONSOLE=
may only be specified for an SNA work station and only if
this work station has a line printer in addition to the
normal terminal console.
YES causes POWER/VS to interrupt the outbound printer
flow whenever messages are generated for the remote
operator unless a free session is available with the work
station (MLU environment only). For multiple logical
units, messages are always sent when a free session is
found, regardless whether or not jobs are being
transmitted, even if CONSOLE=NO is specified.
For single logical units, NO prevents POWER/VS from
interrupting an outbound printer flow for the
transmission of messages to the remote operator.
In this
case, the messages are collected and submitted to the
operator after POWER END OF JOB has been reached.
If the SNA configuration does not contain an additional
line printer and CONSOLE=YES has been specified, the
printout will contain interspersed messages to the remote
operator.
If this parameter is omitted, CONSOLE=NO is assumed as
default.
!Q~:
For the 3790, CONSOLE=YES should always be
specified.
PSWRD=
specifies the security password that may have been
defined for the remote work station being described. The
password must match the password contained in the user
data of the LOGON command.
If the password is invalid,
it is set to blanks, and an MNOTE statement will appear
in the Assembly listing.
SESSLIM=
specifies the maximum number of sessions that may be
logged on by an SNA work station.
Any value from 1 to 6
may be specified.
If this parameter is omitted or invalidly specified, the
value 1 is assumed as default.
CMPACT=
specifies the default name of the compaction table to be
used for a work station if no compaction table is called
for in the * $$ LST or * $$ PRT statement. Data
compaction can be requested by means of a JECL statement
even though no compaction was selected originally, either
by default or explicitly.
The name of the compaction
table may be up to 4 characters long; the first character
must be a letter (A through Z) or a $, a ~, or a ••
LU=
specifies a list of secondary logical unit names that may
log on using the remote-ID specified in the REMOTE=
parameter. These names must be specified in accordance
with the definitions for VTAM.
If this parameter is
specified, LOGON requests for a given remote-ID will only
be accepted if the name of the logical unit attempting to
log on appears in the list of logical unit names for this
remote-ID. If the name is not contained in the name
list, the LOGON request is rejected.
36
POWER/VS Installation Guide and Reference
If this parameter is not specified, no logical unit name
test is performed during the LOGON procedure.
Note: The number of names to be specified for one
remote-ID may be larger than the number specified in the
SESSLI! parameter. The number of logical unit names is
only limited by the DOS/VS Assembler restrictions.
LIST=
specifies the number of print positions in a line. Any
number can be used from 80 to 150. The maximum value is
that of the maximum nUBber of print characters per line
of the printer. The following maximum values of LIST
apply: 144 for the 2770, 2780, and 3780; 126 for the
3741.
!Qte: For the 2770 and 132 print positions, the buffer
expansion feature is reguired and must be specified with
the parameter BE=YES.
TRNSP=
specifies the transparency feature on the terminal. This
feature is required for the transmission of object decks.
NO may be specified only if no object decks are to be
transmitted to this terminal. All data characters
between X'OO' and X 1 40' are then converted to zeros, when
transmitting to the terminal.
BE=
specifies buffer expansion, which applies to the 2110
only. The size of the buffer is then 256 bytes.
BE=YES or ABE=YES are necessary if LIST=132 is specified.
HFC=
specifies horizontal format control on the 2770 and 2780.
Horizontal for.at control is a standard feature of the
3780; a specification of HFC, irrespective of the operand
(NO or YES), is ignored.
!Q!~:
If HFC and SCE are both specified, HFC is ignored.
SCE=
specifies space compression/expansion, which applies to
the 2770 and 3780 only.
ABE=
specifies additional buffer expansion for the 2770.
size of the buffer is then 512 bytes.
MRF=
specifies the multiple record feature for the 2780 only.
CS=
specifies the component selection feature on the 3780
terminal. Required if a 3181 punch is connected to the
3780.
TRACE=
specifies that all I/O interrupts and timeout records for
RJE,BSC lines are to be traced for this terminal as soon
as this remote-ID signs on. For more information on this
I/O trace, refer to the DOS/VS POWER/VS Logic manuals,
SY33-8576 and SY33-8577.
Chapter 2.
Installing POWER/VS
The
37
Following are two examples of macro definition sequences for the
generation of POWER/VS systems.
~!~mEl~-1.
NAMEl
*
POWER with RJE,BSC and RJE,SMA support:
POWER SNA= (3)
PLINE
PLINE
PLINE
PLINE
PRMT
PRMT
PRI1T
PRI1T
PRMT
PRKT
PRI1T
~~~mEl~-1.
NAME2
ADDR=x'cuu'
ADDR=x'cuu'
ADDR=x'cuu'
ADDR=x'cuu'
REMOTE=1,
TYPE=2780
REMOTE=2,
TYPE=2770
REMOTE=3,
TYPE=3780
REMOTE=4,
TYPE=2770
REMOTE=5,
TYPE=LUT1,
CONSOLE=YES
REMOTE=6,
TYPE=LUT1,
CONSOLE=YES
REMOTE=7,
TYPE=LUT1,
CONSOLE=YES,
SESSLIM=4,
CMPACT=TEXT
UP TO 4 WORK STATIONS KAY BE LOGGED
ON CONCURRENTLY
DEFINES BSe LINE
DEFINES BSC LINE
DEFINES BSC LINE
DEFINES BSC LINE
DEFINES BSC REMOTE USER
DEFINES Bse REJliOTE USER
DEFINES BSC RErtOTE USER
DEFINES BSC REMOTE USER
DEFINES SNA REMOTE USER
DEFINES SNA REMOTE USER
DEFINES SMA REI10TE USER
POWER with RJE,SNA support only:
POWER SNA=(3"POW)
PRl"IT REMOTE=l,
TYPE=LUT1,
CONSOLE=YES,
SESSLIM=5
PRMT REMOTE=2,
TYPE=LUT1,
CONSOLE=YES,
SESSLIM=2,
CMPACT=TEXT,
1U= (LUO 1, LU02)
PRMT REMOTE::::3,
TYPE=LUTl
PCPTAB Macro
By means of the PCPTAB macro, you define a compaction table set for the
POWER/VS SNA support. Any number of compaction tables may be generated
for a specific PO~ER/VS installation; they are identified and referred
to by their names.
compaction tables need not be generated during the POWER/VS system
generation. They can be provided at any time, as required. For more
information on compaction tables refer to "Data Compaction" in
Appendix A.
38
POWER/VS Installation Guide and Reference
To code the parameters of the PCPTAB macro correctly, consider the
following:
The maximu. length of a character string defined as an operand of a
System/370 Assembler instruction is 255 bytes. This means that, in the
80-column card image format, the operands of th~ NOMASTn parameters may
have to be continued in subsequent continuation cards pertaining to the
same parameter. Any card 'that is to be continued on a subsequent card
.ust have a nonblank continuation character in column 72. The asterisks
shown below (in brackets) in column 72 of the macro format description
indicate that new parameters may follow.
Name
name
loperation
I
IOperands
I
leol
IpePTAB
I
I
I
I
I
I
I MASTER=(mcl, ••• ,mc16)
I
I[ ,NOMAST1= (nme (ll , ••• ,nme (n» ]
1
I[ ,NOMAST2= (nmc (n+1) , ••• ,nmc (p) ) )
I
I[ ,NOllAST3= (nmc (p+l) , ••• ,nme (q» ]
I[ *]
P~ogramming
172
I
I[ *]
I
I [*]
I
I
Notes:
name
specifies the symbolic name of the compaction table. The
name may be from one to four characters long; the first
character ~ust be alphabetic (A-Z, $, m, or #). During
POWER/VS generation, this name will become the phase name
of the default compaction table. If no name is
specified, PCPT is used as the name.
PlASTER=
specifies the set of master characters. From 3 to 16
master characters may be specified. For details
concerning the selection of master characters, refer to
Appendix A. The master characters can be specified as
character or hexadecimal values in any sequence,
separated by commas; for example, MASTER=(A,B,40,D,7F).
NOMASTn=
specifies the set of non-master characters. The number
of non-master characters to be specified depends on the
number of master characters defined in the MASTER=
parameter. I f . is the number of master characters and
nm the required number of non-master characters, then
-
•
If m = 16, then nm = 0
•
If ..
< 16, then nm =
256 -
m(11+1) •
For details concerning the selection of non-master
characters, refer to Appendix A. The non-master
characters can be specified as character or hexadecimal
values in any sequence, separated by commas; for example,
NOMAST1=(X,N,3A,1C,BO,H) •
The maximum length of the character strings that may be
specified in the NOMSTn= parameters is 255 bytes,
including the separating commas and the enclosing
parentheses. However, you may continue the non-master
character specifications of, for example, NO!AST1= by
using the NOMAST2= parameter even though the maximum
string length in NOKAST1= has not yet been reached.
Chapter 2.
Installing POWER/VS
39
A number of rules apply for the character specifications of the KASTER=
and NOMASTn= operands. These are:
•
A master or non-master character must not be specified more than
once.
•
The following characters, if specified as master or non-master
characters, must be enclosed in single quotes when specified in
character notation in the respective operands:
Left parenthesis:
IC'
Right parenthesis:
') I
Comma:
Blank:
•
•
,,
,
.
.
or hexadecimal 4D
or
he~adecimal
5D
or hexadecimal 6B
or hexadecimal 40.
The following characters, if specified in character notation as
master or non-master characters, must be specified twice while th~y
count as one:
Ampersand:
&&
or hexadecimal 50
Quote:
I •
or hexadecimal 7D.
For performance reasons, forms-feed and new-line (FF (X'OC') and NL
(X ' 1S'»
characters should be specified as non-master characters.
Select-channel characters (SELn or X'04' and SEL2 through SEL12 or
X'82' through X'7C') and the carriage~return (CR or X'ODI) character
should be specified as required.
(Refer to "Outbound Print Data" in
Appendix A).
After assembly, the resulting object module must be link-edited and
cataloged in a core image library (system or private) with the phase
name specified in the name field of the PCPTAB macro.
40
POWER/VS Installation Guide and Reference
POWER/VS PHASES
The system co~e image library of the DOS/VS system contains one version
of POWER/VS, which is generated with default values for all macro
options and is cataloged under the phase name POWER. The names of the
phases that constitute POWER/VS are listed in Figure 2-6~
•
I Phase Name
I
I Function
I
1----------------------------------------------------------------------1
Initialization and termination
$$BPOWIN
$$BSGftNT
IPW$$AQ
IPW$$AS
IPW$$CP
IPW$$DD
IPW$$DQ
IPW$$ER
IPW$$FQ
IPW$$GA
IPW$$GD
IPW$$IB
IPW$$IC
IPW$$I1
IPi$$I2
IPW$$LF
IPW$$LH
IPi$$LN
IPW$$LR
IPW$$LU
IPW$$LW
IPW$$MD
IPW$$M.P
IPW$$MS
IPi$$NQ
IPW$$NU
IPW$$OB
IPW$$OC
IPW$$OE
IPW$$O'l'
IPW$$PA
IPW$$PD
IPW$$PL
IPW$$PP
IPW$$PR
IPW$$PS
IPW$$RQ
IPW$$SA
IPW$$SC
IPW$$SL
IPW$$Sft
IPW$$SN
IPW$$TM
IPW$$TR
IPW$$VE
IPW$$XJ
IPW$$XR
IPW$$XW
POWER
output setup for unit record (macro-called)
Add to queue
Asynchronous service function (for 3800 printer only)
Command processor
Display POWER/VS files
Delete from queue
3540 physical reader
Free queue
Get account record
Get da ta reco rd
Inbound processor
Initiate command processor
Initialization
Initialization
Logoff processor
SNA logon processor 1
SNA logon processor 2
Logical reader
LUB and POB routines
Logical writer
Message definition
Message processor
Remote message handler
Next from queue
Nucleus
Outbound processor
Outbound compaction
Open 3540
Open tape
Put account record
Put data record
Physical list
Physical punch
Physical reader
Print status report
Reserve queue
Save account record
Scan and check parameter
Get source library record
Spool management
SMA manager
Remote job entry
Task termination
VTAM exits
Execution JECL analysis
Execution reader
Execution writer
Minimum POWER/VS system
L
Figure 2-6.
POWER/VS Phase Names and Their Functions
Chapter 2.
Installing POWER/VS
41
POWER/VS GENERATION PROCEDURE
This section describes four steps for generating POWER/VS:
1.
Select the various macro options as required. For this purpose, use
a copy of the coding work sheet illustrated in Figure 2-7 to record
your choices.
2.
Assemble the POWER/VS generation macros, which create the POWER/VS
generation table. The resulting object module contains the code
necessary to invoke the POWER/VS initialization module.
3.
Link-edit the object module to the system core image library.
4.
For ease of serviceability, check if the translating system dump
transients are still in the core image library.
After generation, POWER/VS can be initialized by the start-up procedures
described in Chapter 4 of this manual.
I
IColumns
11
r
110
116
172
1---------------------------------------------------------------------luser-name IPOWER
IDBLK=
I
f---------------------------------------------------------------------I
I TRACKGP=
I
fLTAB=
IPRI=
ISUBLIB=
I ACCOUNT=
ISTDLINE=
ISTDCARD=
IJLOG=
IJSEP=
IRBS=
IRDREXIT=
IPAUSE=
ISPOOL=
ISNA=
IFEED=
IMOLT12=
ICOPYSEP=
Figure 2-7 (Part 1 of 2).
42
Work Sheet for Coding POWER/VS Generation
ftacros
POWER/VS Installation Guide and Reference
r--------------------------------------------------------------------------------------------,
Columns
1
172 t
1
110
116
user-name
IPRltT
IREMOTE=
----------------------------------------------------------------------1
I cont • d ,CLRPRT=
,
I
----------------------------------------------------------------------1
I
I MRKFRM=
I
I
----------------------------------------------------------------------f
IPLINE IADDR=
1
I
----------------------------------------------------------------------1
1
ISWITCH=
I
I
----------------------------------------------------------------------1
I
1TIMEOUT=
I
I
----------------------------------------------------------------------1
1
IPSWRD=
I
I
----------------------------------------------------------------------1
,
!TRNSP=
1
1
----------------------------------------------------------------------1
I
ICODE=
I
I
----------------------------------------------------------------------1
r
I MODSET=
' I
,TYPE=
I
ILSTROUT=
1
t---------------------------------------------------------------------1
IPUNBOUT=
I
---------------------------------------------------------------------'REF=
ICONSOLE=
IPSWRD=
---------------------------------------------------------------------,
I SESSLIK=
I
----------------------------------------------------------------------1
I
ICMPACT=
1
I
----------------------------------------------------------------------1
I
ILU=
I
I
----------------------------------------------------------------------1
,
,LIST=
I
I
----------------------------------------------------------------------1
I
ITRNSP=
I
I
----------------------------------------------------------------------1
1
IBE=
I
I
----------------------------------------------------------------------1
I
,fiFe=:
1
I
----------------------------------------------------------------------1
,
IseE=
I
I
----------------------------------------------------~-----------------1
1
IABE=
I
I
----------------------------------------------------------------------1
I
fMRF=
I
1
----------------------------------------------------------------------1
I
ICS=
1
I
----------------------------------------------------------------------1
1
ITRACE=
I
I
----------------------------------------------------------------------1
lEND
I
1
I
Figure 2-7 (Part 2 of 2).
Work Sheet for Coding
Macros
Chapter 2.
POWER/iS
Generation
Installing POWER/VS
43
Terminals Supported by POWERIVS
For RJE,BSC operation, the POWER/VS RJE program can support up to 25
remote terminals of the types IBM 2770, 2780, 3741, 3780 or 3771, 3773,
3774, and 3775 (as a 2770) or 3776 (as a 3180); however, only four
terminals can be attached to a System/370 Model 115 and six terminals to
a Model 125.
For RJE,SNA operation, POWER/VS supports up to 200 work stations (single
,or multiple logical units) of the types IBM 3770 and 3790.
IBM 2770 DATA COMMUNICATION SYSTEM
This system may be used as an RJE terminal. It can be connected to the
central system by means of common carrier leased or switched facilities.
The devic9s that are attachable to the IBM 2770 are described in System
~Q~EQn~~1§1-IB~_111Q_~~!g_~Qm~Yni£ation_~y§!gm, GA21-3013.
•
545 Output Punch, Model 3 or 4 (output switch 2)
•
2203, Model A1 or A2, or 2213 Printer, Model 1 or 2 (output switch 1)
•
2502 Card Reader, Model A1 or A2 (input switch 2).
1.
A card reader and a printer are required, a card punch is optional.
2.
The standard keyboard provided with the 2770 may be used as a 2502
reader for text that is compatible with card input. Such input is
limited to entry of commands and short job streams (the complete
stream must fit entirely into the 2770 buffer). Lowercase
characters are not translated to uppercase; therefore, uppercase
characters must be entered specifically if so required.
•
EBCDIC or ASCII transmission code
•
Extended retry transmission
•
WACK response (wait before transmit positive acknowledgment)
•
Line termination.
44
POWER/VS Installation Guide and Reference
•
Buffer expansion (256 characters)
•
Additional buffer expansion (512 bytes)
•
Space compression/expansion
•
Horizontal format control
•
Automatic answering
•
144-character print line
•
EBCDIC transparency (required for object decks only).
Only punched output to a remote terminal may be in transparent mode. If
punched output is not a requirement, or if the user transmits in nontransparent mode only, the EBCDIC transparency feature on the 2770 and
transparency on the 2701 Data Adapter Unit or Integrated Communications
Adapter may be omitted.
IBM 2780 DATA TRANSMISSION TERMINAL (HODEL 1 OR 2)
--
This terminal can be connected to the central system by common carrier
leased or switched facilities or privately owned communication
facilities. The devices that are attachable to the IBM 2780 are
described in £Q~2Qn~n!_Q~2£~iE1ionl_I~~_~1§Q_Q~1g_!~~n2mi2§iQn_!~£min21,
GA27-3005.
•
EBCDIC or ASCII transmission code
•
Extended retry transmission
•
Line termination
•
WACK response (wait before transmit positive acknowledgment) •
Supported
Featur~2
•
Multiple record transmission (up to 7 records)
•
Horizontal format control
•
•
•
•
•
Automatic answering
Selective character set
•
EBCDIC transparency (required for object decks only) •
Automatic turnaround (Kodel 2)
120-character print line
144-character print line
Chapter 2.
Installing POWER/VS
45
Note: Only punched output to a remote terminal may be in transparent
mode.
If punched output is not a requi~ement, or if the user transmits
his punched output in non-transparent mode only, the EBCDIC transparency
feature on the 2780 and trans9arency on the 2701 Data Adapter Unit, 2703
Transmission Control Unit, or Integrated Communications Adapter may be
omitted.
IBM 3741 DATA STATION (MODEL 2 OR 4)
This data station is supported as an RJE terminal compatible with the
IBK 2780 without the multiple record transmission feature.
It can be
connected to the central system by means of common carrier leased or
switched facilities. Devices attachable to the 3741 are described in
IBH 3741 Data station Reference Manual, GA21-9183.
There are no required features on the 3741.
IBM 3771 COMMUNICATION TERMINAL
The IBM 3771 Communication Terminal is a mUltipurpose keyboard/printer
terminal to which the following I/O devices may be attached:
•
3501 Card Reader.
•
3521 Card punch, with or without Read Feature, attached via an IBM
3782 Card Attachment Unit Model 1.
For details concerning the components of the 3771, refer to the
publication IBM l770 Data Comaunication S~m, system Components,
GA27-3097.
POWER/VS supports the 3771 in RJE,BSC mode (as a 2770) and in RJE,SNA
mode.
IBK 3173 COMMUNICATION TERMINAL
The IBM 3773 Communication Terminal is a multipurpose keyborad/printer
terminal with a Magnetic Diskette Storage device with a capacity of
242 688 bytes of storage. For details concerning the components of the
3773, refer to the publication IBM 3770 Data Communication Sy~
~Y§te~~omponents, GA27-3097.
POWE~/VS
supports the 3773 in RJE,BSC mode (as a 2710) and in RJE,SNA
mode.
46
POWER/VS Installation Guide and Reference
IBM 3774 COMMUNICATION TERMINAL
The IBM 3774 Communication Terminal is a multipurpose keyboard/printer
terminal to which the following I/O devices may be attached:
•
One or two IBK Magnetic Diskette Storage devices (248 688 bytes of
storage per device) •
•
One card reader: either a 2502 Card Reader, attached via a 3782 Card
Attachment unit, or a 3501 Card Reader.
•
One 3521 Card Punch with or without Read Feature, attached via a 3782
Card Attachment Unit.
•
One 3784 Line Printer.
For details concerning the components of the 3774, refer to the
publication IB~ 3770 Data Communication System, ~stem Components,
GA27-3097.
POWER/VS supports the 3774 in RJE,BSC mode (as a 2770) and in RJE,SNA
mode.
IBK 3775 COMMUNICATION TERMINAL
The IBM 3775 Communication Terminal is a mUltipurpose keyboard/printer
terminal to which the following I/O devices may be attached:
•
One or two IBM Magnetic Diskette Storage devices (242 688 bytes of
storage per device) •
•
One card reader: either a 2502 Card Reader, attached via a 3782 Card
Attachment Unit, or a 3501 Card Reader.
•
One 3521 Card Punch with or without Read Feature, attached via a 3782
card Attachment Unit.
For details concerning the components of the 3775, refer to the
publication IBM 3770 Data comaunication Syste~L-~stem Com2Qngnts,
GA27-3097.
POWER/VS supports the 3775 in RJE,BSC mode (as a 2770) and in RJE,SNA
mode.
IBM 3776 COMMUNICATION TERMINAL
The IBM 3776 Communications Terminal is a multipurpose, medium-speed
remote job entry terminal. To the basic unit, which is a
keyboard/printer console, the following I/O devices may be attached:
•
One or two IBM Kagnetic Diskette storage devices (242 688 bytes of
storage per device) •
Chapter 2.
Installing POWER/VS
47
•
One card reader: either a 2502 Card Reader, attached via a 3782 Card
Attachment Unit, or a 3501.Card Reader.
•
One 3521 Card Punch, with or without Read Feature, attached via a
3782 Card Attachment Unit.
For details concerning the components of the 3776, refer to the
publication I~~_J77Q_Q~1g_fQ~.Yni£~!!2n_§Y§!~m~_§y§te~_£2mE2~n12,
GA27-3097.
POWER/VS supports the 3776 in RJE,BSC mode (as a 3780) and in RJE,SNA
mode.
IBK 3780 DATA COMMUNICATION
TERMINA~
This terminal may also be used as an RJE terminal. It can be connected
to the central system by means of common carrier leased or switched
facilities.
The devices that are attachable to the IBM 3780 are
described in ~22n~1-Informgtion fQ£-i~IBM 3730 Data Communicati2ll§
I~LID!n~l, GA27-3063.
The 3780 terminal consists of:
•
A card reader
•
A printer
•
A terminal console
I•
A 3781 card punch
(optional; must be hardware-attached as device
2 or 3) •
•
EBCDIC or ASCII transmission cod.
•
Extended retry transmission
•
WACK response (wait before transmit positive acknowledgment) •
•
Additional print positions
•
Component selection for printer/punch device
•
EBCDIC transparency (required for object decks only).
1.
Only punched output to a remote terminal may be in transparent mode.
If punched output is not a requirement, or if the user transmits in
nontransparent mode only, the EBCDIC transparency feature on the
3780 and transparency on the 2701 or 2103 or on the Integrated
Communications Adapter may be omitted.
48
POWER/VS Installation Guide and Reference
2.
Online .ode settings for RJE terainals attached to a CPU Model '15
or 125: The bit settings of the ICA line mode specification for an
RJE ter.inal that is attached to a Model 115 or 125 CPU are
described in !~~~I2temL372-~2g~1_11~ Fun2!iQD~!_£h~£!~i21ic~,
GA33-1510, and in IBM SY§1em/370 Model 125 Functional
~ha~cte~i£§, GA33-1506, respectively.
IBM 3790 COMMUNICATION SYSTEM
The IBM 3790 Communication System is a programmable, operator-oriented
terminal system. POWER/VS supports the 3790 Communication System
Version 6 as an SNA work station with the 3790 RJE Work Station Package
(WSP) operating on the 3791 Controller. The 3790 may be attached to the
host system either by the local channel attachment or by an SOLC
telecommunications line controlled by a 3704 or 3105 Communications
Controller. Up to three logical printers, one logical reader and one
logical console are supported. For details, refer to the DOS/VS
POWER/VS~ station Deer's Guide, GC33-6049.
POWERIVS Support for Other Devices
IBM 2560 AND 5425
POWER/VS supports the IBK 2560 and the IBM 5425 as input or output
devices. POWER/VS will handle 96-column cards on input and output for
the 5425. If SYSPCH is assigned to the 2560 or the 5425, POWER/VS
supports:
I.
program-controlled stacker selection
•
Punch and interpret
•
Card print
•
Punch/print.
The 2560 and 5425 are subject to the following restrictions:
•
POWER/VS cannot update or interpret a card input file.
•
POWER/VS ignores stacker selection for input cards.
•
Read column binary is not supported.
•
In a given partition, POWER/VS will only spool both punch and read
functions if a unique physical device address is specified for each
function (user dummy for at least one function), for instance, X'OOC'
for the read function and X'OlC' for the punch function.
•
POWER/VS uses hopper 1 for input.
•
POWER/VS uses the hopper specified by the user for output, provided
separator cards are not specified. If separator cards are specified,
hopper 2 is used for output.
Chapter 2.
Installing POWERjVS
49
IBM 3525
POWER/VS supports the basic read and punch functions of the IBK 3525
card reader. Punch/interpret and punch/print are also supported, as
well as the card print feature.
If SYSPCH is assigned to the 3525,
POWER/VS supports the following functions:
•
Program-controlled stacker selection
•
Print
•
Punch/print (multiline)
•
~utomatic
•
User-controlled line positioning
•
Print overflow.
line positioning
The assignment of a logical unit to a 3525 card reader or card punch is
subject to the same rules that apply to the assignment of a logical unit
to a 2560 or a 5425.
IBM 3800
POWER/VS supports the IBM 3800 Printer as an output device. Before
installing a 3800, you should be familiar with the contents of the
DOS/V2-IBM~O Printing subsyste~~gram.er·§_GuiS§, GC26-3900.
You
can find information in the section npOWER/VS considerations" in the
chapter "Planning for the 3800".
50
POWER/VS Installation Guide and Reference
Chapter 3. Using POWERIVS
POWER/VS is a reader/writer spooling processor that provides automatic
staging of unit-record input and output, class scheduling, and priority
scheduling for all DOS/iS programs executed under its control. The
Remote Job Entry (RJE) facility of POWER/VS permits jobs to be submitted
from remote terminals to the central system and job output to be routed
from the central system to the remote terminal.
This chapter describes how to use POWER/VS. At the central system, you
have two sets of commands, or statements, to control the operation of
POWER/VS and to submit jobs to the system. These are:
•
The POWER/VS central operator (POCL) commands
•
The POWER/VS job entry control language (JECL) statements.
The formats and functions of these two sets of commands are explained in
detail in this chapter.
In addition, this chapter also covers four other topics.
These are:
•
The cross-partition communication macros. ~hese macros enable you to
request certain POWER/VS functions from within an application program
not running under POWER/VS control.
•
Specific macros to provide job accounting under POWER/VS and to
perform output segmentation, for example, for long-running jobs~
•
The control statements available to start POWER/VS using the
AUTOSTART feature.
I.
General rules for the POWER/VS user.
At a remote terminal or work station, you use another set of commands.
These are called the POWER/VS Remote Job Entry (RJE) terminal commands.
A detailed description of their formats and functions is contained in
the ~OWER/VS W~t~tation Us~~Gui~, GC33-6049. A summary of the
POWER/VS statements and comaands is provided with the POWER/VS reference
card, ~OS/VS POWIRLIS Reference Summ~y, GX33-9004.
POWERIVS Central Operator Commands
The POWER/VS central operator co •• ands allow you to control POWER/VS and
POWER/VS RJE operation from the central operator's console. They are
entered in the same way as attention routine commands. At the display
operator console of a System/370 Kodel 115 or 125, these commands can be
entered directly without pressing the request key.
For almost all POWER/VS command codes, a 1-character short form is
available. All the options of a command are valid for both the short
form and the extended command code.
The POWER/VS central operator commands may be divided into the following
three groups:
Chapter 3.
Using POWER/VS
51
•
Queue Management Com.ands. These commands control the various
POWER/VS inout and output queues.
•
Task Management Commands. These commands are used to control the
reader/writer tasks and the execution processors.
•
Control Commands. These commands allow special actions concerning
lines, print forms, accounting, and broadcasting activities.
Figure 3-1 gives an overview of the three groups of POWER/VS central
operator commands.
,
t I~-2f.
I ~omman~
t
I ~Qde
IjQE~at!Qnll
r
I
I
I
I
I job (s) •
I
J £2..!!.nnd
I SnQrt
I Fo!:!.
I Function
I
1---------------------------------------------------------------------I
IPDISPLAY
I D
IDisp1ay the status of POWER/VS
IQueue
IPALTER
I Management
I
,Commands,
I
JPDELETE
I
I
I
A
I
I
I
I
IAlter the processing attributes of
la POWER/VS job.
I
L
I
I
I
IPRELEASE
,R
1
I
I
IDelete queue entries or messages.
I
IRelease POWER/VS jobs for further
I processing •
1---------------------------------------------------------------------I
IPSTART
S
start a task or place a partition
I
I
I
I
I
I
I
I
I
r
IPSTOP
!Task
I Management
ICommands
I
I
I
IPGO
I
IPEND
I
I PCANCEL
I
J
under the control of POWER/VS.
P
stop a task or release a partition
from POWER/VS control.
G
Reactivate a task or a partition.
Terminate POWER/VS.
C
cancel a POWER/VS status report.
F
Terminate processing of the current
POWER/VS job.
IPRESTART
T
Restart a writer task.
IPBRDCST
r
IPACCOONT
J
B
rPFLUSH
I
I
Control
Commands
I
Figure 3-1.
J
IPINQUIRF.
,
I
IPSETUP
U
,
ITransmit a message.
ISave accumulated account file
I records.
I
IDisplay the status of RJE lines.
I
IPrint page layout.
POWER/VS Central operator Commands
The general format of the POWER/VS central operator commands is as
follows:
Each central operator co.mand has two fields, the operation field and
the operand field. The operation field can be specified in either the
extended or the abbreviated format. The operand field contains one or
more parameters separated by commas, or contains no parameters at all.
52
POWER/VS Installation Guide and Reference
If operands are specified, they aust be separated fro. the operation
field by at least one blank. An optional parameter of a command is
enclosed in brackets. stacked options represent alternatives, one and
only one of which may be chosen. Braces enclose alternatives, one of
which must be chosen. The operator com_ands can be entered in either
uppercase or lowercase characters.
Commas have to be set as indicated, trailing commas must not be coded.
COKKAND DESCRIPTIONS
The PACCOUNT (or J) co.mand empties the POWER/VS account file and saves
the processed account file records. POWER/VS informs you with message
1Q31I when the file is nearly full. Message 1Q79I will indicate to you
when the account file has been saved. If any POWER/VS task requires an
account record and no space is available, you will receive message
1Q321.
This command can be used at any time.
i
-
•
I Operation
IOperands
I
:{~ACCOUNT}
:[tapeaddr,(denSit ][ ,tfilenameJ]
:
I
I
I
I DISK,dfilename
I
I DEL
I
I
I
1----------------------------------------------------------------------1
y
L
tapeaddr
specifies the address of the tape drive on which the file
is to be written. The format is the following:
cuu
X'cuu'
where cuu is the channel and unit number.
density
specifies the density of the tape on which the file has
to be written. The format is the following:
ss
X'ss'
tfilename
specifies the file name of the labeled tape file to be
created. If no file name is specified, the system treats
the file as a standard unlabeled DOS/VS tape file.
Your programaer aust ensure that / / ASSGN and / / TLBL
information (for the labeled tape) is provided in the
POWER/VS partition before initialization of POWER/VS.
The / / TLBL card must have the filename tltfilena.e u •
Chapter 3.
Using POWER/VS
53
I DISK,dfilename specifies
to disk.
that the POWER/VS account file is to be written
Your prograamer must ensure that / / ASSGN,
/ / DLBL, and / / EXTENT information (for a disk sequential
output file) is provided in the POWER/VS partition before
initialization of POWER/VS.
The device type on which the saved account file is to
reside must be the same as that for the IJAFILE.
The / / DLBL card must have the filename ttdfilenallle".
DEL
specifies that the account file records are to be
deleted.
PACCOUNT
180
irite the account file to an unlabeled tape
mounted on drive 180.
PACCOUNT
180,ACC~FLE
write the account file onto tape as a standard
label file.
PACCOUNT
DEL
Delete all account file records.
PACCOUNT
Spool account file records to punch queue.
If the command is issued without an operand, the account file is spooled
to disk and stored in the punch queue with jobname=PACCOUNT,priority=l,
class=P, and disposition=HOLD assigned. ~o retrieve the account file
records, start a punch writer task for output class P.
Each card contains the following information:
1
2-72
Account record identifier (byte 43 of the account record) •
Data (bytes 0-70 of the account record) punched in the same
positions as it appears in the account record, including the
record identifier.
73-78
Record number of the account file.
79-80
Sequence number of continuation cards. One account record
may require two or three punched cards.
The PALTER (or A) command alters the attributes of a POWER/VS job after
it has been logged by POWER/VS. Any number of attributes may be
modified with one command.
Changes of the class or priority parameters place the job at the end of
the specified class or priority group.
If the command specifies a job that is being executed, POWER/VS issues
message 1R88I, indicating that the job attributes cannot be altered. If
the command requests a change of job attributes for a job whose output
is being processed (the job is already in the list or punch queue), only
the number-of-copies attribute can be changed, except if the job is
being transmitted to a 3790 workstation (with PDI~=FMH2). All other
54
POWER/VS Installation Guide and Reference
para.eters are ignored and message 1R881 is issued to indicate that the
job attributes cannot be altered.
If the output is segmented, however,
and the first segment has already been deleted, not even the number-ofcopies parameter can be changed.
Note that the job's class, disposition, and priority attributes may be
different in the input and output queues, because input class,
disposition, and priority are defined in the * $$ JOB statement, whereas
output class, disposition, and priority are defined in the * $$ LST
(* $$ PRT) and * $$ PUN statements.
If the output job is destined for a 3800 printer, you are able to change
only the transmission count.
The transmission count is displayed in the
first line of the status report. The total number of copies still to be
produced (including the transmission in progress) is displayed in the
second display line of the status report.
If there is copy grouping (for more information refer to the COPYG
parameter in the * $$ LST statement) and the output is assigned to a
3800, and you reduce the number of transmissions and increase it with a
later PALTER command, the previously truncated group values are
restored. If the new number of transmissions is greater than the
original copy grouping, then values of 1 are added.
t
IOperation
,
IOperands
1---------------------------------------------------------------------I {PALTER}
queue,{jObname[,jObnUBber 1}
1 A
ALL
*abc
class1
[ ,PRI=priority]
( ,DISP=disposition]
[ ,CLASs=class2]
[ ,COPY=number-of-copies]
[,REMOTE=remid)
['CKPAc~={;~.e}]
queue
specifies the queue for which the command is to be
executed in the form:
LST
PUN
RDR
for the list gueue
for the punch queue
for the reader queue.
jobname
specifies the job name by which the POWER/VS job is known
to POWER/VS. The job name can be 2 ~o 8 alphameric
characters (including "I", ".", and "_H) long_
jobnumber
specifies the 1- to 5-digit job number assigned to the
POWER/iS job by POWER/iS. The PDISPLAY command may be
used to determine" the correct job number.
ALL
requests that specific attributes for all POWER/VS jobs
in the specified queue are to be altered.
Chapter 3.
Using POWER/VS
55
*abc
requests that attributes are.to be altered for POWER/VS
jobs whose names begin with the specified characters.
For abc, any combination of up to seven alphameric characters (including "/", ".", and "-H) may be specified.
classl
requests that attributes for POWER/VS jobs with the
specified class are to be altered. Valid specifications
are A - Z and 0 - 6.
PRl=
specifies the new priority of the indicated POWER/VS
job(s). Priority is specified as a single digit from 0
to 9. Nine is the highest priority.
DlSP=
specifies the new disposition of the indicated POWER/VS
job(s). You can specify:
H
K
L
I
o
for
for
for
for
hold
keep
leave
dispatchable.
CLASS=
specifies the new class (class 2) of the indicated
POWER/VS job(s). You can specify any alphabetic
character from A to Z. Specification of digits 0 to 6 is
permitted for partition input classes.
COpy=
specifies the number of copies to be produced after the
command is issued, including the one in progress. The
number-of-copies specification, which may range from 0 to
99, applies only to output, and is ignored if specified
for an input entry.
REMOTE=
may be specified as any number from 0 to 200.
'0'
indicates the central location. The REMOTE=
specification applies only to output, and is ignored if
specified for an input entry.
CMPACT=
specifies whether data compaction is to be performed for
the transmission of job output to an SNA work station.
*
indicates that the default compaction table
(defined in the PRMT macro) is to be used.
name
identifies the 4-character name of the compaction
table to be used.
NO
indicates that no compaction is to be performed.
~~~!E!~2:
PALTER , LST,PAYROLL,DISP=H,CLASS=B
Change the disposition of the output
of job PAYROLL to H and change the
class to B.
A PON,*PAYRL,DISP=D
Alter the disposition to 0 of all
POWER/VS jobs in the punch queue
whose names begin with PAYRL.
PALTER LST,P,CLASS=Q
Change all class P jobs to class Q.
56
POWER/VS Installation Guide and Reference
PBRDCST Command
The PBRDCST (or B) command enables you to send (broadcast) messages to
remote users. Up to 16 messages are queued and made available to one or
all remote users on request.
ftessages to all remote users (ALLUSERS) are queued and given a sequence
number. This number can be determined using the PDISPLAY command.
Broadcast messages routed to one specific operator are displayed as soon
as the terminal is ready to receive the message.
j
,
I Operation
I Operands
I
I----------------------------------------------~-----------------------1
I{:BRDCST}
I{remid}' 'text'
I
I ALLUSERS
:
I
-J
I
remid
specifies the remote-id of the user for whom the broadcast
message is intended. Remote users are identified by numbers
from 1 to 200. Zero is reserved for the central location.
ALLUSERS
specifies that the broadcast message is intended for all
remote users.
'text'
specifies the text of the broadcast message, entered between
single quotation marks. Single quotation marks within the
message must be entered as two quotation marks. The maximum
length of the message text is as follows:
•
For ALLUSERS-type messages: 46 characters.
•
For messages from the terminal to the host system: 60
characters.
•
For messages from the host system to the terminal:
characters.
49
If the length of a message text exceeds these maximum values,
issue two or more PBRDCST commands, because all characters
beyond the maximum text length will be truncated.
PBRDCST 150,'RJE WILL SHUT DOWN IN 30 !INUTES'
Broadcast this message to the user with the
remote-ID 150.
PBRDCST ALLUSERS,'RJE STARTS AT 800 HRS A.M.'
Broadcast this message to all users in the system.
Chapter 3.
Using POWER/VS
51
The PCANCEL (or C) command terminates printing of output initiated by
the PDISPLAY command.
j
--.
,operation
IOperands
I
I
I
I
1----------------------------------------------------------------------1
,{PCANCEL}
I[ STATUS]
I
C
I
I
STATUS
specifies that the printing initiated by a PDISPLAY command
is to be terminated.
PCANCEL
Terminate printing initiated by. a PDISPLAY command.
The PDELETE (or L) command removes one or more POWER/VS jobs from the
specified queue. Jobs being executed in a partition or being processed
by a writer task are not affected by this command.
I
I
I Operation
IOperands
I
I L
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
,
1--------------------------------------------------------------------1I
I{PDELETE}
I queue, jobname( ,jobnullber)
r
I
I
I
I
I
queue, ALL
gueue,class
queue, *abc
PlSG(, n ]
L
-J
queu~
specifies the queue for which the command is to be
executed in the form:
LST
PUN
RDR
for list queue
for punch queue
for reader queue.
jobname
specifies the 2- to a-character job name by which the
entry is known to POWER/VS.
jobnumber
specifies the 1- to 5-digit job number assigned to the
queue entry by POWER/VS. The PDISPLAY command can be
used to determine the correct job number.
ALL
specifies that all POWER/VS jobs in the specified queue
are to be deleted.
cla.r;s
specifies that all POWER/VS jobs of a certain class are
to be deleted from the specified queue. Valid
specifications are A - Z and 0 - 6.
58
POWER/VS Installation Guide and Reference
*abc
specifies that all POWER/VS jobs whose names begin with
the specified characters are to be deleted from the
specified queue. You can specify up to 1 alphameric
characters (including "/It, I t . I t , and It-It) following the
asterisk.
ftSG,n
specifies that the ALLUSERS-type message with number n is
to be deleted. The message number can be determined
using the PDISPLAY MSG com.and. If n is omitted, all
ALLOSERS-type messages originated by the central operator
are deleted.
PDELETE RDR,ALL
Delete the entire reader queue.
PDELRTE LST,B
Delete all class B entries in the list queue.
PDELETE KSG
Delete all ALLUSERS-type messages.
PDELETE LST,*ASSM
Delete all entries in the list queue starting with
the letters ASSft.
The PDISPLAY (or D) co •• and can be used to display POWER/VS jobs,
ALLUSERS-type messages in the POiER/VS queues, or the status of POWER/VS
resources.
An example of a POWER/VS status report is given in
"Initiating POiER/VS without AUTOSTART" in Chapter 4.
The status reports are produced at the logical device SYSLOG or at a
printer (see the operand "listaddr"). Each queue entry is represented
by one line containing the following items:
ItelDs
jobname'
jobnumber
priority
disposition
class
FROII remote -ID
TO remote-ID
Number-of-records/pages
Number-of-copies
Forms-number
I Characters
8
5
1
1
1
3
3
6
2
4
The last four items are displayed for output only. For punch output,
the number of records is displayed, whereas for list output the number
of pages is displayed.
Each line of the status report starts with the message number lR46I. If
the status report is made up of entries fro. different queues, the name
of the queue is printed before the first entry is displayed.
The disposition of a queue entry may appear as H for hold, K for keep
after processing, L for leave, D for delete after processing or * if an
execution processor or a writer task is currently processing the entry.
Chapter 3.
Using POWERjVS
59
The class can appear as an alphameric character from A to Z, or from
o to 6.
Remote-ID is displayed as a number from 0 to 200.
central location is O.
The remote-ID of the
The number-of-copies column for an impact printer (such as the IBM 1403)
displays the number of copies still left (including the copy for the job
being printed), or the total number of copies to be produced when the
output file has not yet started to print. For an IBM 3800 Printer
assigned at job execution time, the column displays the transmission
count. In order to distinguish between the transmission count value and
the number of copies, the transmission count is preceded by an asterisk
(*) •
If the output file is destined for an IBM 3800 Printer, a second display
line is issued in the status report indicating:
•
The forms overlay to be flashed
•
The "BURST" request
•
The total or still-to-do number of copies.
The forms overlay and burst indications are displayed only when they are
requested for the output job. For more information on the BURST and
FLASH parameters refer to the * $$ LST statement later in this chapter.
If ~KPACT=name or CMPACT=NO is found in a queue entry, an additional
line is issued in the status report indicating:
•
The job name (8 characters)
•
The job number
•
The compaction option (NO or 'name', up to 4 characters).
(5 characters)
If a writer task is processing a queue entry when the PDISPLAY command
is entered, the number-of-records/pages is the number of records or
pages left to be produced for the current copy. The operator can use
this information to determine whether to stop a writer task or let it
continue until the current queue entry is completed.
When a job is not active because it was flushed (by means of the PFLOSH
command) or stopped (using the PS~OP ••• RESTART command) before the
PDIS?LAY command is issued, the number of copies displayed is the
original copy count as specified in the * $$ LST(* $$ PRT) OR * $$ PUN
statement. If the IeR is installed the number of copies displayed is
the current number of copies left to be produced, including the one that
was in progress when the job was flushed or stopped. However, the
number of pages/cards displayed is the original total number.
When processing of a flushed (or stopped) job is resumed again and a
PDISPLAY is issued subsequently, the number-of-copies value displayed is
again the number of copies left to be produced, including the one in
progress.
60
POWER/VS Installation Guide and Reference
I
IOperation
I
I
IOperands
1----------------------------------------------------------------------1
I{PDISPLAY}
queue,jobname[ ,jobnumber)
I
I D
I
I
gueue[ ,ALL]
gueue,HOLD
queue,FREE
gueue,RJE[,remid]
queue, LOCAL
queue,*abc
queue, class
ALL[ ,listaddr]
HOLD
FREE
RJE[ ,remid)
LOCAL
*abc
MSG
A
M
Q
__________________________________________________________________________
---J
T
queue
specifies the gueue for which the PDISPLAY command is to
be executed in the form:
LST
PUN
RDR
for list queue
for punch queue
for reader queue.
jobname
specifies the 2- to a-character job name by which the
POWER/VS job is known to POWER/VS.
jobnumber
specifies the 1- to 5-digit job number assigned to the
POWER/VS job by POWER/VS.
ALL
specifies a request for the status of all POWER/VS jobs
in the specified queue. If the queue operand is not
specified, status information for all jobs in all queues
is displayed.
HOLD
specifies a request for the status of all POWER/VS jobs
in the specified queue that are not available for
processing (that is, in hold or leave state). If the
queue operand is not specified, status information is
displayed for all such jobs in all queues.
Chapter 3.
Using POWER/VS
61
FREE
specifies a request for the status of all POWER/VS jobs
in the specified queue that are available for processing
(that is, in the keep or dispatchable state). If the
queue operand is not specified, status information is
displayed for all such jobs in all queues.
RJE
specifies a request for the status of all RJE-type
POWER/VS jobs in the specified queue. If the queue
operand is not specified, status information is displayed
for all such jobs in all queues.
remid
Specified with the RJE operand, remid indicates a request
for the status of all POWER/VS jobs in the specified
queue that were SUbmitted by, or routed to a specific
remote user. Valid specifications are 0 for the central
operator and 1 to 200 for remote operators.
LOCAL
specifies a request for the status of all POWER/VS jobs
in the specified queue that were submitted from, or
routed to the central location. If the queue operand is
not specified, status information is displayed for all
such jobs in all queues.
*abc
specifies a request for the status of all POWER/VS jobs
whose names begin with the specified characters. For
abc, you can specify any combination of up to seven
alphameric characters, including "/", ".", and "-H. If
the queue operand is not specified, status information
for all such jobs in all queues is displayed.
class
specifies a request for the status of all POWER/VS jobs
with the specified class in the specified queue. Class
can be specified as a character from A to Z, or from
o to 6 (input class onl y) •
listaddr
specifies the physical printer on which the status report
is to be listed. Enter the channel and unit address in
the format
cu u
0
r XI
CU u'
•
MSG
specifies a request to display all ALLUSERS-type
messages, and to identify the users who submitted them.
The number displayed with each message can be used to
delete them.
A
specifies a request for a list of all active reader and
writer tasks, together with the jobs they are currently
processing.
specifies a request to redisplay a list of all system
messages for which an operator response is still
required.
Q
specifies a request for the number of free queue records,
and POWER/VS account records (if applicable) •
T
specifies a request for the current time and date. The
current number of virtual storage pages reserved by PFIX
macros and the current number of POWER/VS tasks is also
displayed.
62
POWER/VS Installation Guide and Reference
Example~:
PDISPLAY RDR,*ASS!
Display the status of all POWER/VS jobs in the
reader queue whose names begin with ASSM.
PDISPLAY RDR,ASSEM
Display the status of POWER/VS job ASSEM in the
reader queue.
PDISPLAY ALL
Display the status of all POWER/VS jobs in all
queues.
PEND Command
The PEND command terminates POWERjVS operation, releases all POWER/VSsupported partitions and restores the POWER/VS partition to normal
DOS/iS operation. All unit-record devices in the POWER/VS partition and
in the partitions controlled by POWER/VS are unassigned. Unless KILL is
specified, all· active POWER/VS tasks are allowed to continue until they
have finished processing the current POWER/VS job (that is, for the job
Which is being executed, or whose output is being printed or punched).
If KILL is specified, POWER/VS is terminated immediately.
,
,
IOperation
IOperands
I PEND
I
I
I [uraddr
I
I
1----------------------------------------------------------------------1
J
I
I
I
I KILL(, uraddr ]
J
I
no operand
terminates the POWER/VS system normally without a dump or
status report.
KILL
specifies immediate termination of the POWER/VS system
and caUSes a dump to be printed if a printer is assigned.
POWER/VS-supported partitions are canceled, but reader
and writer tasks are terminated as for the PSTOP command.
uraddr
specifies the unit-record device address of the printer
on Which the status report (dump, if KILL is specified)
is to be printed. The format can be either cun or
X·cuu'. If uraddr is not specified, no status report
(dump) will be provided. The printer remains assigned
after POWER/VS has been terminated.
Note:
SYSLST must be assigned to uraddr in the POWER/VS
partition.
PEND KILL,OOE
Immediate ter.ination with system dump on printer OOE.
PEND
Hormal termination without status report or dump.
PEND OOE
Normal termination with status report.
will be provided.
Chapter 3.
No system dump
Using POWER/VS
63
PFLUSH Command
The PFLUSH (or F) command terminates processing of a POWER/VS job by a
POWER/VS task. When a reader task is flushed, fUrther input processing
for the job is terminated and a reader queue entry for the job is not
built.
When a writer task is flushed, further output processing for the job is
terminated and the job's output queue entry is deleted unless HOLD was
specified or the number-of-copies value in the * $$ LST (* $$ PRT) or
* $$ PUN statement is great~r than 1. The specified reader/writer task
continues processing for th~ next available POWER/VS job.
When a writer task for a job with
its queue entry is also placed in
started again (from the beginning
interrupt~d)
by means of a PALTER
two or more output copies is flushed,
the HOLD state. This output can be
of the copy whose output was
or a PRELEASE command.
i
- ,
I Operation
I
IOperands
1----------------------------------------------------------------------1
:{:FLUSH}
:{Uraddr[ ,HOLD]
}
:
1
I partition[,HOLD]
I
I
,
uraddr
specifies the unit record device associated with the
reader/writer task.
HOLD
specifies that the corresponding queue entry is
deleted. Once the entry has been placed in the
state, it cannot be deleted when a partition or
task is flushed.
This operand is ignored if it
specified for a reader task.
not to be
HOLD
writer
is
You may require the HOLD option, for example, to delay
processing of a job that needs more resources than are
available at the time. Jobs requiring the same resources
may thus be grouped to optimize the use of system
resources.
partition
specifies that the POWER/VS job is to be terminated and
the corresponding reader queue entry is to be deleted
unless HOLD or KEEP has been specified. In the case of
DISP=K, the disposition is changed to L. If the reader
queue entry of a POWER/VS job is deleted, POWER/VS builds
a list queue entry containing a message to the
programmer. This message informs him that the job has
been flushed by the PFLUSH command. Valid partition
specifications are BG or Fn, where n is the partition
number. Note, however, that only partitions under
POWER/VS control can be flushed by means of this command.
Note: If the command PSTOP cUU,EOJ was previously issued
for a writer task, the command PFLUSH causes this task to
be stopped immediately, but for safety reasons, the job's
output queue entry is not deleted.
The current DOS/VS job will be canceled without DUMP,
regardless of any dump options specified.
64
POWER/VS Installation Guide and Reference
PFLUSH OOE
Delete list queue entry currently being printed and
continue with next entry.
PPLUSH BG
Delete reader queue entry currently being processed and
continue with next entry.
PFLUSH BG,HOLD Terminate processing of reader queue entry currently
being processed. Place the entry in the hold state and
continue with the next entry.
The PGO (or G) command reactivates a POWER/VS routine that is waiting
for an operator response. You would normally use this command after you
have responded to an action-type message. You cannot use PGO to restart
a partition or task that was stopped by a PSTOP command.
!Q1~:
Reader tasks operating on
int~rrupt when the READY key has
card readers that give a "device end"
been pressed are automatically
reactivated when the device end occurs. You do not need the PGO command
for such tasks.
i
I Operation
IOperands
I {PGO}
I G
I
I
I
1----------------------------------------------------------------------1
I{Uraddr
}
I
,
r
I
I partition,cuu
L
uraddr
•
specifies the unit record device associated with the
writer task (Note: Reader tasks are reactivated
automatically. They do not need a PGO command). It has
the format:
cuu or X'cuu'
partition,cuu
specifies the partition and device whose output is being
spooled to tape. Valid partition specifications are BG
or Fn, where n is the partition number. Note, however,
that only partitions under POWER/VS control can be
reactivated by means of this command.
Examples:
PGO OOE
Reactivate a list writer task, for example after the
required form has been set up.
PGO BG
Reactivate BG execution, for example after a new tape has
been mounted.
PGO B(;,OOE
Reactivate BG execution after mounting a tape for the
output of printer OOE.
Chapter 3.
Osing POWER/VS
65
PINQUIRE Command
The PINQUIRE (or I) command provides you with status information for a
specific Bse line or logical unit or for all BSC lines and active
logical units.
!Q!~:
When POWER/VS executes on a virtual machine under VM/310 and, for
whatever reason, this machine entered CP mode, you must not specify the
short form (I) of the PINQUIRE command, because this would result in the
attempt of the Control Program (CP) to perform an IPL.
I
,
I Operation
IOperands
I
r,{PINQUIRE}
I
'{luname}
I
I
I
I
I
1----------------------------------------------------------------------1
I
I
I
I
I lineaddr
I
I ALL
I
I
luname
specifies the name of the logical unit for which the
status information is desired.
lin~addr
specifies the address of the Bse line for which status
information is requested, specified in the format cuu or
X·cuu'.
ALL
specifies that status information for all supported lines
is to be displayed.
The status of a line or a logical unit may be one of the following:
•
PROCESSING
The remote user has entered a valid SIGNON or
LOGON command. For BSe users, the remote-ID is
displayed together with the line status. For SNA
users, the session is logged on and a processor
(for example, Inbound or outbound) is active on
the session.
•
NOT LOGGED ON
No SRA user is currently logged on to the
specified logical unit ("luname" specification).
This status information is not applicable to BSC
lines.
•
LOGGED ON
The session is logged on, but no processor is
active (not applicable to BSC lines) •
•
LOGGING ON
The session is in process of being logged on (not
applicable to BSC lines).
•
INACTIVE
The line has been started by the central operator
with a PSTART command, but no user is currently
signed on (applicable only to BSC lines) •
•
NOT INITIATED
The line has not been started by the central
operator (applicable only to BSC lines) •
•
~OT
Support for the line was not provided during
POWER/VS generation (applicable only to BSC
lines) •
66
SUPPORTED
POWER/VS Installation Guide and Reference
Display the status of all supported lines.
PINQUIRE ALL
Line status report produced:
030
031
032
033
034
RT74
PROCESSING 22
PROCESSING 150
PROCESSING 4
NOT INITIATED
INACTIV~
LOGGED ON 041
The PRELEASE (or R) command takes one or more POWER/VS jobs out of the
hold or leave state and makes them available for processing. If ALL or
"class" was specified in the PRELEASE command, jobs with disposition L
are not released.
After processing, a job originally in the leave state
has its queue entry returned to disposition L. output of a POWER/VS job
that is directed to a terminal can be released only from the terminal.
i
IOperation
IOperands
I R
I
I
I
I
I,
I
I queue, ALL
,
I queue, class
I
I gueue,*abc
queue
specifies the queue for which the command is to be
executed in the form:
1---------------------------------------------------------------------'{PRELEASE}
I queue,jobname[ ,jobnumber]
--
LST
PUN
RDR
for list queue
for punch queue
for reader queue.
jobname
specifies the job name, consisting of 2 to 8 alphameric
characters including It/", ".It, and "-", by which the
entry is known to POWER/VS.
jobnumber
specifies the 1- to 5-digit job number assigned to the
entry by POWER/VS. Use the PDISPLAY command to determine
the job number.
ALL
specifies that all POWER/VS jobs in the queue, except
those with disposition L, are to be released.
class
specifies that all POWER/VS jobs, except those with
disposition L, of a certain class in the specified queue
are to be released. Valid specifications are A - Z and
o - 6.
*abc
specifies that POWER/VS jobs in the specified queue whose
names begin with the specified characters are to be
released. You can specify up to seven alphameric
characters (including "/", ft.", and It_") in place of abc.
Chapter 3.
Using POWER/VS
67
The central operator may not release jobs routed to a remote
terminal or work station.
HQ1~:
PRELEASE LST,PAYROLL
Release POWER/VS job PAYROLL in the list queue.
PRELEASE RDR,ALL
Release all POWER/VS jobs in the reader queue.
PRELEASE LST,*PAY
Release all POWER/VS jobs in the list queue whose
names begin with PAY.
PRESTAR!~2mmand
The PRESTART (or T) command restarts printed or punched output for a
POWER/VS job from the beginning or from a specified page or card, within
the segment. It can only be used while the task is active.
I
i
IOperation
I
IOperands
1----------------------------------------------------------------------1
'{PRESTART}
1 uraddr,( n I ,i)
1
I, T
I uraddr
i
l
,
specifies the unit record device associated with a list
or punch writer task.
n
specifies a signed or un~igned value from 0 to 9999. A
plus sign indicates page or card forward, a minus sign
indicates page or card backward from the point where
processing was interrupted. No sign indicates a
specified count from the beginning. If you specify too
great a backward count, or if the operand is omitted,
printing or punching is resumed from the first page or
card. If you specify too great a forward count, a
message is issued and the command is ignored.
i
specifies the copy group index to be used for the
restart. Any value between 0 and 8 is valid. When 0 is
specified, a value of 1 is used. When i is omitted,
output processing continues with the copy group index
currently used. This operand is valid only for an IBM
3800 Printer.
PRESTART 00E,-10
!!otg,:
c~nnot
68
Reprint the previous ten pages and continue.
After a "PSTOP uraddr,RESTARTIt command has been issued, PRESTART
be used.
A PSTART must be given before to reactivate the task.
POWER/VS Installation Guide and Reference
The PSETUP (or U) command prints one or more pages of list output with
all printable characters of a page replaced by the character X.
When
the PGO command is issued to resume printing, the pages are printed
again with their original contents. The command allows you to check and
adjust forms alignment. Adjust.ent is made manually while printing of
the setup pages is in progress. The PSETUP command may be used only
after message 1Q40A or lQA51 has been received.
i
•
IOperation
IOperands
I
,
I
I
1----------------------------------------------------------------------1
'{PSETUP}
luraddr[ ,n]
I
U
I
I
uraddr
specifies the device address of the printer on which the
pages are to be printed.
n
specifies the nu.ber of pages to be printed as one or two
digits. If n is omitted, only one page is printed.
12~:
A page is defined as a skip to channel 1. That
means: if a job output does not contain skips to channel
1, POWER/VS will count the entire output as one page.
If
a PSETUP is issued in this case, the complete job output
will be printed with X characters.
PSETOP OOE,2
Print two
setu~
pages
Page 1
xxxX'
xx xxxxxx
xx xxxxxxxx
xxx xxx
xxxxx
xxxxx
x
x
xxxxxx
xxxxxxxx
xxxxxx
Page 2
xxxx
xx xxxxx
xx xxxx
xxxxxx
xxxxx
xxxxx
x
x
xxxxxx
xxxxxx
xxxxxx
When the PGO command is issued to resume printing, the pages are printed
again with their· original contents.
Page 1
NAKE
L. KEEFFE
N. REYNOLDS
SALARY
HOMBER
69060
41240
$
$
NUMBER
33110
76779
$
$
1,080.05
798.83
Page 2
NAKE
D. HALEY
A. WATT
SALARY
497.11
699.42
Chapter 3.
Using POWER/VS
69
A PSTART (or S) command starts either a partition or a reader, writer,
or RJE task.
task,uraddr,tapeaddr
RDR. ,craddr,[
class) ,duaddr( ,2]
RDR,duaddr,(class), 'file-ide ,[vols),( S)[ ,V]
RJE,lineaddr[ ,password]
RJE,SNA
specifies the task to be started in the form:
task
RDR
LST
PUN
for reader task
for list task
for punch task.
uraddr
specifies the unit-record device associated with the
reader or writer task. You may specify X'cuu' or cuu.
class
For a writer task, this operand specifies the output
class or classes that the task may process. up to four
classes may be specified by any four alphabetic
characters from A to Z. The order in which classes are
specified will be the order of processing. The default
class is A.
For a reader task, this operand defines the input class
that is to be assigned to all jobs without a class specification in their * $$ JOB cards (provided no * $$ CTL
statement is in effect). "class" is specified as an
alphameric character from A to Z, or from 0 to 6. The
default class is A.
For a partition, this operand is used to define the input
class (or classes) of the jobs that may be executed in
the partition. Up to four classes may be specified using
from one to four alphameric characters: A to z or 0 to 6.
The order in which classes are specified will be the
order of execution. If class is not specified, only
partition-dependent jobs (that is, POWER/VS jobs with a
matching partition-type input class) are selected.
n
specifies the number of buffers that the task will use.
Valid speCifications are 1, 2, or D, where:
1
2
D
70
1 buffer
2 buffers
4 buffers (2 input and 2 output buffers).
POWER/VS Installation Guide and Reference
The specification of D is valid only for a list writer
task and if the ICR is installed. The operand n is
ignored for a punch writer task. If the operand is
omitted, the task is started with one buffer.
!Qte: Storage for the buffers is used only as long as
the task is active.
When the task becomes inactive, the
buffers are released and the storage is returned to the
POWER/VS storage pool.
partition
specifies the partition to be brought under the control
of POWER/VS. If the partition is already controlled by
POWER/VS, the PSTART command acts the same as a normal
attention routine START command. A message is issued if
the partition is still active or not supported, or has a
higher priority than the POWER/VS partition. valid
specifications are BG or Fn, where n is the partition
number.
outclass
specifies the default class of this partition's output.
nay be any alphabetic character. The default is A.
ftT
specifies that this partition is to support a never
ending (or long running) multitask job. When no more
cards are available for the partition, only the task
which reads cards is placed in the wait state. Other
tasks continue and provide output. Segmentation of the
output is controlled via the LFCB macro (forms control
buffer printer only) or the SEGMENT macro (printer and
punch output). The initial job stream for this partition
should have a LST and PUN statement for each spooled
output device that may be used. A PSTOP command for this
partition also cancels the multitasking parameter.
tapeaddr
specifies the address of the tape drive on which a spool
tape is mounted. Only list and punch tasks can he
started from a tape. "tapeaddr" must be specified as
X·cuu'.
craddr
specifies the address of the card reader for a reader
task that is to read input from both a card reader and a
diskette. You may specify X'cuu' or cuu.
duaddr
specifies the address of the 3540 diskette unit whose
input is to be spooled. You may specify X'cuu' or cuu.
2
specifies that a reader task is to be started with two
buffers. If this operand is not specified, the task is
started with one buffer.
'file-ide
specifies the name of the diskette file, to he read; it
must be identical with the file name in the HDR1 label on
the diskette. One to eight alphameric characters,
including blanks, may be entered between the quotes.
vols
specifies the maximum number of diskettes to be read.
The reader task terminates either aft~r the specified
number of diskettes has been read or at the end of a
diskette whose HDRl label indicates that this is the last
diskette of the file.
Any decimal number from 1 to 255
may be specified; the default is 1.
Cha~ter
3.
Using POWER/VS
71
S
specifies that volume sequence checking is desired. The
sequence number of the first volume must be 1 and the
numbers of succeeding volumes must be specified in
increments of 1.
v
specifies that only diskette files that have been
verified are to be accepted. If 'V' is specified and the
diskette file to be read has not been verified, the file
will be rejected. If the parameter is omitted, no
checking for whether diskette f~les have been verified
will be carried out.
RJE
specifies that the command was given to start an RJE,BSC
task.
lineaddr
specifies the line address associated with the RJE task.
You may specify the line address as X'cuu' or as cuu.
password
specifies a password consisting of up to eight
characters. If you specify a password, the remote
operator can only sign on by specifying the same password
in his * •. SIGNON command.
RJE,SNA
causes POWER/VS to activate the VTAM interface. Upon
completion, a message is sent to the central operator
indicating that the SNA work stations may now log on.
PSTART RDR,OOC,2
start reader task on X'OOC'. Assign class 2 to
all jobs without class assignments.
PSTART RJE,030,NEWYORK start an RJE task on line 030.
security password.
PSTART LST,OOB,AB
PST~RT
PUN,OOD,X'285 t
NEWYORK is the
start a list task on X'OOB' to print output
output from POWER/VS jobs with classes A and B.
start a punch task on X'OOD' to punch output that
was spooled onto tape mounted on drive X'265'.
PSTART Fl,AB
Bring F1 under control of POWER/VS. Select (for
execution) input classes A and B only.
PSTART RDR,OOC,,2
start a reader task on X'OOC' with two buffers.
Assign class A to all jobs without class
assignments.
PSTART F2,Z,B,MT
Bring F2 under control of POWER/VS. Select (for
execution) input class Z only. The default
output class for this partition is B. This is a
multitask partition.
Hote: If you want to process a diskette containing more than one SYSIN
file, one specific PSTART command is required for each SYSIN file to be
processed.
72
POWER/VS Installation Guide and Reference
PSTOP Command
The PSTOP (or P) command stops a reader, writer, or RJE task, or
releases a partition from POWER/VS control.
Unless modified by the EOJ operand, PSTOP terminates tasks in the
following way: when a reader task is stopped, further input processing
for the POWER/VS job being read is terminated. No entry for that job is
placed in the input queue. When a writer task is stopped, further
output processing is terminated, but the terminated output is not
deleted from the output queue. When the task is started again,
processing of this output starts with the first record.
For reader/Writer or RJE,BSC tasks r POWER/VS acknowledges the PSTOP
command with a message at both the central location and the terminal.
I
I Operation
IOperands
1---------------------------------------------------------------------'{PSTOP}
I uraddr[,EOJ
]
, P
I
I
I
I
I
1 partition
I
1 lineaddr[,EOJ]
I
uraddr
specifies the unit-record device address associated with
the reader or writer task. You may specify X'cuu' or
cuu.
EOJ
specifies that the task will not stop until it has
completed processing for the current POWER/VS job. This
means (1) for a reader task that it viII not stop until
all input for the POWER/VS job being read has been
spooled and (2) for a writer task that it will not stop
until all currently processed printed (or punched) output
for a particular POWER/VS job is complete. EOJ should
always be specified for RJE tasks, unless an emergency
occurs.
RESTART
specifies that when the task is restarted, processing
will begin at the record following the last one processed
before the PSTOP command was issued. ,This applies also
when the number-of-copies value was specified greater
than 1. RES~ART applies only to output processing.
I
I
I
,RESTART
I RJE,SNA[ ,EOJ]
I
I RJE, SN A,luname[ , EOJ]
!2!~:
If neither RESTART nor EOJ is specified when an
output task is stopped, processing will begin with the
first record of the same output when the task is started
again by a PSTART command.
The PRESTART co •• and cannot be used after a PSTOP
com.and.
Chapter 3.
Using POWER/VS
73
partition
specifies the partition to be stopped. When a partition
is stopped by means of a PSTOP command, the partition not
only is stopped, but is completely released by POWER/VS.
This form of the PSTOP command is not effective until all
processing for the POWER/VS job currently being executed
is completed. Valid specifications are BG or Fn, where n
is the partition number. Note, however, that only
partitions under POWER/VS control can be stopped by means
of this comlland.
After the partition has been released by POWER/VS, the
partition may be started as a normal batch partition
using the START command. To restart it as a POWER/VScontrolled partition, use the PSTART command.
lineaddr
specifies the line address (X'cuu' or cuu) associated
with the RJR task.
RJE,SNA
causes POWER/VS to deactivate the VTAM interface
immediately. The optional specification EOJ allows an
orderly termination; that is, active inbound or outbound
processes may continue until the current job entry is
completed.
luname
specifies, in combination with the operands RJE,SNA (and
in addition, optionally, EOJ) that POWER/VS is to
deactivate only the session identified by the "luname ll
operand. For multiple logical unit work stations,
individual sessions may be logged off by the central
operator without logging off the entire work station.
EZs,!!lElg§:
PSTOP OOE,EOJ
Stop the list writer task operating on OOE after it
has completed printing the list output of the current
POWER/VS job.
PSTOP 030
Stop the RJE task operating on line 030 immediately.
If this task is reading, the input records already
spooled for the current RJE job are lost. If the
task is writing, output will start from the first
record of that output when the task is restarted.
PSTOP OOD,RESTART
stop the punch task opgrating on OOD. When the task
is started again, processing of the stopped entry
will continue at the point of interruption.
PSTOP F3
Release partition F3 from control of POWER/VS after
execution of the POWER/VS job currently being
processed is complete.
PSTOP RJE,SNA,EOJ
Stop all RJE,SNA sessions as soon as processing of
all jobs in all sessions has been completed.
PSTOP RJE,SNA,SESl Terminate the SNA session with the name SESl
immediately.
74
POWER/VS Installation Guide and Reference
POWERIVS Job Entry Control Language Statements
Under POWER/VS, a job is not necessarily the same as a job under DOS/VS.
To define a job to POWER/VS and have that job logged in the system, the
POWER/VS job entry control language (JECL) or the DOS/VS jOb control
language (JCL) may be used. Exa.ples are shown in Figure 3-2.
If Jet is used, a job is logged under the name specified in the / / JOB
statement, and this statement, together with the /& statement, delimits
the job. If JECL is used, the * $$ JOB and * $$ EOJ statements delimit
a job, and the name specified in the * $$ JOB statement is used to log
the particular job. A job defined to POWERjVS by using JECL may
comprise several DOS/VS jobs or only part of such a job.
You should be aware that POWERjVS will generate a /& in the job stream
in two instances:
•
If POWER/VS reads a / / JOB statement without an immediately preceding
/& statement.
•
-
If several POWER/VS jobs are defined for one DOS/VS job, where an
$$ JOB statement is not immediately preceded by an * $$ EOJ
statement.
*
Because JECL statements begin with an asterisk-blank, job control treats
them as comments when POWER/VS is not in operation. This also means
that for a writer-only system, dual entries would be created for LST,
PUN, and PRT statements. Because this is not allowed, II OPTION NOLOG
should precede the JECL statements.
POWER/VS assigns a number to each job name that it logs 'in order to
distinguish between jobs for which identical names were specified. You
must use that name and, possibly, the number assigned to it whenever you
issue an operator command to control the processing of that job entry.
Once a job has been defined to, and logged in, the system by POWER/VS,
that job is referred to as a POWER/VS job. The first LST (and the first
PUN) output from a POWER/VS job will have the same numb9r as the input
job. However, any subsequent LST or PUN entries will have unique job
numbers in order to facilitate queue manipulation. All segments of
count-driven segmentation (RBS=xxx) will have the same number as the
first segment. For accounting purposes, all output contains the job
numb~r of the reader queue entry when a record is placed in the account
file.
Chapter 3.
Using POWER/VS
75
DOSIVS
Job Stream
Comments
/I JOB ONE
II EXEC JOBSTEPA
OOSIVSJob.
with no JC L changes.
1&
II JOB lWO
/I EXEC JOBSTEPB
*$$ PUN CLASS=X
.1/ EXEC JOBSTEPC
No "$$ JOB/EOJ required
for LST or PUN statements.
1&
*$$ JOB THIRD
/I JOB THREE
/I EXEC JOBSTEPD
Optional POWER/VS JECL.
Required if SVSIPT statements
include a 1/ JOB card,
1&
*$$ EOJ
*$$ JOB FORTH
II JOB FOUR
/I EXEC JOBSTEPE
1/ EXEC JOBSTEPF
No *$$ EOJ required, if
POWER/VS job is followed
by *$$ JOB statement.
1&
"$$ CTL CLASS=B
*$$ JOB FIFTH
/I JOB FIVE
/I EXEC JOBSTEPG
No *$$ EOJ required.
1&
*$$ JOB SI XTH
/I JOB SIX
1/ EXEC JOBSTEPH
1&
/I JOB SEVEN
Multiple DOS/vS jobs in one
POWER/VS job.
(*$$ JOB and *$$ EOJ are
both required for thi •• )
/I EXEC JOBSTEPI
1&
*$$ EOJ
*$$ JOB SEVENTH
II JOB EIGHT
II EXEC JOBSTEPJ
*$$ EOJ
*$$ JOB EIGHTH
Multiple POWER/VS jobs for
one DOS/VS io6.
II EXEC JOBSTEPK
1&
*$$ EOJ
*$$ CTL CLASS=A
Default CLASS reset to A.
II JOB NINE
II EXEC JOBSTEPL
POWER/vS will generate the
missing 1&.
/I JOB TEN
*$$ LST FNO=8Xll
/I EXEC JOBSTEPM
*$$ LST
/I EXEC
.J"t: ... ~.·"nJ:>"~
Multiple LST outputs per job
(2nd report is segmented.)
Int.CT'''!) .. '
1&
Figure 3-2.
76
Examples of the Use of POWER/VS JECL
POWER/VS Installation Guide and Reference
FUNCTIONS OF JECL STATEMENTS
JECL provides a convenient means for the programmer to specify how
POWER/VS is to handle a particular job. He may use JECL statements for
the following:
1.
Under POWER/VS and POWER/VS RJE to:
•
•
•
•
•
•
•
•
•
•
2.
Assign job execution priorities.
Assign input and output dispositions.
Hold a job entry in one or all queues.
Direct unit-record print or punch output to tape rather than t~
disk.
Suppress spooling of unit record print or punch output.
Specify the partition in which the job entry is to be executed.
Specify the input or output class.
Request segmentation of lengthy output.
Insert source statement library data into the input stream.
Specify 3800 printer character style selection, bursting, forms
overlay flashing, and copy modification.
Under POWER/VS RJE only to:
•
•
•
Direct output to another user or messages to all terminal users.
Direct output to be returned to a terminal or to be processed
locally at the central system.
Specify compaction table names (SKA only) •
Normally you will not be concerned with the completion of JECL
statements; you may, however, be called upon to change or correct JECL
statements that your programmer prepared and inserted in the job stream.
Por the JECL statements * $$ LST, * $$ PRT, and * $$ PUN, POWER/VS
provides the possibility of error correction at job execution time.
If
one of these statements was incorrectly specified, the central operator
receives a message indicating the error. He may then do;one of the
following:
•
Correct the erroneous statement
•
Ignore the error
•
Plush the job.
To correct the error, the central operator types in a correct JECL
statement, upon which the system processes this statement and continues
executing the job.
To ignore the
corresponding
console. The
parameters in
error, the central operator enters End-of-Block or a
command (depending on the type of console) at the system
system then selects default values for the JECL statement
error and continues processing.
To flush the job, the central operator enters PLUSH.
processing the next job in the associated queue.
The system starts
PORKAT OF JECL STATEftENTS
A JECL statement must be completely contained in columns 1-11; column 72
of a single statement Bust be blank. If the statement is continued,
column 72 must contain a non-blank character. However, LST and PUN
Chapter 3.
using POWER/VS
77
statements cataloged in SL! books cannot be continued. Columns 73-80
may be used as a sequence field.
This is illustrated in Figure 3-3.
Columns
1-4
,
,
J
L
1
$$
I
I
0
Figur~
3-3.
173-80
112
Identifi- 1Operation
cation
IField
Field
*
I
I
,5-71
®
IOperand
IField
I
1
I
I
I
I Comments
I Field
,
I
®
I
I
I
0
IContin-ISeguence Field
luation I
(Field
I
I
I
I
I
I
I
®
I
I
®
Format of JECL statements
Each JECL statement consists of the following fields:
Contains the characters * $$ in columns 1
through 4. Column 2 must be blank.
This field can be used for
POWER/VS purposes only.
1.
I~niifi£S!iQll-fiel~:
2.
Q~ration field:
Specifies the JECL operation. It may either
directly follow the second dollar sign or be separated from the
second dollar sign by one or more blanks. At least one blank must
separate the operation field from the operand field.
3.
Q£grand field:
Contains one or more positional or keyword
parameters, separated by commas. A blank terminates the operand
field; therefore, no parameter may contain embedded blanks. Keyword
or positional parameters cannot be mixed within one statement.
When a keyword parameter contains subparameters, the subparameters
must be se~arated by commas and enclosed in parentheses. When only
one subparameter is specified, the parentheses can be omitted.
~otg:
Some POWER/VS features are supported only through keyword
notations.
Positional parameters must be specified in a fixed order. If a
positional parameter is omitted, its delimiting comma must be coded.
If trailil g parameters are omitted, trailing commas can also be
omitted.
If no parameters are specified, the entire operand field
can be om tted. When a comment field is present and the entire
operand field is blank, the omitted operand field is indicated by a
comma, which is preceded and followed by at least one blank. If the
operand f~eld exceeds column 71, the field may be continued
according\to the following rules:
78
•
The operand field can be broken after a comma that separates two
parameters, and can be continued on the next card starting from
columns 6 through 16. Column 72 of the first card must contain a
nonblank character. This process can be repeated for as many
cards as are necessary. Continuation cards are not supported for
LST or PUN statements within SLI books.
•
Columns 1 to 4 of each continuation statement must contain
(asterisk-blank-dollar-dollar). Column 72 of a one-card
statement or a last continuation card must be blank.
POWER/VS Installation Guide and Reference
*
$$
4.
£omments field:
Bay contain any information. This field can be
broken off anywhere and continued on the next card in any column,
subject to the same rules given for the operand field.
5.
Continuation field:
As stated above, this field (column 72) is used
to indicate that the inforaation in the present card is continued in
the next card.
6.
~~gY~£~-ii§!g:
May contain up to eight characters of optional
information used for coutrol statement identification. If present,
the sequence field is positionally dependent and .ust start in
column 73.
Note:
POWER/VS converts all POWER/VS JECL statements (including
continuation cards) and DOS/VS JCL statements (starting with / / in
columns 1 and 2) to uppercase characters before they are written onto
the POWER/VS data files.
The sequence field (columns 13 to 80) will not
be converted.
?be DOS/VS coamands /*, /&, per. anent ASSGN and comment statements are
not converted to uppercase.
OSING JECL STATEMENTS
Figure 3-4 lists all JECL statements, together with a brief explanation
of their functions, in alphabetic order. This overview is followed by
detailed discussions of the function and the parameters of each of these
statements.
,
I JECL statement
I Function
1---------------------------------------------------------------------1* $$ CTt
Assigns a new default input class to
jobs.
PO~ER/VS
I
1* $$ DATA
t
Inserts data from the reader queue into a book
being read from a source statement library.
*
$$ EOJ
Indicates the end of a POWER/VS job.
*
$$ JOB
Indicates the beginning of a POWER/VS job and
provides handling information.
* $$ LST
Provides handling information for printed output.
*
*
*
$$ PUN
Provides handling information for punched output.
$$ RDR
Inserts a diskette file into the ,input stream from
a card reader.
*
$$ StI
Inserts data from a source statement sublibrary
into the job stream.
*
$$ /*
Indicates the end of a POWER/VS job step (used withl
the 5L! statement only).
I
*
$$ /&
Indicates the end of a POWER/VS job (used with the I
SLI statement only),.
I
$$ PRT
J
I
Figure 3-4.
JECL Statements
Chapter 3.
Using
PO~ER/VS
19
The CTL, JOB, and EOJ statements should be presented at DOS/VS job
control time. All other JECL statements can be included anywhere in the
input stream. Kore than one LST or PUN statement is allowed per
POWER/VS job.
JECL (* $$ JOB and * $$ EOJ) must always be used in a writer-only
partition (a partition that uses POWER/VS only for its output) and is
used with the following restrictions:
•
RDR, CTL, SLI, and DATA statements are treated as comments.
•
LgT and PUN statements are recognized at job control time, or whp.n
user-generated and written to SYSLOG.
•
A number of JOB statement parameters are not meaningful and are
ignored.
•
Output produced outside the bounds of a POWER/VS-defined job will be
ignored.
!Q!g:
Data-driven output segmentation is not supported in a writer-only
partition.
JECL statements contained in a user data stream are considered to be
data if read by a writer-only partition. This allows source statement
books containing, JECL statements to be cataloged. Specifically, LST,
PUN, and DATA statements should be included in source statement books.
But a JOB statement will only appear on SYSLOG, and an EOJ statement
will act as "no operation". SLI is invalid in a source statement book
which is to be cataloged.
Notg:
For most of the JECL statements, you may specify parameters
either in the keyword or in the positional form; but do not use both
forms in the same statement. If you use the positional form, you must
code a comma whenever you omit an operand, except at the end of a
statement. For example, in the statement
*
$$ PUN H,,03
omission of the "forms-number" operand is indicated by the second comma
following the character H, while omission of the "norbml" operand at the
end of the statement requires no extra comma.
An optional parameter of a command is shown enclosed in brackets.
Braces enclose alternatives, one of which must be chosen. Stacked
options represent alternatives, one and only one of which may he chosen.
80
POWER/VS Installation Guide and Reference
The * $$ CTL statement allows you to assign a new default input class
specification for POWER/VS jobs that are not controlled by JECL, or for
which the class parameter was omitted from the * $$ JOB statement. The
* $$ CTL statement may be placed at any POWER/VS job boundary. It
overrides all input default class specifications presently in force and
remains in gffect until the next * $$ CTL statement is encountered or
the reader task is stopped with a PSTOP command. The statement is
ignored in a Writer-only system.
I
,
IOperation
IOperands
I
I
I
1---------------[------------------------------------------------------,
t * $$ CTL
1 CLASS=!!
}]
1
,
!2~g:
lclass
,
J
This statement is only available in the keyword format.
CLASS=
specifies the input class to which all subsequent jobs
are assigned if they do not contain a class specification
in their * $$ JOB statement. The CLASS= parameter may be
used in order to group jobs that require the same I/O
configuration, partition, or other resources for
execution. If CLASS= is not specified, class A is
assumed. The class specification may be specified as any
alphabetic character from A to Z or as a single number
from 0 through 6. When specified as a number, the input
is partition-dependent.
The CLASS= parameter in the * $$ CTL statement overrides
the class specified in the PST ART command, which
overrides default class A.
The * $$ DATA statement allows you to insert data into a book that is
retrieved from the source statement library by an * $$ SL1 statement.
Input following the DATA statement must be terminated by a /* or /&
statement. DATA statements must be preceded by an * $$ SLI statement;
otherwise, they are treated as comments. * $$ SLI update statements
($SLI in columns 73-76) and * $$ DATA statements may be used together.
However, they must appear in the job stream in the same order as the
corresponding images appear in the source statement library book. The
statement is ignored in a writer-only partition.
j
•
IOperation
I
IOperands
1----------------------------------------------------------------------1
1* $$ DATA
I nalle
I
,
!Q~~:
name
_--J
This statement is only available in the positional format.
specifies the nalle of the corresponding * $$ DATA
statement in the source statement library book whe~e data
is to be inserted. The name can be from one to eight
alphameric characters, the first of Which must be
alphabetic.
Chapter 3.
Using POWER/VS
81
The * $$ EOJ statement marks the end of a POWER/VS job and, if used, is
normally placed at the end of a DOS/VS job or job step. This statement
is required in a writer-only partition. If this statement is submitted
at any other time than DOSjVS job control time, it is still acted upon
by PO~ER/VS.
1r Operation
,Operands
I•
1----------------------------------------------------------------------1
1* $$ EOJ
I
I
,
J
This statement has no operands.
!
$$ JQB Statement
The * $$ JOB statement may be placed anywhere in a DOS/VS job stream to
specify POWER/VS job attributes or to begin a POWER/VS job. This statement is required in a writer-only partition.
An * $$ JOB statement encountered in the input stream without a
preceding * $$ EOJ statement is used as a delimiter for the previous
POWER/VS job. If the * $$ JOB statement is omitted, POWER/VS jobs are
delimited by the / / JOB and /& job control statements. The POWER/VS job
name is then copied from the DOS/VS job name.
H212:
In a writer-only partition, an
any subsequent * $$ JOB statement.
*
$$ EOJ statement must precede
Positional format:
I
,
IOperation
IOperands
1,
I jobname
1
1----------------------------------------------------------------------1
1* $$ JOB
1[AUTONAPlE] , [~
] ,[ pr iori ty J,[ class]
I
82
disposition
POWER/VS Installation Guide and Ref.erence
,I
Keyword forllat:
Operation
I•
IOperands
----------------------------------------------------------------------J
$$ JOB
I [J!U'=f~1l!.QN1K'E!}]
*
I
lJobname
I [,DIsp={n
\]
I
dispositionJ
I
I( ,PRI=priority]
I
t[ ,CLASS=class]
I
I[ ,OSER=user information]
L____________________________________________________________________________
~
!2!~:
JNM=
The USER operand can only be specified in the keyword format.
specifies the name by which the job and its queue entries
are known to POWER/VS. If the job contains several
DOS/VS jobs, they are all logged in POWER/VS by the job
naae in the * $$ JOB statement. The default name
AUTONAKE is assigned if "jobname" is not specified. The
job name may be specified as two to eight alphameric
characters (0 - 9, A - Z, #, $, it, / , -, or period
The use of the job names ALL, HOLD, FREE, RJE, LOCAL, or
one-character job names should be avoided as they may
conflict with some POWER/VS operator commands.
(.».
DISP=
specifies how POWER/VS will route and schedule the
associated entry in the read queue. It may be one of the
following: B for hold, K for keep, L for leave, or D for
delete after processing. The default is D.
D - Delete after processing. The job is automatically
scheduled by POWER/VS according to its class and
priority. After job execution, the read queue entry
is deleted from the read queue and the data file
space is released.
H - Hold job. The job remains in the read queue; it is
not dispatched by POWER/VS until the operator changes
the disposition to D or K by means of the PALTER
command or issues the PRELEASE command.
K - Keep after processing. The job will be automatically
scheduled by POWER/VS according to its class and
priority. After job execution, the read queue entry
is not deleted from the read queue, but the
disposition becomes L.
L - Leave in queue. The job remains in the read queue;
it is not dispatched by POWER/VS, until the operator
changes the disposition to K or 0 by means of the
PALTER com.and or issues the PRELEASE command.
EQ~:
The specification of a disposition is ignored in a
writer-only partition.
Chapter 3.
Using POWER/VS
93
PRI=
specifies the priority assigned to this job in both input
and output queues.
It is specified as a single digit
from 0 to 9. Nine is the highest priority.
If the
priority parameter is not specified, POWER/VS assigns the
default priority defined in the PR~= parameter of the
POWER macro. Jobs are dispatched on a first-in-first-out
basis within priority and class. The specification of a
priority is ignored in a writer-only partition.
CLASS=
specifies the class that is assianed to the job entry in
the input queUe.
It may be specified as an alphabetic
character from A through Z, or as a numeric character
from 0 through 6. This parameter may be used to group
jobs that require the same I/O configuration, partition,
or other resources for execution. The specification of a
class is ignored in a writer-only partition.
Classes 0 through 6 have a specific meaning and are
called the partition-dependent classes. Jobs with class
o can only be selected for execution in the background
partition, jobs with class 1 in partition F1, and so on.
If the class parameter is omitted, the class
specification is taken from the CTL statement.
If no CTL
statement is specified, the class is established by the
PSTART command. If no class is specified at all, default
class A is assigned.
Note:
When the * $$ JOB statement is coded in its
positional form, class 0 may be coded as BG, and classes
1 through 6 may be coded as F1 through F6.
USER=
84
Up to 16 bytes of user information may be specified.
If
JLOG=YES was specified during POWER/VS generation, this
information is printed on SYSLOG when the execution read
task encounters an * $$ JOB statement. The POWER/VS user
information also appears in the POWER/VS account records
and in separator pages. The user information must be
specified as alphameric unless it is enclosed in single
quotes.
POWER/VS Installation Guide and Reference
~~T
(* $$ PRIL Statement
The * $$ LST (or * $$ PDT) state.ent defines the attributes of the
intercepted list output of a POWER/VS job. LST and PRT are eguivalent
operation codes. Any number of * $$ LST statements is permitted for
each POWERjVS job, except in a reader/writer partition, where only one
statement for each device and for each job is allowed. If the * $$ LST
statement is not included in the job, the default values established
during POWER/VS generation ar~ assumed. Additionally, when an IBM 3800
Printer is being used, the default printer setup values established for
the 3800 by the SETDF operator com.and are taken.
certain parameters (BURST, CHARS, COPYG, DFLT, FLASH, and MODIFY) on the
* $$ LST statement are only valid for the IBM 3800 Printer. For more
information on the 3800 and the use of these parameters see the ~OS/VS
IBM-180tlrintinq~ubsy§tem Prograo!tI.!§ Guidst, GC26-3900.
* $$ LST statements do not reguire that
also be used.
*
$$ JOB and
*
$$ EOJ statements
The specifications of a particular * $$ LST statement remain in effect
until a subsequent * $$ LST statement for the same printer (LST=) is
issued, or until the end of the POWER/VS job.
For each * $$ LST statement within a POWER/VS job, a separate list queue
entry and job number is created (data-driven output segmentation). The
first list entry will contain the sa.e job number as the associated RDR
queue entry. However, any subsequent list entries will have a unique
job number. Repeated use of the SEGKENT macro in the same job will have
the same effect.
No~~:
nata-driven output segmentation is not supported in a writer-only
partition.
/ / ASSGN statements must have been issued for the printer referred to by
the LST or PRT statement.
If an error is detected in the * $$ LST (* $$ PRT) statement, the
central operator may correct the statement during job execution.
positional format:
I
Operation
1
IO?erands
----------------------------------------------------------------------1
LST
I [!!
[!]J ,[ forms-number],
I
* $$
or
* $$
PRT
I disposition class
I '
I
I
![~umber-Of-coPiesJ,[nOrbm'),[linetab)
I
I tapeaddr
I
L -_________________________________________________________________________ - - - J
Chapter 3.
Using POWER/VS
85
Keyword format:
I
Operation
*
-------------------------------------------------------I
[DISP={~disposition}]
$$ LST
or
*
I
IOperands
I
,
$$ PRT
[
,CLASS={!
}]
class
[ ,PRI=priori ty ]
[ , REMOTE=rell id ]
[,
FNO:{;o~!:~::mber}]
[ ,JSEP= (sep[ ,option]) ]
[ ,COPY:{'number-Of-copies }]
[ ,COPYG= (groupvalue( ,groupvalue •••
J) J
[ ,TADDR=tapea1dr]
[,RBK=(norblll,norbm2) ]
[ ,LTAB=linetab]
[ , RBS=norbs]
[,UcS=(phasename[,option) ]
[ ,FCB=phasename)
[ ,LST=lstaddr]
[,CMPACT= {:~me}]
[ ,CHARS= (tablename[ , tablename ••• ]) ]
I ['DFLT={~} ]
I
I[ ,FLASH= ([ overlayname][ ,count]) ]
I
'[ , aODIFY= (coPYllodnaae[ , tablen ame]) ]
Noig:
The operands PRI, RE"OTE, JSEP, COPYG, RBS, ncs, FCB, LST,
CMPACT, BORST, CHARS, DFLT, FLASH, and MODIFY can only be specified in
the keyword form of the statement.
86
POWER/VS Installation Guide and Reference
DISP=
specifies the disposition of the printed output after
execution of the job. The disposition specification
options are listed below:
D - Delete after processing. The list queue entry is
written to a printer according to its class and
priority ..
H - Hold.. The list queue entry remains in the list
queue; it is not written to a printer by POWER/VS
until the operator changes the disposition to D or K
by means of the PALTER command or issues the PRELEASE
co •• and.
K - Keep after processing..
The list queue entry is
automatically written to a printer according to its
class and priority. When printing is completed, the
list queue entry is not deleted from the list queue,
and the disposition of the queue entry becomes L.
L - Leave in queue.
The list queue entry remains in the
list queue; it is not written to a printer until the
operator changes the disposition to D or K by means
of the PALTER command or issues the PRELEASE command.
H - Output without spooling. If N is specified, print
requests are not intercepted. output is written
directly, without spooling. In this case, all other
parameters (except "LST = .... ") are ignored. If the
N option is specified, and the device to which SYSLST
is assigned is not available at execution time,
message OP31D (device not operational) may be issued
repeatedly.
--
T - Spool to tape intermediate storage.
to initiate printing.
PSTART is used
If the disposition specification is omitted, D is
assumed.
0, H, K, and L are only valid when the output is spooled
to disk.
When the output is to be printed at a terminal, Nand T
are invalid options.
CLASS=
specifies the class of the printed output after execution
of the job. It may be specified as any alphabetic
character (A through Z). A class may be specified in
conjunction with "forms-number" to group together the
salle types of printed output. "class" is only meaningful
when the output is spooled to disk. If a class is
specified and the positional form is used, a disposition
must also be specified. If "class" is omitted, A is
assigned. If the * $$ LST statement is omitted, an
output class can be specified in the PSTART command.
There is no comma between disposition and class in
the positional form. A blank must separate these tvo
parameters.
IQ~:
PRI=
specifies the priority (0-9) of the LST output.
is the priority of the job.
Chapter 3.
Default
Using POWER/VS
87
REKOTE=
specifies the TO remote-ID to which list output is to be
routed. Each list queue entry also has assigned to it a
FROM remote-ID, which identifies the user who initially
submitted the job. The uremid" specification can be a
number from 0 to 200. Numbers 1 to 200 represent
specific remote users. If "remid" is 0, list output is
directed to the central installation. If this parameter
is omitted or if the positional form of the * $$ LST
statement (which does not support this parameter) is
used, list output is routed to the central location if
the job was SUbmitted locally, or is routed according to
the LSTROUT specification in the PRKT macro if the job
vas submitted remotely.
FNO=
specifies the type of forms to be used according to
installation reqUirements.
The forms number is specified
by one to four alphameric characters, /, -, or period
(.). If "forms-number" is not specified, it is assumed
to be four blanks, representing the installation's
standard type of forms.
When a list writer task is to
process output from a list queue entry, it determines
whether this forms number matches that of the previous
list queue entry. If they match, the list writer task
processes the output.
If they do not, message 1Q40Ais
issued, or lQA5A for the 3800 Printer. If the first
queue entry processed after a PSTART has a forms ID of
four blanks, no mount message is issued. If the output
is directed to a 3741, this parameter must not be
specified.
A mount message is issued for FCB printers every time an
FCB is loaded. Forms alignment is then possible.
JSEP=
specifies the number of job separator pages (0 to 9). If
not specified, the value defined during POWER/VS
generation in the first entry of the JSEP parameter of
the POWER macro is assumed.
Following "sep", an optibn (either Y or N) can be
specified, where:
Y - specifies that the separator pages are also produced
between copies of the output file.
N - suppresses the generation of separator pages between
each copy of an output file.
When the option is not specified, the COPYSEP
specification defined during POWER/VS generation is
assumed.
!Q!g:
This option is available only with the 3800 ICR
and is in effect only when a nonzero specification for
JSEP is defined, either during POWER/VS generation or in
the * $$ LST (or * $$ PRT) statement.
Each separator page contains the POWER/VS job name and
number, user information from the * $$ JOB statement, and
the date and time. Separator pages that delimit the last
or only segment contain also the word "LAST".
For a nonzero specification, one more page than specified
viII be printed. This is because printing may have
occurred on the paper perforation. The page length is
determined by the LTAB specification.
88
POWER/VS Installation Guide and Reference
COpy=
specifies the number of copies of printed output from the
list queue entry. This parameter is ignored when the
output is not spooled to disk. The parameter is
specified by one or two digits. If omitted or 0 or 00 is
specified, one copy is printed. If additional copies are
required when disposition is T, the tape must be
reprinted.
!2~g:
If the COpy parameter is used together with the
the page count on the printed output will
not be in proper sequence.
RBS parameter,
COPYG=
describes (for the IBM 3800 Printer) how the printed
copies of the output file are to be grouped. Each
IIgroupvalue tl specifies the number of copies of each
individual page that is to be printed in a group before
starting to print the next page. POWER/VS retransmits
the entire output file for each group value specified.
Up to eight group values can be sp~cified. The copy
group index is used for counting of the group valUes. No
single group value can exceed 255, nor can the sum of
thos~ specified exceed 255.
This parameter has effect only when the output file is
directed to an IBM 3800 Printer. Otherwise it is
ignored. This parameter is also ignored when the output
is not spooled to disk. If the COPYG parameter is
omitted, no copy grouping occurs.
TADDR=
specifies the channel and unit address (and, optionally,
the recording density) of the tape drive to be used for
spooling to tape inter.ediate storage when the job is
being executed. This parameter may be specified in one
of the following ways:
cuu
X'cuu'
(cua, ss)
(X'cuu',ss)
(cuu,X 'ss ')
(X'cuu' ,X'ss·).
"55" can only be specified in the keyword format.
It
shows the density of the output tape. The specification
of "tapeaddr" forces a disposition of T. If DISP=T is
specified and "tapeaddr" is omitted, the operator is
requested to specify the tape address during job
execution via message lQ55D.
Two or more files can be written to a single tape.
Multivolume files are also supported.
I~:
The output of a multivolume file is split at
logical boundaries.
In case of printer output, this is a
skip to channel 1. That means that a print output that
does not contain skips to channel 1 cannot be split into
two or more volumes.
The RBS parameter is not active when spooling onto tape.
Chapter 3.
Using POWER/VS
89
RBM=
norbm1
specifies the number of lines (list records) intercepted
before message lQ52I is sent to the operator. This
parameter is specified by one to six digits.
If "norbm1"
is omitted, the value defined during POWER/VS generation
in the first entry of the STDLINE parameter of the POWER
macro is assumed.
norbm2
specifies the additional number of list records intercepted each time before message 1Q52I is reissued. It is
specified by one to six digits. If "norbm2" is omitted,
the preceding comma and the parentheses may be omitted
and the value defined during POWER/VS generation in the
second entry of the STDLINE parameter of the POWER macro
is assumed. This value is also assumed when the
positional form of the LST statement is used.
LTAB=
specifies the carriage control tape format to be used by
POWER/VS when print requests are intercepted for a nonFCB-type printer. As a default, the value of the LTAB=
parameter specified in the POWER macro is used. This
parameter, coded as 13 two-digit decimal values,
represents the positions of the first line on the page
and channels 1 through 12. Channel 1 must be the first
channel of a page. The format is:
dOdld2d3d4d5d6d7d8d9dl0dlld12
where dO is the number of lines between channel 12 of the
preceding page and channell of the new page; d1 is the
number of lines between channel 1 and the first line of
the printed page, it should always be 00. d2 is the
number of lines from channell to channel 2; and finally,
d12 is the number of lines from channell to channel 12.
If channel 1 is the same as the first line of the printed
page, dl therefore is coded as 00. Similarly, if a
channel is not represented, it must be coded 00, but
channel 1 must always be present on the control tape or
in the FCB. The sum of dO and d12 is assumed to specify
the maximum number of lines that can physically fit on a
page. If d12 is specified as 00, a default value is
taken from the co•• unication region. If a skip is
encountered to a channel that was not specified, message
OP73I is issued.
An LFCB macro issued in the problem program updates the
LTAB format.
90
1.
It is advisable to use the "forms-number" parameter
in conjunction with the "linetab" parameter. This
causes the list writer task to pause, thus allowing
the operator to mount the correct carriage control
tape on the printer.
2.
Channell on the carriage tape is used as an
indicator for a page boundary and should therefore be
specifietl.
POWER/VS Installation Guide and Reference
RBS=
specifies the number of list pages (that is, the number
of skips to channel 1) intercepted before the output is
segmented (count-driven output segmentation). It is used
only when spooling to disk intermediate storage. This
operand is ignored if DISP=T was specified. It is
specified by one to six digits and overrides the POWER/VS
generation specification of the RBS= parameter of the
POWER macro. A zero means that no segmentation will take
place.
When output segmentation occurs, the operator is notified
via message 1Q53I.
UCS=
or
PCB=
specifies the name of the phase under which an FCB (Forms
Control Buffer) or UCB (Universal Character Set Buffer)
image is cataloged in the core image library. Together
with the UCB phase name, an option may be specified which
can be either F, C, FC, or CF, where
F - signifies that the UCB is to be loaded with the
folding operation code to permit printing of
uppercase for lowercase bit configurations.
C - Prevents the data checks from being generated because
of print line mismatches with the UCB.
The specified core image library phase is loaded into the
FCB or UCB when a list writer task starts processing the
output related to the * $$ LST statement.
If ucs is coded and CHARS is not coded in the * $$ LST
(or * $$ PRT) statement and if the output file is
assigned to a 3800 printer, the UCS name is used as the
first character arrangement table name. For more
information on the CHARS parameter, see description of
the * $$ LST statement later in this chapter.
Return to a default UCB can only be made via a subsequent
$$ LST statement.
*
When an * $$ LST statement with an FeB phase name
specification is encountered by the execution processor,
the specified buffer image is read to update the internal
LTAB representation to reflect the new buffer.
Any LTAB
specification in the * $$ LST statement is therefore
ignored if FCB is also specified. The FCB specification
for a non-PCB printer is accepted, but is only used to
update the LTAB. For output directed to forms control
huffer printers, POWER/VS will ensure that the standard
FCB (depending on the printer type) is loaded if no FCB
parameter or LST statement is supplied for the job.
Return to a default FCB is made at the end of the
processing of the current LST entry.
Chapter 3.
Using POWER/VS
91
When the IB~ 3300 Printer is installed and the first four
characters of the PCB phase name are $$$$, the execution
processor changes the $$$$ depending on the device for
which the FCB is ~rocessed. The prefixes that are
inserted for $$$$ are:
FCB1
FCB2
FCB3
FCB4
for
for
for
for
a
a
a
a
3800
3211
3203
5203
Printing SUbsystem
printer
printer
printer.
This gives you device-independent processing for FCBs.
However, when using this feature, it is still your
responsibility to supply FCB images with phase names
according to the above convention.
This parameter is not supported by the positional form of
the * $$ LST statement.
When using SNA terminals or workstations for the
production of list output, you should consider the
following:
As POWER/VS does not support Select Vertical Format
(SVF), it is the responsibility of the remote operator to
set up the vertical tab tables at the remote work
station. However, the FCB name is sent if PDIR is
supported and if the name has been specified in the JECL
statements * $$ LST or * $$ PRT.
Note: When the output file is directed to an 3800
prInter, the first four characters of the FCB phase name
must be FCB1.
It is advisable to use the
conjunction with the "FCB"
list writer task to pause,
mount the correct carriage
LST=
"forms-number" parameter in
parameter. This causes the
thus allowing the operator to
control tape on the printer.
specifies either the logical or physical address of the
output printer for the list queue entry being created.
The address can be either in the form SYSxxx, where xxx
is LST or any valid program.er logical unit, or in the
form cuu (or X'cuu'), which is the channel and unit
number of an actual or a dummy printer. SYSxxx must be
assigned to the correGt printer before the * $$ LST
statement is processed. If a program produces two or
more different reports (which, in addition, may require
different forms), this parameter must be used to define
specific printers for each of the reports. If this
parameter is omitted, the default is the first printer
address specified at partition start-up. For example, if
at start-up, the following printers were specified o~
SYSLOG: PRINTERS=00E,01E,02E, then printer OOE would be
the default. In order to have the
* $$ LST statement
parameters take effect for printer OlE or 02E, LST=OlE or
LST=02E must be specified.
This parameter is not supported by the positional form of
the * $$ LST statement.
92
POWER/VS Installation Guide and Reference
CKPACT=
specifies the uame of the compaction table to be used.
This name may consist of 1 to 4 alphameric characters.
If NO is specified, no compaction will be performed for
this job.
If the CMPACT parameter is omitted, the default
compaction table specified in the PRMT macro will be
used.
BURST=
This parameter applies to 3800 printers only. BURST
specifies whether the output printed by the 3800 is to go
to the optional Burster-Trimmer-Stacker. Valid
specifications are Y or N, where:
Y - indicates that the printed output is to be burst into
separate sheets.
N - indicates that the output is to be continuously
fanfold.
When the BURST parameter is omitted, the default paper
threading request is taken (this default may have been
established using the SETDF operator command).
Also,
when DFLT=N has been specified, BURST=N is assumed as the
default.
When you direct your output to the Burster-TrimmerStacker, stacked sheets of each output file are
automatically separated from those of the preceding file.
Copies and copy groups are also separated.
The BURST parameter is syntax-checked but ignored for
printers other than the 3800.
CHARS=
This parameter applies to 3800 printers only.
CHARS
specifies the character arrangement tables to be used by
the 3800 for printing of the output file.· "table name"
specifies the 1- to 4-character name of the character
arrangement table (not including the system-assigned
prefix, XTB1, of the phase name).
Up to four table names
can be specified.
For more information on character
arrangement tables and their use, see the QOS/VS IBM 3800
f.inting Subsystem Prggrammer's Guide, GC26-3900.
*
If CHARS is coded and UCS is not coded in the
$$ LST
(or * $$ PRT) statement and if the output file is
assigned to an impact printer with the UCS feature, then
the first character arrangement table name is used as the
UCS name.
The CHARS parameter is syntax-checked but ignored for
printers other than the 3800.
Chapter 3.
Using POWERjVS
93
DFLT=
This parameter applies to 3800 printers only. It
specifies whether the IBM 3800 Printer is to be set with
the defaults that are specified by the operator in the
SETDF command.
Y - specifies that the defaults previously established
for the particular printer are to be used. The
default values are used when the corresponding
parameter is not specified. Defaults can be
established by means of the SETDF command for the
following parameters: BURST, CHARS, FCB, FLASH, FNO
(forms), and MODIFY.
N - specifies not to use the defaults established with
the SETDF command, but to use the 3800's hardware
defaults instead, when needed.
~hen
this parameter is omitted, DFLT=Y is the default.
The DFLT parameter is syntax-checked but ignored for
printers other than the 3800.
FLASlJ=
This parameter applies to 3800 printers only. It
specifies the 1- to 4-character name of th'~ forms overlay
frame to be used by the 3800 printer. Following
overlayname a flash count can be specified. It specifies
the number of copies to be flashed with the overlay,
beginning with the first copy. Any specification from 0
to 255 is valid. If the overlay name is specified
without a count or a comma after the name, or if the
count value is greater than the number of copies
specified (with the COpy or COPYG parameter), all copies
are flashed. If the name is followed by a comma but no
count is specified, a value of 0 is assumed as default
(no copies are flashed) •
If a count is specified without an overlay name, the
forms overlay frame loaded at the time of printing is
used. If a count of 0 is specified, the operator is
asked to load the requested forms overlay frame but the
overlay is not flashed.
The FLASH parameter has effect only for a 3800 printer.
~hen specified for another printer, the parameter is
syntax-checked but ignored.
If the FLASH parameter is omitted and DFLT=Y has been
specified, the default forms overlay name established for
the printer by means of the SETDF operator command is
taken. If no default forms overlay name has been
established, or if DFLT=N was specified, no flashing
occurs for the data set.
~hen a list writer task for an IBK 3800 Printer is to
process output from a list queue entry, it determines
whether the overlay name matches that of the previous
list queue entry. If they match, the list writer task
processes the output.
If they do not, message 1QA5A is
issued, requesting the operator to insert that
particular forms overlay frame into the 3800. There is,
however, no verification by POWER/VS that ~he requested
frame has been inserted.
94
POWER/VS Installation Guide and Reference
MODIFY=
This parameter applies to 3800 printers only. Predefined
data can be printed on all pages of an output file for
the 3800 printer. The data can be specified by using the
MODIFY parameter.
"copymodname" specifies the 1- to q-character name of the
copy modification phase that was assigned when it was
built (not including the system-assigned prefix HOD1) •
ntablename" is the 1- to 4-character name of the
character arrangement table to be used when printing the
copy modification text. This character arrangement table
need not be one of those specified with the CHARS
parameter, if the 3800 has enough character generation
storage. If "tablename" is not specified, the first
character arrangement table specified or defaulted with
the CHARS parameter is used for the copy modification.
The MODIFY parameter is syntax-checked but ignored for
printers other than the 3800.
*
$$ PUN Statement
*
The
$$ PUN statement defines the attributes of the intercepted punch
output of a POWER/VS job unti1 a subsequent * $$ PUN or an end-of-job
(* $$ EOJ or /&) statement is encountered. Any number of * $$ PUN
statements is permitted per POWER/VS job, except in a reader/ writer
partition, where only one statement per device and per job is permitted.
If the * $$ PUN statement is not included in the job, the default values
established during POWER/VS generation are assumed. * $$ PUN statements
do not require * $$ JOB and * $$ EOJ statements also to be used.
For each * $$ PUN statement within a POWER/VS job, a separate punch
queue entry and job number is created (data-driven output segmentation;
see the section "concepts and Functions" in Chapter 1). The first punch
entry will contain the same job number as the associated RD~ queue
entry. However, any subsequent punch entries will have a unique job
number. Repeated use of the SEGMENT macro in the same job viII have the
same effect.
Note:
Data-driven output segmentation is not supported in a writer-only
partition.
If an error is detected in the * $$ PUN statement, the central operator
may correct the statement during job execution.
Positional format:
I
I
I Operation
I Operands
I
I
, disposition
!
!I [~umber-of-coPiesJ.[
1----------------------------------------------------------------------1
1* $$ PUN
I [Q
[l]"]'( forms-number],
,
I
I
class
!I
Dorb.1]
tapeaddr
--'
Chapter 3.
Using POWER/VS
95
Keyword format:
r
I Operation
IOperands
1----------------------------------------------------------------------
1*
I
I
$$ PUN
[DISP={I!..
.
}]
d~spos~t1on
[,CLASS={~lass}]
:
I
I
I
I
I
I
I
I
I
I
I
( ,PRI=priority)
[ , REMOTE=remid ]
[ ,FNO=forms-number)
[ ,JSEP= (sep[ ,option]) ]
,
[
,COPY={l
}]
number-of-copies
[ ,TADDR=tapeaddr[,X'ss')]
I
I
[ ,RBM= (norbm 1, norbm2) ]
I
I
[ , RBS=norbs]
I
I
[,PUN=punaddr)
L
- - - - - - - - - -_________________________________________________
I __________________
Note: The operands PRI, REMOTE, JSEP, RBS and PUN can only be specified
In-the keyword form.
DISP=
specifies the disposition of the punched output after
execution of the job. The disposition specification
options are listed below. D, H, I, K, and L. are only
valid when the output is spooled to disk. When the
output is punched at a terminal, Nand T are invalid.
D - Delete after processing. The punch queue entry is
automatically written to a punch according to its
class and priority.
H - Hold. The punch queue entry remains in the punch
queue; it is not written to a punch by POWER/VS until
the operator changes the disposition to D or K by
means of the PALTER command or issues the PRELEASE
command.
I - Return output to input queue. In some situations it
may be useful to return the punch output of a
POWER/VS job directly to the input queue. For
example, the assembler normally stores its output
(including JeL) on tape. for subsequent input to a
catalog run; under POWER/VS however, it can store
output directly in the input queue.
96
POWER/VS Installation Guide and Reference
The newly-built input queue entry has the same
jobnaae, remote-ID, and priority as the entry that
produces the output. Class becomes that specified in
the * $$ PUN statement; disposition becomes D. This
facility should only be used for jobs producing punch
output in executable format.
The I option is ignored in a writer-only partition.
The option suppresses count-driven output
segmentation and also ignores the mUltiple-copies
specification.
K - Keep after processing.
The output is automatically
written to a punch according to its class and
priority.
When punching is complete, the punch queue
entry is not deleted from the punch queue, and the
disposition of the queue entry becomes L.
L - Leave in queue.
The job remains in the punch queue;
it is not written to a punch until the operator
changes the disposition to K or D by means of the
PALTER co •• and or issues the PRELEASE command.
N - No spooling.
If N is specified, punch requests are
not intercepted. It allows direct writer
capabilities without spooling.
If the N option is
specified and the device is not available at
execution time, message 1Q46I is issued and punch
output is spooled.
T - Tape spooling.
The output is spooled to tape that is
used as intermediate storage.
CLASS=
specifies the class of the punch output of the job.
It
may be specified as any alphabetic character (A through
Z)..
"class lt may be used in conjunction with nformsnumber lt to group together the same types of punch output.
Punch tasks can be specified by class to process the
output. A class specification is only meaningful when
the output is spooled to disk.
If "class" is specified and the positional form is usea,
"disposition lt must also be specified.· If "class" is
omitted, class A is assigned. If the * $$ PUN statement
is omitted, an output class can be specified in the
PSTART command.
Note: There is no comma between "disposition" and
'itCIiss ll in the positional form.
PRI=
specifies the priority (0-9) of the punch output. If
omitted, the priority of the job is taken as default.
REMOTZ=
specifies the ~o remote-ID to which punch output is to be
routed. Each punch queue entry also has a FROM remote-ID
assigned to it, which identifies the user who initially
submitted the job.
"remid" can be a number from 0 to
200. Numbers 1 to 200 are specific remote users. If
"remid" is specified as 0, punch output is directed to
the central installation. If this parameter is omitted
or if the positional form of the * $$ PUN statement is
used, punch output is routed to the central location for
locally submitted jobs or is routed according to the
PUNROUT specification in the PRMT macro for jobs
submitted remotely.
Chapter 3.
Using POWER/VS
97
FNO=
specifies, by one to four alphameric characters, /, -, or
period (.), the type of card forms to be used. If a
forms numbe~ is not specified, it is assumed to be four
blanks, representing the installation's standard type of
card forms.
When a punch writer task is to process
output from a punch queue entry, it determines whether
this forms number matches that of the previous punch
queue entry. If they match, the punch writer task
processes the output.
If they do not match, message
1Q40A is issued. If the first queue entry processed
after a PSTART has a forms ID of four blanks, no mount
message is issued. If the output is directed to a 3741,
this parameter must not be specified.
JSEP=
specifies job separation. 0-9 can be specified. If 0 is
specified, no job separation occurs. Job separation
means that before the job's punched output one card containing the POWER/VS jobname (punched so that it can be
read on the back of the card) and from two to eight cards
containing 12-11-0-8-9 punches (in all 80 columns) are
added and that behind the job's punched output two blank
cards are added. This occurs if 1, 2, or 3 is specified.
If 4 is specified, one additional 12-11-0-8-9 card is
punched; if 5 is specified, two additional 12-11-0-8-9
cards are punched, and so on.
KQ~:
Stacker selection is ignored if job separation is
requested. The default stacker for the given device is
used instead.
If the 3800 ICR is installed, an option (either Y or N)
can be specified following the "sep" parameter, where:
Y - specifies that separator cards are also included
between copies of each punch output.
N - suppresses the inclusion of separator cards between
copies of the punch output.
When the option is not specified, the COPYSEP
specification defined during POWER/VS generation is
assumed.
!Q1g: The option is only in effect when a nonzero JSEP
specification is defined, either during POWER/VS
generation or in the * $$ PUN statement.
COPY=
98
specifies the number of copies to be punched from the
punch queue entry. The parameter is specified by one or
two digits. If it is not specified, 1 is assumed. If 0
or 00 is specified, one copy is punched. This parameter
is ignored when the output is not spooled to disk. If
additional copies are required when the disposition is T,
the tape must be repunched.
POWER/VS Installation Guide and Reference
TADDR=
specifies the channel and unit address (and, optionally,
the recording density) of the tape drive to be used for
spooling when the job is executed. Its format may be
specified in one of the following ways:
cuu
X'cuu'
(cuu,ss)
(X' cuu' , S5)
(CUU,X 'SS')
(X • CU U • , X • 5 S .) •
"SSP can only be specified in keyword format.
It shows
the density of the output tape. The specification of
"tapeaddr" forces disposition T. If DISP=T is specified
and "tapeaddr" is omitted, the operator is requested via
message 1Q55D to specify the tape address at job
execution time.
Two or more files can be written to a single tape.
Multivolume files are also supported.
RBM=
norbm1
specifies the number of punch records intercepted before
message 1Q52I is sent to the operator. This parameter is
specified by one to six digits. If "norbm1" is omitted,
the value defined during POWER/VS generation in the first
entry of the STDCARD parameter of the POWER macro is
assumed.
norbm2
specifies the additional number of punch records
intercepted before message 1Q52I is issued again. It is
specified by one to six digits. If "norbm2" is omitted,
the preceding com.a as well as the parentheses may be
omitted and the value defined during POWER/VS generation
in the second entry of the STDCARD parameter of the POWER
macro is assumed. This value is also assumed if the
positional form of the * $$ PUN statement is used.
RBS=
specifies the number of punch records intercepted before
the ontput is segmented (count-driven output
segmentation). It is used only when spooling to disk
intermediate storage. This parameter, which is ignored
if DISP=T was selected, is specified by one to six digits
and overrides the POWER/VS generation specification of
the RBS parameter of the POWER macro. A zero means that
no segmentation will take place. When output
segmentation occurs, the operator is notified via message
1Q53I. For seg.entation on a 3525, and if print commands
are used, all segments must be punched in a row, or
separator cards must be specified. This is necessary to
ensure that the last two records will not be lost.
PUN=
specifies either the logical or physical address of the
output punch for the punch queue entry being created.
The address can be either in the form SYSxxx, where xxx
is PCH or any valid programmer logical unit, or in the
form cuu (or X'cuu'), which is the channel and unit
number of an actual or a dummy punch. If this parameter
is omitted, the default is the first punch address
specified at partition start-up. This parameter is
needed when two or more punches are used to punch two or
mOre card files produced by a single program.
Chapter 3.
Using POWERjVS
99
The * $$ RDR statement is used to insert a 3540 diskette file into input
being read from the card reader. There are two modes of input
processing, which are:
1.
SYSIN-mode processing; the physical unit number of the 3540 diskette
device must not be specified. The file to be read from the diskette
must contain 80- or 81-byte records. Only the last 80 bytes of an
81-byte record are passed to the reader.
The file to be read from
the diskette must contain the necessary JECL and/or Jet job stream
if the POWER/VS command PSTART RDR does not specify both card reader
and 3540 physical unit addresses.
2.
Data-mode processing; the physical unit number of the diskette from
which the input data file is read must be specified. The JECL
and/or JeL statements are read from the card reader. If two or more
RDR statements are issued in one POWERjVS job, they must specify the
same physical unit number.
!Q!g:
In a writer-only partition, this statement is ignored.
Positional format:
I
,
I Operation
IOperands
,
I----------------~-----------------------------------------------------1
1* $$ RDR
I (disket te-addr],( 'file-id' ]
S]
I
I
,.[1
1
.
] ,(
number-of-d~skettes
•
Keyword format:
r
1
I
Op~ration
*
$$ RDR
IOperands
(DEV=diskette-addr]
[ , FID=' file-id • )
[
,NOD={'
}]
number-of-diskettes
[,vse= {~~s}]
[ , VER= {~~S}]
[ , FEED= {i~s}]
Notg: The operands VER and FEED can only be specified in the keyword
form of the statement.
100
POWER/VS Installation Guide and Reference
DEV=
specifies the physical unit number (X'cuu' or cuu) used
by the user program to read the input data file.
The
physical unit must not be specified for SYSIN files~
In
one POWER/VS job, more than one RDR statement can be
specified to insert more than one 3540 data file, but the
different RDR statements must indicate the same physical
unit number in the DEV parameter.
FID=
specifies the file name (in quotes) as it appears in the
HDRl label on the 3540 diskette. One to eight alphameric
characters can be specified.
If this parameter is
omitted, POWER/VS reads the file specified by the first
non-secured HDR1 label found on the diskette that is
currently mounted. The size of the record to be read is
taken from the HDRl label.
NOD=
specifies the maximum number of diskettes to be read.
One to three digits can be specified. Allowed values are
1 to 255.
The default value is 1. Reading stops after
the specified number of diskettes are processed, or after
reading a diskette whose HDR1 label indicates that it was
the last volume of the file.
vsc=
specifies whether volume sequence checking is desired.
If omitted, no sequence checking will take place.
Sequence numbers must start with 1 and must be
incremented by 1 up to a maximum of 99.
VER=
specifies optional file verification. If VER=YES is
specified, POWER/VS checks that file verification had
been performed on the diskette file (verify field in the
HDR1 label of the file set to ·V·).
If VER=YES and the
verify field was not set to IV', the file is rejected
during file OPEN. If VER=NO or if the parameter is
omitted, the verify field in the HDR1 label is ignored
during processing.
FEED=
specifies the option to eject and feed a new diskette at
end-of-file of the preceding diskette.
This parameter
can be used in combination with the FEED parameter of the
POWER macro instruction.
During the POWER/VS generation,
you have established the system default value for the
FEED option (YES or NO); this system default can be
overridden by the FEED parameter of the * $$ RDR JECL
statement. Any time a * $$ RDR statement is going to be
processed, the FEED parameter is reset to the system
default as specified in the POWER macro instruction.
*
During program execution. the
$$ SLI statement causes the private and
the system source statement library to be searched for a book, which,
when found, is inserted into the job stream. The private source
statement library. if assigned to the POWER/VS partition, is searched
first.
An * $$ SLI statement does not require that
statements also be used.
*
$$ JOB and
Chapter 3.
*
$$ EOJ
Using POWER/VS
101
Statements may be added to or deleted from the source statement library
books. Such update statements may be inserted before or after SSL
statements or may replace or delete them. They have special codes in
columns 73-80:
columns 73-76
columns 78-80
column 17
contain '$SLI'
contain a sequence number
contains a special code:
A
Insert after book statement with the same
number or before the one with the next higher
sequence number.
B
Insert before book statement with equal or
higher sequence number.
D
Delete the book statement with the same
sequence number.
Other
Replace the book statement with same sequence
number or insert this statement.
Source statement library up~ate statements and * $$ DATA statements,
when used, must follow the * $$ SLI statement in the same sequence as
the statements in the book they correspond to.
Books are cataloged into the source statement library with the DOS/VS
program MAINT. ~o include /* and /& statements in a book, submit them
as * $$/* and * $$/& statements since /* and /& statements are not
accepted as data by KAINT. To include LST and PUN statements, submit
them as * $x LST or * $x PUN, where x can be any character other than
blank or $. If the book is not found in the specified sublibrary,
message 1Q44I is issued and the job is flushed.
,
,
,Operation
IOperands
I
1----------------------------------------------------------------------1
1* $$ SLI
I[sublib.]bookname
I
I
!Q12:
This statement is only available in the positional format.
sublib.
specifies the name of the sublibrary to be searched.
Valid suhlibrary names are A through Z, 0 through 9, $,
#, or ~, followed by a period (.).
Sublibraries A, C, 0,
E, F, and Z are already defined as special-purpose
libraries in DOS/VS. This parameter is optional. If
omitted, the sublibrary specification at POWER/VS
generation is used.
book name
specifies the book name to be searched for and inserted
into the job stream. If "bookname" begins with $$, it
will be changed depending upon the partition in which the
SLI book is being processed. $$ becomes $B in BG or $n
in the foreground partition Pn.
102
POWER/VS Installation Guide and Reference
The following examples illustrate the use of the
statements:
1.
$$ StI and
*
$S DATA
Job to insert data from the card reader into the book "A55M".
~e
*
*
*
1*
*
$$ JOB
$$ 5LI
$$ DATA
INSERT
ASS!
INPUTA
POWER ACCOONT=YES
END
POWER ACCOUNT=YES
END
1*
/&
"ASSK~
book
BKEND ASSM
II JOB INSERT
II EXEC ASSEMBLY
*
*
$$ DATA INPUT!
$$1&
BKEND
$$ EOJ
II JOB INSERT
II EXEC ASSEMBLY
2.
*
(From
(From
(From
(From
(From
(From
book
book
card
card
card
book
"ASSMIt)
"ASSM")
reader)
reader)
reader)
ItAS5M It)
Assume that a private source statement library is assigned to the
POWER/V5 partition. A job (read in from the card reader) references
the book "XMPL" in that library (sublibrary B) and contains SL
update statements as well as DATA statements. The book statements
replace the 5LI statement. However, statements XMPL0020, XMPL0100,
and XMPL0120 are overridden by the corresponding SL update
statements in the input stream. In addition, statement $StIll00 is
inserted.
Also, the cards between the DATA statement and the first
1* statement in the input job stream replace the DATA statement in
XMPL. The resulting job stream is placed in the read queue.
Chapter 3.
Using POWER/VS
103
col. 73-80
*
$$ JOB
ASSEMSLI
B.XMPL
* $$ 5L1
I I ASSGN
SYSPCH,X'182'
* $$ DATA INPUTA
DEFAULT POWER ACCOUNT=YES
$5L10020
END
1*
I I A5SGN
I I A5SGN
I I MTC
*
5YS1PT,X'132'
SYS010,X'183'
RON, X • 182'
$5LI0100
$5L1A100
$5LI0120
$$ EOJ
Col. 73-80
BKEND
B.XMPL
ASSEMBLE
II JOB
SY5PCH,X'180'
II ASSGN
ASSEMBLY
II EXEC
* $$ DATA INPUTA
WTM,5YSPCH
II MTC
WTK,SYSPCH
II MTe
REW,SYSPCH
II MTC
* $$/&
CATALOG
II JOB
SYSIPT,X'180'
II ASSGN
MAINT
II EXEC
RUN,X'180'
/ / MTC
* $$/*
* $$/&
LINK
II JOB
1/ OPTION CATAL
INCLUDE DEFAULT
*
*
II
$$1*
EXEC
$$/&
LNKEDT
XKPLOO10
XKPLOO20
XMPLOO30
XKPLOO40
XliPLOO5Q
XMPLOO60
XMPLOO70
XMPL0080
XMPLOO90
XMPL0100
XKPL0110
XMPL0120
XMPL0130
Xl'1PL0140
XI1PL0150
Xl1PL0160
XI.'tPL0180
XMPL0200
XMPL0210
XMPL0220
BKEND
104
POWER/VS Installation Guide and Reference
R~ultinSLjQb
stream Elaced in
rea~~
Col. 73-80
*
ASSEMSLI
$$ JOB
ASSEMBLE
/ / JOB
5YSPC3,X'182 1
/ / ASSGN
ASSEMBLY
/ / EXEC
DEFAULT POWER ACCOUNT=YES
END
XMPL0010
$5LI0020
XftPLOO30
/*
WTM,SYSPCH
// MTC
WTM,SYSPCH
// MTC
REW,SYSPCH
// MTC
/&
CATALOG
// JOB
5YSIPT,X' 182 I
/ / A5SGN
SYS010,X'183'
/ / ASSGN
MAINT
// EXEC
RUN,X'182'
/ / MTC
/*
/&
LINK
/ / JOB
/ / OPTION CATAL
INCLUDE DEFAULT
/*
LNKEDT
/ / EXEC
/&
* $$ EOJ
IMPLOO50
XMPLOO60
XMPLOO70
XMPL0080
XHPLOO90
$5LI0100
$5L1A100
XMPL0110
$5LI0120
XMPL0130
IKPL0140
XMPL0150
XMPL0160
XMPL0180
XliPL0200
XMPL0210
XMPL0220
updated
inserted
inserted
inserted
modified
updated
inserted
updated
modified
modified
modified
modified
-The end-of-jobstep and end-of-job statements are used to delimit DOS/VS
job definitions within the source statement library books (see the
* $$ 5L1 statement above) •
The end-of-jobstep statement delimits DOS/VS job definitions within the
source statement library books.
I
IOperation
1
I
IOperands
1----------------------------------------------------------------------1
1* $$ /*
I
I
,
I
This statement has no operands.
The end-of-job statement deli.its DOS/VS jobs within the source
statement library books.
i
IOperation
,
I
IOperands
1----------------------------------------------------------------------1
I
I
1* $$ /&
,
I
This statement has no operands.
Notes:
':--LST and PUN statements within the 5L1 books may not be continued
from one record to the next.
Chapter 3.
Using POWER/VS
105
2.
~he
following rules and restrictions must be considered:
•
Nested 5L1 statements are not permitted.
•
An SL1 book may invoke a DOS/VS procedure.
•
A
•
Each SL1 book represents a POWER/VS procedure and may not include
embedded * $$ JOB statements. However, one POWER/VS job may
include two or more SL! statements.
DOS/VS procedure may not invoke an SL1 book.
• *
$$ LST and * $$ PUN statements may not be continued in an 5L1
book. However, there is no restriction on the use of / / JOB,
* $$ /*, and * $$ /& statements.
•
3.
SYSRDR, SYSIPT, and SYSIN cannot be reassigned within an 5L1
book.
~he
private source statement library containing the SLI books must
be assigned to the POWER/VS ~artition before POWER/VS is started.
Cross-Partition Communication Macros
This section describes the macros that allow access to POWER/VS
functions from a partition not controlled by POWER/VS. These macros can
be used only if SPOOL=YES was specified in the POWER macro during
POWER/VS generation, and if XECB support was specified during D05/VS
generation.
POWER/VS answers spooling requests originating from the SVA; however,
the DTFs (or CCBs), CCWs, and data areas must reside in a partition and
not in the SVA.
To connect to POWER/VS, use the XECBTAB macro with the following
operands:
XECBTAB TYPE=DEF1NE,
XECB={SPKXECB},
ICRXEC8
ACCESS=XWA1T
SP~XECB is required for the GETSPOOL and CTLSPOOL macros; 1CRXECB is
required for the PUTSPOOL macro. The 3-byte address of the 5PL must be
placed in SPMXECB+5 and/or 1CRXECB+5 by the user program.
Not~:
For each program using the GETSPOOL, PUTSPOOL, ana CTLSPOOL
macros, the specification of the SPL TYPE=MAP macro is required~
If the partition using the cross-partition support has a higher priority
than POWER/VS, a system error may be issued if an abnormal end or shut
down occurs before all cross-partition active tasks have completed.
If·the cross-partition user issues JECL statements to POWER/VS through
the support macros, the format is not variable. Only one blank must
appear between the "*" and "$$" and the first parameter~
only one partition may actively use the cross-partition support at a
time~
106
POWER/VS Installation Guide and Reference
MACRO DESCRIPTIONS
The SPL (Spool Parameter List) macro creates a
PUTSPOOL, GET5POOL, and CTLSPOOL macros.
para~eter
list for the
I
Name
IOperation
IOperands
ICol1
I
I
172 I
I
I
I[ ,JOBN=jobname J
----------------------------------------------------------------------1
I TYPE=DEFINE
(name 115PL
(* ]I
,
I
I
[ * )I
I
I
I[ ,DISP=disposition]
[* ]I
I
I
I[ ,CLASS=class )
I
I
I
I
I
PRI
DISP
CLASS
REPfOTE
I[ ,REQ= CANCEL
I
I
I
I
[* ]I
]
[*)
SCRATCH
STATUS
COMMAND
(*J
I[ ,CBUF=firstbufaddr)
I
I[ ,PBUF=bufaddr]
[*]
I
1[,PBUFL=huflength]
[* ]
I
I( ,NEWVAL=value )
or
,
H name] ISPL
I
I TYPE=MAP
I
1[*]1
I
I
I[ *] I
1[,SPMIECB={YE5}]
r
I
I
I
I[ IC~XECB={YES}]
I
I
L -_ _ _ _ _ _ _ _ _ _,_ _ _ _ _ _ _ _I_ _ _ _ _ _ _ _ _ _ _ _!Q
______________________________________
I - - - JI
I
I
TYPE=
!Q
causes, with the specification DEFINE, a ~arameter list
to be initially set up with the keywords and values to be
used in the POTSPOOL, GETSPOOL, and CTL5POOL macros.
These values can later be changed by specifying the
corresponding keywords in the macros themselves.
with the specification MAP, this operand causes a DS~CT
of the SPt to be generated. TYPE=MAP must be specified
once in every program using GETSPOOL, POTSPOOL, CTLSPOOL.
If TYPE=MAP is specified, only the parameters SPMIECB=
and ICRIECB= (see below) may be coded.
Chapter 3.
using POWER/VS
107
JOBN=
specifies a unique job name to be assigned to the
POWER/VS input queue.
If omitted, the default name is
DUMMY.
DISP=
specifies the output disposition code for the submitted
job as it will appear on the POWER/VS output queue. If
omitted, the default is K.
CLASS=
specifies the POWERjVS output class (A-Z) for the
submitted job as it will appear on the POWER/VS output
queue. If omitted, the default is \.
REQ=
specifies the requested operation for a CTLSPOOL macro.
PRI alters the priority of the named job on the output
gueue (see note below).
DISP alters the disposition of the named job on the
output queue (see note below) •
CLASS alters the job class of the job on the output queue
(see note below) •
REMOTE alters the\remote terminal identification to which
list output of the job is to be routed (see note below) •
CANCEL causes the job to be cancelled from the input
gueue if it has not yet executed.
SCRATCH causes the named job to be deleted from the
POWER/VS output queue.
STATUS causes the disposition of the named job on the
input or output queue to be returned in the SPQD field of
the SPL, and the queue indicator in the SPsQ field.
COMMAND indicates that you have supplied a valid POWER/VS
command in the PBUF area.
!Q!~:
If PRI, DISP, CLASS or REMOTE are used, the
NEWVAL= operand must also be specified.
CBUF=
specifies the address of the first buffer containing the
job stream. The format of each 88-byte buffer area is as
follows:
a fOUr-byte pointer to the next buffer in the
chain (or a for the last buffer), four bytes reserved,
and an aO-byte data buffer area.
PBUF=
specifies the address of a buffer area which is for use
by POWER/VS and for POWER/VS feedback information on
certain error conditions. The length of this buffer area
must be at least as bytes.
PBOFL=
indicates the length of PBUF. It must be set to the
maximum length of the output data records, with trailing
blanks truncated. The minimum allowed is 88 bytes.
If
omitted, the default is 88 bytes.
NEWVAL=
indicates the new value that is to be assigned to the
PRI, DISP, CLASS, or REMOTE attribute of the job named in
a CTLSPOOL request. The meaning of the one-byte value
depends on the REO operand.
108
POWER/VS Installation Guide and Reference
SPMXECB=
and
reRIECB=
specify that a DSECT for each of these XECBs is to be
generated. The format of the DSECTs is as follows:
DSECT
SPMXECBU DS
SPMERROR DS
SPMSPLP DS
DSECT
ICRXECBU DS
ICRERROR DS
ICRSPLP DS
XECB
F
X
AL3
XECB
F
X
AL3
POR GETSPOOL AND CTLSPOOL
XECB
ERROR RETURN CODE
SPL pointer
FOR PUTSPOOL
XECB
ERROR RETUR'l CODE
SPL POINTER
The POTSPOOL macro is used to submit a job stream from the user1s buffer
area to the POWER/VS input queue for later execution in a partition
under control of POWER/VS.
only the statements of the initial PUTSPOOL job stream are analyzed for
the existence of any POWER/VS JECL statements, in particular * $$ JOB,
LST, or PRT statements. If no JECL statements are detected at the
beginning of the initial PUTSPOOL job stream, * $$ JOB and LST/pRT
statements are built in accordance with the given SPL parameters. If
any JECL statements are encountered at the beginning of the initial
PUTSPOOL job stream, they are first placed in the input queue, and then
any missing * $$ JOB and/or LST/pRT statements are constructed.
*
$$ RDR statements cannot be submitted using the PUTSPOOL macro.
No~:
When register notation is allowed for parameters of this macro
(indicated by "(reg)" as a possible parameter value), any general
register except registers 0, 1, 14, and 15 may be specified.
The register contains the parameter value, except for JOBN, whose
register must point to an eight-byte field with the jobname rightadjusted.
I
IName
IOperation
IOperands
I
I
I
1-----------------------------------------------------------------t[name] PUTSPOOL
SPL=(reg)
ICol
72
[ *)
[,JOBN={jObname}]
(reg)
(* )
[,PBUF={bUfaddr}J
(reg)
[* J
[ ,CONT= (reg) ]
( *]
[ ,DISP={diSPosition}]
(reg)
[* ]I
[ ,CLASS= {Class}]
l(reg)
[* ]I
I
I
I
I
I
I
I
I
I
I
I
I
[ ,CBUF={firstbufaddr}J
(reg)
•
L
Chapter 3.
Using POWER/VS
109
name
specifies the macro label.
parameter is specified.
SPL=
specifies the address of the spool parameter list (SPL)
to be used by the PUTSPOOL macro. The SPL defines the
POWER/VS request for the job stream indicated by the JOBN
operand.
JOBN=
specifies a unique job name to be assigned to the
POWER/VS input queue. The same name must be used for the
output queue when it is referenced by the GETSPOOL or
CTLSPOOL macros.
PBU?=
specifies the address of a buffer area which is for use
by POWER/VS and for POWER/VS feedback information on
certain error conditions. The length of this buffer area
must be at least 88 bytes.
CONT=
If the buffers processed by this execution of PUTSPOOL do
not contain the complete job stream, this operand should
be used to give the address of a continuation routine.
In this routine, you can submit further data buffers
associated with the same job stream. However, no other
parameters may be changed in the continuation routine.
Return to POWE~/VS is via register 14. When this
parameter is used, CBUF= must also be specified and the
macro aust have a label.
DISP=
specifies the output disposition code for the submitted
job as it will appear on the POWER/VS output queue (LST
or PUN). The disposition must be a valid POWER/VS
disposition. If you supply a * $$ LST or * $$ PRT
statement, it must contain the same disposition code.
CLASS=
specifies the POWER/VS output class (A-Z) for the
submitted job as it will appear on the POWER/VS output
queue (LST or PUN). specify a unique class if you want
to have controlled access to the file($) by means of
GETSPOOL. If you supply a * $$ LST or * $$ PRT
statement, it must contain the same output class.
CBUP=
specifies the address of the first buffer containing the
job stream. The format of each S8-byte buffer area is as
follows: a four-byte pointer to the next buffer in the
chain (or 0 for the last buffer), four bytes reserved,
and an SO-byte data buffer area. If the CONT operand is
specified together with CBUF, the same buffers must be
reused for the continuation data. If register notation
is used, the continuation routine must reset the contents
of the previously used register if different buffers are
used.
110
Required if the CONT
POWER/VS Installation Guide and Reference
The GETSPOOL .acro is used to request retrieval of list output currently
held in POWER/VS output queues on disk.
The output is to be returned to
the buffer area of the partition issuing the GETSPOOL macro. Retrieval
may be sequential or direct.
GETSPOOL can request list output only if the disposition of the queue
entry is D or K. However, as for a list task, th~ disposition of the
queue entry is changed to L after processing. Therefore, before a
sUbsequent GETSPOOL request can be issued, the disposition of the entry
has to be changed back to D or K, using the CTLSPOOL macro.
Note:
When register notation is allowed for parameters of this macro
(indicated by " (reg)- as a possible parameter value), any general
register except registers 0, 1, 14, and 15 may be specified.
The register contains the paraaeter value, except for JOBN, whose
register must point to an eight-byte field with the jobname rightadjusted.
r
I
tName
I Operation
IOperands
ICol1
I
r
I
172
1-----------------------------------------------------------------I[na.e] GETSPOOL
I SPL= (reg)
,
[*)
[*]
1[,JOBN={jObname}]
I
(reg)
I
[*]
I( ,CLAss={class}J
I
I
I
---r
(reg)
I[ ,PBUF={bUfaddr}]
(reg)
[*]
1(,PBUFL={bUflength}]
I
(reg)
[ *]
,
I
I
I [ ,CC={YES}J
I
NO
I
( *]
I
I
I
I
![rLINENo={nU&ber})
!
(reg)
~____________________________________________________________________________J
Programming Notes:
SPL=
specifies the address of the spool parameter list (SPL)
to be used by the GETSPOOL macro. The SPL defines the
POWER/VS request for the job stream indicated by the
JOBN= operand.
If the LINENO= operand was used in a
previous direct GETSPOOL request, the same SPL must be
specified in the present request, or line positioning
will be lost.
JOBN=
specifies the POWER/VS job name for the job stream as
assigned by PUTSPOOL. If the LINENO= operand was used in
a previous direct GETSPOOL request, the same job name
must be specified in the present request, or line
positioning will be lost.
CLASS=
specifies the POWER/VS output class (A-Z) as assigned by
PUTSPOOL.
Chapter 3.
Using POWER/VS
111
PBUF=
specifies the address of a buffer area which is to
receive the retrieved output record and/or POWER/VS
feedback information on certain error conditions. If
this operand is used, PBUFL= must also be specified.
PBOPL=
indicates the length of PBUF. It must be set to the
maximum length of the output data records, with trailing
blanks truncated. The length of the output data record,
with trailing blanks truncated, is returned in the 4-byte
SPRL field of the SPL. The minimum allowed is 88 bytes.
cc=
If CC=YES is specified, the command code of the CCW
associated with this data record is returned in the SPCC
field of the SPL. If the record is a control record, the
buffer contains blanks; if it is a data record, the SPCC
field is always updated.
LINE!tO=
If this is the first GETSPOOL request, sequential
retrieval of the output records begins at the line
specified (relative to the beginning of the output file) ,
or, if LINEBO= has been omitted, from the beginning of
the file. Since any subsequent GETSPOOL request would
reposition to the line number specified, the LINENO=
operand should be omitted for subsequent sequential
retrieval.
The CTLSPOOL macro is used to
POWER/~S
•
Alter the attributes of a
job
•
Cancel a submitted job prior to its execution
•
Delete the list output of a job after its execution
•
Display the status of a job
•
Issue a valid user-supplied POWER/VS command.
NQ!g:
When register notation is allowed for parameters of this macro
(indicated by "(reg)" as a possible parameter value), any general
register except registers 0, 1, 14, and 15 may be specified.
The register contains the parameter value, except for JOBN, whose
register must ooint to an eight-byte field with the jobname rightadjusted.
112
POWER/VS Installation Guide and Reference
i
I
IName
I Operation
I Operands
ICol1
I
I
I
172 ,
1------ ----------I(nalle] CTLSPOOL
SPL= (reg)
[ *]
[,JOBN={jObname}l
(reg)
[*]
[ ,PBUP={bUfaddr}l
(reg)
[*]
PRI
DISP
CLASS
REl10TE
[,REQ- CANCEL
]
SCRATCH
STATUS
COMMAND
(reg)
I
[*]
( ,NEWVAL={VaIUe}]
(reg)
SPL=
specifies the address of the spool parameter list (SPL)
to be used by the CTLSPOOL macro. The SPL defines the
POWER/VS request for the job stream indicated by the
JOBN= operand.
JOBN=
specifies the POWER/VS job name for the job stream as
assigned by PUTSPOOL.
PBUF=
specifies the address of a buffer area which is for use
by POWER/VS and for POWER/VS feedback information. The
length of this buffer area must be 88 bytes.
REQ=
specifies the requested operation as follows:
PRI alters the priority of the named job on the output
queue (see note below).
DISP alters the disposition of the named job on the
output queue (see note below) •
CLASS alters the job class of the job on the output queue
(see note below).
REMOTE alters the remote terminal identification to which
list output of the job is to be routed jsee note below} •
CANCEL causes the job to be cancelled from the input
queue if it has not yet executed.
SCRATCH causes the named job to be deleted from the
POWER/VS output queue.
STATUS causes the disposition of the named job on the
input or output queue to be returned in the SPQD field of
the SPL, and the queue indicator in the SPSQ field.
COMMAND indicates that you have supplied a valid POWER/VS
com.and in the PBUP area.
(reg) indicates that the request code is provided in a
general register. You may specify one of the following
codes in this register:
Chapter 3.
Using POWER/VS
113
X'01'
X' 02'
X' 04'
X' OS'
X' 10'
X • 20 •
X' 40 I
X'SO'
(P~I)
(DISP)
(CLASS}
(REMOTE)
(CANCEL)
(SCRA'l'CH)
(STATOS)
(COMMAND)
-
Alter routing priority (PALTER)
Alter ronting disposition (PALTER)
Alter ronting class (PALTER)
Alter routing remote-IO (PALTER)
Cancel input (POELETE RDR)
Scratch output (PDELETE LST)
Display status of job (PDISPLAY)
Issue POWER/VS command.
HQte:
If PRI, DISP, CLASS, or REMOTE are used, the
NEWVAL= operand must also be specified.
NEWVAL=
indicates the new value that is to be assigned to the
PRI, DISP, CLASS, or REMOTE attribute of the named job.
The meaning of the one-byte value depends on the REO
operand and can be as follows:
•
•
•
•
For
Por
Por
For
PRI, the new priority of the job
DISP, the new disposition of the job
CLASS, the new class of the job
REMOTE, the new terminal identifier.
The value specified can be either a character (for
example, NEWVAL='A') or a number (for example,
NEWVAL=16). If register notation is used, all values
must be hexadecimal.
Not~:
When using the CTLSPOOL macro, you may specify one of the
following POWER/VS operator commands:
•
PALTER (A) command
•
PCANCEL (e) command
•
PDELETE (L) command
•
PDISPLAY (D) command
•
PRELEASE
(~)
command.
Any of these commands must be submitted in the SS-byte buffer addressed
by the PBUF= parameter and invoked by the request type REQ=COMMAND.
The remaining operator commands are not available in the cross-partition
communication environment.
RETURN CODES FROM POTSPOOL, GETSPOOL, AND CTLSPOOL
Figure 3-5 shows the return codes that are supplied following the
execution of a PUTSPOOL, GETSPOOL, or CTLSPOOL macro. These return
codes are displayed in the SPER field of the SPL and in the error field
of the DSECT generated by the TYPE=MAP operand of the SPL (at SPKXECB+4
or ICRXECB+4), except for return codes X'41 1 and X'SSI, which are
indicated in XECB+4 only.
XWAIT and XPOST return codes in register 15 are to be diagnosed by the
user (see macro expansions: XPOST errors are doubled to maintain
uniqueness). The XWAIT and XPOST macros and the corresponding return
codes are described in the section "Cross-Partition Event Control
Macros" in the publication ~Q§L!~_~YE~~!i2Q~gnd_!L2-~~££Q§. GC33-5373.
114
POWEP/VS Installation Guide and Reference
i
IReturnlMeaning
Code
I
IDisplayed at
IXECB+4 ISPER
x
x
x
x
x
x
x
x
Invalid job name in SPL.
x
x
The PBUF buffer area is smaller than 88 bytes
or not large enough to hold the largest output
data record (PBUFL in GETSPOOL too small) •
x
x
X'22'
GETS POOL was unable to locate output file by
specified job name, job class, and dispatchable POWER/VS disposition, or requested output
file is in use.
I
x
X'24'
A loop occurred in the PUTSPOOL buffer chain,
or more than 4096 buffers were used per
request.
x
x
X'28'
Invalid CTLSPOOL REQ operand.
x
x
X
X
X
X
X
X
(see
X
X
IA POWER/VS error occurred during PUTSPOOL (see
Inotes below).
X
X
IInvalid data buffer chain (PUTSPOOL).
X
X
IX'84'
IInvalid POWER/VS buffer address (PBUF).
X
X
I
I
X'08'
End of data encountered during a GETSPOOL
request, or invalid LINENO specified in
GETSPOOL.
X'11'
Command not
X' 12'
Invalid
X '14
Invalid output class (not A-Z)
I
IX'18'
I
IX'21'
I
I
I
X'41'
allowe~.
POWE~/VS
output disposition in SPL.
POWER/VS terminated normally, or
IPOWER/VS terminated abnormally, or
IPOWER/VS spool management task terminated
labnormally.
I
r
I
I
I (see notes below).
I
IX 1 42'
',X'44
1
IA POWER/VS error occurred during CTLSPOOL
IA POWER/VS error occurred during GETSPOOL
Inotes below) •
I
I
I
I
I
I
1
,
IX'48'
IX'82'
IX'88'
in SPL.
IInvalid SPL address.
X
I
1---------------------------------------------------------------------INotes:
11.
I
12.
1
1
I
I
13.
I
I
The first 44 characters of the POWER/VS message text are displayed
in PBUF, starting at offset 28 of PBOF.
No spool management error detection is done for a CTLSPOOL request
with REQ=COMMAND specified. You must analyze the message returned
by POWER/VS in the PBUF area.
If the command in the CTLSPOOL
request results in more than one message, only the first message
is returned.
All values specified in the NEWVAL operand of the CTLSPOOL macro
must conform with the current POWER/VS values for priority, disposition, and related parameters.
---J
L
Figure 3-5.
PUTSPOOL, GETSPOOL, and CTLSPOOL Return Codes
Chapter 3.
Using POWER/VS
115
Job Accounting
A single source program ma.cro is provided for use i·n conjunction with
POWER/VS: the PUTACCT macro. This macro relates to job accounting.
When using POWER/VS, the job accounting interface information and
job accounting information is collected in the POWER/VS account
file.
The account file consists of five types of records:
POWE~/VS
•
Reader account records
•
List account records
•
Punch account records
•
Execution account records
•
BSC line and SNA session account records.
The layouts of the account records are shown in Figures 3-6 to 3-11. On
the account file, and after saving from the account file onto tape or
disk, the records are included as physical sequential records. When
saved on punched cards, account data for the reader, list, punch, and
execution account records will appear in columns 2-72, and for the ~JE
account records in columns 2-57.
Column 1 of every card contains a copy o~ the record identifier (byte
42) of the record, columns 13-78 contain the sequential account record
number and columns 79-80 contain the sequence number within that record.
READER ACCOUNT RECORD
A reader account record is created for each read queue entry that is
entered into the POWER/VS system. Whether or not the queue entry bas
actually been placed in the queue file is indicated by the POWER/VS
cancel code. The record is copied from the first 58 bytes of the
corresponding queue record.
116
POWER/VS Installation Guide and Reference
r---------------------------------------------------------------------------,
Bytes IDescription
IPormat I
l
00-07 IDate in forma~ specified at SYSGEN (mm/dd/yy or
Idd/mm/yy) •
I
a
Start time of read, in packed decimal (ORBMMSSF;
F = sign) •
p
12-15
Stop time of read (OHHMMSSFi P
p
16-31
16 bytes of user inforaation.
a
32-39
POWER/VS job name.
a
40-41
Job number assigned by POWER/VS.
b
42
Record identifier.
a
08-11
sign) •
43
IPOWER/VS cancel code.
I
44
IReserved.
I
45-47 IReader device address, or SNA.
I
48
IFROM remote ID.
I
49
ITO remote ID.
I
50
IInput class.
I
51
IInput priority number.
I
52-55 INumber of records read (including record added or
Ideleted by an RDR exit routine) •
I
56-57 INumber of tracks for input storage.
1
a:
b:
p:
b
b
a
b
b
a
a
b
b
for alphameric
for binary
for packed decimal.
Note: The TO remote ID is a dummy entry in the Reader Account Record
land in the Execution Account Record. It is copied from a PROM
Iremote ID.
Figure 3-6.
Reader Account Record
LIST ACCOUNT RECORD
A list account record is created for each list queue entry that is
processed by a list task. It is a copy of the first 72 bytes of the
corresponding queue record.
Chapter 3.
Using POWER/VS
117
Bytes IDescription
I Forllat 3
00-07 IDate in format specified at SYSGEN (mm/dd/yy or
Idd/mm/yy) •
a
I
08-11 ,start time of list, in packed decimal (OHHKMSSF;
IF = sign) •
,
,
12-15 IStop time of list (OHHMMSSF; F = sign) •
16-31 116 bytes of user information from
*
$$ JOB card.
I
32-39 IPOWER/VS job name.
r
I
40-41 IJob number assigned by POWER/VS.
I
42
'Record identifier.
I
43
IPOWER/VS cancel code.
I
44
IReserved.
I
,
,
p
p
a
a
b
a
b
b
45-47 IPrinter device address, or SNA.
a
48
IFROM remote ID.
b
ITO remote 10.
b
49
I
IPrinted output class.
50
I
IPrinted output priority number.
51
I
a
a
Number of lines printed.
b
56-57
Number of tracks for output storage.!
b
58
Job suffix number assigned by POWER/VS ....
b
59
Number of printed copies. z
b
60-63
Print forms identification.
a
64-67
Number of extra records printed due to PRESTART,
PSETUP, separator lines, or extra copies.
b
68-69
Number of pages printed (skips to channel 1).
b
52-55
70-71 INumber of extra pages printed due to PRESTART, PSETUP,
Iseparator cards, or extra copies.
b
Only for spooling to disk. When spooling to tape, field is zero.
If more than one copy is provided, the statistics are totals for all
copies.
3 a:
alphameric
b:
binary
p:
packed decimal •
... will be X'FP' for last or only segment of job.
1
2
Figure 3-7.
118
List Account Record
POWER/VS Installation Guide and Reference
PUNCH ACCOUNT RECORD
A punch account record is created for each punch queue entry that is
processed by a punch task. It is a copy of the first 68 bytes of the
corresponding queue record.
i
IPorllat 3 1
Bytes IDescription
a
00-07 IDate in format specified at SYSGEN (mm/dd/yy or
dd/mm/yy) •
p
08-11
Start time of punch, in packed decimal (ORHMKSSF;
F = sign) •
12-15
Stop time of punch,
16-31
16 bytes of user information from
32-39
POWER/VS job name from
40-41
Job number assigned by POWERjVS.
b
42
Record identifier.
a
43
POWER/VS cancel code.
b
44
Reserved.
b
45-47
Punch device address, or SNA.
a
48
FROM remote ID.
b
49
TO remote 10.
50
Punched output class.
51
(OHHK8SSF; F = sign) •
*
*
a
$$ JOB card.
a
$$ JOB card.
a
IPunched output priority number.
a
I
52-55 INumber of records punched.
b
I
156-57 INumber of tracks for output storage. 1
I
I
I
1
I
1
I
1
158
159
b
IJob suffix number assigned by POWER/VS..
b
INumber of punched copies. 2
b
160-63 IPunch forms identification.
a
164-67 INumber of additional cards punched due to restart,
I
Iseparator cards, or extra copies.
1
a
1---------------------------------------------------------------------,I
Only for spooling to disk. When spooling to tape, field is zero.
12 If more than one copy is provided, the statistics are totals for all
1 copies.
13 a: alphameric
I
I
b:
binary
p: packed decimal.
,. Will be X'FF' for last or only segment of job.
,
Figure 3-8.
Punch Account Record
Chapter 3.
Using POWER/VS
119
EXECUTION ACCOUNT RECORD
An execution account record is created for each queue set (user job
step) that has been processed by POWER/VS.
,
,Bytes
,Label
IDescription
IFormat 2
I
(mm/dd/yy or dd/mm/yy).
Start time of job (OHH~MSSF; F = sign) •
Stop time of job (OHHMKSSF; F = sign) •
16 bytes of user information.
Current powER/VS job name.
Job number assigned by POWER/VS.
Record identifier.
POWER/VS cancel code.
Reserved.
Reserved.
FROftl remote ID.
TO remote ID.
Class.
Priority.
Number of lines spooled.
INumber of cards spooled.
INumber of pages spooled.
ILength of SIO table.
ILength of total account record.
IReserved.
IDOS/VS job name from / / JOB card.
116 hytes user information from / / JOB card.
IPartition ID in EBCDIC format.
IDOS/VS cancel code.
Type of record; S =job step, L =last step.
Reserved.
Phase name, taken from / / EXEC card.
End addr. of active program phase, COaREG.
CPU time elapsed in a job step: counted in
300ths of a second.
Overhead time; elapsed time not charged to
any partition, in 300ths of a second.
All-bound time; system wait state time
divided between running partitions, in
300ths of a second.
SIO tables: 6 bytes for each device specified by SYSGEN options, as follows:
two bytes for device address (Oeuu),
1
four bytes for count of sros in current jobl
step.l
I
Overflow byte: normally X'20-, but X'30' if I
more devices are used within a partition
I
than specified by SYSGEN options.
I
User account information (provided via userl
IPOTACCT macro) •
I
1-------------------------------------------------------------------Date in format specified at SYSGEN
00-07
a
IAEDY
08-11
12-15
16-31
32-39
40-41
42
43
44
IAEST
IAEET
IAEUI
IAENM
IAENO
IAERI
I AECN
c
45-47
48
49
50
51
52-55
56-59
60-61
62-63
64-65
66-71
72-79
80-95
96-97
98
99
100-103
104-111
112-115
116-119
120-123
fAERJ
IAECU
IAEFJ
IAETJ
1AECL
IAEPY
1111
1,
124-127
128-
t
I
I
11
1
11
1
1128+m(3)
I
I
I
I
I
I
t
I
I
t128+m+1(~}
I
p
p
a
a
b
a
b
b
b
b
b
a
b
b
b
b
b
b
a
a
a
b
a
a
b
b
b
b
b
b
1---------------------------------------------------------------------11 POWER/VS will update the SIO tables in the execution account record
I
with the number of I/Os it has intercepted for spooling purposes.
alphameric, b: binary, p: packed decimal.
I (3)
m = Total length of SIO tables.
t (~)
Maximum length of execution account record = 2008 bytes.
12 a:
I
Figure 3-9.
120
Execution Account Record
POWER/VS Installation Guide and Reference
RJE ACCOUNT RECORDS
A line account record is created for each RJE,BSC user session when
signoff or line stop is processed. It is a copy of the first 56 bytes
of the Line Control Block.
Bytes IDescription
00-07 IDate in format specified at SYSGEN (mm/dd/yy
lor dd/mm/yy) •
I
08-11 ISIGNON time in packed decimal (OMMMMSSF; F = sign).
I
12-15 ISIGNOFF time (OMMaaSSF: F = sign) •
I
16-31 116 bytes user information.
I
32-39 ,Line password.
a
p
p
a
a
I
40-41 INumber of invalid responses during transmission (4).
b
I
42
IRecord identifier.
I
ISIGNOFF code
fX'01' - Normal SIGNOFF
X'02' - SIGNOFF forced due to central stop
X'04' - SIGNOFF forced due to excessive idle time
X'OS' - SIGNOFF forced due to unrecoverable I/O error.
43
a
b
44
Terminal error count.
b
45-47
Line address.
a
4S
FROM remote ID.
b
49
TO remote ID.
b
50-51 ITransmission count per session (1).
I
52-53 (Timeout count per session (2).
I
54-55 (Error count per session (3).
1
a:
b:
p:
alphameric
binary
packed decimal.
,
b
I
I
b
I
b
-------1
I
I
I
~----------------------------------------------------------------------------~
Figure 3-10.
BJE,BSC Line Account Record
comparing (1) to (2) gives an indication of idle time per session.
comparing (1), (3), and (4) gives an indication of line quality.
(1),
(2), and (3) are also printed locally at SIGNOFF.
A session account record is created when an RJE,SNA user session is
terminated. It is a copy of bytes 32-79 of the SNA unit control block.
Chapter 3.
Using POWER/VS
121
IFormat!
Bytes IDescription
00-07 IDate in format specified at SYSGEN (mm/dd/yy or
Idd/mm/yy) •
t
08-11 ISIGNON time (OHHHMSSF; F
= sign).
I
a
p
12-15 fSIGNOFF time (OHHMKSSFi P = sign) •
p
16-31
16 bytes of user information.
a
32-39
Logical unit name.
a
40-41
Number of invalid responses during transmission.
b
42
SNA record identifier.
a
43
Session termination code
X'01' - normal termination (LOGOFP or SIGNOFF)
X'02' - abnormal termination.
b
44-47
Remote identifier.
b
a:
alphameric
b:
binary
p:
packed decimal.
~--------------------------------------------------------------------~
1
Figure 3-11.
122
RJE,SNA Session Account Record
POWER/VS Installation Guide and Reference
PUTACCT MACRO
The PUTACCT macro adds user account information to the end of the
execution account record. The macro is included in the user-written
$JOBACCT phase that is called at the end of each job or job step.
The exact location of the field for the user account information can
vary, and is dependent on the length of the SIO tables field that
directly precedes it.
i
,
IName
IOperation
IOperands
ICol1
I
1
I
172 1
1---'------------------------------------------------------------------1
I (naae] I PUTACC'l'
I (reg 1)
I
, (reg2)
I
-.J
I
~amming
Notes:
(reg1)
must specify the address of the area containing the user
account information. Register notation must be used.
Any general register except registers 0, 1, 14, and 15
may be specified.
(reg2)
must contain the length of the area. Register notation
must be used.
Any general register except registers 0,
1, 14, and 15 may be specified. The maximum length may
not exceed 2008 bytes minus 8 bytes for the control field
minus the length of the execution account record.
!2te: If POWER/VS does not support job accounting or if
the partition is not running under control of POWERjVS,
the PUTACCT .acro is ignored.
In the following, an example routine is shown to insert user information
in the POWER/VS execution account records:
EXIT
ADAC
Rl
RO
RE ,
CaRG
POWFLG1
COMRG
OSING CMRG,R1
TM
POWFLG1,X'BO'
BNO
EXIT
LA
R 1 ,ADAC
LA
RO,LIADAC
PUTACCT (R 1) , (RO)
OS
OH
BR
RE
DC
EQO
EQU
EQO
GET PARTITION COMMUNICATION REGION
DECLARE ADDRESSABILITY
ACCOUNT SUPPORT FOR THIS PARTITION
BRANCH IF NOT
ADDRESS ADDITIONAL INFO
LENGTH ADDITIONAL INFO
PASS INFO TO POWER/VS
RETURN TO $JOBCTLN
CIADDITIONAL ACCOUNT INFOR~ATIONI
1
REGISTER 1
o
REGISTER 0
14
REGISTER 14
DSECT
DS
CL164
RQO
*
END
Chapter 3.
Using POWER/VS
123
Output Segmentation
SEGMENT MACRO
The SEGMENT macro allows control of output segmentation and the
specification of new output parameters to POWER/VS for a job running in
a POWFR/VS-controlled partition.
IName
IOperation
"
IOperands
ICol
I
172
I
I[ ,FORMS=yyyy]
I
I[ ,JECL= raddr \]
I
\.(reg)j
I
I[ ,NAME=name]
r
1---------------------------------------------------------------------l(name]lSEGMENT
I DEVADDR=SYSxxx
1(*]
I
1
I
I
I
I
I
I
I
I
I
I
I
I
t[ *]
I
I(
I
I
I
*J
I
DEVADDR=
specifies the system or programmer logical unit assigned
to the device on which the segmentation is to occur.
This may be SYSLST, SYSPCR, or SY5000 - SYSmax. This
operand is required.
FORMS=
specifies the new 1- to 4-character forms identification
to be supplied to POWER/VS. The forms identification
must be alphameric, a slash (I), a hypen (-), or a period
(.). If this operand (as well as the JECL operand) is
omitted, the forms identification will be blank.
JECL=
specifies, in place of the forms identification, the
address of a 71-byte save area in which a POWER/VS
* $$ LST, PUN or JOB statement is stored. The LST or PUN
parameters of the * $$ LST or PUN statements need only be
coded if the default values are not sufficient. For
details, refer to "POWER/VS Job Entry Control Language
statements" in this chapter. No continuation statements
are allowed. Any valid POiER/VS parameters may be placed
in this ~ECL area. This operand may be specified as a
symbolic address or in register notation (registers
2-12) •
NAM.E=
specifies a 1- to 8-character name which will be given to
the nev segment. If this operand is omitted, the name of
the segment active on the task will be used.
!ote:
If JECL JOB statements are to be passed via the JECL operand, the
NAME operand should be omitted. The SEGM.ENT macro causes segmentation
to occur and establishes new values for a new segment. If a JECL JOB
statement is passed, it will rename the current seg.ent and should be
passed after a JECL LST or PUN statement is passed. JECL JOB statements
should only be used to provide new user information.
If the output device is not being spooled by POWER/VS, a message viII be
issued on SYSLOG so that the operator can take the required action.
124
POWER/VS Installation Guide and Reference
If output segmentation is requested for output directed to a 3S00
printer, be aware that POWER/VS uses the default printer setup for the
new segment unless you have supplied a JECL LS~ (or PRT) statement
defining the same printer setup.
After issuing the SEG!ENT macro you
can also issue in your application program a SETPRT macro requesting the
proper printer setup.
Example of SEGMENT macro use:
LA
R2,LSTCARD
SEGMENT DEVADDR=SYSLST,JECL=(R2),
NAME=TESTOUT
1STCARD DC
*
CL71'* $$ 1ST FNO=ACB,DISP=H,PRI=1'
RETURN CODES
Successful completion of the SEGMENT macro is indicated to the problem
program by a return code of 0 in register 15.
If the operation fails,
re9ister 15 contains one of the return codes listed below.
Return Code
Dec Hex
fteaning
4
One of the following:
S
X'04'
X'OS'
•
The device addressed by the DEVADDR ope~and is not a
device currently being spooled by POWER/VS.
•
POWER/VS is not active.
•
The partition in which your program is running is not
supported by POWER/VS.
•
The spooled device has a disposition of N.
•
The JECL statement provided was not a
or PUN statement.
*
$$ JOB, LST,
POWER/VS cannot accept the JECL statement because the
partition was not started as a multitasking partition and
the partition is waiting for work, or the partition was
started as a multitasking partition and is waiting for
work, but no JECL statement was submitted for this
device.
Chapter 3.
Using POWER/VS
125
POWERIVS AUTOSTART Statements
POWER/VS offers an automatic start-up facility, called AUTOSTART, that
facilitates the POWER/VS initiation, especially when POWER/VS must be
terminated and restarted frequently and with identical spooling device
assignments.
The following four control statements are available to automatically
initiate POWER/VS:
•
•
•
•
The FORMAT statement
The READER statement
The PRINTE~S statement
The PUNCHES statement.
These statements, which may be entered from a diskette file, via a
cataloged procedure, or in cards, and which must be sUbmitted to the
system via the SYSIN device assigned to the POWER/VS partition, are
described in the following sections.
If an error is detected in an AUTOSTART statement (card deck,
file, or cataloged procedure), POWER/VS expects the corrected
and all subsequent start-up statements to be entered from the
The remaining statements in the card deck, the diskette file,
cataloged procedure are ignored.
Note:
diskette
statement
console.
or in the
The POWER/VS AUTOSTART statements start always in card column 1.
STATEMENT DESCRIPTIONS
By means of the FORMAT statement, you specify whether you want to
perform a warm start, or, if not, which of the POWER/VS files are to be
formatted.
You use this statement, which must immediately follow the
/ / EXEC POWER job control statement, in a way similar to the response
_ you would provide for message 1Q11D if POWER/VS AUTOSTART were not
available.
NO
indicates that no POWER/VS file is to be formatted.
is a POWER/VS warm start.
Q
indicates that the POWER/VS queue file is to be
formatted.
D
indicates that the POWER/VS queue and data files are to
be formatted.
A
indicates that the POWER/VS account file is to be
formatted.
126
POWER/VS Installation Guide and Reference
This
combination
indicates that two of the parameters Q, D, and A may be
specified. The parameters can be specified in any
sequence; they must be separated by commas. For example,
to indicate that all three files are to be formatted,
specify PORMAT=A,D.
One blank must follow the parameter (or the parameter sequence)
specified in this statement. Only one FORMAT statement may be issued
for the POWER/VS AUTOSTART procedure.
Using the READER statement, you define the input spooling device of the
POWER/VS-controlled partition identified in the immediately preceding
PSTART command. The value to be specified for this statement is similar
to the response you would provide for message lR50D if POWER/VS
AUTOSTART were not available.
IREADER={NO }
cuu
I,
NO
indicates that no input spooling device is to be assigned
for this partition. Por POWER/VS, this means that the
partition being started is a writer-only partition.
cuu
specifies the channel and unit address of the partition's
input spooling device. Only one input spooling device
may be specified per partition; however, you may specify
the same device for several partitions.
PRINTERS Statement
By means of the PRINTERS statement, you define the list (print) output
spooling devices of the POWER/VS-controlled partition identified in the
preceding PSTART command. The value to be specified for this statement
is similar to the response you would provide for message 1R50D if
POWER/VS AUTOSTART were not available.
i
IPRINTERS={NO
}
I
cuul, ••• ,cuu8
,
NO
{
indicates that no list (print) output spooling device is
to be assigned for this partition. If PRINTERS=NO and
PUNCHES=NO (see below) is specified, this means that the
partition being started is a reader-only partition.
~UU1}
cuua
specifies the channel and unit addresses of up to eight
list (print) output spooling devices in this partition.
If more than one device is to be specified, any two "cuu"
definitions must be separated by a comma. The same
device or devices may be specified in several partitions.
Chapter 3.
Using POWER/VS
127
Using the PUNCHES statement, you define the punch output spooling
devices of the POWER/VS-controlled partition identified in the preceding
PSTART command. The value to be specified for this statement is similar
to the response you would provide for message lR50D if POWER/VS
AUTOSTART were not available.
i
IPUNCHES={NO
}
I
cuu1, ••• ,cuu8
L
indicates that no punch output spooling device is to be
assigned for this partition.
If PUNCHES=NO and
PRINTERS=NO (see above) is specified, this means that the
partition being started is a reader-only partition.
NO
{
~UU1}
cuuS
specifies the channel and unit addresses of up to eight
punch output spooling devices in this partition. If more
than one device is to be s~ecified, any two "cuu"
definitions must be separated by a comma. The same
device or devices may be specified in several partitions.
An example of how to use the POWER/VS AUTOSTART statements is contained
in "Initiating POWER/VS with AUTOSTART" in Chapter 4 of this manual.
128
POWER/VS Installation Guide and Reference
Chapter 4. Operating a System,
Controlled by POWERIVS
There are two ways of submitting jobs to POWER/VS and of retrieving
them:
•
By starting the POWER/VS partition explicitly as in the procedure
described below.
•
By using the PUTSPOOL macro as described in Chapter 3.
The POWER/VS cross-partition facility requires no commands (for example,
PSTART or PSTOP) to be given. Spool management tasks are created and
deleted dynamically by POWER/VS.
Assumptions
The following sample procedure for initiating POWER/VS and running jobs
under the control of POWERjVS is based on the assumption that POWER/VS
resides in partition Fl and that the following I/O devices are available
for spooling input and output:
IBM 2540 Card Reader with device address I'OOC'
IBM 2540 Card Punch with device address X'OOD'
IBM 1403 Printer with device address X'OOE'
IBM 3203 Printer with device address X'01E'
IBM 3800 Printer with device address X'118'
IBM 3340 Direct Access Storage with device address X'260'
IBM 3330 Disk Storag@ wjth device address X'133'
IBM 2780 Data Transmission Terminal with device address X'060'.
The direct access storage is used for the POWER/VS files; the data
transmission terminal for remote job entry. The example also assumes
that POWER/VS will support BG, F2, and F3.
Initiating POWERIVS
POWER/VS can be initiated at any time. POWER/VS is initiated in a
DOS/VS system like any problem prograa. In addition, the AUTOSTART
facility is available, which allows you to start POWER/VS with a minimum
of intervention. The facility is particularly useful if POWER/VS must
be initiated frequently with unchanged'device addresses, tasks, spooled
partitions, and RJR lines. For details concerning the POWE~/VS
AUTOSTART facility, consult the section "POWER/VS AUTOSTART statements"
in Chapter 3.
The start-up procedure (with and without AUTOSTART) includes the
following steps:
Chapter 4.
oper,ating a System controlled by POWER/VS
129
•
Formatting of POWER/VS queues.
(Not necessary when the information
already accumulated is to be used. This procedure is called a warm
start.) If the extents used to define the POWER/VS files are changed
between one execution of POWER/VS and another, the POWER/VS files
should be reformatted. These files should also be reformatted if a
new generation of POWER/VS was link-edited since the files were used
last.
•
Verifying that the disk packs used for the POWER/VS files are mounted
on the proper disk drives and that these drives have been made ready.
•
starting POWER/VS tasks.
•
Starting POWER/VS controlled partitions.
•
specifying the devices to be spooled in each controlled partition.
INITIATING POWER/VS WITROUT AUTOSTART
The following is a description of the steps required to start POWER/VS
when the AUTOSTART facility cannot be used:
Make the reader, the printer, and the punch available for POWER/VS use
by unassigning these devices in the partition that owns them; for
example:
ASSGN
ASSGN
ASSGB
ASSGN
SYSIN,OA
SYSLST,OA
SYSPCH,UA
SYSnnn,OA
(if the device was used as a programmer logical
unit) •
You may also enter the sequence
DVCDN
DVCUP
X'cuu'
X'cuu'
for each of the affected devices.
If the partition into which POWER/VS is to be loaded is still active,
stop it by issuing the STOP co.mand.
Allocate sufficient real and virtual storage to the POWER/VS partition.
If the supervisor of your system was generated with the required real
and virtual storage allocations, this step may be omitted. Your system
programmer will tell you how much storage you must allocate. A typical
example:
ALLOCR F1R=30K
ALLOC Fl=196K
130
POWER/VS Installation Guide and Reference
!ot2:
Before you can allocate the required real and virtual storage
space for the POWER/VS partition, you must stop all partitions in your
DOS/VS system by means of the DOS/VS com_and UNBATCH partition.
After
successful storage allocation, you may start the DOS/VS partitions
again.
start the POWER/VS partition using the START command.
enter:
For example,
START Pl
You can omit this step if you intend to enter the POWER/VS initiation
statements via SYSLOG (see step 6). Otherwise, assign 5YSRDR to the
device from which the POWER/VS initiation statements are to be read.
Assign SYSLST if your installation requires
•
A status report after a warm start.
•
A dump of the POWER/VS partition, should POWER/VS terminate
abnormally during initiation.
See Pigure 4-2 for an example of a status report after a warm start.
Place the POWER/VS initiation statements into SYSRDR assigned in step 4.
An example of these statements, which vary from one installation to
another, is given in Figure 4-1.
/ / JOB POWER/VS INITIATION
/ / AS5GN 5Y5000,X 1 260 1
/ / DLBL IJAFILE,'POWER/VS ACCTPILE',99/365,DA
/1 EXTENT SYSOOO,POWER1,1,O.12,60
1/ AS5GN SYS001,X'260'
/ / DLBL IJQPILE,'QFILE POWER/V5',99/365,DA
1/ EXTENT SYS001,POWER1,l,O.72,48
I I AS5GN 5Y5002,X 1 133 1
/ / ASSGN SY5003,X'134 1
I I DLBL IJDFILE,'DATAPIL POWER/VS',99/365,DA
/1 EXTENT SYS002,POWER1,1,O,95,855
/1 EXTENT SYS003,POWER2,1,O,3800,1045
I I EXEC POWER
(see note 3 below)
Figure 4-1.
Job Stream Exaaple for POWER/VS Initiation
Chapter 4.
operating a System controlled by POWER/VS
131
H.ot~:
1.
DLBL and EXTENT statements may have been stored on the label
cylinder(s) of your system pack.
In this case, they need not be
provided as part of the initiation job stream.
2.
5YSOOO, SYS001, and SYS002 may be assigned to different device
types.
3.
If your POWER/iS system includes RJE,SNA support, or if you are
using an IBM 3800 printer, you must specify the SIZE= parameter in
the /1 EXEC statement; for example:
1/ EXEC POWER,SIZE=234K.
POWER/VS STATUS REPORT
04/30/77
TOTAL NUMBER OF QUEUE RECORDS
OF FREE QUEUE RECORDS
MAX. NO. OF QUEUE RECORDS USED IN PRESENT SESSION
NU~BER
DATA FILE
IJDFILE
TOTAL NUMBER OF TRACKS
TRACK GROUP SIZE
DATA BLOCK SIZE
ACCOUNT FILE
1178 RECORDS
1079 RECORDS
118 RECORDS
1178 TRACKS
1 TRACK
952 BYTES
IJAFILE
TOTAL NUMBER OF TRACKS
PERCENTAGE OF FILE THAT IS FILLED
19 TRACKS
14 %
REAL STORAGE ALLOCATED TO POWER/VS PARTITION
NUMBER OF TIMES WAITING FOR REAL STORAGE
MAXIKOM NUMBER OF REAL PAGES FIXED
MAXI~UM NUMBER OF TASKS ACTIVE AT ONE POINT IN TIME
11 PAGES
Figure 4-2.
0 TIMES
9 PAG~S
13 TASKS
Example of a POWER/VS Status Report
Notes:
1~f POWER/VS has been generated without the job accounting support,
the account file statistics are replaced by the message
NO ACCOONT SUPPORT.
2.
Statistics provided by POWER/VS following a warm start supply
information about activities from the time POWER/VS was started
until the time the statistics are displayed.
The maximum number of
queue records used in a report after warm start gives the number of
active entries.
3.
Statistics provided by POWER/iS following a PEND command give
information about the end~d POWER/VS session.
Up to five extents can be specified if additional extents are needed for
the POWER/VS data file.
They can be either on the same volume, or if
they are on different volumes, logical unit assignments must be in
ascending sequence of volumes to be used.
SY5002-SYS006 can be used for
the POWER/VS data file; they must be assigned to the same type of
device.
132
POWER/VS Installation Guide and Reference
Step 7
When the message
lQllD FORMAT QUEUES=
is displayed, your response can be one of the following:
Q( , A]
=
Format the queue file [and, optionally, the account file].
D[ , A]
=
Format the queue file and the data files [and, optionally,
the account file].
A
Format the account file.
NO
No formatting is required
Note:
(warm start).
Instead of entering NO, you may simply press END/ENTER.
If you perform a warm start, and if you assigned SYSLST in step 5,
POWER/VS prints a status report (see Figure 4-2 for an example) •
In case of an abnormal warm start (warm start after an abnormal termination of POWER/VS), the following job number will be one higher than
expected to prevent duplicate job numbers for accounting information.
When initiation is complete, the message
lQ12I POWER/VS INITIATION COMPLETED
is displayed. SYSRDR, SYSIPT, SYSLST, and SYSPCH are then unassigned in
the POWER/VS partition.
step 8
Ose the PSTART command to start POWER/VS tasks.
statement:
For example, the
PSTART RDR,OOC,A
causes a POWER/VS reader task to spool input from OOC and assign class A
to all reader queue entries from that reader, unless another class is
specified in the JECL for an entry.
The statement:
PSTART F2,2A
places a partition under control of POWER/VS.
Note that, for this
purpose, F2 must have lower priority than the POWER/VS partition. Row
to start POWER/VS tasks, partitions and RJE lines that are to operate
under control of POWER/VS, is described in more detail later in this
procedure.
When you enter the PSTART command to bring a partition under control of
POWER/VS, you are prompted to specify the devices that are to be spooled
for that partition. The prompting messages are (for the above example) :
1Q86I
1RSOD
lR50D
lRSOD
PLEASE SPECIFY DEVICES TO BE SPOOLED
F2 READER=
F2 PRINTERS=
F2 PUNCHES=
Chapter 4.
Operating a system controlled by POWER/VS
133
SYSLOG stops after each aessage to allow you to specify a device address
(or NO if a specific device type is not used) as shown in the example
below:
lR50D
F2 READER=OOC
1R50D
F2 PRINTERS=OOE,OlE
lR50D
F2 PONCHES=NO
Note:
If your response is READER=NO, but you specify one or more
addresses for PRINrERS or for PUNCHES or for both, POWER/VS operates as
a writer-only spooling program for the partition concerned. POWER/VS
spools the input only if your response is READER=cuu, PRINTERS=NO and
PUNCHES=NO.
A device can be specified only once, even if it can both
read and wri tee
After a partition has been brought under control of POWER/VS, I/O
requests from that partition to the specified devices are intercepted by
POWER/VS. If the reader queue does not contain an entry for processing
in this particular partition, POWER/VS displays the message:
1Q34I P2 WAITING FOR WORK
INITIATING POWER/VS WITH AOTOSTART
The following are examples for the steps required to start POWER/VS
using the AUTOSTART facility:
Step 1
Start the POWER/VS partition, using the START com.and. You may have to
stop the partition before you can issue the START command.
Note:
The initiation statements, and also the AUTOSTART cards, may be
supplied via a SYSIN file on disk, tape, or diskette, or via a card
reader, but the / / EXEC POWER statement should not be supplied via a
procedure.
If this is done, the DOS/VS procedure library is in use
during the entire POWER/VS run and may not be updated until POWER/VS is
ended.
Step 2
Assign SYSIN for the POWER/VS partition to the device from which the
POWER/VS initiation state_ents and the POWER/VS AUTOSTART statements are
to be read.
Place the required statements in the SYSIN device assigned in step 2 and
make the device ready. You may also supply the initiation and AUTOSTART
statements via a cataloged procedure. An example of the AUTOSTART
statements that may be presented to POWER/VS immediately following the
/ / EXEC POWER statement is given below:
134
POWER/VS Installation Guide and Reference
FOR~~T=NO
PSTART RDR,OOC
PSTART BG,ABC
READER=QOC
PRINTERS=OOE
PUNCHES=OOD
PSTART F2,DEF
READER=OOC
PRINTERS=01E
PUNCHES=OOD
PST~~T LST,OOE
PSTART LST,01E
PSTART PUN,OOD
PSTART RJE,060
/*
The FORMAT state.ent must be the first one after the / / EXEC statement.
If the FORMAT statement is omitted, POWER/VS prompts you for acceptable
format specifications in the same way as it does when you start POWER/VS
without AUTOSTART.
The statements that start a system task (partition) can be entered in
any sequence. However, once a partition has been started, the device
specifications for that partition must follow immediately and in the
sequence:
1.
2.
3.
READER= statement
PRINTERS= statement
PUNCHES: statement.
After POWER/VS has processed the FORMAT statement and read the remaining
statements from SYSIPT, it anassigns SYSRDR, SYSIPT, SYSPCH, and SYSLST
for the POWER/VS-controlled partitions and processes the PSTART commands
that were submitted via SYSIPT. If any of the PSTART commands are
invalid, POWER/VS prompts you to specify the correct device address.
Job streams to be processed under control of POWER/VS can immediately
follow the POWER/VS AUTOSTART statements.
Spooling device specifications can be made as follows:
READER=fNO }
lCUU
PRINTERS={NO
}
cuu1,cuu2, ••• ,cuu8
PUNCRES={NO
}
cuu1,cuu2, ••• ,cuu8
If the spooling device specifications in the AUTOSTART,statements are
incorrect or incomplete, POWER/VS prompts you for acceptable
specifications in the same way as it does when you start POWER/VS
without AUTOSTART.
ASSIGNING DUMMY DEVICES
POWER/VS intercepts I/O requests addressed to specific physical devices,
regardless of the symbolic units that are assigned to these physical
devices. If I/O requests are intercepted by POWER/VS, the assignment
for the physical unit is in fact a dummy assignment, because the
physical device is not used by the problem program. with POWER/VS you
Chapter 4.
Operating a System Controlled by POWER/VS
135
can assign logical units in different partitions to the same physical
unit-record device. such assignments are regarded as dummy assignments,
since the assigned physical device is not used by all the partitions in
which it is assigned. Dummy devices, however, are not required, except
for multifunction card devices. The use of writer-only partitions as
well as cardless systems normally require dummy devices.
Each ASSGN statement or command in a POWER/VS-controlled partition is
checked by job control to determine if I/O requests for the specified
logical unit are to be intercepted by POWER/VS. If requests for a
certain physical unit are to be intercepted by POWER/VS, job control
will not check for conflicting I/O assignments. As a result two or more
assignments are permitted from different partitions to the same unitrecord device, as long as no more than one of these assignments implies
physical ownership of the device.
CHANGING PARTITION PRIORITIES
The priority of the POWER/iS partition must always be higher than that
of the partitions under its control.
If you want to change the priorities of the partitions while POWER/VS is
active, the DOS/VS PRTY command is rejected if you make an attempt to
give one of the partitions supported by POWER/VS a higher priority than
the POWER/VS partition.
POWER/VS initialization is canceled if the priorities of the partitions
conflict with the POWER/VS requirements.
Issuing POWERIVS Commands
POWER/VS commands can be entered in one of three ways:
•
At the system console by the central operator
•
At a remote terminal or work station by the terminal operator
•
Within an anplication program by means of the CTLSPOOL macro.
At the system console, POWER/VS operator commands are entered in the
same way as attention routine commands (omit steps 1 and 2 if your
system operates on a Kodel 115 or 125):
1.
2.
3.
4.
Press RBQUEST
wait for AR to appear
Enter the command
Press END or ENTER.
Most of the POWER/VS commands available to the central operator are
either queue management or task management commands. Queue management
commands enable you. to manipulate the queue entries for the POWER/VS
jobs; task management commands allow you to control POWER/VS operation.
Figure 4-3 shows the two groups of commands by the function they
control.
136
POWER/VS Installation Guide and Reference
~---------------------------------------------------------------------------,
TYE~_Q!
i§hort
tFoil
Command
Queue
Management
Comaands
IPDISPLAY
D
I
I
I PALTER
A
I
I
IPDELETE
I
IPRELEASE
L
R
I
Task
M.anagement
commands
PSTART
S
PSTOP
P
PGO
G
PEND
Figure 4-3.
IFunction
I
IDisplay the status of POWER/VS
I job (5)
I
•
IAlter the processing attributes of
I a POW ER/V S job.
I
IDelete queue entries or messages.
I
IRelease POWER/VS jobs for further
Iprocessing.
Istart a task, place a partition unIder the control of POWER/VS, or
lestablish the POWER/VS-VTAM. interI face (RJE, SN A) •
I
Istop a task, release a partition
tfrom POWER/VS control, terminate
an SNA user session, or terminate
RJE,SNA processing.
Reactivate a task or a partition.
Terminate POWER/VS.
PCANCEL
c
Cancel a POWER/VS status report.
PFLUSH
F
Plush (cancel processing of) the
current queue entry.
PRESTART
T
Restart a writer task.
POWER/VS Commands
Whenever you enter a queue management command related to a set of queue
entries for a particular POWER/VS job, make sure that your command
correctly identifies the job by the name under which it was logged by
POWER/VS and, possibly, also by the number that POWER/VS assigned to it.
A number is required when two or more POWER/VS jobs have been entered
under identical names.
If you are in doubt about the correct identification of a POWER/VS job,
enter a PDISPLAY command specifying either the queue and the job name or
the queue and ALL before you enter the queue management command in
question. The status report you receive provides you ~ith a list of
POWER/VS jobs currently logged in a specific queue, and under a specific
name if you specified a job name.
For the terminal operator, a set of commands similar to the JECL
commands is available for entry at a remote terminal or work station.
These commands, vhich are referred to as the Remote Operator Command
Language (ROeL), are described in the POWER/VS Work station User's
Guide, GC33-6049.
Chapter 4.
Operating a system Controlled by POWER/VS
137
To invoke a POWER/VS service from an application program executing in a
partition other than the POWER/VS partition, the macro instruction
CTLSPOOL may be used with the parameter specification REQ=COnaAND.
However, this macro allows only five commands to be issued. These are:
•
•
•
•
•
The
The
The
The
The
PALTER command
PCANCEL com.and
PDELETE command
PDISPLAY command
PRELEASE command.
The use of this macro and the related additional macros is explained in
detail in "Cross-Partition Communication Kacros" in Chapter 3.
I STARTING
AND STOPPING A USER PARTITION
Bringin~fartition
Under the Control of POWER/VS
When you bring a partition under the control of POWER/VS, you activate
the POWER/VS task that makes spooled input available for processing in
the named partition.
To bring a partition under the control of POWER/VS, use the PSTART
command.
For example, the statement:
PSTART F2,AB2
causes those POWER/VS jobs in the reader queue with a class
specification of A, B, or 2 to be executed in partition F2.
!Q!g:
A clas$ specification of AB3 in the above command would have been
flagged as invalid because the partition-dependent class 3 does not
match the partition identifier specified in the command (F2).
The statement:
S
BG,OA,X
causes POWER/VS to place the BG partition under control of POWER/VS.
Jobs of class '0' and 'A' may be processed by this partition.
All print
and punch output will have a default class of ·X'.
When a partition is placed under POWER/VS control, one or more program
classes can be specified to ensure that only programs with one of these
classes can be executed in that partition. If it is desirable to change
this class specification, proceed as follows:
1.
stop the p.artition (see "stopping POWER/VS Tasks" in the section
"Task Control" below).
2.
Start the partition again using a PSTART command that specifies the
neW program classes to be handl~d by that partition.
138
POWER/VS Installation Guide and Reference
A user may have special spooling requirements not supported by POWER/VS,
for example when using the special punch features of the IB~ 2560
Multifunction Card unit.
This requires special handling for a job.
In the following, a procedure is described to stop a partition under
POWER/VS, start it again under control of the DOS/VS supervisor, execute
the job, and bring the partition back under POWER/VS control after the
job is finished.
•
Stop the partition on a job boundary using PSTOP.
•
stop any POWER/VS reader or writer task that uses devices which say
be required by the job to be run.
•
Issue the DOS/iS START com.and.
•
Assign the necessary devices for the partition.
•
Make the devices ready and start the partition using the ENTER key.
•
When the job has finished, stop the partition using the DOS/VS STOP
command.
•
Issue the PSTART com.and to start the POWER/VS partition.
TASK CONTROL
A reader task reads records from a card reader, a tape, or a diskette
device and writes them onto intermediate storage on disk. You may start
a reader task any time you have a physical reader available, regardless
of the number of reader tasks currently active.
To start a reader task, use the PSTART command.
statement:
PSTA~T
For example, the
RDR,00C,2
starts a reader task with a partition-dependent class specification.
The task causes the job streams in the specified reader (OOC) to be read
and spooled onto disk. Unless a different class is specified in the job
streams, the POWER/VS jobs spooled by this task will be executed in
partition F2.
The statement:
PSTART RDR,OOC,B
starts a reader task with a partition-independent class. In this case,
a POWER/VS job spooled by the task is assigned class B, unless a
different class is specified in the job stream of that job.
Chapter 4.
Operating a System Controlled by POWER/VS
139
The statement:
PSTART RDR,OOB,,'INPUT',2
starts a reader task to read a file named INPUT from two diskette
volumes on device OOB.
The statement:
PSTART RDR,480
starts a reader task from a tape on device 480.
A list (print) or punch writer task transfers data from intermediate
storage to the printer or punch, respectively. You may start a list or
punch task whenever you have a physical printer or punch available,
regardless of the number of writer tasks currently active.
To start a writer task, use the PSTART command.
statement:
For example, the
PSTART LST,OOE,AB
starts a list (print) task to print output of POWER/VS jobs that had
classes A and B assigned. The task uses the printer whose device
address is OOE.
The statement:
PSTART LST,118,T,2
starts a list (print) task with two print buffers to print output of
POWER/VS jobs that have class T assigned.
The task uses the printer
whose device address is 118.
The statement:
PSTART PUN,OOD,X'28S'
starts a punch task to punch on the device OOD the output that was spooled
onto a tape.
That tape is mounted on the drive with the address X'28S'.
The PSTOP command is available to stop a POWER/VS task, to take control
of a partition away from POWER/VS, and to stop transmission of data via
an RJE line.
To stop a reader task, you should specify EOJ as the second operand. If
you fail to do so, the reader task terminates input processing
imm~diately, the queue entry which was being built by the task is not
included in the reader queue, and the rest of the statements will not be
read. Examples of PSTOP commands to stO? a reader task are given below.
The statement:
PSTOP
Ooe
causes the associated reader task to stop input processing immediately.
140
POWER/VS Installation Guide and Reference
The statement:
PSTOP OOC,EOJ
causes the associated reader task to stop after it has (1) finished
processing the current POWER/VS job and (2) placed the queue entry which
was being built into the reader queue.
To stop a list task, you can use the PSTOP command without a second
operand, or with EOJ or RESTART specified as the second operand. For
example, the statement:
PSTOP OOE
causes the associated list task to stop output processing immediately,
but the current queue entry is not deleted from the output queue. When
the task is started again (by issuing a PSTART command), processing of
the output for that queue entry starts again with the first output
record.
The statement:
PSTOP OOE,RESTART
has the same immediate effect as the above example. However, when the
task is started again (by PSTART), processing of the output for the
queue entry starts with the record following the last one processed
before the PSTOP command was issued, and when a 3800 printer was used,
with the copy group index being processed when the PSTOP command was
issued. For more information on copy grouping refer to the description
of the * $$ LST statement in Chapter 3.
The statement:
PSTOP OOE,EOJ
causes the associated list task to stop after it has fin~shed printing
the output for the current list queue entry. When the task is started
again (by PSTART), it processes the output of the next entry in the list
queue.
POWER/VS acknowledges the PSTOP command by message lQ33I.
The information provided above for stopping a list task also applies to
stopping a punch task. Examples of PSTOP commands to stop a punch task
follow:
PSTOP OOD
PSTOP OOD,RESTART
PSTOP OOD,EOJ
POWER/VS acknowledges the command by message 1Q33I.
The following procedure is recommended for using the PSTOP command to
stop RJE lines, except in cases where a line must be stopped without
regard for whether it is currently in the processing or inactive state:
1.
Issue a PINQUIRE ALL command to determine the current status of your
RJE lines.
2.
Issue a PSTOP command for a line which is inactive. Specify EOJ as
the second operand in your PSTOP command, in case a remote entry was
started between the time processing of your PINQUIRE command was
completed and processing of your PSTOP command begins.
Chapter 4.
Op~rating
a System Controlled by POWER/VS
141
If, for example, you issue the command
PSTOP 060
then all read and write activities are stopped immediately. If the line
was being used to transmit data from the terminal, input data is lost.
If the line was being used to transmit data to the terminal, that output
data is still in the output queue. If you issue the command
PSTOP 060,EOJ
then transmission of input or output is allowed to continue until the
end of the current queue entry.
POWE~/VS
acknowledges the command by message 1R02I.
To take control of a partition away from POWER/VS, you also use the
PSTOP command. For example, assuming that partition F2 was originally
placed under POWER/VS control by an appropriate PSTART command, then
PSTOP F2
causes program execution in partition F2 for a particular reader queue
entry to be completed and the partition to be returned to DOS/VS
control.
After the partition is released by POWER/VS, SYSRDR and all assignments
to spool devices for this partition are also released.
POWER/VS acknowledges the command by message 1Q33I. After display of
this messag~, the partition is available for processing under DOS/VS.
To return the partition to POWER/VS control, you have to issue the
DOS/VS STOP or UNBATCH commani, followed by a PST~RT command.
REKOTE JOB ENTRY - BSC TERMINALS
By starting an RJE,BSC line, you actually start a POWER/VS RJE task.
This task processes job streams from a terminal and creates reader queue
entries (one per POWER/VS job transmitted from the terminal). On
request from the terminal operator, an RJE print or punch task makes
output available for transmission to the terminal. POWER/VS allows you
to start up to 25 RJE,BSC lines for concurrent operation.
To start an RJE,BSC line, use the PSTART command.
statement:
For example"
the
PSTART RJE,060
causes the line with the physical device address 060 to be started.
When POWER/VS has finished executin9 this command, a terminal operator
whose terminal is attached to this line can sign on.
142
POWER/VS Installation Guide and Reference
The statement:
PSTART RJE,060,RJESYS12
causes the same POWER/VS action as the above example. However, the
SIGN ON command from a terminal operator whose terminal is attached to
line 060 is accepted only when he specifies the password RJESYS12 in his
SIGNON command.
Note:
If a password is specified in the PSTART command for an RJE,BSC
line, this password overrides the password specified in the PLINE macro
for this line.
controlling RJE,BSC Operations
The following POWER/VS commands can be used to monitor and control
RJE,BSC operations from the central installation:
PSTART
start an RJE line (this is discussed above) •
PINQUIRE
Display the status of one or all supported RJE lines.
PDISPLAY
Display the status of RJE-type queue entries.
PALTER
Change the destination of output for remotely entered
POWER/VS jobs.
PDELETE
Delete ALLUSERS messages originated by the central operator.
PBRDCST
Send a message to an individual terminal user or to all
terminal users.
PSTOP
Stop an RJE line.
REKOTE JOB ENTRY - SNA TERMINALS
Establishing the VTAM Interface for POWER/VS with RJE.SNA
Before SNA terminal users can log on to POWER/VS, you must have
established the interface between POWER/VS and VTAM, as V~AK handles all
physical line management for SNA terminals, using Synchronous Data Link
Control (SDLC).
VTAM must run in a partition with a higher priority than POWER/VS.
To establish the interface, use the PSTART command in'the format:
PSTART RJE,SNA
This command causes POWER/VS to activate the VTAM interface by opening
the Application control Block (ACB), after which logical units that have
been identified to VTAM can log on.
If the com.and is valid, the
message 1V04I RJE,SNA STARTED is displayed. If the command is invalid,
an information-type message is displayed.
Refer to DOS/VS POWER/~
Works!gtion Qser'§_Guide, GC33-6049 for possible causes.
Chapter 4.
Operating a System Controlled by POWER/VS
143
The following POWERjVS commands can be used to monitor and control
RJE,SNA operations from the central installation:
PSTART
Establish the VTAn interface.
PINQUIRE
DisDlay the status of one logical unit, or display the
logical unit names of all active logical units (status:
PROCESSING and LOGGED ON) , together with the remote-IDs of
the Users operating them.
PDISPLAY
Display the status of ~JE (BSe and SNA)-type queue entries or
list all ALLUSERS-type messages.
PALTER
Change the destination, class, disposition, or copy count of
output for remotely entered POWER/VS jobs.
PDELETE
Delete one or more entries from the specified job queue;
alternatively delete one specific ALLUSERS-type message or
delete all ALLUSERS-type messages.
PBRDCST
Send a message to an individual terminal user or to all
terminal users.
PSTOP
Terminate a specific user session or deactivate the VTAM
interface and thereby all current user sessions.
To stop a session identified by 'luname ' , the following format appli.es:
PSTOP RJE,SNA,luname( ,EOJJ
RJE,SNA
Informs POWER/VS that the command applies to an SNA session
or to all SNA processing. If no more parameters are
specified, POWER/VS imaediately deactivates the VTAn
interface.
luname
Causes POWER/VS to terminate only the session with the
logical unit whose name is specified by this parameter.
ROJ
All active input or output processing will be completed for
current POWER/VS job entries. If this parameter is omitted,
all processing is stopped immediately for the affected
session.
In case of emergency, the central operator may also terminate a session.
To do this, he issues the VTAK command
VARY NET,INACT,I,ID=luname
upon which VTAM will notify POWER/VS in the LOSTE~n exit. POWER/VS
handles this termination in a similar way as an unconditional LOGOFF
request.
144
POWER/VS Installation Guide and Reference
The following lists the possible central operator commands to terminate
RJE,SNA operations and the actions taken by the system:
HALT QUICK
This VTAft command causes VTAM to notify POWER/VS that
an emergency stop is required for all active SNA
sessions.
HALT
This VTAM co•• and causes VTAM to notify POWER/VS to
begin an orderly termination of all sessions. The
same action is taken as if a conditional LOGOFF
terminal command had been requested for all sessions.
PSTOP RJE,SNA,EOJ
or PEND
POWER/VS makes a conditional termination
for all sessions.
PSTOP RJE,SNA
or P~ND KILL
POWER/VS makes an unconditional LOGOFF for all
sessions.
TERMINATING POWER/VS
POWER/VS may be terminated normally, for example ~hen programs that do
not need a POWER/VS environment must be run, or in an emergency.
Before you terminate POWER/VS, inform any operators of remote terminals
that the shutdown procedure is about to begin. Then enter PEND. For
example, the statement:
PEND
causes (1) all active tasks to continue processing until they encounter
the end of the current POWER/VS job, (2) the POWER/VS-controlled
partition to be released when program execution for the currently
processed reader queue entries is finished, and (3) the POWER/VS
partition to be released. Your operating system is restored to norMal
DOS/VS operation when message 1Q211 has been displayed.
The statement:
PEND OOE
causes the same action as in the above example. In addition, a status
report is printed on the printer with the address OOE by POWER/VS before
it restores your operating system to normal DOS/VS operation. This
status report is similar to the one provided by POWER/VS after a warm
start (see Figure 4-2).
Chapter 4.
op~rating
a System Controlled by POWER/VS
145
Emergency Termination
When it is necessary to terminate POWER/VS immediately because of an
emergency situation, use the PEND command with the operand KILL. This
command causes POWER/VS to terminate immediately and, if a printer
address is specified, to produce a system dump (printout of virtual
storage) on the specified printer.
As a result of a PEND co •• and with the KILL operand, input and output of
jobs is broken off. A warm start enables you to restart output from the
beginning of the interrupted job. Input of a job entry that was
interrupted by the co •• and must be resubmitted completely.
Two examples of the PEND command with" the KILL operand follow.
statement:
The
PEND KILL
causes an emergency termination of POWER/VS without a systea dump being
produced.
The statement:
PEND KILL,OOE
causes an emergency termination of POWER/VS with a system dump being
produced on the printer with the address OOE.
Your operating ~ystem is restored to normal DOS/VS operation when
message 1Q21I has been displayed.
MULTIPURPOSE UNIT-RECORD DEVICES
If your installation uses any of these devices for POWE~/VS, remember
that they cannot be used simultaneously for a reader and a punch task.
If it is necessary to start the reader task for one of these devices
while the punch routine is still processing, you must first stop the
punch task using the PSTOP com.and. For example, the statement:
PSTOP OOD,EOJ
causes the device to stop punching on completion of the output for the
punch queue entry currently being processed by the associated punch
task.
The statement:
PSTOP OOD,RESTART
causes the device to stop punching output im.ediately.
In both cases, POWER/VS displays the message 1Q33I STOPPED PON,OOD when
the punching operation has stopped. You may then start the reader task
using the command
PSTART RDR,OOD
1U6
POWER/VS Installation Guide and Reference
After the reader task finishes reading the new input, stop it and
restart the interrupted punch task. For the above example, the com.ands
would be:
PSTOP OOD
(assuming that the last card in the read hopper has been read)
following message 1Q33I:
and,
PSTART PUN,OOD
Miscellaneous Devices
USING THE IBM 3540 DISKETTE INPUT/OUTPUT UNIT
You can use the 3540 unit as a POWER/VS input device, either as a card
reader (SYSIN mode) or as a supplement to the card reader (data mode) •
POWER/VS can, for example, read the job control statements from the card
reader and then switch to the diskette unit to read a data fil9, or it
can read control statements and card image data from the diskette unit,
using no card reader at all.
For 3540 SYSIN files, a reader task will read either 80- or 81-character
records from diskette and put aO-character records onto the spool disk.
The size of ,the records to be read is obtained from the HDR1 label on
the file and must be 80 or 81 bytes. If the input records are 81
characters in length, only the last 80 bytes will be copied to the
POWER/VS data file.
If an * $$ RDR statement is read from the diskette, POWER/VS issues a
message (lQ90I INVALID * $$ RDR STATEMENT) and flushes to the next
POWER/VS job on the diskette file currently being processed.
The SYSIN records can be read only by a user program that is reading
from a card reader specified at partition start-up as a unit-record
device to be spooled. Because DTFDU cannot be assigned to a card
reader, DTFDU cannot be used to access these files.
ExamEle: Job control statements and data are both on one 3540 SYSIN
file.
The operator enters a PSTART command to start a reader task on a
3540 diskette (X'OOB'):
PSTART RDR,X'OOB',B,'FILE-ID',31
Up to 31 diskettes of the file called FILE-ID will be read. Reading
stops after 31 diskettes or after reading a diskette that does not have
a continuation indicator in its label. One 3540 file may contain many
DOS/VS jobs and/or POWER/VS jobs. Jobs with no cla'ss specification in
their * $$ JOB card, or jobs for which no * $$ CTL statement is in
effect, are put into class B.
During program exeuction, the records will only be passed to programs
reading from a card reader that has been specified as the reader spool
device when starting the partition.
Chapter 4.
Operating a system Controlled by POWER/VS
147
For data files, a reader task can read records of from 1 to 128
characters.
These records are not examined for control statements and
are written onto the spool file exactly as read.
The data records
cannot be read by programs accessing a card reader.
They can only be
read by a user program that is reading from the physical unit specified
on the * $$ RDR statement. This unit must be assigned to a 3540.
Either DTFDU or DTFDI can be used to access these files.
Two or more files per 3540 volume may be specified through the use of
two or more * $$ RDR statements in the card reader.
Note that although a diskette file may be inserted into a card input
stream, it is not possible to insert card data into the middle of a
diskette file or to insert one diskette file into another.
The
*
$$ RDR statement causes a POWER/VS task to insert information from
a 3540 file into the input being read from the card reader.
You do not
need to submit other JECL statements for a job containing a RDR
statement.
This statement is ignored in a writer-only partition.
~!gm21~_1:
The job control statements are in the card reader, data is
on the 3540. The operator enters a PSTART command for the card reader
(X'OOC') and input class A:
PSTART RDR,OOC,A,OOB
This command informs POWER/VS to start a reader task at address X'OOCI
with the ability to read from a 3540 at address X'OOB' also.
Both input
devices belong to the reader task and cannot be used physically by any
other partition or POWER/VS task until the reader task terminates.
The
following cards are in the card rader (X.OOC'):
/ / .10B EXl
/ / ASSGN 5YS008,X'OOB'
/ / DLBL FILE,'FILE-ID'"DU
I I EXTENT SYS008
/ / EXTENT SY5008
/ / EXEC PROG
* $$ RDR DEV=X'00B',FID=IFILE-IDI,NOD=2
/*
/&
The 5YS008 specification in the / / EXTENT statements is not required if
the symbolic unit was assembled into the DTFDO.
The RDR statement causes the reader to suspend card reading to read up
to two diskettes of the data file named FILE-ID. Records on the 3SQO
may be from 1 to 128 bytes long and will not be examined for control
statements by either the reader task or the execution processor.
When
the end-of-file identifier is reached, card reading is resumed.
During the execution of the user program, not all of the FILE-ID records
spooled by the reader task may be read.
To prevent the remainder of the
records from being passed to job control as 5YSIN data (once the * $$
RDR statement is reached), any request to the card input spool device
will cause POWER/VS to skip records until the end of the FILE-ID file.
148
POWER/VS Installation Guide and Reference
Example 2: Some job control statements are in the card reader,
additional job control state.ents and data are on a 3540 diskette. The
operator enters a PSTART command for the card reader CX'OOC') and input
class A:
PSTART RDR,OOC,A,OOB
This command causes the reader task to insert 3540 data from X'OOB' into
the input stream on the spool disk when an * $$ RDR statement is
encountered in the card input stream. The following cards are in the
card read~r:
1/ JOB EXl
/&
*
$$ RDR FID='TESTJOB'
I I JOB EX2
The * $$ RDR statement causes the reader task to suspend card reading
and to read one diskette of a SYSIN file named TESTJOB from the 3540
specified in the PSTART com.and (X·OOB'). The TESTJOB file could
contain the following statements, for example:
I I JOB ASSEM
1/ EXEC ASSEMBLY
source code
1&
For more information on the use of the * $$ RDR statement, refer to the
section "POWER/VS Job Entry control Language statements" in Chapter 3.
Not~:
POWER/VS will only spool 80- or 81-byte records from the 3540 for
programs that ask for card input. A user converting from a
Multifunction Card Unit to a 3540 must change his programs if 96-byte
records were used.
Chapter 4.
op~ratin9
a System Controlled by POWER/VS
149
Appendix A. Data Compaction
compaction provides a method by which non duplicate characters may be
compressed. It takes advantage of the fact that most data streams use a
relatively small subset of the 256 possible EBCDIC characters. Although
there are a number of ways to do compaction, only the algorithm to be
implemented for the POWER/VS SNA support is discussed.
For compaction, you must supply a compaction table to POWER/VS. The
process is relatively simple, but you must know the data to be
transmitted. First, determine the set of all possible characters that
may appear in the data stream. Next, count the number of possible
characters, then using Figure 1-1, match this number with the closest
(but not smaller) number appearing in the first column. The second
coluMn shows how many master characters must be selected for the
corresponding number of compact code characters. If the number of
compact code characters is greater than 247, you should specify no
compaction.
r-----------------------------------------------------------,
Number of Compact
INumber of Kaster
I
I Characters
Code Characters
I
------------------------------------------------------I
247
3
I
240
4
5
231
220
6
207
192
7
8
175
156
135
112
87
60
31
16
9
10
11
12
13
14
15
16
I
I
I
I
I
I
I
I
t
J
I
I
r
I
Figure A-l.
Numbers of Master Characters Related to Numbers
of Compact Code Characters
For example, to choose a master character subset for this appendix, you
would define the possible characters that may occur as shown in Figure
A-2.
Thus you have determined that this appendix may include, up to 85
different characters. In the first column of Figure A-1, the number
closest to 85 (but not smaller) is 87. Now increase the number of
characters in the character set to equal the number from Figure 1-1.
For this appendix, you might choose:
<
>
Less than
Greater than
(X' 4C I)
(X'6E') •
Now, from this character subset, qhoose the m most frequently used
characters, where m is the number of master characters in Figure A-1.
For a large subset of 87, m equals 13. For the m most frequent
characters in this document, you might select:
a, d, e, g, i, 1, n,
0,
r, s, t, u, and blank
Appendix A.
Data Compaction
151
I
,
I Characters
IName
IHex Code
I
1-------------- ---------------------------------------------------1
Cl - C9
IA - I
IJ
IS
fa
Ij
Is
10
-
- i
Uppercase letters
r
Lowercase letters
R
-
-
Dl - D9
E2
81
Z
z
Numerals
Blank
Left bracket
Period
Left parenthesis
Plus sign
Ampersand
Riqht bracket
Doilar sign
Asterisk
Right parenthesis
SeIllicolon
Hyphen
Slash
Comma
Percent
Underscore
Question mark
Colon
Pound sign
At sign
Single quote
Equal sign
Double quote
- 9
1)1
I[
I•
I(
1+
1&
I]
1$
1*
I>
I;
11/
I,
1%
1I?
I:
1#
,1=Iii)'
I"
91
A2
FO
40
AD
4B
4D
4E
50
BD
5B
5C
5D
SE
60
61
6B
6C
6D
6F
-
-
-
E9
89
99
A9
F9
7A
7B
1C
7D
f7E
.-
11F
I
Figure A-2.
Example of Compact Code Set
To define the compaction table for POWER/iS, you can specify the
parameters in the PCPTAB macro as follows:
name
PCPTAB MASTER=(a,d,e,g,i,1,n,o,r,s,t,u,40)
NOMAST1=(A,B,C,D,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S,
T,U,V,W,X,Y,Z,b,c,f,h,j,k,m,p,q,
v,w,x,y,z,0,1,2,3,4,5,6,7,8,9,AD,
4B,4D,QE,SO,BD,5B,SC,5D,5E,60,61,6B,
6C,6D,6F,1A,1B,1C,1D,1E,1F,4C,6E)
The macro PCPTAB builds tables using these parameters. For details
concerning the PCPTAB macro, refer to the section "POWER/VS Gen~ration
Macros" in Chapter 2.
To compress and compact the data stream, POWER/VS performs the
following:
c~aracter
1.
Scans the data, looking for consecutive blank
length 2 or greater.
2.
Scans the data, looking for consecutive duplicate character strings
of length 3 or greater.
152
POWER/VS Installation Guide and Reference
strings of
*
*
*
*
3.
For each string of nonblank and nonduplicate characters, POWER/VS
then checks if any character is not a member of the set of compact
code characters (master or non-master characters). If so, POWE~/VS
creatas a string control byte (SCB) for noncompressed and
noncompacted characters and continues with the next string.
4.
If all characters are in the compact code subset, POWER/VS
translates the whole string to compact code.
Then POWER/VS scans
the string, looking for two consecutive master characters.
Each
time this occurs, POWER/VS compacts the two bytes into a single byte
and continues. A fourth kind of SCB describes the compacted string.
It is important that the compact code subset include all (or almost all)
characters in the data stream. Otherwise, an entire string may not be
compacted.
To illustrate how much reduction can be realized, operate the algorithm
on the sentence for step 2 above using the example for PCPTAB
specifications (as coded before). This character string contains 103
characters, assuming one blank between each word. For step 2, the
following pairs of master characters are found in order:
an,s ,e ,da,ta, l,oo,in,g ,or,on,se,ut,e ,du,li,at,
e ,ar,te,r ,st,ri,ng,s ,l,en,gt, 0, r,gr,ea,te.
There are 33 pairs of master characters.
Potentially, this sentence can
be reduced from 96 characters ~wo SCBs added for nonduplicate character
string with compression only) to 62.
A reduction of about 35 percent.
A discussion follows of how POWER/VS does compression and compaction and
how it builds its tables for compaction and decompaction.
The string control byte (SCB) as defined for SNA is a byte consisting of
a two-bit string identifier and a six-bit count field.
It is defined as
follows:
seB
Bits
Explanation
xxOOOOOO
Reserved.
OOxxxxxx
Noncompressed characters. The SCB is followed by 1-63 data
bytes. The number of data bytes is given by xxxxxx. The
next SCB follows the last data byte.
01xxxxxx
Compact code characters. The SCB is followed by 1-63 bytes.
Each byte may represent two consecutive master characters, or
a single character in the compact code subset; and both kinds
of bytes may exist in the same string. The number of bytes
is given by xxxxxx; and it represents the number of bytes
following the SCB, not the number of data bytes represented
by the string (before compaction). The next SCB follows the
last byte.
10xxxxxX
Duplicate blanks.
The SCB represents 1-63 consecutive blanks
(X'40 ' ). The number of blanks represented is given by
xxxxxx. The next SCB follows this seB immediately.
l1xxxxxx
Duplicate next character. The seB and the character
immediately following the SCB reprpsent 1-63 consecutive
duplicate. characters. The duplicated character is the
character following the SCB. The number of duplicate
characters is given by xxxxxx. The next SCB follows the
duplicated character.
Invalid if present.
Appendix A.
Data compaction
153
If compression is being done but not compaction, SCBs of the form
B'Olxxxxxx' are not valid.
There are two important rules that must be followed for SCBs:
seB
•
An
and its string may not span request unit
(RU) boundaries
•
Compression and compaction operate on byte strings.
There is not necessarily any relationship between the boundaries of an
SCB string and the boundaries of a logical record. A logical record may
begin or end in the middle of an SCB string. In the same manner,
single-character string (SCS) control characters may be compressed as
well as data.
The PCPTAB macro builds a set of compaction tables consisting of 256byte tables - a translate-and-test table for compaction (TRTC), and a
translate table for compaction (XLTC), - and an FaR3 (function
management header) ready for transmission to the work station.
The PCPTAB macro builds the TRTC so that it contains zeros at the
displacements corresponding to each member of the compact code subset,
and nonzero values at all other displacements. The XLTC table contains
meaningful entries only at displacements corresponding to the compact
code subset members. The values at those displacements are such that no
compact code character will translate into a byte whose high-order digit
and low-order digit are less than m, where m is the number of master
characters.
The value for the first master character is always X'FO'. The second
master character gets X'Fl', and so forth, until the master character
subset is exhausted. If the number of master characters is '6, there
are no non-master characters, and the XLTC is then complete. If m is
less than 16, the first non-master character gets X'Fm+", and so forth,
up to X'FF'.
If m is less than 15, the next 16 non-master characters are assigned
X'EO' - XIEF'. If m is less than 14, the next 16 non-masters are
assigned X'DO' - X'DF', and so forth, until the point is reached such
that if X'xO' were assigned to the next non-master, both digits would be
less than m. When that point is reached, the next non-master gets
X'yz', where y=m-l and z=m. The following non-master gets X'yz+", and
so forth, up to X'yF'. The next non-masters get X'y-lz', X'y-1z+1', up
to X'y-1F'. Each time X'yF' is reached, the high-order digit is reduced
by 1, until the last non-master gets X'OF'.
.
Using the example from this appendix, the tables generated with the
PCPTAB macro are as shown in Figures A-3 and A-4. For the TRTC table, a
dash represents any nonzero value. For the XLTC table, a dash
represents any value, because such a character will not occur in the
string.
154
POWER/VS Installation Guide and Reference
.-----
IxO xl x2 x3 x4 x5 x6 x7 x8 x9 xl xB xC xD xE xF
------------------------------------------------,
Ox lx
2x
3x
4x
5x
6x
1x
8x
9x
Ax
Bx
Cx
Dx
Ex
Px
00
00
00
00
00 00 00
00 00 00
00 00
00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -
00 00 00
00 00 00
00 00
00 00 00
Pigure A-3.
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
-
Translate-and-Test Table for Compaction (TRTC)
xO xl x2 x3 x4 x5 x6 x7 x8 x9 xA xB xC xD xE xF
Ox
1x
2x
3x
4x
5x
6x
7x
------------------------------------------------,
FC 3~
-
8x -
9x
Ax
Bx
ex
Dx
Ex
Fx
6D 6E PD
5P 4D 4E
3F 2D 2E
1E 1F FF
FO EO El Fl F2 &2 F3 &3 F4 E4 E5 F5 &6 F6 F7 E7 E8 F8 F9 FA FB E9 EA EB EC ED -
5E -
-
BE EF DO
D7 D8 D9
CD CE
AF 9D 9E 9F
D1
DA
CF
80
D2
DB
BD
8E
03 D4 DS D6
DC DD DE DF
BE BF AD AE
8F 7D 7E 7F
6P
4F
2F
00
50 3D FE 1D
DE OF
-
J
Pigure 1-4.
Translate Table for Compaction (XLTC)
POWER/VS uses the TRTC and XLTC tables in the following way to perform
data compaction:
POWER/VS first scans the data to separate strings of duplicate data from
strings of nonduplicate characters. Then POWER/VS scans the
nonduplicate strings for characters outside the compact code subset
using the TRTC table.
If a character outside the compact code subset is found, POWER/VS does
not attempt to perform compaction.
The string goes into the request
unit as a noncompressed string.
If all characters are members of tne.
compact code subset, POWER/VS translates them to compact code, using the
XLTC table ..
POWER/VS then scans the data, looking for two adjacent
and combines these characters into one byte ..
Appendix A..
m~ster
characters
Data compaction
155
The example below shows how this algorithm works for the following
sentence:
"1. Scans the data, looking for consecutive duplicate character strings
of length 3 or greater."
This would appear in storage (in hexadecimal)
F14B40E2
95874086
8381A385
86409385
838195A2
96994083
40838881
9587A388
40A38885
9695A285
998183A3
40F34096
408481A3
83A4A389
859940A2
99408799
816B4093
A5B54084
A3998995
8581A385
as:
96969289
A4979389
87A24096
994B
POWER/VS would first scan the string, looking for consecutive duplicate
character strings of length 3 or greater.
No such string exists in the
first 63 characters, so POWER/VS would establish the 1 (X'pl') as the
beginning of a non-duplicate string, and the blank (X'40') character
between the words 'character' and 'strings' as the end of the
nonduplicate string. POWER/VS then tests this string, using the example
TRTC table, and finds that all characters are members of the compact
code subset.
POWER/VS then translates the whole string to compact code,
using the XLTC table. The resulting string (first 63 bytes only)
becomes:
9D6EFCCD E1FOp6F9 FCFAE3F2 FCF1FOFA F02DFCF5 F7F7E5F4
F6F3FCE2 F7F8FCEl F7F6F9F2 E1FBFAP4 E9F2FCFl FBE7F5F4
E1FOFAF2 FCE1E3FO F8FOE1FA F2F8FC
Now POWER/VS scans the string, looking for two adjacent master
characters. The target buffer for this example then becomes (first byte
is the SCB) :
6A9D6EFC CDE1Q§2f
92E1~!F4
FAE3l~lQ
!Q2DC577
E91C1BE7 54El0A2C E1E308FO
E5463~E2
78FCE176
E1A28~
The underlined bytes represent two master characters. Thus, 63
characters have been reduced to 43, including the SCB.
156
POWER/VS Installation Guide and Reference
Appendix B. RJE, SNA 1/0 Specifications
This appendix describes the major functions of POWER/VS RJE,-SN A with
respect to the handling of input and output information. Data directed
from a peripheral device to the host system is referred to as inbound
data; information directed from the host system to a peripheral device
is called outbound data.
POWER/VS processes the following types of inbound data:
•
Console data
•
Card data.
In thq outbound direction, the following information can be processed:
•
Print data
•
Punch data
•
Console data.
The following sections discuss the handling characteristics for these
types of data. Additionally, a summary of the support for Data Plow
control (DFe) requests is also provided. Refer to Figure B-4 for a
support summary of the ~OWER/VS RJE,SNA data communication facilities,
to Figure B-5 for a su •• ary of the single character string (SCS) control
characters supported by POWER/VS RJE,SNA, and to Figure B-6 for an
overview of the data stream interruptions supported by POWER/VS for SNA
terminals.
Inbound Console Data
POWER/VS assumes that inbound console data exclusively consists of
commands, and treats this information as such. It deblocks each RU into
aO-byte images using the same scanning algorithm as described later in
the section "Inbound Card Data". Inbound console data may be
transparent or nontransparent; however, POWER/VS does not support
compression for inbound console data.
Inbound Card Data
Inbound card data consists of one or more jobs, delimited either by
DOS/VS JCL job delimiter statements (// JOB and /&) or by POWER/VS JECL
job delimiter statements (* $$ JOB and * $$ EOJ).
Figures B-1 and 3-2
give examples of these two types of inbound card data streams.
Appendix B.
RJE,SNA I/O Specifications
157
I
"1
I II JOB A
I
I
I
I 1&
I II JOB B
I
I
I
Start job
··
·
End job
Start job
··
·
1&
..
** ..
START LST,class
START PUN,class
DISPLAY
RDR,class
* JOB C
II
II EXEC PGM
data
..
1*
1&
End job
See note
Start job
End job
L
Figure B-1.
Inbound Card Data with DOS/VS JCt Job Delimiters
~:
You may enter remote operator commands punched in cards; however,
these will only be recognized and acted upon when they are submitted
between DOS/VS or POWER/VS job boundaries.
*
start job
$$ JOB
*
$$ EOJ
START LST,class
*
START PUN,class
*
DISPLAY RDR,class
* $$ JOB
II JOB A
*
End job
See note
start job
1&
II
JOB B
/ / EXEC PGM
data
1*
1&
*
$$ EOJ
Figure B-2.
158
End job
Inbound Card Data with POWERjVS JBeL Job Delimiters
POWER/VS Installation Guide and Reference
.-
Note:
You may enter remote operator commands punched in cards; however,
these viII only be recognized and acted upon when they are submitted
between DOS/VS or POWER/VS boundaries.
Inbound card data may be transmitted from a card reader or a disk
(optional device on certain work stations). POWEN/VS treats both device
types identically.
If POWER/VS did not encounter a valid job delimiter at the end of
inbound data transmission (that is, either a /& or a * $$ EOJ
statement), it will add the appropriate job delimiter. rhen the job is
placed in the Hold queue, and a message is sent to the originating
remote operator stating the disposition of the job. The operator may
then issue a command to release or to delete this job.
Data from a work station is transmitted in the form of request/response
units (RUs) vhich may be up to 256 bytes long. POWER/VS deblocks each
RU and creates SO-byte card images using the following algorithm:
1.
The first 80 bytes of the RU are scanned for a record delimiter
character) •
2.
If no record delimiter is detected, an interchange record separator
(IRS)
(SCS
is assu.ed to follow the 80 bytes.
3.
If the next (81st) byte is a record delimiter, it is ignored and the
next logical record is assumed to start with the 82nd byte.
4.
If the 81st byte is not a record delimiter, this byte is assumed to
be the first byte of the next logical record.
5.
If a record delimiter is found before the 80th byte, this delimiter
is discarded and the record is padded with blanks to 80 bytes. The
byte following the record delimiter is considered to be the first
byte of the next logical record.
Outbound Print Data
For print jobs, POWER/VS supports the following SCS functions:
•
SELECT CHANNEL nn
•
FORMS FEED
•
CARRIAGE RETURN
•
NEW LINE
These functions are briefly discussed below.
Appendix B.
RJE,SNA I/O specifications
159
r
I
ISELECT CHANNEL nn
(SELnn), X'04nn'l
This command is inserted after a print line if the request vas to skip
to channel nn after printing. The following codes apply:
Hexadecimal
Represtmtation
(see note below)
X' 8,.
X'82'
X'83'
X'84'
X'8S'
X'86 1
1
2
3
4
5
6
7
8
9
10
11
12
X'87'
X 1 88'
X'89'
X'7!'
X'7B'
X'7C'
Note:
If SELOl is specified, this value is converted to, and
transmitted as, the FORKS FEED character (X'OC').
i
•
,FORMS FEED
(FF), X'OC'I
L
This command is transmitted instead of the SELECT CHANNEL 1 command.
,
.
,
,
ICARRIAGE RETURN (CR), X'OD'I
This command is inserted after the print line if the request was to
print with no space.
I
,
I NEW LINE
,
(Nt), X '15'
I
I
This command is inserted before or after the print line depending on
whether the request was to space one line before or after printing.
If
two or more blank lines are r~guested, the appropriate number of NL
commands are inserted.
Notes:
1.
POWER/VS does not support the Select vertical Format (SiF) feature.
Therefore, it is the responsibility of the remote operator to s~t up
the vertical tab tables at the remote work station. However, the
FCB name is sent if PDIR is supported and if the name has been
specified in the * $$ LST or * $$ PRT statement.
2.
The maximum logical record length is 132 bytes.
160
POWER/VS Installation Guide and Reference
Outbound Punch Data
Outbound punch data consists of one or more punch jobs from the output
class specified in the START PUN[ ,class] command by the remote operator.
The punch data stream is transmitted in transparent mode unless ASCII
was specified in the BIND parameters for that work station. Compression
and compaction are not supported for punch output.
Each logical record is ~receded by a TRN byte and a l-byte binary count
indicating the number of bytes of transparent data. Trailing blanks are
truncated so that th~ data count for each record is less than, or equal
to 80 bytes.
An IRS character follows each logical record. The TRN and
the IRS characters are the only two SCS characters supported for punch
output.
Outbound Console Data
Outbound console data consists of messages. The message processor uses
the NL character to properly format each message. The NL character is
the only SCS character used by the message processor.
Data Flow Control (DFC) Requests
Figure B-3 shows the DFC requests supported for both inbound and
outbound SNA support.
I
,
IDFC Request
I Inbound
(Outbound
,
I
I
I
I
I
I
1--------------------------------------1
ICANCEL
IYES
IYES
I
ISIGNAL
IYES
INO
I LUSTA T
I YES
I N/A
ICHASE
ISHUTD
ISHUTC
IRSHUTD
INO
INO
tN/A
INO
IN/A
IN/A
INO
IYES
I
I
Figure B-3.
DPC Request Support for SNA
INBOUND DPC REQUESTS
CANCEL:
CANCEL may be received at any time. If received during inchain-state, POWER/VS will discard the current job being
received, that is, POWER/VS will not place it into the input
queue and will free the resources. A positive response is
sent to CANCEL. If received during between-chain state,
POWER/VS will positively respond to CANCEL but take no
further ,action.
Appendix B.
RJE,SNA I/O Specifications
161
SIGNAL:
SIGNAL indicates a request for change in direction. If
outbound processing is performed, POWER/VS will force the
end-of-chain and send CD with FMH1 indicating suspend.
If POWER/VS is in receive or standby state, SIGNAL will be
ignored. The positive response to SIGNAL is sent by VTA!
automatically.
LUSTAT:
The following LU status codes are supported by POWER/VS:
X'OOOlXXOO' Component now available.
X'OB1CXXOO' Component failure: permanent error for an
outbound device.
where XX = device selection byte of FMH1.
All other codes and conditions will be negatively responded
to, the outbound processor sends ADS (if in DS state) and
terminates.
CHASE:
CHASE is not supported. A negative response indicating
function not supported is returned.
SHUTe:
Shutdown Complete is not supported. This should never be
received as it is only returned in response to SHOTD which is
not sent by POWER/VS.
RSHUTD:
Request Shutdown is interpreted by POWER/VS as a request for
CLEAR, UNBIND when the current active processor completes.
The inbound processor waits for an PM Header indicating Abort
or End Data stream with EB or CD.
The outbound processor completes the sending of the current
job(s) and any pending messages, then terminates the session.
OUTBOUND DFC REQUEST
CANCEL:
162
CANCEL viII be sent by the outbound processor whenever a
negative response is received, and during in-chain-state.
There are no other conditions under which POWER/VS viII send
CANCEL.
POWER/VS Installation Guide and Reference
POWER/VS RJE,SNA
Facilities
IInbound Data
IOutbound Data
I-------------~--------------------------------I Console
Icard
IPrint IPunch I Console
Compression
No
No
Yes(l)
No
No
Compaction
No
No
Yes (1)
No
No
RU Spanning
No
No
Yes
No
No
ASCII Characters
Yes
Yes
Yes
Yes
Yes
Truncate Blanks
Yes (2)
Yes (2)
No
Yes
Transparency
Yes (1)
Yes (1)
No
Yes
1
1
1,2,3
1
FMH Type
(1)
No
Default
and default
----------------------------------------------------------------------
Notes:
1:--rf ASCII is not specified.
2. Depending on the work station.
Figure B-4.
Data Communication Facilities supported by POWER/VS RJE,SNA
i
i
IData Inbound
IData Outbound
Ito Host System Ifrom Host System
IPOWER/VS SNA SCS (Single
Icharacter string) control
Icharacters supported
I
,Character
IValue
New Line (NL)
X'15'
Carriage Return (CR)
X'OD'
Forms Feed (FF)
X'OC'
I
I
IYes
I
IYes
IYes
I
IYes
I
IYes
I
IYes
IYes
I
IYes
I
X' lE'
Select Channel (SEL)
X'04xx',No
Required New Line
(RNL)
Figure B-S.
X'3S 1
X'06'
I
IConsolelPunch
Interchange Record
Separator (IRS)
Transparency (TRN)
,
ICard
I
No
No
No
Yes
r
I
I
INo
I
I
IYes
I
IYes
I
I
I
I
I
IYes
I
IYes
,
No
Yes
No
IPrint
,
IConsolel
IYes
Yes
IYes
t
IYes
No
I
INo
I
I
tYes
I
tNo
I
INo
I
No
No
No
No
No
SCS Control Characters Supported by POWER/VS RJE,SNA
Appendix B.
RJE,SNA I/O Specifications
163
1
Interrupt by
1
IInbound data
I
(Outbound data
I
I
1---------------------------------------1
I Con50le I Card
tPrint IPunch
I Console ,
1------------------------------ ----------------------- ---------------1
,Interrupt
lof
I Inbound data
I
I
I
I
•
Console
I
I
I
•
Card
I
I
Ye5(2)
I
,
•
Yes
Punch
Yes
•
console
No
I
I
I
I
•
•
Print
Punch
No
No
J
IYes
No
I
INO
No
No
I
I
I '
I
I
I No
I
I
I
t
IYes(3)
INa
INo
IYes (2)
t
IYes(1)
'
II Yes
I Yes
No
I
I
I
I
INa
I
INo
I
,
•
I
No
I
Print
IOutbound data already interI rupted by inbound card data
No
I
IOutbound data
I
I
t
I
I
INo
I
,
"
I
No
I
I
I
I
I
I
INa
I
tNo
J---------------------------------------------------------------------I Note§.:
11.
12.
13.
If CONSOLE=YES in PRMT macro.
Function not available for the 3770.
Function not available for the 3110 and 3190.
I
Figure B-6.
164
Data Interruptions Supported by POWER/VS RJE,SNA
POWER/VS Installation Guide and Reference
I
I
Appendix C. LOGON Mode Table and BIND
Parameter Requirements
To use POWER/VS with RJR,SNA, you must have generated VTAn under your
DOSjVS operating system.
This appendix concentrates on the LOGON mode
(LOG~ODE) table to be defined during the VTAM generation.
One entry is
required in the LOGMODE table for each individual group of sessions with
identical VTAM BIND characteristics.
The LOGMODE table, which must be cataloged in the VTAM core image
library (private or system), contains the BIND parameter specifications
as required for each individual group of sessions.
As a remote
operator, you must specify the name of the appropriate entry in the
LOGMODE table when you issue the LOGON command. For details concerning
the BIND parameters in general, refer to the DOS/iS VTA~ System
grogr~~er's_Guiag, GC27-6957.
The following example (FigUre C-1) shows the definition of a LOGMODE
table entry by means of the MODEENT macro.
Note that the continuation
characters that must be specified in column 72 have been omitted in the
example.
,
Byte no. I
in BIND ,
username MODETAB
I
I
I
I
I
I
t
user name MODEENT LOGKOOE=name,
FMPROF=X'03',
2
TSPROF=X'03',
3
4
PRIPROT=X'~3',
=X'A1',
(without compression
(LST,PON»
5
SECPROT=X' A 1 • ,
COKPROT=X'7080',
=X' 7880 .,
6,7
(with ASCII
(3770 only»
RUSIZES=X'858S 1
Figure C-1.
8,9
LOGON Kode Table Coding Example
Figure C-2 shows the BIND parameters for the presentation services to be
used with a 3790 or 3777 work station. The string of 12 hexadecimal
values applies to bytes 14 through 25 of the BIND parameters.
Appendi~
C.
LOGON Mode Table and BIND Parameter Requirements
165
Byte no. in BIND
14
15
16
17
18
19
20
21
22
23
24
25
2
3
4
5
6
7
8
9
10
11
12
PSERVIC=X'
00
20
POI R (information about COpy count, chain, FCB buffer
40
COMPACTION to POWER from 3790
60
POI R + COMPACTION
Figure C-2.
166
00
ROR not allowed (3790 POWER)
40
ROR allowed
00
Print output for 3790
not allowed
80
Print output allowed
BIND Parameters for the Presentation Services
POWER/VS Installation Guide and Reference
Appendix D. Examples of
Status Report Output
This appendix describes two status report examples for the IBM 3800
Printer.
They show the status report output that results when you issue
the PDISPLAY command shown.
In each example, the numbered notes
describe the item indicated with the same circled number on the listing.
Example-1.
If you issue the PDISPLAY command:
d 1st
the status report has the following form:~
First job
Second job
Third job
F1
F1
{ F1
{F1
F1
{F1
IR461
tR461
IR46I
IR46I
IR461
LIST QUEUE
P
C FRO!>l TO
PWR001
00162 3
B 000 000
FLASH=FLSH,BURST,COPIES= 36
PWR002
00170 4 H C 000 000
PAYROLL 00172 8 K P 000 000
IR~LA~YR'COPIE~4
PAGES CC FORM
3 *8 FFFF
518
1 ABeD
~~PA~
1
The name of the output job is PAYROLL, and it has an associated job
number of 172, a priority of 8, a disposition of K (keep), and an
assigned class of P. The job input has been read from a local
reader device, and the output is to be printed on a local printer.
The job output contains 1815 pages.
2
The asterisk indicates that the output file is destined for printing
on a 3800 Printing Subsystem.
3
The output is printed twice (that is, the transmission count is 2).
4
The forms overlay name is PAYR.
5
The total number of copies produced for this job is 4 (although the
output is only transmitted twice across the channel) •
6
The forms number requested for the job is PAYF.
7
"BURST" indicates that the paper must be threaded through the
Burster-Trimmer-Stacker before printing of job PWR001 can be
started.
Ex~~-l.
d
If you issue the PDISPLAY command:
a
the status report has the following form:
Appendix D. Examples of Status Report output
167
F1
F1
F1
IR48I
tR481
IR481
LST,OOE,T
,2
F2,OOC,Ai
JRlC'~~
INACTIVE
IN~IVE
Notes:
1
"RDR" indicates the type of task.
LST
PUN
RDR
BG-F6
Possible types are:
writer task
punch task
reader task
execution task.
2
"OOC" is the unit record device address associated with this task.
3
This position shows the class or classes that can be processed by
the task. The order in which the classes are specified shows the
order of processing.
4
This position indicates the number of buffers used, where:
1
2
D
=
1 print buffer
2 print buffers, 1 input buffer for data file
2 print buffers, 2 input buffers for data file.
5
This identifies the job name and job number of the job currently
being processed when the task is active.
6
This is the job class associated with the job.
7
This indicates that the corresponding task is inactive.
168
POWEP/VS Installation Guide and Reference
Appendix E. Reader Exit Routine
For a user-written reader exit routine, you must consider the following:
POWER/VS performs a conversion to uppercase characters for all POWER/VS
JECL and DOS/VS JCL statements (column 1 to 72) that start with / / in
columns 1 and 2. DOS/VS comment statements and ASSGN statements without
/ / (permanent assignments) will not be translated.
The routine receives control from POWER/VS only for DOS/VS JCL or
POWER/VS JECL statements. It must be reentrant if it is called from
more than one partition; and it must be self-relocating unless the
relocating loader option is in effect.
Any JeL or JECL statement can be changed or deleted and other statements
can be inserted. The original statement is presented again after each
inserted statement has been processed. When all the insertions have
been made, a return cod~ of X'OO' or X'04 1 is placed in register 15 to
accept or delete the original statement.
When the reader exit routine receives control from POWER/VS, register 0
contains the address of the statement read and register 1 the length of
the statement. To return to POWER/VS, issue a BR 14 instruction.
Between entry and exit of this routine, no operation may he performed
that might cause a WAIT condition for the POWER/VS partition.
The user-writtp.n exit routine must not alter the contents of registers
10, 11, 12, and 13. These registers are reserved for POWER/VS internal
use. Register 11 points to the task control block of the read task and
may he used to identify the task.
Before returning control to POWER/VS, you must specify a return code in
register 15. POWER/VS expects one of the following return codes:
XIOO'
Normal return; process this statement.
X'04'
Delete; ignore this statement.
X'OSI
Insert; process new statement, return original statement to the
user.
Any number of statements may be inserted. Preceding every
job control statement that has to be inserted, one byte must be
reserved. This byte is used as an interface with the POWER/VS
message service when the job control statement is incorrect.
X'OC'
Flush the DOS/VS job.
X'10'
Flush the POWER/VS job.
When new statements are added (return code X'OS'), the address of the
must be provide~ in register 0 and its length in register 1.
The length must be XISOI.
stat~ment
Flu~h conditions (return codes XIOC' and X'10') at job boundary (first
card of a POWER/VS job) wi11 be ignored and message lRS7I will be logged.
If ACCOONT=YES was specified, the number of records read in the reader
account record will ,include records added or deleted through the RDREXIT
routine.
If a reader exit was generated and AOTOSTART is to be performed, the
user must return to POWER/VS with X'OOI in register 15.
Appendix E. Reader Exit Routine
169
Bibliography
DO~Lsystem
!t~.!H\9.ement
DOS/VS~tem
Generation, GC33-5377
Guide, GC33-5371
QOS/VS POWERLVS Work station User's Guide, GC33-6049
QQ~L!~_EQ~~RL!~_B~f~~n£~_~Y~~,
GX33-9004
QOSLILPOWERLVS Logic-RYi....1, SY33-8576
DOSL!~~OWERL.YL~Qgic
IBM System/370
~odel
Part 2, SY33-8577
125 Functional Characteristics, GA33-1506
IBM 2701 Data Adapter Unit, GA22-6864
Component DescriEtion: IBM 2780 Data Transmission Terminal, GA27-3005
IBM 3770 Data Communication System, System Components, GA27-3097
Compongnt~2cription
for the
IB~
3780 Data Communications Terminal,
GA27-3063.
Bibliography
171
Index
W?ere more than one page reference is
the major reference is first.
g~ven,
channel selection codes 161
channel 1 skip 90
channel 12
repeated posting of 30
character arrangement table
specification 93
class specification
changing of 138
partition-dependent 138
partition-independent 138
clear the 3800 page buffer 31
CMPACT parameter 36
coding work sheet 42,43
compact code 151
example of 152
compaction
151
compaction rules 40
compaction table 151,36
definition of 152
generation 38
identification 38
name 39
phase name 40
storage 15
component selection (on IBM
3780)
37
compression 154
of nonduplicate characters 151
COMPROT parameter 165
conditional termination 145
CONSOLE parameter
restrictions 36
for single logical units 36
for multiple logical units 36
for the 3790 36
copy count display 60
copy group index 68
copy groups (IBM 3800)
89
copy modification (IBM 3800)
95
copy separator pages/cards 31,83,98
correction of JECL statements
dUring job execution 71
* $$ LST 85
* $$ PRT 85
* $$ PUN 95
$JOBACCT phase 123
*abc operand
in PALTER 55
in PDELETE 58
in PDISPLAY 61
in PRELEASE 67
// EXEC statement 21
ACB
(§g~ application control block)
account file 116,2
formattinq of 133
size of i3
account records 116
adding resources 9
additional extents for data
file 132
adjusting forms alignment 69
algorithm for RO deblocking 159
alignment of forms 69
ALLOC 21
allocation of storage 130,7
ALLOCH 21
ALLUSERS
message processing 57
parameter 57
application control block 143
ASCII 33
attention routine commands 51
automatic start-up 126
AUTONAME 82
AUTOSTART facility 126,130
.AUTOSTART feature 51
AUTOSTART statements
errors in 126
example of use 134,135
FORMAT 126
PRINTERS 127
PITNCHES 128
READER
127
sequence of 135
BIND parameters for presentation
services 166
bit settings for ICA line mode 49
breakdown 7
broadcast message text lenqth 57
BSC line 142
BSC terminals 2
buffer expansion 37
. additional 37
Burster-Trimmer-Stacker (IB! 3800)
calculation of GETVIS pool
size 30
carriage control tape 90
carriage return command 161
central operator commands 51
short from of 51
central operator functions 5
changing attributes of
POWER/VS jobs 54
93
(~~ carriage return command)
cross-partition communication 22,51
macros 106,4
return codes 115
CTLS~OOL macro
112,29
NEWVAL parameter in 114
request code specification in 113
restrictions 4,112
use of 136
use of operator commands in 114
data block size
assumtions 26
for IBM 3211 printers 26
for tape or disk interme1iate
storage 26
Index
173
data compactio~
151,56
example 152,154
data-driven output segmentation 85
data file 2
additional extents 132
block size 12
entries in 7
formatting of 133
track group size 13
data flow control request 157
inbound
162
outbound
163
!=':upport of
162
data mode 100,148
data stream interruptions 164,157
d~blocking of RUs, algorithm
159
default priority 27
defaults for IBM 3800 94
defining RJE,BSC lines 32
DFC request
(see data flow control request)
direct access storage devices
support of 2
djrection of RJE job output 7
diskette files 100
in SYSIN mode
147
in Data mode
148
diskette unit 147
display of copy count 60
DOS/VS
~CL statements, conversion of
79
procedure library 134
special considerations 22
supervisor generation
requirements 22
dual code feature (IBM 2701)
33
dual communication interface
(IBM 2701)
33
dummy devices 135
dumn 146
EBCDIC 33
eject-and-feed option 101
emergency termination 146
entering POWER/VS commands 136
EOJ operand of PSTOP 73
errors in AUTOSTART statements
126
example
of AUTOSTART procedure 134,135
of POWER/VS initiation 130
of POWER/VS status report
132
FCB
(§22 forms control buffer)
FF
(2~e forms feed command)
file verification
101
fixable area 14,15
frashing forms overlays 94
flushing reader task 64
flushing writer task 64
with several output copies
FMPROF parameter 165
FOPT macro
XECB specification in 22
174
64
format
or central operator commands
of JFCL statements 77
FORMAT statement 126
formatting POWER/VS files 133
forms alignment 69
forms control buffer 91,27
forms feed command 160
forms overlay (IBM 3800)
9q
forms specification 88
52
generating DOS/VS supervisor 22
generating POWER/VS 24
GETSPOOL macro 111,29
LINENO parameter 112
required queue entry disposition
GETVIS area 14,16
GETVIS pool size
calculation of 29
horizontal format control
37
I/O trace 37
IB/Il 2560 49
I~M 2770
required features 44
supported features 45
supported I/O units 44
transparency feature 45
IBM 2780
required features 45
supported features 45
transparency feature 46
IBM 3525 50
IBM 3540 diskette I/O unit 147
IBM 3741
compatibility with IBM 2780 46
r~quired features
46
IBM 3771 46
attachable devices 46
IB~ 3773
46
integrated diskette 46
IBM 3774 47
attachable devices 47
IRM 3775 47
attachable devices 47
IBM 3776 47
attachable devices 47
IBM 3780
components 48
required features 48
supported features 48
transparency feature 48
IBM 3790 49,9
attachment to host system 49
logical devices 49
RJE work station package 49
IBM 3800
JECL statement parameters 89,93
POWER/VS generation parameters 31
support 50
IBM 5425 49
POWER/VS Installation Guide and Reference
111
-
ICA line mode
bit settings 49
ICRXECB 107,109
improving system efficiency 9
INACTIVE status 66
inbound card data
characteristics 151
interruptions 164
inbound console data
characteristics 157
interruptions 164
inbound data 151
initiating POWER/VS
129
with AUTOSTART 134
without AUTOSTART 130
inserting diskette files
100
installation planning 10
installation prerequisites 10
installing POWBR/VS 10
interchange record separator
150,162
intermediate storage requirements 11
IOTAB macro
specification of LUB entri~s in 22
IRS
(§ee interchCl.nge record separator)
ISTLINK7 2lJ
JECL
(see job entry control language)
JECL commands 136
JECL delimiter statements
end of job 105
end of jobstep 105
JECL functions 71
JRC'L .statements
* $$ CTL 81
* $$ DATA 81
examples 103,104
* $$ EOJ 82
* $$ JOB
positional 82
keyword 83
* $$ LST
positional 85
keyword 86
* $$ PRT
pOSitional 85
keyword 86
* $$ PUN
positional 95
keyword 96
* $$ RDR
. positional 100
keyword 100
* $$ SLI 101
examples 103,104
execution-time corrections 17
format of 11
functions of 77
keyword parameters 78,80
positional parameters 78,80
restrictions 80
summary ··19
use of 79
job accounting 116,51,4
job control 3
job delimiter statements
DOS/VS job control 157,75
POWER/VS JECL 157,15
job entry control language 51,15
job execution 3
job input 3
job names
one-character names 83
restrictions 83
job output 3
job segmentation 29
job separation 28,88,98
length of broadcast message text 57
parameter in GET5POOL 111
lin1c-editing NCP modules
job stream 24
list queue entry 85
list task
140
local unit record I/O devices
support of 2
LOGGED ON status 66
LOG~IN~ ON status
66
logical boundaries for segm~ntation 124
logical reader 9
logical printer 9
logical punch 9
logjcal unit 143
logical unit name storage 15
logical unit buffe~ limit 23
logical unit names
avoiding names EOJ and ALL 23
LOGP!ODE 165
LOGON mode table 165
coding example 165
LOGON storage 15
LOSTERM exit 144
LST operand
use for different ~eports 92
LIN~NO
tu
(~
logical unit)
machine requirements 10
macros
accounting support 123
cross-partition communication 106
POWER/VS generation 24
segmentation 124
mark form function (IBM 3800)
31
master characters (compaction)
number of 39,151
range 151
rules 40
selection of 151
special characters 40
maximum resource requirements 9
minimum storage requirements 9,10
MLU
(see multiple logical unit)
Index
175
KODEENT macro 165
mUltiple chann~l 12 posting 30
multinurpose UR devices 134
interrupting operations on
1~6
restarting interrupted operat10ns
multivolume files 89,148
147
NCP
(§~~ network control program)
NCP requirements 23
nested SLI statements 106
network control program 8
new line command 161
NL
(~ new line command)
NOLOG option 75
non-master characters (compaction)
rules 40
number of 40
special characters 40
normal termination 145
NOT INITIATED status 66
NOT LOGGED ON status 66
NOT SUPPORTED status 66
outbound console data
characteristics 161
interruptions 164
outbound data 158
outbound print data
characteristics 159
interruptions 164
scs functions supported 160
outbound punch data
characteristics 161
interruptions 164
output segmentation 12Q,51
count-driven 4,75
data-driven 4,85
program-driven 4
output spooling to tape 89,98
39
PCPTAB macro 38
PDELETE command 58
examples 59
use in CTLSPOOL macro 114
PDISPLAY command 59,138
copy count indication
for active task 60
for inactive task 60
examples 63
items displayed 59,60
status report 59
example of 167
use in CTLSPOOL macro 114
PEND command 63
examples 63
requesting status report 63
permanent area 14,15
PFLUSH command 64
examples 65
PGO command 65,69
examples 65
phase name of compaction table 39
PINQUIRE command 66
example 67
restriction for short form 66
status information 66
planning the installation 10
PLINE macro 32
aDplicability 25
POCL
(§g~ control operator commands)
POWER macro 25
POWE~/VS
command 53
examples 54
pageable area 14,16
P~LTER command
54
examples 56
use in CTLSPOOL macro 114
partition priority 1
password
overridina of 33
oassword definition
.
in POWERjVS generation 33
during POWER/VS execution 33
password specification
~
in PLINE macro 143
in PSTART command 143
PBRnCST command 57
examples 57
length of message text 57
PCANCEL command 58
use in CTLSPOOL macro 114
P~CCOUNT
176
POWER!VS Installation Guide and Reference
account file
123
accounting support 22
AUTOSTART 126
central operator commands 51
format of 52
concept 3
files 2
initiation
with AOTOSTART 134
without AOTOSTART 130
initiation statements 131
example 131
installation 10
job
.
end 82
start 83
major functions 6
partition
changing priorities of 136
structure of 14
phase names 41
queues
manipulation of 1
operator control of 1
requirements in DOS/VS 7
RJE task 142
status report example 132
storage allocation 130
storage requirements 13
task
POWER/VS (continued)
dctivation of 13~
deactivation of 140
terminal sunport 44
termination
emergency 146
normal
145
POWER/VS application name
specification for VTAM 30
POWE~/VS generation macros
24
coding conventions 24
macro sequence 32
examples 38
PRELEASE command' 67
examples 68
use in CTLSPOOL macro 114
presentation services 165
BIND parameters for
166
PRESTART command 68
backward/forward count in 68
example 68
page definition 68
PRINTERS statement 127
priority 1,136
PRIPROT parameter 165
PRMT macro 33,25
short form of 35
PROCRSSING status 66
proqramming systems 8
required 8
optional 8
PSETUP command 69
adjusting forms alignment 69
example 69
page definition 69
PST~.l?T command
70
bUffers 70
examples 72
long-running jobs 71
segmentation 71
Use of
133
verifying diskette files 12
volume sequence checking 72
PSTOP command 73,140
ROJ ooerand 73,141
examples 74
RESTART operand 73,141
punch task
140
PUNCRES statement 128
PUTACCT macro 123
e~ample of
123
PUTSPOOL macro 29,109
gueue entries
creation of 7
queue file 2,13
formatting of 133
size of 11
queue management commands
136
RDREXIT phase
14
reader exit
conventions 169
parameter 29
return codes 169
user-written task 29
READER statement
127
rearler task
139
reader-only partition
127,128
real partition size 14,16
REF parameter
to use short PRMT from 35
restrictions 35
errors in referenced PRMT 35
remote control block 15
remote job entry 7,51,142
devices 2
remote operator command lanquage 137
repeated posting of channel 12 30
request/response unit 159
requested operation for CTLSPOOL 113
requesting display
of active tasks 62
of ALLUSERS messages 62
of fr~e queue records 62
of system messages 62
of time and date 62
resource reguirements 9
RESTART operand of PSTOP 73
restarting
flushed writer task 64
partition 139
return codes
from PUTSPOOL, GETSPOOL, CTLSPOOL 115
from reader exit task 169
from SEGMENT macro 125
returning partitions
to DOS/VS control 142
to POWER/VS control 142
RJE
(§gg remote job entry)
RJE job output
direction of 7
RJE task lU2
RJE,BSC operations
control of 1£13
RJE,SNA facilities 163
~JE,SNA operations
control of 1£14
R~JE,SNA session
start-up 143
termination
145
R'''E,SNA support
NCP requirements 23
SIZE parameter requirement 132
specification in POW~R macro 29
VTAM requirements 23
RMCB
(~ remot'e control block)
Index
177
ROCL
(~
remote operator command language)
RSIZR
11,13
RU
(§g~ request/response unit)
RU deblocking algorithm 159
RUSIZES parameter 165
SCB
(§~~
string control byte)
SCS
(~ single character string)
SCS control characters 163,154
SDLe'
(§g~ synchronous data link control)
SDLC terminals 2
secondary logical unit names 36
SECPROT parameter 165
SEG~ENT macro
124
return codes 125
segmentation boundaries 124
segmentation of output 4
select vertical format 160
SELOl
160
separator pages/cards
copy. separation 31,B8,98
job separation 28,88,98
sequence of AUTOSTART statements 135
SESSLIM parameter 36
SETDP operator command 85
SETPRT macro 4,125
sign on 143
simplified LOGON procedure 23
single character string 154
SIZE parameter (in / / EXEC)
9,132
short form
of central operator commands 52
of PRMT macro 35
SLI update statements 81,101
SNA
(§gg system network architecture)
S~A logical unit
22
SNA support 1
SNA terminals 143
SNA unit control block 15
source statement library 81
reserved sublibraries 102
search sequence 101
space calculation
for SNA control blocks 15
space compression/expansion 37
SPL
(~2 spool parameter list)
SPL DSECT 107
SPL macro 107
SPL TYPE=MAP requirement 106
SPMXECB 106,109
SPOOL interface 29
spool parameter list 107
DSECT 107
178
spool parameter list definition
in CTLSPOOL macro 113
i~ GETSPOOL macro
111
in PUTSPOOL macro 109
spooling 1
spooling to tape 89
START command
use of 131
starting lines 142
status report 145
example
132
stopping lines 141
storage allocation 1,21,130
storage calculation
base values 16,17
example 18
storage requirements, m1n~mum 9
string control byte 153,156
sublibrary 27
SUCB
(~ SNA unit control block)
StJPVR macro 22
SVP
(§~ select vertical format)
synchronous data link control 143
SYSIN files
on diskette 72
SYSIN mode 100,147
SYSRDR assignment
131
system breakdown 7
system dispatching priority 7
system dump 146
system network architecture 7
system requirements 9
tailoring DOS/VS 7
task management commands 136
teleprocessing facility 7
terminal attachment requirements
for Bse 10
for SNA 11
terminal commands 51
terminals
support of 2
termination of POWER/VS
emergency 146
normal
145
termination of SNA sessions
all sessions 145
by central operator 145
conditional 145
individual sessions 144
unconditional 145
timeout 32
track group 27
translate table for compaction 154
example 155
translate-and-test table for
compaction 154
example
155
POWER/VS Installation Guide and Reference
transmission code 33
transparency 163
transparency feature 33,37
TRN
(~
transparency)
TRTC
(sgg translate-and-test table for
compaction)
TSPROF parameter 165
UCB
(§gg universal character set buffer)
unconditional LOGOFF 145
unit-record devices
support of 2
universal character set buffer 91
user exit
(~ reader exit)
user information
in *$$ JOB statement 84
user partition 138
user responsibilities 7
using POWER/VS 51
USS tailoring services 23
V~RY command
144
Virtual" Telecommunications
Access Method 8,143
VM/370 8
volume sequence checking 101
VSIZE 14
VTAM
(§~ Virtual Telecommunications
T\ccess Method)
VTA~ requirements
23
VTAM interface
activating 72
deactivating 74
partition priority 143
WACB
(2~ work area control block)
warm start 7,133
work area control block 15
work sheet for POWER/VS generation
work station package 49
writer task 140
writer-only partition 127
WSP
(2ee work station package)
42,43
XECB specification
for cross-partition communication
XF,CBTAB macro 106
XLTC
(2~ translate table for comnaction)
29
Index
179
READER'S COMMENT FORM
GC33-6048.1
DOS/VS POWER/VS
Installation Guide and Reference
Please comment on the usefulness and readability of this publication, suggest additions and deletions, and
list specific errors and omissions (give page numbers). All comments and suggestions become the property
of IBM. If Y0L; wish a reply, be sure to include your name and address.
COMMENTS
THANK YOU FOR YOUR COOPERATION
PLEASE FOLD ON TWO LINES, STAPLE AND MAIL
GC33-6048-1
YOUR COMMENTS, PLEASE
Your comments on the other side of this form will help us improve future editions of this publication.
Each reply will be carefully reviewed by the persons and department responsible for writing and publishing
this material.
Please note that requests for copies of publications and for assistance in utilizing your IBM system should
be directed to your IBM representative or the IBM bran~h office serving your locality.
.
..
• • • • • • • • • • • ·1 . . . . . . . . . ' . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
0
0
en
---en<
"'U
0
:E
m
::0
---<
CJ)
IBM Program Product Center
Publications Department (0446)
Schwertstrasse 58
::I
c
a.
(tI
Germany
til
:J
a.
::0
(tI
......
(tI
-.
(tI
::I
(')
(tI
.
. t._ ....................................................................................................... .
)
"'U
....
~
(tI
a.
:J
C
en
»
G>
(')
w
w
0,
--- ------ ----- --- --
0
-
-~-.~
,J::.
...
r:p
GC33-6048-1
/---
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.3 Linearized : No XMP Toolkit : Adobe XMP Core 4.2.1-c043 52.372728, 2009/01/18-15:56:37 Create Date : 2012:05:30 14:12:17-08:00 Modify Date : 2012:05:31 04:49:31-07:00 Metadata Date : 2012:05:31 04:49:31-07:00 Producer : Adobe Acrobat 9.51 Paper Capture Plug-in Format : application/pdf Document ID : uuid:b5917d42-71e7-44be-a3aa-11fbd45e95e8 Instance ID : uuid:5746b883-d354-4850-93fe-cdc13fa6e341 Page Layout : SinglePage Page Mode : UseNone Page Count : 187EXIF Metadata provided by EXIF.tools