0% found this document useful (0 votes)

452 views221 pages

GC32 9138 00

Self

Uploaded by

Sutti Karthik S J

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

452 views221 pages

GC32 9138 00

Self

Uploaded by

Sutti Karthik S J

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 221

Configuration and Customization Guide

AF/OPERATOR®

Version 340

GC32-9138-00

September 2002

Candle Corporation
201 North Douglas Street
El Segundo, California 90245-9796
Registered trademarks and service marks of Candle Corporation: AF/OPERATOR, AF/PERFORMER, AF/REMOTE, Availability Command Center,
Candle, Candle Command Center, Candle Direct logo, Candle Electronic Customer Support, Candle logo, Candle Management Server, Candle Management
Workstation, CandleNet Portal, Candle Technologies, CL/CONFERENCE, CL/SUPERSESSION, CommandWatch, CandleNet Command Center, CT, CT/Data
Server, CT/DS, DELTAMON, eBA, eBA*ServiceMonitor, eBA*ServiceNetwork, eBusiness Assurance, eBusiness Institute, ETEWatch, IntelliWatch, IntelliWatch
Pinnacle, MQSecure, MQView, OMEGACENTER, OMEGAMON, OMEGAMON/e, OMEGAMON II, OMEGAMON Monitoring Agent, OMEGAVIEW,
OMEGAVIEW II, PQEdit, Solutions for Networked Applications, Solutions for Networked Businesses, and Transplex.
Trademarks and service marks of Candle Corporation: Alert Adapter, Alert Adapter Plus, Alert Emitter, AMS, Amsys, AutoBridge, AUTOMATED
FACILITIES, Availability Management Systems, Candle Alert, Candle Business Partner Logo, Candle Command Center/SentinelManager, Candle
CommandPro, Candle CIRCUIT, Candle eDelivery, CandleLight, CandleNet, CandleNet 2000, CandleNet eBP, CandleNet eBP Access, CandleNet eBP
Administrator, CandleNet eBP Broker Access, CandleNet eBP Configuration, CandleNet eBP Connector, CandleNet eBP File Transfer, CandleNet eBP Host
Connect, CandleNet eBP Object Access, CandleNet eBP Object Browser, CandleNet eBP Secure Access, CandleNet eBP Service Directory, CandleNet eBP
Universal Connector, CandleNet eBP Workflow Access, CandleNet eBusiness Assurance, CandleNet eBusiness Exchange, CandleNet eBusiness Platform,
CandleNet eBusiness Platform Administrator, CandleNet eBusiness Platform Connector, CandleNet eBusiness Platform Connectors, CandleNet eBusiness
Platform Powered by Roma Technology, CandleNet eBusiness Platform Service Directory, CCC, CCP, CEBA, CECS, CICAT, CL/ENGINE, CL/GATEWAY,
CL/TECHNOLOGY, CMS, CMW, Command & Control, Connect-Notes, Connect-Two, CSA ANALYZER, CT/ALS, CT/Application Logic Services, CT/DCS,
CT/Distributed Computing Services, CT/Engine, CT/Implementation Services, CT/IX, CT/Workbench, CT/Workstation Server, CT/WS, !DB Logo, !DB/DASD,
!DB/EXPLAIN, !DB/MIGRATOR, !DB/QUICKCHANGE, !DB/QUICKCOMPARE, !DB/SMU, !DB/Tools, !DB/WORKBENCH, Design Network, DEXAN, e2e,

eBAA, eBAAuditor, eBAN, eBANetwork, eBAAPractice, eBP, eBusiness Assurance Network, eBusiness at the speed of light, eBusiness at the speed of light logo,
eBusiness Exchange, eBusiness Institute, eBX, End-to-End, ENTERPRISE, Enterprise Candle Command Center, Enterprise Candle Management Workstation,
Enterprise Reporter Plus, EPILOG, ER+, ERPNet, ESRA, ETEWatch Customizer, HostBridge, InterFlow, Candle InterFlow, Lava Console, MessageMate,
Messaging Mastered, Millennium Management Blueprint, MMNA, MQADMIN, MQEdit, MQEXPERT, MQMON, NBX, NetGlue, NetGlue Extra, NetMirror,
NetScheduler, OMA, OMC Gateway, OMC Status Manager, OMEGACENTER Bridge, OMEGACENTER Gateway, OMEGACENTER Status Manager,
OMEGAMON Management Center, OSM, PC COMPANION, Performance Pac, PowerQ, PQConfiguration, PQScope, Response Time Network, Roma, Roma
Application Manager, Roma Broker, Roma BSP, Roma Connector, Roma Developer, Roma FS/A, Roma FS/Access, RomaNet, Roma Network, Roma Object
Access, Roma Secure, Roma WF/Access, Roma Workflow Access, RTA, RTN, SentinelManager, Somerset, Somerset Systems, Status Monitor, The Millennium
Alliance, The Millennium Alliance logo, The Millennium Management Network Alliance, TMA2000, Tracer, Unified Directory Services, Volcano and ZCopy.
Trademarks and registered trademarks of other companies: AIX, DB2, MQSeries and WebSphere are registered trademarks of International Business
Machines Corporation. SAP is a registered trademark and R/3 is a trademark of SAP AG. UNIX is a registered trademark in the U.S. and other countries,
licensed exclusively through X/Open Company Ltd. HP-UX is a trademark of Hewlett-Packard Company. SunOS is a trademark of Sun Microsystems, Inc. All
other company and product names used herein are trademarks or registered trademarks of their respective companies.

Threaded Environment for AS/400, Patent No. 5,504,898; Data Server with Data Probes Employing Predicate Tests in Rule Statements (Event Driven
Sampling), Patent No. 5,615,359; MVS/ESA Message Transport System Using the XCF Coupling Facility, Patent No. 5,754,856; Intelligent Remote Agent for
Computer Performance Monitoring, Patent No. 5,781,703; Data Server with Event Driven Sampling, Patent No. 5,809,238; Threaded Environment for
Computer Systems Without Native Threading Support, Patent No. 5,835,763; Object Procedure Messaging Facility, Patent No. 5,848,234; End-to-End
Response Time Measurement for Computer Programs, Patent No. 5,991,705; Communications on a Network, Patent Pending; Improved Message Queuing
Based Network Computing Architecture, Patent Pending; User Interface for System Management Applications, Patent Pending.

NOTICE: This documentation is provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions set forth in
the applicable license agreement and/or the applicable government rights clause.
This documentation contains confidential, proprietary information of Candle Corporation that is licensed for your internal use only. Any unauthorized use,
duplication, or disclosure is unlawful.

2 AF/OPERATOR Configuration and Customization Guide V340

Contents

Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

