_beta log|z
(Beta 92)
Administrator Guide
Version 7 Release 2
December 15, 2022
Document number: B92-V7R2-ADM-EN-20221215
Beta Systems DCI Software AG
Alt-Moabit 90d
D-10559 Berlin
www.betasystems-dci.com
Support Contact Information
support@betasystems.com
Telephone Germany:
0800-BETASYS (or 0800-2382797)
Telephone International:
+49 (0)6321 499 15 108
IBM and all IBM products mentioned in this publication are trademarks or
registered trademarks of International Business Machines Corporation.
Microsoft, Windows, Windows Explorer, and Windows PowerShell are
trademarks or registered trademarks of Microsoft Corporation.
SAP, XMI, BC-XBP, RFC, and all other SAP products mentioned in this
publication are trademarks or registered trademarks of SAP AG.
Sun Solaris and SunOS are trademarks of Sun Microsystems.
Control-M is a registered trademark of BMC Software, Inc.
All other trademarks mentioned in this publication are the property of their
respective owners.
© 2022 Beta Systems DCI Software AG
All rights reserved. This manual may not be copied in part or in its entirety
for distribution to third parties without the express written permission of the
publisher.
Contents
Contents
Introduction............................................................................................... 9
Introducing _beta log|z ............................................................................. 10
Structure of the documentation ................................................................ 19
What you can find in this manual ............................................................. 22
Product names and identifiers .................................................................. 24
Conventions used in this manual ............................................................. 26
What is new in _beta log|z ....................................................................... 29
V7R2-02 (POM8137): New functions in _beta log|z ............................ 29
V7R2-01 (POM8073): New functions in _beta log|z ............................ 30
V7R2-00 (POM8004): New functions in _beta log|z ............................ 31
V7R1-04 (POM7667): New functions in _beta log|z ............................ 33
V7R1-03 (POM7635): New functions in _beta log|z ............................ 34
V7R1-02 (POM7588): New functions in _beta log|z ............................ 34
V7R1-01 (POM7562): New functions in _beta log|z ............................ 35
V7R1-00 (NONE): New functions in _beta log|z .................................. 35
Leading in to _beta log|z ....................................................................... 42
_beta log|z product components .............................................................. 43
MSGCLASS and job output lists .............................................................. 44
OMS control cards .................................................................................... 47
ISPF application ....................................................................................... 52
Basic functions ..................................................................................... 54
Primary Selection Menu ....................................................................... 55
Administration Selection Menu ............................................................. 56
Panel structure ......................................................................................... 57
News (Option N) ..................................................................................... 59
General (Option A.1) .............................................................................. 61
Definitions Selection Menu ....................................................................... 62
_beta log|z layouts (Option A.1.1) ............................................................ 63
Layout creation sequence .................................................................... 64
Default layouts provided by _beta log|z ............................................... 65
Which default layout is used for which online option?.......................... 67
Layout fields (Option A.1.1.1) ............................................................... 72
Search layouts (Option A.1.1.2) ........................................................... 76
Displaying search layouts ..................................................................... 76
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
3
Contents
Changing search layouts ...................................................................... 79
Inserting search layouts ....................................................................... 83
Defaults for search layouts ................................................................... 89
Result layouts (Option A.1.1.3) ............................................................ 91
Displaying result layouts ....................................................................... 91
Changing result layouts ........................................................................ 94
Inserting a job result layout .................................................................. 98
Defaults for result layouts ................................................................... 102
Job group (Option A.1.2) ........................................................................ 103
Defining job masks for job groups ...................................................... 106
Determining the best matching job group .......................................... 108
Determining online and archive retention period................................ 111
Assigning jobs to job groups .............................................................. 117
Notify groups (Option A.1.3) ................................................................... 122
Enterprise (Option A.2) ........................................................................ 124
Processing enterprise data..................................................................... 125
Enterprise definition concept and sequence .......................................... 127
Rule group definitions (Option A.2.1) ..................................................... 130
Rule definitions (Option A.2.2) ............................................................... 132
Operation definitions (Option A.2.3) ....................................................... 136
Run cycle definitions (Option A.2.4) ....................................................... 140
Agent group definitions (Option A.2.5) ................................................... 142
Agent definitions (Option A.2.6) ............................................................. 144
Activating and refreshing agents ........................................................ 149
Scan group definitions (Option A.2.S) .................................................... 151
SAP system definitions (Option A.2.7) ................................................... 153
SAP server definitions (Option A.2.8) .................................................... 156
SAP account definitions (Option A.2.9) .................................................. 159
Working with file operations for normal logs .......................................... 161
Working with file operations for endless logs ......................................... 162
Working with file operations for Windows event logs ............................. 163
Transferring a Unix system log to _beta log|z ........................................ 165
Working with SAP operations for job logs .............................................. 168
Working with SAP operations for endless logs ...................................... 170
File tailoring (Option A.3) .................................................................... 172
Tailoring files .......................................................................................... 173
Tailoring JCL for batch utilities (Option A.3.1)........................................ 175
Deleting or reusing an empty GAR database (Option A.3.2) ................. 177
Adding a new GAR database (Option A.3.3) ......................................... 180
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
4
Contents
Monitor (Option A.M) ............................................................................ 182
Displaying agent rule status information (Option A.M.1) ........................ 183
Which rules are planned for execution and at what time? ................. 185
Displaying rule definitions ................................................................... 186
Displaying jobs and logs read in by a rule .......................................... 187
Displaying definitions of the agent connected to a rule ...................... 188
Displaying or processing reload requests (Option A.M.2) ...................... 189
Displaying _beta log|z statistics (Option A.M.3) ..................................... 191
Archive (Option A.A) ............................................................................ 192
Archiving concept ................................................................................... 193
Working with generation archive (GAR) databases ............................... 195
Determining archive retention period and medium ................................ 197
Working with archive pools and archive datasets .................................. 199
The archive run ...................................................................................... 203
Archive definition .................................................................................... 205
Defining archive pools (Option A.A.1) ................................................ 206
Displaying archive datasets (Option A.A.2) ........................................ 212
Archive volume records (Option A.A.3) .............................................. 215
System (Option A.S) ............................................................................. 218
System Options Selection Menu ............................................................ 219
Generation (Option A.S.1) ...................................................................... 220
Subsystems (Option A.S.2) .................................................................... 223
Global options (Option A.S.3)................................................................. 230
Special reload (Option A.S.4) ................................................................. 236
Reload by generation (Option A.S.4.1) .............................................. 237
Sorting the Archived Job Select Table ............................................... 241
Processing reload requests ................................................................ 242
B92RLOAD Reload V2 (Option A.S.4.2) ............................................ 245
Reloading lists or job information using B92RLOAD Reload V2 ........ 247
B92RLOAD Reload V3 (Option A.S.4.3) ............................................ 249
Selecting a reload request .................................................................. 251
Defining a reload request ................................................................... 253
Processing one or all reload requests ................................................ 255
B92RLOAD V3 report ......................................................................... 256
Using automatic reload ....................................................................... 257
Reader (Option A.R) ............................................................................. 259
Class (Option A.R.1) .............................................................................. 260
JES reader (Option A.R.2) ..................................................................... 264
Scanning (Option A.R.3) ........................................................................ 268
Selecting scan definitions ................................................................... 270
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
5
Contents
Defining scan definitions .................................................................... 274
Target field IDs ................................................................................... 284
Example: Defining a primary search string ........................................ 289
Example: Defining additional criteria for job selection........................ 303
Scan definitions for Message Output Facility (MOF).......................... 305
Simulating the execution of scan definitions ...................................... 306
NoError (Option A.R.4) ........................................................................... 308
Selecting NoError definitions .............................................................. 309
Specifying NoError completion codes ................................................ 312
Log processing (Option A.R.5) ............................................................... 315
Event actions (Option A.R.6) .................................................................. 318
Skeletons and variables ..................................................................... 322
Event processing ................................................................................ 324
Standard events ................................................................................. 327
Large list monitoring and outlim processing ........................................... 331
Triggering e-mail via DD MAILOUT ....................................................... 339
Database (Option A.D) ......................................................................... 344
Which databases are available? ............................................................ 345
_beta log|z database components ......................................................... 346
What happens when a database becomes full? .................................... 350
Databases (Option A.D.1) ...................................................................... 351
Defining spool files ............................................................................. 355
Updating spool files ............................................................................ 357
Displaying database information ........................................................ 359
Dictionary (Option A.D.2) ....................................................................... 362
Displaying tables (Option A.D.2.1) ..................................................... 363
Displaying keys (Option A.D.2.2) ....................................................... 368
Displaying fields (Option A.D.2.3) ...................................................... 370
Displaying system databases (Option A.D.2.4).................................. 371
Database usage statistics (Option A.D.3) .............................................. 373
Statistic values (Option A.D.3.1) ........................................................ 374
Displaying daily or hourly statistics..................................................... 375
Statistic batch reports (Option A.D.3.2) .............................................. 376
Fields in the statistics panels .............................................................. 378
Fields for the RPGPRINT, RPGWORK, RPTRUN and RPTLIST
options ....................................................................................... 381
Deleting obsolete statistics data (Option D.3.3) ................................. 382
Database queries (Option A.D.Q) .......................................................... 383
Generating JCL for database utilities (Option A.D.4) ............................. 385
BSA Service Manager (Option A.D.S) ................................................... 388
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
6
Contents
Product batch utilities.......................................................................... 389
Starting product batch utilities ................................................................ 391
General structure of the JCL .................................................................. 392
B92ADR01: Updating volume/label information of archive datasets ..... 395
B92AGINF: Getting agent information ................................................... 398
B92ARPRI: List archiving ....................................................................... 400
Parallel archiving ................................................................................ 403
Errors during archiving ....................................................................... 405
B92ARSEC: Job record cleanup ............................................................ 406
B92BCAPI: Querying the database via command API .......................... 409
B92BFJBR: Job information report......................................................... 415
B92BFJGI: Job Group Information ......................................................... 419
B92CLAR2: Clear extended generation archive records ....................... 421
B92CLARC: Archive cleanup ................................................................. 424
B92CLARS: Cleanup for agent rule status and statistics....................... 429
B92CLEVT: Clearing events .................................................................. 434
B92CLLST: List cleanup......................................................................... 437
B92CLREO: List reorganization ............................................................. 441
B92DAILY: Daily job ............................................................................... 442
B92DBVER: Database verification ......................................................... 444
B92FFIND: Find in online/offline logs ..................................................... 446
B92FFIND and automatic reload requests ......................................... 453
B92FFIND for searching syslogs........................................................ 457
B92MICRO: Microfiche........................................................................... 461
B92MUPDT: Mass update...................................................................... 464
Updating jobs with B92MUPDT .......................................................... 467
Updating lists with B92MUPDT .......................................................... 470
B92PRINT: Printing/Mailing lists ............................................................ 472
B92RDPS4: Reading z/OS Unix files into _beta log|z ........................... 484
B92SENDL: Transferring lists to an EJM agent ..................................... 488
B92SSRCH: Advanced search in online logs ........................................ 497
Selection parameters.......................................................................... 500
Search-related parameters ................................................................. 502
Search expressions ............................................................................ 503
B92SSRCH reports ............................................................................ 507
Customer-specific report (OMSPUNCH) ............................................ 512
B92WAIT4: Waiting for a job or list ........................................................ 515
B92WEEKL: Weekly job ......................................................................... 520
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
7
Contents
Calling _beta log|z from REXX scripts ............................................... 523
Introduction ............................................................................................. 524
BRXOPEN: Opening a session .............................................................. 526
BRXOMS - READER: Reader-related commands ................................. 527
BRXCLOSE: Closing a session.............................................................. 530
Example: Starting/Stopping a reader ..................................................... 531
Example: Querying reader status ........................................................... 532
Example: Querying reader usage statistics............................................ 533
Extended Index Facility (EIF) .............................................................. 534
User fields for user-defined indexes ....................................................... 535
EIF Select (Option M.1) .......................................................................... 537
RACF security for EIF jobs ..................................................................... 538
Scan definitions .................................................................................... 539
Overview................................................................................................. 540
Scan definitions identical for JES2 and JES3 (S#92SJ23) .................... 541
Scan definitions used for JES2 (S#92SJ2) ............................................ 548
Scan definitions used for JES2 syslog (S#92SL2) ................................. 549
Scan definitions used for JES3 syslog (S#92SL3) ................................. 550
Scan definitions used for JES3 (S#92SJ3) ............................................ 551
Scan definitions used for EVT (S#92SEVT)........................................... 553
Questions and answers ....................................................................... 555
Glossary of terms ................................................................................. 558
Index ...................................................................................................... 566
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
8
Introduction
In this chapter
Introduction
In this chapter
Topic
Page
Introducing _beta log|z ............................................................................. 10
Structure of the documentation ................................................................ 19
What you can find in this manual.............................................................. 22
Product names and identifiers .................................................................. 24
Conventions used in this manual.............................................................. 26
What is new in _beta log|z ........................................................................ 29
V7R2-02 (POM8137): New functions in _beta log|z ............................. 29
V7R2-01 (POM8073): New functions in _beta log|z ............................. 30
V7R2-00 (POM8004): New functions in _beta log|z ............................. 31
V7R1-04 (POM7667): New functions in _beta log|z ............................. 33
V7R1-03 (POM7635): New functions in _beta log|z ............................. 34
V7R1-02 (POM7588): New functions in _beta log|z ............................. 34
V7R1-01 (POM7562): New functions in _beta log|z ............................. 35
V7R1-00 (NONE): New functions in _beta log|z................................... 35
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
9
Introduction
Introducing _beta log|z
Introducing _beta log|z
Overview
The ever-increasing number of daily production jobs makes it necessary to
minimize the manual work done on checking job output.
With _beta log|z, all sysout from the JES spool can be managed, checked
for errors, and archived. As soon as a job is completed, the results can be
viewed online and action can be taken in case of error detection.
_beta log|z is an integrated solution for enterprise-wide job log
management. _beta log|z is a log management system which can be used
to manage job and process logs in Unix, Linux and Windows systems. The
system searches the platforms' logs for errors, ensuring smooth production
throughout the entire enterprise.
Job and process log
checking - an integral
task for the whole
enterprise
Business critical systems, such as those used for resource planning,
supply chain management or customer relationship management
throughout the enterprise, are currently often run on different platforms in
z/OS, Unix, and Windows.
Safeguarding and monitoring production in all systems is a strategic task
that enterprises need to do centrally and comprehensively. The data
center provides the best infrastructure for checking and archiving job and
process logs through its z/OS platform.
Administrators of Unix, SAP and Windows can use the web interface
provided by _beta log|z when they need access to their job and process
logs.
The connection of distributed systems to the z/OS platform is therefore the
decisive prerequisite for successful and efficient IT production in
heterogeneous IT landscapes.
Single-point-of-control
through agent
technology
_beta log|z uses communications agents to connect the central z/OS
system with distributed systems.
The rules the agents use to gather and transfer the job and process logs
can be defined centrally, using an online dialog in _beta log|z, and are
then transferred to the respective agents.
Rules are thus stored centrally in a single point-of-control and can be
handled there by data center staff and platform administrators. This allows
for the flexible allocation of log administration between the data center and
distributed administration.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
10
Introduction
Introducing _beta log|z
_beta log|z architecture
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
11
Introduction
Benefits of using _beta
log|z
Introducing _beta log|z
•
Enterprise processes are optimized and resources saved due to
extended use of data center infrastructure
•
Comprehensive checking and archiving of job and process logs for the
whole enterprise
•
Central management of distributed production processes and central
storage of job and process logs
•
Automatic pre-selection of job and process logs according to selection
criteria
•
Single point of control for configuring file and SAP checking rules
•
Flexible allocation of log handling between the data center and
distributed administration
•
Web interface for viewing files and logs in the web browser
•
Transparent production for users outside the data center
•
Production security through efficient log management for distributed
systems
•
Integration of all job and process logs into central archiving
•
Frees up extra production capacity on distributed platforms
•
Provides an overview of individual systems' workloads
•
Data center output can now be quantified
Enterprise-wide
integrated archiving
concept for job and
process logs
Job and process logs from distributed systems are also included in the
central long-term archive of _beta log|z.
Statistics on jobs and
process logs read in
The integrated statistic monitor of _beta log|z enables users to determine
and document the number of files and logs that have been read in.
This enables you to implement an integrated archiving concept for job and
process logs for the entire enterprise.
In this way individual systems' workloads can be accessed and data center
output clearly quantified for internal and external customers.
Error response
_beta log|z checks job logs for error messages and condition codes. _beta
log|z scans all sysout lists for errors according to user-defined criteria,
relieving your data center staff of the time-consuming, tedious chore of
checking jobs for errors.
Data center staff can easily see all jobs that ended in error in an online
error queue. _beta log|z also reduces reruns by flagging errors such as
NOT CATLG and ABEND.
_beta log|z can also notify users automatically when it detects errors, for
example, via TSO send or e-mail.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
12
Introduction
Introducing _beta log|z
Online control
_beta log|z provides straightforward, easy-to-use ISPF panels for browsing
job logs, output lists, and z/OS system logs. Tutorials are available to help
guide you through the panels. Functions such as printing lists or parts of a
list, determining how long a list should stay online, and whether or not it
should be archived, can all be performed online. Authorized users are also
able to display and modify the installation parameters online.
Beta Browser
The Beta Browser offers helpful tools for your work on the screen.
_beta log|z makes locating specific fields easier by offering the following
highlighting options:
•
Colors, intensity, blinking, underscoring, reverse video
To revise or check your data, you no longer need to spend a lot of time
searching for the correct row and column. _beta log|z offers you the
following:
•
Vertical and horizontal rulers, retention of the title lines, column
exclusion
Search functions facilitate the quick location of certain text occurrences by
means of:
•
Labeling of text passages, searching for specific character strings,
indexing search character strings
Queues
_beta log|z uses a unique logical job queue concept, enabling you to keep
track of any change of job status. Jobs are checked for error conditions
and put onto the appropriate queue when they are read into _beta log|z.
The queue is displayed when a job is selected for display. Different online
retention periods may be assigned to the logical queues. The retention
periods can be specified in days or in generations.
Job processing
The job processing options are specified by job groups or sysout classes.
Jobs are organized into job groups according to their job names. In the job
group definition, online and archive retention periods are defined. As an
alternative, jobs and lists can be grouped by the sysout class in which they
are processed.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
13
Introduction
Introducing _beta log|z
Archiving
_beta log|z enables you to archive and retrieve output lists, job base
records, and z/OS syslogs with simple ISPF requests. _beta log|z archives
data on tape, disk, or optical disk.
The location of every archived list and every job base record is stored in
the _beta log|z database so that any output can be easily retrieved from
the archive volume any time - years later, if necessary. No job log will get
lost. In case of error, a job can be completely reconstructed, even if it was
running over a period of several days.
Jobs are assigned to archive pools depending on their archive retention
periods. A separate archive volume is allocated for each archive pool.
Thus, only jobs with the same archive retention period are located on one
tape. Therefore, the tape can be released earlier.
The online job base index keeps the storage location of all archived and
online job logs, making retrieval quick and convenient.
A list can be re-archived time and again as long as it is displayed online.
Files are defined dynamically, thus rendering operator intervention
unnecessary.
Dual archival
_beta log|z offers a Dual Archive Mode so that you can keep two identical
copies of your archives. Archiving to two separate files at the same time
safeguards against loss of data due to media failure (tape, disk, or optical
disk).
Data compression
All sysout lists are compressed by _beta log|z before they are written to
the spool dataset(s). Archived sysout on tape is compressed as well. By
using data compression for both archived and online lists, _beta log|z
saves up to 70 % of storage space.
Reload
Every archived list and every job base record can be reloaded with one
simple _beta log|z/ISPF command. You no longer need to handle a
manual inventory. _beta log|z takes over the search for the existing
archive volume and positions itself exactly at the beginning of the archived
list, thus reducing the search time to a minimum.
_beta log|z reloads the list under the original job base record, so that you
can quickly and efficiently print out the lists if desired.
Security
The _beta log|z security interface enables you to protect sensitive output
lists against unauthorized access. You can control access with the help of
your security system, for example RACF. You can determine who should
receive error messages, and which users should be allowed to see certain
output.
Batch utilities
_beta log|z batch utility programs enable you to manage the databases
and perform various archival and retrieval functions. Some of the _beta
log|z batch utilities can be started online. The executable JCL is
automatically generated by the system.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
14
Introduction
Logs on distributed
platforms
Introducing _beta log|z
Data centers are increasingly processing more job logs from platforms
other than z/OS (for example, SAP, Windows, Unix). _beta log|z takes full
account of this. _beta log|z expands scheduler functionality in z/OS. _beta
log|z has its basis in the z/OS system, and can collect, analyze and
archive job logs from SAP, Windows and Unix. _beta log|z fulfills the
following three main tasks:
•
To scan job output, identifying errors instantly.
Production staff have to monitor thousands of jobs daily. Having to
check the logs of each job manually would be an extremely costintensive undertaking. _beta log|z checks logs automatically, and can
alert users immediately if there are any errors. More typically, jobs are
placed in an Error queue, where production staff can select only the
incorrect jobs, view them online and analyze the error. Details of the
errors and their solutions can be attached to the job in _beta log|z for
later reference (in case the error reoccurs).
•
To provide a tool for querying and viewing job output online, without
having to hold output in the z/OS Job Entry System.
The z/OS operating system's JES system is responsible for starting
and monitoring system jobs and tasks. Output can be held in this
system and viewed using SDSF software. However, the capacity of the
JES system is limited, and at some point job output has to be deleted
from the JES. _beta log|z does this automatically, and places job
output into the _beta log|z databases and spools. Here, they are
compressed so that they require less space, and can be viewed
online. Jobs are defined to a specific job pool with definitions as to
how long a job is to be held online, whether a job is to be archived,
and if so, for how long.
•
To provide a long-term archive for job output to meet the needs of the
audit department.
Jobs are held in the _beta log|z long-term archive, where they can be
retrieved and viewed at a later date. For many (finance-related) batch
jobs there is also a legal requirement to keep the job available for
scrutiny for x years. _beta log|z can fulfill this requirement. Batch find
and recall utilities are available to search the archive for particular jobs
or events.
Enterprise-wide log
archive
_beta log|z is an enterprise-wide log archive, whether for mainframe job
logs, SAP job logs, Windows Event logs or endless logs from a firewall
system. _beta log|z also incorporates functionalities that support
production in the enterprise through IT automation.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
15
Introduction
Introducing _beta log|z
Collecting, sending and
archiving log files
The central innovation is that log files from distributed systems can be
located and sent to a central computer for archiving. Log data is typically
produced by different applications in the data center (webservers, SAP
systems, databases, etc.). Such applications are usually run on distributed
systems and produce many log files there. The EJM agents collect these
files and send them to _beta log|z for central archiving.
Configurable user
interface
With _beta log|z a specific 'look and feel' interface can be generated for
each user, giving every user their own individual layout profile for
presenting views and selecting different types of logs. This dynamic user
interface is very useful for presenting different types of logs, such as job
logs, system logs and event logs. You can define your own search and
result layouts for each job and log type.
Client-based billing
_beta log|z can be used for accounting by using the data that have been
read in. The basis for client-based billing is a special key that can be
specified when the EJM agents or SAP accounts are defined. In addition to
the client-based billing key, the SMF record will then contain information
on the file name, file size and source. Using these data, the customer can
bill the costs for _beta log|z to the appropriate departments or users.
SYSPLEX support
The SYSPLEX protocol XCF can be used to establish cross-LPAR
communication. This means that _beta log|z can be started and contacted
in dialog without knowing the actual LPAR and its associated resources.
Agent/Rule status entries
The agent/rule status entries can be displayed in _beta log|z Enterprise
User Interface.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
16
Introduction
Processing of different
log types (Windows,
Unix, SAP)
Introducing _beta log|z
Applications such as SAP write their information to endless logs. These
logs are held in a predefined storage area on disk, reserved for important
system information. Once this area has been filled, new data is written to
the beginning of the file, where it overwrites existing data. This means that
important information may be lost.
_beta log|z provides a mechanism enabling these endless logs to be
stored in sub-areas in _beta log|z, and making all of these daily partitions
available to _beta log|z in one area. This has the following advantages: no
data is lost, and the log partitions can be allocated to small storage areas
on the systems concerned.
_beta log|z processes every endless log from Windows/Unix file systems
and also SAP endless system logs.
A _beta log|z operation determines what is to be processed, for example:
•
Normal Windows/Unix logs
•
Endless Windows/Unix logs
•
Windows event logs
In addition to the various logs used by the Windows system, the
administrator also has access to event logs. These are system,
application and security logs containing important information from the
Windows system. This log format is stored in Windows in binary form
and cannot be read by normal means. These endless logs with their
important Windows system data can be read into _beta log|z, ensuring
that important information is available in a long-term archive.
•
SAP jobs (including job definitions, job logs, job spool lists, child jobs,
application logs)
•
SAP system logs
•
SAP security audit logs
•
Output from IWS (IBM Workload Scheduler) can be processed and
archived.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
17
Introduction
EJM agents
Introducing _beta log|z
•
Central administration via the BQL database
•
Central viewing of:
•
•
ONLINE status of the agents and the SAP server, agents
operating system and version
•
Advantages of processing rules: time-specific orientation, freely
selectable intervals, output selection via masks
EJM agents can process the following source data:
•
ASCII and binary text files
•
Windows Event logs, such as system logs, security logs,
application logs
•
SAP system logs
•
SAP security audit logs
•
SAP jobs (including job definitions, job logs, job spool lists, child
jobs, application logs)
•
Rule history - when which rule has been processed and with which
return code
•
Error messages are written in the log file and for every processed
rule in the database
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
18
Introduction
Structure of the documentation
Structure of the documentation
Overview
This section describes which manuals are available for _beta log|z, _beta
job|z, and related products.
_beta log|z User Guide
•
Overview of _beta log|z
•
_beta log|z online application
•
_beta log|z batch utilities
•
Glossary
•
Overview of _beta log|z
•
_beta log|z online administrator application
•
_beta log|z batch utilities
•
Glossary
•
_beta log|z installation and customization
•
Security considerations
•
Batch utilities for system maintenance
•
_beta log|z user exits
•
JES considerations
•
Operator console commands
•
_beta log|z system messages and user abend codes
•
User abend codes and product-specific return codes
•
Overview of _beta log|z console commands and online commands
•
Over view of OMS control cards
•
Overview of _beta browse commands
_beta log|z
Administrator Guide
_beta log|z Installation
and System Guide
_beta log|z
Messages and Codes
_beta log|z
Reference Card
_beta browse
Reference Card
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
19
Introduction
_beta job|z
Administrator Guide
_beta job|z Installation
and System Guide
_beta job|z Messages
and Codes
BSA Installation and
System Guide
BSA Messages and
Codes
BSA Service Manager
Manual
Structure of the documentation
•
Overview of _beta job|z
•
Explanation of the _beta job|z online application
•
Concepts, components, and structure of _beta job|z
•
EJM job instructions and syntax
•
Descriptions and examples of different types of jobs like:
•
SAP jobs and SAP-specific settings
•
File transfer jobs
•
High-frequency jobs
•
Command-line programs
•
Batch utilities
•
Workload balancing with Workload Balancer (WLB)
•
Event triggering with Extended Triggering Facility (ETF) (including
Failover and Package Control)
•
_beta job|z installation and customization
•
Checklists and step-by-step guides
•
Security considerations
•
Batch utilities for system maintenance
•
_beta job|z user exits
•
Operator console commands
•
Agent installation and customization
•
_beta job|z system messages and user abend codes
•
Open Systems messages
•
Error codes for all _beta job|z components
This manual includes the following:
•
Description of the Beta Systems Architecture (BSA) installation and
customization
•
Global system information
This manual includes the following:
•
BSA component system messages
(message ranges 8000 through 9599 and 9700 through 9999)
•
User abend codes
This manual includes the following:
•
General description of the BSA Service Manager application
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
20
Introduction
_beta report Manual
_beta smf Manual
_beta view User Guide
for _beta log|z
_beta view Installation
and System Guide
Structure of the documentation
This manual includes the following:
•
General description of the _beta report application
•
Description of _beta report commands in alphabetical order
This manual includes the following:
•
General description of the _beta smf application
•
Description of _beta smf control parameters, field descriptions and
field formats
•
Examples of use
This manual contains the following information on the additional
component _beta view:
•
Description of _beta view
•
Accessing data contained in _beta log|z via _beta view
This manual contains the following information on the additional
component _beta view:
•
Installation of _beta view
•
Customization of _beta view
•
Troubleshooting information
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
21
Introduction
What you can find in this manual
What you can find in this manual
Introduction
This chapter provides an overview of the _beta log|z features.
Leading in to _beta log|z
This chapter provides an overview of the product and the manual.
It describes the JCL modifications necessary to process jobs with _beta
log|z. You will also find a lead-in to the _beta log|z ISPF application and a
description of its menu structure.
News (Option N)
This chapter describes the usage of the news menus.
General (Option A.1)
This chapter explains the definition of layouts, job groups, and notify
groups. Layout fields, search and result layouts are described here. You
will get to know how to insert, copy, and change search and result layouts.
In addition, a table shows all default layouts used by _beta log|z.
Enterprise (Option A.2)
This chapter deals with the Enterprise definitions and its concepts.
File tailoring (Option A.3)
This chapter explains the batch and database utilities for enlarging,
reducing, renaming, reusing, and reallocating databases.
Monitor (Option A.M)
This chapter explains the display of agent rule status information, the
usage of reload requests and _beta log|z statistics.
Information on rules and its connected agents are described and how you
can clean up the agent rule status table. You can find out which rules are
planned for execution and at what time.
Archive (Option A.A)
This chapter deals with the archive concept and functions.
System (Option A.S)
This chapter explains the global system options, the special reload, and
the automatic reload of _beta log|z.
Reader (Option A.R)
This chapter describes the _beta log|z readers and the definition of sysout
classes, scan definitions, log processes, and event actions. In addition,
you can define error codes to easily find out whether or not a job has been
set to error.
Database (Option A.D)
This chapter describes the _beta log|z databases.
Batch utilities
This chapter describes all _beta log|z batch utilities. Some batch utilities
can be started from the ISPF application. For a description, see "Batch
utilities (Option 3)" in _beta log|z User Guide.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
22
Introduction
What you can find in this manual
EJM agents
This chapter explains basics about EJM agents and how to work with
them. This chapter also provides information on data types processed by
_beta log|z.
Scan definitions
This chapter contains an overview of the definitions that are provided by
_beta log|z for scanning sysout.
Questions and Answers
This chapter gives answers to some frequently asked customer questions
about _beta log|z.
Glossary of terms
The glossary explains some important terms that are used in the
documentation.
Index
The index lists keywords alphabetically to help you find information
contained in this manual.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
23
Introduction
Product names and identifiers
Product names and identifiers
Overview
Each mainframe product of Beta Systems DCI Software AG has a two-digit
numeric identifier.
_beta log|z
92 is the identifying number of _beta log|z. You will see the identifying
number in:
Product identifiers
•
Program and job names like B92DLOAD
•
LST parameters (B92_SSID)
•
LST member name (B92LSTxx)
•
System identifier in the JCL ('S=92')
Following is a list of the numeric product identifiers of our products on the
z/OS mainframe:
32 is the identifying number of _beta move.
39 is the identifying number of _beta doc|z transform.
48 is the identifying number of _beta job|z.
88 is the identifying number of _beta access.
89 is the identifying number of _beta access monitor.
91 is the identifying number of _beta check|z.
92 is the identifying number of _beta log|z.
93 is the identifying number of _beta doc|z.
97 is the identifying number of _beta doc|z plus.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
24
Introduction
Names of products
and add-ons
Product names and identifiers
Product
Predecessor (or internal name)
_beta access
Beta 88
_beta access analyze
Beta 88 RACF Drill Down Facility (Beta 88 RDF)
_beta access easy
Beta 88 Web Helpdesk (Beta 88 WHD)
_beta access monitor
Beta 89
_beta browse
Beta 23 (Beta Browse Facility)
_beta check|z
Beta 91
_beta compliance
Beta 96 Enterprise Compliance Auditor
_beta control
Enterprise Control Center (ECC)
_beta doc|z
Beta 93
_beta doc|z plus
Beta 93 Fast Retrieval (Beta 93 FR) and Beta 97
_beta doc|z transform
Beta 93 Document Transformer (Beta 93 DT), Beta 93
Data Privacy (Beta 93 DP), and Beta 39
_beta job|z
Beta 92 Enterprise Job Manager (EJM) and Beta 48
_beta job|z agent
EJM agent
_beta log|z
Beta 92
_beta move
Beta 32
_beta report
BSA Report Generator
_beta smf
Beta Log Formatter and Beta SMF Reporter
_beta view
Discovery Web Enabler (DWE) and
Beta Web Enabler (BWE)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
25
Introduction
Conventions used in this manual
Conventions used in this manual
Sideheads
The manuals of _beta log|z contain different types of information:
•
Task-based information, for example, procedures containing a
sequence of numbered steps
•
Reference information, for example, panel and parameter descriptions
The sideheads in the margin help you locate the required information
quickly.
Keys
All keys are displayed in the manual in uppercase letters. Function keys
(also called program function keys) are referred to as PFn, for example:
Use PF8 to scroll downwards and PF7 to scroll upwards.
Use PF11 to scroll to the right and PF10 to scroll to the left.
Panel navigation
All procedures and panel descriptions use the "Primary Selection Menu"
as point of reference. For example:
To display file rule output:
•
From the "Primary Selection Menu", select option O, then
option 1.
You don't have to enter these options in separate steps and you don't have
to return to the "Primary Selection Menu" all the time. Do the following to
access the "Select Jobs to be printed" panel in one step:
Enter ...
in the command line to call this panel from ...
3.1
the _beta log|z Primary Selection Menu
=3.1
any _beta log|z panel
Note: The ISPF jump function is not available under
VDF.
Panels
Panels are displayed in a monospaced font and framed in a box. As a rule,
the entire panel is displayed.
The following applies to the displayed panels:
JCL
•
The padding character for required fields is the dot ( . ) and the
padding character for optional fields is the underline character ( _ ).
•
The panel ID is displayed in the top-left corner of the panel. (You can
turn this display on or off using the primary command PANELID.)
JCL is displayed in the manual in a small monospaced font and framed in
a dashed box. Lower case italic characters are used for generic cards and
variables.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
26
Introduction
Dataset names
Conventions used in this manual
The manual uses the high-level qualifier BETA for libraries that are
typically shared by BSA and the Beta Systems DCI products. For example,
BETA.PARMLIB is used to refer to the library that contains the LST
members.
The manual uses the high-level qualifier BETA92 for _beta log|z libraries
and databases. BSA is used for libraries of Beta Systems Architecture. For
example, BETA92.LOAD is used for the _beta log|z load module library,
and BSA.LOAD is used for the BSA load module library.
Libraries and databases at your data center will most likely have different
names. Make sure that your JCL contains uses correct high-level
qualifiers, which comply to the conventions used at your data center.
Listings and reports
Like JCL, listings and reports are also displayed in a small monospaced
font and framed in a dashed box.
Console commands
Console commands are displayed in the manual in a large monospaced
font. For example:
To start the product STC, enter the following console command:
S stcname
where stcname must be replaced with the name of the product
started task.
Primary commands
Primary commands are displayed in the manual in uppercase letters. To
execute a primary command, type the primary command in the command
line and press ENTER.
Many primary commands have a long form and one or several short forms.
Instructions in this manual use the long form of the primary command and
include short forms in parentheses. For example:
Command
Description
PAGEBREAK ON
(PBR ON)
Show the bottom marker of each page.
Generic names and variables are displayed in lowercase italic letters.
Example: To display a specific hit page in the Browser, enter the following
primary command (long or short form):
Command
Description
PAGE nnn
(P nnn)
Position to the specified page
(nnn = page number).
where nnn must be replaced with the desired page number.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
27
Introduction
Line commands
Conventions used in this manual
Line commands are displayed in the manual in bold uppercase letters.
Line commands consist of one, two, or three characters. The manual
shows available line commands like this:
A
Description of line command A
AB
Description of line command AB
To execute a line command, type the line command in the Sel column of
the table in front of the desired entry and press ENTER.
The available line commands are displayed in ISPF tables underneath the
panel title. Depending on the table type, you can switch this display off by
entering Extended help = No in your profile (option P.2).
You can also switch the display on and off with the primary commands
PROF HL OFF and PROF HL ON.
Keyword and positional
parameters
Keyword parameters and positional parameters are displayed in the
manual in a monospaced font using the following syntax:
PARM='ssid[,TRACE=Y|N]'
ssid is a required positional parameter where ssid refers to the subsystem
ID. The subsequent keyword parameter is optional, which is indicated by
square brackets. A vertical bar separates alternative values. Keywords are
displayed in uppercase letters.
Double-dot operator
The double-dot operator between integers indicates a range of integer
values. For example, 2..5 expands to a list containing the values 2, 3, 4,
and 5.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
28
Introduction
What is new in _beta log|z
What is new in _beta log|z
Overview
Following is a list of the new functions and features and other product
changes.
V7R2-02 (POM8137): New functions in _beta log|z
New functions
Following is a list of the new functions and fixes for _beta log|z:
•
Support of the favid parameter added to the Favorite fields in the
Web Link Settings under option A.S.3
For example, if the ID of the favorite in _beta view is B92P, enter the
following in the Favorite fields:
Job Link Favorite
List Link Favorite
===> favid=B92P&target=list
===> favid=B92P
Earlier versions of _beta log|z always expected values with the favkey
syntax, for example, fav_B92Prole, and added the favkey parameter
automatically when generating links.
The favkey parameter is deprecated in _beta log|z and _beta view.
Please switch to favid= instead.
•
Two new scan definitions to allow syslog processing from multiple
JES MAS
ScanID TargetID Chain name ScannedList A/N Description
ID in title
2505
800/163
JES200I
*
N
Scan SMF ID for job ID SYSLxxxx
216
2506
800/163
JES200I
*
N
Scan SMF ID for job ID SYSLxxxx
217
The new scan definitions ensure that generated keys are unique at all
times when _beta log|z processes z/OS syslogs from multiple
JES spools.
When a z/OS syslog is read into _beta log|z, the new scan definitions
extract the SMF ID and set the job ID to SYSLxxxx, where xxxx is the
4-digit SMF ID of the z/OS image, for example, SYSLBT50.
The new scan definitions are inactive by default. Enable them
manually if needed.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
29
Introduction
What is new in _beta log|z
•
New LST parameter B92_JIT_SORT = DSID | STEP
The new LST parameter B92_JIT_SORT can be used to disable the
special sort in the "Job Information Table" introduced with _beta log|z
V7R1 for spinned lists.
Parameter name
Value
Description
Opt./Req. Default
B92_JIT_SORT
DSID |
STEP
Determines the sort order of lists in the "Job
Information Table"
Optional
DSID
STEP
Lists are arranged according to
dataset ID
STEP Lists with identical stepname/procstep/
ddname are arranged next to one
another in the table to hold spinned lists
together during display and print
•
Throughput of the event router has been increased
Event buffer overflow (OMS3010E EVENT BUFFER IS FULL) is now
less likely because events are processed faster.
V7R2-01 (POM8073): New functions in _beta log|z
New functions
Following is a list of the new functions and fixes for _beta log|z:
•
Event search with multiple jobnames/rulenames
Up to six jobname/rulename fields can now be defined in an event
search layout (Option A.1.1.2).
•
Dynamic deletion of empty GAR files
It is now possible to delete empty GAR files. You can tailor a GDEL job
for this task under option A.3.2.
•
Improved fault tolerance of mailing in case of SMTP connect error
The _beta log|z STC informs on SMTP connect errors via events and
messages. The STC retries the connect at regular intervals. Mail will
be sent when the SMTP server becomes available again.
•
Scanning now supports date formats and time formats without
separator:
New date formats: YYYYMMDD and YYMMDD
Available for target IDs: 1 (start date), 3 (end date), 164 (submit date)
New time format: HHMMSS and HHMM
Available for target IDs: 2 (start time), 4 (end time), 165 (submit time)
•
B92ARPRI: Expiration date in OMSPRINT
The batch utility B92ARPRI now provides the expiration date of each
archive dataset included in the OMSPRINT report.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
30
Introduction
What is new in _beta log|z
V7R2-00 (POM8004): New functions in _beta log|z
Overview
The following new functions of V7R2-00 affect _beta log|z.
Reader statistics
_beta log|z now saves statistical data on the usage of JES readers and
OSY readers in the new RDRSTATS table. Information like the number of
jobs, lists and lines and the amount of MB processed by each reader is
stored in this table. Each reader writes its values when the first job in a
new hour is processed and at shutdown.
The reader statistics can be displayed in _beta control. It is also possible
to retrieve this information from the database via the batch utility
B92BCAPI and the REXX interface (BRXOMS).
The cleanup up of reader statistics in RDRSTATS is handled by the
B92CLARS batch utility, which also cleans up agent rule status information
in the ARSTATUS table and _beta log|z statistics in the B92STATS table.
Deletion from the RDRSTATS table is controlled via the new RDR_DAYS
parameter. The minimum value of this parameter is 30 days.
Deletion from the B92STATS table is controlled via the STAT_DAYS
parameter. The minimum value of this parameter has been increased from
30 to 720 days, which means that the statistical information of the last two
years is now exempt from deletion.
Note: Numbers in RDRSTATS don't include data read in from the recovery
dataset during STC restart. Some numbers from slave STCs will also not
be included if the master STC is unavailable when slaves are stopped.
Reader statistics should therefore not be used for accounting purposes.
Command API
The command API as known from _beta job|z has been implemented in
_beta log|z.
The command API is used internally by _beta log|z functions, but it is also
used by _beta control, the REXX interface (BRXOMS), and the batch utility
B92BCAPI.
Two new LST parameters are available for controlling the command API:
•
B92_CMDCL_ENCODING = codepage_number
Host codepage of the _beta log|z system (Default: 1141)
•
B92_CMDCL_TRACE = YES | NO
Controls tracing (Default: NO)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
31
Introduction
Mailing
What is new in _beta log|z
Character conversion in _beta log|z mailing is now completely based on
the iconv installation available on the z/OS host. You can use the shell
command iconv -l to list which codepages are available in your
environment, for example, with the help of a BPXBATCH job:
jobcard
//UNIX
EXEC PGM=BPXBATCH,REGION=8M
//STDERR
DD SYSOUT=*
//STDOUT
DD SYSOUT=*
//STDPARM DD *
sh iconv -l
The default encoding as specified in the global options (Option A.S.3)
continues to be used, but now prefers standard IBM codepage identifiers
like IBM-037 or IBM-273. The field name in the panel has been renamed
from Translation Table to Codepage in this context. Legacy values in this
field like CECP037 and CECP273 continue to be supported and are
converted internally to the appropriate IBM identifier. DEFAULT and blank
are also converted to IBM-273.
Other changes
•
The REXX interface (BRXOMS) can be used to retrieve reader
statistics from the database via REXX script. The REXX interface can
also be used for stopping and starting readers and for monitoring
reader status.
•
The batch utility B92BCAPI can be used to retrieve information such
as usage data and reader statistics in batch mode.
•
The new target field ID 196 can be used for scanning the numeric
dataset ID (max. 8 digits), which determines the order in which logs
are displayed in the job information table.
IDs must be unique per each job. Duplicate IDs are automatically
corrected during reader processing.
•
The maximum length of the long user name has been increased from
12 to 64.
•
The maximum length of the line count has been increased in external
display from 7 to 10 digits.
This change affects the online display, but also the OMSPRINT reports
of B92BFJBR, B92MUPDT, B92PRINT, and B92SENDL.
•
UXSIN=B02UXSIN is now tailored in the B92SSIxx member for
initialization because B02UXSIN is required for login ports as of
BSA level 1771-03.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
32
Introduction
What is new in _beta log|z
V7R1-04 (POM7667): New functions in _beta log|z
New functions
Following is a list of the new functions for _beta log|z:
•
B92UXSEC/B92UXSE4
A new function code (105) has been added to enable BrowseAll for all
lists that a user is authorized to access if authorization for some lists is
lacking (based on READ access for B92.ssid.BRS.jobname.ddname).
•
Reader recovery dataset
The reader recovery datasets are now checked when the subsystem
(reader router) or readers are started. When a version mismatch is
detected, the recovery dataset is automatically initialized for the
current product version.
Previously, recovery datasets had to be deleted manually in case of
version mismatch to prevent STC abends.
•
New trace options in OSY reader
Parameter name
Value
Description
Opt./Req. Default
B92_OSY_RDR_TRACE_
AGENT
name, * or
blank
Set to name or * to activate OSY reader tracing
for one or all agents. blank deactivates OSY
reader tracing.
Optional
blank
Use B92_OSY_RDR_TRACE_ALL, _HDR etc.
to specify which information should be traced.
B92_OSY_RDR_TRACE_
ALL
B92_OSY_RDR_TRACE_
HDR
B92_OSY_RDR_TRACE_
HDRF
B92_OSY_RDR_TRACE_
CMD
YES | NO
Determines which information should be traced if Optional
B92_OSY_RDR_TRACE_AGENT is not blank.
OSY reader timing trace is always for all agents
and included in _ALL, but can also be activated
and deactivated independently via B92_OSY_
RDR_TRACE_TIMING.
NO
Set the trace parameters dynamically when
instructed to do so by Beta Systems support.
Specify what to trace first and then activate the
trace via B92_OSY_RDR_TRACE_AGENT.
Changes take effect at the next OSY reader
wakeup.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
33
Introduction
What is new in _beta log|z
V7R1-03 (POM7635): New functions in _beta log|z
New functions
•
Triggering e-mail via DD MAILOUT
It is possible to trigger the sending of e-mail by including a dataset with
appropriate instructions under the DD name MAILOUT in your job
step.
You can include _beta view links to any log of the corresponding job
(except DD MAILOUT) in the generated e-mail message or you can
send the job logs as attachment.
For more information, see "Triggering e-mail via DD MAILOUT" on
page 339 in _beta log|z Administrator Guide.
•
LST parameter B92_DAILY_PARLOCK = NO | YES (default)
By default, parallel execution of B92CLLST and B92ARSEC is
prevented via enqueue for the same ssid within the sysplex. If the
same ssid is used for separate _beta log|z systems on different LPARs
in your sysplex, you can prevent parallel execution check by coding
B92_DAILY_PARLOCK=NO. If you do this, you have to use other
methods to prevent parallel execution of B92CLLST and B92ARSEC
for the same _beta log|z system on the individual LPAR.
V7R1-02 (POM7588): New functions in _beta log|z
New functions
•
A new function code (104) has been added to the security exit to
protect the insert/update/delete of event action definitions
(Option A.R.6). Required authorization: UPDATE access for
B92.ssid.SYS.
•
As of _beta browse (Beta 23) V7R1-03, you can control whether the
FINDINDEX(FX) command should honor the Find line limit specified
in the user profile (Browser options). This is done via the LST
parameter B92_LIMIT_FX_COMMAND = YES|NO. The default is NO,
which means that the limit does not apply to FINDINDEX(FX).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
34
Introduction
What is new in _beta log|z
V7R1-01 (POM7562): New functions in _beta log|z
New functions
•
Refresh (REF) added to "Reload Request Selection Table"
(Option A.M.2)
•
DD name can now be changed during scanning (Target field ID 43)
This function can be used, for example, to restrict access to certain
lists based on content. To prevent normal users from accessing lists
with special content, use an appropriate scan definition that assigns a
special DD name (for example, SECURE) upon finding a specific
string. If you are using B92UXSE4 as security exit, you can then use
the RACF profile B92.ssid.BRS.*.SECURE to protect access to all logs
of this name.
V7R1-00 (NONE): New functions in _beta log|z
Overview
The following new functions of V7R1-00 affect _beta log|z.
New name
Beta 92 is now called _beta log|z.
See "Product names and identifiers" on page 24 for a list of the names of
Beta Systems DCI products.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
35
Introduction
Health checker
What is new in _beta log|z
Several functions have been added to _beta log|z to help detect potential
problems caused by inappropriate definitions and parameters. These
functions have been summarized under the term health checker and are
described below.
The health checker can be activated/deactivated via the LST parameter
B92_HEALTH_CHECK = ON|OFF. The default is ON.
The health checker writes a summary log to DD JESMSGLG of the started
task. The messages are described below. More detailed information is
written to DD B92HC000 if this DD statement is present in your _beta log|z
started task procedure.
Database verified at STC start
B92DBVER is now automatically executed when a _beta log|z master STC
is started. The result of the database verification is written to the STC logs
(DD JESMSGLG and DD B92HC000) and to event table EVT00.
•
Messages written to JESMSGLG/B92HC000 if okay
OMS5510I DATABASE IS UP TO DATE
•
Messages written to JESMSGLG/B92HC000 if not okay
OMS5511E DATABASE IS NOT UP TO DATE
OMS5512E DB UPDATE (member – location) IS NOT INSTALLED
Message OMS5512E with information on the member that contains
the database update and the location of this update is repeated for
each update that is missing.
•
Additional messages written to DD B92HC000
OMS5513I DB update (dbtable/dbfield) for Vvrm (ptf_level) bsa_level installed
OMS5513E DB update (dbtable/dbfield) for Vvrm (ptf_level) bsa_level NOT installed (member – location)
•
Events in EVT00 (Event ID 9255) in accordance with messages
See "Health check event" below.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
36
Introduction
What is new in _beta log|z
LST parameter check at STC start
The plausibility of selected LST parameters is checked when the _beta
log|z STC is started. The result of the LST parameter check is written to
the STC logs (DD JESMSGLG and DD B92HC000) and to event table
EVT00.
•
Message written to JESMSGLG/B92HC000 if okay
OMS5520I BETA 92 PARAMETERS COMPLY WITH BETA RECOMMENDATIONS
•
Messages written to JESMSGLG/B92HC000 if not okay
OMS5521W BETA 92 PARAMETERS INCONSISTENT WITH BETA RECOMMENDATIONS
An additional OMS5522W message is written for each LST parameter
that doesn't comply with Beta Systems recommendations:
OMS5522W 001 BQL_SHARE_OPTION=ALL ==> BQL SPEEDMASTER DISABLED
OMS5522W 002 B92_RDR_MULTI_INSERT=1 ==> MULTI-INSERT DISABLED
•
Events in EVT00 (Event ID 9255) in accordance with messages
See "Health check event" below.
Health check event
Event ID (Severity) Description
9255 (I,W,E)
Activation: B92_HEALTH_CHECK = ON (Default)
Severity and event text depend on action and result
Database verification okay at STC start
I: DATABASE IS UP TO DATE
Database verification not okay at STC start
E: DATABASE IS NOT UP TO DATE
One additional event is created for each database update that is missing.
E: DB UPDATE (member – location) IS NOT INSTALLED
LST parameter check okay at STC start
I: BETA 92 PARAMETERS COMPLY WITH BETA RECOMMENDATIONS
Potential LST parameter check warnings at STC start
W: BETA 92 PARAMETERS INCONSISTENT WITH BETA RECOMMENDATIONS
One additional event is created for each offending LST parameter.
W: 001 BQL_SHARE_OPTION=ALL ==> BQL SPEEDMASTER DISABLED
W: 002 B92_RDR_MULTI_INSERT=1 ==> MULTI-INSERT DISABLED
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
37
Introduction
What is new in _beta log|z
Scan definition handling
The handling of the standard scan definitions (also called Beta-defined
scan definitions) has been changed. The new handling ensures that the
scan definitions are always kept up-to-date at all _beta log|z installations,
which will avoid the occurrence of problems caused by outdated scan
definitions.
The new handling is as follows:
•
The standard scan definitions are included in the reader program.
•
The definitions in the SCN table are checked and updated at every
start of the _beta log|z master STC. The result of the comparison is
logged in the JESMSGLG of the STC.
OMS1109I SCAN DEFINITIONS UPDATED: ALL ARE ALREADY UP TO DATE
OMS1109I SCAN DEFINITIONS UPDATED: [n INSERT[S]] [n DELETE[S] [n UPDATE[S]]
OMS1109I SCAN DEFINITIONS UPDATED: SKIPPED IN SLAVE STC(ssid)
•
Users can display the standard scan definitions under option A.R.3.
They can activate and deactivate the standard scan definitions, but
they cannot delete or modify them. It is also possible to toggle the test
status of standard scan definitions.
Automatic scan definition update does not change the current status of
existing scan definitions (Active/Inactive/Test). The last change
information of definitions (CUSER, CDATE, CTIME) whose status
deviates from the standard is also preserved.
This change affects all definitions within the scan ID range 1000..9999 with
the following exceptions:
•
Scan ID range 6000..6299 (Dataset reader)
•
Scan ID range 7000..7199 (EIF)
Customer-specific scan definitions are not affected.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
38
Introduction
Spool model check
What is new in _beta log|z
A spool model check is now automatically carried out at STC start and
following the allocation and formatting of a new spool file. The result of the
spool model check is written to the JESMSGLG of the STC and to event
table EVT00. The severity of the message and the event depends on the
result of the spool model check.
JESMSGLG
The following message is written to the JESMSGLG at STC start and upon
the successful formatting of a new spool file:
OMS9546I/W SPOOL FILES:n
SPOOL MODELS:n
TOTAL CYLINDERS OF SPOOL MODELS:n
The severity is I if the number of spool models remaining is okay.
The severity is W if the number is too low.
Event
Following is a description of the event that is generated following the
formatting of a new spool file:
Event ID (Severity) Description
9300 (I,W,E)
Automatic spool formatting event (BSA)
Activation: Always active
Severity and event text depend on result; warning threshold defined via
LST parameter BQL_SPOOLCHECK_MODEL=min
Spool formatting successful
I: NO. OF SPOOL MODELS(n) CYL(cyl_models) SPOOL FMT OK
DSN(dsname) CYL(cyl_ds)
Spool formatting successful, number of models remaining too low
W: NO. OF SPOOL MODELS(n) BELOW THRESHOLD (min)
CYL(cyl_models) SPOOL FMT OK DSN(dsname) CYL(cyl_ds)
Spool formatting failed
E: SPOOL FMT FAILED DSN(dsname) RC(rc) CYL(cyl_ds) REMAINING
MODELS(n) CYL(cyl_models)
SSL-secured mail
You can now use SSL/TLS to secure the communication between the
_beta log|z started task and the SMTP server when sending e-mail.
Support of SSL/TLS is based on the use of AT-TLS.
For more information, see "SSL-secured communication with SMTP
server" in _beta log|z Installation and System Guide.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
39
Introduction
View JESJCLIN
What is new in _beta log|z
It is now possible to use line command V directly in the "Job Selection
Table" for opening JESJCLIN in the editor, for example, to resubmit a job
with or without modification.
Line command V now works like this:
•
All lists are opened as one list in the editor if the job is a non-z/OS job.
•
JESJCLIN is opened by default in the editor if the job is a z/OS job.
Change the value in the new View Job Mode field in your user profile
(Option P.3) from JESJCLIN to ALL if you want line command V to
open all lists of a z/OS job.
Spinned lists
Two enhancements affect the display and handling of spinned lists in the
"Job Information Table":
•
Entering line command B in front of a spinned list will open all lists of
the same name concatenated as one list in the Beta Browser.
•
The sort order of spinned lists is now determined by their name (DD
name/stepname/procstep). This means that lists of the same name are
shown next to one another. Previously, the sort order was determined
by the DSID.
Note on B92PRINT: Online spinned lists are sorted by name during
printing/mailing. Offline spinned lists are printed/mailed in the order in
which they are read from the archive dataset.
New layouts for _beta
view
_beta log|z now provides a new set of layout search/result definitions that
has been specially adapted for _beta view.
The names of the 3270 layouts begin with BETA_ and the names of the
complementary _beta view layouts begin with VIEW_.
SMF records
Support of extended IBM header
As of z/OS 2.3, SMF subtype records can be written with the standard IBM
header (24 bytes) or with the extended IBM header (56 bytes). The offsets
of the fields following the IBM header depend on which type is used.
The BETA92.SAMPLIB therefore includes a set of record descriptions with
relative offsets that can be used with both standard IBM header and
extended IBM header. An alternative set of members with absolute offsets
for IBM standard header is also included.
The writing of standard or extended IBM header is controlled via the LST
parameter B92_SMFREC_VERSION:
0
Standard IBM header (default)
1
Extended IBM header
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
40
Introduction
Others
What is new in _beta log|z
•
Option 1: The Runtime field has been extended from 8 digits
(hh:mm:ss) to 10 digits (hhhh:mm:ss) in the "Job Select Table" and in
the "Job Information Table".
This change does not affect the selection tables of the reload options,
where the maximum length continues to be 8 digits. The maximum
value 99:59:59 in the reload selection tables means that the runtime
was 99:59:59 or longer.
•
Support of 8-digit job execution class (Important: Existing recovery
dataset must be deleted during the update of an existing Beta 92
system to V7R1.)
•
Online Retention Period (in days) for Job Info added to Job Group
Definition (Option A.1.2)
Value in JobInfo column overrides Yes/No of Only keep Job Base
Record from the global options (Option A.S.3)
Earlier changes
•
The LST parameter B92_ADM_LIST_ACCESS is now also honored by
B92SSRCH.
•
The RFF batch utilities of _beta log|z require a minimum region size of
64 MB.
For a list of earlier changes, see Beta 92/Beta 92 EJM V6R2 Release
Notes and Update Instructions.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
41
Leading in to _beta log|z
In this chapter
Leading in to _beta log|z
In this chapter
Topic
Page
_beta log|z product components .............................................................. 43
MSGCLASS and job output lists............................................................... 44
OMS control cards .................................................................................... 47
ISPF application........................................................................................ 52
Basic functions ...................................................................................... 54
Primary Selection Menu........................................................................ 55
Administration Selection Menu ............................................................. 56
Panel structure.......................................................................................... 57
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
42
Leading in to _beta log|z
_beta log|z product components
_beta log|z product components
Started task (STC)
The _beta log|z started task (STC) uses the standard z/OS subsystem
interface (SSI) to communicate with JES2 or JES3 to provide _beta log|z
with job logs and sysout lists. The z/OS external writer uses the same
interface to JES. The started task runs in its own z/OS address space and
functions without operator commands.
The started task should remain continuously active in order to process jobs
from the JES spool. If the started task is not active, the jobs remain on the
JES spool until the _beta log|z started task is started again.
The started task can process up to eight JES output classes.
ISPF application
The _beta log|z ISPF application is a set of online panels, tutorials,
messages, and accompanying programs for the IBM licensed product
ISPF and ISPF/PDF. The ISPF application provides you with a
standardized, interactive method of viewing, checking, printing, and
retrieving job logs and job output lists.
Databases
All databases are VSAM ESDS datasets. All descriptions of fields, tables
and keys are stored in the definition file BETA92.DB.DEF.
Mirror databases
The use of mirror databases is optional. File mirroring provides a high level
of reliability and quick recovery in case of DASD media failures. The mirror
files are maintained as parallel copies of the original files.
Batch utilities
_beta log|z offers a number of batch utilities for your daily work. They allow
you to perform a number of activities: archiving sysout lists and job
records, printing one or more jobs, reloading job records, and deleting lists.
Most batch utilities can be started online. The executable JCL is
automatically generated by the system.
Usage based pricing
Please note that every job and every list read into _beta log|z is counted
separately for UBP (usage based pricing). In particular, this applies to all of
the output read into _beta log|z by the EJM agents.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
43
Leading in to _beta log|z
MSGCLASS and job output lists
MSGCLASS and job output lists
Overview
The JCL MSGCLASS and other JCL parameters control which jobs and
which lists are to be processed and stored by _beta log|z.
Message class
JES2 and JES3 store all job logs in a JES spool dataset under the sysout
class specified in the MSGCLASS parameter of the job card, in the
following example message class P:
+-----------------------------------------------+
|//MYJOB
JOB acct,name,MSGCLASS=P
|
|...
|
+-----------------------------------------------+
If you do not code this parameter on your job card, JES uses an
installation default, usually output class A.
Job output names
The _beta log|z "Job Information Table" displays the job output.
Lists are the output of a job. Each list has a name associated with it. Lists
can be, for example, JES lists as well as logs.
JES lists
JES places the following lists into the specified output class:
1. JESJCLIN contains the JCL processed by the job.
2. JESMSGLG contains JES statistics and messages. If the job fails in a
JES2 system, the JES messages will not appear. Instead, you'll see a
list with the name FAILED. This can happen if your job card has an
invalid JES parameter.
3. JESJCL contains the JCL of the job you submitted. It may also contain
procedures used in the job.
4. JESYSMSG contains the z/OS allocation and deallocation messages,
the step condition codes, and other messages from your program and
from installation exits.
Message level
The z/OS job card parameter MSGLEVEL determines the amount of
information you see in the JES sysout lists. It should always be coded or
defaulted to MSGLEVEL=(1,1) for output classes processed by _beta
log|z.
Refer to the IBM z/OS JCL manual if you are not sure how to code the
MSGLEVEL parameter.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
44
Leading in to _beta log|z
Sysout class
MSGCLASS and job output lists
Your job produces other sysout lists when you code SYSOUT in a
DD statement in your JCL. The SYSOUT keyword specifies an output
class. When this output class is processed by the _beta log|z started task,
_beta log|z takes the sysout list from the JES spool and puts it in its online
spool.
+-----------------------------------------------+
|//MYJOB
JOB acct,name,MSGCLASS=P
|
|//STEP1
EXEC PGM=TEST
|
|//SYSPRINT DD SYSOUT=P
|
+-----------------------------------------------+
If you code SYSOUT=* on a DD statement, the sysout list gets the same
output class as the message class for the job. _beta log|z takes the sysout
list from the JES spool and places it in its online spool if the message class
of the job is processed by _beta log|z.
+-----------------------------------------------+
|//MYJOB
JOB acct,name,MSGCLASS=P
|
|//STEP1
EXEC PGM=TEST
|
|//SYSPRINT DD SYSOUT=*
|
+-----------------------------------------------+
If you do not want _beta log|z to process all of your sysout lists, use a JES
print sysout class in the DD statement.
Note: The maximum LRECL for lists processed by _beta log|z is 29000.
Copying sysout to more
than one class
You can use the OUTPUT JCL card if you want to send output to more
than one class.
For example, if you want to send one copy of your sysout list to a JES
printer (here: message class A) and another copy to _beta log|z (here:
message class P):
+--------------------------------------------------+
|//MYJOB
JOB acct,name,MSGCLASS=P
|
|//PRINT
OUTPUT CLASS=A
|
|//BETA
OUTPUT CLASS=P
|
|//STEP1
EXEC PGM=REPORT
|
|//REPORT1 DD SYSOUT=(,),OUTPUT=(*.PRINT,*.BETA) |
+--------------------------------------------------+
In this example, the message class output of the job and a copy of the
sysout list created by the DD statement REPORT1 go into _beta log|z. In
addition, JES prints a second copy of REPORT1.
Note: You can always use _beta log|z to print the lists or parts of lists
afterwards.
The z/OS OUTPUT JCL statement offers many more possibilities. For
further information, read the IBM z/OS JCL manual.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
45
Leading in to _beta log|z
Processing sysout
without JES lists
MSGCLASS and job output lists
You can send sysout lists of your job to _beta log|z without the JES lists,
but this is not recommended.
_beta log|z retrieves part of its job information from the scanning of the
JES lists, for example, information on the steps that ran and their condition
codes or ABEND codes. _beta log|z is unable to detect errors indicated in
the job logs if the JES lists are not processed by _beta log|z.
In the following example, the list produced by the DD statement REPORT1
is sent to a message class that is processed by _beta log|z, but the JES
lists are sent to a different message class. The job and its list will be
available in _beta log|z, but the information available in the "Job
Information Table" will be incomplete.
+-----------------------------------------------+
|//MYJOB
JOB acct,name,MSGCLASS=A
|
|//STEP1
EXEC PGM=REPORT
|
|//REPORT1 DD SYSOUT=P
|
+-----------------------------------------------+
z/OS syslog output
The z/OS system log dataset contains a record of (almost) everything that
happens in your system. Data center staff often use the z/OS syslog to see
what happened to a particular job or to answer user questions.
We recommend that you read the syslog into _beta log|z and let it be
automatically archived by _beta log|z. Users can browse the syslog from
the online spool while the syslog is online, or they can reload it from the
archive.
For information on syslog processing, see "z/OS syslog" in _beta log|z
Installation and System Guide.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
46
Leading in to _beta log|z
OMS control cards
OMS control cards
Overview
OMS control cards direct the flow of information and control what the
program does with the input.
OMS control cards are typically inserted directly following the job card.
Syntax
An OMS control card is coded like a normal JCL comment card and looks
like this:
//*OMS keyword
keyword determines which action is triggered. Some keywords have
additional parameters, for example:
//*OMS keyword=value
-OR//*OMS keyword additional text
Diagnostic messages
By default, each //*OMS keyword in the JCL leads to the generation of a
job message record, which are displayed in the diagnostic messages
section of the "Job Information Table". This means that you can use
//*OMS without a keyword to insert comments, for example:
PE92BR20 -------------------------------------------------- Row
1 of
18
Command ===> ________________________________________________ Scroll ===> PAGE
Job Information Table REJ#§DMP (J0047188)
Submitted 24.10.2017 at 15:33:51 by REINH1
Started
24.10.2017 at 15:33:51 in class A on system BETA
Ended
24.10.2017 at 15:33:53
Position:
N - Note
M - Message
S - Step
L - List
S - Browse a list
K - Toggle keep status
V - View a list
X - Toggle nokeep status
B - Browse spinned list A - Toggle re-archive
X - Ext.Info
O - IWS
P,M - Print/Mail a list
R,U - Reload a list
T - Call Scan Test
Message
//*OMS HICC 16
//*OMS CALL SYSPROG IF THERE ARE ANY PROBLEMS WITH THIS JOB
//*OMS USE QUICK DIAL 123
------------------------------------------------------------------------------Sel Stepname Procstep Errortxt CC
CPU-Time
SRB-Time Private High Prv
DELETE
0 0:00:00.02 0:00:00.00
244 K
40 K
DUMP1
0 0:00:00.01 0:00:00.00
252 K
72 K
DUMP2
0 0:00:00.11 0:00:00.02
252 K
72 K
//*OMS SAVE
You can use the SAVE keyword to instruct _beta log|z to archive this job.
You can use this keyword to override standard processing, for example, if
the output class of your job has been defined as a NOSAVE class. The
lists and the job information will be archived according to the rules defined
by your administrator.
+---------------------------------------------------------------------+
|//MYJOB
JOB acct,name,MSGCLASS=P
|
|//*OMS
SAVE
|
|//STEP1
EXEC PGM=REPORT
|
|//REPORT1 DD SYSOUT=*
|
+---------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
47
Leading in to _beta log|z
//*OMS NOSAVE
OMS control cards
Use the NOSAVE keyword to instruct _beta log|z not to archive this job.
You can use this keyword to override standard processing, for example, if
the output class of your job has been defined as a SAVE class. When the
online retention period of your job has expired, the cleanup batch utility
deletes the lists and the job information.
+---------------------------------------------------------------------+
|//MYJOB
JOB acct,name,MSGCLASS=P
|
|//*OMS
NOSAVE
|
|//STEP1
EXEC PGM=REPORT
|
|//REPORT1 DD SYSOUT=*
|
+---------------------------------------------------------------------+
//*OMS NET
You can use the NET keyword to specify the name of a job net as a kind of
pre-selection criterion (max. 8 characters).
When the name of a net is entered in the Job Select panel, all jobs that
belong to that net (in addition to any other selection criteria previously
indicated) will be selected and displayed.
Notes for JES3 users
JES3 users are already familiar with job nets. You do not need to use this
card if the job is already a member of a JES3 job net. If there is a //*NET
and an //*OMS NET card in the JCL, _beta log|z takes the net name for
the job from the last card present.
Notes for JES2 users
JES2 does not offer job nets. JES2 users can use this _beta log|z control
card to assign a job net name to a series of related jobs. For example, the
daily backup jobs could all have the following _beta log|z control card:
//*OMS
NET=MYNET
In the _beta log|z Job Select panel, the //*OMS NET card may be used
as an additional preselection criterion; this will reduce the number of lists
that are displayed. The //*OMS NET control card does not affect job run.
Using as department identifier
An additional reason for using the //*OMS NET control card can be to
assign a department identifier to the job. This card can be automatically
inserted into a job via the submit exit. You can then limit access to the job
on the basis of the department identifier in the _beta log|z user security
exit.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
48
Leading in to _beta log|z
//*OMS HICC
OMS control cards
Use the HICC keyword to specify the highest acceptable condition code for
a job. _beta log|z will not place the job onto the Error queue if the return
code is lower than or equal to the specified value.
+---------------------------------------------------------------------+
|//MYJOB
JOB acct,name,MSGCLASS=P
|
|//*OMS
HICC=8
|
|//STEP1
EXEC PGM=REPORT
|
|//REPORT1 DD SYSOUT=*
|
+---------------------------------------------------------------------+
The highest acceptable condition code of the _beta log|z subsystem is
determined by the value of Error Code Lowest in the subsystem options
(option A.S.2). You can use the HICC card to increase the highest
acceptable condition code for individual jobs, but you cannot reduce it. The
HICC card will have no effect if the coded value is less than Error Code
Lowest.
If NO EVALUATION message occurs
The following job message may be displayed in the "Job Information
Table" under certain conditions:
NO EVALUATION OF //*OMS HICC=nn IF PRESENT IN JCL
This message informs you that this job was processed using the standard
condition code handling of the _beta log|z system. The HICC keyword, if
coded in the JCL, was not evaluated. For more information, see the
description of the accompanying message OMS1191I in _beta log|z
Messages and Codes.
//*OMS USER
Use the USER keyword to assign a job to a user at read-in time.
+---------------------------------------------------------------------+
|//MYJOB
JOB acct,name,MSGCLASS=P
|
|//*OMS
USER=SYSMAD
|
|//STEP1
EXEC PGM=REPORT
|
|//REPORT1 DD SYSOUT=*
|
+---------------------------------------------------------------------+
In this example, _beta log|z assigns the job MYJOB to the TSO user ID
SYSMAD. In the Job Select table, the entry SYSMAD appears in the User
column for this job. This job remains in the SYSMAD work queue, and no
other user can change the status of this job.
The TSO user SYSMAD can enter the queue type keyword M for MY
queue in the Job Select table to display all jobs with this TSO user ID in
the User column.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
49
Leading in to _beta log|z
//*OMS RETPD
OMS control cards
You can use the RETPD keyword to specify an online retention period for
lists. You can use this keyword to override the retention period of the job
group that the job belongs to. The retention period is specified in number
of workdays.
+---------------------------------------------------------------------+
|//MYJOB
JOB acct,name,MSGCLASS=P
|
|//*OMS
RETPD=10
|
|//STEP1
EXEC PGM=REPORT
|
|//REPORT1
DD SYSOUT=*
|
+---------------------------------------------------------------------+
In this example, _beta log|z keeps all sysout lists from MYJOB in the
online spool for 10 days.
Note: The maximum value is determined by the online retention period of
the job record. If you specify a retention period that is longer, _beta log|z
sets the value to the job record retention period minus one day. The job
record retention period is defined in the Job Record field of the job group
definition.
//*OMS DOC
You can use the DOC keyword to add a user-defined comment to a job.
The text is stored in a JBRE user field (standard: JBREUF01) and can be
included in the Job Selection dialog and the Job Selection table via
appropriate layouts. The maximum length of the comment is
64 characters.
+---------------------------------------------------------------------+
|//MYJOB
JOB acct,name,MSGCLASS=P
|
|//*OMS DOC SEL123-GRP123-XYZ
|
|//STEP1
EXEC PGM=REPORT
|
|//REPORT1
DD SYSOUT=*
|
+---------------------------------------------------------------------+
Scanning for //*OMS DOC
The scan definition for this keyword must be active if you want to use the
//*OMS DOC keyword (see "Scanning (Option A.R.3)" on page 268).
For information on layout definitions, see "_beta log|z layouts (Option
A.1.1)" on page 63. Set the LST parameter B92_COMMENT_FIELD to the
JBRE user-defined field if you want to enable users to add/edit comments
in the Job Selection table.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
50
Leading in to _beta log|z
//*OMS COM
OMS control cards
You can use the COM keyword to add user-coded comments to a job,
which are displayed in the diagnostic messages section of the "Job
Information Table". All text following the blank(s) after COM is considered
a comment.
+---------------------------------------------------------------------+
|//MYJOB
JOB acct,name,MSGCLASS=P
|
|//*OMS COM CALL SYSPROG IF THERE ARE ANY PROBLEMS WITH THIS JOB
|
|//*OMS COM USE QUICK DIAL 123
|
|//STEP1
EXEC PGM=REPORT
|
|//REPORT1
DD SYSOUT=*
|
+---------------------------------------------------------------------+
You can enter more than one comment card. Each one has to be
preceded by //*OMS COM.
Note: There is no need to use the COM keyword if your _beta log|z
system generates a message record for each //*OMS card in the JCL
(see "Diagnostic messages" on page 47).
Event keywords
The Beta-defined scan definitions include several definitions that cause the
writing of an event record.
The scanned keywords are:
//*OMS EVT=
//*OMS LNK/
//*OMS DSN=
Each scan definition includes appropriate event processing parameters
like event ID and severity.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
51
Leading in to _beta log|z
ISPF application
ISPF application
Panels
In the header of each panel, you can see the name of the product you are
currently using.
The next line is the command line. Here, you can enter commands. If in a
panel there is only a choice of certain options, this line is called the
OPTION line. In that case, you have to enter the number of the option you
want. In tables, you can edit entries with line commands. These are
entered in front of the entry in the Sel column of the table.
Entry fields
Entry fields are marked by an arrow (===>).
Output fields
Fields that cannot be altered are marked by a colon ( : ).
Confirming entries
Press the ENTER key to confirm an entry.
Resetting values in
selection layout
Under options 1, 2, O, L, and E, you can use the primary command RES
or RESET to reset the fields of the currently selected layout to their default
values.
Table set-up
The _beta log|z tables show data from the _beta log|z database. All tables
have a headline that explains the information displayed in the different
columns.
Line commands
Line commands can be used, for example, to get detailed information on
the selected table entry. The available line commands are listed in the
upper part of the panel.
Tables
In any table, you can enter the display/suppress command PROF HL
ON/OFF in the command line to display or not display the commands
available to you in that particular table. Suppressing the command display
leaves more space for table rows to be displayed. The display of the
available commands can also be set in the system profile (option P.2,
Extended Help Mode=Yes|No). In all tables, you have the possibility to
enter several line commands at once before confirming with ENTER. The
different commands are then executed one after the other.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
52
Leading in to _beta log|z
Scrolling within tables
Leaving a panel or a table
ISPF application
Some tables contain so much information that the screen is not large
enough to show all of it. In this case, you must use the function keys UP
and DOWN (defaults are PF7 and PF8) to scroll up and down within the
table. If a table contains more columns than can be shown on the screen,
use the function keys RIGHT (default: PF11) to scroll to the right and LEFT
(default: PF10) to scroll to the left.
Use command ...
or function key ...
to scroll ...
DOWN
PF8
downward
UP
PF7
upward
RIGHT
PF11
to the right
LEFT
PF10
to the left
When pressing the END key (PF3), you can leave a panel without
executing any command.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
53
Leading in to _beta log|z
ISPF application
Basic functions
Invoking functions
directly
Functions and subfunctions can be called up directly. For example, enter
P.3 in the COMMAND line to go directly from the "Primary Selection Menu"
to the "User Profile" panel.
To jump from one option to another within _beta log|z, you do not need to
go back to the "Primary Selection Menu" each time. Enter = and the
number of the option you want to go directly to the panel. For example,
enter =P.3 in the COMMAND line of any _beta log|z panel to go to your
user profile.
Using masks
Help function
Many panels enable you to use masks in selection criteria, for example.
You can use the following wildcards:
Wildcard
Description
Percent sign ( % ) or
Question mark ( ? )
Represents any single character
Single asterisk ( * )
Represents any sequence of characters
(incl. zero string)
Online help is available for every panel. Call it up with the HELP key (PF1).
You will receive explanations on the parameters and functions concerning
the panel from which you called up the help text.
Starting from the "Primary Selection Menu", you can call up all help texts
on _beta log|z in sequence.
Messages
The _beta log|z ISPF application may output messages and error
messages on the screen. These messages are displayed in short in the
upper right corner of the screen.
Press the HELP key (PF1) to display a longer and more informative
version of the message in the second line of the screen.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
54
Leading in to _beta log|z
ISPF application
Primary Selection Menu
Primary Selection Menu
When you call _beta log|z, the "Primary Selection Menu" appears:
PE92PRIM ---------------------------------------------------------------------Option ===> __________________________________________________________________
Primary Selection Menu
System
- B92PROD
Location - BERLIN
Subsys-ID - B92P
User ID
- AVSCHM
1
2
3
JOB
RELOAD
UTILITIES
-
Display or Print Online Jobs
Display and Reload Archived Jobs
Display Utilities Selection Menu
O
OPEN SYSTEMS
-
Unix, Windows, SAP Output Selection Menu
L
E
SYSLOG
EVENTS
-
Display or Print Syslogs
Display Events
P
PROFILE
N
NEWS
A
ADMIN
M
MORE
Select one of the above options, or press END key to exit.
Press the HELP key from any panel for help information.
Options
Option
Description
1
Job
Select, display, and print job information, job logs, and
sysout lists
2
Reload
Display and reload archived z/OS jobs
3
Utilities
Submit batch jobs online
O Open Systems
Select, display, and print Open Systems logs obtained
via rules
L
Syslog
Select, display, and print system logs
E
Events
Display events
P
Profile
Display and change user profile parameters
N
News
Display product news
A
Admin
Select and display information on definitions, archiving,
system, and database (Note: This option is for system
administrators only.)
M More
Display or print _beta log|z Extended Index Facility (EIF)
and SAM Jupiter Log Audit Facility (LAF) output
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
55
Leading in to _beta log|z
ISPF application
Administration Selection Menu
Administration Selection
Menu
When you select A - Admin in the "Primary Selection Menu", the
"Administration Selection Menu" appears:
PE92AD00 -------------------------------------------------------------------Option ===> __________________________________________________________________
Administration Selection Menu
1
2
GENERAL
ENTERPRISE
-
System
- B92PROD
Location - BERLIN
Subsys-ID - B92P
User ID
- AVSCHM
Display Definitions Selection Menu
Display Enterprise Definitions Selection Menu
3
FILE TAILORING
-
Display Batch Job Generation Selection Menu
M
MONITOR
-
Display Monitoring Selection Menu
A
S
R
ARCHIVE
SYSTEM
READER
-
Display Archive Processing Selection Menu
Display System Options Selection Menu
Display Reader Options Selection Menu
D
DATABASE
-
Display Service and Database Selection Menu
Select one of the above options, or press END key to return to the previous
menu. Press the HELP key from any panel for help information.
Note
This menu is to be used by system administrators only.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
56
Leading in to _beta log|z
Panel structure
Panel structure
Overview
This section shows the panel structure of the _beta log|z ISPF application.
The overview includes references that help you find the descriptions of the
corresponding options in the documentation.
Panel structure
Primary Selection Menu (see page 55)
1 JOB (see _beta log|z User Guide)
2 RELOAD (see _beta log|z User Guide)
3 UTILITIES (see _beta log|z User Guide)
O OPEN SYSTEMS (see _beta log|z User Guide)
L SYSLOG (see _beta log|z User Guide)
E EVENTS (see _beta log|z User Guide)
P PROFILE (see _beta log|z User Guide)
N NEWS (see page 59)
A ADMIN (see page 22)
1 GENERAL (see page 61)
1 LAYOUT (see page 63)
1 LAYOUT FIELDS (see page 72)
2 SEARCH LAYOUT (see page 76)
3 RESULT LAYOUT (see page 91)
2 JOB GROUP (see page 103)
3 NOTIFY GROUP (see page 122)
4 LOG TYPE
2 ENTERPRISE (see page 124)
1 RULE GROUPS (see page 130)
2 RULES (see page 132)
3 OPERATIONS (see page 136)
4 RUNCYCLES (see page 140)
5 AGENT GROUP (see page 142)
6 AGENTS (see page 144)
S SCAN GROUP (see page 151)
7 SAP SYSTEMS (see page 153)
8 SAP SERVERS (see page 156)
9 SAP ACCOUNTS (see page 159)
3 FILE TAILORING (see page 172)
1 BATCH (see page 175)
D DAILY (see page 442)
D1 ARPRI (see page 400)
D2 CLLST (see page 437)
D3 ARSEC (see page 406)
W WEEKLY (see page 520)
W1 CLARC (see page 424)
W2 CLAR2 (see page 421)
W3 CLARS (see page 429)
W4 CLEVT (see page 434)
(continued)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
57
Leading in to _beta log|z
Panel structure
(continued)
M MORE
2 GAR DATABASES (see page 177)
3 GADD (see page 180)
M MONITOR (see page 182)
1 ARSTATUS (see page 183)
2 RELOAD REQUESTS (see page 189)
3 STATISTICS (see page 191)
A ARCHIVE (see page 192)
1 DEFINITION (see page 206)
2 DATA SETS (see page 212)
3 VOLUMES (see page 215)
S SYSTEM (see page 218)
1 GENERATION (see page 220)
2 SUBSYSTEM (see page 223)
3 GLOBAL (see page 230)
4 SPECIAL RELOAD (see page 236)
1 RELOAD BY GENERATION (see page 237)
2 RELOAD V2 (see page 245)
3 RELOAD V3 (see page 249)
R READER (see page 259)
1 CLASS (see page 260)
2 READER (see page 264)
3 SCAN (see page 268)
4 NOERROR (see page 308)
5 LOG PROCESS (see page 315)
6 EVENT ACTION (see page 318)
D DATABASE (see page 344)
1 DATABASE (see page 351)
2 DICTIONARY (see page 362)
1 TABLES (see page 363)
2 KEYS (see page 368)
3 FIELDS (see page 370)
4 DATABASE (see page 371)
3 STATISTICS (see page 373)
1 BROWSE (see page 374)
2 BATCH (see page 376)
3 CLEANUP (see page 382)
4 UTILITIES
Q QUERY (see page 383)
S SERVICE (see page 388)
1 EIF SELECT (see page 534)
2 LOG AUDIT
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
58
News (Option N)
News (Option N)
Overview
You can use option N to define news items, which provide information on
new features, changes in _beta log|z, or any other current topics of interest
to the users of _beta log|z.
News items are displayed at program start when a user calls _beta log|z.
By default, each news item is displayed to each user only once during the
period that the item is valid. You can also specify that a news item should
be repeated on a daily basis.
If more than one news panel is available for display, the panels appear in
alphabetical order.
Procedure
1. Enter N in the primary panel to call the "News Item Table". This
displays a list of existing news items.
2. Enter line command I to insert a news panel (or enter line command C
to copy an existing news panel).
The "Insert News Item" panel is displayed:
PE92NW11 ---------------------------------------------------------- Page 1 of 2
Command ===> _________________________________________________________________
Insert News Item
Name
Language
Type
===> ........
===> .
===> .......
Valid from: Date ===> ..........
Time ===> ........
Repeat Daily
===> NO.
(E)nglish or (G)erman
(G)eneral,(U)ser,(A)dmin or (S)ystem
Valid to: Date
Time
(Y)es or (N)o
===> __________
===> ________
Title ===> ............................................................
Text ===> .................................................................
===> _________________________________________________________________
===> _________________________________________________________________
===> _________________________________________________________________
===> _________________________________________________________________
===> _________________________________________________________________
Press ENTER to insert this entry or DOWN key to go to next page.
Press END key to cancel changes or HELP key for help information.
3. Fill out the fields (see the table of fields below).
The information is stored in the database table NEWS of the database
MAINDATA (see option A.D.2.1 for the table).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
59
News (Option N)
Fields
Field
Description
Name
Enter a name for the news panel (max. 8 characters).
Language
Choose E for English or G for German to display the
news panel in the English or German panels of _beta
log|z.
Type
Specify the news type General, User, Admin or
System. This makes it easier to identify the target group
for the news in the News Item Table.
Valid from/to Date
Specify the validity period for the news, for example,
from 04/01/2013 to 05/01/2013. When this period
expires, the news panel is no longer displayed during
program start. You can also specify an exact date and
time when the news is to be displayed.
Valid from/to Time
Specify the time for the news, for example, from
00:10:00 to 00:17:00. When the time (and date) period
expires, the news panel is no longer displayed at
program start. You can also specify an exact date and
time when the news is to be displayed.
Repeat Daily
Specify Yes if this news item should be repeated on a
daily basis.
Title
The title of the news panel (max. 60 characters).
Text
The news itself. You can enter max. 910 characters (65
characters in each of the 14 rows).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
60
General (Option A.1)
In this chapter
General (Option A.1)
In this chapter
Topic
Page
Definitions Selection Menu ....................................................................... 62
_beta log|z layouts (Option A.1.1) ............................................................ 63
Layout creation sequence..................................................................... 64
Default layouts provided by _beta log|z ................................................ 65
Which default layout is used for which online option? .......................... 67
Layout fields (Option A.1.1.1) ............................................................... 72
Search layouts (Option A.1.1.2) ........................................................... 76
Displaying search layouts ..................................................................... 76
Changing search layouts ...................................................................... 79
Inserting search layouts ........................................................................ 83
Defaults for search layouts ................................................................... 89
Result layouts (Option A.1.1.3) ............................................................. 91
Displaying result layouts ....................................................................... 91
Changing result layouts ........................................................................ 94
Inserting a job result layout ................................................................... 98
Defaults for result layouts ................................................................... 102
Job group (Option A.1.2) ........................................................................ 103
Defining job masks for job groups ...................................................... 106
Determining the best matching job group ........................................... 108
Determining online and archive retention period ................................ 111
Assigning jobs to job groups ............................................................... 117
Notify groups (Option A.1.3) ................................................................... 122
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
61
General (Option A.1)
Definitions Selection Menu
Definitions Selection Menu
Procedure
Option A.1 - General in the Primary Selection menu opens the "Definitions
Selection Menu":
PE92DF00 ---------------------------------------------------------------------Option ===> __________________________________________________________________
Definitions Selection Menu
1
LAYOUT
-
System
- B92PROD
Location - BERLIN
Subsys-ID - B92P
User ID
- AVSCHM
Display Layout Definitions Selection Menu
2
JOB GROUP
-
Display or Update Job Group Definitions
3
NOTIFY GROUP
-
Display or Update Notify Group Definitions
4
LOG TYPE
-
Display or Update Log Type Definitions
Select one of the above options or press END key to return to the previous
menu. Press the HELP key from any panel for help information.
•
The options for layouts, job groups, and notify groups are described in
the sections that follow.
•
The log type definition (option A.1.4) is used for SAM Jupiter Log Audit
Facility (LAF) output.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
62
General (Option A.1)
_beta log|z layouts (Option A.1.1)
_beta log|z layouts (Option A.1.1)
Overview
_beta log|z enables a different user interface to be created for every user,
each with an individual layout profile for presenting views and selecting
different types of logs. A dynamic user interface of this type is very useful
for presenting different types of logs such as job logs, system logs and
event logs.
•
The search and result layouts for various kinds of jobs and logs are
administered under option A.1.1. Here you can define which field,
table column etc. is to be displayed where and under which name.
•
Log types are standard Windows/Unix logs, endless Windows/Unix
logs, Windows event logs, SAP logs, and SAP system logs.
•
The predefined layouts are listed below.
•
The panels and tables shown in the _beta log|z manuals are the
standard panels and tables supplied with _beta log|z before
customization.
Selecting layouts
(Option P.8)
Under option P.8, you can select which search layout you want to use for
selection. The result layout for displaying jobs and logs is specified in the
search layout definition. For more information, see "Selecting user layouts
(Option P.8)" in _beta log|z User Guide.
Dynamic layout handling
Dynamic layout handling enables entries to be saved for every user, layout
and language specified. This means that when the language or layout is
changed, the most recent entries for the new layout or language are
displayed.
Example: User USER1 enters Jobname=A* in the English layout
BETA_HSTJ_SEARCH. USER1 then changes to the German layout
BETA_HSTJ_SEARCH and enters Jobname=B*. When the user changes
back to the English layout BETA_HSTJ_SEARCH, Jobname=A* is still
displayed.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
63
General (Option A.1)
_beta log|z layouts (Option A.1.1)
Layout creation sequence
Overview
The following is an example sequence on how to create result layouts,
search layouts, and how to link them up with one another.
Result and search layouts can be created for host jobs, file rules, SAP job,
system logs, and events.
Layout result types can be job or log result layouts.
Example
1. Create a job result layout for host jobs.
Use the line command CF under option A.1.1.3.
2. Specify the fields in the job result layout for host jobs.
Use the line command F under option A.1.1.3.
3. Create a log result layout for host jobs.
Use the line command CF under option A.1.1.3.
4. Specify the fields in the job result layout for host jobs.
Use the line command F under option A.1.1.3.
5. Create a search layout for host jobs.
Use the line command CF under option A.1.1.2.
6. Specify the fields in the search layout for host jobs.
Use the line command F under option A.1.1.2.
7. Connect the job and log result layouts for host jobs with the new
search layout for host jobs.
Enter the line command S in front of the new search layout for host
jobs under option A.1.1.2. Select the new job result layout for host jobs
in the field Job Result Layout. Select the new log result layout for
host jobs in the field Log Result Layout.
8. Select the new search layout for host jobs under option P.8.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
64
General (Option A.1)
_beta log|z layouts (Option A.1.1)
Default layouts provided by _beta log|z
Overview
_beta log|z includes two sets of default layouts:
•
One set of layouts for the ISPF application (3270)
•
One set of layouts specially adapted for _beta view
These two sets of layouts (so-called Beta layouts) cannot be changed or
deleted.
Layouts (3270)
Option
The following table shows the default layouts for the _beta log|z ISPF
application. The names of these definitions start with BETA_. The search
layout definition specifies the name of the job result layout that is to be
used.
Category
Search layout
Job result layout
1
Online Host Jobs and
Host Logs
BETA_HSTJ_SEARCH
BETA_HSTJ_RESULT
2
Archived Host Jobs and
Host Logs
BETA_ARCH_SEARCH
BETA_ARCH_RESULT
O.1
Online File Rule Jobs and File
Rule Logs
(Normal Logs, Endless Logs,
Windows Event Logs)
BETA_FILR_SEARCH
BETA_FILR_RESULT
O.2
Online SAP Jobs and
SAP Logs
BETA_SAPJ_SEARCH
BETA_SAPJ_RESULT
O.3
Archived File Rules and
File Rule Logs
BETA_ARCF_SEARCH
BETA_ARCF_RESULT
O.4
Archived SAP Jobs and
SAP Logs
BETA_ARCS_SEARCH
BETA_ARCS_RESULT
System Logs
BETA_SYSL_SEARCH
BETA_SYSL_RESULT
E.0
Events (Type 00)
BETA_EVNT_SEARCH
BETA_EVNT_RESULT
E.1
Events (AAL)
BETA_EV01_SEARCH
BETA_EV01_RESULT
E.2
IWS occurrences
BETA_EV02_SEARCH
BETA_EV02_RESULT
L
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
65
General (Option A.1)
Layouts _beta view
_beta log|z layouts (Option A.1.1)
The following table shows the default layouts for _beta view. The names of
these definitions start with VIEW_. The search layout definition specifies
the name of the job result layout that is to be used.
Category
Search layout
Job result layout
Jobs
VIEW_HSTJ_SEARCH
VIEW_HSTJ_RESULT
Jobs (Archive)
VIEW_ARCH_SEARCH
VIEW_ARCH_RESULT
Decentral Files
VIEW_FILR_SEARCH
VIEW_FILR_RESULT
Decentral Files (Archive)
VIEW_ARCF_SEARCH
VIEW_ARCF_RESULT
SAP Output
VIEW_SAPJ_SEARCH
VIEW_SAPJ_RESULT
SAP Output (Archive)
VIEW_ARCS_SEARCH
VIEW_ARCS_RESULT
System Logs
VIEW_SYSL_SEARCH
VIEW_SYSL_RESULT
Events
VIEW_EVNT_SEARCH
VIEW_EVNT_RESULT
Activity Audit Log
VIEW_EV01_SEARCH
VIEW_EV01_RESULT
IWS Occurrences
VIEW_EV02_SEARCH
VIEW_EV02_RESULT
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
66
General (Option A.1)
_beta log|z layouts (Option A.1.1)
Which default layout is used for which online option?
Overview
The installation default is as follows (online option P.8):
Job Select Layout Name
===> BETA_HSTJ_SEARCH
(* for list)
File Rule
SAP Job
Layout Name
Layout Name
===> BETA_FILR_SEARCH
===> BETA_SAPJ_SEARCH
(* for list)
(* for list)
Job Reload Layout Name
===> BETA_ARCH_SEARCH
(* for list)
File Rule Reload Layout Name
SAP Job Reload Layout Name
===> BETA_ARCF_SEARCH
===> BETA_ARCS_SEARCH
(* for list)
(* for list)
Event Layout Name (EVT00)
===> BETA_EVNT_SEARCH
(* for list)
The upper right corner of the selection panel displays which layout is used.
Job select layout name
The layout you select in the Job Select Layout Name field is used for all
selections made under online option 1 - Job.
The installation default layout is BETA_HSTJ_SEARCH. When you use
this layout, all host jobs are selected by submit, start or end time.
PE92BR00 ---------------------------------------------------------------------Command ===> ________________________________________________ Scroll ===> PAGE
Display Jobs by End Time
Select from last
Select from Date
Select to
Date
Job Name 1
Job Name 3
Job ID
===> 19 hours..
===> TODAY.....
===> TODAY.....
===> *_______
===> ________
===> ________
Layout: BETA_HSTJ_SEARCH
1-99, (m)inutes, (h)ours, or (d)ays
Time ===> 00:00:00
Time ===> 23:59:59
Job Name 2 ===> ________
Job Name 4 ===> ________
Job Net ID ===> ________
Optional Criteria
Queue Type
===> ________
Job Group ID ===> ________
Job Message Class
===> _
System ID ===> ________
Job Error Text
===> ________
Init Errors only ===> ____ (Y/N/blank)
Jobs with Notes only ===> ____
(Y/N/blank)
Long Job Name
===> ________________________________
Host Name
===> __________________________________________________
Additional Arguments ===> NO..
(Y/N)
Press ENTER key to display jobs.
Press END key to return to the previous menu.
Jumping from other
products
The default selection panel of option 1 with default search layout
BETA_HSTJ_SEARCH is always used to jump from IWS, _beta doc|z,
_beta job|z into _beta log|z.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
67
General (Option A.1)
File rule layout name
_beta log|z layouts (Option A.1.1)
The layout you select in the field File Rule Layout Name is used for all
selections made under online option O.1 - Online UNIX/Windows.
The installation default layout is BETA_FILR_SEARCH. When you use this
layout, all file rules are selected by submit, start, or end time.
PE92BF00 ---------------------------------------------------------------------Command ===> ________________________________________________ Scroll ===> PAGE
Display File Rules by End Time
Layout: BETA_FILR_SEARCH
Select from last
Select from Date
Select to
Date
===> 99 hours..
===> TODAY.....
===> TODAY.....
1-99, (m)inutes, (h)ours, or (d)ays
Time ===> 00:00:00
Time ===> 23:59:59
Rule Name
Agent
===> ________
===> ________
Optional Criteria
Operation
Host Name
===> ________
===> __________________________________________________
Rules w. Notes only ===> ____
Rules w. Errors only ===> ____
Queue Type
===> ________
(Y/N/blank)
(Y/N/blank)
Press ENTER key to display file rule output.
Press END key to return to the previous menu.
SAP job layout name
The layout you select in field SAP Job Layout Name is used for all
selections made under online option O.2 - Online SAP.
The installation default layout is BETA_SAPJ_SEARCH.
When you use this layout, all SAP jobs are selected by submit, start, or
end time.
PE92BS00 ---------------------------------------------------------------------Command ===> ________________________________________________ Scroll ===> PAGE
Display SAP Jobs by End Time
Select from last
Select from Date
Select to
Date
===> __ hours..
===> TODAY.....
===> TODAY.....
Rule Name
Agent
===> ________
===> ________
Layout: BETA_SAPJ_SEARCH
1-99, (m)inutes, (h)ours, or (d)ays
Time ===> 00:00:00
Time ===> 23:59:59
Optional Criteria
Operation
===> ________
Queue Type ===> ________
SAP Job Name
===> ________________________________
Job Error Text
===> ________
Jobcount ===> ________
SAP Server
===> ________
Client ===> ___
SAP User
===> ____________
Host Name
===> __________________________________________________
Jobs with Notes only ===> ____
Errors only ===> ____ (Y/N/blank)
Press ENTER key to display sap rule output.
Press END key to return to the previous menu.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
68
General (Option A.1)
Job reload layout name
_beta log|z layouts (Option A.1.1)
The layout you select in the field Job Reload Layout Name will be used
for selecting archived jobs under online option 2 - Reload.
The installation default layout is BETA_ARCH_SEARCH. When you use
this layout, all archived host jobs will be displayed.
PE92RL00 ---------------------------------------------------------------------Command ===> ________________________________________________ Scroll ===> PAGE
Display Archived Jobs
Layout: BETA_ARCH_SEARCH
Select from last
Select from Date
Select to
Date
===> 1_ hours..
===> 01.03.2012
===> 13.04.2012
Optional Criteria
Job Name 1
Job Name 3
System ID
Job Group ID
Initial Errors only
Job Message Class
Status Type
===> ________
===> ________
===> ____
===> ________
===> ____
===> _
===> ________
1-99, (m)inutes, (h)ours, or (d)ays
Time ===> 00:00:00
Time ===> 23:59:59
Job Name 2 ===> ________
Job Name 4 ===> ________
Job ID ===> ________
(Y/N/blank)
(0-9, A-Z or +)
(ME)ssages,(ER)ror,(NO)tes,(ED)F
Press ENTER key to display archived jobs.
Press END key to return to the previous menu.
File rule reload layout
name
The layout you select in the field File Rule Reload Layout Name will be
used for selecting archived file rules under online option O.3 - Archived
UNIX/Windows.
The installation default layout is BETA_ARCF_SEARCH. When you use
this layout, all archived file rules will be displayed.
PE92RF00 ---------------------------------------------------------------------Command ===> ________________________________________________ Scroll ===> PAGE
Display Archived File Rules
Layout: BETA_ARCF_SEARCH
Select from last
Select from Date
Select to
Date
===> __ hours..
===> TODAY.....
===> TODAY.....
1-99, (m)inutes, (h)ours, or (d)ays
Time ===> 00:00:00
Time ===> 23:59:59
Optional Criteria
Rule Name
Agent
Operation
Long Job Name
Long Host Name
===> ________
===> ________
===> ________
===> ________________________________
===> __________________________________________________
Rules w. Errors only ===> ____
Status Type
===> ________
(Y/N/blank)
(ME)ssages,(ER)ror,(NO)tes
Press ENTER key to display archived rules.
Press END key to return to the previous menu.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
69
General (Option A.1)
SAP job reload layout
name
_beta log|z layouts (Option A.1.1)
The layout you select in the field SAP Job Reload Layout Name will be
used for selecting archived SAP jobs under online option O.4 - Archived
SAP.
The installation default layout is BETA_ARCS_SEARCH. When you use
this layout, all archived SAP jobs will be selected by time.
PE92RE00 ---------------------------------------------------------------------Command ===> ________________________________________________ Scroll ===> PAGE
Display Archived SAP Jobs
Layout: BETA_ARCS_SEARCH
Select from last
Select from Date
Select to
Date
===> __ .......
===> ..........
===> ..........
1-99, (m)inutes, (h)ours, or (d)ays
Time ===> ________
Time ===> ________
Optional Criteria
Rule Name
Agent
Operation
SAP Job Name
Long Host Name
SAP Server
Client
===> ________
===> ________
===> ________
===> ________________________________
===> __________________________________________________
===> ________
===> ___
Jobs w. Errors only
Status Type
===> ____
===> ________
(Y/N/blank)
(ME)ssages,(ER)ror,(NO)tes
Press ENTER key to display archived SAP jobs.
Press END key to return to the previous menu.
Syslog layout name
The layout is used for selecting system logs under online option LSyslog.
Only the default Syslog layout BETA_SYSL_SEARCH can be used.
Therefore this layout is not displayed under option P.8.
PE92SL00 ---------------------------------------------------------------------Command ===> ________________________________________________ Scroll ===> PAGE
Display Syslogs
Select from last
Select from Date
Select to
Date
Job Name
z/OS System ID
Layout: BETA_SYSL_SEARCH
===> __ hours..
===> TODAY.....
===> TODAY.....
1-99, (m)inutes, (h)ours, or (d)ays
Time ===> 00:00:00
Time ===> 23:59:59
: SYSL*
===> ____
or
Agent Name ===> ________
Press ENTER key to display syslogs.
Press END key to return to the previous menu.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
70
General (Option A.1)
Event layout name
_beta log|z layouts (Option A.1.1)
The layout is used for selecting events under online option E - Events.
The installation default layout is BETA_EVNT_SEARCH.
PE92EV00 ---------------------------------------------------------------------Command ===> ________________________________________________ Scroll ===> PAGE
Display Events by Input Date
Layout: BETA_EVNT_SEARCH
Select from last
Select from Date
Select to
Date
===> 99 days...
===> TODAY.....
===> TODAY.....
1-99, (m)inutes, (h)ours, or (d)ays
Time ===> 00:00:00
Time ===> 23:59:59
Event Text
Severity
===> *.................................................
===> _
(I/W/E)
Event ID
Category
Source
Status
===> _____
===> ________
===> ____
===> _
Event Job/Rule
System ID
===> ________________________________
===> ________
(H)ostJob,(F)ileRule,(S)APRule
(B)eta,(U)ser
(I/P/E)
Press ENTER key to display events.
Press END key to return to the previous menu.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
71
General (Option A.1)
_beta log|z layouts (Option A.1.1)
Layout fields (Option A.1.1.1)
Overview
All the available layout fields can be displayed under option A.1.1.1.
Procedure
To display fields with specific properties, proceed as follows:
1. In the primary panel, select A.1.1 to display the "Layout Definitions
Selection" menu:
2. Enter 1 for "Layout Fields".
The "Layout Field Definition Selection" panel comes up:
PE92LD01 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Layout Field Definition Selection
Field Name
Location
Category
Data Type
===> *...............
===> ________
(O)nline or (A)rchive
===> ________
(HO)stJob, (FI)leRule, (SA)PJob,
(EV)ent, (SY)slog, (GE)neral
===> ________
(C)har,(D)ate,(T)ime,(I)nteger,(F)lag
DB Table
===> ________
DB Field
===> ________
Virtual Fields only ===> ___
(Y)es, (N)o or blank
Search Allowed
Display Allowed
(Y)es, (N)o or blank
(Y)es, (N)o or blank
===> ___
===> ___
Press ENTER key to display layout field definitions.
Press END key to return to the previous menu.
3. Enter the selection criteria you want to use (see the table of fields
below).
For example, type an asterisk * in field Field Name, Online in field
Location, and press ENTER. The matching entries will be displayed in
the "Layout Fields Table":
PE92LD10 -------------------------------------------------- Row
1 of
177
Command ===> ________________________________________________ Scroll ===> PAGE
Layout Fields Table
S - Select
Sel Field Name
DB Table DB Field Virt DataType Lngth SrchA DsplA Category
Additional Args
YES FLAG
00004 YES
NO
HOSTJOB
Agent
JBRE
AGENAME NO
CHAR
00008 YES
YES
GENERAL
Agent Group
JBRE
AGRPNAME NO
CHAR
00024 YES
YES
GENERAL
Archive List Flg JLR
JLRSTFAR NO
FLAG
00007 YES
YES
GENERAL
Archive Pending JBR
JBRARFPE NO
FLAG
00003 NO
NO
GENERAL
Archive PointerJ JBR
JBRARCPT NO
INTEGER 00032 NO
NO
GENERAL
Archive PointerL JLR
JLRARCPT NO
INTEGER 00032 NO
NO
GENERAL
Archive Pool Job JBR
JBRAPOOL NO
CHAR
00008 NO
NO
GENERAL
Archive Pool JLR JLR
JLRAPOOL NO
CHAR
00008 NO
YES
GENERAL
Archived Flag
JBR
JBRARFAR NO
FLAG
00003 YES
NO
GENERAL
AAL Comment
EVT01
AALCOMM NO
CHAR
00080 YES
YES
EVENT
AAL Event ID
EVT01
EVTID
NO
INTEGER 00005 YES
YES
EVENT
AAL Event Token EVT01
EVTTOKEN NO
INTEGER 00032 YES
YES
EVENT
AAL Field1
EVT01
AALFLD1 NO
CHAR
00008 YES
YES
EVENT
AAL Field2
EVT01
AALFLD2 NO
CHAR
00008 YES
YES
EVENT
AAL Field3
EVT01
AALFLD3 NO
CHAR
00010 YES
YES
EVENT
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
72
General (Option A.1)
_beta log|z layouts (Option A.1.1)
Which fields you can use while inserting layouts depends on the
location, category and type you selected. Only the fields relevant for
the defined layout type will be displayed and can be used during layout
definition.
4. Enter the line command S in front of a field.
The "Display Layout Field Definition" panel appears:
PE92LD14 ---------------------------------------------------------------------Command ===> ________________________________________________________________
Display Layout Field Definition
Last update: BETAINST 01/01/2008 12:00:00
Field Name
:
Event System ID
DB Table
DB Field
:
:
EVT00
EVTSYSID
Location
Data Type
Length
Category
:
:
:
:
ONLINE
CHAR
00008
EVENT
Search Allowed
Display Allowed
:
:
YES
YES
Description
:
Event00 System ID
ID :
or
Virtual Field :
0000000412
-
Press END key to return to previous menu or HELP key for help information.
This is a purely informational panel.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
73
General (Option A.1)
Fields
Line command
_beta log|z layouts (Option A.1.1)
Field
Description
Field Name
Enter a specific layout field name or use a mask. The
entry is case-sensitive.
Location
The location of layout fields can be (O)nline or (A)rchive.
Enter one of the location types to select either fields for
online layouts or only fields for archive layouts. Or leave
the field blank to select fields of both locations.
Category
Enter (HO)stJob, (FI)leRule, (SA)PJob, (EV)ent,
(SY)slog, or (GE)neral to display fields belonging to this
category. (GE)neral will display fields that can be used
by more than one category. If you leave the field blank,
all fields of all categories will be displayed.
Data Type
Enter one of the data types: (C)har, (D)ate, (T)ime,
(I)nteger, (F)lag to see only fields of this specific type. If
you leave the field blank, all data field types will be
displayed.
DB Table
Enter the name of a database table or use a mask to
display only the fields of the specified table.
DB Field
Enter the name of a database field or use a mask to
display only the specified fields.
Virtual Fields only
Enter (Y)es to select only virtual fields that do not exist
in the _beta log|z database. Enter (N)o to display only
real _beta log|z database fields. Leave the field blank to
select both virtual and real database fields.
Search Allowed
Enter (Y)es to select only fields that can be used as
search criterions in search layouts. Specify (N)o to
select only fields that are not allowed to be used as
search criterions. Or leave the field blank to display both
categories.
Display Allowed
Enter (Y)es to select only fields that can be used as
table columns in result layouts. Enter (N)o to display
only fields that are not allowed to be used as result table
columns. Or leave the field blank to display both
categories.
S
Displays or updates a Beta-defined or user-defined layout field.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
74
General (Option A.1)
Search locations and
categories
_beta log|z layouts (Option A.1.1)
Only fields from online tables (for example, JBR, JBRE, JLR, JLRE, and
some virtual fields not present in the database) are available for online
search layouts. Fields from archive tables (GAR, GARE, and some virtual
fields) are available for archive search layouts.
Only fields that have been defined and released under option A.1.1.1 (field
Search Allowed=YES) can be used in a search layout. The following field
categories are available:
Field category
Search layout category
HOSTJOB
Host-specific fields
Note: EJM jobs and EDF jobs are displayed
under the host categories.
Changing a layout field
definition
FILERULE
File rule-specific fields
SAPJOB
SAP-specific fields
EVENT
Event-specific fields
SYSLOG
Syslog-specific fields
GENERAL
Common fields used for all categories
The layout field definitions of predefined Beta fields cannot be changed or
deleted.
Only the layout field definitions of user fields can be changed. Adapt or
create a layout field definition that matches the data of the user field. For
more information, see "User fields for user-defined indexes" on page 535.
Field in use
If a field is already being used in a layout, the display layout field definition
panel is automatically displayed instead of the update panel. The message
"Field in use" indicates that it is not possible to change this field definition.
PE92LD14 -------------------------------------------------------- Field in use
Command ===> ________________________________________________________________
Display Layout Field Definition
Last update: BETAINST 09/01/2004 12:00:00
Field Name
:
JBRE Userfield 1
DB Table
DB Field
:
:
JBRE
JBREUF01
Location
Data Type
Length
Category
:
:
:
:
ONLINE
CHAR
00064
GENERAL
Search Allowed
Display Allowed
:
:
YES
YES
Description
:
JBRE Userfield 1
ID :
or
Virtual Field :
0000000096
-
Press END key to return to previous menu or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
75
General (Option A.1)
_beta log|z layouts (Option A.1.1)
Search layouts (Option A.1.1.2)
Displaying search layouts
Overview
Search layouts determine the properties and the appearance of search
dialogs / selection panels for online and archive searches.
Procedure
To display search layouts, proceed as follows:
1. In the primary panel, select A.1.1 to display the "Layout Definitions
Selection" menu.
2. Enter 2 for "Search Layouts" and press ENTER.
The "Search Layout Definition Selection" panel comes up:
PE92LD02 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Search Layout Definition Selection
Layout Name
Search Location
Category
Language
===> *...............
===> _______
(O)nline or (A)rchive
===> ________
(HO)stJob, (FI)leRule, (SA)PJob,
(EV)ent, (SY)slog, (AL)l
===> _
(E)nglish or (G)erman
Panel Title
===> __________________________________________________
Press ENTER key to display search layouts.
Press END key to return to the previous menu.
3. Enter the selection criteria you want to use. For example, type an
asterisk * in the field Layout Name, Online in the field Search
Location, and press ENTER:
PE92LD20 -------------------------------------------------- Row
1 of
21
Command ===> ________________________________________________ Scroll ===> PAGE
Search Layout Table
S - Select
I - Insert
F - Display Fields of this Layout
Sel
C - Copy
D - Delete
CF - Copy with Fields
Name
L Category Location Panel Title
BETA_ARCF_SEARCH E FILERULE ARCHIVE Display Archived File Rules
BETA_ARCH_SEARCH E HOSTJOB ARCHIVE Display Archived Jobs
BETA_ARCS_SEARCH E SAPJOB
ARCHIVE Display Archived SAP Jobs
BETA_EVNT_SEARCH E EVENT
ONLINE
Display Events by Input Date
BETA_EV01_SEARCH E EVENT
ONLINE
Display Activity Audit Log Records
BETA_EV02_SEARCH E EVENT
ONLINE
Display IWS Occurrences by Submit T
BETA_FILR_SEARCH E FILERULE ONLINE
Display File Rules by &B92JSEL Time
BETA_HSTJ_BWESRC E HOSTJOB ONLINE
Display Jobs by &B92JSEL Time
BETA_HSTJ_SEARCH E HOSTJOB ONLINE
Display Jobs by &B92JSEL Time
BETA_SAPJ_SEARCH E SAPJOB
ONLINE
Display SAP Jobs by &B92JSEL Time
BETA_SYSL_SEARCH E SYSLOG
ONLINE
Display Syslogs
VIEW_ARCF_SEARCH E FILERULE ARCHIVE Display Archived File Rules
VIEW_ARCH_SEARCH E HOSTJOB ARCHIVE Display Archived Jobs
VIEW_ARCS_SEARCH E SAPJOB
ARCHIVE Display Archived SAP Jobs
VIEW_EVNT_SEARCH E EVENT
ONLINE
Display Events by Input Date
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
76
General (Option A.1)
_beta log|z layouts (Option A.1.1)
The "Search Layout Table" panel shows all installation default online
search layouts as well as all online search layouts you have defined so
far.
4. For example, type the line command S in front of the search layout
"BETA_HSTJ_SEARCH" and press ENTER.
The " Display Search Layout-General Fields" panel appears:
PE92LD21 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Display Search Layout-General Fields Last update: BETAINST 09/01/2004 12:00:00
Layout Name
Search Location
Category
Language
: BETA_HSTJ_SEARCH
: ONLINE
: HOSTJOB
: E
Panel Title
Description
: Display Jobs by &B92JSEL Time
: Default Layout for Option 1
:
: BETA_HSTJ_RESULT
: BETA_HSTL_RESULT
Job Result Layout
Log Result Layout
ID :
0000000001
Optional Date and Time Search Parameters
Date Field
:
Time Field
:
Input Optional
: NO
Press END key to return to previous panel or HELP key for help information.
This is a purely information panel.
Fields
Field
Description
Layout Name
Enter a specific layout name or use a mask. You can
find an overview of the default layout names in "Default
layouts provided by _beta log|z" on page 65.
Search Location
The location of layouts can be (O)nline or (A)rchive.
Enter one of the location types to select either online
layouts or archive layouts.
Category
Enter (HO)stJob, (FI)leRule, (SA)PJob, (EV)ent,
(SY)slog, or (AL)l to display layouts belonging to this
category. ALL displays only layouts that can be used for
selections for more than one category. If you leave the
field blank, all layouts of all categories will be displayed.
Language
Enter E for English or G for German to display only
layouts in the selected language.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
77
General (Option A.1)
Line commands
_beta log|z layouts (Option A.1.1)
S
Displays a search layout.
F
Displays a table containing all fields defined within the specific
search layout. Here you can directly insert new fields, or copy,
update and delete available fields of this layout.
I
Inserts a search layout.
C
Copies a search layout without fields.
CF
Copies a search layout with all fields used in the layout.
Note: The search layout to be inserted must use the same search
location and category as the search layout to be copied.
D
Deletes a search layout.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
78
General (Option A.1)
_beta log|z layouts (Option A.1.1)
Changing search layouts
Overview
We recommend that you copy an existing search layout with all of its fields
so that you can practice changing a search layout before you insert a new
one.
A Beta-defined layout cannot be changed or deleted, but you can make a
copy and then change the copy.
Time selection
In the date and time fields you decide which date and time is to be used for
the search request.
If the fields are blank, the date and time (submit time, start time or end
time) set in your user profile (option P.3) and in the subsystem options
(A.S.2) will be automatically used for your selection.
If you want to use a different time for the selection (for example, the readin time or a time from a user field), you must enter these in the optional
date and time search criteria. If you have selected date and time fields in
the optional fields Date and Time, the time selection is made using these
field entries. Only date and time fields which match within one search
layout can be selected. If they mismatch, a message will inform you.
In the field Input optional you can decide whether an entry in the date and
time fields is mandatory: Enter No for mandatory fields or Yes when an
entry in these fields is to be optional.
Time selection for
archive layouts
Only the submit time can be used for archive layout selections because no
other times are saved (in the GAR table). For this reason, no entries in the
optional date and time fields can be made for archive layouts.
Procedure
First decide which search layout you want to copy, for example
BETA_HSTJ_SEARCH, language E. It is not possible to change the
Search Location and Category when copying a search layout.
Proceed as follows:
1. Display the desired search layouts. The procedure is described in
"Search layouts (Option A.1.1.2)" on page 76.
2. In the Search Layout table, enter the line command CF in front of the
search layout BETA_HSTJ_SEARCH, language E, and press ENTER.
The "Insert Search Layout - General Fields" panel comes up:
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
79
General (Option A.1)
_beta log|z layouts (Option A.1.1)
PE92LD22 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Insert Search Layout - General Fields
Layout Name
Search Location
Category
===> BETA_HSTJ_SEARCH
: ONLINE
: HOSTJOB
Language
Panel Title
Description
===> E
(E)nglish or (G)erman
===> Display Jobs by &B92JSEL Time.....................
===> Default Layout for Option 1_______________________
===> ______________
Job Result Layout ===> BETA_HSTJ_RESULT (* for list)
Log Result Layout ===> BETA_HSTL_RESULT (* for list)
Optional Date and Time Search Parameters
Date Field
===> ________________
Time Field
===> ________________
Input Optional
===> NO.
(* for list)
(* for list)
(Y)es or (N)o
Press ENTER key to insert this entry.
Press END key to cancel changes or HELP key for help information.
3. Enter a new layout name, for example MY_HSTJ_SEARCH1, the
language, the panel title, and the description.
4. Select a job and a log result layout in the following two fields. Choose
one of the installation default result layouts or one you created
beforehand.
For more information, see "Inserting a job result layout" on page 98.
5. Enter an asterisk * in the date field and press ENTER.
The "Insert Search Layout - Data Column List" panel comes up:
PE92LD2A ---------------------------------------------------------- Row 1 of 6
Command ===> ________________________________________________ Scroll ===> PAGE
Insert Search Layout - Data Column List
S - Select
Please Select a Data Column
Sel Field Name
DB Table DB Field Type Lngth Description
End Date
JBR
SRCENDD DATE 00010 Source End Date
Plan. Date
JBRE
JBREPLDT DATE 00010 Planned date of rule executio
Rdr-Date
JBR
JBRRINDT DATE 00010 Job Read-in Date
Rld-Date
JBR
JBRRLDDT DATE 00010 Reload date of job
Start Date
JBR
SRCSTRTD DATE 00010 Source Start Date
Submit Date
JBR
SRCSUBD DATE 00010 Source Submit Date
******************************* Bottom of data ********************************
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
80
General (Option A.1)
_beta log|z layouts (Option A.1.1)
6. Enter the line command S, for example, in front of the field End Date,
and press ENTER.
7. In the time field select, for example, the field End Time.
The panel may now look like the following:
PE92LD22 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Insert Search Layout - General Fields
Layout Name
Search Location
Category
===> MY_HSTJ_SEARCH1.
: ONLINE
: HOSTJOB
Language
Panel Title
Description
===> E
(E)nglish or (G)erman
===> Display Jobs by End Date and Time.................
===> My First Layout for Option 1______________________
===> ______________
Job Result Layout ===> BETA_HSTJ_RESULT (* for list)
Log Result Layout ===> BETA_HSTL_RESULT (* for list)
Optional Date and Time Search Parameters
Date Field
===> End Date________
Time Field
===> End Time________
Input Optional
===> YES
(* for list)
(* for list)
(Y)es or (N)o
Press ENTER key to insert this entry.
Press END key to cancel changes or HELP key for help information.
8. Press ENTER to insert the changed search layout.
9. Enter the line command F in front of the changed search layout to
display the fields used in the layout.
In the panel you can insert new fields and/or delete other ones.
10. Press ENTER to save your changes.
If you want to use this layout for your select requests under option 1,
you must select it under option P.8.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
81
General (Option A.1)
Changes after definition
_beta log|z layouts (Option A.1.1)
To change anything in the layout later on, proceed as follows:
1. Display the desired search layout. The procedure is described in
"Search layouts (Option A.1.1.2)" on page 76.
2. In the Search Layout table, enter the line command S in front of the
search layout and press ENTER.
The "Update Search Layout-General Fields" panel is displayed:
PE92LD21 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Update Search Layout-General Fields
Layout Name
Search Location
Category
Language
Last update: AVSCHM
: MY_HSTJ_SEARCH1
: ONLINE
: HOSTJOB
: E
12/18/2012 10:34:31
ID :
0000000056
Panel Title
Description
===> Display Jobs by End Date and Time.................
===> My First Layout for Option 1______________________
===> ______________
Job Result Layout ===> BETA_HSTJ_RESULT (* for list)
Log Result Layout ===> BETA_HSTL_RESULT (* for list)
Optional Date and Time Search Parameters
Date Field
===> End Date________
Time Field
===> End Time________
Input Optional
===> YES
(* for list)
(* for list)
(Y)es or (N)o
Press ENTER key to update this entry.
Press END key to return to previous panel or HELP key for help information.
In the update panel you can change the panel title, the description,
you can choose other job and log result layouts, and other date and
time selection criteria.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
82
General (Option A.1)
_beta log|z layouts (Option A.1.1)
Inserting search layouts
Note on time selection
In the date and time fields you decide which date and time is to be used for
the search request.
If the fields are blank, the date and time (submit time, start time or end
time) set in your user profile (option P.3) and in the subsystem options
(A.S.2) will be automatically used for selection.
If you want to use a different time for the selection (for example, the readin time or a time from a user field), you must enter it in the optional date
and time search criteria. If you have selected date and time fields in the
optional fields Date and Time, the time selection is made using these field
entries. Only date and time fields which match within one search layout
can be selected. If they mismatch, a message will inform you.
In the field Input optional you can decide whether an entry in the date and
time fields is mandatory: Enter No for mandatory fields or Yes when an
entry in these fields is to be optional.
Note on time selection
for archive layouts
Only the submit time can be used for archive layout selections because no
other times are saved (in the GAR table). For this reason, no entries in the
optional date and time fields can be made for archive layouts.
Before you begin
An appropriate job result must exist for you to be able to save you new
search layout. Job and log result layout must be of the same category as
the search layout.
Create appropriate result layouts before defining the search layout. In the
example below, we will use the job result layout ALL_JOB_HITS and the
log result layout ALL_LOG_HITS. For more information, see "Inserting a
job result layout" on page 98.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
83
General (Option A.1)
Procedure
_beta log|z layouts (Option A.1.1)
To insert a search layout, proceed as follows:
1. Display the "Search Layout Table". The procedure is described in
"Search layouts (Option A.1.1.2)" on page 76.
2. In the "Search Layout Table" enter the line command I in front of any
search layout and press ENTER.
The "Insert Search Layout - General Fields" panel is displayed:
PE92LD22 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Insert Search Layout - General Fields
Layout Name
Search Location
Category
===> ................
===> .......
===> ........
(O)nline or (A)rchive
(HO)stJob, (FI)leRule, (SA)PJob,
(EV)ent, (AL)l
Language
===> .
(E)nglish or (G)erman
Panel Title
===> ..................................................
Description
===> __________________________________________________
===> ______________
Job Result Layout ===> ................ (* for list)
Log Result Layout ===> ________________ (* for list)
Optional Date and Time Search Parameters
Date Field
===> ________________
Time Field
===> ________________
Input Optional
===> NO.
(* for list)
(* for list)
(Y)es or (N)o
Press ENTER key to insert this entry.
Press END key to cancel changes or HELP key for help information.
3. Enter a new layout name, e.g. MIXED_SEARCH, search location
Online, category ALL, language E, panel title "Mixed Search", and as
the description "Mixed search for Host/File/SAP/Event".
4. Select appropriate result layouts in the following two fields, in this
example ALL_JOB_HITS and ALL_LOG_HITS. For more information,
see "Inserting a job result layout" on page 98.
5. Enter an asterisk * in the date field and press ENTER.
The "Insert Search Layout - Data Column List" panel is displayed:
PE92LD2A --------------------------------------------------------- Row 1 of 10
Command ===> ________________________________________________ Scroll ===> PAGE
Insert Search Layout - Data Column List
S - Select
Please Select a Data Column
Sel Field Name
DB Table DB Field Type Lngth Description
AAL Input Date
EVT01
EVTINPDT DATE 00010 AAL Input Date (Event01)
End Date
JBR
SRCENDD DATE 00010 Source End Date
Event Input Date EVT00
EVTINPDT DATE 00010 Event00 Input Date
Event Proc Date EVT00
EVTPRODT DATE 00010 Event00 Processed Date
Event SubmitDate EVT00
SRCSUBD DATE 00010 Event00 Submit Date
Plan. Date
JBRE
JBREPLDT DATE 00010 Planned date of rule executio
Rdr-Date
JBR
JBRRINDT DATE 00010 Job Read-in Date
Rld-Date
JBR
JBRRLDDT DATE 00010 Reload date of job
Start Date
JBR
SRCSTRTD DATE 00010 Source Start Date
Submit Date
JBR
SRCSUBD DATE 00010 Source Submit Date
******************************* Bottom of data ********************************
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
84
General (Option A.1)
_beta log|z layouts (Option A.1.1)
6. Enter the line command S in front of the field you want to use and
press ENTER. For the example search layout "MIXED_SEARCH",
these fields are left blank.
The panel may now look as follows for the example mixed search
layout:
PE92LD22 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Insert Search Layout - General Fields
Layout Name
Search Location
Category
===> MIXED_SEARCH....
===> ONLINE.
===> ALL.....
(O)nline or (A)rchive
(HO)stJob, (FI)leRule, (SA)PJob,
(EV)ent, (AL)l
Language
===> E
(E)nglish or (G)erman
Panel Title
===> Mixed Search......................................
Description
===> Mixed Search for Host/File/SAP/Event______________
===> ______________
Job Result Layout ===> ALL_JOB_HITS.... (* for list)
Log Result Layout ===> ALL_LOG_HITS____ (* for list)
Optional Date and Time Search Parameters
Date Field
===> End Date________
Time Field
===> End Time________
Input Optional
===> YES
(* for list)
(* for list)
(Y)es or (N)o
Press ENTER key to insert this entry.
Press END key to cancel changes or HELP key for help information.
7. Press ENTER to save the entries in the general fields.
The search layout is saved and displayed in the Search Layout table.
8. Enter the line command F in front of the inserted search layout "Mixed
Search".
The "Insert Search Criterion" panel appears:
PE92LD26 ------------------------------------------------------- No data found
Command ===> ________________________________________________________________
Insert Search Criterion
Layout Name
Search Location
Category
Language
:
:
:
:
MIXED_SEARCH
ONLINE
ALL
E
Field Name
===> ................
Label
===> ....................
Length of Input Field ===> ..
Position in Search Panel
Line
===> ..
Column
===> .
Attributes of Search Criterion
Mandatory
===> ...
Uppercase only
===> ...
(* for list)
(1 - 50)
(1 - 99)
(1 or 2)
(Y)es or (N)o
(Y)es or (N)o
Press ENTER key to insert this entry.
Press END key to cancel changes or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
85
General (Option A.1)
_beta log|z layouts (Option A.1.1)
9. Enter an asterisk * in the field Field Name and press ENTER.
The "Insert Search Criterion - Data Column List" panel is displayed:
PE92LD2A -------------------------------------------------------- Row 1 of 129
Command ===> ________________________________________________ Scroll ===> PAGE
Insert Search Criterion - Data Column List
S - Select
Please Select a Data Column
Sel Field Name
DB Table DB Field Type Lngth Description
Additional Args
FLAG 00004 Additional Arguments
Agent
JBRE
AGENAME CHAR 00008 Agent Name
Agent Group
JBRE
AGRPNAME CHAR 00024 Agent Group Name
Archive List Flg JLR
JLRSTFAR FLAG 00007 List archived
Archived Flag
JBR
JBRARFAR FLAG 00003 Job archived
AAL Comment
EVT01
AALCOMM CHAR 00080 AAL Comment (Event01)
AAL Event ID
EVT01
EVTID
INT 00005 AAL Event ID for events of si
AAL Event Token EVT01
EVTTOKEN INT 00032 AAL Unique Event Token (Event
AAL Field1
EVT01
AALFLD1 CHAR 00008 AAL Field1 (Event01)
AAL Field2
EVT01
AALFLD2 CHAR 00008 AAL Field2 (Event01)
AAL Field3
EVT01
AALFLD3 CHAR 00010 AAL Field3 (Event01)
AAL Field4
EVT01
AALFLD4 CHAR 00008 AAL Field4 (Event01)
AAL Input Date
EVT01
EVTINPDT DATE 00010 AAL Input Date (Event01)
AAL Input Time
EVT01
EVTINPTM TIME 00011 AAL Input Time (Event01)
A list of the fields available for the layout type and location is
displayed.
10. Press PF8 to display more fields.
11. Enter the line command S in front of a field, e.g. Jobname, and press
ENTER to display the "Insert Search Criterion" panel:
PE92LD26 ---------------------------------------------------------------------Command ===> ________________________________________________________________
Insert Search Criterion
Layout Name
Search Location
Category
Language
:
:
:
:
MIXED_SEARCH
ONLINE
ALL
E
Field Name
===> Jobname.........
Label
===> Jobname.............
Length of Input Field ===> 08
Position in Search Panel
Line
===> ..
Column
===> .
Attributes of Search Criterion
Mandatory
===> ...
Uppercase only
===> ...
(* for list)
(1 - 50)
(1 - 99)
(1 or 2)
(Y)es or (N)o
(Y)es or (N)o
Press ENTER key to insert this entry.
Press END key to cancel changes or HELP key for help information.
You must decide the length of the input field, the position in the search
panel and the attributes of the search field.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
86
General (Option A.1)
_beta log|z layouts (Option A.1.1)
12. Enter the following for the field Jobname:
PE92LD26 ---------------------------------------------------------------------Command ===> ________________________________________________________________
Insert Search Criterion
Layout Name
Search Location
Category
Language
:
:
:
:
MIXED_SEARCH
ONLINE
ALL
E
Field Name
===> Jobname.........
Label
===> Jobname.............
Length of Input Field ===> 08
Position in Search Panel
Line
===> 01
Column
===> 1
Attributes of Search Criterion
Mandatory
===> NO.
Uppercase only
===> YES
(* for list)
(1 - 50)
(1 - 99)
(1 or 2)
(Y)es or (N)o
(Y)es or (N)o
Press ENTER key to insert this entry.
Press END key to cancel changes or HELP key for help information.
13. Press ENTER to save your entries.
14. Next select the fields Rulename, Agent, Job ID and Queue Type for
the mixed search layout example.
15. Enter the line command F in front of the new mixed search layout in
the Search Layout table.
The "Search Criterion Table of Layout ..." panel with the following
definitions is displayed for the example:
PE92LD25 -------------------------------------------------- Row
1 of
5
Command ===> ________________________________________________ Scroll ===> PAGE
Search Criterion Table of Layout MIXED_SEARCH
Layout: MIXED_SEARCH
S - Select
Lang: E
I - Insert
Location: ONLINE
Category: ALL
C - Copy
D - Delete
Sel Field Name
Label
Length Line Column Mand. UCase
Jobname
Jobname
08
01
1
NO
YES
Rulename
Rule
08
02
1
NO
YES
Agent
Agent
08
03
1
NO
YES
Job ID
Job ID
08
04
1
NO
YES
Queue Type
Queue Type
08
05
1
NO
YES
******************************** BOTTOM OF DATA ********************************
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
87
General (Option A.1)
Fields
_beta log|z layouts (Option A.1.1)
Field
Description
Field Name
This name identifies the layout field to which this search
criterion is connected.
Label
Here you can specify the label for the search criterion.
Length of Input Field
Specify the length (1..50) of an input field. This value
must not exceed the maximal length of 50 and must not
exceed the maximal length of the layout field. For more
information on screen page size defaults, see "Defaults
for search layouts" on page 89.
Position in Search
Panel: Line
Specify the line (1..99) on which the search criterion is
to be positioned in the selection panel. To position the
field directly below the time parameters specify line 1.
For more information on screen page size defaults, see
"Defaults for search layouts" on page 89.
Column
Specify 1 to position the field on the left side of the
panel. Or specify 2 to position it on the right side.
Attributes of Search
Criterion
Mandatory
Enter Yes to determine that an input in this field is
required. Enter No if this is to be an optional field.
Uppercase only
Line commands
Note on flag fields: If a flag field (for example, archived
flag or error flag) is defined with Mandatory = Yes, the
user must enter either Yes or No when using the layout.
This makes it impossible to get both types of entries, i.e.
entries flagged Yes and entries flagged No. To enable
the selection of both, it must be possible to leave the
flag field blank, which means that Mandatory must be
No.
Enter Yes to convert input to uppercase. If not enter No.
S
Displays a field definition
I
Inserts a layout field
C
Copies a layout field
D
Deletes a layout field
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
88
General (Option A.1)
_beta log|z layouts (Option A.1.1)
Defaults for search layouts
Panel layout
PANEL HEADER
COMMAND LINE
BLANK
PANEL TITLE
BLANK
SELECT from Last
SELECT from Date/Time
SELECT from Date/Time
1. USER LAYOUT LINE
…
<
>
Example:
Label left
20
Label left
20
FIXED UPPER PART OF THE PANEL
MAX. WIDTH: 80 CHARACTERS
Delimiter
6
Delimiter
6
Field left Blank Label right
10
2
17
Field long
50
Field right
16
max. 99 USER LAYOUT LINES allowed, displayed on 1 screen panel: 13 LINES
BLANK
FIXED LOWER PART OF THE PANEL
ACTION STATEMENT
ACTION STATEMENT
Info rows
The upper part of every selection panel displays information that cannot be
changed. It consists of the panel header, the command line, one blank
line, the panel title defined in the layout, one further blank line and the
three "Select from last", "Select from Date/Time" and "Select to Date/Time"
lines. This means that row 9 is the first row in the panel that can be
changed.
At the bottom of the panel there are three additional rows reserved for a
blank line and the action statements.
Panel size
One screen of a panel normally consists of 24 lines in length and 80
characters in width.
Selection criteria
A maximum of 99 rows can be defined as search criteria.
You can leave blank lines between individual search criteria.
Note: If you want to include some lines in a defined layout later on, you will
need to renumber all of the lines.
Scrolling
If more selection criteria have been defined than fit on the screen, you can
scroll up and down using PF7 and PF8.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
89
General (Option A.1)
Length of definable fields
_beta log|z layouts (Option A.1.1)
Field left
=>
10 characters
Field right
=>
16 characters
Field single
=>
50 characters
The limit on the left field is only valid when another field is to be positioned
to the right of it. Fields on the left side of the panel can be a maximum of
10 characters long and fields on the right side a maximum of 16 characters
long. Fields can also cover the entire width of the panel; these fields can
be a maximum of 50 characters long.
Fields cannot extend over several lines. This means that the Long Host
Name field only allows for the entry of one row with a max. of
50 characters.
If the length of the criterion entered in the left field is too long, no righthand field can be defined for this row.
An entry for a selection criterion must not be longer than the maximum
predefined length for this field (max. field length <= database field length).
Multiple identical fields
If several fields have been defined for the same database field in a layout,
they are linked by OR (for example, fields Jobname1 - Jobname4).
Additional arguments
The additional arguments field can be defined like any other selection
criterion. The additional arguments panel is however subsequently hidden,
cannot be changed, and always looks the same.
Note: Additional arguments cannot be displayed by _beta view.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
90
General (Option A.1)
_beta log|z layouts (Option A.1.1)
Result layouts (Option A.1.1.3)
Displaying result layouts
Procedure
To display result layouts:
1. In the "Primary Selection Menu", enter A.1.1 to display the "Layout
Definitions Selection Menu".
2. Enter 3 for "Result Layouts" and press ENTER.
The "Result Layout Definition Selection" panel is displayed:
PE92LD03 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Result Layout Definition Selection
Layout Name
Search Location
Category
Result Type
Language
===> *...............
===> ONLINE_
(O)nline or (A)rchive
===> ________
(HO)stJob, (FI)leRule, (SA)PJob,
(EV)ent, (SY)slog, (AL)l
===> JOBRESULT
(J)obResult or (L)ogResult
===> _
(E)nglish or (G)erman
Panel Title
===> __________________________________________________
Press ENTER key to display result layouts.
Press END key to return to the previous menu.
3. Enter the selection criteria you want to use (see the table of fields
below).
For example, enter an asterisk * in the field Layout Name, Online in
the field Search Location, and press ENTER:
PE92LD30 -------------------------------------------------- Row
1 of
17
Command ===> ________________________________________________ Scroll ===> PAGE
Result Layout Table
S - Select
F - Display Fields
Sel
I - Insert
C - Copy
D - Delete
CF - Copy with Fields
Name
L Typ Category Location Panel Title
BETA_EVNT_RESULT E JOB EVENT
ONLINE
Event Select Table
BETA_EVNT_RESULT G JOB EVENT
ONLINE
Event-Auswahltabelle
BETA_EV01_RESULT E JOB EVENT
ONLINE
Activity Audit Log Table
BETA_EV01_RESULT G JOB EVENT
ONLINE
Activity Audit Log Tabelle
BETA_FILR_RESULT E JOB FILERULE ONLINE
File Rule Select Table
BETA_FILR_RESULT G JOB FILERULE ONLINE
File-Regel Auswahltabelle
BETA_HSTJ_RESULT E JOB HOSTJOB ONLINE
Job Select Table
BETA_HSTJ_RESULT G JOB HOSTJOB ONLINE
Job-Auswahltabelle
BETA_SAML_RESULT E JOB HOSTJOB ONLINE
SAM Log Select Table
BETA_SAML_RESULT G JOB HOSTJOB ONLINE
SAM-Log-Auswahltabelle
BETA_SAMR_RESULT E JOB HOSTJOB ONLINE
SAM Report Select Table
BETA_SAMR_RESULT G JOB HOSTJOB ONLINE
SAM-Report-Auswahltabelle
BETA_SAPJ_RESULT E JOB SAPJOB
ONLINE
SAP Job Select Table
BETA_SAPJ_RESULT G JOB SAPJOB
ONLINE
SAP-Job Auswahltabelle
BETA_SYSL_RESULT E JOB SYSLOG
ONLINE
Syslog Select Table
The "Result Layout Table" shows all the default online result layouts.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
91
General (Option A.1)
_beta log|z layouts (Option A.1.1)
4. For example, enter line command S in front of the result layout
"BETA_HSTJ_RESULT", and press ENTER.
The "Display Result Layout-General Fields" panel is displayed:
PE92LD31 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Display Result Layout-General Fields Last update: BETAINST 09/01/2004 12:00:00
Layout Name
Search Location
Category
: BETA_HSTJ_RESULT
: ONLINE
: HOSTJOB
ID :
0000000001
Result Type
Language
: JOBRESULT
: E
Panel Title
Description
: Job Select Table
: Default Layout for Select Table of Host Jobs
:
Press DOWN key to display layout columns.
Press END key to return to previous panel or HELP key for help information.
Because this is an installation default layout, this panel is purely
informational and cannot be changed.
When you display one of the layouts that you have created, an update
panel comes up automatically.
Fields
Field
Description
Layout Name
Enter a specific result layout name or use a mask. You
can find an overview of the default result layout names
in "Result layouts (Option A.1.1.3)" on page 91.
Search Location
The location of layouts can be (O)nline or (A)rchive.
Enter one of the location types to select either online
layouts or archive layouts.
Category
Enter (HO)st Job, (FI)leRule, (SA)PJob, (EV)ent,
(SY)slog, or (A)ll to display layouts belonging to this
category. ALL displays layout that can be used for more
than one category. If you leave the field blank, all
layouts of all categories will be displayed.
Result Type
Enter (J)obResult or (L)ogResult to display only result
layouts of the selected type.
Note: Log result layouts were supported by the former
add-on Beta 92 Enterprise User Interface (EUI). They
are now obsolete.
Language
Enter E for English or G for German to display only
result layouts of the selected language.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
92
General (Option A.1)
Line commands
_beta log|z layouts (Option A.1.1)
S
Displays a result layout
F
Displays a table containing all fields allowed to be used within the
specific result layout
Here you can directly insert or delete columns by entering or
deleting position numbers for columns, or you can change column
properties.
To display the table, you can use the line command F or press PF8
in the table of displayed fields.
I
Inserts a result layout
C
Copies a result layout without fields
CF
Copies a result layout with all columns belonging to the layout
Note: The result layout to be inserted must use the same result
location, category, and result type as the result layout to be copied.
D
Deletes a result layout
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
93
General (Option A.1)
_beta log|z layouts (Option A.1.1)
Changing result layouts
Overview
We recommend that you copy an existing result layout with all of its
columns so that you can practice changing a result layout before you insert
a new one. Beta-defined layouts cannot be changed or deleted but you
can copy them and then alter them. First decide which result layout you
want to use, for example, BETA_HSTJ_RESULT, language E.
Note: Before you copy and change result layouts later on, check first in
which search layout the specific result layout is used. Display, for example,
all online and English search layouts under option A.1.1.2 and scroll to the
right using PF11 in the "Search Layout Table" panel.
PE92LD20 -------------------------------------------------- Row
1 of
9
Command ===> ________________________________________________ Scroll ===> PAGE
Search Layout Table
S - Select
I - Insert
F - Display Fields of this Layout
C - Copy
D - Delete
CF - Copy with Fields
Sel
Name
L JOBRESULT Layout LOGRESULT Layout Description
BETA_EVNT_SEARCH E BETA_EVNT_RESULT
BETA_EV01_SEARCH E BETA_EV01_RESULT
BETA_FILR_SEARCH E BETA_FILR_RESULT BETA_FILL_RESULT Default Layout für
BETA_HSTJ_SEARCH E BETA_HSTJ_RESULT BETA_HSTL_RESULT Default Layout for
BETA_SAML_SEARCH E
Default Layout for
BETA_SAMR_SEARCH E
Default Layout for
BETA_SAPJ_SEARCH E BETA_SAPJ_RESULT BETA_SAPL_RESULT Default Layout for
BETA_SYSL_SEARCH E BETA_SYSL_RESULT
Default Layout for
MY_HSTJ_SEARCH1 E BETA_HSTJ_RESULT BETA_HSTL_RESULT My First Layout for
******************************** BOTTOM OF DATA ********************************
Here you can check to which search layouts the specific result layout is
connected to.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
94
General (Option A.1)
Procedure
_beta log|z layouts (Option A.1.1)
To change a result layout:
1. Display the "Result Layout Table". The procedure is described in
"Result layouts (Option A.1.1.3)" on page 91.
2. In the "Result Layout Table" enter the line command CF, for example,
in front of the result layout BETA_HSTJ_RESULT, language E and
press ENTER.
The "Insert Result Layout - General Fields" panel is displayed:
PE92LD32 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Insert Result Layout - General Fields
Layout Name
Search Location
Category
===> BETA_HSTJ_RESULT
: ONLINE
: HOSTJOB
Result Type
Language
: JOBRESULT
===> E
Panel Title
Description
===> Job Select Table.......................
===> Default Layout for Select Table of Host Jobs______
===> ______________
(E)nglish or (G)erman
Press ENTER key to insert this entry and proceed with the column definition.
Press END key to cancel changes or HELP key for help information.
The line command CF copies a result layout with all columns
belonging to the layout. Due to the fact that copied result layouts must
use the same search location and category as the result layout to be
copied, you cannot change the contents of the fields Search Location
and Category.
3. Enter a new layout name, for example, MY_HSTJ_RESULT1, the
search location, the category, the result type, the language, the panel
title, the description, and press ENTER.
The "Result Layout Columns Table for Layout ..." panel comes up:
PE92LD35 --------------------------------------------------- Insert successful
Command ===> ________________________________________________ Scroll ===> PAGE
Result Layout Columns Table for Layout MY_HISTJ_RESULT1
Pos = Column position
Len = Column length
H = Hold column on all pages
A
= Attribute: (H)ighlighted, (R)ight justified, (B)oth H and R
Layout:
Sel.Jobname . Job ID .
Date
. Time . Status . Error . User .Jobgroup
Sel.Jobname .Runtime . Rdr-Date .Rdr-Time. Rld-Date . Net ID .Cls.Msgcl.System.
Pos A H Len DefL Header
App Append Header
Description
01 _ Y 8_ 8
Jobname_____________ _ ____________________ Source Jobname
02 _ _ 8_ 8
Job ID_____________ _ ____________________ JES Job ID
03 _ _ 10 10
Date_____________ Y Searched Date/Time__ Searched Date: D
04 _ _ 8_ 11
Time______________ _ ____________________ Searched Time: D
05 _ _ 10 10
Status____________ _ ____________________ Beta 92 Status
06 H _ 8_ 8
Error______________ _ ____________________ Job Error Text
07 _ _ 8_ 8
User______________ _ ____________________ Job assigned to
08 _ _ 8_ 8
Jobgroup____________ _ ____________________ assigned Jobgrou
09 _ _ 10 10 Runtime_____________ _ ____________________ Job Runtime
10 _ _ 10 10
Rdr-Date___________ Y Read________________ Job Read-in Date
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
95
General (Option A.1)
_beta log|z layouts (Option A.1.1)
A message displayed on the upper right of the panel informs you that
the insertion of the changed job result layout has been successful.
Now you can alter the columns used by this job result layout. Above
the table with the available columns a preview of the defined result
layout is displayed which is refreshed or updated each time you press
ENTER.
4. Press PF8 to display more available columns for the result layout.
5. Enter new columns if you want to.
Note: If you include new columns, you must renumber all columns in
use. Duplicate positions will be prevented.
6. Finally press ENTER and PF3 to leave the panel.
The "Confirm Changes of Result Layout Columns" panel appears:
PE92LD3X -------------------------------------------- Layout changes not saved
Command ===> ________________________________________________________________
Confirm Changes of Result Layout Columns
Result Layout
:
MY_HISTJ_RESULT1
Do you want to save your changes of Result Layout Columns?
Save
===> .
(Y/N)
Press ENTER key to confirm your request.
Press END key to abort your request or HELP key for help information.
7. Enter Yes if you want to save your changes in the new job result
layout.
8. In the Result Layout table, enter the line command F in front of the
changed job result layout to display the columns used in the layout.
9. To use this job result layout for your requests, specify it in a search
layout under option A.1.1.2.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
96
General (Option A.1)
Layout columns
_beta log|z layouts (Option A.1.1)
Columns
Description
Pos
The position of the column in the result layout can be
determined here. Only fields with position numbers will be used
as columns in the result layout.
A
The following attributes of a field can be defined: (H)ighlighted,
(R)ight justified, (B)oth - highlighted and right justified.
H
Enter (Y)es if you want to hold the column on all displayed
table pages when scrolling. A column can only be defined as a
hold column when it is located on the first table layout page.
Otherwise leave the field blank.
Len
Enter the length (max. 70) of the respective column.
DefL
The default column length is displayed here for your
information.
Header
Enter a text used for the column header.
App
Append Header
These two fields were only relevant for the former add-on
Beta 92 EUI and are now obsolete.
Description
Enter a descriptive text.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
97
General (Option A.1)
_beta log|z layouts (Option A.1.1)
Inserting a job result layout
Overview
A job result layout definition specifies which columns are to be displayed in
the table displayed as a result of a search.
Note: Log result layouts were supported by the former add-on Beta 92
Enterprise User Interface (EUI). They are now obsolete.
Before you start
•
First look at all the (general fields and) columns available and write
down the ones you want to output, and their length.
•
Determine which columns are to appear on each screen during
scrolling. These are known as "hold columns".
We recommend that you use these columns as the first columns in the
layout, because they automatically shift from the right to the left during
scrolling.
•
Determine the remaining entries and position the columns so that the
screen length of 80 characters is divided effectively. Up to 3 screens or
3 table pages can be filled.
The hold columns appear on every screen, so they must also be taken
into account when establishing the length of each screen. They are
specified only once. It is possible to display only a part of a field. If a
field is only partly displayed, it will be truncated on the right. Please
make sure that this makes sense. A length of 6 is only suitable for date
columns if you are working exclusively with a Julian date format with a
two-digit year date.
•
Number the columns.
•
Enter the new result layout as described below.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
98
General (Option A.1)
Procedure
_beta log|z layouts (Option A.1.1)
To insert a job or log result layout:
1. Displaying the "Result Layouts Table". The procedure is described in
"Result layouts (Option A.1.1.3)" on page 91.
2. In the Result Layout table, enter the line command I in front of any
result layout and press ENTER.
The "Insert Result Layout - General Fields" panel is displayed:
PE92LD32 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Insert Result Layout - General Fields
Layout Name
Search Location
Category
===> ................
===> .......
(O)nline or (A)rchive
===> ........
(HO)stJob,(FI)leRule,(SA)PJob,(EV)ent,(AL)l
Result Type
Language
===> .........
===> .
Panel Title
Description
===> .......................................
===> __________________________________________________
===> ______________
(J)obResult or (L)ogResult
(E)nglish or (G)erman
Press ENTER key to insert this entry and proceed with the column definition.
Press END key to cancel changes or HELP key for help information.
3. Enter the general fields for the new result layout.
Example: new layout name ALL_JOB_HITS, search location Online,
category All, result type Job result, language E, the panel title "All
Category Hit List", and the description "All Category Hit List" and press
ENTER.
The "Result Layout Columns Table for Layout ..." panel is displayed:
PE92LD35 --------------------------------------------------- Insert successful
Command ===> ________________________________________________ Scroll ===> PAGE
Result Layout Columns Table for Layout ALL_JOB_HITS
Pos = Column position
Len = Column length
H = Hold column on all pages
A
= Attribute: (H)ighlighted, (R)ight justified, (B)oth H and R
Layout:
Sel.
Pos A H Len DefL Header
App Append Header
Description
.. _ _ 8_ 8
Agent_______________ _ ____________________ Agent Name
.. _ _ 24 24 Agent Group_________ _ ____________________ Agent Group Name
.. _ _ 70 70 AAL Comment_________ _ ____________________ AAL Comment (Eve
.. _ _ 5_ 5
AAL Event ID________ _ ____________________ AAL Event ID for
.. _ _ 32 32 AAL Event Token_____ _ ____________________ AAL Unique Event
.. _ _ 8_ 8
AAL Field1__________ _ ____________________ AAL Field1 (Even
.. _ _ 8_ 8
AAL Field2__________ _ ____________________ AAL Field2 (Even
.. _ _ 10 10 AAL Field3__________ _ ____________________ AAL Field3 (Even
.. _ _ 8_ 8
AAL Field4__________ _ ____________________ AAL Field4 (Even
.. _ _ 10 10 AAL Input Date______ _ ____________________ AAL Input Date (
A message displayed on the upper right-hand side of the panel
informs you that the insertion of the new result layout has been
successful.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
99
General (Option A.1)
_beta log|z layouts (Option A.1.1)
4. Select the columns to be added to your result layout by entering a
position number in the corresponding column.
The following applies:
•
Only fields with position numbers will be used as columns in the
result layout. You can scroll through the table using PF7/PF8.
When you define a log result layout, the number of available
columns is higher because it includes both job-specific and log/listspecific information.
•
When you press ENTER, columns with position numbers are
moved to the beginning of the table, where they are arranged
according to their position. A preview of the defined result layout is
displayed below Layout.
•
Position numbers need not be consecutive while you are defining
the layout. Columns will be numbered consecutively during Save.
If want to insert a new column at a later point, you will have to
renumber the columns in use. Duplicate positions will be
prevented.
After you have finished selecting the columns, the result layout could
look like the following:
PE92LD35 -------------------------------------------------------- Row 1 of 112
Command ===> ________________________________________________ Scroll ===> PAGE
Result Layout Columns Table for Layout ALL_JOB_HITS
Pos = Column position
Len = Column length
H = Hold column on all pages
A
= Attribute: (H)ighlighted, (R)ight justified, (B)oth H and R
Layout:
Sel.Host-Job.SAP-Job Name
.SAP-Job Count.Rule Group
.Rule
.Agent
Sel.Operation.Submit D .Submit T.Start D
.Start T .End Date .End Time.
Sel.Search D .Search T.Status
.User
.Job Group.Runtime .Reader D .
Pos A H Len DefL Header
App Append Header
Description
01 _ _ 8_ 8
Host-Job Name_______ _ ____________________ Source Jobname
02 _ _ 17 32 SAP-Job Name________ _ ____________________ Long Job Name
03 R _ 13 8
SAP-Job Count_______ _ ____________________ SAP Job Count
04 _ _ 16 24 Rule Group__________ _ ____________________ Rule Group Name
05 _ _ 8_ 8
Rule________________ _ ____________________ File / SAP Rule
06 _ _ 8_ 8
Agent_______________ _ ____________________ Agent Name
07 _ _ 8_ 8
Operation___________ _ ____________________ File / SAP Opera
08 _ _ 10 10 Submit D____________ Y Submitted___________ Source Submit Da
09 _ _ 8
11 Submit T____________ _ ____________________ Source Submit Ti
10 _ _ 10 10 Start D_____________ Y Started_____________ Source Start Dat
11 _ _ 8
8
Start T_____________ _ ____________________ Source Start Tim
12 _ _ 10 10 End Date____________ Y Ended_______________ Source End Date
13 _ _ 8
8
End Time____________ _ ____________________ Source End Time
14 _ _ 10 10 Search D____________ Y Searched____________ Searched Date: D
15 _ _ 8
11 Search T____________ _ ____________________ Searched Time: D
16 _ _ 10 10 Status______________ _ ____________________ Beta 92 Status
17 _ _ 8
8
User________________ _ ____________________ Job assigned to
18 _ _ 9
8
Job Group___________ _ ____________________ assigned Jobgrou
19 R _ 10 10 Runtime_____________ _ ____________________ Job Runtime
20 _ _ 10 10 Reader D____________ Y Read________________ Job Read-in Date
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
100
General (Option A.1)
_beta log|z layouts (Option A.1.1)
5. Press ENTER and then PF3 to leave the panel.
The "Confirm Changes of Result Layout Columns" panel appears:
PE92LD3X -------------------------------------------- Layout changes not saved
Command ===> ________________________________________________________________
Confirm Changes of Result Layout Columns
Result Layout
:
ALL_JOB_HITS
Do you want to save your changes of Result Layout Columns?
Save
===> .
(Y/N)
Press ENTER key to confirm your request.
Press END key to abort your request or HELP key for help information.
6. Enter Y to save your changes in the new result layout.
To verify your result layout, you can enter the line command F in front
of the new result layout displayed in the "Result Layout Table". To use
the job or log result layout for your requests, specify its name in the
corresponding search layout under option A.1.1.2.
Layout columns
Column
Description
Pos
The position of the column in the result layout can be
determined here. Only fields with position numbers will be
used as columns in the result layout.
A
The following attributes of a field can be defined: (H)ighlighted,
(R)ight justified, (B)oth - highlighted and right justified.
H
Enter (Y)es if you want to hold the column on all displayed
table pages when scrolling. A column can only be defined as a
hold column when it is located on the first table layout page.
Otherwise leave the field blank.
Len
Enter the length (max. 70) of the column.
DefL
The default column length is displayed here for your
information.
Header
Enter a text used for the column header.
App
Append Header
These two fields were only relevant for the former add-on
Beta 92 EUI and are now obsolete.
Description
Here you can enter a descriptive text.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
101
General (Option A.1)
_beta log|z layouts (Option A.1.1)
Defaults for result layouts
User layout (Option P.7)
If users create their own user layout under option P.7, this user layout will
be used for the Job Select table display (and only there).
Screen panel
size defaults
On one screen normally 24 lines in length and 80 characters in width can
be displayed.
Panel layout
<
>
The
first
5 characters
are
reserved
for the
selection
column
(blank SEL blank)
<
>
Table Columns must fit onto max. 3 panel screens: 3 x 80 characters
< reserved 5 char. + a max. column length of 70 can be displayed on one screen
>
Max. number of columns
in a table
The maximum number of table columns that can be displayed in a layout is
limited to the number that fit onto 3 panel screens.
Scrolling
If the table layout is too big for a single screen, you can scroll from right
(PF11) to left (PF10).
On column width
In contrast to the search layout, you can enter a length larger than the
maximal length defined in the layout field definition - as long as the entry
does not exceed the maximal length of 70 characters. We recommend in
any case that you define the width of 'small' columns to be no longer than
the title.
Note: If the last column of a screen has the attribute of being right aligned
or both (left and right aligned), it is a character longer than the one with the
left aligned attribute or the one that is highlighted.
Holding columns on all
screens during scrolling
Layout columns marked with Yes in the column Hold are held on all
screens, otherwise it would not be possible to display the same database
field several times in a table.
App and Append Header
The two fields App and Append Header were only relevant for the former
add-on Beta 92 EUI and are now obsolete.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
102
General (Option A.1)
Job group (Option A.1.2)
Job group (Option A.1.2)
Overview
A job group is a collection of jobs with similar properties. _beta log|z uses
job groups for the following purposes:
•
Determining the online and archive retention period of job records and
lists
•
Selecting jobs for display in the Job Select table and checking
authorization (deny/grant access to job logs)
You can define a maximum of 512 job groups.
Assigning jobs to job
groups
Jobs can be assigned to job groups based on the following:
•
Via the job name
Define one or more job masks for each job group if you want to assign
jobs to the groups via the job name. See "Best match or longest
retention" on page 119 for more information.
•
Via the message class
Specify Class Processing Active = Yes in the reader class definition
together with the name of a job group if you want to assign all jobs of
this class to a specific job group. See "Sysout class processing" on
page 121 for more information.
Navigation
From the "Primary Selection Menu", choose:
•
Option A.1.2
The "Job Group Definition Selection" panel is displayed, in which you
can enter your selection criteria.
Insert Job Group
Definition panel
This panel enables you to create a new job group definition.
PE92DF23 --------------------------------------------------------------------Command ===> ________________________________________________________________
Insert Job Group Definition
Job Group
===> ........
Title
===> ________________________________________
Archive Retention
Period (in days)
| Onl. Reten| tion Periods
Archive
Media
| Online
| Type
===> .....
===> .....
Queues
Input Ready Error Work
Job Job
Info Record
===> .... .... .... .... ....
===> ..... ..... ..... ..... Days
....
.....
Pool (opt.) ===> ________ | Max. Online RETPD for Generations ===> ____ Days
Press ENTER key to insert this entry and continue.
Press END key to cancel changes or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
103
General (Option A.1)
Fields
Job group (Option A.1.2)
Field
Description
Job Group
Name of the job group (max. 8 characters)
Title
A title is a descriptive name that helps to identify the
group. This field is optional.
Archive (retention
period)
Specify how long the lists and the job records of this job
group should be kept in the archive. The archive
retention period is defined in calendar days and is
counted from the day of the archive run.
The archive retention period of an archived job cannot
be shorter than its online retention period. Specify 0 if
you do not want to archive the jobs of a job group.
Note: Other ways of preventing that a list is archived
are: using the OMS keyword NOSAVE in the JCL,
changing keep status using line command X, or defining
the output class as NOSAVE.
Media
Specify the archive medium: Tape, Disk, Filet (FileTek),
or ODISK (optical disk).
Pool (opt.)
Optionally, you can specify the name of an existing
archive pool if you want to assign the job group to this
pool. The retention period of the archive pool must be
higher than or equal to the archive retention period of
the job group.
Leave this field blank if you want _beta log|z to choose
the pool automatically.
Archive pools are defined under option A.A.1 (see
"Defining archive pools (Option A.A.1)" on page 206.
For more information on archiving, see "Archiving
concept" on page 193.
Dedicated/Client archive pools
The definition of archive pools as dedicated pools, i.e.
client archive pools, enables you to archive the data of
multiple clients in separate pools. _beta log|z does not
use dedicated/client archive pools for other job groups.
When a dedicated archive pool has been assigned to a
job group and is now used as a client archive pool,
archiving in this pool is only allowed via client job
groups.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
104
General (Option A.1)
Job group (Option A.1.2)
Field
Description
Online (retention
periods) and Type
In the Online field under each queue (Input, Ready,
Error, and Work), specify how long the lists of a job
should be kept online if the job is in this queue. The
corresponding Type field determines whether the value
refers to number of workdays (Days) or number of
generations (Gener).
All queues with Type=Gener must have the same value
in the Online field. Retention periods can be different if
Type=Days. The number of workdays is specified under
option A.S.3 (see "Global options (Option A.S.3)" on
page 230).
The value under Job Info determines the online
retention period of the job information records in
workdays. 0 means that the job info is deleted when the
lists are deleted or when the job base record is deleted
The value under Job Record determines the online
retention period of the job base record. This retention
period cannot be shorter than the retention period of a
queue or of the job info. The retention period must be
specified in workdays if Job Info > 0.
Max. Online RETPD for Specify the maximum number of days that a list is to be
Generations
held online if its online retention period is specified in
number of generations (Type=Gener).
You can use this field to avoid that list generations are
held online forever, for example, if a job has been
renamed or if it does no longer run on a regular basis.
Allowed: 1..9999
Default: Value from the Max. Online RETPD for
Generations field under option A.S.3 (see "Global
options (Option A.S.3)" on page 230).
For examples on defining retention periods in workdays, generations, or a
mixture of both, see "Retention period in workdays" on page 114.
Line commands
The following line commands are available in the "Job Group Definition
Table".
S
Selects the job group definition for display or update
D
Deletes the job group definition
I
Inserts a new job group definition (insert)
C
Inserts a new job group definition (copy)
M
Displays all job masks belonging to the job group definition
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
105
General (Option A.1)
Job group (Option A.1.2)
Defining job masks for job groups
Overview
Jobs that don't undergo class processing are assigned to job groups by
matching the job name against the existing job mask definitions.
Define one or more inclusive job masks for each job group. You can also
define one exclusive job mask for each job group.
For more information on how jobs are assigned to job groups, see
"Assigning jobs to job groups" on page 117.
Navigation
To define a new job mask for a job group:
1. Under option A.1.2, select and display the job groups in the "Job
Group Definition Table".
2. Enter line command M in front of the desired job group.
If the job group already has job mask definitions, the "Job Masks of
Job Group..." table is called. Otherwise, the "Insert Job Mask
Definition" panel will be called instead.
PE92DF24 -------------------------------------------------- Row
1 of
2
Command ===> ________________________________________________ Scroll ===> PAGE
Job Masks of Job Group BXW
S - Select Job Mask Definition
I - Insert Job Mask Definition
D - Delete Job Mask Definition
Sel Job Mask Excl
TB92*
NO
TB93*
NO
******************************** BOTTOM OF DATA *******************************
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
106
General (Option A.1)
Job group (Option A.1.2)
3. Enter line command I in front of any entry to display the "Insert Job
Mask Definition" panel:
PE92DF25 ---------------------------------------------------------------------Command ===> ________________________________________________________________
Insert Job Mask Definition
Job Group
: TEST
Job Mask
===> ........
Exclusive
===> ....
(Y)es or (N)o
Press ENTER key to insert this entry and continue.
Press END key to cancel changes or HELP key for help information.
4. Type your values in the fields and press ENTER.
Fields
Line commands
Field
Description
Job Group
The name of the job group is displayed.
Job Mask
The mask may contain the wildcard question mark ?,
the wildcard percent sign %, or the wildcard asterisk *.
Question mark and percent sign represent any single
character and have a higher priority than *.
Exclusive
No to assign all jobs matching the job mask to the job
group. Yes to assign all jobs that do not match the job
mask to the group. (The examples in the following
section illustrate how to use this parameter.)
Note: Only one mask is allowed to be EXCLUSIVE.
S
Selects the job mask definition for display or update
D
Deletes the job mask definition
I
Inserts a new job mask definition
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
107
General (Option A.1)
Job group (Option A.1.2)
Determining the best matching job group
Overview
_beta log|z job selection/display and security functions always use the
best-match principle when working with job masks. _beta log|z archive and
cleanup utilities can assign jobs to job groups based on best-match or
longest retention.
Hierarchy
_beta log|z evaluates the jobname against the job masks of all job groups
and determines the best match according to the following hierarchy:
1. Inclusive/Exclusive job masks
A job mask with EXCLUSIVE flag not set is a better match than a job
mask with EXCLUSIVE flag set.
2. Number defined characters (incl. blank if no asterisk)
A job mask with a higher number of defined characters is a better
match than a job mask with a lower number of defined characters.
3. Positions of defined characters
A job mask with defined characters on the left is a better match than a
job mask with defined characters further to the right.
Example
The following example shows the hierarchical structure of job masks that is
used to find the best match.
Job group
Job masks
Length
Position
ID
GROUP01
*DAILY
Excl.=No
5
01111100
MASK01
GROUP02
*STC
Excl.=No
3
01110000
MASK02
GROUP03
B92*
Excl.=No
3
11100000
MASK03
"Job Group" and "Job Masks" are exemplary definitions given by the user.
"Length" and "Position" are internal sort criteria. "ID" is a short name.
Example
This example shows which job would be assigned to which group.
Job name
Job group
Matched by mask
B92DAILY
GROUP01
MASK01
B92STC
GROUP03
MASK03
B93STC
GROUP02
MASK02
B92RLOAD
GROUP03
MASK03
You can find further examples on the following pages.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
108
General (Option A.1)
Job group (Option A.1.2)
Example 1 - Determining
best matching mask
The following example shows the hierarchical structure of job masks that is
used to find the best match. Inclusive job masks rank before exclusive job
masks. Job masks with a high number of non-generic characters rank
before job masks with a low number of non-generic characters. The default
job mask '*' comes last in the hierarchy.
The following jobs are assigned to the following four job groups:
ABCDAILY, ABCDUMP, ABCTEST, B92DAILY, B92DUMP, B92TEST,
HUGO1, HUGO2, HUGO3, TESTB92, TESTABC, TESTHUGO
Job group
Job masks
Effect
Assigned jobs
GROUP01
B92D*
Excl.=No
All jobs whose name begins with 'B92D' are
assigned to this job group.
B92DAILY
B92DUMP
GROUP02
B92*
Excl.=No
All jobs whose name begins with 'B92'
B92TEST
(except 'B92D' for whom GROUP01 is a
better match) are assigned to this job group.
GROUP03
TEST*
Excl.=Yes
All jobs whose name does not begin with
'TEST' (except 'B92' for whom GROUP01
and GROUP02 are a better match) are
assigned to this job group.
DEFAULT
*
Excl.=No
All other jobs are assigned to this job group. TESTB92
TESTABC
In this example, only jobs whose name
TESTHUGO
begins with 'TEST' are assigned to this
group. For all other jobs, GROUP01 through
GROUP03 are a better match.
Example 2 - Excluding
subgroups
ABCDAILY
ABCDUMP
ABCTEST
HUGO1
HUGO2
HUGO3
To exclude subgroups of jobs from a job group, use a combination of less
discrete and a more discrete job masks, as in the following example:
Job group
Job masks
BETA92
B92*
Exclusive = No
All jobs whose name begins
with 'B92' (except for
B92TEST) are assigned to
job group BETA92.
DEFAULT
B92TEST*
*
Exclusive = No
Exclusive = No
All other jobs are assigned
to job group DEFAULT. The
discrete job mask B92TEST
prevents that test jobs are
assigned to group BETA92.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
Effect
109
General (Option A.1)
Example 3 - Using
exclusive job masks for
security
Job group (Option A.1.2)
An installation uses job mask 'PAY*' for all jobs pertaining to the payroll.
To deny normal users access to payroll jobs, it defines the job group
NONPAY that contains all jobs that do not pertain to the payroll.
Job group
Job masks
NONPAY
PAY*
Effect
Exclusive =
Yes
All jobs whose name does
not begin with 'PAY' are
assigned to this job group.
By granting users access to resource B92.ssid.BRS.NONPAY, users get
access to all jobs except for the payroll jobs. For more information on
security, see the descriptions of the security exits and of the RACF
authority tables in "RACF security" in _beta log|z Installation and System
Guide.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
110
General (Option A.1)
Job group (Option A.1.2)
Determining online and archive retention period
Overview
Use the job group definition to define the online retention period and the
archive retention period of the jobs that are assigned to this job group.
"Job timeline" on page 115 shows the simplified timeline of an archived job
in _beta log|z: How long which information is available online and when it
is deleted by which batch utility.
Archive retention period
The archive retention period is specified in calendar days.
Specify an archive retention period of 0 days if the jobs of this job group
are not to be archived.
It is possible to override values from the job group via line commands or
OMS control cards.
Online retention period
Online retention periods are specified in workdays or generations in these
fields of the job group definition:
Onl. Retention Periods
Online
Type
Queues
Input Ready Error Work
Job Job
Info Record
===> .... .... .... .... ....
===> ..... ..... ..... ..... Days
....
.....
You can specify the following values for each job group:
•
Online retention period of lists (in workdays or generations)
You can specify a different value for each of these queues: Input,
Ready, Error, and Work.
•
Online retention period of job information records (in workdays)
If the value for Job Info is 0, the job information records are deleted
when the lists are deleted or when the job base record is deleted (see
description of Only keep Job Base Record in "How long to keep job
information online" on page 113).
•
Online retention period of job base record (in workdays or generations)
The online retention period of the job base record cannot be shorter
than the other online retention periods (queues/job info). Generations
cannot be used if the value for Job Info is greater than 0.
It is possible to override values from the job group via line commands or
OMS control cards.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
111
General (Option A.1)
Queues and online
retention periods
Job group (Option A.1.2)
The list cleanup utility B92CLLST deletes the lists whose online retention
has expired. B92CLLST evaluates queues and online retention periods,
and deletes the lists accordingly. B92CLLST does not delete lists with
status Arch=Pend.
A job can be on more than one queue. Queues are evaluated in this order:
1. Delete queue
2. Nonretain queue
3. History/Reload queue
4. Work queue
5. Error queue
6. Ready queue
7. Input queue
The global options parameter Use best matching Job Groups controls
which job group is used when determining the retention period of the
Work/Error/Ready/Input queue:
If YES The online retention period of the best matching job group is used
and controls deletion.
If NO
The online retention periods of all matching job groups are
evaluated, and the longest retention period controls deletion.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
112
General (Option A.1)
How long to keep job
information online
Job group (Option A.1.2)
Job information records (i.e. job list records, job step records, job message
records, etc.) can take up a lot of space in the JOB database. It therefore
makes sense to keep this information in the JOB database only as long as
it is really necessary.
The global setting Only keep Job Base Record field in the global options
(Option A.S.3) determines which of these two values (minimum or
maximum) is used as your default:
•
The minimum online retention period of the job information is the
online retention period of the lists.
•
The maximum retention period of the job information is the online
retention period of the job base record.
As of V7R1, you can specify an online retention period that lies between
these two values in the job group definition. You can specify a different
online retention period for each job group.
When is the job information deleted from the JOB database:
If Job Info = 0 in the job group definition and Only keep Job Base
Record = Yes, the job information records are deleted following the
deletion of the lists.
If Job Info > 0 in the job group definition, the job information records are
deleted after the specified number of days.
If Job Info = 0 in the job group definition and Only keep Job Base
Record = No, the job information records are deleted when the job base
record is deleted.
Note on generation processing:
Only keep Job Base Record = Yes is not honored if the online retention
period is specified in generations. In this case, the job information records
are deleted when the job base record is deleted.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
113
General (Option A.1)
Trade-offs
Job group (Option A.1.2)
You have to consider the trade-offs when determining the online
retentention period of the job information records.
If the online retention period of the job info is long:
Pro:
Reduces the necessity for reloading. Under option 1, users can
display detailed job information in the "Job Information Table"
without having to reload the job. Printing/Mailing can send archived
lists directly from the archive medium via batch print (Option 3.1).
Con:
Uses more space in the database, which may force you to reduce
the online retention period for job records.
If the online retention period of the job info is short:
Retention period in
workdays
Pro:
Less space is required in the database, which makes it possible to
increase the online retention period for job records.
Con:
Only the information from the "Job Selection Table" is available
online for when the job info is offline. It is not possible to display
detailed job and step information without prior reload, or to print
lists from the archive medium.
Specify the online retention period of the job group in workdays if you want
to hold lists available online for a certain number of days.
_beta log|z takes weekends into account when evaluating retention
periods. The number of workdays per week is specified under option A.S.3
(see "Global options (Option A.S.3)" on page 230).
Example:
The following example shows the deletion time for a job running on
Thursday morning at an installation that has five workdays per week.
The B92DAILY job, which includes the List Cleanup Utility B92CLLST, is
scheduled to run at 10:00 PM.
Retention period in
generations
If the online retention period is
...
the job/list is deleted on ...
1 day
Friday night
2 days
Monday night
3 days
Tuesday night
Specify the online retention period of the job group in generations if you
want to hold the lists of a certain number of job runs online.
Example:
To hold the lists of the last 7 runs of the B92DAILY job online, specify an
online retention period of 7 generations for the job group that covers the
B92DAILY job.
To ensure that there is always 7 generations of job logs and sysout lists
online, you have to specify the same value for each queue.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
114
General (Option A.1)
Job group (Option A.1.2)
Combining workdays and
generations
Combining workdays and generations in one job group definition is
generally not recommended because it can lead to undesired results.
Important: Generation processing always has precedence over workday
processing.
For example, if a job named B92TEST1 is on a queue with a retention
period of 1 generation, then B92CLLST processes all jobs of this name like
this:
Job timeline
The lists of the most recent B92TEST1 job are not deleted.
•
The lists of all other B92TEST1 jobs are deleted. The queues of these
jobs and their retention periods are not evaluated.
The following figure shows the simplified timeline of an archived job in
_beta log|z.
Time
SPOOL
•
Read in
Job/Lists
(Reader)
Archive
Run
(B92ARPRI)
1
2
Delete from Online
Lists
JobInfo
JobBase
(B92CLLST) (B92ARSEC) (B92ARSEC)
3
4
5
Delete from
archive
(B92CLARC)
6
Lists
Job Base
JOB DB
Job Info
a)
b)
c)
GAR
GAR DB
GARE
ARCHIVE DS
(B92CLAR2)
Job Base
Job Info
Lists
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
115
General (Option A.1)
Job group (Option A.1.2)
1) The job lists are read into _beta log|z and stored on the spool. The
reader creates the job base record and the job information records for
this job in the JOB database.
2) The lists and the job records are archived at the next run of the
B92DAILY job.
The archive utility B92ARPRI saves the lists together with the job
records in an archive dataset (see "Working with archive pools and
archive datasets" on page 199).
B92ARPRI writes one GAR record in the current generation archive
database. This record contains a pointer to the job in the archive
dataset and a subset of the information from the job record.
B92ARPRI also writes a GARE record if the job comes from an EJM
agent. It is possible to disable the writing of these records (B92_ARP_
NOGARE = YES).
3) The list cleanup utility B92CLLST deletes job lists from the spool at the
end of their online retention period. B92CLLST is included in the
B92DAILY job.
4) The job record cleanup utility B92ARSEC deletes job information
records from the JOB database at the end of their online retention
period. The online retention period of job information records is
determined by the following:
a) If Job Info = 0 in the job group and Only keep Job Base Record =
Yes in the global options (Option A.S.3), the job information records
are deleted following the deletion of the lists.
b) If Job Info > 0 in the job group, the job information records are
deleted after the specified number of days.
c) If Job Info = 0 in the job group and Only keep Job Base Record =
No in the global options (Option A.S.3), the job information records are
deleted when the job base record is deleted.
5) The job record cleanup utility B92ARSEC deletes the job base record
from the JOB database at the end of its online retention period.
6) The archive cleanup utility B92CLARC deletes the generation archive
record from the GAR database when the archive dataset has expired.
Note: Extended generation archive records (GAREs) are deleted from
the database by a separate utility. B92CLAR2 deletes all GAREs that
are older than the specified date or older than the specified number of
days. The archive expiration date of the corresponding jobs is not
checked.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
116
General (Option A.1)
Job group (Option A.1.2)
Assigning jobs to job groups
Methods
There are different methods for assigning jobs to job groups:
•
Job group processing via job masks
This method is often called job group processing.
The job name is matched against the existing job masks of all job
groups and the job is assigned to the best match. Archive and cleanup
utilities can also assign jobs to the matching job group with the longest
retention. You can define job name masks based on inclusion (for
example, include all jobs whose name matches B92*) or on exclusion
(include all jobs whose name does not match B92*).
•
Job group processing via sysout class
This method is often called sysout class processing.
The job is assigned to a job group based on its message class. The
reader class definition specifies the name of the job group. For more
information on sysout class processing, see "Sysout class processing"
on page 121 and "Class (Option A.R.1)" on page 260.
You can use both job group processing and sysout class processing in
your _beta log|z system. For example, you can use job group processing
for jobs with standardized names and sysout class processing for jobs with
non-standardized names. Or you can make use of the two methods
because some sysout of a job is processed differently from the rest of the
sysout, for example, dumps are not archived or have a shorter retention
period.
Important: Make sure that all jobs are covered by your job group
definitions. A job group definition with the job mask * should be used to
ensure that all jobs are covered.
Jobgroup column
In the "Job Selection Table" (Option 1), the Jobgroup column displays the
name of the job group that is used for job selection/display and security.
The displayed job group can be the best-matching job group or it can be
the job group defined for the message class of the job. Which job group is
displayed depends on these settings:
•
Class Processing Active in the reader class definition (Option A.R.1)
•
Show class processing in the global options (Option A.S.3)
Show class processing (Option A.S.3)
Yes
Class Processing Active
(Option A.R.1)
No
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
Yes
No
Class processing
job group
Best matching
job group
Best matching
job group
Best matching
job group
117
General (Option A.1)
Job group (Option A.1.2)
Note: The value of the Use best matching Job Groups field in the global
options (Option A.S.3) is only used by the _beta log|z archive and cleanup
utilities, but does not affect job selection/display and security functions. If
Use best matching Job Groups = No, the job group used by the _beta
log|z archive and cleanup utilities can be different from the job group
displayed in the Jobgroup column.
Job names:
B39DAILY, B39TEST, B92DAILY, B92TEST, B93DAILY, B93TEST
Job groups:
GROUP1 includes jobs whose name begins with B*.
GROUP2 includes jobs whose name begins with B9*.
GROUP3 includes jobs whose name begins with B92*.
Selecting ...
Displays jobs ... Comment
GROUP3
B92DAILY
B92TEST
No other job name begins with B92*
GROUP2
B93DAILY
B93TEST
B92DAILY and B92TEST are not
displayed because GROUP3 is a
better match
GROUP1
B39DAILY
B39TEST
B92DAILY, B92TEST, B93DAILY, and
B93TEST are not displayed because
GROUP2 and GROUP3 are a better
match
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
118
General (Option A.1)
Defining a job group
hierarchy
Job group (Option A.1.2)
If you want to use a subset principle for displaying jobs in the Job Select
table, you have to choose job group names accordingly. You can then
enter a mask when selecting jobs via the job group.
Example:
Job names:
B39DAILY, B39TEST, B92DAILY, B92TEST, B93DAILY, B93TEST
Job groups:
GROUPB includes jobs whose name begins with B*.
GROUPB9 includes jobs whose name begins with B9*.
GROUPB92 includes jobs whose name begins with B92*.
Best match or longest
retention
Selecting ...
Displays jobs ... Comment
GROUPB92
B92DAILY
B92TEST
GROUPB92 includes all jobs whose
name begins with B92*
GROUPB9*
B92DAILY
B92TEST
B93DAILY
B93TEST
Mask GROUPB9* includes the job
groups GROUPB9 and GROUPB92
GROUPB*
B92DAILY
B92TEST
B93DAILY
B93TEST
B39DAILY
B39TEST
Mask GROUPB* includes the job
groups GROUPB, GROUPB9, and
GROUPB92
_beta log|z job selection/display and security functions always use the
best-match principle when assigning jobs to job groups via the job masks.
_beta log|z archive and cleanup utilities can use the best-match principle
or the longest-retention principle:
•
Best match principle
If a job name is covered by several job groups, the job is assigned to
the group with the best matching job mask.
•
Longest retention principle
If a job name is covered by several job groups, the job is assigned to
the group with the longest retention period.
Which method you choose determines the archive and online retention
period of a list. Use option A.S.3 to define whether to use the best match
principle or the longest retention principle for archive and cleanup utilities
(see "Global options (Option A.S.3)" on page 230).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
119
General (Option A.1)
Job group (Option A.1.2)
Example:
Job names:
B39DAILY, B39TEST, B92DAILY, B92TEST, B93DAILY, B93TEST
Job groups:
Job group ...
includes jobs ...
and has a retention period of ...
GROUP1
B*
90 days
GROUP2
B9*
180 days
GROUP3
B92*
90 days
_beta log|z assigns jobs as follows if the best-match principle is used
(see "Determining the best matching job group" on page 108):
Jobs ...
are assigned to ...
Comment
B39DAILY
B39TEST
GROUP1
The retention period of the jobs will
be 90 days.
B93DAILY
B93TEST
GROUP2
The retention period of the jobs will
be 180 days.
B92DAILY
B92TEST
GROUP3
The retention period of the jobs will
be 90 days.
_beta log|z assigns jobs as follows if the longest-retention principle is
used:
Jobs ...
are assigned to ...
Comment
B39DAILY
B39TEST
GROUP1
The retention period of the jobs will
be 90 days.
B92DAILY
B92TEST
B93DAILY
B93TEST
GROUP2
The retention period of the jobs will
be 180 days. B92DAILY and
B92TEST match two job groups.
The jobs are assigned to the group
with the longer retention period.
Note: The parameter Use best matching job groups applies only when a
job is assigned to a job group via job masks (job group processing), but
not when a job is assigned to job group via the sysout class (sysout class
processing).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
120
General (Option A.1)
Sysout class processing
Job group (Option A.1.2)
You can also assign jobs to job groups via their sysout class. In this case,
the entire output of a class is assigned to a particular job group. This
method is useful if job names are not fully standardized.
When a job is read into _beta log|z, the program checks whether sysout
class processing is active for any of the lists. If it is, the list is marked
accordingly.
To use sysout class processing requires the following definitions:
1. Define a job group and enter the retention periods and archive
medium you want to be used for the sysout class (Option A.1.2).
2. In the sysout class definition, specify Class Processing Active=Yes
and enter the name of the job group in the field Class Processing
Job Group (Option A.R.1).
Note: You have to restart the _beta log|z reader for your changes to take
effect. To do this, use the console command F stcname,RESTART
READER. When using multi-image processing, you have to this for each
z/OS image.
Example: Combining job group and sysout class processing
All jobs whose name begins with ABC should stay online for 10 days and
should stay in the archive for 60 days. Dumps of these jobs should stay
online for 1 day and should not be archived at all.
To do this requires the definition of two job groups (in the example,
GRPABC and SYSOUTR) and a special sysout class for dumps (in the
example, class R).
•
GRPABC has an online retention period of 10 days and an archive
retention period of 60 days. Use the job group definition panels to
assign job mask ABC* to this group.
•
SYSOUTR has an online retention period of 1 day. Do not assign any
job masks to this group. Use the class definition panel to define sysout
class R as NOSAVE and assign this class to group SYSOUTR.
The following job assigns logs to class P and a dump to class R.
+-------------------------------------------------------------------+
|//ABCTEST JOB account,&SYSUID,CLASS=A,MSGCLASS=P
|
|//step
EXEC PGM=program
|
|//STEPLIB DD DISP=SHR,DSN=datasetname
|
|//REPORT1 DD SYSOUT=*
|
|//REPORT2 DD SYSOUT=*
|
|//DUMP
DD SYSOUT=R
|
+-------------------------------------------------------------------+
In the job selection table, job ABCTEST is displayed as belonging to job
group GRPABC. The sysout written to DD REPORT1 and DD REPORT2
is processed according to the definitions of this job group. It is archived
and stays online for 10 days as defined in job group GRPABC. The sysout
written to DD DUMP is processed according to the definition for class R,
that is, it is not archived and it stays online for 1 day. The "Job Information
Table" displays "Arch=No" for this list.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
121
General (Option A.1)
Notify groups (Option A.1.3)
Notify groups (Option A.1.3)
Overview
_beta log|z can send a TSO message to a group of users when the _beta
log|z reader puts a job on the error queue.
Required definitions
The following definitions are required if you want this:
Under option A.1.3 (notify group):
•
Add one entry for each user that is to be a member of the notify group.
Under option A.S.2 (subsystem options):
•
Specify Yes in the Send Message on Error field.
•
Specify Yes in the to Notify Group field.
•
Enter the name of the notify group in the Group ID field.
For more information, see "Subsystems (Option A.S.2)" on page 223.
Changes require reader
restart
For any changes to the notify group definitions to take effect, the _beta
log|z reader has to be restarted. To to this, enter the console command
F stcname,RESTART READER. When using multi-image processing, you
have to restart the _beta log|z reader for each z/OS image.
Navigation
From the "Primary Selection Menu", choose:
•
Option A.1.3
The "Notify Group Definition Selection" panel is displayed, in which
you can enter your selection criteria.
Insert Notify User
Definition panel
PE92DF43 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Insert Notify User Definition
Notify Group ===> ........
Group name
User ID
No generic user IDs allowed
===> ........
Press ENTER key to insert this entry and continue.
Press END key to cancel changes or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
122
General (Option A.1)
Fields
Line commands
Notify groups (Option A.1.3)
Field
Description
Notify Group
Enter the name of a new or existing notify group.
User ID
Enter the user ID of the TSO user who is to be a
member of this group. A user can be a member of more
than one group.
The following line commands are available in the "Notify User Definition
Table":
S
Selects the user definition for display or update
D
Deletes the user definition
I
Adds a new user definition (insert)
C
Adds a new user definition (copy)
A
Activates/Deactivates the user definition
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
123
Enterprise (Option A.2)
In this chapter
Enterprise (Option A.2)
In this chapter
Topic
Page
Processing enterprise data ..................................................................... 125
Enterprise definition concept and sequence .......................................... 127
Rule group definitions (Option A.2.1) ..................................................... 130
Rule definitions (Option A.2.2)................................................................ 132
Operation definitions (Option A.2.3) ....................................................... 136
Run cycle definitions (Option A.2.4) ....................................................... 140
Agent group definitions (Option A.2.5) ................................................... 142
Agent definitions (Option A.2.6).............................................................. 144
Activating and refreshing agents ........................................................ 149
Scan group definitions (Option A.2.S) .................................................... 151
SAP system definitions (Option A.2.7) ................................................... 153
SAP server definitions (Option A.2.8) ..................................................... 156
SAP account definitions (Option A.2.9) .................................................. 159
Working with file operations for normal logs ........................................... 161
Working with file operations for endless logs ......................................... 162
Working with file operations for Windows event logs ............................. 163
Transferring a Unix system log to _beta log|z ........................................ 165
Working with SAP operations for job logs .............................................. 168
Working with SAP operations for endless logs ....................................... 170
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
124
Enterprise (Option A.2)
Processing enterprise data
Processing enterprise data
Overview
The definitions under option A.2 are used for reading in data from other
platforms with the help of _beta job|z agent.
The definitions in _beta log|z define which logs should be read in from
which machine. Agents installed on the other platforms collect the logs and
transfer them to _beta log|z, for example, in order to archive them.
Operation categories
File operations
An operation determines what is to be processed. There are two
categories:
•
File operations
•
SAP operations
File operations can process
•
Normal Unix/Windows logs
•
Endless Unix/Windows logs
•
Windows event logs
Prerequisite
You must have an operational _beta job|z agent on the
Unix/Linux/Windows machine where the files are located.
For installation and configuration instructions, see:
•
SAP operations
"Installing _beta job|z agent" in _beta job|z Installation and System
Guide
SAP operations can process:
•
SAP jobs (including its job definitions, job logs, spool lists, child jobs,
application logs)
•
SAP system logs
•
SAP security audit logs
Prerequisite
You must have an operational _beta job|z agent on a Unix/Linux/Windows
machine with access to the SAP server. _beta job|z agent can be installed
on the SAP server machine itself, but this is not required. The relevant
function modules must be available on the SAP system in the /BETASYS/
namespace.
For installation and configuration instructions, see:
•
"Installing _beta job|z agent" in _beta job|z Installation and System
Guide
•
"Integration with SAP" in _beta job|z Installation and System Guide
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
125
Enterprise (Option A.2)
Chapter structure
Processing enterprise data
"Enterprise definition concept and sequence" on page 127 gives an
overview of the definitions under option A.2.1 through A.2.9 and proposes
a best sequence for creating the definitions. This is followed by sections
describing each definitition. At the end of the chapter, you can find more
information on which data can be processed and examples of use:
•
"Working with file operations for normal logs" on page 161
•
"Working with file operations for endless logs" on page 162
•
"Working with file operations for Windows event logs" on page 163
•
"Transferring a Unix system log to _beta log|z" on page 165
•
"Working with SAP operations for job logs" on page 168
•
"Working with SAP operations for endless logs" on page 170
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
126
Enterprise (Option A.2)
Enterprise definition concept and sequence
Enterprise definition concept and sequence
Overview
This section contains an overview of the definitions available under the
Enterprise option A.2.
It also proposes a best sequence for defining file rules and SAP rules.
SAP license
A valid license for SAP support is required if you want to process SAP
rules with _beta log|z.
If the license check fails, the SAP server (Option A.2.8) is set offline in
_beta log|z and the following message is written to the agent log file
logfile.txt:
B92ONLE No License available for <SAP system>
Definitions
Option
Definition
Description
A.2.1
Rule groups
File rules and SAP rules are organized into rule groups.
A.2.2
Rules
What When Where Who: A rule serves as a connection point for
other definitions, which contain the actual processing instructions.
What is to be processed is defined via the connected operation.
Optionally, you can also connect a scan group.
When (at what time and how often) processing takes place is
defined via the connected run cycle.
Where processing takes place is defined via the connected agent
(file rule) or SAP server (SAP rule).
A SAP rule also includes a user ID for processing (connected
SAP account).
A.2.3
Operations
What: An operation determines what is to be processed. This can
be either a file operation or an SAP operation.
An operation can be the transfer of a file or log (for example, a
normal log, an endless log, a Windows event log, a Unix system
log), the transfer of an SAP job (including its job definitions, job
logs, spool lists, child jobs, and application logs) or the transfer of
SAP system logs or SAP security audit logs.
A.2.4
Run cycles
When: A run cycle determines at what time and how often a rule is
executed.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
127
Enterprise (Option A.2)
A.2.5
Enterprise definition concept and sequence
Agent groups
Where: Agents are organized into agent groups. The agent group
determines where (i.e. on which agent or agents) a file rule is to be
processed.
Create an agent group for one agent if you want to process files of
one Unix/Windows/Linux machines. Add multiple agents to the
agent group if you want to process similar files from multiple
systems.
A.2.6
Agents
An agent can process file rules on the local machine and/or
SAP rules on an SAP server.
The address where the agent can be found must be entered.
A.2.S
Scan groups
What: A scan group (optional) defines keywords. An agent can use
scan groups during file rule processing to determine whether a file
is to be transferred to _beta log|z or not.
A.2.7
SAP Systems
Optionally, SAP servers and SAP accounts that belong together
can be grouped into SAP systems.
A.2.8
SAP servers
Where: In SAP environments, an SAP server determines where an
SAP rule is to be processed.
The TCP/IP address where the SAP server can be found and the
address of an agent must be entered.
A.2.9
SAP accounts
File rule definition
sequence
Who: In SAP environments, an SAP account, i.e. an SAP user who
is allowed to log on to the system and who is to process an SAP
rule can be named.
Create the definitions for a file rule in the following sequence:
1. Specify in an operation definition what is to be processed (Option
A.2.3).
2. Optionally, define special keywords in a scan group to determine what
is to be processed (Option A.2.S).
3. Specify in a run cycle definition when and how often processing should
take place (Option A.2.4).
4. Create one or more agent definitions depending on where processing
should take place (Option A.2.6).
5. Create an agent group definition and connect the agent definition(s)
(Option A.2.5).
6. Create a rule group (Option A.2.1).
7. Create a rule as a member of a rule group and group the
what/when/where definitions under this rule (Option A.2.2).
8. Activate the rule (Option A.2.2, Line command A).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
128
Enterprise (Option A.2)
SAP rule definition
sequence
Enterprise definition concept and sequence
Create the definitions for a SAP rule in the following sequence:
1. Specify in an operation definition what is to be processed (Option
A.2.3).
2. Specify in a run cycle definition when and how often processing should
take place (Option A.2.4).
3. Create a definition for the agent, which is placed between _beta log|z
and SAP server (Option A.2.6).
4. Specify in an SAP server definition where processing should take
place (Option A.2.8).
5. Specify in an SAP account definition under which user ID processing
should take place (Option A.2.9).
6. Create a rule group (Option A.2.1).
7. Create a rule as a member of a rule group and group the
what/when/where/who definitions under this rule (Option A.2.2).
8. Activate the rule (Option A.2.2, Line command A).
Activating rules
Line command A in the "Rule Definition Table" enables you to activate and
deactivate rules.
Rule activation is only possible when prerequisites are fulfilled:
File rule
The rule must be connected to a rule group and it must be
connected to appropriate definitions on what (operation)/
when (run cycle)/where (agent group).
SAP rule
The rule must be connected to a rule group and it must be
connected to appropriate definitions on what (operation)/
when (run cycle)/where (SAP server with agent)/
who (SAP account).
You can use these columns in the "Rule Definition Table" to verify that
prerequisites are fulfilled:
...
Rule Run- Opera AGrp/ SAP
... Type
Group cycle tion SAPSv Accnt
... FILERULE
Y
Y
Y
Y
N
... SAPRULE
Y
Y
Y
Y
Y
When you activate a rule, the rule plan will be updated on the agent side at
the next manual or automatic agent refresh (see "Activating and refreshing
agents" on page 149). The current rule plan is stored in the file
ruleplan.txt in the B92/session directory of the agent.
Maximum number of lists
A rule can process a maximum of 500 lists at one time. If there are more
lists, processing is repeated until all lists have been processed.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
129
Enterprise (Option A.2)
Rule group definitions (Option A.2.1)
Rule group definitions (Option A.2.1)
Overview
File rules and SAP rules are organized into rule groups.
Navigation
From the "Primary Selection Menu", choose:
Option A.2.1
•
The "Rule Group Selection" panel is displayed, in which you can enter
your selection criteria.
Insert Rule Group
Definition panel
This panel enables you to create a new rule group definition.
PE92EP12 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Insert Rule Group Definition
Name
===> ........................
Description ===> ___________________________________________________
===> ___________________________________________________
===> ___________________________________________________
===> ___________________________________________________
===> ____________________________________________________
Press ENTER key to insert this entry.
Press END key to cancel changes or HELP key for help information.
Fields
Line commands
Field
Description
Name
Unique name of the rule group (required entry)
Description
Text which describes the rule group (optional)
The following line commands are available in the "Rule Group Definition
Table".
S
Selects the rule group definition for display or update
I
Adds a new rule group definition (insert)
C
Adds a new rule group definition (copy)
D
Deletes the rule group definition
Note: A rule group can be deleted only if no rule is connected to
this rule group.
LR
Lists all rules connected to the rule group
MR
Adds the rule to a rule group
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
130
Enterprise (Option A.2)
Adding a rule to a rule
group
Rule group definitions (Option A.2.1)
To add a rule to a rule group:
1. In the "Rule Group Definition Table", enter line command MR in front
of the rule group to which the rule is to be added.
The "Move Rule to Rule Group" panel is displayed:
PE92EP15 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Move Rule to Rule Group
Move Rule
Rule Name
Rule Type
===> ........
===> ........
(* for list)
(F)ILERULE, (S)APRULE or *
to Rule Group
Rule Group Name
:
BETA_RULEGROUP
Press ENTER key to update rule entry.
Press END key to cancel changes or HELP key for help information.
2. In the field Rule Name enter a rule name or enter an asterisk * to
display all file or SAP rules.
3. In the field Rule Type enter F or file rules or S for SAP rules to display
either file rules or SAP rules, and press ENTER.
4. In the panel select one rule by entering S in front of that rule, and
press ENTER twice.
You will see the "Rule Group Definition Table" and the message that
the rule has been added to a rule group.
Connected rules
The Connected Rule field in the "Rule Group Selection" panel enables
you to select rule groups according to the rules which are connected.
Line command LR in the "Rule Group Definition Table" shows connected
rules in the "Rule Definition Table". The line commands in the "Rule
Definition Table" can be used to modify the rule definitions.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
131
Enterprise (Option A.2)
Rule definitions (Option A.2.2)
Rule definitions (Option A.2.2)
Overview
A rule serves as a connection point for the what/when/where/who
definitions that you have created under option A.2.
Navigation
From the "Primary Selection Menu", choose:
Option A.2.2
•
The "Rule Selection" panel is displayed, in which you can enter your
selection criteria.
Insert Rule Definition
panel
This panel enables you to create a new rule definition.
PE92EP21 -------------------------------------------------------- Page 1 of 2
Command ===> _________________________________________________________________
Insert Rule Definition
Name
Type
===> ........
===> ........
Active
: NO
(F)ILERULE or (S)APRULE
Title
===> ________________________
Rule Group
Runcycle
===> ________________________
===> ________________________
Description
===> ___________________________________________________
===> ___________________________________________________
===> ___________________________________________________
===> ___________________________________________________
===> ____________________________________________________
(* for list)
(* for list)
Press ENTER or DOWN key to proceed inserting this entry.
Press END key to cancel changes or HELP key for help information.
Fields
Field
Description
Name
Unique name of the rule (required entry)
Type
Type of the rule (required entry)
FILERULE
Runs on Unix/Linux/Windows systems
SAPRULE
Runs on SAP systems
Title
Title (optional, max. 24 characters)
Rule Group
Name of the rule group to which the rule belongs
(optional when you create a definition, but required for
activation)
Runcycle
Run cycle which is to be used (optional when you create
a definition, but required for activation)
Description
Text which describes the rule (optional)
File Operation
Only if FILERULE:
File operation to be executed (optional when you create
a definition, but required for activation)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
132
Enterprise (Option A.2)
Rule definitions (Option A.2.2)
Field
Description
Agent Group
Only if FILERULE:
Agent group which defines on which
Unix/Linux/Windows agents the rule is to be executed
(optional when you create a definition, but required for
activation)
Scan Group
Only if FILERULE:
Name of a scan group (optional)
The name can refer to a scan group for agent-side
processing (Option A.2.S). These scan groups are
evaluated before files are transferred.
The name can also refer to the name of a scan group
for reader-side processing (Option A.R.3). This
processing takes place after files have been
transferred.
SAP Operation
Only if SAPRULE:
SAP operation to be executed (optional when you
create a definition, but required for activation)
SAP Server
Only if SAPRULE:
SAP server where to execute the operation (optional
when you create a definition, but required for activation)
SAP Account
Only if SAPRULE:
SAP account which the SAP rule is to use for logging
onto the specified SAP server (optional when you create
a definition, but required for activation)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
133
Enterprise (Option A.2)
Line commands
Displaying the agent/rule
status
Rule definitions (Option A.2.2)
The following line commands are available in the "Rule Definition Table".
S
Selects the rule definition for display or update
I
Adds a new rule definition (insert)
C
Adds a new rule definition (copy)
D
Deletes the rule definition
A
Activates/Deactivates the rule
ST
Displays the status entries of the rule
DR
Displays the connected rule group
DC
Displays the connected run cycle
DO
Displays the connected operation
DG
Displays the connected agent group
DS
Displays the connected SAP server
DU
Displays the connected SAP account
Line command ST displays all status entries of a rule in the "Agent-Rule
Status Table". You can use the information displayed in this table to verify
the correcting processing of the rules.
The "Agent-Rule Status Table" can also be called via option A.M.1.
For more information, see "Displaying agent rule status information (Option
A.M.1)" on page 183.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
134
Enterprise (Option A.2)
Connecting definitions to
a rule
Rule definitions (Option A.2.2)
A rule serves as a connection point for other definitions, which contain the
actual processing instructions.
In case of a file rule, specify the name of an existing definition in the
corresponding field to connect this definition to the rule:
•
Rule group (required)
•
Run cycle (required)
•
File operation (required)
•
Agent group (required)
•
Scan group (optional)
In case of a SAP rule, specify the name of an existing definition in the
corresponding field to connect this definition to the rule:
•
Rule group (required)
•
Run cycle (required)
•
SAP operation (required)
•
SAP server (required)
•
SAP account (required)
Selecting definitions via mask
All of the fields listed above support the selection via mask.
When you type a mask in a field and press ENTER, the matching
definitions are displayed in a table and you can select the desired entry via
the line command S.
Example: SYSLRUL$
A sample file rule SYSLRUL$ is delivered under option A.2.2. The rule is
an endless rule. You only have to add your agent group and your rule
group to the rule.
You can use the rule for transferring Unix system logs to _beta log|z, for
example. For more information, see "Transferring a Unix system log to
_beta log|z" on page 165.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
135
Enterprise (Option A.2)
Operation definitions (Option A.2.3)
Operation definitions (Option A.2.3)
Overview
An operation definition determines what is to be processed.
For example, an operation can be the transfer of a file or log or the transfer
of an SAP job.
For more details on the different categories and examples of use, see also:
Navigation
•
"Working with file operations for normal logs" on page 161
•
"Working with file operations for endless logs" on page 162
•
"Working with file operations for Windows event logs" on page 163
•
"Transferring a Unix system log to _beta log|z" on page 165
•
"Working with SAP operations for job logs" on page 168
•
"Working with SAP operations for endless logs" on page 170
From the "Primary Selection Menu", choose:
•
Option A.2.3
The "Operation Selection" panel is displayed, in which you can enter
your selection criteria.
Insert FILE Operation
Definition panel
This panel enables you to create a file operation definition.
PE92EP31 --------------------------------------------------------- Page 1 of 2
Command ===> _________________________________________________________________
Insert FILE Operation Definition
Name
Title
===> ........
===> ________________________
Description ===> ___________________________________________________
===> ___________________________________________________
===> ___________________________________________________
===> ___________________________________________________
===> ____________________________________________________
Delete Log ===> NO.
(Y)es or (N)o
Log Type
===> ........
(E)ndless, (N)ormal or (W)inevent
File Name
===> ............................................................
................................................................................
................................................................................
................................................................................
Press ENTER to insert this entry or DOWN key to go to next page.
Press END key to cancel changes or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
136
Enterprise (Option A.2)
Fields
Operation definitions (Option A.2.3)
Field
Description
Name
Unique name of the operation (required entry)
Title
Title (optional, max. 24 characters)
Description
Text which describes the operation (optional)
Delete Log
Specifies whether to delete the log file on the system
after it has been transferred to _beta log|z (required)
Note: For the log type Winevent, Delete Log=YES is
not allowed to be entered. Windows event logs cannot
be deleted.
Log Type
Specifies the type of log that is to be processed:
File Name
•
(E)ndless Unix/Windows logs
•
(N)ormal Unix/Windows logs
•
(W)indows event logs, which are endless log types
Specify one of the following:
•
File name with path if normal or endless log
•
Event type if Windows event log
An entry in this field is required.
Wildcards can be used in the path and file name if the
file operation is for normal logs, for example:
/usr/local/myjobs/2007.??.??/O*
No wildcards are allowed if the file operation is for
endless logs or Windows event logs.
Insert SAP Operation
Definition panel
This panel enables you to create an SAP operation definition.
PE92EP33 --------------------------------------------------------------------Command ===> _________________________________________________________________
Insert SAP Operation Definition
Name
Title
===> ........
===> ________________________
Type
===> ........
Delete Log
===> ___
(Yes/No)
Read Childjobs ===> ___
(Yes/No)
(J)oblog, (S)yslog or (A)uditlog
Read Spool
===> ___
(Yes/No)
Read Appl.Log ===> ___
(Yes/No)
SAP Jobname
SAP Jobcount
===> ________________________________
===> ________
SAP User
Description
===> ___________________________________________________
===> ___________________________________________________
===> ___________________________________________________
===> ___________________________________________________
===> ____________________________________________________
===> ____________
Press ENTER key to insert this entry.
Press END key to cancel changes or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
137
Enterprise (Option A.2)
Fields
Operation definitions (Option A.2.3)
Field
Description
Name
Unique name of the operation (required entry)
Title
Title (optional, max. 24 characters)
Type
Specifies the operation type (required):
Delete Log
•
JOBLOG
•
SYSLOG
•
AUDITLOG
Enter Yes to delete the logs found in the system after
they have been transferred to _beta log|z. Enter No if
you do not want the logs to be deleted. The field can
only be used with the operation type JOBLOG. An entry
in this field is required.
Important: Do not specify Yes if you have defined a file
size limit (Outlim) in the relevant agent definitions in
_beta job|z because this would cause the loss of output
affected by outlim (see "SAP output processing" on
page 337).
Read Spool
Enter Yes to read the spool lists of the SAP jobs. The
field can only be used with the operation type JOBLOG.
An entry in this field is required.
Read Childjobs
Enter Yes to read the logs of all child jobs belonging to
the SAP jobs. Enter No if the child job logs are not to be
transferred.
The field can only be used with the operation type
JOBLOG. An entry in this field is required.
Read Appl. Log
Enter Yes to read the application log of the SAP jobs.
One application log per SAP job can be transferred.
Enter No if the application log is not to be transferred.
The field can only be used with the operation type
JOBLOG. An entry in this field is required.
SAP Jobname
Enter an SAP job name or a mask to specify which jobs
are to be selected by this operation (required).
SAP Jobcount
Enter the identification of the job(s) in the SAP system
or a mask (optional).
SAP User
Enter the name of the SAP user who is the owner of the
jobs to be selected (optional).
Description
Text which describes the operation (optional)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
138
Enterprise (Option A.2)
Line commands
Connecting an operation
to a rule
Operation definitions (Option A.2.3)
The following line commands are available in the "FILE/SAP Operation
Definition Table".
S
Selects the operation definition for display or update
I
Adds a new operation definition (insert)
C
Adds a new operation definition (copy)
D
Deletes the operation definition
LR
Lists the rules to which the operation is connected
AO
Connects the operation to a rule
You can use the line command AO to connect a file operation to a file rule
or an SAP operation to an SAP rule.
For example, to add a file operation to a file rule:
1. In the "File Operation Definition Table", enter the line command AO in
front of a file operation.
The following panel appears:
PE92EP38 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Add FILE Operation to FILE Rule
Add FILE Operation
Operation Name
:
B92AGEL2
to FILE Rule
Rule Name
===> ........
(* for list)
Press ENTER key to update rule entry.
Press END key to cancel changes or HELP key for help information.
2. Enter a rule name, or enter an asterisk * to display all file rules, then
select one by entering S in front of the respective file rule, and press
ENTER.
You will see the "File Operation Definition Table" and the message
that the operation has been added to a rule.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
139
Enterprise (Option A.2)
Run cycle definitions (Option A.2.4)
Run cycle definitions (Option A.2.4)
Overview
A run cycle determines at what time and how often a rule is executed.
Navigation
From the "Primary Selection Menu", choose:
•
Option A.2.4
The "Runcycle Selection" panel is displayed, in which you can enter
your selection criteria.
Insert Runcycle
Definition panel
This panel enables you to create a new run cycle definition.
PE92EP42 --------------------------------------------------------------------Command ===> _________________________________________________________________
Insert Runcycle Definition
Runcycle Name
===> ........................
Start:
as soon as possible ===> YES
or Start Date
===> __________
Run only once
or repeat every
Description
===> YES
===> 0__ days
(Y)es or (N)o
Start Time ===> ________
(Y)es or (N)o
===> 0_ hours ===> 0_ mins
===> ___________________________________________________
===> ___________________________________________________
===> ___________________________________________________
===> ___________________________________________________
===> ____________________________________________________
Press ENTER key to insert this entry.
Press END key to cancel changes or HELP key for help information.
Fields
Field
Description
Runcycle Name
Enter the name of the run cycle you want to create
(required entry).
Start as soon as
possible
Enter Yes to start the run cycle as soon as possible.
Enter No to specify a particular start date and time in
the following fields (required entry).
or Start Date/Time
Enter a particular start date and time for the run cycle
(an entry is only required when Start as soon as
possible=No has been entered).
Run only once
Enter Yes to run the run cycle only once. Enter No to
repeat the run cycle in the specified interval (see next
field).
or repeat every
Enter the interval in days/hours/minutes (an entry is only
required when Run only once=No has been entered).
Note: At least 1 minute must be used for an interval.
Runcycle Description
Enter a description for the run cycle.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
140
Enterprise (Option A.2)
Line commands
Run cycle definitions (Option A.2.4)
The following line commands are available in the "Runcycle Definition
Table".
S
Selects the run cycle definition for display or update
I
Adds a new run cycle definition (insert)
C
Adds a new run cycle definition (copy)
D
Deletes the run cycle definition
Note: A run cycle can be deleted only if it is not used in a rule.
Connected rules
LR
Lists the rules to which the run cycle is connected
MR
Adds the run cycle to a rule group
The Assigned to Rule field in the "Runcycle Selection" panel enables you
to select run cycles according to the rules which are connected.
Line command LR in the "Runcycle Definition Table" shows connected
rules in the "Rule Definition Table". The line commands in the "Rule
Definition Table" can be used to modify the rule definitions.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
141
Enterprise (Option A.2)
Agent group definitions (Option A.2.5)
Agent group definitions (Option A.2.5)
Overview
Agents are organized into agent groups.
An agent group with multiple agents enables you to transfer similar files
from multiple systems. Create a separate agent group for each agent if
you don't need this.
Navigation
From the "Primary Selection Menu", choose:
Option A.2.5
•
The "Agent Group Selection" panel is displayed, in which you can
enter your selection criteria.
Insert Agent Group
Definition panel
This panel enables you to create a new agent group definition.
PE92EP52 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Insert Agent Group Definition
Name
===> ........................
Description ===> ___________________________________________________
===> ___________________________________________________
===> ___________________________________________________
===> ___________________________________________________
===> ____________________________________________________
Press ENTER key to insert this entry.
Press END key to cancel changes or HELP key for help information.
Fields
Field
Description
Name
Unique name of the agent group (required entry)
Description
Text which describes the agent group (optional)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
142
Enterprise (Option A.2)
Line commands
Agent group definitions (Option A.2.5)
The following line commands are available in the "Agent Group Definition
Table".
S
Selects the agent group definition for display or update
I
Adds a new agent group definition (insert)
C
Adds a new agent group definition (copy)
D
Deletes the agent group definition
Note: An agent group can only be deleted when no agent is
connected to this agent group.
LA
Lists all agents connected to the agent group
Use this line command when you want to add a new agent to the
agent group or remove an agent from the agent group.
LR
Lists all rules connected to the agent group
AG
Adds the agent group to a rule
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
143
Enterprise (Option A.2)
Agent definitions (Option A.2.6)
Agent definitions (Option A.2.6)
Overview
Agents can be used to process file rules or SAP rules in the Windows/
Unix/Linux environment. To be able to process rules, an agent must be
defined in _beta log|z.
Navigation
From the "Primary Selection Menu", choose:
Option A.2.6
•
The "Agent Selection" panel is displayed, in which you can enter your
selection criteria.
Note on Agent Definition Table
The following abbreviations are used in the "Agent Definition Table":
Insert Agent Definition
panel
A
Active status (Y/N)
O
Online status (Y/N)
Pri
Priority (0..9; 0=highest and 9=lowest)
LgL
Log level (0..3)
This panel enables you to create a new agent definition.
PE92EP61 ---------------------------------------------------------- Page 1 of 2
Command ===> _________________________________________________________________
Insert Agent Definition
Name ===> ........
Title ===> ________________________ Active ===> YES (Y/N)
beta logz SSID ===> ____
SSL Encrypt. ===> NO. (Y/N)
Priority
===> .
(0-9)
Max Log Gen. ===> 0.
(0-99)
Outlim
===> 0.... (0-99999 MB)
Log Outlim
===> 0.
(0-99 MB)
Port Number
===> ..... (Default: 10210) Log Level
===> 0
(0-3)
TCP/IP Address ===> ...................................................
===> ___________________________________________________
===> ___________________________________________________
===> ___________________________________________________
===> ______________________________________________
Host Name
: Version
: Oper. System : Online
: NO
Offline Since: Last Refresh: Last List
: Press ENTER to insert this entry or DOWN key to go to next page.
Press END key to cancel changes or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
144
Enterprise (Option A.2)
Fields (Page 1)
Agent definitions (Option A.2.6)
Field
Description
Name
Unique name of the agent
Title
Optional title for the agent (max. 24 characters)
Active
Yes activates the agent
beta logz SSID
The subsystem ID (SSID) of the _beta log|z system that
the agent is to be assigned to. Only existing SSIDs are
valid, i.e. the SSID must have been defined under
option A.S.2 beforehand.
It is also possible to assign an agent to the SSID of a
slave STC. This reduces the workload on the master
STC and helps distribute CPU and memory
consumption more evenly. The most CPU-consuming
connections can be distributed to more than one STC.
If the field is left blank, the agent will be assigned to the
master system or to the system defined in the LST
parameter BQL_MASTER_SSID. For more information,
see "Assigning agents to an SSID in master/slave
configurations" in _beta log|z Installation and System
Guide.
After a new SSID is specified, the following are logged
in the STC log of the new system:
•
the agent logoff from the _beta log|z STC used
previously
•
the agent logon to the new system.
Note: If you are using routers, only one SSID can be
defined per router. All agent definitions which use the
same router must also use the same _beta log|z SSID.
SSL Encrypt.
Specify Yes if you want to use SSL encryption for the
communication with this EJM agent
SSL encryption must also be enabled on the agent side.
For more information, see "Using SSL-secured
connections" in _beta job|z Installation and System
Guide.
Priority
The priority (0..9) determines the frequency of the
monitoring cycle that checks the availability of the agent.
0 is the highest priority and 9 is the lowest.
Low-priority agents are checked less frequently. Highpriority agents are checked more frequently. The actual
frequency is determined by the priority and the value of
the LST parameter B92_MONI_PAUSE.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
145
Enterprise (Option A.2)
Agent definitions (Option A.2.6)
Field
Description
Max Log Gen.
The number (0..99) of log file generations to be created
Default: 0
When one of the parameters Log OutLim or Max Log
Gen. is 0, no generation file will be created. The log file
information will be written to a single log file.
Outlim
The maximum file size in MB that the EJM agent is
allowed to transfer to _beta log|z. The maximum file size
is 99999 MB. 0 means that the file size is not checked.
The file size limit does not apply to endless file rules.
For more information on outlim processing, see "Large
list monitoring and outlim processing" on page 331.
Log Outlim
The size (0..99) of each agent log file generation in MB.
The log file size you choose depends on the specified
log level and the number of processed rules. Default: 0
When an agent log file reaches the specified size, it is
stored as the first generation of the agent log file. An
existing first generation log file is overwritten. An empty
agent log file is then created automatically. This enables
the more efficient use of storage space, and log
message generations.
Up to 99 agent log file generations can be created. See
field Max Log Gen. for more information.
Port Number
Port number of the agent
Log Level
A log level between 0 and 3 to determine how much
trace output the agent prints to its log:
TCP/IP Address
0
No logging
1
Error messages only
2
Like 1, but also with warning messages
3
Like 2, but also with informational messages
The TCP/IP address of the agent (required entry).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
146
Enterprise (Option A.2)
Agent definitions (Option A.2.6)
The following fields display information on the agent:
Fields (Page 2)
Field
Description
Host Name
Host name of the system on which the agent is running
Version
Current version and build level of the agent
Oper. System
Operating system where the agent is running
Online
Yes indicates that the agent is online, No that it is offline
Offline Since
If the agent is offline, this field contains the time and
date on which it went offline.
Last Refresh
The timestamp of the last time the agent was refreshed.
Last List
The timestamp of the last time the agent transferred a
list to _beta log|z.
Field
Description
Router Address
Router Port
If you are using the EJM router for this agent:
TCP/IP address and port number of the EJM router
Account Key
A character string (up to 143 characters, optional)
The account key is included in the SMF records for
client-based billing, which are written when the
B92UXSMF exit is active. By default, it is inactive.
For more information, see "B92UXSMF: Client-based
billing SMF record exit" in _beta log|z Installation and
System Guide.
Description
A description or comment about the agent (optional).
Use the second panel if you do not have enough space
to enter the description in the first panel. You can enter
up to 256 characters for the agent description.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
147
Enterprise (Option A.2)
Line commands
Agent definitions (Option A.2.6)
The following line commands are available in the "Agent Definitions
Table".
S
Selects the agent definition for display or update
I
Adds a new agent definition (Insert)
C
Adds a new agent definition (Copy)
D
Deletes the agent definition
RF
Sends a refresh request to the agent
The agent retrieves all definitions from the database anew.
PI
Updates the plugin definition for an agent
Complete the "Plugin Definition" freeform field. Use semicolons to
separate the parameters. Refresh the agent for your changes to
take effect. The definition will be automatically added to the
params.ini of the agent.
For detailed information on the freeform field used for the plugin
definition, see "Activating the _beta log|z plugin for Control-M" in
_beta log|z Plugin for Control-M Manual.
GL
Gets the last 29K of the agent logfile (useful for troubleshooting)
LA
Lists agent groups connected to the agent
When no agent group is connected to the agent, the insert
connection panel is displayed.
Primary command
LR
Lists the rules connected to the agent
LS
Lists the SAP servers connected to the agent
ST
Displays all agent/rule status entries that belong to the agent
The primary command RFALL can be used to refresh all agents that are
selected for display in the "Agent Definition Table" (see "Refreshing
multiple agents" on page 150).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
148
Enterprise (Option A.2)
Agent definitions (Option A.2.6)
Activating and refreshing agents
Overview
After defining a new agent, you have to activate the agent. Without
activation, the agent will not be able to process any rules.
After modifying an existing agent, send a refresh request to the agent to
make your changes take effect. If you don't send this request, your
changes will take effect the next time when the agent refreshes its
definitions (automatic refresh every midnight).
Activating an agent
To activate an agent:
1. Under _beta log|z option A.2.6, display the agent definition in the
"Agent Definition Table".
2. Enter line command S to display the "Update Agent Definition" panel,
set the field Active to Yes and confirm with ENTER.
Note: The field Online will be automatically set to Yes by the system
when the agent is started.
3. On the agent platform, check to make sure that the EJM agent is
running. Start it if necessary.
4. Under _beta log|z option A.2.6, return to the previous panel "Agent
Definition Table" and enter the line command RF in front of the agent.
The agent will retrieve its definitions from the _beta log|z system.
5. Check to make sure that the Online field has been set to Yes by the
system.
Result: The new agent is now active and online, and can be used for
processing.
Refreshing an agent
To send a refresh request to a single agent:
1. Under _beta log|z option A.2.6, display the agent definition in the
"Agent Definition Table".
2. Enter line command RF in front of the agent that you want to refresh.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
149
Enterprise (Option A.2)
Refreshing multiple
agents
Agent definitions (Option A.2.6)
You can use the primary command RFALL to send a refresh command to
all agents that are displayed in the "Agent Definition Table". The agent
refresh is triggered with the help of an update job (B92AGUPD).
To use the RFALL command:
1. Under _beta log|z option A.2.6, display the desired agents in the
"Agent Definition Table".
2. Enter the primary command RFALL in the command line.
This will display a panel with the jobcard from your profile.
3. Edit your jobcard if necessary and then press ENTER to submit the
update job.
Notes
•
B92AGUPD does not wait for a response from the agent (fire and
forget).
•
Administrators who are familiar with BQL can also submit B92AGUPD
directly from the BETA92.CNTL. You can adapt the selection criteria in
the WHERE statement according to your demands.
Important: The rest of the BQL statement must not be changed!
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
150
Enterprise (Option A.2)
Scan group definitions (Option A.2.S)
Scan group definitions (Option A.2.S)
Overview
A scan group (optional) defines one or more keywords. An agent can use
scan groups during file rule processing to determine whether a file is to be
transferred to _beta log|z or not.
Scan group processing
Scan groups affect agent-side processing and optionally host-side
processing (reader).
Agent-side processing
The keywords defined in a scan group are used on the agent side. When a
file rule references a scan group, the agent scans the contents of each file
that is covered by the rule before the transfer. The file is transferred only if
it contains all the keywords defined by the scan group.
Host-side processing
The name of a scan group can be referenced by scan definitions (Option
A.R.3), which are used by the reader for host-side processing. If the scan
group of a file rule is referenced by scan definitions, the reader applies
these scan definitions when it receives files that are covered by this file
rule.
Navigation
From the "Primary Selection Menu", choose:
•
Option A.2.S
The "Scan Group Definitions Selection" panel is displayed, in which
you can enter your selection criteria.
Insert Scan Group
Definition panel
This panel enables you to create a new scan group definition.
PE92SO41 --------------------------------------------------------------------Command ===> _________________________________________________________________
Insert Scan Group Definition
Scan Group Name ===> ........
Keyword
===> ...................................................
===> ___________________________________________________
===> ___________________________________________________
===> ___________________________________________________
===> ____________________________________________________
Separator
===> _
Description
===> __________________________________________________
Press ENTER key to insert this entry.
Press END key to cancel changes or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
151
Enterprise (Option A.2)
Fields
Scan group definitions (Option A.2.S)
Field
Description
Scan Group Name
Unique name of the scan group (required entry)
Scan Group Keyword
One or more keywords
Processing is case-sensitive. Use the character defined
in the next field as separator if your scan group defines
multiple keywords.
Line commands
Separator
Character used as separator between keywords
Description
Descriptive text (optional)
S
Selects the scan group definition for display or update
I
Adds a new scan group definition (insert)
C
Adds a new scan group definition (copy)
D
Deletes the scan group definition
Note: A scan group definition can be deleted only if it is not used in
a file rule or scan definition.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
152
Enterprise (Option A.2)
SAP system definitions (Option A.2.7)
SAP system definitions (Option A.2.7)
Overview
SAP servers and SAP accounts that belong together can be grouped into
SAP systems.
Navigation
From the "Primary Selection Menu", choose:
Option A.2.7
•
The "SAP System Selection" panel is displayed, in which you can
enter your selection criteria.
Insert SAP System
Definition panel
This panel enables you to create a new SAP system definition.
PE92EP72 --------------------------------------------------------------------Command ===> _________________________________________________________________
Insert SAP System Definition
Name
===> ........................
Description ===> ___________________________________________________
===> ___________________________________________________
===> ___________________________________________________
===> ___________________________________________________
===> ____________________________________________________
Press ENTER key to insert this entry.
Press END key to cancel changes or HELP key for help information.
Fields
Field
Description
Name
Unique name of the SAP system (required entry)
Description
Descriptive text (optional)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
153
Enterprise (Option A.2)
Line commands
Adding an SAP server to
an SAP system
SAP system definitions (Option A.2.7)
The following line commands are available in the "SAP System Definition
Table".
S
Selects the SAP system definition for display or update
I
Inserts SAP systems
C
Copies SAP systems
D
Deletes SAP systems
LS
Lists all connected SAP servers to the SAP system
LU
Lists all connected SAP accounts to the SAP system
MS
Adds an SAP server to an SAP system
MU
Adds an SAP account to an SAP system
To add an SAP server to an SAP system:
1. In the "SAP System Definition Table", enter the line command MS in
front of an SAP system.
The following panel appears:
PE92EP74 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Move SAP Server to SAP System
Move SAP Server
SAP Server Name
===> ........
(* for list)
to SAP System
SAP System Name
:
ROMYS 2ND TST SAP SYSTEM
Press ENTER key to update sap server entry.
Press END key to cancel changes or HELP key for help information.
2. Enter an SAP server name or enter an asterisk * to display all SAP
servers, select one by entering S in front of the respective SAP server
you want to use, and press ENTER.
You will see the SAP System Definition table and the message that
the SAP server has been added to the SAP system.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
154
Enterprise (Option A.2)
Adding an SAP account
to an SAP system
SAP system definitions (Option A.2.7)
To add an SAP account to an SAP system:
1. In the "SAP System Definition Table", enter the line command MU in
front of an SAP system.
The following panel appears:
PE92EP75 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Move SAP Account to SAP System
Move SAP Account
SAP Account Name ===>
........
(* for list)
to SAP System
SAP System Name
:
ROMYS 2ND TST SAP SYSTEM
Press ENTER key to update sap account entry.
Press END key to cancel changes or HELP key for help information.
2. Enter an SAP account name or enter an asterisk * to display all SAP
accounts, select one by entering S in front of the respective SAP
account you want to use, and press ENTER.
You will see the "SAP System Definition Table" and the message that
the SAP account has been added to the SAP system.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
155
Enterprise (Option A.2)
SAP server definitions (Option A.2.8)
SAP server definitions (Option A.2.8)
Overview
SAP server definitions determine where SAP rules are processed.
An SAP server definition specifies where the SAP server can be found
(TCP/IP address) and which agent should be used.
Navigation
From the "Primary Selection Menu", choose:
•
Option A.2.8
The "SAP Server Selection" panel is displayed, in which you can enter
your selection criteria.
Insert SAP Server
Definition panel
This panel enables you to create a new SAP server definition.
PE92EP81 ---------------------------------------------------------- Page 1 of 2
Command ===> _________________________________________________________________
Insert SAP Server Definition
Name
Title
===> ........
===> ________________________
System Number
Agent
SAP System
===> ..
===> ________
===> ________________________
Active ===> NO.
Online
: NO
(Y)es, (N)o
(* for list)
(* for list)
TCP/IP Address ===> ...................................................
===> ___________________________________________________
===> ___________________________________________________
===> ___________________________________________________
===> ____________________________________________________
Description
===> ___________________________________________________
===> ___________________________________________________
Press ENTER to insert this entry or DOWN key to go to next page.
Press END key to cancel changes or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
156
Enterprise (Option A.2)
Fields
SAP server definitions (Option A.2.8)
Field
Description
Name
Enter a unique name for the SAP server (required
entry).
Title
Enter a title for the SAP server (optional, max. 24
characters).
Active
Enter Yes to activate this SAP server. Enter No if you
do not want the SAP server to perform any actions
(required entry).
Online
This field is automatically set to Yes (SAP server is
online) or No (SAP server is offline).
System Number
Enter the system number of the SAP server (required
entry).
Agent
Enter a name of an agent which is to be connected to
the SAP server or '*' to select an agent from the
displayed list (required entry before the SAP server can
be activated).
SAP System
Enter a name of an SAP system which is to be
connected to the SAP server or '*' to select an SAP
system from the displayed list (optional).
TCP/IP Address
Enter the TCP/IP address of the SAP server (required
entry).
Description
Enter a description of the SAP server (optional).
Use the second panel if you do not have enough space
to enter the description in the first panel. You can enter
up to 256 characters for the agent description.
Line commands
The following line commands are available in the "SAP Server Definitions
Table".
S
Selects the SAP server definition for display or update
I
Adds a new SAP server definition (insert)
C
Adds a new SAP server definition (copy)
D
Deletes the SAP server definition
LR
Lists the rules connected to the SAP server
DA
Displays the agent connected to the SAP server
AS
Adds the SAP server to a rule
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
157
Enterprise (Option A.2)
Connected rules
SAP server definitions (Option A.2.8)
The Connected Rule field in the "SAP Server Selection" panel enables
you to select SAP servers according to the rules which are connected.
Line command LR in the "SAP Server Definition Table" shows connected
rules in the "Rule Definition Table". The line commands in the "Rule
Definition Table" can be used to modify the rule definitions.
Adding an SAP server to
a rule
To add an SAP server to a rule:
1. In the "SAP Server Definition" table enter the line command AS in front
of an SAP server.
The following panel appears:
PE92EP85 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Add SAP Server to SAP Rule
Add SAP Server
SAP Server Name
:
RODSAPS1
to SAP Rule
Rule Name
===> ........
(* for list)
Press ENTER key to update rule entry.
Press END key to cancel changes or HELP key for help information.
2. Enter a rule name, or enter an asterisk * to display all rules, then select
one by entering S in front of the respective rule, and press ENTER.
You will see the "SAP Server Definition" table and the message that
the SAP server has been added to a rule.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
158
Enterprise (Option A.2)
SAP account definitions (Option A.2.9)
SAP account definitions (Option A.2.9)
Overview
An SAP account definition contains information on an SAP user who is
allowed to log onto a system.
Navigation
From the "Primary Selection Menu", choose:
Option A.2.9
•
The "SAP Account Selection" panel is displayed, in which you can
enter your selection criteria.
Insert Agent Definition
panel
This panel enables you to create a new SAP account definition.
PE92EP91 ---------------------------------------------------------- Page 1 of 2
Command ===> _________________________________________________________________
Insert SAP Account Definition
Account Name ===> ........................
Client
User Name
Language
Password
===> ...
===> ............
===> ..
===>
SAP System
===> ________________________
Account Key
===> ___________________________________________________
===> ___________________________________________________
===> _________________________________________
Description
===> ___________________________________________________
===> ___________________________________________________
(* for list)
Press ENTER to insert this entry or DOWN key to go to next page.
Press END key to cancel changes or HELP key for help information.
Fields (Page 1)
Field
Description
Account Name
Enter a unique name of the SAP account (required
entry).
Client
Enter a client number (required entry). The number of
the client is defined in the SAP system. The SAP user
specified here must be authorized to access this
system.
User Name
Enter the name of an SAP user who is allowed to log on
to the SAP system (required entry).
Language
Determine the language (enter D for German or E for
English) in which the SAP system output of jobs is to be
generated for the specified user (required entry).
Password
Define the internally used SAP password (max. 40
digits). The entry is case-sensitive. The password is
used when the SAP user is logging on to the SAP
system (required entry).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
159
Enterprise (Option A.2)
SAP account definitions (Option A.2.9)
Field
Description
SAP System
Enter the name of the SAP system to which the SAP
account belongs or '*' to display a list of all matching
SAP systems, enter S in front of the SAP system you
want to use, and press ENTER (optional entry).
Account Key
A character string (up to 143 characters, optional)
The account key is included in the SMF records for
client-based billing, which are written when the
B92UXSMF exit is active. By default, it is inactive.
For more information, see "B92UXSMF: Client-based
billing SMF record exit" in _beta log|z Installation and
System Guide.
Description
Enter a description of the SAP account
(up to 256 characters, optional).
Use the second panel if you do not have enough space
to enter the description in the first panel.
Line commands
The following line commands are available in the "SAP Account Definition
Table".
S
Display or edit an SAP account definition
I
Insert an SAP account definition
C
Copy an SAP account definition
D
Delete an SAP account definition
LR
List the rules connected to an SAP account
For a description of the line command, see "Connecting an
operation to a rule" on page 139.
AU
Adds an SAP account to a rule
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
160
Enterprise (Option A.2)
Working with file operations for normal logs
Working with file operations for normal logs
Overview
Normal logs can be transferred to _beta log|z and archived there.
In _beta log|z, the normal logs can be found under option O.1.
File operations for
normal logs
The log type (normal) is defined in the file operation (Option A.2.3).
File operations for normal logs assume that files are not changed after the
creating application or system has finished writing.
File operations for normal logs can process ASCII files in Unix/Windows
environments and they can process binary files. The agent detects the file
type on the basis of the MIME-type definition for the file extension (see
"MIME-type handling when transferring files to _beta log|z" in _beta job|z
Installation and System Guide).
The use of wildcards in the file operation enables the processing of normal
logs in multiple subdirectories. You can use wildcards in the path and in
the file name.
Example: IWS output
IWS stores its output files with job-related content in these subdirectories:
Use wildcards in the file operation to process and archive this output:
ABC/AB/*/*.txt
All files with the extension txt in all subdirectories one hierarchy below the
subdirectory AB (here: 19.09.2007 - 21.09.2007) will be found and
processed.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
161
Enterprise (Option A.2)
Working with file operations for endless logs
Working with file operations for endless logs
Overview
Endless logs can be transferred to _beta log|z and archived there.
In _beta log|z, the endless logs can be found under option O.1, where they
are displayed with status L.
File operations for
endless logs
The log type (endless) is defined in the file operation (Option A.2.3).
Processing
Endless logs are transferred without any data overlap. The agent notes
and records the line number.
File operations for endless logs assume that an application or system
continually writes data into the same file.
One job ID is used for each endless rule per agent and per day. The
submit date is the date on which the rule is executed. The submit time is
set to 00:00:00.
The DDNAME is used to identify the individual parts of an endless log in
the same way as it is for the host system logs. Here the time at which the
relevant part of the endless log was archived is also noted and recorded.
Note: When you delete a log, the line number is not saved because the
complete file is always archived like a normal file rule. The job ID, submit
date and time for subsequent logs are handled in the same way as
described above.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
162
Enterprise (Option A.2)
Working with file operations for Windows event logs
Working with file operations for Windows event logs
Overview
Windows event logs are endless log types such as system logs, security
logs and application logs. They can be transferred to _beta log|z and
archived there. In _beta log|z, the Windows event logs can be found under
option O.1, where they are displayed with status L.
Prerequisites
_beta log|z uses the _beta job|z agent and Windows PowerShell for
retrieving Windows event logs.
Windows PowerShell must be installed on the Windows machine. The
execution policy of Windows PowerShell must allow the execution of local
unsigned scripts.
The minimum PowerShell version is V2, but using a higher version is
recommended because of enhanced functionality. For example, in higher
versions of PowerShell, you can define different execution policies
depending on scope. If you are using PowerShell V2, .NET Framework
V3.5 must be installed on the Windows machine (even if a higher .NET
Framework version is present).
Important note on execution policy:
The 64-bit version of PowerShell and the 32-bit version of PowerShell
have separate environments. As of V7.1, the EJM agent is a 64-bit
application and will therefore call the 64-bit version of PowerShell.
Previous versions of the EJM agent are 32-bit applications and will
therefore call the 32-bit version of PowerShell. Make sure that you define
the execution policy for the appropriate version of PowerShell.
As of PowerShell V3, you can define the appropriate execution policy
(RemoteSigned or Unrestricted) for the local machine or for individual
users.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
163
Enterprise (Option A.2)
Event types
Working with file operations for Windows event logs
The log type (Windows event log) and the Windows event type are defined
in the file operation (Option A.2.3).
Use the File Name field of the file operation definition to specify the event
type. Names are case insensitive, but must otherwise be entered exactly
with/without blanks as shown below.
•
Application
•
ForwardedEvents
•
HardwareEvents
•
Internet Explorer
•
Key Management Service
•
Security
•
Setup
•
System
•
Windows PowerShell
Which event types are available depends on the Windows version.
Which Windows event logs can be transferred to _beta log|z also depends
on your system setup, for example, whether your Windows system security
settings allow this.
Example of a Windows event log
Date
Time
Event-Type
Source
Computer Name
User
----------------------------------------------------------------------------------------------------------25.08.2007 06:47:21 Information EventLog
BLN-GX270
N/A
Event: The Event log service was stopped.
25.08.2007 07:02:20 Information EventLog
BLN-GX270
N/A
Event: Microsoft (R) Windows 2000 (R) 5.0 2195 Service Pack 3 Uniprocessor Free.
25.08.2007 07:02:20 Information EventLog
BLN-GX270
N/A
Event: The Event log service was started.
25.08.2007 07:02:31 Information SNMP
BLN-GX270
N/A
Event: The SNMP Service has started successfully.
13.09.2007 11:43:35 Information EventLog
BLN-GX270
N/A
13.09.2007 11:43:35 Information EventLog
BLN-GX270
N/A
Event: The Event log service was started.
13.09.2007 11:49:31 Error
NETLOGON
BLN-JEK1DSKW2
N/A
Event: Attempt to update DNS Host Name of the computer object
in Active Directory failed. The updated value was 'bln-gx270.de.eu.beta.ads'.
The following error occurred:
The security context could not be established due to a failure in the requested quality
of service (e.g. mutual authentication or delegation).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
164
Enterprise (Option A.2)
Transferring a Unix system log to _beta log|z
Transferring a Unix system log to _beta log|z
Overview
A Unix system log can be transferred to _beta log|z.
Processing
First a Unix system log is written to a file via the _beta job|z agent program
b92syslog. Several filters can be used when writing the file.
The agent program b92syslog appends the system log messages to the
output file.
Next the Unix system log is transferred to _beta log|z via an endless rule,
for example, SYSLRUL$.
This ensures that no system log information is lost.
Prerequisites
•
The Unix system program syslog-ng must be available on the Unix
machine.
We recommend that you use version 2.0 or higher of the program
syslog-ng because then the agent program b92syslog will be
automatically restarted when it has been stopped or canceled for
whatever reason. When lower versions are used, the program
b92syslog must be restarted manually.
•
An endless rule must be available in _beta log|z (Option A.2.2).
You can use the sample file rule SYSLRUL$ as a basis. You only have
to add your agent group and your rule group to the rule.
Procedure
1. On your Unix system, customize your syslog-ng configuration in
/etc/syslog-ng/syslog-ng.conf according to your needs:
•
Define a source (optional).
•
Define a destination with the program driver b92syslog (required).
The agent program b92syslog has to be entered in the
configuration file syslog-ng.conf of the Unix system program
syslog-ng. If no parameters for the program b92syslog have
been entered in the destination statement of the file syslogng.conf, the output file will automatically be stored under the
following name: agent installation directory/logs/b92syslog.out.
•
Define a log (required).
See the example below:
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
165
Enterprise (Option A.2)
Transferring a Unix system log to _beta log|z
# sample configuration file for syslog-ng on AIX
# customize to your needs
# log syslog-ng's own messages to /var/log/syslog-ng.log
source s_internal {
internal();
};
destination d_syslognglog {
file("/var/log/syslog-ng.log" owner("root") group("adm") perm(0640));
};
log {
source(s_internal);
destination(d_syslognglog);
};
#...
#syntax:
#source Beta 92 logical source identifier {
#
...
#};
#destination Beta 92 syslog destination {
#
program( "/agent installation directory/bin/b92syslog
#
../logs/Beta 92 syslog output file name.out" );
#};
#log {
#
source(Beta 92 logical source identifier);
#
destination(Beta 92 syslog destination);
#};
#example:
source src {
#
...
};
destination b92sysdest {
program( "/opt/BetaSystems/EJM/Agent/bin/b92syslog ../logs/mysyslog.out" );
};
log
{
source(src);
destination(b92sysdest);
};
2. Restart the program syslog-ng.
The program syslog-ng starts the agent program b92syslog which
writes the Unix system log to the specified file.
3. Activate the endless rule on the _beta log|z system, for example, the
sample rule SYSLRUL$ (option A.2.2), to transfer the system log file
from the Unix system to the _beta log|z system.
4. Make sure that your Unix agent is active and online.
The repeat time of the run cycle in the sample rule SYSLRUL$ is once
per day. The result is then displayed under option L (when the job
name starts with SYSL); otherwise the Unix system log is stored under
option O.1.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
166
Enterprise (Option A.2)
Example: Unix system
log transferred to _beta
log|z (Option L)
Transferring a Unix system log to _beta log|z
PE92SL10 ------------------------------------------------ Row
1 of
1
Command ===> ________________________________________________ Scroll ===> PAGE
Syslog Select Table
S,? - Select a syslog
P,M - Print/Mail a syslog
I - Reset input queue
N - Change user notes
Sorted by Submit Date and Time D
Displayed Submit date and time
W - Toggle work queue
K - Toggle keep status
T - Toggle non-retain
X - Toggle nokeep status
B - Browse a syslog
E - Toggle error queue
R - Reload offline syslog
Sel Jobname
System
Date
Time
Type
S SYSLRUL$ AVSCHM1 04/09/08
00:00:00 OPEN SYSTEMS
******************************** BOTTOM OF DATA ********************************
A Unix system log displayed in the browser:
PE23BRW1 Browse
Page 1
Line 1
Cols 1
80
Command ===>
Scroll ===> CSR
RULENAME: SYSLRUL$
JOBID: FAAQ6564 EXTENSION:
FILENAME: 12:45:49
PAGES: 1
LINES: 13
-----------------------------------------------------------------------------2008-04-09T11:20:22+00:00 notice local2 libra sudo sudo: [ID 702911 local2.notic
2008-04-09T11:20:22+00:00 info syslog libra syslog-ng syslog-ng[13150]: Terminat
2008-04-09T11:20:22+00:00 notice syslog libra syslog-ng syslog-ng[13150]: syslog
2008-04-09T11:22:48+00:00 notice local2 libra sudo sudo: [ID 702911 local2.notic
2008-04-09T11:22:48+00:00 notice syslog libra syslog-ng syslog-ng[13514]: syslog
2008-04-09T11:32:48+00:00 info syslog libra syslog-ng syslog-ng[13514]: Log stat
2008-04-09T11:42:48+00:00 info syslog libra syslog-ng syslog-ng[13514]: Log stat
2008-04-09T11:52:48+00:00 info syslog libra syslog-ng syslog-ng[13514]: Log stat
2008-04-09T12:02:48+00:00 info syslog libra syslog-ng syslog-ng[13514]: Log stat
2008-04-09T12:12:48+00:00 info syslog libra syslog-ng syslog-ng[13514]: Log stat
2008-04-09T12:22:48+00:00 info syslog libra syslog-ng syslog-ng[13514]: Log stat
2008-04-09T12:32:48+00:00 info syslog libra syslog-ng syslog-ng[13514]: Log stat
2008-04-09T12:42:48+00:00 info syslog libra syslog-ng syslog-ng[13514]: Log stat
BOTTOM OF LIST -----------------------------------------------------------------
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
167
Enterprise (Option A.2)
Working with SAP operations for job logs
Working with SAP operations for job logs
Overview
The BC-XBP interface is used for reading job output data, for example, job
logs, and spool data.
The interface enables the system to find job output data on SAP and send
this data from SAP to the z/OS system for archiving.
SAP jobs
SAP jobs and SAP job definitions can be transferred to the z/OS system,
displayed (Option O.2) and archived (Option O.4).
Logs of SAP jobs
SAP logs of SAP jobs can be transferred to the z/OS system, processed,
displayed (Option O.2) and archived (Option O.4).
Due to identification reasons, only one SAP log may be transferred to the
z/OS system, processed, and archived for one SAP job.
Spool lists of SAP jobs
SAP spool lists of SAP jobs can be transferred to the z/OS system,
processed, displayed (Option O.2) and archived (Option O.4).
You can decide whether or not SAP spool lists of SAP jobs are to be
transferred to the z/OS system.
During SAP operation definition for the operation type joblog
(Option A.2.3), Yes must be entered in the field Read Spool (default No).
A number of spool lists may exist for one SAP job. The maximum number
of spool lists allowed for one SAP job is the same number as the number
of jobs steps for an SAP job. However, some job steps do not produce any
spool lists. The step number of the SAP job step, which created the spool
list, is stored in the _beta log|z step name field.
Child jobs of SAP jobs
The child jobs of SAP jobs can be transferred to the z/OS system,
processed, displayed (Option O.2) and archived (Option O.4).
You can decide whether or not the child jobs of SAP jobs are to be
transferred to the _beta log|z system.
During SAP operation definition for the operation type joblog
(Option A.2.3), Yes (default No) must be entered in the field Read
Childjobs.
The original SAP name of the SAP child job is displayed in the job
information table in the field Long JobName.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
168
Enterprise (Option A.2)
Application logs of SAP
jobs
Working with SAP operations for job logs
SAP application logs of SAP jobs can be transferred to the z/OS system,
processed, displayed (Option O.2) and archived (Option O.4).
One application log per SAP job can be transferred.
You can decide whether or not SAP application logs of SAP jobs are to be
transferred to the _beta log|z system.
During SAP operation definition for the operation type joblog
(Option A.2.3), Yes (default No) must be entered in the field Read Appl.
Log.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
169
Enterprise (Option A.2)
Working with SAP operations for endless logs
Working with SAP operations for endless logs
Overview
SAP system logs and SAP audit logs are endless logs.
The BC-XBP interface is used for reading these logs.
SAP system logs
SAP system logs can be transferred to the z/OS system, to the _beta log|z
system, processed, displayed (Option O.2) and archived (Option O.4).
The DD name is used for identifying all parts of one SAP system log (the
same applies to host system logs). The time when the respective part of
the SAP system log was archived is stored there.
In _beta log|z only one job ID is used for each SAP rule per agent and per
day. The submit date is always the current date of the SAP rule execution.
The agent automatically sets the submit time to 00:00:00. The transfer of
an SAP system log to the z/OS system is limited in time (max. 1 hour) and
in size (page limit).
During SAP operation definition (Option A.2.3), choose the SAP operation
type Syslog.
When you choose the SAP operation type Syslog, the fields Delete Log,
Read Spool, Read Childjobs, and Read Appl. Log must be left blank. No
input is allowed. The fields SAP Job Name, SAP Jobcount, and SAP
User must also be left blank.
Note: Due to an SAP-specific default, 80 pages per select can only be
transferred for an SAP system log.
SAP security audit log
SAP security audit logs can be transferred to the _beta log|z system,
processed, displayed (Option O.2) and archived (Option O.4).
SAP security audit logs are stored in _beta log|z in the same way as
Unix/Windows endless logs and are handled in the same way as SAP
system logs.
During SAP operation definition (Option A.2.3), choose the operation type
Auditlog to transfer SAP security audit logs to _beta log|z.
You can display the security audit log under option O.2.
Select a time period for the selection, select the respective rule in the "SAP
Job Select Table". You can use the line command S in front of the rule to
display the results of the rule run. In the "SAP Job Information Table" you
can select a rule run to display the SAP security audit log.
The SAP security audit log may contain messages coming from several
SAP servers.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
170
Enterprise (Option A.2)
Use case
Working with SAP operations for endless logs
You can set up _beta log|z to monitor the SAP security audit log and send
e-mail when it encounters relevant security messages in the log. The
following definitions are necessary in _beta log|z to achieve this:
•
Scan definition(s) with target field ID 550 (write event)
•
Event action for sending e-mail
The security-relevant message text that you want to scan for has to be
specified in the scan definition. When found, _beta log|z generates the
specified type of event in the EVT00 table. The associated event action
causes the sending of e-mail.
Time synchronization
There is normally no need to install _beta job|z agent directly on the SAP
application server because the agent communicates with SAP via the RFC
interface.
In order to ensure that the data to be archived from the SAP system is
selected correctly, there must be no time differences between the agent
and the SAP system. Otherwise, errors will be unavoidable. If it is not
possible to guarantee completely accurate synchronization at the data
center, the agent will have to be installed directly on the appropriate SAP
application server.
Runcyle intervals
The selection of SAP endless logs (system and audit log) takes place at
intervals of one run cycle.
The following example illustrates this:
Delete
From
Delete
Select
and
To
From
Run Cycle Interval
Run Cycle Interval
Select
To
Rule
Start
Run Cycle Interval
Current
Time
When the run cycle interval is set to one day and a starting time of 12:00,
the SAP rule will start every day at 12:00.
It selects all data (according to the operation) from the day before last and
archives them in _beta log|z. If the Delete flag is set for the relevant
operation, the data (according to the operation) from the day before the
day before last are deleted (the data had already been archived in _beta
log|z the day before).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
171
File tailoring (Option A.3)
In this chapter
File tailoring (Option A.3)
In this chapter
Topic
Page
Tailoring files........................................................................................... 173
Tailoring JCL for batch utilities (Option A.3.1) ........................................ 175
Deleting or reusing an empty GAR database (Option A.3.2) ................. 177
Adding a new GAR database (Option A.3.3).......................................... 180
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
172
File tailoring (Option A.3)
Tailoring files
Tailoring files
Overview
The file tailoring utilities under option A.3. enable the administrator to
generate complete maintenance batch jobs online and to administrate and
maintain the _beta log|z databases. This option complements the general
file tailoring utilities under A.D.4 (see "Generating JCL for database
utilities (Option A.D.4)" on page 385).
Note
We recommend that you use file tailoring to create and process batch
utilities and database utilities instead of adjusting the jobs by hand.
Please do not change the tailored values in the generated JCL of the
respective job. In case of an error, these jobs will automatically restore the
previous version of your database. This is possible due to conditional
processing paths which ensure that no former version will get lost.
During VDF sessions, file tailoring for options A.3.2 and A.3.3 is not
supported, please use ISPF instead. Option A.3.1 can be used under VDF.
SIGNON
For batch jobs which have indirect access to the product database (slave),
specify parameter SIGNON=YES. For batch jobs which have direct access
to the product database (master), specify parameter SIGNON=NO.
YES means the batch utility accesses the _beta log|z database via the
_beta log|z started task; the _beta log|z started task must be active when
you run the batch utility (default).
NO means the batch utility requests exclusive control of the _beta log|z
database; the _beta log|z started task must be inactive when you run the
batch utility.
You can use a DUMMY DD statement for B92DEF when the program
signs on to the product started task (SIGNON=YES).
Navigation
From the "Primary Selection Menu", choose:
•
Option A.3
The "Batch Job Generation Selection Menu" panel is displayed, from
which you can choose the desired option.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
173
File tailoring (Option A.3)
Batch Job Generation
Selection Menu
Tailoring files
PE92FT00 ---------------------------------------------------------------------Option ===> __________________________________________________________________
Batch Job Generation Selection Menu
System
- B92PROD
Location - BERLIN
Subsys-ID - B92P
User ID
- AVSCHM1
1
BATCH
-
Generate Batch Job for Batch Utilities
processing with signon=yes
2
GAR DATABASES
-
Generate Batch Job for Archive Generation Databases
processing with signon=no
3
GADD
-
Add New GAR Generation Database
processing with signon=yes
To generate other jobs for database maintenance please use option A.D.4.
Select one of the above options, or press END key to return to the previous
menu. Press the HELP key from any panel for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
174
File tailoring (Option A.3)
Tailoring JCL for batch utilities (Option A.3.1)
Tailoring JCL for batch utilities (Option A.3.1)
Overview
The file tailoring function enables you to generate executable JCL for
selected batch utilities.
Batch utilities
Following is a list of the batch utilities offered under option A.3.1:
Option
Batch utility
For more information, see...
D
DAILY
B92DAILY
"B92DAILY: Daily job" on page 442
D1 ARPRI
B92ARPRI
"B92ARPRI: List archiving" on page 400
D2 CLLST
B92CLLST
"B92CLLST: List cleanup" on page 437
D3 ARSEC
B92ARSEC
"B92ARSEC: Job record cleanup" on page 406
WEEKLY
B92WEEKL
"B92WEEKL: Weekly job" on page 520
W1 CLARC
B92CLARC
"B92CLARC: Archive cleanup" on page 424
W2 CLAR2
B92CLAR2
"B92CLAR2: Clear extended generation archive
records" on page 421
W3 CLARS
B92CLARS
"B92CLARS: Cleanup for agent rule status and
statistics" on page 429
W4 CLEVT
B92CLEVT
"B92CLEVT: Clearing events" on page 434
W
The batch utilities of option D1 through D3 are included in B92DAILY.
The batch utilities of option W1 through W4 are included in B92WEEKL.
Procedure
1. Enter option 1 in the "Batch Job Generation Selection" menu to display
the "Batch Job Generation for Batch Utilities" panel:
PE92FT01 --------------------------------------------------------------------Command ===> _________________________________________________________________
Batch Job Generation for Batch Utilities
System
- B92PROD
Location - BERLIN
Subsys-ID - B92P
User ID
- REINH1
Generate Batch Job for:
D
D1
D2
D3
DAILY
ARPRI
CLLST
ARSEC
- Daily Job
- List Archiving
- List Cleanup
- Job Record Cleanup
W
W1
W2
W3
W4
WEEKLY - Weekly Job
CLARC - Archive Cleanup
CLAR2 - Archive Cleanup (Extended Records)
CLARS - ARSTATUS, B92 & Rdr Stat. Cleanup
CLEVT - Event Cleanup
Run in Analyze Mode
===> _ (Y/N)
Days ===> ___
Days ===> ___ / ___ / ___
Days ===> ___
Analyze Mode = yes is not
available for Options D and W.
Press ENTER key to proceed processing this selection.
Press END key to cancel changes or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
175
File tailoring (Option A.3)
Tailoring JCL for batch utilities (Option A.3.1)
2. Type the desired option in the command line, specify values in the
fields of the panel (Run in Analyze Mode and Days) where
appropriate, and press ENTER.
Values in the Days field(s) are required for options W2 through W4.
The value of the Run in Analyze Mode field is honored by options D1
through D3 and W1 through W4, but not by option D (B92DAILY) and
W (B92WEEKL).
For example, the following combination of entries generates JCL for
B92CLARS (cleanup agent rule status and/or statistics) in analyze
mode:
PE92FT01 --------------------------------------------------------------------Command ===> W3_______________________________________________________________
Batch Job Generation for Batch Utilities
System
- B92PROD
Location - BERLIN
Subsys-ID - B92P
User ID
- REINH1
Generate Batch Job for:
D
D1
D2
D3
DAILY
ARPRI
CLLST
ARSEC
- Daily Job
- List Archiving
- List Cleanup
- Job Record Cleanup
W
W1
W2
W3
W4
WEEKLY - Weekly Job
CLARC - Archive Cleanup
CLAR2 - Archive Cleanup (Extended Records)
CLARS - ARSTATUS, B92 & Rdr Stat. Cleanup
CLEVT - Event Cleanup
Run in Analyze Mode
===> Y (Y/N)
Days ===> ___
Days ===> 10_ / 730 / 30_
Days ===> ___
Analyze Mode = yes is not
available for Options D and W.
Press ENTER key to proceed processing this selection.
Press END key to cancel changes or HELP key for help information.
The JCL is generated and displayed in the Browser when you press
ENTER. You can submit the JCL or save it in a member for later use.
In the example, the entries in the Days fields are reflected by the
SYSIN parameters ARS_DAYS(10), STAT_DAYS(730) and
RDR_DAYS(30). The entry Run in Analyze Mode = Y is reflected by
the EXEC parameter TYPE=ANALYZE.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
176
File tailoring (Option A.3)
Deleting or reusing an empty GAR database (Option A.3.2)
Deleting or reusing an empty GAR database (Option A.3.2)
Overview
_beta log|z uses generation archive (GAR) databases for storing
information on archived jobs. We recommend that you work with yearly
generations (see "Working with generation archive (GAR) databases" on
page 195).
This section describes how you can remove or reuse an old GAR
database after it has become empty. A GAR database becomes empty
when all jobs that have been archived during this year have expired.
DELETE vs. REUSE
The following should be taken into account when you decide what to do
with empty GARs:
•
Generation ID
The generation ID is preserved when you reuse an old GAR database.
The highest ID no longer indicates the newest data when you REUSE.
Do not REUSE if the highest ID should indicate the newest data.
•
SIGNON=YES vs. SIGNON=NO
A job with SIGNON=NO requires exclusive access. The STC and all
other access to the database must be stopped when you run this job.
A REUSE job requires SIGNON=NO. A DELETE job that removes the
references to the GAR database and the VSAM datasets also requires
SIGNON=NO.
A DELETE job that only removes the references from the _beta log|z
database can run with SIGNON=YES. (And you can later delete the
actual VSAM datasets later after an STC restart.)
Instructions
To generate JCL for deleting/reusing a GAR database:
1. Select option A.3.2.
The GAR databases are displayed in a table.
2. Enter the line command S in front of a database entry with
Empty=YES and follow the instructions in the displayed panels.
Notes:
•
The GAR database to be deleted or reused has to be empty.
•
Option A.3.2 will not let you generate JCL for a GAR database that is
not empty.
•
A DELETE/REUSE job will terminate with an error if the GAR
database is not empty.
•
You can save the generated JCL in a member for later use.
JCL with SIGNON=YES can also be submitted directly.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
177
File tailoring (Option A.3)
Deleting or reusing an empty GAR database (Option A.3.2)
Deleting an empty GAR
A DELETE job includes the following steps:
Step 1:
Removing the definition of the GAR database from the
database definition file
Step 2:
Deleting the generation index entry of the GAR database from
the GIR table
Optionally, you can include a step that deletes the VSAM datasets:
Step 3:
Deleting the generation index entry of the GAR database from
the GIR table
Option A.3.2 let's you choose between the following:
•
Generating JCL with SIGNON=NO that includes all 3 steps
•
Generating JCL with SIGNON=YES for only the first 2 steps
This job removes the references from the _beta log|z database. (And
you can delete the VSAM datasets later after an STC restart.)
The corresponding panel where you can choose between the two options
looks like this:
PE92FT27 --------------------------------------------------------------------Command ===> _________________________________________________________________
Delete empty Archive Generation Database
Generation ID
Last Date
Database Name
:
:
:
01
1994-12-31
PROD.V3BETA92.ARCH1994.G01
System
- PROD
Location - BERLIN
Subsys-ID - B92P
User ID
- B92ADM1
Determine if you want to remove only the reference to the Archive Generation
DB from the B92DEF file or if you want to delete the VSAM file as well.
Delete VSAM file
===> N (Y/N)
For Y you need to stop the started task
prior to submitting the job.
If you choose N you have to delete the
VSAM file later by yourself,
but the started task can remain running.
Press ENTER key to proceed the file tailoring processing.
Press END key to cancel changes or HELP key for help information.
Fields
Field
Description
Delete VSAM file
N
Generates JCL with SIGNON=YES for removing the
references only
Y
Generates JCL with SIGNON=NO for removing the
references and deleting the VSAM datasets
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
178
File tailoring (Option A.3)
Deleting or reusing an empty GAR database (Option A.3.2)
Reusing an empty GAR
The REUSE job changes the last date in the GIR record that belongs to
the GAR database. It also lets you change the name of the GAR database
so that it can reflect the year for which it is used.
The corresponding panel where you can enter the required values looks
like this:
PE92FT25 --------------------------------------------------------------------Command ===>
Reuse an empty GAR Database
Generation ID
:
02
Last Date
===> 12/31/2020
Old Database Name
:
New Database Name
===> BETA92.DB.ARCH2020.G01
(optional)
System
- PROD
Location - BERLIN
Subsys-ID - B92P
User ID
- AVSCHM1
BETA92.DB.ARCH2008.G01
Press ENTER key to proceed processing this selection.
Press END key to cancel changes or HELP key for help information.
Fields
Field
Description
Generation ID
The ID number of the selected generation is displayed.
Last Date
Enter the new end date for the generation. Jobs will be
archived up to this date in the database. A suggestion is
already given. If necessary (although not
recommended), you can change the date to adjust it to
your special requirements. This field is required.
OLD Database Name
The name of the selected database is displayed.
NEW Database Name
Enter a new name for the GAR database to adjust it to
the new date. If possible, a suggestion is already given.
An entry in this field is optional.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
179
File tailoring (Option A.3)
Adding a new GAR database (Option A.3.3)
Adding a new GAR database (Option A.3.3)
Overview
This option enables you to generate an executable batch job to insert a
new GAR database.
Note: Before submitting the generated job, it is not necessary to stop the
running _beta log|z started task or jobs accessing the _beta log|z
database (SIGNON=YES).
Procedure
1. Enter option 3 in the "Batch Job Generation Selection" menu to display
the "Add New GAR Generation Database" panel:
PE92FT03 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Add New GAR Generation Database
System
- B92PROD
Location - BERLIN
Subsys-ID - B92P
User ID
- AVSCHM1
Generation ID
Last Date
:
03
===> 12/31/2014
Database Name
===> BETA92.V7R2Mx.VSAM.GARD03..............
Current GAR Space
:
000010
Prim. Space in Cyls ===> ......
SMS-Managed
===> Y (Y/N)
Sec. Space ===> ______
Volume ===> ______
Optional SMS-Parameters
Storage Class
===> ________
Data Class
===> ________
Management Class
===> ________
Press ENTER key to proceed processing this selection.
Press END key to cancel changes or HELP key for help information.
2. Enter your specific values.
3. Press ENTER to generate the job and submit it.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
180
File tailoring (Option A.3)
Fields
Adding a new GAR database (Option A.3.3)
Field
Description
Generation ID
The ID number of the selected generation is displayed.
Last Date
Enter the new end date for the generation. Jobs are
archived up to this date in the database. A suggestion is
already given. If necessary (although not
recommended), you can change the date to adjust it to
your special requirements. This field is required.
Database Name
Enter the new name of the database here. If possible, a
suggestion is already given. An entry in this field is
required.
Current GAR Space
The space of the previous GAR database in cylinders is
displayed here.
Prim. Space in Cyls
Define the space in cylinders which is be used for the
allocation of the new GAR database. An entry in this
field is required.
SMS-Managed
Enter Yes if you want to use SMS managed volumes.
Entering No requires a volume. This field is required.
Sec. Space
Define a secondary space for the database in cylinders.
Volume
Enter the volume on which the database is to be
allocated. An input in this field is required when SMS
managed=No has been coded.
Storage Class
Enter the name of the storage class that is be used to
determine the unit and volume characteristics of the
database when it is created. This field is optional.
Data Class
Enter the name of the data class to obtain database
characteristics, such as record format, record length,
etc. for the database allocation. This field is optional.
Management Class
Indicate the name of the management class for the new
database. The attributes of a management class serve
the control database migration and backup after the
database has been allocated. This field is optional.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
181
Monitor (Option A.M)
In this chapter
Monitor (Option A.M)
In this chapter
Topic
Page
Displaying agent rule status information (Option A.M.1) ........................ 183
Which rules are planned for execution and at what time?.................. 185
Displaying rule definitions ................................................................... 186
Displaying jobs and logs read in by a rule .......................................... 187
Displaying definitions of the agent connected to a rule ...................... 188
Displaying or processing reload requests (Option A.M.2) ...................... 189
Displaying _beta log|z statistics (Option A.M.3) ..................................... 191
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
182
Monitor (Option A.M)
Displaying agent rule status information (Option A.M.1)
Displaying agent rule status information (Option A.M.1)
Overview
You can use option A.M.1 to view agent rule status information without
having to search for it in the Enterprise administration menu (Option A.2).
If a job does not run, its logs are not sent to _beta log|z (error case). In this
case you can search for status information on the relevant agent and its
rule to find the error.
Alternatively, you can view the "Agent-Rule Status Table" displayed by line
command ST under option A.2.6
Agent rule cleanup
Agent rule status information is cleaned up together with other statistical
data by the B92CLARS batch utility, which has to run on a regular basis.
For more information on this utility and recommended frequency, see
"B92CLARS: Cleanup for agent rule status and statistics" on page 429.
Procedure
To display information on rules and the agents connected to a rule,
proceed as follows:
1. In the primary panel enter A.M.1 for option "ARSTATUS - Display
Agent-Rule Status Information".
The following panel is displayed:
PE92AR00 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Display Agent-Rule Status Information by Planned Execution Time
Select from last
===> 1_
days___
Start Date
End
Date
===> TODAY.....
===> TODAY.....
Rule Name
Rule Type
Agent Name
===> ________
===> ________
===> ________
Last Error Code
===> ________
1-99, (m)inutes, (h)ours, or (d)ays
Start Time
End
Time
===> 00:00:00
===> 23:59:59
(F)ILERULE,(S)APRULE or blank
Press ENTER key to display Agent-Rule Status.
Press END key to return to the previous menu.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
183
Monitor (Option A.M)
Displaying agent rule status information (Option A.M.1)
2. Enter the selection criteria you want to use and press ENTER.
The following panel is displayed:
PE92AR10 -------------------------------------------------- Row
1 of
27
Command ===> ________________________________________________ Scroll ===> PAGE
Agent-Rule Status Table
S - Select Status Record
DR - Display Rule
DJ - Display Job
DA - Display Agent
Rule
Rule
Agent
Planned Execution
Last Success
Error
Sel Name
Type
Name
Date
Time
Date
Time
Code
REHFRULE FILERULE REHAGENT 10/05/08
00:36:08 10/05/08
00:36:08
REHFRULE FILERULE REHAGENT 10/05/08
00:06:08 10/05/08
00:06:08
REHFRULE FILERULE REHAGENT 10/05/08
04:06:08 10/05/08
04:06:08
REHFRULE FILERULE REHAGENT 10/05/08
03:36:08 10/05/08
03:36:08
REHFRULE FILERULE REHAGENT 10/05/08
03:06:08 10/05/08
03:06:08
REHFRULE FILERULE REHAGENT 10/05/08
02:36:08 10/05/08
02:36:08
REHFRULE FILERULE REHAGENT 10/05/08
02:06:08 10/05/08
02:06:08
REHFRULE FILERULE REHAGENT 10/05/08
01:36:08 10/05/08
01:36:08
REHFRULE FILERULE REHAGENT 10/05/08
01:06:08 10/05/08
01:06:08
REHFRULE FILERULE REHAGENT 10/05/08
08:36:08 10/05/08
08:36:08
REHFRULE FILERULE REHAGENT 10/05/08
08:06:08 10/05/08
08:06:08
REHFRULE FILERULE REHAGENT 10/05/08
07:36:08 10/05/08
07:36:08
REHFRULE FILERULE REHAGENT 10/05/08
07:06:08 10/05/08
07:06:08
REHFRULE FILERULE REHAGENT 10/05/08
06:36:08 10/05/08
06:36:08
0
0
0
0
0
0
0
0
0
0
0
0
0
0
You can display the agent rule information using the following line
commands: S - select status record, DJ - display job, DR - display rule,
DA - display agent.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
184
Monitor (Option A.M)
Displaying agent rule status information (Option A.M.1)
Which rules are planned for execution and at what time?
Agent rule status level
You can display the agent rule status level. The planned execution date
and time of a rule is displayed here.
Procedure
To display agent rule information, proceed as follows:
1. Follow the procedure described in "Displaying agent rule status
information (Option A.M.1)" on page 183.
2. Enter the line command S in front of a rule.
You will see information on the rule, the planned execution date and
time of the rule, and information on error codes:
PE92EP68 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Display Agent-Rule Status
Rule Name
Rule Type
:
:
REHFRULE
FILERULE
Planned Execution of Rule
Date
: 10/05/08
Time
: 00:36:08
Last Error Code :
Last Error
Description
:
Agent Name
:
REHAGENT
Last Successful Execution of Rule
Date
: 10/05/08
Time
: 00:36:08
0
Finished normally [11 file(s) processed]. Rule
ended.
Press END key to return to previous menu or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
185
Monitor (Option A.M)
Displaying agent rule status information (Option A.M.1)
Displaying rule definitions
Rule definitions
You can jump directly from the agent rule status table to the definitions for
the corresponding rule.
Procedure
To display the definitions of a rule, proceed as follows:
1. Follow the procedure described in "Displaying agent rule status
information (Option A.M.1)" on page 183.
2. Enter the line command DR in front of a rule.
Details on the rule definition will be displayed:
PE92EP26 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Display Rule Definition
Name
Type
:
:
Title
:
Rule Group
Runcycle
File Operation
Agent Group
Scan Group
:
:
:
:
:
Description
:
REHFRULE
FILERULE
Last update: AVSCHM2
10/02/08
Active
:
13:03:34
YES
REHFRULEGROUP
EVERYHALFHOUR
REHFOPER
REHAGENTGROUP
RENASCAN
Press END key to return to previous menu or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
186
Monitor (Option A.M)
Displaying agent rule status information (Option A.M.1)
Displaying jobs and logs read in by a rule
Lists and logs of a job
You can jump directly from the agent rule status table to the lists of a job.
You can display first the job that has already been read in, and then the
corresponding logs.
Procedure
To display the jobs and logs read in by a rule, proceed as follows:
1. Follow the procedure described in "Displaying agent rule status
information (Option A.M.1)" on page 183.
2. Enter the line command DJ in front of a rule.
The following panel is displayed:
PE92BF10 ------------------------------------------------ Row
1 of
1
Command ===> ________________________________________________ Scroll ===> PAGE
File Rule Select Table
Sorted by Submit Date and Time D
Displayed End date and time
S,? - Select a rule
W - Toggle work queue
P,M - Print/Mail all logs T - Toggle non-retain
I - Reset input queue
B - Browse all logs
N - Change user notes R,U - Reload offline logs
K - Toggle keep status
X - Toggle nokeep status
E - Toggle error queue
Sel Rulename Agent
Operation
Date
Time
Status
Error
User
REHFRULE REHAGENT REHFOPER 10/05/08
00:36:09 I
******************************** BOTTOM OF DATA ********************************
3. Enter one of the available line commands, for example, line command
B to browse all logs.
Further information is also provided, depending on whether you have
selected the file rule type File Rule or SAP Rule (File Rule Select
Table or SAP Rule Select Table).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
187
Monitor (Option A.M)
Displaying agent rule status information (Option A.M.1)
Displaying definitions of the agent connected to a rule
Agent definitions
You can jump directly from the agent rule status table to the definitions of
the agent belonging to a particular rule.
Procedure
To display the jobs and logs read in by a rule, proceed as follows:
1. Follow the procedure described in "Displaying agent rule status
information (Option A.M.1)" on page 183.
2. Enter the line command DA in front of a rule.
The following panel is displayed:
PE92EP64 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Display connected Agent
Name
:
CHK62L10
Title
Last update: KLAUK1
11/16/2017 13:25:38
:
Active
beta logz SSID
Port Number
TCP/IP Address
:
:
:
92T1
SSL Encryption
10210
Priority
VM-SLES10XDV.DEVELOP.BETA.ADS
Router Port
Router Address
:
:
0
Account Key
Description
:
:
Version
: V6.2 B12
Online
: YES
Last Refresh: 08/20/2018 11:56 by KLAUK2
:
:
:
YES
NO
0
Oper. System : x86Linux
Offline Since: Last List
: 08/21/2018 14:18:01
Press END key to return to previous menu or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
188
Monitor (Option A.M)
Displaying or processing reload requests (Option A.M.2)
Displaying or processing reload requests (Option A.M.2)
Overview
_beta log|z offers a reload request function. This function enables you to
display or process all reload requests of all users that are still pending at
present.
When automatic reload has been activated, you can monitor the pending
reload requests under this option A.M.2. For information on using
automatic reload, see "Using automatic reload" on page 257.
Procedure
1. Select option M.2 - Reload Requests in the "Administration Selection
Menu" to display the following panel:
PE92RS20 -------------------------------------------------- Row
1 of
9
Command ===> ________________________________________________ Scroll ===> PAGE
Reload Request Selection
S - Select Reload Request
D - Delete Reload Request
Sel
Date
Time
Jobname
Job ID
Type
CUser
CTime
CDate
01/08/08
14:45:58 B92AGINF J0029531 00000000 AVSCHM
09:55:00 02/26/08
02/14/08
14:51:18 BXW#PR
J0010018 00000000 AVSCHM
18:10:15 02/25/08
02/14/08
14:55:14 JEKFRUL2 FAAK8540 00000000 AVSCHM
18:10:15 02/25/08
02/14/08
15:03:16 BXW#PR
J0010029 00000000 AVSCHM
18:10:15 02/25/08
02/14/08
15:11:36 BXW#PR
J0010044 00000000 AVSCHM
18:10:15 02/25/08
02/14/08
15:12:23 BXW#PR
J0010046 00000000 CAESAR
18:10:14 02/25/08
02/14/08
15:13:09 BXW#PR
J0010050 00000000 BALTHA
18:08:06 02/25/08
02/14/08
15:20:13 JEKFRUL2 FAAK7236 00000000 AVSCHM
18:08:06 02/25/08
02/14/08
15:42:17 B92ARPRI J0010096 00000000 AVSCHM
18:08:06 02/25/08
******************************** BOTTOM OF DATA ********************************
The list contains all jobs of all users that have been marked for
reloading in _beta log|z. All pending reload requests are displayed.
2. Enter S in front of a reload job and press ENTER.
The following panel comes up:
PE92RS23 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Reload Request Display
Last update: AVSCHM
Time
Time
02/26/08
Select from Date
Select to
Date
: 01/08/08
: 01/08/08
Job Name
Job ID
Job Message Class
Archive Pointer
Reload Version
: B92AGINF
: J0029531
: X
: 2008011C03D600000095060000950600
: 6
09:55:00
: 14:45:58
: 14:45:58
Press END key to return to the previous panel or Help key for help
information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
189
Monitor (Option A.M)
Displaying or processing reload requests (Option A.M.2)
The reload request with information on submit date and time, job
name, job ID, job group ID, job message class, archive pointer and
reload version is displayed.
3. Press PF3 to return to the previous panel.
4. Enter line command U in front of a reload request (for a single reload
request) or enter the primary command RELO (for all of your reload
requests) to display the "Reload Batch Submit" panel:
PE92RL25 --------------------------------------------------------------------Command ===> _________________________________________________________________
-------------------------------------I
I
I beta logz V7R2 List Reload Utility I
I
I
--------------------------------------
Job Statement Information
===> //jobname JOB acct,name,CLASS=A,MSGCLASS=P
===> //*
===> //*
===> //*
Press ENTER key to Submit job.
Press END key to return to previous menu or HELP key for help information.
5. Check the JCL of the job, and submit it to process all pending reload
requests.
Line commands
Primary commands
Note on autoreload
S
Displays the reload request
D
Deletes the reload request
U
Invokes the batch reload of all requests for this job
RELOAD
RELO
Invokes the batch reload to process all reload requests of
all users
REFRESH
REF
Updates the "Reload Request Selection Table"
If autoreload is enabled, the line command U and the primary command
RELO are no longer needed, and they are therefore not displayed in the
corresponding _beta log|z panels by default. If you want to display them
anyway, see the description of the LST parameter B92_RLD_URGENT in
"LST parameters in B92LSTxx" in _beta log|z Installation and System
Guide. For information on using automatic reload, see "Using automatic
reload" on page 257.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
190
Monitor (Option A.M)
Displaying _beta log|z statistics (Option A.M.3)
Displaying _beta log|z statistics (Option A.M.3)
Overview
Option A.M.3 enables you to display statistics on the origin (host) of jobs
and lists that have been read into _beta log|z.
Statistics cleanup
Statistical data is cleaned up together with agent rule status information by
the B92CLARS batch utility, which has to run on a regular basis.
For more information on this utility and recommended frequency, see
"B92CLARS: Cleanup for agent rule status and statistics" on page 429.
Display beta logz
Statistics panel
PE92ST00 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Display beta logz Statistics
Start Date (MM/DD/YYYY) ===> ..........
End
Date (MM/DD/YYYY) ===> __________
Display only totals
or Time Period
===> Y
===> _
(Y)es, (N)o
per (H)our, (D)ay, (M)onth
Long Hostname
===> ____________________________________________
Press ENTER key to display the Statistics Table.
Press END key to return to the previous menu.
Procedure
In the "Display beta logz Statistics" panel, specify the start date and the
end date of the time period you require.
•
To display only total statistical values per host for the specified time
period, leave default Y in the Display only totals field.
In each of the ensuing panels you will be able to successively break
these statistics down into values per month, day and hour by means of
line command S.
•
To display totals for the specified unit of time per host, type N in
Display only totals field and specify a unit of time ((H)our, (D)ay,
(M)onth) in the Time Period field.
•
To display values for a specific host only, specify a fully qualified host
name or a mask in the Long Hostname field.
In the displayed table, scroll to the right (PF11) to display the number of
megabytes that have been transferred to _beta log|z by each system
during the specified period of time.
Usage based pricing
Please note that every job and every list read into _beta log|z is counted
separately for UBP (usage based pricing). In particular, this applies to all of
the output read into _beta log|z from the EJM agents.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
191
Archive (Option A.A)
In this chapter
Archive (Option A.A)
In this chapter
Topic
Page
Archiving concept ................................................................................... 193
Working with generation archive (GAR) databases ............................... 195
Determining archive retention period and medium................................. 197
Working with archive pools and archive datasets .................................. 199
The archive run ....................................................................................... 203
Archive definition .................................................................................... 205
Defining archive pools (Option A.A.1) ................................................ 206
Displaying archive datasets (Option A.A.2) ........................................ 212
Archive volume records (Option A.A.3) .............................................. 215
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
192
Archive (Option A.A)
Archiving concept
Archiving concept
Overview
Archive retention periods of jobs are calculated at the run of the archive
batch utility B92ARPRI.
B92ARPRI is included in the B92DAILY job (see "B92ARPRI: List
archiving" on page 400 and "B92DAILY: Daily job" on page 442).
What affects archive
processing
Line commands affecting
archiving process
All of the following affects archive processing:
•
Job Group Definitions
(Job Group Retention Periods and dedicated pools)
See "Job group (Option A.1.2)" on page 103 and "Defining archive
pools (Option A.A.1)" on page 206.
•
Reader Class Definitions
(Class Processing Active/Job Group)
See "Class (Option A.R.1)" on page 260.
•
Global Options
(Jobs with JCL Init Errors, Use best matching Job Groups, Default
Archive Media)
See "Global options (Option A.S.3)" on page 230.
•
OMS control cards
(OMS SAVE and OMS NOSAVE)
See "OMS control cards" on page 47.
•
Line commands in the Job Select Table
(Toggle keep/nokeep status, Toggle re-archiving)
See "Selecting jobs (Option 1)" in _beta log|z User Guide.
The line commands X and K can be used to change the status of the lists
of a job (keep/nokeep):
•
Enter the line command in front of the job in the "Job Select Table" if
you want to change the status of all lists of this job.
•
Enter the line command in front of the list in the "Job Information
Table" if you want to change the status of an individual list.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
193
Archive (Option A.A)
Archiving concept
Flowchart:
Archive hierarchy
S e le cte d lis t is
a rc h i v e d
J o b G ro u p
A rc h i v e R e t e n t i o n
P e ri o d = 0 d a y s
J o b i n fo a n d l i s t s a re
n o t a rc h i v e d
M a rk e d fo r
D e l e t i o n (D )
J o b i n fo a n d l i s t s a re
n o t a rc h i v e d
R e a rc h i v i n g
(A )
N O K E E P (X )
fo r a p a rt i c u l a r l i s t
(J L R )
S e le cte d lis t is
a rc h i v e d
K E E P (K )
fo r a p a rt i c u l a r l i s t
(J L R )
N O K E E P (X )
fo r a l l l i s t s
(J B R a n d J L R )
J o b i n fo a n d l i s t s a re
a rc h i v e d
J o b i n fo a n d l i s t s a re
n o t a rc h i v e d
OMS
SAVE
NOSAVE
C LA S S
J o b i n fo a n d l i s t s a re
a rc h i v e d
J o b i n fo a n d l i s t s a re
n o t a rc h i v e d
K E E P (K )
fo r a l l l i s t s
(J B R a n d J L R )
OMS
NOSAVE
J o b i n fo a n d l i s t s a re
a rc h i v e d
S e le cte d lis t is
n o t a rc h i v e d
J o b i n fo a n d l i s t s a re
n o t a rc h i v e d
SAVE
C LA S S
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
194
Archive (Option A.A)
Working with generation archive (GAR) databases
Working with generation archive (GAR) databases
Overview
When B92ARPRI archives a job, it writes one GAR record in the current
generation archive database. This record contains a pointer to the job in
the archive dataset and a subset of the information from the job record.
This information remains available until the job is deleted from the archive.
_beta log|z stores GAR records in generation databases for better
handling of large amounts of data. This storage concept also enables
_beta log|z to ensure acceptable search times.
The GAR records in generation archive databases are searched and
displayed when you use option 2 and option A.S.4.n.
Yearly generations
recommended
We recommend that you work with yearly generations. This means that
each generation archive database holds the GAR records of one year.
At the end of each year, create a new GAR database generation for the
coming year. Instead of allocating a new GAR, you can also reuse an old
GAR that has become empty.
Generation Index
Definition Table
You can use option A.S.1 to display the generation archive databases that
are connected to your _beta log|z system.
The following "Generation Index Definition Table" shows a set of
databases where the GAR databases with the generation ID 01 and 02
have been reused for newer data. The current generation archive
database has the generation ID 02.
PE92DF50 -------------------------------------------------------- Row 1 of 12
Command ===> ________________________________________________ Scroll ===> PAGE
Generation Index Definition Table
S - Select Gen ID Definition
I - Insert Gen ID Definition
C - Copy Gen ID Definition
D - Delete Gen ID Definition
Sel Gen-ID Gen-Last-Date First-Job-Date Last-Job-Date Comment
>
01
2019-12-31
2019-01-01
2019-12-31
UNTIL 31.12.2019
02
2020-12-31
2020-01-01
2020-02-19
UNTIL 31.12.2020
03
2009-12-31
2009-01-01
2009-12-31
UNTIL 31.12.2009
04
2010-12-31
2010-01-01
2010-12-31
UNTIL 31.12.2010
05
2011-12-31
2011-01-01
2011-12-31
UNTIL 31.12.2011
06
2012-12-28
2012-01-01
2012-12-29
UNTIL 31.12.2012
07
2013-12-31
2013-12-29
2013-12-31
UNTIL 31.12.2013
08
2014-12-31
2014-01-01
2014-12-31
UNTIL 31.12.2014
09
2015-12-31
2015-01-01
2015-12-31
UNTIL 31.12.2015
10
2016-12-31
2016-01-01
2016-12-31
UNTIL 31.12.2016
11
2017-12-31
2017-01-01
2017-02-19
UNTIL 31.12.2017
12
2018-12-31
2018-01-01
2018-12-31
UNTIL 31.12.2018
******************************** BOTTOM OF DATA ********************************
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
195
Archive (Option A.A)
Working with generation archive (GAR) databases
Some administrators may prefer to continue the sequential numbering of
GAR IDs, so that the newest data is always in the GAR database with the
highest ID. The following "Generation Index Definition Table" shows such
a set of databases, where obsolete GAR databases have been removed
after they have become empty.
PE92DF50 -------------------------------------------------------- Row 1 of 12
Command ===> ________________________________________________ Scroll ===> PAGE
Generation Index Definition Table
S - Select Gen ID Definition
I - Insert Gen ID Definition
C - Copy Gen ID Definition
D - Delete Gen ID Definition
Sel Gen-ID Gen-Last-Date First-Job-Date Last-Job-Date Comment
>
16
2009-12-31
2009-01-01
2009-12-31
UNTIL 31.12.2009
17
2010-12-31
2010-01-01
2010-12-31
UNTIL 31.12.2010
18
2011-12-31
2011-01-01
2011-12-31
UNTIL 31.12.2011
19
2012-12-28
2012-01-01
2012-12-29
UNTIL 31.12.2012
20
2013-12-31
2013-12-29
2013-12-31
UNTIL 31.12.2013
21
2014-12-31
2014-01-01
2014-12-31
UNTIL 31.12.2014
22
2015-12-31
2015-01-01
2015-12-31
UNTIL 31.12.2015
23
2016-12-31
2016-01-01
2016-12-31
UNTIL 31.12.2016
24
2017-12-31
2017-01-01
2017-02-19
UNTIL 31.12.2017
25
2018-12-31
2018-01-01
2018-12-31
UNTIL 31.12.2018
26
2019-12-31
2019-01-01
2019-12-31
UNTIL 31.12.2019
27
2020-12-31
2020-01-01
2020-02-19
UNTIL 31.12.2020
******************************** BOTTOM OF DATA ********************************
Further information
_beta log|z online application includes functions for the following:
•
"Adding a new GAR database (Option A.3.3)" on page 180
•
"Deleting or reusing an empty GAR database (Option A.3.2)" on
page 177
Keep adding new GAR databases if you don't want to reuse. Optionally,
you can remove obsolete GAR databases after they have become empty.
This section describes how to do this:
•
"Removing an empty GAR database"
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
196
Archive (Option A.A)
Determining archive retention period and medium
Determining archive retention period and medium
Overview
A job group definition specifies which archive retention period and which
archive medium is to be used for jobs of this group. Each job is assigned
to a job group using either the best-match principle or the longest retention
principle (see "Best match or longest retention" on page 119).
Define archive pools whose retention period and archive media
correspond to the specifications of the job groups. Job groups with like
retention periods and like archive media are archived together, using the
archive pools for grouping.
Example
Each job group is assigned to the archive pool whose definition specifies
the same archive medium and the same archive retention period. In the
following example, there are five job groups and three archive pool
definitions.
Assigning job groups to
archive pools (part 1)
Job group
defining ...
is assigned to ...
defining ...
GRP01
10 Days on Disk
POOL_A
30 Days on Disk
GRP02
30 Days on Disk
POOL_A
30 Days on Disk
GRP03
31 Days on Disk
POOL_B
90 Days on Disk
GRP04
90 Days on Disk
POOL_B
90 Days on Disk
GRP05
365 Days on Tape POOL_C
365 Days on Tape
If there is no archive pool with the same archive retention period, the job
group is assigned to the archive pool with the next higher archive retention
period and the same archive medium.
Assigning job groups to
archive pools (part 2)
Job group
defining ...
is assigned to ...
defining ...
GRP01
30 Days on Disk
POOL_A
30 Days on Disk
GRP02
30 Days on Tape
POOL_C
365 Days on Tape
GRP03
90 Days on Disk
POOL_B
90 Days on Disk
GRP04
90 Days on Tape
POOL_C
365 Days on Tape
GRP05
365 Days on Tape POOL_C
365 Days on Tape
If there is no archive pool with the same archive medium and a higher
retention period, the corresponding lists will remain on the spool with
status Pend. The batch utility prints a list of all lists that could not be
archived.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
197
Archive (Option A.A)
Note on job groups
Determining archive retention period and medium
The job group displayed in the Jobgroup column of the Job Select table is
not necessarily the job group that is used for archiving.
•
For the jobs that are assigned to job groups via the message class
(reader class has Class Processing Active = Yes (option A.R.1)), the
following applies:
If option A.S.3 has Show class processing = Yes, the Job Select
table displays the job group that is also used for archiving.
If option A.S.3 has Show class processing = No, the job group from
the reader class definition is used for archiving, but the Job Select
table displays the best-matching job group (job mask).
•
For the jobs of all other classes, the following applies:
If option A.S.3 has Use best matching job group = Yes, the Job
Select table displays the job group that is also used for archiving.
If option A.S.3 has Use best matching job group = No, the matching
job group with the longest retention is used for archiving, but the Job
Select table displays the best-matching job group (job mask).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
198
Archive (Option A.A)
Working with archive pools and archive datasets
Working with archive pools and archive datasets
Overview
_beta log|z uses archive pools to facilitate archive media management and
to save archive space.
Archive pools are defined under option A.A.
Archive retention period
The archive retention period determines how long job logs, sysout lists,
and job records will remain available. Define different archive media and/or
different archive retention periods for each archive pool according to your
needs.
Archive media
Job logs, sysout lists, and job records can be archived to disk, tape, or
optical disk.
The job group definition specifies the archive retention period and the
archive medium. Jobs belonging to this job group are assigned to the
archive pool that has the same archive medium and the same or the next
higher retention period.
Archiving on tape
When archiving on tape, separate volumes are used for each pool. This
means that when several archive datasets are written onto the same tape,
the retention periods of the datasets are about the same.
Note on copying and moving tape archive datasets
Always use a utility that copies block by block to copy _beta log|z archive
datasets, for example, ICEGENER. Do not use a utility that copies record
by record, for example, IEBGENER.
Updating the volume and label information in the archive dataset record
(table ADR) is optional when _beta log|z locates archive datasets via the
system catalog (default).
B92ARPRI
Batch utility B92ARPRI archives lists and associated job information in
archive datasets. B92ARPRI assigns jobs on the basis of the job group
definition to an archive pool that has the same archive medium and the
same or a higher archive retention period.
The archive utility B92ARPRI checks each list on the online spool and
archives all lists that are marked for archiving (Arch = Pend). The utility
skips lists that have already been archived (Arch = Yes) and lists that are
not to be archived (Arch = No).
If a list cannot be assigned to any archive pool, it will remain on the online
spool with status Pend. The archive batch utility B92ARPRI prints a list of
all jobs that could not be assigned to any pool. To archive these lists at the
next run of the archive utility, you must first modify the job group or archive
pool definitions.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
199
Archive (Option A.A)
Archive status to
Pend or No
Working with archive pools and archive datasets
There are several ways of setting the archive status of lists to Pend (must
be archived) or No (need not be archived):
•
Class definitions
You can define an entire Sysout class as SAVE class (lists will be
archived) or NOSAVE class (lists will not be archived). Lists assigned
to a SAVE class get archive status Pend when read into _beta log|z,
lists assigned to a NOSAVE class get archive status No. For more
information, see "Class (Option A.R.1)" on page 260.
•
Job group definitions
Define how many days jobs and lists assigned to this job group should
remain in the archive. Lists assigned to this job group get archive
status 'Pend' when read into _beta log|z. Define an archive retention
period of 0 (zero) days if the jobs and lists assigned to this job group
should not be archived.
•
OMS control cards
Use the control card //*OMS SAVE in the JCL if you want to archive
jobs that otherwise would not be archived. Use the control card //*OMS
NOSAVE in the JCL if you do not want to archive jobs that otherwise
would be archived.
When are lists archived?
Jobs that need to be archived get status Arch=Pend when read into _beta
log|z. Lists and associated job information of these jobs are archived at the
next run of the archive utility B92ARPRI, which is part of the B92DAILY
job.
Reloading from the
archive
_beta log|z requires the job base record for reloading. For example, when
reloading lists and other job information of a job that ran on 13 August
2017, _beta log|z proceeds as follows:
If the job base records of 13 August 2017 are still available online:
_beta log|z finds the job base record in the online database. This record
contains the pointer to the primary archive dataset that was used for this
job. Lists and associated job information are reloaded from this archive
dataset.
Archive datasets
For each archive dataset that is written to disk, tape, or optical disk, _beta
log|z creates a dataset record. The dataset record contains information
about the creation date, expiration date, and the status of the dataset.
You can display a list of archive datasets under option A.A.2.
Each archive run can write one or several datasets onto the archive
medium.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
200
Archive (Option A.A)
Archive dataset names
Working with archive pools and archive datasets
The name of an archive dataset consists of:
•
The prefix, which is specified in the archive pool definition (DSName
Prefix)
•
The qualifier Eyyddd, whereby yyddd is the date in Julian format, for
example, E17045 for February 14, 2017. (Note: datasets written
before 1/1/2000 have the qualifier Dyyddd.)
•
The second qualifier is Nnnn where nnn is a three-digit number. The
first archive dataset written on a given date gets the number 999, the
second archive dataset gets the number 998, etc.; for each new
archive dataset written on the same day, the number is decreased by
1. On the next day, the numbering of the datasets starts again with
999.
Example
If the prefix defined in the archive pool is B92.ARCH, the first archive
dataset created on February 14, 2017 is called B92.ARCH.E17045.N999,
the second B92.ARCH.E17045.N998, the third B92.ARCH.E17045.N997,
and so on.
The number of datasets created on one day depends on the number of
times you run the archive utility and the maximum number of jobs that are
archived in one dataset.
Dual archiving
_beta log|z supports dual archiving to safeguard against data loss due to
media failure. To use dual archiving, define the archive pool as dual
archive pool.
With this function, archiving will take place on two separate archive media.
You can choose any combination of archive media for dual archiving, for
example disk and tape, disk and optical disk, or tape and tape.
You can define different archive retention periods for the first and the
second archive medium. For example, you can define "30 days on disk" for
one archive and "3 years on tape" for the other archive.
The longest retention period determines the archive medium.
Example
You have defined a dual archive pool POOL01 (Archive Mode = Dual).
The primary copy of the archive uses the archive medium tape and has a
retention period of 1096 days. The secondary copy of the archive uses
archive medium disk and has a retention period of 30 days.
All jobs of job groups that have the archive medium tape and a retention
period of 1096 days will be assigned to the archive pool POOL01. They
will be archived to disk (where they will expire after 30 days) and to tape
(where they will expire after three years).
To ensure that reloading jobs will access the medium disk during the first
30 days after archiving, define Reload from=Secondary in the archive
pool. After the archive dataset on disk has expired, lists will automatically
be reloaded from the primary copy of the archive on tape.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
201
Archive (Option A.A)
Special archive pools
Working with archive pools and archive datasets
Archive pool SPECIAL is used for archiving corrupted lists. You must
define this pool before running batch utility B92ARPRI in cleanup mode
(parameter TYPE=CLEANUP).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
202
Archive (Option A.A)
The archive run
The archive run
Overview
The archive job B92ARPRI checks the archive status of all jobs and lists.
All lists that need to be archived are sorted according to archive medium
and archive retention period, assigned to the respective archive pools, and
then archived together with the corresponding job records.
Allocating archive
datasets
B92ARPRI allocates the archive datasets on (optical) disk or tape,
according to the defined archive medium.
Archive volumes are dynamically allocated by B92ARPRI. You need at
least one disk, tape, or FileTek unit during the archive run. If you use dual
archive mode, you need two units.
When creating archive datasets, B92ARPRI uses the unit and volume
definitions of the archive pool. The name of an archive dataset consists of
the prefix defined in the archive pool plus the two additional qualifiers
Eyynnn.Nnnn (see "Archive dataset names" on page 201).
Archiving to tape
When archiving to tape, a request for one archive volume is issued for
every archive pool. The program writes an archive dataset onto the tape.
The expiration date of the dataset is based on the retention period of the
archive pool starting from the time of the archive run.
By default, each tape is used for several archive runs until it is full. You
can also make B92ARPRI use a new tape for every archive run (New tape
each archive run field in archive pool definition).
Only archive datasets of the same archive pool will be written onto one
volume. When new archive datasets are added to active tapes, the
expiration date of the volume will be automatically updated. When tapes
run full in the middle of an archive run, B92ARPRI requests a new tape
and continues.
Limiting the size of the archive dataset
Reloading will be faster if archive datasets on tape are not too big. We
therefore recommend that you limit the size of archive datasets on tape via
the LST parameter B92_JOBLIMIT_ARCDS. This parameter defines the
maximum number of jobs that should be archived in one archive dataset.
By default, B92ARPRI creates one archive dataset for each archive pool
(without job limit).
Actual archive retention
period
The archive retention period is relative to the day of the archive run.
The archive retention period is determined by the archive pool.
Note: The archive retention period of the archive pool may be higher than
the archive retention period of the job group.
Example: The job group defines an archive retention period of 30 days,
but the best matching archive pool defines a retention period of 40 days.
This means that the actual archive retention period is 40 days.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
203
Archive (Option A.A)
Deleting information
The archive run
The archive job B92ARPRI archives list and job data on archive volumes,
but it does not delete any data. Data is deleted by the following batch
utilities:
•
B92CLLST deletes lists from the online spool when their online
retention period has expired.
•
B92ARSEC deletes job information records and job base records from
the JOB database when their online retention period has expired.
•
B92CLARC deletes archive information from the database when their
archive retention period has expired.
These batch utilities are all included in the B92DAILY job.
Expiration date and catalog entries
Archive datasets are expired automatically when the expiration date of the
dataset or the volume has been reached. The z/OS catalog entries are
either deleted by your tape management system or with the IDCAMS
utility. The catalog entries can be viewed under ISPF option 3.2.
Re-archiving lists
You can re-archive lists that have already been archived before. The
archive run can be repeated as long as the list is displayed in the "Job
Information Table".
The entry Arch=Yes marks lists that have been previously archived. To rearchive such a list, enter the line command A in the "Job Information
Table" (see the _beta log|z User Guide for more information).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
204
Archive (Option A.A)
Archive definition
Archive definition
Navigation
When you select option A.A - Archive in the "Primary Selection Menu",
the following panel is displayed:
PEB8AR00 ---------------------------------------------------------------------Option ===> __________________________________________________________________
Archive Options Selection Menu
System
- B92PROD
Location - BERLIN
Subsys-ID - B92P
User ID
- B92ADM1
1
DEFINITION
-
Display Archive Pool Definitions
2
DATA SETS
-
Display Archive Data Set Information
3
VOLUMES
-
Display Archive Volume Information
Select one of the above options. Press END to return to the previous menu.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
205
Archive (Option A.A)
Archive definition
Defining archive pools (Option A.A.1)
Selecting archive pools
1. When you select option 1 - Definition of the "Archive Options
Selection Menu", the "Archive Definition Selection" panel will be
displayed. Here you can enter selection criteria to display existing
archive pools.
PEB8AP50 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Archive Pool Selection
Archive Product
Archive Pool Name
Archive Mode
Archive Retention Period
Archive Pool Title
===> B92
B92 or *
===> *.......
Pool Name or mask
===> *_____
(S)ingle, (D)ual or *
===> _____
1-36500 or blank
===> ________________________________________
Press the ENTER key to display the archive pool definitions.
Press the END key to return to the previous menu.
2. Press ENTER to display a list of existing archive pools that match the
selection criteria. If there is no matching archive pool, the "Archive
Pool Definition" panel will be displayed.
PEB8AP05 ---------------------------------------------------- Row 1
of 3
Command ===> ________________________________________________ Scroll ===> PAGE
Display Archive Pool Definitions
S - Select Archive Pool Definition
I - Insert Archive Pool Definition
Sel Prod Pool
B92 ASDF
Mode
SINGLE
D - Delete Archive Pool Definition
V - Insert Volume for KODAK Pools
Media
TAPE
Retpd Title
00001
00000
------------------------------------------------------------------------------B92 POOL1
SINGLE DISK
00020 FIRST ARCHIVE POOL
00000
------------------------------------------------------------------------------B92 POOL99
SINGLE DISK
00010 POOL 10 TAGE
00000
------------------------------------------------------------------------------******************************** BOTTOM OF DATA ********************************
This table displays the name of the archive product (always B92), the
archive pool name, the archive medium and the archive retention
period. The Mode column shows if single or dual archiving is defined.
The Title column gives a short description of the archive pool.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
206
Archive (Option A.A)
Fields
Archive definition
Field
Description
Archive Product
Always B92 for _beta log|z archives.
Archive Pool Name
Enter a pool name or a mask (*).
Archive Mode
S to select single archive pools;
D to select dual archive pools;
* to select single and dual archive pools.
Archive Retention
Period
Specify a number to select pools with this retention
period.
Archive Pool Title
Enter a name or a mask to select pools via the title.
Line commands
Inserting an archive pool
S
Selects the archive pool for display or update
I
Inserts a new archive pool
D
Deletes the archive pool
V
This line command is for Kodak pools only, which are not
supported by _beta log|z at present.
To define a new archive pool:
1. Enter line command I in front of an archive pool in the "Archive Pool
Display" panel.
This will display the "Archive Pool Definition" panel. The "Archive Pool
Definition" panel is also displayed if no (matching) archive pool exists.
PEB8AP10 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Insert Archive Pool Definition
Archive Product
Archive Pool Name
Archive Media Name
===> B92
===> ........
===> .....
Archive Pool Owner
Archive Pool Title
===> ________
===> ________________________________________
(T)ape,(D)isk,(F)ilet,(K)odak
Press the ENTER key to insert the archive pool definition.
Press the END key to return to the previous panel.
2. Pressing ENTER will display an additional definition panel. Which
panel will be displayed depends on the archive medium. See the
description of the "Insert B92 Primary Pool Definition" panel for each
archive medium below.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
207
Archive (Option A.A)
Archive definition when
archiving on tape
Archive definition
The following panel is displayed for the archive medium TAPE:
PEB8AP30 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Insert B92 Primary Pool Definition
Archive Pool Name
Archive Media Name
Title
Last Update:
: POOL1
Owner
: TAPE
: MY POOL TITLE
:
DSName Prefix
===> ................................ (Max 32 Characters)
Primary Unit
===> ........
Retention Period ===> 00001
(1-36500 Days)
New tape each archive run ===> NO.
Compression
===> NO....
(Y)es,(N)o
(Y)es,(N)o,(I)gnore
Archive Mode
Secondary Media Name
(S)ingle,(D)ual
(T)ape,(D)isk,(F)ilet,(K)odak
===> SINGLE
===> _____
Press the ENTER key to insert the archive pool definition.
Press the END key to return to the previous panel.
Archive definition when
archiving on disk
The following panel is displayed for archive medium DISK:
PEB8AP22 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Insert B92 Primary Pool Definition
Archive Pool Name
Archive Media Name
Title
Last Update:
: POOL2
Owner
: DISK
: MY POOL TITLE
:
DSName Prefix
===> ................................ (max 32 Characters)
Data Set Size
===> .....
(0,200-65535 Tracks)
Retention Period ===> 00001
(1-36500 Days)
Extended Attrib. ===> ___
(O)pt,(N)o, or blank
SMS Managed
===> YES
(Y)es,(N)o
STORCLAS
===> ________
DATACLAS
===> ________
MGMTCLAS
===> ________
Archive Mode
Secondary Media Name
===> SINGLE
===> _____
(S)ingle,(D)ual
(T)ape,(D)isk,(F)ilet,(K)odak
Press the ENTER key to insert the archive pool definition.
Press the END key to return to the previous panel.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
208
Archive (Option A.A)
Archive definition
Archive definition when
archiving on FileTek
The following panel is displayed for archive medium FileTek:
PEB8AP90 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Insert B92 Primary Pool Definition
Archive Pool Name
Archive Media Name
Title
Last Update:
: POOL3
Owner
: FILET
: MY POOL TITLE
:
DSName Prefix
===> ................................ (max 32 Characters)
Data Set Size
===> .....
(10-65000 Mega Bytes)
Retention Period ===> 00001
(1-36500 Days)
Volume Set
Group Name
Group Pwd
===> ________
===> ________
===> ________
Archive Mode
Secondary Media Name
===> SINGLE
===> _____
File Set
===> ________
File Pwd
===> ________
(S)ingle,(D)ual
(T)ape,(D)isk,(F)ilet,(K)odak
Press the ENTER key to insert the archive pool definition.
Press the END key to return to the previous panel.
Fields
Field
Description
Archive Product
Always B92 for _beta log|z archives
Archive Pool Name
Enter a name of up to eight characters (the first character
must be alphabetic). Various archive pools can be defined
by means of the pool name. An individual retention period
can be assigned to each pool.
Note: The name SPECIAL is reserved for the archive pool
that is used for corrupted lists.
Archive Media Name Enter TAPE to archive to tape, DISK to archive to DASD,
or FILET to archive to FileTek. Depending on the specified
archive medium, different panels are called up when
pressing ENTER.
Note: The archive medium Kodak is not supported by
_beta log|z.
Archive Pool
OWNER
Invalid for _beta log|z.
Archive Pool Title
Here you can enter a title of the archive pool.
Archive Pool Name
The name of the archive pool is displayed.
Owner
Invalid for _beta log|z.
Archive Media Name The archive medium is displayed.
Title
You can enter a descriptive title (max. 40 characters) in this
field (optional).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
209
Archive (Option A.A)
Archive definition
Field
Description
DSName Prefix
Enter a prefix of up to 32 characters used for building the
dataset name. Ensure that the name matches the valid
conventions. The two qualifiers Eyyddd (date) and Nnnn
(number) are added automatically to this prefix by the
program (see "Archive dataset names" on page 201).
Primary Unit
The unit is entered in this field. Make sure that the name
corresponds to valid conventions.
RETPD
Assign the retention period to this archive pool. The archive
retention period indicates the number of days for which the
data are to be stored on the archive datasets. A retention
period of 1 up to 36500 days is possible.
New tape each
archive run
If you enter Yes here, a new tape will be requested for
each archive run.
Compression
With this field you can determine whether or not IDRC
features are used. If you enter Yes, the archiver will use
IDRC capability of tape drives. If you enter No, the archiver
will not use the IDRC capabilities of tape drives. If you enter
Ignore, the data recording mode is determined by your
z/OS tape definitions.
Dataset Size
Specify the size in tracks of the dataset which is to be
defined.
To specify an appropriate value needs some experience.
When you are using the disk archiving option for the first
time, be sure to designate plenty of space for the dataset. If
no further archive lists are written into this dataset, the
remaining space is freed automatically. Under ISPF you
can learn about the number of tracks which are actually
needed. Use the appropriate value for future definitions.
When disk archive datasets are SMS managed, specify 0
(zero) in this field to use the space allocations of the
corresponding SMS DATACLAS.
SMS Managed
Entering No will display the following fields:
Vol1-Vol6
Enter the name of the disk on which to archive.
Unit1-Unit6
Enter the unit on which to archive.
Entering Yes will display the fields STORCLAS,
DATACLAS, and MGMTCLAS instead.
It is possible to specify a data class, storage class and/or
management class. Although you are using SMS, input
through these fields is not forced (site dependent). Please
contact your storage administrator for class names valid at
your site.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
210
Archive (Option A.A)
Archive definition
Field
Description
Volume-Set
Please see the Callable Interface Programmer's Guide,
Release 1.7 of the SM Host Software.
File-Set/
Group-Name/
Group-Pw/File-Pw
Please see the Callable Interface Programmer's Guide,
Release 1.7 of the SM Host Software.
Archive Mode
Choose between single and dual archiving.
Secondary Media
Name
If you choose dual archive mode, define the medium that is
to be used for the secondary copy of the archive.
Depending on the archive medium, an additional definition
panel will be displayed. For information on these panels,
refer to the corresponding panel used for defining the
primary copy of the archive, where you can find
descriptions for all fields except the following: Reload from.
By default, _beta log|z reloads archived lists and records
from the primary copy of the archive. Enter Secondary to
reload lists and records from the secondary copy of the
archive instead.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
211
Archive (Option A.A)
Archive definition
Displaying archive datasets (Option A.A.2)
Overview
Dataset records are generated automatically during each _beta log|z
archive run. One record is created for each dataset that is written to the
archive volume. These records contain information about the creation
date, expiration date, and archive retention period. All of the information is
taken from the archive pool definitions.
Navigation
From the "Primary Selection Menu" choose:
•
Option A.A.2
The "Archive Dataset Selection" panel is displayed.
Archive Dataset
Selection
This panel enables you to enter the selection criteria for a particular
dataset. Information on the dataset records matching these criteria is
displayed.
PEB8AD50 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Archive Data Set Selection
Archive Product
Archive Pool Name
Archive Media
===> B92
===> *.......
===> TAPE_
Archive Retention Period
Archive Creation Date
===> _____
===> __________
B92 or *
Pool Name or mask
(T)APE, (D)ISK, (F)ILET,
(K)ODAK or blank
1-36500 Days or blank
MM/DD/YY
Press the ENTER key to display the archive data sets.
Press the END key to return to the previous menu.
Fields
Field
Description
Archive Product
Always B92 for _beta log|z archives.
Archive Pool Name
Enter the name of an archive pool or a mask ( * ).
Archive Media
Enter TAPE to select datasets on tape, DISK to
select the disk archive, and FILET to select the
optical disk archive.
Archive Retention Period
Here you can enter an archive retention period.
Archive Creation Date
Enter a creation date if you wish to display only
datasets that have been archived on or after a
certain date.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
212
Archive (Option A.A)
Archive definition
Display Archive Datasets
The "Display Archive Datasets" table shows all dataset records that match
your selection criteria. You can scroll to the right to display more
information.
PEB8AD05 ------------------------------------------------- Row 1
of 2878
Command ===> ________________________________________________ Scroll ===> PAGE
Display Archive Data Sets
S - Select Data Set Information
Sel Pool
POOL7
POOL7
POOL7
POOL7
POOL7
POOL7
POOL7
POOL7
POOL7
POOL7
POOL7
POOL7
POOL7
POOL7
POOL7
POOL7
Columns
Archive dataset
information
Page 1 of 3
( LEFT/RIGHT )
Media Crea. Date Data Set Name
TAPE 08/08/11
BETA92P.ARCHIVE.POOL7.E11220.N998
TAPE 08/09/11
BETA92P.ARCHIVE.POOL7.E11221.N998
TAPE 08/10/11
BETA92P.ARCHIVE.POOL7.E11222.N997
TAPE 08/10/11
BETA92P.ARCHIVE.POOL7.E11222.N998
TAPE 08/11/11
BETA92P.ARCHIVE.POOL7.E11223.N998
TAPE 08/12/11
BETA92P.ARCHIVE.POOL7.E11224.N998
TAPE 08/15/11
BETA92P.ARCHIVE.POOL7.E11227.N998
TAPE 08/16/11
BETA92P.ARCHIVE.POOL7.E11228.N998
TAPE 08/17/11
BETA92P.ARCHIVE.POOL7.E11229.N998
TAPE 08/18/11
BETA92P.ARCHIVE.POOL7.E11230.N997
TAPE 08/19/11
BETA92P.ARCHIVE.POOL7.E11231.N998
TAPE 08/22/11
BETA92P.ARCHIVE.POOL7.E11234.N995
TAPE 08/22/11
BETA92P.ARCHIVE.POOL7.E11234.N998
TAPE 08/23/11
BETA92P.ARCHIVE.POOL7.E11235.N998
TAPE 08/24/11
BETA92P.ARCHIVE.POOL7.E11236.N997
TAPE 08/24/11
BETA92P.ARCHIVE.POOL7.E11236.N998
Table column
Description
Pool
Name of the archive pool the dataset is archived on
Media
Archive medium the dataset is archived on
Crea. Date
Creation date of the archive dataset
Dataset Name
Full name of the archive dataset
Select a dataset record with line command S to display detailed
information on an archive dataset in the "Archive Dataset Information"
panel:
PEB8AD20 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Archive Data Set Information
Data Set Name
Archive Medium
Archive Pool
Product
: BETA92P.ARCHIVE.POOL7.E11220.N998
: TAPE
: LONG
: B92
Retention Period
Creation Date
Expiration Date
: 0730
: 08/08/11
: 08/07/13
First Volser
Second Volser
Third Volser
: H00599
:
:
Identifier
Status
: 2011220C03E60000
===> GOOD..
Press the END key to return to the previous panel.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
213
Archive (Option A.A)
Fields
Archive definition
Field
Description
Dataset Name
Name of the dataset (see "Archive dataset names" on
page 201).
Archive Medium
Archive medium on which the archive dataset is written
Archive Pool
Name of the archive pool
Product
Indicates the Beta product (always B92 for _beta log|z
archives)
Retention Period
Archive retention period of the archive dataset (inherited
from the archive pool definition)
Creation Date
Creation date of the dataset
Expiration Date
Expiration date of the dataset
First/Second/Third
Volser
These fields show the volume serial numbers of the
archive medium.
Identifier
Timestamp (for internal use)
The timestamp is created when a dataset is allocated
and active.
Status
The dataset status GOOD means the dataset can be
used in future. If BAD is indicated here, the dataset
cannot be used again. A dataset is set into the status
BAD when an error occurred during read.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
214
Archive (Option A.A)
Archive definition
Archive volume records (Option A.A.3)
Overview
An archive volume record contains information on the current volume of an
archive pool (medium tape). You can display these records to obtain
information on the number of files in the archive unit and to see the status
of the tape.
Navigation
From the "Primary Selection Menu" choose:
•
Option A.A.3
The "Select Archive Volumes for Media Tape" panel is displayed.
Select Archive Volumes
for Media Tape
This panel displays information on the current archive volume; this option
is available only if the archive medium is TAPE.
PEB8AV00 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Select Archive Volumes for Media Tape
Archive Product
Archive Pool Name
Volume Use
===> B92
===> *.......
===> _________
B92 or *
Pool Name or mask
(P)rimary or (S)econdary
Press the ENTER key to display the archive volume definitions.
Press the END key to return to the previous menu.
Fields
Field
Description
Archive Product
Always B92 for _beta log|z archives
Archive Pool Name
Enter the name of an archive pool or a mask.
Volume Use
Enter P to select primary copies of archives, S to select
secondary copies of archives (for dual archive mode,
only).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
215
Archive (Option A.A)
Archive definition
Archive Volume
Selection table
PEB8AV05 ---------------------------------------------------- Row 1
of 4
Command ===> ________________________________________________ Scroll ===> PAGE
Archive Volume Selection
S - Select Archive Volume
Sel Pool
Volume Unit
Status Use as Prod
POOL3
H00019 ROBO
GOOD
PRIM
B92
POOL5
H00663 ROBO
GOOD
PRIM
B92
POOL7
H01016 ROBO
GOOD
PRIM
B92
SPECIAL H00412 ROBO
GOOD
PRIM
B92
******************************** BOTTOM OF DATA ********************************
Columns
Column
Description
Pool
Displays the pool name.
Volume
Displays the volume.
Unit
Displays the name of the unit that is used for archiving.
Status
The status GOOD means the volume can be used in
future. If BAD is indicated here, the volume cannot be
used again.
Use
Displays whether the volume is used for the primary
archive or the secondary archive.
Prod
Always B92 for _beta log|z archives
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
216
Archive (Option A.A)
Archive definition
Select a volume with the line command S to display the "Archive Volume
Record Display" panel.
Volume information
PEB8AV20 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Volume Record for Media Tape
Last Update:
Archive Pool
Name
Data Set Name Prefix
: POOL7
: BETA92P.ARCHIVE.POOL7
Volume Serial
Unit Type
File(s) on Tape
: H00019
: ROBO
: 00008
Volume Status
Use as
Volume full
: GOOD
: PRIM
===> NO..
(Y)es, (N)o
Press the ENTER key to update the archive volume record.
Press the END key to return to the previous panel.
Fields
Field
Description
Archive Pool Name
The archive pool name is displayed here.
Dataset Name Prefix
This is the name of the dataset for which you specified a
prefix in the archive pool definition.
Volume Serial
The volume serial number of the archive medium is
displayed.
Unit Type
The name of the unit used for archiving is displayed, for
example, TAPE.
File(s) on Tape
The number of files on the volume are displayed.
Volume Status
The status GOOD means the volume can be used in
future. If BAD is indicated here, the volume cannot be
used again. A dataset is set into status BAD when an
error occurred during read.
Use as
Displays whether the volume is used for the primary
archive or the secondary archive.
Volume full
Enter YES when the volume is not to be used any
longer.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
217
System (Option A.S)
In this chapter
System (Option A.S)
In this chapter
Topic
Page
System Options Selection Menu ............................................................ 219
Generation (Option A.S.1) ...................................................................... 220
Subsystems (Option A.S.2) .................................................................... 223
Global options (Option A.S.3) ................................................................. 230
Special reload (Option A.S.4) ................................................................. 236
Reload by generation (Option A.S.4.1)............................................... 237
Sorting the Archived Job Select Table ............................................... 241
Processing reload requests ................................................................ 242
B92RLOAD Reload V2 (Option A.S.4.2) ............................................ 245
Reloading lists or job information using B92RLOAD Reload V2 ........ 247
B92RLOAD Reload V3 (Option A.S.4.3) ............................................ 249
Selecting a reload request .................................................................. 251
Defining a reload request.................................................................... 253
Processing one or all reload requests ................................................ 255
B92RLOAD V3 report ......................................................................... 256
Using automatic reload ....................................................................... 257
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
218
System (Option A.S)
System Options Selection Menu
System Options Selection Menu
Overview
Use the "System Options Selection Menu" to change or display _beta log|z
system options.
Navigation
From the "Primary Selection Menu", choose:
•
System Options
Selection Menu
Option A.S
PE92SO00 ---------------------------------------------------------------------Option ===> __________________________________________________________________
System Options Selection Menu
1
GENERATION
-
System
- B92PROD
Location - BERLIN
Subsys-ID - B92P
User ID
- AVSCHM
Display or Update Generation Index Definitions
2
SUBSYSTEM
-
Display or Update Subsystem Options
3
GLOBAL
-
Display or Update Global Options
4
SPECIAL RELOAD
-
Display Special Reload Selection Menu
Select one of the above options, or press END key to return to the previous
menu. Press the HELP key from any panel for help information.
Options
Option
Description
1 GENERATION
Display or update of generation index definitions
(see "Generation (Option A.S.1)" on page 220).
2 SUBSYSTEM
Display or update of subsystem options (see
"Subsystems (Option A.S.2)" on page 223).
3 GLOBAL
Display or update of global options (see "Global
options (Option A.S.3)" on page 230).
4 SPECIAL RELOAD
Display the special reload menu (see "Special
reload (Option A.S.4)" on page 236).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
219
System (Option A.S)
Generation (Option A.S.1)
Generation (Option A.S.1)
Overview
Generation archive (GAR) databases contain information about archived
jobs. Each generation of this database is meant to hold the archived job
records of one year (see "Working with generation archive (GAR)
databases" on page 195).
At the end of each year, create a new GAR database generation for the
coming year. Use option A.3.3 when adding a new GAR database (see
"Adding a new GAR database (Option A.3.3)" on page 180).
Option A.S.1 can be used to show the GAR databases that are connected
to your _beta log|z system.
Note on reloading
The records in the GAR databases are searched and displayed under
option 2 and option A.S.4.n.
In the _beta log|z global options (Option A.S.3), you can specify how many
GAR databases are to be searched when jobs are selected for reloading.
Via option A.S.4.1, it is also possible to select jobs for reloading from
earlier GAR databases.
Navigation
From the "Primary Selection Menu", choose:
•
Option A.S.1
The "Generation Index Definition Selection" panel is displayed, in
which you can enter your selection criteria.
Enter a generation ID, or an asterisk * to display all generations.
Generation Index
Definition Table
PE92DF50 -------------------------------------------------------- Row 15 of 25
Command ===> _______________________________________________ Scroll ===> PAGE
Generation Index Definition Table
S - Select Gen ID Definition
I - Insert Gen ID Definition
C - Copy Gen ID Definition
D - Delete Gen ID Definition
Sel Gen-ID Gen-Last-Date First-Job-Date Last-Job-Date Comment
>
16
31.12.2009
01.01.2009
31.12.2009
GAR FOR 2009
17
31.12.2010
01.01.2010
31.12.2010
GAR FOR 2010
18
31.12.2011
01.01.2011
31.12.2011
GAR FOR 2011
19
31.12.2012
01.01.2012
31.12.2012
GAR FOR 2012
20
31.12.2013
01.01.2013
31.12.2013
GAR FOR 2013
21
31.12.2014
01.01.2014
31.12.2014
GAR FOR 2014
22
31.12.2015
01.01.2015
29.12.2015
GAR FOR 2015
23
31.12.2016
01.01.2016
31.12.2016
GAR FOR 2016
24
31.12.2017
01.01.2017
31.12.2017
GAR FOR 2017
25
31.12.2018
01.01.2018
17.03.2018
GAR FOR 2018
******************************** BOTTOM OF DATA ********************************
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
220
System (Option A.S)
Line commands
Generation (Option A.S.1)
The following line commands are available in the "Generation Index
Definition Table":
S
Selects a generation index definition.
I
Inserts a generation index definition.
Note: A new generation index definition is inserted automatically
for the new GAR database when you add a new GAR under option
A.3.3.
C
Copies a generation index definition.
D
Deletes a generation index definition.
Important: Do not delete the generation index definition of a GAR
database that has already been used by B92ARPRI.
Update Generation ID
Definition
PE92DF51 --------------------------------------------------------------------Command ===> ________________________________________________________________
Update Generation ID Definition
Generation ID
Last update: BETAINST 20.12.2017 12:00:00
: 25
Generation Last Date
===> 31.12.2018
Generation Comment
===> GAR FOR 2018________________________
____________________________________
First Job Date
Last Job Date
: 01.01.2018
: 17.03.2018
Press ENTER key to update this entry and continue.
Press END key to cancel changes or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
221
System (Option A.S)
Fields
Generation (Option A.S.1)
Field
Description
Generation ID
ID of the generation database
Generation Last Date
End date of this generation database
Each generation of the GAR database is meant to hold
the archived job records of one year. The generation
last date will therefore typically be the last day of the
corresponding year.
Generation Last Date
Generation Comment
Optional comment that describes this generation
First Job Date
This field is automatically filled by B92ARPRI during
archiving. It contains the date of the first job/list that has
been archived in this generation database.
Last Job Date
This field is automatically updated by B92ARPRI during
archiving. It contains the date of the last job/list that has
been archived in this generation database.
The value of the Generation Last Date field determines in which
generation database a job description is stored by B92ARPRI.
To enable archiving, a current generation database with a generation last
date higher than the current date must exist.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
222
System (Option A.S)
Subsystems (Option A.S.2)
Subsystems (Option A.S.2)
Overview
The _beta log|z subsystem options record contains subsystem-specific
parameters for the _beta log|z subsystem.
When changes take
effect
For any changes of reader-related settings to take effect, the _beta log|z
reader has to be restarted. To to this, enter the console command
F stcname,RESTART READER. When using multi-image processing, you
have to restart the _beta log|z reader for each z/OS image.
Online-related settings take effect when you run the CLIST.
Navigation
From the "Primary Selection Menu", choose:
•
Option A.S.2
The "Subsystem Options Selection" panel is displayed, in which you
can enter your selection criteria.
Insert Subsystem
Options panel (Page 1)
The subsystem options definition comprises three panel pages. Only the
first page is displayed when you insert a new record. Use line command S
to update the fields of page 2 and 3 after inserting a new record.
PE92SO23 --------------------------------------------------------------------Command ===> ________________________________________________________________
Insert Subsystem Options
Subsystem ID
Subsystem Name
Subsystem Title
===> ....
Net ID
===> ........
===> ........
Location
===> ................
===> ________________________________________
Error Code Lowest
Job Selection Length
===> ....
===> .
Highest
1-8
Extended Messages
Write SMF Records
===> ....
===> ....
(Y)es or (N)o
(Y)es or (N)o
Send Message on Error ===> ....
to Submitter
===> ____
to Console
===> ____
to MOF
===> ____
to Notify Group ===> ____
(Y)es or (N)o
(Y)es or (N)o
(Y)es or (N)o
(Y)es or (N)o
Group ID
===> ....
===> ________
Press ENTER key to insert this entry and continue.
Press END key to cancel changes or HELP key for help information.
Fields (Page 1)
Field
Description
Subsystem ID
Subsystem ID
Net ID
Net ID
Subsystem Name
The maximum length of the subsystem name is eight
characters. Subsystems must have different system
names.
Location
Physical location (city) of the subsystem
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
223
System (Option A.S)
Subsystems (Option A.S.2)
Field
Description
Subsystem Title
The title is a short description of the subsystem
(optional).
Error Code Lowest
This field specifies the lowest completion code which is
to be treated as an error (1-9999). That is, all condition
codes up to this value are okay.
Error Code Highest
This field specifies the upper limit of condition codes
that are to be regarded as errors. Condition codes
higher than this value are considered to be okay.
_beta log|z shows step completion codes for every job
step in the "Job Information Table". If at least one of the
steps ended with a completion code within the range
denoted by the lowest and highest condition codes
specified here, the job is put into the Error queue.
Example:
Lowest Error Condition Code: 4
Highest Error Condition Code: 10
In this example, condition codes up to 3 are okay.
Condition codes from 4 to 10 (incl.) indicate errors.
Condition code 11 and higher are okay.
If you want to suppress condition code checking, enter
9999 for both the lowest and highest values.
There are two other ways of performing condition code
checking on a more selective basis:
•
You can include the HICC keyword on the OMS
control card for a job whose MSGCLASS output is
processed by _beta log|z (see "OMS control cards"
on page 47).
•
You can check condition codes with the help of a
user exit. See "User exits" in _beta log|z Installation
and System Guide.
Job Selection Length
See field descriptions of page 2
Extended Messages
One message is usually issued to the operator console
and the z/OS Syslog for each job processed. If
Extended Messages=Yes, one additional message is
written to the z/OS Syslog for each processed sysout
list. The messages are described in BSA Messages and
Codes.
Write SMF Records
Set this field to Yes if you want _beta log|z to write an
SMF record type 6 for each sysout list that it reads in.
For information on the product SMF records, see "SMF
records" in _beta log|z Installation and System Guide).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
224
System (Option A.S)
Subsystems (Option A.S.2)
Field
Description
Send Message on Error _beta log|z can send a TSO message to one or more
destinations when the _beta log|z reader puts a job on
the error queue. Specify Yes in this field if you want this,
and specify Yes in the desired destination fields:
to Submitter: The message is sent to the user specified
in the NOTIFY parameter of the jobcard.
to Console: The message is sent to the operator
console.
to MOF: The message is sent to the message output
facility (MOF). For more information, see "Scan
definitions for Message Output Facility (MOF)" on
page 305.
to Notify Group: The message is sent to all TSO users
that are a member of the notify group specified in the
Group ID field. For more information, see "Notify groups
(Option A.1.3)" on page 122.
Update Subsystem
Options panel (Page 2)
This panel contains the names of the steplibs (BETA92.CNTL and
BSA.CNTL), the parameter library (BETA.PARMLIB), and LST members.
This information is used when running batch utilities from the ISPF online
application.
PE92SO24 ---------------------------------------------------------- Page 2 of 3
Command ===> ________________________________________________________________
Update Subsystem Options
Subsystem ID
Last update: B92ADM1
: B92P
Net ID
Job Selection Length
Ask after Jobs Selected
Continue after Job Select Limit
===> 4
===> 0....
===> NO..
08/02/13
14:27:09
: DEBETA01
1-8
0-99999
(Y)es or (N)o
STEPLIB Dataset 1
STEPLIB Dataset 2
STEPLIB Dataset 3
STEPLIB Dataset 4
SFFPARM Dataset
===> BSA.LOAD____________________________________
===> BETA92.LOAD_________________________________
===> ____________________________________________
===> ____________________________________________
===> BETA.PARMLIB................................
Beta01 LST Member ID
Beta92 LST Member ID
===> 00
===> 00
00 - ZZ
00 - ZZ
Press ENTER to update the definition. Press UP for previous page or DOWN
for next page. Press END to cancel changes or HELP for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
225
System (Option A.S)
Fields (Page 2)
Subsystems (Option A.S.2)
Field
Description
Job Selection Length
This field can be used to optimize the search algorithm
when selecting jobs for display in the job select table.
The entry is of relevance only when you enter a job
mask or job net ID as selection criterion. We
recommend that you enter 4 or a higher value.
By default, time is the primary search criterion and the
job name or job net ID is the secondary search criterion.
For example, when you specify a time and job mask for
job selection, _beta log|z scans the database for jobs
matching the specified time. For each hit, it then checks
whether the job name also matches the specified mask.
You can revert this order and make _beta log|z scan the
database for jobs matching the specified mask first. For
each hit, it then checks whether the job also matches
the specified time.
The entry in this field determines when the search order
is reverted. For example, enter 5 to revert the search
order when the specified mask has a minimum length of
5 characters. If you enter 0 (zero), time is always used
as the primary search criterion.
Which search method is more efficient depends on the
naming conventions used at your site. Performance
tests with different settings will help you find the
optimum value for your site.
Ask after Jobs Selected You can use this field to limit the number of jobs found
during job selection and during selection of archived
jobs. Whether it is possible to override this limit or not
depends on the entry in the following field.
Continue after Job
Select Limit
This setting affects the Job Select table and the
Archived Job Select table when the specified number of
jobs has been reached.
If Yes, users can select more jobs (ENTER) or display
the current selection (PF3). Displayed message: Job
limit reached. PF3 to stop selection or ENTER
to continue.
If No, the current selection is displayed. Displayed
message: Job limit reached, maximum number of
displayable jobs reached.
STEPLIB Dataset 1-4
Enter the name of the steplib datasets (1-4).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
226
System (Option A.S)
Subsystems (Option A.S.2)
Field
Description
SFFPARM Dataset
Enter the name of Beta parameter library, which
includes the members B92LSTxx and B01LSTxx.
For more detailed information on the BETA.PARMLIB
and on the parameters defined in the LST members,
see "How to use LST parameters" and "LST parameters
in B92LSTxx" in _beta log|z Installation and System
Guide.
BETA01 LST Member
ID
BETA92 LST Member
ID
Update Subsystem
Options panel (Page 3)
This number or character combination identifies the LST
members in the BETA.PARMLIB. If you do not code it,
members B01LST00 and B92LST00 will be used.
PE92SO25 ---------------------------------------------------------- Page 3 of 3
Command ===> ________________________________________________________________
Update Subsystem Options
Subsystem ID
Last update: B92ADM1
: B92P
Net ID
08/02/13
14:27:09
: DEBETA01
No. of EDF Subsys & OSY Readers
Job Select Usage Default
Allow override by user
Time Usage Default
Allow override by user
===> 5.
===> END...
===> YES
===> LONG.
===> YES
0-20 (Minimum 1 to use EDF)
(EN)d,(ST)art,(SU)bmit
(Y)es or (N)o
(L)ong,(S)hort
(Y)es or (N)o
Set User-ID as Writer Name
for Online print only
Online print under
===> NO.
(Y)es or (N)o
===> USER
(U)ser or (S)tc
Allow Job Selection using:
Form and Sysout Class
Leading Wildcards in Jobname
===> YES
===> YES
(Y)es or (N)o
(Y)es or (N)o
Press ENTER to update the definition or UP to display the previous page.
Press END key to cancel changes or HELP key for help information.
Fields (Page 3)
Field
Description
No of EDF Subsys &
OSY Readers
Define the number of EDF/OSY readers that are to be
running in parallel to read in lists from EDF and from
EJM agents (0 - 20). The default is 0. We recommend
that you specify 5 readers. The number of readers
affects the data throughput from the Unix/Windows
system.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
227
System (Option A.S)
Subsystems (Option A.S.2)
Field
Description
Job Select Usage
Default
Specify the time that job selection (Option 1 - Job
Select) is to be based on by default:
•
Job submit time
•
Job start time
•
Job end time
The following field (Allow override by user) determines
whether users can override this default in their user
profile.
Note: When you define new defaults for job time usage
and job time format, changes will come into effect only
after the CLIST has been called again.
Time Usage Default /
Allow override by user
Enter Short to use hh:mm and Long to use hh:mm:ss to
display job start and end time in the Job Select table.
The following field (Allow override by user) determines
whether users are allowed to override this default in
their user profile.
Recommended settings: We recommend that you set
Time Usage Default=LONG and Allow override by
user=NO.
Note: When you define new defaults for job time usage
and job time format, changes will come into effect only
after the CLIST has been called again.
Set User-ID as Writer
Name for Online print
only
If Yes, the user ID will be automatically set as JES writer
name for online printing. (In this case, the writer name in
the "Print Characteristics" panel will be ignored.)
Online print under
When using line command P, the print requests are
submitted under the user ID of the current user (USER)
or under the user ID of the started task (STC). See
"Online print under user or STC" on page 229.
Allow Job Selection
using Form and Sysout
Class
Specify Yes to allow job selection via form and sysout
class (option 1- Job Select, Additional Arguments).
Allow Job Selection
using Leading
Wildcards in Jobname
Specify Yes to allow job selection using leading
wildcards in the job name field (option 1 - Job Select
and option 2 - Reload).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
228
System (Option A.S)
Line commands
Subsystems (Option A.S.2)
The following line commands are available in the "Subsystem Options
Selection" table:
S
Selects a subsystem options record for display or update
I
Inserts a new subsystem record
D
Deletes a subsystem options record
C
Copies a subsystem options record
V
Verifies the database level of the connected database
For details on output, see the description of the corresponding
batch utility in "B92DBVER: Database verification" on page 444.
Online print under user
or STC
Note
Online print under PAGEDEF/FORMDEF _beta log|z under VDF
_beta log|z
USER
blank
VDF STC
TSO User ID
USER
value(s) present
VDF STC
_beta log|z STC
STC
blank
_beta log|z STC
_beta log|z STC
STC
value(s) present
_beta log|z STC
_beta log|z STC
If you want to print to a file and you have specified User in the field Online
print under, the user must have the RACF authorization UPDATE.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
229
System (Option A.S)
Global options (Option A.S.3)
Global options (Option A.S.3)
Overview
The global options define certain global default values that apply to all
_beta log|z subsystems, for example, default retention periods and
defaults for sending e-mails.
Navigation
Option A.S.3
Global Options
Definitions panel (Page 1)
PE92SO03 --------------------------------------------------------------------Command ===> _________________________________________________________________
Global Option Definitions
Last update: B92ADM
Default Retention Periods
Reload Retention Period
===> 1...
Max. Online RETPD for Generations ===> 0...
07.11.2017 12:12:55
Days
Days
Default Archive Media
===> DISK.
(T)ape,(D)isk,(O)Disk,(F)ILET
Only keep Job Base Record
===> NO.
(Y)es or (N)o
Jobs with JCL Init Errors
===> SAVE..
(S)ave or (N)osave
Use best matching Job Groups ===> YES
(Y)es or (N)o
Show class processing
===> NO.
(Y)es or (N)o
Number of Work Days per Week ===> 5
1-7
Maximum Lines per Page
===> 55.
10-999
No. of Generation
===> 2.
1-99
System Date Mask
===> YYYY-MM-DD MM/DD/YYYY,DD.MM.YYYY
DD/MM/YYYY,YYYY.DDD,YYYY-MM-DD
Press ENTER to update the definition or DOWN to display the next page.
Press END key to cancel changes or HELP key for help information.
Fields (Page 1)
For the effects of the settings in this panel on the Job Select table, also
see the _beta log|z User Guide. For more information on the archiving
process, see "The archive run" on page 203.
Field
Description
Reload Retention
Period
The reload retention period defines the number of days
a reloaded job and its sysout lists will stay online.
Max. Online RETPD for Default value for: Maximum number of days that a list is
Generations
held online if its online retention period is specified in
number of generations
You can also specify a value in the Max. Online RETPD
for Generations field of each job group definition, which
overrides this default (see "Job group (Option A.1.2)" on
page 103).
You can use this field to avoid that list generations are
held online forever, for example, when a job has been
renamed or does no longer run on a regular basis.
Allowed values: 1..9999 (in days)
Default Archive Media
The default archive medium is used for jobs that cannot
be assigned to any valid class. It is also used as default
in systems that work without job masks.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
230
System (Option A.S)
Global options (Option A.S.3)
Field
Description
Only keep Job Base
Record
This setting is not used if the job group definition
specifies an online retention period for job information
records (Job Info > 0).
Specify when job information records are to be deleted
from the JOB database:
No
They are deleted together with the job base
record at the end of the online retention period
of the job.
Yes
They are deleted following the deletion of the
lists from the online spool.
For more information, see "How long to keep job
information online" on page 113.
Jobs with JCL Init
Errors
Specify whether jobs with JCL Init Errors are to be
archived (Save) or not (Nosave).
Use best matching Job
Groups
Controls how jobs are assigned to job groups by the
_beta log|z archive and cleanup utilities
The job group from the class is used if the class
definition specifies Class Processing Active = Yes.
The following principle is used for the jobs of all other
classes:
Yes
Best match principle (most discrete job mask)
No
Longest retention period (highest numeric value;
DAY/GEN is ignored)
For more detailed information and examples, see "Best
match or longest retention" on page 119.
Show class processing
Controls how jobs are assigned to job groups by the
_beta log|z job selection/display and security functions:
Yes
The job group from the class is used if the class
definition specifies Class Processing Active =
Yes. The best-match principle is used for the
jobs of all other classes.
No
The best-match principle is used for all jobs.
Number of Work Days
per Week
Enter the number of workdays per week (1..7). This
specification relates to the online retention period. For
example, enter 5 if workdays are Monday through
Friday.
Maximum Lines per
Page
Controls the page length of batch utility reports
Allowed values: 0..999 (Default: 55)
0 means that the maximum number of lines per page is
not checked.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
231
System (Option A.S)
Global options (Option A.S.3)
Field
Description
No. of Generation
Specify how many generation databases are to be
searched when a user submits a selection under
option 2 - RELOAD.
Allowed values: 1..99
System Date Mask
Date format to be used in the reports of batch utilities:
MM/DD/YYYY (American)
DD.MM.YYYY (Continental)
DD/MM/YYYY (British)
YYYY.DDD (Julian)
YYYY-MM-DD (International)
Global Options
Definitions panel (Page 2)
Use page 2 of the "Global Options Definitions" panel to define the defaults
for sending e-mails.
Note: If you are working with event actions of type EMAIL, you have to
restart the event router (primary command RES under option A.R.6) for
any changes on this page to take effect.
PE92SO30 ---------------------------------------------------------- Page 2 of 3
Command ===> _________________________________________________________________
Global Option Definitions
Last update: B92ADM
07.11.2017 12:12:55
Mail Settings
Mail Server Address ===> your.smtp.server__________________________________
===> __________________________________________________
===> __________________________________________________
===> __________________________________________________
Mail Server Port
===> 25___
Codepage ===> CECP273_
Mail from
===> b92print@betasystems.com__________________________
===> __________________________________________________
Web Link Settings
beta view URL
===> http://server:port/betaview_______________________
===> __________________________________________________
===> __________________________________________________
===> __________________________________________________
Job Link Favorite ===> favid=B92P&target=list___________________
List Link Favorite ===> favid=B92P_______________________________
Press ENTER to update the definition, press UP or DOWN to display other pages.
Press END key to cancel changes or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
232
System (Option A.S)
Fields (Page 2)
Global options (Option A.S.3)
Field
Description
Mail Server Address
IP address (numeric or symbolic) and port number of
the mail server to be used for sending e-mails
Mail Server Port
The standard port number of mail servers is 25. Ask
your administrator if in doubt.
_beta log|z supports the use of SSL/TLS (via AT-TLS)
when communicating with the SMTP server. For more
information, see "SSL-secured communication with
SMTP server" in _beta log|z Installation and System
Guide.
Codepage
Codepage used for conversion from EBCDIC when
sending e-mail
Character conversion uses the iconv installation
available on the z/OS host. Specify a standard
IBM codepage identifier like IBM-037 or IBM-273.
Standard IBM codepage identifiers are preferred, but
the legacy translation table values (CECP037,
CECP273, CECP277, CECP278, CECP280, CECP285,
CECP297, CECP500, CECP1026, CECP1145,
CECP1148, and CECP1155) continue to work and are
equivalent with IBM-037, IBM-273, etc. DEFAULT and
blank are also equivalent with IBM-273.
Note: The mail command under option 1 is codepage
aware and honors the terminal code page of the user.
Use the codepage from A.S.3 as terminal code page for
all other data that is used for mailing to avoid problems
with codepage-dependent characters.
Mail from
Default sender address for sending e-mail
This e-mail address makes _beta log|z recognizable for
the recipient as the sender of the mail. When a user
sends e-mail, the address from the user profile
(Option P.3) overrides the default from the global
options.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
233
System (Option A.S)
Global options (Option A.S.3)
Field
Description
beta view URL
If your _beta log|z system can be accessed via _beta
view, you can send web links to jobs and logs via email. You have to provide the following information:
Job Link Favorite
List Link Favorite
•
URL of the _beta view application
•
_beta view favorite to be used for job link
•
_beta view favorite to be used for list link
For example, if the ID of the favorite in _beta view is
B92P, enter the following in the Favorite fields:
Job link:
favid=B92P&target=list
List link:
favid=B92P
The target parameter controls how a generated link
opens in _beta view after the user has logged in. If you
want _beta view to show the job in the job selection
table, add &target=list in the Job Link Favorite
field. By default, a link opens the job list(s) in the _beta
view | browser. The corresponding parameter is
&target=document.
In skeletons, use the JOBLINK variable to generate a
link to the job, and the LISTLINK variable to generate a
link to the list. An example skeleton for a type Email
event action (Option A.R.6) can be found in "E-mail
skeleton" on page 323.
Note on favkey parameter (deprecated)
_beta log|z generates links with the favkey parameter if
values in the Favorite fields do not start with favid= and
expects values in the favkey syntax, for example,
fav_B92Prole. The favkey parameter is deprecated in
_beta log|z and _beta view.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
234
System (Option A.S)
Global Options
Definitions panel (Page 3)
Global options (Option A.S.3)
On page 3 of the "Global Options Definitions" panel, you can define a
disclaimer text (max. 36 lines with up to 70 characters each), which will be
appended to each e-mail message after the signature. Use PF8 (DOWN)
and PF7 (UP) for scrolling.
PE92SO31 ---------------------------------------------------------- Page 3 of 3
Command ===> _________________________________________________________________
Global Option Definitions
Last update: B92ADM
07.11.2017 12:12:55
Global Mail Settings
Email Disclaimer (1/3)
===> --____________________________________________________________________
===> Mandatory Information for business email according to German trade law
===> Pflichtangaben für geschäftliche Emails gemäß Handelsgesetzbuch und___
===> Aktiengesetz:_________________________________________________________
===> Beta Systems Software AG______________________________________________
===> Alt-Moabit 90d________________________________________________________
===> 10559 Berlin__________________________________________________________
===> Germany_______________________________________________________________
===> Phone: +49-(0)30-726 118-0____________________________________________
===> Fax: +49-(0)30-726 118-800____________________________________________
===> info@betasystems.com__________________________________________________
===> -_____________________________________________________________________
Press ENTER to update the definition, press UP or DOWN to display other pages.
Press END key to cancel changes or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
235
System (Option A.S)
Special reload (Option A.S.4)
Special reload (Option A.S.4)
Overview
The "Special Reload Selection Menu" provides access to the special
reload functions of _beta log|z.
Navigation
Option A.S.4
Special Reload Selection
Menu
PE92SR00 --------------------------------------------------------------------Option ===> __________________________________________________________________
Special Reload Selection Menu
1
RELOAD BY GEN.
-
System
- PROD
Location - BERLIN
Subsys-ID - B92P
User ID
- B92ADM
Display and Reload Archived Jobs by Generation
2
RELOAD V2
-
Display Version 2 Reload Selection Table
3
RELOAD V3x
-
Display or Update Reload Requests Version V32/V31
Select one of the above options or press END key to return to the previous
menu. Press the HELP key from any panel for help information.
Options
The following special reload functions are available in the "Special Reload
Selection Menu":
1
Reload by Generation
Enables you to reload archived jobs from a specific generation
database
2
Reload V2
Enables you to reload unconverted lists that were archived with
Beta 92 V2
3
Reload V3x
Enables you to reload unconverted lists that were archived with
Beta 92 V2
Further information
General information on the reloading procedure and the different methods
for reloading can be found in "Reloading jobs and lists (Option 2)" in _beta
log|z User Guide.
For information on the auto-reload function, see "Using automatic reload"
on page 257.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
236
System (Option A.S)
Special reload (Option A.S.4)
Reload by generation (Option A.S.4.1)
Overview
Reload by generation enables you to display archived jobs of a particular
generation database. Thus not only the latest generations but also earlier
generations can be retrieved.
Note
Data which have been converted from Beta 92 Version 2 are displayed in
this table without job ID, runtime, number of steps and lists, message
class, status, sysout class and error. Jobs from Beta 92 Version 3.2.1 and
earlier are displayed without steps and without the status M and N.
Procedure
1. Select option S.4.1 - Reload by Generation in the Administration
Selection menu to call the "Display archived Jobs" panel:
PE92RS00 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Display archived Jobs
Select GenID:
either relative ===> - 0.
Select from Date
Select to
Date
===> 02/01/08..
===> 02/15/08..
Optional Selection Criteria
Job Name
===> RODJOB*_
Job ID
===> *_______
System ID
===> *___
Job Group ID
===> *_______
Only Jobs from Version ===> ___
Initial Errors only
===> ____
Job Message Class
===> _
Status Type
===> ________
or absolute ===> ..
Time
Time
===> 00:00:00
===> 23:59:59
Job name or mask
Job ID
or mask
System ID or mask
Job group ID or mask
V2, V3X or V33
(Y)es,(N)o or blank
0-9, A-Z, + or :
(ME)ssages,(ER)ror,(NO)tes,(ED)F
Press ENTER key to display archived Jobs Selection Table.
Press END key to return to the previous menu.
2. Enter your selection criteria and press ENTER to call the "Archived
Job Select Table":
PE92RS10 ------------------------------------------------ Row
1 of
1959
Command ===> ________________________________________________ Scroll ===> PAGE
Archived Job Select Table
Sorted by Submit date and time D
Displayed Submit date and time
Line commands:
R - Insert Reload Request
Q - Display Reload Request
RR - Insert Block of Requests (from/to)
Primary commands: RBR Display curr Req of all users
RBR ALL Display all Req of all users
Sel
Date
Time
Jobname
Job ID Runtime Steps Lists
02/14/08 12:14:02 RODJOB01 J0009763 00:00:01
1
4
02/14/08 12:14:02 RODJOB02 J0009764 00:00:01
1
4
02/14/08 12:14:02 RODJOB03 J0009765 00:00:01
1
4
02/14/08 12:14:02 RODJOB04 J0009766 00:00:02
1
5
02/14/08 12:14:02 RODJOB05 J0009767 00:00:01
1
4
02/14/08 12:14:02 RODJOB06 J0009768 00:00:01
1
4
02/14/08 12:14:02 RODJOB07 J0009769 00:00:01
1
24
02/14/08 12:14:02 RODJOB07 J0009769 00:00:01
1
4
02/14/08 12:14:02 RODJOB08 J0009770 00:00:01
1
35
02/14/08 12:14:02 RODJOB09 J0009771 00:00:01
1
4
02/14/08 12:14:02 RODJOB10 J0009772 00:00:01
1
4
02/14/08 12:07:07 RODJOB11 J0009745 00:01:08
1
6
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
Status
M
Ver
04
04
04
04
04
04
04
04
04
04
04
04
237
System (Option A.S)
Special reload (Option A.S.4)
This table lists information about archived jobs that match your
selection criteria. You can press PF11 to display additional
information.
3. Use the available line commands to create reload requests for the
desired jobs.
Notes on Archived Job
Select Table
Fields
•
99:59:59 is the maximum value in the Runtime column and means
that the runtime was 99:59:59 or longer.
•
255 is the maximum value in the Lists column and means that the job
has 255 lists or more.
Field
Description
Select GenID
Enter a generation ID. All archived jobs with this
generation ID will be displayed. The value must be
numeric.
relative
Relative to the current date, where the most
current generation ID is 0.
absolute
The first generation ID is 0. You have to
know the date of this generation ID.
Select from Date/Time
and Select to
Date/Time
To select archived jobs via the time range, enter a
start/end date. All jobs that fall within this range will be
displayed. Time refers to the job start time / end time.
Job Name
To select archived jobs via the job name, enter a job
name or a mask.
Job ID
To select archived jobs via the job ID assigned by JES,
enter a job ID or a mask. JES prefixes the job number
with a three-character identifier (JOB for job, TSU for
TSO user, STC for started task). You can abbreviate the
JES prefix to the first letter and drop leading zeros.
System ID
To select archived jobs via the CPU system ID by which
they were run, enter a system ID or a mask.
Job Group ID
You can delimit the selection by specifying a job group.
You can use masks as well.
Only Jobs from Version Enter the Beta 92 version of the selection you want to
reload (V2 for Version 2, V3X for Version 3.2.1 and
earlier, V33 for Version 3.3.x). The data being displayed
have been converted to Version 3.3.x.
Initial Errors only
Specify 'Yes' to select only jobs with errors. Specify 'No'
to select only jobs without errors. Leave the field blank
to select jobs with and without errors.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
238
System (Option A.S)
Special reload (Option A.S.4)
Field
Description
Job Message Class
Here, you can enter the MSGCLASS= parameter of the
jobcard if it is an output class processed by Beta 92. If
the job's message class is not processed by Beta 92,
enter the sysout class of the first processed list.
Status Type
Here, you can delimit the display to jobs that have the
status Message for jobs that contain a message, Error
for jobs with errors, Notes for jobs that contain a note,
or EDF for jobs that were read-in via Beta 92 EDF.
Sorted by Submit date
and time
D indicates that the table is sorted in descending order.
If this field is blank, the table is sorted in ascending
order.
Status
The status of the displayed job: M for jobs that contain a
message, N for jobs that contain a note, E for jobs with
errors, + for jobs that were read-in via Beta 92 EDF, and
: for lists sent by EJM agents.
Ver
Archive/Conversion version information
01 Job was archived by Beta 92 V2 and converted
02 Job was archived by Beta 92 V3R1M1 - V3R2M1
and converted (original conversion program)
04 Job was archived by Beta 92 V3R3M1 or later
05 Job was archived by Beta 92 V3R1M1 - V3R2M1
and converted (enhanced conversion program)
SysID
CPU system ID
M Sysout
The job message class is shown at the first position. Up
to 7 other classes can be displayed if used for the job
sysout.
Error
Error type:
S XXX
System abend code
UXXX
User ABEND code
JCL INIT
Error because of z/OS JCL error
USR DEF User-defined error
CC XXXX Condition code in error range
Exp. Date
OUTLIM
Output limit exceeded
JCL FAIL
Error during job runtime
Expiration date
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
239
System (Option A.S)
Line commands
Primary commands
Note on autoreload
Special reload (Option A.S.4)
R
Marks a reload request
RR
Writes a reload request (from-to)
Q
Displays reload request for this job only
F
Finds a job name in this display
TPRINT
Prints the screen
SORT
Sorts different columns in the table in ascending (blank)
or descending (D) order
RBR
Displays all reload requests of this user within the time
range indicated in the panel "Display Archived Jobs";
reload requests being generated as V2 and V3X under
option 2, "Beta 92 Archive Version", are also displayed
RBR ALL
Displays all reload requests of all users and lists; reload
requests being generated as V2 and V3X under option 2,
"Beta 92 Archive Version", are also displayed
RELO
Invokes the batch reload for all reload requests of all
users
If autoreload is enabled, the line command U and the primary command
RELO are no longer needed, and they are therefore not displayed in the
corresponding _beta log|z panels by default. If you want to display them
anyway, see the description of the LST parameter B92_RLD_URGENT in
"LST parameters in B92LSTxx" in _beta log|z Installation and System
Guide. For information on using automatic reload, see "Using automatic
reload" on page 257.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
240
System (Option A.S)
Special reload (Option A.S.4)
Sorting the Archived Job Select Table
Syntax
The primary command SORT has the following syntax:
SORT column_name sort_order
column_name
sort_order
Note
Specify column_name ...
To sort according to ...
DATE
Submit date and time
TIME
Submit time
JOBNAME
Jobname
JOBID
Job ID
RUNTIME
Job runtime
STEPS
Number of steps
LISTS
Number of lists
STATUS
Status
JOBGROUP
Job group
VERSION
Archive version
ERROR
Error column
Specify sort_order ...
To sort in ...
A or blank
Ascending order (lowest to highest - default)
D
Descending order (highest to lowest)
The current sort order is displayed in the first line of the "Archived Job
Select Table".
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
241
System (Option A.S)
Special reload (Option A.S.4)
Processing reload requests
Procedure
•
When jobs have been marked for reloading using line command R, the
"Reload Request Selection" table is displayed when you enter the
primary command RBR, RBR ALL or the line command Q in the
"Archived Job Select" table:
PE92RS20 -------------------------------------------------- Row
1 of
8
Command ===> ________________________________________________ Scroll ===> CSR
Reload Request Selection
S - Select Reload Request
D - Delete Reload Request
Sel
Date
Time
Jobname
Job ID
Type
CUser
CTime
CDate
02/14/08
14:51:18 BXW#PR
J0010018 00000000 AVSCHM
18:10:15 02/25/08
02/14/08
14:55:14 JEKFRUL2 FAAK8540 00000000 AVSCHM
18:10:15 02/25/08
02/14/08
15:03:16 BXW#PR
J0010029 00000000 AVSCHM
18:10:15 02/25/08
02/14/08
15:11:36 BXW#PR
J0010044 00000000 AVSCHM
18:10:15 02/25/08
02/14/08
15:12:23 BXW#PR
J0010046 00000000 AVSCHM
18:10:14 02/25/08
02/14/08
15:13:09 BXW#PR
J0010050 00000000 AVSCHM
18:08:06 02/25/08
02/14/08
15:20:13 JEKFRUL2 FAAK7236 00000000 AVSCHM
18:08:06 02/25/08
02/14/08
15:42:17 B92ARPRI J0010096 00000000 AVSCHM
18:08:06 02/25/08
******************************** BOTTOM OF DATA ********************************
This table lists all reload requests within the time range indicated in the
panel "Display Archived Jobs".
It is possible that several reload requests appear in column Jobname
for one job.
Line commands
D
Deletes all reload requests of this job
S
Displays the reload request
U
Invokes the batch reload of all requests for this job
Primary command
RELO
Note on autoreload
If autoreload is enabled, the line command U and the primary command
RELO are no longer needed, and they are therefore not displayed in the
corresponding _beta log|z panels by default. If you want to display them
anyway, see the description of the LST parameter B92_RLD_URGENT in
"LST parameters in B92LSTxx" in _beta log|z Installation and System
Guide. For information on using automatic reload, see "Using automatic
reload" on page 257.
Invokes the batch reload for all reload requests of all
users
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
242
System (Option A.S)
Converting from
version 3.2.1 and earlier
Special reload (Option A.S.4)
Usually, there is only one entry per job in the GAR. More than one entry
exists if:
•
Class processing is active for at least one class.
•
Lists of a job were archived during different runs of job DAILY.
You only have to mark one entry for a job in order to reload all lists of this
job.
The Type column indicates if the job itself (00000000) or a list of this job
(000000nn) is displayed.
Converting from
version 3.3.x
Usually, there is only one entry per job in the GAR. More than one entry
exists if:
•
Class processing is active for at least one class.
•
Lists of a job were archived during different runs of job DAILY.
You only have to mark one entry for a job in order to reload all lists of this
job.
The type is always 00000000.
Converting from
version 2
There exists only one record after the conversion, and only one reload
request has been produced. The type is always 00000000.
•
Enter line command S to display the "Reload Request Display" panel:
PE92RL23 --------------------------------------------------------------------Command ===> _________________________________________________________________
Reload Request Display
Last update: AV1
07/09/2002 15:02:38
Select from Date
Select to
Date
: 06/28/2002 Time
: 06/28/2002 Time
Job Name
Job ID
Job Message Class
Archive Pointer
Reload Version
: BXW#LPR
: TSU02403
:
: 2002180C03E700000000010000000100
: 6
Press END key to return to the previous panel or
information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
: 08:16:59
: 08:16:59
Help key for help
243
System (Option A.S)
Fields
Special reload (Option A.S.4)
Field
Description
Archive Pointer
The archive pointer is written from the generation
database to the reload request.
Reload Version
_beta log|z offers the following reload versions:
2: RV2 (from 3.3)
3: V3.2 online
4: Job/List being converted from Version 2 to Version
3.3.x
5: Job/List being converted from Version 3.2.1 or 3.1.x
to Version 3.3.x (old conversion)
6: Job/List of Version 3.3.x
7: Job/List being converted from Version 3.2.1 or 3.1.x
to Version 3.3.x (new conversion)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
244
System (Option A.S)
Special reload (Option A.S.4)
B92RLOAD Reload V2 (Option A.S.4.2)
Overview
Reload V2 enables you to reload lists that were archived under Beta 92 V2
and have not yet been converted.
Recommended: We recommend that you convert all affected jobs
because Reload V2 makes reloading very slow. After conversion you can
use option 2 from the "Primary Selection Menu"
1. Select option 2 - Reload V2 in the "Special Reload Selection Menu" to
call the "Reload Request Selection" panel.
Selecting information
from the archive
2. Enter selection criteria to retrieve a list of jobs and lists that have been
archived under Beta 92 V2.
Reload Request
Selection
PE92UT03 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Reload Request Selection
Select from Date
Select to
Date
Job Name
===> 03/31/2004
===> 03/31/2004
===> *_______
Time ===> 00:00:00
Time ===> 23:59:59
Job name or mask
Optional Selection Criteria
(only honored during reload, not when displaying Reload Selection Table)
Job ID
Job Net ID
Job Group ID
Initial Errors only
Job Message Class
Queue Type
===> *_______
===> *_______
===> *_______
===> ____
===> _
===> _____
Job ID or mask
Net ID or mask
Job group ID or mask
(Y)es or (N)o
0-9, A-Z
Queue type
Press ENTER key to display Reload Selection Table.
Press END key to return to the previous menu.
Fields
Field
Description
Select from Date/Select Enter the time range for which you would like to display
to Date
archive information. Entries in these fields are required.
Select from Time/Select Here, you can specify the selection criteria according to
to Time
submit time. These entries are optional. If the fields are
left blank, the defaults 00:00:00 for start and 23:59:59
for end time are automatically used.
Job Name
Enter a job name or a mask.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
245
System (Option A.S)
Special reload (Option A.S.4)
The entries in the following fields are optional. They will be honored by
batch utility B92RLOAD when reloading lists and jobs from the archive
media. They cannot be honored when retrieving the list of archived jobs
because the required information is no longer available online.
Field
Description
Job ID
Enter the job identification assigned to the job by the
Job Entry Subsystem (JES) or enter a mask (* or ?). A
job ID consists of the job number prefixed by a one- or
three-character identifier (J or JOB for job, S or STC for
started task, T or TSU for TSO user).
Job Net ID
Enter the name of a job net, or a mask. For more
information on jobs nets, see "OMS control cards" on
page 47.
Job Group ID
You can delimit the selection by specifying a job group.
You can use masks as well. Job groups are defined
under option A.1.2 of the "Primary Selection Menu".
Initial Errors only
This option refers to jobs that were placed onto the
ERROR queue when they were read into _beta log|z.
Whether the jobs were moved onto another queue later,
is immaterial. Specify Yes to select only jobs with errors.
Specify No to select only jobs without errors. Leave the
field blank to select jobs with and without errors.
Job Message Class
Here, you can enter the MSGCLASS parameter of the
jobcard if it is an output class processed by _beta log|z.
If the job's message class is not processed by _beta
log|z, enter the sysout class of the first processed list.
Queue Type
Here, you can delimit the reloading process to jobs that
were set onto a particular queue. Leave this field blank if
jobs on all queues are to be selected. Possible queues
are: I, R, E, H, and W. For more information on queues,
see "Logical queues".
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
246
System (Option A.S)
Special reload (Option A.S.4)
Reloading lists or job information using B92RLOAD Reload V2
Overview
The batch utility "B92RLOAD Reload V2" is used for reloading
unconverted list that were archived with Beta 92 V2.
Procedure
1. Press ENTER in the "Reload Request Selection" panel to display a list
of all jobs archived under Beta 92 Version 2 or earlier that match the
specified criteria.
2. Do one of the following:
Reload Request
Selection (2)
•
To create a reload request, enter line command I in front of the
job.
The reload request will be executed at the next run of the Reload
batch utility. See "Reloading jobs and lists (Option 2)".
•
To reload a job and its lists immediately, enter line command U in
front of the job. This will display the Reload Batch Submit panel.
Modify the displayed jobcard for the reload job if necessary and
press ENTER to submit the job.
PE92UT03 -------------------------------------------------- Row
1 of
213
Command ===> ________________________________________________ Scroll ===> PAGE
Reload Request Selection
I - Insert Reload Request
U - Perform Reload Request
Submit
Sel Jobname
Date
Time
Media
SYSLBETA 01/01/2007 00:00:00 DISK
ZACKSCH 01/01/2007 00:05:01 TAPE
SCHEDULE 01/01/2007 00:15:00 TAPE
FLS93R61 01/01/2007 11:10:56 DISK
SYSLBETA 01/02/2007 00:00:00 DISK
SYSLBETA 01/02/2007 00:00:00 DISK
ZACKSCH 01/02/2007 00:05:01 TAPE
SCHEDULE 01/02/2007 00:15:01 TAPE
BPCPR1
01/02/2007 00:15:51 TAPE
AUTOCMD 01/02/2007 00:30:01 TAPE
DFHSM
01/02/2007 07:36:36 DISK
DFHSM
01/02/2007 07:40:29 DISK
DFHSM
01/02/2007 07:43:31 DISK
BSS01ARI 01/02/2007 08:32:29 TAPE
BSS01ARI 01/02/2007 09:05:24 TAPE
Pool
Dual
DISK01
LONG
LONG
DISK01
DISK01
DISK01
LONG
LONG
LONG
LONG
DISK01
DISK01
DISK01
LONG
LONG
Note: When auto-reload has been activated, other reload commands
are no longer needed and therefore redundant. The line command U is
no longer displayed and can no longer be entered in the _beta log|z
panels by default. Ask your _beta log|z administrator if you want to use
the line command U.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
247
System (Option A.S)
Special reload (Option A.S.4)
B92RLOAD V2 report
+------------------------------------------------------------------------------------------+
| Beta 92 V7R2 - VERSION 4 RELOAD UTILITY
15.02.2007 11:21:01 PAGE 1
|
|
|
| JOBNAME
JESID
DATE
TIME
DDNAME
STEP
PROCSTEP ACTION
|
|-------- -------- -------- -------- -------- -------- -------- ---------------------------|
| AV1PROC JOB07915 01.01.07 13:49:49 *
*
*
JOB HAS BEEN RELOADED
|
| AV1PROC JOB07915 01.01.07 13:49:49 JESMSGLG JES2
*
LIST HAS BEEN RELOADED
|
| AV1PROC JOB07915 01.01.07 13:49:49 JESJCL
JES2
*
LIST HAS BEEN RELOADED
|
| AV1PROC JOB07915 01.01.07 13:49:49 JESYSMSG JES2
*
LIST HAS BEEN RELOADED
|
| AV1PROC JOB07915 01.01.07 13:49:49 SYSUT2
STEP1
*
LIST HAS BEEN RELOADED
|
|
|
| 1 JOB(S) AND 4 LIST(S) HAVE BEEN RELOADED.
|
| PROGRAM B92RLOAD ENDED WITH RC(0).
|
+------------------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
248
System (Option A.S)
Special reload (Option A.S.4)
B92RLOAD Reload V3 (Option A.S.4.3)
Overview
Reload V3 enables you to reload lists that were archived under Beta 92 V3
and have not yet been converted.
Jobs and lists reloaded from the Version 3.2.1 and 3.1.x archives are
placed by _beta log|zonto the History queue. The online retention period
for this queue is defined under option A.S.3 - Global Options.
Recommended: We recommend that you convert all affected jobs
because Reload V3 makes reloading very slow. Use option 2 from the
"Primary Selection Menu" for the reloading of converted jobs.
Use this option only for lists of version 3 which have not yet been
converted. Use this option only if there are still any lists which have not yet
been converted. Reloading becomes very slow. We recommend that you
start the conversion as soon as possible and use option 2 from the
"Primary Selection Menu".
B92RLOAD
The batch utility B92RLOAD performs all reload requests that have been
defined via:
•
"Job Select Table" and "Job Information Table" (line command R)
•
Option L.2 - RELOAD V3x
•
Option 3.3 - RELOAD V2
Jobs and lists reloaded from the archives are placed by _beta log|z onto
the History queue. Choose option A.S.3 to specify the default retention
period for a reloaded job and its sysouts.
You will find the JCL in member B92RLOAD in the BETA92.CNTL.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
249
System (Option A.S)
B92RLOAD JCL
Special reload (Option A.S.4)
The example below shows the complete JCL for B92RLOAD:
+-------------------------------------------------------------------+
|jobcard
|
|//RELOAD
EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92RLOAD,SIGNON=YES')
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//B92DEF
DD DUMMY
|
|//*
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//*
|
|//B92LOG
DD SYSOUT=*
|
|//B92TRACE DD SYSOUT=*
|
|//SYSPRINT DD SYSOUT=*
|
|//OMSPRINT DD SYSOUT=*
|
|//*
|
+-------------------------------------------------------------------+
When the program BST01RFF is started with the parameters
PARM=('PGM=B92RLOAD'), all pending reload requests for Version 3,
Version 2 or Version 1 lists and jobs are carried out. These parameters
must be indicated exactly as shown here. The parameters B01LST and
B92LST indicate which parmlib members are to be loaded to run this job.
The STEPLIB card indicates the load module library where the _beta log|z
programs are located.
The SFFPARM card indicates the BETA parameter library.
The B92DEF DD card defines the _beta log|z database definition file. It
can be set to DUMMY because the B92RLOAD program accesses the
database via the _beta log|z started task.
The B92LOG DD card allows the realization of a trace function to protocol
error conditions during the reload run. In case a trace is to be written to a
dataset, the DCB parameters must be as follows:
DSORG=PS, RECFM=FB, LRECL=200
The B92TRACE DD card offers trace information on error cases. This is
for simulation purposes.
With the OMSPRINT DD card you specify where the log is to be written to.
Return codes
0
Program ended normally.
4
No jobs to reload found.
8
An error occurred.
16
Severe error occurred.
24
Started task unavailable during utility run.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
250
System (Option A.S)
Special reload (Option A.S.4)
Selecting a reload request
Procedure
Reload Request
Selection
•
Select option 2 - Reload in the "Special Reload Selection Menu" to call
up the "Reload Request Selection" panel in which you can specify
selection criteria for the reload requests. Only reload requests
matching the specified criteria will be selected.
PE92UT03 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Reload Request Selection
Select from Date
Select to
Date
Job Name
===> 03/31/2004
===> 03/31/2004
===> *_______
Time ===> 00:00:00
Time ===> 23:59:59
Job name or mask
Optional Selection Criteria
(only honored during reload, not when displaying Reload Selection Table)
Job ID
Job Net ID
Job Group ID
Initial Errors only
Job Message Class
Queue Type
===> *_______
===> *_______
===> *_______
===> ____
===> _
===> _____
Job ID or mask
Net ID or mask
Job group ID or mask
(Y)es or (N)o
0-9, A-Z
Queue type
Press ENTER key to display Reload Selection Table.
Press END key to return to the previous menu.
The following table is displayed after you press ENTER:
PE92UT02 -------------------------------------------------- Row
1 of
1
Command ===> _________________________________________________________________
Reload Request Selection
S - Select Reload Request
I - Insert Reload Request
D - Delete Reload Request
C - Copy Reload Request
Start
End
Date
Time
Date
Time
Jobname
Job ID
Net ID
DDName
30.06.2007 00:00:00 TODAY
23:59:59 *
*
*
*
******************************** BOTTOM OF DATA ********************************
Sel
This table lists all reload requests that match your selection criteria.
The first reload request in the list was created via option 3.2 - Reload.
All other reload requests in the list were inserted by _beta log|z on
entering line command R in the Job Select table.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
251
System (Option A.S)
Fields
Line commands
Special reload (Option A.S.4)
Field
Description
Select from Date/Time
and Select to
Date/Time
To select reload requests via the time range, enter a
start/end date and (optionally) a start/end time. All
reload requests that fall entirely or partly within this
range will be displayed. Time refers to the job submit
time.
Job Name
To select reload requests via the job name, enter a job
name or a mask.
Job ID
To select reload requests via the job ID assigned by
JES, enter the job identification assigned to the job by
the Job Entry Subsystem (JES) or enter a mask (* or ?).
A job ID consists of the job number prefixed by a one- or
three-character identifier (J or JOB for job, S or STC for
started task, T or TSU for TSO user).
Job Net ID
To select reload requests via the job net, enter a job net
or a mask. For more information on jobs nets, see "OMS
control cards" on page 47.
The following line commands are available in the panel:
S
Selects the reload request for display or update
I
Adds a new reload request (insert)
D
Deletes a reload request
C
Adds a new reload request (copy)
U
Performs the reload request
Note: When auto-reload has been activated, other reload
commands are no longer needed and redundant. Therefore the
line command U is no longer displayed and can no longer be
entered in the product panels by default. Ask your product
administrator if you want to use the line command U.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
252
System (Option A.S)
Special reload (Option A.S.4)
Defining a reload request
Procedure
•
Insert Reload Request
To define a new reload request, enter line command I in the "Reload
Request Selection" panel. This will display the "Insert Reload Request"
panel:
PE92UT12 --------------------------------------------------------------------Command ===> _________________________________________________________________
Insert Reload Request
Select from Date
Select to
Date
===> 30.06.2006
===> TODAY
Time
Time
===> 00:00:00
===> 23:59:59
Optional Selection Criteria
Job Name
Job ID
Job Net ID
Job Group ID
Initial Errors only
Job Message Class
Queue Type
===> *
===> *
===> *
===>
===>
===>
===>
Job name or mask
Job ID
or mask
Net ID
or mask
Job group ID or mask
(Y)es or (N)o
0-9, A-Z
Queue type
Press ENTER key to insert this entry and continue.
Press END key to cancel changes or HELP key for help information.
Fields
Field
Description
Select from Date/Select Specify from which time range you wish to reload jobs.
to Date
Entries in these fields are required. The specification
relates to the job submit time.
Select from Time/Select You can specify start and end times to select reload
requests. These entries are optional.
to Time
Specify HH or HH.MM or HH.MM.SS. A colon (:) may be
used as a delimiter as well. If you do not enter any value
in these fields, the defaults 00:00:00 for start and
23:59:59 for end time are used.
Job Name
Enter the full job name specified in the job card, or a
mask. All jobs matching this entry are selected.
Specifying a job name remarkably speeds up reloading.
Job ID
Enter the job identification assigned to the job by the
Job Entry Subsystem (JES) or enter a mask (* or ?). A
job ID consists of the job number prefixed by a one- or
three-character identifier (J or JOB for job, S or STC for
started task, T or TSU for TSO user). This entry is
optional.
Job Net ID
Enter the name of a job net, or a mask. This entry is
optional.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
253
System (Option A.S)
Special reload (Option A.S.4)
Field
Description
Job Group ID
You can delimit the selection by specifying a job group.
You can use masks as well. Job groups are defined
under option A.1.2 of the "Primary Selection Menu".
Initial Errors only
This option refers to jobs that were placed onto the
ERROR queue when they were read into _beta log|z.
Whether the jobs were moved onto another queue later,
is immaterial. Specify Yes to select only jobs with errors.
Specify No to select only jobs without errors. Leave the
field blank to select jobs with and without errors.
Job Message Class
Here, you can enter the MSGCLASS= parameter of the
job card if it is an output class processed by _beta log|z.
If the job's message class is not processed by _beta
log|z, enter the sysout class of the first processed list.
Queue Type
Here, you can limit the reloading process to jobs that
were set onto particular _beta log|z queues. Possible
queues are: I, R, E, H, and W (see "Logical queues" in
_beta log|z User Guide.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
254
System (Option A.S)
Special reload (Option A.S.4)
Processing one or all reload requests
Procedure
By default, the _beta log|z reload utility performs all reload requests that
have been defined via line command R in the "Job Select Table" or the
"Job Information Table" or via the "Reload Request Insertion" panel.
To start the reload batch utility, use one of the methods described below.
Processing all reload
requests
1. Select option A.S.4.3 from the "Primary Selection Menu".
2. Display all or some of the current reload requests in the "Reload
Request Selection" panel.
3. Enter primary command RELOAD. This will display the List Reload
Utility in a panel.
Note: You can also submit the batch utility B92RLOAD directly from
the BETA92.CNTL.
Processing a single
reload request
1. Select option A.S.4.3 from the "Primary Selection Menu".
2. Display all or some of the current reload requests in the "Reload
Request Selection" panel.
3. Enter line command U in front of a reload request.
This will display the List Reload Utility in a panel:
List Reload Utility
PE92RL25 --------------------------------------------------------------------Command ===> _________________________________________________________________
-------------------------------------I
I
I beta logz V7R2 List Reload Utility I
I
I
--------------------------------------
Job Statement Information
===> //jobname JOB acct,name,CLASS=A,MSGCLASS=P
===> //*
===> //*
===> //*
Press ENTER key to Submit job.
Press END key to return to previous menu or HELP key for help information.
Note: When auto-reload has been activated, other reload commands are
no longer needed and redundant. Therefore the line command U is no
longer displayed and can no longer be entered in the _beta log|z panels by
default. Ask your _beta log|z administrator if you want to use the line
command U.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
255
System (Option A.S)
Special reload (Option A.S.4)
B92RLOAD V3 report
+---------------------------------------------------------------------------------------------------+
|Beta 92 V7R2 - VERSION 4 RELOAD UTILITY (REQUEST PROTOCOL)
|
|SDATE
STIME
PDATE
PTIME
JOBNAME JOBID
DDNAME NETID GROUP
CLS ERR USER
DATE
TIME|
|------- ------ ------- ------- -------- -------- ------- ------ ------ ---- --- ------- ----- -----|
|07.07.07 09:43:24 07.07.07 09:43:24 BXW#DR1 JOB05069 1
F
STL3
12.07.07 14:40:24|
|Beta 92 V7R2 - VERSION 4 RELOAD UTILITY (RELOAD PROTOCOL)
07/12/2006 14:40:55 PAGE 1
|
|JOBNAME
JESID
DATE
TIME
DDNAME
STEP
PROCSTEP ACTION
|
|-------- -------- ---------- -------- -------- -------- -------- ---------------------------|
|BXW#DR1 JOB05069 07/07/2007 09:43:24 *
*
*
JOB HAS BEEN RELOADED
|
|BXW#DR1 JOB05069 07/07/2007 09:43:24 JESMSGLG JES2
*
LIST HAS BEEN RELOADED
|
|BXW#DR1 JOB05069 07/07/2007 09:43:24 JESMSGLG JES2
*
LIST HAS BEEN RELOADED
|
|BXW#DR1 JOB05069 07/07/2007 09:43:24 JESMSGLG JES2
*
LIST HAS BEEN RELOADED
|
|BXW#DR1 JOB05069 07/07/2007 09:43:24 JESMSGLG JES2
*
LIST HAS BEEN RELOADED
|
|BXW#DR1 JOB05069 07/07/2007 09:43:24 JESMSGLG JES2
*
LIST HAS BEEN RELOADED
|
|1 JOB(S) AND 5 LIST(S) HAVE BEEN RELOADED.
|
|PROGRAM B92RLOAD (NEW
) ENDED WITH RC(0).
|
+---------------------------------------------------------------------------------------------------+
Action
Action
Description
ARCHIVE DATA SET HAS
EXPIRED
The job could not be reloaded because the
archive retention period has expired.
JOB HAS BEEN RELOADED
The job has been reloaded.
JOB IS ONLINE
The job has not been reloaded because the job
is already in the online spool.
LIST HAS BEEN RELOADED
The list has been reloaded.
LIST IS ONLINE
The list has not been reloaded because the list
is already in the online spool.
CRITERIA DO NOT MATCH
The program could not find any jobs or lists
which match the given criteria.
RELOAD FAILED
Reloading has failed.
ARCHIVE DATASET
ALLOCATION ERROR
The job could not be reloaded due to an
allocation error.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
256
System (Option A.S)
Special reload (Option A.S.4)
Using automatic reload
Overview
The autoreload function makes it possible to handle the processing of the
generated reload requests automatically.
Reload requests are generated when jobs are marked for reloading, for
example, via line command R under option 1 or 2.
Master/Slave STC or
autoreload STC
You can enable the automatic reload function in one of the following STCs:
•
Product master STC
•
Product slave STC
•
Separate autoreload STC
Do not enable the autoreload function in more than one STC.
Triggers for automatic
reload
LST parameters for
enabling autoreload
Reloading is started by the automatic reload function when:
•
The number of jobs marked for reloading exceeds the specified
maximum (see B92_AUTORLD_REQUEST_LIMIT_HIGH)
•
The end of the autoreload interval has been reached (see
B92_AUTORLD_INTERVAL) and the number of jobs marked for
reloading has reached the specified minimum (see
B92_AUTORLD_REQUEST_LIMIT_LOW)
•
The autoreload interval has gone by for the specified number of times
without reloading (see B92_AUTORLD_SETTLE_COUNT) and reload
requests are present
Use the following LST parameters to enable the autoreload function in a
started task.
Parameter name
Value
Description
Opt./Req. Default
B92_AUTORLD_ENABLED
YES | NO
YES enables the automatic reload function in the Optional
current started task (master, slave, or autoreload
STC)
NO
Important: If the B92LSTxx member is shared
by more than one STC, you have to code
B92_AUTORLD_ENABLED=YES on the EXEC
parm of the STC procedure.
B92_AUTORLD_SSID
ssid
Specifies the subsystem (master or slave) that is see description
used by the autoreload function to access the
product database
none
This parameter is required if B92_AUTORLD_
ENABLED=YES.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
257
System (Option A.S)
Special reload (Option A.S.4)
LST parameters for
autoreload processing
Parameter name
Use the following LST parameters to control how the autoreload function
processes reload requests:
Value
Description
Opt./Req. Default
B92_AUTORLD_INTERVAL 0..180
Number of seconds after which the autoreload
function checks the number of reload requests
Optional
120
B92_AUTORLD_REQUEST numeric
_LIMIT_HIGH
value
Maximum number of reload requests
Optional
see description
Optional
10
Optional
1
Optional
NO
This parameter sets the highest number of
reload requests that are allowed to accumulate.
Reload is triggered when the number of reload
requests exceeds this value.
Default: Value of B92_AUTORLD_REQUEST_
LIMIT_LOW multiplied by 2
B92_AUTORLD_REQUEST numeric
_LIMIT_LOW
value
Minimum number of reload requests
B92_AUTORLD_SETTLE_
COUNT
Maximum number of intervals without reloading
numeric
value
B92_AUTORLD_VERBOSE YES | NO
Changing parameters
dynamically
This parameter sets the lowest number of reload
requests that have to accumulate. Reload is
triggered when this number and the end of the
next interval has been reached.
B92_AUTORLD_INTERVAL multiplied by
B92_AUTORLD_SETTLE_COUNT is the
maximum wait time of a reload request. Reload
is triggered when the specified number of
intervals has gone by, even if there a fewer
reload requests than
B92_AUTORLD_REQUEST_LIMIT_LOW.
Set to YES to log automatic reload activities
The following LST parameters can be changed dynamically with the help
of the BSA Service Manager (Option A.D.S):
•
B92_AUTORLD_INTERVAL
•
B92_AUTORLD_SETTLE_COUNT
•
B92_AUTORLD_REQUEST_LIMIT_LOW
•
B92_AUTORLD_REQUEST_LIMIT_HIGH
"Working with started task parameters (Option 1)" in BSA Service Manager
Manual describes how you can insert and activate these parameters for
the product and subsystem in use.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
258
Reader (Option A.R)
In this chapter
Reader (Option A.R)
In this chapter
Topic
Page
Class (Option A.R.1) ............................................................................... 260
JES reader (Option A.R.2)...................................................................... 264
Scanning (Option A.R.3) ......................................................................... 268
Selecting scan definitions ................................................................... 270
Defining scan definitions ..................................................................... 274
Target field IDs ................................................................................... 284
Example: Defining a primary search string ......................................... 289
Example: Defining additional criteria for job selection ........................ 303
Scan definitions for Message Output Facility (MOF) .......................... 305
Simulating the execution of scan definitions....................................... 306
NoError (Option A.R.4) ........................................................................... 308
Selecting NoError definitions .............................................................. 309
Specifying NoError completion codes ................................................ 312
Log processing (Option A.R.5) ............................................................... 315
Event actions (Option A.R.6) .................................................................. 318
Skeletons and variables...................................................................... 322
Event processing ................................................................................ 324
Standard events .................................................................................. 327
Large list monitoring and outlim processing ........................................... 331
Triggering e-mail via DD MAILOUT ........................................................ 339
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
259
Reader (Option A.R)
Class (Option A.R.1)
Class (Option A.R.1)
Under option A.R.1, define each sysout and reader class that is to be
processed by _beta log|z.
Overview
You also have to create one or more reader definitions under option A.R.2
in order for a class to be processed.
Class definition
Class definitions contain information on the sysout or reader classes to be
processed.
One class can be used for several reader definitions (under option A.R.2).
Note: JES sysout or reader classes for the message classes of jobs being
spooled into _beta log|z should be exclusively used for _beta log|z. Sysout
or reader classes processed by _beta log|z cannot be used for any other
purpose: these sysout classes can neither be printer classes nor can they
be processed by a z/OS external writer.
Navigation
From the "Primary Selection Menu", choose:
•
Option A.R.1
The "Reader Class Definition Selection" panel is displayed, in which
you can enter your selection criteria.
Insert Reader Class
Definition panel
PE92RD13 ---------------------------------------------------------------------Command ===> ________________________________________________________________
Insert Reader Class Definition
Sysout Class
Save Status
===> .
===> ......
A-Z, 0-9, + or :
(S)ave or (N)osave
Outlim Line Number
Outlim Spool Class
Outlim Hold Sysout
===> ..........
===> .
===> ......
0-2147483647
A-Z, 0-9
(H)old or (N)ohold
Class Processing Active
Class Processing Job Group
===> ....
===> ________
(Y)es or (N)o
Press ENTER key to insert this entry and continue.
Press END key to cancel changes or HELP key for help information.
Fields
Field
Description
Sysout Class
Enter a valid sysout class: A-Z, 0-9, : or +
_beta log|z uses the classes : (colon) and + (plus sign)
for data read in from other platforms. Definitions for the
sysout classes : and + are only necessary if class
processing is to be used. For more information on these
classes, see "Open Systems data" on page 263.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
260
Reader (Option A.R)
Class (Option A.R.1)
Field
Description
Save Status
Enter Save to archive all sysout lists and job records of
this class. Enter Nosave if you do not want to archive
sysout lists and job records of this class.
Additional information:
You can override this default status online using line
commands and in the JCL using OMS keywords.
If the class status is set to Nosave, a list will not be
archived. The sysout class definition has a higher
priority than a job group definition.
If two _beta log|z subsystems share the same database,
it is not possible to define a different Save status for a
sysout class that is processed by both systems. If one
definition specifies Save status=Save, this will be
honored by both subsystems.
Outlim Line Number
Specifies the maximum number of lines of sysout lists
that should be read in by the JES reader
Sysout lists that exceed the specified maximum are
requeued to JES according to the values specified in
Outlim Spool Class and Outlim Hold Sysout.
The default is 60.000.000 lines. 0 means that the default
will be used.
Further information on large lists and outlim
Outlim Spool Class
•
You can also make _beta log|z issue a warning
message when reading in large lists. For more
information on this and outlim processing in general,
see "Large list monitoring and outlim processing" on
page 331.
•
Outlim processing can also be handled by the user
exit B92UXOLM (see "B92UXOLM: Output limit exit"
in _beta log|z Installation and System Guide).
•
Outlim Line Number is not used by the OSY
reader (: and + class). The agent definition in _beta
log|z and _beta job|z can be used to define the
output limit for each individual agent (in MB).
Sysout lists affected by outlim processing are requeued
to JES to the sysout class specified here.
Note: The current _beta log|z system will not read in
requeued output, even if the specified class is defined in
the current _beta log|z system with attributes that would
normally cause the reading in of this list (outlim, hold,
etc.).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
261
Reader (Option A.R)
Class (Option A.R.1)
Field
Description
Outlim Hold Sysout
Sysout lists affected by outlim processing are requeued
to JES and allocated with the attribute specified here.
Enter Hold to hold the output, which may be released
for printing or deleted by an operator command.
Enter Nohold if you do not want to hold the output. If
the outlim spool class is defined as a Hold class in JES,
specifying Nohold here will have no effect.
Class Processing
Active
If job processing for this class should be affected by
sysout class attributes, enter Yes in this field and
specify the name of an existing job group in the Class
Processing Job Group field. For more information, see
"Sysout class processing" on page 121.
If you enter No, job processing is done according to the
job group to which a job belongs because of its name.
Class Processing Job
Group
Line commands
Enter the name of an existing job group if Class
Processing Active = Yes.
The following line commands are available in the "Reader Class Definition
Table":
S
Selects the reader class definition for display or update
I
Adds a new reader class definition (insert)
C
Adds a new reader class definition (copy)
D
Deletes the reader class definition
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
262
Reader (Option A.R)
Open Systems data
Class (Option A.R.1)
_beta log|z uses the following message classes for Open Systems data:
:
(colon) is used for data read in via _beta log|z rules
You can find this data under online option O.
+
(plus sign) is used for all other data read into _beta log|z from other
platforms, for example, logs of EJM jobs read-in from EJM agents
You can find this data under online option 1.
To be able to read in Open Systems data, one or more subsystem readers
must be started. The number of readers is specified in the No. of EDF
Subsys & OSY Readers field (Option A.S.2).
If you want to use class processing for Open Systems data, create a
definition for message class + or : and specify the name of the job group in
the class definition. For more information, see "Sysout class processing"
on page 121.
Note: You have to restart the _beta log|z reader for any of these definition
changes to take effect. To do this, use the console command
F stcname,RESTART READER. When using multi-image processing, you
have to do this for each z/OS image.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
263
Reader (Option A.R)
JES reader (Option A.R.2)
JES reader (Option A.R.2)
Overview
A JES reader definition determines which sysout class or classes are to be
processed by this reader. You can also specify selected SAPI parameters
to additionally limit the selection of lists to be read in by a reader.
JES reader name/ID
JES readers are identified by the reader name followed by a dot and the
2-digit JES reader ID, for example: B92P.08. The reader name is normally
identical with the subsystem ID (ssid). The reader name and the reader ID
are part of the reader definition.
Most JES reader messages (OMS96nnx) include information on the JES
reader where the message originated, for example:
OMS9612I B92P.08 PROCESSING AVM12500(J0871168)
OMS9604I JES READER B92P.08 IS WAITING FOR NEXT LIST
A reader can process up to 36 classes. Classes are defined under option
A.R.1. One class can be used in several reader definitions.
36 reader IDs for each reader name can be specified. 36 reader IDs per
one SSID can be used.
Note on JES reader optimization
You can improve performance by increasing the number of active JES
readers up to five. No significant performance improvements can be
expected when running more than five JES readers in parallel.
Navigation
From the "Primary Selection Menu", choose:
•
Option A.R.2
The "Reader Definition Selection" panel is displayed, in which you can
enter your selection criteria.
Insert Reader Definition
panel
PE92RD23 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Insert Reader Definition
Reader Name
Startup
Sysout Classes
===> B92P
Reader ID
===> ..
===> .......
(A)ctive or (D)ormant
===> ....................................
A-Z, 0-9
Additional Selection Criteria
Jobname
===> ________
Destination
===> ________
Node Name
===> ________
Minimum Lines
===> 0_________
Forms ===> ________
===> ________
Queue Selection:
Type Selection:
===> ________
===> ________
HLD ===> NO_
JOB ===> YES
Owner
Writer
===> ________
===> ________
Maximum Lines
===> 0_________
===> ________
===> ________
===> ________
===> ________
XWH ===> NO_
STC ===> YES
WTR ===> YES
TSU ===> YES
APPC ===> YES
Press ENTER key to insert this entry and continue.
Press END key to cancel changes or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
264
Reader (Option A.R)
Fields
JES reader (Option A.R.2)
Field
Description
Reader Name
The reader name identifies to which _beta log|z system
the reader belongs.
Enter the 4-character _beta log|z subsystem ID.
If you are defining a reader for a separate reader started
task, enter the reader name as specified in the parameter
B92_RDR (see "Separate reader started task").
Reader ID
2-digit JES reader ID which identifies the reader within
the _beta log|z subsystem
Startup
Determines whether the JES reader is automatically
started when the _beta log|z started task is started
Sysout Classes
A
Active (reader is automatically started with STC)
D
Dormant (reader has to started separately)
Sysout class(es) to be processed by this reader
You can specify up to 36 classes (A..Z and 0..9). You can
only specify classes that have been defined under
option A.R.1.
In the following fields you can specify additional selection criteria for the
JES subsystem interface SAPI to limit the jobs/lists that are processed by
this reader.
Most fields support masks with the following wildcards:
?
stands for any single character at this position
*
for any sequence of characters
Field
Description
Jobname
Job name or mask as filter (max. 8 characters)
Owner
Owner user ID or mask as filter (max. 8 characters)
Destination
Destination or mask as filter (max. 8 characters)
Writer
Writer name or mask as filter (max. 8 characters)
Node Name
Original 8-character node name from which the job was
submitted (No masks allowed!)
Minimum Lines/
Maximum Lines
Minimum/Maximum number of lines that a list must have
to be processed by this reader
0 means that there is no limit.
Forms
Up to 8 form numbers as filter (max. 8 characters each)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
265
Reader (Option A.R)
JES reader (Option A.R.2)
Queue Selection
Type Selection
Specify from which queues the JES reader is to select the
output by entering YES or NO in the corresponding field.
It is possible to select output from more than one queue.
HLD
JES2: YES selects Hold/Leave output
JES3: YES selects Hold for TSO
XWH
JES2: n/a
JES3: YES selects Hold for XWTR
WTR
JES2: YES selects WRITE/KEEP Output
JES3: YES selects output from the writer queue
Specify which output type the JES reader is to process by
entering YES or NO in the corresponding field. It is
possible to select more than one output type.
JOB
YES selects batch jobs (JOBs)
STC
YES select started tasks (STCs)
TSU
YES selects time sharing users (TSUs)
APPC YES selects APPC output
Line commands
The following line commands are available in the "Reader Definition
Table":
S
Selects the reader definition for display or update
I
Adds a new reader definition (insert)
C
Adds a new reader definition (copy)
D
Deletes the reader definition
Starting/Stopping a JES reader
The following line commands are available only for readers of the current
subsystem ID (protected via the function code 79):
R
Restarts the reader
F
Freezes (i.e. stops) the reader
To start, stop, and restart all of the _beta log|z readers or an individual
JES reader, you can also use console commands (see "Console
commands" in _beta log|z Installation and System Guide).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
266
Reader (Option A.R)
Primary commands
JES reader (Option A.R.2)
The following primary commands are available in the "Reader Definition
Table":
FIND
Searches in the table for the entered string
SORT
Sorts the table by different columns in ascending (A) or
descending (D) order
You can enter up to three column names in the SORT
command. The following column names are available in
the table: Name, ID, Startup, Classes, Jobname, Owner,
Destin, Writer, Node.
Example: SORT NAME,D ID,A STARTUP,A
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
267
Reader (Option A.R)
Scanning (Option A.R.3)
Scanning (Option A.R.3)
Overview
_beta log|z retrieves job information partly from the control blocks, partly
by scanning sysout.
Sysout scanning is controlled by so-called scan definitions (option A.R.3).
Each scan definition is identified by a unique number (scan ID).
Beta-defined scan
definitions
All scan definitions required by _beta log|z for sysout scanning are
automatically installed with the product.
These so-called Beta-defined scan definitions have a scan ID <= 9999.
You cannot modify or delete any scan definitions within this range, but you
can activate and deactivate these definitions.
For a list of the Beta-defined scan definitions, see "Scan definitions" on
page 539.
User-defined scan
definitions
In addition to the standard scanning parameters required by _beta log|z,
you can also add definitions with your own user-defined parameters for the
scanning of job lists and logs.
For example, you can search job logs for certain strings and place a job
onto the error queue or remove it from the error queue if the string is
found. Or you can scan job logs and sysout lists to retrieve additional
selection criteria for the "Job Select Table".
User-defined scan definitions have a scan ID >= 10000. User-defined scan
definitions can be changed as needed.
Note: The performance of the JES readers will go down as the number of
additional scanning parameters increases. For this reason, user-defined
scanning parameters should be used sparingly.
Target field IDs
The target field IDs are used to be able to scan for certain conditions and
to store the scanning result in the specified target field. Scan definitions for
most target field IDs are loaded into the database at installation time.
Target field IDs greater than or equal to 800 are used for scan definition
chains, i.e. for dependent scan processing.
For a list of the target field IDs, see "Target field IDs" on page 284.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
268
Reader (Option A.R)
Reader restart required
Scanning (Option A.R.3)
You have to restart the _beta log|z readers for any changes to the
scanning parameters to take effect.
When using multi-image processing, you have to restart the readers for
each z/OS image.
The following console command restarts the _beta log|z readers of a
system:
F stcname,RESTART READER
For more information on operator console commands, see "Console
commands" in _beta log|z Installation and System Guide.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
269
Reader (Option A.R)
Scanning (Option A.R.3)
Selecting scan definitions
1. Enter A.R.3 in the Primary Selection menu to display the "Scan
Definition Selection" panel:
Procedure
PE92SO01 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Scan Definition Selection
Job/Rule
===> *_______
DDName
===> *_______
Scan Group ===> ________
Stepname
Title
from Scan ID ===> __________
Category
===> ________
===> *_______ Procstep ===> *_______
===> *_______________________________
to Scan ID ===> __________
(H)ostJob, (F)ileRule, (S)APJob
Primary Search String
===> ________________________________
Secondary Search String ===> ________________________________
Target field ID
Chains only
User defined only
Test Status
Definition Status
===> *__
===> ___
===> ___
===> ___
===> _
Chain Name ===> ________
(Y)es, (N)o or blank
(Y)es, (N)o or blank
(Y)es, (N)o or blank
(A)ctive, (I)nactive or blank
Press ENTER key to display Scan Definitions.
Press END key to return to the previous menu.
2. Enter your selection criteria (see table of fields below the procedure)
and press ENTER.
The "Scan Definitions Table" displays the scan definitions matching
the selection criteria you specified (here: category Host job):
PE92SO10 -------------------------------------------------- Row
1 of
265
Command ===> ________________________________________________ Scroll ===> PAGE
Scan Definition Table
S - Select Scan Definition
I - Insert Scan Definition
A - Activate\Deactivate Scan Def.
D - Delete Scan Definition
C - Copy Scan Definition
T - Toggle Test Status of Scan Def.
Sel A T Title
Scan ID
ChainName EoC
Y N SCAN JOB NOT RUN IEFC452I
B01 0000001000
NO
Y N SCAN JOB FAILED IEF453I
B02 0000001001
NO
Y N SCAN JOB MESSAGE CLASS
B03 0000001002
NO
Y N SCAN STEPNAME WITH PROCSTEP B11 0000001003
NO
Y N SCAN STEPNAME WITHOUT PROCST B12 0000001004
NO
Y N SCAN PROCSTEPNAME
B13 0000001005
NO
Y N SCAN STEP CONDITION CODE
B14 0000001006
NO
Y N SCAN ALLOCATION ERRORS
B15 0000001007
NO
Y N SCAN DISK ALLOCATION ERRORS B16 0000001008
NO
Y N SCAN STEPNAME NOT RUN
B17 0000001009
NO
Y N SCAN STEPN NOT RUN W/O PSTEP B18 0000001010
NO
Y N SCAN PROCNAME NOT RUN
B19 0000001011
NO
Y N SCAN STEPTEXT NOT EXEC
B20 0000001012
NO
N N SCAN NOT CATALOGED 2
B21 0000001013
NO
FldID EvtID
74
75
25
11
11
12
14
30
30
11
11
12
13
30
3. Press PF11 to display the right columns of the table (PF10/PF11 to
scroll to the left/right): Job/Rule, Stepname, Procstep, DDName.
The columns of the "Scan Definitions Table" are described below the
procedure.
Fields
Field
Description
Job/Rule
Enter the name of a host job or the name of a file or SAP
rule, or use a mask.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
270
Reader (Option A.R)
Scanning (Option A.R.3)
Field
Description
Stepname
Enter a step name or a mask.
Procstep
Enter a procstep name or a mask.
DDName
Enter the DD name which is to be used on the job card or
a mask.
Title
Enter a scan definition title or a mask.
Scan group
Enter a name of a scan group or a mask.
from/to Scan ID
Enter the first / last scan ID of the range you want to
display. Or enter the numeric unique scan ID of a scan
definition in both fields to display only the scan definition
with the specified ID.
Category
Enter H for host job, F for file rule, or S for SAP job. Then
only scan definitions of this scan definition type will be
displayed. If you leave the field blank, all kinds of scan
definitions will be displayed.
Primary Search String Enter a search string or a mask to display scan definitions
containing the specified primary search argument. The
entry in this field is case-sensitive.
Secondary Search
String
Enter a search string or a mask to display scan definitions
containing the specified secondary search argument. The
entry in this field is case-sensitive.
Target field ID
The target field ID identifies the field that is updated if the
scanned line fulfills the search criteria. For a list of target
field IDs, see "Target field IDs" on page 284.
Chain Name
Enter a chain name used for dependent scan definitions
or enter a mask.
Chains only
Enter Yes to display only scan definition chains, enter No
to display only scan definitions without chains. Or leave
this field blank to display both kinds of scan definitions.
User defined only
Enter Yes to display only user-defined scan definitions,
enter No to display only Beta-defined scan definitions. Or
leave this field blank to display both kinds of scan
definitions.
Test Status
Enter Yes to display only scan definitions in test status,
enter No to display only scan definitions without the test
status. If you leave the field blank, all scan definitions
regardless of their status will be selected.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
271
Reader (Option A.R)
Columns
Scanning (Option A.R.3)
Field
Description
Definition status
Enter A to display only active scan definitions.
Enter I to display only inactive scan definitions.
Leave blank to display active and inactive scan
definitions.
Column
Description
A
If Y is displayed in this column, the scan definition is
active.
If N is displayed in this column, the scan definition is not
active.
T
If Y is displayed in this column, the scan definition is in
test status.
If N is displayed in this column, the scan definition test
status is not set.
Title
The title gives a short description of the scan definition.
The number in the last column specifies the following:
Bxx = can be used for JES2 or JES3, 2xx = JES2, 3xx =
JES3, Exx = EDF, Sxx = Syslog
Scan ID
The scan ID contains the unique numeric ID of this scan
definition.
Note: Scan definitions with a scan ID less than 10000
are Beta-defined definitions that cannot be changed.
Chain Name
This field shows the name of chain or a group of
dependent scan definitions.
EoC (End of Chain)
This field displays for dependent scan definitions
whether the scan definition is the last in a scan definition
chain. For normal (standalone) scan definitions, the field
is set to No, which is the default.
FldID
This field displays the field ID which is to be updated.
EvtID
The numeric event ID used by the scan definition to
identify an event is displayed. The event ID can be used
to assign an action to an event. More information can be
found in "Event actions (Option A.R.6)" on page 318.
Job/Rule
Stepname
Procstep
DDName
These columns display what you previously defined as
the selection criteria. The entries define which sysout
lists are to be scanned for the strings specified in the
scan definition.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
272
Reader (Option A.R)
Line commands
Scanning (Option A.R.3)
S
Selects the scan definition for display or update
I
Adds a new scan definition (insert)
A
Activates the scan definition when it is inactive;
Deactivates the scan definition when it is active
D
Deletes the scan definition
C
Adds a new scan definition (copy)
T
Toggles, i.e. sets or resets, the scan definition in test status
In the column T, Y will be displayed for a scan definition in test
status.
To start a scan definition test, use the line command T in the "Job
Information Table", in the "File Rule Information Table", in the
"SAP Job Information Table", or in the "Syslog Information Table".
For more information, see "Simulating the execution of scan
definitions" on page 306.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
273
Reader (Option A.R)
Scanning (Option A.R.3)
Defining scan definitions
Procedure
1. To define new scan definitions, enter the line command I or C in the
Scan Definitions table.
This will display the first "Insert Scan Definition" panel:
PE92SO11 ---------------------------------------------------------- Page 1 of 5
Command ===> _________________________________________________________________
Insert Scan Definition
Scan ID
===> 0000010024
Job/Rule
===> ........ Stepname
DDName
===> ........ Title
Scan Group ===> ________
Category ===> ........
===> ........ Procstep ===> ........
===> ________________________________
(* for list)
Primary Search Arguments (case-sensitive)
String
===> ................................
Search Primary String
between lines
===> 0____
at word position
===> 0_
or between columns
===> 1__
Secondary String
Processing Condition
===> NO.
===> NO.
and ===> 0____
plus ===> 0_
and ===> 80_
Length
===> ..
characters
(Y)es or (N)o
(Y)es or (N)o
Press ENTER or DOWN key to proceed inserting this entry.
Press END key to cancel changes or HELP key for help information.
2. In the first scan definition panel, define the following:
•
Which sysout lists are to be scanned (job or rule name, category,
step name, procstep, DD name)?
•
What is the search string?
•
At which position in the line should the search string occur?
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
274
Reader (Option A.R)
Scanning (Option A.R.3)
•
Specify between which lines the character string is to be searched
in the list (Search Primary String between lines). With this
parameter you can limit the search.
•
Do you want to use a secondary search string?
Note: The search is case-sensitive.
If you want to use a secondary search string, enter Yes in the field
Secondary String. Then the second scan definition panel will be
displayed.
•
Do you want to use a processing condition?
If so, enter Yes in the field Processing Condition. Then the third
scan definition panel will be displayed
Provided that Yes has been entered in the field Secondary String,
the second "Insert Scan Definition" panel is displayed when you press
ENTER:
PE92SO12 ---------------------------------------------------------- Page 2 of 5
Command ===> _________________________________________________________________
Insert Scan Definition
Scan ID
Job/Rule
DDName
Scan Group
: 0000010024
: ERGJOB1
Stepname
: *
Title
:
: *
:
Category
Procstep
: FILERULE
: *
Secondary Search Arguments (case-sensitive)
String
===> ................................
Length
===> ..
Negate Result
===> NO.
(Y)es or (N)o
Search Secondary String
between lines
===> 0____
at word position
===> 0_
or between columns
===> 1__
and ===> 0____
plus ===> 0_
and ===> 80_
characters
Press ENTER or UP or DOWN key to proceed inserting this entry.
Press END key to cancel changes or HELP key for help information.
3. In the second panel, define the following:
•
What is the second search string?
•
Must it be present or absent in the line containing the first string?
•
At which position in the line should the string be searched?
•
Specify between which lines the character string is to be searched
in the list (Search Primary String between lines). With this
parameter you can limit the search.
Note: This panel is skipped if you don't define a second search
string.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
275
Reader (Option A.R)
Scanning (Option A.R.3)
Provided that Yes has been entered in the field Processing
Condition in the first scan definition panel, the third "Insert Scan
Definition" panel is displayed when you press ENTER:
PE92SO17 ---------------------------------------------------------- Page 3 of 5
Command ===> _________________________________________________________________
Insert Scan Definition
Scan ID
: 0000010024
Processing Condition
Comparison Type
Title :
(Extract only if this condition is true)
===> .......
(S)tring or (I)nteger
Position of Reference Value
Relative to string
at word position
or at column
===> 0
===> 0_
===> 0__
plus
Comparison Length
===> 0.
or
Comparison Values
Value 1 ===> ................................
Value 2 ===> ________________________________
===> 0_ characters
until ===> _
found
Operator ===> .. (e.g. EQ)
Operator ===> __ (e.g. EQ)
Press ENTER or UP or DOWN key to proceed inserting this entry.
Press END key to cancel changes or HELP key for help information.
4. In the third panel, define the following:
•
the comparison type
•
the position of the reference value
•
the comparison length and the comparison values with operators
PE92SO13 ---------------------------------------------------------- Page 4 of 5
Command ===> _________________________________________________________________
Insert Scan Definition
Scan ID
: 0000010024
Title :
Extraction Arguments
Field ID to be updated
String to be returned
===> ... : Unknown code
===> ________________
Extract string length
Data Type
Relative to String
at word position
or at column
===> ....
===> _____
===> 0
===> 0_
===> 0__
or until ===> _
found
Date Mask ===> __________
Event Processing Parameters
Event ID
Table Name
===> _____
===> ________
Severity
===> _ (I/W/E)
Field Name ===> ________
plus
===> 0_ characters
Press ENTER or UP or DOWN key to proceed inserting this entry.
Press END key to cancel changes or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
276
Reader (Option A.R)
Scanning (Option A.R.3)
5. In the fourth "Insert Scan Definition" panel, define what to do when
search strings are found, namely, which field pertaining to the scanned
job should be updated (target field ID). You can also define here that
the scan definition is part of a chain.
•
To define the extraction arguments, first specify the field to be
updated, i.e. the target field ID.
•
To define a scan definition chain that is not used to update a field,
specify 800 as the target field ID, and set the length and position
field to 0.
•
To update a field with a string extracted from the scanned line,
specify the position and length of the string and define the field to
be updated.
•
To update a field with a fixed string, enter the string and define the
field to be updated.
•
To define a scan definition chain that is to update a field, specify
the position of the string to be returned or the fixed string to be
returned.
•
Determine the data type to be extracted. Valid data types are
DATE and TIME. If you have specified DATE, you must enter a
valid date mask.
•
In addition, you can define event parameters, such as the event
ID, the event table name and field, and the severity. For a
description of all fields, see the table of fields below.
PE92SO14 ---------------------------------------------------------- Page 5 of 5
Command ===> _________________________________________________________________
Update Scan Definition
Last update: AVSCHM1
Scan ID
Title :
: 0000010022
Chain Arguments
Chain Name
===>
Next Scan ID to be activated ===> 0
End of Chain
===> NO
04/29/08
16:04:06
(Y)es or (N)o
Field ID to be updated
Output offset
===> 000
===> 000
: Unknown code
Temporary disabled
Report unmatched
Blank Removal
===> NO
===> NO
===> NO
(Y)es or (N)o
(Y)es or (N)o
(Y)es or (N)o
Press ENTER to proceed updating this record or UP key for previous page.
Press END key to cancel changes or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
277
Reader (Option A.R)
Scanning (Option A.R.3)
6. In the fifth panel, "Update Scan Definition", define the following:
•
parameters for scan definition chains, such as chain name, next
scan ID to be activated, end of chain
•
the field which is to be updated
•
the position of the string which is to be returned within the output
field and
•
several fields used for scan definition chains, such as "Temporary
disabled", "Report unmatched", "Blank Removal". For a
description of all fields, see the table of fields below.
Note: This panel is skipped if you do not define a scan definition chain
which is characterized by 800 in the field Target field ID. Also see the
panel "Update Scan Definition (5)" in "Example: Defining a primary
search string" on page 289 for detailed information.
Fields (Page 1)
Field
Description
Scan ID
A new scan ID is automatically suggested. Enter another
numeric unique scan ID used for the scan definition, if
applicable.
Category
Enter H for host job, F for file rule, or S for SAP job. Then
this scan definition type will be used.
Job/Rule
Enter the name of a host job or the name of a file or SAP
rule.
Stepname
Enter a step name.
Procstep
Enter a procstep name.
DDName
Enter the DD name which is to be used on the job card.
Title
Enter a scan definition title.
Group
Enter a scan group name or * to select a group from the
displayed scan group list.
Primary Search
Arguments (casesensitive): String
Enter the string to be searched for when lists and logs are
scanned.
Length
Specify the length of the primary search string.
Specify between which lines, columns, or at which word
Search Primary
String between lines, position the search string must occur in the list. Set both
at word position, or fields to 0 to scan all lines of a list.
between columns
Secondary String
Enter Yes to extend the search. A secondary search panel
will be displayed. When No is entered, no secondary
search string can be defined.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
278
Reader (Option A.R)
Fields (Page 2)
Scanning (Option A.R.3)
Field
Description
Processing
Condition
Enter Yes to define a condition for the processing of the
scan result in the additionally displayed panel. When No is
entered, no additional condition can be defined.
Field
Description
Scan ID, Category,
Job/Rule,
Stepname,
Procstep, DDName,
Title, Group
These fields display what has been specified in the first
scan definition panel.
Secondary Search
Arguments (casesensitive): String
Enter the secondary string to be searched for when lists
and logs are scanned.
Length
Specify the length of the secondary search string.
Negate Result
Enter Yes if the secondary search string must be absent
from the line containing the primary search string. Enter No
if the secondary search string must be present in the line
containing the primary search string.
Specify between which lines, columns, or at which word
Search Secondary
String between lines, position the secondary search string must occur in the list.
at word position, or Set both fields to 0 to scan all lines of a list.
between columns
Fields (Page 3)
Field
Description
Scan ID, Title
These fields display what has been specified in the first
scan definition panel.
Processing
Condition (Extract
only if this condition
is true): Comparison
Type
Enter the data type which is to be used for a comparison.
Use the type String to compare alphabetic or numeric
strings, or strings which contain other characters. Specify
the type Integer to perform numeric comparisons with
whole numbers.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
279
Reader (Option A.R)
Scanning (Option A.R.3)
Field
Description
Position of
Reference Value:
Relative to string,
at word position,
or at column
Specify an absolute or a relative position for the reference
value. For a relative position, specify the position of the
reference value relative to the primary or secondary search
string. Specify to which search string the reference value is
to be related:
0 - for the definition of an absolute position,
1 - for a position relative to the primary search string, or 2 for a position relative to the secondary search string.
Specify the word position of the reference value within the
scanned line. If you want to define the position by the
column number, enter 0.
You can move the position at which the reference value is
located n characters to the right from the beginning of the
word.
Specify the column number at which the reference value
begins. If you want to define the position by the word
position, enter 0.
Note: Enter the position either absolute -counted from the
beginning of the line - or relative -counted from the
beginning of the search string.
Comparison Length
Specify the length which is to be used for the comparison. If
you enter 0,the length will be determined by the stop
character specified in field or until <x> found.
or until x found
Instead of defining a length, you can define a stop
character to compare from the specified position of the
reference value up to this stop character. Then the
specified comparison length will be ignored. The stop
character can be any character or number.
Comparison Values: Enter any value with which the reference value is to be
compared. Up to two values can be entered. Next specify
Value 1/Operator
the kind of comparison operation that is to be performed.
Value 2/Operator
Available comparison operators are:
EQ (equal to: ==), NE (not equal to: !=), LT (less than: <),
LE (less than OR equal to: <=), GT (greater than: >), GE
(greater than OR equal to: >=).
Note: Two conditions are connected by a logical AND.
Fields (Page 4)
Field
Description
Scan ID, Title
These fields display what has been specified in the first
scan definition panel.
Extraction
Arguments:
Field ID to be
updated
Enter the target field ID for the field that is to be updated.
You can press PF1 in the panel to display the complete list
of available target field IDs or see "Target field IDs" on
page 284.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
280
Reader (Option A.R)
Scanning (Option A.R.3)
Field
Description
String to be returned Specify a string of max. 16 characters if you want a fixed
string to be written to the specified target field.
Leave this field blank if a string extracted from the scanned
line is to be returned. You have to specify the position and
length of this string in the following fields.
Extract string length
Specify the length of the string which is to be extracted
from the scanned line; you can enter one of the following:
n
The specified number of characters will be extracted at
the specified position.
0
The whole word at the specified position will be
extracted.
+n The whole word plus n characters to the right will be
extracted.
-n The whole word minus n characters will be extracted.
The word will be truncated by the specified number of
characters.
The value specified in this required field will be ignored if
you specify a stop character in the next field.
or until x found
Specify a stop character if the string is to be extracted at
the specified position up to this stop character.
The stop character itself is not included in the extracted
string. The stop character can be any character or number.
Data Type
Specify DATE or TIME to extract a date or time value.
Otherwise leave the field empty.
Valid date masks (must be specified in Date Mask field):
MM/DD/YYYY or MM/DD/YYYY
DD/MM/YYYY or DD/MM/YY
DD.MM.YYYY or DD.MM.YY
YYYY.DDD or YY.DDD
YYYYMMDD or YYMMDD
YYYY-MM-DD
Valid time masks:
hh:mm:ss:ff or hh:mm:ss or hh:mm
hhmmss or hhmmss
Date Mask
Specify the date mask if the data type is DATE. Otherwise
leave the field empty.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
281
Reader (Option A.R)
Scanning (Option A.R.3)
Field
Description
Relative to String,
at word position,
or at column
You can define whether the string to be returned begins at
an absolute or at a relative position. For a relative position,
specify the position of the reference value relative to the
primary or secondary search string. Specify to which
search string the reference value is to be related:
0 - for the definition of an absolute position,
1 - for a position relative to the primary search string, or 2 for a position relative to the secondary search string.
Specify the absolute or relative word position of the string
to be returned within the scanned line. If you want to define
the position by the column number, enter 0 here.
You can move the position at which the return string is
extracted n characters to the right from the beginning of the
word. For an example of extracting at word position, press
PF1 in the fourth scan definition panel.
Specify the column at which the string to be extracted
begins. Enter the column position either absolute - counted
from the beginning of the line - or relative - counted from
the beginning of the search string. If you want to define the
position by the word position, enter 0 here.
Event Processing
Parameters
The following fields are only used if you define a scan
definition for event processing with the target field ID 550.
Event ID
Enter a numeric ID to identify an event. You can use this
event ID subsequently to assign an action to this event
(under option A.R.6).
Enter the event ID 0 when no event is to be triggered by the
scan definition. For more information, see the definition of
event actions (see page 318).
Note: The event IDs 9000 - 9999 are internally used by
_beta log|z for default events. Do not use these numbers in
your own user-defined scan definitions.
Severity
Specify the severity of the event: I for informational, W for
warning, or E for error.
Table Name
Enter the name of a database event table. The scan result
will be saved in this table. For more information, see
"Displaying tables (Option A.D.2.1)" on page 363.
Field Name
Enter the name of a database event field. The scan result
will be saved in this field. For more information, see the
database fields (see page 370).
To store event information in more than one event field, use
a scan definition chain (target field ID 800) in combination
with events (target field ID 550).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
282
Reader (Option A.R)
Fields (Page 5)
Scanning (Option A.R.3)
Field
Description
Scan ID, Title
These fields display what has been specified in the first
scan definition panel.
Chain Arguments:
Chain Name
Enter a chain name for a set of dependent scan definitions.
A chain consists of a number of scan definitions which
depend on each other and which are activated one after the
other.
Next Scan ID to be
activated
Specify the scan ID of the next scan definition in the chain.
The scan definition is activated after the current scan
definition.
End of Chain
Enter Yes to indicate the end of the chain which means that
the processing for the specified target field ID should take
place now.
Enter No to indicate that the scan result is to be used later
on in a subsequent scan definition.
Field ID to be
updated
Specify the target field which is to be updated by this chain
scan definition. You can press PF1 in the panel to display
the complete list of available target field IDs or see "Target
field IDs" on page 284.
Output offset
Enter the start column at which the scanned string is to
appear in the output line. With this field you can combine
the results of two or more scan definitions in one output
line.
Example: The first scan definition of a chain extracts the
text "This is". The output offset field is set to 0. A second
scan definition extracts the text "an example" and writes it
at offset 8. The result in the target field is "This is an
example".
Temporary disabled
Enter Yes to define a "sleeping" scan definition which is by
default disabled but will be activated by another scan
definition of that chain. Note: The first scan definition in a
chain must always be defined with No.
Report unmatched
Enter Yes to write a text in the specified target field if a
scan definition does not match. You can define the text in
the field String to be returned on the fourth page of the
scan definition.
Blank Removal
Enter Yes to remove all blanks from the extracted string.
The default is No.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
283
Reader (Option A.R)
Scanning (Option A.R.3)
Target field IDs
Overview
Target field IDs identify database record fields where scanned values are
stored.
The target field ID is specified in the scan definition in the Field ID to be
updated field.
The table below shows a list of the target field IDs with a short description.
For an illustration where this information is shown in job-related panels,
see:
Target field IDs
•
"Target field IDs for the Job Select Table" on page 287
•
"Target field IDs for the Job Information Table" on page 288
Target field ID
Description
1
Job start date
2
Job start time
3
Job end date
4
Job end time
5
Job highest condition code
6
Job owner user ID
7
Job net ID
8
*OMS RETPD=card value
9
*OMS HICC=card value
10
Job execution class
11
Step record step name
12
Step record procstep name
13
Step record error text
14
Step record step condition code
15
Step record system abend code
16
Step record user abend code
17
Step record CPU time minutes
18
Step record CPU time seconds
19
Step record SRB time minutes
20
Step record SRB time seconds
21
Step record private memory
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
284
Reader (Option A.R)
Scanning (Option A.R.3)
Target field ID
Description
22
Step record high private memory
23
Step record extended memory
24
Step record high extended memory
25
Job message class
26
Job system name
27
Job error text
28
Set/reset job error status
29
Set/reset job init error status
30
Insert a job message record (JMR)
31
Insert an extended select record
32
Job start date and time (YYDDD.HHMM)
33
Job end date and time (YYDDD.HHMM)
34
Job JES3 group ID
35
Job JES3 system ID
36
Job CPU time minutes
37
Job CPU time seconds
38
Ignore this step error
39
Reset job in error at list end
40
Reset job in error immediately
41
Force job status to NOERROR
42
Set job error text & status
43
DD name
50
Write text to B92EVENT
51
Write text with time to B92EVENT
52
Write scanned date to buffer
53
Write scanned time to buffer
70
Set job NOSAVE status
71
Set job SAVE status
72
Set job RETPD card there
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
285
Reader (Option A.R)
Scanning (Option A.R.3)
Target field ID
Description
74
Set JCL INIT error status
75
Set JCL FAIL error status
101
Notify user ID (internal use)
120
Syslog: Set job name SYSL (smfid)
121
Syslog: Set DD name
122
Syslog: Set submit date, set submit time to 00:00
123
Syslog: Set step name
163
Job ID
164
Job submit date
165
Job submit time
166
Job name
167
Long host name
168
Long job name
169
Long user name
180
LAF: Job name
196
Numeric dataset ID (max. 8 digits)
IDs must be unique per each job. Duplicate IDs are
automatically corrected during reader processing.
200-249
MOF: Write informational message to JESMSGLG
300-349
MOF: Write warning message to JESMSGLG
400-449
MOF: Write error message to JESMSGLG
500-531
JBRE user fields 01 - 32
550
Write event record at list end
551
Write event record immediately
800
Scan definition chain (for dependent scan processing)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
286
Reader (Option A.R)
Target field IDs for the
Job Select Table
Scanning (Option A.R.3)
The following panels illustrate which target field ID corresponds to which
column of the "Job Select Table". For example, ID6 in the User column
shows that the job owner user corresponds to the target field ID 6.
PE92BR10 ------------------------------------------------ Row
1 of
5
Command ===> ________________________________________________ Scroll ===> PAGE
Job Select Table
S,? - Select a job
P,M - Print/Mail a job
I - Reset input queue
N - Change user notes
Sorted by Submit date and time D
Displayed End date and time
W - Toggle work queue
K - Toggle keep status
T - Toggle non-retain
X - Toggle nokeep status
B - Browse all sysouts
J - Browse JES ysouts
R - Reload offline lists E - Toggle error queue
Sel Jobname
Job ID
Date
Time
Status
Error
User
Jobgroup
QOTEST01 JOB07575 ID1/ID3
ID2/ID3 R E
+ ID75
ID6
STANDARD
QOTEST01 JOB07570 (depends on the
R E
+ ID74
AV1
STANDARD
QOTEST01 JOB07568 selected display
I E
+ ID15
AV1
STANDARD
QOTEST01 JOB07555 field)
R E
+ CC 008
AV1
STANDARD
QOTEST01 JOB07531
I E
+ CC 008
AV1
STANDARD
******************************** BOTTOM OF DATA ********************************
Additional information by pressing PF11:
PE92BR10 ------------------------------------------------ Row
1 of
5
Command ===> ________________________________________________ Scroll ===> PAGE
Job Select Table
S,? - Select a job
P,M - Print/Mail a job
I - Reset input queue
N - Change user notes
Sorted by Submit date and time D
Displayed End date and time
W - Toggle work queue
K - Toggle keep status
T - Toggle non-retain
X - Toggle nokeep status
B - Browse all sysouts
J - Browse JES ysouts
R - Reload offline lists E - Toggle error queue
Sel Jobname
Runtime
Rdr-Date Rdr-Time Net ID Class
Msgcl System
QOTEST01 0000:00:03 05/19/2017 09:19:08 ID7
A
ID25 ID26
QOTEST01 0000:00:00 05/19/2017 09:18:17
A
N
QOTEST01 0000:00:01 05/19/2017 08:42:55
A
N
BETA
QOTEST01 0000:00:02 05/19/2017 08:18:17
A
N
QOTEST01 0000:00:01 05/19/2017 08:12:10
A
N
******************************** BOTTOM OF DATA ********************************
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
287
Reader (Option A.R)
Target field IDs for the
Job Information Table
Scanning (Option A.R.3)
The following panels illustrate which target field ID corresponds to which
field or column of the "Job Information Table". For example, ID11 in the
Stepname column shows that the step name corresponds to the target
field ID 11.
PE92BR20 -------------------------------------------------- Row
1 of
13
Command ===> ________________________________________________ Scroll ===> PAGE
Job Information Table QOTEST01 (JOB07575)
Submitted 05/19/2008 at 10:47:09 by AV1
Started
ID1/ID32
at ID2
in class A on system ID26
Ended
ID3/ID33
at ID4
with ID75
Position:
N - Note
M - Message
S - Step
L - List
S - Browse a list
K - Toggle keep status
V - View a list
X - Toggle nokeep status
B - Browse spinned list A - Toggle re-archive
X - Ext.Info
O - IWS
P,M - Print/Mail a list
R,U - Reload a list
T - Call Scan Test
Message
//*OMS
ID30
S4 PROC1 ID30
------------------------------------------------------------------------------Sel Stepname Procstep Errortxt CC
CPU-Time
SRB-Time Private High Prv
ID11
ID12
ID27
ID15 ID17:ID18 ID19:ID20
ID21 K
ID22 K
PROC1
S2
ID14
0:00.01
0:00.00
12 K
284 K
PROC1
S3
ID13
0:00.00
0:00.00
0 K
0 K
PROC1
S4
0:00.00
0:00.00
0 K
0 K
Additional information by pressing PF8:
PE92BR20 -------------------------------------------------- Row
1 of
13
Command ===> ________________________________________________ Scroll ===> PAGE
Job Information Table QOTEST01 (JOB07575)
Submitted 05/19/2008 at 10:47:09 by AV1
Started
ID1/ID32
at ID2
in class A on system ID26
Ended
ID3/ID33
at ID4
with ID75
Position:
N - Note
M - Message
S - Step
L - List
S - Browse a list
K - Toggle keep status
V - View a list
X - Toggle nokeep status
B - Browse spinned list A - Toggle re-archive
X - Ext.Info
O - IWS
P,M - Print/Mail a list
R,U - Reload a list
T - Call Scan Test
Message
//*OMS
ID30
S4 PROC1 ID30
------------------------------------------------------------------------------Sel Row DDName Stepname Procstep Pages
Lines Class Form
Arch Status
1 JESMSGLG JES2
1
25 ID25 STD
PEND ONLINE
2 JESJCL
JES2
1
26
N
STD
PEND ONLINE
3 JESYSMSG JES2
1
24
N
STD
PEND ONLINE
******************************** BOTTOM OF DATA *******************************
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
288
Reader (Option A.R)
Scanning (Option A.R.3)
Example: Defining a primary search string
Panel Update Scan
Definition (Page 1)
On page 1 of the "Update Scan Definition" panel define the following:
•
Which sysout lists are to be scanned (job name, category, step name,
procstep, DD name)?
•
What is the search string?
•
At which position in the line should the search string occur?
PE92SO11 ---------------------------------------------------------- Page 1 of 5
Command ===> _________________________________________________________________
Update Scan Definition
Last update: BETAINST 08/12/2002 12:00:00
Scan ID
: 0000001061
Job/Rule
===> *....... Stepname
DDName
===> JESYSMSG Title
Scan Group ===> ________
Category ===> HOSTJOB.
===> *....... Procstep ===> *.......
===> SCAN DUPLICATE
DSN
B69
(* for list)
Primary Search Arguments (case-sensitive)
String
===> DATA SET........................
Search Primary String
between lines
===> 0____
at word position
===> 0_
or between columns
===> 1__
Secondary String
Processing Condition
===> NO.
===> NO.
and ===> 0____
plus ===> 0_
and ===> 20_
Length
===> 8.
characters
(Y)es or (N)o
(Y)es or (N)o
Press ENTER or DOWN key to proceed updating this entry.
Press END key to cancel changes or HELP key for help information.
Which sysout lists are to be scanned?
In the upper part of the panel, define which sysout lists are to be scanned
(scan ID, category, job name, step name, procstep, DD name). Title gives
a short description of the scan definition.
The field Scan ID displays the unique numeric ID used for this scan
definition. Scan definitions with a scan ID less than 10000 are Betadefined definitions and cannot be changed by the customer. See also
"Selecting scan definitions" on page 270.
What is the search string?
In the center part of the panel (Primary Search Arguments), define the
search string (max. 32 characters) and the length of the string.
Note: The search is case-sensitive. Observe uppercase and lowercase
when entering the search string.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
289
Reader (Option A.R)
Scanning (Option A.R.3)
At which position in the line should the search string occur?
In the lower part of the panel (Search Primary String), define the position
of the string within the line. You can delimit the position by specifying a
start and ending column or by specifying that the string must occur in the
nth word (plus an optional number of characters to the right of this word).
Field
Description
between lines
Enter the line numbers between the string is to be
occur.
at word position
Enter a number n if the string must occur in the nth word
in the line. Enter 0 (zero) to define the location by start
and ending column.
Note: For _beta log|z scan definitions, a word is a string
of one or more alphanumeric characters delimited by
two blanks, beginning of line and blank, or blank and
end of line.
plus
Enter a number to define a position within the word or to
the right of the specified word position. Define the
position in relation to the beginning of the specified
word. Enter 0 (zero) if the search string occurs
anywhere within the nth word.
between columns
Enter the start and ending column to delimit the location
within the line by column number.
Example 1
To scan for string IEF251I anywhere within a line of 80 characters:
•
string = IEF251I
•
length = 7
•
at word position 0 plus 0
•
between columns 1 and 80
Example 2
To scan for string IEF251I at the exact word position in line:
hh.mm.ss JOBnnnnn
IEF251I jobname
•
string = IEF251I
•
length = 7
•
at word position 3 plus 0
•
between columns 0 and 0
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
JOB CANCELLED
290
Reader (Option A.R)
Scanning (Option A.R.3)
Example 3
To scan for string 251I at an exact position within the 3rd word of lines:
hh.mm.ss JOBnnnnn
hh.mm.ss JOBnnnnn
IEF251I jobname
IMG251I jobname
•
string = 251I
•
length = 4
•
at word position 3 plus 3
•
between columns 0 and 0
JOB CANCELLED
JOB CANCELLED
Defining the secondary search string
If you don't want to define a secondary search string, enter Secondary
string=No in panel "Update Scan Definition (1)". In this case, the next
panel in the sequence is "Update Scan Definition (4)".
To define a secondary search string, enter Secondary string=Yes in
panel "Update Scan Definition (Page 1)". This will display panel "Update
Scan Definition (Page 2)", where you define the following:
•
What is the second search string?
•
Must it be present or absent in the line containing the first string?
•
At which position in the line should the string be searched?
Defining a processing condition
If you don't want to define a processing condition, enter Processing
Condition=No in panel "Update Scan Definition (Page 1)". In this case,
the next panel in the sequence is "Update Scan Definition (Page 4)".
To define a processing condition, enter Processing Condition=Yes in
panel "Update Scan Definition (Page 1)". This will display panel "Update
Scan Definition (Page 3)", where you define the following:
•
What is used as the comparison type?
•
At which position is the reference value?
•
What are the comparison length and the comparison values with its
operators?
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
291
Reader (Option A.R)
Scanning (Option A.R.3)
Panel Update Scan
Definition (Page 2)
PE92SO12 ---------------------------------------------------------- Page 2 of 5
Command ===> _________________________________________________________________
Update Scan Definition
Scan ID
Job/Rule
DDName
Scan Group
: 0000001061
: *
Stepname
: JESYSMSG Title
:
Last update: BETAINST 08/12/2002 12:00:00
Category
: *
Procstep
: SCAN DUPLICATE
DSN
: HOSTJOB
: *
B69
Secondary Search Arguments (case-sensitive)
String
===> ................................
Length
===> 0.
Negate Result
===> NO.
(Y)es or (N)o
Search Secondary String
between lines
===> 0____
at word position
===> 0_
or between columns
===> 0__
and ===> 0____
plus ===> 0_
and ===> 0__
characters
Press ENTER or UP or DOWN key to proceed updating this entry.
Press END key to cancel changes or HELP key for help information.
The upper part of the panel displays which sysout lists are to be scanned
(scan ID, job/rule name, category, step name, procstep, DD name) and the
title of the scan definition.
•
What is the second search string?
See the description of the primary search string above.
Must it be present or absent in the line containing the first string?
Define Negate Result=No if the string must also be present in the line
containing the first string.
Define Negate Result=Yes if the string must be absent from the line
containing the first string.
At which position in the line should the string be searched?
See the description of the primary search string above.
Example
To find lines containing the message identifier ABC123I and the string
UNIT OFFLINE in lines:
hh.mm.ss JOBnnnnn
hh.mm.ss JOBnnnnn
hh.mm.ss JOBnnnnn
ABC123I jobname
ABC123I jobname
ABC123I jobname
UNIT OFFLINE
UNIT ONLINE
UNIT UNAVAILABLE
-
String = ABC123I
Length = 7
-
at word position 3 plus 0
between columns 0 and 0
Secondary string = Yes
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
292
Reader (Option A.R)
Scanning (Option A.R.3)
-
String = OFFLINE
Length = 7
-
Negate Result = No
-
at word position 6 plus 0
between columns 0 and 0
If the scan definition is to cover both error conditions UNIT OFFLINE and
UNIT UNAVAILABLE, define that string ONLINE must be absent from the
scanned line. To do this, define the following secondary search string:
-
String = ONLINE
Length = 6
-
Negate Result = Yes
-
at word position 6 plus 0
between columns 0 and 0
Updating a field with fixed string or extracted string
In the third panel, define what to do in case of a search hit.
Panel Update Scan
Definition (Page 3)
•
Which field of the scanned job should be updated?
•
Should it be updated with a fixed string or with a string extracted from
the scanned line?
•
If extracted string, should it be extracted at a fixed position or at a
position relative to one of the search strings?
PE92SO17 ---------------------------------------------------------- Page 3 of 5
Command ===> _________________________________________________________________
Update Scan Definition
Last update: BETAINST 08/12/2002 12:00:00
Scan ID
Title : SCAN DUPLICATE
: 0000001061
Processing Condition
Comparison Type
DSN
B69
(Extract only if this condition is true)
===> .......
(S)tring or (I)nteger
Position of Reference Value
Relative to string
at word position
or at column
===> 0
===> 0_
===> 0__
plus
Comparison Length
===> 0.
or
Comparison Values
Value 1 ===> ................................
Value 2 ===> ________________________________
===> 0_ characters
until ===> _
found
Operator ===> .. (e.g. EQ)
Operator ===> __ (e.g. EQ)
Press ENTER or UP or DOWN key to proceed updating this entry.
Press END key to cancel changes or HELP key for help information.
The upper part of the panel displays the scan ID and the title of the scan
definition as defined in the first scan definition panel.
Processing Condition (Extract only if this condition is true):
Comparison Type
Enter the data type which is to be used for a comparison. Use the type
String to compare alphabetic or numeric strings, or strings which contain
other characters. Specify the type Integer to perform numeric comparisons
with whole numbers.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
293
Reader (Option A.R)
Scanning (Option A.R.3)
Position of Reference Value: Relative to string, at word position, or at
column
Specify an absolute or a relative position for the reference value. For a
relative position, specify the position of the reference value relative to the
primary or secondary search string.
Specify to which search string the reference value is to be related:
0
Position is absolute
1
Position is relative to the primary search string
2
Position is relative to the secondary search string
Specify the word position of the reference value within the scanned line. If
you want to define the position by the column number, enter 0.
You can move the position at which the reference value is located
n characters to the right from the beginning of the word. Specify the
column number at which the reference value begins. If you want to define
the position by the word position, enter 0.
Note: Enter the position either absolute -counted from the beginning of the
line - or relative -counted from the beginning of the search string.
Comparison Length or until x found
Specify the length which is to be used for the comparison. If you enter 0,
the length will be determined by the stop character specified in field or
until<x> found.
Instead of defining a length, you can define a stop character to compare
from the specified position of the reference value up to this stop character.
Then the specified comparison length will be ignored. The stop character
can be any character or number.
Comparison Values: Value 1/Operator, Value 2/Operator
Enter any value with which the reference value is to be compared. Up to
two values can be entered. Next specify the kind of comparison operation
that is to be performed.
Available comparison operators are:
EQ equal to: ==
NE not equal to: !=
LT less than: <
LE less than or equal to: <=
GT greater than: >
GE greater than or equal to: >=
Note: Two conditions are connected by a logical AND.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
294
Reader (Option A.R)
Scanning (Option A.R.3)
Panel Update Scan
Definition (Page 4)
PE92SO13 ---------------------------------------------------------- Page 4 of 5
Command ===> _________________________________________________________________
Update Scan Definition
Last update: BETAINST 08/12/2002 12:00:00
Scan ID
Title : SCAN DUPLICATE
: 0000001061
DSN
B69
Extraction Arguments
Field ID to be updated
String to be returned
===> 800 : Chain scan definition
===> ________________
Extract string length
Data Type
Relative to String
at word position
or at column
===> 0...
===> _____
===> 0
===> 4_
===> 0__
or until ===> _
found
Date Mask ===> __________
Event Processing Parameters
Event ID
Table Name
===> _____
===> ________
Severity
===> _ (I/W/E)
Field Name ===> ________
plus
===> 0_ characters
Press ENTER or UP or DOWN key to proceed updating this entry.
Press END key to cancel changes or HELP key for help information.
The upper part of the panel displays which sysout lists are to be scanned
(scan ID, job name, step name, procstep, DD name) and the title of the
scan definition.
Which field should be updated?
Enter the numeric value of the field which is to be updated in the field Field
ID to be updated or enter 800 if you want to define a scan definition chain.
For a list of valid field IDs and their meaning, see "Target field IDs" on
page 284.
Updating fields with a fixed string or value
Updating fields with a fixed string or value requires the following definition:
•
String to be returned
Define the string or value that should be written to the specified field.
(Legal entries are dependent on the data type of the field.)
The Extract string length field cannot be left blank because it is required,
but the specified value is ignored if the String to be returned field is filled.
Example: Placing a job on the error queue
To place a job that fulfills the search criteria on the error queue, define the
following:
-
Field ID to be updated = 28
-
String to be returned = Yes
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
295
Reader (Option A.R)
Scanning (Option A.R.3)
Example: Removing a job from the error queue
To remove a job that fulfills the search criteria from the error queue, define
the following:
-
Field ID to be updated = 28
-
String to be returned = No
Note: To place a job on the initial error queue or remove it from this queue,
specify target field ID 29 instead.
Updating fields with strings extracted at absolute position
Use the following five fields to extract strings at an absolute position:
Field
Description
Extract string length
This field determines the length of the string to be
extracted. The examples below illustrate how to use this
field to extract:
•
n characters (Extract string length = n)
•
a word (Extract string length = 0)
•
a word plus n characters to the right (Extract string
length = +n)
•
a word plus n characters to the left (Extract string
length = -n)
or until x found
Instead of defining the length, you can also define a
stop signal. The stop-signal can be any character or
number.
at absolute word
position
Position of the word within the scanned line. (A word is
a string of one or more alphanumeric characters
delimited by two blanks, beginning of line and blank, or
blank and end of line.)
plus n characters
Moves the position at which the return string is extracted
n characters to the right (positive value) or to the left
(negative value).
at absolute column
Extracts the specified number of characters at this
column.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
296
Reader (Option A.R)
Scanning (Option A.R.3)
Example
The following sample line is used to describe the extraction of strings from
the scanned line:
22.12.19 JOB01234
ABC123I TEST
UNIT: ONLINE
The following examples illustrate how you can use these five fields to
extract a particular string. Fields that are not listed contain either zero or a
blank. In many cases, there are several ways to achieve the desired result.
To extract...
... for example ...
enter ...
n characters at a given 22.12
column position
Extract string length = 5
at absolute column = 1
an entire word
ABC123I
at absolute word position = 3
Note: 'Extract string length = 0' means extract
the entire word.
a word plus n
characters to the right
ABC123I TE
Extract string length = +3
at absolute word position = 3
a word plus n
characters to the left
1234 ABC123I
at absolute word position = 3
plus -6 characters
Note: 'Extract string length = 0' means extract
the entire word. 'Plus n characters' extends
this selection to the left. There are two blanks
between '4' and 'A'
a word truncated by n
characters at the end
ABC123
Extract string length = -1
at absolute word position = 3
a word truncated by n
characters at the
beginning
123I
at absolute word position = 3
plus 3 characters
Note: 'Extract string length = 0' means extract
the entire word. 'Plus n characters' moves the
selection pointer to the right.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
297
Reader (Option A.R)
To extract...
Scanning (Option A.R.3)
... for example ...
enter ...
a word truncated by m 123
characters at the end
and n characters at
the beginning
Extract string length = -1
at absolute word position = 3
plus 3 characters
a substring of n
characters extracted
from within a word
123
Extract string length = 3
at absolute word position = 3
plus 3 characters
the first n characters of ABC
a word
Extract string length = 3
at absolute word position = 3
a word and all
following characters
up to a stop sign
or until : found
at absolute word position = 4
plus 0 characters
TEST UNIT
Note: 'Extract string length = 0' means extract
the entire word. 'or until : found' extends this
selection to the right to the next colon (or end
of line if not found). The stop sign is not
included in the extracted string.
the last n characters
preceding a word
19
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
Extract string length = 2
at absolute word position = 2
plus -3 characters
298
Reader (Option A.R)
Scanning (Option A.R.3)
Updating fields with strings extracted at relative position
Leave the field String to be returned blank and use the following five
fields to define the string to be extracted:
Use the following five fields to extract strings at an absolute position:
Field
Description
Extract string length
This field determines the length of the string to be
extracted. The examples below illustrate how to use this
field to extract:
relative to String
•
n characters (Extract string length = n)
•
a word (Extract string length = 0)
•
a word plus n characters to the right (Extract string
length = +n)
•
a word plus n characters to the left (Extract string
length = -n)
Enter 1 if the following entries refer to the primary
search string.
Enter 2 if they refer to the secondary search string.
at relative word position Enter +n to extract the nth word to the right of the
search string.
You can use the fields plus n characters and Extract
string length to extend or truncate the selection.
plus n characters
Moves the position at which the return string is extracted
n characters to the right (positive value).
at relative column
Use this field to extract the search string at a specific
column position relative to the beginning of the search
string.
Sample line
The following sample line is used to describe the extraction of strings from
the scanned line:
... ALLOCATE FAILED FOR device RC=rc S99ERROR=eeee ...
The primary search string is ALLOCATE FAILED.
The secondary search string is S99ERROR.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
299
Reader (Option A.R)
Scanning (Option A.R.3)
Examples
The following examples illustrate how you can use these five fields to
extract a particular string. Fields that are not listed contain either zero or a
blank. In many cases, there are several ways to achieve the desired result.
To extract...
enter ...
the device name device
relative to String = 1
at relative word position = 3
Note: Extract string length=0 means extract
the entire word.
The word position is defined in relation to the
first word of the search string.
the return code rc
relative to String = 1
at relative word position = 4
plus n characters = 3
Note: Extract string length=0 means extract
the entire word.
Plus 3 characters truncates the first three
characters of this word.
the four-digit error code eeee
Extract string length = 4
relative to String = 2
at relative column = 9
Event processing parameters
The following fields are only used if you define a scan definition for event
processing with the target field ID 550.
In the field Event ID enter a numeric ID to identify an event. You can use
this event ID subsequently to assign an action to this event (under option
A.R.6). Enter the event ID 0 when no event is to be triggered by the scan
definition. Note: The event IDs 9000 - 9999 are internally used by _beta
log|z for default events. Do not use these numbers in your own userdefined scan definitions.
In the field Severity specify the severity of the event: I for informational, W
for warning, or E for error.
In the field Table Name enter the name of a database event table. The
scan result will be saved in this table.
In the field Field Name enter the name of a database event field. The scan
result will be saved in this field.
To store event information in more than one event field, use a scan
definition chain (target field ID 800) in combination with events (target field
ID 550).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
300
Reader (Option A.R)
Scanning (Option A.R.3)
Panel Update Scan
Definition (Page 5)
PE92SO14 ---------------------------------------------------------- Page 5 of 5
Command ===> _________________________________________________________________
Update Scan Definition
Last update: BETAINST 08/12/2002 12:00:00
Scan ID
Title : SCAN DUPLICATE
: 0000001061
DSN
B69
Chain Arguments
Chain Name
===> IGD17101
Next Scan ID to be activated ===> 0000001062
End of Chain
===> NO.
(Y)es or (N)o
Field ID to be updated
Output offset
===> 000 : Unknown code
===> 007
Temporary disabled
Report unmatched
Blank Removal
===> YES
===> NO_
===> NO_
(Y)es or (N)o
(Y)es or (N)o
(Y)es or (N)o
Press ENTER to proceed updating this record or UP key for previous page.
Press END key to cancel changes or HELP key for help information.
How can I group a set of dependent scan definitions?
Field
Description
Chain Name
Enter a chain name to group a set of dependent scan
definitions. (A chain consists of a number of scan
definitions which depend on each other and which are
activated one after the other.)
Which scan ID should be activated next in the chain?
Field
Description
Next Scan ID to be
activated
Specify the scan ID of the scan definition which is to be
activated next when the current scan definition has
matched.
Is this scan definition the last in the chain? Or should the specified
target field be updated?
Field
Description
End of Chain
Enter Yes to indicate that the processing for the specified
field ID which is to be updated should take place now.
Enter No if the scan result is to be used later in a
succeeding scan definition.
Note: At least the last activated scan definition in a chain
must be marked as the end of the chain.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
301
Reader (Option A.R)
Scanning (Option A.R.3)
Which field is to be updated?
Field
Description
Field ID to be
updated
Enter a numeric value of the field which is to be updated by this scan
definition. For a list of valid field IDs and their meanings, see "Target field
IDs" on page 284.
Output Offset
Enter the start column where the scanned string should appear in the output
line. This field enables you to combine the results of two or more scan
definitions in one output line.
Temporary disabled
Enter Yes to define a temporarily disabled scan definition (which is the
default). This scan definition can be activated by another scan definition of
that chain. Specify No for the first scan definition in a chain.
Note: In a chain of dependent scan definitions all definitions except for the
first must be temporarily disabled.
Report unmatched
Enter Yes to search for strings that do NOT appear in the list. You must
enter the text which is to be returned, for example, COMPLMSG MISSED,
in the field String to be returned on page 3 of the "Update Scan Definition"
panel.
Example: If your job step which always executes with RC=0 does not
produce the output line "COMPLETED SUCCESSFULLY", you can produce
such a message record (use target field ID 30). (By default the field is set to
No.)
Blank Removal
Enter Yes if the blanks in the result string are to be removed before the
result string is saved in the target field. The default value is No.
Example: Blanks are removed from the extracted string when the system
ID is retrieved from this line of the JESMSGLG:
J E S 2
J O B
L O G -- S Y S T E M
B E T A -- N O D E
D E B E T A J 2
Before blank removal: B E T A
After blank removal:
BETA
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
302
Reader (Option A.R)
Scanning (Option A.R.3)
Example: Defining additional criteria for job selection
Overview
DD B55IN contains the line: function RULESET rule set name
In the following example, function and rule set name are to be extracted
from DD B55IN and inserted as additional job selection criteria.
Adding two search criteria requires two separate scan definitions.
The "Update Scan Definition" panel shows the required entries for
searching DD B55IN for string RULESET at the second word position.
PE92SO11 ---------------------------------------------------------- Page 1 of 5
Command ===> _________________________________________________________________
Update Scan Definition
Last update: AVSCHM1
Scan ID
Job/Rule
DDName
Group
Category ===> HOSTJOB
===> *
Procstep ===> *
===> ADD SELECTION BY FUNCTION
(* for list)
: 0000010024
===> *
Stepname
===> B55IN
Title
===>
Primary Search Arguments
String
===> RULESET
(case-sensitive)
Search Primary String
between lines
===> 0
at word position
===> 2
or between columns
===> 1
Secondary String
Processing Condition
Length
and ===> 0
plus ===> 0
and ===> 80
===> NO
===> NO
06/07/2008 11:40:51
===> 7
characters
(Y)es or (N)o
(Y)es or (N)o
Press ENTER or DOWN key to proceed updating this entry.
Press END key to cancel changes or HELP key for help information.
The "Update Scan Definition" panel shows the required definitions for
updating target field ID 31 with the function name extracted from the first
word position:
PE92SO13 ---------------------------------------------------------- Page 4 of 5
Command ===> _________________________________________________________________
Update Scan Definition
Last update: AVSCHM1
Scan ID
Title : TEST
: 0000010024
06/07/2008 11:40:51
Extraction Arguments
Field ID to be updated
String to be returned
===> 31
===>
: Insert an extended select record
Extract string length
Data Type
Relative to String
at word position
or at column
===> 0
===>
===> 0
===> 1
===> 0
or until ===>
Date Mask ===>
Event Processing Parameters
Event ID
Table Name
===>
===>
Severity
===>
Field Name ===>
plus
===> 0
found
characters
(I/W/E)
Press ENTER or UP or DOWN key to proceed updating this entry.
Press END key to cancel changes or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
303
Reader (Option A.R)
Scanning (Option A.R.3)
The scan definition that adds the rule set name as search criterion requires
the following definitions:
at absolute word position ===> 3
All other fields (except the title) are identical to the first scan definition.
When selecting jobs, enter Additional arguments=Yes and specify a
function and/or rule set name in the "Extended Job Selection" panel. In the
following example, only stack jobs for rule set MYRULES will be selected.
PE92BR02 ---------------------------------------------------------------------Command ===> _________________________________________________________________
More Optional Selection Criteria
Jobs with Sysout Class
Jobs with Form
===> _
===> ________
Extended Job Selection Criteria
Criteria 1
Criteria 2
Criteria 3
Criteria 4
Criteria 5
Criteria 6
Criteria 7
Criteria 8
===> STACK___________________________
===> MYRULES_________________________
===> ________________________________
===> ________________________________
===> ________________________________
===> ________________________________
===> ________________________________
===> ________________________________
Press ENTER key to display jobs.
Press END key to return to the previous panel.
Note
We recommend that you do not define target field ID 31 which is assigned
to all jobs. Otherwise this will have a negative effect on the database size,
the reader performance and the online performance.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
304
Reader (Option A.R)
Scanning (Option A.R.3)
Scan definitions for Message Output Facility (MOF)
Overview
A range of target field IDs in scan definitions are reserved for the Message
Output Facility (MOF).
Message
When the string defined in the corresponding scan definition has been
found in the scanned log, _beta log|z generates an informational message,
a warning message, or an error message of the type:
OMS28nnx jobname jesid submitting_userid scandata
MOF target field IDs
Required definitions
The target field ID specified in the scan definition determines the number
and severity of the message that is generated.
Target field ID
Generate this type of message
200 through 249
MOF: Write informational messages to JESMSGLG
(OMS2800I through OMS2849I)
300 through 349
MOF: Write warning messages to JESMSGLG
(OMS2800W through OMS2849W)
400 through 449
MOF: Write error messages to JESMSGLG
(OMS2800E through OMS2849E)
•
Scan definitions: Define scan definitions for one or several of the
target field IDs described in the previous table (option A.R.3).
•
Subsystem options: on page 1 of the subsystem options, specify the
following:
Send Message on Error=YES
to MOF=YES
•
Note
To log messages generated by the Message Output Facility in
DD B92EVENT, the following LST parameter must be set:
B92_MOF2EVENT=YES
Changes will become effective after stopping and restarting the product
STC.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
305
Reader (Option A.R)
Scanning (Option A.R.3)
Simulating the execution of scan definitions
Overview
You can simulate the execution of your scan definitions to check their
accuracy and efficiency before they are used in production. The feature
considerably facilitates the creation of scan definitions.
The scan definition is set in test status under option A.R.3 in the "Scan
Definition Table" (see "Scanning (Option A.R.3)" on page 268).
Procedure
To start the scan definition simulation:
1. Enter the line command T in front of a job name or a rule name.
This line command is available in the "Job Information Table", the "File
Rule Information Table", in "SAP Job Information Table", and in the
"Syslog Information Table". The example below uses the "Job
Information Table".
PE92BR20
Command ===>
Row
1 of
8
Scroll ===> CSR
Job Information Table AVMMAIL2 (J0050797)
Submitted 09/07/09
Started
09/07/09
Ended
09/07/09
at 14:20:37 by BEATE3
at 14:20:38 in class A on system BETA
at 14:20:39
Position:
M - Message
N - Note
S - Step
L - List
S - Browse a list
K - Toggle keep status
V - View a list
X - Toggle nokeep status
B - Browse spinned list A - Toggle re-archive
X - Ext.Info
O - IWS
P,M - Print/Mail a list
R,U - Reload a list
T - Call Scan Test
Sel Stepname Procstep Errortxt CC
CPU-Time
SRB-Time Private High Prv
PRINT
0
0:00.08
0:00.01
2304 K
19736 K
------------------------------------------------------------------------------Sel Row DDName Stepname Procstep Pages
Lines Class Form
Arch Status
1 JESJCLIN JES2
1
58
Y
STD
PEND ONLINE
2 JESMSGLG JES2
1
50
Y
STD
PEND ONLINE
3 JESJCL
JES2
1
37
Y
STD
PEND ONLINE
4 JESYSMSG JES2
1
40
Y
STD
PEND ONLINE
5 OMSPRINT PRINT
2
30
Y
STD
PEND ONLINE
Note: Only active scan definitions and scan definitions in test status
will be processed. The scanning will only be simulated, i.e. the scan
result will not be written to the database field defined in the target
field ID of your scan definition. The user who is allowed to display and
browse a list, is also allowed to execute a scan definition test.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
306
Reader (Option A.R)
Scanning (Option A.R.3)
The result of the scan test is displayed in the "Scan Test Table":
PE92BR40
Command ===>
12 scan results found
Scroll ===> CSR
Scan Test Table for AVMMAIL2 (JESYSMSG)
S - Select Scan Definition
Sel Scan ID
FieldID Extracted
0000001004 011
PRINT
0000001006 014
0000
0000001037 800-021 2304
0000001038 800-022
296
0000001039 800-023
19736
0000001040 800-024
14468
0000001041 800-017
0
0000001042 800-018 00.08
0000001043 800-019
0
0000001044 800-020 00.01
0000001029 001
2009250.
0000001032 003
2009250.
0000001001 075
**DD Name does not match mask
**
0000001002 025
**DD Name does not match mask
**
0000001003 011
**Scan definition does not match**
0000001005 012
**Scan definition does not match**
Len Line
005
004
005
005
007
007
004
005
004
005
008
008
26
26
38
38
38
38
38
38
38
38
39
40
The table shows the matching scan definition, i.e. which character
chain would be written to which field, or the reason why a scan
definition does not match, for example, due to a job name mask not
matching.
Note on scan definition chains: Some scan definitions are not used
to extract certain strings. They are used to indicate the beginning of a
scan definition chain. In this case, the scan test will return the search
string.
2. Enter S in front of a scan result line to display the scan definition used:
PE92SO10
Command ===>
Row
1 of
1
Scroll ===> CSR
Scan Definition Table
S - Select Scan Definition
I - Insert Scan Definition
A - Activate\Deactivate Scan Def.
D - Delete Scan Definition
C - Copy Scan Definition
T - Toggle Test Status of Scan Def.
Sel A T Title
Scan ID
C ChainName EoC EventID
Y Y SCAN STEPNAME WITHOUT PROCST B12 0000001004 N
NO
******************************** BOTTOM OF DATA ********************************
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
307
Reader (Option A.R)
NoError (Option A.R.4)
NoError (Option A.R.4)
Overview
You can determine the success or failure of a job via its job completion
code under the NoError option A.R.4. You can extend the list of
acceptable job condition codes and exclude error codes so that they are
not treated as errors. The advantage is that certain return codes can be
considered not to be an error.
When the return code of a job matches a NoError definition, the return
code of the job is set to 0, i.e. to the normal job completion code. Any job
that ended with this completion code is treated as having ended normally.
The extended list of NoError job completion codes might be of importance
for job tracking purposes. An enhanced error code suppression might also
be important for the exchange with other programs that are using other
ranges of completion codes, for example, IBM Workload Scheduler for
z/OS (IWS).
The NoError option A.R.4 enhances the definitions of the subsystem
options under option A.S.2. In the fields Error Code Lowest and Error
Code Highest the lower and the upper limit for job error codes are
determined (1st panel, option A.S.2).
For changes to take
effect
The NoError table is read by the _beta log|z readers when they are
started. If you change the NoError definitions of your system, you have to
restart the readers for your changes to take effect.
Note on _beta job|z
The _beta log|z NoError definitions can also be used by _beta job|z (see
"NoError handling" in _beta job|z Administrator Guide).
The NoError table is read by the _beta job|z started task when it is started.
If you change the _beta log|z NoError definitions, enter the following
console command for your changes to take effect in _beta job|z:
F stcname,REF NOERROR
where stcname is the name of the _beta job|z started task.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
308
Reader (Option A.R)
NoError (Option A.R.4)
Selecting NoError definitions
Procedure
1. Enter 4 in the Reader menu A.R.
The "NoError Definition Selection" panel is displayed:
PE92RD04 ---------------------------------------------------------------------Command ===> _________________________________________________________________
NoError Definition Selection
Jobname
Stepname
Procstep
===> *.......
===> ________
===> ________
The following line commands will be available when the table is displayed:
S - Select NoError Definition
I - Insert NoError Definition
D - Delete NoError Definition
C - Copy
NoError Definition
Press ENTER key to display the selected definitions.
Press END key to return to the previous menu.
2. Enter your selection criteria in the fields Jobname, Stepname and/or
Procstep. Masks are allowed.
3. Press ENTER to display the "NoError Definition Table":
PE92RD40 -------------------------------------------------- Row
1 of
32
Command ===> ________________________________________________ Scroll ===> PAGE
NoError Definition Table
S - Select NoError Definition
I - Insert NoError Definition
D - Delete NoError Definition
C - Copy NoError Definition
Opera RC Lowest Highest
Sel Jobname Stepname Procstep tor Type Good RC Good RC
B92AGINF *
*
RANGE S
000
013
CHRIS123 SSSSSSS* PPPPPPP0 EQ
CC
0001
CHRIS123 SSSSSSS1 P1P1P1P1 EQ
CC
0001
ERGJOB0X STEP2
*
EQ
CC
0002
JYSABEND *
*
LT
S
055
RODJOB0X STEP1
*
RANGE U
0001
0010
RODJOB0X STEP2
*
EQ
CC
0002
RODJOB0X STEP3
*
NE
S
0C3
RODJOB0X STEP4
*
LT
U
0004
RODJOB0X STEP5
*
LE
CC
0005
RODJOB01 STEP1
*
RANGE CC
0001
0010
RODJOB01 STEP1
*
RANGE U
0001
0010
RODJOB01 STEP1
*
RANGE S
0C1
0C7
RODJOB02 STEP1
*
EQ
S
B37
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
Group
Name
309
Reader (Option A.R)
NoError (Option A.R.4)
4. Press PF11 to display the right columns of the table (PF10/PF11 to
scroll to the left/right).
The columns are described below the procedure.
PE92RD40 -------------------------------------------------- Row
1 of
32
Command ===> ________________________________________________ Scroll ===> PAGE
NoError Definition Table
S - Select NoError Definition
I - Insert NoError Definition
D - Delete NoError Definition
C - Copy NoError Definition
Opera RC Lowest Highest
Sel Jobname
tor Type Good RC Good RC Reason
B92AGINF RANGE S
000
013 internal error code suppression
CHRIS123 EQ
CC
0001
test case
CHRIS123 EQ
CC
0001
test case
ERGJOB0X EQ
CC
0002
CC 0002 valid
JYSABEND LT
S
055
error code suppression for TWS
RODJOB0X RANGE U
0001
0010 U0000 - U0010 valid
RODJOB0X EQ
CC
0002
CC 0002 valid
RODJOB0X NE
S
0C3
S 0C4 not valid
RODJOB0X LT
U
0004
U0000 - U0003 valid
RODJOB0X LE
CC
0005
CC 0000 - CC 0005 valid
RODJOB01 RANGE CC
0001
0010 CC 0000 - CC 0010 valid
RODJOB01 RANGE U
0001
0010 U0000 - U0010 valid
RODJOB01 RANGE S
0C1
0C7 S 0C1 - S0C7 valid
RODJOB02 EQ
S
B37
Ignore B37
Columns
Line commands
Column
Description
Jobname
The defined job name is displayed.
Stepname
The specified step name is displayed.
Procstep
The specified procedure step is displayed.
Operator
The comparison operator in use is shown.
RC Type
The type of the return code is displayed.
Lowest Good RC
The lowest specified completion code which is treated as a
NoError code is displayed.
Highest Good RC
The highest specified completion code which is treated as a
NoError code is displayed
Group Name
The specified NoError group is displayed.
Reason
The reason why the job completion code has been defined
as a NoError code is displayed.
S
Selects a NoError definition
I
Inserts a NoError definition
D
Deletes a NoError definition
C
Copies a NoError definition
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
310
Reader (Option A.R)
Primary commands
NoError (Option A.R.4)
FIND
Searches for a string in the table
SORT
Sorts the columns "Jobname", "Stepname", and
"Procstep" in the table in ascending (blank) or
descending (D) order
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
311
Reader (Option A.R)
NoError (Option A.R.4)
Specifying NoError completion codes
Procedure
1. Select NoError definitions. See "Selecting NoError definitions" on
page 309.
2. Enter the line command I in front of any NoError definition in the
"NoError Definition Table".
The "Insert NoError Definition" panel is displayed:
PE92RD43 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Insert NoError Definition
Jobname
Stepname
Procstep
===> ........
===> ........
===> ........
Type of RC
===> ..
CC, S or U
Operator
===> .....
Range, EQ, NE, LT, LE, GT or GE
Lowest Good RC ===> ....
Highest Good RC ===> ____
Group Name
Reason
===> ________
===> ............................................................
Press ENTER key to insert this entry and continue.
Press END key to cancel changes or HELP key for help information.
3. Specify the NoError definition (see the table below for a description of
all fields).
The error code that is not to be considered an error must be entered in
the field Lowest Good RC.
When the return code of a job matches a NoError definition, the return
code of the job is set to 0, i.e. to the normal job completion code. Any
job that ended with this completion code is treated as having ended
normally.
4. Press ENTER to save the new NoError definition.
Fields
Field
Description
Jobname
Enter the job name or a job mask (%, ? for any single
character at this position or * for any sequence of
characters) to determine to which jobs the NoError
definition applies (max. 8 characters).
Stepname
Enter the name of the step to which the NoError
definition applies (max. 8 characters). You can use
wildcards to mask the step name.
Procstep
Enter the name of the procstep to which the NoError
definition applies (max. 8 characters). You can use
wildcards to mask the procstep name.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
312
Reader (Option A.R)
NoError (Option A.R.4)
Field
Description
Type of RC
Specify the return code type used for the NoError
definition:
Operator
CC
Condition code
S
System abend code
U
User abend code
Specify the comparison operator to be used for the
NoError definition.
Available comparison operators are:
RANGE
EQ
equal to: ==
NE
not equal to: !=
LT
less than: <
LE
less than OR equal to: <=
GT
greater than: >
GE
greater than OR equal to: >=
The comparison operator RANGE requires a value in
both Lowest Good RC and Highest Good RC. For
other operators, specify the comparison value in the
Lowest Good RC field and leave Highest Good RC
empty.
Lowest Good RC
Specify the lowest step condition code, system abend
code, or user abend code which is to be treated as a
NoError code (max. 4 characters).
Or specify an individual value of a return code if you use
any other operator than RANGE.
Highest Good RC
Specify the highest step condition code, system abend
code, or user abend code which is to be treated as a
NoError code (max. 4 characters).
Or leave the field blank if you use any other operator
than RANGE.
Group Name
Enter a group name (optional, max. 8 characters)
This field can be used for grouping NoError definitions.
You can also use this field as member name, for
example, when keeping the NoError definitions of _beta
log|z and IWS in sync. Use _beta report to download the
definitions and then use downloaded members as
NoError members in an IWS parmlib.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
313
Reader (Option A.R)
NoError (Option A.R.4)
Field
Description
Reason
Describe the reason for the suppression, i.e. why the
completion code has been defined as a NoError code
and why the job is not to be put onto the error queue
(max. 60 characters). An entry is required.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
314
Reader (Option A.R)
Log processing (Option A.R.5)
Log processing (Option A.R.5)
Overview
Create appropriate log processing definitions if you want _beta log|z to
apply log processing to the output of certain jobs, TSO users, or started
tasks.
Log processing means that one job base record is created for each sysout
list of the job, TSO user, or started task.
It is also possible to restrict log processing to a particular class. For
example, JESMSGLG, JESJCL, and JESYSMSG can be processed like a
normal job and the remaining sysout can be processed like a log job.
Note on z/OS syslog: _beta log|z provides for special processing of the
z/OS syslog, where one job base record is created for the syslogs of one
day. For information on syslog processing, see "z/OS syslog" in _beta
log|z Installation and System Guide.
Log queue
Jobs that undergo log processing are called log jobs.
Log jobs are placed on the log queue and can be recognized by the L in
the Status column of the "Job Select Table". You can limit your selection
to log jobs by entering L in the Queue Type field.
Line command S opens the sysout of a log job directly in the Beta
Browser. The "Job Information Table" is skipped. Enter the line
command ? in front of a log job to display the "Job Information Table".
Submit/Start/End time
The end time and the submit time of a log job is the _beta log|z read-in
time.
The start time of a log job is the start time of the job or started task or the
login time of the TSO user.
Example:
Processing STC sysout
This example looks at the effect of log processing on the sysout printing of
a started task, for example, via line command P in _beta log|z or _beta
doc|z. A sysout list from the started task is processed as follows:
If log processing is applied to the started task:
•
_beta log|z adds a new job record for each sysout print. The job name
is the name of the started task.
•
This job has one list DD SYSnnnnn, which is the sysout of the print
command.
•
The submit time of the log job is the read-in time into _beta log|z.
If standard processing is applied to the started task:
•
_beta log|z adds an additional DD SYSnnnnn under the existing _beta
log|z job record of the started task.
•
The submit time of the job is normally the time when the started task
was started.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
315
Reader (Option A.R)
Log processing (Option A.R.5)
Changes require reader
restart
For any changes to the log processing definitions to take effect, the _beta
log|z reader has to be restarted (F stcname,RES RDR). When using multiimage processing, you have to restart the _beta log|z reader for each z/OS
image.
Navigation
From the "Primary Selection Menu", choose:
•
Option A.R.5
The "Log Processing Definition Selection" panel is displayed, in which
you can enter your selection criteria.
Insert Log Processing
Definition panel
PE92DF33 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Insert Log Processing Definition
Log Job Name ===> ........
Name or Mask
Type
===> ...
(S)tc, (T)su or (J)ob
Class
===> _
Class or blank
Press ENTER key to insert this entry and continue.
Press END key to cancel changes or HELP key for help information.
Fields
Field
Description
Log Job Name
Name or a mask that identifies the job, STC, or TSO
user
Type
Specify one of the following types:
Class
STC
Started task
TSU
TSO user
JOB
Standard job
Optionally, you can enter a class. Log processing will
then be applied only to the sysout of this class, but not
to the other output of the job, STC, or TSO user.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
316
Reader (Option A.R)
Line commands
Log processing (Option A.R.5)
The following line commands are available in the "Log Processing
Definition Table":
S
Selects the log processing definition for display or update
I
Adds a new log processing definition (insert)
C
Adds a new log processing definition (copy)
D
Deletes the log processing definition
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
317
Reader (Option A.R)
Event actions (Option A.R.6)
Event actions (Option A.R.6)
Overview
An event action is an action that is triggered by the occurrence of an event.
For general information on events, see "Event processing" on page 324
and "Standard events" on page 327.
An event action can be submitting a job or sending a notification by e-mail.
Sent e-mail can include a _beta view link to the event-triggering job or a
list of this job. Skeletons with variables are used for the generation of JCL
and e-mail text.
An event action is associated with a specific event or group of events via
the numeric event ID. If the event is triggered by scanning, the event ID is
defined in the event processing parameters of the scan definition that
writes the corresponding event record (see "Event processing" on
page 324).
Notes
Event tables EVT01 and EVT02 do not support event action processing.
Submitter of JOB event
actions
By default, the current STC user is the submitter of event actions of the
type JOB. Specify a user name (max. 8 digits) in the LST parameter
B92_DEFAULT_SUB_USER if you want to use a different user ID.
Note: The _beta log|z STC user must have READ access to the profile
BETA.ssid.CHANGE.USERID in the FACILITY class to be able to carry
out the user switch.
Navigation
From the "Primary Selection Menu", choose:
•
Option A.R.6
The "Event Action Definition Selection" panel is displayed, in which
you can enter your selection criteria.
Changes require event
router restart
For any changes to the event action definitions to take effect, the revent
router has to be restarted. To do this, enter the primary command RES in
the "Event Action Definition Table".
A new event action definition is always inactive. If you want to activate it,
enter line command A in front of the definition before you restart the event
router. The Act column of the "Event Action Definition Table" shows
whether a definition is active.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
318
Reader (Option A.R)
Event actions (Option A.R.6)
Insert Event Action
Definition panel (Page 1)
PE92DF11 ---------------------------------------------------------- Page 1 of 2
Command ===> _________________________________________________________________
Insert Event Action Definition
Event Action Name ===> ........
Event ID
===> .....
Description
===> __________________________________________________
===> __________________________________________________
Severity
Category
===> .
===> ________
Job Name
System ID
Event Text
===> ................................
===> ........
===> __________________________________________________
Action Type
===> .....
I, W or E
(H)ostJob, (F)ileRule or (S)APRule
(E)mail or (J)ob
Press ENTER or DOWN key to proceed inserting this entry.
Press END key to cancel changes or HELP key for help information.
Fields (Page 1)
Field
Description
Event Action Name
The name identifies the event action definition (required).
Event ID
This numeric ID associates the event action to the event
or to a group of events (required).
Description
Descriptive text
Severity
Action will be triggered only if the event has the specified
severity:
Category
I
Informational
W
Warning
E
Error
Enter a category to trigger the action only if the event
occurs in output that comes from the specified category:
H
Host jobs
F
File rules
S
SAP rules
blank
Any category
Jobname
Enter the name of a job or a job mask to trigger the action
only if the event occurs in a specific job.
System ID
Enter a system, an agent name, or use a mask to trigger
the action only if the event occurs on a specific system.
Event Text
Enter the text of the event or a mask to trigger the action
only if the event occurs with a specific text.
Action Type
Enter J (job) if the action is submitting a job.
Enter E (e-mail) if the action is sending e-mail.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
319
Reader (Option A.R)
Event actions (Option A.R.6)
This panel is displayed if the action type is JOB:
Insert Event Action
Definition panel
(Page 2 - JOB)
PE92DF13 ---------------------------------------------------------- Page 2 of 2
Command ===> _________________________________________________________________
Insert Event Action Definition
Event Action Name
Event ID
Action Type
Job Member
: JOBEVT1
: 12112
: JOB
===> ........
Press ENTER to insert this entry or UP key for previous page.
Press END key to cancel changes or HELP key for help information.
Fields (Page 2 - JOB) Field
Description
Job Member
Enter the name of the member in your _beta log|z job
library (B92JLIB) that contains the job to be submitted by
this event action.
See "Skeletons and variables" on page 322 for a list of
available variables.
Insert Event Action
Definition panel
(Page 2 - EMAIL)
This panel is displayed if the action type is EMAIL:
PE92DF12 ---------------------------------------------------------- Page 2 of 2
Command ===> _________________________________________________________________
Insert Event Action Definition
Event Action Name
Event ID
Action Type
: MAILEVT1
: 15000
: EMAIL
Email Skeleton
===> ........
Email Address
===> ...................................................
===> ___________________________________________________
===> ___________________________________________________
===> ___________________________________________________
===> ___________________________________________________
Press ENTER to insert this entry or UP key for previous page.
Press END key to cancel changes or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
320
Reader (Option A.R)
Event actions (Option A.R.6)
Fields (Page 2 - EMAIL)
Field
Description
Email Skeleton
Name of the e-mail skeleton to be used
The skeleton must be located in your _beta log|z job
library (B92JLIB). The skeleton contains the text of the
e-mail and optionally the parameters MAILFROM and
SUBJECT.
See "Skeletons and variables" on page 322 for a list of
available variables. See "E-mail skeleton" on page 323
for an example of an e-mail skeleton.
Email Address
E-mail address of the mail recipient
Separate e-mail addresses by a comma if you want to
send mail to more than one recipient.
Line commands
Primary command
The following line commands are available in the "Event Action Definition
Table":
S
Selects the event action definition for display or update
I
Adds a new event action definition (insert)
D
Deletes the event action definition
C
Adds a new event action definition (copy)
A
Activates the event action when it is inactive;
deactivates the event action when it is active
L
Lists the scan definitions that use the event action (same event ID)
The following primary commands are available in the "Event Action
Definition Table":
RES
Restarts the event router
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
321
Reader (Option A.R)
Event actions (Option A.R.6)
Skeletons and variables
Overview
The JCL of the event action type JOB and the e-mail of the event action
type EMAIL are generated from skeletons. The name of the skeleton is
specified in the event action definition.
The skeletons are stored as members in the _beta log|z job library
(B92JLIB) and can contain variables.
Maximum width
JCL triggered by the event action type JOB has a fixed width of 80
characters.
An e-mail triggered by the event action type EMAIL can have a maximum
width of 320 characters.
Variables
Each variable starts with a percent sign ( % ) and ends with a period ( . ).
Variables are case-sensitive.
Variable
Description
%DATE.
Current date (Format: System date mask)
%TIME.
Current time (hh:mm:ss:ff)
%INPDATE.
Input date (Format: System date mask)
%INPTIME.
Input time (hh:mm:ss:ff)
%CATEGORY.
Category (HOSTJOB, FILERULE, or SAPRULE)
%DSID.
ID of the dataset
%EVTID.
Event ID
%EVTTABLE.
Event table
%EVTTEXT.
Event text
%EVTTOKEN.
Unique token of the event
%JOBID.
JES ID of the job
%JOBNAME.
Job name
%SEVERITY.
Severity of the event (I for informational, W for warning,
or E for error)
%SOURCE.
BETA if scan ID <=9999
USER if scan ID >=10000
%SYSID.
If HOSTJOB: System ID
If FILERULE: Agent name
If SAPRULE: SAP system name
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
322
Reader (Option A.R)
Event actions (Option A.R.6)
Variable
Description
%JOBLINK.
Only for action type EMAIL:
Link to the job in _beta view, based on the URL and
favorite defined in global options (see "Global options
(Option A.S.3)" on page 230)
%LISTLINK.
Only for action type EMAIL:
Link to the list in _beta view, based on the URL and
favorite defined in global options (see "Global options
(Option A.S.3)" on page 230)
E-mail skeleton
Optionally, you can specify the following processing information in the first
two lines of the skeleton if the skeleton is used for the action type EMAIL:
MAILFROM=mail sender
SUBJECT=mail subject
If MAILFROM= is not coded, the entry in the field Mail from under option
A.S.3 is used instead (see "Global options (Option A.S.3)" on page 230).
If SUBJECT= is not coded, the following default subject is used instead:
B92EVENT from ssid at date,time source jobname (job ID)
Example:
MAILFROM=b92admin@betasystems.com
SUBJECT=JOB ERROR FOR %JOBNAME..%JOBID..%DATE..%TIME.
This is an automatic e-mail triggered by _beta log|z.
The following job has ended in error:
Jobname: %JOBNAME.
JES ID: %JOBID.
Follow the links below to show the job in _beta view.
-- To display the job in the Job Selection table:
%JOBLINK.
-- To open the list in the _beta view | browser:
%LISTLINK.
Kind regards,
Your _beta log|z team
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
323
Reader (Option A.R)
Event actions (Option A.R.6)
Event processing
Overview
_beta log|z includes definitions for the processing of standard events. Most
standard events are generated by the reader and are triggered by scan
definitions. Standard events can also be triggered by known values, for
example, RCs or outlim from SAPI.
Standard error events
_beta log|z can generate an event when it places a job on the Error queue.
The error event contains information on the job that ended with an error.
It is also possible to limit event generations to certain error conditions. This
behavior is controlled via the LST parameter B92_ERROR_TRACKING.
For example, code the following if you want events generated for all jobs
that end in error and all jobs that exceed the output limitation:
B92_ERROR_TRACKING=JOB,OUTLIM
For more information on the LST parameter B92_ERROR_TRACKING,
see "Standard events" on page 327.
Events triggered by
scanning
Use a scan definition (Option A.R.3) with target field ID 550 if an event is
to be triggered by the occurrence of a particular message text in a list.
The target field ID is specified on page 4 of the scan definition in the Field
ID to be updated field. The event processing parameters are also
specified in this panel. You can specify the event ID, the severity of the
event (informational, warning, or error), the event table name, and the
event field name.
The event parameters are only used if the scan definition is used for event
processing (i.e. if the target field ID is 550). Use a scan definition chain
(target field ID 800) if you want to fill several event fields.
Action triggered by event
Use the event ID to link an event, for example, the occurrence of a
particular message text, with an event action (submitting a job or sending
e-mail). Specify the same event ID in the action definition (Option A.R.6)
as in the scan definition (Option A.R.3) if the occurrence of a particular
message should cause the submission of a job or sending of an e-mail.
When the scan definition matches, an event is written to the _beta log|z
event table. The result of the scanning is stored in the specified event table
and field. This also triggers the event action defined for this event, for
example, submitting a job or sending an e-mail.
Note: Event tables EVT01 and EVT02 do not support event action
processing.
Further information
For more information on scan definitions, see "Scanning (Option A.R.3)"
on page 268.
For more information on event actions, see "Event actions (Option A.R.6)"
on page 318.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
324
Reader (Option A.R)
Event tables
Event actions (Option A.R.6)
Event information is stored in event tables. An event table (EVTnn) can
contain up to 32 user-defined fields. The maximum length of each field is
255 characters.
Event tables EVT00 through EVT49 are reserved for use by Beta Systems.
EVT50 through EVT99 can be used for storing use-case-dependent event
information, for example, FTP data. Please contact Beta Systems if you
want to use an additional event table.
Three event tables are available by default:
Event table
Online option
Purpose
EVT00
E.0
Standard events
EVT01
E.1
_beta log|z Activity Audit Log (AAL)
EVT02
E.2
IWS occurrences
Note: Event tables EVT01 and EVT02 do not support event action
processing.
Event option
Event information can be displayed online under option E (see "Events
(Option E)" in _beta log|z User Guide).
Event IDs
Each type of event is identified by an event ID. The event IDs 9000..9999
are reserved for internal use by _beta log|z. Do not use any event IDs
within this range in your own user-defined scan definitions.
Using B92WAIT4 in event
actions
Event processing and reader processing are asynchronous. This can lead
to problems if the triggered event is processed before the data of the
originating job has been completely stored in the _beta log|z database.
For example, an event action definition specifies that a particular list of a
job is to be processed by B92PRINT or B92SSRCH. If reader processing
has not yet finished and the corresponding job base record (JBR) and job
list records (JLR) are not yet present, B92PRINT or B92SSRCH will end
with a Job not Found error.
You can prevent this type of error from happening by using a two-step host
job for this type of event action:
Step 1 (B92WAIT4) checks for the presence of the desired job or list.
Step 2 (B92PRINT or B92SSRCH) processes the corresponding list.
For more information, see "B92WAIT4: Waiting for a job or list" on
page 515.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
325
Reader (Option A.R)
Shared databases
disable event router
Event actions (Option A.R.6)
The _beta log|z event router is unable to work if the database is shared
with BQL_SHARE_OPTION=ALL. Message OMS1029W informs you
about this. Events are written when the database is shared, but the status
of each generated event is set to E (Error), which means that no event
action is triggered.
For more information on the BQL_SHARE_OPTION parameter, see
"Sharing databases with the BQL share option" in BSA Installation and
System Guide.
Maximum number of
events
The _beta log|z readers send events to the event router without waiting
that the events are actually triggered. The event router submits the events
in an asynchronous manner and takes care of the recovery.
When a list is scanned by a scan definition, a maximum of 50 events are
allowed to be created.
A maximum of 10 actions are allowed to be triggered by an event. If more
actions are triggered, message OMS3028E (too many actions found for
event event token, max. 10) will come up.
The internally used event buffer can store or process up to 500 events.
When the threshold has been reached, the messages OMS3010E (event
buffer full), OMS3101E (failed to trigger event event token), OMS3030W
(high water mark reached, nnn event buffered) will inform you about the
situation.
When the number of events is lower than 100 in the event buffer, new
events can be stored and processed.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
326
Reader (Option A.R)
Event actions (Option A.R.6)
Standard events
Event ID (Severity) Description
9200 (E)
Job error event: An event is generated for each job that ends with an error.
Activation: B92_ERROR_TRACKING = JOB | ALL
Event text: JOB
9200 (W)
ON SYSTEM sysid
IN ERROR - errorcode
Step error event: An event is generated for each step that ends with an
error.
Activation: B92_ERROR_TRACKING = STEP | ALL
Event text: STEP stepname.procstepn errortype - errorcode
9205 (W)
Outlim event: An event is generated when a list is not read in because it
exceeds the output limitation. For more information, see "Large list
monitoring and outlim processing" on page 331.
Activation: B92_ERROR_TRACKING = OUTLIM | ALL
Event text: OUTLIM ERROR FOR LIST
9208 (W)
ddname
Zero lines event: An event is generated when a list with 0 lines is
encountered during reading in.
Activation: B92_ERROR_TRACKING = ZLINES | ALL
Event text: LIST WITH [DECLARED] ZERO LINES
9211 (W)
ddname
Reader warning for large lists: An event is generated when a list with more
than num lines is encountered during reading in. For more information, see
"Large list monitoring and outlim processing" on page 331.
Activation: B92_RDR_THRESHOLD_LINES = num
Event text: SYSPRINT HAS n LINES - THRESHOLD EXCEEDED
9201 (I)
DD B92EVT event
Activation: Scan ID 9201
Event text: arbitrary (text from B92EVT)
nnnnn (I,W,E)
DD B92EVT event
Activation: Scan ID 9210
Event text: arbitrary (text from B92EVT)
9202 (I)
//*OMS EVT= in JCL
Activation: Scan ID 9202
Event text: your text from //*OMS EVT=your text card
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
327
Reader (Option A.R)
Event actions (Option A.R.6)
Event ID (Severity) Description
9206 (I)
//*OMS LNK/ in JCL
An event is generated based on the presence of //*OMS LNK/.
Activation: Scan ID 9206
Event text: //*OMS LNK/aaa/bbb/jcl.txt
9207 (I)
//*OMS DSN= in JCL
Activation: Scan ID 9207
Event text: //*OMS DSN=data.set.name
9209 (I)
*OMS EVT= in SCRIPT (EJM)
Activation: Scan ID 9209
Event text: your text from *OMS EVT=your text
9203 (I)
IWS special resource event (SRSTAT)
Activation: Scan ID 9203
Event text: From EQQMLOG message EQQZ015I
9204 (I)
_beta log|z batch utility end event
Activation: Scan ID 9204
Event text: From JESMSGLG message OMS1026I
9225 (I)
OMSMAIL event: Mail triggered by DD MAILOUT with initial OMSMAIL;
for more information, see "Triggering e-mail via DD MAILOUT" on page 339
Activation: Scan ID 9211
Event text: MAIL TRIGGERED BY MAILOUT
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
328
Reader (Option A.R)
Event actions (Option A.R.6)
Event ID (Severity) Description
9255 (I,W,E)
Health checker event
Activation: B92_HEALTH_CHECK = ON (Default)
Severity and event text depend on action and result
Database verification okay at STC start
I: DATABASE IS UP TO DATE
Database verification not okay at STC start
E: DATABASE IS NOT UP TO DATE
One additional event is generated for each database update that is missing.
E: DB UPDATE (member – location) IS NOT INSTALLED
LST parameter check okay at STC start
I: BETA 92 PARAMETERS COMPLY WITH BETA RECOMMENDATIONS
Potential LST parameter check warnings at STC start
W: BETA 92 PARAMETERS INCONSISTENT WITH BETA RECOMMENDATIONS
One additional event is generated for each offending LST parameter.
W: 001 BQL SPEEDMASTER DISABLED DUE TO BQL_SHARE_OPTION=ALL
W: 002 B92_RDR_MULTI_INSERT DISABLED DUE TO VALUE 1
9300 (I,E)
Automatic database extension event (BSA)
Activation: Always active (dataset ID not set by this event)
Severity and event text depend on result
DB extension successful
I: BQL DB ENLARGE SUCCESSFUL FOR file RC(rc) - NEWSIZE: new
(prev) USAGE: u % (m % OF MAX ALLOCATED)
DB extension failed
E: BQL DB ENLARGE **FAILED** FOR file RC(rc) - SIZE: current
USAGE: u % (m % OF MAX ALLOCATED)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
329
Reader (Option A.R)
Event actions (Option A.R.6)
Event ID (Severity) Description
9300 (I,W,E)
Automatic spool formatting event (BSA)
Activation: Always active (dataset ID not set by this event)
Severity and event text depend on result; warning threshold defined via
LST parameter BQL_SPOOLCHECK_MODEL=min
Spool formatting successful
I: NO. OF SPOOL MODELS(n) CYL(cyl_models) SPOOL FMT OK
DSN(dsname) CYL(cyl_ds)
Spool formatting successful, number of models remaining too low
W: NO. OF SPOOL MODELS(n) BELOW THRESHOLD (min)
CYL(cyl_models) SPOOL FMT OK DSN(dsname) CYL(cyl_ds)
Spool formatting failed
E: SPOOL FMT FAILED DSN(dsname) RC(rc) CYL(cyl_ds) REMAINING
MODELS(n) CYL(cyl_models)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
330
Reader (Option A.R)
Large list monitoring and outlim processing
Large list monitoring and outlim processing
Overview
_beta log|z provides several functions that help you monitor your system
for incoming large lists. Outlim processing prevents that lists that are too
large are read in at all.
Large list processing
Large lists are read in normally, but a warning message or a warning event
is generated for notification purposes. Data center personnel can act
according to the procedures established for large lists.
You can use the following methods to recognize large lists:
•
Warning message when list has n% of reader class outlim
If you code B92_OUTLIM_WARNING = n, the warning message
OMS1113W is output each time when a list is read in whose size is
between n% and 100% of the Outlim Line Number value specified in
reader definition. This parameter is honored by the JES reader, but not
by the OSY reader.
•
Warning message and event when list has more than n lines
If you code B92_RDR_EVT_THRESHOLD_LINES = n, the warning
message OMS1196W is output each time when a list is read in whose
size exceeds the specified number of lines. In addition, an event with
the event ID 9211 is created in the EVT00 table. This parameter is
honored by both the JES reader and the OSY reader.
The default for both LST parameters is not to generate any warnings.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
331
Reader (Option A.R)
Outlim processing
Large list monitoring and outlim processing
Lists that exceed the output limitation (outlim) are not read in.
You can use the following methods to specify an output limit:
•
In the reader class definition (option A.R.1), you can specify an output
limit in the Outlim Line Number field. This output limit (max. number
of lines) affects all lists that are processed by the JES reader via this
class.
Exception: JESMSGLG, JESJCL, and JESYSMSG are not affected
by outlim processing and B92_OUTLIM_WARNING.
For information on outlim processing of sysout lists, see "Sysout outlim
processing" on page 334.
•
In the agent definition, you can specify an output limit in the Outlim
field.
•
In _beta log|z: Option A.2.6
•
In _beta job|z: Option A.3
This output limit (max. size in MB) does not affect all lists that are
transferred by an agent. For information on which list are affected and
on how they are processed, see:
Events
•
"EJM agent job processing" on page 335
•
"EJM agent rule processing" on page 335
•
"SAP output processing" on page 337
You can make _beta log|z generate events to help you monitor outlim
processing and large lists. You can define an appropriate action for each
event type, for example, sending an e-mail notification. For more
information, see "Event actions (Option A.R.6)" on page 318.
Outlim event
For example, if the value of B92_ERROR_TRACKING includes OUTLIM,
an event with the event ID 09205 is generated in the EVT00 table when
outlim processing a list:
PE92EV20 --------------------------------------------------------------------Command ===> _________________________________________________________________
Display Event Information
Event Token
Input Date
Input Time
:
:
:
00DB005FE549E9B43200000008400001
2022-02-01
Processed Date
15:28:05
Processed Time
:
:
2022-02-01
15:28:06
Event ID
Severity
:
:
09205
W
Category
Source
:
:
HOSTJOB
BETA
Job Name
Job ID
System ID
:
:
:
REJ#EXT
USR32313
USR
Submit Date
Submit Time
Dataset ID
:
:
:
2022-02-01
15:28:00
00000104
Event Text
:
STDOUT
HAS
B92O0000
1.5 MB - OUTLIM ERROR
-
Press END key to return to previous menu or HELP key for help information.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
332
Reader (Option A.R)
Large list monitoring and outlim processing
Large-list event
For example, if B92_RDR_EVT_THRESHOLD_LINES = 1000000, an
event with the event ID 09211 is generated in the EVT00 table when a
large list is read in:
PE92EV20 --------------------------------------------------------------------Command ===> _________________________________________________________________
Display Event Information
Event Token
Input Date
Input Time
:
:
:
00CF3F6A038EF3CC4E00000001080001
2015-07-15
Processed Date
11:11:36
Processed Time
:
:
2015-07-15
11:11:36
Event ID
Severity
:
:
09211
W
Category
Source
:
:
HOSTJOB
BETA
Job Name
Job ID
System ID
:
:
:
IM#SEARC
J0028265
BETA
Submit Date
Submit Time
Dataset ID
:
:
:
2015-07-15
11:11:33
00000262
Event Text
:
PMSOUT
B92P.00
HAS
1113494 LINES - THRESHOLD EXCEEDED -
Press END key to return to previous menu or HELP key for help information.
In addition, a warning message is output in the JESMSGLG:
OMS1196W B92P.00 - THRESHOLD EXCEEDED - IM#SEARC(J0028265) PMSOUT
HAS 1113494 LINES
Member B92RP01J in the BETA92.SAMPLIB provides JCL for _beta
report to generate a report on the large-list events of a given day in the
EVT00 table.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
333
Reader (Option A.R)
Sysout outlim processing
Large list monitoring and outlim processing
If one or more sysout lists of a job are longer than the output limit, _beta
log|z does the following:
1. It places the job onto the Error queue with the error text OUTLIM.
2. It writes messages (OMS1114I or OMS1115I) to the operator console
informing the operator of this condition.
3. It requeues the affected sysout lists to the JES spool. Other lists of the
job are not affected by outlim processing, and are processed normally.
Sysout lists affected by outlim processing are written to the class
defined under Outlim Spool Class in the reader class definition.
These lists will appear under the original name of the job. Specify
Outlim Hold Sysout = Yes in the reader class definition if you want to
allocate this output with the Hold attribute.
4. It creates a one-page placeholder list for each list affected by outlim
processing. This placeholder list contains one of the following lines:
•
LIST WAS CHANGED BY OUTLIM PROC.
•
LIST WAS RE-ROUTED TO CLASS(outlim_spool_class).
Additional information
•
Outlim processing can also be handled by the user exit B92UXOLM
(see "B92UXOLM: Output limit exit" in _beta log|z Installation and
System Guide).
•
Outlim processing is also affected by the following LST parameters:
•
•
B92_RDR_OLM_DEST (change destination)
•
B92_RDR_OLM_FORM (change form)
•
B92_RDR_OLM_WTR (changes writer name)
If the _beta log|z started task has to requeue several large sysout lists
to the outlim spool class, JES may issue a warning message. This
message informs the operator that the _beta log|z started task has
exceeded output lines. (This is because JES counts each requeued
list as if it were output coming from the _beta log|z started task.)
Operators can ignore this JES message.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
334
Reader (Option A.R)
Large list monitoring and outlim processing
The agent definition in _beta job|z (Option A.3) specifies a maximum file
size in MB, which applies to:
EJM agent job
processing
•
STDOUT.EJM
•
STDERR.EJM (as of V7.1 Build 14)
•
JOBLOG.JBATCH
If a checked file is larger than the specified file size limit, this file is not
transferred to the host, but remains on the agent. The affected file is
moved from ../B48/ejfjobs/ssid/b48jobid to
../B48/outlimfiles/ssid/b48jobid and the suffix .outlim is added to the file
name, for example, STDOUT.EJM.outlim or STDERR.EJM.outlim.
A placeholder list is sent to _beta job|z and/or _beta log|z, which includes
information on the name, location and size of the original list.
Example of placeholder list:
L I S T
I N F O
I N S E R T E D
B Y
E J M
A G E N T
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
OMS1025I LIST WAS CHANGED BY OUTLIM.
ORIGINAL LIST WAS SAVED AS: /usr/path/subpath/B48/outlimfiles/B48P/0004851022/STDOUT.EJM.outlim
OUTLIM SIZE: 4 MB, LIST SIZE: 38.5 MB
EJM agent rule
processing
The output limit defined in the agent definition in _beta log|z (Option A.2.6)
applies to files that are sent to _beta log|z via rules.
When the file size exceeds the specified limit, the following happens:
•
Instead of transferring the original list, the EJM agent sends a job with
an OUTLIM list to _beta log|z. The corresponding rule has the error
status OUTLIM in _beta log|z.
•
The following message is written to the z/OS operator console and to
the agent log file to indicate outlim processing:
OMS1025I LIST WAS CHANGED BY OUTLIM
•
The list that exceeds the file size limit remains on the agent side.
Exceptions: The file size limit is ignored:
•
When sending endless file rules
•
By the programs EDF tracker and XBP2.0
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
335
Reader (Option A.R)
Log file processing
Large list monitoring and outlim processing
Affected log files remains on the agent side. They can be renamed
depending on the value of the Delete Log field in the operation definition
(option A.2.3).
If Delete Log=NO, the affected file preserves its original name. The agent
log contains the following information:
L I S T
I N F O
I N S E R T E D
B Y
E J M
A G E N T
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
OMS1025I LIST WAS CHANGED BY OUTLIM.
ORIGINAL LIST IS: /usr/path/myfile.txt
OUTLIM SIZE: 4 MB, LIST SIZE: 8.5 MB
If Delete Log=YES, the affected file is renamed to
original_filename.time_stamp.outlim. The agent log contains the
following information.
L I S T
I N F O
I N S E R T E D
B Y
E J M
A G E N T
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
OMS1025I LIST WAS CHANGED BY OUTLIM.
ORIGINAL LIST WAS SAVED AS: /usr/path/myfile.txt.1208508900.outlim
OUTLIM SIZE: 4 MB, LIST SIZE: 8.5 MB
Note: Files with the extension *.outlim are never sent to _beta log|z, even
if a rule using wildcards matches the file name. Files with the extension
*.outlim must be deleted manually on the agent side.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
336
Reader (Option A.R)
SAP output processing
Large list monitoring and outlim processing
The output limit affects SAP spools, child jobs, application logs and job
logs (via SAP job log rules), SAP security audit logs (via SAP audit log
rules) and SAP system logs (via SAP system log rules). Affected output
remains in the SAP system. The EJM agent sends a placeholder list to
_beta log|z, which includes information on the affected output, its size, and
its location in the SAP system.
Important: Do not combine Delete Log and Outlim. Delete Log would
cause the deletion in SAP of affected output, which means that the output
would be lost.
The output limit does not affect the SAP system log. Due to an SAPspecific default, only 80 pages can be transferred per select in case of an
SAP system log. Endless logs are never affected.
During the transfer, the SAP system log is separated into parts due to a
time-specific criterion set in SAP. Each of the parts will be checked
separately. If a part is greater than the defined limit, the agent sends a
placeholder list with the following message (here: for SAP spools):
L I S T
I N F O
I N S E R T E D
B Y
E J M
A G E N T
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
OMS1025I LIST WAS CHANGED BY OUTLIM.
ORIGINAL LIST CAN BE FOUND IN THE SAP SYSTEM.
OBJECTNAME: SPOOL0000014617
, JOB: CHKB48S2/15103600
OUTLIM SIZE: 4 MB, LIST SIZE: 7.5 MB
For SAP spools, the name of the original spool is displayed. The original
spool is available in the SAP system and will then not be transferred by the
agent.
For SAP logs, the following message is issued:
L I S T
I N F O
I N S E R T E D
B Y
E J M
A G E N T
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
OMS1025I LIST WAS CHANGED BY OUTLIM.
ORIGINAL LIST CAN BE FOUND IN THE SAP SYSTEM.
OUTLIM SIZE: 4 MB, LIST SIZE: 4.5 MB
For SAP job logs and SAP application logs, the message contains a note
to the log:
L I S T
I N F O
I N S E R T E D
B Y
E J M
A G E N T
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
OMS1025I LIST WAS CHANGED BY OUTLIM.
ORIGINAL LIST CAN BE FOUND IN THE SAP SYSTEM.
JOB: CHKB48S2/15103600
OUTLIM SIZE: 4 MB, LIST SIZE: 4.5 MB
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
337
Reader (Option A.R)
Large list monitoring and outlim processing
For SAP security audit logs, the message contains the time period of the
selection:
L I S T
I N F O
I N S E R T E D
B Y
E J M
A G E N T
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
OMS1025I LIST WAS CHANGED BY OUTLIM.
ORIGINAL LIST CAN BE FOUND IN THE SAP SYSTEM.
SELECT SECURITY AUDITLOG FROM 19.02.2019/05:08:04 TO
19.02.2019/06:08:03
OUTLIM SIZE: 4 MB, LIST SIZE: 6.5 MB
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
338
Reader (Option A.R)
Triggering e-mail via DD MAILOUT
Triggering e-mail via DD MAILOUT
Overview
It is possible to trigger the sending of e-mail by including a dataset with
appropriate instructions under the DD name MAILOUT in your job step.
You can include _beta view links to any log of the corresponding job
(except DD MAILOUT) in the generated e-mail message or you can send
the job logs as attachment.
Processing
The reader generates a so-called OMSMAIL event (ID 9225) when it
encounters a job step that has a DD MAILOUT job log with the OMSMAIL
eyecatcher in line 1, for example:
//MAILIN
DD *
OMSMAIL
your OMSMAIL parameters
/*
The mailing router monitors the event table at regular intervals for new
OMSMAIL events. If present, the mailing router generates e-mail
according to the instructions contained in DD MAILOUT of the
corresponding job.
The mailing router retrieves the following parameters from the global
options (Option A.S.3):
•
Address and port of the SMTP server
•
Default character translation table
•
Settings for generating web links
•
Disclaimer text
Note: The _beta log|z mailing router is unable to work if the database is
shared with BQL_SHARE_OPTION=ALL (see "Event processing" on
page 324).
LST parameters
The mailing router is controlled via the following LST parameters:
Parameter name
Value
Description
B92_MAILR_INTERVAL
4..180
Specifies how frequently the mailing router
Optional
checks the event table for new OMSMAIL events
(ID interval in seconds)
4
Optional
4
Optional
YES
B92_MAILR_TOKENDELAY 4..60
Specifies the minimum age (in seconds) of the
selected OMSMAIL events
Opt./Req. Default
Specifying an appropriate delay ensures the
availability of the job output in the database at
the time when the OMSMAIL event is processed.
B92_MAILR_ALLOW_
ATTACH
YES | NO
Controls whether the mailing router allows the
sending of attachments
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
339
Reader (Option A.R)
Triggering e-mail via DD MAILOUT
Parameter name
Value
Description
Opt./Req. Default
B92_MAILR_BODY_SIZE
n
Limits the maximum size of the specified body
text to n bytes (max. 32000)
Optional
MAILOUT syntax
32000
The MAILOUT dataset contains processing instructions for generating an
e-mail message.
The following syntax rules apply to the contents of the MAILOUT dataset:
•
The word OMSMAIL must be coded at line 1 column 1.
•
Optionally, the encoding of the MAILOUT dataset can be specified at
line 1 column 9 using the following parameter:
CCSID=code_page_number
where code_page_number is the max. 4-digit number of the CECP
codepage. No blanks are allowed between the parameter name and
value.
Default: Encoding specified in Translation Table field under
option A.S.3
•
Code the remaining parameters on the following lines using the
following syntax:
•
All parameter names are case-sensitive.
•
Each parameter must be coded on a separate line. The parameter
name must be coded at column 1 of the line and it must be directly
followed by a colon (no blanks allowed).
•
The parameter value must be coded on the same line.
Exception: The value of the Body parameter (i.e. the body text) is
coded below the Body: line. Don't code any text following Body:
if you want to send an empty message.
•
The sequence of parameters is arbitrary.
Exception: The Body parameter must be the last parameter in the
MAILOUT dataset.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
340
Reader (Option A.R)
Triggering e-mail via DD MAILOUT
OMSMAIL parameters
Parameter name
Description
Opt./Req.
From:
From e-mail address
Required
Reply-To:
Reply-to e-mail address
Optional
To:
To e-mail address
Required
This parameter can be specified up to 16 times.
Cc:
Copy e-mail address
Optional
This parameter can be specified up to 16 times.
Subject:
Subject of the e-mail message
Required
Attach:
Adds job output as attachment
Optional
Specify as value ddname.stepname to identify the
job output that you want to include. Mask characters
( * % ? ) are allowed. Asterisk is assumed for the
step if you don't specify a name.
This parameter can be specified up to 16 times.
Attachtype:
Determines the type of attachment
Optional
Allowed: LIST | ZIP (default)
Link:
Adds _beta view links to the job and to job output
Optional
Specify as value ddname.stepname to identify the
job output that you want to include. Mask characters
( * % ? ) are allowed. Asterisk is assumed for the
step if you don't specify a name.
This parameter can be specified up to 16 times.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
341
Reader (Option A.R)
Triggering e-mail via DD MAILOUT
Parameter name
Description
Opt./Req.
Signature-DD:
Identifying suffix of the PO dataset that contains the Optional
signature members
This PO dataset must be allocated by the _beta
log|z STC. The DD name must be B92S plus suffix
(min. length: 1, max. length: 4; allowed: A-Z, 0-9, $,
#, §)
Default: B92SLIB
Signature-Member:
Name of the signature member
Optional
Signature-Codepage:
Encoding of the signature member
Optional
Specify the max. 4-digit number of the CECP
codepage (like CCSID=code_page_number)
Default: Same as CCSID=code_page_number
Body:
Indicates the beginning of the body text
Required
The body text is coded below the Body: line. Don't
code any text following the Body: line if you want
to send an empty message.
Example
The following instructions are for an e-mail with several links:
//MAILIN
DD *
OMSMAIL CCSID=273
From: b92admin@betasystems.com
To: techdoc@betasystems.com
Subject: Links to OMSMAIL job
Link: MAILREJ1
Link: MAILREJ2
Signature-Member: B92DFLT
Body:
Following are links to the job and to two logs.
/*
The generated e-mail body has the following structure:
1. Text from Body: parameter
2. Job URL:
_beta view link to job
3. List URL:
_beta view link to first list
_beta view link to second list
4. -5. Text from signature member
6. Disclaimer text if defined in global options (Option A.S.3)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
342
Reader (Option A.R)
Error and warning
messages
Triggering e-mail via DD MAILOUT
Parameters are checked for validity. A job message record with an
appropriate error or warning text is created for each problem detected.
_beta log|z tries to pass all mailing requests to the mailserver regardless.
The job message record contains a warning text when the detected
problem typically does not prevent the sending of the e-mail message. For
example, warnings inform about unknown parameters (which are ignored)
and values that are too long (which are truncated).
The job message record contains an error text when the detected problem
typically prevents the sending of the e-mail message. If the mailserver can
be reached and the From: parameter is valid, the mailserver may send an
error mail in this case.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
343
Database (Option A.D)
In this chapter
Database (Option A.D)
In this chapter
Topic
Page
Which databases are available?............................................................. 345
_beta log|z database components.......................................................... 346
What happens when a database becomes full?..................................... 350
Databases (Option A.D.1) ...................................................................... 351
Defining spool files.............................................................................. 355
Updating spool files ............................................................................ 357
Displaying database information ........................................................ 359
Dictionary (Option A.D.2) ........................................................................ 362
Displaying tables (Option A.D.2.1) ..................................................... 363
Displaying keys (Option A.D.2.2) ........................................................ 368
Displaying fields (Option A.D.2.3) ....................................................... 370
Displaying system databases (Option A.D.2.4) .................................. 371
Database usage statistics (Option A.D.3) .............................................. 373
Statistic values (Option A.D.3.1) ......................................................... 374
Displaying daily or hourly statistics ..................................................... 375
Statistic batch reports (Option A.D.3.2) .............................................. 376
Fields in the statistics panels .............................................................. 378
Fields for the RPGPRINT, RPGWORK, RPTRUN and RPTLIST
options ....................................................................................... 381
Deleting obsolete statistics data (Option D.3.3) ................................. 382
Database queries (Option A.D.Q)........................................................... 383
Generating JCL for database utilities (Option A.D.4) ............................. 385
BSA Service Manager (Option A.D.S) .................................................... 388
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
344
Database (Option A.D)
Which databases are available?
Which databases are available?
Overview
Option D - Database in the "Administration Selection Menu" enables you to
display the "Service and Database Selection Menu". Under this option, you
can display the databases used. The following section describes the
databases and the corresponding panels.
Option A.D of the "Primary Selection Menu" is to display the databases in
use. You can delete and add spool files. _beta log|z offers communication
through BQL language.
_beta log|z uses internally formatted VSAM ESDS datasets to store data.
All descriptions of fields, tables and keys are stored in the definition file
BETA92.DB.DEF. The use of mirror databases is optional. File mirroring
provides a high level of reliability and quick recovery in case of DASD
media failures. The mirror files are maintained as parallel copies of the
original files.
The connections between the logical and the physical data names are
defined in the database description.
Fields and tables
A field is defined by its name, its type (character, integer, small integer,
byte or flag) and its internal and external length.
A table is a collection of fields which are assigned to a logical file name
and, if necessary, to a logical key file name.
A table may own one or more keys to accelerate the access to the
individual records in the table.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
345
Database (Option A.D)
_beta log|z database components
_beta log|z database components
Overview
This section describes the datasets of the _beta log|z database.
The following table uses BETA92.DB as high-level qualifier of the dataset
names.
Datasets
Dataset name
Short name Description
BETA92.DB.ARCH.DATA
ARCDATA
Contains information about the archive datasets
and the archive volumes
BETA92.DB.ARCH.KEY
ARCKEY
Contains the keys (pointers) of the ARCH.DATA
database
BETA92.DB.ARCHINF.DATA
ARCIDATA
Contains product-specific archive information
BETA92.DB.ARCHINF.KEY
ARCIKEY
Contains the keys (pointers) of the
ARCHINF.DATA database
BETA92.DB.ARCHyyyy.Gnn
GARDATnn Contains information about archived jobs, where
yyyy specifies the year and nn the generation
number
See "GAR databases" on page 348 for more
details.
BETA92.DB.CLNT.DATA
CLNTDATA Contains information on the configuration and
status levels of EJM agents; also contains _beta
log|z product-specific statistics
Note: The tracing of statistics data cannot be
disabled due to internal requirements.
BETA92.DB.CLNT.KEY
CLNTKEY
Contains the keys (pointers) of the CLNT.DATA
database
BETA92.DB.DEF
B92DEF
Contains the definitions (databases, tables, keys,
and fields) for the entire _beta log|z database
BETA92.DB.EVT.DATA
EVTDATA
Contains the _beta log|z events that are displayed
under option E
BETA92.DB.EVT.KEY
EVTKEY
Contains the keys (pointers) of the EVT.DATA
database
BETA92.DB.EXT.DATA
EXTDATA
Contains information on jobs from other platforms
(long job name, fully-qualified hostname, long user
name)
See "Job extension database" on page 348 for
more details.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
346
Database (Option A.D)
_beta log|z database components
Dataset name
Short name Description
BETA92.DB.JOB.DATA
JOBDATA
Contains information about all of the job logs and
sysout lists under control of _beta log|z
BETA92.DB.JOB.KEY
JOBKEY
Contains the keys (pointers) of the JOB.DATA
database
BETA92.DB.LGF.DATA
LGFDATA
Contains information that is used in connection
with _beta smf
BETA92.DB.LGF.KEY
LGFKEY
Contains the keys (pointers) of the LGF.DATA
database
BETA92.DB.LOG.DATA
LOGFILE
Contains logging information for recovery
See "LOG database" on page 348 for more details.
BETA92.DB.MAIN.DATA
MAINDATA
Contains information on the system configuration,
which is necessary to utilize the job base records,
submit/start/end times, the Job Group data and list
scanning record information
BETA92.DB.MAIN.KEY
MAINKEY
Contains the keys (pointers) of the MAIN.DATA
database
BETA92.DB.SPOOLnn.DATA
SPnnnnnn
Contains job logs and SYSOUT lists
See "Spool datasets" on page 349 for more details.
BETA92.DB.STAT.DATA
B92STAT
Contains statistical information
BETA92.DB.SYNC.DATA
SYNCFILE
Control access to the product database
There is no need to save the SYNC file.
BETA92.DB.YXT.DATA
YXTDATA
Contains extended job information and user profile
information for layouts
BETA92.DB.YXT.KEY
YXTKEY
Contains the keys (pointers) of the YXT.DATA
database
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
347
Database (Option A.D)
GAR databases
_beta log|z database components
Generation archive (GAR) databases contain information about archived
jobs.
Your first GAR databases have been allocated as part of the installation
procedure. Each generation of this database is meant to hold the archived
job records of one year. At the end of each year, create a new GAR
database generation for the coming year.
For more information, see "Working with generation archive (GAR)
databases" on page 195.
GAR dataset size
An archive generation database requires the following space:
80 cylinders for 1,000 jobs per day
800 cylinders for 10,000 jobs per day
etc.
The minimum size is 20 cylinders.
Job extension database
The EXT.DATA database is an extension to the JOB database.
The database component EXTDATA contains the job extension records,
which are used to store additional information for jobs from other platforms
(long job name, fully-qualified host name, long user name). Use these
guidelines when determining space required for EXTDATA:
•
For each 10 000 jobs, allocate 57 cylinders on a 3390 DASD volume.
This is only an approximate size. The space needed depends on the
number of JBRE user fields you are planning to use.
If you are not reading in data from other platforms, you can make this
database very small.
LOG database
The LOG database is used by BSA for storing recovery information when
data is updated in the database files.
The usage of LOG.DATA should be monitored because the amount of
space required will grow with the number of database files, for example,
when new GAR databases are added over the course of time.
Secondary space recommended
LOG.DATA should be allocated with secondary space.
We recommend the following values (in cylinders):
Primary space:
90
Secondary space: 5
If necessary, plan on reallocating LOG.DATA with secondary space during
a maintenance window. You can tailor an appropriate job using option
A.D.4. All database access must be stopped when you run the RE-ALLOC
job. There is no need to save the contents of the LOG database before
reallocation.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
348
Database (Option A.D)
Spool datasets
_beta log|z database components
Spool datasets contain job logs and SYSOUT lists. _beta log|z writes job
logs and SYSOUT lists in compressed form to the spool datasets. This can
save up to 70% space on DASD.
Data compression also provides a high degree of security against
unauthorized access. Spool datasets can only be read by the _beta log|z
programs.
One spool dataset is allocated as part of the installation procedure. Use
the _beta log|z ISPF application (option A.D.1) to define model spool
datasets, which will be allocated and formatted automatically when
needed.
_beta log|z automatically switches spool datasets when the current dataset
runs full. It automatically allocates additional spool datasets based on the
model spool datasets when all datasets run full.
Spool dataset size
We recommend that you use a small number of large spool datasets rather
than a large number of small spool datasets. (Using a small number of
spool datasets will reduce the time required by batch jobs to allocate the
datasets.)
The first spool dataset is allocated by job B92DBFOR. The name and size
of this dataset is specified while running the installation REXX and tailored
accordingly in member S#92UDEF in the CNTL library. You can check and
if necessary modify the specifications in this member before running
B92DBFOR. The size for additional spool datasets is specified online
when defining model spool datasets.
For best performance, a CIsize of 4K is recommended for _beta log|z
spool datasets.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
349
Database (Option A.D)
What happens when a database becomes full?
What happens when a database becomes full?
Overview
When the used space of a dynamic database reaches a critical level (high
water mark minus 1 percent), it is extended automatically. For more
information on dynamic databases, see "Dynamic database extension" in
BSA Installation and System Guide.
If a database is not dynamic, warning messages of the following type are
written to the console when used space reaches a critical level (high water
mark):
OMS9550W HIGH WATER MARK REACHED nn%/datasetname
The high water mark is typically defined at 90 percent, which means that
this type of message occurs when free space drops below 10 percent.
If a database is in danger of running full, stop the JES reader and make
extra space available, for example, by running the daily maintenance job
B92DAILY or by enlarging the database in question. The _beta log|z
Installation and System Guide describes how to enlarge a database.
Note
You can see in the "Data Set Definition Selection" panel how much space
is available in each _beta log|z database.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
350
Database (Option A.D)
Databases (Option A.D.1)
Databases (Option A.D.1)
1. When you select option A.D - Database of the "Primary Selection
Menu", the "Service and Database Selection Menu" is displayed:
Procedure
PEB5DA00 ---------------------------------------------------------------------Option ===> __________________________________________________________________
Service and Database Selection Menu
System
- B92PROD
Location - BERLIN
Subsys-ID - B92P
User ID
- AVSCHM
1
DATABASE
-
Display or Update System Database
2
DICTIONARY
-
Display Dictionary Information
3
STATISTICS
-
Statistics of Database Usage
4
UTILITIES
-
Generate Batch Jobs for Database Maintenance
Q
QUERY
-
Database Query
S
SERVICE
-
Service Manager
Parameter for Option 1 and 2 :
Display numeric values with leading zeros ===> YES
(Y)es, (N)o
Select one of the above options. Press END to return to the previous menu.
2. Choose option 1 - Database to display a list of all _beta log|z
databases or to create, modify or delete spool files.
When you select option 1 - Database, the "Data Set Definition
Selection" table is displayed:
PEB5DD10 ---------------------------------------------------- Row 1
of 55
Command ===> ________________________________________________ Scroll ===> PAGE
Dataset Definition Selection
Databases for Subsystem SSID B92P
I - Insert Model
S - Select Dataset Definition or
Update Model or Status
X - Database Extension
Sel
Fields
Dataset Name
BETA92.DB.DEF
BETA92.DB.EVT.DATA
BETA92.DB.EVT.KEY
BETA92.DB.EXTDATA
BETA92.DB.GARD01
BETA92.DB.GARD02
BETA92.DB.JOB.DATA
BETA92.DB.JOB.KEY
BETA92.DB.LOG.DATA
BETA92.DB.MAIN.DATA
BETA92.DB.MAIN.KEY
Page 1 of 3
( LEFT/RIGHT )
SYSVAR Support : INACTIVE
F - Format Model
D - Delete Model or Empty
R - Reset Model (ERR)
RX - Reset Database Extension (FEX)
X Total
Free
% Sta
00000900 00000739 017 OPN
00003600 00001790 050 OPN
00001800 00001744 003 OPN
00007200 00007118 001 OPN
00001800 00001737 003 OPN
00001800 00001523 015 OPN
00001980 00001770 010 OPN
00001800 00001742 003 OPN
00001800 00001226 031 OPN
00001800 00001293 028 OPN
00000900 00000853 005 OPN
Field
Description
SYSVAR Support
The status of the SYSVAR support is displayed here (active
or inactive). Static system symbols are used to represent
fixed values such as system names and sysplex names.
For information on activating SYSVAR support, see "Static
system symbol support" in BSA Installation and System
Guide. _beta log|z does not support SYSVAR.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
351
Database (Option A.D)
Columns
Databases (Option A.D.1)
Column
Description
Data Set Name
The name of the z/OS dataset is shown here. All datasets
are VSAM/ESDS organized.
X
Y in this column indicates the presence of database
extensions based on concatenated datasets (EXT01,
EXT02 etc.). The current BSA version provides only limited
support for this type. While it is possible to continue to work
with the existing database, the current BSA version does
not support any further extension.
Important: It is no longer meaningful to work with
concatenated VSAM datasets because BSA (as of V4)
supports the so-called "extended VSAM datasets", which
enable a total maximum size of 28 GB for BQL databases.
If you are still working with concatenated datasets, include
the task of merging these datasets when planning your
database maintenance.
Total
Size of the dataset in 4K blocks.
Free
Total number of free 4K blocks.
%
Percentage of 4K blocks currently used. When 90 % is
used, a warning is issued.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
352
Database (Option A.D)
Databases (Option A.D.1)
Column
Description
Status
The Status column can contain one of the following entries:
CLS
(Closed) Dataset could not be opened
EMP
(Empty) Dataset is empty
A dataset gets the status EMP (empty) after the
online retention period of all lists has expired. You
may delete this dataset with the line command D.
However, this command will not physically delete
the dataset.
ERR
(Error) Dataset is in error
FMT
(Format) Spool file is being formatted
FUL
(Full) Dataset is full
If there is no more space to store any lists, the
started task sets the status to FUL automatically
and switches to the next available dataset.
MOD
(Model) Spool file in status model
The dataset is not yet allocated. A dataset with the
status MOD is used to allocate new datasets.
OPN
(Open) Dataset is open
ONL
(Read only) Dataset is read-only
FEX
Format extend error
Note: For information on deleting a database, see "Notes
on model spool file definitions" in BSA Installation and
System Guide. Only databases in status MOD, EMP, ERR,
or FMT can be deleted.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
353
Database (Option A.D)
Line commands
Databases (Option A.D.1)
I
Inserts a new spool file
F
Allocates and formats a spool model
The dataset must be a spool file with status MOD (model).
S
Selects the dataset for display or update
If you select a spool dataset with the status EMP (empty),
OPN (open), FUL (full), or ONL (read-only), the "Data Set
Definition Status Update" panel will be displayed; you may change
the read-only status of this spool dataset.
If you select a spool dataset with the status MOD (model), the
"Spool Model Definition Update" panel will be displayed; you may
change SMS entries, volume specifications, the size of the control
blocks and the assumed space allocation requirements. If you
select a spool file with a different status or if you select any other
dataset, you cannot make any changes at all.
D
Deletes an empty spool file with the status EMP (empty) or MOD
(model)
The status of the dataset is set to ONL (read only); you have to
confirm deletion in the additional panel which will be displayed.
Note: This line command is disabled when database sharing is
active.
R
Resets the status of a spool file with the status ERR (error) to MOD
(model)
Note: Use this command only if the error occurred because the
dataset could not be allocated.
X
Starts the dynamic database extension manually
This command is only available for dynamic databases. This
means that the database must fulfill the following conditions:
•
Type is DA (DATA) or KE (KEY)
•
Secondary space has been defined or volume candidates are
available or both
Maximum size: BQL databases support a total maximum size of
4 GB for a standard VSAM dataset and of 28 GB for an extended
VSAM dataset. Extended VSAM datasets are defined via the SMS
data class.
RX
Resets FEX status (FEX = Format EXtend error; this status is set if
the dynamic database extension fails)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
354
Database (Option A.D)
Databases (Option A.D.1)
Defining spool files
1. In the "Data Set Definition Selection" table, enter line command I in
front of a spool dataset to display the "Insert Model Definition":
Procedure
PEB5DDR3 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Insert Model Definition
Product
===> ________
SYSVAR Support : INACTIVE
Data Set Name
===> .......................................
Data Set Type
===> SP
(SP - Spool)
4 KB blocks
===> 1
(1-7, for CIsize)
Volume
===> ......
Space Allocation Requirements:
Primary Space
===> ...... (Cylinders)
If managed by SMS:
MGMTCLAS ===> ________
STORCLAS ===> ________
DATACLAS ===> ________
Press the ENTER key to confirm your request.
Press the END key to abort your request and to return to the previous panel.
2. Enter your definitions.
Fields
Field
Description
Product
The Beta product you are working with.
SYSVAR Support
The status of the SYSVAR support is displayed here (active
or inactive). Static system symbols are used to represent
fixed values such as system names and sysplex names.
For information on activating SYSVAR support, see "Static
system symbol support" in BSA Installation and System
Guide. _beta log|z does not support SYSVAR.
Data Set Name
This parameter refers to the VSAM file name of a _beta
log|z database and must conform with z/OS naming
conventions.
Data Set Type
The dataset type must always be Spool. Other dataset
types are not used.
4 KB blocks
Specify the size of the VSAM control interval (CI) by
entering the number of 4K blocks which should be used.
You may enter a value between 1 and 7.
Volume
Specify the volume which is to be used. When SMS is
specified here, the assignment of a volume or a unit is left
to the SMS.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
355
Database (Option A.D)
Databases (Option A.D.1)
Field
Description
Space Allocation
Requirements:
Primary Space
Specify the dataset size in cylinders (legal values: 1
through 9999).
We recommend that you use a small number of large spool
files rather than a high number of small spool files. If
warranted by your system load, you could make each spool
files as large as the respective disk. See the _beta log|z
Installation and System Guide for further information on
spool files.
If managed by SMS: Management and storage class or data class have to be
specified only if you use SMS:
MGMTCLAS
Enter the z/OS MGMTCLAS parameter.
STORCLAS
Enter the z/OS STORCLAS parameter.
DATACLAS
Enter the z/OS DATACLAS parameter. If you have
specified management class and storage class, you may
leave this field blank.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
356
Database (Option A.D)
Databases (Option A.D.1)
Updating spool files
Spool files with status
MOD (model)
1. In the "Data Set Definition Selection" table, enter line command S in
front of a spool file with the status MOD (model). The " Update Spool
Model Definition" panel is displayed.
PEB5DDR4 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Update SPOOL Model Definition
Product
: B92
SYSVAR Support : INACTIVE
Data Set Name
: BETA92.VSAM.SPOOL10.DATA
Short Name
: SP000057
4 KB blocks
===> 1
(1-7, for CIsize)
Volume
===> SMS...
Space Allocation Requirements:
Primary Space
===> 001000 (Cylinders)
Type
Data Set Status
File ID
: 00057
If managed by SMS:
MGMTCLAS ===> MC#STD__
STORCLAS ===> STC#PROD
DATACLAS ===> ________
: SP
: MOD
Press the ENTER key to confirm your request.
Press the END key to abort your request and to return to the previous panel.
2. Enter your definitions.
Spool files with status
EMP, OPN, FUL, or ONL
1. In the "Data Set Definition Selection" table, enter line command S in
front of a spool file with the status EMP (empty), OPN (open), FUL
(full), or ONL (read-only). The "Update Data Set Definition Status"
panel is displayed:
PEB5DDR5 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Update Status of Data Set Definition
Product
: B92
SYSVAR Support : INACTIVE
Data Set Name
: BETA92.VSAM.SPOOL07.DATA
Short Name
: SP000054
CIsize
: 04096
Volume
: SMS
Space Allocation Requirements:
Primary Space
: 001000 Cylinders
Type
: SP
Data Set Status
: EMP
Data Set Status Readonly ===> YES
File ID
: 00054
If managed by SMS:
MGMTCLAS
: MC#STD
STORCLAS
: STC#PROD
DATACLAS
:
(Y)es,(N)o
Press the ENTER key to confirm your request.
Press the END key to abort your request and to return to the previous panel.
2. Enter your definitions.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
357
Database (Option A.D)
Fields
Databases (Option A.D.1)
Field
Description
Short Name
The short name of spool files consists of the letters SP and
the file ID (nnnnnn).
File ID
The file ID is automatically assigned by the system.
Type
SP indicates a spool file.
Data Set Status
MOD indicates that the spool file has the status MOD
(model).
The status of the dataset may be EMP (empty), OPN
(open), ONL (read only) or FUL (full).
Data Set Status
Read only
Enter YES to change the status of the dataset to ONL
(=read-only). Utilities are able to delete lists from the spool
during cleanup, but no new lists will stored in this spool.
Entering NO removes the read-only status.
Notes
When you change the status of one or several spool
datasets to READ ONLY and you want this change to take
effect immediately, you must restart the _beta log|z readers
(F stcname,RES RDR).
Read-only spool files are always checked at startup to
ensure the deletion of unused reader blocks, irrespective of
the value of the LST parameter BQL_SPOOLCHECK.
The other fields are described in "Defining spool files" on page 355.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
358
Database (Option A.D)
Databases (Option A.D.1)
Displaying database information
Procedure
1. In the "Data Set Definition Selection" table enter line command S in
front of a database file.
The "Display Data Set Information" panel is displayed.
PEB5DD21 --------------------------------------------------------- Page 1 of 3
Command ===> _________________________________________________________________
Display Data Set Information
Product
Data Set Name
: B92
: BETA92.VSAM.JOB.DATA
Database Information
Short Name
CI Size
High Alloc RBA
High Used RBA
: JOBDATA
: 04096
: 0000021600
: 0000021600
Cache Buffer
: 00003000
Type
Data Set Status
High Water Mark
Warning Threshold
: DA
: OPN
===> 91 Percent
: 03000 Cyl.
SYSVAR Support : INACTIVE
File ID
: 00036
I/O-Read
I/O-Write
I/O-Requests
Caching
Allocated
: 0000013896
: 0000043288
: 0000630787
: 091 Percent
: 004 Percent
Press DOWN to display the next page or END to return to the previous panel.
2. Press PF8 to display the next panel:
PEB5DD22 --------------------------------------------------------- Page 2 of 3
Command ===> _________________________________________________________________
Display Data Set Information
Product
Data Set Name
VSAM Information
Catalog Name
Cluster Name
Data Name
Extended VSAM File
Space Information
Primary Space
Secondary Space
Total Space
Number of Extents
SMS Information
MGMTCLAS
: MC#STD
: B92
: BETA92.VSAM.JOB.DATA
SYSVAR Support : INACTIVE
: CATALOG.MVSICF1.VOMS
: BETA92.VSAM.JOB.DATA
: BETA92.VSAM.JOB.DATA.DATA
: NO
: 000005
: 000002
: 000011
: 003
Cylinders
Cylinders
Cylinders
STORCLAS
Record Length
Records per Track
Tracks per Cylinder
: STC#B92
DATACLAS
: 04096
: 00012
: 00015
:
Press DOWN / UP to display the next / previous page or END to return.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
359
Database (Option A.D)
Databases (Option A.D.1)
3. Press PF8 to display a third panel:
PEB5DD23 --------------------------------------------------------- Page 3 of 3
Command ===> _________________________________________________________________
Display Data Set Information
Product
Data Set Name
: B92
: BETA92.VSAM.JOB.DATA
Volume Information
Number of Volumes
: 01
SYSVAR Support : INACTIVE
Number of Volume Candidates
: 00
Vol_01 Vol_02 Vol_03 Vol_04 Vol_05 Vol_06 Vol_07 Vol_08 Vol_09 Vol_10
OMS030
Press UP to display the previous page or END to return to the previous panel.
Fields
Field
Description
Product
Beta Systems product you are working with.
Data Set Name
This parameter refers to the VSAM file name of a _beta
log|z database and must conform with z/OS naming
conventions.
SYSVAR Support
The status of the SYSVAR support is displayed here
(active or inactive). Static system symbols are used to
represent fixed values such as system names and
sysplex names. For information on activating SYSVAR
support, see "Static system symbol support" in BSA
Installation and System Guide. _beta log|z does not
support SYSVAR.
Database Information
fields
The short name used by the system, the unique file ID
number used by the system, the size of the VSAM
control interval (CI size), the number of the highest
allocated relative byte address, and the number of the
highest relative byte address in use are displayed.
Cache Buffer
The 8-digit number of 4K-storage buffer for performance
improvement.
Type
Indicates the type of database:
DA (DATA): Data file
KE (KEY): Key file
SY (SYNC): Synchronization file
LO (LOG): Log file
NO (DEF): Definition file
SP (SPOOL): Spool file
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
360
Database (Option A.D)
Databases (Option A.D.1)
Field
Description
Data Set Status
The dataset status can be: CLS (closed), EMP (empty),
ERR (error), FMT (format), FUL (full), MOD (model),
ONL (read only), OPN (open), or FEX (format extend
error).
High Water Mark
High water mark (in percent)
As of BSA 1771-03, this value can be changed
dynamically.
Warning threshold/
Allocated
These values are displayed only if the optional
MAXSIZE value has been defined for this database in
the database definition file:
Warning threshold is a user-defined value (in cylinders)
which can be used to monitor the growth of dynamic
databases when extends are formatted (messages
OMS9549I and OMS9549W).
Allocated displays the amount of allocated space (in
percent) in relation to the warning threshold.
I/O-Read
number of database read access
I/O-Write
number of database write access
I/O-Req.
complete number of database requests (I/O-Read, I/OWrite, Caching)
Caching
database access displayed in percentage points, the
access processed via the speed master and not via the
database is shown.
VSAM Information
fields
The name of the VSAM catalog, the name of the VSAM
cluster, and the name of the VSAM cluster with the type
DATA.
Space Information
fields
The primary and secondary space requests in cylinders,
the maximum length of dataset records, the number of
records per track, the totally allocated space in
cylinders, the number of tracks per cylinder, and the
number of extents in use are displayed.
SMS Information fields
SMS information on SMS management classes
(MGMTCLAS), SMS storage classes (STORCLAS), and
SMS data classes (DATACLAS) is displayed.
Volume Information
fields
The number of defined volumes, the number of unused
volumes (candidates), and the volser number (1 - 10) of
the volume on which the dataset is located are
displayed.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
361
Database (Option A.D)
Dictionary (Option A.D.2)
Dictionary (Option A.D.2)
Navigation
Enter option A.D.2 in the "Primary Selection Menu" to display the
"Dictionary Selection Menu":
PEB5DI00 ---------------------------------------------------------------------Option ===> __________________________________________________________________
Dictionary Selection Menu
1
TABLES
-
Display Table Definitions
2
KEYS
-
Display Key Definitions
3
FIELDS
-
Display Field Definitions
4
DATABASE
-
Display System Database
( Summary Information )
System
- B92PROD
Location - BERLIN
Subsys-ID - B92P
User ID
- AVSCHM
Select one of the above options. Press END to return to the previous menu.
Primary commands
SORT col1[,A|D col2,A|D
col3,A|D]
Sorts the displayed table in
ascending (A) or descending (D)
order in accordance with the
specified column(s) (col1, col2, col3)
A list of the column names is
displayed in the help panel.
SORT
Displays a help panel for the SORT
command for the displayed table.
TPRINT
Prints the displayed table. You can
determine where you want to print in
the panel TPRINT Parameter which is
displayed when you enter the
command in the command line.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
362
Database (Option A.D)
Dictionary (Option A.D.2)
Displaying tables (Option A.D.2.1)
Procedure
•
Enter option 1 to display the "Database Table Display" panel, which
displays information about all tables defined in the definition file.
You can also display a list of all fields and keys that are defined for a
table. A key defines the order in which the fields of a table are sorted.
PEB5DI02 ------------------------------------------------------ Row 1
of 71
Command ===> ________________________________________________ Scroll ===> PAGE
Display Database Tables
F - Display field definitions
Sel
Columns
Line commands
K - Display key definitions
Table
Long Name
ABR
ARCHIVE_BLOCK_RECORD
ADR
ARCHIVE_DATASET_RECORD
AGENT
AGENT_DEFINITION_RECORD
AGENTGRP AGENT_GROUP_DEFINITION
AGMEMBER AGENT_GROUP_MEMBER_DEFINITION
APR
ARCHIVE_POOL_RECORD
ARSTATUS AGENT_RULE_STATUS_DEFINITION
AVR
ARCHIVE_VOLUME_RECORD
BSAUBP
BSA_UBP_BASE
B92STATS B92STATS
CGR
CLASS_GROUP_RECORD
DATACOL DATA_COLUMN
DETLLAY DETAIL_LAYOUT
DLAYFLD DETAIL_LAYOUT_FIELD
DRC
V1_ARCHIVE_DATASET_RECORD
EVTACT
EVENT_ACTION_RECORD
Length Comment
00053 ARCHIVE BLOCK RECORD
00144 ARCHIVE DATASET RECORD
05176 AGENT DEFINITION RECORD
00296 AGENT GROUP DEFINITION
00048 AGENT GROUP MEMBER DEFINITI
00415 ARCHIVE POOL RECORD
00301 AGENT RULE STATUS DEFINITIO
00184 ARCHIVE VOLUME RECORD
00085 UBP TABLE
00088 AGENT STATISTICS
00031 CLASS GROUP RECORD
00161 DATA COLUMN
00152 DETAIL LAYOUT
00050 DETAIL LAYOUT FIELD
00059 V1 ARCHIVE DATASET RECORD
00450 EVENT ACTION RECORD
Column
Description
Table
A short description of the table is displayed.
Long name
Indicates the name of the table.
Length
The length of the table in byte.
Comment
A comment to describe the function of the table.
F
Displays all fields assigned to a table.
K
Displays all keys assigned to a table.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
363
Database (Option A.D)
Dictionary (Option A.D.2)
Which fields are
assigned to a table?
•
Enter line command F in front of a table definition.
The "Display Fields for Table .." panel is displayed, showing all the
fields assigned to a table:
PEB5DI21 ------------------------------------------------------ Row 1
of 12
Command ===> ________________________________________________ Scroll ===> PAGE
Display Fields for Table ABR (File: ARCDATA)
S - Display field definition
Sel
Field
Long Name
C Pos
Internal External
ARCVERS ARC_VERSION
N 00000 00002 S 00003 C
ARCPROD ARC_PRODUCT
N 00002 00003 C 00003 C
ABRBLKNL ABR_ABRBLKNL
N 00005 00004 I 00010 C
ABRSTMP0 ABR_STMP0
N 00009 00008 H 00016 C
ABREXPD0 ABR_ABREXPD1_PRIMARY
N 00017 00004 D 00010 C
ABRBLKP0 ABR_ABRBLKP0
N 00021 00004 I 00010 C
ABRDISP0 ABR_ABRDISP0
N 00025 00002 S 00005 C
ABRSTMP1 ABR_STMP1
N 00027 00008 H 00016 C
ABREXPD1 ABR_ABREXPD1_SECODARY
N 00035 00004 D 00010 C
ABRBLKP1 ABR_ABRBLKP1
N 00039 00004 I 00010 C
ABRDISP1 ABR_ABRDISP1
N 00043 00002 S 00005 C
ABRRES
N 00045 00008 C 00008 C
******************************* BOTTOM OF DATA ********************************
Columns
Column
Description
Field
Indicates the short name of the field
Long Name
Indicates the name of the field
C
N
Non-conversion field
Y
Field is converted, which means that a text is
assigned to the field's value. The assigned text will
be used for external display. Only flag and byte
fields have to be converted.
Pos
Indicates the field's position in the table
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
364
Database (Option A.D)
Dictionary (Option A.D.2)
Column
Description
Internal
Indicates the field type and the internal field length
The following field types may appear in this column:
C
Character
V
Variable character (max. 1000 bytes)
I
Long integer (4 bytes)
S
Small integer (2 bytes)
B
Byte
F
Flag (1 byte)
H
Hexadecimal representation
P
Spool pointer
D
Date (4 bytes)
T
Time (4 bytes)
G Complex data type (token)
A field with the type G (token) may consist of two
different fields, for example, a date field (D) and a
time field (T).
External
Indicates the field type and the external field length
While for internal data representation field types with
non-displayable characters such as the date field can be
used, external display requires the use of character
fields (C).
Line commands
S
Token field (G)
Note that a token field (G) represents a logical name that summarizes a
set of different fields. Therefore a token field cannot be selected with the
line command S.
Note on panel "Display
Fields for Table …"
In the panel "Display Fields for Table..." the fields that are summarized in a
token are listed below the token name. You can calculate of how many
fields a token consists. Add up the internal or external field length until the
length of the token field is reached.
Displays field information
The following example shows a token field defined with the external length
19 that consists of a date field (length 8) and a time field (length 11).
Example
Internal
G 0008
D 0004
T 0004
External
G 0019
C 0008
C 0011
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
365
Database (Option A.D)
Dictionary (Option A.D.2)
Field definition
•
Select a field with the line command S to display the "Definition for
Field .." panel:
PEB5DI24 ------------------------------------------------------ Row 1
of 1
Command ===> ________________________________________________ Scroll ===> PAGE
Definition for Field ARCVERS
Field
ARCVERS
Long Name
C Internal External
ARC_VERSION
N 00002 S 00003 C
Comment : ARCHIVE VERSION
------------------------------------------------------------------------------******************************* BOTTOM OF DATA ********************************
Columns
Column
Description
Comment
A short description of the field is displayed.
The other columns are described above.
Which keys are assigned
to a table?
1. Enter line command K to display a list of all keys assigned to a table:
PEB5DI22 ------------------------------------------------------ Row 1
of 5
Command ===> ________________________________________________ Scroll ===> PAGE
Display Keys for Table JBR
( LEFT/RIGHT )
S - Display key definition
Sel
Key
Long Name
Length Table
Type
JBRKEY00 JBRKEY00
00024 JBR
UN
JBRKEY01 JBRKEY01
00016 JBR
GE
JBRKEY02 JBRKEY02
00016 JBR
GE
JBRKEY04 JBRKEY04
00016 JBR
GE
JBRKEY05 JBRKEY05
00016 JBR
GE
******************************* BOTTOM OF DATA ********************************
2. Press PF11 to display the key comments and PF10 to hide them.
Columns
The following information is shown in the table: the key's short and long
name, the length of the key, and the table the key is assigned to.
The column "Type" has two status: Un indicates that the key is unique, Ge
indicates that the key is used in a table more than once.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
366
Database (Option A.D)
Dictionary (Option A.D.2)
Line command
S
Key definition
•
Displays all fields assigned to a key
Select a key definition with the line command S to display the
"Definition for Key ..." panel:
PEB5DI23 ------------------------------------------------------ Row 1
of 5
Command ===> ________________________________________________ Scroll ===> PAGE
Definition for Key JBRKEY00
S - Display field definition
Sel
Field
Long Name
C Pos
Internal External
B92SUBTK B92_SUB_TOKEN
N 00000 00008 G 00021 G
SRCSUBD SOURCE_SUBMIT_DATE
N 00000 00004 D 00010 C
SRCSUBT SOURCE_SUBMIT_TIME
N 00004 00004 T 00011 C
SRCJOBN SOURCE_JOBNAME
N 00016 00008 C 00008 C
SRCJOBI SOURCE_JOB_JESID
N 00008 00008 C 00008 C
******************************* BOTTOM OF DATA ********************************
See above for an explanation of the table columns.
If you select a field definition with the line command S the panel
"Definition for Field ..." is displayed.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
367
Database (Option A.D)
Dictionary (Option A.D.2)
Displaying keys (Option A.D.2.2)
Which keys are defined?
•
Call up option 2 in the "Dictionary Selection Menu".
The "Display Database Keys" panel shows you all the keys defined in
the database.
PEB5DI03 ------------------------------------------------------ Row 1
of 103
Command ===> ________________________________________________ Scroll ===> PAGE
Display Database Keys
F - Display field definitions
Sel
Columns
( LEFT/RIGHT )
T - Display table definitions
Key
Long Name
ABRI00
ABR_ABRI01
ADRI00
ADR_ADRI00
ADRI01
ADR_ADRI01
ADRI02
ADR_ADRI02
AGEKEY00 AGEKEY00
AGEKEY01 AGEKEY01
AGMKEY00 AGMKEY00
AGMKEY01 AGMKEY01
AGRPKEY0 AGRPKEY00
APRI00
APR_APRI00
ARSTKEY0 ARSTKEY00
ARSTKEY1 ARSTKEY01
ARSTKEY2 ARSTKEY02
AVRI00
AVR_AVRI00
BSAUBPI1 BSA_UBPI01
BSAUBPI2 BSA_UBPI02
Length Table
Type
00012 ABR
UN
00008 ADR
UN
00004 ADR
GE
00016 ADR
UN
00008 AGENT
UN
00252 AGENT
UN
00032 AGMEMBER UN
00032 AGMEMBER UN
00024 AGENTGRP UN
00008 APR
UN
00025 ARSTATUS UN
00025 ARSTATUS UN
00021 ARSTATUS GE
00015 AVR
UN
00014 BSAUBP
UN
00014 BSAUBP
UN
The column "Table" indicates the name of the table a key is assigned to.
For an explanation of the other table columns and available line
commands, see "Displaying tables (Option A.D.2.1)" on page 363.
Line commands
Which fields are
assigned to a key?
F
Displays all fields assigned to a key.
T
Displays all fields assigned to a table.
•
Enter line command F in the panel "Display Database Keys'" to display
the "Display Fields for Key" panel showing you the fields that are
assigned to a key.
PEB5DI21 ------------------------------------------------------ Row 1
of 5
Command ===> ________________________________________________ Scroll ===> PAGE
Display Fields for Key JBRKEY00
S - Display field definition
Sel
Field
Long Name
C Pos
Internal External
B92SUBTK B92_SUB_TOKEN
N 00000 00008 G 00021 G
SRCSUBD SOURCE_SUBMIT_DATE
N 00000 00004 D 00010 C
SRCSUBT SOURCE_SUBMIT_TIME
N 00004 00004 T 00011 C
SRCJOBN SOURCE_JOBNAME
N 00016 00008 C 00008 C
SRCJOBI SOURCE_JOB_JESID
N 00008 00008 C 00008 C
******************************* BOTTOM OF DATA ********************************
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
368
Database (Option A.D)
Dictionary (Option A.D.2)
For an explanation of the other table columns and available line
commands, see "Displaying tables (Option A.D.2.1)" on page 363.
Which fields are
assigned to a table?
•
Enter T in the panel "Display Database Keys" to display the following
table.
The "Display Fields for Table .." table shows you the fields assigned to
a table.
PEB5DI21 ------------------------------------------------------ Row 1
of 37
Command ===> ________________________________________________ Scroll ===> PAGE
Display Fields for Table JBR
S - Display field definition
Sel
Field
Long Name
B92SUBTK B92_SUB_TOKEN
SRCSUBD SOURCE_SUBMIT_DATE
SRCSUBT SOURCE_SUBMIT_TIME
SRCJOBI SOURCE_JOB_JESID
SRCJOBN SOURCE_JOBNAME
B92STRTK B92_STR_TOKEN
SRCSTRTD SRCSTRTD
SRCSTRTT SRCSTRTT
B92ENDTK B92_END_TOKEN
SRCENDD SRCENDD
SRCENDT SRCENDT
B92RINTK B92_JBR_RIN_TOKEN
JBRRINDT B92_JBR_RINDATE
JBRRINTM B92_JBR_RINTIME
B92RLDTK B92_JBR_RLD_TOKEN
JBRRLDDT B92_JBR_RLDDATE
C Pos
Internal External
N 00000 00008 G 00021 G
N 00000 00004 D 00010 C
N 00004 00004 T 00011 C
N 00008 00008 C 00008 C
N 00016 00008 C 00008 C
N 00024 00008 G 00018 G
N 00024 00004 D 00010 C
N 00028 00004 T 00008 C
N 00032 00008 G 00018 G
N 00032 00004 D 00010 C
N 00036 00004 T 00008 C
N 00040 00008 G 00018 G
N 00040 00004 D 00010 C
N 00044 00004 T 00008 C
N 00048 00008 G 00018 G
N 00048 00004 D 00010 C
For an explanation of the other table columns and available line
commands, see "Displaying tables (Option A.D.2.1)" on page 363.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
369
Database (Option A.D)
Dictionary (Option A.D.2)
Displaying fields (Option A.D.2.3)
Which fields are defined?
•
Call up option 3 in the "Dictionary Selection Menu" to display the panel
"Display Database Fields".
The "Display Database Fields" table shows all the fields defined in the
database:
PEB5DI04 -------------------------------------------------- Row 1
of 749
Command ===> ________________________________________________ Scroll ===> PAGE
Display Database Fields
F - Display field definition
Sel
Field
Long Name
AALCOMM B92_AAL_COMMENT
AALFLD1 B92_AAL_FIELD1
AALFLD2 B92_AAL_FIELD2
AALFLD3 B92_AAL_FIELD3
AALFLD4 B92_AAL_FIELD4
AALNEW
B92_AAL_NEW_RECORD
AALOLD
B92_AAL_OLD_RECORD
AALTEXT B92_AAL_TEXT
AALTYPE B92_AAL_TYPE
ABRBLKNL ABR_ABRBLKNL
ABRBLKP0 ABR_ABRBLKP0
ABRBLKP1 ABR_ABRBLKP1
ABRDISP0 ABR_ABRDISP0
ABRDISP1 ABR_ABRDISP1
ABREXPD0 ABR_ABREXPD1_PRIMARY
ABREXPD1 ABR_ABREXPD1_SECODARY
T - Display table definitions
C Internal External
N 00080 C 00080 C
N 00008 C 00008 C
N 00008 C 00008 C
N 00010 C 00010 C
N 00008 C 00008 C
N 15000 V 15000 V
N 15000 V 15000 V
N 00032 C 00032 C
Y 00001 B 00003 C
N 00004 I 00010 C
N 00004 I 00010 C
N 00004 I 00010 C
N 00002 S 00005 C
N 00002 S 00005 C
N 00004 D 00010 C
N 00004 D 00010 C
For an explanation of the other table columns and available line
commands, see "Displaying keys (Option A.D.2.2)" on page 368.
Displaying field
definitions
•
To display information on the field definition, enter F in front of a field
and press ENTER.
PEB5DI24 ------------------------------------------------------ Row 1
of 20
Command ===> ________________________________________________ Scroll ===> PAGE
Definition for Field APRMED1
Field
APRMED1
Long Name
C Internal External
APR_MEDIA1
Y 00001 B 00005 C
Comment : ARCHIVE MEDIA
Name
:
Long name
:
Value
: D
Text
: DISK
Language : E
Alternate text:
------------------------------------------------------------------------------APRMED1 APR_MEDIA1
Y 00001 B 00005 C
Comment : ARCHIVE MEDIA
Name
:
Long name
:
Value
: O
Text
: ODISK
Language : E
Alternate text:
------------------------------------------------------------------------------APRMED1 APR_MEDIA1
Y 00001 B 00005 C
Comment : ARCHIVE MEDIA
Name
:
Long name
:
Value
: T
Text
: TAPE
Language : E
Alternate text:
-------------------------------------------------------------------------------
The short field name, a comment, the long field name, the value, the
language, the conversion field type, the internal and external data
format, a text, and an alternate text are displayed.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
370
Database (Option A.D)
Dictionary (Option A.D.2)
Displaying system databases (Option A.D.2.4)
Select option 4 of the "Dictionary Selection Menu" to display a list of all
system databases.
Procedure
PEB5DI01 ------------------------------------------------------ Row 1
of 55
Command ===> ________________________________________________ Scroll ===> PAGE
Display System Databases
Dataset Name
BETA92.DB.ARCH.DATA
BETA92.DB.ARCH.KEY
BETA92.DB.ARCHINF.DATA
BETA92.DB.ARCHINF.KEY
BETA92.DB.CLNT.DATA
BETA92.DB.CLNT.KEY
BETA92.DB.DEF
BETA92.DB.EVT.DATA
BETA92.DB.EVT.KEY
BETA92.DB.EXTDATA
BETA92.DB.GARD01
BETA92.DB.GARD02
BETA92.DB.JOB.DATA
BETA92.DB.JOB.KEY
BETA92.DB.LOG.DATA
BETA92.DB.MAIN.DATA
BETA92.DB.MAIN.KEY
BETA92.DB.SPOOL01.DATA
Columns
( LEFT/RIGHT )
X Sta FileID Buffer
% Type HWM
OPN 00032 00000100 012 DA
90
OPN 00033 00000100 001 KE
90
OPN 00034 00000100 012 DA
90
OPN 00035 00000100 002 KE
90
OPN 00046 00000100 029 DA
90
OPN 00047 00000100 060 KE
90
OPN 00001 00000000 017 NO
-OPN 00049 00001000 050 DA
90
OPN 00050 00001000 003 KE
90
OPN 00038 00001000 001 DA
90
OPN 00044 00000100 003 DA
90
OPN 00045 00000100 015 DA
90
OPN 00036 00002000 010 DA
90
OPN 00037 00001000 003 KE
90
OPN 00042 00000000 031 LO
-OPN 00030 00000050 028 DA
90
OPN 00031 00000050 005 KE
90
OPN 00043 00000000 065 SP
--
Column
Description
Dataset Name
Name of the system database
X
Y in this column indicates the presence of database
extensions based on concatenated datasets (EXT01,
EXT02 etc.). The current BSA version provides only
limited support for this type. While it is possible to
continue to work with the existing database, the current
BSA version does not support any further extension.
Important: It is no longer meaningful to work with
concatenated VSAM datasets because BSA (as of V4)
supports the so-called "extended VSAM datasets",
which enable a total maximum size of 28 GB for BQL
databases. If you are still working with concatenated
datasets, include the task of merging these datasets
when planning your database maintenance.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
371
Database (Option A.D)
Fields
Dictionary (Option A.D.2)
Column
Description
Sta
The status column can contain one of the following
entries:
USE (in use): The dataset is in use.
CLS (closed): The dataset could not be opened.
MOD (model): Not available for VDF.
ONL (read only): The dataset can only be read.
FMT (format): Not available for VDF.
EMP (empty): The dataset is empty.
ERR (error): An error occurred.
FEX Format extend error
FUL (full): The dataset is full.
OPN (open): The dataset is active. The dataset can be
used by the started task.
FileID
The file identification number (file ID) that is
automatically assigned by the system.
Buffer
The 8-digit number of buffers which can be used for the
cache.
%
The number of 4k blocks in use displayed as
percentage points.
Type
Indicates the type of database:
DA (DATA): Data file
KE (KEY): Key file
SY (SYNC): Synchronization file
LO (LOG): Log file
NO (DEF): Definition file
SP (SPOOL): Spool file
HWM
Displays the high water mark value of the database (in
percent)
Field
Description
VolSer
Shows the volume currently used
When SMS is displayed here, the assignment of a
volume or a unit has been left to the SMS.
Unit
Shows the unit type where the dataset is stored
Space
Displays the space used by the dataset in cylinders
CIsize
Indicates the size of the control interval (CI)
Short Name
Shows the short name of the dataset
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
372
Database (Option A.D)
Database usage statistics (Option A.D.3)
Database usage statistics (Option A.D.3)
Overview
Option D.3 in the "Primary Selection Menu" or in the "Administration
Selection Menu" of your Beta product and in the "Service Manager
Selection Menu" calls the "Database Statistics Menu".
The option allows you to display statistical information on the usage of the
respective database, or to create a report. The information is productdependent.
Usage based pricing
Please note that every job and every list read into _beta log|z is counted
separately for UBP (usage based pricing). In particular, this applies to all of
the output read into _beta log|z by the EJM agents.
Navigation
•
Enter D.3 in the "Service Manager Selection Menu" to display the
following panel:
B5UBPP ---------------------------------------------------------------------Option ===> __________________________________________________________________
Database Statistics Menu
System
- B92PROD
Location - BERLIN
Subsys-ID - B92P
User ID
- AVSCHM1
1
BROWSE
-
Display Statistics Database Values
2
BATCH
-
Generate Statistics Database Batch Report
3
CLEANUP
-
Batch Job for Statistics Database Cleanup
Select one of the above options. Press END to exit.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
373
Database (Option A.D)
Database usage statistics (Option A.D.3)
Statistic values (Option A.D.3.1)
Overview
The "Display Statistic Values" panel is the starting point for displaying
database statistics.
Procedure
1. Select option 1 in the "Database Statistics Menu" to call up the
following panel:
PEB5UBP1 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Display Statistic Values
Start Date (MM/DD/YYYY)
End
Date (MM/DD/YYYY)
===> 01/01/2010
===> TODAY_____
Selection
===> M
per (H)our, (D)ay, (M)onth
Subdivision by
SSID, Sysclone, Sysplex
===> N
(Y)es, (N)o
Optional Selection Criteria:
Subsystem ID
Sysclone Name
Sysplex Name
===> ____
===> __
===> ________
Press ENTER to display the Database Statistics Table.
Press END to return to the previous menu.
2. Enter the time selection criteria to limit the date range of the records
that are to appear in the statistics (Start Date/End Date).
For more information on the entry in each of the following fields, see
"Fields in the statistics panels" on page 378.
3. Specify whether you want statistics to be displayed on an hourly, daily
or monthly basis (Selection).
Note: When specifying the time range, please remember the longer
the time range, the longer the selection process takes.
4. Specify whether the statistics are to be subdivided (Subdivision by).
5. Specify the Optional Selection Criteria to further limit the amount of
data received. If you do not change the default *, all the possible
entries for the criterion concerned will be selected (Subsystem ID,
Sysclone Name, Sysplex Name).
6. Press ENTER to display the "Statistics Table".
This table contains all records matching the criteria entered in the
corresponding fields.
Results
The results you obtain depend on the selection criteria you have used.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
374
Database (Option A.D)
Database usage statistics (Option A.D.3)
Displaying daily or hourly statistics
Overview
The statistics tables can display monthly, daily or hourly statistics. The
monthly and daily statistics tables respectively can be used to obtain
detailed daily information on database usage for a particular month, or
detailed hourly information for a particular day.
The information displayed by line command S depends on the table it was
entered in.
Using S to display daily
statistics
If you selected the option (M)onth in the Selection field, the database
usage statistics are displayed on a monthly basis.
•
Using S to display hourly
statistics
Note
To display the daily statistics for a particular month, enter line
command S in front of the relevant entry.
If you selected the option (D)ay in the Selection field, the database usage
statistics are displayed on a daily basis.
•
To display the hourly statistics for a particular day, enter line command
S in front of the relevant entry.
•
Because minutes are not relevant, line command S is not available for
the hourly statistics table.
•
The Hour column displays the period in full hours.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
375
Database (Option A.D)
Database usage statistics (Option A.D.3)
Statistic batch reports (Option A.D.3.2)
Overview
The "Statistic Batch Report" panel is the starting point for generating
statistical database reports using _beta report.
Procedure
1. Select option 2 in the "Database Statistics Menu" to call up the
following panel:
PEB5UBP2 --------------------------------------------------------------------Command ===> _________________________________________________________________
Statistics Batch Report
Start Date (MM/DD/YYYY)
End
Date (MM/DD/YYYY)
===> YESTERDAY.
===> TODAY_____
Selection
===> H
per (H)our, (D)ay, (M)onth
RPGPRINT/WORKFILE Options
===> Y
(Y)es,(N)o
Optional Selection Criteria:
Subsystem ID
Sysclone Name
Sysplex Name
===> ____
===> __
===> ________
Press ENTER to generate the respective batch job.
Press END to return to the previous menu.
2. Fill in the fields as required, and press ENTER.
For more information on the entry in each of the fields, see "Fields in
the statistics panels" on page 378 and "Fields for the RPGPRINT,
RPGWORK, RPTRUN and RPTLIST options" on page 381.
3. (a) If you set the field RPGPRINT/WORKFILE Options to Yes, the
following panel is displayed:
PEB5UBOP ---------------------------------------------------------------------Command ===> _________________________________________________________________
RPGPRINT
Options:
Class
===> _
Forms Number ===> ____
Destination ===> ________
RPGWORK
Writer Name ===> ________
User ID
===> ________
Options:
Type
Prim. Space
Sec. Space
===> ___
===> __
===> __
(T)RK,(C)YL
Job Card:
===> //REJUBP JOB 1,ACCOUNT,CLASS=A,MSGCLASS=P,NOTIFY=&SYSUID_______________
===> //*_____________________________________________________________________
===> //*_____________________________________________________________________
===> //*_____________________________________________________________________
Press ENTER to continue with the job generation. Press UP to display the
previous page. Press END to return to the previous menu.
3.
(b) If you set the field RPGPRINT/WORKFILE Options to No, press
ENTER.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
376
Database (Option A.D)
Result
Database usage statistics (Option A.D.3)
The job is generated and the JCL is displayed. Accept or modify the
entries before submitting the job.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
377
Database (Option A.D)
Database usage statistics (Option A.D.3)
Fields in the statistics panels
Overview
The table lists the fields in the statistics panels in alphabetical order.
Field
Description
Remarks
Report Type
Enables you to
generate different
types of reports.
(S)tatus report
Enter S to generate a status report with the usage values of
the accounting period. The actual usage report for Beta
Systems is generated. Note: The STATUS report can only
be generated once during the agreed report period. Because
of this, the report period is checked. A report will only be
permitted if the last report date plus the days in the agreed
report period is less than or equal to the current date. If it is
greater, it means that the new report date has not yet been
reached. In this case the runtime message 8627E (file
RPTRUN) will inform you of the earliest possible report date.
The detail report contains the numerical values from the
database for the report period. The current values for
resource usage are saved as old values before being
overwritten.
(T)est report
Enter T to generate a test report with the current usage
values. The test report is for auditing purposes, and mainly
concerns itself with the records containing the numerical
database values as shown in the detail report. The detail
report contains the records created during the interval
defined by the start and end values. If no end value is
specified, the interval starts with the start value and ends on
the current date. The date values must comply with the
structure of the date mask.
Valid date masks: DD.MM.YY, DD.MM.YYYY, DD/MM/YY,
DD/MM/YYYY, MM/DD/YY, MM/DD/YYYY, YY.DDD,
YYYY.DDD and MMDDYYYY
The table with the summary report is not created.
(L)ast report
Enter L to generate a report with the usage values of the
previous accounting period. The last report is for auditing
purposes. Here, unlike the STATUS report, the summary
report does not contain the latest usage values, but shows
the values for the previous report period (old values). The
old values are the ones that were saved when the current
usage values were deleted by the last STATUS report.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
378
Database (Option A.D)
Database usage statistics (Option A.D.3)
Field
Description
Remarks
RPGPRINT/
WORKFILE
Options
Enables you to
specify the
parameters
required for the
RPGPRINT and
RPGWORK files.
(Y)es - You will receive a second panel enabling you to specify
the parameters required for the RPGPRINT and RPGWORK
files.
Selection
Use this parameter
to specify the time
period that is to be
used as the basis
for the statistics.
You can choose
between (H)our,
(D)ay, (M)onth.
(N)o - The default values for RPGPRINT and RPGWORK will be
accepted. They are normally sufficient.
For the fields available when this option is set to YES, see the
separate table in "Fields for the RPGPRINT, RPGWORK,
RPTRUN and RPTLIST options" on page 381.
Depending to the date range you have chosen (Start/End Date),
the number of activities counted so far, i.e. jobs, pages, profiles,
etc., will be displayed on a monthly, daily or hourly basis.
H - hourly; the smallest unit for displaying the selected time
range.
Example:
Date
08/18/03
08/18/03
Hour
12-13
14-15
JOBS
205
102
LISTS
817
408
All the activities counted were executed on the 18th of August,
205 between 12:00 - 13:00 and 102 between 14:00 - 15:00.
D - daily; the activities counted for the selected time range are
displayed accumulated per day.
Example:
Date
08/18/03
JOBS
307
LISTS
1225
All the activities occurred on the 18th of August.
M - monthly; the activities counted for the selected time range
are displayed accumulated per month.
Example:
Date
08/03
JOBS
307
LISTS
1225
All the activities counted in August are displayed.
Start/End Date
Use these
parameters to
specify the date
range that is to be
used as the basis
for the statistics.
Choose between the following date formats:
•
American: MM/DD/YY or MM/DD/YYYY
•
Continental: DD.MM.YY or DD.MM.YYYY
•
British: DD/MM/YY or DD/MM/YYYY
•
Julian: YY.DDD or YYYY.DDD
•
International: YYYY-MM-DD
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
379
Database (Option A.D)
Database usage statistics (Option A.D.3)
Field
Description
Remarks
Subdivision by
Use this parameter (Y)es - The output table will show which SSID, Sysclone and
to specify whether Sysplex systems were used for each month, day or hour.
the statistics are
(N)o - The output table will not list the various systems.
displayed
separately for each
system, or as a
summary of all
systems.
Subsystem ID
Use this parameter You can use a generic value (e.g. B93*) or a blank.
to specify the
subsystem to be
used as a basis for
the statistics.
Sysclone Name Use this parameter You can use a generic value (e.g. T*) or a blank.
to specify the
Sysclone name of
the system on
which the
subsystem ID used
as a basis for the
statistics was
active.
Sysplex Name
Use this parameter You can use a generic value (e.g. INSTPL*) or a blank.
to specify the
sysplex of the
system on which
the subsystem ID
used as a basis for
the statistics was
active.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
380
Database (Option A.D)
Database usage statistics (Option A.D.3)
Fields for the RPGPRINT, RPGWORK, RPTRUN and RPTLIST options
Overview
The table lists in alphabetical order the fields that are available when you
set the field RPGPRINT/WORKFILE Options to Yes. Doing so enables
you to specify the parameters required for the RPGPRINT and RPGWORK
files.
For more information, refer to the _beta report Manual.
Field
Description
Remarks
Class
Specifies an output class for
printing the report.
Valid classes are A* - Z* and 0 - 9.
Default = *
Destination
Assigns the destination of the
SYSOUT dataset.
Optional.
Forms Number
Identifies the forms on which the
SYSOUT dataset is to be printed.
Optional.
Job Card
Specifies a job card for the current
print job.
If you have already defined a job card, it
is displayed here and can be modified as
required.
Prim. Space
Size in Type of the primary space
required for the RPGWORK
dataset.
Default = 15
Sec. Space
Indicates the unit for additional
DASD space, if required, this unit
Default = 5
Type
Indicates the unit for the space
required for the RPGWORK
dataset.
TRK = tracks
Optional.
CYL = cylinders
Default = CYL
User ID
Identifies a node (destination) and a Optional.
TSO user ID at that node.
Writer Name
Identifies the member name of the
external writer name.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
Default = RPGPRINT
Optional.
381
Database (Option A.D)
Database usage statistics (Option A.D.3)
Deleting obsolete statistics data (Option D.3.3)
Overview
The CLEANUP option in the "Database Statistics Menu" enables you to
generate a batch job that deletes obsolete usage data from the statistics
database.
Time range
The time range of the data that will be deleted is controlled by the program
and cannot be changed by the user.
All data that is older than three years will be deleted. The deletion date is
always based on January 1 of the current year. For example, a job that is
generated on any date of the year 2013 deletes statistical data of the years
2009, 2008, etc.
Procedure
To delete obsolete statistical data:
1. Select option 3 Cleanup from the "Database Statistics Menu".
2. If necessary, edit the job card in the displayed panel and press
ENTER.
The JCL for the cleanup job is generated from the corresponding
skeleton and displayed in the editor.
3. Enter SUB to submit this job.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
382
Database (Option A.D)
Database queries (Option A.D.Q)
Database queries (Option A.D.Q)
Overview
You can query the database via the "Generic Command Interface" panel.
There are two ways of making the database query:
•
You can enter the required data in the fields in the upper half of the
panel (Command, Table, Condition, Fields, Values).
-OR•
You can enter the database query in BQL format in the multi-line field
in the lower half of the panel. The Command field in the upper half of
the panel must be left blank in this case.
Warning
Only use the SELECT command in this panel. Incorrect use of other BQL
commands such as UPDATE or DELETE can do irreparable damage to
the database and make it unusable.
Information return codes
When querying _beta log|z databases, some product-specific information
return codes may come up. For a list of these codes, see "Product-specific
information return codes" in _beta log|z Messages and Codes.
Procedure
1. Enter option A.D.Q in the "Primary Selection Menu" to display the
"Generic Command Interface" panel:
PEB5DQ00 ---------------------------------------------------------------------Command ===> _________________________________________________________________
Generic Command Interface
Router
Command
Table
Condition
Fields
Values
: BQRT
Ssid : B92P
Router name
(*) Input case sensitive
===> NO_ (Y)es,(N)o
===> ______
(S)elect
===> ________
Table name
===> __________________________________________________
===> __________________________________________________
===> __________________________________________________
(*)
(*)
Command (leave above command field blank):
Resources Limit ===> NO_ (Y/N)
===> ________________________________________________________________ (*)
===> ________________________________________________________________ (*)
===> ________________________________________________________________ (*)
===> ________________________________________________________________ (*)
===> ________________________________________________________________ (*)
Press the ENTER key to issue the request.
Press the END key to return to the previous menu.
2. Enter your database query.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
383
Database (Option A.D)
Fields
Database queries (Option A.D.Q)
Field
Description
Database Query:
Command
Enter the BQL command SELECT or simply an S.
Table
Specify the name of the database table. You can obtain a
complete list of all existing tables by entering enter 1 in
the "Dictionary Selection Menu".
Condition
Logical operators can be used to specify selection
criteria.
Fields
Enter all database fields that are to be selected. You can
obtain a complete list of all existing fields by entering 3 in
the "Dictionary Selection Menu". To select all fields, enter
a mask *.
Values
Define the operator value which refers to a field content.
BQL command
Enter a database query in BQL. You will find a complete
explanation of the BQL command SELECT in the _beta
report Manual, see command "BQL_EXEC".
Resources Limit
(YES/NO)
Set this parameter to Yes if you want to limit the storage
space. You can specify values in an additional panel.
The default is NO under TSO/ISPF and YES under VDF
(VAF/CAF/IAF).
Fields of "Database Query Resources" panel
Field
Description
Space
Enter the space allocation in cylinders of the temporary
dataset used for data storage. If you specify Space=0,
then no temporary dataset is created.
Note: The default values are for 50 cylinders of space for
the temporary dataset and 2 MB memory for the central
storage (under VDF). The system administrator can
change these defaults with the help of the LST
parameters BQL_QRY_MAXMEMORY and
BQL_QRY_FILESPACE. For a description of these
parameters, see "Global LST parameters for BQL" in
BSA Installation and System Guide.
Memory
This field displays the size of the memory in megabytes.
If only one address space is available for all users, the
entry in this field cannot be changed.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
384
Database (Option A.D)
Generating JCL for database utilities (Option A.D.4)
Generating JCL for database utilities (Option A.D.4)
Overview
Option A.D.4 can be used to generate JCL for the maintenance of the
_beta log|z database (ENLARGE, REDUCE, ALTER, etc.).
The option uses skeletons from the BSA.ISPSLIB and generates the JCL
according to your input in the displayed panels. You can display, send or
save the generated JCL in a member.
Caution
Database utilities should be used only by experienced users with a
profound knowledge of the product databases.
Caution: Improper handling may result in an irrevocable loss of data.
STC active/inactive
The _beta log|z started task must be ACTIVE when you generate the JCL
of the maintenance job, but INACTIVE when you submit the JCL.
Stop all _beta log|z started tasks (including slave STCs) and batch jobs
that access the _beta log|z database before submitting the JCL of a
maintenance job.
Exception: The STC must be active when jobs are tailored with
SIGNON=YES, for example, UNLOAD jobs.
Notes on file tailoring
•
The generated JCL uses the libraries that are currently allocated by
the _beta log|z started task.
Option A.D.4 does not use the library names specified in the system
options.
•
If mirror databases exist, they are automatically taken into
consideration when the JCL is generated.
•
Multi-selection via primary command requires that the HLQ of the
selected files is identical.
The error message No prefix found is output if different HLQs are
detected in the selection.
•
Option A.D.4 works with its own jobcard variables in the user profile. If
the SE92JOBC skeleton exists in the BETA92.ISPSLIB, the jobcard is
taken from this member instead and the panel that displays the
jobcard is skipped.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
385
Database (Option A.D)
Instructions
Generating JCL for database utilities (Option A.D.4)
To generate JCL for a database utility:
1. Select option A.D.4.
The _beta log|z databases are displayed in a table.
Spool files are excluded from the display, but can be selected via the
primary commands. Mirror databases are also never displayed
because they are automatically processed together with the
corresponding data/key files.
2. Do one of the following:
•
Enter the line command S in front of a database entry.
•
Enter one of the these primary commands for multi-selection by
type:
ALL to select all databases
DB to select all file types except spool
SP to select all spool file types (depending on the product:
Spool (SP), Reload (SR), Index (IX), Cache (CA), and
Global (GL))
A panel is displayed which shows the maintenance tasks available for
your selection.
3. Select the maintenance task for which you would like to generate the
JCL and follow the instructions in the displayed panels.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
386
Database (Option A.D)
Maintenance tasks
Generating JCL for database utilities (Option A.D.4)
The maintenance tasks offered depend on your selection.
If you have selected multiple entries via the primary command ALL, DB, or
SP, the following options are available:
1
ALTER
2
MOVE (alter with copy)
If you have selected a single entry via the line command S, the options
available depend on the database type:
•
•
•
•
•
Type Data (DA)
1
ENLARGE
2
REDUCE
3
ALTER
4
MOVE (alter with copy)
5
UPD-HWM (change the High Water Mark)
6
UNLOAD
7
LOAD
8
REBUILD (recreating the key file)
Type Key (KE)
1
ENLARGE
2
ALTER
3
MOVE (alter with copy)
4
UPD-HWM (change the High Water Mark)
Type Sync (SY)
1
ALTER
2
RE-ALLOC (re-allocate)
3
CLEARSYN
Type Log (LO)
1
ALTER
2
RE-ALLOC (re-allocate)
Definition file (NO)
None (The DEFI file is included by the primary commands ALL and
DB.)
Further information
For more information on individual database utilities, see "Databases and
database batch utilities" in BSA Installation and System Guide.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
387
Database (Option A.D)
BSA Service Manager (Option A.D.S)
BSA Service Manager (Option A.D.S)
Overview
The BSA Service Manager provides the following functions:
•
Changing LST parameters while the started task is running
•
Activating functions like TCP/IP dynamically
•
Displaying detailed system and status information
•
Running diagnostic reports and SMF reports
The panels of the Service Manager are available in English only.
Procedure
To call the Service Manager, choose option S from the Service and
Database Selection menu.
PEB4PRM1 --------------------------------------------------------------------Option ===> __________________________________________________________________
Service Manager Selection Menu
-
Subsys-ID - B92P
Sysname
- B92PROD
1
PARM
Display/Change Started Task Parameters
2
3
4
OPERATION
APPLICATION CONNECTIVITY -
Monitor/Control Started Task
Monitor/Control Started Task Applications
Monitor/Control Started Task Connectivities
5
SUBSYSTEMS
-
Work with Subsystems
R
S
REPORTS
SMF
-
Display Diagnostic Reports Selection Menu (TSO only)
Display Selection Menu of beta smf
(TSO only)
D
DATABASE
-
Display Database Selection Menu
Select one of the above options. Press END to return to the previous menu.
More information
The BSA Service Manager is described in the BSA Service Manager
Manual.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
388
Product batch utilities
In this chapter
Product batch utilities
In this chapter
Topic
Page
Starting product batch utilities ................................................................ 391
General structure of the JCL .................................................................. 392
B92ADR01: Updating volume/label information of archive datasets...... 395
B92AGINF: Getting agent information .................................................... 398
B92ARPRI: List archiving ....................................................................... 400
Parallel archiving ................................................................................ 403
Errors during archiving........................................................................ 405
B92ARSEC: Job record cleanup ............................................................ 406
B92BCAPI: Querying the database via command API........................... 409
B92BFJBR: Job information report ......................................................... 415
B92BFJGI: Job Group Information ......................................................... 419
B92CLAR2: Clear extended generation archive records ....................... 421
B92CLARC: Archive cleanup ................................................................. 424
B92CLARS: Cleanup for agent rule status and statistics ....................... 429
B92CLEVT: Clearing events................................................................... 434
B92CLLST: List cleanup ......................................................................... 437
B92CLREO: List reorganization ............................................................. 441
B92DAILY: Daily job ............................................................................... 442
B92DBVER: Database verification ......................................................... 444
B92FFIND: Find in online/offline logs ..................................................... 446
B92FFIND and automatic reload requests ......................................... 453
B92FFIND for searching syslogs ........................................................ 457
B92MICRO: Microfiche ........................................................................... 461
B92MUPDT: Mass update ...................................................................... 464
Updating jobs with B92MUPDT .......................................................... 467
Updating lists with B92MUPDT .......................................................... 470
B92PRINT: Printing/Mailing lists............................................................. 472
B92RDPS4: Reading z/OS Unix files into _beta log|z............................ 484
B92SENDL: Transferring lists to an EJM agent ..................................... 488
B92SSRCH: Advanced search in online logs......................................... 497
Selection parameters .......................................................................... 500
Search-related parameters ................................................................. 502
Search expressions ............................................................................ 503
B92SSRCH reports............................................................................. 507
Customer-specific report (OMSPUNCH) ............................................ 512
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
389
Product batch utilities
In this chapter
B92WAIT4: Waiting for a job or list......................................................... 515
B92WEEKL: Weekly job ......................................................................... 520
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
390
Product batch utilities
Starting product batch utilities
Starting product batch utilities
Overview
_beta log|z provides batch utilities for numerous tasks, for example:
•
Printing or mailing lists
•
Searching lists
•
Database maintenance (housekeeping)
•
Downloading/Uploading data from/into the database
This chapter contains a description of these batch utilities.
Running batch utilities
Tailored JCL for the batch utilities can be found in the BETA92.CNTL. You
can submit the jobs from the BETA92.CNTL.
Batch utilities can also be started from the ISPF application:
•
Option 3 (Utilities Selection Menu)
Selected batch utilities can be started from the "Utilities Selection
Menu" (Option 3). This option is intended for all types of users of the
ISPF application.
Provide appropriate information in the displayed panel sequence. The
JCL of the batch utility is generated automatically by the ISPF
application when you press ENTER in the last panel. The JCL is
submitted automatically or displayed in the ISPF editor.
For more information, see "Batch utilities (Option 3)" in _beta log|z
User Guide.
•
Option A.3 (Batch Job Generation Selection Menu)
The file tailoring utilities of the "Batch Job Generation Selection Menu"
(Option A.3) can be used to generate the JCL for maintenance batch
jobs in order to administrate and maintain the product databases. This
option is intended for administrators.
For more information, see "File tailoring (Option A.3)" on page 172.
Note
The product STC must be active in order to use the batch utilities
described here.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
391
Product batch utilities
General structure of the JCL
General structure of the JCL
Overview
JCL examples of all product batch utilities can be found in the
BETA92.CNTL.
The JCL in this library is generated according to your specifications during
installation.
You can also tailor JCL for numerous batch utilities online.
JCL
This is the standard JCL that applies to most product batch utilities.
Note: The RFF batch utilities of _beta log|z require a minimum region size
of 64 MB.
+------------------------------------------------------------------------+
|jobcard
|
|//stepname EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92xxxxx,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DISP=SHR,DSN=BETA92.DB.DEF
|
|//*
|
|//SYSPRINT DD SYSOUT=*
|
|//B92LOG
DD SYSOUT=*
|
|//OMSPRINT DD SYSOUT=*
|
|//OMSERROR DD SYSOUT=*
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//*
|
|//SYSIN
DD *
|
|...
|
|/*
|
+------------------------------------------------------------------------+
If SIGNON=YES, it is okay for most _beta log|z batch utilities to use
DUMMY in the DD statement B92DEF of the database definition file:
+------------------------------------------------------------------------+
|...
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DUMMY
|
|...
|
+------------------------------------------------------------------------+
For more information, see "B92DEF DD DUMMY" on page 394.
DD statements and parameters that are used only by individual batch
utilities are described in the section of the corresponding batch utility.
PGM=BST01RFF
PGM=BST01RFF in the EXEC statement indicates that the batch job runs
in an RFF environment (RFF = Remote Function Facility). This is the
standard for all product batch utilities.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
392
Product batch utilities
General structure of the JCL
EXEC PARM
The EXEC PARM specifies the following:
•
Which program is to be executed by BST01RFF
•
Which parameters are to be used for controlling the execution of this
program
Standard parameters are listed below.
Parameter
Description
S=92
Product number (92 is the identifier of _beta log|z)
PGM=name
Name of the program to be executed, for example
B92ARPRI or B92CLLST
B01LST=xx
B92LST=xx
BETA.PARMLIB members whose parameters should be
used
SIGNON=YES|NO
YES
The batch utility accesses the database via the
product STC. The product STC must be active
when the batch utility is started. SIGNON=YES is
the default.
NO
The batch utility requests exclusive access to the
product database. The product STC must be
inactive when the batch utility is started.
For other program-specific parameters that are coded in the EXEC PARM,
see the description of the individual program.
Note on maximum length
The maximum length of the EXEC PARM is 100 characters. You can do
the following if you need to save on length:
•
Leave out SIGNON=YES because this is the default.
•
Leave out S=92 if the program number can be retrieved from the
program name (B92xxxxx).
•
Use the abbreviated form of parameters if available.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
393
Product batch utilities
DD statements
General structure of the JCL
DD statement
Description
STEPLIB
Load libraries (by default BSA.LOAD and BETA92.LOAD)
B92DEF
Database definition file
DD DUMMY is okay for most product batch utilities (see
page 394).
SFFPARM
Parameter library (BETA.PARMLIB)
The members B01LSTxx and B92LSTxx must be located
in this library.
B92DEF DD DUMMY
SYSPRINT
Dataset for system messages (if needed)
B92LOG
Dataset for the processing log
OMSPRINT
Dataset for the results log
OMSERROR
Dataset for the error log (if needed)
SFFFDUMP
Dataset for subsystem dumps (if needed)
SYSUDUMP
Dataset for system dumps (if needed)
SYSIN
Dataset for program-specific control parameters
If SIGNON=YES, it is okay for most _beta log|z batch utilities to code
B92DEF DD DUMMY in the JCL.
Name of database definition file required by...
The following batch utilities do not work with a DD DUMMY statement, but
require the name of the _beta log|z database definition file in the B92DEF
DD statement. The submitting user must have CONTROL access to the
_beta log|z database.
•
B92ARPRI
•
B92CLREO
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
394
Product batch utilities
B92ADR01: Updating volume/label information of archive datasets
B92ADR01: Updating volume/label information of archive datasets
Overview
The batch utility B92ADR01 updates the entries of archive datasets in the
ADR table with the volume and label information from the z/OS system
catalog. You can use B92ADR01 after moving or copying _beta log|z
archive datasets in order to update the information on these datasets in
the _beta log|z database.
Moving/Copying archive
datasets
z/OS catalog
_beta log|z can locate archive datasets based on the information of the
z/OS catalog or based on the information in the ADR table. This behavior
is controlled via the LST parameter B08_RELOAD_CATLG.
If YES (default), _beta log|z uses the z/OS catalog. In this case, updating
the volume/label information in the ADR table is optional. You can run
B92ADR01 after archive datasets have been moved to ensure that the
information displayed by _beta log|z is correct.
If NO, _beta log|z uses the ADR table. In this case, updating the
volume/label information in the ADR table is required. You must run
B92ADR01 after archive datasets have been moved to ensure that these
datasets can be accessed by _beta log|z.
Copy utility
Always use a utility that copies block by block to copy _beta log|z archive
datasets, for example, ICEGENER.
Do not use a utility that copies record by record, for example, IEBGENER.
The use of an IEBGENER-compatible utility leads to reblocking. Archive
pointers will no longer work correctly during reloading when an archive
dataset has been reblocked. It is possible to make _beta log|z read
reblocked datasets sequentially via the LST parameter
B08_RELOAD_SEQ=YES.
JCL
You can find JCL for this batch utility in the BETA92.CNTL in member
B92ADR01.
+-----------------------------------------------------------------------+
|jobcard
|
|//stepname EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92ADR01,SIGNON=YES',
|
|//
'TYPE=xxxx',
|
|//
'SHOW=xxxx',
|
|//
'USE=xxxx',
|
|//
'MEDIA=xxxx',
|
|//
'MIGVOL=xxxx')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DUMMY
|
|//
|
|//B92LOG
DD SYSOUT=*
|
|//OMSPRINT DD SYSOUT=*
|
+-----------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
395
Product batch utilities
EXEC parameters
B92ADR01: Updating volume/label information of archive datasets
Parameter
Description
TYPE
ANALYZE Checks for discrepancies between _beta
log|z database and z/OS catalog, but does
not update the _beta log|z database
UPDATE
Updates the volume and label information of
archive datasets according to the z/OS
catalog
This parameter is required.
SHOW
ALL
Logs all archive datasets in OMSPRINT.
MOVED
Logs archive datasets in OMSPRINT only if
the volume and label information is not
identical in the _beta log|z database and in
the z/OS catalog.
Default: MOVED
USE
ALL
Checks each archive dataset on a volume
FIRST
Checks the first dataset on a volume. If the
volume and label information of the first
dataset is identical in the _beta log|z
database and the z/OS catalog, the
remaining datasets on this volume are
skipped.
Default: ALL
MEDIA
One of the following archive media:
•
TAPE
•
DISK
•
FILET
•
KODAK
•
ODISK
Default: TAPE
MIGVOL
Name of migration volume
Default: MIGRAT
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
396
Product batch utilities
Return codes
B92ADR01: Updating volume/label information of archive datasets
0
Program terminated normally.
4
The program has not found any data to be updated; the program
terminated normally.
8
One or more errors have occurred during processing, for
example, the program has encountered archive datasets that are
not cataloged.
16
One or more parameters specified in the EXEC statement are
invalid.
24
Error while opening DD OMSOUT or DD B92LOG.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
397
Product batch utilities
B92AGINF: Getting agent information
B92AGINF: Getting agent information
Overview
Parameters
Batch utility B92AGINF can be used to retrieve the following information
from one or more agents:
•
Version and build level of the agent and its modules
•
Operating system and agent user
•
Parameters
•
Rule plan
•
Current log file (max. 29K)
Use the EXEC parm AGENT to specify the name of an agent
(max. 8 characters), for example:
AGENT=WINAGENT
You can also specify a mask, for example:
AGENT=WIN*
You can control which information is to be retrieved via the presence or
absence of the corresponding DD statements.
JCL
You can find JCL for this batch utility in the BETA92.CNTL in member
B92AGINF.
+---------------------------------------------------------------------+
|jobcard
|
|//stepname EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92AGINF,SIGNON=YES,AGENT=agentname')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DUMMY
|
|//*
|
|//VERSION DD SYSOUT=*
|
|//SYSINFO DD SYSOUT=*
|
|//PARAMS
DD SYSOUT=*
|
|//RULEPLAN DD SYSOUT=*
|
|//LOGFILE DD SYSOUT=*
|
+---------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
398
Product batch utilities
DD statements
B92AGINF: Getting agent information
DD statement
Description
VERSION
Shows information on the version and build level of the
agent and its modules
SYSINFO
Shows information on the operation system and the
name of the agent user
Operation system information under Unix can include
network name, release, version, and processor type.
Operation system information under Windows can
include version, service pack, and build number.
PARAMS
Shows information on all the parameter settings in the
agent configuration file B92/params.ini
For more information on these parameters, see "Agent
configuration file B92/params.ini" in _beta job|z
Installation and System Guide.
Return codes
RULEPLAN
Shows the current rule plan of the agent
LOGFILE
Shows the most recent information from the current log
file (max. 29K)
0
The program terminated normally.
8
The program could not find an agent of the specified name.
Check the specified agent name or mask in the EXEC parm or the
agent definitions in _beta log|z (Option A.2.6).
24
Note on local agent
programs
The STC was inactive when batch job B92AGINF was started.
Instead of the B92AGINF batch utility, you can also use the command-line
program b92rac on the EJM agent to retrieve the described information
(see "b48rac and b92rac: Getting agent information").
The version information can also be retrieved via version.exe under
Windows or version under Unix.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
399
Product batch utilities
B92ARPRI: List archiving
B92ARPRI: List archiving
Overview
Archive utility B92ARPRI archives sysout lists and the associated job
information to archive media. You can start the batch utility B92ARPRI
from the BETA92.CNTL or under online option A.3.1, option D1 (see
"Tailoring JCL for batch utilities (Option A.3.1)" on page 175).
B92ARPRI is included in the B92DAILY job (see "B92DAILY: Daily job" on
page 442).
Archiving process
B92ARPRI archives all lists that are in status Pend. "Pend" means that a
list is marked for archiving, but has not been archived yet.
•
Lists and jobs will only be marked as archived after the archive dataset
has been successfully closed.
•
If an error occurs during the archiving process, batch utility B92ARPI
can simply be restarted because lists and jobs will only be marked as
archived once the archive dataset has been successfully closed, i.e.
the archiving process finished without errors.
Archive processes can be started in parallel (faster archiving). For more
information, see "Parallel archiving" on page 403.
Archive pool
A separate archive volume is allocated for every archive pool. When the
volume is full, a new one is requested and the job continues automatically.
The archive job dynamically allocates the necessary archive volumes.
Single archiving mode requires one free unit (disk, tape, or optical disk),
dual archiving mode requires two free units.
Archive retention period
The archive retention period of lists is defined in the job group. B92ARPRI
sorts the lists according to their archive retention periods, and assigns
them to the archive pool with the same archive medium as the job group
and the same or next higher retention period.
The archive retention period starts on the day of the archive run, not after
the online retention period is over. The actual retention period in the
archive may be higher than the archive retention period defined in the job
group, as shown in the following examples:
•
The job group defines an archive retention period of 30 days, but the
best matching archive pool defines a retention period of 40 days. This
will lead to a factual archive retention period of 40 days.
•
The job group and the archive pool define an archive retention period
of 30 days on tape. As each archive run adds a new archive dataset to
an active tape, the expiration date of the tape volume is set anew to 30
days at each run. After four runs, the factual archive retention period of
the first archive dataset on the volume will be 34 days.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
400
Product batch utilities
B92ARPRI: List archiving
If there is no suitable archive pool for a list (retention period too short or
wrong archive medium), the list remains on the online spool with status
Pend. The archive utility report prints the names of all lists that could not
be assigned to any pool. Modify the job group definitions or archive pool
definitions to ensure that the lists will be archived at the next run of the
archive batch utility.
After archiving, lists remain on the spool for the defined online retention
period which is determined by the job group and the queue. After the
online retention period has expired, lists are deleted from the online spool
by the batch utility B92CLLST.
JCL
You can find JCL for this batch utility in the BETA92.CNTL in member
B92ARPRI and in member B92DAILY.
+-------------------------------------------------------------------+
|jobcard
|
|//ARCH001 EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92ARPRI,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DISP=SHR,DSN=BETA92.DB.DEF
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//*
|
|//OMSPRINT DD SYSOUT=*
|
|//OMSERROR DD SYSOUT=*
|
|//SYSPRINT DD SYSOUT=*
|
|//B92LOG
DD SYSOUT=*
|
+-------------------------------------------------------------------+
Logging errors
If errors occur during the archive process, they will be written to
DD OMSERROR. If DD OMSERROR is not coded, message "IEC130I
OMSERROR DD STATEMENT MISSING" is written to the JESMSGLG
and the error messages are written to DD OMSPRINT instead.
Analyze mode
(simulation)
Code TYPE=ANALYZE in the EXEC parm if you want to run the program
in analyze mode.
In analyze mode, B92ARPRI prints the report that shows which lists would
be archived, without actually archiving them.
//ARCH001
//
//
Return codes
EXEC PGM=BST01RFF,REGION=0M,
PARM=('S=92,B01LST=xx,B92LST=xx',
'PGM=B92ARPRI,SIGNON=YES,TYPE=ANALYZE')
0
Program terminated normally.
4
No lists to be archived found.
8
An error occurred.
16
Severe error occurred.
24
Started task unavailable during batch utility run.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
401
Product batch utilities
B92LOG
B92ARPRI: List archiving
B92LOG logs job group information and other settings that affect the
processing of B92ARPRI.
B92LOG is also used for logging error conditions that can occur during the
program run.
OMSPRINT
+------------------------------------------------------------------------------------------------------------------+
|BETA92 V7R2
- LIST ARCHIVE UTILITY (ERROR SUMMARY)
Page
1 |
|
|
|JOBNAME
JESID
DATE
TIME
DSID
DDNAME
STEP
PROCSTEP
POOL
MEDIA ACTION
|
|-------- -------- ---------- -------- -------- -------- -------- -------- -------- ----- -------------------------|
|B92T3DA J0016650 20.12.2021 14:09:23 00000263 B92LOG
ARCH001
POOL2
DISK Archive FAILED (Run Cleanup)|
|
|
|
|
|
|
|
|
|BETA 92 V7R2
- LIST ARCHIVE UTILITY
Page
2 |
|
|
|JOBNAME
JESID
DATE
TIME
DSID
DDNAME
STEP
PROCSTEP
POOL
MEDIA ACTION
|
|-------- -------- ---------- -------- -------- -------- -------- -------- -------- ----- -------------------------|
|DSNAME:BETA92.ARCHIVE.POOL2.D020.E21354.N995
VOLUME:OMS010 UNIT:3390
EXPDT:19.12.2022
|
|B92T3DA J0016650 20.12.2021 14:09:23 00000001 JESJCLIN JES2
POOL2
DISK Archived
|
|B92T3DA J0016650 20.12.2021 14:09:23 00000002 JESMSGLG JES2
POOL2
DISK Archived
|
|B92T3DA J0016650 20.12.2021 14:09:23 00000003 JESJCL
JES2
POOL2
DISK Archived
|
|B92T3DA J0016650 20.12.2021 14:09:23 00000004 JESYSMSG JES2
POOL2
DISK Archived
|
|B92T3DA J0016650 20.12.2021 14:09:23 00000259 OMSPRINT ARCH001
POOL2
DISK Archived
|
|B92T3DA J0016650 20.12.2021 14:09:23 *
*
*
*
POOL2
DISK Archived
|
+------------------------------------------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
402
Product batch utilities
B92ARPRI: List archiving
Parallel archiving
Overview
Parallel archiving has the following advantages:
•
Archiving in up to 4 individual pools non-scheduled and at the same time
•
Up to 4 pools can be excluded from archiving
Recommended:
Use only for dedicated
pools
If you want to use parallel archiving, you should only use it for archiving
into dedicated pools (also called client archive pools).
Defining dedicated pools
All archive pools are defined under option A.A.1 "Archive Pool Definition"
(see page 206).
Client archive pools enable you to archive the data of multiple clients in
separate pools.
Specifying the name of an existing archive pool in the Pool (opt.) field of
one or more job group definitions makes an archive pool into a dedicated
archive pool (see "Job group (Option A.1.2)" on page 103).
_beta log|z does not use dedicated archive pools for other job groups.
Prerequisites for parallel
archiving
•
Set the LST parameter B92_MULTI_ARCHIVE to YES to enable
parallel archiving.
•
Use the following parameters in the EXEC parm of the JCL of
B92ARPRI to specify which archive pools are to be used for parallel
archiving:
POOL[1..]=poolname enables you to specify up to four pool names.
MODE=I[NC] means that the specified pools are to be included into
archiving, whereas MODE=E[XC] means that the specified pools are to
be excluded from archiving.
Note: B92ARPRI does not check whether the archive pools used for
parallel archiving are dedicated archive pools.
Example 1:
Archiving in one pool
The following example shows how to include the individual pool TAPE0461
for archiving:
//ARCH001 EXEC PGM=BST01RFF,REGION=0M,
//
PARM=('S=92,B01LST=00,B92LST=00',
//
'PGM=B92ARPRI,SIGNON=YES,MODE=I',
//
'POOL1=TAPE0461')
When this B92ARPRI job has ended with RC=0, you can find the name of
the included pool under the DD name B92LOG:
parallel archiving enabled
INCLUDE mode specified
POOL: TAPE0461 included.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
403
Product batch utilities
Example 2:
Archiving in two pools
B92ARPRI: List archiving
Code the following to include the two pools TAPE0010 and TAPE0020 for
archiving:
//ARCH002 EXEC PGM=BST01RFF,REGION=0M,
//
PARM=('S=92,B01LST=00,B92LST=00',
//
'PGM=B92ARPRI,SIGNON=YES,MODE=I',
//
'POOL1=TAPE0010,POOL2=TAPE0020')
When this B92ARPRI job has ended with RC=0, you can find the names of
the included pools under the DD name B92LOG:
parallel archiving enabled
INCLUDE mode specified
POOL: TAPE0010 included.
POOL: TAPE0020 included.
Example 3:
Excluding pools from
archiving
Code the following to exclude the two pools TAPE0030 and TAPE0040
from archiving:
//ARCH003 EXEC PGM=BST01RFF,REGION=0M,
//
PARM=('S=92,B01LST=00,B92LST=00',
//
'PGM=B92ARPRI,SIGNON=YES,MODE=E',
//
'POOL1=TAPE0030,POOL2=TAPE0040')
When this B92ARPRI job has ended with RC=0, you can find the names of
the excluded pools under the DD name B92LOG:
parallel archiving enabled
EXCLUDE mode specified
POOL: TAPE0030 excluded.
POOL: TAPE0040 excluded.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
404
Product batch utilities
B92ARPRI: List archiving
Errors during archiving
No matching archive pool
B92ARPRI sorts all lists with status Arch=Pend according to their archive
retention periods and assigns them to the archive pool having the same
archive medium as the job group and the same or next higher retention
period. If the utility does not find a suitable pool, the lists are skipped and
remain on the online spool with status Arch=Pend.
To archive these lists, define an archive pool that uses the same archive
medium as the job group and has the same or a higher retention period.
The lists will then be archived at the next run of the archive utility.
Archive FAILED
When running in normal mode, B92ARPRI does not archive lists that are
corrupt. Corrupt lists will be logged with the message "Archive FAILED".
To archive corrupt lists:
1. Check whether there is an archive pool named SPECIAL.
If there is not, define an archive pool under this name.
2. Add parameter TYPE=CLEANUP to the PARM statement of job
B92ARPRI and submit this job.
//ARCH001
//
//
EXEC PGM=BST01RFF,REGION=0M,
PARM=('S=92,B01LST=xx,B92LST=xx',
'PGM=B92ARPRI,SIGNON=YES,TYPE=CLEANUP')
B92ARPRI replaces corrupt pages with dummy pages and archives
the corresponding lists to archive pool SPECIAL.
Note: If TYPE=CLEANUP is coded, B92ARPRI archives only lists that are
corrupt. Therefore do not add this parameter to the daily archive run.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
405
Product batch utilities
B92ARSEC: Job record cleanup
B92ARSEC: Job record cleanup
Overview
Batch utility B92ARSEC deletes job base records and job information
records from the JOB database when the online retention period of these
records has expired.
B92ARSEC is included in the B92DAILY job (see "B92DAILY: Daily job"
on page 442).
You can start the batch utility B92ARSEC from the BETA92.CNTL or
under online option A.3.1, option D3 (see "Tailoring JCL for batch utilities
(Option A.3.1)" on page 175).
JCL
You can find JCL for this batch utility in the BETA92.CNTL in member
B92ARSEC and in member B92DAILY.
+-------------------------------------------------------------------+
|jobcard
|
|//ARCH002 EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92ARSEC,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BSA.LOAD
|
|//
DD DISP=SHR,DSN=BETA92.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DISP=SHR,DSN=BETA92.DB.DEF
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//*
|
|//OMSPRINT DD SYSOUT=*
|
|//SYSPRINT DD SYSOUT=*
|
|//B92LOG
DD SYSOUT=*
|
|//*
|
+-------------------------------------------------------------------+
Analyze mode
(simulation)
Code TYPE=ANALYZE in the EXEC parm if you want to run the program
in analyze mode.
In analyze mode, B92ARSEC creates the OMSPRINT report that shows
which jobs would be deleted without actually deleting them.
//ARCH002
//
//
EXEC PGM=BST01RFF,REGION=0M,
PARM=('S=92,B01LST=xx,B92LST=xx',
'PGM=B92ARSEC,SIGNON=YES,TYPE=ANALYZE')
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
406
Product batch utilities
Return codes
B92ARSEC: Job record cleanup
0
Program terminated normally.
4
No job base records were deleted.
8
An error occurred.
When a warning is issued, check whether the maximum online
retention period for generations has been specified in the field
Max. Online RETPD for Generations under option A.1. 2 "Job
Group" (see page 103) or under option A.S.3 "Global Options"
(see page 230).
Make sure that a value in days (1..9999) has been entered.
Note: The entry under option A.1.2 overrides the entry under
option A.S.3 when both fields are filled with values.
B92LOG
16
Severe error occurred.
24
Started task unavailable during utility run.
B92LOG logs job group information and other settings that affect the
processing of B92ARSEC.
B92LOG is also used for logging error conditions that can occur during the
program run.
OMSPRINT
+--------------------------------------------------------------------------------------------------------+
|BETA92 V7R2
- JOB RECORD CLEANUP UTILITY
2017-12-06 11:07:29 PAGE 1|
|
|
|
JOB INFO JOB REC. ONLINE
|
|JOBNAME JESID
DATE
TIME
GROUP
RETPD
RETPD
SINCE
ACTION
|
|-------- -------- ---------- -------- -------- -------- -------- -------- -----------------------|
|UWK4871 USR11218 2017-11-22 11:29:49 SYSTEM
7(D)
7(D)
9(D) DELETED
|
|CHKB48XX J0008829 2017-11-22 13:09:51 SYSTEM
7(D)
7(D)
9(D) DELETED
|
|CHKB48XX USR11221 2017-11-22 13:11:10 SYSTEM
7(D)
7(D)
9(D) DELETED
|
|CHKB48J2 J0008835 2017-11-22 13:12:06 SYSTEM
7(D)
7(D)
9(D) DELETED
|
|CHKB48J2 USR11232 2017-11-22 13:14:34 SYSTEM
7(D)
7(D)
9(D) DELETED
|
|CHKB48J2 J0008850 2017-11-22 13:17:51 SYSTEM
7(D)
7(D)
9(D) DELETED
|
|CHKB48J2 USR11246 2017-11-22 13:20:05 SYSTEM
7(D)
7(D)
9(D) DELETED
|
|CHKB48J2 J0008853 2017-11-22 13:21:30 *DELETE*
DELETED
|
|CHKB48J2 USR11257 2017-11-22 13:22:48 *DELETE*
DELETED
|
|CHKB48J2 J0008859 2017-11-22 13:24:29 SYSTEM
7(D)
7(D)
9(D) DELETED
|
|CHKB48J2 USR11268 2017-11-22 13:25:47 SYSTEM
7(D)
7(D)
9(D) DELETED
|
|REJJOB1 J0009500 2017-11-23 08:16:54 REJGRP1
1(D)
5(D)
9(D) DELETED
|
|REJJOB2 J0009501 2017-11-23 08:17:01 REJGRP2
2(D)
5(D)
9(D) DELETED
|
|REJJOB3 J0009502 2017-11-23 08:17:10 REJGRP3
3(D)
5(D)
9(D) DELETED
|
|REJGENER J0009731 2017-11-23 08:28:51 REJGENER
5(G)
6(G) DELETED
|
|REJGENER J0009732 2017-11-23 08:28:59 REJGENER
5(G)
7(G) DELETED
|
|
|
| 16 JOBS HAVE BEEN DELETED.
|
| 0 JOBS PROCESSED WHICH EXCEEDED LIST NUMBER THRESHOLD.
|
|
|
|CURRENT INSTALLATION IS SET TO 5 WORK DAYS PER WEEK.
|
|JOBGROUP SELECTION WAS DONE DUE TO BEST MATCHING MASK.
|
|ONLY KEEP JOB BASE RECORD SET TO 'NO'.
|
|
|
|PROGRAM B92ARSEC (NONE
) ENDED WITH RC(0).
|
+--------------------------------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
407
Product batch utilities
Note on columns
Note on list number
threshold
B92ARSEC: Job record cleanup
Column
Description
DATE/TIME
The date and time listed apply to the time the last list of a
job was read into _beta log|z.
JOB INFO RETPD
This value indicates the online retention period of the job
info record (as explicitly specified in the job group definition
or deducted on the basis of Only keep Job Base Record).
JOB REC RETPD
This value indicates the online retention period of the job
base record in days or generations (as specified in the job
group definition).
ONLINE SINCE
This value indiciates the number of workdays that the job
has been online.
COUNT
This column displays how long the job base record has
actually been in _beta log|z; the number refers to either
days (D) or generations (G).
ACTION
If job cleanup has been successful, this column displays
the message "DELETED".
To reduce the risk of memory shortage, command buffering is disabled
when deleting the records of jobs with many lists. By default, jobs with
more than 100 lists fall into this category. The LST parameter
B92_DAILY_THXL defines the threshold value.
For informative reasons, OMSPRINT includes information on how many
jobs of this category were processed:
n JOBS PROCESSED WHICH EXCEEDED LIST NUMBER THRESHOLD.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
408
Product batch utilities
B92BCAPI: Querying the database via command API
B92BCAPI: Querying the database via command API
Overview
The batch utility B92BCAPI can be used to access the _beta log|z
database via the command API, for example, to retrieve information such
as usage data and reader statistics in batch mode.
Note on reader statistics
Reader statistics don't include data read in from the recovery dataset
during STC restart. Some numbers from slave STCs will also not be
included if the master STC is unavailable when slaves are stopped.
Reader statistics should therefore not be used for accounting purposes.
JCL
You can find JCL for this batch utility in the BETA92.CNTL in member
B92BCAPI.
+------------------------------------------------------------------------+
|jobcard
|
|//B92BCAPI EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92BCAPI,SIGNON=YES',
|
|//
'CAPI_TRACE=NO ',
|
|//
'CAPI_FLIST=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//*
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//SYSABEND DD SYSOUT=*
|
|//CMDIN
DD *
|
|command_to_be_executed
|
|/*
|
|//CMDOUT
DD SYSOUT=*,
|
|//
DCB=(LRECL=8192,BLKSIZE=8192,RECFM=FB)
|
|/*
|
+------------------------------------------------------------------------+
Return codes
0
Program ended normally.
4
Program ended with warnings.
8
Internal error has occurred.
16
No data found.
20
Error reported by backend, for example, syntax error.
24
Communication error.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
409
Product batch utilities
DD statements
B92BCAPI: Querying the database via command API
DD statement
Description
STEPLIB
Load libraries (normally BETA92.LOAD and BSA.LOAD)
SFFPARM
Parameter library (BETA.PARMLIB)
The members B01LSTxx and B92LSTxx must be located
in this library.
EXEC parameters
SFFFDUMP
Dataset for subsystem dumps (if needed)
SYSUDUMP
Dataset for system dumps (if needed)
SYSABEND
Dataset for abends (if needed)
CMDIN
Dataset containing the commands to be executed
CMDOUT
Dataset for command output
Parameter
Description
CAPI_FLIST
YES
Each field name/value pair is output on a
separate line
NO
One line is output per record
Default: NO
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
410
Product batch utilities
CMDIN parameters
B92BCAPI: Querying the database via command API
Specify the commands to be executed under DD CMDIN.
Following is a selection of the product-specific commands:
Command
Description
JOB_SEL
Selects jobs
JOB_GET
Gets information on a single job
JOB_STEP_SEL
Selects steps of a single job
JOB_LIST_SEL
Selects lists of a single job
JOB_LIST_GET
Gets a list of a single job
JOB_JCL_SUB
Submits JCL on a z/OS system
READER_SEL
Selects readers
READER_GET
Gets information on a single reader
READER_STOP
Stops a single reader
READER_START
Starts a single reader
READER_RESTART
Restarts a single reader
READER_USAGE_SEL Determines usage statistics of readers
READER_USAGE_
HISTORY_SEL
Selects statistical information on a single reader
USAGE_SEL
Selects statistical information
The command interface is self-descriptive. The following set of commands
is available to get information on available functions, parameters, and
fields:
Command
Description
FUNCTION_LST
Returns a list of all available functions
PARAMETER_LST
Returns a list of all parameters for a specified function
FIELD_LST
Returns a list of all fields for a specified function
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
411
Product batch utilities
CMDIN syntax
B92BCAPI: Querying the database via command API
You can specify a single command with its parameters in DD CMDIN.
You can code the entire string on a single line or you can continue it over
multiple lines like this...
FUNCTION_LST
FIELDS(FUNCNAME,DESC)
...or like this:
FUNCTION_LST
FIELDS(
FUNCNAME,
DESC
)
White space can be used for better readability.
Example 1
CMDIN:
FUNCTION_LST FIELDS(FUNCNAME,DESC)
CMDOUT (with CAPI_FLIST=YES):
FIELD
: VALUE
--------------------------------------------------------------------------FUNCNAME : VERSION_GET
DESC
: Returns the backend type, a description and the version number...
--------------------------------------------------------------------------FUNCNAME : FUNCTION_LST
DESC
: Returns a list of all available functions.
--------------------------------------------------------------------------FUNCNAME : PARAMETER_LST
DESC
: Returns a list of all parameters for a specified function.
--------------------------------------------------------------------------FUNCNAME : FIELD_LST
DESC
: Returns a list of all fields for a specified function.
--------------------------------------------------------------------------FUNCNAME : JOB_SEL
DESC
: Select jobs.
--------------------------------------------------------------------------...
Code FUNCTION_LST FIELDS(*) or simply FUNCTION_LST to return all
fields.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
412
Product batch utilities
Example 2
B92BCAPI: Querying the database via command API
CMDIN:
PARAMETER_LST FUNCNAME (JOB_SEL)
CMDOUT (with CAPI_FLIST=YES):
FIELD
: VALUE
--------------------------------------------------------------------------PARMNAME : LDAYS
LENGTH
: 2
FMTI
: S
REQUIRED : N
EMPTY
: Y
WILDCARD : N
UPRCASE : N
VALUES
: 0..99
DESC
: Selection on the last days.
--------------------------------------------------------------------------PARMNAME : LHOURS
LENGTH
: 2
FMTI
: S
REQUIRED : N
EMPTY
: Y
WILDCARD : N
UPRCASE : N
VALUES
: 0..99
DESC
: Selection on the last hours.
--------------------------------------------------------------------------PARMNAME : LMINUTES
LENGTH
: 2
FMTI
: S
REQUIRED : N
EMPTY
: Y
WILDCARD : N
UPRCASE : N
VALUES
: 0..99
DESC
: Selection on the last minutes.
--------------------------------------------------------------------------...
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
413
Product batch utilities
Example 3
B92BCAPI: Querying the database via command API
CMDIN:
FIELD_LST FUNCNAME(JOB_SEL)
CMDOUT (with CAPI_FLIST=YES):
FIELD
: VALUE
--------------------------------------------------------------------------FLDNAME : JOBKEY
FLDLNAME : JOB_KEY
LENGTH
: 35
FMTI
: C
DEF
: N
DESC
: Unique key to a processed job.
--------------------------------------------------------------------------FLDNAME : SUBDATE
FLDLNAME : SUBMIT_DATE
LENGTH
: 10
FMTI
: D
DEF
: N
DESC
: Submit date of job.
--------------------------------------------------------------------------FLDNAME : SUBTIME
FLDLNAME : SUBMIT_TIME
LENGTH
: 11
FMTI
: T
DEF
: N
DESC
: Submit time of job.
--------------------------------------------------------------------------FLDNAME : SUBSTMP
FLDLNAME : SUBMIT_TIMESTAMP
LENGTH
: 22
FMTI
: C
DEF
: Y
DESC
: Submit timestamp of job.
--------------------------------------------------------------------------...
Example 4
CMDIN:
VERSION_GET
CMDOUT (with CAPI_FLIST=YES):
FIELD
: VALUE
--------------------------------------------------------------------------DATASRC : STC
TYPE
: OMS
TITLE
: beta logz (Beta 92)
VERSION : V7.2
BUILD
: nnnnn
SYSNAME : BETA92P
SYSLVL
: V7R2-nn
SYSPTF
: xyznnnn
BSALVL
: 1771-03
BSAPTF
: PBSnnnn
---------------------------------------------------------------------------
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
414
Product batch utilities
B92BFJBR: Job information report
B92BFJBR: Job information report
Overview
B92BFJBR can be used to print job information in a report. The information
that can be printed corresponds to the information that is displayed online
in the "Job Information Table".
Option 3 - Utilities
You can also use option 3.3 to generate and submit JCL for the
B92BFJBR batch utility.
For more information, see "Printing job information report (Option 3.3 B92BFJBR)" in _beta log|z User Guide.
JCL
You can find JCL for this batch utility in the BETA92.CNTL in member
B92BFJBR.
+-------------------------------------------------------------------+
|jobcard
|
|//REPORT
EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92BFJBR,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DUMMY
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//*
|
|//OMSPRINT DD SYSOUT=*
|
|//SYSIN
DD *
|
|REPORT
|
| SDATE(TODAY)
|
| STIME(01.00.00)
|
| PDATE(TODAY)
|
| PTIME(22.00.00)
|
| JOBNAME(AV1BETA)
|
| JOBID(JOB00012)
|
| NETID(AV1)
|
| QUEUE(INPUT)
|
| SYSID(BETA)
|
| ERRORS(YES)
|
| MSGCLASS(Q)
|
| GROUP(SYSTEM)
|
| ERRTEXT('CC 0008')
|
| DIAGS(YES)
|
| STEPS(YES)
|
| NOTES(NO)
|
| EXTRE(YES)
|
| LISTS(YES)
|
|/*
|
+-------------------------------------------------------------------+
Return codes
0
Program terminated normally.
4
No job matched selection criteria.
8
An error occurred.
16
Severe error occurred.
24
Started task unavailable during utility run.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
415
Product batch utilities
SYSIN parameters
B92BFJBR: Job information report
Parameter
Description
REPORT
Begins the printing process
This parameter does not have a value. The parameter
has to be coded at initial position.
SDATE(start_date)
The beginning date for the job selection. This parameter
is required.
STIME(start_time)
The beginning time for the job selection. This parameter
is optional.
Default: 00:00:00
PDATE(end_date)
The ending date for the job selection. This parameter is
required.
PTIME(end_time)
The ending time for the job selection. This parameter is
optional.
Default: 23:59:59
JOBNAME(jobname)
Defines a full job name or a mask for the job selection
process. If JOBID has not been entered this parameter
is required.
JOBID(job_ID)
Defines a full JES Job ID name or a mask for the job
selection process. If job name has not been entered this
parameter is required.
NETID(net_id)
Defines a full JES3 or _beta log|z NET ID name or a
mask for the job selection process. This parameter is
optional, and when not used the net ID will not limit the
job selection.
QUEUE(queue)
Defines a _beta log|z queue. This parameter is optional.
SYSID(system_id)
Defines a _beta log|z system ID. This parameter is
optional.
ERRORS(YES|NO)
YES selects all jobs with errors and NO all error free
jobs. When not used the presence of errors will not limit
job selection.
MSGCLASS(msgclass) Defines a JES message class. Only jobs with this
message class will be selected. This parameter is
optional, and when not present, jobs from all _beta log|z
message classes can be selected.
GROUP(group_name)
Defines a job group name or a mask for the job
selection process. When not used the job group name
will not limit the job selection.
ERRTEXT(error_text)
You can delimit the job selection by a specific error
code.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
416
Product batch utilities
B92BFJBR: Job information report
The following criteria do not delimit the job selection process but rather
present output options for the list:
Parameter
Description
DIAGS(YES|NO)
Determines whether diagnostic messages are included
in the report
Default: NO
STEPS(YES|NO)
Determines whether job step and procstep information
is included in the report
Default: NO
NOTES(YES|NO)
Determines whether user notes are included in the
report
Default: NO
EXTRE(YES|NO)
Determines whether extension records (JXR and JBRE)
are included in the report
Default: NO
LISTS(YES|NO)
Determines whether list information is included in the
report
Default: NO
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
417
Product batch utilities
B92BFJBR: Job information report
OMSPRINT
+-----------------------------------------------------------------------------------------------------------------------------------------+
|BETA 92 V7R2
- JOB CONTROL REPORT UTILITY
2020-09-24 13:31:52 PAGE
0|
|
|
|PROGRAM B92BFJBR (POMnnnn) STARTED.
|
|
|
|REPORT
|
| SDATE(TODAY)
|
| STIME(00:00:00)
|
| PDATE(TODAY)
|
| PTIME(23:59:59)
|
| JOBNAME(REJ#§DMP)
|
| DIAGS(YES)
|
| STEPS(YES)
|
| NOTES(YES)
|
| EXTRE(YES)
|
| LISTS(YES)
|
|BETA 92 V7R2
- JOB CONTROL REPORT UTILITY
2020-09-24 13:31:52 PAGE
1 |
|
|
|JOBNAME
JES-ID
SUB DATE SUB TIME STA DATE STA TIME END DATE END TIME
STATUS
ERROR
USER
JOBGROUP NET ID JOBCLASS MC |
|-------- -------- ---------- -------- ---------- -------- ---------- -------- ---------- -------- -------- -------- -------- -------- -- |
|REJ#§DMP J0012747 2020-09-24 13:25:39 2020-09-24 13:25:39 2020-09-24 13:25:40 I
REJ#GRP DEBETAJ2 A
Y |
|** STEP INFO
: STEPNAME PROCSTEP ERRORTXT CC
CPU-TIME
SRB-TIME PRIVATE
HIGH PRV
|
|
-------- -------- -------- ----- ---------- ---------- ---------- ---------|
|
REFBACK
0000 0:00:00.00 0:00:00.00 4
K 0
K
|
|
DELETE
0000 0:00:00.02 0:00:00.00 248
K 40
K
|
|
DUMP1
0000 0:00:00.04 0:00:00.00 224
K 440
K
|
|
DUMP2
0000 0:00:00.05 0:00:00.01 224
K 440
K
|
|
DUMP3
0000 0:00:00.02 0:00:00.00 224
K 440
K
|
|** LIST INFO
: DDNAME
STEPNAME PROCSTEP PAGES
LINES CLASS
FORM
ARCH STATUS
|
|
-------- -------- -------- ------- ------- ----- -------- ---- ------|
|
JESJCLIN JES2
1
56
Y
STD
PEND ONLINE
|
|
JESMSGLG JES2
1
24
Y
STD
PEND ONLINE
|
|
JESJCL
JES2
1
44
Y
STD
PEND ONLINE
|
|
JESYSMSG JES2
1
81
Y
STD
PEND ONLINE
|
|
SYSPRINT DELETE
1
21
Y
STD
PEND ONLINE
|
|
SYSPRINT DUMP1
1
12
Y
STD
PEND ONLINE
|
|
SYSPRINT DUMP2
2
58
Y
STD
PEND ONLINE
|
|
SYSPRINT DUMP3
1
12
Y
STD
PEND ONLINE
|
|======================================================================================================================================== |
|
|
|1 JOB(S) MATCHED SELECTION CRITERIA.
|
|
|
|PROGRAM B92BFJBR (POMnnnn) ENDED WITH RC(0).
|
+-----------------------------------------------------------------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
418
Product batch utilities
B92BFJGI: Job Group Information
B92BFJGI: Job Group Information
Overview
B92BFJGI can be used to print a cross reference list showing you the job
masks that are defined for a job group.
Option 3 - Utilities
You can also use option 3.2 to generate and submit JCL for the B92BFJGI
batch utility.
For more information, see "Printing job group to job mask relations (Option
3.2 - B92BFJGI)" in _beta log|z User Guide.
JCL
You can find JCL for this batch utility in the BETA92.CNTL in member
B92BFJGI.
+-------------------------------------------------------------------+
|jobcard
|
|//PRINT
EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92BFJGI,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DUMMY
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//*
|
|//OMSPRINT DD SYSOUT=*
|
+-------------------------------------------------------------------+
Return codes
0
Program terminated normally.
4
No character string found.
8
An error occurred.
16
Severe error occurred.
24
Started task unavailable during utility run.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
419
Product batch utilities
OMSPRINT
B92BFJGI: Job Group Information
The Job Group Utility report is a cross reference list showing which job
masks are related to the job groups specified in your subsystem. The
report also shows the online and archive retention periods.
+--------------------------------------------------------------------------------------------------------------------------------+
|BETA92 V7R2
- JOB GROUPS TO JOB MASKS RELATIONS
2018-02-22 09:09:27 PAGE
1 |
|
|
|JOB GROUP JOB MASK1
JOB MASK2
JOB MASK3
JOB MASK4
QUEUES
JOB
JOB
ARCHIVE MEDIA |
|
JOB MASK5
JOB MASK6
JOB MASK7
JOB MASK8
INPUT
READY
ERROR
WORK
INFO
RECORD
|
|--------- ----------- ----------- ----------- ----------- -------- -------- -------- -------- -------- -------- -------- ------ |
|CXBDUMMY B92#CXB*
0(D)
0(D)
0(D)
0(D)
0(D)
0(D)
0(D) DISK
|
|ABCGENER ABCGENER
5(G)
5(G)
5(G)
5(G) -------5(G)
0(D) DISK
|
|ABCGRP1
ABCJOB1
1(D)
1(D)
1(D)
1(D)
1(D)
5(D)
0(D) DISK
|
|ABCGRP2
ABCJOB2
2(D)
2(D)
2(D)
2(D)
2(D)
5(D)
0(D) DISK
|
|ABCGRP3
ABCJOB3
ABCJOB4
ABCJOB5
ABCJOB6
3(D)
3(D)
3(D)
3(D)
3(D)
5(D)
0(D) DISK
|
|
ABCJOB7
ABCJOBX
ABCJOBY
ABCJOBZ
|
|ABCGRP4
ABC*
4(D)
4(D)
4(D)
4(D)
4(D)
5(D)
365(D) TAPE
|
|STLGROUP STL*
1(D)
2(D)
3(D)
4(D)
3(D)
10(D)
365(D) TAPE
|
|SYSTEM
*
4(D)
4(D)
4(D)
3(G)
7(D)
7(D)
20(D) DISK
|
|
|
|8 JOB GROUPS WERE PROCESSED.
|
|
|
|PROGRAM B92BFJGI (NONE
) ENDED WITH RC(0).
|
+--------------------------------------------------------------------------------------------------------------------------------+
•
JOB MASK1 through JOB MASK8 shows the job masks of the job
group.
•
INPUT, READY, ERROR and WORK shows the online retention
period of the job lists according to queues. D means number of
workdays, and G means number of generations.
•
JOB INFO shows the online retention period in workdays of the job
information records of the queues. 0(D) or hyphens indicate that the
job info is deleted when the lists are deleted or when the job base
record is deleted. Hyphens are shown when retention periods are
specified in number of generations.
•
JOB RECORD shows the online retention period of the job base
records. D means number of workdays, and G means number of
generations.
•
ARCHIVE shows the archive retention period in calendar days.
•
MEDIA shows the archive medium.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
420
Product batch utilities
B92CLAR2: Clear extended generation archive records
B92CLAR2: Clear extended generation archive records
Overview
The batch utility B92CLAR2 deletes extended generation archive records
(GAREs) from the database.
You can start the batch utility B92CLAR2 from the BETA92.CNTL or under
online option A.3.1, option W2 (see "Tailoring JCL for batch utilities
(Option A.3.1)" on page 175).
GAR/GARE maintenance
Generation archive records (GARs) and extended generation archive
records (GAREs) are stored in archive generation databases.
GARs are deleted by the archive cleanup utility B92CLARC when the
corresponding jobs have expired.
GAREs that are no longer needed must be deleted separately with the
help of the batch utility B92CLAR2.
You should run B92CLAR2 at regular intervals because GAREs take up a
lot of space in the archive generation databases. B92CLAR2 deletes all
GAREs that are older than the specified date or older than the specified
number of days. The archive expiration date of the corresponding jobs is
not checked.
B92CLAR2 is included in the weekly job B92WEEKL (see page 520).
Note: The writing of GAREs can be suppressed via the LST parameter
B92_ARP_NOGARE.
JCL
You can find JCL for this batch utility in the BETA92.CNTL in member
B92CLAR2 and in member B92WEEKL.
+-----------------------------------------------------------------------+
|jobcard
|
|//CLAR2
EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92CLAR2,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DISP=SHR,DSN=BETA92.DB.DEF
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//SYSABEND DD SYSOUT=*
|
|//*
|
|//B92LOG
DD SYSOUT=*
|
|//OMSPRINT DD SYSOUT=*
|
|//*
|
|//SYSIN
DD *
|
|
DAYS(n)
|
|/*
|
+-----------------------------------------------------------------------+
-OR|...
|
|//SYSIN
DD *
|
|
DATE(tt.mm.yyyy)
|
|/*
|
+-----------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
421
Product batch utilities
B92CLAR2: Clear extended generation archive records
Analyze mode
(simulation)
Code TYPE=ANALYZE in the EXEC parm if you want to run the program
in analyze mode.
In analyze mode, B92CLAR2 creates the report that shows which GAREs
would be deleted, without actually deleting them.
//CLAR2
//
//
SYSIN keywords
EXEC PGM=BST01RFF,REGION=0M,
PARM=('S=92,B01LST=xx,B92LST=xx',
'PGM=B92CLAR2,SIGNON=YES,TYPE=ANALYZE')
Parameter
Value
Default
Description
DAYS
0..9999
None
Deletes all GAREs that are older than
the specified number of days
Note: DAYS(0) causes the deletion of
all GAREs.
DATE
Return codes
Valid date in the
date format used
by your system
None
Deletes all GAREs that are older than
the specified date
Example: DATE(27.11.2017) causes
the deletion of the GAREs of all jobs
with a submit date of 26.11.2017 or
earlier.
0
Program terminated normally.
4
No records for deletion were found.
8
An error occurred.
16
Severe error occurred.
24
Started task unavailable during batch utility run.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
422
Product batch utilities
Report
B92CLAR2: Clear extended generation archive records
The program outputs the following information to OMSPRINT:
•
Number of records that have been read
•
Number of records that have been deleted or are to be deleted
+--------------------------------------------------------------------------------------------------+
|BETA92 V7R2 TABLE GARE ENTRIES CLEANUP UTILITY - DELETE RUN
27.11.2017 14:16 Page
1
|
|-------------------------------------------------------------------------------------|
|The following input parameters were processed:
|
|
|
| DAYS(30)
|
|
|
| ALL GARES OLDER THAN 28.10.2017 ARE TO BE DELETED.
|
|
|
|
|
|
|
|BETA92 V7R2 TABLE GARE ENTRIES CLEANUP UTILITY - ANALYZE RUN 26.06.2009 14:16 Page
2
|
|-------------------------------------------------------------------------------------|
|SRCSUBD
SRCSUBT
SRCJOBN RULENAME RULETYPE OPERNAME AGENAME SAPSNAME
ACTION
|
|-------------------------------------------------------------------------------------|
|01.10.2017 16:44:46 B92RUL1 B92RUL1
FILERULE B92OPER
B92AGE1
have been deleted |
|01.10.2017 16:57:31 B92RUL1 B92RUL1
FILERULE B92OPER
B92AGE1
have been deleted |
|
|
|. . . . . . . .
|
|
|
|
|
|*******************************************************************************
|
|*
Generation(1)
3927 GARE records have been deleted
|
|*******************************************************************************
|
|
|
|
|
|*******************************************************************************
|
|*
3927 Total GARE records have been deleted
|
|*******************************************************************************
|
|
|
|
|
|
|
|PROGRAM B92CLAR2 (NONE
) ENDED WITH RC(0).
|
|
|
+--------------------------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
423
Product batch utilities
B92CLARC: Archive cleanup
B92CLARC: Archive cleanup
Overview
The archive cleanup utility B92CLARC deletes expired archive records and
archive information after the corresponding archive datasets have expired.
Use the LST parameter B92_CLARC_JOBDETAIL to log more detailed
information on the records which are to be deleted.
The archive cleanup utility has been included into the weekly job
B92WEEKL (see page 520).
You can start the batch utility B92CLARC from the BETA92.CNTL or under
online option A.3.1, option W1 (see "Tailoring JCL for batch utilities
(Option A.3.1)" on page 175).
B92_CLARC_JOBDETAIL
Use the LST parameter B92_CLARC_JOBDETAIL to control how much
information is written to OMSPRINT by the batch utility B92CLARC:
NO
The report includes information on the archive datasets in use.
This is the default.
YES
In addition to information on the archive datasets in use, the report
includes information on which records are deleted.
See the report examples below.
JCL
You can find JCL for this batch utility in the BETA92.CNTL in member
B92CLARC and in member B92WEEKL.
+-------------------------------------------------------------------+
|jobcard
|
|//CLEANARC EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92CLARC,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DISP=SHR,DSN=BETA92.DB.DEF
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//OMSPRINT DD SYSOUT=*
|
+-------------------------------------------------------------------+
Analyze mode
(simulation)
Code TYPE=ANALYZE in the EXEC parm if you want to run the program
in analyze mode.
In analyze mode, B92CLARC prints a report on all archive records that
would be deleted, without actually deleting them.
//CLEANARC EXEC PGM=BST01RFF,REGION=0M,
//
PARM=('S=92,B01LST=xx,B92LST=xx',
//
'PGM=B92CLARC,SIGNON=YES,TYPE=ANALYZE')
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
424
Product batch utilities
Return codes
Report
(analyze run - no detail)
B92CLARC: Archive cleanup
0
Program terminated normally.
4
No archive information deleted.
8
An error occurred.
16
Severe error occurred.
24
Started task unavailable during batch utility run.
If B92_CLARC_JOBDETAIL=NO and TYPE=ANALYZE, the report written
by B92CLARC looks as follows:
+---------------------------------------------------------------------------------+
|BETA92 V7R2
- ARCHIVE CLEANUP UTILITY ANALYZE RUN 2010-04-19 10:59:54 PAGE 1 |
|
|
| Dataset
Media Volume
|
| -------------------------------------------- ----- -----|
| BETA92.POOL1.D020.E10063.N986
DISK OMS020
|
| BETA92.POOL1.D020.E10063.N985
DISK OMS030
|
| BETA92.POOL1.D020.E10063.N984
DISK OMS020
|
| BETA92.POOL1.D020.E10063.N983
DISK OMS030
|
| BETA92.POOL1.D020.E10063.N982
DISK OMS010
|
| BETA92.POOL1.D020.E10063.N981
DISK OMS000
|
|
|
|
|
|
|
|
|
| TABLE RV2: 4 ARCHIVE RECORDS WOULD BE DELETED.
|
|
|
| TABLE GAR: 7553 GENERATION RECORDS WOULD BE DELETED.
|
|
|
| PROGRAM B92CLARC (POMnnnn ) ENDED WITH RC(0).
|
|
|
+---------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
425
Product batch utilities
Report
(analyze run - detailed)
B92CLARC: Archive cleanup
If B92_CLARC_JOBDETAIL=YES and TYPE=ANALYZE, the report
written by B92CLARC looks as follows:
+---------------------------------------------------------------------------------+
|BETA92 V7R2
- ARCHIVE CLEANUP UTILITY ANALYZE RUN 2010-04-19 10:59:54 PAGE 1 |
|
|
| JOBNAME
DATE
TIME
POOL
MEDIA
EXPDT
ACTION
|
| -------- ---------- -------- -------- ----- ---------- -------|
| B92ALT01 2010-01-13 11:36:05 PNOSAVE TAPE 2010-04-15 EXPIRED
|
| B92ALT01 2010-01-14 11:36:05 PNOSAVE TAPE 2010-04-15 EXPIRED
|
| B92ALT01 2010-01-15 11:36:05 PNOSAVE TAPE 2010-04-15 EXPIRED
|
| B92DAILY 2010-01-16 11:36:06 PNOSAVE TAPE 2010-04-15 EXPIRED
|
|
|
|
|
|BETA92 V7R2
- ARCHIVE CLEANUP UTILITY ANALYZE RUN 2010-04-19 10:59:54 PAGE 2 |
|
|
|
|
| JOBNAME
SRCJOBI
DATE
TIME
EXPDT ACTION
|
| -------- -------- ---------- -------- ---------- -------|
| B48BIMV1 USR13248 2010-03-02 07:38:33 2010-03-24 EXPIRED
|
| MAPPENIR USR13256 2010-03-02 07:38:34 2010-03-24 EXPIRED
|
| MAPPENIR USR13266 2010-03-02 07:38:34 2010-03-24 EXPIRED
|
| MAPPENIR USR13276 2010-03-02 07:38:34 2010-03-24 EXPIRED
|
| B48VARI USR13288 2010-03-02 09:10:55 2010-03-24 EXPIRED
|
| B48VARI2 USR13298 2010-03-02 08:11:09 2010-03-24 EXPIRED
|
|
|
| . . .
|
|
|
|
|
|BETA92 V7R2
- ARCHIVE CLEANUP UTILITY ANALYZE RUN 2010-04-19 10:59:54 PAGE 3 |
|
|
|
|
| Dataset
Media Volume
|
| -------------------------------------------- ----- -----|
| BETA92.POOL1.D020.E10063.N986
DISK OMS020
|
| BETA92.POOL1.D020.E10063.N985
DISK OMS030
|
| BETA92.POOL1.D020.E10063.N984
DISK OMS020
|
| BETA92.POOL1.D020.E10063.N983
DISK OMS030
|
| BETA92.POOL1.D020.E10063.N982
DISK OMS010
|
| BETA92.POOL1.D020.E10063.N981
DISK OMS000
|
|
|
|
|
|
|
|
|
|
|
| TABLE RV2: 4 ARCHIVE RECORDS WOULD BE DELETED.
|
|
|
| TABLE GAR: 7553 GENERATION RECORDS WOULD BE DELETED.
|
|
|
| PROGRAM B92CLARC (POMnnnn ) ENDED WITH RC(0).
|
|
|
+---------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
426
Product batch utilities
Report
(delete run - no detail)
B92CLARC: Archive cleanup
If B92_CLARC_JOBDETAIL=NO and the program does not run in analyze
mode, the report written by B92CLARC looks as follows:
+---------------------------------------------------------------------------------+
|BETA92 V7R2
- ARCHIVE CLEANUP UTILITY - DELETE RUN 2010-04-19 10:59:54 PAGE 1 |
|
|
| Dataset
Media Volume
|
| -------------------------------------------- ----- -----|
| BETA92.POOL1.D020.E10063.N986
DISK OMS020
|
| BETA92.POOL1.D020.E10063.N985
DISK OMS030
|
| BETA92.POOL1.D020.E10063.N984
DISK OMS020
|
| BETA92.POOL1.D020.E10063.N983
DISK OMS030
|
| BETA92.POOL1.D020.E10063.N982
DISK OMS010
|
| BETA92.POOL1.D020.E10063.N981
DISK OMS000
|
|
|
|
|
|
|
|
|
| TABLE RV2: 4 ARCHIVE RECORDS HAVE BEEN DELETED.
|
|
|
| TABLE GAR: 7553 GENERATION RECORDS HAVE BEEN DELETED.
|
|
|
| PROGRAM B92CLARC (POMnnnn ) ENDED WITH RC(0).
|
|
|
+---------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
427
Product batch utilities
Report
(delete run - detailed)
B92CLARC: Archive cleanup
If B92_CLARC_JOBDETAIL=YES and the program does not run in
analyze mode, the report written by B92CLARC looks as follows:
+---------------------------------------------------------------------------------+
|BETA92 V7R2 - ARCHIVE CLEANUP UTILITY - DELETE RUN 2010-04-19 10:59:54 PAGE 1 |
|
|
| JOBNAME
DATE
TIME
POOL
MEDIA
EXPDT
ACTION
|
| -------- ---------- -------- -------- ----- ---------- -------|
| B92ALT01 2010-01-13 11:36:05 PNOSAVE TAPE 2010-04-15 DELETED
|
| B92ALT01 2010-01-14 11:36:05 PNOSAVE TAPE 2010-04-15 DELETED
|
| B92ALT01 2010-01-15 11:36:05 PNOSAVE TAPE 2010-04-15 DELETED
|
| B92DAILY 2010-01-16 11:36:06 PNOSAVE TAPE 2010-04-15 DELETED
|
|
|
|
|
|BETA92 V7R2 - ARCHIVE CLEANUP UTILITY - DELETE RUN 2010-04-19 10:59:54 PAGE 2 |
|
|
|
|
| JOBNAME
SRCJOBI
DATE
TIME
EXPDT ACTION
|
| -------- -------- ---------- -------- ---------- -------|
| B48BIMV1 USR13248 2010-03-02 07:38:33 2010-03-24 DELETED
|
| MAPPENIR USR13256 2010-03-02 07:38:34 2010-03-24 DELETED
|
| MAPPENIR USR13266 2010-03-02 07:38:34 2010-03-24 DELETED
|
| MAPPENIR USR13276 2010-03-02 07:38:34 2010-03-24 DELETED
|
| B48VARI USR13288 2010-03-02 09:10:55 2010-03-24 DELETED
|
| B48VARI2 USR13298 2010-03-02 08:11:09 2010-03-24 DELETED
|
|
|
| . . .
|
|
|
|
|
|BETA92 V7R2 - ARCHIVE CLEANUP UTILITY - DELETE RUN 2010-04-19 10:59:54 PAGE 3 |
|
|
|
|
| Dataset
Media Volume
|
| -------------------------------------------- ----- -----|
| BETA92.POOL1.D020.E10063.N986
DISK OMS020
|
| BETA92.POOL1.D020.E10063.N985
DISK OMS030
|
| BETA92.POOL1.D020.E10063.N984
DISK OMS020
|
| BETA92.POOL1.D020.E10063.N983
DISK OMS030
|
| BETA92.POOL1.D020.E10063.N982
DISK OMS010
|
| BETA92.POOL1.D020.E10063.N981
DISK OMS000
|
|
|
|
|
|
|
|
|
|
|
| TABLE RV2: 4 ARCHIVE RECORDS HAVE BEEN DELETED.
|
|
|
| TABLE GAR: 7553 GENERATION RECORDS HAVE BEEN DELETED.
|
|
|
| PROGRAM B92CLARC (POMnnnn ) ENDED WITH RC(0).
|
|
|
+---------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
428
Product batch utilities
B92CLARS: Cleanup for agent rule status and statistics
B92CLARS: Cleanup for agent rule status and statistics
Overview
Batch utility B92CLARS cleans up the following tables:
ARSTATUS
Contains status information on agent rule runs
B92STATS
Contains statistics on jobs/lists based on origin
RDRSTATS
Contains statistics on jobs/lists based on reader processing
You can start the batch utility B92CLARS from the BETA92.CNTL or
online under option A.3.1, option W3 (see "Tailoring JCL for batch utilities
(Option A.3.1)" on page 175).
Processing
Run B92CLARS at regular intervals with appropriate parameters to
remove obsolete data from the database.
Recommended frequency
We strongly advise you to run B92CLARS at least once a week and have
therefore included this batch utility in the weekly job B92WEEKL (see
page 520).
If the affected tables are used intensively, you may want to move
B92CLARS from B92WEEKL to the daily job B92DAILY (see page 442).
Table cleanup and minimum retention periods
The ARSTATUS table is processed if the ARS_DAYS or DAY parameter is
coded. There is no minimum retention period, but the most recent record
on the execution of a rule on an agent is excluded from deletion by default.
This record is used by the agent as a starting point for the next execution
of the rule.
The B92STATS table is processed if the STAT_DAYS parameter is coded.
The minimum retention period is 730 days.
The RDRSTATS table is processed if the RDR_DAYS parameter is coded.
The minimum retention period is 30 days.
All tables can be processed in one program run.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
429
Product batch utilities
JCL
B92CLARS: Cleanup for agent rule status and statistics
The example shows the JCL of the B92CLARS utility:
+-------------------------------------------------------------------+
|jobcard
|
|//CLARS
EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92CLARS,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DUMMY
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//SYSABEND DD SYSOUT=*
|
|//*
|
|//B92LOG
DD SYSOUT=*
|
|//OMSPRINT DD SYSOUT=*
|
|//SYSIN
DD *
|
|
ARS_DAY(5)
|
|
STAT_DAYS(730)
|
|
RDR_DAY(30)
|
|
MESSAGE(SHORT)
|
|/*
|
+-------------------------------------------------------------------+
Analyze mode
(simulation)
Code TYPE=ANALYZE in the EXEC PARM if you want to run the program
in analyze mode.
In analyze mode, B92CLARS reports on which entries would be deleted
from the tables, without actually deleting them.
//CLARS
//
//
Return codes
EXEC PGM=BST01RFF,REGION=0M,
PARM=('S=92,B01LST=xx,B92LST=xx',
'PGM=B92CLARS,SIGNON=YES,TYPE=ANALYZE')
0
Program terminated normally.
4
No records for deletion were found.
If the program processes more than one table, the job will end
with RC=4 if at least one of the processed tables leads to RC=4.
8
An error occurred.
16
Severe error occurred.
24
Started task unavailable during batch utility run.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
430
Product batch utilities
SYSIN parameters
B92CLARS: Cleanup for agent rule status and statistics
Parameter
Description
ARS_DAYS(nnn)
-orDAY(nnn)
Calculation of the start date on which processing is
to begin in the ARSTATUS table. If ARS_DAYS(0)
is specified, all entries except for the most recent
one are deleted.
STAT_DAYS(nnn)
Calculation of the start date on which processing is
to begin for statistics in the B92STATS table. The
value must be greater than or equal to 720 days.
RDR_DAYS(nnn)
Calculation of the start date on which processing is
to begin for statistics in the RDRSTATS table. The
value must be greater than or equal to 30 days.
MESSAGE(LONG|SHORT) This parameter specifies the format in which the
search results are displayed in the log.
LONG
A detailed log is written to OMSPRINT:
All entries to be deleted are specifically
listed.
SHORT
An overview of entries that have been
deleted or are due for deletion is printed.
Default: LONG
DEL_ALL(YES|NO)
NO
The most recent record from the
ARSTATUS table is excluded from
deletion, even if it is included in the
range defined by ARS_DAYS/DAY.
YES
All entries included in the range defined
by ARS_DAYS/DAY will be deleted from
the ARSTATUS table.
Default: NO
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
431
Product batch utilities
OMSPRINT
B92CLARS: Cleanup for agent rule status and statistics
The program outputs the following information to DD OMSPRINT:
•
Number of records that have been read
•
Number of records that have been kept (only for table ARSTATUS)
•
Number of records that have been deleted or are to be deleted
+-------------------------------------------------------------------------------------------------------------------+
|B92CLARS CLEANUP UTILITTY
27.07.2021 13:38:24
Page 1
|
|----------------------------------------------------------------------------------------------------------------- |
|The following input parameters were processed:
|
| ARS_DAYS(10)
|
| STAT_DAYS(730)
|
| RDR_DAYS(30)
|
| MESSAGE(SHORT)
|
|
|
|
|
| Enddate for deletion of Agent-Rule Status entries is 17.07.2021, endtime is 23:59:59
|
| Enddate for deletion of Beta 92 Statistics entries is 28.07.2019, endtime is 23:59:59
|
| Enddate for deletion of Reader Statistics entries is 27.06.2021, endtime is 23:59:59
|
|
|
|BETA 92 V7R2
AGENT-RULE STATUS CLEANUP - ANALYZE RUN
27.07.2021 13:38:24
Page 2
|
|----------------------------------------------------------------------------------------------------------------- |
|
RULENAME RULETYPE AGENAME
ACTION
|
|----------------------------------------------------------------------------------------------------------------- |
| *****
CHKWINEV FILERULE CHK72W10 0 records would be deleted ***
|
| *****
ELOGRUL$ FILERULE CHK72L12 0 records would be deleted ***
|
| *****
RODALTAB FILERULE ROD72L12 189 records would be deleted ***
|
| *****
ROD15KB FILERULE ROD72L12 22602 records would be deleted ***
|
| *****
ROD15KB FILERULE ROD72PLX 22625 records would be deleted ***
|
| ...
|
|BETA 92 V7R2
AGENT-RULE STATUS CLEANUP - ANALYZE RUN
27.07.2021 13:38:24
Page 4
|
|
|
|
******************************************************************************************
|
|
*
*
|
|
*
Table ARSTATUS:
68337 total number of processed records
*
|
|
*
================================================================================
*
|
|
*
15 Agent-Rule Status records would be kept
*
|
|
*
68322 Agent-Rule Status records would be deleted
*
|
|
*
*
|
|
******************************************************************************************
|
|
|
| ARSTATUS Cleanup ended with RC(0).
|
|
|
|BETA 92 V7R2
B92 STATISTICS CLEANUP - ANALYZE RUN
27.07.2021 13:38:24
Page 5 |
|----------------------------------------------------------------------------------------------------------------- |
| DATE
HOSTNAME
ACTION
|
|----------------------------------------------------------------------------------------------------------------- |
| *****
EDF
789 records would be deleted ***
|
| *****
MVS
2919 records would be deleted ***
|
| ...
|
|BETA 92 V7R2
B92 STATISTICS CLEANUP - ANALYZE RUN
27.07.2021 13:38:24
Page 6 |
|
|
|
******************************************************************************************
|
|
*
*
|
|
*
Table B92STATS:
3421 total number of processed records
*
|
|
*
================================================================================
*
|
|
*
*
|
|
*
3421 Beta 92 Statistics records would be deleted
*
|
|
*
*
|
|
******************************************************************************************
|
|
|
| RDRSTATS Cleanup ended with RC(0).
|
(continued)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
432
Product batch utilities
B92CLARS: Cleanup for agent rule status and statistics
(continued)
|BETA 92 V7R2
B92 STATISTICS CLEANUP - ANALYZE RUN
27.07.2021 13:38:24
Page 7 |
|----------------------------------------------------------------------------------------------------------------- |
| DATE
ACTION
|
|----------------------------------------------------------------------------------------------------------------- |
| 27.04.2021 ***
12 records would be deleted ***
|
| 28.04.2021 ***
13 records would be deleted ***
|
| 29.04.2021 ***
15 records would be deleted ***
|
| 30.04.2021 ***
11 records would be deleted ***
|
| 01.05.2021 ***
2 records would be deleted ***
|
| ...
|
|BETA 92 V7R2
B92 STATISTICS CLEANUP - ANALYZE RUN
27.07.2021 13:38:24
Page 8 |
|
|
|
******************************************************************************************
|
|
*
*
|
|
*
Table RDRSTATS:
815 total number of processed records
*
|
|
*
================================================================================
*
|
|
*
*
|
|
*
815 Reader Statistics records would be deleted
*
|
|
*
*
|
|
******************************************************************************************
|
|
|
| RDRSTATS Cleanup ended with RC(0).
|
|
|
|PROGRAM B92CLARS (NEW
) ENDED WITH RC(0).
|
+-------------------------------------------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
433
Product batch utilities
B92CLEVT: Clearing events
B92CLEVT: Clearing events
Overview
Use the batch utility B92CLEVT to delete old event records from event
tables (EVTnn).
All events older than the specified number of days will be deleted from the
event tables. It is possible to specify a different value for each event table.
The batch utility B92CLEVT has been included into the weekly
housekeeping job B92WEEKL (see page 520).
You can start the batch utility B92CLEVT from the BETA92.CNTL or under
online option A.3.1, option W4 (see "Tailoring JCL for batch utilities
(Option A.3.1)" on page 175).
JCL
You can find JCL for this batch utility in the BETA92.CNTL in member
B92CLEVT and in member B92WEEKL.
+-----------------------------------------------------------------------+
|jobcard
|
|//CLEVT
EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92CLEVT,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DISP=SHR,DSN=BETA92.DB.DEF
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//SYSABEND DD SYSOUT=*
|
|//*
|
|//B92LOG
DD SYSOUT=*
|
|//OMSPRINT DD SYSOUT=*
|
|//*
|
|//SYSIN
DD *
|
| DAYS(5)
|
| EVT01_DAYS(10)
|
| MESSAGE(LONG)
|
|/*
|
+-----------------------------------------------------------------------+
Return codes
0
Program terminated normally.
4
No records found for deletion.
8
An error occurred.
16
Severe error occurred.
24
Started task unavailable during batch utility run.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
434
Product batch utilities
Analyze mode
(simulation)
B92CLEVT: Clearing events
Code TYPE=ANALYZE in the EXEC parm if you want to run the program
in analyze mode.
In analyze mode, B92CLEVT prints a report on the events that would be
deleted from the event tables, without actually deleting any events.
//CLEVT
//
//
SYSIN keywords
EXEC PGM=BST01RFF,REGION=0M,
PARM=('S=92,B01LST=00,B92LST=00',
'PGM=B92CLEVT,SIGNON=YES,TYPE=ANALYZE')
DAYS(n)
Only the event records that are older than n days
will be deleted. The event records of the last n days
will be preserved.
The specified value will be used for each event
table EVTnn, unless a table-specific value has
been coded using EVTnn_DAYS(n).
Allowed values: 0..9999
This parameter is required.
EVTnn_DAYS(n)
Like DAYS(n), but table-specific value for the
corresponding event table EVTnn.
MESSAGE(LONG|SHORT)
Controls which reports are written by B92CLEVT
If LONG, the following reports are printed:
•
A summary report (DD OMSPRINT), which
contains information on the number of event
records deleted from each event table.
•
A detailed report (DD OMSEVTnn) for each
event table, which lists the deleted events.
If SHORT, only the summary report is written to
DD OMSPRINT.
OMSPRINT
A summary report of the following type is written to DD OMSPRINT:
+-------------------------------------------------------------------------------------------------------------------+
|BETA 92 V7R2 EVENT STATUS CLEANUP UTILITY - DELETE RUN
date time
Page 0|
|-------------------------------------------------------------------------------------------------------------------|
|
|
|The following input parameters were processed:
|
|DAYS(360)
|
|MESSAGE(LONG)
|
|
|
|BETA 92 V7R2 EVENT STATUS CLEANUP UTILITY - DELETE RUN
date time
Page 1|
|-------------------------------------------------------------------------------------------------------------------|
|
|
|
EVENT TABLE
COUNT
ACTION
|
|
-------------------------------------------------------------------------------------------------------------- |
|
EVT00
8
records older than 13.11.2018 have been deleted (LAYOUT BETA_EVNT_RESULT.E)
|
|
EVT01
0
records older than 13.11.2018 have been deleted (LAYOUT BETA_EV01_RESULT.E)
|
|
EVT02
0
records older than 13.11.2018 have been deleted (LAYOUT BETA_EV02_RESULT.E)
|
|
============================================================================================================== |
|
Table EVTnn
8
Total records have been deleted
|
|
|
|
|
|Program B92CLEVT (ptflevel) ended with RC(0).
|
+-------------------------------------------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
435
Product batch utilities
OMSEVTnn
B92CLEVT: Clearing events
A detailed report containing the deleted events is written to DD
OMSEVTnn for each event table if the SYSIN parameter
MESSAGE(LONG) is coded.
DD OMSEVTnn is allocated dynamically (SYSOUT=*) if not present in the
JCL.
By default, B92CLEVT uses the English standard result layout of the
corresponding event table (Option A.1.1.3). Use LST parameter
B92_CLEVT_nn if you want to use a different layout for individual tables.
For example, if you want to use the German layouts:
B92_CLEVT_00 = BETA_EVNT_RESULT.G
B92_CLEVT_01 = BETA_EV01_RESULT.G
B92_CLEVT_02 = BETA_EV02_RESULT.G
You can also use your own result layouts. The language suffix (.E for
English, .G or .D for German) is required.
If the specified layout (for example USER_EV00_RESULT.G) does not
exist, B92CLEVT tries with the English suffix next and then with the
English standard result layout for this table (in the example:
BETA_EV00_RESULT.E). Layout substitution is logged in B92LOG.
Deletion is not affected.
The following example shows a report written to DD OMSEVTnn. The
report is based on the default layout (BETA_EVNT_RESULT.E) and
shows the events that were deleted from the event table EVT00.
+------------------------------------------------------------------------------------------------------------------------------+
|BETA 92 V7R2 EVENT STATUS CLEANUP UTILITY - DELETE RUN
date time
Page 1
|
|
|
|EVT00: All EVENTS older than 13.11.2018 are deleted.
LAYOUT: BETA_EVNT_RESULT.E
|
|
|
|
|
|Input Date ! Time ! Job/Rule ! Severity ! Status ! Event Text
! Job ID ! Sub Date ! ... |
|-----------!-------!----------!----------!--------!---------------------------------------------!----------!------------! ... |
|2018-11-13 ! 09:21 ! JYSL1171 ! E
! P
! JOB ON SYSTEM USR
IN ERROR - CC 0048 ! USR95313 ! 2018-11-13 ! ... |
|2018-11-13 ! 09:31 ! JYSL1171 ! E
! P
! JOB ON SYSTEM USR
IN ERROR - CC 0048 ! USR95324 ! 2018-11-13 ! ... |
|2018-11-13 ! 09:34 ! JYSL1171 ! E
! P
! JOB ON SYSTEM USR
IN ERROR - CC 0048 ! USR95346 ! 2018-11-13 ! ... |
|2018-11-13 ! 09:39 ! AZU01J01 ! E
! P
! JOB ON SYSTEM USR
IN ERROR - CC 0048 ! USR95357 ! 2018-11-13 ! ... |
|2018-11-13 ! 09:39 ! AZU06J01 ! E
! P
! JOB ON SYSTEM USR
IN ERROR - CC 0048 ! USR95373 ! 2018-11-13 ! ... |
|2018-11-13 ! 09:49 ! AZU03J01 ! E
! P
! JOB ON SYSTEM USR
IN ERROR - CC 0077 ! USR95384 ! 2018-11-13 ! ... |
|2018-11-13 ! 09:53 ! AZU03J01 ! E
! P
! JOB ON SYSTEM USR
IN ERROR - CC 0077 ! USR95417 ! 2018-11-13 ! ... |
|2018-11-13 ! 12:45 ! AZU03J01 ! E
! P
! JOB ON SYSTEM USR
IN ERROR - CC 0077 ! USR95444 ! 2018-11-13 ! ... |
+------------------------------------------------------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
436
Product batch utilities
B92CLLST: List cleanup
B92CLLST: List cleanup
Overview
The list cleanup utility B92CLLST checks the _beta log|z database for
online lists that are obsolete. All lists are deleted whose online retention (in
days or generations) has expired. B92CLLST does not delete lists that are
still waiting to be archived (status Arch=Pend).
The list cleanup utility is included in the B92DAILY job (see "B92DAILY:
Daily job" on page 442).
You can start the batch utility B92CLLST from the BETA92.CNTL or under
online option A.3.1, option D2 (see "Tailoring JCL for batch utilities (Option
A.3.1)" on page 175).
Queues and retention
periods
B92CLLST evaluates queues and retention periods, and deletes lists
accordingly.
A job can be on more than one queue. Queues are evaluated in this order:
1. Delete queue
2. Non-retain queue
3. History/Reload queue
4. Work queue
5. Error queue
6. Ready queue
7. Input queue
The global options parameter Use best matching Job Groups controls
which job group is used when determining the retention period of the
Work/Error/Ready/Input queue:
If YES The online retention period of the best matching job group is used
and controls deletion.
If NO
The online retention periods of all matching job groups are
evaluated, and the longest retention period controls deletion.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
437
Product batch utilities
JCL
B92CLLST: List cleanup
You can find JCL for this batch utility in the BETA92.CNTL in member
B92CLLST and in member B92DAILY.
+-----------------------------------------------------------------------+
|jobcard
|
|//CLEANUP EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92CLLST,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DISP=SHR,DSN=BETA92.DB.DEF
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//*
|
|//OMSPRINT DD SYSOUT=*
|
|//B92LOG
DD SYSOUT=*
|
|//*
|
+-----------------------------------------------------------------------+
Analyze mode
(simulation)
Code TYPE=ANALYZE in the EXEC parm if you want to run the program
in analyze mode. In this case, B92CLLST will print a report on all online
lists that would be deleted from the online spool without actually deleting
any lists.
//CLEANUP
//
//
Return codes
EXEC PGM=BST01RFF,REGION=0M,
PARM=('S=92,B01LST=xx,B92LST=xx',
'PGM=B92CLLST,SIGNON=YES,TYPE=ANALYZE')
0
Program terminated normally.
4
No lists were deleted.
8
An error occurred.
When a warning is issued, check whether the maximum online
retention period for generations has been specified in the field
Max. Online RETPD for Generations under option A.1. 2 "Job
Group" (see page 103) or under option A.S.3 "Global Options"
(see page 230).
Make sure that a value in days (1..9999) has been entered.
Note: The entry under option A.1.2 has precedence over the
entry under option A.S.3 when both fields are filled with values.
B92LOG
16
Severe error occurred.
24
Started task unavailable during batch utility run.
B92LOG logs settings that affect the processing of B92CLLST.
B92LOG is also used for logging error conditions that can occur during the
program run.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
438
Product batch utilities
OMSPRINT
B92CLLST: List cleanup
The report displays all lists that were deleted.
+--------------------------------------------------------------------------------------------------------------------------+
|BETA92 V7R2
- LIST CLEANUP UTILITY
05.01.2018 06:01:04 PAGE 1
|
|
|
|JOBNAME
JESID
DATE
TIME
GROUP
QUEUE
DDNAME
ONLINE
COUNT
CLASS SAVE ARCH ACTION STATUS
|
|-------- -------- ---------- -------- -------- ------- -------- -------- -------- ----- ---- ---- ------- --------------- |
|ZZ#93V61 J0034833 03.01.2018 06:02:48 BETA93
INPUT
JESJCLIN
2(D)
2(D)
P
YES YES DELETED
|
|
03.01.2018 06:02:48 BETA93
INPUT
JESMSGLG
2(D)
2(D)
P
YES YES DELETED
|
|
03.01.2018 06:02:48 BETA93
INPUT
JESJCL
2(D)
2(D)
P
YES YES DELETED
|
|
03.01.2018 06:02:48 BETA93
INPUT
JESYSMSG
2(D)
2(D)
P
YES YES DELETED
|
|
03.01.2018 06:02:48 BETA93
INPUT
SYSPRINT
2(D)
2(D)
P
YES YES DELETED
|
|
03.01.2018 06:02:48 BETA93
INPUT
SYSPRINT
2(D)
2(D)
P
YES YES DELETED
|
|
03.01.2018 06:02:48 BETA93
INPUT
SYSUT2
2(D)
2(D)
P
YES YES DELETED
|
|
03.01.2018 06:02:48 BETA93
INPUT
SYSPRINT
2(D)
2(D)
P
YES YES DELETED
|
|ZZ#93V62 J0034845 03.01.2018 06:02:48 BETA93
INPUT
JESJCLIN
2(D)
2(D)
P
YES YES DELETED
|
|
03.01.2018 06:02:48 BETA93
INPUT
JESMSGLG
2(D)
2(D)
P
YES YES DELETED
|
|
03.01.2018 06:02:48 BETA93
INPUT
JESJCL
2(D)
2(D)
P
YES YES DELETED
|
|
03.01.2018 06:02:48 BETA93
INPUT
JESYSMSG
2(D)
2(D)
P
YES YES DELETED
|
|
03.01.2018 06:02:48 BETA93
INPUT
SYSPRINT
2(D)
2(D)
P
YES YES DELETED
|
|
03.01.2018 06:02:48 BETA93
INPUT
SYSPRINT
2(D)
2(D)
P
YES YES DELETED
|
|
03.01.2018 06:02:48 BETA93
INPUT
SYSUT2
2(D)
2(D)
P
YES YES DELETED
|
|
03.01.2018 06:02:48 BETA93
INPUT
SYSPRINT
2(D)
2(D)
P
YES YES DELETED
|
|BETA88KK J0035585 04.01.2018 08:12:59 *DELETE* DELETE JESJCLIN
0(D)
1(D)
P
NO
DELETED JOB DELETED
|
|
04.01.2018 08:12:59 *DELETE* DELETE JESMSGLG
0(D)
1(D)
P
NO
DELETED JOB DELETED
|
|
04.01.2018 08:12:59 *DELETE* DELETE JESJCL
0(D)
1(D)
P
NO
DELETED JOB DELETED
|
|
04.01.2018 08:12:59 *DELETE* DELETE JESYSMSG
0(D)
1(D)
P
NO
DELETED JOB DELETED
|
|
04.01.2018 08:12:59 *DELETE* DELETE SYSTSPRT
0(D)
1(D)
P
NO
DELETED JOB DELETED
|
|...
|
|
|
|1699 JOBS WITH 13477 LISTS HAVE BEEN PROCESSED.
|
|
|
|2491 LISTS HAVE BEEN DELETED.
|
|
|
|CURRENT INSTALLATION IS SET TO 5 WORK DAYS PER WEEK
|
|
|
|JOB GROUP SELECTION WAS DONE DUE TO BEST MATCHING MASK.
|
|
|
|PROGRAM B92CLLST (NONE
) ENDED WITH RC(0).
|
+--------------------------------------------------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
439
Product batch utilities
B92CLLST: List cleanup
The Status column may contain the following information:
Status
Status
Description
LIST DELETED
The list has been deleted.
JOB DELETED
The last list of a job has been deleted.
NOKEEP LIST
The list attribute in the job information table has been
changed to NOSAVE. The list is deleted without
archiving.
LIST KEPT
The list attribute in the job information table has been
changed to SAVE. The list has to be archived before it
can be deleted.
NOKEEP JOB
The job attribute in the job information table has been
changed to NOSAVE. The job is deleted without
archiving.
JOB KEPT
The job attribute in the job information table has been
changed to SAVE. The job has to be archived before it
can be deleted.
OMS NOSAVE CARD
Because of the keyword NOSAVE the sysout lists of this
job are deleted without archiving.
OMS SAVE CARD
Because of the keyword SAVE the sysout lists of this
job have to be archived before they can be be deleted.
JCL ERROR
Job with JCL error. Whether jobs with JCL errors are
saved or not depends on the entry in the field Jobs with
JCL Init Errors.
CLASS REQUIRED
Job processed according to sysout class specifications.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
440
Product batch utilities
B92CLREO: List reorganization
B92CLREO: List reorganization
Overview
The list reorganization utility B92CLREO should run on a monthly basis to
ensure spool data integrity. B92CLREO reorganizes the lists on the spool
and frees blocks that contain obsolete data. The utility watches and
processes only spool data which are in the system for longer than 24
hours. This is to prevent intervention in the current _beta log|z processing.
JCL
You can find JCL for this batch utility in the BETA92.CNTL in member
B92CLREO.
+-------------------------------------------------------------------+
|jobcard
|
|//CLREORG EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92CLREO,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DISP=SHR,DSN=BETA92.DB.DEF
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//*
|
|//SYSPRINT DD SYSOUT=*
|
|//*
|
+-------------------------------------------------------------------+
Return codes
0
Program terminated normally.
8
An error occurred.
16
Severe error occurred.
24
Started task unavailable during batch utility run.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
441
Product batch utilities
B92DAILY: Daily job
B92DAILY: Daily job
Overview
B92DAILY includes several housekeeping batch utilities. B92DAILY should
be run on a daily basis.
For details, see the description of the individual each batch utilities.
Batch utilities
B92DAILY includes the following batch utilities:
1. List archive utility - B92ARPRI (see page 400)
2. List cleanup utility - B92CLLST (see page 437)
3. Job cleanup utility - B92ARSEC (see page 406)
You can start B92DAILY from the BETA92.CNTL or under online option
A.3.1, option D (see "Tailoring JCL for batch utilities (Option A.3.1)" on
page 175).
Note: The analyze mode to simulate the steps of execution is not available
for B92DAILY. However, you can first choose the analyze mode for each
of the batch utilities included in B92DAILY before starting the daily job
itself.
JCL
You can find the JCL in the BETA92.CNTL in member B92DAILY.
|+----------------------------------------------------------------------+
|jobcard
|
|//*********************************************************************|
|//*
PROCESS HISTORY MANAGER (BETA 92 - V7R2)
*|
|//*
(C) COPYRIGHT BETA SYSTEMS DCI SOFTWARE AG, 2022
*|
|//* ----------------------------------------------------------------- *|
|//*
DAILY MAINTENANCE
*|
|//*
- B92DAILY *|
|//*
(FILE TAILORING)
*|
|//* ----------------------------------------------------------------- *|
|//*
THIS JOB ARCHIVES DESIGNATED JOBS FROM THE BETA 92 SPOOL,
*|
|//*
DELETES EXPIRED LISTS FROM THE BETA 92 SPOOL AND
*|
|//*
DELETES EXPIRED JOBS FROM THE BETA 92 DATABASES.
*|
|//*********************************************************************|
|//*
|
|//*-------------------------------------------------------------------*|
|//* STEP 1: THE -LIST ARCHIVING UTILITY- ARCHIVES SYSOUT
*|
|//*
LISTS AND PERTINENT JOB INFORMATION FROM THE
*|
|//*
BETA 92 SPOOL.
*|
|//*-------------------------------------------------------------------*|
|//ARCH001 EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92ARPRI,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//*
|
(continued)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
442
Product batch utilities
B92DAILY: Daily job
(continued)
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DISP=SHR,DSN=BETA92.DB.DEF
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//SYSABEND DD SYSOUT=*
|
|//*
|
|//B92LOG
DD SYSOUT=*
|
|//OMSPRINT DD SYSOUT=*
|
|//OMSERROR DD SYSOUT=*
|
|//*
|
|//*-------------------------------------------------------------------*|
|//* STEP 2: THE -LIST CLEANUP UTILITY- DELETES ALL LISTS FROM THE *|
|//*
BETA 92 SPOOL WHOSE ONLINE RETENTION PERIOD HAS EXPIRED. *|
|//*-------------------------------------------------------------------*|
|//CLEANUP EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92CLLST,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//*
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DISP=SHR,DSN=BETA92.DB.DEF
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//SYSABEND DD SYSOUT=*
|
|//*
|
|//B92LOG
DD SYSOUT=*
|
|//OMSPRINT DD SYSOUT=*
|
|//*
|
|//*-------------------------------------------------------------------*|
|//* STEP 3: THE -JOB RECORD CLEANUP UTILITY- DELETES ALL JOB BASE *|
|//*
RECORDS FROM THE BETA 92 DATABASE WHOSE RETENTION PERIOD *|
|//*
HAS EXPIRED.
*|
|//*-------------------------------------------------------------------*|
|//ARCH002 EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92ARSEC,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//*
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DISP=SHR,DSN=BETA92.DB.DEF
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//SYSABEND DD SYSOUT=*
|
|//*
|
|//B92LOG
DD SYSOUT=*
|
|//OMSPRINT DD SYSOUT=*
|
|//*
|
+-----------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
443
Product batch utilities
B92DBVER: Database verification
B92DBVER: Database verification
Overview
The database verification utility B92DBVER checks for database changes,
for example, to verify the database level. This utility can be called online
from option A.S.2 using line command V, or it can be run as a batch job. It
is also started at STC start by the health checker function.
JCL
You can find JCL for this batch utility in the BETA92.CNTL in member
B92DBVER.
+----------------------------------------------------------------------+
|jobcard
|
|//B92DBVER EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92DBVER,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DISP=SHR,DSN=BETA92.DB.DEF
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//*
|
|//B92LOG
DD SYSOUT=*
|
|//SYSPRINT DD SYSOUT=*
|
|//OMSPRINT DD SYSOUT=*
|
|//*
|
+----------------------------------------------------------------------+
Return codes
0
All required database changes are present.
16
Some required database changes are missing, or insufficient
access authority.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
444
Product batch utilities
Report
Columns
B92DBVER: Database verification
+--------------------------------------------------------------------------------------------+
|BETA92 V7R1
- DATABASE VERIFICATION UTILITY
14.03.2018 14:40:08 PAGE 1 |
|VERIFY DATABASE CHANGES IN : BETA92.DB.DEF
|
|
|
|
DB-File/
|
|Table
Fld/Key Version PTF-No. BSA-Level Installed Installation Member
|
|-------- -------- ------- -------- ---------- --------- ----------------------------------- |
|GOR
GORDMASK 3.1.4 New
BSA9733-02 YES
|
|RBR
RBRAPOOL 3.1.4 New
BSA9733-02 YES
|
|
|
|ADR
ADRMED
3.2.1 New
BSA9733-03 YES
|
|APR
APRMED1
3.2.1 New
BSA9733-03 YES
|
|AVR
AVRMED
3.2.1 New
BSA9733-03 YES
|
|SOR
SORJSLIM 3.2.1 New
BSA9733-03 YES
|
|JBR
JBRKEY00 3.2.1 New
BSA9733-03 YES
|
|
|
| ...
|
|
|
|LGFCTL
LGFPLUS
6.1.0 New
BSA1461-00 YES
|
|LGFFLD
LGFFPOS
6.1.0 New
BSA1461-00 YES
|
|LGFREC
LGFRTYPE 6.1.0 New
BSA1461-00 YES
|
|LGFREP
LGFRPDTA 6.1.0 New
BSA1461-00 YES
|
|LGFSYS
LGFINDSN 6.1.0 New
BSA1461-00 YES
|
|LGFFLD
LGFPRCF1 6.1.0 POM6032 BSA1461-01 YES
|
|
|
|EVT02
EVT2APPL 6.2.0 New
BSA1461-03 YES
|
|LGFFLD
LGFFOFMT 6.2.0 New
BSA1461-03 YES
|
|
|
|JBR
JBRJOBC8 7.1.0 New
BSA1771-00 YES
|
|JGI
JGIJ1RPD 7.1.0 New
BSA1771-00 YES
|
|
|
|DATABASE IS UP TO DATE
|
|PROGRAM B92DBVER (NONE
) ENDED WITH RC(0)
|
+--------------------------------------------------------------------------------------------+
Column
Description
Table
Displays the table in which the field resides.
DB File/ Fld/Key
Displays the database file, the field or the key for which
the database change came into effect.
Vers.
Displays the version number with which the database
change came into effect.
PTF Number
The data changes can be carried out either by a PTF
change or a modification level. This field displays the
PTF number with which the database change came into
effect.
BSA-Level
Highest available BSA level at the time when the
database update was made available
Installed
YES
Database update has been installed
NO
Database update has not been installed
Installation Member
If updates are missing from the database:
Member name and library (SAMPLIB or CNTL) where
the database update was made available
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
445
Product batch utilities
B92FFIND: Find in online/offline logs
B92FFIND: Find in online/offline logs
Overview
B92FFIND can be used to search job logs and lists for specified character
strings. The batch utility B92FFIND processes online and archived logs
and sysout lists.
B92FFIND vs. B92SSRCH
_beta log|z provides two batch utilities for searching job logs and lists for
specific strings. Choose the appropriate batch utility according to the task
at hand:
B92FFIND
B92SSRCH
Max. two strings can be connected
using AND or OR. AND-connection can
be line-based or list-based.
More than two search expressions can
be connected using Boolean logic.
Evaluation is always based on the line.
Job logs and lists that are to be
searched can be online or offline.
Job logs and lists that are to be
searched must be online.
Only the first 133 columns of a hit line
are printed in the report. Three dots
( ... ) indicate that a hit line is longer.
The entire hit line is printed in the
report.
Other functions special to B92SSRCH:
•
Advanced search options such as
WORD, PREFIX, SUFFIX,
P (PICTURE), X (HEX)
•
User-defined reports (OMSPUNCH)
For more information on B92SSRCH, see "B92SSRCH: Advanced search
in online logs" on page 497.
Option 3 - Utilities
You can also use option 3.4 and 3.5 to generate JCL for the B92FFIND
batch utility.
For more information, see "Finding in online/offline lists (Option 3.4 B92FFIND)" in _beta log|z User Guide and "Finding in syslogs (Option 3.5
- B92FFIND)" in _beta log|z User Guide.
B92FFIND and automatic
reload
When searching the archives, you can automatically mark for reloading all
lists that contain hits. For more information, see "B92FFIND and automatic
reload requests" on page 453.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
446
Product batch utilities
B92FFIND and security
B92FFIND: Find in online/offline logs
By default, B92FFIND carries out the standard security checks at job or job
group level and at list level during the search. It is possible to reduce this
workload of the STC for authorized users who have to search a large
number of job logs.
If the LST parameter B92_ADM_LIST_ACCESS = YES has been coded,
B92FFIND checks at the beginning whether the user is authorized to use
B92FFIND (and B92SSRCH) on any list. Authorized users must have
READ access to the profile B92.ssid.ADL (function code 64 of the security
exit). If the user is authorized, B92FFIND will not carry out the standard
security checks during the search.
Processing steps
A search is carried out in two processing steps:
1. Processing the specified selection criteria to select the lists that are to
be searched
2. Processing the specified search arguments to find what you are
looking for in the selected lists
JCL
You can find JCL for this batch utility in the BETA92.CNTL in member
B92FFIND.
+-------------------------------------------------------------------+
|jobcard
|
|//SEARCH
EXEC PGM=BST01RFF,REGION=OM,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92FFIND,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DUMMY
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//*
|
|//B92LOG
DD SYSOUT=*
|
|//OMSPRINT DD SYSOUT=*
|
|//*
|
|//SYSIN
DD *
|
|BFIND
|
| SDATE(24.02.2010)
|
| STIME(00:00:00)
|
| PDATE(25.02.2010)
|
| PTIME(00:00:00)
|
| JOBNAME(ROD*)
|
| OPERATOR(OR)
|
| SLINE(0)
|
| PLINE(0)
|
| OPTIONS(FIRST)
|
| SCOPE(BOTH)
|
| MESSAGE(LONG)
|
| MIXEDMODE(NO)
|
| RELOAD(NO)
|
| STRING1('ROD')
|
|//*
|
|+------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
447
Product batch utilities
B92FFIND: Find in online/offline logs
Return codes
Syntax DD SYSIN
0
Program terminated normally.
4
No character string found.
8
An error occurred.
16
Severe error occurred.
24
Started task unavailable during utility run.
DD SYSIN contains the control parameters of the program.
There are two types of SYSIN parameters:
•
Parameters where the name of the parameter is coded without a value
Example: BFIND or BFSFD
•
Parameters where the name of the parameter is followed by a value,
which must be enclosed in parentheses
Example: MESSAGE(SHORT)
Some parameters have default values, which are used when the keyword
is not specified.
Code each parameter on a separate line. Except for the search string, the
names and values of all parameters must be coded in uppercase.
Comments can be added using the following syntax:
parametername(value)
SYSIN parameters
/* comment */
Parameter
Description
BFIND
instructs the batch find program to search lists
This parameter does not have a value. The
parameter has to be coded at initial position.
SDATE(start_date)
The beginning date for the job selection. This
parameter is required.
STIME(start_time)
The beginning time for the job selection. This
parameter is optional.
Default: 00:00:00
PDATE(end_date)
The ending date for the job selection. This
parameter is required.
PTIME(end_time)
The ending time for the job selection. This
parameter is optional.
Default: 23:59:59
JOBNAME(jobname)
Defines a full job name or a mask for the job
selection process. If JOBID has not been
entered this parameter is required.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
448
Product batch utilities
B92FFIND: Find in online/offline logs
Parameter
Description
JOBID(job_id)
Defines a full JES Job ID name or a mask for
the job selection process. If JOBNAME has not
been entered, this parameter is required.
NETID(net_id)
Specifies a job network name or mask
GROUP(groupname)
Specifies a job group name or mask
DDNAME1(name)
..
DDNAME4(name)
Limits the search to certain lists
MSGCLASS(class)
Masks can be used as well. The DD name
must be the name shown in the "Job
Information Table" for this list. This parameter
is optional. If you do not code it, all sysouts of
the job are searched.
Selects only jobs with this message class
This parameter is optional. If you do not code
it, all message classes processed by _beta
log|z are selected.
MESSAGE(LONG|SHORT)
This parameter decides the format in which the
search results will be presented in the log. In
any case, for both LONG and SHORT you get
the job name, job ID, step name, procstep
name, DD name and submit date and time of
the list containing the string(s). In addition, if
you have chosen Whole as operator, a
summary line tells which string(s) were found
in the list.
LONG
A detailed report of the search hits
is written. Each line of a list that
contains the searched string(s) will
be printed in the report.
SHORT
Only the number of search hits for
each list is indicated.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
449
Product batch utilities
B92FFIND: Find in online/offline logs
Parameter
Description
SLINE(n)
PLINE(n)
When you specify MESSAGE(LONG) to print a
detailed report, you can use the parameters
SLINE(n) and PLINE(n) to include lines
preceding and following the search hit in the
report.
Code SLINE(n) to include n preceding lines
Code PLINE(n) to include n following lines
Allowed values: 0..10
Default: 0
Markings in the report:
OPTIONS(ALL|FIRST|LAST)
--
Identifies lines preceding the search hit
>>
Identifies lines containing the search
hit
++
Identifies lines following the search hit
limits the number of hits that will be listed in
the report.
ALL
All search hits are listed for each list
(default).
FIRST Only the first search hit is listed for
each list.
LAST Only the last search hit is listed for
each list.
SCOPE(BOTH|ONL)
ONL
Searches only online lists.
BOTH Searches both online and offline lists
(default). In this case, a chronological
order of the searched jobs and the
search results according to submit time
cannot be guaranteed.
STRING1(string)
Specify the string you want to search for. This
parameter is required. The maximum length of
the string is 64 characters.
If the search string contains blanks, it must be
enclosed in quotation marks. It is possible to
search for a separate word within a line by
adding a leading and a trailing blank. This
method will not work if the word you are
looking for is separated from the surrounding
text by a comma, period, bracket, etc.
STRING2(string)
Specify the second string you want to search
for in the same way as STRING1. The
parameter is optional.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
450
Product batch utilities
B92FFIND: Find in online/offline logs
Parameter
Description
OPERATOR(OR|ANDL|WHOLE) The operator determines the logical relation
between the given search strings. It is ignored
if only one string is searched.
RELOAD(YES|NO)
OR
string1 or string2 or both must be
found in the list (default).
WHOLE
Both string1 and string2 must
occur in the same list.
ANDL
Both string1 and string2 must
occur in the same line.
YES will mark the found lists of a job for
reloading.
B92FFIND and automatic reload requests: To
ensure processing without accessing conflicts
between B92FFIND and the automatic reload,
see "B92FFIND and automatic reload
requests" on page 453.
The reload request will be displayed if you call
option 2 of the "Primary Selection Menu". The
job and all its lists will be reloaded when you
run the reload job B92RLOAD.
Enter NO if you do not want the lists to be
marked for reloading.
Default: NO
MIXEDMODE(YES|NO)
Enter YES to search for the string regarding
upper and lower case.
Default: NO
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
451
Product batch utilities
OMSPRINT
B92FFIND: Find in online/offline logs
OMSPRINT provides the following information on each hit list: job name,
job ID, step name, procstep name, DD name, and submit date and time.
The example includes the hit lines with preceding and following lines
(MESSAGE(LONG), SLINE(2), and PLINE(3)).
+------------------------------------------------------------------------------------------------------------+
| BETA92 V7R2
BATCH FIND UTILITY
|
|
|
| THE FOLLOWING INPUT PARAMETERS WERE PROCESSED:
|
|
|
| BFIND
|
| SDATE(31.07.07)
|
| STIME(08:00:00)
|
| PDATE(01.08.07)
|
| PTIME(11:00:00)
|
| JOBNAME(B92DAIL*)
|
| JOBID(*)
|
| NETID(*)
|
| GROUP(*)
|
| OPERATOR(OR)
|
| SLINE(2)
|
| PLINE(3)
|
| OPTIONS(ALL)
|
| SCOPE(BOTH)
|
| MESSAGE(LONG)
|
| RELOAD(NO)
|
| STRING1('DFHSM')
|
| STRING2('HSMPRT')
|
|
|
|
|
|JOBNAME(B92DAILY) JOBID(JOB01546) STEP(ARCH001) PROCSTEP(*) DDNAME(B92LOG) DATE(31.07.2007) TIME(08:00:04) |
|------------------------------------------------------------------------------------------------------------|
|--* 31.07.2007 08:00:04.46:
DAILY
90 TAPE 00002 00002 00003 00005
|
|--* 31.07.2007 08:00:04.46:
DEMO
366 TAPE 00003 00003 00005 00010
|
|>>* 31.07.2007 08:00:04.46:
DFHSM
90 TAPE 00005 00005 00005 00010
|
|++* 31.07.2007 08:00:04.46:
FLS
366 TAPE 00005 00005 00005 00010
|
|++* 31.07.2007 08:00:04.46:
FLS#LOG
366 TAPE 00005 00005 00005 00005
|
|++* 31.07.2007 08:00:04.46:
FLSDUMPS
366 TAPE 00005 00005 00005 00010
|
|--* 31.07.2007 08:00:04.47:
B*96*
BETA96
0x00 0x83b0
|
|--* 31.07.2007 08:00:04.47:
Q?55*
Q55
0x00 0x83b0
|
|>>* 31.07.2007 08:00:04.47:
*HSM*
DFHSM
0x00 0x8370
|
|++* 31.07.2007 08:00:04.47:
*BSA*
BSA
0x00 0x8370
|
|++* 31.07.2007 08:00:04.47:
*BSA*
BETA14
0x00 0x8370
|
|
|
|
|
|=========================================================================================================
|
|=
B 9 2 F F I N D :
S T A T I S T I C S
=
|
|=========================================================================================================
|
|= total number of processed jobs
:
2
=
|
|= total number of processed lists
:
20
=
|
|= number of found matches for STRING1
:
2
=
|
|= number of found matches for STRING2
:
0
=
|
|=========================================================================================================
|
|
|
| PROGRAM B92FFIND (POMnnnn) ENDED WITH RC(0)
|
|
|
+------------------------------------------------------------------------------------------------------------+
Error messages
Message
Meaning
UNABLE TO ACQUIRE
SUFFICIENT STORAGE
The internal storage used by the program is not
sufficient. Please inform _beta log|z support.
UNABLE TO ACQUIRE
SUFFICIENT STORAGE
FOR THE FUNCTION
The available storage is not sufficient to store all
necessary string information. Starting from this
message, all further strings are printed out.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
452
Product batch utilities
B92FFIND: Find in online/offline logs
B92FFIND and automatic reload requests
Overview
When searching the archives, B92FFIND can generate reload requests for
the lists that contain hits. These reload requests may lead to access
conflicts if the automatic reload function starts processing the requests
while B92FFIND is still searching the archive.
To avoid this type of conflict, it is possible to make B92FFIND collect
reload requests in a dataset. In a second step, you can upload these
reload requests with the help of B92ULOAD after B92FFIND has finished.
Recommended two-step
procedure for autoreload
If automatic reloading is enabled, we recommend that you collect reload
requests in a dataset when running B92FFIND with the SYSIN parameter
RELOAD(YES). To make B92FFIND do this, code an appropriate
DD statement for this dataset in the JCL:
DD name:
B92IRBR
DCB:
DCB=(RECFM=FB,LRECL=80)
If DD B92IRBR is present, all reload requests generated during the search
will be written to this dataset instead of to the database.
After B92FFIND has finished, run B92ULOAD to load the reload requests
of DD B92IRBR into the database table RBR.
Logging jobs to be
reloaded
The jobs that are to be reloaded are logged in DD OMSPRINT.
•
If DD B92IRBR is present, the following is output to OMSPRINT for
each job:
Job : job name
Jobid : job ID is written as an entry RBR into B92IRBR
At the end of the program a message informs you that the records of
DD B92IRBR must be uploaded into the database:
*** Please note , RBR records must be inserted ****
•
If DD B92IRBR is not present, all reload requests generated during
the search are written directly into the database table RBR.
Job : job name
Jobid : job ID is inserted in table RBR
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
453
Product batch utilities
JCL
B92FFIND: Find in online/offline logs
In the following JCL example, the SYSIN parameter RELOAD has been
set to YES, and the B92IRBR card has been coded. The job step with the
program B92ULOAD uploads the reload requests into the _beta log|z
database.
+-------------------------------------------------------------------+
|jobcard
|
|//SEARCH
EXEC PGM=BST01RFF,REGION=OM,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92FFIND,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DUMMY
|
|//*
|
|//B92IRBR DD DSN=USER.B92IRBR,DISP=(NEW,CATLG),
|
|//
SPACE=(TRK,(5)),
|
|//
DCB=(RECFM=FB,LRECL=80,BLKSIZE=80)
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//*
|
|//B92LOG
DD SYSOUT=*
|
|//OMSPRINT DD SYSOUT=*
|
|//*
|
|//SYSIN
DD *
|
|BFIND
|
| SDATE(24.02.2010)
|
| STIME(00:00:00)
|
| PDATE(25.02.2010)
|
| PTIME(00:00:00)
|
| JOBNAME(ROD*)
|
| OPERATOR(OR)
|
| SLINE(0)
|
| PLINE(0)
|
| OPTIONS(FIRST)
|
| SCOPE(BOTH)
|
| MESSAGE(LONG)
|
| MIXEDMODE(NO)
|
| RELOAD(YES)
|
| STRING1('ROD')
|
|//*
|
|//LOADRBR EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx,
|
|//
'PGM=B92ULOAD,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DUMMY
|
|//*
|
|//B92LOG
DD SYSOUT=*
|
|//OMSPRINT DD SYSOUT=*
|
|//SYSOUT
DD SYSOUT=*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//*
|
|//SYSIN
DD DISP=SHR,DSN=USER.B92IRBR
|
|//*
|
|+------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
454
Product batch utilities
B92FFIND: Find in online/offline logs
OMSPRINT if
DD B92IRBR is coded
+------------------------------------------------------------------------------------------------------------+
| BETA92 V7R2
BATCH FIND UTILITY
|
|
|
| THE FOLLOWING INPUT PARAMETERS WERE PROCESSED:
|
|
|
| BFIND
|
|
SDATE(19.4.2010)
|
|
STIME(00:00:00)
|
|
PDATE(19.4.2010)
|
|
PTIME(13:00:00)
|
|
JOBNAME(B48SAP)
|
|
JOBID(*)
|
|
NETID(*)
|
|
GROUP(*)
|
|
OPERATOR(OR)
|
|
OPTIONS(ALL)
|
|
SCOPE(BOTH)
|
|
MESSAGE(LONG)
|
|
RELOAD(YES)
|
|
MIXEDMODE(NO)
|
|
SLINE(0)
|
|
PLINE(0)
|
|
STRING1(*** ISPF transaction log ***)
|
|
|
| IN THE FOLLOWING LIST(S) STRING(S) WERE FOUND :
|
| JOBNAME(B48SAP) JOBID(J0052798) STEP(DELETE) PROCSTEP(*) DDNAME(ISPLOG) DATE(19.04.2010) TIME(10:24:11)
|
| ---------------------------------------------------------------------------------------------------------- |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|**
|
|** Job : B48SAP
Jobid : J0052798 is written as an entry RBR into B92IRBR
|
|**
|
| * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *|
|
|
| JOBNAME(B48SAP) JOBID(J0052805) STEP(DELETE) PROCSTEP(*) DDNAME(ISPLOG) DATE(19.04.2010) TIME(10:29:271)
|
| ---------------------------------------------------------------------------------------------------------- |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|
|
|...
|
|
|
|
=================================================================
|
|
=
B 9 2 F F I N D :
S T A T I S T I C S
=
|
|
=================================================================
|
|
= total number of processed jobs
:
6
=
|
|
= total number of processed lists
:
102
=
|
|
= number of found matches for STRING1
:
66
=
|
|
=================================================================
|
|
|
| PROGRAM B92FFIND (POMxxxx ) ENDED WITH RC(0).
|
|
|
|
*** Please note , RBR records must be inserted ****
|
|BOTTOM OF LIST -------------------------------------------------------------------------------------------- |
+------------------------------------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
455
Product batch utilities
B92FFIND: Find in online/offline logs
OMSPRINT if
DD B92IRBR not coded
+------------------------------------------------------------------------------------------------------------+
| BETA92 V7R2
BATCH FIND UTILITY
|
|
|
| THE FOLLOWING INPUT PARAMETERS WERE PROCESSED:
|
|
|
| BFIND
|
|
SDATE(19.4.2010)
|
|
STIME(00:00:00)
|
|
PDATE(19.4.2010)
|
|
PTIME(13:00:00)
|
|
JOBNAME(B48SAP)
|
|
JOBID(*)
|
|
NETID(*)
|
|
GROUP(*)
|
|
OPERATOR(OR)
|
|
OPTIONS(ALL)
|
|
SCOPE(BOTH)
|
|
MESSAGE(LONG)
|
|
RELOAD(YES)
|
|
MIXEDMODE(NO)
|
|
SLINE(0)
|
|
PLINE(0)
|
|
STRING1(*** ISPF transaction log ***)
|
|
|
| IN THE FOLLOWING LIST(S) STRING(S) WERE FOUND :
|
| JOBNAME(B48SAP) JOBID(J0052798) STEP(DELETE) PROCSTEP(*) DDNAME(ISPLOG) DATE(19.04.2010) TIME(10:24:11)
|
| ---------------------------------------------------------------------------------------------------------- |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|>>
Time
*** ISPF transaction log ***
Userid: AVMUSR Date: 10/04/19 Page: 1 |
|**
|
|** Job : B48SAP
Jobid : J0052798 is inserted in table RBR
|
|**
|
| * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
|
|...
|
+------------------------------------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
456
Product batch utilities
B92FFIND: Find in online/offline logs
B92FFIND for searching syslogs
Overview
B92FFIND includes special functions for searching the syslog if you are
using special syslog processing. These functions make syslog search very
fast because B92FFIND searches only those lists that fall within the
specified date and time range.
Syslog search is controlled via the SYSIN parameter BFSFD. Syslog
search can also be started online using option 3.5 (see "Finding in syslogs
(Option 3.5 - B92FFIND)" in _beta log|z User Guide.
Required:
Special syslog
processing
The syslog search of B92FFIND can only be used if the syslog has
undergone special processing.
Special syslog processing creates one job record (SYSLxxxx) for the
syslogs of one day. The DD name of each list shows the time of the first
record in this list (hh:mm:ss).
Special syslog processing is based on a set of scan definitions, which
must be active at the time when the syslog is read in. For more
information, see "z/OS syslog" in _beta log|z Installation and System
Guide.
Syslog under option 1
The following example of the "Job Select Table" shows the entries of a
syslog that has been processed by the syslog scan definitions:
PE92BR10
Command ===>
Row
1 of 7
Scroll ===> CSR
Job Select Table
S,? - Select a job
P,M - Print/Mail a job
I - Reset input queue
N - Change user notes
Sorted by Submit Date and Time D
Displayed Submit date and time
W - Toggle work queue
K - Toggle keep status
T - Toggle non-retain
X - Toggle nokeep status
B - Browse all sysouts
J - Browse JES sysouts
R - Reload offline lists E - Toggle error queue
Sel Jobname
Job ID
Date
Time
Status
Error
User
Jobgroup
? SYSLBETA STC00033 08/20/2007 00:00:00 R L
ABCD2
SYSLOG
SYSLBETA STC00033 08/19/2007 00:00:00 R L
AVSCHM2 SYSLOG
SYSLBETA STC00033 08/18/2007 00:00:00 R L
AVSCHM1 SYSLOG
SYSLBETA STC00033 08/17/2007 00:00:00 R L
ABCD1
SYSLOG
SYSLBETA STC00033 08/16/2007 00:00:00 R L
ABBB3
SYSLOG
SYSLBETA STC00033 08/15/2007 00:00:00 R O L
AVSCHM1 SYSLOG
SYSLBETA STC00033 08/14/2007 00:00:00 I O L
SYSLOG
******************************* BOTTOM OF DATA ********************************
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
457
Product batch utilities
B92FFIND: Find in online/offline logs
Line command B opens the complete syslog of one day in the Beta
Browser.
Entering S or ? displays the "Job Information Table":
PE92BR20
Command ===>
Row
1 of
8
Scroll ===> PAGE
Job Information Table for SYSLBETA (STC00033)
Submitted 08/20/2007 at 00:00:00 by +MASTER+
Started
08/20/2007 at 00:00:00
Ended
08/20/2007 at 01:11:04
Position:
N - Note
M - Message
S - Step
L - List
S - Browse a list
K - Toggle keep status
V - View a list
X - Toggle nokeep status
B - Browse spinned list A - Toggle re-archive
Sel Row DDName Stepname Procstep
1 01:11:03 BPXOINIT
2 08:02:24 BPXOINIT
3 09:23:59 BPXOINIT
4 09:42:51 BPXOINIT
5 10:25:05 BPXOINIT
6 11:04:30 BPXOINIT
7 11:27:21 BPXOINIT
8 11:42:41 BPXOINIT
Pages
35
36
35
36
36
35
36
35
Lines
10005
10005
10019
10001
10068
10004
10030
10070
X - Ext.Info
O - IWS
P,M - Print/Mail a list
R,U - Reload a list
T - Call Scan Test
Class Form
L
STD
L
STD
L
STD
L
STD
L
STD
L
STD
L
STD
L
STD
Arch Status
YES ONLINE
YES ONLINE
YES ONLINE
YES ONLINE
YES ONLINE
YES ONLINE
YES ONLINE
YES ONLINE
The DD name refers to the time this part of the syslog was read in to _beta
log|z as a separate list.
JCL
The following example shows the complete JCL for the syslog search with
B92FFIND:
+-------------------------------------------------------------------+
|jobcard
|
|//SEARCH
EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92FFIND,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DUMMY
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//OMSPRINT DD SYSOUT=*
|
|//*
|
|//SYSIN
DD *
|
| BFSFD
|
|
SDATE(TODAY)
|
|
STIME(07:00:00)
|
|
PDATE(TODAY)
|
|
PTIME(09:00:00)
|
|
JOBNAME(SYSL*)
|
|
JOBID(STC*)
|
|
OPERATOR(OR)
|
|
OPTIONS(ALL)
|
|
SCOPE(ONL)
|
|
MESSAGE(LONG)
|
|
RELOAD(NO)
|
|
SLINE(2)
|
|
PLINE(3)
|
|
MIXEDMODE(NO)
|
|
STRING1('SYSLOG')
|
|
STRING2('IEE042I')
|
+-------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
458
Product batch utilities
SYSIN parameters
B92FFIND: Find in online/offline logs
Parameter
Description
BFSFD
Instruction for B92FFIND syslog search
This parameter does not have a value. The
parameter has to be coded at initial position.
SDATE(start_date)
STIME(start_time)
PDATE(end_date)
PTIME(end_time)
Date/Time selection refers to the time when
the message was logged. All lines written
within the specified date/time range are
searched.
Otherwise like standard search with B92FFIND
(see page 448)
JOBNAME(SYSLxxxx)
Specific jobname of a syslog or a mask like
SYSL*. This parameter is required.
SCOPE (BOTH|ONL)
RELOAD (YES|NO)
Like standard search with B92FFIND (see
page 448)
STRING1(jes_id)
Corresponds to the Name Type field of
option 3.5
Use this required parameter to specify what to
search for. Enter an ID or a mask of the
following types: S (Started Task), T (TSO
User), or J (Job). This field is required. You
can enter up to 8 characters.
Note: The program searches for the specified
string at column 38 (two-digit year date mask)
or column 40 (four-digit year date mask).
STRING2(string)
Corresponds to the String field of option 3.5
Use this optional parameter to specify which
string is to be searched. You can specify up to
64 characters. If a search string contains
blanks, it must be enclosed in single quotation
marks.
Note: The program searches for the specified
string between column 57 (two-digit year date
mask) or column 59 (four-digit year date mask)
and the end of the line.
OPERATOR(ANDL)
Both strings must occur in the same line. Other
values are not meaningful for syslog search.
MIXEDMODE (YES|NO)
Like standard search with B92FFIND (see
page 448)
MESSAGE (LONG|SHORT)
SLINE(n)
PLINE(n)
Like standard search with B92FFIND (see
page 448)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
459
Product batch utilities
Return codes
OMSPRINT
B92FFIND: Find in online/offline logs
0
Program terminated normally.
4
No search string was found.
8
An error occurred.
16
Severe error occurred.
24
Started task unavailable during utility run.
You find Name Type (STRING1) between positions 38 and 45. You find
String (STRING2) beginning at position 57.
The report contains a list of the Syslog parameters that you defined.
+-----------------------------------------------------------------------------------------+
|BETA 92 V7R2
- BATCH FIND UTILITY
|
|
|
| THE FOLLOWING INPUT PARAMETER WERE PROCESSED:
|
| BFSFD
|
|
SDATE(TODAY)
|
|
STIME(07:00:00)
|
|
PDATE(TODAY)
|
|
PTIME(09:00:00)
|
|
JOBNAME(SYSL*)
|
|
JOBID(STC*)
|
|
OPERATOR(OR)
|
|
OPTIONS(ALL)
|
|
SCOPE(BOTH)
|
|
MESSAGE(LONG)
|
|
RELOAD(NO)
|
|
SLINE(2)
|
|
PLINE(3)
|
|
MIXEDMODE(NO)
|
|
STRING1(SYSLOG)
|
|
STRING2(IEE042I)
|
|
|
|
|
| IN THE FOLLOWING LIST(S) STRING(S) WERE FOUND :
|
| JOBNAME(SYSLBETA) JOBID(STC00022) STEP() PROCSTEP() DDNAME(06:48:25) DATE(17.0
|
| -----------------------------------------------------------------------------|
|--N 0000000 BETA
02137 06:48:25.22
00000290 IEF196I IEF237I JES2 A
|
|--N 0000000 BETA
02137 06:48:25.24
00000290 IEF196I IEF285I
+MAS
|
|>>X 0000000 BETA
02137 06:48:25.24 SYSLOG
00000000 IEE042I SYSTEM LOG DAT
|
|++N 4000000 BETA
02137 06:48:25.24
00000090 IEE043I A SYSTEM LOG D
|
|++N C000000 BETA
02137 06:48:25.89
00000081 #HASP309 INIT A1
INA
|
|++NC0000000 BETA
02137 06:48:25.90 INTERNAL 00000290 SE '06.48.25 JOB06036
|
| * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
|
| JOBNAME(SYSLBETA) JOBID(STC00022) STEP() PROCSTEP() DDNAME(07:00:17) DATE(17.0
|
| -----------------------------------------------------------------------------|
|--N 0000000 BETA
02137 07:00:17.21
00000290 IEF196I IEF237I JES2 A
|
|--N 0000000 BETA
02137 07:00:17.23
00000290 IEF196I IEF285I
+MAS
|
|>>X 0000000 BETA
02137 07:00:17.23 SYSLOG
00000000 IEE042I SYSTEM LOG DAT
|
|++N 4000000 BETA
02137 07:00:17.23
00000090 IEE043I A SYSTEM LOG D
|
|++N 0020000 BETA
02137 07:00:17.23 JOB06083 00000081 IGD104I QAB93.Q93P.DB.
|
|++S
DDNAME=SYS00005
|
|
|
|
=============================================================================
|
|
=
B 9 2 F F I N D :
S T A T I S T I C S
=
|
|
=============================================================================
|
|
= total number of processed jobs
:
1
=
|
|
= total number of processed lists
:
6
=
|
|
= number of found matches for STRING1
:
2
=
|
|
=============================================================================
|
|
|
| PROGRAM B92FFIND (POMnnnn) ENDED WITH RC(0).
|
|
|
+-----------------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
460
Product batch utilities
B92MICRO: Microfiche
B92MICRO: Microfiche
Overview
The batch utility B92MICRO prepares online output for microfiche
processing.
The microfiche batch utility B92MICRO can process jobs and sysout lists
from the _beta log|z spool. Further processing to transfer this data onto a
microfiche facility is possible.
The preparation of the list follows the standard format. A user exit is
available, which can be used to format output for various microfiche
devices.
JCL
You can find JCL for this batch utility in the BETA92.CNTL in member
B92MICRO.
The EXEC parm 'V2=SKIP' allows you to prevent (reloaded) V2 jobs from
being microfiched.
+-------------------------------------------------------------------+
|jobcard
|
|//MFICH
EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92PRINT,SIGNON=YES,V2=SKIP')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DUMMY
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//*
|
|//OMSPRINT DD SYSOUT=*
|
|//SYSUT2
DD SYSOUT=*
|
|//SYSIN
DD *
|
|MICRO
|
| UPDATE(YES)
|
| AUTOSEL(YES)
|
| PDATE(TODAY)
|
| JOBNAME(*)
|
| USER(ADMIN)
|
| MESSAGE(LONG)
|
| DATASET(BETA92.MICRO.OUT)
|
| DISPOSITION(SHR)
|
|/*
|
+-------------------------------------------------------------------+
Return codes
0
Program terminated normally.
4
No lists to be microfiched found.
8
An error occurred.
16
Severe error occurred.
24
Started task unavailable during batch utility run.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
461
Product batch utilities
Syntax DD SYSIN
B92MICRO: Microfiche
DD SYSIN contains the control parameters of the program.
There are two types of SYSIN parameters:
•
Parameters where the name of the parameter is coded without a value
Example: MICRO
•
Parameters where the name of the parameter is followed by a value,
which must be enclosed in parentheses
Example: MESSAGE(SHORT)
Some parameters have default values, which are used when the
parameter is not coded.
The names and values of all parameters must be coded in uppercase.
Comments can be added using the following syntax:
parametername(value)
SYSIN parameters
/* comment */
Parameter
Description
MICRO
Instructs the print program to Microfiche
This parameter does not have a value. The parameter
has to be coded at initial position.
USREXIT(YES|NO)
This parameter specifies the processing of the lists
through a user exit. If YES is coded, the user exit
B92UXFCH is called. This parameter is optional. The
default is NO.
_beta log|z user exits are described in the _beta log|z
Installation and System Guide.
Other selection
parameters
B92MICRO supports the same selection parameters as
B92PRINT. For a detailed description of all parameters,
see "B92PRINT: Printing/Mailing lists" on page 472.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
462
Product batch utilities
B92MICRO: Microfiche
OMSPRINT
+---------------------------------------------------------------------------------------------------------+
| BETA 92 V7R2 - BATCH PRINT UTILITY
08.03.2008 11:41:55 PAGE 1
|
|
|
| THE FOLLOWING INPUT PARAMETER WERE PROCESSED:
|
|
|
| MICRO
|
|
UPDATE(YES)
|
|
SDATE(07:03:08)
|
|
STIME(08:00:00)
|
|
PDATE(07:03:08)
|
|
PTIME(20:00:59)
|
|
JOBNAME(MITT*)
|
|
DDNAME1(*)
|
|
JOBID(*)
|
|
GROUP(*)
|
|
NETID(*)
|
|
SEPARATOR(NO)
|
|
MESSAGE(LONG)
|
|
CLASS(7)
|
|
AUTOSEL(YES)
|
| Beta92 V7R2 - BATCH PRINT UTILITY
08.03.2008 11:41:56 PAGE 2
|
|
|
| JOBNAME
JESID
DATE
TIME
DDNAME
STEP
PROCSTEP PAGES
LINES ACTION
|
| -------- -------- -------- -------- -------- -------- -------- ------- ---------------------------------|
| MITTW1
JOB08870 07.03.08 09:14:26 JESMSGLG JES2
*
2
113
LIST WAS MICROFICHED
|
| MITTW2
JOB08870 07.03.08 09:14:26 JESJCL
JES2
*
1
29
LIST WAS MICROFICHED
|
| MITTW3
JOB08870 07.03.08 09:14:26 JESYSMSG JES2
*
3
191
LIST WAS MICROFICHED
|
| MITTW4
JOB08871 07.03.08 09:14:26 JESMSGLG JES2
*
2
114
LIST WAS MICROFICHED
|
|
|
| 4 LIST(S) WERE PRINTED OR MICROFICHED.
|
|
|
| PROGRAM B92PRINT ENDED WITH RC(0).
|
+---------------------------------------------------------------------------------------------------------+
The report of the microfiche utility contains a list of the processing
parameters that you defined. If you specify parameter MESSAGE(LONG),
the report contains a complete table of the microfiched lists.
Action
The following messages can occur in the Action column:
Message
Meaning
JOB IS OFFLINE
The job logs and Sysout lists could not be
microfiched because the job information (or part of
the job information) is no longer online.
LIST WAS MICROFICHED The list was microfiched.
LIST IS OFFLINE
The list could not be microfiched in online mode
because the list is no longer online. Offline lists can
only be microfiched in batch mode.
MICROFICHE OF LIST
FAILED
An error occurred during microfiche.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
463
Product batch utilities
B92MUPDT: Mass update
B92MUPDT: Mass update
Overview
Batch utility B92MUPDT (mass update) enables you to move jobs or lists
from one queue to another. For example, you can move a job from the
ready queue to the work queue, or vice versa. Or you can move individual
lists of a job to the delete queue.
B92MUPDT can be used to update jobs while the corresponding job base
records are available. Lists can be updated while the corresponding job list
records are available. It is not possible to move offline lists to the delete
queue.
For more information on the queues, see "Logical queues" in _beta log|z
User Guide.
JCL
You can find JCL for this batch utility in the BETA92.CNTL in member
B92MUPD.
+-----------------------------------------------------------------------+
|jobcard
|
|//MUPDT
EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92MUPDT,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DUMMY
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//*
|
|//B92LOG
DD SYSOUT=*
|
|//OMSPRINT DD SYSOUT=*
|
|//*
|
|//SYSIN
DD *
|
| parameters
|
|/*
|
+-----------------------------------------------------------------------+
Return codes
0
Program terminated normally.
4
No jobs or lists have been processed.
8
An error occurred.
16
A severe error occurred.
24
Started task unavailable during batch utility run.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
464
Product batch utilities
Selection and processing
instructions
B92MUPDT: Mass update
Use DD SYSIN to code your instructions for the mass update utility
B92MUPDT.
Code each statement on a separate line. All instructions must be in
uppercase.
Use the following syntax if a statement serves simply as a selection
criterion: keyword(value) where keyword can be any of the selection
parameters listed below.
Use the following syntax if a statement serves as selection criterion and
triggers an update: keyword(value,function) where keyword can be
JOBNAME or DDNAME:
•
Code JOBNAME(jobname,function) together with your other
selection criteria if you want to move one or more jobs (i.e. update job
base records). SDATE(startdate) and EDATE(enddate) are
required. Other selection criteria are optional. function is explained
in "Updating jobs with B92MUPDT" on page 467.
•
Code DDNAME(ddname,function) together with your other selection
criteria if you want to move one or more lists (i.e. update job list
records). SDATE(startdate) and EDATE(enddate) plus
JOBNAME(jobname) or JOBID(jesid) are required. Other selection
criteria are optional. DDNAME(ddname,function) can be coded more
than once (max. 256). function is explained in "Updating lists with
B92MUPDT" on page 470.
Note: In one job step, B92MUPDT can update either job base records or
job list records, but not both. This means that you cannot code both
JOBNAME(jobname,function) and DDNAME(ddname,function) in the
same job step, but one of them must be coded.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
465
Product batch utilities
SYSIN parameters
B92MUPDT: Mass update
Parameter
Description
SDATE(startdate)
Start date for job selection (required)
STIME(starttime)
Start time for job selection (optional; default:
00:00:00)
PDATE(enddate)
End date for job selection (required)
PTIME(endtime)
End time for job selection (optional; default
23:59:59)
JOBNAME(jobname,function)
Code if you want to move one or more jobs:
jobname is a job name or a mask, which controls
job selection. function specifies which action is to
be carried out.
This parameter is explained in more detail in
"Updating jobs with B92MUPDT" on page 467.
DDNAME(ddname,function)
Code if you want to move one or more lists:
together with:
ddname is a list name or a mask, which controls
list selection. function specifies which action is to
be carried out.
JOBNAME(jobname)
-orJOBID(jesid)
This parameter is explained in more detail in
"Updating lists with B92MUPDT" on page 470.
JOBNAME(jobname) or JOBID(jesid) must be
coded for job selection. The lists will be selected
from the selected jobs.
NETID(netid)
JES3 net ID or _beta log|z net ID or mask
(optional)
QUEUE(queue)
_beta log|z logical queue (optional)
SYSID(sysid)
JES2 system ID (optional)
MSGCLASS(class)
JES message class (optional)
STEPS(stepname)
Step name or mask (optional)
SYSOUTCLASS(class)
Select lists of the specified SYSOUT class
Note: This optional parameter can only be used
when updating lists. The parameter is ignored
when updating jobs.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
466
Product batch utilities
B92MUPDT: Mass update
Updating jobs with B92MUPDT
JOBNAME parameter
Code JOBNAME(jobname,function) together with your other selection
criteria if you want move one or more jobs to a different queue where:
•
jobname is a job name or a mask, which controls job selection
•
function consists of the queue name in full or abbreviated form, an
equal sign, and the value YES or NO. function specifies which
action is to be carried out.
JOBNAME parameter
Description
Corresponding
line command
JOBNAME(jobname,INPUT=YES)
JOBNAME(jobname,I=YES)
Puts jobs on the input queue
I --> INPUT
JOBNAME(jobname,ERROR=YES)
JOBNAME(jobname,E=YES)
Puts jobs on the error queue
JOBNAME(jobname,ERROR=NO)
JOBNAME(jobname,E=NO)
Removes jobs from the error queue
JOBNAME(jobname,WORK=YES)
JOBNAME(jobname,W=YES)
Puts jobs on the work queue
JOBNAME(jobname,WORK=NO)
JOBNAME(jobname,W=NO)
Removes jobs from the work queue
JOBNAME(jobname,DELETE=YES)
JOBNAME(jobname,D=YES)
Puts jobs on the delete queue
JOBNAME(jobname,DELETE=NO)
JOBNAME(jobname,D=NO)
Removes jobs from the delete queue
JOBNAME(jobname,NON-RETAIN=YES)
JOBNAME(jobname,T=YES)
Puts jobs on the non-retain queue
JOBNAME(jobname,NON-RETAIN=NO)
JOBNAME(jobname,T=NO)
Removes jobs from the non-retain
queue
JOBNAME(jobname,KEEP=YES)
JOBNAME(jobname,K=YES)
Sets the status "must be archived" for K --> KEEP
jobs and their lists
JOBNAME(jobname,KEEP=NO)
JOBNAME(jobname,K=NO)
Removes the status "must be
archived" from jobs and their lists
JOBNAME(jobname,NOKEEP=YES)
JOBNAME(jobname,X=YES)
Sets the status "need not be archived" X --> NOKEEP
for jobs and their lists
JOBNAME(jobname,NOKEEP=NO)
JOBNAME(jobname,X=NO)
Removes the status "need not be
archived" from jobs and their lists
INPUT=NO is not possible. The job
can only be moved from the ready
queue to the input queue, but not vice
versa.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
E --> ERROR
W --> WORK
D --> DELETE
T --> NON-RETAIN
467
Product batch utilities
B92MUPDT: Mass update
Job owner (JBROWNER)
handling
The "Job Selection Table" displays the job owner in the User column.
The owner of a job is stored in the JBROWNER field. The update of this
field is handled differently, depending on whether the queue or status of
the job or list is changed via B92MUPDT or via the corresponding line
command.
•
When a change is carried out via B92MUPDT, the submitting user of
B92MUPDT becomes the owner of the modified job.
•
When a change is carried out online via the user interface, the update
of the JBROWNER field depends on the change of the queue or
status.
The following table contains a summary of the differences:
Reset to
INPUT queue
Update
ERROR queue
Update
WORK queue
Update online via line command
Update via B92MUPDT job
Line command I
JOBNAME(jobname,I=YES)
The JBROWNER field is blanked.
The job submitter becomes job owner.
Line command E (toggle)
JOBNAME(jobname,E=YES|NO)
Only the job owner can toggle the
error queue. The job owner remains
unchanged.
The job owner is not checked. The job
submitter becomes job owner.
Line command W (toggle)
JOBNAME(jobname,W=YES|NO)
The online user becomes the job
owner when putting a job on the work
queue.
The job submitter becomes job owner.
The JBROWNER field is blanked
when a job is removed from the work
queue.
Update
DELETE queue
Update
NONRETAIN
queue
Update
KEEP status
Update
NOKEEP status
Line command D (toggle)
JOBNAME(jobname,D=YES|NO)
The job owner remains unchanged.
The job submitter becomes job owner.
Line command T (toggle)
JOBNAME(jobname,T=YES|NO)
The job owner remains unchanged.
The job submitter becomes job owner.
Line command K (toggle)
JOBNAME(jobname,K=YES|NO)
The job owner remains unchanged.
The job submitter becomes job owner.
Line command X (toggle)
JOBNAME(jobname,X=YES|NO)
The job owner remains unchanged.
The job submitter becomes job owner.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
468
Product batch utilities
B92MUPDT: Mass update
Example with report
This example updates the KEEP status of jobs.
+------------------------------------------------------------------------------------------------------------------------------------+
|BETA 92 V7R2
- JOB MASS UPDATE UTILITY
2020-06-11 17:38:51 PAGE 1
|
|
|
|PROGRAM B92MUPDT (NONE
) STARTED.
|
|SDATE(TODAY)
|
|PDATE(TODAY)
|
|JOBNAME(REJ*,K=YES)
|
|
|
|
|
|BETA 92 V7R2
- JOB MASS UPDATE UTILITY
2020-06-11 17:38:51 PAGE 2
|
|
|
|JOBNAME
JES-ID
SUB DATE SUB TIME JOB-CL
STATUS RE/INP
ERR
WORK
DEL NON-RET NOKEEP KEEP USER
ACTION
|
|-------- -------- ---------- -------- ----------- -------------- ------- ------ ---- ------------------|
|REJCPAGE J0027488 2020-06-11 12:47:19
Y
ONLINE
READY
NO
NO
NO
NO
NO
YES
REINH1
updated |
|REJCPAGE J0027497 2020-06-11 12:50:27
Y
ONLINE
READY
NO
NO
NO
NO
NO
YES
REINH2
updated |
|REJAJOB J0027498 2020-06-11 12:50:28
Y
ONLINE
READY
NO
NO
NO
NO
NO
YES
REINH1
unchanged |
|REJCPAGE J0027712 2020-06-11 17:33:26
Y
ONLINE
INPUT
NO
NO
NO
NO
NO
YES
REINH1
updated |
|REJAJOB J0027713 2020-06-11 17:33:27
Y
ONLINE
INPUT
NO
NO
NO
NO
NO
YES
unchanged |
|
|
|5 JOB(S) MATCHED SELECTION CRITERIA.
|
|
|
|0 LIST(S) MATCHED SELECTION CRITERIA.
|
|
|
|PROGRAM B92MUPDT (NONE
) ENDED WITH RC(0).
|
+------------------------------------------------------------------------------------------------------------------------------------+
Action column
Action
Explanation
updated
The job has been moved.
unchanged
The job is already in the queue.
*not updated
It is not possible to move the job into the target queue. You
can find more details on this in B92LOG.
failed
There was an error in the update. The move to the target
queue was unsuccessful.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
469
Product batch utilities
B92MUPDT: Mass update
Updating lists with B92MUPDT
DDNAME parameter
Code DDNAME(ddname,function) together with your other selection
criteria if you want to move one or more lists to a different queue where:
•
ddname is a list name or a mask, which controls list selection from the
selected jobs
•
function consists of the queue name in full or abbreviated form, an
equal sign, and the value YES or NO. function specifies which
action is to be carried out.
DDNAME parameter
Description
Corresponding
line command
DDNAME(ddname,REARCH=YES)
DDNAME(ddname,R=YES)
Marks lists for rearchiving
A --> Rearchive
DDNAME(ddname,REARCH=NO)
DDNAME(ddname,R=NO)
Removes rearchive status from lists
DDNAME(ddname,NOKEEP=YES)
DDNAME(ddname,X=YES)
Sets status of lists to "need not be
archived"
DDNAME(ddname,NOKEEP=NO)
DDNAME(ddname,X=NO)
Removes the status "need not be
archived" from lists
DDNAME(ddname,KEEP=YES)
DDNAME(ddname,K=YES)
Sets the status of lists to "must be
archived"
DDNAME(ddname,KEEP=NO)
DDNAME(ddname,K=NO)
Removes the status "must be
archived" from lists
DDNAME(ddname,DELETE=YES)
DDNAME(ddname,D=YES)
Puts lists on the delete queue
DDNAME(ddname,DELETE=NO)
DDNAME(ddname,D=NO)
Removes lists from the delete queue
Note on delete queue
X --> Nokeep
K --> Keep
D --> Delete
The job and its lists must be ONLINE if you want to mark or unmark lists of
a job for deletion.
After a list has been placed on the DELETE queue, the list has the status
NO/ONLINE. After B92CLLST has processed the list, the status changes
to NO/OFFL.
Lists with status NO/OFFL are not archived. The job will be removed from
the job information table at the end of its online retention period.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
470
Product batch utilities
B92MUPDT: Mass update
Example with report
This example marks lists for rearchiving.
+------------------------------------------------------------------------------------------------------------------------------------+
|BETA 92 V7R2
- JOB MASS UPDATE UTILITY
2020-06-11 18:02:24 PAGE 1
|
|
|
|PROGRAM B92MUPDT (NONE
) STARTED.
|
|SDATE(TODAY)
|
|PDATE(TODAY)
|
|JOBNAME(REJ%SMF%)
|
|DDNAME(LGFLOG,R=YES)
|
|DDNAME(LGFPACK,R=YES)
|
|
|
|
|
|BETA 92 V7R2
- JOB MASS UPDATE UTILITY
2020-06-11 18:02:24 PAGE 2
|
|
|
|JOBNAME
JES-ID
SUB DATE SUB TIME JOB-CL
STATUS RE/INP
ERR
WORK
DEL NON-RET NOKEEP KEEP USER
ACTION
|
|-------- -------- ---------- -------- ----------- -------------- ------- ------ ---- ------------------|
|REJ§SMF1 J0027720 2020-06-11 17:59:32
Y
ONLINE
INPUT
NO
NO
NO
NO
NO
NO
|
|
DDNAME
STEPNAME PROCSTEP CLASS
PAGES LINES STATUS
REARCH
NOKEEP
KEEP
DELETE
ACTION
|
|
-------- --------- -------- ------ ----- ----- ----------- -------------------------------|
|
LGFLOG
SMFREP
Y
1
3 ONLINE
YES
NO
NO
NO
updated
|
|
LGFPACK
SMFREP
Y
1
4 ONLINE
YES
NO
NO
NO
updated
|
|
|
|
*****
JBR has been updated
: JBROWNER - REINH1
ACTION updated
**********************
|
|================================================================================================================================== |
|
|
|1 JOB(S) MATCHED SELECTION CRITERIA.
|
|
|
|2 LIST(S) MATCHED SELECTION CRITERIA.
|
|
|
|PROGRAM B92MUPDT (NONE
) ENDED WITH RC(0).
|
+------------------------------------------------------------------------------------------------------------------------------------+
Action column
Action
Explanation
updated
The list has been moved.
unchanged
The list is already in the queue.
*not updated
It is not possible to move the list into the target queue. You
can find more details on this in B92LOG.
failed
There was an error in the update. The move to the target
queue was unsuccessful.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
471
Product batch utilities
B92PRINT: Printing/Mailing lists
B92PRINT: Printing/Mailing lists
Overview
B92PRINT can be used to print/mail online and offline job logs and sysout
lists. Offline lists will be printed directly from the archive medium. Printing
offline lists requires that the entire job information is available online (see
"How long to keep job information online" on page 113).
Option 3 - Utilities
You can also use option 3.1 to generate and submit JCL for the B92PRINT
batch utility.
For more information, see "Printing/Mailing lists (Option 3.1 - B92PRINT)"
in _beta log|z User Guide.
JCL
The following shows sample JCL for B92PRINT:
+-------------------------------------------------------------------+
|jobcard
|
|//PRINT
EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx')
|
|//
'PGM=B92PRINT,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DUMMY
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//*
|
|//B92LOG
DD SYSOUT=*
|
|//OMSPRINT DD SYSOUT=*
|
|//*
|
|//SYSIN
DD *
|
|PRINT
|
| SDATE(08/01/08)
|
| STIME(00/00/00)
|
| PDATE(TODAY)
|
| PTIME(23:59:59)
|
| MASK(MM/DD/YY)
|
| AUTOSEL(NO)
|
| JOBNAME(*)
|
| JOBID(*)
|
| NETID(*)
|
| GROUP(*)
|
| MESSAGE(SHORT)
|
| STEPN(STEP01)
|
| PSTEPN(PROC01)
|
| QUEUE(INPUT)
|
| ERRORS(YES)
|
| MSGCLASS(Q)
|
| DDNAME1(SYSPRINT)
|
| USER(AV1SCHM)
|
| SYSCLASS(R)
|
| SEPARATOR(YES)
|
| SCOPE(ONL)
|
| CLASS(P)
|
|/*
|
+-------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
472
Product batch utilities
Return codes
Syntax DD SYSIN
B92PRINT: Printing/Mailing lists
0
Program terminated normally.
4
No lists to be printed found.
8
An error has occurred.
16
Severe error occurred.
24
Started task unavailable during utility run.
DD SYSIN contains the control parameters of the program.
There are two types of SYSIN parameters:
•
Parameters where the name of the parameter is coded without a value
Example: PRINT
•
Parameters where the name of the parameter must be followed by a
value, which must be enclosed in parentheses
Example: MESSAGE(SHORT)
Some parameters have default values, which are used when the
parameter is not specified.
Code each statement on a separate line. Parameter names and values
must be coded in uppercase.
Comments can be added using the following syntax:
parametername(value)
/* comment */
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
473
Product batch utilities
SYSIN parameters
(selection)
B92PRINT: Printing/Mailing lists
Parameter
Description
PRINT
Instructs the print program to print
This parameter is required, and it has to be
coded at initial position.
SMODE(SUBMIT|END)
SDATE(start_date)
Specifies whether the date/time values refer to
the submit date/time or to the end date/time
SUBMIT
Select jobs according to submit time
(default)
END
Select jobs according to end time
Specifies the start date for job selection
This parameter is optional if you have specified
AUTOSEL(YES). Otherwise, it is required.
STIME(start_time)
Specifies the start time for job selection
(optional)
Default: 00:00:00
PDATE(end_date)
Specifies the end date for job selection
(required)
PTIME(end_time)
Specifies the end time for job selection
(optional)
Default: 23:59:59
MASK(date_mask)
Specifies the date mask used with the
parameters SDATE and PDATE
This parameter is only required if you use a
British date format, for example:
SDATE(22/09/2013)
PDATE(23/09/2013)
MASK(DD/MM/YYYY)
AUTOSEL(YES|NO)
This parameter is used together with the
parameter UPDATE like this:
•
UPDATE(YES) causes the print utility to
mark the jobs that is has processed.
•
AUTOSEL(YES) causes the print utility to
select only jobs that have not been marked.
Default: NO
JOBNAME(jobname)
Specifies a job name or a mask
You must code JOBNAME(jobname),
JOBID(job_id), or both.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
474
Product batch utilities
B92PRINT: Printing/Mailing lists
Parameter
Description
JOBID(job_id)
Specifies a JES job ID or a mask
You must code JOBNAME(jobname),
JOBID(job_id), or both.
NETID(net_id)
Specifies a JES3 or _beta log|z net ID or a mask
(optional)
GROUP(group_name)
Selects jobs of a specific job group (optional)
STEPN(step_name)
Specify a step name or mask if you want to print
only the lists of that step.
PSTEPN(procstep_name)
Specify a procstep name or mask if you want to
print only the lists of that procstep.
QUEUE(queue)
Selects only jobs in a specific _beta log|z queue
(optional)
ERRORS(YES|NO)
YES limits the selection to jobs that came into
_beta log|z with errors. NO selects only jobs that
had no errors. Leave this parameter out to
select both kinds of jobs.
MSGCLASS
(message_class)
Selects jobs of a specific JES message class
(optional)
DDNAME1(name) DDNAME4(name)
Specify up to four DD names or masks if you
want to print only the lists with that DD name.
The DD name must match the name shown in
the "Job Information Table" for this list.
This parameter is optional. If you do not code it,
all sysouts of the job are printed.
Note: The LST parameter B92_REP_MISSING_
LIST_AS_WARNING determines program
behavior when printing selected lists (DDName):
SYSCLASS(sysout_class)
NO
The program skips jobs if the specified
list is not present. RC=0 if the program
has printed at least one list.
YES
The program prints a warning message
if the specified list is not present for a
job. RC=4 if the program has printed at
least one warning message.
Selects lists of a particular SYSOUT class
(optional)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
475
Product batch utilities
SYSIN parameters
(processing)
B92PRINT: Printing/Mailing lists
Parameter
Description
UPDATE(YES|NO)
This parameter is used together with the
parameter AUTOSEL like this:
UPDATE(YES) causes the print utility to mark
the jobs that is has processed.
AUTOSEL(YES) causes the print utility to select
only jobs that have not been marked.
Default: NO
SCOPE(ONL|BOTH)
ONL
prints only online lists (default)
BOTH prints both online and offline lists
MESSAGE(LONG|SHORT)
Specifies the amount of information that is
output to OMSPRINT
LONG
Verbose log
SHORT
Concise log
Default: LONG
SEPARATOR(YES|NO)
Specify SEPARATOR(YES) if you want blockletter separator pages between each job printed.
Default: NO
FPAGE(page_number)
Indicates the first page to be printed if you want
to print a range of pages
LPAGE(page_number)
Indicates the last page to be printed if you want
to print a range of pages
INCOMPLETE(YES|NO|ONLY) Determines the handling of lists that have not
(yet) been completely read in
YES
Incomplete lists are also printed
NO
Incomplete lists are not printed
ONLY Only incomplete lists are printed
Default: YES
Expect RC=4 when an incomplete list is printed.
OMSPRINT includes an appropriate message:
1 NUMBER OF INCOMPLETE LISTS
The user name, the job name, and the _beta
log|z system concerned are also issued.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
476
Product batch utilities
SYSIN parameters
(e-mail output)
B92PRINT: Printing/Mailing lists
Parameter
Description
MAILTO1(address(es))
MAILTO2(address(es))
E-mail address of the recipient where the mail is
to be sent; use a comma as a separator if you
specify more than one address.
MAILLINK(YES|NO)
MAILATTACH(YES|NO)
MAILZIP(YES|NO)
Controls how the information will be sent:
If MAILLINK(YES), a _beta view link is sent for
each job or list.
If MAILATTACH(YES), each job or list is sent as
an attachment in text format (*.txt).
If MAILZIP(YES), all jobs or lists are zipped into
one archive, which is sent as an attachment.
MAILFROM(address)
The e-mail address entered under option P.3 is
displayed here. The address is used as the
sender. This is to enable replies to the sender.
When the address has not been defined under
P.3, the default sender from the global option
A.S.3 (field Mail from) will be used instead.
MAILMODE(J|L)
Mail mode determines whether _beta log|z
generates one link or file per job (J) or per list
(L).
Note: If at least one list of a job contains binary
data, _beta log|z automatically switches to L
when sending zipped or unzipped attachments
because the encoding of each list needs to be
processed separately.
MAILSUBJ(text)
Subject line of your e-mail (max. 70 characters)
If you don't specify a subject, _beta log|z uses a
default subject line (B92PRINT of job(s)
(jobname_mask,jobid_mask,fromdate,fromtime
– todate,totime))
MAILJINFO(YES|NO)
Specify YES if you want _beta log|z to add the
following job information to your subject line:
(job name, job ID, submit date, submit time)
The default is MAILJINFO(YES).
MAILTEXT1(text) MAILTEXT9(text)
The mail text contains information on the e-mail.
MAILUCCSID(codepage)
Encoding of instructions in DD SYSIN
Specify a valid IBM codepage, for example,
IBM-280 or IBM-1144 for Italian.
Default: Encoding specified in Translation
Table field under option A.S.3
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
477
Product batch utilities
SYSIN parameters
(other output)
B92PRINT: Printing/Mailing lists
Parameter
Description
CLASS(sysout_class)
Defines the sysout class where the job logs
should be printed to
FILE(ddname)
If you don't code the parameters for a dataset or
a sysout class in DD SYSIN, B92PRINT defaults
to DD SYSUT2 for output. Code FILE(ddname)
if you want to print the job logs to the specified
DD name instead.
In order to print via SUBSYS, specify the name
of the SUBSYS DD statement. For an example,
see "Printing via SUBSYS" on page 481.
DATASET(dataset)
To print to a dataset, specify the fully qualified
name. The dataset name will be processed
exactly as it is given, without adding any
prefixes or suffixes.
You can print to a sequential or a PO dataset.
Add the member name in parentheses when
printing to a PO dataset.
DISPOSITION(SHR|MOD|OLD| Disposition of the dataset when printing to
NEW)
dataset
Specify SHR, MOD or OLD if you want to print
to an existing dataset.
Specify NEW if you want to print to new dataset.
Use the following parameters to define DCB
information for the new dataset:
SPACE(BLOCKS|CYLINDERS|TRACKS)
PRIMARY(n)
SECONDARY(n)
DIRBLOCKS(n)
RECFM(record_format)
LRECL(n)
BLKSIZE(n)
VOLSER(volser)
UNIT(unit_type)
STORCLAS(storage_class)
DATACLAS(data_class)
MGMTCLAS(management_class)
BURST(YES|NO)
Use the BURST parameter for sysout datasets
which are to be printed on the IBM 3800 printing
subsystem to burst the output into separate
sheets.
DESTINATION
(destination)
This parameter corresponds to the JCL
parameter DEST. Use it to assign the
destination of the sysout dataset.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
478
Product batch utilities
B92PRINT: Printing/Mailing lists
Parameter
Description
CHARS(character_
arrangement_tables)
Use the CHARS parameter for sysout datasets
which are to be printed on the IBM 3800 printing
subsystem. You may specify the names of up to
four character arrangement tables. If you code
more than one table, the tables must be
separated by commas.
USER(user_id)
identifies a TSO user ID at a node. It
corresponds to the JCL parameter
DEST=(dest,userid).
FCB(FCB name)
This parameter controls line feeds.
FORMS(form)
This parameter identifies the forms on which the
sysout dataset is to be printed. This parameter
corresponds to the JCL parameter
SYSOUT=(class,,form).
FLASH(overlay_name,copies)
You may use the FLASH parameter for sysout
datasets which are to be printed on the IBM
3800 printing subsystem. The FLASH parameter
identifies the forms overlay and optionally
specifies the number of copies on which the
forms overlay is to be printed.
WRITER
(writer_name)
This parameter identifies the OUTPUT
WRITERNAME which is the same as the
JCL parameter SYSOUT=(class,writer).
HOLD(YES|NO)
This parameter corresponds to the JCL
parameter HOLD. Code HOLD(YES) to hold the
sysout dataset on the JES spool. If you do not
specify this parameter, the sysout dataset will be
processed according to the standard settings of
the specified sysout class.
MODIFY
(module_name)
This parameter corresponds to the JCL
parameter MODIFY. Use it for sysout datasets
which are to be printed on the IBM 3800 printing
subsystem. Use it to specify a copy-modification
module and optionally a table reference
character (TRC). The table reference character
identifies a table name from the CHARS
parameter.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
479
Product batch utilities
B92PRINT: Printing/Mailing lists
Parameter
Description
UCS(character_set)
This parameter corresponds to the JCL
parameter UCS. It identifies the universal
character set image that JES is to use in printing
the sysout dataset. On an impact printer, this
parameter identifies a print train. On the IBM
3800 printing subsystem, UCS is identical to
CHARS.
OPTCD=J(YES|NO)
This parameter corresponds to the JCL
parameter OPTCD. It specifies whether or not
the list contains table reference characters
(TRC). TRC in the data stream identify which
character sets are to be used on the IBM 3800
printing subsystem.
Default: NO
DISTINFO1(distribution_
information)
This parameter specifies the first part of the
distribution information which is printed three
times at the top and at the bottom of each
separator page. You may specify a text of up to
40 characters.
DISTINFO2(distribution_
information)
This parameter specifies the second part of the
distribution information. You may specify a text
of up to 39 characters.
Printing/Mailing spinned
lists
Online spinned lists are sorted by name during printing/mailing.
Offline spinned lists are printed/mailed in the order in which they are read
from the archive dataset.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
480
Product batch utilities
Printing via SUBSYS
B92PRINT: Printing/Mailing lists
The print output produced by the B92PRINT utility can be printed via
SUBSYS or SUBSYS-STMT, for example, in order to print job logs via the
SUBSYS interface into _beta doc|z. Specify the name of the SUBSYS DD
statement via the SYSIN parameter FILE, as shown in the following
example:
+-------------------------------------------------------------------+
|...
|
|//B93SBSYS DD SUBSYS=(B93P,B92,PRINT),
|
|//
DCB=(RECFM=VB,LRECL=200,BLKSIZE=27998)
|
|//SYSIN
DD *
|
| PRINT
|
| SDATE(01.04.2008)
|
| PDATE(16.04.2008)
|
| JOBNAME(AVMJOB1)
|
| JOBID(J0007150)
|
| MESSAGE(LONG)
|
| FILE(B93SBSYS)
|
|/*
|
+-------------------------------------------------------------------+
The SYSIN print parameter FILE specifies the name of the SUBSYS DD
statement.
Note: Printing via SUBSYS can only be used when printing in batch mode.
OMSPRINT (mailing)
Following is a sample report when lists are sent as attachments:
+-----------------------------------------------------------------------------------------------------------------------+
| BETA92 V7R2
- BATCH PRINT UTILITY
14.04.2018 11:40:19 PAGE 1 |
| THE FOLLOWING INPUT PARAMETERS WERE PROCESSED:
|
| PRINT
|
| SDATE(01.04.18)
|
| STIME(00:00:00)
|
| PDATE(TODAY)
|
| PTIME(23:59:59)
|
| MASK(MM/DD/YY)
|
| AUTOSEL(NO)
|
| JOBNAME(*)
|
| JOBID(*)
|
| NETID(*)
|
| GROUP(*)
|
| MESSAGE(LONG)
|
| SCOPE(ONL)
|
| MAILTO1(avschm1@betasystems.com,avschm2@betasystems.com,)
|
| MAILTO2(avschm3@betasystems.com)
|
| MAILATTACH(YES)
|
| MAILZIP(NO)
|
| MAILMODE(J)
|
| MAILTEXT1(The lists have been sent for your information.)
|
| MAILTEXT2( )
|
| MAILTEXT3( )
|
| MAILTEXT4( )
|
| MAILTEXT5( )
|
| MAILTEXT6( )
|
|
|
| BETA92 V7R2
- BATCH PRINT UTILITY
14.04.2018 11:40:19 PAGE 2 |
| JOBNAME
JESID
SUB-DATE SUB-TIME END-DATE
END-TIME DDNAME
STEP
PROCSTEP PAGES LINES
ACTION
|
| -------- -------- ---------- -------- ---------- -------- -------- -------- -------- ------- ------- -----------------|
| AVMSAPRU SAAT2580 01.04.2018 00:00:00 01.04.2018 00:00:00 11:16:42
1
35
LIST SENT AS MAIL|
| AVMSAPRU SAAT2580 01.04.2018 00:00:00 01.04.2018 00:00:00 12:16:42
1
35
LIST SENT AS MAIL|
| AVMSAPRU SAAT2580 01.04.2018 00:00:00 01.04.2018 00:00:00 13:16:42
1
35
LIST SENT AS MAIL|
| AVMSAPRU SAAT2580 01.04.2018 00:00:00 01.04.2018 00:00:00 14:16:42
1
35
LIST SENT AS MAIL|
| AVMSAPRU SAAT2580 01.04.2018 00:00:00 01.04.2018 00:00:00 15:16:42
1
35
LIST SENT AS MAIL|
| ...
|
| 3432 LIST(S) SENT AS MAIL.
|
| PROGRAM B92PRINT (POMnnnn) ENDED WITH RC(0).
|
+-----------------------------------------------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
481
Product batch utilities
B92PRINT: Printing/Mailing lists
The column Action may contain the following messages:
Action
OMSPRINT (printing)
Message
Description
JOB IS OFFLINE
The job logs and Sysout lists cannot be mailed because
the job is no longer in the online spool.
LIST IS OFFLINE
The list could not be mailed because the list is not in the
online spool.
MAILING FAILED
An error occurred during mailing.
LIST SENT AS MAIL
The list has been sent as an e-mail.
The report of the print utility contains a list of the print parameters that you
defined.
+----------------------------------------------------------------------------+
| BETA92 V7R2 - BATCH PRINT UTILITY
09.04.18 11:41:55
PAGE 1 |
| THE FOLLOWING INPUT PARAMETERS WERE PROCESSED:
|
| PRINT
|
| SDATE(09.04.2018)
|
| STIME(12:07:00)
|
| PDATE(09.04.2018)
|
| PTIME(12:35:59)
|
| JOBNAME(MITT*)
|
| DDNAME1(*)
|
| JOBID(*)
|
| GROUP(*)
|
| NETID(*)
|
| SEPARATOR(NO)
|
| MESSAGE(LONG)
|
| CLASS(X)
|
| AUTOSEL(NO)
|
+----------------------------------------------------------------------------+
The verbose report contains a complete table of the printed lists.
+------------------------------------------------------------------------------------------------------+
| BETA92 V7R2 - BATCH PRINT UTILITY
09.04.2018
11:41:56
PAGE 2 |
|
|
|JOBNAME JESID SUB-DATE SUB-TIME END-DATE END-TIME DDNAME STEP PROCSTEP PAGES LINES ACTION
|
|------- ------ -------- -------- -------- -------- ------ ---- -------- ----- ----- -----------------|
|MITTW1 J0004333 09.04.18 12:07:17 09.04.08 12:17:17 JESJCL JES2
1
30 List was printed|
|MITTW2 J0004334 09.04.18 12:08:10 09.04.08 12:25:13 JESJCL JES2
1
29 List was printed|
|MITTW3 J0004335 09.04.18 12:18:25 09.04.08 12:19:13 JESJCL JES2
1
24 List was printed|
|MITTW4 J0004336 09.04.18 12:22:12 09.04.08 12:35:13 JESJCL JES2
1
25 List was printed|
|
|
|
|
|
|
|
4 LIST(S) WERE PRINTED OR MICROFISHED.
|
|
|
|
|
|
|
|
PROGRAM B92PRINT (POMnnnn) ENDED WITH RC(0)
|
|
|
|
|
+------------------------------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
482
Product batch utilities
Action
B92PRINT: Printing/Mailing lists
The following messages can occur in the Action column:
Message
Description
JOB IS OFFLINE
The job logs and Sysout lists cannot be printed
because the job information (or part of the job
information) is no longer online.
LIST WAS PRINTED
List has been printed.
LIST IS OFFLINE
The list could not be printed in online mode because
the list is no longer online. Offline lists can only be
printed in batch mode.
PRINT TO THIS DATA
SET IS NOT ALLOWED
RACF does not allow printing to this dataset.
LIST PRINT FAILED
An error occurred during printing.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
483
Product batch utilities
B92RDPS4: Reading z/OS Unix files into _beta log|z
B92RDPS4: Reading z/OS Unix files into _beta log|z
Overview
B92RDPS4 reads z/OS Unix into _beta log|z on the mainframe.
Files that have been read in by B92RDPS4 can be selected and displayed
under option O.1 ("Display File Rules ...").
Data transfer
B92RDPS4 uses the OSY reader for data transfer.
Batch job
STDIN
STDOUT
B92RDPS4
Directory
(USS side)
OSY Reader Protocol
Started task
B92RDPS2
BETA92.SPOOL
BETA92.DB
(JBR, ...)
JCL
B92RDPS4 is a standalone program, which does not use RFF.
You can find JCL in the BETA92.CNTL in member B92RDPS4.
+-----------------------------------------------------------------------+
|jobcard
|
|//RDPS4
EXEC PGM=B92RDPS4,REGION=0M,
|
|//
PARM=('STDIN_CP=IBM-273',
|
|//
'B92_RDR_SRC_CP=ISO8859-1',
|
|//
'B92_RDR_DEST_CP=IBM-273')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//*
|
|//STDOUT
DD SYSOUT=*
|
|//STDIN
DD *
|
| SSID(B92P)
|
| PATHNAME(/u/beta_public/samples/*)
|
| DISP(KEEP)
|
+-----------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
484
Product batch utilities
Return codes
EXEC parameters
B92RDPS4: Reading z/OS Unix files into _beta log|z
0
Program terminated normally.
8
An error occurred.
24
Started task unavailable during batch utility run.
Use the following EXEC parameters to specify the codepages used. All
parameters are optional.
Parameter
Default
Description
B92_RDR_SRC_CP
IBM-1047
Source codepage
This is the codepage of the file to be read in.
B92_RDR_DEST_CP
IBM-1141
Destination codepage
The file is converted to this codepage when
sent to _beta log|z.
STDIN_CP
IBM-1141
STDIN codepage
This is the codepage of STDIN, which
contains the input parameters for B92RDPS4.
Codepage conversion
The iconv utility is used for codepage conversion. You can display a
complete list of available codepages using the following command under
USS:
iconv -l
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
485
Product batch utilities
B92RDPS4: Reading z/OS Unix files into _beta log|z
STDIN parameters
The following parameters can be specified in DD STDIN.
Syntax: parametername(value)
Parameter
Description
SSID
_beta log|z subsystem that the files are to be read into
(required)
Allowed: Max. 4-digit subsystem ID
PATHNAME
Filepath to the USS files that are to be transferred
(required)
Allowed: Max. 255-digit string
You can use masks for file and directory names, or you
can use discrete names.
DISP
Controls whether files are deleted from USS after being
read into _beta log|z:
KEEP
Files are not deleted.
DELETE
Files are deleted.
Default: KEEP
Example output from
STDOUT
2009-04-24 08:20:11.05 OMS2354I # using the following code pages:
2009-04-24 08:20:11.06 OMS2354I #
B92_RDR_DEST_CP : IBM-1141
2009-04-24 08:20:11.06 OMS2354I #
B92_RDR_SRC_CP : IBM-1047
2009-04-24 08:20:11.06 OMS2354I #
STDIN_CP
: IBM-1141
2009-04-24 08:20:11.06 OMS2354I # processing the following parameters:
2009-04-24 08:20:11.06 OMS2354I #
SSID
= (92T2)
2009-04-24 08:20:11.06 OMS2354I #
DISP
= (KEEP)
2009-04-24 08:20:11.06 OMS2354I #
PATHNAME
= (/u/beta_public/samples/*)
2009-04-24 08:20:11.10 OMS2351I Transferring: (/u/beta_public/samples/c89code/aio_client.c)
2009-04-24 08:20:11.20 OMS2352I Transferring: DONE (36 bytes).
2009-04-24 08:20:11.10 OMS2351I Transferring: (/u/beta_public/samples/c89code/aio_client_stress.c)
2009-04-24 08:20:11.20 OMS2352I Transferring: DONE (199 bytes).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
486
Product batch utilities
Value mapping
B92RDPS4: Reading z/OS Unix files into _beta log|z
Files that have been read in can be viewed by means of option O.1
("Display File Rules ...").
Values are mapped to the fields of the file rule as shown in the following
table:
DB field
Description
Value
JBRMSGCL
Message class
: (colon)
RULENAME
Rule name
Job name of the batch job
SRCJOBN
Job name
Job name of the batch job
SRCJOBI
Job ID
Job ID of the batch job
SRCSUBD
Submit date
Current date
SRCSUBT
Submit time
Current time
AGENAME
Agent name
USSAGENT
OPERNAME
Operation name
USSOPER
SRCDDND
DD name
DDnnnn (serial number)
JBRSYSID
System ID
z/OS system ID under which the batch job ran
JBREHOST
Long host name
Host name of the machine where the batch job ran
JLREFILE
File name
Complete file name
JBRSUBID
Submit user ID
User ID of the TSO user that submitted the job
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
487
Product batch utilities
B92SENDL: Transferring lists to an EJM agent
B92SENDL: Transferring lists to an EJM agent
Overview
B92SENDL (data mover) transfers lists from _beta log|z to a _beta job|z
agent.
Lists that are to be transferred must be online.
It is possible to run several B92SENDL jobs at the same time.
Prerequisites
•
A definition of the receiving agent must exist in the _beta log|z
database (option A.2.6). The agent status must be active and online.
The name of the receiving agent has to be specified in the EXEC
parameter AGENT=agentname.
•
The receiving agent must have the necessary access rights to create
and modify directories and files.
B92SENDL ends with an error if the agent cannot write into at least
one file during the data transfer.
Agent-side handling
Target directories and target files are created on the agent side if they
don't exist.
Existing target files are overwritten by a new job.
Content is concatenated if multiple lists are transferred to a single target
file within the same job.
EBCDIC/ASCII
conversion
Text data is converted from EBCDIC to ASCII by the receiving agent on
the basis of the Ascii.tab conversion table in the agent bin directory.
Binary data is transferred without conversion. B92SENDL chooses binary
transfer based on the metadata of the list (binary flag in JLRE table, which
is set when reading in binary MIME type).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
488
Product batch utilities
JCL
B92SENDL: Transferring lists to an EJM agent
You can find JCL for this batch utility in the BETA92.CNTL in member
B92SENDL.
AGENT=agentname specifies the receiving agent. Replace agentname
with the name of your agent.
+-----------------------------------------------------------------------+
|jobcard
|
|//ANALYZE EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92SENDL,SIGNON=YES',
|
|//
'AGENT=agentname')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DUMMY
|
|//*
|
|//B92LOG
DD SYSOUT=*
|
|//OMSPRINT DD SYSOUT=*
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//*
|
|//SYSIN
DD *
|
|parameters
|
|/*
|
+-----------------------------------------------------------------------+
Return codes
0
Program terminated normally.
4
At least one SELECT block has found no data to be transferred.
Some data may have been transferred if several SELECT blocks
have been processed.
8
An error occurred (see B92LOG and OMSPRINT).
24
Started task unavailable during batch utility run.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
489
Product batch utilities
SYSIN syntax
B92SENDL: Transferring lists to an EJM agent
B92SENDL has the following SYSIN syntax:
SELECT comment
JOBNAME= jobname -OR- RULENAME= rulename
DDNAME=
ddname
STEPNAME= stepname
FROMDATE= fromdate
FROMTIME= fromtime
TODATE=
todate
TOTIME=
totime
REQUIRED= YES|NO
FILE=
filename -OR- FILENAME= filename
PATHNAME= pathname
HOSTNAME= hostname
...
The keyword SELECT marks the beginning of a transfer request block.
You can code up to 16 SELECT blocks in one job. The SELECT blocks
are processed sequentially. Each SELECT block can process up to 100
hits (lists).
Code a hyphen ( - ) as continuation sign if the value of a parameter is
continued on the next line. The continuation sign can be coded anywhere
at the end of the line. For example:
FILENAME=C:\Directory\Subdirectory1\Subdirectory2\
Subdirectory3\Targetfile.txt
Examples
-
Following is an example for a job.
//SYSIN
DD *
SELECT 0
JOBNAME = USRS*
DDNAME = JESMSGLG
FROMDATE= 09.07.2017
FROMTIME= 00:13
TODATE = 09.07.2017
TOTIME= 23:50
FILE=C:\targetdir\%JOBNAME..%DATE..TXT
/*
Following is an example for a rule:
//SYSIN
DD *
SELECT 0
RULENAME = USRF*
FROMDATE= 12.07.2017
FROMTIME= 00:20:00
TODATE = 12.07.2017
TOTIME = 20:10:00
FILE=C:\targetdir\%DATE..txt
/*
For information on variables, see "Variables in FILE/FILENAME" on
page 494.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
490
Product batch utilities
B92SENDL: Transferring lists to an EJM agent
SYSIN parameters
Parameter
Opt./Req.
Description
DDNAME
Optional
Selects lists according to DD name (max. 8 characters)
You can use wildcards (*, ?, %).
ERRORS
FILE or
FILENAME
Optional
Required
Limits the selection to jobs with/without errors:
YES
Selects only jobs that are in error.
NO
Selects only jobs that have not been assigned to the error queue.
Fully qualified name of the target directory and the target file on the agent
side (max. length: 256 characters)
You can use variables to create unique names (see "Variables in
FILE/FILENAME" on page 494).
FROMDATE
Required
Start date of the selection
Selection is based on submit time. Use the date format as defined in the
global options (option A.S.3).
FROMTIME
Required
Start time of the selection (see also TIMERANGE)
Selection is based on submit time.
The following time formats can be used: HH, HH:MM and HH:MM:SS.
HOSTNAME
Optional
Host name (max. 256 characters; wildcards are allowed)
Example: To select entries with the following host name:
10.56.79.18:10210
You can enter one of the following:
HOSTNAME=*10210
HOSTNAME= *10.56.79*
HOSTNAME= 10.56.79.18:10210
JOBID
Optional
Job ID or a mask
JOBNAME
Required if Job name or mask (max. 8 characters)
RULENAME
Note: The parameters JOBNAME and RULENAME are mutually
is not coded
exclusive. Either JOBNAME or RULENAME must be coded, but not both.
You can use wildcards (*, ?, %).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
491
Product batch utilities
B92SENDL: Transferring lists to an EJM agent
Parameter
Opt./Req.
Description
PATHNAME
Optional
Selects list according to directory/file name (max. 1024 characters)
Wildcards can be used.
Example: To select entries with the following path name:
C:\b92.test2.new\winjob.v4r4.txt
You can enter one of the following:
PATHNAME=*v4r4.txt
PATHNAME=*winjob.v4r4.txt
PATHNAME=C:\b92.test2.new\winjob.*
PATHNAME=C:\b92.test2.new\winjob.v4r4.txt
REQUIRED
Optional
Defines whether a list must be available
If YES: B92SENDL terminates if a SELECT block does not have any hits.
If NO: B92SENDL writes a warning message and continues with the next
SELECT block if a SELECT block does not have any hits.
Values: YES | NO Default: NO
RULENAME
Required if Rule name (max. 8 characters)
JOBNAME Note: The parameters JOBNAME and RULENAME are mutually
is not coded exclusive. Either JOBNAME or RULENAME must be coded, but not both.
You can use wildcards (*, ?, %).
SKIPICL
Optional
Skip lists that are marked as incomplete
Values: YES | NO Default: YES
STEPNAME
Optional
Selects lists according to step name (max. 8 characters)
You can use wildcards (*, ?, %).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
492
Product batch utilities
B92SENDL: Transferring lists to an EJM agent
Parameter
Opt./Req.
Description
TIMERANGE
Optional
If NO, FROMTIME specifies the start time on the start date, and TOTIME
specifies the end time on the end date; B92SENDL selects jobs/rules
between these two points of time.
If YES, FROMTIME specifies the start time on each day between
start/end date, and TOTIME specifies the end time on each day between
start/end date; B92SENDL selects jobs/rules that fall within this timeslice
on each day.
Values: YES | NO Default: NO
Example:
FROMDATE
TODATE
FROMTIME
TOTIME
= 15.04.2017
= 17.04.2017
= 10:00
= 10:59
If TIMERANGE = NO, the selected date/time range will be as follows:
15.04.2017 10:00 to end of day
16.04.2017 entire day
17.04.2017 start of day to 10:59
If TIMERANGE = YES, the selected date/time range will be as follows:
15.04.2017 10:00 to 10:59
16.04.2017 10:00 to 10:59
17.04.2017 10:00 to 10:59
TODATE
Optional
End date of the selection
Selection is based on submit time. Use the date format as defined in the
global options (option A.S.3).
Default: TODAY
TOTIME
Optional
End time of the selection (see also TIMERANGE)
The following time formats can be used: HH, HH:MM and HH:MM:SS.
Default: Current time of day
USETEMP
Optional
If YES, files are transferred to a temporary agent directory first, and then
moved to the specified target directory at the end of the B92SENDL job.
The temporary directory is created under the B92\session\bql directory.
Each B92SENDL jobs uses a separate temporary agent directory. In case
of an error, B92SENDL deletes the temporary agent directory with the
files transferred so far if the connection to the agent still exists.
Values: YES | NO Default: YES
WRITEMETA
Optional
Metadata of each job is written to a file called #META#.TXT in the target
directory; data is appended if this file is already present.
Values: YES | NO Default: NO
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
493
Product batch utilities
B92SENDL: Transferring lists to an EJM agent
Variables in
FILE/FILENAME
The following variables can be used in the value of the FILE or FILENAME
parameter:
Variable
Description
%DDNAME.
DD name
%EXTENSION.
Original extension of the file that was read in
If not available, B92SENDL uses bin for binary files and txt
for text files.
%FILENAME.
%FILENAME. is equivalent to
%DDNAME..%STEPNAME..%EXTENSION.
%JOBID.
JES ID of the job
%JOBNAME.
Name of the job
%RULENAME.
Name of the rule
%STEPNAME.
Step name
%DATE.
Submit date in the format YYYYMMDD
%TIME.
Submit time in the format HHMMSShh
%YYYY.
Four-digit year of submit date
%MM.
Two-digit month of submit date
%DD.
Two-digit day of submit date
%hh.
Two-digit hour of submit time
%mm.
Two-digit minute of submit time
%ss.
Two-digit second of submit time
%EYYYY.
Four-digit year of end date
%EMM.
Two-digit month of end date
%EDD.
Two-digit day of end date
%ehh.
Two-digit hour of end time
%emm.
Two-digit minute of end time
%ess.
Two-digit second of end time
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
494
Product batch utilities
B92SENDL: Transferring lists to an EJM agent
Notes
•
Variables must start with a percent sign ( % ) and end with a
period ( . ).
•
Variables are case-sensitive.
•
B92SENDL ends with an error if the start or end sign is missing or if an
invalid variable is coded.
•
During variable substitution, B92SENDL replaces colon ( : ), forward
slash ( / ), and backward slash ( \ ) with underscore ( _ ) to prevent the
generation of illegal filenames.
•
Code two percent signs ( %% ) in the value of the FILE or FILENAME
parameter if you want to use a percent sign ( % ) in the name of the
target file or directory.
Example of a file name
OMSPRINT
Coded value:
/<targetdir>/%JOBNAME..%DDNAME..%STEPNAME..%DATE..%TIME.
Possible result:
/<targetdir>/USRJOB.MYDD.MYSTEP.20170503.07054300
The following is an example of OMSPRINT:
+---------------------------------------------------------------------------------------------+
| BETA92 V7R2
- DATA MOVER (B92SENDL)
15.06.17 14:38:17 PAGE 1
|
|---------------------------------------------------------------------------------------------|
|THE FOLLOWING INPUT PARAMETERS WERE PROCESSED:
|
|
|
| SELECT VERARB 1
|
| JOBNAME= USR*
|
| DDNAME= *
|
| STEPNAME = ANALYZE
|
| FROMDATE= 14.06.2017
|
| FROMTIME= 09:00
|
| TODATE = 14.06.2017
|
| TOTIME = 12:01:00
|
| REQUIRED = NO
|
| FILE=C:/targetdir/%%STEPNAME..%%DDNAME..%%JOBNAME..%DATE..%TIME.
|
|
|
|
|
| BETA92 V7R2
- DATA MOVER (B92SENDL)
15.06.17 14:38:17 PAGE 2
|
| --------------------------------------------------------------------------------------------|
| JOBNAME JESID
SUB-DATE
SUB-TIME STEPN
PROCSTEP DDNAME PAGES LINES TRANSFERRED TO|
| ------- ------- ---------------- ------- -------- ------ ------ ------ --------------|
| USRSEND2 J0019920 2017-06-14 12:22:22 ANALYZE
B92LOG
1
30
C:/targetdir/.|
| USRSEND2 J0019920 2017-06-14 12:22:22 ANALYZE
OMSPRINT 2
40
C:/targetdir/.|
| USRSEND3 J0019921 2017-06-14 12:22:22 ANALYZE
B92LOG
1
50
C:/targetdir/.|
| USRSEND3 J0019921 2017-06-14 12:22:22 ANALYZE
OMSPRINT 2
10
C:/targetdir/.|
| USRSNDAI J0019582 2017-06-14 10:48:43 ANALYZE
B92LOG
1
8
C:/targetdir/.|
|
|
|
|
|
|
|
===================================================================
|
|
=
B 9 2 S E N D L :
S T A T I S T I C S
=
|
|
===================================================================
|
|
= total number of transferred files :
5
=
|
|
= total number of processed jobs
:
53
=
|
|
= total number of processed lists
:
53
=
|
|
= total number of incomplete lists
:
0
=
|
|
===================================================================
|
|
|
|
|
| Program B92SENDL (NONE
) ended with RC(0).
|
+---------------------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
495
Product batch utilities
#META#.TXT
B92SENDL: Transferring lists to an EJM agent
The following is an example of a #META#.TXT file (WRITEMETA=YES):
+------------------------------------------------------------------------------+
|SRCJOBN=REJ#§DMP
|
|SRCJOBI=J0029932
|
|SRCSUBD=26.04.2017
|
|SRCSUBT=10:14:49:82
|
|SRCSTRTD=26.04.2017
|
|SRCSTRTT=10:14:49
|
|SRCENDD=26.04.2017
|
|SRCENDT=10:14:50
|
|JBRRINDT=26.04.2017
|
|JBRRINTM=10:14:50
|
|JBRMSGCL=Y
|
|JBRNETID=
|
|JBRERRTX=
|
|JBROWNER=
|
|SRCJOBCL=A
|
|JBRSYSID=BETA
|
|JBRSUBID=REINH1
|
+------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
496
Product batch utilities
B92SSRCH: Advanced search in online logs
B92SSRCH: Advanced search in online logs
Overview
You can use the _beta log|z spool search utility B92SSRCH to search all
job logs and logs in the online spool. You can find JCL in the
BETA92.CNTL in member B92SSRCH.
B92SSRCH vs. B92FFIND
_beta log|z provides two batch utilities for searching job logs and lists for
specific strings. Choose the appropriate batch utility according to the task
at hand:
B92SSRCH
B92FFIND
More than two search expressions can
be connected using Boolean logic.
Evaluation is always based on the line.
Max. two strings can be connected
using AND or OR. AND-connection can
be line-based or list-based.
Job logs and lists that are to be
searched must be online.
Job logs and lists that are to be
searched can be online or offline.
The entire hit line is printed in the
report.
Only the first 133 columns of a hit line
are printed in the report. Three dots
( ... ) indicate that a hit line is longer.
Other functions special to B92SSRCH:
•
Advanced search options such as
WORD, PREFIX, SUFFIX,
P (PICTURE), X (HEX)
•
User-defined reports (OMSPUNCH)
For more information on B92FFIND, see "B92FFIND: Find in online/offline
logs" on page 446.
Option 3 - Utilities
You can also use option 3.6 to generate JCL for the B92SSRCH batch
utility.
For more information, see "Advanced search in online lists (Option 3.6 B92SSRCH)" in _beta log|z User Guide.
B92SSRCH and security
By default, B92SSRCH carries out the standard security checks at job or
job group level and at list level during the search. It is possible to reduce
this workload of the STC for authorized users who have to search a large
number of job logs.
If the LST parameter B92_ADM_LIST_ACCESS = YES has been coded,
B92SSRCH checks at the beginning whether the user is authorized to use
B92SSRCH (and B92FFIND) on any list. Authorized users must have
READ access to the profile B92.ssid.ADL (function code 64 of the security
exit). If the user is authorized, B92SSRCH will not carry out the standard
security checks during the search.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
497
Product batch utilities
JCL
B92SSRCH: Advanced search in online logs
The following example shows the JCL for B92SSRCH:
+-------------------------------------------------------------------+
|jobcard
|
|//SEARCH
EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92SSRCH,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DUMMY
|
|//*
|
|//B92LOG
DD SYSOUT=*
|
|//OMSPRINT DD SYSOUT=*
|
|//OMSOUT
DD SYSOUT=*
|
|//OMSPUNCH DD SYSOUT=*
|
|//SYSIN
DD *
|
|
SEARCH('IEF' 18 25 PREFIX)
|
|
SDATE(YESTERDAY)
|
|
PDATE(TODAY)
|
|
JOBNAME(MYJOB*)
|
|
DDNAME(JESMSGLG)
|
|/*
|
+-------------------------------------------------------------------+
Return codes
0
Program terminated normally.
1
The job/list selection has returned one or more entries, but the list
search has ended with "No data found". This return code can be
changed using the NODATARC parameter.
4
The job/list selection has ended with "No data found".
8
DD statement missing or syntax error in DD SYSIN.
16
Severe error occurred.
24
Started task unavailable during utility run.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
498
Product batch utilities
SYSIN syntax
B92SSRCH: Advanced search in online logs
Each SYSIN parameter is coded as a name-value pair. The value is
enclosed in parentheses.
The following syntax rules apply:
•
Each SYSIN parameter must be coded on a separate line.
(Exceptions: The SEARCH parameter and the PUNCH parameter
can be continued on subsequent lines.)
•
The opening parenthesis must be placed directly after the parameter
name without any intervening blanks. Leading and trailing blanks are
allowed within the parentheses that contain the value.
These statements are valid:
parametername(value)
parametername( value )
These statements are not valid:
parametername (value)
parametername ( value )
•
Initial asterisk ( * ) marks the entire line as a comment. If you want to
add a comment on the same line following a parameter, you must
code at least one blank between the closing parenthesis and the
asterisk.
In this example, only the parameter on the second line will be
processed:
*parametername(value)
parametername(value) * comment
Processing steps
A search is carried out in the following steps:
1. Processing the specified selection criteria to select the lists that are to
be searched
See "Selection parameters" on page 500 for a description of available
parameters.
2. Processing the specified search arguments to find what you are
looking for in the selected lists
See "Search expressions" on page 503 for a description of available
parameters.
The reports that are output by B92SSRCH can also be controlled by a set
of parameters:
•
For information on how to control available reports, see "B92SSRCH
reports" on page 507.
•
For information on defining your own reports, see "Customer-specific
report (OMSPUNCH)" on page 512.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
499
Product batch utilities
B92SSRCH: Advanced search in online logs
Selection parameters
Overview
In the first step, B92SSRCH selects the lists that are to be searched
according to the selection criteria coded under DD SYSIN. The following
table describes the selection criteria that can be coded.
Selection criteria
Parameter
Value
Max.
length
Occurrence
Default
SDATE
(startdate)
10
1
TODAY
STIME
(starttime)
11
1
00:00:00:00
PDATE
(enddate)
10
1
TODAY
PTIME
(endtime)
11
1
23:59:59:99
DATEMASK
(datemask)
10
1
GORdmask
JOBNAME
(jobname)
8
1..n
*
STEPNAME
(stepname)
8
1..n
*
PROCSTEP
(procstep)
8
1..n
*
DDNAME
(ddname)
8
1..n
*
LISTID (see below)
(listid)
10
1..n
*
JOBID
(jobid)
8
1
*
SUBUSER
(userid)
8
1
*
MSGCLASS
(messageclass)
1
1
*
NETID
(netid)
8
1
*
SYSID
JES2: (system_id)
JES3: (system_id)
4
8
1
1..n
*
ERRTEXT
(errortxt)
8
1
*
ERROR
(YES | NO )
4
1
*
DAY (see below)
(date [+/-days])
20
1..n
TODAY
SLICE (see below)
(hh[:mm]-hh[:mm])
11
1..n
00-23
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
500
Product batch utilities
Selection parameter
processing
B92SSRCH: Advanced search in online logs
Some selection parameters are included in the query that selects the lists
from the _beta log|z database. Other selection parameters are checked
after the query has returned the collection of lists, directly before each
individual list is searched.
DAY parameter
If you specify more than two DAY parameters, the maximum and the
minimum value are included in the query that selects the lists from the
_beta log|z database. The other values are checked after the query has
returned the collection of lists, directly before each individual list is
searched.
The parameters DAY and SDATE/PDATE are mutually exclusive.
SLICE parameter (time
frames)
You can use the SLICE parameter to limit the search to specific time
frames within the selected date/time range. If you don't specify minutes,
hh:00 will be used as start time and hh:59 as end time.
Example:
SDATE(13.11.2014)
PDATE(14.11.2014)
SLICE(09:00-09:59)
Limits the search to these two time frames:
13.11.2014 from 09:00 to 09:59 and
14.11.2014 from 09:00 to 09:59
LISTID parameter
You can use the LISTID parameter to select a list via its internal ID
(SRCDSID). You can specify the ID of the list in decimal format (max. 10
digits) or in hexadecimal format (max. 8 digits).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
501
Product batch utilities
B92SSRCH: Advanced search in online logs
Search-related parameters
Overview
In the second step, B92SSRCH searches the selected lists. This section
describes the search-related parameters that can be coded.
Search-related
parameters
Occurrence
Default
(search expression) 9999
1
none
CASESENSITIVE
(YES | NO )
4
1
NO
NODATARC (see below)
(rc)
4
1
1
NODATAMSG (see below)
(message)
59
1
none
Parameter
Value
SEARCH (see "Search expressions"
on page 503)
NODATARC parameter
Max.
length
If the first processing step (job/list selection) ends with "No data found",
B92SSRCH ends with RC=4.
If the second processing step (list search) ends with "No data found",
B92SSRCH ends with RC=1 by default. This return code can be changed
using the NODATARC parameter.
Note: The return codes 4, 8 and 12 cannot be used as value for
NODATARC.
NODATAMSG parameter
If the first processing step (job/list selection) ends with "No data found",
B92SSRCH writes one of these messages to OMSPRINT:
•
NO DATA FOUND IN TABLE JBR
•
NO DATA FOUND IN TABLE JLR
If the second processing step (list search) ends with "No data found",
B92SSRCH does not write a message by default. Use the NODATAMSG
parameter if you want B92SSRCH to write a message in this situation. The
specified message will be written to OMSPRINT and to JESMSGLG. For
example:
Parameters in SYSIN
NODATARC(3)
NODATAMSG('NO HITS!')
Messages in OMSPRINT
NO HITS!
PROGRAM B92SSRCH (POMnnnn) ENDED WITH RC(0003).
Messages in JESMSGLG
OMS9999I NO HITS!
OMS1026I PROGRAM(B92SSRCH) ENDED WITH RC(3)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
502
Product batch utilities
B92SSRCH: Advanced search in online logs
Search expressions
Overview
The SEARCH parameter specifies what to search for.
The search is line-based. Control characters are not interpreted.
SEARCH syntax
The SEARCH parameter has the following syntax:
SEARCH(search_expression)
You can connect multiple search expressions using AND or OR, for
example:
SEARCH(search_expression1 AND search_expression2 OR
search_expression3...)
You can use parentheses to control order of precedence, for example:
SEARCH(search_expression1 AND (search_expression2 OR
search_expression3))
The SEARCH parameter can be continued on subsequent lines.
Search expression
A search expression consists of one or more values, which must be
specified in the prescribed order. The following values can be specified:
SEARCH('string' boundary startcol endcol NOT)
The search string is required. All other values are optional.
Value
Meaning
'string'
Search string
The search string must be enclosed in single quotation marks.
The search string must be coded on a single line. It is not
possible to continue a search string on the following line.
Prefix the string with X if you want to search for a hexadecimal
string, for example:
SEARCH(X'C2C5E3C1' WORD 10 20)
Prefix the string with P if you want to search for a picture string
(see page 506).
boundary
Position of the search string within a word
boundary can be one of the following:
PREFIX
At the beginning of a word
SUFFIX
At the end of a word
WORD
As a single word
A word consists of alphanumeric characters (A..Z, a..z, 0..9).
The search engine interprets any other characters as a
separator.
If boundary is not specified, the string can occur at any
position.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
503
Product batch utilities
B92SSRCH: Advanced search in online logs
Value
Meaning
startcol
endcol
Column positions where the search is to start and end
Specify one value if the string has to occur at exactly this
column position. B92SSRCH calculates endcol based on the
length of the string. Don't specify any column positions if you
want to search the entire line.
Allowed values: 1..10000
Negates the search expression, i.e. lines where 'string' does
not occur at the specified position are regarded as hits.
NOT
Examples
•
Hit lines must contain both strings EUR and Paid:
SEARCH('EUR' AND 'Paid')
•
Hit lines must contain either a combination of EUR and Paid, or a
combination of Account and Settled:
SEARCH(('EUR' AND 'Paid') OR ('Account' AND 'Settled'))
Recommendation: Using parentheses in this type of search
expression is recommended because this makes the expression more
readable. But parentheses are not strictly required in this example
because the following search expression leads to the same result:
SEARCH('EUR' AND 'Paid' OR 'Account' AND 'Settled')
•
Hit lines must contain both EUR and Paid, but not Settled:
SEARCH('EUR' AND 'Paid' AND 'Settled' NOT)
•
Hit lines must contain Paid between column 5 and 30, or Settled
between column 17 and 25:
SEARCH(('Paid' 5 30) OR ('Settled' 17 25))
•
Hit lines must contain OMS at the beginning of a word or VT.DATA at
the end of a word:
SEARCH(('OMS' PREFIX) OR ('VT.DATA' SUFFIX))
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
504
Product batch utilities
B92SSRCH: Advanced search in online logs
•
Hit lines must contain one of the specified RACF commands at the
beginning of the line. Lines are searched for the long version and for
the short version of the command, with or without preceding
TSOEXEC.
SEARCH( ( 'ADDGROUP ' 1 9 OR 'AG '
1 3 OR
'ADDSD '
1 6 OR 'AD '
1 3 OR
'ADDUSER ' 1 8 OR 'AU '
1 3 OR
'ALTDSD '
1 7 OR 'ALD ' 1 4 OR
'ALTGROUP ' 1 9 OR 'ALG ' 1 4 OR
'ALTUSER ' 1 8 OR 'ALU ' 1 4 OR
'DELDSD '
1 7 OR 'DD '
1 3 OR
'DELGROUP ' 1 9 OR 'DG '
1 3 OR
'DELUSER ' 1 8 OR 'DU '
1 3 )
OR 'TSOEXEC ' 1 8 AND
(' ADDGROUP ' OR ' AG ' OR
' ADDSD '
OR ' AD ' OR
' ADDUSER ' OR ' AU ' OR
' ALTDSD '
OR ' ALD ' OR
' ALTGROUP ' OR ' AG ' OR
' ALTUSER ' OR ' ALU ' OR
' DELDSD '
OR ' DD ' OR
' DELGROUP ' OR ' DG ' OR
' DELUSER ' OR ' DU ' ) )
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
505
Product batch utilities
Picture strings
B92SSRCH: Advanced search in online logs
B92SSRCH supports ISPF picture strings. Prefix the string with P if you
want to search for a picture string.
Several characters have a special meaning when used in a picture string.
Some of these special characters depend on your EBCDIC codepage. The
following table shows an overview of the supported characters with special
meaning in selected codepages:
Hexcode
in
EBCDIC
IBM273/
IBM1141
(Germany)
IBM037/
IBM1140
(US etc.)
IBM297/
IBM1147
(France)
IBM280/
IBM1144
(Italy)
IBM284/
IBM1145
(Spain)
Any character
7E
=
=
=
=
=
Any character that is not a blank
5F
^
¬
^
^
¬
Any character that cannot be displayed
4B
.
.
.
.
.
Any numeric character, 0-9
7B
#
#
£
£
Ñ
Any non-numeric character
60
-
-
-
-
-
Any alphabetic character
7C
§
@
à
§
@
Any lowercase alphabetic character
4C
<
<
<
<
<
Any uppercase alphabetic character
6E
>
>
>
>
>
Any special character, neither
alphabetic nor numeric
5B
$
$
$
$
$
Examples
This picture string finds any sequence of 3 letters plus 4 digits plus 1 letter:
German host codepage:
P'§§§####§'
US host codepage:
P'@@@####@'
French host codepage:
P'ààࣣ££à'
Italian host codepage:
P'§§§££££§'
Spanish host codepage:
P'@@@ÑÑÑÑ@'
A picture string can include alphanumeric characters, which represent
themselves, mixed with the characters that have special meaning. For
example, the following picture string can be used to find _beta log|z error
message numbers (OMS plus 4-digit number plus E):
German/US host codepage:
P'OMS####E'
French/Italian host codepage:
P'OMS££££E
Spanish host codepage:
P'OMSÑÑÑÑE'
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
506
Product batch utilities
B92SSRCH: Advanced search in online logs
B92SSRCH reports
Overview
The result of the search is written to one or several reports. A trace is
written by default, which enables you to analyze the search in detail.
Parameters that control
output
Keyword
Syntax
Notes
PRINT
PRINT(m n [ALL|FIRST|LAST])
Controls how search hits are logged in OMSOUT
and B92LOG (see below)
TRACE
YES | NO (default YES)
If YES, trace information is output to reports
OMSPRINT includes:
•
Total number of occurrence of each string
(These numbers include occurrences in lines
that do not qualify as search hits.)
If DD B92LOG is coded, it includes:
PUNCH
((varname) [('string')] [mode])
•
SYSIN parameters processed (including
default parameters and their values)
•
Number of selected jobs (JBR) and lists (JLR)
•
Search hit information (same as OMSOUT)
The PUNCH parameter can be used to define your
own report, which is output to OMSPUNCH.
For more information, see "Customer-specific
report (OMSPUNCH)" on page 512.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
507
Product batch utilities
PRINT parameter
B92SSRCH: Advanced search in online logs
The PRINT parameter controls how search hits are logged in OMSOUT
and B92LOG:
By default, B92SSRCH prints the following for each list with search hits:
1. Header line that identifies the job list, which contains the following
information (OMSOUT and B92LOG):
•
Job name (SRCJOBN)
•
Job ID (SRCJOBI)
•
Step name (SRCSTPD)
•
Proc step (SRCPRCD)
•
DD name (SRCDDND)
•
Submit date (SRCSUBD)
•
Submit time (SRCSUBT)
2. If PRINT(m n ALL|LAST):
•
Number of lines that were searched (B92LOG only)
3. Hit lines of the job list (OMSOUT only)
This output corresponds to the following values of the PRINT parameter:
PRINT(0 0 ALL)
Code the PRINT parameter with the following values if you want to modify
output as follows:
m
Print also the specified number of lines that precede each hit line
n
Print also the specified number of lines that follow each hit line
ALL
Print all hits of each list
FIRST Print only the first hit of each list
LAST Print only the last hit of each list
Legal values for m and n: 0..9 (Control characters are not interpreted.)
B92SSRCH ensures that each line is only output once if there is any
overlap between hit lines and preceding/following lines. For example, if a
list contains two hits in neighboring lines and PRINT(2 1 ALL),
B92SSRCH prints the following:
1. Two lines preceding the first hit line
2. First hit line
3. Second hit line
4. One line following the second hit line
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
508
Product batch utilities
Output datasets
B92SSRCH: Advanced search in online logs
The following output datasets can be specified for B92SSRCH
(all optional):
DD name
Contents
OMSPRINT
•
PTF level
•
SYSIN definitions
•
Return code with error messages
•
If RC=0, statistics on the number of hits
B92LOG
Trace output
OMSOUT
Results of the search in standard format: hit lines, page
number, line number
OMSPUNCH
Customer-specific report defined by the PUNCH parameter
For more information, see "Customer-specific report
(OMSPUNCH)" on page 512.
OMSPRINT
OMSPRINT contains the following information:
•
PTF level
•
SYSIN definitions
•
Return code with error messages
•
If RC=0, statistics on the number of hits
+-----------------------------------------------------------------------------------------------------------------------------------+
|THE FOLLOWING SYSIN PARAMETER WERE PROCESSED:
|
|SDATE(YESTERDAY)
|
|PDATE(TODAY)
|
|SLICE(08-09)
|
|DATEMASK(DD.MM.YYYY)
|
|JOBNAME(RE§DUMPA)
|
|DDNAME(*)
|
|SEARCH('CHARACTER' AND 'SECTION')
|
|-----------------------------------------------------------------------------------------------------------------------------------|
|STRING 'CHARACTER' OCCURRED
12 TIMES AS STRING
|
|STRING 'SECTION'
OCCURRED
4 TIMES AS STRING
|
|-----------------------------------------------------------------------------------------------------------------------------------|
|PROGRAM B92SSRCH (POM6104) ENDED WITH RC(0000).
|
+-----------------------------------------------------------------------------------------------------------------------------------+
Note: If TRACE is set to YES, this report lists the total number of
occurrence of each string. These numbers include occurrences in lines
that do not qualify as search hits.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
509
Product batch utilities
OMSOUT
B92SSRCH: Advanced search in online logs
OMSOUT contains the result of the search. Two lines are output for each
hit:
Line 1: Jobname, JES ID, step name, procstep name, DD name, submit
date, submit time
Line 2: page:line = hit line
+-----------------------------------------------------------------------------------------------------------------------------------+
|BETA SYSTEMS V7R2-nn B92SSRCH REPORT 13.11.2014 AT 08:22:35 PAGE
1
|
|-----------------------------------------------------------------------------------------------------------------------------------|
|! SRCJOBN: RE§DUMPA SRCJOBI: J0079368 SRCSTPD: JES2
SRCPRCD:
SRCDDND: JESJCLIN SRCSUBD: 12.11.2014 SRCSUBT: 08:58:31 !|
|000001:0012 = //*THIS CHARACTER (§) IS A SECTION MARK
|
|-----------------------------------------------------------------------------------------------------------------------------------|
|! SRCJOBN: RE§DUMPA SRCJOBI: J0079368 SRCSTPD: JES2
SRCPRCD:
SRCDDND: JESJCL
SRCSUBD: 12.11.2014 SRCSUBT: 08:58:31 !|
|000001:0009 =
//*THIS CHARACTER (§) IS A SECTION MARK
|
|-----------------------------------------------------------------------------------------------------------------------------------|
|! SRCJOBN: RE§DUMPA SRCJOBI: J0080245 SRCSTPD: JES2
SRCPRCD:
SRCDDND: JESJCLIN SRCSUBD: 13.11.2014 SRCSUBT: 08:21:08 !|
|000001:0012 = //*THIS CHARACTER (§) IS A SECTION MARK
|
|-----------------------------------------------------------------------------------------------------------------------------------|
|! SRCJOBN: RE§DUMPA SRCJOBI: J0080245 SRCSTPD: JES2
SRCPRCD:
SRCDDND: JESJCL
SRCSUBD: 13.11.2014 SRCSUBT: 08:21:08 !|
|000001:0009 =
//*THIS CHARACTER (§) IS A SECTION MARK
|
+-----------------------------------------------------------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
510
Product batch utilities
B92LOG
B92SSRCH: Advanced search in online logs
B92LOG contains trace information. It is written if TRACE is set to YES.
+-----------------------------------------------------------------------------------------------------------------------------------+
|SYSIN PARAMETER:
|
|JOBNAME
(RE§DUMPA)
|
|STEPNAME
(*
)
|
|LISTID
(*
)
|
|PROCSTEP
(*
)
|
|ERRTEXT
(*
)
|
|ERROR
(*)
|
|JOBID
(*
)
|
|SUBUSER
(*
)
|
|SDATE
(YESTERDAY )
|
|STIME
(00:00:00:00)
|
|PDATE
(TODAY
)
|
|PTIME
(23:59:59:99)
|
|DATEMASK
(DD.MM.YYYY)
|
|MSGCLASS
(*)
|
|NETID
(*
)
|
|CASESENSITIVE(N)
|
|TRACE
(Y)
|
|SYSID
(*
)
|
|NODATARC
(0001)
|
|DDNAME
(*
)
|
|SLICE
(08:00 - 09:59)
|
|PRINT
(0 0 ALL)
|
|STRING
('CHARACTER')
|
|STRING
('SECTION')
|
|-----------------------------------------------------------------------------------------------------------------------------------|
|
2 ENTRIES HAVE BEEN SELECTED IN TABLE JBR
|
|-----------------------------------------------------------------------------------------------------------------------------------|
|
16 ENTRIES HAVE BEEN SELECTED IN TABLE JLR
|
|-----------------------------------------------------------------------------------------------------------------------------------|
|! SRCJOBN: RE§DUMPA SRCJOBI: J0079368 SRCSTPD: JES2
SRCPRCD:
SRCDDND: JESJCLIN SRCSUBD: 12.11.2014 SRCSUBT: 08:58:31 !|
|TOTAL NUMBER OF LINES:
47
|
|-----------------------------------------------------------------------------------------------------------------------------------|
|! SRCJOBN: RE§DUMPA SRCJOBI: J0079368 SRCSTPD: JES2
SRCPRCD:
SRCDDND: JESJCL
SRCSUBD: 12.11.2014 SRCSUBT: 08:58:31 !|
|TOTAL NUMBER OF LINES:
35
|
|-----------------------------------------------------------------------------------------------------------------------------------|
|! SRCJOBN: RE§DUMPA SRCJOBI: J0080245 SRCSTPD: JES2
SRCPRCD:
SRCDDND: JESJCLIN SRCSUBD: 13.11.2014 SRCSUBT: 08:21:08 !|
|TOTAL NUMBER OF LINES:
47
|
|-----------------------------------------------------------------------------------------------------------------------------------|
|! SRCJOBN: RE§DUMPA SRCJOBI: J0080245 SRCSTPD: JES2
SRCPRCD:
SRCDDND: JESJCL
SRCSUBD: 13.11.2014 SRCSUBT: 08:21:08 !|
|TOTAL NUMBER OF LINES:
35
|
+-----------------------------------------------------------------------------------------------------------------------------------+
Note: B92LOG lists the total number of JBR/JLR entries retrieved during
the selection step. This includes entries whose lists do not qualify as
search hits.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
511
Product batch utilities
B92SSRCH: Advanced search in online logs
Customer-specific report (OMSPUNCH)
Overview
You can use the PUNCH parameter to define your own report.
B92SSRCH writes one line to OMSPUNCH for each line that matches the
search expression. The PUNCH parameter defines which information
should be included in this line. You can choose from a set of variables,
which B92SSRCH replaces with the appropriate values during the search.
Optionally, you can add strings to separate these values.
Syntax
The PUNCH parameter has the following syntax:
PUNCH( (var) [('string')] [mode] )
More complex instructions will be clearer if you code parameters on
separate lines, for example:
PUNCH((var_1) ('string_1')
(var_2) ('string_2')
...
(var_n) ('string_n'))
-ORPUNCH((var_1)
(var_2)
...
(var_n)
CSV(x))
where:
•
var_1, var_2 ... var_n stand for the names of variables
•
string stands for a sequence of characters
•
x stands for a single character
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
512
Product batch utilities
Job/List information
Page/Line number
Hit line
B92SSRCH: Advanced search in online logs
The following variables refer to metadata on the job and list that contains
matching lines:
Variable
Description
SRCJOBN
Job name
SRCJOBI
Job ID
SRCSTPD
Step name
SRCPRCD
Proc step
SRCDDND
DD name of the list
SRCSUBD
Submit date
SRCSUBT
Submit time
SRCSTRTD
Job start date
SRCSTRTT
Job start time
SRCENDD
Job end date
SRCENDT
Job end time
JBRSYSID
Execution system ID
JBRJ3SYS
JES3 system ID
JBRSUBID
Submitter user ID
JBRNETID
Job net ID
JBRERRTX
Determined error text
The following variables refer to the location of the matching lines within the
list:
Variable
Description
PNUM
Page number where the hit was found
LNUM
Line number (on page) where the hit was found
TLNUM
Line number (in list) where the hit was found
The following variable refers to the matching lines themselves:
Variable
Description
LINE
Entire text line
LINE startcol endcol
Text between specified column positions
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
513
Product batch utilities
STD mode
B92SSRCH: Advanced search in online logs
In STD mode, parameter values and separating strings are simply
concatenated. STD mode is the default, which means that there is no need
to code this parameter.
SEARCH('CHARACTER' AND 'SECTION')
PUNCH( (SRCJOBI) ('--')
(SRCDDND) (:)
(LINE)
STD )
-ORSEARCH('CHARACTER' AND 'SECTION')
PUNCH( (SRCJOBI) ('--')
(SRCDDND) (:)
(LINE) )
Report lines in OMSPUNCH:
J0079368--JESJCLIN:
J0079368--JESJCL :
CSV mode
//*THIS CHARACTER (§) IS A SECTION MARK
//*THIS CHARACTER (§) IS A SECTION MARK
In CSV mode, each parameter value (and each separating string, if
present) is enclosed in quotation marks, and the specified delimiter is
inserted between them:
SEARCH('CHARACTER' AND 'SECTION')
PUNCH( (SRCJOBI) (SRCDDND) (LINE) CSV(;) )
Report lines in OMSPUNCH:
"J0079368";"JESJCLIN";"//*THIS CHARACTER (§) IS A SECTION MARK"
"J0079368";"JESJCL ";"
//*THIS CHARACTER (§) IS A SECTION MARK"
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
514
Product batch utilities
B92WAIT4: Waiting for a job or list
B92WAIT4: Waiting for a job or list
Overview
B92WAIT4 checks for the presence of a job or list in the _beta log|z
database. It is possible to make the program wait and repeat this check at
specified intervals until the desired list is present. Optionally, you can
check for additional conditions.
Use case
B92WAIT4 was introduced to avoid problems caused by the asynchronous
processing of events and reading in, but you can use B92WAIT4 in any
situation where it is useful to check that a required list is present.
Using B92WAIT4 in event processing
An event definition specifies that a particular list of a job is to be processed
by B92PRINT or B92SSRCH. Because reader processing and event
processing are asynchronous, it is possible that the triggered event is
processed before the data of the originating job has been completely
stored in the _beta log|z database. In this case, B92PRINT or B92SSRCH
would end with a Job not Found error because the corresponding Job
Base Records (JBR) or Job List Records(JLR) are not yet present in the
_beta log|z database. You can prevent this type of error from happening
by using a two-step host job for this type of event action. Step 1
(B92WAIT4) checks for the presence of the desired job or list, and step 2
(B92PRINT or B92SSRCH) processes the corresponding list.
JCL
B92WAIT4 is a standalone program, which does not use RFF.
+----------------------------------------------------------------------+
|jobcard
|
|//CHECK
EXEC PGM=B92WAIT4
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//*
|
|//OMSPRINT DD SYSOUT=*
|
|//B92LOG
DD SYSOUT=*
|
|//SYSIN
DD *
|
| SSID
= B92P
|
| DATE
= %DATE.
|
| TIME
= %TIME.
|
| JOBNAME = %JOBNAME.
|
| JOBID
= %JOBID.
|
|/*
|
+----------------------------------------------------------------------+
-OR- (using EXEC parm)
+----------------------------------------------------------------------+
|jobcard
|
|//CHECK
EXEC PGM=B92WAIT4,
|
|//
PARM=('S=B92P,D=%DATE.,J=%JOBNAME.,I=%JOBID.')
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//*
|
|//OMSPRINT DD SYSOUT=*
|
|//B92LOG
DD SYSOUT=*
|
+----------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
515
Product batch utilities
Parameters
B92WAIT4: Waiting for a job or list
Parameters for B92WAIT4 can be specified via the EXEC parm or via
DD SYSIN or both. In case of conflict, the EXEC parm parameter has
precedence over the DD SYSIN parameter.
EXEC parm
A
SYSIN parameter
Description
DATEMASK
Valid date mask, e.g. YYYY-MM-DD
The DATEMASK parameter is optional.
See description of DATE parameter
below.
S
SSID
_beta log|z subsystem ID
J
JOBNAME
Jobname(JBR field SRCJOBN)
You can use * as mask character.
In event actions, you can use
%JOBNAME. for the name of the job that
originates the event.
I
JOBID
Jobid(JBR field SRCJOBI)
You can use * as mask character.
In event actions, you can use %JOBID.
for the JES ID of the job that originates
the event.
F
FILE
File/DDname (JLR field SRCDDND)
To identify the list you can specify:
ddname
-ORstep.ddname
-ORstep.procstep.ddname
You can use * as mask character.
L
LISTID
Unique dataset ID of the file within the job
(JLR field SRCDSID)
In list-specific event actions, you can use
%LISTID. for the dataset ID of the
originating list.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
516
Product batch utilities
B92WAIT4: Waiting for a job or list
EXEC parm
D
SYSIN parameter
Description
DATE
Submit date (JBR field SRCSUBD)
You can use any of the supported date
masks (see online option P.2). B92WAIT4
is able to recognize most date formats
automatically based on the length and the
separator(s) used. Optionally, you can
specify the date format using the
DATEMASK parameter.
You can also specify TODAY,
YESTERDAY, or the day of the week. The
point of reference of TODAY and
YESTERDAY is the current time, not the
time when B92WAIT4 was started.
In event actions, you can use %DATE. for
the submit date of the job that originates
the event.
T
TIME
Submit time (JBR field SRCSUBT)
Specify the time using these formats:
•
hh:mm:ss:xx
•
hh:mm:ss
(selects hh:mm:ss:00 - hh:mm:ss:99)
•
hh:mm
(selects hh:mm:00:00 - hh:mm:59:99)
•
hh
(selects hh:00:00:00 - hh:59:59:99)
In event actions, you can use %TIME. for
the submit time of the job that originates
the event.
C
CHECK
Check condition, for example:
•
ERROR<YES>
•
STATUS<E>
•
ERRTEXT<CC 0008>
•
SYSTEM<sysid>
•
NETID<netid>
You can use * as mask character, for
example:
•
R
RETRY
ERRTEXT<CC*>
Number of tries/retries
1..999 seconds, default: 6; code 1 if
B92WAIT4 should only try once.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
517
Product batch utilities
B92WAIT4: Waiting for a job or list
EXEC parm
N
SYSIN parameter
Description
INTERVAL
Retry interval
1..999 seconds, default: 10
M
MULTIRC
RC if selection returns multiple hits
1..4095; default: 1
Q
CHECKRC
RC if the result of one or more CHECK
conditions is negative
1..4095; default: 2
Return codes
OMSPRINT
0
Single matching job/list found
1
Multiple matching jobs/lists found
2
At least one check condition failed
4
No matching job/list found
8
Error occurred
24
Subsystem not available
In the following example, B92WAIT4 has found a single matching job:
+----------------------------------------------------------------------------------+
|BETA92 V7R2-nn CHECK AND WAIT FOR A JOB OR LIST
13.07.2012 07:16:58:05
|
|
|
|Request summary:
|
| parm / sysin
value
|
| ---- / -------- ---------------------------|
| S
/ SSID:
(B92P)
|
| J
/ JOBNAME: (B92XXXX4)
|
| I
/ JOBID:
()
|
| F
/ FILE:
()
|
| L
/ LISTID:
()
|
| D
/ DATE:
(TODAY)
|
| A
/ DATEMASK: (DD.MM.YYYY)
|
| T
/ TIME:
(07:16)
|
| C
/ CHECK:
(<>)
|
| R
/ RETRY:
(6)
|
| N
/ INTERVAL: (10)
|
| M
/ MULTIRC: (1)
|
| Q
/ CHECKRC: (2)
|
|----------------------------------------------|
|JOB FOUND: B92XXXX4 (J0023338) 13.07.2012 / 07:16:37:89
|
|CHECK COUNTDOWN 05 - JOB/LIST FOUND
|
|CHECK SUCCESSFUL
|
|PROGRAM B92WAIT4 (POM3014 ) ENDED WITH RC(0)
|
+----------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
518
Product batch utilities
B92WAIT4: Waiting for a job or list
In the following example, B92WAIT4 has found two matching lists:
+----------------------------------------------------------------------------------+
|BETA92 V7R2-nn CHECK AND WAIT FOR A JOB OR LIST
13.07.2012 07:16:59:15
|
|
|
|Request summary:
|
| parm / sysin
value
|
| ---- / -------- ---------------------------|
| S
/ SSID:
(B92P)
|
| J
/ JOBNAME: (B92XXXX4)
|
| I
/ JOBID:
()
|
| F
/ FILE:
(OMSPRINT)
|
| L
/ LISTID:
()
|
| D
/ DATE:
(HEUTE)
|
| A
/ DATEMASK: (DD.MM.YYYY)
|
| T
/ TIME:
(07:16)
|
| C
/ CHECK:
(<>)
|
| R
/ RETRY:
(6)
|
| N
/ INTERVAL: (10)
|
| M
/ MULTIRC: (1)
|
| Q
/ CHECKRC: (2)
|
|----------------------------------------------|
|LIST FOUND: B92XXXX4 (J0023338) 13.07.2012 / 07:16:37:89 OMSPRINT/00000257 STP1
|
|LIST FOUND: B92XXXX4 (J0023339) 13.07.2012 / 07:16:57:95 OMSPRINT/00000257 STP1
|
|CHECK COUNTDOWN 05 - JOB/LIST FOUND
|
|CHECK SUCCESSFUL
|
|PROGRAM B92WAIT4 (POM3014 ) ENDED WITH RC(1)
|
+----------------------------------------------------------------------------------+
B92LOG
An activity log is written to DD B92LOG:
+----------------------------------------------------------------------------------------------------------------------------------------+
|* 13.07.2012 07:16:58.05: program B92WAIT4 (POM3014 ) started
|
|* 13.07.2012 07:16:58.05: lrecl(0) blksize(0) recfm(
)
|
|* 13.07.2012 07:16:58.05: SELECT TABLE(JBR) FIELDS(SRCJOBN,SRCJOBI,SRCSUBT,SRCSUBD,JBRNETID,JBRERRTX,JBRSYSID,JBRJ3SYS,JBRSTFL JBRSTFL |
|* 13.07.2012 07:16:58.05: G,JBRQUFER) WHERE(SRCJOBN LIKE B92XXXX4 AND SRCSUBD = TODAY AND SRCSUBT = 07:16)
|
|* 13.07.2012 07:16:58.05: rc = -1 / 0, rcnt = 1, mcnt = 1, i = 5
|
|* 13.07.2012 07:16:58.06: program B92WAIT4 (POM3014 ) ended with rc(0)
|
+----------------------------------------------------------------------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
519
Product batch utilities
B92WEEKL: Weekly job
B92WEEKL: Weekly job
Overview
B92WEEKL includes several housekeeping batch utilities. B92WEEKL
should be run on a weekly basis. This will prevent the _beta log|z
databases from getting too full.
For details, see the description of the individual each batch utilities.
Batch utilities
B92WEEKL includes the following batch utilities:
1. Archive cleanup utility - B92CLARC (see page 424)
2. Generation archive record cleanup utility - B92CLAR2 (see page 421)
3. Agent rule cleanup utility - B92CLARS (see page 429)
4. Event cleanup utility - B92CLEVT (see page 434)
You can start B92WEEKL from the BETA92.CNTL or under online option
A.3.1, option W (see "Tailoring JCL for batch utilities (Option A.3.1)" on
page 175).
Note: The analyze mode to simulate the steps of execution is not available
for B92WEEKL. However, you can first choose the analyze mode for each
of the batch utilities included in B92WEEKL before starting the weekly job
itself.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
520
Product batch utilities
JCL
B92WEEKL: Weekly job
You can find JCL in the BETA92.CNTL in member B92WEEKL.
+-----------------------------------------------------------------------+
|jobcard
|
|//* ----------------------------------------------------------------- *|
|//*
WEEKLY MAINTENANCE
*|
|//*
- B92WEEKLY *|
|//*
(FILE TAILORING)
*|
|//* ----------------------------------------------------------------- *|
|//*
THIS JOB DELETES EXPIRED ARCHIVE INFORMATION,
*|
|//*
DELETES EXTENDED ARCHIVE INFORMATION OLDER THAN N DAYS,
*|
|//*
DELETES ARSTATUS AND STATISTCS INFO OLDER THAN N DAYS AND
*|
|//*
DELETES EVENT INFO OLDER THAN N DAYS FROM THE B92 DATABASE.
*|
|//*********************************************************************|
|//*-------------------------------------------------------------------*|
|//* STEP 1: THE -ARCHIVE CLEANUP UTILITY- DELETES EXPIRED ARCHIVE *|
|//*
RECORDS AND INFORMATION FROM BETA 92 DATABASE.
*|
|//*-------------------------------------------------------------------*|
|//CLNARC EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92CLARC,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DISP=SHR,DSN=BETA92.DB.DEF
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSUDUMP DD SYSOUT=*
|
|//SYSABEND DD SYSOUT=*
|
|//*
|
|//OMSPRINT DD SYSOUT=*
|
|//B92LOG
DD SYSOUT=*
|
|//*-------------------------------------------------------------------*|
|//* STEP 2: THE -EXTENDED ARCHIVE CLEANUP UTILITY- DELETES EXTENDED *|
|//*
ARCHIVE INFORMATION THAT IS OLDER THAN THE SPECIFIED
*|
|//*
NUMBER OF DAYS.
*|
|//*-------------------------------------------------------------------*|
|//CLAR2
EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92CLAR2,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DISP=SHR,DSN=BETA92.DB.DEF
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSABEND DD SYSOUT=*
|
|//*
|
|//OMSPRINT DD SYSOUT=*
|
|//B92LOG
DD SYSOUT=*
|
|//*
|
|//SYSIN
DD *
|
| DAYS(5)
|
(continued)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
521
Product batch utilities
B92WEEKL: Weekly job
(continued)
|//*-------------------------------------------------------------------*|
|//* STEP 3: THE -ARSTATUS AND STATISTICS CLEANUP UTILITY- DELETES
*|
|//*
AGENT-RULE STATUS AND B92 STATISTICS INFORMATION THAT
*|
|//*
IS OLDER THAN THE SPECIFIED NUMBER OF DAYS.
*|
|//*-------------------------------------------------------------------*|
|//CLARS
EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92CLARS,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DISP=SHR,DSN=BETA92.DB.DEF
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSABEND DD SYSOUT=*
|
|//*
|
|//OMSPRINT DD SYSOUT=*
|
|//B92LOG
DD SYSOUT=*
|
|//*
|
|//SYSIN
DD *
|
| ARS_DAYS(5)
|
| STAT_DAYS(30)
|
| MESSAGE(LONG)
|
|//*-------------------------------------------------------------------*|
|//* STEP 4: THE -EVENT CLEANUP UTILITY- DELETES EVENT INFORMATION
*|
|//*
THAT IS OLDER THAN THE SPECIFIED NUMBER OF DAYS.
*|
|//*-------------------------------------------------------------------*|
|//CLEVT
EXEC PGM=BST01RFF,REGION=0M,
|
|//
PARM=('S=92,B01LST=xx,B92LST=xx',
|
|//
'PGM=B92CLEVT,SIGNON=YES')
|
|//*
|
|//STEPLIB DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB
|
|//B92DEF
DD DISP=SHR,DSN=BETA92.DB.DEF
|
|//*
|
|//SFFFDUMP DD SYSOUT=*
|
|//SYSABEND DD SYSOUT=*
|
|//*
|
|//OMSPRINT DD SYSOUT=*
|
|//B92LOG
DD SYSOUT=*
|
|//*
|
|//SYSIN
DD *
|
| DAYS(5)
|
|/*
|
+-----------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
522
Calling _beta log|z from REXX scripts
In this chapter
Calling _beta log|z from REXX scripts
In this chapter
Topic
Page
Introduction ............................................................................................. 524
BRXOPEN: Opening a session .............................................................. 526
BRXOMS - READER: Reader-related commands ................................. 527
BRXCLOSE: Closing a session .............................................................. 530
Example: Starting/Stopping a reader...................................................... 531
Example: Querying reader status ........................................................... 532
Example: Querying reader usage statistics ............................................ 533
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
523
Calling _beta log|z from REXX scripts
Introduction
Introduction
Overview
The BRX interface enables you to connect to _beta log|z from your REXX
scripts, for example, in order to retrieve usage data or to start/stop
readers.
A set of external REXX functions has been made available in the
BETA92.LOAD for this purpose. This LOAD library must be allocated in
the steplib of the JCL or in your logon procedure.
Functions
Function
Description
BRXOPEN
Opens a session in the indicated subsystem
BRXOMS
Calls a command that _beta log|z offers for
access via the REXX interface
The following command group is available:
READER
BRXCLOSE
JCL
Starting/Stopping a reader and
querying reader status or reader
usage/statistics
Closes the indicated session
The program IKJEFT01 sets up a TSO/E environment from which you can
invoke execs and CLISTs and issue TSO/E commands.
The following JCL works with a temporary dataset to include the REXX in
the job output:
+------------------------------------------------------------------------+
|jobcard
|
|//CREATE
EXEC PGM=IEBGENER
|
|//SYSIN
DD DUMMY
|
|//SYSPRINT DD SYSOUT=*
|
|//SYSUT2
DD DSN=&TEMPREX(REXTSO),DISP=(,PASS),
|
|//
SPACE=(CYL,(1,1,1)),UNIT=3390,
|
|//
DCB=(LRECL=80,RECFM=FB,DSORG=PO)
|
|//SYSUT1
DD
*
|
| your rexx
|
|/*
|
|//RUN
EXEC PGM=IKJEFT01,PARM='REXTSO'
|
|//STEPLIB
DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SYSEXEC
DD DISP=(SHR,PASS),DSN=&TEMPREX
|
|//SYSTSPRT DD SYSOUT=*
|
|//SYSTSIN
DD DUMMY
|
+------------------------------------------------------------------------+
The following JCL runs the exec named BRXEX#01 contained in the PO
dataset B92USR.REXX:
+------------------------------------------------------------------------+
|jobcard
|
|//RUN
EXEC PGM=IKJEFT01,PARM='BRXEX#01'
|
|//STEPLIB
DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SYSEXEC
DD DISP=SHR,DSN=B92USR.REXX
|
|//SYSTSPRT DD SYSOUT=*
|
|//SYSTSIN
DD DUMMY
|
+------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
524
Calling _beta log|z from REXX scripts
Introduction
Alternatively, you can also use IRXJCL, which runs the exec in a nonTSO/E address space:
+------------------------------------------------------------------------+
|jobcard
|
|//RUN
EXEC PGM=IRXJCL,PARM='BRXEX#01'
|
|//STEPLIB
DD DISP=SHR,DSN=BETA92.LOAD
|
|//
DD DISP=SHR,DSN=BSA.LOAD
|
|//SYSEXEC
DD DISP=SHR,DSN=B92USR.REXX
|
|//SYSTSPRT DD SYSOUT=*
|
|//SYSTSIN
DD DUMMY
|
+------------------------------------------------------------------------+
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
525
Calling _beta log|z from REXX scripts
BRXOPEN: Opening a session
BRXOPEN: Opening a session
Overview
The BRXOPEN function opens a session in a subsystem.
Opening a session is a prerequisite for calling a product-specific function.
The session ID is a required parameter of the BRXOMS function.
It is possible and sometimes necessary to open more than one session in
the same subsystem to control the processing of a script.
Syntax
Components
Example
sessionid = BRXOPEN("ssid")
sessionid
Unique identifier of the session in the script
ssid
Max. 4-digit subsystem ID
SESSION1 = BRXOPEN("B92P")
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
526
Calling _beta log|z from REXX scripts
BRXOMS - READER: Reader-related commands
BRXOMS - READER: Reader-related commands
Overview
The READER command group of the BRXOMS function enables you to
work with readers.
Commands
The READER command group has the following commands:
SELECT
Executes a selection for reader status
Subparameters:
Selection criteria to be passed to the
command API
USAGE_SELECT
Executes a selection for reader usage statistics
Subparameters:
Selection criteria to be passed to the
command API
USAGE_HISTORY_
SELECT
Executes a selection for reader usage history
Subparameters:
Selection criteria to be passed to the
command API
FETCH
Fetches a single result row from an ongoing
selection
Each field of the returned result is available in a
REXX variable of the same name.
GET
Gets a single result by ID
Each field of the returned result is available in a
REXX variable of the same name.
Subparameter:
RDRKEY (Unique reader key)
START
Starts a reader
Subparameter:
RDRKEY (Unique reader key)
STOP
Stops a reader
Subparameter:
RDRKEY (Unique reader key)
RESTART
Restarts a reader
Subparameter:
RDRKEY (Unique reader key)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
527
Calling _beta log|z from REXX scripts
Syntax READER
SELECT/FETCH/GET
BRXOMS - READER: Reader-related commands
FETCH and GET are typically used nested like shown below for row-byrow processing of the result of READER SELECT:
RC = BRXOMS(sessionid1, "READER", "SELECT",
selection_parms)
...
IF RC == 0 THEN
DO WHILE(BRXOMS(sessionid1,"READER", "FETCH") == 0)
...
RC = BRXOMS(sessionid2, "READER", "GET", RDRKEY)
...
END
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
528
Calling _beta log|z from REXX scripts
Components
BRXOMS - READER: Reader-related commands
sessionid1
sessionid2
Session IDs opened via BRXOPEN
RC
Return code of this command
Note: The session ID used in GET must be
different from the session ID of the ongoing
database query via SELECT/FETCH.
0
Normal termination
1
End of data encountered by FETCH
command
4
Warning
8
Internal error
16 No data found
20 Backend error (IRC provides more
information)
24 Communication error (IRC provides more
information)
IRC
Information code
IRC is set on RC=20 and RC=24.
selection_parms
Selection parameters supported by the command
API function READER_SEL (see examples later
in this chapter and "B92BCAPI: Querying the
database via command API" on page 409)
RDRKEY
RDRTYPE
RDRNAME
RDRID
STAMODE
STATUS
CUSER
CDATE
CTIME
CSTMP
Fields returned by the command API functions
READER_SEL and READER_GET (see
"B92BCAPI: Querying the database via command
API" on page 409)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
529
Calling _beta log|z from REXX scripts
BRXCLOSE: Closing a session
BRXCLOSE: Closing a session
Overview
The BRXCLOSE() function closes a session in a subsystem.
Syntax
RC = BRXCLOSE("ssid")
Components
ssid
Max. 4-digit subsystem ID
RC
Return code of this command
0
Normal termination
4
Warning
8
Internal error
20 Backend error (IRC provides more
information)
24 Communication error (IRC provides more
information)
IRC
Information code
IRC is set on RC=20 and RC=24.
Example
RC = BRXCLOSE("B92P")
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
530
Calling _beta log|z from REXX scripts
Example: Starting/Stopping a reader
Example: Starting/Stopping a reader
Overview
Following is an example of a REXX that uses the BRX interface of _beta
log|z for stopping a JES reader.
Sample REXX
/* REXX */
BRXDEBUG = "FALSE"
SESSION1 = BRXOPEN("B92P")
/* ACTION AND READER KEY
/* ACTION: START|STOP|RESTART
/* RDRKEY: JES|OSY.<SSID>.<NN>
*/
*/
*/
ACTION = "STOP"
RDRKEY = "JES.B92P.00"
RC = BRXOMS(SESSION1,"READER",ACTION,RDRKEY)
IF RC == 24 THEN SAY "STC NOT AVAILABLE"
LASTRC = RC
CALL BRXCLOSE(SESSION1)
RETURN LASTRC
Note: A command for an OSY reader affects all OSY readers. A command
for a JES reader affects only the indicated JES readers.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
531
Calling _beta log|z from REXX scripts
Example: Querying reader status
Example: Querying reader status
Overview
Following is an example of a REXX that uses the BRX interface of _beta
log|z for querying the status of all JES readers.
Sample REXX
/* REXX */
BRXDEBUG = "FALSE"
SESSION1 = BRXOPEN("9204")
SESSION2 = BRXOPEN("9204")
/* CREATE SELECTION */
PARMS="FIELDS(RDRKEY,RDRTYPE,RDRNAME,STATUS)"
RC = BRXOMS(SESSION1, "READER", "SELECT", PARMS)
IF RC == 24 THEN SAY "STC NOT AVAILABLE"
IF RC == 16 THEN SAY "NO DATA FOUND FOR SELECTION"
/* FETCH RESULT */
IF RC == 0 THEN
DO WHILE(BRXOMS(SESSION1, "READER", "FETCH") == 0)
/* SHOW STATUS ONLY FOR JES READERS */
IF RDRTYPE == "JES" THEN
DO
RC = BRXOMS(SESSION2, "READER", "GET", RDRKEY)
IF RC == 0 THEN
DO
SAY RDRTYPE "READER" RDRKEY "IS" STATUS
END
ELSE
RETURN RC
END
END
/* RC(1) MEANS NO MORE DATA */
IF RC == 1 THEN RC = 0
LASTRC = RC
CALL BRXCLOSE(SESSION1)
CALL BRXCLOSE(SESSION2)
RETURN LASTRC
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
532
Calling _beta log|z from REXX scripts
Example: Querying reader usage statistics
Example: Querying reader usage statistics
Overview
Following is an example of a REXX that uses the BRX interface of _beta
log|z for querying reader usage statistics.
Sample REXX
/* REXX */
BRXDEBUG = "TRUE"
SESSION1 = BRXOPEN("9204")
KEY="JES.9204.01"
/* CREATE SELECTION */
FIELDS="FIELDS(YEAR,WEEK,MONTH,DAY,JOBNUM,LISTNUM,LINENUM,MBYTES)"
RKEY="RDRKEY("KEY")"
PARAMS=RKEY " " FIELDS
RC = BRXOMS(SESSION1, "READER", "USAGE_HISTORY_SELECT", PARAMS)
IF RC == 24 THEN SAY "STC NOT AVAILABLE"
IF RC == 16 THEN SAY "NO DATA FOUND FOR SELECTION"
/* FETCH RESULT */
IF RC == 0 THEN
SAY LEFT("RDRKEY",12) RIGHT("YEAR",4) RIGHT("MONTH",5),
RIGHT("DAY",3) RIGHT("WEEK",4) RIGHT("#JOBS",6),
RIGHT("#LISTS",6) RIGHT("#LINES",6) RIGHT("#MBYTE",6)
DO WHILE(BRXOMS(SESSION1, "READER", "FETCH") == 0)
SAY LEFT(KEY,12) RIGHT(STRIP(YEAR),4) RIGHT(STRIP(MONTH),5),
RIGHT(DAY,3) RIGHT(STRIP(WEEK),4) RIGHT(STRIP(JOBNUM),6),
RIGHT(STRIP(LISTNUM),6) RIGHT(STRIP(LINENUM),6) ,
RIGHT(STRIP(MBYTES),6)
END
/* RC(1) MEANS NO MORE DATA */
IF RC == 1 THEN RC = 0
LASTRC = RC
CALL BRXCLOSE(SESSION1)
RETURN LASTRC
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
533
Extended Index Facility (EIF)
In this chapter
Extended Index Facility (EIF)
In this chapter
Topic
Page
User fields for user-defined indexes ....................................................... 535
EIF Select (Option M.1) .......................................................................... 537
RACF security for EIF jobs ..................................................................... 538
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
534
Extended Index Facility (EIF)
User fields for user-defined indexes
User fields for user-defined indexes
Overview
_beta log|z supports the creation of user-defined indexes for job logs. For
example, you can index program name, library, version, completion code,
error messages, information on individual job steps, individual sysout lists,
or other information that might be relevant to your organization.
Job logs can then be selected according to the following:
Extended Index
Facility (EIF)
•
Your user-defined criteria (for example, program name, library, and
version)
•
The standard criteria (for example, date/time, job name, queue, etc.)
•
A combination of both user-defined and standard criteria
The functions for creating user-defined indexes in _beta log|z are included
in the standard product.
Previous versions of Beta 92 required a separate license for the add-on
Extended Index Facility (EIF).
How EIF works
EIF uses a set of 32 fields in the JBRE record for storing user-defined
selection criteria. The maximum length of each field is 64 characters.
JBRE records are stored in the EXT database. Check whether the size of
the EXT database needs to be adjusted before you start using EIF.
The information for the user-defined fields is extracted from the job logs via
scan definitions. Use the target field IDs 500 through 531 to fill the userdefined fields JBREUF01 through JBREUF32 respectively.
Layout definitions for
online and archive
JBRE records have the same online retention period as JBR records. The
user-defined fields JBREUF01 through JBREUF32 can be used in your
layouts for online jobs. You have to create appropriate layout field
definitions for the user-defined fields to be able to use them in your search
and result layouts.
Only the first eight user-defined fields are included in the GARE table
during archiving. This means that only JBREUF01 through JBREUF08 can
be used in your layout for offline jobs.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
535
Extended Index Facility (EIF)
Implementing EIF
User fields for user-defined indexes
Determine which information you need in addition to the standard criteria
of _beta log|z.
After you have determined which information you require, create the
appropriate definitions in _beta log|z:
•
Create scan definitions to extract the information that is relevant to
you.
•
Create or modify the required layout definitions, namely:
•
Layout field definitions
•
Search layout definitions
•
Result layout definitions
For more information, see "_beta log|z layouts (Option A.1.1)" on
page 63.
•
Specify the default search layout search in the B92LSTxx member:
B92_LAYOUT_EIF=name_HSTJ_SEARCH
Users can override this default by specifying a different layout in the
user profile (Option P.8).
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
536
Extended Index Facility (EIF)
EIF Select (Option M.1)
EIF Select (Option M.1)
Overview
Use option M.1 to access the EIF Select panel.
Enter your selection criteria and press ENTER to display the result table.
Your layout definitions determine which fields are displayed in the select
panel and the result table. Navigation under option M.1 corresponds to the
navigation under option 1. For a description of the line commands and
primary commands, see the _beta log|z User Guide.
Sample panel
PE92BC00 --------------------------------------------------------------------Command ===> ________________________________________________ Scroll ===> PAGE
Selection for Compile Lists by Prod. Time
Layout: XY_HSTJ_SEARCH
Select from last
Select from Date
Select to
Date
===> __ .......
===> __________
===> __________
1-99, (m)inutes, (h)ours, or (d)ays
Time ===> ________
Time ===> ________
Program Name
Source Name
===> ........
===> ........
Optional Criteria
Version
Program Type
Library
Developer
===> ____
===> __________
===> ____________________________________________
===> ________
Job Name
Job ID
===> ________
===> ________
Queue Type ===> ________
Jobs with Notes ===> ____ (Y/N/blank)
Press ENTER key to display selected records.
Press END key to return to the previous menu.
Note on reloading
The reload function of _beta log|z does not support reload via EIF-specific
user fields such as program name or source name.
For EIF jobs, we therefore recommend that you set the online retention
period of the job base record to the same value as the archive retention
period. The online retention period of the job information should be shorter
to prevent that too much information is held online in the JOB database.
For more information, see "Determining online and archive retention
period" on page 111.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
537
Extended Index Facility (EIF)
RACF security for EIF jobs
RACF security for EIF jobs
Overview
Access to EIF jobs is protected via the function codes 67 and 68.
Function codes
•
Function code 67 enables you to include EIF lists in the security
concept. It is available for line commands B, J, S, P, R, and U under
online option M.1 (EIF SELECT).
Function code 67 for EIF works in a similar way to function code 2,
which is used for option 1.
•
RACF profiles for codes
67/68
Function code 68 is available wherever the user has access to the
contents of EIF lists (i.e. Browse, Print, Find).
The following standard RACF profile is created by B92UXSEC:
B92.ssid.STL
You can create an enhanced RACF profile by modifying B92UXSEC. For
example, you can add the value of JBREUF04 (for example, program
name) and JBREUF03 (for example, source name) to the profile:
B92.ssid.STL.jbreuf04.jbreuf03
JBREUF04 and
JBREUF03
When function codes 67 and 68 are invoked, fields S92JOBN and
S92GROUP of control block B92#SEC are filled as follows:
Field name
Type
Description
S92JOBN
CL8
JBREUF03 (for example, source name)
S92GROUP
CL8
JBREUF04 (for example, program name)
When exit program B92UXSEC is called, control block B92#SEC is
transferred to program B92UXSEC.
You can use the values contained in the two fields to adjust the exit
(similar to job group security – function code 19), so that you can only see
EIF lists with specific source names and/or program names.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
538
Scan definitions
In this chapter
Scan definitions
In this chapter
Topic
Page
Overview ................................................................................................. 540
Scan definitions identical for JES2 and JES3 (S#92SJ23) .................... 541
Scan definitions used for JES2 (S#92SJ2) ............................................ 548
Scan definitions used for JES2 syslog (S#92SL2) ................................. 549
Scan definitions used for JES3 syslog (S#92SL3) ................................. 550
Scan definitions used for JES3 (S#92SJ3) ............................................ 551
Scan definitions used for EVT (S#92SEVT) ........................................... 553
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
539
Scan definitions
Overview
Overview
List of tables
The following tables contain a list of the definitions provided by _beta log|z
for scanning sysout.
The scan definitions are sorted by scan ID.
Identifier in title
The identifying number in the title of the scan definition indicates its range
of use.
Identifier
Scan definition is used for ...
Bnn
Both JES2 and JES3
2nn
JES2
3nn
JES3
Enn
Events
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
540
Scan definitions
Scan definitions identical for JES2 and JES3 (S#92SJ23)
Scan definitions identical for JES2 and JES3 (S#92SJ23)
ScanID TargetID Chain name ScannedList A/N Description
ID in title
1000
74
-
JESMSGLG
Y
Scan job not run IEFC452I. Set JCL
INIT error.
B01
1001
75
-
JESMSGLG
Y
Scan job failed IEF453I status.
Set JCL FAIL error if this message
occurs.
B02
1002
25
-
JESJCL
Y
Scan job message class
(MSGCLASS=)
B03
1003
11
-
JESYSMSG
Y
Scan step name with procstep
B11
(IEF142I). This definition gets the step
name if a procedure is used.
1004
11
-
JESYSMSG
Y
Scan step name without procstep
B12
(IEF142I). This definition gets the step
name if a procedure is not used.
1005
12
-
JESYSMSG
Y
Scan procstep name (IEF142I). This
definition gets the procstepname of a
job.
B13
1006
14
-
JESYSMSG
Y
Scan step condition code (IEF142I/
EXECUTED). This definition is gets
the step condition code of a job.
B14
1007
30
-
JESYSMSG
Y
Scan allocation errors (IEF21). This
definition creates a message record
for any allocation errors.
B15
1008
30
-
JESYSMSG
Y
Scan disk allocation errors (IEF25).
This definition creates a message
record for any disk allocation errors.
B16
1009
1
-
JESYSMSG
Y
Scan step name not run (IEF272I).
This definition gets the step name
although the step has not been
executed.
B17
1010
11
-
JESYSMSG
Y
Scan step name not run without
procstep (IEF272I). This definition will
get the step name of a job although
the step has not been executed.
B18
1011
12
-
JESYSMSG
Y
Scan procname not run (IEF272I).
B19
This definition will get the procname of
a procedure although the procstep has
not been executed.
1012
13
-
JESYSMSG
Y
Scan step text not executed (IEF272I)
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
B20
541
Scan definitions
Scan definitions identical for JES2 and JES3 (S#92SJ23)
ScanID TargetID Chain name ScannedList A/N Description
ID in title
1013
30
-
JESYSMSG
N
Scan "not cataloged 2" (IEF287I). This B21
definition will create a message record
if the message IEF287I is found in the
job log.
1014
28
-
JESYSMSG
N
Scan not cataloged error status
B22
(IEF287I). This definition will put a job
that ends with a "not cataloged 2" error
message in the Error queue.
1015
27
-
JESYSMSG
N
Scan not cataloged error text IEF287I/ B23
NOT CATLGD. This definition writes
the NOT CATLGD error text message.
1016
17
-
JESYSMSG
N
Scan CPU time in minutes
(IEF374I/STOP)
B24
1017
18
-
JESYSMSG
N
Scan CPU time in seconds
(IEF374I/STOP)
B25
1018
19
-
JESYSMSG
N
Scan SRB time in minutes
(IEF374I/STOP)
B26
1019
20
-
JESYSMSG
N
Scan SRB time in seconds
(IEF374I/STOP)
B27
1020
21
-
JESYSMSG
N
Scan virtual (IEF374I/STOP)
B28
1021
22
-
JESYSMSG
N
Scan highly virtual (IEF374I/STOP)
B29
1022
32
-
JESYSMSG
Y
Scan start date and time
(IEF375I/START)
B30
1023
33
-
JESYSMSG
Y
Scan end date and time
(IEF376I/STOP)
B32
1024
11
-
JESYSMSG
Y
B33
Scan step name with procstep
(IEF472I). This definition gets the step
name if a procedure is used.
1025
11
-
JESYSMSG
Y
B34
Scan step name without procstep
(IEF472I). This definition gets the step
name if a procedure is not used.
1026
12
-
JESYSMSG
Y
Scan procstepname (IEF472I). This
definition gets the procstepname of a
job.
B35
1027
15
-
JESYSMSG
Y
Scan system abend
(IEF472I/- SYSTEM)
B36
1028
16
-
JESYSMSG
Y
Scan user abend
B37
1029
1
-
JESYSMSG
N
Scan job start date (IEF472I/USER=)
B39
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
542
Scan definitions
Scan definitions identical for JES2 and JES3 (S#92SJ23)
ScanID TargetID Chain name ScannedList A/N Description
ID in title
1030
2
-
JESMSGLG
Y
Scan job start time (3/4) (IEF403I)
B40
1031
75
-
JESYSMSG
N
Scan duplicate DSN (IGD17101)
B42
1032
3
-
JESYSMSG
N
Scan job end date (IEF376I/STOP)
B43
1033
4
-
JESMSGLG
Y
Scan job end time (4/4) (IEF404I)
B44
1034
4
-
JESMSGLG
Y
Scan job end time (4/4) failed
(IEF453I)
B45
1035
74
-
JESMSGLG
Y
Scan job not run IEF452I
B46
1036
75
-
JESMSGLG
Y
Scan job cancel IEF251I
B47
1037
1038
1039
1040
1041
1042
1043
1044
800 /
021
022
023
024
017
018
019
020
IEF374
IEF374
IEF374
IEF374
IEF374
IEF374
IEF374
IEF374
JESYSMSG
Y
Y
Y
Y
Y
Y
Y
Y
SCAN VIRTUAL STORAGE
- Private memory
- High private memory
- Extended memory
- High extended memory
- CPU time minutes
- CPU time seconds
- SRB time minutes
- SRB time seconds
B56
B57
B58
B59
B60
B61
B62
B63
SCANID 1043 deactivates 1135
SCANID 1044 deactivates 1137
(from chain TSU-JSR). Reason:
IEF374I and IEF032I
1045
30
-
JESYSMSG
N
SCAN NOT CAT/ RECTL/ ROLL/UN
(IEF287I)
B64
1046
28
-
JESYSMSG
N
SCAN NOT CAT/ RECTL/ ROLL/UN
(IEF287I)
Job status set / reset
B65
1047
27
-
JESYSMSG
N
SCAN NOT CAT/ RECTL/ROLL/UN
(IEF287I)
Write job error text
B66
1060
1061
1062
800 /
JESYSMSG
030
IGD1710I
IGD1710I
IGD1710I
Y
Y
Y
Write DSN in offset 0
Write DSN in offset 7
Write "DUP IN CAT" in offset 55
(IGD17101I/DATA SET)
B69
B69
B69
800 /
030
030
030
ICH408T1
ICH408T1
ICH408T1
JESMSGLG
Y
Y
Y
1063
1064
1065
Write JMR:
*** JOB HAS RACF
Messages (ICH408I) ***
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
B70
B70
B70
543
Scan definitions
Scan definitions identical for JES2 and JES3 (S#92SJ23)
ScanID TargetID Chain name ScannedList A/N Description
ID in title
Y
Y
Y
Scan message for dump (IEA995I)
Write in offset 0 *** ABEND
Write abend code infos in offset 0
Insert a message record
B71
B71
B71
JESYSMSG
Y
SCAN ERROR IEC1 *13-RC
B72
-
JESYSMSG
Y
SCAN ERROR IEC1 *37-RC
B73
ICE***A
SYSO*
Y
SCAN ICE***A
(DFHSORT)
B74
Scan Waiting for data (IEF379I)
Set "WAITING FOR" in offset 0
Write DSN in offset 20
B74
B74
1067
1068
1069
800 /
030
030
030
IEA995I
IEA995I
IEA995I
JESYSMSG
1070
030
-
1071
030
1072
800 /
030
1073
1074
800 /
000
030
IEF863I
IEF863I
JESMSGLG
Y
Y
1075
030
-
JES*
Y
Scan message IEF379I
Write CATALOG ERROR in JMR
1076
Not used at present
(Deleted in V4R5)
1077
Not used at present
(Deleted in V4R5)
B76
1078
04
-
JESMSGLG
Y
Scan JOB FAILED IEF451I
B79
1079
75
-
JES*
Y
Scan IEF378I - JOB FAILED
- Set error status to YES
B80
1080
28
-
JES*
Y
Scan IEF378I
- Set error status to YES/RESET
B81
1081
75
-
JES*
Y
Scan IEF379I
- Set error status to YES
B82
1082
28
-
JES*
Y
Scan IEF379I
- Set error status to YES
B83
1083
1084
1085
1086
1087
1088
1089
1090
800 /
027
027
IEF287
JESYSMSG
Y
Y
Y
Y
Y
Y
Y
Y
Scan NOT CATLG 2
IEF287I
B84
1092
04
Y
Scan job failed
Message IEF450I
030
-
JESMSGLG
Write a message record
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
B85
544
Scan definitions
Scan definitions identical for JES2 and JES3 (S#92SJ23)
ScanID TargetID Chain name ScannedList A/N Description
1093
1094
1095
1096
1097
1098
1099
1100
ID in title
Not used at present
(Chains IEF450-U and IEF450-S,
deleted with POM3116 for V4R5)
1101
1102
1103
1104
1105
1106
1107
1108
Not used at present
(Chain ICH408T1 deleted with
POM3321 for V4R5, and with
POM6129 for V6R1)
Not used at present
1109
1110
1111
1112
1113
1114
1115
1116
(Chain ICH408T3 deleted with
POM3321 for V4R5, and with
POM6129 for V6R1)
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
800
- 017
- 017
- 017
- 017
- 018
- 019
- 019
- 019
- 020
- 021
- 022
- 023
- 024
1130
33
IEF032
JESYSMSG
JESYSMSG
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
- from z/OS 1.12 (IEF032I)
CPU time minutes JSR
B91
CPU time seconds JSR
SRB time minutes JSR
SRB time seconds JSR
Priv. storage JSR
Priv. storage JSR
Ext. storage JSR
Ext. storage JSR
- from z/OS 1.12 (IEF033I)
Scan job end date / time
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
B92
545
Scan definitions
Scan definitions identical for JES2 and JES3 (S#92SJ23)
ScanID TargetID Chain name ScannedList A/N Description
ID in title
1131
B93
52
-
JESMSGLG
Y
Scan current date:
1. In JES2:
09.55.04 J0035654 ---- THURSDAY,
04 NOV 2010 ---2. In JES3:
17:06:30 ---- IAT6853 THE CURRENT
DATE IS MONDAY, 02 AUG 2010 ---
1132
53
-
JESMSGLG
Y
Scan the last time in JESMSGLG
B94
1133
53
-
JESMSGLG
Y
Scan the last time in JESMSGLG
B95
1134
1135
1136
1137
800024
-024
-024
-024
TSO-JSR
JESYSMSG
Y
Y
Y
Y
Missing IEF032I message in the TSO
session – i.e. missing JSR
(IEF142I/IEF472I)
B96
1138
1139
1140
1141
1142
800036
- 036
- 036
- 036
- 037
IEF033
JESYSMSG
Y
Y
Y
Y
Y
CPU time (hours, minutes and
seconds) in the JBR fields
JBRCPUTM and JBRCPUTS
B96
1200
70
-
JESJCL
Y
Scan OMS NOSAVE card
B04
1201
70
-
JESJCL
Y
Scan OMS NOSAVE in procedure
B47
1202
71
-
JESJCL
Y
Scan OMS SAVE card
B05
1203
71
-
JESJCL
Y
Scan OMS SAVE in procedure
B92
1204
9
-
JESJCL
Y
Scan OMS HICC card
B06
1205
9
-
JESJCL
Y
Scan OMS HICC in procedure
B49
1206
8
-
JESJCL
Y
Scan OMS RETPD card
B07
1207
8
-
JESJCL
Y
Scan OMS RETPD in procedure
B50
1208
6
-
JESJCL
Y
Scan OMS USER card
B08
1209
6
-
JESJCL
Y
Scan OMS USER in procedure
B51
1210
7
-
JESJCL
Y
Scan OMS NET card
B09
1211
7
-
JESJCL
Y
Scan OMS NET in procedure
B09
1212
30
-
JESJCL
N
Scan OMS COM card
B10
1213
30
-
JESJCL
N
Scan OMS COM in procedure
B53
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
546
Scan definitions
Scan definitions identical for JES2 and JES3 (S#92SJ23)
ScanID TargetID Chain name ScannedList A/N Description
ID in title
1214
30
-
JESJCL
Y
Scan OMS MSG card
B38
1215
30
-
JESJCL
Y
Scan OMS MSG in procedure
B54
1216
30
-
JESJCL
Y
Scan OMS SAVE card
B31
1217
30
-
JESJCL
Y
Scan OMS SAVE in procedure
B55
1218
500
-
JESJCL
Y
GET OMS DOC
B89
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
547
Scan definitions
Scan definitions used for JES2 (S#92SJ2)
Scan definitions used for JES2 (S#92SJ2)
ScanID TargetID Chain name ScannedList A/N Description
ID in title
2000
10
-
JESMSGLG
Y
Scan JES2 job class
($HASP373/CLASS).
201
2001
800/26
CH1
JESMSGLG
Y
Scan JES2 job system ID for STC
(J E S 2 J O B L O G).
202
2002
74
-
JES*
Y
Scan JES2 cancel before execution
($HASP106). This definition sets JCL
INIT error status if a job is canceled
before execution.
203
2003
30
-
JESMSGLG
Y
Scan JES2 authorization error
(IEF722I). This definition writes the
reason for the authorization error in a
job message record.
204
2004
28
-
JESMSGLG
Y
Scan JES2 authorization error status
(IEF722I). This scan definition puts a
job which ended with an authorization
error in the Error queue.
205
2005
27
-
JESMSGLG
Y
Scan JES2 authorization error text
(IEF722I). This definition writes the
NOT AUTH error text message.
206
2006
101
-
JESMSGLG
Y
Scan JES2 get userID IRR010I 207
207
2007
34
-
JESMSGLG
Y
Scan JES2 SRVCLASS for WLM
($HASP373 - SRVCLASS)
208
2008
800/007
CH2
JESMSGLG
Y
Scan note for JES2 jobs (J O B L O G) 209
2009
04
-
JESMSGLG
Y
SCAN JES2 $HASP395
(end time of the job)
210
2010
26
-
JESMSGLG
Y
Scan SYSTEM- ID for JES2 job
($HASP373)
211
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
548
Scan definitions
Scan definitions used for JES2 syslog (S#92SL2)
Scan definitions used for JES2 syslog (S#92SL2)
ScanID TargetID Chain name ScannedList A/N Description
ID in title
2500
800/122
JES200D
*
Y
Set job submit time to 00:00:00
213
2501
800/121
JES200T5
*
Y
Scan time for DD name of syslog list
(2-digit year date mask)
212
2502
800/121
JES200T7
*
Y
Scan time for DD name of syslog list
(4-digit year date mask)
212
2503
800/120
JES200N
*
Y
Scan SMF ID for job name SYSLxxxx
209
2504
800/26
JES2-SYS
*
Y
Scan system ID
215
2505
800/163
JES200I
*
N
Scan SMF ID for job ID SYSLxxxx
216
2506
800/163
JES200I
*
N
Scan SMF ID for job ID SYSLxxxx
217
Multiple JES spools
Also activate the definitions with scan ID 2505 and 2506 when you are
processing the z/OS syslogs of different from multiple JES spools via NJE.
These scan definitions are available as of V7R2-02. When active, the
job ID Snnnnnnn is replaced by _beta log|z with SYSLxxxx, where xxxx is
the 4-digit SMF ID of the z/OS image (like job name). This ensures that
generated keys are unique even if nnnnnnn is identical.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
549
Scan definitions
Scan definitions used for JES3 syslog (S#92SL3)
Scan definitions used for JES3 syslog (S#92SL3)
ScanID TargetID Chain name ScannedList A/N Description
ID in title
3500
800/122
JES300D2
*
N
Scan syslog date for two-digit year
date masks
324
3501
800/122
JES300D4
*
N
Scan syslog date for four-digit year
date masks
322
3502
800/121
JES300T2
*
N
Scan time for DD name of syslog list
321
3503
800/120
JES300N
*
N
Scan SMF ID for jobname SYSLxxxx
(example, adjust to your environment)
320
3504
800/120
JES301N
*
N
Scan SMF ID for job name SYSLxxxx
(example, adjust to your environment)
320
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
550
Scan definitions
Scan definitions used for JES3 (S#92SJ3)
Scan definitions used for JES3 (S#92SJ3)
ScanID TargetID Chain name ScannedList A/N Description
ID in title
3000
7
-
JESJCL
Y
Scan JES3 net ID.
301
3001
30
-
JESMSGLG
Y
Scan JES3 authorization error
(IEF722I). This definition writes the
reason for the authorization error in a
message record.
302
3002
28
--
JESMSGLG
Y
Scan JES3 authorization error status
(IEF722I). This definition puts a job
which ended with an authorization
error in the Error queue.
303
3003
27
-
JESMSGLG
Y
Scan JES3 authorization error text
(IEF722I). This definition writes the
NOT AUTH error text message.
304
3004
35
-
JESMSGLG
Y
Scan JES3 system ID
(IAT2000/SELECTED).
305
3005
34
-
JESMSGLG
Y
Scan JES3 group ID (IAT2000/GRP=). 306
3006
30
-
JESMSGLG
Y
Scan JES3 job canceled (IAT2006/
CANCELED).
307
3007
28
-
JESMSGLG
Y
Scan JES3 job canceled status. This
definition puts a job that ended with a
"canceled error" in the Error queue.
308
3008
27
-
JESMSGLG
Y
Scan JES3 job canceled text. This
scan definition writes the CANCELED
error text message.
309
3009
30
-
JESMSGLG
Y
Scan JES3 DSN not found (IAT4404).
This definition creates a message
record if a dataset is not found.
310
3010
30
-
JESMSGLG
Y
Scan JES3 JCL errors (IAT420). This
definition creates a message record if
a JCL error occurs.
311
3011
74
-
JESMSGLG
Y
Scan JES3 JCL errors in error text
(IAT420). This definition will set the
JCL INIT error if a JCL error occurs.
312
3012
74
-
JESMSGLG
Y
313
Scan JES3 express canceled
(IAT4801). This definition will set the
JCL INIT error if the IAT9201 message
is found in the job log.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
551
Scan definitions
Scan definitions used for JES3 (S#92SJ3)
ScanID TargetID Chain name ScannedList A/N Description
ID in title
3013
30
-
JESMSGLG
Y
Scan JES3 oper issued canceled
314
(IAT5550/CANCEL). This definition will
create a message record if a cancel is
executed.
3014
28
-
JESMSGLG
Y
Scan JES3 oper issued canceled text.
This definition writes the CANCEL
error text message.
315
3015
27
-
JESMSGLG
Y
Scan JES3 oper issued canceled text
This definition writes the CANCEL
error text message.
316
3016
74
-
JESMSGLG
N
Scan JES3 job card error (IAT6130).
This definition sets the JCL INIT error
if the job card was coded incorrectly.
317
3017
101
-
JESMSGLG
Y
Scan JES3 get USERID (IRR010I)
318
3018
34
-
JESMSGLG
y
SCAN JES3 SRVCLASS for WLM
(IAT2000)
319
3019
30
-
JESMSGLG
Y
SCAN JES3 message IAT4410
320
3020
30
-
JESMSGLG
Y
Scan JES3 JOB not run IAT442
331
3021
74
-
JESMSGLG
Y
Scan JES3 JOBCARD error (IAT613)
332
3022
30
-
JESMSGLG
Y
IAT5550 OPERATOR ISSUED
CANCEL
333
3023
28
-
JESMSGLG
Y
IAT5550 OPERATOR ISSUED
CANCEL
334
3024
27
-
JESMSGLG
Y
IAT5550 OPERATOR ISSUED
CANCEL
335
3025
3026
3027
3028
3029
3030
800/030
000
000
000
000
030
JESMSGLG
Y
Y
Y
Y
Y
Y
SCAN MSG IAT440* JES3
IAT4401: the DSN and STEP name
will be stored
IAT4404: a message record with the
respective values will be written.
336
3031
035
JESMSGLG
Y
SCAN JES3 SYSTEM ID for message 337
IEA630I
3032
035
JESJCL
Y
SCAN JES3 SYSTEM ID for STC
(IEFC653I)
338
3033
3034
800/
JESMSGLG
Y
Y
Scan IEF450I for JES3 Failed
(REASON=0000050)
339
REASON-5
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
552
Scan definitions
Scan definitions used for EVT (S#92SEVT)
Scan definitions used for EVT (S#92SEVT)
ScanID TargetID Chain name ScannedList A/N Description
ID in title
9201
550
-
B92EVT
Y
Scan line from DDNAME B92EVT
(table EVT00)
E01
9202
550
-
JESJCL
Y
Get OMS EVT card
E02
9203
550
-
EQQMLOG
N
Scan SRSTAT special resource
(EQQZ015I)
E03
9204
550
-
JESMSGLG
Y
Scan B92 program ended (OMS1026I) E04
9206
550
-
JESJCL
Y
Get OMS LNK card
E06
9207
550
-
JESJCL
Y
Get OMS DSN= card
E07
9209
550
-
SCRIPT
Y
Get OMS EVT card for FILE SCRIPT
E08
9210
552
-
B92EVT
Y
Message structure:
E09
+ nnnnn s event text
where nnnnn is the event ID and s is
the severity (I, W, or E)
9211
550
-
MAILOUT
9220
800/550
TWS-OCCU JESJCL
Y
Generate mail trigger event (ID=9225) E11
if OMSMAIL eyecatcher is present
Y
Get IWS application from JESJCL
E20
TWS-OCCU chain retrieves values
from TWS occurrence information in
JESJCL, for example:
//*>< TWS OCCURRENCE --> DEVAPP
020 1311050201
This information is only present if
ITOM(YES) is set in the JTOPTS
statement of IWS.
9221
800/550
TWS-OCCU JESJCL
Y
Get IWS operation number from TWS
occurrence info
E20
9222
800/550
TWS-OCCU JESJCL
Y
Get date mask for IWS input arrival
E20
9223
800/550
TWS-OCCU JESJCL
Y
Get year of IWS input arrival date from E20
TWS occurrence info
9224
800/550
TWS-OCCU JESJCL
Y
Get month of IWS input arrival date
from TWS occurrence info
E20
9225
800/550
TWS-OCCU JESJCL
Y
Get day of IWS input arrival date from
TWS occurrence info
E20
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
553
Scan definitions
Scan definitions used for EVT (S#92SEVT)
ScanID TargetID Chain name ScannedList A/N Description
ID in title
9226
800/550
TWS-OCCU JESJCL
Y
Get time format for IWS input arrival
time
E20
9227
800/550
TWS-OCCU JESJCL
Y
Get hours of IWS input arrival time
from TWS occurrence info
E20
9228
800/550
TWS-OCCU JESJCL
Y
Get minutes of IWS input arrival time
from TWS occurrence info
E20
9230
800/550
TWS-OCC2
Y
Get IWS application from SCRIPT
E21
SCRIPT
TWS-OCC2 chain retrieves values
from TWS occurrence information in
SCRIPT, for example:
//*>< TWS OCCURRENCE --> DEVAPP
020 1311050201 WS48
This information is added by _beta
job|z.
9231
800/550
TWS-OCC2
SCRIPT
Y
Get IWS operation number from
TWS occurrence info
E21
9232
800/550
TWS-OCC2
SCRIPT
Y
Get date mask for IWS input arrival
E21
9233
800/550
TWS-OCC2
SCRIPT
Y
Get year of IWS input arrival date from E21
TWS occurrence info
9234
800/550
TWS-OCC2
SCRIPT
Y
Get month of IWS input arrival date
from TWS occurrence info
E21
9235
800/550
TWS-OCC2
SCRIPT
Y
Get day of IWS input arrival date from
TWS occurrence info
E21
9236
800/550
TWS-OCC2
SCRIPT
Y
Get time format for IWS input arrival
time
E21
9237
800/550
TWS-OCC2
SCRIPT
Y
Get hours of IWS input arrival time
from TWS occurrence info
E21
9238
800/550
TWS-OCC2
SCRIPT
Y
Get minutes of IWS input arrival time
from TWS occurrence info
E21
9239
800/550
TWS-OCC2
SCRIPT
Y
Get workstation from TWS occurrence E21
info
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
554
Questions and answers
Questions and answers
Frequently asked
questions (FAQs)
In this chapter you find answers to questions that are frequently asked by
users of _beta log|z.
Question:
How can I print the "Job Select Table"?
Answer:
Enter the primary command TPRINT in the command line of the "Job
Select Table".
TPRINT prints only the columns of the "Job Select Table" that are currently
displayed.
Question:
How can I prevent a single job with a high condition code being put onto
the Error queue?
Answer:
Use the OMS control card //*OMS HICC.
Question:
When jobs are processed via sysout classes, why does the "Job Select
Table" not display the name of the job group for which processing via
sysout class was defined?
Answer:
The job group which is valid for selection and display of a job is the one
the job belongs to because of its name.
Question:
Is it possible to change the attributes of function keys?
Answer:
Yes. Enter the primary command KEYS in the command line of the Beta
Browser. You will receive a table displaying the function keys and the
commands that are attributed to each of them. Now you may change these
according to your needs. This will have no effect on the ISPF attributes of
the function keys.
Question:
How can I send a job to _beta log|z and to the printer at the same time?
Answer:
Assign two sysout classes to the job via the JES OUTPUT card.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
555
Questions and answers
Question:
What happens to the jobs in the online spool when the sysout class
attributes are changed from SAVE to NOSAVE or vice versa?
Answer:
The change applies to all jobs which are currently in the online spool. If the
status of the sysout class was changed from SAVE to NOSAVE, jobs
which are already in the spool and should be archived can be "kept" with
the line command K in the "Job Select Table". This command changes the
status of the job it is used on from NOSAVE to SAVE.
If the status of the sysout class was changed from NOSAVE to SAVE, you
can undo this with the line command X in the "Job Select Table" when the
jobs are in the spool already but are not to be archived. This command
changes the status of the job it is used on from SAVE to NOSAVE.
Question:
How long do reloaded lists stay online?
Answer:
The online retention period of reloaded lists is set according to the default
specified in the global options (Option A.S.3).
Question:
How can I print a job from _beta log|z to a z/OS dataset?
Answer:
Enter line command P in the "Job Select Table" or in the "Job Information
Table" and choose Print Type=Batch in the following "Print
Characteristics" panel. Specify a dataset that already exists. When you
start the B92PRINT, you may enter a name in the SYSUT2 card, too.
Question:
Is it possible to delete a sysout class?
Answer:
It is possible, but we recommend that you delete a sysout class only when
no more jobs or lists are online in that class. Otherwise, these jobs/lists
cannot be archived or deleted from the spool.
Question:
What does the attribute "Class Processing Active" in the sysout class
definition mean?
Answer:
It means that for this output class, all jobs and their lists are to be
processed as defined in the job group entered in the field Class
Processing Job Group.
You can control job processing according to sysout class criteria. In this
case, a specified job group has to be entered without job mask in the
sysout class definition and Class Processing Active must be set to Yes.
Class Processing Active=Yes activates processing via sysout class.
If Class Processing Active=No is entered, jobs are processed according
to the criteria defined in the job group that the job belongs to because of its
job name.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
556
Questions and answers
Question:
How can I delete a spool file?
Answer:
Change the status of the spool file to Data Set Status Readonly=Yes
(option A.D.1). No more lists are written to this file after that. When the
online retention periods of all lists on the spool file are expired, and the list
cleanup job has deleted all lists, the spool file gets the status EMPTY. It
can then be deleted with line command D.
Caution: You cannot use the ISPF online application to delete a spool file
when you are using the BQL share option. Use the program BST05CMD
instead (see "Notes on model spool file definitions" in BSA Installation and
System Guide).
Note: Read-only spool files are always checked at startup to ensure the
deletion of unused reader blocks, irrespective of the value of the LST
parameter BQL_SPOOLCHECK.
Question:
Is it possible to enter generic user IDs for the Sendgroup so that more than
eight users get the error messages?
Answer:
No. The messages are sent via the TSO SEND command which does not
allow generic user IDs. The user IDs have to be fully qualified.
Question:
How can I deactivate the current scanning parameters?
Answer:
You can activate and deactivate scanning parameters in the "Scan
Definition Table" (Option A.R.3). Line command A toggles the status from
active to inactive and back. Use the line command D if you want to delete
scanning parameters altogether. You have to stop and restart the _beta
log|z readers (F stcname,RES RDR) for any changes to take effect.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
557
Glossary of terms
Glossary of terms
accounting key
_beta log|z can be used for accounting. The basis for client-based billing is
a special key that can be specified when the EJM agents or SAP accounts
are defined. In addition to the client-based billing key, the SMF record will
then contain information on the file name, the file size and the source.
Using these data, the customer can bill the costs for _beta log|z to the
appropriate departments or users.
agent
For Unix/Windows/Linux environments, an agent determines where a file
rule is to be processed. The address where the agent can be found must
be entered. An agent can process file rules and SAP rules.
The agent can only process SAP rules when an SAP server has been
defined. In addition, an SAP account is needed to be able to log on to an
SAP system.
agent group
Agents can be organized into agent groups.
If you need to transfer files with the same name from different systems,
you can use an agent group.
archive definition
In an archive definition, you define an archive pool with an archive
retention period and an archive medium. During archiving, jobs are
assigned to archive pools depending on their archive retention period as
specified in the job group definition.
archive medium
For an archive definition, you have to specify an archive medium. You can
archive to tape, disk, or optical disk (FileTek).
archive pool
Various archive pools can be defined by means of a group name. An
individual retention period can be assigned to each group. During
archiving, jobs are assigned to archive pools depending on their archive
retention period as specified in the job group definition.
BQL
BQL (Beta Query Language) is the language used for creating, updating,
and querying the relational databases used by Beta Systems products.
certificate
Certificates are used as a means of authenticating communication
partners.
Your public certificate contains your public key and your name. It also
includes information on the issuer of the certificate.
Sending a certificate with a public key requires access to the matching
private key.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
558
Glossary of terms
cleanup
The job and list cleanup utilities delete jobs and lists whose online
retention period has expired from the database. Jobs and lists with SAVE
status are not deleted unless they have already been archived.
database
The _beta log|z databases are VSAM ESDS organized. They contain all
information about jobs read in, archive information and pointers to the
spool datasets where the lists of the processed jobs are located.
dataset record
A dataset record is automatically generated whenever an archive job
writes data to a tape archive volume. The dataset record contains
information about the expiration date of the volume, the number of files on
the volume and a sequential number. Dataset records can be viewed
under online option A.A.2.
dual archival
_beta log|z offers the possibility to duplicate archive datasets. This
safeguards against loss of data due to media failure.
During the archive run, each archive dataset is written to two archive
media at the same time. You can archive to tape, disk, or optical disk
(FileTek). You can use the same or different archive media for the primary
copy and the secondary copy of the archive.
endless file
Endless files are files into which data will continue to be written.
endless log
Endless-type file operations process ASCII files in Unix/Windows
environments. The assumption is that data will continue to be written into
these logs. Endless logs are logs from Unix applications, for example.
expiration date
The expiration date of an archive volume is the date when it is released to
be used again and the current information on the volume is deleted. This
date is calculated out of the current date plus the number of days for the
archive retention period as specified in the archive pool definition. Each
time an archive job writes data to an archive volume, this date is set higher
according to the archive pool specifications.
field
A field is an area of a database record into which a particular item of data
is entered.
file list
Any list of a file coming from a Windows, Linux, or Unix system.
generation
The retention period of a job can be defined in calendar days or in
generations. Generations relate to the job name. When a job runs three
times, for example, it creates three generations.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
559
Glossary of terms
high water mark
The high water mark value of a database is its warning level for used
space (in percent). If you work with dynamic databases, the system
extends the database before this critical value is reached. If you don't work
with dynamic databases, the system writes warning messages to the
console when used space in a database has reached its high water mark:
OMS9550W HIGH WATER MARK REACHED nn%/dsname
job group
A job group is a collection of jobs with similar properties. Job groups are
used for selecting jobs online, defining online and archive retention
periods, and protecting access to confidential jobs (security).
Jobs are assigned to job groups based on the job name or on the
message class. When jobs are assigned to job groups via the job name,
the assignment can be based on inclusion (jobs whose name matches a
given mask belong to a group) or on exclusion (jobs whose name does not
match a given mask belong to a group).
job group ID
Job group name.
Job Information Table
(JIT)
The Job Information table displays detailed information on a job (online
option 1, line command S).
The Job Information table displays a summary of job information,
including: error messages (if any), step condition codes, how many steps
were taken for completion, and a list of available sysout datasets.
job (base) record
A job (base) record contains all job information like the date and time when
the job was submitted, the job name and JES ID and the names of the
sysout lists produced by the job. Job base records are stored in the JOB
database.
key field
A field of a relational database table which, alone or together with other
key fields, forms a unique identifier for a record (a table entry). The
aggregate of these fields is usually referred to simply as "the key".
label
A label is a symbolic name that can be assigned to a text passage when
you display a list in the Beta Browser. You can display a list of all labels
and jump to the respective page directly. This facilitates information
retrieval out of a list.
log
Job, started task, or TSO user whose system output is processed by _beta
log|z in the same manner as z/OS system logs. Logs are marked by an L
in the Status column of the Job Select table.
Logs are Windows/Linux/Unix file lists as well as SAP logs and SAP
definition files.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
560
Glossary of terms
menu
ISPF panels for the selection of ISPF functions are called "menu" or
"selection menu".
message class
(MSGCLASS)
The MSGCLASS parameter in the JCL designates the output class for the
job logs or JES lists (JESMSGLG, JESJCL, JESYSMSG). If the
MSGCLASS is an output class processed by _beta log|z, detailed job
information like step completion codes, etc., can be displayed in the Job
Information table.
normal log
Normal-type file operations process ASCII files in Unix/Windows
environments. The assumption is that data will not continue to be written
into these files. This means that the files are created and then normally not
changed. These files can be created via a Job Scheduling system and will
then be job-related.
OMS control cards
OMS control cards can be inserted in the JCL to control processing
options when the job comes into _beta log|z. This includes for example the
setting of a retention period, condition code processing, or assigning the
job to a job net.
Open Systems log
Open Systems logs are Windows/Linux/Unix file lists as well as SAP logs
and SAP definition files.
operation
An operation determines what is to be processed. This can be either a file
operation or an SAP operation.
An operation can be the transfer of a file or log (normal log, endless log, or
Windows event log) or the transfer of an SAP job (including its job
definitions, job logs, and spool lists) or the transfer of an SAP system log.
•
File operations:
Normal Unix/Windows logs, endless Unix/Windows logs, Windows
event logs
•
SAP operations:
SAP jobs (including its job definitions, job logs, and spool lists), SAP
system logs
panel
An ISPF panel is a screen mask with user input fields.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
561
Glossary of terms
PKI
Public Key Infrastructure (PKI) is a method for issuing, distributing, and
checking digital certificates assigned to a person or a machine.
Asynchronous encryption for public and private keys is used. A certificate
confirms the assignment of a key to a person or a machine. The certificate
itself is created by a certificate authority (CA), also sometimes referred to
as a certification authority. The key contains information on a person or a
machine as well as a public key part.
A PKI may contain certificate authorities, registration authorities, a
certificate management service, and X.500 directories. A PKI verifies the
identity of each party involved in a transaction. Examples of these
transactions include confirming the origin of proposal bids or the author of
e-mail messages.
A PKI supports the use of certificate revocation lists (CRLs). A CRL is a list
of revoked certificates. CRLs provide a more universal method for
authenticating client identity by certificate and can verify the validity of
trusted CA certificates. An X.500 directory server stores and retrieves
CRLs and trusted CA certificates. The protocols used for storing and
retrieving information from an X.500 directory server include Directory
Access Protocol (DAP) and Lightweight Directory Access Protocol (LDAP).
queue
Jobs are assigned to job queues, which indicate the status of the job and
other characteristic features.
record
An ordered set of fields in a database table (also called row).
reload
Archived information that is no longer available online must be reloaded
first before you can display it online.
retention period
The retention period indicates the number of days job logs and sysout list
are to be kept either online or in the archive. You indicate retention periods
in the job groups.
The online retention period determines how long you may view information
about a particular job online. It is defined in workdays or in generations.
The archive retention period indicates the number of calendar days for
which the data is to be stored on the archive media.
rule
A rule combines what is to be processed, when, how often, where, and
with what it is to be processed.
The What (operation), When and how often (run cycle), Where (agent/SAP
server), and With what (SAP account for SAP rules) are grouped into a file
rule or into an SAP rule.
rule group
Rules can be organized into rule groups. Rule groups can be, for example,
file rule or SAP rule groups.
run cycle
A run cycle determines at what time and how often a rule is executed.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
562
Glossary of terms
SAP account
For SAP environments, the agent needs to know the SAP account to be
able to log on to an SAP server and to process SAP rules.
SAP job log
JOBLOG-type SAP operations process SAP batch jobs via the XBP
interface. Job spool lists can be processed as well as job logs.
SAP log
Any SAP job log coming from an SAP job.
SAP server
For SAP environments, an SAP server determines where an SAP rule is to
be processed.
The TCP/IP address where the SAP server can be found must be entered,
and an agent must be selected.
SAP system
The SAP system combines the SAP server and the SAP account.
SAP system log
SYSLOG-type SAP operations process SAP system logs. They are not
processed via the file system, as in endless file operations, but via SAP's
XMB interface.
selection menu
ISPF panels for the selection of ISPF functions are called "menu" or
"selection menu".
separator
Separator pages are printed before and after the output of a job. These
pages contain, for example, job name and JES ID. In addition, they can
contain distribution information indicating to the printer operator what is to
be done with the printed output.
smart card
A smart card is a pocket-sized card with an embedded microchip. Smart
cards can employ a public key infrastructure (PKI).
Smart cards can be used for authentication. When inserted into a smart
card reader, and a PIN has been entered, the smart card transfers data to
and from a central computer.
spool dataset
Spool datasets are VSAM ESDS datasets which hold the sysout lists of the
jobs processed by _beta log|z.
A new spool file is allocated based on a model spool files when all existing
spool files are full.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
563
Glossary of terms
SSL
Secure Sockets Layer (SSL), and its successor, Transport Layer Security
(TLS), are communication protocols that provide data privacy and integrity
between a client and a server over internet/intranet networks.
SSL/TLS addresses the following security considerations.
•
Authentication: When a client initiates communication with a server
over a secure connection, the server presents a set of credentials. The
public certificate of the server is the container that is used to send this
set of credentials. This certificate enables the client to verify that the
server is who and what it claims to be. This process is known as
server authentication. The server may also request a certificate from
the client, so that the server can verify that the client is who and what it
claims to be. This process is known as client authentication.
•
Confidentiality: Encryption ensures that the data that is passed
between the client and the server cannot be deciphered by a third
party and that the data remains confidential.
•
Integrity: Encryption safeguards against data being modified in transit
by a third party.
SSL and TLS are often used interchangeably, where one implies the other.
The protocols SSLv1/SSLv2/SSLv3 are widely considered to be obsolete
and should not be used anymore. Secure connections should always use
TLS instead of SSL.
started task
A started task is a z/OS batch procedure which with a z/OS start command
is called up directly from a system console and does not need a job card.
Like a job or a TSO user, a started task runs in its own z/OS address
space.
subsystem ID
The subsystem ID is determined at the time of the installation of _beta
log|z, and may be up to 4 characters in length.
sysout class
_beta log|z can process up to eight sysout classes. If you activate class
processing for a sysout class, all jobs of this class are assigned to a
specific job group.
table
A collection of records in a relational database.
TLS
See SSL.
tutorial
A tutorial is an ISPF help panel which can be called with the HELP
command (usually assigned to function key PF1). It contains explanations
concerning the panel which it was called from.
user profile
The user profiles contains user-specific defaults which are used whenever
a user invokes _beta log|z. The user parameters include, for example,
screen attributes, tutorial language, and defaults for print requests.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
564
Glossary of terms
Windows event log
Windows event logs can be compared to endless logs. The assumption is
that data will continue to be written into these files.
_beta log|z offers the possibility to archive Windows event logs, such as
system logs, security logs, application logs.
word
String of one or more characters delimited by non-alphanumeric
characters. Valid delimiters are, for example, blank, period, hyphen, colon,
beginning of line, and end of line.
Sysout scanning uses only three word delimiters: beginning of line, blank,
and end of line.
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
565
Index
Index
Symbols & Numeric
B92AGINF
398
_beta view links
B92ARPRI
175, 199, 400
B92ARSEC
175, 406
B92BCAPI
409
B92BFJBR
415
B92BFJGI
419
B92CLAR2
421
B92CLARC
175, 424
B92CLARS
429
230, 322, 323, 339
A
activating agents
149
Administration Selection Menu
56
agents
activating
149
agent definitions
agent groups
144
142
agent rule cleanup
429
B92CLEVT
434
agent rule statistics
429
B92CLLST
119, 175, 437
B92CLREO
441
agent rule status information
182, 183
agent rule status level
185
B92DAILY
175, 442
agent rule status table
186
B92DBVER
444
refreshing
B92DEF
149
ARCH.DATA and ARCH.KEY database
346
ARCHINF.DATA and ARCHINF.KEY database
346
472
B92FFIND
446, 453
B92FFIND (syslog search)
B92MICRO
461
archive cleanup
424
B92MUPDT
464
archive datasets
203, 206, 212
B92PRINT
472
archive medium
103, 197, 203, 206, 212, 215
B92RDPS4
484
archive pointer
242
B92RLOAD
175
B92SENDL
488
B92SSRCH
497
archive pool
197, 199, 206, 212
archive pool for job groups
archive retention period
archive volume
archive, dual
197
193, 197, 199, 400
215
206
Archived job select table
archiving job output
archiving lists
237, 241
47, 48
193, 197, 199, 203, 400
B92STAT
346
b92syslog
165
B92WAIT4
515
B92WEEKL
520
batch reload
242
batch utilities
389, 391
457
ARCHyyyy.Gnn
346
B92ADR01
395
automatic reload
257
B92AGINF
398
B92ARPRI
175, 199, 400
B92ARSEC
175, 406
B92BCAPI
409
B92BFJBR
415
B
B92_CLARC_JOBDETAIL
B92_MULTI_ARCHIVE
B92ADR01
424
403
395
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
566
Index
batch utilities (continued)
database field
370
368
B92BFJGI
419
database key
B92CLAR2
421
database level check
B92CLARC
175, 424
database query
383
B92CLARS
429
database tables
363
B92CLEVT
434
database usage
350
B92CLLST
119, 175, 437
database usage statistics
B92CLREO
441
databases
B92DAILY
175, 442
components
346
B92DBVER
444
definition file
346
B92FFIND
446, 453
457
DEF.DATA
103, 193, 400
346
B92MICRO
461
default layout
B92MUPDT
464
deleting old GAR database
B92PRINT
472
dictionary
B92RDPS4
484
disk
B92RLOAD
175
dual archive
B92SENDL
488
dump
B92SSRCH
497
B92WAIT4
515
EDF sysout class
B92WEEKL
520
EIF
BC-XBP
108
Beta Query Language (BQL)
binary data
67
383
474
BSA Service Manager
388
362
206
197, 206
121
260
See Extended Index Facility (EIF)
endless file
161
endless log
136, 161
error condition
49
error queue
49, 122
events
C
318, 324
event default error
caching
event ID
359
cleanup batch utility B92CLARS
client archive pool
EVT.DATA and EVT.KEY database
346
EXT.DATA
51
condition code
49
conventions
72, 534
F
308
file rule definition sequence
control cards (//*OMS)
346
346
Extended Index Facility (EIF)
409
completion code
327
See also Windows event logs
103, 193, 400
COM (OMS keyword)
327
270
standard event IDs
429
CLNT.DATA and CLNT.KEY database
command API
177
E
168
best match principle
373
351, 355, 362, 371
dedicated pool
B92FFIND (syslog search)
444
47
26
D
file transfer
488
function keys
52
128
G
data compression
Data Mover
10, 346
See B92SENDL
data set status
371
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
GAR databases
See generation archive (GAR)
databases
GARE records
115, 421
567
Index
generation archive (GAR) databases
adding a new GAR database
195
180
deleting or reusing an empty GAR database
177
displaying generation index definitions (GIRs)
layout overview
65
line commands
26, 52, 54
list names
44
list transfer
488
log definition
220
log jobs
generation ID
220
315
315
log result layout
H
LOG.DATA
help panels
359
I/O-Request
I/O-Write
B92_AUTORLD_ENABLED
257
B92_AUTORLD_INTERVAL
257
B92_AUTORLD_REQUEST_LIMIT_HIGH
359
257
359
IBM Workload Scheduler
indexes, user-defined
ISPF application
44
LST parameters
49
I
I/O-Read
346
logical record length (LRECL)
52, 54
HICC (OMS keyword)
98
B92_AUTORLD_REQUEST_LIMIT_LOW
See IWS
B92_AUTORLD_SETTLE_COUNT
535
B92_AUTORLD_SSID
52, 54
IWS occurrences
B92_CLARC_JOBDETAIL
318
J
257
257
B92_AUTORLD_VERBOSE
IWS
257
257
424
M
JBREUFnn
535
JCL parameters
MAIN.DATA and MAIN.KEY database
44
masks
JES lists (JESJCLIN, JESMSGLG, JESJCL,
JESYSMSG)
JES spool
54, 106, 108
maximum logical record length (LRECL)
44
Message Output Facility (MOF)
43
mirror databases
44
MOF
121
job group definitions
103, 106
job group processing
117, 121
job groups, assigning jobs to
See Message Output Facility (MOF)
MSGCLASS parameter
44
MSGLEVEL parameter
44
N
108, 117, 118, 119
navigation in panels
52, 54
44, 187
navigation in tables
52, 54
job mask
108
NET (OMS keyword)
48
48
news panel
job output name
job record
44
103, 121
job result layout
98
JOB.DATA and JOB.KEY database
NoError table
308
normal log
136, 161
346
NOSAVE status
notify groups
layout field
59
NOSAVE (OMS keyword)
L
layout definition
461
346
job log
job net
44
305
microfiche batch utility B92MICRO
JES sysout (JESMSGLG, JESJCL, JESYSMSG)
job base record
346
48
103, 260
122
63
72
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
568
Index
O
rules
OMS control cards
OMSERROR
rule definitions
47, 48, 49, 50, 51
rule groups
401
online retention period
OPC
132
130
rule planned for execution
103, 114, 119, 230
rule plans
See IWS
run cycle
operations
125, 136
optical disk
206
outlim event
327, 331
140
S
SAP account
159
136, 168
260, 331, 334
SAP job log
output as log job
315
SAP jobs
168
SAP log
168
117
OUTPUT parameter
44
SAP rule definition sequence
P
SAP server
403
SAP spool list
primary archive
199
SAP system
primary commands
168
153
SAP system log
52, 54
primary selection menu
55, 56
SAP XBP
printing into _beta log|z
315
SAPI interface
PROF HL ON|OFF
26, 52, 54
Q
136, 168
168
264
SAVE (OMS control card)
SAVE status
R
274, 539
scan definition chain
scan definition test
reader class
260
reader net ID
260
scan group
reader subsystem ID
268, 274
270, 306
151, 219
scanning performance
260
268
re-archiving lists
203
scanning sysout
refreshing agents
149
scanning, case-sensitive
reload, automatic
257
scrolling in panels
reloading
289, 303
reloading from the archive
reload requests
247, 253
189, 242, 247, 253
52
search argument examples
230
search layout
report page length
230
search layout default
retention period
Service Manager
102
103, 114, 118, 119
89
SMF records
SMF record type 6
193, 197, 199, 400
retention period (online)
50, 230
SORT command
RETPD (OMS keyword)
50
sorting tables
362
special reload
236
149
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
488
388
retention period (archive)
RFALL
497
76, 79, 83
sending datasets to agent
91, 94
504
searching lists in online spool only
report date mask
result layout default
289
search function
230, 236
result layout
47
260
scan definitions
103
129
156
parallel archiving
queues
185
132
outlim processing
output class
132
223
241, 362
569
Index
spinned lists
W
480
spool files
346, 355, 357
SPOOLnn.DATA
SSID
346
See subsystem ID
SSL/TLS encryption for agents
started task (STC)
statistic batch report
376
54
Windows event logs
136, 161
YXT.DATA and YXT.KEY database
z/OS external writer
statistic database values
375
statistics on _beta log|z
191
statistics on database usage
346
43
z/OS subsystem interface
43
373
481
223
subsystem ID
SYNC.DATA
syslog
wildcard characters
Z
229
subsystem
230, 322, 323, 339
Y
144
43, 44
STC online print
SUBSYS print
Web Enabler links
223
346
315
syslog scanning
syslog-ng
457
165
sysout as log job
sysout class
315
121, 260
sysout class processing
sysout list
117
260
sysout scanning
268, 274, 289, 303
system database
371
system option
219
system parameter
219
tape, archiving on
206
T
target field IDs
274, 284, 287, 288
test status for scan definitions
270, 306
Tivoli Workload Scheduler for z/OS
TLS encryption for agents
TSO user
See IWS
144
315
tutorial
54
TWS
See IWS
U
Unix system log
136, 165
USER (OMS keyword)
49
_beta log|z (Beta 92) V7R2 Administrator Guide – December 15, 2022
570