Zeke Reference Guide

ASG-Zeke OS/390
Reference Guide
Version 5.2
Publication Number: AZM0400-52
Publication Date: May 2002
The information contained herein is the confidential and proprietary information of Allen Systems Group, Inc. Unauthorized use of this information and disclosure to
third parties is expressly prohibited. This technical publication may not be reproduced in whole or in part, by any means, without the express written consent of Allen
Systems Group, Inc.
1982-2002 Allen Systems Group, Inc. All rights reserved.
All names and products contained herein are the trademarks or registered trademarks of their respective holders.
ASG-Zeke and Zeke are trademarks of Allen Systems Group, Inc.
ASG Worldwide Headquarters Naples Florida USA | asg.com | info@asg.com

1333 Third Avenue South, Naples, Florida 34102 USA Tel: 941.435.2200 Fax: 941.263.3692 Toll Free: 800.932.5536 (USA only)
ASG Documentation/Product Enhancement Fax Form

Please FAX comments regarding ASG products and/or documentation to (941) 263-3692.
Company Name
Telephone Number
Product Name/Publication
Version #
Product:
Publication:
Tape VOLSER:
Enhancement Request:
2002 Allen Systems Group, Inc.

All names and products are trademarks or registered trademarks of their respective holders.
Site ID
Contact name
Publication Date
ASG Support Numbers

ASG provides support throughout the world to resolve questions or problems regarding
installation, operation, or use of our products. We provide all levels of support during normal
business hours and emergency support during non-business hours. To expedite response time,
please follow these procedures.
Please have this information ready:
Product name, version number, and release number
List of any fixes currently applied
Any alphanumeric error codes or messages written precisely or displayed
A description of the specific steps that immediately preceded the problem
The severity code (ASG Support uses an escalated severity system to prioritize service to
our clients. The severity codes and their meanings are listed below.)
Verify whether you received an ASG Service Pack for this product. It may include
information to help you resolve questions regarding installation of this ASG product. The
Service Pack instructions are in a text file on the distribution media included with the
Service Pack.
If You Receive a Voice Mail Message:

1
Follow the instructions to report a production-down or critical problem.
Leave a detailed message including your name and phone number. A Support representative
will be paged and will return your call as soon as possible.
Please have the information described above ready for when you are contacted by the Support
representative.
Severity Codes and Expected Support Response Times

Severity
Meaning
Expected Support Response

Time
Production down,
critical situation
Within 30 minutes
Major component of product disabled
Within 2 hours
Problem with the product, but customer has

work-around solution
Within 4 hours
"How-to" questions and enhancement

requests
Within 4 hours
ASG provides software products that run in a number of third-party vendor environments. Support
for all non-ASG products is the responsibility of the respective vendor. In the event a vendor
discontinues support for a hardware and/or software product, ASG cannot be held responsible for
problems arising from the use of that unsupported version.
Business Hours Support

Your Location
Phone
Fax
E-mail
United States and

Canada
800.354.3578
239.263.2883
support@asg.com
Australia
61.2.9460.0411
61.2.9460.0280
support.au@asg.com
England
44.1727.736305
44.1727.812018
support.uk@asg.com
France
33.141.028590
33.141.028589
support.fr@asg.com
Germany
49.89.45716.222
49.89.45716.400
support.de@asg.com
Singapore
65.6332.2922
65.6337.7228
support.sg@asg.com
All other countries:
1.239.435.2200
support@asg.com
Non-Business Hours - Emergency Support

Your Location
Phone
Your Location
Phone
United States and

Canada
800.354.3578
Asia
65.6332.2922
Japan/Telecom
0041.800.9932.5536
Australia
0011.800.9932.5536
Netherlands
00.800.3354.3578
Denmark
00.800.9932.5536
New Zealand
00.800.9932.5536
France
00.800.3354.3578
Singapore
001.800.3354.3578
Germany
00.800.3354.3578
South Korea
001.800.9932.5536
Hong Kong
001.800.9932.5536
Sweden/Telia
009.800.9932.5536
Ireland
00.800.9932.5536
Switzerland
00.800.9932.5536
Israel/Bezeq
014.800.9932.5536
Thailand
001.800.9932.5536
Japan/IDC
0061.800.9932.5536
United Kingdom
00.800.9932.5536
All other countries
1.239.435.2200
ASG Web Site

Visit http://www.asg.com, ASGs World Wide Web site.
Submit all product and documentation suggestions to ASGs product management team at
http://www.asg.com/asp/emailproductsuggestions.asp.
If you do not have access to the web, FAX your suggestions to product management at (239)
263-3692. Please include your name, company, work phone, e-mail ID, and the name of the ASG
product you are using. For documentation suggestions include the publication number located on
the publications front cover.
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
About this Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Publication Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
1 Zeke Utility Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Statement Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Character String Delimiters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Formatting Rules for OCCURS/WHEN Clauses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Jobnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Zeke Input Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command Acceptance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Zeke Program JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
3
3
4
4
5
5
5
Batch Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
BACKUPCopy the Zeke Database or Audit Trail Dataset . . . . . . . . . . . . . . . . . . . . . . 6
CALENDARAdd/Maintain System Calendars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
CREATEInitialize the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
DOCCopy Documentation Into the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
EVENTAdd/Maintain Event Master Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
JCLCopy JCL Into the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
OPTIONS Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
RESTORERestore Database Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
SCHEDULECreate the New Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
OVERRIDESelect Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
VAULTControlling the Vault Dataset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Simulating the Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
SIMULATESimulating the Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
2 ZEKESET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
ASG-Zeke OS/390 Reference Guide
SET Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Statement Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET ABENDTerminate a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET ROUTECreating Large Block Letter Separator Pages . . . . . . . . . . . . . . . . . . . .
SET xCOMIssuing System and Zeke Commands . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET VARIABLEDefining Zeke Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET COMMENTAdd Comment Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET CONDCODE or SET RETCODESet Condition or Return Codes . . . . . . . . . . .
SET GOTOBranch within Control Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET WAITSetting a Wait Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OPTION NOSUBVariable Substitution in ZEKESET . . . . . . . . . . . . . . . . . . . . . . . .
CDATEDate Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ON ERRORSyntax Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
75
75
79
79
81
82
84
84
86
87
87
88
95
3 Report Writer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Generating Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Output Reports to File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Report Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Report SequenceEvent and Plan Listings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Page BreaksEvent and Plan Listings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Line SpacingEvent and Plan Listings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selecting FieldsEvent and Plan Listings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
104
104
106
107
107
LIST EVENT/PLANEvent Master and Schedule Listings . . . . . . . . . . . . . . . . . 110

Sample Report - LIST PLAN - 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
LIST CALIDZeke Calendar Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Sample Report - LIST CALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
LIST VARIABLEZeke Variable Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Sample Report - LIST VARIABLE - 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
LIST OPERRECSZeke Operator ID Information . . . . . . . . . . . . . . . . . . . . . . . 135
Sample Report - LIST OPERRECS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
LIST OPERCLASOperator ID Security Classes. . . . . . . . . . . . . . . . . . . . . . . . . 137
Sample Report - LIST OPERCLAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
LIST RESOURCESystem Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Sample Report - LIST RESOURCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
4 Operator Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Entering Operator Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Command Prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
ii
Contents
Command Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verifying Command Acceptance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering Multiple Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
141
142
142
143
Global Event Selection Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

ZADD Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
ZALTER Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Altering JCL Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Altering Other Event Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Altering System-related Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Altering Initiator Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
159
159
160
166
167
ZDELETE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

ZDISABLE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disabling Scheduled Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disabling Automatic Replies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disabling Electronic Vaulting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
172
172
173
174
ZDISPLAY Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Event Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Variable Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Initiator Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Automatic Reply Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying System Pool Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Zeke Agents Identifying Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Remote Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Communication Records Information . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Tracing Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PathFinderDisplaying Preceding and Succeeding Events. . . . . . . . . . . . . . . . . . . . .
ZDISPLAY Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
174
176
181
182
183
184
184
185
185
186
186
189
191
ZENABLE Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

ZHOLD Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
ZID Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
ZINFO Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
ZKILL Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
ZMAP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
ZOK Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
ZREFRESH Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
ZRELEASE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
ZRELOAD Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
iii
ZRESOURCE Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

ZSCAN Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
ZSET Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Set Variable Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Set Default System ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
ZSTATUS Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
iv
Preface
The ASG-Zeke OS/390 Reference Guide provides information about the enterprise
scheduling product ASG-Zeke (herein called Zeke). This guide assumes that the
appropriate components have been installed at your site.
Allen Systems Group, Inc. (ASG) provides professional support to resolve any questions
or concerns regarding the installation or use of any ASG product. Telephone technical
support is available around the world, 24 hours a day, 7 days a week.
ASG welcomes your comments, as a preferred or prospective customer, on this
publication or on any ASG product.
About this Publication

This publication consists of these chapters:
Chapter 1, "Zeke Utility Program," describes the Zeke batch utility functions and
parameters.
Chapter 2, "ZEKESET," provides information on using Zeke job and input control
statements.
Chapter 3, "Report Writer," describes the LIST function of the Zeke batch utility,
which produces several types of reports.
Chapter 4, "Operator Commands," describes the operator commands used to make

changes from any OS/390 console or from the /COMM or the /ZCOM functions of
the Zeke online facility. Most can also be issued from any primary command line in
the Zeke ISPF online facility.
Related Publications
The documentation library for ASG-Zeke consists of these publications (where nn
represents the product version number):
ASG-Zeke OS/390 Users Guide (AZM0200-nn) explains the procedures for using
Zeke to schedule your enterprise.
ASG-Zeke OS/390 Installation Guide (AZM0300-nn) defines Zeke system

requirements, provides instructions for installing Zeke, and explains the optional
features you can activate after installing.
ASG-Zeke OS/390 Reference Guide (AZM0400-nn) provides a reference for using

Zeke batch programs and operator commands, and for generating reports.
ASG-Zeke Quick Reference (AZM0900-nn) is a quick-reference guide to Zeke

operator commands, providing command syntax and examples.
ASG-Zeke Messages and Codes (AZM1200-nn) lists the Zeke messages, describes
their meanings, causes, and resolutions, and provides return code explanations.
ASG-OASIS Reference Guide (AZO0300-nn) provides information about

ASG-OASIS (herein called OASIS), the framework for the ASG workload
management products.
Note:
To obtain a specific version of a publication, contact the ASG Service Desk.
vi
Publication Conventions
Allen Systems Group, Inc. uses these conventions in technical publications:
Convention
Represents
ALL CAPITALS
Directory, path, file, dataset, member, database,

program, command, and parameter names.
Initial Capitals on Each Word Window, field, field group, check box, button, panel (or
screen), option names, and names of keys. A plus sign
(+) is inserted for key combinations (e.g., Alt+Tab).
lowercase italic
monospace
Information that you provide according to your

particular situation. For example, you would replace
filename with the actual name of the file.
Monospace
Characters you must type exactly as they are shown.

Code, JCL, file listings, or command/statement syntax.
Also used for denoting brief examples in a paragraph.
Vertical Separator Bar ( | )

with underline
Options available with the default value underlined (e.g.,

Y|N).
vii
viii
1Zeke Utility Program
This chapter describes the Zeke batch utility program, the format of the statements, and the
commands and keywords. It also includes a description of the Simulation program.
General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Statement Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Character String Delimiters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Formatting Rules for OCCURS/WHEN Clauses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Jobnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Zeke Input Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command Acceptance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Zeke Program JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
3
3
4
4
5
5
5
Batch Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
BACKUPCopy the Zeke Database or Audit Trail Dataset . . . . . . . . . . . . . . . . . . . . . . 6
CALENDARAdd/Maintain System Calendars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
CREATEInitialize the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
DOCCopy Documentation Into the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
EVENTAdd/Maintain Event Master Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
JCLCopy JCL Into the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
OPTIONS Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
RESTORERestore Database Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
SCHEDULECreate the New Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
OVERRIDESelect Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
VAULTControlling the Vault Dataset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Simulating the Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
SIMULATESimulating the Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
General Information
These are the main functions performed by the utility program.
Command
Description
SCHEDULE
Creates the daily schedule
BACKUP
Backs up the Zeke database
CREATE
Initializes a database
RESTORE
Restores a backup database
EVENT
Adds and maintains EMRs
CALENDAR
Adds and maintains system calendars
OPTIONS
Performs various functions within Zeke
JCL
Copies JCL into the database
DOC
Copies documentation into the database
VAULT
Controls the vault dataset
1 Zeke Utility Program
Statement Format
The following are the formatting rules for the Zeke utility input statements:
Begin a statement in any column and end the statement by column 72. Columns 73
through 80 are ignored.
Continue on as many statements as necessary in any column (from 1 through 72).

No continuation character is required. All parameters following a command are
assumed to belong to that command until the next command word is encountered.
Enter $$ (two dollar signs) to signify the end of a statement, so Zeke knows to
process the statement without reading the next command first. This is optional.
Separate parameters and operands by either an equal sign (=) or by one or more
spaces.
Enclose multiple operands within parentheses and separate by a comma or by one

or more spaces. Parentheses are optional for one operand.
Separate parameters by a comma or by one or more spaces. Use either a comma or

one or more spaces to separate items, but not both. A comma followed by a space
indicates the end of the statement to Zeke.
If you are running multiple versions of Zeke, the EXEC card must include the
subsystem name, if other than SSSI. For example,
//Z1
EXEC
ZEKEUTL,PARM=SUBSYS=subsystem name
Character String Delimiters

Use a special character to delimit character string operands. Special characters include
any HEX character of 7F or less (except for a dollar sign) such as a quote, dash, slash, or
parenthesis. The delimiter character cannot appear within the character string.
The following are valid examples of the use of character string delimiters:
EVENT
EVENT
EVENT
EVENT
UPD
UPD
UPD
UPD
3 DESC='THIS IS THE DESCRIPTION'