What’s New in AF/OPERATOR Version 340 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 1. About the Customizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Customization Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Before You Begin Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Required Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Required Final Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Optional Customization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Chapter 2. Required Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Customization Considerations (Step 0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Define Systems in Complex (Step 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Define Address Spaces for Each System (Step 2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
JES Customization (Step 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Define Address Space Environment (Step 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Chapter 3. Optional Application and Feature Customization. . . . . . . . . . . . . . . . . . . . . . . . 49

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
CICS Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
IMS Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Installing the IMS DFSCMTI Command Processor for IMSCMD . . . . . . . . . . . . . . . . . .57
Configuring the AF/OPERATOR BMP for IMSCMD and the IMS Transaction Execution
Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Configuring AF/OPERATOR to Permit IMSCMD to Issue Transactions . . . . . . . . . . . . .63
JES3 Command and WTO Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Logmode Table for VTAM-Connected Optional Features . . . . . . . . . . . . . . . . . . . . . . . .68
MSMF (Peer-to-Peer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
NetView Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
OMEGAMON Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
OMEGAVIEW Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Programmerless Open VTAM Interface (POVI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
TCP/IP Trusted HOSTNAME Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Subsystem Logging Facility Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

Contents 3
Chapter 4. Accessing and Exiting the Customizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Accessing the Customizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Exiting the Customizer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Chapter 5. Manual Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Required Manual Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Verifying Required Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
Optional Manual Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Enabling the Sysplex RSV pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
CICS Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
IMS Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100
JES3 Command and WTO Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101
Running AF/OPERATOR without JES3 after an IPL . . . . . . . . . . . . . . . . . . . . . . . . . .102
VTAM Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
NetView Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
POVI and/or OMEGAMON Virtual Terminal Support . . . . . . . . . . . . . . . . . . . . . . . . .106
OMEGAVIEW Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
Programmerless Open VTAM Interface (POVI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108
Logmode Table Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
TCP/IP Trusted HOSTNAME Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
Reconfirming Required Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112

Chapter 6. Reviewing Your Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Complex Overview Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
System Overview Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117

Chapter 7. Starting and Stopping AF/OPERATOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Starting AF/OPERATOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
Stopping AF/OPERATOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128

Chapter 8. Customizing the AF/OPERATOR User Interface . . . . . . . . . . . . . . . . . . . . . . . 129

Customizing the Interface Using the Customizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
Verifying the User Interface Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132

Chapter 9. AF/OPERATOR Startup Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Startup Parameter Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135

Chapter 10. Migration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Single AF/OPERATOR Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164
AF/OPERATOR Coexistence with Existing Automation Products . . . . . . . . . . . . . . . . .165
Multiple AF/OPERATOR Address Spaces on a Single MVS System . . . . . . . . . . . . . . .167
Multiple AF/OPERATOR Address Spaces on Multiple Systems . . . . . . . . . . . . . . . . . .170
Considerations for IMS/VS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
Coexistence Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173

4 AF/OPERATOR Configuration and Customization Guide V340

Appendix A. Defaults for Customizer-Generated Members . . . . . . . . . . . . . . . . . . . . . . . . . 175
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175

Appendix B. AF/Operator Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Library Listings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180
Libraries Allocated for Each Defined Address Space . . . . . . . . . . . . . . . . . . . . . . . . . .181

Appendix C. Installing the REXX Alternate Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Appendix D. Customizing Additional Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

The Additional Utilities Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186
AOSSFTBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187
AOSSNTBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
AOSVCTBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189
AOUSRSEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190

Appendix E. Checkpointing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Checkpoint Dataset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194
Checkpointing Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195
Space Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

Appendix F. POVI and CT/Engine Element and Dataset Names . . . . . . . . . . . . . . . . . . . . . 199

Names and Name Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200

Appendix G. SMF Record Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Appendix H. Guide to Candle Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Base Maintenance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208
Enhanced Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212
Customer Support Contact Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Contents 5
6 AF/OPERATOR Configuration and Customization Guide V340
Preface

P
About This Document
This guide explains how to customize AF/OPERATOR® to the requirements of your data
center using the Customizer. Its chapters are designed to be read in sequence. The first
chapter gives an overview of the features and functions of the Customizer. Subsequent
chapters give instructions on how to use the Customizer to tailor AF/OPERATOR for your site.
The person performing this customization should be a senior-level computer operator, a
systems programmer, or a Candle representative.

Prerequisites
This guide assumes that AF/OPERATOR and related products in use at your site have been
SMP/E installed and that maintenance has been applied to bring them up to current levels of
service. For installation information, refer to Installing Candle Products on MVS.

Documentation set information

The following manuals comprise the AF/OPERATOR documentation set:
n AF/OPERATOR Configuration and Customization Guide
n AF/OPERATOR User’s Guide
n AF/OPERATOR Command Reference Manual
n AF/OPERATOR User Interface Guide
n AF/OPERATOR OMEGAMON II for SMS Data Interface
n AF/OPERATOR Message Manager
n AF/OPERATOR Started Task Manager
n AF/OPERATOR: Using the Subsystem Logging Facility
n Connecting AF/OPERATOR and AF/REMOTE Using TCP/IP
n Candle Product Messages Manual

Preface 7
Where to look for more information
For more information related to this product, please see the
n technical documentation CD-ROM that came with your product
n technical documentation information available on the Candle Web site at
www.candle.com
n online help provided with this product

Ordering additional documentation

To order additional product manuals, contact your Candle Customer Support representative.

We would like to hear from you

Candle welcomes your comments and suggestions for changes or additions to the
documentation set. A user comment form, located at the back of each manual, provides
simple instructions for communicating with the Candle Information Development
department.
You can also send email to UserDoc@candle.com. Please include "AF/OPERATOR
Configuration and Customization Guide V340" in the subject line.

8 AF/OPERATOR Configuration and Customization Guide V340

Documentation Conventions

Introduction
Candle documentation adheres to accepted typographical conventions for command syntax.
Conventions specific to Candle documentation are discussed in the following sections.

Panels and figures

The panels and figures in this document are representations. Actual product panels may differ.

Revision bars
Revision bars (|) may appear in the left margin to identify new or updated material.

Variables and literals

In examples of command syntax, uppercase letters are actual values (literals) that the user
should type; lowercase letters are used for variables that represent data supplied by the user.
Default values are underscored.
LOGON APPLID (cccccccc)
In the above example, you type LOGON APPLID followed by an application identifier
(represented by cccccccc) within parentheses.
Note: In ordinary text, variable names appear in italics.

Preface 9
Documentation Conventions

Symbols
The following symbols may appear in command syntax:

Table 1. Symbols in Command Syntax

Symbol Usage
| The “or” symbol is used to denote a choice. Either the argument
on the left or the argument on the right may be used. Example:
YES | NO
In this example, YES or NO may be specified.
[] Denotes optional arguments. Those arguments not enclosed in
square brackets are required. Example:
APPLDEST DEST [ALTDEST]
In this example, DEST is a required argument and ALTDEST is
optional.
{} Some documents use braces to denote required arguments, or to
group arguments for clarity. Example:
COMPARE {workload} -
REPORT={SUMMARY | HISTOGRAM}
The workload variable is required. The REPORT keyword must be
specified with a value of SUMMARY or HISTOGRAM.
_ Default values are underscored. Example:
COPY infile outfile - [COMPRESS={YES | NO}]
In this example, the COMPRESS keyword is optional. If specified,
the only valid values are YES or NO. If omitted, the default is YES.

10 AF/OPERATOR Configuration and Customization Guide V340

Adobe Portable Document Format

Printing this book

Candle supplies documentation in the Adobe Portable Document Format (PDF). The Adobe
Acrobat Reader will print PDF documents with the fonts, formatting, and graphics in the
original document. To print a Candle document, do the following:
1. Specify the print options for your system. From the Acrobat Reader Menu bar, select File >
Page Setup… and make your selections. A setting of 300 dpi is highly recommended as is
duplex printing if your printer supports this option.
2. To start printing, select File > Print... on the Acrobat Reader Menu bar.
3. On the Print pop-up, select one of the Print Range options for
n All
n Current page
n Pages from: [ ] to: [ ]

4. (Optional). Select the Shrink to Fit option if you need to fit oversize pages to the paper size
currently loaded on your printer.

Printing problems?
The print quality of your output is ultimately determined by your printer. Sometimes printing
problems can occur. If you experience printing problems, potential areas to check are:
n settings for your printer and printer driver. (The dpi settings for both your driver and
printer should be the same. A setting of 300 dpi is recommended.)
n the printer driver you are using. (You may need a different printer driver or the Universal
Printer driver from Adobe. This free printer driver is available at www.adobe.com.)
n the halftone/graphics color adjustment for printing color on black and white printers (check
the printer properties under Start > Settings > Printer). For more information, see the
online help for the Acrobat Reader.
n the amount of available memory in your printer. (Insufficient memory can cause a
document or graphics to fail to print.)
For additional information on printing problems, refer to the documentation for your printer
or contact your printer manufacturer.

Contacting Adobe
If additional information is needed about Adobe Acrobat Reader or printing problems, see
the Readme.pdf file that ships with Adobe Acrobat Reader or contact Adobe at
www.adobe.com.

Preface 11
Adobe Portable Document Format

12 AF/OPERATOR Configuration and Customization Guide V340

What’s New in AF/OPERATOR

W Version 340

This section provides a description of the new features that have been incorporated into
AF/OPERATOR Version 340.

TCP/IP connectivity enhancements

TCP/IP communications have been simplified by permitting you to optionally remove the AF
packet header when communicating between AF/OPERATOR and systems or applications
that are unable to comply with the Candle AF packet header protocol. You accomplish this by
means of a new option on the LINK DEFINE and COMM START commands. In addition,
new SEND and RECEIVE datatypes have been added to the COMSDRCV REXX function.
You must use the SEND and RECEIVE datatypes when you want to transfer data over a link
having the AF packet header turned off.
New keywords have been added to COMM START and COMM STOP commands. The
CONNECT_EXEC keyword on the COMM START command identifies a named exec that
runs whenever a connection to the server is established and is mandatory when you have
specified AFPACKET(OFF). The CID keyword on the COMM STOP command identifies a
particular connection to a server to be stopped.
A new COMADMIN REXX function provides GIVE and TAKE options that permit passing
ownership of a connection from one match to another.

Passing larger amounts of data on a TCP/IP match

You can now pass more data to an individual match. AF/OPERATOR will permit passing a
larger amount of parameter data to a REXX procedure. In addition, it will provide the
capability to create a conversation between matches so that multiple 32K packets can be
transferred. This is accomplished by permitting the DATARPLY datatype to code the
replylength keyword on the COMSDRCV REXX function.

Automated peer-to-peer link management

By predefining link attributes, it is now possible to automatically establish connections at
AF/OPERATOR startup. The following product changes support this function:
n The optional RECOVERY keyword on the LINK DEFINE command indicates that an
INACTIVE link having a desired state of ACTIVE is to be automatically started when the
specified server becomes available.

What’s New in AF/OPERATOR Version 340 13

n The new ACTIVATE keyword on the LINK DEFINE command indicates that a LINK
START is to be automatically attempted for a particular linkid, assuming a successful link
definition.
n The new SCOPE keyword on the LINK START command specifies those links that are to
be selected for LINK START processing according to their activation state.
n Two new startup parameters, HOSTNAME and LINKDEFS are added.
HOSTNAME(xxxxxxxx) overrides the default name of the trusted hostnames member in
RKANPAR. The LINKDEFS(xxxxxxxx) parameter overrides the default name of the link
definitions member in RKANPAR. During product startup, when TIMEOUT(nnn) is
specified on the LINKDEFS keyword, it specifies the amount of time to wait for the LINK
START command issued immediately after processing the LINKDEFS member to
complete before startup is allowed to continue.

Changes to the OPER command when RESP is specified

The OPER command issues an MVS or subsystem command. On this command, the RESP
parameter specifies that a set of line variables will receive the response text resulting from the
command. Additional parameters have been added to the OPER command when specified
with the RESP parameter:
n TIMEOUT(pp,ss): The new ss value specifies the number of seconds (from 1 through
3600) that AF/OPERATOR is to wait for each response message line from a multi-line
write to operator before assuming the response is complete.
n MAXLINES(nnnn): This new parameter specifies that a response is to be deemed
complete when the specified number of lines is received.
n ENDMSG(prefix): This new parameter specifies that the response is to be deemed
complete when the specified prefix is encountered in one of the response lines.
The ss value is also added to the OPERRESP AF/OPERATOR startup parameter.
In addition, the CMDSDRCV function has been modified such that when it causes an OPER
command with RESP specified to be executed on a remote system, it also causes an AOCASE
variable to be built when the reply from the remote system is received.

Additional modifications
n New global variables have been added for COM matches.
n A DUB_AS_PROCESS command, having the same function as the AF/OPERATOR
startup parameter of the same name, has been provided.

Storage Constraint Relief

The amount of storage constraint relief realized will vary depending on AF/OPERATOR
startup parameters and will be equal to (MAXMAT - MAXRUN) * 480 bytes.

14 AF/OPERATOR Configuration and Customization Guide V340

Online documentation
With Version 340, Candle Corporation has moved AF/OPERATOR manuals from IBM
BookMaster to Adobe FrameMaker. This move was made to better enable us to address our
customers’ needs by providing tools that enhance productivity.
One of the results of the move is that it is no longer possible to create BookManager versions
of the AF/OPERATOR manuals. However, the manuals remain available online in the Adobe
PDF version on CD-ROM and are also available on the Candle Corporation website at
www.Candle.com.
The documentation CD being provided with this release has robust and easy-to-use search
capabilities. You can search for information in multiple volumes, multiple versions, and across
products. The CD also provides easy setup of search indexes with a single click of the mouse.
If you want to order printed copies of the documentation, please contact your Candle
Support Services representative.

Enhancements to product documentation

n Additional documentation about obtaining SMF data has been added to the
AF/OPERATOR User’s Guide.
n Additional documentation about using the Probe Directive, Probe Input, and Misc. Parms
fields has been added to the OMEGACENTER Status Manager User’s Guide.

What’s New in AF/OPERATOR Version 340 15

16 AF/OPERATOR Configuration and Customization Guide V340
About the Customizer

1
Introduction
The Customizer supplied with this product is an automated facility that you use to customize
AF/OPERATOR. This Customizer may differ from other Candle Customizers that you have
used. Before starting customization, review this guide to learn about the Customizer and the
customization process.
This chapter presents an overview of the features and use of AF/OPERATOR. Other chapters
give details about the customization process and Customizer use.

Chapter Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Customization Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Before You Begin Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Required Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Required Final Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Optional Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

About the Customizer 17

Overview

Terminology
In the Customizer, a complex is defined as one or more systems connected by
communication links, with all systems accessing shared resources, such as direct access
storage device (DASD) volumes.

Components of the Customizer

The Customizer consists of dialogs that you access from the Candle Installation/Configuration
Assistance Tool (CICAT). After using CICAT to install AF/OPERATOR and apply
maintenance, you use the Customizer to guide you through the required and optional tasks of
defining variables and tailoring batch jobs in order to customize AF/OPERATOR for your
complex.

Using the CICAT

To perform the configuration process, you must perform a combination of procedures, some
using the CICAT and some performed manually. The first procedures in the process require
you to use the CICAT.
If you have not previously installed the CICAT, during the installation of this or any other
Candle product, you must do so now.
If you want to use a CICAT from a previous installation, you must ensure that it is the most
current version of the CICAT.
For information on using the CICAT, see Installing Candle Products on MVS. You must
ensure that the CICAT is correctly installed before beginning the configuration procedure.

Constraints and limitations

The Customizer has the following constraints and limitations.
n To customize a multiple-system complex, you must install AF/OPERATOR on sharable
DASDs. These storage devices must be accessible from any of the systems you define in
the complex for customization.
n The Customizer provides SMS support. This feature applies only to datasets allocated by
the Customizer. When defining runtime library information for each system, SMS users
can either specify volume/unit type or SMS storage/management classes. The Customizer
uses these values to allocate all support datasets for each AF/OPERATOR address space.
n All POVIs (if more than one is defined) must use the same security package.
n When specifying library names on any Customizer panel, always include high- and
low-level qualifiers. Do not enclose library names in quotes.
n Only one person may use the Customizer at any time. The Customization Menu records
the time, date, and user ID of the person who made the last access to each main
customization step, and enables different users to perform certain customization steps and
to share the same variable pools and statuses.

18 AF/OPERATOR Configuration and Customization Guide V340

Overview

n The job card information used by the Customizer is provided by CICAT. If you need to
change this information, you must do it from the CICAT.

The Customizer process

The Customizer’s menus and dialogs guide you through the AF/OPERATOR customization
process by presenting choices and requesting information specific to each system in your
complex. You are asked, for example, to provide the parameter list, the startup procedures,
and the VTAM® definitions for various optional features.
The Customizer then uses this information to tailor members or to generate the batch jobs
needed to customize the product. In either case, the Customizer saves the member in a
permanent dataset and places you in ISPF edit, where you can review and modify the
member if necessary.
At this point, you can have the Customizer submit a batch job for you, if it generated one, or
you may choose to submit the job at a later time. Remember to submit it later if you do not
submit it at the time it is generated. The Customizer assumes a particular step has been
completed if a job is generated, whether you submit it or not. Candle therefore recommends
that you submit jobs as they are generated.

Important
Do not change the names of AF/OPERATOR datasets while you are editing JCL. Change
them only when prompted in the Customizer panels. Because of AF/OPERATOR
dependencies, the Customizer carries dataset names to other members that must
reference them. Dataset names edited in JCL are not carried over and may cause an
error.

Sample 4-system complex

The following figure shows a 4-system complex. Systems A, B, C, and D each have access to
a set of shared DASD volumes. You can run the Customizer once to customize all defined
AF/OPERATOR address spaces in this complex.

About the Customizer 19

Overview

Multiple system complexes

You can have multiple system complexes. However, the Customizer supports only one
complex, unless the systems have sharable DASD volumes. Thus, if your multiple system
complex does not have sharable DASD volumes, you must run the Customizer separately for
each AF/OPERATOR you want to customize.

Help facility
A Customizer Help facility provides information about the parameters the Customizer asks
you to supply and the actions it is performing. Press F1 to display Help.

Restarting the Customizer

You can stop and start the Customizer if necessary. The main menu records the time, date,
and user ID that last accessed each main customization step. The Customizer provides two
displays showing the status of the customization process:
n Complex Overview panel (F10)
n System Overview panel (F11)
Both displays are accessible from the function keys on main Customizer menus.

Multiple address space support

This feature allows you to run multiple copies of AF/OPERATOR Version 320 (and above)
based products simultaneously on one MVS system.
Use of the multiple address space support feature results in

20 AF/OPERATOR Configuration and Customization Guide V340

Overview

n more efficient dispatching and sequencing of work by allowing you to dedicate different
copies of AF/OPERATOR for specific tasks. For example, you can dedicate one
AF/OPERATOR to look for IMS messages, a second for CICS™ messages, a third for
network traffic messages, and so on.
n better use of storage through access to multiple storage systems
n improved reliability, availability, and serviceability (RAS) due to the isolation of impact on
production automation by new or untested automation
n reduced need for IPLs
n the ability to run several Candle automation products on a single MVS system
n easier migration because the subsystem is independent of different product versions

Migration considerations
If you are running a pre-Version 320 environment, the following system configurations are
possible with the addition of multiple address space support in AF/OPERATOR Version 320
and later releases.
n single AF/OPERATOR compatibility
n AF/OPERATOR coexistence with existing automation products
n multiple AF/OPERATOR address spaces on a single MVS system
n multiple AF/OPERATOR address spaces on multiple systems
Each of these configurations raises issues that you must consider when migrating to
AF/OPERATOR Version 320 and later from automation products such as AF/OPERATOR
Version 250. These issues are discussed in detail in “Migration Considerations” on page 163.

AF/OPERATOR user interface

You can access the AF/OPERATOR user interface using option 2 of item A, AMS
Applications Customization, on the Primary Customization Menu.
To complete the configuration of the AF/OPERATOR user interface, perform the procedure
described in “Customizing the Interface Using the Customizer” on page 130.

About the Customizer 21

Customization Process

Overview
Customization consists of three major activities:
n Required Customization
n Optional Customization
n Required Final Customization
Note: Required customization is sometimes referred to as configuration.

Primary Customization Menu

The steps in customization are shown on the Primary Customization Menu.

Vnnn ------------------- !AMS PRIMARY CUSTOMIZATION MENU ------------------

OPTION ===>

Enter the selection number on the line above.

Selection last accessed

Required Customization Time Date Userid
==> 0 Customization Considerations
1 Define Systems in Complex
2 Define Address Spaces for Each System
3 JES Customization
4 Define Address Space Environments

Optional Application/Feature Customization Time Date Userid

A !AMS Application Customization
F Install Optional Features
U Additional Utilities

Required Final Customization Time Date Userid

5 Generate Task List and Members for Startup

F1=Help F3=Exit F5=Reset F10=Complex_Overview F11=System_Overview

Customization Considerations, selection 0 under Required Customization, involves planning

the customization and is an essential activity in the process. You will learn more about it in
“Before You Begin Customization” on page 24.

22 AF/OPERATOR Configuration and Customization Guide V340

Customization Process

Sequence of customization
This figure shows the customization process, including the Candle-recommended steps of
preparation, review, and verification. It also indicates where and how to use the Customizer
and other aids during customization. Refer to this figure as you read the overview of the
Customizer main menu functions in the following paragraphs.

About the Customizer 23

Before You Begin Customization

Overview
Successful customization depends on thorough preparation. To assist you, Candle has created
customization worksheets to help you gather and record the information you need to
customize AF/OPERATOR. The worksheets list all Customizer-controlled steps in the
customization process and provide a place to record your site’s specific customization
guidelines and preferences. See “Required Customization” on page 33 and “Optional
Application and Feature Customization” on page 49 for copies of the worksheets.

Prerequisites
This guide asssumes that AF/OPERATOR has been SMP/E installed and that maintenance
has been applied to bring it up to current levels of service. Refer to Installing Candle Products
on MVS for information.

Customization recommendations
Candle recommends you perform the following steps to prepare for customization:
1. Review this document:
2. Read any technical bulletins that accompanied your documentation set. Bulletins contain
current information about a product that may not be included in the current documentation
set.
3. Review the PSP bucket using CECS or call Candle Support Services to obtain the most
current PSP bucket. The PSP bucket may contain new information about customization not
included in the current documentation set.
4. Start the Customizer, as described in “Accessing and Exiting the Customizer” on page 83, and
display the Primary Customization Menu. Then perform the following:
a. Select step 0, Customization Considerations, to read online lists of the following
information to help you prepare for customization:
n support datasets
n product features
n naming convention for generated JCL member/logmode
n customization default values

b. Display the Help facility and read through all Help panels to
familiarize yourself with the Customizer and AF/OPERATOR customization
requirements.
5. Review the customization worksheets in “Required Customization” on page 33 and then
gather and record the information you will need to customize the Customizer. Pay particular
attention to all tasks you must perform manually before you can customize a feature. These
tasks are listed along with that feature’s worksheet.
When you have finished your preparation, you are ready to customize AF/OPERATOR.

24 AF/OPERATOR Configuration and Customization Guide V340

Before You Begin Customization

Reviewing your progress

As shown in “Sequence of customization” on page 23, you can review the status of the
customization periodically by viewing the Customizer’s Complex Overview and System
Overview panels. See “Reviewing Your Progress” on page 113 for instructions on using these
panels.

About the Customizer 25

Required Customization

Overview
On the Primary Customization Menu, Required Customization is the first major category. To
install AF/OPERATOR for each system in the complex, you must perform steps 1 through 5.
Step 0, Customization Considerations, is informational only.
Worksheets are provided in Chapter 2 for you to gather site-specific information to complete
each of these steps:
1. define systems in a complex
2. define address spaces for each system
3. JES customization
4. define address space environments
5. generate task list and members for startup

Define systems in complex (step 1)

In this step, you define the systems in your complex in terms of the following:
n system (maximum 4 characters)
n job entry subsystem
n VTAM major node
n MVS version
n disk volume serial
n disk unit type
n SMS storage class
n SMS management class
The Customizer assigns default values for Disk Volume Serial and Disk Unit Type from values
defined by the Candle Installer in the runtime library. You can add a new system definition or
browse, modify, or delete an existing definition.
The systems you define in this step must meet the Customizer’s definition of a complex; that
is, they must all have access to the same sharable DASD volumes. Otherwise, you must
consider each system separately as a single-system complex.

26 AF/OPERATOR Configuration and Customization Guide V340

Required Customization

Define address spaces for each system (step 2)

In this step, you define the address spaces for each system in your complex in terms of the
following:
n started task name
n address space number (##)
n AF/OPERATOR user interface component
n VSAM disk volume serial
n VSAM disk unit type
n VSAM SMS storage class
n VSAM SMS management class
n non-VSAM disk volume serial
n non-VSAM disk unit type
n non-VSAM SMS storage class
n non-VSAM SMS management class
The Customizer assigns default values for both the VSAM and non-VSAM Disk Volume Serial
and Disk Unit Type from values previously set in the system definition. You can add a new
address space definition or browse, modify, or delete an existing definition.
You can define up to 16 address spaces for each system you are running.
If you want to run multiple address spaces on one system, do the following:
1. Create the first address space by defining it with an RO (relative order) of zero. The RO
parameter (0–9, A–F) lets you define address spaces sequentially as you create them. This
establishes the order in which address spaces will receive all SSI traffic.
2. Create address spaces to handle specific traffic. For example, specify one for CICS
commands and WTOs, one for IMS, one for POVI, one for OMEGAVIEW, and so on. One of
these will then receive the product-specific data and perform any automation specified for this
interface.
For example, if you specify an address space with an RO of 3 to process CICS information, a
CICS command received by the address space with an RO of 0 is sent to the address space
with RO=1, then passed on to the address space with RO=2, and then to the CICS-specific
address space (RO=3), which then performs the specified action.
If you have defined only one address space per system, Candle recommends that you
designate it with an RO of zero.
Note: Resource use increases for each address space that you define for a system. Careful
consideration should be given as to your site’s needs. Whether or not you use
multiple address space support, you must define at least one address space for each
system in your complex in which automation is performed.

About the Customizer 27

Required Customization

JES customization (step 3)

This step provides JES customization as follows:

JES2 Builds the JES2 offset table for each system in your complex
The Customizer generates a batch job to receive and apply an SMP/E
usermod to build or update the JES offset table in the AF/OPERATOR load
library. You can review and edit each job before submitting it.
JES3 Builds the JES3 offset table and installs the JES3 WTO console exit (the offset
table name with an E appended) for each system in your complex
The Customizer generates a batch job to receive and apply an SMP/E
usermod to build or update the JES offset table AF/OPERATOR load library.
It also installs the JES3 WTO console exits into the AF/OPERATOR load
library. You can review and edit each job before submitting it.

The JES offset table names are user-definable.

Define address space environments (step 4)

This step is threefold:
1. You define the startup parameters for AF/OPERATOR to use at initialization in the member
and dataset you specify. The default is member OGPRMc##, which is stored in non-VSAM
dataset rhilev.RKANPAR.
If DISKMLOG=Y, the Customizer generates a batch job to allocate a set of DASD message
log datasets.
Note: When DISKMLOG=N, the fields associated with DISKMLOG are optional; when
DISKMLOG=Y, they are required.
2. You specify the load library reference method (STEPLIB or not).
The Customizer generates the AF/OPERATOR startup procedure.
3. You allocate the following basic AF/OPERATOR support datasets for each system in your
complex.
n RKOGCKP—a VSAM dataset used for checkpointing user-defined system variables and
time-of-day traps.
n RKOGLH01 and RKOGLH02—historical log datasets used by the AF/OPERATOR
RETAIN*VIEW facility.
Each AF/OPERATOR address space must have its own set of supporting datasets. The
Customizer names the datasets as follows:
CHECKPOINT rvhilev.@system##.RKOGCKP
HISTORICAL LOGS rhilev.@system##.RKOGLH01
rhilev.@system##.RKOGLH02
where rvhilev and rhilev are the high-level qualifiers, system is the system in which the
address space resides, and ## is the unique ID of the address space.
The Customizer generates a batch job to define the startup parameters, generate the started
task, and allocate the support datasets. You can review and edit the job before submitting it.

28 AF/OPERATOR Configuration and Customization Guide V340

Required Final Customization

Generate task list and members for startup (step 5)

Generate Task List and Members for Startup, step 5 on the Primary Customization Menu
under Required Final Customization, generates
n a report of the required final tasks you must perform manually to finish customizing
AF/OPERATOR for this complex
n miscellaneous startup members
You always perform this step after completing required customization steps 1 through 4 and
after any or all optional customization steps.
The report lists the
n generated VTAM nodes and startup procedures you need to copy to the appropriate
VTAMLST and PROCLIB datasets
n name of the load library you must add to your site’s APF list
n name of the load library you need to include in the LINKLISTs
n location of the Customizer-generated batch jobs
The Customizer saves the report in a temporary dataset, which you can browse and/or print.
The output libraries must be concatenated as follows:

Output library 1 In the SYSPROC ddname if you are using TSO and want to access
OG*TSO. (OG*TSO is described in detail in the AF/OPERATOR User’s
Guide.)
Output library 2 In the RKANCMD ddname of the AF/OPERATOR startup procedure.

Verifying required customization

After you have completed required customization steps 1 through 5 and the final tasks
associated with them, Candle recommends that you use the sample $$OGINIT file provided
with AF/OPERATOR to perform some simple customization verification tests. You can run
this file as the first startup command file or after initializing the product. After completing this
step successfully, you can proceed to “Optional Customization” on page 30.

About the Customizer 29

Optional Customization

Overview
Items A, F, and U on the Primary Customization Menu are optional.
n Application Customization
n Install Optional Features
n Install Additional Utilities
Using the data you have recorded on the Optional Features worksheets, complete these steps
as necessary. Online help is available to guide you through each step.

Caution
If you plan to use POVI or OG*TSO, see “Installing the REXX Alternate Library” on
page 183 to determine if you need to install the REXX Alternate Library.

Applications Customization
Item A, Applications Customization, on the Primary Customization Menu, displays a
submenu of Candle products that use AF/OPERATOR as a base component. If an application
is not installed on your system, Component not installed will appear on the submenu.

Install Optional Features

Item F, Install Optional Features, on the Primary Customization Menu, displays a submenu of
optional interfaces. You can install and customize any of these interfaces to meet your site’s
requirements.
The Customizer tailors members or generates batch jobs to install each interface you select.
You can review and edit each job before submitting it.

30 AF/OPERATOR Configuration and Customization Guide V340

Optional Customization

Install the. . . if you want to. . .

CICS Interface trap and process CICS messages written to transient data queues.
IMS Interface trap IMS MTO messages and commands.
JES3 Interface trap JES3 commands and console messages as you would MVS
console messages and commands.
Multi-System Management consolidate console traffic of remote and local sites into a
Facility (MSMF) Interface single-image console display for multiple installations or for an
installation with multiple processors.
NetView Interface communicate with the IBM NetView product using NetView’s
Program-to-Program interface. You can use NetView REXX to
execute AF/OPERATOR commands from within NetView and
retrieve AF/OPERATOR data and data obtained from other Candle
system-monitoring software, such as OMEGAVIEW.
OMEGAMON Interface communicate with any of the supported Candle OMEGAMON
products (OMEGAMON for MVS, OMEGAMON for IMS,
OMEGAMON for CICS, and OMEGAMON II for DB2®). The
OMEGAMONs monitor the performance of your systems.
OMEGAVIEW Interface post status to and read lights from one or more Candle
OMEGAVIEW products. OMEGAVIEW monitors a database of
status items that you define to give you a high-level, multisystem
overview of your complex’s health.
Programmerless Open VTAM connect AF/OPERATOR to various VTAM 3270 applications. You
Interface (POVI) can use the POVI Keystroke Recorder to play back scripts of
pre-recorded interactions with VTAM 3270 applications. POVI is
often interfaced with TSO applications, such as the IBM
Information/Management product, and schedulers, such as OPC™
and CA-7™.

Additional Utilities
Item U, Additional Utilities, on the Primary Customization Menu, displays a submenu of
optional AF/OPERATOR batch utilities. The Customizer generates the batch jobs necessary
to install these utilities and lets you review and edit the code it generates, but it does not
submit the jobs.
If you have not previously installed the IBM Library for SAA REXX/370, you must install the
REXX Alternate Library to run compiled programs. See “Installing the REXX Alternate
Library” on page 183 for the procedure.

Verifying Optional Customization

After you have completed optional customization steps F and U, and the final tasks associated
with them, Candle recommends running the sample $$OGINIT file again to make sure you
did not inadvertantly change any of the required customization parameters.

About the Customizer 31

Optional Customization

32 AF/OPERATOR Configuration and Customization Guide V340

Required Customization

2
Introduction
This chapter describes the steps you take to prepare for customizing AF/OPERATOR and
performing the required customization steps.
Required Customization consists of steps 0 through 4 on the Primary Customization Menu.
All steps use a worksheet except step 0. The worksheets help you gather information. Step 0
provides information. Photocopy and fill out a set of the worksheets for each AF/OPERATOR
address space.

Chapter Contents
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Customization Considerations (Step 0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Define Systems in Complex (Step 1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Define Address Spaces for Each System (Step 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
JES Customization (Step 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Define Address Space Environment (Step 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Required Customization 33
Before You Begin

Before You Begin

Introduction
Before you begin customizing AF/OPERATOR:
1. Obtain a copy of the list of variables that were substituted at your site during the SMP/E
installation process.
2. Complete the information-gathering worksheets in this chapter.
Completing the worksheets before starting the customization process helps you complete the
customization more quickly.
3. Perform pre-customization manual tasks, as listed.

Recommendation
After performing Required Customization or Optional Customization, use Generate Task List
and Members for Startup, step 5 on the Primary Customization Menu, to create a report of
manual steps that you must complete. See “Generate task list and members for startup (step
5)” on page 29 for more information.

Information gathering
Photocopy the worksheets and fill out one for each address space you define to the
Customizer. The worksheets list all the Customizer-controlled steps in the customization
process and provide a place to record your site’s specific customization guidelines and
preferences.
You may need to consult with your site’s JES system programmer or administrator, VTAM
system programmer or administrator, DASD manager, CICS and/or IMS administrators, and
the SMS security administrator to obtain the appropriate values for the worksheets.

Manual tasks before you customize

Some customization tasks cannot be automated. When manual customization tasks must be
performed before a feature is customized, they are listed with that feature’s worksheet.

34 AF/OPERATOR Configuration and Customization Guide V340

Customization Considerations (Step 0)

Information available
Step 0 contains online notes about the customization process and lists of Candle naming
conventions and default values. Information is presented in four categories:
n support datasets
n product features
n generated member naming conventions
n customization default values
No worksheet is required for step 0.

Required Customization 35
Define Systems in Complex (Step 1)

Define Systems in Complex (Step 1)

Introduction
Values you specify in Define Systems in Complex are used throughout the Customizer.

System Managed Storage (SMS)

If your complex uses SMS to manage datasets, you can optionally specify SMS storage class
and SMS management class for AF/OPERATOR support datasets. The disk volume/unit and
SMS storage/management class fields are mutually exclusive.

36 AF/OPERATOR Configuration and Customization Guide V340

Define Systems in Complex (Step 1)

Define systems in complex worksheet

Required Customization 37
Define Systems in Complex (Step 1)

38 AF/OPERATOR Configuration and Customization Guide V340

Define Address Spaces for Each System (Step 2)

Introduction
Address spaces that you assign to specific systems are used for multiple address space
support.

Define address spaces for each system worksheet

Customizer
Description Default Your Site
Started task name No default.
Specify the 1–8 character started task
name. The first character must be
alphabetic.
Address space ID No default.
Specify the 1–2 alphanumeric character
(##) unique address space name. ##
can be any combination of
alphanumeric and national characters.
AF/OPERATOR user interface Y If product
Specify that the AF/OPERATOR user is installed.
interface be accessed by this address N If product is not
space. installed.
Non-VSAM disk volume serial Default value is
Specify the non-VSAM disk volume inherited from the
serial ID. system definition.

Non-VSAM disk unit type Default value is

Specify the non-VSAM disk unit type. inherited from the
system definition.
Non-VSAM SMS storage class Default value is
Specify the non-VSAM SMS storage inherited from the
class. system definition.

Non-VSAM SMS management class Default value is

Specify the non-VSAM SMS managment inherited from the
class. system definition.

VSAM disk volume serial Default value is

Specify the VSAM disk volume serial ID. inherited from the
system definition.
VSAM disk unit type Default value is
Specify the VSAM disk unit type. inherited from the
system definition.

Required Customization 39
Define Address Spaces for Each System (Step 2)

Customizer
Description Default Your Site
VSAM SMS storage class Default value is
Specify the VSAM SMS storage class. inherited from the
system definition.
VSAM SMS management class Default value is
Specify the VSAM SMS managment inherited from the
class. system definition.

40 AF/OPERATOR Configuration and Customization Guide V340

JES Customization (Step 3)

Introduction
An appropriate JES offset table for each system is referenced using information you provide
in this step.

JES2/JES3 customization worksheet

Description Customizer Default Your Site

JES TYPE=JES2
JES2 offset table KOGJ2TAB
Specify the job entry subsystem type.
JES2 MACRO libraries SYS1.SHASMAC
Specify up to 3 libraries on your system
that contain the JES2 macros.

JES TYPE=JES3
JES3 offset table KOGJ3TB
Specify the job entry subsystem type.
JES3 MACRO libraries SYS1.JES3MAC
Specify up to 3 libraries on your system
that contain the JES3 macros.

Required Customization 41
Define Address Space Environment (Step 4)

Define Address Space Environment (Step 4)

Overview
In this step, you
n define the set of parameters to be used at AF/OPERATOR initialization for each address
space defined to the Customizer
n generate the AF/OPERATOR startup procedure
n allocate the AF/OPERATOR support datasets (named according to Candle’s naming
standards that are based on previously selected dataset name high-level qualifiers for
runtime datasets and are not customizable).

Define startup parameters worksheet

Use this worksheet to define startup parameters.

Note: c is the last character of the system name (defined in step 1). ## is the address space ID.

The parameters and defaults in the following table appear as listed on the Customizer panels.
The startup parameters are described in “AF/OPERATOR Startup Parameters” on page 133.

42 AF/OPERATOR Configuration and Customization Guide V340

Define Address Space Environment (Step 4)

Required Customization 43
Define Address Space Environment (Step 4)

44 AF/OPERATOR Configuration and Customization Guide V340

Define Address Space Environment (Step 4)

Required Customization 45
Define Address Space Environment (Step 4)

Generate startup procedure and allocate support datasets worksheet

Use this worksheet to generate the AF/OPERATOR startup procedure and allocate the
support datasets.

Description Customizer Default Your Site

AF/OPERATOR LOAD LIBRARY Y
REFERENCED VIA STEPLIB
Alternatively, the AF/OPERATOR load
library may be referenced by LINKLIST.
COMMAND LIBRARIES No default
Specify up to three libraries.

46 AF/OPERATOR Configuration and Customization Guide V340

Define Address Space Environment (Step 4)

Define clusters
SLF journaling requires backup datasets. They are VSAM linear datasets which can be
defined with IDCAMS as follows:
//DEFINE EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
DELETE hilev.RKOGSLF0 SCRATCH PURGE
DELETE hilev.RKOGSLF1 SCRATCH PURGE
DEFINE CLUSTER(NAME(‘hilev.OGSLF00’) -
SHR(1 3) -
CYL(pri sec) -
VOL(volser) -
LINEAR)
DEFINE CLUSTER(NAME(‘hilev.OGSLF01’) -
SHR(1 3) -
CYL(pri sec) -
VOL(volser) -
LINEAR)
The amount of space to allocate depends on the number and kind of traps you set and the
size of your system.

Define backup datasets in the startup JCL

To use journaling you must define the backup datasets to AF/OPERATOR. Add the following
DD statements to your AF/OPERATOR startup JCL:
//RKOGSLF0 DD DISP=SHR,DSN=hilev.OGSLF00,DISP=SHR
//RKOGSLF1 DD DISP=SHR,DSN=hilev.OGSLF01,DISP=SHR
You only need to add these statements to the local SLF.

Required Customization 47
Define Address Space Environment (Step 4)

48 AF/OPERATOR Configuration and Customization Guide V340

Optional Application and

3 Feature Customization

Introduction
This chapter describes the steps you take to customize AF/OPERATOR applications and
features.

Chapter Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
CICS Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
IMS Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Installing the IMS DFSCMTI Command Processor for IMSCMD . . . . . . . . . . . . . . . . . . . . 57
Configuring the AF/OPERATOR BMP for IMSCMD and the IMS Transaction Execution
Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Configuring AF/OPERATOR to Permit IMSCMD to Issue Transactions . . . . . . . . . . . . . . . 63
JES3 Command and WTO Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Logmode Table for VTAM-Connected Optional Features . . . . . . . . . . . . . . . . . . . . . . . . . 68
MSMF (Peer-to-Peer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
NetView Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
OMEGAMON Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
OMEGAVIEW Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Programmerless Open VTAM Interface (POVI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
TCP/IP Trusted HOSTNAME Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Subsystem Logging Facility Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Optional Application and Feature Customization 49

Overview

Optional Application/Feature Customization consists of 3 major categories:

1. Applications Customization
Enables you to access the AF/OPERATOR user interface and to configure related products
that use AF/OPERATOR as a base component.
Refer to the documentation that accompanies the Candle product you are installing.
2. Install Optional Features
Enables you to install several different interfaces. A worksheet for each interface is provided
in this section.
3. Install Additional Utilities
Enables you to install optional utilities. See “Customizing Additional Utilities” on page 185
for further information.

50 AF/OPERATOR Configuration and Customization Guide V340

CICS Interface

Before you customize

Before you use the Customizer to set up the CICS Interface, you need to perform a few
manual steps on the CICS global user exit, which will be used by all systems at your site that
run the interface. The instructions for systems running CICS Version 3 or 4 differ slightly from
those running Version 2. Use the method appropriate for your system.
The Customizer generates batch JCL to install the following CICS exit programs:

KABCICS for CICS Version 2

KABCICS3 for CICS Version 3 or 4

The Customizer can support both exit programs on a system.

Running CICS Version 2

Modify the source code of the CICS Interface program KABCICS as needed. KABCICS
resides in the thilev.TKANMAC library. It has two sections:
n Code that manages the enabling or disabling of a CICS global user exit (GLUE) at exit
point XTDREQ.
n Code that uses the AOSIM routine to select and forward to AF/OPERATOR any CICS
messages written to the transient data queue. (For information on AOSIM, see the
AF/OPERATOR User’s Guide.)
The first section requires no modification. In the second section, you may need to modify two
areas:
n Code to select the transient data destinations of interest. The code to filter by destination
ID is located after the label CHECKMSG. As supplied, the exit forwards messages being
sent to transient data destinations that begin with the letter C (that is, CICS reserved
destinations).
n Code to select the messages that should be forwarded to AF/OPERATOR. An example of
such code is located after the label CHEKMSG2 and commented out. As supplied, the
exit forwards all messages.
By default, this exit sends the selected messages to all active AF/OPERATOR address spaces
for processing. If you want to direct the messages to a specific AF/OPERATOR address space
instead of all AF/OPERATOR address spaces, you need to indicate the MVS subsystem name
of that AF/OPERATOR address space. (This is the value you specified for the SUBSYS startup
parameter on the specified AF/OPERATOR system.) Follow the instructions supplied in the
exit routine.

Optional Application and Feature Customization 51

CICS Interface

Running CICS Version 3 or 4

Modify the source code of the CICS Interface program KABCICS3 as needed. KABCICS3
resides in the thilev.TKANMAC library. It has two sections:
n Code that manages the enabling or disabling of a CICS global user exit (GLUE) at exit
point XTDOUT.
n Code that uses the AOSIM routine to select and forward to AF/OPERATOR any CICS
messages written to the transient data queue. (For information on AOSIM, see the
AF/OPERATOR User’s Guide.)
The first section requires no modification. In the second section, you may need to modify two
areas:
n Code to select the transient data destinations of interest. The code to filter by destination
ID is located after the label CHECKTD1. As supplied, the exit forwards messages being
sent to transient data destinations that begin with the letter C (that is, CICS reserved
destinations).
n Code to select the messages that should be forwarded to AF/OPERATOR.An example of
such code is located after the label CHECKTD2 and commented out. As supplied, the
exit forwards all messages.
By default, this exit sends the selected messages to all active AF/OPERATOR address spaces
for processing. If you want to direct the messages to a specific AF/OPERATOR address space
instead of all AF/OPERATOR address spaces, you need to indicate the MVS subsystem name
of that AF/OPERATOR address space. (This is the value you specified for the SUBSYS startup
parameter on the specified AF/OPERATOR system.) Follow the instructions supplied in the
exit routine.

CICS Interface worksheet

Photocopy and fill out a worksheet for each system that will use the AF/OPERATOR CICS
Interface. If you are running multiple releases of CICS on a system, make extra copies as
needed.

52 AF/OPERATOR Configuration and Customization Guide V340

CICS Interface

Optional Application and Feature Customization 53

IMS Interface

Before you customize

The IMS interface exit allows AF/OPERATOR to monitor IMS for messages and commands.
Before you use the Customizer to set up the IMS interface, you (or an IMS administrator)
need to perform the following manual tasks on the IMS exit, which will be used by all systems
at your site that run the interface.
1. The AF/OPERATOR IMS Interface uses the IMS user exit name DFSAOUE0.
2. Code AOEXIT=YES on the COMM macro of your IMS stage 1. (See the IBM document
IMS/VS System Definition Reference Manual for more information.)
Note: If you are running IMS 5.1 or later, you must omit this step.
3. Run IMS stage 1 to produce the IMS stage 2 JCL. You must include the library that contains
the AF/OPERATOR AOI exit in the stage 2 JCL.
If you plan to link the exit into a library other than your IMS load library, concatenate the
other library into your stage 2 JCL.

Technical considerations
If you use the IMS interface, consider the following:
n If your exit alters message text, the AF/OPERATOR AOI (KABIMX02) will receive the
altered messages.
n The return code returned to IMS is the code established by your user exit.

Candle-supplied sample exit programs

Candle supplies two sample exit programs that use the IMS command authorization exit
DFSCCMD0 (available in IMS/VS 4.1 and above).

KABIMX02 Processes commands and command responses of any number of lines.

KOGIMXCC Executed before an IMS command executes, enables command traps to be
written using the SUPPRESS keyword to allow or disallow spcified
commands.

Call sequence
The IMS interface calls the AOSIM alert facility that uses cross-memory services to report
events to the central AF/OPERATOR task. With AOSIM, subsystems that do not use the MVS
console for event reporting such as IMS can communicate with AF/OPERATOR.
IMS invokes the AOI exit before any message displays on the IMS master terminal and prior
to processing any command issued from it.

54 AF/OPERATOR Configuration and Customization Guide V340

IMS Interface

Diagram of call sequence with only the Candle exit

The following diagram represents the call sequence after installation of the Candle exit alone.
In this case, the Candle exit is named DFSAOUE0.

DFSAOUE0----(calls)----AOSIM---
|
|
(uses)
|
|
XMS----(communicates with)----AF/OPERATOR

Diagram of call sequence with your user exits

The following diagram represents the call sequence after installation of the Candle driver
(DFSAOUE0) which calls your user exit (AOIEXIT1) then calls the Candle exit KABIMX02,
KOGIMXCC, or both.

Optional Application and Feature Customization 55

IMS Interface

IMS Interface worksheet

Photocopy and fill out a worksheet for each system that will use the AF/OPERATOR IMS
Interface exit. If you are running multiple releases of IMS per system, make extra copies as
needed.

56 AF/OPERATOR Configuration and Customization Guide V340

Installing the IMS DFSCMTI Command Processor for IMSCMD

Overview
The Customizer supplies a DFSCMTI command processor ITASK, installed via the IMS
Partner Product user exit for IBM/ESA releases 5.1 and higher. DFSCMTI extends the
functionality of AF/OPERATOR to issue IMS commands. This unit describes how to install the
IMS Partner Product user exit.

Prerequisites to installing the DFSCMTI Command Processor

AF/OPERATOR version 150 or later and IBM’s IMS/VS must be installed on your system.

Modes of operation
When the DFSCMTI command processor is active in an IMS region being referenced by the
IMSCMD REXX function in AF/OPERATOR, the DFSCMTI command processor will be used
automatically to issue commands to IMS and retrieve the responses. No changes are needed
to any of the user’s existing REXX programs that invoke the IMSCMD function. The
START\STOP subfunctions of the IMSCMD function are no longer used and are disabled.

Installing the DFSCMTI Command Processor

Perform the following steps to install Customizer’s DFSCMTI command processor via the IMS
Partner Product user exit.
1. If you already have a DFSPPUE0 exit, change the source code for that exit to name the entry
point DFSPPUE1. If you do not have access to the source code, use Linkage Editor control
statements to make this change. If you need the Customizer user exit to call more than one
Partner Product user exit, rename the entry points to DFSPPUE1, DFSPPUE2, DFSPPUE3,
and (up to) DFSPPUE4. The Customizer user exit will call these exits in alphabetical order.
When linking the Customizer user exit with an existing exit, insert the following statement
before the INCLUDE statement for the existing exit:

CHANGE OLDNAME(DFSPPUEn)
where OLDNAME is the entry point of the existing exit and n is a number between 1 and 4.
This renames the entry point to DFSPPUE1 (DFSPPUE2, DFSPPUE3, or DFSPPUE4), so that
the Customizer exit can also process this exit.
Note: If you do not need the Customizer user exit to call an existing DFSPPUE0, proceed to
step 3.
2. Use the Assembly and Linkage Editor job streams in the &thilev.TKANSAM file to assemble
and link your exits. You can find the JCL to assemble and link the user exits in member
KSLPPUAL. You can find the JCL to link the user exits with the Customizer user exit in
member KSLPPULK.
3. Create a load module called DFSPPUE0 from the load module KSLUExM, where x=F for
IMS 5.1, x=G for IMS 6.1, and x=H for IMS 7.1. KSLUExM (renamed DFSPPUE0) calls any
existing DFSPPUE1, DFSPPUE2, DFSPPUE3, and DFSPPUE4, in this order. If DFSPPUE0

Optional Application and Feature Customization 57

Installing the IMS DFSCMTI Command Processor for IMSCMD

encounters a non zero return code from any of these calls, it preserves and returns the return
code to IMS. For all return codes that are zero, DFSPPUE0 now provides AF/OPERATOR
functionality to issue IMS commands.
KSLUExM depends on any called DFSPPUEx to save and restore the registers that IMS
provides to it. KSLUExM runs in 31 bit addressing mode and may reside above the 16M line.
Note: The Subsystem Logging Facility (SLF) component of AF/OPERATOR also uses the
IMS partner product user exit. The same Candle module, KSLUExM, supports both
IMSCMD and SLF and needs to be installed only once.
4. Copy the module DFSPPEU0 created in Step 3 along with all modules starting with KSL from
the &thilev.TKANMOD library into the IMS RESLIB where the exit is to be enabled.

58 AF/OPERATOR Configuration and Customization Guide V340

Configuring the AF/OPERATOR BMP for IMSCMD and the IMS Transaction Execution Interface

Configuring the AF/OPERATOR BMP for IMSCMD and the IMS

Transaction Execution Interface

Overview
Before you can use the IMSCMD function of AF/OPERATOR or the IMS Transaction
Execution Interface, you must define the AF/OPERATOR Batch Message Processing (BMP)
region to IMS as described in this unit.
Using the IMSCMD function, you can send a command to IMS from a REXX EXEC and
receive the command response. You can also issue non-interactive IMS transactions. See
“Configuring AF/OPERATOR to Permit IMSCMD to Issue Transactions” on page 63 for the
configuration changes required to use IMSCMD to issue these transactions.
Using the IMS Transaction Execution Interface, AF/OPERATOR can insert time-controlled
IMS transaction work using the BMP task. The BMP task runs as a companion address space
to the AF/OPERATOR Command Processor ITASK that is started using DFSPPUE0. The
Transaction Execution Interface is available for work during any period that the IMS control
region is available.

Prerequisites for using the AF/OPERATOR BMP

To use the AF/OPERATOR BMP, you must have installed the Command Processor support as
described in “Installing the IMS DFSCMTI Command Processor for IMSCMD” on page 57.
To use the IMS Transaction Execution Interface, you must have installed the Subsystem
Logging Facility (SLF). Information about SLF is found in the Subsystem Logging Facility
User’s Guide.

Required configuration and customization

Complete the following steps to define the AF/OPERATOR BMP to IMS:
1. Access the AF/OPERATOR Customizer and select option F.2.3, Install the IMS Command
BMP.
2. The Customizer prompts you for the name to be associated with the AF/OPERATOR BMP.
This name is used for both the PSB (Program Specification Block) and the transaction code.
The default name for both the PSB and the transaction code is KSLIMPSB. This default can
be changed if necessary, but use the same name for both the PSB and the transaction code.
Naming considerations:
A. If multiple AF/OPERATOR systems will send commands to the same IMS control
region, you must define a unique PSB and transaction code name for each
AF/OPERATOR system.
B. If only one AF/OPERATOR system will send commands to multiple IMS control
regions, you can define the same PSB and transaction code name to each IMS control
region.

Optional Application and Feature Customization 59

Configuring the AF/OPERATOR BMP for IMSCMD and the IMS Transaction Execution Interface

C. A table of IMS resource definitions, KSLBLTBL, is required for each IMS control
region based on the IMSID. It is your responsibility to keep table KSLBLTBL in sync
with the IMS resource definitions for each of the IMS control region environments.
3. The Customizer adds the name you specify to the following members stored in the
rhilev.@system.RKANSAM dataset. You can use these Customizer-generated members to
complete the installation.

Member Description
PSBACBGN JCL to run the PSB and ACB gens. The default KSLIMBMP ACB Generation
statement is provided and recommended for use:
BUILD PSB=KSLIMPSB OG/MVS BMP PSB NAME
IMSBPGEN PSBGEN utility input statements. The following default definition is provided
and recommended for use:
PSBGEN PSBNAME=KSLIMPSB, + PSB NAME FOR BMP
LANG=ASSEM
IMSBAGEN ACBGEN utility input statements.
IMSBIGEN IMS SYSGEN input statements. The following default definitions are
provided and recommended for use:
APPLCTN PSB=KSLIMPSB, +
PGMTYPE=BATCH

TRANSACT CODE=KSLIMPSB, +
MSGTYPE=(SNGLSEG,NONRESPONSE), +
MODE=SNGL

IMSBSGEN IMS Security Maintenance Utility (SMU) input statements.

4. After reviewing the JCL, submit the job named PSBACBGN to run the PSBGEN utility and
the ACBGEN utility.
More information on the JCL procedures to run the PSBGEN and ACBGEN utilities can be
found in your data center’s IMS.PROCLIB(PSBGEN) and IMS.PROCLIB(ACBGEN). More
information on the PSBGEN and ACBGEN utilities can be found in IBM’s IMS Utilities
Reference: System.
5. Optionally, to disable the IMS Transaction Execution Interface in an IMS region, specify DD
KSLNOBMP.

60 AF/OPERATOR Configuration and Customization Guide V340

Configuring the AF/OPERATOR BMP for IMSCMD and the IMS Transaction Execution Interface

6. Define each IMS environment to KSLBLTBL if unique PSB and TRANCODE names are
required. If defaults are used for all IMS region environments, it is not necessary to customize
KSLBLTBL. (See sample member KSLBLTBL for additional details about its customization.)
*
KSLBLTBL $SLBL TYPE=INITIAL,MAXABEND=10,BMPWAIT=30
*
I51B $SLBL TYPE=ENTRY,IMSID=I51B,PROC=KSLBMBMP +
PSB=I51BPSB,TRANCODE=I51BPSB,AGN=your.agn.name
*
I61C $SLBL TYPE=ENTRY,IMSID=I61C,PROC=KSLBMBMP +
PSB=I61CPSB,TRANCODE=I61CPSB,AGN=your.agn.name
*
$SLBL TYPE=FINAL
7. Define and customize each proclib member specified in the KSLBLTBL for each IMS region.
(See sample member KSLBMBMP for additional details about the customization of BMP
PROCLIB members.)*
//************************************************************************************************
//* IMS BMP PROCEDURE FOR SLF IMS TRANSACTION EXECUTION SERVICE*
//*************************************************************************************************
//KSLBMBMP PROC MBR=KSLBMXX,PSB=,IN=,OUT=,
// OPT=N,SPIE=0,TEST=0,DIRCA=000,
// PRLD=,STIMER=,CKPTID=,PARDLI=,
// CPUTIME=,NBA=,OBA=,IMSID=,AGN=,
// SSM=,PREINIT=,RGN=512K,
// ALTID=,APARM=,LOCKMAX=,
// SYS2=SMFID,SOUT=A
//*
//BMP EXEC PGM=KSLIBAM,REGION=&RGN,
// PARM=(BMP,&MBR,&PSB,&IN,&OUT,
// &OPT&SPIE&TEST&DIRCA,&PRLD,
// &STIMER,&CKPTID,&PARDLI,&CPUTIME,
// &NBA,&OBA,&IMSID,&AGN,&SSM,
// &PREINIT,&ALTID,
// ‘&APARM’,&LOCKMAX)
//*
//STEPLIB DD DSN=-THILEV-.TKANMOD,DISP=SHR
// DD DSN=IMS.VNNN.&SYS2.RESLIB,DISP=SHR
//*
//PROCLIB DD DSN=IMS.VNNN.&SYS2.PROCLIB,DISP=SHR
//*
//SYSUDUMP DD SYSOUT=&SOUT,
// DCB=(LRECL=121,RECFM=VBA,BLKSIZE=3129),
// SPACE=(125,(2500,100),RLSE,,ROUND)

Optional Application and Feature Customization 61

Configuring the AF/OPERATOR BMP for IMSCMD and the IMS Transaction Execution Interface

Required manual customization steps

The following are required manual customization steps.
1. If applicable, define the AF/OPERATOR transaction code or codes to your installation’s IMS
Security Maintenance Utility to allow the AF/OPERATOR BMP to send IMS commands.
IMSBSGEN allows the AF/OPERATOR transaction to enter any IMS commands permitted by
IMS to be submitted from a BMP.
More information about the IMS Security Maintenance Utility can be found in IMS Utilities
Reference: System. Use the AGN= keyword for each entry in KSLBLTBL to define the
application group name for each IMS definition, if applicable.
2. If applicable, define the AF/OPERATOR transaction to your external security product.
3. Update the IMS SYSGEN on each IMS system where commands will be issued.
IMSBIGEN contains the APPLCTN and TRANSACT macro statements to be added to your
installation’s IMS SYSGEN to define the BMP and its transaction code to IMS. Do not specify
a PROCLIM= parameter on the TRANSACT statement.
More information on the IMS SYSGEN and its input macro statements can be found in your
IMS System Definition Reference manual.
4. You can implement the new AF/OPERATOR BMP definitions and any new security
definitions into your IMS online system without stopping and starting the system by using the
IMS Online Change Utility. You will issue /MODIFY PREPARE and then /MODIFY COMMIT
online change commands to switch to the updated definitions. More information can be
found in the IMS Utilities Reference&colon. System manual and in the IMS Operator’s
Reference.
5. Add the IMS RESLIB dataset to the AF/OPERATOR STEPLIB concatenation.

62 AF/OPERATOR Configuration and Customization Guide V340

Configuring AF/OPERATOR to Permit IMSCMD to Issue Transactions

Overview
Before you can use the IMSCMD function to issue non-interactive transactions, various
configuration steps must be performed.

Configuration requirements for using IMSCMD to issue transactions

These are the requirements for using IMSCMD to issue a transaction:
1. The transaction issued must be non-interactive.
2. Response from the transaction is limited to single-segment messages routed specifically to the
transaction code assigned to the BMP.
3. In your transaction, be sure to specify the correct return transaction code; otherwise you may
get status QH from DL/I.
4. You must generate this alternate modifiable PCB:
PCB TYPE=TP,MODIFY=YES,EXPRESS
Generate the alternate PCB in addition to these usual PSB statements:
PSBGEN PSBNAME=KOGIMPSB, + PSB name for IMSCMD
LANG=ASSEM, + Assembler language
IOASIZE=132 I/O area, at least 132 bytes

Optional Application and Feature Customization 63

JES3 Command and WTO Exits

Before you customize

The AF/OPERATOR JES3 Command and WTO exits use the JES3 user exit names IATUX18
and IATUX31. If your site has existing JES3 Command and WTO exits, back them up before
installing the new AF/OPERATOR exits. If you upgrade either AF/OPERATOR or JES3, these
exits must be reinstalled.

JES3 exits
If you are running JES3, consider the following:
n You only need to install these exits if your site has dedicated JES3 consoles.
n These exits are not required if you only have MCS consoles.
n If you have a combination of dedicated JES3 consoles and MCS consoles, you must
install these exits if you want the ability to suppress commands and messages on the
dedicated JES3 consoles.
Note: Installing these exits may create a condition in which the WTOs issued by JES3 create
a double match—one for JOBTYPE=JES3 and the other for JOBTYPE=STC.
n If you have JES3 Version 2.2 or below, you must install the JES3 interface in order to use
the JES3OPER command. (You would use JES3OPER to issue commands to JES3, for
example, JES3OPER ‘*I R’).
n If you have JES3 Version 2.2.1 or above, you do not need to use the JES3OPER
command. Instead, you can use the OPER command, for example, OPER ‘*I R’.
n If you keep your JES3 exit modules, the batch job renames your exit IATUX18/IATUX31
to USRXIT18/USRXIT31.
n Most MVS/XA releases of JES3 require the exits to be AMODE 31 compatible.
n These JES3 exits must be installed on every running system.
n The return code returned to JES3 is the highest code established by either the user exit or
the AF/OPERATOR exit.

64 AF/OPERATOR Configuration and Customization Guide V340

JES3 Command and WTO Exits

AF/OPERATOR exits
The AF/OPERATOR exits, KABJ3X18 and KABJ3X31, are used at the following exit points:

IATUX18 The exit point for commands. It is invoked prior to any

processing of a command issued by a JES3 console.
IATUX31 The exit point for WTOs. It is invoked before the message is
received from the JES3 console.

If your installation already uses exit routines for the IATUX18 and IATUX31 exit points,
perform one of the following actions:
n Replace your exits with AF/OPERATOR exits and develop AF/OPERATOR traps and
REXX programs to duplicate the functions of your exits.
n Use your existing JES3 exits along with AF/OPERATOR exits by installing the supplied
exit driver programs.
The AF/OPERATOR exits meet the JES3 re-entrant requirement. Therefore, when your user
exits are linked with AF/OPERATOR exits, they must be link-edited as re-entrant code.
Notes:
1. If your user exit suppresses or deletes a message or command, the
AF/OPERATOR exit (KABJ3Xnn) will not receive that message or command.
2. If your user exit alters message text, descriptor codes, or command text, the AF/OPERATOR
exit (KABJ3Xnn) will receive the altered data.

AOSIM alert facility

The JES3 interface uses the AOSIM alert facility, which reports events to the central
AF/OPERATOR task using cross-memory services. With AOSIM, subsystems, such as JES3,
that do not use the MVS console for event reporting can communicate with AF/OPERATOR.

Diagram of call sequence with only the Candle exit

The following diagram represents the call sequence after installation of either of the Candle
exits.

IATUXnn-----(calls)----AOSIM---
|
|
(uses)
|
|
XMS----(communicates with)----AF/OPERATOR

Optional Application and Feature Customization 65

JES3 Command and WTO Exits

Diagram of call sequence with your user exit

The following diagram represents the call sequence after installation of the Candle driver
(IATUXnn) which calls your user exit (USRXITnn) and then calls the Candle exit (KABJ3Xnn).

If your user exit (USRXITnn) suppresses or deletes a message or command, the

AF/OPERATOR exit (KABJ3Xnn) will not receive that message or command. If your user exit
(USRXITnn) alters message text, descriptor codes, or command text, KABJ3Xnn will receive
the altered data.
The return code returned to JES3 is the highest code established by either the user exit or the
AF/OPERATOR exit.

66 AF/OPERATOR Configuration and Customization Guide V340

JES3 Command and WTO Exits

JES3 command and WTO exits worksheet

Photocopy and fill out the following worksheet for each system that will use the
AF/OPERATOR JES3 Command and WTO exits.

JES3 load library No default

Specify the name of your JES3 load
library where the exits will be installed.
Disk volume No default
Specify the disk volume serial of your
JES3 load library.
Disk unit type No default
Specify the disk unit type of your JES3
load library.

Optional Application and Feature Customization 67

Logmode Table for VTAM-Connected Optional Features

Introduction
The logmode table is shared by the following AF/OPERATOR optional features:
n MSMF (Peer-to-Peer)
n OMEGAMON Interface
n OMEGAVIEW Interface
n Programmerless Open VTAM Interface
The logmode table must be assembled before you customize any of the above features. The
Customizer prompts for it in option 0 of the Install Optional Features menu.

Caution
Candle recommends that you use the default logmode table name, KABLMT. If you
want to change the table name, you must use the Customizer to do so to ensure that
the new name is propagated to the appropriate places throughout the product.

CICS Autoinstall terminals and POVI considerations

For CICS Autoinstall terminals and POVI, the following lists the supported logmode entry
names (where x is the 3278 model (2, 3, 4, or 5):
NSQ3270x - non-SNA, queriable
NS3278x - non-SNA, non-queriable
SQ3270x - SNA, queriable
S3278x - SNA, non-queriable
These entry names correspond directly to the logmodes in the KABLMT MODETAB. To
connect to a CICS AUTOINSTALL environment, you must provide the CICS region with
termtype entries that correspond to each KABLMT logmode that will be used. You cannot
override these logmodes because of the POVI playback/record facilities heavy dependency on
the logmode and session parameters.

Logmode table worksheet

Description Customizer Default Your Site

Logmode table name KABLMT
Specify the logon mode table name.
VTAMLIB SYS1.VTAMLIB
Specify the VTAM library dataset.

68 AF/OPERATOR Configuration and Customization Guide V340

MSMF (Peer-to-Peer)

MSMF (Peer-to-Peer) worksheet

Photocopy and fill out a worksheet for each address space that will use the AF/OPERATOR
Multi-System Management Facility.

Description Customizer Default Your Site

MSMF APPLID user-defined system
Specify the application name you will name and SUBSYS
use for Multi-System Management
Facility communication.
You can specify one MSMF APPLID per
address space.

Optional Application and Feature Customization 69

NetView Interface

Before you customize

The AF/OPERATOR NetView Interface uses the NetView user exit names DSIEX01,
DSIEX06, and DSIEX11. If your site has existing NetView exits, back them up before
installing the new AF/OPERATOR exits.

NetView Interface worksheet

Photocopy and fill out a worksheet for each system that will use the AF/OPERATOR NetView
Interface.

70 AF/OPERATOR Configuration and Customization Guide V340

OMEGAMON Interface

Virtual terminal interface module

The Programmerless Open VTAM Interface and the OMEGAMON Interface share a common
pool of virtual terminals, the AF/OPERATOR virtual terminals. The customization step to
define these terminals is the same for both. As part of this step, the Customizer tailors the
assembly source and batch job to build the Virtual Terminal Interface Module, AOVTPOOL.
This module is necessary for POVI and/or OMEGAMON Interface support. It contains the
sum of all the AF/OPERATOR virtual terminals for OMEGAMON and POVI defined to the
Customizer. The module will be installed as an SMP/E USERMOD in the AF/OPERATOR
load library.
Virtual terminal LUs are defined to VTAM. They are used for automation in place of physical
3270 terminals. In order to start sessions that use virtual terminal LUs, AF/OPERATOR
obtains the names of these LUs from AOVTPOOL. From the pool of virtual terminals
identified in the AOVTPOOL module, AF/OPERATOR selects an unused virtual terminal LU
for POVI or OMEGAMON when a logon executes.
If all the virtual terminals in the pool are in use, attempts to invoke the logon command result
in the message OBV220 SESSION CANNOT START - NO VIRTUAL TERMINALS
AVAILABLE. If this message is issued and no sessions have been inadvertently left active,
you must reassemble AOVTPOOL and link it to a virtual terminal count appropriate to the
needs of your site.
If you are customizing this application for multiple systems, ensure that a unique virtual
terminal prefix is defined for each system.
Note: If you are running only the OMEGAMON Interface or only POVI, but not both, a
unique panel is supplied for each interface for defining virtual terminals. If you are
running both interfaces, define the virtual terminals once only using panel
KOGIK069.

Optional Application and Feature Customization 71

OMEGAMON Interface

OMEGAMON Interface worksheet

Photocopy and fill out a worksheet for each system that will use the AF/OPERATOR
OMEGAMON Interface.

72 AF/OPERATOR Configuration and Customization Guide V340

OMEGAVIEW Interface

Virtual terminal interface module

The OMEGAVIEW Interface has its own pool of virtual terminals, the OMEGAVIEW Interface
virtual terminals. As part of this step, the Customizer tailors the assembly source and batch job
to build the OMEGAVIEW Interface Virtual Terminal Interface Module, AOVTPLU0. This
module is necessary for OMEGAVIEW Interface support. It contains the sum of all
AF/OPERATOR virtual terminals for OMEGAVIEW defined to the Customizer. The module
will be installed as an SMP/E USERMOD in the AF/OPERATOR load library.
Virtual terminal LUs are defined to VTAM. They are used for automation in place of physical
3270 terminals. In order to start sessions that use virtual terminal LUs, AF/OPERATOR
obtains the names of these LUs from AOVTPLU0. From the pool of virtual terminals
identified in the AOVTPLU0 module, AF/OPERATOR selects an unused virtual terminal LU
for OMEGAVIEW when a logon executes.
If all the virtual terminals in the pool are in use, attempts to invoke the logon command result
in the message OBV220 SESSION CANNOT START - NO VIRTUAL TERMINALS
AVAILABLE. If this message is issued and no sessions have been inadvertently left active,
you must reassemble AOVTPLU0 and link it to a virtual terminal count appropriate to the
needs of your site.
If you are customizing this application for multiple systems, ensure that a unique virtual
terminal prefix is defined for each system.

OMEGAVIEW Interface worksheet

Photocopy and fill out a worksheet for each system that will use the AF/OPERATOR
OMEGAVIEW Interface.

Description Customizer Default Your Site

Virtual terminal prefix VVTMmm
Specify the prefix to be used for mm = 00 to 99.
OMEGAVIEW Interface virtual terminal
definitions.
Virtual terminal count 20
Specify the number of OMEGAVIEW
Interface virtual terminals to enable.

Optional Application and Feature Customization 73

Programmerless Open VTAM Interface (POVI)

Before you customize

Before you begin Programmerless Open VTAM Interface (POVI) customization, decide how
many POVIs will be installed in your complex. Multiple systems or an entire complex can
share one POVI address space. Sometimes two are used, for example, a production POVI
and a test POVI. However, multiple POVIs can be installed on a single system. The
Customizer can configure up to 10 POVIs.

POVI network resources

The Customizer defines the various network resources that support POVI. The following table
directs you to the worksheets used to define these resources.

Resource Location
AF/OPERATOR virtual terminal LUs; also used for POVI: See page 77
OMEGAMON Interface support OMEGAMON: See page 71.
POVI management application LUs (playback POVI: See page 78
manager, recording manager, basic operator, and
CUA operator)
CT/Engine virtual terminal LUs POVI: See page 78
Logmode table used for AF/OPERATOR virtual Logmode: See page 68
terminals, CT/Engine virtual terminals, and other
VTAM connected optional features
VTAM 3270 applications accessible by POVI POVI: See page 79

Sequence of POVI customization

The worksheets in the following sections ask for the information you will need to to complete
POVI customization. There are nine steps for POVI customization; the first seven may require
worksheet preparation. The steps are performed in sequence.
1. Define Number of POVI Address Spaces
2. Define CT/Engine High Level Qualifier
3. Define POVI Security System
4. Allocate POVI Support Datasets
5. Define AF/OPERATOR Virtual Terminals
6. Define POVI Management Application and CT/Engine Virtual Terminals
7. Define Accessible VTAM Applications
8. Customize POVI Control Members
9. Additional POVI Security System Preparation

74 AF/OPERATOR Configuration and Customization Guide V340

Programmerless Open VTAM Interface (POVI)

POVI step 1 address space worksheet

Define the number of POVI address spaces in your complex.

Non-VSAM disk unit type Default value is

Specify the non-VSAM disk unit type. inherited from the
system definition.
Non-VSAM SMS storage class Default value is
Specify the non-VSAM SMS storage inherited from the
class. system definition.

Non-VSAM SMS management class Default value is

Specify the non-VSAM SMS inherited from the
management class. system definition.

VSAM disk volume serial Default value is

Specify the VSAM disk volume serial ID. inherited from the
system definition.
VSAM disk unit type Default value is
Specify the VSAM disk unit type. inherited from the
system definition.
VSAM SMS storage class Default value is
Specify the VSAM SMS storage class. inherited from the
system definition.
VSAM SMS management class Default value is
Specify the VSAM SMS management inherited from the
class. system definition.

Optional Application and Feature Customization 75

Programmerless Open VTAM Interface (POVI)

POVI step 2 CT/Engine worksheet

Define the CT/Engine high-level qualifier. CT/Engine is the Candle-supplied base component
on which POVI runs. It provides dialog management services to the POVI environment.

Description Customizer Default Your Site

High-level qualifier &thilev
Verify the CT/Engine Version 180
high-level qualifier. If no default value
displays, it is likely that CT/Engine
Version 180 was already installed at your
site by another Candle product. Specify
the CT/Engine Version 180 high-level
qualifier.

POVI step 3 security system worksheet

Specify the type of security system you will use.
If you select CA-TOP SECRET® or CA-ACF2® as your POVI security system, you can
optionally install one of the following authorization validation exits. The exit names are not
customizable.

KLVTSNEV CA-TOP SECRET exit

KLVA2NEV CA-ACF2 exit

76 AF/OPERATOR Configuration and Customization Guide V340

Programmerless Open VTAM Interface (POVI)

POVI step 4 support datasets worksheet

The Customizer allocates support datasets for each POVI that you define. You must perform
this step to generate the batch job that allocates the support datasets.

POVI step 5 AF/OPERATOR virtual terminals worksheet

Specify AF/OPERATOR virtual terminal definitions for each system.
Note: If you have already customized the OMEGAMON Interface, then you have already
completed this step and can proceed to the next worksheet.

Virtual terminal interface module

Optional Application and Feature Customization 77

Programmerless Open VTAM Interface (POVI)

identified in the AOVTPOOL module, AF/OPERATOR selects an unused virtual terminal LU

for POVI or OMEGAMON when a logon executes.
If all the virtual terminals in the pool are in use, attempts to invoke the logon command result
in the message OBV220 SESSION CANNOT START - NO VIRTUAL TERMINALS
AVAILABLE. If this message is issued and no sessions have been inadvertently left active,
you must reassemble AOVTPOOL and link it to a virtual terminal count appropriate to the
needs of your site.
If you are customizing this application for multiple systems, ensure that a unique virtual
terminal prefix is defined for each system.
Note: If you are running only the OMEGAMON Interface or only POVI, but not both, a
unique panel is supplied for each interface for defining virtual terminals. If you are
running both interfaces, define the virtual terminals once only using panel
KOGIK069.

POVI step 6 application and virtual terminal worksheet

Specify the POVI(n) management applications and CT/Engine virtual terminal definitions.
This step defines these applications and definitions to VTAM and CT/Engine.

78 AF/OPERATOR Configuration and Customization Guide V340

Programmerless Open VTAM Interface (POVI)

VIRT TERM COUNT 10

Specify the number of CT/Engine virtual
terminals to enable.
Note: POVI may be suffixed with a number (n), for example POVIn, where n is blank or 1–9. The
defaults are for POVI number 0 (n=blank). For POVI 1–9, all default VTAM application APPLIDs are
suffixed with the POVI number (n) in order to produce a unique default value for each POVI.

POVI step 7 VTAM entries worksheet

Define accessible VTAM entries. The entries you define will appear on the POVI Session
Selection Menu.
You may need to attach a separate piece of paper, with columns for Session ID, VTAM
APPLID, and Description, if you have many entries to define for your POVI main menu.

POVI step 8
No worksheet preparation is required for this step.
n Each POVI address space must have its own set of VSAM databases. The Customizer
generates members that identify the names of the NAM, table, and viewlog databases and
that identify the POVI security type.

Optional Application and Feature Customization 79

Programmerless Open VTAM Interface (POVI)

n The Customizer then generates the POVI startup procedure.

POVI step 9
No worksheet preparation is required for this step.
Follow the instructions in the Customizer to authorize users for POVI.

80 AF/OPERATOR Configuration and Customization Guide V340

TCP/IP Trusted HOSTNAME Table

In order to control who has access to your system through a TCP/IP server, you must define a
list of authorizd hostnames or IP addresses that can connect to a particular AF/OPERATOR.
This list is referred to as the trusted hostnames list. The trusted hostnames list is stored as a
member called HOSTNAME in the same PDS used for the startup parameters member. This
is the PDS referenced by the RKANPAR DD in the AF/OPERATOR startup procedure.

Defining the trusted HOSTNAME table in your TCP/IP network

The HOSTNAME table in your RKANPAR dataset can be created and maintained either
manually using the ISPF editor or through the AF/OPERATOR Customizer. In the
Customizer, you can reach the HOSTNAME dialog by selecting F.9 from the Primary
Customization Menu. This dialog permits you to enter new data and modify existing data
using ISPF table services.
If you would rather maintain the table manually via ISPF, you will find a description of the
required format in the AF/OPERATOR User’s Guide chapter titled “Understanding the
Communications Environment,” the section called “Configuration Requirements for
Establishing TCP/IP Connections.”

Optional Application and Feature Customization 81

Subsystem Logging Facility Support

Defining Backup Datasets for Journaling

The SLF journaling facility writes journal data directly to an MVS dataspace at the interval
you specify on the JOURNAL startup parameter. SLF journaling requires backup datasets.
These are VSAM linear datasets that can be defined as described below in Defining clusters.
You must also define the backup datasets to AF/OPERATOR as described in Defining backup
datasets in the startup JCL. (Note that the datasets must have two-digit suffixes.)

Defining clusters
SLF journaling requires backup datasets. They are VSAM linear datasets which can be
defined with IDCAMS as follows:
//DEFINE EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
DELETE hilev.RKOGSLF0 SCRATCH PURGE
DELETE hilev.RKOGSLF1 SCRATCH PURGE
DEFINE CLUSTER(NAME(‘hilev.RKOGSLF0’) -
SHR(1 3) -
CYL(pri sec) -
VOL(volser) -
LINEAR)
DEFINE CLUSTER(NAME(‘hilev.RKOGSLF1’) -
SHR(1 3) -
CYL(pri sec) -
VOL(volser) -
LINEAR)
The amount of space to allocate depends on the number and kind of traps you set and the
size of your system.

Defining backup datasets in the startup JCL

To use journaling you must define the backup datasets to AF/OPERATOR. Add the following
DD statements to your AF/OPERATOR startup JCL:
//RKOGSLF0 DD DISP=SHR,DSN=hilev.RKOGSLF0,DISP=SHR
//RKOGSLF1 DD DISP=SHR,DSN=hilev.RKOGSLF1,DISP=SHR
You only need to add these statements to the local SLF.

82 AF/OPERATOR Configuration and Customization Guide V340

Accessing and Exiting the Customizer

4
Introduction
The Customizer is accessed from the Candle Installation/Configuration Assistance Tool
(CICAT). You can run CICAT under ISPF option 6.
If you installed AF/OPERATOR using the batch installation method, you must still use the
CICAT to access the Customizer. “Accessing the Customizer after batch installation” on page
85 provides the procedure.

Chapter Contents
Accessing the Customizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Exiting the Customizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Accessing and Exiting the Customizer 83

Accessing the Customizer

Requirements for Access

This procedure assumes that
n AF/OPERATOR was installed as described in Installing Candle Systems on MVS.
n All available maintenance was applied.

Access procedure
To access the Customizer, perform the following steps.
1. Enter the TSO EXECUTE command
EX ‘shilev.INSTLIB’
2. Press Enter.
The CICAT Main Menu displays.
3. On the CICAT Main Menu, select option 5, Configure Products, and press Enter.
The Product Selection Menu displays.
4. On the Product Selection Menu, select option 2, Select Product to Configure.
5. From the displayed list, choose AF/OPERATOR.
6. Press Enter to display the AMS Primary Customization Menu.

Vnnn ------------------- !AMS PRIMARY CUSTOMIZATION MENU -------------------

OPTION ===>

Enter the selection number on the line above.

--- Last Selected---

_________Required Customization Time Date User
==> 0 Customization Considerations
1 Define Systems in Complex
2 Define Address Spaces for Each System
3 JES Customization
4 Define Address Space Environments

_________Optional Application/Feature Customization Time Date Userid

A !AMS Application Customization
F Install Optional Features
U Additional Utilities

_________Required Final Customization Time Date Userid

5 Generate Task List and Members for Startup

F1=Help F3=Exit F5=Reset F10=Complex_Overview F11=System_Overview

84 AF/OPERATOR Configuration and Customization Guide V340

Accessing the Customizer

Note: If you installed the product using the batch install procedure, see “Accessing the
Customizer after batch installation,” below, for the steps needed to access the
Customizer.
You are now ready to begin customization as described in “Customization Process” on page
23.

Accessing the Customizer after batch installation

The CICAT is required for configuration and customization of the product regardless of the
installation method. If you installed AF/OPERATOR using the batch install method, you must
perform the following steps in order to access the Customizer after performing steps 1—5 in
“Access procedure” on page 84.

Accessing and Exiting the Customizer 85

Accessing the Customizer

Step Action
1 Select Assist product installation from the Installation/Configuration Primary
Menu and press Enter.
Result: The Product Installation Menu appears.
2 Select Define installation parameters from the Product Installation Menu and
press Enter.
Result: The first Installation Parameters panel appears.
3 Complete the information requested on the first Installation Parameters panel by
doing the following:
a. Enter the standard jobcard that will be used for all of the batch jobs built by
the CICAT.
b. Enter the unit type and volume serial number information for the product
and maintenance tapes. (Do not enter a PSP tape volume serial number
here.)
c. Press Enter to continue to the next panel.
Result: The second Installation Parameters panel appears.
4 Complete the information requested on the second Installation Parameters panel by
doing the following:
a. Enter the installation parameters to define your SMP/E environment.
The CICAT is designed to install products into a shared CSI. Once the
SMP/E dataset information is entered, it applies to any product being
installed.
b. Press Enter to continue to the next panel.
Result: The third Installation Parameters panel appears.
5 Complete the information requested on the third Installation Parameters panel by
doing the following:
a. Verify the installation parameters that will be used to allocate and define
the product target and distribution libraries. The values were propagated
from the previous panel.
b. Change the information, if necessary, to meet your requirements.
c. Press Enter to continue to the next panel.
Result: The fourth Installation Parameters panel appears.
6 Complete the information requested on the fourth Installation Parameters panel by
doing the following:
a. Verify the installation parameters that will be used to allocate and define
the product-specific runtime datasets. The values were propagated from
the previous panels.
b. Change the information, if necessary, to meet your requirements.
c. Press Enter.
Result: The installation parameters are defined. The CICAT generates all the
necessary installation job streams using all of the definitions you have entered. The
Product Installation Menu is redisplayed after this process has completed.
7 Continue configuration by performing steps 3–6 of the procedure beginning on
page 84.

86 AF/OPERATOR Configuration and Customization Guide V340

Exiting the Customizer

Procedure
Press F3 from the Primary Customization Menu to exit the Customizer. You are returned to
the CICAT Installation/Configuration Primary Menu.

Accessing and Exiting the Customizer 87

Exiting the Customizer

88 AF/OPERATOR Configuration and Customization Guide V340

Manual Customization

5
Introduction
To complete your customization of AF/OPERATOR, you must perform a few steps manually,
both for the required components and for each optional feature you plan to use. The
information in this section includes instructions from the manual task list generated by step 5
of the Primary Customization Menu, Generate Task List and Members for Startup. Each
generated item described is identified by its default name and location. The list generated by
option 5 provides you with specific libraries and member names as defined within the
Customizer.
Note: Follow the procedure given on each system that runs AF/OPERATOR unless
specifically instructed otherwise.

Chapter Contents
Required Manual Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Verifying Required Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Optional Manual Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Enabling the Sysplex RSV pool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
CICS Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
IMS Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
JES3 Command and WTO Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Running AF/OPERATOR without JES3 after an IPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
VTAM Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
NetView Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
POVI and/or OMEGAMON Virtual Terminal Support . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
OMEGAVIEW Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Programmerless Open VTAM Interface (POVI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Logmode Table Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
TCP/IP Trusted HOSTNAME Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Reconfirming Required Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Manual Customization 89
Required Manual Customization

Required Manual Customization

Introduction
This section describes the steps you must perform to complete AF/OPERATOR customization.
They are:
n Support dataset allocation
n JES customization
n AF/OPERATOR startup procedure
n STEPLIB/LINKLIST
n APF authorization

Before you begin

See page 92 for instructions on using the $$OGINIT program to verify required
customization.

Support dataset allocation

Submit the jobs that allocate the AF/OPERATOR support datasets if you have not done so
already. Required support dataset JCL is in rhilev.@system.RKANSAM(OGSPDS##).

JES customization
Submit the job that builds the JES offset table if you have not done so already.
n The JES2 offset table JCL is in rhilev.@system.RKANSAM(J2TABJCL).
This submits an SMP/E job to apply a usermod to customize the JES2 table.
Alternatively, you can update the JES2 offset table without using SMP/E by using the
KOGJSJCL member in TKANSAM. This method is not recommended.
n The JES3 offset table JCL is in rhilev.@system.RKANSAM(J3TABJCL).
Batch job J3TABJCL also installs the JES3 WTO console exit.

AF/OPERATOR startup procedure

Copy the AF/OPERATOR startup procedure to SYS1.PROCLIB or to an appropriate user
PROCLIB dataset. You can find the startup procedure in rhilev.@system.RKANSAM.

STEPLIB/LINKLIST
If you have not specified the AF/OPERATOR load libraries in the STEPLIB DD statement,
make certain that they are included in the LINKLIST (SYS1.PARMLIB(LNKLSTcc)).

90 AF/OPERATOR Configuration and Customization Guide V340

Required Manual Customization

APF authorization
You must APF-authorize the AF/OPERATOR load libraries for each system on which
AF/OPERATOR will run. To do this, add the names of the following AF/OPERATOR libraries
and their disk volumes to the APF list named SYS1.PARMLIB(IEAAPFcc):
n thilev.TKANMOD
n thilev.TKANMODL
n thilev.TKANMODS
Note: If you have OMEGAMON for MVS, you can temporarily APF-authorize the
AF/OPERATOR load libraries using the OMEGAMON APFUA command.
If you choose to place the AF/OPERATOR libraries in the LINKLIST, verify that the linklist
dataset you have chosen is authorized either through the LNKAUTH=LNKLST parameter of
SYS1.PARMLIB(IEASYScc) or through explicit inclusion in SYS1.PARMLIB(IEAAPFcc).

Manual Customization 91
Verifying Required Customization

Verifying Required Customization

Overview
Use the REXX exec $$OGINIT to verify that required customization was completed
successfully. $$OGINIT resides in rhilev.RKANPAR. You can execute $$OGINIT either
during or after AF/OPERATOR startup and use it later to call other routines as you develop
them.
Note: Remember to specify $$OGINIT, if you have not already done so, when you generate
the task list and members for startup (after performing any customization and before verifying
customization). $$OGINIT does not reside in RKANCMD unless you specify it. See
“Generate task list and members for startup (step 5)” on page 29 for more information.
$$OGINIT process
$$OGINIT tests the following areas:
n command trap processing
n WAIT WTO processing
n WTO command
n global match variables
n system variables
n OPER with response (RESP)&mdash.LINE variables
n DO WHILE loop
n REXX functions
Note: The $$OGINIT program does not verify customization of the optional features.
Executing $$OGINIT
Execute the $$OGINIT program using one of the methods described below.
n To execute $$OGINIT as the first startup command file, issue the following command on
the system console:
S startup_proc,TYPE=’CMD(‘’’’EX $$OGINIT’’’’)’
n To execute the program after AF/OPERATOR startup, issue the following command on a
system console:
subsys EX $$OGINIT
where subsys is the subsystem name assigned by the SUBSYS value.
If you have already issued the KOGOCMDS REXX exec to enable unprefixed commands,
you can issue the command without the subsys prefix:
EX $$OGINIT
n To direct the command to a particular AF/OPERATOR address space (if you have
multiple address spaces on a system), prefix the command with the SUBSYS value:
subsys EX $$OGINIT

92 AF/OPERATOR Configuration and Customization Guide V340

Verifying Required Customization

Note: Make sure that there is a sufficient number of free subsystem consoles in your sysplex.
Each AF/OPERATOR address space has its own dedicated consoles. If several
AF/OPERATOR address spaces are active, you may run out of subsystem consoles.
See “SSCONNUM(number of subsystem consoles)” on page 157 for more
information.

Manual Customization 93
Optional Manual Customization

Optional Manual Customization

Introduction
To complete your customization of AF/OPERATOR’s optional features, you must perform a
few steps manually for each feature you plan to use. This section describes the manual tasks
required for each optional feature:

Feature Location
Sysplex RSV Pool See page 95
CICS Interface See page 98
IMS Interface See page 100
JES3 Commands and WTO Exits See page 101
MSMF (Peer-to-Peer) Connections See page 103
NetView Interface See page 104
AF/OPERATOR Virtual Terminal Interface See page 106
OMEGAVIEW Interface See page 107
Programmerless Open VTAM Interface (POVI) See page 108

Follow the procedure given on each system that will use the optional feature unless specifically
instructed otherwise.

Important
The information in this section includes instructions that form the manual task list
generated by step 5 of the Primary Customization Menu, Generate Task List and
Members for Startup. The list provides you with specific libraries and member
names as you defined them with the Customizer.

94 AF/OPERATOR Configuration and Customization Guide V340

Enabling the Sysplex RSV pool

Overview
Whether you need to enable AF/OPERATOR to manage resources across the Sysplex or need
to allow REXX shared variables to be shared between AF/OPERATOR or OG/MVS systems
across the Sysplex, it is necessary to define an XES cache data structure within the active
CFRM policy of the Sysplex coupling facility.
Use the Administrative Data Utility to define a structure and update the CFRM policy of the
Sysplex Coupling Facility. For information, see IBM’s Setting Up a Sysplex, GC28-1449.
This is an example of a control statement needed to add a structure:
STRUCTURE NAME(KOG_RSV_POOL)SIZE(5000)

Structure name
Be sure to check the CACHE startup parameter for rules regarding the naming of the XES
structure for use with AF/OPERATOR. See “AF/OPERATOR Startup Parameters” on page
133.

Size calculations for XES structure

The amount of space that is required for the allocation of the XES cache structure used by
AF/OPERATOR for the SYSPLEX REXX shared variable pool is dependent upon the size and
number of variables it must contain.
When an XES structure is defined to the coupling facilty, certain lower level attributes are not
specified. These are only supplied when the first connection is made and the structure is first
allocated. However, the actual structure size attribute must be specified on the definition. This
section will assist you in determining the size of the structure required for your automation.
Data is maintained within an XES cache structure in what are referred to as data entries. One
of the characteristics of the AF/OPERATOR structure attributes is that a data entry can be
subdivided into up to a maximum of 16 data elements.
The size of an AF/OPERATOR structure data element is, by default, 256 bytes. Therefore, the
default maximum data entry size is 4,096 bytes (4K). Since the data entry also contains the
REXX shared variable name and a few extra control bytes, the actual maximum data length is
slightly less than 4,096 bytes.
You can choose a maximum data entry size of 4, 8, 16, or 32K using the MAXSIZE
subparameter of the CACHE startup parameter.
Since the data element size is a sixteenth of the data entry size, using a larger MAXSIZE value
will directly affect the data element size. For example, using MAXSIZE(32) means you have a
data element size of 2,048 bytes. Thus, a structure of a certain size will contain fewer data
elements than one having a smaller specification for MAXSIZE.

Manual Customization 95
Enabling the Sysplex RSV pool

AF/OPERATOR structure sizes

For AF/OPERATOR, it is acceptable to use a 4K data entry size, which is the default MAXSIZE
on the CACHE startup parameter. Generally, 100 AF/OPERATOR “resources” should be
able to be contained within approximately 4500K of structure storage.
The following table should provide a guide as to how large a structure is required.

# of AF/OPERATOR Resources Structure Size

100 5,000K
200 9,000K
300 14,000K
400 18,000K
500 23,000K

General formula for structure size

The data entry size affects the structure size calculation. Choose the smallest size necessary to
contain your largest expected data. The data entry size is selected using the MAXSIZE
subparameter of the CACHE startup parameters.

Using a 4K MAXSIZE (the default)

If you specify a 4K MAXSIZE, the corresponding data element size would be 256 bytes. The
formula resembles the following:
structure size in K=(total number of data elements + 202)/2.133
To determine the structure size you require, you must:
n Calculate the average length of the variables you will store in the structure
n Calculate the number of data elements used to contain the average variable. Divide by
the data element size and round up to the next whole number.
n Calculate the total number of data elements to be used in the formula. Multiply by the
number of variables required to be stored in the structure.
Here is an example, assuming a 4K MAXSIZE:
n If the average length of variables is 100 bytes, then 100/256=0.39. Rounded up, this
yields 1 data element per variable.
n If you expect to have 10,000 variables, that means having 10,000 data elements.
n Therefore, you require a structure size of (10,000+202)/2.133=4,783K or approximately
5,000K.
Or:
n If the average length of variables is 4,000 bytes.

96 AF/OPERATOR Configuration and Customization Guide V340

Enabling the Sysplex RSV pool

n Then 4,000/256=15.62 rounded up, yielding 16 data elements per variable.

n If you expect to have 650 variables, that means having 650x16=10,400 data elements.
n Therefore, you require a structure size of (10,400+202)/2.133=4,781K or approximately
5,000K.

Using an 8K MAXSIZE
With an 8K MAXSIZE, the data element size is 512 bytes and the formula resembles:
structure size in K=(total number of data elements + 138)/1.414

Using an 16K MAXSIZE

With a 16K MAXSIZE, the data element size is 1,024 bytes and the formula resembles:
structure size in K=(total number of data elements + 104)/0.838

Using an 32K MAXSIZE

With an 32K MAXSIZE, the data element size is 2,048 bytes and the formula resembles:
structure size in K=(total number of data elements + 86)/0.461

Manual Customization 97
CICS Interface

CICS Interface

Introduction
The instructions for Version 3 or 4 of CICS differ from Version 2 of CICS. Use the method
appropriate for your system.

Procedure for CICS Version 2

Use the following procedure to prepare your system for the AF/OPERATOR CICS Interface.
1. Verify that you have read access to the CICS macro libraries and write access to the CICS
load libraries.
2. Define a PPT entry for the CICS Interface program as assembler and resident, either directly
or with RDO. If you want to update the PPT table directly, add the following entry before the
DFHPPT TYPE=FINAL macro and restart CICS.
DFHPPT TYPE=ENTRY,PROGRAM=KABCICS
If you use RDO, follow the steps below.
a. Define the CICS Interface program using the following command:
CEDA DEFINE PROGRAM(KABCICS) GROUP(cproduct) LANGUAGE(ASSEMBLE)
where cproduct is the name of your group list.
b. Install the program on your running system with this command:
CEDA INSTALL GROUP(cproduct)
c. Add group cproduct to your existing group list with this command:
CEDA ADD GROUP(cproduct)
3. Update the CICS startup PLT table so the exit will be enabled automatically at CICS startup
by placing the following entry before the DFHPLT TYPE=FINAL macro:
DFHPLT TYPE=ENTRY,PROGRAM=KABCICS
4. Define a PCT entry of any 4-character transaction ID (for example, KABC) and associate it
with program KABCICS. You can define the entry directly with a DFHPCT macro or with
RDO. If you want to update the PCT table directly, add the following entry before the
DFHPCT TYPE=FINAL macro and restart CICS.
DFHPCT TYPE=ENTRY,TRANSID=KABC,PROGRAM=KABCICS
If you use RDO, install the definition.
CEDA DEFINE INSTALL PROGRAM(KABCICS) GROUP(cproduct)

98 AF/OPERATOR Configuration and Customization Guide V340

CICS Interface

Procedure for CICS Version 3 or 4

Use the following procedure to prepare your system for the AF/OPERATOR CICS Interface.
1. Verify that you have read access to the CICS macro libraries and write access to the CICS
load libraries.
2. Define the CICS Interface program as assembler and resident with the following CEDA
command:
CEDA DEFINE PROGRAM(KABCICS3) GROUP(cproduct) LANGUAGE(ASSEMBLE)
where cproduct is the name of your group list.
If you prefer to define the program in batch mode with the DFHCSDUP utility, use the
following parameter card format:
DEFINE PROGRAM(KABCICS3) GROUP(cproduct) LANGUAGE(ASSEMBLE)
3. Install the program on your running system as follows:
CEDA INSTALL GROUP(cproduct)
4. Add the group cproduct to your existing group list:
CEDA ADD GROUP(cproduct)
If you prefer to add the group in batch mode with the DFHCSDUP utility, use the following
parameter card format:
ADD GROUP(cproduct)
5. Update the CICS startup PLT table so the exit will be enabled automatically at CICS startup
by placing the following entry after the DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM
macro:
DFHPLT TYPE=ENTRY,PROGRAM=KABCICS3
6. Define a PCT entry of any 4-character transaction ID (for example, KABC) and associate it
with program KABCICS3. You can define the entry directly with a DFHCSDUP utility or with
RDO.
7. Be sure that the transaction ID is defined with CMDSEC=NO, or modify your security system
to grant sufficient authority for transactions to issue EXEC CICS INQUIRE, ENABLE, and
DISABLE commands.
8. Install the definition to CICS.

Manual Customization 99
IMS Interface

IMS Interface

Procedure
Perform these steps to complete your customization of the IMS Interface:
1. Install the IMS exits if you have not done so already. You can find the exit installation jobs in
rhilev.@system.RKANSAM(IMSJCLc).
2. Once you have installed the exits, use your IMS stage 2 JCL to link the exits into your IMS
nucleus.

100 AF/OPERATOR Configuration and Customization Guide V340

JES3 Command and WTO Exits

Procedure
Perform these steps to complete your customization of the JES3 Command and WTO exits.
1. Install the JES3 WTO and command exits if you have not done so already. You can find the
exit installation jobs in rhilev.@system.RKANSAM(J3WCJCL).
Once installed, the exits will be activated at the next JES3 startup.
2. If the user exits are currently installed as part of LPA, perform an IPL using the CLPA option.

Manual Customization 101

Running AF/OPERATOR without JES3 after an IPL

Procedure
If you require AF/OPERATOR to be able to start JES3, you can use the following procedure:
1. Create a Started Task with all of the SYSOUT DD statements either specified as DUMMY or
referencing sequential datasets.
2. Update $$OGINIT to start JES3, VTAM, or any other Started Tasks, including a second
AF/OPERATOR Started Task. This latter Started Task terminates the first AF/OPERATOR and
continues with the IPL tasks.
3. Initiate the Started Task you have created using SUB=MSTR.

102 AF/OPERATOR Configuration and Customization Guide V340

VTAM Definitions

Procedure
To complete your customization of the MSMF (peer-to-peer facility), NetView, OMEGAMON,
OMEGAVIEW, and POVI, copy the generated VTAM members to SYS1.VTAMLST or to a
user VTAMLST dataset. The generated VTAM nodes are in rhilev.@system.RKANSAM
datasets.
If at least one of the above features is customized, there will be one major node member per
system. Each system has its own JCL library. The major node names are defined in option 1
of the Primary Customization Menu.

Manual Customization 103

NetView Interface

NetView preparation
Perform these steps to enable communication between AF/OPERATOR and NetView.
1. Install the NetView exits if you have not done so already. You will find the exit installation jobs
in rhilev.@system.RKANSAM(NETVJCL).
2. To set up NetView Interface communication on the NetView side, include the
AF/OPERATOR load library (thilev.TKANMOD) in both of the following procedures:
n NetView startup procedure
n NetView subsystem address space procedure
To determine where to place the AF/OPERATOR load library in the NetView startup
procedures, consider the following points:
n If you plan to install the AF/OPERATOR NetView exits (or have done so already), place
the library at the beginning of the STEPLIB concatenation.
n If you do not want to install the AF/OPERATOR NetView exits but do want to use the
NetView Interface AOCMD REXX function, place the library at the end of the STEPLIB
concatenation.
n Whether or not you install the AF/OPERATOR exits, place the load library in the same
place in each of the startup procedures.

AF/OPERATOR preparation
To initialize communication between NetView and AF/OPERATOR, make the NetView
module CNMNETV available to AF/OPERATOR by placing the module within one of the
following:
n LPA
n system LNKLST
n OG/MVS STEPLIB
Once AF/OPERATOR can access CNMNETV, you can automatically activate the
AF/OPERATOR side of the interface by issuing the AF/OPERATOR command NVISTART.
The NVISTART command may be issued at any time while AF/OPERATOR is running. You
can automate the AF/OPERATOR communication initialization process by including the
NVISTART command in your AF/OPERATOR startup command file.
Note: If NetView itself is unavailable when you issue NVISTART, AF/OPERATOR attempts to
initiate communication at regular intervals until NetView becomes available.

104 AF/OPERATOR Configuration and Customization Guide V340

NetView Interface

Enabling console communication

With the NetView Interface’s console communication function, you can use AF/OPERATOR
to issue commands to NetView using the MVS console and to initiate NetView activities
directly.
Console communication with NetView may already be implemented at your site. If this is the
case, all you need to do is install the AF/OPERATOR NetView exits. If not, you need to
modify the following NetView parameter library members to establish console
communication to NetView.
1. The NetView PARMLIB member DSIDMN defines the Subsystem Interface router. Locate the
entry in DSIDMN shown in example form below. Set the INIT parameter to Y.
TASK MOD=CNMCSSIR,TASKID=CNMCSSIR,PRI=5,INIT=Y
2. Define an operator ID for the automation task in the DSIOPF member of the NetView
PARMLIB as shown in the example entry below.
AUTO1 OPERATOR PASSWORD=????
PROFILEN profilename
AUTO2 OPERATOR PASSWORD=????
PROFILEN profilename
3. Define a profile to be used by automation operator IDs.
profilename PROFILE IC=LOGPROF1
AUTH MSGRECVR=NO,CTL=GLOBAL
4. Define AUTOTASK as a command (statement) in the DSICMD member. Refer to the
NetView manuals for the exact syntax, but the CONSOLE= parameter should specify the
desired console ID number as shown in the example below. You may also refer to member
CNME1035 in the NetView sample CLIST library.
AUTOTASK OPID=AUTO1,CONSOLE=console_id
You can now use AF/OPERATOR to initiate execution of NetView CLISTs and commands.
Use the AF/OPERATOR OPER statement from within an AF/OPERATOR REXX program as
follows:
OPER ‘%NetView clist/cmd’ CONSOLE(console_id)
where % is the NetView designator character and console_id is the same number that was
defined with the AUTOTASK command.

Manual Customization 105

POVI and/or OMEGAMON Virtual Terminal Support

Overview
The AF/OPERATOR Virtual Terminal Interface uses VTAM services to provide access between
AF/OPERATOR and
n POVI address spaces
n VTAM applications, such as OMEGAMON
POVI and OMEGAMON share the same virtual terminal pool, AOVTPOOL.

Customizing the virtual terminal interface

To finish customizing the virtual terminal interface, submit the batch job
rhilev.@system.RKANSAM(AOVTPOL@) if you have not done so already.
This completes your customization of the OMEGAMON Interface. See page 108 for the
manual tasks that complete POVI customization.

Prerequisites for enabling the OMEGAMON Interface

To enable the OMEGAMON Interface, make certain the following conditions are met:
n AF/OPERATOR and the OMEGAMON(s) are running.
n AF/OPERATOR virtual terminals for OMEGAMON and POVI are active.
n A VTAM session is established using the AF/OPERATOR LOGON command with the
OMEGAMON application type specified. (The LOGON command is described in detail
in the AF/OPERATOR Command Reference Manual) The application types for
supported OMEGAMONs are:

OMEGAMON Type
OMEGAMON for MVS OMMVS
OMEGAMON for CICS OMCCS
OMEGAMON II for DB2 OMDB2
OMEGAMON for IMS OMIMS
OMEGAVIEW Interface OMEGAVIEW Interface

106 AF/OPERATOR Configuration and Customization Guide V340

OMEGAVIEW Interface

AF/OPERATOR Virtual terminal support

If you have not done so already, install the virtual terminal interface module AOVTPLU0 for
OMEGAVIEW support. You can find the installation batch job in
rhilev.@system.RKANSAM(AOVTPLU@).

Prerequisites for enabling the OMEGAVIEW Interface

To enable the OMEGAVIEW interface, the following conditions must be met:
n Make sure that AF/OPERATOR and OMEGAVIEW are both running.
n Use the VTAM VARY ACTIVE command to make sure that
– the AF/OPERATOR virtual terminals for OMEGAVIEW support are active
– all OMEGAVIEW APPLIDs are active
n A VTAM session is established using the AF/OPERATOR LOGON command with the
application type OMVIEW specified. To do so:
1. Create a member in &thilev.RKANCMD that contains the following LOGON command
information:
/* REXX */
“LOGON OMVIEW APPLID(sdmappl) NAME(addressmv)”
where sdmappl is the VTAM application name defined in OMEGAVIEW and
addressmv is the user-defined name that will be used for subsequent calls.
2. Execute the LOGON command in one of the following ways:
– From a console, issue:
O340 EX LOGONMV
or
F omcgate,EX LOGONMV
where O340 is the subsystem name used to establish the OMEGAVIEW connection in
this example. The AF/OPERATOR default startup procedure name is OMCGATE.
– Within a REXX exec:
CALL logonmv
where logonmv is your site’s name for the REXX exec.
n To alert AF/OPERATOR when an OMEGAVIEW status change has occurred, the
AF/OPERATOR AOSIM facility must be made available to OMEGAVIEW. To do this,
include the AF/OPERATOR load library in the STEPLIB concatenation of the
OMEGAVIEW startup procedure.

Manual Customization 107

Programmerless Open VTAM Interface (POVI)

Requirements
Before you complete customization of POVI, be sure you have taken each of these steps in
the Customizer:
1. Define the Number of POVI Address Spaces
Each system you enter for POVI should match a system already entered during customization.
The Customizer automatically assigns a number between 0 and 9 to each POVI address
space.
2. Define CT/Engine High-Level Qualifier
The CT/Engine libraries are required for customization of the POVI startup procedure and the
POVI security system exit (if the security system is ACF2 or TOP SECRET). If these libraries
were installed during AF/OPERATOR installation, the Customizer displays their high-level
qualifier for verification. Otherwise, you need to specify the high-level qualifier.
3. Define POVI Security System
Specify the security system to be used by POVI.
Follow the Customizer’s instructions for completing customization of the security system you
selected.
4. Allocate POVI Support Datasets
The Customizer generates a batch job to allocate the 3 required POVI support datasets. You
can review the JCL and submit it.
5. Define AF/OPERATOR Virtual Terminals
If you already customized the OMEGAMON interface, you can skip this step. Otherwise,
follow the instructions in the Customizer to generate the
n AF/OPERATOR virtual terminals
n batch job to install the virtual terminal module AOVTPOOL
To finish customizing the virtual terminal interface, submit the batch job
rhilev.@system.RKANSAM(AOVTPOL@).
6. Define POVI Management Application and CT/Engine Virtual Terminals
This step generates 3 members:
n the VTAM definition that contains the POVI APPLIDs
n the POVI virtual terminal definitions (member KOGVTERM)
n the POVI initialization parameters (member KOGPSTRT)
7. Define Accessible VTAM Applications
Specify all VTAM 3270 applications that you want POVI to be able to access.
8. Customize POVI Control Members This step generates
a. control members KOGSYSIN, KLVINNAM, KLVINTB, and KLVINVLG
b. the POVI startup procedure
9. Additional POVI Security System Preparation
Follow the instructions in the Customizer to specify users to be allowed access to POVI.
Recustomizing POVI: If, after initialization, you want to redefine VTAM applications,
access the Customizer and perform steps 7 and 8 above.

108 AF/OPERATOR Configuration and Customization Guide V340

Programmerless Open VTAM Interface (POVI)

Starting POVI procedure

At this point, you need to perform one additional procedure to complete POVI customization:
1. Use the VTAM VARY ACTIVE command to make sure that
n both the AF/OPERATOR virtual terminals and the CT/Engine virtual terminals are active
n all POVI APPLIDs are active
2. Make sure that AF/OPERATOR is running
3. Execute the CT/Engine started task for POVI (S poviproc)
4. After the V180 ready appears, issue the following command from the system console:
F poviproc,KOGDECL
5. Define each TSO user ID that you want to have access to POVI by issuing the following
command:
F poviproc,NAM SET userid PASSWORD=password

Setting POVI ADMIN Authority

To set POVI ADMIN authority, isssue this command from the system console:
F POVI, NAM SET userid ADMIN:Y

Stopping POVI Procedure

To stop POVI’s CT/Engine started task, issue the MVS STOP (P) command as follows:
P poviproc
When you have completed the above procedure, AF/OPERATOR displays a message
confirming your shutdown request.
Although not recommended, you can bypass this confirmation message by modifying the
RKOGPARM dataset member KOGSYSIN and adding CONFIRM(0) as an option. The
CONFIRM(n) option prevents accidental shutdowns by requiring you to confirm the
shutdown command by entering it a second time within the specified number of seconds.
When set to zero, confirmation is not required. For more information about the CONFIRM(n)
command, see the CT/Engine Customization Guide.

Manual Customization 109

Logmode Table Name

Procedure
Follow the procedure below to complete customization of the logmode table name.
1. Submit the logmode table job, if you have not done so already. You can find the batch job in
rhilev.@system.RKANSAM(MODETABL).
2. Copy load module thilev.TKANMOD(KABLMT) to SYS1.VTAMLIB or to an appropriate
VTAMLIB dataset.
KABLMT is the default value; however, the value is user-definable. SYS1.VTAMLIB is the
default load library; however, this value is also user-definable.

110 AF/OPERATOR Configuration and Customization Guide V340

TCP/IP Trusted HOSTNAME Table

If you use TCP/IP to communicate with AF/OPERATOR, you must define the TCP/IP hosts
with which you will communicate. You may do this using the ISPF editor. The HOSTNAME
table is located in the dataset used with the RKANPAR DD name.
You will find a description of the required format in the AF/OPERATOR User’s Guide chapter
titled “Understanding the Communications Environment,” the section called “Configuration
Requirements for Establishing TCP/IP Connections.”

Manual Customization 111

Reconfirming Required Customization

Description
At this point, you may want to rerun the command file $$OGINIT to verify that you did not
inadvertently change any of the required customization parameters.
See “Verifying Required Customization” on page 92 for information on $$OGINIT.

112 AF/OPERATOR Configuration and Customization Guide V340

Reviewing Your Progress

6
Introduction
The Customizer provides 2 levels of status displays to help you track the progress of your
AF/OPERATOR customization:
n The Complex Overview panel shows the overall customization status of the first 15
systems in your complex.
n System Overview panels show detailed customization status for any system in your
complex.

Chapter Contents
Complex Overview Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
System Overview Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Reviewing Your Progress 113

Complex Overview Panel

Accessing the Complex Overview Panel

The Complex Overview Panel is accessible from function keys on the Primary Customization
Menu (the main menu), the Install Optional Features menu, and the Programmerless Open
VTAM Interface menu.

F10 Displays the Complex Overview panel

You can view the panel at any time during the customization process when this function key is
displayed.

The panel
The Complex Overview panel summarizes in a scrollable screen the customization status of
the major components for the first systems you have defined for your complex. By viewing
this panel, you can determine quickly how far along you are in the customization process.

Vnnn ------------------------ COMPLEX OVERVIEW ----------------------------------

COMMAND ===>

| - C O M P O N E N T S - |- APPLICATIONS -
_# _SYSTEM | MSMF POVI JES CICS IMS NETV OMEG MVI | OSM AFOP
1 MYSY | NO NO JES2 3 NO NO NO NO | -- --
2 SYSA | YES YES JES2 2 YES YES YES YES | -- --
3 SYSB | YES YES JES3 4 YES YES YES YES | -- --
4 SYSC | NO NO NO -- NO YES NO NO | -- --
5 ---- | -- -- -- -- -- -- -- -- | -- --
6 ---- | -- -- -- -- -- -- -- -- | -- --
7 ---- | -- -- -- -- -- -- -- -- | -- --
8 ---- | -- -- -- -- -- -- -- -- | -- --
9 ---- | -- -- -- -- -- -- -- -- | -- --
10 ---- | -- -- -- -- -- -- -- -- | -- --

-REXX Alternate Library->YES REXXLIB->YES SAMPLB->YES AUTOLIB->YES

AO/MVS Version: 340
OSM/MVS Version: N/A
AF/OPERATOR FOR MVS Version: 340

-- -Undefined NO - Req.,not enabled NO - Opt.,not enabled YES - enabled

F1=Help F3=End **=Up F8=Down

114 AF/OPERATOR Configuration and Customization Guide V340

Complex Overview Panel

Field descriptions
The Complex Overview panel contains these fields.

Field Description
SYSTEM Displays the system whose customization status appears in the remaining fields
of the row.
MSMF Displays customization status for Multi-System Management Facility
(peer-to-peer) Connections (option 4 on the Install Optional Features menu).
POVI Displays customization status for the Programmerless Open VTAM Interface
(option 8 on the Install Optional Features menu).
JES Displays JES version (JES2 or JES3), if customized (option 3 on the Primary
Customization Menu).
CICS Displays version (2, 3, or 4) for the CICS Interface, if customized (option 1 on
the Install Optional Features menu).
IMS Displays customization status for the IMS Interface (option 2 on the Install
Optional Features menu).
NETV Displays customization status for the NetView Interface (option 5 on the Install
Optional Features menu).
OMEG Displays customization status for the OMEGAMON Interface (option 6 on the
Install Optional Features menu).
MVI Displays customization status for the OMEGAVIEW Interface (option 7 on the
Install Optional Features menu).
OSM Displays installation status for the OMEGACENTER Status Manager.
AFOP Displays customization status for the AF/OPERATOR user interface.

Status definitions
The customization status for each component can be any of the following:

Green (YES) You have generated the supported code to customize this component, but may
not have submitted the job or completed all required manual steps.
Blue (--) You have not installed or defined this component for customization.
Red (NO) You have not generated supported code to customize this component, and it
requires customization.
Yellow (NO) You have not generated supported code to customize this component, but
customization is optional.

Reviewing Your Progress 115

Complex Overview Panel

Displaying the Complex Overview Panel

To display the Complex Overview panel:
1. If you are not currently at one of the following menus, press F3 until you are.
n Primary Customization Menu
n Install Optional Features menu
n Programmerless Open VTAM Interface menu
2. Press F10 to display the Complex Overview panel.
Note: The status lights on this panel show only that you have performed that particular
customization step and not that you have submitted the job or have completed any
manual steps required afterwards.
3. When you have finished viewing the panel, press F3 to return to the menu.

116 AF/OPERATOR Configuration and Customization Guide V340

System Overview Display

Accessing the System Overview display

The System Overview display is accessible from a function key on the Primary Customization
Menu (the main menu), the Install Optional Features menu, and the Programmerless Open
VTAM Interface menu.

F11 Displays System Overview panels

You can view the panel at any time during the customization process when this function key is
displayed.
The System Overview display consists of 3 panels that show detailed customization status for
the system you select. By viewing these panels, you can see the
n status of customization steps
n member names
n location of output members

Displaying the System Overview Panels

To display the System Overview panels for a particular system:
1. If you are not currently at one of the following menus, press F3 until you are.
n Primary Customization Menu
n Install Optional Features menu
n Programmerless Open VTAM Interface menu
2. Press F11.
If you have defined more than one system to customize, the Customizer displays the
Select System to Display panel.
3. Select the system you want to display by moving the cursor to the left of the system, typing S,
and pressing Enter.
The Customizer displays the first System Overview panel.

Reviewing Your Progress 117

System Overview Display

System Overview Panel 1

The first System Overview panel is shown in this example.

Vnnn ---------------- SYSTEM OVERVIEW (SYS1-1A) -------------------------------

COMMAND ===> More +

The following customization steps have been completed with applicable options:

PRODUCT COMPONENT DONE NAME MISCELLANEOUS INFORMATION________

|STARTED TASK PROC | YES | STC1A | AS#:1A,DSN=ABCD.EFGH.V150.SYS1.RKANSAM
|JES OFFSET TABLE | NO | KOGJ2TAB | ==>JES2/JES3 offset table not assembled
|AF/OPER COMPONENT | NO | N/A |
|CHECKPOINTING | NO | N/A | Checkpoint reload options:(NONE,NOLIST)
|STARTUP PARAMETERS | YES | OGPARM1A | ABCD.EFGH.V150.RKANCMD
|ALLOCATE DATASETS | NO | N/A | CKPT=N,DUMP=N,LOG01=N,LOG02=N
|DASD MESSAGE LOG | NO | N/A |
|RELATIVE ORDER | YES | RO=0 | Prefix commands to this A.S. by SUBSYS
|LINKID | YES | SYS1O120 |
|SUBSYS | YES | O120 |
|MSMF DEFINITIONS | NO | N/A |
|VTAM DEFINITIONS | NO | SYS1NODE | Prefix/count=
|EXITS | NO | NV,IM,J3 | NV(1/6/11):N/N/N,IMS:N,JES3(18/31):N/N
| | YES | CICS | Version: 3

-- =Undefined NO =Req.,not enabled NO =Opt.,not enabled YES =Enabled

F1=Help F3=End **=Bkwd F8=Fwd

This displays data for address space ID 1A defined on system SYS1.

Field descriptions

Field Description
Product Component
Identifies the system component whose customization status appears in the
remaining fields of the row. Components include:

118 AF/OPERATOR Configuration and Customization Guide V340

System Overview Display

n Started Task PROC (option 2 on the Primary Customization Menu)

n JES2 Offset Table (option 3 on the Primary Customization Menu)
n AF/OPERATOR user interface Component (option A.2 on the Primary
Customization Menu)
n Checkpointing (option 4 on the Primary Customization Menu)
n Startup Parameters (option 4 on the Primary Customization Menu)
n Allocate Datasets (option 4 on the Primary Customization Menu)
n DASD Message Log (option 4 on the Primary Customization Menu)
n Relative Order (option 4 on the Primary Customization Menu)
n LINKID (option 4 on the Primary Customization Menu)
n SUBSYS (option 4 on the Primary Customization Menu)
n MSMF Definitions (option 4 on the Install Optional Features menu)
n VTAM Definitions (option 0 on the Install Optional Features menu)
n EXITS (options 2, 3, and 5 on the Install Optional Features Menu)
Done Displays the customization status for each component, which can be any of
the following:
n Green (YES) means you have generated the supporting code to
customize this component but may have not yet submitted the job or
completed all required manual steps.
n Blue (--) means you have not installed or defined this component for
customization.
n Red (NO) means you have not generated supporting code to
customize this component, and it requires customization.
n Yellow (NO) means you have not generated supporting code to
customize this component, but customization is optional.
Member Name n Displays the name of the member associated with the customization of
this component.
Miscellaneous Information
n Displays significant information related to the customization of this
component.

Reviewing Your Progress 119

System Overview Display

System Overview Panel 2 (POVI panel 1)

The second System Overview panel shows POVI customization status.

Vnnn --------------------- SYSTEM OVERVIEW (SYS1) ----------------------------

COMMAND ===> More -+

The following customization steps have been completed with applicable options:
- POVI DISPLAY 1 of 2
MAJOR NODE POVI PLAYBACK RECORD OPER
PRODUCT COMPONENT DONE NAME SECURITY APPL APPL APPL
|POVI - PRIMARY | YES | SYS1NODE | ACF2 | OVIAO | OVIUSER | OVIOPER
|POVI - SECONDARY 1 | -- | | | | |
|POVI - SECONDARY 2 | NO | | ACF2 | | |
|POVI - SECONDARY 3 | -- | | | | |
|POVI - SECONDARY 4 | -- | | | | |
|POVI - SECONDARY 5 | -- | | | | |
|POVI - SECONDARY 6 | -- | | | | |
|POVI - SECONDARY 7 | -- | | | | |
|POVI - SECONDARY 8 | -- | | | | |
|POVI - SECONDARY 9 | -- | | | | |

-- =Undefined NO =Req.,not enabled NO =Opt.,not enabled YES =Enabled

F1=Help F3=End F7=Bkwd F8=Fwd

120 AF/OPERATOR Configuration and Customization Guide V340

System Overview Display

Field definitions

Field Description
Product Component
Identifies the POVI address space (Primary 0, Secondary 1 through 9) whose
customization status appears in the remaining fields of the row.
Done Displays the customization status for each POVI address space, which can be
any of the following:
n Green (YES) means you have generated the supported code to customize
this POVI but may have not yet submitted the job or completed all
required manual steps.
n Blue (--) means you have not installed or defined this POVI for
customization.
n Red (NO) means you have not yet generated supported code to
customize this POVI, and it requires customization.
n Yellow (NO) means you have not generated supported code to customize
this POVI, but customization is optional.
Major Node Name Displays the name of the member containing the CT/Engine virtual terminal
definitions for this POVI address space (option 1 on the Primary
Customization Menu). You must eventually copy this member to the
appropriate SYS1.VTAMLST library.
POVI Security Displays the type of security (RACF, ACF2, TOP, or NAM) you have selected
for this POVI address space (option 3 on the POVI customization menu). This
must be the same for all POVI’s.
Playback Appl Displays the VTAM application ID (APPLID) used by AF/OPERATOR (using
the AF/OPERATOR LOGON command) to playback previously recorded
scripts (option 6 on the POVI customization menu).
Record Appl Displays the VTAM APPLID of the user interface for POVI CT/Engine
recording manager sessions and for automating VTAM 3270 applications in
general (option 6 on the POVI customization menu).
Oper Appl Displays the VTAM APPLID of the CT/Engine interface used by authorized
personnel to enter CT/Engine commands or diagnose POVI problems (option
6 on the POVI customization menu).

Reviewing Your Progress 121

System Overview Display

System Overview Panel 3 (POVI panel 2)

The third System Overview panel, like the second, displays POVI customization status.

Vnnn --------------------- SYSTEM OVERVIEW (SYS1) -----------------------------

COMMAND ===> More -

The following customization steps have been completed with applicable options:
- POVI DISPLAY 2 of 2
CUA VTAM LU VTAM LU STARTED
PRODUCT COMPONENT DONE APPL PREFIX COUNT TASK NAME MISC FLAGS
|POVI - PRIMARY | YES | OVICUA | AOOVI | 10 | POVIPRC0 | 1-Y,2-Y,3-Y
|POVI - SECONDARY 1 | -- | | | | |
|POVI - SECONDARY 2 | NO | | | | | 1-N,2-N,3-N
|POVI - SECONDARY 3 | -- | | | | |
|POVI - SECONDARY 4 | -- | | | | |
|POVI - SECONDARY 5 | -- | | | | |
|POVI - SECONDARY 6 | -- | | | | |
|POVI - SECONDARY 7 | -- | | | | |
|POVI - SECONDARY 8 | -- | | | | |
|POVI - SECONDARY 9 | -- | | | | |

Note: Flags= 1 - Control members created

2 - Logon applications defined
3 - Supporting datasets defined
-- =Undefined NO =Req.,not enabled NO =Opt.,not enabled YES =Enabled

F1=Help F3=End F7=Bkwd **=Fwd

122 AF/OPERATOR Configuration and Customization Guide V340

System Overview Display

Field descriptions

Field Description
CUA Appl Displays the VTAM APPLID of the CUA interface used by authorized
personnel to enter CT/Engine commands or diagnose POVI problems (option
6 on the POVI customization menu).
VTAM LU Prefix Displays the prefix for the CT/Engine virtual terminal IDs that AF/OPERATOR
uses to establish virtual sessions between CT/Engine and the host 3270
applications (option 6 on the POVI customization menu).
VTAM LU Count Displays the number of virtual terminals to define for this POVI address space
(option 6 on the POVI customization menu). The Customizer defines as
many virtual terminal names as requested by appending a unique number to
the CT/Engine virtual terminal prefix.
Started Task Name Displays the name of POVI startup procedure for this POVI address space
(option 1 on the POVI customization menu). You must copy this member to
the appropriate SYS1.PROCLIB library.
Misc Flags Displays flag numbers 1 through 3 with the suffix Y (Yes) or N (No) to
indicate the following:
n 1:Y/N specifies whether or not you have created control members
(KOGSYSIN, KLVINNAM, KLVINTB, KLVINVLG, and the POVI startup
proc) for this POVI address space (option 8 on the POVI customization
menu).
n 2:Y/N specifies whether or not you have defined logon applications
(accessible VTAM applications) for the POVI environment (option 7 on
the POVI customization menu).
n 3:Y/N specifies whether or not you have allocated support databases
(NAM, TABLEDB, VIEWLOG, POVI USER PARMLIB) for this POVI
address space (option 4 on the POVI customization menu). Yes indicates
that the datasets exist.

Note: The status lights on the System Overview panels show only that you have performed
that particular customization step, not that you have submitted the job or have
completed any manual steps required afterwards.
4. Press F8 to move forward through the System Review panels, F7 to move backward.
5. When you have finished viewing the panels, press F3 to return to the menu.

Reviewing Your Progress 123

System Overview Display

124 AF/OPERATOR Configuration and Customization Guide V340

Starting and Stopping AF/OPERATOR

7
Introduction
This chapter describes starting and stopping AF/OPERATOR. To successfully start
AF/OPERATOR, all required automated and manual customization steps must already be
completed.

Chapter Contents
Starting AF/OPERATOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Stopping AF/OPERATOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Starting and Stopping AF/OPERATOR 125

Starting AF/OPERATOR

Introduction
AF/OPERATOR startup procedures are established during customization. These options are
contained in a PDS member referenced by the startup procedure. The default name of the
parameter member is OGPRMc##, where ## is the address space ID.

Standard start procedure

You can start AF/OPERATOR by issuing the MVS START command from any operator’s
console:
START OMCGATE
This command starts AF/OPERATOR using the default startup procedure name OMCGATE.
If you used a different procedure name during the customization of AF/OPERATOR, use the
appropriate name.
Note: The first time you start AF/OPERATOR you may receive message AOP0744, which
reads:
WRONG LRECL/BLKSIZE ON RKOGLHnn - OK TO MODIFY (Y OR N)?
Respond Y to allow AF/OPERATOR to override the LRECL/BLKSIZE of the OGLOGnn file.
Note: For whatever name you choose for the AF/OPERATOR started tasks, the priority
assigned to that task must be as high as that for your JES system.

Alternate start procedures

If necessary, you can create additional startup procedures with varying startup parameters.
For example, you can have the option of restoring TOD traps at startup and not restoring user
variables (or the reverse).
Create the following two members to contain alternate startup options:

RESTODS Member used to restore TOD traps, but not previously

checkpointed user variables. It must contain the parameter
RELOAD(TODS).
RESVARS Member used to restore previously checkpointed user
variables, but not TOD traps. It must contain the parameter
RELOAD(VARS).

You can use the following start commands to override the default startup parameter list.
START omcgate,RKANPAR=RESTODS
START omcgate,RKANPAR=RESVARS
An alternate method of overriding the default startup parameters is to specify parameters on
the START command. The format is:
START omcgate,TYPE=’parm1,parm2,...,parmn’

126 AF/OPERATOR Configuration and Customization Guide V340

Starting AF/OPERATOR

Here is an example for a system with a 1-character system ID of A:

START omcgate,TYPE=’RELOAD(TODS,LIST),CID(1)’
Once AF/OPERATOR is running, you may want to issue the AF command from the console
in order to display the current operating mode and the options in effect. See the
AF/OPERATOR Command Referenece Manual for a complete description of the AF
command.

Initial command
One of the parameters specified while customizing AF/OPERATOR is COMMAND (CMD).
COMMAND defines the name of the first command executed when AF/OPERATOR starts. By
default, this is ‘EX $$OGINIT’. The sample $$OGINIT file provided with AF/OPERATOR
performs customization verification tests. Your initial file can contain commands to vary active
the major node and activate the OMEGAMON virtual sessions, the NetView Interface, the
Programmerless Open VTAM Interface, and the peer-to-peer connections.

Cold starting a new version of AF/OPERATOR

Normally, you will want to start a new version of AF/OPERATOR with the RELOAD(NONE)
parameter. This option starts AF/OPERATOR without using previous checkpointing
information by reformatting the checkpoint dataset.

Error messages
If you experience problems starting AF/OPERATOR and have verified that you have met
VTAM requirements, check the error messages in the RKOGLOGM. If you cannot resolve the
problem, produce copies of the AF/OPERATOR message log and the RKANPAR member,
and contact Candle Support Services. Candle telephone numbers are listed in the front
matter of this document.
If you need to provide a dump to Candle Support Services, produce an unformatted dump in
machine readable format. Copy the dump to tape and accompany it with the JCL used to
create it.

Starting and Stopping AF/OPERATOR 127

Stopping AF/OPERATOR

Procedure
To stop AF/OPERATOR and allow current matches to complete, enter the AF STOP
command:
O340 AF STOP
This message appears:
!AOP0000 AF/OPERATOR V320 COPYRIGHT 20nn CANDLE CORP.
!AOP0999 taskname AF/OPERATOR ENDED
!AOP0004 taskname AF/OPERATOR MESSAGE LOG STOPPED
Do not use the AF STOP product control command unless you want to stop AF/OPERATOR
entirely.
To provide downwards compatibility with previous versions of AF/OPERATOR, the AO STOP
command functions as a command synonym for the AF STOP command.

Technical considerations
n If you want AF/OPERATOR to remain active but to take no action when traps are
triggered, put AF/OPERATOR in warn mode. See the AF/OPERATOR Command
Reference Manual for information on the AF WARN command.
n If you want to prevent AF/OPERATOR from trapping particular events, use the TRAP
DISABLE command to disable those specific traps.

128 AF/OPERATOR Configuration and Customization Guide V340

Customizing the AF/OPERATOR

8 User Interface

Introduction
This chapter will guide you through customization of the AF/OPERATOR user interface. Both
AF/OPERATOR and OMEGACENTER must be installed prior to performing the
customization tasks.

Important
Make sure you have already customized the required components of
AF/OPERATOR before you begin to customize the AF/OPERATOR user interface. If
you have not yet customized AF/OPERATOR, see “About the Customizer” on page
17 for instructions.

Chapter Contents
Customizing the Interface Using the Customizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Verifying the User Interface Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Customizing the AF/OPERATOR User Interface 129

Customizing the Interface Using the Customizer

Overview
To customize the AF/OPERATOR user interface, you will use the CICAT to perform four basic
steps:
1. Generate the AF/OPERATOR user interface logon program.
2. Populate the AF/OPERATOR user interface runtime table library.
3. Update the AF/OPERATOR user interface runtime ISPF tables.
4. Install the IBM Alternate Library for compiled REXX, if necessary.

Procedure
Follow the steps below to customize AF/OPERATOR.‘

Step Action
1 On the Product Selection Menu, select AF/OPERATOR by typing S in the
entry field. Press Enter.
Result: The Primary Customization Menu appears.
2 Make sure you have already customized the required parts of
AF/OPERATOR before you continue.
1. To find out whether AF/OPERATOR has already been customized, press
F11 from the Primary Customization Menu.
Result: The System Overview panel lists the systems on which
AF/OPERATOR has been installed.
2. Select a system by typing S in the entry field. Press Enter.
Result: A second System Overview panel shows exactly which
AF/OPERATOR components have already been customized on the
system you selected. Each component is identified as either required or
optional.
3. If any required components of AF/OPERATOR have not been
customized, Candle recommends that you finish customizing them before
you customize the AF/OPERATOR user interface. See “About the
Customizer” on page 17 for instructions.
If AF/OPERATOR has already been customized, go on to the next step.
3 From the Primary Customization Menu, select AMS Applications
Customization by typing A in the Option field. Press Enter.
Result:The Applications Customization panel appears.
4 Select AF/OPERATOR for MVS by typing 2 in the Option field. Press
Enter.
Result: The AF/OPERATOR for MVS Customization Menu appears.

130 AF/OPERATOR Configuration and Customization Guide V340

Customizing the Interface Using the Customizer

Step Action
5 Select Generate AF/OPERATOR for MVS User Interface Logon
Program by typing 1 in the Option field. Press Enter.
Result: The Customizer displays the name of the default output dataset.
This is the dataset where the AF/OPERATOR user interface logon program
will be stored. You can accept or override the default.
Tip: The output dataset must already be allocated and must be fixed block
with a record length of 80. The dataset must also be concatenated to the
SYSPROC ddname for any TSO user authorized to log onto the
AF/OPERATOR user interface.
6 To accept the default dataset name, press Enter. To change the dataset name,
type a new name and press Enter.
Result: The Customizer generates the REXX program that will provide
access to the AF/OPERATOR user interface. The AF/OPERATOR for MVS
Customization Menu then reappears.
7 Select Populate AF/OPERATOR for MVS Runtime Table Library by
typing 2 in the Option field. Press Enter.
Result: The Customizer tailors a batch job to populate the AF/OPERATOR
user interface runtime table library.
8 Review the code and press F3 to save it.
Result: The Submit Job for Execution panel appears. The Submit Job for
Execution panel appears.
9 Press Enter to submit the job, then press Enter again when you see ***.
Result: The Customizer submits the job and redisplays the AF/OPERATOR
for MVS Customization Menu.
10 Select Update AF/OPERATOR for MVS Runtime ISPF Tables by
typing 3 in the Option field. Press Enter.
Result: The table variables are updated to reference the correct product
libraries.
11 Press F3 twice.
Result: The Primary Customization Menu reappears. If either the IBM
REXX Runtime Library or the IBM Alternate Library for compiled REXX has
already been installed at your data center, you have now finished
customizing the AF/OPERATOR user interface. See “Verifying the User
Interface Customization” on page 132.
The AF/OPERATOR user interface requires installation of either the IBM
REXX Runtime Library or the IBM Alternate Library for compiled REXX. If
neither of those libraries has been installed at your data center, you can use
the Customizer to install the IBM Alternate Library for compiled REXX,
which is provided on a separate tape in your product package. See
“Installing the REXX Alternate Library” on page 183 for instructions.

Customizing the AF/OPERATOR User Interface 131

Verifying the User Interface Customization

Procedure
Follow this procedure to verify that the AF/OPERATOR user interface has been installed and
customized properly.

Step Action
1 Exit from the Customizer by pressing F3.
2 To start the AF/OPERATOR user interface, type this command at the command
line of any ISPF panel and press Enter:

TSO AO340

Result: The AF/OPERATOR Version 340 main panel appears. You can use the
Configuration option on this panel to set up profiles, user authorizations, and
recovery notification. Press F1 from any panel or input field for help.

Using the KAORSTRT command to initialize RCF

The KAORSTRT command initializes the AF/OPERATOR user interface’s resource control
facility (RCF). After you finish customizing AF/OPERATOR and the AF/OPERATOR user
interface, you need to tailor the KAORSTRT command for your data center.
A sample command, shown below, is provided in the startup member $$OGINIT (which
resides in rhilev.RKANCMD). $$OGINIT is run during the AF/OPERATOR customization
verification.
EX KAORSTRT ‘runtime_table_library rcf’
where:

runtime table library

Is the name of the AF/OPERATOR Version 340 runtime table library. The
default library, rhilev.RKANISP, is allocated during product customization.
rcf Is the name of the RCF for this copy of AF/OPERATOR. If you are running
more than one copy of AF/OPERATOR, each RCF must have a unique name
(for example, rcf1, rcf2, and rcf3). If you do not specify a name, the default
name RCF is used. You can only run one RCF in an AF/OPERATOR. Multiple
RCFs require multiple copies of AF/OPERATOR.

Candle recommends that you include the EX KAORSTRT command as part of your
AF/OPERATOR initialization startup process.
For further information on configuring and using the AF/OPERATOR user interface, see the
AF/OPERATOR User Interface Guide.

132 AF/OPERATOR Configuration and Customization Guide V340

AF/OPERATOR Startup Parameters

9
Introduction
This chapter describes the startup parameters that AF/OPERATOR uses at initialization. You
specify these parameters when you define address space environments using the Primary
Customization Menu.

Chapter Contents
Startup Parameter Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
ABENDLIM(WTO(nn),CMD(nn),WARNING) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
AOVTPOOL(LOADMOD1) and AOVTPLU0(LOADMOD2) . . . . . . . . . . . . . . . . . . . 136
ARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
CACHE(STRNAME(structure-name),MAXSIZE(nn)). . . . . . . . . . . . . . . . . . . . . . . . . 137
CKPT or NOCKPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
COMMAND(’first command to execute’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
CONSOLE(type) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
CONSOLE ID(console ID/console name) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
CPULIM(CPU seconds) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
DUB_AS_PROCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
DISKMLOG or NODISKMLOG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
FLOODCNTL(duplicate message limit). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
HOSTNAME(xxxxxxxx) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
JESTBL(member name | KOGJ2TAB or KOGJ3TB) . . . . . . . . . . . . . . . . . . . . . . . . 142
JOURNAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
LINKDEFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
LINKID(local system name and subsystem address space name or SYSID) . . . . . . . . 147
LOGON_RESPTIME(number of seconds). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
LOGONTLM(maximum number of seconds) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
MAXJOBS(maximum number of jobs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
MAXMAT(maximum number of queued and running matches) . . . . . . . . . . . . . . . . 148
MAXRUN(maximum number of concurrent matches). . . . . . . . . . . . . . . . . . . . . . . . 148
MAXTRP(maximum number of defined traps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

AF/OPERATOR Startup Parameters 133

MLWTO(FIRST, BUFNUM(10), MAXTVAL(15) | ALL) . . . . . . . . . . . . . . . . . . . . . . 150
MPFOPTS(NONE | SUPP | AUTO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
MSGDFLT (option,option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
MSGLIM(maximum number of messages per match) . . . . . . . . . . . . . . . . . . . . . . . . 152
MSMF_FOCAL_POINT(system) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
MSMF INTEGRITY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
OPERRESP(MAXTVAL(pp,ss)). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
OSYSNAME(Y | N) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
POVITRGC(\) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
RELOAD(type,option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
REXXARGS(AF | TSO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
REXXOUT(WTO | NOWTO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
RO(x) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
RTCD9_REPLY_SUPPRESSION(Y | N). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
RXSEARCH(LOAD | REXX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
SSCONNUM(number of subsystem consoles). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
STATS(COLLECT(OPT,...OPT),SMFREC(SMF#)) . . . . . . . . . . . . . . . . . . . . . . . . . . 157
SUBSYS(subsystem name | O34 and RO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
SYSID(JES3 name | system) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
TODISYNC(Y | N) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
TRAPDFLT(options) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
TRAPRESP(N | Y) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
UNDFTEXT(CMD | LOG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

134 AF/OPERATOR Configuration and Customization Guide V340

Startup Parameter Descriptions

Parameter descriptions
The AF/OPERATOR startup parameters are listed in alphabetical order by field name as they
appear on the Customizer panels. In some cases, the field name on a panel differs from the
Customizer-generated code that is saved in the RKANPAR member. The descriptions of the
AF/OPERATOR parameters that follow include each parameter’s default.

Symbol substitution in RKANPAR

When using MVS/SP Version 5.2 or greater, you can use system symbols within the startup
member in RKANPAR. At startup, these symbols are replaced by the appropriate substituted
text. Using system symbol substitution permits you to share a PARMLIB member between
AF/OPERATOR tasks.
Thus, for example, if you specify within RKANPAR the startup parameter
LINKID(&SYSNAME.O340) a different value is generated for LINKID depending on the
system where AF/OPERATOR is started. Starting AF/OPERATOR on SYSA and SYSB will
result in values of LINKID(SYSAO340) and LINKID(SYSBO340) respectively.

ABENDLIM(WTO(nn),CMD(nn),WARNING)
Default setting: ABENDLIM(WTO(30),CMD(5))
Specifies that a command (CMD) and/or WTO is disabled when the abend limit is reached.
The variable nn can be 1 to 99. If an option is not specified, the default (5 abends for CMD,
30 for WTO) is used.

CMD AF/OPERATOR stops trapping commands through the subsystem interface.

You can enable the command interface again by issuing the AF SSIRESET
or AF CMD command using the MODIFY command (for example, F
task,AF SSIRESET where task is the started task name of AF/OPERATOR
at your site).
WTO AF/OPERATOR stops trapping WTOs and DOMs. You can enable the WTO
and DOM interfaces again by issuing the AF SSIRESET, AF WTO, or AF
DOM command. If command processing has been disabled, you must issue
the commands using the MODIFY command; if not, issue the commands as
normal.
WARNING When specified, this option causes the production of a warning message
when the abend count reaches or exceeds 50 percent of the abend limit.
Note: Whether or not this warning message can be trapped depends upon
the nature of the abend.

The ABENDLIM parameter defines 4 system variables: AOABLCMD, AOABLWTO,

AOABCCMD, and AOABCWTO. AOABLCMD and AOABLWTO contain values for the
command and WTO abend limits, and cannot be changed while AF/OPERATOR is running.
AOABCCMD and AOABCWTO contain values for the command and WTO abend counts.

AF/OPERATOR Startup Parameters 135

Startup Parameter Descriptions

You can use the values in these variables in your site’s automation code to find out how many
abends have occurred or to control the issuing of the SSIRESET command.
The SSIRESET command clears all the abend count fields and enables all SSI functions. If
you prefer, you can issue AF CMD, AF WTO, and AF DOM commands individually to enable
each function and clear its abend count field.
Note: AOABCCMD and AOABCWTO can only be reset to zero. You cannot use a LET or
SYSVPUT to change them to any other value.
Abend limits prevent recursive abends in SSI from locking out AF/OPERATOR or the console
address space. Candle recommends that you initially set low limits (the defaults) and adjust
them upwards or downwards to suit your operating environment.

AOVTPOOL(LOADMOD1) and AOVTPLU0(LOADMOD2)

These parameters override the names of the default terminal definition modules.
If no values are specified, the default values will be the original names, AOVTPOOL and
AOVTPLU0.

LOADMOD1 and LOADMOD2

Specify the names of modules in the STEPLIB concatenation and are
the Assembled and AOVTPLU0 terminal definitions, respectively.

ARM
Default setting: ARM(NOLISTEN,DISABLED)
The ARM startup parameter permits the AF/OPERATOR task to monitor automatic restart
management (ARM)-related activities and to register itself with ARM for automatic recovery.
When the ARM LISTEN exit is enabled to monitor for ARM events, any ARM event that
occurs is delivered for AF/OPERATOR trap processing as an internal WTO. The ARM event
causes a message to be generated, but the WTO is not written to the SYSLOG. The message
is trappable using a WTO trap, provided that the WTO trap includes the AOTRAP keyword.
ARM processing is available only when running under MVS/SP Version 5.2 or later.

>> ARM (LISTEN/NOLISTEN >

>> ><
ENABLED(ELEMENT(xx),READY/NOREADY )

DISABLED

LISTEN Establishes a Listen exit for automatic restart management (ARM) events.
NOLISTEN Monitoring does not occur for ARM events (the default).
ENABLED AF/OPERATOR task is registered with ARM.

136 AF/OPERATOR Configuration and Customization Guide V340

Startup Parameter Descriptions

ELEMENT(xx)
Specifies the element name under which AF/OPERATOR is
registered with ARM. The maximum length of the element name is
16 characters, which can be alphanumeric characters, national
characters ($, #, or @), or the underscore (_). Element names must
not start with a number. Element names starting with the letters A
through I or the character string SYS are reserved by IBM.
READY Indicates automatically to ARM that AF/OPERATOR is ready for
work (the default).
NOREADY Causes the ARM-ready indication to be deferred to a user entry. You
enter the ARM-ready indication using the ARM REXX function. For
information about the ARM REXX function, see “Candle-Supplied
REXX Functions” in the AF/OPERATOR Command Reference
Manual.

DISABLED AF/OPERATOR task is not registered with ARM (the default).

CACHE(STRNAME(structure-name),MAXSIZE(nn))
The CACHE startup parameter enables the SYSPLEX REXX shared variable pool within
AF/OPERATOR, thus permitting the sharing of AF variables between AF/OPERATOR tasks
across a Sysplex environment.
It specifies the name of a cache data structure defined within the active CFRM policy of the
Sysplex coupling facility that will contain the AF variable data.

STRNAME Specifies the structure name of the cache structure defined to the active
CFRM policy to which this AF/OPERATOR will connect.
The maximum length of structure-name is 16 characters. A structure name
can consist of upper case alphanumeric characters, national characters ($, #,
and @), and the underscore (_). It must begin with an alphabetic character.
Structure names starting with the letters A through I or the character string
SYS are reserved.
MAXSIZE Specifies the approximate maximum size, in Kilobytes, of the data contained
within REXX shared variables defined to the Sysplex pool. The default value
is 4. Possible values are 4, 8, 16, and 32.
For the best use of coupling facility resources, specify the lowest value
required to contain your largest expected data value.
Note: The MAXSIZE value is applied when the structure is allocated.
(Structure allocation occurs when the first AF/OPERATOR to connect to the
structure is started after structure definition or after all data has been deleted
and resources cleaned up using SETXCF FORCE.) Any AF/OPERATOR
connecting to a structure that is already allocated cannot alter the MAXSIZE
value already assigned. If an attempt is made to alter MAXSIZE in these
circumstances, a warning message is issued indicating that the MAXSIZE
value could not be honored.

AF/OPERATOR Startup Parameters 137

Startup Parameter Descriptions

CKPT or NOCKPT
Default setting: CKPT(N)
This option is the “master switch” that activates or deactivates the AF/OPERATOR
checkpointing facility. The purpose of checkpointing is to preserve time-of-day traps and
user-defined system variables across AF/OPERATOR restarts.

N The Customizer default. TOD traps and system variables that you define will not be
checkpointed. The Customizer adds

NOCKPT

to your RKANPAR member.

Y The checkpointing facility will be enabled. The Customizer adds
CKPT

to your RKANPAR member.

To specify:
n what types of objects to reload at restart, see the RELOAD parameter
n when TOD traps are reloaded, see the TODISYNC parameter
n global checkpointing defaults for TOD traps, see the TRAPDFLT parameter

COMMAND(’first command to execute’)

Default setting: CMD('EX $$OGINIT')
COMMAND (or CMD) specifies the first command to be executed after AF/OPERATOR is
initialized. This parameter is used to run a command file that sets default values and
establishes the initial environment for AF/OPERATOR. The command file must be enclosed
in quotes. By default, the command is EXEC. EXEC starts the execution of command file
$$OGINIT, which runs a short installation verification procedure.

CONSOLE(type)
You can use this startup parameter to choose whether to employ subsystem consoles or
EMCS consoles.
AF/OPERATOR requires one console for every simultaneous use of the OPER command with
the RESP option. For information about the OPER command, see the AF/OPERATOR
Command Reference Manual chapter entitled “AF/OPERATOR Commands”.

>> CONSOLE(TYPE( SUBSYS ),LIMIT(number),PREFIX(prefix),KEY(key)) ><

EMCS

138 AF/OPERATOR Configuration and Customization Guide V340

Startup Parameter Descriptions

TYPE The console type, as follows:

SUBSYS Specifies that subsystem consoles are used regardless of the

MVS level.
For TYPE=SUBSYS, determine the number of subsystem
consoles that your installation is currently using by issuing
the D C,SS command. Count the number of consoles that
display as SUBS/SUBS. These are unused subsystem
consoles.
If the number of subsystem consoles you require is greater
than the number of unused consoles, you can generate
more by adding the following statement to the CONSOLxx
member of SYS1.PARMLIB:
CONSOLE DEVNUM(SUBSYSTEM) AUTH(ALL)

IPL your system to refresh this member of SYS1.PARMLIB.

EMCS Specifies that EMCS consoles are used as long as the MVS
system is at 4.2 level or above. If CONSOLE(EMCS) is
specified on a system with an MVS release earlier than 4.2,
the parameter is not honored and subsystem consoles are
used.

LIMIT(number) Controls the maximum number of consoles that can be in use by a particular
AF/OPERATOR address space, subject to the following:
n If TYPE=EMCS, the value for LIMIT can be 0 - 9999.
n If TYPE=SUBSYS, the value for LIMIT can be 0 - 99.
n If the LIMIT parameter is not specified, the default value is 4.
n If 0 is specified, no consoles will be used by the AF/OPERATOR address
space.
PREFIX(prefix) For EMCS consoles, sets the prefix of default console names. Valid values are
any 1- 4 alphanumeric characters (beginning with an alphabetic character).
The default is the subsystem ID as specified on the SUBSYS startup
parameter.
Default console names are created by appending a 4-character sequence
number to the value of this PREFIX subparameter. The 4-character sequence
number may be from 0001—nnnn, where nnnn is the value specified on the
LIMIT parameter above.
Note: This subparameter is meaningful only for EMCS consoles
KEY(key) An arbitrary string from 1 to 8 characters in length that is used with the MVS
D C,KEY= command to display information about the EMCS consoles
being defined. While this parameter is not required, Candle recommends
that you use the same string here as you have used in the PREFIX
subparameter.

AF/OPERATOR Startup Parameters 139

Startup Parameter Descriptions

CONSOLE ID(console ID/console name)

Default setting: CID(0)
CONSOLE ID (or CID) specifies the ID of the console used by AF/OPERATOR to issue
commands and WTOs (unless otherwise specified within the command or WTO). Any valid
MVS console ID or name is acceptable.
The default CID is the master console or the console from which the command to start
AF/OPERATOR was issued (if AF/OPERATOR is run as a started task). The default will be
used if the console ID is omitted, if the value specified is invalid, or if the console specified has
been deactivated. To ensure that AF/OPERATOR can always issue console commands and
WTOs, enter 0 to specify the master console.
Note: To determine whether a console is active, use the MVS DISPLAY CONSOLES
command.

CPULIM(CPU seconds)
Default setting: CPULIM(200)
Specifies the maximum number of CPU seconds for which any command file can execute.
This parameter prevents infinite looping in command procedures due to logic errors. The
valid range is 1 to 32767 seconds, with a default for AF/OPERATOR of 200.
Note: For the AF/OPERATOR user interface Resource Manager to run correctly, Candle
recommends that you set the CPULIM value to at least 250.

DUB_AS_PROCESS
Changes the default OS/390 UNIX System Services setting for DUB so that any new subtask
is treated as a separate process.
By default, a user of OS/390 UNIX System Services is treated as a thread within the individual
process of the address space. Certain programs may require that the user execute as a
separate process within a multitasking address space.
A program invoked using the AFCALL command can fail if it uses OS/390 UNIX System
Services and is unable to coexist with another active user of OS/390 UNIX System Services
within the AF/OPERATOR address space.
Note: The AF/OPERATOR TCP/IP client/server tasks created using the LINK START and
COMM START commands can use OS/390 UNIX System Services.
Important: This parameter should not be used if AF/OPERATOR is being started with
SUB=MSTR unless you are sure that UNIX System Services is available when
AF/OPERATOR starts. When a call is made to UNIX System Services to set DUB, and UNIX
System Services is not ready to handle the request, the request is delayed, causing
AF/OPERATOR to hang. If you are using SUB=MSTR, use the AF DUB_AS_PROCESS
command prior to starting TCP/IP communications. See the description of AF
DUB_AS_PROCESS in the OMEGACENTER Gateway for MVS Command Reference
Manual.

140 AF/OPERATOR Configuration and Customization Guide V340

Startup Parameter Descriptions

DISKMLOG or NODISKMLOG
Default setting: DISKMLOG(N)
DISKMLOG or the absence of this parameter enables or disables the switchable DASD
message log processing option.

N The Customizer default, directs the AF/OPERATOR message log to a SYSOUT

dataset. The Customizer-generated startup procedure references the
RKOGLOGM DD statement. The Customizer adds
NODISKMLOG

to your RKANPAR member.

Y Directs the AF/OPERATOR message log to pre-allocated switchable DASD
datasets. The Customizer prompts you to specify how many DASD datasets to
pre-allocate for this purpose (from 2 to 99). The Customizer-generated startup
procedure references OGMSGLnn DD statements (where nn = 01 to 99). The
RKOGLOGM DD statement will be commented out.
Each dataset will be allocated with an LRECL of 133 and a RECFM of FB. The
default message log dataset attributes (1200 BLKS of blocksize 6118) will fill
approximately 10 cylinders (for IBM 3380s). Such a log dataset will hold
approximately 55,200 messages. The Customizer adds
DISKMLOG

to your RKANPAR member.

This parameter is a single keyword and has no operands. Its presence in your
RKANPAR tells AF/OPERATOR to look for the //OGMSGLnn DD statements
and use them for message logging.

The switchable DASD message log option ensures message logging occurs even when JES is
unavailable. When a DASD dataset (pre-allocated for message logging) fills up,
AF/OPERATOR automatically redirects the log to the next dataset in the sequence. When the
last one fills up, the log switches back to the first one in the sequence. This process repeats for
as long as AF/OPERATOR remains active.

FLOODCNTL(duplicate message limit)

Default setting: FLOODCNTL(0)
Specifying FLOODCNTL can prevent AF/OPERATOR from being flooded with so many
duplicate WTO matches from the same job that the MAXMAT value is reached. Specify the
number of duplicate WTO matches that is to be considered a flood condition. The default, 0,
means that flood control checking does not occur. The maximum value for FLOODCNTL is
999.
Note: If 1 is specified, the value is automatically increased to 2. If the value specified is
greater than (MAXMAT * 80%) LESS MAXRUN, then the value is automatically
reduced to the value of (MAXMAT * 80%) LESS MAXRUN.

AF/OPERATOR Startup Parameters 141

Startup Parameter Descriptions

When checking for a flood condition, only the BACKLOG is checked. The BACKLOG
comprises those messages that have been queued to AF/OPERATOR, but have not yet been
accepted for processing. Once a queued match has been accepted for processing, it is no
longer used in testing for a flood condition. Once a flood condition is detected, only the first
match that is currently in the queue for this WTO is accepted by AF/OPERATOR and the
WTO trap that created the matches is disabled. All duplicate matches in the queue will be
discarded.
Specifying the use of FLOODCNTL does not relieve you of writing your traps to handle the
trapping of multiple duplicate WTO messages that are issued by the same job. Depending on
the value you specify for FLOODCNTL, the priority of the job that is issuing the messages,
and the general performance of your system, some duplicate messages will be written to the
operator before a flood condition is detected.
When a flood condition is detected, and if the trap causing multiple messages to occur is
disabled, AF/OPERATOR issues message AOP4098. When message AOP4098 is issued to
notify you that a specific trap is disabled, it is your responsibility to take whatever action is
required to reenable the trap.

HOSTNAME(xxxxxxxx)
Default member name: HOSTNAME.
This parameter overrides the default name of the trusted hostnames member in the
RKANPAR dataset.

JESTBL(member name | KOGJ2TAB or KOGJ3TB)

Default setting: JESTBL(KOGJ2TAB/KOGJ3TB)
Specifies the JES2 or JES3 offset table name (7-character maximum). It is the name of the
load module member that reflects the assembled field offsets for that particular system. The
module is loaded by AF/OPERATOR at startup to enable JES match variables to be accessed.
For JES3, AF/OPERATOR automatically defines the console exit module name as the offset
table name with an E appended. For example, if the offset table name is KOGJ3TB, the
WTO exit name is KOGJ3TBE.
You must insure that your module names reside in the AF/OPERATOR load library or the
MVS search libraries at startup.

142 AF/OPERATOR Configuration and Customization Guide V340

Startup Parameter Descriptions

JOURNAL
Required in AF/OPERATOR if you want traps to generate journal data. Journaling requires
backup datasets. The SLF journaling facility writes journal data directly to an MVS dataspace
within the SLF. At the interval you specify on the JOURNAL startup parameter, the contents
of the dataspace are copied to the currently active VSAM backup dataset. When a backup
dataset is full, writing is swapped to the alternate dataset and an archive procedure is
automatically started to archive the dataset that is full. The process to create the VSAM linear
backup datasets and define them in the startup JCL is found in “Defining Backup Datasets for
Journaling” on page 63.
The SLF journaling facility supports journaling within and across Sysplexes. When journaling
occurs within a Sysplex, that is, the local and remote SLFs are both within the same Sysplex,
connectivity is through the Cross-System Coupling Facility (XCF). When journaling occurs
between Sysplexes, connectivity is through TCP/IP. A complete discussion of SLF journaling
can be found in the Subsystem Logging Facility User’s Guide.
Here, we describe the AF/OPERATOR JOURNAL startup parameter and the settings required
to support both XCF and TCP/IP are documented. The syntax of the JOURNAL startup
parameter is:

JOURNAL >

LOCAL >

INTERVAL(n) ,ARCHIVE(x) PORT(nn)

REMOTE

(LINK(HOSTNAME(xx),PORT(nn) )

,ID(id) ,HUB
>

,GROUP(slfgroup) ,MODIFY_ID(slfsubs)

,SUFFIX(0) ,DESC(‘description text’)

> ><

,IMSCMD_LOG(YES/NO)

AF/OPERATOR Startup Parameters 143

Startup Parameter Descriptions

Journaling using XCF

If you are connecting a LOCAL and REMOTE SLF that are executing on systems within the
same Sysplex configuration, all of the JOURNAL keywords are optional. If omitted, each
keyword has a default value.
This example shows a standard XCF connection between a LOCAL and REMOTE:
JOURNAL(LOCAL,GROUP(TESTSLF1),SUFFIX(0))
and
JOURNAL(REMOTE,GROUP(TESTSLF1),SUFFIX(0))
If the GROUP and SUFFIX were allowed to default, the example could be as simple as
JOURNAL(LOCAL) and JOURNAL(REMOTE).

Journaling using TCP/IP

If the LOCAL and REMOTE SLF don’t execute in the same Sysplex, then the PORT keyword
is required on the LOCAL SLF and the LINK, PORT, and HOSTNAME keywords are required
on the REMOTE SLF. This example defines a TCP/IP connection.
JOURNAL(LOCAL(PORT(1025)))
and
JOURNAL(REMOTE(LINK(HOSTNAME(SYSA),PORT(1025))))

Journaling when connectivity is both XCF and TCP/IP

It is possible that both types of connections will be used in combination. That is, a LOCAL
SLF will be connected to a REMOTE SLF within the Sysplex via XCF and to another
REMOTE outside the Sysplex with TCP/IP. In that case, the LOCAL definition must use both
the PORT and GROUP options, but a REMOTE generally will use only GROUP or LINK,
unless it is a REMOTE Hub. See the SLF User’s Guide for a full discussion of the various
types of Sysplex configurations.
Parameters

LOCAL Specifies that this AF/OPERATOR manages the SLF dataspace.

REMOTE Indicates that intersystem communications are used and events are routed to
another AF/OPERATOR system that is managing an SLF dataspace.

144 AF/OPERATOR Configuration and Customization Guide V340

Startup Parameter Descriptions

LOCAL suboperands

PORT(nn) For the local SLF, defines the port number on which this TCP/IP
communications server will be listening for new client communications.
Port number can be any integer greater than or equal to 1025 and less
than or equal to 32767.
INTERVAL(nn) Defines the amount of time in seconds between checkpoint operations
for a local system. This causes the data in the dataspace to be physically
written to the VSAM backup dataset. The valid range is 1 to 3600
seconds, with a default of 60.
ARCHIVE(slfarchi) A 1-8 character name of the MVS archive procedure that starts
automatically when the VSAM backup dataset is full. The default archive
proc name is SLFARCHI.
The procedure is started with a SUFFIX=nn parameter, where nn equals
‘00’ or ‘01’, indicating which VSAM backup dataset is full and requires
archiving. These correspond to the RKOGSLF0 and RKOGSLF1 DD
statements in the AF/OPERATOR startup JCL.
S slfarchi,SUFFIX=nn

REMOTE suboperands

LINK Subparameters of the LINK parameter define the TCP/IP link used to
connect the remote to the local SLF.

HOSTNAME(xx) Used by the remote SLF only to connect to the

LOCAL. HOSTNAME must be used in conjunction
with PORT. The maximum length of
remote-hostname is 24 characters. It can be either a
dotted decimal IP address or a hostname defined to
your network’s domain name server. If
remote-hostname is a dotted decimal IP address,
none of the four numeric levels of the address can
exceed 255.
PORT(nn) Identifies the TCP/IP port number of the local SLF.
PORT must be used in conjunction with HOSTNAME
to fully identify the local SLF. Port number can be any
integer greater than or equal to 1025 and less than or
equal to 32767.

AF/OPERATOR Startup Parameters 145

Startup Parameter Descriptions

ID(id) Used by the REMOTE SLF to override the default

SLF LINKID.
Note: The ID you specify must not start with the #
symbol. AF/OPERATOR reserves linkids beginning
with a # in the range #0000001 to #9999999 for
internal use only.
HUB Indicates that this is a REMOTE hub. The TCP/IP
connection is used to connect to the LOCAL and the
XCF GROUP is joined.
If HUB is not specified, the XCF GROUP parameter
is ignored. Omitting the HUB specification causes this
connection to be a standard remote SLF using a
TCP/IP connection to the local SLF.

Common suboperands

GROUP(slfgroup) A 1-8 character group name identifier (slfgroup) used for intersystem
communication. Events on a remote system in this group are routed to
the associated local system. The default group name is SLFGROUP.
You associate a remote SLF system with a local SLF system by using
matching GROUP and SUFFIX parameters in the JOURNAL startup
parameter.
For example, if you start the local SLF with
JOURNAL(LOCAL,GROUP(TESTSLF1),SUFFIX(0))

then you connect the remote SLF with

JOURNAL(REMOTE,GROUP(TESTSLF1),SUFFIX(0))
MODIFY_ID(slfsubs)
A 1-8 character task name an operator uses to communicate directly with
the SLF journal task, independently of other AF/OPERATOR functions.
The operator uses a MVS modify command. The default SLF journal task
name is SLFsubs where subs is the AF/OPERATOR subsystem name.
SUFFIX(nn) A numeric value between 0 and 15 used to locate the correct journal
dataspace when displaying the information. The default is zero.
All SLF systems that interconnect or network should specify the same
suffix value.

146 AF/OPERATOR Configuration and Customization Guide V340

Startup Parameter Descriptions

DESC(description) Text (up to 25 characters) to distinguish between multiple journal

dataspaces used by multiple products. The default is spaces. If you imbed
spaces in the text, surround description with quotes. Examples:
DESC(TESTING)

DESC(‘TEST SLF’)
IMSCMD_LOG Specifying IMSCMD_LOG(YES) causes all IMSCMD response data to be
written automatically to SLF if SLF logging is available. The default is
IMSCMD_LOG(NO).

LINKDEFS
The syntax of the LINKDEFS parameter is:

>> LINKDEFS(xxxxxxxx ) ><

,TIMEOUT(nnn)

Default setting: LINKDEFS(LINKDEFS,TIMEOUT(20))

This parameter overrides the default name of the link definitions member in the RKANPAR
dataset. The default member name is LINKDEFS.
TIMEOUT(nnn) is optional and specifies the amount of time to wait during product startup
for the LINK START command that is issued immediately after processing the LINKDEFS
member to complete before startup is allowed to continue. nnn is the number of seconds in
the range 0-180, with a default value of 20. Using a value of 0 produces an indefinite wait.

LINKID(local system name and subsystem address space name or SYSID)

Default setting: LINKID(system and SUBSYS)
Specifies the name transmitted in peer-to-peer event messages (such as PEERLINK DEFINE)
to remote AF/OPERATOR address spaces. LINKID specifies the sending peer’s system name.
It can be used to filter WTO and CMD events received by remote peers. The value can be
any 1 to 8 character alphanumeric string, starting with an alphabetic character.
Each address space across all MVS systems must have a unique local system name. For this
reason, Candle recommends that LINKID be equal to
n The MVS SMFID for the AF/OPERATOR address space specified with an RO of zero on
each MVS system. For example, the recommended LINKID of SYSA with an RO of zero
is SYSA.
n The SMFID plus SUBSYS for the AF/OPERATOR address spaces specified with an RO of
1–9 or A–F. For example, the recommended LINKID of SMFID SYSA with an RO of 9 is
SYSAO159.

AF/OPERATOR Startup Parameters 147

Startup Parameter Descriptions

LOGON_RESPTIME(number of seconds)
Default setting: LOGON_RESPTIME(0)
Note: This parameter applies only to OMEGAVIEW sessions.
This value is the default number of seconds for the RESPTIME option of the LOGON
command. It is the maximum time that a VTAM session established by means of the LOGON
command is expected to take to respond. If the specified number of seconds is exceeded, the
LOGON session is terminated.

number of Specifies the default number of seconds for the RESPTIME option on the
seconds LOGON command. May be a value from 0 - 9999.

LOGONTLM(maximum number of seconds)

Default setting: LOGONTLM(20)
Specifies the maximum number of seconds allowed for AF/OPERATOR to connect to a
VTAM session (using the OMEGAMON Interface, the OMEGAVIEW Interface, or the
Programmerless Open VTAM Interface). The valid range is from 1 to 99. After the LOGON
command is issued, AF/OPERATOR waits for the specified number of seconds and verifies
that a session has been established. The following message is issued if the LOGON attempt
failed:
OBV224: STIMER ECB POSTED
If you are attempting to log on to a large network or you think your system’s response time
may be slow, increase the default.

MAXJOBS(maximum number of jobs)

Default setting: MAXJOBS(0)
Specifies the maximum number of jobs that can run concurrently on a different host. You can
specify a maximum value of 9000. This parameter should only be used in conjunction with
software products that transmit messages from one host to another. If no such software is
installed, set MAXJOBS to 0. JES3, AF/OPERATOR, and AF/OPERATOR’s peer-to-peer
facility do not require this parameter.

MAXMAT(maximum number of queued and running matches)

Default setting: MAXMAT(500)
Specifies the maximum number of both queued and running matches (tasks) that can be
handled by AF/OPERATOR. Estimate the maximum number of matches you expect at
activity peaks. The maximum value is 10000.

MAXRUN(maximum number of concurrent matches)

Default setting: MAXRUN(50)
Specifies the maximum number of matches you expect to be processed concurrently.
Matches exceeding this number are queued for later execution. The maximum value is 500.

148 AF/OPERATOR Configuration and Customization Guide V340

Startup Parameter Descriptions

MAXTRP(maximum number of defined traps)

Default setting: MAXTRP(1000)
Specifies the maximum number of traps, enabled and disabled, that can be defined. You can
specify a maximum value of 10000.
For the AF/OPERATOR user interface, you need to adjust the number of traps according to
the applications you are using. Traps used by other products must be added to those used by
the AF/OPERATOR user interface. Use the following guidelines to determine how you set this
parameter.
The following traps are used in AF/OPERATOR Version 340:
n Short-lived traps
These are TOD(*) traps that send events to various components of the product. They are
returned to the pool immediately upon execution. It is unlikely that a problem with heavy
trap utilization will occur with these traps unless many events happen at the same
moment. User actions that affect short-lived traps are:
– RCF commands. Each RCF command entered uses one short lived trap.
– Recovery retry notification definitions. Trap usage occurs only when a retry limit
(starting notification) is reached.
– Success/fail command definitions. Trap usage occurs only when they execute.
– Scheduled event occurrences. This refers specifically to the time between scheduled
events. In general, if scheduled events are close to each other, it is likely that
AF/OPERATOR will increase its trap
n Medium-lived traps
These are WTO traps that are used while an activity is in progress. These traps are
obtained when an activity starts and then returned to the free pool once the activity
completes. Medium-lived traps are of more concern than short-lived traps. The number
of success and fail messages defined can affect this usage of traps. To determine how
many traps will be used, you must identify all the resources that will be starting up or
shutting down at the same time. Group the resources together that will execute
overlapping activities. Trap usage equals the total number of success and fail messages
for that group of resources. If an activity retry count is defined for a resource that fails to
come up, the traps stay in use longer.
n Long-lived traps
These are WTO traps that extend beyond the life of events and activities. A long-lived trap
stays up for as long as the resource is up. User recovery retry definitions affect these traps.
To calculate the trap usage, identify all resources that are running together or resources
with overlapping up times. The usage is the total of all the recovery definitions for that
group of resources.
n Time-based traps
These are traps that schedule events in the future. Their life span depends on how far into
the future they are scheduled. User schedule definitions affect these traps. The number of
scheduled definitions is not proportional to the trap utilization. At any given moment,

AF/OPERATOR Startup Parameters 149

Startup Parameter Descriptions

there is only one time-based trap outstanding. That trap represents the next event to
occur. When that event occurs, it sets up another trap for the next event to occur. This is
not the same as the short-lived trap used to process the event. That short-lived trap is the
event.
Events that affect different resources at the same time (for example, resources that are
scheduled for some action at the same time) are handled under one event trap.

MLWTO(FIRST, BUFNUM(10), MAXTVAL(15) | ALL)

Default setting: MLWTO(FIRST BUFNUM(10) MAXTVAL(15))
This parameter specifies how AF/OPERATOR traps multi-line WTOs (MLWTOs) and
processes the matches they trigger.

FIRST Choosing Y specifies that AF/OPERATOR will trap the first line of each MLWTO
and put subsequent lines in AOTXT line variables. AF/OPERATOR assigns up
to 999 AOTXT line variables. Line variable are described in the AF/OPERATOR
Command Reference Manual.
An N response on the FIRST keyword specifies ALL, other keywords will be
ignored. Note: A WTO trap will only trap the first line of an MLWTO if you have
specified MLWTO(FIRST) at startup. This is also true for a WTO trap generated
by WAIT.
BUFNUM(10) Specifies the approximate number of MLWTOs that can be stored in the buffer
created when the MLWTO(FIRST) option is specified. (BUFNUM reverts to 0
when ALL is specified.) The value can range from 1 to 99. MLWTO buffer
storage is allocated in CSA. The contents of the buffer can be retrieved using the
AOTXTn line variable described in the AF/OPERATOR Command Reference
Manual.
MAXTVAL(15) A global timeout value that you can set for all MLWTO trapping on your
AF/OPERATOR system. It allows you to adjust the timeout interval for
MLWTOs with no end marker. MAXTVAL specifies, in seconds, how long to
wait after each line before assuming that the MLWTO has ended. The value
can range from 1 to 99 seconds. It is not the total elapsed time allowed for an
MLWTO. Normally, MLWTOs are available for processing by AF/OPERATOR
when the end marker is received. MAXTVAL is ignored if ALL is specified.
ALL The ALL specification is included only for downwards compatibility with the
Candle AOI Version 200, so that command procedures developed using the
ALL keyword do not require modification.
Important: If you are using AF/OPERATOR, do not choose this option. Using
ALL makes writing trap action commands more difficult and hinders
AF/OPERATOR performance.
On the Customizer panel, an N response on the FIRST keyword specifies ALL.
ALL indicates that AF/OPERATOR will monitor every line of a multi-line WTO
and will trigger a match if text from any line of the MLWTO matches the trap
pattern. The BUFNUM and MAXTVAL options are not available, and
AOTXT# and AOTXTn variables are not returned, if ALL is specified.

150 AF/OPERATOR Configuration and Customization Guide V340

Startup Parameter Descriptions

MPFOPTS(NONE | SUPP | AUTO)

Default setting: MPFOPTS(NONE)
Determines how AF/OPERATOR handles WTOs suppressed or automated by the Message
Processing Facility (MPF) of MVS.

NONE No WTOs are ignored (including those suppressed by MPF).

SUPP Only those WTOs suppressed by MPF are ignored.
AUTO Only those WTOs marked for automation in MPF are processed by
AF/OPERATOR.

The following table summarizes AF/OPERATOR’s handling of MPF settings. (In order for
AF/OPERATOR automation to occur, a trap must exist.)

MPF Flag Settings for the WTO Values of the MPFOPTS Parameter

NONE SUPP AUTO

None Process Process Ignore
Suppress Process Ignore Ignore
Auto Process Process Process
Auto and Suppress Process Ignore Process

AF/OPERATOR Startup Parameters 151

Startup Parameter Descriptions

MSGDFLT (option,option)
Default setting: MSGDFLT(ROUT(3,11), DESC(5),TPUT)
Specifies the default attributes for messages issued by AF/OPERATOR and from WTOs within
AF/OPERATOR command procedures. Options are:

ROUT(nn,...,mm)
Specifies the default routing codes or ranges for AF/OPERATOR
messages. Up to 128 different codes can be specified. The Customizer
panel accommodates 5 codes (the default). You can add more when
you are placed in edit mode for the RKANPAR member.
You can specify a range of routing codes by using a colon (:) or a dash (-)
as a delimiter:

ROUT(CODE,S,N:N,N-N)
DESC(nn,...,mm) Specifies the default descriptor codes or ranges for AF/OPERATOR
messages. Up to 16 different codes can be specified. The Customizer
panel accommodates 5 codes (the default). You can add more when
you are placed in edit mode for the RKANPAR member.
You can specify a range of descriptor codes by using a colon (:) or a dash
(-) as a delimiter:

DESC(CODE,S,N:N,N-N)
TPUT Indicates that messages addressed to TSO users are sent using
cross-memory TPUTs, causing them to appear on the user’s screen.
NOTPUT Indicates that messages addressed to TSO users are sent to the console.

For more information on routing and descriptor codes, refer to the IBM manual MVS/ESA
Message Library: Routing and Descriptor Codes.

MSGLIM(maximum number of messages per match)

Default setting: MSGLIM(1000)
Specifies the maximum number of messages that any match can issue. This parameter
prevents console flooding due to logic errors in command procedures. A match that issues
more messages than specified by MSGLIM is abended with user abend code 722. Setting a
value for MSGLIM that is too low causes excessive abends. The maximum setting is 32767;
the minimum is 10.

152 AF/OPERATOR Configuration and Customization Guide V340

Startup Parameter Descriptions

MSMF_FOCAL_POINT(system)
Default setting: None
Required for startup of the MSMF recovery feature, this parameter indicates the control point
system in a given MSMF facility. The specified system is the system receiving messages.

system The name of the focal point system; that is, the system receiving messages
from all of the other systems.

MSMF INTEGRITY
Default setting: MSMF INTEGRITY(N)
This option controls the level of the APPC integrity options that are used to detect MSMF
(Multi-System Management Facility) message loss.

N Message loss is not detected. The Customizer adds the following lines to your
RKANPAR member:
MSMF_INTEGRITY_LEVEL(BASE)
MSMF_INTEGRITY_SCOPE(NONE)
Y Multi-System Management Facility (MSMF):message loss
APPC confirmation protocols are used to detect the loss of messages. Warning
message 3036 or 3037 is displayed when a message is not delivered successfully.
The Customizer adds the following lines to your RKANPAR member:
MSMF_INTEGRITY_LEVEL(CONFIRM)
MSMF_INTEGRITY_SCOPE(ALL)
For more information, see the LU type 6.2 topic in the Transaction Programmers
Reference Manual.

OPERRESP(MAXTVAL(pp,ss))
Default setting: OPERRESP(5,5)
This parameter sets the default timeout value for MLWTOs with no end marker and
single-line WTO responses generated from the OPER with RESP command. The following
parameter is added to your RKANPAR member:
OPERRESP(MAXTVAL(pp,ss))

pp The number of seconds (from 1 through 99) that OPER/RESP will wait for the
first (primary) or only message of a response. The default is 5 seconds.
ss The number of seconds (from 1 through 99) that OPER/RESP will wait for the
subsequent messages of an MLWTO. The default is the value specified for pp.

If the OPERRESP parameter is not present during startup, the default of 5 seconds will be
used for both pp and ss. The number of seconds specified is the time between messages, not
the total elapsed time for the command. If the TIMEOUT(pp,ss) parameter is specified on the
OPER command, it overrides the default timeouts.

AF/OPERATOR Startup Parameters 153

Startup Parameter Descriptions

OSYSNAME(Y | N)
Default setting: OSYSNAME(Y)
The options are:

Y Allows AF/OPERATOR to determine the system ID, job name, job type, and job
ID from which an event (for example, a message) originated. This is necessary in
JES3, MSMF (peer-to-peer), and IBM sysplex environments. The SYSID, job
name, job type, and job ID are respectively stored in the global match variables
AOSID, AOJNAME, AOJTYPE, and AOJID.
JES3 users who want to differentiate between messages originating on a local
system and messages originating on a global system should specify
OSYSNAME(Y) in conjunction with the SYSID parameter.
Due to the way JES3 works, the job type for cross-system messages (originating
on one system but reissued on another) is always JOB. The AOJTYPE variable
will contain the true job type for messages issued on the originating system (either
JOB, STC, or TSU).
MSMF (peer-to-peer) and sysplex users who want to see the originating system ID,
job name, job type, and job ID for messages issued on the remote system in
response to the WTO command with SYSID parameter should also set
OSYSNAME(Y). Otherwise, these messages will reflect the values of the system
on which they were reissued.
N Specifies that AOSID, AOJNAME, AOJTYPE, and AOJID reflect the values of the
system specified in the SYSID parameter.
JES3 users who do not need to differentiate between messages originating on
their local and global systems can specify OSYSNAME(N) in conjunction with the
SYSID parameter. Messages will then reflect the SYSID of the global system.

POVITRGC(\)
Default setting: POVITRGC(\)
POVI uses a set of commands provided by AF/OPERATOR for direct communication with
VTAM 3270 applications. These commands all begin with a single character known as the
POVI trigger.
The default POVI trigger character is defined as “\” (back slash). This default can be changed
to accommodate terminal keyboards that do not have that character. If you find it necessary
to change the default, in addition to changing the character on this parameter, you must also
do the following:
1. Log on to the CT/Engine CUA operator APPLID.
2. Select Miscellaneous on the Administration pulldown menu.
3. Change the trigger character setting.
Do this for each POVI with which a particular AF/OPERATOR will communicate. You must
then substitute the new trigger character for all occurrences of the “\” in previously written or
Candle-supplied command procedures.

154 AF/OPERATOR Configuration and Customization Guide V340

Startup Parameter Descriptions

RELOAD(type,option)
Default setting: RELOAD(NONE, NOLIST)
Specifies whether, during initialization, AF/OPERATOR should restore TOD trap and
user-defined variable data previously written to the checkpoint dataset. Types are:

ALL Specifies that all of the data previously written to the checkpoint dataset
(ddname=RKOGCKP) will be restored. (The same as specifying TODS,
VARS, and RSVS.)
NONE Specifies that no data previously written to the checkpoint dataset will be
restored.
Important: Use this option with care, it reformats the checkpoint dataset.
All checkpointed traps and variables will be lost.
TODS Specifies that only TOD traps will be restored.
RSVS Specifies that REXX shared variables will be restored.
VARS Specifies that only user-defined system variables will be restored.

Options are:

LIST Specifies that during AF/OPERATOR initialization, a message will be

written to the AF/OPERATOR message log for each checkpoint record
which has been successfully restored.
NOLIST Specifies that during AF/OPERATOR initialization, no messages will be
written to the AF/OPERATOR message log regarding the reloaded
checkpoint record.

REXXARGS(AF | TSO)
Default setting: REXXARGS(AF)
Specifies how the EXEC command passes argument strings from AF/OPERATOR command
procedures to REXX execs.

AF Specifies that arguments passed to REXX execs should be interpreted as

they are in AF/OPERATOR command procedures: each argument
delimited by a blank is received by the REXX EXEC as a separate
parameter. Retain the default setting of AF to avoid modifying existing
REXX language command procedures written for other Candle products.
Note: You must set REXXARGS to AF if you will be running the
AF/OPERATOR user interface.
TSO Specifies that arguments passed to REXX execs should be interpreted as
they normally are in the TSO environment: anything between the quotes
is received as a single parameter.

AF/OPERATOR Startup Parameters 155

Startup Parameter Descriptions

For example, the parameters in the statement

EXEC REXXEXEC ‘HELLO THERE’
would be interpreted as follows:

AF 2 parameters: HELLO and THERE

TSO 1 parameter: HELLO THERE

REXXOUT(WTO | NOWTO)
Default setting: REXXOUT(NOWTO)
Specifies whether output of REXX SAY and TRACE commands will be written to the
SYSLOG and the job log of the AF/OPERATOR task.

NOWTO Specifies that output of REXX SAY and TRACE commands will be
suppressed and will not be written to the logs.
WTO Specifies that output of REXX SAY and TRACE commands will be written
to SYSLOG and the job log of the AF/OPERATOR task. Output will be
written to OGMSGLOG, to RKOGLOGM, and, under OG*TSO, to the
OG*TSO PSEUDOCONSOLE.

RO(x)
Default setting: RO(no default)
Sets the relative order in which active AF/OPERATOR address spaces receive command and
WTO events. An address space with a relative order of zero is the first address space to
receive command and WTO events. The RO value (x) can be from 0 to 9 through A to F.
Address spaces with the same relative order receive SSI data in order of initialization; the
address space started first receives data first. If any AF/OPERATOR subsystems are shut
down and then restarted, they will resume their position of relative order. Once set, the values
of RO for a specific subsystem cannot be altered without a system IPL.

RTCD9_REPLY_SUPPRESSION(Y | N)
Default setting: RTCD9_REPLY_SUPPRESSION(Y)
Specifies whether replies to WTORs with a route code of 9 will be suppressed internally.

Y The word SUPPRESSED replaces the text of any reply to a WTOR with a
route code of 9.
N Replies to WTORs with a route code of 9 are not suppressed.

156 AF/OPERATOR Configuration and Customization Guide V340

Startup Parameter Descriptions

RXSEARCH(LOAD | REXX)
Default setting: RXSEARCH(LOAD)
Specifies the search order for REXX functions.

LOAD Specifies that the LOAD libraries are to be searched prior to the CLIST/EXEC
libraries.
REXX Specifies that the CLIST/EXEC libraries are to be searched prior to the LOAD
libraries.

Syntax
RXSEARCH(LOAD) or
RXSEARCH(REXX)
Note: In most cases, the value of this parameter should be set according to where most of
your REXX functions reside. If the majority are compiled programs, use the default
LOAD. If the majority are REXX EXECs, change this parameter to REXX.

Caution
There are some functions in the samplib that have the same name as programs supplied by IBM, for
example, WTO, WTOR, and so forth. If you use any REXX EXEC having a name that matches a
program in your load libraries, you must set this parameter to REXX.

SSCONNUM(number of subsystem consoles)

This parameter is replaced by the CONSOLE LIMIT() parameter.

STATS(COLLECT(OPT,...OPT),SMFREC(SMF#))
Default setting: NO DEFAULT SETTING
The STATS parameter specifies how AF/OPERATOR gathers SMF data used for statistical
reports.

SMF# Is the SMF record number to be used for the AF/OPERATOR data. The
default is 200. Check with your systems programmer to determine which
numbers are being collected by SMF and are not currently in use by another
application.
OPT Can be one or more of the following:

NONE No SMF data will be collected.

ALL All SMF data will be collected.
MATCH Only MATCH data will be collected.
EXEC Only EXEC data will be collected.
FILE Only FILE data will be collected.
IMMED Only immediate update information will be collected
for message suppression and rerouting.

AF/OPERATOR Startup Parameters 157

Startup Parameter Descriptions

Options may be specified in any combination and in any order with the following
considerations:
n If NONE is specified, it takes precedence over any other options specified at the same
time.
n If ALL is specified, it takes precedence over any other options specified at the same time
with the exception of NONE.
The following is an example of the AF/OPERATOR startup parameter:
STATS(COLLECT(NONE),SMFREC(200))

SUBSYS(subsystem name | O34 and RO)

Default setting: SUBSYS(O34 and RO)
Specifies the name of the MVS subsystem.
Note: Specify the SUBSYS parameter only when issuing a command from a console. Do not
specify SUBSYS in a REXX exec.
The parameter is a 1 to 4 character string beginning with a 3-character OMEGACENTER
address space prefix and ending with the RO parameter. The characters can be
n uppercase alphabetical characters
n numerals 0 to 9
n any of the following:
cent sign (), period (.), less than (<), left brace ({), plus sign (+), broken line (|),
ampersand (&), exclamation point (!), dollar sign ($), dash (-), slash (/), per cent sign (%),
underline (_), greater than (>), at sign (@), apostrophe (’), quote mark (=), back slash (\),
tilde (~)
You can use characters such as $ or / in conjunction with alphabetical characters, numeric
digits, or other characters. You cannot define SUBSYS as a 1-character string composed of,
for example, $ or /.

Caution: The Customizer uses O34 as the address space prefix, but you can define
it as you choose. However, SUBSYS cannot conflict with
n an MVS console command (for example, STOP)
n MVS console command abbreviations (for example, R, F, P, D, or $DI)
n an MVS subsystem ID (for example, AFP, AB22, JES2, JES3, or ACF)
n any subsystem recognition characters (for example, $, /, or *)

158 AF/OPERATOR Configuration and Customization Guide V340

Startup Parameter Descriptions

SYSID(JES3 name | system)

Default setting: SYSID(local MVS system name)
Specifies the name of the MVS system in which the AF/OPERATOR address space is running.
JES2 users must specify the name of the MVS system on which the AF/OPERATOR address
space is executing or accept the default. This name is specified by the SYSNAME= parameter
in SYS1.PARMLIB(IEASYSxx) and is the default for JES2 or JES3.
JES3 users may specify the ID of the JES3 MAIN processor on which the AF/OPERATOR
address space is executing and must specify OSYSNAME(Y) if they need to differentiate
between messages originating on a local system and messages originating on a global system.

TODISYNC(Y | N)
Default setting: TODISYNC(N)

N Specifies that time-of-day (TOD) traps restored from the checkpoint dataset are
scheduled to run at startup.
Y Causes restored TOD scheduling to be delayed until the entire initialization is
completed and you issue the AF TODSTART command. Specifying Y avoids
receiving error messages issued when a trap fires and does not have access to
data it needs from the system.
Note: Specifying Y only suspends TOD traps which are stored in the checkpoint file.
Other TOD traps defined after initialization are processed normally.

AF/OPERATOR Startup Parameters 159

Startup Parameter Descriptions

TRAPDFLT(options)
Default setting: TRAPDFLT(LOG, DISABLE,NORETAIN)
Allows you to specify default attributes for all types of traps. Y on the Customizer panel
indicates a positive response (LOG,ENABLE,RETAIN). N indicates a negative response
(NOLOG,DISABLE,NORETAIN). Options are:

LOG Each time a trap is triggered, a message is written to the AF/OPERATOR

message log.
NOLOG When a trap is triggered, no message is written to the AF/OPERATOR
message log.
ENABLE The trap is enabled (activated) as soon as it is defined.
DISABLE The trap is disabled (deactivated) when it is defined. It must be enabled by a
TRAP ENABLE command.
RETAIN Information about each match is recorded for display by the automation
facility’s RETAIN*VIEW facility.
NORETAIN Information about each match is not recorded for the automation facility’s
RETAIN*VIEW facility.
ALLSYS If ALLSYS is specified, the default attribute for the SYSID(pattern) of your
traps becomes SYSID(*). Traps with an unspecified SYSID will trap events
from any system.
Exception: ALLSYS(Y) does not apply to traps generated internally by the
WAIT command.
If ALLSYS is not specified, the SYSID startup parameter value is used as the
default attribute for the SYSID(pattern) of your traps. Traps with an
unspecified SYSID will only trap events from the local system.
In JES3 environments, not using ALLSYS means
n If OSYSNAME(Y) is specified, only messages from the global will be
trapped on the global.
n If OSYSNAME(N) is specified, all messages will be trapped on the
global, even if originally issued on a local.
CKPT(TOD) If CKPT(TOD) is specified, all TOD traps will be checkpointed unless you
explicitly override this default by including the NOCKPT option on each
TRAP ADD TOD command.
If CKPT(TOD) is not specified, all TOD traps will not be checkpointed by
default.
Note: The CKPT startup parameter must be specified to activate the
checkpointing facility.

160 AF/OPERATOR Configuration and Customization Guide V340

Startup Parameter Descriptions

TRAPRESP(N | Y)
Default setting: TRAPRESP(N)

Y Specifies that messages in response to commands issued by AF/OPERATOR are

eligible for trapping and AF/OPERATOR will check to see if a trap exists for the
response. The responses are made available through line variables. (See the
AF/OPERATOR Command Reference Manual, for information on line variables.)
N Specifies that AF/OPERATOR does not check if a trap exists for solicited responses
to AF/OPERATOR commands.

UNDFTEXT(CMD | LOG)
Default setting: UNDFTEXT(LOG)

LOG Routes unrecognized text in a command file to the AF/OPERATOR log.

CMD Executes undefined text as an assumed MVS operator command.

AF/OPERATOR Startup Parameters 161

Startup Parameter Descriptions

162 AF/OPERATOR Configuration and Customization Guide V340

Migration Considerations

10
Introduction
This chapter covers some considerations you should be aware of when migrating from a
previous version of AF/OPERATOR to the current Version 340.

Chapter Contents
Single AF/OPERATOR Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
AF/OPERATOR Coexistence with Existing Automation Products . . . . . . . . . . . . . . . . . . 165
Multiple AF/OPERATOR Address Spaces on a Single MVS System. . . . . . . . . . . . . . . . . 167
Multiple AF/OPERATOR Address Spaces on Multiple Systems . . . . . . . . . . . . . . . . . . . . 170
Considerations for IMS/VS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Coexistence Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Migration Considerations 163

Single AF/OPERATOR Compatibility

If you do not use multiple address space support (that is, you are running only one
AF/OPERATOR address space on one MVS system), AF/OPERATOR Version 340 will
perform similarly to your pre-Version 240 automation product with the exception of
automation console commands.

Migration issue

Migration
Issue Description
Command In Version 340, all automation console commands (for example, SHOW TRAPS)
qualification must be directed to a specific AF/OPERATOR subsystem in one of the following
ways:
n Prefix the command with the AF/OPERATOR subsystem name specified by
the SUBSYS startup parameter. (See “AF/OPERATOR Startup
Parameters” on page 133 for information about startup parameters.)
n Issue the MVS MODIFY command to direct the console command by address
space name.
For compatibility with pre-Version 240 console commands, execute the
KOGOCMDS REXX exec from the startup automation procedure (specified using
the CMD startup parameter). The REXX exec issues TRAP ADD commands to
enable pre-Version 240 commands to be matched and processed by the current
address space. This exec is generated during the customization process.
$$OGINIT is called using the CMD startup parameter. $$OGINIT can call
KOGOCMDS as follows: Status = KOGOCMDS(‘’O340’’), where O340 is
the subsystem that will be responsible for processing unprefixed AF/OPERATOR
commands. Refer to the comments in KOGOCMDS for further details.
Note: Specify the SUBSYS parameter only when issuing a command from a
console. Do not specify SUBSYS in a REXX exec.

164 AF/OPERATOR Configuration and Customization Guide V340

AF/OPERATOR Coexistence with Existing Automation Products

Introduction
AF/OPERATOR can coexist with previous releases of Candle automation products on the
same MVS system.

Migration issues
Because command and WTO events are serially processed by each automation subsystem,
the following considerations must be addressed:

Migration Issue Description

Subsystem Console commands
processing of Processed in the reverse order of automation address space startups
command and after a system IPL. For example, if AF/OPERATOR Version 340 is
WTO events started after a pre-Version 340, the automation of console commands
is processed by the AF/OPERATOR Version 340 address space first,
then by the pre-Version 340 address space.
WTO messages
Processed in the order of automation address space startups after a
system IPL. For example, if AF/OPERATOR Version 340 is started
after a pre-Version 340, the automation of messages is processed by
the AF/OPERATOR pre-Version 340 address space first, then by the
AF/OPERATOR Version 340 address space.
Exception: JES3 sites determine the order of message processing as
the reverse order of address space startups after an IPL.
Communicating In Version 340, all automation console commands (for example, SHOW
between TRAPS) must be directed to a specific AF/OPERATOR subsystem in one of
AF/OPERATOR the following ways:
address spaces
n Prefix the command with the AF/OPERATOR subsystem name
specified by the SUBSYS startup parameter (for example, O340
SHOW TRAPS). Because the SUBSYS value must be unique within
an MVS image, Candle recommends that you use O340 for the
AF/OPERATOR address space name. O34 indicates an
AF/OPERATOR Version 340 subsystem; 0 indicates that this is the first
AF/OPERATOR subsystem started after an IPL.
n Issue the MVS MODIFY command to direct the console command by
address space name (for example, F OGO340, SHOW TRAPS).

Note: Specify the SUBSYS parameter only when issuing a command from
a console. Do not specify SUBSYS in a REXX exec.

Migration Considerations 165

AF/OPERATOR Coexistence with Existing Automation Products

Migration Issue Description

AOSIM AOSIM is used to
n initiate end-user defined automation events
n automate CICS, IMS, and JES3 events
n initiate automation from OMEGAVIEW actions

AOSIM can be either link-edited into load modules or dynamically loaded

and called. If AOSIM is link-edited into load modules, the modules must
be relinked with the AF/OPERATOR Version 340 AOSIM in order to issue
events to the AF/OPERATOR Version 340 address spaces. Because
OMEGAVIEW dynamically loads AOSIM, the STEPLIB load library must
reference the AF/OPERATOR Version 340 load library in which AOSIM
resides.
NetView PPI When an AF/OPERATOR address space coexists with a pre-Version 340
address space and the NetView PPI is used, you must ensure that the
equivalent version of the NetView load modules distributed by Candle is
included in the associated NetView and NetView subsystem started task
JCL procs. Therefore, a NetView address space with the pre-Version 340
load modules installed and an AF/OPERATOR Version 340 address space
must not communicate with each other.

166 AF/OPERATOR Configuration and Customization Guide V340

Multiple AF/OPERATOR Address Spaces on a Single MVS System

Migration issues
More than one AF/OPERATOR address space can be started on one MVS system. To do this,
the following considerations must be addressed:

Migration
Issue Description
Subsystem Console commands and WTO messages are processed in the order of
processing of automation address space startups after a system IPL. You can use the RO
command and (relative order) parameter to set the order in which events are processed.
WTO events Specify the first address space to receive data with an RO of 0, the second with
an RO of 1, and so on. If any AF/OPERATOR subsystems are later shut down
and then restarted, they will resume their position of relative order.
Separating Automation REXX execs can be directed to separate AF/OPERATOR address
automation spaces. Each address space may allocate a different RKANCMD PDS
containing the automation procedures to be executed within the address space.
For example, separate REXX execs into common and address space-specific
partitioned datasets. You can then use a combination of dataset
concatenations to allow some or all address spaces to execute the common
procedures. Procedure combinations are useful when AF/OPERATOR address
spaces are configured as stand-by address spaces that intercept events not
suppressed by lower relative order address spaces.

Migration Considerations 167

Multiple AF/OPERATOR Address Spaces on a Single MVS System

Migration
Issue Description
Communicating In Version 340, all automation console commands (for example, SHOW
with TRAPS) must be directed to a specific AF/OPERATOR subsystem in one of the
AF/OPERATOR following ways:
address spaces
n Prefix the command with the AF/OPERATOR subsystem name specified by
the SUBSYS startup parameter (for example, O340 SHOW TRAPS).
Because the SUBSYS value must be unique, Candle recommends that you
use O340 for the AF/OPERATOR address space name. O34 indicates an
AF/OPERATOR Version 340 subsystem; 0 indicates that this is the first
AF/OPERATOR subsystem started after an IPL.
For example, to start four AF/OPERATOR address spaces on an MVS
system assigned an SYSID (SMFID) of SYSA, assign a unique SUBSYS
name to each address space (O340, O341, O342, and O343) in the order
you require for event processing. Then, to ensure that the AF/OPERATOR
address spaces are started in relative order after an IPL, issue the MVS
START commands for these address spaces as part of the startup
automation procedure for the first OMEGACENTER address space. (See
SUBSYS in “AF/OPERATOR Startup Parameters” on page 133 for
more information.)
n Issue the MVS MODIFY command to direct the console command by
address space name (for example, F SYSA, SHOW TRAPS).
For compatibility with pre-Version 240 console commands, execute the
KOGOCMDS REXX exec from the startup automation procedure (using the
COMMAND startup parameter). KOGOCMDS issues TRAP ADD commands to
enable pre-Version 240 comands to be matched and processed by the current
address space.
CAUTION: If you call the KOGOCMDS REXX exec, ensure that the command
traps added are only for a single AF/OPERATOR address space responsible for
processing unqualified commands on MVS systems. If traps are added for more
than one AF/OPERATOR address space, processing of unqualified console
commands will be unpredictable. Candle recommends that you invoke the
KOGOCMDS REXX exec as part of the startup automation procedure so that
unqualified console commands are matched and processed in the first (RO=0)
address space.
$$OGINIT is called using the CMD startup parameter. $$OGINIT can call
KOGOCMDS as follows: Status = KOGOCMDS(‘’O340’’), where O340 is
the subsystem that will be responsible for processing unprefixed
AF/OPERATOR commands. Refer to the comments in KOGOCMDS for further
details.
Note: Specify the SUBSYS parameter only when issuing a command from a
console. Do not specify SUBSYS in a REXX exec.

168 AF/OPERATOR Configuration and Customization Guide V340

Multiple AF/OPERATOR Address Spaces on a Single MVS System

Migration
Issue Description
WTO message User-defined traps for messages issued from AF/OPERATOR address spaces
traps with may require recoding to limit WTO messages issued from the current address
AOTRA space. This prevents the traps from being triggered by WTO messages issued
from other AF/OPERATOR address spaces. You can use the
ASID(&AOTASKAS) and SYSID(&AOSYSID) parameters to limit trapping to
the AF/OPERATOR address space in which the traps were created.
The system variables perform the following functions:

AOSYSID Specifies the MVS system ID on which the AF/OPERATOR

address space is running.
AOTASKAS Specifies the address space ID (ASID, decimal integer value)
of the AF/OPERATOR address space.

Prioritizing Once automation has been separated into multiple AF/OPERATOR address
address space spaces, you can assign a specific MVS performance group to a specific address
by site policies space in order to match your site’s workload policies.
For example, if system critical automation is placed in one AF/OPERATOR
address space, the performance group for that address space can be set to allow
it to execute in preferred MVS domains (those with high CPU and I/O
dispatching priorities). Alternatively, the performance group assigned for
AF/OPERATOR address spaces that execute non-critical and test automation
can specify low demand MVS domains.
Isolating You can separate automation into multiple AF/OPERATOR address spaces in
automation to order to isolate critical production automation from unstable test automation.
improve RAS Outages caused by abending or looping automation procedures will only affect
the AF/OPERATOR address space in which the unstable procedure runs.
Furthermore, higher relative order address spaces can be programmed to
intercept events that have not been suppressed by lower relative order address
spaces.

Migration Considerations 169

Multiple AF/OPERATOR Address Spaces on Multiple Systems

Migration issues
Multiple AF/OPERATOR address spaces executing on multiple MVS systems in an MVS
complex can communicate with each other through peer-to-peer links:

Migration
Issue Description
Linking systems Specify the SYSID (SMFID) as the LINKID startup parameter for the first
AF/OPERATOR address space started on each system to provide compatibility
with pre-Version 240 peer-to-peer link conventions and to minimize recoding of
existing automation procedures, such as REXX exec and command files.
For peer-to-peer links by other address spaces, Candle recommends that you use
the following naming convention to construct the value for LINKID:
n The SYSID (SMFID) of the MVS system (for example, SYSA).
n The SUBSYS prefix value, O34, for the AF/OPERATOR address space name.
n The RO value, 0–9,A–F, for the relative order of the address space.
Using these conventions, the LINKIDs on two systems (A and B) for address spaces
started third on each system are SYSAO342 and SYSBO342. These conventions
are recommended, not required. However, whatever method you choose to define
LINKID, remember that its value must be unique within the VTAM network
connecting AF/OPERATOR address spaces in an MVS complex. (See LINKID in
“AF/OPERATOR Startup Parameters” on page 133 for more information.)
Note: Use of multiple links can be complex. Candle recommends that you start
with multiple address space support in an MVS complex by defining peer-to-peer
links only between the AF/OPERATOR address spaces on each system defined
with a relative order of zero. You can link other address spaces when you need
them.
MSMF trapping Use the LINKID() parameter on the TRAP ADD and TRAP CHANGE automation
by LINKID commands so that SSI events passed between systems can be trapped by specific
receiving AF/OPERATOR address spaces. For example, you can make
AF/OPERATOR address spaces with subsystem names of O342 responsible for
CICS automation on SYSA and SYSB.
The traps for WTO messages received from remote address spaces specify the
LINKID startup parameter of the sending address space. LINKID patterns can also
be used in trapping to allow filtering by partial LINKID values.
You can also use LINKID to trap events for
n load balancing, by distributing inbound automation events to specific
AF/OPERATOR address spaces and peer-to-peer links
n enhanced RAS, by providing redundant peer-to-peer communication paths
between MVS systems
n off loading of peer-to-peer processing to dedicated AF/OPERATOR address
spaces

170 AF/OPERATOR Configuration and Customization Guide V340

Multiple AF/OPERATOR Address Spaces on Multiple Systems

Preventing WTO and command rerouting loops are possible because of the increased
WTO and rerouting combinations that can occur between multiple linked peer address
command spaces. For example, the following set of TRAP ADD commands can cause an
rerouting loops infinite rerouting loop between 3 peer address spaces:
On SYSA:
TRAP ADD(XXX) WTO(XXX*) ....NEWSYS(SYSB)
On SYSB:
TRAP ADD(XXX) WTO(XXX*) ....NEWSYS(SYSC)
On SYSC:
TRAP ADD(XXX) WTO(XXX*) ....NEWSYS(SYSA)

Note: The potential for rerouting loops to occur is increased by the number of
AF/OPERATOR address spaces trapping and rerouting WTO and command
events. Candle recommends that you begin multiple address space support by
limiting peer-to-peer trapping and rerouting to only the address spaces with a
relative order of zero. Once established, you can expand to more sophisticated
combinations of peer event handling.

Migration Considerations 171

Considerations for IMS/VS

Introduction
The table below describes migration considerations.

Migration issues

Migration Issue Description

Additional Previously, the Candle-supplied exit program, KABIMX02, which you can use
function for for the IMS exit DFSAOUE0, only processed commands. Now this exit program
sample exit also processes command responses of any number of lines.
program To maintain backward compatability, this new feature of KABIMX02 is shipped
KABIMX02 disabled. To enable processing of multiple segment messages:
1. Locate these statements in the KABIMX02 source code:
LCLC &ENAMULT
&ENAMULT SETC ‘N’ <---ENABLE MULTIPLE SEGMENT? ‘Y’ or ‘N’

2. Change ’N’ to ’Y’.

Note: With IMS 5.1 and above, it is no longer necessary to linkedit DFSAOUE0
into the IMS nucleus. It is now a standalone 31-bit module that is enabled by
residing in IMS RESLIB. Specifying AOEXIT=YES on the COMM system
generation macro is no longer valid.
JOBTYPE(IMS) Documentation of the TRAP command, found in the AF/OPERATOR User’s
considerations Guide, describes JOBTYPE(IMS) and indicates a special condition where you
must set the SYSID parameter to the IMS control region name where the
message originates.
You can either use the actual SYSID or IMS region name. This is preferred, but
not required, when using SLF.
Both Candle-supplied exit programs KABIMX02 and KOGIMXCC provide the
ability to use the actual SYSID and region name. To maintain backward
compatability, this feature is shipped disabled. To enable the feature, do the
following in each exit module source:
1. Locate these source statements:
LCLC &ENAUSER
&ENAUSER SETC ‘N’ <---ENABLE AOUSERID OVERRIDE? ‘Y’ OR ‘N’

2. Change ’N’ to ’Y’.

172 AF/OPERATOR Configuration and Customization Guide V340

Coexistence Considerations

Checkpoint data considerations

AF/OPERATOR can restore data written to the checkpoint KSDS by any of the supported
older versions of the product. However, maintenance to the older version is required in order
to permit this restoration to occur. For information, call your Candle Support Center.

Subsystem Logging Facility intersystem connectivity

Users of the Subsystem Logging Facility (SLF) should be aware that AF/OPERATOR Version
340 can act as the central repository (referred to as the local SLF) for remote SLF systems at
an older level. However, maintenance to the older version is required to permit this to occur.
For information, contact your Candle Support Center.

Migration Considerations 173

Coexistence Considerations

174 AF/OPERATOR Configuration and Customization Guide V340

Defaults for Customizer-Generated

A Members

Overview

Introduction
This appendix describes some default characteristics of the JCL and assembly source
generated by the Customizer.

JCL members
When you use the Customizer to tailor AF/OPERATOR’s functions and features to your
complex, you can choose to save generated JCL and submit the job at a later, more
convenient time. The following lists the default names and libraries of AF/OPERATOR batch
jobs you can choose to submit after you exit the Customizer.

Default names for JCL members

The Customizer uses the default names listed below for the JCL members it generates.
The following members reside in the rhilev.@system.RKANSAM library.

Name Description
OGSPDS## AF/OPERATOR runtime dataset JCL.
CICSJLc CICS V2 exit JCL.
CICS3JLc CICS V3 exit JCL.
IMSJCLc IMS exit JCL.
J2TABJCL JES2 offset table JCL.
J3TABJCL JES3 offset table JCL.
J3WCJCL JES3 command and WTO exit JCL.
J3CNJCL JES3 console exit JCL.
NETVJCL NetView exit JCL.
LVSPDSn POVI support dataset JCL.

Defaults for Customizer-Generated Members 175

Overview

The following members reside in the rhilev.@system.RKANSAM library.

Name Description
ACF2JCL ACF2 security exit JCL for POVI.
TOPJCL TOP SECRET® security exit JCL for POVI.
MODETABL Logmode table JCL.

Utilities
The following is a list of the utilities customized using option B of the Primary Customization
Menu.
Name Description
AOSSFTBL Subsystem function table.
AOSSNTBL Subsystem table name.
AOSVCTBL SVC name table.
AOUSRSEC Command security exit.

The default library for the utility batch jobs generated by the Customizer is
rhilev.@system.RKANSAM.
Virtual terminal interface
The Customizer uses the following names for the virtual terminal interface’s assembly source
and JCL members.
Name Description
AOVTPOOL Virtual terminal interface assembly source for OMEGAMON and POVI that
tells AF/OPERATOR the LU name to be used to start POVI and OMEGAMON
automation sessions.
AOVTPOL@ Virtual terminal interface JCL for OMEGAMON and POVI.
AOVTPLU0 Virtual terminal interface assembly source for OMEGAVIEW.
AOVTPLU@ Virtual terminal interface JCL for OMEGAVIEW.

The default library for all of the assembly source and JCLV members generated by the
Customizer is rhilev.@system.RKANSAM.
Generating JCL for remote systems
Some of the batch jobs the Customizer generates reference system libraries such as
SYS1.MACLIB and SYS1.MODGEN. If you generate JCL for a system other than the local
system (the system where you are executing the Customizer), be aware of how the job uses
system libraries.
When you submit a generated job without modification, by default, the job references the
system libraries listed in the master catalog of the system running the job. Since each system
in the complex can run with different MVS and maintenance levels, this may not always be
appropriate.
To ensure that the job references the correct system libraries, you can do either of the
following:

176 AF/OPERATOR Configuration and Customization Guide V340

Overview

n Reroute the JCL so that it always references libraries on a specific volume. To do this,
uncomment the JOBPARM S=system_id statement near the top of the JCL member,
change the system identifier if needed, and submit the job.
n Run the JCL from the appropriate system.

Defaults for Customizer-Generated Members 177

Overview

178 AF/OPERATOR Configuration and Customization Guide V340

AF/Operator Libraries

B
Introduction
In a multi-system complex, some of the libraries allocated by the Customizer contain
address-space-specific information (for example, checkpoint datasets). Since such libraries
should not be shared, the Customizer allocates a set for each defined address space. Other
AF/OPERATOR libraries reside on shared DASD volumes for central reference.
This section describes the AF/OPERATOR shared libraries and the libraries allocated to each
defined address space.

AF/Operator Libraries 179

Library Listings

Libraries shared across the complex

The following AF/OPERATOR libraries are referenced by the Customizer.

Library Names Library Descriptions

rhilev.RKANCMD Command Library.
rhilev.RKANPAR AF/OPERATOR parameters
rhilev.@system.RKANSAM JCL Library.
rhilev.RKANBIN Object library.
rhilev.TKANMAC Assembly source library.
thilev.TKANMOD AF/OPERATOR load library.
thilev.TKANHENU AF/OPERATOR and POVI Help library.
svhilev.CSI SMP/E CSI.
thilev.TKANPENU POVI panel library.
thilev.TKANCMD POVI command library.
thilev.TKANISP OG*TSO ISPF environment library.

Since the JCL, command, and object datasets are runtime libraries, they are allocated by the
Customizer. During initialization, the Customizer determines if these libraries exist or are
cataloged. If any one of them is not cataloged, the Customizer will dynamically allocate it
using the runtime library information (high-level qualifier, volume serial number, and unit
type) supplied by the CICAT.

Library shared by address spaces

.rhilev.@system.RKANSAM is shared by all the AF/OPERATOR address spaces within the
system. When a new system is defined, this library is allocated automatically. When the
system is deleted, the library is deleted as well.

180 AF/OPERATOR Configuration and Customization Guide V340

Libraries Allocated for Each Defined Address Space

AF/OPERATOR datasets for each address space

The following datasets are required for each AF/OPERATOR address space. The DASD
message log datasets are required only if you specify the DISKMLOG=Y startup option.

Library Names Library Descriptions

rvhilev.@system##.RKOGCKP Checkpoint dataset.
rhilev.@system##.RKOGLH01 Historical log dataset.
rhilev.@system##.RKOGLH02 Historical log dataset.
rhilev.@system##.RKOGLMnn DASD message log datasets.

where system is a user-defined field of 1–4 characters in length (usually the SMFID), ## can
be alphanumeric and/or national characters, and nn can be 01–99.

POVI
The following supported datasets are allocated as part of the POVI customization. Each POVI
address space requires its own set of support datasets.

Library Names Library Descriptions

rhilev.POVIn.RKOGPARM User customized parameter library.
rvhilev.POVIn.RKOGNAM Network Access Manager database.
rvhilev.POVIn.RKOGTDB Table database.
rvhilev.POVIn.RKOGVLG View log database.

where n can be 0–9.

AF/Operator Libraries 181

Libraries Allocated for Each Defined Address Space

182 AF/OPERATOR Configuration and Customization Guide V340

Installing the REXX Alternate Library

C
Introduction
The Alternate Library enables users who do not have the IBM Library for SAA REXX/370
installed to run compiled REXX programs. It contains a language processor that transforms
the compiled programs and runs them with the REXX interpreter, which is part of TSO/E and
CMS.
The Alternate Library (HWJ9133) can be ordered directly from IBM free of charge, and must
be ordered if you wish to have a maintainable copy at your site. However, Candle provides a
non-maintainable copy of IBM’s Alternate Library (version 3, level 0) with AF/OPERATOR
Our tape contains two files, CANDLE.IBM.SEAGALT (the alternate library) and
CANDLE.IBM.SEAGSAM (the sample library) that are direct copies of the corresponding IBM
libraries.
If you choose to install the Alternate Library from Candle, you can do this using the
Customizer (option U) that restores these two data sets from tape to two DASD datasets. The
DASD datasets are called &hilev.SEAGALT and &hilev.SEAGSAM where &hilev is the
high-level qualifier you selected in the Customizer (option 0).

Compile Programming Table

The Compile Programming Table (CPT), IRXCMPTM, is the default module that specifies a
library to TSO/E. Since a default CPT is installed with TSO/E, you must install an updated
version of the CPT in order to use the Alternate Library.
An executable copy of IRXCMPTM (CPT) exists in CANDLE.IBM.SEAGALT, the Alternate
Library. You can place this executable copy directly into SYS1.LINKLIB, replacing the TSO/E
default CPT.
Note: If you are already using a modified CPT, you should exercise caution to ensure that
you maintain your existing modifications.
The user sample source for the IRXCMPTM program is provided in the
CANDLE.IBM.SEAGSAM dataset, in member EAGKUMOD. If you have a modified CPT,
then you probably already have a version of the program.

Installing the REXX Alternate Library 183

Activating the Alternate Library
For performance reasons, you should always use the IBM Library if it is available on your
system. The IBM library must reside in the Link Pack Area (LPA), and the Alternate Library
must reside in LINKLIST. Placing the Alternate Library in the LINKLIST prevents you from
overriding the IBM Library in the LPA.
If you do not have the IBM Library installed, you do not need to take any action to activate
the Alternate Library. It will be available after being installed and copied into the LINKLIST.

Messages
Use of the Alternate Library requires that REXX programs be compiled using the proper
options (ALTERNATE, SLINE, etc.) to ensure that the resulting modules are in a form that the
Alternate Library can use. If this is not done properly, the resulting program execution could
fail for a variety of reasons. Although there are many run-time messages that could indicate a
failure, the following messages are the most common:
FANENV0708T THE ALTERNATE OPTION REQUIRES THE SLINE OPTION
Explanation: When specifying the ALTERNATE compiler option, the SLINE option is
required. The Alternate Library cannot prepare the control blocks needed by the Interpreter if
the source of the REXX program is not included at compile time using the SLINE option.
User Response: Compile the REXX program again, specifying both the ALTERNATE and
SLINE compiler options.
FANENV0709W DLINK HAS NO EFFECT WHEN RUNNING WITH ALTERNATE
LIBRARY
Explanation: The DLINK option supports a direct link of an external subroutine or function
when a module is generated from OBJECT output. This option is supported by the IBM
Library but not the Alternate Library. The Alternate Library runs the compiled REXX program
by invoking the interpreter; the standard system search order is used.
User Response: When distributing compiled REXX programs, include the external
subroutines and functions that are directly linked by the IBM Library as separate modules for
the Alternate Library.
EAGREX0304I THE PROGRAM CANNOT RUN WITH THE ALTERNATE
LIBRARY
Explanation: The program has been compiled with the NOALTERNATE compiler option.
User Response: Compile your program with the ALTERNATE compiler option.

184 AF/OPERATOR Configuration and Customization Guide V340

Customizing Additional Utilities

D
Introduction
This appendix provides information about customizing utilities listed on the Additional
Utilities panel.

Customizing Additional Utilities 185

The Additional Utilities Panel

Displaying the Additional Utilities panel

Select item U from the Primary Customization Menu to display the Additional Utilities panel.

Vnnn ------------------- ADDITIONAL UTILITIES -----------------

OPTION ===>

Enter the selection number on the line above.

Program Description

R REXX - Install IBM Alternate Library for compiled REXX

1 AOSSFTBL - Subsystem function table

2 AOSSNTBL - Subsystem table name
3 AOSVCTBL - SVC name table
4 AOUSRSEC - Command security exit

Using utilities
When you type the appropriate selection number and press Enter, the Customizer generates a
batch job. You are given the opportunity to review and edit the job. The Customizer does
not submit the batch jobs. They are stored in your rhilev.@system.RKANSAM library.
Candle recommends that you generate the following miscellaneous utility jobs during
customization so they are available if you need them.

Utility Description
AOSSFTBL Subsystem function table
AOSSNTBL Subsystem table name
AOSVCTBL SVC name table
AOUSRSEC Command security exit

These utilities are further described in the sections that follow.

186 AF/OPERATOR Configuration and Customization Guide V340

AOSSFTBL

Introduction
The AOSSFTBL utility allows you to customize subsystem function descriptions.

CSECT name: AOSSFTBL

Load Module: KOGSHOPR
Type: DATA

Purpose
AOSSFTBL is used in one of the following ways:
n By a SHOW SSCTS command that assigns a descriptive text to each subsystem function
displayed in response to this command:
subsys SHOW SSCTS(namepattern) DETAIL
n By a SHOW SSCTS command specifying a list of subsystem functions used as selection
criteria.
The SHOW SSCTS command and its options are explained in the AF/OPERATOR
Command Reference Manual.

Syntax
AOSSFTBL consists of a series of macro calls that associate a subsystem function number
with a descriptive text string. The macro is @SSF. It requires two operands separated by a
comma: the subsystem function number and the text string. For example:
@SSF 1,’SO - PROCESS SYSOUT DATA SETS’

Implementation
Review and modify, if necessary, the default CSECT located in
thilev.TKANMAC(AOSSFTBL). Then review the JCL in the Customizer-generated member
AOSSFTBL to verify that it conforms to your installation standards. It is stored in the
rhilev.@system.RKANSAM library. Submitting this job receives and applies the USERMOD
TOGD001. Be sure to include thilev.TKANMAC in the SYSLIB concatenation for SMP/E
apply.
Note: Accepting the USERMOD ends your ability to restore the previous version. Verify the
return codes/messages and run a test by issuing the SHOW SSCTS command.

Customizing Additional Utilities 187

AOSSNTBL

Introduction
The AOSSNTBL utility allows you to customize subsystem name descriptions.

CSECT name: AOSSNTBL

Load Module: KOGSHOPR
Type: DATA

Purpose
AOSSNTBL is used by the SHOW SSCTS command to assign a descriptive name to each
4-character subsystem ID in your system. The 4-character name (as it appears in the SSCT)
can be specified in character or hex format. The descriptive name appears in response to the
command:
subsys SHOW SSCTS
The name appears with or without any of the other command options explained in the
AF/OPERATOR Command Reference Manual.

Syntax
AOSSNTBL consists of a series of macro calls that associate a subsystem name with a
descriptive text string. The macro is @SSN. It requires two operands separated by a comma:
the subsystem name pattern and the text string. For example:
@SSN C’JES?’,’JOB ENTRY SUBSYSTEM’

Implementation
Review and modify, if necessary, the default CSECT provided on the distribution tape in
thilev.TKANMAC(AOSSNTBL). Then review the JCL in the Customizer-generated member
AOSSNTBL to verify that it conforms to your installation standards. It is stored in the
rhilev.@system.RKANSAM library. Submitting this job receives and applies the USERMOD
TOGD002. Be sure to include thilev.TKANMAC in the SYSLIB concatenation for SMP/E
apply.
Note: Accepting the USERMOD ends your ability to restore the previous version.
Verify the return codes/messages and run a test by issuing the SHOW SSCTS command.

188 AF/OPERATOR Configuration and Customization Guide V340

AOSVCTBL

Introduction
The AOSVCTBL utility allows you to customize SVC names and descriptions.

CSECT name: AOSVCTBL

Load Module: KOGSHOPR
Type: DATA

Purpose
AOSVCTBL is used by the SHOW SVCS command to assign a descriptive name to each
3-digit SVC number in the range 000 through 255. The descriptive name appears in response
to this command:
subsys SHOW SVCS
The name appears with or without any of the other command options explained in the
AF/OPERATOR Command Reference Manual.

Syntax
AOSVCTBL consists of a series of macro calls that associate an SVC number with a
descriptive text string. The macro is @SVC. It requires two operands separated by a comma:
the SVC number and the text string. For example:
@SVC 000,’EXCP/XDAP’

Implementation
Review and modify, if necessary, the default CSECT provided on the distribution tape in
thilev.TKANMAC(AOSVCTBL). Then review the JCL in the Customizer-generated member
AOSVCTBL to verify that it conforms to your installation standards. It is stored in the
rhilev.@system.RKANSAM library. Submitting this job receives and applies the USERMOD
TOGD003. Be sure to include thilev.TKANMAC in the SYSLIB concatenation for SMP/E
apply.
Verify the return codes/messages and run a test by issuing the SHOW SVCS command.

Customizing Additional Utilities 189

AOUSRSEC

Introduction
The AOUSRSEC utility exit allows you to customize command security options.

CSECT name: AOUSRSEC

Load Module: AOSECURE
Type: EXIT

Purpose
AOUSRSEC enables you to impose security on AF/OPERATOR commands. It allows you to
n Unconditionally accept.
n Unconditionally reject.
n Prompt for a userid/password.
n Alter the command text for any command routed through AF/OPERATOR. (All
commands can be routed in this way.)

Structure
AOUSRSEC consists of assembler language instructions that examine the command being
executed. It compares the match authority with the command authority in KOGCDTBL.
AOUSRSEC receives information about the command issuer, and may require a password to
proceed or to override the user authority level. KOGCDTBL contains entries for all
AF/OPERATOR commands and their authority. The default authority for all matches is 255;
unless the user changes this authority, matches can issue any command. All commands have
authority 0 except the following:

Authority Command
10 TPUT
20 LET, WAIT, EXECUTE
40 OPER
80 AF, TRAP, ADDRESS, IMSOPER, JES3OPER, LOGON, LOGOFF, PEER, PEERLINK

If you want to use the exit external security, you can have AF/OPERATOR prompt for a user
ID and password by sending a return code of 16 from the exit. Then reinvoke the exit,
passing the replied information. The exit may now perform whatever security checking you
desire.

190 AF/OPERATOR Configuration and Customization Guide V340

AOUSRSEC

Input to this exit is a parameter list as follows:

Offset
(Decimal) Length Use
+0 4 Pointer to command buffer (2-byte length followed by text)
+4 4 Pointer to AF/OPERATOR command table entry
+8 4 Pointer to return message area (2-byte length followed by 255-byte
area)
+12 4 Pointer to jobname or user ID
+16 4 Pointer to 2-byte console ID or (if negative) ASID

+20 4 Pointer to 8-byte password area

+24 4 Pointer to 17-byte reply area containing the WTOR response for
userid/password
+28 1 Flag byte (includes exit reinvocation)

In addition, R0 contains the AUTH level currently assigned to this match.

The following fields may be modified by this exit:

Match authority level Return R15 = 4, R0 = AUTH level 0 through 255.

Command text Return R15 = 4, new text in command buffer.
Password Return R15 = 8, new text in password area.
Message area Byte 1 (length) not 0 causes message to be sent to user.

Return codes from this exit cause the following results:

0 Allow the command to execute.

4 Allow with AUTH and command text update.
8 Prompt for specified password; allow if correct response given.
12 Reject.
16 AF/OPERATOR issues a WTOR to prompt for a userid/password.

Customizing Additional Utilities 191

AOUSRSEC

Implementation
Review and modify, if necessary, the sample exit provided in thilev.TKANMAC(AOUSRSEC).
Then review the JCL in the Customizer-generated member AOUSRSEC to verify that it
conforms to your installation standards. It is stored in the rhilev.@system.RKANSAM library.
Submitting this job receives and applies the USERMOD TOGX001. Be sure to include
thilev.TKANMAC in the SYSLIB concatenation for SMP/E apply.
Note: Accepting the USERMOD ends your ability to restore the previous version.
Verify the return codes/messages and run a test.

192 AF/OPERATOR Configuration and Customization Guide V340

Checkpointing

E
Introduction
This appendix
n contains background information on checkpoint datasets
n lists the parameters and commands that control checkpointing
n explains how to estimate dataset space requirements if the default AF/OPERATOR VSAM
checkpoint dataset is not large enough for your needs

Checkpointing 193
Checkpoint Dataset

Checkpoint Dataset
A checkpoint dataset is a key-sequenced, VSAM dataset that allows you to checkpoint TODs
and user-defined system variables to a DASD dataset. Each time a user-defined variable is
added, changed, or deleted, AF/OPERATOR checkpoints this information.

Important
Checkpoint datasets cannot be shared among multiple copies of AF/OPERATOR.
Each AF/OPERATOR address space needs its own checkpoint dataset if you want
to checkpoint in that address space.

During your first startup of AF/OPERATOR, use the RELOAD(NONE) startup parameter in
order to reformat the checkpoint datasets. In subsequent startups you can use
RELOAD(TODS), RELOAD(VARS), RELOAD(RSVS), or a combination of TODS, VARS,
and/or RSVS, or just RELOAD(ALL).

194 AF/OPERATOR Configuration and Customization Guide V340

Checkpointing Facility

Overview
Checkpointing is optional. The checkpointing facility gives you the ability to perserve, across
AF/OPERATOR restarts, any time-of-day traps and system variables your site has defined.
The checkpointing facility writes all information about checkpointed variables and TOD traps
to a VSAM dataset, and maintains a record for each checkpointed item. When the value of a
checkpointed variable or the status of a checkpointed TOD trap changes, the facility updates
this information. After a product restart, checkpointing puts your system into the same state it
was in when it went down.

Enabling the checkpointing facility

If your site took the customization defaults at installation time, then your RKANPAR
(AF/OPERATOR initialization parameters) member contains the NOCKPT startup parameter,
and the checkpointing facility is disabled. If your RKANPAR member contains the CKPT
parameter, then the checkpointing facility is enabled at your site.

Defaults for checkpointing

Checkpointing defaults for your system are set by the following AF/OPERATOR startup
parameters:
n CKPT/NOCKPT
n TRAPDFLT
n RELOAD
n TODISYNC
If AF/OPERATOR is installed and running, you can determine the default settings for your
system by issuing the AF command with no operand.

TOD traps and checkpointing

Checkpointing of individual TOD traps is controlled by the following keywords on the TRAP
ADD TOD command:
n CATCHUP
n CKPT/NOCKPT
The TRAP ADD TOD command is documented in the AF/OPERATOR Command Reference
Manual.

Checkpointing user-defined system variables

A user-defined system variable is a variable defined with a scope of system through one of the
following:
n the DCL statement for command procedures, for example

Checkpointing 195
Checkpointing Facility

DCL MYSYSVAR CHAR(25) SYSTEM INIT(‘THIS IS A SYSTEM VARIABLE’)

n the SYSVPUT function for REXX execs, for example
MYSYSVAR = ‘THIS IS A SYSTEM VARIABLE’
RC = SYSVPUT(MYSYSVAR)
To checkpoint user-defined system variables, the CKPT startup parameter must be specified.
This activates the checkpointing facility.
If you want to restore your user-defined system variables at the next AF/OPERATOR restart,
you must also use the RELOAD startup parameter. This parameter specifies which type of
records you would like to restore/reload. If you want to restore only variables specify
RELOAD(VARS)

Checkpointing TOD traps

To checkpoint TOD traps, the CKPT startup parameter must be specified. This activates the
checkpointing facility.
If you want to restore TOD traps at the next AF/OPERATOR restart, you must also specify the
RELOAD startup parameter. This parameter specifies which type of objects you would like to
restore/reload. If you want to reload only TOD traps, specify
RELOAD(TODS)
Whether or not a TOD trap is checkpointed depends on the following:
n If the TRAPDFLT(CKPT(TOD)) startup parameter has also been specified then all TOD
traps will be checkpointed, unless explicitly overridden for each trap using the NOCKPT
option of the TRAP ADD TOD command.
To determine whether all TOD traps are checkpointed by default, issue the AF command.
This command displays several system settings. If the line
TRAPDFLT(........,CKPT(TOD)) is listed in the display, then your system is set to
checkpoint all TOD traps by default.
n If a trap is defined with the CKPT option of the TRAP ADD TOD command, as in the
following example:
TRAP ADD(MYTOD) TOD CKPT ........<other TOD trap keywords>
the trap will be checkpointed.
n If a trap is defined with the CATCHUP option of the TRAP ADD TOD command, as in the
following example:
TRAP ADD(MYTOD) TOD CATCHUP......<other TOD trap keywords>
it will be checkpointed.
Because CATCHUP needs the checkpointing facility to function, specifying CATCHUP on a
TOD trap means implicit checkpointing.
n If a TOD trap is defined with both the CATCHUP and NOCKPT options, the NOCKPT
option will be ignored.
To determine whether or not a particular TOD trap is checkpointed, issue the SHOW TRAP
command. The trap status information will show either CKPT or NOCKPT.

196 AF/OPERATOR Configuration and Customization Guide V340

Space Allocation

Introduction
The following information is for users who want to estimate checkpointing space allocation
requirements. However, the default allocation performed by the Customizer is sufficient in
most cases and need not be modified, particularly for new users.
The VSAM dataset was predefined with the DEFINE CLUSTER command. The checkpoint
dataset is a VSAM key-sequenced dataset (KSDS), and it is initialized with the REPRO
command.

Customization additions
Use the following information to determine how much space you will need for your VSAM
dataset.
n For each checkpointed record (TODS, VARS, or RSVS), AF/OPERATOR uses a minimum
of 28 bytes of information (including a 20-byte key). The remainder of the record
contains the user-defined value of the checkpointed record.
n The maximum length of a single record in the AF/OPERATOR checkpoint dataset is 32K
of information.
n AF/OPERATOR variables may be up to 255 bytes in length.
n The TOD checkpoint record is 580 bytes in length.
n There is no limit to the total size of the checkpoint dataset.
To estimate the average size of your checkpointed records and the number of records your file
will contain, use the following formulae:
Total Number of Records:

NR = Nc + Ni + Nx

where Nc = number of Character System variables

Ni = number of Integer System variables
Nx = number of Other Type System variables

Average Length of Records:

LR = ((Lc+28) * Nc) + ((Li+28) * Ni) + ((Lx+28) * Nx)

-----------------------------------------------------------------------------------
NR

where Lc = avg length of character variables

Li = avg length of integer variables (always 4)
Lx = avg length of other variables

Checkpointing 197
Space Allocation

Once you have determined the average record length and the average number of records per
file, refer to the IBM Administration Guide for information on space allocation requirements.
Allocate the cluster using NR and LR according to instructions in the VSAM manual.

198 AF/OPERATOR Configuration and Customization Guide V340

POVI and CT/Engine Element and

F Dataset Names

Introduction
AF/OPERATOR Version 340 POVI uses CT/Engine Version 180 as a base component. The
following lists describe the Programmerless Open VTAM Interface and CT/Engine libraries
and parameter member names.

POVI and CT/Engine Element and Dataset Names 199

Names and Name Changes

Candle-supplied POVI libraries

The following list describes the Candle-supplied Programmerless Open VTAM Interface
libraries for CT/Engine Version 180.

TKANCMD Programmerless Open VTAM Interface Command List Library

TKANHENU Programmerless Open VTAM Interface Help Library
TKANPAR Programmerless Open VTAM Interface Parameter Library
TKANPENU Programmerless Open VTAM Interface Panel Library

CT/Engine libaries
The following list describes the CT/Engine Version 180 libraries.

TKANCMD CT/Engine Command List Library

TKANPENU CT/Engine SSPL Panel and Help Library
TKANPAR CT/Engine Parameter Library
TKANSAM CT/Engine Sample Library
TKANMODL CT/Engine Load Module Library
RKLVLOG CT/Engine Master Event Log
RKLVSNAP CT/Engine Abnormal Event Log

CT/Engine TKANPAR parameter members

The following describes the CT/Engine Version 180 TKANPAR members.

KLVSYSIN CT/Engine Startup Parameters

KLVINNAM CT/Engine Network Access Manager
KLVINTB CT/Engine Table Access Manager
KLVINVLG CT/Engine View Log Parameters
KLVINNAF CT/Engine Network Accounting Facility
KLVINPSM CT/Engine Presentation Space Manager
KLVINSTG CT/Engine Storage Initialization Specifications
KLVINPO CT/Engine Program Operator Parameters

200 AF/OPERATOR Configuration and Customization Guide V340

Names and Name Changes

CT/Engine samples
The following lists the name changes for CT/Engine samples from Version 146 to Version
180.

Version 146 Name Version 180 Name Description

AMDUSR20 KLVUSR20 AMDPRDMP/IPCS GTF
Formatting Exit Source
ASMUSR20 KLV@AS20 KLVUSR20 Assembly and
Linkedit JCL
VTPA2NEV KLVA2NEV ACF2 Entry Validation Exit
Source

POVI and CT/Engine Element and Dataset Names 201

Names and Name Changes

202 AF/OPERATOR Configuration and Customization Guide V340

SMF Record Layout

G
Introduction
This appendix provides the layout of the SMF record.
Note: In the Offsets column, the first number is a decimal representation, while the
second is a hexadecimal representation.

Offsets Name Length/ Description

Dec/Hex Format
00 SSR_SMF_RECORD 294 Variable from 166 -- 294
00 SSR_SMF_HEADER 30 Standard SMF Record Header
00 SSR_RECORD_LENGTH 2 Binary Length of this Record
22 SSR_SEGMENT_DESC 2 Binary RDW Segment Descriptor
44 SSR_FLAGS 1 Binary SMF Processing Flags
55 SSR_RECORD_TYPE 1 Binary Type of SMF Record
66 SSR_EVENT_TIME 4 Packed 1/100ths Seconds Since Midnight
10 A SSR_EVENT DATE 4 Packed Date of Event (0CYYDDDF)
14 E SSR_LSYSNAME 8 EBCDIC
14 E SSR_SMF_ID 4 EBCDIC MVS SMF ID
18 12 SSR_SUBSYSTEM_ID 4 EBCDIC MVS SUBSYSTEM ID
22 16 SSR_RECORD_SUBTYPE 2 Binary Subtype ‘0’

24 18 SSR_OG_DATA
24 18 SSR_OG_JOB_NAME 8 EBCDIC Name of OG Job/Task

32 20 SSR_EVENT_DATA 134 Event-Related Data

SMF Record Layout 203

Offsets Name Length/ Description
Dec/Hex Format
32 20 SSR_EVENT_TYPE 4 EBCDIC Type of Event
n MATC Match Data
n EXEC Exec Data
n FILE File Data
n IMME Immediate Updates
36 24 SSR_EVENT_STAGE 4 EBCDIC Stage of Event
n STAR Match Start
n STOP Match Stop
n OPEN File Open
n CLOS File Close
n READ File Read
n WRIT File Write

40 28 SSR_MATCH_INFO
40 28 SSR_MATCH# 4 Binary Match Number
44 2C SSR_MATCH_TYPE 4 EBCDIC Match Type
n UNDF Undefined
n DOM Delete Outstanding Message
n TOD Time-of-Day
n CMD Command
n WTO Write to Operator
n WTL Write to Log
n OMVS OMEGAMON for MVS
n OCIC OMEGAMON for CICS
n ODB2 OMEGAMON for DB2
n OIMS OMEGAMON for IMS
n SCH Internally Scheduled
n NVI NetView
n COMM Communications
48 30 SSR_TRAP_NAME 24 EBCDIC Originating Trap Name
72 48 SSR_CPU_TIME_USED 4 Binary CPU Time Used (0.000S)
76 4C SSR_EXEC_NAME 8 EBCDIC Originating EXEC Name
84 54 SSR_CONS_NAME 8 EBCDIC Originating Console Name

92 5C SSR_FILE_INFO 72
92 5C SSR_DD_NAME 8 EBCDIC File DD Name
100 64 SSR_FILE_NAME 8 EBCDIC OG File Name

204 AF/OPERATOR Configuration and Customization Guide V340

Offsets Name Length/ Description
Dec/Hex Format
108 6C SSR_DATA_SET_NAME 44 EBCDIC Dataset Name
152 98 SSR_MEMBER_NAME 8 EBCDIC Member Name
160 A0 SSR_RECORD_CNT 4 Binary Accumulative Record Count

92 5C SSR_IMM_INFO 72 Immediate Updates Event Type

92 5C SSR_IMM_SUPP_FLAG 1 EBCDIC Suppressed? (Y/N)
93 5D SSR_IMM_ROUT_FLAG 1 EBCDIC Route Change? (Y/N)
94 5E SSR_IMM_HCOPYSUPP 1 EBCDIC Hard copy suppressed? (Y/N)
95 5F SSR_IMM_HCOPYFORC 1 EBCDIC Hard copy forced? (Y/N)
96 60 SSR_IMM_NEWSYS 8 EBCDIC New System ID
104 68 SSR_IMM_NEWCONS 8 EBCDIC New Console Name
112 70 SSR_IMM_OLDDESC 4 Binary Old Description Codes
116 74 SSR_IMM_NEWDESC 4 Binary New Description Codes
120 78 SSR_IMM_OLDROUT 16 Binary Old Route Codes
136 88 SSR_IMM_NEWROUT 16 Binary New Route Codes
152 98 12 Reserved

164 A4 SSR_TEXT_INFO Command or WTO Information

164 A4 SSR_TEXT_LEN 2 Binary Actual Length of WTO
166 A6 SSR_TEXT 128 EBCDIC Variable Length Text Area

SMF Record Layout 205

206 AF/OPERATOR Configuration and Customization Guide V340
Guide to Candle

H Customer Support

Introduction
Candle Corporation is committed to producing top-quality software products and
services. To assist you with making effective use of our products in your business
environment, Candle is also committed to providing easy-to-use, responsive customer
support.
Precision, speed, availability, predictability—these terms describe our products and
Customer Support services.
Included in this Guide to Candle Customer Support is information about the following:
Base Maintenance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
– Telephone Support
– eSupport
– Description of Severity Levels
– Service-level objectives
– Recording and monitoring calls for quality purposes
– Customer Support Escalations
– Above and Beyond
Enhanced Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
– Assigned Support Center Representative (ASCR)
– Maintenance Assessment Services (MAS)
– Multi-Services Manager (MSM)
Customer Support Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
– Link to Worldwide Support Telephone and E-mail information

Guide to Candle Customer Support 207

Base Maintenance Plan

Overview
Candle offers a comprehensive Base Maintenance Plan to ensure that you realize the
greatest value possible from your Candle software investments. We have more than 200
technicians providing support worldwide, committed to being responsive and to
providing expedient resolutions to support requests. Technicians are available worldwide
at all times during the local business day. In the event of an after-hours or weekend
emergency, our computerized call management and forwarding system will ensure that a
technician responds to Severity One situations within one hour. For customers outside of
North America, after-hours and weekend support is provided in English language only by
Candle Customer Support technicians located in the United States.

Telephone support
Candle provides consistently reliable levels of service—thanks to our worldwide support
network of dedicated experts trained for specific products and operating systems. You will
always work with a professional who truly understands your problem.
We use an online interactive problem management system to log and track all
customer-reported support requests. We give your support request immediate attention
by routing the issue to the appropriate technical resource, regardless of geographic
location.
Level 0 Support is where your call to Candle Customer Support is first handled.
Your support request is recorded in our problem management system, then
transferred to the appropriate Level 1 support team. We provide Level 0 manual
interaction with our customers because we support more than 170 products. We feel
our customers would prefer personal interaction to a complex VRU or IVR selection
menu.
Level 1 Support is the service provided for initial support requests. Our Level 1
team offers problem determination assistance, problem analysis, problem resolutions,
installation assistance, and preventative and corrective service information. They also
provide product usage assistance.
Level 2 Support is engaged if Level 1 cannot provide a resolution to your problem.
Our Level 2 technicians are equipped to analyze and reproduce errors or to
determine that an error is not reproducible. Problems that cannot be resolved by
Level 2 are escalated to Candle’s Level 3 R&D support team.
Level 3 Support is engaged if a problem is identified in Candle product code. At
Level 3, efforts are made to provide error correction, circumvention or notification
that a correction or circumvention is not available. Level 3 support provides available
maintenance modifications and maintenance delivery to correct appropriate
documentation or product code errors.

208 AF/OPERATOR Configuration and Customization Guide V340

Base Maintenance Plan

eSupport
In order to facilitate the support process, Candle also provides eSupport, an electronic
full-service information and customer support facility, using the World Wide Web at
www.candle.com/support/. eSupport allows you to open a new service request and
update existing service requests, as well as update information in your customer profile.
New and updated service requests are queued to a support technician for immediate
action. And we can respond to your request electronically or by telephone—it is your
choice.
eSupport also contains a continually expanding knowledge base that customers can tap
into at any time for self-service access to product and maintenance information.
The Candle Web Site and eSupport can be accessed 24 hours a day, 7 days a week by
using your authorized Candle user ID and password.

Description of Candle severity levels

Responses to customer-reported product issues and usage questions are prioritized within
Candle according to Severity Code assignment. Customers set their own Severity Levels
when contacting a support center. This ensures that we respond according to your
individual business requirements.
Severity 1 A crisis affects your ability to conduct business, and no procedural
Crisis workaround exists. The system or application may be down.
Severity 2 A high-impact problem indicates significant business effect to you. The
High program is usable but severely limited.
Severity 3 A moderate-impact problem involves partial, non-critical functionality loss or
Moderate a reasonable workaround to the problem. A “fix” may be provided in a future
release.
Severity 4 A low-impact problem is a “how-to” or an advisory question.
Low
Severity 5 This is a request for software or documentation enhancement. Our business
Enhancement units review all requests for possible incorporation into a future release of the
Request product.

Guide to Candle Customer Support 209

Base Maintenance Plan

Candle has established the following service-level objectives:

Call Status Severity 1 Severity 2 Severity 3 Severity 4 Severity 5

Goal Goal Goal Goal Goal
First Call Time to 90% within one minute
Answer
Level 1 Response 90% within 90% within one hour
(Normal Business 5 minutes
Hours)
Level 2 Response Warm 90% within 90% within eight hours
(Normal Business Transfer two hours
Hours)
Scheduled Hourly or as Daily or as Weekly or as agreed Notification is
follow-up agreed agreed made when an
(status update) enhancement is
incorporated
into a generally
available
product.
Notification is made when a fix is incorporated into a generally available
product.
The above information is for guideline purposes only. Candle does not guarantee or warrant the above service levels. This information is
valid as of October 1999 and is subject to change without prior notice.

Recording and Monitoring Calls for Quality Purposes

Candle is committed to customer satisfaction. To ensure that our customers receive high
levels of service, quality and professionalism, we’ll monitor and possibly record incoming
and outgoing Customer Support calls. The information gleaned from these calls will help
us serve you better. If you prefer that your telephone call with Candle Customer Support
in North America not be monitored or recorded, please advise the representative when
you call us at (800) 328-1811 or (310) 535-3636.

Customer Support Escalations

Candle Customer Support is committed to achieving high satisfaction ratings from our
customers. However, we realize that you may occasionally have support issues that need
to be escalated to Candle management. In those instances, we offer the following simple
escalation procedure:
If you experience dissatisfaction with Candle Customer Support at any time, please
escalate your concern by calling the Candle support location closest to you. Ask to speak
to a Customer Support manager. During standard business hours, a Customer Support
manager will be available to talk with you or will return your call. If you elect to hold for a
manager, you will be connected with someone as soon as possible. If you wish a return
call, please tell the Candle representative coordinating your call when you will be
available. After contacting you, the Customer Support manager will develop an action
plan to resolve your issue. All escalations or complaints received about support issues are
logged and tracked to ensure responsiveness and closure.

210 AF/OPERATOR Configuration and Customization Guide V340

Base Maintenance Plan

Above and Beyond

What differentiates Candle’s support services from our competitors? We go the extra mile
by offering the following as part of our Base Maintenance Plan:
n Unlimited multi-language defect, installation and operations support
n eSupport using the World Wide Web
n Regularly scheduled product updates and maintenance provided at no additional
charge
n Over 200 specialized technicians providing expert support for your Candle products

Guide to Candle Customer Support 211

Enhanced Support Services

Overview
Our Base Maintenance Plan provides a high level of software support in a packaged
offering. However, in addition to this plan, we have additional fee-based support services
to meet unique customer needs.
The following are some examples of our added-value support services:
n Assigned Support Center Representative Services (ASCR)
– An assigned focal point for managing support escalation needs
– Proactive notification of available software fixes
– Proactive notification of product version updates
– Weekly conference calls with your ASCR to review active problem records
– Monthly performance reviews of Candle Customer Support service levels
– Optional on-site visits (extra charges may apply)
n Maintenance Assessment Service (MAS)
– On-site assessment services
– Advice about product maintenance and implementation
– Training your staff to develop efficient and focused procedures to reduce overall
cost of ownership of your Candle software products
– Analysis of your Candle product environment: versions, updates, code correction
history, incident history and product configurations
– Reviews to ensure that purchased Candle products and solutions are used
effectively
n Multi-Services Manager (MSM)
Multi-Services Manager provides highly valued services to customers requiring on-site
full time expertise to complement their technical resources.
– Dedicated on-site Candle resource (6 months or one year) at your site to help
ensure maximum use and effectiveness of your Candle products
– Liaison for all Candle product support activities, coordination and assistance with
implementation of all product updates and maintenance releases
– Works with your staff to understand business needs and systems requirements
– Possesses technical and systems management skills to enhance your staff’s
knowledge and expertise
– Other projects as defined in Statement of Work for MSM services

212 AF/OPERATOR Configuration and Customization Guide V340

Customer Support Contact Information

Link to Worldwide Support Telephone and E-mail information

To contact Customer Support, the current list of telephone numbers and e-mail addresses
can be found on the Candle Web site, www.candle.com/support/.
Select Support Contacts from the list on the left of the page.

Guide to Candle Customer Support 213

Customer Support Contact Information

214 AF/OPERATOR Configuration and Customization Guide V340

Index

Symbols installing REXX Alternate Library 131

$$OGINIT verification of required customization 132
executing 92 verifying installation 132
rerunning 112 Allocate Support Datasets
verifying for AF/OPERATOR user interface 132 manual tasks 90
allocate support datasets
Numerics description 28
worksheet 46
1-CHAR ID field (CICS) 53
allocated
1-CHAR ID field (IMS) 56
for AF/OPERATOR address spaces 181
for POVI 181
A Alternate Library, REXX 131, 183
abend limit AONOJES, replacement for 102
CMD 135 AOSIM 166
command 135 AOSIM alert facility
WARNING 135 with IMS 54
WTO 135 with JES3 65
ABENDLIM parameter 135 AOSSFTBL utility 187
accessing AOSSNTBL utility 188
the Customizer 84 AOSVCTBL utility 189
after batch installation 85 AOTRAP 169
additional utilities 31 AOUSRSEC utility 190
Additional Utilities panel 186 AOVTPLU0 73
address space command 136
alternate name 147 AOVTPOOL 71, 77
datasets 37 command 136
defining 39 APF authorization 91
ID field 39 APPC
address space coexistence confirmation protocols 153
AOSIM 166 integrity options 153
command qualification 165 Applications 30
NetView PPI 166 applications customization 30
subsystem event processing 165 ARM
ADMIN authority command 136
POVI 109 ASCR
Adobe portable document format 11 assigned support center representative 212
AF/OPERATOR ASID parameter 169
generating the logon program 130 assigned support center representative
populating runtime table library 131 ASCR 212
specifying logon program dataset automatic restart management (ARM) 136
output REXX dataset name 131
updating runtime ISPF tables 131
B
using the Customizer 130
batch installation, accessing the Customizer 85
AF/OPERATOR for MVS field 39
batch jobs after exiting Customizer
AF/OPERATOR load library (via STEPLIB) field 46
JCL 175
AF/OPERATOR STEPLIB 104
remote 176
AF/OPERATOR user interface
utilities 176

Index 215
virtual terminal interface 176 connecting to VTAM 148
console definition 140
C CONSOLE ID(0) parameter 140
CACHE CPU limit 140
command 137 CPULIM parameter 140
Candle Installation and Configuration Assistance creating backup datasets for 82
Tool. (CICAT) CT/Engine 200
See CICAT defining high-level qualifier 108
checkpointing i2.V180 library names 200
activating/deactivating 138 CT/Engine V180 name changes 201
dataset 194 CUA OPERATOR APPL field 78
defaults 195 customer support
enabling 195 base maintenance plan 208
facility 195 contact information 213
restoring data 155 enhanced support services 212
space allocation 197 eSupport 209
TOD traps 196 severity levels 209
keywords 195 telephone support 208
user-defined system variables 195 customization
CICAT after initialization 108
accessing after using batch installation 85 considerations 35
customizing AF/OPERATOR 130 JES 28
defined 18 optional 30
using 18 manual 94
CICAT Main Menu 84 prerequisites 24
CICS Interface process 19
manual customization 98 recommendations 24
preparing to customize 51 required 26 , 29
reason to install 31 sequence 23
Version 2 51, 98 status
Version 3 or 4 52, 99 progress 114
worksheet 52 verification of for AF/OPERATOR user
CICS load library field 53 interface 132
CICS MACRO libraries field 53 verifying 29
CICS Version field 53 Customization Considerations 24
CID(0) parameter 140 importance 22
CKPT parameter 138 customization considerations 35
CMD parameter 138 Customizer 18, 19, 20, 23, 26, 84, 87
cold starting AF/OPERATOR 127 for AF/OPERATOR 17, 130
Command libraries field 46 customizer defaults 135
COMMAND parameter 127, 138 customizing applications 30
compiled REXX 131, 183
complex D
defining the systems 26 DASD
definition 18 accessibility 18
sample 19 Dataset field (startup) 42
Complex Overview panel 114 dataset name
blue status 115 AF/OPERATOR 131
green status 115 datasets
red status 115 naming standards 35, 46
yellow status 115 supporting 35
concurrent jobs 148 default
CONFIRM(n) 109 JCL 175

216 AF/OPERATOR Configuration and Customization Guide V340

utility 176 the task list 29
defaults
AF/OPERATOR startup parameters 135 H
for customization 35 help 35
define address space environment 42 Customization Considerations 24
Define Address Spaces Help facility 20
description 27
Help facility 20
define address spaces
High-level qualifier field (POVI) 76
worksheet 39
HOSTNAME parameter 142
Define Startup Parameters
HOSTNAME table, trusted 111
description 28
define startup parameters defining 81
worksheet 42
Define Systems in Complex I
description 26 IATUX18 exit driver 64
define systems in complex IATUX31 exit driver 64
worksheet 36 IMS Interface
Description field (POVI) 75, 79 manual customization 100
Disk unit type field (JES3) 67 preparing to customize 54
Disk volume field (JES3) 67 reason to install 31
DISKMLOG parameter 141 worksheet 56
DUB_AS_PROCESS parameter 140 IMS RESLIB field 56
IMS Transaction Execution Interface function
E required configuration 59
error messages 127 IMS/VS
eSupport migration consideerations for 172
customer support 209 IMSCMD
exec used to issue transactions 63
KOGOCMDS 164, 165, 168 IMSCMD function 63
passing arguments 155, 156 required configuration 59
exiting the Customization 87 Include user exit field (IMS) 56
Include user exit field with KABJ3X18 (JES3) 67
Include user exit field with KABJ3X31 (JES3) 67
F
Include user exit with AODSIX01 (NetView) 70
FLOODCNTL 141
Include user exit with AODSIX06 (NetView) 70
for AF/OPERATOR
Include user exit with AODSIX11 (NetView) 70
accessing 84
INITDATA field (POVI) 79
components
initial command 127
exiting 87
initialization 42, 138
process 19, 23
installation, batch
required steps 26
accessing the Customizer 85
restarting 20
installing optional features 30
for AO/OPERATOR
Introduction 90
constraints 18
for OG/MVS
exiting 87 J
restarting 20 JCL default libraries 175
JES Customization
G description 28
Generate Startup Procedure JES customization 90
description 28 worksheet 41
worksheet 46 JES type field 37
generating JES2 MACRO libraries field 41
the AF/OPERATOR logon program 130 JES2 offset table field 41

Index 217
JES3 Command and WTO Exits MACRO libraries field (NetView) 70
manual customization 90, 101 Macro libraries field (POVI) 76
preparing to customize 64 MACRO libraries fields 56
JES3 command and WTO exits main menu 22
worksheet 67 maintenance assessment service
JES3 Interface, reason to install 31 MAS 212
JES3 load library field 67 manual customization 106
JES3 MACRO libraries field 41 trusted HOSTNAME table
JES3 offset table filed 41 defining TCP/IP hosts 111
JES3, running AF/OPERATOR without MAS
manual customization 102 maintenance assessment service 212
JESTBL parameter 142 matches
job origination 154 concurrent 148
jobs, concurrent 148 maximum 148
JOURNAL parameter 143 MAXJOBS parameter 148
journaling 82 MAXMAT parameter 148
MAXRUN 148
K MAXTRP parameter 149
KABIMX02 54 Member field (startup) 42
KAORSTRT command 132 message log 141
KOGIMXCC 54 messages
archiving 141
KOGOCMDS REXX exec 164, 165, 168
attributes 152
error 127
L lost 153
layout, SMF record 203 maximum 152
libraries 175, 176, 180, 181, 200, 201 origination 154
default timeout 153
virtual terminal interface 176
trapping 161
panel specification 18
migration 164, 165, 166, 167, 168, 169, 201
library name changes
considerations for IMS/VS 172
CT/Engine samples 201
multiple address space
limitations of the Customizer 18
MSMF links 170
LINKDEFS parameter 147
MSMF trapping by LINKID 170
LINKID parameter 147, 170
multiple MVS images 170
logging off 87
preventing loops 171
Logmode Table for VTAM-connected optional
started task requirements 166
features
description 68 MLWTO parameter 150
logmode table for VTAM-connected optional features MPFOPTS parameter 151
worksheet 68 MSGDFLT parameter 152
Logmode table name field 68 MSGLIM 152
logmode table name, manual customization 110 MSM
logon multi-services manager 212
program for AF/OPERATOR 130 MSMF APPLID field 69
LOGON data field (POVI) 79 MSMF FOCAL POINT parameter 153
LOGON_RESPTIME parameter 148 MSMF INTEGRITY parameter 153
LOGONTLM parameter 148 MSMF Interface
MSMF FOCAL POINT parameter 153
looping 140
MSMF. (MSMF) Interface
LPA 104
MSMF INTEGRITY parameter 153
multiple address space 165, 167
M AOTRAP 169
MACRO libraries field (JES3) 67 command qualification 168

218 AF/OPERATOR Configuration and Customization Guide V340

prioritizing automation 169 defining the trusted HOSTNAME table 81
separating automation 167 OSYSNAME parameter 154
single MVS image 167 output dataset (REXX)
subsystem event processing 167 for AF/OPERATOR 131
support 20, 27 Overview 30, 130
multiple MVS images 170
multi-services manager P
MSM 212 panels
Multi-System Management Facility (MSMF) Interface Additional Utilities 186
reason to install 31 CICAT Main Menu 84
worksheet 69 Complex Overview panel 114
Multi-System Management Facility(MSMF) Interface Primary Customization Menu 84
MSMF APPLID field 69 main menu 22
MVS console definition 140 System Overview panel 117
MVS subsystem name 158 System Overview panel (POVI panel 1) 120
MVS version field 37 System Overview Panel (POVI panel 2) 122
parameter members, TKANPAR 200
N parameters
NAM field (POVI) 77 defining 28
name changes parameter definition 133
CT/Engine samples 201 PLAYBACK Manager field 78
naming conventions 35 POVI
NetView Interface 166 See Programmerless Open VTAM Interface (POVI)
enabling console communication 105 setting ADMIN authority 109
worksheet 70 POVI address spaces 106
Netview Interface POVI shutdown confirmation 109
manual customization 104 POVI, starting 109
reason to install 31 POVI, stopping 109
NetView load library field 70 POVITRGC parameter 154
NOCKPT parameter 138 Primary Customization Menu 22, 84
non-interactive transactions printing problems 11
using IMSCMD to issue 63 processing time 140
non-VSAM disk unit type field 37, 39, 75 Programmerless Open VTAM Interface (POVI) 108,
non-VSAM disk volume serial field 37 , 39, 75 200
Non-VSAM SMS management class field 38 Candle-supplied libraries 200
non-VSAM SMS management class field 39, 75 CT/Engine samples
Non-VSAM SMS storage class field 38 V180 name changes 201
non-VSAM SMS storage class field 39, 75 Description field 75, 79
High-level qualifier field 76
O manual customization 108
OG*TSO 29, 30 NAM field 77
OMEGAMON Interface pre-customization 74
manual customization 106 reason to install 31
reason to install 31 security
worksheet 72 customization 18
OMEGAVIEW Interface Security system field 76
reason to install 31 System field 75
OMEGAVIEW interface TABLEDB field 77
worksheet 73 trigger 154
OPERATOR APPL field 78 virtual terminal support 106
OPERRESP parameter 153 worksheets 75
optional customization 30

Index 219
R the Customizer 84
record layout, SMF 203 starting POVI 109
RECORDING Manager field 78 startup 28, 133
relative order, alternate name 156 parameters 42
RELOAD parameter 155 Customizer defaults 135
Required Customization procedure 46
manual tasks symbol substitution in RKANPAR during 135
Overview 90 Startup Parameters
required customization LOGON_RESPTIME 148
overview 26 MSMF Focal Point 153
required final customization 29 startup parameters
restarting the Customizer 20 AOVTPLU0
Result 131 AOVTPOOL 136
REXX 131, 155, 156, 164, 165, 168 ARM 136
Alternate Library 131, 183 CACHE 137
compiled 131, 183 FLOODCNTL 141
Runtime Library 131, 183 status of customization 114
REXXARGS parameter 155 STC name filed 42
REXXOUT parameter 156 STEPLIB/LINKLIST 90
RKANPAR member 153 stopping AF/OPERATOR 128
RKANPAR, system symbols used in 135 stopping POVI 109
RKOGLOGM 127 SUBSYS parameter 158, 165, 168, 170
RO parameter 27, 156, 167, 170 Subsystem Logging Facility
route code 9 reply suppression 156 defining backup datasets for journaling 82
RSV pool defining clusters 82
manual customization optional customization 82
enabling 95 subsystem, alternate name 158
RTCD9_REPLY_SUPPRESSION parameter 156 support
runtime ISPF tables for AF/OPERATOR, coexistence 165
updating 131 single MVS image 167
Runtime Library, REXX 131, 183 support dataset allocation 28, 90
RXSEARCH parameter 157 suppression, route code 9 reply 156
SYSID parameter 159, 169, 170
S SYSOUT class field 53
Security system field (POVI) 76 Sysplex RSV pool
manual customization
severity levels
enabling 95
customer support 209
shared system 169
across complex 180 alternate name 159
by address spaces 180 datasets 37
single address space defining address spaces 27
command qualification 164 field 37, 75
SMF record layout 203 system LNKLST 104
SMFID 37 System Managed Storage (SMS)
SMS Customizer support 18
See System Managed Storage (SMS) specifying 36
space allocation 197 System Overview panel 117
specifying System Overview panel (POVI panel 1) 120
output REXX dataset name for AF/OPERATOR System Overview Panel (POVI panel 2) 122
AF/OPERATOR logon program dataset 131 system symbols used in RKANPAR 135
started task name field 39, 75
starting T
AF/OPERATOR 126 table library

220 AF/OPERATOR Configuration and Customization Guide V340

for AF/OPERATOR 131 required customization 29, 92
TABLEDB field (POVI) 77 VIRT TERM COUNT field (POVI) 79
TCP/IP VIRT TERM PREFIX field (POVI) 78
defining the trusted HOSTNAME table 81 Virtual Terminal Count field 72, 77
TCP/IP hosts Virtual terminal count field 73
defining for trusted HOSTNAME table 111 Virtual Terminal Prefix field 72 , 77
telephone support Virtual terminal prefix field 73
customer support 208 virtual terminals
time-of-day (TOD) traps OMEGAMON 72, 73, 75, 76, 77, 78, 79
restoring 155 OMEGAVIEW 73
storing in checkpoint dataset 159 POVI 77, 78, 79
TKANPAR members 200 VSAM disk unit type field 38, 39, 75
TODISYNC parameter 159 VSAM disk volume serial field 38, 39 , 75
Transaction Execution Interface, IMS 59 VSAM SMS management class field 38, 40, 75
transactions VSAM SMS storage class field 38 , 40, 75
using IMSCMD to issue 63 VTAM
TRAPDFLT parameter 160 connection 148
TRAPRESP parameter 161 major node field 37
traps manual customization 103
attributes 160 VTAM applications, such as OMEGAMON 106
maximum 149 VTAM APPLID field (POVI) 79
multi-line WTOs 150 VTAMLIB field 68
trusted HOSTNAME table
defining TCP/IP hosts 111
trusted HOSTNAME table, defining 81
W
Will your site include its own JES3 Command exit
(Exit driver IATUX18) in addition to
U Candle’s? 67
undefined text 161 WORK UNIT field 53
UNDFTEXT parameter 161 worksheet
User exit library field 56, 70 allocate support datasets 46
user exits CICS Interface 52
KOGIMXCC define address spaces 39
KABIMX02 54 define startup parameters 42
user interface logon program define systems in complex 36
for AF/OPERATOR 130
Generate Startup Procedure 46
using
IMS Interface 56
the Customizer
JES customization 41
CICAT for AF/OPERATOR 130
utilities JES3 command and WTO exits 67
AOSSFTBL 187 logmode table for VTAM-connected optional
features 68
AOSSNTBL 188
MSMF (Peer-to-Peer) node 69
AOSVCTBL 189
NetView Interface. 70
AOUSRSEC 190
OMEGAMON interface 72
OMEGAVIEW 73
V POVI 75
variables WTO handling 151
AOSYSID
WTOR, route code 9 reply suppression 156
AOTASKAS 169
verifying
AF/OPERATOR user interface. installation 132
optional customization 31
required AF/OPERATOR user interface
customization 132

Index 221

zOSV2R3 - MVS Program Management - User's Guide and Reference - IBM - 2017
No ratings yet
zOSV2R3 - MVS Program Management - User's Guide and Reference - IBM - 2017
258 pages
Esp Doc
No ratings yet
Esp Doc
51 pages
Connect Direct
No ratings yet
Connect Direct
128 pages
Changeman Administrator Guide
100% (3)
Changeman Administrator Guide
228 pages
CONTROL-M For zOS User Guide
No ratings yet
CONTROL-M For zOS User Guide
996 pages
Connect Direct For Windows
No ratings yet
Connect Direct For Windows
68 pages
CA-Easytrieve Plus - 6.4 - Reference Guide
100% (1)
CA-Easytrieve Plus - 6.4 - Reference Guide
563 pages
CA 7 Complete Commands
No ratings yet
CA 7 Complete Commands
664 pages
CNTRL M
No ratings yet
CNTRL M
885 pages
File Transfer in Rumba Mainframes
No ratings yet
File Transfer in Rumba Mainframes
17 pages
Connect Direct UsersGuide40
No ratings yet
Connect Direct UsersGuide40
128 pages
Ibm Websphere MQ (MQ Series) in A Nutshell: (Prepared by Channu Kambalyal)
No ratings yet
Ibm Websphere MQ (MQ Series) in A Nutshell: (Prepared by Channu Kambalyal)
4 pages
Endevor User Training Guide
100% (1)
Endevor User Training Guide
43 pages
MQSeries Architecture - Generali
No ratings yet
MQSeries Architecture - Generali
13 pages
IMS DC - Details
No ratings yet
IMS DC - Details
117 pages
MVS Messages
No ratings yet
MVS Messages
872 pages
Gnana Prasad Gopathi
No ratings yet
Gnana Prasad Gopathi
7 pages
ESP Codes and Messages
100% (1)
ESP Codes and Messages
1,720 pages
Tivoli NetView
No ratings yet
Tivoli NetView
9 pages
ISPW Part 2 Test Drive ISPW Change A Cobol PGM With Content Assist
No ratings yet
ISPW Part 2 Test Drive ISPW Change A Cobol PGM With Content Assist
47 pages
CA7 Workload Automation RefGd
0% (1)
CA7 Workload Automation RefGd
378 pages
Cobol Reference
No ratings yet
Cobol Reference
767 pages
S33 ATechnicalIntroductiontoCICSTransactionGatewayV6
No ratings yet
S33 ATechnicalIntroductiontoCICSTransactionGatewayV6
31 pages
Sysview Admin ENU
No ratings yet
Sysview Admin ENU
553 pages
VTAM Operations
No ratings yet
VTAM Operations
679 pages
IMS DC Programming
No ratings yet
IMS DC Programming
615 pages
Total Supra DML
No ratings yet
Total Supra DML
17 pages
NatStar v7 2011
No ratings yet
NatStar v7 2011
12 pages
ChangeMan DS User Guide
No ratings yet
ChangeMan DS User Guide
496 pages
DFSMSHSM Primer
No ratings yet
DFSMSHSM Primer
396 pages
IBM Debugger Trng1
No ratings yet
IBM Debugger Trng1
31 pages
SDSF For JES3
No ratings yet
SDSF For JES3
126 pages
ROSCOE - B001673e - Programs and Utilities Guide
No ratings yet
ROSCOE - B001673e - Programs and Utilities Guide
326 pages
CL Commands Vii
No ratings yet
CL Commands Vii
338 pages
ESP Scheduling Manual For Z/os
100% (2)
ESP Scheduling Manual For Z/os
634 pages
B3 Debuging IMS 200902
No ratings yet
B3 Debuging IMS 200902
37 pages
ZEKE Scheduling Tool Guide
No ratings yet
ZEKE Scheduling Tool Guide
52 pages
CL Commands III
No ratings yet
CL Commands III
890 pages
Program Directory For Websphere MQ For Z/Os
No ratings yet
Program Directory For Websphere MQ For Z/Os
68 pages
AdministrationGuide Ioa514ag
No ratings yet
AdministrationGuide Ioa514ag
1,018 pages
ISPF Questions
No ratings yet
ISPF Questions
10 pages
Solaris To Linux Migration
No ratings yet
Solaris To Linux Migration
450 pages
CA-idms Ads Alive User Guide 15.0
No ratings yet
CA-idms Ads Alive User Guide 15.0
142 pages
Mvs Commands
No ratings yet
Mvs Commands
2 pages
Omegamon Db2 Classic
100% (1)
Omegamon Db2 Classic
634 pages
NS TrafficMgmt Guide
100% (1)
NS TrafficMgmt Guide
798 pages
NS AppFirewall Guide
No ratings yet
NS AppFirewall Guide
396 pages
NS GSG en
No ratings yet
NS GSG en
142 pages
Citrix Netscaler Installation and Configuration Guide - Volume 1
No ratings yet
Citrix Netscaler Installation and Configuration Guide - Volume 1
866 pages
Vsphere - Perf - Exchange - Comparing Performance of iSCSI and NFS Storage-Protocols With and Wo Jumbo Frames
No ratings yet
Vsphere - Perf - Exchange - Comparing Performance of iSCSI and NFS Storage-Protocols With and Wo Jumbo Frames
10 pages
Orbix Mainframe: Artix Transport User's Guide
No ratings yet
Orbix Mainframe: Artix Transport User's Guide
144 pages
NS Admin Guide
No ratings yet
NS Admin Guide
124 pages
NS Networking Guide
No ratings yet
NS Networking Guide
234 pages
Networking
No ratings yet
Networking
91 pages
NS TrafficMgmt Guide PDF
No ratings yet
NS TrafficMgmt Guide PDF
770 pages
Mod05 GL Maint
No ratings yet
Mod05 GL Maint
38 pages
SPM Operation Guide
No ratings yet
SPM Operation Guide
54 pages
NovellPress Novell Certified Linux Professional Course 3057 Novell SUSE LINUX Network Services Training Book
No ratings yet
NovellPress Novell Certified Linux Professional Course 3057 Novell SUSE LINUX Network Services Training Book
520 pages
Manual CMC
No ratings yet
Manual CMC
468 pages
Getting Started 2 3 PDF
No ratings yet
Getting Started 2 3 PDF
34 pages
Workshop - Week 8 Mysql Practical Exercise
No ratings yet
Workshop - Week 8 Mysql Practical Exercise
3 pages
Inner Product Spaces Explained
No ratings yet
Inner Product Spaces Explained
11 pages
Lesson 3 Performing Security Assessments
No ratings yet
Lesson 3 Performing Security Assessments
15 pages
Linear Programming & Optimization Quiz
No ratings yet
Linear Programming & Optimization Quiz
4 pages
Rational vs. Irrational Inequalities
No ratings yet
Rational vs. Irrational Inequalities
13 pages
Letter 5G FWA Policy 08.04.2025
No ratings yet
Letter 5G FWA Policy 08.04.2025
24 pages
Chandan Resume
No ratings yet
Chandan Resume
6 pages
Readings in The Philippine History Course Assessment 2
No ratings yet
Readings in The Philippine History Course Assessment 2
1 page
OnShape Keyboard Shprtcuts
0% (1)
OnShape Keyboard Shprtcuts
1 page
Pooja QA Resume
No ratings yet
Pooja QA Resume
2 pages
Fundamental Operations On Integers
No ratings yet
Fundamental Operations On Integers
13 pages
Cybersecurity Roadmap Zero To Hero
No ratings yet
Cybersecurity Roadmap Zero To Hero
3 pages
Database Queries for Business Users
No ratings yet
Database Queries for Business Users
8 pages
BodorThinker3.0 4 SM en
100% (1)
BodorThinker3.0 4 SM en
122 pages
Mavigard - Mas
No ratings yet
Mavigard - Mas
37 pages
Model, Render, Animate: Houdini Foundations
No ratings yet
Model, Render, Animate: Houdini Foundations
24 pages
IT Support & Infrastructure Guide
No ratings yet
IT Support & Infrastructure Guide
227 pages
Coding Deret Angka
No ratings yet
Coding Deret Angka
3 pages
Victory School Membership System Project
No ratings yet
Victory School Membership System Project
5 pages
UM1021 - STM32F105xx - 107x - 2xx - 4xx USB - en - CD00289278
No ratings yet
UM1021 - STM32F105xx - 107x - 2xx - 4xx USB - en - CD00289278
107 pages
Data Logger Huato User Guide
No ratings yet
Data Logger Huato User Guide
16 pages
مكتبة نور كيفية تثبيت Microsoft Visual FoxPro 9 0 3
No ratings yet
مكتبة نور كيفية تثبيت Microsoft Visual FoxPro 9 0 3
12 pages
Web Hosting Server Details
No ratings yet
Web Hosting Server Details
11 pages
Thesis Writing Made Easy
100% (3)
Thesis Writing Made Easy
6 pages
DDTi Manual
No ratings yet
DDTi Manual
34 pages
Computer Networks Exam Feb 2020
No ratings yet
Computer Networks Exam Feb 2020
2 pages
Top Networking Interview Questions (2024) - InterviewBit
No ratings yet
Top Networking Interview Questions (2024) - InterviewBit
33 pages
Real-Time Bus Tracking App Development
No ratings yet
Real-Time Bus Tracking App Development
6 pages
MVP Monk Build Ragnarok Classic
No ratings yet
MVP Monk Build Ragnarok Classic
2 pages
Arch and Types of Snowflake Stages
No ratings yet
Arch and Types of Snowflake Stages
51 pages