RMS/Online Reference Guide

RMS/Online Reference Guide
R MS /On l i n e
V11.35
—
Te chnical Reference
RMS™ is a software product of Mantissa Corporation. All rights are reserved. Reproduction of, use of, or distribution of, this
documentation is prohibited unless written consent is obtained from Mantissa Corporation. This document contains
proprietary information and is intended for use only by licensees and those evaluating potential use of RMS in their respective
operating environment.
ADMS, Advanced Datacenter Management Solutions, AOM, Advanced Output Management, ASO, Advanced Systems
Operation, RMS/Spool, RMS/DeskTop and Mantissa Directions are trademarks of Mantissa Corporation.
Mantissa, the Mantissa logo, THE REPORT MANAGEMENT SYSTEM, RMS, RDMS, QSERV, RMS/ONLINE, RDMS/
SOFTCOPY, RMS/DESKTOP, OPS/MASTER, JOB/MASTER, RUN/MASTER, and CONSOLE/MASTER are registered
trademarks of Mantissa Corporation.
All other company and product names are trademarks or registered trademarks of their respective companies and should be
treated as such.
Copyright © Mantissa, Corporation 1983-2013
Publication Information
Publication Name:
Publication Number:
RMS Release:
Original Publication Date:
P/N:
RMS System Reference Manual
0013.00a
11.35
September, 1997
RMS012
Revised:
Sunday, November 24, 2013
RMS/Online® Version 11.35
Table of Contents: The Report Management System
System Reference Guide
TABLE OF CONTENTS
Table of Contents
Chapter 1
THE REPORT MANAGEMENT SYSTEM
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
Introduction .................................................................................................................................... 25
Historical Perspective on Report Management Systems ............................................................................25
High Performance RMS Characteristics .....................................................................................................26
Functional Component Capabilities ............................................................................................................27
RMS/Online ..........................................................................................................................................27
RMS/Spool ...........................................................................................................................................27
RMS/DeskTop ......................................................................................................................................29
RMS/DeskTop Makes Reports Useful ..........................................................................................29
RMS Architecture .......................................................................................................................................31
What is the repository? .........................................................................................................................31
What are the limits? ..............................................................................................................................31
What is the Controller? .........................................................................................................................32
What is stored in the repository? ..........................................................................................................33
How is the repository managed? ..........................................................................................................33
How is report data placed in the repository? ........................................................................................33
Subsystem Interface (MVS) ...........................................................................................................33
External Writer Interface ...............................................................................................................34
How does the user access the report information? ...............................................................................34
RMS Capabilities ........................................................................................................................................34
Administrative Services ........................................................................................................................34
Distribution Definition .........................................................................................................................35
Packaging Capabilities .........................................................................................................................35
Media Control .......................................................................................................................................35
Report Viewing .....................................................................................................................................36
Report Printing and Reload ..................................................................................................................36
Archive / Recovery ...............................................................................................................................37
Help Facilities .......................................................................................................................................37
Report Processing Cycle .............................................................................................................................38
Capture ..................................................................................................................................................38
Distribution Definition .........................................................................................................................39
Index for Base Datasets ........................................................................................................................39
Archive Retention-based for Base Datasets .........................................................................................39
Distribution ...........................................................................................................................................39
Index for Distributed Datasets ..............................................................................................................40
Archive for Distributed Datasets ..........................................................................................................40
Viewing / Printing / Recovery / Reload for Distributed and Base Datasets .........................................40
© 2013 Mantissa Corporation. All rights reserved.
3
Table of Contents: Report Data Capture
RMS/Online® Version 11.35
System Reference Guide
TABLE OF CONTENTS
Index Maintenance for Distributed and Base Datasets .........................................................................40
Archive Demand for BASE Datasets ...................................................................................................40
Purge Storage space release ..................................................................................................................40
Operating Environment ...............................................................................................................................40
Software Requirements .........................................................................................................................40
Hardware Requirements .......................................................................................................................41
Chapter 2
REPORT DATA CAPTURE
Placing Reports in the RMS Repository .....................................................................................................43
Assigning Meaningful Names to report datasets ..................................................................................43
How Repository Attributes Are Assigned ............................................................................................44
Data Capture Schematic .......................................................................................................................46
Capturing Report Datasets with the Subsystem Interface ....................................................................47
Specifying Capture Criteria ...........................................................................................................47
Selection Attributes ........................................................................................................................47
Completing Selection Fields ..........................................................................................................48
Attributes To Be Assigned .............................................................................................................48
Capturing JOBLOG Datasets .........................................................................................................50
Capturing Report Datasets with the External Writer Interface .............................................................50
Method 1 - Routing Individual SYSOUTS ....................................................................................51
Routing SYSOUT to RMS and Assigning Unique Names: ....................................................51
in //ddname1 statement: ..........................................................................................................51
Method 2 - Routing All SYSOUT Data for a Job ..........................................................................51
Routing All Job SYSOUT to RMS .........................................................................................51
in //jobname statement .............................................................................................................52
in //ddname statements ............................................................................................................52
RMS Controller ...........................................................................................................................................52
Overview ..............................................................................................................................................52
Task / File Relationship Schematic ......................................................................................................54
Specifying Options ...............................................................................................................................55
Starting, Modifying, and Stopping the Controller Task .......................................................................57
Task Initiation ................................................................................................................................57
Task Processing Criteria Modification ..........................................................................................58
Task Termination ...........................................................................................................................59
SYSOUT Selection ...............................................................................................................................60
Log File Management ...........................................................................................................................60
MVS ...............................................................................................................................................60
VSE ................................................................................................................................................60
Chapter 3
4
© 2013 Mantissa Corporation. All rights reserved.
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
Quick Start Checklist ..................................................................................................................... 43
RMS/Online® Version 11.35
Table of Contents: Implementation Strategy
IMPLEMENTATION STRATEGY
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
Overview ......................................................................................................................................... 61
Administrator Responsibilities ....................................................................................................................61
Determining Report Management Requirements .................................................................................61
Planning a Managed Report Environment ............................................................................................62
Report Management Database ..............................................................................................................62
System Security ....................................................................................................................................62
Repository Management .......................................................................................................................63
Distribution Capabilities .............................................................................................................................63
Consolidation of Reports ......................................................................................................................63
Copy Variation .....................................................................................................................................63
Priority Output ......................................................................................................................................63
Sending Reports ....................................................................................................................................63
Assignment Of Specific Output Attributes ...........................................................................................63
Data Stream Insertion ...........................................................................................................................63
Deletion of Unwanted Report Data ......................................................................................................64
Selection of Total/Control Data Pages .................................................................................................64
Production Of Output Separators .........................................................................................................64
Media Control - Softcopy, Desktop, Hardcopy, etc. ............................................................................64
Steps in Creating a Distribution Definition .................................................................................................64
Step 1 - Obtaining the Necessary Information ...............................................................................64
RM80004 Sample Job Control ................................................................................................64
Class and/or destination ID serviced by the External Writer ..................................................64
Step 2 - Selecting a Group of Reports ............................................................................................65
Identifying a Distribution Report Group .................................................................................65
First Time Users - Selecting a Benchmark Group ...................................................................65
Step 3 - Capturing Selected Sysout Datasets .................................................................................65
Report Creation for OS/MVS ..................................................................................................65
Report Creation for VSE .........................................................................................................66
Step 4 - Determining Distribution Requirements ..........................................................................67
Interview Sessions ...................................................................................................................68
Report Ownership ....................................................................................................................68
Report Breakdown ...................................................................................................................68
Special Handling .....................................................................................................................68
Output Media Format ..............................................................................................................68
Distribution Hierarchy Definition ...........................................................................................68
Step 5 -Producing Report Maps .....................................................................................................69
Step 6 -Entering the Distribution Instruction Set ...........................................................................69
Base Dataset Names ................................................................................................................69
Define Distribution Requirements ...........................................................................................69
Maps of the Reports .................................................................................................................69
RM80004 Processing Summary ..................................................................................................................70
RM80004 Processing Flow .........................................................................................................................70
Scan Phase ............................................................................................................................................71
© 2013 Mantissa Corporation. All rights reserved.
5
TABLE OF CONTENTS
System Reference Guide
Table of Contents: Implementation Strategy
RMS/Online® Version 11.35
TABLE OF CONTENTS
Principle 1. Page Delineation .........................................................................................................71
Principle 2. Determination of Ownership ......................................................................................71
Principle 3. Ownership Information Location ...............................................................................71
Principle 4. Report Identification ...................................................................................................71
Principle 5. Page Ownership ..........................................................................................................71
Principle 6. Output Sequence Determination .................................................................................72
Order Phase ...........................................................................................................................................73
Output Phase .........................................................................................................................................73
Distribution Instruction Sets. ......................................................................................................................73
The RMS Distribution Definition Facility ............................................................................................73
Instruction Set Records - A Functional Description .............................................................................73
Distribution Options .......................................................................................................................74
Copy Control ..................................................................................................................................74
Send Report ....................................................................................................................................74
Translate .........................................................................................................................................74
Package Control .............................................................................................................................74
Dataset Selection ............................................................................................................................74
Report Definition ...........................................................................................................................74
Explicit Definition ...................................................................................................................74
Implicit Definition ...................................................................................................................75
Creating A Distribution Definition .............................................................................................................75
RMS/DD Transactions .........................................................................................................................75
Terminology .........................................................................................................................................76
Step by Step ..........................................................................................................................................77
Access Authorization Panel ...........................................................................................................78
Primary Menu Panel .......................................................................................................................79
RMS/Distribution Definition Primary Menu Panel .......................................................................80
Distribution Options Panel .............................................................................................................81
Media Production Priorities .....................................................................................................81
ORD(er) ...................................................................................................................................81
Recipient Field - Name/Length/Notes .....................................................................................82
Distribution Options Panel (continued) .........................................................................................82
General Options .......................................................................................................................82
RMS/Online Options ...............................................................................................................83
Process Code Options ..............................................................................................................84
Mapping Options .....................................................................................................................84
Custom Report Definition Panel ....................................................................................................85
Recognizable Characteristics: .................................................................................................85
Report Recognition Information ..............................................................................................87
Recipient Field Line Column/Coordinate ...............................................................................88
Send Report Panel ..........................................................................................................................90
Dataset Selection Panel ..................................................................................................................91
Process Code/Condition ..........................................................................................................92
FCB Requirements Summary ........................................................................................................93
Custom Packaging Panel ................................................................................................................94
6
© 2013 Mantissa Corporation. All rights reserved.
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
System Reference Guide
RMS/Online® Version 11.35
Table of Contents: Repository Management
Output Priority Panel .....................................................................................................................96
Recipient/Location Equate Panel ...................................................................................................97
Auto Report Definition Panel ........................................................................................................98
Content/Recipient Conversion Panel .............................................................................................99
Recipient/Recipient Convert Panel ..............................................................................................100
Automatic Packaging Panel .........................................................................................................101
Data Insertion Panel .....................................................................................................................103
Insertion Information ...................................................................................................................105
Testing Your Instruction Set .....................................................................................................................106
Testing is performed at several levels. .........................................................................................107
Instruction Set Reorganization ..................................................................................................................107
Set Reorganization Panel .............................................................................................................108
Chapter 4
REPOSITORY MANAGEMENT
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
Concepts ....................................................................................................................................... 109
Types of Repository datasets ....................................................................................................................109
RMS Archive Types ..................................................................................................................................110
Base Archive Creation / Life Cycle ....................................................................................................110
Packet Archive Creation / Life Cycle .................................................................................................111
Retention-Based Archive Creation / Life Cycle .................................................................................112
FileSet Backup and Restore ......................................................................................................................112
RM90007 (Backup) Processing ..........................................................................................................112
RM90008 (Restore) Processing ..........................................................................................................113
Recommendation ................................................................................................................................113
Daily Backup / Restore ................................................................................................................113
Weekly and/or Monthly Backup / Restore ...................................................................................113
Repository Sharing among Filesets ...........................................................................................................114
RM80001 - Base Dataset Management Utility .........................................................................................115
Guide to Commands ...........................................................................................................................115
System Facilities .................................................................................................................................115
Typical uses: ................................................................................................................................116
RM80001 Use ...........................................................................................................................................116
Selecting Datasets ...............................................................................................................................116
Archive Scheduling ............................................................................................................................117
RM80001 Control Statements ...................................................................................................................117
Notation Conventions .........................................................................................................................117
Control Statement ...............................................................................................................................118
Types ............................................................................................................................................118
Option ....................................................................................................................................118
Select .....................................................................................................................................118
Order ............................................................................................................................................118
Syntax ...........................................................................................................................................118
© 2013 Mantissa Corporation. All rights reserved.
7
TABLE OF CONTENTS
System Reference Guide
Table of Contents: Repository Management
RMS/Online® Version 11.35
TABLE OF CONTENTS
Parameters ....................................................................................................................................118
Continuation .................................................................................................................................119
Command Descriptions ......................................................................................................................119
INSERT*DATA*STREAM ........................................................................................................119
INSERT*DATA*STREAM PARAMETERS .............................................................................119
Optional Parameters ..............................................................................................................119
Notes on INSERT*DATA*STREAM .........................................................................................121
OUTPUT*CONTROL .................................................................................................................121
OUTPUT*CONTROL Command Summary ...............................................................................121
OUTPUT*CONTROL PARAMETERS ......................................................................................122
Required Parameters ..............................................................................................................122
Optional Parameters ..............................................................................................................122
RUN*MODE (ARCHIVE Mode) ................................................................................................123
RUN*MODE Command Summary (ARCHIVE Mode) .............................................................124
RUN*MODE PARAMETERS ....................................................................................................124
Required Parameters ..............................................................................................................124
Optional Parameters ..............................................................................................................124
RUN*MODE (RECOVER Mode) ...............................................................................................124
RUN*MODE Command Summary (RECOVER Mode) .............................................................124
RUN*MODE PARAMETERS ....................................................................................................124
Required Parameters ..............................................................................................................124
Optional Parameters ..............................................................................................................124
RUN*MODE (RETRIEVE Mode) ..............................................................................................124
RUN*MODE Command Summary (RETRIEVE Mode) ............................................................124
RUN*MODE PARAMETERS ....................................................................................................125
Required Parameters ..............................................................................................................125
RUN*OPTIONS ..........................................................................................................................125
RUN*OPTIONS Command Summary ........................................................................................125
RUN*OPTIONS PARAMETERS ...............................................................................................125
Required Parameters ..............................................................................................................125
Optional Parameters ..............................................................................................................125
Notes on Process Codes: .......................................................................................................126
Select ............................................................................................................................................126
select Command Summary .......................................................................................................................127
Select PARAMETERS ..............................................................................................................................127
Required Parameters ..............................................................................................................127
Optional Parameters ..............................................................................................................127
RM80001 Control Statement Examples ....................................................................................................129
OS/MVS Command Examples ..............................................................................................129
File Create Examples ...................................................................................................................129
Specific Report Retrieval ......................................................................................................129
Specific Report Retrieval Qualified by Destination and Forms ............................................129
Specific Report Dataset Retrieval by Class and Form Identifier; User Exit Output .............130
Generic Report Retrieval. Qualified. Print Image Tape Output. ...........................................130
“ALL” Generic Retrieval. Print Image Tape Output .............................................................130
8
© 2013 Mantissa Corporation. All rights reserved.
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
System Reference Guide
RMS/Online® Version 11.35
Table of Contents: System Administration
Obtain an Alphabetical Cross Reference Listing of the Entries in the Repository ...............130
Report Archive Examples ............................................................................................................130
Generic Archive .....................................................................................................................131
Archive and Purge .................................................................................................................131
Specific Archive ....................................................................................................................132
Report Recovery ........................................................................................................................................132
Specific Report Recovery with Reload to repository. ...........................................................132
Multiple Report Recovery .....................................................................................................133
Additional Command Examples ..................................................................................................133
Microfiche File Create Examples ..........................................................................................133
Generic Report Retrieval .......................................................................................................134
Obtain an Alphabetical Cross Reference Listing of the Entries in the Repository ...............134
BASE Dataset Archive Examples .............................................................................................................134
Generic Archive .....................................................................................................................134
“ALL” Archive ......................................................................................................................134
Specific Report Archive ........................................................................................................135
Report Recovery ........................................................................................................................................135
Specific Report Recovery ......................................................................................................135
Report Recovery Using List Attribute Record ......................................................................135
Multiple Report Recovery .....................................................................................................136
Recreating an Archive Directory List ....................................................................................136
Chapter 5
SYSTEM ADMINISTRATION
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
Additional Administrative Transactions .................................................................................... 137
Administrative Control Dataset Records ..................................................................................................137
Access Group Master ...................................................................................................................137
User Master ..................................................................................................................................137
Location Master ...........................................................................................................................137
Retention Control .........................................................................................................................137
Administrative Transaction Characteristics ..............................................................................................137
Panel Format .......................................................................................................................................137
PF Keys ...............................................................................................................................................138
Template Use ......................................................................................................................................138
Multi-panel Transactions ....................................................................................................................138
Help Facilities .....................................................................................................................................139
Administrative Transactions .....................................................................................................................139
Access Authorization ..........................................................................................................................139
Primary Menu .....................................................................................................................................139
Administrative Menu ..........................................................................................................................139
Add Transactions .........................................................................................................................139
Inquire Transactions .....................................................................................................................140
Change Transactions ....................................................................................................................140
© 2013 Mantissa Corporation. All rights reserved.
9
TABLE OF CONTENTS
System Reference Guide
Table of Contents: System Administration
RMS/Online® Version 11.35
TABLE OF CONTENTS
Delete Transactions ......................................................................................................................140
List Transactions ..........................................................................................................................140
Building A Management Database ...........................................................................................................140
Collecting the Required Information ..................................................................................................140
Creating System Control Records ......................................................................................................141
Access Authorization Panel .........................................................................................................141
Primary Menu Panel .....................................................................................................................142
System Administrative Panels ...................................................................................................................142
Administrative Menu Panel .........................................................................................................144
Access Group Master Panel .........................................................................................................145
User Master Panel ........................................................................................................................146
Security Profile ..........................................................................................................................................147
User Master Panel (continued) .....................................................................................................149
Job Statement Information ........................................................................................................................149
Location Master Panel .................................................................................................................150
Location Master Panel (continued) ..............................................................................................151
Retention Control Panel ...............................................................................................................152
Output Definition Panel ...............................................................................................................153
System Customization Panel .......................................................................................................157
Output Definition ......................................................................................................................................158
Output Definition Highlights ..............................................................................................................159
Adding An Output Definition Record .......................................................................................................159
Verification Report .............................................................................................................................161
Output Request ...................................................................................................................................161
Linking Output Definition Panels .......................................................................................................162
WebAccess Document Groups .................................................................................................................162
RMS WebAccess Highlights ..............................................................................................................163
Docgroup Definition ...........................................................................................................................163
Adding a Docgroup Profile Record .................................................................................................164
Linking DOCGROUP Panels .......................................................................................................167
System Administration Case Study ........................................................................................... 169
The Requirements ...............................................................................................................................169
The System ...................................................................................................................................169
The Reports ..................................................................................................................................169
Data Entry ...........................................................................................................................................169
Administrative Menu Panel .........................................................................................................170
Access Group Master Panel .........................................................................................................171
Administrative Menu Panel .........................................................................................................172
Location Master Panel .................................................................................................................173
Location Master Panel (continued) ..............................................................................................174
Administrative Menu Panel .........................................................................................................175
Location Master Panel .................................................................................................................176
Location Master Panel (continued) ..............................................................................................177
Location Master Panel .................................................................................................................178
Location Master Panel (continued) ..............................................................................................179
10
© 2013 Mantissa Corporation. All rights reserved.
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
System Reference Guide
RMS/Online® Version 11.35
Table of Contents: System Security
Administrative Menu Panel .........................................................................................................180
User-1 Master Record .................................................................................................................181
User-1 Master Panel (continued) .................................................................................................183
User-2 Master Record ..................................................................................................................184
User-2 Master Record (continued) ...............................................................................................186
User-3 Master Record .................................................................................................................187
User-3 Master Panel (continued) .................................................................................................189
Resource Security ...............................................................................................................................189
Resource Security Panel ..............................................................................................................190
Canceling Reports ...............................................................................................................................198
Retention-Based Archive ..........................................................................................................................199
System Administration Panel .....................................................................................................200
Retention Control Panel ..............................................................................................................201
Retention Control Panel - RMODEL Record .............................................................................201
Retention Control Panel - Report Record
...............................................................................203
Submitting Jobs from RMS .......................................................................................................................204
Help Management .....................................................................................................................................205
Help Maintenance Menu ....................................................................................................................205
Help List Display .........................................................................................................................205
Help Information for Help .....................................................................................................205
Help Format Information .......................................................................................................205
PF Key and Option Field Assignments ..............................................................................................205
Reserved Word List ............................................................................................................................206
Help Characters ..................................................................................................................................206
Help Variables ..............................................................................................................................206
Leaflets ...............................................................................................................................................207
Chapter 6
SYSTEM SECURITY
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
Definition of Terms ...................................................................................................................... 209
Security Level Definition ..........................................................................................................................209
System Security ..................................................................................................................................209
Access Group Level Security .............................................................................................................209
User Level Security ............................................................................................................................209
Resource Level Security .....................................................................................................................209
Security Maintenance .........................................................................................................................210
Access Group Master Panel .........................................................................................................211
Security Considerations .........................................................................................................211
Security Considerations for User Records ...................................................................................212
Security Considerations .........................................................................................................212
Transaction Security Add/Delete/Inquire Panel ..........................................................................213
Transaction Security ..............................................................................................................213
Location/Report Security Add/Delete/Inquire Panel ...................................................................214
© 2013 Mantissa Corporation. All rights reserved.
11
TABLE OF CONTENTS
System Reference Guide
Table of Contents: Display Print Facility
RMS/Online® Version 11.35
System Reference Guide
TABLE OF CONTENTS
Transaction Security ..............................................................................................................214
Security Examples .....................................................................................................................................214
Step 1. ..........................................................................................................................................215
Step 2. ...........................................................................................................................................216
Step 3. ...........................................................................................................................................217
Step 4. ...........................................................................................................................................218
Step 5. ...........................................................................................................................................219
Step 6. ...........................................................................................................................................220
Step 7. ...........................................................................................................................................221
Step 8. ...........................................................................................................................................222
Step 9. ...........................................................................................................................................223
Step 10. .........................................................................................................................................224
Step 11. .........................................................................................................................................225
Chapter 7
DISPLAY PRINT FACILITY
Access .......................................................................................................................................................227
Report Access .....................................................................................................................................227
System Access ....................................................................................................................................227
Communicating Your Report Access Requirements ................................................................................229
Requesting On-line Report Access .....................................................................................................229
Report Title and Originating System ...........................................................................................229
Viewing Capabilities .................................................................................................................................229
How to Use RMS/DPF ..............................................................................................................................230
Panel Management Characteristics .....................................................................................................230
Panel Format ................................................................................................................................230
Selection Characteristics ..............................................................................................................230
Scrolling Characteristics ..............................................................................................................230
Program Function Key Utilization .....................................................................................................231
System Help Facilities ...............................................................................................................................231
System User Panels ............................................................................................................................231
Session Example 1. ......................................................................................................................232
Objective ................................................................................................................................232
Session Example 2. ......................................................................................................................232
Objective ................................................................................................................................232
Session Example 3. ......................................................................................................................233
Objective ................................................................................................................................233
Access Authorization Panel .........................................................................................................234
Primary Menu Panel .....................................................................................................................235
Display/Print Menu Panel ............................................................................................................236
Index Panel ...................................................................................................................................237
Versions Panel ..............................................................................................................................238
12
© 2013 Mantissa Corporation. All rights reserved.
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
Introduction .................................................................................................................................. 227
RMS/Online® Version 11.35
Table of Contents: Problem Determination and Resolution
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
Display Panel ...............................................................................................................................239
Command Description ..............................................................................................................................240
Line Positioning/Scroll Operations ...........................................................................................................245
Recover / Print Panel ....................................................................................................................246
RMS Note Pad Facility .............................................................................................................................246
Note Pad Panel .............................................................................................................................247
RMS Security for Note pad access .....................................................................................................248
Note pad Usage Step by Step .............................................................................................................251
Note pad Usage – Reload from Group Archive .................................................................................265
Task/Panel Cross Reference ...............................................................................................................276
Using the Display for the First Time User ................................................................................................276
Important Keys .............................................................................................................................276
System Help Facilities .................................................................................................................276
How to get started ...............................................................................................................................276
Primary Menu Panel .....................................................................................................................277
Display/Print Menu Panel ............................................................................................................278
Index Panel ...................................................................................................................................279
Versions Panel ..............................................................................................................................280
Display Panel ...............................................................................................................................281
Report Viewing Features ...........................................................................................................................281
Report Formatting ...............................................................................................................................282
Saving Your Format for Later Use .....................................................................................................283
Line Positioning/Scroll Operations ....................................................................................................283
Locating Information Within the Report ............................................................................................284
Using the Windowing Features ..........................................................................................................285
Informational Commands ...................................................................................................................286
Using the Note Pad Capability ...........................................................................................................287
Selective And Full Version Printing .........................................................................................................287
Printing an Entire Report ....................................................................................................................288
Recover / Print Panel ....................................................................................................................289
Printing Selective Pages .....................................................................................................................289
Chapter 8
PROBLEM DETERMINATION AND RESOLUTION
Common Problems /Solutions .................................................................................................... 291
Chapter 9
MESSAGES AND CODES
RMS Messages ............................................................................................................................. 297
Introduction ...............................................................................................................................................297
Explanation of Message Format .........................................................................................................297
© 2013 Mantissa Corporation. All rights reserved.
13
TABLE OF CONTENTS
System Reference Guide
Table of Contents: Tutorial
RMS/Online® Version 11.35
System Reference Guide
TABLE OF CONTENTS
Messages ...................................................................................................................................................298
RM Codes ...........................................................................................................................................298
RMS Abend Codes ....................................................................................................................................415
Call Status Codes ......................................................................................................................................423
From ESFOPEN/ESFOPNC Interface .........................................................................................423
From ESFCLOS Interface .........................................................................................................................425
From ESFWRIT Interface .........................................................................................................................425
From ESFREAD Interface ........................................................................................................................427
From ESFSTAT/ESFSTAC Interface .......................................................................................................428
From ESFPURG/ESFPURC Interface ......................................................................................................428
From ESFROUT/ESFROUC Interface .....................................................................................................430
From ESFNECT Interface .........................................................................................................................430
From ESFCOMI Interface .........................................................................................................................432
Dynamic Allocation Return Codes ...........................................................................................................433
Chapter 10
TUTORIAL
Distribution Problem Definition and Results ............................................................................................435
Example ..............................................................................................................................................435
Screen 1 - Define the Distribution Options ..................................................................................436
Screen 2 - Define the “Stock” Report ..........................................................................................437
Screen 3 - Define the “VENACT” Report ...................................................................................438
Screen 4 - Define the “PROFIT” Report .....................................................................................438
Screen 5 - Adjust Stock Report Copies for Client 002 ................................................................439
Screen 6 - Send Client 001 Profit Report to Client 003 ...............................................................440
Screen 7 - Define Client 001 Packaging Requirements ...............................................................441
Screen 8 - Define Client 002 Packaging Requirements ...............................................................442
Screen 9 - Define Client 003 Packaging Requirements ...............................................................442
Dataset Profile (MVS only) ......................................................................................................................443
Specifying Capture Criteria ................................................................................................................443
Selection Attributes ...................................................................................................................................444
Completing Selection Fields ...............................................................................................................445
Attributes to be Assigned ..........................................................................................................................445
Examples of Sysout/Report Management Coding ....................................................................................447
Existing Customer ..............................................................................................................................447
Viewing Dataset Profiles ...........................................................................................................................449
Using the Primary Menu ...........................................................................................................................450
Creating a Packet Containing a Single Report .............................................................................451
Distribution Options Panel ........................................................................................................................456
Dataset Selection Panel .............................................................................................................................459
Custom Report Definition Panel for Sales Activity Report ......................................................................463
Custom Packaging Panel for Sales Activity Report ..................................................................................469
14
© 2013 Mantissa Corporation. All rights reserved.
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
Report Distribution Tutorial ........................................................................................................ 435
RMS/Online® Version 11.35
Table of Contents: Installation
Chapter 11
INSTALLATION
MVS System Installation/Verification ......................................................................................... 475
Introduction ...............................................................................................................................................475
Release Level Upgrade .............................................................................................................................475
RMS MVS Installation Checklist ..............................................................................................................476
Task 1 ...........................................................................................................................................477
Upload install files ..........................................................................................................................477
Task 2 ...........................................................................................................................................479
Installing the System .......................................................................................................................479
Task 3 ...........................................................................................................................................482
Prepare Repository/Start RMS Subsystem .................................................................................482
132 Column Support CICS Table Parms ...............................................................................485
TSO Environment Preparation ......................................................................................................485
Task 4 ...........................................................................................................................................486
System Verification .......................................................................................................................486
Initial User ID/Password .......................................................................................................488
Task 5 ..........................................................................................................................................489
Task 6 ...........................................................................................................................................490
RMS/WebAccess Installation ................................................................................................490
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
VSE System Installation/Verification ......................................................................................... 498
Introduction ...............................................................................................................................................498
Late-breaking Installation notes .........................................................................................................498
System Requirements .........................................................................................................................498
Release Level Upgrade .............................................................................................................................498
RMS VSE Installation Checklist ...............................................................................................................500
Task 1 ...........................................................................................................................................501
Download Install Job ......................................................................................................................501
Task 2 ...........................................................................................................................................502
Installing the System .......................................................................................................................502
Task 3 ...........................................................................................................................................504
Prepare Report Repository/Start RMS Subsystem. .....................................................................504
Task 4 ...........................................................................................................................................505
CICS Environment Preparation ....................................................................................................505
Task 5 ...........................................................................................................................................506
JCL Preparation ...............................................................................................................................506
Task 6 ...........................................................................................................................................509
Installation Verification ..................................................................................................................509
Initial User ID/Password .......................................................................................................509
Task 7 ...........................................................................................................................................510
CICS Transaction Gateway and RMS/WebAccess ...............................................................510
Component Configurations ........................................................................................................ 516
© 2013 Mantissa Corporation. All rights reserved.
15
TABLE OF CONTENTS
System Reference Guide
Table of Contents: Installation
RMS/Online® Version 11.35
System Reference Guide
TABLE OF CONTENTS
Archive / Distribution Component Configuration ....................................................................................516
16
© 2013 Mantissa Corporation. All rights reserved.
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
NOTES: ...................................................................................................................................... 517
Online Component Configuration .............................................................................................................517
Initial User ID/Password ....................................................................................................................520
Control File Configuration ........................................................................................................................520
Directives ............................................................................................................................................520
fsname - File set name ...........................................................................................................520
fencePrimary - Fence the primary subsystem. ......................................................................520
ignoreAux - Ignore Auxiliary Subsystems if down (for write operations) ...........................521
drain - Drain a subsystem ......................................................................................................521
useOrder - Use order of cache array members ......................................................................521
maxpercent - Maximum percentage utilization (before NOT being considered) ..................522
minfreeBlk - Minimum free blocks (before use) ...................................................................522
minfreeFqe - Minimum free file queue elements (before use) ..............................................522
tmessageLevel - Trace message level ....................................................................................522
RMS Integrity via QXCNTRL ...........................................................................................................523
Sample QXCNTRL Definition (INST02) without an array. ..............................................................523
Adding an auxiliary subsystem to cache array ...................................................................................524
Sample QXCNTRL Definition (INST02) with an array. ...................................................................524
Multiple Filesets ........................................................................................................................................525
Additional Filesets .................................................................................................................525
Let’s Recap ............................................................................................................................525
RvvrmCTL Startup: The FSETnn is an entry in QXPARMS DD ........................................527
Controller startup ...................................................................................................................527
Parm Member: RvvrmCTP ....................................................................................................527
Multiple Fileset DDNAMES: Site oriented ..........................................................................528
VSAM Dataset Configuration ...................................................................................................................529
VSAM Space Allocation ..............................................................................................................529
Description and Suggested Placement of VSAM Datasets ..........................................................529
QXACDS ...............................................................................................................................529
QXRCDS ...............................................................................................................................529
QXDCDS ...............................................................................................................................529
QXWKDS ..............................................................................................................................529
Placement ..............................................................................................................................529
RMS Controller Configuration .................................................................................................................530
CICS front end for RMS/Online ...............................................................................................................532
RMS/WebAccess CICS Security Management ........................................................................................533
Overview ............................................................................................................................................533
Dependencies ......................................................................................................................................534
Sign-On Security ................................................................................................................................534
Access Security ...................................................................................................................................534
ESM Definitions .................................................................................................................................534
$RMSVIEW Security Class ...............................................................................................................535
$RMSCMD Security Class .................................................................................................................535
Exit Modifications ..............................................................................................................................536
RMS/Online® Version 11.35
Table of Contents: Installation
Compile and Link Exit .......................................................................................................................536
Parameter List: Sign-On Request .......................................................................................................536
Returned Messages: Sign-On Request ...............................................................................................536
Parameter List: Report Access Request ..............................................................................................537
RMS SVC ..................................................................................................................................................537
SVC Installation .................................................................................................................................537
JES Exits ...................................................................................................................................................539
JES Exit Installation ...........................................................................................................................539
NOTES: ........................................................................................................................................540
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
RMS Subsystem Initialization ..................................................................................................... 541
Overview ...................................................................................................................................................541
Space Allocations ...............................................................................................................................541
Initialization Parameters ............................................................................................................................542
Syntax Rules .......................................................................................................................................543
RMS Initialization Parameters ............................................................................................................545
Initialization Parameter Description .........................................................................................................546
Multi-access Spool (MVS only) ................................................................................................................551
Configuration ......................................................................................................................................552
Starting the Multi-access SPOOL Configuration ...............................................................................552
There are three types of warm starts: ....................................................................................552
File Creation and Queuing ...........................................................................................................553
RMS Initialization Options .......................................................................................................................553
Starting and Stopping RMS .........................................................................................................553
Recovery and Warm Start ...................................................................................................................554
RMS Operator Commands ........................................................................................................................554
MVS .............................................................................................................................................554
VSE ..............................................................................................................................................554
Commands ...................................................................................................................................555
CHKPT Force Checkpoint ...........................................................................................................555
DA Display Active .......................................................................................................................555
DF Display File ............................................................................................................................555
Disk .............................................................................................................................................................555
DS Display Status ........................................................................................................................555
ESYS Restart/Reset System (MVS only) ....................................................................................556
LSYS List System Status (MVS Only) ........................................................................................556
SHUTDOWN Terminate RMS ....................................................................................................556
WRITELOG .................................................................................................................................556
RMS/WebAccess Application Server Notes .............................................................................. 557
Supported Platforms ..................................................................................................................................557
............................................................................................................................................................557
Load Balancing .........................................................................................................................................558
Appendix-A
© 2013 Mantissa Corporation. All rights reserved.
17
TABLE OF CONTENTS
System Reference Guide
Table of Contents: System Exit Programs
RMS/Online® Version 11.35
System Reference Guide
What is an Exit? ........................................................................................................................... 561
Exit Summary .....................................................................................................................................561
General Exit Characteristics ......................................................................................................................561
The Parameter List .......................................................................................................................561
RM00 RMS/Online Exits ...................................................................................................................562
Linking the Exits ..........................................................................................................................563
Security Exit Parameter List ........................................................................................................564
Print Characteristics Exit Parameter List .....................................................................................564
RM80000 (External Writer) Exits .............................................................................................................564
Input Exit ............................................................................................................................................565
Loading The Input Exit ................................................................................................................565
Input Exit Processing ...................................................................................................................565
Input Exit Data Area Definition ...................................................................................................566
SMF Exit .............................................................................................................................................567
SMF Exit Processing ....................................................................................................................567
SMF Exit Data Area Definition ...................................................................................................568
RM80001 (Archive/Recovery) Exits ........................................................................................................568
Security Exit .......................................................................................................................................569
Potential Uses ...............................................................................................................................569
Security Exit Processing ..............................................................................................................569
Output Exit .........................................................................................................................................570
Potential Uses ...............................................................................................................................570
Loading Output Exit .....................................................................................................................571
Output Exit Processing .................................................................................................................571
Output Exit Data Area Definition ................................................................................................571
MVS Accounting Data .................................................................................................................572
Additional Output Exit Considerations ........................................................................................572
RM80004 (Distribution Component) Exits ...............................................................................................572
Security Exit .......................................................................................................................................572
Potential Uses ...............................................................................................................................572
Security Exit Processing ..............................................................................................................573
Security Exit Data Area Definition ..............................................................................................573
RMS User Exit Parm List ...................................................................................................................574
RMS/WebAccess CICS Security Management .......................................................................... 575
Security Management ................................................................................................................................575
Overview ............................................................................................................................................575
Dependencies ......................................................................................................................................575
Sign On Security .................................................................................................................................575
Access Security ...................................................................................................................................575
ESM Definitions .................................................................................................................................575
$RMSVIEW Security Class ...............................................................................................................576
$RMSCMD Security Class .................................................................................................................576
RMS Interregion Operating Considerations .......................................................................................577
Exit Modifications ..............................................................................................................................577
18
© 2013 Mantissa Corporation. All rights reserved.
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
TABLE OF CONTENTS
SYSTEM EXIT PROGRAMS
RMS/Online® Version 11.35
Table of Contents: Field Level Security
Compile and Link the Exit ..................................................................................................................577
Parameter List - Sign On Request ......................................................................................................578
Possible Returned Messages from Sign On Request ..........................................................................578
Parameter List - Report Access Request ............................................................................................579
RMS/Online Security Calls ................................................................................................................579
Appendix-B
FIELD LEVEL SECURITY
Transactions ................................................................................................................................. 581
Access Group Security for DD: ...................................................................................................584
Appendix-C
DISTRIBUTION INSTRUCTIONS
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
Using Keyword Commands ........................................................................................................ 585
MVS ....................................................................................................................................................585
VSE .....................................................................................................................................................585
Distribution Key Definition and Development .........................................................................................585
Selecting Base Datasets for Distribution ...................................................................................................587
Getting Started ....................................................................................................................................587
Control Statements .............................................................................................................................588
Option Commands .......................................................................................................................588
Definition Commands ..................................................................................................................588
Task/Command Cross Reference ..............................................................................................................589
Command Order ........................................................................................................................................589
Language Considerations ...................................................................................................................590
Parameter Set ......................................................................................................................................590
Command Continuation ...............................................................................................................590
Reserved Words ...........................................................................................................................591
Field Comparison/Replacement .........................................................................................................591
Process Control Commands ................................................................................................................591
Notation Conventions .........................................................................................................................591
Distribution Definition With Keywords Tutorial ......................................................................................592
Begin Coding ......................................................................................................................................592
Understanding Each Command ..........................................................................................................592
Identifying the Report ..................................................................................................................593
Controlling the Output .................................................................................................................594
Creating the Packet to Contain the Report ...................................................................................594
Selecting the Dataset ....................................................................................................................595
Some New Requirements .............................................................................................................595
The new code / new concepts. .....................................................................................................596
Sending Additional Copies .................................................................................................................597
© 2013 Mantissa Corporation. All rights reserved.
19
TABLE OF CONTENTS
System Reference Guide
Table of Contents: Distribution Instructions
RMS/Online® Version 11.35
TABLE OF CONTENTS
The current code is shown below: ................................................................................................600
The new code with new requirements shown in bold type: .........................................................600
Other Considerations .................................................................................................................................602
Inserting Data .....................................................................................................................................603
Distribution Instruction Sets Examples .....................................................................................................604
Keyword Command Summary .................................................................................................... 609
DEFINE*KEY ..........................................................................................................................................609
DEFINE*KEY Command Summary ...........................................................................................609
DEFINE*KEY PARAMETERS ..................................................................................................609
RECOVER ................................................................................................................................................610
RECOVER Command Summary .................................................................................................610
RECOVER PARAMETERS ........................................................................................................610
RUN*OPTIONS .......................................................................................................................................611
RUN*OPTIONS Command Summary ........................................................................................611
RUN*OPTIONS PARAMETERS ...............................................................................................611
Input Process Commands ..........................................................................................................................614
BROADCAST ...........................................................................................................................................614
BROADCAST Command Summary ...........................................................................................615
BROADCAST PARAMETERS ..................................................................................................615
COPY ........................................................................................................................................................616
COPY PARAMETERS ................................................................................................................616
FORM*CONTROL*BUFFER .................................................................................................................617
FORM*CONTROL*BUFFER Command Summary ..................................................................617
FORM*CONTROL*BUFFER PARAMETERS .........................................................................618
NOTES on FORM*CONTROL*BUFFER: ................................................................................618
IDENTIFY*REPORT ...............................................................................................................................618
IDENTIFY*REPORT Command Summary ................................................................................618
IDENTIFY*REPORT PARAMETERS ......................................................................................618
Optional Parameters .....................................................................................................................620
SELECT ....................................................................................................................................................623
SELECT Command Summary .....................................................................................................623
SELECT PARAMETERS ............................................................................................................623
Optional Parameters .....................................................................................................................623
Notes on PROCESS*CODE: .......................................................................................................624
TRANSLATE ...........................................................................................................................................625
TRANSLATE Command Summary ............................................................................................625
TRANSLATE PARAMETERS ...................................................................................................626
Optional Parameters .....................................................................................................................626
OUTPUT PROCESS COMMANDS ........................................................................................................627
INSERT*DATA*STREAM .....................................................................................................................627
INSERT*DATA*STREAM PARAMETERS .............................................................................627
OUTPUT*CONTROL ..............................................................................................................................630
OUTPUT*CONTROL Command Summary ...............................................................................630
OUTPUT*CONTROL PARAMETERS ......................................................................................630
PRIORITY ................................................................................................................................................632
20
© 2013 Mantissa Corporation. All rights reserved.
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
System Reference Guide
RMS/Online® Version 11.35
Table of Contents: Resource Security Categories, Types and Codes
PRIORITY Command Summary .................................................................................................633
PRIORITY PARAMETERS ........................................................................................................633
CREATE*PACKET ..................................................................................................................................633
CREATE*PACKET Command Summary ..................................................................................633
CREATE*PACKET PARAMETERS .........................................................................................634
Appendix-D
RESOURCE SECURITY CATEGORIES, TYPES AND CODES
Transaction Security ................................................................................................................... 637
Resource Types with Associated Resource ID’s ................................................................................637
Resource Type HM - Help Management ............................................................................................638
Resource Type SA - System Administration ......................................................................................638
Resource Type RS - Resource Security ..............................................................................................639
Resource Type DD - Distribution Definition .....................................................................................640
Administrative Documents ........................................................................................................................642
Access Group Master ................................................................................................................................642
Security Profile .........................................................................................................................................643
User Master ...............................................................................................................................................643
Appendix-E
LEAFLET
Prototype ...................................................................................................................................... 645
Leaflet Variable Symbol .....................................................................................................................646
Appendix-F
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
JCL VARIABLE SYMBOLS
Variable for PRT.JOB.PRINT Substitution ................................................................................. 649
Cancel Job Stream Variable Symbols ................................................................................................650
Appendix-G
RMS/BASIC
File and Job Control Requirements ........................................................................................... 651
RM80001 File/Job Control Requirements ................................................................................................651
File Requirements ...............................................................................................................................651
RMS Repository Files ..................................................................................................................651
RMS SYSIN File .........................................................................................................................651
RMS SYSOUT File .....................................................................................................................651
© 2013 Mantissa Corporation. All rights reserved.
21
TABLE OF CONTENTS
System Reference Guide
Table of Contents: Conversion from Positional Commands
RMS/Online® Version 11.35
System Reference Guide
TABLE OF CONTENTS
Utility Input/Output Files .............................................................................................................651
RM80004 File/Job Control Requirements ................................................................................................652
File Requirements ...............................................................................................................................652
RMS Repository Files ..................................................................................................................652
RMS SYSIN File .........................................................................................................................652
Calculating Disk Work Space Requirements .....................................................................................653
Appendix-H
CONVERSION FROM POSITIONAL COMMANDS
Overview ....................................................................................................................................... 655
Conversions ...............................................................................................................................................655
Appendix-I
System Reports ............................................................................................................................ 659
RMS/Online Reports .................................................................................................................................659
RMS/Online Reports on File by Location ................................................................................................659
RMS001 ..............................................................................................................................................659
RMS/Online Reports on File by Report ....................................................................................................660
RMS002 ..............................................................................................................................................660
RMS/Online System Administration Archive Datasets ............................................................................660
RMS003 ..............................................................................................................................................660
RMS/Online Distribution Definition Reports within Instruction Set by Report .......................................660
RMS004 ..............................................................................................................................................660
RMS/Online Distribution Definition Reports within Instruction Set by Instruction Set ..........................660
RMS005 ..............................................................................................................................................660
RMS/Online Distribution Definition Datasets Processed by Instruction Set ............................................661
RMS006 ..............................................................................................................................................661
RMS/Online System Administration User List .........................................................................................661
RMS007 ..............................................................................................................................................661
RMS/Online System Administration Locations ........................................................................................661
RMS008 ..............................................................................................................................................661
RMS/Online System Administration Access Groups ...............................................................................661
RMS009 ..............................................................................................................................................661
RMS/Online System Administration Security Groups (Transactions) .....................................................661
RMS010 ..............................................................................................................................................661
RMS/Online System Administration Security Groups (Locations) ..........................................................661
RMS011 ..............................................................................................................................................661
RMS/Online Send Report by Report ID ...................................................................................................662
RMS012 ..............................................................................................................................................662
RMS/Online Reports on File by Location ..............................................................................................662
RMS013 ..............................................................................................................................................662
22
© 2013 Mantissa Corporation. All rights reserved.
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
REPORTS
RMS/Online® Version 11.35
Table of Contents: RMS Utilities
RMS/Basic Statistical Reports ..................................................................................................................662
RMS200 ..............................................................................................................................................662
Appendix-J
RMS UTILITIES
RM90044, RM90046 and Weekly VSAM File Maintenance ........................................................ 663
Overview ............................................................................................................................................663
PRINT PUNCH (Program RM90044) ......................................................................................................663
DEFPRPU JCL MEMBER .................................................................................................................663
DEFPRPU JCL MEMBER .................................................................................................................664
FROM: ...................................................................................................................................665
TO: .........................................................................................................................................665
COPYISN (Program RM90046) ...............................................................................................................666
Sample of COPYISN executed from a proclib: ....................................................................667
WEEKLY VSAM FILE MAINTENANCE (MAINT01) ........................................................................667
MAINT01 ...........................................................................................................................................668
IDCAMS: DELETE/DEFINE ............................................................................................................668
Glossary
REPORT MANAGEMENT
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
Terminology ................................................................................................................................. 669
Archiving ............................................................................................................................................669
Automatic Packaging Panel ................................................................................................................669
Auto Report Definition Panel .............................................................................................................669
Base Dataset .......................................................................................................................................669
Broadcast ............................................................................................................................................669
Broadcasting .......................................................................................................................................669
Checkpoint Dataset .............................................................................................................................670
Common Definitions ..........................................................................................................................670
Content/Recipient Conversion Panel ..................................................................................................670
Copy Control Panel ............................................................................................................................670
CREATE*PACKET ...........................................................................................................................670
Custom Packaging Panel ....................................................................................................................670
Custom Report Definition Panel .........................................................................................................670
Data Insertion Panel ............................................................................................................................670
Dataset Selection Panel ......................................................................................................................671
Define*Key .........................................................................................................................................671
Distribution Endpoint .........................................................................................................................671
Distribution Key .................................................................................................................................671
Distribution Key Element ...................................................................................................................671
Distribution Options Panel .................................................................................................................671
© 2013 Mantissa Corporation. All rights reserved.
23
TABLE OF CONTENTS
System Reference Guide
Table of Contents: Report Management
RMS/Online® Version 11.35
System Reference Guide
RO_Reference_Guide(v11r35m1)TOC.fm: Revised Sunday, November 24, 2013
TABLE OF CONTENTS
Extracting ............................................................................................................................................671
FORM*CONTROL*BUFFER ...........................................................................................................671
IDENTIFY*REPORT ........................................................................................................................671
INSERT*DATA*STREAM ...............................................................................................................672
Key Element .......................................................................................................................................672
Mapping ..............................................................................................................................................672
ORDER PHASE .................................................................................................................................672
OUTPUT*CONTROL ........................................................................................................................672
Output Phase .......................................................................................................................................672
Output Priority Panel ..........................................................................................................................672
Page Format Data ...............................................................................................................................672
Priority ................................................................................................................................................673
Recipient/Location Equate Panel ........................................................................................................673
Recipient/Recipient Convert Panel .....................................................................................................673
Report .................................................................................................................................................673
Report Mapping ..................................................................................................................................673
Report Top of Form ............................................................................................................................673
RMS/ARC ..........................................................................................................................................673
RUN*OPTIONS .................................................................................................................................673
Scan Phase ..........................................................................................................................................673
SELECT ..............................................................................................................................................673
Send Report Panel ..............................................................................................................................674
Set Reorganization Panel ....................................................................................................................674
TRANSLATE .....................................................................................................................................674
WAITARC ..........................................................................................................................................674
WAITARCINDX ................................................................................................................................674
24
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
System Reference Guide
Chapter 1: The Report Management System
Introduction
Historical Perspective on Report Management Systems
Chapter 1
THE REPORT MANAGEMENT SYSTEM
Introduction
Congratulations! The fact that you are reading this means that you have already selected, or may be engaged in the
process of selecting or replacing, a report management system for your enterprise. If you are a key figure in the
selection or implementation process, you have before you one of the best opportunities of your business career to
achieve significant cost saving for your organization. Your efforts will result in significant improvements in the use
and availability of information essential for your business operations, increase the “velocity” of that information and
increase its value by making it more timely.
This chapter will present overview information on RMS. It will attempt to give you a historical perspective on the
origins and architectural underpinnings of the major systems now in the marketplace.
HISTORICAL PERSPECTIVE ON REPORT MANAGEMENT SYSTEMS
In 1981, Mantissa produced the first general-purpose system for the distribution, archive, and recovery of reports.
Before the introduction of RMS, numerous attempts to deal with the problems by changing application systems to
support report management functionality. The prevailing wisdom now is that any such implementation though well
intended is a mistake since there are numerous report management products that achieve the desired functionality
without having to alter the application system producing the reports.
Since the advent of the general purpose report management system, the prediction has been that there would be no
long-term need for such systems since the report as we know it would become an outmoded relic. It hasn’t happened.
The problems related to report management are today more complicated than in 1981. For example, the prospect of
giving a specific recipient the option to receive reports on CD was unheard of at that time. Microfiche and hardcopy
were the only media types available at that time.
Chap_01(v11r35m1).fm: Revised Sunday, November 24, 2013
Between 1981 and 1985 two other products dealing with report management appeared. During 1985 (after Mantissa
had approximately 300 installations in the United States), other software (and some hardware) companies began to
realize that report management was a new product category. Suddenly, every company that had anything to do with
displaying reports or printing had a report distribution system.
That year, Mantissa continued its innovation with the introduction of RMS/Online a system for storing and viewing
distributed reports. Shortly after the introduction of this product, other products that had originally appeared as
JOBLOG management and display systems were updated to handle distributed reports.
In 1987 Mantissa released RMS/Spool, a system for printing, viewing and management of reports in a mainframe
environment. A significant feature of RMS/Spool is the SUBSYSTEM technology used by system. This system was
enhanced in 1989 to include unattended delivery of reports distributed by RMS (or other distribution systems) to
mainframe connected PCs.
In 1989, Mantissa introduced the first report management system for LAN/WAN stand-alone PCs. The system, RMS/
DeskTop, featured four major components: 1.) Report Viewing and version management, 2.) Data Extraction, a data
mining feature for reports, 3.) Automated printing for printing select reports as they are delivered to the remote site,
© 2013 Mantissa Corporation. All rights reserved.
25
CHAPTER 1: INTRODUCTION
If your organization is now one of the hundreds that are replacing a report management system that looked good on
paper but didn’t work as well in the real world, don’t be discouraged. The fact that your company possessed the
business savvy to be an early adopter of report management software means that it has already benefited
tremendously, even if the system used represented a less-than-optimum solution.
RMS/Online® Version 11.35
Chapter 1: The Report Management System
Introduction
High Performance RMS Characteristics
System Reference Guide
and 4.) Optical Archive for the optical media storage of reports. This system, caused a major ripple in the industry
and forced competing companies to release products that delivered or appeared to deliver the same type of
functionality. Unlike the current Windows version of DeskTop, the first release of the product was a DOS-based
application.
The most recent releases of RMS/DeskTop continues to distinguish itself from other competing products by
providing full management of reports, optical archive, data extraction capabilities, and a system that really manages
the report usage cycle. RMS also provides a feature called Document Retreival System (DRS) which allows the
RMS/DeskTop user the capability of retrieval of reports from RMS directly without having to leave RMS/DeskTop./
HIGH PERFORMANCE RMS CHARACTERISTICS
CHAPTER 1: INTRODUCTION
26
•
Cache Array Support
Multiple sub-systems supporting one fileset.
•
Large Dataset Support
RMS now supports SPOOL repository dataset extents greater than 65K tracks (maximum 983000 tracks) in
size and may be located any where within the first 983000 tracks on a 3390 disk.
•
MAS (Multi-access System) repository support.
The system supports up to 7 CPUs in a complex.
•
Extensible Repository.
The system supports small and large (up to 8/10 terabyte) with equal ease.
•
Asynchronous repository write operations.
Tasks do not wait on repository write operations to proceed.
•
Asynchronous repository dataset deletion requests and space release.
Tasks should never be suspended by purge requests or free space requests.
•
The system scales well..
The system will operate well in a small environment of 500 users and a much larger environment of eight (8)
thousand users.
•
Multiple index fileset support
The physical repository is capable of being shared by any number of index filesets to avoid space
management and administrative overhead.
•
Single image index update.
All index updates regardless of the originating task or CPU can be performed on a single CPU.
•
Simultaneous distribution tasks.
The architecture does not limit the number of tasks that can be employed to meet scheduling deadlines.
Distribution tasks, regardless of the number active, operate unimpeded by the other tasks. There are no long
waits or enqueue holds that will suspend the tasks.
•
Efficient large directory support.
The system will scale well when the number of active report directory entries increases substantially. The
repository should support a million active datasets as well as it supports 10,000 datasets.
© 2013 Mantissa Corporation. All rights reserved.
Chap_01(v11r35m1).fm: Revised Sunday, November 24, 2013
The characteristics of multi-tasking and functional overlap that make a great operating system are equally important
in the performance of a report management system. These characteristics manifest themselves in many different ways
within RMS, but the net effect is increased throughput and extraordinary system capacity. The following is a recap of
those characteristics that are significant architectural facets of RMS:
RMS/Online® Version 11.35
Chapter 1: The Report Management System
System Reference Guide
Introduction
Functional Component Capabilities
RMS/Online
FUNCTIONAL COMPONENT CAPABILITIES
RMS is a fully automated report distribution and management solution for mainframe and LAN/WAN/Standalone PC
environments. RMS is comprised of three products designed to work together to effectively automate the distribution
and management of reports. The RMS family of products includes:
•
RMS/Online
•
RMS/Spool
•
RMS/DeskTop
•
Provides repository structure for the storage of reports.
•
Provides a means of efficiently moving reports to the repository.
•
Distributes and creates packets in accordance with user-defined criteria.
•
Provides full media support for all distributed reports.
•
Provides archive and recovery facilities for all distributed reports regardless of media.
•
Automates the distribution definition process.
•
Enables report viewing, selective printing, and tracking of all distributed reports.
•
Maintains the database necessary to view reports, set retention thresholds, and define report datasets to be
managed by the RMS subsystem.
•
Provides integrated Help management facilities.
•
Provides Resource Security for the protection of reports and transactions.
•
Includes a Dataset Profile Management enabling selective management of application reports without
changes in application JCL.
CHAPTER 1: INTRODUCTION
RMS/Online
RMS/Spool
Chap_01(v11r35m1).fm: Revised Sunday, November 24, 2013
RMS/SPOOL is a complete, independent spooling system implementing general spooling facilities for 3270-type
printer devices, IP Printers, PCs and offering full end-user control with a high degree of automation. In addition,
RMS/SPOOL offers powerful facilities for job submission, inter-program data interchange, and multi-CPU
environments.
Distributed control is implemented by collecting the printers and display terminals into network groups. The network
group is a collection of printers, display devices, and print files forming a logical unit defined by the individual
installation. Printers and display terminals may be added or deleted while RMS/SPOOL is running. Attributes for a
device will be partly obtained from VTAM or TCP/IP and partly from installation-dependent default values.
•
Within the network group, the end user is unaware of the other parts of the network, is independent of the
system operator, and is in total control of his own (and only his own) printers and print files.
•
Without any need of manual intervention, RMS/SPOOL will perform the tasks outlined below:
•
Whenever a spool file is ready for processing, a printer is automatically acquired.
•
Depending on the particular printer setup, number of print lines, classes, etc., the highest priority print
task is selected.
•
The user is notified when another form should be mounted.
•
The physical printing is performed with full FCB support.
© 2013 Mantissa Corporation. All rights reserved.
27
RMS/Online® Version 11.35
Chapter 1: The Report Management System
Introduction
Functional Component Capabilities
RMS/Spool
•
The printer is released when no more work is pending or on request by another application.
•
Printed spool files may be kept in the system after printing. The retention period for printed files can be
specified for the individual file, for the destination, or for the whole system.
•
Spool files left open by an abnormally ended CICS application program are automatically closed.
If required, the end-user may:
•
Change spool file attributes (class, form number, FCB, file name, etc.).
•
Change printer-selection criteria (process other classes, etc.).
•
Route spool files to another printer or to JES2/JES3 or VSE Power.
•
Re-queue processed spool files for reprinting.
•
Intervene during the automatic printer handling (halt a printer, backspace, forward space, etc.).
•
CHAPTER 1: INTRODUCTION
28
Report when a requested setup is complete (if RMS/SPOOL requires a new form to be
mounted).
•
Access to the network groups is controlled via user id. The system programmer can either choose internal
security or external security systems such as RACF, TOPSECRET or ACF2.
•
The end user communicates with RMS/SPOOL either through the RMS/SPOOL Menu System or through a
RMS/SPOOL console via an ordinary 3270-type VTAM-controlled display terminal. The Menu System
makes it possible to use RMS/SPOOL without knowing the syntax of the underlying commands. The
operator panel on SCS printers can also be used to communicate with RMS/SPOOL.
•
The installation may also choose to further automate the operation or develop its own user dialogue using
the Advanced Communication Interface, which will open a full console session with an application program.
Please refer to chapter 3 for further details.
•
Programmers may use the standard call interface of RMS/SPOOL or the SUBSYS Interface for creation or
recreation or retrieval of spool files. The SUBSYS Interface allows RMS/SPOOL facilities to be used by
application programs or standard IBM utilities without modification.
•
The NJE Interface makes RMS/SPOOL a true member of NJE Interface the NJE product family and lets
RMS/SPOOL receive files from and send files to JES2, JES3/BDT, RSCS and POWER. The product MVS/
BDT V2 is a prerequisite for JES3, because current JES3 versions do not support SNA NJE conditions.
•
The Virtual Printer Interface allows programs to create RMS/SPOOL files without any changes to the
existing program at all. It is especially intended for CICS and IMS environments, where it can be difficult to
make application program changes.
•
The PSF interface lets RMS/SPOOL work as the system spool for PSF, so the end user can control his own
AFP printers.
•
RMS/SPOOL offers a highly efficient method of creating batch jobs and submitting them for execution from
an application program. Application programs may also make use of spool files as interim storage for data to
be used later on in the same program or another online or batch program.
•
Via the GDDM Interface it is possible to place GDDM output files under RMS/SPOOL control. It is thereby
possible to archive, reprint, and reroute GDDM output like any other RMS/SPOOL file.
•
The HP-LaserJet Interface gives support for printing of IBM 3800-1 generated DCF files on HP-LaserJet
printers.
•
The spool-file transfer program ESFSPTP is used to create backup or archive copies of all or a subset of the
spool files.
© 2013 Mantissa Corporation. All rights reserved.
Chap_01(v11r35m1).fm: Revised Sunday, November 24, 2013
•
System Reference Guide
RMS/Online® Version 11.35
Chapter 1: The Report Management System
System Reference Guide
•
Introduction
Functional Component Capabilities
RMS/DeskTop
The general print utility ESFPRINT is used to create a spool file from an ordinary OS dataset. It contains
complete, functional replacements for the IBM DSPRINT, PRINTDS, and PRINTOFF commands.
RMS/DeskTop
RMS/DeskTop Version 3.x is a powerful industrial-strength report management system which
automatically and transparently receives your reports from your organization’s mainframe, minicomputer,
or PC and stores them on your PC’s media (or LAN file server’s media), providing you with access to view,
browse, search, mark, reorganize, mine, export and print any data contained within those reports. But its
real strength lies in its advanced architecture for performing these functions!
A few of RMS/DeskTop’s architectural strengths include:
An user definable report explorer for quick and easy access to reports. The explorer features include:
•
Date range filtering and selection.
•
Prior version range selection.
•
Hierarchal method for exploring report categories.
•
Annotation features.
•
Ability to import or export various other file types.
•
Report Cataloging which provides transparent access to reports, without having to know where the reports
are stored (regardless of storage media).
•
Powerful new repository techniques, including automatic low-level indexing and media bridging
•
A shared magnetic cache controller, with up to four cache levels
You can think of RMS/DeskTop as a file security agent, file cabinet, filing clerk, and research assistant, all
rolled into one.
RMS/DeskTop Makes Reports Useful
Chap_01(v11r35m1).fm: Revised Sunday, November 24, 2013
RMS/DeskTop allows you to display and analyze report data that has previously been printed to disk as a
print or spool file. In a business environment, these files are usually distributed through a communications
interface, magnetic tape, CD-ROM, or diskette.
© 2013 Mantissa Corporation. All rights reserved.
29
CHAPTER 1: INTRODUCTION
•
Chapter 1: The Report Management System
Introduction
Functional Component Capabilities
RMS/DeskTop
RMS/Online® Version 11.35
System Reference Guide
CHAPTER 1: INTRODUCTION
Chap_01(v11r35m1).fm: Revised Sunday, November 24, 2013
RMS/DeskTop allows you to select a report file that has been stored on disk and display it on your
computer monitor in the format it was originally printed or stored. But this is only the beginning of your
RMS/DeskTop experience.
30
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 1: The Report Management System
Introduction
RMS Architecture
What is the repository?
System Reference Guide
RMS ARCHITECTURE
What is the repository?
The repository is a high-speed storage tier of DASD managed by the RMS subsystem. The system permits storage of
up to 1+ million active datasets. Datasets are spread evenly across all extents in the storage tier to level access I/O
contention. The diagram below depicts the relationship between RMS distribution tasks, your application systems
which generate reports to be managed by RMS, JES, and the CICS/TSO user environment.
Application
Programs
Distribution
Controller
Tasks
Native
Read
RMS/
CHAPTER 1: INTRODUCTION
Call Interface
Transport
Interface
Subsystem
Interface
JES2
Filter
CICS
TSO
Chap_01(v11r35m1).fm: Revised Sunday, November 24, 2013
RMS Subsystem
What are the limits?
Realistically there are no limits. Our largest customer manages over 11 billion lines per month with RMS and has
about 70 DASD volumes committed to report storage. This represents less than 28% (a repository may be almost a
terabyte) of the potential capacity for just one subsystem! There can be any number of subsystems active. With the
addition of Cache Array Support, one controller can load multiple repositories.
This same user processes over 750,000 RMS transactions per day in a CICS environment. With the exception of find
operations in the viewing transaction, all transactions have sub-second response times.
Your application may create files to be viewed or distributed (or both) of any length. No limits exist on the size and
complexity of the distributions, number of recipients, etc.
© 2013 Mantissa Corporation. All rights reserved.
31
RMS/Online® Version 11.35
Chapter 1: The Report Management System
Introduction
RMS Architecture
What is the Controller?
System Reference Guide
What is the Controller?
Notice the block in the previous diagram labeled “Controller”. The diagram below depicts the relationship between
the RMS controller task, the RMS subsystem, and JES2.The controller main task and the associated sub-tasks
perform the following functions:
•
Transport Subtask:
External writer support to add JES datasets to the repository.
•
Archive Subtask:
Group (retention group) support for reports.
•
Purge Subtask:
Dataset deletion support.
•
Index Subtask:
Index management (addition, deletion, update) support (for up to 8 filesets per subsystem).
•
Output Subtask:
Service for selective and print-on-demand requests.
•
Recover Subtask:
Support for restoring archive datasets to viewing status within Online.
CHAPTER 1: INTRODUCTION
JES
RMS
Controller Main Task
Output
Recovery
Archive
Index 1
Transport
Purge
Index 2
Index N
Data
S
M t1
R se
le
Fi
Data
Data
Data
ep
S ry
M o
R sit
o
R
RMS
Subsystem
Data
Data
Data
32
© 2013 Mantissa Corporation. All rights reserved.
Chap_01(v11r35m1).fm: Revised Sunday, November 24, 2013
Data
RMS/Online® Version 11.35
System Reference Guide
Chapter 1: The Report Management System
Introduction
RMS Architecture
What is stored in the repository?
What is stored in the repository?
The repository holds two types of datasets, “BASE” and “DISTRIBUTED”. Base datasets are captured by RMS
either through the RMS Subsystem interface or the external writer interface. They represent the original report
information produced by an application system.
Base datasets may also be viewable. Viewing status for base datasets is contingent on whether or not they were
assigned a fileset name by the external writer or subsystem interface. However, the main characteristic that
distinguishes a base dataset is that a base datasets can be distributed (used as input to the RMS distribution
component (RM80004)). The fileset name is assigned in the RMS Controller Parms.
A normal by-product of the distribution process is the creation of distributed or Softcopy datasets. These distributed
datasets remain in the repository along with base datasets until removed by subsequent backup, update or restore
cycle activity. All stored reports have unique names and are indexed by report within a location within access group.
Any number of versions may be maintained to provide the desired level of availability. Expiration based on a specific
number of versions of a report and/or expiration by days resident in the repository are supported.
The repository is maintained by a functional subsystem and the RMS controller. The subsystem features MultiAccess-Spool (MAS) support that permits concurrent distribution, viewing access, archive, and recovery from up to 7
CPUs.
The subsystem repository consists of from 1 to 255 files. Each file consists of contiguous DASD space and may be as
small as a single cylinder or as large 64,000 tracks on any disk device supported by the host system. The subsystem
maintains a sparse index of entries in the repository which is updated any time there is an addition or modification to
the repository. This sparse index yields high speed access to any of the entries.
How is report data placed in the repository?
Subsystem Interface (MVS)
The RMS Subsystem Interface (SSI) provides a direct link to the RMS repository for output from the application
program. SYSOUT data can be routed to the SSI rather than to JES. No JCL changes are required. There is no drain
time for moving data through JES. Moving the data once, rather than to the JES spool then to the repository,
minimizes overhead and is transparent to the user.
Chap_01(v11r35m1).fm: Revised Sunday, November 24, 2013
Intermediate storage requirements are significantly reduced and read/write operations are minimized since the
SYSOUT is received directly from the application. The data is compressed as it is being transferred and SYSOUT
processed by the subsystem interface are available for further processing immediately after the file is closed by the
application program. The SSI manages space allocation, purge, and status presentation and has clear advantages over
using the external writer interface.
The RMS Dataset Profile capability enables the user to select which SYSOUT datasets are to be processed by the
RMS subsystem. Specific attributes are maintained in a profile table. As application JCL is processed, attributes of
the Job and individual DD statements are presented to JES Exit 6 where SYSOUT attributes are compared to the
profile table attributes. A match condition between attributes of the dataset and profile attributes will route the
SYSOUT directly to the repository. If there is no match the SYSOUT is routed to JES.
© 2013 Mantissa Corporation. All rights reserved.
33
CHAPTER 1: INTRODUCTION
How is the repository managed?
RMS/Online® Version 11.35
Chapter 1: The Report Management System
Introduction
RMS Capabilities
How does the user access the report information?
System Reference Guide
External Writer Interface
The external writer interface (EWI) is used to place JES2 datasets in the RMS repository. The only job control
modifications necessary to route reports to the RMS Repository via the external writer are to the SYSOUT DD
statements. Datasets may be routed to the external writer based on SYSOUT class, destination ID or a combination of
these attributes. Of course, program output can be directed to any combination of classes and destinations. The
SYSOUT from an entire job, or from specific DD statements within the job, may be routed to RMS.
How does the user access the report information?
Once a user has entered proper identification, RMS can provide an index of reports available for viewing. The Report
Index shows all the reports available (security considered) for a specific user. RMS also provides a report tracking
facility that permits inquiry based on the media type of the report. RMS can thereby provide instant historical
information (and ability to recover) for all reports regardless of their original media.
RMS CAPABILITIES
CHAPTER 1: INTRODUCTION
A report management system orders, consolidates, routes, archives, recovers and provides complete media control of
report information. The following diagram indicates how the interlocking capabilities of RMS support enterprise
output management requirements.
ARCHIVE / RECOVERY /
DISTRIBUTION
VIEWING
VTAM / TCP/IP Report
Delivery/Printing
Administrative Services
This on-line facility enables you to describe the report management environment. Using administrative services you
can define:
34
•
Access groups (application report groups).
•
Locations (physical and/or logical distribution endpoints).
© 2013 Mantissa Corporation. All rights reserved.
Chap_01(v11r35m1).fm: Revised Sunday, November 24, 2013
PC / LAN REPORT MANAGEMENT
and OPTICAL ARCHIVE
RMS/Online® Version 11.35
Chapter 1: The Report Management System
System Reference Guide
Introduction
RMS Capabilities
Distribution Definition
•
Users of reports.
Please note that RMS has a signon exit that permits definition of users “on the fly” based on your security
profile for a particular user.
•
Report retention characteristics for reports and tracking information.
•
Resource security permits you to control access to reports, transactions, and system facilities. A convenient
exit facility is provided that enables you to interface with your current security system.
•
Distribution definition is accomplished through a menu-driven, distribution definition facility that operates
under CICS and TSO.
•
A report mapping facility that takes the guess work out of the definition process.
•
Lowest data entry requirements of any available system. We call this implicit definition. This type of
definition can mean as much as a 100 to 1 reduction in the initial and ongoing data entry requirements of
other available systems.
•
Copy control at the report level for each recipient and output media type.
•
Zero copy capability to delete reports for specific recipients.
•
An entire report or any part of a report may be BROADCAST to any number of additional recipients. The
copy count and media may be varied for each additional recipient.
•
Data Insertion. Any data string may be inserted in the output. Uses include the control of 3800 printers in an
advanced function printing environment, DJDE control information insertion for 9700/8700 control, and
control information insertion for any of the popular on-line/off-line microfiche systems.
•
Dated override capability. Many definition panels permit effective date overrides. Such variables as copy
count for a report/recipient combination may be placed in effect for a specific number of days. After the
change is no longer relevant, the system discards this type of change and reverts to the standard copy count.
Chap_01(v11r35m1).fm: Revised Sunday, November 24, 2013
Packaging Capabilities
•
Unique packet(s) may be created for each user.
•
Each packet may have a customized banner page with name and address if desired.
•
Reports within packets are collated in the same order each day to reduce confusion and reduce the search
time for a report.
•
By default, each packet is a unique dataset. Laser printer output is therefore separated by a ‘BOT' marker or
tray offset simplifying the distribution process.
•
Packets contain a manifest list at the end showing exactly which reports were distributed, along with the
number of pages/lines. Users can verify receipt/content in minutes.
•
Any combination of reports from any system(s) may be included in a distributed packet. The number of
reports and pages is unlimited.
Media Control
•
Support of up to eight media categories in a single execution. Recipients may receive report packets in any
or all media types.
•
Automatic routing support for RJO printers/terminals.
•
No JCL is necessary because dynamic allocation facilities are used to create print datasets. Individual
packets may be routed to DASD/TAPE files at will.
© 2013 Mantissa Corporation. All rights reserved.
35
CHAPTER 1: INTRODUCTION
Distribution Definition
RMS/Online® Version 11.35
Chapter 1: The Report Management System
Introduction
RMS Capabilities
Report Viewing
System Reference Guide
•
Priority may be given to packets which have time-constrained delivery, increased importance, or the need to
meet courier deadlines.
•
Each distribution produces a GLOBAL MANIFEST list that provides detailed information on all reports
distributed by media type.
•
Selective display of manifest information by media type is available on-line.
NOTE: Reports may be delivered to any output media supported by your operating system.
Report Viewing
CHAPTER 1: INTRODUCTION
•
Notes may be attached to any line of a report.
•
80 and 132 character screen support.
•
Index/version list of each report.
•
Report reformat via column selection.
•
Simultaneous viewing in up to four windows (8 reports in each window). Both horizontal and vertical aspect
viewing are supported.
•
Scroll left/right up/down in both LINE and PAGE mode.
•
Secured viewing by user/location permits a user to view only certain columns of a report.
•
USER VIEWS that can perform automatic formatting of a report at the time the report is accessed. Any
number of USER VIEWS can be stored and retrieved by each user.
•
FIND character string (FIRST, LAST, NEXT, PREV).
•
NOTE (bookmark) a specific report page/line/column.
•
RECALL a noted location.
•
ZOOM a window (expand to full screen, contract).
•
Header hold and scale line.
NOTE: RMS gives you true windowing, not just split-screens. Up to four windows at one time. Screens
can be split vertically, making it easy to compare one report to another.
•
All reports distributed by RMS, regardless of the media, may be printed/reprinted as required. Reports
which are no longer on-line are retrieved from the appropriate archive dataset.
•
On-line reports may be printed by selective page range. All the user need do is mark the page ranges to be
printed during the viewing session.
•
Selectively printed reports may be reformatted using the column select command. Reports secured by a
system administrator using the Administrative Format Save command are printed in column secured format.
•
Reports which have been de-staged from the repository may be reloaded for viewing. Reloaded reports
appear in the same access group and location as the original report. All reloaded reports are placed under the
report ID “RELOADED”. Reloaded reports that show up in this scratchpad area will appear on the index list
with a description that indicates the original report id, and distribution date and time.
NOTE: Any report packet or page range of any packet may be placed on-line or downloaded
automatically to a personal computer attached to your network.
36
© 2013 Mantissa Corporation. All rights reserved.
Chap_01(v11r35m1).fm: Revised Sunday, November 24, 2013
Report Printing and Reload
RMS/Online® Version 11.35
Chapter 1: The Report Management System
System Reference Guide
Introduction
RMS Capabilities
Archive / Recovery
Archive / Recovery
RMS supports BASE archive, Packet archive, and Retention-based archive. The characteristics of these will be
discussed in detail in Chapter 4. Some of the significant archive characteristics include:
•
Archived reports are compressed for storage efficiency (30 to 70%).
•
Packet archive for a snapshot of all reports for all medias in the entire distribution.
•
Group archive that stores like-retention data in the same data set. SMS compatible.
•
Any report you distribute, regardless of the media type, can be recovered.
•
Recovered reports retain original production attributes unless overridden.
•
Recovered reports may be reloaded to viewable status.
•
In the case of the recovery of an entire packet, original packet structure is retained.
Help Facilities
Chap_01(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 1: INTRODUCTION
RMS contains a fully integrated HELP management system that puts usable information on the system at the
operator's fingertips. Additional help facilities may be added by the installation and customized for its environment.
© 2013 Mantissa Corporation. All rights reserved.
37
RMS/Online® Version 11.35
Chapter 1: The Report Management System
Introduction
Report Processing Cycle
Capture
System Reference Guide
REPORT PROCESSING CYCLE
Discussions in this book relating to the management of reports by RMS relate directly to the report processing cycle
outlined in the following diagram. This diagram is useful in giving you a big picture of the order and objectives of
Distribution Definition
Start
Capture
Purge
Storage space Released
Index
for Base Datasets
Archive
retention-based for Base Datasets
Repository Purge
Space Released
Distribution
Report Processing Cycle
Index
CHAPTER 1: INTRODUCTION
for Distributed Datasets
Archive
Archive
Distributed Reports
Demand for Base Datasets
Index Maintenance
Version Management
Viewing / Printing
Recovery / Reload
Distributed / Base Datasets
Denotes recurring operation.
each step in the processing cycle. Take the time to review this diagram and the short descriptions of each process in
the cycle.
RMS automatically recognizes and captures report datasets placed under its control. This capture process is
accomplished either through a subsystem interface or the external writer interface facility provided by your job entry
system (JES2/JES3 or VSE/Power).
The RMS subsystem interface bypasses JES completely and captures SYSOUT directly from the application system.
RMS subsystem intercepts the report information the same way as JES2.
The external writer interface offers another method of placing report information to be managed in the RMS
repository. The external writer operates as a started task in the RMS Controller Region and retrieves application
reports based on the selection criteria it has been requested to service. Output from multiple applications may be
directed to RMS concurrently. Once the dataset created by the application has been successfully compressed and
stored in the RMS repository, the original entry is purged from the JES spool.
38
© 2013 Mantissa Corporation. All rights reserved.
Chap_01(v11r35m1).fm: Revised Sunday, November 24, 2013
Capture
RMS/Online® Version 11.35
System Reference Guide
Chapter 1: The Report Management System
Introduction
Report Processing Cycle
Distribution Definition
Distribution Definition
The distribution definition process is accomplished using the Distribution Definition component of RMS.
Distribution definition is a recurring operation that is as dynamic as your environment. Search arguments are
compared to data on each page of the application output to determine page ownership. Pages with like ownership
attributes form report packets. Each packet contains ordered report pages bundled by recipient.
During RMS processing, each packet receives an identifying banner page followed by the report data, in the
requested sequence, with the correct number of copies of each report, as defined in RMS/DD. These packets are then
placed back into the JES spool using dynamic allocation or VSE segmentation.
Index for Base Datasets
As each base dataset is placed in the repository, it is assigned a fileset attribute. If the fileset attribute is null, no index
processing takes place. If a fileset attribute is assigned as the result of the fileset attribute value in the dataset profile
(for SSI processed datasets), or as the result of the DEFAULT*FILESET parameters in the RMS Controller start-up,
the file will be indexed by the index task processing datasets with that fileset attribute.
Archive Retention-based for Base Datasets
If the Base dataset is not assigned a fileset, there can be no retention-based archive processing. The fileset identifier is
assigned using the dataset profile capability in the case of SSI processed datasets, or the DEFAULT*FILESET value
in the case where the datasets are processed by the external writer interface.
If a fileset attribute is assigned to a base dataset, the dataset first has an index record created. At this point, the index
task determines whether the dataset should be archived by analyzing the retention control records for the fileset it is
servicing. If the index task determines that archive is necessary, it creates a memo for the archive task group
requesting that an archive be created for this base dataset.
Distribution
Distribution processing is usually organized around application systems. Since the successful completion of a
processing cycle is usually a significant sync point in the operations cycle, distribution is usually scheduled at the end
of an application system processing cycle or at selected points in the processing cycle. A given execution of the
distribution component may create output for any number of recipients in any and all of the media types.
Chap_01(v11r35m1).fm: Revised Sunday, November 24, 2013
Distribution processing creates an Index update set for processing by the RMS Controller index task servicing the
fileset matching that of the distribution run. The fileset for the distribution run is taken from the FSNAME value in
the QXCNTRL file. This control file must be the same control file referenced by the Control region for that fileset.
Distribution processing analyzes the reports being distributed to determine whether or not any of the reports are
subject to retention-based archive processing. If any of the reports are to be archived, a summary file for each
retention-based archive group is created. These archive group files are subsequently used as input to archive
processing for distributed datasets.
Distribution processing may also create a packet archive. Packet archives represent a great way to achieve the
recovery of an entire packet for any reports distributed. Packet archive is forced for SOFTCOPY processing and
required if any retention-based archive processing is to take place.
© 2013 Mantissa Corporation. All rights reserved.
39
CHAPTER 1: INTRODUCTION
NO FILESET = NO INDEX = NO ARCHIVE = NO AUTOMATED RECOVERABILITY
Chapter 1: The Report Management System
Introduction
Operating Environment
Index for Distributed Datasets
RMS/Online® Version 11.35
System Reference Guide
Index for Distributed Datasets
The index file created in the Distribution run is processed by the index sub-task processing index data for the fileset
assigned by the distribution run. This fileset value is taken from the FSNAME field in the QXCNTRL file that was
used in the distribution run.
Archive for Distributed Datasets
The archive summary files created by the distribution process serve as input to the RMS Control region archive tasks.
These tasks use these archive summary files to gather reports referenced in the summary files and allocate archive
files with the appropriate retention and dataset name.
Viewing / Printing / Recovery / Reload for Distributed and Base Datasets
At this point in the life cycle, base datasets that had an associated fileset and distributed datasets may be viewed or
printed. Softcopy datasets which have been purged from the repository but which still have index versions may have
the archive data reloaded for viewing or simply printed from the archive file.
Index Maintenance for Distributed and Base Datasets
As output packets are created, the report information may be placed on a Packet Archive. These reports may also be
placed in another type of archive called a Retention-Based archive. If the need to recreate a report arises, it may be
retrieved directly from the appropriate tape at a specific report/recipient level. For example, reproduce Trial Balance
for Cost Center 4 only. Any report processed by RMS can be recovered.
Archive Demand for BASE Datasets
Base datasets must be processed by the base dataset utility program RM80001 to be deleted from the repository.
Specifically, they must be archived with the PURGE option. Doing this marks the datasets to be deleted by the purge
sub-task in the RMS Controller region. Archive may take place by application or by dataset process code. A process
code is a unique 11 character stamp that is used to mark distributed or ‘spent’ datasets. If process code management is
used, the archive can simply retrieve all datasets that bear a specific process code with the assurance that the dataset
is no longer needed by any other distribution tasks.
Purge Storage space release
Operating system files space is released for archive datasets. Repository space is released on a demand basis to
achieve the desired retention for on-line datasets.
OPERATING ENVIRONMENT
Software Requirements
40
•
MVS JES2 and JES3 or VSE
•
CICS or TSO
© 2013 Mantissa Corporation. All rights reserved.
Chap_01(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 1: INTRODUCTION
Usually performed daily, index maintenance takes the form of a fileset backup (RM90007) followed by an update
mode restore (RM90008). The backup creates a snapshot of the fileset. A fileset consists of all the VSAM files,
(Administrative Control Dataset, Distribution Control dataset, Report Control dataset), and the associated data
objects in the repository. Once this snapshot is safely in hand, the restore program analyzes the index records on the
backup file and creates an index maintenance file that tells the index and purge tasks in the RMS control region
whether to delete the index, delete the data, or both.
RMS/Online® Version 11.35
Chapter 1: The Report Management System
System Reference Guide
•
Introduction
Operating Environment
Hardware Requirements
VSAM
Hardware Requirements
A processor that supports either MVS or VSE
•
IBM 3270 display terminals (3277 model 2, 3278 models 2-5, 3279 models 2-3, 3178) or compatible
terminals with program function keys
•
A method of uploading binary files to the mainframe
•
15 megabytes of DASD space to store the distribution libraries.
Chap_01(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 1: INTRODUCTION
•
© 2013 Mantissa Corporation. All rights reserved.
41
Chapter 1: The Report Management System
Introduction
Operating Environment
Hardware Requirements
RMS/Online® Version 11.35
System Reference Guide
Chap_01(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 1: INTRODUCTION
42
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 2: Report Data Capture
Quick Start Checklist
Placing Reports in the RMS Repository
Assigning Meaningful Names to report datasets
System Reference Guide
Chapter 2
R E P O R T D A TA C A P T U R E
Quick Start Checklist
This chapter contains detailed information relating to how you capture report data for subsequent management by
RMS and how to manage the RMS/ Controller.
Are you on track? By now you or someone assisting you in the installation of RMS should have completed the
following tasks.
System Installation. This includes program installation and customization of the system. See the installation manual
for complete details.
1.
See that you have started the subsystem.
2.
Test files are loaded. This is part of the installation procedure.
3.
RMS/Online System Administration should be available through CICS or TSO.
4.
The RMS Control region is active. Make sure before starting the control region, that you clearly understand the
implications. Starting the control region with a class/destination selection attribute that is in use as a production
class will cause information in that class to be accessed, placed in the repository, and deleted from JES. At best
you will irritate a lot of people. At worst you could cost yourself hours of time trying to figure out what happened
to the reports. If at all possible, select a class or class/destination that is not currently in use.
At a minimum, you should know or have access to the following information:
SYSTEM VALUE/ATTRIBUTE
Subsystem ID
Subsystem Task Name
Controller Task Name
Selection Class/Destination
VALUE /ATTRIBUTE
YOUR INSTALLATION
__________
__________
__________
Class ____ Dest________
EXAMPLE
R135
R1135SUB
R1135CTL
R Class LOCAL Dest
PLACING REPORTS IN THE RMS REPOSITORY
Before we discuss how to place reports in the RMS repository, let’s spend a moment on what they will be called once
they get there. The naming scheme for reports processed by RMS should follow a convention that is meaningful and
designed to allow the installation to take advantage of selection options used by the various RMS systems. Reports
moved from the application program to the RMS repository are named by the SYSOUT DD statements in an
application’s job control or by using the RMS dataset profile facility. This allows for easy retrieval and processing
within the RMS system.
© 2013 Mantissa Corporation. All rights reserved.
43
CHAPTER 2: REPORT DATA CAPTURE
Chap_02(v11r35m1).fm: Revised Sunday, November 24, 2013
Assigning Meaningful Names to report datasets
RMS/Online® Version 11.35
Chapter 2: Report Data Capture
Quick Start Checklist
Placing Reports in the RMS Repository
How Repository Attributes Are Assigned
System Reference Guide
BASE Dataset Name
EXAMPLE:
CAG10001
where:
CA
G1
0001
User application cost accounting
Processing group one (1) i.e., district, region, courier deadline
Serial number of report within the processing flow.
A dataset name similar to this example is meaningful since the elements that make up the dataset name include an
application prefix (CA) and a processing group identifier (G1). This makes it immediately recognizable. In addition,
it provides for two levels of report selection using generic qualifiers:
All datasets having the application prefix CA
DS PREFIX = =>CA
or
All datasets having the application prefix CA and the processing group ID G1:
DS PREFIX = =>CAG1
or
All reports with names containing the processing group ID G1:
DS PREFIX = =>**G1
Special care should be taken to ensure that the national character “@” is not used as the first character of the name.
This character is reserved for RMS checkpoint datasets.
How Repository Attributes Are Assigned
CHAPTER 2: REPORT DATA CAPTURE
44
BASE DATASET NAME
A 1 to 8 position name used with the dataset number to
uniquely identify a dataset. This name originates from the
report name sub-parameter of the DD statement used to define
the SYSOUT file to the spooling subsystem. If the report name
sub-parameter was omitted, the report name defaults to the
name of the job that created it.
DATASET NUMBER
This is a 7 digit number assigned by the RMS Subsystem to
ensure report identifier uniqueness.
REPOSITORY DATE AND TIME
This is the date and time the writer stored the first line of the
dataset. These attributes are used internally by the Report Management Software.
CLASS
This is the output class of the report.
FORM IDENTIFIER
The forms code specified in the Job Control DD statement at
© 2013 Mantissa Corporation. All rights reserved.
Chap_02(v11r35m1).fm: Revised Sunday, November 24, 2013
As the selected SYSOUT datasets are stored in the repository, they are assigned report attributes. These attributes
define the logical and physical characteristics of the report. These attributes and their origin are as follows:
RMS/Online® Version 11.35
System Reference Guide
Chapter 2: Report Data Capture
Quick Start Checklist
Placing Reports in the RMS Repository
How Repository Attributes Are Assigned
the time the report was spooled to the Host Subsystem.
COPY COUNT
The number of report copies specified in the Job Control statement.
The Remote Job Entry Site identifier specified in the DEST
sub-parameter of the Job Control DD statement that created the
SYSOUT dataset.
JOB NAME
The name of the job executed to create this report entry.
JOB NUMBER
The JES job number of the creating job.
Chap_02(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 2: REPORT DATA CAPTURE
DESTINATION
© 2013 Mantissa Corporation. All rights reserved.
45
Chapter 2: Report Data Capture
RMS/Online® Version 11.35
Quick Start Checklist
Placing Reports in the RMS Repository
Data Capture Schematic
System Reference Guide
Data Capture Schematic
Refer to the following schematic when reading the paragraphs relating to capture of datasets.
RMS SYSOUT Capture
Via External Writer Interface
External Writer
Application
Job
JES
Spool Dataset
//DDNAME DD SYSOUT =(Q,INRO1)
RMS
Repository
Via Subsystem Interface
JES
Subsystem
CHAPTER 2: REPORT DATA CAPTURE
Application
Job
46
F
I
L
T
E
R
RMS
Subsystem
JES
Spool Dataset
© 2013 Mantissa Corporation. All rights reserved.
Chap_02(v11r35m1).fm: Revised Sunday, November 24, 2013
R
M
S
RMS/Online® Version 11.35
Chapter 2: Report Data Capture
Quick Start Checklist
Placing Reports in the RMS Repository
Capturing Report Datasets with the Subsystem Interface
System Reference Guide
Capturing Report Datasets with the Subsystem Interface
The RMS Dataset Profile capability permits you to select which SYSOUT datasets are to be processed by the RMS
subsystem. Specific dataset attributes are established in a table of dataset profiles. As application JCL is processed,
attributes of the Job and individual DD statements are presented to JES Exit 6 where SYSOUT attributes are
compared to the dataset profiles. A match in attributes will route the dataset directly to the subsystem repository or
they may be routed to RMS/Spool for subsequent delivery to a VTAM printer, attached PC, or FTP node. If there is
no match the dataset is routed to JES. The Dataset Profile panel in the RMS/Online facility is used to enter a dataset
profile or alter an existing profile. The following discussion will specify how this optional redirection takes place.
NOTE: It is NOT possible to send the same SYSOUT dataset to both subsystems.
Dataset profiles are used by JES Exit 6 to re-route JES output to the RMS or ESF subsystem.
To view all existing dataset profiles, select option 4 (Sysout/Report Management) from the main on-line menu and
then specify “LP” for (List Dataset Profiles). A listing of all existing profiles will be displayed. You may change a
profile by placing a “C” in the column next to the profile to be changed. The Dataset Profile section of RMS/Online
works the same way as all other System Administration transactions.
Specifying Capture Criteria
From main menu option 4 (Sysout/Report Management), enter “AP” for Add Dataset Profile. A blank Dataset Profile
panel will be displayed. The screen has two major parts: Selection Attributes and Attributes to be Assigned. The
following discussion will explain the use of each panel.
Selection Attributes
JES Exit 6 compares all SYSOUT datasets against a storage resident table of the dataset profiles. The comparison is
against the selection attributes of each dataset profile record. The exit makes its comparison such that a more specific
selection specification for a SYSOUT dataset will be used before a more general one. This allows you to specify
default selection attributes for SYSOUT datasets. The following table summarizes the order in which JES Exit 6
groups the dataset profile Selection Profiles for comparison against the JES SYSOUT datasets. Dataset profiles
which specify more selection attribute fields are compared first and dataset profiles which only specify an output
class are compared last. An ‘X’ in the tablerepresents a comparison. If therw is no ‘X’, a comparison will not be
made. For example, if FCB was to be checked, all other values must be specified in the dataset profile.
1
2
3
4
5
Job Name
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Chap_02(v11r35m1).fm: Revised Sunday, November 24, 2013
Proc Name
Step Name
DD Name
Class
Destination
Form
FCB
Writer Name
© 2013 Mantissa Corporation. All rights reserved.
6
7
8
9
X
X
X
X
X
X
X
X
CHAPTER 2: REPORT DATA CAPTURE
COMPARISON ORDER
ATTRIBUTE
47
RMS/Online® Version 11.35
Chapter 2: Report Data Capture
Quick Start Checklist
Placing Reports in the RMS Repository
Capturing Report Datasets with the Subsystem Interface
System Reference Guide
Completing Selection Fields
The fields for selection attributes correspond to the actual SYSOUT attributes. At least one field must be entered.
Spaces in a field specify that the attribute is not to be used in the comparison. Some fields allow a variable
designation. This means that the field will return a match condition in the comparison if any value exists in that
attribute for the SYSOUT dataset. Those fields and the appropriate variable designation are summarized in the
following table. These designations may be used to complete the assigned attributes described later.
ATTRIBUTE FIELD
VARIABLE NAME
Job Name
Proc Name
Step Name
DD Name
Class
Destination
Form
FCB
Writer Name
&JOB
none
none
none
none
&DEST
none
none
&XWTR
Job Name may contain the prefix indicator ‘*’. This allows a selection based upon a beginning portion of the Job
Name. The following are valid wild card designations:
A*
Select all datasets whose job names begin with A.
ABC*
Select all datasets whose job names begin with ABC.
ABCD*
Select all datasets whose job names begin with ABCD.
Attributes To Be Assigned
CHAPTER 2: REPORT DATA CAPTURE
48
ACCESS GROUP
Specify the Access Group in which to place this SYSOUT dataset. The default
value is “DEFAULT”. So that these are common across all installations, please
use RMSC0000.
LOCATION
Specify the Location in which to place this SYSOUT dataset. The default
value is “DEFAULT”. So that these are common across all installations, please
use RMSC0000.
REPORT ID
The report ID to assign to this SYSOUT dataset. The default value is
“DEFAULT”.
DATASET NAME
The report repository Dataset Name to assign to this SYSOUT dataset. This is
the name used by the RM80001 and RM80004 programs in the SELECT
statements. Default value is “DEFAULT”.
CLASS
The class to associate with this dataset. The default value is the JES class. If
Owner is RMSCBASE, and Destination is RMSC0004 and the Class is left
blank, the default is P to indicate that the dataset should have an index entry
added to the RCDS (Report Control Dataset).
FORM
The form name to associate with this dataset. The default value is the JES form
name.
© 2013 Mantissa Corporation. All rights reserved.
Chap_02(v11r35m1).fm: Revised Sunday, November 24, 2013
Once JES Exit 6 determines that a sysout dataset matches an entry in the dataset profile table, the SYSOUT dataset
may have certain attributes assigned to it. Some of these attributes are specific to RMS/Online and others are
replacements for standard JES SYSOUT attributes. The bottom portion of the Dataset Profile panel allows you to
specify as few or as many of these attributes as you wish. If an attribute field is left blank the default value is
assigned. The attributes and defaults are:
RMS/Online® Version 11.35
Chapter 2: Report Data Capture
Quick Start Checklist
Placing Reports in the RMS Repository
Capturing Report Datasets with the Subsystem Interface
System Reference Guide
FCB
The FCB name for this dataset. The default value is the JES FCB name.
EXTERNAL WRITER
NAME
This is an alternate external writer name to give to the dataset. This is useful if
the dataset is going to RMS/SPOOL and a different external writer name is
needed.
SUBSYS
This is the subsystem to pass the dataset to after assigning new attributes. To
place the SYSOUT dataset into the RMS report repository specify your site’s
name assigned to the RMS subsystem. In order to send a dataset to RMS/
SPOOL, specify your site’s Subsystem ID for the RMS/SPOOL subsystem. A
default value may be passed via the ‘S=’ parameter on the INST11
JOB. (Reference the Installation section of this manual). If a value is
not entered and no default set, the dataset will remain in JES.
OWNER
Specifies the owner of the dataset. This must be equal to “RMSCBASE” for all
datasets sent to the RMS Subsystem. Other values are acceptable if the dataset
is going to RMS/SPOOL.
DESTINATION
This specifies the destination of the dataset. This must be equal to
“RMSC0004” for all datasets sent to the RMS Subsystem. If the dataset is
going to RMS/SPOOL, specify the printer node to receive the dataset.
FILESET
Specifies the fileset to associate the sysout dataset(s) to. A fileset consists of a
QXCNTRL dataset and a set of VSAM files (i.e., QXACDS, QXDCDS,
QXRCDS).
ATTRIBUTE
ACCEPTED VARIABLES
Access Group
Location
Report ID
Dataset Name
Class
Form
FCB
XWTR
SUBSYS
Owner
Destination
FileSet
none
none
&XWTR; &JOB
&XWTR; &JOB
none
none
none
none
none
none
none
none
CHAPTER 2: REPORT DATA CAPTURE
Chap_02(v11r35m1).fm: Revised Sunday, November 24, 2013
Some output fields accept variables for their value. This decreases the number of specific dataset profiles needed. The
valid variable names are specified in the Selection Attribute discussion. The fields accepting variables are
summarized in the following table.
NOTE: The source code for JES Exit 6 is included in the source library supplied with the product. It is
possible to change the manner in which SYSOUT datasets are handled in this exit.
© 2013 Mantissa Corporation. All rights reserved.
49
RMS/Online® Version 11.35
Chapter 2: Report Data Capture
Quick Start Checklist
Placing Reports in the RMS Repository
Capturing Report Datasets with the External Writer Interface
System Reference Guide
The following example of a Dataset Profile panel is used to select the SYSOUT for all SYSOUTs having an external
writer name and a class designation of 3. These SYSOUT datasets will be placed into the report repository for
immediate viewing under Access Group RMSC0000 and Location RMSC0000. The Report ID will be the same as
the external writer name. The dataset name referenced by RM80001 and RM80004 will be the same as the external
writer name.
R.M.S. - Dataset Profile Management
Mode: ADD
Selection Attributes:
Jobname_ ProcStep Step____
Attributes To Be Assigned:
AccessGP Location ID_____
RMSC0000 RMSC0000
Owner___ Dest____ FileSet_
RMSCBASE RMSC0004 FSET01
Date: Tuesday,
10/08/96 Time: 16:56:10
----------------------------------------
DDName__ C Dest_____________ Form FCB_ XWTR____
3
&XWTR
ReportID DSName__ C Form Fcb_ Xwtr____ SubSys__
&XWTR
&XWTR
R135
PF1=Help PF3=End
RM9134I Enter information for new record.
Panel 1 of 1
Capturing JOBLOG Datasets
A JOB statement MSGCLASS may be captured and routed to an alternate JES Writer Class. This capability is
implemented by adding a Dataset Profile record with the Selection Attributes of DDName “MSGCLASS” along with
the selected class and the Selection Attributes To Be Assigned as the Class to be substituted. Only these three fields in
the Dataset Profile record should be coded for the substitution to function properly.
As an example, suppose we want to route any jobs with the JOB statement MSGCLASS specified as U to be routed to
Class V. Through the RMS/ONLINE Dataset Profile Management, create a record with the Selection Attributes of
DDName, MSGCLASS and Class U and specify in the Attributes to Be Assigned area, Class V.
CHAPTER 2: REPORT DATA CAPTURE
The most important aspect of the Transport processing subtask is the designation of the report selection criteria.
Selection may be based on SYSOUT class(es) or destination id. If selection is by class, the Transport subtask will
retrieve all reports within the designated class(es). Conversely, if only a destination is used, then reports for that
destination will be retrieved regardless of SYSOUT class. A combination of class(es) and destination will service
only those reports for the specified class(es) and destination. Whatever the selection criteria used, it is important that
only those reports to be processed by RMS have these selection characteristics.
The reason for routing reports to RMS may be for back-up purposes only. In this case the best approach for selection
might be to use destination selection. This would allow the installation to insert an “OUTPUT” JES statement in jobs
requesting dual routing, one for local print, the other for writer selection.
50
© 2013 Mantissa Corporation. All rights reserved.
Chap_02(v11r35m1).fm: Revised Sunday, November 24, 2013
Capturing Report Datasets with the External Writer Interface
RMS/Online® Version 11.35
Chapter 2: Report Data Capture
Quick Start Checklist
Placing Reports in the RMS Repository
Capturing Report Datasets with the External Writer Interface
System Reference Guide
The job control modifications necessary for storing reports in the RMS Repository are limited to SYSOUT DD
statements. In order to route a report to RMS, its SYSOUT DD statement must be changed to match the writer
selection criteria. In addition, whenever applicable, the “FREE=CLOSE” parameter should be specified to direct JES
to schedule the SYSOUT for output dispatching at the time it is closed instead of waiting for job termination. Doing
this will enable the dataset drain by the Transport subtask to overlap production processing.
The SYSOUT from an entire job, or from specific DD statement within the job, may be routed to RMS. The two
methods that can be used to route report data are outlined in the following paragraphs.
Method 1 - Routing Individual SYSOUTS
In order to route selective reports from a job, the user would simply change the SYSOUT value(s) of the desired
reports.
This method is preferred because it creates a more concise and manageable directory of repository datasets. For
example, if 15 entries were created during a job, they would all have the same name using Method 2. This creates
serious limitations in the management, selection, and recovery of these datasets. Method 1, on the other hand, permits
the assignment of unique names to each entry giving maximum management flexibility.
Routing SYSOUT to RMS and Assigning Unique Names:
//jobname
//STEP1
//ddname1
//STEPn
//ddname3
JOB(whatever),MSGCLASS=A
EXEC PGM=pgmname
DD SYSOUT=(X,reportname),FREE=CLOSE
EXEC PGM=pgmname
DD SYSOUT=(X,reportname),FREE=CLOSE
where:
in //ddname1 statement:
X
is the class assigned.
(reportname)
is an optional report name that the user can assign to uniquely reference the
report(s) created by this DD statement. If omitted, the report name defaults to
jobname.
FREE=CLOSE
permits early writer processing.
NOTE: If a SYSOUT dataset is opened and closed multiple times during the job execution
FREE=CLOSE must be omitted.
In order to route all of a job’s report output to RMS, the user need only specify a class being serviced by the writer in
the appropriate Job Control Language statement.
This could be as simple as specifying the output class on the Job Card, for a job using only one class.
Method 2 is NOT the recommended method. Method 1, using the reportname field in the SYSOUT DD statement, is
the preferred approach because of the additional report management capabilities it provides.
Routing All Job SYSOUT to RMS
//jobname
//STEP1
//ddname
© 2013 Mantissa Corporation. All rights reserved.
JOB (,,,,FFFF,CCC),MSGCLASS=X
EXEC PGM=pgmname
DD SYSOUT=*,FREE=CLOSE
51
CHAPTER 2: REPORT DATA CAPTURE
Chap_02(v11r35m1).fm: Revised Sunday, November 24, 2013
Method 2 - Routing All SYSOUT Data for a Job
RMS/Online® Version 11.35
Chapter 2: Report Data Capture
Quick Start Checklist
RMS Controller
Overview
System Reference Guide
//STEP2
//ddname2
EXEC PGM=pgmname
DD SYSOUT=(*,,FFF2),COPIES=1,FREE=CLOSE
where:
in //jobname statement
FFFF
is the default forms type to be used if one is not specified on the SYSOUT DD
statement.
CCC
is the default copy count to be used if once is not specified on the SYSOUT
DD statement.
X
is the class to be used for all SYSOUT report routing unless overridden on the
SYSOUT DD statement.
in //ddname statements
*
indicates that the class specified in the MSGCLASS parameter on the JOB
card is to be used for the routing of this report.
uses the installation forms, etc. or job card overrides.
FFF2
is an overriding forms type to be used for this report.
COPIES=1
is an overriding copy count for this report.
NOTE: For a more detailed description of these fields, see the Job Control Language Reference
Manual for your OS/MVS operating system.
RMS CONTROLLER
Overview
CHAPTER 2: REPORT DATA CAPTURE
1.
Transport processing (writer)
2.
Purge processing
3.
Index processing
4.
Output processing (services all Online print requests)
5.
Recovery processing (processes archived datasets for reprint/restore)
6.
Archive processing (manages datasets with an associated fileset)
The Transport subtask component of RMS provides communication and data transfer functions between the Job
Entry Subsystem (JES) and the repository. The subtask requests SYSOUT datasets from JES based on the selection
criteria specified by the user. These requests use the standard subsystem interface.
52
© 2013 Mantissa Corporation. All rights reserved.
Chap_02(v11r35m1).fm: Revised Sunday, November 24, 2013
The following functional components operate under the started task name of RvvrmCTL (where vvrm is the version
and release level). This is the name of the procedure delivered as part of the installation material for RMS. The
controller manages the following tasks:
RMS/Online® Version 11.35
System Reference Guide
Chapter 2: Report Data Capture
Quick Start Checklist
RMS Controller
Overview
The selection process is based on SYSOUT class and/or destination ID parameters supplied by the user. The selection
values are specified at the time the RvvrmCTL procedure is started. In addition, new selection values may be entered
at any time using the MVS MODIFY command.
Chap_02(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 2: REPORT DATA CAPTURE
Once a SYSOUT has been selected, it is moved from JES to the RMS repository. This repository is managed by the
RMS Subsystem. If the dataset does not have the same class as designated in the JOBLOG*CLASS parm of the
RvvrmCTL started procedure, it is added to the repository as a BASE dataset.
© 2013 Mantissa Corporation. All rights reserved.
53
Chapter 2: Report Data Capture
Quick Start Checklist
RMS Controller
Task / File Relationship Schematic
RMS/Online® Version 11.35
System Reference Guide
Task / File Relationship Schematic
From the standpoint of task structure and file relationships, the control region is structured as indicated in the
following diagram.
Chap_02(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 2: REPORT DATA CAPTURE
54
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 2: Report Data Capture
Quick Start Checklist
RMS Controller
Specifying Options
System Reference Guide
Specifying Options
The RMS Controller accepts options from SYSIN, the execute PARM field, or both. Some of the options are valid
only at initial start-up of the controller. Others may be specified on the modify command (MVS) or in response to an
outstanding message number in the case of VSE. The commands fall into two categories; Process control commands
and Log control commands. The following table contains information relating to the commands and the point at
which the parameter may be entered.
RVVRMCTL PROCESS CONTROL COMMANDS
FUNCTION
ACCEPTABLE VALUES
ARCHIOFF
Used to turn off archive
processing.
Used to turn off a specific
archive task. N = 1-3.
Used to control writer
dataset selection.
N/A
No
N/A
No
From 1 to 8 classes;
CANCEL
Yes
Used to control writer
dataset selection.
Valid Destination;
CANCEL
Yes
Used to designate the name
of the processing exit for
each dataset retrieved by the
writer.
FileSet name for WRITER
datasets.
Load Module Name. Note:
must be authorized.
No
CLASS
C
DEST
D
EXIT (eeeeeeee)
DEFAULT*FILESET
FS01 - FS08
Used to specify the FileSet
association for viewable
datasets.
INDEX*LOCK*SPAN (nnnnn)
Sets the number of
consecutive write operations
to the FILESET RCDS file
before the file is de-queued.
Used to turn off index
processing.
Used to turn off a specific
index task. n=1-8.
Used to control writer
dataset selection.
INDEXOFF
INDXnOFF
JOBLOG*CLASS
JC
OUTPTOFF
OUTPnOFF
PROCESS*GROUP
Used to turn off output
processing.
Used to turn off a specific
OUTPUT task. N= 1-2.
Used to establish writer
process group.
CANCEL
1 - 8 character fileset name
to be assigned to all datasets.
Blanks and special
characters are not allowed.
1 - 8 character alphameric
name of a DD statement in
the control region JCL
which points to the control
file for a fileset.
Blanks and special
characters are not allowed.
100-10000
No
No
No
N/A
No
N/A
No
From 1 to 8 classes;
CANCEL
Yes
N/A
No
N/A
No
1 to 4 character process
group identifier.
No
CHAPTER 2: REPORT DATA CAPTURE
ARCHnOFF
Chap_02(v11r35m1).fm: Revised Sunday, November 24, 2013
MAY BE CHANGED
WITH MODIFY
COMMAND
COMMAND
PG
© 2013 Mantissa Corporation. All rights reserved.
55
RMS/Online® Version 11.35
Chapter 2: Report Data Capture
Quick Start Checklist
RMS Controller
Specifying Options
System Reference Guide
RVVRMCTL PROCESS CONTROL COMMANDS
MAY BE CHANGED
WITH MODIFY
COMMAND
COMMAND
FUNCTION
ACCEPTABLE VALUES
PURGEOFF
Used to turn off purge
processing
Used to turn off recover
processing.
Used to turn off a specific
recovery task. N= 1-2
Used to turn on writer
processing.
Used to turn off writer
processing.
N/A
No
N/A
No
N/A
No
N/A
No
N/A
No
RECOVOFF
RECOnOFF
TPORTON
TPORTOFF
RVVRMCTL LOG CONTROL COMMANDS
ACCEPTABLE VALUES
ARCHIVELOG*LIMIT
Used to control the number
of lines written to the
ARCHIVE log file before
the log is closed and reopened.
Used to control the number
of lines written to the
INDEX log file before the
log is closed and re-opened.
Used to control the number
of lines written to the
OUTPUT log file before the
log is closed and re-opened.
Used to control the number
of lines written to the
PURGE log file before the
log is closed and re-opened.
Used to control the number
of lines written to the
RECOVER log file before
the log is closed and reopened.
Used to control the number
of lines written to the
STATUS log file before the
log is closed and re-opened.
Used to control the number
of lines written to the
TRANSPORT log file
before the log is closed and
re-opened.
500 - 999,999
Yes
500 - 999,999
Yes
500 - 999,999
Yes
500 - 999,999
Yes
500 - 999,999
Yes
500 - 999,999
Yes
500 - 999,999
Yes
INDEXLOG*LIMIT
ILL
OUTPUTLOG*LIMIT
OLL
PURGELOG*LIMIT
PLL
RECOVERLOG*LIMIT
RLL
CHAPTER 2: REPORT DATA CAPTURE
STATSLOG*LIMIT
SLL
TRANSLOG*LIMIT
TLL
© 2013 Mantissa Corporation. All rights reserved.
Chap_02(v11r35m1).fm: Revised Sunday, November 24, 2013
FUNCTION
ALL
56
MAY BE CHANGED WITH
MODIFY COMMAND
COMMAND
RMS/Online® Version 11.35
Chapter 2: Report Data Capture
Quick Start Checklist
RMS Controller
Starting, Modifying, and Stopping the Controller Task
System Reference Guide
RVVRMCTL LOG CHARACTERISTIC COMMANDS
COMMAND
FUNCTION
STATS*CLASS
Used to control the output
N/A
CLASS of the control region
logs.
Used to control the
N/A
DESTINATION of the
control region logs.
Used to close and re-open
N/A
all the log files.
To close and open individual
log files enter the first three
bytes of the log file name
(i.e., PUR, REC, TRA,
ARC, IND, or OUT).
STATS*DEST
WL (ALL)
ACCEPTABLE VALUES
MAY BE CHANGED WITH
MODIFY COMMAND
N
N
Yes
Starting, Modifying, and Stopping the Controller Task
The Controller Task is managed with the following commands:
Start (S)
Initiate Processing
Modify (F)
Modify Processing Criteria
Stop (P)
Terminate Processing
Task Initiation
The controller is initiated by entering a standard start command from the operator console. The format of this
command is as follows:
START/S PPPPPPPP,OPTION='keywords'
•
PPPPPPPP identifies the procedure name. If utilizing the procedures supplied on the installation tape, this
name is RvvrmCTL.
•
OPTION= allows entry of controller processing criteria to replace those specified in PROC statement
symbolic defaults. The symbolic label is OPTION, and the entry format is:
•
OPTION='keyword(value) keyword(value)'
•
Keywords are used to specify report selection criteria to be used in place of the default specified in the
PROC statement.
© 2013 Mantissa Corporation. All rights reserved.
CHAPTER 2: REPORT DATA CAPTURE
Chap_02(v11r35m1).fm: Revised Sunday, November 24, 2013
where:
57
RMS/Online® Version 11.35
Chapter 2: Report Data Capture
Quick Start Checklist
RMS Controller
Starting, Modifying, and Stopping the Controller Task
System Reference Guide
EXAMPLE:
1. Start RvvrmCTL
In this example, RvvrmCTL will be started as part of the RMS control region using the default selection criteria
specified on the PROC statement:
2. S RvvrmCTL,OPTION=’CLASS (Z)’.
The value entered will cause all JES SYSOUT class Z to be processed. In this example, the writer will be started
as part of the RMS control region. Notice that the options specified will override those on the RvvrmCTL procedure statement.
3. S RvvrmCTL,OPTION=’CLASS(PN)’
This command utilizes keyword operands to specify the selection criteria. The operands shown in this example
will result in the processing of JES SYSOUT for classes P and N destined for local routing.
4. S RvvrmCTL,OPTION=’CLASS(PN) PROCESS*GROUP(P1)’
This command utilizes keyword operands to specify the selection criteria. The operands shown in this example
will result in the processing of JES SYSOUT for classes P and N destined for local routing. The PROCESS*GROUP command assigns a process identifier to the writer subtask. This process identifier is used to
coordinate processing among writers started with like selection criteria.
5. S RvvrmCTL,OPTION=’CLASS(PN) INDEXOFF’
This command utilizes keyword operands to specify the selection criteria. The operands shown in this example
will result in the processing of JES SYSOUT for classes P and N destined for local routing. The INDEXOFF
option causes the main task not to initiate index processing for this execution of the controller.
6. S RvvrmCTL,OPTION=’CLASS(PN) INDEXOFF PURGEOFF’
This command utilizes keyword operands to specify the selection criteria. The operands shown in this example
will result in the processing of JES SYSOUT for classes P and N destined for local routing. The INDEXOFF
option causes the main task not to initiate index processing for this execution of the controller. The PURGEOFF
option causes the main task not to initiate purge processing for this execution of the controller.
Task Processing Criteria Modification
The processing criteria used to initiate the writer may be changed at any time via the entry of a modify command. The
command format is:
MODIFY/F PPPPPPPP,keywords
where:
•
PPPPPPPP is the procedure name specified on the start command.
•
“Keywords” are the keywords and their associated values for the selection criteria to be changed. When
“CANCEL” is specified (where it is valid), it will disable that function.
Chap_02(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 2: REPORT DATA CAPTURE
58
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 2: Report Data Capture
Quick Start Checklist
RMS Controller
Starting, Modifying, and Stopping the Controller Task
System Reference Guide
Modify Commands
EXAMPLE:
1. MODIFY RvvrmCTL,CLASS(R)
Class 'R' Override
Procedure Name
Modify Command
In this example the selection criteria is changed to Class R.
2. F RvvrmCTL,CLASS(CANCEL )
Cancel Class Override
Procedure Name
Modify Command
Here, a previously entered class selection is cancelled. If selection by destination was also
specified, processing continues with it as the criteria. (i.e... DEST(xxxx))
Task Termination
Once the writer has been started, it will continue to execute until a stop command is entered to terminate it:
STOP/P PPPPPPPP
where:
PPPPPPPP is the procedure
Stop Command
EXAMPLE:
Chap_02(v11r35m1).fm: Revised Sunday, November 24, 2013
Procedure Name
Stop Command
Modify/Stop commands are not acted upon until processing for the current SYSOUT dataset has been completed. Be
patient when a stop command is entered. All the active tasks must stop before the started task will end.
NOTE: The RvvrmCTL region should NEVER be cancelled. Doing this may damage the INDEX file
(RCDS).
© 2013 Mantissa Corporation. All rights reserved.
59
CHAPTER 2: REPORT DATA CAPTURE
1. P RvvrmCTL
RMS/Online® Version 11.35
Chapter 2: Report Data Capture
Quick Start Checklist
RMS Controller
SYSOUT Selection
System Reference Guide
SYSOUT Selection
The SYSOUT selection process is based on the following criteria:
•
Selection is based on output class and/or destination identifier.
•
Classes 0-9, A-Z may be selected.
•
No more than eight (8) selection classes per writer.
•
Any valid JES destination id may be specified.
•
Classes/Destinations are specified in the execute parm list or the console start command.
•
Classes/Destinations may be changed during processing via the modify command.
•
Held SYSOUT datasets are not selectable.
SYSOUT datasets are presented to the Transport processing subtask as discrete datasets by JES. If the
JOBLOG*CLASS parameter is included, all datasets of the specified class that do not have a specific name will be
concatenated to form one repository dataset for a job.
Log File Management
Each RMS Controller Task dynamically creates a log file to inform the user of actions taken by the task. The log files
are produced in a format easily printed or viewed.
Log files are spin disposition sysout datasets. These files are automatically closed and re-opened every nnn lines
depending on the value for the log limit set for the subtask in the start-up parms for the Controller. You may force the
log file closed by entering a modify command for the controller task using one of the following:
MVS
F RvvrmCTL,WL(ALL)
Write ALL LOG FILES
F RvvrmCTL,WL(abc)
Write INDIVIDUAL LOG FILES
Where abc is equal to the first three positions of the log file
name
(ARC, IND, OUT, PUR, REC, TRA).
CHAPTER 2: REPORT DATA CAPTURE
(msg #) WL(ALL)
Write ALL LOG FILES
(msg #) WL(abc)
Write INDIVIDUAL LOG FILES
Where abc is equal to the first three positions of the log file
name
(ARC, IND, OUT, PUR, REC, TRA)
Log files are routed based on the information in the STATS*CLASS and STATS*DEST parameters in RvvrmCTL.
60
© 2013 Mantissa Corporation. All rights reserved.
Chap_02(v11r35m1).fm: Revised Sunday, November 24, 2013
VSE
System Reference Guide
Chapter 3: Implementation Strategy
Overview
Administrator Responsibilities
Determining Report Management Requirements
Chapter 3
I M P L E M E N TA T I O N S T R A T E G Y
Overview
RMS performs ordering, routing, and output media control of report data in accordance with distribution definition
information. RMS/DD, a component of RMS/ONLINE is used to provide the information necessary to consolidate,
package, and create index information for reports that are to be distributed.
In this section we discuss the use of RM80004 as it relates to the Distribution Definition component of RMS/Online.
As such, we define a step-by-step process necessary to prepare an instruction set to distribute a group of reports.
Think of it as a cook book approach for utilizing RM80004 to meet your distribution needs.
We assume that all necessary software installation has been performed. (See RMS Installation Guide in Chapter 11.
At this point, the actual implementation of the distribution system is ready to begin. It is your responsibility to select
a group of reports for distribution by RM80004. This chapteris intended for use by the RMS/Online system
administrator and/or access group administrator.
ADMINISTRATOR RESPONSIBILITIES
Installations considering the implementation of RMS/ONLINE should note that the system requires that someone be
designated to define, control, and manage the viewing environment. Therefore, it is worth designating someone to act
as a focal point for the addition of new reports and the overall security of the reports. The system administrator for
RMS has the following major areas of responsibility:
•
Determination of report distribution requirements
•
Defining a report management structure
•
Creating and maintaining a report management database
•
System Security
•
Establishing and adjusting retention thresholds
•
Establishing archive retention requirements for reports
•
Assisting users in answering questions about RMS
Some of the tasks performed by the distribution administrator are outlined below.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
Determining Report Management Requirements
The results of any effort to add structure, efficiency and effectiveness to the management of your organization’s
reports will be questionable at best if they don’t match the real needs of the users of those reports. Very few
installations will be able or willing to quickly commit the majority of their reports for on-line viewing. Within the
framework of a management policy regarding what types of report data will be available for viewing, the system
administrator must determine those reports where on-line viewing is the most cost effective and efficient method of
presentation. Factors relating to timely presentation, availability, training of users, and number of users must be
considered.
© 2013 Mantissa Corporation. All rights reserved.
61
CHAPTER 3: IMPLEMENTATION STRATEGY
RMS/Online® Version 11.35
RMS/Online® Version 11.35
Chapter 3: Implementation Strategy
System Reference Guide
Planning a Managed Report Environment
Users of RMS have already made a decision to aggressively pursue a structured report management environment.
These users have logical groups of reports that, in the majority of cases, fall into application or time-slot categories.
RMS will allow you to add structure and organization to your output management cycle. It permits you to bring one
report at a time under its control until the desired results are achieved.
Report Management Database
You describe the basic structure of your report distribution environment to RMS/ONLINE by creating the following
types of records.
Access Group Master
This record is used to control use of certain system resources.
Location Master
The Location Master record contains data that uniquely identifies a distribution location in your organization. It also contains
default print characteristics for that particular location.
User Master
The User Master record contains the user ID and sign-on data
for a valid user of the system. The User Master also contains
security profile information.
Retention Control
Retention Control records are used to designate the retention
criteria for resident reports and report tracking information.
Distribution Definition
Defines the distribution requirements for a specific set of users.
System Security
RMS Resource Security permits the use of no security, user-defined security (via an exit facility), and security at the
access group, location and report level.
The user identification must be defined to the system unless a sign-on exit is used which provides this identification.
This user identification may be from 1 to 8 characters and you may elect to use the CICS or TSO user ID.
If a User Master is created without a password, security checking at sign-on is bypassed. In order to use any
administrative function, a particular user must be defined as an administrator.
RMS/ONLINE provides security on a promotable basis. Consider the basic security hierarchy defined in the user
master record:
ACCESS GROUP
a controlled group of reports
SECURITY GROUP
one or more users
RESOURCE TYPE
transaction, location, report
ACCESS TYPE
all or partial
A particular user is granted partial or complete access to a given resource for a given access group and security group.
Transactions and reports may be secured for given security groups. The user master record provides the basic level of
control. It specifies the access group/security group/resource combinations that are valid for a particular user. The
user may be assigned one of two types of access to a particular access group/security group/resource combination.
Type “A” (all) access permits access to all of a particular resource in an access group. Type “P” (partial) access
causes the system to validate access to the transaction or report by reading the security profile records for that
resource.
62
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Administrator Responsibilities
Planning a Managed Report Environment
System Reference Guide
Chapter 3: Implementation Strategy
Overview
Distribution Capabilities
Repository Management
Consult the documentation for Resource Security for an overall discussion of the interaction between user profile
information and security information.
Repository Management
The system administrator is responsible for controlling RMS and the reports managed by the system. Depending on
the installation, the administrator may be called upon to increase space allocations for the repository. Chapter 4
contains a discussion of additional administrative tasks relating to repository management.
DISTRIBUTION CAPABILITIES
Taken together, all components of RMS represent 350 years of development and a lot of knowledge from our
customers. There is very little in the way of report management that can’t be done with RMS. Getting the big picture
is important for your success, and for the successful implementation of the system. Your knowledge of the system and
its capabilities will have a tremendous effect on the return on investment for your enterprise.
The RMS distribution component provides the following capabilities.
Consolidation of Reports
RM80004 will combine the data from selected reports so that the reports for each distribution endpoint can be output
as one continuous stream of data. This dramatically reduces both the distribution work load and the possibility of
error. Other uses include the production of composite microfiche, mainframe mastered CDs, and transmission files.
Copy Variation
Each distribution endpoint may be given a different number of copies of the same report. This copy flexibility permits
easy response to the changing needs of the distribution network without waste or overhead.
Priority Output
Through the use of the priority command, high priority distribution endpoints may be assigned a priority to cause
their output to be produced before other endpoints. The priority scheduling of output can be useful in meeting courier
or transmission deadlines. High priority remote output might be handled in this manner.
Sending Reports
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
The Send Report capability permits report data destined for a particular distribution endpoint to be sent to additional
endpoint(s). Broadcast is useful when one report has to be routed to multiple end users.
Assignment Of Specific Output Attributes
Output attribute assignment is an important distribution capability. For instance, it implies that the report data for
multiple distribution endpoints can be produced in one sysout and have individual attributes such as class,
disposition, form, and copy count may also be assigned.
Data Stream Insertion
Through the use of simple commands, information can be inserted before, on, or after individual reports. The
insertion can be specific, limited to a report for a user, or global, all reports for all users, or any combination of the
two. This facility can be especially useful in the use of output devices that require in-stream definition commands,
i.e., page printers, on-line microfiche units. In addition, a user can customize his separator pages, supplying a report
use description or additional distribution instructions.
© 2013 Mantissa Corporation. All rights reserved.
63
CHAPTER 3: IMPLEMENTATION STRATEGY
RMS/Online® Version 11.35
RMS/Online® Version 11.35
Chapter 3: Implementation Strategy
System Reference Guide
Deletion of Unwanted Report Data
Report data that is no longer desired may be deleted. This may be accomplished by specifying a page format
identification record that indicates the deletion of an entire report, or by specifying copy count of zero for a particular
report/endpoint combination.
Selection of Total/Control Data Pages
The total or control pages of a report entry may be separately selected for distribution. Another potential use for this
facility is for the creation of a “statement of condition” report for the processing installation by extracting total or file
balancing data pages from the spooled report entries. In this way, a small report can be produced on a daily basis that
serves as an installation check-point document.
Production Of Output Separators
Distribution separators containing up to 8 blocked letters for flag data, and user defined message data may be
produced for each endpoint.
The number and presence of separators are optional. The front separator contains the word ‘START’, the date and
time the packet production was started, and the message data. The trailing separator contains the word ‘END’, the
date and time the packet production was ended and the message data.
Media Control - Softcopy, Desktop, Hardcopy, etc.
RMS supports 8 standard medias making a report available on-line is as easy as distributing that report to a user with
a media type of SOFTCOPY, Desktop delivery or reports works the same way
STEPS IN CREATING A DISTRIBUTION DEFINITION
In order to ensure a successful report management implementation, you must first identify the information necessary
and all the tasks to be performed. The following presents a possible project plan that could be used to implement
RM80004.
Step 1 - Obtaining the Necessary Information
The first task in our implementation consists of gathering information that will be needed in subsequent points in the
project cycle. This information is:
RM80004 Sample Job Control
Included on the RMS installation tape are two example job control streams. These job streams can be used as models
for your production RM80004 execution streams. They are in-stream procedures and are named:
RMSMAP
example RM80004 map job.
RMSRUN
example RM80004 distribution job that will distribute the case
study reports.
Class and/or destination ID serviced by the External Writer
The Job Entry System Interface is accomplished using the external writer. The writer is designed to retrieve data from
the Job Entry System based on pre-determined classes and/or destination ID. In order to make the job control changes
required to identify reports to be serviced by the writer, this class and/or destination must be known. This class/
destination ID was selected when the product was installed. Use of a unique destination is strictly optional. The class
used may be any class not being used by other applications.
64
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Steps in Creating a Distribution Definition
Deletion of Unwanted Report Data
System Reference Guide
Chapter 3: Implementation Strategy
Overview
Steps in Creating a Distribution Definition
Media Control - Softcopy, Desktop, Hardcopy, etc.
Step 2 - Selecting a Group of Reports
In this task we select the reports to be distributed by RM80004. This selection process involves the following steps:
Identifying a Distribution Report Group
A distribution report group consists of those reports that, due to some specific relationship, should be distributed
together. Each report group represents a logical point in the processing cycle where distribution should occur. The
relationships on which this grouping is based could be any of the following:
•
Processing schedules which require that we process groups of users for a given application. This could occur
when the input to an application is available based on a delivery schedule. In this case, distribution could be
performed by processing group.
•
Output availability schedules that require that certain reports be available for distribution at specific times
during the processing cycle. This would occur in situations where output shipment is tied to deadlines, for
example, remote transmissions, or courier routes.
•
Related information could also constitute a grouping, for example, all reports for an application processing
cycle.
First Time Users - Selecting a Benchmark Group
We should start with a few reports, maybe a small application. Remember, during the trial period we are working
within a finite time frame. Also, limiting the number of reports allows us to implement quickly, gaining confidence,
and the knowledge necessary to apply the concepts to larger conversions.
•
Upon completion of this task, copies of the selected reports must be available in the repository. Therefore,
the reports we choose must be easily reproduced, preferably by a controlled rerun or from some type of
backup media.
•
Select reports that provide the most return from your implementation efforts. The reports we choose should
be ones that cause problems for the normal distribution process. Benefits resulting from the implementation
of RM80004 will be more evident with these types of reports.
Step 3 - Capturing Selected Sysout Datasets
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
In this task, the base datasets containing the selected reports are placed in the repository. These datasets must be
available for use in subsequent tasks. The creation of base datasets may be accomplished in any of the following
manner:
•
Produced from a previously created back-up source
•
Produced as the result of a controlled re-run
•
Produced during the normal production processing cycle.
The effort involved in any of these methods depends on the operating system environment.
Report Creation for OS/MVS
Report entries are placed in the RMS repository using the external writer interface or RMS Subsystem Interface. This
processing occurs when the JES spooling sub-system encounters a report stream assigned an output class and/or
destination ID designated for processing by the RMS writer. The class and/or destination assignment is made via the
JCL SYSOUT DD statement associated with desired reports. The JCL changes necessary to trigger writer processing
are as follows:
© 2013 Mantissa Corporation. All rights reserved.
65
CHAPTER 3: IMPLEMENTATION STRATEGY
RMS/Online® Version 11.35
RMS/Online® Version 11.35
Chapter 3: Implementation Strategy
System Reference Guide
SYSOUT DD Statement
EXAMPLE:
//PRINT DD
SYSOUT=(X,REPTNAME,STK1),
//
DCB=(RECFM=FA,BLKSIZE=133),
//
FREE=CLOSE
where:
X
indicates the SYSOUT class serviced by
the writer
REPTNAME
is the unique name to be assigned to the
base dataset from the SYSOUT DD,
STK1
indicates the form name
Report Creation for VSE
Report entries are placed in the RMS repository using the transport server interface. This processing occurs when
POWER receives a report assigned to an output class/or destination ID designated for processing by the RMS
transport server. The class and/or destination assignment is made via the POWER JECL LST statement.
LST statement
EXAMPLE:
* $$ LST CLASS=X,DEST=(RMS,REPTNAME)
where:
X
indicates the class serviced by the transporter.
Regardless of the method used to produce the reports, the previously outlined JCL changes must be made. The
following procedure can be used in making these changes.
First, obtain copies of the JCL procedures that will be used to create the reports. Using these copies, we can make the
necessary changes and thoroughly test them without impacting normal production processing. In the case of the
controlled re-run or normal production cycle report create, the JCL copies can be retained for use when we place
RM80004 into production.
For MVS, scan the JCL copies to locate the SYSOUT DD statements containing the selected reports. As we
encounter these DDs, the SYSOUT class and/or destination ID are changed to indicate RMS processing.
For VSE, adding appropriate POWER JECL LST statements will segment the report(s) and allow the transporter to
process them via class/and/or destination ID.
We can also assign names to each of the SYSOUT datasets. In addition, they should be constructed in a manner that
will allow the user to take advantage of name selection options used by RM80004.
66
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Steps in Creating a Distribution Definition
Media Control - Softcopy, Desktop, Hardcopy, etc.
RMS/Online® Version 11.35
Overview
Steps in Creating a Distribution Definition
Media Control - Softcopy, Desktop, Hardcopy, etc.
System Reference Guide
EXAMPLE:
Report name
SLG10001
where:
SL
user application sales accounting
G1
processing group one (1), i.e., district, region, courier deadline
0001
serial number of report within application processing flow.
A report name patterned along the lines of this example is meaningful since it indicates the creating application
system (SL), and the processing group (G1). This makes it immediately recognizable by the operations staff for
reference purposes.
It also provides for two levels of report selection through the use of GNAME qualification. This allows the user to
specify selection of all reports whose names carry the application prefix:
DS PREFIX ==> SL
or
All reports whose name is prefixed by the application and processing group values:
DS PFEFIX ==> SLG1
or
All reports whose name includes the processing group ID:
DS PREFIX ==> **G1
and
Of course, full name selection may also be used:
DS NAME ==> SLG10001
Special care should be taken to ensure that the character “@” is not used as the first character of a base dataset.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
Once the JCL changes have been made and tested, we should schedule an actual report creation run.
•
Ensure that the writer task is started during the report creation process. This is necessary in order for JES/
POWER to route the report data streams to the repository.
•
If reports produced as the result of a normal production processing cycle must be printed in addition to being
placed in the managed dataset, you must run a RMS/ARC report print execution that returns a copy of the
report(s) to JES/POWER for subsequent printing. The managed dataset copy is left intact.
Step 4 - Determining Distribution Requirements
In this task, we gather the information necessary to define our distribution requirements to RM80004. This
information may be obtained via interview sessions with the individual currently responsible for distribution. The
report recipient is an even better source of information. Many times reports are produced which are no longer needed
and a telephone interview with the user will uncover their real needs. Upon completion of the interviews, we should
have the data necessary to define our distribution key format to RM80004.
© 2013 Mantissa Corporation. All rights reserved.
67
CHAPTER 3: IMPLEMENTATION STRATEGY
Chapter 3: Implementation Strategy
Chapter 3: Implementation Strategy
RMS/Online® Version 11.35
System Reference Guide
Interview Sessions
The majority of our questions are directed to those currently handling output distribution. However, depending on
any microfiche and/or RJE transmission requirements, there may be individuals in other areas to interview (i.e.,
Technical Support, Application Programming, Production Control).
Several pages of subject reports may be needed for reference as we conduct our interviews. As a result of the previous
task, our reports are now in the repository. We simply need to request a copy of each to be printed. This can be
accomplished by:
1.
Submitting a report print job. Since an RMS/ARC print request does not delete reports, they will be available for
later use.
2.
Viewing the captured report at a terminal.
We are now ready to begin our interview sessions. The following questions provide an outline for the topics to be
discussed:
Report Ownership
1.
To whom are the reports distributed?
2.
What information from the report pages, if any, do you use in determining ownership (i.e., client name/number,
department name/number, etc.)?
3.
What external information sources, if any, do you use in determining report ownership (i.e., distribution control
list, memory, etc.)?
Report Breakdown
1.
Does every distribution recipient receive complete copies of each report?
2.
Do the reports require further breakdown based on values from each report page (i.e., by company, department,
bank, branch, etc.)?
Special Handling
1.
What is the normal number of copies of each report the distribution points are to receive?
2.
Which distribution endpoints receive a number of copies differing from the norm?
3.
Are copies of an endpoint report distributed to another endpoint?
4.
Are there any special routing instructions for any of the endpoints?
Output Media Format
1.
What type of output is to be produced (i.e., print, microfiche, remote transmission)?
2.
By distribution endpoint, what are the output media requirements?
3.
What remote destination ID’s are used for remote transmission?
4.
What is the relationship of endpoints to the remote destination ID’s (which endpoint(s) goes to each remote ID)?
5.
What report output classes are to be used for printed output?
6.
Are there any other output media types that have not been discussed?
Distribution Hierarchy Definition
The information obtained from the interviews now allows us to determine the data elements necessary to distribute
our reports. Review of this information will provide the answers to these questions:
1.
68
Does our distribution involve multiple output types (i.e., print, microfiche, remote transmission, etc.)?
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Steps in Creating a Distribution Definition
Media Control - Softcopy, Desktop, Hardcopy, etc.
System Reference Guide
Chapter 3: Implementation Strategy
Overview
Steps in Creating a Distribution Definition
Media Control - Softcopy, Desktop, Hardcopy, etc.
2.
Are we distributing to multiple endpoints (i.e., company, bank, plant, division, region)?
3.
Are there additional subordinate levels of distribution breakdown within each endpoint (i.e., department within
company, branch within bank, client within region)?
Answering the above questions will dictate the recipient fields that will make up our distribution key. Each of these
elements represents a level potential distribution breakdown that is used to cluster report pages into related groups
(i.e., all report pages for the same output type, all report pages for a client within an output type, all report pages
for a client within a region within an output type).
Record your findings for future entry on the Distribution Options panel. Once we have determined the recipient fields
and distribution order, we enter this information using the Distribution Options panel of RMS/DD. Distribution
Instruction Sets must have a unique name assigned. This name is from 1 to 16 contiguous alphanumeric characters.
The Distribution Options record is always the first record created in each instruction set.
Step 5 -Producing Report Maps
At this point in our implementation we are ready to begin entering the distribution definition. In order to define
reports, it is necessary to have mapped copies of our reports.
The purpose of the report map is to provide the page coordinates of the information to be used by RM80004 for report
identification and recipient field development. This information is provided to RM80004 via the Custom Report
Definition Panel.
Maps are produced by RM80004 using a RUN*OPTIONS command specifying the MAP operand (see
RUN*OPTIONS command, located in the Appendix section of this manual) and the SELECT command to indicate
the BASE dataset entries to be mapped.
The production of a map requires the use of one of the job control unloaded from the install tape in the first
installation task. The name of this job stream is RMSMAP. Before submitting this job, review the JCL parameters
making any necessary changes required by your installation. You must also change the RM80004 command stream to
include the SELECT commands that refer to base dataset entries produced at your site.
Step 6 -Entering the Distribution Instruction Set
As the result of previously completed tasks, you now have the information necessary to enter the distribution
instruction set. This information includes:
Base Dataset Names
These are the names of the report SYSOUT datasets placed in the repository. These names are assigned based on
methods discussed earlier.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
Define Distribution Requirements
The information gathered from our interview sessions provides an explanation of how the reports are to be
distributed.
We have determined the distribution order and recipient of the key elements necessary to produce our reports in the
appropriate sequence/groups.
Maps of the Reports
The previously created report maps define the page coordinates of the data on each report.
© 2013 Mantissa Corporation. All rights reserved.
69
CHAPTER 3: IMPLEMENTATION STRATEGY
RMS/Online® Version 11.35
RMS/Online® Version 11.35
Chapter 3: Implementation Strategy
System Reference Guide
RM80004 PROCESSING SUMMARY
The distribution component of RMS (RM80004), interprets the distribution instruction information prepared using
RMS/DD.
For example, reports produced by an application system may contain report information for ten divisions within a
single company, each of these with different routing and distribution requirements (i.e., some may be at remote
locations, others are local, other divisions may have different media requirements such as hardcopy and/or
microfiche).
Ideally, this data would be consolidated by division and then each division’s report “packet” made available for any
unique routing and distribution requirements. RMS allows complete distribution customization by endpoint without
application or system software changes.
No matter what the distribution requirements, the following steps take place for reports distributed by RMS.
1.
Your application systems produce reports. These reports are placed directly into the RMS repository if the subsystem interface is used, or moved from the JES spool to the repository if the external writer interface is used.
2.
RM80004 distributes a selected set of reports using the instruction sets produced by RMS/DD. There is no limit
to the number of report datasets that may be distributed in a single invocation of this program.
3.
The RMS Controller INDEX task adds the index information by RM80004 to the appropriate index files set.
4.
The RMS Controller Archive task(s) create retention-based archives for all the reports identified during the distribution as candidates for this type of archive.
RM80004 PROCESSING FLOW
As reports are created by application programs, they are placed in the report repository by the external writer
interface or subsystem interface. Once all reports for a distribution group are available in the repository, RM80004 is
invoked to distribute reports in that distribution group.
The distribution process has two input sources, RMS/DD instruction sets and the repository containing base datasets
to be distributed. Instruction sets are used to define and tailor each execution for a specific group of reports. These
instruction sets produce commands which can be logically grouped into three categories.
COMMAND TYPE
Process Control
Input Process
Output Process
EFFECT ON SYSTEM
Commands in this category are used to define processing options applicable for a given RM80004
execution. These records provide system control values (i.e., command buffer space) and output
limits (i.e., maximum output pages). Also included in this group are commands which define the
distribution hierarchy.
These commands are used to identify the base datasets that are to be processed. Once report
selection has occurred, other commands supply the information necessary to distribute reports (i.e.,
page coordinates of any recipient identifier field, and so on).
Output process commands are used to identify each distribution location and to assign output
attributes (i.e., output class, destination ID, record length, etc.). Another command in this
category is used to insert external data at specific points in the output stream. Through the use of
these commands, page printer and microfiche unit control information may be inserted before or
after any report and/or endpoint
The distribution process performed by RM80004 proceeds in three distinct phases. These phases are Scan, Order and
Output.
70
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
RM80004 Processing Summary
Media Control - Softcopy, Desktop, Hardcopy, etc.
RMS/Online® Version 11.35
Overview
RM80004 Processing Flow
Scan Phase
System Reference Guide
Scan Phase
In the scan phase, all commands are read, edited, and stored in the system command buffer. The selected base datasets
are read, the retrieved report pages are interrogated and distribution keys developed. During this phase, RM80004
operation is based on the following principles:
Principle 1. Page Delineation
A base dataset report is a collection of pages which can be individually identified by a top-of-form print control
character (usually channel 1).
Page 1
Page 2
Top of Form
Top of Form
Principle 2. Determination of Ownership
For each page of a base dataset, RM80004 can determine the ownership by one of the following:
1. The base dataset name.
2. A unique data string on the page, such as a title.
3. The actual ownership information, such as company 001.
4. A combination of the above.
Principle 3. Ownership Information Location
The ownership information for each page within a report is in a consistent location.
Line 1==>
Trial
Line 3==>
Line 1==>
CO 001
Trial
Line 3==>
CO 002
Principle 4. Report Identification
For each different page of a report there exists a data string that will enable RM80004 to determine the ownership.
This data string is called Report Identification Data.
Line 1==>
Trial
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CO 001
Line 1==>
Journal
CO 001
The occurrence of the data
string “TRIAL” on Line 1
indicates the company number
is on Line 3 starting in Column
5.
The occurrence of the data
string “JOURNAL’ on Line 1
indicates the company number
is on Line 3 starting in Column
128.
Principle 5. Page Ownership
For each page of a report, RM80004 can construct a “key” that will contain the ownership or routing information.
© 2013 Mantissa Corporation. All rights reserved.
71
CHAPTER 3: IMPLEMENTATION STRATEGY
Chapter 3: Implementation Strategy
RMS/Online® Version 11.35
Chapter 3: Implementation Strategy
System Reference Guide
Report Page(s)----------------------------------------------- Distribution Key(s)-------------Trial
CO 001
Page 1
BR 88
Trial
CO 001
Page 1
BR 89
00188
00189
Principle 6. Output Sequence Determination
The information in the key determines the sequence of the output. The lowest keys are output first. Pages having like
keys are adjacent to each other in the output stream.
Report Page(s)-------------------------------------Distribution Key(s)------------------Trial
CO 001
Edit
CO 001
Trial
CO 001
BR 88
BR 88
BR 89
00188
00188
00189
Using the preceding concepts, the scan phase of RM80004 develops a distribution key for each report page to be
received by a distribution endpoint. In many cases, multiple distribution keys may be developed for a single page.
This occurs when an endpoint is to receive more than one copy of a report.
EXAMPLE:
Branch 88 receives two copies of its TRIAL report.
Report Page(s)----------------------------- Distribution Key(s)---------------------Trial
Page1
00188 (copy 1)
CO 001
BR 88
00188 (copy 2)
Trial
Page 1
00189 (copy 1)
CO 001
BR 89
Multiple distribution keys for the same report page are also generated for a report page that is to be distributed to
multiple endpoints.
72
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
RM80004 Processing Flow
Scan Phase
RMS/Online® Version 11.35
Overview
Distribution Instruction Sets.
Order Phase
System Reference Guide
EXAMPLE:
Branch 89 receives one copy of Branch 88’s Trial Report.
Report Page(s)----------------------------- Distribution Key(s)----------------------Trial
CO 001
Page 2
BR 88
00188 (Branch 88 copy 1)
00188 (Branch 88 copy 2)
00189 (Branch 89 copy 1)
As the distribution keys are developed, they are placed in very small records to be sorted by the order phase. Along
with the distribution keys, these records contain the location of the report page in the base dataset.
Order Phase
Once the scan phase has been completed, RM80004 dynamically invokes the installation sort program to order the
distribution records. The output of the order phase is a file sequenced by distribution endpoint. It should be noted that
at no time is the actual report data sorted. Only the generated distribution keys are sorted.
Output Phase
In the output phase, the sorted distribution records are read. The report page location stored in the record is used to
retrieve the report page from the managed dataset. The contents of the sort record distribution key are analyzed and
then packaging requirements are determined.
Packaging requirements are determined by comparing the distribution key values with the values specified in the
Custom Packaging and Automatic Packaging records. Each time a match occurs, the corresponding report page is
written to an output report file with the desired attributes (i.e., class, destination ID, etc.). Since the distribution keys
have been sorted by ownership, the result of the output process is that all the report pages for each distribution
endpoint are now together in a single output stream.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
DISTRIBUTION INSTRUCTION SETS.
The RMS Distribution Definition Facility
RMS/DD permits you to enter and maintain detailed instructions relating to your report distribution environment
using a series of formatted panels. You can view these instruction sets as automated replacement for the manual
instructions you may now maintain in a notebook in the distribution area. RM80004 uses the instruction set entered in
the INSTRUCTION*SET*NAME parameter in the RUN*OPTIONS command.
Instruction Set Records - A Functional Description
Distribution set records are used to perform the following:
1.
Establish a distribution hierarchy
2.
Set run-time distribution options
© 2013 Mantissa Corporation. All rights reserved.
73
CHAPTER 3: IMPLEMENTATION STRATEGY
Chapter 3: Implementation Strategy
Chapter 3: Implementation Strategy
3.
Designate which datasets are to be distributed
4.
Define packaging and output characteristics and order
System Reference Guide
Distribution Options
This record contains a definition of the distribution hierarchy, media production priorities, and indicators outlining
the various system run-time options (diagnose, for instance) selected by the distribution administrator. It is the first
record constructed for each distribution set.
Copy Control
Copy Control records contain information relative to the non-default copy variation requirements for the report group
processed by the instruction set.
Send Report
Send Report records permit the shipment of a report to alternate recipients in the distribution network. There is one
record for each unique alternate endpoint/report combination.
Translate
Translate records are used where information appearing on the report does not permit correct collation or routing of
the report.
Package Control
These records control the packaging of output.
Dataset Selection
These records designate which repository datasets contain the reports to be distributed during the distribution system
execution.
Report Definition
Actually, there are two types of report definition records, one for custom definition and another for automatic
definition. These records define the individual reports that will be distributed by RM80004.
Report definition with RMS/DD is accomplished using “Implicit Definition”. The RMS system is the only report
management system, to our knowledge, that uses this technique. Other systems use “Explicit Definition”. The
differences between these two techniques are subtle and somewhat difficult to understand. It is, important, however,
that you comprehend the differences.
Explicit Definition
Let’s start with Explicit Definition. Explicit Definition is nothing more than using a formatted screen to update a
distribution database with unique records containing search argument information for every possible search argument
iteration or combination that might ever be encountered when the distribution system is processing any of your report
data.
For example, suppose you had twenty reports identified as Reports A through T and the reports are to be distributed
to 100 endpoints (bank branches 1 through 100). With Explicit Definition, it would be necessary for you to build
2,000 database records containing the equivalent of ReportA/Branch 1, ReportA/Branch 2 - ReportA/Branch 100.
You would then do the same for Report B through Report T.
If you required additional output media for the Report/Endpoint pair (such as microfiche, in addition to hardcopy), it
would be necessary to repeat this process in its entirety.
74
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Distribution Instruction Sets.
Instruction Set Records - A Functional Description
RMS/Online® Version 11.35
RMS/Online® Version 11.35
Overview
Creating A Distribution Definition
RMS/DD Transactions
System Reference Guide
Explicit Definition has two major drawbacks:
1.
Voluminous data entry.
2.
Equally heavy on-going maintenance.
Implicit Definition
Implicit Definition uses Default/Exception processing as its basis. In the previous example using Implicit Definition,
each report would be described only once (in this case 20 updates to the database) and the 100 recipients (bank
branches 1 through 100) would be described only once (in this case 100 updates to the database). The record pairs
that are normally created by the data entry process using the Explicit technique are now created dynamically using the
Implicit technique. All dynamically created record pairs are assigned a default set of output attributes. Only
exceptions to those defaults would require additional entries into the distribution database.
For instance, if 98 of the 100 branches wanted 2 copies of report A, then the record defining that report would contain
a default copy count for all branches of COPIES=2. The exceptions, in this case, branches 99 and 100, would be
entered into the database as exception records for Report A indicating that in processing Report A, if branch number
equals 99, then send 1 copy of Report A to that branch, and if branch number equals 100, send 3 copies of Report A
for that branch. The distribution database would contain only 122 records in this example of Implicit Definition.
In order to give you some idea of the significance of the difference in data entry requirements of these two
techniques, we have provided the formulas to calculate the number of screens of one of the more popular Explicit
Definition systems along with the formula to calculate screens using Mantissa’s RMS system.
EXPLICIT
IMPLICIT
Reports x 2 x # Recipients = # Screens
Reports + # Recipients = # Screens
Applying these formulas to our example of 20 reports for 100 recipients (bank branches), the results would be:
EXPLICIT
IMPLICIT
20 x 2 x 100 = 4,000 records
20 + 100 = 120 records
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
If you try to use RMS/DD as an Explicit Definition system, you create tremendous overhead both for yourself and
your processing center.
CREATING A DISTRIBUTION DEFINITION
RMS/DD Transactions
Before getting into a detailed description of the individual transactions, it is worth the time to discuss the application
flow for administrative transactions. If you use the menus, gaining access to the RMS/DD facilities requires the
following steps:
Step 1 Sign-on to RMS/Online. The Primary Menu is presented.
Step 2 Select Option 3 on the Primary Menu. The Distribution Definition Primary Menu is displayed.
Step 3 Select the desired transaction. Entering ADO would cause the Add Distribution Option panel
to be presented.
© 2013 Mantissa Corporation. All rights reserved.
75
CHAPTER 3: IMPLEMENTATION STRATEGY
Chapter 3: Implementation Strategy
Chapter 3: Implementation Strategy
System Reference Guide
After the requested operation is performed, the user is prompted for entry of the next field. You may use the End PF
key in order to return to the Administrative Menu or the Return PF key to exit RMS/Online.
Access Authorization
The user’s first interaction with RMS/Online for each session (a session is the time between sign-on and sign-off) is
through the Access Authorization panel. The Access Authorization panel may be by-passed completely by entering the user
ID and password (if any) after the transaction code.
The transaction code necessary to invoke RMS/Online is assigned by your installation. The Access Authorization panel
appears after entering this transaction identifier. Information entered on the panel is used to establish the Access group and
the identity of the user. If security is used, the password field is compared to either the password field in the User Master
record or to the password in the installation security system for access verification.
The NEW and VERIFY passwords may be entered by the user to establish a new password.
Primary Menu
Depending on RMS/Online installation options, the Primary Menu may be presented immediately after sign-on. As the name
suggests, this menu is the initial entry point for all RMS/Online transactions. In the case of Distribution Definition, Option 3 is
selected.
RMS/DD Menu
After selecting Option 3 on the Primary Menu, the Distribution Definition Menu is displayed. Transactions are available for the
records maintained by the RMS/DD component of RMS/Online: Add and List. The first character of various options indicates
the type of transactions: A, L, for Add and List transactions respectively.
Add Transactions
If you select one of the Add transactions, “ADO” (Add Distribution Options) for instance, the Distribution Options Panel is
presented with a message asking for record information. When the data has been entered, pressing Enter will complete the
transaction.
List Transactions
List transactions permit you to select various record types on a generic basis. Once the list is presented, you may then key A,
C, D, and I for Add, Change, Delete and Inquire, respectively, in the ID field on the list panel. The advantage of using the List
transactions is the reduction in the amount of keystrokes necessary to retrieve and update Instruction Set records.
Terminology
Now that you are ready to create your first distribution instruction set. In order to understand the concepts presented
by this material, it is necessary that you understand the following terms:
76
Distribution Key
Up to 30 characters of user defined information that identifies
ownership of a group of report pages. The key information can
be made up of data residing on the report and/or constant data
supplied by the user. The 30 characters can be subdivided into
a maximum of 9 separately accessible recipient field elements.
Distribution key definition is performed using the Distribution
Options panel. RM80004 assigns a distribution key for each
report page distributed.
Logical Report
Each unique page format that can be identified to RM80004. A
sysout dataset can contain 1 or more logical reports.
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Creating A Distribution Definition
Terminology
RMS/Online® Version 11.35
RMS/Online® Version 11.35
Overview
Creating A Distribution Definition
Step by Step
System Reference Guide
Instruction Set
A set of instructions that control one execution of RM80004.
This set of instructions will:
1.
Determine the datasets selected for processing from the
repository.
2.
Define the logical reports within the selected datasets.
3.
Define the output media requirements for the processed
reports.
Recipient Field
One element of a Distribution Key that will determine the output sequence of reports processed by RM80004. These usually
represent the hierarchy of an organization. For instance, if your
organization consists of divisions that are subdivided into
regions, your distribution recipient fields can be DIVISION
and REGION. The recipient fields are described on the Distribution Option panel (ADO from the main menu).
Packet Manifest
A report produced (optionally) at the end of each packet. It
contains information about each report within that packet.
Sometimes called an INDEX Report.
Global Manifest
A packet that contains a copy of all packet manifests for a
given RM80004 execution. It is dynamically created and will
be placed in Class A with a name of MANIFEST.
Base Dataset
Refers to a report entry residing in the managed dataset. Each
of these base datasets consists of the report data for each sysout
produced by the program.
Report Page
A group of report lines that is preceded by a top-of-form
printer carriage control character (usually channel 1).
Report Page Format Data
Any contiguous string of characters, including blanks, appearing on the report page that allows distinction of one report from
another, i.e., report titles.
System Command Buffer
Storage area used to store RM80004 commands. The command
buffer size can be varied by RM80004 execution.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
Step by Step
We are now ready to begin the actual data entry for the selected report group. If you are familiar with RMS/Online,
you may bypass the following pages relating to system sign-on and menu selection.
© 2013 Mantissa Corporation. All rights reserved.
77
CHAPTER 3: IMPLEMENTATION STRATEGY
Chapter 3: Implementation Strategy
RMS/Online® Version 11.35
Chapter 3: Implementation Strategy
System Reference Guide
Access Authorization Panel
R.M.S. - Access Authorization
Mantissa (C)opyright MCMXCII
Required:
User ID
Password
==>
==>
Optional:
New Password
Verify Password
==>
==>
Program Function
Use
Caution
When
Changing
PF1=Help
(( New and Verify Passwords ))
((
** Must Match **
))
Keys:
PF01 ==>
PF04 ==>
PF07 ==>
PF10 ==>
PF3=End
Date: Monday,
10/07/96 Time: 12:49:16
SubSys: R135 Tran:
TermID: 002B ___
PF02
PF05
PF08
PF11
==>
==>
==>
==>
PF03
PF06
PF09
PF12
==>
==>
==>
==>
PF4=Return
Figure 1. Access Authorization Panel
The user’s first interaction with RMS/Online for each session is through the Access Authorization panel. The Access
Authorization panel may be by-passed completely by entering the user ID and password (if any) after the transaction
code.
The transaction code necessary to invoke RMS/Online is assigned by your installation. The Access Authorization
panel appears after entering the transaction identifier. Information entered on the panel is used to establish the Access
group and the identity of the user. If security is used, the Password field is compared to either the Password field in
the User Master record or to the password in the installation security system for access verification.
The NEW and VERIFY passwords may be entered by the user to establish a new password.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Creating A Distribution Definition
Step by Step
78
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Overview
Creating A Distribution Definition
Step by Step
System Reference Guide
Primary Menu Panel
R.M.S. - Primary Menu
Access Group - IVSYSTEM
Date: Monday,
10/07/96 Time: 12:51:12
SubSys: R135 Tran:
TermID: 002B ___
Option ==> 3
1.
2.
3.
4.
5.
6.
T.
Display/Print
Administration
Distribution(Implicit)
Sysout/Report
Security
Help Management
Tutorial
PF1=Help
PF3=End
-
Display/Print a Report in the RMS Database
Administration and Resource Control
Distribution Definition and Management
Sysout/Report Profile Management
Security Definition and Management
Help Management and Maintenance
Tutorial on System Capabilities/Facilities
PF4=Return
Figure 2. RMS/Online Primary Menu Panel
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
The PRIMARY MENU is presented immediately after the Access Authorization panel. All major system functions
are accessible from this panel. The available options are:
1. Display/Print
Display/Print a Report in the RMS Database
2. Administration
Administration and Resource Control
3. Distribution
Distribution Definition and Management
4. Sysout/Report
Sysout/Report Profile Management
5. Security
Security Definition and Management
6. Help Management
Help Management and Maintenance
T. Tutorial
Tutorial
Enter 3 in the option field and press Enter to select the Distribution Definition menu.
© 2013 Mantissa Corporation. All rights reserved.
79
CHAPTER 3: IMPLEMENTATION STRATEGY
Chapter 3: Implementation Strategy
RMS/Online® Version 11.35
Chapter 3: Implementation Strategy
System Reference Guide
RMS/Distribution Definition Primary Menu Panel
R.M.S. - Distribution Definition
Date: Monday,
10/07/96 Time: 12:53:38
SubSys: R135 Tran:
TermID: 002B ___
Option ==> ADO
Name ==> RDMSCASE
(Instruction Set)
Distribution:
Master/Options
Recipient/Location Equate
Define:
Custom Definition
Automatic Definition
Copy Control
Send Report
Content/Recipient Conversion
Recipient/Recipient Conversion
DATASETS:
To Be Distributed
PACKAGING/OUTPUT:
Custom Packaging
Automatic Packaging
Data Insertion
Output Priority
PF1=Help
PF3=End
__ Options __
Add
List
------------ADO
LDO
ARL
LRL
------------ACD
LCD
AAD
LAD
ACC
LCC
ASR
LSR
ACR
LCR
ARR
LRR
------------ADS
LDS
------------ACP
LCP
AAP
LAP
ADI
LDI
AOP
LOP
PF4=Return
Figure 3. RMS/DD Primary Menu Panel
The Primary Distribution Definition panel is used to gain access to basic distribution functions. You must enter the
Distribution Set name and select an option to proceed. The Distribution Instruction Set name may be 1 to 16
characters long and must be unique. This name is used by RM80004 to retrieve the instruction set. If you are creating
a new instruction set, your first transaction must be ADO (Add Distribution Options).
If you are updating an existing set, use the LDO option to list the instruction sets available.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Creating A Distribution Definition
Step by Step
80
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Overview
Creating A Distribution Definition
Step by Step
System Reference Guide
Distribution Options Panel
RMS/DD - Distribution Master
Mode: ADD
Date: Monday,
Disn: RDMSCASE
10/07/96 Time: 12:54:55
*** Media Production Priorities
Hardcopy- 1 Tape- 2 Microfich- 3 DASD- 4 Remote- 5 Network- 6 Softcopy- 7
OUT
ORD
Symbolic ----------- / FLD
Recipient Field Name / LEN
/
/
/
/
/
/
/
/
/
Notes----------------------------------------
Notes ==>
==>
PF1=Help
PF3=End
PF4=Ret
PF7=Bwd
PF8=Fwd
ENTER=Update/Inq
Panel 1 of 2
Figure 4. Distribution Options Panel (1 of 2)
The Distribution Option record is constructed using information gathered in steps discussed earlier. It permits the
definition of the media production priority, consolidation hierarchy (recipient field identification), and other run-time
options. (See panel 2 of 2.)
Media Production Priorities
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
The values assigned here will govern the output priorities for the various medias. Each media must have a unique
priority. The defaults are:
Media
Priority
HARDCOPY
1
TAPE
2
MICROFICHE
3
DASD
4
REMOTE
5
NETWORK
6 (RESERVED for RMS/Desktop)
SOFTCOPY
7
ORD(er)
This field governs the order in which report pages will be ordered within media category.
© 2013 Mantissa Corporation. All rights reserved.
81
CHAPTER 3: IMPLEMENTATION STRATEGY
Chapter 3: Implementation Strategy
RMS/Online® Version 11.35
Chapter 3: Implementation Strategy
System Reference Guide
Recipient Field - Name/Length/Notes
These fields permit the specification of up to 9 recipient fields which can be used to produce the desired order and
packaging of reports. This will define the key structure.
The fields are usually common information appearing on reports to be distributed. For manufacturing, you might
have a plant number on reports that would be the source of information to be used in consolidation/distribution. Keep
in mind that the fields do not have to be the names of common fields on your reports. Constant information can be
used and mixed with report fields to attain the desired results.
NOTE: Once a distribution options record is added all fields except the OUT ORD and FLD LEN may
be maintained. In order to change these fields or delete/add symbolic recipient field names, you
must reorganize the distribution instruction set. Refer to the section on Instruction Set
Reorganization and Copy for details.
Distribution Options Panel (continued)
RMS/DD - Distribution Options
Mode: ADD
Date: Monday,
10/07/96 Time: 12:57:20
----------------------------------------
------------------------------- General Options ------------------------------Packet Archive (N/Y) ==> N
Command Buffer Space(K) ==> 00080
Sep. Page Msg Lines ==> 10
Audit Report Line Count ==> 56
Packet Page Limit
==> 99999999 Default Media Type
==> HARDCOPY
Manifest Format(S/L) ==> L
Diagnostic Record Dump ==> N
Diagnose? (N/Y)
==> N
------------------------------- R.M.S. Options -------------------------------Softcopy (N/Y) ==> N Media Tracking (N/Y) ==> N Access Group ==>
---------------------------- Process Code Options ----------------------------Input Process Code ==>
Output Process Code ==>
Process Code Cond.
==>
------------------------------ Mapping Options -------------------------------Produce A Map? ==> N
Maximum Map Lines ==> 20
Map Page Limit ==> 99999999
Map Line Column
==> 002
PF1=Help
PF3=End
PF4=Ret
PF7=Bwd
PF8=Fwd
ENTER=Update/Inq
Panel 2 of 2
Figure 5. Distribution Options Panel (2 of 2)
General Options
PACKET ARCHIVE (N/Y)
82
DEFAULT: N
Specification of ‘Y’ will cause RM80004 to produce a packet
archive of all reports distributed. ‘Y’ is suggested since the
packet level archive permits recovery of specific reports for a
given user. YES is forced if SOFTCOPY = Y is selected. The
value must by “Y” for retention-based archive to work.
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Creating A Distribution Definition
Step by Step
System Reference Guide
Chapter 3: Implementation Strategy
Overview
Creating A Distribution Definition
Step by Step
COMMAND BUFFER SPACE (K)
DEFAULT: 80
The command buffer space specification is used to cause
RM80004 to acquire appropriate buffer space for processing of
the instruction set.
SEP PAGE MSG LINES
DEFAULT: 10
Used to control the number of message lines printed on the
start and end separator pages for each packet. The value may
range from 00 to 25.
AUDIT REPORT LINE COUNT
DEFAULT:50
Used to set the maximum line count for the RM80004
(QXSTATS DD) system report. Acceptable line count values
are 20 through 66.
PACKET PAGE LIMIT
DEFAULT: 99999999
Used to limit the total output for each copy of each report in a
packet to the value specified for page output limit. The minimum is 1. The maximum and the default is 99999999 pages.
DEFAULT MEDIA TYPE
*** Not Currently Used ** Reserved. Used to establish a
default media for comparison field in the distribution definition
panels.
MANIFEST FORMAT S/L
DEFAULT: (L)ong
Indicates that the long form of the packet manifest (INDEX)
will be created. The short manifest does not include information about the JES job that created the report.
DIAGNOSTIC RECORD DUMP
DEFAULT: N
Used to cause RM80004 to produce a listing of all distribution
keys generated from the run. These will be printed on the
Dataset Selection report from DD statement QXSTATS.
DIAGNOSE (N/Y)
DEFAULT: N
Used to cause RM80004 to produce command-format edit
information only. No reports will be processed when this
option is set to “Y”.
RMS/Online Options
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
SOFTCOPY (N/Y)
DEFAULT: N
Used to indicate that RM80004 is to place reports in the repository for viewing. Use of this parameter forces the ARCHIVE
option to be activated.
Your RM80004 JCL must include the DD statements for
QXARCHO, if this option is used.
MEDIA TRACKING (N/Y)
© 2013 Mantissa Corporation. All rights reserved.
DEFAULT: N
Used to request that report tracking information be added to
QXRCDS.
83
CHAPTER 3: IMPLEMENTATION STRATEGY
RMS/Online® Version 11.35
RMS/Online® Version 11.35
Chapter 3: Implementation Strategy
System Reference Guide
ACCESS GROUP
DEFAULT: None
This is a required parameter used to specify the access group
qualifier for viewable (SOFTCOPY) and tracked reports (See
MEDIA*TRACKING). The Access Group MUST be defined
before an instruction set can be created referencing this value.
Process Code Options
INPUT PROCESS CODE
DEFAULT: None
This is an optional parameter used when re-processing data
that has been processed and stamped with a process code using
the Output Process Code option.
PROCESS CODE CONDITION
DEFAULT: None
This field is used to specify a condition for a match when using
the Input Process Code field. Choices are:
EQ
GE
GT
LE
LT
NE
OUTPUT PROCESS CODE
- Equal
- Greater Than or Equal
- Greater Than
- Less Than or Equal
- Less Than
- Not Equal
DEFAULT: None | ccc....ccc | GENERATE
Used to provide a value that is to indicate the selected base
datasets have been processed. Upon successful job completion,
each selected dataset is updated with the specified value. Of
the two possible values, character string is a user supplied
value from 1 to 11 characters in length. A value of GENERATE indicates that RM80004 is to automatically assign a
value. The value will be the date and time the first dataset was
processed by RM80004. This assigned value will be in the
form of:
Y YD DD H HM M SS
NOTE: Once an entry has been assigned a process code, it can only be reprocessed by its specific
process code value via the Input Process Code or the Process Code Fields on either the
Distribution Options Panel or Dataset Select panel.
Mapping Options
84
PRODUCE A MAP?
DEFAULT: N
“Y” causes all datasets processed to be mapped. Mapping
reproduces the first n lines (see MAXIMUM MAP LINES) of
each page with the line number printed in the position you designate (see MAP LINE COLUMN) and a column scale across
the top of the page.
MAXIMUM MAP LINES
DEFAULT: 20
Used to set the number of lines on each physical report page
that will be mapped. Many applications require that only the
first 5 lines be mapped.
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Creating A Distribution Definition
Step by Step
RMS/Online® Version 11.35
Overview
Creating A Distribution Definition
Step by Step
System Reference Guide
MAP PAGE LIMIT
DEFAULT: 9999999
Used to limit the number of pages mapped for each base
dataset.
MAP LINE COLUMN
DEFAULT: 2
Used to indicate the starting column number to print the line
number in for mapped output. The maximum value that may be
specified is 204.
Custom Report Definition Panel
RMS/DD - Custom Report Definition
Mode: ADD
Date: Monday,
Disn: RDMSCASE
10/07/96 Time: 12:59:48
Report ID ==>
Indx Title ==>
Def Copies ==> 01
DS Name
==>
DS Prefix
Append N/Y
Def Media
==>
==> N
==> HARDCOPY
Priority
==> 5000
---------------------ID Data 1 =>
ID Data 2 =>
Report Recognition Information ----------------------Line =>
COL =>
Line =>
COL =>
--------- Recipient Field Line/Column Coordinate or Constant Value ----------Recipient Field Name / Line / C/O / C/S / Constant(10) or Search(30) Value
REGION
(01) /
/
/
/
COMPANY
(02) /
/
/
/
CLIENT
(03) /
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
PF1=Help PF3=End PF4=Ret ENTER=Update/Inq
RM9134I Enter information for new record.
Figure 6. Custom Report Definition Panel
Each report to be processed by RM80004 must have its unique recognition characteristics defined. This is done by
using the custom report definition panel. Each custom definition takes the following into consideration:
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
Recognizable Characteristics:
1.
A unique 8 character REPORT ID must be assigned to this logical report. This name will appear with the INDX
TITLE on the packet manifest report.
2.
You must define to RM80004 the base dataset entry that contains the logical report identified in this panel. This
is done by specifying the full name in the DS NAME field or the prefix qualified name in the DS PREFIX field.
3.
Use the ID DATA 1 and ID DATA 2 fields (if necessary) provided the page coordinates of the report fields can
be used to uniquely distinguish this logical report from other reports that may appear in the same queue dataset.
This is typically a report title or report number on the page.
4.
The Recipient Field Line/Column information is used to define the line column coordinate or alternatively constant data that will be transferred to the recipient fields of the distribution key.
© 2013 Mantissa Corporation. All rights reserved.
85
CHAPTER 3: IMPLEMENTATION STRATEGY
Chapter 3: Implementation Strategy
RMS/Online® Version 11.35
Chapter 3: Implementation Strategy
5.
System Reference Guide
•
If recipient data is to be taken from the actual report page (plant number, perhaps), you define the line/
column coordinates of the report field used as the source of the recipient field data. These coordinates are
obtained from the report map. In some cases, the report data is not suitable for the formation of a consistent
recipient field that would yield the desired ordering. A Content/ Recipient conversion facility is provided to
overcome this problem.
•
Recipient fields may also have a source other than the report page. You may omit the Line/Column values,
place a ‘C’ in the C/S field and up to 10 characters in the Constant (10).... field.
Determine the standard number of copies of the report each primary endpoint is to receive. This value is entered
in the Copies field.
Having completed the Custom Report Definition panel, you have entered the information necessary to construct the
primary ownership identification for each page of the logical report. Next, you may address the customization of
distribution for this report for each endpoint. Using the requirements gathered during the interview sessions, you can
determine:
If there are special situations requiring alteration of our generated distribution keys.
•
If any of our endpoints require copy counts differing from the established default copy count, use the Copy Control panel to designate these variations.
•
Whether the report is to be distributed to additional endpoints not defined by the
primary distribution key. In this case, use the Send Report panel to route the report to alternate distribution endpoints.
Steps 1 through 5 are repeated for each logical report to be distributed.
86
REPORT ID
DEFAULT: None
Assigns an internal use mnemonic to the logical report defined
by this panel. Report identifier may be an alphanumeric value,
from 1 to 8 characters in length. No special characters are permitted. This name may be used for recovering individual
reports from archived segments to RMS/ARC. The REPORT
ID is used in conjunction with the INDX TITLE operand to
provide logical report descriptions on the manifest reports and
ONLINE Index and Versions panels.
DS NAME
DEFAULT: None
This value is the name of the dataset containing the report
defined by this panel. DS NAME or DS PREFIX (but not both)
must be specified.
DS PREFIX
DEFAULT: None
This value is the prefix of the datasets containing the report
defined by this panel. This is a convenient way to search multiple datasets for a common report.
INDX TITLE
DEFAULT: None
This value provides the descriptive title to be used in the packet
and global index report. Specifying * or ID1 causes the system
to use the character string coded in ID Data 1 as the title. Specifying ID 2 causes the system to use the character string coded
in ID Data 2.
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Creating A Distribution Definition
Step by Step
RMS/Online® Version 11.35
Overview
Creating A Distribution Definition
Step by Step
System Reference Guide
APND N/Y
DEFAULT: N
Specifying Y causes all pages matching the custom report definition to be assigned the same distribution characteristics as the
previous page. One use for this option would be to define a
totals page and send a copy of the totals page to another endpoint, but append the original page to the body of the report.
DEF COPIES
DEFAULT: 01
Designates the default number of copies to be produced for the
report. From 0 - 99 may be specified.
PRIORITY
DEFAULT: 5000
Used to assign the priority of a report within an output segment. The lower the priority assigned, the closer to the front of
a packet the report will print. Report priority must be a numeric
value from 0 to 9999.
DEF MEDIA
DEFAULT: HARDCOPY
Default media is used for the logical media category. RM80004
supports 7 logical media groupings for the segregation of
reports/endpoints during output.
Valid media specification(s) are:
HARDCOPY
TAPE
MICROFICHE
DASD
REMOTE
NETWORK
SOFTCOPY
All categories except SOFTCOPY indicate output is to be in
the form of print line images with IBM machine control characters. The output is directed to the dynamically allocated or
in-stream DD statement designated with a custom packaging or
automatic packaging transaction.
Report Recognition Information
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
Report recognition information is used to designate the unique recognition characteristics of a report. The first level
of qualification is the dataset name or name prefix. ID DATA 1 and ID DATA 2 add additional levels of qualification.
ID DATA 1...ID DATA 2
This is a string of characters that uniquely identifies a particular logical report. This data is usually, but not always, report
title information. The maximum character string length is 30.
When spaces are included at the end of the character string or
the entire character string is spaces, then the string must be
enclosed in parenthesis.
LINE
This is the line number on which the character string appears.
Line 1 through 88 may be designated.
© 2013 Mantissa Corporation. All rights reserved.
87
CHAPTER 3: IMPLEMENTATION STRATEGY
Chapter 3: Implementation Strategy
Chapter 3: Implementation Strategy
COLUMN
System Reference Guide
This is the column number of the first position of the character
string. If column is omitted, the system performs a search on
the designated line for the character string. Valid column numbers are 2 - 204.
Recipient Field Line Column/Coordinate
In this section of the custom report definition panel, you supply the location or value of the various recipient fields
comprising the distribution order information.
RECIPIENT FIELD NAME
Supplied by system from data entered in the distribution
options panel.
LINE
Is the line number on which the recipient identification data
appears.
C/O
Either the column coordinate at which the recipient data
resides or the Offset from the beginning of the search value at
which the recipient value begins.
C/S
Enter C(ONSTANT) in this field and omit the line/column values if you want the recipient field value to be the constant
entered in the ‘Constant or Search’.
Enter S(EARCH) in this field if you want the system to search
the specified line for the value entered in the ‘Constant or
Search’ field.
CONSTANT (10) or SEARCH (30) VALUE
Use this field if you place C (for constant) or S (for search) in
the C/S field. Search character strings may be up to 30 characters. If you have a search string with spaces, enclose the entire
value in quotes.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Creating A Distribution Definition
Step by Step
RMS/Online® Version 11.35
88
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Overview
Creating A Distribution Definition
Step by Step
System Reference Guide
Copy Control Panel
RMS/DD - Copy Control
Mode: ADD
Report ID ==>
Copies
==> 01
Start Date ==>
Date: Monday,
Disn: RDMSCASE
End Date
==>
Duration
10/07/96 Time: 13:01:25
==>
Recipient Field Name / If the Recipeint Fields Contain
MEDIA*CATEGORY
/
LOCATION*ID
/
REGION
COMPANY
CLIENT
(01) /
(02) /
(03) /
/
/
/
/
/
/
PF1=Help PF3=End PF4=Ret ENTER=Update/Inq
RM9134I Enter information for new record.
Figure 7. Copy Control Panel
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
The Copy Control panel is used to specify the report copy requirements that vary from those prescribed in the custom
report definition panel. Report ID is the same value assigned in the Custom Report Definition transaction. The report
may be eliminated for a particular endpoint by specifying 00 in the copies field. Use the START DATE/END DATE/
DURATION fields only for override records. Base (standard) records should have these fields omitted. Media
category refers to the DEF(AULT) Media assigned in the Custom Report Definition transaction. Specify a Location
Value only if you have used the Recipient to Location Equate transaction (see Advanced Function) to define such a
location.
REPORT ID
DEFAULT: None
This field identifies the report to have the number of copies
varied.
COPIES
DEFAULT: 01
Used to specify the number of copies produced for a viewpoint. Valid copy values are 00-99.
START DATE
DEFAULT: None
Use the Start Date (YYMMDD) field to indicate the beginning
date that this Copy Control record should become effective.
Copy control records that specify the standard number of copies should not have a start date.
END DATE
DEFAULT: None
Use End Date (YYMMDD) to invalidate this copy control
record after a specific date.
© 2013 Mantissa Corporation. All rights reserved.
89
CHAPTER 3: IMPLEMENTATION STRATEGY
Chapter 3: Implementation Strategy
RMS/Online® Version 11.35
Chapter 3: Implementation Strategy
System Reference Guide
DURATION
DEFAULT: None
You may specify the duration in days of the Copy Control
record instead of the End Date. If both End Date and Duration
are specified, End Date takes precedence.
RECIPIENT FIELD NAME
DEFAULT: None
These are initialized by the system and contain the recipient
field names entered in the Distribution Options panel.
IF RECIPIENT FIELDS CONTAIN...
DEFAULT: None
Enter values here which uniquely identify the recipient to
which this Copy Control record applies.
Send Report Panel
RMS/DD - Send Report
Mode: ADD
Report ID ==>
Copies
==>
Start Date ==>
Date: Monday,
Disn: RDMSCASE
End Date
==>
Duration
10/07/96 Time: 13:02:45
==>
REC FLD Name / If Recipient Fields Contain... / Send Report to this Recipient..
MEDIA*CATEGO /
/
LOCATION*ID /
/
REGION
COMPANY
CLIENT
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
PF1=Help PF3=End PF4=Ret ENTER=Update/Inq
RM9134I Enter information for new record.
Figure 8. Send Report Panel
The Send Report panel is used to specify those recipients to receive copies of another distribution recipients report.
Up to 99 copies of a report can be sent to the alternate endpoint.
NOTE: Do not use the Send Report to send a report to the same recipient. Use the Copy Control panel
to accomplish this.
A report which has had its copy count reduced to zero by default (custom definition/or override
(Copy Control)) may still be sent to any number of additional endpoints.
REPORT ID
90
DEFAULT: None
This field identifies the report to be sent to an additional recipient. It should match the Report ID entered on the Custom
Report Definition panel.
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Creating A Distribution Definition
Step by Step
RMS/Online® Version 11.35
Overview
Creating A Distribution Definition
Step by Step
System Reference Guide
COPIES
DEFAULT: 01
Used to specify the number of copies sent to the additional
recipient.
START DATE
DEFAULT: None
Use the Start Date (YYMMDD) field to indicate the beginning
date that this Send Report record should become effective.
END DATE
DEFAULT: NoneUse End Date (YYMMDD) to deactivate this
Send Report record after a specific date.
DURATION
DEFAULT: None
You may specify the duration of this Send Report record
instead of the End Date. If both End Date and Duration are
specified, End Date takes precedent.
IF RECIPIENT FIELD CONTAINS....
DEFAULT: None
Enter values here which uniquely identify the recipient from
which the report is sent.
SEND REPORT TO THIS RECIPIENT....
DEFAULT: None
Enter values here which uniquely identify the endpoint to
receive the report. Any recipient field not designated in these
fields will be given values equal to the recipient from which
the report was sent.
Dataset Selection Panel
RMS/DD - Dataset Selection
Mode: ADD
Date: Monday,
Disn: RDMSCASE
10/07/96 Time: 13:04:03
Dataset Name ==>
DS Prefix
==>
Select Pri.
==> 5000
----------------------- Additional Selection Criteria ----------------------Output Class ==>
Destination ==>
Form Ident.
==>
OS Job Name
==>
OS Job Num
==>
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
--------------------------- Process Code/Condition -------------------------Process Code ==>
Condition
==>
(EQ,NE,GT,LT,GE,LE)
---------------------------- FCB Requirements ----------------------------For Channel ==> CH01 CH02 CH03 CH04 CH05 CH06 CH07 CH08 CH09 CH10 CH11 CH12
Line Number ==> 001
Top Form CH ==> 01
PF1=Help PF3=End PF4=Ret ENTER=Update/Inq
RM9134I Enter information for new record.
Figure 9. Dataset Selection Panel
© 2013 Mantissa Corporation. All rights reserved.
91
CHAPTER 3: IMPLEMENTATION STRATEGY
Chapter 3: Implementation Strategy
Chapter 3: Implementation Strategy
System Reference Guide
Base datasets are selected for processing using the qualifying information specified on this panel. Two types of
selection are permitted: specific name or generic prefix. Both types permit positions in the name to be ignored by
placing an asterisk (*) in those positions of the name or name prefix.
Any number of base datasets may be selected for processing in a single RM80004 job. Selection and full name may
be intermixed to attain the desired results. Generic selection of datasets causes processing in alphabetical sequence.
OUTPUT CLASS
DEFAULT: None
Used to limit selection to those entries with a matching class.
Valid classes are A-Z, 1-9.
DESTINATION
DEFAULT: None
Used to limit selection to those entries with a matching destination identifier. NJE users should use the short format specification for NODE:REMOTE destinations (NnnnRnnn).
FORM IDENT
DEFAULT: None
Used to limit selection to those entries with a matching forms
identifier.
OS JOB NAME
DEFAULT: None
Used to limit selection to those entries created in the JOB
matching the supplied name.
OS JOB NUMBER
DEFAULT: None
Used to limit selection to those entries created in the OS/VS
job matching the designated job number.
DS NAME
DEFAULT: None
Used to specify the full dataset name of from 1 to 8 characters.
If there is more than one base dataset with the specified name,
the entry most recently created is selected for processing.
DS PREFIX
DEFAULT: None
A parameter used to select by name prefix. Selection by prefix
always implies selection of every base dataset having this prefix.
SELECT PRI
DEFAULT: 5000
Used to specify the selection processing sequence. Note: When
utilizing checkpoint processing, the Select PRI would be “1”.
The lowest number will be the highest priority; “1” equals first.
Process Code/Condition
Process codes are used to restrict RMS selection of datasets. A character string specified as the comparison value may
be from 1 to 11 characters. This value is compared to the process code value contained in each base dataset matching
all other selection characteristics. A match condition is determined using the operation code operand. The possible
operation codes are:
EQ - equal to (default)
GE - greater than or equal to
GT - greater than
LE - less than or equal to
LT - less than
NE - not equal
92
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Creating A Distribution Definition
Step by Step
RMS/Online® Version 11.35
Chapter 3: Implementation Strategy
Overview
Creating A Distribution Definition
Step by Step
System Reference Guide
The use of the masked comparison character “*” in any comparison value position causes that position to be ignored
in the comparison operation. This would allow the selection of groups of process codes, i.e.,
PROCESS CODE==> A**********
CONDITION==> NE
Would cause the selection of all processed base datasets not having an “A” in the first position of the process code.
PROCESS CODE
DEFAULT: None
Any character string from 1 to 11 contiguous bytes can be used
to limit dataset selection.
CONDITION
DEFAULT: EQ
Specifies the condition code for the selection process.
NOTE: Once a dataset has been assigned a process code it can only be selected for further processing
using the PROCESS CODE ==> field on the dataset selection panel or the INPUT PROCESS
CODE ==> field of the distribution options panel.
The OUTPUT PROCESS CODE ==> field on the distribution option panel is used to assign
process codes to base datasets.
Process code specifications on the dataset selection panel override the INPUT PROCESS
CODE specification of the distribution option panel.
FCB Requirements Summary
This section of the panel is used to describe the channel control characteristics of a group of queue datasets to
RM80004. Channel control descriptions are necessary for RM80004 to map and/or extract key data from report pages
if multiple form types are processed.
DEFAULT: None
CH01 - CH12 establishes a channel/line number relationship.
LINE NUMBER
DEFAULT: 01 (For Channel 1)
The line number of the individual channels.
TOP FORM CH
DEFAULT: 01
The top of form channel is used to specify the channel number
that represents the top of form for this dataset.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHANNEL
© 2013 Mantissa Corporation. All rights reserved.
93
CHAPTER 3: IMPLEMENTATION STRATEGY
RMS/Online® Version 11.35
RMS/Online® Version 11.35
Chapter 3: Implementation Strategy
System Reference Guide
Custom Packaging Panel
RMS/DD - Custom Packaging
Mode: ADD
Packet Name
Sep Pages
Outplex Num
Message Txt
==>
==> 2
==> 1
==>
Recipient Field Name
MEDIA*CATEGORY
LOCATION*ID
or
REGION
(01)
COMPANY
(02)
CLIENT
(03)
PF1=Help
RM9134I
Date: Monday,
Disn: RDMSCASE
Indx Copies ==> 1
Location Nm ==>
02/05/01 Time: 10:45:20
Indx Packet?
==> N
Accounting
/ When Recipient Fields Contain. Break
/
/
(Either Location or Recipient)
/
/
/
/
/
/
/
/
/
PF3=End PF4=Ret PF7=Bwd PF8=Fwd
Enter information for new record.
ENTER=Update/Inq
Panel 1 of 8
Figure 10. Custom Packaging Panel
The Custom Packaging panel provides a way to partition the RM80004 output into packets with varying separator
page block letters, message data and output attributes. During the Output phase of RM80004 processing, data entered
via the Custom Packaging panel is compared to the content of the distribution key data associated with each report
page. When all the conditions specified have been met, the current output file is closed and a new packet is created.
94
PACKET NAME
DEFAULT: None
This field is required and is used to assign the name of the
packet. This name is 1 to 8 characters long and must conform
to OS/MVS DD naming conventions.
SEP PAGES
DEFAULT: 2
This field is used to override the default number of RM80004
separator pages. From 0 to 9 pages may be generated for each
packet. This value may be overridden if separator are specified
on the corresponding output characteristics panel (panels 2-8)
for the media specified.
INDX COPIES
DEFAULT: 1
Use this field to designate the number of copies of either the
global index (if INDX PACKET = Y) or the packet index (the
default). From 0-9 may be specified.
INDX PACKET (N/Y)
DEFAULT: N
May be used to indicate that this Custom Packaging panel
describes the global index packet. This packet will contain a
copy of each packet manifest produced within this run of
RM80004.
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Creating A Distribution Definition
Step by Step
System Reference Guide
Chapter 3: Implementation Strategy
Overview
Creating A Distribution Definition
Step by Step
OUTPLEX NUM
DEFAULT: 1
Specification of ‘N’ indicates that this Custom Packaging
panel describes a packet that is to have the reports aligned on
even page boundaries in the packet. This will cause all reports
to be produced with an even number of pages. Specification of
2,4,6,8 is also supported.
LOCATION NM
DEFAULT: PACKET NAME
This field designates the name of the location receiving the
report packet. A location name must be an alphanumeric character string of from 1 to 16 positions. Spaces are not permitted
in the location name.
MESSAGE TXT
DEFAULT: None
Used to designate up to 30 characters of text data to be printed
on packet separator pages.
RECIPIENT FIELD/SET PRIORITY WHEN RECIPIENT FIELDS CONTAIN
These fields specify the conditions under which the packet
defined by this panel is to be created. Media category refers to
the DEF(AULT) media assigned in the Custom Report Definition panel. If multiple media have been generated, then one
Custom Packaging panel may be used to describe all media. In
this case the MEDIA*CATEGORY field may contain an * followed by the first letters of all the media. For example, if hardcopy, softcopy and microfiche media were used, then the
MEDIA*CATEGORY field could be coded “*HSM” and the
appropriate panels 2-8 used to describe the output characteristics. Specify a Location value only if you have used the Recipient to Location Equate or Send Report transaction to equate
the referenced location.
DEFAULT: Packet level accounting
The Accounting Break field is used to specify sub-accounting
breaks for the packet INDEX report. Enter Y on the same line
as the recipient field(s) for which you desire sub-accounting.
Each time any of the indicated recipient fields change total
lines and pages are printed for that report on the packet index.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
ACCOUNTING BREAK
© 2013 Mantissa Corporation. All rights reserved.
95
CHAPTER 3: IMPLEMENTATION STRATEGY
RMS/Online® Version 11.35
RMS/Online® Version 11.35
Chapter 3: Implementation Strategy
System Reference Guide
Output Priority Panel
RMS/DD - Output Priority
Mode: ADD
Priority
==> 5000
Start Date ==>
Date: Monday,
Disn: RDMSCASE
End Date
==>
Duration
10/07/96 Time: 13:07:15
==>
Recipient Field Name / Set Priority When Recipient Fields Contain
MEDIA*CATEGORY
/
LOCATION*ID
/
REGION
COMPANY
CLIENT
PF1=Help
(01) /
(02) /
(03) /
/
/
/
/
/
/
PF3=End
PF4=Ret
ENTER=Update/Inq
Figure 11. Output Priority Panel
The Output Priority panel is used to control the output production priority for report pages having specific recipient
field values.
96
PRIORITY
DEFAULT: 5000
This field establishes the output priority of the distribution
keys matching the recipient field values entered. Keep in mind
that output priority supersedes all other location/recipient qualifiers in determining the output order to the distributed report
stream.
START DATE
DEFAULT: None
Use the start date field (YYMMDD) to indicate the beginning
date that this record should become effective. Records that
specify the standard priorities should not have a start date.
END DATE
DEFAULT: None
Use end date (YYMMDD) to invalidate this record after a specific date.
DURATION
DEFAULT: None
You may specify the duration instead of the end date. If both
end date and duration are specified, end date takes precedence.
RECIPIENT FIELD NAME
These are initialized by the system and contain the
recipient field names entered in the Distribution Options panel.
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Creating A Distribution Definition
Step by Step
RMS/Online® Version 11.35
Overview
Creating A Distribution Definition
Step by Step
System Reference Guide
IF RECIPIENT FIELDS CONTAIN...
Enter values here which uniquely identify the recipient to
which this priority record applies.
Recipient/Location Equate Panel
RMS/DD - Recipient/Location Equate
Mode: ADD
Date: Monday,
Disn: RDMSCASE
10/07/96 Time: 13:09:19
Location ID ==>
* Comparison Recipient Field Values For This Location *
Recipient Field Name / Contents of Recipient Fields REGION
(01) /
COMPANY
(02) /
CLIENT
(03) /
/
/
/
/
/
/
PF1=Help PF3=End PF4=Ret ENTER=Update/Inq
RM9134I Enter information for new record.
Figure 13. Recipient/Location Equate
The Recipient/Location Equate panel provides a way to assign a short form reference (the location name) for the
various recipient field combinations that will be used within the definition. Use of the Recipient/Location Equate can
also add to the clarity of the definition since you only have to enter the unique combination of key elements once. All
other references are made using the Location ID.
LOCATION ID
Enter the identifier to be assigned to the location. It must be 1
to 16 alphanumeric characters. Spaces are not permitted in the
location name.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
COMPANION RECIPIENT FIELD VALUES.... Enter the recipient field values which should be equated to this
Location ID.
Once you have equated a Location ID to a specific set of Recipient field names, you may use this value on those
panels permitting specification LOCATION NM.
© 2013 Mantissa Corporation. All rights reserved.
97
CHAPTER 3: IMPLEMENTATION STRATEGY
Chapter 3: Implementation Strategy
RMS/Online® Version 11.35
Chapter 3: Implementation Strategy
System Reference Guide
Auto Report Definition Panel
RMS/DD - Auto Report Definition
Mode: ADD
Date: Monday,
Disn: RDMSCASE
10/07/96 Time: 13:11:05
Report ID
==>
DS Name ==>
DS Prefix ==>
Report ID Line ==>
Report ID COL ==>
Length
==>
Var Title Line ==>
Var Title COL ==>
Length
==>
Default Copies ==> 01 Priority
==> 5000
Def Media ==> HARDCOPY
Append (N/Y)
==> N
---------------------- Report Recognition Information ----------------------ID Data 1 =>
Line =>
COL =>
ID Data 2 =>
Line =>
COL =>
--------- Recipient Field Line/Column Coordinate or Constant Value ----------Recipient Field Name / Line / C/O / C/S / Constant(10) or Search(30) Value
REGION
(01) /
/
/
/
COMPANY
(02) /
/
/
/
CLIENT
(03) /
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
PF1=Help PF3=End PF4=Ret ENTER=Update/Inq
RM9134I Enter information for new record.
Figure 14. Auto Report Definition Panel
The Auto Report Definition panel provides powerful facilities for defining multiple reports with one panel. Many of
today’s application systems, especially packaged systems, have very consistent report formats. Such formatting lends
itself to definition using the Auto Report Definition panel. When you use this panel, you are basically saying that the
formatting of the report is consistent enough to provide the report ID and index titling information on a global basis.
You will notice that the Auto Definition has Report ID Line and Variable Title Line fields which permit you to specify
where RM80004 should look for these fields. Each time the indicated report ID data in the actual report changes,
RM80004 generates an internal definition for a new report.
NOTE: For Auto Report Definition fields not documented below, consult the Custom Report Definition
panel field descriptions.
98
REPORT ID LINE
DEFAULT: None
This field specifies the line number of the report ID field on the
application report. This line number is obtained from the
RM80004 Map.
REPORT ID COL
DEFAULT: None
This field specifies the column number of the Report ID field
on the application report. This column number is obtained
from the RM80004 Map.
LENGTH:
DEFAULT: None
This field contains the length of the Report ID to be
taken from the report page. This length is used by RM80004 to
determine when a new report definition should be internally
generated.
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Creating A Distribution Definition
Step by Step
RMS/Online® Version 11.35
Overview
Creating A Distribution Definition
Step by Step
System Reference Guide
VARIABLE TITLE LINE
DEFAULT: None
The field specifies the length of the title information to be
obtained from the report.
Content/Recipient Conversion Panel
RMS/DD - Content/Recipient Conversion
Mode: ADD
Report ID
Date: Monday,
Disn: RDMSCASE
10/07/96 Time: 13:12:35
==>
Report Field Content To Recipient Conversion VALUES
NOTE: Only one set of original/converted field
values may be entered below.
Report FLD
REGION
COMPANY
CLIENT
/ If Report Field Contains........ / Then Set Recipient Field To....
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
PF1=Help PF3=End PF4=Ret ENTER=Update/Inq
RM9134I Enter information for new record.
Figure 15. Content/Recipient Conversion Panel
The Content/Recipient Conversion panel is used to substitute some value for a recipient element. Most applications
do not require this capability. The panel is used to alter otherwise unsuitable key elements to achieve the proper sort
sequence of distribution keys. For example, consider an application where 3 reports are to be distributed for 2
endpoints.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
If one of the 3 reports had an endpoint name rather than the actual endpoint number (bank number, department
number, etc.), then the Content/Recipient panel could be used to substitute the endpoint number for the non-usable
name on that report.
NOTE: Only one set of fields may be entered per panel. These fields must be on the same panel row.
REPORT ID
DEFAULT: None
This field identifies the report to which the content to recipient
conversion applies. An * may be used here to make this conversion apply to all Report ID’s.
REPORT FLD
DEFAULT: None
This field is initialized by the system and contains the name of
the recipient field entered in the Distribution Options panel.
IF THE REPORT FIELD CONTAINS
DEFAULT: None
Enter the value here that you wish to have converted.
© 2013 Mantissa Corporation. All rights reserved.
99
CHAPTER 3: IMPLEMENTATION STRATEGY
Chapter 3: Implementation Strategy
RMS/Online® Version 11.35
Chapter 3: Implementation Strategy
System Reference Guide
THEN SET RECIPIENT FIELD TO...
DEFAULT: None
Enter the converted value to be placed into the recipient field
identified by “Report FLD.”
Recipient/Recipient Convert Panel
RMS/DD - Recipient/Recipient Convert
Mode: ADD
Date: Monday,
Disn: RDMSCASE
10/07/96 Time: 13:14:19
Report ID ==>
Recipient To Recipient Conversion Criteria
Recip FLD NM / When Recipient Fields Contain
MEDIA*CATEGO /
/ Set Recipient Fields To .......
/
REGION
COMPANY
CLIENT
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
PF1=Help PF3=End PF4=Ret ENTER=Update/Inq
RM9134I Enter information for new record.
Figure 16. The Recipient/Recipient Convert Panel
This panel permits the conversion of one or more recipient field elements from one value to another. You are not
restricted as in the Content/Recipient panel to one field pair. You may, for instance, compare for two recipient fields
and only convert one field. The field you convert does not have to be the same field you used for the comparison.
100
REPORT ID
DEFAULT:
This field identifies the report to which the Recipient/Recipient
conversion applies.
RECIP FLD NM
DEFAULT
This field is filled in by the system using the recipient field
names assigned in the Distribution Options panel.
WHEN RECIPIENT FIELDS CONTAIN...
DEFAULT: None
These fields contain the comparison values on which
RM80004 bases its decision to proceed with the recipient field
conversion.
SET RECIPIENT FIELDS TO
DEFAULT: None
These fields represent the converted values that will replace the
original recipient fields if the comparison recipient fields all
match the indicated values.
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Creating A Distribution Definition
Step by Step
RMS/Online® Version 11.35
Overview
Creating A Distribution Definition
Step by Step
System Reference Guide
Automatic Packaging Panel
RMS/DD - Automatic Packaging
Mode: ADD
Packet Name
Sep Pages
Outplex Num
Message Txt
==>
==> 2
==> 1
==>
Recipient Field Name
MEDIA*CATEGORY
LOCATION*ID
or
REGION
(01)
COMPANY
(02)
CLIENT
(03)
Date: Monday,
Disn: RDMSCASE
10/07/96 Time: 13:15:46
Indx Copies ==> 1
Location Nm ==>
/ When Recipient Fields Contain
/
/
(Either Location or Recipient)
/
/
/
/
/
/
/
/
/
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
RM9134I Enter information for new record.
Participates In --(N/Y)
LOC.
PKT. Accounting
Name
Name Break
ENTER=Update/Inq
Panel 1 of 8
Figure 17. Automatic Packaging
The Automatic Packaging panel provides a way to partition the RM80004 output report stream into packets without
having to specifically reference unique recipient field characteristics. Like Custom Packaging, Auto Packaging
permits the creation of varying block letters and message data. Unlike Custom Packaging, you only enter a fraction of
the information that might have to be entered for Custom Packaging. The trade-off is the lack of uniqueness in the
block letter formation, customized message text, etc.
The concept behind Automatic Packaging is quite simple: Recipient characteristics that will govern the partitioning
of the RM80004 output stream will vary on a predetermined basis. If the recipient field values change, then the output
report stream will be partitioned. With Automatic packaging, it is possible to create any number of packets.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
During the Output phase of RM80004 processing, data entered via the Automatic Packaging panel is compared to
page characteristics of the output stream. When the page characteristics and comparison characteristics match, the
current packet is ended and a new one is started.
Values from the chosen recipient field can be placed in the packet name (block letters on separator pages) and in the
message text. This is done by putting *’s in the places where recipient values are wanted. Example: If a packet is
wanted for each company with packet name CL001, CL002, CL003, etc., then the company recipient field would
participate in the packet name formation (“Y” under participate in PKT.NAME). PACKET NAME field would
contain CL and message text might read “SEND TO COMPANY ***”. The same thing may be done with location
name. It can be made to change when the recipient field changes. One notable difference is that multiple fields may
be used to fill in the location name. Therefore, Region and Company could be placed in the location name by using
REGION*COMPANY** in the LOCATON NM, and indicating that those fields participate in the location name.
PACKET NAME
© 2013 Mantissa Corporation. All rights reserved.
DEFAULT: None
This field is used to specify the PACKET NAME prototype.
The name consists of two parts: 1 fixed and 1 variable. The
101
CHAPTER 3: IMPLEMENTATION STRATEGY
Chapter 3: Implementation Strategy
Chapter 3: Implementation Strategy
System Reference Guide
fixed part (usually first) may represent a set character string
that is identifiable as an application prefix. You might, for
instance, make the prefix for accounts payable application AP.
The remainder of the name contains asterisks to indicate variable positions in the name. These variable positions are filled
sequentially with values derived from the recipient fields designated as participants in the packet name formation.
SEP PAGES
DEFAULT: 2
This field is used to override the default number of RM80004
separator pages. From 0 to 9 pages may be generated for each
packet. This value may be overridden if separator are specified
on the corresponding output characteristics panel (panels 2-8)
for the media specified.
INDX COPIES
DEFAULT: 1
Use this field to designate the number of copies of either the
global index (if INDX PACKET = Y) or the packet index (the
default). From 0-9 may be specified.
OUTPLEX NUM
DEFAULT: 1
Specification of “N” indicates that this Automatic Packaging
panel describes a packet that is to have the reports aligned on
even page boundaries within the packet. This will cause all
reports to be produced with an even number of pages. Specification of 2,4,6,8 is also supported.
LOCATION NM
DEFAULT: PACKET NAME
This field designates the name of the location receiving the
report packet. A location name must be an alphanumeric character string of from 1 to 16 positions. Spaces are not permitted
in the location name.
MESSAGE TXT
DEFAULT: None
Used to designate up to 30 characters of message text data to
be printed on this packet separator pages.
RECIPIENT NAME FIELD/WHEN RECIPIENT FIELDS CONTAIN
These fields specify the conditions under which the packet
defined by this panel is to be created. Media category refers to
the DEF(AULT) media assigned in the Custom Report Definition transaction. Specify a Location value only if you have
used the Recipient to Location Equate transaction to equate the
referenced location.
PARTICIPATES IN ACCOUNTING BREAK
102
DEFAULT: Packet level accounting
The Accounting Break field is used to specify sub-accounting
breaks for the packet INDEX report. Enter Y on the same line
as the recipient field(s) for which you desire sub-accounting.
Each time any of the indicated recipient fields change, total
lines and pages are printed for the packet.
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Creating A Distribution Definition
Step by Step
RMS/Online® Version 11.35
RMS/Online® Version 11.35
Overview
Creating A Distribution Definition
Step by Step
System Reference Guide
PARTICIPATES IN LOC. NAME
DEFAULT: N
This field is used to indicate that this recipient field will participate in the formation of the location name for each packet that
is created. Multiple fields may participate. The location of
these in the location name is indicated by placing *’s in the
LOCATION NM field.
PARTICIPATES IN PKT. NAME
DEFAULT:N
This field indicates that this recipient field will participate in
the formation of the packet name and the message text field for
each packet created. Only one field may participate. Where it
goes in the packet name is indicated by placing *’s in the
PACKET NAME field.
Data Insertion Panel
RMS/DD - Data Insert
Mode: ADD
Location Nm ==>
Start Date
Report ID
Insert Seq.
Copy Number
Copy Cond
User CC N/Y
Numb. Times
==>
==>
==>
==>
==>
==>
==>
Date: Monday,
Disn: RDMSCASE
Packet Name
==>
Media Category ==>
End Date
==>
10/07/96 Time: 13:17:39
Duration
==>
(LT,LE,EQ,NE,GT,GE)
<- Y If you will supply print carriage control
Before Report N/Y ==>
On Report N/Y ==>
After Report N/Y ==>
On Start Sep N/Y ==>
On End Sep N/Y ==>
--------------------------- Insertion Information ----------------------------TYP LN CCC
....+....1....+....2....+....3....+....4....+....5....+
PF1=Help
PF3=End
PF4=Ret
ENTER=Update/Inq
Panel 1 of 2
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
Figure 18. Data Insertion
The Data Insertion panel(s) are used to selectively insert print or control information in the distributed report stream.
The Data Insertion facility could, for instance, be used to add formatting information to the print stream for channel
attached e microfiche systems, DJDE information for 9700/8700 laser printers, or on a more simplistic level,
customized address or banner page information.
LOCATION NM
© 2013 Mantissa Corporation. All rights reserved.
Limits the insertion operation to packets having a location
name matching this value.
103
CHAPTER 3: IMPLEMENTATION STRATEGY
Chapter 3: Implementation Strategy
RMS/Online® Version 11.35
Chapter 3: Implementation Strategy
System Reference Guide
PACKET NAME
DEFAULT: NONE
This field is required and is used to designate the distributed
packet in which data will be inserted. The packet name is the
same as the name assigned via the Custom Packaging and Auto
Packaging panels.
MEDIA CATEGORY
DEFAULT: HARDCOPY
Limits the data insertion operation to packets of the designated
media type.
START DATE
DEFAULT: NONE
Use the start date field (YYMMDD) to indicate the beginning
date this record should become effective.
END DATE
Default: NONE
Use end date (YYMMDD) to invalidate this record after a specific date.
DURATION
DEFAULT: NONE
You may specify the duration instead of the end date. If both
end date and duration are specified, end date takes precedence.
REPORT ID
DEFAULT: NONE
This field specifies the name of the report with which inserted
data is to be associated, i.e., if report ID is equal to
“xxxxxxxx”, then insert the designated data.
INSERT SEQ.
DEFAULT: NONE
This field is required and contains a user-defined sequence
number that will govern the order in which data will be
inserted.
COPY NUMBER
DEFAULT: 01
This field is used to designate the copy number of the report for
which the Data Insertion is to be active.
COPY COND.
DEFAULT: EQ
This field specifies the condition relative to the copy number
field that will govern the insertion of the specified data.
EQ
GE
GT
LE
LT
NE
USER CC N/Y
104
- equal to (default)
- greater than or equal to
- greater than
- less than or equal to
- less than
- not equal
DEFAULT: (N)o
Specifying (Y)es indicates that the user will supply carriage
control. Note that this is another way of saying that you will
enter position 1 of each print line supplied. VSE Users must
specify ‘Y’ and carriage control must supplied.
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Creating A Distribution Definition
Step by Step
RMS/Online® Version 11.35
Overview
Creating A Distribution Definition
Step by Step
System Reference Guide
NUMB. TIMES
DEFAULT: 1
Indicates the number of times (1-9) that the data will be
inserted.
BEFORE REPORT N/Y
DEFAULT: N(o)
Specifies whether the inserted data is to be placed before the
report specified.
ON REPORT N/Y
DEFAULT: (N)o
Limits the data insertion to printing on report pages for the designated report ID.
AFTER REPORT N/Y
DEFAULT: N(o)
Limits the data insertion operation to insertion AFTER the designated report ID.
ON START SEP N/Y
DEFAULT: (N)o
Limits the data insertion operation to insertion on each of the
packet start separator pages.
ON END SEP N/Y
DEFAULT: (N)o
Limits the data insertion operation to insertion on each of the
packet end separator pages.
Insertion Information
TYP
LN
CCC ....1....+....2....
Each of the Insertion Information lines may contain hexadecimal or character information that will participate in the
insertion operation. Each line contains the type (TYP), line (LN), column (CCC), and actual information to be
inserted (....+....).
Valid entries in the TYP field are (C) for character or (X) for hexadecimal.
The line number represents a relative line slot (1-50) if User CC N/Y is Y. Otherwise, line indicates the line on which
the data is to be printed.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
Column (CCC) represents the start column for this data string. The data line is in the format.
1-1
Print control command must be provided if User CC is (Y)es.
Machine control characters are required.
2-204
Print information
NOTE: NOTE: An additional Data Insertion panel is available for up to 20 additional lines of information.
Any number of Data Insertion panels may be created. Keep in mind that the
INSERT SEQ ==> field is used to dictate the order that the lines are marked.
© 2013 Mantissa Corporation. All rights reserved.
105
CHAPTER 3: IMPLEMENTATION STRATEGY
Chapter 3: Implementation Strategy
RMS/Online® Version 11.35
Chapter 3: Implementation Strategy
System Reference Guide
Data Stream Insertion Overview
What is Data Stream Insertion?
Data Stream Insertion is the ability to insert lines of data at specified points in output print streams.
What advantage does this offer user?
Data Stream Insertion gives a user the ability to insert native mode DJDE data before and after separator pages
and individual reports. This makes available a full range of 9700/8700 capabilities through the use of simple
keyword commands.
How does the Data Stream Insertion capability operate?
Data Stream Insertion can operate at the logical report level. By making use of RDMS’ ability to combine all
the reports for a given distribution endpoint, the data stream insert capability permits you to switch from
portrait to landscape, change forms, etc. for each report and for each user if necessary. Using the
INSERT*DATA*STREAM command, you simply code the DJDE commands and designate where they are to
be inserted in the output print stream.
Does application code need to be changed?
No.
What about other uses?
Other uses include:
1. Insertion of on-line or off-line microfiche formatting commands.
2. Generation of customized separator pages.
3. Insertion of additional handling instructions.
4. Special user message insertions.
5. Report cover page generation.
TESTING YOUR INSTRUCTION SET
The RM80004 commands generated by RMS/DD must be tested for both syntax and logic errors. In order to simplify
the test process,you can organize the testing into two steps. In the first step use RM80004 to syntax edit our
instruction set without actually attempting to distribute the report. By doing this you can execute and edit as many
times as necessary without the creation of unwanted output.
Once all edit errors are corrected, you can perform the second step in the command testing. In this step you perform
an actual RM80004 distribution run to test the validity of the definition. The test facilities available in RM80004
enable you to verify distribution key generation and packaging without actually printing reports. The following
outlines the effort necessary to accomplish command testing.
•
In order to test the commands, you will use the example job control stream, RMSRUN. This JCL is supplied with
the system installation materials, and should be available as a result of the first installation task. The following
changes are to be made to this run stream:
Supply a JCL JOB card compatible with installation standards.
Review the symbolic parameters specified on the PROC statement making the required changes.
The RM80004 command input for this job should be a RUN*OPTION command specifying
INSTRUCTION*SET*NAME as its only parameter. The name of your distribution set should be specified as the
value for this parameter.
Change the Distribution Option record by specifying ‘Y’ in the Diagnose field. If DIAGNOSE=Y, RM80004
ignores the dataset select records and produces no output.
Repeat the scan and review until all errors/warnings are identified and corrected.
106
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Testing Your Instruction Set
Step by Step
System Reference Guide
•
Chapter 3: Implementation Strategy
Overview
Instruction Set Reorganization
Step by Step
Once the Instruction Set is edited, logical correctness must be verified. In this test, we perform an actual
RM80004 execution to verify the distribution performed.
Testing is performed at several levels.
1.
Set the Packet Page Limit to 10. This allows us to execute a full distribution run limiting the actual output to a
few pages per endpoint. This provides a means by which you can verify the endpoint breakdown process without
producing all the output.
2.
We submit the RM80004 JCL for a test run specifying the name of the Instruction Set.
3.
Upon completion of the test run, review the command audit trail for errors and/or warnings. If any are found, correct them.
4.
Each RM80004 execution produces a management report providing a list, by packet, of each report distributed to
the endpoints. This report is produced with the banner page title “MANIFEST”. Locate the manifest and review
the reports that RM80004 distributed in each of the packets. If the reports listed agree with stated distribution
requirements, proceed with the next review item. If it does not agree, review the key trace data locating the keys
being generated in error and correct the corresponding RM80004 commands.
5.
Now we review each of the packets to verify the report consolidation process. We check to ensure that all reports
placed in a packet do, in fact, belong there. If the packet structure is correct, we have completed the command
stream test. If the packet structure is not as it should be, correct the appropriate panels and repeat the test steps.
6.
Reset the packet page limit to the maximum value before placing it in production status.
INSTRUCTION SET REORGANIZATION
Distribution Instruction Sets generated with RM80004/DD may require reorganization when the initial distribution
options record contains either a recipient field length or an order designation which does not accurately reflect the
actual length of the recipient field or the defined hierarchy (via the ORD field) produces undesirable report ordering.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
Access to the Set Reorganization panel is via the ADR transaction. The name of the instruction set to be reorganized
is entered with the transaction code (ADR) from the main menu panel. Set Reorganization implies the creation of
another instruction set under the name entered in the REORGANIZED SET NAME ==> field
© 2013 Mantissa Corporation. All rights reserved.
107
CHAPTER 3: IMPLEMENTATION STRATEGY
RMS/Online® Version 11.35
RMS/Online® Version 11.35
Chapter 3: Implementation Strategy
System Reference Guide
Set Reorganization Panel
RMS/DD
- Set Reorganization
Mode: ADD
Date: Monday,
Disn: RDMSCASE
10/07/96 Time: 13:20:10
Reorganized Set Name
==>
Strt Reorganization(N/Y) ==> N
Existing Organization --------ORD Recipient Field Name / LEN
1
REGION
(01) / 01
2
COMPANY
(02) / 02
3
CLIENT
(03) / 03
/
/
/
/
/
New Organization -------------ORD Recipient Field Name / LEN
/
/
/
/
/
/
/
/
NOTES ==>
==>
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
RM9134I Enter information for new record.
Prev
Order
ENTER=Update/Inq
Instruction Set Reorganization.
The EXISTING ORGANIZATION fields on the panel simply reflect the status of the Distribution Master/Options at
the time the reorganization panel was displayed. These fields are for informational purposes only and may not be
changed.
The NEW ORGANIZATION section of the panel permits the following:
1.
Rearrangement of existing recipient field(s)
2.
Deletion of recipient field(s)
3.
Addition of recipient field(s)
Set Reorganization is subject to the same limitations/constraints as the Distribution Master/Option, i.e., total length of
all fields may not exceed 30 characters, new ORD fields must be ascending/consecutive order, etc. The PREV(ious)
LEN(gth) and ORDER fields must be specified when recipient field values in the existing definitions are to be
retained/carried forward to the reorganized instruction set.
NOTE: Set Reorganization is initiated when all edit checks are successful and Y is entered in the STRT
REORGANIZATION (N/Y) ==> field. Lengthy set reorganization could take some time, but most
will complete in a few seconds.
The Set Reorganization transaction may be used to copy an existing instruction set by specifying all of the existing
fields in the PREV(ious) LEN(gth) and PREV(ious) ORDER fields.
108
© 2013 Mantissa Corporation. All rights reserved.
Chap_03(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 3: IMPLEMENTATION STRATEGY
Overview
Instruction Set Reorganization
Step by Step
RMS/Online® Version 11.35
Chapter 4: Repository Management
Concepts
Types of Repository datasets
System Reference Guide
Chapter 4
REPOSITORY MANAGEMENT
Concepts
This chapter contains information on the RMS system components used to archive, recover, backup, reload, and
manipulate the content of the repository. Managing the RMS repository though not a difficult task, requires that you
understand the characteristics of repository datasets and how RMS system components may be used to manage these
datasets.
Even decisions that seem minor at this point can come back to haunt you later. A good example is the decision made
relating to the way repository datasets are named. You may have noticed that considerable attention is given to this
subject. Though we can’t force you to chose a naming convention that will permit bulk management of the repository
by application, every installation is inevitably faced with a situation where they find it desirable to archive and purge
repository datasets by parent application system. If a naming convention like the one we suggest has been used, an
application system that creates 40 BASE datasets can be archived and purged from the repository with two control
statements. The same task without such order could take as many as 41 control statements.
TYPES OF REPOSITORY DATASETS
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
Datasets are said to be managed if there is a fileset name associated with the dataset. The fileset name is like a
mailing address. Just as an address would tell the post office where to send a letter, the fileset name tells the RMS
Controller index task where to store the index elements for a dataset. As the term managed implies, there are many
essential report management functions that take place automatically. If no fileset name is assigned, there can be no
index. No index means that the dataset is non-managed.
With the exception of transient internal use datasets, there are only two types of datasets that reside in the RMS
repository, BASE and Distributed. BASE datasets contain the SYSOUT report information created by your
application system and subsequently placed in the repository by the subsystem or external writer interface. Base
datasets may be either managed or non-managed. Base datasets become managed datasets when the external writer or
subsystem interface assigned a fileset name.
Distributed Datasets as the name implies are the result of the distribution of some or all of the information contained
in one or more BASE datasets. All distributed datasets are managed datasets. The following table is a summary of the
more prominent attributes of each type of repository dataset.
REPOSITORY DATASET TYPE
ACTION / ATTRIBUTE
Creation
© 2013 Mantissa Corporation. All rights reserved.
NON-MANAGED BASE
by customer application system.
Placed in Repository by
subsystem or external writer
interface.
MANAGED BASE
(GROUP ARCHIVE)
DISTRIBUTED
(GROUP ARCHIVE)
by customer application system. RM80004
Placed in Repository by
subsystem or external writer
interface.
109
CHAPTER 4: REPOSITORY MANAGEMENT
The strategy you adopt in managing the RMS repository will have a direct bearing on the ease with which the
repository can be managed. For example, if your strategy is to maintain access to reports for 30 days while keeping
the size of the RMS repository at the lowest possible level, you would want to set the data retention of these reports to
a value considerably less than 30 days. If you do not find it desirable to view BASE datasets because of the space
these datasets would take in the repository, you would not assign a fileset name to BASE datasets and would delete
these datasets as soon as they were distributed.
RMS/Online® Version 11.35
Chapter 4: Repository Management
Concepts
RMS Archive Types
Base Archive Creation / Life Cycle
System Reference Guide
REPOSITORY DATASET TYPE
ACTION / ATTRIBUTE
MANAGED BASE
(GROUP ARCHIVE)
NON-MANAGED BASE
DISTRIBUTED
(GROUP ARCHIVE)
No
No
RM80001
Actual Deletion
Viewable
RM99998 (RMS Controller
Purge Task)
No
Printing
RM80001
requested by user of RMS/
Online
Yes
Yes
RM90008 based on retention
criteria
RM99998 (RMS Controller
Purge Task)
Yes if Softcopy. All other
distributed medias may be
reloaded and viewed
requested by user of RMS/
Online
Reloading
RM80001
Backup
Restore
RM80001
RM80001
may be reloaded for viewing by
RM10000 (RMS Controller
Recover Task)
RM90007
RM90008
may be reloaded for viewing by
RM10000 (RMS Controller
Recover Task)
RM90007
RM90008
Yes
Yes
RM90008 based on retention
criteria
RM99998 (RMS Controller
Purge Task)
Yes
RMS ARCHIVE TYPES
RMS supports the following archive types. Each one of these archive types can be used to achieve different
objectives.
ARCHIVE TYPE
CREATED BY
WHEN?
BASE
RM80001
On Demand
Packet
RM80004
During Distribution
Retention-Based
Control Region
Automatically, based
on retention criteria
CHARACTERISTICS
Frees Repository space, permits recovery of any number of
BASE datasets
Permits printing of all or part of a distributed packet.
Recovery may be initiated by batch job or RMS/ONLINE
transaction.
Permits reload and printing of individual reports. Recovery
is initiated from RMS/Online
Base Archive Creation / Life Cycle
BASE archive is used for the high-speed backup and or removal of BASE datasets from the repository. Usually this
type of archive is coordinated with the distribution of the content of the BASE datasets so that a snapshot of the
original application output is created and held pending any requests for lost distributed reports. As you will see from
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 4: REPOSITORY MANAGEMENT
File set name
Indexed
Scheduled for Deletion
110
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 4: Repository Management
Concepts
RMS Archive Types
Packet Archive Creation / Life Cycle
System Reference Guide
the description of the Retention-based archive, individual reports may be recovered from retention-based archives as
well. BASE archives are created by RM80001. A full discussion of the capabilities of this program can be found later
in this chapter.
BASE Archive Creation / Life Cycle
Application
Drain Operation
1
Systems
Base Dataset Use
Base Dataset Deletion
1. Datasets are resident in Repository after Drain Operation
2. RM80001 may request deletion of the dataset
Packet Archive Creation / Life Cycle
Packet archives are created as a normal by-product of the distribution process. Packet archives represent a snapshot of
all the reports as distributed by RM80004. Packet archives might be used to re-print the entire content of a packet or
selected reports from a packet.
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
Packet Archive Creation / Life Cycle
Application
Systems
Drain Operation
Recovery Operations
Report Distribution
Archive Expires
1
2
1. Packet Archive files contain a snapshot of all the output created for a Distribution process.
2. Archive expiration is based on desired recoverability for Packets.
© 2013 Mantissa Corporation. All rights reserved.
111
CHAPTER 4: REPOSITORY MANAGEMENT
2
Base Dataset Archive
RMS/Online® Version 11.35
Chapter 4: Repository Management
Concepts
FileSet Backup and Restore
Retention-Based Archive Creation / Life Cycle
System Reference Guide
Retention-Based Archive Creation / Life Cycle
Retention-based archives may contain BASE datasets and/or distributed datasets that have like retention
characteristics. A retention-based archive maximizes storage management by ensuring that all reports in a specific
file expire at the same time. This type of archive is based on characteristics in the retention control record(s).
Retention-Based Archive Creation / Life Cycle
Application
Systems
Drain Operation
Archive Creation
CHAPTER 4: REPOSITORY MANAGEMENT
Archive Expires
2
Report Distribution 1
Recovery/Reload
3
1. Retention Records govern retention-based archive. Archive summary files are produced.
2. Summary files are processed by RMS Controller Archive tasks.
3. Archive files contain reports with same retention characteristics.
FILESET BACKUP AND RESTORE
RM90007 (Backup) Processing
The backup program places all data from the managed files into a variable blocked sequential dataset. This backup
file is in a sequence necessary and required by the restore program for proper retention record handling. See the JCL
Installation Library for current JCL procedures. RM90007 has no control statements.
112
© 2013 Mantissa Corporation. All rights reserved.
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
RMS/ONLINE files are maintained through the use of the backup and restore programs (RM90007 and RM90008,
respectively). Through the combination of Control Statements and retention control records, the report information in
the fileset can be kept at appropriate retention levels.
RMS/Online® Version 11.35
Chapter 4: Repository Management
Concepts
FileSet Backup and Restore
RM90008 (Restore) Processing
System Reference Guide
RM90008 (Restore) Processing
The restore process reads the file created by the backup and places either all the data or selected data into the output
files. If a full restore is requested, then all data is restored. If a partial restore is requested, then all administrative and
system control records are restored, but only report data and control records which meet the criteria specified in the
retention control records are restored. If update is specified, the INDEX is updated in place with retention control
characteristics being taken into consideration.
It is recommended that both the backup and restore process be completed daily using the $R UPDATE option. It is
very important that these backups be kept for file recovery should disk I/O errors occur.
Recommendation
1.
The Backup should be run at least once daily.
2.
The Restore process should be run once each day.
3.
The Restore should be run in $R UPDATE mode so that all other system components can proceed without interruption.
Weekly and/or Monthly Backup / Restore
1.
The Backup/Restore process may be run on a weekly or monthly basis so that the VSAM files can be deleted and
redefined. This clears any control area/control interval splits that may have occurred.
2.
The restore mode should be $R PARTIALCLEAR for those customers that have only one fileset serviced by the
target SUBSYSTEM. This will drop any datasets that have passed their required retention. The CLEAR will
cause all datasets in the subsystem to be cleared. This reduces the file space requirements on the spool files for
the restore process. Without the CLEAR, the restore will require double the space for the data elements.
3.
The restore mode should be $R PARTIALSYNC for those customers that have more than one fileset serviced by
the target SUBSYSTEM.
4.
CICS files must be closed and de-allocated during a FULL, FULLCLEAR, PARTIALCLEAR, OR PARTIALSYNC operation.
5.
The RMS control region associated with this fileset must be brought down.
CONTROL STATEMENTS FOR RM90008
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
POS
1-3
POS 4-80
MODE
$R
PARTIALCLEAR
LOAD
$R
PARTIAL
LOAD
$R
PARTIALSYNC
LOAD
$R
FULLCLEAR
LOAD
$R
FULL
LOAD
© 2013 Mantissa Corporation. All rights reserved.
FILE STATUS
VSAM FILES
Reload of VSAM
files, retention
considered.
Reload of VSAM
files, retention
considered.
Reload of VSAM
files, retention
considered.
All files loaded
from tape.
All files loaded
from tape
FILE STATUS
REPOSITORY
RETENTION
CONTROL
FILE
ACCESS
CONTROL*
REGION
All datasets for all
filesets are deleted.
Applies
No
Down
All datasets for this
fileset will be
deleted.
All datasets for this
fileset will be
deleted.
All datasets for all
filesets are deleted.
All datasets for this
fileset will be
deleted.
Applies
No
Down
Applies
No
Down
Ignored
No
Down
Ignored
No
Down
113
CHAPTER 4: REPOSITORY MANAGEMENT
Daily Backup / Restore
RMS/Online® Version 11.35
Chapter 4: Repository Management
Concepts
Repository Sharing among Filesets
Recommendation
System Reference Guide
CONTROL STATEMENTS FOR RM90008
POS
1-3
$R
POS 4-80
FILE STATUS
VSAM FILES
MODE
UPDATE
UPDATE
Index for all files
past retention are
scheduled for
deletion.
FILE STATUS
REPOSITORY
RETENTION
CONTROL
Datasets past
retention are
scheduled for
deletion.
FILE
ACCESS
Applies
Yes
CONTROL*
REGION
Up
$M1
“STARTUP
MESSAGE”
to console
$M2
“TERMINATION
MESSAGE”
to console
*The controller region which has been started with the INDEXOFF option need not be terminated.
REPOSITORY SHARING AMONG FILESETS
CHAPTER 4: REPOSITORY MANAGEMENT
The datasets in multiple filesets may be pooled by using a common repository. Prior to release 11, a VSAM dataset
(QXRQDS) was used to store report data. Pre-release 11 filesets looked like the diagram below:
FILE SET 1
FILE SET 2
QXRQDS
(Data)
QXRQDS
(Data)
QXRCDS
QXRCDS
(Index)
(Index)
QXDCDS
QXDCDS
(Distrib)
(Distrib)
QXACDS
(Admin)
QXACDS
(Admin)
Each of these filesets had their own QXRQDS prior to RMS release 11.0. The following schematic shows the
relationship of the files using a common repository for the storage of the data objects.
FILE SET 2
FILE SET 1
QXRCDS
QXRCDS
QXDCDS
QXDCDS
(Distrib)
(Distrib)
QXACDS
QXACDS
(Admin)
(Admin)
RMS v.11 Repository
QXRQDS
(up to 255 Volumes of Data)
114
© 2013 Mantissa Corporation. All rights reserved.
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
(Index)
(Index)
RMS/Online® Version 11.35
Chapter 4: Repository Management
Concepts
RM80001 - Base Dataset Management Utility
Guide to Commands
System Reference Guide
Index objects remain in the same files they were in prior to release 11. Using this approach offers the following
advantages:
•
The data objects may be purged and the space recovered without taking the systems out of service.
•
Over allocations for each of the datasets can be consolidated resulting in less wasted space.
•
Base datasets stored in separate datasets prior to release 11 may be stored in a consolidated repository beginning
with release 11.
The backup/restore process takes into consideration the fileset to which the data objects belong. Only those data
objects associated with the index data in a fileset is placed on a backup file created by RM90007.
Restore processing (partial or full) attempts to delete repository datasets appearing in the backup file. If data objects
have been deleted through the communication interface or because of a previous reload of the file, a purge operation
will be attempted. This may result in the production of diagnostic messages by the purge processing task. These may
be ignored.
This section describes the functional characteristics of the archive management program RM80001. Explanations of
the command structure and examples of the use of these commands in typical production environment situations are
included. Refer to the installation section of this manual for a description of the installation procedures and file
requirements for this program.
Readers are assumed to have a data management background and knowledge of the Job Control Language (JCL) for
your system.
Guide to Commands
The following table contains a cross reference of various report management tasks and the commands used to
accomplish those tasks. The left column lists the task. The middle column more fully describes the task. The right
column lists the command used to perform the task.
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
TASK
DEFINITION
ARCHIVE
One or more BASE datasets
ASSIGN
INSERT
RECOVER
Output attributes to segment of report data
Data into the print stream
One or more BASE datasets from an
archive file
BASE datasets for processing
Reporting audit line count
SELECT
SET
COMMAND
RUN*MODE
(ARCHIVE parameter)
OUTPUT*CONTROL
INSERT*DATA*STREAM
RUN*MODE
(RECOVER parameter)
SELECT
RUN*OPTIONS
System Facilities
RM80001 performs all the functions necessary for the interpretation of control commands, location of base datasets,
and subsequent processing of report data. Output media type is also controlled by these programs.
Detailed information regarding the size and characteristics of the base datasets processed is produced during each
execution. Hardcopy and system log output also record any unusual situations encountered by the system. All
commands are listed during each execution.
© 2013 Mantissa Corporation. All rights reserved.
115
CHAPTER 4: REPOSITORY MANAGEMENT
RM80001 - BASE DATASET MANAGEMENT UTILITY
Chapter 4: Repository Management
Concepts
RM80001 Use
Selecting Datasets
RMS/Online® Version 11.35
System Reference Guide
Typical uses:
1.
Creation of Microfiche Source.
RM80001 will selectively retrieve entries that are to be placed on microfiche. The reports may be retrieved and stacked in
any order. The various output options are listed below by version of the system.
VSE
Print Image
User Exit Defined
MVS
Print Image
Specific DD -- User Defined
Print
User Exit Defined
2.
Archive Report Data.
CHAPTER 4: REPOSITORY MANAGEMENT
RM80001 provides a complete backup and recovery system. The archive facility can reduce costly reruns and
provide better end user service.
3.
Release of repository space.
Repository space may be scheduled for release by executing RM80001 and specifying PURGE and ARCHIVE
in the RUN*MODE command.
4.
Production of Customized Output
The exit facility of RM80001 permits the examination and output of report data. RM80001 passes the report data
line by line to the exit. Simple action codes and a single parameter call list make exit processing as simple as
writing a batch sequential file processing program. Interface consistency guarantees familiarity and ease of
coding for additional applications such as microfiche file conversion.
5.
Management of Non-Managed Datasets.
Non-managed datasets are marked for purge and deleted when the archive tasks are idle.
6.
Report Portability.
Datasets which have been archived can be transported from one operating environment to another. For example,
a VSE archive file can be processed in an MVS environment.
Selecting Datasets
Datasets are retrieved using the qualifying information specified in the select command. The NAME keyword may be
used to specify the full dataset name of from 1 to 8 characters. The GNAME keyword is used to select by name
prefix.
Selection by prefix always implies selection of every dataset that has this prefix. Full dataset name selection will
retrieve only one dataset matching the name specified. When selecting by specific name, if there is more than one
dataset with the specified name, the entry most recently created is selected for processing.
116
© 2013 Mantissa Corporation. All rights reserved.
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
RM80001 USE
RMS/Online® Version 11.35
Chapter 4: Repository Management
System Reference Guide
Concepts
RM80001 Control Statements
Archive Scheduling
Both the NAME and GNAME forms of selection permit positions in the name to be ignored during the comparison.
The positions in the name which are to be ignored are indicated by using a mask character (*) in that position of the
name. For example, all datasets having an ‘A’ in position 1, a ‘C’ in position 3 and a ‘D’ in position 4 will be selected
by using the following command.
SELECT GNAME (A*CD)
Other dataset attributes may be used to refine the selection process. For example, the following dataset select record
will select the dataset DIS01 which also has a class of ‘A’, and a form identification of ‘S1PT’.
The selection qualifiers vary slightly by operating system. The section “Control Statements” contains SELECT
command format and available selection options for each of the systems. Any number of datasets may be selected for
processing during a single execution. Selection by prefix and full name may be intermixed to attain the desired
results.
Archive Scheduling
Typically, archive operations are scheduled based on the DASD space allocated to the RMS repository. The smaller
the repository dataset, the more often archive must be performed. However, the minimum repository size should be
that necessary to hold at least two (2) times the largest work unit to be processed, i.e., output from an application.
This would ensure enough space so that application overlap would not pose a problem.
If DASD space is not a primary concern, a single archive at either the beginning or the end of a production cycle may
suffice. Archive of datasets from the previous processing cycle at the beginning of the next would allow reports to be
available for any necessary processing without scheduling a R E CO VE R job. Whichever approach is selected, careful
thought should be given to the archive process to ensure it meets the individual installation’s needs for report
retention and repository space.
RM80001 CONTROL STATEMENTS
Notation Conventions
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
The notation convention used to describe the format of RM80001 commands is not part of the command structure.
Rather, it serves only as a basis for describing the structure of the commands.
All command-format illustrations adhere to the following conventions:
•
Brackets [ ] indicate an optional parameter or sub-parameter.
•
Braces { } indicate a choice of entry; if no default value is indicated, one of the entries must be chosen.
•
Vertical Bar | is used to separate alternative items. Only one of the items may be selected.
•
Other punctuation such as parentheses, commas, spaces, etc.
must be entered as shown.
•
Bold face indicates the exact characters to be entered. Upper case only.
•
Lower case type in the format illustration specifies data to be supplied by the user.
•
Underscored type indicates a default option. The underscored value is assumed if the parameter is omitted.
© 2013 Mantissa Corporation. All rights reserved.
117
CHAPTER 4: REPOSITORY MANAGEMENT
SELECT NAME (DIS01) CLASS (A) FORM (S1PT)
Chapter 4: Repository Management
Concepts
RM80001 Control Statements
Control Statement
RMS/Online® Version 11.35
System Reference Guide
This section describes the RM80001 control statements. Commands are described in alphabetical order. Parameters
associated with each command are organized by the categories REQUIRED and OPTIONAL. Within these
categories, the parameters are also alphabetized. Parameters may be coded in random order.
Control Statement
Types
Option
The option commands are:
•
RUN*MODE which controls the execution mode of the system.
•
RUN*OPTIONS which activates run options.
•
OUTPUT*CONTROL which assigns output attributes to datasets.
•
INSERT*DATA*STREAM, which inserts print records into output data.
Select
CHAPTER 4: REPOSITORY MANAGEMENT
The select command controls which datasets are retrieved and the order in which they are retrieved.
•
SELECT is used to select specific print BASE dataset entries from the repository or archive dataset.
Order
Generally speaking, commands must be presented to RM80001 in a prescribed order. All RM80001 commands
except the S E LE C T command are optional. When present, the other RM80001 commands should be entered in the
following order.
1.
RU N *M O DE O P TI ON A L
2. RU N *O P TI ON S O PT I ON A L
3.
IN S ER T *D AT A *S TR E AM OP TI O NA L
4.
OU T PU T *C ON T RO L O PT I ON AL
5.
SE L EC T R EQ U IR ED
NOTE: OUTPUT*CONTROL and SELECT commands may be interspersed.
Syntax
All RM80001 commands have the general structure:
COMMAND indicates the functional nature of the service requested; parameters describe the service.
Commands begin at or to the right of the left margin. The margins are 2 and 72. Commands are separated from their
associated parameters (if any) by one or more spaces, comments, or reserved words. A comment is any character string
that begins with $* and ends with *$. Comments may not contain an embedded *$. Commands beginning in position 1 are
assumed to be positional control records.
Parameters
All parameters are keyword parameters. These parameters usually have an associated value. A keyword is a specific
character string. For example, in:
118
© 2013 Mantissa Corporation. All rights reserved.
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
COMMAND parameters .........
RMS/Online® Version 11.35
Chapter 4: Repository Management
Concepts
RM80001 Control Statements
Command Descriptions
System Reference Guide
SELECT NAME (REPORT1)
SELECT is a command and NAME is a keyword parameter that indicates that the value “REPORT1” is the name of a
base dataset to be selected for processing. Value data is always enclosed in parentheses. A value may be a sub-list
with entries that are separated by commas. Parentheses and commas are not permitted as value data.
Continuation
Commands may be continued on several records. Continuation is not permitted between a keyword and its associated
value. Each record except the last must have a hyphen as the last non-blank before or at the right margin. A hyphen
indicates the continuation of a command.
Command Descriptions
•
IN S ER T *D AT A *S TR E AM which permits data to be inserted in the output data stream.
•
OU T PU T *C ON T RO L which assigns output attributes to datasets retrieved by RM80001.
•
RU N *M O DE which controls the execution mode of the system.
•
RU N *O P TI ON S which activates RM80001 run options.
•
SE L EC T which identifies the dataset(s) to be processed.
NOTE: “Notation Conventions” in “About This Book” describes the command documentation notations.
INSERT*DATA*STREAM
The format of the IN S ER T *D AT A *S TR E AM command is:
INSERT*DATA*STREAM
IDS
[AFTER*REPORT*ID (report id)]
[BEFORE*REPORT*ID (report id)]
[ON*REPORT*ID (report id)]
[CONTROL*CHAR]
[INSERT*DATA (line, column, character string)]
INSERT*HEX*DATA (line, column, hexadecimal string)]NUMBER*TIMES
(number of times | 1)]
[ON*END*SEP]
[ON*START*SEP]
[SEGMENT*NAME (segment identifier)]
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
INSERT*DATA*STREAM PARAMETERS
Optional Parameters
AF T ER * RE PO R T* ID (report id)
is an optional parameter that indicates insertion of data after a
specific report ID.
Alternate Keyword(s): ARI
BE F OR E *R EP O RT *I D (report id)
is an optional parameter that indicates insertion of data before a
specific report ID.
Alternate Keyword(s): BRI
ON * RE P OR T* I D (report id)
is an optional parameter that indicates insertion of data on a
specific report ID. Use of O N *R EP O RT *I D will cause the
inserted data to be placed at the bottom of each page of the
report id specified.
© 2013 Mantissa Corporation. All rights reserved.
119
CHAPTER 4: REPOSITORY MANAGEMENT
This section describes each command(s) format and parameters. They are described in the following order:
RMS/Online® Version 11.35
Chapter 4: Repository Management
Concepts
RM80001 Control Statements
Command Descriptions
System Reference Guide
is an optional parameter that indicates print command characters (all skipping and spacing) will be supplied. Machine control characters must be supplied for each line referenced. If
C ON TR O L* CH A R is omitted, the system advances to the top
of a new page (channel 1) before insertion is performed.
Alternate Keyword(s): CC
CO N TR O L* CH A R
NOTE: (VSE) Control*Char is a required parameter in the VSE environment.
IN S ER T *D AT A (line, column, char string) is an optional parameter that provides data to be inserted in
character format.
Alternate Keyword(s): ID
Line
CHAPTER 4: REPOSITORY MANAGEMENT
Column
1-1
2-204
Character String
If the CONTROL*CHAR is specified, Line indicates the relative line slot (150). Otherwise, Line indicates the line on which the data is to be printed.
The starting column for this data string. The data line is in the format.
Print control command (must be provided if CONTROL*CHAR specified.)
Print data. (See note 2.)
Any alphanumeric data string.
IN S ER T *H EX * DA TA (line, column, hexadecimal char string)
is an optional parameter that provides data to be inserted in
hexadecimal format. Alternate Keyword(s): IHD
Column
1-1
2-204
Character String
120
If the CONTROL*CHAR is specified, Line indicates the relative line slot (150). Otherwise, Line indicates the line on which the data is to be printed.
The starting column for this data string. The data line is in the format.
Print control command (must be provided if CONTROL*CHAR specified.)
Print data. (See note 2.)
Any hexadecimal data string. Valid characters are 0-9 and A-F. An odd number
of characters will be right justified with a leading zero. (See note 2.)
NU M BE R *T IM E S (number of times | 1)
is an optional parameter that indicates the number of times (19) the data is to be inserted.
Alternate Keyword(s): NT
ON * EN D *S EP
is an optional parameter that limits this
I NS ER T *D AT A *S T RE AM command to printing the data
stream on the end separator page. At the time the data is to be
inserted, the printer will be positioned at line 49. The user is
responsible for supplying machine control commands for spacing skipping or printing from this point.
Alternate Keyword(s): OES
ON * ST A RT *S E P
is an optional parameter that limits this
I NS ER T *D AT A *S T RE AM command to printing the data
stream on the start separator page. At the time the data is to be
inserted, the printer will be on line 49. The user is responsible
© 2013 Mantissa Corporation. All rights reserved.
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
Line
RMS/Online® Version 11.35
Chapter 4: Repository Management
Concepts
RM80001 Control Statements
Command Descriptions
System Reference Guide
for supplying machine control commands for spacing, skipping or printing from this point.
Alternate Keyword(s): OSS
SE G ME N T* NA M E (segment identifier)
is an optional parameter that limits this
I NS ER T *D AT A *S T RE AM command to a unique packet
or segment name. The S EG ME N T* N AM E is the same as the
name parameter of the CR E AT E* P AC KE T command in
RM80004. Omitting this parameter indicates that the command
applies to all segments.
Alternate Keyword(s): SN
Notes on INSERT*DATA*STREAM
1.
In addition to the R EP OR T *I D referenced in the ID E NT IF Y *F O RM AT command, special report ID’s
have been assigned.
-start separator pages
EN D SE P
-end separator pages
MA N IF E ST
-manifest
* (asterisk)
-all REPORT*ID’s except above
2.
Since continuation of a value within a parameter is not allowed with the key word facility, multiple
IN S ER T *D AT A and/or I N SE R T* HE X *D AT A commands may be used to form an entire line of data
using the column value.
3.
AF T ER * RE PO R T* ID and BE F OR E *R EP O RT *I D may be specified on the same command.
CHAPTER 4: REPOSITORY MANAGEMENT
They are:
ST A RT S EP
OUTPUT*CONTROL
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
The format of the OU T PU T *C ON T RO L command is:
OUTPUT*CONTROL
OUTCTL
[BURST]
[CHARS (name 1[,name 2, name 3, name 4])]
[CLASS (output class | A)]
[COPIES (number of copies | 1)]
[DDNAME (ddname | SELECTED DATASET NAME)]
[DESTINATION (dest ID | LOCAL)]
[DISPOSITION (disp | SPIN)]
[EXTERNAL*WRITER*NAME (name)]
[FLASH (name[,copies])]
[FORM*CONTROL*BUFFER (fcb name)]
[FORM (form name)]
[LRECL (nnn | 133)]
[SEPARATOR*PAGES (number separators | 2)]
[UCS (name)]
OUTPUT*CONTROL Command Summary
OU T PU T *C ON T RO L commands are used to assign the required output characteristics to one or more report
datasets. These characteristics include:
CLASS
COPY COUNT (Job Entry System)
DESTINATION (RJE)
© 2013 Mantissa Corporation. All rights reserved.
121
RMS/Online® Version 11.35
Chapter 4: Repository Management
Concepts
RM80001 Control Statements
Command Descriptions
System Reference Guide
DISPOSITION
FORM
NUMBER OF SEPARATOR PAGES (RM80001 generated)
The relationship between the OU TP U T* C ON TR O L command and SELECT command(s) is positional. When
RM80001 encounters an O U TP UT * CO NT R OL command, it stores all the designated attributes. Every SELECT
command encountered until the next OU T PU T* C ON TR O L command is “tagged” with these attributes. As a result,
multiple SELECT commands may require only one OU T PU T* C ON TR O L command.
OS/MVS RM80001 permits a report dataset to be directed to a specific DD statement with the DDNAME parameter.
All other parameters, with the exception of SE P AR AT O R* PA G ES , are ignored when the DDNAME parameter is
used. Use of DDNAME parameter requires that a DD statement with the indicated name be added to the RM80001
JCL. All such DD statements for RM80001 output must specify full DCB information. When RM80001 output is
directed to SYSOUT, the record format should always be FM. Specification of FBM or FM for disk or tape data sets
will cause position 1 of each record to be lost. Output to disk or tape should be FB or VB.
CHAPTER 4: REPOSITORY MANAGEMENT
When recovering distributed report packets, the parameters specified in the RM80001 O UT P UT * CO NT R OL
statement will be merged with the parameters specified by the OU T PU T *C ON T RO L statement in effect when the
segment was originally created by RM80004. Thus, parameters such as DESTINATION can be coded to cause a
segment originally routed to an RJE destination to be reprinted locally.
OUTPUT*CONTROL PARAMETERS
Required Parameters
None.
BU R ST
Is an optional parameter used to indicate that, if printed on an
IBM 3800 printer, the “Burster, Trimmer, Stacker” feature is to
be used.
CH A RS (name 1[,name 2, name 3, name 4])
Is an optional parameter used to indicate, if printed on an IBM
3800 printer, the names(s) of from one to four character
arrangement tables to be used.
CL A SS (output class | A)
Is an optional parameter used to assign an output class. Valid
entries are A-Z and 0-9. The default is A.
CO P IE S (number of copies | 1)
Is an optional parameter used to designate the JES copy count.
The default is 1. The maximum is 99.
DD N AM E (name | SELECTED DATASET NAME) (MVS ONLY)
Is an optional parameter used to specify the name of a DD
statement that has been added to the RM80001 JCL. The name
supplied must conform to naming conventions. Use of the
DDNAME parameter causes all other parameters to be
ignored. OS/MVS RM80001 will dynamically allocate the output file using the name of the BASE dataset if the DDNAME
parameter is omitted.
DE S TI N AT IO N (dest ID | LOCAL)
122
Is an optional parameter used to supply a remote destination
name. The default destination is LOCAL. JES2 NJE users
should specify NO DE : RE M OT E destinations using the short
© 2013 Mantissa Corporation. All rights reserved.
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
Optional Parameters
RMS/Online® Version 11.35
Chapter 4: Repository Management
Concepts
RM80001 Control Statements
Command Descriptions
System Reference Guide
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
DI S PO S IT IO N (disp | SPIN)
Is an optional parameter used to request alternate disposition of
the output dataset. Specify H for HOLD disposition. The
default is SPIN, the equivalent of FREE=CLOSE.
Alternate Keyword(s): DISP
EX T ER N AL *W R IT ER * NA M E (name)
Is an optional parameter used to specify the external writer
sub-parameter of the SYSOUT parameter in file dynamically
allocated by RM80001.
Alternate Keyword(s): EWN
FL A SH (name[,copies])
Is an optional parameter used to indicate, if printed on an IBM
3800 printer, the name of the forms overlay to be used and
optionally the number of copies on which the forms overlays to
be printed.
FO R M* C ON TR O L* BU F FE R (fcb name)
Is an optional parameter used to request the form control buffer
image to be used.
Alternate Keyword(s): FCB
FO R MD E F (form definition name)
Is an optional parameter used to request the form definition to
be used .
FO R M (form name)
Is an optional parameter used to designate the form identifier
of the output data.
LR E CL (nnn | 133)
Is an optional parameter used to designate the logical record
length. The default is 133.
PA G ED E F (page definition name)
Is an optional parameter used to request the page definition to
be used .
SE P AR A TO R* P AG ES (no. separators | 2)
Is an optional parameter used to enter the number of RM80001
separator pages you wish to have generated. From 0 to 9 pages
may be generated. The default is 2 pages (front and back). This
should not be confused with operating system separator pages
which are produced as the result of printer start-up parameters.
Alternate Keyword(s): SEP
UC S (name)
Is an optional parameter used to describe the character set to be
used for printing on an IBM 1403 or IBM 3211 printer.
“NAME” specifies the one to four character name suffix of the
character set desired.
RUN*MODE (ARCHIVE Mode)
The format of the RU N *M O DE command is:
RUN*MODE
RM
ARCHIVE
© 2013 Mantissa Corporation. All rights reserved.
123
CHAPTER 4: REPOSITORY MANAGEMENT
form NnnnRnnn convention. See JES2 NJE DESTINATION
parameter for a full explanation of this form.
Alternate Keyword(s): DEST
RMS/Online® Version 11.35
Chapter 4: Repository Management
Concepts
RM80001 Control Statements
Command Descriptions
System Reference Guide
[PURGE]
RUN*MODE Command Summary (ARCHIVE Mode)
The R U N* M OD E command, A R CH IV E parameter is used to place RM80001 in ARCHIVE execution mode. The
purpose of the archive facility is to perform back-up operations on one or more datasets residing in the repository.
RUN*MODE PARAMETERS
Required Parameters
is a required parameter used to place RM80001 in ARCHIVE
execution mode.
AR C HI V E
Optional Parameters
is an optional parameter used to request the deletion of datasets
that have been archived.
PU R GE
RUN*MODE (RECOVER Mode)
CHAPTER 4: REPOSITORY MANAGEMENT
The format of the RU N *M O DE command is:
RUN*MODE
RM
RECOVER
[CHECKPOINT*RECOVERY]
RUN*MODE Command Summary (RECOVER Mode)
The R U N* M OD E R EC OV E R parameter is used to place RM80001 in recovery execution mode. This recovery
capability permits entries which have been stored as the result of a previous archive operation to be reprinted or, in
the case of OS/MVS system, returned to the repository. Archive files created by VSE RM80001 may be processed in
an OS/MVS environment.
RUN*MODE PARAMETERS
Required Parameters
is a required parameter used to place RM80001 in RECOVER
execution mode.
RE C OV E R
CH E CK P OI NT * RE CO V ER Y
is an optional parameter indicating to RM80001 that, in addition to reloading the entries selected, the checkpoint subpool
should be reconstructed from the archive volume. This option
should be specified for reloads resulting from a condition that
required an archive “all” and the re-initialization of the repository dataset.
RUN*MODE (RETRIEVE Mode)
The format of the RUN*MODE command is:
RUN*MODE
RM
RETRIEVE
RUN*MODE Command Summary (RETRIEVE Mode)
This RU N* M OD E command is not necessary. This mode is the default R UN *M O DE and the exclusion of this
command will cause the use of the retrieve mode.
124
© 2013 Mantissa Corporation. All rights reserved.
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
Optional Parameters
RMS/Online® Version 11.35
Chapter 4: Repository Management
Concepts
RM80001 Control Statements
Command Descriptions
System Reference Guide
RUN*MODE PARAMETERS
Required Parameters
RE T RI E VE
RUN*OPTIONS
The format of the RU N *O P TI ON S command is:
RUN*OPTIONS
RUNOPT
[INPUT*PROCESS*CODE (comparison value, operation code | EQ)]
[LINE*COUNT (lines per page) | 56]
[OUTPUT*PROCESS*CODE (character string | GENERATE)]
[PASSWORD (character string)]
[USER*ID (character string)]
RUN*OPTIONS Command Summary
RUN*OPTIONS PARAMETERS
Required Parameters
None.
Optional Parameters
IN P UT * PR OC E SS *C O DE (comparison value, operation code | EQ)
is an optional parameter used to restrict RMS execution to a
group of previously processed BASE datasets. The string specified as the comparison value operand can be from 1 to 11 positions. It is compared to the process code value contained in
each dataset selected. A match condition is determined using
the operation code operand. The possible operation codes are:
EQ - equal to (default)
GE - greater than or equal to
GT - greater than
LE - less than or equal to
LT - less than
NE - not equal
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
The use of the masked comparison character “*” in any comparison value position causes that position to be ignored in the
comparison operation. This would allow the selection of
groups of process codes, i.e.,
© 2013 Mantissa Corporation. All rights reserved.
125
CHAPTER 4: REPOSITORY MANAGEMENT
The R U N* O PT IO N S command is used to set various RM80001 execution options.
RMS/Online® Version 11.35
Chapter 4: Repository Management
Concepts
RM80001 Control Statements
Command Descriptions
System Reference Guide
IN P UT * PR OC E SS *C O DE (A**********,NE)
would cause the select of all processed BASE dataset entries
other than those having an “A” in their first position.
Alternate Keyword(s): IPC
Notes on Process Codes:
1.
Once a BASE dataset has been assigned a process code it can only be selected using the
I N P U T * P R O C E S S * C O D E or P R O C E S S * C O D E operands on either the
RU N *O PT I ON S or SE LE C T commands, respectively.
2.
The O U TP U T* PR O CE SS * CO D E operand can be used to change an existing process code.
3.
An I NP UT * PR O CE SS * CO DE of all “*” with an operation code of EQ will result in all process BASE dataset entries being processed.
LI N E* C OU NT (lines per page) | 56)
CHAPTER 4: REPOSITORY MANAGEMENT
is an optional parameter used to set the maximum line count
for the RM80001 system report. Acceptable line count values
are 20 through 66.
Alternate Keyword(s): LC
OU T PU T *P RO C ES S* C OD E (character string | GENERATE)
is an optional parameter used to provide a value that is to indicate the selected BASE datasets have been processed. Upon
successful completion of the RMS execution, each selected
BASE dataset is updated with the specified value. Of the two
possible values, character string is a user supplied value from 1
to 11 characters in length. A value of GENERATE indicates
the RMS software is to automatically assign a value. This
assigned value will be in the form of
DDDDDTTTTTT, where:
DDDDD is the Julian RMS execution date (YYDDD)
TTTTTT is the RMS execution time (HHMMSS)
Alternate Keyword(s): OPC
NOTE: OUTPUT*PROCESS*CODE is not valid for an RMS Recover Request from a Packet level
PA S SW O RD (character string)
is an optional parameter used to provide a password for the
user written security exit. This value is from one to eight characters in length and is user defined.
Alternate Keyword(s): PW
US E R* I D (character string)
is an optional parameter used to identify the user attempting
the RMS execution. It can be from one to eight characters in
length and is user defined.
Alternate Keyword(s): UID
Select
The format of the SE L EC T command is:
SELECT
126
© 2013 Mantissa Corporation. All rights reserved.
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
archive dataset.
RMS/Online® Version 11.35
Concepts
RM80001 Control Statements
Command Descriptions
System Reference Guide
SEL
Chapter 4: Repository Management
{NAME(name) | GNAME (name prefix)}
[CLASS (class)]
[CROSS*REFERENCE]
[DESTINATION (dest id)]
[EXIT*NAME (program name)]
[FORM (form id)]
[JOB*NAME (job name)]
[JOB*NUMBER (nnnnn)]
[PROCESS*CODE (comparison value, operation code | EQ)]
[QUEUE*DATASET*NUMBER]
[REPOSITORY*RELOAD]
[REPORT*ID (name)]
[REPORT*NUMBER (nnnnn)]
select Command Summary
Any number of BASE datasets may be selected for processing during a single execution. Selection by prefix and full
name may be intermixed to attain the desired results. Datasets are always retrieved in the same order as the SELECT
records. Retrieval by prefix causes the datasets to be retrieved in alphabetical sequence.
Select PARAMETERS
Required Parameters
NA M E (name)
is a required parameter used to specify the full dataset name of
from 1 to 8 characters. If there is more than one BASE dataset
with the specified name, the entry most recently created is
selected for processing.
GN A ME (name prefix)
is a required parameter used to select by name prefix. Selection
by prefix always implies selection of every BASE dataset
having this prefix.
OR
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
Optional Parameters
CL A SS (class)
is an optional parameter used to limit selection to those entries
with a matching class. Valid classes are A-Z, 0-9.
CO N CA T EN AT E
is an optional parameter used to request that the datasets, processed as the result of the current select record, be appended to
the dataset most recently processed. Use of concatenate with
the GNAME form of selection will cause all datasets processed
to be placed in one physical file.
Alternate Keyword(s): CONCAT
CR O SS * RE FE R EN CE
is an optional parameter used to request an index list of disk
resident or archive resident datasets.
DE S TI N AT IO N (dest id)
is an optional parameter used to limit selection to those entries
with a matching destination identifier. NJE users should use
the short format specification for NODE:REMOTE destinations (NnnnRnnn).
Alternate Keyword(s): DEST
© 2013 Mantissa Corporation. All rights reserved.
127
CHAPTER 4: REPOSITORY MANAGEMENT
BASE datasets are selected for processing using the qualifying information specified in the SELECT command. Two
types of selection are permitted, specific name or generic prefix. Both types permit certain positions in the name to be
ignored by placing an asterisk (*) in those positions of the name or name prefix.
Chapter 4: Repository Management
Concepts
RM80001 Control Statements
Command Descriptions
RMS/Online® Version 11.35
System Reference Guide
EX I T* N AM E (program name)
is an optional parameter used to specify the name of a user exit
that is to receive RM80001 output. Note that all standard
RM80001 output/segmentation facilities are negated by the use
of an exit.
FO R M (form id)
is an optional parameter used to limit selection to those entries
with a matching forms identifier.
JO B *N A ME (job name)
is an optional parameter used to limit selection to those entries
created in an OS/MVS JOB matching the supplied name.
JO B *N U MB ER (nnnnn)
is an optional parameter used to limit selection to those entries
created in the OS/MVS job matching the designated job number.
CHAPTER 4: REPOSITORY MANAGEMENT
PR O CE S S* CO D E (comparison value, operation code | EQ)
is an optional parameter used to restrict RMS execution to a
group of previously processed datasets. The string specified as
the comparison value operand can be from 1 to 11 positions. It
is compared to the process code value contained in each BASE
dataset entry selected during the RMS execution. A match condition is determined using the operation code operand. The
possible operation codes are:
128
PR O CE S S* CO D E (A**********, NE)
would cause the selection of all processed BASE dataset
entries other than those having an “A” in their first position.
Alternate Keyword(s): PCODE
QU E UE * DA TA S ET *N U MB E R (nnnnnn)
is an optional parameter used to limit selection to that entry
with a matching repository number. Preceding or trailing
blanks are not accepted.
Alternate Keyword(s): Q DN , RE PO R T* N UM BE R , R N
RE P OS I TO RY * RE LO A D
is an optional parameter used during dataset recovery
(R U N* M OD E R EC O VE R ) to indicate that processed entries
are to be returned directly to the repository.
RE P OR T *I D (name)
is an optional parameter that may be used when “RU N* M OD E
R EC OV E R” is specified and the input archive file is an
RM80004 packet archive. Otherwise it is ignored if coded.
When specified, this parameter will cause the first or only copy
of the named report within the segment to be selected. This is
the name assigned in the RM80004 ID E NF IT Y *R E PO RT
© 2013 Mantissa Corporation. All rights reserved.
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
EQ - equal to (default)
GE - greater than or equal to
GT - greater than
LE - less than or equal to
LT - less than
NE - not equal
The use of the masked comparison character “*” in any comparison value position causes that position to be ignored in the
comparison operation. This would allow the selection of
groups of process codes, i.e.,
RMS/Online® Version 11.35
Chapter 4: Repository Management
Concepts
RM80001 Control Statement Examples
Command Descriptions
System Reference Guide
command via the R EP OR T *I D parameter. If the segment
contains more than one copy of the named report and all are to
be selected, GNAME must be used to specify the segment
name.If all copies of all reports contained within an archived
segment are to be selected, this parameter should be omitted.
Alternate Keyword(s): RID
RE P OR T *N UM B ER (nnnnn)
is an optional parameter used to limit selection to that entry
with a matching repository dataset report number.
Alternate Keyword(s): RN
RM80001 CONTROL STATEMENT EXAMPLES
OS/MVS Command Examples
1.
Microfiche Source File Production
2.
Report Archive (Backup/Purge)
3.
Report Recovery (Reload)
File Create Examples
The file create capability of RM80001 can produce tapes in print image for off host microfiche creation. Optionally,
the retrieved report data may be passed to a user exit. JES print output is the default format.
The following examples illustrate various combinations of control records which are used to create the microfiche
files.
Specific Report Retrieval
The following control stream retrieves the report “DDAO3” and produces a print image source tape.
EXAMPLE:
OUTPUT*CONTROL DDNAME (PRTAPE)
SELECT NAME (DDAO3)
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
Specific Report Retrieval Qualified by Destination and Forms
The following control stream retrieves report “ARD03” for remote destination RMT4 having a forms identifier of
STD4.
EXAMPLE:
OUTPUT*CONTROL DDNAME (PRTAPE)
SELECT NAME (ARD03) DEST (RMT4) FORM (STD4)
© 2013 Mantissa Corporation. All rights reserved.
129
CHAPTER 4: REPOSITORY MANAGEMENT
This section contains control stream examples pertaining to the use of RM80001 for:
RMS/Online® Version 11.35
Chapter 4: Repository Management
Concepts
RM80001 Control Statement Examples
Command Descriptions
System Reference Guide
Specific Report Dataset Retrieval by Class and Form Identifier; User Exit Output
The following example illustrates selection of the report “SAV03” in class “X”. Output by RM80001 is suppressed
and the report data is passed to the user exit “USEREXIT”.
EXAMPLE:
SELECT
NAME (SAV03) CLASS (X) FORM (STD1) EXIT*NAME (USEREXIT)
Generic Report Retrieval. Qualified. Print Image Tape Output.
The following example shows how the generic report retrieval facility might be used to retrieve all reports with
names beginning with the characters “DSC” created by the
JOB DSC001 having a forms identifier of STD1.
EXAMPLE:
CHAPTER 4: REPOSITORY MANAGEMENT
OUTPUT*CONTROL DDNAME (PRTAPE)
SELECT GNAME (DSC) JOB*NAME (DSC001) FORM (STD1)
NOTE: The DDNAME OPERAND VALUE PRTAPE in the OUTPUT*CONTROL statement specifies the
user supplied DD statement that has been included in the execution stream.
“ALL” Generic Retrieval. Print Image Tape Output
The following special case of the generic retrieval mode will retrieve all the datasets in the repository and place these
entries on tape in print image format.
EXAMPLE:
OUTPUT*CONTROL DDNAME (PRTAPE)
SELECT GNAME (*)
Obtain an Alphabetical Cross Reference Listing of the Entries in the Repository
EXAMPLE:
SELECT GNAME (*) CROSS*REFERENCE
Report Archive Examples
The report ARCHIVE facility is one of the dataset management functions performed by the RM80001 product. This
facility provides for the off-loading of selected report entries to user defined magnetic media. The off-load data is
stored in compressed form, thereby reducing the amount of storage required for report backup.
In addition, once the selected reports have been archived, their spool space may be released and made available for
the storing of new reports. This “purge” operation is optional and may be requested at the time of archive execution.
130
© 2013 Mantissa Corporation. All rights reserved.
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
An alphabetical cross reference of all the datasets in the repository may be requested by specifying a generic name of
* and specifying the CR O SS *R E FE R EN CE parameter.
RMS/Online® Version 11.35
Chapter 4: Repository Management
Concepts
RM80001 Control Statement Examples
Command Descriptions
System Reference Guide
Generic Archive
In this example we will request the archive of all reports whose name begins with DSC. The entries will be copied to
the output media, however they are not removed from the repository.
EXAMPLE:
RUN*MODE ARCHIVE
SELECT GNAME (DSC)
This example provides for the selection of all report entries whose names end with DDA. In addition to being copied
to the archive media, the entries are deleted from the repository and the space made available for reuse.
RUN*MODE ARCHIVE PURGE
SELECT GNAME (*****DDA)
The following example illustrates how all the reports for a specific JES job name may be archived. The select
command requests that all reports created by JOB DSC0001 be copied to the backup media, however, they are not to
be purged.
EXAMPLE:
RUN*MODE ARCHIVE
SELECT GNAME (*) JOB*NAME (DSC0001)
Archive and Purge
Here we back up every report in the repository and make the space available for reuse.
EXAMPLE:
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
RUN*MODE ARCHIVE PURGE
SELECT GNAME (*)
© 2013 Mantissa Corporation. All rights reserved.
131
CHAPTER 4: REPOSITORY MANAGEMENT
EXAMPLE:
Chapter 4: Repository Management
Concepts
Report Recovery
Command Descriptions
RMS/Online® Version 11.35
System Reference Guide
Specific Archive
Archive output containing specific reports may also be created. In the following example three reports will be
archived, however, they are not removed from the repository.
EXAMPLE:
RUN*MODE ARCHIVE
SELECT NAME (DSCSTMTS) FORM (STMT)
SELECT NAME (DSC*****) JOB*NUMBER (100)
SELECT NAME (DSCTRIAL) JOB*NUMBER (105)
Once reports are on an archive file they may be retrieved for routing to JES for eventual reprint or for reloading
directly to the repository for reprocessing. This facility is provided by the RM80001 repository management function
RECOVER.
Reports selected for reprint will be assigned their original output attributes unless overridden via an
OU T PU T *C ON T RO L command.
If reports which use a special FCB image are selected for reprint, an OU TP U T* C ON TR O L command specifying
the FCB name must precede the dataset select record for that report. Entries selected for reload will be restored to the
repository with their original characteristics.
Specific Report Recovery with Reload to repository.
The following statements would be used to reload the report named “DSCSTMTS” to the repository.
EXAMPLE:
RUN*MODE RECOVER
SELECT GNAME (DSCSTMTS) REPOSITORY*RELOAD
The following sequence of commands would result in the entry “DSCTRIAL” being routed to JES for reprint. Since
a special FCB is required, an OU T PU T* C ON TR O L command specifying the FCB name is supplied. In addition,
we will request two (2) JES copies.
EXAMPLE:
RUN*MODE RECOVER
OUTPUT*CONTROL FORM (TRIL) COPIES (2) FCB (DT01)
SELECT NAME (DSCTRIAL)
132
© 2013 Mantissa Corporation. All rights reserved.
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 4: REPOSITORY MANAGEMENT
REPORT RECOVERY
RMS/Online® Version 11.35
Chapter 4: Repository Management
Concepts
Report Recovery
Command Descriptions
System Reference Guide
Multiple Report Recovery
In a single recovery execution, selection for both report reprint and reload may be requested. In this example
REPORT1will be selected for reprint to SYSOUT class E and routed to remote destination RMT3. During this same
execution REPORT2 will be selected for reload to the repository.
EXAMPLE:
RUN*MODE RECOVER
OUTPUT*CONTROL CLASS (E) DEST (RMT3)
SELECT NAME (REPORT1)
SELECT NAME (REPORT2) REPOSITORY*RELOAD
Additional Command Examples
1.
Microfiche Source Production
2.
Report Archive
3.
Report Recovery
Microfiche File Create Examples
The microfiche source file production capability of RM80001 can produce tapes in print image format. Optionally,
the retrieved report data could be passed to a user exit. Print image is the default output format.
The following examples illustrate various combinations of control records which might be used to create these
microfiche files.
The first command stream retrieves the report “DDA03” and produces a print image microfiche source tape.
EXAMPLE:
SELECT NAME (DDA03)
The following control stream retrieves report “AR003” having a class of “C”.
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
EXAMPLE:
SELECT NAME (ARD03) CLASS (C)
The following example illustrates selection of the report “SAV03” in class “X”. Output by RM80001 is suppressed
and the report data is passed to the user exit “USEREXIT”.
EXAMPLE:
SELECT NAME (SAV03)
CLASS (X)EXIT*NAME (USEREXIT)
© 2013 Mantissa Corporation. All rights reserved.
133
CHAPTER 4: REPOSITORY MANAGEMENT
This section contains control stream examples pertaining to the use of RM80001 for:
Chapter 4: Repository Management
Concepts
BASE Dataset Archive Examples
Command Descriptions
RMS/Online® Version 11.35
System Reference Guide
Generic Report Retrieval
The following example shows how the generic report retrieval facility might be used to retrieve all reports with
names beginning with the characters “DSC” that have a class of “A” .
EXAMPLE:
SELECT GNAME (DSC) CLASS (A)
Obtain an Alphabetical Cross Reference Listing of the Entries in the Repository
An alphabetical cross reference of all the datasets in the repository may be requested by specifying a generic name of
* and specifying the CR O SS *R E FE R EN CE parameter.
EXAMPLE:
SELECT GNAME (*) CROSS*REFERENCE
The report archive facility of RM80001 provides BASE dataset archive capabilities for the contents of the repository.
The archive files created using this archive facility feature provide for the recovery of individual datasets should the
need arise.
A directory list of the archived datasets is produced during the archive process. The list may also be created from the
archive file. See “Recreating an Archive Directory List” in the “Report Recovery” section.
The following examples illustrate how various combinations of dataset select records might be used to create report
backup. Note that in each example the dataset select records are preceded by the RU N *M OD E command ARCHIVE
parameter. This keyword causes RM80001 to operate in archive mode.
Generic Archive
The following sequence of statements will create two archive files. The first file will contain all datasets with names
beginning with the characters “FIS”. The last file will contain all datasets with names beginning with “DSC”.
EXAMPLE:
RUN*MODE ARCHIVE
SELECT GNAME (FIS)
SELECT GNAME (DSC)
“ALL” Archive
The following example illustrates how all BASE datasets in the repository would be archived.
EXAMPLE:
RUN*MODE ARCHIVE
SELECT GNAME (*)
134
© 2013 Mantissa Corporation. All rights reserved.
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 4: REPOSITORY MANAGEMENT
BASE DATASET ARCHIVE EXAMPLES
RMS/Online® Version 11.35
Chapter 4: Repository Management
Concepts
Report Recovery
Command Descriptions
System Reference Guide
Specific Report Archive
Archive files containing specific reports may also be created. In the following example, three reports will be
archived.
EXAMPLE:
RUN*MODE ARCHIVE
SELECT NAME (REPORT02) CLASS (A) DISP (D)
SELECT NAME (STATEMNT) CLASS (F) DISP (L)
SELECT NAME (TRIALBAL) CLASS (Z) DISP (H)
REPORT RECOVERY
During a recover operation, reports are returned to POWER under their original name (VSE) or under the name of the
recover job if MVS.
When reports are returned to the JES, the following attributes are automatically restored if an
OU T PU T *C ON T RO L command is not in effect for that entry:
•
CLASS
•
COPY COUNT
•
FORM IDENTIFICATION
•
REMOTE ID
If reports, which have special FCB requirements are to be returned to JES, an OU T PU T *C ON T RO L command
must precede the dataset select record for that report. In a VSE environment, failure to do this can result in
cancellation of RM80001 due to a channel program failure.
Specific Report Recovery
The following statements would be used to return the report names “STATEMNT” to JES.
EXAMPLE:
RUN*MODE RECOVER
SELECT NAME (STATEMNT)
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
Report Recovery Using List Attribute Record
The following sequence of statements shows the use of the list attribute record in recovering a report with a special
forms control buffer.
EXAMPLE:
RUN*MODE RECOVER
OUTPUT*CONTROL form(abcd) copies(2)fcb(fcb2105) SELECT NAME (MCSTAT)
© 2013 Mantissa Corporation. All rights reserved.
135
CHAPTER 4: REPOSITORY MANAGEMENT
Once reports are on an archive file they may be retrieved for reprint or the replacement of COM tapes by using the
RM80001 R UN * MO DE command. To use this capability, you need only precede the dataset select records for
reports to be recovered with a R UN *M O DE R E CO V ER COMMAND.
Chapter 4: Repository Management
Concepts
Report Recovery
Command Descriptions
RMS/Online® Version 11.35
System Reference Guide
Multiple Report Recovery
The following sequence of statements returns both reports to JES. Although the reports have no special FCB or the
OUTPUT*CONTROL record is used to change the class and form number.
EXAMPLE:
RUN*MODE RECOVER
OUTPUT*CONTROL CLASS(F) FORM(XXXX)
SELECT NAME (REPORT1)
SELECT NAME (REPORT2)
Recreating an Archive Directory List
If an archive directory list is misplaced, it may be re-created by specifying “*” in the GNAME parameter and coding
the C R OS S* R EF ER E NC E parameter of a S EL EC T command. All qualifiers apply, i.e., only class A entries will
be listed. The following example illustrates the control record requirements to produce such a list.
EXAMPLE:
Chap_04(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 4: REPOSITORY MANAGEMENT
RUN*MODE RECOVER
SELECT GNAME (*) CROSS*REFERENCE CLASS (A)
136
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Administrative Control Dataset Records
Panel Format
System Reference Guide
Chapter 5
SYSTEM ADMINISTRATION
Additional Administrative Transactions
All SYSOUT datasets placed in the RMS repository fileset are viewable at the time they are added if they have an
associated fileset.
After the installation of RMS/ONLINE, the index files contain a system control record that has information relating
to default system installation values and thresholds, a user master that contains the information, user ID and password
for the system administrator, and test set data for verifying the proper operation of the system. The user ID, password,
and access group for the system administrator are established as part of the installation procedure.
ADMINISTRATIVE CONTROL DATASET RECORDS
Records in the administrative control dataset (ACDS) form a report management database that supplies RMS/
ONLINE with information necessary to make report information available on-line. The following discussion should
give you a better understanding of the contents of the ACDS.
Access Group Master
All reports belong to access groups. The concept of an “access group” may be compared to that of being a member of
a club. Your membership “card” in this case is the default access group and profile data in your user record. Some
users have access to “club” facilities (transactions, reports) that others are not allowed to use.
Access group records must be created before any user records are created. Usually the access group masters are
created to control reports that comprise the printed output from a single application or for a functional area of your
operation.
User Master
User Master records keep track of individuals permitted to use RMS. Each potential user must have a user record. The
system or access group administrator may optionally enter profile data granting specific users the right to use certain
system resources. See “Resource Security” for more information. User ID’s must be unique.
Location Master
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
Retention Control
Retention Control records are used to designate in versions or days the retention requirements for reports. Retention
may be controlled at the entire access group level or the location/report level (keep report X 3 days for user Y).
ADMINISTRATIVE TRANSACTION CHARACTERISTICS
All administrative transactions share common characteristics with regard to panel formatting and system response.
Panel Format
Panel Heading
© 2013 Mantissa Corporation. All rights reserved.
Left to right, the descriptive panel name, date, day of week and
time of day are always displayed.
137
CHAPTER 5: SYSTEM ADMINISTRATION
A Location Master defines a unique distribution location within your organization.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Administrative Transaction Characteristics
PF Keys
System Reference Guide
Panel Body
Transaction related data.
Line 23
Active PF keys.
Line 24
Message data area. Single line messages will always appear in
this area. Multi-line messages will cause the message “MULTIPLE MESSAGES PENDING” to appear in the message line.
Depressing the Help PF key will cause the full text of all outstanding messages to be displayed.
PF Keys
PF key usage is consistent throughout the system. Regardless of the transaction, the following will result in the
designated system action.
PF1 - HELP
Displays the first Help panel for the Active panel. If any error
messages are pending, the first Help panel is always the text of
the diagnostic or information message(s). Once Help is activated, the user is guided to additional Help panels.
PF3 - END
Depressing the End key will cause the system to terminate the
function currently active and re-display the previous menu
panel. Any data keyed on the current panel is disregarded.
PF4 - EXIT
Depressing PF4 will cause you to exit the system.
PF7 - PAGE UP
PAGE UP for all administrative transactions will cause the system to scroll backward one panel at a time through panels comprising the transaction. Pressing PAGE UP on page one of a
multi-panel transaction causes the last panel to be displayed.
That is, it “wraps” from first to last panel.
PF8 - PAGE DOWN
PAGE DOWN for all administrative transactions will cause the
system to scroll forward one panel at a time through panels
comprising the transaction.
ENTER
Complete or initiate action. The Enter key is depressed whenever you have entered data on a menu or add/change/delete/
inquire and want to request that action be taken. For delete and
change transactions, depressing Enter after the data is displayed will cause the deletion or change to take place.
Some administrative transactions permit the use of a template record identifier to reduce data entry overhead. For
example, if you are constructing a Location Master record for location “auditing”, you could use the contents of an
existing Location record and change only the fields required.
Multi-panel Transactions
Multi-panel transactions all permit the use of page up and page down keys for reviewing the other panels. The paging
function permits you to scroll front to back or back to front without having to pass all the pages.
138
© 2013 Mantissa Corporation. All rights reserved.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
Template Use
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Administrative Transactions
Help Facilities
System Reference Guide
Help Facilities
System Help facilities are available to the system administrator. Anywhere in the system the Help key can be
depressed to receive the first Help panel for the panel being displayed. Once inside Help, on-screen prompts will
explain the available options and the values/PF keys that can be used to access additional Help text.
ADMINISTRATIVE TRANSACTIONS
Before getting into a detailed description of the individual transactions, it is worth the time to outline the application
flow for administrative transactions. If you use the menus, gaining access to the administrative facilities requires the
following steps:
Step 1.
Sign-on to RMS/ONLINE.
The Primary Menu is presented.
Step 2.
Select Option 2 on the Primary Menu.
The Administrative Menu is displayed.
Step 3.
Select the desired administrative transaction.
After the requested operation is performed, the administrator is prompted for entry of the next field. You may use the
End PF key in order to return to the Administrative Menu and the Return PF key to exit RMS/ONLINE.
Access Authorization
Each user accessing RMS must pass an access authorization test. If only the transaction code is entered, the
authorization panel is presented for the entry of a user ID and password. Optionally, the user may enter the user ID
and password with the transaction code and avoid presentation of this panel.
NOTE: You may bypass RMS internal security and use your installation security package. This is
accomplished by using the security exit facility available in RMS.
Primary Menu
Depending on installation options, the Primary Menu may be presented immediately after sign-on. As implied by the
name, this menu is the initial entry point for RMS. In the case of system administration, Option 2 is selected.
NOTE: A fast-path transaction facility permits you to go directly from the initial transaction line to the
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
Administrative Menu
After selecting Option 2 on the Primary Menu, the Administrative Menu is displayed.
Five types of transactions are available for the records maintained by the system administration component: add,
inquire, change, list and delete. The first character of various options indicate the type of transactions: A, I, C, L, D
for add, inquire, change, list, and delete transactions respectively.
Add Transactions
If you select one of the add transactions, ‘AL’ (Add Location) for instance, the Location Master Panel is presented
with a message asking for record information. When the data has been entered, pressing ENTER will complete the
transaction.
© 2013 Mantissa Corporation. All rights reserved.
139
CHAPTER 5: SYSTEM ADMINISTRATION
administrative panel of your choice.
Chapter 5: System Administration
Additional Administrative Transactions
Building A Management Database
Collecting the Required Information
RMS/Online® Version 11.35
System Reference Guide
Inquire Transactions
All inquire transactions present a panel with a message asking for a record identifier. After the identifier data is
entered, pressing Enter will present the information for the record in question. You may over-type the ID fields on the
screen for the next inquiry.
Change Transactions
Change transactions are identical to Inquiry transactions up to the point where the record data is displayed. The user
may then page back and forth (in the case of multi-panel transactions), make the desired changes and confirm these
changes by pressing ENTER.
Delete Transactions
Delete transactions are identical to Change transactions, except that pressing Enter causes the record to be deleted.
System Administration transactions changes, deletes, adds, and displays only responds to a depression of the Enter
key.
List Transactions
After many resources have been defined it is useful to list them for review. When reviewing a list of records the
individual records may be chosen for “C”hange, “I”nquiry, or “D”eletion.
BUILDING A MANAGEMENT DATABASE
Collecting the Required Information
CHAPTER 5: SYSTEM ADMINISTRATION
1.
How will reports be organized and named?
Answering this question is the key to the formation of access groups. An access group by its nature implies that
there is a collection of reports that have common security, archive and recovery characteristics. Application systems are the most likely place to start looking when considering the creation of access groups. Functional grouping is also possible. Each execution of RM80004 can distribute to one access group. Report names are the
identifiers assigned in the RM80004 distribution definitions. Report names should be unique to avoid confusion.
They may consist of from 1 to 8 alphanumeric characters. Subject to these limitations, the report names in the
REPORT*ID parameters of the existing RM80004 distribution definition may be used.
2.
Which RM80004 command streams will be affected?
At a minimum, RM80004 procedures that will create index information for eventual viewing must have a
QXCNTRL DD statement containing the dataset information and the name of the SUBSYSTEM that will manage the repository files. Also, distribution definitions must have RUN*OPTIONS commands added or be modified to specify the desired processing options. RM80004 cannot index report data for eventual display unless the
REPORT*ID parameter has been used in the IDENTIFY*REPORT commands. You must also decide whether
the names currently being assigned to the output packets are acceptable for location names. If not use the LOCATION*NAME parameter of the CREATE*PACKET command to generate the packet name.
3.
Who will use the system?
User ID’s and passwords may need to be assigned. Contact information like address and phone number would
also be useful.
4.
How will distribution locations be named?
If the packet names in the current RM80004 distribution definitions are not acceptable for long-term use, you
need to decide on naming conventions for the locations.
These are only the major questions.
140
© 2013 Mantissa Corporation. All rights reserved.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
In order to build the report management database, you have to answer the following questions:
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Building A Management Database
Creating System Control Records
System Reference Guide
Creating System Control Records
Once you’ve collected the required information, add the records to the RMS/ONLINE database in the following
order:
1.
User Master Records - who will be using the system?
2.
Location Masters - where will reports be distributed?
3.
Access Group Master - how will reports be group?
4.
Retention Control Records - how long will reports be retained?
Access Authorization Panel
R.M.S. - Access Authorization
Mantissa (C)opyright MCMXCII
Required:
User ID
Password
==>
==>
Optional:
New Password
Verify Password
==>
==>
Program Function
Use
Caution
When
Changing
PF1=Help
PF3=End
Date: Tuesday,
10/08/96 Time: 17:03:23
SubSys: R134 Tran:
TermID: 0028 ___
(( New and Verify Passwords ))
((
** Must Match **
))
Keys:
PF01 ==>
PF04 ==>
PF07 ==>
PF10 ==>
PF02
PF05
PF08
PF11
==>
==>
==>
==>
PF03
PF06
PF09
PF12
==>
==>
==>
==>
PF4=Return
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
The user’s first interaction with RMS/ONLINE for each session is through the Access Authorization panel. The
Access Authorization panel may be bypassed completely by entering the user ID and password (if any) after the
transaction code.(CICS ONLY)
A transaction code necessary to invoke RMS/ONLINE is assigned by your installation. The Access Authorization
panel appears after entering this transaction identifier. Information entered on the panel is used to establish the default
Access group and identity of the user. If security is used, the Password field is compared to the Password field in the
User Master record or to the password in the installation security system for access verification.
NEW and VERIFY passwords may be entered by the user to establish a new password.
© 2013 Mantissa Corporation. All rights reserved.
141
CHAPTER 5: SYSTEM ADMINISTRATION
Figure 1. Access Authorization Panel
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
System Administrative Panels
Creating System Control Records
System Reference Guide
Primary Menu Panel
R.M.S. - Primary Menu
Access Group - IVSYSTEM
Date: Monday,
10/07/96 Time: 09:47:23
SubSys: R134 Tran:
TermID: 002B ___
Option ==>
1.
2.
3.
4.
5.
6.
T.
Display/Print
Administration
Distribution(Implicit)
Sysout/Report
Security
Help Management
Tutorial
PF1=Help
PF3=End
-
Display/Print a Report in the RMS Database
Administration and Resource Control
Distribution Definition and Management
Sysout/Report Profile Management
Security Definition and Management
Help Management and Maintenance
Tutorial on System Capabilities/Facilities
PF4=Return
Figure 2. Primary Menu Panel.
The Primary Menu is presented immediately after the Access Authorization panel. All major system functions are
accessible from this panel. The available options are:
1.
2.
3.
4.
5.
6.
T
- Display/Print
- Administration
- Distribution
- Sysout/Report
- Security
- Help Management
- Tutorial
CHAPTER 5: SYSTEM ADMINISTRATION
SYSTEM ADMINISTRATIVE PANELS
All of the system administration functions are supported through a series of ONLINE addition and modification
panels. This section depicts the various panels and discusses their use in defining access groups, users, distribution
locations and retention control requirements to RMS/ONLINE.
The available panels are:
142
Access Group-
Add/Change/Delete/Inquire/List
User-
Add/Change/Delete/Inquire/List
Location-
Add/Change/Delete/Inquire/List
© 2013 Mantissa Corporation. All rights reserved.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
Enter 2 in the option==> field and press <ENTER> to select the System Administration Menu.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
System Administrative Panels
Creating System Control Records
System Reference Guide
Retention -
Add/Change/Delete/Inquire/List
Output Definition -
Add/Change/Delete/Inquire/List
Customization -
Add/Change/Delete/Inquire/List
Extended Info -
Inquire
Field Level Security-
Add/List
After the sign-on data is entered, RMS/ONLINE presents a Primary Menu panel. Option 2 (System Administration),
when selected, presents the Administrative Menu panel. The Administrative Menu panel permits selection of the
various addition, change, deletion and inquiry facilities. The following session example illustrates the various steps
and the type of interaction necessary to perform an administrative task.
EXAMPLE:
Session 1.
Objective: Define a user to RMS/Online.
1. Sign-on to RMS/ONLINE.
2. The Primary Menu panel appears.(Figure 2)
3. Select System Administration. (Option 2)
4. The Administrative Menu panel appears.(Figure 4)
5. Enter “AU” for Add User function.
6. The User Master (Addition) panel appears.(Figure 5)
7. Enter the required information and press <ENTER>.
8. The next User Master (Addition) panel appears.(Figure 5)
Press PF3/PF15 to return to the Administrative Menu panel or enter data for the next user.
Each of the administrative functions may be invoked from the Administrative Menu panel. During addition
operations, the system will present another “ADD” panel upon successful completion of the last addition. Pressing
PF3 will cause the system to return to the Administrative Menu panel. When PF3 is pressed twice in succession, the
Primary Menu panel is displayed. PF4 will exit RMS/ONLINE.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
Examples of the various administrative panels and a description of the panels may be found on the following pages.
© 2013 Mantissa Corporation. All rights reserved.
143
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
System Administrative Panels
Creating System Control Records
System Reference Guide
Administrative Menu Panel
R.M.S. - Administration
Access Group: IVSYSTEM
Date: Monday,
10/07/96 Time: 09:54:32
SubSys: R134 Tran:
TermID: 002B ___
Option ==>
Access ==> IVSYSTEM
Access Group:
User:
Location:
Retention:
Output Definition:
Customization:
Extended Info:
Field Security:
PF1=Help
PF3=End
____________
Options
Add
Change
Delete
AA
CA
DA
AU
CU
DU
AL
CL
DL
AR
CR
DR
AO
CO
DO
AC
CC
DC
_____________
Inquire List
IA
LA
IU
LU
IL
LL
IR
LR
IO
LO
IC
LC
EI
FS
---
---
---
---
PF4=Return
Figure 4. Administrative Menu Panel
The Administrative Menu panel is presented immediately after Option 2 (System Administration) is selected on the
Primary Menu panel. All administrative addition, change, deletion, list, and inquiry functions are available from this
panel. The first letter of the administrative transaction code is always A, C, D, I or L for Add, Change, Delete, Inquiry
and List respectively; the next characters define the record type that is the object of the transaction. For example, the
Add User transaction code is AU.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
144
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
System Administrative Panels
Creating System Control Records
System Reference Guide
Access Group Master Panel
R.M.S. - Access Group Master
Mode: ADD
Date: Tuesday,
10/08/96 Time: 17:08:31
---------------------------------------*** Access Group ***
Access Group Identifier
==> IVSYSTEM
Secured/Unsecured (S/U)
==> S
Description > INVENTORY REPORTS
> RUN FOR CENTRAL ACCOUNTING DEPARTMENT
> CONTAINS DAILY, WEEKLY, AND MONTHLY REPORTS
*** Administrator ***
Administrator ID
Administrator Name
==> US001
Phone Number ==> 205-945-8930
==> JOHN DOE
PF1=Help PF3=End PF4=Ret ENTER=Update/Inq
RM9134I Enter information for new record.
Figure 5. Access Group Master Panel
The Access Group Master panel is used to add, modify, and inquire on Access group data. Access groups are
established as the basis for accessibility and security of reports. The hierarchy for the control of the report data is as
follows: ACCESS GROUP, SECURITY GROUPS, and REPORTS.
Access Group Identifier
This field must be from 1 to 8 alphanumeric characters. It identifies the name of the Access Group and is a required field.
Secured/Unsecured
This field is used to indicate if the RMS/ONLINE security will
be used to control access to these reports. If “U” is entered
here, any user may view any report in this Access group.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
NOTE: All other fields are documentation only.
© 2013 Mantissa Corporation. All rights reserved.
145
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
System Administrative Panels
Creating System Control Records
System Reference Guide
User Master Panel
R.M.S. - User Master
Mode: ADD
User ID
Def. Access GP
Def. Location
User Name
Phone Number
Address Line 1
Line 2
Line 3
Line 4
DS Print Job
ACC-GRP
MANTISSA
==>
==>
==>
==>
==>
==>
==>
==>
==>
==>
SECUR-GP
US001
Date: Tuesday,
10/08/96 Time: 17:10:22
---------------------------------------US001
Template User ==>
MANTISSA
User Password ==>
CHICAGO
JOHN DOE
205-945-8930
MANTISSA CORPORATION
201 SUMMIT PARKWAY
BIRMINGHAM, AL 35209
ABC123
User Type
Sel Print Job ==>
***** Security Profile *****
RT S ACC GRP
SECUR-GP RT S ACC-GRP
DP A MANTISSA US001
LR A IVSYSTEM
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
RM9134I Enter information for new record.
SECUR-GP
US001
ENTER=Update/I
==> S
RT S
LR A
Panel 1 of 2
Figure 6. User Master Panel (1 of 2)
The User Master panel is used to add, modify and inquire on the user data. When initially added to the system, a user
is assigned a user ID and security characteristics. The user identification must be unique within the RMS/ONLINE
system. If RMS/ONLINE security facilities are to be used, a password must be entered. Contact data such as name,
phone and address may also be stored for each user. The Security profiles specify the Access Group/Security Group/
Resource Type/Security Type combinations that are valid for this user.
NOTE: Profiles are interpreted in the order they appear on the panel.
146
USER ID (Required)
An eight position field to assign to user ID which is used when
signing on to RMS/ONLINE.
TEMPLATE USER (Optional)
An eight Character field to Identify the User Master record to
use as a template. The User Master specified here must already
be on file.
© 2013 Mantissa Corporation. All rights reserved.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
RMS/Online has a method of maintaining common sets of Security Profiles. These are called Path Profiles. In this
case, the User Record contains a pointer to a record containing these common profiles. Any number of users may
point to this record. To specify a Path Profile, insert the user ID of this profile record in the Access Group field of the
“Security Profile” and an “*” in position one of the Security Group field. The Path Profile is a special type of user
record and is referred to as a “PROFILE” user. When creating this record, placing a “P” in the user type field
designates this record as a profile record. This prevents anyone from inadvertently signing on under a profile User ID.
(Up to five levels of a Path may be specified, i.e., a profile record may Path to another profile record which points to
another, which points to another.)
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Security Profile
Creating System Control Records
System Reference Guide
DEF ACCESS GP (Required)
An eight position field to identify the most commonly used
report access group for this user. This default access group will
appear on the Display/Print menu.
USER PASSWORD (Required)
An eight position field to assign the user password.
USER TYPE (Optional)
TYPE USER
STANDARD
SYSTEM ADMINISTRATOR
PROFILE
ACCESS GROUP
ADMINISTRATOR
DEF LOCATION (Required)
FIELD COMMENT
(blank)
S
P
A
DESCRIPTION
STANDARD USER
SYSTEM ADMIN
SECURITY PROFILE ONLY
ACCESS GROUP
ADMINISTRATOR
A sixteen position field to identify the most commonly used
location value for this user. This value will automatically
appear on the panel when the Display/Print menu is presented.
DS PRINT JOB (Optional)
This field represents a 20 character suffix that RMS/ONLINE
uses to append to the qualifier “PRT.XXX” in order to determine the name of the JCL member in Help Management that
will be used to print reports from an archive file. “XXX” is
selectable during product installation but is usually left at the
default value of ‘JOB.’. In this example, DPRINT is the suffix
of the job which is submitted when a print request is issued by
the user for printing from an archive. The JCL for this print job
is maintained on the Help Management System as member
PRT.JOB.DPRINT.
SEL PRINT JOB (Optional)
A twenty position field required if the user will be doing selective print from the RMS/ONLINE files. The JCL for this print
job is maintained on the Help Management System as member
PRT.JOB.SPRINT.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
NOTE: JCL must be defined in Help Management with the name that is generated for the DS print job
and SEL print job parameters.
SECURITY PROFILE
The security profile describes the resources (transactions and reports) available to this user. This area of the panel is
a table of resources this user may access.
For a practical example of how to use the following fields, refer to Systems Administration case study in this manual.
© 2013 Mantissa Corporation. All rights reserved.
147
CHAPTER 5: SYSTEM ADMINISTRATION
USER NAME, PHONE NUMBER, ADDRESS LINE 1-4 (Optional)
These fields should be used to record contact information
about this user.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Security Profile
Creating System Control Records
System Reference Guide
ACC-GRP (Required)
An eight position field used to assign the first resource level to
this user. The first security resource should always be ‘transactions’ and the first access group should always be the same as
the default access group.
SECUR-GP (Required)
An eight position field used to assign the security group to
which this user belongs. A Security Group is a group of users
with similar security requirements. This helps to reduce entry
of different security requirements multiple times.
RT (Required)
A two position field used to identify the resource type to be
used. Valid resource types are:
DD - DISTRIBUTION DEFINITION
DA - DISTRIBUTION ACCESS
DM - DATASET MANAGEMENT
DP - DISPLAY/PRINT (see Note)
HM- HELP MANAGEMENT
LR - LOCATION REPORT
RS - RESOURCE SECURITY
NOTE: DISPLAY PRINT
The first DP (Display Print) Access Group required within the security profile dictates the
Display/Print functions for all other Access Groups present on the Security Profile screens for
this user. (Only one DP resource type profile is necessary).
Available Resource Type codes for these categories may be found in the Appendix-D in this
manual.
S (Required)
A one position field to indicate the level of transaction accessibility the user has to the resource type. Available options are:
A- ALL (Will have access to all in this group)
P- PARTIAL (Will be limited, security is partial)
Security panels. (Item #5 on the Primary Menu). If “A” is entered, the user will have access to all
available transactions (if RT defines a transaction resource) or all available reports in this
Access Group (if RT defines a Location/Report resource “LR”).
148
© 2013 Mantissa Corporation. All rights reserved.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
NOTE: If a “P” is entered here it will be necessary to define the security requirements via the Resource
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Job Statement Information
Creating System Control Records
System Reference Guide
User Master Panel (continued)
R.M.S. - User Master
Mode: ADD
Date: Tuesday,
10/08/96 Time: 17:12:20
----------------------------------------
Job Statement Information: Selective Print
==> //PRINT JOB (01,MT,853,T),'MANTISSA/BHAM',MSGCLASS=X,CLASS=A,
==> //
USER=TJRM,NOTIFY=TJRM
==>
==>
Job Statement Information: Dataset Print
==> //PRINT JOB (01,MT,853,T),'MANTISSA/BHAM',MSGCLASS=X,CLASS=A,
==> //
USER=TJRM,NOTIFY=TJRM
==>
==>
Job Statement Information: Cancel Report
==> //CANCEL JOB (01,MT,853,T),'MANTISSA/BHAM',MSGCLASS=X,CLASS=A,
==> //
USER=TJRM,NOTIFY=TJRM
==>
==>
PF1=Help
PF3=End
PF4=Ret
PF7=Bwd
PF8=Fwd
ENTER=Update/I
Panel 2 of 2
Figure 7. User Master Panel (2 of 2)
Selective Print
** Reserved** Beginning with release 11.31 all selective
print requests are serviced by the Output processing subtask in the RMS Controller region. Four available lines to
enter Job Card information to be used when a selective print
request is submitted. The default print job to be submitted is
member name ‘PRT.JOB.SPRINT’ defined by the Help Management system (Item 6 on main menu).
Dataset Print
Four available lines to enter job card information to be used
when a dataset print request is submitted. The default print job
to be submitted is member name ‘PRT.JOB.DPRINT’ defined
by the Help Management system (Item 6 on main menu and
specified on the first User Master panel).
Cancel Report
Four available lines to enter Job Card information to be used
when a cancel report request is submitted. The default cancel
job to be submitted is member name ‘CAN.JOB.STREAM’
defined by the Help Management system (Item 6 on main
menu and specified on the first User Master panel).
NOTE: The values entered here will be placed where the respective variables occur in the DPRINT and
CAN JCL member.
© 2013 Mantissa Corporation. All rights reserved.
149
CHAPTER 5: SYSTEM ADMINISTRATION
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
JOB STATEMENT INFORMATION
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Job Statement Information
Creating System Control Records
System Reference Guide
Location Master Panel
R.M.S. - Location Master
Mode: ADD
Date: Tuesday,
10/08/96 Time: 17:15:26
----------------------------------------
Location Name
==> CHICAGO
AD. Access Group ==> MANTISSA
***
Location Name
Phone Number
Address Line 1
Line 2
Line 3
Line 4
Line 5
Line 6
Line 7
==>
==>
==>
==>
==>
==>
==>
==>
==>
Template Location ==>
Name/Phone/Address
***
NEW DIRECTIONS CORPORATION
205-945-8930
201 SUMMIT PARKWAY
BIRMINGHAM, AL 35209
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
RM9134I Enter information for new record.
ENTER=Update/I
Panel 1 of 2
Figure 8. Location Master Panel (1 of 2)
The Location Master panel is used to add, change, and inquire on a Location. Each Location Master represents a
report distribution endpoint or recipient in your organization. The Location Master record includes name and address,
message and default print characteristics information.
CHAPTER 5: SYSTEM ADMINISTRATION
LOCATION NAME (Required)
A sixteen position field to indicate the name of this location.
This name corresponds to the LOCATION Name field on the
Custom Packaging Panel.
TEMPLATE LOCATION (Optional)
This field can be used to copy information from a template
location record. In order to use the template capability, type the
new location to be added in the LOCATION NAME field and
the pattern location name in the TEMPLATE field and press
ENTER. Information from the template record is then copied.
You may change the fields that vary from the template location
record and press ENTER to confirm the addition of the new
record.
AD ACCESS GROUP (Required)
An eight position field to identify the administrative access
group for this location. This will be used to determine the
administrative access group for this particular location.
LOCATION NAME, PHONE NUMBER, ADDRESS LINE 1-7 (Optional)
150
© 2013 Mantissa Corporation. All rights reserved.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
The LOCATION*NAME parameter specified in the RM80004 CREATE*PACKET command is used to specify a
value that corresponds to a Location Master Name.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Job Statement Information
Creating System Control Records
System Reference Guide
These fields are for documentation only. Use these fields to
document instructions as to how reports should be sent to this
location.
Location Master Panel (continued)
R.M.S. - Location Master
Mode: ADD
Date: Monday,
08/26/98 Time: 10:57:49
----------------------------------------
____________________________ Output Attributes _______________________________
Class
==>
Burst ==>
OLmt ==>
Form
==>
Fls/CC ==>
:
UCS ==>
:
FCB:A/V
==>
:
OPTCD ==>
PWD ==>
Dest
==>
Node
==>
Seps ==>
Desk/EWN ==>
Modify ==>
:
Xpro ==>
PageDEF
==>
Char1 ==>
Disp ==>
FormDef
==>
Char2 ==>
Blk ==>
LRECL
==>
Char3 ==>
Pri ==>
Copies
==>
Char4 ==>
DDNM ==>
Name
==>
Title
==>
Dept/XPRO ==>
Building ==>
Room
==>
Addr 1
==>
Addr 2
==>
Addr 3
==>
Addr 4
==>
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd ENTER=Update/I
Panel 2 of 2
Figure 9. Location Master Panel (2 of 2)
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
This panel is used to specify the default print characteristics for a location. The Print Request panel in RMS Online
permits retrieval of these default attributes. The Location Master Panel has been expanded to allow for extended JCL
Keyword support. The XPRO, and Dept/XPRO fields are utilized by our XPROCESS logic if you have this added
feature.
© 2013 Mantissa Corporation. All rights reserved.
151
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Job Statement Information
Creating System Control Records
System Reference Guide
Retention Control Panel
R.M.S. - Retention Control
Mode: ADD
Date: Thursday, 01/25/01 Time: 08:02:54
________________________________________
Access Group
Media Name
Location
Report/Model
* Enter ’RMODEL’ for retention model *
* Model name for retention models
*
==>
==>
==>
==>
Data Retention Versions ==>
Data Retention Days
==>
Tracking Retention Versions ==>
Tracking Retention Days
==>
Archive Grp Identifier ==>
Archive Grp Max Block
==>
Archive Grp Max Segment ==>
___________________________ Allocation Attributes ____________________________
==>
==>
==>
==>
==>
==>
PF1=Help PF3=End PF4=Ret ENTER=Update/Inq
RM9134I Enter information for new record.
Figure 10. Retention Control Panel
The Retention Control panel is used to create records which govern how long report data will be retained for viewing
and how long the report tracking information will be kept. Retention is promotable. If only the access group identifier
is entered on this panel, then the retention control record created would control retention for all reports in that access
group which do not already have retention control records associated. Specification of Access Group and Media has a
similar effect except that the retention characteristics apply only to reports having a matching media type not already
associated with more specific Retention Control records. Each additional level (location/report) permits you to place
more specific controls on retention of viewing and tracking information.
NOTE: Use a top-down approach. Leave no blank fields where a lower field is assigned a value. The
CHAPTER 5: SYSTEM ADMINISTRATION
Retention versions and days may not be intermixed. That is, you may not designate 3 versions for viewing and 20
days tracking. When used, the media name must correspond to the media names outlined in RM80004 - The Report
Distribution Management System, System Reference Manual. (see IDENTIFY*REPORT command.)
152
ACCESS GROUP (Required)
An eight position field in which the first level specific retention
control may be placed. If only the Access Group is entered
then all media types, all reports, at all locations will be
assigned this retention record.
MEDIA NAME (Optional)
A ten position field in which the second level specific retention
control may be placed. If Access Group and Media Category
are entered, all reports in that Access Group with that media
type would be assigned the entered retention record.
© 2013 Mantissa Corporation. All rights reserved.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
only exception to this rule is the LOCATION field. If left blank the record will apply to all
locations.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Job Statement Information
Creating System Control Records
System Reference Guide
LOCATION (Optional)
A sixteen position field in which the third level specific retention control may be placed. If Access Group, Media Category,
and Location are entered then all reports with these characteristics would be assigned the designated retention values.
NOTE: If this field is left blank, any reports that are entered will apply across all locations.
REPORT (Optional)
An eight position field in which the fourth level specific retention control may be placed. The report level allows you to state
retention controls all the way down to the report level.
DATA RETENTION VERSIONS
TRACKING RETENTION VERSIONS
Each field is four positions allowing data to be retained on the
viewing database file for the number of versions entered (maximum 9999).
DATA RETENTION DAYS
TRACKING RETENTION DAYS
Each field is four positions allowing data to be retained on the
viewing database file for the number of days entered (maximum 9999).
Output Definition Panel
R.M.S. - Output Profile
Mode: ADD
Profile ID
==>
DefAgeLimit
==>
N O T E S:
==>
=>
=>
=>
=>
Date: Thursday, 08/26/98 Time: 12:11:50
________________________________________
PF1=Help
PF3=End
PF4=Ret
PF7=Bwd
PF8=Fwd
ENTER=Update/Inq
CHAPTER 5: SYSTEM ADMINISTRATION
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
_______ Packet Content _______
AccessGp Location________ ReportID Seq_ Grp_ Flags OAL Note___________________
Panel 1 of 5
Figure 11. Output Definition Menu Panel
The Output Definition panel is used to create Output Profiles for use by Display Print users to compose a unique
packet of available reports from their viewing session. These packets can be printed, or sent to other media.
© 2013 Mantissa Corporation. All rights reserved.
153
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Job Statement Information
Creating System Control Records
System Reference Guide
Following is a description of the fields on the output definition panel.
PROFILE ID (Required)
This is the name of the Output Profile definition. Any 1-8 contiguous character name is allowed. Blanks and special characters are not allowed.
DEFAGELIMIT (Optional)
This field is used to control the default number of days to use
when considering whether to include the reports specified in
the Packet Content of the record in the requested 'OV' (output
verification) or 'OR' (output request).
If more than one output profile record is linked together, the
DEFAGELIMIT on the first record will govern the entire
record.
NOTES (Optional)
This field is for User documentation purposes.
The Packet Content portion of the panel is used to list the reports to include in the packet that is created. The reports
specified in this area can come from any INDEX of reports the Display Print user has access to. The fields are
described as follows:
ACCESS GROUP (Required)
The access group of the report.
LOCATION (Required)
The location of the report.
REPORTID (Required)
The report id from the INDEX panel.
SEQUENCE (Optional)
Used to ‘I’nsert, or ‘D’elete lines from the packet content portion of the panel.
GROUP
This field is not currently used.
FLAGS
This field is used to override the values in the DEFAGELIMIT,
and OAL fields. Acceptable values in the FLAGS field are as
follows:
+
which means regardless of how old the report is, include it in
the request
CHAPTER 5: SYSTEM ADMINISTRATION
-
which means to exclude the report
OAL
This field is used to determine the number of days to use when
considering whether to include the report in the requested 'OV'
(output verification, or 'OR' (output request).
NOTE
This field is not currently used.
Panels 1, 2 and 3 of the Output Definition panel are used to specify packet content information.
154
© 2013 Mantissa Corporation. All rights reserved.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
and
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Job Statement Information
Creating System Control Records
System Reference Guide
R.M.S. - Output Profile
MODE: ADD
DATE: Wednesday, 08/26/98 TIME: 12:00:53
________________________________________
____________________________ Output Attributes _______________________________
Class
==>
Burst ==>
OLmt ==>
Form
==>
Fls/CC ==>
:
UCS ==>
:
FCB:A/V
==>
:
OPTCD ==>
PWD ==>
Dest
==>
Node
==>
Seps ==>
Desk/EWN ==>
Modify ==>
:
Xpro ==>
PageDEF
==>
Char1 ==>
Disp ==>
FormDef
==>
Char2 ==>
BLK ==>
LRECL
==>
Char3 ==>
Pri ==>
Copies
==>
Char4 ==>
DDNM ==>
Name
==>
Title
==>
Dept/XPRO ==>
Building ==>
Room
==>
Addr 1
==>
Addr 2
==>
Addr 3
==>
Addr 4
==>
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd ENTER=Update/I
Panel 4 of 5
Figure 12. Output Definition Menu Panel 4
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
Output Definition panel #4 is used to assign output attributes to the packet of reports being created. If you are linking
several output definitions together (see Linking Output Definition Panels) the output attributes from the FIRST
Output definition will govern the destination of the packet.
© 2013 Mantissa Corporation. All rights reserved.
155
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Job Statement Information
Creating System Control Records
System Reference Guide
R.M.S. - Output Profile
MODE: ADD
DATE: Wednesday, 10/09/96 TIME: 17:25:03
________________________________________
________________________ Banner Page Information _____________________________
BLK Letter ==>
JCL Member ==>
Addr Line 1 =>
Addr Line 2 =>
Addr Line 3 =>
Addr Line 4 =>
Addr Line 5 =>
PF1=Help PF3=End PF4=RET PF7=BWD PF8=FWD ENTER=UPDATE
PANEL 5 OF 5
Panel 5 of 5
Figure 13. Output Definition Menu Panel 5
Output Definition panel #5 contains BLK Letter, and name and address information. The JCL Member field that
appears on panel #5 is not currently used in an output definition. The BLK Letter field is used to provide the name of
the packet which will appear on the banner (separator) page(s). Name and Address information appears in the bottom
left hand corner of the banner page.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
156
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Job Statement Information
Creating System Control Records
System Reference Guide
System Customization Panel
R.M.S. - Customization
Mode: ADD
Date: Tuesday,
10/08/96 Time: 17:31:06
----------------------------------------
System Customization Values
Base Trans-ID
Admin User ID
Password Days
Abend Prefix
Min Resp Time
Find Limit
==>
==>
==>
==>
==>
==>
RM00
SYSUI
90
30
00
10000
Template-Tran ==>
JCL Var Char ==>
Password Times =>
Message Prefix =>
Help Language ==>
UC Translate ===>
$
3
RM
ENG
Y
PF1=Help PF3=End PF4=Ret ENTER=Update/Inq
RM9134I Enter information for new record.
Panel 1 of 1
Figure 13. System Customization Panel
The Customization Panel allows for customization of the transaction specified in the panel. One RmVvrm program
may be installed to handle any number of transactions each having its own files and customization parameters. This
panel is only necessary when these items need changes. Defaults are assigned at installation time.
NOTE: 1.) These custom changes will only take affect after CICS has been cycled. In the TSO
environment it will be necessary to log off and log on again.
BASE TRANS-ID
This is the transaction ID for which the following parameters
are to apply. This ID must have been defined in the RMSOLGEN macro call added to the UTT0011 load module when the
system is installed (See Task 2.0 in the System Installation/Verification).
TEMPLATE TRAN
This is the name of another Customization Record to be used
as a model when building this record. Change the fields that
are different before pressing <ENTER> to add the panel. This
is identical to template management used in other administrative transactions.
ADMIN USER ID
The user ID of the System Administrator for these files.
© 2013 Mantissa Corporation. All rights reserved.
157
CHAPTER 5: SYSTEM ADMINISTRATION
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
2.) When assigning values to these fields, complete the entire panel except for the “template
tran”. DO NOT LEAVE BLANK FIELDS!
Chapter 5: System Administration
Additional Administrative Transactions
Output Definition
Creating System Control Records
RMS/Online® Version 11.35
System Reference Guide
JCL VAR CHAR
This is the character which will be recognized as the beginning
of a variable to be replaced when a print request is serviced.
Any field beginning with this character should be a variable
name listed in Appendix K.
PASSWORD DAYS
The number of days a password will be valid before requiring
the user to enter a new password.
PASSWORD TIMES
The number of times a user may try entering a password before
that user will be denied access.
ABEND PREFIX
The two character prefix assigned to any RMS generated
ABEND. If this code were set to RM then a 45 ABEND would
appear as an RM45 ABEND. RM is the default should this be
left blank.
MESSAGE PREFIX
The two character prefix assigned to any RMS generated message.
MIN RESP TIME
This field may usually be used to specify in seconds, the fastest
response permitted by the system.
HELP LANGUAGE
This will be the three character code used to select the help system panels when PF1 is entered. ENG should be used here
unless your help member contains other language support.
FIND LIMIT
This field will be the default number of lines searched when a
find transaction is entered. Maximum value is 999,999,999.
UC TRANSLATE
This field will control the upper case translation of all entered
data. Values are Y or N.
OUTPUT DEFINITION
Imagine never having to change a program again to support the use of new output technology. Output Definition
provides RMS/Online users the capability to produce customized output without the need for JCL or programming
changes.
Output Definition provides standard SYSOUT attribute support. Dynamic allocation of any operating system
sequential dataset is supported. AFP objects and DJDE definitions can be stored for inclusion in Output Definition
requests. Printer independence is maintained by using Output Definitions allowing you to change AFP objects, or
DJDE records without the need for program modifications.
Complete control of the approval, staging, and printing process is in the hands of the user. An Output Verification
report is available that allows users to approve the Output Request content prior to actual staging. Once approved, the
Output Request is issued, and the packet is staged for processing by the Output Processing Subtask, a component of
the RMS Control Region.
158
© 2013 Mantissa Corporation. All rights reserved.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
Output Definition allows users to define the order and content of an output packet they can request at any time. These
definitions are stored in OD profiles. Once defined, the Output Definitions are invoked ‘on demand’ by users from
the Index panel in the Display Print Facility. In order to be eligible for inclusion in an ‘OR’ (output request), the
reports must be viewable.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Adding An Output Definition Record
Output Definition Highlights
System Reference Guide
Output Definition Highlights
•
Supports new Output Technology
•
AFP via OUTDEF
•
DJDE definition support
•
On Demand Requests
•
Customized output / No JCL changes
•
Any operating system Sequential Dataset supported
•
Ability to define order & content of output
•
On-line Verification report availability
•
Standard SYSOUT attribute support
•
Maintains printer independence / No programming changes
ADDING AN OUTPUT DEFINITION RECORD
Following is an example of adding an Output Definition record (‘AO’).
R.M.S. - Output Profile
Mode: ADD
Profile ID
==>
DefAgeLimit
==>
N O T E S:
==>
=>
=>
=>
=>
Date: Thursday, 08/26/98 Time: 12:11:50
________________________________________
_______ Packet Content _______
AccessGp Location________ ReportID Seq_ Grp_ Flags OAL Note___________________
PF4=Ret
PF7=Bwd
PF8=Fwd
ENTER=Update/Inq
Panel 1 of 5
CHAPTER 5: SYSTEM ADMINISTRATION
PF3=End
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
PF1=Help
Output Definition Panel 1 of 5
© 2013 Mantissa Corporation. All rights reserved.
159
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Adding An Output Definition Record
Output Definition Highlights
System Reference Guide
Panels 2 and 3 allow additional Packet content.
R.M.S. - Output Profile
MODE: ADD
DATE: Wednesday, 08/26/98 TIME: 12:00:53
________________________________________
____________________________ Output Attributes _______________________________
Class
==>
Burst ==>
OLmt ==>
Form
==>
Fls/CC ==>
:
UCS ==>
:
FCB:A/V
==>
:
OPTCD ==>
PWD ==>
Dest
==>
Node
==>
Seps ==>
Desk/EWN ==>
Modify ==>
:
Xpro ==>
PageDEF
==>
Char1 ==>
Disp ==>
FormDef
==>
Char2 ==>
BLK ==>
LRECL
==>
Char3 ==>
Pri ==>
Copies
==>
Char4 ==>
DDNM ==>
Name
==>
Title
==>
Dept/XPRO ==>
Building ==>
Room
==>
Addr 1
==>
Addr 2
==>
Addr 3
==>
Addr 4
==>
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd ENTER=Update/I
Panel 4 of 5
Output Definition Panel 4 of 5
R.M.S. - Output Profile
MODE: ADD
DATE: Thursday, 10/10/96 TIME: 20:54:48
________________________________________
CHAPTER 5: SYSTEM ADMINISTRATION
PF1=Help PF3=End PF4=RET PF7=BWD PF8=FWD ENTER=UPDATE
Panel 5 of 5
Output Definition Panel 5 of 5
160
© 2013 Mantissa Corporation. All rights reserved.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
________________________ Banner Page Information _____________________________
BLK Letter ==> DANJONES JCL Member ==>
Addr Line 1 => DAN M.JONES
Addr Line 2 => 201 SUMMIT PARKWAY
Addr Line 3 => BIRMINGHAM, AL 35209
Addr Line 4 =>
Addr Line 5 =>
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Adding An Output Definition Record
Verification Report
System Reference Guide
Verification Report
The Output Verification (‘OV’) command produces a report that is routed to the Access Group and Location where
the OV command was issued from. The Report*ID is PRINTVER. This report allows users to approve the content of
the Output Request prior to being staged by the Output processing subtask.
The format of the ‘OV’ command is as follows:
(where ‘profname’ is equal to your Output definition profile
name)
OV PR O FN AM E <ENTER>
An example screen follows:
R.M.S. - Index of Reports
Date: Thursday,
Location: BIRMINGHAM
( SOFTCOPY
)
Command ==> OV PROFILE1
ID ReportID Report Title_______________ Media_____
01 REPORT01 RELEASE 11 RPT THRU FILTER
SOFTCOPY
02 REPORT02 RELEASE 11 RPT THRU FILTER
SOFTCOPY
03 REPORT03 RELEASE 11 RPT THRU FILTER
SOFTCOPY
04 REPORT04 RELEASE 11 RPT THRU FILTER
SOFTCOPY
05 REPORT05 RELEASE 11 RPT THRU FILTER
SOFTCOPY
06 REPORT06 RELEASE 11 RPT THRU FILTER
SOFTCOPY
07 REPORT07 RELEASE 11 RPT THRU FILTER
SOFTCOPY
08 REPORT08 RELEASE 11 RPT THRU FILTER
SOFTCOPY
09 REPORT09 RELEASE 11 RPT THRU FILTER
SOFTCOPY
10 REPORT10 RELEASE 11 RPT THRU FILTER
SOFTCOPY
11 REPORT11 RELEASE 11 RPT THRU FILTER
SOFTCOPY
12 REPORT12 RELEASE 11 RPT THRU FILTER
SOFTCOPY
13 REPORT13 RELEASE 11 RPT THRU FILTER
SOFTCOPY
14 REPORT14 RELEASE 11 RPT THRU FILTER
SOFTCOPY
15 REPORT15 RELEASE 11 RPT THRU FILTER
SOFTCOPY
16 REPORT16 RELEASE 11 RPT THRU FILTER
SOFTCOPY
17 REPORT17 RELEASE 11 RPT THRU FILTER
SOFTCOPY
PF1=Help
PF3=End
PF4=Ret
10/10/96 Time: 20:29:49
Date____
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
Scroll ==> PAGE
Time____ JESID
19:14:59
486
19:14:59
486
19:14:59
486
19:14:59
486
19:14:59
486
19:14:59
486
19:14:59
486
19:14:59
486
19:14:59
486
19:14:59
486
19:14:59
489
19:14:59
489
19:14:59
489
19:14:59
489
19:14:59
489
19:14:59
489
19:14:59
489
PF6=Refresh PF7=Bwd PF8=Fwd
Output Request
The Output Request is invoked ‘on demand’ and sent to the Output processing subtask for staging. It is not necessary
to perform Output Verification prior to issuing an ‘OR’ command. Reports must be viewable On-line to be eligible
for inclusion in an Output Request.
The format of the ‘OR’ command is as follows:
© 2013 Mantissa Corporation. All rights reserved.
(where ‘profname’ is equal to your Output definition profile
name)
CHAPTER 5: SYSTEM ADMINISTRATION
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
OR profname <ENTER>
161
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Linking Output Definition Panels
System Reference Guide
An example screen follows:
R.M.S. - Index of Reports
Date: Thursday,
Location: BIRMINGHAM
( SOFTCOPY
)
Command ==> OR PROFILE1
ID ReportID Report Title_______________ Media_____
01 REPORT01 RELEASE 11 RPT THRU FILTER
SOFTCOPY
02 REPORT02 RELEASE 11 RPT THRU FILTER
SOFTCOPY
03 REPORT03 RELEASE 11 RPT THRU FILTER
SOFTCOPY
04 REPORT04 RELEASE 11 RPT THRU FILTER
SOFTCOPY
05 REPORT05 RELEASE 11 RPT THRU FILTER
SOFTCOPY
06 REPORT06 RELEASE 11 RPT THRU FILTER
SOFTCOPY
07 REPORT07 RELEASE 11 RPT THRU FILTER
SOFTCOPY
08 REPORT08 RELEASE 11 RPT THRU FILTER
SOFTCOPY
09 REPORT09 RELEASE 11 RPT THRU FILTER
SOFTCOPY
10 REPORT10 RELEASE 11 RPT THRU FILTER
SOFTCOPY
11 REPORT11 RELEASE 11 RPT THRU FILTER
SOFTCOPY
12 REPORT12 RELEASE 11 RPT THRU FILTER
SOFTCOPY
13 REPORT13 RELEASE 11 RPT THRU FILTER
SOFTCOPY
14 REPORT14 RELEASE 11 RPT THRU FILTER
SOFTCOPY
15 REPORT15 RELEASE 11 RPT THRU FILTER
SOFTCOPY
16 REPORT16 RELEASE 11 RPT THRU FILTER
SOFTCOPY
17 REPORT17 RELEASE 11 RPT THRU FILTER
SOFTCOPY
PF1=Help
PF3=End
PF4=Ret
10/10/96 Time: 20:29:49
Date____
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
10/10/96
Scroll ==> PAGE
Time____ JESID
19:14:59
486
19:14:59
486
19:14:59
486
19:14:59
486
19:14:59
486
19:14:59
486
19:14:59
486
19:14:59
486
19:14:59
486
19:14:59
486
19:14:59
489
19:14:59
489
19:14:59
489
19:14:59
489
19:14:59
489
19:14:59
489
19:14:59
489
PF6=Refresh PF7=Bwd PF8=Fwd
Linking Output Definition Panels
To link multiple output definition panels together, key the Profile ID you wish to link to as the LAST access group in
the packet content area.
Once we link to another Output Profile, we do not branch back to read other entries from previous profiles.
When you issue the ‘OR’ (Output Request) for the Profile name, and it is a “linked” profile, the Output
Characteristics that govern the packet will come from the first profile in the link.
WEBACCESS DOCUMENT GROUPS
RMS WebAccess provides a quick and easy way to select reports for viewing. Through the use of Document Groups,
reports are organized within the browser window in a hierarchical, tree/branch display. Document Groups structure
viewing by Cabinet (Access Group), Drawer (Location) and File (Report ID).
Users can enter one (or more) DOCGROUPS at sign-on and the explorer view returned will contain all of the reports
they have access to.
The DOCGROUP profile name is used at Sign-On along with a UserID and Password to access softcopy reports
through the web browser. While all users have access to any of the DOCGROUPS defined in the system, it does not
mean they have access to every report referenced within the document groups. Access to the report data is governed
162
© 2013 Mantissa Corporation. All rights reserved.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
Report viewing via RMS WebAccess is available for any user with an XML compatible browser running Internet
Explorer 5.0 or above. User access to the WebAccess product is through a directory interface. The reports presented
to the user in the directory interface are added and maintained by document group profile records. These profile
records are referred to as a DOCGROUP. DOCGROUP profiles are kept in the QXACDS VSAM file. The
QXACDS file contains all of the administrative records needed to control user access to reports and printing
functions within RMS Online and RMS WebAccess.
RMS/Online® Version 11.35
System Reference Guide
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
RMS WebAccess Highlights
by internal security available within RMS Online, or by RMS WebAccess external security management. The sample
WebAccess ESM exit is the SEC0020 member available in the installation JCL library. Full details on how to
implement the WebAccess ESM exit can be found in the RMS Systems Reference - Installation Guide.
RMS WebAccess Highlights
•
Full GUI replacing traditional 'green-screen' character terminals
•
Watch function to provide for passive monitoring of character strings within a report
•
Find function providing text string searches
•
Up to 240 character print line viewing of report data on screen
•
Reports archived off-line can be easily retrieved and restored to RMS Online for WebAccess viewing
•
Select reports to view from the Document Group panel
•
Page Up/Down in full screen mode
•
Horizontal and vertical scale line feature for ease of navigation
•
Local, Email, or Host printing capabilities
•
Font resize of report data to allow display in a font of your choice
Docgroup Definition
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
The following pages outline the steps required to add document groups to the RMS system(s). DOCGROUP
maintenance is performed by the RMS Systems Administrator, or by an individual who has access to the
Administration functions of the RMS System. System Administrator functions are detailed in Appendix-D of the
RMS Systems Reference Manual.
© 2013 Mantissa Corporation. All rights reserved.
163
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Adding a Docgroup Profile Record
System Reference Guide
Adding a Docgroup Profile Record
R.M.S. - Primary Menu
Access Group - MANTISSA
Date: Tuesday,
03/05/02 Time: 14:43:08
SubSys: C134 Tran: HOL0 TermID: CP12 ___
Option ==> 2
1.
2.
3.
4.
5.
6.
T.
Display/Print
Administration
Distribution(Implicit)
Sysout/Report
Security
Help Management
Tutorial
PF1=Help
PF3=End
-
Display/Print a Report in the RMS Database
Administration and Resource Control
Distribution Definition and Management
Sysout/Report Profile Management
Security Definition and Management
Help Management and Maintenance
Tutorial on System Capabilities/Facilities
PF4=Return
From the RMS primary menu enter '2' in the Option ==> field and key <ENTER>.
R.M.S. - Administration
Access Group: MANTISSA
Date: Tuesday,
03/05/02 Time: 14:45:07
SubSys: C134 Tran: HOL0 TermID: CP12 ___
Option ==> AO
Access ==> MANTISSA
CHAPTER 5: SYSTEM ADMINISTRATION
Extended Info:
Field Security:
PF1=Help
PF3=End
_____________
Inquire List
IA
LA
IU
LU
IL
LL
IR
LR
IO
LO
IC
LC
EI
FS
---
---
---
---
PF4=Return
The Administration menu is presented. From this panel enter 'AO' in the Option ==> field and key <ENTER>.
164
© 2013 Mantissa Corporation. All rights reserved.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
Access Group:
User:
Location:
Retention:
Output Definition:
Customization:
____________
Options
Add
Change
Delete
AA
CA
DA
AU
CU
DU
AL
CL
DL
AR
CR
DR
AO
CO
DO
AC
CC
DC
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Adding a Docgroup Profile Record
System Reference Guide
R.M.S. - Output Profile
Mode: ADD
Profile/Loc
User/Media
Favorite/Pkt
DefAgeLimit
==>
==>
==>
==>
N O T E S:
==>
=>
=>
=>
=>
Date: Tuesday,
03/05/02 Time: 14:49:13
________________________________________
_______ Packet Content _______
AccessGp Location________ ReportID Seq_ Grp_ Flags OAL Note___________________
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
RM9134I Enter information for new record
ENTER=Update/Inq
Panel 1 of 5
The 'AO' command will return the Output Profile panel in Add mode.
R.M.S. - Output Profile
Mode: ADD
Profile/Loc
User/Media
Favorite/Pkt
DefAgeLimit
Date: Tuesday,
03/05/02 Time: 14:49:13
________________________________________
==> SAMPLE01
==>
==>
==>
AccessGp
MANTISSA
MANTISSA
MANTISSA
IVSYSTEM
IVSYSTEM
==> Sample document group (DOCGROUP) profile
=> for RMS WebAccess viewing
=>
=>
=>
_______ Packet Content _______
Location________ ReportID Seq_ Grp_ Flags OAL Note___________________
MAIN0001
SALES001
MAIN0001
SALES002
MAIN0001
PROFIT
SALES
STOCK
SALES
VENACT
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
RM9134I Enter information for new record
© 2013 Mantissa Corporation. All rights reserved.
ENTER=Update/Inq
CHAPTER 5: SYSTEM ADMINISTRATION
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
N O T E S:
Panel 1 of 5
165
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Adding a Docgroup Profile Record
System Reference Guide
The profile record 'SAMPLE01' is an example of a DOCGROUP that references a single Web BASE transaction
within a single CICS region. The diagram below shows the relationship of the reports referenced in the Packet
Content area to their physical location on the mainframe.
Following is a description of the fields on the Output Profile Record. Fields required for a DOCGROUP profile are
noted.
Profile/Loc:
(Required)
1-16 character name. Field contains the DOCGROUP name.
User/Media:
(Not Used) Field not used for DOCGROUP records.
Favorite/Pkt:
(Not Used) Field not used for DOCGROUP records.
DefAgeLimit:
(Not Used) Field not used for DOCGROUP records.
N O T E S:
(Optional)
NOTES field is a text area used to record information about the
document group profile and its' use.
CHAPTER 5: SYSTEM ADMINISTRATION
166
AccessGp
(Required)
1-8 character name. Specifies the Access Group used when the
report was distributed by the RM80004 job.
Location
(Required)
1-16 character name. Specifies the Online (softcopy) Location
where the report resides.
ReportID
(Required)
1-8 character name. Specifies the name of the Report as it
appears in RMS Online.
Seq
(Optional)
1 character field. Valid values are 'I' to insert a new record, or
'D' to delete an old record. Key either 'I' or 'D' and depress
<Enter>. If inserting a new record add the appropriate
AccessGp/Location/ReportID combination and depress
<Enter> to update the record. If deleting an old record, depress
<Enter> to update the record.
Grp
(Not Used) Field not used for DOCGROUP records.
Flags
(Not Used) Field not used for DOCGROUP records.
OAL
(Not Used) Field not used for DOCGROUP records.
Note
(Optional)
Field is only used when linking to a remote Online system.
© 2013 Mantissa Corporation. All rights reserved.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
The Packet Content area is where the reports to be viewed by the RMS WebAccess browser are defined. The reports
entered in the Packet Content area will be grouped by Access Group and Location in RMS WebAccess. The order in
which reports are entered in the packet content area does not reflect the order in which they will be presented in the
browser. Panels 2 and 3 of the record are available for additional input of reports. To access these panels key 'PF8'.
Panels 4 and 5 of the record are not used for Document Group records.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Adding a Docgroup Profile Record
System Reference Guide
Linking DOCGROUP Panels
To link multiple DOCGROUP panels together, key an '*' (asterisk) in the AccessGp field in the packet content area.
In the Location field key the name of the DOCGROUP you wish to link to.
R.M.S. - Output Profile
Mode: INQUIRE
Profile/Loc
User/Media
Favorite/Pkt
DefAgeLimit
Date: Wednesday, 03/06/02 Time: 12:45:15
________________________________________
==> SAMPLE01
==>
==>
==>
N O T E S:
AccessGp
MANTISSA
MANTISSA
MANTISSA
IVSYSTEM
IVSYSTEM
*
==> SAMPLE DOCUMENT GROUP (DOCGROUP) PROFILE
=> FOR RMS WEBACCESS VIEWING
=>
=>
=>
_______ Packet Content _______
Location________ ReportID Seq_ Grp_ Flags OAL Note___________________
MAIN0001
SALES001
MAIN0001
SALES002
MAIN0001
PROFIT
SALES
STOCK
SALES
VENACT
SAMPLE02
PF1=Help PF3=End PF4=Ret PF7=Bwd
RM9020I Enter record identifier
PF8=Fwd
ENTER=Update/Inq
Panel 1 of 5
The profile record above 'SAMPLE01' shows the record modified to reference a DOCGROUP 'SAMPLE02' residing
in the same Web BASE transaction within a single CICS region. The diagram/chart below shows the relationship of
the reports referenced in the Packet Content area to their physical location on the mainframe.
Profile/Loc:
(Required)
1-16 character name. Field contains the DOCGROUP name.
User/Media:
(Not Used) Field not used for DOCGROUP records.
Favorite/Pkt:
(Not Used) Field not used for DOCGROUP records.
DefAgeLimit:
(Not Used) Field not used for DOCGROUP records.
N O T E S:
(Optional)
NOTES field is a text area used to record information about the
document group profile and its' use.
The Packet Content area is where the reports to be viewed by the RMS WebAccess browser are defined. Panels 2 and
3 of the record are available for additional input of reports. To access these panels key 'PF8'. Panels 4 and 5 of the
record are not used for Document Group records.
AccessGp
(Required)
1-8 character name. A value of '*' is valid in the first position
of the AccesGp field if the profile record links to another
DOCGROUP profile.
Location
(Required)
1-16 character name. If the AccessGp field contains an '*', the
Location field would contain the name of the DOCGROUP
© 2013 Mantissa Corporation. All rights reserved.
167
CHAPTER 5: SYSTEM ADMINISTRATION
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
Following is a description of the fields on the Output Profile Record. Fields required for a DOCGROUP profile are
noted.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Adding a Docgroup Profile Record
System Reference Guide
profile record the users wishes to link to.
ReportID
(Not Used) Field not used for DOCGROUP records.
Seq
(Optional)
Grp
(Not Used) Field not used for DOCGROUP records.
Flags
(Not Used) Field not used for DOCGROUP records.
OAL
(Not Used) Field not used for DOCGROUP records.
Note
(Not Used) Field not used for DOCGROUP records.
1 character field. Valid values are 'I' to insert a new record, or
'D' to delete an old record. Key either 'I' or 'D' and depress
<Enter>. If inserting a new record add the appropriate
AccessGp/Location/ReportID combination and depress
<Enter> to update the record. If deleting an old record, depress
<Enter> to update the record.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
168
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
The Requirements
System Reference Guide
System Administration Case Study
Now that all panels have been covered in detail, let’s see how to put these pieces together in a series of tasks that will
accomplish the building of a database to match a given environment. Let’s take a set of requirements that represents a
hypothetical case and then see the details of how to build a set of records to control the system correctly. You may
need to review the Resource Security Systems Reference Manual for descriptions of the security panels.
The Requirements
For our example, we will describe an environment limited to one application system. The concepts we use here could
be expanded to include any size environment. The example is designed to show the use of each entry panel and would
probably not represent a real life example that could be used for the determination of the number of panels it would
take to enter all your work.
The System
The Inventory Control System - let’s make this the Access Group and give it the name IVSYSTEM.
The Reports
These reports are part of those sent as examples and installed with the system. They should be viewable to test the
results of the case study entry. If you actually enter the transactions we go through, please delete them afterwards so
others may do the case study.
STOCK
Year-to-date Stock Status Report
VENACT
Vendor Activity Report
PROFIT
Year-to-date Sales Profitability Report
The Locations
Denver
Successful Products, Inc.
Chicago
New Directions Corp.
New York
Headquarters Company
The Users and the Resources They Need
THE USERS AND THE RESOURCES THEY NEED
LOCATION
Denver
Chicago
Tom Williams
New York
RESOURCES
Display Print: Index, Versions, Display all reports.
Display Print: All except Print Start. Needs the following
reports: All reports for New York and see no other reports.
Display Print: Display all reports. Access all transactions.
Data Entry
Now let’s take a look at the panels that would satisfy this set of requirements specified.
© 2013 Mantissa Corporation. All rights reserved.
169
CHAPTER 5: SYSTEM ADMINISTRATION
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
USER
Carol Johnson
John Graham
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Data Entry
System Reference Guide
Administrative Menu Panel
R.M.S. - Administration
Access Group: IVSYSTEM
Date: Tuesday,
10/08/96 Time: 17:33:08
SubSys: R134 Tran:
TermID: 0028 ___
Option ==> AA
Access ==> IVSYSTEM
Access Group:
User:
Location:
Retention:
Output Definition:
Customization:
Extended Info:
Field Security:
PF1=Help
PF3=End
____________
Options
Add
Change
Delete
AA
CA
DA
AU
CU
DU
AL
CL
DL
AR
CR
DR
AO
CO
DO
AC
CC
DC
_____________
Inquire List
IA
LA
IU
LU
IL
LL
IR
LR
IO
LO
IC
LC
EI
FS
---
---
---
---
PF4=Return
This panel is the starting place for all System Administration entry and is accessed by selecting option 2 from the
main menu panel. The Access Group displayed on this panel will be that of the user adding these records. When you
make these changes your default access group will appear here.
FIELD
OPTION
VALUES
AA
DESCRIPTION
This will display the panel for the entry of the Access
Group record.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
170
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Data Entry
System Reference Guide
Access Group Master Panel
R.M.S. - Access Group Master
Mode: ADD
Date: Tuesday,
10/08/96 Time: 17:33:41
---------------------------------------*** Access Group ***
Access Group Identifier
==> IVSYSTEM
Secured/Unsecured (S/U)
==> S
Description > INVENTORY CONTROL SYSTEM
>
>
*** Administrator ***
Administrator ID
Administrator Name
==> SYSUI
Phone Number ==> 945-8930
==> JOHN DOE
PF1=Help PF3=End PF4=Ret ENTER=Update/Inq
RM9134I Enter information for new record.
This panel is needed to document information about the Access Groups and the System Administrator that is in
control of the Access Group.
ACCESS GROUP
SECURED/UNSEC.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
DESCRIPTION
ADMINISTRATOR ID
PHONE NUMBER
ADMINISTRATOR NAME
© 2013 Mantissa Corporation. All rights reserved.
VALUES
DESCRIPTION
IVSYSTEM
The name of the Access Group
Identifier.
These will be secured reports and
only those with correct security will
be able to access them. If U is
entered anyone with a logon will be
able to view reports in this access
group.
Documentation
S
INVENTORY
CONTROL
SYSTEM
SYSUI
(205)945-8930
JOHN DOE
CHAPTER 5: SYSTEM ADMINISTRATION
FIELD
This will be used to obtain and
display information about the
administrator when the AD
transaction is entered from the
display.
Documentation
Documentation
171
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Data Entry
System Reference Guide
Administrative Menu Panel
R.M.S. - Administration
Access Group: IVSYSTEM
Date: Tuesday,
10/08/96 Time: 17:35:04
SubSys: R134 Tran:
TermID: 0028 ___
Option ==> AL
Access ==> IVSYSTEM
Access Group:
User:
Location:
Retention:
Output Definition:
Customization:
Extended Info:
Field Security:
PF1=Help
PF3=End
____________
Options
Add
Change
Delete
AA
CA
DA
AU
CU
DU
AL
CL
DL
AR
CR
DR
AO
CO
DO
AC
CC
DC
_____________
Inquire List
IA
LA
IU
LU
IL
LL
IR
LR
IO
LO
IC
LC
EI
FS
---
---
---
---
PF4=Return
Now let’s add the correct location records. These records exist on your database when the system is shipped, and
unless they have been deleted, will not have to be entered. This may be checked with the LL command from this
panel. If the records do not exist, use the following transactions to build them.
FIELD
OPTION
VALUES
AL
DESCRIPTION
This will present the Add Location panel.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
172
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Data Entry
System Reference Guide
Location Master Panel
R.M.S. - Location Master
Mode: ADD
Date: Tuesday,
10/08/96 Time: 17:35:38
----------------------------------------
Location Name
==> DENVER
AD. Access Group ==> IVSYSTEM
Location Name
Phone Number
Address Line 1
Line 2
Line 3
Line 4
Line 5
Line 6
Line 7
==>
==>
==>
==>
==>
==>
==>
==>
==>
Template Location ==>
***
Name/Phone/Address
SUCCESSFUL PRODUCTS
(493) 876-8751
1234 MAIN STREET
SUITE 500
DENVER, CO 12345
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
RM9134I Enter information for new record.
***
ENTER=Update/I
Panel 1 of 2
On this panel we will enter identifying data and documentation about the location.
FIELD
VALUES
DENVER
AD. ACCESS GROUP
IVSYSTEM
ALL OTHER FIELDS
See Above
The name for the location. This will be the same as the
LOCATION on the Custom Packaging panel (RMS/DD) or
the LOCATION*NAME parameter on the
CREATE*PACKET command.
Administrative access group for this location. Used to
determine the system administrator for this location.
Documentation for identifying the location.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
LOCATION NAME
DESCRIPTION
© 2013 Mantissa Corporation. All rights reserved.
173
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Data Entry
System Reference Guide
Location Master Panel (continued)
R.M.S. - Location Master
Mode: ADD
Date: Monday,
08/26/98 Time: 10:57:49
----------------------------------------
____________________________ Output Attributes _______________________________
Class
==> D
Burst ==>
OLmt ==>
Form
==>
Fls/CC ==>
:
UCS ==>
:
FCB:A/V
==>
:
OPTCD ==>
PWD ==>
Dest
==>
Node
==>
Seps ==>
Desk/EWN ==>
Modify ==>
:
Xpro ==>
PageDEF
==>
Char1 ==>
Disp ==>
FormDef
==>
Char2 ==>
Blk ==>
LRECL
==>
Char3 ==>
Pri ==>
Copies
==>
Char4 ==>
DDNM ==>
Name
==>
Title
==>
Dept/XPRO ==>
Building ==>
Room
==>
Addr 1
==>
Addr 2
==>
Addr 3
==>
Addr 4
==>
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd ENTER=Update/I
Panel 2 of 2
These are the print characteristics that may be retrieved during an on-demand or selective print operation. This is
done by typing an “L” on the print characteristics panel displayed when the print transaction has been submitted. For
examples of how this panel will effect print processing, see the RMS/Online/Display Print Facility User Guide.
FIELD
CLASS
VALUES
D
DESCRIPTION
This will be printed in the D print class when the print
transaction is entered and the location attributes are
chosen.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
174
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Data Entry
System Reference Guide
Administrative Menu Panel
R.M.S. - Administration
Access Group: IVSYSTEM
Date: Tuesday,
10/08/96 Time: 17:35:04
SubSys: R134 Tran:
TermID: 0028 ___
Option ==> AL
Access ==> IVSYSTEM
Access Group:
User:
Location:
Retention:
Output Definition:
Customization:
Extended Info:
Field Security:
PF1=Help
PF3=End
____________
Options
Add
Change
Delete
AA
CA
DA
AU
CU
DU
AL
CL
DL
AR
CR
DR
AO
CO
DO
AC
CC
DC
_____________
Inquire List
IA
LA
IU
LU
IL
LL
IR
LR
IO
LO
IC
LC
EI
FS
---
---
---
---
PF4=Return
Now let’s add the next location.
FIELD
VALUES
AL
DESCRIPTION
This will go to this panel for adding the location record.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
OPTION
© 2013 Mantissa Corporation. All rights reserved.
175
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Data Entry
System Reference Guide
Location Master Panel
R.M.S. - Location Master
Mode: ADD
Date: Tuesday,
10/08/96 Time: 17:39:52
----------------------------------------
Location Name
==> CHICAGO
AD. Access Group ==> IVSYSTEM
Location Name
Phone Number
Address Line 1
Line 2
Line 3
Line 4
Line 5
Line 6
Line 7
==>
==>
==>
==>
==>
==>
==>
==>
==>
Template Location ==>
***
Name/Phone/Address
NEW DIRECTIONS CORP.
(303) 837-9457
432 LAKESIDE ROAD
CHICAGO, IL 66069
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
RM9134I Enter information for new record.
***
ENTER=Update/I
Panel 1 of 2
Here we will enter identifying data and documentation about the location.
VALUES
DESCRIPTION
LOCATION NAME
FIELD
CHICAGO
AD. ACCESS GROUP
IVSYSTEM
ALL OTHER FIELDS
See Above
The name for the location. This will be the same as the
LOCATION on the Custom Packaging panel (RMS/DD) or
the LOCATION*NAME parameter of the
CREATE*PACKET command.
Administrative access group for this location. Used to
determine the system administrator for this location.
Documentation for identifying the location.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
176
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Data Entry
System Reference Guide
Location Master Panel (continued)
R.M.S. - Location Master
Mode: ADD
Date: Monday,
08/26/98 Time: 10:57:49
----------------------------------------
____________________________ Output Attributes _______________________________
Class
==> C
Burst ==>
OLmt ==>
Form
==>
Fls/CC ==>
:
UCS ==>
:
FCB:A/V
==>
:
OPTCD ==>
PWD ==>
Dest
==>
Node
==>
Seps ==>
Desk/EWN ==>
Modify ==>
:
Xpro ==>
PageDEF
==>
Char1 ==>
Disp ==>
FormDef
==>
Char2 ==>
Blk ==>
LRECL
==>
Char3 ==>
Pri ==>
Copies
==>
Char4 ==>
DDNM ==>
Name
==>
Title
==>
Dept/XPRO ==>
Building ==>
Room
==>
Addr 1
==>
Addr 2
==>
Addr 3
==>
Addr 4
==>
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd ENTER=Update/I
Panel 2 of 2
These are the print characteristics that can be retrieved during demand or selective print operations. This is done by
typing an “L” on the print characteristics panel displayed when the print transaction has been submitted.
FIELD
VALUES
C
DESCRIPTION
This will be printed in the C print class when the print
transaction is entered and the location attributes are
chosen.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
CLASS
© 2013 Mantissa Corporation. All rights reserved.
177
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Data Entry
System Reference Guide
Location Master Panel
R.M.S. - Location Master
Mode: ADD
Date: Tuesday,
10/08/96 Time: 17:41:35
----------------------------------------
Location Name
==> NEW YORK
AD. Access Group ==> IVSYSTEM
Location Name
Phone Number
Address Line 1
Line 2
Line 3
Line 4
Line 5
Line 6
Line 7
==>
==>
==>
==>
==>
==>
==>
==>
==>
Template Location ==>
***
Name/Phone/Address
HEADQUARTERS COMPANY
(703) 693-8302
2901 WALL STREET
NEW YORK, NY 11122
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
RM9134I Enter information for new record.
***
ENTER=Update/I
Panel 1 of 2
Here we will enter identifying data and documentation about the New York location.
VALUES
DESCRIPTION
LOCATION NAME
FIELD
NEW YORK
AD. ACCESS
IVSYSTEM
The name for the location. This will be the same as the
LOCATION on the Custom Packaging panel (RMS/DD) or
the LOCATION*NAME parameter on the
CREATE*PACKET command.
Administrative access group for this GROUP location.
Used to determine the system administrator for this
location.
Documentation for identifying the location.
ALL OTHER FIELDS
See Above
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
178
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Data Entry
System Reference Guide
Location Master Panel (continued)
R.M.S. - Location Master
Mode: ADD
Date: Monday,
08/26/98 Time: 10:57:49
----------------------------------------
____________________________ Output Attributes _______________________________
Class
==> N
Burst ==>
OLmt ==>
Form
==>
Fls/CC ==>
:
UCS ==>
:
FCB:A/V
==>
:
OPTCD ==>
PWD ==>
Dest
==>
Node
==>
Seps ==>
Desk/EWN ==>
Modify ==>
:
Xpro ==>
PageDEF
==>
Char1 ==>
Disp ==>
FormDef
==>
Char2 ==>
Blk ==>
LRECL
==>
Char3 ==>
Pri ==>
Copies
==>
Char4 ==>
DDNM ==>
Name
==>
Title
==>
Dept/XPRO ==>
Building ==>
Room
==>
Addr 1
==>
Addr 2
==>
Addr 3
==>
Addr 4
==>
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd ENTER=Update/I
Panel 2 of 2
These are the print characteristics that can be retrieved during demand or selective print operations. This is done by
typing an “L” on the print characteristics panel displayed when the print transaction has been submitted.
FIELD
VALUES
N
DESCRIPTION
This will be printed in the N print class when the print
transaction is entered and the location attributes are
chosen.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
CLASS
© 2013 Mantissa Corporation. All rights reserved.
179
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Data Entry
System Reference Guide
Administrative Menu Panel
R.M.S. - Administration
Access Group: IVSYSTEM
Date: Tuesday,
10/08/96 Time: 17:43:23
SubSys: R134 Tran:
TermID: 0028 ___
Option ==> AU
Access ==> IVSYSTEM
Access Group:
User:
Location:
Retention:
Output Definition:
Customization:
Extended Info:
Field Security:
PF1=Help
PF3=End
____________
Options
Add
Change
Delete
AA
CA
DA
AU
CU
DU
AL
CL
DL
AR
CR
DR
AO
CO
DO
AC
CC
DC
_____________
Inquire List
IA
LA
IU
LU
IL
LL
IR
LR
IO
LO
IC
LC
EI
FS
---
---
---
---
PF4=Return
Now you are ready to identify the users that will be at the locations you previously entered. A <PF3> from the
Location Master panel will return to this menu panel.
FIELD
SELECTION OPTION
VALUES
AU
DESCRIPTION
This will select and add user transaction.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
180
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Data Entry
System Reference Guide
User-1 Master Record
R.M.S. - User Master
Mode: ADD
User ID
Def. Access GP
Def. Location
User Name
Phone Number
Address Line 1
Line 2
Line 3
Line 4
DS Print Job
ACC-GRP
IVSYSTEM
==>
==>
==>
==>
==>
==>
==>
==>
==>
==>
Date: Tuesday,
10/08/96 Time: 17:44:00
---------------------------------------1001
Template User ==>
IVSYSTEM
User Password ==>
DENVER
CAROL JOHNSON
(846) 356-5458
SUCCESSFUL PRODUCTS INC.
DENVER, CO
PW1001
User Type
DPRINT
Sel Print Job ==>
***** Security Profile *****
SECUR-GP RT S ACC GRP
SECUR-GP RT S ACC-GRP
1001
DP P IVSYSTEM 1001
LR A
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
RM9134I Enter information for new record.
ENTER=Update/I
SECUR-GP
==>
RT S
Panel 1 of 2
This panel will determine what RMS/Online resources Carol Johnson will be permitted to use. It will identify her as a
user and profile the transactions and reports she may view.
VALUES
1001
DEF. ACCESS GP
IVSYSTEM
USER
PASSWORD
PW1001
USER TYPE
Blanks
DEF.
LOCATION
USER NAME
DENVER
DESCRIPTION
This will be the user ID that Carol will use when signing
on to RMS/Online. This is an assigned number and
standards should be used. Your security officer might have
standards for your company already.
This is the default access group that will appear when
Carol goes to the Display/Print menu to access reports.
This is the password Carol must give when signing on to
RMS/Online. Standards and local security requirements
are important in deciding what is entered here.
This field is used to classify your users. It may be left
blank. “S” in this field means this user is a system
administrator. A “P” indicates this is a profile user record.
This is the location that will appear when Carol goes to the
Display/Print menu.
See panel
Documentation
DPRINT
This is the suffix of the Help Management Member Name
containing the JCL that Carol will use to print from an
archive file. The JCL is maintained on the Help
Management system as member
PRT.JOB.DPRINT.
PHONE NUMBER
ADDRESS LINE 1-4
DSPRINT JOB
© 2013 Mantissa Corporation. All rights reserved.
181
CHAPTER 5: SYSTEM ADMINISTRATION
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
FIELD
USER ID
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Data Entry
System Reference Guide
FIELD
VALUES
SEL PRINT JOB
SPRINT
ACC-GRP
IVSYSTEM
SECUR-GRP
1001
RT
DP
S
P
ACC-GRP
IVSYSTEM
SECUR-GP
1001
RT
S
LR
A
DESCRIPTION
** Reserved ** Selective print requests are serviced by the
output sub-task of the RMS Controller task beginning with
release 11.31.
The first resource given to Carol is transactions. Always
make this the first item. This access group must be the
same as the default access group entered above.
This is the security group that Carol is a part of. Since she
has unique security requirements, make this the same as
her user ID so it can be easily found later. If she has the
same requirements as a group of users for which
requirements have already been entered, this would refer to
that Security Group.
The first (and only) set of transactions Carol will have is
the Display and Print transactions.
Because Carol does not need all Display/Print transactions,
we will go to the security system and enter a partial list of
those she is allowed or denied.
Next, let’s give Carol access to reports. Once again the first
set of reports should be those in the default access group.
Her report access is also unique and we’ll use her user ID
so we can find the security group later.
The resource type is Location/Report resource.
Carol will have access to all Location/Reports within the
Access Group IVSYSTEM.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
182
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Data Entry
System Reference Guide
User-1 Master Panel (continued)
R.M.S. - User Master
Mode: ADD
Date: Tuesday,
10/08/96 Time: 17:46:04
----------------------------------------
Job Statement Information: Selective Print
==> //*
==> //*
==> //*
==> //*
Job Statement Information: Dataset Print
==> //PRINTRPT JOB (10,AB,555,T),'SUCCESSFUL PRODUCTS',MSGCLASS=X
==> //*
==> //*
==> //*
Job Statement Information: Cancel Report
==> //CANRPT JOB (10,AB,555,T),'SUCCESSFUL PRODUCTS',MSGCLASS=X
==> //*
==> //*
==> //*
PF1=Help
PF3=End
PF4=Ret
PF7=Bwd
PF8=Fwd
ENTER=Update/I
Panel 2 of 2
Variables
PRT.JOB.DPRINT
$DJC1
$DJC2
$DJC3
$DJC4
CAN.JOB.STREAM
$CJC1
$CJC2
$CJC3
$CJC4
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
Member
© 2013 Mantissa Corporation. All rights reserved.
CHAPTER 5: SYSTEM ADMINISTRATION
This is the second panel for the User Master record. It provides a way to customize the JCL used when the DPRINT
and CANCEL jobs are submitted. The most common items to be entered here is the JOB card that will be used when
Carol submits a print request. The JCL entered here must adhere to JCL syntax rules and must also conform to your
installation standards for Job Control Language. These will be the values placed where the respective variables occur
in the DPRINT and CANCEL JCL members.
183
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Data Entry
System Reference Guide
User-2 Master Record
R.M.S. - User Master
Mode: ADD
User ID
Def. Access GP
Def. Location
User Name
Phone Number
Address Line 1
Line 2
Line 3
Line 4
DS Print Job
ACC-GRP
IVSYSTEM
==>
==>
==>
==>
==>
==>
==>
==>
==>
==>
Date: Tuesday,
10/08/96 Time: 17:49:02
----------------------------------------
1002
Template User ==>
IVSYSTEM
User Password ==>
CHICAGO
JOHN GRAHAM
(312) 662-5458
NEW DIRECTIONS CORP.
CHICAGO, IL
PW1002
User Type
DPRINT
Sel Print Job ==> SPRINT
***** Security Profile *****
SECUR-GP RT S ACC GRP
SECUR-GP RT S ACC-GRP
SECUR-GP
1002
DP P IVSYSTEM 1002
LR P
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
RM9134I Enter information for new record.
ENTER=Update/I
==>
RT S
Panel 1 of 2
This panel will determine how John Graham will be able to use RMS/Online. It will identify him as a user and profile
the transactions and reports he may view.
VALUES
DESCRIPTION
CHAPTER 5: SYSTEM ADMINISTRATION
1002
DEF. ACCESS GP
IVSYSTEM
USER
PASSWORD
PW1002
USER TYPE
Blanks
This field is used to classify your users. It may be left
blank. “S” in this field means this user is a system
administrator. A “P” indicates this is a profile user record.
DEF.
LOCATION
USER NAME
CHICAGO
This is the location that will appear when John goes to the
Display/Print menu
See panel
Documentation
DPRINT
This is the suffix of the Help Management Member Name
containing the JCL that John will use to print from an
archive file. The JCL is maintained on the Help
Management system as member
PRT.JOB.DPRINT.
This will be the user ID that John will use when signing on
to RMS/Online.
This is the default access group that will appear when John
goes to the Display Print menu to access reports.
This is the password John must give when signing on to
RMS/Online.
PHONE NUMBER
ADDRESS LINE 1-4
DSPRINT JOB
184
© 2013 Mantissa Corporation. All rights reserved.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
FIELD
USER ID
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Data Entry
System Reference Guide
FIELD
VALUES
SPRINT
ACC-GRP
IVSYSTEM
SECUR-GP
1002
RT
DP
S
P
ACC-GRP
IVSYSTEM
SECUR-GP
1002
RT
S
LR
P
DESCRIPTION
** Reserved ** Selective print requests are serviced by the
output sub-task of the RMS Controller task beginning with
release 11.31.
The first resource to give John is transactions. Always
make this the first item. This access group must be the
same as the default access group entered above.
This is the security group that John is a part of. Since he
has unique security requirements, make this the same as
his ID so it can be easily found later.
The first (and only) set of transactions John will have is the
Display and Print transactions.
Because John does not need all Display/Print transactions,
we will go to the security system and enter a partial list of
those he is allowed or denied.
Next, let’s give John access to reports. Once again the first
set of reports should be those in the default access group.
His report access is also unique and we’ll use his user ID
so we can find the security group later.
The resource type is Location/Report resource.
John will have access to all Location/Reports within the
Access Group IVSYSTEM except the Profit report.
Resource Security information limiting John’s report
access will need to be entered.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
SEL PRINT JOB
© 2013 Mantissa Corporation. All rights reserved.
185
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Data Entry
System Reference Guide
User-2 Master Record (continued)
R.M.S. - User Master
Mode: ADD
Date: Tuesday,
10/08/96 Time: 17:50:29
----------------------------------------
Job Statement Information: Selective Print
==> //*
==> //*
==> //*
==> //*
Job Statement Information: Dataset Print
==> //PRINTRPT JOB (10,AB,777,T),'NEW DIRECTIONS CORP',MSGCLASS=X
==> //*
==> //*
==> //*
Job Statement Information: Cancel Report
==> //CANRPT JOB (10,AB,777,T),'NEW DIRECTIONS CORP',MSGCLASS=X
==> //*
==> //*
==> //*
CHAPTER 5: SYSTEM ADMINISTRATION
186
Member
Variables
PRT.JOB.DPRINT
$DJC1
$DJC2
$DJC3
$DJC4
CAN.JOB.STREAM
$CJC1
$CJC2
$CJC3
$CJC4
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
This is the second panel for the User Master record. It provides a way to customize the JCL used when the DPRINT
and CANCEL jobs are submitted. The most common items to be entered here is the JOB card that will be used when
John submits a print request. The JCL entered here must adhere to JCL syntax rules and must also conform to your
installation standards for Job Control Language. These will be the values placed where the respective variables occur
in the DPRINTand CANCEL JCL members.
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Data Entry
System Reference Guide
User-3 Master Record
R.M.S. - User Master
Mode: ADD
User ID
Def. Access GP
Def. Location
User Name
Phone Number
Address Line 1
Line 2
Line 3
Line 4
DS Print Job
ACC-GRP
IVSYSTEM
==>
==>
==>
==>
==>
==>
==>
==>
==>
==>
Date: Tuesday,
10/08/96 Time: 17:54:07
----------------------------------------
1003
Template User ==>
IVSYSTEM
User Password ==>
NEW YORK
TOM WILLIAMS
(212) 545-9990
HEADQUARTERS COMPANY
NEW YORK, NY
PW1003
User Type
DPRINT
Sel Print Job ==>
***** Security Profile *****
SECUR-GP RT S ACC GRP
SECUR-GP RT S ACC-GRP
1003
DP A IVSYSTEM 1003
LR A
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
RM9134I Enter information for new record.
ENTER=Update/I
SECUR-GP
==>
RT S
Panel 1 of 2
This panel will determine how Tom Williams will be able to use RMS/Online. It will identify him as a user and
profile the transactions and reports he may view.
VALUES
USER ID
1003
DEF. ACCESS GP
IVSYSTEM
USER PASSWORD
PW1003
USER TYPE
Blanks
DEF. LOCATION
NEW YORK
USER NAME
See panel
DESCRIPTION
This will be the user ID that Tom will use when signing on
to RMS/Online.
This is the default access group that will appear when Tom
goes to the Display/Print menu to access reports.
This is the password Tom must give when signing on to
RMS/Online
This field is used to classify your users. It may be left
blank. “S” in this field means this user is a system
administrator. A “P” indicates this is a profile user record.
This is the location that will appear when Tom goes to the
Display/Print menu.
Documentation
PHONE NUMBER
ADDRESS LINE 1-4
DSPRINT JOB
DPRINT
SEL PRINT JOB
SPRINT
© 2013 Mantissa Corporation. All rights reserved.
This is the suffix of the Help Management Member Name
containing the JCL that Tom will use to print from an
archive file. The JCL is maintained on the Help
Management system as member
PRT.JOB.DPRINT.
** Reserved ** Selective print requests are serviced by the
output sub-task of the RMS Controller task beginning with
release 11.31.
187
CHAPTER 5: SYSTEM ADMINISTRATION
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
FIELD
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Data Entry
System Reference Guide
FIELD
VALUES
ACC-GRP
IVSYSTEM
SECUR-GP
1003
RT
DP
S
A
ACC-GRP
IVSYSTEM
SECUR-GP
1003
RT
S
LR
A
DESCRIPTION
The first resource to give Tom is transactions. Always
make this the first item. This access group must be the
same as the default access group entered above.
This is the security group that Tom is a part of. Since he
has unique security requirements, make this the same as
his user ID so it can be easily found later.
The first (and only) set of transactions Tom will have is the
Display and Print transactions.
The A indicates that Tom may use all Display/Print
transactions. No other entry is needed for transactions.
Next, let’s give Tom access to reports. Once again the first
set of reports should be those in the default access group.
His report access is also unique and we’ll use his user ID
so we can find the security group later.
The resource type is Location/Report resource.
Tom will have access to all Location/Reports within the
Access Group IVSYSTEM at the location New York.
Since A is entered here Tom will be able to view other
locations as well as New York. Resource Security Records
must be entered for those reports Tom may view. Those
panels are ahead.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
188
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Resource Security
System Reference Guide
User-3 Master Panel (continued)
R.M.S. - User Master
Mode: ADD
Date: Tuesday,
10/08/96 Time: 17:56:06
----------------------------------------
Job Statement Information: Selective Print
==> //*
==> //*
==> //*
==> //*
Job Statement Information: Dataset Print
==> //PRINTRPT JOB (10,AB,999,T),'HEADQUARTERS CO',MSGCLASS=X
==> //*
==> //*
==> //*
Job Statement Information: Cancel Report
==> //CANRPT JOB (10,AB,999,T),'HEADQUARTERS CO',MSGCLASS=X
==> //*
==> //*
==> //*
PF1=Help
PF3=End
PF4=Ret
PF7=Bwd
PF8=Fwd
ENTER=Update/I
Panel 2 of 2
Member
Variables
PRT.JOB.DPRINT
$DJC1
$DJC2
$DJC3
$DJC4
CAN.JOB.STREAM
$CJC1
$CJC2
$CJC3
$CJC4
Resource Security
Because we listed a resource with “P” in the security profile portion of the User Master panel, we must now list those
items we want to permit or deny (whichever is the shortest).
From the Primary Menu Panel select #5 (Resource Security).
© 2013 Mantissa Corporation. All rights reserved.
189
CHAPTER 5: SYSTEM ADMINISTRATION
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
This is the second panel for the User Master record. It provides a way to customize the JCL used when the DPRINT
and CANCEL jobs are submitted. The most common items to be entered here is the JOB card that will be used when
it submits a print request. The JCL entered here must adhere to JCL syntax rules and must also conform to your
installation standards for Job Control Language. These will be the values placed where the respective variables occur
in the DPRINTand CANCEL JCL members.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Resource Security
System Reference Guide
Resource Security Panel
R.M.S. - Security
Date: Monday,
10/07/96 Time: 12:29:32
SubSys: R134 Tran:
TermID: 002B ___
Option ==> ADP
Transaction Type Security:
Display/Print
Administration
Distribution
Dataset Profile Mngmt
Resource Security
Help Management
___________ Options___________
Add
Delete
Inquire
List
ADP
DDP
IDP
LDP
ASA
DSA
ISA
LSA
ADD
DDD
IDD
LDD
ADM
DDM
IDM
LDM
ARS
DRS
IRS
LRS
AHM
DHM
IHM
LHM
Location/Report Security:
ALR
PF1=Help
PF3=End
DLR
ILR
LLR
PF4=Return
FIELD
SELECTION OPTION
VALUES
ADP
DESCRIPTION
This will take us to the panel to add a security record to
allow Carol Johnson a set of Display/Print transactions.
Each transaction you add will be placed in the list of resources on the right side of the panel. A complete list of
available transactions can be found in Appendix G of this manual. The <PF7> and <PF8> keys may be used to scroll
this list up or down.
CHAPTER 5: SYSTEM ADMINISTRATION
190
VALUES
ACCESS GROUP
SECURITY GROUP
PERMIT/DENY
IVSYSTEM
1001
P
ADD SOFTCOPY DPF/
TX
I
DESCRIPTION
The default access group on Carol’s User Master record
Carol’s security group.
Since Carol needs three Display/Print transactions we will
list those to permit. If she needed all except one then we
would deny her access to one transaction. The reason for
this field is to give the user the ability to reduce the data
entry requirements to the absolute minimum.
The first transaction we are giving Carol is the Index. This
will allow Carol to look at the index of reports available in
her assigned locations.
© 2013 Mantissa Corporation. All rights reserved.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
FIELD
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Resource Security
System Reference Guide
R.M.S. - Resource Security Maint.
Mode: ADD
Access Group
==>
Security Group ==>
IVSYSTEM
1001
Permit/Deny Access
ADD SOFTCOPY/DPF TX
PF1=Help
PF3=End
PF4=Ret
Date: Monday,
10/07/96 Time: 12:32:42
----------------------------------------
==> V
PF7=Bwd
==> P
Resource
********
I
________
________
________
________
________
________
________
________
________
________
________
PF8=Fwd
TOP
ENTER=Update/I
The last transaction entered will now show on the Resource list. Now enter the next transaction for Carol.
FIELD
V
DESCRIPTION
The next transaction needed is for the Versions
panel.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
ADD SOFTCOPY/DPF TX
VALUES
© 2013 Mantissa Corporation. All rights reserved.
191
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Resource Security
System Reference Guide
R.M.S. - Resource Security Maint.
Mode: ADD
Access Group
==>
Security Group ==>
IVSYSTEM
1001
Permit/Deny Access
ADD SOFTCOPY/DPF TX
PF1=Help
PF3=End
PF4=Ret
Date: Monday,
02/05/01 Time: 15:51:06
----------------------------------------
==> D
PF7=Bwd
==> P
Resource
********
V
________
________
________
________
________
________
________
________
________
________
________
PF8=Fwd
BOT
ENTER=Update/I
The last transaction entered will now show on the top of our Resource list. Now enter the last transaction for Carol.
FIELD
ADD SOFTCOPY/DPF TX
VALUES
D
DESCRIPTION
The next transaction needed is for display.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
192
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Resource Security
System Reference Guide
R.M.S. - Security
Date: Monday,
10/07/96 Time: 12:29:32
SubSys: R134 Tran:
TermID: 002B ___
Option ==> ADP
Transaction Type Security:
Display/Print
Administration
Distribution
Dataset Profile Mngmt
Resource Security
Help Management
___________ Options___________
Add
Delete
Inquire
List
ADP
DDP
IDP
LDP
ASA
DSA
ISA
LSA
ADD
DDD
IDD
LDD
ADM
DDM
IDM
LDM
ARS
DRS
IRS
LRS
AHM
DHM
IHM
LHM
Location/Report Security:
ALR
PF1=Help
PF3=End
DLR
ILR
LLR
PF4=Return
Now let’s add the transactions available to John Graham. These will be quicker because we can use the deny option.
FIELD
ADP
DESCRIPTION
This will take us to the panel to add a security record that
will allow John a set of Display/Print transactions.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
SELECTION OPTION
VALUES
© 2013 Mantissa Corporation. All rights reserved.
193
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Resource Security
System Reference Guide
R.M.S. - Resource Security Maint.
Mode: ADD
Access Group
==>
Security Group ==>
IVSYSTEM
1002
ADD SOFTCOPY/DPF TX
PF1=Help
PF3=End
PF4=Ret
Date: Monday,
10/07/96 Time: 12:37:23
----------------------------------------
Permit/Deny Access
==> D
==> PS
PF7=Bwd
PF8=Fwd
Resource
********
________
________
________
________
________
________
________
________
________
________
________
________
ENTER=Update/I
The use of the deny option will prevent John the use of the print start transaction and allow him the use of all other
display/print transactions.
FIELD
PERMIT/DENY ACCESS
ADD SOFTCOPY/DPF TX
VALUES
D
PS
DESCRIPTION
To deny him the PS transaction.
PS stands for Print Start.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
194
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Resource Security
System Reference Guide
R.M.S. - Security
Date: Monday,
10/07/96 Time: 12:39:33
SubSys: R134 Tran:
TermID: 002B ___
Option ==> ALR
Transaction Type Security:
Display/Print
Administration
Distribution
Dataset Profile Mngmt
Resource Security
Help Management
___________ Options___________
Add
Delete
Inquire
List
ADP
DDP
IDP
LDP
ASA
DSA
ISA
LSA
ADD
DDD
IDD
LDD
ADM
DDM
IDM
LDM
ARS
DRS
IRS
LRS
AHM
DHM
IHM
LHM
Location/Report Security:
ALR
PF1=Help
PF3=End
DLR
ILR
LLR
PF4=Return
John Graham was allowed to view all Chicago reports except the profit report. This will be another use for the deny
option.
FIELD
ALR
DESCRIPTION
This will take us to the panel to identify the reports John
Graham has available to view.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
Selection Option
VALUES
© 2013 Mantissa Corporation. All rights reserved.
195
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Resource Security
System Reference Guide
R.M.S. - Resource Security Maint.
Mode: ADD
Access Group
==>
Security Group ==>
IVSYSTEM
1002
ADD REPORT IDENTIFIER
PF1=Help
PF3=End
PF4=Ret
Date: Monday,
10/07/96 Time: 12:41:29
----------------------------------------
LOCATION IDENTIFIER
Permit/Deny Access
==> CHICAGO
==> D
==> PROFIT
PF7=Bwd
PF8=Fwd
Resource
********
________
________
________
________
________
________
________
________
________
________
________
________
ENTER=Update/I
This panel allows us to identify the reports you want to deny or permit a user to have. We are denying John access to
the profit report. He will be able to view all other reports in the CHICAGO location.
CHAPTER 5: SYSTEM ADMINISTRATION
ACCESS GROUP
IVSYSTEM
LOCATION IDENTIFIER
CHICAGO
SECURITY GROUP
1002
PERMIT/DENY ACCESS
D
ADD REPORT
PROFIT
IDENTIFIER
196
VALUES
DESCRIPTION
The default access group on
John’s User Master record.
This is the location for the
reports John will need.
John’s user ID. If his security
was the same as a group of
users, then the correct security
group would be used here
We are going to deny him the
use of one report.
The report that John cannot
view.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
FIELD
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Resource Security
System Reference Guide
R.M.S. - Security
Date: Monday,
10/07/96 Time: 12:39:33
SubSys: R134 Tran:
TermID: 002B ___
Option ==> ALR
Transaction Type Security:
Display/Print
Administration
Distribution
Dataset Profile Mngmt
Resource Security
Help Management
___________ Options___________
Add
Delete
Inquire
List
ADP
DDP
IDP
LDP
ASA
DSA
ISA
LSA
ADD
DDD
IDD
LDD
ADM
DDM
IDM
LDM
ARS
DRS
IRS
LRS
AHM
DHM
IHM
LHM
Location/Report Security:
ALR
PF1=Help
PF3=End
DLR
ILR
LLR
PF4=Return
Tom Williams was allowed access to all display/print transactions. Display/print security records do not need to be
added for Tom.
Tom is allowed to view all reports within his location. If all or “A” was entered on his user profile, then he could view
all reports for all locations within the access group. That is not our requirement. We want to limit him to only his
location. Here is how to limit him to just his location.
FIELD
VALUES
ALR
DESCRIPTION
This will take us to the panel to identify the reports Tom
Williams has available to view.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
SELECTION OPTION
© 2013 Mantissa Corporation. All rights reserved.
197
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
WebAccess Document Groups
Canceling Reports
System Reference Guide
R.M.S. - Resource Security Maint.
Mode: ADD
Access Group
==>
Security Group ==>
IVSYSTEM
1003
LOCATION IDENTIFIER
Permit/Deny Access
ADD REPORT IDENTIFIER
PF1=Help
PF3=End
PF4=Ret
Date: Monday,
10/07/96 Time: 12:41:29
----------------------------------------
==> DUMMY
PF7=Bwd
PF8=Fwd
==> NEW YORK
==> D
Resource
********
________
________
________
________
________
________
________
________
________
________
________
________
ENTER=Update/I
This panel allows us to identify the access characteristics of the reports for a particular user. We could list those that
Tom is permitted to access. The objective is to use the permit/deny option to reduce the amount of entry.
VALUES
CHAPTER 5: SYSTEM ADMINISTRATION
ACCESS GROUP
IVSYSTEM
LOCATION IDENTIFIER
NEW YORK
SECURITY GROUP
1003
PERMIT/DENY ACCESS
D
ADD REPORT
DUMMY
DESCRIPTION
The default access group in Tom’s User Master
record.
This is the location for the reports Tom will
need.
Tom’s user ID. If his security was the same as a
group of users, then the access to a security
group would be used here.
We are going to deny Tom access to a report that
does not exist and never will exist. This will
allow him access to all other reports in the New
York location.
The report we are denying Tom.
IDENTIFIER
Canceling Reports
Reports may be canceled by first displaying the Versions panel and selecting the desired report by placing a “C” in the
ID column. This will “Queue” the report for cancellation. Upon leaving the Versions panel, a job stream is submitted
to the internal reader for processing. (Cancel is performed in BATCH mode to maintain integrity of the VSAM files.)
If it is necessary to maintain the JCL which is submitted, this may be done through Help Management by updating
member “CAN.JOB.STREAM”.
198
© 2013 Mantissa Corporation. All rights reserved.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
FIELD
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Retention-Based Archive
Canceling Reports
System Reference Guide
The entire output from a particular execution of RM80004 may be canceled through System Administration/
Extended Information. When displaying the Run Tracking records, placing a “C” in the ID column will initiate the
cancel process for the selected RM80004 run.
NOTE: Cancelling via EI (extended information) cancels all reports associated with the date.
RETENTION-BASED ARCHIVE
RMS now provides a retention-based archive. With retention-based archive, reports with like retention requirements
can be grouped together to form a single archive dataset for each group. Using this type of archive allows ‘on
demand’ recovery and reprint of reports. This archive is fully SMS compatible, permits complete control of the SMS
storage hierarchy and is transparent to the SMS catalog and storage class.
There are two types of archives that take place within the RMS system. One is a Retention-Based archive and the
other is a BASE dataset archive.
Retention-based archive is only possible if a dataset is managed. A Managed dataset is any dataset that has an
associated fileset. The value specified in the DEFAULT*FILESET parameter of the RMS Control Region start-up
permits assignment of fileset name for datasets processed by the external writer interface. The Dataset Profile panel
permits assignment of a fileset for datasets processed by the subsystem interface. Though all distributed datasets are
associated with a fileset, BASE datasets may or may not have an associated fileset.
Retention-Based archive is performed by archive processing subtasks in the RMS control region. Retention-based
archive is activated through use of Retention Models.
Retention Models are added to RMS/Online via System Administration (‘AR’). The Retention Model allows users to
group reports with like retention attributes together. Variables are available for use in building the prototype archive
dataset name. The variables are resolved at create time to ensure the uniqueness of each archive dataset name. Items
such as date and time may be used to ensure unique dataset names and easy reference back to the distribution run.
New and existing retention control records can contain an archive group indicator which references a retention model
that contains the archive information.
•
Viewed immediately after recovery
•
Printed on a Local printer
•
Printed at a remote printer via RMS/Spool
•
Transmitted to a DeskTop Node or FTP Node
•
Held for subsequent redistribution
CHAPTER 5: SYSTEM ADMINISTRATION
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
Associating all datasets with a fileset allows for automated recovery of data. Recovery and reprint requests are staged
to the Recovery Processing Subtasks. BATCH jobs are no longer required to process recovery and reprint requests.
Many benefits accrue as a result of automated recovery. Recovered datasets may be:
NOTE: Without a FILESET, no INDEXing takes place, and no AUTOMATED
RECOVERY can occur.
© 2013 Mantissa Corporation. All rights reserved.
199
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Retention-Based Archive
Canceling Reports
System Reference Guide
System Administration Panel
R.M.S. - Administration
Access Group: MANTISSA
Date: Thursday, 01/25/01 Time: 09:13:10
SubSys: R134 Tran: B340 TermID: CP07 ___
Option ==> AR
Access ==> MANTISSA
Access Group:
User:
Location:
Retention:
Output Definition:
Customization:
Extended Info:
Field Security:
PF1=Help
PF3=End
____________
Options
Add
Change
Delete
AA
CA
DA
AU
CU
DU
AL
CL
DL
AR
CR
DR
AO
CO
DO
AC
CC
DC
_____________
Inquire List
IA
LA
IU
LU
IL
LL
IR
LR
IO
LO
IC
LC
EI
FS
---
---
---
---
PF4=Return
Figure 1. System Administration Panel
You may enter the Retention Control panel from the Administrative Menu as shown above. This panel is used to add
retention and archive model records. Enter ‘AR’ <ENTER> to begin.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
200
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Retention-Based Archive
Canceling Reports
System Reference Guide
Retention Control Panel
R.M.S. - Retention Control
Mode: ADD
Date: Thursday, 01/25/01 Time: 09:13:23
________________________________________
Access Group
Media Name
Location
Report/Model
* Enter 'RMODEL' for retention model *
* Model name for retention models
*
==>
==>
==>
==>
Data Retention Versions ==>
Data Retention Days
==>
Tracking Retention Versions ==>
Tracking Retention Days
==>
Archive Grp Identifier ==>
Archive Grp Max Block
==>
Archive Grp Max Segment ==>
___________________________ Allocation Attributes ____________________________
==>
==>
==>
==>
==>
==>
PF1=Help PF3=End PF4=Ret ENTER=Update/Inq
RM9134I Enter information for new record.
Figure 2. Retention Control Panel
Retention Control Panel - RMODEL Record
R.M.S. - Retention Control
Mode: ADD
Access Group
Media Name
Location
Report/Model
==> MANTISSA
==>
==> RMODEL
==> KEEP0003
Data Retention Versions ==>
Data Retention Days
==>
* Enter 'RMODEL' for retention model *
* Model name for retention models
*
0003
Tracking Retention Versions ==>
Tracking Retention Days
==>
Archive Grp Identifier ==> KEEP0003
Archive Grp Max Block
==>
Archive Grp Max Segment ==>
___________________________ Allocation Attributes ____________________________
==> DSN=PROD.R133.DYYMMDD.T#HHMMSS.ARCGROUP.RMSARC
==>
==>
==>
==>
==>
PF1=Help
PF3=End
PF4=Ret
CHAPTER 5: SYSTEM ADMINISTRATION
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
Date: Wednesday, 01/25/01 Time: 09:14:59
________________________________________
ENTER=Update/Inq
Figure 3. Retention Control Panel - RMODEL
© 2013 Mantissa Corporation. All rights reserved.
201
Chapter 5: System Administration
Additional Administrative Transactions
Retention-Based Archive
Canceling Reports
RMS/Online® Version 11.35
System Reference Guide
CHAPTER 5: SYSTEM ADMINISTRATION
202
Access Group (Required)
Any 1-8 character name describing the Access Group with
which the RMODEL is associated.
Media Name (Optional)
Media category the RMODEL record is associated with. If this
field is left blank, the RMODEL record will pertain to all
medias.
Location (Required)
The Location field for an RMODEL record must be equal to
RMODEL.
Report/Model (Required)
The name of the RMODEL record.
Data Retention Versions
NOT USED. The data retention versions field is not used on an
RMODEL record.
Tracking Retention Versions
NOT USED. The tracking retention versions field is not used
on an RMODEL record.
Data Retention Days (Required)
The number of days to keep the archive dataset. On the
RMODEL record, a value of ‘9999’ in Data Retention Days
will cause the archive dataset to be allocated with a disposition
of DISP=(New,Delete,Delete). This can be used during testing
to ensure the process is working. The value must be changed
prior to production if you want the archives to be kept after creation.
Tracking Retention Days
NOT USED. The tracking retention days field is not used on
an RMODEL record.
Archive Grp Identifier (Optional)
The archive group identifier field must contain a value if you
will be using the ARCGROUP symbolic below as part of the
dataset name. The RMODEL name is useful for this purpose.
Archive Grp Max Block
NOT USED. This field is reserved for future development.
Archive Grp Max Segment
NOT USED. This field is reserved for future development.
Allocation Attributes
Only the first line of the allocation attributes portion of the
panel is available for input. Data input on lines 2-6 is prohibited and will cause allocation failures if used. These fields are
for future development.
Dataset Symbolics
The following symbolics can be used to ensure that each retention archive dataset created has a unique 44 character JES
dataset name.
HHMMSS
Format=HHMMSS. Represents the time the dataset was created in HHMMSS format.
T#
Format=T#. Mantissa Corporation strongly recommends the
use of the T# indicator as a portion of the dataset name. The
use of ‘T#’ helps to ensure uniqueness in the generated dataset
name. Upon dataset creation, ‘T#’ will be resolved with an
archive task indicator of ‘A1’, ‘A2’, or ‘A3’ indicating the
© 2013 Mantissa Corporation. All rights reserved.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
Following is a description of the fields on the Retention Control RMODEL panel. Fields that are required on an
RMODEL record are noted.
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Retention-Based Archive
Canceling Reports
System Reference Guide
archive sub-task that serviced the request to generate the
dataset.
YYMMDD
Format=YYMMDD. Represents the date the dataset was created in YYMMDD format.
ARCGROUP
Format=1-8 character archive group identifier. The archive
group identifier field must be filled in to use this field. This
field typically contains the RMODEL record name. The field
is padded with ‘#’s if less than 8 characters.
ACCGROUP
Format=1-8 character access group identifier. If desired, the
access group associated with the RMODEL record can be used
as part of the generated dataset name.
AV2 through AV6 (Not Used)
The fields AV2 through AV6 are for future development.
In the example, the created dataset would have the following DSNAME created:
PROD.ARC.D961010.A1201349.RMSARC
The dataset name informs us at a glance that the archive task that created it ran on October 10, 1996, at 08:13:49 P.M.
Retention Control Panel - Report Record
R.M.S. - Retention Control
Mode: ADD
Date: Wednesday, 01/24/01 Time: 15:25:54
________________________________________
Access Group
Media Name
Location
Report/Model
* Enter 'RMODEL' for retention model *
* Model name for retention models
*
==> MANTISSA
==>
==> SUPPORT
==> TELECOM
0001
Tracking Retention Versions ==>
Tracking Retention Days
==>
0003
Archive Grp Identifier ==> KEEP0003
Archive Grp Max Block
==>
Archive Grp Max Segment ==>
___________________________ Allocation Attributes ____________________________
==>
==>
==>
==>
==>
==>
PF1=Help PF3=End PF4=Ret ENTER=Update/Inq
RM9134I Enter information for new record.
CHAPTER 5: SYSTEM ADMINISTRATION
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
Data Retention Versions ==>
Data Retention Days
==>
Figure 4. Retention Control Panel - Report
Following is a description of the fields on the Retention Control panel. Fields that are required on the record are
noted.
Access Group (Required)
© 2013 Mantissa Corporation. All rights reserved.
Any 1-8 character name describing the Access Group the
203
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Submitting Jobs from RMS
Canceling Reports
System Reference Guide
record is associated with.
Media Name (Optional)
The Media category you want the record associated with. If
this field is left blank, the record will pertain to all medias
within the Access Group specified.
Location (Optional)
The location the record is associated with. If you leave this
field blank, the retention will pertain to all Locations the specified report is in.
Report/RMODEL (Required)
The 1-8 character name of the REPORT ID.
Data Retention Versions (Optional)
The number of versions of the specified report you want viewable.
Tracking Retention Versions (Optional)
The number of versions of the report to track for viewing and
reprint purposes. The tracking retention versions have to be
greater than, or equal to the value specified in the data Retention Versions field.
Data Retention Days (Optional)
The number of days you want the specified report viewable.
Tracking Retention Days (Optional)
The number of days to track the report for viewing and reprint
purposes. The tracking retention days has to be greater than, or
equal to the value specified in the Data Retention Days field.
Archive Grp Identifier (Optional)
Required if referencing an RMODEL record. The 1-8 character name of an RMODEL record to associate the retention
control record to. If you specify an Archive Group Identifier,
you must use Data Retention Days and Tracking Retention
Days. You must also ensure that the number of Tracking
Retention Days is less than, or equal to the Data Retention
Days specified in the RMODEL record you reference in the
Archive Group Identified field.
Archive Grp Max Block
NOT USED. This field is reserved for future development.
Archive Grp Max Segment
NOT USED. This field is reserved for future development.
Allocation Attributes
The allocation attributes portion of the retention control record
panel is only used on an RMODEL record.
When using retention based archive, changes to your Retention Control records require the
control region to be cycled in order for the ‘new’ records to be read.
SUBMITTING JOBS FROM RMS
RMS may submit jobs to the host operating system under the following conditions:
1.
An authorized user has requested that an entire dataset be printed. The dataset may or may not be resident. A
dataset in this case is defined as a report for a specific location.
2.
An authorized user has requested selective (page range) printing for a resident dataset.
3.
An authorized user has requested cancellation of specific reports (or) the entire output of an RM80004 execution.
Cancellation deletes the Index/Version information and the report data.
204
© 2013 Mantissa Corporation. All rights reserved.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
NOTE:
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Help Management
Help Maintenance Menu
System Reference Guide
The default job streams defined in Help Management and submitted by RMS/Online for these tasks are:
Case 1 - Dataset Print -
PRT.JOB.DPRINT
Case 2 - Report Cancellation -
CAN.JOB.STREAM
Note that the body of each of these job control streams is maintained by RMS/HM (Help Management). At the time
the User Master is created, the System Administrator can designate the names of the Help members containing the
body of the JCL to be submitted for dataset and selective printing. A helpful hint is to only include the execution JCL
in the help panel. Use the help panel to submit job statements that execute cataloged procedures with overrides. This
lowers the required entry on the help panel.
Each user may have up to four jobs related statements to be appended to the body of the JCL member. This permits
selective accounting by an individual user.
HELP MANAGEMENT
Help Maintenance Menu
Help maintenance is used to add, modify, delete and view Help information in the Help Resource file. Key in the
selection character of the desired function and fill in the appropriate fields. If you are unsure of the Help Resource
name, ‘L’ will give you a list. Further help is available under “Help List Display” and “Help Formatting” under the
main HELP Menu.
Help List Display
Help List allows you to display a list of resources and their descriptions on the screen. Scrolling is allowed and is
implemented through the standard scroll PF keys. You may select a generic key for selection to narrow the selection
criteria. A line item may be selected for update, delete or viewing by placing a U, D or V on the appropriate ID field
and press Enter.
NOTE: While viewing a help panel the <CLEAR> key will return the viewer to the Help Menu or Help
List panel.
Help Information for Help
HELP formatting allows you to design a Help panel with attributes and control information for later display using the
HELP system. Text and control characters are input onto the panel free-form by using the cursor control keys. When
the panel is as desired, you may exit formatting by pressing the <ENTER> key. To abort, press the <CLEAR> key.
The low intensity character (+), the high intensity character (%) and the non-display character (@) are used to assign
attributes to a panel data string. For example, if the following string were entered:
% HIGH INTENSITY, + LOW INTENSITY, @ NON-DISPLAY
The displayed result would be:
HIGH INTENSITY, LOW INTENSITY,
PF Key and Option Field Assignments
The PF key assignments and option field assignments are defined by preceding the PF key or option character with a
logical not sign. The format of a definition is as follows:
XX X Y Y YY...
© 2013 Mantissa Corporation. All rights reserved.
205
CHAPTER 5: SYSTEM ADMINISTRATION
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
Help Format Information
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Help Management
Reserved Word List
System Reference Guide
where
XX X
= PF key assignment or option character
YY Y Y. . .
= Function to be performed
PF key assignments are of the format PF? or PFK? (? is the PF key number.) Option character is any valid character
A-Z.
Functions may define reserved word commands such as END, SETCSR or may give the Help Resource ID or page
number to pass control if the PF key or option has been selected. A resource ID or page number may be followed by
(RR,CC) to specify where the upper left hand corner of this panel should be displayed. If a page number is desired,
then it must be preceded by the letter P and contain four digits (P0001). (See variable definition for option field input
specification.)
Reserved Word List
The following is a list of valid reserved words:
END
Exit Help.
UP
Adds 1 to page number.
DOWN
Subtracts 1 from page number.
SETCSR
Sets the Row/Column at cursor position for next display.
Help Characters
The tilde (~) is used to delimit special command characters. Below is a list of these command characters and their
formats:
D
Drop (do not erase) the area right of this command.
L
Locate the cursor at the specified position format: L(RR,CC).
X
Allow the display of a control character such as %, +, etc.
where ‘X’ is replaced by one of these characters.
F
Fill to the last tilde with the fill string between the F and the
second tilde.
C
Center the string between the tildes on the line.
CHAPTER 5: SYSTEM ADMINISTRATION
Generates:
~F X Y Z ~
~
X Y Z X Y Z X Y Z X Y Z X Y Z
This:
~C CE N TE RE D ~
Generates:
CE NT E RE D
Help Variables
Variable information contained in the system may be displayed on the screen by specifying a variable name preceded
by an &.
An example of a variable would be &SACADW (which is the day of the week).
If we keyed:
206
© 2013 Mantissa Corporation. All rights reserved.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
This:
RMS/Online® Version 11.35
Chapter 5: System Administration
Additional Administrative Transactions
Help Management
Leaflets
System Reference Guide
TODAY IS &SACADW
The display would be:
TODAY IS WEDNESDAY
If an & is not preceded or followed by a character, it is considered to be an option field. The option field allows an
input option to be keyed for command selection. (See PF key/Option field definition.)
If a variable name is suffixed with an &, the field is processed as an input field, the data being placed in an area for
selection by the processing program. Note that this option is only valid where programming supports such fields.
Leaflets
RMS/Online has the ability to display “leaflets” (small panels) that you design. The AD and PF commands available
in DPF are examples of this capability. Using the Help Management component of the system, you design the
information leaflet and determine its content. These leaflet panels have names formed as follows:
where:
DS P .E N G. LE A FL ET X X
DS P .E N G. LE A FL ET is a constant prefix
XX is the leaflet command
A copy of the AI leaflet prototype is located in the appendices section of this manual.
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
NOTE: The END line is required to end the member. If it is not there, problems will occur.
© 2013 Mantissa Corporation. All rights reserved.
207
Chapter 5: System Administration
Additional Administrative Transactions
Help Management
Leaflets
RMS/Online® Version 11.35
System Reference Guide
Chap_05(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 5: SYSTEM ADMINISTRATION
208
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Definition of Terms
Security Level Definition
System Security
System Reference Guide
Chapter 6
SYSTEM SECURITY
Definition of Terms
This document contains information on the RMS security system. RMS/RS is the security component of RMS/
Online. RMS/RS allows you to permit or deny access to system resources based on profile information present in the
user master record. You might, for instance, grant one user the ability to perform Display Print transactions, while
denying that same user access to System Administrator and Resource Security transactions.
The following terms are used throughout this document. Taking a moment to review their meanings will enhance
your ability to understand RMS/RS.
Access Group
User
Security Group
Resource
A group of resources having similar accessibility
characteristics.
Someone granted access to RMS/Online through the creation of
a User Master record.
A collection of users having similar security requirements.
The object to be secured.
SECURITY LEVEL DEFINITION
System Security
RMS/Online always secures its resources by default. The only exception is in a situation where there has been a user
security exit module linked with the system. In that case, the responsibility for securing resources resides with the
user. The calls to the user exit will be made each time a request for services has been entered. This chapter must be
understood completely before attempting an exit. The format of the exit parameter list can be found in the
“Installation Procedures” section of this manual.
Access Group Level Security
The first security check for access permission at the report level is the security flag of the Access Group record. If the
Access Group record is set up as unsecured, then access to the report in question is permitted. If the Access Group is
secured, normal security checking is performed.
Chap_06(v11r35m1).fm: Revised Sunday, November 24, 2013
User Level Security
A user is either unsecured (an “S” denoting System Administrator in the User Type field) or secured (User Type field
is not an “S”). If the user is unsecured, then they are allowed access to all resources in the system, otherwise they are
secured through the User Profile/Security record combinations.
Resource Level Security
Security records are maintained at the resource level. There are two types, Transaction and Report. Each of these is
maintained as lists of resources. Transactions are qualified by specific Access Group, Security Group combinations.
Reports are qualified by Access Group, Security Group and Location.
© 2013 Mantissa Corporation. All rights reserved.
209
CHAPTER 6: SYSTEM SECURITY
Chapter 6: System Security
Chapter 6: System Security
System Reference Guide
Security Maintenance
Security is maintained at multiple levels in RMS/Online. If the user is a system administrator type “S”, then the user
is allowed access to any resource in the system. If this field is left blank or contains any character other than “S”, then
this user is subject to system security management. When a user is secured, user profiles must be defined for each
resource type within RMS/Online to which the user will be allowed access.
Before getting into how these user profiles are defined, let’s discuss the resource types. There are several resource
types within the system (see the list in Appendix A). However, there are only two security categories. These
categories are Transaction and Location/Report. The Transaction security resource types are broken down by their
main menu sub-titles (i.e., Display Print, System Administration, etc.) and are secured only under the users default
Access Group. Location/Report security allows reports for different Access Group, Security Group, Location
combinations to be secured for the user.
All of this sounds complex, but really isn’t. Let’s return now to the User Record security profiles. To allow a user to
perform any Display Print transactions, we would need to set up a profile with the Access Group the same as the
default Access Group of the user. The security group may be the same as the User ID (this is only a name for reading
the security records, if there are any) and the resource type would be “DP” (Display Print).
To allow this user access to all of these transactions, we would put “A” (all) under security type, and that‘s all that is
necessary. On the other hand, we may not wish this person access to all of these transactions and may wish to permit
access to only one (or a few). To allow partial security, it would be necessary to change the security type from “A”
(all) to “P” (partial). The “P” tells the system that there are security records to be read for this profile. If there are no
security records in the file for this Access Group/Security Group/Resource type combination, then access is denied.
To keep this from happening, we must enter these records through Security Maintenance. Adding the security records
requires only the entry of the Access Group, the Security Group, the Transaction ID to be secured and whether the
security data entered indicates permitted access or denied access.
Also, there is a method of maintaining common sets of Security Profiles. These are called Path Profiles. In this case,
the User Record contains a pointer to a record containing these common profiles. Any number of users may point to
this record by inserting the user ID of this profile record in the Access Group field of the “Profile” and a “*” in
position one of the Security Group field. This “dummy” user record is referred to as a “PROFILE” user. When
creating this record, placing a “P” in the user type field designates this record as a profile record, keeping anyone
from inadvertently signing on with it. (Up to five levels of a Path may be specified, i.e., a profile record may Path to
another profile record which points to another, which points to another.)
NOTE: All profiles within a profile set ahead of a Path profile are executed before the Path.
The following panel pages show how these security records are maintained.
Chap_06(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 6: SYSTEM SECURITY
Definition of Terms
Security Level Definition
Security Maintenance
RMS/Online® Version 11.35
210
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Definition of Terms
Security Level Definition
Security Maintenance
System Reference Guide
Access Group Master Panel
R.M.S. - Access Group Master
Mode: ADD
Date: Monday,
10/07/96 Time: 17:33:13
---------------------------------------*** Access Group ***
Access Group Identifier
Secured/Unsecured (S/U)
Description >
>
>
==>
==>
*** Administrator ***
Administrator ID
Administrator Name
==>
==>
Phone Number ==>
PF1=Help PF3=End PF4=Ret ENTER=Update/Inq
RM9134I Enter information for new record.
Access Group Master Pane
Security Considerations
This panel is discussed in the System Administration manual, beginning with Chapter 4, and can be reached by
depressing “2” from the main menu then “AA” in the administration menu.
Chap_06(v11r35m1).fm: Revised Sunday, November 24, 2013
The SECURED/UNSECURED ==> indicator in the Access Group Master is used only for Location/Report security.
Transactions are always assumed to be secured. Specifying “U” will cause security checking to be by-passed
altogether for reports in this Access Group. An “S” specification causes either RMS/Online or user security
processing to be invoked.
© 2013 Mantissa Corporation. All rights reserved.
211
CHAPTER 6: SYSTEM SECURITY
Chapter 6: System Security
RMS/Online® Version 11.35
Chapter 6: System Security
System Reference Guide
Security Considerations for User Records
R.M.S. - User Master
Mode: ADD
User ID
Def. Access GP
Def. Location
User Name
Phone Number
Address Line 1
Line 2
Line 3
Line 4
DS Print Job
ACC-GRP
==>
==>
==>
==>
==>
==>
==>
==>
==>
==>
SECUR-GP
Date: Monday,
10/07/96 Time: 17:34:48
---------------------------------------Template User ==>
User Password ==>
User Type
Sel Print Job ==>
***** Security Profile *****
RT S ACC GRP
SECUR-GP RT S ACC-GRP
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
RM9134I Enter information for new record.
ENTER=Update/I
SECUR-GP
==>
RT S
Panel 1 of 2
Security Considerations for User Records
Security Considerations
This panel is discussed in the System Administration Manual and can be reached by depressing “2” from the main
menu.
The User Master record forms the basis for establishing the resource security requirements for that user. Recall that
there are two major resource categories: Transaction and Location/Report.
All transactions are secured by coding Access Group/Security Group/Resource Type/Security Type sets in the
security profile fields. For all transaction security, the Access Group in the profile must match the default access
group for the user.
Security profiles for Location/Report access should specify the Access Group to which the report belongs, the
Security Group, “LR” in the Resource Type field, and “A” or “P” in the Security Type field. An “A” in the Security
Type field indicates access to resources with matching security characteristics.
Chap_06(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 6: SYSTEM SECURITY
Definition of Terms
Security Level Definition
Security Maintenance
212
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Definition of Terms
Security Level Definition
Security Maintenance
System Reference Guide
Transaction Security Add/Delete/Inquire Panel
R.M.S. - Resource Security Maint.
Mode: ADD
Access Group
==>
Security Group ==>
Permit/Deny Access
ADD SOFTCOPY/DPF TX
PF1=Help
PF3=End
Date: Monday,
10/07/96 Time: 17:36:20
----------------------------------------
PF4=Ret
==>
PF7=Bwd
==>
Resource
********
________
________
________
________
________
________
________
________
________
________
________
________
PF8=Fwd
ENTER=Update/I
Transaction Security Add/Delete/Inquire Panel
Transaction Security
Regardless of the type of transaction you are attempting to secure, the panel depicted on this page is presented. The
type of transaction resource is listed to the left of the Resource constant. Any resources already in the file are listed in
the Resource column. PF7/PF8 may be used to view additional resource ID’s. Top and Bottom will appear to the right
of the first and last resource in the Access Group/Security Group being maintained. All transaction resources are
secured using an Access Group that matches the default Access Group in the user master record. For inquiry
operations, enter the Access Group and Security Group and depress <Enter>. Secured transaction codes will appear
in alphabetical order in the RESOURCE column.
NOTE: Refer to Appendix-D,“Resource Security Categories, Types and Codes” for a list of valid Display
Chap_06(v11r35m1).fm: Revised Sunday, November 24, 2013
Print transactions.
© 2013 Mantissa Corporation. All rights reserved.
213
CHAPTER 6: SYSTEM SECURITY
Chapter 6: System Security
RMS/Online® Version 11.35
Chapter 6: System Security
System Reference Guide
Location/Report Security Add/Delete/Inquire Panel
R.M.S. - Resource Security Maint.
Mode: ADD
Access Group
==>
Security Group ==>
LOCATION IDENTIFIER
Permit/Deny Access
ADD REPORT IDENTIFIER
PF1=Help
PF3=End
Date: Monday,
10/07/96 Time: 17:37:17
----------------------------------------
PF4=Ret
==>
PF7=Bwd
==>
==>
Resource
********
________
________
________
________
________
________
________
________
________
________
________
________
PF8=Fwd
ENTER=Update/I
Location/Report Security Add/Delete/Inquire Panel
Transaction Security
The Location/Report Security maintenance panel is used to secure a report for a specific Access Group, Security
Group and Location combination. Reports which have already been entered appear in the RESOURCE column. Top
and Bottom appear on the first and last resource line. PF7/PF8 can be used to space backward and forward in the file.
For Inquiry, enter the Access Group, Security Group, and Location information and depress <ENTER>. The secured
reports will appear in the Resource column. The type of security active will appear in the
PERMIT/DENY == > field.
SECURITY EXAMPLES
Our example will show how to set up security for a User whose user ID is “JDOE”. The following things are required
of security.
214
•
Permit the user access to the Display/Print facility transactions: D (Display),
V (Versions), I (Index).
•
Permit the user access to Report “STOCK” of Location “Chicago” and Access Group “IVSYSTEM”.
•
Deny access to all other RMS/Online facilities.
© 2013 Mantissa Corporation. All rights reserved.
Chap_06(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 6: SYSTEM SECURITY
Definition of Terms
Security Examples
Security Maintenance
RMS/Online® Version 11.35
Definition of Terms
Security Examples
Security Maintenance
System Reference Guide
Step 1.
R.M.S. - User Master
Mode: ADD
User ID
Def. Access GP
Def. Location
User Name
Phone Number
Address Line 1
Line 2
Line 3
Line 4
DS Print Job
Date: Monday,
10/07/96 Time: 17:38:26
----------------------------------------
==> JDOE
==>
==>
==>
==>
==>
==>
==>
==>
==>
Template User ==>
User Password ==>
User Type
Sel Print Job ==>
***** Security Profile *****
RT S ACC GRP
SECUR-GP RT S ACC-GRP
ACC-GRP
SECUR-GP
PF1=Help
RM9134I
PF3=End PF4=Ret PF7=Bwd PF8=Fwd
Enter information for new record.
ENTER=Update/I
SECUR-GP
==>
RT S
Panel 1 of 2
This panel is discussed in the System Administration manual and can be reached by depressing “2” from the main
menu.
Chap_06(v11r35m1).fm: Revised Sunday, November 24, 2013
It is necessary, first, to ensure that the User Master record is set up correctly for security processing. For “JDOE” we
will leave the User Type field blank to indicate security checking is to be done.
© 2013 Mantissa Corporation. All rights reserved.
215
CHAPTER 6: SYSTEM SECURITY
Chapter 6: System Security
RMS/Online® Version 11.35
Chapter 6: System Security
System Reference Guide
Step 2.
R.M.S. - User Master
Mode: ADD
Date: Monday,
10/07/96 Time: 17:38:26
----------------------------------------
User ID
Def. Access GP
Def. Location
User Name
Phone Number
Address Line 1
Line 2
Line 3
Line 4
DS Print Job
ACC-GRP
==> JDOE
Template User ==>
==> IVSYSTEM
User Password ==> PW001
User Type
==> CHICAGO
==>
==>
==>
==>
==>
==>
==>
Sel Print Job ==>
***** Security Profile *****
SECUR-GP RT S ACC GRP
SECUR-GP RT S ACC-GRP
SECUR-GP
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
RM9134I Enter information for new record.
ENTER=Update/I
==>
RT S
Panel 1 of 2
Next, we must set up the default Access Group and Location for “JDOE”. These defaults will show on the Display/
Print menu when the user first enters the facility. Also, the default Access Group is used as the Access Group for
transaction security.
The password assigned to User Type is to be “PW001” which will be entered when JDOE signs on to RMS/Online.
Chap_06(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 6: SYSTEM SECURITY
Definition of Terms
Security Examples
Security Maintenance
216
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Definition of Terms
Security Examples
Security Maintenance
System Reference Guide
Step 3.
R.M.S. - User Master
Mode: ADD
User ID
Def. Access GP
Def. Location
User Name
Phone Number
Address Line 1
Line 2
Line 3
Line 4
DS Print Job
ACC-GRP
IVSYSTEM
==>
==>
==>
==>
==>
==>
==>
==>
==>
==>
Date: Monday,
10/07/96 Time: 17:38:26
---------------------------------------JDOE
IVSYSTEM
CHICAGO
JOHN DOE
Template User ==>
User Password ==>
PW001
User Type
DPRINT
Sel Print Job ==> SPRINT
***** Security Profile *****
SECUR-GP RT S ACC GRP
SECUR-GP RT S ACC-GRP
SECUR-GP
SEC01
DP P
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
RM9134I Enter information for new record.
ENTER=Update/I
==>
RT S
Panel 1 of 2
Now set up the Security Profile for “JDOE”. The Access Group for transaction security is always the default Access
Group of the user. Here it is “IVSYSTEM”. The Security Group is the name of a list of transactions to be permitted or
denied access. We will call ours “SEC01”. The Resource Type (RT) is the Transaction Group to be secured. To secure
the transactions for Display/Print this field is set to “DP”.
Chap_06(v11r35m1).fm: Revised Sunday, November 24, 2013
The last field for this profile is the “Security” field (S). A “P” here designates “Partial” security. This will tell the
security processor to read security records. We have now set up a profile for transaction security within Display/Print.
© 2013 Mantissa Corporation. All rights reserved.
217
CHAPTER 6: SYSTEM SECURITY
Chapter 6: System Security
RMS/Online® Version 11.35
Chapter 6: System Security
System Reference Guide
Step 4.
R.M.S. - User Master
Mode: ADD
User ID
Def. Access GP
Def. Location
User Name
Phone Number
Address Line 1
Line 2
Line 3
Line 4
DS Print Job
ACC-GRP
IVSYSTEM
==>
==>
==>
==>
==>
==>
==>
==>
==>
==>
JDOE
IVSYSTEM
CHICAGO
JOHN DOE
Date: Monday,
10/07/96 Time: 17:38:26
---------------------------------------Template User ==>
User Password ==>
PW001
User Type
DPRINT
Sel Print Job ==> SPRINT
***** Security Profile *****
SECUR-GP RT S ACC GRP
SECUR-GP RT S ACC-GRP
SECUR-GP
SEC01
DP P IVSYSTEM SEC01
LR P
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
RM9134I Enter information for new record.
ENTER=Update/I
==>
RT S
Panel 1 of 2
We must now set up the profile for Location/Report Security. In the Access Group field insert the name of the Access
Group to which this report belongs. This is assigned via RMS/DD or in the RMS/RDC Run Stream. Our example
uses “IVSYSTEM”. The Security Group is “SEC01”, the same as used on the “DP” profile. Under Resource type,
place “LR” (Location/Report), and for Security (S) place a “P” for partial security.
These are all the changes necessary to the user record to meet our security requirements.
Chap_06(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 6: SYSTEM SECURITY
Definition of Terms
Security Examples
Security Maintenance
218
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Definition of Terms
Security Examples
Security Maintenance
System Reference Guide
Step 5.
R.M.S. - Access Group Master
Mode: ADD
Date: Monday,
10/07/96 Time: 17:43:26
---------------------------------------*** Access Group ***
Access Group Identifier
==> IVSYSTEM
Secured/Unsecured (S/U)
==> S
Description > INVENTORY CONTROL SYSTEM
> RUN FOR THE CENTRAL ACCOUNTING DEPARTMENT
> CONTAINS DAILY, WEEKLY, AND MONTHLY REPORTS
*** Administrator ***
Administrator ID
Administrator Name
==>
==>
Phone Number ==>
PF1=Help PF3=End PF4=Ret ENTER=Update/Inq
RM9134I Enter information for new record.
This panel is discussed in the System Administration Manual and can be reached by depressing “2” from the main
menu.
Chap_06(v11r35m1).fm: Revised Sunday, November 24, 2013
When setting up the Access Group Master it is necessary to assign an “S” to the security indicator. This tells security
to secure all reports for this Access Group.
© 2013 Mantissa Corporation. All rights reserved.
219
CHAPTER 6: SYSTEM SECURITY
Chapter 6: System Security
RMS/Online® Version 11.35
Chapter 6: System Security
System Reference Guide
Step 6.
R.M.S. - Security
Date: Monday,
10/07/96 Time: 17:44:52
SubSys: R134 Tran:
TermID: 002B ___
Option ==>
Transaction Type Security:
Display/Print
Administration
Distribution
Dataset Profile Mngmt
Resource Security
Help Management
___________ Options___________
Add
Delete
Inquire
List
ADP
DDP
IDP
LDP
ASA
DSA
ISA
LSA
ADD
DDD
IDD
LDD
ADM
DDM
IDM
LDM
ARS
DRS
IRS
LRS
AHM
DHM
IHM
LHM
Location/Report Security:
ALR
PF1=Help
PF3=End
DLR
ILR
LLR
PF4=Return
The next step in setting up security is for the user to add security records. To do this, enter Security by entering “5”
from the main menu. The above panel will appear on the terminal. To add Display/Print transaction entries, select
option ADP (Add Display Print) from this menu.
The List Function is also available. For example: LDP will list all Display Print security groups.
Chap_06(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 6: SYSTEM SECURITY
Definition of Terms
Security Examples
Security Maintenance
220
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Definition of Terms
Security Examples
Security Maintenance
System Reference Guide
Step 7.
R.M.S. - Resource Security Maint.
Mode: ADD
Access Group
==>
Security Group ==>
IVSYSTEM
SEC01
ADD SOFTCOPY/DPF TX
Date: Monday,
10/07/96 Time: 17:45:51
----------------------------------------
Permit/Deny Access
==> D
==> P
Resource
********
________
________
________
________
________
________
________
________
________
________
________
________
PF1=Help
PF3=End
PF4=Ret
PF7=Bwd
PF8=Fwd
ENTER=Update/I
Chap_06(v11r35m1).fm: Revised Sunday, November 24, 2013
The Access Group and the Security Group should be entered as the same Access Group and Security Group of the
Security Profile for “DP”, “JDOE”. Now, enter a “P” in the Permit/Deny indicator stating that we wish this list of
transactions to be permitted access. Enter a “D” in the “ADD SOFTCOPY/DPF TX” field and depress <ENTER>.
© 2013 Mantissa Corporation. All rights reserved.
221
CHAPTER 6: SYSTEM SECURITY
Chapter 6: System Security
RMS/Online® Version 11.35
Chapter 6: System Security
System Reference Guide
Step 8.
R.M.S. - Resource Security Maint.
Mode: ADD
Access Group
==>
Security Group ==>
IVSYSTEM
SEC01
ADD SOFTCOPY/DPF TX
PF1=Help
PF3=End
PF4=Ret
Date: Monday,
10/07/96 Time: 17:46:54
----------------------------------------
Permit/Deny Access
==> V
PF7=Bwd
PF8=Fwd
==> P
Resource
********
D
________
________
________
________
________
________
________
________
________
________
________
TOP
ENTER=Update/I
As you can see, a resource of “D” is now in the Resource list column. A “V” is entered next and...
Chap_06(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 6: SYSTEM SECURITY
Definition of Terms
Security Examples
Security Maintenance
222
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Definition of Terms
Security Examples
Security Maintenance
System Reference Guide
Step 9.
R.M.S. - Resource Security Maint.
Mode: ADD
Access Group
==>
Security Group ==>
IVSYSTEM
SEC01
ADD SOFTCOPY/DPF TX
PF1=Help
PF3=End
PF4=Ret
Date: Monday,
10/07/96 Time: 17:48:11
----------------------------------------
Permit/Deny Access
==> P
==> I
PF7=Bwd
PF8=Fwd
Resource
********
D
V
________
________
________
________
________
________
________
________
________
________
BOT
ENTER=Update/I
Chap_06(v11r35m1).fm: Revised Sunday, November 24, 2013
... see a “V” in the list. (Note that there is an indicator denoting the bottom of the list. To scroll the list up, depress
the PF7 key.) The last transaction code, an “I”, is now entered, and the list is complete. This user is now secured to
meet our requirements for transaction security.
© 2013 Mantissa Corporation. All rights reserved.
223
CHAPTER 6: SYSTEM SECURITY
Chapter 6: System Security
RMS/Online® Version 11.35
Chapter 6: System Security
System Reference Guide
Step 10.
R.M.S. - Resource Security Maint.
Mode: ADD
Access Group
==>
Security Group ==>
IVSYSTEM
SEC01
ADD REPORT IDENTIFIER
PF1=Help
PF3=End
PF4=Ret
Date: Monday,
10/07/96 Time: 17:50:23
----------------------------------------
LOCATION IDENTIFIER
Permit/Deny Access
==> CHICAGO
==> P
==>
PF7=Bwd
Resource
********
________
________
________
________
________
________
________
________
________
________
________
________
PF8=Fwd
ENTER=Update/I
To allow user access to the report “STOCK”, it is necessary to enter the above panel by keying “ALR” from the
Security Maintenance menu. The fields here are similar to those for transaction security. Access Group and Security
Group are the same as those in the Security Profile for “LR” of “JDOE” User Record.
Location Identifier is the location under which the report “STOCK” resides.
Chap_06(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 6: SYSTEM SECURITY
Definition of Terms
Security Examples
Security Maintenance
224
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Definition of Terms
Security Examples
Security Maintenance
System Reference Guide
Step 11.
R.M.S. - Resource Security Maint.
Mode: ADD
Access Group
==>
Security Group ==>
IVSYSTEM
SEC01
ADD REPORT IDENTIFIER
PF1=Help
PF3=End
PF4=Ret
Date: Monday,
10/07/96 Time: 17:50:23
----------------------------------------
LOCATION IDENTIFIER
Permit/Deny Access
==> CHICAGO
==> P
==> STOCK
PF7=Bwd
PF8=Fwd
Resource
********
________
________
________
________
________
________
________
________
________
________
________
________
ENTER=Update/I
Chap_06(v11r35m1).fm: Revised Sunday, November 24, 2013
Enter the Report Identifier of “STOCK”, depress <ENTER>, and our short list of one report is complete. Our
resource security requirements for this user are also complete. “JDOE” may now sign on and display the report
“STOCK” of Location “Chicago” and Access Group “IVSYSTEM”.
© 2013 Mantissa Corporation. All rights reserved.
225
CHAPTER 6: SYSTEM SECURITY
Chapter 6: System Security
Chapter 6: System Security
System Reference Guide
Chap_06(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 6: SYSTEM SECURITY
Definition of Terms
Security Examples
Security Maintenance
RMS/Online® Version 11.35
226
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
Access
Report Access
System Reference Guide
Chapter 7
DISPLAY PRINT FACILITY
Introduction
Anyone associated with the production and distribution of reports knows that it is an expensive and complicated
process. Application system complexity aside, the fact that individual user’s report delivery needs vary widely,
further complicates matters.
One of the major problems related to report management is distribution labor intensiveness. Sometimes the same
report must be handled by several different people before the required distribution tasks have been completed.
Physical delivery time can often make the report nearly worthless because it is outdated.
Reports committed to RMS/DPF are indexed and decollated so that a single report can be viewed by any number of
locations. Once the users of the system know their Location Name and Access Group, the system will tell them which
reports are available for viewing, the number of versions available, date and time of production, and whether the
report is available on-line or through some other media type, such as microfiche.
All of this is accomplished in accordance with established distribution definitions with complete transparency to end
users. Even though a print dataset might contain the report data for any number of other users, they will never be
aware of the existence of the other users’ report data unless the Distribution Definition indicates that they should have
access to those users’ report material.
ACCESS
Report Access
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
Reports can be retrieved from the Report Management System in the following ways:
On-line viewing
Users to whom reports have been distributed can view and
request reprint of all or part of those reports (security permitting).
Partial report printing
Page ranges of a report may be selected for print during the
actual report viewing process.
Recovery by Location
Selected users may request reprint or reload of an entire report
from either the versions panel or display panel. Because RMS/
ONLINE maintains a catalog of the archive/report version relationship, it can automatically recover a report.
System Access
Access to RMS/DPF is accomplished through a series of formatted panels presented on 32XX or compatible
terminals. Any terminal with at least 24 display lines is supported. Using these panels, the user can retrieve an index
of the available reports, obtain information on specific versions, and display or request reprint. RMS/DPF uses the
following panels:
•
Access Authorization
•
Primary Menu
© 2013 Mantissa Corporation. All rights reserved.
227
CHAPTER 7: DISPLAY PRINT FACILITY
The alternative provided by RMS/DPF permits storage, backup, recovery and view/reprint capabilities of reports as
soon as the production cycle is complete. This translates to reduced expense, faster availability and better service.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
Access
System Access
System Reference Guide
•
Display/Print Menu
•
Index
•
Versions
•
Display
•
Print Characteristics
•
Notepad
Because report pages are usually wider than your terminal screen, the system uses the screen as a window into the
report page.
CHAPTER 7: DISPLAY PRINT FACILITY
LOCATION: CHICAGO
REPORT: STOCK
>
< P:
1 L:
COMMAND ==>
SCROLL ==>
-- START OF DATA --- START OF DATA --- START OF DATA --- TOP OF PAGE --- TOP OF PAGE --- TOP OF PAGE -CHICAGO
YEAR-TO-DATE STOCK STATUS REPORT
ITEM
NO. RECEIPTS
SALES
TRANSFRS
ADJTS
PHY
10001
0
40
11
0
158
10002
0
38
12
0
160
10004
0
36
13
0
162
10005
0
34
14
0
164
10006
0
80
23
0
231
10009
0
66
19
0
87
10011
0
50
15
0
8
10012
0
31
9
2
11
10014
0
72
20
0
108
10015
0
40
11
0
123
10016
0
87
25
0
37
10018
0
91
28
0
71
10019
0
127
41
0
101
10020
0
340
87
7
502
10021
0
16
4
0
5
10022
0
5
1
0
0
10023
0
61
15
0
7
10024
0
11
3
0
1
1
FULL
-- ST
-- T
INV
30
40
50
60
133
23
75
55
225
35
110
85
250
750
45
100
90
40
The 32XX Screen as a Window into a Report
Such operations as data manipulation (through column selection), search operations, and turning from page to page
are accomplished with program function keys located on the terminal keyboard.
RMS/DPF permits you to collapse reports so that only specific columns are viewable on a screen. Data not important
to specific users can be excluded, reducing terminal operations to a minimum. The report data can thereby be
accessed in a more usable form.
228
© 2013 Mantissa Corporation. All rights reserved.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
In the illustration above, you see an example of the terminal screen as a window. RMS/DPF gives you the ability to
move this window right, left, up and down in order to view the necessary data.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
Communicating Your Report Access Requirements
Requesting On-line Report Access
System Reference Guide
COMMUNICATING YOUR REPORT ACCESS REQUIREMENTS
The system administrator is the focal point for the information necessary to make a report available On-line. The
administrator will assign a LOCATION identification that will designate you as a unique distribution location within
your organization. The administrator will also assign the user identification necessary for using RMS/DPF.
Requesting On-line Report Access
Once you have identified a report that you feel should be viewable on-line, you should contact the administrator. The
administrator is in a position to expedite the addition of the control information required to make the report available
on-line. You should be prepared to provide the system/access group administrator with the following information.
Report Title and Originating System
User Access
A list of users that you want to grant permission to view the
report.
Report Retention
How many versions and/or days do you wish to be able to view
on-line?
Decollation Required
Do you wish each user to be able to view all of the report or
just part of the report? Note that any one user may be granted
access to any of the other users’ report information if so
desired.
User Identification
After receiving your request for the on-line viewing of the
report data, the administrator will define those users not
already identified to the system.
During this process the administrator will assign a password to
each user (if this is the installation standard). If you are
assigned a password, it is suggested that it be changed each 30
day period.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
Location Definition
In accordance with system conventions, each endpoint to
which report data is distributed must have a Location Name.
Your administrator will assign you a location name if you don’t
already have one.
VIEWING CAPABILITIES
RMS/DPF gives the user the ability to view reports on any of the 32xx family of terminals. It provides the following
capabilities:
•
Access authorization via internal security or user security exit
•
Report index and versions display to facilitate user selection of reports
•
Report separation so that an individual user sees only that part of a report that is needed
•
Automatic release of reports to the viewing community
•
Column selection of report data on the terminal screen to suit the needs of individual users
© 2013 Mantissa Corporation. All rights reserved.
229
CHAPTER 7: DISPLAY PRINT FACILITY
This information is important to link the requested report back to the creating job so that the report may be selection
for distribution.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
How to Use RMS/DPF
Panel Management Characteristics
System Reference Guide
•
Multi-report viewing through a windowing capability
•
Cancellation (security permitting) of reports
•
Viewing format Definition/Retention
•
Note attachment at the report line level
•
Report RELOAD capability that permits off-line reports to be restored to viewing status
HOW TO USE RMS/DPF
Report information is presented at your terminal in the form of panels. A panel is a display image. As a user, you
cause the system to perform certain functions by entering an option in the OPTION ==> field and depressing the
ENTER key on your terminal.
Panel Management Characteristics
All transactions share common characteristics with regard to panel formatting and system response.
CHAPTER 7: DISPLAY PRINT FACILITY
Panel Format
Panel Heading - Left to right, the descriptive panel name, date, day of week and time of day are displayed. The panel
heading is omitted on the report viewing panel to permit display of additional report data.
Panel Body
Transaction related data
Line 23
Active PF keys
Line 24
Message data area. Single line messages will always appear in
this area. Multi-line messages will cause MULTIPLE MESSAGES PENDING to appear in the message line. Depressing
the HELP PF key will cause the full text of all outstanding
messages to be displayed.
Selection Characteristics
Scrolling Characteristics
On panels where scroll operations apply, the following values may be entered in the SCROLL ==> field.
230
(P)AGE
- scroll to report top of page (Display panel only)
(H)ALF
- scroll half the panel depth
(F)ULL
- scroll full panel depth
NNNNN
- scroll NNNNN lines
© 2013 Mantissa Corporation. All rights reserved.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
On panels such as Index and Versions where multiple items are listed for selection, two methods of selection are
available. Using the Versions panel as an example, you will notice that there is an ID field on the left border of the
panel and a COMMAND ==> field at the top of the panel. On such panels, the cursor may be positioned in the ID
field of the desired selection and place the option in the selected items ID field. The same item may be selected by
entering the option followed by the ID field number. Selection of line item 03 for printing could be entered as ‘P 3’ in
the command field.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
System Help Facilities
Program Function Key Utilization
System Reference Guide
Program Function Key Utilization
RMS/DPF uses pre-defined program function (PF) keys to aid viewing. A complete list of the PF keys is located in
the following table. Individual users may customize their PF key settings on the Access Authorization panel. We
discourage this customization since the documentation will no longer match the actual operation of the system.
PF KEY
HELP
SWITCH NOTE
END
SWITCH REPORT
1/13
2/14
3/15
4/16
FIND/REPEAT FIND
5/17
NOTE
SCROLL/PAGE UP
6/18
7/19
SCROLL/PAGE DOWN
8/20
SWITCH WINDOW
9/21
SCROLL LEFT
SCROLL RIGHT
ZOOM
WINDOW
10/22
11/23
12/24
DESCRIPTION
Displays an explanation of the options now available to the user.
Retrieves noted page locations and displays them in succession.
Returns to the previously displayed panel.
Causes the next active report, if any, within the current window to be
displayed. A specific report name may be entered on the command
line.
Reissues a previously issued FIND command, beginning at the
position established by the previously issued FIND command if data
is found, otherwise from the top of the screen.
Notes the current display location.
Scrolls upward through the report for the value specified in the Scroll
Value field.
Scrolls down through the report
data for the value specified in the Scroll Value field.
Switches from the active window
to the next window available.
Shifts the panel to the left.
Shifts the panel to the right.
Changes current window from window size to full screen and viceversa.
SYSTEM HELP FACILITIES
RMS/DPF has corresponding Help panel(s) for each system panel. In order to access the Help panel, the user simply
presses the Help program function key (PF1/PF13).
Each Help panel contains a complete explanation of the entry/data requirements for the panel in question.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
System User Panels
This section depicts the various user panels and discusses their use in gaining access to the system, displaying reports,
scheduling selective or full report printing, obtaining report index or version information, and soliciting system help
facilities.
•
ACCESS AUTHORIZATION
•
PRIMARY MENU
•
DISPLAY/PRINT MENU
•
INDEX
•
VERSIONS
•
DISPLAY
•
REQUEST PRINT
•
NOTEPAD
© 2013 Mantissa Corporation. All rights reserved.
231
CHAPTER 7: DISPLAY PRINT FACILITY
FUNCTION
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
System Help Facilities
System User Panels
•
System Reference Guide
TUTORIAL
The user’s first interaction with RMS/Online for each session (a session is the time between sign-on and sign-off) is
through the Access Authorization panel. The Access Authorization panel may be bypassed completely by entering
the user ID and password (if any) after the transaction code.
.RM.S. - Access Authorization
Mantissa (C)opyright MCMXCII
CHAPTER 7: DISPLAY PRINT FACILITY
Required:
User ID
Password
==>
==>
Optional:
New Password
Verify Password
==>
==>
Program Function
Use
Caution
When
Changing
PF1=Help
PF3=End
Keys:
PF01 ==>
PF04 ==>
PF07 ==>
PF10 ==>
Date: Monday,
10/07/96 Time: 17:11:15
SubSys: R134 Tran:
TermID: 002B ___
(( New and Verify Passwords ))
((
** Must Match **
))
PF02
PF05
PF08
PF11
==>
==>
==>
==>
PF03
PF06
PF09
PF12
==>
==>
==>
==>
PF4=Return
System User Panels
After this sign-on is entered, RMS/Online presents a Primary Menu panel that can be used to access various RMS/
Online components. The following session examples illustrate the steps and the type of interaction necessary to
perform three RMS/DPF tasks.
Session Example 1.
Objective
1.
Sign-on to RMS/Online.
2.
The Primary Menu panel is displayed. Select “1” for RMS Display/Print. The Display/Print Menu is presented.
Enter “D” in the Option ==> field, DENVER in the LOCATION NAME ==> field,
and PROFIT in the REPORT NAME ==> field.
Session Example 2.
Objective
Print yesterday’s copy of EDITRUN using default and report characteristics data.
1.
232
Sign-on to RMS/Online (or return to the Display/Print Menu).
© 2013 Mantissa Corporation. All rights reserved.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
Display the most recent copy of PROFIT report for location DENVER.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
System Reference Guide
Introduction
System Help Facilities
System User Panels
2.
The Primary Menu panel is displayed. Select “1” for RMS Display/Print. The Display/Print Menu is presented.
3.
Enter “V” in the Option field and DENVER in the Report Name field.
4.
The Versions panel is displayed showing the available versions of PROFIT. The versions of the report are displayed beginning with the most recent version.
5.
Enter “P” and the display line number field of the version to be printed in the Command field.
Session Example 3.
Objective
1.
Sign-on to RMS/Online (or return to the Display/Print Menu).
2.
The Primary Menu panel is displayed. Select “1” for Display/Print. The Display/Print menu is presented.
3.
Enter “I” in the Option field and DENVER in the Location Name field.
4.
The Index panel is displayed. Display, Version and Print functions may be selected at this point.
Pressing PF3/PF15 will cause RMS/DPF to exit from the current panel, or exit the system if depressed during the
display of the Primary Menu panel.
The system Help facility may be invoked at any time by pressing PF1/PF13. When Help is invoked, a tutorial screen
appears with information pertaining to the system function currently being used. PF3/PF15 may then be depressed to
return to the screen being displayed before Help was invoked.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
Examples of the various RMS/DPF system panels and a description of the options available using those panels may
be found on the following pages.
© 2013 Mantissa Corporation. All rights reserved.
233
CHAPTER 7: DISPLAY PRINT FACILITY
Display a list of all reports available for viewing at distribution location DENVER.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
System Help Facilities
System User Panels
System Reference Guide
Access Authorization Panel
.
RM.S. - Access Authorization
Mantissa (C)opyright MCMXCII
Required:
User ID
Password
==>
==>
Optional:
New Password
Verify Password
==>
==>
CHAPTER 7: DISPLAY PRINT FACILITY
Program Function
Use
Caution
When
Changing
PF1=Help
PF3=End
Date: Monday,
10/07/96 Time: 17:11:15
SubSys: R134 Tran:
TermID: 002B ___
(( New and Verify Passwords ))
((
** Must Match **
))
Keys:
PF01 ==>
PF04 ==>
PF07 ==>
PF10 ==>
PF02
PF05
PF08
PF11
==>
==>
==>
==>
PF03
PF06
PF09
PF12
==>
==>
==>
==>
PF4=Return
Access Authorization Panel
The CICS transaction code and/or TSO option necessary to invoke RMS/Online is assigned by your installation. The
Access Authorization panel appears after entering this RMS/Online transaction identifier. Information entered on the
panel is used to establish the identity of the user. If security is used, the Password field is compared to either the
RMS/Online Password field in the User Master record or to the password in the installation security system for access
verification.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
The NEW and VERIFY passwords may be entered by the user to establish a new password if password verification is
used.
234
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
System Help Facilities
System User Panels
System Reference Guide
Primary Menu Panel
R.M.S. - Primary Menu
Access Group - IVSYSTEM
Date: Monday,
10/07/96 Time: 17:13:03
SubSys: R134 Tran:
TermID: 002B ___
Option ==>
Display/Print
Administration
Distribution(Implicit)
Sysout/Report
Security
Help Management
Tutorial
PF1=Help
PF3=End
-
Display/Print a Report in the RMS Database
Administration and Resource Control
Distribution Definition and Management
Sysout/Report Profile Management
Security Definition and Management
Help Management and Maintenance
Tutorial on System Capabilities/Facilities
PF4=Return
Primary Menu Panel
Depending on options selected during system installation, the Primary Menu may be presented immediately after the
Access Authorization panel. All major system functions are accessible from this panel. The available options are:
1. Display/Print
2. Administration
3. Distribution
4. Dataset Management
5. Security
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
6. Help Management
T. Tutorial
Select Option 1 to gain access to DISPLAY/PRINT.
© 2013 Mantissa Corporation. All rights reserved.
235
CHAPTER 7: DISPLAY PRINT FACILITY
1.
2.
3.
.4.
5.
6.
T.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
System Help Facilities
System User Panels
System Reference Guide
Display/Print Menu Panel
R.M.S. - Display/Print
Date: Monday,
10/07/96 Time: 17:15:48
SubSys: R134 Tran:
TermID: 002B ___
Option ==>
I.
V.
D.
T.
Index
Versions
Display
Tutorial
Access Group
Location
Report ID
Version Num
Media Type
CHAPTER 7: DISPLAY PRINT FACILITY
PF1=Help
-
==>
==>
==>
==>
==>
IVSYSTEM
CHICAGO
STOCK
Required
Required
Required for Options D,V
Optional - 0001 for -1
Optional - * or Media Type
SOFTCOPY
PF3=End
Index of Reports by Location
Versions List for a Specific Report
Display/Print a Report in the RMS Database
Tutorial on System Capabilities/Facilities
PF4=Return
Display/Print Menu Panel
The Display/Print Menu panel is accessed by selecting Option 1 on the Primary option menu. Available options
include:
I
V
D
T
Index
Versions
Display
Tutorial
The Index option (I or blank) displays an index of reports available for viewing by the user. Index is the default
option.
The Display option (D) causes the display of the contents of a report. If no version number is entered, the most recent
version is displayed (version 000). The next previous version will be displayed if 1 is entered in the Version field (the
current version added is considered the “0” version). For a report produced once a day, the report produced
yesterday is version 1, the previous day’s would be version 2, etc.
The System Tutorial option (T) causes the main Help option panel to be displayed.
FIELD REQUIREMENTS FOR EACH OPTION
(D)isplay
236
Access Group
Location Name
Report ID
Version (Optional, Default-000)
Media Name (Entry Ignored, Default-SOFTCOPY)
© 2013 Mantissa Corporation. All rights reserved.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
The Versions option (V) requires that the user select a Report name and a Location name. This option produces a
display of all versions of a particular report. The versions are listed by media type from most recent to oldest.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
System Help Facilities
System User Panels
System Reference Guide
FIELD REQUIREMENTS FOR EACH OPTION
(I)ndex
(V)ersions
Access Group
Location Name
Media Name (Optional, Default-SOFTCOPY)
*in the media field causes all medias to be displayed.
Access Group
Location Name
Report ID
Media Name (Optional, Default-SOFTCOPY)
Index Panel
10/07/96 Time: 17:17:02
Date____
10/03/96
10/03/96
10/01/96
Scroll ==> PAGE
Time____ JESID
09:49:30
148
09:49:30
148
09:35:08
303
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Index of Reports
Date: Monday,
Location: CHICAGO
( SOFTCOPY
)
Command ==>
ID ReportID Report Title_______________ Media_____
01 PROFIT
YEAR-TO-DATE SALES PROFITA
SOFTCOPY
02 VENACT
VENDOR ACTIVITY REPORT
SOFTCOPY
03 STOCK
YEAR/TO/DATE STOCK STATUS
SOFTCOPY
04
05
06
07
08
09
10
11
12
13
14
15
16
17
PF1=Help PF3=End PF4=Ret PF6=Refresh PF7=Bwd PF8=Fwd
RM9102I --- Bottom of data reached ---
Index Panel
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
This panel displays an alphabetical index of those reports available to a location.
The Version (V), Display (D) and Print (P) function may be invoked by entering the desired function in the command
field followed by the ID number of the desired report.
The user may scroll forward and backward in the index list until the desired report is located by using the Scroll Up/
Down PF keys.
Output definition requests (‘OV’ and ‘OR’) are submitted from the Index panel.
The ‘OV’ (Output Verification) command submits a verification of the Output Definition and will return a report
(PRINTVER) to the Access Group, and Location the User is in at the time the ‘OV’ request is issued. The report is
used to verify the presence of the requested reports on-line prior to submission of the Output Request.
The ‘OR’ (Output Request) command submits the Output Definition, and routes the requested packet based on the
information contained in panels 4 & 5 of the output definition.
The format of the commands are as follows:
© 2013 Mantissa Corporation. All rights reserved.
237
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
System Help Facilities
System User Panels
System Reference Guide
OV profname <ENTER>
(where ‘profname’ is equal to your Output definition profile name)
OR profname <ENTER>
(where ‘profname’ is equal to your Output definition profile name)
Versions Panel
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Versions of a
Location: CHICAGO
Command ==>
ID Date____ Time____
01 10/03/96 09:49:30
02 10/01/96 09:45:29
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
PF1=Help
RM9102I
Report
Date: Monday,
Report: PROFIT
10/07/96 Time: 17:18:57
Media: SOFTCOPY
Scroll ==> PAGE
Name_____Number Vers Status__ Pages__ Lines___ JES__Name
INR02
468
0 ........
2
46 OO1134
INR02
338
1 ........
2
46 OO1134
PF3=End PF4=Ret PF6=Refresh PF7=Bwd PF8=Fwd
--- Bottom of data reached ---
Versions Panel
This panel displays version information for a selected report. The report versions are listed from the most recent to
oldest. Scroll capabilities permit the user to locate the desired version of a report. The Display (D), Print (P), Output
(O), Recovery (R), and Cancel (C) report functions may be invoked by entering the desired function followed by the
ID number of the selected report. Entering “D 1” or “S 1” in the Command field would display the report version on
line “01” of the versions panel. The Version panel shows the Location name, the Report ID, number of lines and
pages, the date and time the report was processed, repository number, and the name of the JOB that created the report.
POSITION
238
CHARACTER
DEFINITION
1.
D
Report has been deleted from the repository but is eligible for
recovery.
2.
+
Report appended (added to) during the distribution process.
3.
A
Dataset was retention-base archived.
3
N
Dataset was not a candidate for retention-based archive processing.
4.
B
Base Dataset
5.
X
Data object severed.
5.
P
Protected base dataset at the time of last RM90007 backup.
© 2013 Mantissa Corporation. All rights reserved.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
There are 8 Status positions defined as follows:
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
System Help Facilities
System User Panels
System Reference Guide
6.
R
This dataset was reloaded (recovered) to viewing status
7.
O
Output attributes reside with version record.
8.
D
Delete of dataset is pending.
------------------- W1
-----------------------------------------------| LOCATION: CHICAGO
REPORT: PROFIT
>
< P:
1 L:
1
| COMMAND ==> OW
SCROLL ==> FULL
|
-- START OF DATA --- START OF DATA --- START OF DATA -|
-- TOP OF PAGE --- TOP OF PAGE --- TOP OF PAGE -|
CLIENT 002
YEAR-TO-DATE SALES PROFITABILITY REPORT
|
11 AM
Y
COST
AVG COST
% COST
SALES
|
A10001
13
546.00
42.00
40.38
406.00
|
A10001
12
566.00
44.00
50.38
706.00
|
A10001
11
586.00
46.00
60.38
906.00
|
A10001
10
596.00
48.00
80.38
306.00
|
A10006
13
546.00
42.00
40.38
406.00
------------------- W2
-----------------------------------------------| LOCATION: CHICAGO
REPORT: STOCK
>
< P:
1 L:
1
| COMMAND ==>
SCROLL ==> FULL
|
-- START OF DATA --- START OF DATA --- START OF DATA -|
-- TOP OF PAGE --- TOP OF PAGE --- TOP OF PAGE -|
CHICAGO
YEAR-TO-DATE STOCK STATUS REPORT
|
ITEM
NO. RECEIPTS
SALES
TRANSFRS
ADJTS
PHY IN
| 10001
0
40
11
0
158
3
| 10002
0
38
12
0
160
4
| 10004
0
36
13
0
162
5
| 10005
0
34
14
0
164
6
| 10006
0
80
23
0
231
13
Display Panel
This panel is used to display the content of one or more reports. Once a report is displayed, various commands may
be used to customize the presentation of the report(s) to fit individual needs.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
You communicate with the display facility by a combination of PF key depressions and commands entered in the
COMMAND ==> field at the top of the panel.
In the following command description, brackets (“[“and “]”) are used for notation only and should not be entered
with command data. When used in the description of command options, these brackets indicate that one or more
fields may be entered with a command. The vertical bar “|” indicates that one of the listed options may be entered
with a command.
You will notice that with many of the commands, the same command is used to activate and deactivate the option. For
instance, a scale line (a line that provides a visual marker for report lines) may be added and removed by typing
(S)CALE into the command area of the panel.
LONG FORM
SHORT FORM
.A....A
*ADMIN CONTACT INFO
*ADMIN FORMAT
DELETE
© 2013 Mantissa Corporation. All rights reserved.
AD
AFD
USAGE
Note the current display location.
Note ID must begin with a period.
Display administrator contact information.
Administrative Format Delete
239
CHAPTER 7: DISPLAY PRINT FACILITY
Display Panel
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
Command Description
System User Panels
System Reference Guide
LONG FORM
*ADMIN FORMAT
RETRIEVE
*ADMIN FORMAT SAVE
ANOTE
CLOSEW
*COLUMN SELECT
FIND
*FORMAT DELETE
*FORMAT RETRIEVE
*FORMAT SAVE
HEADER
LEFT
LOCATE
CHAPTER 7: DISPLAY PRINT FACILITY
OPENR
OPENW
PF
*PRINT END
*PRINT START
REPORTI
RESET
RIGHT
SCALE
*SEARCH RANGE
*WINDOW SET
=X
ZOOM
SHORT FORM
USAGE
AFR
Administrative Format Retrieve
AFS
AN
CW
CS
Administrative Format Save
F
FD
FR
FS
H
LE
L
OR
OW
PF
PE
PS
RI
RS
RT
S
SR
WS
X
Z
Attach a note to line
Close the current window
Specify columns and order of data to
be displayed
Find a character string
Delete a viewing format set
Retrieve a viewing format set
Save a viewing format set
Select header hold lines
Shift display left
Locate a specific line number or
previously noted location
Open an additional report
Open an additional viewing window
Display the default PF key usage
End the selection of a range of pages
Start the selection of a range of start pages
Display report information for current report
Reset the viewing options
Shift display right
Place a ruler line at the top of the display
Set search range for FIND command
Select a window set for report display
Exit RMS/Online
Changes current window from window size to
full screen and vice-versa
* Short form only
COMMAND DESCRIPTION
Label the current location. A period (“.”) followed by up to 7
characters is used to identify the current page location. The
labeled location may be retrieved for viewing by entering the
assigned label as the operand on a LOCATE (L) command.
AD
Entering AD in the COMMAND ==> field of the display will
cause the administrator name and phone number to be displayed. This may be useful if you are having problems you feel
240
© 2013 Mantissa Corporation. All rights reserved.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
A....A
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
Command Description
System User Panels
System Reference Guide
the administrator may help you resolve. This command causes
part of the window being displayed to be overlaid. You may
restore the viewing panel(s) by pressing PF3.
ADMIN FORMAT DELETE U....U
AFD
The Administrative Format Delete command is used to remove
a secured viewing format set previously added by the Administrative Format Save command. U....U is the name of the user to
which the secured format applies. The administrator must be
viewing the report to which the format applies (same Access
Group/Location ID) in order to delete the format record.
ADMIN FORMAT RETRIEVE U....U
The Administrative Format Retrieve command enables a system administrator to retrieve viewing format information previously saved using the Administrative Format Save (AFS)
command. U....U is the name of the user to which the secured
format applies.
ADMIN FORMAT SAVE U....U
AFS
The Administrative Format Save (AFS) command provides a
convenient method of restricting access by a specific user to
selected columns of a report. The same attributes saved by the
Format Save command are also retained by the AFS command.
The difference is that the selected columns may not be reset by
the user. U....U is the user identification to which the secured
format will apply.
ANOTE [NNNNNNN]
AN
The ANOTE command is used to attach a “sticky note” to a
specific line [nnnnnn] of a report. The notes may be accessed
during the viewing session by entering LNOTE (LN).
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
CLOSEW
CW
Close the current window. The panel area previously occupied
by the window is erased and the current window is changed to
the next active window.
COLUMN SELECT [x,y......]
CS
The COLUMN SELECT command is used to select and reorganize the columns of a report to make the content of that
report more usable to the viewer. Columns may be selected in
any order and columns selected by one x,y pair may overlap
© 2013 Mantissa Corporation. All rights reserved.
241
CHAPTER 7: DISPLAY PRINT FACILITY
AFR
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
Command Description
System User Panels
System Reference Guide
those selected by another select pair. The only requirement is
that x be less than or equal to y in each x,y pair, and that neither
value be less than 1 or greater than 240.
In order to select columns 1 through 10 and 20 through 40 for
viewing, the following CS command would be entered:
CS 1,10 20,40Since there is no restriction with regard to column order, we
could view the same columns in reverse order by entering:
CS 20,40 1,10Columns may be reset by entering CS with no x,y pairs.
FIND ‘STRING’ | * [NEXT | PREV | FIRST | LAST]
F
The FIND command is used to locate a character string (word
or phrase) in the report being viewed. The search will commence at the top of the screen, either forward (down) or back
(up). The FIND operands are:
CHAPTER 7: DISPLAY PRINT FACILITY
STRING
is the word or phrase to be located. If the word or phrase contains one of the following characters / ‘$- #, it should be
enclosed in quotes.
*
causes the character string last entered to be used as the object
of the current command.
NEXT
causes the next occurrence of the character string to be
located. (N)ext is the default.
PREV
causes the previous occurrence of the character string to be
located.
FIRST
causes the first occurrence of the character string to be located.
LAST
causes the last occurrence of the character string to be located.
FORMAT DELETE A.....A
FD
The FORMAT DELETE command is used to remove a format
set previously added by a FORMAT SAVE command.
FORMAT RETRIEVE [A.....A]
The FORMAT RETRIEVE command enables a user to retrieve
viewing format information previously saved using the FORMAT SAVE (FS) command. A.....A is the name of the format
set (up to 10 characters) to be retrieved. If A.....A is omitted,
the DEFAULT format set is retrieved.
FORMAT SAVE A.....A
FS
The FORMAT SAVE command provides a convenient method
of saving viewing format information. The following values
are retained for subsequent viewing operations using the
242
© 2013 Mantissa Corporation. All rights reserved.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
FR
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
Command Description
System User Panels
System Reference Guide
retrieved format: SCALE, HEADER HOLD, SCROLL
VALUE, ACTIVE COLUMN SELECTION,.A.....A is the
name under which the format is stored for subsequent retrieval
by the FORMAT RETRIEVE (FR) command. Multiple formats may be saved for the same report. If DEFAULT is specified or the A.....A is omitted, the format is automatically
retrieved at the time the report is accessed by the user. It should
be noted that format records are stored by user permitting multiple users to establish and control their unique viewing
requirements for the same report.
HEADER [N]
H
Heading lines may be removed by entering H with no operand.
LNOTE [NNNNNN]
LN
The LNOTE (List Notes) command is used to list the notes
attached to specific lines or a report. The list will begin with
notes attached to lines greater than or equal to [nnnnnn].
LEFT [nnn]
LE
The LEFT command is used to position the viewing window
NNN position to the left in the current display image.
LOCATE .A....A | NNNN
L
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
The LOCATE command is used to position a report to a previously labeled viewing position or to a specific line or page. If
the SCROLL ==> value is HALF, FULL OR NNNN, positioning is to the specified line. If the scroll value is PAGE, positioning is to the specified page.
.A....A is a label previous assigned.
NNNN is a report line number or page number.
OPENR
OR
Open a report. After the open window command is entered, a
report selection sub-panel is presented in the current window.
Information entered in this sub-panel determines which report
will be retrieved for viewing in the new window. Once multiple
reports are opened, the PF4 key may be used to switch between
open reports.
© 2013 Mantissa Corporation. All rights reserved.
243
CHAPTER 7: DISPLAY PRINT FACILITY
The HEADER command is used to request that up to 21 lines
of header data be held at the top of the scroll page. The held
header lines are highlighted for subsequent scroll operations.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
Command Description
System User Panels
System Reference Guide
OPENW
OW
Open a window. After the open report command is entered, a
report selection sub-panel is presented in the newly created
window. Information entered in this sub-panel determines
which report will be retrieved. Once multiple windows are
opened, the PF9 key is used to switch windows.
PF
This command displays the default PF key settings for RMS/
Online. Depress END when you have reviewed these settings.
Your display will be restored to its original viewing location.
PRINT END
PE
CHAPTER 7: DISPLAY PRINT FACILITY
The PRINT END command is used to indicate the end of a
range of pages selected for printing.
PRINT START
PS
The PRINT START command designates the beginning page
of a page range to be printed.
REPORTI
RI
The report information command displays extended information on the report being viewed.
RESET
RS
Reset the viewing options. Column selection is removed. The
scale line (if any) is removed. Header hold line is set to zero.
RIGHT [NNN]
RT
SCALE
S
The SCALE command adds or deletes the ruler line to/from the
current display. The ruler lines serves as a horizontal visual reference while viewing a report. It looks like this:
....+...10....+...20....+...30....+...40....+...50....+...
60....+...70....+...80
SEARCH RANGE [NNNNNNNN]
SR
244
© 2013 Mantissa Corporation. All rights reserved.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
The RIGHT command is used to position the viewing window
NNN position to the right in the current display image.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
Line Positioning/Scroll Operations
System User Panels
System Reference Guide
99,999,999 may be entered. If the number of lines is omitted,
the default search range (5,000) is assumed.
WINDOW SET [NNNN]
WS
The WINDOW SET command is used to select a window set
which will divide the panel into viewing areas. Available window sets are:
H3
Q4
V2
Horizontal aspect window set.
Each window occupies one-half of the panel area.
Horizontal aspect window set.
Each window set occupies one-third of the panel area.
Horizontal aspect window set.
Each window set occupies one-fourth of the panel area.
Vertical aspect window set.
Each window set occupies one-half of the panel area.
Entering “WS” with no set name causes the full screen (default) to be selected.
LINE POSITIONING/SCROLL OPERATIONS
RMS/DPF accepts four scroll values. One of the following may be entered after using the Tab key
=>| to advance to the SCROLL ==> field.
H(ALF)
Scroll half the depth of the current window.
F(ULL)
Scroll the depth of the current window.
NNNN
Scroll NNNN lines.
P(AGE)
A scroll value of page positions from the current viewing page
to the next/previous report page.
The scroll value may be overridden by entering a number in the command line before depressing the scroll PF keys.
If RMS/DPF receives a number in the command line while the scroll value is HALF, FULL, OR NNNN, the number
entered is interpreted as the number of lines to scroll. If the scroll value is PAGE when a value is entered, the system
scrolls this many pages.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
Entering the letter “M” (maximum) and depressing a scroll key will cause the system to scroll to the top or bottom of
the dataset, depending on which PF key is depressed.
When M(aximum) is entered and the scroll left/right key is depressed, the viewing window is positioned as far to the
maximum right or left position of the viewing data as possible.
© 2013 Mantissa Corporation. All rights reserved.
245
CHAPTER 7: DISPLAY PRINT FACILITY
H2
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
System User Panels
System Reference Guide
Recover / Print Panel
R.M.S. - Recover / Print
Location: CHICAGO
Option ==>
Date: Wednesday, 08/26/98 Time: 15:52:47
Report: STOCK
Date/Time: 120490 033407
(R)- Recover (P) - Print
(L) - Get Loc Attributes
CHAPTER 7: DISPLAY PRINT FACILITY
____________________________ Output Attributes _______________________________
Class
==>
Burst ==>
OLmt ==>
Form
==>
Fls/CC ==>
:
UCS ==>
:
FCB:A/V
==>
:
OPTCD ==>
PWD ==>
Dest
==>
Node
==>
Seps ==>
Desk/EWN ==>
Modify ==>
:
JCLm ==>
PageDEF
==>
Char1 ==>
Disp ==>
FormDef
==>
Char2 ==>
BLK ==>
LRECL
==>
Char3 ==>
Pri ==>
Copies
==>
Char4 ==>
DDNM ==>
Name
==>
Title
==>
Dept/XPRO ==>
Building ==>
Room
==>
Addr 1
==>
Addr 2
==>
Addr 3
==>
Addr 4
==>
PF1=Help PF3=End PF4=Return
Recover / Print Panel
The Recover/Print panel is presented if the system Print, Output, or Recover option was selected on the Versions
panel, or pages were selected during a viewing operation. Address/message data and physical print characteristics
may be entered on the screen. Default address data is taken from the User Master and default print characteristics are
taken from those print characteristics assigned when the report was distributed.
Print characteristics may be retrieved from the Location Master by typing “L” and ENTER.
To submit the Print Request, type ‘P’ in the Option==> field and depress <ENTER>.
To submit the Recovery Request, type ‘R’ in the Option==> field and depress <ENTER>.
The Note Pad feature allows users to attach ‘sticky notes’ at the report line level to reports in softcopy. The note pad
allows for up to two (2) pages of text to be entered for each line of the report.
In RMS Release 11.34 notes processing has been enhanced to ensure note pad entries are maintained properly within
the RMS Online system. Highlighted below are the features and functionality of the note pad facility.
246
•
The Userid of the user adding the Note to the report is tracked for audit purposes and is shown on the ‘LN’ (list
note) results.
•
Notes that have been added to reports are backed up and restored when normal file maintenance (RM90007/
RM90008) is performed.
© 2013 Mantissa Corporation. All rights reserved.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
RMS NOTE PAD FACILITY
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
System User Panels
System Reference Guide
•
Notes are deleted from the QXACDS VSAM file only after the Run Tracking record for the distribution job has
been deleted and a PARTIAL, PARTIALCLEAR or PARTIALSYNC restore (RM90008) has been performed.
•
All RMS Online users have the ability to add notes (AN) and list notes (LN).
•
Access to note pad commands allowing changes (CN), deletions (DN), or inquiries (IN) are controlled via the
security profile portion of the user master record in conjunction with the associated resource security entries.
•
Notes that are added to reports governed by a group archive follow the report throughout its’ life in the Online (in
both viewable and tracking statuses). This affords users the ability to have the ‘original notes’ for a report
reloaded if a request is issued to reload a report that is being tracked.
•
Once reloaded, additional notes can be added to the reloaded version of the report.
Note Pad Panel
Date: Monday,
10/07/96 Time: 17:27:07
AG/Loc/Rid - IVSYSTEM CHICAGO
VENACT
DS Nm/Dt/Time - INR01
100296 172043 00000437
Attached to Line => 00000005 Title - VENDOR ACTIVITY REPORT
> EXAMPLE: NOTE
>
> THIS IS AN EXAMPLE OF THE POSSIBLE USE OF THE RMS NOTE PAD FACILITY. THE
> FIRST LINE OF THE NOTE IS DISPLAYED AS A SHORT FORM REMINDER OF THE CONTENT
> OF THE NOTE WHEN THE LIST NOTE FACILITY IS USED TO SHOW THE NOTES ASSOCIATED
> WITH THE REPORT BEING VIEWED.
>
>
>
>
>
>
>
>
>
>
>
>
Panel 1 of 2
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
RM9134I Enter information for new record.
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Sticky Note
Mode: ADD
© 2013 Mantissa Corporation. All rights reserved.
247
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
RMS Security for Note pad access
System Reference Guide
RMS Security for Note pad access
The following panels outline the steps to follow to ensure security has been set up properly to allow Online users to
use the note pad facility. A brief explanation follows each panel.
R.M.S. - User Master
Mode: INQUIRE
User ID
Def. Access GP
Def. Location
User Name
Phone Number
Address Line 1
Line 2
Line 3
Line 4
DS Print JCL
Date: Tuesday,
03/21/00 Time: 16:33:18
________________________________________
==>
==>
==>
==>
==>
==>
==>
==>
==>
==>
PF1=Help
RM9020I
PF3=End PF4=Ret PF7=Bwd
Enter record identifier.
PF8=Fwd
NOTE01
User Type
JCL ==> SPRINT
*****
S ACC-GRP
SECUR-GP
P
ENTER=Update/I
==>
RT S
Panel 1 of 2
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 7: DISPLAY PRINT FACILITY
ACC-GRP
MANTISSA
NOTE01
Template User ==>
MANTISSA
User Password ==>
AREA01
USER FOR NOTE PAD TESTING
205-402-0280
MANTISSA CORPORATION
CUSTOMER SUPPORT TEAM
2200 VALLEYDALE ROAD
BIRMINGHAM, AL 35244-2011
DPRINT
SELPrint
***** Security Profile
SECUR-GP RT S ACC GRP
SECUR-GP RT
NOTEUSER DP P MANTISSA NOTEUSER LR
248
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
RMS Security for Note pad access
System Reference Guide
The Security Profile area of the User Master record defines which resource security records to reference to govern the
activity of the user while viewing softcopy reports. Only one (1) set of ‘DP’ transactions is defined for each user.
Multiple entries are allowed to provide access to all of the online locations and reports the user can access. These
entries along with the corresponding resource security records ensure users access only the locations and reports
defined for their use.
Access Group
==>
Security Group ==>
MANTISSA
NOTEUSER
ADD SOFTCOPY/DPF TX
PF3=End
PF4=Ret
Permit/Deny Access
==>
PF7=Bwd
==> P
Resource
********
CN
D
DN
I
IN
P
PS
SR
V
________
________
________
PF8=Fwd
TOP
BOT
ENTER=Update/I
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
PF1=Help
Date: Wednesday, 03/22/00 Time: 16:07:43
----------------------------------------
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Resource Security Maint.
Mode: ADD
© 2013 Mantissa Corporation. All rights reserved.
249
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
RMS Security for Note pad access
System Reference Guide
The Resource Security panel above governs the Display Print transactions available to the user. This record
corresponds with the information entered in the Security Profile area of the User Master record. The user is permitted
to perform any of the ‘DP’ transactions in the resource list.
R.M.S. - Resource Security Maint.
Mode: ADD
Access Group
==>
Security Group ==>
MANTISSA
NOTEUSER
ADD REPORT IDENTIFIER
CHAPTER 7: DISPLAY PRINT FACILITY
PF1=Help
PF3=End
PF4=Ret
Date: Wednesday, 03/22/00 Time: 16:34:30
----------------------------------------
LOCATION IDENTIFIER
Permit/Deny Access
==> NOSALES
PF7=Bwd
PF8=Fwd
==> AREA01
==> P
Resource
********
MYSALES
NOSALES
________
________
________
________
________
________
________
________
________
________
TOP
BOT
ENTER=Update/I
The Resource Security panel above governs the Reports available to the user within the access group and location
specified. This record corresponds with information entered in the Security Profile area of the User Master record.
The user is permitted to perform any of their display print transactions for all of the reports permitted in the resource
list.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
If you have a user who has access to all reports within a given location, it is more efficient to use the Deny option and
deny a Report ID that does not exist, for example, DUMMY. By design, if you deny access to a specific Report ID,
you imply access to all other reports within the location.
250
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage Step by Step
System Reference Guide
Note pad Usage Step by Step
The following panels outline the steps to follow to use the note pad facility. Each command is explained in detail.
R.M.S. - Display/Print
Date: Thursday, 03/23/00 Time: 13:48:15
SubSys: C134 Tran: HOL1 TermID: CP06 ___
Option ==> I
Index
Versions
Display
Tutorial
Access Group
Location
Report ID
Version Num
Media Type
PF1=Help
-
==> MANTISSA
==> AREA01
==>
==>
==>
PF3=End
Index of Reports by Location
Versions List for a Specific Report
Display/Print a Report in the RMS Database
Tutorial on System Capabilities/Facilities
Required
Required
Required for Options D,V
Optional - 0001 for -1
Optional - * or Media Type
PF4=Return
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
The Display Print menu is presented upon sign-on to RMS Online via the RM01 (or equivalent) transaction. The
access group and location are set to the default values defined in the user master record. These values represent the
access group and location most often referenced by the user. If the user is permitted via resource security to access
other Access groups and Locations, they can modify the fields to the desired values.
© 2013 Mantissa Corporation. All rights reserved.
251
CHAPTER 7: DISPLAY PRINT FACILITY
I.
V.
D.
T.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage Step by Step
System Reference Guide
Option ‘I’ will produce an index list.
R.M.S. - Index of Reports
Date: Thursday,
Location: AREA01
( SOFTCOPY
)
Command ==>
ID ReportID Report Title_______________ Media_____
01 MYSALES
MONTHLY MYSALES
SOFTCOPY
02 NOSALES
YEARLY NOSALES
SOFTCOPY
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
CHAPTER 7: DISPLAY PRINT FACILITY
PF1=Help
RM9102I
03/23/00 Time: 13:49:58
Date____
03/23/00
03/23/00
Scroll ==> PAGE
Time____ JESID
13:25:46
199
13:25:46
199
PF3=End PF4=Ret PF6=Refresh PF7=Bwd PF8=Fwd
--- Bottom of data reached ---
Option ‘I’ produces a list of all reports the user is entitled to view within the location specified. Access to reports is
governed by RMS Online Security components.
PF1=Help
RM9102I
252
03/23/00 Time: 13:49:58
Date____
03/23/00
03/23/00
Scroll ==> PAGE
Time____ JESID
13:25:46
199
13:25:46
199
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
R.M.S. - Index of Reports
Date: Thursday,
Location: AREA01
( SOFTCOPY
)
Command ==> v1
ID ReportID Report Title_______________ Media_____
01 MYSALES
MONTHLY MYSALES
SOFTCOPY
02 NOSALES
YEARLY NOSALES
SOFTCOPY
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
PF3=End PF4=Ret PF6=Refresh PF7=Bwd PF8=Fwd
--- Bottom of data reached ---
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage Step by Step
System Reference Guide
The ‘Vn’ command (where ‘n’ is the ID of the report) will provide a list that contains all of the versions of the
requested report within the specified location. The ‘Vn’ command can be entered on the command line, or you can
overtype the selection in the ID column.
PF1=Help
RM9102I
Report
Date: Thursday,
Report: MYSALES
Name_____Number Vers Status__
MCHOLLER
609
0 ..A...O.
MCHOLLER
554
1 ..A...O.
MCHOLLER
501
2 ..A...O.
MCHOLLER
445
3 ..A...O.
MCHOLLER
199
4 ..A...O.
MCHOLLER
145
5 ..A...O.
MCHOLLER
57
6 ..A...O.
MCHOLLER
41
7 ......O.
MCHOLLER
26
8 ......O.
03/23/00 Time: 14:03:00
Media: SOFTCOPY
Scroll ==> PAGE
Pages__ Lines___ JES__Name
6
150 P390CGNR
6
150 P390CGNR
6
150 P390CGNR
6
150 P390CGNR
6
150 P390CGNR
6
150 P390CGNR
6
150 P390CGNR
6
150 P390CGNR
6
150 P390CGNR
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Versions of a
Location: AREA01
Command ==>
ID Date____ Time____
01 03/23/00 13:25:46
02 03/23/00 13:23:57
03 03/23/00 13:17:52
04 03/23/00 13:15:05
05 03/16/00 15:02:37
06 03/16/00 15:01:48
07 03/16/00 14:36:44
08 03/16/00 11:01:20
09 03/16/00 10:39:28
10
11
12
13
14
15
16
17
PF3=End PF4=Ret PF6=Refresh PF7=Bwd PF8=Fwd
--- Bottom of data reached ---
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
The panel above is a complete version listing for the report requested.
R.M.S. - Versions of a Report
Date: Thursday, 03/23/00 Time: 14:03:00
Location: AREA01
Report: MYSALES
Media: SOFTCOPY
Command ==> d1
Scroll ==> PAGE
ID Date____ Time____ Name_____Number Vers Status__ Pages__ Lines___ JES__Name
01 03/23/00 13:25:46 MCHOLLER
609
0 ..A...O.
6
150 P390CGNR
02 03/23/00 13:23:57 MCHOLLER
554
1 ..A...O.
6
150 P390CGNR
03 03/23/00 13:17:52 MCHOLLER
501
2 ..A...O.
6
150 P390CGNR
04 03/23/00 13:15:05 MCHOLLER
445
3 ..A...O.
6
150 P390CGNR
05 03/16/00 15:02:37 MCHOLLER
199
4 ..A...O.
6
150 P390CGNR
06 03/16/00 15:01:48 MCHOLLER
145
5 ..A...O.
6
150 P390CGNR
07 03/16/00 14:36:44 MCHOLLER
57
6 ..A...O.
6
150 P390CGNR
08 03/16/00 11:01:20 MCHOLLER
41
7 ......O.
6
150 P390CGNR
09 03/16/00 10:39:28 MCHOLLER
26
8 ......O.
6
150 P390CGNR
10
11
12
13
14
15
16
17
PF1=Help
RM9102I
PF3=End PF4=Ret PF6=Refresh PF7=Bwd PF8=Fwd
--- Bottom of data reached ---
© 2013 Mantissa Corporation. All rights reserved.
253
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage Step by Step
RMS/Online® Version 11.35
System Reference Guide
The ‘Dn’ command (where ‘n’ is the ID of the report to be viewed) will open the requested report for viewing through
RMS Online. The ‘Dn’ command can be entered on the command line, or you can overtype the selection in the ID
column.
CHAPTER 7: DISPLAY PRINT FACILITY
LOCATION: AREA01
REPORT: MYSALES >
< P:
1 L:
1
COMMAND ==>
SCROLL ==> FULL
___Start of Data___
___Start of Data___
___Start of Data___
___St
____Top of Page____
____Top of Page____
____Top of Page____
____T
CALIFORNIA STATE DISTRIBUTORS
PAGE 1 00010002
MONTHLY MYSALES REPORT
02/19/92 00020002
AREA 01
FOR YEAR ENDED OCTOBER 31, 1996
00030002
00040002
REGULAR
BONUS
TOTAL
00050002
SALESMAN
SALESMAN
COMMISSION
COMMISSION
COMMISSION
00060002
15896
TIM C EVANS
$800.00
$3.28
$803.28
00070002
23960
ROGER D SMITH
$4,314.69
$4,314.69
00080002
98111
DON E LEFTY
$1,000.00
$1,000.00
00090002
54543
GEORGE I IMAY
$2,400.00
$2,400.00
00100002
70599
EDGAR P ALLEN
$750.00
$750.00
00110002
47783
JEFFRY A TALMAN
$732.28
$732.28
00120002
39756
PAUL M VOUGHT
$2,000.00
$2,000.00
00130002
23456
DAVID GRAY
$5,000.00
$5,000.00
00140002
00001
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00150002
00002
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00160002
00003
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00170002
00004
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00180002
00005
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00190002
00006
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00200002
LOCATION: AREA01
REPORT: MYSALES >
< P:
1 L:
1
COMMAND ==> AN 1
SCROLL ==> FULL
___Start of Data___
___Start of Data___
___Start of Data___
___St
____Top of Page____
____Top of Page____
____Top of Page____
____T
CALIFORNIA STATE DISTRIBUTORS
PAGE 1 00010002
MONTHLY MYSALES REPORT
02/19/92 00020002
AREA 01
FOR YEAR ENDED OCTOBER 31, 1996
00030002
00040002
REGULAR
BONUS
TOTAL
00050002
SALESMAN
SALESMAN
COMMISSION
COMMISSION
COMMISSION
00060002
15896
TIM C EVANS
$800.00
$3.28
$803.28
00070002
23960
ROGER D SMITH
$4,314.69
$4,314.69
00080002
98111
DON E LEFTY
$1,000.00
$1,000.00
00090002
54543
GEORGE I IMAY
$2,400.00
$2,400.00
00100002
70599
EDGAR P ALLEN
$750.00
$750.00
00110002
47783
JEFFRY A TALMAN
$732.28
$732.28
00120002
39756
PAUL M VOUGHT
$2,000.00
$2,000.00
00130002
23456
DAVID GRAY
$5,000.00
$5,000.00
00140002
00001
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00150002
00002
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00160002
00003
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00170002
00004
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00180002
00005
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00190002
00006
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00200002
254
© 2013 Mantissa Corporation. All rights reserved.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
Display of the requested report.
RMS/Online® Version 11.35
System Reference Guide
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage Step by Step
The ‘AN n’ command allows you to attach your ‘Sticky Note’ to the line number specified in the ‘n’ value. The
following panel is returned once you press <enter> to process your command.
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Sticky Note
Date: Thursday, 03/23/00 Time: 14:16:24
Mode: ADD
AG/Loc/Rid - MANTISSA AREA01
MYSALES
Dataset Nm/Dt/Time/Num - MCHOLLER 031600 103656 00000022
Distributed Dt/Time/Num - 032300
132546 16773387
Line => 00000001 032300 141624 Title - MONTHLY MYSALES
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
Panel 1 of 2
RM9134I Enter information for new record.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
The line number on which the note is to be added is in the heading for the note record. Other relative information
about the report is included for reference purposes.
© 2013 Mantissa Corporation. All rights reserved.
255
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage Step by Step
RMS/Online® Version 11.35
System Reference Guide
Each line of the report can contain up to two (2) pages of text.
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Sticky Note
Date: Thursday, 03/23/00 Time: 14:16:24
Mode: ADD
AG/Loc/Rid - MANTISSA AREA01
MYSALES
Dataset Nm/Dt/Time/Num - MCHOLLER 031600 103656 00000022
Distributed Dt/Time/Num - 032300
132546 16773387
Line => 00000001 032300 141624 Title - MONTHLY MYSALES
> text added to line one of the report titled mysales.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
Panel 1 of 2
RM9134I Enter information for new record.
LOCATION: AREA01
REPORT: MYSALES >
< P:
1 L:
1
COMMAND ==> AN 1
SCROLL ==> FULL
RM9028I Addition successful. Enter information for next record.
___Start of Data___
___Start of Data___
___Start of Data___
___St
____Top of Page____
____Top of Page____
____Top of Page____
____T
CALIFORNIA STATE DISTRIBUTORS
PAGE 1 00010002
MONTHLY MYSALES REPORT
02/19/92 00020002
AREA 01
FOR YEAR ENDED OCTOBER 31, 1996
00030002
00040002
REGULAR
BONUS
TOTAL
00050002
SALESMAN
SALESMAN
COMMISSION
COMMISSION
COMMISSION
00060002
15896
TIM C EVANS
$800.00
$3.28
$803.28
00070002
23960
ROGER D SMITH
$4,314.69
$4,314.69
00080002
98111
DON E LEFTY
$1,000.00
$1,000.00
00090002
54543
GEORGE I IMAY
$2,400.00
$2,400.00
00100002
70599
EDGAR P ALLEN
$750.00
$750.00
00110002
47783
JEFFRY A TALMAN
$732.28
$732.28
00120002
39756
PAUL M VOUGHT
$2,000.00
$2,000.00
00130002
23456
DAVID GRAY
$5,000.00
$5,000.00
00140002
00001
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00150002
00002
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00160002
00003
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00170002
00004
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00180002
00005
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00190002
256
© 2013 Mantissa Corporation. All rights reserved.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
Screen shows initial text for the note attached to line one of the MYSALES report. The note is only attached to the
version of the MYSALES report referenced by the Distributed Date/Time/Number field.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage Step by Step
System Reference Guide
LOCATION: AREA01
REPORT: MYSALES >
< P:
1 L:
1
COMMAND ==> ln
SCROLL ==> FULL
___Start of Data___
___Start of Data___
___Start of Data___
___St
____Top of Page____
____Top of Page____
____Top of Page____
____T
CALIFORNIA STATE DISTRIBUTORS
PAGE 1 00010002
MONTHLY MYSALES REPORT
02/19/92 00020002
AREA 01
FOR YEAR ENDED OCTOBER 31, 1996
00030002
00040002
REGULAR
BONUS
TOTAL
00050002
SALESMAN
SALESMAN
COMMISSION
COMMISSION
COMMISSION
00060002
15896
TIM C EVANS
$800.00
$3.28
$803.28
00070002
23960
ROGER D SMITH
$4,314.69
$4,314.69
00080002
98111
DON E LEFTY
$1,000.00
$1,000.00
00090002
54543
GEORGE I IMAY
$2,400.00
$2,400.00
00100002
70599
EDGAR P ALLEN
$750.00
$750.00
00110002
47783
JEFFRY A TALMAN
$732.28
$732.28
00120002
39756
PAUL M VOUGHT
$2,000.00
$2,000.00
00130002
23456
DAVID GRAY
$5,000.00
$5,000.00
00140002
00001
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00150002
00002
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00160002
00003
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00170002
00004
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00180002
00005
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00190002
00006
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00200002
The ‘LN’ (list note) command produces a listing of all of the ‘sticky notes’ that have been added to the report being
viewed. To generate the list, key ‘LN’ on the command line and press <enter>.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
Note(s) listing by Report
Command ==>
ID
-01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
Noteline
Number__
00000003
00000002
00000001
PF1=Help
RM9101I
Entry
Date_______________
Wednesday, 04/19/00
Wednesday, 04/19/00
Wednesday, 04/19/00
Date: Wednesday, 04/19/00 Time: 10:56:35
Scroll ==> PAGE
Entry
Time____
10:54:40
10:50:08
10:49:41
User
ID______
P390C
P390C
P390C
PF3=End PF4=Ret PF7=Bwd PF8=Fwd
--- Top of data reached ---
© 2013 Mantissa Corporation. All rights reserved.
Note
Line
NOTE
NOTE
NOTE
PF10=Left
1____________________
ADDED TO LINE THREE T
ADDED TO LINE TWO TO
ADDED TO LINE ONE TO
PF11=Right
257
CHAPTER 7: DISPLAY PRINT FACILITY
Once you have entered the desired text on the ‘Sticky Note’ panel and press <enter>, the RM9028I message will
appear. The message indicates the note has been added successfully.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage Step by Step
System Reference Guide
The Notes list generated from the ‘LN’ command shows all line numbers of the report that have a ‘sticky note’
attached to them. The list presented is in descending order by line number.
The list panel is used to inquire (IN), change (CN) or delete (DN) notes.
Note(s) listing by Report
Command ==> i2
CHAPTER 7: DISPLAY PRINT FACILITY
ID
-01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
Noteline
Number__
00000003
00000002
00000001
PF1=Help
RM9101I
Entry
Date_______________
Wednesday, 04/19/00
Wednesday, 04/19/00
Wednesday, 04/19/00
Date: Wednesday, 04/19/00 Time: 10:56:35
Scroll ==> PAGE
Entry
Time____
10:54:40
10:50:08
10:49:41
User
ID______
P390C
P390C
P390C
PF3=End PF4=Ret PF7=Bwd PF8=Fwd
--- Top of data reached ---
Note
Line
NOTE
NOTE
NOTE
PF10=Left
1____________________
ADDED TO LINE THREE T
ADDED TO LINE TWO TO
ADDED TO LINE ONE TO
PF11=Right
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
The ‘In’ (inquire note) command is performed from the List Note display.
258
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
System Reference Guide
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage Step by Step
The ‘In’ command (where ‘n’ is the ID of the noteline) allows the user to view the ‘sticky note’ attached to the line
referenced by the ‘n’ value. The ‘In’ command can be entered on the command line or you can overtype the selection
in the ID column.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Sticky Note
Date: Thursday, 04/20/00 Time: 10:05:51
Mode: INQUIRE
AG/Loc/Rid - MANTISSA AREA01
MYSALES
Dataset Nm/Dt/Time/Num - MCHOLLER 040500 115423 00000005
Distributed Dt/Time/Num - 041200
111506 16773087
Line => 00000002 041900 104954 Title - MONTHLY MYSALES
> NOTE ADDED TO LINE TWO TO SHOW HOW LIST FUNCTION WORKS.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
Panel 1 of 2
RM9020I Enter record identifier.
© 2013 Mantissa Corporation. All rights reserved.
259
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage Step by Step
System Reference Guide
The Inquire note panel displays the content of the ‘sticky note’ attached to the line number of the report referenced in
the Line => field. If the note contained more than one page worth of data, the ‘PF8’ key would be used to view the
second page of notes.
Note(s) listing by Report
Command ==> c1
CHAPTER 7: DISPLAY PRINT FACILITY
ID
-01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
Noteline
Number__
00000003
00000002
00000001
PF1=Help
RM9101I
Entry
Date_______________
Wednesday, 04/19/00
Wednesday, 04/19/00
Wednesday, 04/19/00
Date: Wednesday, 04/19/00 Time: 10:56:35
Scroll ==> PAGE
Entry
Time____
10:54:40
10:50:08
10:49:41
User
ID______
P390C
P390C
P390C
PF3=End PF4=Ret PF7=Bwd PF8=Fwd
--- Top of data reached ---
Note
Line
NOTE
NOTE
NOTE
PF10=Left
1____________________
ADDED TO LINE THREE T
ADDED TO LINE TWO TO
ADDED TO LINE ONE TO
PF11=Right
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
The ‘Cn’ (change note) command is performed from the List Note panel.
260
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
System Reference Guide
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage Step by Step
The ‘Cn’ command (where ‘n’ is the ID of the noteline) allows the user to change or add to the content of a note
attached to a report line. The ‘Cn’ command can be entered on the command line or you can overtype the selection in
the ID column.
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Sticky Note
Date: Wednesday, 04/19/00 Time: 11:01:28
Mode: CHANGE
AG/Loc/Rid - MANTISSA AREA01
MYSALES
Dataset Nm/Dt/Time/Num - MCHOLLER 040500 115423 00000005
Distributed Dt/Time/Num - 041200
111506 16773087
Line => 00000003 041900 105021 Title - MONTHLY MYSALES
> NOTE ADDED TO LINE THREE TO SHOW HOW LIST FUNCTION WORKS.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
Panel 1 of 2
RM9019I Change/Add Information. Depress Enter to update.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
The panel above is the ‘sticky note’ record in change mode. The RM9019I message indicates users can change or
add data to the note. The change is made only on the line number of the report referenced in the Line => heading.
© 2013 Mantissa Corporation. All rights reserved.
261
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage Step by Step
System Reference Guide
Up to two pages of notes can be changed and/or added. Panel 2 is available if additional space is required. Use the
‘PF8’ key to advance to panel 2 of 2.
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Sticky Note
Date: Wednesday, 04/19/00 Time: 11:01:28
Mode: CHANGE
AG/Loc/Rid - MANTISSA AREA01
MYSALES
Dataset Nm/Dt/Time/Num - MCHOLLER 040500 115423 00000005
Distributed Dt/Time/Num - 041200
111506 16773087
Line => 00000003 041900 105021 Title - MONTHLY MYSALES
> changing text to demonstrate how notes that have been added can
> be changed.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
Panel 1 of 2
RM9019I Change/Add Information. Depress Enter to update.
In change mode the cursor will be positioned in the text area. Change or add text as desired and press <enter> to
update the record.
ID
-01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
Noteline
Number__
00000003
00000002
00000001
PF1=Help
RM9027I
262
Entry
Date_______________
Wednesday, 04/19/00
Wednesday, 04/19/00
Wednesday, 04/19/00
Date: Wednesday, 04/19/00 Time: 11:02:21
Scroll ==> PAGE
Entry
Time____
11:02:21
10:50:08
10:49:41
User
ID______
P390C
P390C
P390C
Note
Line 1____________________
CHANGING TEXT TO DEMONSTRA
NOTE ADDED TO LINE TWO TO
NOTE ADDED TO LINE ONE TO
PF3=End PF4=Ret PF7=Bwd PF8=Fwd PF10=Left PF11=Right
Changes recorded. Enter identifier for next change.
© 2013 Mantissa Corporation. All rights reserved.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
Note(s) listing by Report
Command ==>
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage Step by Step
System Reference Guide
After you have entered the desired changes to the ‘Sticky Note’, the RM9027I message will be returned. The
message indicates the changes were successfully recorded.
ID
-01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
Noteline
Number__
00000003
00000002
00000001
PF1=Help
Date: Wednesday, 04/19/00 Time: 11:02:21
Scroll ==> PAGE
Entry
Date_______________
Wednesday, 04/19/00
Wednesday, 04/19/00
Wednesday, 04/19/00
PF3=End
PF4=Ret
Entry
Time____
11:02:21
10:50:08
10:49:41
PF7=Bwd
User
ID______
P390C
P390C
P390C
PF8=Fwd
Note
Line 1____________________
CHANGING TEXT TO DEMONSTRA
NOTE ADDED TO LINE TWO TO
NOTE ADDED TO LINE ONE TO
PF10=Left
CHAPTER 7: DISPLAY PRINT FACILITY
Note(s) listing by Report
Command ==> d3
PF11=Right
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
The ‘Dn’ (delete note) command is performed from the List Note display.
© 2013 Mantissa Corporation. All rights reserved.
263
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage Step by Step
RMS/Online® Version 11.35
System Reference Guide
The ‘Dn’ command (where ‘n’ is the ID of the noteline) allows the user to delete the ‘sticky note’ attached to the
report line. The ‘Dn’ command can be entered on the command line or you can overtype the selection in the ID
column.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Sticky Note
Date: Wednesday, 04/19/00 Time: 11:12:15
Mode: DELETE
AG/Loc/Rid - MANTISSA AREA01
MYSALES
Dataset Nm/Dt/Time/Num - MCHOLLER 040500 115423 00000005
Distributed Dt/Time/Num - 041200
111506 16773087
Line => 00000001 041900 104922 Title - MONTHLY MYSALES
> NOTE ADDED TO LINE ONE TO SHOW HOW LIST FUNCTION WORKS.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
Panel 1 of 2
RM9021I Depress ENTER to confirm deletion.
264
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage – Reload from Group Archive
System Reference Guide
The delete note command has no additional operands. When the delete panel is presented, the RM9021I message
prompts the user to depress <enter> to confirm the deletion of the record. The record is deleted immediately once the
<enter> key is depressed.
ID
-01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
Noteline
Number__
00000003
00000002
PF1=Help
RM9026I
Entry
Date_______________
Wednesday, 04/19/00
Wednesday, 04/19/00
Date: Wednesday, 04/19/00 Time: 11:12:23
Scroll ==> PAGE
Entry
Time____
11:02:21
10:50:08
User
ID______
P390C
P390C
Note
Line 1____________________
CHANGING TEXT TO DEMONSTRA
NOTE ADDED TO LINE TWO TO
CHAPTER 7: DISPLAY PRINT FACILITY
Note(s) listing by Report
Command ==>
PF3=End PF4=Ret PF7=Bwd PF8=Fwd PF10=Left PF11=Right
Deletion complete. Enter identifier for next deletion.
After confirming the deletion of the note, the List Note display is returned. The RM9026I message is returned to
notify the user that the deletion of the record has been completed.
The List Note display has been updated and contains only the remaining notes associated with the report.
Note pad Usage – Reload from Group Archive
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
The notepad facility is available for any report viewable within RMS Online. Users have the ability to index BASE
datasets from application jobs in addition to distributed datasets from RM80004 jobs. Indexing BASE datasets
requires the DEFAULT*FILESET be specified in the RvvrmCTP member. RvvrmCTP is the parameter deck that
governs the functions to be performed by the RvvrmCTL (control region) started task.
Datasets that are indexed, both base and distributed, are candidates for group archive. Using the group archive
(retention based) methodology for your viewable datasets provides for long term archival and recovery of the datasets
within RMS Online. By design any ‘sticky notes’ that have been attached to the report follow it throughout its’ life in
the RMS repository. This feature is very beneficial as it allows for the dataset and its’ historical ‘sticky notes’ to be
readily available for recall.
Once a group archive managed dataset is reloaded, original ‘sticky notes’ can be changed and additional ‘sticky
notes’ can be added to the report lines.
© 2013 Mantissa Corporation. All rights reserved.
265
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage – Reload from Group Archive
System Reference Guide
The following panels provide examples of notes that have been attached to a report governed by a group archive.
R.M.S. - Index of Reports
Date: Monday,
Location: RMSC0000
( SOFTCOPY
)
Command ==> v2
ID ReportID Report Title_______________ Media_____
01 RELOADED All reloaded reports ++++
SOFTCOPY
02 MADISON
SOFTCOPY
03 MCHOLLER
SOFTCOPY
04
05
06
07
08
09
10
11
12
13
14
15
16
17
CHAPTER 7: DISPLAY PRINT FACILITY
PF1=Help
PF3=End
PF4=Ret
04/24/00 Time: 13:24:15
Date____
04/07/00
04/07/00
04/07/00
Scroll ==> PAGE
Time____ JESID
11:18:24
0
11:18:24
430
11:18:13
429
PF6=Refresh PF7=Bwd PF8=Fwd
Index list of reports within a location.
PF1=Help
266
PF3=End
Report
Date: Monday,
Report: MADISON
Name____ Number_ Vers Status__
MADISON
531
0 ..AB..O.
MADISON
527
1 ..AB..O.
MADISON
524
2 ..A.P.O.
MADISON
0
3 D.ABP.O.
MADISON
0
4 D.ABP.O.
PF4=Ret
04/24/00 Time: 13:24:16
Media: SOFTCOPY
Scroll ==> PAGE
Pages__ Lines___ JES__Name
84
2100 P390CGNR
84
2100 P390CGNR
84
2100 P390CGNR
84
2100 P390CGNR
84
2100 P390CGNR
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
R.M.S. - Versions of a
Location: RMSC0000
Command ==>
ID Date____ Time____
01 04/11/00 12:57:45
02 04/07/00 12:59:44
03 04/07/00 11:30:03
04 04/07/00 11:21:26
05 04/07/00 11:18:24
06
07
08
09
10
11
12
13
14
15
16
17
PF6=Refresh PF7=Bwd PF8=Fwd
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage – Reload from Group Archive
System Reference Guide
Version list of the MADISON report. The 3rd and 4th versions of the report have been destaged (as noted by the 1st
position of the status field) and are only available for viewing if the report is reloaded to softcopy.
PF3=End
PF4=Ret
PF6=Refresh PF7=Bwd PF8=Fwd
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
PF1=Help
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Versions of a Report
Date: Monday,
04/24/00 Time: 13:24:16
Location: RMSC0000
Report: MADISON
Media: SOFTCOPY
Command ==>
Scroll ==> PAGE
ID Date____ Time____ Name____ Number_ Vers Status__ Pages__ Lines___ JES__Name
01 04/11/00 12:57:45 MADISON
531
0 ..AB..O.
84
2100 P390CGNR
02 04/07/00 12:59:44 MADISON
527
1 ..AB..O.
84
2100 P390CGNR
03 04/07/00 11:30:03 MADISON
524
2 ..A.P.O.
84
2100 P390CGNR
04 04/07/00 11:21:26 MADISON
0
3 D.ABP.O.
84
2100 P390CGNR
a *------------------------------------------------------*4
2100 P390CGNR
0 |
- ARCHIVE INFORMATION |
0 |
|
0 | DSN > PROD.NP.D000407.A2111847.CJHBASE3.RMSARC
|
0 | ON VOLSER > ******
|
1 | DATE/TIME > 04/07/00
* 11.18.47
|
1 *------------------------------------------------------*
12
13
14
15
16
17
© 2013 Mantissa Corporation. All rights reserved.
267
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage – Reload from Group Archive
System Reference Guide
The Archive Information above shows the dataset name, date and time of the group archive that contains the report
data we will be reloading. The ‘AI leaflet’ is presented by keying ‘AI’ over the column ID of a report version record.
You do not have to key the ‘AI’ command before proceeding with the reload of the data, it is provided for information
purposes only. Key ‘PF3’ to return to the version list.
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Versions of a
Location: RMSC0000
Command ==> r5
ID Date____ Time____
01 04/11/00 12:57:45
02 04/07/00 12:59:44
03 04/07/00 11:30:03
04 04/07/00 11:21:26
05 04/07/00 11:18:24
06
07
08
09
10
11
12
13
14
15
16
17
PF3=End
Date: Monday,
Report: MADISON
Name____ Number_ Vers Status__
MADISON
531
0 ..AB..O.
MADISON
527
1 ..AB..O.
MADISON
524
2 ..A.P.O.
MADISON
0
3 D.ABP.O.
MADISON
0
4 D.ABP.O.
PF4=Ret
04/24/00 Time: 13:24:47
Media: SOFTCOPY
Scroll ==> PAGE
Pages__ Lines___ JES__Name
84
2100 P390CGNR
84
2100 P390CGNR
84
2100 P390CGNR
84
2100 P390CGNR
84
2100 P390CGNR
PF6=Refresh PF7=Bwd PF8=Fwd
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
PF1=Help
Report
268
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage – Reload from Group Archive
System Reference Guide
R.M.S. - Recover / Print
Date: Monday,
04/24/00 Time: 13:25:05
Location: RMSC0000
Report: MADISON Date/Time: 040700 111824
Option ==> r
(R)- Recover (P) - Print (L) - Get Loc Attributes
____________________________ Output Attributes _______________________________
Class
==> 9
Burst ==>
OLmt ==>
Form
==> STD
Fls/CC ==>
:
UCS ==>
:
FCB:A/V
==>
:
OPTCD ==>
PWD ==>
Dest
==> LOCAL
Node
==>
Seps ==> 2
Desk/EWN ==>
Modify ==>
:
JCLm ==>
PageDef
==>
Char1 ==>
Disp ==>
FormDef
==>
Char2 ==>
BLK ==> P390C
LRECL
==>
Char3 ==>
Pri ==>
Copies
==> 001
Char4 ==>
DDNM ==>
Name
==> SUPPORT QA TEAM
Title
==>
Dept/XPRO ==>
Building ==>
Room
==>
Addr 1
==> MANTISSA CORPORATION
Addr 2
==> QUALITY ASSURANCE
Addr 3
==> 2200 VALLEYDALE ROAD
Addr 4
==> BIRMINGHAM, AL 35244
PF1=Help
PF3=End
PF4=Return
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
Key ‘R’ in the Option = = > field and depress <enter>. This panel is used to issue (R)ecover or (P)rint requests, or to
obtain (L)ocation attributes prior to printing.
R.M.S. - Versions of a Report
Date: Monday,
04/24/00 Time: 13:25:10
Location: RMSC0000
Report: MADISON
Media: SOFTCOPY
Command ==> r5
Scroll ==> PAGE
ID Date____ Time____ Name____ Number_ Vers Status__ Pages__ Lines___ JES__Name
01 04/11/00 12:57:45 MADISON
531
0 ..AB..O.
84
2100 P390CGNR
02 04/07/00 12:59:44 MADISON
527
1 ..AB..O.
84
2100 P390CGNR
03 04/07/00 11:30:03 MADISON
524
2 ..A.P.O.
84
2100 P390CGNR
04 04/07/00 11:21:26 MADISON
0
3 D.ABP.O.
84
2100 P390CGNR
05 04/07/00 11:18:24 MADISON
0
4 D.ABP.O.
84
2100 P390CGNR
06
07
08
09
10
11
12
13
14
15
16
17
PF1=Help
RM9062I
PF3=End PF4=Ret PF6=Refresh PF7=Bwd PF8=Fwd
Print request processed.
© 2013 Mantissa Corporation. All rights reserved.
269
CHAPTER 7: DISPLAY PRINT FACILITY
The ‘Rn’ command (where ‘n’ is the ID of the report to be reloaded) is used to recover a destaged report to a viewable
status. Depress <enter> and the following screen is returned.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage – Reload from Group Archive
System Reference Guide
The RM9062I message is returned to show your request has been processed. The reload request is dispatched to the
RvvrmCTL (control region) started task for processing.
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Index of Reports
Date: Monday,
Location: RMSC0000
( SOFTCOPY
)
Command ==>
ID ReportID Report Title_______________ Media_____
01 MCHOLLER
SOFTCOPY
02 MADISON
SOFTCOPY
03 RELOADED All reloaded reports ++++
SOFTCOPY
04
05
06
07
08
09
10
11
12
13
14
15
16
17
PF1=Help
RM9102I
04/24/00 Time: 13:28:03
Date____
04/11/00
04/11/00
04/07/00
Scroll ==> PAGE
Time____ JESID
12:57:48
382
12:57:45
381
11:18:24
0
PF3=End PF4=Ret PF6=Refresh PF7=Bwd PF8=Fwd
--- Bottom of data reached ---
Once the control region has processed the reload request, the Index of Reports will show an entry with a Report ID of
RELOADED. This is the Report ID assigned to all reports that are reloaded to softcopy.
PF1=Help
270
PF3=End
PF4=Ret
04/24/00 Time: 13:28:36
Date____
04/11/00
04/11/00
04/07/00
Scroll ==> PAGE
Time____ JESID
12:57:48
382
12:57:45
381
11:18:24
0
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
R.M.S. - Index of Reports
Date: Monday,
Location: RMSC0000
( SOFTCOPY
)
Command ==> v3
ID ReportID Report Title_______________ Media_____
01 MCHOLLER
SOFTCOPY
02 MADISON
SOFTCOPY
03 RELOADED All reloaded reports ++++
SOFTCOPY
04
05
06
07
08
09
10
11
12
13
14
15
16
17
PF6=Refresh PF7=Bwd PF8=Fwd
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage – Reload from Group Archive
System Reference Guide
The ‘Vn’ command (where ‘n’ is the ID of the report) will provide a list that contains all of the versions of the
requested report within the specified location. The ‘Vn’ command can be entered on the command line, or you can
overtype the selection in the ID column.
PF1=Help
RM9102I
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Versions of a Report
Date: Monday,
04/24/00 Time: 13:28:43
Location: RMSC0000
Report: RELOADED
Media: SOFTCOPY
Command ==>
Scroll ==> PAGE
ID Date____ Time____ Name____ Number_ Vers Status__ Pages__ Lines___ JES__Name
01 04/07/00 11:18:24 MADISON
713
0 ..N..RO.
84
2100 P390C
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
PF3=End PF4=Ret PF6=Refresh PF7=Bwd PF8=Fwd
--- Bottom of data reached ---
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
The panel above is a version listing of all the reports that have been RELOADED in the location specified. The
Name field contains the original Report ID.
R.M.S. - Versions of a Report
Date: Monday,
04/24/00 Time: 13:28:43
Location: RMSC0000
Report: RELOADED
Media: SOFTCOPY
Command ==> d1
Scroll ==> PAGE
ID Date____ Time____ Name____ Number_ Vers Status__ Pages__ Lines___ JES__Name
01 04/07/00 11:18:24 MADISON
713
0 ..N..RO.
84
2100 P390C
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
PF1=Help
RM9102I
PF3=End PF4=Ret PF6=Refresh PF7=Bwd PF8=Fwd
--- Bottom of data reached ---
© 2013 Mantissa Corporation. All rights reserved.
271
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage – Reload from Group Archive
System Reference Guide
The ‘Dn’ command (where ‘n’ is the ID of the report to be viewed) will open the requested report for viewing through
RMS Online. The ‘Dn’ command can be entered on the command line, or you can overtype the selection in the ID
column.
CHAPTER 7: DISPLAY PRINT FACILITY
LOCATION: RMSC0000
REPORT: RELOADED >
< P:
1 L:
1
COMMAND ==> ln
SCROLL ==> FULL
___Start of Data___
___Start of Data___
___Start of Data___
___St
____Top of Page____
____Top of Page____
____Top of Page____
____T
CALIFORNIA STATE DISTRIBUTORS
PAGE 1 00010019
MONTHLY TELECOM REPORT
02/19/92 00020019
ZONE 01
FOR YEAR ENDED OCTOBER 31, 1995
00030020
00040019
REGULAR
BONUS
TOTAL
00050019
SALESMAN
SALESMAN
COMMISSION
COMMISSION
COMMISSION
00060019
15896
TIM C EVANS
$800.00
$3.28
$803.28
00070019
23960
ROGER D SMITH
$4,314.69
$4,314.69
00080019
98111
DON E LEFTY
$1,000.00
$1,000.00
00090019
54543
GEORGE I IMAY
$2,400.00
$2,400.00
00100019
70599
EDGAR P ALLEN
$750.00
$750.00
00110019
47783
JEFFRY A TALMAN
$732.28
$732.28
00120019
39756
PAUL M VOUGHT
$2,000.00
$2,000.00
00130019
23456
DAVID GRAY
$5,000.00
$5,000.00
00140019
00001
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00150019
00002
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00160019
00003
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00170019
00004
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00180019
00005
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00190019
00006
CANDACE CARROLL
$1,740.00
$50.00
$1,790.00
00200019
Display of the requested report.
ID Noteline Entry
-- Number__ Date_______________
01 00000002 Friday,
04/07/00
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
PF1=Help
RM9101I
272
Date: Monday,
Entry
Time____
11:20:51
User
ID______
BASE
PF3=End PF4=Ret PF7=Bwd PF8=Fwd
--- Top of data reached ---
04/24/00 Time: 13:29:16
Scroll ==> PAGE
Note
Line 1____________________
NOTE ADDED TO LINE TWO OF
PF10=Left
PF11=Right
© 2013 Mantissa Corporation. All rights reserved.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
Note(s) listing by Report
Command ==>
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage – Reload from Group Archive
System Reference Guide
The ‘LN’ (list note) command produces a listing of all of the ‘sticky notes’ that have been added to the report being
viewed. To generate the list, key ‘LN’ on the command line and press <enter>.
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Sticky Note
Date: Monday,
04/24/00 Time: 13:30:16
Mode: INQUIRE
AG/Loc/Rid - RMSC0000 RMSC0000
MADISON
Dataset Nm/Dt/Time/Num - MADISON 040700 111824 00000020
Distributed Dt/Time/Num - 040700
111824 16773157
Line => 00000002 040700 112026 Title > NOTE ADDED TO LINE TWO OF MADISON BASE DATASET. NEED TO VERIFY STATUS
> OF NOTE AFTER BACKUP AND RESTORE PROCESSES. CJH.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
Panel 1 of 2
RM9020I Enter record identifier.
The ‘In’ (inquire note) command is performed from the List Note display.
The notes attached to the original report are available when the report has been reloaded.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
Note(s) listing by Report
Command ==> c1
ID Noteline Entry
-- Number__ Date_______________
01 00000002 Friday,
04/07/00
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
PF1=Help
RM9101I
Date: Monday,
Entry
Time____
11:20:51
User
ID______
BASE
PF3=End PF4=Ret PF7=Bwd PF8=Fwd
--- Top of data reached ---
© 2013 Mantissa Corporation. All rights reserved.
04/24/00 Time: 13:30:42
Scroll ==> PAGE
Note
Line 1____________________
NOTE ADDED TO LINE TWO OF
PF10=Left
PF11=Right
273
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage – Reload from Group Archive
RMS/Online® Version 11.35
System Reference Guide
The ‘Cn’ (change note) command is performed from the List Note panel.
New notes can be added to the reloaded report, and the text of the original note(s) can be changed as desired.
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Sticky Note
Date: Monday,
04/24/00 Time: 13:31:02
Mode: CHANGE
AG/Loc/Rid - RMSC0000 RMSC0000
MADISON
Dataset Nm/Dt/Time/Num - MADISON 040700 111824 00000020
Distributed Dt/Time/Num - 040700
111824 16773157
Line => 00000002 040700 112026 Title > NOTE ADDED TO LINE TWO OF MADISON BASE DATASET. NEED TO VERIFY STATUS
> OF NOTE AFTER BACKUP AND RESTORE PROCESSES. CJH.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
Panel 1 of 2
RM9019I Change/Add Information. Depress Enter to update.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
The panel above is the ‘sticky note’ record in change mode. The RM9019I message indicates users can change or
add data to the note. The change is made only on the line number of the report referenced in the Line => heading.
274
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
RMS Note Pad Facility
Note pad Usage – Reload from Group Archive
System Reference Guide
Up to two pages of notes can be changed and/or added. Panel 2 is available if additional space is required. Use the
‘PF8’ key to advance to panel 2 of 2.
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Sticky Note
Date: Monday,
04/24/00 Time: 13:31:02
Mode: CHANGE
AG/Loc/Rid - RMSC0000 RMSC0000
MADISON
Dataset Nm/Dt/Time/Num - MADISON 040700 111824 00000020
Distributed Dt/Time/Num - 040700
111824 16773157
Line => 00000002 040700 112026 Title > NOTE ADDED TO LINE TWO OF MADISON BASE DATASET. NEED TO VERIFY STATUS
> OF NOTE AFTER BACKUP AND RESTORE PROCESSES. CJH.
> note is being properly handled by backup and restore process. this report
> was destaged and subsequently reloaded from a group archive.
> the text of the original note is being amended to contain the additional
> input shown here.
>
>
>
>
>
>
>
>
>
>
>
PF1=Help PF3=End PF4=Ret PF7=Bwd PF8=Fwd
Panel 1 of 2
RM9019I Change/Add Information. Depress Enter to update.
In change mode the cursor will be positioned in the text area. Change or add text as desired and press <enter> to
update the record.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
Note(s) listing by Report
Command ==>
ID Noteline Entry
-- Number__ Date_______________
01 00000002 Monday,
04/24/00
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
PF1=Help
RM9027I
Date: Monday,
Entry
Time____
13:33:05
User
ID______
P390C
04/24/00 Time: 13:33:05
Scroll ==> PAGE
Note
Line 1____________________
NOTE ADDED TO LINE TWO OF
PF3=End PF4=Ret PF7=Bwd PF8=Fwd PF10=Left PF11=Right
Changes recorded. Enter identifier for next change.
© 2013 Mantissa Corporation. All rights reserved.
275
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
Using the Display for the First Time User
Task/Panel Cross Reference
System Reference Guide
After you have entered the desired changes to the ‘Sticky Note’, the RM9027I message will be returned. The
message indicates the changes were successfully recorded.
All Note Pad functions are valid for use on a Reloaded report.
Task/Panel Cross Reference
TASK
Sign on system
Display a report
Change your password
Produce index of available reports.
View version of a particular report
PANEL
Access Authorization
Display/Print Menu (Option D)
Access Authorization
Display/Print Menu
Display/Print Menu
USING THE DISPLAY FOR THE FIRST TIME USER
CHAPTER 7: DISPLAY PRINT FACILITY
Information on the operation of the 3270 display terminal can be found in the following IBM publications:
•
Operators Guide for IBM 3270 Information Display Systems GA27-2742
•
IBM 3290 Information Panel Description and Reference GA23-0021
Important Keys
•
PF keys - Using the program function (PF key) is a fast way to instruct RMS/DPF to perform a certain task.
Pressing a PF key will also cause the transmission of any information entered into fields on the panel. For example, entering 8 in the COMMAND ==> field and pressing PF 7 (Scroll Backward) will cause RMS/DPF to position the report display back 7 lines.
•
ENTER - Pressing Enter causes the data entered into the current panel to be transmitted to RMS/DPF. RMS/DPF
responds to the various commands and fields entered.
•
ERASE EOF - Causes data in the current field, from the cursor position to the end of the field, to be erased. It’s
just an easy way to erase text.
•
Cursor keys - Used to position the cursor on the screen. RMS/DPF input fields are marked by ==>. Pressing the
cursor keys with just an arrow will position the cursor in the direction indicated. The keys marked >| and <| cause
the cursor to advance or retreat to the next field each time they are pressed.
•
PF1 - Perhaps the most important key, especially if you are a new user. Pressing the PF1 key gives you access to
the system Help facilities.
RMS/Online has a corresponding Help panel(s) for each system panel. In order to access the Help panel, the user
simply presses the Help program function key (PF1/PF13).
Each Help panel contains a complete explanation of the entry/data requirements for the panel in question.
How to get started
1.
The first thing you must do is sign on to the terminal. Your terminal may have a system-wide security system that
must be satisfied first. If so, please enter the following transaction:
(your data center security officer should fill in your sign-on transaction here.)
2.
276
RMS has its own security system and, if not bypassed by your data center, requires you to enter the following:
© 2013 Mantissa Corporation. All rights reserved.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
System Help Facilities
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
Using the Display for the First Time User
How to get started
System Reference Guide
RMNN XXXXXXXX YYYYYYYY
WHERE
NN
=
XXXXXXXX
*________________
YYYYYYYY
*________________
YOUR USER ID IS
YOUR PASSWORD
*
=
=
*Your Security Administrator or training instructor should fill in these items.
3.
The following panels in this chapter depict the sequence of steps you must follow to get to your report. There are
instructions on how you navigate within the report you are displaying.
Primary Menu Panel
R.M.S. - Primary Menu
Access Group - IVSYSTEM
Date: Monday,
10/07/96 Time: 18:06:07
SubSys: R134 Tran:
TermID: 002B ___
1.
2.
3.
4.
5.
6.
T.
Display/Print
Administration
Distribution(Implicit)
Sysout/Report
Security
Help Management
Tutorial
F1=Help
PF3=End
-
CHAPTER 7: DISPLAY PRINT FACILITY
Option ==>
Display/Print a Report in the RMS Database
Administration and Resource Control
Distribution Definition and Management
Sysout/Report Profile Management
Security Definition and Management
Help Management and Maintenance
Tutorial on System Capabilities/Facilities
PF4=Return
Depending on options selected during system installation, the Primary Menu may be presented immediately after the
Access Authorization panel. All major system functions are accessible from this panel.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
Select option “1” to gain access to the Display/Print Facility.
If this is not the panel displayed after sign on, then go to the next page.
© 2013 Mantissa Corporation. All rights reserved.
277
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
Using the Display for the First Time User
How to get started
System Reference Guide
Display/Print Menu Panel
R.M.S. - Display/Print
Date: Monday,
10/07/96 Time: 18:07:23
SubSys: R134 Tran:
TermID: 002B ___
Option ==>
I.
V.
D.
T.
Index
Versions
Display
Tutorial
Access Group
Location
Report ID
Version Num
Media Type
CHAPTER 7: DISPLAY PRINT FACILITY
PF1=Help
-
==>
==>
==>
==>
==>
PF3=End
Index of Reports by Location
Versions List for a Specific Report
Display/Print a Report in the RMS Database
Tutorial on System Capabilities/Facilities
IVSYSTEM
CHICAGO
VENACT
SOFTCOPY
Required
Required
Required for Options D,V
Optional - 0001 for -1
Optional - * or Media Type
PF4=Return
From this panel you may display reports, view an index of available reports or determine the versions of each report.
First, look at the index of reports for your location. Do this by entering an “I” in the OPTIONS ==> field.
Your default Access Group and Location Name assigned to your user ID will be displayed here. Other Access Groups
and Locations may be entered by tabbing to those fields and entering their full names. If you have others available,
you or your systems administrator should list those here:
LOCATION NAMES
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
ACCESS GROUPS
278
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
Using the Display for the First Time User
How to get started
System Reference Guide
Index Panel
10/07/96 Time: 18:08:17
Date____
10/03/96
10/03/96
10/01/96
Scroll ==> PAGE
Time____ JESID
09:49:30
148
09:49:30
148
09:35:08
303
PF1=Help PF3=End PF4=Ret PF6=Refresh PF7=Bwd PF8=Fwd
RM9102I --- Bottom of data reached ---
This panel displays an index of those reports available to a location. The location on this panel is Chicago.
Multiple versions (previous days) of these reports may be kept for viewing. In order to see the versions of the reports
available, enter “V” and the ID number of the report you want. In our example, “V1” will display the versions of the
YEAR-TO-DATE SALES PROFIT report. However, at this point you probably may want to display the most recent
copy of one of the listed reports.
If you want to display the 000 version (most recent copy) of the report, enter “S” or “D” and the ID number of the
report you want. (Or key in “S “or “D” next to the desired item in the ID column.) In our example above, “D” would
display the latest version of the VENDOR ACTIVITY REPORT. Requesting the display of a report from the index
panel will always display the most recent version added to the viewing files.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
If the index contains more than 17 entries, then you may scroll forward and backward in the index list by using the
Scroll Up/Scroll Down PF keys.
The Index panel is used for submission of Output Definition Verification and requests. (See the Output Definition
Chapter).
NOTE: The PF keys and their functions may be viewed by entering PF in the
COMMAND ==> area. Return by using the PF3 key.
© 2013 Mantissa Corporation. All rights reserved.
279
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Index of Reports
Date: Monday,
Location: CHICAGO
( SOFTCOPY
)
Command ==>
ID ReportID Report Title_______________ Media_____
01 PROFIT
YEAR-TO-DATE SALES PROFITA
SOFTCOPY
02 VENACT
VENDOR ACTIVITY REPORT
SOFTCOPY
03 STOCK
YEAR/TO/DATE STOCK STATUS
SOFTCOPY
04
05
06
07
08
09
10
11
12
13
14
15
16
17
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
Using the Display for the First Time User
How to get started
System Reference Guide
Versions Panel
R.M.S. - Versions of a
Location: CHICAGO
Command ==>
ID Date____ Time____
01 10/03/96 09:49:30
02 10/01/96 09:45:29
03 10/01/96 09:26:23
04 10/01/96 09:23:35
05 10/01/96 09:13:36
06
07
08
09
10
11
12
13
14
15
16
17
Report
Date: Monday,
Report: PROFIT
Name_____Number Vers Status__
INR02
468
0 ........
INR02
338
1 ........
INR02
309
2 .+......
INR02
290
3 .+......
INR02
270
4 .+......
10/07/96 Time: 18:08:55
Media: SOFTCOPY
Scroll ==> PAGE
Pages__ Lines___ JES__Name
2
46 OO1134
2
46 OO1134
6
138 OO1134
6
138 OO1134
6
138 OO1134
CHAPTER 7: DISPLAY PRINT FACILITY
PF1=Help PF3=End PF4=Ret PF6=Refresh PF7=Bwd PF8=Fwd
RM9102I --- Bottom of data reached ---
The report versions are listed from newest to oldest. Scroll capabilities permit the user to locate the desired version of
a report should there be more than 17 versions. The Display (D,S), Print (P), Output (O), Recover (R), and Cancel (C)
report functions may be invoked by entering the desired function followed by the ID number of the selected report.
For our example we have selected to display the 000 version of the PROFIT report.
Type “D1” or “S1” in the COMMAND field and press ENTER.
This will display the most recent version of the PROFIT report.
NOTE: The Cancel, Output, Recover, and Print commands may be limited to specific users or the
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
System Administrator at your installation.
280
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
Report Viewing Features
How to get started
System Reference Guide
Display Panel
1
FULL
-- ST
-- T
INV
30
40
50
60
133
23
75
55
225
35
110
85
250
750
45
100
90
40
The preceding pages have shown how to get to the display panel for a desired report. It was assumed that the user did
not know which reports were available and which versions were available to view. There is a simple way to view the
report if the Report ID and version is known.
On the Display/Print Menu panel enter:
OPTIONS ==>
D
ACCESS GROUP ==>
(Required, enter your Access Group)
LOCATION NAME ==>
(Required, enter your Location)
REPORT NAME ==>
(Required, enter the Report you want)
VERSION ==>
(Optional Default-000)
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
The result is the same whether the long or short version is used to get to the report display.
REPORT VIEWING FEATURES
Once a report is displayed, various commands may be used to customize the presentation of the report(s) to fit
individual needs.
You communicate with the display print facility by a combination of PF key depressions and commands entered in
the COMMAND ==> field at the top of the panel.
All available commands are covered in this chapter. They are organized into four logical groups that perform the
following functions.
•
Format your reports for viewing
© 2013 Mantissa Corporation. All rights reserved.
281
CHAPTER 7: DISPLAY PRINT FACILITY
LOCATION: CHICAGO
REPORT: STOCK
>
< P:
1 L:
COMMAND ==>
SCROLL ==>
-- START OF DATA --- START OF DATA --- START OF DATA --- TOP OF PAGE --- TOP OF PAGE --- TOP OF PAGE -CHICAGO
YEAR-TO-DATE STOCK STATUS REPORT
ITEM
NO. RECEIPTS
SALES
TRANSFRS
ADJTS
PHY
10001
0
40
11
0
158
10002
0
38
12
0
160
10004
0
36
13
0
162
10005
0
34
14
0
164
10006
0
80
23
0
231
10009
0
66
19
0
87
10011
0
50
15
0
8
10012
0
31
9
2
11
10014
0
72
20
0
108
10015
0
40
11
0
123
10016
0
87
25
0
37
10018
0
91
28
0
71
10019
0
127
41
0
101
10020
0
340
87
7
502
10021
0
16
4
0
5
10022
0
5
1
0
0
10023
0
61
15
0
7
10024
0
11
3
0
1
Chapter 7: Display Print Facility
Introduction
Report Viewing Features
Report Formatting
RMS/Online® Version 11.35
System Reference Guide
•
Locate information within the report
•
Using the windowing features
•
Informational commands
In the following command description, brackets (“[“and “]”) are used for notation only and should not be entered
with command data. When used in the description of command options, these brackets indicate that one or more
fields may be entered with a command. The vertical bar “|” indicates that one of the listed options may be entered
with a command.
You will notice that with many of the commands, the same command is used to activate and deactivate the option. For
instance, a scale line (a line that provides a visual marker for report lines) may be added and removed by typing
(S)cale into the command area of the panel.
Report Formatting
CHAPTER 7: DISPLAY PRINT FACILITY
Once your report is displayed, you may use the column select (CS) command to reformat the columns of the reports
in any order you would like to see them. To assist you in the selection of the correct columns, the S(cale) command
will give you a scale line at the top of the panel. Movement up/down and left/right can be done with PF7/PF8 and
PF10/PF11, respectively.
SCALE
S
The SCALE command adds or deletes the ruler line to/from the current display. The ruler lines serves as a horizontal
visual reference while viewing a report. It looks like this:
....+...10....+...20....+...30....+...40....+...50....+... 60....+...70....+...80
COLUMN SELECT [xy......]
CS
The COLUMN SELECT command is used to select and reorganize the columns of a report to make the content of
that report more usable to the viewer. Columns may be selected in any order and columns selected by one x,y pair
may overlap those selected by another select pair. The only requirement is that x be less than or equal to y in each x,y
pair, and that neither value be less than 1 or greater than 240.
In order to select columns 1 through 10 and 20 through 40 for viewing, the following CS command would be entered:
CS 1,10 20,40
Since there is no restriction with regard to column order, we could view the same columns in reverse order by
entering:
Columns may be reset by entering CS with no x,y pairs or by using the RESET command.
NOTE: If you are unable to change your format contact your system administrator.
RESET
RS
Reset the viewing options. Column selection is removed. The scale line (if any) is removed. Header hold lines are set
to zero.
282
© 2013 Mantissa Corporation. All rights reserved.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
CS 20,40 1,10
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
Report Viewing Features
Saving Your Format for Later Use
System Reference Guide
Saving Your Format for Later Use
Once you have chosen the best format to display a report, if you want to save that format you can use the FORMAT
SAVE command. This saves your format to be used the next time you view any version of this report. You can use
this format later by the use of the FORMAT RETRIEVE command.
FORMAT SAVE [A.....A]
FS
FORMAT RETRIEVE [A.....A]
FR
The FORMAT RETRIEVE command enables a user to retrieve viewing format information previously saved using
the FORMAT SAVE (FS) command. A.....A is the name of the format (up to 10 characters) to be retrieved. If A.....A
is omitted, the DEFAULT format set is retrieved.
FORMAT DELETE [A.....A]
FD
The FORMAT DELETE command is used to remove a format previously added by a FORMAT SAVE command.
Line Positioning/Scroll Operations
RMS/DPF accepts four scroll values. One of the following may be entered after using the <TAB> key >| to advance
to the SCROLL ==> field.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
H(ALF)
F(ULL)
NNNN
P(AGE)
Scroll half the depth of the current window.
Scroll the depth of the current window.
Scroll NNNN lines.
A scroll value of page positions from the top of the printed page
to the top of the next printed page.
The scroll value may be overridden by entering a number in the command line before depressing the scroll PF keys.
If a number is entered in the command line while the scroll value is HALF, FULL, OR NNNN, the number is
interpreted as the number of lines to scroll. If the scroll value is PAGE when a value is entered, the system scrolls this
many pages.
Entering the letter M (maximum) and depressing a scroll key will cause the system to scroll to the top or bottom of
the report, depending on which PF key is depressed.
When M(aximum) is entered and the scroll left/right key is depressed, the viewing window is positioned as far to the
right or left position of the viewing data as possible.
© 2013 Mantissa Corporation. All rights reserved.
283
CHAPTER 7: DISPLAY PRINT FACILITY
The FORMAT SAVE command provides a convenient method of saving a viewing format. The following values are
retained for subsequent viewing operations using the retrieved format: SCALE, HEADER HOLD, SCROLL
VALUE, ACTIVE COLUMN SELECTION, A.....A is the name under which the format is stored for subsequent
retrieval by the FORMAT RETRIEVE (FR) command. Multiple formats may be saved for the same report. If
DEFAULT is specified, the format is automatically retrieved the next time the report is accessed. It should be noted
that format records are stored by USER ID permitting multiple users to establish and control their unique viewing
requirements for the same report.
Chapter 7: Display Print Facility
RMS/Online® Version 11.35
Introduction
Report Viewing Features
Locating Information Within the Report
System Reference Guide
Locating Information Within the Report
The most important command used to locate information within reports is the FIND command. You must know some
character string near or on the line you want to find.
FIND [‘STRING’ | *] [NEXT | PREV | FIRST | LAST]
F
The FIND command is used to locate a character string (word or phrase) in the report being viewed. The search will
commence at the top of the screen, either forward (down) or back (up).
The FIND operands are:
'STRING'
*
CHAPTER 7: DISPLAY PRINT FACILITY
NEXT
N
PREV
P
FIRST
F
LAST
L
Is the word or phrase to be located. If the word or phrase contains
one of the following characters / ‘$ ~ #, it should be enclosed in
quotes.
Causes the character string last entered to be used as the object of the
current command.
Causes the next occurrence of the character string to be located. This
will include any occurrences on the display panel. Next is the default.
Causes the previous occurrence of the character string to be located.
Causes the first occurrence of the character string to be located.
Causes the last occurrence of the character string to be located.
NOTE: The maximum number of lines the FIND command will search is controlled by the SEARCH
RANGE (SR) command.
Once you find the information you are looking for, it can be marked for later return. Use the label command [.A.....A]
or PF6 key to label the place in the report you want to LOCATE later.
.A....A
Label the current location. A period (“.”) followed by up to 7 characters is used to identify the current page location.
The labeled location may be retrieved for viewing by entering the assigned label as the operand on a LOCATE (L)
command.
LOCATE command is used to position a report to a previously labeled viewing position or to a specific line or page.
If the SCROLL ==> value is HALF, FULL OR NNNN, positioning is to the specified line. If the scroll value is
PAGE, positioning is to the specified page.
NOTE:
.A....A is a label previously assigned.
NNN is a report line number or page number if the SCROLL value is PAGE.
While looking through your reports, you may want to hold column headers at the top of the page for use later. Use the
HEADER command.
284
© 2013 Mantissa Corporation. All rights reserved.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
LOCATE [.A....A | NNNN]
L
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
Report Viewing Features
Using the Windowing Features
System Reference Guide
HEADER [N]
H
The HEADER command is used to request up to 21 lines of header data be held at the top of the scroll page. The held
header lines are highlighted for subsequent scroll operations. Any viewable lines may be held, not just report title
lines.
Heading lines may be removed by entering H with no operand.
SEARCH RANGE [NNNNNNNN]
SR
This command is used to establish a search range for find operations. While finding information within reports the
system will look at a maximum number of lines before interrupting the find operation. This maximum number of
search lines may be overridden with the SEARCH RANGE command. The default is 5000 lines. Values of from 1 to
99,999,999 may be entered. If the number of lines is omitted, the default search range (5,000) is assumed.
Windowing is a way to partition the screen so that multiple reports may be viewed simultaneously. Each partition
may be used like an independent screen. The advantage of this ability to partition the screen is that multiple reports
(or multiple windows of the same report) can be viewed at the same time. All functions available to the full panel are
available to each window. The WINDOW SET command lets you establish the format of the screen. The full screen
report is the first (and default) window and the other windows may be opened or closed at any time. If you want to
change window sets, you may do so without closing. Those that are open will be viewed with the new window set
automatically.
WINDOW SET [SET NAME]
WS
The WINDOW SET command is used to select a window set which will divide the panel into viewing areas.
Available window sets are:
H2
Horizontal aspect window set. Each window occupies one-half
of the panel area.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
------------------------------------------
H3
Horizontal aspect window set. Each window set occupies onethird of the panel area.
Q4
Quadrant aspect window set. Each window set occupies onefourth of the panel area.
© 2013 Mantissa Corporation. All rights reserved.
285
CHAPTER 7: DISPLAY PRINT FACILITY
Using the Windowing Features
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
Report Viewing Features
Informational Commands
V2
System Reference Guide
Vertical aspect window set. Each window set occupies one-half
of the panel area.
Entering “WS” with no set name causes the full screen (default) to be selected.
OPENW
OW
Open a window. After the open window command is entered, a report selection sub-panel is presented in the new
window. Information entered in this sub-panel determines which report will be presented in the new window.
CLOSEW
CW
CHAPTER 7: DISPLAY PRINT FACILITY
Close the current window. The panel area previously occupied by the window is cleared and the current window is
changed to the next active window.
Multiple reports may be opened from the full panel or from any window. Multiple reports may be opened inside each
window. You may toggle back and forth between reports by using PF4/16.
OPENR
OR
Open a report. After the open report command is entered, a report selection sub-panel is presented in the current
window. Information entered in this sub-panel determines which report will be displayed in the active window.
The PF4 key may be used to switch or toggle between open reports inside a window. By entering the report name on
the command line before the PF4 key is pressed, the switch will be to report specified. Otherwise reports will be
displayed in order opened.
ZOOM
Z
The Zoom command is for use within any open window. It enlarges the window to the entire terminal display area.
When entered again, it restores the active window environment from which it was originally entered. The PF12 key is
equivalent to the Zoom command.
Switches from the active window to the next window available.
Informational Commands
Some commands that are used to display information that is not found on the index versions or display panels. These
commands are:
REPORTI
RI
The report information command displays extended information on the report being viewed.
286
© 2013 Mantissa Corporation. All rights reserved.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
PF9
RMS/Online® Version 11.35
System Reference Guide
Chapter 7: Display Print Facility
Introduction
Selective And Full Version Printing
Using the Note Pad Capability
PF
This command displays the default PF key settings for RMS/Online. Depress PF3 when you have reviewed these
settings and your display will be restored to its original viewing location.
AD
Entering AD in the COMMAND ==> field of the display will cause the administrator name and phone number to be
displayed. This may be useful if you are having problems you feel the administrator may help you resolve. This
command causes part of the window being displayed to be overlaid. You may restore the viewing environment by
pressing PF3.
Using the Note Pad Capability
The Note Pad panel is presented if the Attach Note (AN] command is entered during a viewing session. The Note Pad
is a multi-panel display. Place any text in the Note Pad that you desire. Notes are attached to specific report lines. Any
number of notes (up to the number of lines in a report) may be entered. Press PF7/PF8 to page Up/Down. Press
<ENTER> to confirm the note addition and return to the viewing session.
LN
The List Note panel is presented when the LNOTE (LN) command is entered during a viewing session. Notes after
the line number entered with the LN command are listed in ascending line number sequence. The command “LN
2500” would display a list of notes attached to line numbers of equal or greater value than 2500. Individual notes may
be selected for viewing by entering I NN, where NN is the line number of the note record on the list panel. Optionally,
you may overtype the ID field with “I”.
Notes may be changed from the List Notes panel by entering “C NN”, where NN is the ID number of the note you
want to change. Optionally you may overtype the ID field on the individual lines of the List Note panel. Change the
note as desired and press <ENTER> to confirm the change and return to the List Note panel.
Notes may be deleted from the List Notes panel by entering “D NN”, where NN is the ID number of the note you
want to delete. Optionally you may overtype the ID field on the individual lines of the List Note panel. The note to be
deleted will be displayed with a message advising you to depress <ENTER> to confirm delete.
SELECTIVE AND FULL VERSION PRINTING
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
RMS allows you to print reports that are resident in the viewing files and those that have been archived. Selective
page printing is available when printing viewable files.
Print requests during the viewing of a report (Selective Page Printing) will have the column select attributes carried
over to the printing operation.
© 2013 Mantissa Corporation. All rights reserved.
287
CHAPTER 7: DISPLAY PRINT FACILITY
AN
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
Selective And Full Version Printing
Printing an Entire Report
System Reference Guide
Printing an Entire Report
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Versions of a
Location: CHICAGO
Command ==>
ID Date____ Time____
01 10/03/96 09:49:30
02 10/01/96 09:45:29
03 10/01/96 09:26:23
04 10/01/96 09:23:35
05 10/01/96 09:13:36
06
07
08
09
10
11
12
13
14
15
16
17
Report
Date: Monday,
Report: PROFIT
Name_____Number Vers Status__
INR02
468
0 ........
INR02
338
1 ........
INR02
309
2 .+......
INR02
290
3 .+......
INR02
270
4 .+......
10/07/96 Time: 18:11:17
Media: SOFTCOPY
Scroll ==> PAGE
Pages__ Lines___ JES__Name
2
46 OO1134
2
46 OO1134
6
138 OO1134
6
138 OO1134
6
138 OO1134
PF1=Help PF3=End PF4=Ret PF6=Refresh PF7=Bwd PF8=Fwd
RM9102I --- Bottom of data reached ---
From the Versions Panel type PX, or Ox, where X = the ID of the version to be printed.
Before the print job is submitted you will see a Request Print Panel that will allow you to change the print
characteristics and the routing instructions.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
NOTE: Standards at your installation may cause the Request Print panel not to be displayed.
288
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 7: Display Print Facility
Introduction
Selective And Full Version Printing
Printing Selective Pages
System Reference Guide
Recover / Print Panel
Option ==>
Date: Wednesday, 08/26/98 Time: 15:52:47
Report: STOCK
Date/Time: 120490 033407
(R)- Recover (P) - Print
(L) - Get Loc Attributes
____________________________ Output Attributes _______________________________
Class
==>
Burst ==>
OLmt ==>
Form
==>
Fls/CC ==>
:
UCS ==>
:
FCB:A/V
==>
:
OPTCD ==>
PWD ==>
Dest
==>
Node
==>
Seps ==>
Desk/EWN ==>
Modify ==>
:
JCLm ==>
PageDEF
==>
Char1 ==>
Disp ==>
FormDef
==>
Char2 ==>
BLK ==>
LRECL
==>
Char3 ==>
Pri ==>
Copies
==>
Char4 ==>
DDNM ==>
Name
==>
Title
==>
Dept/XPRO ==>
Building ==>
Room
==>
Addr 1
==>
Addr 2
==>
Addr 3
==>
Addr 4
==>
PF1=Help PF3=End PF4=Return
The Recover / Print Panel will first appear with the print characteristics assigned to this report when it was added to
the database. If you wish to change these characteristics you may do so by tabbing to the various fields and entering
those changes. Once the changes have been entered and “P” is entered in the Option field, the print request is queued
when the <ENTER> key is pressed.
Off-line reports may be recovered and reloaded to the repository for viewing. Entering an “R” in the Option ==> will
cause an off-line report to be placed back in the repository in viewing status. Recovered reports are always restored to
their original location under the report ID of RELOADED. Recovered reports which an individual user may access
appear on an index panel display. The original report ID, date and time appear in the title fields of the recovered entry.
Recovered reports are subject to retention processing like any other report. Since recovered reports are placed in
index under a consistent report ID(RELOADED), they are easily located. The most recently recovered entry will
always be the first entry on the index panel.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
There is a set of default print characteristics available to each Location. These may be retrieved by typing “L” in the
Option field and <ENTER>. Once these are retrieved, the print job can be submitted as above.
Printing Selective Pages
Within a report page ranges may be selected for printing. This is done while viewing the report. The following steps
will select a group of pages for printing.
STEP 1
STEP 2
STEP 3
STEP 4
STEP 5
© 2013 Mantissa Corporation. All rights reserved.
Display the report which you want to print.
Page to or find the first page to print.
Type “PS” in the command field, then <ENTER>.
Page to or find the last page to print or remain on the current page if only that
one page is to be printed.
Type “PE” in the command field, then <ENTER>.
289
CHAPTER 7: DISPLAY PRINT FACILITY
R.M.S. - Recover / Print
Location: CHICAGO
Chapter 7: Display Print Facility
Introduction
Selective And Full Version Printing
Printing Selective Pages
RMS/Online® Version 11.35
System Reference Guide
NOTE: Steps 2 through 6 may be repeated up to 15 times to select 15 different sets of pages to be
printed.
Once the display for that report is ended (PF3) key, the Request Print Panel will be displayed automatically. This
panel will allow you to change the print characteristics and the routing instructions for the print being requested.
PRINT START
PS
The PRINT START command designates the beginning page of a page range to be printed.
PRINT END
PE
The PRINT END command is used to indicate the end of a range of pages selected for printing.
Chap_07(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 7: DISPLAY PRINT FACILITY
290
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 8: Problem Determination and Resolution
Common Problems /Solutions
System Reference Guide
Chapter 8
PROBLEM DETERMINATION
AND
RESOLUTION
Common Problems /Solutions
This chapter contains some common questions that are asked when using the Report Management System. A
suggested solution(s) is provided after each problem.
QUESTION:
Where can I find information on the values of the key elements at different points in the
execution of my instruction set?
ANSWER: With each execution of your instruction set, RMS automatically prints a Selected
Dataset(s) Report. This report contains a great deal of valuable information. It is
contained in the sysout from the Q X ST A TS D D statement.
NOTE: Refer to Appendix I for a complete examples of all system reports.
In addition, the system provides detailed descriptions of each dataset
that is selected and a listing of all commands in the instruction set.
The K EY*TR ACE (Diagnostic Record Dump) provides a listing
(within the Selected Dataset(s) Report) of all key element values and all
associated information. These keys are printed in the order the pages
appear in the print dataset. There is a lot of information to be gained
from the key trace data. Each key line printed also contains the Report
ID. This is valuable to tie this key record back to an
IDE NTIFY *REPO RT or Custom Definition panel.
Notice also that any additional keys generated from a
BRO ADCAS T or Send Report panel are also listed.
NOTE: Refer to Appendix I for a complete example of all system reports.
My reports are printing in an unexpected order.
Chap_08(v11r35m1).fm: Revised Sunday, November 24, 2013
ANSWER: Your key elements dictate the order in which your reports are sorted (and
printed). Check to be sure that your current key structure sorts your reports in the
desired order. You can use the S ET R E OR GA N IZ A TI ON P A NE L in DD to
change the order (and length) of your key elements. Refer to the Operator’s Tutorial and Advanced Applications for more information on key structure.
QUESTION:
One of my reports is going into the wrong packet.
ANSWER: Follow the steps below to try to pinpoint the problem.
1. Run the instruction set with the KEY* TRACE (Diagnostic Record
Dump). This will cause the system to print all sort keys during the run
(they will be listed by dataset in order of input).
2. Find the keys in question and examine the values in the keys.
3. Check to see that the proper Report ID is shown for the key and that it
© 2013 Mantissa Corporation. All rights reserved.
291
CHAPTER 8: PROBLEM DETERMINATION/RESOLUTION
QUESTION:
RMS/Online® Version 11.35
Chapter 8: Problem Determination and Resolution
Common Problems /Solutions
System Reference Guide
4.
5.
6.
7.
8.
QUESTION:
matches back to the IDE NTIFY *REPO RT (Custom Report
Definition).
If a BROA DCAST (send report) statement is specified, check to see
if the report is sent to the desired packet. The results of a
BROADCAST command will be shown immediately following the
original key on the Key Trace.
Check to see if the CREAT E*PAC KET (Custom Packaging Panel)
key element values or recipient values match the keys that are being
built.
Check to be sure that the CR EATE* PACKE T (Custom Packaging
Panel) key element values or recipient values match the keys that are
being built.
Be aware that a match on a new CREAT E*PAC KET statement
(Custom Packaging Panel) triggers the creation of a new packet.
Once a packet is closed, it is never re-opened.
How do I get my reports to RMS/DPF?
ANSWER: You must specify the media type SOFTCOPY. For more information, refer to the
Operator’s Tutorial and Advanced Applications
QUESTION:
How do I create a packet that contains just the manifest report?
ANSWER: The CREATE*PACKET command has an optional parameter called GLOBAL*MANIFEST. This parameter will tell the system that the packet being create
with the CREATE*PACKET command should contain only the manifest report.
The DD equivalent is the IN D EX P AC K ET ( Y/ N) ? (Specify “Y”) field on
the Custom Packaging Panel. This option is defined to send the Global Manifest
to print class A with the packet name “MANIFEST”.
PROBLEM:
I have received the following message:
MSG#105 RM0105E UNDEFINED CHANNEL (X”93), EXECUTION TERMINATED
SOLUTION: If you receive this message, it means that RMS has encountered a channel skip
Chap_08(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 8: PROBLEM DETERMINATION/RESOLUTION
in a carriage control that you did not identify with an FCB command. Use the
F OR M* C ON TR O L* B UF FE R command to define the channel skip. The
292
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
Chapter 8: Problem Determination and Resolution
Common Problems /Solutions
System Reference Guide
FCB is used by JES to print a dataset. It is the source for all channel skips for
that print dataset. Refer to the System Command Reference Summary for a list
of the channel command values.
QUESTION:
I want to identify a report by the title (STOCK). However, the title is on the first line (column 50) on all pages, except for one page where it is on line 2 (column 50). How can I
identify this report?
ANSWER: You can identify this report with two IDENTIFY*REPORT commands, as shown
below:
EXAMPLE:
ID E NT I FY *R E PO RT FO R MA T *D AT A 1( 1, 5 0, S TO CK ) RE P OR T *I D( S TO CK )
.
.
.
.
ID E NT I FY *R E PO RT FO R MA T *D AT A 1( 2, 5 0, S TO CK ) RE P OR T *I D( S TO CK )
NOTE: Both of the IDENTIFY*REPORT commands have the same REPORT*ID.
QUESTION:
I received the following JCL message:
“DD STATEMENT MISSING”
ANSWER: Check to see if you have FR E E= CL O SE on a DD statement that you reference
© 2013 Mantissa Corporation. All rights reserved.
293
CHAPTER 8: PROBLEM DETERMINATION/RESOLUTION
Chap_08(v11r35m1).fm: Revised Sunday, November 24, 2013
in a Custom Packaging Panel or OUTPUT*CONTROL statement. If so, remove
this parameter. Also check to see that any D D NA ME referenced in a Custom
Chapter 8: Problem Determination and Resolution
RMS/Online® Version 11.35
Common Problems /Solutions
System Reference Guide
Packaging Panel or O UT PU T *C O NT RO L statement has a corresponding
DD statement in the JCL. It must be in the step that executes the RM80004 program.
PROBLEM:
I received the message “unknown” under the PRINT CTL heading on the Data Set Selection Report.
ANSWER: The carriage control is missing from the dataset after it’s captured by the transport server . Make sure that the indicator for Carriage Control in the DCB
parameter of the DD statement in the creating application JCL indicates the correct machine or ASA carriage control.:
EXAMPLE:
RE C FM =F M [Fixed length with machine carriage control]
RE C FM =F B M [Fixed length and blocked with machine carriage control]
RE C FM =F A [Fixed length with ASA carriage control]
RE C FM =F B A [Fixed length and blocked with ASA carriage control]
QUESTION:
How can I tell the system not to print separator pages between packets?
ANSWER: Specify SE PA R AT O R* PA G ES (0 ) (separator pages zero). If you are using
DD, specify “0” in the SE P P AG E S == > field on the Custom Packaging
Panel.
PROBLEM:
I received the following message:
MSG# 220 RM0220E Command Sequence Error
SOLUTION: This indicates that your commands are not in the required order, as shown
below:
CHAPTER 8: PROBLEM DETERMINATION/RESOLUTION
RUN*OPTIONS
DEFINE*KEY
RECOVER
PRIORITY
TRANSLATE
BROADCAST
COPY
IDENTIFY*REPORT
INSERT*DATA*STREAM
OUTPUT*CONTROL
CREATE*PACKET
FORM*CONTROL*BUFFER
SELECT
PROBLEM:
Each page in one of my packets is duplicated.
SOLUTION: You have performed a B RO A DC AS T (send report) to the same endpoint to
which the report is originally being sent.
PROBLEM:
294
I have received the following message:
© 2013 Mantissa Corporation. All rights reserved.
Chap_08(v11r35m1).fm: Revised Sunday, November 24, 2013
EXAMPLE:
RMS/Online® Version 11.35
Chapter 8: Problem Determination and Resolution
Common Problems /Solutions
System Reference Guide
MSG# 213 RM0213E command TABLE SPACE EXHAUSTED
SOLUTION: You are probably executing a large command stream that has exceeded the
Command Buffer Space. You should increase the size of the buffer space. We
suggest that you increase it by 50 percent, then try running the command
stream again. Increasing the buffer space will increase the size of your program. This may require you to increase the Region on the job card.
PROBLEM:
RMS (RM80004) goes into a loop, performing nothing the first time it’s run.
SOLUTION: You’ve probably attempted to send reports to the RMS/DPF (softcopy) program and the last step of the installation for the Online (RMS/DPF) programs
was not completed correctly. Try re-installing the Online software (or just
rerun the last step to be sure RM80004 is relinked). Refer to the Installation
Guide for more information.
PROBLEM:
I ran RM80004 and got the message “Dataset Not Found”. I know that the dataset was
sent to the repository and did appear in the repository shortly after the run.
SOLUTION: The dataset was probably not yet in the repository at the precise moment
RM80004 was looking for it. There is a method for checking to make sure the
dataset is in the repository before running RM80004. Use Checkpoint Datasets
to check for the desired dataset(s). If the checkpoint is not satisfied, the system
will wait 2 minutes and check again. It will continue checking until the dataset
is found Be sure to delete checkpoints once they’re used. If they are not deleted,
the next run may be started prematurely.
Consider using the RMS Subsystem Interface. Using the SSI you can
be assured that the dataset will be available as soon as the application
has finished processing.
PROBLEM:
I received the following message:
RM0128E INVALID SEGMENT NAME
Chap_08(v11r35m1).fm: Revised Sunday, November 24, 2013
segment name. The segment name must be 8 alphanumeric characters, with no
blanks or special characters. The segment name must begin with an alpha
character to conform to OS/MVS DD naming standards.
© 2013 Mantissa Corporation. All rights reserved.
295
CHAPTER 8: PROBLEM DETERMINATION/RESOLUTION
SOLUTION: You have probably specified too many characters or illegal characters in the
Chapter 8: Problem Determination and Resolution
System Reference Guide
CHAPTER 8: PROBLEM DETERMINATION/RESOLUTION
Chap_08(v11r35m1).fm: Revised Sunday, November 24, 2013
Common Problems /Solutions
RMS/Online® Version 11.35
296
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
RMS Messages
Introduction
Explanation of Message Format
System Reference Guide
Chapter 9
MESSAGES
AND
CODES
RMS Messages
INTRODUCTION
This publication provides an explanation of the format and meaning of the messages and ABEND codes issued by
RMS. It does not contain specific information on the use of facilities in these systems or the options available in each.
These options are described in the System Reference Manuals for these systems.
Explanation of Message Format
All messages issued by the Report Management System adhere to a common format. This format serves as an internal
trace facility that assists in the problem diagnosis and resolution and consists of two components: the message
identifier and the text. The message identifier is an eight (8) character alphanumeric value structured as follows:
RMnnnnt
where:
RM
RMS message prefix.
nnnn
Numeric message code assigned to message text component.
t
Message severity:
C
Critical error with possible compromise of report data. Processing could not be continued.
E
Error-Processing could not be continued
I
Information and system status.
W
Warning, error occurred but processing continued.
The text portion of the message provides a descriptive explanation of the situation that resulted in its being issued.
The text is free form and varies in length.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
EXAMPLE:
RM0001E xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Severity Level
Message Number
System
MESSAGE NUMBER AND TEXT______________________________
EXPLANATION___________________________________
SUGGESTED ACTION__________________________
© 2013 Mantissa Corporation. All rights reserved.
297
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
MESSAGES
RM Codes
RM0000
RM0001
RM0002
Invalid control statement type.
The input command entry preceding this message is invalid. The system issues the message and sets a program return code of 08.
Operator Response: Correct and re-enter the command.
xxxxxxxx Was not found.
Entry xxxxxxxx was not found.
Operator Response: Ensure that the queue dataset selection record contains the correct name and selection criteria.
RMS security processing required but security module
unavailable, execution terminated.
The RMS Access Group Master record indicated that security was active; however, no
security processing routine has been provided. A completion code of 08 is returned.
Operator Response: Re-link the RMS product including the appropriate security
routine, or update Access Group Master record, turning off the security indicator.
RM0003
End of volume.
The current output volume has been dismounted because of a change in output format
(VSE only), a volume terminate record was encountered (VSE only), or because end of file
was reached for the input control file.
Operator Response: Information only.
RM0004
xxxxxxxx, Null file. (VSE only)
RM0007
Checkpoint read for xxxxxxxx FQE number ffffffff has failed, continuing.
The entry xxxxxxxx is a null dataset.
Operator Response: Information only.
Dynamic allocation of name xxxxxxxx FQE ffffffff has failed.
RM0008
RM0009
RM0010
298
Read error accessing xxxxxxxx FQE number ffffffff, page nnnnnnnn.
An error occurred while reading the data file. The system issues the message, takes a snap
dump of relevant control blocks and sets a program return code of 08.
Operator Response: If this occurs in the OUTPUT PHASE of a distribution run,
check that the date being distributed was not archived and purged between the scan
and output phases by another job.
Security violation attempting to access xxxxxxxx/#nnnnn.
A deny access code was returned from the security module.
Operator Response: Processing continues; however, a return code of 04 is posted by
the RMS product upon completion.
xxxxxxxx Was not recovered.
The requested dataset was not found on the archive file.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
Operator Response: Ensure that the correct name was specified in the dataset select
statement and that the correct archive file was processed by RM80001.
RM0017
QUEUE write error during archive purge
RM0018
Repository space almost exhausted. Dataset creation suspended Subsystem=xxxxxxxx.
RM0021
No response from subsystem xxxx, - waiting.
RM0022
RM0023
RM0024
RM0025
RMS is waiting on a response from the xxxx subsystem.
Operator Response: Make sure that the xxxx subsystem is active.
Storage acquisition request error. Processing terminated.
The RM80001 storage management routine encountered an error while attempting to
acquire virtual storage; the message is issued and a program return code of 08 set.
Operator Response: This is typically a short on storage situation. Increase region/
partition size and restart.
Storage acquired - Length = nnnnnnnn, Address = aaaaaaaa.
Information messages issued each time RMS system acquires work area storage.
Operator Response: No action.
Storage release request error, processing terminated.
Error occurred while attempting to free a previously acquired block of storage.
Operator Response: System issues a return code of 08 and terminates. Call Mantissa Product Support.
Error allocating segment xxxxxxxx, output routed to QXPRINT. (OS/
MVS only)
An attempt by RMS/RDC to dynamically allocate the requested SEGMENT has failed.
All output is routed to the default segment.
Operator Response: Verify the SEGMENT command name field to ensure that it
conforms to the OS DD statement name field requirements.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM0026
DDNAME xxxxxxxx omitted from job stream, default is QXPRINT.
(OS/MVS only)
RMS/RDC attempted to route the output for the current segment to the user supplied DD,
specified in the OUTPUT*CONTROL command that was not included in the execution
job control. The output was rerouted to the default SYSOUT QXPRINT.
Operator Response: Include missing statement in next execution cycle.
RM0030
© 2013 Mantissa Corporation. All rights reserved.
Internal archive error - report data left intact.
An internal error occurred while segmentation archival was active. Processing is terminated with a return code of 08.
Deletion of drain trace dataset failed for xxxxxxxx. The RMS controller transport subtask
requested the subsystem to purge a dataset that it was using as a drain indicator. The subsystem failed to find the requested dataset.
Operator Response: Accumulate output listings and contact Mantissa Product Support.
299
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
Deletion of drain trace dataset failed for xxxxxxxx.
The RMS controller transport subtask requested the subsystem to purge a dataset that it
was using as a drain indicator. The subsystem failed to find the requested dataset.
RM0031
Transport Server parameter processing error.
RM0032
kkkkkkkk (wwwwwwww) is invalid.
RM0033
RM0034
The keyword value displayed is invalid. The writer issues the error message and then terminates.
Operator Response: Correct the keyword list value and restart the writer procedure.
Repository version/modification level conflict. Processing terminated.
The file version/modification level does not match that of the program.
System Action: The program terminates.
Operator Response: Contact system administrator.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
This is a general message code and can have any of the following text.
DISTRIBUTION INDEX WRITE FAILURE
Every execution of RM80004 that creates SOFTCOPY or media tracking records creates
an RMSCINDX dataset. At EOJ (end of job), the RMSCINDX dataset is handed to the
RMS control region started task for processing by the INDEX sub-task.
A DISTRIBUTION INDEX WRITE FAILURE message means the INDEX sub-task processing an RMSCINDX dataset has encountered a write error while attempting to add the
index record to the QXRCDS file managed by the task. This may either be the result of a.)
An out of space condition with the dataset, 2.) A hardware error (least likely), or 3.) Errors
caused by having previously written part of the content of the RMSCINDX dataset to the
RXRCDS file.
Operator Response: Once the issue with the QXRCDS file has been resolved and
the control region has been cycled, one (1) DISTRIBUTION INDEX WRITE FAILURE message will be issued for each record that was updated prior to processing
being suspended on the RMSCINDX dataset by the INDEX sub-task.
Internal error. Zero buffer address
The repository access program (UT90066) has encountered
an instance where, due to a damaged file or a storage acquisition failure, the buffer address
token returned to the application is zero.
xxxxx failed for subsystem(ssss). RC=rr.
where xxxxx is Open, Write or Close. The job or started task receiving the error is unable
to communicate with the subsystem specified in the error text.
Operator Response: Ensure a FORMAT start of the subsystem completed successfully the first time the subsystem task was started.
Verify the values specified on the following parameters match:
SUBID
(found in RvvrmSUP member)
300
SSNAME
(found in RvvrmCTP member)
SSNAME
(found in INST02 install job to initialize QXCNTRL file)
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
SSN
(found in CDRMS2 install member from RMSOGEN customization in INST01)
Issue a 'DS' (display status) command to determine if available FQE's (file queue elements) have been exhausted.
If the FQE's in use match the total available all are exhausted and FQE's will need to
be freed using Mantissa backup & restore utilities, or the number of FQE's (file queue
elements) will have to be increased.
Increasing the number of FQE's will require a reformat and reload of the entire content of the repository and is usually NOT a viable option in any production environment. A change to the NUMFQES parameter in the RvvrmSUP member requires a
COLD start of the repository. Before undertaking this task appropriate backups
(RM80001 and RM90007) should be created.
Contact Mantissa Customer Support for assistance if needed.
OUT ADD FAILURE
An Output Server sub-task has encountered a problem while attempting to create an Output Definition using print attribute values entered on the Recover/Print Request panel in
RMS/Online.
Review the output server log to determine the value(s) keyed on the print request (i.e.:
OUTLIM, PAGEDEF, FORMDEF, etc.).
To determine if print request processing has been suspended, or to identify all files currently waiting for processing by the output server, perform a display file command for the
following owner/destination combination:
DF,O=RMSC0005,DEST=RMSC0005
Operator Response: Contact Mantissa Customer Support for assistance if needed.
REPORT VERSION RECORD NOT LOCATED
Expected report version record does not exist and therefore cannot be located.
SCRATCH/PURGE FAILED
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
The Transport Server sub-task failed to delete a base scratch dataset.
RMS opens a transient dataset when data is being drained from JES to ensure the entire
dataset is captured before deleting the dataset from JES.
The SCRATCH/PURGE FAILED message may occur if two transport sub-tasks are servicing the same repository and one of the sub-tasks had already deleted the dataset before
the second sub-task could access the same file for deletion.
Operator Response: Only one (1) TRANSPORT sub-task should be active servicing
a given class, destination or class/destination.
UT90061 has detected a read error on FQE xxxxxxxx RC=yy
System Action: EOF has been forced!
UT90061 has truncated a record for FQE xxxxxxxx RC=yy
System Action: Processing continues.
File xxxxxxxx in program RM10000 has been allocated to yyyyyy.
ORIG STATUS FAILED
An error status was returned from the subsystem.
© 2013 Mantissa Corporation. All rights reserved.
301
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
Route failed. (Retried) SS/Own/Dest/FQE:
ssssssss/oooooooo/ddddddd/ffffffff
Route failed. (Permanent) SS/Own/Dest/FQE:
ssssssss/oooooooo/dddddddd/ffffffff
File xxxxxxxx in program RM10001 has been allocated to yyyyyy.
Transport Server recovery environment enabled.
Transport Server recovery environment failed.
Estae recovery routine entered.
Estae environment suspended. Termination process beginning.
Estae entered with SDWA provided
Estae entered without SDWA provided
Termination processing complete.
JES interface is Process Sysout (PSO).
JES interface is Sysout Application Program Interface (SAPI).
SAPI control (Terminate interface) issued.
Error occurred during despooling - continuing. Dataset Deleted.
Error occurred during despooling - continuing. Dataset retained.
Error occurred during despooling - halt in progress. Dataset retained.
Duplicate Sysout envountered.
Input Error: Interface=SSOBType JES Disp=iedindi
Repository Dataset xxxxxxxx
Resource String=RSC JobName=stJobNme
EOD MISSING. BLOCK REPAIRED
RC=08
PARM FILE READ
Route failed. (Permanent) SSN/O/D/FQE#/RC =
302
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
ssssssss/oooooooo/dddddddd/ffffffff/rr
Scratch/Purge failed! SSN/O/D/FQE#/RC =
ssssssss/oooooooo/dddddddd/ffffffff/rr
Purge failed for appended dataset.
Purge failed for archive dataset.
UT90051 OUTADD FAILURE!
IPWSEGM failed RC/FB= / .
IPWSEGM failed RC/FB= / .
Tape assign error - ASSGN-2. RC/DDNAME=
RM0035
RM0036
Transport Server command processing error.
A command delivered to the Transport server through PARM or MODIFY command is
not valid.
Operator Response: Correct and re-enter the command information.
Transport Server MODIFY command processing error.
Command ignored.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
See message RM0035.
RM0037
Transport Server options accepted.
RM0038
ssssssss Server is waiting for work on xxxxxxxx at yyyyyyyy.
DD/FS dddddddd/ffffffff).
Options entered via PARM or MODIFY processing have been processed successfully.
Operator Response: None.
The control region server ssssssss has entered a wait state because no work is available to
process.
xxxxxxxx = date stamp.
yyyyyyyy = year stamp.
dddddddd = dataset name.
ffffffff = fileset name.
Operator Response: None.
RM0039
ssssssss Server is waiting for work on xxxxxxxx at yyyyyyyy.
DD/FS dddddddd/ffffffff).
The control region server ssssssss has entered a wait state because no work is available to
process.
xxxxxxxx = date stamp.
yyyyyyyy = year stamp.
dddddddd = dataset name.
ffffffff = fileset name.
Operator Response: None.
© 2013 Mantissa Corporation. All rights reserved.
303
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
RM0040
Command processing resulted in a null selection list. Re-enter. (OS/
MVS only)
A start/modify command was entered that caused a null selection criteria list to be generated. The writer issues the message and enters a 2 minute wait state. Upon completion of
the wait, selection list processing is retried.
Operator Response: Enter a modify command with valid selection criteria.
RM0041
Subsystem request error has occurred for subsystem (ssss).
(OS/MVS only)
The Job Entry Subsystem encountered an error while attempting to service a writer
request for work. The writer takes a snap dump, issues the error message and then terminates.
Operator Response: This is a severe error that should be brought to the attention of
a systems programmer. ENSURE that all writer output is available for review.
RM0042
Subsystem response error has occurred for subsystem (ssss).
(OS/MVS only)
The writer detected an error in the Job Entry Subsystem’s response to a request for work.
The writer takes a snap dump of the Request Control Block and of the common writer
work areas, issues the error message, and then terminates.
Operator Response: This is a severe error that should be brought to the attention of
a systems programmer. Ensure that all writer output is available for review. This
could be caused by incorrect DEST request for data movement by this control region.
Check the DEST and CLASS parameters on the EXEC of RM9999 within RMSCTL
control region.
RM0043
Resource ENQ request error. (OS/MVS only)
RM0044
Input sysout file initialization error, QDS = xxxxxxxx.
(OS/MVS only)
Internal writer error. The writer issues message and terminates.
Operator Response: Call Mantissa Product Support.
An error was encountered when at attempt was made to dynamically allocate the named
SYSOUT dataset. The writer takes a snap dump of the Dynamic Allocation Request Block
and the common writer work area, issues the error message, and then shuts down. The
selected dataset is left intact in the Job Entry Subsystem.
Operator Response: This is a severe error that should be brought to the attention of
a systems programmer. Ensure that all writer output is available for review.
RM0045
Input Dataset Dynamic Allocation failed, QDS = xxxxxxxx.
RC=cccc RSC=ssssssss.
An error was encountered when at attempt was made to dynamically allocate the named
SYSOUT dataset. The writer takes a snap dump of the Dynamic Allocation Request Block
and the common writer work area, issues the error message, and then shuts down. The
selected dataset is intact in the Job Entry Subsystem.
cccc = return code
ssssssss = reason code
Operator Response: This is a severe error that should be brought to the attention of
a systems programmer. Ensure that all writer output is available for review.
304
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM0046
File initialization error, processing terminated.
(OS/MVS only)
This is a standard operator console message issued for any file initialization error. It will
be accompanied by a “write to programmer” SYSOUT error message that will further
define the error. The writer issues the message and then terminates.
Operator Response: None.
RM0047
Error during the despooling operation, processing terminated. (OS/
MVS only)
This is a standard operator console message issued for any error that occurs while the
writer is writing a report entry to QXSPOOL. It will be accompanied by a “write to programmer” SYSOUT error message that will further define the error. The writer issues the
message and then terminates.
Operator Response: None.
RM0048
Dataset dynamic deallocation failed, QDS = xxxxxxxx.
(OS/MVS only)
An error was detected when the writer attempted to dynamically unallocate a previously
retrieved SYSOUT dataset. The writer takes a snap dump of the Dynamic Unallocation
Request Block and the common writer work area, issues the error message, and then terminates. The SYSOUT dataset that was being unallocated is left in the Job Entry Subsystem and is deleted from the repository.
Operator Response: This is a severe error that should be brought to the attention of
a systems programmer. Ensure that all writer output is available for review.
RM0049
File termination error, processing terminated.
(OS/MVS only)
This is a standard operator console message issued for any file initialization error. It will
be accompanied by a “write to programmer” SYSOUT error message that will further
define the error. The writer issues the message and then terminates.
Operator Response: None.
RM0052
aaaaaaaaaa Server control file is bbbbbbbb. FSNAME IS ccccccc.
Lock span=#####.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
This is an informational message indicating that the aaaaaaaaaa server is using the RMS
control file bbbbbbbb and the fileset name cccccccc. Lock span is the number of index
write before de-queueing.
RM0061
© 2013 Mantissa Corporation. All rights reserved.
Critical input error. (OS/MVS only)
A critical input error on a selected SYSOUT dataset was trapped by the writer SYNAD
routine. The writer initiates normal end of data set processing, deleting the entry from JES
and retaining that part of the dataset already placed in the repository. This condition could
result from a damaged or incomplete JES dataset resulting from an abnormal operating
system shutdown.
Operator Response: This could be a temporary disk I/O error. The user should
restart the writer procedure. If the error persists, contact a systems programmer.
Ensure all writer output is available for review.
305
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
RM0062
Input error on JES dataset from jjjjjjjj/nnnnnnnn, dataset
nnnnnnnnn, dataset drain terminated.
This message accompanies RM0061 and identifies the dataset causing the error. The
writer issues message and takes a snap dump.
Operator Response: None.
RM0063
Transport server was stopped by the operator during QDS(dddddddd)
drain.
Operator Response: None.
RM0065
Job file control block access error for DDN = xxxxxxx.
(OS/MVS only)
An error occurred when the writer attempted to read the JFCB for the selected dataset. The
writer issues message, takes a snap dump and terminates.
Operator Response: Restart writer.
RM0067
Transport Server is inactive on xxxxxxxx at yyyyyyyy. Utilization ##
percent.
The Transport server has entered an extended wait because no work is available to process.
Operator Response: None.
RM0068
Transport Server is waiting for work on xxxxxxxx at yyyyyyyy. Utilization ## percent.
The Index server has entered await a state because no work is available to process.
Operator Response: None.
RM0069
Transport Server is terminating.
RM0070
Storage for segmentation archival not available.
Processing terminated.
Self-explanatory.
Operator Response: None.
During an RMS/RDC execution with RUN*OPTION archive specified, adequate storage
was not available to perform the archive function.
Operator Response: Increase region size and rerun the RMS/RDC job.
306
RM0071
User exit initialization error, exit processing bypassed.
RM0073
Error acquiring storage for user SMF Exit, processing terminated.
An error occurred while loading a requested user exit. User exit processing is ignored.
Operator Response: Ensure the correct exit name was entered via the keyword
operand EXIT. Also ensure that the exit exists in the correct library. Re-enter exit
request command.
Execution parm specified inclusion of user SMF exit, but insufficient virtual storage was
available for initialization of the parameter area.
Operator Response: The writer execution continues without the user SMF exit.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM0076
Packet xxxxxxxx created for Location llllllllllllllll. Media is
mmmmmmmm.
RM0077
Packet xxxxxxxx has been allocated with DDNAME dddddddd.
RM0079
Packet xxxxxxxx has been appended to the file with DDNAME
dddddddd. Close/Open sequence bypassed.
RM0081
Length error occurred for QDS (nnnnnnnn/#####) records truncated.
RM0090
Control file for index update is xxxxxxxx. Fileset name is ffffffff.
RM0094
aaaaaaaaaa. Allocation failed for SYSOUT dataset.
USER/FT/FS uuuuuuuu/tttttttt/ssssssss.
The writer has detected one or more records of a greater length than indicated in the
opened DCB for named dataset.
Operator Response: Some data may have been lost. Insure that the creating program create the data with a consistent logical record length.
Operator Response: None.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
The dynamic allocation of the SYSOUT dataset failed for subtask aaaaaaaaaa.
USER = User ID
FT = Target subsystem
FS = Fileset
Operator Response: Contact your system administrator.
RM0095
Access Group/ Location/ Report = aaaaaaaa/llllllll
rrrrrrrr/xxxxxxxx.
RM0101
Sort failed, return code = nn.
RM0102
Invalid top-of-form specification.
RM0105
Undefined channel (x”cc”), execution terminated.
© 2013 Mantissa Corporation. All rights reserved.
The sort merge program which is loaded by RMS/RDC has failed with a return code of nn.
The system issues the message and sets a program return code of 08.
Operator Response: Consult the reference documentation for the sort in use at your
installation.
The value specified in the REPORT TOP OF FORM field in the queue dataset select control record must be 1-9, A, B, or C.
Operator Response: Correct the control record and resubmit the job.
RMS/RDC has encountered a channel command in the queue dataset (X”CC” = machine
control character). This channel has not been defined by:
System Action: An FCB command. (OS/MVS and VSE)
or
An FCB named in the FCB NAME field of the queue dataset select record. (VSE)
The system issues the message and sets a program return code of 08.
Operator Response: Make sure that the channel control characteristics of the
dataset(s) being processed are accurately reflected by the FCB command or the
named FCB.
307
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
System Reference Guide
RM0106
RM0108
Data block construct out of bounds. Block skipped.
While deblocking a data read from the repository, a record was found which was less that
the minimum allowed or greater than the maximum allowed. This block will not be processed.
Operator Response: Processing continues.
RM0110
Start scan hh:mm:ss.
RM0111
Start order hh:mm:ss.
RM0112
Start output hh:mm:ss.
RM0113
Definition error(s), map option forced.
RM0114
308
Severe errors, execution terminated.
Errors encountered and indicated by preceding messages have made successful execution
of RMS/RDC improbable. The system issues the message and sets a program return code
of 08.
Operator Response: Correct the indicated errors and resubmit the job.
Information only. Issued at the beginning of the SCAN PHASE of RMS/RDC execution.
Operator Response: None.
Information only. Issued at the beginning of the distribution key sort phase.
Operator Response: None.
Information only. Issued at the beginning of the RMS/RDC output phase.
Operator Response: None.
Error(s) in the current dataset select record has caused the system to force MAPPING of
the current dataset.
Operator Response: Correct the faulty queue dataset select record and resubmit the
job.
End output hh:mm:ss for distribution ddddddddd.
Information only. Issued at the end of the RMS/RDC output phase.
Operator Response: None.
RM0124
Invalid Form Control Field specification.
RM0125
Non-numeric or illogical Form Control line number.
RM0126
Segment invalid or non-numeric key start.
The FCB command contains an invalid channel specification or is formatted improperly.
Operator Response: Ensure that all channel specifications are correct and that the
FCB command contains Cnnn fields which begin in position 4 of the record, and
which are separated by spaces.
The nnn part of the Cnnn channel/line field in the FCB record is either non-numeric or
contains a line number in excess of 255.
Operator Response: Correct the FCB record.
The key start field in the segment command contains a value which is non-numeric or in
excess of 30.
Operator Response: Code the appropriate key start value.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM0127
RM0128
Segment Name Field invalid.
RM0129
Segment statement ignored.
RM0130
Invalid internal request encountered.
RM0136
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
Segment invalid or non-numeric compare length.
The compare length field in the segment command contains a value which is non-numeric
or in excess of 30.
Operator Response: Code the appropriate compare length field.
The segment name must contain only alphanumeric characters.
Operator Response: Replace the invalid characters with acceptable characters.
For reasons previously listed, the most recently listed SEGMENT command has been
ignored.
Operator Response: Correct the indicated errors.
The system encountered an internally generated request code that was invalid. The message is issued, a snap dump taken and a program return code of 08 is set.
Operator Response: Call Mantissa Product Support making sure that the snap dump
and all related executed job logs are available. Attempt to rerun job.
Awaiting checkpoint entry = eeeeeeee. (OS/MVS only)
A dataset select record beginning with the character “@” has been encountered by RMS/
RDC. The system will wait for an indefinite amount of time for the named entry to be
added to the repository.
Operator Response: Information only.
RM0137
Segment rollover start location invalid.
RM0138
Segment endpoint manifest copies invalid.
RM0139
Segment control table space exceeded. Entry ignored.
RM0140
RMS Control Region is ready for communications.
RM0141
aaaaaaaaaa. Call interface failed during bbbbb processing. Status/PID
= cc/dd.
The rollover start location value must be omitted or numeric.
Operator Response: Correct and re-enter.
The number of manifest copies value must be omitted or numeric.
Operator Response: Correct and re-enter.
More segment control commands have been entered than can be stored in the table space
available.
Operator Response: Increase region/partition size and restart.
This is an informational message indicating that the Control Region is operational.
A bbbbb (open/close) call to the subsystem by subtask, aaaaaaaaaa, resulted in a status of
cc for passed parameter dd.
© 2013 Mantissa Corporation. All rights reserved.
309
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
RM0150
Table management failure. Function=Reset/Addition.
Table=aaaaaaaa.
A table management request for the reset or addition of table aaaaaaaa has failed. Allocate
additional storage to the region and rerun the job.
RM0160
RM0172
Primary subsystem tables could not be located.
The primary subsystem (JES) tables could not be located. The RMS JES exits and filter
table cannot be loaded.
Operator Response: Call Mantissa Product Support with your operating system and
JES version/modification levels.
RM0173
GETMAIN failed for Exit Routine control block.
RM0174
S806 for SUBSYSTEM ROUTER => XXXXXXXX
RM0175
SYSOUT ROUTER xxxxxxxx properly installed.
RM0176
JES version mismatch - xxxxxxxx/ yyyyyyyy
RM0177
Integrity information not found in user exit.
RM0178
310
Process code processing failed, execution terminated.
OUTPUT*PROCESS*CODE specified in the RUN*OPTIONS command but insufficient
virtual storage was available to table the names of all selected queue entries. Run will terminate.
Operator Response: Increase the virtual storage available in the region (partition)
and resubmit the RMS/Basic job.
A request for CSA/ECSA failed. The RMS JES Exits cannot be installed.
The RMS JES exit, xxxxxxxx, was not found.
Operator Response: Assure that the JES exits have been linked into an authorized
library. Rerun the install job.
The RMS JES exit xxxxxxxx has been installed.
Operator Response: No action.
The attempt to load an RMS JES exit could not be loaded. The RMS JES exit was compiled under JES V.R.M. xxxxxxxx and loaded under JES V.R.M.
Operator Response: Compile and link the RMS JES exits under the same JES
V.R.M. that they will be loaded under.
The RMS JES exit could not be loaded. Required information in the RMS JES exit could
not be located.
Operator Response: Restore the integrity information in the exit as received from
Mantissa Corporation.
JES XIT control block not found.
The RMS JES exit could not be loaded. The JES Exit Information Table, XIT, could not be
located. This could indicated a non-supported version of JES.
Operator Response: Verify that RMS is compatible with the version of JES that is
running.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM0179
RMS subsystem ROUTER entry point not found.
RM0180
RMS ROUTER xxxxxxxx already properly installed.
RM0181
Refresh Improper - RMS ROUTER not installed.
RM0182
JES EXIT load failed.
RM0183
Local Lock failed for GETMAIN of JES XRT.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM0184
The RMS JES exit could not be loaded. Required information in the RMS JES exit could
not be located.
Operator Response: Restore the $ENTRY JES macro in the exit as received from
Mantissa Corporation.
The RMS JES exit xxxxxxxx could not be loaded. The exit has been previously loaded.
Operator Response: Rerun the INST11 job with the PARM='REFRESH' parameter
included.
The RMS JES exit could not be refreshed - it has not been loaded.
Operator Response: Rerun the INST11 job without the PARM='REFRESH'.
The LOAD of the RMS JES exit failed.
Operator Response: Insure that the JES exits have been linked into an authorized
library. Rerun the INST11 job.
Exclusive use of the RMS/JES tables could not be obtained. This condition may occur if
the INST11 job is run while there is high activity through the RMS JES exits.
Operator Response: Rerun the INST11 job.
SSCT for ssss could not be located.
The control table for subsystem ssss was not active.
Operator Response: Insure the RMS subsystem has been started.
RM0185
GETMAIN failed for RMS SSCT control block.
RM0186
RMSSSCT =xxxxxxxx
RM0187
Parms read were ppppp pppppppp ppppp S= ssss.
RM0188
Cannot allocate storage for JOB/PROC/STEP table.
RM0189
Length of PARMS passed is zero.
© 2013 Mantissa Corporation. All rights reserved.
A request for CSA/ECSA failed. The RMS JES exit cannot be installed.
Operator Response: Rerun the INST11 job when CSA/ECSA is available.
The address of the RMS subsystem control table is xxxxxxxx. This informational message
is printed when PARM='DEBUG' is included in the INST11 job.
Operator Response: None.
The parameters passed from the INST11 job are listed when PARM='DEBUG' is included.
Operator Response: None.
A request for CSA/ECSA failed. The RMS JES exit cannot be installed.
Operator Response: Rerun the INST11 job when CSA/ECSA is available.
No parameters were coded in the INST11 job.
Operator Response: Include parameters in the INST11 job as indicated in the RMS
311
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
Installation Guide.
RM0190
Refresh improper - RMS ROUTER not installed.
The RMS JES exit refresh failed because the JES exit has not been installed.
Operator Response: Rerun the INST11 job without the PARM ='REFRESH' parameters.
RM0191
RMS SYSOUT filter data could not be created.
RM0192
RMS$IN DD could not be opened.
RM0193
RMS ROUTER has been activated as requested.
RM0194
RMS ROUTER has been deactivated as requested.
RM0195
Address of PARMS passed was zero.
RM0196
Router table has xxxxxxxx entries xxxxxxxx
RM0197
xxxxxxxx Refresh completed.
RM0198
RMS lock was on code - Table not loaded.
RM0199
JOB jjjjjjjj PROC pppppppp STEP ssssssss DD dddddddd
CL c DEST eeeeeeee FORM ffff FCB bbbb WTR wwwwwwww.
A request for CSA/ECSA failed. The RMS filter table cannot be loaded.
Operator Response: Rerun the INST11 job when CSA/ECSA is available.
The RMS filter table could not be found.
Operator Response: In RMS/Online, create filter table records prior to running the
INST11 job.
The RMS JES exit has been activated as requested.
Operator Response: None.
The RMS JES exit has been deactivated as requested.
Operator Response: None.
An error occurred attempting to address the parameters passed from the INST11 job.
Operator Response: Correct the parameters in the INST11 job and rerun.
This is an informational message indicating how many entries are available and allocated
in the RMS filter table.
Operator Response: None.
Refresh of the RMS JES exit, xxxxxxxx, was successful.
Operator Response: None.
Exclusive access to the RMS/JES tables could not be obtained.
Operator Response: Rerun the INST11 job.
This is an informational message provided when the trace facility is turned on in RMFILTER.
Operator Response: None.
RM0200
312
Invalid control statement type.
Self explanatory.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
Operator Response: Correct the control record identification field.
RM0201
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM0202
Queue dataset name omitted.
The queue dataset name field in the IDENTIFY*FORMAT/IDENTIFY*REPORT command must contain a full or generic name.
Operator Response: Supply the appropriate name.
Number of copies invalid.
The number of copies field must be omitted or numeric.
Operator Response: Supply the appropriate copy count.
RM0203
Copy group/table ID invalid.
RM0204
Translate/Mod Group ID invalid.
RM0205
APPEND/PIGGYBACK option invalid.
RM0207
Broadcast Group ID invalid.
RM0209
Data line number invalid.
RM0211
Data starting column invalid.
RM0212
Data length field invalid.
RM0213
Command table space exhausted xxxxxxxxxx.
© 2013 Mantissa Corporation. All rights reserved.
The copy group ID references a copy group that does not exist.
Operator Response: Ensure that the group ID table field contains numeric data that
references a defined copy control group.
The translate group ID references a group that does not exist.
Operator Response: Ensure the translate group ID table field references a defined
translate control group.
The piggyback option field in the $I record must contain a blank or ‘P’.
Operator Response: Check the control record for overlapped or incorrectly specified fields.
The broadcast group ID is invalid or the reference broadcast group does not exist.
Operator Response: Ensure that the broadcast group ID field references a defined
broadcast group.
The report line number must be in the range of 01 to 66.
Operator Response: Supply the appropriate line number.
The starting column number of the keyword data is not in the range of 002 to 204.
Operator Response: Supply the appropriate column number.
The length specified for the keyword data must range from 01 to 30.
Operator Response: Supply the appropriate length.
The control record buffer space has been exhausted. No additional control records will be
accepted.
Operator Response: Increase the COMMAND*BUFFER*SPACE on the
RUN*OPTIONS command.
313
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
RM0214
INVALID HEX DATA - VALID RANGE 0-9, A-F.
The data entered does not contain valid hexadecimal characters.
Operator Response: Correct and retry.
RM0215
START COL PLUS DATA LENGTH EXCEEDS MAXIMUM..
RM0220
Command sequence error.
RM0221
Key line number invalid.
RM0222
Key start position invalid.
RM0223
Key Length invalid.
RM0224
Distribution key position invalid.
RM0225
Translate Group ID invalid.
RM0228
Comparison length invalid.
The specified data exceeds the maximum line length..
Operator Response: Correct and retry.
A control record has not been entered in the proper sequence.
POSITIONAL FORMATKEYWORD FORMAT
$T
RUN*OPTIONS
DEFINE*KEY
RECOVER
$M
TRANSLATE
$B
BROADCAST
$C
COPY
$R
$I/K SET(S)
IDENTIFY*REPORT
INSERT*DATA*STREAM
$O/$S SET(S)
OUTPUT*CONTROL/CREATE*PACKET
$F
FORM*CONTROL*BUFFER
QUEUE DATASET
SELECT
SELECT RECORD(S)
314
The report line number is not in the range of 01-88.
Operator Response: Supply the correct key line number.
The key data starting column position is not in the range 002-204.
Operator Response: Supply the appropriate starting column number.
The length specified is not in the range of 01-30.
Operator Response: Supply an acceptable length.
The starting position in the distribution key is not in the range of 01-30.
Operator Response: Supply an acceptable length.
The translate group ID field references a group that does not exist.
Operator Response: Ensure that the group ID field contains numeric data that references a defined translate control group.
The length specified for the data to be compared to the distribution key data is not in the
range of 01-30.
Operator Response: Supply the correct length.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM0229
TARGET/REPLACEMENT length invalid.
RM0231
Storage released for pppppppp. Adr=aaaaaaaa, Len=llllllll.
RM0241
Group ID invalid.
RM0242
Copies invalid.
RM0252
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM0253
The length specified for the data to be substituted for the distribution endpoint key data is
not in the range of 01-30.
Operator Response: Supply the correct length.
Storage released.
Operator Response: Self-explanatory.
The group identifier referenced on the command is invalid.
Operator Response: Correct the GROUP*ID value and resubmit the job.
The value specified for number of copies in the preceding command is either non-numeric
or invalid for the indicated MEDIA*CATEGORY.
Operator Response: Correct the command and resubmit the job.
Comparison length invalid.
The compare length specified is not in the range of 01-30.
Operator Response: Supply the correct length for the comparison.
Search length invalid.
The search length specified is invalid. This field must be numeric and in the length of 0130.
Operator Response: Supply the correct length.
RM0254
No matching manifest Report ID.
RM0255
Report ID is invalid.
RM0256
Manifest control entry space exceeded.
RM0257
Invalid or non-numeric compare length.
RM0258
Invalid or non-numeric comparison start.
© 2013 Mantissa Corporation. All rights reserved.
The REPORT*ID parameter has not been coded on the IDENTIFY*FORMAT or IDENTIFY*REPORT command. If the commands are positional, the report identifier specified
in the $I control statement does not have a corresponding $R control entry.
Operator Response: None.
For previously recorded reasons, the most recent $R record is invalid.
Operator Response: Self explanatory.
A spill has occurred in the report manifest control record storage area.
Operator Response: Subsequent manifest data will be edited, but not stored for processing.
The length field in the $R control record is either non-numeric or would cause comparison
outside the distribution key (keystart + length exceeds maximum key length of 30).
Operator Response: Supply the correct length.
The comparison start field was found to be non-numeric or not in the range of 01
315
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
Operator Response: Review commands as shown in DATASET SELECTION
REPORT. The command in error will have **DIAG** printed to the right, with
detailed information about the error.
RM0259
Control entry error -- processing terminated
An error was detected in the control statements. The remaining control statements are
flushed and processing terminated.
Operator Response: Correct the control statement error and rerun.
NOTE: If there are no diagnostic messages or command errors, it may mean that you have attempted
to create RMS/DPF reports, but you have not specified RMS/DPF in the RUN*OPTIONS
command.
RM0280
Omitted or non-numeric key segment LENGTH/START.
A SEGMENT or CREATE*PACKET command having invalid comparison length/start
data has been encountered. The most probable cause for keyword commands is that no
segment name has been used for comparison.
Operator Response: Correct and resubmit the command.
RM0281
Key field overrun/overlap.
RM0282
Distribution key definition >>> ACCEPTED <<<.
RM0283
Distribution Key Definition >>> REJECTED <<<.
RM0284
Control buffer acquisition failure.
RM0285
Location*ID must be alpha-numeric data.
RM0286
Storage unavailable for complete manifest due to number of reports
and/or copies.
The DEFINE*KEY command contains definition data that causes key segments to overlap or the total length of the key exceeds 30 characters.
Operator Response: Redefine the distribution key so that the fields do not overlap
or exceed the 30-character maximum length.
Operator Response: Self explanatory.
The DEFINE*KEY command has been rejected due to previously listed reasons.
Operator Response: Verify your parameters, correct and retry.
RMS/RDC has unsuccessfully attempted to acquire space for the storage of system commands. System operation continues with the default 80,000 character area.
Operator Response: VSE Increase the partition GETVIS area size.
Self explanatory.
Operator Response: Correct the indicated command and resubmit the job.
During the output phase of RMS/RDC, an attempt to acquire additional storage to account
for reports or copies was unsuccessful. The manifest of one or more packets and the global
manifest will be incorrect. If RUN*OPTION SOFTCOPY is specified, one or more
reports may not be receivable. Run should continue.
Operator Response: RMS/RDC region specification should be increased at least
64K.
316
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM0287
Output key element Name(s) and Location*ID are mutually exclusive.
RM0288
Key element name(s) and Location*ID are mutually exclusive for segmentation.
A translate command specifies both key element names and a LOCATION ID as output.
This is not allowed.
Operator Response: Correct command in error and resubmit the RMS/RDC execution.
Self explanatory. RMS/RDC only allows segmentation to be based on key values or
LOCATION *ID, not both.
Operator Response: Correct command in error and resubmit the RMS/RDC execution.
RM0289
LOCATION*NAME syntax error.
RM0290
Packet pppppppp has been directed to the DD named dddddddd.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM0291
Self explanatory.
Operator Response: Correct command in error and resubmit the RMS/RDC execution.
Self explanatory.
Internal error, selected ssssssss but read xxxxxxxx.
Self explanatory.
RM0292
Media*Category “SOFTCOPY” not valid for global manifest segment.
RM0293
Multiple copies not allowed for this Media*Category, set to 1 copy.
RM0294
aaaaaaaaaa Index not created because object sentinel invalid.
bbbbbbbb/cccccccc.
The preceding CREATE*PACKET command indicated both “MEDIA*CATEGORY
(RMS/DPF)” and GLOBAL*MANIFEST, which is invalid. The GLOBAL*MANIFEST
can only be directed to a hard copy type MEDIA*CATEGORY.
Operator Response: Correct the CREATE*PACKET command and resubmit the
RMS/RDC job.
The preceding CREATE*PACKET command indicated both “MEDIA*CATEGORY
(RMS/DPF) and COPIES, which is invalid.
Operator Response: Correct the CREATE*PACKET command and resubmit the
RMS/RDC job.
The sentinel value, RMS-W, was not present in the Report Index Detail Record. The
dataset is purged.
aaaaaaaaaa = sub-task name
bbbbbbbb = owner name in the FQE
cccccccc = destination name in the FQE
Operator Response: Contact your system administrator.
RM0295
dddddddddd Location Report Record write has failed on xxxxxxxx at
tttttttt.
An attempt to write this record has failed.
© 2013 Mantissa Corporation. All rights reserved.
317
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
ddddddddddd = dataset
xxxxxxxx = task name / external writer name
tttttttt = time
Operator Response: Run IDCAMs and verify that the file in question (the report
control dataset) is no out of space.
RM0296
dddddddddd Report version Record write has failed on mm/dd/yy at
hh:mm:ss.
An attempt to write this record has failed.
Operator Response: Run IDCAMs and verify that the file in question (the report
control dataset) is no out of space.
318
RM0297
Purge Server is waiting for work on mm/dd/yy at hh:mm:ss.
RM0299
Archive Server has been attached.
RM0300
Archive server has been detached.
RM0301
Archive server has ended.
RM0302
Control region is active. Version/mod is vvmm, Subsystem is ssssssss.
RM0303
RMS controller must be in an APF authorized library.
RM0304
Transport server has ended. (ssssssssss)
RM0305
Transport server has been detached.
RM0306
Purge server has ended. (ssssssssss)
The Purge server has entered await a state because no work is available to process.
Operator Response: None.
The Archive Server has been attached by the RMS controller main task.
Operator Response: None.
The Archive Server has been detached by the RMS controller main task.
Operator Response: None.
Self-explanatory.
The RMS control region is now active. vvmm is the version modification level of the system. ssssssss is the subsystem identification for the control region.
The RMS control region must be installed in an APF authorized library for the external
writer interface to operate.
Operator Response: Ensure that the controller programs listed in the RMS control
region PROC are resident in an APF authorized library.
The control region main task has recognized the termination of the transport server.
ssssssss will be Normally or Abnormally depending on the termination condition.
Operator Response: If Abnormally is the ending status, examine other messages to
determine the cause.
Self-explanatory.
The control region main task has recognized the termination of the purge server. ssssssss
will be Normally or Abnormally depending on the termination condition.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
Operator Response: If Abnormally is the ending status, examine other messages to
determine the cause.
RM0307
RM0308
RM0309
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM0310
Purge server has been detached.
Self-explanatory.
Control region has ended. (ssssssssss)
The control region main task has ended. ssssssss will be Normally or Abnormally depending on the termination condition.
Operator Response: If Abnormally is the ending status, examine other messages to
determine the cause.
Transport server has been attached.
Self-explanatory.
Purge server has been attached.
Self-explanatory.
RM0311
Index server has ended. (ssssssssss)
RM0312
Index server has been detached.
RM0313
Index server has been attached.
RM0314
Output server has been attached.
RM0315
Output server has been detached.
RM0316
Output server has ended. (ssssssssss)
RM0317
RMS interface. - IDENTIFY failed. RC=cc
© 2013 Mantissa Corporation. All rights reserved.
The control region main task has recognized the termination of the Index server. ssssssss
will be Normally or Abnormally depending on the termination condition.
Operator Response: If Abnormally is the ending status, examine other messages to
determine the cause.
Self-explanatory.
Self-explanatory.
Self-explanatory.
Self-explanatory.
The control region main task has recognized the termination of the Output server. ssssssss
will be Normally or Abnormally depending on the termination condition.
Operator Response: If Abnormally is the ending status, examine other messages to
determine the cause.
The RMS XPPC facility has attempted to IDENTIFY to POWER/VSE. The IDENTIFY
has failed due to the return code listed.
Operator Response: Consult the appropriate VSE manual on the XPPC facility to
diagnose the reason for failure of the IDENTIFY.
319
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
320
System Reference Guide
RM0318
JES to RMS interface. - Error in CONNECT. RC=cc
RM0319
JES to RMS interface. - Error in TERMINATE. RC=cc
RM0320
JES to RMS interface. - RC=cc REA=yy.
RM0321
JES to RMS interface. - Error in SENDR.
RM0322
JES to RMS interface. - VSE/Power has been terminated.
RM0323
JES to RMS interface. - VSE RC=cc.
RM0324
JES to RMS interface. - Error in DISCONNECT. RC=cc.
RM0325
JES to RMS interface. - VSE/Power termination in progress.
RM0326
JES to RMS interface. - Error in SENDR (WAIT).
RM0327
JES to RMS interface. - VSE RC=cc
The RMS XPPC facility has attempted to CONNECT to POWER/VSE. The CONNECT
has failed due to the return code listed.
Operator Response: Consult the appropriate VSE manual on the XPPC facility to
diagnose the reason for failure of the CONNECT.
The RMS XPPC facility has attempted to TERMINATE the connection to POWER/VSE.
The TERMINATE has failed due to the return code listed.
Operator Response: Consult the appropriate VSE manual on the XPPC facility to
diagnose the reason for failure of the TERMINATE.
The RMS XPPC facility has failed for reasons previously listed.
Operator Response: Consult the appropriate VSE manual on the XPPC facility to
diagnose the reason for failure.
The RMS XPPC facility has attempted a SENDR to POWER/VSE. The
OPERATION has failed.
Operator Response: Consult the appropriate VSE manual on the XPPC facility to
diagnose the reason for failure of the SENDR.
The interface has been terminated due to reasons previously listed.
The RMS XPPC facility has attempted a request from POWER/VSE. The OPERATION
has failed.
Operator Response: Consult the appropriate VSE manual on the XPPC facility to
diagnose the reason for failure of the request.
The RMS XPPC facility has attempted a DISCONNECT from POWER/VSE. The OPERATION has failed.
Operator Response: Consult the appropriate VSE manual on the XPPC facility to
diagnose the reason for failure of the DISCONNECT.
The RMS XPPC facility has attempted to communicate with a POWER/VSE system that
is in the process of termination. The operation cannot continue for this reason.
The RMS XPPC facility has attempted a SENDR to POWER/VSE. The
OPERATION will be retried after a wait of 2 minutes.
The RMS XPPC facility has attempted a request from POWER/VSE. The OPERATION
has failed.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
Operator Response: Consult the appropriate VSE manual on the XPPC facility to
diagnose the reason for failure of the request.
RM0328
JES to RMS interface. - VSE/Power termination in progress.
RM0329
JES to RMS interface. - Waiting for connection to VSE/Power XPCC
interface.
The RMS XPPC facility has attempted to communicate with a POWER/VSE system that
is in the process of termination. The operation cannot continue for this reason.
The RMS XPPC facility has attempted a CONNECT to POWER/VSE which is not ready
to receive connections.
Operator Response: The operation will be retried on 2 minute intervals until the
connection is successful.
RM0330
JES to RMS interface. - Error reading dataset. Job=aaaaaaaajnum=bbbbbb.
RMS detected an error while reading a dataset from JES for job aaaaaaaa, job number
bbbbbb.
RM0331
RM0331 Allocation failed for checkpoint dataset.
RM0336
aaaaaaaaaa server has been attached.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM0337
Dynamic allocation of the checkpoint dataset failed.
System Action: Processing is terminated.
Operator Response: The checkpoint dataset DD name is QXRQDS. The dataset
name is assigned in the INST02 job during installation. The checkpoint dataset must
be a cataloged dataset.
This is an informational message indicating that the aaaaaaaaaa server has been successfully attached.
aaaaaaaaaa server is waiting for work on mm/dd/yy at hh:mm:ss
This is an informational message indicating that the aaaaaaaaaa server is operating properly.
RM0338
aaaaaaaaaa server has ended. (bbbbbbbbbb)
RM0339
aaaaaaaaaa server has been detached.
RM0444
aaaaaaaaaa BASE processing for bbbbbbbbbb. mm/dd/yy at
hh:mm:ss. DD/FS eeeeeeee/ffffffff).
This is an informational message indicating that the aaaaaaaaaa subtask has ended normally.
This is an informational message indicating that the aaaaaaaaaa subtask has been
detached.
This is an informational message indicating that the aaaaaaaaaa subtask is processing a
base dataset for distribution run number bbbbbbbbbb using the RMS control file eeeeeeee
and fileset name ffffffff.
© 2013 Mantissa Corporation. All rights reserved.
321
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
System Reference Guide
RM0445
aaaaaaaaaa UPDT processing for bbbbbbbbbb. mm/dd/yy at
hh:mm:ss. DD/FS cccccccc/dddddddd).
This is an informational message indicating that the aaaaaaaaaa subtask is processing an
update for distribution run number bbbbbbbbbb using the RMS control file cccccccc and
fileset name dddddddd.
RM0446
tttttttttt aaaaaaaaaa Begin/End for bbbbbbbbbb on mm/dd/yy at
hh:mm:ss. DD/FS cccccccc/dddddddd).
This is an informational message indicating that tttttttttt task aaaaaaaaaa subtask is processing a report for distribution run number bbbbbbbbbb using the RMS control file
cccccccc and fileset name dddddddd.
RM0447
aaaaaaaaaa process complete for definition bbbbbbbbbbbbbbbb on
mm/dd/yy at hh:mm:ss.
This is an informational message indicating that the aaaaaaaaaa subtask has completed
processing on location name bbbbbbbbbbbbbbbb.
RM0448
aaaaaaaaaa Index not created because object is empty. bbbbbbbb/
cccccccc.
The subtask aaaaaaaaaa could not create an index because the dataset was empty for
owner bbbbbbbb and destination cccccccc.
RM0702
Value outside acceptable limits
value=keyword.
The value listed for the indicated parameter is outside the acceptable limits.
Operator Response: Correct and resubmit.
RM0703
RM0704
A parameter value field has a missing open or close parentheses. All parameter values
must be enclosed in parentheses.
Operator Response: Correct and resubmit.
Sub-list syntax/excessive entries.
A sublist value field has either an excessive number of sublist entries or a missing close
parentheses or comma.
Operator Response: Correct and resubmit.
RM0705
Syntax error. Missing command.
RM0706
Keyword not recognizable.
RM0707
322
Syntax error. Missing open/close paren.
The first value found was not a valid command.
Operator Response: Correct and resubmit.
The indicated keyword is not valid for the command.
Operator Response: Correct and resubmit.
Maximum value length exceeded for xxxxxxxx.
The length of the value for the indicated parameter exceeds the allowable length.
Operator Response: Correct and resubmit.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM0708
Specified Instruction Set not available.
RM0709
Copy count invalid. Defaulting to 01.
RM0996
Initialization no longer performed by this program. Consult install
manual.
The copy count was invalid and has been reset to 1.
Operator Response: Correct and resubmit.
The preprocessing exit detected an invalid media type.
RUN*MODE(INITIAL) is not supported by the RM80001/RM80004 program. Initialization of the repository is performed by the RMS subsystem, OPTION=FORMAT.
Operator Response: Remove the RUN*MODE(INITIAL) statement.
RM1000
RM1001
Cannot issue STAX macro.
RM1002
** Attention interrupt **.
RM1004
Parse RC=04 - Incomplete parameters.
RM1005
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
No parameters passed.
This message does not apply to command processors. The message is issued if the parameter string passed to the program executing as a call-program is omitted or contains only
delimiters (spaces/commas)
System Action: Execution is terminated.
RM1006
RM1007
© 2013 Mantissa Corporation. All rights reserved.
The program tried to set up an attention exit but received a non-zero return code from the
STAX macro.
System Action: Execution is terminated.
This message is issued when the PA1 key is entered.
System Action: See accompanying message.
A return code of 04 (decimal) was returned from the parse service routine. This message
will be issued if you make an error in the calling sequence and your profile indicates no
prompt.
System Action: Execution is terminated.
Parse RC=08 - Attention interrupt.
The PA1 key was hit execution of the PARSE service routines.
System Action: Execution is terminated.
Parse RC=12 - Programming error.
During execution of the parse service routines, a return code of 12 (decimal) was returned.
Please consult your system programming group if you receive this message.
System Action: Execution is terminated.
Parse RC=16 - No storage available.
The parse service routines could not complete because of a storage shortage. Please notify
your system programming group or use a larger size operand when logging onto TSO.
System Action: Execution is terminated.
323
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
System Reference Guide
RM1008
Parse RC=20 - Validation routine requested halt.
RM1009
Parse RC=24 - Programming error.
RM1010
DD statement for SYSIN missing.
RM1011
RM1012
RM1013
RM1014
RM1015
324
This message is included for future needs and is not used at the moment. If it is issued,
please notify your system programming group.
System Action: Execution is terminated.
During execution of the parse service routines, a return code of 24 (decimal) was returned.
Please consult your system programming group if you receive this message.
System Action: Execution is terminated.
This message does not apply to command processors. The program executes as a call-routine and the parameter string indicates that parameter input should be taken from the
SYSIN dataset. This dataset has not been allocated.
System Action: Execution is terminated.
No F1DSCB for SYSIN-dataset.
This message does not apply to command processors. The program executes as a call-routine and the parameter string indicates that parameter input should be taken from the
SYSIN dataset. This dataset is allocated but does not physically exist.
System Action: Execution is terminated.
Cannot open SYSIN.
This message does not apply to command processors. The program executes as a call-routine and the parameter string indicates that parameter input should be taken from the
SYSIN dataset. This dataset is allocated but could not be opened.
System Action: Execution is terminated.
Invalid DCB information for SYSIN.
This message does not apply to command processors. The program executes as a call-routine and the parameter string indicates that parameter input should be taken from the
SYSIN dataset. This dataset, however, does not conform to the attributes of a SYSIN
dataset; i.e., 80 bytes fixed records.
System Action: Execution is terminated.
Parameter WORKAREA full.
This message does not apply to command processors. The program executes as a call-routine and the parameter-input from the SYSIN-dataset is too excessive to be held within the
work area in the program. This area is big enough to hold any valid combinations of
parameters; correct your input.
System Action: Execution is terminated.
SYSIN contains no parameters.
This message does not apply to command processors. The program executes as a call-routine and the parameter-input from the SYSIN-dataset contains only comments and blank
records or was completely empty. Correct your input.
System Action: Execution is terminated.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
System Reference Guide
RM1016
Unbalanced parenthesis - begins.
RM1017
Unknown keyword found - begins.
RM1018
Keyword must have operand - xxxx.
RM1019
Keyword takes no operand -xxxx.
RM1020
No active RMS subsystem found.
RM1021
ESF subsystem does not exist - xxxx.
RM1022
ESF subsystem is not active - xxxx.
RM1023
RM1024
© 2013 Mantissa Corporation. All rights reserved.
This message does not apply to command processors. The program found a syntax error in
the parameters. The number of left parenthesis must equal the number of right-parenthesis.
System Action: Execution is terminated.
This message does not apply to command processors. The program found an unassigned
keyword within the parameters. The first 8 bytes of the keyword in question replaces the
'xx....xx' in the message.
System Action: Execution is terminated.
This message does not apply to command processors. The program found a keyword with
no operand attached; the parameter syntax requires that this keyword must be specified
with an operand entry.
System Action: Execution is terminated.
This message does not apply to command processors. The program found a keyword with
an operand attached. The parameter syntax requires that this keyword must be specified
without an operand entry.
System Action: Execution is terminated.
The program was attempting to create an RMS spool file, but no RMS subsystems have
been activated to process the OPEN request. You must wait until RMS has been started or
you must use the SYSOUT option to create a JES spool file instead.
System Action: Execution is terminated.
The program was attempting to create an ESF spool file using a specific ESF subsystem,
but the name given in the SUBSYS parameter is unknown in the system. You must use the
SYSOUT option to create a JES spool file instead.
System Action: Execution is terminated.
The program was attempting to create an ESF spool file using a specific ESF subsystem,
but the ESF subsystem named in the SUBSYS parameter is not active.
System Action: Execution is terminated.
Cannot open SYS1.IMAGELIB.
The program received a non-zero return code from the IMGLIB OPEN MACRO. Please
contact the system programming group.
System Action: Execution is terminated.
FCB could not be found - ‘FCB2xxxx’.
The forms control buffer specified in the FCB parameter could not be found.
System Action: Execution is terminated.
325
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
System Reference Guide
RM1025
RM1026
RM1027
The program could not obtain sufficient working storage. Specify a larger size in the size
parameter in the logon request to TSO.
System Action: Execution is terminated.
No input source specified.
The program could not determine which input data to act upon. Use the keywords
DDNAME and DSNAME to specify the input dataset.
System Action: Execution is terminated.
Dataset is not cataloged - xx..xx.
The dataset name specified as input could not be located. Ensure the spelling is correct and
if so, use the VOLUME keyword.
System Action: Execution is terminated.
RM1028
Dynamic allocation failed: xxxx-xxxx.
RM1029
Invalid dataset name.
RM1030
Volume is not mounted.
RM1031
DD statement missing - xxxxxxxx.
RM1033
Unexpected Return Code from DEVTYPE-MACRO - RC=xx.
RM1034
RM1035
326
Insufficient storage available.
The program tried to perform dynamic allocation against the dataset you named in the
DSNAME - parameter but received a non-zero return code. xxxx-xxxx is replaced with
error/info codes from the DYNALLOC request block. Refer to the OS Manual SPL: Job
Management for a description of these codes.
System Action: Execution is terminated.
The dataset name given by the DSNAME parameter is not syntactically correct.
System Action: Execution is terminated.
The VOLUME holding the dataset named in the DSNAME parameter is not mounted and
you do not have mounting authorization.
System Action: Execution is terminated.
The dataset named by the DDNAME parameter is not allocated.
System Action: Execution is terminated.
The program tried to obtain device characteristics for the device holding the input dataset
but received a non-zero return code from the DEVTYPE MACRO. 99 is replaced by the
return code in decimal.
System Action: xecution is terminated.
Device is not DASD.
The input dataset is a member of a partitioned dataset but the device on which the dataset
resides is not a direct access device.
System Action: Execution is terminated.
Cannot open file as library.
The input dataset is a member of a partitioned dataset but the dataset could not be opened
using the BPAM access method.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
System Action: Execution is terminated.
RM1036
RM1037
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM1038
Member not found - xxxxxxxx.
The input dataset is a member of a partitioned dataset but the member could not be found
in the dataset directory. If the member name reads unknown then the error occurred during
END-OF-VOLUME switching for a concatenated dataset.
System Action: Execution is terminated.
Dataset contains no CC.
The CCHAR keyword was used in the processing specifications for the dataset indicating
that embedded control characters (ASA or MACHINE) should be honored, but the dataset
contains no such control characters.
System Action: Execution continues using single spacing mode.
I/O-error -xx....xx.
An I/O error occurred during processing of the dataset. xx....xx is replaced by bytes 50127 of the informational message returned from the SYNADAF MACRO.
System Action: Execution is terminated.
RM1039
Dynamic unallocation failed: xxxx-xxxx.
RM1040
Return Code from ESFOPEN is C'xx'.
RM1041
Return Code from ESFWRIT is C'xx'.
RM1042
The program tried to perform dynamic allocation against the dataset previously allocated,
but received a non-zero return code. xxxx-xxxx is replaced with the error/info codes from
the DYNALLOC request block. Refer to the OS Manual SPL: Job Management for a
description of these codes.
System Action: Execution is terminated.
The program tried to OPEN an ESF spool file but received a non-blank return code from
ESF. xx is replaced by the code returned and is explained in the ESF Manual messages and
codes.
System Action: Execution is terminated.
The program tried to write a line to an OPEN ESF spool file but received a non-blank
return code from ESF. The code is explained in the ESF Manual messages and codes.
System Action: Execution is terminated.
Output limit exceeded.
The estimated number of print lines is about to be exceeded and no further writing will be
done. You must increase the value specified in the OUTLIM parameter.
System Action: Execution is terminated.
RM1043
Return Code from ESFCLOSE is C'xx'.
RM1044
Cannot allocate spin-off dataset - xxxx-xxxx.
© 2013 Mantissa Corporation. All rights reserved.
The program tried to CLOSE an OPEN ESF spool file, but received a non-blank return
code from ESF. The code is explained in the ESF Manual messages and codes.
System Action: Execution is terminated.
The program tried to dynamically allocate a spin-off dataset but received a non-zero return
327
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
code. xxxx-xxxx is replaced with the error/info codes from the DYNALLOC request
block. Refer to the OS Manual SPL: Job Management for a description of these codes.
System Action: Execution is terminated.
RM1045
No destination specified.
RM1046
Invalid or missing destination.
RM1050
Cannot open VSAM file - xxxxxxxxxxxx.
RM1051
VSAM read error.
RM1052
Cannot open SYSIPT parm file.
RM1053
RM1054
An invalid printer destination was specified.
System action:
VSAM file could not be opened, VSAM object not TYPE CLUSTER, or TYPE DATA.
System Action: Execution terminates.
ERROR WHILE READING VSAM file.
System Action: Execution terminates.
Parm field specified SYSIN, but in-stream parameter file cannot be opened, assigned
ignore (DOS only).
System Action: Execution terminates.
FCB load failure.
Error while loading FCB (DOS only).
System Action: Execution terminates.
File name missing - xxxxxxx.
Specified DDNAME not specified in an DBDL statement.
System Action: Execution terminates.
RM1055
Cannot open SYSIPT data file.
RM1056
Dataset not in catalog - xxxxxxxx.
RM1057
RM1060
328
No printer destination was specified. This is a required parameter.
DDNAME field specified SYSIPT, but in-stream data file cannot be opened, assigned
ignore (DOS only).
System Action: Execution terminates.
Error return from SHOWCAT call.
System Action: Execution terminates.
Dataset type invalid - xxxxxxxxxxxx.
Dataset is not a CLUSTER or DATA component.
System Action: Execution terminates.
Margin specification(s) ignored - cannot determine page length
You have requested one or two margin area(s) to be printed but have not supplied informations regarding the length of the page. Use either the PAGELEN or the FCB keyword to
supply this information.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
System Action: Execution continues.
RM1061
RM1070
The program could not allocate a spin-off dataset with a DESTINATION name of 'xxxx'
because this name has not been defined to the primary spooling system. Have your system
programming group DEFINE the requested ESF subsystem to JES or use another ESF
subsystem (use the SUBSYS keyword).
System Action: Execution is terminated.
Cannot open directory.
Cannot OPEN directory for a PO-dataset for LIST/PRINT processing
System Action: Execution terminates.
RM1071
No members in dataset - xxxxxx.
RM1077
SYSOUT dataset opened.
RM1078
Cannot open SYSOUT dataset.
RM1079
SYSOUT dataset closed - 99999999 records.
RM1080
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
Dest name ‘xxxxxxxx’ unknown.
The dataset specified for the PRINTOFF LIST/PRINT processing does not contain any
members
System Action: Execution continues using next dataset in list (if any).
This is an informational message stating that the SYSOUT dataset, which you requested to
be created, has been successfully opened.
System Action: Execution continues.
The program could not OPEN the SYSOUT dataset just allocated. Please contact your
system programming group.
System Action: Execution is terminated.
This is an informational message stating that the SYSOUT dataset has been successfully
CLOSED and made available for JES processing.
System Action: Execution continues.
CCHAR specification invalid for AWS - single spacing used.
This message APPLIES to TS/2 processing only. The CCHAR keyword was used in the
processing specifications for the TS/2 AWS. This indicates that embedded control characters (ASA or MACHINE) should be honored, but the AWS holds no such control characters.
System Action: Execution continues using single spacing mode.
RM1081
AWS is empty.
RM1082
Unexpected ReturnCode reading AWS - RC=99.
© 2013 Mantissa Corporation. All rights reserved.
This message applies to TS/2 processing only. The TS/2 AWS was specified as the input
dataset but it contains no records.
System Action: Execution is terminated.
This message applies to TS/2 processing only. The TS/2 AWS READ routine returned a
non-zero return code during sequential AWS processing - 99 is the decimal code returned.
System Action: Execution is terminated.
329
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
System Reference Guide
RM1083
RM1093
This message applies to TS/2 processing only. The TS/2 allocation routine was invoked to
allocate the device holding the input dataset but the routine returned a non-zero return
code. The code returned replaces the 99 in the message.
System Action: Execution is terminated.
Spool file #xxxxxx xxxxxxx - 99999999 records.
This is an informational message stating that the ESF spool file has been successfully
CLOSED. The message also indicates the ESF CLOSE option: If the file is CLOSED, the
file is scheduled for print processing at the DESTINATION assigned to the file; if the file
is held the file is not scheduled for print processing until it is manually released; if the file
is deleted it is removed from the ESF print queue because it was empty.
RM1094
All column specification could not be processed.
RM1095
Spool file #999999 opened.
RM1097
The storage available to the program did not allow for all column ranges to be processed.
System Action: Execution continues.
This is an informational message stating that an ESF spool file has been successfully
opened. The sequence number assigned to the file must be used when manipulating the
spool file at a later time.
System Action: Execution continues.
Parameter error - xx....xx.
The operand of the keyword substituting xx....xx.is in error due to invalid length or contents.
System Action: Execution terminates.
RM1098
Cannot open file as QSAM dataset.
RM1099
No FORMAT1 LABEL found - xxxxxxxxxxxx.
RM1100
Only 1 operand for - xxxx (keyword).
RM1101
RM1102
330
Unexpected Return Code from TS/2 allocation - RC=99.
The input dataset could not be opened for QSAM processing - Please contact your system
programming group.
System Action: Execution terminates.
The input dataset does not physically exist.
System Action: Execution terminates.
Range is not allowed for this operand.
System Action: Execution is terminated.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
Range invalid for - xxxx (keyword).
Range is invalid for this operand.
System Action: Execution is terminated.
Opr. not numeric - xxxx (keyword).
The operand must be numeric.
System Action: Execution is terminated.
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM1103
Opr. not alphanum - xxxx (keyword).
RM1104
Opr. too long - xxxx (keyword).
RM1105
The operand must be alphanumeric.
System Action: Execution is terminated.
The operand is too long.
System Action: Execution is terminated.
Num out of range - xxxx (keyword).
The operand is numeric but its value is invalid.
System Action: Execution is terminated.
RM1106
Invalid sequence number.
RM1150
-nodename-EZA1617I nnnnn bytes transferred in nn.nnn
seconds.
The sequence number is invalid.
System Action: Execution is terminated.
When TCP/IP FTP completes a file transfer to another node, EZA1617I is issued to show
the bytes and transfer time. See IBM manuals for a complete explanation of EZA1617I.
RMS/Spool echoes this message to the console and puts the nodename of the receiving
report(file) with the message.
Operator Response: No operator action is suggested.
RM1151
FTP node xxxxx trouble. Node is not accessible and will be retried in a
few seconds.'
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
TCP/IP FTP could not contact the receiving node(xxxxx) or a transmission error occurred.
Operator Response: Make sure that the receiving node is ready to receive the transmission. The transmission will be retried in a few seconds(12). If the retry process is
not desirable, then a P,xxxx command can be sent to the Spool address space to shut
down the node, but then a S,xxxx command will have to be entered to restart the
receiving node.
RM1152
ESFFTP input parm error, please correct.
RM1153
Subsystem Communications Error.
RM2000
DD statement missing - SYSPRINT.
© 2013 Mantissa Corporation. All rights reserved.
The ESFFTP program has a parm error. The program can be located in the started procedure.
Operator Response: Correct the parm error. An example parm would look like this
PARM=’-,SEVEPC’, where - is the comchar of RMS/Spool and SEVEPC is the
nodename of the receiving TCP/IP node.
The ESFFTP program was unable to communicate with the RMS subsystem.
Operator Response: Contact your system administrator to verify enough communications channels are defined.
The ESFSPTP utility has failed because the SYSPRINT DD statement is missing.
Operator Response: Add a valid SYSPRINT DD statement to the ESFSPTP job and
rerun.
331
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
RM2001
RM2002
RM2003
RM2004
Cannot open file - SYSPRINT.
The ESFSPTP utility has failed because the SYSPRINT cannot be opened.
Operator Response: Correct the SYSPRINT DD statement in the ESFSPTP job and
rerun.
No parameters passed.
The ESFSPTP utility has failed because the required parameters are missing or incorrect.
Operator Response: Correct the parameters in the ESFSPTP job and rerun. The
xFnnn parameter and the SUBSYS=xxxx parameter are required.
Error in parameters - Begins ''
''.
The ESFSPTP utility has failed because the parameters coded are incorrect.
Operator Response: Correct the parameters in the ESFSPTP job and rerun.
N-File# O-File# Filename Dest Form FCB. Q Cpy Lines Stat Time
Error Programmers Name.
This is an informational message header describing the files the ESFSPTP utility has
backed up or restored.
RM2005
Backup function selected Date: yy/ddd - Time: hh:mm:ss.
Load function selected Date: yy/ddd - Time: hh:mm:ss.
This is an informational message indicating that the ESFSPTP utility backup/load function
has been selected.
RM2006
332
ESF subsystem is not available.
The particular RMS subsystem, passed as the SUBSYS=xxx parameter, is not currently
active.
Operator Response: Either start the requested RMS subsystem or correct the SUBSYS=xxx parameter and rerun the job.
RM2007
Index file not allocated - Listing ignored.
RM2008
Cannot open file - xxxxxxxx.
RM2009
ESFSTAT Return code is xx.
RM2010
DD statement missing - xxxxxxxx.
The INDEX dataset has not been allocated.
Operator Response: If a list RMS files successfully processed is desired, add the
INDEX DD statement to the job and rerun.
The INDEX, BACKUP or LOAD dataset cannot be opened.
Operator Response: Correct the specific DD statement and rerun the job.
The RMS subsystem returned an unexpected return code of xx to an ESFSTAT request.
Operator Response: Look up the return code in the RMS System Reference Manual
under "Call Status Codes - From ESFSTAT/ESFSTAC Interface".
The ESFSPTP utility has failed because the xxxxxxxx DD statement is missing.
Operator Response: Add a valid xxxxxxxx DD statement to the ESFSPTP job and
rerun.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM2012
Parameter value error'.
RM2013
Backup file has invalid format'.
RM2014
ESFSPTP ended - xxxxxxxx file(s) dumped/loaded.
RM2015
Parameters: xxxx, yyyy, zzzz, . . .
RM2016
Processing backup dataset created on Date:mm/dd/yy.
RM2017
RM5000
RM5001
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM5002
The RMS subsystem returned "Parameter Error" return code.
Operator Response: Call Mantissa Product Support.
The ESFSPTP utility has failed because an invalid format was specified on the BACKUP
DD statement.
Operator Response: The BACKUP dataset must be specified as a sequential dataset
with a record format of VB.
This is an informational message indicating that the ESFSPTP utility backup/load function
has completed.
This is an informational message indicating the parameters that were passed to the ESFSPTP utility.
This is an informational message indicating the date of the backup dataset being processed
by the ESFSPTP utility.
File - xxxxxxx - not loaded, exists already.
The ESFSPTP utility cannot load file number xxxxxxx because it already exists.
Operator Response: Code the parameter DUP=YES to specify that the file is to be
restored by the Load function even if a duplicate file already exists.
Rms/Online Security Failure.
No user record for user named by installation security exit.
Operator Response: Contact your System Administrator for RMS/Online.
RMS/Online temp storage failure. Clear screen to continue.
RMS could not retrieve the transactions’ saved data. This is a persistent failure.
Operator Response: Contact your systems administrator. Verify the ACDS dataset
was not rebuilt.
RMS/Online has been restarted since your last entry. Reenter your
transaction ID.
RMS and CICS were restarted since the last time you entered RMS. The saved temp storage records in the ACDS do not apply now.
Operator Response: Simply re-enter your transaction ID.
RM5003
RMS/Online is no longer resident due to a NEWCOPY. Contact your
system administrator.
A NEWCOPY function was performed on RMS. This will cause a multitude of problems.
You cannot continue.
Operator Response: Your system administrator must recycle CICS.
© 2013 Mantissa Corporation. All rights reserved.
333
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
System Reference Guide
RM5004
RMS/Online initialization has not completed. Reenter your transaction.
The first entry into RMS performs several initialization steps. While this is going on, all
others are temporarily locked out. The process should only take a few second.
Operator Response: Simply re-enter your transaction. If the message repeats, it
could mean the initialization failed. Contact your system administrator if this occurs.
RM5005
RMS/Online transaction code was not found in gen table.
RM5006
RMS/Online program was not linked with an AMODE of 31.
RM5007
RMS/Online program was not defined with EXECKEY of CICS.
RM7000
RM7001
RM7002
RM7003
334
The transaction code used to initiate RMS was not defined when your administrator customized RMS.
Operator Response: Make sure the transaction codes needed to execute RMS were
specified in the RMSOGEN macro used in the “INST01” installation job.
The RMS/ONLINE program was relinked with an incorrect AMODE.
Operator Response: Relink the program RMvvrm with the following SYSLIN
statement: MODE AMODE(31),RMODE(24).
RMS/ONLINE's CICS program attribute needs to be defined with an execution key of
CICS.
Operator Response: Alter the RMvvrm program attribute changing the EXECKEY
from USER to CICS. Then INSTALL the program definition and retry the transaction.
Specify options for xxxxxxxx.
The extended spooling facility has been started and is now waiting for the initialization
option(s) to be entered by the operator. Xxxxxxxx identifies the RMS release and level.
Operator Response: RMS enters and remain in the wait state until the operator
enters the option(s). Enter initialization option(s) via the OS reply command.
Invalid option, re-specify.
One or more of the options entered were invalid.
System Action: RMS re-issues message RM7000 and waits for new option(s).
Operator Response: Respond with valid option(s) to message RM7000.
Initialization failed, correct above problems and restart RMS.
Severe initialization problems were detected, which made it impossible to start RMS. The
cause of the problems may be determined from previously issued error messages.
System Action: RMS terminates processing.
Operator Response: Correct any problems, if possible, or contact the system programming group for help.
xxxxxxxx DD statement missing.
A required DD statement with ddname xxxxxxxx was missing in the RMS procedure.
System Action: RMS terminates processing.
Operator Response: Add the required DD statement to the RMS procedure and
restart RMS.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
System Reference Guide
RM7004
Unable to open file for DDNAME xxxxxxxx.
RM7005
Parameter statement is invalid.
RM7006
Duplicate spool volume-serial: xxxxxx.
RM7007
Volume xxxxxx not mounted.
RM7008
No Spool/CHKPT Dataset found on volume xxxxxx.
RM7009
VTOC I/O-Error on volume xxxxxx.
RM7010
Logic error processing volume xxxxxx.
RM7011
Spool/CHKPT on volume xxxxxx has no extents.
© 2013 Mantissa Corporation. All rights reserved.
RMS was unable to open the file described by the DD statement with ddname xxxxxxxx.
System Action: RMS terminates processing.
Operator Response: Correct any errors in the DD statement for the file and restart
RMS.
The parameter statement displayed preceding this message is in error.
System Action: RMS will set an error flag, scan the remaining parameter statements,
and terminate processing.
Operator Response: Correct the invalid parameter statement and restart RMS.
The volume with volume serial number xxxxxx was specified more than once as a spool
volume in the initialization parameter dataset.
System Action: RMS terminates processing.
Operator Response: Correct the initialization parameter statements and restart
RMS.
The volume with volume serial number xxxxxx was requested as a spool volume, but the
volume is not mounted.
System Action: RMS terminates processing.
Operator Response: Mount the required volume, or correct the initialization parameter statements, and restart RMS.
The initialization parameters specified a spool or checkpoint dataset on volume xxxxxx,
but the dataset was not found on the volume.
System Action: RMS terminates processing.
Operator Response: Allocate a spool or checkpoint dataset on the volume and start
RMS with the format option, or correct the initialization parameters and restart RMS.
RMS issued an OBTAIN SVC to get the extended information for the spool dataset on
volume xxxxxx, but the OBTAIN SVC detected an I/O error in the VTOC.
System Action: RMS terminates processing.
Operator Response: If this is not a hardware failure, contact the system programming group for help.
RMS issued an OBTAIN SVC which returned an error code of 16.
System Action: RMS terminates processing.
Operator Response: Contact the system programming group for help.
The spool or checkpoint dataset on volume xxxxxx was allocated without any space definition and is thus not usable by RMS.
System Action: RMS terminates processing.
335
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
Operator Response: Allocate a new spool or checkpoint dataset with a valid space
definition, and “format” start RMS.
RM7012
RM7013
RM7014
RM7015
RM7016
RM7017
RM7018
336
Spool/CHKPT allocation failed for volume xxxxxx,RC=yy.
RMS was not able to dynamically allocate the spool or checkpoint dataset on volume
xxxxxx. The return code from dynamic allocation was yy.
System Action: RMS terminates processing.
Operator Response: If the cause of the error is not obvious, then contact the system
programming group for help.
Open failed for DDNAME yyyyyyyy volume xxxxxx.
RMS was unable to open the spool dataset on volume xxxxxx with the allocated dd name
yyyyyyyy.
System Action: RMS terminates processing.
Operator Response: Contact the system programming group for help.
BLKSIZE invalid for volume xxxxxx.
The BLKSIZE parameter was too low for volume xxxxxx.
System Action: RMS terminates processing.
Operator Response: Change the BLKSIZE value to allow a maximum of 8 spool
records per track, and then “format” start RMS.
Initialization parameters successfully scanned.
RMS was started with the SCAN initialization option, and after successful validation of all
the initialization parameters, it terminates with this message.
System Action: RMS terminates processing.
Operator Response: None.
Invalid SVCCODE specified, RC=?
RMS was unable to use the SVC routine specified in SVCCODE initialization parameter.
System Action: RMS terminates processing. The return code can have the following
values:
RC=1 The SVCCODE value exceeds the maximum ESR code allowed by your MVS
system.
RC=2 Invalid SVC or ESR entry specified.
RC=3 Unable to update ESR entries under MVS/XA.
RC=4 The specified SVC/ESR entry is already in use.
RC=5 Unable to load the RMSSVC module into the CSA.
RC=6 The SVCUPDTE facility is not supported under MVS370.
Operator Response: Contact the system programming group for help.
Specified external security exit is not installed.
RMS was unable to locate the security exit corresponding to the specification in the
SECUEXT initialization parameter.
System Action: RMS terminates processing.
Operator Response: Inform your system programming group.
Initialization parameter statement in error.
The parameter statement shown in this message file was in error. This message is followed
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
by error message RM7005.
System Action: RMS will set an error flag, scan the remaining parameter statements,
and terminate processing.
Operator Response: Correct the invalid parameter statement and restart RMS.
RM7019
Incomplete definition for UserID xxxxxxxx.
RM7020
ESFPARM Dynamic Allocation failed RC=xx, Error/Info
code=yyyyyyyy.
During initialization RMS detected an incomplete definition of userid xxxxxxxx.
System Action: The parameter statement validation will continue, and RMS will terminate after checking all of the parameters.
Operator Response: Correct the definition for the user and restart RMS.
RMS was unable to allocate the parameter deck file. Documentation of the return code and
the error/info code can be found in either the MVS Job Management manual or the MVS/
XA System Macros and Facilities manual.
System Action: Processing continues.
Operator Response: Inform your system programming group.
RM7021
ESFPARM dynamic Unallocation failed RC=xx, Error/Infocode=yyyyyyyy.
RMS was unable to unallocate the parameter deck file. Documentation of the return code
and the error/info code can be found in either the MVS Job Management manual or the
MVS/XA System Macros and Facilities manual.
System Action: Processing continues.
Operator Response: Inform your system programming group.
RM7022
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7023
RM7024
RM7025
© 2013 Mantissa Corporation. All rights reserved.
GETVCE failed for volume xxxxxx RC=xx.
RMS received return code xx from a GETVCE macro on volume xxxxxx. The return code
xx is explained in the VSE Advanced Functions Diagnosis Reference manual.
System Action: RMS terminates processing.
Operator Response: Contact the system programming group for help.
Continuing....CHKPT successful yy.ddd hh:mm:ss.
RMS has successfully completed a checkpoint.
System Action: Warm Start is continuing.
Operator Response: None.
Formatting xxxxxx.
A “format” start has been requested, and RMS is now formatting the spool dataset on volume xxxxxx.
System Action: Processing continues.
Operator Response: None.
I/O-Error formatting xxxxxx.
An I/O error was detected while RMS was formatting the spool dataset on volume
xxxxxx.
System Action: RMS terminates processing.
Operator Response: Correct any hardware problems, and restart RMS with the “for-
337
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
mat” option.
RM7026
RM7027
Subsystem interface not dormant.
RM7028
Unable to obtain storage for subsystem SSCT.
RM7029
Unable to obtain storage for subsystem SSVT.
RM7030
Unable to obtain storage for CMB buffer pool.
RM7031
Unable to obtain storage for the RMS address space vector table.
RM7032
338
Error during search of module xxxxxxxx, RC=y.
During initialization RMS was neither able to locate the requsted module xxxxxxx in the
link pack area nor to load the module in to the common system area. The return code can
have the following values:
RC=1 - Module found on link-library list, but not found in the LPA/MLPA.
RC=2 - Neither STEPLIB, JOBLIB nor link-library list contains the module.
RC=3 - Unable to allocate enough CSA storage to contain the module.
RC=4 - Error during module load into CSA.
RC=5 - The ESFSSSM module was not at a matching release level.
System Action: RMS terminates processing.
Operator Response: Contact the system programming group for help.
During initialization RMS found that its subsystem interface was not in the dormant state.
System Action: RMS terminates processing.
Operator Response: Another RMS task was probably executing. If not, contact the
system programming group for help, or IPL the entire MVS system.
RMS was unable to allocate the SSCT subsystem control block.
System Action: RMS terminates processing.
Operator Response: Try to start RMS again a bit later since the problem might be
due to storage contention. If this does not help, then IPL the entire MVS system.
RMS was unable to allocate the SSVT subsystem control block.
System Action: RMS terminates processing.
Operator Response: Same as for message RM7028.
RMS was unable to allocate the command message buffer pool.
System Action: RMS terminates processing.
Operator Response: Try to start RMS again a bit later. If this does not solve the
problem, then you may either decrease the NUMCMBS value in the initialization
parameters or IPL the entire MVS system.
RMS was unable to allocate the RMS address space vector table.
System Action: RMS terminates processing.
Operator Response: Try to start RMS again a bit later, or IPL the entire MVS system.
SSVT points to RMS ASVT with invalid control block identifier.
A RMS ASVT already existed in storage, but the control block identifier was not valid.
System Action: RMS terminates processing.
Operator Response: IPL the entire MVS system, or contact the system programming group for help.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM7033
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7034
File xxxxxxxx was opened for output, now pclosed.
During RMS initialization, it was found that file xxxxxx was left open for output processing.
System Action: The file is permanently closed. Processing continues.
Operator Response: None.
File xxxxxxx was opened for input, now pclosed.
During RMS initialization, it was found that file xxxxxx was left open for input processing.
System Action: The file is permanently closed. Processing continues.
Operator Response: None.
RM7035
File xxxxxx on network node yyyyyyyy interrupted.
RM7036
Identify failed for xxxxxxx subtask, RC = yy.
RM7037
Attach failed for xxxxxxx subtask, RC = yy.
RM7038
File xxxxxx Destination yyyyyyyy re-queued for transfer.
RM7039
Unexpected end-of-file on ESFPARM.
RM7040
© 2013 Mantissa Corporation. All rights reserved.
During RMS initialization, it was found that file xxxxxx was left in the process of being
printed on network node yyyyyyyy.
System Action: The file is interrupted, and print processing will continue from the
file’s last checkpoint. Processing continues.
Operator Response: None.
During initialization RMS received a non-zero return code from an IDENTIFY macro
instruction attempting to identify the module xxxxxxx. The OS system returned a completion code of yy.
System Action: RMS terminates processing.
Operator Response: Try to restart RMS, and if the error still occurs, then contact the
system programming group for help.
During initialization RMS received a non-zero return code from an ATTACH macro
instruction attempting to attach the module xxxxxxx. The OS system returned a completion code of yy.
System Action: RMS terminates processing.
Operator Response: Try to restart RMS, and if the error still occurs, contact the system programming group for help.
During initialization RMS found that file xxxxxx with destination yyyyyyyy was marked
as active on the automatic file transfer interface.
System Action: The file is re-queued for transfer.
Operator Response: None.
During initialization RMS detected an unexpected end of file condition on the parameter
dataset.
System Action: RMS is terminated.
Operator Response: Correct the parameter dataset, and restart RMS.
Incomplete definition for network node xxxxxxxx.
During initialization RMS detected an incomplete definition of network node xxxxxxxx.
339
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
System Action: The parameter statement validation will continue, and RMS will terminate after checking all of the parameters.
Operator Response: Correct the definition for the network node, and restart RMS.
RM7041
RM7042
Internal trace requested, xxxxx entries allocated.
The internal trace option (specified by the TRACE initialization parameter) has been activated and xxxxx trace table entries have been allocated.
System Action: Processing continues.
Operator Response: None.
Specified separator exit is not installed.
During initialization RMS was unable to locate the separator exit specified in the SEPAEXIT subparameter of a NODE definition.
System Action: RMS is terminated.
Operator Response: Correct the definition of the printer NODE and restart RMS.
RM7043
CID Name xxxxxxxx is already defined as a node, alias or CID Name.
RM7044
Unable to obtain storage for CIB pool.
RM7046
Unable to obtain storage for new SAST table.
RM7047
Unable to obtain storage for FSS pool.
RM7048
Company: Company-Name.
During initialization of the CID definition pool, RMS detected that the CID name
xxxxxxxx is a duplicate name.
System Action: RMS is terminated.
Operator Response: Correct the definition of the CID and restart RMS.
During initialization RMS was unable to allocate storage in CSA subpool 241 for the communication interface block pool.
System Action: RMS is terminated.
Operator Response: Reduce the number of communication channels or ports
defined and restart RMS.
RMS was unable to allocate storage for a new SAST table.
System Action: RMS terminates processing.
Operator Response: Same as for message RM7028.
RMS was unable to allocate ECSA storage for a new FSS pool.
System Action: RMS terminates processing.
Operator Response: Try to start RMS again a bit later since the problem might be
due to storage contention. If this does not help, then IPL the entire MVS system.
This message displays the decoded information contained in the password CODE and
COMPANY keywords from your startup parameters. Values for xxxxxxxxxxxxx are:
Product: (RMS|RMS)
Features: 11,222,333,444,555,666,777,MNT
Exp date: mm/dd/yy
CPU #?: ssssmmmm (ssss=serial, mmmm=model)
Company: --- company name -----------System Action: Processing continues.
340
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
Operator Response: No operator response required.
RM7049
** WARNING ** - RMS will expire on yy/ddd.
RM7050
System parameter error.
RM7051
Waiting for checkpoint-dataset lock.
RM7052
Unable to obtain CHKPT dataset lock - I/O error-, reply Y or N to continue.
RMS will not be functional after day DDD in year YY because the license has expired.
This message is issued 14 days before the specified date.
System Action: Processing continues.
Operator Response: Contact the system programming group.
The system parameter table as defined by parameter statements S1 through S7 is invalid
for one of the following reasons:
The entries in the table are not contiguous.
The table contains duplicate entries.
The table does not contain the SMF CPU id for this system.
An attempt was made to change the table on a warm start.
System Action: RMS terminates processing.
Operator Response: Analyze parameter statements S1 through S7 and correct the
problem. Start RMS again.
RMS initialization processing has determined (by examining the checkpoint dataset lock
record) that another system has control of the checkpoint dataset lock and has not relinquished that control.
System Action: RMS initialization processing cannot continue until it has exclusive
control of the checkpoint dataset lock. Initialization processing attempts to obtain the
checkpoint dataset lock once each second for the next 30 seconds. If RMS cannot
obtain the lock, message RM7052 is issued. If RMS can obtain the lock, initialization
processing continues.
Operator Response: None.
RMS initialization processing was not able to obtain control of the checkpoint dataset.
Either another system in the complex has abnormally terminated without releasing the
checkpoint dataset lock, or an I/O error occurred while RMS was attempting to obtain the
lock. Note: If you are performing a cold start and using a new checkpoint dataset or if you
are performing a configuration-wide warm start, this message can be issued as part of normal processing and does not indicate an error condition.
NOTE: IMPORTANT - Take special care to answer response correctly!
System Action: If the operator replies “Y,” RMS initialization processing continues
without the checkpoint dataset lock. If the operator replies “N,” RMS terminates.
Operator Response: If this is a cold start using a new checkpoint dataset or a configuration wide warm start (no other systems in the multi access spool complex are running), reply “Y.” If this is not a cold start using a new checkpoint dataset or a
configuration wide warm start, reply “N” and notify the system programming group.
© 2013 Mantissa Corporation. All rights reserved.
341
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
System Reference Guide
RM7053
RM7054
RM7055
Warm start denied, invalid checkpoint record.
The checkpoint record is invalid for one of the following reasons:
* Permanent I/O error.
* Operator has replied “N” to message RM7053.
System Action: RMS terminates processing.
Operator Response: Ensure that the system being started is the same as, or is compatible with, the last one run. If major incompatibilities in the RMS parameter values
are discovered, the system must be cold started.
Complex not dormant.
Analysis indicates that at least one system in the complex is not dormant.
System Action: Message RM7056 follows requesting operator response.
Operator Response: See message RM7056.
RM7056
Reply Y or N to continue COLD start.
RM7057
Reply Y or N to confirm reset on system(s) sid sid sid...
RM7058
342
Reply Y or N to confirm checkpoint record change.
The operator has made a valid request to change the fundamental checkpoint record. The
operator is asked to confirm his intent to change the record.
System Action: RMS waits for the operator to reply.
Operator Response: Reply “Y” if the checkpoint record is to be changed (this
includes the creation of a new checkpoint dataset); otherwise reply “N.”
Analysis determined that the complex is not dormant. The operator must determine if it is
safe to continue. This message is preceded by message RM7055.
System Action: RMS waits for operator reply.
Operator Response: Evaluate the complex environment and enter appropriate reply.
If “N” is entered, processing is terminated.
RMS initialization has determined, through analysis of the checkpoint record, that the
documented member(s) of the complex are not currently active. However, since a system
can remain active between a RMS failure and a RMS restart without recording checkpoint
records, the above analysis must be confirmed by the operator.
System Action: RMS waits for the operator to reply.
Operator Response: Determine whether all of the systems documented in the message text are inactive. You must reply “Y” if all documented systems are inactive.
RMS will then perform a cold start or a warm start, depending on what you specified
previously in response to message RM7000 (specify options). You must reply “N” if
one or more of the documented systems are active. RMS will then attempt to perform
a warm start, regardless of the kind of start you specified previously. An incorrect
reply might cause RMS processing to terminate abnormally.
System parameter table error.
Same as message RM7050, but the error was detected when RMS validated the checkpoint record during warm start processing.
System Action: RMS terminates processing.
Operator Response: Same as message RM7050.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM7059
Cold-Start / Warm-Start / All-System Warm-Start / System-xxxx
Warm Start is in process.
RMS is being initialized. The message text indicates (1) whether the initialization includes
all of the systems in the multi access spool complex or only the system with ID xxxx and
(2) the type of RMS initialization (cold or warm) that is taking place.
System Action: Processing continues.
Operator Response: None.
RM7060
System being restarted on xxxx.
RM7061
I/O-error accessing checkpoint dataset.
The operator is attempting to perform a warm start for RMS on this system. The attempt
fails because system xxxx has already issued an ESYS RMS command to restart RMS on
this system.
System Action: RMS initialization terminates.
Operator Response: Wait for the completion of restart on system xxxx, and then
perform a warm start for RMS on this system.
RMS failed to access the RMS checkpoint record correctly because the checkpoint dataset
space allocated is not adequate for the number of FQEs defined in the parm deck.
This message can be issued if the size of the checkpoint dataset is not large enough to
accommodate the NUMFQES specified in the parameter deck. It can also be issued if the
spool dataset is allocated over multiple extents and the checkpoint dataset is not large
enough.
System Action: RMS terminates processing.
Operator Response: Check the parms. Increase the size of the checkpoint dataset.
If it does not startup, decrease the number of NUMFQES and retry.
NOTE: IMPORTANT - If you are to format be sure to back up all files within RMS. A FORMAT or COLD
start of the subsystem will erase files. Take caution!
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7062
RM7063
© 2013 Mantissa Corporation. All rights reserved.
Spool allocation error, following volumes/extents expected.
During warm start, RMS detected that one or more spool datasets have changed position
or size. Message RM7063 displays the expected locations of the spool datasets.
System Action: See message RM7063.
Operator Response: See message RM7063. Verify the size of the checkpoint dataset
is large enough to accommodate the NUMFQE's specified, or lower the NUMFQE's
and attempt to start the subsystem again. If it still fails, allocate a larger checkpoint
dataset. If your spool dataset is allocated over multiple extents, increase the size of
the checkpoint dataset and attempt to start the subsystem again. Use the Space Allocation chart in the Installation section as a guide in determining how large your
checkpoint file should be.
VOLSER: xxxxxx EXTENT: START: ssssssss END:
The expected positions of the spool datasets are listed by message RM7063. The location
and size of the spool datasets must not be changed if RMS is to be warm started. Furthermore, all systems in a multi access spool complex must define the same spool datasets.
System Action: RMS terminates processing.
Operator Response: Correct the SPOOL parameter statements and restart RMS.
343
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
System Reference Guide
RM7064
Warm/restart open file count below zero. Reply Y or N to continue.
RM7065
BUILDQ Warm-Start denied, complex not dormant.
RM7066
344
During warm start processing, RMS detected an open file count below zero. This could
happen after a system crash.
System Action: RMS waits for the operator to reply.
Operator Response: If the operator replies “Y,” RMS resets the open file count to
zero and continues the initialization processing. This could be required for each open
file at the time of the system crash. The operator should reply ‘Y’ to each occurrence
at this message to continue a warm start.If the operator replies “N,” RMS terminates
with a disastrous error code CH06 (see message RM799).
A BUILDQ warm start could not be performed because at least one system in the complex
was not dormant.
System Action: RMS terminates processing
Operator Response: Ensure that the entire complex is dormant before starting a system with the BUILDQ option.
Load failed for xxxxxxxx module.
During initialization RMS received a non-zero return code from a LOAD macro instruction attempting to load the module xxxxxxx.
System Action: RMS terminates processing.
Operator Response: Contact the system programming group for help.
RM7067
Unable to locate $IJBSEOT - ESFEOTSK not installed.
RM7068
RMS end of task module ESFEOTSK installed.
RM7069
RMS end of task module ESFEOTSK not installed.
RM7070
Waiting for access to RMS checkpoint dataset.
During search for $IJBSEOT in VSE low core, RMS gets a zero pointer or end of table.
System Action: RMS continues processing, but RMS will not be called at end of
task in another partition address space.
Operator Response: Contact the system program group response for help.
ESFEOTSK has successfully front-ended module $IJBSEOT. Now the supervisor will call
ESFEOTSK and give control back to $IJBSEOT after RMS has checked for any open file
and channels for the task. This message only comes the first time the RMS system is
started after the system has been IPLed.
System Action: RMS continues processing.
Operator Response: None.
During initialization RMS received a non-zero return code from a LOAD macro instruction attempting to load the module ESFEOTSK.
System Action: RMS continues processing, but RMS will not be called at end of
task in another partition address space.
Operator Response: Contact the system programming group for help.
RMS has issued a read (with RESERVE) operation to the checkpoint dataset. The number
of seconds specified as the warning interval on the WARNTIM parameter has elapsed, but
the read operation has not been completed. Another system in the multi access spool complex might have terminated while holding a read (with RESERVE) operation on the check-
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
point dataset.
System Action: RMS issues this message every time the warning interval specified
on WARNTIM expires until the read operation completes.
Operator Response: Ensure that other systems in the complex are operational. If an
other system is down, it is probably holding a read (with RESERVE) on the RMS
checkpoint dataset. If the failed system cannot be restarted, the read (with RESERVE)
must be cleared by pressing SYSTEM RESET on the failed system. After pressing
SYSTEM RESET, message RM7071 might be issued.
RM7071
Waiting for release of RMS CHKPT lock by xxxx.
RM7072
System xxxx yyyyyyyyy.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7073
RMS has successfully accessed the checkpoint dataset. However, it has determined (by
examining the checkpoint dataset lock record) that system xxxx has control of the checkpoint dataset lock and has not relinquished that control.
System Action: RMS cannot continue processing until it has exclusive control of the
checkpoint dataset lock. This message is repeated approximately every 30 seconds
until the other system relinquishes control of the checkpoint dataset lock.
Operator Response: If system xxxx has failed, issue a “ESYS,RESET=xxxx” command to cause RMS to remove control of the checkpoint dataset lock from system
xxxx.
A RMS system in a multi access spool configuration has detected that the status
(yyyyyyy) of another system (xxxx) in the complex has been altered.
System Action: Processing continues.
Operator Response: None.
Spool datasets are full.
All available spool space has been allocated. This message will appear at approximately
30-second intervals until the condition is corrected.
System Action: RMS rejects all requests for direct access space until a purge function completes and the associated direct access space becomes available.
Operator Response: Determine which files are awaiting output (DF command), and
then initiate output processing for those files. If no RMS output is queued (all files
printed), then purge the files which have printed.
RM7074
Unable to obtain control over subsystem resource.
RM7075
Unable to obtain control over CHKPT/SID resource.
© 2013 Mantissa Corporation. All rights reserved.
During initialization RMS was unable to obtain control over the specified subsystem name
(see SUBID parameter).
System Action: See message RM7077, which will follow this message.
Operator Response: Check that no RMS job using the same subsystem name is
active.
During initialization RMS was unable to obtain control over the specified SID/CHKPT
names.
System Action: See message RM7077, which will follow this message.
Operator Response: Check that no RMS system using the same checkpoint dataset
and system identification is active.
345
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
RM7076
RM7077
RM7079
346
Subsystem still in operating status.
During initialization RMS found that its subsystem interface was not in the dormant state.
System Action: If the previous RMS job is no longer active, initialization continues.
Otherwise, message RM7077 is issued.
Operator Response: Check that no RMS system using the same subsystem identification is active.
Subsystem not dormant, reply “Y” to continue or “N” to terminate.
See the messages RM7074, RM7075, RM7076, of which one or more will precede this
message.
System Action: RMS waits for the operator to reply.
Operator Response: Reply “Y” if RMS is allowed to use this subsystem identification; otherwise, reply “N.”
Module xxxxxx loaded from yyyyyy yyyyyy.
During initialization RMS loaded module xxxxxxxx is loaded from either LPA LIB or J/S
LIB.
J/S LIB COPY TO CSA
LINKLIB COPY TO CSA
This message provides information concerning where the module was found and whether
the module was copied to CSA or not.
System Action: Processing continues.
Operator Response: None.
RM7080
Unauthorized RMS SVC call.
RM7089
Termination delayed, waiting for xxxxxxxx opened by jjjjjjjj.
RM7097
REFRESH option was specified at startup.
RM7098
Assignment of special properties to RMS failed.
The RMS SVC was called either from an unauthorized caller or with invalid parameters.
System Action: The RMS SVC just returns to the caller.
Operator Response: Inform your system programming group.
RMS has abnormally terminated, but the termination has been delayed because the communication channel xxxxxxxx opened by job jjjjjjjj has not been closed. The user program
has been notified via its communication end (CEND) ECB or EXIT routine.
System Action: RMS will enter wait state until the communication channel is
closed.
Operator Response: Take the action necessary to terminate the job specified.
The subsystem interface modules will be reloaded. Any additional subsystems referencing
the program areas will abend until they are brought down and up again.
Operator Response: Take the action necessary to terminate the job specified.
During initialization RMS was unable to change to the unique RMS storage protection
key. This key must be established.
System Action: RMS terminates processing.
Operator Response: Contact the system programming group for help.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7099
ESTAE Create failed, initialization terminated.
During initialization RMS was unable to create an ESTAE environment. This environment
must be established.
System Action: RMS terminates processing.
Operator Response: Contact the system programming group for help.
RM7100
Simple xxxx start completed.
RM7101
RMS waiting for work.
RM7102
RMS terminated.
RM7103
Stop command ignored.
RM7104
Missing command or command too long.
RM7105
Unable to obtain command buffer. Command discarded.
RM7106
File xxxxxx purged, owner=oooooooo dest=xxxxxxxx.
RM7107
** Resource shortage - xxxx **.
© 2013 Mantissa Corporation. All rights reserved.
RMS has successfully completed an xxxx start, where xxxx is cold or warm.
System Action: Processing continues. The subsystem is now ready for work.
Operator Response: None.
RMS detected an out of work condition. This message is displayed only in single system
configurations and indicates that no logical process is currently active in the system.
System Action: RMS enters wait state until work becomes ready.
Operator Response: None.
RMS has completed a normal termination sequence.
System Action: RMS terminates processing.
Operator Response: None.
A “P RMS” command has been issued by the operator. This is not allowed, and the command has been rejected.
System Action: Processing continues.
Operator Response: To stop RMS, use the SHUT DOWN command.
A command string which was too long or all blanks has been entered by the operator.
System Action: The command string is disregarded, and processing continues.
Operator Response: Re-enter a valid command.
RMS was unable to allocate an internal command buffer.
System Action: The command string is disregarded, and processing continues.
Operator Response: Try to re-enter the command a bit later.
File xxxxxx with owner name oooooooo and destination name dddddddd has been successfully purged.
System Action: Processing continues.
Operator Response: None.
A get buffer request has been issued, but no buffer was available. Xxxx defines the type of
buffer requested:
CMBB - Console message buffer.
LOGB - LOG file buffer.
347
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
System Reference Guide
SMFB - SMF recording buffer.
SNAB - SNA network buffer.
System Action: Processing continues.
Operator Response: None.
RM7120
Node xxxxxxxx - invalid DCE found.
RM7121
Node xxxxxxxx - already defined.
RM7122
Node xxxxxxxx - no more nodes can be defined.
RM7123
Node xxxxxxxx - invalid network group number.
RM7124
Node xxxxxxxx - undefined DEFNODE specified.
RM7125
Node xxxxxxxx - already connected to a network group.
RM7126
Node xxxxxxxx - not redefined, fined, because it was active.
RM7127
348
When trying to dynamically add node xxxxxxxx, RMS found an existing DCE with a different type.
System Action: Processing continues.
Operator Response: Contact the systems programming group.
The node xxxxxxxx could not be defined because the name already existed.
System Action: Processing continues.
Operator Response: Use unique names when defining users and nodes.
The node xxxxxxxx could not be defined because the total number of nodes added to the
parameter deck exceeded the DYNDISP/DYNPRT parameters.
System Action: Processing continues.
Operator Response: Decrease the number of nodes in the parameter deck and reissue the REINIT command, or shut down and restart RMS.
The group number on node xxxxxxxx was greater than the maximum group parameter.
System Action: Processing continues.
Operator Response: Change the MAXGROUP parameter and shut down and restart
RMS.
The DEFNODE subparameter on node xxxxxxxx specified a non-existent DEFNODE.
System Action: Processing continues.
Operator Response: Change the DEFNODE subparameter to a valid default node,
or add the missing DEFNODE.
RMS tried to connect node xxxxxxxx, which was already related to a network group.
System Action: Processing continues.
Operator Response: Contact the systems programming group.
The node xxxxxxxx could not be redefined because it was in session with RMS when the
REINIT command was issued.
System Action: Processing continues.
Operator Response: Reissue the REINIT command when the node is drained if the
node definition was changed.
Node xxxxxxxx - duplicate alias name.
The specified alias name for node XXXXXXXX was already assigned to another node.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
System Action: Processing continues.
Operator Response: If the alias name was moved from one node to another node,
reissue the REINIT command.
RM7130
Invalid password.
RM7131
Access to requested group rejected.
RM7132
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7134
A logon request has been rejected because an invalid password was specified.
System Action: The logon request is discarded.
Operator Response: Enter correct password.
A logon request has been rejected because the user specified a group which was not authorized for his use.
System Action: The logon request is discarded.
Operator Response: Enter valid group.
Access to requested terminal rejected.
A logon request has been rejected because the user used a terminal which was not authorized for his use.
System Action: The logon request is discarded.
Operator Response: Logon from a valid terminal.
Undefined userid.
A logon request has been rejected because the user specified an undefined userid.
System Action: The logon request is discarded.
Operator Response: Specify a valid userid.
RM7135
Undefined group.
RM7136
Undefined related node.
RM7140
Name xxxxxxxx - no more users can be defined.
RM7141
Name xxxxxxxx - already defined.
© 2013 Mantissa Corporation. All rights reserved.
A logon request has been rejected because the user specified an undefined group.
System Action: The logon request is discarded.
Operator Response: Specify a valid group.
A logon request has been rejected because the user specified an undefined related node.
System Action: The logon request is discarded.
Operator Response: Specify a valid node name.
The user xxxxxxxx could not be defined because the total number of users added to the
parameter deck exceeded the DYNUSER parameter.
System Action: Processing continues.
Operator Response: Decrease the number of users in the parameter deck and/or
increase the DYNUSER value in the initialization parameters. Then reissue the
REINIT command, or shut down and restart RMS.
The user xxxxxxxx could not be defined because the name already existed.
System Action: Processing continues.
Operator Response: Use unique names when defining users and nodes.
349
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
System Reference Guide
RM7200
*** RMS Resource Cleanup xxxxxxxx for tp jjjjjjjj. ssssssss.pppppppp
***.
The RMS interface cleanup module has performed resource cleanup for job jjjjjjjj, step
ssssssss, proc-step pppppppp, where tp is JS for job step cleanup or ST for subtask
cleanup. The cleanup may have been COMPLETED or FAILED (xxxxxxxx).
System Action: Processing continues.
Operator Response: None, but it may be necessary to abnormally terminate RMS,
when it is to be stopped, if the cleanup has failed.
RM7201
*** RMS Resource Cleanup failed for address space xxxx, code y ***.
RM7202
*** RMS Resource Cleanup complete for address space xxxx ***.
RM7250
The RMS interface resource cleanup module has successfully completed resource cleanup
for failing address space xxxx.
System Action: Processing continues.
Operator Response: None, but note that RMS will probably have to be terminated
using the ABEND command or the OS cancel command instead of the SHUTDOWN
command.
SVC dump scheduled for job jjjjjjjj step ssssssss.
A communication interface IRB running under a user TCB has abnormally terminated,
and an SVC dump has been scheduled for the terminating request block.
System Action: The user TCB under which the IRB was executing is abnormally terminated.
Operator Response: None.
RM7251
SVC dump scheduled for terminating application.
RM7252
Termination complete for xxxxxxxx opened by jjjjjjjj.
RM7253
350
The RMS interface cleanup processing has failed, and a simple resource cleanup for
address space xxxx (hex) has been performed. If code y is “T,” the error occurred during
execution of the end of task cleanup routine. If code y is “X,” the ESTAE routine has been
invoked during execution of the end of task cleanup routine.
System Action: Processing continues.
Operator Response: Please notify the systems programming group, and note that
RMS will probably have to be terminated using the ABEND command or the OS cancel command instead of the SHUTDOWN command.
Same as message RM7250 except that the termination routine was unable to obtain a work
area in which a complete message could be built.
System Action: Same as message RM7250.
Operator Response: Same as message RM7250.
RMS has completed termination processing for communication channel xxxxxxxx, which
was opened by job jjjjjjjj.
System Action: Processing continues.
Operator Response: None.
Termination in progress for xxxxxxxx opened by jjjjjjjj.
The RMS resource cleanup has initiated termination for communication channel
xxxxxxxx, which was opened by job jjjjjjjj.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
System Action: The communication channel is closed, and processing continues.
Operator Response: None.
RM7300
RM7301
Virtual printer interface started.
RM7302
Virtual printer xxxxxxxx started session with yyyyyyyy.
RM7303
RM7304
RM7305
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
ESTAE create failed for virtual-printer subtask.
The virtual printer subtask was unable to establish an ESTAE environment.
System Action: RMS will terminate initialization.
Operator Response: Try to restart RMS, or contact the systems programming group
for help.
The virtual printer subtask has been successfully started, and all ACBs have been opened.
System Action: Processing continues.
Operator Response: None.
The virtual printer xxxxxxxx has received a bind and an STD from application yyyyyyyy.
System Action: Processing continues.
Operator Response: None.
Virtual printer xxxxxxxx ending session with yyyyyyyy.
The virtual printer xxxxxxxx has received an unbind from application yyyyyyyy.
System Action: Processing continues.
Operator Response: None.
Virtual printer interface stopped.
The virtual printer interface has been successfully stopped.
System Action: Processing continues.
Operator Response: None.
Virtual printer interface terminated.
The virtual printer interface has been successfully terminated.
System Action: Processing continues.
Operator Response: None.
RM7306
Virtual printer xxxxxxxx stopped by operator.
RM7307
Virtual printer xxxxxxxx started by operator.
RM7308
ESFVPS TPEND request has been scheduled for virtual printer
xxxxxxxx.
The virtual printer xxxxxxxx has been successfully stopped by operator.
System Action: Processing continues.
Operator Response: None.
The virtual printer xxxxxxxx has been successfully started by operator.
System Action: Processing continues.
Operator Response: None.
The virtual printer interface has been notified by VTAM to terminate printer xxxxxxxx.
System Action: Processing continues.
Operator Response: None.
© 2013 Mantissa Corporation. All rights reserved.
351
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
RM7309
Virtual printer subtask abended.
RM7310
Self-explanatory text describing which function was current.
RM7311
For virtual printer xxxxxxxx in routine yyyyyyyyyyyyyyyy.
RM7312
ACB error flags xx.
RM7313
The virtual printer subtask has abended.
System Action: Virtual printer subtask is stopped.
Operator Response: Contact the systems programming group for help.
The virtual printer subtask has detected an error and has entered a routine to display which
function was current.
System Action: Depending on the error.
Operator Response: Contact the systems programming group for help.
Error during yyyyyyyyyyyyyyyy on virtual printer xxxxxxxx.
System Action: See message RM7310.
Operator Response: See message RM7310.
Depending on the error, the ACB error flags are shown.
System Action: See message RM7310.
Operator Response: See message RM7310.
RPL rc,f2,f3,ssei,usei
Depending on the error, the RPL flags are shown, where "rc" is VTAM return code, "f2" is
VTAM feedback code 2, "f3" is VTAM feedback code 3, "ssei" is VTAM system sense
information, "usei" is VTAM user sense information.
System Action: See message RM7310.
Operator Response: See message RM7310.
RM7314
RMS xxxxx status field yy.
RM7315
R15 xx.
RM7316
Message not found xxxx,yy,zz.
RM7317
Status printer stopped; Status printer started; VTAM SCIP exit is
active; VTAM RPL exit is active; VTAM TPEND exit is active.
Depending on the error, the RMS function and status are shown.
System Action: See message RM7310.
Operator Response: See message RM7310.
Depending on the error, register 15 is shown.
System Action: See message RM7310.
Operator Response: See message RM7310.
Error routine was entered and no error messages were found, so xxxx are routine codes, yy
is the status field, and zz is the request (all shown in hex).
System Action: None.
Operator Response: Contact the systems programming group for help.
Self explanatory text showing what status and which exit were active, if any.
System Action: See message RM7310.
Operator Response: See message RM7310.
352
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM7318
RM7319
RM7320
RM7321
RM7322
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7323
RM7324
RM7325
xxxxx open yyyyy active virtual printers.
This message is displayed in response to a display status (DS) command. Xxxxx is the
number of virtual printers, and yyyyy is the number of virtual printers which has active
sessions.
System Action: Processing continues.
Operator Response: None.
Virtual printer interface halted.
This message is displayed in response to a display status (DS) command and indicates the
virtual printer interface has been stopped.
System Action: Processing continues.
Operator Response: None.
Virtual printer interface abended.
This message is displayed in response to a display status (DS) saying virtual printer interface has abended.
System Action: Processing continues.
Operator Response: None.
Virtual printer command rejected, no virtual printer defined.
A SNET,VPS or PNET,VPS has been entered but is rejected because no virtual printer
subtask has been started.
System Action: The command is discarded, and processing continues.
Operator Response: None.
Virtual printer command rejected, interface busy.
A SNET,VPS or PNET,VPS has been entered, but is rejected because the virtual printer
interface is busy with another SNET,VPS or PNET,VPS.
System Action: The command is discarded and processing continues.
Operator Response: Enter the command a bit later.
Virtual printer command rejected, interface already active.
A SNET,VPS has been entered but is rejected because the virtual printer interface is
already started.
System Action: The command is discarded and processing continues.
Operator Response: None.
Virtual printer command rejected, interface already inactive.
A PNET,VPS has been entered but is rejected because the virtual printer interface is
already stopped.
System Action: The command is discarded, and processing continues.
Operator Response: None.
Virtual printer xxxxxxxx closed.
Virtual printer xxxxxxxx open no session.
Virtual printer xxxxxxxx open session with yyyyyyyy.
Virtual printer xxxxxxxx open session with yyyyyyyy file zzzzz.
This message is displayed in response to a display printer node which has a virtual printer
defined. Xxxxxxxx is the virtual printer name, yyyyyyyy is the application RMS is in ses-
© 2013 Mantissa Corporation. All rights reserved.
353
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
sion with, zzzzz is the file sequence number in RMS, if any file is open.
System Action: Processing continues.
Operator Response: No operator response required.
RM7326
Invalid or zero pointer in RPLUSFLD.
RM7327
No more virtual storage available, virtual printer interface will be
stopped.
The virtual printer interface has received an RPL with no user field, or it does not point to
a valid control block. The RPL is ignored because the virtual printer interface cannot
relate to any active session.
System Action: Processing continues.
Operator Response: None.
The request for storage to contain the Device Control Element control block failed. The
virtual printer will be stopped.
RM7328
Virtual printer xxxxxxxx has been removed.
RM7329
Virtual printer xxxxxxxx has been re-allocated.
RM7350
The virtual printer xxxxxxxx has been reallocated.
xxxx
RMS has received a message xxxx from an NJE session.
System Action: Processing continues.
Operator Response: None.
RM7351
xxxxxxxx is now sign-on to yyyyyyyy.
RM7352
xxxxxxxx is now sign-off from yyyyyyyy.
RM7353
Session is now started with yyyyyyyy.
RM7354
RM7355
354
The virtual printer xxxxxxxx has been reset and removed.
NJE node yyyyyyyy has received an NJE sign on record from xxxxxxxx and accepted it.
System Action: Processing continues.
Operator Response: None.
NJE node yyyyyyyy has received an NJE sign off record from xxxxxxxx and accepted it.
System Action: Processing continues.
Operator Response: None.
RMS has accepted NJE session with yyyyyyyy.
System Action: Processing continues.
Operator Response: None.
Session is now ended with yyyyyyyy.
RMS has completed NJE session with yyyyyyyy.
System Action: Processing continues.
Operator Response: None.
xxxxxxxx NJE session halted.
RMS has halted all paths to xxxxxxxx after command h,xxxxxxxx.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
System Action: Processing continues.
Operator Response: None.
RM7356
xxxxxxxx NJE session drained.
RM7357
Missing response from xxxxxxxx.
RM7358
Error in response from xxxxxxxx.
RM7359
Invalid FMH Record received from xxxxxxxx.
RM7360
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7361
RMS has drained all paths to xxxxxxxx, after receiving unbind from VTAM, or command
P,xxxxxxxx, PNET, TNET have been used.
System Action: Processing continues.
Operator Response: None.
ESFNJE has sent an RPL to xxxxxxxx with definitive response, but next inbound RPL
was not a response.
System Action: Session will be drained.
Operator Response: Contact the systems programming group.
ESFNJE has received a response from xxxxxxxx which was not ok.
System Action: Session will be drained.
Operator Response: Contact the systems programming group.
ESFNJE has received a function management header which was invalid.
System Action: Session will be drained.
Operator Response: Contact the systems programming group.
Error during GETMAIN of PCB to xxxxxxxx.
Non-zero return code during GETMAIN of process control blocks for xxxxxxxx.
System Action: Session will be drained.
Operator Response: Contact the systems programming group.
Error during GETMAIN of SNA buffer for xxxxxxxx.
Non-zero return code during getmain of SNA buffer for xxxxxxxx.
System Action: Session will be drained.
Operator Response: Contact the systems programming group.
RM7362
Compaction found in record from xxxxxxxx, not supported.
RM7363
Invalid sysout or job control record received from xxxxxxxx.
RM7364
Receiving file zzzzzz from node xxxxxxxx to destination yyyyyyyy initiated.
During decompressing, a compaction character was found which is not supported.
System Action: Session will be drained.
Operator Response: Contact the systems programming group.
ESFNJE has received a record from xxxxxxxx which contains invalid RCB.
System Action: Session will be drained.
Operator Response: Contact the systems programming group.
ESFNJE has permitted node xxxxxxxx to allocate a spool file with destination yyyyyyyy
and file number zzzzzz.
© 2013 Mantissa Corporation. All rights reserved.
355
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
System Action: Processing continues.
Operator Response: None.
RM7365
Error during RMS yyyyy RC xx for NJE node zzzzzzzz, cancel will be
sent.
ESFNJE has received return code xx during yyyyy where yyyyy is open, close, read, write
and xx are depending on yyyyy.
System Action: Cancel command will be sent to zzzzzzzz.
Operator Response: None.
RM7366
Transfer initiated for file zzzzzz destination xxxxxxxx node yyyyyyyy.
ESFNJE has sent request to destination xxxxxxxx for permission to allocate spool file
zzzzzz for node yyyyyyyy.
System Action: Processing continues.
Operator Response: None.
RM7367
Allocate denied for file zzzzzz destination xxxxxxxx node yyyyyyyy.
RM7368
File zzzzzz requested to destination xxxxxxxx node yyyyyyyy.
RM7369
RM7370
RM7371
ESFNJE has received allocation denied as answer to request for permission to allocate on
destination xxxxxxxx node yyyyyyyy.
System Action: Processing continues.
Operator Response: None.
Action after msg RM7367, file zzzzzz is requeued to destination xxxxxxxx node
yyyyyyyy.
System Action: Processing continues.
Operator Response: None.
PCB will be drained.
Action after msg RM7368, PCB, which was the receiver, will be flagged as drained.
System Action: Processing continues.
Operator Response: Contact the systems programming group.
Transfer finish for file zzzzzz destination xxxxxxxx node yyyyyyyy.
ESFNJE has successfully completed transfer file zzzzzz to RMS destination xxxxxxxx
node yyyyyyyy.
System Action: Processing continues.
Operator Response: None.
Receiving file zzzzzz from node xxxxxxxx to destination yyyyyyyy finish.
ESFNJE has successfully received file zzzzzz from node xxxxxxxx to destination
yyyyyyyy
System Action: Processing continues.
Operator Response: None.
RM7372
356
File zzzzzz requested to destination xxxxxxxx node yyyyyyyy.
Action after TNET command or VTAM error for file zzzzzz, depending on who has
responsibility for the file, msg RM7373 can be assumed.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
System Action: Processing continues.
Operator Response: None.
RM7373
File zzzzzz destination xxxxxxxx node yyyyyyyy deleted.
RM7374
NJE xxxxxxxx - invalid DCE found.
RM7375
NJE xxxxxxxx - already defined.
RM7376
NJE xxxxxxxx - no more nodes can be defined.
RM7377
NJE xxxxxxxx - undefined DEFNJE specified.
RM7378
NJE xxxxxxxx - not redefined, because it was active.
RM7379
NJE xxxxxxxx - duplicate alias name.
© 2013 Mantissa Corporation. All rights reserved.
Action after TNET command or VTAM error for file zzzzzz, depending on who has
responsibility for the file, msg RM7372 can be assumed.
System Action: Processing continues.
Operator Response: None.
When trying to dynamically add NJE xxxxxxxx, RMS found an existing DCE with a different type.
System Action: Processing continues.
Operator Response: Contact the systems programming group.
The NJE xxxxxxxx could not be defined because the name already existed.
System Action: Processing continues.
Operator Response: Use unique names when defining users and nodes.
The NJE xxxxxxxx could not be defined because the total number of NJE’s added to the
parameter deck exceeded the DYNNJE parameters.
System Action: Processing continues.
Operator Response: Decrease the number of NJE’s in the parameter deck and reissue the REINIT command, or shut down and restart RMS.
The DEFNJE subparameter on NJE xxxxxxxx specified a non-existent DEFNJE.
System Action: Processing continues.
Operator Response: Change the DEFNJE subparameter to a valid default NJE, or
add the missing DEFNJE.
The NJE xxxxxxxx could not be redefined because it was in session with RMS when the
REINIT command was issued.
System Action: Processing continues.
Operator Response: Reissue the REINIT command when the node is drained if the
node definition was changed.
The specified alias name for NJE xxxxxxxx was already assigned to another node.
System Action: Processing continues.
Operator Response: If the alias name was moved from one node to another node,
reissue the REINIT command.
357
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
RM7380
NJE nnnnnnnn alias aaaaaaaa SR=a, ST=b, JR=c, JT=d, STATUS=ssssssss.
RM7380
ee owner =oooooooo, writer =wwwwwwww, file =ffffff.
RM7380
Record=zzzzzzz, datasets=xxxxx.
Response to D,xxxxxxxx where:
xxxxxxxx is the VTAM application name.
yyyyyyyy
is the alias name.
a
is the number of SYSOUT receivers.
b
is the number of SYSOUT transmitters.
c
is the number job receivers.
d
is the number of job transmitters.
ssssssss
is current status of NJE session.
ee
is either SR,ST,JR or JT.
oooooooo
is owner of current file.
wwwwwwwwis the writer name.
zzzzzz
is the current file number.
rrrrrrr
is the number of records received or sent.
xxxxx
is the number of datasets received or sent.
System Action: Processing continues.
Operator Response: None.
358
RM7400
Session xxxxxxxx Started on network work group yyyy.
RM7401
Unable to establish session xxxxxxxx.
RM7402
Session xxxxxxxx ended on/clean up network group yyyyy.
The RMS VTAM interface has established a session with network node xxxxxxxx belonging to network group yyyyy.
System Action: Processing continues.
Operator Response: None.
The RMS VTAM interface was unable to establish a session with network node
xxxxxxxx.
System Action: The session request is discarded, and processing continues.
Operator Response: Try to re-establish the session, and if the problem still persists,
contact the systems programming group for help.
The RMS VTAM interface has successfully terminated a session with network node
xxxxxxxx in network group yyyyy.
System Action: Processing continues.
Operator Response: None.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM7403
RM7404
RM7409
RM7409
Session xxxxxxxx rejected, invalid bind parameter(s).
The RMS/VTAM interface has rejected a logon request because one or more of the bind
parameters were not acceptable.
System Action: The logon request is discarded.
Operator Response: Contact the systems programming group for help.
Session xxxxxxxx rejected, no storage available for SNA buffer.
The RMS VTAM interface has rejected a logon request because storage for a SNA buffer
could not be obtained.
System Action: The logon request is discarded.
Operator Response: Contact the systems programming group for help.
Desktop xxxxxxxx logon invalid user=yyyyyyyy.
The RMS VTAM interface has rejected a logon request because the logon reply parameters were not acceptable.
System Action: The logon request is discarded.
Operator Response: Enter correct reply.
Invalid logon reply format.
The RMS VTAM interface has rejected a logon request because the logon reply parameters were not acceptable.
System Action: The logon request is discarded.
Operator Response: Enter correct reply.
Desktop,xxxxxxxx login invalid User=uuuuuuuu.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
The RMS VTAM interface was unable to login to the desktop clients.
System Action: The report will not be sent to the PC.
Operator Response: Correct the node parameters.
RM7410
*** Timeout on session xxxxxxxx ***.
RM7411
Automatic wrap-around now on.
RM7412
© 2013 Mantissa Corporation. All rights reserved.
RMS has detected that the network display node xxxxxxxx has exceeded its timeout interval.
System Action: RMS terminates the session with the network node.
Operator Response: None.
The user pressed the PA1 key, causing the processing mode of the display device to be
altered to automatic wrap around mode.
System Action: Processing continues, but new messages will now automatically
wrap around from the bottom line to the top line.
Operator Response: None.
Automatic wrap-around now off.
The user pressed the PA1 key, causing the processing mode of the display device to be
altered so automatic message wrap around will not occur.
System Action: Processing continues, but new messages will not automatically wrap
around from the bottom line to the top line. User intervention or a one minute timeout
interval must occur before the first line on the screen will be overlaid.
Operator Response: None.
359
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
RM7420
RM7420
Desktop xxxxxxxx waiting for work, class=yyyyyyyy.
No more work was available for node xxxxxxxx servicing output classes yyyyyyyy.
System Action: Processing continues.
Operator Response: None.
RM7421
File yyyyyy on printer xxxxxxxx, zzzzzzzz lines.
RM7421
File yyyyyy on desktop xxxxxxxx, zzzzzzzz lines.
RM7422
File yyyyyy setup--xxxxxxxx--F=ffff--C=cccc (MPL=pp/d LPI).
RM7423
RM7423
360
Printer xxxxxxxx inactive, class= yyyyyyyy.
No more work was available for printer node xxxxxxxx servicing output classes
yyyyyyyy.
System Action: Processing continues.
Operator Response: None.
The printer node xxxxxxxx has selected file yyyyyy for output processing. A total of
zzzzzzz lines are to be printed, which means the number of copies multiplied by the number of output lines per copy.
System Action: Processing continues.
Operator Response: None.
The node xxxxxxxx has selected file yyyyyy for output processing. A total of zzzzzzz
lines are to be printed, which means the number of copies multiplied by the number of output lines per copy.
System Action: Processing continues.
Operator Response: None.
Printer node xxxxxxxx has selected file yyyyyy for output processing, but the operator has
to change form and/or FCB to ffff and/or cccc. RMS assumes this form to be pp lines high
and will print d lines per inch.
System Action: The printer is placed in halted state. Processing continues.
Operator Response: Enter a start command when the printer is ready. (SCS printers
only: The start command may also be given by pressing the PA1 key on the printercontrol panel.)
Printer xxxxxxxx yyyy.
The processing state of printer node xxxxxxxx has been changed. The word yyyy, specifying the action, is one of the following: REPEATED, TERMINATED, HALTED, CANCELLED, RESTARTED, INTERRUPTED, BACKSPACED, or FORWARDSPACED.
System Action: The specified action is performed. Processing continues.
Operator Response: None.
Desktop xxxxxxxx yyyy.
The processing state of node xxxxxxxx has been changed. The word yyyy, specifying the
action, is one of the following: REPEATED, TERMINATED, HALTED, CANCELLED,
RESTARTED, INTERRUPTED, BACKSPACED, or FORWARDSPACED.
System Action: The specified action is performed. Processing continues.
Operator Response: None.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM7424
RM7425
RM7426
RM7427
RM7428
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7429
RM7430
RM7431
© 2013 Mantissa Corporation. All rights reserved.
FCB image request failed.
A printer node was unable to queue an FCB image request to the image loader subtask.
System Action: The printer node is drained and the file held. Processing continues.
Operator Response: If a new start of the printer node does not work, then restart the
entire RMS system as soon as possible.
FCB Image Delete Request failed, code=xx.
RMS was unable to delete an FCB image. Return code from the DELETE SVC was xx.
System Action: The printer node is drained and the file held. Processing continues.
Operator Response: If a new start of the printer node does not work, then restart the
entire RMS system, or contact the systems programming group for help.
FCB Image Load Request failed, code=xx.
RMS was unable to load an FCB image from SYS1.IMAGELIB. The return code from the
LOAD SVC was xx.
System Action: The printer node is drained and the file held. Processing continues.
Operator Response: If a new start of the printer node does not work, then try to
restart the entire RMS system, or contact the systems programming group for help.
FCB Image xxxx not found.
A printer node has requested a load of FCB image xxxx, but the image was not found in
SYS1.IMAGELIB.
System Action: The printer node is drained and the file held. Processing continues.
Operator Response: Add the requested image to SYS1.IMAGELIB and start the
printer node.
INT REQ,xxxxxxxx,rc,f2,sysi,ussi.
An intervention required condition has been detected on network node xxxxxxxx. "rc" is
the VTAM return code, "f2" is the VTAM feedback code 2, "sysi" is the VTAM system
sense information, and "ussi" is the VTAM user sense information.
System Action: RMS waits for the printer to signal that it is ready. Processing continues.
Operator Response: Ready the printer node.
I/O Error on xxxxxxxx,rc,f2,sysi,ussi.
An uncorrectable I/O error has been detected on network node xxxxxxxx. "rc" is the
VTAM return code, "f2" is the VTAM feedback code 2, "sysi" is the VTAM system sense
information, and "ussi" is the VTAM user sense information.
System Action: The printer node is interrupted and drained. Processing continues.
Operator Response: Correct any hardware problems and start the printer node.
Forward space on xxxxxxxx reached EOF, last 10 pages follow.
A forward space command for printer node xxxxxxxx reached end of file on the spool file.
System Action: The spool file is backspaced 10 pages from end of file, and print
processing continues from that point.
Operator Response: None.
File yyyyyy printed on printer xxxxxxxx.
The printer node xxxxxxxx has finished printing file yyyyyy.
361
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
System Action: Processing continues.
Operator Response: None.
RM7431
RM7432
RM7433
RM7433
RM7434
RM7435
RM7436
362
File yyyyyy printed on desktop xxxxxxxx.
The node xxxxxxxx has finished printing file yyyyyy.
System Action: Processing continues.
Operator Response: None.
Not enough free storage to start printer xxxxxxxx, please try later.
RMS was unable to allocate virtual storage space for a spool buffer during start of printer
xxxxxxxx.
System Action: The printer node is drained. Processing continues.
Operator Response: Inform your system programming group. It may be necessary
to increase the region size for RMS.
FCB image xxxx contains invalid yyy specification.
The FCB image xxxx contains an invalid specification in the special RMS FCB extension.
The value yyy specifies the parameter in error, which may be MPP, CPI, or PPM.
System Action: The printer node is drained and the file held. Processing continues.
Operator Response: Correct the FCB in error and start the printer node.
GDDM ACB is not open.
A file could not be printed with the GDDM interface because the VTAM ACB was closed.
System Action: The printer node is drained, and the file is held. Processing continues.
Operator Response: Ensure that the ACB used by GDDM is open.
Not enough storage to start GDDM interface.
RMS was unable to allocate virtual storage for the GDDM interface.
System Action: The printer node is drained, and the file is held. Processing continues.
Operator Response: Inform your system programming group. It may be necessary
to increase the region size for RMS.
Error in GDDM interface RM7435.
RMS has received a nonzero return code from the GDDM interface. The second line contains an error message from the interface. This is another RMS message or a GDDM message.
System Action: The printer node is drained, and the file is held. Processing continues.
Operator Response: Inform your systems programming group.
Requested yyy parameters are not supported on printer xxxxxxxx.
The printer node xxxxxxxx does not support the SCS command yyy. The yyy specification
may have the value SVF or PPM.
System Action: The printer node is drained and the file held. Processing continues.
Operator Response: Correct the node parameter statements and restart RMS or
install compression support in RMSP3 (DeskTop PC).
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM7437
FTPNode xxxxxxxx busy, will retry, Class = x
RM7438
File yyyyy sent to FTP File xxxxxxxx, zzzzzzzz lines
RM7439
File yyyyy prepared for FTPNode xxxxxxxx
RM7440
Not enough free storage to start FTPNode xxxxxxxx, please try later
RM7441
RM7442
The FTPNode XXXX is busy and waiting on the FTP transfer to complete.
System Action: This message is repeated every 15 seconds.
Operator Response: No operator response required. No operator response
required.The node can be cancelled and restarted at a later time.
The FTPNode XXXXXXXX has selected file YYYYY for output processing. A total of
ZZZZZZZZ lines are to be sent to a MVS data set for FTP transfer.
System Action: Processing continues.
Operator Response: No operator response required.No operator response required.
The FTPNode XXXXXXXX has completed the file preparation and put the data in a MVS
data set.
System Action: RMS/Spool will automatically start a procedure to FTP the data set
to a TCPIP node.
Operator Response: No operator response required.No operator response required.
RMS/Spool does not have enough system memory to start this process.
System Action: The FTPNode is not started.
Operator Response: Try to restart the FTPNODE later or restart RMS/Spool with a
bigger region size.
Is your FTP Server for xxxxxxxx ready to receive?
RMS/Spool is telling the operator to make sure that the system is ready to receive reports.
System Action: Processing continues.
Operator Response: Check with the receiver (normally a PC) to make sure a FTP
server is started.
FUNC=xxxxxxxx FAILED AT:xxxxxxxx XPCC-RETC/REAS=yy/zz
PWR-RC/FDBK=aa/bb.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
Power VSE report access failure.
Operator Response: Contact your system administrator.
RM7450
Image load rejected.
RM7451
FORMDEF xx..xx not found.
© 2013 Mantissa Corporation. All rights reserved.
An IMAGE load was rejected.
System Action: Processing of this file is terminated, and the printer is drained. Processing continues.
Operator Response: Contact system programming.
The FORMDEF specified for this print file does not exist.
System Action: Processing of this file is terminated, and the printer is drained. Processing continues.
Operator Response: Change the FORMDEF to an existing one.
363
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
System Reference Guide
RM7452
PAGEDEF xx..xx not found.
RM7453
Image delete rejected.
RM7454
364
The PAGEDEF specified for this print file does not exist.
System Action: Processing of this file is terminated, and the printer is drained. Processing continues.
Operator Response: Change the PAGEDEF to an existing one.
An IMAGE delete was rejected.
System Action: Processing of this file is terminated, and the printer is drained. Processing continues.
Operator Response: Contact system programming.
HRESET not found.
The module HRESET does not exist in IMAGELIB.
System Action: Processing of this file is terminated, and the printer is drained. Processing continues.
Operator Response: The module HRESET must be created. See Initialization and
customization guide.
RM7455
Font xxxxxxxx not found.
RM7456
Font def xxxxxxxx not found.
RM7457
Module HDEVTYPS not found.
RM7458
Msg gt buff, check xxxxxxxx.
One of the fonts, specified in the CHARS parameter for this file, does not exist.
System Action: Processing of this file is terminated, and the printer is drained. Processing continues.
Operator Response: Change the FONT to an existing one.
One of the fontdef modules for a temporary softfont specified in the CHARS parameter
for this file, does not exist.
System Action: Processing of this file is terminated, and the printer is drained. Processing continues.
Operator Response: The fontdef module must be added to IMAGELIB.
The module HDEVTYPS was not found in IMAGELIB.
System Action: Processing of this file is terminated, and the printer is drained. Processing continues.
Operator Response: A HDEVTYPS module must be assembled and linked into
IMAGELIB.
A message from a module, which the RMS HP LASERJET support tried to send, was
greater than the VTAM buffer, and could not be sent. The message is probably located in
the named module.
System Action: Processing of this file is terminated, and the printer is drained. Processing continues.
Operator Response: Either increase the SNABSIZE in the RMS startup parameters,
or split the message into smaller messages and assemble and link into IMAGELIB.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
System Reference Guide
RM7470
LOGON rejected for network node xxxxxxxx.
RM7471
LOSTTERM scheduled for network node xxxxxxxx, code=yy.
RM7472
TPEND scheduled, code=xx.
RM7473
RELREQ scheduled for network node xxxxxxxx.
RM7474
Recovery scheduled for network node xxxxxxxx.
RM7475
Receive - any RPL with zero RPL user field ignored.
RM7476
NSEXIT scheduled for network node xxxxxxxx, cleanup RU =yyyyyyy
© 2013 Mantissa Corporation. All rights reserved.
A logon request from network node xxxxxxxx has been rejected because the node name is
unknown to RMS.
System Action: The logon request is discarded. Processing continues.
Operator Response: If the node should be made available for RMS, add the node
definition to the RMS initialization parameter dataset and restart RMS.
RMS has been notified by VTAM that contact with network node xxxxxxxx has been lost.
VTAM reason code is yy.
System Action: The session with the affected network node is interrupted and terminated. Processing continues.
Operator Response: Reactivate the network node, if applicable.
RMS has been notified by VTAM that the entire network is to be halted. VTAM reason
code is xx.
System Action: If reason code is 00, the VTAM interface will be stopped when all
active sessions have been terminated. If reason code is not 00, all sessions will be
interrupted, and the VTAM interface will be stopped immediately.
Operator Response: None.
RMS has been notified by VTAM that another application wants to use network node
xxxxxxxx.
System Action: The session with the network node is terminated if this has been
allowed in the RMS initialization parameter dataset. Otherwise, this condition is
ignored.
Operator Response: None.
RMS has been notified by VTAM that the network node xxxxxxxx has requested a transmission recovery sequence.
System Action: The session with the network node is interrupted and terminated.
Operator Response: None.
The RMS VTAM network interface has received an RPL with no user field. The RPL is
ignored, because RMS cannot relate it to any active session.
System Action: Processing continues.
Operator Response: Contact your systems programming group.
RMS has been notified by VTAM that contact with network node xxxxxxxx has been lost.
The contents of the request unit are yyyyyyyy.
System Action: The session with the affected network node is interrupted and terminated. Processing continues.
Operator Response: Reactivate the network node, if applicable.
365
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
System Reference Guide
RM7476
NSEXIT scheduled for node xxxxxxxx, yyyyyyyy RU=zzzzzzzz.
RM7477
Mainframe xxxxxxxx enabled for compression but DeskTop PC not
enabled.
RMS has been notified by VTAM that some network service is requested for node
xxxxxxxx. The yyyyyyy field identifies the service requested and may have the value
CLEANUP, NSPE or NOTIFY. If RMS decides to ignore the request, then yyyyyyy contains the value CLEANUP. The field zzzzzzzz contains the first 38 bytes of the request
unit received from VTAM. See the VTAM Programming manual for more information
about NSEXIT exit routines.
System Action: The session or the pending session request with the affected network
node is interrupted and terminated. Processing continues.
Operator Response: Reactivate the network node, if applicable.
The host (mainframe) defined node (xxxxxxxx) is defined in the RMS parms as a compression supported one (DESKTOPA) but RMSP3 (DESKTOP PC) does not support compression.
System Action: Processing terminates for that node.
Operator Response: Correct the device type or the logmode entry of the printer, and
start the printer node.
RM7479
I/O error on xxxxxxxx, desktop=yyyyyyyy, rc=zz
RM7480
Mainframe xxxxxxxx not enabled for compression but DeskTop PC is
enabled.
An uncorrectable I/O error has been detected on network node xxxxxxxx. The DeskTop
procedure is yyyyyyyy. RC is the DeskTop return code.
System Action: The DeskTop node is interrupted and drained. Processing continues.
Operator Response: Correct any hardware problems and start the DeskTop node.
The host (mainframe) defined node (xxxxxxxx) is not defined in the RMS parms as a
compression supported one (i.e. DESKTOPA) but RMSP3 (DESKTOP PC) does support
compression.
System Action: Processing terminates for that node.
Operator Response: Correct the node parameter statements and restart RMS or
install compression support in RMS on the host.
366
RM7481
ESF Node xxxxxxxx enabled for compression.
RM7490
Network interface started.
RM7491
Network interface stopped.
Self explanatory.
The RMS VTAM network interface has been successfully started, and logon requests can
be processed.
System Action: Processing continues.
Operator Response: None.
The RMS/VTAM network interface has been successfully stopped, and logon requests can
no longer be processed.
System Action: Processing continues.
Operator Response: None.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM7498
Unexpected inbound RPL received from xxxxxxxx.
RM7499
* VTAM error on xxxxxxxx,st,ttttttt,rc,f2,f3,ssei,usei.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7500
The RMS VTAM network interface has received an RPL with no user field. The RPL is
ignored because RMS cannot relate it to any active session.
System Action: Processing continues.
Operator Response: Contact your systems programming group.
A VTAM error has been detected on network node xxxxxxxx. The VTAM request was
st,tttttt. "rc" was the VTAM return code; "f2" was the VTAM feedback code 2; "f3" was
the VTAM feedback code 3; "ssei" was the VTAM system sense information; and "usei"
was the VTAM user sense information.
System Action: Depends on request type.
Operator Response: Depends on request type. See IBM 3270 Component Description (GA23-0044) and ACF/VTAM Macro Language Reference for additional information.
Logic error in converter function.
A SUBSYS request has been passed to a subsystem support converter function, and a
logic error was detected during modification of the internal text.
System Action: The SUBSYS request is not processed.
Operator Response: Contact your systems department.
RM7501
No storage available in subpool 230.
RM7502
Invalid output class.
RM7503
Invalid sequence number.
RM7504
Invalid forms number.
© 2013 Mantissa Corporation. All rights reserved.
The SUBSYS request could not be processed because no storage was available in subpool
230.
System Action: The SUBSYS request is rejected.
Operator Response: Contact your systems department.
The DD SUBSYS subparameter number 1 or the ESFALLOC CLASS parameter is not
valid. Valid output classes are A-Z,0-9, or national characters.
System Action: The allocation request is rejected.
Operator Response: Correct the subparameter in the SUBSYS parameter or the
ESFALLOC operand.
A sequence number was assumed to be specified in the first subparameter of the SUBSYS
request or as a subparameter of the SEQNR keyword parameter of ESFALLOC, but the
format was invalid.
System Action: The allocation request is rejected with a JCL error.
Operator Response: Correct the sequence number.
The SUBSYS subparameter number 4 or the ESFALLOC parameter FORM specifying the
forms number is invalid. The value must be expressed as alphanumeric or national characters.
System Action: The allocation request is rejected with a JCL error.
Operator Response: Correct the forms specification.
367
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
RM7505
RM7506
Invalid owner name.
The SUBSYS subparameter number 2 or the ESFALLOC OWNER parameter specifying
the owner name is invalid. Only alphanumeric or national characters are valid.
System Action: The allocation request is rejected with a JCL error.
Operator Response: Correct the owner name and rerun the job.
Missing or invalid destination name.
A SUBSYS/ESFALLOC request was passed to RMS, but no destination was specified, in
either the SUBSYS subparameter number 3 or the DEST parameter on the DD statement
(JCL allocation only), or the specified destination is invalid (JCL allocation and ESFALLOC requests).
System Action: The allocation request is rejected with a JCL error.
Operator Response: Correct the DD statement to specify a valid destination name,
either in the SUBSYS subparameter or in the DEST parameter.
RM7507
Invalid retain subparameter.
RM7508
Invalid system affinity name.
RM7509
Only 12 SUBSYS subparameters are supported.
RM7510
Allocation failed - subsystem not active.
RM7511
Allocation failed - rejected by interface exit.
RM7512
Allocation failed - unable to locate the interface exit.
RM7513
Allocation request cancelled by system operator - subsystem not
active.
The system affinity name in the SUBSYS subparameter number 5 or in the ESFALLOC
AFFINITY operand is invalid. Valid characters are alphanumeric or national characters.
System Action: The allocation request is rejected with a JCL error.
Operator Response: Correct the system affinity name and rerun the job.
The SUBSYS request specifies more than 12 subparameters.
System Action: The SUBSYS request is rejected with a JCL error.
Operator Response: Remove the extra subparameters and rerun the job.
During allocation processing of the SUBSYS request(s) RMS detected that the RMS subsystem was not active.
System Action: The SUBSYS request(s) were rejected with a JCL error.
Operator Response: Start the RMS subsystem and rerun the job.
The SUBSYS/ESFALLOC request was rejected by the interface exit.
System Action: The allocation request is rejected with a JCL error.
Operator Response: Contact the systems department for help.
During allocation processing, the allocation function was unable to locate the interface
exit in LPA/MLPA.
System Action: The SUBSYS request(s) were the rejected with a JCL error.
Operator Response: Make sure that the RMS subsystem is properly started, then
rerun the job. If problems still exist, contact your systems department.
RMS was not active at allocation time. The system operator was asked to start RMS but
368
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
cancelled this job instead.
System Action: The SUBSYS request was rejected with a JCL error.
Operator Response: Make sure the RMS subsystem is started; then rerun the job.
RM7514
User field exceeds 4 characters.
RM7515
Invalid hold subparameter.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7516
The SUBSYS subparameter specifying the user field cannot contain more than 4 characters.
System Action: The SUBSYS request is rejected with a JCL error.
Operator Response: Correct the user field and rerun the job.
The SUBSYS subparameter number 8 must be omitted or specified as HOLD.
System Action: The SUBSYS request is rejected with a JCL error.
Operator Response: Correct the subparameter field and rerun the job.
Invalid delete subparameter.
The SUBSYS subparameter number 9 must be omitted or specified as DELETE.
System Action: The SUBSYS request is rejected with a JCL error.
Operator Response: Correct the subparameter field and rerun the job.
RM7517
Invalid FCB subparameter.
RM7518
Invalid copies subparameter.
RM7519
Invalid OUTLIM subparameter.
RM7520
Allocation failed - return code ‘xx’ from RMS open/close.
© 2013 Mantissa Corporation. All rights reserved.
The SUBSYS subparameter number 10 or the ESFALLOC FCB parameter, specifying the
FCB name, is invalid.
System Action: The allocation request is rejected with a JCL error.
Operator Response: Correct the subparameter field and rerun the job.
The SUBSYS subparameter number 11 or the ESFALLOC COPIES parameter, specifying
the copy count, is invalid. The parameter must be specified as 1 to 3 numeric characters in
the range 1 to 255.
System Action: The allocation request is rejected with a JCL error.
Operator Response: Correct the subparameter field and rerun the job.
The SUBSYS subparameter number 12 or the ESFALLOC OUTLIM parameter, specifying the output limit, is invalid. The parameter must be specified as 1 to 8 numeric characters in the range 1 to 16777215.
System Action: The allocation request is rejected with a JCL error.
Operator Response: Correct the subparameter field and rerun the job.
The SUBSYS allocation request could not be processed, because the RMS file to be read
could not be properly opened or closed.
System Action: The allocation request is rejected with a JCL error. “Xx” is replaced
by the error code returned from the ESFOPEN or ESFCLOS routine.
Operator Response: Interpret the return code from the ESFOPEN/ESFCLOS routine and take appropriate action.
369
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
System Reference Guide
RM7521
Job jjjjjjjj unable to allocate file ffffffff -subsystem ssss not active,
reply wait or cancel.
Job jjjjjjjj requests allocation of file ffffffff to subsystem ssss, but subsystem ssss is not
active. When the reply is CANCEL, the job is terminated with a JCL error. When the reply
is WAIT, the subsystem checks every minute for 5 minutes for subsystem activation.
When the subsystem is activated, allocation processing continues.This is repeated 5 times
before the job is terminated with a JCL error.
System Action: The allocation function enters wait state until the operator enters the
reply.
Operator Response: Reply CANCEL if subsystem ssss cannot be started within 25
minutes, otherwise reply WAIT.
RM7522
RM7523
370
File ffffffff redirected to subsystem ssss by subsystem interface exit.
The interface exit has redirected the file ffffffff to be allocated to subsystem ssss instead of
the one requested in the SUBSYS parameter.
System Action: Processing continues.
Operator Response: None.
Error in SJF processing.
An error was detected during processing of an OUTPUT JCL reference.
System Action: The allocation request is rejected with a JCL error.
Operator Response: Specify a valid OUTPUT reference and rerun the job.
RM7524
DYNALLOC return code is xxxx-xxxx.
RM7525
DDNAME invalid.
RM7526
DDNAME in use.
RM7527
Cannot issue STAX macro.
The subsystem dataset allocation request could not be processed successfully. xxxx-xxxx
are the S99ERROR and S99INFO codes from the DYNALLOC request block. A description of these codes can be found in the OS manual SPL: JOB MANAGEMENT.
System Action: Processing is terminated.
Operator Response: Interpret the codes returned and take appropriate action.
An ESFALLOC command was issued, but the first positional operand, specifying the
ddname to be assigned to the dataset, is not valid.
System Action: The allocation request is not processed.
Operator Response: Correct the parameter and retry the request.
An ESFALLOC command was issued, but the first positional operand, specifying the
ddname to be assigned, already has an allocation associated with it.
System Action: The allocation request is not processed.
Operator Response: Free the current allocation (use the FREE FILE(ddname) command), or select another name for the file.
The ESFALLOC command processor could not issue the STAX macro to catch later attention interrupts (PA1).
System Action: The allocation request is not processed.
Operator Response: Consult your systems programming group.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM7528
Insufficient space available for parse.
RM7529
Programming error in ESFALLOC.
RM7530
RM7531
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7532
The PARSE service routines did not complete successfully because of a no storage condition.
System Action: The allocation request is not processed.
Operator Response: Increase the SIZE operand on your LOGON request or contact
your systems programming group.
The PARSE service routines returned a completion code indicating a programming error
in ESFALLOC.
System Action: The allocation request is not processed.
Operator Response: Save the issued calling sequence and contact your system programming group.
Not a subsystem dataset - xxxxxxxx.
The file named in the LIKE operand of ESFALLOC is not a RMS subsystem dataset.
System Action: The allocation request is not processed.
Operator Response: Omit the LIKE operand or specify the ddname of a RMS subsystem dataset allocated either by ESFALLOC or allocated in your LOGON procedure.
No allocation found - xxxxxxxx.
The file named in the LIKE operand of ESFALLOC is not allocated; i.e., a DD statement
is missing.
System Action: The allocation request is not processed.
Operator Response: Omit the LIKE operand, or specify the ddname of a RMS subsystem dataset allocated either by ESFALLOC or allocated in your LOGON procedure.
Subsystem does not exist - xxxx.
The subsystem name specified in the SUBSYS parameter of ESFALLOC is not an active
RMS subsystem.
System Action: The allocation request is not processed.
Operator Response: Specify an active RMS subsystem name in the SUBSYS operand or allow the value to default.
RM7533
No RMS subsystem active.
RM7534
Reference to a non-RMS subsystem - xxxx.
© 2013 Mantissa Corporation. All rights reserved.
ESFALLOC found no active RMS subsystem to process the allocation request.
System Action: The allocation request is not processed.
Operator Response: Contact the person within your organization responsible for
RMS.
The subsystem which you have named in the SUBSYS operand of ESFALLOC is not a
RMS subsystem.
System Action: The allocation request is not processed.
Operator Response: Specify the name of a RMS subsystem or allow the parameter
to default.
371
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
System Reference Guide
RM7535
Subsystem is not available - xxxx.
RM7536
Conflicting parameters.
RM7537
Invalid record format specification.
RM7538
Insufficient work area provided.
RM7539
No filename specified.
RM7540
RM7541
RM7543
372
The RMS subsystem specified in the SUBSYS operand of ESFALLOC is not started or is
terminating, or the subsystem interface has been halted.
System Action: The allocation request is not processed.
Operator Response: Select another RMS subsystem or allow the subsystem name to
default.
It was not possible to determine from the combination of specified parameters of ESFALLOC if an input dataset or an output dataset was to be allocated. This will be the case if
you, for example, specify CLASS together with SEQNR. CLASS assigns an output
attribute, and SEQNR specifies the number of an existing file.
System Action: The allocation request is not processed.
Operator Response: Specify parameters applicable to the type of dataset you
require allocated.
In ESFALLOC, an output dataset must have a record format of F, FA, FM, FB, FBA,
FBM, V, VA, VM, VB, VBA or VBM.
This message results when ESFALLOC is called and the work area provided is too small.
The caller must provide a work area of at least 1,048 bytes. The area must be allocated on
a double word boundary and the first word must contain the length of the area.
FILENAME is a required positional parameter when ESFALLOC is called. It is the functional equivalent to the DDNAME field in the JCL statement. When using ESFALLOC as
a call-routine, FILENAME may contain CL8’********’, and if so, ESFALLOC will
return the DDNAME dynamically assigned to the dataset in this area.
Permanent close failed for file ffffffff - subsystem ssss not active.
During SUBSYS unallocation of the file ffffffff, a permanent close is performed for the
file. This permanent close could not be done because subsystem ssss was not active.
System Action: Processing terminates.
Operator Response: Restart the RMS subsystem.
Permanent close failed for file ffffffff - no storage in subpool 230.
During unallocation a permanent close is to be performed for the file ffffffff. To do this,
the unallocation function needs storage for a parameter list, but this storage could not be
obtained.
System Action: Processing terminates; no permanent close is effected.
Operator Response: Contact your systems department.
Permanent close failed for file ffffffff - return code ‘cc’ from RMS.
During unallocation a permanent close is to be performed for the file using the normal
RMS close interface. For some reason RMS was unable to close the file and returned a
return code cc. See Programmer’s Guide for an explanation of the return code.
System Action: Processing terminates; the file is not permanently closed.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
Operator Response: Contact the systems department for help.
RM7545
Permanent close failed for file ffffffff - rejected by interface exit.
RM7546
Permanent close failed for file ffffffff - reopen failed RC ‘cc’ from
RMS open.
During unallocation a permanent close is to be performed, but the interface exit rejected
the close request.
System Action: Processing terminates; no close is done.
Operator Response: Contact your systems department for help.
During unallocation a permanent close is to be performed, and if the file has been temporary closed, it is necessary to reopen the file before the permanent close can be done. For
some reason RMS could not reopen the file and returned return code cc to describe the
error. See Programmer’s Guide for an explanation of the return code.
System Action: Processing terminates, the file remains temporarily closed.
Operator Response: Contact your systems department.
RM7550
Open failed for file ffffffff - subsystem ssss not active.
RM7551
Open failed for file ffffffff - no storage in subpool 230.
RM7553
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7554
© 2013 Mantissa Corporation. All rights reserved.
File ffffffff could not be opened because subsystem ssss was not active.
System Action: Processing terminates.
Operator Response: Start subsystem ssss and rerun the job.
No storage was available to build a RMS open parmlist for this SUBSYS request.
System Action: Processing terminates.
Operator Response: Contact your systems department.
Open failed for file ffffffff - return code ‘cc’ from RMS open.
RMS was unable to open the file for this subsystem request. See Programmer’s Guide for
explanation of return codes.
System Action: Processing terminates.
Operator Response: Contact your systems department.
Open error on file ffffffff - reason code=x.
An error was detected during open processing of file ffffffff. The reason code will explain
the error:
__ Code Explanation
__ 0 - File already open.
__ 1 - File allocated for output, but file opened file for input.
__ 2 - Access method not sequential.
__ 3 - Invalid record length.
__ 5 - RECFM not fixed or variable.
__ 6 - Return code from user interface exit not 0 or 4.
__ 7 - Allocated as input file, but opened as output file.
System Action: Processing terminates.
Operator Response: Correct the problem or contact your systems department for
help.
373
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
System Reference Guide
RM7555
RM7556
Open failed for file ffffffff - rejected by interface exit.
The interface exit rejected the open request for file ffffffff.
System Action: Processing terminates.
Operator Response: Contact your systems department.
Open failed for file xxxxxxxx - error in SJF processing.
A non-zero return code was received from an SJFREQ macro during the processing of an
OUTPUT JCL statement reference.
System Action: Processing terminates.
Operator Response: Check that the OUTPUT reference is valid.
RM7560
Temporary close failed for file ffffffff - subsystem ssss not active.
RM7563
Temporary close failed for file ffffffff - return code ‘cc’ from RMS
close.
During close processing of a SUBSYS file, only a temporary close is performed for the
file. This temporary close could not be done because subsystem ssss was not active.
System Action: Processing terminates.
Operator Response: Restart the RMS subsystem.
During close of a SUBSYS request, only a temporary close is performed. For some reason
RMS was unable to close the file and returned a return code cc. See Programmer’s Guide
for an explanation to the return code.
System Action: Processing terminates, the file is not temporarily closed.
Operator Response: Contact the systems department for help.
RM7565
Temporary close failed for file ffffffff - rejected by interface exit.
RM7580
Start command rejected, interface already active.
RM7581
374
The interface exit rejected the temporary close request.
System Action: Processing terminates, no temporary close is performed.
Operator Response: Contact your systems department for help.
A start SUBSYS interface command has been rejected because the interface is already
active.
System Action: Processing continues.
Operator Response: None.
SUBSYS interface started.
A start SUBSYS interface command has been successfully completed.
System Action: The SUBSYS parameter interface is started.
Operator Response: None.
RM7582
Halt command rejected, interface already halted.
RM7583
SUBSYS interface halted.
A halt SUBSYS interface command has been rejected because the interface is already
halted.
System Action: Processing continues.
Operator Response: None.
A halt SUBSYS interface command has been successfully completed.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
RMS Messages
Messages
RM Codes
System Reference Guide
System Action: The SUBSYS parameter interface is stopped.
Operator Response: None.
RM7590
Function not supported by RMS-SVC-dump scheduled-SVC dump
not scheduled.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
The subsystem support module has received a subsystem request not supported by RMS.
If an SVC DUMP was taken, register 10 points to the SSOB requesting the function not
supported. If no SVC DUMP was taken, the reason is that no storage was available for
work areas.
System Action: Processing continues and the request is rejected.
Operator Response: Contact your systems department.
RM7600
nodename FSIREQ order failed, RC=xxxx, ORDER=xxxxxxxxxxxx.
RM7601
nodename FSIREQ order failed, rc=xxxx, ORDER=xxxxxxxxxxxx.
RM7602
nodename xxxxxxxx failed, rc=xx, file=xxxxxxxx.
RM7603
nodename incorrect DSID specified in FSIREQ GETREC.
RM7604
nodename GETREC called before GETDS.
RM7605
RM7606
© 2013 Mantissa Corporation. All rights reserved.
The FSS interface has received a non-zero return code from an FSIREQ order. The return
code is documented in the PSF, Diagnosis Guide and Reference for MVS manual.
System Action: Processing continues.
Operator Response: None.
The FSS interface has received a non-zero return code from an FSIREQ order. The return
code is documented in the PSF, Diagnosis Guide and Reference for MVS manual.
System Action: Processing continues.
Operator Response: None.
A call to one of the RMS interface routines ESFOPEN, ESFWRIT, ESFCLOS, ESFNETC
or ESFNETC received a non blank status code. The return code is documented in the
chapter: “Status Codes from the Call Interface.”
System Action: Processing continues.
Operator Response: Contact the system programming group.
An FSIREQ GETREC request with a DSID that does not match the current open RMS file
was received.
System Action: The call is rejected with an indication of a logic error.
Operator Response: Contact the system programming group.
A FSIREQ GETREC request was received before any GETDS was received.
System Action: The call is rejected.
Operator Response: Contact the system programming group.
nodename non-zero response received, RETC=xx’.
A FSIREQ SEND received a non-zero response code.
System Action: Processing continues.
Operator Response: Contact the system programming group.
ESTAE create failed for ESFORDER subtask.
The ESFORDER subtask received a non-zero return code from when issuing the ESTAE
375
CHAPTER 9: MESSAGES & CODES
RMS/Online® Version 11.35
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
macro.
System Action: Processing continues without an error recovery environment.
Operator Response: Contact the system programming group.
RM7607
nodename unsupported FSIREQ invoked.
RM7608
nodename FSIREQ received in wrong address space.
RM7609
ESFORDER subtask abended.
RM7700
ESTAE create failed for file-transfer subtask.
RM7701
File-transfer subtask abended.
RM7702
RM7703
376
An unsupported FSIREQ was invoked.
System Action: Processing continues.
Operator Response: Contact the system programming group.
A call to one of the RMS FSS interfaces was issued in an address space that did not match
the current address space. This is probably due to an abnormal termination of the RMS
address space.
System Action: An S0C1 abend is provoked.
Operator Response: Contact the system programming group.
The ESFORDER subtask abended.
System Action: Processing continues, but it is no longer possible to issue orders to
the FSS.
Operator Response: Contact the system programming group.
The file transfer subtask was unable to establish an ESTAE environment.
System Action: RMS will terminate initialization.
Operator Response: Try to restart RMS, or contact the systems programming group
for help.
A disastrous error has occurred in the file transfer subtask, and the ESTAE exit routine has
received control.
System Action: The file transfer interface is marked inactive, and can only be started
if the entire RMS system is restarted. Processing continues with the interface halted.
Operator Response: Restart RMS as soon as possible. Save the dump output.
File-transfer initiated for file xxxxx destination yyyyyyyy.
The automatic file transfer service routine has allocated file xxxxx for transfer to JES2/
JES3 destination yyyyyyyy.
System Action: The ESF->JES file transfer interface will initiate transfer of the allocated spool file.
Operator Response: None.
File xxxxxx Destination yyyyyyyy successfully transferred.
The ESF->JES file transfer interface has successfully completed the transfer of file
xxxxxx to JES2/JES3 destination yyyyyyyy.
System Action: The file is marked as printed, and processing continues.
Operator Response: None.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM7704
Dynamic allocation failed, RC=xx, error/info code=yyyyyyyy.
RM7705
Open failed for SYSOUT file, interface terminated.
RM7706
RM7707
RM7708
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7709
RM7720
RM7721
© 2013 Mantissa Corporation. All rights reserved.
The ESF->JES file transfer interface was unable to allocate a spinoff SYSOUT file.
Return code was xx, and error/info code was yyyyyyyy.
System Action: The ESF->JES file transfer interface is abended and halted.
Operator Response: Inform your system programming group. The ESF->JES interface can be restarted with the “SX,ESFTOJES” command when the cause of the
dynamic allocation failure has been corrected.
The ESF->JES file transfer interface was unable to open the JES2/JES3 SYSOUT file.
System Action: The ESF->JES file transfer interface is abended and halted.
Operator Response: Inform your system programming group. The ESF->JES interface can be restarted with the “SX,ESFTOJES” command when the cause of the open
SYSOUT failure has been corrected.
File-transfer subtask waiting for work.
The file transfer service processor found that no more files were awaiting transfer.
System Action: The file transfer interface enters the wait state.
Operator Response: None.
Spool I/O error.
During ESF->JES file transfer, an incomplete spool block chain was detected. This message is only written to the JES2/JES3 sysout file.
System Action: The ESF->JES file transfer interface terminates the JES2/JES3
sysout file, and the RMS file is marked as printed.
Operator Response: None.
File xxxxxx queued for transfer to zzzz destination yyyyyyyy.
File xxxxxx has been queued for automatic file transfer to destination yyyyyyyy in the
JES2/JES3 system zzzz.
System Action: The ESF->JES file transfer interface will perform the transfer.
Operator Response: None.
Subsystem xxxx remote destination validation check RC=yy.
A subsystem remote destination validation check request to the primary subsystem xxxx
has been rejected with return code yy.
System Action: Processing continues.
Operator Response: Inform your system programming group. The subsystem
request return codes are documented in the MVS Debugging Handbook under the
description of the SSOB data area.
ESTAE create failed for SMF Writer subtask.
During initialization the SMF writer subtask was unable to establish an ESTAE recovery
environment.
System Action: Initialization is terminated.
Operator Response: Contact the systems programming group for help.
SMF writer subtask abended, SMF data lost.
The SMF writer subtask has abended. SMF data will be lost.
377
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
System Action: Processing continues without SMF recording.
Operator Response: Restart the entire RMS system as soon as possible. Save the
dump output.
RM7722
RM7723
SMF recording resumed.
RM7725
ESTAE create failed for Log Writer Subtask.
RM7726
Log Writer Subtask abended, log data lost.
RM7727
RM7728
378
SMF data lost, code xx, recording suspended.
A non-zero return code xx has been received from the SMF writer interface. SMF data
will be lost.
System Action: SMF recording is suspended until the SMF writer interface is operational again.
Operator Response: Check that normal MVS SMF recording is operational.
The SMF writer interface has switched from the not operational to the operational state.
System Action: SMF recording is resumed.
Operator Response: None.
he RMS log writer subtask was unable to establish an ESTAE recovery environment.
System Action: Initialization is terminated.
Operator Response: Contact the systems programming group for help.
The log writer subtask has abended.
System Action: Logging is terminated.
Operator Response: Restart RMS as soon as possible if logging is required. Save
the dump output.
Log file allocation failed, code = xx.
The log writer subtask was unable to allocate a spin off SYSOUT file.
System Action: Logging is terminated.
Operator Response: Restart RMS as soon as possible if logging is required.
Open failed for log file data set.
The log writer subtask was unable to open the allocated spinoff SYSOUT file.
System Action: Logging is terminated.
Operator Response: Restart RMS as soon as possible if logging is required.
RM7729
Log file closed.
RM7740
Unable to establish ESTAE environment for image loader subtask.
RM7741
Required volume to locate SYS1.IMAGELIB not mounted.
The image loader subtask was unable to establish an ESTAE recovery environment.
System Action: Initialization is terminated.
Operator Response: Contact the systems programming group for help.
Either the volume containing SYS1.IMAGELIB is not mounted, or a required catalog volume was not mounted.
System Action: Initialization is terminated.
Operator Response: Mount the required volume and restart RMS.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
Chapter 9: Messages and Codes
RMS Messages
Messages
RM Codes
System Reference Guide
RM7742
SYS1.IMAGELIB not cataloged or not found on volume.
RM7743
Read error on catalog or VTOC while attempting to locate
SYS1.IMAGELIB
Either SYS1.IMAGELIB does not exist on the volume to which the catalog points, or it is
not cataloged.
System Action: Initialization is terminated.
Operator Response: Contact the systems programming group for help.
An error occurred in reading the catalog or VTOC.
System Action: Initialization is terminated.
Operator Response: Contact the systems programming group for help.
RM7744
Image Loader Subtask abended, all pending requests cancelled.
RM7760
JES->ESF interface - halt error, RC=yy, SSOBRETN=xx.
RM7761
JES->ESF interface - subsystem - request error, RC=yy, SSOBRETN=xx.
The image loader subtask has abended.
System Action: All pending image requests are cancelled, and no new requests will
be accepted.
Operator Response: Restart RMS as soon as possible. Save the dump.
During halt of the JES->ESF interface, a subsystem request error occurred. The return
codes xx and yy are documented in the MVS Debugging Handbook under the SSOB and
SSSO data areas, respectively.
System Action: The ESF->JES interface is halted.
Operator Response: Inform your system programming group.
A subsystem request error occurred in the JES->ESF interface. The return codes xx and yy
are documented in the MVS Debugging Handbook under the SSOB and SSSO data areas,
respectively.
System Action: The ESF->JES interface is abended and halted.
Operator Response: Inform your systems programming group.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7762
JES->ESF interface error, please hold job 9999 and reply ‘C’ to continue or ‘T’ to terminate.
An error occurred in the JES->ESF interface during allocate, open, read, or unallocate of a
JES2/JES3 SYSOUT file belonging to job 9999.
System Action: The ESF->JES interface enters wait state until the operator enters a
reply to the outstanding WTOR message.
Operator Response: Place job 9999 in hold status, and reply “C” to let the JES>ESF interface continue, or reply “T” to halt the JES->ESF interface.
RM7763
JES->ESF interface- dynamic allocation failed, RC=xx, error/info
code=yyyyyyyy.
The JES->ESF interface was unable to allocate the JES2/JES3 SYSOUT file. An explanation of the return code and the error/info code can be found in either the MVS Job Management manual or the MVS/XA System Macros and Facilities manual.
System Action: The ESF->JES interface issues the WTOR message RM7762.
Operator Response: Inform your systems programming group.
© 2013 Mantissa Corporation. All rights reserved.
379
CHAPTER 9: MESSAGES & CODES
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
System Reference Guide
RM7764
JES->ESF interface - could not open the DSNAME=xxxxxxxxxx.
RM7765
JES->ESF interface - RMS file yyyyyy failed, RC=xx, job 9999 jobnamex, file 99999.
The JES->ESF interface was unable to open the JES2/JES3 SYSOUT file xxxxxxxxxx.
System Action: The ESF->JES interface issues the WTOR message RM7762.
Operator Response: Inform your systems programming group.
The JES->ESF interface detected a RMS error during transfer of a JES2/JES3 SYSOUT
file belonging to job 9999/jobnamex. The failed RMS request yyyyyy may be “OPEN,”
“WRITE,” “CLOSE,” or “ROUTE.” An explanation of the failed request status code xx
can be found in the section “Call Status Codes”.
System Action: The ESF->JES interface is abended and halted, except if it is
“OPEN” with RC=22.
Operator Response: Inform your systems programming group.
RM7766
Job 9999 jobnamex transferred from jesx to rmsx destination
xxxxxxxx file 999999.
One or more JES2/JES3 SYSOUT files from job 9999/jobnamex was successfully transferred from the primary subsystem jesx to RMS rmsx, where it has been saved in file
999999 with the destination xxxxxxxx.
System Action: The resulting RMS file is now ready to be printed.
Operator Response: None.
RM7767
JES->ESF interface - I/O error- *error message*.
RM7768
I/O error on jesx spool, rest of sysout dataset ignored.
RM7769
RM7780
380
The JES->ESF interface detected an I/O error during read of a JES2/JES3 SYSOUT file.
The ****error message**** information is the error description provided by the MVS
SYNADAF routine. An EOF was not present in the JES/SPOOL file. The data is valid up
to this error, however, it may be incomplete.
System Action: The resulting RMS file is now ready to be printed.
Operator Response: None.
The JES->ESF interface detected an I/O error during read of a SYSOUT file from the primary subsystem JESx.
System Action: The ESF->JES interface issues the WTOR message RM7762.
Operator Response: Inform your systems programming group.
JES->I/O error on jesx spool. I/O terminated before EOF.
The JES->ESF interface detected an I/O error during read of a JES2/JES3 SYSOUT file.
An EOF was not present in the JES/SPOOL file. The data is valid up to this error, however, it may be incomplete.
System Action: The resulting RMS file is now ready to be printed.
Operator Response: None.
JES->ESF interface- error in identify- R15=xx.
The JES->ESF interface has gotten a non-zero return code from XPCC during an identify
call to VSE/SP.
System Action: The ESF->JES interface is halted.
Operator Response: Inform your systems programming group.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM7781
RM7782
JES->ESF interface- error in connect- R15=xx.
The JES->ESF interface has got a non-zero return code from XPCC during connect call to
VSE/SP
System Action: The ESF->JES interface is halted.
Operator Response: Inform your systems programming group.
JES->ESF interface- waiting to connect to VSE/POWER XPCC interface.
The JES->ESF interface has tried to connect to VSE/POWER but connection has not been
established after 2 minutes.
System Action: The ESF->JES interface is halted.
Operator Response: Inform your systems programming group.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7783
JES->ESF interface- error in terminate R15=xx.
The JES->ESF interface has gotten a non-zero return code from xpcc during terminal call
to VSE/SP.
System Action: The ESF->JES interface is halted.
Operator Response: Inform your systems programming group.
RM7784
JES->ESF interface- RC=xx FB=xx RTN=xx.
RM7785
JES->ESF interface- error in sender.
RM7786
RM7787
© 2013 Mantissa Corporation. All rights reserved.
The JES->ESF interface has gotten a non-zero return code from POWER, where RC is
return code, FB is feedback code, and RTN is an ESFXFER routine number between 01 08.
01 -> get job output from the spool
02 -> get job output from the spool
03 -> delete the job list from LST q
04 -> quit get spool after RMS
05 -> hold job in LST queue after CM
06 -> lookup XMT queue when TNODE=su
07 -> move job output from XTM to LS
08 -> quit get spool after EOF
System Action: The ESF->JES interface is halted
Operator Response: Inform your systems programming group.
The JES->ESF interface has gotten a non-zero return code from POWER during send,
replay call. This message comes between RM7787 and RM7784.
System Action: The ESF->JES interface is halted.
Operator Response: Inform your systems programming group.
JES->ESF interface- VSE/POWER has been terminated.
The JES->ESF interface has detected that VSE/POWER was terminated abnormally.
System Action: The ESF->JES interface is halted.
Operator Response: Inform your systems programming group.
JES->ESF interface- VSE RC=xx.
This message displays the return code from VSE/SP XPCC interface and will be followed
by more messages.
381
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
RM7788
RM7789
JES->ESF interface- VSE/POWER termination in progress.
The JES->ESF interface has detected that VSE/POWER has termination in progress.
System Action: The ESF->JES interface is halted.
Operator Response: Inform your systems programming group.
RM7790
JES->ESF interface- error in SENDR (wait).
RM7791
JES->ESF interface- VSE REAS=xx.
RM7792
382
JES->ESF interface- error in disconnect R15=xx.
The JES->ESF interface has gotten a non-zero return code from XPCC during disconnect
call to VSE/SP.
System Action: The ESF->JES interface is halted.
Operator Response: Inform your systems programming group.
The JES->ESF interface has gotten a non zero return code from POWER during send,
replay call, this message comes between RM7791 and RM7784.
System Action: The ESF->JES interface is halted.
Operator Response: Inform your systems programming group.
This message displays the reason code from the VSE/SP XPCC interface and will be followed by more messages.
JOB 99999 jobnamex has been held.
This message comes after RM7765 to inform the operator that the job is kept held in the
POWER LST queue.
System Action: The ESF->JES interface is halted.
Operator Response: Inform your systems programming group.
RM7800
OK
RM7801
Shutdown command accepted.
RM7802
Network command rejected, no network defined.
RM7803
Network command rejected, interface busy.
This is a confirmation message which indicates that a command has been successfully
queued for execution.
System Action: Processing continues.
Operator Response: None.
A SHUTDOWN command has been successfully processed, and the system termination
sequence is in progress.
System Action: Processing continues until the network interface and all opened files
have been closed, at which time RMS terminates.
Operator Response: None.
A start net, stop net, or reset net command has been entered but is rejected because no network nodes have been defined to RMS.
System Action: The command is discarded, and processing continues.
Operator Response: None.
A start net, stop net, or reset net command has been rejected because the network interface
is busy processing another start, stop, or reset command.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
System Action: The command is discarded, and processing continues.
Operator Response: Enter the command again a bit later.
RM7804
Start command rejected, interface already active.
RM7805
Stop command rejected, interface already inactive.
RM7806
Network halt already in process.
RM7807
Reset command rejected, interface already inactive.
RM7808
Checkpoint request completed.
RM7810
Undefined file destination.
RM7811
Invalid node name.
RM7812
RM7813
© 2013 Mantissa Corporation. All rights reserved.
A start net command has been rejected because the network interface is already started.
System Action: The command is discarded, and processing continues.
Operator Response: None.
A stop net command has been rejected because the network interface is already stopped.
System Action: The command is discarded, and processing continues.
Operator Response: None.
A stop net command has been rejected because the network interface already is in the process of being stopped.
System Action: The command is discarded, and processing continues.
Operator Response: None.
A reset net command has been rejected because the network interface is already stopped.
System Action: The command is discarded, and processing continues.
Operator Response: None.
An explicit checkpoint request (CHKPT command) has been successfully completed.
System Action: Processing continues.
Operator Response: None.
A command has been entered which specified a file destination which was neither defined
in RMS or JES2/JES3.
System Action: The command is discarded, and processing continues.
Operator Response: Re-enter the command with a valid node name.
A network command has been entered which specifies an invalid node name.
System Action: The command is discarded, and processing continues.
Operator Response: Re-enter the command with a valid node name.
Invalid file sequence number.
A file control command has been entered which contains an invalid file sequence number
or an invalid file sequence range.
System Action: Processing continues.
Operator Response: Re-enter the command with a valid file sequence number or
file sequence range.
File not found.
A file control command has been entered which specifies a nonexisting file.
383
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
System Action: Processing continues.
Operator Response: Re-enter the command with a valid file sequence number.
RM7814
RM7815
File permanently closed.
RM7816
xxxxx outstanding I/O requests.
RM7817
Open file count: aaaaa/bbbbb OUTPUT, ccccc/ddddd input.
RM7818
xxx % Spool utilization.
RM7819
*** System in shutdown sequence ***.
RM7820
384
File not temporarily closed.
A close file command has been entered which specifies a file which was not in the temporarily closed state.
System Action: Processing continues.
Operator Response: Re-enter the command with a valid file sequence number.
A close file command has been successfully completed, and the requested file is now permanently closed.
System Action: Processing continues.
Operator Response: None.
This message is displayed in response to a display status (DS) command. Xxxxx specifies
the current number of incomplete DASD I/O requests in the system.
System Action: Processing continues.
Operator Response: None.
This message is displayed in response to a display status (DS) command. Aaaaa specifies
the total number of files currently opened for output processing; bbbbb specifies the current number of files opened for output processing by this system; ccccc specifies the total
number of files currently opened for input processing, and ddddd specifies the current
number of files opened for input processing by this system.
System Action: Processing continues.
Operator Response: None.
This message is displayed in response to a display status (DS) command or as an information message from the RMS checkpoint processor when the spool utilization has passed
the value specified by the TGWARN initialization parameter. Xxx specifies the current
percentage of spool space in use.
System Action: Processing continues.
Operator Response: None.
This message is displayed in response to a display status request if the system is in the process of being terminated.
System Action: Processing continues.
Operator Response: None.
xxxxxx File queue elements in use - total yyyyyy.
This message is displayed in response to a display status (DS) command. Xxxxxx specifies the number of files currently in the system, and yyyyyy specifies the maximum number of concurrent files allowed.
System Action: Processing continues.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
Operator Response: None.
RM7821
xxxxx active network sessions.
RM7822
VTAM ACB closed.
RM7823
VTAM ACB open- logons enabled.
RM7824
VTAM ACB open- xxxx halt in process.
RM7825
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7826
This message is displayed in response to a display status (DS) command. Xxxxx specifies
the current number of active network sessions.
System Action: Processing continues.
Operator Response: None.
This message is displayed in response to a display status (DS) command when the network interface is stopped.
System Action: Processing continues.
Operator Response: None.
This message is displayed in response to a display status (DS) command when the network interface is started, and logon requests can be processed.
System Action: Processing continues.
Operator Response: None.
This message is displayed in response to a display status (DS) command when the network interface is in the process of being stopped. No logon requests can be processed.
Xxxx is SLOW if a stop net command or a VTAM “Z NET” command has been entered.
Xxxx is FAST if a reset net or a VTAM “Z NET,QUICK” command has been entered or if
the VTAM system is abending.
System Action: Processing continues.
Operator Response: None.
MSG from xxxxxxxx: - - - text - - -.
A message has been received from the network session xxxxxxxx.
System Action: Processing continues.
Operator Response: None.
WRITELOG rejected, logging not active.
A WRITELOG command has been rejected because the log writer task is not active.
System Action: Processing continues.
Operator Response: If logging is required, then restart the RMS system with the
LOG option.
RM7827
WRITELOG rejected, service request pending.
RM7828
FILE xxxxxx OWNER=oooooooo DEST=dddddddd sssss.
© 2013 Mantissa Corporation. All rights reserved.
A WRITELOG command has been rejected because the log writer task is busy processing
another logging request.
System Action: The command is discarded, and processing continues.
Operator Response: Try to enter the command a bit later.
This message is displayed in response to a display active (DA) command. File xxxxxx
(with owner name oooooooo and destination name dddddddd) was found to be active in a
385
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
RMS system. Sssss specifies the processing status of the file and is one of the following:
“IN PURGE” if the file is awaiting purge processing, “ON nnnnnnnn” where RMS
nnnnnnnn is printer node name if the file is active on a network printer in this system’s
network domain, “ON NETWORK” if the file is active on a network printer in another
RMS system’s network domain, “IN TRANSFER” if the file is being transferred to the
JES2/JES3 system, “OPEN INPUT” if the file is opened for input processing, ‘OPEN
OUTPUT’ if the file is opened for output processing, or “????????” if the file has an undefined status (this usually means that there is an error in the system).
System Action: Processing continues.
Operator Response: None.
RM7829
RM7830
RM7831
No active files.
This message is displayed in response to a display active (DA) command if no files were
active in the system.
System Action: Processing continues.
Operator Response: None.
DISPLAY(tttttttt) xxxxxxxx ssssssss G=ggggg AUTH=a RELREQ=r.
This message is displayed in response to a display node command. Tttttttt is the device
type of the display node; xxxxxxxx is the node name; ssssssss is the status of the network
session (“DRAINED”, “DRAINING”, or “ACTIVE”); ggggg is the number of the network group in which this node belongs; a is the authorization level of the node (0 =
restricted user, 1 =ordinary user, 2 = master user); and r specifies whether or not a release
request should be accepted for this node (N if no, D if delayed, or I if immediate).
System Action: Processing continues.
Operator Response: None.
Printer(tttttttt) xxxxxxxx ssssssss G=ggggg.
F=ffff C=cccc Q=qqqqqqqq A=a P=p S=s R=r T=rrrrrrrr I=iiii.
Lines: total: vvvvvvv, printed: wwwwwww
These messages are displayed in response to a display printer node command. Tttttttt is the
device type; xxxxxxxx is the node name; ssssssss is the device status (“DRAINED,”
“ACTIVE (FILE xxxxxx),” “INT REQ,” “DRAINING,” “HALTING,” “INACTIVE,”
“QUEUED,” “HALTED,” or “HALTED (SETUP)”); ggggg is the number of the network
group to which the printer node belongs; ffff is the current form number mounted in the
printer; cccc is the current FCB being simulated, qqqqqqqq is the output class currently
being processed by the printer. A is Y if automatic file selection mode is on or N if automatic file selection mode is off. P is Y if the printer operates in automatic purge mode or N
if not. S is the number of separator pages being produced between files (0, 1, or 2). R is Y
if the printer operates in restricted file selection mode or N if not. rRrrrrrr is the name of
the translate table in use on this printer if any. Iiii is the sense code received from the last
SIMLOGON request, if any. Vvvvvvv is the number of output lines multiplied by the
number of copies for the current file. Wwwwwww is the total number of output lines
printed of the current file.
System Action: Processing continues.
Operator Response: None.
386
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM7832
File-transfer subtask is xxxxxxxx.
RM7833
Halt command rejected, subtask has abended.
RM7834
Halt command rejected, interface already halted.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7835
The status of the file transfer subtask and the two interfaces ESF->JES and JES->ESF are
defined by xxxxxxxx and are one of the following: ACTIVE, ABENDED, HALTED, or
DRAINING.
System Action: Processing continues.
Operator Response: None.
A halt file transfer interface command has been rejected because the file transfer subtask
has abended.
System Action: Processing continues.
Operator Response: If the file transfer interface is required, then restart RMS. Save
the dump output.
A halt file transfer interface command has been rejected because the interface is already
halted.
System Action: Processing continues.
Operator Response: None.
File-transfer interface halted.
A halt file transfer subtask command has been successfully completed.
System Action: Both the ESF->JES interface and the JES->ESF interface are halted
if not already halted.
Operator Response: None.
RM7835
xxxxxxxx interface halted.
RM7836
Start command rejected, subtask has been abended.
RM7837
Start command rejected, interface already active.
RM7838
xxxxxxxx interface started.
© 2013 Mantissa Corporation. All rights reserved.
A halt file interface xxxxxxxx command has been successfully completed. The xxxxxxxx
can be either ESF->JES or JES-> ESF.
System Action: Processing continues.
Operator Response: None.
A start file transfer interface command has been rejected because the file transfer subtask
has abended.
System Action: Processing continues.
Operator Response: If the file transfer interface is required, then restart RMS. Save
the dump output.
A start file transfer interface command has been rejected because the interface is already
active.
System Action: Processing continues.
Operator Response: None.
A start file transfer interface xxxxxxxx command has been successfully completed. The
xxxxxxxx can be either ESF->JES or JES-> ESF.
System Action: Processing continues.
387
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
Operator Response: None.
RM7839
SEQNO filename dest Q form FCB lines CPY PR SID STAT.
xxxxxx oooooooo dddddddd q ffff cccc lllllll cop pr sid ssss.
End-of-display.
This message is displayed in response to a display file command. Xxxxxx is file sequence
number, oooooooo is file owner name; dddddddd is file destination name; q is output
class; ffff is form number; cccc is FCB name; lllllll is the number of output lines; cop is
the number of copies; pr is the files output priority; sid is the system ID of the system on
which the file is active or to which it has affinity; and ssss is the files status. The file status
is one or more of the following characters: E - end of file has been detected; i.e., the file
has been printed.
O - the file is currently opened for output processing.
I - the file is currently opened for input processing.
T - the file is temporarily closed.
B - the file is opened for backwards input processing.
P - the file is queued for purge processing.
H - the file is held.
A - the file is active on a network node.
W - the file is waiting for file transfer.
X - the file is on the file transfer interface.
System Action: Processing continues.
Operator Response: None.
RM7840
Queue empty.
RM7841
xxxxxx file(s) scheduled for purge.
RM7842
GDDM ACB xxxxxx.
RM7846
388
This message is displayed in response to a display file command if no files were found.
System Action: Processing continues.
Operator Response: None.
A purge file command has been successfully completed. Xxxxxx specifies the number of
files scheduled for purge processing.
System Action: Processing continues.
Operator Response: None.
This message is displayed in response to a display status (DS) command. The status of the
ACB used by the GDDM interface is xxxxxx.
System Action: Processing continues.
Operator Response: None.
Reset rejected, file is being purged.
A reset file command has been rejected because the affected file was queued for purge
processing.
System Action: Processing continues.
Operator Response: None.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM7847
RM7848
RM7849
RM7850
RM7850
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7852
RM7855
RM7858
© 2013 Mantissa Corporation. All rights reserved.
Reset rejected, file not permanently closed.
A reset file command has been rejected because the affected file is in the temporarily
closed state.
System Action: Processing continues.
Operator Response: Issue a close file (CF) command followed by the reset command if desired.
Reset rejected, file-transfer in process.
A reset file command has been rejected because the affected file is being transferred to the
JES system.
System Action: Processing continues.
Operator Response: None.
Reset rejected, file active on network.
A reset file command has been rejected because the affected file is being processed by a
network print processor.
System Action: Processing continues.
Operator Response: None.
xxxxxx file(s) routed.
A route file command has been successfully completed. Xxxxxx specifies the number of
files routed.
System Action: Processing continues.
Operator Response: None.
xxxxxx file(s) rerouted.
A requeue file command has been successfully completed. Xxxxxx specifies the number
of files requeued.
System Action: Processing continues.
Operator Response: None.
xxxxxx file(s) released.
A release file command has been successfully completed. Xxxxxx specifies the number of
files released.
System Action: Processing continues.
Operator Response: None.
xxxxxx file(s) held.
A hold file command has been successfully completed and xxxxx specifies the number of
files held.
System Action: Processing continues.
Operator Response: None.
Printer xxxxxxxx not available.
A start printer command for printer xxxxxxxx has been rejected because the network node
is inactive.
System Action: Processing continues.
Operator Response: Activate the printer node via a VTAM “V NET, ACT” command, and enter the start printer command again.
389
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
RM7859
RM7860
A start printer command for printer xxxxxxxx has been rejected because the network
interface is in the process of being terminated.
System Action: Processing continues.
Operator Response: None.
Printer xxxxxxxx already waiting for connection.
A start printer command for printer xxxxxxxx has been rejected because a previous start
command has been queued to VTAM. Another application is using the requested printer,
and VTAM will not initiate start printer processing before the application has released the
printer node.
System Action: Processing continues.
Operator Response: None.
RM7861
Start command rejected, network interface not started.
RM7862
Start xxxxx failed, system operator notified.
RM7863
User(s) not logged on or not receiving.
RM7864
RM7865
RM7866
390
Start xxxxxxxx rejected, network in shutdown.
A start printer command has been rejected because the network interface is stopped.
System Action: Processing continues.
Operator Response: Start the network interface and re-enter the start printer command.
A start printer command request for printer xxxxxxxx has been rejected by VTAM. The
system operator has been notified because the error requires system operator intervention.
System Action: Processing continues.
Operator Response: Contact the systems department for help if necessary.
A message command was entered, but no user received the message.
System Action: Processing continues.
Operator Response: None.
CID xxxxxxxx</G> ssssssss < BY jjjjjjjj >.
This message is displayed in response to a display channel command. Xxxxxxxx is the
name of the communication identifier; /G is present if the CID is defined by a generic
name; ssssssss is the status of the communication channel, and “BY jjjjjjjj” is present if
the channel is opened or in stopping state. Jjjjjjjj will be the name of the JOB or STC
which opened the channel.
System Action: Processing continues.
Operator Response: None.
xxxxx active communication channels.
This message is displayed in response to a display status (DS) command. Xxxxx specifies
the current number of active communication channels.
System Action: Processing continues.
Operator Response: None.
Printer xxxxxxxx busy on GDDM interface.
A start printer command against xxxxxxxx has been rejected because a file is currently
being printed by the GDDM interface. As soon as the file is printed, the printer will be
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
started.
System Action: Processing continues.
Operator Response: None.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7871
xxxx sssssss.
This message is displayed in response to a list system (LSYS) command. Xxxx is the system ID; and sssssss is the current status of the system. Sssssss will be one of the following:
NOT STARTED if the system has never been started.
INACTIVE if the system is currently inactive.
DORMANT if the active system has been “sleeping” for a longer
period than the value of the SYNCTOL initialization parameter.
ACTIVE if the system is currently active.
RESTARTING ON zzzz - if the system is currently being restarted on
system zzzz.
System Action: Processing continues.
Operator Response: None.
RM7872
ESYS already in process.
RM7873
xxxx sssssss.
RM7881
Reinit successfully completed.
RM7882
© 2013 Mantissa Corporation. All rights reserved.
The ESYS (reset system) command is rejected because a previous ESYS command is not
completed.
System Action: Processing continues.
Operator Response: Wait for the previous ESYS command to complete and then
reenter the ESYS command.
An ESYS (reset system) command has been rejected because the affected system is active.
The system may be considered active for three reasons:
1) (ssssssss = “IS ACTIVE AND CANNOT BE RE-STARTED”) The system is
running and is fully operational.
2)(ssssssss = same as 1) The SYNCTOL time interval has not elaspsed since the
system failed.
3)(ssssssss = “RESTARTING ON zzzz”) The system is currently being restarted on system zzzz.
System Action: Processing continues.
Operator Response: None.
A Reinit (reinitialize) command has been successfully completed. All changes to the
parameter deck are updated in RMS.
System Action: Processing continues.
Operator Response: None.
REINIT successful, but some nodes could not be redefined.
A REINIT (reinitialize) command has been successfully completed. Some of the changes
to the parameter deck could not be updated in RMS because the nodes were in session
with RMS.
System Action: Processing continues.
Operator Response: Reissue the REINIT command when the nodes are not in session with RMS.
391
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
System Reference Guide
RM7883
REINIT completed, but some errors occurred during processing.
RM7884
REINIT failed.
RM7891
File busy on another system.
RM7892
A REINIT (reinitialize) command failed because syntax errors were found in the parameter deck.
Operator Response: Contact the systems department.
A file control command has been rejected because the affected file is active on another
system in the multi access spool configuration.
System Action: Processing continues.
Operator Response: None.
Printer in use.
A reset printer command has been rejected because a file is active on the printer.
System Action: Processing continues.
Operator Response: Interrupt the printer and re-enter the reset command if necessary.
RM7893
Printer not active.
RM7894
Operand too long.
RM7895
392
A REINIT (reinitialize) command has been completed. One or more of the changed node
definitions were not successfully updated. This message is preceded by messages which
inform about the node name and the cause of the error.
System Action: Processing continues.
Operator Response: Contact the systems department.
A printer control command has been rejected because the specified printer node is not
connected to the system.
System Action: Processing continues.
Operator Response: Start the printer (using the start command) and re-enter the
command if necessary.
An operand on a command was too long.
System Action: The command string is discarded, and processing continues.
Operator Response: Re-enter the correct command.
Invalid operand(s).
A command was entered with one or more invalid operands.
System Action: The command is discarded, and processing continues.
Operator Response: Re-enter the command with valid operands.
RM7896
Missing operand(s).
RM7897
Invalid command.
A command has been entered, but one or more required operands were missing.
System Action: The command is discarded. Processing continues.
Operator Response: Enter the correct command.
A command has been entered which RMS does not recognize as a valid RMS command.
System Action: The command is discarded. Processing continues.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
Operator Response: Enter the correct command.
RM7898
RM7899
Command string too long, command discarded.
A command string was too long to be contained in an internal command buffer.
System Action: The command string entered is discarded. Processing continues.
Operator Response: Enter the commands in smaller pieces.
Unable to obtain command buffer, command discarded.
The command processor was unable to allocate an internal command buffer to contain the
specified command string.
System Action: The command string is discarded, and processing continues.
Operator Response: Enter the command string a bit later.
RM7950
Dormancy interval change from xxxxxx to yyyyyy.
RM7981
** No MAS support **.
Self explanitory.
The installation is not allowed to use the Multi Access Spool feature.
System Action: Processing is terminated.
Operator Response: Contact the systems department.
RM7982 ** No PSF support **.
The installation is not allowed to use the PSF interface.
System Action: Processing is terminated.
Operator Response: Contact the systems department.
RM7983
** No HP-Laserjet support **.
RM7984
** No enhanced compression support **.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM7985
The installation is not allowed to use the HP LaserJet printer support.
System Action: Processing is terminated.
Operator Response: Contact the systems department.
The installation is not allowed to use compression support.
Processing is terminated.
Contact the systems department.
** No FTP Desktop support **.
The installation is not allowed to use FTP desktop support.
System Action: Processing is terminated.
Operator Response: Contact the systems department.
RM7986
** No desktop support **.
RM7987
** Desktop only device supported **.
© 2013 Mantissa Corporation. All rights reserved.
The installation is not allowed to use desktop support.
System Action: Processing is terminated.
Operator Response: Contact the systems department.
For a DeskTop Lite system, only DeskTop nodes are valid.
393
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
System Reference Guide
RM7988
** No IP print support **.
RM7992
** unrelated security code **.
RM7993
** invalid security code **.
RM7994
** RMS has expired **.
RM7995
RM7996
394
IP printing support is not available for use.
The security code specified in the CODE parameter does not match the name given in the
COMPANY parameter. System action Processing is terminated. Operator response Contact the systems department.
The security code is invalid.
System Action: Processing is terminated.
Operator Response: Contact the systems department.
RMS has detected that the license has expired.
System Action: Processing is terminated.
Operator Response: Contact the systems department.
CHKPT=I/O-error-.
The RMS system has been started on an unauthorized CPU.
System Action: Processing continues.
Operator Response: Contact the systems department.
I/O error- *** error message ***.
RMS has detected a permanent I/O error on one of its spool datasets. *** error message
*** is the error description provided by the MVS SYNAD routines.
System Action: RMS is terminated with an error reason code.
Operator Response: Save the dump output, and restart RMS.
RM7997
Checkpoint was in process, checkpoint data may be invalid.
RM7998
Catastrophic error, ESTAE in control.
RMS has abended, but the termination routines detected that a checkpoint was in process,
and the information in the checkpoint dataset may therefore be invalid.
System Action: Termination continues.
Operator Response: If RMS rejects a restart, notify the systems department.
A system abend has occurred in RMS.
System Action: RMS has entered its recovery routines, and will initiate a termination of the system, and produce a dump.
Operator Response: Restart RMS if possible, or notify the systems department.
Report the failure and save the dump output.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM7999
BIND rejected for xxxxxxxx, xxxxxxxx was not defined or type was
invalid.
VTAM error in module ESFPRTD - R15=xx, RO=xx, FBK2=XX.
APPX error - RC = XX.
File xxxxx aborted on desktop xxxxxxxx.
Disastrous error, error code = xxxx.
RMS has discovered an uncorrectable error in the system. The following error codes may
occur:
ABND
ALL0
ASM0
BFR0
BFR1
BFR2
CCW0
CCW1
CKP0
CH00
CH01
CH02
CH03
CH04
CH05
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CH06
CH07
GETM
INT1
INT2
INT3
IO01
© 2013 Mantissa Corporation. All rights reserved.
An ABEND command has been entered.
The track allocation routine has detected an invalid track allocation map control block.
No message sequence number could be assigned to a command buffer.
A getbuf request failed. Invalid buffer type specified.
A freebug request failed. Invalid buffer type specified.
A freebuff request failed. Buffer already on free buffer queue.
A request to build a channel program has been rejected
because the extent in the MTTR address is invalid.
A request to build a channel program has been rejected
because the request was not valid.
A checkpoint request is being processed, but the requester did
not have exclusive access to the file queue.
Unexpected I/O interrupt (ESFNUC). The checkpoint dataset
lock is held by an unknown system (ESFCKPT).
Permanent I/O error on checkpoint dataset.
Unable to find checkpoint processor PCB to be dispatched.
The checkpoint processor PCB was not on the wait queue.
The checkpoint processor PCB was not on the I/O wait queue.
A checkpoint I/O request has been rejected because the checkpoint dataset SCB is in the BUSY state; i.e., a previous checkpoint has not been completed.
The warm start routine in the checkpoint processor has
detected an open file count below zero.
Unable to start because the file queue could not be rebuilt.
Getmain error.
Duplicate node or alias name found during initialization of
table index.
Allocated FBA checkpoint dataset too small for the current
setup.
Internal error, invalid #ICEREQ call.
An attempt to start a channel program has been rejected
because the extent value was not valid.
395
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
IO02
IO03
IO04
IO05
IO06
NET1
NET2
NET3
NET4
PR01
PRG0
SEC0
XEQ0
XEQ1
XEQ2
XFQ1
XFQ2
XFR1
Unexpected I/O interrupt.
Unable to determine the cause of the I/O interrupt.
Permanent I/O error on a spool dataset.
Unable to find PCB to be dispatched.
PCB to be dispatched for the I/O interrupt was not waiting for
I/O to complete.
The active session count field dropped below zero.
A disastrous error has occurred in the network interface.
The outstanding receive request count field dropped below
zero.
The getbuffer routine returned a buffer already on receive any
queue.
An internal error has occurred in a printer node’s command
request handler.
A track allocation map control block has been detected in
error by the purge processor.
Security routine passed Invalid Return reason code.
A track allocation map control block has been detected
invalid.
The open file count has been reduced to a negative value.
A user track allocation map control block has been detected
invalid during an output (write) operation.
Internal error in the file index look up routine #XFQELKUP.
Internal error in the file index update routine #XFQEUPDT.
An invalid FQE address has been passed to the file transfer
completion routine.
System Action: RMS will terminate with a user abend 0001 and a dump.
Operator Response: Restart RMS if possible and notify the systems department.
Report the failure and save the dump output.
396
RM9000
Multiple messages pending. Press PF1 for complete list.
RM9001
User ID not recognized. Please re-enter.
RM9002
Your password has expired. Enter new password.
More than one diagnostic/informational message has been issued by the system.
Operator Response: Press PF1 for a complete list of messages.
The USER ID entered on the Access Authorization panel or with the System Transaction
code is not a defined user.
Operator Response: Enter correct User Identification.
The current password has been used for the number of days specified as the maximum use
days within system installation parameter.
Operator Response: Enter a new password in the NEW PASSWORD/VERIFY
PASSWORD fields.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM9003
RM9004
New and verify passwords must match.
RM9005
Option not recognized. Select another.
RM9006
RM9007
RM9008
RM9009
RM9010
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
Incorrect password. Please re-enter.
The password entered does not match the password on file.
Operator Response: Enter correct password.
In response to Message 002, the user has entered a new password that does not match the
VERIFY PASSWORD field content.
Operator Response: Re-enter both fields.
The option entered by the user does not match any of the listed options.
Operator Response: Select from the listed options.
Retry threshold exceeded. Contact your Group Administrator.
The maximum logon retry count has been exceeded. That is, you have tried to sign on with
incorrect password information the maximum number of times permitted by the system.
Operator Response: Self explanatory.
Duplicate help resource. Verify and re-enter.
An attempt has been made to add a Help record that already exists.
Operator Response: Enter information under the correct identifier or change the
existing Help record.
Resource ID not in file.
An attempt to read a system or user Help record has resulted in a “RECORD NOT
FOUND” condition.
Operator Response: This may be a system error or a user error. Contact your system
administrator.
Maximum length exceeded for indicated field.
The data entered in the indicated field is not within acceptable limits. The acceptable limits are indicated.
Operator Response: Re-enter data within the acceptable range.
Value is non-numeric or outside allowable range.
A value has been entered which is outside the required limit or is non-numeric.
Operator Response: Re-enter the command with a numeric value within the appropriate limits.
RM9011
Unrecognized option. Please re-enter.
RM9012
To ID not in file, add or insert first.
© 2013 Mantissa Corporation. All rights reserved.
The option entered is not recognized by the menu processor or application program.
Operator Response: Enter option from the menu list or from the known available
options for the program in question.
The Help identifier specified as the target in a copy operation does not exist.
Operator Response: Specify the correct “TO” identifier in the copy operation.
397
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
System Reference Guide
RM9013
From ID not in file, copy terminated.
RM9014
Copy complete.
RM9015
Deletion of Drain Trace Dataset failed for xxxxxxxx.
RM9016
Output request exceeds the maximum number of Profile
References.
RM9017
Page descriptor with invalid length encountered during recovery processing. (RM77701 (HDRORQUE))
The Help identifier specified as the source in a copy operation does not exist.
Operator Response: Specify the correct “FROM” identifier for the copy operations.
The Help Management Copy Request has been successfully completed.
Operator Response: N/A.
This message indicates that there is possible corruption within the input data. RMS is
unable to distinguish whether the record encountered was the start of a dataset record or a
garbage record. This message is displayed when the sort record is not recognized as a format that is Release 8.8 or 11.02 and not 11.30 thru 11.34. The system can not tell if the
record is a start of dataset record or garbage record. Anything that is below a certain
length should be a queue record.
Operator Response: User should attempt to cross reference the input if it is from
tape input to determine if the RM80001 can read any data from the tape. Make sure
the data was created by RMS programs RM80001 or RM80004. If softcopy media
must be retrieved, be sure to include the media category in the Select statement. This
also holds true for any media type other than hardcopy.
RM9018
Record(s) truncated during output for DEST(dddddddd)
Report (rrrrrrrr).
Self explanatory.
RM9019
Change/add information. Press ENTER to update.
System Administration has requested that the fields for the current record be maintained.
Operator Response: Change the fields that need to be maintained and press Enter to
effect these changes.
Transport Server is moving Class(cccccccc) Dest(dddddddd) to ssss.
PGROUP=gggg. selectionClass,selectionDest,rmsssn,pgroup.
Self explanatory.
398
RM9020
Enter Record Identifier.
RM9021
Depress ENTER to confirm deletion.
System Administration is in CHANGE mode and is requesting the identifier of the record
you wish to change.
Operator Response: Enter the identifier of the record to be changed and press Enter.
System Administration is in DELETE mode and has presented the content of the record
for which deletion was requested.
Operator Response: Verify that the displayed record is the correct one and press
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
Enter to complete deletion.
RM9022
This record does not exist. Please enter new record identifier.
System Administration is in CHANGE or DELETE mode. The previously entered record
identifier cannot be located on the file.
Operator Response: Enter the correct identifier.
RM9023 This record already exists. Enter new record identifier.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
While in ADD mode, System Administration has attempted to write a record with a key
that already exists.
Operator Response: Change the record identifier field or maintain the existing
record.
RM9024
Write error encountered while updating this record.
RM9025
Error encountered while trying to delete this record.
RM9026
Deletion complete. Enter identifier for next deletion.
RM9027
Changes recorded. Enter identifier for next change.
RM9028
Addition successful. Enter identifier for next record.
RM9029
The specified template record does not exist.
RM9030
Access group not defined.
© 2013 Mantissa Corporation. All rights reserved.
In CHANGE mode, System Administration has encountered a file error while trying to
update the record being maintained.
Operator Response: This is a file error or an internal system error. Contact your system group and/or Mantissa Product Support.
System Administration is in DELETE mode. While attempting to delete the current
record, a write error occurred.
Operator Response: Check to see that the record was not deleted during the maintenance operation.
System Administration is in DELETE mode and has successfully completed the deletion
of the current record.
Operator Response: Enter next record identifier for deletion or press END.
System Administration is in CHANGE mode. The last changes entered have been successfully recorded.
Operator Response: Enter record identifier for next change or press END.
System Administration is in ADD mode. The specific template record cannot be located.
Operator Response: Enter the correct template identifier or proceed with data entry.
Press ENTER to complete ADD operation.
There is not a template record for the ID number you entered in the template field.
Operator Response: Verify the ID of the template record and re-enter the transaction.
The access group specified does not exist.
Operator Response: Specify the correct access group.
399
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
RM9031
RM9032
RM9033
RM9034
RM9035
RM9036
RM9037
RM9038
400
Access group/location report combination does not exist.
The report information for the access group LOCATION/REPORT cannot be located in
the file.
Operator Response: Ensure that the correct access group LOCATION/REPORT
information was entered.
Screen read error, invalid SBA string received.
When adding Help records or performing PTM maintenance, you may not use erase EOF
or the delete character keys.
Operator Response: Avoid use of erase EOF. If you use the delete character key,
insert a corresponding number of characters.
The access group entered does not exist.
Self explanatory.
Operator Response: Enter the correct access group.
Report access failure. Press PF1 for details.
For reasons indicated when the PF1 key is pressed, the report access failed.
Operator Response: Press PF1 for full details.
The maximum number of reports have been selected for re-print.
Display processing has detected an attempt by the user to reprint selected pages from more
than 8 reports in the current display session.
Operator Response: EXIT display (PF3) and print the 8 reports already selected.
Then display and request print for the remaining reports.
Access failed due to missing panel prototype.
A panel prototype record is a formatted definition record maintained by Help Management. It is used to define the layout of the panel.
Operator Response: This could be a read error. Contact Mantissa Product Support if
the error persists.
Access denied due to report security attributes.
You have attempted access to a secured report.
Operator Response: Contact your system administrator if you feel you need access
to this report.
Command not recognized or non-numeric value entered.
The command data last entered cannot be recognized in the case of a command, or is not
numeric in the case of line/positioning value.
Operator Response: Re-enter the command.
RM9039
Label has been assigned.
RM9040
Switch note ignored. No other label(s) exists.
The label last entered on the VIEWER command line has been accepted and stored.
Operator Response: N/A
The switch note key was pressed, and there are no other active notes for the report being
displayed.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
Operator Response: N/A
RM9041
The following field is required for the current operation.
RM9042
Access failed. Check access group, location, report, media
values.
Panel management has determined that a required field has not been entered. The identifier for the field in question follows this message. Enter the required field.
The requested report cannot be located.
Operator Response: Ensure that the values specified for the access/group location/
report and media values are correct.
RM9043
Scroll value invalid. Previous value retained.
RM9044
Display depth invalid. Previous value retained.
RM9045
Heading depth invalid. Previous value retained.
RM9046
Search criteria invalid. Valid options are as is and caps.
RM9047
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM9048
The scroll value entered was not H(ALF) F(ULL) P(AGE) or NNNN.
Operator Response: Re-enter a valid scroll value.
During an INDEX display or a VERSION display, an ID number entered as the first operand of a command (i.e., D N for Display Report N) is not valid.
Operator Response: Re-enter command.
Self explanatory.
ID number/selection invalid, please retry.
During a report version or report index display, a selection number has been entered that is
not on the left side of the panel.
Operator Response: Enter Correct ID number.
The requested report cannot be located.
The report requested cannot be located.
Operator Response: Re-enter selection value.
RM9049
Scroll value must be FULL, HALF, PAGE or NNNN.
RM9050
Windowed display row offset non-numeric or greater than 1/2 screen
rows.
RM9051
Windowed display column offset non-numeric or greater than 3/4
screen width.
RM9052
There is no window set by this name. Valid sets are H1, H2, H3, V2,
And Q4.
Self explanatory.
The name specified in the Window Set (WS) command is not a valid window set.
Operator Response: Specify one of the window sets indicated in the message.
© 2013 Mantissa Corporation. All rights reserved.
401
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
RM9053
RM9054
An attempt has been made to open a specific window or the next available window and all
windows are currently open.
Operator Response: Select a window set with more windows, or close and reopen
one of the current windows.
Specified window not currently active.
A window identifier has been entered in the command field that is not active.
Operator Response: Before the switch window PF key is pressed, enter the ID of an
active window.
RM9055
Specified window cannot be located.
RM9056
Specified window already open.
RM9057
Print end (PE) acknowledged.
RM9058
The specified report is not available in the current window.
RM9059
Multiplication or division error.
RM9060
Location master does not exist for indicated location.
RM9061
402
Non-matching window ID or all windows open.
A window ID has been entered on the command line and the switch window PF key
pressed. The designated window is not currently active.
Operator Response: Specify an active window.
An OPEN WINDOW command specifying a window ID that is already open has been
entered. If you need additional windows open, enter OW with no window ID. The open
report menu will be displayed in this window.
The previously entered PRINT END (PE) command has been accepted.
Operator Response: N/A.
A report ID has been entered on the command line and the switch report PF key was
pressed.
Operator Response: Specify an active report.
Attempting to divide by zero or an overflow on multiplication.
The requested location does not have a corresponding Location Master record.
Operator Response: The Location Master record may be added by the system
administrator.
Print queue write failed, possible file error.
A file error condition has been returned while attempting to write a print queue record.
Operator Response: Ensure that the file is open.
RM9062
Print request processed.
RM9063
Print end (PE) ignored. No corresponding print start (PS).
A print job stream has been submitted to the internal reader for batch execution.
Operator Response: No response necessary.
A Print Start must be requested prior to a Print End request.
Operator Response: Enter a Print Start on the appropriate page and then the Print
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
End.
RM9064
Print start/print end commands require that the scroll value be page.
RM9065
Print start request ignored. Table is full. Return to display menu to
print the selected pages, or use request print (RP) command to reset
the table.
Use of Print Start (PS) and Print End (PE) commands is only valid for SCROLL ==>
PAGE.
Operator Response: Set the scroll field to Page and continue the selection process.
The print request is not actually activated until display is exited.
Operator Response: If immediate printing is desired, return to the display menu.
RM9066
RM9067
Unable to determine DSN for print queue file.
RM9068
Location version record does not exist for report.
RM9069
Security violation. Contact System Administrator.
RM9070
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
Print start acknowledged. Continue selection.
The first page has been selected for print.
Operator Response: Continue selection process by specifying the Print End command on the appropriate page.
The file name for the print queue record is not allocated to System Administration, or the
record type is not included in the file table.
Operator Response: Check to ensure that all online files are open to CICS. If not,
open and try the transaction again. If all files are open, call Mantissa Product Support.
Internal system error.
Operator Response: Contact Mantissa Product Support.
You have attempted to access a resource for which you do not have security clearance.
Operator Response: Contact your system administrator.
Invalid PF key definition, definition ignored.
A PF key definition entered was either non-numeric, less than 1, greater than 12, or duplicately defined.
Operator Response: Check the fields and correct where appropriate.
RM9071
Type=profile user not valid for LOGON user ID.
RM9073
Start/end column is not numeric.
RM9074
© 2013 Mantissa Corporation. All rights reserved.
Profile user records are used only for security definition and may not be used by active
System Administration users.
Operator Response: Sign on using another User ID.
The start column in the Column Select command is not numeric.
Operator Response: Correct and re-enter the Column Select command.
Column start/end range error. Must be 1-240.
The ending column specified in a COLUMN SELECT pair (i.e., CS SS,EE) is greater than
240.
403
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
Operator Response: Re-enter the Column Select with an ending column in the
range of 1-240.
RM9075
RM9076
The ending column specified in a Column Select pair (i.e., CS SS,EE) is not numeric.
Operator Response: Enter correct value.
Report version record does not exist for report.
Internal system error.
Operator Response: Contact your system administrator.
RM9077
Media not specified or invalid.
RM9078
Run tracking record does not exist for report.
RM9079
File error writing run tracking record.
RM9080
File error rewriting run tracking record.
RM9081
File error writing the location/report record.
RM9082
File error writing the report/version record.
RM9083
File error creating the QXRCDS file.
RM9084
File error writing to target subsystem repository.
RM9085
404
Start/end column is not numeric.
Media is required and was not entered, or the one entered was not a valid media.
Operator Response: Enter a valid media name.
The report control dataset contains a record for which there is no run tracking record.
Operator Response: None. These records are automatically purged from the file.
A failed attempt has been made to add a run tracking record to the report control dataset.
Operator Response: This may be a space allocation problem or an internal system
problem. Contact Mantissa Product Support if the proper space is allocated.
A file error condition has been returned while attempting to write a record to RCDS
VASAM.
Operator Response: Ensure the integrity of the VSAM RCDS file.
A file error condition has been returned while attempting to write a record to RCDS
VSAM.
Operator Response: Ensure the integrity of the VSAM RCDS file.
A file error condition has been returned while attempting to write a record to the RCDS
VSAM file.
Operator Response: Ensure the integrity of the RCDS file.
An error was returned from File Control.
Operator Response: Ensure the integrity of the VSAM RCDS file and retry.
An error was returned from File Control.
Operator Response: Ensure the integrity of the repository file and retry.
Restore control statement missing or invalid.
The restore control statement was omitted or is invalid.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
Operator Response: Refer to documentation for correct formats.
RM9086
Partial restore in progress.
RM9087
Full restore in progress.
RM9088
Error reading the report version record.
RM9089
Print queue record does not exist.
RM9090
Page printing may not be complete.
RM9091
Search range value is not numeric.
RM9092
No keyword prerequisites.
RM9093
No keyword value specified.
RM9094
Invalid keyword specified.
RM9095
RM9096
© 2013 Mantissa Corporation. All rights reserved.
A partial restore of the files in process.
Operator Response: N/A.
A full restore of the files is in process.
Operator Response: N/A.
An error was returned from File Control.
Operator Response: Ensure that the RCDS VSAM file is open to CICS.
While attempting to print a report, the print queue page set records was not found on file.
Operator Response: Re-release the document for print.
All of the selected print may not actually be printed due to premature end of document
condition.
Operator Response: Check output to ensure all have been printed.
The value entered for the search range was not numeric.
Operator Response: Re-enter Search Range with numeric value.
A keyword error from the release Print Job Stream.
Operator Response: Check the released Job Stream in System Administration for
errors.
A keyword error from the released Print Job Stream.
Operator Response: Check the released Job Stream in System Administration for
errors.
A keyword error from the released Print Job Stream.
Operator Response: Check the released Job Stream in System Administration for
errors.
User record not found.
The user record cannot be found on file.
Operator Response: See the system administrator.
Print request job control prototype not found.
The Print Job Stream prototype defined in the user control record could not be located.
The “Selective Print/Dataset print” job stream specified on the User Master record has not
405
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
been added to the Help Management system.
Operator Response: Ensure that there is a prototype by the name specified.
RM9097
Tracking shadow record not found.
RM9098
Associated data component not found.
RM9099
RM9100
RM9101
RM9102
RM9103
Up to window depth-2 header lines may be held.
During a display operation, you have requested more than 4 header lines be held.
Operator Response: N/A
The report version number must be numeric.
A non-numeric report version number has been entered on either a report menu sub panel
or on the Report Display Menu.
Operator Response: Re-key the report version number.
--- Top of data reached ---
The beginning of the report has been encountered during a FIND previous operation.
Operator Response: Press REPEAT FIND to continue.
--- Bottom of data reached ---
The end of the report has been reached while processing a FIND command.
Operator Response: Press REPEAT FIND to continue search.
--- Find data not located ---
The character string designated in the previous FIND command cannot be located.
Operator Response: Ensure correct string was entered.
RM9104
No find data entered.
RM9105
Panel larger than screen size, edit not allowed.
RM9106
Cancel command accepted.
RM9107
406
Internal error. The shadow record written at the beginning of the run could not be located
for deletion.
Operator Response: Correct and resubmit the initialization job.
A FIND command was entered with no find character string.
Operator Response: Re-enter command.
Your terminal attributes are smaller than those of the terminal that last edited this panel.
“COPY” may be used to reduce the size, or a larger terminal may be used.
The report cancel (C) command has been processed. The transaction is queued for processing.
Operator Response: N/A.
Location/report record does not exist for report.
There is no Location/Report record in the RCDS.
Operator Response: Check to ensure valid entry.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM9108
No previous find command entered.
RM9109
Valid Find command options are: FIRST, NEXT, LAST and PREVIOUS.
The FIND PF key has been depressed and no find command has been entered.
Operator Response: Enter a FIND command.
The format of the FIND command is F xxxx option where xxxx is the string to be found
and option is FIRST, LAST, NEXT, PREV.
Operator Response: Re-enter the command.
RM9110
RM9111
RM9112
RM9113
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM9114
Selected line item is null, please retry.
A command has been entered that specified a line number that was not valid.
Operator Response: Re-enter with a valid line number.
End column must be greater than or equal to start column.
A column select command was entered which contained a select pair with the start column
greater than the end column.
Operator Response: Re-enter the CS command.
Default column selection (1-240) is active.
Information only.
Operator Response: N/A.
Current column selection remains active.
The currently active column select command remains in effect because the CS command
entered was not valid
Operator Response: Correct the CS command in the command field.
Error reading the location/report record.
An undetermined error was encountered while attempting to read for the Location/Report
record.
Operator Response: Check to ensure that the correct files were restored during daily
backup/restore processing.
RM9115
Error reading for end of report queue.
RM9116
Append mode; appending supplicate record keys.
RM9117
Error reading for bottom of list.
© 2013 Mantissa Corporation. All rights reserved.
Attempting to read the block containing the last page of data for a report. Either the record
was not found or a file error was encountered. This message can be issued when FQE
number in the report data record does not match the FQE number in the report queue.
Operator Response: Retry the operation.
A Report/Location Name combination is being appended to the same Report/Location
Name combination output by the same run of RM80004.
Operator Response: Check the run stream and assure that this is the desired result.
Could not find last record for the bottom of list.
System Action: Internal error.
407
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
RM9118
Invalid numeric scroll value entered.
RM9119
Scroll amount too large for direction requested.
RM9120
RM9121
RM9122
408
The scroll value entered must be numeric and the scroll UP/DOWN key depressed.
The data to be displayed did not contain enough records to scroll the desired amount.
Operator Response: Select a smaller scroll value.
Invalid security type. Internal error.
The security type passed to the security processor was invalid. Security denied.
Operator Response: Contact Mantissa Product Support.
Invalid transaction code. Re-enter.
The transaction code you have attempted to secure is not valid.
Operator Response: Consult RMS/RS documentation for a list of valid transaction
codes.
No list data available for display.
No records available to list for this selection. End of file or file error.
Operator Response: N/A.
RM9123
Template invalid except during add.
RM9124
No distribution option record exists for this instruction set.
RM9125
Invalid new password. Please re-enter.
RM9126
Report format successfully added.
RM9127
Report format successfully deleted.
RM9128
Report format does not exist.
Use of the template field is only valid during an add transaction.
Operator Response: Clear the template field and then re-enter the transaction.
The distribution option record must always be the first record entered into an instruction
set. This record establishes the instruction set and allows for addition of all other record
types.
Operator Response: Enter the distribution option record by using the ADO option
and giving the instruction set a name in the DIST. SET NAME field.
Self explanatory.
Operator Response: Correct password and re-enter.
Self explanatory.
Operator Response: No action required.
Self explanatory.
Operator Response: No action required.
The report format you have selected does not exist.
Operator Response: Please enter the correct format name. The FORMAT SAVE
transaction may be used to save a currently selected format. This must be done before
the format can be retrieved.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM9129
RM9130
RM9131
RM9132
RM9133
RM9134
RM9135
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM9136
Error deleting report format.
The VSAM deletion of the report format record failed.
Operator Response: Probably already deleted.
Error adding report format.
The VSAM write of the report format record failed.
Operator Response: Possibly already exists.
Format successfully retrieved.
Self explanatory.
Operator Response: No action is required.
Premature end-of-file on QXRCDS, terminating.
End of file on first read for the QXRCDS file.
Operator Response: Determine what is wrong with the file. Check for empty file.
Menu item not supported for list processing.
Menu item selected is not a list type transaction.
Operator Response: Re-specify.
Enter information for new record.
Self explanatory.
Operator Response: No action is required.
Total length of all recipient identifier fields must not exceed 30.
Self explanatory.
Operator Response: Reduce the total length of the recipient fields by reducing the
length of some of the individual fields.
Reference field order (ORD) must be ascending and consecutive.
Self explanatory.
Operator Response: Make sure that the ORD field starts with one and ascends on
each line used. The maximum number is 9.
RM9137
Dataset name or name prefix (but not both) must be specified.
RM9138
Line/column location must be supplied for report ID DATA 1.
RM9139
Line/Column location must be supplied for report ID DATA 2.
© 2013 Mantissa Corporation. All rights reserved.
You have failed to enter the dataset name or the dataset prefix field.
Operator Response: Enter the dataset name or the dataset prefix, but not both.
You have entered ID data without entering the line and column coordinates to look for this
data.
Operator Response: Enter the line and column coordinates where the data is found
on the report page.
You have entered ID data without entering the line and column coordinates to look for this
data.
Operator Response: Enter the line and column coordinates where the data is found
on the report page.
409
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
RM9140
Report ID DATA 2 must not be specified without report ID DATA 1.
Self explanatory.
Operator Response: If only one character string is used to distinguish a report then
it must be entered in the ID data 1 field.
RM9141
Specified media not recognized.
RM9142
No data available to list.
RM9143
RM9144
The media entered is not one of the seven available media categories.
Operator Response: Enter one of the following categories:
HARDCOPY
TAPE
MICROFICHE
DASD
REMOTE
NETWORK
SOFTCOPY.
No records available to list for this selection.
Duplicate media priorities are not permitted.
You have entered the same number for two or more media types.
Operator Response: Correct the one that is incorrect and re-enter the transaction.
The distribution master must designate at least one recipient field
sequence/field name/field length.
You must enter at least one recipient field.
Operator Response: Enter a recipient field with the correct order and length.
RM9145
RM9146
Recipient name/length should be specified for each field.
You must enter a name and length for each recipient field.
Operator Response: Enter the name and length attribute for each recipient field.
Only one recipient field may participate in packet name
formation.
Self explanatory.
Operator Response: Choose which single field should participate in the packet
naming.
RM9147
Packet name must contain asterisks indicating the point at which participant field is to be inserted for name information.
You must indicate the place to insert the named recipient field information into the packet
name. An example might be a packet name of COMP*** with the three digit company
number being inserted into the name. The resulting packets might be COMP001/
COMP002/COMP003, etc.
Operator Response: Indicate the place to insert the recipient data in the packet name
by placing asterisks where the recipient data is to be placed.
RM9148
410
Yes/no type option fields may contain a space, n, or y only.
Self explanatory.
Operator Response: Enter one of the correct values.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
RM9149
Location name must contain asterisks indicating the point at which
participant field is to be inserted for name information.
You must indicate the place to insert the named recipient field information into the location name. An example might be REGION**COMP*** with the two digit region and the
three digit company being inserted into the location name. The results might be packets
with location name of REGION01COMP001, REGION01COMP002,
REGION02COMP001, REGION02COMP002, etc.
Operator Response: Indicate the place where the recipient data is to be placed in the
location name field by putting asterisks in the LOCATION NA field.
RM9150
Extraneous information in panel area is reset. This is caused by keying
into a line with no recipient field name.
Self explanatory.
Operator Response: No action required.
RM9151
Either Location*ID or Recipient Field Elements and associated fields
are required.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
Self explanatory.
Operator Response: Enter the fields required.
RM9152
Information entered exceeds the maximum length for the field.
RM9153
Distribution Instruction Set does not exist.
RM9154
Index Title is required unless APND ==> Y is specified.
RM9155
Valid date in the form YYMMDD is required.
RM9156
Valid condition codes for process codes are: EQ, GE, GT, LE, LT, NE.
RM9157
Cancel procedure submitted.
RM9158
Duplicate field names are not permitted in the Options Record.
© 2013 Mantissa Corporation. All rights reserved.
Self explanatory.
Operator Response: See the length attribute displayed for the maximum length you
may enter.
There is not a Distribution Set on file for the name entered in the DIST SET NAME field.
Operator Response: Enter the correct set name.
You must specify a title for the report. This will be placed on the Manifest Report.
Operator Response: Enter the title you want this report to have on the Manifest
Report.
Self explanatory.
Operator Response: Enter the date in the correct format.
Self explanatory.
Operator Response: Enter the correct condition code.
The cancel procedure has been submitted to the internal reader for execution.
Operator Response: Upon termination, all queued cancel requests will have been
processed.
You have entered an identical recipient field name. Each recipient must have a unique
411
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
System Reference Guide
name assigned to that field.
Operator Response: Enter a unique name for each recipient field.
RM9159
The field order designated did not exist in the old Instruction Set.
RM9160
The Instruction Set deletion/reorganization completed
successfully.
Self-explanatory.
Operator Response: Enter the fields as they currently exist in the old instruction set.
Self explanatory.
Operator Response: No action required.
RM9161
The Instruction Set deletion/reorganization F A I L E D.
RM9162
File error creating the QXACDS file.
RM9163
Job submitted to internal reader.
RM9164
Find Limit reached, press PF5 to continue search.
RM9165
The Instruction Set specified for deletion/reorganization was not found or a file error
occurred.
Operator Response: Check the name for error.
A VSAM error return code has been received attempting to write to the QXACDS.
Operator Response: Ensure that the file is not open to another job and that is has
been allocated correctly.
The JCL selected for batch processing has been submitted to the internal reader.
Operator Response: N/A
Self-explanatory.
Operator Response: No action required unless continuing the search.
User ID must be entered for secured format add/delete/retrieve.
A correct user ID must be entered for this transaction.
Operator Response: Enter the user ID for which you want this format transaction to
apply.
RM9166
Your viewing profile prevents use of this command.
RM9167
Sequence error encountered writing to target subsystem continuing.
Self-explanatory.
Operator Response: See your system administrator or your security officer for use
of this transaction.
A sequence error has been detected in the data object of a report being processed during a
restore operation.
Operator Response: Check for an abend of RM80004 sending work to System
Administration or a prior run of the restore that did not complete successfully.
RM9168
412
Error, FROM and TO Instruction Sets are the same.
Self-explanatory.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS/Online® Version 11.35
RMS Messages
Messages
RM Codes
System Reference Guide
Operator Response: Choose another name for the “from” or the “to” set name.
RM9169
Error, Target Instruction Set already exists.
RM9170
Error in XPCC identification.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM9171
Self-explanatory.
Operator Response: Choose another name for the target set name.
An error has occurred while starting (FUNC=IDENT) the interface to VSE/POWER. Connection to VSE/POWER is not possible at this time.
Error in XPCC connect.
An error has occurred while attempting to establish a communication path
(FUNC=DCONNECT) with VSE/POWER.
RM9172
Error in XPCC DISCONNECT.
RM9173
Error in XPCC TERMINATE.
RM9174
Error in XPCC SENDR.
RM9175
VSE/POWER busy- connect not possible now.
RM9176
No Terminating Find Delimiter entered, please re-enter.
RM9177
Entered data does not match secured field pattern.
RM9178
File error creating the QXDCDS.
RM9179
Record exists- used as template. Change as desired.
RM9180
Report Index Update now in progress.
© 2013 Mantissa Corporation. All rights reserved.
An error has occurred while attempting to stop a communication path (FUNC=DISCONN) with VSE/POWER.
An error has occurred while attempting to terminate use of the VSE/POWER interface
(FUNC=TERMIN).
A service request to VSE/POWER (FUNC=SENDR) has failed.
Self explanatory.
The find transaction with a quote for a beginning delimiter was entered, but no termination
quote was used.
Operator Response: Re-enter command with beginning and ending quotes around
the characters to find.
An attempt to enter data not allowed by Field Level Security was encountered.
Operator Response: Check with your security officer or System Administrator.
A VSAM error return code has been received attempting to write to the QXDCDS.
Operator Response: Ensure that the file is not open to another job and that is has
been allocated correctly.
An update in place operation is in progress.
413
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
RM9181
RM9182
Total column selection > 240. Default (1-240) active.
A column select command was entered which designated a total column width greater
than 240.
Repository Open failed for NON-BASE dataset. Check for active subsystem.
Operator Response: Check for active subsystem.
RM9183
Output Definition record not located. Enter request with correct ID.
RM9184
Output Definition Processing has exceeded maximum profile references.
RM9185
Distribution run tracking record write or update error.
RM9186
The output definition named is not present in the file. Enter a correctly named output definition.
Allocation failed for checkpoint dataset. Cannot continue.
Self explanatory.
Operator Response: Verify location of the dataset.
RM9187
An error occurred when sending JCL to JES via the internal reader.
RM9188
At least one security group is required for this record.
RM9189
AV1 must contain a dataset prototype for RMODEL records.
RM9190
QXRCDS buffer invalidation was not able to complete successfully.
Operator Response: Contact your System Administrator.
Self explanatory.
Self explanatory.
This information message indicates you may not have access to your most recent reports.
Contact your RMS System Administrator immediately. Press ENTER to continue.
The buffer invalidation routine was unable to free the buffers for the index dataset. This is
most likely due to the datasets being set to OPEN at first access. This message could happen on any panel.
Operator Response: Press ENTER (or PF3) to continue. Once the datasets are open
you will get your updated records.
RM9191
Report is not online. Enter R to recover, P to print.
RM9192
Report is not in a recoverable state.
Self explanatory.
Operator Response: Contact your system administrator.
RM9212I Subsystem Entry (ssssssss) not found.
The I/O program tasked with retrieving a block of data, determined that a report residing
in subsystem ssssssss was unable to contact the subsystem.
414
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Messages
RM Codes
RMS/Online® Version 11.35
RMS Messages
RMS Abend Codes
RM Codes
System Reference Guide
Operator Response: Contact your system administration to make sure the requested
subsystem is active and retry.
RM9213I Version modification level mismatch detected by xxxxxxxx.
Pgmvml=pppp Sysvml=ssss.
The report viewing program xxxxxxxx detected different version modification levels
between the program and the system values.
Operator Response: Contact your system administration to make sure the programs
and system initialization tables are in sync.
RM9214I System failed to locate DD statement for the file identified as:
xxxxxxxx.
The I/O program tasked with retrieving a block of data, determined that a subsystem
extent file xxxxxxxx was not found.
Operator Response: Contact your system administration to make sure the programs
and system initialization tables are in sync.
RM9215I I/O module cannot match the trancode tttt and subsystem ssss for
pgm=RM1135 . (UT90066 (obtainFi))
Under CICS, the following will usually follow:
+DFHAP0001 CICSTS32 An abend (code 0C1/AKEA) has occurred at offset
X'00048352' in module RM1135.
After these two, depending on the request, several ASR? Planned abends could occur.
The cause of the abend in CICS was due to the fact that the RMS online system component (RM1135) SPOOL file table was incorrectly initialized on first use. The transaction
code used was defined to CICS and in RMSOLGEN but the subsystem referenced in the
RCDS entry for the transaction set was not started. This left the SPOOL file table corrupted in memory. Even later, when a valid transaction is subsequently entered, RMS
can’t handle the corrupted file table and forces an abend (X’CCCCCCCC’).
From the message above, the tttt transaction set pointed to a set of VSAM files. When a
report was selected from the RCDS which believed the report was housed in the ssss subsystem, the code tried to initialize and access ssss. ssss was not setup for the tttt transaction set and the routine did not initialize the SPOOL file table correctly.
Operator Response: The only way to recover is to cycle CICS and use a valid transaction.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
RM999X --- Error 999, Internal Error ---
This message is for internal use by Mantissa Corporation.
RMS ABEND CODES
RMS, where possible, returns an error message to help the user diagnose a problem. When this is not possible, the
batch job or the online transaction will abend with an RMS abend code.
MVS Batch Abend Codes
Batch jobs abend with a user abend of U30nn:
where 30 is the RMS prefix assigned during installation
and nn is the two digit RMS abend code listed in the following pages.
© 2013 Mantissa Corporation. All rights reserved.
415
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
System Reference Guide
VSE Batch Abend Codes
Batch jobs abend with a system abend of 0C1. The following message will be displayed at the system console prior to
the 0C1 abend:
nn - RMS ABEND HAS OCCURRED.
where nn is the two digit RMS abend code listed on the following pages.
The abend code will also reside in general purpose register 2.
MVS and VSE Transaction Abend Codes
Online transactions abend with a RMnn:
where RM is the RMS prefix assigned during installation.
and nn is the two digit RMS abend code listed in the following pages.
Requirements for reporting system abends
In the event that a system abend occurs, the user is asked to provide Mantissa Customer Support with documentation
that includes:
•
A description of the problem, including any actions being taken when the abend occurred.
•
Include any return code, job statistics, JCL that may be helpful.
•
If the problem stems from distribution issues, provide the command stream that produces the packets as well as
the global manifest from the run.
•
A SYSDUMP is required to diagnose system abends. Provide the dump with the following DCB criteria so that it
can be reviewed with IPCS:
DCB=(BLKSIZE=4160,LRECL=4160,RECFM=FB)
Message format explanation:
ABEND NUMBER
TEXT
EXPLANATION
416
01
Terminal I/O invalid request.
02
Terminal I/O length error.
03
Terminal I/O map failure.
04
Map entry not in table.
Terminal type request invalid. Possible terminal entry missing. Call Mantissa Product
Support.
“LENGERR” exceptional condition returned by CICS. Call Mantissa Product Support.
CICS mapping error has occurred. May be internal, contact in house technical support. If
unable to resolve, call Mantissa Product Support.
CICS mapping error has occurred. Make sure the P2PPT = entry in your RMSOLGEN
macro (see INST01) specifies the correct name (default is RMvvrmM). Also, this module
must be defined as Res=Yes in CICS implementations.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
RMS Abend Codes
RM Codes
RMS/Online® Version 11.35
RMS/Online® Version 11.35
RMS Messages
RMS Abend Codes
RM Codes
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
System Reference Guide
05
Transaction initiate invalid request.
06
Transaction initiate I/O error.
07
Transaction initiate invalid transid.
08
Trace update invalid data.
09
Attempt to GEN key for UNDEF REC type.
10
Error encountered reading help file.
11
Unsupported terminal type used.
12
Invalid SBA string returned from CICS.
13
Too few lines in PTM record.
14
Temporary work file error.
15
System damage or Ver/Mod level mismatch.
16
Transaction ID not in install table.
17
Storage acquisition failure.
18
Wait limit exceeded for initialization.
19
System Control Record file error.
© 2013 Mantissa Corporation. All rights reserved.
Call Mantissa Product Support.
Call Mantissa Product Support.
Invalid record type passed to “key gen” module. This may be caused by corrupted working storage. Have dump available and call Mantissa Product Support.
See Installation Guide for supported terminals.
SET BUFFER ADDRESS corrupted. Have dump available and call Mantissa Product
Support.
Check tailoring macro (RMSOLGEN) and ensure that you are using the correct release of
the macro. There is a mismatch between modules that indicates prior release modules
included in current release being executed. Another possibility may be storage corruption.
Check tailoring macro (RMSOLGEN). Transaction name must match the name in the Program Control Table (PCT).
Online/Batch GETMAIN error. Increase region size.
The first transaction in RMS/Online initializes several areas. The second transaction will
wait for the process to complete. Attempt transaction again. If RM18 abend occurs again,
contact in house CICS support staff to determine why first transaction appears to be hung
in the system.
Have dump available and call Mantissa Product Support.
417
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
418
System Reference Guide
20
Access Group Record not in file.
21
Gregorian to scaler internal date invalid.
22
Data Queue Record not located.
23
Display processing (UT90028) error.
24
Program routine stack exceeded.
25
SCLVR sequence number error.
26
Batch - File open failed.
27
Symbol table invalid.
28
Abend during re-organization writing for
29
Write error on VSAM queue file.
30
Storage violation, GETMAIN header missing.
Check for invalid Gregorian date in “start date” or “end date” in RMS/DD panels, such as
SEND, COPY, etc. Also ensure that your are executing program RM80004 (not
RM80001). This can also occur when RMS/DPF reports are sent multiple times to the
same location.
This can be caused by files being restored out of synchronization. For example, the RCDS
and the RQDS have been restored from different dates. Restore both files from a backup
from the same date.
Call Mantissa Product Support.
Call Mantissa Product Support.
Have dump available. Call Mantissa Product Support.
A U3026 is representative of an empty file. During an RMS install the VSAM files are
populated and initialized by running the INST04 install job. Insure that JCL has all
required DD NAMES and dataset names present. Retrieve preceding IEC* message along
with the user abend.
An INSTRUCTION*SET*NAME already exists by that name. Using RMS/DD and
Advanced Function Menu, type transaction “DDR” and the name of any existing
INSTRUCTION*SET*NAME. The REORG panel is presented. Use the delete function
and the INSTRUCTION*SET*NAME that you were attempting to RE ORG. Hit
“ENTER” when prompted to verify the delete. This does not delete the instruction set. It
only deletes the flag that has been set during the RE ORG. Upon completion, attempt RE
ORG again, using a non-existing instruction set for the new name.
DASD I/O error.
Possible storage corruption during FREEMAIN processing. Try again. If problem persists,
call Mantissa Product Support.
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
RMS Abend Codes
RM Codes
RMS/Online® Version 11.35
RMS Messages
RMS Abend Codes
RM Codes
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
System Reference Guide
31
Rear error on page PTR record.
32
Write error on user record.
33
Read error on user record.
34
GETMAIN error.
35
Maximum record length invalid.
36
VSAM error during load.
37
VSAM error during open.
38
FREEMAIN error.
39
Table management error.
40
Table element header invalid.
41
VSAM error during read.
42
Bad return from VSAM I/O module.
43
File not available from VSAM I/O.
© 2013 Mantissa Corporation. All rights reserved.
Possible duplicate record. See abend message for 48.
DASD I/O error possible.
A GETMAIN error indicates that virtual memory is not adequate to continue processing.
In the event that the abend occurs on startupof RMS, increase the region size and retry
startup.
Abend will occur if the RMS/Online VSAM files are open to CICS. During restore
(RM90008), the 3 VSAM files must be closed and deallocated to CICS. (DCDS, RCDS,
ACDS) Ensure that files are closed/deallocated and restart the restore (RM90008) process.
Also ensure that the 3 VSAM files are included and correct in the RM90008 JCL.
RMS/Online has an internal table management program that is accessed during batch processing. This error indicates that a record in this table was not found or that there was not
enough program storage to accommodate the table. Make sure that the job has at least a
2048K region available. After increasing the region parameter, if this problem persists call
Mantissa Product Support.
Same as 39.
A common cause of a U3042 is when the user has the QXDCDS file open during processing (still in use by CICS or a TSO user) where the file should be closed. One such case
would be during a particular type of backup.
Call Mantissa Support. (Add trace DDNAME #$#$#$#$. Last one in dump contains feedback code (FDBK). User should send output from this DDNAME to Mantissa.)
A DD statement may be missing from CICS proc or File Control Table (FCT). Double
check spelling, etc. Additionally, file may be enqueued. This would be caused by incorrect
share options specified during VSAM define process. (Shareoptions must be “4,3”.)
419
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
Chapter 9: Messages and Codes
System Reference Guide
44
File full condition. DATA component of VSAM file is out of space. Check status of your
files with IDCAMS LISTCAT facility or other utilities at your site. It is recommended that
if you enlarge your DATA component, that you also enlarge the INDEX component. If file
is not out of space, check for actual I/O error on DASD volume.
45
VSAM invalid request.
46
VSAM illogic error.
47
VSAM duplicate record.
48
VSAM duplicate key.
49
50
420
I/O error returned from VSAM.
File full. (DATA component of VSAM file is out of space.) Check status of your files with
IDCAMS LISTCAT facility or other utilities at your site. It is recommended that if you
enlarge your DATA component, that you also enlarge the INDEX component. If file is not
out of space, check for actual I/O error on DASD volume.
INDEX component full. During DEFINE process, be sure to specify space parameter for
the INDEX component. IDCAMS may default to one track at your site. Remember also
that RM80004 program to update the online files may not be run until something is loaded
to the VSAM files. Use the Backup file and RM90008 to load from.
A duplicate record has been added to a VSAM file. This error is passed to us from VSAM
processing. Possible cause: record has been added or modified by program other than
Mantissa supported software. These files must be maintained and updated by our software
and never altered by other methods. Utilities capable of exporting VSAM files are permissible. The duplicate record may be deleted with IDCAMS utility. Normal additions, deletions and changes must be performed by our programs. This will prevent this and other
errors.
Same as 47.
Dataset ID error.
This is a common error presented if the DDNAME within the online assembler macro
(RMSLOGEN) does not have a matching entry in the File Control Table (FCT). To diagnose, provide the user’s CLIST JCL and an IDCAMS print or hex dump of the QXCNTRL file and the CDRMS2 online customization member to Mantissa Customer Support.
File not open.
Files are not open to CICS. Open files to CICS. Caution: if RESTORE (RM90008) is in
progress, do not open files until it has completed. (see code 36)
51
Garbage control data passed to SC90009.
52
Dynalloc for internal reader failed.
53
Read error on report queue.
This may be caused by an internal procedure that prohibits submission of jobs to the internal reader from CICS. This is site controlled and is usually managed with security exits or
JES submission exits. Contact your technical support staff.
Read error on RQDS VSAM file. Possible disk I/O error. Try again and if problem per-
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
RMS Abend Codes
RM Codes
RMS/Online® Version 11.35
RMS/Online® Version 11.35
RMS Messages
RMS Abend Codes
RM Codes
System Reference Guide
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
sists, call Mantissa Product Support.
54
File/program version/modification level mis-match.
55
Open failed on repository files.
56
Version/modification level mis-match.
57
Invalid data block within RQDS.
58
Error returned from ESF call interface.
59
Error reading auxiliary storage record from ACDS.
60
VSAM control file initialization failure.
61
Dynamic allocation failure.
62
Damaged storage management.
63
No record found in data component.
64
Repository dataset (non-base) open failed.
© 2013 Mantissa Corporation. All rights reserved.
Insure that you are executing intended level of software. An IDCAM print of the first
record for either the QXACDS / QXDCDS or the QXRCDS will indicate a version stamp
for each file. If the files are found to be mismatched, use the INST03 install job to delete
and redefine the files, run the INST04 job to recreate the correct QXCNTRL file. (see
code 15)
RQDS or RDDS datasets or DD statements not found.
(see codes 15 and 54)
A RMS/DPF print request has been issued (SPRINT). The report requested has no “top of
from” (skip to channel one). The program is expecting an indicator within this block of
data and it does not exist. It is not possible to print this particular report via RMS/DPF. It
is recommended that all reports routed to RMS/DPF contain a “top of form” indicator.
An error occurred while this system was attempting to open or process a print dataset.
Check the status and name of the RMS subsystem and retry the function.
The transaction information normally found in the ACDS file was not there. This transaction was restarted after the backup and restore process or the files have been changed since
the last enter was made. Re-enter RMS/Online as normal.
The initialization of the VSAM control file has failed. Check the control cards for errors in
the DDNAME and DSNAME areas.
An attempt to dynamically allocate a dataset has failed. Check for internal security restrictions.
This is usually an indicator that the online CICS component has been overlaid or its storage corrupted. Insure the programs are marked resident.
The data component pointed to by the report control dataset (QXRCDS) is missing. The
data in the repository has been deleted.
The error is indicative of a problem with the subsystem. Check to see if the subsystem is
down.
421
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
65
Invalid blocksize specified in common area.
66
VSAM No space available for adding records.
67
Unsupported DTFMT macro used in batch customization.
U0001
A disastrous error has occurred in RMS. Previously issued message(s) may explain the
actual cause of the abend.
U0111
Error detected in the Recovery exit for a VTAM virtual printer session.
U0506
The control block validation routines in the subsystem support module will abend a program with this abend code if the program has modified one or more file control blocks.
U0722
If a program creating a spool file exceeds the specified output limit, then it will be terminated with this abend code.
U0998
Freemain error.
U0999
Getmain error.
U2456
If a program using a subsystem dataset invalidates a subsystem access method control
block, this abend code may be issued.
S0C4
This abend code may occur in an application program if it passes to a RMS interface routine an invalid parameter list address or a parameter list which is not read/write accessible
under the caller’s protection key.
The blocksize specification in the batch generation process is incorrect. This is not a user
specified option. The error is caused by a change to the RMSBGEN macro or storage has
been overlaid.
Transaction ID for RMS/Online has failed due to a VSAM file out of space condition. At
RMS installation, if you chose to use the work file in CICS, verify that this is not the culprit. The RM66 abend is is normally preceded with a DFHAC2206 CICS message that
represents a time applid Transaction tranid failed condition with module DFHTFP
involved. Updates to local recoverable resources will be backed out. Transaction tranid is
abnormally terminated. Any changes to recoverable resources in the local system that
have been performed by the current unit of work are also backed out. The abend code is
either a CICS transaction abend code or a user abend code generated by a CICS ABEND.
Usually a DFHAC2236 message is sent to the master terminal operator. In a transaction
routing environment, the original cause of the failure is usually indicated in the conditional message. If the abend is issued by an IBM program product other than CICS, the
code is documented in the library of that other product.
Action: Run a LISCAT against all VSAM files to verify whether a full file exists.
Once the full file is determined, repro the information from the file, run an IDCAMS
Delete/Redefine to enlarge the file. The information can then be repro'd back into the
newly defined file.
Resubmit the transaction after the cause of the original abend has been corrected or
removed.
Contact Mantissa Product Support.
Requirements for reporting system abends
In the event that a system abend occurs, the user is asked to provide Mantissa Customer Support with documentation
that includes:
422
© 2013 Mantissa Corporation. All rights reserved.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
RMS Abend Codes
RM Codes
RMS/Online® Version 11.35
RMS Messages
Call Status Codes
RM Codes
System Reference Guide
•
A description of the problem, including any actions being taken when the abend occurred.
•
Include any return code, job statistics, JCL that may be helpful.
•
If the problem stems from distribution issues, provide the command stream that produces the packets as well as
the global manifest from the run.
•
A SYSDUMP is required to diagnose system abends. Provide the dump with the following DCB criteria so that it
can be reviewed with IPCS:
DCB=(BLKSIZE=4160,LRECL=4160,RECFM=FB)
CALL STATUS CODES
From ESFOPEN/ESFOPNC Interface
The status code is passed back in the first two bytes of the caller’s parameter list.From ESFOPEN/ESFOPNC
Interface
CODE
‘ ‘
NA
NC
NS
PE
RC
UE
01
02
03
04
05
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
06
07
08
09
12
13
© 2013 Mantissa Corporation. All rights reserved.
MEANING
Two EBCDIC spaces mean successful completion of the open request.
RMS interface is not active or not permitting open requests.
RMS was generated without CICS support, and a call was issued to ESFOPNC.
No storage was available for interface control blocks. You may try the request
later.
One or more parameters in the caller’s parameter list were in error.
The open request has been cancelled by RMS. This usually means that RMS has
abnormally terminated.
The request has been rejected by the interface exit.
The open request has been rejected because the RMS file queue was full.
The open request has been rejected because no more spool space was available.
The open request has been rejected because no storage was available for control
blocks. Please notify the systems department.
The open request has been rejected because no file exists with the requested file
sequence number.
The open request has been rejected because the specified file owner name does
not match the owner name of the requested file.
The open request has been rejected because the specified file destination name
does not match the destination name of the requested file.
The initial open request has been rejected because the file was not permanently
closed.
This status code indicates a logical error in the RMS interface. Please notify the
systems department.
The open request has been rejected because RMS has detected that one of the
file’s control blocks is in error.
The modify open request has been rejected because the file was not temporarily
closed.
Same as status code 12, except that it will appear if the file is not temporarily
closed for output processing.
423
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
CODE
14
15
16
17
18
19
20
21
22
32
34
36
40
MEANING
Same as status code 12, except that it will appear if the file is not temporarily
closed for input processing.
The open request has been rejected because the file is being purged.
The open request has been rejected because the file has no valid user track allocation map.
The open request has been rejected because the file has affinity for another system.
Not used.
The open request has been rejected because the file is awaiting transfer to the
primary JES system.
The open request has been rejected because the file is currently being printed on
a network printer node.
Open rejected by system security.
The initial open output request has been rejected because an undefined file destination was specified.
The open request has been rejected by the security system because the caller has
no access to the requested network group.
The open request has been rejected by the security system because the request is
issued by an undefined userid.
The open request has been rejected by the security system because the request is
issued by an undefined userid.
The open request has been rejected because a pre V10.0 parameter list has been
used and the system is defined with MAXFSEQ > 65535.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
Call Status Codes
RM Codes
424
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
RMS Messages
From ESFCLOS Interface
RM Codes
System Reference Guide
FROM ESFCLOS INTERFACE
CODE
‘ ‘
CE
Two EBCDIC spaces mean successful completion of the close request.
File control block validation error. The file control block interface address in the
parameter list is not valid or points to a control block not defining the requested
file, or the file is not opened by the calling task.
The output limit was exceeded.
A privileged task has obtained control of the requested file’s control blocks.
RMS interface is not active.
File with requested file sequence number has not been opened by caller’s task.
No storage was available for interface control blocks. You may try the request
later.
One or more parameters in the caller’s parameter list were in error.
Close request cancelled by RMS. This usually means that RMS has abnormally
terminated.
Chain error detected locating the subsystem vector table (SSVT) set by AESFPRIV.
The request has been rejected by the interface exit.
The close request has been rejected because the file with the specified file
sequence number could not be located.
The close request has been rejected because mismatching file owner names
were detected. This usually indicates a logical error in the interface program.
Please notify the systems department.
The close request has been rejected because mismatching file destination names
were detected. This usually indicates a logical error in the interface program.
Please notify the systems department.
The close request has been rejected because the file was already closed.
The close request has been rejected. This status code indicates a logical error in
the interface program. Please notify the systems department.
The close request has been rejected because an invalid dataset identification key
has been detected in a spool block.
The close request has been rejected because the file is currently busy on another
system in the multi access spool (MAS) configuration.
The close request has failed, because the file queue was full, so all the copies of
a multiple destination file were not created.
OL
IU
NA
NO
NS
PE
RC
SS
UE
01
02
03
04
05
06
07
11
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
MEANING
FROM ESFWRIT INTERFACE
CODE
‘ ‘
CE
IU
NA
© 2013 Mantissa Corporation. All rights reserved.
MEANING
Two EBCDIC spaces mean successful completion of the write request.
File control block validation error. The file control block interface address in the
parameter list is not valid or points to a control block not defining the requested
file, or the file is not opened by the calling task.
A privileged task has obtained control of the requested file’s control blocks.
RMS interface is not active.
425
CHAPTER 9: MESSAGES & CODES
Chapter 9: Messages and Codes
RMS/Online® Version 11.35
Chapter 9: Messages and Codes
System Reference Guide
CODE
NO
NS
OL
PE
RC
SS
UE
01
02
03
04
05
06
07
08
MEANING
File with requested file sequence number has not been opened.
No storage was available for interface control blocks. You may try the request
later.
The write request has been rejected because the output limit was exceeded.
One or more parameters in the caller’s parameter list were in error.
Write request cancelled by RMS. This usually means that RMS has termianted
abnormally.
Chain error detected locating the subsystem vector table (SSVT) set by AESFPRIV.
The request has been rejected by the interface exit.
The write request has been rejected because the file with the requested file
sequence number could not be located.
The write request has been rejected because mismatching file owner names
were detected. This status code usually indicates a logical error in the interface
program. Please notify the systems department.
The write request has been rejected because mismatching file destination names
were detected. This status code usually indicates a logical error in the interface
program. Please notify the systems department.
The write request has been rejected because the file was not opened for output
processing.
The write request has been rejected. This status code indicates a logical error in
the interface program. Please notify the systems department.
The write request has been rejected because an invalid dataset identification key
has been detected in a spool block.
The write request has been rejected because no more spool space was available.
The record has been discarded.
The write request has been rejected because the file is currently busy on another
system in the multi access spool (MAS) configuration.
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
CHAPTER 9: MESSAGES & CODES
RMS Messages
From ESFWRIT Interface
RM Codes
426
© 2013 Mantissa Corporation. All rights reserved.
RMS/Online® Version 11.35
RMS Messages
From ESFREAD Interface
RM Codes
System Reference Guide
FROM ESFREAD INTERFACE
CODE
‘ ‘
CE
IU
NA
NS
PE
RC
SS
UE
01
02
03
04
05
06
Chap_09(v11r35m1).fm: Revised Sunday, November 24, 2013
07
08
09
10
11
21
22
23
© 2013 Mantissa Corporation. All rights reserved.
MEANING
Two EBCDIC spaces mean successful completion of the read request.
File control block validation error. The file control block interface address in the
parameter list is not valid or points to a control block not defining the requested
file, or the file is not opened by the calling task.
A privileged task has obtained control of the requested file’s control blocks.
RMS interface is not active.
No storage was available for interface control blocks. You may try the request
later.
One or more parameters in the caller’s