45 DESC .THE DESCRIPTION IS DELIMITED BY A PERIOD.
53 DESC=/SLASHES OR OTHER CHARACTERS MAY BE USED/
77 DESC=(PARENTHESES MAY BE USED FOR DELIMITERS)
The following are invalid examples of the use of character string delimiters:
EVENT UPD 4 DESC=(AN OPEN PAREN MUST BE FOLLOWED BY A CLOSE(
EVENT UPD 34 DESC 'DELIMITER CHAR 'QUOTE' CONTAINED IN VALUE'
EVENT UPD 54 DESC=$DOLLAR SIGN MAY NOT BE USED AS DELIMITER$
Delimiters indicate that a value is character instead of numeric.

When there are no delimiters, a character value can only be one word with no spaces,
commas, or equal signs.
3
When there are no delimiters and the value is all numbers, the value is numeric. Otherwise,
it is character.
The following are examples of character, character string, and numeric values:
WHEN
WHEN
WHEN
WHEN
WHEN
(VAR
(VAR
(VAR
(VAR
(VAR
$XYZ
$XYZ
$XYZ
$XYZ
$XYZ
LE
LE
EQ
LE
LE
55)
'55')
YES)
'YES')
/CHAR STRING/)
Numeric value
Character value
Character value
Character (same as above)
Character string
Formatting Rules for OCCURS/WHEN Clauses

Enclose the entire OCCURS and/or WHEN clause within a set of parentheses; however,
the clause can contain internal levels of parentheses. For example,
OCCURS (WORKDAYS AND (DAY GE 8 AND DAY LE 14))
WHEN (EOJ JOBNAME1)
Verify that the clauses contain as many right parentheses as left parentheses.
Refer to your ASG-Zeke OS/390 Users Guide for an overview of how to use OCCURS
clauses and WHEN conditions.
Jobnames
Batch commands support the use of 30-character, mixed-case jobnames, except for
keywords, which must still be entered in upper case.
You must change the editor to CAPS OFF before entering mixed-case jobnames. In CAPS
OFF mode, OS/390 jobnames are not upper cased automatically. You must enter them in
upper case.
The following is a valid statement:
EVENT ADD JOB PayrollReports
The following is an invalid statement:

event add job PayrollReports
With the WHEN condition, you can enter a 30-byte mixed-case jobname as the target of
the jobname triggers, such as EOJ, AEOJ, and NOTDURING JOB. Within the WHEN
condition, Zeke considers case in the jobnames only, not in other WHEN keywords. Both
of the following examples are valid WHEN conditions:
WHEN EOJ JOBA AND EOJ PayrollReports
WHEN eoj JOBA and eoj PayrollReports
4
Zeke Input Source

The Zeke utility program reads input using the DD name SYSIN, or from the console. To
read input from the console, specify the CONSOLE parameter on the execute statement
in the JCL, or include the CONSOLE command as SYSIN data. Console must not be the
last Zeke command supplied through the SYSIN. If so, it will be ignored.
Command Acceptance
A message is printed on the SYSPRINT dataset describing the results of the utility
request. The last character of the message ID indicates:
Last
Character
Description
The completion of a normal system function. For information only.
A severe error. The requested action is not completed.
A potential error. The requested action is completed.
An operator response is required.
Zeke Program JCL

The Zeke installation process installs an OS/390 procedure named ZEKEUTL. Use this
procedure to execute the Zeke utility program.
It contains the necessary DD statements for ZEKECAT, SYSPRINT, and SORTWK1
through SORTWK3.
The following is a sample jobstream to execute ZEKEUTL:
//ZUTIL JOB ,MSGLEVEL=(1,1) ,CLASS=A

//Z1
EXEC ZEKEUTL,PARM=SUBSYS=subsystem name
//SYSIN DD *
EV ADD JOB ....
EV ADD JOB ....
EV ADD JOB ....
/*
//

//Z1
//SYSIN DD *
SCHEDULE TODAY ACTIVATE
/*
//

//Z1
//SYSIN DD *
LIST EVENTS fields=(event,ename,system)
/*
//
Batch Commands
BACKUPCopy the Zeke Database or Audit Trail Dataset
Copies the contents of the Zeke database or the Audit Trail dataset to a tape or disk file.
This creates a backup copy in case the database must be restored.
Use the BACKUP command to backup your database at least once a day. It is
recommended that you back up the database prior to each scheduling run.
The database can be copied in two formats.
Format
Description
Physical
The copy on tape is an exact copy of the database on disk.
Logical
The copy follows the pointers to the different types of database records
and groups all the elements of an event together. Two logical backups
can be merged into one database. See "RESTORERestore Database
Backup" on page 47 for more information on the RESTORE command.
Note:
The Zeke database is not a normal sequential file and most backup/copy utilities do not
perform properly when used with the Zeke database. Use only the Zeke BACKUP and
RESTORE functions.
The Zeke database BACKUP DD name is ZEKEBK. In the ZEKEUTL jobstream, enter
the Zeke backup file dataset name. This is a sequential file.
Caution! Regardless of the value for the ESIACTV generation option, an external
security call is always made to the SAF Security Interface using the resource
class of Z$CATAL with a resource name of BACKUP## and ALTER authority.
If this class information is not defined in your security package, then the SAF
action and return code are determined by your security product. If you do not
have a security product using SAF, Zekes internal security will be used, which
allows the request by default.
Refer to your ASG-Zeke OS/390 Users Guide for more information on creating the Zeke
databases (primary and vault) and on backing up the Zeke database.
Syntax
BACKUP
PHYSICAL
DATASPACE
TAPE
LOGICAL
DISK
Parameters
Parameter
Description
blank
Creates two backup files per backup. One is physical, the other is
logical. This backup copy can be used for either a physical or logical
restore.
PHYSICAL
Creates an exact copy of the Zeke database and produces a full-track

read and write of the physical portion of the database.
Note:
A backup file created with the BACKUP PHYSICAL command

cannot be used to logically restore another database. However, the file
can be used with the RESTORE PHYSICAL parameter to physically
move the database to another dataset with a larger allocated size.
Parameter
Description
LOGICAL
Creates a logically organized copy of the database which can be used

for a logical restore. The database is reorganized (the event numbers
are unchanged). The pointers keep the event elements grouped
together. This allows you to merge two databases.
DATASPACE
Creates a backup copy of the Zeke database (physical, logical, or both)

from a temporary copy of the database created in an OS/390 dataspace.
Note:
Using this parameter reduces I/O against the database, the duration of
the database-wide enqueue, and the time needed for the backup.
TAPE
Default. Copies the contents of the Zeke database to a tape.
DISK
Copies the contents of the Zeke database to a disk file.
Sample JCL
The following is an example of the JCL for the BACKUP function to back up the Zeke
database to tape:
//ZEKEBKUP JOB ,MSGLEVEL=(1,1),CLASS=A

//ZBK
EXEC ZEKEUTL
//ZEKEBK
DD
DSN=ZEKE.BACKUP,DISP=(NEW,KEEP),
//
VOL=(RETAIN,SER=ZEKETP),UNIT=TAPE,LABEL=(1,SL)
//SYSIN
DD
*
BACKUP TAPE DATASPACE
/*
The following is an example of the JCL for the BACKUP function to back up the Zeke
database to disk:
//ZEKEBKUP JOB ,MSGLEVEL=(1,1),CLASS=A

//ZBK
EXEC ZEKEUTL
//ZEKEBK
DD
DSN=ZEKE.DISK.BACKUP,DISP=(,KEEP)),
//
UNIT=SYSDA,SPACE=(CYL,(10,10)),
//
VOL=SER=ZEKEVL
//SYSIN
DD *
BACKUP DISK DATASPACE
/*
The Zeke database is enqueued for the duration of the physical backup. It is recommended
that you schedule the backup during the period that has the least amount of CPU activity.
8
CALENDARAdd/Maintain System Calendars

Adds or updates a standard calendar.
Syntax
CALENDAR
ADD calendar-ID
FISCMNTH nn
WORKDAYS days
HOLIDAYS (dates)
EXPIRE (date)
YEAR yyyy
DELETE calendar-ID
UPDATE calendar-ID
FISCMNTH nn
HOLIDAYS (dates)
WORKDAYS days
EXPIRE (date)
YEAR yyyy
Parameters
Parameter
Description
ADD
Add a new calendar.

For example,
CALENDAR ADD TEST1 FISCMNTH 10 ...
Two different calendars within the same database can have different
working days and different holidays.
DELETE
Delete the existing calendar from the database. If a calendar is

deleted that has a related active event, the scheduling function cannot
process the event.
UPDATE
Update the workdays, and/or holidays of an existing calendar.
calendar-ID
The name of the calendar. The calendar name can be up to 8

characters long.
Parameter
Description
EXPIRE
Date the calendar expires using the format MM/DD/YYYY or

DD/MM/YYYY depending on the date support of your system.
Note:
You can update the expiration date using the batch utility program.
To delete an expiration date, you must use Zeke online facility.
Refer to your ASG-Zeke OS/390 Users Guide for more information
on Zeke calendars.
FISCMNTH
Required with the ADD function. Specify the starting fiscal month.
Values are 1 through 12 (January through December).
HOLIDAYS
Enter up to 30 holiday dates using the format MM/DD/YYYY or

DD/MM/YYYY depending on the date support of your system.
Enclose all the dates within a set of parentheses and separate by
commas or spaces.
Note:
When HOLIDAYS are updated, enter all holidays to remain in

effect on the statement. Any left off of the list are considered
normal working days.
WORKDAYS
Enter all the days that are defined as workdays:

MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY SATURDAY
SUNDAY
Note:
When WORKDAYS are updated, enter all work days on the

statement. Any left off of the list are considered non-working days.
YEAR
10
Required when deleting or updating a year-specific calendar.

Specifies the year that the calendar is valid, using the format YYYY.
If you leave this field blank, the year defaults to ****.
Examples
The following example updates calendar ID A with the proper holidays:
CALENDAR UPDATE A
HOLIDAYS (01/01/2001,07/04/2001,11/23/2001,11/24/2001,12/25/2001,01/01/2002)
FISCMNTH 1
The following example adds calendar B:
CALENDAR
WORKDAYS
HOLIDAYS
FISCMNTH
ADD B
MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY SATURDAY
(01/01/2001 07/04/2001 11/23/2001 11/24/2001 12/25/2001 01/01/2002)
1
CREATEInitialize the Database

Initializes a new or existing database. When the CREATE function is performed on an
existing database, all information in that database is destroyed.
Use the CREATE function for the following reasons:
You are using Zeke for the first time.
You are using a new dataset.
The CREATE function uses the filename ZEKENEW. All other system functions use the
filename ZEKECAT.
The CREATE function is not necessary if the database is being restored, because the
RESTORE function automatically initializes the database (unless the merge option is
specifiedin this case, CREATE functions are not performed).
Caution! Regardless of the value for generation option ESIACTV, an external security
call is always made to the SAF Security Interface using the resource class of
Z$CATAL with a resource name of CREATE## and ALTER authority. If this
class information is not defined in your security package, then the SAF action
and return code are determined by your security product. If you do not have a
security product using SAF, Zekes internal security is used, which allows the
request by default.
Caution! If you have a ZEKE15B user exit in place, then it can override any external
security return code depending on how you have coded ZEKE15B.
11
Refer to your ASG-Zeke OS/390 Users Guide for more information on restoring the Zeke
database and creating the Zeke databases (primary and vault).
Syntax
CREATE
PLEXID name
Parameter
Parameter
Description
PLEXID
An 8-character name uniquely identifying a Zeke database to which

multiple systems are connected. You specify the PLEXID if you are
using the Coupling Facility. This identifier helps you to determine the
database from which records originate.
For example:
CREATE PLEXID PT4X
Sets the PLEXID for the database to PT4X.
Sample JCL
Following is an example of a database create jobstream.
//ZEKECRET
//ZUTL
//ZEKENEW
//
//SYSIN
CREATE
/*
JOB
,MSGLEVEL=(1,1),CLASS=A
EXEC
ZEKEUTL
DD
DSN=ZEKE.MVS.CATALOG,DISP=(NEW,CATLG),
UNIT=SYSDA,VOL=SER=ZEKEVL,SPACE=(CYL,(10))
DD
*
Zeke's database is a simple SD type file. The label information must not indicate ISAM,
DA, or VSAM for the file type; it must indicate SD.
12
DOCCopy Documentation Into the Database

Copies documentation from an outside source, supported by the ASG Service Desk, into
the Zeke database. This function requires a fixed block record length of 80.
Note:
The DD statement of the source dataset must be specified in the jobs JCL or the Zeke
procedure.
Syntax
DOC
event-number
ADD
doc-source
LASTEVent
DELETE
TEXT
ALL
DSN
REPLACE
NOTE
SCRATCH
Parameters
Parameter
Description
ADD
Adds the documentation from an outside source to an event in the

Zeke database.
DELETE
Deletes an event's existing text documentation from the Zeke

database.
REPLACE
Replaces the event's existing documentation with the

documentation from an outside source.
event-number
The event record to be updated.
LASTEVent
Tells Zeke to use the event number from the last successful event
task (for example, the last event that was added or updated).
doc-source
Specifies the outside documentation source. The DD statement for

the source dataset must be specified in the jobs JCL or the Zeke
procedure.
Note:
The Panvalet and Librarian options must be set in the generation

options in order to copy documentation from them.
13
Parameter
14
Description
BIMLibrary
Enter the Bim-Edit library from which you

want to copy documentation, followed by the
parameter BIMMEMBER.
CONDORMember
Enter the Condor library member from which

you want to copy documentation. Can be
followed by the parameters CONDORVER
and/or CONDORPASS.
DDNAME
Required for a partitioned or sequential

dataset. Enter the DD name that contains the
member.
DISK
Enter the disk dataset from which you want to

copy documentation. Can be followed by the
parameters DDNAME, UNIT, LRECL, and
BLOCK.
INSTREAM
Indicates that the documentation follows as

SYSIN data. All SYSIN documentation data
must begin with the DOCSTART statement
and end with the DOCSTOP statement:
DOCSTART
Indicates the beginning of the SYSIN

documentation to be added or replaced. The
maximum line length and amount of data are
limited for each documentation type:
Type
Columns
Statements
TEXT
80
unlimited
NOTE
60
10 statements
SCRATCH
60
10 statements
DSN
52
unlimited
DOCSTOP
Indicates the end of the SYSIN

documentation to be added or replaced.
LIBRARIAN
Enter the Librarian member name from which

you want to copy documentation.
PANVALET
Enter the Panvalet member name from which

you want to copy documentation.
Parameter
Description
PDS
Enter the partitioned dataset member name

from which you want to copy documentation.
The parameter DDNAME is required. For
example,
DOC REPLACE 60 PDS DOC2 DDNAME
DOCLIB
TEXT
SEQUENTIAL
Required if you are copying sequential data.

Enter the DDNAME that contains the
member.
TAPE
Enter the tape dataset from which you want to

copy documentation. May be followed by the
parameters DDNAME, UNIT, LRECL, and
BLOCK.
Specifies Text documentation as the type of documentation to be

added, replaced, or deleted. This is the default.
For example,
DOC DELETE 50
Deletes only text documentation data from Event 50.

ALL
Specifies that all four types of documentation are to be added,

replaced, or deleted.
For example,
DOC DELETE 25 ALL
Deletes all documentation data (Text, Note, Scratch Pad, and

Dataset) from Event 25.
DSN
Specifies Dataset documentation as the type of documentation to

be added, replaced, or deleted. This parameter corresponds to the
TAPE field in the DOC section of the EMR. Use the following
format:
I/O T/D VER DSN
Examples:
I T 001 TEST.TAPEFILE.INPUT
O D 000 TEST.DASDFILE.OUTPUT
15
Parameter
Description
NOTE
Specifies Note documentation as the type of documentation to be

added, replaced, or deleted.
SCRATCH
Specifies Scratch Pad documentation as the type of documentation

to be added, replaced, or deleted.
Sample JCL
The following JCL provides examples for some parameters:
//STEP1
//PDSDOC
//SEQDOC
//SYSPRINT
//SYSIN
DOC ADD 34
EXEC ZEKEUTL
DD DSN=PDS.DOC.TO.ZEKE,DISP=SHR
DD DSN=SEQ.DOC.TO.ZEKE,DISP=SHR
DD SYSOUT=*
DD *
LIBRARIAN DOCMEM1
Adds DOC TEXT to Event 34 in the Zeke database
if DOCMEM1 is found in the Librarian database
specified in the Zeke started task proc.
DOC ADD 35 PANVALET DOCMEM2
Adds DOC TEXT to Event 35 in the Zeke database

if DOCMEM2 is found in the Panvalet database
specified in the Zeke started task proc.
DOC ADD 36 PDS DOCMEM3 DDNAME PDSDOC Adds DOC TEXT from DOCMEM3 to Event 36 if
DOCMEM3 is in the PDS library specified by
the DD=PDSDOC in the add job JCL.
DOC ADD 37 DDNAME SEQDOC SEQUENTIAL
DOC ADD LASTEVENT INSTREAM DSN
Adds DOC TEXT from the sequential dataset to

Event 37 specified by the parm DDNAME,
provided the DDNAME is in the add job JCL.
Adds DSN documentation to the last event on

which a successful command was processed.
DOCSTART
I T 001 ZEKE.FILE.NAME
O T OO1 ZEKE.FILE.NAME2
DOCSTOP
DOC REP 38 INSTREAM SCRATCH
DOCSTART
THIS IS SCRATCH DATA
ENTERED VIA BATCH
DOCSTOP
/*
16
Replaces scratch documentation for Event 38.
EVENTAdd/Maintain Event Master Records

Adds or updates an Event Master Record (EMR).
Refer to your ASG-Zeke OS/390 Users Guide for more information on adding events to
the schedule as they are created.
Syntax
EVENT function
event-type
parameters
event-number
LASTEVent
Work Center Events

Work center events are typically manual tasks Zeke has no control over.
The following parameters are unique to work center events:
LINE1
LINE3
LINE5
LINE2
LINE4
LINE6
System Command Events

System command events can be any command that can be issued from an OS/390
console. System command events (SCOM events) consist of up to 6 lines of commands
and replies. Generally, the first line of an SCOM event is a command that causes the
system to issue a message to which the SCOM event replies. Each line of an SCOM event
specifies a command type.
Command Type
Description
System command
Zeke command
VM command
The following parameters are unique to SCOM events:

SCOM1
SCOM2
SCOM3
SCOM4
SCOM5
SCOM6
17
Job Events
The following parameters are unique to job events. These parameters further define a job
event and its resource requirements.
JCL retrieved by the user exit ZEKE14C may also be defined by using the keywords
specified in the X14CNM1 and X14CNM2 fields on the Generation Options screen.
One of the following Zeke JCL source parameters is required:
ZEKE
PANVALET
USER-SUPPLIED
BIMEDIT
CONDORMEMBER
FNAME
LIBRARIAN
PDS
If JCL source parameters are not specified, the system has no JCL source when the job is
ready for dispatch. A message is issued to the system operator and the job event is placed
on hold.
Message Events
A message event can be any message you want to issue to the system console.
REXX Events
REXX events can be used to execute REXX execs. The following parameters are unique
to REXX events.
REXXCLass
REXXPRIority
ARGuments
Event Command Parameters

Use the following parameters with the EVENT command:
Parameter
Description
function
Required. Describes the action to take. State one of the following:

ADD
Add a new EMR to the database.

For example,
EVENT ADD JOB XYZ...
CONVERT
18
Convert one type of platform event to another

type of platform event. Must be used in
conjunction with Platform parameter.
Parameter
Description
COPY
Copy the base EMR information to a new event

record.
For example,
EVENT COPY 417
EVENT COPY LASTEVENT
COPYAll
Copy the base EMR and all related events

records (including documentation, JCL, and
resource information) to a new event record.
DEACtivate
Flag an event as inactive, but do not remove it

from the database.
For example,
EVENT DEAC 417
EVENT DEAC LASTEVENT
DELete
Delete an EMR from the database. The event

still remains in the schedules of all active
systems.
For example,
EVENT DELETE 417
EVENT DELETE LASTEVENT
REACtivate
Make an inactive event active. The event can be

included in the schedule again.
For example,
EVENT REAC 311
EVENT REAC LASTEVENT
UPDate
Update the characteristics of an existing EMR.

EVENT UPDATE 45 PRIORITY 4
EVENT UPDATE LASTEVENT PRIORITY 4
19
Parameter
Description
event-type
Required for an ADD function. Specifies the type of event. The

event type cannot be changed after the event is added to the
database. Use the event type parameter with the UPDATE
function to change the jobname, Zeke command, message text, etc.
Specify one of the following:
COMMENT
This parameter has no operands. Define the

comment text with the LINE1 through LINE6
parameters.
For example,
EVENT ADD COMMENT
LINE1 THIS IS A HOLIDAY
LINE2 COMMENT EVENT
JOB
Enter the jobname as entered on the job card.

This name displays on the screens and messages
and is used by Zeke to track the event during
execution.
For example,
EVENT UPDATE 34 JOB OPS7TX01
MSG
Enter the message to issue to the system

operator console when it is dispatched. Enclose
in character string delimiters.
For example,
EVENT ADD MSG 'LINE 1 OF MESSAGE'
MSGn
Enter the message text for the second through

sixth lines. To clear a message line, enter the
appropriate message parameter and at least one
space between delimiters.
For example,
MSG1'
'
MSG2 'MORE TEXT HERE IF NEEDED'

MSG3 'STILL MORE, UP TO 6 LINES'
EV UPD 438 MSG4 'NEW MESSAGE LINE'
20
Parameter
Description
SCOMn
Enter any console command. This parameter

has no operands. Define the command text with
the SCOM1 through SCOM6 parameters.
For example,
EVENT ADD SCOM1 "C,D LST,ALL"
VCOM
Enter any VM CP command as long as the

privilege class of the command and the issuing
machine coincide. Enclose in character string
delimiters.
For example,
EVENT ADD VCOM (CP DRAIN 00E)
ZCOM
Enter any Zeke operator command or

combination of commands. Enclose in
character string delimiters. Multiple commands
are executed in sequence.
For example,
EVENT ADD ZCOM 'ZRELEASE JOB ZBC'
EVENT ADD ZCOM 'ZR JOB ABC ZR JOB
XYZ ZD WAIT'
REXx
Enter the member name of the exec to be

dispatched.
EVENT ADD REXX "TESTREXX"
REXXPRI=3 REXXCLASS=A
event-number
Required for all functions, except ADD. Specifies the record to be

updated, copied, etc. The LASTEVENT parameter can be used in
place of the event number.
Note:
The ADD function determines the event number and displays it

on the SYSLST/SYSLOG. The numbers are assigned in
sequential order. Deleted event numbers are reassigned, but
deactivated numbers are not.
LASTEVent
Use this parameter in place of the event number to tell Zeke to use
the event number from the last successful event task (for example,
the last event that was added or updated).
21
Parameter
Description
XXXXXXXX
Valid with job events only. This parameter is set by the user in the
/OPTIONS function of Zeke online facility (see X14CNM1 and
X14CNM2). Specify the name followed by the member name. The
name can be up to 8 characters.
For example,
EVENT UPD 100 USERNAME TESTJCL
USERNAME was specified in the X14CNM1 field.

APPLIcat
Enter a code to identify the application the event is a part of. The
code can be up to 8 characters. This field is used to sort, select, and
restrict access to events by the Report Writer, work center control,
and Zeke operator commands.
ARGuments
Enter arguments, if any are to be passed to the REXX exec.

Enclose all arguments in a single set of character delimiters. The
maximum length of the parameter to this keyword is 67.
AVGDURation
Format HH:MM:SS. Enter the time to have Zeke calculate the

average duration based on the last 10 dispatches.
BIMLibrary
Valid with job events only. Enter the Bim-Edit library that
contains the appropriate JCL.
BIMMember
Valid with job events only. Enter the Bim-Edit member name.
CALid
Required. Enter the calendar ID to use when scheduling this event.

The calendar must exist before the scheduling function is run. Use
the batch CALENDAR command or the online /Calendar to define
the calendar. The default is A.
For example,
CAL PROD
22
Parameter
Description
CCACTION
Enter the code indicating whether condition code processing is to

be executed at EOJ.
For example,
CCACTION=C
The job is cancelled if the condition code criteria is met.

CCACTION=A
The job is considered to have failed if the condition code

criteria is met.
CCACTION=O
The job is OKAY if condition code criteria is met.

CCACTION A CCLOW 0004 CCOPER GT
If the EOJ condition code is greater than 4, then consider the

job to have failed.
CCACTION=A CCHIGH=12 CCLOW=4 CCOPER=RA
CCSTEP=STEP1 CCPROC=USRPG1
Example of all CC parameters used together.

Caution! When adding condition codes through the batch utility,
add them one at a time. If you attempt to add multiple
condition codes in one batch input, only the last one
will be added (you will receive a return code of 0,
indicating that no errors occurred). To add multiple
condition codes, you must either use separate event
updates, or use the Zeke online system.
CCHIGH
Enter a condition code that serves as the high value of a condition

code RANGE criteria. A CCHIGH value must be specified if
CCOPER=RA. Up to 4 characters. (See "CCACTION" for an
example.)
CCLOW
Enter a condition code that either serves as the low value of a

RANGE criteria or is a single value that is compared to a jobs
maximum EOJ condition code. Up to 4 characters. (See
"CCACTION" for an example.)
23
Parameter
Description
CCOPER
Enter one of the following codes to determine the comparison

mode for the supplied CCLOW and CCHIGH values. (See
GT
Greater than
EQ
Equal to
LE
Less than or equal to
LT
Less than
GE
Greater than or equal to
NE
Not equal to
RA
Range
CCPROC
Enter the PROCSTEP name to be checked for a condition code.

(See "CCACTION" for an example.)
CCSTEP
Enter the STEPNAME to be checked for a condition code. (See

CLAss
Valid with job events only. Enter the class or class list (up to six in
a list) for the event.
For example,
EVENT UPD 56 CLA A
EVENT UPD 56 CLA (A,B,C)
EVENT ADD JOB TEST CLASS (G,H,I,T,J,K)
Before the event is dispatched, Zeke searches for an available

initiator that can run this class. If no class is entered, Zeke selects
an available initiator and runs the job with the highest class defined
for that initiator.
24
Parameter
Description
CONTrol
Required. The code indicating whether this job is tracked as an

Zeke-controlled job. Zeke-controlled jobs are tracked throughout
the entire execution.
YES
Default. Zeke recognizes this event as an Zeke-controlled

event.
NO
Zeke does not recognize this event as an Zeke-controlled

event and marks the event as done (SUCC) upon dispatch.
NX
Zeke recognizes this event as a non-executable

Zeke-controlled event.
CONVert
Valid with job events only. Enter a platform type to change the
event to a different one. "PLATform" on page 32 for a list of valid
platforms. Use this parameter only with the UPDATE function and
the PLATFORM parameter.
CONDORMember
Valid with job events only. Enter the Condor library member that
contains the appropriate JCL.
CONDORVersion Valid with job events only. Enter the Condor version number. If
omitted, the default is 001.
CONDORPass
Valid with job events only. Enter the Condor password.

For example,
EVENT ADD JOB DOSNAME3 CONDORM MEMBNM2
CONDORP PASS
DESCription,
DESC2
Enter a one- or two-line description of the event to be used on

summary screens and printed on reports. Up to 60 characters per
line. Enclose within character string delimiters.
For example,
DESC 'PAYROLL UPDATE FOR XYZ COMPANY'
DESC2=/NOTE THE USE OF A VALID CHARACTER STRING
DELIMITER/
DPRiority
Enter the Zeke dispatch priority number between 1 (highest) and

99 (lowest) to distinguish hot jobs from normally scheduled jobs.
The default is 50.
DRL
Assign a Zeke disaster recovery level to the event, if desired.
25
Parameter
Description
EARLYtime
Format HH:MM. From 00:00 to 47:59. Enter the earliest time this
event can be dispatched. To remove this time, enter EARLY with
no operand. If the time is greater than 24:00, Zeke knows the event
is to be processed the next day.
For example,
EARLYTIME 01:00
Eligible for dispatch at 1:00 am.

EARLY 16:00
Eligible for dispatch at 4:00 pm.

Note:
An event can be dispatched at its early time; however, events are

dispatched in schedule time sequence.
ENAme
Enter the name of the event. This field displays on other Zeke
screens and reports to help you identify the event. End of Event
(EOE) WHEN conditions and operator commands reference
events by event name.
EXPIre
Enter the date (MMDDYYYY or DDMMYYYY) the event expires. To

remove this date, enter EXPIRE and a 0 (zero). When the schedule
function runs on or after this date with the ACTIVATE parameter,
the event is automatically deleted.
If a schedule forecast is run for a date that is after the expiration
date, a message informing you of the expired event is displayed.
The event is not deleted.
For example,
EXPIRE 10312001
Deletes event on or after October 31, 2001.

EXPIRE 0
Removes expiration date.

FName
Valid with job events only. Enter the CMS file name that contains
the appropriate JCL or EXEC that creates the JCL.
For example,
EVENT ADD JOB JOBNAM8 FNAME USRNAM01
26
Parameter
Description
FREQCalc
Enter one of the following codes indicating how to calculate the

next dispatch time:
FREQuency
Schedule time; the next run is based on schedule time

regardless of when the job actually runs. This parameter
will default to S' if a value other than S' or C' is entered.
Clock (system) time; the next run is based on the

completion time of the previous run.
Format HH:MM. From 00:00 to 47:59. This field is for recurring

events only. Enter the amount of time the event is to wait before
dispatching again. Zeke adds the current schedule time or the
system time, and this field to determine the next schedule time.
For example,
FREQUENCY=01:00
Dispatches every hour.

FREQ 00:30
Dispatches every 30 minutes.

FTYPE
Valid with job events only. Enter the CMS file type. If you enter
EXEC, Zeke assumes that the operand named is an EXEC that
creates the JCL.
For example,
EVENT ADD JOBNAME9 FNAME USRNAM01 FTYPE OSJCL
EVENT ADD JOBNAME9 FNAME USRNAM02 FTYPE EXEC
If omitted, the default is the file type specified in the CMSFTYPE

field on the Genopt screen.
GROupid
Enter a code to identify the group the event is a part of. Up to 3

characters. This field is used to sort and select events by the Report
Writer, work center control, and Zeke operator commands.
27
Parameter
Description
JCLSTART
Indicates the beginning of the SYSIN JCL to be added for an event

as part of the EVENT ADD process.
All SYSIN JCL data must begin with the JCLSTART statement
and end with the JCLSTOP statement.
The SYSIN JCL must occur after the basic EMR data for the event.
The SYSIN DD of the batch job that is to supply the EVENT ADD
data must have the following format:
//SYSIN DD DATA,DLM=@@
JCL SYSIN data is limited to 450 lines and 80 characters per line.
Leading blanks are reserved for all statements not beginning with
//, /+, /-, or +##. All JCL statements preceded by one of the
characters listed above are automatically positioned in column 1.
Note:
JCL sources other than ZEKEJCL can be specified in the EMR

Add data even if JCL SYSIN is present.
//SYSIN
DD
DATA,DLM=@@
EVENT ADD JOB TESTJOB APP 'TST' GROUP 'TEST
SCHED 10:00 ZEKEJCL=YES
OCC (MONDAY)
JCLSTART
//TESTJOB JOB MSGLEVEL=(1,1)
//STEP1
EXEC PGM=IEBCOPY
//SYSPRINT DD
SYSOUT=*
//INDD
DD
DSN=DSA.TEST,DISP=SHR
//OUTDD
DD
DSN=DSA.TEST2,DISP=SHR
//SYSIN
DD
* COPY INDD=INDD,OUTDD=OUTDD
/*
JCLSTOP
@@
JCLSTOP
28
Indicates the end of the SYSIN JCL to be added for an event as part
of the EVENT ADD process. (See "JCLSTART" for more
information.)
Parameter
Description
LATEtime
Format HH:MM. From 00:00 to 47:59. Enter the time the event
must be dispatched by. If the event is not dispatched by this time,
a message is issued to the console. (If this parameter is omitted, no
message is issued.) If the time is greater than 24:00, Zeke knows
the event is to be processed the next day.
For example,
LATETIME 20:00
Notifies operator if event is not dispatched by 8:00 pm.

LATE 28:00
Notifies operator if event is not dispatched by 4:00 am the next

day.
Late events can have a higher dispatch priority based on the
generation option PRILATE. To remove the LATE time, enter
LATE with no operand.
LIBRarian
Valid with job events only. Enter the Librarian library member
name that contains the appropriate JCL.
LINE1
LINE2
LINE3
LINE4
LINE5
LINE6
Valid with comment events only. Enter up to 60 characters per line

to describe the work center activity. Enclose each comment line
within character string delimiters.
For example,
LINE1 'THIS WILL APPEAR AS LINE ONE'
LINE2=.YOU CAN USE OTHER DELIMITERS.
When updating the comment lines, you only need to specify the
lines to be changed. To blank out a comment line, enter the
appropriate LINE parameter and one space between delimiters.
For example,
LINE2 ' '
Using blank lines is useful for improving the readability of the

comments.
For example,
LINE1 'FRIDAY MASTER RECORD UPDATE'
LINE2 'FORMS ARE DUE FROM BOOKKEEPING'
LINE3 ' '
LINE4 'MAKE SURE THEY ARE NOTIFIED BY'
LINE5 '4:30 PM IF NOT RECEIVED YET'
29
Parameter
Description
MEM
Enter the PDS member name containing the events JCL. For
example,
EVENT ADD JOB TESTJOB2 PDS PRODJCL MEM TEST
MULThit
Enter Yes or No to indicate whether to allow an event to be

scheduled multiple times due to a non-workday. If NO is entered,
Zeke defaults to the MULTHIT value specified in the online
generation option.
MUSTend
Format HH:MM. From 00:00 to 47:59. Enter the latest time the
event can complete processing. If the MUSTEND time is less than
the calculated time, the event is put on hold and an operator
message is issued to the console.
NOTAFter
Format HH:MM, From 00:00 to 47:59. Enter the latest time the
event can be dispatched. If the NOTAFTER time is less than the
system time, the event is put on hold and an operator message is
issued to the console.
NOTE1
NOTE2
NOTE3
NOTE4
NOTE5
NOTE6
NOTE7
NOTE8
NOTE9
NOTE10
Valid with the ADD function only. Enter up to 60 characters per

line to the notepad area of the event. Enclose each note within
character string delimiters. You can use blank lines to improve the
readability of the notepad. To do so, enter the appropriate NOTE
parameter and one space between delimiters.
For example,
NOTE1 'THIS EVENT IS THE MAIN KICKOFF EVENT IN THE
PAYROLL SERIES.'
NOTE2 NOTIFICATION OF WHEN TO RUN THIS EVENT WILL
COME BY FAX FROM
NOTE3 ' '
NOTE4=.NOTICE THAT YOU CAN USE OTHER DELIMITERS.
NWDAY
30
Enter one of the following codes specifying how to schedule this

event on non-workdays:
A
After non-workday (default)
On non-workday
Before non-workday
Do not schedule event
Parameter
Description
OCCURS
Enter an OCCURS clause indicating when the event should be

added to the schedule. Up to 500 characters.
EVENT ADD JOB OCCURS (TUESDAY)
Refer to your ASG-Zeke OS/390 Users Guide for an explanation

of defining OCCURS clauses and a listing of OCCURS clause
keywords.
OPERok
Indicate whether Zeke is to wait for an operator OK before

dispatching the event.
OPEROK=NO
Zeke auto dispatches.

OPEROK=YES
Dispatches only by operator command. When moved from the

schedule queue to the dispatch queue, a message is issued to
the console. The wait reason AWAITING OPER OK is
displayed on ZDISPLAY screens.
PANvalet
Valid with job events only. Enter the Panvalet library member
name that contains the appropriate JCL. Up to 10 characters.
For example,
EVENT ADD JOB JOBNAME3 PANVALET PANNAME1
PDS
Enter the PDS DD name that will be associated in the Zeke started
task with the PDS containing this event's JCL. The member name
is required with PDS.
EVENT ADD JOB TESTJOB1 PDS PRODLIB2 MEM TESTJCL2
The DD name can be a Zeke variable which would allow JCL to

be retrieved from a different dataset, depending on the assigned
value of the variable. This can cause performance degradation due
to OS/390 overhead associated with dynamic dataset allocations.
Note:
When using ZEKEJCL as the PDS name, it must be enclosed in

quotation marks, as shown:
EVENT ADD JOB TESTJOB1 PDS ZEKEJCL MEM TESTJCL1
31
Parameter
Description
PLATform
Indicate the platform the JCL is to be executed on. If not specified,

Zeke defaults to the platform specified in the DEFPLTFM
generation option.
AIX (see Note)
DCOSX (Pyramid)
HPUX (see Note)
MVS
OS2
OS400
SUN (see Note)
TANDEM
USYS
UNIX (all UNIX platforms: AIX, AT&T, HPUX, NCR, SCO,
SunOS, Sun Solaris, etc.)
VMS
VSE
WINDOWS (Windows, Windows NT, and Windows 95)
Note:
Although the AIX, HPUX, and SUN platform codes listed above
are supported, ASG recommends you use the UNIX platform
code.
PRIority
Valid with job events only. Enter the OPSYS priority code
(between 1 and 99) that is valid for the platform this job is to
execute on. If this parameter is omitted, the default priority code
as defined by the generation option DEFJPRTY is used.
For example,
PRIORITY=5
RESASSume
Enter the code indicating whether the event will obtain the
resource from an abended event that has specified
RESKEEP=YES. (If RESMODE is SR, RESASSUME and
RESKEEP must be No.) Valid codes are No, Yes, and Same.
RESASSUME=Y
The event can steal the resource from any abended event that
has specified RESKEEP=YES.
RESASSUME=S
The event that abends can steal the resource from itself, but
cannot steal it from another abended event.
32
Parameter
Description
RESCount
The number of resources this event requires. Enter any number

from 1 to 999. The default is 1.
RESCOUNT=08
RESHold
Enter the code indicating whether to hold the resource if it is

available and in the correct mode.
RESHOLD=NO
Note:
If RESHOLD=YES, the resource can be stolen by another event

with a higher dispatch priority.
RESKeep
Enter the code indicating whether to keep the resource if the event
abends. This resource can be obtained from a restart/rerun event.
(If RESMODE is SR, RESASSUME and RESKEEP must be No.)
RESKEEP=NO
RESMode
RESName
Enter one of the following resource modes required by the event:

EX
(Exclusive) One event has access to this resource. The

maximum RESCOUNT for this code is 1.
ES
(Exclusive/Share) One event has access to this resource

exclusively; however other events can share the resource.
The event that has the resource exclusively should be
coded as EX. The other events can use ES or SR.
*SR
Multiple events have access to this resource.

RESASSUME and RESKEEP must be set to No.
Resource name to be checked for availability before an event is

dispatched. The name can be up to 44 characters. The same
resource name cannot be added to an event more than once.
All resource names to be added through batch must be predefined
to Zeke.
Note:
If you add a resource through batch processing by specifying only

the RESNAME, the other resource parameters will default to
RESCOUNT=01, RESMODE=SR, RESHOLD=NO,
RESKEEP=NO, and RESASSUME=NO.
33
Parameter
Description
RETAin
Enter the code indicating whether Zeke should retain the event if
it is not dispatched on the scheduled date.
For example,
RETAIN=YES
Retain the event for the next (default) run.

RETAIN NO
Discard the event if it is not dispatched.

REXXCLass
Specify a valid ECF class (A through Z, 0 through 9) for the exec

to run in. This keyword must be specified to add a REXX event.
REXXPRIority
Specify the priority assigned a queued request if all subtasks are

busy for the REXXCLASS the exec is assigned to. (Valid values 1
through 9, where 1 is the highest priority. Default is 5.)
ROUTE
Optional with MSG jobs only. The two-digit user-assigned route

code (from 01 to 16) that corresponds to the alternate console route
code. Parentheses are required.
ROUTE=(01)
SCHEDADD
This parameter, along with the EVENT ADD parameter, causes a

newly created event to be added to the schedule queue as soon as
it is created in the database.
For example,
EVENT ADD JOB TESTJOB1 PDS PRODLIB2 MEM TESTJCL2
OCC (MONDAY) SCHEDADD
For events with multiple versions, the SCHEDADD function loads

the number of versions specified in the VERLOAD field on the
EMR. If VERLOAD is set to zero, SCHEDADD will schedule
only a version zero SQR.
34
Parameter
Description
The following example JCL uses the JCLSTART and JCLSTOP

parameters:
//RSCUTIL JOB ,MSGLEVEL=(1,1),CLASS=A
//JS010 EXEC ZEKEUTL,PARM=SUBSYS=ZDEV
//SYSPRINT DD SYSOUT=A
//SYSIN DD DATA,DLM=@@
EVENT ADD JOB RSCTEST2
OCCURS (REQUEST)
ZEKEJCL=YES
EXPIRE 01012001
SCHEDADD
JCLSTART
//RSCTEST2 JOB ,CLASS=A,MSGCLASS=A,
//MSGLEVEL=(1,1)
//JS010 EXEC PGM=IEFBR14
//DD01 DD DUMMY
//
JCLSTOP
@@
SCHEdtime
Required. Format HH:MM. Enter the normal schedule time from

00:00 (default) to 47:59 for this event. If the time is greater than
24:00, Zeke knows the event is to be processed the next day.
For example,
SCHED 12:00
Scheduled for 12:00 P.M. (noon).

SCHED 24:00
Scheduled for 12:00 A.M. (midnight).

SCHED 30:00
Scheduled for 6:00 A.M. the next day.

Note:
An event can be dispatched at its early time; however, events are

dispatched in schedule time sequence.
SCOM1
Valid with system command events only. Enter a C, a comma and

up to 60 characters of system commands. Enclose the line within
character string delimiters.
For example,
EVENT ADD SCOM SCOM1 (C,F CICSPROD,CENT S...)
35
Parameter
Description
SCOM2
SCOM3
SCOM4
SCOM5
SCOM6
Valid with system command events only. Enter up to 60 characters

of system commands and/or responses per line. Enclose each line
within character string delimiters.
SCOMAPPEND
Indicates the beginning of SCOM data in the SYSIN JCL to be

added to an existing SCOM job as part of the EVENT ADD or
EVENT UPDATE process.
All SCOM data must begin with the SCOMSTART or
SCOMAPPEND statement and end with the SCOMSTOP
statement. Each SCOM must begin with a valid SCOM command
code, a comma, and the command text. The command can have a
maximum length of 60 bytes. The following example uses
SCOMAPPEND and SCOMSTOP to add an SCOM EMR.
//JKMADD
JOB ,MSGLEVEL=(1,1),CLASS A
//ZUTL
EXEC ZEKEUTL,PARM=SUBSYS=SSSI
//SYSPRINT DD
SYSOUT=A
//SYSIN
DD
*
EVENT ADD SCOM ENAME SCOMEVENT
SCOMAPPEND
Z,ZID
Z,ZD ALL
C,D A,L
C,D D,T
SCOMSTOP
//*
36
Parameter
Description
SCOMSTART
Indicates the beginning of SCOM data in the SYSIN JCL to be

added for an SCOM event as part of the EVENT ADD or EVENT
UPDATE process.
All SCOM data must begin with the SCOMSTART or
SCOMAPPEND statement and end with the SCOMSTOP
statement. Each SCOM must begin with a valid SCOM command
code, a comma, and the command text. The command can have a
maximum length of 60 bytes.
For the EVENT UPDATE command, SCOMSTART replaces the
event records SCOM data with the SCOM data. The following
example uses SCOMSTART and SCOMSTOP to add an SCOM
event record.
//JKMADD
JOB ,MSGLEVEL=(1,1),CLASS A
//ZUTL
//SYSPRINT DD
SYSOUT=A
//SYSIN
DD
*
EVENT ADD SCOM ENAME SCOMEVENT
SCOMSTART
Z,ZID
Z,ZD ALL
C,D A,L
C,D D,T
SCOMSTOP
//*
SCOMSTOP
Indicates the end of the SYSIN SCOM data to be added to a event

record as part of the EVENT ADD or EVENT UPDATE process.
The SCOM data starts with either the SCOMSTART or
SCOMAPPEND statement.
SET
Valid with workcenter events only. Enter the variables and

associated values when the event is complete. Up to 500
characters. Refer to your ASG-Zeke OS/390 Users Guide for more
information on using variables for work centers, a list of
keywords, and an explanation of how to define a SET clause.
SYStemid
Enter a code to identify the system or pool that owns the event. An
event is associated with only one system or pool. The default is A.
For example,
SYS PROD
SYS A
37
Parameter
Description
TAPES
Valid with job events only. Enter the number of tape drives
required by this job (from 0 to 255). Zeke ensures that the number
of tape drives is free before dispatching the job. If the job is ready
to dispatch and the number of drives is not free, Zeke notifies the
operator that the job is waiting on xxx drives.
This number can be altered by operator command in the SQR, not
the EMR.If Zeke is generated with CALCTAP=YES, Zeke
calculates this number based on the last run. You only need to
specify a number to override this value.
For example,
TAPES=3
Requires three tape drives.

TARGet
Enter the name of the system where the job will execute. The
system name in the SYSTEM field is the dispatching system. If not
specified, Zeke defaults to *Local. The target value to use for
remote/other system dispatch can be acquired by reviewing the
generation option NETREGID of the remote system desired.
TIMES
Enter the number of times this event is to be dispatched per

schedule run. The number must be between 1 (default) and 255. If
this field is greater than 1, the event is called a recurring event.
For example,
TIMES=3
This event occurs three times.

TRIG
38
Enter a code to indicate when the recurring event triggers. A

recurring event is one for which the TIMES field is greater than 1
(i.e., an event with multiple occurrences). A non-recurring event is
one for which the TIMES field is 1; non-recurring events trigger
regardless of the code entered in the TRIG field. Valid values are:
TRIG=A
The recurring event triggers on all occurrences.

This is the default.
TRIG=F
The recurring event triggers on the first

occurrence only.
TRIG=L
The recurring event triggers on the last

occurrence only.
Parameter
Description
USERid
Enter a code to identify the person who is responsible for the event.
The user ID can consist of up to 8 characters.This field is used by
System events for reporting purposes, Comment events for work
center control, and the online security facility for limiting access.
EVENT ADD COMMENT USERID DATACTL1...
EVENT ADD JOB ABC USERID OPERATOR...
This parameter can also be used to blank out an incorrect user ID

on an EMR.
For example,
EVENT UPDATE 123 USERID
VERLOAD
Enter the number of versions of this event to be loaded during the

schedule build. This field defaults to zero. If VERLOAD is set to
zero, only one version of the event (version zero) can be in the
schedule at a time. If VERLOAD is set to one, only one version is
created by the schedule build, but any number of versions can be
added to the schedule after schedule load using the ZADD
command (up to 32767 versions).
EVENT UPDATE VERLOAD 00005
WHEN
Enter any prerequisites that must occur before the event can be
dispatched. Up to 1360 characters.
For example,
EVENT ADD JOB WHEN (EOJ JOBA)
Adds a new job event with a default (version zero) WHEN

clause of EOJ JOBA.
EVENT UPDATE 9 WHEN (EOJ JOBB)
Updates the default WHEN clause for event 9.

Refer to your ASG-Zeke OS/390 Users Guide for how to define
WHEN conditions and for a listing of WHEN condition keywords.
39
Parameter
Description
Only the WHEN condition for version zero (default version) of an

event can be maintained through the batch utility program. To
maintain WHEN conditions for other versions of the event, you
must use the online facility.
Note:
The WHEN clause is not valid for workcenters. Use the SET
clause instead.
ZEKEJCL
Enter YES to indicate the events JCL resides in the Zeke

database.
For example,
EVENT ADD JOB JOBNAMEX ZEKEJCL=YES
Note:
JCL can be automatically added to the database at the time of the

EVENT ADD function by using the JCLSTART function.
40
JCLCopy JCL Into the Database

Copies JCL from an outside source into the Zeke database.
Syntax
JCL
ADD
event number
REPLACE
LASTEVent
DELETE
event number
source
LASTEVent
Parameters
Parameter
Description
ADD
Add the JCL from an outside source to an event in the Zeke

database.
REPLACE
Replaces the event's existing JCL with the JCL from an outside
source.
DELETE
Deletes an event's existing JCL from the Zeke database. Only the
event number is required.
event-number
Required for all functions, unless the LASTEVENT parameter is

used. Specifies the event record to be updated.
LASTEVent
Use this parameter in place of the event number to tell Zeke to use
the event number from the last successful event task (for example,
the last event that was added or updated).
source
Specifies the source of the existing JCL. The DD statement for the
source dataset must be specified in the jobs JCL or the Zeke
procedure.
Note:
These sources must be defined in the Zeke Genopt screen in order

to copy JCL from them.
BIMLibrary
Enter the Bim-Edit library you want to copy

JCL from. Followed by the parameter
BIMMEMBER.
41
Parameter
Description
CONDORMember
Enter the Condor library member you want to

copy JCL from. Can be followed by the
parameters CONDORVER and/or
CONDORPASS.
DDNAME
Required for a partitioned or sequential

dataset. Enter the DD name that contains the
member.
DISK
Enter the disk dataset you want to copy JCL

from. Can be followed by the parameters
DDNAME, UNIT, LRECL, and BLOCK.
INSTREAM
Indicates that the JCL follows as SYSIN data.

All SYSIN JCL data must begin with the
JCLSTART statement and end with the
JCLSTOP statement. "JCLSTART" on
page 28 for additional information.
LIBRARIAN
Enter the Librarian member name you want to

copy JCL from.
PANVALET
Enter the Panvalet member name you want to

copy JCL from.
PDS
Enter the partitioned dataset member name

you want to copy JCL from. The parameter
DDNAME is required. For example,
JCL ADD 45 PDS JCL1 DDNAME JCLLIB
SEQUENTIAL
Enter the sequential dataset member name

you want to copy JCL from. The parameter
DDNAME is required. For example,
JCL ADD 74 SEQUENTIAL DDNAME SEQIN
TAPE
42
Enter the tape dataset you want to copy JCL

from. Can be followed by the parameters
DDNAME, UNIT, LRECL, and BLOCK.
OPTIONS Function
Performs the following functions:
Establish and update the company name and address displayed on reports
Establish and update the Zeke operating passwords
Print the database status report
Set Audit Log tracking options
Reset the following generation options: Posid and Multsys
The OPTIONS function will attempt to update the GENOPT or GENSYS record of the
actual SYSID the update job is executed on. If there is no GENOPT or GENSYS record
for that SYSID, then the generic SYSID record (********) is updated. If you want to
update the generation options for a specific SYSID, use the SYSGEN parm.
Syntax
OPTIONS
parameters
Parameters
Parameter
Description
AUDITCLS
Enter the code (YES or NO) indicating whether to track and log changes
to internal security class records.
OPTIONS AUDITCLS YES
AUDITCMD
Enter the code (YES or NO) indicating whether to track and log Zeke
operator commands.
AUDITCND
to calendar records.
AUDITECD
to external security class definition records.
AUDITEMR
to event master records (EMRs).
AUDITEVT
Enter the code (YES or NO) indicating whether to track and log an
event's execution flow.
AUDITGOP
to Zeke generation options.
43
Parameter
Description
AUDITNAM
to your company name or address.
AUDITOPR
to internal security operator records.
AUDITPAS
to passwords.
AUDITPIN
to partition or initiator definitions.
AUDITPOO
to pool records.
AUDITRES
to resource definition records.
AUDITSQR
to schedule queue records (SQRs).
AUDITVAR
to Zeke variable records.
CPUDEL
Option to delete an erroneous CPUID registration shown via a ZD COM

display. Must be used with the SYSGEN parm.
OPTIONS CPUDEL SYSGEN VSE220C
CUSTID
Enter the customer ID. Valid values are hex digits (0 through 9, A
through F), eight characters in length, and the fifth position is 0 through
7.
OPTIONS NAME1 COMPANY NAME CUSTID 1AE20F17
GRESActv
Enter the code (YES or NO) indicating whether the resource being
defined is available (active). Required when defining a resource. (Refer
to the entry for GRESOURCE for an example.)
GRESCnt
Enter the maximum shared count for the resource being defined (from 1
to 65,535). This number represents how much of a resource is available
to an event. (Refer to the entry for GRESOURCE for an example.)
If not specified, this value defaults to 1.
44
Parameter
Description
GRESOurce Enter the name of the resource being defined. The name can be up to 44
characters. Zeke checks the availability of these resources before the
event is dispatched.
Required when defining a resource. No blanks accepted.
Example of resource definition:
OPTIONS GRESOURCE TESTRESOURCENAME GRESSYID SYSTEMA
GRESACTV YES GRESCNT 5
GRESSyid
Enter the name of the system that owns the resource. (Refer to the entry
for GRESOURCE for an example.)
If not specified, this value defaults to GLOBAL, which means that any
system can share this resource.
You can specify a resource name more than once with different system
IDs.
If the events system ID is assigned to a pool, each resource for that event
should be defined as a GLOBAL resource to ensure proper dispatching.
MULTHit
Enter the code (YES or NO) indicating whether to allow an event to be

scheduled multiple times due to a non-workday. This parm changes the
generation option record for the specified system.
OPTIONS MULTHIT YES
MULTISys
Enter the code (YES or NO) indicating whether the database is shared by
more than one machine. This parm changes the generation option record
for the specified system.
OPTIONS MULTISYS=YES SYSGEN VSE230C
NAME1
Enter your company name. The company name can be up to 40

characters. Enclose within character string delimiters. Your company
name is printed in the Zeke report headings.
NAME1=ALLEN SYSTEMS GROUP
NAME2
NAME3
NAME4
Enter your company address or other information. There are 3 NAME

parameters with 40 characters each. Enclose each line within character
string delimiters.
PASSword
Enter up to 20 passwords. Enclose the list within parentheses and

separate each password by a comma. One of the functions, ADD,
DELETE, or REPLACE is required:
ADd
Adds the specified passwords to the system. For example:

OPTIONS PASSWORD (AAAAAAA,BBBBBBB) ADD
45
Parameter
Description
DElete
Deletes the specified passwords from the system. For

example:
OPTIONS PASSWORD (CCCCCCCC) DELETE
REplace Replaces the entire existing password list with the specified
list. For example:
OPTIONS PASSWORD (AAAAAAAA,BBBBBBBB,CCCCCCCC) REPLACE
POSid
Enter the code (YES or NO) indicating whether to assign a unique ID for
tracking only those jobs dispatched by Zeke. This parm changes the
generation option record for the specified system. The following
example changes the default GENSYS record.
OPTIONS POSID NO
POSIDEND
If POSID=YES, specifies whether POSID information is placed at the

end or the beginning in Zeke-dispatched jobs.
Note:
If POSIDEND is YES, then Zeke jobs that get JCL errors will not be
placed in FAIL status, but will be left pending.
STATus
Prints a database status report. This report lists the amount of used and
available space in the Zeke database.
OPTIONS STATUS
SYSGEN
Enter the system ID of the system you are updating. For example, to
update the POSID option for the system ID PRODSYS enter,
OPTIONS POSID NO SYSGEN PRODSYS
46
RESTORERestore Database Backup

Rebuilds the database from a backup file. You can also specify to restore from a disk file.
Use the RESTORE function to recover the contents of a destroyed database and to move
and/or enlarge the database. The file must have been produced by the utility program
BACKUP function.
When the database is being restored, the CREATE function is not necessary because the
RESTORE function automatically initializes the database (unless the merge option is
specified in this case, CREATE functions are not performed).
Caution! You must completely terminate Zeke prior to restoring the database. Do not use
the RESTORE function to restore an active database! If Zeke is active on any
systems sharing the database, stop the sharing systems by issuing the ZKILL
COLD operator command.
Caution! Regardless of the value for the ESIACTV generation option, an external
security call is always made to the SAF Security Interface using the resource
class of Z$CATAL with a resource name of RESTORE# and ALTER authority.
If this class information is not defined in your security package, then the SAF
action and return code are determined by your security product. If you do not
have a security product using SAF, Zekes internal security will be used, which
allows the request by default.
Caution! If you have a ZEKE15B user exit in place, then it can override any external
security return code depending on how you have defined ZEKE15B.
Note:
We recommend that you cycle OASIS after performing a database restore.

databases (primary and vault).
47
Syntax
RESTORE
blank indicates PHYSICAL;

this is the default
NEWCATLG
DISK
NEWCATID
OLD
NOMSG (default)
LOGICAL
DISK
MESSAGE
MERGE nnnnnnnn
NEWCATLG
NEWCATID
NOSCHED
PLEXID name
NOVAULT
Parameters
48
Parameter
Description
PHYSICAL
(default)
Caution! Do not specify this parameter.
LOGICAL
The database is reorganized (the event numbers are unchanged). The

pointers keep the event elements grouped together. This allows you to
merge two databases.
DISK
Restores the database from a disk file. The default is to restore from a
backup tape.
Zeke defaults to this parameter if you do not enter LOGICAL. The

physical portion of the backup is restored to the disk space. This
RESTORE is an exact copy of the backed up version.
Parameter
Description
MERGE
Use this parameter to merge the backup database with the existing
database. Do not perform the CREATE function. MERGE can only be
done with a logical restore. The LOGICAL parameter is required.
Enter the starting event number for the backup database's events. Choose
a number higher than any event number in the existing database. For
example, if MERGE 101 is entered, the backup database's event 1 is
renumbered 101, event 2 becomes 102, etc. The event numbers in
REFEVENT OCCURS clauses are adjusted accordingly. The event
numbers in the existing database are not changed. Duplicate variables,
calendars, and security records are dropped.
For example,
RESTORE LOGICAL MERGE 1001
Merge the backup database with the existing disk database. Event
number 1 is renumbered as 1001, event 2 becomes 1002, etc.
Note:
If you have changed any generation options, it may be necessary to

issue a ZRELOAD GENOPT after merging two databases. Otherwise,
variable substitution or other functions may be affected. If you are
using the unchanged generic SYSID record of generation options
(********), a ZRELOAD GENOPT is not needed.
MESSAGE
Lists detailed information in the job output regarding the records

restored. During a merge, detail of any duplicate records being dropped
is also listed. Only effective for a logical restore or merge.
NEWCATLG
Specify this option if the Zeke database was corrupted. Zeke maintains
a table of active CPU IDs. If the table was not cleared before the
RESTORE function, the NEWCATLG parameter must be used. Use this
parameter only if Zeke does not perform a normal CREATE/RESTORE
function.
NEWCATID
Specify this option if you are restoring or converting a Zeke database

from one release to another and plan to run both Zeke releases on the
same system, with one of the releases using the original database. If you
attempt to run multiple releases of Zeke on the same system without
using this parameter, both databases will have the same CATID and
various errors may occur. Use of this parameter will cause the newly
restored/converted database to have a new, unique CATID generated for
it by the CREATE process.
Do not use this parameter if you are using the CATID as part of any ESI
resource names. Contact the ASG Service Desk for assistance.
49
Parameter
Description
NOVAULT
Specify this option to exclude the vault information on the database

backup from the database you are currently restoring. This parameter
allows you to restore a database and use it without having to use the vault
it referenced.
For example,
RESTORE LOGICAL DISK MESSAGE NEWCATLG NOVAULT
Creates a logical restore from a disk file without the vault

information.
Note:
You must remove any reference to the vault from your started task JCL
or power startup or you will receive error message at Zeke startup.
NOMSG
No messages are listed. This is the default.
NOSCHED
Does not restore the schedule records. Only effective for a logical restore
or merge. Use of this parameter is recommended because usually the
schedule records on a backup tape are from the previous day's schedule
and are not desired. Another use for this parameter is for backups
containing downloaded SQRs.
Note:
If you are restoring a database prior to release 4.0, then NOSCHED is

the forced default.
OLD
50
Performs a physical restore of a backup tape. Cannot be used with the

LOGICAL parameter.
Parameter
Description
PLEXID
The 8-character name that uniquely identifies the Zeke database. Specify
this option to change the PLEXID name for the database.
Examples:
RESTORE PLEXID PT4X
Set PLEXID to PT4X during physical restore.

RESTORE LOGICAL PLEXID PT4X
Set PLEXID to PT4X during restore.

RESTORE LOGICAL PLEXID
Clear the PLEXID from the database.

To remove the PLEXID, specify the keyword PLEXID without a
PLEXID name.
RESTORE PLEXID
Sample JCL
The Zeke restore file DD name is ZEKERS. In the ZEKEUTL jobstream, enter the Zeke
backup file dataset name.
//ZEKEREST JOB
,MSGLEVEL=(1,1),CLASS=A
//STEP1
EXEC PGM=IEFBR14
//ZEKE
DD
DSN=ZEKE.MVS.CATALOG,DISP=(NEW,CATLG),
//
UNIT=SYSDA,SPACE=(CYL,(10))
//ZRS
EXEC ZEKEUTL
//ZEKECAT
DD
DSN=ZEKE.MVS.CATALOG,DISP=SHR
//ZEKERS
DD
DSN=ZEKE.BACKUP,DISP=OLD,
//
VOL=(,RETAIN,SER=ZEKETP),UNIT=TAPE,LABEL=(1,SL)
//ZEKENEW
DD
DSN=ZEKE.MVS.CATALOG,DISP=SHR,
//
UNIT=SYSDA,VOL=SER=ZEKEVL
//SYSIN
DD
*
RESTORE
/*
//ZEKEREST JOB ,MSGLEVEL=(1,1),CLASS=A
//ZRS
EXEC ZEKEUTL
//ZEKECAT
DD
DSN=ZEKE.MVS.CATALOG,DISP=SHR
//ZEKERS
DD
DSN=ZEKE.BACKUP,DISP=OLD,
//
VOL=(,RETAIN,SER=ZEKETP),UNIT=TAPE,LABEL=(1,SL)
//ZEKENEW
DD
DSN=ZEKE.MVS.CATALOG,DISP=SHR,
//
UNIT=SYSDA,VOL=SER=ZEKEVL
//SYSIN
DD
*
RESTORE LOGICAL MERGE 1001
/*
51
SCHEDULECreate the New Schedule

Selects the events due for processing and creates the schedule. The SCHEDULE
function:
Deletes completed events with a previous RDATE (run date).
If an event is manually added with a future RDATE, the event is NOT removed
from the schedule until the RDATE is reached (regardless of whether the event
has been completed).
If an event is manually added with an RDATE prior to the current date, the
event will be deleted only if the events status is DONE, or if the value for the
RETAIN option in the EMR is N.
Note:
To delete one or more events regardless of their RDATE, perform a SCHEDULE

CLEAR or manually delete the events.
Retains uncompleted events from the previous day's schedule.
Creates a schedule for a future date. (You can forecast an event schedule and make
changes.)
Analyzes each event defined to the database. Determines if the event hits during
the upcoming schedule period.
Caution! Unpredictable results may occur during schedule load function if schedule
functions are run simultaneously. Do not run more than one schedule batch job
at any time on any system or while any system is in tracking mode (ZKILL
WARM). Do not run the job that executes the SCHEDULE TODAY
ACTIVATE function until all previous schedule load has completed on all
systems. The schedule load is complete when system message Z530GI
SCHEDULE LOAD COMPLETE appears on the system console.
Caution! Do not execute multiple SCHEDULE TODAY ACTIVATE SYSIN functions
within one batch job. Unpredictable results may occur.
The typical schedule period is one working day, from 00:00 to 47:59 (47:59 in order to
select all events possibly due); however, any time range can be specified through a
SCHEDULE parameter.
For example, an installation performs the scheduling function three times a day, from
00:00 to 16:00, from 16:01 to 24:00, and from 24:01 to 47:59. This installation has a
working day from 8:00 am one day to 8:00 am the next divided into three shifts. This
installation's events are all scheduled in the range 08:00 through 32:00. All times from
00:00 to 47:59 must be covered.
52
As an alternative, this installation could run the SCHEDULE function once per day, before
8:00 am, the start of the work day (the 3rd shift processes events scheduled from 24:01 to
32:00 for the previous day). The SCHEDULE function maintains the database's SQRs.
There is an SQR for each event in the schedule. SQRs may be from previous schedule runs
if those events were not completed or disabled. Whether existing Schedule Records are
retained depends on several of the SCHEDULE statement parameters and EMR
specifications.
Note:
Zeke provides a user exit that allows you to change various fields in the SQR during the
schedule build. Refer to your ASG-Zeke OS/390 Installation Guide for more information
on the ZEKE02OX User Exit.
Forecasting
The command SCHEDULE with parameters, such as DATERANGE and GENERATE,
can produce reports covering a single day's schedule or several days in the future.
Do not include the ACTIVATE parameter when creating a forecast schedule run; the
ACTIVATE parameter updates the database with a new schedule.
Refer to your ASG-Zeke OS/390 Users Guide for more information on forecasting and
simulating the schedule, creating the Zeke schedule, and setting Zeke to schedule itself.
Syntax
SCHEDULE
TODAY
parameters
DATE mm/dd/yyyy
Parameters
Parameter
Description
TODAY
Uses the current system date as the schedule date.

For example,
SCHEDULE TODAY ...
DATE
Enter the date (in MM/DD/YYYY format) of the schedule run, if

other than the current date. If forecasting, do not use the ACTIVATE
parameter.
For example,
SCHEDULE DATE 12/31/2001 ...
53
Parameter
Description
ACTivate
Required to update the database with the new schedule. If omitted,

Zeke assumes the schedule run is for forecasting purposes.
For example,
Note:
Never run the SCHEDULE function for a future date when

ACTIVATE is specified because the current schedule will be
overlayed.
APPLication
Selects events with the specified application ID.

For example,
SCHEDULE TODAY ACTIVATE APP PAY
You can schedule up to 20 application IDs at one time. To do so,

enclose the set of IDs in parentheses and separate each ID with a
comma.
For example,
SCHEDULE TODAY ACT APP (APP1,APP2,APP3,
APP4,APP5,APP6,APP7,APP8,APP9)
Note:
Generics (such as *) cannot be used with the APPLICATION

parameter; if used, they are taken as literals.
CLEAR
Removes the schedule records with the specified criteria. You can
specify schedule records by group ID, application ID, and user ID.
For example,
SCHEDULE TODAY CLEAR APP=AAC GROUP=DEP USER=PAYRL
Removes the schedule records with an application ID of AAC, a

group ID of DEP and a user ID of PAYRL.
Note:
If a schedule record does not satisfy all the criteria specified in the
statement, the schedule record remains in the schedule.
To clear all Schedule Records, enter the following:
SCHEDULE TODAY CLEAR
54
Parameter
Description
DATASPACE
Creates a copy of the Zeke database in a temporary dataspace. Zeke

reads the event records from the temporary dataspace to create the
schedule. All schedule records are written to the active Zeke
database.
Note:
Using this parameter reduces the I/O against the database, the
duration of the database-wide enqueue, and the time required for a
schedule build.
DATERange
Enter up to 5 pairs of date ranges for a forecast schedule run. Enclose

in parentheses, and separate by commas or spaces. If an ending date
is not specified for the last pair, the same date as the starting date is
assumed. Refer to the GENERATE parameter.
For example,
SCHEDULE DATERANGE (11/15/2001,
11/25/2001,12/14/2001,12/18/2001)
Produces forecasts for November 15, 2001 through November

25, 2001 and December 14, 2001 through December 18, 2001.
DRL
Selects events with the specified disaster recovery level. Delimiters

are required around the value specified for DRL.
For example,
SCHEDULE TODAY ACTIVATE DRL (1-4,7)
Selects the following disaster recovery levels: 1 through 4, and 7

only
DROPOld
Deletes SQRs from a prior day regardless of completion status. If

omitted, the prior day's SQRs are deleted only if flagged as
completed or disabled or Retain was set to N in the EMR.
For example,
SCHEDULE TODAY ACTIVATE DROPOLD
55
Parameter
Description
GENerate
This parameter is used with the DATERANGE parameter. Enter the

code indicating how to produce the forecast schedule run reports.
RANGE
Default. Produce one report for each date pair.
DAY
Produce one report for each date in a range.
ONE
Produce one report for all the days.
For example,
10/03/2001,10/20/2001,10/22/2001) GENERATE RANGE
DATERANGE (10/01/2001,
10/03/2001,10/20/2001,10/22/2001)
Produces two sets of reports, one for each date pair.

10/03/2001,10/20/2001,10/22/2001) GENERATE ONE
Produces one report.

SCHEDULE DATERANGE
(10/01/2001,10/03/2001,10/20/2001,
10/22/2001) GENERATE DAY
Produces six reports, one for each date forecast.

GROupid
Selects events with the specified group ID. Up to 3 characters. For

example,
SCHEDULE TODAY ACTIVATE GROUP SAL
You can schedule multiple group IDs (up to 20) at one time. To do
so, enclose the set of IDs in parentheses and separate each ID with a
comma. For example,
SCHEDULE TODAY ACT GR (GRP1,GRP2,
GRP3,GRP4,GRP5,GRP6,GRP7,GRP8,GRP9)
Note:
Generics (such as *) cannot be used with the GROUPID parameter;

if used, they are taken as literals.
KEEPOld
Retains completed SQRs from a prior day's schedule. If omitted, the

prior day's SQRs are deleted if flagged as completed or disabled.
For example,
SCHEDULE TODAY ACTIVATE KEEPOLD ...
56
Parameter
Description
LISTDesc
Prints the event's description on the schedule report.
LISTEXit
Invokes user exit ZEKE02MX once for each event after all other
reporting for the event is done. Refer to your ASG-Zeke OS/390
Installation Guide for more information on the ZEKE02MX user
exit.
LISTNote
Prints the event's note information on the schedule report. For

example,
SCHEDULE TODAY ACTIVATE LISTNOTE
LISTOccurs
Prints the event's OCCURS clause on the schedule report.
LISTWhen
Prints the event's WHEN condition on the schedule report. For

example,
SCHEDULE TODAY ACT LISTOCCURS LISTWHEN
NOMsgs
Suppresses message Z02A1I during the schedule run. This message

gives the disposition of each schedule record as it is processed.
RDATE
The ACTIVATE parameter also allows you to specify an RDATE

value other than the default value of today. All events added to the
schedule will have the RDATE specified in the statement. For
example,
SCHEDULE TODAY ACTIVATE RDATE 2001364
Updates the schedule with an RDATE of 12/31/2001.

REBuild
Rebuilds existing SQRs for the current schedule date, as long as they
are still active (have not been dispatched). The rebuilt Schedule
Record reflects the updated Event Record information and resets all
WHEN conditions. This parameter is useful when the EMRs are
updated after the SQRs are created. For example,
SCHEDULE TODAY ACTIVATE REBUILD
Note:
ASG recommends that you rebuild individual schedule records by

using the ZADD REBUILD operator command.
57
Parameter
Description
START
Format HH:MM. From 00:00 (default) to 47:59. Enter the starting

time for this schedule run. Selects all events with a SCHEDULE
time equal to or greater than the specified time. Specifying a start
time will prevent the schedule from selecting events with no
schedule time. Ensure that all start times from 00:00 to 47:59 are
scheduled.
SCHEDULE TODAY ACTIVATE START 08:00
This example places events in the schedule that have a start time of
08:00 or greater. If it is desired to have events placed in the schedule
with start times from 00:00 thru 07:59, then a separate SCHEDULE
TODAY statement is necessary.
Note:
Use this parameter only if the schedule day is divided into

separately scheduled segments or time ranges.
STOP
Format HH:MM. From 00:01 to 47:59. Enter the ending time for this
schedule run. Selects all events with a SCHEDULE time equal to or
less than the specified time. Ensure that all times from 00:00 to 47:59
are scheduled.
SCHEDULE TODAY ACTIVATE START 08:01 STOP 16:00
This example places events in the schedule that have a start time
from 08:01 thru 16:00. If it is desired to have events placed in the
schedule with start times out of this range, then a separate
SCHEDULE TODAY statement is necessary.
Note:
Use this parameter only if the schedule day is divided into

separately scheduled segments or time ranges.
58
Parameter
Description
SYStemid
Selects only events that belong to the specified system ID. If omitted,
the schedule is run for all systems defined in the database.
USERid
Selects events with the specified user ID. The user ID can be up to 8
characters. For example,
SCHEDULE TODAY ACTIVATE USER PAYROLL
You can schedule multiple user IDs (up to 20) at one time. To do so,
enclose the set of IDs in parentheses and separate each ID with a
comma. For example,
SCHEDULE TODAY ACTIVATE US (USER1,
USER2,USER3,USER4,USER5,USER6,USER7)
Note:
Generics (such as *) cannot be used with the USERID parameter; if

used, they are taken as literals.
OVERRIDESelect Events
The OVERRIDE subfunction of the SCHEDULE function allows you to include or
exclude events from the schedule regardless of their OCCURS clauses. An event
specified in an OVERRIDE INCLUDE command is included even if the schedule run
time range does not include the event's schedule time.
For example, if the schedule function runs with START 08:00 and STOP 12:00 and event
4 has a schedule time of 16:00, normally the event is not selected because the schedule
time is out of the range. However, if event 4 is specified in an OVERRIDE INCLUDE
command, the event is selected, regardless of the schedule time.
Enter the OVERRIDE command before the SCHEDULE command or commands. It
remains in effect for the duration of the Zeke batch program.
schedule.
59
Syntax
OVERRIDE
INCLUDE
event list or ranges
EXCLUDE
Parameters
Parameter
Description
INCLUDE
Select the specified events.
EXCLUDE
Do not select the specified events.
event list or ranges Enter up to 62 single event numbers and/or 30 event ranges for
each OVERRIDE command. Enclose multiple event numbers
within parentheses and separate by commas or spaces. Separate
the beginning range event number and the ending number with a
hyphen (-). The beginning and ending event numbers are included
in the range.
Examples
The following are some examples of the OVERRIDE command:
OVERRIDE INCLUDE 2
Includes event 2.
OVERRIDE INCLUDE (3,15-30,45-60)
Includes events 3, 15 through 30, and 45 through 60.
OVERRIDE EXCLUDE (4 7)
Excludes events 4 and 7.
OVERRIDE INCLUDE 10 EXCLUDE (5 7)
Includes event 10 and excludes events 5 and 7.
60
Sample JCL
Typically, only one OVERRIDE command is entered per batch program, but if more than
one is entered, it is important to realize that each OVERRIDE command adds to and
subtracts from the previous OVERRIDE command selections. For example,
//SCH
EXEC ZEKEUTL
//SYSIN DD *
OVERRIDE INCLUDE 5
Includes event 5.
OVERRIDE INCLUDE (10 11)

SCHEDULE DATE 12/01/2001
Includes events 5, 10, and 11.
OVERRIDE EXCLUDE (30-40)

Includes events 5, 10, and 11;

excludes events 30 through 40.
/*
REPORTSelecting the Schedule Reports

The REPORT subfunction of the SCHEDULE function allows you to select which of the
reports to print, if you do not need them all. For example, if you are testing an OCCURS
clause of a new event or running a forecast schedule.
The SCHEDULE function, by default, prints 10 reports.
simulating the schedule, and creating the Zeke schedule.
61
Syntax
REPORT
INCLUDE
BACKJOBS
EXCLUDE
BACKLOG
COMMANDS
JOBS
MESSAGE
NEWEVENT
PENDING
REXX
TIMES
WORK
Parameters
62
Parameter
Description
INCLUDE
Print the specified reports.
EXCLUDE
Do not print the specified reports.
BACKJOBS
Specifies the BACKJOBS report, which includes job events not

completed from the prior day.
BACKLOG
Specifies the BACKLOG report, which includes events not completed

from the prior day.
COMMANDS
Specifies the COMMANDS report, which is the schedule of command

events.
JOBS
Specifies the JOBS report, which is the schedule of jobs to be

processed.
MESSAGE
Specifies the MESSAGE report, which is the schedule of message

events.
NEWEVENT
Specifies the NEWEVENT report, which includes events added by the

schedule function.
PENDING
Specifies the PENDING report, which includes events pending or

abended.
REXX
Specifies the REXX report, which is the schedule of REXX events.
Parameter
Description
TIMES
Specifies the TIMES report, which is the schedule listing for a certain
time range (HH:MM through HH:MM).
WORK
Specifies the WORK report, which is the schedule of work center

events.
Sample JCL
Enter the REPORT command before the SCHEDULE command or commands. It
remains in effect for the duration of the Zeke batch program.
Typically, only one REPORT command is entered per batch program, but if more than
one is entered, it is important to realize that each REPORT command adds to and
subtracts from the previous REPORT command selections. For example,
//SCH
EXEC ZEKEUTL
//SYSIN DD *
REPORT EXCLUDE NEWEVENT JOBS
REPORT INCLUDE NEWEVENT
/*
Prints all reports.

Prints all reports except for NEWEVENT and JOBS.
Adds NEWEVENT; prints all reports except for JOBS.
63
VAULTControlling the Vault Dataset

Purpose
Disables electronic vaulting while Zeke is down.
Note:
See also "Disabling Electronic Vaulting" on page 178 for information on performing this
function using the ZDISABLE operator command.
If the vault is disabled via batch, then remove the ZEKEVLT DD namefrom the Zeke
started task JCL before starting Zeke again. Failure to do so will result in vault
initialization.
Be sure to add the ZEKEVLT DD to the batch jobs JCL.
databases (primary and vault) and recovery using electronic vaulting.
Syntax
VAULT DISABLE
Simulating the Schedule

Simulating a Zeke schedule enables you to create a simulation of the schedule and
produces reports as if the schedule had actually run. This function provides a way to test
the runtime of a schedule based on various factors, such as newly added jobs, or reduced
or increased resources.
Caution! Do not run the simulation function against the production database. Run
simulation against a simulation-copied database only. No other Zeke system
should be running against the same database as simulation. Running the
simulation function against the production database will destroy the production
database.
Note:
Simulation jobs must be run against the same subsystem that Zeke is running under.
64
SIMULATESimulating the Schedule

Creates a simulation of the Zeke schedule and produces schedule reports.
simulating the schedule.
Syntax
SIMULATE
STARTDATE date
STOPTIME time
STARTTIME time
DATABASEDD ddname
STOPDATE date
parameters
Parameters
Parameter
Description
STARTDATE
Format MM/DD/YYYY or YYYYDDD. Enter the simulation start

date. For example,
SIMULATE STARTDATE 01/01/2001
STARTTIME
Format HH:MM; from 00:00 to 24:00. Enter the simulation start time.
For example,
SIMULATE STARTTIME 00:00
STOPDATE
Format MM/DD/YYYY or YYYYDDD. Enter the simulation stop

date.
SIMULATE STOPDATE 01/02/2001
STOPTIME
Format HH:MM: from 00:00 to 23:59. Enter the simulation stop time.
SIMULATE STOPTIME 23:59
DATABASEDD
Enter the simulation database DD name. The DD name can be up to

9 characters.
SIMULATE DATABASEDD OUTCAT
Note:
If you specify the COPY parameter, you must specify the same
value for TODD as for DATABASEDD. If both TODD and
DATABASEDD are the word DATASPACE, the simulation
database is copied to a data space. "Running Simulation from a Data
Space" on page 71
65
Parameter
Description
SYSTEM
Enter the name of the system you want to simulate.

SIMULATE SYSTEM MVSSPA
Note:
If the simulation schedule run schedules no events with this system

name, no event dispatching will be simulated. Only one system can
be simulated. If multiple system parameters are entered, all but the
last one are ignored.
INITIATORS
Enter the number of available initiators, from 1-230.

SIMULATE INITIATORS 10
Note:
If more initiators are specified than are defined in the GENSYS

record for the system, simulation generates its own initiator names.
TAPEDRIVES
Enter the number of available tape drives, from 1 to 999.

SIMULATE TAPEDRIVES 5
SATISFY
Enter the conditions to be automatically satisfied. Unless you use this

parameter and specify a condition, the simulation process assumes
there are no conditions to be automatically satisfied. You can use one
or more of the following conditions:
ALL*
AEOP
AEOS
BOP
DSN
EOP
EOS
AT***
OPOK
UOCCEXIT
VAR
WHEN**
WRKCNTR
* Satisfies all of the conditions.

** Specifying this condition excludes satisfaction of OPOK, UOCCEXIT, VAR, and
WRKCNTR.
*** Satisfies all WHEN conditions with remote prerequisites.
For example,
SIMULATE SATISFY OPOK
66
Parameter
Description
SCHEDRUN
Indicate when to run the schedule function.
SCHEDCLR
DAILY*
Run the schedule every 24 hours during simulation.
YES
Run the schedule once, at the beginning of

simulation.
OFF
Do not run the schedule function.
Indicate whether to run the schedule clear function.

YES*
Run the schedule clear once, at the beginning of

simulation.
OFF
Do not run the schedule clear function.
Note:
To simulate your current, existing schedule, perform SIMULATE COPY against the
existing database and schedule records with SCHEDRUN and SCHEDCLR set to OFF.
APPLICATION Specify only for schedule run or schedule clear. Selects events with
the specified application ID. If omitted, events with any application
ID are selected.
GROUPID
Specify only for the schedule or schedule clear. Selects events with
the specified group ID. If omitted, events with any group ID are
selected.
USERID
Specify only for schedule run or schedule clear. Selects events with
the specified user ID. If omitted, events with any user ID are selected.
SYSTEMID
Selects events belonging to the specified system ID. If omitted, the

schedule is run for all systems.
REPORT
This parameter starts the simulation report writer and specifies the
output reports. Must be followed by one or more subparameters.
To print reports from a previous simulation run, ensure that the
ZKSMLOG dataset was saved from the previous run. Then, specify
only REPORT parameters in the SYSIN control statements and point
the ZKSMLOG DD to the saved log. You do not need to rerun the
simulation.
ALL
Prints all simulation reports.

SIMULATE REPORT ALL
67
Parameter
COPY
Description
CONSOLE
Prints the console log from the simulation run.
EXCEPTION
Prints the exception report from the simulation run.
JOBFLOW
Prints the initiator job flow report from the

simulation run.
SCHEDULE
Prints the simulation schedule report.
LINES
Number of lines per page for the report. Defaults to

60.
Starts the simulation copy function and requires subsequent

parameters. Use the COPY parameter to copy a Zeke database. To
perform a successful copy:
COPY must be followed by the FROMDD and TODD

subparameters.
Zeke must be active and pointing to the database to be copied.
You must use the same SUBSYS Zeke is using. Otherwise,

you will receive a U974 user failure.
FROMDD
Enter the source database DD name the simulation

function is copying; use with the copy parameter.
TODD
Enter the destination database DD name the

simulation function is copying; use with the COPY
parameter.
COPY FROMDD=INCAT TODD=OUTCAT
TODD must have the same value as

DATABASEDD. If both values are the word
DATASPACE, the simulation database is copied to
a data space. "Running Simulation from a Data
Space" on page 71
68
The following is a sample jobstream to execute Zeke simulation:
//SIMULATE JOB ,(USER),CLASS=A,MSGCLASS=A

//ZKSM
EXEC PGM=SSS4001,REGION=0K,TIME=1440,
//
PARM='XPROC=JKMX240,OASIS=(OO,L),ZEKE=(ZZ,L,SIM),SUBSYS=SNAM,END'
//SYSPRINT DD SYSOUT=*
//SYSOUT
DD SYSOUT=*
//SYSOUT
DD SYSOUT=*
//SYSABEND DD SYSOUT=*
//PARMLIB DD DSN=OASIS.PARMLIB,DISP=SHR
//INCAT
DD DSN=ZEKE.USER.DATABASE,DISP=SHR,
//
UNIT=3380,VOL=SER=ASWDLB
//OUTCAT
DD DSN=ZEKE.SIMULATE.DATABASE,DISP=SHR,
//
//ZKSMLOG DD DSN=ZEKE.REPORT.LOG,DISP=SHR,
//
UNIT=3380,VOL=SER=ASWDLB,
//
DCB=(LRECL=256,BLKSIZE=5124,RECFM=VB)
//SORTWK01 DD DSN=&&SORTWK01,DISP=(NEW,DELETE,DELETE),
//
SPACE=(CYL,(10,5)),UNIT=3380,VOL=SER=ASWDLB
//ZEKEVLT DD DSN=ZEKE.VAULT.DSN,DISP=SHR
Only required if using
electronic vaulting
//SYSIN
DD *
COPY
FROMDD=INCAT TODD=OUTCAT
SIMULATE
STARTDATE 01/01/2001 STARTTIME 23:00
STOPDATE 01/02/2001 STOPTIME 22:59
DATABASEDD OUTCAT
SATISFY ALL
INITIATORS 10
SYSTEM MVSSPA
TAPEDRIVES 5
REPORT ALL
//
69
This jobstream is similar to the previous one; however, it is not necessary to repeat the
COPY function once you have copied the dataset. You can change values for any of the
parameters and run a different schedule simulation using the same dataset.
Note:
If you are not performing a COPY, Zeke does not need to be active.

//*
//ZKSM
EXEC PGM=SSS4001,REGION=0K,TIME=1440,
//
//SYSOUT
DD SYSOUT=*
//OUTCAT
//
//
//
//
electronic vaulting
//SYSIN
DD *
SIMULATE
DATABASEDD OUTCAT
SATISFY ALL
INITIATORS 5
SYSTEM MVSSPA
TAPEDRIVES 3
REPORT ALL
//
70
This jobstream is only for printing reports. The ZKSMLOG DD provides the data for the
reports and was generated by a previous simulation run.

//*
//ZKSM
EXEC PGM=SSS4001,REGION=0K,TIME=1440
//
//SYSOUT
DD SYSOUT=*
//OUTCAT
//
//
//
//
electronic vaulting
//SYSIN
DD *
REPORT ALL
//
Running Simulation from a Data Space

You can run simulation where the simulation copy of the database is created in an OS/390
data space rather than on DASD. This can result in a significant reduction in the running
time of the job and the amount of I/O it performs. However, the data space containing the
simulation database is discarded at the end of the job. If you wish to save the schedule, or
any other database updates made by the simulation run, you must run simulation with its
database on DASD.
71
To place the simulation database in a data space, use the special DD name DATASPACE
in the TODD parameter of the COPY command and the DATABASEDD parameter of
the SIMULATE command.
//SIMULATE JOB (USER),CLASS=A,MSGCLASS=A,

//ZKDSPSIM EXEC PGM=SSS4001,REGION=0K,
//
//PARMLIB DD DSN=USER.PROCLIB,DISP=SHR
//SYSOUT
DD SYSOUT=*
//*
//INCAT
DD DISP=SHR,DSN=ZEKE.PROD.DBASE
//ZKSMLOG DD DSN=ZEKE.REPORT.LOG,
//
SPACE=(CYL,(5,5),RLSE),
//
DCB=(RECFM=VB,LRECL=256,BLKSIZE=5124),
//
DISP=SHR
//SYSIN
DD *
COPY
FROMDD=INCAT TODD=DATASPACE
SIMULATE
SATISFY ALL
INITIATORS 7
INSTANCE SYSNAME
DATABASEDD DATASPACE
REPORT ALL
//SORTWK01 DD DSN=&&SORTWK01,DISP=(NEW,DELETE),
//
SPACE=(CYL,(3,16)),UNIT=3380,VOL=SER=ZEKEPK
//SORTWK02 DD DSN=&&SORTWK02,DISP=(NEW,DELETE),
//
SPACE=(CYL,(3,16)),UNIT=3380,VOL=SER=ZEKEPK
72
2ZEKESET
Zeke control statements, executed by the ZEKESET program, provide ways to:
Control jobstream flows
Assist in abnormal termination recovery
Interact with user programs through variables
Interact with scheduling function for event triggering
Generate large block letter separator or routing pages
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
SET Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Statement Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET ABENDTerminate a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET ROUTECreating Large Block Letter Separator Pages . . . . . . . . . . . . . . . . . . . .
SET xCOMIssuing System and Zeke Commands . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET VARIABLEDefining Zeke Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET COMMENTAdd Comment Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET CONDCODE or SET RETCODESet Condition or Return Codes . . . . . . . . . . .
SET GOTOBranch within Control Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET WAITSetting a Wait Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OPTION NOSUBVariable Substitution in ZEKESET . . . . . . . . . . . . . . . . . . . . . . . .
CDATEDate Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ON ERRORSyntax Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
75
75
79
79
81
82
84
84
86
87
87
88
95
73
Overview
You can control jobstream flow by using ZEKESET to:
Set variables
Set the step condition code
Set a user abend code
Execute Zeke operator commands
Execute OS/390 commands, JES commands, or VM commands.
To use the program features, you execute the ZEKESET program in any job stream.
ZEKESET functions can be made conditional by using the IF clause of the SET statement.
Control statements follow the same syntax rules as Zeke batch utility input statements
(refer to "General Information" on page 2).
To use the ZEKESET program

}
Execute the following program in any jobstream to execute the job control SET
statements.
//ZSET
JOB
,ZEKESET.SAMPLE,CLASS=A
//ZSAMPLE EXEC PGM=ZEKESET,PARM=SUBSYS=SSSI
//SYSPRINT DD
SYSOUT=A
//SYSIN
DD
*
SET ROUTE (SAMPLE ROUTING PAGE)
SET ABEND 4 IF $ABENDCODE GT 1
/*
The control statements are read from SYSIN and are listed along with informational and
error messages using the DD name SYSPRINT.
Note:
When Zeke submits JCL and encounters a PGM=ZEKESET on an EXEC statement, data
substitution is turned off until the next EXEC statement is encountered.
74
2 ZEKESET
SET Statement
The SET statement performs the following functions:
Any of the above functions can be made conditional by using the IF clause of the SET
statement.
Statement Syntax
SET statements follow the same syntax rules as the ZEKE batch utility input statements
(refer to "General Information" on page 2 for details).
Separate parameters and operands by either an equal sign (=) or by one or more
spaces.
Separate multiple operands within parentheses by a comma or by one or more

spaces.
Separate parameters by a comma or by one or more spaces.

Note:
Use either a comma or one or more spaces to separate items, but not both. A comma
followed by a space indicates end of statement to Zeke.
Precede comments with a comma and at least one space. For example,
SET VAR $LS EQ STEP1 ,
Note comma prior to this comment.
SET VAR $ABC EQ OK ,
Any Zeke statement can have a comment.
SET ROUTE (WORD1 WORD2 ,
A comma must precede the comment.
Complete each ZEKESET statement on a single line (columns 1 to 72).

Continuation statements are not supported by the ZEKESET program.
If you are running multiple versions of Zeke, the EXEC card must include the
subsystem name, if other than SSSI.
//Z1 EXEC
PGM=ZEKESET,PARM=SUBSYS=subsystem name
75
Comments and blank lines are supported. Any line with an asterisk as the first
non-space character is considered a comment line. Comment lines and blank lines
are printed, and are otherwise ignored. Comments can also be placed after a comma
on the same line as a ZEKESET input statement. For example:
CDATE OUTDATE EQ DATE
Set to current date
If desired, you can indent input lines and comment lines for better legibility.
IF Clause of the SET Statement

The IF clause of the Zeke SET statement makes the statement conditional. When the IF
clause is true, Zeke processes the SET statement. When the IF clause is false, the SET
statement is bypassed.
The format of the IF clause is:
IF DATA1 OPERATOR DATA2
where OPERATOR can be any of the following:

EQ
EQual
LE
Less than or Equal
LT
Less Than
GT
Greater Than
GE
Greater than or Equal
NE
Not Equal
DATA1 and DATA2 refer to the "Special Names" described in the following section.
These special names are referenced by several commands. IF clauses on SET statements
can check certain special names in addition to checking variables.
Examples
The following are sample conditional SET statements:
SET VAR $XYZ EQ NO IF $ABC EQ YES
SET PCOM 'R RDR,JOB1' IF PARTN EQ BG
SET VCOM 'CP DRAIN 00E' IF ZEKECPU EQ A
76
2 ZEKESET
SET CONDCODE 4 IF ZEKECPU EQ A

SET ABEND 010 IF LASTCOND GT 4
SET VAR $STPNAME EQ WKLY003 IF $VARNAME1 LE 57
SET CONDCODE 20 IF TIME LE 080000
SET VAR $PR01STP EQ OK IF $PRFLAG EQ NORMAL
SET VAR $BADNEWS EQ *JOB-CANCEL* IF ABTYPE NE NO
SET GOTO BYPSTMTS IF ABTYPE EQ SYSTEM
Special Names
DATA1 and DATA2 of an IF clause can be any of the special names listed below;
however, the value for DATA1 must have the same data type as the value for DATA2.
For example, if the special name is numeric only for DATA1, then the special name must
be numeric only for DATA2. Special names cannot be used as the object of SET
statements.
Note:
The difference between special names and Zeke variables is that special names are
pre-defined to Zeke, while Zeke variables are user-defined and begin with a dollar sign
($).
Special Name
Data
Type Description
ABCODE
The abend code value, if an abend occurred.
ABTYPE
A/N
The abend type, if an abend occurred:

NO
USER
SYSTEM
FLUSH
COMRC
The return code from CP after issuing a SET VCOM

statement.
CPUID
A/N
The CPU serial number (for example, 123456).
77
Special Name
Data
Type Description
DATE
A/N
The current system date (MM/DD/YYYY or

DD/MM/YYYY).
Note:
DATE cannot be used in greater than or less than

comparisons because the year is not compared first. For
example, if DATE contains 12/15/2001 and is compared to
02/02/2001, the result is that the value contained in DATE
is greater than 04/30/2001 because 12/15 is greater than
04/30. Use the DATEJ special name to compare a date.
78
DATEJ
The Julian system date (YYYYDDD).
DAY
The day of the week; a numeric value from 1 to 7 (MON

through SUN).
EVENT
The event number of this job, if it is a Zeke job event.
HIGHCOND
The numeric value of the highest condition code of any step

in this job.
JOBNAME
A/N
The name of the current job.
LASTCOND
The value of the condition code for the previous job step.
LASTPGM
A/N
The name of the program executed by the previous job step.
LASTSTEP
A/N
The name of the previous job step.
THISPGM
A/N
The name of the program executed by this job step.
THISSTEP
A/N
The name of the current job step.
TIME
The current system time (HHMMSS format). If the hour is

less than 10, the leading zero is dropped.
VERSION
The 1- to 5-digit number identifying a particular version of

the event.
ZEKECPU
A/N
The Zeke CPU name for this system.
$XXXXX
A/N
XXXXX represents a Zeke variable.
LITERAL'
A/N
Any character string up to 64 bytes that is delimited.
2 ZEKESET
Special Name
Data
Type Description
NNN
Any explicitly stated numeric value.
XXX
A/N
Any explicitly stated character value that contains no special

characters.
SET ABENDTerminate a Job

The SET ABEND statement immediately terminates a job with any user abend code. No
more control statements in the input stream are executed.
For example:
SET ABEND 1,
User 1 Abend.
SET ROUTECreating Large Block Letter Separator Pages

TheSET ROUTE statement generates large block letter separator pages. Separator pages
are produced on the dataset allocated to SYSPRINT.
ROUTE specifies the word or words to be printed in large block letters. You can enter up
to ten words, and each word can contain up to eight characters. Each word specified is
printed in large block letters on the generated separator page separated by three blank lines.
(Each word is printed on the same page).
Enter multiple routing words within a single set of parentheses. For example,
SET ROUTE (WORD1 WORD2 WORD3 ...
Add the following parameter to print the same separator page multiple times.
Parameter
Description
COPY
Print the same separator page up to 10 times in a row.

Example:
SET ROUTE JOBNAME COPY 2
Prints two copies of a routing page with the job name in large block letters.
Zeke variables and special names can be used as the operand of the ROUTE parameter.
When Zeke variables are used, the value of the variable is the word that is printed in large
block letters. When Zeke special names (ZEKECPU, COMRC, DATEJ, ABTYPE,
ABCODE, etc.) are used, the value of the special name is printed.
79
Character values are truncated to the first eight characters, and numeric values are always
considered to be eight-digit decimal numbers.
Large block letters are printed for the letters of the alphabet (A through Z), the digits zero
through nine (0 through 9), and the special characters $, *, ., -, and /. Other
special characters are treated as blanks.
Examples
The following are examples of the SET ROUTE format:
SET ROUTE DATACTL
Specifies one routing word.
SET ROUTE (DATA CONTROL)
Specifies two routing words.
SET ROUTE (Give to sys programmer)
Specifies four routing words.
SET ROUTE (Job name this step)
Specifies special names for two routing words.
SET ROUTE $VAR1
Specifies a variable for a routing word.
SET ROUTE (JOBNAME $VAR1 **SAVE**)
Specifies a combination of a special name, variable, and a literal.
SET ROUTE JOBNAME COPY 2
Prints two copies of a routing page with the job name in large block letters.
80
2 ZEKESET
SET xCOMIssuing System and Zeke Commands

The SET statement can issue OS/390VSE commands, JES commands, Zeke operator
commands, VM/SP CP commands. The commands are issued by Zeke as the SET
statement is processed.
Requirements for the SET xCOM statement are as follows:
Each statement must specify one of the following codes followed by a comma and
the command or response.
Code
Meaning
OS/390, JES, or sSystem command
VM command/CP command
System response (VSE only)
Zeke command
VSE/POWER command (VSE only)
The statement must be enclosed in delimiters.
Examples
The following are examples of the SET command:
SET SCOM 'D A,L'
OS/390 DISPLAY ALL command.
SET SCOM '$PI I4'
JES2 pause of initiator.
SET VCOM 'MSG OPERATOR HI THERE'
Send a CP message to an operator.
SET ZCOM 'ZREFRESH JOB TSTA0500'
Zeke operator command.
SET ZCOM 'ZID ZMAP ZD AV'
System ID, initiator mapping, initiator availability.
SET VCOM 'M BOB HAVE A NICE DAY'
Send a VM message to a CMS user.
81
The IF clause makes the SET statement conditional. For example,

SET SCOM $TI I1,A IF ZEKECPU EQ A
When Issuing CP Commands

When Zeke issues a CP command from a SET VCOM statement and encounters a
non-zero return code from CP, Zeke waits one second and issues the command again.
Zeke retries the command ten times, issues a message to the operator specifying the
return code from CP, and bypasses the SET VCOM statement.
To modify the number of retry attempts, use the RETRY parameter followed by the
number of retry attempts, from 1 to 10. For example,
SET VCOM 'SMSG USERID HI THERE' RETRY 3
Retry 3 times
To check the CP return code after a set VCOM statement is issued, use the IF clause with
the special name COMRC. The value of COMRC is the CP return code provided to Zeke.
SET VARIABLEDefining Zeke Variables

The SET VARIABLE statement defines Zeke variables and changes existing variable
values. If a variable in a SET statement is not already defined in the database, it is added
and processing continues. Refer to your ASGZeke OS/390 Users Guide for additional
information on using variables.
A variable can be set to any of the following values:
Another Zeke variable
A numeric value (up to eight places) explicitly stated (any leading zeros are
truncated)
A character value (up to 64 characters) explicitly stated or contained in delimiters

(any trailing blanks are truncated)
One of the special names supported by the IF clause of the SET statement, such as
COMRC
The variable assumes the format, numeric or character, of the value it is set to. When a
variable is set to a numeric value, it can be set to plus and/or minus another value. This is
done by using the operators (+) and (-) to add and subtract other values, respectively. A
space must precede and follow either symbol.
82
2 ZEKESET
Note:
You can use both a plus (+) and a minus (-) on the same statement. However, only one
plus and one minus can be used per statement. For example,
SET VAR $VAR1 EQ $A + $B - $C
This statement is valid.
SET VAR $VAR1 EQ $A + $B + $C
This statement is not valid.
Examples
The following are examples of the SET VARIABLE statement:
SET VAR $VARNAME EQ OPER1
Alphanumeric format.
SET VAR $VARNAME EQ OPER1 + OPER2 - OPER3
Numeric format.
SET VAR $XYZ EQ NO,
Sets variable to the character value NO'.
SET VAR $OPERFLAG EQ 'YES',
Sets variable to the character value YES'.
SET VAR $CTR1 EQ 400,
Sets variable to the numeric value 400.
SET VAR $CTR2 EQ $CTR1 + 1,
Adds 1 to the value of $CTR1 and sets $CTR2 to that numeric value.
SET VAR $CTR EQ $CTR + 1 ,
Increments the variable value by 1.
SET VAR $A1 EQ $A2 + $A3 - $A4
Adds values of $A2 and $A3, subtracts that sum from $A4, and sets $A1 to that
result.
SET VAR $B1 EQ $B1 + $B2 - 1,
Adds values of $B1 and $B2, subtracts 1 from that sum, and sets $B1 to that result.
SET VAR $KAM EQ EVENT ,
Sets variable $KAM to the event number of the event that set the variable.
83
SET COMMENTAdd Comment Lines

You can document the processes you have applied in the ZEKESET execution. Use the
COMMENT parameter to specify from 1 to 40 bytes of comments per SET COMMENT
statement. For example:
SET COMMENT (THIS PROGRAM EXECUTES DAILY)
SET CONDCODE or SET RETCODESet Condition or Return Codes

The SET CONDCODE and SET RETCODE statements have the same function.
Use the SET CONDCODE or SET RETCODE statement to set condition or return codes
within the ZEKESET program.
The ZEKESET job step condition code, sometimes called the return code or completion
code, is normally set to zero by the ZEKESET program. However, if errors are detected in
the input control statements, the condition or return code is set to 4, 8, or 12, depending on
the type of error. You can also use the SET CONDCODE nnnn statement or SET
RETCODE statement to set the condition or return code to any value from zero to 4095.
If a user-defined value is set, that value is used when the program terminates. ZEKESET
never overrides a user-set condition or return code. In other words, if errors are detected
in the input stream, but a SET CONDCODE or SET RETCODE statement was
successfully processed, the normal error code is ignored and the user-defined value is used
in its place.
If more than one SET CONDCODE or SET RETCODE statement is processed, the last
value set is the one that is used for the step condition or return code. This allows you to set
the condition or return code based on the value of other data or other conditions. For
example, a condition or return code can be set by a statement in the ZEKESET input
stream, then changed by one or more following statements. This feature allows control of
the Zeke jobstream flow.
The ability to set the step condition or return code can be used with the Zeke special
names LASTCOND and HIGHCOND. These special names represent the highest
condition or return code from the last step executed and the highest condition or return
code encountered in the jobstream, respectively. These names can be used in the IF
portion of a Zeke job control SET statement to test the ZEKESET condition or return
code or any other job step condition or return code. For example,
//JSO10 EXEC PGM=ZEKESET,PARM=SUBSYS=SSSI

SET CONDCODE 99 IF DAY EQ 7
SET ROUTE (ABEND) IF LASTCOND EQ 99
/*
84
2 ZEKESET
The SET CONDCODE or SET RETCODE statement can be used with the OS/390 job
control EXEC statement parameter COND=' to control the sequence of steps executed
within a jobstream. Execute ZEKESET at any point within a job and set the step condition
or return code to any value. Based on the current day, time, date, the CPU-ID, a variable
value, the return code of a previous step, an abend code, etc., test the new condition or
return code through the COND parameter of a subsequent EXEC statement to execute or
bypass the remaining steps as desired.
The following example enables a step return code completion of 12, if the variable is equal
to 6:
//ZSAMP JOB ,ZEKESET.SAMPLE,CLASS=A

//JSO10 EXEC PGM=ZEKESET,PARM=SUBSYS=SSSI
//SYSIN DD *
SET RETCODE 12 IF $VARNAME EQ 6
/*
//
Another example:

//CKDAY EXEC PGM=ZEKESET,PARM=SUBSYS=SSSI
//SYSIN
DD *
SET RETCODE 99 IF DAY EQ 1
/*
//S1
EXEC PGM=PROG1,COND=(99,EQ,CKDAY)
//S2
EXEC PGM=PROG2
//CKS2 EXEC PGM=ZEKESET,PARM=SUBSYS=SSSI
//SYSIN DD *
SET RETCODE 12 IF LASTCOND GT 1
SET RETCODE 0 IF LASTCOND EQ 53
/*
//S3
EXEC PGM=PROG3,COND=(12,EQ,CKS2)
//
85
The following is a description of the example:
The first job step executes the program ZEKESET. If the current day is Monday,
the step terminates with a return code of 99. Otherwise, the return code is zero.
If the current day is Monday, the second job step (S1) is not executed, because the
EXEC statement COND parameter specifies to bypass the step if the return code
from step CKDAY is equal to 99.
The job step CKS2 executes ZEKESET again.
If the previous step (S2) has a return code greater than 1 and less than 53, the
ZEKESET step completes with a return code of 12.
If the previous step (S2) has a return code of 53, the ZEKESET step
terminates with a return code of zero. This return code determines whether the
final step, S3, is executed.
SET GOTOBranch within Control Statements

Use the ZEKESET statement SET GOTO to bypass control statements in the input
stream. This facility operates similar to branching within a program; however, SET
GOTO cannot branch backwards.
The statement specifies a label to be searched for. Labels are coded as the first non-blank
item on a control statement. The label name can be from 1 to 64 characters in length and
must end with a colon (:). Statements containing labels cannot contain other SET
commands. A label statement contains only the label name followed by the colon. If a
specified label cannot be found, processing terminates.
All control statements between the GOTO statement and the specified label statement are
bypassed as shown in the following figure. This includes all conditional and unconditional
SET statements, even other GOTO statements.
.
.
.
.
.
.
.
.
LABEL1:
.
.
86
SET GOTO LABEL1
2 ZEKESET
Any of the special names previously described can be used in a GOTO statement IF clause.
For example,

//S1
EXEC
PGM=PROG1
//S2
EXEC
PGM=ZEKESET,PARM=SUBSYS=SSSI
//SYSPRINT DD
SYSOUT=A
//SYSIN DD *
SET CONDCODE 4
SET CONDCODE 12 IF LASTCOND GT 4
SET GOTO STEP-WAS-OK IF LASTCOND EQ 0
SET ROUTE (STEP S1 HAD NON-ZERO COND CODE)
SET GOTO CONTINUE
STEP-WAS-OK:
SET ROUTE (STEP S1 WAS SUCCESSFUL)
CONTINUE:
SET VAR $FLAG EQ DONE
/*
SET WAITSetting a Wait Interval

To delay processing between ZEKESET statements, specify the number of seconds (from
1 to 9999) to wait in the SET WAIT statement. When the number of seconds is passed,
processing continues with the next statement. For example,
SET WAIT 10
ZEKESET waits at this statement for 10 seconds
You can use SET WAIT to allow a previous command time to process before issuing
another command.
OPTION NOSUBVariable Substitution in ZEKESET

The OPTION NOSUB statement allows you to stop variable substitution during the
execution of ZEKESET. This option is particularly useful if you have event names that
do not begin with letters (for example, that begin with a dollar sign). To turn variable
substitution back on, enter the statement OPTION SUB or exit the ZEKESET program.
The following example executes the ZEKESET program without variable substitution.
//ZSET
JOB
//ZSAMPLE EXEC
//SYSPRINT DD
//SYSIN
DD
OPTION NOSUB
SET WAIT $VAR1
/*
PGM=ZEKESET,PARM=SUBSYS=ZDEV
SYSOUT=A
*
87
The following example enables variable substitution in the ZEKESET program.
//ZSET
JOB
//ZSAMPLE EXEC
//SYSPRINT DD
//SYSIN
DD
OPTION SUB
SET WAIT $VAR1
/*
PGM=ZEKESET,PARM=SUBSYS=ZDEV
SYSOUT=A
*
Note:
The difference between using OPTION NOSUB and ZEKE-CTL NOSUB to turn off
variable substitution is that OPTION NOSUB turns it off at statement execution time,
while ZEKE-CTL NOSUB turns it off at variable substitution time, just prior to dispatch
of the event. Refer to your ASGZeke OS/390 Users Guide for more information on
ZEKE-CTL NOSUB.
CDATEDate Calculations
The CDATE function of ZEKESET performs date calculations using Zeke variables.
These variables can then be used for variable substitution. The variables are specified
without the $ so that if Zeke submits the ZEKESET job, it does not perform variable
substitution and overlay the variable names.
Syntax
CDate target = source operation
Parameters
88
Element
Description
target
The variable the result is stored in.
= (equal)
Can also be entered as EQ.
source
The variable that contains the date to be modified. Only one source
variable is allowed. Dates cannot be added together.
2 ZEKESET
Element
Description
operation You can use an operator and modifier together, use the DAY.x parameter
in addition to the operator and modifier, or use the DAY.x parameter
alone:
operator A plus sign (+) or minus sign (-). This indicates whether
the value is to be added to or subtracted from the numeric
value specified.
modifier A numeric value (either a variable or an actual number)
followed by one of the following modifiers:
DAY.x
DAY
DAYS
If only a numeral is specified, DAY(S) is

the default.
WEEK
WEEKS
Number of weeks.
MONTH
MONTHS
Number of months.
YEAR
YEARS
Number of years.
CDATE supports the DAY.x and DAY.L keywords,

which you may recognize from OCCURS clauses. The
DAY.x parameter determines the specified day of the
month in question, where x is either a numeric value from
1 to 31 or the letter L (to determine the last day of the
month in question).
The DAY.x parameter can be used in addition to other
operators and modifiers, or it can be used in place of an
operator and modifier. For example,
CDATE OUTDATE EQ INDATE DAY.11
If the value of INDATE is 12/14/2001, the eleventh

day of the month is determined, and a final date value
of 12/11/2001 is returned.
CDATE OUTDATE EQ INDATE DAY.L
If the value of INDATE is 12/14/2001, the last day of

the month is determined, and a final date value of
12/31/2001 is returned.
89
Element
Description
CDATE OUTDATE EQ INDATE + 1 MONTH DAY.5
If the value of INDATE is 12/14/2001, one month is

added to it, and the fifth day of the resulting month is
determined. This yields a final date value of
01/05/2002.
CDATE OUTDATE EQ INDATE + 1 WEEK DAY.L
If the value of INDATE is 12/14/2001, one week is

added to it, and the last day of the resulting month is
determined. This yields a final date value of
12/31/2001.
CDATE OUTDATE EQ INDATE DAY.L + 1 WEEK
If the value of INDATE is 12/14/2001, the last day of

the month is determined, and one week is added to the
result. This yields a final date value of 01/07/2002.
Source/Target Variables
The default date format is MM/DD/YYYY (or DD/MM/YYYY if using European
format). To override this format, specify the appropriate format in parentheses following
the variable name. For example, VAR1(YYYYDDD). See below for a list of formats. An
error occurs if you attempt to perform a CDATE operation on two variables with different
year formats (such as one with YY format and one with YYYY format).
The special name DATE can be used as a source variable and does not need any format
specification. The value is the current system date. If you have a source variable $DATE,
use the word VAR in front of it to distinguish it from the special name DATE.
If a proper format is not specified, or if a date cannot be determined, a syntax error results
and the action taken depends on the ON ERROR setting. See "ON ERRORSyntax
Errors" on page 95 for more information. Also refer to "ON EOMEnd-of-Month
Rounding" on page 95 for tips on avoiding syntax errors due to invalid end-of-month date
calculations.
If the source variable and target variable have the same name and format, omit the target
variable and the equal sign. The result is stored into the source variable.
All CDATE input must be valid and non-conflicting.
90
2 ZEKESET
Use the following character strings in any combination to specify the format of a target or
source variable.
YYYY
Four-digit year.
YY
Two-digit year. If the YY value is greater than or equal to 50, it is considered

a 20th century date (19xx); if it is less than 50, it is considered a 21st century
date (20xx).
MM
Two-digit month (01 to 12).
MONA
Three-letter month abbreviation (JAN, FEB, MAR, etc.).
MON
Month name (JANUARY, FEBRUARY, etc.).
DAYN
One-digit day number (1 = Monday, 7 = Sunday).
DAYA
Three-letter day abbreviation (MON, TUE, WED, etc.).
DAY
Day name (MONDAY, TUESDAY, etc.).
DDD
Three-digit day of year (001 to 366 for Julian dates).
DD
Two-digit day of month (01 to 31).
The user-specified format is scanned from left to right. The format elements are matched
in the order in which they appear in the list above. That is, DDD is matched before DD.
For example, if a format contains the string DDDDD, this string is interpreted as the
three-digit day of the year followed by the two-digit day of the month.
The CDATE function always stores an alphanumeric value in the target variable so that
leading zeroes are preserved.
The size and value of a source variable are expected to be consistent with the source format
specified; otherwise, an error results.
If an incomplete date format is specified, only modifiers relevant to the format are valid.
For example, for VAR1(YYYYMM), the only valid modifiers are MONTHS and YEARS.
The DAYS modifier is invalid. But in the case of VAR2(YYYYDDD), the MONTHS
modifier is valid because even though it is not named in the format, it is relevant to the
format.
If the source variable is formatted for only a day (DAY, DAYA, or DAYN), only DAY
modifiers are allowed. For example, if VAR1 contains the word TUESDAY, CDATE
VAR1(DAY) + 8 DAYS stores WEDNESDAY into VAR1.
91
If a variable contains both a complete date and a day value (such as VAR1(DAY MM/DD/YYYY)), the complete date is used for all calculations and any DAY values
come from the result of the complete date calculation. For example, if VAR1 contains
MONDAY - 12/27/2002, then CDATE VAR2(DAY) = VAR1(DAY - MM/DD/YYYY)
+ 2 DAYS + 1 YEAR stores FRIDAY into VAR2, not WEDNESDAY.
If a string in the format does not match any of the elements listed above, it is considered a
literal. A literal in the format for a source variable is expected to have an exact match in
that position in the source variable value; otherwise, an error results. A literal in a target
variable format is simply copied to the target variable value at the position where it was
encountered. This allows you to use characters such as spaces, dashes, slashes, commas,
etc. to separate date elements in the source and target. You can also use numerical digits
and alpha characters to manipulate the date value of the target.
For example,
VAR1(MM DD YYYY)
Separated by spaces.
VAR2(YYYY/DDD)
Separated by a slash.
VAR3(MM-DD-YYYY)
Separated by dashes.
VAR4(MON DD,YYYY)
Combination of spaces and commas.
VAR5(MM/01/YYYY)
Numerical manipulation of date.
VAR6(DDD20YYYY)
Numerical manipulation of date.
Tips On Using CDATE
92
CDATE statements can have conditional IF clauses similar to the IF clause of the
SET statement. When the IF clause is true, Zeke processes the CDATE statement.
When the IF clause is false, the CDATE statement is bypassed.
All date operations are performed from left to right within the CDATE statement.
Treat all CDATE operations output as alphanumeric data for comparison purposes.
2 ZEKESET
Valid CDATE Examples

The following are valid examples of the CDATE statement:
CDATE VAR1 = DATE + 1 DAY
One day is added to the current system date and the result is stored into the variable
VAR1 in default format.
CDATE VAR2(YYYYDDD) = DATE + 3 WEEKS
No format specification is needed for the special name DATE.
CD VAR3(MM-YYYY) = VAR2(YYYYDDD) - 5 DAYS
Format specification is needed for VAR2 and VAR3 because the format is not the
default format.
CD VAR1 EQ VAR1 + 1
Day is assumed for the numeral 1. No format specification is needed for VAR1
because it is in the default format. Since the source and target variable names and
formats are the same, the statement could be simplified to CD VAR1 + 1.
CDATE VAR DATE = DATE + 3
VAR is needed because the source variable name is the same as the special name
DATE.
CD VAR3(MON,DD,YYYY) EQ VAR2 + 3 DAYS + 2 MONTHS
More than one set of operators and modifiers can be used.
CD VAR1 = DATE + 1 DAY - 1 MONTH - 1 DAY
On the last day of the month, this calculates the date of the last day of the previous
month.
CD VAR2 = DATE + 1 DAY + 1 MONTH - 1 DAY
On the last day of the month, this calculates the date of the last day of the following
month.
CDATE VAR4 = DATE + 1 DAY - 1 MONTH
On the last day of the month, this calculates the date of the first day of the current
month.
CDATE VAR5 = DATE + 1 DAY - 2 MONTH
On the last day of the month, this calculates the date of the first day of the previous
month.
93
Sample JCL
//STEP1
EXEC PGM=ZEKESET,PARM=SUBSYS=SSSI
//SYSPRINT DD
SYSOUT=*
//SYSIN
DD
*
CDATE
CURRMNTH(MM) EQ DATE
SET VAR $FISCALMTH EQ '12/04/2001' IF $CURRMNTH EQ '12'
/*
Invalid CDATE Examples

The following are invalid examples of the CDATE statement:
CDATE VAR1 = 3 DAYS + VAR2
This is invalid because the source variable must be the first word following the
equals.
CDATE VAR1 = VAR2 + VAR3
This is invalid because Zeke cannot add two variables.
CDATE DATE + 3
This is invalid because the result cannot be stored into the special name DATE. If
DATE is a variable name, code the statement:
CDATE VAR DATE + 3
CDATE VAR1(YYYYMM) + 3 DAYS

This is invalid because VAR1 does not contain a DAY value.
CDATE VAR1(MMDD) + 20 DAYS
This is invalid because there is no way to determine whether it is a leap year.
CDATE VAR1(DD) + 10 DAYS
This is invalid because there is no way to determine when the next month is
reached.
CDATE OUTDATE EQ INDATE(DAYN DAY)
This is invalid due to conflicting input values. If INDATE has a value of 4
FRIDAY, an error results because day 4 of the week is Thursday, not Friday.
CDATE OUTDATE EQ INDATE(YYYYDDD - MMDDYYYY)
This is invalid due to conflicting input values. If INDATE has a value of 2002001
- 01022002, an error results because day 001 of the year is 01012002, not
01022002.
94
2 ZEKESET
ON EOMEnd-of-Month Rounding
The ON EOM command is used to specify how you want ZEKESET to deal with date
calculations in which the input or output date occurs at the end of a month. It establishes
the rounding settings when it is invoked, and those settings are in effect until another ON
EOM statement is encountered.
ON ERRORSyntax Errors
The ON ERROR ZEKESET statement specifies the action to take when syntax errors are
found in the input control statements supplied to ZEKESET.
The default is to immediately exit the ZEKESET program with a condition code of 4, 8,
or 12 depending on the type of error. The other options are to ignore the error or to set a
specified condition code.
The ON ERROR statement can be used more than once. The last encountered ON ERROR
statement is the one used if a syntax error is found.
Syntax
ON ERROR
IGNORE
RETCODE xxxx
CONCODE xxxx
ABEND
Parameters
Parameter
Description
IGNORE
Ignores the syntax errors and continues with the next ZEKESET
input statement.
RETCODE xxx
Exits the ZEKESET program immediately with the specified return

code. Up to 3 digits.
CONDCODE xxx Exits the ZEKESET program immediately with the specified
condition code. Up to 3 digits.
ABEND
Exits the ZEKESET program immediately with user abend code

U0001.
95
Sample JCL
The ON ERROR IGNORE statement in the following example ignores the syntax errors
and continues with the next ZEKESET input statement.
//TLAZSETI
//
//STEP01
//STEPLIB
//
//SYSPRINT
//SYSIN
ON ERROR
SET ZCOM
SET ZCOM
/*
JOB (10039),'NAME',NOTIFY=TSTLAA,
MSGCLASS=X,MSGLEVEL=(1,1),CLASS=A
EXEC PGM=ZEKESET,PARM='SUBSYS=SSSI'
DD
DSN=ZEKE.R520A.SUP.LINKLIB,DISP=SHR
DD
DSN=OASIS.R240A.SUP.LINKLIB,DISP=SHR
DD
SYSOUT=*
DD
*
IGNORE
'XXX'
'ZD'
The ON ERROR statement in following example exits the ZEKESET program

immediately with the return code 020.
//TLAZSETR
//
//STEP01
//STEPLIB
//
//SYSPRINT
//SYSIN
ON ERROR
SET ZCOM
SET ZCOM
/*
DD
DD
DD
SYSOUT=*
DD
*
RETCODE 020
'XXX'
'ZD'

immediately with the return code U0001.
//TLAZSETA
//
//STEP01
//STEPLIB
//
//SYSPRINT
//SYSIN
ON ERROR
SET ZCOM
SET ZCOM
/*
96
DD
DD
DD
SYSOUT=*
DD
*
ABEND
'XXX'
'ZD'
2 ZEKESET

immediately with the condition code of 018.
//TLAZSETC
//
//STEP01
//STEPLIB
//
//SYSPRINT
//SYSIN
ON ERROR
SET ZCOM
SET ZCOM
/*
DD
DD
DD
SYSOUT=*
DD
*
CONDCODE 018
'XXX'
'ZD'
97
98
3Report Writer
The Report Writer facility is a function of the batch utility program. This chapter describes
the types of reports, the parameters for record selection, how to format the reports and how
to execute the facility.
Generating Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Output Reports to File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Report Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Report SequenceEvent and Plan Listings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Page BreaksEvent and Plan Listings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Line SpacingEvent and Plan Listings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selecting FieldsEvent and Plan Listings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
104
104
106
107
107
LIST EVENT/PLANEvent Master and Schedule Listings . . . . . . . . . . . . . . . . . 110

LIST CALIDZeke Calendar Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Sample Report - LIST CALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
LIST VARIABLEZeke Variable Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
LIST OPERRECSZeke Operator ID Information . . . . . . . . . . . . . . . . . . . . . . . 135
Sample Report - LIST OPERRECS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
LIST OPERCLASOperator ID Security Classes. . . . . . . . . . . . . . . . . . . . . . . . . 137
Sample Report - LIST OPERCLAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
LIST RESOURCESystem Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Sample Report - LIST RESOURCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
99
Generating Reports
The LIST command generates Zeke reports. Many parameters can be used with the LIST
command to generate each report type. Only a few samples are shown in this procedure.
Note:
Security authorization is performed to ensure the user requesting the report has at least
READ access to the requested records. In order to generate a LIST PLAN report, the user
must be authorized for at least READ access to both the EMR and the SQR.
To generate a report
1
Create a jobstream that executes the ZEKEUTL procedure and include the desired
LIST commands. The ZEKEUTL procedure executes the Zeke program. The
following is a sample jobstream using the ZEKEUTL procedure.
//ZUTIL JOB , MSGLEVEL=(1,1),CLASS=A

//Z1
//SYSIN DD *
LIST EVENT . . . .
LIST PLAN . . . .
LIST VAR . . . .
LIST CALID . . . .
LIST RESOURCE . . . .
/*
Use the following LIST commands, depending upon the desired result:
Command
Description
Produce Event
Listing
LIST EVENT [selection-parameters]

LIST EVENTS [selection-parameters]
For valid selection parameters, see "LIST EVENT/PLAN

Event Master and Schedule Listings" on page 110
Produce
Scheduled
Event Listing
LIST PLAN [selection-parameters]
For valid selection parameters, see "LIST EVENT/PLAN

Event Master and Schedule Listings" on page 110
LIST VAR [selection-parameters]

Produce
Variable Listing For valid selection parameters, see "LIST VARIABLEZeke
Variable Information" on page 131
100
3 Report Writer
Command
Description
LIST CALID [selection-parameters]

Produce
Calendar Listing For valid selection parameters, see "LIST CALIDZeke
Calendar Information" on page 129.
Produce
Security Class
Listing
LIST OPERCLAS
Produce
Operator ID
Listing
LIST OPERRECS
Produce
Resource
Listing
LIST RESOURCE
(no selection parameters for this command)
To add a report title to the top of the report, use the TITLE parameter followed by
name of the report. If the title contains more than one word, the title must be
surrounded by quotation marks or parentheses. The title can be up to 60 characters,
and the keyword TITLE can be abbreviated TITL.
For example, to produce a report with the title SCHEDULE LISTING FOR
SYSTEM X BY USERID, use the following:
LIST PLAN TITLE SCHEDULE LISTING FOR SYSTEM X BY USERID
To change the line spacing from the default of single-spacing to alternative line
spacing, use one of the following parameters.
To double-space between entries, use SPACE2.
To triple-space between entries, use SPACE3.
For example, to produce a double-spaced report for all events, use the following:
LIST EVENT SPACE2
To specify the sort sequence for the report, use the SEQUENCE parameter followed
by the desired keywords contained in a single set of parentheses. Valid keywords are
listed in "Report SequenceEvent and Plan Listings" on page 104
For example, to select SYSTEM A events and sequence by event number within
event type, use the following:
LIST EVENT SYS A SEQUENCE (TYPE)
101
To add page breaks that sort by sequence, specify PAGEBREAK with the same
SEQUENCE parameter followed by the desired keywords contained in a single set
of parentheses. Valid page break keywords are listed in "Page BreaksEvent and
Plan Listings" on page 106
For example, to produce an Event Listing of all events, sorted by event type within
the same system ID, and display every new event type on a new page, use the
following:
LIST EVENT SEQUENCE (SYSTEM TYPE) PAGE (TYPE)
To specify fields to be printed on the report, use the FIELDS parameter followed by
the desired keywords contained in a single set of parentheses. Valid FIELDS
keywords are listed in "Selecting FieldsEvent and Plan Listings" on page 107
For example, to an Event Listing of all events containing the event description field
and last date of last dispatch field, use the following:
LIST EVENT FIELDS (DESC DISPDATE)
The default sort order is by event number.

8
102
Once you have completed your jobstream, execute the ZEKEUTL program to
generate the report.
3 Report Writer
Output Reports to File

Use the OUTFILE parameter to write selected records to a work file for user processing.
The output file can be written to DASD or tape. The OUTFILE keyword can be followed
by an operand naming the DD name for the output file. The default DD name is
ZEKEWK.
When the OUTFILE parameter is used, a DD statement for the output dataset (ZEKEWK,
or the user-specified name) must be available in the jobstream. Each LIST command opens
the dataset, writes selected records, and then closes the dataset. If multiple LIST
commands refer to the same DD, only the first dataset is processed.
The record layout of the output record is in Zeke install library member ZEKERCD. The
record consists of three parts:
The schedule queue record extractnot used for an Event Master Listing
The WHEN condition for the schedule queue record (LIST PLAN) or the lowest
version WHEN condition (LIST EVENT)
The EMR extract
The output dataset DCB information is as follows:

RECFM = VB
LRECL = 4000
BLKSIZE = 4008
To create a sequential disk file

1
Create a jobstream using the LIST command with the OUTFILE parameter to write
selected records to a file. For example, to write a scheduled event named JOB200 to
a file, use the following:
LIST PLAN JOB JOB200 OUTFILE
To name the output file, specify the DD name in a single set of parentheses after the
OUTFILE parameter. For example, to write scheduled event JOB200 to an output
file called USRNAME, use the following:
LIST PLAN JOB JOB200 OUTFILE (USRNAME)
103
To override the DFSORT message from appearing in Zeke report output, use the
following DD card and SYSIN parameters:
//DFSPARM DD *
OPTION MSGDDN=SYSOUT
After you complete your jobstream, execute the ZEKEUTL procedure to generate
the file.
Report Formatting
A number of parameters are available to format your reports. You can select the sequence
of the information, control the page breaks and spacing, select additional information and
the fields to be printed.
Report SequenceEvent and Plan Listings

The SEQUENCE parameter specifies the sort sequence for the Event and Plan Listings.
Default sequence is event number for LIST EVENT(S) and schedule time for LIST
PLAN.
Note:
The command used for events is entered either as EVENT or EVENTS.
Parameters
The SEQUENCE parameter is followed by the keywords, all contained within a single set
of parentheses. Up to five keywords can be specified. Specify major sort fields first.
104
Parameter
Description
SEQuence
Specifies the sort sequence for the report.

Keyword
Description
APPLICAT
By application ID
CALID
By calendar ID
DISPDATE
By last dispatch date
DISPPRI
By dispatching priority
3 Report Writer
Parameter
Description
DISPTIME
By last dispatch time
EARLY
By early time
ENAME
By event name
EVENT
By event number
GROupid
By group ID
HITDATE
By date the event was selected
JOBNAME
By jobname
LATE
By late time
SCHED
By schedule time
SELDATE
By date schedule record was built
STATtime
By time of last event status change (dispatch, BOJ, EOJ,

etc.)
SYSTEM
By owning system ID
TYPE
By event type
USERid
By user ID
VARiable
By variable name
VERsion
By version number
105
Page BreaksEvent and Plan Listings

The PAGEBREAK parameter specifies the field that controls page breaks on the report.
Every time the value of this field changes, a new page is created. In order to avoid an
abundance of page breaks, specify a PAGEBREAK field that is also a field specified as a
SEQUENCE parameter.
Parameters
The PAGEBREAK parameter is followed by the keywords, all contained within a single
set of parentheses.
Parameter
Description
PAGEbreak
Specifies the field that controls page breaks on the report.

Keyword
Description
APPLICAT
Application ID
CALID
Calendar ID
DISPPR
Dispatching priority
EVENT
Event number
GROUPID
Group ID
HITDATE
Due date
SELDATE
Select date
SYSTEM
System ID
TYPE
Event type
USERID
User ID
Example:
LIST EVENTS SEQUENCE (SYSTEM TYPE) PAGE (TYPE)
Produces an event master listing of all events, sorted by event

type within system ID. Every new event type is printed on a new
page.
106
3 Report Writer
Line SpacingEvent and Plan Listings

The reports are single-spaced. Use the following parameters if alternate spacing is
desired.
SPACE2
Print the report double-spaced.
SPACE3
Print the report triple-spaced.
Selecting FieldsEvent and Plan Listings

The FIELDS parameter specifies the fields to be printed on the report.
Parameters
The FIELDS parameter is followed by the keywords, all contained within a single set of
parentheses. Each keyword represents a field on the event master or event schedule
records, or both. The record used depends on the LIST command (PLAN=SQRs;
EVENTS=EMRs).
Up to 132 characters can be printed on a line. When calculating line length, add two spaces
between fields. A single asterisk (*) indicates that this is information from the EMR. Two
asterisks (**) indicate that this is information from the Schedule Recordvalid only for
PLAN listing.
Parameter Description
FIELDs
Specifies the fields to be printed on the report. Use the following keywords
to specify the fields. Separate the keywords with a comma, and enclose all
the keywords in a set of parentheses.
LIST EVENTS FIELD=(APP,ENAME,PLAT,SYS,SCHED)
The Length field below indicates the maximum length of the output for each
keyword. For example, if you choose to print the event description
(DESCRIPT keyword) on the report, the output for that field will be 60 bytes
or less.
Keyword
Length
Description
APPlicat
Application ID
CALid
Event calendar ID*
CONTrol
Tracking indicator for Zeke-controlled jobs
DESCript
60
Event description*
107
108
DISPCount
Number of dispatch times*
DISPDate
Last dispatch date
DISPPrio
Dispatching priority
DISPTime
Time of last dispatch
DRL
Disaster recovery level
EARLytim
Early time
ENAme
12
Event name
EVent
Event number
EXCeptio
20
Exception processing reasons**
EXPire
Event expiration date
FREQCalc
Frequency calculation for recurring events based

on schedule time or clock time
FREQUenc
Dispatch frequency for recurring events
GROupid
Group ID
HITdate
Schedule date**
JOBname
Jobname
LATEtime
Late time
LJOBname
30
Long jobname (jobname longer than 8 characters

or mixed-case jobname of any length)
MULTihit
Allow multiple schedule records due to a

non-workday
MUSTend
Time by which event should end
NOTAfter
Time after which event is not to be dispatched
NWDAY
How to schedule on non-workdays
OPErok
YES/NO for OPEROK parameter
3 Report Writer
PLATform
Operating system event will execute on
RETain
YES/NO for RETAIN parameter
SCHEdtim
Schedule time
SELdate
Date schedule record created**
STATTime
Time of last event status change (dispatch, BOJ,

EOJ, etc.)**
STATUS
Schedule record status (SUCC, HOLD, PEND

etc.)**
SYStem
System ID that owns event
TEXt
62
Lists command text for xCOM events; lists DOC

text for job events
TEXT1
62
First line of event description
TIMes
Number of dispatch times
TYPE
Event type
USErid
Event user ID
VERsion
Event version number
The following keywords are for job events only.

AUTOReply
YES/NO for AUTO REPLIES parameter
AVGDur
Average duration*
CLAss
Class list
JCLsourc
17
JCL source*
Jobname
Jobname
PRIority
Job priority
TAPes
Number of required tapes
TARGet
Execution system NETREGID

109
LIST EVENT/PLANEvent Master and Schedule Listings

This command lists EMR or SQR information from the Zeke database. The Event Master
Record Listings (EVENT) and schedule queue record Listings use the same reporting
parameters. The Schedule Listing (PLAN) has additional parameters that are also
described in this section.
Note:
In order to generate a LIST PLAN report, the user must be authorized for at least READ
access to both the EMR and SQR.
Parameters
All parameters have an AND relationship except for the Event Type parameters, which
have an OR relationship. If you use the Event Type parameter, the event must match all
criteria to be selected.
Parameter
Description
ABEnd
Valid with Schedule Listing (PLAN) only. Selects events that

completed abnormally.
ACTive
Valid with Event Listing (EVENT) only, because all schedule

records are active. Selects only active records. If not specified for
an EVENTS Listing, selects both active and deactivated events.
LIST EVENTS ACTIVE JOB
Select active job events.
110
ADDed

were added to the schedule with the ZADD command.
ALTEred

were altered by a Zeke command, such as ZALTER or
ZENABLE.
ALTNOTDur
Valid with Schedule Listing (PLAN) only. Selects events for

which the ZALTER command was used with the NOTDUROK
parameter.
ALTTimeok

which the ZALTER command was used with the TIMEOK
parameter.
ALTWhenok

which the ZALTER command was used with the WHENOK
parameter.
3 Report Writer
Parameter
Description
APPL
Specifies the application ID to match. Up to 8 characters. If you do

not know the full application ID, enter the beginning characters of
the application ID or the letters you know with wildcard characters
in the place of the unknown characters. You can enter a ? (question
mark) to search for any single character or an * (asterisk) in any
position to search for all positions following it. If the operand is
fewer than 8 characters, the comparison is made only for the
number of characters entered, including wildcards.
LIST PLAN APPL ABC
Select scheduled events with an application ID of ABC.

LIST PLAN APPL T*
Select scheduled events with an application ID beginning with

T.
LIST EVENT APPL A?C
Select events with an application ID beginning with A, ending

with C, and with any character in the 2nd position.
LIST EVENT APPL ABC*
Select events with an application ID beginning with ABC.

Note:
Use delimiters when values might be confused with other Zeke

parameter names.
BACklog
Valid with Schedule Listing (PLAN) only. Selects the schedule

records for the prior working day.
CLass
Specifies the class that an event must have in its class list to be
selected. The class can be up to 2 characters. Assumes the JOB
parameter. If no value is entered, any job event with a class is
selected.
LIST EVENTS CLASS
Select job events that have at least one class specified.

LIST PLAN CLASS (A,X)
Select scheduled job events that have class A or class X in

their class list.
Note:
The class is the class of the event, not the JCL class.
111
Parameter
Description
COMMent
Selects all work center events. All event types are selected if no
event type is specified. More than one event type can be entered on
a command line.
LIST EVENTS COMMENT
Select work center events only.

COMpleted
Valid with Schedule Listing (PLAN) only. Selects events with a

normal completion status (not pending or abend status).
DATASPACE
Use a dataspace when generating the report. Allows the batch

program to execute much more quickly.
LIST EVENTS DATASPACE
LIST PLAN DATASPACE
DEACtivate
Valid with Event Listing (EVENT) only, because all schedule

records are active. Selects only deactivated events. If not specified
for an EVENTS listing, selects both active and deactivated events.
LIST EVENTS DEAC
List all deactivated events.

DISabled
Valid with Schedule Listing (PLAN) only. Selects disabled events.
DOne
Valid with Schedule Listing (PLAN) only. Selects completed

events, regardless of the status (normal, abnormal, or disabled).
EARlytime
Selects events with early dispatch times.

LIST EVENTS EARLY
List only events that have an early dispatch time.
112
3 Report Writer
Parameter
Description
ENAme
Specifies a name an event must match. Up to 12 characters. If you

do not know the event name, enter the beginning characters of the
event name or the letters you know with wildcard characters in the
place of the unknown characters. You can enter a ? (question
mark) to search for any single character or an * (asterisk) in any
position to search for all positions following it. If the operand is
less than 12 characters, the comparison is made for as many
characters as are entered.
LIST PLAN ENAME PAY?01?
List scheduled events with a name that has PAY in positions

one through three, and 01 in positions five and six.
LIST EVENT ENAME *PR
List events with a name that ends with PR.

EVENTS
If the PLAN parameter is omitted, produces an Event Listing using

the EMRs.
If PLAN is entered, produces a Schedule Listing with specified
events. You can enter one or more event numbers and use the
RANGE, EXCLUDE, and EXRANGE parameters to select
specific events.
LIST EVENTS
Produce standard event report.

LIST EVENTS (33,34,88,134,332)
Report on these events. A maximum of 31 event numbers can

be specified.
LIST PLAN EVENTS (1,2,3,4,5)
Plan report on only these scheduled events.
113
Parameter
Description
EVTCal
Specifies one or more calendar IDs. Events with one of the listed
calendar IDs are selected. Up to 8 characters. If you do not know
the full calendar ID, enter the beginning characters of the calendar
ID or the letters you know with wildcard characters in the place of
the unknown characters. You can enter a ? (question mark) to
search for any single character or an * (asterisk) in any position to
search for all positions following it. If the operand is fewer than 8
characters, the comparison is made only for the number of
characters entered, including wildcards.
LIST PLAN EVTCAL ACCTGQ11
List scheduled events with calendar ID ACCTGQ11.

LIST EVENT EVTCAL ACCTG*
Select events with a calendar ID beginning with ACCTG.

LIST EVENT EVTCAL A*2
Select events with a calendar ID beginning with A, ending

with 2, and with any character in positions 2 through 7.
EXCEptions
Valid with Schedule Listing (PLAN) only. Selects events with an

exception recorded. For example, ZALTER of the schedule time,
events run late, added, held, disabled, or refreshed.
EXCLude
Specifies the events to exclude from the report. Any event number
listed is excluded even if within a selected range or specified with
the EVENTS parameter.
LIST EVENTS RANGE (100,200) EXCLUDE (104, 107,
108)
Report on events 100 through 200 except for events 104, 107,
and 108.
EXRange
Specifies the range of events to exclude from the report. Enter the
starting and ending event number and enclose in parentheses.
More than one range can be entered. A starting number without an
ending is assumed to go to the end of the database.
LIST EVENTS EXRANGE (10,20)
Report on all events except events 10 through 20.

LIST EVENTS RANGE (100,200) EXRANGE
(130,150,180,185)
Report on events 100 through 200, except events 130 through

150 and 180 through 185.
114
3 Report Writer
Parameter
Description
GROupid
Specifies the group ID to match. If you do not know the full group
ID, enter the beginning characters of the group ID or the letters you
know with wildcard characters in the place of the unknown
characters. You can enter a ? (question mark) to search for any
single character or an * (asterisk) in any position to search for all
positions following it. If the operand is fewer than 3 characters, the
comparison is made for as many characters as are entered.
LIST PLAN GROUP 001
List scheduled events with a group ID of 001.

LIST PLAN GROUP B*
List scheduled events with a group ID that begins with a B.

LIST EVENTS GROUP Q?2
List events with a group ID beginning with Q, ending with 2,

and with any character in the 2nd position.
LIST EVENTS GROUP QP*
List events with an group ID beginning with QP.

Note:
Use delimiters when values might be confused with other Zeke

parameters.
HOld
Valid with Schedule Listing (PLAN) only. Selects events that are
currently on hold.
115
Parameter
Description
JOB
Specifies the jobs to match. If entered alone, selects all job events.
All event types are selected if no event type is specified. If you do
not know the jobname, enter the beginning characters of the
jobname or the letters you know with wildcard characters in the
place of unknown characters. You can enter a ? (question mark) to
search for any single character or an * (asterisk) in any position to
search for all positions following it. If the operand is fewer than 8
characters, the comparison is made for as many characters as
entered. More than one event type can be entered on a command
line.
LIST EVENTS JOB
Select only job events.

LIST EVENTS JOB (PR*)
Select job events with jobnames beginning with PR.

LIST EVENTS JOB CL**P***
Select job events with jobnames beginning with CL and that

have a P in the fifth position of the jobname.
LAte
Valid with Schedule Listing (PLAN) only. Selects scheduled

events that are flagged as late.
LATETime
Selects events that have a LATE time specified, regardless of their

LATE status.
LIST EVENTS LATET SYS C
Select all events on system C that have a LATE time.

LISTAcctg
Prints the accounting information for each event. This information

includes the number of dispatches and date and time of the last
dispatch.
LIST EVENTS LISTACCTG
Produce an EVENT report with dispatch information.

LISTCond
Prints the defined condition codes for each event.

LIST EVENTS LISTCOND
Produce an EVENT report with condition code information.

LISTDESc
Prints the event description on the first line for each event. The
detailed event information is printed below the description.
LIST EVENTS LISTDESC
Produce EVENT report with event descriptions.

116
3 Report Writer
Parameter
Description
LISTDOc
Prints all event documentation. This is the same as specifying

LISTNOTE, LISTDSN, LISTTEXT, and LISTPAD.
LISTDSn
Prints the defined tape datasets and current volume serial numbers
for each event.
LISTEXit
Invokes user exit ZEKE02MX once for each event after all other
reporting for the event is done. Refer to your ASG-Zeke OS/390
Installation Guide for more information on the ZEKE02MX exit.
LISTJcl
Prints the JCL defined in the database. The JCL follows the
detailed event information.
LISTNotes
Prints the note information for each event.

LIST EVENTS LISTNOTES
Produce EVENT report with note information.

LISTOccurs
Prints the OCCURS clause for each event.

LIST EVENTS LISTOCCURS
Produce EVENT report with OCCURS clause information.

LISTPad
Prints the scratch pad information for each event and comment
lines for work centers.
LISTReply
Prints the automatic replies and messages for each event.
LISTRESO
Prints the resource information for each event.
LISTText
Prints the text information for each event.
LISTVols
Prints the required disk volumes following the detailed event

information.
117
Parameter
Description
LISTWhen
Prints WHEN conditions for each selected event. For work

centers, prints SET conditions.
LIST EVENTS LISTWHEN
Produce EVENT report WHEN information.

For events with multiple SQRs (versions) with the same schedule
date, the WHEN conditions for ALL versions are printed on the
report.
Multiple keywords can be used, separated by spaces or commas.
LIST EVENTS LISTW WH (EOJ,VAR,EOE)
Select all events with an EOJ, EOE, or a variable in the

WHEN condition.
MSG
Selects all message events. All event types are selected if no event
type is specified. More than one event type can be entered on a
command line.
LIST EVENTS MSG
Select message events.

LIST EVENTS MSG ZCOM
Select message events and Zeke command events.

NOEARly
Selects events that do not have an EARLY dispatch time.

LIST EVENTS NOEARLY
Select only events with no EARLY dispatch time.

NOLate
Select events that do not have LATE time.

LIST EVENTS NOLATE
Select only events with no LATE time.

NOOperok
Selects events that do not require an operator OK prior to event

dispatch.
LIST EVENTS JOB NOOPEROK
Select job events that do not require an OPEROK.

NOTDone
118
Valid with Schedule Listing (PLAN) only. Selects schedule

records that are not complete (not DONE or disabled).
3 Report Writer
Parameter
Description
OCCURSDETAIL
Valid with Event Listing (EVENT) only. Selects events with

OCCURS clauses that contain the specified keywords.
LIST EVENTS OCCURSDETAIL (MONDAY)
Lists events that have an OCCURS clause that contains the

keyword MONDAY.
OPErok
Selects events that require an operator OK prior to dispatch

(OPEROK=YES).
LIST EVENTS JOB OPEROK
List job events that require OPEROK.

OUTFILE
Writes the selected records to a file for user processing. "Output

Reports to File" on page 103 for more information.
PENDing
Valid with Schedule Listing (PLAN) only. Selects PENDING

scheduled events.
PLan
Produces reports using the schedule queue records. You can enter
one or more event numbers and use the RANGE, EXCLUDE, and
EXRANGE parameters to select specific jobs. For current day
schedule reports, schedule a LIST PLAN at the end of the day,
immediately before the schedule load (make the schedule load a
successor to the LIST PLAN job).
LIST PLAN
Produce schedule listing.

PRIority
Specifies events based on priority code (1-15). Events with a

matching priority are selected.
LIST EVENTS PRIORITY 5
List events with a priority of 5.

LIST EVENTS PRI (7,8,9)
List events with a priority of 7, 8, or 9.

RAnge
Specifies a range of event to select for reporting. Specify, within

parentheses, a starting and ending event number. More than one
range can be entered. A starting number without an ending is
assumed to go to the end of the database.
LIST EVENTS RANGE (40,60,100,117,300)
Select events from event number 40 through event 60, from

event 100 through event 117, and from event 300 to the end.
119
Parameter
Description
REAdy
Valid with Schedule Listing (PLAN) only. Selects events that are
ready to run (time and WHEN conditions are satisfied), but have
not been dispatched yet.
RECURring
Selects events that occur more than once daily (recurring events).
LIST EVENTS RECUR MSG
List all recurring message events.

REFreshed

were refreshed by the ZREFRESH command.
RESDETAIL
Selects all events in the database with logical resources defined.

LIST EVENTS RESDETAIL
Lists events with logical resources.

LIST EVENT RESDETAIL RESOURCE1
List events with RESOURCE1 as a logical resource.

REXX
Selects all REXX events. All event types are selected if no event
type is specified. More than one event type can be entered on a
command line.
LIST EVENTS REXX
Select REXX events.

LIST EVENTS REXX ZCOM
Select REXX and Zeke command events.

SCOm
Selects all System command events. All event types are selected if
no event type is specified. More than one event type can be entered
on a command line.
LIST EVENTS SCOM
Select only System command events.

STArt
Specifies a time (HH:MM). Events scheduled after this time are

selected. The valid range is from 00:00 (default) to 47:59.
LIST EVENTS START 04:00
Select events with scheduled time later than 04:00.
120
3 Report Writer
Parameter
Description
STOp
Specifies a time (HH:MM). Events scheduled before this time are

selected. The valid range is 00:01 to 47:59 (default).
LIST EVENTS STOP 16:00
Select events that have a scheduled time earlier than 16:00.

LIST EVENTS START 08:01 STOP 16:00
Select events with schedule times after 8:01 and before 16:00.
SYStems
Events owned by one of the specified systems or work centers are

selected. The system name can be up to 8 characters. If this
parameter is omitted, all systems and work centers are selected.
LIST EVENTS SYS A
Select system A events.

LIST PLAN SYS (A, MVSA, MVSB) JOB
Select scheduled job events for systems A, MVSA, and MVSB.

TAPes
Selects job events that require at least one tape drive prior to job
dispatch.
LIST EVENTS TAPE
List job events that require at least one tape drive.

LIST EVENTS TAPE SYS B
List job events for system B that require at least one tape
drive.
TARGet
Selects events that execute on the specified remote system. Up to

8 characters.
LIST PLAN TARGET REG4
List scheduled events that execute on the remote system with a

netregid of REG4.
LIST EVENT TARG DALLAS45
List events that execute on the remote system with a netregid

of Dallas45.
TIMEOk

events that are time satisfied.
121
Parameter
Description
TITLe
Specifies the report title to be printed on the report heading. The

title can be up to 50 characters. Enclose the title within delimiters.
LIST PLAN TITLE 'SCHEDULE LISTING FOR SYSTEM X BY USERID'
LIST EVENTS TITLE (EVENT MASTER LISTING BY SYSTEMID)
TODay
Valid with Schedule Listing (PLAN) only. Selects todays

schedule records.
USERid
Specifies the user ID to match. Up to 8 characters. If you do not

know the full user ID, enter the beginning characters of the user ID
or the letters you know with wildcard characters in the place of the
unknown characters. You can enter a ? (question mark) to search
for any single character or an * (asterisk) in any position to search
for all positions following it. If the operand is fewer than 8
characters, the comparison is made for as many characters as are
entered.
LIST PLAN USER DATACTL1
Select from the scheduled queue records (PLAN) all the jobs
with user ID DATACTL1.
LIST EVENTS USER DATA*
Select all events with a user ID beginning with DATA.

LIST EVENTS USERID D?1
Select events with a user ID beginning with D, ending with 1,

and with any character in position 2.
LIST EVENTS USER DA*
Select events with a user ID beginning with DA.

VCOm
Selects all VM command events. All event types are selected if no

event type is specified. More than one event type can be entered on
a command line.
LIST EVENTS VCOM
Select only CP command events.

WHendetail
Selects events with WHEN/SET conditions that contain the

specified jobname, program name, or variable. Up to 30 operands
can be entered. Only as many characters entered are compared. An
asterisk (*) is not a wildcard character.
LIST EVENTS WHENDETAIL $ABC
Select events that have a WHEN condition with a variable

beginning with $ABC.
122
3 Report Writer
Parameter
Description
LIST EVENTS JOB
WHENDETAIL (PAY01P18,PAY01P19,$VARXX)
Select job events that have WHEN conditions with the

jobnames PAY01P18 or PAY01P19, or a variable beginning
with $VARXX.
The following keywords can also be used with the
WHENDETAIL parameter. They must be enclosed in
parentheses.
Keyword
Description
AEOE
Abnormal end of event
AEOJ
Abnormal end of job
AEOP
Abnormal end of program
AEOS
Abnormal end of step
AT
Remote prerequisites.
BOJ
Beginning of job
BOP
Beginning of program
DSN
Dataset name
EOE
End of event (includes weak and extended EOEs)
EOG
End of group (includes weak EOGs)
EOJ
End of job (includes weak and extended EOJs)
EOP
End of program
EOS
End of step
NOTJ
Not during job
NOTP
Not during program
VAR
Variable
WEOE
Weak end of event
123
Parameter
Description
WEOG
Weak end of group
WEOJ
Weak end of job
XEOE
Extended end of event
XEOJ
Extended end of job
Example:
LIST EVENTS WHEN (VAR)
Select all events with a variable in the WHEN condition.

(Multiple keywords must be separated by spaces or commas. )
LIST EVENTS WHEN (EOJ,VAR,EOE)
Select all events with an EOJ, EOE, or variable in the WHEN

condition.
WHENOk

events that are WHEN satisfied.
ZCOm
Selects all Zeke command events. All event types are selected if
no event type is specified. More than one event type can be entered
on a command line.
LIST EVENTS ZCOM
Select only Zeke command events.

LIST EVENTS ZCOM JOB
Select job events and Zeke command events.

Sample Report - LIST EVENTS
Sample JCL
The following JCL produces a sample LIST EVENTS report using the JOB,
LISTOCCURS and LISTWHEN parameters.
//REPORT1 JOB
//STEP1 EXEC ZEKEUTL,P=SUBSYS=SSSI
//SYSIN
DD *
LIST EVENTS JOB LISTOCCURS LISTWHEN
/*
//
124
3 Report Writer
Sample Report
LIST EVENTS report using the JOB, LISTOCCURS, and LISTWHEN parameters.
ZEKE 5.20 Z5200A000 X240A000 - ZEKE UTILITY PROGRAM MAINTENANCE LISTING
SSSI RUN 0042
DATE 08/23/2001
LIST EVENTS JOB LISTOCCURS LISTWHEN

Z02C8I REPORT SEQUENCE NUMBER 001 - RECORDS SELECTED=0000010
Z0214I ENTERING SORT PHASE
Z0215I ENTERING PRINT PHASE
ZEKE 5.20 Z520A000 X240A000
REPORT ZEKE02M-01 RUN 0042
EVENT EVNT SCHED EARLY LATE
NUMBER TYPE TIME TIME TIME
101 JOB
102 JOB
104 JOB
106 JOB
110 JOB
112 JOB
113 JOB
114 JOB
115 JOB
116 JOB
00:00
0 OCCURS
00:00
0 OCCURS
00:00
0 OCCURS
00:00
0 OCCURS
0
WHEN
1
WHEN
00:00
0 OCCURS
00:00
0 OCCURS
00:00
0 OCCURS
00:00
0 OCCURS
00:00
0 OCCURS
00:00
0 OCCURS
THURSDAY
ZEKE EVENT MASTER RECORD LISTING
CALID
SYSTEM
A
PRD
(REQUEST)
A
PRD
(REQUEST)
A
PRD
(REQUEST)
A
PRD
(REQUEST)
(VAR $ABC EQ 10)
(VAR $AAA2 EQ 20)
A
PRD
(DAILY)
A
PRD
(DAILY)
A
PRD
(DAILY)
A
PRD
(DAILY)
A
PRD
(DAILY)
A
PRD
(REQUEST)
******* NUMBER OF EVENTS REPORTED -
APP
GRP USERID
ID
DATE 08/23/2001 TIME 15:30:38

SEQ # 001 PAGE 1
EVENT NAME
JOB NAME
XXXXJOC
PRD1
PRD1
VARIABLE
TVSET
PRDSUB
PRDJOBV
08/16/2001 18:31
PRDJOBV
TVSET
08/16/2001 18:31
PRDJOB1
PAY1
PRDJOB2
PRDJOB2
PAY1
PRDJOB3
PRDJOB3
PRDJOB4
LAST
TIME
08/16/2001 12:26
PRDJOB1
PAY1
LAST
DATE
PRDJOB4
08/16/2001 18:31
PRDDATEJ 08/16/2001 18:31
10
125
Sample Report - LIST PLAN - 1

Sample JCL
The following JCL produces a sample LIST PLAN report using the SYS, LISTNOTES,
LISTPAD, and LISTTEXT parameters.
//REPORT3 JOB
//SYSIN
DD *
LIST PLAN SYS PRD LISTNOTES LISTPAD LISTTEXT
/*
//
Sample Report
LIST PLAN report using the SYS, LISTNOTES, LISTPAD, and LISTTEXT parameters.
SSSI
RUN 0041
DATE
08/23/2001
LIST PLAN SYS PRD LISTNOTES LISTPAD LISTTEXT

Z
ZEKE 5.20 Z520A000 X240A000
THURSDAY
ZEKE SCHEDULE OF EVENTS
EVENT VERSN EVNT SCHED EARLY LATE

NUMBER
TYPE TIME TIME TIME
CALID
3
0 WORK 00:00
A
COMMENT LINES : THIS IS A WORK CENTER EVENT
10
12
13
14
15
16
16
16
7
0
0
0
0
0
0
0
0
0
JOB
JOB
JOB
JOB
JOB
JOB
JOB
JOB
WORK
00:00
00:00
00:00
00:00
00:00
00:00
00:00
00:00
00:00
A
A
A
A
A
A
A
A
A
SYSTEM
APP
GRP
ID
USERID
DATE 08/23/2001 TIME 15:29:26

SEQ # 001
PAGE
1
EVENT NAME
PRD
WORKCTR
PRD
PRD
PRD
PRD
PRD
PRD
PRD
PRD
PRD
TVSET
PRDJOB1
PRDJOB2
PRDJOB3
PRDJOB4
PAY1
JOB NAME
TVSET
PRDJOB1
PRDJOB2
PRDJOB3
PRDJOB4
PRDDATEJ
PRDDATEJ
PRDDATEJ
COMMENT LINES : THIS HAS MULTIPLE VARIABLES

SCRATCH PAD - THIS IS FOR QUICK NOTES.
IT MAY BE USED FOR LONG DESCRIPTIONS THAT COULD SPAN SEVERAL LINES.
NOTE DOC - THIS IS A NOTE
8
0 WORK 00:00
-
PRD
AP1
EVTAP1
COMMENT LINES : THIS EVENT IS FOR AP1

9
0 WORK 00:00
A
PRD
AP2
EVTAP2

11
0 WORK 00:00
A
PRD
COMMENT LINES : THIS WORK CENTER USES '>' AND '<'

126
14
LAST
TIME
08/19/2001 08:53
MULTIVAR
TEXT DOC - THIS IS THE TEXT INFORMATION.
LAST
DATE
00010000
00011000
00020000
08/09/2001 09:04
08/09/2001
08/28/2001
08/28/2001
08/28/2001
08/15/2001
09:04
18:18
18:18
18:18
07:48
3 Report Writer
Sample Report - LIST PLAN - 2

Sample JCL
The following JCL produces a LIST PLAN report using the NOTDONE, TITLE,
SPACE2, FIELDS, SEQUENCE, LISTW, and LISTDOC parameters.
//REPORT5 JOB
//SYSIN
DD *
LIST PLAN NOTDONE TITLE DAILY SCHEDULE OF EVENTS
SPACE2 FIELDS
(SCHED,EVENT,ENAME,JOBNAME,DESC,OPEROK,
AVGDUR) SEQUENCE (SCHED) LISTW LISTDOC
/*
//
127
Sample Report
LIST PLAN report sample using the NOTDONE, TITLE, SPACE2, FIELDS,
SEQUENCE, LISTW, and LISTDOC parameters.
SSSI
RUN 0040
DATE
08/23/2001
LIST PLAN NOTDONE TITLE 'DAILY SCHEDULE OF EVENTS'

SPACE2 FIELDS
(SCHED,EVENT,ENAME,JOBNAME,DESC,OPEROK,
AVGDUR) SEQUENCE (SCHED) LISTW LISTDOC
ZEKE 5.20 Z520A000 X240A000
SCHED EVENT EVENT NAME
TIME NUMBER
00:00
JOB NAME
THURSDAY
DAILY SCHEDULE OF EVENTS
DATE 08/23/2001 TIME 15:27:50

SEQ # 001
PAGE
1
DESCRIPTION OF EVENT
OPR AVGDUR
OK HH:MM:SS
7 MULTIVAR
MULTI VARIABLE WORK CENTER
NO
0
WHEN (?XVAR A1 EQ 10 AND ?XVAR A2 EQ 20 AND XVAR A3 EQ 30 AND XVAR A4 EQ 40)
COMMENT LINES : THIS HAS MULTIPLE VARIABLES

SCRATCH PAD - THIS IS FOR QUICK NOTES.
TEXT DOC - THIS IS THE TEXT INFORMATION.
IT MAY BE USED FOR LONG DESCRIPTIONS THAT COULD SPAN SEVERAL LINES.
00010000
00011000
00020000
NOTE DOC - THIS IS A NOTE

00:00
8 EVTAP1
THIS IS AP1 EVENT
0
WHEN (?XVAR APPL1 EQ EVT1)
NO

00:00
9 EVTAP2
THIS IS AP2 EVENT
0
WHEN (?XVAR APPL1 EQ EVT2)
NO

00:00
10 TVSET
00:00
11
0
TVSET
THIS JOB IS BASED ON A VARIABLE VALUE
WORK CENTER
WHEN (?XVAR A1 EQ 10)
NO
00:00:01
NO
COMMENT LINES : THIS WORK CENTER USES '>' AND '<'

00:00
17
MAAZJOB2 MATTS 2
NO
00:00:00
05:00
15 PRDJOB4
PRDJOB4
THIS JOB RETURNS RESULT 4
NO
00:00:00
06:00
14 PRDJOB3
PRDJOB3
NO
00:00:00
07:00
13 PRDJOB2
PRDJOB2
NO
00:00:00
08:00
12 PRDJOB1
PRDJOB1
NO
00:00:00
128
10
3 Report Writer
LIST CALIDZeke Calendar Information

List information about the system calendars. Select one or more calendars by specifying
the calendar IDs.
Syntax
LIST CALID
*
name
YEAR nnnn
CALSPEC
YEAR
CALUSER
CALSTD
Parameters
Use the following parameters to select the calendars:
Parameter
Description
Report on all existing calendars.
name
Report on a specific calendar for the current year.

LIST CALID Q1
Report on the Q1 calendar.

LIST CALID (ACCT1,ACCT2,ACCT3)
Report on ACCT1, ACCT2, and ACCT3 calendars for the current

year.
LIST CALID (A,NORMAL,F)
Report on calendars A, NORMAL, and F.

CALSPEC
Report on all special calendars.
CALUSER
Report on all user calendars.
CALSTD
Report on all standard calendars.
YEAR
Report on a specific calendar year. If omitted, the current year

calendar is selected.
LIST CALID ACCT2 YEAR 2002
Report on the calendar ACCT2 for 2002.
129
Sample Report - LIST CALID

Sample JCL
//REPORT4 JOB
//SYSIN
DD *
LIST CALID A
/*
//
Sample Report
LIST CALID A
ZEKE STANDARD CALENDAR ID: A
YEAR: ****
** WORK DAYS **
******************* HOLIDAYS *****************
MONDAY:
TUESDAY:
WEDNESDAY:
THURSDAY:
FRIDAY:
SATURDAY:
SUNDAY:
01/01/****
YES
YES
YES
YES
YES
NO
NO
FISCAL START MONTH: 01

CALENDAR START DATE:
CALENDAR EXPIRE DATE:
07/04/****
12/31/****
CALENDER END DATE:

DATE LAST ACCESSED: 08/09/2000
******* NUMBER OF CALENDARS REPORTED -
130
12/25/****
SSSI RUN 0039
DATE 08/23/2001
3 Report Writer
LIST VARIABLEZeke Variable Information

List Zeke variables. When system-dependent variables are specified in a selection list, the
names are resolved for the system in which the report is being produced.
Note:
The LIST VARIABLE report does not list OASIS variables.
Syntax
LIST VARIABLE
CHAracter
LISTOld
NUMeric
TITLe title
variable name
Parameters
Use the following parameters to select the variables.
Parameter
Description
CHAracter
Selects only variables with character formats.
LISTOLd
Lists the previous and current values of the selected variables.
NUMeric
Selects only variables with numeric formats.
131
Parameter
Description
TITLe
Specifies the report title, up to 60 characters.

LIST VARIABLE CHAR TITLE (CHARACTER FORMAT ZEKE
VARIABLES)
variable-name Selects the indicated variables. If no variables are listed, selects all
system variables defined in the catalog.
LIST VARIABLE
List all Zeke variables.

Up to 30 variables can be specified for each report. To perform
generic selection, precede the variable with an asterisk (*) and
enter only the characters to be compared. An asterisk in any other
position is considered to be a wildcard character.
LIST VAR $XYZ
List only variable $XYZ.

LIST VAR ($A,$B,$C,$D)
List these four variables.

LIST VAR (*$PAY)
List variables beginning with $PAY.

LIST VAR ($A***01)
List variables with $A in the first and second positions and 01

in the sixth and seventh.
132
3 Report Writer
Sample Report - LIST VARIABLE - 1

Sample JCL
The following JCL produces a sample LIST VARIABLES report using the TITLE
parameter.
//REPORT6 JOB
//SYSIN
DD *
LIST VARIABLES TITLE CURRENT VARIABLES
/*
//
Sample Report
LIST VARIABLES report sample using the TITLE parameter.
SSSI RUN 0038
DATE 08/23/2001
LIST VARIABLES TITLE 'CURRENT VARIABLES'

ZEKE 5.20 Z520A000 X240A000

THURSDAY
CURRENT VARIABLES
ZEKE DATA-NAME
DATE SET TIME SET
JOB/PGM NAME
$AAA1
$AAA2
$AAA3
$AAA4
$ABC
$DEF
08/25/01
08/25/01
08/25/01
08/25/01
08/23/01
07/16/01
OPERATOR
OPERATOR
OPERATOR
OPERATOR
PDOPER
PRD1
10:04:23
10:04:24
10:04:24
10:04:24
14:50:53
08:23:25
******* NUMBER OF DATA-NAMES REPORTED -
USR
USR
USR
USR
USR
USR
PR/SYSTEM
TSO-PRD
TSO-PRD
TSO-PRD
TSO-PRD
TSO-PRD
TSO-PRD
DATE 08/23/2001 TIME 15:19:23

SEQ # 001 PAGE 1
DATA-NAME VALUE
NUMERIC
NUMERIC
NUMERIC
NUMERIC
GHI
XYZ
VALUE
VALUE
VALUE
VALUE
=
=
=
=
10
20
30
40
133
Sample Report - LIST VARIABLE - 2

Sample JCL
The following JCL produces a LIST VARIABLES report using the LISTOLD parameter.
//REPORT6 JOB
//SYSIN
DD *
LIST VAR LISTOLD
/*
//
Sample Report
LIST VARIABLES report sample using the LISTOLD parameter.
SSSI RUN 0037
DATE 08/23/2001
LIST VAR LISTOLD

ZEKE 5.20 Z520A000 X240A000

THURSDAY
ZEKE DATA-NAME LISTING
ZEKE DATA-NAME
DATE SET
TIME SET
JOB/PGM NAME
$AAA1
PRIOR
$AAA2
PRIOR
$AAA3
PRIOR
$AAA4
PRIOR
$ABC
PRIOR
$DEF
PRIOR
07/25/2001 10:04:23
: :
08/25/2001 10:04:24
08/13/2001 09:12:10
08/25/2001 10:04:24
08/13/2001 09:12:11
08/25/2001 10:04:24
08/13/2001 09:12:12
08/23/2001 14:50:53
07/17/2001 10:23:28
07/16/2001 08:23:25
07/16/2001 08:23:20
OPERATOR USR
JOB
OPERATOR USR
OPERATOR USR
OPERATOR USR
OPERATOR USR
OPERATOR USR
OPERATOR USR
PDOPER
USR
PRD1
USR
PRD1
USR
PRD1
USR
VALUE
VALUE
VALUE
VALUE
VALUE
VALUE
******* NUMBER OF DATA-NAMES REPORTED -
134
PR/SYSTEM
TSO-PRD
TSO-PRD
TSO-PRD
TSO-PRD
TSO-PRD
TSO-PRD
TSO-PRD
TSO-PRD
TSO-PRD
TSO-PRD
TSO-PRD
DATE 08/23/2001 TIME 15:15:13

SEQ # 001 PAGE 1
DATA-NAME VALUE
NUMERIC
---- NO
NUMERIC
NUMERIC
NUMERIC
NUMERIC
NUMERIC
NUMERIC
GHI
DEF
XYZ
---- NO
VALUE = 10
PREVIOUS VALUE EXISTS ----VALUE = 20
VALUE = 20
VALUE = 30
VALUE = 30
VALUE = 40
VALUE = 40
PREVIOUS VALUE EXISTS -----
3 Report Writer
LIST OPERRECSZeke Operator ID Information

List information about all operator IDs defined in the database.
Syntax
LIST OPERRECS
Sample Report - LIST OPERRECS

Sample JCL
//REPORT8 JOB
//SYSIN
DD *
LIST OPERRECS
/*
//
135
Sample Report
ZEKE 5.20 Z520ADV6 X240A000 - ZEKE UTILITY PROGRAM MAINTENANCE LISTING
SSSI
RUN 0117
LIST OPERRECS
ZEKE 5.20 Z520ADV6 X240A000
ZEKE OPERATOR ID LISTING
Operator Id: CARLTST

Class Id: A
Userid:
Zcom
Event
********
W
W
CCCCCCC
W
W
ALLGOV
W
W
SEINI*
W
W
BARBARA
W
W
STEVEW*
W
W
RICHARDS
W
W
Date Added: 01/11/2001 Last Updte: 08/07/2001

Work
Documentation
Variable
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
Operator Id: OPERATOR

Class Id: A
Userid:
Zcom
Event
********
W
W
ALLPAY*
W
W
Date Added: 01/11/2001 Last Updte:

Work
Documentation
Variable
W
W
W
W
W
W
Operator Id: TEST1

Userid:
********
USER2
USER3
USER4
Date Added: 01/10/2001 Last Updte: 08/16/2001

Work
Documentation
Variable
W
W
W
N
W
W
W
N
N
W
N
N
Zcom
W
N
W
W
Class Id: A
Event
W
N
W
W
******* NUMBER OF OPERATOR IDS REPORTED -
136
3 Report Writer
LIST OPERCLASOperator ID Security Classes

List information about all operator ID security classes defined in the database.
Syntax
LIST OPERCLAS
Sample Report - LIST OPERCLAS

Sample JCL
//REPORT7 JOB
//SYSIN
DD *
LIST OPERCLAS
/*
//
Sample Report
ZEKE 5.20 Z520ADV6 X240A000 - ZEKE UTILITY PROGRAM MAINTENANCE LISTING
SSSI
RUN 0117
LIST OPERCLAS
ZEKE 5.20 Z520ADV6 X240A000
ZEKE SECURITY CLASS LISTING
CLASS: A Evt- W Zcm- W Cal- W Opt- W Wrk- W Sec- W Doc- W

Schedule Control (Operator) Commands Allowed (Y=yes, N=no)
Zadd
Zalter
Zdelete
Zdisable
Zdisplay
Y
Y
N
Y
Y
Zid
Zkill
Zmap
Zhold
Zok
Y
N
Y
Y
Y
Zreload
Zset
Zstatus
Zrelease
Zscan
Y
Y
Y
Y
Y
CLASS: B Evt- W Zcm- W Cal- W Opt- W Wrk- W Sec- W Doc- W

Schedule Control (Operator) Commands Allowed (Y=yes, N=no)
Zadd
Zalter
Zdelete
Zdisable
Zdisplay
N
Y
N
N
Y
Zid
Zkill
Zmap
Zhold
Zok
Y
N
Y
Y
Y
**** Number of Security classes reported -
Zreload
Zset
Zstatus
Zrelease
Zscan
Var- W
Y
Y
Y
N
Y
Rst- W
Zres Disp
Zres Alt
Zenable
Zrefresh
Zres Rel
Var- W
Y
Y
N
Y
Y
Y
Y
Y
Y
Y
Rst- W
Zres Disp
Zres Alt
Zenable
Zrefresh
Zres Rel
137
LIST RESOURCESystem Resources

List the resource name and description.
Syntax
LIST RESOURCE
Sample Report - LIST RESOURCE

Sample JCL
//REPORT7 JOB
//SYSIN
DD *
LIST RESOURCE
/*
//
Sample Report
ZEKE 5.20 Z520A000 X240A000
TIME 12:48:07
005
PAGE
1
THIS IS THE DATABASE FOR GWS............
DATE 08/18/2000
LIST RESOURCES ON TSO45
Resource name
Instance
TAPEDRIVE
EDRESO
EDR1
EDR2
EDR2
EDR3
TAPE
EANRESOCLAY
ALPHA
TSO45
REG7
REG8
OPDESK
(GLOBAL)
TSO45
MEDA
TSO45
(GLOBAL)
(GLOBAL)
(GLOBAL)
(GLOBAL)
(GLOBAL)
TSO45
TSO45
******* NUMBER OF RESOURCE NAMES REPORTED -
12
138
TUESDAY
Maximum
Shared
0001
0100
0001
0001
0001
0001
9901
0001
0001
0001
0010
0010
SEQ #
Active?
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
4Operator Commands
This chapter describes the Zeke operator commands that can be entered from any OS/390
console or from the /ZCOM functions of the Zeke online facility. All Zeke operator
commands (with the exception of ZKILL) can also be issued from any primary command
line in the Zeke ISPF online facility.
Entering Operator Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command Prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verifying Command Acceptance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering Multiple Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
140
140
141
141
142
142
143
Global Event Selection Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

ZADD Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
ZALTER Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Altering JCL Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Altering Other Event Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Altering System-related Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Altering Initiator Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
159
159
160
166
167
ZDELETE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

ZDISABLE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disabling Scheduled Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disabling Automatic Replies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disabling Electronic Vaulting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
172
172
173
174
ZDISPLAY Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Event Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Variable Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Initiator Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Automatic Reply Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying System Pool Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Zeke Agents Identifying Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Remote Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Communication Records Information . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Tracing Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
174
176
181
182
183
184
184
185
185
186
186
139
PathFinderDisplaying Preceding and Succeeding Events. . . . . . . . . . . . . . . . . . . . . 189

ZDISPLAY Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
ZENABLE Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
ZHOLD Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
ZID Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
ZINFO Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
ZKILL Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
ZMAP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
ZOK Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
ZREFRESH Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
ZRELEASE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
ZRELOAD Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
ZRESOURCE Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
ZSCAN Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
ZSET Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Set Variable Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Set Default System ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
ZSTATUS Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Entering Operator Commands

Enter Zeke operator commands from any OS/390 console or through the /ZCOM function
of the Zeke online facility. Zeke operator commands (with the exception of ZKILL) can
also be issued from any primary command line in the Zeke ISPF online facility.
Command Prefix
If you are running more than one Zeke, you must add an additional prefix to the Zeke
command to distinguish between systems. Use the CMDPREFX parameter in OASIS
options to add a prefix. Refer to the ASG-OASIS OS/390 Reference Guide for additional
information.
140
4 Operator Commands
Documentation Conventions
The following table describes the special conventions used within this chapter to flag
information in the operator command explanations. To learn how to format your operator
commands correctly, it is important that you understand how these text conventions are
used in this chapter.
UPPERCASE
Type the word exactly as shown.
lowercase
Variable. You must supply the value.
UPPERlower Illustrates command abbreviations. Upper case portion is required;

lower case portion is optional.
Command Abbreviations
Most Zeke operator commands and parameters are abbreviated. Command and parameter
abbreviations can be as few as the first 2 letters. The shortest form that is acceptable to
the system for each command is illustrated in the commands syntax diagram. Parameter
abbreviations are shown in the parameter description table following each commands
syntax diagram.
Example:
The syntax for the ZMAP command would be illustrated as follows:
ZMap
ALL
CLass
class-ID
The following parameters are valid with the ZMAP command. Notice that the ALL
parameter cannot be abbreviated, but the CLASS parameter can be abbreviated as CL.
Parameter
Description
none
Displays only the initiators running active Zeke jobs.

ZMAP
ALL
Displays initiators running active Zeke jobs and non-Zeke jobs. Only jobs
that started after Zeke came up are listed.
ZMAP ALL
141
Parameter
Description
CLass
Displays all jobs running in a specified dynamic class or all dynamic

classes.
ZMAP CL=C
Display all jobs running in dynamic class C.

ZM CLASS
Display all jobs running in all dynamic classes.
Command Syntax
Enter at least one space between a command and its first parameter.
ZHOLD SYSTEM
When you enter a value with a parameter, enter the value immediately following the
parameter. Separate the value and parameter with either one or more spaces, or an equal
sign.
ZDISPLAY JOB JOBNAME1
ZDISPLAY JOB=JOBNAME1
These two commands are equal.

When you enter multiple parameters with one command, separate the parameters by either
one or more spaces, or by a comma, but not both.
ZDISPLAY DQ,JOB
ZDISPLAY DQ JOB
These two commands are equal.
Verifying Command Acceptance

Zeke either rejects a command with an error message, or it processes the command and
reports on the results.
For example, an operator enters ZD JOB LATE to display all late job events. Any late job
events are displayed. If no job events are late, the system responds with an appropriate
message, such as:
Z0909W NO QUALIFYING ENTRIES.
142
4 Operator Commands
When one or more events match the parameter selection criteria, the number of events
selected is displayed on the console, such as:
Z09141 NUMBER OF EVENTS SELECTED WAS 3.
Entering Multiple Commands

Enter multiple Zeke commands on the command line simply by entering a command,
then following it with a second command, and so on.
Global Event Selection Parameters

A number of event selection parameters are available globally. These parameters are
available to be used with any Zeke operator command that requires event selection,
including ZALTER, ZDISABLE, ZDISPLAY, ZENABLE, ZHOLD, ZOK, ZREFRESH,
ZRELEASE, ZSTATUS, and ZSCAN.
The following table lists the global event selection parameters and notes instances where
the function of a specific parameters differs among command.
Parameter
Description
ALl
ZDISPLAYDisplays all scheduled events in the system or

specified systems.
ZDISPLAY ALL
Display all events regardless of status.

All other commandsSelects all the events.
ZHOLD ALL
Place operator hold on all events.

ZHOLD
This would select nothing.

Note:
Since ALL is a global parameter, it cannot be used with event

number or jobname alone.
143
Parameter
Description
APPLication
Specifies the application ID to match. Up to 3 characters. If the

operand is less than 3 characters, the comparison is made for as many
characters as entered.
ZD APPL P*
Select all events with an application ID beginning with P.

ZD APPL (INS)
Use delimiters when code might be confused with another

parameter.
CLass
Specifies the class an event must have in its class list to be selected.
Assumes the Job parameter.
ZD CLASS *
Selects all jobs with a class specified in their class list.

ZD CLASS A
Selects jobs with class A specified in their class list.

ZD DQ CL *
Selects jobs in the dispatch queue with any class specifed in their
class list.
ZD DQ CL A
Selects jobs in the dispatch queue with class A specified in their

class list.
DAte
Specifies a Julian date (YYDDD or YYYYDDD format) and selects

events for this date. (When using the YYDDD format, if the YY
portion of the date is greater than or equal to 50, it is considered a
20th century date (19xx); if it is less than 50, it is considered a 21st
century date (20xx).)
ZD EV 27 DA 2000001
Select only the schedule record of event 27 for January 1, 2000.

A date value of 99999 can be used with the following commands,
which use the Global Event Selection parameters to scan the
schedule for matching events: ZALTER, ZDELETE, ZDISABLE,
ZDISPLAY, ZENABLE, ZHOLD, ZOK, ZREFRESH,
ZRELEASE, and ZSCAN. When DATE 99999 is used within one of
these commands, Zeke scans the schedule for all events matching the
global event selection parameters entered, and then selects the events
with the earliest schedule date.
144
4 Operator Commands
Parameter
Description
Note:
Only uncompleted events will be selected; events that are done,

AEOJ, pending, active, or forced done will not be selected.
For example,
ZDISABLE APP JEM DATE 99999
Searches the schedule for all uncompleted events with an

application ID of JEM, and then disables the ones with the
earliest schedule date.
When using the DATE parameter in Zeke commands issued from an
SCOM event, a ZCOM event, or a ZEKESET utility job, the
keyword SCHDT can be entered in place of a Julian date. This tells
Zeke to substitute the events schedule date for the value SCHDT
before sending the command to the command processor.
ZADD JOB JOBADD DATE SCHDT
SCHDT is replaced with the schedule date of the event that

issued the command.
The SCHDT keyword works differently when used by a ZEKESET
batch job submitted outside of Zeke. In this case, the current system
date is substituted in place of SCHDT.
Note:
In order for the SCHDT keyword to be substituted within a

ZEKESET utility job, it must appear in a SET ZCOM or SET
SCOM statement.
DOne
Selects events that are successfully completed or disabled. If this

parameter is omitted, completed or disabled events are not selected
unless the EVENT parameter is specified.
ZD DONE
Select all completed events.

ZD DONE,JO
Select all completed job events.
145
Parameter
Description
DQ
Selects events that are in the dispatch queue. To select other events,
enter SQ. If both DQ and SQ are omitted, both are assumed.
ZD DQ
Select all events that are currently in the dispatch queue.

ZD DQ,ZC
Select only Zeke command events in the dispatch queue.

EName
Specifies an event name that must match. Up to 12 characters. To

perform generic selection, precede the jobname with an asterisk (*)
and enter only the characters to be compared. An asterisk in any
other position is considered to be a wildcard character.
ZDISPLAY ENAME *PAY ALL
Select all names beginning with PAY.

ZDISPLAY ENAME 01**********
Select names with any characters in positions 3 through 12.

ZALTER ENAME *PAY EARLY 1000 ALL
Requires the ALL parameter when used with ZALTER.

EVent
Specifies one or more event numbers to be selected. Enclose

multiple event numbers in parentheses and separate them with
commas or spaces. Up to 20 event numbers can be entered.
ZD EV 143
Select event 143 only.

ZA EV (10,11,12) WHENOK
Select events 10, 11, and 12.

ZADD EV (14 20 50)
Select events 14, 20, and 50.

FROm
Specifies a time (HH:MM). Selects events scheduled after this time.

ZD JOB FRO=1200
Select jobs scheduled after 12:00 (noon).

GE
Specifies a date (YYYYDDD). Selects events scheduled on or after

this date. This parameter must follow the keyword DATE.
ZD DATE GE 2000001
Select all events scheduled on or after January 1, 2000.
146
4 Operator Commands
Parameter
Description
GRoupid
Specifies the group ID to match. Up to 3 characters. If the operand is

less than 3 characters, the comparison is made for as many characters
as entered.
ZADD GROUP 1*
Select events with a group ID beginning with 1, provided

MultGr allows the add.
ZD GROUP 011
Select only events with a group ID of 011.

ZD GROUP T*
Select any events that have a group ID that begins with T.

ZD GROUP (INS)
Use delimiters when value might be confused with a parameter.

HOLD
Selects an event on hold, or with the specific hold specified.

ZD HOLD
Displays all jobs on hold.

ZD HOLD=NET
Displays all jobs on hold with a network hold.

JOb
ZDISPLAY CommandIf entered alone, displays job event

information. If a jobname value is specified, displays the event with
that jobname. If omitted, displays all job events. Up to 30 characters
are accepted, but case is not considered. Due to space restrictions, all
30 characters do not display on output.
ZD JOB
Display all jobs.

ZD JO *PR
Display all jobs that begin with PR.

ZD JOB PR**0001
Display all jobs that start with PR and end with 0001.
ZD JOB P*U*0*1*
Display all jobs that have P in position 1, U in position 3, 0 in

position 5, 1 in position 7.
147
Parameter
Description
All Other CommandsSpecifies the jobname of the event to

be selected. To perform generic selection, precede the jobname with
an asterisk (*) and enter only the characters to be compared. Also, an
asterisk in any other position is considered to be a wildcard
character. Up to 30 characters are accepted, but case is not
considered. For ZADD, mixed case is not allowed. To select all jobs,
enter a single asterisk as the jobname.
ZH JOB *
Hold all jobs.

ZA JOB * NEWCLASS B
Alter all job events to run class B.

LE
Specifies a date (YYYYDDD format). Selects events scheduled on

or before this date. This parameter must follow the keyword DATE.
ZD DATE LE 2000001
Select all events scheduled on or before January 1, 2000.

MSg
Selects all message events. More than one event type can be entered
on a command line.
ZD MSG
Display message events.

NETRegid
Selects all events waiting for a job on the specified NETREGID.

ZD NETR SYSC
Display events waiting for a job on SYSC.

REXx
Selects REXX events. All event types are selected if no event type is
specified. More that one event type can be entered on a command
line. For example,
ZD REX
Select all REXX events.

SCom
Selects all system command events. More than one event type can be
entered on a command line.
ZD SCO
Display all system command events.
148
4 Operator Commands
Parameter
Description
SQ
Selects events that are in the schedule queue and are not in the
dispatch queue. To select other events, enter DQ. If both DQ and SQ
are omitted, both are assumed.
ZD SQ,JOB
Select job events that are currently in the schedule queue.

ZD SQ
Select all events that are in the schedule queue.

SYstem
Specifies a 1- to 8-character system ID. Events owned by the

specified system are selected. If the specified system is not the
system the command is entered on, only events in the schedule queue
are selected. If this parameter is omitted, only the events from the
system where the command was entered are selected. Enter an
asterisk (*) with the ZDISPLAY command to display information
from all systems sharing the same Zeke database.
ZA EV 5 WHENOK SYS B
Alter an event on System B.

ZD SYSTEM *
Display the active schedule records from all systems.

ZD DONE SYS *
Display successfully completed events from all systems.

TARGet
Selects events with the specified target.

ZD TARG=SYS2
Selects all events with a target value of SYS2.

TO
Specifies a time (HH:MM). Selects events scheduled before this

time.
ZD JOB TO 1200
Select job events that are scheduled before noon.

ZD FRO=1200 TO=1600
Select all events scheduled between noon and 1600 hours (4:00
PM).
149
Parameter
Description
USerid
Specifies the user ID to match. If the operand is less than eight

characters, the comparison is made for as many characters as
entered.
ZD USERID OPERATOR
Select only events with user ID of OPERATOR.

ZD USERID OP*
Select any event that has a user ID that begins with OP.
ZD USER (ACC)
Select any event that has a user ID that begins with ACC.
Note:
Use delimiters when value might be confused with a parameter.

VCom
Selects only VM command events. More than one event type can be
ZD VCOM
Select all VM command events.

ZD VC ZC
Select all VM command and Zeke command events.

VER
Selects the specified version of the event. To specify a specific

version, enter the 1-to-5 digit version number.
ZDEL EV 30 VER 2
Delete all SQRs for version 2 of event 30.

ZDEL EV 30 DATE 2000001 VER 2
Delete only the SQR for schedule date January 1, 2000 for
version 2 of event 30.
If a version number is not specified, all versions of the event are
selected.
ZDEL EV 30
Delete all SQRs for event 30.

ZDEL EV 30 DATE 2000001
Delete all version of event 30 with a matching schedule date of

January 1, 2000.
150
4 Operator Commands
Parameter
Description
WORKCenter
Selects only work center events. More than one event type can be
ZD WORKC
Select all work centers.

Note:
The ZD WORKC command works only if generation option

Loadcomm is set to YES.
ZCom
Selects only Zeke command events. More than one event type can be
ZD ZCOM
Select all Zeke command events.

ZD ZC VC
Select all Zeke command and VM/SP CP command events.
151
ZADD Command
The ZADD command creates a schedule queue record for an existing Event Master
Record. Use this command to add any type of event, including an on-request event, to the
schedule. (You cannot ZADD an event template.)
Refer to your ASG-Zeke OS/390 Users Guide for information on manually adding events
to the schedule and setting Zeke to schedule itself.
Syntax
ZADd
EName name
EVent number
JOB name
APPLication app-ID
GROupid group-ID
USERid user-ID
ENable
HOld
RDAte yyyyddd
RDAte 99999
RDAte SCHDT
AUto
FORCE
CURRplus hhmm
NEWUSER user-ID
REBUIld
REfresh
RERUN
DAte yyyyddd
DAte 99999
DAte SCHDT
NOMSG
RUN
PREView
VER version-num
Parameters
The ZADD command requires the EVENT parameter (specifies event number), the
ENAME parameter (specifies event name), or the JOB parameter (specifies jobname). The
other parameters are optional.
Parameter
Description
AUTO
Adds one to the number of dispatch times value if the schedule record
is active. The REFRESH and ENABLE parameters are assumed. This
parameter is not valid for a comment event.
ZADD EV 19 AUTO
APPLication Searches for events with the specified application ID. Up to 8

characters. If you do not know the full application ID, enter the
beginning characters of the application ID or the letters you know
with wildcard characters in the place of the unknown characters. You
can enter a ? (question mark) to search for any single character or an
* (asterisk) in any position to search for all positions following it.
152
4 Operator Commands
Parameter
Description
ZADD APPL ACCT
Adds events with the application ID of ACCT to the schedule,

provided MultAp allows the add.
ZADD APPL Q?R*
Adds events with the application ID beginning with Q in position

1, any letter in position 2, and R in position 3 to the schedule,
provided MultAp allows the add.
ZADD APPL QU*
Adds events with the application ID beginning with QU to the

schedule, provided MultAp allows the add.
ZADD ENAME JOB* APPL ACCT
Adds events with the event name beginning with JOB and an
application ID beginning with ACCT to the schedule, provided
MultEn and MultAp allow the add.
Note:
When multiple matches are found, the parameter with the most
restrictive Mult(xx) generation option setting overrides the
specifications of the other parameters.
ALL
Adds all events matching the search pattern.
CURRplus
Updates the scheduled time on the event by adding the time specified
in this parameter to the current start time. If the current Sched time is
zero, the specified time is added to the system time and saved in the
Sched time field. Enter the amount of time you want to add to the
current system time to create the new schedule time of the job.
Specify the hour and minutes in a value between 0000 and 4800.
ZADD EVENT 123 CURRPLUS 0130
Changes the start time of event 123 to 1 hour and 30 minutes from
the current system time.
If the resulting start time is greater than 4800, the job is not added.
DAte
Format YYYYDDD or YYDDD. (When using the YYDDD format,

if the YY portion of the date is greater than or equal to 50, it is
considered a 20th century date (19xx); if it is less than 50, it is
considered a 21st century date (20xx).)
Specifies the schedule date for this event if it is different from the
system date.
ZADD EV 100 DA 2002091
153
Parameter
Description
By issuing the ZADD command with a date value of 99999, you can
add an event with the schedule date of the earliest event in the
schedule that is dependent on the event being added.
ZADD EV 234 DATE 99999
Searches the schedule for the earliest event (the event with the
earliest schedule date) that has not been dispatched because it is
waiting on Event 234. Event 234 is then added with that schedule
date. If no events are waiting on Event 234, Event 234 is added
with the current system date as the schedule date.
If you issue a single ZADD command to add multiple events, a
schedule date is calculated for each event as it is added.
By issuing the ZADD command with a date value of SCHDT, a new
event can be added to the schedule with the same schedule date as the
event issuing the ZADD command.
If the ZADD...SCHDT command is issued from a ZCOM event, a
Z-type command in an SCOM event, or a SET ZCOM statement from
a ZEKESET utility program dispatched as a Zeke event, the new
event is added to the schedule with the same schedule date as the
event issuing the command. If the ZADD...SCHDT command is
issued from any other environment, the current system date is used as
the new events schedule date.
ENable
Changes the schedule record's status to ENABLE from a disabled

status.
ZADD EV 19 ENABLE
ENAMe
Searches the catalog for the specified event name. Up to 12

characters. If you do not know the event name, enter the beginning
characters of the event name or the letters you know with wildcard
characters in the place of the unknown characters. You can enter a ?
(question mark) to search for any single character or an * (asterisk) in
any position to search for all positions following it.
Note:
If the operand in fewer than 12 characters, the comparison is made

only for the number of characters entered, including wildcard
characters.
154
4 Operator Commands
Parameter
Description
ZADD ENAME TESTJOB00001
Adds event name TESTJOB00001 to the schedule.

ZADD ENAME EVNTNAM?
Adds event names beginning with the character string

EVNTNAM and any alphanumeric value in position 8 to the
schedule, provided MultEn allows the add.
ZADD ENAME EVNTNAM? ALL
Adds all event names beginning with the character string

EVNTNAM and any alphanumeric value in position 8 to the
ZADD ENAME 01******
Adds 8-character event names beginning with 01 to the schedule,

provided MultEn allows the add.
ZADD ENAME 01**********
Adds 12-character event names beginning with 01 to the

ZADD ENAME JOB* APPL ACCT
Adds events with the event name beginning with JOB and an
application ID beginning with ACCT to the schedule, provided
MultEn and MultAp allow the add.
Note:
When multiple jobs matches are found, the parameter with the most
EVent
Searches the database for the specified event numbers. Follow this
parameter with one or more event numbers. Enclose multiple event
numbers in parentheses and separate them with commas or spaces. Up
to 20 event numbers can be entered.
ZADD EV 19
ZADD EV (19,45,100)
FORCE
Releases an event's resources before the event is re-added using the

ZADD REBUILD command. This produces the same result as issuing
the ZRESOURCE RELEASE command to release the resources
followed by the ZADD REBUILD command. If there are no
resources for the event, this parameter is ignored.
ZADD EV 12 REBUILD FORCE
155
Parameter
Description
GROup
Adds one or more events with the specified group ID to the schedule.
The MULTGR generation option (refer to your ASG-Zeke OS/390
Users Guide) indicates the action to take when more than one event
matches the specified group ID.
ZADD GROUP OPR
Adds events with the group ID of OPR to the schedule.

HOld
Places an operator hold on the event after it is added, refreshed, or

enabled. This parameter is not valid for a comment event.
JOB
Searches the database for the specified jobname. Mixed case

jobnames are not allowed.
ZADD JOB TESTJOB
To enter a generic jobname, enter an asterisk followed by the pattern

(*ABC). You can also use an asterisk as a wildcard character in the
jobname (AB*D).
Note:
When multiple jobs matches are found, the parameter with the most
NEWUSER
The new user ID to be associated with the SQR being created. If this
parameter is specified, the security call checks this new user ID for
ALTER level access to the SQR. If this parameter is not specified, the
security call checks the user ID specified in the EMR.
Once the SQR is created with a new user ID, all subsequent security
calls will use the NEWUSER value (in the SQR Userid field).
This parameter allows different versions of an SQR to be associated
with different user IDs.
ZADD EV (5,6,7) VER 33 NEWUSER ABC
Adds a version 33 SQR to the schedule with a user ID of ABC for

each of the specified events.
NOMSG
Suppresses messages Z0905I and Z0906W.
PREView
Produces a list of events that would be added to the schedule if the

command string was submitted without the Preview parameter.
ZADD GROUP OPR PREVIEW
Displays a preview of events to be added from GROUP OPR.
156
4 Operator Commands
Parameter
Description
RDate
Format YYYYDDD or YYDDD. (When using the YYDDD format, if

the YY portion of the date is greater than or equal to 50, it is
Specifies the run date to be associated with the schedule record. An
event that has a future run date is not run until that date; however, the
events WHEN conditions may or may not be tracked throughout the
period depending upon the setting of the generation option Trigdate.
By issuing the ZADD command with an RDATE value of SCHDT, a
new event can be added to the schedule with the same run date as the
event issuing the ZADD command.
If the ZADD...SCHDT command is issued from a ZCOM event, a
Z-type command in an SCOM event, or a SET ZCOM statement from
a ZEKESET utility program dispatched as a Zeke event, the new
event is added to the schedule with the same run date as the event
issuing the command. If the ZADD...SCHDT command is issued
from any other environment, the current system date is used as the
new events run date.
By issuing the ZADD command with a date value of 99999, you can
add an event with the run date of the earliest event in the schedule that
is dependent on the event being added.
ZADD EVENT 234 RDATE 99999
Searches the schedule for the event with the earliest run date that
has not been dispatched because it is waiting on event 234. Event
234 is then added with that run date. If no jobs are waiting on
event 234, it is added with the current system date as the run date.
If you issue a single ZADD command to add multiple events, a run
date is calculated for each event as it is added.
REBUIld
Recreates the schedule record. (If a schedule record does not exist,
this parameter is ignored.) This produces the same result as deleting
an SQR and re-adding it.
Resets all WHEN conditions
Reflects any Event Master Record changes
Resets any ZALTER changes to the Event Master Record

values.
ZADD EV 19 REBUILD
157
Parameter
Description
REfresh
Refreshes a schedule record (regardless of its status). The ZADD

REFRESH does not place an operator hold on the event like the
ZREFRESH command does.
ZADD EV 19 REFRESH
RERUN
Adds the RERUN designation to the schedule record. The RERUN

designation appears in the ZDISPLAY output and is passed to the user
exit ZEKE14D. If the option TRIGRRN=NO, the event will not
trigger the WHEN conditions of other events. Use the NORERUN
parameter of the ZALTER command to remove the RERUN
designation.
RUN
Satisfies the following conditions for a event: TIMEOK, WHENOK,

OPEROK, NOTDURING, and ZRELEASE. Checks the following
conditions before dispatching the event: SYSTEM HOLD,
INITIATOR, TAPES and RESOURCES. Any NOTDURING clauses
are ignored. Adds the event to the schedule using the event master
record information.
ZADD JOB TSO1H001 RUN
USERid
Adds one of more events with the specified user ID to the schedule.
The MULTUS generation option (refer to your ASG-Zeke OS/390
Users Guide) indicates the action to take when more than one event
matches the specified user ID.
ZADD USER DEV
Adds events with the user ID of DEV to the schedule.

VER
Adds the specified version of the event to the schedule. However, if

the VERLOAD field on the EMR for the event is set to zero, you can
only add a version zero SQR. The maximum allowed versions of an
event is 32767.
ZADD EV 5 VER 99
Creates an SQR for version 99 of event 5.

ZADD EV (5,6,7) VER 99
Creates SQRs for version 99 of events 5, 6, and 7.

If you issue the ZADD command without the VER parameter, and if
the VERLOAD field is greater than zero, Zeke will add 1 to the
highest version in the schedule and create an SQR for that version. For
example, if there are no versions of the event in the schedule, version
1 is added. If the highest version in the schedule is 7, version 8 is
added.
158
4 Operator Commands
ZALTER Command
The ZALTER command temporarily alters schedule record information, some
system-related features, and initiator availability. When changing event-related
information, at least one of the Global Event Selection parameters is required. See
"Global Event Selection Parameters" on page 143 for a listing.
Altered schedule record information does not modify the Event Master Record. Only the
information of a specific occurrence of an event is changed, its permanent information is
not altered.
Altering JCL Source

Syntax
ZAlter
global
CONDORMember name
CONDORPass password
CONDORVersion version
FName CMS-name
FType CMS-type
LIBRarian name
PANvalet name
PDSDd name
PDSMem name
ZEKEJcl
Parameters
Parameter
Description
CONDORMember
Condor member name that is retrieved when the event is

dispatched.
CONDORPass
Condor password that is passed to CONDOR when the event is

dispatched.
CONDORVersion Condor version that is passed to Condor when the event is

dispatched.
FName
Specifies the CMS file name that is retrieved when the event is
dispatched. The filename can be up to 8 characters in length.
FType
Specifies the CMS file type that is retrieved when the event is
dispatched.The file type can be up to 4 characters.
LIBRarian
LIBRARIAN member name accessed during job submission.
159
Parameter
Description
PANvalet
Panvalet member name used during job submission.
PDSDd
PDS DD name used during job submission.

ZA EV 14 PDSD ZEKDD1
Changes the PDS name for event 14.

PDS member name used during job submission.
PDSMem
ZA EV 14 PDSM JOBABC
Changes the PDS member for event 14.

Zeke JCL.
ZEKEJcl
Altering Other Event Fields

The following parameters are used with the ZALTER command to change selected
schedule records. The event selection logic notifies the operator of how many event
records were modified.
Syntax
ZAlter
global
CONtrol
YES
NO
NX
DURation hhmm
EArly hhmm
FReq hhmm
LAte hhmm
MUSTEnd hhmm
NOTAfter hhmm
SChed hhmm
DOne
Failure
SYNch
LOCAL
REMOTE
NEWTARG=netregid
NEWSysid systemid
NOTDUROk
RUN
TIMEOk
WHENOk
(class, ...)
PRiority nn
TApes nn
TImes nnn
NORERun
RERUN
NOTRig
TRIG
WHENAND condition
AT netregid
WHENOR condition
AT netregid
condition
160
DPRI nn
NEwclass
AT netregid
4 Operator Commands
Parameters
At least one of the Global Event Selection Parameters (starting on page 143) is required.
If you use ENAME, the parameter ALL is required.
Parameter
Description
AT
Used with the WHENAND, WHENOR, or WHENOK parameter to

add or WHENOK a remote WHEN condition. AT specifies the
NETREGID of the remote system.
ZALTER EV 1 WHENAND (EOJ JOBC AT SYSB)
ZALTER EV 1 WHENOR (EOJ JOBC AT SYSB)
ZALTER EV 1 WHENOK (EOJ JOBB AT SYSB)
CONTrol
DOne
Required. The code indicating whether this job is tracked as an

Zeke-controlled job. Zeke-controlled jobs are tracked throughout the
entire execution.
YES
Default. Zeke recognizes this event as an Zeke-controlled

event.
NO
Zeke does not recognize this event as an Zeke-controlled

event and marks the event as SUCC upon dispatch.
NX
Zeke recognizes this event as a non-executable

Zeke-controlled event.
Forces an event to F/S (Forced Success) status. F/S satisfies the

WHEN conditions for any events that reference that event.
ZA JOB TS01H001 DONE
DPRI
Changes the event's dispatch priority number. Values are between 1

and 99, 1 being the highest priority.
DURation
Format HHMM. Changes the event's average duration time. Specify

the hour and minute.
ZA EV 100 DUR 0300
EArly
Format HHMM. Changes the earliest time the event can be

dispatched. Specify the hour and minutes in a value between 0000 and
4759.
ZA EV 14 EA 0100
Failure
Marks the event with a F/F (Forced Failure) status and triggers any
failure dependencies.
ZA EV 35 FAILURE
161
Parameter
Description
FReq
Format HHMM. Changes the time between dispatches for a recurring

event. Specify the hour and minutes in a value between 0000 and
4759.
ZA JOB TS01H001 FR 0010
LAte
Format HHMM. Changes the time an operator is to be notified if the

event has not been dispatched. Specify the hour and minutes in a value
between 0000 and 4759.
ZA JOB *PAY LA 2000
MUSTEnd
Format HHMM. MUSTEND time for this event.

ZA EV 1 MUSTE 1105
NEwclass
Changes the class list for a job event. If a value is not entered, the
event can run in any class. If one or more values are entered, the event
can only run as one of those classes.
ZA EV 46 NEWCL
ZA EV 46 NEWCL B
ZA EV 46 NE (F,V,Q,R,S,T)
NEWTARG
Changes the NETREGID of the system where the job event is

executed.
ZA JOB *CER TARG=AANAS400 NEWTARG=RMTSYS2
Changes the target information for all job events with jobnames
beginning with CER and target of AANAS400 to RMTSYS2.
Note:
You may not use the ZALTER command with NEWTARG keyword
NEWSysid
Changes the system ID where the job event is executed.

ZA EV 45 SYS B NEWSYS A
NORERun
Removes the RERUN designation. See the "RERUN" parameter for

more information.
NOTAFter
Format HHMM. Time after which the event cannot be dispatched.

ZA EV 1 NOTAF 1600
NOTDUROk
Removes the NOTDURING requirements from an event.

ZA EV 77 NOTDUROK
162
4 Operator Commands
Parameter
Description
NOTRig
Changes an event so that it does not participate in any type of trigger.

ZA JOB JOBC NOTRIG
WEAK conditions can still be satisfied by an event that has been

ZALTERd with NOTRIG. For example, normally, if JOB C is in the
schedule, the WHEN condition WHEN (WEOE JOBC) would not be
weakly satisfied and would not be marked with a #. However, if JOB
C is ZALTERd with the NOTRIG option, the WHEN condition will
be weakly satisfied and will be marked with a # because the NOTRIG
option causes JOB C to be completely ignored for triggering
purposes. Since Zeke does not find JOB C when checking weak
conditions, all weak conditions that refer to JOB C will be weakly
satisfied.
PRiority
Changes the job OPSYS priority. Specify a value between 1 and 15.
ZA JOB *AR PRI 4
RERUN

exit ZEKE14D. If the option TRIGRRN=NO, the event will not
designation.
RUN
Satisfies the following conditions for an event: TIMEOK, WHENOK,

OPEROK, NOTDUROK, and ZRELEASE. Checks the following
conditions before dispatching the event: SYSTEM HOLD,
INITIATOR, TAPES and RESOURCES. Any NOTDURING clauses
are ignored for this SQR, until a new one is added re-using the EMR
information.
ZA JOB TS01H001 RUN
SChed
Changes the time an event is scheduled to run (SCHEDULE time).

Specify the hour and minutes in a value between 0000 and 4759.
ZA EV 432 SC 1200
SYNch
Synchronizes the schedule records downloaded to a Zeke Agent when

the job status on Zeke does not match the job status on Zeke Agent.
LOCAL
Use this keyword when the Zeke copy of the schedule

queue record is out-of-date, as indicated by STALEZ in
the DL Status field in Schedule View.
ZALTER JOBA SYNCH=LOCAL
Zeke sends a request to Zeke Agent for the updated

information and rebuilds the schedule record.
163
Parameter
Description
REMOTE Use this keyword when the Zeke Agent copy of the
schedule record is out-of-date, as indicated by STALEA in
the DL Status field in Schedule View.
ZALTER JOBA SYNCH=REMOTE
Zeke downloads the updated schedule record to Zeke

Agent.
TApes
Change the number of available tape drives required before an event

can be dispatched. If you enter zero, the system does not check for
tape drives.
ZA EV 56 TA 2
TIMEOk
Satisfies the time requirement, regardless of the actual time.

ZA JOB *AR TIMEOK
TImes
Changes the number of times a recurring event is to be dispatched.

Specify a number between one and 255.
ZA EV 56 TI 4
TRIG
Reverses the effect of the NOTRIG parameter if this parameter is

entered before the event is dispatched. The event can now trigger
other events. See the "NOTRig" parameter for more information.
ZA EV 6 TRIG
WHENAND
Adds a specified WHEN condition in addition to the existing WHEN

conditions.
ZA EV 5 WHENAND (EOJ JOB1)
Add the specified clause to the existing WHEN condition with an

and relationship. This means that the added clause must be
satisfied in addition to the existing WHEN condition.
ZALTER EV 1 WHENAND (EOJ JOBC AT SYSB)
Add a remote WHEN condition with an and relationship.
164
4 Operator Commands
Parameter
Description
WHENOk
Satisfies prerequisites (WHEN conditions) for the specified event. If

the event is time satisfied when this parameter is used, the event
moves from the schedule queue to the dispatch queue.
Note:
If there are existing WHEN conditions, you must add any additional
WHEN conditions before issuing a WHENOK. When you issue a
ZALTER WHENOK, Zeke will not recognize subsequently added
WHEN conditions.
ZA EV 1 WHENOK
Satisfy all WHEN conditions for event 1.

Satisfy the remote WHEN condition.

ZA EV 5 WHENOK EOJ JOB1
Satisfy the EOJ JOB1 WHEN condition for event 5. Any other
WHEN conditions for event 5 are not affected.
ZA JOB *PAY WHENOK VAR $GO
Satisfy the WHEN condition for the variable $GO for all job
events whose jobnames begin with PAY. The value of $GO is not
changed.
Satisfy the EOJ JOBB WHEN condition for event 1 on the remote
system SYSB.
ZALTER EV 5 VER 2 WHENOK (EOJ JOBA VER 2)
Satisfy the specified WHEN condition for version 2 of event 5.

Parentheses are required when using the VER keyword.
ZALTER EV 25 WHENOK (EOJ JOBA, WEOJ JOBB, AEOJ JOBC,
BOJ JOBD)
Satisfy the specified multiple WHEN conditions for event 25.

Any other WHEN conditions for event 25 are not affected.
165
Parameter
Description
WHENOR
Adds a specified WHEN condition to the existing WHEN conditions

with an OR condition.
ZA EV 5 WHENOR (EOJ JOB1)
Add the EOJ JOB1 WHEN condition to the existing WHEN

conditions for event 5. The event is WHEN satisfied when either
the existing WHEN condition or this newly added one is satisfied.
ZA EV 5 WHENOR '(EOJ JOB1 and EOJ JOB2) OR (VAR $A
EQ GO)'
Add the specified WHEN conditions to the existing WHEN

conditions for event 5. The event is WHEN satisfied when one of
the following conditions is satisfied:
Existing conditions
EOJ JOB1 and EOJ JOB2
VAR $A EQ GO
ZALTER EV 1 WHENOR (EOJ JOBC AT SYSB)
Add a remote WHEN condition with an or relationship.
Altering System-related Features

Syntax
ZAlter
HOLDCms
NOMSG
SMF
Parameters
Parameter
Description
HOLDCms
Turns off messages to the console and places a hold on any events that
would have generated this message. Otherwise, messages appear on the
operator console if the Zeke1 machine stops processing JCL requests.
ZA HOLDCMS
NOMSG
SMF
This parameter toggles on and off the trace messages when Zeke calls the
SMF exits.
ZA SMF
166
4 Operator Commands
Altering Initiator Availability

Zeke maintains a table that contains the times each initiator is available. Specify the days
and times each initiator is available to Zeke through the online facility. Use the ZALTER
INITIATOR command to temporarily override the table. To reset the times, issue the
ZRELOAD INIT command.
SyntaxParameters
ZAlter
IN init-ID
AVailable (from-hhmm, to-hhmm,...)

DAY n
Use the following parameters with the ZALTER INITIATOR command.

Parameter
Description
AVailable
Required. Changes the times an initiator is available. Specify the start

and stop times in parentheses, separated by a comma. Multiple start
and stop times (up to four ranges) can be entered.
ZA IN T1 AV (0,400,0800,2400)
Make initiator T1 available to Zeke from 00:00 to 4:00, and from

8:00 to 24:00.
INitiator
Required. Changes the named initiator ID.

ZA IN T1 AV (0,2400)
Make initiator T1 available to Zeke from 00:00 to 24:00.

Note:
If you are using JES3 or generation option DISPSEL=NO, the

ZALTER INITIATOR command is not valid.
DAY
Changes the day the initiator is available. Specify a number between

one and seven representing the day. The current day is assumed unless
this parameter is used.
ZA IN T1 AV (0,2400) DAY 3
Make initiator T1 available to Zeke from 00:00 to 24:00 on

Wednesday.
167
ZDELETE Command
The ZDELETE command deletes variables from the Zeke database or deletes schedule
queue records from the schedule, depending on the parameters used.
Deleted variables are added to the system again if used in a ZEKESET SET VAR
statement, or in the ZSET operator command, because Zeke variables are added when first
used.
After a schedule queue record has been deleted, a new schedule queue record for the same
event can be added via the ZADD command and any new information in the Event Master
Record for that event is reflected in the added schedule queue record.
Syntax
ZDELete
EName name
EVent number
JOB name
APPLication app-ID
GROupid group-ID
USERid user-ID
VAriable var-name
DAte yyyyddd
FORCE
PREView
ALL
VER number
Parameters
Use the following parameters with the ZDELETE command:
Parameter
Description
APPLication Deletes the event or the selection of events that have the specified
application ID. If you do not know the full application ID, enter the
beginning characters of the application ID or the letters you know
with wildcard characters in the place of the unknown characters. You
can enter a ? (question mark) to search for any single character or an
* (asterisk) in any position to search for all positions following it.
ZDEL APPL PAY
Deletes the first event with the application ID of PAY from the
schedule.
ZDEL APPL P?Y
Deletes the first event with the application ID beginning with P in

position 1, any letter in position 2, and Y in position 3 from the
schedule.
ZDEL APPL AY*
Deletes the first event with the application ID beginning with AY

from the schedule.
168
4 Operator Commands
Parameter
Description
DAte
Format YYYYDDD or YYDDD. (When using the YYDDD format,

if the YY portion of the date is greater than or equal to 50, it is
Deletes the named event for the specified Julian date (in the case of
multiple occurrences of the event on different dates).
ZDEL EV 10 DATE 2001091
EVent
Deletes the named event.

ZDELETE EV 5
ZDEL EV (3,5)
A console message is issued upon successful completion of a delete.

ENAME
Searches the catalog for the specified event name. If you do not know
the event name, enter the beginning characters of the event name or
the letters you know with wildcard characters in the place of the
unknown characters. You can enter a ? (question mark) to search for
any single character. If the operand is less than eight characters, the
comparison is made for as many characters as entered.
ZDEL ENAME EVNTNAM1
Deletes event name EVNTNAM1 from the schedule.
ZDEL ENAME EVNTNAM*
Deletes the first event name beginning with the character string
EVNTNAM and any letter in position 8 from the schedule.
FORCE
Releases an event's resources before deleting the event's schedule

record. This produces the same result as releasing all of the resources
and then deleting the event. If there are no resources for the event, this
parameter is ignored.
ZDEL EV 12 FORCE
169
Parameter
Description
GROup
Deletes the event or selection of events that have the specified group
ID. If you do not know the full group ID, enter the beginning
characters of the group ID or the letters you know with wildcard
characters in the place of the unknown characters. You can enter a ?
(question mark) to search for any single character or an * (asterisk) in
any position to search for all positions leading or following it.
ZDEL GROUP OPR
Deletes the first event with the group ID of OPR from the
schedule
ZDEL GROUP O?R
Deletes the first event with the group ID beginning with O in

position 1, any letter in position 2, and R in position 3 from the
schedule.
ZDEL GROUP OP*
Deletes the first event with the group ID beginning with OP from
the schedule.
JOB
Searches for events with the specified jobname. If you do not know
the jobname, enter the beginning characters of the jobname or the
letters you know with wildcard characters in the place of the unknown
characters. You can enter a ? (question mark) to search for any single
character or an * (asterisk) in any position to search for all positions
following it.
ZDEL JOB TESTJOB1
Deletes events with the jobname TESTJOB1 from the schedule.
ZDEL JOB TESTJOB?
Deletes the first event with a jobname beginning with the

character string TESTJOB and any letter in position 8 to the
schedule.
ZDEL JOB *B1
Deletes events with jobnames ending in B1 from the schedule.
PREView
Produces a list of events that would be deleted from the schedule if the
command string was submitted without the Preview parameter.
ZDEL GROUP OPR PREVIEW
Displays a preview of events to be deleted for GROUP OPR.
170
4 Operator Commands
Parameter
Description
USERid
Searches for scheduled events with the specified user ID. If you do not
know the full user ID, enter the beginning characters of the user ID or
the letters you know with wildcard characters in the place of the
unknown characters. You can enter a ? (question mark) to search for
any single character or an * (asterisk) in any position to search for all
positions leading or following it.
ZDEL USER DEV
Deletes the first event with the user ID of DEV from the schedule.
ZDEL USER D?V
Deletes the first event with the user ID beginning with D in

position 1, any letter in position 2, and V in position 3 from the
schedule.
ZDEL USER EV*
Deletes the first event with the user ID beginning with EV from
the schedule.
VAriable
Deletes the named variable.

ZDELETE VAR $XZY
ZDEL VAR $MSGON
A console message is issued upon successful completion of a delete.

VER
Deletes the specified version of the event. If a 1-to 5-digit version

number is not specified, all versions of the event are deleted.
ZDEL EV 30 VER 2
Delete all SQRs for version 2 of event 30.
ZDEL EV 30 DATE 2000001 VER 2
Delete only the SQR for schedule date January 1, 2000 for
version 2 of event 30.
171
ZDISABLE Command
The ZDISABLE command disables selected events or automatic replies. A display of
done events includes disabled events, which are noted on the screen. Disabled events are
deleted from the schedule, and dropped at the same time other completed events are
dropped (typically when the next day's schedule update is processed).
Refer to your ASG-Zeke OS/390 Users Guide for more information on disabling auto
replies.
Disabling Scheduled Events

Disabling a schedule queue record does not effect future scheduling of that event. As with
all operator commands, the Event Master Record is not changed. To enable a disabled
event, use the ZENABLE command.
Syntax
ZDISAble
global
Parameters
Use any of the Global Event Selection Parameters (starting on page 143) with the
ZDISABLE command.
Examples
The following are examples of using the ZDISABLE command and some of the Global
Event Selection parameters:
ZDISABLE EV 56
Disable the schedule record for event 56.
ZDISA EV 56 DA 2001001
Disable the schedule record for event 56 that is dated January 1, 2001.
ZDISA JOB *PR DA 2001001
Disable all job events with a jobname beginning with PR for schedule date January
1, 2001. These are the prior days jobs that are being removed from the schedule
manually.
Note:
The ZDISABLE command prevents WHEN conditions referring to that event from being
satisfied.
172
4 Operator Commands
Disabling Automatic Replies

To disable an auto reply for an event that is not running, use the REPLY and EVENT
parameters.
Syntax
ZDISAble
REPly
EVent num
INITiator init-ID
JOBname name
Parameters
Use the following parameters with the ZDISABLE command to disable automatic
replies:
Parameter
Description
EVent
Specifies the event number for which the auto reply is to be disabled.
The auto reply can only be disabled before the event is dispatched.
JOBname
jobname for which you want to disable automatic replies.
INITiator
If the event is running, you must disable the auto replies for that
initiator/partition. Enter the initiator ID with the REPLY and INIT
parameters.
ZDISA REP INIT T3
Disables the auto reply currently active in initiator T3.

REPly
Disables the auto reply for the specified event.

ZDISA REP EV 77
Disables auto reply for event 77.
173
Disabling Electronic Vaulting

You can disable electronic vaulting while Zeke is active. See "VAULTControlling the
Vault Dataset" on page 64 for syntax for performing the function in batch.
Syntax
ZDISAble
VAULT
Parameters
Use the following parameter with the ZDISABLE command to disable electronic
vaulting:
Parameter
Description
VAULT
Disables electronic vaulting.
ZDISPLAY Command
The ZDISPLAY command displays the following types of requested information:
174
Information about events (STATUS, TIMES, etc.)
The value and current status of a Zeke variable
The times that initiators are considered available, along with status information
Automatic replies that are active for a job event
The system IDs contained in a system pool
The CPUs currently running
Tracing calls to the schedule and variable monitors, and Zekes security routine
Listing event predecessor and event successor information for an event with other
events dependent upon it and for an event that is dependent upon others
Catalog and vault volume and dataset information
4 Operator Commands
Unless one of the following parameters is entered, Zeke assumes the ZDISPLAY request
is for event information.
Display Type
For more informtion, see...
Variable
"Displaying Variable Information" on page 181
Initiator Availability
"Displaying Initiator Information" on page 182
Auto Replies
"Displaying Automatic Reply Information" on page 183
System Pool
"Displaying System Pool Information" on page 184
Communications
Records
"Displaying Communication Records Information" on page 185
Database Information "Displaying Database Information" on page 186

Agent Schedule
Download
Information
"Displaying Zeke Agents Identifying Information" on page 184
Remote Prerequisite
Information
"Displaying Remote Prerequisites" on page 185
Variable Monitor
"Displaying Tracing Messages" on page 186
Zeke JCL Exits
Schedule Monitor
Zeke Security
Monitor
175
Displaying Event Information

You can display information about events, such as status, schedule times, and JCL
sources.
Syntax
ZDisplay
global
ABend
ACTive
DONE
FRee
HOld
LAte
NEEDOk
PEnding
RECurring
RESOurce
TARGet=value
STATus
TApes
WAit
WHendetail
XRef
COM
DEsc
DLStatus
INfo
JCLD event-name
NOte
STimes
ACTIVE
DISpatched
FAIL
QUEued
SCHeduled
SUCcess
var-name
jobname
program
Parameters
To display event information, you can use both the event parameters as described in the
following table or the Global Event Selection Parameters (starting on page 143).
Parameter
176
Description
ABend
Selects the events that were dispatched and terminated abnormally.
ACTive
Selects all events that are currently processing.
COM
Displays the active Zeke systems that are sharing the database. The
COM parameter is valid only in multi-CPU environments.
DEsc
Displays the associated description for the selected event.
DLStatus
Displays the download status of events.
4 Operator Commands
Parameter
DOne
Description
Selects only completed events.

ZD DO
Displays all completed scheduled events.

ZD JCLN DONE
Displays completed job events.

FRee
Selects only events that are not on operator hold.

ZD JO FRE
Select job events that are not on operator hold.

HOld
Selects only events that are on hold.

ZD JOB HO
Select job events on hold.

HOLD can be used with a qualifier such as OPER, SJCL, NET,
RFSH, DNPL, PSID, INTR or REXX to select events that are on hold
for a particular reason.
ZD HOLD=SJCL
Selects events on hold with a job card or JCL submittal problem.

ZD HO=REXX
Select REXX events on hold with a REXX dispatch error.

INfo
Displays the event name, application, group, and user ID. Display
Format 4 is used (message Z0926I).
JCLD
Displays the JCL source for a specified event.

ZD JCLD EV 2
Display the JCL source for event 2.

LAte
Selects late events. An event is late when it is not dispatched before

its late time.
ZD LATE
Display all late events.

ZD JOB LA
Display late job events.

ZD JO LA DQ
Display late job events in the dispatch queue.

177
Parameter
NEEDOk
Description
Selects only events that require an operator OK.

ZD ZC NEEDOK
Select Zeke command events that require an operator OK.

NOTDuring
Selects events with one or more NOTDURING conditions specified.
NOte
Displays up to six lines of information about the event.
PEnding
Selects jobs that are pending.

ZD PE
Displays all pending events.

ZD JOB PE
Displays pending job events.

RECurring
Selects only recurring events.

ZD JOB REC
Select recurring job events.

RESOurce
Displays the events that have resource requirements.

ZD ZC RESO
Display Zeke command events that have resource requirements.

TARGet
Displays job events with the specified target.

ZD TARGET=*REMOTE
Display all job events with a Target value of *REMOTE specified

in its EMR.
178
4 Operator Commands
Parameter
STATus
Description
Selects the events that have the specified status.

ACTive
Displays events currently running.
DISpatched
Displays events that have been dispatched but

have not started running.
FAIl
Displays events that did not satisfy the time and

WHEN conditions.
QUEued
Displays events that are in the dispatch queue.
SCHeduled
Displays events that have not satisfied the time

and WHEN conditions.
SUCcess
Displays events that completed successfully.

For example,
ZD STAT SUC
Displays all events that completed

successfully.
STimes
Displays the values for each of the event's defined times: Early,
Schedule, Late, Mustend, Notafter, and Duration.
TApes
Selects job events that use tape drives. The JOB parameter is
assumed.
ZD TAPES
Select all job events that use tape drives.

ZD TAPE,LATE
Select all job events that use tapes and are late.
WAit
Selects events in the dispatch queue and uses Display Format 3. The
reason each event is waiting in the dispatch queue is displayed next to
each event.
ZD WAIT
Select all events in DQ status, and show the WAIT reasons.

ZD WA,JOB
Select all job events in the dispatch queue and show the reason
each is waiting.
179
Parameter
WHendetail
Description
Selects events with WHEN condition statements and displays the

status of the prerequisite. Additional lines are displayed for each
prerequisite. Use this parameter to determine what conditions are
delaying the dispatching of an event.
ZD EV 13 WH
XRef
Zeke satisfied the WHEN condition.
An operator command was used to manually

satisfy the WHEN condition.
A weak WHEN condition was satisfied because

the event to satisfy the condition is not in the
schedule.
Selects events with WHEN conditions that contain the specified

jobname, program name, or variable. Produces the same display
format as the WHENDETAIL parameter.
ZD XREF $VAR1
Display WHEN information for events triggered by $VAR1.

ZD XR JOBA
Display WHEN information for events triggered by job JOBA.

ZD XR PROGA
Display WHEN information for events triggered by program

PROGA.
180
4 Operator Commands
Displaying Variable Information

You can display the value and current status of a Zeke variable.
Syntax
ZDisplay
VAriable $var-name
ALL
Parameters
The following parameters, when used with the ZDISPLAY command, display the value
of a Zeke variable, along with some other related information.
Parameter
Description
VAriable
Specifies the name of the Zeke variable to display. The Zeke variable
must begin with a dollar sign ($) and can be from 2 to 16 characters.
ZD VAR $XYZ
Display the value of Zeke variable $XYZ.

ALL
Displays the value of the Zeke variable and some status information.
Must be used with the VARIABLE parameter.
ZD VAR $ABC ALL
Display the value of Zeke variable $ABC and related status

information.
Note:
These parameters cannot be used with OASIS variables.
181
Displaying Initiator Information

You can display the times each initiator is available. Specify the days and times each
initiator is available to Zeke through the online facility.
Syntax
ZDisplay
IN init-ID
AVailable
DAY n
Parameters
Use the following parameters of the ZDISPLAY command to display this information.
Parameter
Description
AVailable
Displays the times an initiator is available. All initiators are displayed,

unless the INITIATOR parameter is specified. The current day is
assumed, unless the DAY parameter is specified.
ZD AV
Display today's times and classes for all initiators. If you are
using JES3 or generated Zeke with the option Dispsel=NO, the
ZDISPLAY AVAILABLE command is not valid.
INitiator
Displays the named initiator information only.

ZD INI I7
Display information for initiator I7.

DAY
Display initiator information for the specified day. Specify a number

between one and seven representing the day. The current day is
assumed, unless this parameter is used.
ZD AV,DAY=5
Display initiator information for Friday.

ZD DAY=5
Display initiator information for Friday (AV is assumed).

ZD DAY 4 INI I5
Display initiator I5 information for Thursday.
182
4 Operator Commands
Displaying Automatic Reply Information

You can display the active automatic reply elements for a given job event or initiator. If a
Zeke job event is running, Zeke displays the messages and replies that are active for that
job event.
Syntax
ZDisplay
REPly
JOBname name
INITiator init-ID
Parameters
Parameter
Description
JOBname
Specifies the job event the messages and auto replies are to be
displayed for.
ZD JOB TESTXYZ REPLY
Display replies for the job event TESTXYZ.

INITIATOR
Displays the active automatic reply elements for a given initiator.

If a Zeke job event is running in the selected initiator, Zeke displays
the messages and replies that are active for that job event.
For example:
ZD REPLY INIT T3
Display replies for initiator T3. Issue this command while the job
is running and waiting for a reply.
REPly
Displays the messages and replies for an active job event.
183
Displaying System Pool Information

You can display the system IDs contained in the specified pool (message Z0974I).
Syntax
ZDisplay
POOLid pool-ID
Parameter
Use the following parameter of the ZDISPLAY command to display this information.
Parameter
Description
POOLid
Specifies the pool ID to be displayed.

ZD POOL POOL1
Display the system IDs contained in pool POOL1.
Displaying Zeke Agents Identifying Information

You can display the list of Zeke Agents for schedule download (message
Z09D1I/Z09D2I/Z09D3I). The output includes message ID for the heading, the
NETREGID, the download status, the description for each Zeke Agent, and whether the
Zeke Agent has been deleted.
Syntax
ZDisplay
DOWnload
Parameter
184
Parameter
Description
DOWnload
Displays information about schedule download agents and their

processing status.
4 Operator Commands
Displaying Remote Prerequisites

You can display information about the remote prerequisites sent to Zeke from another
system (message Z09AQI/Z09ARI). The output includes the trigger type, jobname, and
originating NETREGID for each remote prerequisite.
Syntax
ZDisplay
REMDepn
Parameter
Parameter
Description
REMDepn
Displays information about remote prerequisites.
Displaying Communication Records Information

You can display the system IDs that Zeke thinks are currently active against this database
(message Z0985I/Z0986I).
Syntax
ZDisplay
COM
Parameter
Parameter
Description
COM
Displays the system IDs currently active against this database.
185
If the Multsys generation option is set to N and there is only one Zeke active on the
database, the following message is displayed in response to the ZD COM command:
Z0988I
ZEKE MULTI SYSTEM COMMUNICATION IS NOT ACTIVE
Note:
An invalid or inactive system ID registration can be removed by using the batch

CPUDEL option.
Displaying Database Information

You can display both vault and primary database information (message Z09AKI).
Syntax
ZDisplay
CATALOG
Parameter
Parameter
Description
CATALOG
Displays vault/primary database information.
Displaying Tracing Messages

You can activate tracing messages on the console and activates security calls at various
points in ZEKE15A. ASG Service Desk personnel might ask you to activate these
messages to assist in debugging a Zeke problem.
186
4 Operator Commands
Syntax
ZDisplay
DATAname
JCLExit
JCLWto
SChd
SEC
TRACE
UCBScan
ALL
ENd
Error
OFf
ALL
ENd
OFf
ALL
ENd
OFf
ALL
ENd
Error
NOCOMm
OFf
ALL
ON
OFf
ALL
ON
OFf
ALL
ON
OFf
Parameters
Parameter
DATAname
Description
Controls tracing of calls to ZEKE04A, the Zeke VARIABLE

monitor.
Must be followed by one of the following subparameters:
ALl
Traces ALL calls.
ENd
Turns tracing off.
ERRor
Traces only those calls that result in a non-zero return

code.
ZD DATANAME ERROR
Traces only calls to ZEKE04A that result in a

non-zero return code.
OFf
JCLExit
Turns tracing off.
Traces all calls to the Zeke JCL exits.
187
Parameter
SChd
Description
Controls tracing of calls to ZEKE03A, the Zeke SCHEDULE

monitor. Also controls tracing of calls to the dispatch monitor
and /COMM tasks.
Must be followed by one of the following subparameters:
ALl
Traces ALL calls.
ENd
Turns tracing off.
ERRor
Traces only those calls that result in a non-zero return

code.
OFf
Turns tracing off.

ZD SCHD ALL
Traces all calls to ZEKE03A.

ZD SCHD END
Turns ZEKE03A tracing off.

SECurity
Controls tracing of security calls to ZEKE15A, Zekes internal

security module. For information about how to control tracing
for external security, see the documentation on the SET
ESITRACE command in the ASG-OASIS OS/390 Reference
Guide.
Must be followed by either the ON or OFF subparameter. The
ALL parameter is optional.
TRACE DOWNload
188
ALL
Displays all trace messages. This subparameter can

display up to 11 lines of messages at each trace point,
so only use this parameter when necessary.
ON
Turns tracing on and displays the first 2 lines of

messages.
OFF
Turns tracing off.
Controls tracing of schedule download messages. Must be

followed by either the ON or OFF subparameter.
ON
Turns tracing on and displays the first 2 lines of

messages.
OFF
Turns tracing off.
4 Operator Commands
PathFinderDisplaying Preceding and Succeeding Events

You can display the chain of events or hierarchy of events that are dependent on other
events, as specified in the WHEN condition of the event master record for dependent
events. See "Display Format SUCCESSOR and/or PREDECESSORFormat 8" on
page 204 for a description of the format and headings.
Syntax
ZDisplay
PREdecessor
SUccessor
JOb jobname
EVent number
DAte yyyyddd
LEVel number
VERsion number
Parameters
Parameter
Description
PREdecessor Displays the events that the specified event is dependent on.
ZD PRE JO JOB1
Display all events that JOB1 is dependent upon.

If you specify an event and there are multiple versions of the event in
the current schedule, you must use the VER parameter to specify a
particular version.
SUccessor
Displays the events that are dependent on the specified event.

ZD SU EV 26
Display all events that are dependent upon Event 26.

EVent
Displays the events that are dependent on or are a dependency for the
specified event number.
JOb
Displays the events that are dependent on or are a dependency for the
specified jobname.
189
Parameter
Description
DAte
Displays events with the specified schedule date (YYYYDDD or

YYDDD).
ZD PRE EV 27 DA 2001001
Display all events that event 27 for January 1, 2001 is dependent

upon.
By issuing the ZDISPLAY command with a date value of 99999, you
can display an event with the schedule date of the earliest event in the
schedule that is dependent on the event being displayed.
ZD SU EV 234 DATE 99999
Displays the event with the earliest schedule date that has not
been dispatched because it is waiting on event 234.
Note:
When using the YYDDD format, if YY is greater than or equal to

50, then the date is considered a 20th century date (19xx); if it is less
than 50, it is considered a 21st century date (20xx).
LEVel
Displays the specified number of levels in a particular hierarchy of

events. The default level is 1, which displays those events
immediately dependent on the specified event. Enter a number
between 1 and 999 or an (*) asterisk to display all levels.
ZD SU EV 100 LEV 3
Display up to 3 levels of events that are dependent upon Event

100.
VERsion
To specify an event when there are multiple versions of that event in

the current schedule, use this parameter to specify a particular
version.
You can display both predecessor and successor events by specifying both, as in the
following example:
ZD PRE SUC JOB PAYROLL1
Display all jobs that PAYROLL1 is dependent upon and all jobs dependent upon
PAYROLL1.
190
4 Operator Commands
ZDISPLAY Formats
There are several display formats. The format type is determined by the parameters
entered with the ZDISPLAY command. Display Format 1 (see "Main Display Format
Format 1a" on page 192) is used unless one of the following parameters is entered.
Display Type
Format Type
JOB
"Display JOBFormat 2" on page 195
(with no other
type specified)
WAIT
"Display WAITFormat 3" on page 196
INFO
"Display Format INFOFormat 4" on page 199
DONE
"Display Format DONE Format 5" on page 200
DONE JOB
"Display Format DONE and JOBFormat 6" on page 202
AVAILABLE
"Display Format for AVAILABLEFormat 7" on page 203
PRED/SUCC
"Display Format SUCCESSOR and/or PREDECESSOR

Format 8" on page 204
HOLD
"Display Format HOLDFormat 9" on page 205
DLSTATUS
"Display Format for DLSTATUS" on page 208
DOWNLOAD
"Display Format for DOWNLOAD" on page 207
Each display format has column headings, which are described with each display format
sample. Events are displayed in sequence starting with the earliest schedule time. An
asterisk (*) to the right of the event number indicates that the schedule entry is in the
dispatch queue, ready for dispatching. An asterisk (*) to the left of a jobname, program, or
variable indicates that the WHEN condition is satisfied. The following symbols are
displayed down the far right column of each screen.
Symbol
Meaning
blank
Event is neither WHEN nor time-satisfied.
Event is WHEN and time-satisfied and ready for dispatching.
Event is in the dispatch queue and is waiting for a free initiator.
Event has no WHEN condition, but is not time-satisfied.

191
Symbol
Meaning
WHEN conditions for the event are satisfied, but the event is waiting to be
time-satisfied.
Event is time-satisfied, but is waiting for WHEN conditions to be satisfied.

Use the ZDISPLAY WHEN command to display the WHEN conditions of the
event.
This symbol appears to the left of a weak WHEN condition. This indicates the
WHEN condition is satisfied because the dependency is not in the schedule.
Main Display FormatFormat 1a

The following screen, Display Format 1a, is used if JOB, WAIT, or INFO parameters are
not entered.
Z0922I DATE
000003 2000325
000003 2000325
000003 2000325
000010 2000329
000014 2000329
000003 2000328
000010 2000329
000003 2000332
000004*2000332
RDATE
2000325
2000325
2000325
2000329
2000329
2000328
2000329
2000332
2000332
VERS
0001
0003
0004
0001
0001
0001
0002
0001
0001
TYPE
JOB
JOB
JOB
JOB
JOB
JOB
JOB
JOB
JOB
JOB/EVT NAME
EANTST03
EANTST03
EANTST03
CER6K1
CERJ14
EANTST03
CER6K1
EANTST03
EANTST04
DP
50
50
50
50
50
50
50
50
50
SCHED FREQ CNT

STATUS
00:00
1 * SUCC 15:46
00:00
1 * SUCC 14:06
00:00
1 * SUCC 14:09
00:00
1 * SUCC 16:12
00:00
1 * HOLD
00:00 00:01 123 T
00:00
1 * PEND 16:17
00:00
1 T
00:00
1 *
The following describes the column headings.

Heading
Description
Z0922I
Message ID for the column heading. This column displays the event
numbers.
DATE
Date (Julian) the event was added to the schedule.
RDATE
Run date.
VERS
Version of the event.
TYPE
Event type.
JOB/EVT NAME Jobname, if a job event, otherwise, the event name.
192
DP
Dispatch priority.
SCHED
Normal dispatch time.
4 Operator Commands
Heading
Description
FREQ
For recurring events, the amount of time between dispatches.
CNT
Number of times the event is scheduled.
STATUS
Column to the right of CNT displays the symbol indicating the

current status, and if the job is complete, the time it completed.
{unlabeled}
Symbol
Meaning
blank
Event is neither WHEN nor time-satisfied.
Event is WHEN and time-satisfied and ready for

dispatching.
Event is in the dispatch queue and is waiting for a free

initiator.
Event has no WHEN condition, but is not

time-satisfied.
WHEN conditions for the event are satisfied, but the

event is waiting to be time-satisfied.
Event is time-satisfied, but is waiting for WHEN

conditions to be satisfied. Use the ZDISPLAY WHEN
command to display the WHEN conditions of the
event.
This symbol appears to the left of a weak WHEN

condition. This indicates the WHEN condition is
satisfied because the dependency is not in the schedule.
The last column indicates whether the job was executed at a remote
location and lists the name of the remote location as it appears in the
Target field on the EMR screen.
193
Display Format for DESCFormat 1b

The following screen is used if the DESC parameter is entered. The screen format is the
same as the main display format except there is an additional line of information. The
event description is displayed for each event.
Z0922I DATE
RDATE
VERS TYPE
000003 2000325 2000325 0001 JOB
DESC: TEST EVENT
000003 2000325 2000325 0003 JOB
DESC: TEST EVENT 2
000003 2000325 2000325 0004 JOB
DESC: TEST EVENT 3
000010 2000329 2000329 0001 JOB
DESC: REMOTE JOB - UNIX
000014 2000329 2000329 0001 JOB
DESC: REMOTE JOB - NT
000003 2000328 2000328 0001 JOB
DESC: TEST EVENT 4
000010 2000329 2000329 0002 JOB
DESC: ROUTED TO UNIX BOX 6K1
JOB/EVT NAME DP SCHED FREQ

EANTST03
50 00:00
CNT
STATUS
1 * SUCC 15:46
EANTST03
50 00:00
1 * SUCC 14:06
EANTST03
50 00:00
1 * SUCC 14:09
CER6K1
50 00:00
1 * SUCC 16:12
CERJ14
50 00:00
1 * HOLD
EANTST03
50 00:00 00:01 123 T
CER6K1
50 00:00
1 * PEND 16:17
Display NOTEFormat 1c
The following screen is used if the NOTE parameter is entered. The screen format is the
same as the main display format except the existing Note Documentation is displayed for
each event.
Z0922I DATE
RDATE
VERS TYPE JOB/EVT NAME DP SCHED FREQ CNT
000014 2000329 2000329 0001 JOB CERJ14
50 00:00
1
000003 2000328 2000328 0001 JOB EANTST03
50 00:00 00:01 123
NOTE: FROM THE DOCUMENTATION OPTION, YOU CAN DISPLAY EXISTING
DOCUMENTATION FOR AN EVENT.
YOU CAN MAINTAIN SCRATCH PAD, NOTE, TEXT, OR DATASET
DOCUMENTATION IF DOCUMENTATION ALREADY EXISTS FOR THIS
EVENT.
000004*2000332 2000332 0001 JOB EANTST04
50 00:00
1
000013 2000332 2000332 0001 JOB TESTJOB1
50 00:00
1
NOTE: THIS IS A NOTE FOR EVENT NUMBER ONE.
THIS NOTE CAN BE UP TO
SIX LINES IN LENGTH.
FREE-FORM INFORMATION
CAN BE KEYED IN DESCRIBING
JOB REQUIREMENTS.
000009 2000332 2000332 0001 JOB CERJ9
50 00:00
1
NOTE: EVENT 8 REQUIRES
THE PAYROLL EDIT
TO BE IN BALANCE.
000014 2000332 2000332 0001 JOB CERJ14
50 00:00
1
194
*
T
STATUS
HOLD
*
*
HOLD NET
HOLD NET
4 Operator Commands
Display WHENDETAILFormat 1d
The following screen is used if the WHENDETAIL parameter is entered. The screen
format is the same as the main display format except for the addition of the version of the
WHEN clause that was used for the scheduled event.
Z0922I DATE
RDATE VERS TYPE JOB/EVT NAME DP SCHED FREQ CNT
STATUS
000014 2000329 2000329 0001 JOB CERJ14
50 00:00
1 * HOLD
0 WHEN: (*EOJ CERJ3 AT ZTEAM6K1)
000003 2000328 2000328 0001 JOB EANTST03
50 00:00 00:01 123 T
0 WHEN: (EOJ JOBA AT A)
000003 2000332 2000332 0001 JOB EANTST03
50 00:00
1 T
000008 2000332 2000332 0001 JOB EANTST08
50 00:00
1 T
1 WHEN: (EOJ EANTST04)
000014 2000332 2000332 0001 JOB CERJ14
50 00:00
1 T
0 WHEN: (EOJ CERJ3 AT ZTEAM6K1)
000015 2000332 2000332 0001 JOB CERJ15
50 00:00
1 T
0 WHEN: (EOJ TESTJOB1 AT ZTEM6K1)
Display XREFFormat 1e
The following screen is used if the XREF parameter is entered.
Z0922I DATE
RDATE
VERS TYPE JOB/EVT NAME
000003 2000328 2000328 0001 JOB EANTST03
000003 2000332 2000332 0002 JOB EANTST03
000034 2000336 2000336 0001 JOB KAMTST03
0 WHEN: (EOJ JOBA AT A AND WEOJ JOBB)
DP SCHED FREQ CNT

50 00:00 00:01 123 T
50 00:00
1 T
50 00:00
1 T
STATUS
Display JOBFormat 2
The following screen is used if the JOB parameter is entered.
Z0923I DATE
000014 2000329
000003 2000328
000003 2000332
000004*2000332
000013 2000332
000008 2000332
000009 2000332
000014 2000332
000015 2000332
000013 2000332
VERS
0001
0001
0001
0001
0001
0001
0001
0001
0001
0002
JOB NAME
CERJ14
EANTST03
EANTST03
EANTST04
TESTJOB1
EANTST08
CERJ9
CERJ14
CERJ15
TESTJOB1
SCHED CLASS
00:00
00:00
00:00
00:00
00:00
00:00
00:00
00:00
00:00
00:00
DP TPS VMEM STATUS

JOBID
TARGET
50
JOB05119
50
50
50
50
HOLD NET
TOBIE
50
50
HOLD NET
ZTEAMH
50
50
50
HOLD NET
TOBIE

Heading
Description
Z0923I
numbers.
195
Heading
Description
DATE
Julian date of the schedule record.
VERS
JOB NAME Jobname, if a job event, otherwise, the event name.

SCHED
CLASS
Class or class list the event is authorized to run under.
DPR
Dispatching priority code.
TPS
Number of tape drives required.
VMEM
Minimum amount of virtual memory.
STATUS
Event status, such as HOLD, PEND, ACT, etc.
JOBID
JES job ID.
TARGET
NETREGID of the remote system the JCL will execute on (if applicable).
If the job was submitted to run locally, this field is blank.
Display WAITFormat 3
The following screen is used if the WAIT parameter is entered.
Z0924I DATE
000014 2000329
000004*2000332
000013 2000332
000009 2000332
000013 2000332
196
VERS
0001
0001
0001
0001
0002
TYPE
JOB
JOB
JOB
JOB
JOB
JOB NAME
CERJ14
EANTST04
TESTJOB1
CERJ9
TESTJOB1
SCHED CLASS DPRI TPS R REASON

00:00
50
NO DQ ENTRY
00:00
1
N NEED OPER OK
00:00
50
NEED RESOURCES
00:00
50
N TAPE DRIVES REQ
00:00
2
N AWAITING RETRY
STAT
HOLD
HOLD
HOLD
HOLD
HOLD
4 Operator Commands

Heading
Description
Z0924I
numbers.
DATE
VERS
TYPE
Event type.
JOB NAME Jobname, if a job event, otherwise, the event name.

SCHED
CLASS
DPRI
TPS
Number of tape drives required.
An N indicates the job was submitted with remote system specified as

the target. If blank, the job was submitted to run locally.
REASON
Reason the event is waiting to execute:

Awaiting Retry
The event attempted dispatch but failed with a

recoverable error. It will attempt to dispatch again.
Delay Dispatch
Zeke is delaying the event dispatch due to

multi-CPU processing requirements.
Dispatch JCL Error Zeke encountered an error reading the JCL while
attempting to dispatch the event. The event was
placed on hold.
DSN Trigger Hold
There are multiple SQRs in the schedule with the

same DSN trigger specified. The Dsntrig generation
option is set to NT, so Zeke did not trigger any of the
events, and the events were placed on hold.
Dspl=No, Pool Evt

on VSE
Zeke attempted to dispatch a pool event on a VSE

system with Dispsel set to N. The event was placed
on hold.
Event was
ZREFRESHed
A ZREFRESH command was issued for this event;

the event was refreshed and placed on operator
hold.
197
Heading
Description
Internal Error Hold
The event was placed on hold due to an internal

error in Zeke processing.
Need Initiator
The event is waiting for an available initiator.
Need Operok
The event requires an operator OK (ZOK

command) prior to dispatch.
Need Resources
The event is waiting for resources. Issue the

ZRESOURCE command to display the resources.
Network Error Hold The event was placed on hold due to a networking
error.
198
New DQT-entry
The event has been placed in the dispatch queue but

the dispatcher has not attempted to dispatch the
event. The event will be dispatched during the next
dispatch process.
No Com-entry
The event is both time-satisfied and

WHEN-satisfied, but is in a held status of some
kind.
No Disp-com
The event is currently being processed by

multi-CPU processing. The event will be available
for dispatching after the communication record is
processed.
No Disp-load
There is a new schedule record entry added by the

schedule load that is currently processing. The entry
will be available for dispatching when the schedule
load is complete.
Notdur Pgm/Job
The event is waiting for the completion of a

program or job that is specified in the event's
WHEN clause. If a short-term condition still exists
after one minute, there may be a problem with the
dispatch.
Operator Hold
(ZHOLD)
The event was placed on operator hold because a

ZHOLD command was issued for the event.
4 Operator Commands
Heading
STAT
Description
Posid=N,
Cntrl=Y,
Remote Job
The POSID generation option is set to No and the

Control field on the EMR is set to Yes. With these
settings, Zeke has no way to track a remote job, so
the event was placed on hold. In order for Zeke to
track a remote job, POSID must be set to Yes.
Otherwise, Control must be set to No so that Zeke
will not attempt to track the remote job.
Security Violation
The job does not have the authority to run on the

platform it was sent to. The event was placed on
hold.
System on Hold
The Zeke dispatching system is on hold. Issue the

ZRELEASE command with the system parameter.
Tape Drives Req
The required number of tape drives are not

available.
The status of the event, such as HOLD, PEND, or ACT.
Display Format INFOFormat 4

The following screen is used if the INFO parameter is entered.
Z0926I DATE
000014 2000329
000003 2000328
000003 2000332
000004*2000332
000013 2000332
000008 2000332
000009 2000332
000014 2000332
000015 2000332
000013 2000332
VERS
0001
0001
0003
0001
0001
0001
0001
0001
0001
0002
SCHED
00:00
00:00
00:00
00:00
00:00
00:00
00:00
00:00
00:00
00:00
TYPE
JOB
JOB
JOB
JOB
JOB
JOB
JOB
JOB
JOB
JOB
JOB/EVT-NAME
DEP FROM 6K1
EANTST03
EANTST03
EANTST04
TO-TOBIE-NT
EANT
TO-ZCAL HP
DEP FROM 6K1
CERTST
TO-TOBIE-NT
APPL
CER
EAN
EAN
EAN
CER
EAN
CER
CER
CER
CER
GRP
CER
EAN
EAN
EAN
CER
EAN
CER
CER
CER
CER
USERID
*
T
T
*
carlr
*
EAN
T
richards *
T
T
carlr
*
HOLD
HOLD NET
HOLD NET
HOLD NET

Heading
Description
Z0926I
Message ID for the column heading. This column displays the

event numbers.
DATE
VERS
SCHED

199
Heading
Description
TYPE
Event type.
JOB/EVT-NAME
Jobname, if a job event, otherwise, the event name.
APPL
Application ID.
GRP
Group ID.
USERID
User ID.
{unlabeled}
Event status, such as HOLD, PEND, ACT, etc.
{unlabeled}
An N indicates the job was submitted with remote system

specified as the target. If blank, the job was submitted to run
locally.
Display Format DONE Format 5

The following screen is used if the DONE parameter is entered.
Z0969I
000003
000003
000003
000010
000010
000006
000013
000009
000010
000013
DATE
2000325
2000325
2000325
2000329
2000329
2000332
2000332
2000332
2000332
2000332
VERS
0001
0003
0004
0001
0002
0001
0001
0001
0001
0002
TYPE
JOB
JOB
JOB
JOB
JOB
JOB
JOB
JOB
JOB
JOB
JOB/EVT NAME
EANTST03
EANTST03
EANTST03
CER6K1
CER6K1
CERJ6
TESTJOB1
CERJ9
CER6K1
TESTJOB1
CCODE
C0000
FLUSH
C0000
C0000
SCHED FREQ
00:00
00:00
00:00
00:00
00:00
C0000 00:00
00:00
00:00
C0000 00:00
00:00
CNT
1 *
1 *
1 *
1 *
1 *
1 *
1 *
1 *
1 *
1 *
STATUS
SUCC 15:46
FAIL 14:06
SUCC 14:09
SUCC 16:12
PEND 16:17
SUCC 00:07
HOLD NET
HOLD NET
SUCC 00:09
HOLD NET
R
R
R
R
R
R

Heading
Description
Z0969I
numbers.
DATE
VERS
TYPE
Event type.

CCODE
200
Abend or condition code.
4 Operator Commands
Heading
Description
SCHED
FREQ
CNT
STATUS
Completion status and time.
F/OK
The event had abended, been refreshed, and finished

successfully.
ACTV
The event is currently running.
FAIL
The event ended abnormally.
SUCC
The event has completed successfully.
FBOK
The abended event has been forced to EOJ.
F/S
The event has been forced to Forced Succes status.
PEND
The event has been dispatched and is awaiting execution

or, if executing, the jobname on the DOS job card does not
match the jobname shown on the Job field on the Event
Master Record Functions screen.
An N indicates the job was submitted with remote system

specified as the target. If blank, the job was submitted to run locally.
201
Display Format DONE and JOBFormat 6

The following screen is used if the DONE and JOB parameters are entered.
Z0970I
000003
000003
000003
000010
000010
000006
000013
000009
000010
000013
DATE
2000325
2000325
2000325
2000329
2000329
2000332
2000332
2000332
2000332
2000332
VERS
0001
0003
0004
0001
0002
0001
0001
0001
0001
0002
JOB NAME
EANTST03
EANTST03
EANTST03
CER6K1
CER6K1
CERJ6
TESTJOB1
CERJ9
CER6K1
TESTJOB1
SCHED CLASS DPRI

00:00
50
00:00
50
00:00
50
00:00
50
00:00
50
00:00
50
00:00
50
00:00
50
00:00
50
00:00
50
CCODE
C0000
S806
C0000
C0003
FLUSH
C0000
C0000
C0000
C0004
C0000
15:46
14:06
14:09
16:12
16:17
00:07
16:17
16:18
00:09
16:19
R JOBID
JOB03708
JOB03667
JOB03668
JOB04499
202
Heading
Description
Z0970I
numbers.
DATE
VERS
JOB NAME
Jobname.
SCHED
CLASS
DPRI
CCODE
Abend or condition code.
{untitled}
The column to the right of CCODE displays the status time.
An N indicates the job was submitted with remote system specified as

the target. If blank, the job was submitted to run locally.
JOBID
JES job ID (if the job has gone ACTV on the system).
4 Operator Commands
Display Format for AVAILABLEFormat 7

The following screen is used if the AVAILABLE parameter is entered.
Z0930I ID CLASSES
-BUSY- A A
-IDLE- B BA
-IDLE- C CBA
-IDLE- D DCBA
-IDLE- 2 I
-IDLE- 10 W
DRAIN
E EDCBA
DRAIN
F F
DRAIN
G G
UNDEF
1
UNDEF
3
START/STOP TIME RANGES FOR Saturday

00:00-24:00 09:30-24:00
00:00-24:00
00:00-24:00
00:00-24:00
00:00-24:00
00:00-24:00
00:00-24:00
00:00-24:00
00:00-24:00
00:00-24:00
00:00-24:00

Heading
Description
Z0930I
Message ID for the column heading. This column displays the

initiator status.
ID
Initiator ID.
CLASSES
Classes the initiator can run.
START/STOP
Starting and ending times the initiator is available to Zeke. There

are up to four ranges.
TIME RANGES
Another set of times the initiator is available to Zeke.
FOR SATURDAY Status for the requested day of the week.
203
Display Format SUCCESSOR and/or PREDECESSORFormat 8

The following screen is displayed when the SUCCESSOR and/or PREDECESSOR
parameters are entered.
ZnnnnI PREDECESSORS &
LVL JOB/EVT NAME TYPE
2 VCOM#Y4
VCOM
2 ZCOM#Y3
ZCOM
>>1 JOBX2
JOB
SUCCESSORS FOR THE REQUESTED EVENT:

EVENT
DATE
VERS WHEN TRIGGER NAME T-VER STATUS AVDUR
000001 2002214 0002
PEND
000002 2002214 0001
ACT
000003 2002214 0001 EOE VCOM#Y4
T
00:25
WEOE ZCOM#Y3
2 JOBY2
*** NOT IN THE SCHEDULE
REMOTE EVENT ***
2 WORK#Y1
WORK 000005 2002214 0001
SUCC
>>1 JOBX1
JOB 000006 2002214 0001 EOJ JOBY2
T
00:20
WEOE WORK#Y1
--------------------------------------------------------------------------EOJ JOBX1
-------------------------------------------------------------------------->>1 JOBB1
JOB 000008 2002214 0001 EOJ JOBA
T
HOLD
00:15
2 JOBC2
JOB 000010 2002214 0004 WEOJ JOBB1
T
00:00
>>1 JOBB2
JOB 000011 2002214 0001 EOJ JOBA
T
00:35
2 ZCOM#C3
ZCOM 000012 2002214 0001 WEOE JOB#B2
T
2 VCOM#C4
VCOM 000013 2002214 0003 EOE JOB#B2
T
The following describes the column headings:

Heading
Description
LVL
Indicates the level of hierarchy of the job flow:

0
Original event or job as specified in the ZDISPLAY

command.
Predecessor or successor of the specified event or job.
Predecessor or successor of a level 1 predecessor or

successor.
JOB/EVT NAME
Jobname, if a job event, otherwise, the event name.
TYPE
Event type.
EVENT
Event number.
DATE
VERS
WHEN
Type of WHEN condition.
TRIGGER NAME Jobname or event that triggers the WHEN condition for the
jobname or event listed.
204
4 Operator Commands
Heading
Description
T-VER
Triggering version of the event.
STATUS
Event status, such as HOLD, PEND, ACTIVE, etc.
AVDUR
Average duration time for a job or event.
{unlabeled}
If two or more events have the same name and one of the events
triggers another, then both events with the same name will appear
with the word DUP beside each one in the right margin of the
screen.
Display Format HOLDFormat 9

The following screen is displayed when the HOLD parameter is entered.
Z0922I
000014
000013
000009
000013
DATE
2000329
2000332
2000332
2000332
RDATE
2000329
2000332
2000332
2000332
VERS
0001
0001
0001
0002
TYPE
JOB
JOB
JOB
JOB
JOB/EVT NAME
CERJ14
TESTJOB1
CERJ9
TESTJOB1
DP
50
50
50
50
SCHED FREQ
00:00
00:00
00:00
00:00
CNT
1
1
1
1
*
*
*
*
STATUS
HOLD
HOLD NET
HOLD NET
HOLD NET

Heading
Description
Z0922I
numbers.
DATE
RDATE
Run date.
VERS
TYPE
Event type.

DP
Dispatching priority.
SCHED
FREQ
CNT
STATUS
The last column displays the HOLD status and reason codes. The
statuses are:
205
Heading
{unlabeled}
206
Description
DNPL
Zeke attempted to dispatch a pool event on a VSE

system with Dispsel=NO. The event was placed on
hold.
DSNT
There are multiple SQRs in the schedule with the same

DSN trigger specified.The Dsntrig generation option is
set to NT, so Zeke did not trigger any of the events, and
the events were placed on hold.
INTR
Event was placed on hold due to an internal error in

Zeke processing.
NET
Event was placed on hold due to a networking error.
OPER
Event was placed on hold because a ZHOLD command

was issued for the event.
PSID
Posid generation option is set to No and the Control field

on the EMR is set to Yes. With these settings, Zeke has
no way to track a remote job, so the event was placed on
hold. In order for Zeke to track a remote job, Posid must
be set to Yes. Otherwise, Control must be set to No so
that Zeke will not attempt to track the remote job.
REXX
OASIS ECF error. OASIS encountered an error

dispatching the REXX exec for a REXX event. OASIS
should display an error message on the system console.
RFSH
A ZREFRESH command was issued for this event. The

event was refreshed and placed on operator hold.
SEC
Job does not have the authority to run on the platform it

was sent to. The event was placed on hold.
SJCL
Zeke encountered an error reading the JCL while

attempting to dispatch the event. The event was placed
on hold.
The NETREGID of the execution system (the TARGET value).
4 Operator Commands
Display Format for DOWNLOAD

The following screen is displayed when the DOWNLOAD parameter is entered.
ASG-Zeke
Command ===>
Zeke Command Output Display
BROWSE
Row 1 of 6
Scroll ==> PAGE
Please enter a valid Zeke operator command or option number.

Press PF3/PF15 key to return to the schedule control function panel.
------------------------------------------------------------------------------Z09D1I NETREGID STATUS SCHEDULE#
DESCRIPTION
Z09D2I NTAGENT
NTSYNC 00:00
ZEKE AGENT NT
Z09D2I OS400AGT NTSYNC 00:00
ZEKE AGENT OS400
Z09D2I UNIXAGNT NTSYNC 00:00
ZEKE AGENT UNIX
Z09D2I VMSAGENT NTSYNC 00:00
ZEKE AGENT VMS
Z09D3I 00004 SCHEDULE DOWNLOAD AGENTS
******************************* Bottom of data ********************************

Heading
Description
Z09D1I
Message ID for the column heading.
NETREGID
Zeke Agent NETREGID
STATUS
Status of the Zeke Agent.

UNKNWN
Zeke Agent status has not been sent to Zeke.
NTSYNC
Zeke Agent is not synchronized with Zeke.
IDLE
Zeke Agent is waiting for work.
DLDING
Schedule record data is being downloaded to the

Zeke Agent.
WAIT
Zeke has downloaded a schedule or job to the Zeke

Agent and is waiting for a response.
OOSYNC
Zeke Agent and Zeke are out of synchronization.
INACT
Zeke is not active.
UNSUPP
This Zeke Agent does not support schedule

download.
DESCRIPTION
Optional user-defined descriptive text.
(deleted)
This Zeke Agent has been removed from the download agent table
in the Zeke database, but might still have work in progress.
207
Display Format for DLSTATUS

The following screen is displayed when the DLSTATUS parameter is entered.
Z09D5I DATE
VERSN TYPE
000001 2001212 00000 JOB
DESC: JOB1
000002 2001212 00000 JOB
DESC: JOB2
000003 2001212 00000 JOB
DESC: JOB3
Z0905I NUMBER OF SCHEDULE
EVENT NAME
TESTJOB1
TARGET
NTAGENT
STATUS
NOTSNT
TESTJOB2
NTAGENT
NOTSNT
TESTJOB3
NTAGENT
NOTSNT
ENTRIES SELECTED WAS 00003 SYSTEM MBCX240A
208
Heading
Description
Z09D5I
Message ID for the column heading.
DATE
VERSN
Version number of the job event.
TYPE
Event type. Only job events can be downloaded to Zeke Agent, so

JOB should always be displayed as the type.
EVENT NAME
Event name.
TARGET
NETREGID of the remote system downloading the job event.
STATUS
Download status of the job event.

NOTSNT
Event has not yet been downloaded to Zeke Agent.
NOSUPP
This Zeke Agent does not support schedule

download.
ERROR
An internal error occurred during schedule

download to target.
SENT
Job event has been successfully downloaded to

Zeke Agent.
PENDING
An update to the downloaded schedule record is

pending.
STALEZ
Event status is mismatched between Zeke and Zeke

Agent. The Zeke status is out-of-date.
STALEA
Event status is mismatched between Zeke and Zeke

Agent. The Zeke Agent status is out-of-date.
4 Operator Commands
Heading
Description
??xx??
Unknown status. Contact the ASG Service Desk for

assistance.
ZENABLE Command
The ZENABLE command reactivates or enables one or more events that were previously
disabled using the ZDISABLE command. Can also reactivate the automatic reply
elements for an event for which automatic replies were disabled.
A disabled event that was scheduled for a prior day will most likely have been dropped by
the current day's first schedule update.
Refer to your ASG-Zeke OS/390 Users Guide for information on enabling auto replies.
Syntax
ZENable
global
NOMSG
REPly
EVent num
INITiator init-ID
JOBname name
Parameters
Use any of the Global Event Selection Parameters (starting on page 143) to select events
to be enabled. The following parameters can also be used with the ZENABLE command.
Parameter
Description
EVent
Event number for which auto replies are to be enabled. This command
only has effect if the ZDISABLE command was previously used to
disable auto replies for the event.
ZENA EV 55 REP
Enable previously disabled auto-replies for event 55.

JOBname
Jobname for which auto replies are to be enabled.

ZEN JOB TS010000
Enable previously disabled job event TS010000.
209
Parameter
Description
NOMSG
REPLY
Enables the auto reply for the specified event.
ZHOLD Command
The ZHOLD command performs the following functions:
Places an operator hold on one or more events
Places an operator hold on an initiator
Prevents Zeke from dispatching any events (called a SYSTEM HOLD)
An operator hold on an event prevents Zeke from dispatching the event. The event can be
in either the schedule queue or the dispatch queue when the hold is placed on it.
If the event is in the schedule queue, it still follows the normal progression into the
dispatch queue when the time and prerequisite requirements are satisfied, but is not
dispatched. A ZD HOLD will display all events on hold. A ZD HOLD=reason will display
events that are held with the specified hold reason. A hold is released with the ZRELEASE
command.
An operator hold on an initiator prevents Zeke from dispatching any jobs to that initiator.
It does not prevent jobs from running in that initiator if they are submitted by any source
other than Zeke. Only an initiator defined to the GENSYS option can be held.
A system hold prevents Zeke from dispatching any events of any type. Zeke continues to
perform its monitoring duties while on hold, and events still move from the schedule queue
to the dispatch queue as their time and prerequisites are satisfied, but no events are
dispatched while a system hold is in effect. A system hold is removed with the
ZRELEASE command. The system hold remains in effect until it is released, or until Zeke
is terminated.
Note:
It is possible to interrupt a system hold to run some jobs, without releasing the system
hold. To do so, place a hold on all events, and then release the existing system hold.
Release the events that you want to run. When you are ready to run everything normally,
release the hold on all events.
210
4 Operator Commands
Syntax
ZHold
global
INitiator init-name
SYstem
NOMSG
Parameters
To place a hold on one or more events, enter one or more Global Event Selection
Parameters (starting on page 143) to select the events. An event hold remains in effect
until it is specifically released, regardless of any system IPLs.
Examples
The following are some examples of using the Global Event Selection parameters with
the ZHOLD command:
ZH EV 45
Place operator hold on event 45.
ZH JOB *PR
Place operator hold on any job event having a jobname beginning with PR.
ZH ALL
Place operator hold on each event in the schedule queue.
ZH JOB *
Place operator hold on all job events
ZH GRO PAY ALL
Place operator hold on all events with the group name PAY.
ZH AP JOB ALL
Place an operator hold on all events with the application name JOB. To place a hold
on an initiator, use the INITIATOR parameter to name the initiator. This keyword
indicates the hold is an initiator hold and not an event hold or a system hold. In this
case, all other hold parameters are ignored.
To place a system hold on Zeke, use the parameter SYSTEM. In this case, any event
selection parameters are ignored.
To verify whether there is a system hold in effect, enter ZHOLD SYSTEM. If there is
already a system hold, the command is rejected. If not, the command is accepted and an
appropriate message is displayed.
A system hold or an initiator hold remains in effect until a ZRELEASE SYSTEM
command is issued, until the system is IPL'd, or until Zeke is cycled.
211
Parameters
The following parameters can also be used with the ZHOLD command:
Parameter
Description
NOMSG
INitiator Places a hold on the specified initiator.

ZH IN A
Place operator hold on initiator A.

ZH IN 10
Place operator hold on initiator 10.

SYstem
Suspends event dispatching. No event is dispatched while a system hold

is in effect.
ZHOLD SYS
Place a hold on the entire system from which the command is issued.
The ZHOLD SYSTEM command must be issued from the system being
placed on hold it cannot be used to place another system on hold.
Therefore, if you issue the ZHOLD SYSTEM command with a system
ID, the system ID is ignored and the system it was issued from is put on
hold. For example, issuing the command ZH SYS CPUA from CPUB
will place the CPUB system on hold rather than CPUA (because the
system ID is ignored).
212
4 Operator Commands
ZID Command
The ZID command displays the following information on the system console:
Zeke/OASIS version identification
CPU model and serial number
Number of days remaining in the password counter (number of days left in the
45-day grace period that Zeke will run without obtaining a proper operating
password from the ASG Service Desk)
Current date and time
CPU ID and CPU name
Set of generation options in use
Subsystem ID
Catalog ID and name
NETREGID
Volume and dataset name
Syntax
ZID
Sample Output
Z0903I ZEKE Z520A000 X240A000 9672-030041 Days: 13
Z0903I Time 10:47:52 01/08/2000 Saturday 2000008
Z0903I Cpuid:G Cpuname:PT51ZK51 Genopt:********
Z0903I Subsys:GWS4 Catid:AF3F35C8 P Netregid:ZEKEAL5R
Z09AKI ZEKECAT AF3F35C8 VOL=DEV400 DSN=ZEKE.R520A.GWS.DBASE
213
ZINFO Command
The ZINFO command displays the following information on the system console:
Zeke/OASIS version identification
CPU model and serial number
Number of days remaining in the password counter (number of days left in the
45-day grace period that Zeke will run without obtaining a proper operating
password from the ASG Service Desk)
Current date and time
CPU ID and CPU name
Set of generation options in use
Subsystem
Catalog ID
NETREGID
Number of entries
Space allocated for each schedule table
Total schedule table size
Amount in use
Amount unused
Syntax
ZINFO
Sample Output
Z0903I
Z0903I
Z0903I
Z0903I
214
ZEKE Z520A000 X240A000 9672-030041 Days: 13

Time 10:49:28 01/08/2000 Saturday 2000008
Cpuid:G Cpuname:PT51ZK51 Genopt:********
Subsys:GWS4 Catid:AF3F35C8 P Netregid:ZEKEAL5R
OVR/BLK
# BLKS
# ENT
ALLOC
SQT
3,300
3
60
9,900
ETT
8,400
4
160
8,400
DQT
1,300
1
40
1,300
DSN
1,780
1
40
1,780
4 Operator Commands
ZKILL Command
The ZKILL command terminates the time monitoring, event dispatching, and command
processing functions of Zeke or terminates only Zeke dispatching.Refer to your
ASG-Zeke OS/390 Users Guide for more information on restarting or terminating Zeke.
Syntax
ZKILL
COLD
FORCE
WARM
Parameters
One of the following parameters is required with the ZKILL command:
Parameter
Description
COLD
Terminates all Zeke processing and release all Zeke program and
table storage. Other products within the same address space remain
active.
ZKILL COLD
WARM
Terminates only Zeke dispatching. Zeke still performs all tracking of

jobs, triggering and updates. Other products within the same address
space remain active, as well as Zekes SMF exits.
ZKILL WARM
215
ZMAP Command
The ZMAP command maps the OS/390 initiators that are running active jobs. The
information includes the following:
Current jobname
Phase name
Zeke step name
Zeke event number
Start time of each job
Elapsed real time for each job
CPU time
Start I/O count
Syntax
ZMap
ALL
CLass
class-ID
Parameters
The following parameters can also be used with the ZMAP command:
Parameter
Description
none
Displays only the initiators running active Zeke jobs.

ZMAP
ALL
Displays initiators running active Zeke jobs and non-Zeke jobs. Only
jobs that started after Zeke came up are listed.
ZMAP ALL
CLass
Displays all jobs running in a specified dynamic class or all dynamic

classes.
ZMAP CL=C
Display all jobs running in dynamic class C.

ZM CLASS
Display all jobs running in all dynamic classes.

216
4 Operator Commands
ZOK Command
The ZOK command notifies Zeke that an event has been approved by the operator for
dispatch. If the OPEROK field response on the Event Master Record is YES (Y), ZOK is
required for an event.
When events requiring an operator approval move from the schedule queue to the dispatch
queue, the operator is notified by a console message. The events remain in the dispatch
queue until the ZOK command is issued.
Note:
If an event is in the schedule more than once, the ZOK command only affects the first
occurrence.
Syntax
ZOK
global
Examples
Use the Global Event Selection Parameters (starting on page 143) with the ZOK
command. The following are examples of using the ZOK operator command with some
of the Global Event Selection parameters.
ZOK EV 56
Select event 56 for OPEROK.
ZOK JOB *PR
Select all job events having a jobname beginning with PR for OPEROK.
ZOK ALL
Provide OPEROK for all that require it.
ZOK DQ,ZCOM
Provide OPEROK for all ZCOM events in the dispatch queue.
ZOK GR PAY ALL
Provides OPEROK for all events with group ID PAY.To display a list of all events
that require an operator OK, use the ZDISPLAY command and the OPEROK
parameter, or use the ZSTATUS command and the ALL parameter.
217
ZREFRESH Command
The ZREFRESH command refreshes a schedule queue record by resetting the event as if
it had not been run. The prerequisite and completion indicators are reset.
Because the REFRESH command resets all prerequisite completion indicators, all
prerequisite conditions (EOJ, AEOJ, etc.) must be satisfied once again. To automatically
satisfy the prerequisites, use the ZALTER WHENOK command.
Any refreshed event is placed on operator hold automatically by the system. The operator
has to release the hold before the event can dispatch. This prevents the system from taking
any action concerning the event before the operator is ready.
Only events that have been dispatched (events in SUCC, ACTV, or PEND status) can be
refreshed using the ZREFRESH command.
Syntax
ZREFresh
global
EVent number
RERUN
FORCE
Parameters
To select an event or events, enter one or more of the Global Event Selection Parameters
(starting on page 143). The following parameters can also be used with the ZREFRESH
command.
Parameter
Description
RERUN

exit ZEKE14D. If the option TRIGRRN=NO, the event does not
designation.
ZREF EV 6 RERUN
Set up Event 6 for processing again and add the RERUN

designation to the schedule record.
218
4 Operator Commands
Parameter
Description
FORCE
Releases an event's resources before refreshing the event. This

produces the same effect as releasing all of the resources and then
issuing the ZREFRESH command. If there are no resources for the
event, this parameter is ignored.
ZREF EV 12 FORCE
Release all resources and then set up event 12 for processing

again.
Examples
The following examples show the use of some of the Global Event Selection parameters.
ZREFRESH JOB * APP TST
Set up all job events with application of TST for processing again.
ZREF JOB * GRO PRD
Set up job event with a group ID of PRD for processing again.
The following example uses both ZREFRESH and ZALTER on the same command line.
ZREF EV 45 ZA EV 45 WHENOK
Set up event 45 for processing again, and consider all prerequisites satisfied.
219
ZRELEASE Command
The ZRELEASE command releases the following types of holds:
An operator hold on one or more events
An operator hold on an initiator
An operator hold on Zeke
A system hold on one or more events
Syntax
ZRelease
global
INITiator init-ID
SYstem
Parameters
To release an operator hold on one or more events, use the Global Event Selection
Parameters (starting on page 143). The system reports the number of events selected for
release. An event is not selected for release if it is not currently being held. So, the
message ZREL EV 45 of Z0906W NO QUALIFYING SCHEDULE ENTRIES FOUND
might mean that event 45 is not selected for the release because it is not being held.
Examples
The following are some examples of using Global Event Selection parameters:
ZR EV 45
Release the operator hold on event 45.
ZR JOB PR******
Release the operator hold on any job event having a jobname beginning with PR.
ZR ALL
Release the operator hold on all events in the schedule queue or dispatch queue.
ZR JOB *
Release the operator hold on all job events.
ZR JOB * HOLD=NET
Release the operator hold on all job events that have been internally placed on NET
hold.
220
4 Operator Commands
Note:
Valid qualifiers for HOLD are: OPER, SJCL, NET, RFSH, DNPL, INTR, and PSID.
To release an operator hold on an initiator, use the INITIATOR parameter. This parameter
names the initiator to be released. A hold on an initiator prevents Zeke from dispatching
job events to that initiator.
Parameter
Description
INitiator
Specifies the one- or two-character ID of the initiator to be released.

ZR IN A
Release the operator hold on initiator A.

ZR IN 10
Release the operator hold on initiator 10.

To release a system hold, use the SYSTEM parameter. A system hold prevents Zeke from
dispatching any events, except events released to dispatch with a ZRELEASE. A
subsequent system release permits all event dispatching by Zeke. The SYSTEM parameter
is only accepted if a system hold is currently in effect; otherwise, the command is rejected
with an appropriate error message.
Parameter
Description
SYstem
Releases a hold on event dispatching. No event is dispatched while a

system hold is in effect.
ZREL SYS B
Releases dispatching for system B.
221
ZRELOAD Command
The ZRELOAD command reloads selected system tables. If you are running multiple
systems, the ZRELOAD command must be issued for each system.
Note:
Audit options are not reset by the ZRELOAD GENOPT command. Zeke must be cycled
before they are effective.
Syntax
ZRELOAD
GENopt
INITiator init-ID
JOBIndex
SCHD
Parameters
Use the following parameters with the ZRELOAD command:
Parameter
Description
INITiator
Reloads the system initiator tables.
GENopt
Reloads the system generation options. The following generation

options are not reset by the ZRELOAD GENOPT command; Zeke
must be cycled before they are effective:
AUR
IDCAMS
JOBXIT#
MULTSYS
NETREGID
OPRHOLD
POSID
VARINDEX
WKTRGDN
X14COML
DYNSMF
IEFU83
Note:
You must exit from the Generation Options screen in order for the
ZRELOAD GEN command to take effect.
222
JOBIndex
Reloads the job index in storage. If the generation option DataSpac is

Y, this index resides in a dataspace. If the EDBindex genopt is Y, it
resides in common storage. If neither option is set, the command does
not apply.
SCHD
Reloads the Zeke schedule tables for the system.
4 Operator Commands
ZRESOURCE Command
The ZRESOURCE command maintains resources defined to the Zeke database. Use this
command and its parameters to display resource detail, alter resource detail, and release a
resource from events or a system.
Syntax
ZRESource
DISPLAY
ALTER
RELease
resource name
*
resource name
*
resource name
*
ALL
SYStem sys-ID
SYStem *
ALLSHR
NOSHR
SHR n
ENABLE
DISABLE
ALL
EVtnum number
DAte yyyyddd
SYStem sys-ID
SYStem *
VER number
Parameters
Use the following parameters with the ZRESOURCE command:
Parameter
Description
resource name Required. Resource names cannot contain embedded blanks. Enter
an asterisk (*) to display all resources.
ZRES DISPLAY 3480
Displays resource detail for resource 3480.

ZRES DISPLAY *
Displays resource detail for all resources.

DISPLAY
Displays the resources. The DISPLAY parameter can be followed

by the following subparameters:
223
Parameter
Description
SYStem
Shows resource detail for all systems (*), a specific

system name, or the system where you entered the
ZRESOURCE command (default).
ZRES DISPLAY 3480
Displays resource detail for the system you are

on.
ZRES DISPLAY 3480 SYS MVSA
Displays resource detail for the MVSA system.

ALTER
Alters the resource as specified.

Note:
Use one of the following subparameters to how the resource is

altered.
ALLSHR
Allows all events to share this resource.

ZRES ALTER 3840 ALLSHR
NOSHR
Prevents this resource from being shared by other

events.
ZRES ALTER 3840 NOSHR
SHR {n}
Indicates how many events can use this resource at

one time.
ZRES ALTER 3840 SHR 5
ENABLE
Enables the resource for all events defined to use it.

ZRES ALTER 3840 ENABLE
DISABLE
Disables the resource for all events defined to use it.

ZRES ALTER 3840 DISABLE
RELEase
Releases the resource from an event or events.

ALL
You must enter this or the EVTNUM parameter.

Releases the resource from all events.
ZRES REL 3480 ALL
EVtnum
224
You must enter this or the ALL parameter. Releases

the resource from this event.
4 Operator Commands
Parameter
Description
DAte
This parameter is required if you use EVTNUM.

Format YYYYDDD. Specifies the schedule record
date. The resource is released for this schedule
record only.
ZRES REL 3480 EV 100 DA 2002214
SYStem
Specifies the system from which to release the

resource. The default is the system on which the
command is entered. Enter * for all systems.
ZRES REL 3480 ALL SYS *
VER
Releases the resource from the specified version of

the event. If a version number is not specified, the
resources are released for all versions of the event.
ZRES REL 3480 EV 100 VER 3
Sample Output
The following is a sample of the output:
Z0994I RESOURCE DISPLAY
SHARE
MAX EX SYSTEM
RESOURCE NAME
3
3 N (GLOBAL) EWP1
SHR(10/0/2001055 A, 11/0/2001055 A, 12/0/2001055 A)
event number
version
schedule date
ZSCAN Command
The ZSCAN command validates or retrieves JCL that will be submitted by Zeke. For
example, for an OS/390 job the JCL is passed to OS/390 with the TYPRUN=SCAN
parameter specified on the job card.
ZSCAN can be used for any job event in the schedule queue that will be submitted to an
operating system that supports this type of feature. The event's schedule queue record is
not affected in any way and the event is dispatched normally when all its dispatch
requirements are met.
The default is to scan the event on the submission system. If another system is desired, use
the ONSYS parameter.
225
Syntax
ZSCAN
global
ONSYS sys-ID
JCLR
Parameters
Use any of the Global Event Selection Parameters (starting on page 143) with the
ZSCAN command. The following parameters can also be used with the ZSCAN
command:
Parameter
Description
JCLR
Retrieves the JCL from the JCL source and puts it in the SQR so you
can view or update it. The JCL must reside on the same system you
are issuing the command from. For example:
ZSCAN EV 14 JCLR
Retrieves the JCL for event 14.

Note:
The JCLR parameter cannot be used with the ONSYS parameter.

ONSYS
Scans the JCL on the specified system. For example:

ZSCAN JOB PAY ONSYS B
Submit job PAY for scanning on system B. System B must match

the platform type of the job.
Note:
The ONSYS parameter cannot be used with the JCLR parameter.
226
4 Operator Commands
ZSET Command
Set Variable Values
The ZSET command can be used to set the value of a Zeke variable to a specified or
calculated value. The variable is added to the Zeke database if it does not already exist.
The ZSET command cannot be used to set OASIS variable values.
Syntax
ZSET
VAriable $var-name
EQual
value
+ value
- value
All Zeke variables must begin with a dollar sign ($).

If the variable value contains special characters, such as an asterisk (*), period (.), or
ampersand (&), enclose the value within single quotes ('). For example, *** or =.
Single quotes are not required for numeric values, unless the first digit is zero. If you do
not enclose a number beginning with zero in single quotes, the leading zero is dropped. If
you enclose a numeric variable value in single quotes, you cannot add to or subtract from
the value using the plus and minus parameters. Also, if you enclose a date value in single
quotes, you cannot perform date calculations on the variable.
If quote marks are part of the character string, enclose the string within another set of
quotes. For example, if the string is KEEP THE QUOTES, enter KEEP THE
QUOTES as the value.
All valid Zeke special names, such as ZEKECPU, DATEJ, TIME, and DATE, can be
specified as the value of a Zeke variable. The variable value becomes the value represented
by the Zeke special name.
Examples
ZSET VAR $CHAR3 EQ DATE
$CHAR3 is equal to the current date.
ZSET VAR $CHAR4 EQ ZEKECPU
$CHAR4 is equal to the CPU name.
227
Parameters
Use the following parameters with the ZSET command:
Parameter
Description
VAriable
Specifies the name of the variable to be set.
EQual
Precedes the new value for the variable.

ZSET VAR $TEST EQ YES
$TEST is equal to YES (character value).

ZSET VAR $TEST1 EQ 456
$TEST1 is equal to 456 (numeric value).

ZSET VAR $TEST2 EQ $TEST1
$TEST2 is equal to $TEST1.

ZSET VAR $CHAR1 EQ 'A CHAR STRING'
$CHAR1 is equal to 'A CHAR STRING' (character value).

Note:
You can use both a plus (+) and a minus (-) on the same statement. However, only one
plus and one minus can be used per statement. For example, ZSET VAR $VAR1 EQ
$A + $B - $C is valid, but ZSET VAR $VAR1 EQ $A + $B + $C is not valid
+ (plus)
Adds the value to the value following EQUAL. Can be specified in a

numeric value or variable.
ZSET VAR $TEST3 EQ $TEST3 + 1
$TEST3 is incremented by one.

- (minus)
Subtracts the value from the value following EQUAL. Can be

specified in a numeric value or variable.
ZSET VAR $TEST3 EQ 4 + $TEST1 - $TEST2
$TEST3 is increased by 4, plus the value of $TEST1, minus the

value of $TEST2.
228
4 Operator Commands
Set Default System ID

The ZSET command issued with the SYSTEM parameter changes the default system ID
for subsequent operator commands. This only affects the commands entered from the
user that enters the ZSET command. The system ID is not affected.
Refer to your ASG-Zeke OS/390 Users Guide for more information on setting Zeke
variable values, using variables to trigger events, and using variables to restart a job.
Syntax
ZSET
SYStem sys-ID
SYStem
*
Normally, the Zeke command processor assumes the commands entered are from the
system from which the command originates. To enter commands for events on another
system ID, you must enter the system ID on the command line.
This command is useful for CMS users, since each CMS user accessing the same Zeke
database must have a unique system ID. Events displayed in the ZCOM function are
always on a different system ID (that of an OS/390 user ID). Use this command to establish
a default system ID for subsequent commands (even the operator console command
processor on System A could be set to affect events on System B by default). The ZSET
command with the SYSTEM parameter is allowed even if other types of ZSET commands
are restricted through Zeke's security system.
ZSET SYSTEM B
Sets the default system to system B. All operator commands are assumed to apply
to system B until the system is reset.
ZD
Displays events on system B. Same as entering ZD SYS B
ZA EV 4 NEWSYS A
Changes event 4 from system A to system B.
ZD SYS C
Displays system C events.
ZSET SYS *
Causes subsequent Zeke commands to effect qualified events on ALL systems.
229
ZSTATUS Command
The ZSTATUS command displays the reason an event is waiting in the dispatch queue.
The output from the command is displayed on the system console. (If the event is simply
waiting for an initiator, the reason is not displayed.) Some of the reasons include:
Waiting for a required number of available tape drives
Waiting for an operator OK
Any message displayed at the time operator action was first required is redisplayed.
The ZSTATUS command displays the same information as the ZD WAIT command on
page 196.
Only events in the dispatch queue are selected for processing by the ZSTATUS command.
Refer to your ASG-Zeke OS/390 Users Guide for information on using Schedule View to
monitor events.
Syntax
ZSTatus
global
Parameters
The Global Event Selection parameter DQ (dispatch queue) is assumed for this
command. The parameter SQ (schedule queue) is ignored if entered. Use any other
Global Event Selection Parameters (starting on page 143) to select the proper events.
Examples
The following examples demonstrate the use of the ZSTATUS command, along with
some of the Global Event Selection parameters.
Note:
The output from this command will be displayed on the system console.
ZSTATUS EV 88
Display status of event 88.
ZST JOB CD07UPDT
Display status of job CD07UPDT
230
Index
Symbols
$XXXXX special name 78
A
ABCODE special name 77
ABTYPE special name 77
ACTV status 201
address on reports, updating 43
AEOJ (abnormal end of job) status 201
Audit Log Facility 43
B
backing up the database, BACKUP batch
utility 68
batch utility program
character string delimiters 3
$$ (two dollar signs), end of
statement 3
command acceptance 5
executing ZEKEUTL procedure 5
formatting rules 3
OCCURS/WHEN clauses 4
main functions 2
parameters and operands, syntax of 3
reading input source 5
statement format 3
BACKUP command 68
CALENDAR command 911
CREATE command 11
DOC function 1316
EVENT command 1740
JCL function 4142
OPTION function 4346
OVERRIDE command 5961
REPORT command 6163
RESTORE command 4751
SCHEDULE command 5263
SIMULATE function 65
VAULT function 64
C
calculating dates (CDATE) 88
calendars
CALENDAR batch utility 911
listing calendar information 129
CAPS OFF
using to enter mixed case job names in
WHEN conditions 4
case mixed see job name long
CDATE, date calculations 88
code, see condition codes
commands
issuing via SET xCOM 81
commands, see batch utility program,
operator commands
company name on reports, updating 43
COMRC special name 77
condition codes 23
setting codes using ZEKESET 84
conventions page vii
CPU password 43
CPUID special name 77
CREATE batch utility 11
creating
sequential disk file 103
creating a sequential disk file 119
D
database
backing up the database 68
copying
Audit Trail dataset 6
documentation to the
database 13
JCL into the database 41
Zeke database 6
initializing the database 11
restoring the database 47
status report 43
vault, disabling 64
dataset triggering hold code 197, 206
dataspace
use in report generation 112
date calculations (CDATE) 88
231
DATE special name 78

DATEJ special name 78
DAY special name 78
dispatching, see WHEN conditions
DOC batch utility 1316
E
electronic vaulting, see vaulting
event
activating an event 19
converting platform event 18
deactivating an event 19
EVENT batch utility 1740
job events 1840
listing events 110128
refreshing events 158, 218
status codes 197, 205
versions
adding to the schedule
(batch) 34, 39
maintaining versions using
operator commands 150
EVENT special name 78
F
F/OK status 201
F/S status 201
FAIL status 201
FBOK status 201
forecasting the schedule 53
function codes, see condition codes
G
generation options
DataSpac 222
DISPSEL 167
EDBindex 222
LOADCOMM 151
Mult(xx) 153, 155156
MULTSYS 186
Multsys 43
Posid 43
GRESOURCE parameter 45
GRESSYID parameter 45
H
HIGHCOND special name 78
I
IF clauses within SET statements 76
J
JCL
232
job
batch utility 4142

Zeke job control statements 74
ZEKEUTL 5
event 1840
job name
long
in WHEN conditions 4
with most operator
commands 148
with ZADD 148
with ZDISPLAY 147
mixed case, see job name long
JOBNAME special name 78
L
LASTCOND special name 78
LASTEVENT batch parameter 13, 21, 41
LASTPGM special name 78
LASTSTEP special name 78
LITERAL special name 78
long job name, see job name long
M
mixed case, see job name long
MULTHIT parameter 45
MULTISYS parameter 45
N
NAME1 parameter 45
NAME2 parameter 45
NAME3 parameter 45
NAME4 parameter 45
NETREGID 161
NNN special name 79
NOTRIG option 163
O
OCCURS clauses
formatting rules 4
ON EOM command (end-of-month
rounding) 95
operator commands
abbreviations 141
documentation conventions 141
entering commands from console,
/ZC, or ZCOM 139
global event selection parameters 143
multiple parameters 142
ZADD 152
see also ASG-Zeke User Guide
ZALTER 159
ZDELETE 168
Index
ZDISABLE 172
ZDISPLAY 174
ZENABLE 209
ZHOLD 210
ZID 213
ZINFO 214
ZKILL 215
ZMAP 216
ZOK 217
ZREFRESH 218
ZRELEASE 220
ZRELOAD 222
ZRESOURCE 223
ZSCAN 225
ZSET 227
ZSTATUS 230
operator IDs
listing information about IDs 135
security classes, listing information
about 137
operators in IF clauses 76
OPTION batch utility 4346
OUTFILE parameter 103, 119
output reports to file 103
OVERRIDE batch utility 5961
P
password 43
PASSWORD parameter 45
PEND status 201
POSID parameter 46
POSIDEND parameter 46
printing the database status report 43
R
RDATE 52
reason codes 197, 205
recurring events 38
refreshing events 158, 218
remote prerequisites (satisfying WHEN
conditions on remote systems) 185
REPORT batch utility 6163
report writer facility
calendar listings
reporting parameters 129
sample reports 130
creating a sequential disk file 103,
119
event master listings
fields parameters 107
line spacing parameters 107
page break parameters 106
report formatting 104

sample reports 124
sort sequence parameters 104
formatting reports 101
operator ID listing 135
operator ID security class listing 137
output report to file 103
printing the database status report 43
report types 100
schedule listings
fields parameters 107
line spacing parameters 107
page break parameters 106
report formatting 104
sample reports 126127
sort sequence parameters 104
updating company name and
address 43
variable listing
sample reports 133135, 137
138
restoring the database, RESTORE batch
utility 4751
return codes, see condition codes
S
SCHDT keyword 145, 154, 157
schedule
forecasting 53
listings 110128
SCHEDULE batch utility 5263
OVERRIDE command 5961
REPORT command 6163
simulating the schedule 53
simulation 53, 65
SCOM events 17
security
listing information about operator ID
security classes 137
sequential disk file, creating 103, 119
SET clause, IF clause within 76
SET VARIABLE statement 82
SET xCOM, issuing system and Zeke
commands 81
simulating the schedule 53, 65
STALEA download status 164
STALEZ download status 163
status
database status report 43
download
STALEA 164
STALEZ 163
233
event status 197, 201, 205

STATUS parameter 46
SUCC status 201
SYSGEN parameter 46
system
command events, see SCOM events
T
THISPGM special name 78
THISSTEP special name 78
TIME special name 78
tracking
options, Audit Log 43
triggering events, hold code 197, 206
U
user IDs
blanking out an incorrect user ID in an
EMR 39
V
variables
defining a new variable 82
listing variable information 131
setting values 82, 227
substitution, deactivating
(ZEKESET) 87
vaulting, VAULT batch utility 64
VERSION special name 78
W
WEAK conditions 163
WHEN conditions
formatting rules 4
listing events with a particular WHEN
condition 122
satisfying WHEN conditions on
remote systems 185
WEAK conditions 163
work centers 17
X
XXX special name 79
Z
ZADD command 152
see also ASG-Zeke Users Guide
ZALTER operator command 159
ZDELETE operator command 168
ZDISABLE operator command 172
ZDISPLAY operator command 174
ZEKECPU special name 78
ZEKESET function
234
branching within control

statements 86
creating large block letter separator
pages 79
date calculations 88
issuing CP commands 82
SET statement syntax 75
setting a wait interval 87
setting condition codes 84
setting return codes 84
special name values 77
terminating a job 79
turning off variable substitution 87
ZEKEUTL 5
ZENABLE operator command 209
ZHOLD operator command 210
ZID operator command 213
ZINFO operator command 214
ZKILL operator command 215
ZMAP operator command 216
ZOK operator command 217
ZREFRESH operator command 218
ZRELEASE operator command 220
ZRELOAD operator command 222
ZRESOURCE operator command 223
ZSCAN 225
ZSET operator command 227
ZSTATUS operator command 230
ASG Worldwide Headquarters Naples Florida USA I asg.com

Zeke Reference Guide

Uploaded by

Copyright:

Available Formats

Zeke Reference Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Zeke Reference Guide

Uploaded by

Copyright:

Available Formats

ASG-Zeke OS/390

ASG Worldwide Headquarters Naples Florida USA | asg.com | info@asg.com

ASG Documentation/Product Enhancement Fax Form

2002 Allen Systems Group, Inc.

ASG Support Numbers

Product name, version number, and release number

List of any fixes currently applied

Any alphanumeric error codes or messages written precisely or displayed

A description of the specific steps that immediately preceded the problem

If You Receive a Voice Mail Message:

Follow the instructions to report a production-down or critical problem.

Severity Codes and Expected Support Response Times

Expected Support Response

Major component of product disabled

Problem with the product, but customer has

"How-to" questions and enhancement

Business Hours Support

United States and

All other countries:

Non-Business Hours - Emergency Support

United States and

All other countries

ASG Web Site

1 Zeke Utility Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

ASG-Zeke OS/390 Reference Guide

LIST EVENT/PLANEvent Master and Schedule Listings . . . . . . . . . . . . . . . . . 110

4 Operator Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Global Event Selection Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

ZDELETE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

ZENABLE Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

ASG-Zeke OS/390 Reference Guide

ZRESOURCE Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

About this Publication

Chapter 4, "Operator Commands," describes the operator commands used to make

ASG-Zeke OS/390 Reference Guide

ASG-Zeke OS/390 Installation Guide (AZM0300-nn) defines Zeke system

ASG-Zeke OS/390 Reference Guide (AZM0400-nn) provides a reference for using

ASG-Zeke Quick Reference (AZM0900-nn) is a quick-reference guide to Zeke

ASG-OASIS Reference Guide (AZO0300-nn) provides information about

To obtain a specific version of a publication, contact the ASG Service Desk.

Directory, path, file, dataset, member, database,

Information that you provide according to your

Characters you must type exactly as they are shown.

Vertical Separator Bar ( | )

Options available with the default value underlined (e.g.,

ASG-Zeke OS/390 Reference Guide

1Zeke Utility Program

ASG-Zeke OS/390 Reference Guide

Creates the daily schedule

Backs up the Zeke database

Restores a backup database

Adds and maintains EMRs

Adds and maintains system calendars

Performs various functions within Zeke

Copies JCL into the database

Copies documentation into the database

Controls the vault dataset

1 Zeke Utility Program

Continue on as many statements as necessary in any column (from 1 through 72).

Enclose multiple operands within parentheses and separate by a comma or by one