production control system implementation guide€¦ · production control system implementation...

(COPYRIGHT © 1999, B I MOYLE ASSOCIATES, INC.)

BIM-FAQS/PCS is a proprietary product of B I Moyle Associates, Inc. It cannot bereproduced, changed, copied, or stored in any form (including, but not limited to, copieson magnetic media) without the express prior written permission of B I MoyleAssociates, Inc.

R

B I MOYLE ASSOCIATES, INC.

B I M - F A Q S / P C S

PRODUCTION CONTROL SYSTEM

IMPLEMENTATION GUIDE

Release 5.1

This documentation applies toRelease 5.1 of the program productBIM-FAQS/PCS.

Original Printing ................ 04/18/1999Last Revised....................... 04/18/2000

Implementation Guide iii

Contents

About This GuidePurpose .............................................................................................................................. ATG–1Organization...................................................................................................................... ATG–1Who Should Use This Manual ........................................................................................ ATG–2Publications ....................................................................................................................... ATG–3Related Publications......................................................................................................... ATG–4Conventions Used in This Manual................................................................................. ATG–5Diagnostic Procedures ..................................................................................................... ATG–6

Collecting Diagnostic Data....................................................................................... ATG–6Interpreting Diagnostic Data ................................................................................... ATG–7Calling Technical Support........................................................................................ ATG–7

Chapter 1: Introduction to BIM-FAQS/PCSWhat Is BIM-FAQS/PCS? ......................................................................................................1–1SYS$EVT PDS...........................................................................................................................1–5Converting from Version 3.4 or Earlier ................................................................................1–6

Using JCLCONV...............................................................................................................1–8Converting Event Information......................................................................................1–10Converting CA Schedules and Jobs .............................................................................1–12

Chapter 2: Storing JCLOverview ..................................................................................................................................2–1Accessing Members from JCL Sources .................................................................................2–4

Command Types for Submitting JCL ............................................................................2–6Using the BIM-FAQS/PCS PDS .....................................................................................2–7Managing the PDS............................................................................................................2–8Using ICCF......................................................................................................................2–10Using CMS Server ..........................................................................................................2–11Using BIM-EDIT .............................................................................................................2–12Using CA-VOLLIE .........................................................................................................2–14Using CA-DRIVER.........................................................................................................2–15Using CA-LIBRARIAN..................................................................................................2–16Using CA-PANVALET..................................................................................................2–17

iv BIM-FAQS/PCS

Using CONDOR............................................................................................................. 2–18Using VSE Library Members........................................................................................ 2–19Using the POWER RDR Queue.................................................................................... 2–20

Chapter 3: Activating the SchedulerOverview.................................................................................................................................. 3–1Preparing to Activate the Scheduler..................................................................................... 3–2

Adding Optional SVA Phases ........................................................................................ 3–2Activating BIM-FAQS/PCS Hooks ............................................................................... 3–3Additional Startup Options ............................................................................................ 3–6

Activating the Scheduler........................................................................................................ 3–7Overview........................................................................................................................... 3–7Where to Activate JCLSCHED ....................................................................................... 3–7Before Using JCLSCHED ................................................................................................ 3–9When JCLSCHED Is Activated .................................................................................... 3–11Detecting Messages When JCLSCHED Is Not Active............................................... 3–12

Managing the Scheduler ...................................................................................................... 3–13Scheduler Control Commands..................................................................................... 3–13Loading Events Into the Current Event File............................................................... 3–15Controlling Event Processing ....................................................................................... 3–18Initiating Interfaces Used by the Scheduler................................................................ 3–20Miscellaneous Commands............................................................................................ 3–21PCSLOG: Reducing Overhead to Improve Performance ........................................ 3–22

Chapter 4: Job GenerationOverview.................................................................................................................................. 4–1Job Terminology...................................................................................................................... 4–2JCL Jobstream Examples ........................................................................................................ 4–3

Overview........................................................................................................................... 4–3One-Step Job ..................................................................................................................... 4–3Multi-Step Job Without Nested Calls ............................................................................ 4–4Multi-Step Job with Nested Calls .................................................................................. 4–5Job with User Variable .................................................................................................... 4–6

Job Generation Commands.................................................................................................... 4–7Overview........................................................................................................................... 4–7Generating Jobs as Part of an Event Command........................................................... 4–9

Override Parameters............................................................................................................. 4–10Overview......................................................................................................................... 4–10Restarting Jobs................................................................................................................ 4–13Changing POWER Job Values...................................................................................... 4–15

Implementation Guide v

Overriding Device Assignments ..................................................................................4–17Changing UPSI, EXEC, PROC, and DATE Values.....................................................4–18Testing JCL ......................................................................................................................4–20Overriding User Variables ............................................................................................4–21

Reviewing JCL Before Submission......................................................................................4–23JCLTRACE Utility ..........................................................................................................4–23

Chapter 5: Defining System ConfigurationOverview ..................................................................................................................................5–1Defining BIM-FAQS/PCS Configuration.............................................................................5–2Defining Private User ID Options .........................................................................................5–4

Defining CMS Submit Defaults ......................................................................................5–4Defining Panel Defaults...................................................................................................5–6

Defining System Options........................................................................................................5–9Defining User ID Classes.................................................................................................5–9Defining System CMS Submit Defaults.......................................................................5–11Defining System Panel Defaults ...................................................................................5–13Defining CMS Server Defaults .....................................................................................5–16Defining Global Configuration Options......................................................................5–17Defining Batch Defaults for Global Configuration ....................................................5–20Defining User Class Configuration Options...............................................................5–24Defining Library Defaults .............................................................................................5–27Specifying Holiday and Cycle Definitions..................................................................5–29Listing Holiday Definitions by IDs ..............................................................................5–30Editing a Holiday ID......................................................................................................5–31Defining a Holiday ID ...................................................................................................5–32Updating a Cycle ID.......................................................................................................5–34Editing a Cycle ID ..........................................................................................................5–35Defining a Cycle .............................................................................................................5–36Updating a User Calendar ............................................................................................5–38Listing an Exception Date ID ........................................................................................5–39Defining an Exception ID ..............................................................................................5–40Accessing the CPUID NODEID Synonym Table .......................................................5–42Defining CPU ID Synonyms .........................................................................................5–43Specifying Dataset Exclusion........................................................................................5–44Specifying Dataset Logging Suppression....................................................................5–46Specifying Dataset Logging by Partition.....................................................................5–47Specifying Dataset Logging by Phase..........................................................................5–49Specifying Dataset Logging by VSE Job......................................................................5–50Including Datasets for Logging ....................................................................................5–51Excluding Datasets from Logging................................................................................5–52Defining Partner Node Names .....................................................................................5–53

vi BIM-FAQS/PCS

Chapter 6: Defining SecurityOverview.................................................................................................................................. 6–1Defining Initial Security ......................................................................................................... 6–3

Preliminary Security Considerations ............................................................................ 6–3Accessing BIM-FAQS/PCS Security ............................................................................. 6–5Defining Your Security Administrator........................................................................ 6–10Modifying the $DEFAULT User ID............................................................................. 6–11Defining Security Rules for All Other Users .............................................................. 6–12

Defining the Rest of Security ............................................................................................... 6–15Defining User ID Classes .............................................................................................. 6–15Defining Member-Level Security................................................................................. 6–18Defining Event Group Security.................................................................................... 6–22Defining Event-Level Security ..................................................................................... 6–25Defining Global Utility Security................................................................................... 6–28Defining User Class Utility Security............................................................................ 6–31Defining Event Node Name Security Rules ............................................................... 6–33Defining Remote Node Name Security Rules ............................................................ 6–36

Chapter 7: PCSEVRP: Event Report WriterOverview.................................................................................................................................. 7–1Event Definition Fields........................................................................................................... 7–4Control Statements................................................................................................................ 7–19

ACTION .......................................................................................................................... 7–19END ................................................................................................................................. 7–20FILE.................................................................................................................................. 7–21FORECAST ..................................................................................................................... 7–22INCLUDE........................................................................................................................ 7–23PRINT .............................................................................................................................. 7–24SELECT ........................................................................................................................... 7–25SORT................................................................................................................................ 7–28TITLE ............................................................................................................................... 7–29* (Comment).................................................................................................................... 7–30

Chapter 8: Monitoring Schedule HistoryOverview.................................................................................................................................. 8–1Using the Batch Monitoring Utilities.................................................................................... 8–3

Setting Up Schedule Monitoring.................................................................................... 8–3Using BIM$ACUT................................................................................................................... 8–4

Overview of Control Statements.................................................................................... 8–4ACTION ............................................................................................................................ 8–8

Implementation Guide vii

SELECT............................................................................................................................8–10SORT ................................................................................................................................8–12PRINT ..............................................................................................................................8–14OUTPUT..........................................................................................................................8–16MERGE ............................................................................................................................8–17MERGE Examples ..........................................................................................................8–21EVTSUM..........................................................................................................................8–25DEFINE............................................................................................................................8–27

Using BIM$ADUT .................................................................................................................8–28Overview of Control Statements ..................................................................................8–28ACTION ..........................................................................................................................8–32SELECT............................................................................................................................8–34SORT ................................................................................................................................8–36PRINT ..............................................................................................................................8–38OUTPUT..........................................................................................................................8–40MERGE ............................................................................................................................8–41DEFINE............................................................................................................................8–45BIM$ADUT Examples ...................................................................................................8–46

Using BIM$DSUT ..................................................................................................................8–48Overview of Control Keywords ...................................................................................8–48ACTION ..........................................................................................................................8–51SELECT............................................................................................................................8–52SORT ................................................................................................................................8–55PRINT ..............................................................................................................................8–57OUTPUT..........................................................................................................................8–59MERGE ............................................................................................................................8–60MERGE Examples ..........................................................................................................8–64DEFINE............................................................................................................................8–68

Using Online Options to Monitor BIM-FAQS/PCS..........................................................8–69Viewing Account History Online.................................................................................8–69Viewing Audit History Online .....................................................................................8–72Viewing Dataset History Online ..................................................................................8–75Viewing Event Forecasts ...............................................................................................8–77Checking Processing Periods ........................................................................................8–80

Chapter 9: Cross-Reference ReportsOverview ..................................................................................................................................9–1JCL Cross-Reference Reports .................................................................................................9–1

REPORT: Selecting Members.........................................................................................9–2OPT: Selecting Report Types .........................................................................................9–3JCLCREF: Report Processing .........................................................................................9–4PROC by Containing Member........................................................................................9–7

viii BIM-FAQS/PCS

JOB by Containing Member ........................................................................................... 9–7File ID by Containing Member....................................................................................... 9–8DTF by Containing Member........................................................................................... 9–8Assign by Containing Member ...................................................................................... 9–9EXEC by Containing Member ...................................................................................... 9–10Running Frequent Reports............................................................................................ 9–10CREF: Cross-Referencing Events ................................................................................ 9–11

Chapter 10: Using CMSOverview................................................................................................................................ 10–1Tailoring the BCMI EXEC .................................................................................................... 10–3Tailoring the PCSCMS EXEC .............................................................................................. 10–5RXPCS: Setting and Retrieving Global Variables ............................................................ 10–7Using CMS Server................................................................................................................. 10–9

Chapter 11: Using CICSOverview................................................................................................................................ 11–1Scheduler Startup: CICS Table Entries.............................................................................. 11–2BIM$TICI: CICS Table Entries............................................................................................ 11–3Communications: CICS Table Entries ............................................................................... 11–4JCLRCICS Programs............................................................................................................. 11–6

Chapter 12: Submitting Commands in a Batch JobstreamOverview................................................................................................................................ 12–1JCLXCU Control Statements................................................................................................ 12–2JCLXCU Examples ................................................................................................................ 12–4

Appendix A: PDSIO: Allowing Application Programs Accessto PDSOverview................................................................................................................................. A–1PDSIO Parameters.................................................................................................................. A–3Using PDSIO Functions......................................................................................................... A–7

Opening a Member for Input: OPEI ............................................................................ A–7Reading a PDS Member (Get Next Record): READ .................................................. A–9Closing a PDS Member After Reading: CLOS ......................................................... A–10Opening a Member for Output: OPEO ..................................................................... A–11Writing to a PDS Member: WRIT .............................................................................. A–12

Implementation Guide ix

Closing a PDS Member: CLOS ...................................................................................A–13Deleting a PDS Member: DELE..................................................................................A–14Closing PDS Member for Output and Posting DATA= Condition: CLOP...........A–15Determining Whether a Member Exists: FIND ........................................................A–16Submitting a Member: GEN........................................................................................A–17Getting a Directory List ................................................................................................A–18Executing an IMOD Synchronously: EXEC ..............................................................A–20Executing an IMOD Through FAQSAO: IMOD ......................................................A–21Retrieving a PCS Global Variable: GVAR.................................................................A–22Setting a PCS Global Variable: PVAR........................................................................A–23

Appendix B: User Exits PCSEX1 and PCSEX2Introduction............................................................................................................................. B–1

Index .......................................................................................................................... Index-1

x BIM-FAQS/PCS

Implementation Guide ATG–1

About This Guide

PurposeThe BIM-FAQS/PCS Implementation Guide describes the procedures needed toinstall this product.

OrganizationThis manual is organized as follows:

Chapter Description

1 Provides an overview of BIM-FAQS/PCS and how it is used.

2 Describes the libraries where you can store your BIM-FAQS/PCS JCL members, the command formats foraccessing these libraries, and any additional informationunique to these libraries.

3 Describes the startup requirements for BIM-FAQS/PCS andexplains the commands used to control the BIM-FAQS/PCSjob scheduler.

4 Describes the basics of BIM-FAQS/PCS job generation, JCLcomponents, generation commands, and the overrides forthose commands.

5 Describes the BIM-FAQS/PCS configuration.

6 Explains how to secure access to various BIM-FAQS/PCSfunctions, and how to protect PDS members, event files, andutilities.

7 Explains the batch utility PCSEVRP, which allows you todefine the contents and layout of event reports.

8 Provides an overview of BIM-FAQS/PCS monitoring.

9 Describes the batch cross-referencing tools CREF andJCLREF.

Continued

Who Should Use This Manual

ATG–2 BIM-FAQS/PCS

Continued

Chapter Description

10 Explains how to use CMS to access the BIM-FAQS/PCSonline features.

11 Explains the requirements for using CICS with BIM-FAQS/PCS.

12 Provides an overview of the JCLXCU utility.

A Explains the PDSIO routine.

B Explains the user exits PCSEX1 and PCSEX2.

Index Provides an efficient way to locate specific material.

Who Should Use This ManualAudience Profile

The BIM-FAQS/PCS Implementation Guide is for users who:

• Set up the product after installation

• Maintain the product

• Activate the scheduler

• Define job schedules

• Define security and configuration

• Define and modify JCL members

The BIM-FAQS/PCS Operations Guide is for users who:

• Define, maintain, and schedule events

• Define and maintain PDS members

• Set up, run, and restart jobs

Publications


PublicationsOverview of Documentation Set

The documentation set provided with BIM-FAQS/PCS consists of the followingmanuals:

• BIM-FAQS common manuals

• BIM-FAQS/PCS Implementation Guide

• BIM-FAQS/PCS Operations Guide

BIM-FAQS Common Manuals

Manual Contents

Installation and InitializationGuide

Information you need to install and initialize theBIM-FAQS/ASO and BIM-FAQS/PCS products

Message Guide A list of messages and codes you mightencounter using these products, and anexplanation and action for each one

Product-Specific Documentation

Manual Contents

Implementation Guide Information on how to get started afterinstallation, including where to store your JCL,how to activate the scheduler, how to monitoryour schedule, and how to define systemsecurity and configuration

Operations Guide Information on how to perform the day-to-dayoperations of the data center using BIM-FAQS/PCS

Related Publications


Related PublicationsBesides the manuals in this BIM-FAQS/PCS documentation set, the followingreference materials can help you to use BIM-FAQS/PCS:

• IBM VSE advanced functions manuals:

• Data Management Concepts (GC33-6192)

• System Control Statements (SC33-6198)

• VSE/VSE JCL, by Steve Eckols

• The REXX Language: A Practical Approach to Programming, by M.F. Cowlishaw

Conventions Used in This Manual


Conventions Used in This ManualThe following table lists and explains the conventions used throughout thismanual when command format or JCL statement format is shown:

Convention Explanation Example

UPPERCASE TYPE Any part of a command or JCLstatement in uppercase typemust be typed exactly as it isshown.

The following command mustbe typed exactly as shown:

EVLOAD

lowercase italic type Any part of a command or JCLstatement in lowercase italictype must be replaced withspecific variable information.

hh:mm must be replaced with thenumber of hours (hh) andminutes (mm) betweenoccurrences:

FREQ hh:mm

lowercase nonitalic Any part of a command or JCLstatement in lowercase nonitalictype must be replaced with oneof a limited number of choices inthat position.

ro must be replaced with a validrelational operand such as EQ,LT, GT, LE, or GE:

// IF USERn ro value cmd

Parentheses ( ) Parentheses must be typedwherever they appear.

The parentheses shown must betyped when you enter thiscommand:

cond=val (px ro valx)

Brackets [ ] Any part of a command or JCLstatement surrounded bybrackets is optional. Do not typethe brackets when you enter thecommand or JCL statement.

You can specify a CPU ID, oryou can enter the commandwithout a specific CPU ID:

CPU [cpuid]

Vertical bars | Vertical bars separate optionsfrom which you can select. Donot type the vertical bar whenyou enter the command or JCLstatement.

You can select either YES or NO:

HOLD [YES|NO]

Diagnostic Procedures


Diagnostic ProceduresRefer to the table below for a summary of the procedures you should follow ifyou have a problem with this software product. Each of these procedures isdetailed on the following pages.

Step Action

1 Categorize the problem and collect data. See “CollectingDiagnostic Data.”

2 Try to identify the problem. See “Interpreting Diagnostic Data.”

3 Collect diagnostic data and call support. See “Calling TechnicalSupport.”

4 Work with Technical Support to solve the problem.

Collecting Diagnostic Data

In the table below, use the left column to categorize the problem your site hasencountered. Then, follow the instructions in the corresponding right column togenerate useful diagnostic data.

For Be Sure to Check

Installation errors All output produced by MSHP when the productwas installed.

Screen errors Copies of the screens in error. Listings of alluser-coded BIM-FAQS/PCS interfaces in use.

BIM-FAQS/PCS abends The CICS generated dump. All JCL, console logsand messages for the failure. Listings of alluser-coded BIM-FAQS/PCS interfaces in use.

User-initiated functions Check the console logs, all JCL, listings, and screensfor failure. Listings of all user-coded BIM-FAQS/PCS interfaces in use.



Interpreting Diagnostic Data

After collecting the specified diagnostic data, write down answers to thefollowing questions:

• What was the sequence of events prior to the error condition?

• What circumstances existed when the problem occurred and what action wastaken?

• Has this situation occurred before? What was different then?

• Did the problem occur after a particular PTF was applied or after a newrelease of the software was installed?

• Was a new release of the operating system installed recently?

• Has the hardware configuration (tape drives, disk drives, and so forth)changed?

From the answers to these questions and the diagnostic data, try to identify thecause and resolve the problem. If it is determined that the problem is a result ofan error in this software product, contact BIM Technical Support.

Calling Technical Support

B I Moyle Associates Inc. provides telephone support for all its products.

If you are in North America, call (952)-933-2885. Outside North America, callyour local BIM Software Agent.

Please have the following information ready before contacting BIM TechnicalSupport:

• All the diagnostic information described in "Collecting Diagnostic Data."Product name and release number.

• Product name and release number of any other software you suspect isinvolved.

• Release level and PUTLEVEL of the operating system.

• Your name, telephone number and extension (if any).

• Your company name.

Implementation Guide 1–1

Chapter 1Introduction to BIM-FAQS/PCS

What Is BIM-FAQS/PCS?Introduction

BIM-FAQS/PCS is a production control system for the VSE operatingenvironment. BIM-FAQS/PCS provides event-based job scheduling, including acomprehensive online user interface and a full set of batch utilities. BIM-FAQS/PCS features:

• Event-driven scheduling

• An easy-to-use online system

• JCL management

• Auditing and accounting reports

• Comprehensive security and configuration

BIM-FAQS/PCS requires no modifications to the IBM operating system.

Event-Driven Scheduling

A BIM-FAQS/PCS event can submit jobs, issue commands, and initiate REXXIMODs. You can define the day an event will be scheduled by using one of thesupplied keywords or a user-defined keyword.

A few of the ways you can define an event to be dispatched are according to thetime of day, completion of a job, a specific global variable value, the completionof a work station condition, a console message, or a posting by another product.You can also have the event command dispatched to a remote system.

Event definition is fast and easy with BIM-FAQS/PCS for the following reasons:

• You can create prerequisite conditions, called WHEN clauses, by using fill-in-the-blank fields on screens; these fields eliminate the need to learn the syntaxfor these statements.

• You can easily define scheduling ("processing period") keywords if none ofthe supplied keywords will do. You can then display a calendar of days toverify whether your definition is correct. All of this is accomplished withoutleaving the event definition screen.

• Field-level help is available to help you determine the values available for aparticular field. For instance, you can access a list of all supplied scheduling

What Is BIM-FAQS/PCS?

1–2 BIM-FAQS/PCS

keywords by placing the cursor in the field and pressing PF1; an online helpscreen is displayed and the keywords are described.

BIM-FAQS/PCS Online

The online system can be accessed through any of the following interfaces:

• BIM-FAQS/ASO

• CMS

• CICS

• BTAM

• VTAM

You can access the online system through BIM$TIDR using a BTAM terminal oras a VTAM application.

Access through CMS is completely independent of the VSE system and isavailable even if the VSE system is down.

Most BIM-FAQS/PCS online screens present information, including events in thecurrent or master schedule, JCL members, global variables, work stationdefinitions, security and configuration options, user-defined schedulingkeywords, and cycle calendars in a "directory" format.

Directories offer the following advantages:

• Screen hierarchies enable you to access information of increasing detail onsuccessive screens, usually by cursor-selecting the desired item.

• Prefix commands entered next to an item enable you to manipulate it or toaccess related information. For example, the audit history associated with anevent can be accessed by using the A command.

• Subsets of a directory can be viewed using selection criteria provided onmany displays. For example, you can view only those events that havecompleted execution.

• Fast-path commands allow for quick access to related BIM-FAQS/PCSscreens.



JCL Management

BIM-FAQS/PCS supports user job control in many existing libraries. You canretrieve JCL from:

• BIM-FAQS/PCS partitioned datasets

• VSE libraries

• CMS minidisks

• ICCF libraries

• BIM-EDIT, CA-PANVALET, CONDOR, CA-VOLLIE, and CA-LIBRARIANlibraries

BIM-FAQS/PCS supplies its own partitioned dataset (PDS). You can keep yourJCL where it currently resides or move it to the BIM-FAQS/PCS PDS.

BIM-FAQS/PCS supports conditional JCL (submit time and run time) which can:

• Set and query global variables

• Substitute variable data anywhere in a job

• Insert additional jobsteps

• Initiate REXX IMODs

• Alter job flow (conditional branches)

BIM-FAQS/PCS provides additional functionality for JCL that resides in thePDS, such as:

• Control security and auditing

• Cross-reference reports

• Globally update JCL

Accounting and Audit History

Changes to BIM-FAQS/PCS events or JCL members create audit records. Allauditing information is available for viewing online.

Accounting information is maintained for all jobs submitted by BIM-FAQS/PCS.Accounting displays are available online to summarize the average start time,duration, CPU usage, and I/Os initiated by all executions of an event over thepast year.


1–4 BIM-FAQS/PCS

Security and Configuration

BIM-FAQS/PCS security and configuration are defined online. With securitydefinitions, you can control access to:

• Online screens

• BIM-FAQS/PCS events and event groups

• PDS members

• User classes

• BIM-FAQS/PCS utilities

With configuration options, you can establish options for the system or for aspecific user ID. For the system, you can define:

• CMS submission defaults

• Event definition, panel, and PDS defaults

• CMS server defaults

• User classes for common security needs

• Global system options, including batch configuration defaults

• External library defaults

• CPU ID synonyms

• Holidays and cycles

• Dataset exclusion and logging options

For a user ID, you can define:

• CMS submission defaults

• Event definition, panel, and PDS defaults

• Prerequisite knowledge

Background

This manual assumes that you are familiar with the VSE (Virtual StorageExtended) operating system and with VSE JCL (job control language).

You should also be familiar with how your schedule is set up. When defining anevent or scheduling a job, it is important to know when it should run, what jobshave to run before it can run, what jobs can't run at the same time, and the orderof all jobs in the schedule.

SYS$EVT PDS


SYS$EVT PDSIntroduction

To relieve some of your PDS constraints, BIM-FAQS/PCS has a new PDS forevent information--the SYS$EVT PDS. This PDS contains all of your master andcurrent event definitions, and is used only by BIM-FAQS/PCS.

All BIM-FAQS/PCS event information must be moved from the SYS$MON PDSto the SYS$EVT PDS. If you are currently running a release of FAQS/PCS priorto 4.5, you will need to perform a conversion to the new PDS after installing thisnew release.

Procedure

To convert to the new PDS structure, perform a backup of the MON PDS andrestore to the SYS$EVT PDS using PCSEVBR. The PCSEVBR utility converts onlythe master event file.

To back up SYS$MON and restore to SYS$EVT, use the following JCL:

* $$ JOB JNM=PCSEVBR,CLASS=Y,LDEST=(,destname)* $$ LST CLASS=A,DISP=D// JOB PCSEVBR// TLBL PCSEVI,'PCSEVBR.BACKUP'// TLBL PCSEVO,'PCSEVBR.BACKUP'// ASSGN SYS010,TAPE// LIBDEF PHASE,SEARCH=(BIMLIB.PCS,BIMLIB.GSS)// EXEC PCSEVBR,SIZE=PCSEVBRBACKUP PDS=MON CLOSE=REWRESTORE LIST=YES/*/&* $$ EOJ PCSEVBR

Converting from Version 3.4 or Earlier

1–6 BIM-FAQS/PCS

Converting from Version 3.4 or EarlierIntroduction

If you have a version of CA-FAQS/PCS prior to Version 3.4, you must perform aconversion function. This section explains how to use the JCLCONV utility toconvert to BIM-FAQS/PCS from a version prior to Version 3.4.

Depending on your former release, you may need to issue different JCLCONVcommands. The following table shows the conversion function to performdepending on the version you have:

Release Conversion Function

Prior to 3.4 (and not JCLMAN) Converts event file format and holiday ID

Pre-DCM-Systems (JCLMAN) Converts time-driven jobs to BIM-FAQS/PCSevents

Conversion Commands

The following commands are used by the JCLCONV utility. Depending on yourrelease number, you may need to use one or two of the following commands atconversion.

Command Function

CONVERT Converts old event file format to the current eventfile format.

CONVERT HOLIDAY Converts the event maintenance one-digit Cal-IDfield to the three-digit Hol-ID field.

EVENT Converts time-driven jobs to event files. Used onlywhen converting from JCLMAN, the time-driven jobscheduler, to BIM-FAQS/PCS, the event-drivenscheduler.



Event File Format Changes

Pre-Version 3.4/Post-JCLMAN: Users of CA-FAQS/PCS event-drivenscheduling Version 3.32 and earlier should note that the event file format haschanged.

The format of the event file now incorporates the event DESCRIPTION field andadditional time fields. The CONVERT conversion command converts event fileformats.

JCLMAN Only: Users of the JCLMAN time-driven scheduling should note thatthe event file format has changed.

Converting Cal-ID to Hol-ID

The calendar ID, used in Version 3.2 to define event calendars on the EventMaintenance screens, changed with Version 3.4. You must use the CONVERTHOLIDAY command to convert the one-digit Cal-ID to the new three-digitHol-ID.


1–8 BIM-FAQS/PCS

Using JCLCONV

Sample Procedure

Complete the following steps to convert from any version prior to 3.4 (and post-JCLMAN):

1. Deactivate the $JOBEXIT and $JOBACCT phases by executing JCLXCU withthe JCL OFF and JA OFF statements.

2. Complete the installation procedures for BIM-FAQS/PCS.

3. Execute JCLCONV with the CONVERT and CONVERT HOLIDAYstatements.

4. Load the new version's JCLACCT phase into the SVA by performing a SETSDL.

5. Enable the $JOBEXIT and $JOBACCT hooks by executing JCLXCU with theENABLE statement, and any other normal startup options.

6. Initialize the BIM-FAQS/PCS online partition.



Sample Jobstream

Step 1: The following example shows the jobstream used to complete theconversion from versions prior to 3.4 (and post-JCLMAN):

// EXEC JCLXCUJCL OFFJA OFF/*

Step 2: Install the product following the installation procedures described in theBIM-FAQS (ASO & PCS) Installation and Initialization Guide.

Steps 3-5: The following example shows the jobstream used to implement theconversion commands, to reload the SVA phase, to enable the job exit andaccounting hooks, and any other normal startup options:

// EXEC JCLCONVCONVERTCONVERT HOLIDAY/*SET SDLJCLACCT,SVA/*// EXEC JCLXCUENABLE LOAD=N,EVENTS=2048/*/&

After this jobstream is executed, event processing will continue.

Step 6: Initialize the online partition.


1–10 BIM-FAQS/PCS

Converting Event Information

Timetable Conversion

You must use the JCLCONV EVENT command if you are converting to BIM-FAQS/PCS from JCLMAN, and you want to use JCLSCHED with its time-drivenscheduler capabilities. The following timetable entries are converted:

#nnn----.CAL All members of this type are converted to events. The event name created is inthe format xttttnnn, where x is the first character of the day, tttt is the time of theevent, and nnn is a sequence number (from 001 to 999). The first event name thatdoes not exist is chosen. The character that represents Thursday is R; for Sunday,the character is U.

JCLTnnnn All members of this type are converted into events. The JCLTtttt membersshould not be deleted since they are used as the event's command file. Theformat of the event name created is JCLTnnn, where tttt is the time of theJCLTtttt member and nnn is the next available sequence number, between 001and 999. Existing calendar overrides remain effective. JCLCONV remembers thedays and times that had overrides and accordingly places the correct day into theevent definition.

Multiple-CPU Conversion

The JCLCONV utility converts events in the CPU where the scheduler is running.If more than one CPU is running, you must use the JCLCONV utility to convertevents on each CPU. Then the scheduler should be terminated and restarted onall CPUs (using the JCLSCHED utility).

Sample ProcedureComplete the following steps to convert from JCLMAN to BIM-FAQS/PCS:

1. Deactivate the $JOBEXIT phase by executing JCLXCU with the JCL OFFstatement.

2. Complete the installation procedures for BIM-FAQS/PCS.

3. Execute JCLCONV with the EVENT statement.

4. Load the new version's JCLACCT phase into the SVA by performing a SETSDL.

5. Enable the $JOBEXIT and $JOBACCT hooks by executing JCLXCU with theENABLE statement, and any other normal startup options.

6. Initialize the BIM-FAQS/PCS online partition.



Sample Jobstream

Step 1: The following example shows the jobstream used to complete theconversion from JCLMAN to BIM-FAQS/PCS:

// EXEC JCLXCUJCL OFF/*

Step 2: Install the product following the installation procedures described in theBIM-FAQS (ASO & PCS) Installation and Initialization Guide.

Steps 3-5: The following example shows the jobstream used to implement theconversion commands, to reload the SVA phase, to enable the job exit andaccounting hooks, and any other normal startup options:

// EXEC JCLCONVEVENT/*SET SDLJCLACCT,SVA/*// EXEC JCLXCUENABLE LOAD=N,EVENTS=2048/*

After this jobstream is executed, event processing will continue.

Step 6: Initialize the BIM-FAQS/PCS online partition.


1–12 BIM-FAQS/PCS

Converting CA Schedules and Jobs

Introduction

In Release 4.0, the CACONVRT IMOD has been replaced with the CACONVEX(extract) and CACONVBL (build) IMODs. If you are converting your schedulefrom CA-SCHEDULER to BIM-FAQS/PCS, CACONVEX and CACONVBL canhelp you reduce the amount of event information that needs to be rekeyed.

Limitations

Because of certain architectural differences, CACONVEX and CACONVBLcannot convert CA-SCHEDULER keywords and criteria statements that defineevent relationships. You will need to evaluate your event relationships and usethe appropriate BIM-FAQS/PCS values in your schedule and event definitions.

Procedure

To convert your schedule from CA-SCHEDULER to BIM-FAQS/PCS using theCACONVEX and CACONVBL IMODs, follow these steps:

1. Customize (if necessary) the following items in CACONVBL:

• Default LATE and ABORT times• Default PROC library for those who schedule VSE PROCs• Handling of schedules/jobs defined with AUTOSEL=NO• BACKLOG time definition• Ability to generate scheduled events for testing

2. Run the sample jobstream to build JCLEVNT-compatible event definitioncontrol statements. The jobstream runs the CA-SCHEDULER utilityCAJUTIL0 to generate an ANALYZE SCHEDULE report. This report is thenread by CACONVEX to produce an intermediate file in the POWER PUNqueue. CACONVBL is then executed to read the intermediate file andproduce card output acceptable to JCLEVNT. A report is produced withinformation regarding the conversion process, including any warning orexceptional condition messages.

3. Run JCLEVNT to define the events.

4. Using the report produced in Step 2, review the warnings and make thenecessary changes using the BIM-FAQS/PCS online system.

5. Review each event to confirm that an equivalent schedule was defined by theconversion process. This can be done via online and batch forecasting andreporting. Utilities such as PCSEVRP and JCLEVNT with the CREF functionare helpful.

6. Re-evaluate the schedule to simplify event definitions by taking advantage ofthe BIM-FAQS/PCS methodology and features.



Sample Jobstream

The following example shows the jobstream used to perform the conversion fromCA-SCHEDULER to BIM-FAQS/PCS:

* $$ JOB JNM=CA2PCS,USER='TO BIMPCS',DISP=D* $$ LST LST=SYSLST,DISP=H,RBS=0,USER='CASADATA OUTPUT'* $$ PUN PUN=SYSPCH,DISP=H,RBS=0,USER='CACONVEX OUTPUT'// JOB CA2PCS CONVERT FROM CA-SCHEDULER TO BIM-FAQS/PCS/** STEP 005 - EXTRACT DATA FROM CA-SCHEDULER// LIBDEF PHASE,SEARCH=(CALIB,SCHEDLR)// EXEC CAJUTILO,SIZE=(AUTO.80K)ANALYZE SCHEDULE NAME=schdname/** $$ LST LST=SYSLST,DISP=D,DEST=(,BIMPCS)/*// LIBDEF PHASE,SEARCH=(BIMLIB.PCS,BIMLIB.GSS)* STEP 010 - EXTRACT INFORMATION FROM CA-SCHEDULER DATABASE// EXEC BIM$RXBA,SIZE=BIM$RXBA,PARM='CACONVEX CA2PCS'/** $$ PUN PUN=SYSPCH,DISP=D,RBS=0,DEST=(,BIMPCS)/** STEP 015 - GENERATE BIM-FAQS/PCS EVENT DEFINITIONS// EXEC BIM$RXBA,SIZE=BIM$RXBA,PARM='COCONVBL CA2PCS'/*/&* $$ EOJ


1–14 BIM-FAQS/PCS

Notes:

• The POWER jobname must match the parameters specified for bothCACONVEX and CACONVBL on the EXEC statement for BIM$RXBA.

• The POWER PUN and LST queues must not contain members of the samename. The IMODs retrieve data from the LST and PUN queues. Other datawill produce incorrect results.

• The output produced by this jobstream is formatted for input to JCLEVNT.

Restrictions

The following CA-SCHEDULER schedules and jobs will require extra manualeffort:

• DATETABs are not converted. Where possible, keywords referencingDATETABs are converted to CYCLE keyword derivations. Events aredefined with the proper CYCLE IDs. An informational message is producedidentifying each DATETAB and the corresponding CYCLE ID.

• Some CA-SCHEDULER keywords do not have PCS-equivalent keywords.They have to be evaluated individually. Keywords such as DAYxOFn,WEEKxOFn, RDxxxx, WWOMxx, and LEAP-YEAR are incompatible.

• Some CRITERIA statements may be too complex for BIM-FAQS/PCS togenerate a single event definition. These are noted in the warnings.

• CRITERIA statements can be defined with conditions that are OR'd together.BIM-FAQS/PCS treats these as successor conditions. SCD conditions thatare OR'd are unsupported by BIM-FAQS/PCS. A maximum of 24 successorconditions may be defined to any event.

• CRITERIA statements defined with ANDs are generated as predecessor(WHEN) conditions. BIM-FAQS/PCS supports a maximum of eight perevent.

• The START keyword cannot be converted automatically. The conversionroutine ignores the START condition and defines the event as a predecessor.If it is necessary that events start at the same time, they should be definedwith the same predecessor conditions.


Chapter 2Storing JCL

This chapter describes the libraries where you can store your JCL members, thecommand formats for accessing these libraries, and any additional informationunique to particular libraries.

OverviewIntroduction

This chapter describes the libraries where you can store your JCL members, thecommand formats for accessing these libraries, and any additional informationunique to particular libraries.

JCL Sources

BIM-FAQS/PCS schedules JCL from a number of libraries. These librariesinclude:

• BIM-FAQS/PCS PDS

• BIM-EDIT

• ICCF

• CMS server

• CA-VOLLIE

• CA-DRIVER

• CA-LIBRARIAN

• CA-PANVALET

• CONDOR

• VSE

• POWER RDR Queue

You can schedule JCL from any of the above libraries. However, there areadvantages to using the BIM-FAQS/PCS PDS.

Overview

2–2 BIM-FAQS/PCS

Reasons for Selecting the BIM-FAQS/PCS PDS

You gain the following features by using the BIM-FAQS/PCS PDS to scheduleJCL:

• Last-execution timestamp on PDS members

• Full member-level security for PDS members

• Concurrent access to the PDS from VSE and native CMS

• BCIN CMS interface support

• Improved use of DASD space

• Online maintenance to PDS members

• Selective member restoration

• Selective member deletion

• Online directory list

• Full reporting and cross-referencing

Definition: PDS

A PDS (partitioned dataset) is a type of library used to store members. You definethe BIM-FAQS/PCS PDS much like an ordinary sequential disk file, and format itusing the BIM$PUTL utility.

Because the PDS is managed entirely on disk, it can be shared between two ormore machines. The BIM-FAQS/PCS PDS is the supplied JCL library for BIM-FAQS/PCS.

JCL Ready to Go

BIM-FAQS/PCS requires no additions or adjustments to your existing JCL.

However, you may enhance how your existing JCL works with BIM-FAQS/PCSin the following ways:

• Add conditional logic (PCL) to the simpler (step) procedures first. As youbecome familiar with the schedule, you can add more complex procedures.

• Add runtime conditional logic (ECL) as your operation requires it.

• Merge duplicate JCL into a few general purpose procedures.

Overview


Copying Members From External Libraries

You can copy JCL members from external libraries into the BIM-FAQS/PCS PDSvia:

• The BIM-FAQS/PCS online screen, External Library Browse and Copy.

• The PDSCOPY REXX IMOD. $PDSCOPY is executed from BIM$RXBA.

For More Information: See the BIM-FAQS/PCS Operations Guide for moreinformation about using BIM-FAQS/PCS Online or REXX to copy members fromexternal libraries into the BIM-FAQS/PCS PDS.

Accessing Members from JCL Sources

2–4 BIM-FAQS/PCS

Accessing Members from JCL SourcesIntroduction

This section describes the command formats for members stored in the differentJCL libraries. When you schedule or generate a member, you must use thecorrect format for its library. In some cases, you must catalog the appropriateJCL library interface program before using its corresponding interface.

Library Command Formats

Members that reside in the JCL libraries can be scheduled by accessing thelibraries using their unique command formats. The following table lists thecommand formats for JCL libraries:

Command Format Used to ScheduleMembers

Abbreviated Command Format

ppp:membname.ttt membname

D=ppp:ssss M=membname D:membname

&SUB membname.ttt.mmm (JCLSCHED) N/A

SUB membname.ttt.mmm (JCLXCU) N/A

V=libname M=opi.membname V:opi.membname

W:membname W:membname

B=libname S=sysname M=membname B:membname

L=libname M=membname L:membname

P=libname M=membname P:membname

X=libname M=membname X:membname

S=library.sublibrary M=membname.ttt S:membname.ttt

R:membname N/A

Using the Abbreviated Format

The abbreviated command formats reference the default library names asspecified in your BIM-FAQS/PCS configuration. If you want to specify a libraryother than the default, you must use the full command format.

For More Information: See Chapter 5, “Defining System Configuration,” formore information about defining library defaults.



VSE Abbreviated Command Format

With the VSE abbreviated command format, BIM-FAQS/PCS uses the followingVSE library source search chain:

// LIBDEF SOURCE,SEARCH=lib.sublib

When you submit from VSE libraries, the abbreviated format will use the LIBDEFsource search chain of the partition.

PDS and ICCF Defaults

The PDS and ICCF defaults differ slightly. Both allow you to define more thanone library: five for PDS and three for ICCF. For PDS this creates a PDS searchstring; when a PDS command is issued, the system looks for the member in thefirst default library, and if the member is not found in the first default library, thesecond is searched, then the third, and so on. For ICCF you can define a primarylibrary, a connected library, and a common library. Members are searchedsequentially in these libraries also.

For More Information: See Chapter 5, “Defining System Configuration,” formore information about defining library defaults.

What Library Members Can Contain

Members stored in the JCL libraries can contain:

• PCL conditional language

• REXX procedure calls (BIMs' implementation of REXX)

• Members from other JCL libraries (using a ./ PROC statement)

• Variables for JCL and data

The following sections explain the JCLSCHED command formats and theirexceptions.


2–6 BIM-FAQS/PCS

Command Types for Submitting JCL

Introduction

BIM-FAQS/PCS makes submitting JCL from libraries very easy and flexible.You can use several types of commands depending on where you're issuing thecommands from and what you want to do. The following table explains thedifferent types of commands:

Command Type Function

JCLSCHED Submits a member from the system console or from anevent

JCLXCU Submits a member through the batch utility

Online Interfaces Submits a member from other online interfaces(BIM-FAQS/ASO, BIM$TICI, or BIM$TIDR)

JCLSCHED

The rest of this chapter uses the JCLSCHED command as its sample forexplanation. This is the command method most commonly used to access JCLmembers.

JCLXCU

You can use the JCLXCU utility to issue job generation commands that access JCLmembers in batch. The following format is required to submit a JCL memberusing JCLXCU:

GEN membname

This command generates a jobstream that will access a library or library member.

Online Interfaces

You can call JCL members from various online interfaces. The following formatis required to call a member via BIM-FAQS/ASO, BIM$TICI, or BIM$TIDR:

.membname

Accessing Members Using ./PROC

You can use a PROC statement to call JCL members from a library. Thefollowing format is required to call a JCL member using a PROC statement:

./ PROC membname

For more information about the ./ PROC statement, see Chapter 4, “JobGeneration.”



Using the BIM-FAQS/PCS PDS

Introduction

This section describes:

• The command format for accessing members stored in the BIM-FAQS/PCSPDS

• Additional maintenance tools for managing PDS members

Command FormatThe following command is required to access members in a PDS:

ppp:membname.ttt

ppp 3-character PDS ID. Standard PDS IDs used by BIM include:

• MON PDS. Contains user-defined JCL and REXX IMODs.

• VIO PDS. Contains audit and account files, screen definitions, and onlineuser profiles.

• EVT PDS. Contains event files.

membname 2-to-8-character member name. If only the member name is used as a command,BIM-FAQS/PCS assumes, by default, that you are calling a PDS member.

ttt 1-to-3-character member type. The default is MON. To change the default, youmust change the DATATYP parameter through the configuration displays. Formore information, see Chapter 5, “Defining System Configuration.”

PDS ID Search String

With BIM-FAQS/PCS configuration, you can define a PDS search string. In otherwords, when accessing JCL from a PDS, you can define up to five PDS IDs, andthe system will search each PDS in the list, looking for the member name in each.

For More Information: For information about defining the PDS search string, seeChapter 5, “Defining System Configuration.”


2–8 BIM-FAQS/PCS

Managing the PDS

Introduction

This section describes the utilities available to manage the BIM-FAQS/PCS PDS:BIM$PUTL and JCLMAN.

Managing the PDS: BIM$PUTL and JCLMAN

BIM-FAQS/PCS provides the BIM$PUTL and JCLMAN batch utilities. WithBIM$PUTL you can format, analyze, backup, restore, dequeue, or show adirectory list of a PDS. With JCLMAN you can perform file maintenance on aspecific member of a PDS. Some member file maintenance functions includeadding, updating, deleting, replacing, copying, or moving PDS members.

Using BIM$PUTL: Online or Batch

You can perform BIM$PUTL functions by submitting batch commands usingJCL, or entering the same information using the online BIM$PUTL screens. Bothmethods generate a batch jobstream to perform the PDS maintenance functions.

For More Information: For an explanation of how to use the BIM$PUTL utilitywith online screens, see the BIM-FAQS/PCS Operations Guide. For anexplanation of how to use BIM$PUTL with batch commands, see the BIM-GSSInstallation and Utilities Guide.

Using JCLMAN

You can perform JCLMAN functions by submitting batch commands using JCL.This method generates a batch jobstream that performs the PDS membermaintenance functions. The batch procedures JCLMAINT, JCLGEN, JCLSERV,JCLTRACE, JCLTAPE, and JCLDSERV enable you to maintain PDS members.

For More Information: See the BIM-FAQS/PCS Operations Guide for anexplanation of how to use these procedures and JCLMAN member maintenanceutilities.

Backing Up the PDS

You should periodically back up all PDSs to ensure successful recoverycapabilities. You should use the BIM$PUTL BACKUP command because itenables you to perform:

• A full or partial library restore

• Integrity checks

Each backup is a separate execution of BIM$PUTL.



JCL for Backing Up a PDS

The following JCL performs two complete PDS backups to two tapes for theMON PDS and the VIO PDS:

// TLBL GSPDSO,'MON.BACKUP'// ASSGN SYS010,280// LIBDEF PHASE,SEARCH=(BIMLIB.PCS,BIMLIB.GSS)// EXEC BIM$PUTLPDS=MON,BACKUP/*// TLBL GSPDSO,'VIO.BACKUP'// ASSGN SYS010,281// LIBDEF PHASE,SEARCH=(BIMLIB.PCS,BIMLIB.GSS)// EXEC BIM$PUTLPDS=VIO,BACKUP/*

To restrict a backup to a subset of a full PDS, use the SEL= statement. Forexample, SEL=ABC*.* outputs all files with ABC in the first three positions of thefilename.

For More Information

See the BIM-GSS Installation and Utilities Guide for more information about theBIM$PUTL utility and backing up members.


2–10 BIM-FAQS/PCS

Using ICCF

Introduction


• The command format for accessing members stored in an ICCF library

• Access considerations for ICCF members.

Note: You cannot use BIM-FAQS/PCS to submit compressed ICCF members

Command Format

The following command format is required to access members in an ICCF library:

D=pppp.ssss M=membname

Variables

Variable Explanation

pppp 1-to-4-digit primary ICCF library number. Value can be 1 to 9999.

ssss 1-to-4-digit secondary ICCF library number. Value can be 1 to9999. ssss is optional.

membname 1-to-8-character ICCF member name. If only the member name isused as a command, the primary and secondary ICCF librarynumbers defined through the configuration displays are used.SeeChapter 5, “Defining System Configuration” for moreinformation about ICCF defaults defined in configuration.

Access Considerations

ICCF does not need to be running for the ICCF command to work. In otherwords, the ICCF library can be accessed even when ICCF is not running.However, do not schedule ICCF members while the library is being reorganized.This can result in ICCF access errors.



Using CMS Server

Introduction

The CMS server:

• Can submit packed members

• Requires no VSE storage

• Supports pre-existing CMS includes

From a CMS server you can access only BIM-FAQS/PCS PDS members and anyminidisk accessible by the server. To access members, use ./ PROC statements.


• The command format for accessing members stored on a CMS server

• Access considerations for members on a CMS server

• How to use a CMS server

Command Formats

The following command formats are required to access members stored on aCMS server:

JCLSCHED command format:&SUB membname.ttt.m

JCLXCU command format:SUB membname.ttt.m

Variables


membname 1-to-8-character member name.

ttt 1-to-8-character member type. ttt is optional.

m 1-character member mode. m is optional.

Configuration Information

For more information about configuring and using CMS, see Chapter 10, “UsingCMS.”


2–12 BIM-FAQS/PCS

Using BIM-EDIT

Introduction


• The command format for accessing members stored in a BIM-EDIT library

• Access considerations for BIM-EDIT members

Command Format

The following command format is required to access members in a BIM-EDITlibrary:

B=libname S=sysname M=membname

Variables


libname The BIM-EDIT internal library name. The library name cannotexceed 16 characters.

sysname The BIM-EDIT system name. The system name cannot exceed8 characters.

membname The BIM-EDIT member name. The member name cannotexceed 16 characters.

NOTE: The total length of this command cannot exceed 38 characters.


Before a member can be scheduled from a BIM-EDIT library, you must catalogthe JCLBIME phase to the BIM-FAQS/PCS residence library.

The JCLBIME.MON member contains the JCL to catalog the JCLBIME phase. Totailor the JCLBIME.MON member, add LIBDEF OBJ,SEARCH= statements forthe BIM-FAQS/PCS and BIM-EDIT residence libraries, and add a LIBDEFPHASE,CATALOG= statement to the JCLBIME.MON member. Once tailoring iscompleted, make sure the JCLBIME phase is in the JCLSCHED partition LIBDEFsearch chain.

LU6.2 Interface: If you are using the BIM-EDIT LU 6.2 interface, you mustcatalog the JCLBIME6 phase to the BIM-FAQS/PCS residence library. Tailor theJCLBIME6.MON member by adding LIBDEF OBJ,SEARCH= statements for theBIM-FAQS/PCS and BIM-EDIT residence libraries, and adding a LIBDEFPHASE,CATALOG= statement. Once tailoring is completed, make sure theJCLBIME phase is in the JCLSCHED partition LIBDEF search chain.



There is a JCL member on the MON PDS called JCLBIMNM.MON that allowsthe default BIM-EDIT System Name to be changed for PCS. The default isBIMEDIT. Note that this can be overridden using the command as shown above,or by using the PCS library defaults panel (PCS O.I). See Defining LibraryDefaults.


2–14 BIM-FAQS/PCS

Using CA-VOLLIE

Introduction


• The command format for accessing members stored in a CA-VOLLIE library

• Access considerations for CA-VOLLIE members

Command Format

The following command format is required to access members in a CA-VOLLIElibrary:

V=libname M=opi.membname

Variables


libname CA-VOLLIE library VSE DLBL name

opi 3-character CA-VOLLIE op ID

membname Member name


Before a member can be scheduled from a CA-VOLLIE library, you must catalogthe JCLVOLI phase to the BIM-FAQS/PCS residence library.

The JCLVOLI.MON member contains the JCL to catalog the JCLVOLI phase. Totailor the JCLVOLI.MON member, add LIBDEF OBJ,SEARCH= statements forthe BIM-FAQS/PCS and CA-VOLLIE residence libraries, and add a LIBDEFPHASE, CATALOG= statement to the JCLVOLI.MON member. Once tailoring iscompleted, make sure the JCLVOLI phase is in the JCLSCHED partition LIBDEFsearch chain.

Note: To regenerate the most current version of the VIP modules, refer to theCA-VOLLIE documentation.



Using CA-DRIVER

Introduction


• The command format for accessing members stored in a CA-DRIVER library

• Access considerations for CA-DRIVER members

Command Format

The following command format is required to access members in a CA-DRIVERlibrary:

W:membname

Variable

membname is an 8-character member name.


Before a member can be scheduled from a CA-DRIVER library, you must catalogthe JCLDRIV phase to the BIM-FAQS/PCS residence library.

The JCLDRIV.MON member contains the JCL to catalog the JCLDRIV phase. Totailor the JCLDRIV.MON member, add LIBDEF OBJ,SEARCH= statements forthe BIM-FAQS/PCS and CA-DRIVER residence libraries, and add a LIBDEFPHASE, CATALOG= statement to the JCLDRIV.MON member. Once tailoring iscompleted, , make sure the JCLDRIV phase is in the JCLSCHED partition LIBDEFsearch chain.


2–16 BIM-FAQS/PCS

Using CA-LIBRARIAN

Introduction


• The command format for accessing members stored in a CA-LIBRARIANlibrary

• Access considerations for CA-LIBRARIAN members

Command Format

The following command format is required to access members in aCA-LIBRARIAN library:L=libname M=membname

Variables


libname CA-LIBRARIAN library VSE DLBL name

membname 3-to-8-character member name


The JCLLIBR phase resides in the BIM-FAQS/PCS residence library.

Although not required, you may want to add the following phases to the SVA (ifthey are not already there) for performance and storage reasons:

• FAIROPN

• FAIRLOC

• FAIRMOD

• FAIRREC

• FAIRNTE

• FAIRPNT

• FAIRCLS

If you don't add these phases to the SVA, you must add a LIBDEFPHASE,SEARCH= statement for the BIM-FAQS/PCS library and CA-LIBRARYin the partition where the scheduler's running and in any online partitions.

Note: The default SYS NO is SYS004.



Using CA-PANVALET

Introduction


• The command format for accessing members stored in a CA-PANVALETlibrary

• Access considerations for CA-PANVALET members

Command Format

The following command format is required to access members in a CA-PANVALET library:P=libname M=membname

Variables


libname CA-PANVALET library VSE DLBL name



The JCLPANV phase resides in the BIM-FAQS/PCS residence library.

Although not required, you may want to add the PAM phase to the SVA (if it isnot already there) for performance and storage reasons. If the PAM phase is notin the SVA, you must add the CA-PANVALET library to the LIBDEF SEARCHchain for the scheduler partition and any partitions running in the onlineinterface.


2–18 BIM-FAQS/PCS

Using CONDOR

Introduction


• The command format for accessing members stored in a CONDOR library

• Access considerations for CONDOR members

Command Format

The following command format is required to access members in a CONDORlibrary:X=libname M=membname

Variables


libname CONDOR library name, derived from the VSE DLBLname. Although library names start with GA, this prefix isnot required.

membname 3-to-8-character member name.


Before a member can be scheduled from a CONDOR library, you must catalogthe JCLPNX phase to the BIM-FAQS/PCS residence library.

The JCLPNX.MON member contains the JCL to catalog the JCLPNX phase. Totailor the JCLPNX.MON member, add a LIBDEF OBJ,SEARCH= statement forthe BIM-FAQS/PCS and CONDOR residence libraries. Also, add a LIBDEFPHASE, CATALOG= statement to the JCLPNX.MON member. Once tailoring iscompleted, make sure the JCLPNX phase is in the JCLSCHED partition LIBDEFsearch chain.



Using VSE Library Members

Introduction


• The command format for accessing members stored in a VSE library

• Tips for using VSE effectively

Command Format

The following command format is required to access members in a VSE library:

S=library.sublibrary M=membname.ttt

Abbreviated Format: The following abbreviated command format can be used toaccess members in a VSE library:

S:membname:ttt

With the abbreviated command, BIM-FAQS/PCS uses the VSE library sourcesearch chain, // LIBDEF SOURCE,SEARCH=lib.sublib.

Variables


library Library name

sublibrary Sublibrary name


ttt 1-to-8-character member type (can't be OBJ or PHASE)


In order to access VSE library members, the VSE library:

• Must be defined in either standard or partition labels

• Can include members from any other library or sublibrary


2–20 BIM-FAQS/PCS

Using the POWER RDR Queue

Introduction

Use the scheduling command R:membname to indicate that the JCL in the jobmembname is to be submitted out of the POWER RDR queue. This commandpulls in the copy of the job with the lowest POWER job number (i.e., oldest) fromthe POWER RDR queue.

Command FormatR:membname:

membname is the name of the job to submit from the POWER RDR queue. Thereis no "full" command format for this command.

You can include additional POWER override parameters such as CLASS= orDISP=. For more information on POWER overrides, see Chapter 4, “JobGeneration.”

Disposition

BIM-FAQS/PCS handles the disposition of jobs submitted from the POWER RDRqueue in the following ways:

When the Job Is Scheduled, BIM-FAQS/PCS:

D Deletes the original job

H Deletes the original job

K Leaves the original job in the POWER queue

L Leaves the original job in the POWER queue

If the job is not found and was scheduled as an event, the event is marked asabended.



POWER Parameters

The POWER job parameters LDEST, XDEST, and PDEST are not available toBIM-FAQS/PCS. Therefore, specify these parameters by using the statements inthe following table:

To Specify Use a DEST= Parameter on the

LDEST information POWER LST statement

PDEST information POWER PUN statement

XDEST information POWER XMT statement

Note: If DISP=K is specified as a POWER override parameter and the job that isalready in the RDR queue has a disposition o f K or L, then after BIM-FAQS/PCSsubmits the member, there will be two jobs in the RDR queue: the original joband the one submitted with DISP=K. This happens because BIM-FAQS/PCScopies the member to a new member when submitting it.


2–22 BIM-FAQS/PCS


Chapter 3Activating the Scheduler

This chapter explains some of the startup requirements for BIM-FAQS/PCS. Italso explains the commands used to help control the BIM-FAQS/PCS jobscheduler.

OverviewPreparing to Activate the Scheduler

Before you activate the job scheduler, you should:

• Add appropriate SVA phases

• Enable data collection

Activating the Scheduler

The job scheduler can be activated:

• In a dedicated non-shared or shared batch partition

• As a subtask of CICS (not recommended for VSE/ESA 1.3 and above)

• As a subtask of a maintask

Managing the Scheduler

The functions performed by the scheduler control commands include:

• Handling events

• Initiating various interfaces

Preparing to Activate the Scheduler

3–2 BIM-FAQS/PCS

Preparing to Activate the SchedulerIntroduction

Once you've installed BIM-FAQS/PCS, you must take the following steps toensure quick and effective activation:

1. Add appropriate phases to SVA

2. Make sure JA=YES is specified as part of the IPL SYS statement

Adding Optional SVA Phases

You can add the following phases to the SVA (leaving more partition space):

• BIM$PV24,SVA (required if BIM-FAQS/ASO is not used)

• BIM$PV31,SVA (required if BIM-FAQS/ASO is not used)

• GSAOGEM,SVA (required if using CA-EXPLORE for VSE)

• JCLPOST,SVA

• PCSADR,SVA

• PCSSUC,SVA



Activating BIM-FAQS/PCS Hooks

Introduction

BIM-FAQS/PCS is activated in two stages: activating the optional $JOBACCT,$JOBEXIT, $$BOPEN, and $$BCLOSE hooks, and activating JCLSCHED, theBIM-FAQS/PCS job scheduler. The $JOBACCT hook is responsible for BIM-FAQS/PCS data collection. The $$BOPEN and $$BCLOSE hooks are responsiblefor dataset detection.

This section describes how to activate the BIM-FAQS/PCS job hooks. Rememberthat before doing this, you must load the BIM-FAQS/PCS product code. You canalso add the appropriate phases to the SVA.

Activating Job Hooks

The JCLXCU batch utility controls the job hooks and account logging using theENABLE and DISABLE control statements.

The ENABLE control statement activates BIM-FAQS/PCS hooks and enablesaccount logging. The following format is required for the ENABLE controlstatement:

ENABLE [LOAD=Y|N][,LOG=Y|N][,JOBX=$JOBEX0n][,DSN=Y|N][,DSNLOG=Y|N] [,DESKTOP=name] [,EVENTS=nnnnn]

The following table explains the function of each parameter in the ENABLEcontrol statement:

Statement Function

LOAD When BIM-FAQS/PCS is enabled, the event schedule will bereloaded. The default is Y.

LOG Enables job account logging. The default is Y.

JOBX This only applies to users that have VSE/ESA 1.2 or higher andthat use the JOBEXIT table. This parameter identifies the ten jobexits, which are specified in the JOBEXIT table. The default is$JOBEX00 (recommended).

DSN Enables dataset detection and activates $$BOPEN and$$BCLOSE hooks. The default is Y.

DSNLOG Enables dataset logging to the PDS. The default is Y.

DESKTOP This applies to users that have CA-Prevail/XP-Manager andwant BIM-FAQS/PCS event status routed to a remotedestination. This parameter identifies the GMF name whereevent status is routed. The default GMF name is DESKTOP.


3–4 BIM-FAQS/PCS

EVENTS Specifies the maximum number of Events that can be placed inSystem GETVIS. The number must be large enough to handlethe maximum number of events expected in the Current EventFile at any one time. Default value is 2048 Events, Max=15000.System GETVIS used will range from 4K to 472K with thedefault using 68K. ((32bytes* #evts)+32bytes) rounded to next4K.

The DISABLE control statement disables the BIM-FAQS/PCS hooks $JOBEXIT,$JOBACCT, $$BOPEN, and $$BCLOSE, and disables account logging. Thefollowing format is required for the DISABLE control statement:

DISABLE

JCL for Activating Job Hooks

The following example shows the JCL that activates BIM-FAQS/PCS and enablesthe optional account logging feature. In the ENABLE statement, LOAD=Nprevents the loading of the current event file at activation. The statement alsoactivates dataset detection and enables dataset logging along with an index filefor 3500 events.

// LIBDEF *,SEARCH=BIMLIB.PCS// EXEC JCLXCU,SIZE=JCLXCU ENABLE LOAD=N,DSN=Y,EVENTS=3500/*

Activating Hooks Before POWER Startup

You should activate BIM-FAQS/PCS using JCLXCU before POWER startup. Ifthe BIM-FAQS/PCS phases aren't activated then, you'll need to run a VSE jobthrough each partition to give control to the BIM-FAQS/PCS job exit.

IPL Requirements

Because data collection is performed by the $JOBACCT hook, you must specifyJA=YES in the ASI procedure on the IPL SYS statement.

Multiple-CPU Considerations

You must activate the $JOBACCT and $JOBEXIT hooks on every CPU used toschedule jobs, and on every CPU where BIM-FAQS/PCS job conditions occur.The job account and job exit hooks collect data, and if they're not active, BIM-FAQS/PCS can't detect VSE-related conditions.

Dataset Detection Considerations

The PCSSRV program must be active on all CPUs where dataset detection isused. PCSSRV monitors dataset activity and performs dataset logging.



Remote Scheduling Considerations

With BIM-FAQS/PCS, users can dispatch event commands to remote systems forexecution. However, for this remote scheduling feature to work properly, besure that PCSLOG, JCLSCHED and BIM$GMSR are executing on both thesending and receiving systems.

We recommend that your JCLSCHED.CTL member contain this command:

AUTO $PCSLOG

To test the communications protocol between systems, use the schedulercommand &RMT. To send commands from the console, use &REMCMD. Bothcommands are described later in this chapter.

Alternative Remote Scheduling Methods for VSE Systems

Method Explanation

1 JCLSCHED, PCSLOG, and BIM$GMSR execute on both CPUs.Also, your JCL resides on the remote (target node) system.

The scheduler identified in the Event Cpuid field on the onlineEvent Maintenance Edit screen ships the event command to theremote scheduler specified in the Target Node field. The remotescheduler issues the command or submits the job.

Once the command or job has completed, the remote system sendscompletion information to the originating scheduler (the CPUspecified in the Event Cpuid field), so it can update the eventstatus.

2 JCLSCHED, PCSLOG, and BIM$GMSR execute on the sendingsystem. Only PCSLOG and BIM$GMSR need to execute on thereceiving system. JCLSCHED is optional on the receiving system.

This method uses the existing VSE/POWER networking facilitiesof PNET. Your JCL must reside on the sending system (the CPUspecified in the Event Cpuid field on the online Event MaintenanceEdit screen).

3 After the job is submitted, it is routed by POWER to the remotesystem.

If you use this method, you must add ,RMT as the last parameter on the eventcommand. Parameter RMT causes the scheduler to tag the JCL. BIM-FAQS/PCSwill intercept the completion information and send it back to the originatingsystem so it can update the event status.


3–6 BIM-FAQS/PCS

Additional Startup Options

Introduction

With the JCLXCU utility, you can supply additional startup options.

Startup Options

The following options can be used with JCLXCU at startup:

Option Function

DMAXRC value Sets the default maximum return code used for anevent's WHEN condition. value must be four digits.

DABEND value Sets the default abend code used with job accounting.value must be four digits.

Sample Procedure

The following example shows the JCL that disables automatic loading of events,and sets a default maximum return code and abend code:

// LIBDEF *,SEARCH=BIMLIB.PCS// EXEC JCLXCU,SIZE=JCLXCUDMAXRC 0004DABEND 0003/*


For more information about the JCLXCU utility, see Chapter 12, “SubmittingCommands in a Batch Jobstream.”




Overview

Introduction

JCLSCHED, BIM-FAQS/PCS’ event scheduler program, schedules events anddispatches event commands that can:

• Schedule jobs

• Issue BIM-FAQS/PCS scheduler control commands

• Run REXX procedures

• Issue VM CP commands

• Issue VSE/POWER commands

• Issue operator commands

These functions can be executed alone or in any combination.

Where to Activate JCLSCHED

Introduction

You can start JCLSCHED in any one of the following areas:

• A dedicated non-shared or shared partition

• A subtask of CICS (not recommended for VSE/ESA 1.3 and above)

• A subtask of a main task

Activating JCLSCHED in a Partition

Use the following JCL to activate the scheduler as a main task in a batchpartition:

// JOB JCLSCHED// LIBDEF *,SEARCH=BIMLIB.PCS// EXEC JCLSCHED,SIZE=JCLSCHED/*

This JCL causes an outstanding reply ID on the console, enabling you tocommunicate with the scheduler. For example, you can respond to this reply IDby requesting that jobs be generated on demand.


3–8 BIM-FAQS/PCS

Activating JCLSCHED as a CICS Subtask

You can activate the scheduler as part of the CICS startup. You must enter theappropriate CICS table entries. This is not recommended for VSE/ESA 1.3 andabove.

For More Information: CICS table entries are required to start the scheduler as asubtask of CICS. For more information about using CICS to activate the BIM-FAQS/PCS scheduler, see Chapter 11, “Using CICS.”

Activating JCLSCHED as a Subtask

You can activate the scheduler as a subtask of a main task by using the BIM-GSSBIM$UTTS facility.

The following example shows the JCL used to run the scheduler as a subtask:

// LIBDEF PHASE,SEARCH=(BIMLIB.PCS)// EXEC BIM$UTTS,SIZE=mainsize,PARM='maintask#JCLSCHED'

maintask is the name of the main task under which the scheduler will run.mainsize is what is required to run the program specified as maintask. Whenspecifying SIZE=, do not use the value of AUTO. The AUTO keyword willautomatically startup the named commands in the jclshed.ctl member.



Before Using JCLSCHED

JCLSCHED Storage Requirements

The following table shows the storage requirements for the partition whereJCLSCHED runs:

To You need

Run BIM-FAQS/PCS 200K for phases loaded and 100K for schedulercommands.

Run BIM-FAQS/PCSand BIM-FAQS/ASO

200K for the phases loaded and 200K or moreGETVIS for running BIM-FAQS/ASO under thescheduler.

Edit members Up to 640K GETVIS. (You can get a patch fromBIM Technical Support if you need to increase ordecrease the maximum storage amount to editmembers.)

JCLSCHED Startup

When JCLSCHED starts up, it locates the JCLSCHED.CTL member in the BIM-FAQS/PCS SYS$MON PDS, reads it, and executes the commands found there.Some commands that may appear in JCLSCHED.CTL are:

AUTO &FAQSAOAUTO &FAQSVMXAUTO &EVLDOFF

Multiple-CPU Parameter

If you have multiple CPUs, you can use CPU=cpu_ID as a parameter with each ofthe AUTO statements to indicate the CPU IDs to which the statements apply. Ifused, CPU= must be the last parameter on the AUTO statement. cpu_ID can besix characters.

In the following example, the command AUTO $PCSSRV will be performed onlyon CPU ID 000001:

AUTO &FAQSAOAUTO $PCSSRV CPU=000001


3–10 BIM-FAQS/PCS

Activating PCSSRV

The PCSSRV program monitors all dataset activity and performs dataset logging.PCSSRV must be active on all CPUs where dataset detection will be used.

The following example shows the JCL used to run PCSSRV as a maintask:

// JOB PCSSRV// LIBDEF PHASE,SEARCH=BIMLIB.PCS// EXEC PCSSRV,SIZE=PCSSRV/&

To terminate PCSSRV when running as a maintask, enter the MSG command andthe partition ID in which PCSSRV is running:

MSG partitionID

The following example shows the JCL used to run PCSSRV as a subtask of theBIM-FAQS/ASO VMCF interface:

// JOB BIM$UTTS// LIBDEF PHASE,SEARCH=(BIMLIB.PCS)// EXEC BIM$UTTS,SIZE=FAQSVMX,PARM='FAQSVMX#PCSSRV'/&

To terminate PCSSRV when running as a subtask, terminate the maintask.

Note: You can also subtask PCSSRV under the scheduler. To do so, add anAUTO $PCSSRV statement in the JCLSCHED.CTL SYS$MON PDS file.



When JCLSCHED Is Activated

Introduction

When JCLSCHED is activated, the following actions occur:

1. Commands in the JCLSCHED.CTL member are processed.

2. A console prompt is displayed.

3. Events are processed.

4. A wait is entered on the timer and console.

Entering Console Commands

The console prompt enables you to enter commands into JCLSCHED. When youenter a command from the console, the requested action is performed and thestatus (if any) is reported on the console. The console prompt displays at thecompletion of each command.

Using JCLSCHED Commands

Because JCLSCHED supports many facilities, you or the system can enter avariety of scheduler control commands. These commands are outlined in thefollowing section.


3–12 BIM-FAQS/PCS

Detecting Messages When JCLSCHED Is Not Active

Message Processor

You can activate the message processor as a subtask of a main task by using theBIM$UTTS facility. The message processor scans the BIM-FAQS/ASO messagetable for messages that BIM-FAQS/ASO has detected and updates the events toindicate the message has been detected.

Use the message processor only when JCLSCHED is not active on a systemwhere messages are to be detected. For example, use the message processor on aCPU in a multi-CPU environment that is not running JCLSCHED.

JCL

The following example shows the JCL used to run PCSMSG as a maintask:

// JOB PCSMSG// LIBDEF PHASE,SEARCH=BIMLIB.PCS// EXEC PCSMSG,SIZE=PCSMSG/&

To terminate PCSMSG when running as a maintask, enter the MSG commandand the partition ID in which PCSMSG is running:

MSG partitionID

The following example shows the JCL used to run the message processor as asubtask of the BIM-FAQS/ASO VMCF interface:

// JOB BIM$UTTS// LIBDEF PHASE,SEARCH=(BIMLIB.PCS)// EXEC BIM$UTTS,SIZE=FAQSVMX,PARM='FAQSVMX#PCSMSG'/&

To terminate PCSMSG when running as a subtask, terminate the maintask.

Note: To be sure message detection occurs across CPUs, the SYS$MON PDSmust be shared by those CPUs.




Scheduler Control Commands

Introduction

Scheduler control commands help to manage JCLSCHED by handling event files,initiating interfaces, and performing various other functions.

Commands

Command Function

&ALERTVSE Initiates the BIM-ALERT/VSE logger task.

&AO membname Runs the REXX membname procedure. This requiresthe FAQS AO subtask to be active(e.g., &FAQSAO).

&CMS cmd Submits the specified command to run on the BIM-FAQS/PCS CMS server.

&COFF Disables console input.

&CON Enables console input.

&CP vmcmd Issues VM command.

&EVIO n Changes event file scan interval.

&EVLDOFF Disables automatic loading of events at midnight.

&EVLDON Enables automatic loading of events at midnight.

&EVLOAD Loads new events in the current event file and deletesevents completed during the previous processingperiod from the event file.

&EVNAME Displays the event name on the console when theevent is scheduled.

&EVOFF Disables the event scheduler.

&EVON Enables the event scheduler.

&EVRLOAD Deletes and reloads the current event file.

&EVTEST Controls event scheduling simulation.Continued


3–14 BIM-FAQS/PCS

Continued

Command Function

&FAQSAO Subtasks the BIM-FAQS/ASO REXX processor.

&FAQSIUX Subtasks the BIM-FAQS/ASO IUCV interface.

&LOADMSG Rebuilds the message table for events in the currentevent file.

&LOADTIME Loads events at a specified time.

&REMCMD Sends a scheduler command to the specified remotesystem.

&RMT Tests the LU 6.2 connection between systems.

&SECLD Loads security in the partition where the scheduler'srunning.

&TERMINATE Ends the scheduler.

$phasename Loads and attaches the phase as a subtask.



Loading Events Into the Current Event File

Introduction

Before event processing can occur, events must be loaded into the current eventfile.

The following commands affect how events are loaded into the current event file:

• &EVLOAD

• &EVRLOAD

• &EVLDON and &EVLDOFF

• &LOADTIME

&EVLOAD

The &EVLOAD command makes newly created events available for the currentday's schedule. &EVLOAD takes events from the master event file, which do notexist in the current event file for the current processing period, and merges theminto the current event file. &EVLOAD does not replace the existing current eventfile with a new one; rather, it updates the existing file with new events.

When you issue &EVLOAD, the events portion of BIM-FAQS/PCS searches themaster event file for the events eligible for the current processing period andplaces those events in the current event file. If an event is added to the masterevent file during the day, you can use the &EVLOAD command to move it to thecurrent event file.

&EVLOAD also deletes events from the current event file that have completedduring the previous processing period.

To load the current event file at a time other than midnight, use &LOADTIME toset the desired event load time. See &LOADTIME below for more information.

&LOADMSG: This command rebuilds the message table for events in thecurrent event file. Use &LOADMSG when events with message predecessorconditions are defined from CPUs other than the one the message will bedetected on--for example, if you are using CMS. You can also use &LOADMSGwhere the same schedule is shared by multiple systems. So one system can use&EVLOAD to load the schedule, and the other can use &LOADMSG to rebuildthe message table.

&EVRLOAD

Much like the &EVLOAD command, the &EVRLOAD command creates thecurrent event file for the current processing period. The difference between&EVLOAD and &EVRLOAD is that &EVRLOAD deletes the existing currentevent file before it extracts the proper events from the master event file.


3–16 BIM-FAQS/PCS

If you want to load a schedule for a specific date other than the currentprocessing period, specify yy/mm/dd after &EVRLOAD.

Loading Event Groups

With &EVLOAD and &EVRLOAD, use the G=mask parameter to load or reloadevents to the current event file by group mask. The format of this parameter is:

&EVLOAD [G=mask]&EVRLOAD [yy/mm/dd] [G=mask]

The optional parameter G=mask indicates a 1-to-8-character mask for an eventgroup. This can be either a specific or generic name. Both an asterisk (*) and aplus sign (+) create generic masks:

An asterisk (*) represents an unconditional match on a group of characters.

A plus sign (+) represents an unconditional match on a specific character.

The default value is asterisk (*), meaning all event groups are loaded.

When you use &EVLOAD or &EVRLOAD with the G=mask parameter, onlygroups that match the mask and are defined to be scheduled that day are loaded.With &EVRLOAD, the G=mask parameter must follow the date parameter.

In the following example, &EVLOAD merges new events from groups startingwith PAY into the current event file. Any events with the same name andscheduling day as those already in the current file will not be added.

&EVLOAD G=PAY*

In the following example, &EVRLOAD deletes all events in groups starting withPAY and then merges all PAY groups into the current event file:

&EVRLOAD G=PAY*



&EVLDON and &EVLDOFF

The &EVLDON command enables the scheduler to reload and update thecurrent event file at midnight. (Midnight is the system default when &EVON isspecified.)

To disable automatic event loading, use &EVLDOFF. Then you can issue&EVLOAD to load the current event file manually.

&LOADTIME

The &LOADTIME command alters the automatic loadtime default of midnight.

Before you use this command, &EVLDON and &EVON must be set (they are setby default). If either of these is not set, no load occurs.

The format of the command is as follows:

&LOADTIME [nnnn]

The optional parameter nnnn is the time of day, on a 24-hour clock. Values are0000-2359; the default is 0000 (midnight).

If you use the &LOADTIME command with no parameters, the current setting of&LOADTIME will be displayed at the console. If you enter a time-of-day valuethat is out of the valid range, the current setting will be displayed.

As an example, if at 8 a.m. (0800), you specify &LOADTIME 0900, the event loadwill occur at 9 a.m. If you specify &LOADTIME 0900 at 10 a.m. (1000), the eventload will not occur until the next day at 9 a.m.

Add the &LOADTIME command to your JCLSCHED.CTL member if you wantthe load to run automatically at a specified time (other than midnight) every day.

To turn off the automatic load, use the &EVLDOFF command.


3–18 BIM-FAQS/PCS

Controlling Event Processing

Introduction

You can control how events will be processed by entering the appropriatecommands independently on the console, in the JCLSCHED.CTL startup file, orby scheduling event commands as events themselves.

The following commands control how events are processed:

• &EVON and &EVOFF

• &EVIO n

• &EVNAME

• &EVTEST and &EVTEST OFF

&EVON and &EVOFF

When JCLSCHED is initiated, the scheduler is automatically enabled. In otherwords, event scheduling begins by default. The &EVON command enables eventscheduling.

&EVOFF disables the event scheduling until an &EVON command isencountered.

&EVIO n

The scheduler is designed to look for the occurrence of events. The &EVIO ncommand changes how often the scheduler scans the current event file for achange. n represents 5-second intervals. The default is 15 seconds (&EVIO 3).

On a non-shared, native-VSE system, n may reach a maximum of 60, whichwould make the scan interval every 5 minutes.

&EVNAME

Use the &EVNAME control command to control whether the event name isdisplayed on the console when the event is scheduled.

The format of the command follows:

&EVNAME ON|OFF

The default is OFF.



&EVTEST

&EVTEST enables event scheduling simulation. &EVTEST enables you to runbut not execute all event-driven jobs or commands. JCLDUMMY is substitutedfor the normal program name on EXEC statements and performs no operation(that BIM-FAQS/PCS will process).

You can submit jobs manually while in test mode.

The format of the command follows:

&EVTEST ON|OFF

&EVTEST OFF disables event scheduling simulation.

Note that BIM-FAQS/PCS comments out SLI cards during processing. So SLIcards are treated as comments and are not processed.

Also note that in test mode the EXEC PROC= statement is changed to a commentso that the specified procedure is not executed. The following shows the formatof an EXEC statement in test mode:

/* EXEC PROC=name


3–20 BIM-FAQS/PCS

Initiating Interfaces Used by the Scheduler

Introduction

Using scheduler control commands, you can initiate the following systeminterfaces either on the console or in the JCLSCHED startup file:

• Online interfaces for BIM-FAQS/ASO

• The BIM-FAQS/ASO REXX processor

• Any other subtaskable program ($)

• The BIM-ALERT/VSE logger task

&FAQSIUX

The &FAQSIUX command initiates the BIM-FAQS/ASO IUCV interface. If theinterface is already active, the request is bypassed.

&FAQSAO

The &FAQSAO command sets up the interface to use REXX IMODs. It initiatesthe online interface through BIM-FAQS/ASO in the partition where thecommand is executed. &FAQSAO enables you to run REXX IMODs and usemessage features.

&AO membname: This command causes the scheduler to execute the REXXprocedure membname. REXX procedures reside in the MON PDS with data typeOAL. REXX procedures executed using the &AO command do not generatePOWER output. If you want POWER output, call REXX procedures from anBIM-FAQS/PCS-generated job.

$phasename

To attach and load a subtask, prefix the appropriate scheduler command with $.For example, $FAQSVMX attaches the FAQS VMCF interface.

&ALERTVSE

Use the &ALERTVSE command to initiate the logger task for BIM-ALERT/VSE.If the logger task is already active, the request is bypassed.



Miscellaneous Commands

Introduction

The miscellaneous control commands affect the scheduler, but not in relation toevents or interfaces.

&CON and &COFF

The &CON command enables outstanding reply IDs to occur in the partitionwhere &CON is executed. This enables operator input on the console.

To disable console reply, use &COFF. This command prevents the occurrence ofoutstanding reply IDs in the partition. To temporarily enable console reply,enter MSG pid. If you enter &CON, you can enable console reply permanently.This only works when the scheduler is the main task.

OCCF Users: If you are using the IBM OCCF feature, you must issue the &COFFcommand to prevent outstanding reply IDs.

&CP vmcmd

To issue VM/CP commands, use &CP vmcmd. This command allows you to passthe CP command parameters to VM. Resulting responses are displayed on theconsole.

&CMS cmd

The &CMS command enables you to execute commands on the BIM-FAQS/PCSCMS server. To issue commands such as VM/CP commands or CMS REXXprocedures, use &CMS cmd.

Note that the server must have access to the resources specified in the command(cmd) in order to execute the command.


3–22 BIM-FAQS/PCS

PCSLOG: Reducing Overhead to Improve Performance

Introduction

Use the PCSLOG task to improve the performance of BIM-FAQS/PCS. The$JOBACCT processing done at the end of each step and at the end of a job iseliminated from the partition and is handled by PCSLOG. PCSLOG can run as amaintask or subtask.

PCSLOG is recommended; it can save at least three I/O actions per jobstep andwill noticeably decrease the time it takes to run a job.

If you are using remote scheduling, the use of PCSLOG is mandatory.

Running PCSLOG as a Subtask

On a system where JCLSCHED is running, you can specify PCSLOG in theJCLSCHED.CTL member as a subtask, using the command AUTO $PCSLOG.

Running PCSLOG as a Maintask

On a system where JCLSCHED is not running, you should run PCSLOGwherever you have enough space, in a fairly high priority partition. Use JCLsimilar to the following for running as a maintask. You could also run it as asubtask using, for example, the BIM-GSS utility BIM$UTTS.

// JOB PCSLOG// LIBDEF *,SEARCH=BIMLIB.PCS// EXEC PCSLOG,SIZE=PCSLOG/&

If PCSLOG runs as a maintask, issue the command MSG partition (for example,MSG F6) when you want to shut it down.


Chapter 4Job Generation

This chapter covers the basics of BIM-FAQS/PCS job generation: JCLcomponents, generation commands, and the overrides for those commands.

OverviewThis chapter explains the following basics of BIM-FAQS/PCS job generation:

• JCL components of simple and multi-step jobs

• Commands that generate jobs once the JCL is defined

• Overrides that change values within existing job JCL at the point of jobgeneration

• Reviewing JCL prior to submission

Job Terminology

4–2 BIM-FAQS/PCS

Job TerminologyThe following terms are basic to an understanding of JCL and job generation.

Job A job is one or more steps presented to VSE for execution as a single unit of work.In BIM-FAQS/PCS a job is a single POWER or VSE job generated by one BIM-FAQS/PCS command.

Jobs are identified in JCL with POWER JECL job statements (* $$ JOB). If no jobstatement is used, BIM-FAQS/PCS generates a POWER JECL job statement (* $$JOB JNM=jobname) with the same name as the VSE job statement, orAUTONAME if the VSE job statement is not the first statement.

JCL JCL (job control language) defines what a job does and describes its systemenvironment.

Job Step A job step is each program within a job or the execution of a program explicitlyidentified by a job.

During job restarts, steps are used as restart points for existing jobstreams. InJCL, steps are identified by step headers.

Jobstream A jobstream is a series of JCL statements, possibly combined with some data to beprocessed.

Member A member is a library entry containing one or more JCL statements. Statementsidentify control and user information.

BIM-FAQS/PCS job generation commands generate jobs by calling members.

Nested Call A nested call is a statement that calls a job outside of the current jobstream. Jobscall other jobs using PROC statements.

JECL JECL (job entry control language) supplements JCL to control POWERoperations. JECL directs POWER's job scheduling and output spooling functions.

JECL statements begin with an asterisk, followed by a space, followed by twodollar signs, followed by another space (* $$ ). When cataloging members to thePDS, use * DD to identify JECL statements. At job submission, BIM-FAQS/PCStranslates JECL stored as * DD to * $$.

JCL Jobstream Examples



Overview

Introduction

This section shows the range of JCL that can be applied to generate jobs withBIM-FAQS/PCS.

Job Components

The sample jobs in this section include some of the basic JCL statements, such asJOB, ASSGN, TLBL, and EXEC statements.

One-Step Job

Introduction

The simplest job executes one program without nested calls. Initial JCL and stepscan be included as part of the job.

Because the system generates the ending slash ampersand (/&) statement in ajob, you don't have to catalog that statement as part of the library member.

Example

The following example shows the JCL required to generate the job JCLBU:

// JOB BACKUP BIM-FAQS/PCS LIBRARY// ASSGN SYS010,X'280'// TLBL GSPDSO,'BU.MON'// EXEC BIM$PUTL,SIZE=BIM$PUTLPDS=MON,BACKUP/*/&


4–4 BIM-FAQS/PCS

Multi-Step Job Without Nested Calls

Introduction

A job can have multiple steps. Step headers in the job identify each new step.

With multiple step headers in a job you can use the restart parameter. And if astep header format is defined using the PROCMNT configuration option, you canrestart at any VSE comment statement.

Example

The following sample jobstream has the multiple steps, JCLCBUM - BACKUPBIM-FAQS/PCS MON PDS and JCLBUV - BACKUP BIM-FAQS/PCS VIO PDS:

// JOB BACKUP PDS/. JCLBUM - BACKUP BIM-FAQS/PCS MON PDS// ASSGN SYS010,X'280'// TLBL GSPDSO,'BU.MON'// EXEC BIM$PUTL,SIZE=BIM$PUTLPDS=MON,BACKUP/*/. JCLBUV - BACKUP BIM-FAQS/PCS VIO PDS// ASSGN SYS010,X'280'// TLBL GSPDSO,'BU.VIO'// EXEC BIM$PUTL,SIZE=BIM$PUTLPDS=VIO,BACKUP/*/&

Restarting Jobs Using Step Headers

To restart the job BACKUP at its second step, enter BACKUP,S=JCLBUV. Therestart point is the VSE comment statement JCLBUV - BACKUP BIM-FAQS/PCSVIO PDS.



Multi-Step Job with Nested Calls

Introduction

A job can have multiple steps, with each step residing in a separate member.Steps are called using PROC statements in the calling job.

Example

The following jobstream shows the initial JOB statements and the nested calls (./PROC) for each of the steps in the job BACKUP:

* $$ JOB JNM=BACKUP// JOB BACKUP./ PROC JCLBUM./ PROC JCLBUV

BACKUP includes the members JCLBUM and JCLBUV.

/. JCLBUM - BACKUP BIM-FAQS/PCS MON PDS// ASSGN SYS010,X'280'// TLBL GSPDSO,'BU.MON'// EXEC BIM$PUTL,SIZE=BIM$PUTLPDS=MON,BACKUP/*/. JCLBUV - BACKUP BIM-FAQS/PCS VIO PDS// ASSGN SYS010,X'280'// TLBL GSPDSO,'BU.VIO'// EXEC BIM$PUTL,SIZE=BIM$PUTLPDS=VIO,BACKUP/*/&

Restarting Jobs Using Step Headers

To restart the job BACKUP at its second step, enter BACKUP,S=JCLBUV. Therestart point is the ./ PROC JCLBUV statement.


4–6 BIM-FAQS/PCS

Job with User Variable

Introduction

More complex jobs can contain user variables or conditional generationstatements.

You can use PCL to define default variable values. For more information aboutsubmitting user variables using PCL |PARM statements, see the BIM-FAQS/PCSOperations Guide.

Example

The following sample jobstream contains a |PARM statement that defines theuser variable &TAPE. Because the |PARM statement defines it, wherever&TAPE occurs in this job, it is replaced with DAILY.

|PARM &TAPE='DAILY'* $$ JOB JNM=ICCFBKRS,CLASS=2// JOB ICCFBKRS BACKUP/RESTOR ICCF LIBRARY// ASSGN SYS005,TAPE// ASSGN SYS010,DISK,VOL=SYSWK1,SHR// TLBL DTSBKUP,'ICCF.&TAPE.BACKUP'// EXEC DTSUTILBACKUP/*// ASSGN SYS004,SYS005// TLBL DTSRSTR,'ICCF.&TAPE.BACKUP'// EXEC DTSUTILRESTORE/*/&* $$ EOJ

Variable Substitution

When a variable is replaced by a variable value, the whole statement may beaffected because of the length replaced. For example, if the substituted value isshorter than the variable name (including the ampersand), the statement shiftsleft. And if the substituted value is longer than the variable name, the statementshifts right.

Variable Overrides

You can override values for user variables. See "Override Parameters" later inthis chapter.

Job Generation Commands



Overview

Introduction

For scheduling purposes, you can generate jobs in several ways:

• As part of an event command

• As a reply to a scheduler partition

• Using the JCLXCU batch utility

• Within another member (as a nested member)

• From a BIM-FAQS/ASO-supported interface

• From a BCIN CMS interface or BCIN CICS interface

Job generation commands can include generation overrides as parameters.Override parameters are described later in this chapter.

Job Generation Command FormatAll job generation commands have a jobname within their format. If a JCLmember does not reside in the PDS, use proper naming conventions. For moreinformation on accessing members from different JCL libraries for job generation,see Chapter 2, “Storing JCL.”

In order to Use this format

Pass commands to the scheduler(JCLSCHED), either as:

• Part of an event command

• A reply to the schedulerpartition

membname

Request a member from a CMSserver, if using JCLSCHED toschedule a job

&SUB filename.filetype.filemode

Pass commands by JCLXCU GEN membnameContinued


4–8 BIM-FAQS/PCS

Continued

In order to Use this format

Request a member from a CMSserver, if using JCLXCU toschedule a job

SUB filename.filetype.filemode

Nest a member within a memberin a jobstream

./ PROC membname

Pass commands from aBIM-FAQS/ASO-supported orBCIN interface

.membname

Exception: Nested Members in CMS

Members referenced by PROC statements in CMS server JCL must reside in theBIM-FAQS/PCS PDS.

Jobs Passed to POWER via XPCC

Jobs generated by BIM-FAQS/PCS are passed to POWER via the XPCC interface.Support for XPCC must be specified at POWER installation.

POWER SLI Support

BIM-FAQS/PCS can schedule jobs using POWER SLI (source library-memberinclusion). However, BIM-FAQS/PCS can't expand any variables found in theSLI member.



Generating Jobs as Part of an Event Command

Introduction

The most common way to generate a job is by using an event command from theCurrent Event Maintenance Screen.

Sample Current Event Maintenance ScreenThe following sample screen shows job generation for the event PCS1:

JOLEVT .Z ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q013===>

** Event Maintenance for File=MASTER --- Status=Mast **

Event Name ===> PCS1 Group Name ===> Description ===> TEST NEW PARM Event Hold ===> N Event Cpuid ===> DEVVSE ABND RC ===> Command ===> MON:PCS,C=7,&DAY='LAST' CSPD ===> 5___ Target Node ===>

Early Time ===> 0600 Late Time ===> 3000 Abort Time ===> 3000 XDATE OR ¬ MTWTFSS CYCLE H Hol-id W Event Day ===> FRI ___ _ _ _______ 000 _ 000 _ Occurrences ===> Frequency ===> Start Date ===> End Date ===>

When Cond. ===> N Successors ===> N Variables ===> N Data Sets ===> N Tape Reels ===> 00 Cartridges ===> 00 Resources ===> N Excl type ===> Exclude ===> ________ ________ ________ ________ ________

PF1=Hlp PF2=Tra PF3=Ret PF4=Upd PF5=New PF8=Fwd PF9=Del PF10=When PF11=For

Event Command

You can submit job generation commands and override parameters in the inputarea to the right of the Command field (Command ===>). When the event runswith a command in this field, this command is executed.

Example: In the sample screen, when the event PCS1 is run, the member PCS inthe MON PDS is run, changing the POWER class to 7, and substituting LAST forthe &DAY user variable.

POWER Overrides

On the Current Event Maintenance Screen, values for POWER class, system ID,priority, and disposition entered in the Command field override the same valuesin the CSPD field.

Example: For the event PCS1, POWER class 5 is defined in the CSPD field underC. Because the Command field contains a POWER class override (C=7), thePOWER class used is class 7.

Override Parameters

4–10 BIM-FAQS/PCS

Override Parameters

Overview

The rest of this chapter describes parameters you can use to override jobgeneration commands. Override parameters apply to all job generationcommands, and can replace all occurrences of the override value in a JCLmember.

You can also use override parameters when calling nested members (using ./PROC). See the following list of these parameters.

Assumption

Override parameter format and examples are described only as they relate tooverrides passed to the scheduler.

The following basic format is used for job generation commands with overrideparameters:

jobname,parameters

Override Parameters


Override Parameters

The following override parameters can accompany a jobname when it isscheduled:

Parameter Format Function

Start=strtstep:endstep Restarts a job starting at strtstep and ending just prior toexecuting the ending step endstep

End=endstep Restarts a job starting at the beginning of the job andending just prior to executing the specified ending stepstepname

RERUN Reruns a job by inserting the JCLRERUN.CTL memberthrough a nested member call after the first VSE jobstatement is found

Class=n Overrides POWER job class

SYSID=n Overrides POWER SYSID (if there's shared spoolsupport)

PRI=n Overrides POWER job priority

DISP=n Overrides POWER job disposition

cua=cua,... Overrides device referenced on ASSGN statement

SYSnnn=cua Overrides SYS logical unit referenced on ASSGNstatement

UPSI=nnnnnnnn Overrides UPSI value

PGM=oldname=newname Changes phase name on EXEC statements

PROC=oldname=newname,... Changes member name on PROC statements

DATE=mm/dd/yy Overrides // DATE value. If yy is less than 50, it isassumed to be year 20yy.

DEBUG Tests JCL, generating an EXEC of the JCLDUMMYutility

&variable=value Overrides the user-variable value of the jobname. Thismust be the last override parameter.

DATA=Y Suppresses variable substitution for a nested membercall

Override Parameters

4–12 BIM-FAQS/PCS

Multiple Overrides

Any number of overrides can be supplied in any sequence. To continue consoleinput, end a parameter with a comma and a space. A maximum of eightcommand lines (or 512 characters) of parameter data is supported.

Example: Enter the following command in order to

Generate the PAYROLL job with the scheduler running in F3

Change the POWER class to B, assignments for 380 to 381, and the UPSI value to01000000:

3 PAYROLL,C=B,380=381,UPSI=01000000

Overrides as Part of Nested Member Calls

Multi-step jobs with nested member calls (./ PROC membname) can include thefollowing override parameters:

• cua=cua,...

• SYSnnn=cua

• UPSI=nnnnnnnn

• PGM=oldname=newname

• PROC=oldname=newname,...

• DATE=mm/dd/yy

• &variable=value (This must be the last override parameter)

• DATA=Y

Override Parameters


Restarting Jobs

Introduction

You can restart a job at a specific point, designated as a step (as defined by thePROCMNT configuration option). Additionally, using a single statement, youcan restart a job at a specific point then end it at a specific point. A step can be aVSE comment or a nested member call (./ PROC). To perform a restart, youmust know the name of the step where you want to start; and if ending at aparticular point you must know that stepname also.

Optional Omission of POWER JECL

Through BIM-FAQS/PCS configuration, you can specify whether to save JECLstatements before a job is restarted. POWER JOB, LST, and PUN statements aresaved by default. However, POWER RDR or SLI statements prior to a restart arenot saved by default.

All POWER JECL statements, based upon whether they are JOB, LST, PUN, RDR,or SLI statements, are generated up to the specified restart point. After the firstVSE job statement is output, the contents of the JCLRSTRT.CTL member areinserted as though a nested member call was made. All other statements prior tothe specified restart point are omitted.

All statements up to any of the following statements are saved:

• // EXEC (VSE EXEC card)

• |LABEL (PCL label card)

• |STEP (PCL label card)

• /. (VSE label card)

Using the JCL restart card retention option on the Global Configuration OptionsScreen, you can specify if and which types of statements are retained when a jobis restarted.

If the restart point is not found, an error message is produced and no job is run.

For More Information: For more information about retaining JECL statementsupon restart, see Chapter 5, “Defining System Configuration.”

Restarting a Job Using a Range

You can use the End= statement to restart a job starting at the beginning of thejob and ending just prior to executing the specified ending step.

Override Parameters

4–14 BIM-FAQS/PCS

The following format is required to terminate a job at a step other than the end ofthe job.

jobname,End=endstep

Everything up to, but not including endstep, will be included as part of the restart.

Format

The following format is required to restart a job at a specific step.

jobname,Start=stepname

The following format is required to restart a job at a specific starting step and toend just prior to executing the specified ending step:

jobname,Start=strtstep:endstep

Start= can be abbreviated to S=.

Example

The following command generates the job PAYROLL without any steps beforePAYSTEP2:

3 PAYROLL,Start=PAYSTEP2

Exception: .CTL Members

Member names with the .CTL suffix are output without regard to the Start=restart request. This exception permits the JCLRSTRT.CTL member to be outputafter the VSE job statement.

Note: The .CTL suffix is normally reserved for BIM-FAQS/PCS system use.

PROCMNT Option

The Start= parameter restarts at either a matching PROC, |LABEL, |STEP, /.VSE label, or a matching VSE comment if the PROCMNT batch configurationoption is defined. PROCMNT defines the format of a restart command. Thedefault format is STEP *, which can be changed. STEP * starts matching in thefirst non-blank column after column two of each comment statement.

Example: The following sample JCL comment statement (* ) uses the STEP *format:

* STEP JCLCOND1 - BACKUP BIM-FAQS/PCS LIB TO TAPE

For information about defining the default step header format as a globalconfiguration option, see Chapter 5, “Defining System Configuration.”

Override Parameters


Changing POWER Job Values

Introduction

You can override the following POWER job defaults and substitute specificvalues for them:

• Class

• System ID

• Priority

• Disposition

Format for Overriding POWER Class

The following format is required to override the POWER class for a job:

jobname,Class=n

n is a POWER class (0-9, A-Z). Class can be abbreviated to C. C=* causes the jobto be scheduled where the command is processed. If jobname has a POWER classdefined, that class is overridden by a C=n command.

Format for Overriding POWER SYSID

The following format is required to schedule a job to a specific POWER SYSID:

jobname,SYSID=n

n is any numeric SYSID from 1-9. To override a SYSID, you must have sharedspool support.

Format for Overriding POWER Priority

The following format is required to override the POWER job priority:

jobname,PRI=n

n is any numeric priority from 1-9.

Override Parameters

4–16 BIM-FAQS/PCS

Format for Overriding POWER Disposition

The following format is required to override the POWER job disposition:

jobname,DISP=n

n can be POWER disposition D, H, L, or K.

Event Maintenance Screen Overrides

POWER overrides entered as part of an event command on the EventMaintenance Screen take precedence over the POWER values entered in theCSPD fields on the same screen.

Override Parameters


Overriding Device Assignments

Introduction

You can temporarily override device assignments for a job by changing either theCUA or the SYS logical unit found on ASSGN statements. No change is made tothe member on the disk file.

Format

The following format is required to submit a job and change any deviceaddresses on ASSGN statements:

jobname,cua=cuajobname,SYSnnn=cua

cua can be a 3-character CUA.

Examples

The following examples show temporarily overridden device assignments for thejobname PAYROLL:

Example Explanation

3 PAYROLL,280=284 Changes all assignments temporarily from280 to 284

3 PAYROLL,SYS010=282 Changes all assignments for SYS010 to 282

3 PAYROLL,280=281,281=280 Exchanges devices within a single job(280 becomes 281, and originalassignments for 281 become 280)

Override Parameters

4–18 BIM-FAQS/PCS

Changing UPSI, EXEC, PROC, and DATE Values

UPSI Values

You can override UPSI values in members. The following format is required:

jobname,UPSI=nnnnnnnn

If you specify UPSI= but no UPSI statement is found in the member, no UPSI isgenerated.

Example: The following command changes the UPSI value for the jobnamePAYROLL to 00001000:

3 PAYROLL,UPSI=00001000

EXEC Values

You can change program phase names on EXEC statements. The followingformat is required:

jobname,PGM=oldname=newname

If the specified phase name is executed more than once, the replacement isperformed for each occurrence. You can specify only one phase name.

Example: The following command changes all EXECs for PAYOLD to PAYNEW:

3 PAYROLL,PGM=PAYOLD=PAYNEW

Override Parameters


PROC Values

You can update member names on PROC statements. The following format isrequired:

jobname,PROC=oldname=newnamejobname,PROC=(old1=new1,old2=new2)

Example: The following command replaces the dummy member JOBDATA witha member name JOB0024.

3 JOB6,PROC=JOBDATA=JOB0024

In a case like this, you may want to catalog a member under the dummy namethat contains a null data stream. This allows the member to be used with orwithout optional data statements.

Rules: The following rules apply when changing PROC member names:

1. If you try to override a member name generated by system variable(&&PARAM) substitution, the name is matched.

2. If you supply a Start= parameter that skips PROC= override, no substitutionis made.

3. If you try to override a member name whose member cannot be found, thecommand is bypassed.

DATE Values

You can change VSE DATE (// DATE) statement values. The following formatis required:

jobname,DATE=date

If you specify DATE= but no DATE statement is found in the member, no DATEstatement is generated. date format is based on your VSE system date definition.

Example: The following command changes any VSE DATE values in memberPAYROLL to read 02/01/91 in the generated job:

3 PAYROLL,DATE=02/01/91

Override Parameters

4–20 BIM-FAQS/PCS

Testing JCL

DEBUG

You can specify the DEBUG parameter to generate a jobstream to test JCL. If youspecify DEBUG, the jobstream generator functions and any // EXEC statementsare changed to generate an EXEC of the JCLDUMMY utility. JCLDUMMYdisplays on the printer any EXEC statement input and goes to end-of-job. Allnormal VSE JCL error checking is still performed.

Format

The following format is required to submit a job in test mode:

jobname,DEBUG

Example

The following command generates the job JOB6 in test mode:

3 JOB6,DEBUG

CAUTION!

POWER SLI cards with EXEC statements can not be read by DEBUG.

Override Parameters


Overriding User Variables

Introduction

You can change user variables that occur in JCL. User variables are identified bya single ampersand (&).

You can override variables set by JCL or PCL.

Format

The following format is required to submit user variable overrides:

jobname,&variable=value

Rules

The following list explains the guidelines for submitting user variable overrides:

• variable is a 1-to-8-character string.

• value is a 0-to-255-character string.

• A value containing special characters must be delimited by single or doublequotation marks.

• All other override parameters must be specified before the first user-variableoverride parameter.

• A user variable list can consist of one or more variables and their associatedvalues.

Examples

The following examples show how to specify other override parameters withuser variable overrides:

Example Explanation

PAYROLL,Class=6,UPSI=1000,&DAY=LAST The job PAYROLL isgenerated in class 6, with aUPSI value of 1000, and theuser variable &DAY is set toLAST.

JOBTEST,&B='20',&CARDCODE='A' The job JOBTEST isgenerated with the uservariable &B set to 20 and&CARDCODE set to A.

Override Parameters

4–22 BIM-FAQS/PCS

Suppressing Variable Substitution

Use DATA=Y to suppress variable substitution for a nested member call (PROCstatement). Suppression of variable resolution is useful for data containingampersands (&) that shouldn't be interpreted as PCS variables. In other words,you can use DATA=Y to preserve variable definitions (& statements).

Example: The following command bypasses all ampersands in a job:

jobname,DATA=Y

Reviewing JCL Before Submission



JCLTRACE Utility

Introduction

The JCLTRACE utility enables you to display JCL statements before they'resubmitted in a jobstream. In this way you can see the results of your JCL,including resolved variables and nested member calls, before you execute it. Youcan use JCLTRACE to debug or scan a JCL member before executing it.

JCLTRACE generates an online display or hard copy printout of the JCL to beused by POWER, as if a job generation command had processed the member.

All security checking and error logging are performed as though a job generationcommand was submitted. This can result in extraneous error messages on theoperator console. All parameters normally supplied by the system operator musteither be part of the member call or supplied by the operator.

TRACE Command

You can enter ./ TRACE membname instead of ./ PROC membname and submit ajob. TRACE temporarily enables trace output for a single member.

Required JCL

The following JCL is required to run JCLTRACE:

// JOB JCLTRACE// LIBDEF PROC,SEARCH=BIMLIB.PCS// EXEC PROC=JCLTRACE./ TRACE membname./ END/&


4–24 BIM-FAQS/PCS

Executing JCLTRACE Under ICCF

The following commands invoke JCLTRACE under ICCF:

* @JCLTRACE membname&&OPTIONS 0010001/INP&/LOAD JCLMAN/ASSGN SYS009,READER/OPTION GETVIS=P-60K&/UPSI 10010000./ TRACE &&PARAM1./ END/END/PEND$

If the trace function JCLTRACE is run under ICCF, the terminal user receives theresulting console dialog. JCLTRACE is a macro invoked by the @JCLTRACEmembname statement.

Output

JCLTRACE output is sent to the printer (SYSLST) or terminal rather than thePOWER reader queue. Any POWER job boundaries are identified on theresulting display or printout.

Disabling Address Environments

When a REXX IMOD is executed from either the PCS or BIM editor via theTRACE command or by using the batch program JCLTRACE, the followingREXX functions are disabled:

• ADDRESS CICS

• ADDRESS POWER

• ADDRESS CONSOLE

• ADDRESS SCHEDULE

• ADDRESS EVENT (except for LIST)

• ADDRESS PDS (except for GET)

• $PVAR IMOD

Any request to issue these functions simply sets the return code to 0 and returns.

Also during TRACE functions, global variables are resolved but not set (notpermanently updated).


Chapter 5Defining System Configuration

This chapter covers BIM-FAQS/PCS configuration.

OverviewWhat Is Configuration?

BIM-FAQS/PCS configuration definitions control the operation of BIM-FAQS/PCS. In particular, the BIM-FAQS/PCS configuration contains user ID,global, and user class configuration settings for BIM-FAQS/PCS.

Configuration Member: JCLCONFG.CTL

The BIM-FAQS/PCS system is controlled by the configuration member. Thismember is created and maintained online (via any supported online interfaces).If the PDS accessed does not contain a configuration, then BIM-FAQS/PCS usesthe configuration for the MON PDS.

A default configuration member, cataloged as part of the installation library,demonstrates the basic parameter formats.

The configuration member, JCLCONFG.CTL, is not intended for manualmaintenance. You should use only the online system to access this member.Note that all enhanced BIM-FAQS/PCS features are located on the online system.

Configuration by User ID or System

BIM-FAQS/PCS configuration identifies configuration options as either private orsystem. You can set configuration values for your user ID using the privateoptions or set up global or class configuration options and defaults using thesystem options.

Users without authority to change system options will see only privateconfiguration options on the Configuration Options Menu Index.

This chapter explains the different private user ID and system options you candefine.

Defining BIM-FAQS/PCS Configuration

5–2 BIM-FAQS/PCS

Defining BIM-FAQS/PCS ConfigurationIntroduction

If you are an authorized user, you can update or display an existingconfiguration or create a new one. If you are not authorized, you can update ordisplay your private user ID options, but you can't change system options.

Accessing BIM-FAQS/PCS Configuration

To access BIM-FAQS/PCS configuration, select Configuration Options from theOnline Menu Index by entering O at the command line. The ConfigurationOptions Menu Index is displayed.

Configuration Options Menu Index

JOLOPT .O ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q013===>

** BIM-FAQS/PCS Configuration Options - Menu Index **

Private User ID Options System Options

V CMS Submit Defaults Q System CMS Submit Defaults E Panel Defaults R System Panel Defaults S CMS Server Defaults G Global Configuration Options U User Class Config. Options C User ID Classes I Library Defaults F Define Holidays and Cycles D CPUID Synonyms & Nodes N Dataset Exclusion T Dataset Logging J Partner Node Names

PF1=Help PF3=Return PF6=Update

Private Configuration Options

Private configuration options are used to set up defaults for the current user ID.The following table briefly describes each private user ID configuration option.

Option Function

CMS Submit Defaults Identifies where a job is to be routed

Panel Defaults Establishes defaults when events are created, defaults forthe event panel, and defaults for PDS browsing andupdating

Defining BIM-FAQS/PCS Configuration


System Configuration Options

System configuration defaults and options are used to maintain defaults orconfiguration options for any user ID, not just the current user ID. The followingtable briefly describes each system configuration option.

Option Function

User ID Classes Maintains user classes

System CMS SubmitDefaults

Identifies where a job is to be routed, for any user ID,when using BCIN CMS

System Panel Defaults Establishes defaults when events are created, defaultsfor the event panel, defaults for PDS browsing andupdating, defaults when events or PDS members aredeleted, and defaults for how log files are displayed--for any user ID

CMS Server Defaults Defines the CMS server machine options

Global ConfigurationOptions

Sets up the global configuration options

User Class Config.Options

Sets up user class configuration options

Library Defaults Sets up default library options for interfaces

Define Holidays andCycles

Defines event holidays, cycles, and user-definedcalendars

CPUID NODEIDSynonym Table

Defines CPU ID synonyms

Dataset Exclusion Specifies datasets to be monitored for exclusion

Dataset Logging Specifies dataset logging suppression

Partner Node Names Specifies which nodes in your network you wantBIM-FAQS/PCS to communicate with.

Defining Private User ID Options

5–4 BIM-FAQS/PCS


Defining CMS Submit Defaults

Introduction

The CMS Submit Defaults option enables you to determine where a job is to berouted for your user ID. By setting up default values, you identify which virtualmachine will receive jobs submitted from BIM-FAQS/PCS or the system editor.If you don't set default values, jobs submitted from CMS remain in the VM/CPPUNCH queue of the submitting user ID.

Accessing CMS Submit Defaults

To access CMS submit defaults for your user ID, select the CMS Submit Defaultsoption from the Configuration Options Menu Index by entering V at thecommand line. The Set Up CMS Defaults Screen is displayed.

Set Up CMS Defaults Screen

JOLOPT .V ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.PROFILE===> BIM-FAQS/PCS Set Up CMS Defaults

CMS Options for User ===> PROFILE

Class ===> A Enter class of target machine reader. User ===> VSE Enter target machine user ID. Node ===> Enter node name of target remote system. RSCS ===> Enter name of your RSCS on this VM system.




Procedure

To define CMS submit defaults for your user ID, follow these steps:

1. From the Configuration Options Menu Index, select the CMS SubmitDefaults option by entering V at the command line. You will see the Set UpCMS Defaults Screen.

2. Specify user defaults in any of the following fields:

CLASS the specified VM/CP reader class of the receiving machine

USER the VM user ID of the receiving virtual machine

NODE the network node where the machine is located

RSCS the name of the local RSCS virtual machine

3. To update the values on disk, press PF4 (Update).


5–6 BIM-FAQS/PCS

Defining Panel Defaults

Introduction

The Panel Defaults option enables you to establish for your user ID onlinedefaults for creating events, the event definition panels, PDS browse and updatefunctions, confirmation of delete functions, and how log files are displayed.These defaults are overridden with the values specified on one of the EventMaintenance Screens. The following table shows the various defaults you can setusing the Panel Defaults option:

Option Explanation

Event Default Values You can define the following event defaults:

• Early time

• Late time

• Abort time

• CPU ID

Event Panel DisplayOptions

You can set the following panel display options:

• Whether the event will be refreshed upon exitingthe panel

• Whether group information or time information isdisplayed

• Whether the events will be sorted by time ratherthan name

• Whether the events can be transferred to themaster file

PDS Update andBrowse Defaults

You can define the following PDS defaults:

• PDS ID

• Data type

MiscellaneousDefaults

You can set the following panel defaults:

• Whether the user is prompted with a confirmationmessage when deleting an event or PDS member.

• Whether the log files are displayed LIFO or FIFO.



Accessing Panel Defaults

To access BIM-FAQS/PCS online panel defaults for your user ID, select the PanelDefaults option from the Configuration Options Menu Index by entering E at thecommand line. The Set up Event and PCS Browse and Update Defaults Screen isdisplayed.

Set Up Event and PDS Update and Browse Defaults Screen

The following screen shows an example of the Set Up Event and PDS Update andBrowse Defaults Screen:

JOLOPT .E ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.PROFILE===>

**BIM-FAQS/PCS Set Up Event and PCS Update and Browse Defaults**

User ===> PROFILE

Event Default Values Event Panel Display Options Early Time ===> Event Refresh ===> Late Time ===> Display Group ===> Abort Time ===> Sort Time ===> Event Cpu ID ===> Tran to Mast ===>

PDS Update and Browse Defaults Miscellaneous Defaults PDS Id ===> Confirm Deletes ===> Data Type ===> Log direction ===>

PF1=Help PF3=Return PF4=Update PF12=Exit


5–8 BIM-FAQS/PCS

Procedure

To define event, panel, and PDS defaults for your user ID, follow these steps:

1. From the Configuration Options Menu Index, select the Panel Defaultsoption by entering E at the command line. You will see the Online Set upEvent and PDS Browse and Update Defaults Screen.

2. Specify user event defaults in any of the following fields:

Early Time the earliest desired time for the event to execute

Late Time the time after which the event is marked late

Abort Time the time when the event can no longer be executed

Event CPU ID the CPU ID of the machine where the event is to bescheduled

3. Specify user panel defaults in any of the following fields:

Event Refresh whether the event directory will be refreshed uponexiting the current Event Maintenance Edit Screen

Display Group whether group information or late and abort timeinformation is displayed

Sort Time whether the events will be sorted by time rather thanname

Tran to Mast not valid for user ID configuration

4. Specify user PDS defaults in any of the following fields:

PDS ID the PDS ID to browse or update

Data type the data type to browse or update

5. Specify miscellaneous panel defaults in the following fields:

Confirm Deletes whether the user is prompted with a confirmationmessage when deleting events or PDS members.Specify Y or N.

Log direction whether log files are displayed LIFO or FIFO.Specify L or F.


Defining System Options



Defining User ID Classes

Introduction

The User ID Classes option enables you to put user IDs with similarcharacteristics into classes. These are the classes used to define configurationoptions by class.

You may establish user classes for security or configuration purposes. Each userclass is presented in alphanumeric order, with the first ten user IDs of each classdisplayed on the screen. A user class contains one or more user IDs.

If you specify the same user ID more than once in a class, the system will use thelast occurrence.

JCLCONFG.CTL Member

All changes made to the global configuration, user class configuration, or securityoptions are saved to the JCLCONFG.CTL member in the MON PDS.

Accessing User ID Classes

To access user ID classes, select the User ID Classes option from theConfiguration Options Menu Index by entering C at the command line. The UserID Classes Screen is displayed.


5–10 BIM-FAQS/PCS

User ID Classes Screen

JOLUCL .C ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q013===>

** BIM-FAQS/PCS User ID Classes **

CLASS USER IDs

_ A ADMN PCSMAINT

_ B ROBERT

_ Z U17 U18 U19 U20 U21 U23 U24 U25 U26 U27

L=Delete O=Options S=Security U=Update PF1=Help PF3=Return PF4=Add PF6=Update PF7=Bwd PF8=Fwd

Procedure

To define user ID classes, follow these steps:

1. From the Configuration Options Menu Index, select the User ID Classesoption by entering C at the command line. You will see the User ID ClassesScreen.

2. To add a new class of user IDs, press PF4 (Add). Enter the new user ID classand the user IDs that belong in that class.

3. To maintain a user ID class, use one of the maintenance options. See thetable below for a description of these options.

4. To save updates to user classes, press PF6 (Update).

Maintenance Options

The following table describes the maintenance options you can enter in thecommand input field to the left of defined classes:

Option Function

L Deletes a user class

O Displays configuration options associated with a user class

S Displays security options associated with a user class

U Displays all user IDs within a user class, enabling you to maintainthe class



Defining System CMS Submit Defaults

Introduction

The System CMS Submit Defaults option enables you to determine where a job isto be routed for any user ID. By setting up default values, you identify whichvirtual machine will receive jobs submitted from BIM-FAQS/PCS or the systemeditor. If you don't set default values, jobs submitted from CMS remain in theVM/CP PUNCH queue of the submitting user ID.

Accessing System CMS Submit Defaults

To access CMS submit defaults for the system, select the System CMS SubmitDefaults option from the Configuration Options Menu Index by entering Q at thecommand line. The Set Up CMS Defaults Screen is displayed.

Set Up CMS Defaults Screen

JOLOPT .Q ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q013===> BIM-FAQS/PCS Set Up CMS Defaults

CMS Options for User ===> $DEFAULT

Class ===> Enter class of target machine reader. User ===> Enter target machine user ID. Node ===> Enter node name of target remote system. RSCS ===> Enter name of your RSCS on this VM system.



5–12 BIM-FAQS/PCS

Procedure

To define system CMS submit defaults, follow these steps:

1. From the Configuration Options Menu Index, select the System CMS SubmitDefaults option by entering Q at the command line. You will see the Set UpCMS Defaults Screen.

2. To change the system options for a user ID, enter the user ID in the CMSoptions for User ===> field

3. Specify user defaults in any of the following fields:

Class the specified VM/CP reader class of the receiving machine

User the VM user ID of the receiving virtual machine

Node the network node where the machine is located

RSCS the name of the local RSCS virtual machine


$DEFAULT User ID

The $DEFAULT user ID contains the default options for users who do not havetheir own options specified.



Defining System Panel Defaults

Introduction

The System Panel Defaults option enables you to establish online system defaultsfor creating events, the event definition panels, PDS browse and updatefunctions, confirmation of delete functions, and how log files are displayed. Notethat values specified on one of the Event Maintenance screens override thedefaults defined on the Online Set Up System Event and PDS Browse andUpdate Defaults Screen. The following table shows the various defaults you canset using the Panel Defaults option:

Option Explanation

Event DefaultValues

You can define the following event defaults:

• Early time

• Late time

• Abort time

• CPU ID

Event PanelDisplayOptions

You can set the following panel display options:

• Whether the event will be refreshed upon exiting the panel

• Whether group information or time information isdisplayed

• Whether the events will be sorted by time rather thanname

• Whether the events can be transferred to the master file

PDS Updateand BrowseDefaults

You can define the following PDS defaults:

• PDS ID

• Data type

MiscellaneousDefaults

You can set the following panel defaults:

• Whether the user is prompted with a confirmationmessage when deleting an event or PDS member.

• Whether the log files are displayed LIFO or FIFO.


5–14 BIM-FAQS/PCS

Accessing System Panel Defaults

To access online panel defaults for the system, select the System Panel Defaultsoption from the Configuration Options Menu Index by entering R at thecommand line. The Set Up System Event and PDS Browse and Update DefaultsScreen is displayed.

Set Up System Event and PDS Update and Browse Defaults Screen

JOLOPT .R ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q013===>

**BIM-FAQS/PCS Set Up Event and PCS Update and Browse Defaults**

User ===> $DEFAULT

Event Default Values Event Panel Display Options Early Time ===> 0800 Event Refresh ===> Late Time ===> 2400 Display Group ===> Abort Time ===> 3000 Sort Time ===> Event Cpu ID ===> VSE Tran to Mast ===> N

PDS Update and Browse Defaults Miscellaneous Defaults PDS Id ===> MON Confirm Deletes ===> Y Data Type ===> JCL Log direction ===> L

PF1=Help PF3=Return PF4=Update PF12=Exit

Procedure

To define system event defaults, follow these steps:

1. From the Configuration Options Menu Index, select the System PanelDefaults option by entering R at the command line. You will see the OnlineSet Up Event and PDS Browse and Update Defaults Screen.

2. To change the system options for a user ID, enter the user ID in the(User ===> field).

3. Specify user event defaults in any of the following fields:

Early Time the earliest desired time for the event to execute

Late Time the time after which the event is marked late

Abort Time the time when the event can no longer be executed

Event CPU ID the CPU ID of the machine where the event is to bescheduled

4. Specify user panel defaults in any of the following fields:

Event Refresh whether the event directory will be refreshed upon exitingthe current Event Maintenance Edit Screen



Display Group whether group information or late and abort timeinformation is displayed

Sort Time whether the events will be sorted by time rather thanname

Tran to Mast whether the current events can be transferred to theMaster Event File

5. Specify user PDS defaults in any of the following fields:

PDS ID the PDS ID to browse or update

Data type the data type to browse or update

6. Specify miscellaneous panel defaults in the following fields:

Confirm Deletes whether the user is prompted with a confirmationmessage when deleting events or PDS members. SpecifyY or N.

Log direction whether log files are displayed LIFO or FIFO. Specify Lor F.


$DEFAULT User ID

The $DEFAULT user ID contains the default options for users who do not havetheir own options specified.


5–16 BIM-FAQS/PCS

Defining CMS Server Defaults

Introduction

If you'll be submitting your JCL from CMS, you should define CMS serverdefaults. By defining these defaults, you won't have to move your JCL fromwhere it currently resides. The CMS Server Defaults option enables you to definethe CMS server machine options. More specifically, you can tell BIM-FAQS/PCSwhich spool class to spool the JCL to for each VSE guest. A single CMS servercan submit to a maximum of 30 machines.

PCSSERV is the default CMS server machine ID, and A is the default spool classfor each VSE machine.

Accessing CMS Server Defaults

To access CMS server defaults, select CMS Server Defaults from theConfiguration Options Menu Index by entering S at the command line. The CMSServer Defaults Screen is displayed.

CMS Server Defaults Screen

JOLSERV .S ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q013===> BIM-FAQS/PCS CMS Server ID Defaults

Server VM Machine ID ===> PCSSERV VSE Machine ID Spool Class VSE Machine ID Spool Class VSE A ________ _ VSE14 A ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _ ________ _




Procedure

To define CMS server defaults, follow these steps:

1. From the Configuration Options Menu Index, select CMS Server Defaults byentering S at the command line. You will see the CMS Server DefaultsScreen.

2. Enter the server machine ID in the CMS (Server Machine ID ===> field).

3. Enter the values of the target VSE guest machine you're sending jobs to andthe spool class.

4. To save the updates, press PF4 (Update).

5. Restart JCLSCHED to implement CMS server defaults.

Defining Global Configuration Options

Introduction

The Global Configuration Options option enables you to set up the systemconfiguration options globally. The options set up here pertain to all users thatdo not have user class-specific options set up. If a user ID is part of a class, andthat class has default configuration values established, the global values areoverridden.

JCLCONFG.CTL Member

All changes made to the user classes and user options are written to theJCLCONFG.CTL member in the MON PDS.

Accessing Global Configuration

To access global configuration options, select Global Configuration Options fromthe Configuration Options Menu Index by entering G at the command line. Thefirst Global Configuration Options Screen is displayed.


5–18 BIM-FAQS/PCS

Global Configuration Options Screen (First)

JOLOPT .G ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q013===>

** BIM-FAQS/PCS Global Configuration Options **

Current User Classes: Z

Y AUDIT Trail enabled N CA-DRIVER local variable support Y POWER SLI catalog support N CA-FLEE GSERV shifting Y Log messages to console Y Retain POWER JOB statements upon RESTART Y Retain POWER LST statements upon RESTART Y Retain POWER PUN statements upon RESTART N Retain POWER RDR and SLI statements upon RESTART N Scan columns 1-80 for variables (default 1-71) Y Preserve columns 72-80 from variable substitution Y Convert PCL operator replies to uppercase

PF1=Help PF3=Return PF6=Update PF8=Fwd

Procedure

To define global configuration options, follow these steps:

1. From the Configuration Options Menu Index, select Global ConfigurationOptions by entering G at the command line. The first Global ConfigurationOptions Screen is displayed.

2. Select the options you want to enable (Y) globally. See information for theseoptions in the following table.




Current User Classes Field

The Current User Classes field at the top of the first Global ConfigurationOptions Screen indicates all current user classes. If classes are defined, theoptions defined on this screen do not affect the users in those classes.

Option Function

AUDIT Trail enabled Logs access to BIM-FAQS/PCS events andmembers.

CA-DRIVER localvariable support

Allows all user variables to be local to eachmember and not available to other memberswithin the same jobstream.

POWER SLI catalogsupport

Supports POWER SLI catalog.

CA-FLEE GSERV shifting Shifts JCL or JECL found with "==" two positionsto the left.

Log messages to console Logs BIM-FAQS/PCS messages to console.

Retain POWER JOBstatements uponRESTART

Saves POWER JOB statements up to the restartstep, when a restarted job was submitted with theS= parameter.

Retain POWER LSTstatements uponRESTART

Saves POWER LST statements up to the restartstep, when a restarted job was submitted with theS= parameter.

Retain POWER PUNstatements uponRESTART

Saves POWER PUN statements up to the restartstep, when a restarted job was submitted with theS= parameter.

Retain POWER RDR andSLI statements uponRESTART

Saves POWER RDR and SLI statements up to therestart step, when a restarted job was submittedwith the S= parameter.

Scan columns 1-80 forvariables (default 1-71)

Looks at variable names in all 80 columns whenusing variable substitution. The default scanscolumns 1-71 only.

Preserve columns 72-80from variable substitution

Prevents columns 72-80 from being overlaid withdata if the data replacement exceeds column 71.This can occur when data is substituted for avariable.

Convert PCL operatorreplies to uppercase

Converts data to uppercase when input is read inresponse to a PCL |REPLY command. If no (N) isselected, replies entered in lowercase may beunrecognized.


5–20 BIM-FAQS/PCS

Defining Batch Defaults for Global Configuration

Introduction

You can define configuration options online to be used when submitting jobsfrom batch. You can set up default values for various batch-related options thatoccur in a batch jobstream.

Accessing Batch Defaults for Global Configuration

To access batch defaults for the global configuration, follow these steps:

1. From the Configurations Options Menu Index, select Global ConfigurationsOptions by entering G at the command line. The first Global ConfigurationOptions Screen is displayed.

2. Press PF8 (Fwd). The second Global Configuration Options Screen isdisplayed.

Global Configuration Options Screen (Second)

JOLOPT .8 ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q013===>

** BIM-FAQS/PCS Global Configuration Options **

Default batch userid ===> ADMN Scheduler Partition ===> Z3 Default POWER JOB class for scheduler submitted jobs ===> X Default POWER JOB class for non-scheduled jobs ===> A Default POWER JOB DISP= parameter ===> D Default POWER JOB priority ===> 4 Default POWER JOB SYSID= parameter ===> Default PDS member datatype ===> MON JCL restart card retention ===> STEP Restart comment format ===> STEP * Additional PCL prefix ===> ./ && GOTO limit counter ===> 12000

PF1=Help PF7=Bwd



Procedure

To define defaults for global configuration options, follow these steps:

1. To define a default, enter a value next to the option. To change a default,overtype the existing value with the new value. See the table after this onefor a description of the different batch defaults you can define.

2. To update the values on disk, return to the first Global ConfigurationOptions Screen and press PF6 (Update).

Global Configuration Options for Batch

Option Description

Default batch userid User ID for batch runs. Specify a value 4-to-8-alphanumeric characters long. The system uses thisvalue where no ID statement is supplied. JCLSCHEDand other batch utilities use this user ID. This option isoften referred to as BATUSER.

Scheduler Partition The partition containing the permanent scheduler. IfJCLMAN or JCLSCHED is running in this partition, theSCLASS parameter is applied. If JCLMAN is running inany other partition, the BCLASS parameter is applied.This option is often referred to as SPAR.

Default POWER JOBclass for schedulersubmitted jobs

Default class for jobs created by the scheduler or fromwithin the scheduler partition. This value is used togenerate the POWER JOB card when a generatedrunstream is passed to POWER. Any user-suppliedvalue overrides this default. This option is often referredto as SCLASS.

Default POWER JOBclass for non-scheduledjobs

Default class for jobs created by batch execution ofJCLMAN. If you specify *, the default is the ID of thecurrent partition. If you specify @, the default is thePOWER class in which JCLMAN was executed. Thisoption is often referred to as BCLASS.

Default POWER JOBDISP= parameter

Default disposition for JECL JOB. If the user-suppliedjob contains a DISP value, that value is used instead ofthis parameter. This option is often referred to as DISP.

Continued


5–22 BIM-FAQS/PCS

Continued

Option Description

Default POWER JOBpriority

This is the POWER JOB priority assigned to jobssubmitted when the priority is not supplied oroverridden by the job submittor. This option is oftenreferred to as PRI.

Default POWER JOBSYSID= parameter

Default SYSID value for POWER JOB cards. This value isused to generate the POWER JOB card and is overriddenby any user-supplied value. This option is often referredto as SYSID.

Default PDS memberdatatype

Default member name suffix for PDS members. Thedefault value is MON. Note that this suffix is not relatedto the name of the currently selected PCS library (PDS).This option is often referred to as DATATYP.

JCL restart cardretention

This option controls which non-POWER cards areretained when a job is restarted. Valid values are

STEP - Keep all cards prior to the first step card(i.e., /., |STEP, |LABEL) or EXEC statement.

NONE - Discard all cards prior to the step beingrestarted.

ALL - Keep all cards prior to the first step card. Thisincludes all EXEC statements prior to the first step card.

PROC - Keep cards including EXEC PROC= statementsprior to the first step card or EXEC program card.

PROG - Keep cards including EXEC program cards priorto the first step card or EXEC PROC= statement.

Restart commentformat

Defines the format of a comment card to be used as avalid restart label for the S= parameter. The operandmay be up to eight characters in the same format as amasked member name, except the first asterisk (genericmask code) will be interpreted as a request to match thespecific restart point.

Note that restart comment cards do not define a memberboundary, only a valid restart point. This means thatthere is no restriction on how many may be present in asingle member. This option is often referred to asPROCMNT.

Continued



Continued

Option Description

Additional PCL prefix A character string to identify PCL control statements inaddition to the system-defined character of "|". Thisoption is often referred to as PCLALT.

GOTO limit counter Default is no checking. If specified, a runstream may notperform more GOTOs than the limit specified. Thisoption is often referred to as GOTOLIM. This preventsendless looping of GOTO's.


5–24 BIM-FAQS/PCS

Defining User Class Configuration Options

Introduction

With the Class Configuration Options Screen you can set up user class batchoptions. These options pertain only to users assigned to defined classes. Acommon use of this configuration function is to set up into user classes users thatwill share configuration options. For example, you can group securityadministrators or systems programmers, who may require different options thanthe general user, into their own classes.

JCLCONFG.CTL Member

All changes made to the user classes and global options are written to theJCLCONFG.CTL member in the MON PDS.

Accessing User Class Configuration Options

To access user class configuration options, select User Class Config. Options fromthe Configuration Options Menu Index by entering U at the command line. TheUser Class Configuration Options Screen is displayed.

User Class Configuration Options Screen

JOLOPT .U ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q013===>

** BIM-FAQS/PCS Class Configuration Options **

Current User Classes: Z Option Class ===> Z

N CA-FLEE GSERV shifting Y Log messages to console Y Retain POWER JOB statements upon RESTART Y Retain POWER LST statements upon RESTART Y Retain POWER PUN statements upon RESTART N Retain POWER RDR and SLI statements upon RESTART N Scan columns 1-80 for variables (default 1-71) Y Preserve columns 72-80 from variable substitution Y Convert PCL operator replies to uppercase

PF1=Help PF3=Return PF4=Add PF6=Update PF7=Bwd PF8=Fwd PF9=Del

Scrolling Through Classes

The PF8 (Fwd) key moves alphabetically through all of the classes that havebatch options defined.



Procedure

To define user class configuration options, follow these steps:

1. From the Configuration Options Menu Index, select User Class Config.Options by entering U at the command line. You will see the ClassConfiguration Options Screen.

2. To add a new user class, press PF4 (Add). Enter the new class in the Option(Class ===> field).

3. Select the batch options you want to enable (Y) globally. See information forthese options in the table on the next page.


User Class Configuration Options

Option Function

CA-FLEE GSERVshifting

Shifts JCL or JECL found with "==" two positions tothe left.

Log messages toconsole

Logs BIM-FAQS/PCS messages to console.

Retain POWER JOBstatements uponRESTART

Saves POWER JOB statements up to the restart step,when a restarted JOB was submitted with the S=parameter.

Retain POWER LSTstatements uponRESTART

Saves POWER LST statements up to the restart step,when a restarted JOB was submitted with the S=parameter.

Retain POWER PUNstatements uponRESTART

Saves POWER PUN statements up to the restart step,when a restarted JOB was submitted with the S=parameter.

Retain POWER RDRand SLI statementsupon RESTART

Saves POWER RDR and SLI statements up to therestart step, when a restarted JOB was submitted withthe S= parameter.

Scan columns 1-80 forvariables (default 1-71)

Looks at variable names in all 80 columns when usingvariable substitution. The default scans columns 1-71only.

Continued


5–26 BIM-FAQS/PCS

Continued

Option Function

Preserve columns 72-80from variablesubstitution

Prevents columns 72-80 from being overlaid with data ifthe data replacement exceeds column 71. This occurswhen data is substituted for a variable.

Convert PCL operatorreplies to uppercase

Converts data to uppercase when input is read inresponse to a PCL |REPLY command. If no (N) isselected, replies entered in lowercase may beunrecognized.



Defining Library Defaults

Introduction

If you'll be submitting your JCL from a library, you should define librarydefaults. The Library Defaults configuration option enables you to set up defaultlibrary names. The names that you define are shorter and are often easier toremember.

Why Set Up Library Defaults?

Default library names enable you to enter shorter commands to access librarymembers. For example, if you need to access a member in a ICCF library, youenter D=libname M=membname. If you have set up a default library name forthe ICCF library, all you need to enter is D:membname.

Accessing Library Defaults

To access default library names, select the Library Defaults option from theConfiguration Menu Index by entering I at the command line. The LibraryDefaults Screen is displayed.

Library Defaults Screen

JOLLIB .I ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.PCSMAINT===>

** Library Defaults **

BIM-EDIT Library Name ===> __________________ BIM-EDIT Logon Parameter ===> _________________ BIM-EDIT System Name ===> ________

CA-LIBRARIAN Library Name ===> ________

CA-VOLLIE Library Name ===> ________

CONDOR Library Name ===> ________

CA-PANVALET Library Name ===> ________

ICCF Primary Library ===> 0008 ICCF Connected Library ===> 0010 ICCF Common Library ===> 0036

PDS Search String ===> PRD MON VIO EVT

PF1=Help PF3=Return PF4=Update PF9=Delete


5–28 BIM-FAQS/PCS

Procedure

To define default library names, follow these steps:

1. From the System Configuration Menu Index, select the Libraries Defaultsoption by entering I at the command line. You will see the Library SupportDefaults Screen.

2. To add a default, tab to the library you want to set the default name for andenter a valid library name. This will be the library name accessed by theshorter access command.

3. Press PF4 (Update) to update the library name default. To maintain adefault, press either PF4 (Update) or PF9 (Delete).

Defining the ICCF Defaults

For ICCF you can define a primary library, a connected library, and a commonlibrary. Members in these libraries are searched sequentially.

Defining the PDS Search String

The system default for a PDS is MON. To define a string to use to search for PDSmembers, enter the PDS names in the order in which they should be searched.When a PDS access command is issued, the system looks in the first PDSspecified in the string, and if the member is not there, it searches the second, thenthe third, and so on.

This search string is used for JCL scheduling purposes only.



Specifying Holiday and Cycle Definitions

Introduction

The Define Holidays and Cycles option enables you to define holidays andworkdays, and cycles. These definitions can be used with event definitions.

Accessing the Holiday and Cycle Definition Entry Panel

To access the Holiday and Cycle Definition Entry Panel, select Define Holidaysand Cycles from the Configuration Options Menu Index by entering F at thecommand line. The Holiday and Cycle Definition Entry Panel is displayed.

Holiday and Cycle Definition Entry Panel

JOLCAL .F ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q013===>

**BIM-FAQS/PCS Online - Holiday and Cycle definition entry panel**

Selection Panel for maintaining and displaying Holiday and Cycle definitions. Also, if any user defined calendars have been set up, a user may display and edit them. Enter A B C D E or F for the appropriate selection.

A Holiday Definition List by IDs B Holiday Id 000 Display and Edit C Cycle Definition List by IDs D Cycle Id 000 Display and Edit E Display and Edit any Existing User Defined Calendar F Exception Date Definition List by IDs

PF1=Help PF3=Return

Holiday and Cycle Options

Option Function

Holiday Definition List by IDs Displays holiday definitions by IDs

Holiday ID 000 Display and Edit Allows editing of holiday definitions

Cycle Definition List by IDs Displays cycle definitions by Ids

Cycle ID 000 Display and Edit Allows editing of cycle definitions

Display and Edit Existing UserDefined Calendar

Displays user-defined calendars

Exception Date Definition List byIDs

Displays exception date definitions by IDs


5–30 BIM-FAQS/PCS

Listing Holiday Definitions by IDs

Introduction

The Holiday Definition List by IDs option enables you to view a list of all holidaydefinitions in numeric order by ID.

The List of Holiday Definitions by ID Screen displays the ID numbers,descriptions, and update information about all holiday definitions.

List of Holiday Definitions by ID Screen

JOLCAL .3 ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q013===> List of Holiday definitions by Id ID Description Update Timestamp _ 000 Default Holidays 01/23/98 10.50. _ 240 Special holidays 10/21/97 06.34.

Actions: L=Delete X=Edit PF1=Help PF2=Refresh PF3=Return PF4=Add

Using the List of Holiday Definitions by ID Screen

1. From the Holiday and Cycle Definition Entry Panel, select the HolidayDefinition List by IDs option by entering A at the command line. The List ofHoliday Definitions by ID Screen is displayed.

2. To delete an ID, enter L in the input field next to the ID.

3. To edit an ID, enter X in the input field next to the ID. The Holiday IDEditing Screen is displayed.

4. To add an ID, press PF4 (Add). The Holiday ID Editing Screen is displayed.

5. To refresh the screen, press PF2 (Refresh).



Editing a Holiday ID

Introduction

The Holiday ID Editing Screen enables you to edit holidays and workdays for aspecific holiday ID.

Holiday ID Editing Screen

JOLCAL .g ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q013===>

Holiday Id ===> 240 Desc ===> Special holidays

97/09/01 ________ ________ ________ **/12/26 ________ ________ ________ 97/11/27 ________ ________ ________ **/01/01 ________ ________ ________ 97/11/28 ________ ________ ________ **/12/25 ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________

MTWTFSS Enter Holidays in YY/MM/DD Format XXXXX__ <=== Workdays Place X beneath valid workdays

PF1=Help PF3=Return PF4=Write to Disk

Procedure

To edit an ID, change workdays, and edit holiday ID descriptions, follow thesesteps:

1. To edit an ID, enter X in the input field next to the ID. To add an ID, pressPF4 (Add). The Holiday ID Editing Screen is displayed.

2. To edit a specific ID, enter new holidays in yy/mm/dd format on blank lines,or type over existing holidays. You can substitute ** for yy, mm, or dd toglobally match on any year, month, or day. Holidays are any of the defineddates.

3. To change workdays, enter X beneath valid workdays.

4. To edit the holiday ID description, enter new information in the (Desc ===>)field.

5. To save changes, press PF4 (Write to Disk).


5–32 BIM-FAQS/PCS

Defining a Holiday ID

Introduction

The Holiday ID 000 Display and Edit option allows you to establish defaultholidays and workdays.

On the Holiday Definitions Screen, you can specify a holiday ID and descriptionto create multiple holiday IDs with different holiday definitions.

Holiday Definitions Screen

JOLCAL .B ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q013===>

Holiday Id ===> 000 Desc ===> Default Holidays

**/12/25 ________ ________ ________ 98/09/07 ________ ________ ________ **/01/01 ________ ________ ________ 98/11/27 ________ ________ ________ **/07/06 ________ ________ ________ 98/11/26 ________ ________ ________ 98/05/25 ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________



Default Holiday

The holiday ID 000 is the default ID. You can access the default holiday screenand enter a new holiday ID number to create a new holiday ID.



Procedure

In order to use any keyword associated with holidays and workdays in an event,you must define default holidays and workdays.

To define a new holiday ID, follow these steps:

1. From the Holiday and Cycle Definition Entry Panel, select the Holiday ID000 Display and Edit option by entering B at the command line. The HolidayDefinitions Screen is displayed.

2. In the (Holiday Id ===> field), enter a 3-digit identification number rangingfrom 000-255.

3. In the Desc ===> field, enter a description of up to 20 characters.

4. Define a maximum of 64 holidays. A holiday must be defined in yy/mm/ddformat. You can substitute ** for yy, mm, or dd to globally match on any year,month, or day. Holidays are any of the defined dates.

5. Define workdays by entering X beneath valid workdays. Workdays are daysthat do not fall on a holiday.

6. To save the changes, press PF4 (Write to Disk). IDs are displayed on the Listof Holiday Definitions by ID Screen.


5–34 BIM-FAQS/PCS

Updating a Cycle ID

Introduction

The Cycle Definition List by IDs option allows you to view a list of all cycledefinitions in numeric order by ID.

The List of Cycle Definitions by ID Screen displays the ID numbers, descriptions,and update information about all cycle definitions.

List of Cycle Definitions by ID Screen

JOLCAL .C ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===> List of Cycle definitions by Id ID Description Update Timestamp _ 000 Default cycle table 10/14/97 14.57. _ 014 Quarterly cycle 01/20/98 08.42.


Procedure

To update a cycle ID, follow these steps:

1. From the Holiday and Cycle Definition Screen, select the Cycle DefinitionList by IDs option by entering C at the command line. The List of CycleDefinitions by ID Screen is displayed.

2. To delete an ID, enter L in the input field next to the ID.

3. To edit an ID, enter X in the input field next to the ID. The Cycle ID EditingScreen is displayed.

4. To add an ID, press PF4 (Add). The Cycle ID Editing Screen is displayed.

5. To refresh the screen, press PF2 (Refresh).



Editing a Cycle ID

Introduction

The Cycle ID Editing Screen enables you to edit a specific ID and edit the cycle IDdescription.

Cycle ID Editing Screen

JOLCYC .j ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

Cycle Id ===> 000 Desc ===> Default cycle table Date range for cycle period Date range for cycle period

(01) **/10/01 <===> **/11/02 (16) ________ <===> ________ (02) **/11/03 <===> **/12/05 (17) ________ <===> ________ (03) **/12/06 <===> **/12/31 (18) ________ <===> ________ (04) **/01/01 <===> **/02/01 (19) ________ <===> ________ (05) **/02/02 <===> **/03/01 (20) ________ <===> ________ (06) **/03/02 <===> **/04/01 (21) ________ <===> ________ (07) **/04/02 <===> **/05/02 (22) ________ <===> ________ (08) **/05/03 <===> **/06/05 (23) ________ <===> ________ (09) **/06/06 <===> **/07/03 (24) ________ <===> ________ (10) **/07/04 <===> **/08/04 (25) ________ <===> ________ (11) **/08/05 <===> **/09/01 (26) ________ <===> ________ (12) **/09/02 <===> **/09/30 (27) ________ <===> ________ (13) ________ <===> ________ (28) ________ <===> ________ (14) ________ <===> ________ (29) ________ <===> ________ (15) ________ <===> ________ (30) ________ <===> ________


Procedure

To edit a specific cycle ID and edit the cycle ID description, follow these steps:

1. To edit an ID, enter X in the input field next to the ID. To add an ID, pressPF4 (Add). The Cycle ID Editing Screen is displayed.

2. To edit a specific ID, enter the date range for cycle period in yy/mm/dd formaton blank lines, or type over existing dates.

3. You can substitute ** for yy to match all years. The date range is a set ofspecific start and end dates for a cycle. The start date of a date range doesnot have to be the next sequential date following the end date of the previousdate range. You can use cycles to implement quarters, trimesters, or otherschedules.

4. To edit the cycle ID description, enter new information in the (Desc ===>field).

5. To save changes, press PF4 (Write to Disk).


5–36 BIM-FAQS/PCS

Defining a Cycle

Introduction

The Cycle ID 000 Display and Edit option allows you to establish default cycles.

On the Cycle Definitions Screen, you can specify a cycle ID and description tocreate multiple cycle IDs with different cycle definitions.

Cycle Definitions Screen

JOLCYC .D ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

Cycle Id ===> 000 Desc ===> Default cycle table Date range for cycle period Date range for cycle period

(01) **/10/01 <===> **/11/02 (16) ________ <===> ________ (02) **/11/03 <===> **/12/05 (17) ________ <===> ________ (03) **/12/06 <===> **/12/31 (18) ________ <===> ________ (04) **/01/01 <===> **/02/01 (19) ________ <===> ________ (05) **/02/02 <===> **/03/01 (20) ________ <===> ________ (06) **/03/02 <===> **/04/01 (21) ________ <===> ________ (07) **/04/02 <===> **/05/02 (22) ________ <===> ________ (08) **/05/03 <===> **/06/05 (23) ________ <===> ________ (09) **/06/06 <===> **/07/03 (24) ________ <===> ________ (10) **/07/04 <===> **/08/04 (25) ________ <===> ________ (11) **/08/05 <===> **/09/01 (26) ________ <===> ________ (12) **/09/02 <===> **/09/30 (27) ________ <===> ________ (13) ________ <===> ________ (28) ________ <===> ________ (14) ________ <===> ________ (29) ________ <===> ________ (15) ________ <===> ________ (30) ________ <===> ________


Default Cycle

The cycle ID 000 is the default ID. You can access the default holiday screen andenter a new holiday ID number to create a new holiday ID.



Procedure

In order to use any keyword associated with cycles in an event, you must definedefault cycles.

To define a new cycle ID, follow these steps:

1. From the Holiday and Cycle Definition Entry Panel, select the Cycle ID 000Display and Edit option by entering D at the command line. You will see theCycle Definitions Screen.

2. In the (Cycle Id ===> field), enter a 3-digit ID ranging from 000-255.

3. In the (Desc ===> field), enter a description of up to 20 characters.

4. Define up to 30 cycles. Cycle dates must be defined in yy/mm/dd format.Enter the date range for each cycle in the numbered blank spaces. The daterange is a set of specific start and end dates for a cycle. The start date of adate range does not have to be the next sequential date following the enddate of the previous date range. You can use cycles to implement quarters,trimesters, or other schedules.

5. To save the changes, press PF4 (Write to Disk). IDs are displayed on theCycle Definition List by IDs Screen.


5–38 BIM-FAQS/PCS

Updating a User Calendar

Introduction

The Display and Edit Any Existing User Defined Calendar option enables you toview an alphanumeric list of all user-defined calendars. The List of UserCalendars by Name Screen displays the user calendar names and updateinformation about all user-defined calendars.

List of User Calendars by Name Screen

JOLCAL .E ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===> List of User Calendars by name User Calendar Update Timestamp _ RJD1 10/21/97 06.26.


Procedure

To update a user calendar, follow these steps:

1. From the Holiday and Cycle Definition Screen, select the Display and EditAny Existing User Defined Calendar option by entering E at the commandline. The List of User Calendars by Name Screen is displayed.

2. To delete a user calendar, enter L in the input field next to the user name.

3. To view a user calendar, enter X in the input field next to the user name. Youwill see the specific file displayed with all the comments and dates enteredinto that user calendar.

4. To define a user calendar, press PF4 (Add). The Create a New Calendar IDDefinition Screen is displayed. For more information about defining a usercalendar, see the BIM-FAQS/PCS Operations Guide.

5. To exit the file, press PF3 (Return).



Listing an Exception Date ID

Introduction

Use exception date lists to handle exceptional scheduling conditions. In a list youcan either specify dates you do or don't want the event to run.

The Exception Date Definition List by IDs option enables you to view a list of allexception date definitions in numeric order by ID. The screen displays the IDnumbers, descriptions, and update information about all exception definitions.

List of Exception Date Definitions by ID Screen

JOLCAL .F ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===> List of Exception Date definitions by Id ID Description Update Timestamp _ 226 Test XDATE dates 10/14/97 15.12.


Using the List of Exception Date Definitions by ID Screen

To Do This

Delete an exception ID Enter L in the input field next to the ID.

Edit an exception ID Enter X in the input field next to the ID. TheException Date Maintenance panel is displayed.

Add an exception ID Press PF4 (Add). The Exception Date Maintenancepanel is displayed.

Refresh the panel Press PF2 (Refresh).


5–40 BIM-FAQS/PCS

Defining an Exception ID

Introduction

Use the Exception Date Maintenance Screen to include or exclude dates for aspecific exception ID. On this screen, you can define schedule exceptions that areabsolute; that is, BIM-FAQS/PCS looks at these definitions before any otherscheduling parameters such as event day, easy day, cycle, and holiday.

Use the exception date overrides to handle exceptional conditions--for example,last-minute schedule changes or special occurrences.

Exception Date Maintenance Screen

JOLXDT .x ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===> ** Exception Date Maintenance **

Xdate Id ===> 226 Desc ===> Test XDATE dates

**/03/03 _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________




Procedure

To create or edit an exception ID, follow these steps:

1. To edit an ID, enter X in the input field next to the ID on the List of ExceptionDate Definitions panel, or to add an ID, press PF4 (Add). In both cases, theException Date Maintenance panel is displayed.

2. If you are adding a new exception ID, enter a 3-digit identification number,ranging from 001-255, in the (Exception ID ===> field).

3. In the (Desc ===> field), enter a description of up to 20 characters.

4. Enter exception dates in yy/mm/dd format on blank lines, or type overexisting exception dates. You can substitute ** for yy, mm, or dd to globallymatch on any year, month, or day. Any defined date is considered anexception. You can preface a date with the "not" symbol (¬) or exclamationmark (!) to indicate that events are not to be run on that date.

5. To save changes, press PF4 (Write to Disk). IDs are displayed on the List ofException Date Definitions by ID panel.

Exception ID 000

The exception ID 000 is the default. It indicates that no exceptions are defined.You can't edit exception ID 000.


5–42 BIM-FAQS/PCS

Accessing the CPUID NODEID Synonym Table

Introduction

If you know which system CPUs you will be using, you can define synonyms fortheir CPU IDs on the CPUID NODEID Synonym Table. You can assign a nameor a word as a synonym for a 6-to-8-digit CPU ID.

One reason to define CPU ID synonyms is that it is easier to remember a namethan a 6-to-8-digit number. Using CPU ID synonyms may reduce user typingerrors. Another reason to define CPU ID synonyms is that if you need to changeCPUs, you need only to change the IDs in one place--on the CPU ID NODEIDSynonym Table.

Node IDs

Node IDs indicate remote systems on which you can execute events. You candefine node IDs using the BIM-GSS BIM$GMSR utility.

Procedure

To access the CPUID NODEID Synonym Table, select the CPU-Id SynonymTable option from the Configuration Options Menu Index by entering D at thecommand line. The CPUID NODEID Synonym Table is displayed.

CPUID NODEID Synonym Table

JOLCPU .D ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** CPUID NODEID SYNONYM TABLE **

SYNONYM CPUID SYNONYM CPUID VSE = FF039001 ________ = ________ VSENONE = 99999999 ________ = ________ VSE14 = 039002 ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________ ________ = ________




CPUID NODEID Synonym Table PF Keys

PF Key Description

PF1 Displays help information for this screen

PF3 Returns you to the previous screen

PF4 Writes the record to disk

Defining CPU ID Synonyms

Introduction

Synonyms for CPUs can be defined, then used in place of the 6-to-8-digit CPU IDin event definitions. Authorized users can define up to 32 synonyms.

Procedure

To define CPU ID synonyms, follow these steps:

1. Access the CPUID NODEID Synonym Table by selecting option D from theConfiguration Options Menu Index.

2. Enter a synonym in the SYNONYM column. The synonym value is 1-8characters.

3. In the CPUID column, enter the last 6 digits of the CPU ID. (For example, forCPU ID FF030047, enter 030047.)

4. Press PF4 (Write to Disk) to write the record to disk and pass the newinformation to the VSE machine where the function was performed. Thisstep must be done on each machine where the BIM-FAQS/PCS scheduler(JCLSCHED) is running.


5–44 BIM-FAQS/PCS

Specifying Dataset Exclusion

Introduction

The Dataset Exclusion option enables you to specify datasets to be monitored forexclusion. These are datasets that can be specified by an event with a datasetexclusion dependency. Include only those datasets that must not be open whenthe event is scheduled. You do not need to include datasets that will be used astriggers for open or close requests.


For more information about defining dataset dependencies, see theBIM-FAQS/PCS Operations Guide.

Dataset Exclusion Configuration Screen

JOLDSNC .N ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS Dataset Exclusion Configuration **

Dataset name monitored for exclusion Multi-CPU

AP.MASTER.FILE______________________________ N ____________________________________________ _ ____________________________________________ _ ____________________________________________ _ ____________________________________________ _ ____________________________________________ _ ____________________________________________ _ ____________________________________________ _ ____________________________________________ _ ____________________________________________ _ ____________________________________________ _ ____________________________________________ _ ____________________________________________ _ ____________________________________________ _ ____________________________________________ _ PF1=Help PF3=Return PF4=Save PF7=Bwd PF8=Fwd



Procedure

To specify dataset exclusion, follow these steps:

1. From the Configuration Menu Index, select the Dataset Exclusion option byentering N at the command line. The Dataset Exclusion Configuration Screenis displayed.

2. Enter the name of each dataset that can be specified by an event as a datasetexclusion dependency.

Note that generic names are not supported. If you specify an asterisk (*) as adataset name, all files will be monitored. This uses more system GETVISthan listing only the necessary dataset names.

3. In the Multi-CPU field, specify whether the dataset can be accessed fromother CPUs.

Y means the dataset can be accessed from other CPUs. Do not specify Y ifyour system does not use shared CPUs. This adds unnecessary overhead.

N means the dataset cannot be accessed from other CPUs.

4. Press PF4 (Save) to save the dataset exclusion definitions.

Storage Requirements

Dataset exclusion uses the following storage:

• System GETVIS: 48 bytes per active dataset name being monitored inincrements of 8 dataset names or 384 bytes

• Partition GETVIS: 48 bytes per active dataset name being monitored within apartition


5–46 BIM-FAQS/PCS

Specifying Dataset Logging Suppression

Introduction

Dataset logging collects dataset activity for reporting. The Dataset Loggingoption on the Configuration Menu Index enables you to specify datasets toexclude from logging. You can suppress dataset logging by:

• Partition

• Phase name

• VSE jobname

• Dataset name

Accessing the Dataset Logging Configuration Menu

To access the Dataset Logging Configuration Menu, select the Dataset Loggingoption from the Configuration Menu Index by entering T at the command line.

Dataset Logging Configuration Menu

JOLDSNC .T ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS Dataset Logging Configuration Menu **

C Suppression by Partition P Suppression by Phase Name J Suppression by VSE Jobname N Logged Dataset Names D Suppression by Dataset Name

PF1=Help PF3=Return



Specifying Dataset Logging by Partition

Introduction

You can control dataset logging by partition using the Dataset Logging PartitionConfiguration Screen. This screen enables you to specify the type of file andwhether it will be logged in a specific partition.

File Types

You can specify dataset logging by partition for any or all of the file types. Thefollowing table explains each valid file type and how it is referenced:

Type Reference

VSAM VSAM ACB

DASD DTFSD, DTFDA, and some DTFPH macros

TAPE DTFMT and some DTFPH macros

Dataset Logging Partition Configuration Screen

JOLDSNC .C ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS Dataset Logging Partition Configuration **

Type B F F F F F F F F F F F Dynamic Partition Classes G B A 9 8 7 6 5 4 3 2 1 C D E G H I J K L M N O P Q R S T U V W X Y Z

VSAM X X X X X X X X _ X X X X X X _ X X X X X X X X X X X X X X X X X X XDASD _ _ _ _ _ _ _ _ _ _ _ _ X X X X X X X X X X X X X X X X X X X X X X XTAPE X X X X X X X X _ X X X X X X X X X X X X X X X X X X X X X X X X _ X

PF1=Help PF3=Return PF4=Save


5–48 BIM-FAQS/PCS

Procedure

To specify dataset logging by partition, follow these steps:

1. From the Dataset Logging Configuration Menu, select the Suppress loggingby partition option by entering C at the command line. The Dataset LoggingPartition Configuration Screen is displayed.

2. Enter X under each static partition ID or dynamic partition class to indicatethat files of the specified type are eligible for dataset logging in that partition.

Blanks ( _ ) indicate that files of the specified type will not be logged in thatpartition.

3. Press PF4 (Save) to save.



Specifying Dataset Logging by Phase

Introduction

You can control dataset logging by program or phase using the Dataset LoggingPhase Exceptions Screen. This screen enables you to specify phases whosedataset activity will not be logged.

Dataset Logging Phase Exceptions Screen

JOLDSNC .0 ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS Dataset Logging Phase Exceptions **

PHASE PHASE PHASE PHASE PHASE

IDCAMS__ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ PF1=Help PF3=Return PF4=Save

Procedure

To specify dataset logging by phase, follow these steps:

1. From the Dataset Logging Configuration Menu, select the Suppress loggingby phase name option by entering P at the command line. The DatasetLogging Phase Exceptions Screen is displayed.

2. Enter all phases to be excluded from dataset logging. Exact names arerequired. Generic masks are not supported.



5–50 BIM-FAQS/PCS

Specifying Dataset Logging by VSE Job

Introduction

You can control dataset logging by VSE jobname using the Dataset Logging VSEJob Exceptions Screen. This screen enables you to specify VSE jobs whose datasetactivity will not be logged.

Dataset Logging VSE Job Exceptions Screen

JOLDSNC .0 ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS Dataset Logging VSE JOB Exceptions**

VSEJOB VSEJOB VSEJOB VSEJOB VSEJOB

TESTPAY_ TESTPAY2 LIBBKUP_ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ PF1=Help PF3=Return PF4=Save

Procedure

To specify dataset logging by VSE job, follow these steps:

1. From the Dataset Logging Configuration Menu, select the Suppress loggingby VSE jobname option by entering J at the command line. The DatasetLogging VSE JOB Exceptions Screen is displayed.

2. Enter all VSE jobs to be excluded from dataset logging. Exact names arerequired. Generic masks are not supported.




Including Datasets for Logging

Introduction

Another way to control dataset logging is to specify only those datasets you wantto have logged. By default, all datasets will be logged.

Logging Inclusion Screen

The following shows the Logging Inclusion Screen with the default/initial valueof * (all datasets):

JOLDSNC .N ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS Dataset Logging Names to Log **

Dataset Name

*___________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ PF1=Help PF3=Return PF4=Save

Procedure

To include datasets for logging, follow these steps:

1. From the Dataset Logging Configuration Menu, select the Logged DatasetNames option by entering N at the command line. The logging inclusionscreen is displayed.

2. Enter the datasets you want to have logged. Exact names are encouraged,but generic masks are supported:





5–52 BIM-FAQS/PCS

Excluding Datasets from Logging

Introduction

You can control dataset logging by dataset name using the Dataset LoggingName Exceptions Screen. This screen enables you to exclude datasets fromlogging.

Dataset Logging Name Exceptions Screen

JOLDSNC .D ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS Dataset Logging Name Exceptions **

Dataset Name

%VSE.*______________________________________ SQL*.USER.CATALOG___________________________ VSAM.MASTER.CATALOG_________________________ VSESP.USER.CATALOG__________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ PF1=Help PF3=Return PF4=Save

Procedure

To specify dataset logging by dataset name, follow these steps:

1. From the Dataset Logging Configuration Menu, select the Suppress loggingby dataset Name option by entering D at the command line. The DatasetLogging Name Exceptions Screen is displayed.

2. Enter all datasets to be excluded from logging. Exact names are encouraged,but generic masks are supported:






Defining Partner Node Names

Introduction

There is a new option on the Configuration Options Menu Index. Option J--Partner Node Names accesses the Node Name Configuration panel.

The Node Name Configuration panel enables you to specify which nodes in yournetwork you want BIM-FAQS/PCS to communicate with. When PCSLOG isstarted, BIM-FAQS/PCS sends a request to all GMF-enabled PSK nodes forremote system dependencies. All dependencies that BIM-FAQS/PCS willmonitor are sent to BIM-FAQS/PCS.

On the Node Name Configuration panel, you will specify

The nodes in the network that act as agents for BIM-FAQS/PCS and the nodesthat BIM-FAQS/PCS acts as an agent for.

Whether the event command should be converted to upper case characters or leftas typed when the event was defined.

Node Name Configuration Panel

The following is an example of the Node Name Configuration panel:

JOLONOD .J ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS Node Name Configuration **

Upper-Case Node Name All Commands PSK Node

TESTNODE Y N TESTNOD2 Y N TESTNOD3 Y N TESTNOD4 Y Y ________ _ _ ________ _ _ ________ _ _ ________ _ _ ________ _ _ ________ _ _ ________ _ _

PF1=Help PF3=Return PF4=Add/Update PF7=Bwd PF8=Fwd


5–54 BIM-FAQS/PCS

Procedure

To define node names, follow these steps:

1. Access the Node Name Configuration panel by selecting option J on theConfiguration Options Menu Index.

2. Enter an 8-character network name of a node in the Node Name field.

3. Enter N in the Upper Case All Commands field to ensure that the eventcommand associated with this node is saved as typed on the event definitionpanel.

The default is Y, which converts the command-line to uppercase characters.

4. Enter Y in the Node Is A PCS Agent field to signify to BIM-FAQS/PCS that itmust establish communications with this node in order to send and receiveevent data.

The default is N.

5. Press PF4 (Add/Update) to save your changes.


Chapter 6Defining Security


BIM-FAQS/PCS enables you to secure access to various BIM-FAQS/PCSfunctions. The different security options allow you to protect PDS members,event files, and utilities. You can also use the security structure to set up usergroups. These groups contain users with common functions and, therefore,similar security needs.

Steps to Defining Security

The following table outlines the steps suggested to establish a satisfactorysecurity structure:

Defining Initial Security

Perform the following steps to define initial security:

1. Select a user to be security administrator.

2. Add the security administrator's user ID to security, and enable theadministrator to update security and perform any other necessary functions.Set rules for the administrator before setting rules for the $DEFAULT userID.

3. Establish rules for the $DEFAULT user ID. BIM-FAQS/PCS security defaultsare assigned to $DEFAULT user ID. $DEFAULT user ID rules are applied toall user IDs who don't have security rules set for them.

4. Add remaining BIM-FAQS/PCS user IDs. You can define securityindividually or model IDs after an existing ID.

Overview

6–2 BIM-FAQS/PCS

Defining Security for BIM-FAQS/PCS Users

Perform the following steps to define security for BIM-FAQS/PCS Users

1. Define user ID classes.

2. Define PDS member security.

3. Define event group security.

4. Define event security.

5. Define global utility security.

6. Define user-class utility security.

7. Define node name security.

Security Member: JCLCONFG.CTL

The BIM-FAQS/PCS system is controlled by the JCLCONFG.CTL member. Thismember is created and maintained through the online system (via any of theBIM-FAQS/ASO or BCIN online interfaces). You may define a separate memberfor each PDS. If the PDS accessed does not contain a configuration, then BIM-FAQS/PCS uses the security configuration for the MON PDS.

The default JCLCONFG.CTL member is cataloged during installation inSYS$MON and demonstrates the basic parameter formats.

JCLCONFG.CTL is not intended for manual maintenance. The securityadministrator should use only the online system to access this member. All otherusers can be restricted from this member with the PDS Member Security Screen.The online system must be used to support enhanced BIM-FAQS/PCS features.

Security and Partitions

You must update security in every interface and partition. If your scheduler isrunning in a different partition than BIM-FAQS/PCS Online (where securityrules are updated), enter &SECLD in the partition where the scheduler isrunning. &SECLD loads the new security rules. If BIM-FAQS/PCS Online andthe scheduler are in the same partition, &SECLD is unnecessary.




Preliminary Security Considerations

Introduction

Online security is driven by the BIM-FAQS/ASO or CICS user IDs. To establishinitial security, you must:

• Determine who your security administrator will be and define appropriatesecurity options

• Create the $DEFAULT user ID options

Security Administrator

Once you've selected your BIM-FAQS/PCS security administrator, define all thesecurity rules and rights the administrator must have to establish and maintainsecurity for the rest of BIM-FAQS/PCS.

$DEFAULT User ID

BIM-FAQS/PCS security defaults are assigned to the $DEFAULT user ID.$DEFAULT user ID rules are applied to all user IDs that don't have security rulesset for them. For example, if the $DEFAULT user ID was allowed to retrievemembers from CMS only, then all user IDs that haven't had online security rulesdefined for them are able to retrieve members from CMS only.

Define Administrator Before $DEFAULT: Set up rules for the securityadministrator before setting up rules for the $DEFAULT user ID.

When Are Rules Initialized?

The following guidelines apply:

• If you are the security administrator, and you're defining additional rules foryourself, rules are updated at the point of pressing the Update PF key.

• If you are defining or modifying rules for users currently accessed to BIM-FAQS/PCS, those users must exit BIM-FAQS/PCS online, then reenter, forthe rules to be established.


6–4 BIM-FAQS/PCS

Screens Used to Define Initial Security

You must use the following screens to define the security administrator, modifythe $DEFAULT user ID options, and add remaining BIM-FAQS/PCS users:

• System Security Menu Index

• Security User IDs Screen

• Security System Maintenance Screen

These screens are described in the following section, "Accessing BIM-FAQS/PCSSecurity."



Accessing BIM-FAQS/PCS Security

Introduction

BIM-FAQS/PCS enables you to define security quickly and efficiently withonline menus and option screens.

To access BIM-FAQS/PCS security, select the System Security option from theMenu Index by entering S at the command line. The System Security MenuIndex is displayed.

System Security Menu Index

JOLSSEC .S ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS System Security - Menu Index **

O Online Function Security M Member Security V Event Group Security E Event Security G Global BIM-FAQS/PCS Utility Security U User Class BIM-FAQS/PCS Utility Security C User ID Classes N Event Node Name Security R Remote Node Name Security

PF1=Help PF3=Return PF6=Write Rules

Security Options

Option Function

Online FunctionSecurity

Secures access to online BIM-FAQS/PCS functions

Member Security Secures access to specific PDS members

Event Group Security Secures access to events by group ID

Event Security Secures access to specific BIM-FAQS/PCS events

Global Utility Security Specifies system-wide utility security options

User Class UtilitySecurity

Specifies user-class utility security options

Continued


6–6 BIM-FAQS/PCS

Continued

Option Function

User ID Classes Maintains user classes

Event Node NameSecurity

Secures event target node names for users.

Remote Node NameSecurity

Defines the GMF-enabled PSK nodes from whichBIM-FAQS/PCS will accept commands.

Security User IDs

To access a list of the BIM-FAQS/PCS user IDs, select the Online FunctionSecurity option from the System Security Menu Index by entering O at thecommand line. (If BIM-FAQS/PCS is a new installation, no user IDs are listed.)The Security User IDs Screen is displayed. See the following sample screen.The following table lists the functions available from the Security User IDsScreen:

If you want to Then

Define a securityadministrator

Press PF4 (Add). The Security System MaintenanceScreen is displayed and you can add securityadministrator rights.

Modify the$DEFAULT user ID

Enter U next to the $DEFAULT user ID. The SecuritySystem Maintenance Screen is displayed and you canmodify the $DEFAULT user ID's rights.

Add users Press PF4 (Add). The Security System MaintenanceScreen is displayed and you can add specific user IDrights. You can also model a new user after an existinguser.



Sample Security User IDs Screen

JOLUSEC .7 ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS Security User ID's **

USER ID MODEL ID USER ID MODEL ID USER ID MODEL ID

_ ASOMAINT $DEFAULT _ BC41 $DEFAULT _ BTAM0080 $DEFAULT _ DCM $DEFAULT _ BCIN $DEFAULT _ DRJ _ EKEHLER $DEFAULT _ MKJ $DEFAULT _ PCSMAINT _ PCSSERV $DEFAULT _ PROFILE $DEFAULT _ Q003 $DEFAULT _ Q008 $DEFAULT _ Q011 $DEFAULT _ Q013 $DEFAULT _ Q024 $DEFAULT _ ROB/BC42 _ ROBERT _ SJA $DEFAULT _ SYS/A001 $DEFAULT _ SYS/L77D $DEFAULT _ SYSA $DEFAULT

L=Delete M=Model U=Update PF1=Help PF3=Return PF4=Add PF7=Bwd PF8=Fwd

Security System Maintenance

You access the Security System Maintenance Screen from the Security User IDsScreen by performing one of the following actions:

• Press PF4 (Add) to add user ID security options

• Enter U next to a user ID to modify an ID

• Enter M next to a user ID to model an ID on the Security User IDs screen


6–8 BIM-FAQS/PCS

Online Security System Maintenance Screen

The Online Security System Maintenance Screen enables you to define BIM-FAQS/PCS online security. To access field-level help, place the cursor on aspecific input field on this screen and press PF1 (Help). The following screenshows the Online Security System Maintenance Screen:

JOLUSEC .u ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

**BIM-FAQS/PCS Online Security System Maintenance **

PCS/Online User ID ===> Model ID ===>

Y Allow BROWSE function. Y Allow REXX panel. Y Allow FLEE/VSE online. Y Allow BIM$PUTL panel. Y Allow UPDATE function. Y Allow Ext. Lib BROWSE/COPY Y Allow transfer to CMS. Y Event Administrator Y Allow transfer from CMS. Y Allow Beeper Panel Y Allow security definition. Y Allow Product Code maint. Y Allow SYSTEM Config update. Y Allow Online CICS commands Y Allow event maintenance. Y Allow MSHP Online Y Allow event forecasting. Y Allow Resource Display Y Allow audit function. Y Allow CPU definition. Y Allow Calendar definition. Y Allow accounting function. Y Allow Variable alteration. Y Allow Work Station Access.


Options

Option Explanation

Y Allows the user access to the specified function.

N Disallows the user access to the specified function. N suppressesthe function from displaying on online menus.



Event Administrator Options

The Event Administrator field enables you to control access to event files. Thefollowing table explains the valid options for the Event Administrator field:

Option Explanation

Y Allows users access to all event files.

N Limits users' ability when accessing event files. Users can displayand browse the event file, but cannot edit events. Users can requestor demand events to the current file.

A Allows users access to all event files, but they cannot create newevents.

U Limits users' ability when accessing the current file. Users candisplay only events that they requested to the current file and thatwere set up with an event day of REQUEST.

If You Don't Have CMS

If you don't have CMS, you can suppress the Receive from CMS and Transfer toCMS fields on the Menu Index. On the Security System Maintenance Screen,enter N in the Allow Transfer to CMS and Allow Transfer from CMS fields.

For More Information: See the BIM-FAQS/PCS Operations Guide for adescription of the CMS fields on the Menu Index.


6–10 BIM-FAQS/PCS

Defining Your Security Administrator

Introduction

The BIM-FAQS/PCS security administrator establishes and maintains BIM-FAQS/PCS security. Select the user or users who should have such authority,and complete the steps for defining a security administrator.

Defining a Security Administrator

Take the following steps to establish a user ID with security administrator rights:

1. From the System Security Menu Index, select the Online Function Securityoption by entering O at the command line. The Security User IDs Screen isdisplayed.

2. To add a user ID, press PF4 (Add). The Security System Maintenance Screenis displayed.

3. Enter the security administrator's user ID in the (PCS/Online User ID field).To allow the administrator to define security, enter Y next to the Allowsecurity definition field. Then enter Y next to each of the other onlinefunctions the administrator should be able to use.

4. To update security rules in the PDS, press PF4 (Update).



Modifying the $DEFAULT User ID

Introduction

By default, all users have access to all functions. The default security ismaintained by the $DEFAULT user ID, which is supplied with the BIM-FAQS/PCS installation. For any users not specifically defined in security, the$DEFAULT user ID rules apply. Once a security administrator is defined, theadministrator can define security for the $DEFAULT user ID.

Because the supplied $DEFAULT user ID security definition enables completesystem access, it is recommended that you modify the $DEFAULT user IDimmediately. Modify the $DEFAULT user ID to reflect only those security rightsyou wish all of your users to have.

Modifying the $DEFAULT User ID

In modifying the security rules for the $DEFAULT user ID, you can preventaccess to all functions by default. To do this, follow these steps:

1. On the Security System Maintenance Screen, enter N next to all of the rules.

2. Press PF4 (Update) to update the rules for the $DEFAULT user ID.

$DEFAULT user ID security rules apply to all new BIM-FAQS/PCS users atinitial signon.

3. If a user ID is deleted, rules are not deleted until that user exits BIM-FAQS/PCS, then reenters. Upon reentry, the $DEFAULT user ID rules areinitialized.


6–12 BIM-FAQS/PCS

Defining Security Rules for All Other Users

Introduction

Once a security administrator is defined, the administrator can define security forall other BIM-FAQS/PCS users. The security administrator can perform thefollowing functions:

• Adding a user ID

• Updating a user ID

• Modeling a user ID

• Deleting a user ID

The security administrator can base security rules on the unique tasks performedby specific users, or on user groups defined by a model user ID.

How Is a User ID Established

BIM-FAQS/PCS user IDs are listed in alphanumeric order on the Security UserIDs Screen. The user ID is either the CICS 3-character identifier taken from theDFHSNT OPID field, or the BIM-FAQS/ASO user ID or VM/CMS user ID of theuser accessing the BIM-FAQS/PCS online system.

What Is a Model ID?

Model user IDs allow you to maintain many user IDs with identical securityaccess. For example, if you want several computer operators to have the samesecurity privileges, you can define a new or existing user with those privileges,and then model all the other operators after that user ID.

The model ID can be any defined BIM-FAQS/PCS user ID. When the model userID is changed, every ID based on that model operates with those changes at thenext signon to BIM-FAQS/PCS.



Adding a User IDTo add online security rules for an BIM-FAQS/PCS user, follow these steps:


2. To add a new user ID, press PF4 (Add). The Security System MaintenanceScreen that defines security for the specified user is displayed. This screenlists all the functions that can be secured.

3. Enter the new user ID at the (PCS/Online User ID ===> field), and enter Ynext to the functions you want that user ID to be able to access.

4. To update security rules in the PDS, press PF4 (Update).

Updating a User ID

To update online security rules for an BIM-FAQS/PCS user, follow these steps:


2. To update a user ID, enter U in the input field next to the user ID and pressENTER. The Security System Maintenance Screen that defines security forthe specified user is displayed. This screen lists all the functions that can besecured.

3. To update an existing user ID, enter Y next to the functions you want thatuser ID to be able to access.

4. To update security rules in the PDS, press PF4 (Update). The definitions thatapply to that user ID are intitialized upon that user's reentry to BIM-FAQS/PCS.


6–14 BIM-FAQS/PCS

Modeling a User ID

To model one ID's online security rules after another BIM-FAQS/PCS user,follow these steps:


2. To model a user ID, enter M in the input field next to the user ID and pressENTER. The Security System Maintenance Screen that defines security forthe specified user is displayed. This screen lists all the functions that can besecured.

3. To use a model ID, enter the defined BIM-FAQS/PCS user ID at the(Model ID ===> field) that you want the user ID to model.

4. To update security rules in the PDS, press PF4 (Update). The definitions thatapply to that model ID are applied to the associated user IDs upon reentry toBIM-FAQS/PCS.

Deleting a User ID

To delete online security rules for an BIM-FAQS/PCS user, follow these steps:


2. To delete a user ID, enter L in the input field next to the user ID.

3. Press ENTER. The user ID is deleted.

Defining the Rest of Security



Defining User ID Classes

Introduction

The User ID Classes option on the System Security Menu Index enables anadministrator to maintain user classes. User classes are used to group user IDswith similar characteristics. You can establish user groups for security orconfiguration purposes.

User classes are presented in alphanumeric order on the User ID Classes Screen,with the first 10 user IDs of each class shown. A user group can contain one ormore user IDs.

If you specify the same user ID more than once in a class, the system will use thelast occurrence.

Accessing User ID Classes

To access user ID classes, select the User ID Classes option from the SystemSecurity Menu Index by entering C at the command line. The User ID ClassesScreen is displayed.

Sample User ID Classes Screen

JOLUCL .C ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS User ID Classes **

CLASS USER IDs

_ A ADMN PCSMAINT

_ B ROBERT

_ Z U17 U18 U19 U20 U21 U23 U24 U25 U26 U27

L=Delete O=Options S=Security U=Update PF1=Help PF3=Return PF4=Add PF6=Update PF7=Bwd PF8=Fwd


6–16 BIM-FAQS/PCS

Defining User Classes

To define user ID classes, follow these steps:

1. From the System Security Menu Index, select the User ID Classes option byentering C at the command line. The User ID Classes Screen is displayed.

2. To add a new class of user IDs, press PF4 (Add). To maintain a user class,enter one of the following maintenance options in the input field next to theclass: L, O, S, or U.

3. The User ID Class Screen is displayed.

Maintenance Options

The following table describes the maintenance options you can enter in the inputfield to the left of defined classes on the User ID Classes Screen:

Option Function

L Deletes a user class.

O Displays configuration options associated with a user class. Formore information about online and batch class configurationoptions, see Chapter 5, “Defining System Configuration.”

S Displays security options associated with a user class.

U Displays all user IDs within a user class, enabling you to maintainthe class.



Sample User ID Class Screen

JOLUCL .u ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS Userid Class **

USER CLASS ===> A

ADMN PCSMAINT ________ ________ ________ ________ ________

________ ________ ________ ________ ________ ________ ________

________ ________ ________ ________ ________ ________ ________

________ ________ ________ ________ ________ ________ ________

________ ________ ________ ________ ________ ________ ________

________ ________ ________ ________ ________ ________ ________

________ ________ ________ ________ ________ ________ ________

________ ________ ________ ________ ________ ________ ________

PF1=Help PF3=Return PF6=Update PF7=Bwd PF8=Fwd

Adding Users to Classes

When creating a user class on the User ID Class Screen, enter the new 1-characteruser class, then enter the new user IDs associated with that class. If you aremaintaining a user class, you can add, change, or delete user IDs in the class byovertyping null fields or existing user IDs, or erasing existing user IDs.

To update the user ID class changes on disk, press PF6 (Update).


6–18 BIM-FAQS/PCS

Defining Member-Level Security

Introduction

The Member Security option on the System Security Menu Index enables you tosecure all access to specific PDS members.

The Member Security Rules Screen lists the current authorization rules that applyto PDS members. BIM-FAQS/PCS PDS member access may be restricted toprevent unauthorized access.

Accessing Member Security Rules

To access PDS member-level security, select the Member Security option from theSecurity Menu Index by entering M at the command line. The Member SecurityRules Screen is displayed.

Restricting Update Access to JCLCONFG.CTL

To prevent update access to the JCLCONFG.CTL member, the PDS memberwhere security and configuration rules are stored, you should allow updateaccess only to the security administrator.

Sample Member Security Rules Screen

JOLSMEM .M ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS Member Security Rules **

MEMBER AUTHORIZATION LEVELS NAME READ UPDATE EXECUTE

_ *.RJD Y N Y _ EVT:*.EVT N N N _ MON:JCLDOC.MON Y N Y

U=Update PF1=Help PF3=Return PF4=Add PF6=Write Rules PF7=Bwd PF8=Fwd

Authorization Levels

The security administrator can authorize users to read and execute PDS memberswithout being able to update them. The administrator cannot, however,authorize users to have read-only access through a single rule.



Defining Member-Level Security Rules

To define PDS member-level security, follow these steps:

1. From the System Security Menu Index, select the Member Security option byentering M at the command line. The Member Security Rules Screen isdisplayed.

2. To add a member name, press PF4 (Add). To update a member name, enterU in the input field next to the member name.

3. The Member Level Security Rules Screen that shows the definitions for aspecified member is displayed. See the following screen.

Member Level Security Rules Screen

JOLSMEM .u ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===> ** BIM-FAQS/PCS Member Level Security Rules ** Member = MON:JCLDOC.MON (Format=> PDS:mmmmmmmm.ttt)

Specify type of Security by placing an X next to one of the following

Restrict from:

UPDATE X READ and UPDATE _ ALL access _ EXECUTE _

Security applies to USERID's or classes: (default=ALL) User1 ===> User2 ===> User3 ===> User4 ===> User5 ===> User6 ===> User7 ===>

Authorized USERID's or classes to BYPASS this security rule: User1 ===> ADMN User2 ===> User3 ===> User4 ===> User5 ===> User6 ===> User7 ===>

PF1=Help PF3=Return PF6=Write Rules PF9=Delete

Adding Rules for a PDS Member

To add rules for a PDS member, enter a member name in the Member= field.


6–20 BIM-FAQS/PCS

PDS Member Format

The following format is required to add a member name:ppp:mmmmmmmm.ttt

Variables ExplainedThe following table explains the variable information in the PDS member name:


ppp PDS ID. If ppp is not entered, the default ID is MON.

mmmmmmmm Full or partial member name. Masking characters can beused.

ttt Member type. If ttt is not entered, the default type is MON.

Masking Characters: To enter a partial member name, use the maskingcharacters + and *. Use + to match one character. For example, the name +XYZ+matches any 5-character member name, as long as the second, third, and fourthcharacters are XYZ. Use * to match a group of characters. For example, the name*XYZ* matches any member name that contains the character string XYZ.

Limiting Access to PDS MembersRestrict from: This group of fields enables you to protect PDS members byrestricting the kinds of functions performed on the PDS. Enter X in the inputfield of one of the following:

Field What the PDS Member is Protected From

UPDATE Users can't update a PDS member. However, users can stillread and execute the PDS member.

ALL access Users can't access a PDS member.

READ andUPDATE

Users can't read or update a PDS member. However, userscan execute the PDS member.

EXECUTE Users can't execute from a PDS member. However, userscan read and update the PDS member.



Defining Rules by User ID or Class

Security applies to USER IDs or classes: This group of fields enables you todetermine whether PDS member rules apply to specific user IDs or user IDclasses. You can also use these fields to restrict only certain user IDs or user IDclasses. A user ID class is a single-character user ID.

Authorized USER IDs or classes to BYPASS this security rule: This group offields enables you to determine whether user IDs or user ID classes are excludedfrom this rule. At least one user ID must be specified. If there are no exceptionsto this rule, a nonexistent user ID may be specified.

Updating Rules

After PDS security rules have been defined, press ENTER. Then press PF6 (WriteRules) to save the changes. All member and event options, configuration options,and security options are updated at this time.

Deleting Rules

To delete rules for a PDS member, press PF9 (Delete) from the Member LevelSecurity Rules Screen. Then press PF6 (Write Rules) to save the deletion.


6–22 BIM-FAQS/PCS

Defining Event Group Security

Introduction

The Event Group Security option on the System Security Menu Index enablesyou to secure access to events by group ID. Once event group security rules areestablished, only authorized users can see those events. Unauthorized userscannot display the events nor update them in any way.

Accessing Event Group Security

To access event group security, select the Event Group Security option from theSystem Security Menu Index by entering V at the command line. The EventGroup Security Rules Screen is displayed.

Sample Event Group Security Rules Screen

JOLSGRP .V ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS Event Group Security Rules **

EVENT GROUP SCHEDULE

_ AXPSYS MASTER _ AXPSYS CURRENT _ PCSSYS MASTER _ TRIAL CURRENT _ TRIAL MASTER




Defining Event Group SecurityTo define event group security, follow these steps:

1. From the System Security Menu Index, select the Event Group Securityoption by entering V at the command line. The Event Group Security RulesScreen is displayed.

2. To add a new rule to an event group, press PF4 (Add). To update an eventgroup, enter U in the input field next to the event group name.

3. The Event Level Security Rules Screen that defines security for the specifiedevent group is displayed. See the following screen.

Event Level Security Rules Screen

JOLSGRP .u ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===> ** BIM-FAQS/PCS Event Level Security Rules ** Group ===> PCSSYS

Specify type of Security by placing an X next to proper selection

Restrict from:

X ALL MASTER access _ ALL CURRENT access


Authorized USERID's or classes to BYPASS this security rule: User1 ===> PCSMAINT User2 ===> ROBERT User3 ===> User4 ===> User5 ===> User6 ===> User7 ===>


Adding Event Group Security Rules

To add an event group security rule, enter an event group name in the (Group=field) on the Event Level Security Rules Screen. Unauthorized users cannot evenview events within secured groups.

To specify all event groups, enter * as a mask character.


6–24 BIM-FAQS/PCS

Limiting Access to Event Groups

Restrict from: This group of fields enables you to restrict event group security tothe master or current schedule. Users authorized to access the event group areallowed to access all events on the schedule, unless restricted by individual eventsecurity rules. To specify a schedule restriction, enter X in the input field next tothe proper selection.


Security applies to USER IDs or classes: This group of fields enables you todetermine whether event group rules apply to specific user IDs or user IDclasses. You can also use these fields to restrict only certain user IDs or user IDclasses. A user ID class is a single-character user ID.

Authorized USER IDs or classes to BYPASS this security rule: This group offields enables you to determine whether user IDs or user ID classes are excludedfrom this rule. At least one user ID must be specified. If there are no exceptionsto this rule, a nonexistent user ID may be specified.

Updating Rules

After event group security rules have been defined, press ENTER. Then pressPF6 (Write Rules) to save the changes. All member and event options,configuration options, and security options are updated at this time.

Deleting Rules

To delete rules for an event group, press PF9 (Delete) from the Event LevelSecurity Rules Screen. Then press PF6 (Write Rules) to save the deletion.

Securing Events By Group Rules

Once event group security rules are established, only authorized users can seethose events. Unauthorized users cannot display the events nor update them inany way.



Defining Event-Level Security

Introduction

The Event Security option on the System Security Menu Index enables you tosecure access to specific events.

Accessing Event Security Rules

To access event-level security, select the Event Security option from the SystemSecurity Menu Index by entering E at the command line. The Event SecurityRules Screen is displayed.

Sample Event Security Rules Screen

JOLSEVT .E ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS Event Security Rules **

EVENT NAME AUTHORIZATION LEVELS

_ TESTMAN5 MASTER UPDATE _ TESTMAN5 CURRENT UPDATE



6–26 BIM-FAQS/PCS

Defining Event-Level SecurityTo define BIM-FAQS/PCS event-level security, follow these steps:

1. From the System Security Menu Index, select the Event Security option byentering E at the command line. The Event Security Rules Screen isdisplayed.

2. To add an event name, press PF4 (Add). To update an event name, enter Uin the input field next to the event name.

3. The Event Security Rules Screen that defines security for the specified eventname is displayed. See the following screen.

Sample Event Security Rules Screen

JOLSEVT .u ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===> ** BIM-FAQS/PCS Event Security Rules ** Event = TESTMAN5

Specify type of Security by placing an X next to proper selection

Restrict from:

X MASTER Update _ CURRENT Update _ CURRENT Hold _ CURRENT Unhold _ CURRENT Post _ CURRENT Reset

Security applies to user ID's or classes: (default=ALL) User1 ===> User2 ===> User3 ===> User4 ===> User5 ===> User6 ===> User7 ===>

Authorized user ID's or classes to BYPASS this security rule: User1 ===> PCSMAINT User2 ===> User3 ===> User4 ===> User5 ===> User6 ===> User7 ===>


Adding Rules for an Event

To add an event name, enter a specific event name or a generic event mask in the(Event= field) on the Event Security Rules Screen.

Masking Characters: To enter a partial event name, use the masking characters +and *. Use + to match one character. For example, the name +XYZ+ matches any5-character event name, as long as the second, third, and fourth characters areXYZ. Use * to match a group of characters. For example, the name *XYZ*matches any event name that contains the character string XYZ.



Limiting Access to EventsRestrict from: This group of fields enables you to protect events by restrictingthe kinds of functions performed on those events. Enter X in the input field ofone of the following:

Field What the Event is Protected From

MASTER Update Users can't update the master schedule.

CURRENT Update Users can't update the current schedule.

CURRENT Hold Users can't place an event on the current schedule onhold.

CURRENT Unhold Users can't release an event on the current schedule frombeing on hold.

CURRENT Post Users can't post an event on the current schedule.

CURRENT Reset Users can't reset an event on the current schedule.


Security applies to USER IDs or classes: This group of fields enables you todetermine whether event rules apply to specific user IDs or user ID classes. Youcan also use these fields to restrict only certain user IDs or user ID classes. A userID class is a single-character user ID.

Authorized USER IDs or classes to BYPASS this security rule: This group offields enables you to determine whether user IDs or user ID classes are excludedfrom this rule. At least one user ID is required to be specified. If there are noexceptions to this rule, a nonexistent user ID may be specified.

Updating Rules

After event security rules have been defined, press ENTER to return the cursor tothe command line. Then press PF6 (Write Rules) to save the changes. Allmember and event options, configuration options, and security options areupdated at this time.

Deleting Rules

To delete rules for an event, press PF9 (Delete) from the Event Security RulesScreen. Then press PF6 (Write Rules) from the Event Security Rules Screen tosave the deletion.


6–28 BIM-FAQS/PCS

Event Group Versus Event-Level Rules

If both event group rules and event-level rules are defined for a particular event,event group rules override event-level rules.

Defining Global Utility Security

Introduction

The Global Utility Security option on the System Security Menu Index enablesyou to specify entire system utility security options. These options pertain to allusers that do not have specific user class security options set up.

Use these options for normal security rather than special security situations.

Accessing Global Utility Security

To access global utility security, select the Global Utility Security option byentering G at the command line. The Global Utility Security Screen is displayed.

Sample Global Utility Security Screen

JOLSSEC .G ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS Global Utility Security **

Current User Classes: ABZ

Y All JCLRCICS functions allowed Y JCLRCICS dataset Open/Close allowed Y JCLRCICS DL/I Open/Close allowed Y BIM$OIEI DEL= command allowed Y BIM$OIEI submit allowed Y BIM-FAQS/PCS utility access via ICCF interface Y JCLMAINT member ADD allowed Y JCLMAINT member DELETE allowed Y JCLMAINT/BIM$OIEI member REPLACE N JCLMAINT member REPLACE CTL key required Y JCLMAINT member UPDATE allowed N BIM$OIEI update allowed Y JCLXCU allowed to issue OPERATOR commands

PF1=Help PF3=Return PF6=Write rules



Specifying RulesTo define security rules, follow the steps below:

1. From the System Security Menu Index, select the Global Utility Securityoption by entering G at the command line. The Global Utility SecurityScreen is displayed.

2. Set up rules by allowing (Y) or denying (N) access to each BIM-FAQS/PCSutility listed.

3. To update the values on disk, press ENTER; then press PF6 (Write rules).

Current User Classes

The Current User Classes field at the top of the Global Utility Security Screenindicates the user classes that exist, if any. If user classes are defined, the optionsdefined on this screen do not affect the users in those classes.

Utility Security OptionsThe following table lists the different BIM-FAQS/PCS utilities and what enablingthem does:

Utility Function

All JCLRCICSfunctions allowed

Allows use of JCLRCICS. Full use is allowed unlessexplicitly restricted to open and close.

JCLRCICS datasetOpen/Close allowed

Restricts JCLRCICS to allowing only open and closeprivileges. This field is overridden by class security.

JCLRCICS DL/IOpen/Close allowed

Restricts JCLRCICS to allowing only open and closeprivileges on DL/I databases.

BIM$OIEI DEL=command allowed

Allows use of the DEL=pds member command whenupdating a member.

BIM$OIEI submitallowed

Allows jobstream submission from the system editor.This includes submitting jobs using .mmmmmmmm fromthe BIM-FAQS/ASO interface, entering SUBMIT orpressing PF12 while editing a jobstream, and using thesubmit option from the update member screen.

BIM-FAQS/PCSutility access via ICCFinterface

Allows execution of BIM-FAQS/PCS utilities within theICCF interactive partitions.

Continued


6–30 BIM-FAQS/PCS

Continued

Utility Function

JCLMAINT memberADD allowed

Allows addition of PDS members using the JCLMAINTADD function in batch.

JCLMAINT memberDELETE allowed

Allows deletion of PDS members using the JCLMAINTDEL function in batch.

JCLMAINT/BIM$OIEI member REPLACE

Allows replacement of PDS members using theJCLMAINT REP function in batch.

JCLMAINT memberREPLACE CTL keyrequired

Requires LOGOUT control when members are replacedusing JCLMAINT.

JCLMAINT memberUPDATE allowed

Allows updates of PDS member using the JCLMAINTUPD function in batch. If JCLMAINT UPD is allowed,then system editor updates must be allowed.

BIM$OIEI updateallowed

Allows updates of PDS members when using the systemeditor. This utility can be disallowed only whenJCLMAINT updates are disallowed too.

JCLXCU allowed toissue OPERATORcommands

Allows issuance of operator commands from JCLXCU.



Defining User Class Utility Security

Introduction

The User Class Utility Security option on the System Security Menu Indexenables you to specify user class utility security options.

Accessing User Security Classes

To access user class utility security, select the User Class Utility Security optionfrom the System Security Menu Index by entering U at the command line. TheUser Security Classes Screen is displayed.

Sample User Security Classes Screen

JOLSSEC .U ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS User Security Classes **

Current User Classes: ABZ Security Class ===> A

Y ALL JCLRCICS functions allowed Y JCLRCICS dataset Open/Close allowed Y JCLRCICS DL/I Open/Close allowed Y BIM$OIEI DEL= command allowed Y BIM$OIEI submit allowed Y BIM-FAQS/PCS utility access via ICCF interface Y JCLMAINT member ADD allowed Y JCLMAINT member DELETE allowed Y JCLMAINT/BIM$OIEI member REPLACE N JCLMAINT member REPLACE CTL key required Y JCLMAINT member UPDATE allowed N BIM$OIEI update allowed Y JCLXCU allowed to issue OPERATOR commands

PF1=Help PF3=Return PF4=Add PF6=Write PF7=Bwd PF8=Fwd PF9=Del


6–32 BIM-FAQS/PCS

Defining Utility Security by User ClassesTo define user security classes, follow these steps:

1. From the System Security Menu Index, select the User Class Utility Securityoption by entering U at the command line. The User Security Classes Screenis displayed.

2. To add a new user class, press PF4 (Add). The User Security Classes Screenthat enables you to specify rules for user classes is displayed.

3. Enter the new security class name in the (Security Class===> field) thatappears on the screen that's displayed after pressing PF4 (Add) from theUser Security Classes Screen.

Specifying RulesTo define security rules, follow the steps below:

1. From the System Security Menu Index, select the User Class Utility Securityoption by entering U at the command line. The User Security Classes Screenis displayed.

2. Set up rules by allowing (Y) or denying (N) access by class to the utilities.

3. To update the values on disk, press ENTER; then press PF6 (Write).

Deleting Rules

To delete rules for a user class, press PF9 (Del). Then press PF6 (Write) to savethe deletion.

Current User Classes

The Current User Classes field at the top of the User Security Classes Screenindicates the user classes that exist, if any. If users are defined based on thisclass, the options defined on this screen do not affect the users in those classes.



Defining Event Node Name Security Rules

Introduction

There are two new options on the System Security Menu Index:

• Option N accesses the Event Node Name Security Rules panel. Use thispanel to secure event target node names for users.

• Option R accesses the Remote Node Name Security Rules panel. Use thispanel to define the GMF-enabled PSK nodes from which BIM-FAQS/PCSwill accept commands.

Event Node Name Security

The Event Node Name Security Rules panel enables you to establish userauthority for your nodes.

When you define an event on the Event Maintenance Edit panel, you can enter anode name in the Target Node field. This field identifies the node name of aremote system that will execute the action specified in the event command.

By establishing node name security, you can prevent users from entering a nodename that they are not authorized to use.

For example, a user cannot enter SECURE01 if this node name is controlled bynode name security rules. To enter this name in the Target Node field, the usermust be added to the security rule for the SECURE01 node name.

Event Node Name Security Rules Panel

The following is an example of the Node Name Security Rules panel:

JOLSNOD .N ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS Node Name Security Rules **

Node Name SCHEDULE

_ BIM MASTER



6–34 BIM-FAQS/PCS

Adding or Updating Node Name Security RulesTo add a new node name security rule, or to edit an existing rule, take thefollowing steps:

1. Access the Node Name Security Rules panel by selecting option N on theSystem Security Menu Index.

2. To add a new rule, press PF4 (Add). The Node Name Security Rules(Update) panel is displayed.

3. To edit an existing rule, tab to the desired node name and press ENTER orenter U in the input field and press ENTER. The Node Name Security Rules(Update) panel is displayed.

4. Enter a specific or generic node name in the Node field. Node Name securitywill secure the node from all types of access by unauthorized users.

Node name security can be restricted to the master and current eventschedules with a single security rule.

5. Specify the users that this rule applies to. You can restrict specific user IDs oruser ID classes. A user ID class is a single-character ID.

6. Specify the users that are excluded from this rule. You can authorize specificuser IDs or user ID classes. A user ID class is a single-character ID.

You must specify at least one user ID. If there are no exceptions to this rule,you can specify a non-existent user ID.

7. Press PF6 (Write Rules) to save your changes. All configuration and securityoptions are updated.



Node Name Security Rules (Update) Panel

The following is an example of the Node Name Security Rules (Update) panel:

JOLSNOD .u ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===> ** BIM-FAQS/PCS Node Name Security Rules ** Node ===> BIM


Authorized USERID's or classes to BYPASS this security rule: User1 ===> A User2 ===> User3 ===> User4 ===> User5 ===> User6 ===> User7 ===>



6–36 BIM-FAQS/PCS

Defining Remote Node Name Security Rules

Introduction

The Remote Node Name Security Rules panel enables you to define which GMF-enabled nodes that BIM-FAQS/PCS will accept commands and messages from.By establishing remote node name security, you can authorize specific nodes tosend messages to BIM-FAQS/PCS; hence, you can prevent nodes from sendingmessages and running commands on BIM-FAQS/PCS.

Remote Node Name Security Panel

The following is an example of the Remote Node Name Security Rules panel:

JOLRNOD .R ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS Nodes from which messages are accepted **

Node Name Node Name Node Name

BIM ________ ________ P390 ________ ________ VSE ________ ________ VSEEPIC ________ ________ VSEPCS ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________


ProcedureTo define remote node name security, follow these steps:

1. Access the Remote Node Name Security Rules panel by selecting option R onthe System Security Menu Index.

2. In the Node Name fields, enter the 1-to-8-character network names of thenodes that BIM-FAQS/PCS will accept messages and commands from.

3. Press PF4 (Update) to save your changes.


Chapter 7PCSEVRP: Event Report Writer

This chapter covers the batch utility PCSEVRP. With PCSEVRP, you can definethe contents and layout of event reports. A variety of commonly used predefinedreports is also provided.


With the batch utility PCSEVRP you can define the contents and layout of eventreports. A variety of commonly used predefined reports is also provided.

PCSEVRP can be run in VSE or CMS.

Enhanced Feature

PCSEVRP has been enhanced with new control statements. Use PCSEVRP inplace of the older and less flexible JCLEVNT commands LIST and LISTDIR.

Sample JCL

To give you a feel for the PCSEVRP report writer language, the following sampleJCL shows how some of the control statements work.

// EXEC PCSEVRP,SIZE=PCSEVRP

ACTION LISTFILE MASTERTITLE1 'B I MOYLE ASSOCIATES, INC'TITLE2 'EVENTS THAT BEGIN WITH THE LETTER "A"'TITLE3 'SORTED BY EARLY TIME'

SELECT (EVENT(1) EQ A)PRINT EVENT GROUP DESC EARLY LATE ABORTSORT EARLY EVENT

END

Overview

7–2 BIM-FAQS/PCS

Sample Report

The sample JCL contains these statements:

• ACTION statement - Specifies the LIST option

• FILE statement - Selects the master event directory as the basis for the report

• TITLE statements - Give the report a title

• SELECT statement - Screens the master event directory by testing the valuesof specific fields

• PRINT statement - Defines the content and format of the print lines

• SORT statement - Puts the data in desired order

• END statement - Marks the end of the definition

PCSEVRP Control Statements

ControlStatement

Function

ACTION Supplies options and control information

END Marks the end of a report definition when multipledefinitions are included in the same job

FORECAST Specifies date to forecast scheduling

INCLUDE Includes predefined control statements

PRINT Controls format of printed event data

SELECT Filters events selected for printing

SORT Controls printing sequence of events

TITLE Specifies additional report title information

..* Indicates a comment

Overview


Usage Rules

The following rules apply to using PCSEVRP:

• You can specify PCSEVRP control statements in any order.

• All control statements are optional, except PRINT. Without a PRINTstatement, no report will be generated.

• All control statements can be specified multiple times in a definition. Ifstatements conflict (e.g., multiple FILE statements), the system will use thelast occurrence.

• A control statement can not be longer than 72 characters.

• Besides control statements, you can use blank lines in a report definition tomake it more readable.

• PCSEVRP ignores leading, trailing, and multiple embedded spaces in controlstatements.

Event Definition Fields

7–4 BIM-FAQS/PCS

Event Definition FieldsIntroduction

The PCSEVRP control statements reference the event definition fields.

Format

Use the keywords in this section to refer to event definition fields for selection orprinting. By default, reference to a name by itself implies an offset of 0 and alength that corresponds with the item being referenced.

The format for referring to a field is as follows:control_stmt [keyword_type] keyword[+nn][(nn)]

No embedded blanks are allowed.

Example

For example, suppose the event definition field EVENT contains the value12345678. Here are the results of various field references:

If the statement is This is the result

PRINT EVENT 12345678

PRINT EVENT(2) 12

PRINT EVENT+2 345678

PRINT EVENT+2(3) 345

Data Types

Numeric fields are right justified. You can select them without specifyingleading zeros.

Character fields are left justified.



Base Event Definition Fields

The following fields are unique in that they occur only once in an eventdefinition. As a result, you can specify their sorting sequence using the SORTstatement.

Keyword Field Explanation Type Length Format Heading

ABORT Abort time Num 4 ABRT

ABNDRC ABND RC Num 4 Can be blanks ABRC

CAL Event day Char 12 DAY

CALID Holiday ID Num 3 HOL

CART Tape cartridge Num 2 CT

CLASS POWER class override Char 1 C

COMMAND Event command Char 55 COMMAND

CPUID CPU ID Char 8 CPUID

CYCLE Cycle ID Num 3 CYC

EASYDAY Easy day Char 12 Selection format:

Day ro value

ro is any relationaloperator. value canbe any one of thefollowing: OR, NOT,MON, TUE, WED,THU, FRI, SAT, SUN

Print format:

"OR ¬ MTWTFSS"

EASY DAY

DESC Event description Char 16 DESCRIPTION

DISP POWER dispositionoverride

Char 1 D

EARLY Early time Num 4 ERLY

EDATE End date Char 8 yy/mm/dd EDATE

EVENT Event name Char 8 EVENTContinued


7–6 BIM-FAQS/PCS

Continued


EXCLUDE Exclude Char 80 EXCLUDE

EXCLTYPE Exclude type Char 3 JOB or EVT EXCLTYPE

FREQ Frequency Num 4 FREQ

GROUP Group name Char 8 GROUP

HOLD Event hold Char 1 Y or N H

HOLIDAY Holiday action Char 1 S, N, W, O, P, orblank

H

LATE Late time Num 4 LATE

LASTUPD Timestamp Char 19 yy/mm/ddhh:mm:ss

LAST UPDATED

NODENAME Node name Char 8 NODENAME

NWORK Non-workday action Char 1 S, N, W, O, P, orblank

N

OCCUR Occurrences Num 3 Can be “*” OCC

PRI POWER priorityoverride

Num 1 P

SDATE Start date Char 8 yy/mm/dd SDATE

STATUS Event status Char 4 STAT

SYSID POWER SYSIDoverride

Char 1 S

TAPES Tape reels Num 2 TP

XDATE Exception date Num 3 XDT



WHEN Fields

The following fields describe the WHEN clause. Up to eight WHEN clauses canbe defined per event. Because these fields can occur more than once, you cannotuse them with the SORT statement.

The keyword_type is WHEN. The following is an example of the WHEN format:PRINT WHEN MRC


CC IBM cancel code Char 2 CC

CONDMRC Condition MRC Char 2

CONDRC Condition RC Char 2

CONDCC Condition CC Char 2

CONDPN Condition partition ID Char 2

CONDCPU Condition CPU ID Char 2

CONDTIME Time condition shouldoccur

Char 2

CONDUSER Condition user ID Char 2

CPUID CPU ID Char 8 CPUID

ET End time Num 4 ET

MRC IBM $MRC value Num 3 Can be “*” MRC

OP Whether the conditionis ANDed or ORedwith the nextcondition

Char 3 AND or OR OP

PN Partition ID Char 2 PN

PRIMARY Condition value Char 16 PRIMARY

QNAME Qualifier value Char 8 QNAME

QUAL Qualifier type:

$ POWER jobnameE event nameG event groupJ VSE jobname

Char 1 $, J, E, G, or blank Q

RC IBM $RC value Num 4 Can be “*” RCContinued


7–8 BIM-FAQS/PCS

Continued


ST Start time Num 4 ST

STATUS Condition status Char 1 Y or N S

TYPE Condition type Char 8 Values:USER, PROC, PROD,AUX, JOB, DATA,PHASE, MSG, $JOB,$USER, EVENT,VAR, GROUP

TYPE

USER BIM-FAQS/PCSuser ID

Char 8 USERID



DSN Fields

The following fields describe dataset requirements. Multiple dataset items can bedefined per event. Because these fields can occur more than once, you cannot usethem with the SORT statement.

The keyword_type is DSN. The following is an example of the DSN format:PRINT DSN NAME


CONDPN Condition partition Char 2

CONDCPU Condition CPU ID Char 2

CONDTIME Condition time Char 2

CPUID CPU ID where OPENor CLOSE trigger isdetected

Char 8 CPUID

ET End time Num 4 ET

MODE Mode of detection forthe dataset trigger:

I specifies inputU specifies updateA specifies either

input or tape

Char 1 I, U, or A M

NAME Name of the dataset Char 44 DATASET

OP Whether the currentdataset dependency isANDed or ORed withthe next

Char 3 AND or OR OP

PN Partition where thetrigger is detected

Char 2 PN

QNAME Qualifier value Char 8 QNAMEContinued


7–10 BIM-FAQS/PCS

Continued


QUAL Condition type thatfurther qualifies anOPEN or CLOSEdataset:

J specifies job$ specifies POWER

jobP specifies phaseE specifies event

Char 1 J, $, P, or E Q

ST Start time Num 4 ST

STATUS Status of the condition Char 1 X or blank S

TRIG Type of dataset triggercondition:

X specifies dataset O specifies OPEN

requestC specifies CLOSE

request

Char 1 X, O, or C T



Resource Fields

The following fields describe resource requirements. Multiple resource items canbe defined per event. Because these fields can occur more than once, you cannotuse them with the SORT statement.

The keyword_type is RES. The following is an example of the RES format:PRINT RES NAME


NAME Resource name Char 44 RESOURCE

RATE Amount of resourcerequired

Num 3 UTIL

TYPE Type of resource:

L specifies localG specifies globalE specifies

CA-EXPLOREfor VSE

Char 1 E, L, or G T

UTIL Amount of resourcerequired

Num 3 UTIL

OP Whether the currentresourcedependency isANDed or ORedwith the next

Char 3 AND or OR OP


7–12 BIM-FAQS/PCS

Successor Fields

The following fields describe events that are defined as successors to an event.Multiple successor events can be defined per event. Because these fields canoccur more than once, you cannot use them with the SORT statement.

The keyword_type is SUCC. The following is an example of the SUCC format:PRINT SUCC EVENT


ABND Whether thesuccessor commandis based upon thecancel code of theevent

Char 1 Y, N, or "*" A

CONDMRC Conditionaloperand thatcompares the MRCvalues

Char 2

EVENT Name of postedevent

Char 8 EVENT

MRC Maximum returncode

Num 4 Can be "*" MRC



Successor Command Fields

The following fields describe commands that are defined as successors to anevent. Multiple successor commands can be defined per event. Because thesefields can occur more than once, you cannot use them with the SORT statement.

The keyword_type is SUCCMD. The following is an example of the SUCCMDformat:PRINT SUCCMD COMMAND


ABND Whether thesuccessor commandis based upon thecancel code of theevent

Char 1 Y, N, or "*" A

COMMAND Event command toexecute

Char 45 COMMAND

CONDMRC Conditionaloperand thatcompares the MRCvalues

Char 2

MRC Maximum returncode

Num 4 Can be "*" MRC


7–14 BIM-FAQS/PCS

Global Variable Fields

The following fields describe the global variable conditions defined to an event.Multiple global variable conditions can be defined per event. Because thesefields can occur more than once, you cannot use them with the SORT statement.

The keyword_type is VAR. The following is an example of the VAR format:PRINT VAR NAME


CONDVALU Condition forvariablecomparison

Char 2

NAME Variable name Char 16 VARIABLE

OP Whether thevariable conditionis ANDed or ORedwith the next

Char 3 AND or OR OP

STATUS Whether thecondition hasoccurred

Char 1 X or blank S

VALUE Condition value Char 80 VALUE



Data Station Fields

The following fields describe the data station definitions for events. Multipledata station items can be defined per event. Because these fields can occur morethan once, you cannot use them with the SORT statement.

The keyword_type is DATA. The following is an example of the DATA format:PRINT DATA VARNAME


DATATYPE Whether thevariable is numericor character data

Char 4 CHAR or NUM TYPE

GLOBALV Whether thevariable is global(Y) or local (N)

Char 1 Y or N G

HELP User Helpinstructions

Char 80 HELP

IMODNAME Verification IMODname

Char 8 IMODNAME

REQVAR Whether the usermust supply avariable value toupdate thecondition

Char 1 Y or N R

STRIP Whether leadingand trailing blanksare removed frominput value

Char 1 Y or N S

TEXT User instructions Char 80 TEXT

VARNAME Variable name thatreceives input

Char 8 VARIABLE


7–16 BIM-FAQS/PCS

Work Station Fields

The following fields describe the work station definitions for events. Multiplework station items can be defined per event. Because these fields can occur morethan once, you cannot use them with the SORT statement.

The keyword_type is WORK. The following is an example of the WORK format:PRINT WORK TEXT


STATUS Whether thecondition hasoccurred

Char 1 X or blank S

TEXT Work stationcondition text

Char 80 TEXT

Event Note Field

There is only one keyword for NOTE definition. Each item represents a line oftext. Multiple note lines can be defined per event. Because these fields can occurmore than once, you cannot use them with the SORT statement.

The keyword_type is NOTE. The following is an example of the NOTE format:PRINT NOTE TEXT


TEXT Event note text Char 80 Master or currentfile

TEXT



Successor Dependency Fields

The following fields are valid only when reporting on the current event file. Thedata describes the status of events which have this event listed as a successorevent. More than one event can be listed per event. Because these fields canoccur more than once, you cannot use them with the SORT statement.

The keyword_type is SDEP. The following is an example of the SDEP format:PRINT SDEP EVENT


DAY Day the event mustcomplete before thesuccessor can bescheduled

Char 3 DAY

EVENT Event that has thespecified event as asuccessor

Char 8 EVENT

STATUS Whether the eventhas been satisfied

Char 1 Y or blank S

Accounting History Fields

The accounting data used in the PCSEVRP report comes from the accountlogging data. The most recent data available in the account log is used forreporting purposes. This data is unique, and can be specified using the SORTstatement.

The keyword_type is ACCT. The following is an example of the ACCT format:PRINT ACCT LASTDUR


LASTDUR Duration of thejobstep

Char 8 hh:mm:ss LAST DUR

LASTPN Partition where thejob ran

Char 2 PN

LASTSTRT Start time of theevent

Char 8 hh:mm:ss LASTSTRT


7–18 BIM-FAQS/PCS

Event Summary History Fields

The event summary data used in the PCSEVRP report comes from the eventsummary history data. This data is unique, and can be specified using the SORTstatement.

The keyword_type is EVTSUM. The following is an example of the EVTSUMformat:PRINT EVTSUM AVGCPUS


AVGCPUS Average CPUseconds requiredfor the event to run

Num 6 sssshh (secondsand hundredthsof a second)

CPUS

AVGDUR Average duration ofthe event

Char 8 hh:mm:ss AVG DUR

AVGSIOS Average start I/Osrequired for theevent to run

Num 9 AVG SIOS

AVGSTRT Average start timeof the event

Char 8 hh:mm:ss AVG STRT

Control Statements


Control Statements

ACTION

Introduction

The ACTION statement supplies options and control information. You canspecify multiple ACTION statements. If you specify conflicting options, thesystem will use the last statement specified.

FormatACTION option[,option...]

Parameters

Parameter Function

HDR

NOHDR

Prints column headings (default)

Suppresses column headings

LIST

NOLIST

Echoes control cards to printer

Suppresses echo control cards to printer (default)

PAGE

NOPAGE

Breaks pages between events

Suppresses page breaks between events (default)

STATS

NOSTATS

Prints end of report statistics (default)

Suppresses end of report statistics

Example

The following statement suppresses column headings in the report and causes apage break between the data for each event:ACTION NOHDR,PAGE

Control Statements

7–20 BIM-FAQS/PCS

END

Introduction

The END statement specifies the end of a report definition. It is only neededwhen a job contains multiple report definitions. If a job contains only one reportdefinition, you can mark its end using /*.

FormatEND

Example

In the following example, the END statements delimit two report definitions:

// EXEC PCSEVRP,SIZE=PCSEVRP

ACTION LISTFILE MASTERTITLE1 'B I MOYLE ASSOCIATES, INC'TITLE2 'EVENTS THAT BEGIN WITH THE LETTER "A"'TITLE3 'SORTED BY EARLY TIME'

SELECT (EVENT(1) EQ A)PRINT EVENT GROUP DESC EARLY LATE ABORTSORT EARLY EVENT

END

ACTION LISTFILE CURRENTTITLE1 'DIRECTORY OF EVENTS IN CURRENT FILE'INCLUDE $LISTDIREND

Control Statements


FILE

Introduction

The FILE statement indicates whether you want the data for the report drawnfrom the master or current event directory.

If you specify the FILE statement more than once, the system uses the laststatement specified.

FormatFILE [MASTER|CURRENT]

Parameters

Parameter Function

MASTER Reads information from the master event directory (default)

CURRENT Reads information from the current event directory

ExampleFILE CURRENT

Control Statements

7–22 BIM-FAQS/PCS

FORECAST

Introduction

The FORECAST statement specifies a date for forecast scheduling. The statementis valid for the master event directory only.

Note: This statement causes an implicit FILE MASTER statement to be executed.

FormatFORECAST yy/mm/dd

Parameter

yy/mm/dd can be any date, future or past.

Examples

The following example prints a forecasting report for December 15, 1997:// EXEC PCSEVRP,SIZE=PCSEVRP

ACTION LISTTITLE1 'B I MOYLE ASSOCIATES, INC'TITLE2 'FORECAST REPORT FOR 97/12/15'

FORECAST 97/12/15INCLUDE $LISTDIR

END

Control Statements


INCLUDE

Introduction

The INCLUDE statement selects predefined report definitions.

FormatINCLUDE member

Parameter

For member, specify the SYS$MON PDS member containing the report definition.You can nest INCLUDE statements up to eight levels.

PCS Predefined Reports

The following predefined reports are included with BIM-FAQS/PCS:

• $LISTDIR - Prints all events in a specific event file

• $LISTALL - Prints all fields of an event

Predefined reports included with BIM-FAQS/PCS have a member type of EVR.

Note: The definitions of predefined reports may be updated in each release. Ifyou are using a predefined report and would like to preserve its currentdefinition, make a copy of it and give it a different name (e.g., "LISTDIR.EVR").

Example

The following INCLUDE statement incorporates the predefined report $LISTALL:INCLUDE $LISTALL

Control Statements

7–24 BIM-FAQS/PCS

PRINT

Introduction

The PRINT statement controls the format of printed report lines. You mustspecify at least one PRINT statement.

FormatPRINT [field] [+nn] ['const'] ...[-]

Parameters

You can specify the field, +nn, and 'const' parameters in any order and multipletimes. Their order will determine how their items are printed.

Parameter Function

field Specifies any of the event definition fields documented earlier inthis chapter.

+nn Controls horizontal spacing between fields. Specify a valuebetween 0 and 132. Default is 1.

'const' Prints a constant string in the report. Must be enclosed withinapostrophes.

- If you need to continue a print definition across JCL lines,specify a hyphen as a continuation character. The hyphen mustbe the last non-blank character specified and preceded with ablank.

Print File Characteristics

The report width is 132 characters. Headings are supplied for all fields. If youspecify a partial item name by specifying a length, offset, or both, only part of thefield name appears in the print area.

Examples

The following PRINT statement prints a blank line:PRINT ' '

The following PRINT statements define a report line containing three fields:EVENT, DESC, and the DSN extended field NAME.PRINT EVENT DESC DSN NAME

Control Statements


The following PRINT statements define two lines of a report:

PRINT EVENT DESC EARLY(2) +0 ':' +0 EARLY+2 LATE(2) +0 ':' +0 LATE(2) - ABORT(2) +0 ':' +0 ABORT+2 STATUS COMMAND

PRINT +5 'WHEN' WHEN PRIMARY WHEN TYPE

SELECT

Introduction

The SELECT statement is used to select events that will be printed on the reportbased upon event definition criteria. If you don't specify a SELECT statement ina definition, all events in the current or master event directory will be used togenerate the report.

Format

There are two formats for the SELECT statement:

• Format 1 is used to specify fields that are unrelated

• Format 2 is used to specify fields that are related to one another in multi-occurring statements

These formats can be used together.

Note: When grouping extended fields, specify only those of the same type in aparenthetical expression.

Format 1

Use the following format of the SELECT statement to specify fields that areunrelated:SELECT ( field ro data) [AND|OR] ...

Examples: The following statement selects all events with a status of eitherABND or EXP for printing:SELECT (STATUS EQ ABND) OR (STATUS EQ EXP)

The following statement selects all events that have a WHEN condition definedwith a type of EVENT and a primary data field of ABC. Any primary conditionthat contains ABC will be selected; an event does not need to be defined withstatement WHEN EVENT=ABC. Multiple WHEN conditions can satisfy thisselection criteria.SELECT (WHEN TYPE EQ EVENT) AND (WHEN PRIMARY EQ ABC)

Control Statements

7–26 BIM-FAQS/PCS

Format 2

Use the following format of the SELECT statement to specify fields that arerelated to one another in multi-occurring statements. The parentheses imply the"same event condition."SELECT ((ext field ro data) AND (ext field ro data)) [AND|OR] ...

Example: The following example selects all events that have a WHEN conditiondefined with statement WHEN EVENT=ABC:SELECT ((WHEN TYPE EQ EVENT) AND (WHEN PRIMARY EQ ABC))

Parameters

Parameter Function

field Any of the event definition fields documented earlier in thischapter.

ro One of these relational operators: EQ, LE, GE, LT, GT, NE, =,<=, >=, < ,> , ¬=.

data A value to be compared against. Data with embedded blanksmust be enclosed within apostrophes.

ext An extended field belonging to a particular keyword category,such as WHEN, DSN, or RES.

Multiple SELECT Statements

Use AND and OR to specify multiple SELECT statements--that is, severalSELECT statements that are dependent on one another.

If more than one SELECT statement is used, AND is assumed at the end of eachSELECT statement unless you specify OR. Therefore, if several SELECTstatements are supplied, all conditions must be met for a record to be included.

When a line ends with OR, and any condition on that line is matched, the currentrecord is selected even if subsequent lines have tests that fail.

Control Statements


Examples

In the following examples, consider two event definitions:

Event EVENTA has two WHEN conditions:

WHEN EVENT=WHSEINV

WHEN JOB=PAYROLL

Event EVENTB has one WHEN condition:

WHEN EVENT=PAYROLL

The following SELECT statement selects both EVENTA and EVENTB, becauseboth events are defined with WHEN conditions that have type EVENT andprimary field PAYROLL:SELECT (WHEN TYPE EQ EVENT) AND (WHEN PRIMARY EQ PAYROLL)

In the next example, both conditions are checked against the same WHENcondition. Only EVENTB is selected for printing, because it is the only event thathas both WHEN type EVENT and primary field PAYROLL.SELECT ((WHEN TYPE EQ EVENT) AND (WHEN PRIMARY EQ PAYROLL))

Control Statements

7–28 BIM-FAQS/PCS

SORT

Introduction

The SORT statement alters the sequence in which events are printed. If you omitthis statement, the events are printed in alphanumeric order based on the EVENTfield.

Sorting is done in ascending order, either alphabetically or numerically,depending on the data type of the field.

Specify multiple SORT statements to concatenate the sort key.

FormatSORT [field]...

Parameter

Parameter Function

field Any of the event definition fields documented earlier in thischapter, except those that occur multiple times. The fieldlisted first is the primary key, the field listed second is thesecondary, and so on. The total length of the SORT keycannot exceed 256 characters.

Examples

The following SORT statement causes the items in the report to be sorted basedon the EVENT field, and within each event name by the GROUP field:SORT EVENT GROUP

Parts of fields can be used as sort keys. For example:SORT CAL EARLY(2) LATE+2

Control Statements


TITLE

Introduction

The TITLE statement defines the report title. The title is centered below theutility heading. If you omit this statement, the report will not have a title.

FormatTITLEn 'text'

Parameters

Parameter Function

n The title line number. Must be in the range of 1-3.

text Up to 40 characters. Encloses the title in apostrophes.

Example

The following TITLE statements define a 3-line title:TITLE1 'XYZ Report'TITLE2 'Current Event File'TITLE3 'ABC Company'

Control Statements

7–30 BIM-FAQS/PCS

* (Comment)

Introduction

The * statement lets you document report definitions or cause control statementsto be ignored.

Format* [text]

The comment character (*) must be the first character on the line.

Parameter

Parameter Function

text Up to 72 characters

Example

Comment statements are used in the following example to document somecontrol statements in a report definition and to cause these control statements tobe ignored:* Use these only at year end* PRINT DESC DSN NAME DSN CPUID* SORT GROUP


Chapter 8Monitoring Schedule History

This chapter covers BIM-FAQS/PCS monitoring, especially the batch monitoringtools BIM$ACUT, BIM$DSUT, and BIM$ADUT.


Once your schedule is established and operating, you will probably want todetermine how effectively it's running. If jobs or events are not being executed,you can use BIM$ACUT, BIM$ADUT, and BIM$DSUT to find out why.

BIM-FAQS/PCS provides both batch and online tools for monitoring yourschedules. This chapter focuses on three of the batch tools, BIM$ACUT,BIM$DSUT, and BIM$ADUT.

Overview of Monitoring Tools

Tool Type Enables you to

BIM$ACUT Batch Produce archived job accounting history file. Jobaccounting lets you determine when a job ran and theresources it used. Use BIM$ACUT to set up accountingreports, which are useful as diagnostic tools, forexample, to determine why a successor event was nottriggered.

Along with the history file merge utility, BIM$ACUTcreates a history archive file, updates the previouslyarchived history file, and resets the account log file.

BIM$ADUT Batch Produce PDS member auditing reports and historyarchive file. Job auditing can help you to review allmaintenance performed on JCL members and events.For example, you can run reports showing events thatwere posted.

Along with the history file merge utility, BIM$ADUTcreates a history archive file, updates the previouslyarchived history file, and resets the audit log file.

Continued

Overview

8–2 BIM-FAQS/PCS

Continued

Tool Type Enables you to

BIM$DSUT Batch Produce archived dataset history file. Datasetmonitoring is useful for determining when a datasetrequest was issued. You can use the BIM$DSUT batchutility to set up dataset logging reports.

Along with the history file merge utility, BIM$DSUTcreates a history archive file, updates the previouslyarchived history file, and resets the dataset log file.

AccountHistory

Online View job accounting history online (in detail andsummary formats). Cancel codes (CC), return codes($RC), and maximum return codes ($MRC) for eventsare also reported as part of online job accounting.

Both detailed and summarized account history reportsare available online. The detailed reports show you jobaccounting information by event name, proc name, VSEjobname, and several other options. The summarizedreport lists information like average duration of anevent, average CPU seconds, and more.

AuditHistoryscreens

Online View maintenance history on PDS members or events.For example, you can view all events executed on April1, 1998. Or you can view all activity on all members in aspecific PDS library.

DatasetLoggingscreens

Online View dataset history online.

EventForecastingscreens

Online View event forecasts online. Use the Event ForecastReport to view all events scheduled for a specific date orcalendar. This is helpful if you are setting up successoror predecessor events. You can also use the EventForecasting Screen to view event statuses.

ProcessingPeriodscreens

Online View different processing period schedules. Verifysystem- or user-defined processing periods. If you'vedefined cycle or holiday schedules, you can use thisscreen to see when those processing days occur and howthey might affect your event processing.

Using the Batch Monitoring Utilities


Using the Batch Monitoring Utilities

Setting Up Schedule Monitoring

Initiating Job Accounting and Dataset Monitoring

To collect accounting data for jobs submitted via BIM-FAQS/PCS, and to collectdataset history information, specify the following with the JCLXCU utility atstartup:ENABLE LOAD=Y|N,LOG=Y|N,JOBX=$JOBEX0n,DSN=Y|N,DSNLOG=Y|N

ESA 1.2 and Above: The JOBX= parameter of the ENABLE statement is validonly when running ESA 1.2 or above.

Job Accounting Components

The following components are required for job accounting:

• The JCLACCT exit, which captures data for the account log file. JCLACCT isinvoked whenever a proc or event causes a VSE job to execute, provided youspecify LOG=Y at startup.

• The BIM$ACUT report writer and history file merge utility, which create ahistory archive file, update the previously archived history file, and reset theaccount log file.

• The account log file, LACACCNT.CTL, which is the current data capture file.

The following component is optional:

• The history archive file, which is the tape or disk copy of a previous versionof the account log file.

Dataset Monitoring Components

The following components are required for dataset monitoring:

• The $$BOPEN and $$BCLOSE hooks, which are responsible for datasetdetection. These hooks are enabled when you specify DSN=Y at startup.

• If logging is enabled, the SYS$LOG PDS, which creates the dataset log file,PCSDSNOC.CTL. This is the current data capture file.

• The PCSSRV program, which monitors all dataset activity and performsdataset logging. PCSSRV must be active on all CPUs where dataset detectionwill be used.

Using BIM$ACUT

8–4 BIM-FAQS/PCS

Using BIM$ACUT

Overview of Control Statements

Running BIM$ACUT Under CMS

To run BIM$ACUT under CMS, use the PCSCMS EXEC. For more informationabout PCSCMS, see the BIM-FAQS/PCS Operations Guide.

Control StatementsYou can specify control statements in any order, except for DEFINE. If you referto any user items or new print headings, you must define them first.

Statement Function


SELECT Selects records to be processed

SORT Determines sequence of output

PRINT Determines report contents

OUTPUT Determines output file contents

MERGE Updates a history archive file

EVTSUM Establishes event summary options

DEFINE Changes item names or report headings

Item Names and Report Headings

Item names identify the types of information to appear on a report. TheBIM$ACUT control statements are dependent upon item names. Item names aretranslated into report headings. Both item names and report headings can beredefined using the DEFINE control statement.

Using BIM$ACUT


Item Names

ItemName

DefaultHeading

Description Length (chars)

EVENT EVENT PCS event name that caused a VSE job toexecute.

8

DJNM VSE JOB VSE jobname. 8

PHASE PHASE Phase that executed during a particularjobstep.

8

PN PN VSE partition where the BIM-FAQS/PCSactivity occurred.

2

CC CC IBM cancel code for the job. 2

$RC $RC IBM return code of the jobstep. 4

PROC PROC PCS proc that caused a VSE job to execute. 8

PJNM PWR JOB POWER jobname. 8

DAY DAY Day of the week when a particular job orstep ended.

3

$MRC $MRC IBM maximum return code of the job. 4

USER USER ID PCS user who either submitted the PCSproc or caused the event to be scheduled.

8

STAMP -- Timestamp in day mm/dd/yy hh.mm.ssformat. Depending on the type of record,STAMP reflects end-of-step or end-of-jobinformation.

27

DATE DATE Date in yy/mm/dd format, for sortingpurposes. Depending on the type ofrecord, STAMP reflects end-of-step or end-of-job information.

8

TIME TIME Time in hh.mm.ss format. Depending onthe type of record, STAMP reflects end-of-step or end-of-job information.

8

PUSR PWR USR POWER user information. 16Continued

Using BIM$ACUT

8–6 BIM-FAQS/PCS

Continued

ItemName

DefaultHeading

Description Length (chars)

CPUID CPU ID CPU ID serial number on which the JOBexecuted.

8

CPUTT FINLCPU Total CPU time in mmmm.SSS format usedby the particular PCS proc or event. If procor event contained multiple VSE jobs, itscumulative duration is shown.

7

DURT FINLDUR Total duration in hh:mm:ss format of PCSproc or event. If proc or event containedmultiple VSE jobs, its cumulative durationis shown.

8

SIOT FINLSIO Total S I/Os issued on behalf of aparticular proc or event. If proc or eventcontained multiple VSE jobs, itscumulative S I/Os are shown.

7

START START Start time of the jobstep in hh.mm.ss format. 8

STARTT STARTT Start time of the entire job in hh.mm.ssformat--that is, when the first step of acompleted job started.

8

CPUTS STEPCPU Total CPU time in mmmm.SSS format usedby a particular jobstep.

7

DURS STEPDUR Step duration in hh:mm:ss format of aparticular jobstep.

8

SIOS STEPSIO Total S I/Os issued for a particular jobstep. 7

T T Jobstep type. S indicates a multiple-stepjob, and L indicates the last step of a VSEjob.

1

Using BIM$ACUT


Sample Items Names

You can specify full or partial item names with the control keywords. Ifspecifying a partial name, list the offset or length. Indicate an offset with a plussign (+). Offset values count the first character as 0. Enclose lengths withparentheses ( ).

The following table shows examples of full and partial item names using anoffset or length, or both:

Example Explanation Sample VSEJobname

DJNM The whole, 8-character, VSE jobnameis used.

PDSANAL1

DJNM(3) The first three characters of the VSEjobname are used.

PDS

DJNM+4 The last four characters of the VSEjobname are used.

NAL1

DJNM+3(3) The fourth, fifth, and sixth charactersof the VSE jobname are used.

ANA

Using BIM$ACUT

8–8 BIM-FAQS/PCS

ACTION

Introduction

The ACTION control statement supplies options and control information toBIM$ACUT.

FormatACTion parameter[,parameter]

ACTION can be abbreviated as ACT.

Parameter Values

Value Function

LOG|NOLOG LOG logs critical information on the system console,including all errors. Ordinary report output is neverdisplayed on the console.

NOLOG prevents critical information from logging onthe system console, except for severe error messages.NOLOG is the default.

TEST Suppresses alteration of files by BIM$ACUT. Forexample, TEST bypasses any reset of the account file orany output to an archive file. When TEST is used, nooutput files are opened.

LIST|NOLIST LIST displays control statements on SYSLST. ACTIONLIST is forced if ACTION TEST is specified.

NOLIST suppresses display of control statements onSYSLST. NOLIST is the default.

SORTWK=n Specifies the number of sort work files. n defaults to 1.If SORTWK=2 is entered, a DLBL for SORTWK2 mustalso be present. SORTWK=n is not supported undernative CMS execution of BIM$ACUT.

CANCEL Issues a CANCEL macro when errors are detected. Bydefault, errors suppress the processing of a singlestatement or request; however, execution proceeds, anda report is produced using defaults.

CANCEL,DUMP Produces a dump on any error condition that results inabnormal termination.

Continued

Using BIM$ACUT


Continued

Value Function

DUMP=DEBUG Forces a DUMP at end-of-job.

HDR='heading' Specifies the print heading for the output report. headingcan be a maximum of 60 characters delimited by singlequotation marks.

SORTX Specifies that files are sorted externally. Most often usedwith the EVTSUM control statements, since processingsummary information can require a lot of GETVIS.

DEBUG=nnnnnnnn Enables debugging options. Use this option at therequest of BIM Technical Support only.

Using BIM$ACUT

8–10 BIM-FAQS/PCS

SELECT

Introduction

The SELECT control statement specifies which records should be extracted fromthe input file. You must supply at least one SELECT statement to run a report.

FormatSELect itemname ro value

SELECT can be abbreviated as SEL.

Parameters

Parameter Function

itemname Item name (field in an account record for comparison todetermine whether the record is rejected or included in a run).

ro One of the following relational operands: EQ, NE, GT, LT, GE,LE.

value Value or range of values the named item must have to beincluded in the run.

Logical Operators

Operator Used WhenConditions MustBe

Example

AND Combined--thatis, when severalconditions mustbe met before arecord is included

SELECT USER EQ TECHSUP AND DAY EQ SUN

This example selects all records with the PCS user ID TECHSUP runon Sunday. All other records are rejected, including records withthe correct user ID run on other days, and records run on Sundaybut with other user IDs.

OR Separate--that is,when any one ofseveral conditionsbeing met resultsin a record beingselected

SELECT USER EQ TECHSUP OR USER EQ SETUP

This example selects all records with either user ID TECHSUP orSETUP, and rejects all other records.

Using BIM$ACUT



Use AND and OR to specify multiple SELECTs--that is, to specify that severalSELECT statements are dependent on one another.

If more than one SELECT statement is used, AND is assumed at the end of eachstatement unless you specify OR. Therefore, if several SELECT statements aresupplied, all conditions must be met for a record to be included.


Multiple SELECT Statement Examples

Where AND is Assumed: The following SELECT statements show the precedenceof the AND and OR conditions:SELECT DJNM EQ PAYROLLSELECT CC NE 10SELECT USER EQ TECHSUP OR USER EQ SYSTEMS OR USER EQ MIKE

These SELECT statements must work in combination in the following ways:

The first statement selects only those records that had the VSE job PAYROLLexecute. Any records failing this test are rejected. Records that pass this testproceed to the next test.

• Only records with a cancel code other than 10 are kept; records that fail thistest are rejected because neither line includes an OR as the last word.

• The last statement rejects any records whose user ID is not TECHSUP,SYSTEMS, or PAYROLL. Therefore, the selected records are those with oneof these three user IDs that caused the VSE job PAYROLL to execute and thatfinished with an IBM cancel code other than 10.

Where OR is Specified Between Statements: The following SELECT statementsshow the precedence of the AND and OR conditions:SELECT DJNM EQ PAYROLLSELECT CC NE 10 ORSELECT USER EQ TECHSUP OR USER EQ SYSTEMS OR USER EQ MIKE


• The first statement selects only those records that had the VSE job PAYROLLexecute. Any records failing this test are rejected. Records that pass this testproceed to the next test.

• Only records that had a cancel code other than 10 or that had the user IDTECHSUP, SYSTEMS, or PAYROLL are kept.

• Therefore, the selected records are those that had VSE job PAYROLL executewith a cancel code other than 10, or are those that had one of these three userIDs who caused VSE job PAYROLL to execute.

Using BIM$ACUT

8–12 BIM-FAQS/PCS

SORT

Introduction

The SORT control statement specifies the order of the items selected from theinput file. Items from the current account log file or an archived tape or diskhistory file are in chronological order. By default, output is in chronologicalorder.

The SORT statement is optional. When a SORT statement is used, achronological sort is performed automatically. Since records are sorted evenwhen no SORT statement is supplied, records can be combined from multipleprocessors.

FormatSORT item1 item2 item3 ...

The order of the item parameters indicates how the items are sorted. Total lengthof the items listed cannot exceed 32 characters (bytes).

Internal and External Sorts

Sorts can be performed internally (in memory) or externally (on disk). Toimprove performance, use an external sort when sorting more than a fewhundred records. External sorts are not supported when BIM$ACUT is executedunder native CMS.

Internal Sort: If you enter SORT, the sort is done in memory and runs until it'scompleted or no more memory is available. The report is processed based onwhat could be sorted with limited memory. If all records are sorted (sufficientmemory), the report is complete. Otherwise, the report is incomplete.

External Sort: Enter SORTX if you don't have sufficient memory to process asort in memory. Use an external sort if you're sorting more than a few hundredrecords. When an external sort is performed, you must define a DLBL for aSORTWK1 area. The sort work area is always a sequential disk file, so the DLBLmust be type SD. To increase the number of sort work areas, use the ACTIONSORTWK=n parameter.

The external sort program is loaded into the area between the end of BIM$ACUTand the GETVIS area. If less than 80K is available, the sort cannot be loaded, andBIM$ACUT attempts to process all records in storage. Therefore, you shouldspecify the parameter SIZE=(BIM$ACUT,80K) to allow room for the SORTprogram to be loaded.

Using BIM$ACUT


Examples

Example Explanation

SORT PJNM DJNM The POWER jobname (PJNM) is the primary sortfield and the VSE jobname (DJNM) is thesecondary sort field. The length of the resultingsort key is 16 characters. The sort is performed inmemory.

SORTX PUSR+4(4) PN CC Positions 4-7 of the POWER user field are theprimary sort field, with partition (PN) as thesecondary sort field. The IBM cancel code is thetertiary sort field. The length of the resulting sortkey is 8 characters. The sort is performedexternally by calling the system SORT utility.(SORTWK1 must be defined).

Using BIM$ACUT

8–14 BIM-FAQS/PCS

PRINT

Introduction

The PRINT control statement specifies the items to include in a report.

The PRINT statement is optional. If a PRINT statement is not supplied and noother output is defined, the default report format is used. If no PRINT statementis supplied and an OUTPUT statement is present, a printed report is notproduced. Note that a print file is separate from an output file and that differentinformation can be formatted into each file in a single pass of the input.

FormatPRINT item1 item2 item3 ...

The order of the item parameters indicates how the items are printed.


The report width is 132 characters. The system has default headings for allinternal items. If you specify a partial item name by specifying a length, offset, orboth, only part of the default item name appears in the print area.

Default Print Report Item Names

The default print report contains the following item names:

Item Name Description

PN Partition

PJNM POWER jobname

DJNM VSE jobname

PROC PCS proc name

EVENT PCS event name

PHASE Phase name

CC IBM cancel code

$RC IBM return code

SIOS Start I/Os for the jobstep

CPUTS Total CPU time

DURS Step duration

STAMP TimestampContinued

Using BIM$ACUT


Continued


T Jobstep type

USER PCS user

Report Selection Summary

When a PRINT is performed and ACTION LIST is specified, a Report SelectionSummary is printed.

JCL Example: The following JCL shows how to get a Report Selection Summary:// EXEC BIM$ACUT,SIZE=BIM$ACUTACTION LISTMERGE IN=NONE,OUT=NONE,LOG=YESSELECT TYPE EQ L AND EVENT NE ' 'PRINT EVENT/*

Report Example: The Report Selection Summary contains totals of jobs andrecords read and written. Both the number of maintenance executions and thenumber of operations performed are reported. The ACTION LIST commandmust have been specified. The following is an example of the Report SelectionSummary:

Line No. ** Report Selection Summary **

1

2

3

4

5

569 = RECORDS READ (ONLINE LOG + HIST)

237 = RECORDS SELECTED

332 = RECORDS REJECTED

0 = OLD HISTORY JOBS READ

569 = ONLINE LOG JOBS READ

The lines of the Report Selection Summary contain the following information:

• The number of records read from any history archive file and the accountinglog file.

• The number of records processed as a result of the user selection criteria.

• The number of records not processed as a result of the user selection criteria.

• The number of records read from the input file. This number is zero ifIN=NONE.

• The number of new records read from the account log file. Records in theaccount log file found in the history archive file are not included in this total.Since record selection occurs at the transaction level, this number reflects alljobs seen, including jobs in which some or all of the transactions wererejected.

Using BIM$ACUT

8–16 BIM-FAQS/PCS

OUTPUT

Introduction

The OUTPUT control statement specifies which items should be formatted intothe output file. An output file is different from a print file, and differentinformation can be formatted into each file in a single pass of the input. Anoutput file is useful if you want to produce reports other than those provided byBIM$ACUT.

The OUTPUT statement is optional. If an output statement is not supplied, nooutput file is produced.

The OUTPUT control statement is not supported under native CMS execution ofBIM$ACUT.

FormatOUTput item1 item2 item3 ...

The order of the item parameters indicates how the items are output. OUTPUTcan be abbreviated as OUT.

Output File Characteristics

An output file has the following characteristics:

• Can be either a tape or disk file.

• Is always in variable blocked format.

• Has maximum block size of 6008 bytes.

• GSAUDO is the DTF name.

• DTFMT is used if a TLBL card is supplied.

• DTFSD is used if a DLBL card is supplied.

If an OUTPUT statement is supplied but no DLBL or TLBL for GSAUDO can befound, no output is produced. The opposite condition produces the same result:If no OUTPUT statement is supplied and a DLBL or TLBL for GSAUDO ispresent, no output is produced.

Using BIM$ACUT


MERGE

Introduction

The MERGE control statement identifies input for report and controls archiving.Only new records are output. A previously created archive history file can alsobe used as input. In this case, the output history file contains all records from theinput history archive file, plus any records from the account log file not alreadypresent on the history archive file.

The MERGE statement is optional. If a MERGE statement is not supplied, thearchive history file is not updated and the account log file is not reset. If a reportis requested and no MERGE statement is supplied, then the report containsinformation from only the account log file. If a MERGE statement is present, noother statements are required.

MERGE is not available under native CMS execution of BIM$ACUT.

MERGE with Other BIM$ACUT Control Keywords

Any records in the history archive file are also available for user reporting. Thatis, if a run contains a MERGE statement and report generation statements such asSELECT or PRINT, then the resulting report contains information from both theinput history archive file and the account log file.

FormatMERGE [IN=xxxxxxxx],[OUT=xxxxxxxx],[RESET=xxxxxxx],[LOG=xxx]

Using BIM$ACUT

8–18 BIM-FAQS/PCS

IN Parameter Values

You can specify the following values for the IN=xxxxxxxx parameter:

Value Function

NONE Indicates that no archive input file is present. IN=NONE is thedefault.

filename Specifies the name for the input history archive file. The defaultlogical unit is SYS004.

DTFMT format is used for the filename if a TLBL card is supplied.DTFSD format is used for the filename if a DLBL card is supplied.

logunit Specifies the logical unit to be used for a tape file. The defaultfilename is AUDITHI.

If a value other than SYS004 is assigned to the logical unit, youmust assign that unit to the desired tape drive.

filename/logunit

Specifies both an input filename and its logical unit.

Do so by entering a filename and a desired logical unit, separatedby a slash. For example, IN=MYIN/SYS010 specifies a DTF nameof MYIN with logical unit SYS010.

AUDITHI If you are using a tape manager that supports dynamicassignment, you can specify IN=AUDITHI. When AUDITHI isspecified, BIM$ACUT defaults to SYS004. Override the defaultSYS number by specifying the logical unit following AUDITHI.For example, IN=AUDITHI/SYS016 overrides the default value.

Using BIM$ACUT


OUT Parameter Values

OUT= enables you to merge records from an existing archive file into a newarchive history file. You can specify the following values for the OUT=xxxxxxxxparameter:

Value Function

NONE Indicates that no output file is written and the account log file isnot reset. OUT=NONE is the default.

filename Specifies the name for the output history archive file. Thedefault logical unit is SYS005.

DTFMT format is used for the filename if a TLBL card issupplied. DTFSD format is used for the filename if a DLBLcard is supplied.

logunit Specifies the logical unit to be used for a tape file. The defaultfilename is AUDITHO.

If a value other than SYS005 is assigned to the logical unit, youmust assign that unit to the desired tape drive.

filename/logunit

Specifies both an output filename and its logical unit.

Do so by entering a filename and a desired logical unit,separated by a slash. For example, OUT=MYOUT/SYS012specifies a DTF name of MYOUT with logical unit SYS012.

AUDITHO If you are using a tape manager that supports dynamicassignment, you can specify OUT=AUDITHO. WhenAUDITHO is specified, BIM$ACUT defaults to SYS005.Override the default SYS number by specifying the logical unitfollowing AUDITHO. For example, OUT=AUDITHO/SYS017overrides the default value.

Using BIM$ACUT

8–20 BIM-FAQS/PCS

RESET Parameter Values

You can specify the following values for the RESET=xxxxxxxx parameter:

Value Function

NO Prevents the account log file from resetting. RESET=NO is thedefault.

YES Resets the account log file to empty, with the exception ofrecords created on the current day, after the history archive filehas been updated. RESET=YES is ignored if one of thefollowing conditions exists:

No MERGE output file is defined.

The MERGE output file is assigned to IGN andOUT=AUDITHO is specified.

ACTION TEST is specified.

WEEKLY Purges all but last week's records, after the history archive filehas been updated.

MONTHLY Purges all but last month's records, after the history archive filehas been updated.

LOG Parameter Values

You can specify the following values for the LOG=xxx parameter:

Value Function

YES Reads the account log file. LOG=YES is the default. If IN= isspecified, the history input file and the account log file are read, inthat order.

NO Prevents reading of the account log file. If IN= is specified, only thehistory archive file is read. If IN= is not specified, no output isproduced.

Using BIM$ACUT


MERGE Examples

Specifying Files and Purging

The following example specifies MYIN as the TLBL/DLBL name of the input file,MYOUT as the TLBL/DLBL name of the output tape file, and purges all but lastweek's records when the history archive file is updated:MERGE IN=MYIN,OUT=MYOUT,RESET=WEEKLY

Reporting From Account Log File Only

The following jobstream generates a report using the audit log file as input. Sinceno MERGE statement is supplied, only the account log file is read. Since noPRINT statement is supplied, the report produced is in the default format. Allactivity having to do with the VSE jobname PAYROLL that occurred on any date,on or after April 1, 1997, is selected. // JOB HISTORY REPORT // EXEC BIM$ACUT,SIZE=BIM$ACUT SEL DJNM EQ PAYROLL AND DATE GE 97/04/01 /* /&

The preceding example generated a default report since no PRINT statementswere supplied. The following is an example of this default report:

JOB DOCACCT 02/18/98 16.31.40 VSE6.1.2 BIM$ACUT BIM-FAQS/PCS V5.1A ACCOUNT REPORTING UTILITY

PN PWR JOB VSE JOB PROC EVENT PHASE CC $RC STEPSIO STEPCPU DURATION DAY DATE TIME T USERID

F3 JCLSCHED PAYROLL JCLSCHE SHED JCLSCHD 10 0000 0034560 023.45 12:13:42 MON 97/04/19 11:30:10 L ADMN

F2 CICSTST PAYROLL CICSMRO CICS DFHSIP 20 0000 0123455 032.12 23:12:12 MON 97/04/19 12:00:13 L ADMN

F4 MAINT PAYROLL MAINT MAINT LIBR 10 0008 0000345 001.10 00:01.10 MON 97/04/19 13:01:12 L ADMN

Using BIM$ACUT

8–22 BIM-FAQS/PCS

MERGE History Summary

Whenever a MERGE is performed, a MERGE History Summary is produced.This short report contains totals of maintenance jobs read and written. Thefollowing is an example of the MERGE History Summary:

Line No. ** MERGE HISTORY SUMMARY **

1

2

3

4

5

6

7

8

9


5,863 = ONLINE JOBS READ

5,863 = NEW HISTORY JOBS OUTPUT

114 = ONLINE LOG JOBS KEPT

5,750 = ONLINE LOG JOBS DELETED

35.9% = PERCENT COMPRESS SAVINGS

XMRIHLIM NEV 00/00/00 00.00.00

TOD0000 MON 04/15/91 00.00.00

TODRESET SUN 04/14/91 23.59.59

The lines of the MERGE History Summary contain the following information:

• The number of records read from the input history archive file. This numberis zero if INPUT=NONE is specified. These records are all copied to theoutput.

• The number of new records read from the account log file. Records on theaccount log file found on the input history archive file are not included inthis total.

• The total records written to the output history archive file. This is the total ofline 1 and line 2.

• The number of records remaining on the audit log file after the RESET optionis performed.

• The number of records deleted from the audit log file as a result ofperforming the RESET option.

• The percentage of savings by data compression.

• The date of last record that was written to tape.

• The time of day the first record was saved in LACACCNT.CTL.

• The time of day the last record was written to tape.

Lines 6 - 9 are written to the report when OUT=AUDITHO and RESET= anyvalue.

Using BIM$ACUT


Creating a History Archive File

The following jobstream creates a history archive file. All records output to thehistory archive file are purged from the audit log file. No detail report isproduced; only a history summary page is printed.// JOB CREATE HISTORY// DLBL AUDITHO,'BIM$ACUT.HIST'// ASSGN SYS005,351// EXEC BIM$ACUT,SIZE=BIM$ACUTMERGE IN=NONE,OUT=SYS005,RESET=YES/*/&

Updating a History Archive File

The following jobstream updates a history archive file. The input tape is apreviously created history archive file. The output tape contains all records onthe input tape plus all new data from the audit log file. All records output to thehistory archive file are purged from the audit log file. No detail report isproduced; only a history summary page is printed.// JOB UPDATE HISTORY// TLBL AUDITHI,'BIM$ACUT.HIST'// ASSGN SYS004,281// TLBL AUDITHO,'BIM$ACUT.HIST'// ASSGN SYS005,280// EXEC BIM$ACUT,SIZE=BIM$ACUTMERGE IN=SYS004,OUT=SYS005,RESET=YES/*/&

Reporting from History Archive File Only

The following jobstream reads an existing history archive file and generates areport using only that data. No output history archive file is produced. Norecords are purged from the account log file. No history summary page isprinted.// JOB HISTORY REPORT// TLBL AUDITHI,'BIM$ACUT.HIST'// ASSGN SYS004,280// EXEC BIM$ACUT,SIZE=BIM$ACUTMERGE IN=SYS004,LOG=NOSEL CC NE 00 AND CC NE 10/*/&

Using BIM$ACUT

8–24 BIM-FAQS/PCS

Reporting from History Archive File and Account Log File

The following jobstream reads an existing history archive file and the account logfile and generates a report. No output history archive file is produced. Norecords are purged from the account log file. No history summary page isprinted.// JOB HISTORY REPORT// TLBL AUDITHI,'BIM$ACUT.HIST'// ASSGN SYS004,280// EXEC BIM$ACUT,SIZE=BIM$ACUTMERGE IN=SYS004SEL $MRC GT 0000 AND PHASE EQ LIBR/*/&

Using BIM$ACUT


EVTSUM

Introduction

The EVTSUM control statement produces event summary information. Eventsummary information is displayed on the Event Summary Report and can helpyou to determine event trends.

For More Information: See the BIM-FAQS/PCS Operations Guide for moreinformation about the Event Summary Report.

FormatEVTSUM RANGE=(yymm,yymm) PURGE PRINT NOUPDATE

Parameters

All EVTSUM parameters are optional. If no parameters are supplied withEVTSUM, detail information is merged into the summary file, using theinformation currently in the account log file.

Parameter Function

RANGE=(yymm,yymm) Indicates the range of dates for which summarydata is reported. The first yymm is the beginningdate. If 0000 is specified, all summary is reported.The second yymm is the end date, and if notsupplied, defaults to the current processing day.

Specifying a range is the only way to access datafrom an archive history file. Otherwise, data isaccessed only from the account log file.

PURGE Purges the summary file before performing amerge. A purge is implied when RANGE= isspecified.

PRINT Prints the summary report. The default is to notprint a report.

NOUPDATE Prints the summary report, but doesn't update thesummary.

Using BIM$ACUT

8–26 BIM-FAQS/PCS

Key Issues

Consider the following issues when using the EVTSUM control statement:

• Because of the potentially large volume of data processed by EVTSUM, usethe ACTION SORTX control statement to force an external sort.

• EVTSUM statements create a file in the MON PDS named PCSEVNTS.SUM.There is one record per event per CPU ID. Each PDS block can contain eightrecords. For example, 1000 event records occupy 125 PDS blocks.

• EVTSUM statements can be used with other BIM$ACUT statements. Forexample, EVTSUM and MERGE can be combined to create archive filesbased on summary information.

Examples

Example Explanation// EXEC BIM$ACUT,SIZE=(BIM$ACUT,100K) ACTION SORTX EVTSUM MERGE IN=NONE,OUT=NONE,LOG=YES/*

Creates event summary data and mergesdata from the account log file. No report isprinted. This is effective for periodicupdates of event summary.

/ EXEC BIM$ACUT,SIZE=(BIM$ACUT,100K) ACTION SORTX EVTSUM MERGEIN=AUDITHI,OUT=AUDITHO,LOG=YES,RESET=WEEKLY/*

Updates event summary data at the sametime as archive data. The event summarydata is updated from the account log fileonly, since RANGE= isn't specified.

// EXEC BIM$ACUT,SIZE=(BIM$ACUT,100K) ACTION SORTX EVTSUM RANGE=(0000) MERGE IN=AUDITHI,OUT=NONE,LOG=YES/*

Creates event summary data from both thearchive history file and the account log file.The RANGE= implies that the summarydata is purged.

// EXEC BIM$ACUT,SIZE=(BIM$ACUT,100K) EVTSUM RANGE=(9401,9401) NOUPDATE MERGE IN=AUDITHI,OUT=NONE,LOG=YES/*

Prints a report with averages from January1994. In this period, some of the data wasalready archived, yet some data still exists inthe account log file. NOUPDATE indicatesthat the current event summary file is notupdated and is printed.

Using BIM$ACUT


DEFINE

Introduction

The DEFINE control statement defines user items, new print headings, or both.

The DEFINE statement is optional. If a DEFINE statement is not supplied, onlythe default items are available and the built-in print headings for reports anditems are used.

FormatDEFine itemname EQ item [HDR="heading"]

DEFINE can be abbreviated as DEF.

Item Names Used With Other BIM$ACUT Control Statements

Once you've redefined an item using DEFINE, that item name is referencedwhenever the item name parameter is used with the following BIM$ACUTstatements: SELECT, SORT, OUTPUT, and PRINT.

Examples

The following example defines the item JUSER to redefine the USER field and touse a print heading of USER for this field:DEF JUSER EQ USER HDR="USER"

The following example defines the item CPUVAL as the item name and specifiesthat positions 3-8 of the CPUID should print, with CPUVAL as a print heading.All field positions are relative to zero.DEF CPUVAL EQ CPUID+2(6) HDR="CPUVAL"

Using BIM$ADUT

8–28 BIM-FAQS/PCS

Using BIM$ADUT

Overview of Control Statements

Introduction

Use the BIM$ADUT utility to maintain library maintenance history. TheBIM$ADUT utility records auditing data and maintains an audit log file thatreports all maintenance performed on any JCL library members.

Auditing is enabled from the online configuration screens.

Auditing Components

The following components are required for auditing:

• An enabled Audit Trail configuration field. To enable auditing, enter Y inthe Audit Trail Enabled field. See Chapter 5, “Defining SystemConfiguration” for more information about configuration options.

• The BIM$ADUT report writer and history file merge utility. BIM$ADUTproduces reports that use either or both the LACAUDIT.CTL file and thearchive history file.

• LACAUDIT.CTL, the audit log file and current data capture file, whichresides in the SYS$VIO PDS.

The following component is optional for auditing:

• The archive history file, which is a tape or disk copy of a previous version ofthe audit log file.

Running BIM$ADUT Under CMS

To run BIM$ADUT under CMS, use the PCSCMS EXEC. For more informationabout PCSCMS, see the BIM-FAQS/PCS Operations Guide.

Using BIM$ADUT


Control Statements

Statement Function


DEFINE Changes headings or item names

MERGE Updates the archived history file






Item names identify the types of information to appear on a report. BIM$ADUTcontrol statements are dependent upon item names. Item names are translatedinto report headings. Both item names and report headings can be redefined usingthe DEFINE control statement.

Item Names

ItemName

Default Heading Description Length (chars)

TNAME TNAME Member affected. Source library namesinclude a period.

10

TLIB TLIB PDS affected. 7

TSUBL TSUB Member type affected. 3

GSID BIM-FAQS/PCS component thatcreated the audit record.

4

Continued

Using BIM$ADUT

8–30 BIM-FAQS/PCS

Continued

ItemName


GSOP Operation performed. Can be one ofthe following BIM-FAQS/PCSoperations:

40 DIR41 ADD42 COPY43 DELETE44 EXEC45 MOVE46 REPLACE47 UPDATE48 DISPLAY49 RSGEN4A EVENT POST4B EVENT RESET4C EVENT UNHOLD4D EVENT HOLD4E EVENT SATISFY54 EVENT LATE55 EVENT ABORT

2

LTYPE Library type. 1

LACERR LAC error code. 1

TEST Y/N ACTION TEST. 1

ERROR E Types of errors encountered:

N NoneP Security

1

PN PN VSE partition where the BIM-FAQS/PCS member was generated.

2

DJNM VSE JOB VSE jobname. DJNM contains the BIM-FAQS/PCS user ID.

8

PJNM PWR JOB POWER jobname. This is the namefrom the * $$ JOB statement.

8

PUSR PWR USR POWER user information. This is theUSER= field from the * $$ JOBstatement.

16

Continued

Using BIM$ADUT


Continued

ItemName


CPUID CPU ID CPU ID serial number on which theJOB executed.

8

STAMP Timestamp in day mm/dd/yy hh.mm.ssformat.

27

DAY DAY Day of the week. 3

DATE DATE Date in yy/mm/dd format, for sortingpurposes.

8

TIME TIME Time in hh.mm.ss format. 8

Sample Items Names


The following are examples of full and partial item names using an offset orlength, or both:


DJNM The whole, 8-character, VSEjobname is used.

PDSANAL1

DJNM(3) The first three characters ofthe VSE jobname are used.

PDS

DJNM+4 The last four characters of theVSE jobname are used.

NAL1

DJNM+3(3) The fourth, fifth, and sixthcharacters of the VSEjobname are used.

ANA

Using BIM$ADUT

8–32 BIM-FAQS/PCS

ACTION

Introduction

The ACTION control statement supplies options and control information toBIM$ADUT.



Parameter Values

Value Function

LOG|NOLOG LOG logs critical information on the system console, including all errors.Ordinary report output is never displayed on the console.

NOLOG prevents critical information from logging on the system console.Severe error messages are output to SYSLOG. NOLOG is the default.

TEST Suppresses alteration of files by BIM$ADUT. For example, TEST bypassesany reset of the audit file or any output to an archive file. When TEST isused, no output files are opened.

LIST|NOLIST LIST displays control statements on SYSLST. ACTION LIST is forced ifACTION TEST is specified.

NOLIST suppresses display of control statements on SYSLST. NOLIST isthe default.

SORTWK=n Specifies the number of sort work files. n defaults to 1. If SORTWK=2 isentered, a DLBL for SORTWK2 must also be present.

CANCEL Issues a CANCEL macro when errors are detected. By default, errorssuppress the processing of a single statement or request; however,execution proceeds, and a report is produced using defaults.

DUMP Produces a dump on any error condition that results in abnormaltermination.


HDR='heading' Specifies the print heading for the output report. heading can be amaximum of 60 characters delimited by single quotation marks.

Continued

Using BIM$ADUT


Continued

Value Function

SORTI=100 Increases the size of the area reserved for an in-core sort. This storage isallocated from GETVIS. When external sorts are disabled, SORTIdetermines the chunk size acquired by each GETVIS request.

DEBUG=nnnnnnnn Enables debugging options. Use this option at the request of BIMTechnical Support only.

Using BIM$ADUT

8–34 BIM-FAQS/PCS

SELECT

Introduction




Parameters

Parameter Function

itemname Item name (field in an audit record for comparison todetermine whether the record is rejected or included in arun).

ro One of the following relational operands: EQ, NE, GT,LT, GE, LE.

value Value or range of values the itemname must have to beincluded in the run.

Logical Operators

Operator Used WhenConditionsMust Be

Example

AND Combined--that is, whenseveralconditionsmust be metbefore arecord isincluded

SELECT DJNM EQ TECHSUP AND DAY EQ SUN

This example selects all records with a VSE jobname ofTECHSUP that were run on Sunday. All other records arerejected, including records with the correct jobname thatwere run on other days, and records run on Sunday butwith other jobnames.

OR Separate--thatis, when anyone of severalconditionsbeing metresults in arecord beingselected

SELECT DJNM EQ TECHSUP OR DJNM EQ SETUP

This example selects all records with either VSE jobnameTECHSUP or SETUP, and rejects all other records.

Using BIM$ADUT



Use AND and OR to specify whether several SELECT statements are dependenton each other.

If you use more than one SELECT statement, AND is assumed at the end of eachstatement, unless you specify OR. Therefore, if several SELECT statements aresupplied, all conditions must be met for a record to be included.



Where AND is Assumed: The following SELECT statements show the precedenceof the AND and OR conditions:

These SELECT statements must work in combination in the following ways:SELECT TLIB EQ IJSYSRSSELECT DJNM EQ TECHSUP AND PN EQ BG ORSELECT DJNM EQ OPERTNS AND PN EQ F4

Only the following records will be included in the report: Records with VSEjobname TECHSUP that were run in the background partition and that affectedthe IJSYSRS libraries, and records with VSE jobname OPERTNS that were run inthe F4 partition and that update the IJSYSRS. All other records will be rejected.

Where OR is Specified Between Statements: The following SELECT statementsshow the precedence of the AND and OR conditions:

SELECT TLIB EQ IJSYSRSSELECT LTYPE EQ CSELECT DJNM EQ TECHSUP OR DJNM EQ SYSTEMS OR DJNM EQ PAYROLL

Only the following records will be included in the report: Records with VSEjobname TECHSUP, SYSTEMS, or PAYROLL, and that affected IJSYSRS coreimage library.

Using BIM$ADUT

8–36 BIM-FAQS/PCS

SORT

Introduction

The SORT control statement specifies the order of the items selected from theinput file. Items from the current audit file or an archived tape or disk file are inchronological order. By default, output is in chronological order.





Sorts can be performed internally (in memory) or externally (on disk).


External Sort: Enter SORTX if you don't have sufficient memory to process asort in memory. Use an external sort if you're sorting more than a few hundredrecords. When an external sort is performed, you must define a DLBL for aSORTWK1 area. The sort work area is always a sequential disk file, so the DLBLmust be type SD. To increase the number of sort work areas, use the ACTIONSORTI= parameter.

The external sort program is loaded into the area between the end of BIM$ADUTand the GETVIS area. If less than 80K is available, the SORT cannot be loaded,and BIM$ADUT attempts to process all records in storage.

Using BIM$ADUT


Examples

Example Explanation

SORT PJNM TLIB The POWER jobname (PJNM) is the primary sort field andthe TO library is the secondary sort field. The length of theresulting sort key is 15 characters. The sort is performed inmemory.

SORTX PUSR+4(4) PN FNAME Positions 4-7 of the POWER user field represent the primarysort field, with partition (PN) as the secondary sort field.The FROM member name is the tertiary sort field. Thelength of the resulting sort key is 15 characters. The sort isperformed externally by calling the system SORT utility.(SORTWK1 must be defined).

Using BIM$ADUT

8–38 BIM-FAQS/PCS

PRINT

Introduction

The PRINT control statement specifies the items to include in a report.

The PRINT statement is optional. If a PRINT statement is not supplied and noother output is defined, a default report format is used. If no PRINT statement issupplied and an OUTPUT statement is present, a printed report is not produced.Note that a print file is different from an output file, and that differentinformation can be formatted into each file in a single pass of the input.








DJNM VSE jobname

PJNM POWER jobname

PN Partition ID

GSOP Function performed

STAMP Timestamp

TLIB "To" library

TNAME "To" member

PUSR POWER user information

Using BIM$ADUT



When a PRINT is performed, a Report Selection Summary is printed. The ReportSelection Summary contains totals of jobs and records read and written. Both thenumber of maintenance executions and the number of operations performed arereported. If MAINT is used to delete ten phases, one job record that consists often transactions is produced. The MERGE summary report lists only jobs, so thenumbers in the two summary pages must be compared with caution. Thefollowing is an example of the Report Selection Summary:


1

2

3

4

5

1,920 = RECORDS READ (ONLINE LOG + HIST)


1,520 = RECORDS REJECTED




• The number of records read from any archive history file and the audit logfile.



• The number of records read from a archive history file. This number is zeroif IN=NONE. Since record selection occurs at the transaction level, thisnumber reflects all jobs seen, including jobs in which some or all of thetransactions were rejected.

• The number of new records read from the audit log file. Records in the auditlog file found in the archive history file are not included in this total. Sincerecord selection occurs at the transaction level, this number reflects all jobsseen, including jobs in which some or all of the transactions were rejected.

Using BIM$ADUT

8–40 BIM-FAQS/PCS

OUTPUT

Introduction

The OUTPUT control statement specifies which items should be formatted intothe output file. An output file is different from a print file, and differentinformation can be formatted into each file in a single pass of the input.

The OUTPUT statement is optional. If an output statement is not supplied, noreport is produced.

FormatOUTPUT item1 item2 item3 ...










Using BIM$ADUT


MERGE

Introduction

The MERGE control statement merges all audit trail records from the audit logfile to an archive history file. Only new records are output. A previously createdarchive history file can also be used as input. In this case, the output history filecontains all records from the input archive history file plus any records from theaudit log file not already present on the archive history file.

The MERGE statement is optional. If a MERGE statement is not supplied, thearchive history file is not updated and the audit log file is not reset. If a report isrequested and no MERGE statement is supplied, then the report containsinformation from only the audit log file. If a MERGE statement is present, noother statements are required.

MERGE Used With Other BIM$ADUT Control Keywords

Any records in the archive history file are also available for user reporting. Thatis, if a run contains a MERGE statement and report generation statements such asSELECT or PRINT, then the resulting report contains information from both theinput archive history file and the audit log file.


IN Parameter Values

IN= is required and specifies the logical unit to be used for a tape file or theTLBL/DLBL name of the file. You can specify the following values for theIN=xxxxxxxx parameter:

Value Function

NONE Indicates that no archive input file is present. IN=NONE is the default.

filename Specifies the name for the input archive history file. The default logical unit isthen SYS004.

DTFMT format is used for the filename if a TLBL card is supplied. DTFSDformat is used for the filename if a DLBL card is supplied.

logunit Specifies the logical unit to be used for a tape file. The default filename is thenAUDITHI.

If a value other than SYS004 is assigned to the logical unit, you must assign thatunit to the desired tape drive.

Continued

Using BIM$ADUT

8–42 BIM-FAQS/PCS

Continued

Value Function

filename/ logunit Specifies both an input filename and its logical unit.

Do so by entering a filename and a desired logical unit, separated by aslash. For example, IN=MYIN/SYS010 specifies a DTF name of MYINwith logical unit SYS010.

AUDITHI If you are using a tape manager that supports dynamic assignment, youcan specify IN=AUDITHI. When AUDITHI is specified, BIM$ADUTdefaults to SYS004.


OUT= enables you to merge records from an existing archive file into a newarchive history file. You can specify the following values for the OUT=xxxxxxxxparameter.

Value Function

NONE Indicates that no output file is written and the audit log file is not reset.OUT=NONE is the default.

filename Specifies the name for the output archive history file. The default logicalunit is then SYS005.

DTFMT format is used for the filename if a TLBL card is supplied. DTFSDformat is used for the filename if a DLBL card is supplied.

logunit Specifies the logical unit to be used for a tape file. The default filename isthen AUDITHO.

If a value other than SYS005 is assigned to the logical unit, you must assignthat unit to the desired tape drive.

filename/ logunit Specifies both an output filename and its logical unit.

Do so by entering a filename and a desired logical unit, separated by a slash.For example, OUT=MYOUT/SYS012 specifies a DTF name of MYOUT withlogical unit SYS012.

AUDITHO If you are using a tape manager that supports dynamic assignment, you canspecify OUT=AUDITHO. When AUDITHO is specified, BIM$ADUTdefaults to SYS005.

Using BIM$ADUT



RESET= resets the audit log file after the merge is complete. RESET= is ignored ifno MERGE output file is defined or if it is assigned to IGN, or if ACTION TEST isin effect. You can specify the following values for the RESET=xxxxxxxxparameter:

Value Function

NO Prevents the audit log file from resetting. RESET=NO is thedefault.

YES Resets the audit log file to empty, with the exception ofrecords created on the current day, after the archive historyfile has been updated.

WEEKLY Purges all but last week's records, after the archive history filehas been updated.

MONTHLY Purges all but last month's records, after the archive historyfile has been updated.



Value Function

YES Reads the audit log file. LOG=YES is the default. If IN= isspecified, the history input file and the audit log file are read,in that order.

NO Prevents reading of the audit log file. If IN= is specified, onlythe archive history file is read. If IN= is not specified, nooutput is produced.

Using BIM$ADUT

8–44 BIM-FAQS/PCS


Whenever a MERGE is performed, a MERGE History Summary is produced.This short report contains totals of maintenance jobs read and written. Allnumbers in this report refer to maintenance jobs. If MAINT is used to delete tenphases, one job record that consists of ten transactions is produced. Thesummary produced with the reporting options lists transactions, so the numbersin the two summary pages will not match. The following is an example of theMERGE History Summary:


1

2

3

4

5







• The number of records read from the input archive history file. This numberis zero if INPUT=NONE is specified. These records are all copied to theoutput.

• The number of new records read from the audit log file. Records on theaudit log file found on the input archive history file are not included in thistotal.

• The total records written to the output archive history file. This is the total ofline 1 and line 2.



Using BIM$ADUT


DEFINE

Introduction

The DEFINE control statement defines user items, new print headings, or both.Once you use the DEFINE statement to define an item, you can refer to itwherever a built-in item can be referenced--for example, in SELECT, SORT,OUTPUT, and PRINT statements.




Examples

The following example defines the item MYJOB which is identical to the suppliedPOWER jobname and has OUR JOB as a print heading:DEF MYJOB EQ PWRJOB HDR="OUR JOB"

The following example defines MYUSER (and the synonym ACTG) to havepositions 4-11 of the POWER User field and to use a print heading of ACTG NBRfor this field:DEF MYUSER EQ PUSR+4(8) HDR="ACTG NBR"

Using BIM$ADUT

8–46 BIM-FAQS/PCS

BIM$ADUT Examples


The following jobstream creates an archived history file. All records output tothe archived history file are purged from the audit log file. No detail report isproduced; only a history summary page is printed.// JOB CREATE HISTORY// TLBL AUDITHO,'BIM$ADUT.HIST'// ASSGN SYS005,280// EXEC BIM$ADUT,SIZE=AUTOMERGE IN=NONE,OUT=SYS005,RESET=YES/*/&


The following jobstream updates an archived history file. The input tape is apreviously created archived history file. The output tape will contain all recordson the input tape plus all new data from the audit log file. All records output tothe archived history file are purged from the audit log file. No detail report isproduced; only a history summary page is printed.// JOB UPDATE HISTORY// TLBL AUDITHI,'BIM$ADUT.HIST'// ASSGN SYS004,281// TLBL AUDITHO,'BIM$ADUT.HIST'// ASSGN SYS005,280// EXEC BIM$ADUT,SIZE=AUTOMERGE IN=SYS004,OUT=SYS005,RESET=YES/*/&

Report from History--Only

The following jobstream reads an existing archived history file and generates areport using only that data. No output archived history file is produced. Norecords are purged from the audit log file. No history summary page is printed.// JOB HISTORY REPORT// TLBL AUDITHI,'BIM$ADUT.HIST'// ASSGN SYS004,280// EXEC BIM$ADUT,SIZE=AUTOMERGE IN=SYS004,LOG=NOSEL GSOP EQ 42 AND TLIB EQ IJSYSRS/*/&

Using BIM$ADUT


Report from History and Audit Log File

The following jobstream reads an existing archived history file and the audit logfile and generates a report. No output archived history file is produced. Norecords are purged from the audit log file. No history summary page is printed.// JOB HISTORY REPORT// TLBL AUDITHI,'BIM$ADUT.HIST'// ASSGN SYS004,280// EXEC BIM$ADUT,SIZE=AUTOMERGE IN=SYS004SEL GSOP EQ 42 AND TLIB EQ IJSYSRS/*/&

Report from Audit Log File--Only

The following jobstream generates a report using the audit log file as input. Sinceno MERGE statement is supplied, only the audit log file is read. Since no PRINTstatement is supplied, the report produced is in the default format. The SELECTstatement includes only catalog runs that update the SYSRES libraries.// JOB HISTORY REPORT// EXEC BIM$ADUT,SIZE=AUTOSEL GSOP EQ 42 OR GSOP EQ 4A AND TLIB EQ IJSYSRS/*/&

Default Report Output

The preceding example generates a default report since no PRINT statementswere supplied. The following is an example of this default report:

JOB DOCAUDT 02/18/98 16.46.01 VSE6.1.2 BIM$ADUT BIM-GSS 5.1A AUDIT REPORTINGUTILITYPN PWR JOB VSE JOB REQUEST TLIB TNAME TSERIAL DAY DATE TIME POWER USER INFOBG FLEET1 FLEET1 CATALOG IJSYSRS XXYYCTED 2 FRI 98/02/06 10.27.17 TEST PWRBG FLEET1 FLEET1 CATALOG IJSYSRS XXYY1 2 FRI 98/02/06 10.27.17 TEST PWRBG EDECK FLIM CATALS IJSYSRS E.DOSDEF 4 FRI 98/02/06 11.31.22 POWER USRBG COMPILE COBOL CATALR IJSYSRS INV930 22 FRI 98/02/06 11.45.02 INV JOB 6

Using BIM$DSUT

8–48 BIM-FAQS/PCS

Using BIM$DSUT

Overview of Control Keywords

Introduction

Use BIM$DSUT to set up dataset logging reports. Dataset monitoring is usefulfor determining when a dataset request was issued.

Running BIM$DSUT Under CMS

To run BIM$DSUT under CMS, use the PCSCMS EXEC. For more informationabout PCSCMS, see the BIM-FAQS/PCS Operations Guide.

Control Statements

You can specify control statements in any order, except for DEFINE. If you referto any fields, you must define them first.

Statement Function






MERGE Updates a history archive file

DEFINE Changes item names or report headings


Item names identify the types of information to appear on your logging reports.BIM$DSUT control statements are dependent upon item names. On loggingreports, item names are translated into report headings. Both item names andreport headings can be redefined using a DEFINE control statement.

Using BIM$DSUT


Item Names

Item Name DefaultHeading

Description Length(chars)

CPUID CPU ID CPU ID serial number on which the JOB executed. 8

DATE DATE Date in yy/mm/dd format, for sorting purposes.Depending on the type of record, STAMP reflectsend-of-step or end-of-job information.

8

DAY DAY Day of the week when a particular job or stepended.

3

DJNM VSE JOB VSE jobname. 8

DSN DATASETNAME

Name of dataset accessed. 44

EVENT EVENT PCS event name that caused a VSE job to execute. 8

FNAME DTF/ACB Internal DTF or ACB name used to reference thefile.

7

FTYPE FTYPE Type of DTF or ACB used to access the file. 5

MAINTASK MAINTASK Program name from the EXEC statement that wasused to access the file.

8

MODE MODE Access mode (INPUT, OUTPUT, WORK). 6

PHASE PHASE Program name from TCB SAVEAREA that wasused to access the file.

8

PJNM PJNM POWER jobname. 8

PN PN VSE partition where the BIM-FAQS/PCS activityoccurred.

2

PROC PROC PCS proc that caused a VSE job to execute. 8

REQUEST RQST File access request (OPEN or CLOS). 4

STAMP Timestamp in day mm/dd/yy hh.mm.ss format.Depending on the type of record, STAMP reflectsend-of-step or end-of-job information.

27

TIME TIME Time in hh.mm.ss format. Depending on the typeof record, STAMP reflects end-of-step or end-of-job information.

8

Using BIM$DSUT

8–50 BIM-FAQS/PCS

Sample Items Names


Here are some examples of full and partial item names using an offset or length,or both:


DJNM The whole, 8-character, VSE jobname is used. PDSANAL1

DJNM(3) The first three characters of the VSE jobname are used. PDS

DJNM+4 The last four characters of the VSE jobname are used. NAL1

DJNM+3(3) The fourth, fifth, and sixth characters of the VSE jobnameare used.

ANA

Using BIM$DSUT


ACTION

Introduction

The ACTION control statement supplies options and control information toBIM$DSUT.



Parameter Values

Value Function

LOG|NOLOG LOG logs critical information on the system console, including all errors.Ordinary report output is never displayed on the console.

NOLOG prevents critical information from logging on the system console,except for severe error messages. NOLOG is the default.

TEST Suppresses alteration of files by BIM$DSUT. For example, TEST bypasses anyreset of the dataset file or any output to an archive file. When TEST is used, nooutput files are opened.

LIST|NOLIST LIST displays control statements on SYSLST. ACTION LIST is forced ifACTION TEST is specified.

NOLIST suppresses display of control statements on SYSLST. NOLIST is thedefault.

SORTWK=n Specifies the number of sort work files. n defaults to 1. If SORTWK=2 isentered, a DLBL for SORTWK2 must also be present. SORTWK=n is notsupported under native CMS execution of BIM$DSUT.

CANCEL Issues a CANCEL macro when errors are detected. By default, errors suppressthe processing of a single statement or request; however, execution proceeds,and a report is produced using defaults.

CANCEL,DUMP Produces a dump on any error condition that results in abnormal termination.


HDR='heading' Specifies the print heading for the output report. heading can be a maximum of60 characters delimited by single quotation marks.

SORTX Specifies that files are sorted externally.

DEBUG=nnnnnnnn Enables debugging options. Use this option at the request of BIM TechnicalSupport only.

Using BIM$DSUT

8–52 BIM-FAQS/PCS

SELECT

Introduction




Parameters

Parameter Function

Itemname Item name (field in a dataset record for comparison todetermine whether the record is rejected or included in arun).

Ro One of the following relational operands: EQ, NE, GT, LT,GE, LE.

Value Value or range of values the named item must have to beincluded in the run.

Logical Operators

Operator Used WhenConditions MustBe

Example

AND Combined--that is,when severalconditions must bemet before a recordis included

SELECT PHASE EQ IDCAMS AND DAY EQ SUN

This example selects all records with the phase IDCAMS thatwere run on Sunday. All other records are rejected, includingrecords with the correct phase that were run on other days,and records run on Sunday but with other phases.

OR Separate--that is,when any one ofseveral conditionsbeing met results ina record beingselected

SELECT PHASE EQ IDCAMS OR PHASE EQ SORT

This example selects all records with either phase IDCAMS orSORT, and rejects all other records.

Using BIM$DSUT



Use AND and OR to specify whether several SELECT statements are dependenton each other.

If you use more than one SELECT statement, AND is assumed at the end of eachSELECT statement, unless you specify OR. Therefore, if several SELECTstatements are supplied, all conditions must be met for a record to be included.

When a line ends with OR, and any condition on that line is matched, the currentrecord is selected, even if subsequent lines have tests that fail.


Where AND is Assumed: The following SELECT statements show the precedenceof the AND and OR conditions:

These SELECT statements must work in combination in the following ways:SELECT DJNM EQ PAYROLLSELECT MODE NE INPUTSELECT DSN EQ PAY* OR DSN EQ WORK*


• Records that are open for INPUT are rejected; only files open for WORK orOUTPUT are kept. (This is because neither line includes an OR as the lastword).

• Finally, the last statement rejects any records whose dataset name does notstart with PAY or WORK.

• Therefore, the selected records are all datasets that begin with PAY orWORK, that were referenced by VSE job PAYROLL, and that were not openfor INPUT.

Where OR is Specified Between Statements: The following SELECT statementsshow the precedence of the AND and OR conditions:SELECT DJNM EQ PAYROLLSELECT MODE NE INPUT ORSELECT DSN EQ PAY* OR DSN EQ WORK*

Using BIM$DSUT

8–54 BIM-FAQS/PCS



• Only files that were not open for INPUT or records whose dataset namestarts with PAY or WORK are kept.

• Therefore, the selected records are either datasets that begin with PAY orWORK that caused VSE job PAYROLL to execute or datasets that were notaccessed for input by VSE job PAYROLL.

Using BIM$DSUT


SORT

Introduction

The SORT control statement specifies the order of the items selected from theinput file. Items from the current dataset log file or an archived tape or diskhistory file are in chronological order. By default, output is in chronologicalorder.





Sorts can be performed internally (in memory) or externally (on disk). Toimprove performance, use an external sort when sorting more than a fewhundred records. External sorts are not supported when BIM$DSUT is executedunder native CMS.


External Sort: Enter SORTX if you don't have sufficient memory to process asort in memory. Use an external sort if you're sorting more than a few hundredrecords. When an external sort is performed, you must define a DLBL for aSORTWK1 area. The sort work area is always a sequential disk file, so the DLBLmust be type SD. To increase the number of sort work areas, use the ACTIONSORTWK=n parameter.

The external sort program is loaded into the area between the end of BIM$DSUTand the GETVIS area. If less than 80K is available, the SORT cannot be loaded,and BIM$DSUT attempts to process all records in storage. Therefore, you shouldspecify the parameter SIZE=(BIM$DSUT,80K) to allow room for the SORTprogram to be loaded.

Using BIM$DSUT

8–56 BIM-FAQS/PCS

Examples

Example Explanation

SORT PJNM DJNM The POWER jobname (PJNM) is the primary sort field andthe VSE jobname (DJNM) is the secondary sort field. Thelength of the resulting sort key is 16 characters. The sort isperformed in memory.

SORTX DSN(4) PN PHASE Positions 1-4 of the dataset name field are the primary sortfield, with partition (PN) as the secondary sort field. Thephase name is the tertiary sort field. The length of theresulting sort key is 14 characters. The sort is performedexternally by calling the system SORT utility. (SORTWK1must be defined.)

Using BIM$DSUT


PRINT

Introduction

The PRINT control statement specifies the items to include in an output report.

The PRINT statement is optional. If a PRINT statement is not supplied and noother output is defined, a default report format is used. If no PRINT statement issupplied and an OUTPUT statement is present, a printed report is not produced.Note that a print file is different from an output file, and that differentinformation can be formatted into each file in a single pass of the input.








CPUID CPU ID

DJNM VSE jobname

DSN Dataset name

MODE Mode of use

PHASE Phase name

PJNM POWER jobname

PN Partition ID

REQUEST Request type

STAMP Timestamp

Using BIM$DSUT

8–58 BIM-FAQS/PCS


When a PRINT is performed and ACTION LIST is specified, a Report SelectionSummary is printed.

JCL Example: The following JCL shows how to get a Report Selection Summary:// EXEC BIM$DSUT,SIZE=BIM$DSUTACTION LISTMERGE IN=NONE,OUT=NONE,LOG=YESSELECT DSN(1) NE T AND EVENT NE ' 'PRINT EVENT/*

Report Example: The Report Selection Summary contains totals of jobs andrecords read and written. Both the number of maintenance executions and thenumber of operations performed are reported. The ACTION LIST commandmust have been specified. The following is an example of the Report SelectionSummary:


1

2

3

4

5

569 = RECORDS READ (ONLINE LOG + HIST)


332 = RECORDS REJECTED




• The number of records read from any history archive file and the dataset logfile.



• The number of records read from the input file. This number is zero ifIN=NONE.

• The number of new records read from the dataset log file. Records in thedataset log file found in the history archive file are not included in this total.Since record selection occurs at the transaction level, this number reflects alljobs seen, including jobs in which some or all of the transactions wererejected.

Using BIM$DSUT


OUTPUT

Introduction

The OUTPUT control statement specifies which items should be formatted intothe output file. An output file is different from a print file, and differentinformation can be formatted into each file in a single pass of the input. Anoutput file is useful if you want to produce reports other than those provided byBIM$DSUT.

The OUTPUT statement is optional. If an output statement is not supplied, nooutput file is produced.

The OUTPUT control statement is not supported under native CMS execution ofBIM$DSUT.

FormatOUTput item1 item2 item3 ...

The order of the item parameters indicates how the items are output. OUTPUTcan be abbreviated as OUT.










Using BIM$DSUT

8–60 BIM-FAQS/PCS

MERGE

Introduction

The MERGE control statement identifies input for report and controls archiving.Only new records are output. A previously created archive history file can alsobe used as input. In this case, the output history file contains all records from theinput history archive file plus any records from the dataset log file not alreadypresent on the history archive file.

The MERGE statement is optional. If a MERGE statement is not supplied, thearchive history file is not updated and the dataset log file is not reset. If a reportis requested and no MERGE statement is supplied, then the report containsinformation from only the dataset log file. If a MERGE statement is present, noother statements are required.

MERGE is not available under native CMS execution of BIM$DSUT.

MERGE Used with Other BIM$DSUT Control Keywords

Any records in the history archive file are also available for user reporting. Thatis, if a run contains a MERGE statement and report generation statements such asSELECT or PRINT, then the resulting report contains information from both theinput history archive file and the dataset log file.


Using BIM$DSUT


IN Parameter Values

You can specify the following values for the IN=xxxxxxxx parameter:

Value Function

NONE Indicates that no archive input file is present. IN=NONE isthe default.

Filename Specifies the name for the input history archive file. Thedefault logical unit is then SYS004.

DTFMT format is used for the filename if a TLBL card issupplied. DTFSD format is used for the filename if a DLBLcard is supplied.

Logunit Specifies the logical unit to be used for a tape file. Thedefault filename is then AUDITHI.

If a value other than SYS004 is assigned to the logical unit,you must assign that unit to the desired tape drive.

Filename/ logunit Specifies both an input filename and its logical unit.

Do so by entering a filename and a desired logical unit,separated by a slash. For example, IN=MYIN/SYS010specifies a DTF name of MYIN with logical unit SYS010.

AUDITHI If you are using a tape manager that supports dynamicassignment, you can specify IN=AUDITHI. WhenAUDITHI is specified, BIM$DSUT defaults to SYS004.Override the default SYS number by specifying the logicalunit following AUDITHI. For example,IN=AUDITHI/SYS016 overrides the default value.

Using BIM$DSUT

8–62 BIM-FAQS/PCS


OUT= enables you to merge records from an existing archive file into a newarchive history file. You can specify the following values for the OUT=xxxxxxxxparameter.

Value Function

NONE Indicates that no output file is written and the dataset logfile is not reset. OUT=NONE is the default.

Filename Specifies the name for the output history archive file. Thedefault logical unit is then SYS005.

DTFMT format is used for the filename if a TLBL card issupplied. DTFSD format is used for the filename if aDLBL card is supplied.

Logunit Specifies the logical unit to be used for a tape file. Thedefault filename is then AUDITHO.

If a value other than SYS005 is assigned to the logical unit,you must assign that unit to the desired tape drive.

Filename/ logunit Specifies both an output filename and its logical unit.

Do so by entering a filename and a desired logical unit,separated by a slash. For example,OUT=MYOUT/SYS012 specifies a DTF name of MYOUTwith logical unit SYS012.

AUDITHO If you are using a tape manager that supports dynamicassignment, you can specify OUT=AUDITHO. WhenAUDITHO is specified, BIM$DSUT defaults to SYS005.Override the default SYS number by specifying the logicalunit following AUDITHO. For example,OUT=AUDITHO/SYS017 overrides the default value.

Using BIM$DSUT



You can specify the following values for the RESET=xxxxxxxx parameter:

Value Function

NO Prevents the dataset log file from resetting. RESET=NO isthe default.

YES Resets the dataset log file to empty, with the exception ofrecords created on the current day, after the history archivefile has been updated. RESET=YES is ignored if one of thefollowing conditions exists:

No MERGE output file is defined.

The MERGE output file is assigned to IGN andOUT=AUDITHO is specified.

ACTION TEST is specified.

WEEKLY Purges all but last week's records, after the history archivefile has been updated.

MONTHLY Purges all but last month's records, after the history archivefile has been updated.



Value Function

YES Reads the dataset log file. LOG=YES is the default. If IN= isspecified, the history input file and the dataset log file areread, in that order.

NO Prevents reading of the dataset log file. If IN= is specified,only the history archive file is read. If IN= is not specified, nooutput is produced.

Using BIM$DSUT

8–64 BIM-FAQS/PCS

MERGE Examples

Specifying Files and Purging

The following example specifies MYIN as the TLBL/DLBL name of the input file,MYOUT as the TLBL/DLBL name of the output tape file, and purges all but lastweek's records when the history archive file is updated:MERGE IN=MYIN,OUT=MYOUT,RESET=WEEKLY

Reporting From Dataset Log File Only

The following jobstream generates a report using the audit log file as input. Sinceno MERGE statement is supplied, only the dataset log file is read. Since noPRINT statement is supplied, the report produced is in the default format. Allactivity having to do with the VSE jobname PAYROLL that occurred on any date,on or after February 18, 1998, is selected. // JOB HISTORY REPORT // EXEC BIM$DSUT,SIZE=BIM$DSUT SEL DJNM EQ PAYROLL AND DATE GE 98/02/18 /* /&

The preceding example generated a default report since no PRINT statementswere supplied. The following is an example of this default report:

JOB DOCDSN 02/18/98 16.59.14 VSE6.1.2 BIM$DSUT BIM-FAQS/PCS V5.1A DSN LOG REPORTING UTILITY

DATASET NAME DAY DATE TIME RQST MODE PN PWR JOB VSE JOB PHASE CPUID

ALERT.S1SCTY.V50 WED 98/02/18 08.09.13 OPEN INPUT F5 S1B550 S1B550 S1B550 FF039001

VSAM.MASTER.CATALOG WED 98/02/18 08.09.14 OPEN OUTPUT F5 S1B550 S1B550 S1B550 FF039001

BIM.USER.CATALOG WED 98/02/18 08.09.16 OPEN OUTPUT F5 S1B550 S1B550 S1B550 FF039001

ALERT.S1SCTY.V50 WED 98/02/18 08.09.16 OPEN INPUT F5 S1B550 S1B550 S1B550 FF039001

Using BIM$DSUT



Whenever a MERGE is performed, a MERGE History Summary is produced.This short report contains totals of maintenance jobs read and written. Thefollowing is an example of the MERGE History Summary:


1

2

3

4

5

6

7

8






XMRIHLIM NEV 00/00/00 00.00.00

TOD0000 MON 04/15/91 00.00.00

TODRESET SUN 04/14/91 23.59.59


• The number of records read from the input history archive file. This numberis zero if INPUT=NONE is specified. These records are all copied to theoutput.

• The number of new records read from the dataset log file. Records on thedataset log file found on the input history archive file are not included in thistotal.

• The total records written to the output history archive file. This is the total ofline 1 and line 2.



• The date of last record that was written to tape.

• The time of day the first record was saved in PCSDSNOC.CTL

• The time of day the last record was written to tape.

Lines 6 - 8 are written to the report when OUT=AUDITHO and RESET= anyvalue:

Using BIM$DSUT

8–66 BIM-FAQS/PCS


The following jobstream creates a history archive file. All records output to thehistory archive file are purged from the audit log file. No detail report isproduced; only a history summary page is printed.// JOB CREATE HISTORY// DLBL AUDITHO,'BIM$DSUT.HIST'// ASSGN SYS005,351// EXEC BIM$DSUT,SIZE=BIM$DSUTMERGE IN=NONE,OUT=SYS005,RESET=YES/*/&


The following jobstream updates a history archive file. The input tape is apreviously created history archive file. The output tape contains all records onthe input tape plus all new data from the audit log file. All records output to thehistory archive file are purged from the audit log file. No detail report isproduced; only a history summary page is printed.// JOB UPDATE HISTORY// TLBL AUDITHI,'BIM$DSUT.HIST'// ASSGN SYS004,281// TLBL AUDITHO,'BIM$DSUT.HIST'// ASSGN SYS005,280// EXEC BIM$DSUT,SIZE=BIM$DSUTMERGE IN=SYS004,OUT=SYS005,RESET=YES/*/&

Reporting from History Archive File Only

The following jobstream reads an existing history archive file and generates areport using only that data. No output history archive file is produced. Norecords are purged from the dataset log file. No history summary page isprinted.// JOB HISTORY REPORT// TLBL AUDITHI,'BIM$DSUT.HIST'// ASSGN SYS004,280// EXEC BIM$DSUT,SIZE=BIM$DSUTMERGE IN=SYS004,LOG=NOSEL DATE EQ 92/02/29/*/&

Using BIM$DSUT


Reporting from History Archive File and Dataset Log File

The following jobstream reads an existing history archive file and the dataset logfile and generates a report. No output history archive file is produced. Norecords are purged from the dataset log file. No history summary page isprinted.// JOB HISTORY REPORT// TLBL AUDITHI,'BIM$DSUT.HIST'// ASSGN SYS004,280// EXEC BIM$DSUT,SIZE=BIM$DSUTMERGE IN=SYS004SEL PHASE EQ LIBR/*/&

Using BIM$DSUT

8–68 BIM-FAQS/PCS

DEFINE

Introduction

The DEFINE control statement defines user items, new print headings, or both.Once you use the DEFINE statement to define an item, you can refer to itwherever a built-in item can be referenced--for example, in SELECT, SORT,OUTPUT, and PRINT statements.


Item Names Used with Other BIM$DSUT Control Statements

Once you've redefined an item using DEFINE, that item name is referencedwhenever the item name parameter is used with the following BIM$DSUTstatements: SELECT, SORT, OUTPUT, and PRINT.



Examples

The following example defines the item PJNM to redefine the POWJOB field andto use a print heading of POW JOB for this field:DEF PJNM EQ POWJOB HDR="POW JOB"

The following example defines the item CPUVAL as the item name and specifiesthat positions 3-8 of the CPUID should print, with CPUVAL as a print heading.All field positions are relative to zero.DEF CPUVAL EQ CPUID+2(6) HDR="CPUVAL"

Using Online Options to Monitor BIM-FAQS/PCS



Viewing Account History Online

Introduction

You can view job accounting information online to help you determine specificevent information. Both detail and summary reports are available to view eventhistory.

Accessing Online Job Account Information

To access job accounting information, perform either of the following:

• Enter Z at the command prompt from the Menu Index. The Account HistorySelection Panel is displayed, from which you can access detailed or summaryevent reports.

• Enter Z in the input field of a specific event on the Event MaintenanceScreen. The Account History Information Screen is displayed, which listsspecific event and PROC information.

Account History Selection Panel

The Account History Selection Panel enables you to view any BIM-FAQS/PCSaccount record produced because an event or member was executed in apartition. From the Account History Selection Panel, you can access the AccountHistory Information Screen and the Event History Summary Screen. Thefollowing screen shows an example of the Account History Selection Panel:

JOLACCT .Z ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS ACCOUNT HISTORY SELECTION PANEL **

Event ===> (Event name Generics supported) Proc ===> (Proc name Generics supported) Djob ===> (Dos Job Name Generics supported) Pjob ===> (Power Job Name Generics supported) Phase ===> (Phase Name Generics supported) Pid ===> (Partition Id or *) Date ===> (= > < ¬ YY/MM/DD or *) CC ===> (= > < ¬ CC or *) $RC ===> (= > < ¬ $RC or *) $MRC ===> (= > < ¬ $MRC or *) Type ===> (Record type L, S, C, or *)

Fill in information for one or more of the above listed selections. Any selection that is not specified will default to *.

PF1=Help PF2=Summary PF3=Return


8–70 BIM-FAQS/PCS

Account History Information Screen

The Account History Information Screen shows all current account historyrecords based on your selection. The following two screens show an example ofthe full screen of the Account History Information Screen. To move from the firstscreen to the second, you press PF11 (Right); to return to the first from thesecond, press PF10 (Left).

JOLACCT .0 ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===> Account history information Event DJOB Phase PN CC $RC SIO CPUT Date Time Duration GVART14 TSTPCS BIM$ACUT Z3 10 0000 000482 000.56 98/02/18 13.05.24 00.00.11 CICSICCF IESWAITT F2 10 0000 000163 000.26 98/02/18 13.03.42 00.00.01 CICSICCF DTSANALS F2 10 0000 000155 000.28 98/02/18 13.03.41 00.00.02 CICSICCF DTRSETP F2 10 0000 000470 000.97 98/02/18 13.03.39 00.00.43 CICSICCF IESWAITT F2 10 0000 000117 000.37 98/02/18 11.25.16 00.00.02 CICSICCF DTSANALS F2 10 0000 000182 000.40 98/02/18 11.25.14 00.00.08 CICSICCF DTRSETP F2 10 0000 000507 001.65 98/02/18 11.25.05 00.00.25 FAQSMAIN BIM$UTTS Z3 20 0000 068595 787.36 98/02/18 11.07.08 65.18.20 CICSICCF DFHSIP F2 17 0000 026121 746.38 98/02/18 11.02.30 65.15.23 FAQSIUX FAQSIUX Z1 10 0000 019719 066.83 98/02/18 11.01.36 65.12.51 IMOD N/A Z2 98/02/18 08.00.07 FIRSTGRP N/A Z2 98/02/18 00.30.01 TSTNOAUX N/A CM 98/02/18 00.00.44 TESTMAN4 N/A Z2 98/02/18 00.00.44 CHKSRV N/A CM 98/02/18 00.00.43 EVENTBK PCSEVBR PCSEVBR F5 10 0000 000654 000.79 98/02/17 22.04.34 00.00.07 BACKEVT BIM$PUTL BIM$PUTL F5 10 0000 001031 001.24 98/02/17 22.04.2200.00.14 BACKVIO BIM$PUTL BIM$PUTL F5 10 0000 006099 008.12 98/02/17 22.04.0200.01.30 BACKMON BIM$PUTL BIM$PUTL F7 10 0000 004824 006.89 98/02/17 22.02.2400.02.17 PF1=Help PF2=FIFO PF3=Return PF8=Fwd PF11=Right

JOLACCT .B ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===> Account history information Proc PJOB Day $MRC TOTLSIO TOTCPUT Totldur Cpuid T Userid GSACCTM TSTPCS WED 0000 0000482 000.56 00.00.11 FF039002 L PCSSERV ?BIM$OIEI CICSICCF WED 0000 FF039002 S PCSMAINT ?BIM$OIEI CICSICCF WED 0000 FF039002 S PCSMAINT ?BIM$OIEI CICSICCF WED 0000 FF039002 S PCSMAINT ?BIM$OIEI CICSICCF WED 0000 FF039001 S PCSMAINT ?BIM$OIEI CICSICCF WED 0000 FF039001 S PCSMAINT ?BIM$OIEI CICSICCF WED 0000 FF039001 S PCSMAINT ?BIM$OIEI FAQSMAIN WED 0000 0068595 787.36 65.18.20 FF039001 L PCSMAINT ?BIM$OIEI CICSICCF WED 0000 0026881 748.83 65.16.03 FF039001 L PCSMAINT ?BIM$OIEI FAQSIUX WED 0000 0019719 066.83 65.12.51 FF039001 L ASOMAINT WED FF039001 C WED FF039001 C WED FF000001 C WED FF039001 C WED FF000001 C EVENTBK PCSEVBR TUE 0000 0000654 000.79 00.00.07 FF039001 L ADMN PDSEVTBK BIM$PUTL TUE 0000 0001031 001.24 00.00.14 FF039001 L ADMN PDSVIOBK BIM$PUTL TUE 0000 0006099 008.12 00.01.30 FF039001 L ADMN PDSMONBK BIM$PUTL TUE 0000 0004824 006.89 00.02.17 FF039001 L ADMN PF1=Help PF2=FIFO PF3=Return PF8=Fwd PF10=Left



Event History Summary Screen

The Event History Summary Screen (PF2 key) shows summarized accounthistory information. Summary information includes average duration, averageCPU seconds, average SIO count, average start time, and modal start times. Asummary record is maintained for each event that is run per CPU ID.

Averages are maintained based on event data collected over the last 12 monthsthat event occurred.

JOLEFORC.2 ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===> BIM-FAQS/PCS EVENT HISTORY SUMMARY

Event name ===> * CPU ===> *

LAST LOGGED OVERALL AVERAGES EVENT CPUID DATE TIME DURATION CPUS SIOS START

_ AFTERGRP FF000001 98/01/15 09.00.31 0:00:03 0.62 303 11:09:35 _ ALRTBCK FF000001 98/01/22 22.00.19 0:00:16 1.82 1057 22:00:02 _ ALRTBCKW FF000001 98/01/16 22.00.30 0:00:35 2.84 1757 20:02:16 _ BACKEVT FF000001 98/01/22 22.04.21 0:00:12 0.95 755 22:03:38 _ BACKMON FF000001 98/01/22 22.01.56 0:01:44 6.53 4601 21:45:19 _ BACKVIO FF000001 98/01/22 22.03.59 0:01:41 7.40 5640 21:47:30 _ BADIOTST FF000001 98/01/21 11.26.03 0:13:08 0.80 1189 14:36:11 _ CHKSRV FF000001 98/01/23 00.00.16 03:17:04 _ CREFBLD FF000001 98/01/12 22.02.09 0:00:09 0.60 309 22:02:00 _ DUPCAL FF000001 97/12/23 10.09.02 0:00:10 0.61 328 12:28:08 _ EVENTBK FF000001 98/01/22 22.04.34 0:00:05 0.64 505 22:03:58 _ EVLD1 FF000001 98/01/06 13.39.32 12:19:04 _ EVLD2 FF000001 98/01/06 13.39.40 12:48:40 Options: C=CPU D=Duration S=SIO T=Time PF1=Help PF3=Return PF8=Fwd

Enabling Event History Summary Reporting

Event summary data is collected by the EVTSUM control statement of theBIM$ACUT utility. We recommend that you execute this utility to provide moreaccurate and useful data.


See the BIM-FAQS/PCS Operations Guide for the following information about jobaccount history:

• Accounting History Selection Panel input fields

• Account History Information Screen contents

• Event History Summary Screen fields and action codes

• PF-key functions


8–72 BIM-FAQS/PCS

Viewing Audit History Online

Introduction

You can view audit history information online to help you determine specificPDS member or event information. General maintenance information isavailable.

Accessing Online Audit History Information

To access audit history, perform either of the following:

• Enter A at the command prompt from the Menu Index. The Audit HistorySelection Panel is displayed, from which you can access PDS members orevents and general maintenance history.

• Enter A in the input field of a specific event on the Event MaintenanceScreen. The Audit History Screen is displayed, which lists specific memberand library information.

Audit History Selection Panel

The Audit History Selection Panel enables you to view audit history information.From the Audit History Selection Panel, you can access the Audit History Screen.

The following screen shows an example of the Audit History Selection Panel:

JOLAUDT .A ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===> BIM-FAQS/PCS AUDIT HISTORY SELECTION PANELName ===> (Event or PDS member name Generics supported)Date ===> (= > < YY/MM/DD or *)Lib ===> (PDS DLBL name or External Library Name) Functions Member Type _ All Functions _ All Types of Members _ ADD _ Events (Current and Master File) _ COPY _ Master Event File _ DELETE _ Current Event File _ EXEC _ PDS Members _ MOVE _ Source or BIM$OIEI Submit _ REPLACE _ ICCF Members _ UPDATE _ VSE Library Members _ DSPL _ BIM-EDIT Members _ RSGE _ CONDOR Members _ POST _ LIBRARIAN Members _ RESET _ PANVALET Members _ UNHOLD _ VOLLIE Members _ HOLD _ USER Members _ LATE _ POWER RDR Queue _ ABORT PF1=Help PF3=Return



Audit History Screen

The Audit History Information Screen shows all current audit history recordsbased on your selections. The following screens are an example of the full screenof the Audit History Screen for all events that begin with J. To move from thefirst screen to the second, you press PF11 (Right); to return to the first from thesecond, press PF10 (Left).

JOLAUDT .0 ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===> Audit History for J* * Member Typ Request Lib User Library CPU E Day Date Time JCLCONFG CTL DSPL P Q024 SYS$MON FF039001 N WED 98/02/18 13.58.46 JCLCONFG CTL DSPL P Q024 SYS$MON FF039001 N WED 98/02/18 13.54.19 JCLCONFG CTL DSPL P Q024 SYS$MON FF039001 N WED 98/02/18 13.51.29 JCLCONFG CTL DSPL P Q024 SYS$MON FF039001 N WED 98/02/18 12.51.47 JCLCONFG CTL DSPL P Q024 SYS$MON FF039001 N WED 98/02/18 12.49.22 JCLCONFG CTL DSPL P PCSMAINT SYS$MON FF039001 N WED 98/02/18 12.05.14 JCLCONFG CTL DSPL P Q013 SYS$MON FF039001 N WED 98/02/18 10.25.17 JCLCONFG CTL DSPL P Q013 SYS$MON FF039001 N WED 98/02/18 08.34.15 JCLCONFG CTL COPY P PCSMAINT SYS$MON FF039001 N TUE 98/02/17 11.07.17 JCLCONFG CTL DSPL P PCSMAINT SYS$MON FF039001 N TUE 98/02/17 11.06.26 JCLCONFG CTL REPLACE P PCSMAINT SYS$MON FF039001 N TUE 98/02/17 11.03.58 JCLCONFG CTL DSPL P PCSMAINT SYS$MON FF039001 N TUE 98/02/17 11.02.56 JCLSCHED CTL REPLACE P PCSMAINT SYS$MON FF000001 N TUE 98/02/17 09.15.10 JCLSCHED CTL COPY P PCSMAINT SYS$MON FF000001 N TUE 98/02/17 09.14.11 JCLREPTS PRO DSPL L PCSMAINT BIMCOL FF039001 N TUE 98/02/17 08.56.18 JCLJAUTO CTL COPY P PCSMAINT SYS$MON FF039001 N TUE 98/02/17 08.45.59 JCLSCHED CTL COPY P PCSMAINT SYS$MON FF039001 N TUE 98/02/17 08.44.48 JCLMNEWM PRO DSPL L PCSMAINT BIMCOL FF039001 N TUE 98/02/17 08.41.10 JCLMPROC PRO DSPL L PCSMAINT BIMCOL FF039001 N TUE 98/02/17 08.29.20 PF1=Help PF2=FIFO PF3=Return PF8=Fwd PF11=Right

JOLAUDT .B ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===> Audit History for J* * PJOB Pn POWER User Field Group FAQSMAIN Z2 FAQSMAIN Z2 FAQSMAIN Z2 FAQSMAIN Z2 FAQSMAIN Z2 FAQSMAIN Z2 FAQSMAIN Z3 FAQSMAIN Z3 FAQSMAIN Z3 FAQSMAIN Z3 FAQSMAIN Z3 FAQSMAIN Z3 CMS BG CMS BG FAQSMAIN Z3 FAQSMAIN Z3 FAQSMAIN Z3 FAQSMAIN Z3 FAQSMAIN Z3 PF1=Help PF2=FIFO PF3=Return PF8=Fwd PF10=Left


8–74 BIM-FAQS/PCS


See the BIM-FAQS/PCS Operations Guide for the following information aboutaudit history:

• Audit History Selection Panel input fields

• Audit History Screen contents




Viewing Dataset History Online

Introduction

The Dataset Audit Log enables you to view detailed dataset history informationonline.

Accessing Online Dataset History Information

To access dataset history information, perform either of the following:

• Enter D at the command prompt from the Menu Index. The ResourceDisplay Menu is displayed. Enter D at the command prompt from theResource Display Menu. The Dataset Log Selection Panel is displayed, fromwhich you can access a detailed dataset report.

• Enter K in the input field of a specific event on the Event MaintenanceScreen. The Dataset Audit Log is displayed.

Dataset Log Selection Panel

The Dataset Log Selection Panel enables you to select criteria to produce adisplay of dataset history information. From the Dataset Log Selection Panel,you can access the Dataset Audit Log.

The following screen shows the Dataset Log Selection Panel:

JOLDLOG .D ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS DATASET LOG SELECTION PANEL **

DSN ===> * Request ===> * (Request type Open, Close) Mode ===> * (Mode of use Input, Output, Work) Date ===> =* (= > < ¬ YY/MM/DD or *) Djob ===> * (VSE jobname) Pjob ===> * (POWER jobname) Phase ===> * (PHASE name) Event ===> * (EVENT name) Pid ===> * (Partition id) Type ===> * (Type of file)

Fill in information for one or more of the above listed selections. Any selection that is not specified will default to *.

PF1=Help PF3=Return PF4=Flush DSN buffer


8–76 BIM-FAQS/PCS

Dataset Audit Log

The Dataset Audit Log shows all current dataset history records based on yourselection. The following two screens show an example of the full screen of theDataset Audit Log. To move from the first screen to the second, press PF11(Right); to return to the first screen from the second, press PF10 (Left).

JOLDLOG .0 ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS Dataset Audit Log **

DataSet Name DATE TIME DAY RQST

BIM.USER.CATALOG 98/02/18 11.05.31 WED CLOSVSAM.MASTER.CATALOG 98/02/18 11.05.31 WED CLOSALERT.AXPLOG1.V49 98/02/18 11.05.30 WED CLOSVSESP.USER.CATALOG 98/02/18 11.01.42 WED CLOSVSAM.MASTER.CATALOG 98/02/18 11.01.42 WED CLOSPC.HOST.TRANSFER.FILE 98/02/18 11.01.42 WED CLOSVSE.TEXT.REPSTORY.FILE 98/02/18 11.01.42 WED CLOSVSE.MESSAGE.ROUTING.FILE 98/02/18 11.01.41 WED CLOSVSE.CONTROL.FILE 98/02/18 11.01.41 WED CLOSVSE.ONLINE.PROB.DET.FILE 98/02/18 11.01.41 WED CLOSDFHTEMP 98/02/18 11.01.41 WED CLOSCICS.TD.INTRA 98/02/18 11.01.41 WED CLOSCICS.DUMPA 98/02/18 11.01.40 WED CLOSCICS.RSD 98/02/18 11.01.39 WED CLOSBIM.USER.CATALOG 98/02/18 08.55.48 WED CLOS

PF1=Help PF2=FIFO PF3=Return PF8=Fwd PF11=Right

JOLDLOG .B ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS Dataset Audit Log **

DTF/ACB MODE TYPE PN POWJOB DOSJOB MAINTASK PHASE CPUID EVENT

ALTCAT OUTPUT VSAM C1 AXPLOGGR AXPL1 AXPL1 AXPL1 FF039001IJSYSCT OUTPUT VSAM C1 AXPLOGGR AXPL1 AXPL1 AXPL1 FF039001AXPLOG1 OUTPUT VSAM C1 AXPLOGGR AXPL1 AXPL1 AXPLIO FF039001VSESPUC OUTPUT VSAM F2 CICSICCF CICSICCF DFHSIP DFHSIP FF039001IJSYSCT OUTPUT VSAM F2 CICSICCF CICSICCF DFHSIP DFHSIP FF039001INWFILE OUTPUT VSAM F2 CICSICCF CICSICCF DFHSIP DFHSIP FF039001IESTRFL OUTPUT VSAM F2 CICSICCF CICSICCF DFHSIP DFHSIP FF039001IESROUT OUTPUT VSAM F2 CICSICCF CICSICCF DFHSIP DFHSIP FF039001IESCNTL OUTPUT VSAM F2 CICSICCF CICSICCF DFHSIP DFHSIP FF039001IESPRB OUTPUT VSAM F2 CICSICCF CICSICCF DFHSIP DFHSIP FF039001DFHTEMP OUTPUT VSAM F2 CICSICCF CICSICCF DFHSIP DFHSIP FF039001DFHNTRA OUTPUT VSAM F2 CICSICCF CICSICCF DFHSIP DFHSIP FF039001DFHDMPA OUTPUT VSAM F2 CICSICCF CICSICCF DFHSIP DFHSIP FF039001DFHRSD OUTPUT VSAM F2 CICSICCF CICSICCF DFHSIP DFHSIP FF039001ALTCAT OUTPUT VSAM F5 S1B550 S1B550 S1B550 S1B550 FF039001

PF1=Help PF3=Return PF8=Fwd PF10=Left




See the BIM-FAQS/PCS Operations Guide for the following information aboutdataset history:

• Dataset Log Selection Panel input fields

• Dataset Audit Log contents


Viewing Event Forecasts

Introduction

You can view event forecasting reports for specific dates or event day keywords.On the forecast, you can see events that are scheduled and perform the followingfunctions:

• Edit or browse an event

• Display a job on the Event Job Edit Screen

• Display documentation for a job

Accessing Event Forecasting Information

To access event forecast information, perform the following steps:

1. Enter P at the command prompt from the Menu Index. The EventForecasting Selection Screen is displayed.

2. Enter a calendar, keyword, or date, press ENTER, and an Event ForecastingScreen for your selection is displayed. From this screen you can enter theaction codes X, J, or D to display additional information or performadditional event maintenance.


8–78 BIM-FAQS/PCS

Event Forecasting Selection Screen

The Event Forecasting Selection Screen enables authorized users to view eventforecasting reports. From the Event Forecasting Selection Screen, you can accessthe Event Forecasting Screen.

The following screen shows an example of the Event Forecasting SelectionScreen:

JOLFORC .P ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** BIM-FAQS/PCS ONLINE - Event Forecasting Selection **

Enter A or B on the command line or position the cursor on the appropriate selection and depress the enter key after specifying the associated forecasting argument.

Selection Criteria for Event Forecasting

A CALKEY - By calendar/keyword Cal ===> None Calendar/Keyword B DATE - By specific date Date ===> 98/02/18 YY/MM/DD

PF1=Help PF3=Return



Event Forecasting Screen

The Event Forecasting Screen shows an event forecasting report based on yourselection. The following screen shows an example of the Event ForecastingScreen with an event directory for a specific date:

JOLFORC .B ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===> ** BIM-FAQS/PCS ONLINE - Event Forecasting ** Event Forecast Report for Wednesday 98/02/18 Event Job/Cmd Start M S Cpuid PN Duration Description _ AFTERGRP PCSEVRP 11:09 A VSE BG 0:00:03 After the grp _ CARTTAPE &CP 08:45 D VSE TEST TAPE & CART _ GVART14 GSACCTM 00:00 D VSE14 Tst GVAR Stat 14 _ IMOD &AO 09:34 A VSE Z3 TST IMOD FRM PCS _ PCEXAM1 D 16:02 A VSE Z3 D RDR ON VERI _ TAPE &CP 10:16 A VSE Z3 TEST TAPE _ TESTMAN2 5 36:00 D VSE Test diff fings _ TESTMAN3 TESTABND 18:00 D VSE F5 0:00:04 TEST ABENDS _ TESTMAN4 D 01:13 A 039001 Z3 _ TESTMAN5 D 37:13 A VSE Z3 TEST DIFF FINGS _ TSTNOAUX &CMS 02:58 A VSE CM Tst RSTRE no Aux

Actions: A=Audit D=Doc G=Graph I=Refs J=Job N=Note X=Edit Z=Acct K=DSN PF1=Help PF3=Return PF6=/ST PF9=/SN PF12=Exit


See the BIM-FAQS/PCS Operations Guide for more details about:

• Selecting forecast reports

• Performing event maintenance from a forecast

• Using PF keys


8–80 BIM-FAQS/PCS

Checking Processing Periods

Introduction

With the Processing Period Verification Panel, you can:

• Determine the scheduling effects event day keywords will have

• Determine how event day keywords, easy day selections, holiday IDs, andcycle IDs work together for scheduling

• View holiday ID and cycle ID definitions

In other words, before defining an event using the various BIM-FAQS/PCSfeatures, you can set up "trial scenarios" on the Processing Period panels, and seethe effects certain event day keywords, easy day definitions, and holiday or cycledefinitions have on your schedule.

For example, if you've defined the event day keyword WORKDAYS, you can seewhen the workdays are valid for a particular month.

Accessing Processing Period Information

To access processing period information, perform the following steps:

1. Enter Y at the command prompt from the Menu Index. The ProcessingPeriod Verification Panel is displayed.

2. Enter values in the fields you'd like to verify and press ENTER. Dependingon where your cursor is, you'll get either of the following screens.

If the cursor is on the command prompt, a calendar for the current month isdisplayed. The days that are affected by the different field values aredisplayed. All field values work in combination.

If the cursor is on the Holiday Id or Cycle Id field, and an ID is specified,you'll get a list of dates defined for that ID.

The cursor must be in the first position of the field when you access thescreens, or type 'A' or 'B' from the command line.



Processing Period Verification Panel

The Processing Period Verification Panel enables you to enter values to help youverify the days on which events will occur.

From the Processing Period Verification Panel, you can access a particular monthto see the days on which events will occur based on the fields you've defined.You can also access holiday ID and cycle ID definitions (if the cursor is in the firstposition of either of those fields).

The following is an example of the Processing Period Verification Panel:

JOLDATE .Y ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

** Processing Period Verification Panel **

Event Day Keyword ===>

OR Event day and Easy day ===> _ (N/Y)

¬MTWTFSS Easy Day ===> ________

Holiday Action ===> _ Holiday Id ===> ___ Cycle Id ===> ___ Non Workday Action ===> _ Xdate Id ===> ___

PF1=Help PF3=Return


8–82 BIM-FAQS/PCS

Screen Resulting from Processing Period Verification Field Definitions

When you've defined fields on the Processing Period Verification Panel, and thecursor is anywhere other than the Holiday Id or the Cycle Id fields, press ENTER.A monthly screen is displayed that shows the days on which an event willprocess.

The following screen shows the results of defining the event day keywordWORKDAYS and the easy day definition excluding Wednesdays from theProcessing Period Verification Panel:

JOLDATE .0 ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===> Month of February 98 Sun Mon Tue Wed Thu Fri Sat

Event Day WORKDAYS 1 2 3 4 5 6 7

OR ¬MTWTFSS 8 9 10 11 12 13 14

Cycle 000 15 16 17 18 19 20 21

H W 22 23 24 25 26 27 28

Hol-ID 000

XDATE ___

PF1=Help PF3=Return PF7=Bwd PF8=Fwd



Holiday or Cycle ID Definition Screen

From the Processing Period Verification Panel, you can access this holiday screenby entering a value in the Holiday ID field, placing the cursor in the first positionof the field, and pressing ENTER. The following screen shows an example of theHoliday ID Definition Screen:

JOLCAL .g ** BIM-FAQS/PCS Online V5.1A ** ID=VSE.Q024===>

Holiday Id ===> 000 Desc ===> Default Holidays

**/12/25 ________ ________ ________ 98/09/07 ________ ________ ________ **/01/01 ________ ________ ________ 98/11/27 ________ ________ ________ **/07/06 ________ ________ ________ 98/11/26 ________ ________ ________ 98/05/25 ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________




See the BIM-FAQS/PCS Operations Guide for the following information aboutviewing processing periods:

• Processing period input field values

• Viewing monthly sample schedules



8–84 BIM-FAQS/PCS


Chapter 9Cross-Reference Reports

This chapter describes the batch cross-referencing tools CREF (a JCLEVNTcommand) and JCLREF.


This chapter describes two batch cross-referencing tools. The first, JCLCREF, letsyou analyze JCL members. The second, the CREF command of JCLEVNT, showsyou the events that share dependencies.

JCL Cross-Reference ReportsWhat Is a Cross-Reference Report?

JCL cross-reference reports contain a vertical list of items and a horizontal list ofassociated items. For example, a report might list programs and the membernames that execute them. Another report might list DTFs and the members thatcontain a DLBL or TLBL for those DTFs.To create JCL cross-reference reports, take the following steps:

1. Select the member to be processed using the REPORT command.

2. Select the type of cross-reference report using the OPT command.

3. Run the report using the JCLCREF utility.

JCL Cross-Reference Reports

9–2 BIM-FAQS/PCS

Report Types

JCLCREF can produce the following types of reports:

• PROC by containing member

• Job by containing member

• File ID by containing member

• DTF by containing member

• Assign by containing member

• EXEC by containing member

REPORT: Selecting Members

Introduction

The REPORT command selects cross-reference members to be processed by thereport generator. Report files are produced when the END statement isprocessed.

The REPORT function is performed in two stages:

• The first stage analyzes all statements in the specified members andgenerates files on the VIO PDS containing summary information.

• The second stage processes these report files and produces the actual reports.

Format ./ REPORT membname1,membname2,...

membname1 and membname2 are the names of the selected members.



OPT: Selecting Report Types

Introduction

The OPT command selects types of cross-reference reports to be processed by thereport generator. Report files are produced when the END statement isprocessed.

Also, use OPT to select display information.

Format./ OPT CREFxMY

ParameterThe CREFxMY parameter can be one or more of the following:

CREFxMY Function

CREFMMY Cross-references member by member

CREFPMY Cross-references phase by member

CREFDMY Cross-references DTF by member

CREFJMY Cross-references job by member

Files Created in VIO PDSDepending on which CREFxMY parameter you specify, the system will create thefollowing files:

The parameter Creates these files in the VIO PDS

CREFMMY JCLCREFICRFJCLSCANATMPJCLSCANETMP

CREFPMY JCLCREFICRFJCLSCANATMPJCLSCANETMP

CREFDMY JCLCREFICRFJCLSCANATMPJCLSCANETMPJCLSCANDTMPJCLSCANFTMP

Continued


9–4 BIM-FAQS/PCS

Continued

The parameter Creates these files in the VIO PDS

CREFJMY JCLCREFICRFJCLSCANATMPJCLSCANETMPJCLSCANJTMP

JCLCREF: Report Processing

Introduction

To process the report files, JCLCREF reads the files specified on controlstatements and prints the cross-reference listings. The HDR statement specifiesthe page heading. A FILE control statement identifies the PDS member to beused as input.

The JCLCREF member in the MON PDS produces a set of cross-reference listingsfor the entire library.

Report Format

Report headings identify the types of data summarized. The report data isalphabetized by the leftmost column.

A single report can contain several types of cross-reference information, whichare often presented in multiple orders.

Deleting the Input File

Use the DEL parameter to delete a file from your PDS after a report is generated.Use DEL also to remove the cross-reference work files from the VIO PDS.

The following example shows JCL that uses the DEL parameter:// EXEC JCLCREFFILE=JCLCREFICRF;DEL/*



Sample JCL

The following example shows the JCL required for the JCLCREF procedure. Foran explanation of this JCL, see the section directly following it.

// JOB JCLCREF GENERATE STANDARD CROSS REFERENCE REPORTS// ASSGN SYS009,SYSIPT// UPSI 10001110// EXEC PGM=JCLMAN./ ID PDS=MON (1)./ OPTION CREFMMY,CREFPMY,CREFDMY,CREFJMY (2)./ REPORT *.* (3)./ END// EXEC JCLCREF,SIZE=500k (4)HDR=**MEMBER BY CALLING MEMBER** (5)FILE=JCLCREFICRF;DEL (6)/*/ EXEC JCLCREF,SIZE=500kHDR=**JOB BY CONTAINING MEMBER**FILE=JCLSCANJTMP;DEL (7)/*// EXEC JCLCREF,SIZE=500kHDR=**FILE ID BY CONTAINING MEMBER**FILE=JCLSCANFTMP;DEL (8)/*// EXEC JCLCREF,SIZE=500kHDR=**DTF BY CONTAINING MEMBER**FILE=JCLSCANDTMP;DEL (9)/*// EXEC JCLCREF,SIZE=500kHDR=**ASSGN BY CONTAINING MEMBER**FILE=JCLSCANATMP;DEL (10)/*// EXEC JCLCREF,SIZE=500kHDR=**EXEC BY CONTAINING MEMBER**FILE=JCLSCANETMP;DEL (11)/*/&


9–6 BIM-FAQS/PCS

Explanation of JCL

The following list briefly explains the marked statements:

• Specifies the PDS for which the cross-reference report is generated.

• Specifies which cross-reference reports are produced.

• Directs JCLCREF to build the cross-reference files.

• Directs JCLCREF to execute the job that produces the printed cross-referencereports.

• Directs JCLCREF to print whatever is after the equal sign on the cross-reference report.

• Built by JCLCREF to hold information on members by calling members. TheDEL portion of the command deletes this work file once JCLCREF is doneproducing the report.

• Built by JCLCREF to hold information on PROCs by containing members.

• Built by JCLCREF to hold information on file ID by containing members.

• Built by JCLCREF to hold information on DTF by containing members.

• Built by JCLCREF to hold information on ASSGN by containing members.

• Built by JCLCREF to hold information on EXEC by containing members.



PROC by Containing Member

Introduction

This report summarizes information from PROC statements found in selectedmembers.

Format

The name in the left column is the member name from the PROC statement. Thenames listed to the right are members that contain a nested reference to themember in the left column.

Example

The following report indicates that a ./ PROC GSERV statement occurs inmembers FLEE and FLEERROR:**MEMBER BY CALLING MEMBER** GSERV FLEE FLEERROR

JOB by Containing Member

Introduction

This report summarizes information from POWER JECL JOB statements found inselected members.

Format

The name in the left column is the jobname. The names listed to the right of eachjob are the members that reference the job.

Example

The following report indicates that job JNM=BLGUPDT9 is found in membersBLGUPDT7 and BLGUPDT9:**JOB BY CONTAINING MEMBER** BLGUPDT9 BLGUPDT7 BLGUPDT9


9–8 BIM-FAQS/PCS

File ID by Containing Member

Introduction

This report summarizes the file ID information found on the // DLBL statement.

Format

The name in the left column is the file ID found on the // DLBL in selectedmembers. The names listed to the right of each file ID are the members thatreference the file ID.

Example

The following report indicates that file ID NICK.CL.TEST.OK.TO.DELETE isfound in members TESTJCL and NICKTEST:**FILE ID BY CONTAINING MEMBER** NICK.CL.TEST.OK.TO.DELETE TESTJCL NICKTEST

DTF by Containing Member

Introduction

This report summarizes information from TLBL/DLBL statements found inselected members.

Format

The name in the left column is the DTF name. A D is put in the eighth position ofthe name for DLBL statements. A T is put in the eighth position of the name forTLBL statements. The names listed to the right of each DTF are those membersthat reference the identified DTF.

Example

The following report indicates that DTF PCFILE is found on a DLBL (note the Din column 8). This DTF is found in the BACKUP, CONDPCIL, and VSE3BUmembers. The DTF IPT is found on a TLBL statement (note the T in column 8) inmember GSTAPEFL. **DTF BY CONTAINING MEMBER** PCFILE D BACKUP CONDPCIL VSE3BU IPT T GSTAPEFL



Assign by Containing Member

Introduction

This report summarizes information from ASSGN statements found in selectedmembers.

FormatThe name in the left column is the JCL member name, unless the first position is aperiod. The following table lists possible left-column names:

Name Explanation

.Vxxxxxx Volume reference via // ASSGN SYSxxx,...,VOL=xxxxxx

.DEVDISK DASD reference via // ASSGN SYSxxx,DISK,...

.CUA=CCC Unit reference via // ASSGN SYSxxx,CCC

membname Member name that contains items listed on right

All references are listed twice, once as type by containing member and once asmember by referenced item.

ExamplesThe following references are interpreted as shown:

If The report displays

VOL=VOLABC is referenced in anASSGN statement in membersMEMBER1 and MJUNK6

.VVOLABC MEMBER1 MJUNK6

X'014' is referenced in an ASSGNstatement in the member PAYROLL

.CUA=014 PAYROLL

DISK is referenced in an ASSGNstatement in member JOB4

.DEVDISK JOB4


9–10 BIM-FAQS/PCS

EXEC by Containing Member

Introduction

This report summarizes information from EXEC statements found in selectedmembers.

Format

The name in the left column is the program name. The names listed to the rightof each program are the members that reference the phase program.

Example

The following report indicates that the statement // EXEC CORGZ is found in thefollowing four members: FLICFBA3, FLIC3FBA, FLIC32, and JCLFFF2. **EXEC BY CONTAINING MEMBER** CORGZ FLICFBA3 FLIC3FBA FLIC32 JCLFFF2

Running Frequent Reports

Introduction

If cross-reference reports are run more than once a day, you can execute theJCLMAN utility once to create the appropriate files in the VIO PDS. Once thesefiles are created, you can run the JCLCREF program at will.

Example

You can run a cross-reference report that lists DTFs by containing member. Thefollowing sample JCL does not delete the JCLSCANDTMP file, since the DELparameter is not appended to the FILE control statement:// LIBDEF *,SEARCH=BIMLIB.PCS// EXEC JCLCREFHDR=**DTF BY CONTAINING MEMBER**FILE=JCLSCANDTMP/*

Since the file is not deleted, another report can be run later in the day.



CREF: Cross-Referencing Events

Introduction

CREF is useful if you want to view dependencies. The CREF command cross-references events based on their conditions. All of the following condition valuesare used for cross-referencing:

• VSE jobname

• POWER jobname

• POWER user field

• Event name

• Dataset name

• Resources

• Phase name

• Product name

• Work station

• Message ID

• PCS data members

• PCS global variables

FormatCREF [EVENT=mask] [DATE=yy/mm/dd] [BUILD]

Parameters

EVENT selects only those events that match the mask value. An asterisk (*)and/or a plus sign (+) create generic masks:

• A plus sign (+) represents an unconditional match on a specific character.

• An asterisk (*) represents an unconditional match on a group of characters.

DATE selects only those events matching the yy/mm/dd value in the currentevent file.

BUILD creates a cross-reference file to be used to display event relationshipsonline. To view the display, access either the current or master event file andenter I in the input field of the desired event. The BUILD parameter does notproduce a report.

If you do not specify any parameters, CREF will cross-reference all events in themaster event file.


9–12 BIM-FAQS/PCS

Sample Jobstream

The following sample CREF jobstream shows how to cross-reference allinventory events for the month of April 1997: // JOB CROSS REFERENCE INVENTORY EVENTS // LIBDEF PHASE,SEARCH=bimlib.pcs // EXEC JCLEVNT,SIZE=JCLEVNT CREF EVENT=INV* DATE=97/04/** /*/&

Sample Output

Each cross-reference report begins on a separate page. If a certain condition isnot found in the event file, a cross-reference report by that condition is notproduced.

The following sample output is produced by using CREF to cross-reference bymessage:** CROSS REFERENCE BY MESSAGE **0P69I INSTEVNTGLA010 EVENTTST INSTEVNT KEYSMSG0S12I TESTMODE TSTMODE1 TSTMODE2 TSTMODE3 TSTMODE4GJJ8301 TONYHOLD0S031 INSTEVNT KEYSMSG KEYSMSG100D FORMS REPGOOD00F FORMS REPGOOF1Q40A KEYSMSG KEYSMSG1 REPGOOD REPGOOF

The following sample output is produced by using CREF to cross-reference byevent names:** CROSS REFERENCE BY EVENT NAMES **BACKUVIO POSTMID POSTMID1DEMO1 DEMO2 DEMO3 DEMO4 DEMO5 DEMO6 DEMO7DEMO2 DEMO3 DEMO4 DEMO5 DEMO6 DEMO7DEMO3 DEMO4 DEMO5 DEMO6 DEMO7DEMO4 DEMO5 DEMO6 DEMO7DEMO5 DEMO6 DEMO7DEMO6 DEMO7INVNTRY1 INVNTRY2 INVMSG1 INVMSG2 INVMSG3 INVMON INVTHUINVTUE INVWEDINVNTRY2 INVMSG1 INVMSG2 INVMSG3 INVMON INVTHU INVTUEINVWEDPAYROLL1 ACCNT PAY2PREPAY PAYROLL1



The following sample output is produced by using CREF to cross-reference byvariable name:** CROSS REFERENCE BY VARIABLE NAME **&CONT EVTAUX&COUNT INVNTRY1 INVNTRY2&DEMOVAR DEMO1 DEMO2 DEMO4 DEMO6 DEMO7&EQ EVTAUX&GE EVTAUX&GT EVTAUX&INV INVNTRY1 INVNTRY2&VARAA SU0003&VARBB ZU300031&VAR1 OKMSG1 OKMSG2 OKMSG3&VAR2 OKMSG2 OKMSG3


9–14 BIM-FAQS/PCS


Chapter 10Using CMS

This chapter explains how you can use CMS to access BIM-FAQS/PCS onlinefeatures. You can use CMS to access BIM-FAQS/PCS when your VSE system isdown.

This chapter also shows how a native CMS REXX EXEC can retrieve or set BIM-FAQS/PCS global variables.

OverviewSupplied EXECs

The following CMS EXECs are supplied with your BIM-FAQS/PCS installationand must be customized:

• BCMI EXEC

• PCSCMS EXEC

• RXSETUP EXEC

Tailoring the EXECs

You should update the get_disk statements and do_filedef statements in thesupplied EXECs to reflect your MON, EVT, and VIO PDSs. Be sure you arelinked read-write to the disks on which the BIM-FAQS/PCS PDSs reside.

The BCIN interface does not require any VSE resources. For instance:

• VSE doesn't have to be active.

• VSE LOCK file is not required.

• VSE GETVIS is not used.

Overview

10–2 BIM-FAQS/PCS

For More InformationThe following table lists other manuals that describe the supplied EXECs:

For information about See the following manual

Installing the suppliedCMS EXECs

BIM-FAQS (ASO & PCS) Installation andInitialization Guide

Using the appropriateCMS programs andonline interface

BIM-FAQS/PCS Operations Guide

Tailoring the BCMI EXEC


Tailoring the BCMI EXECIntroduction

You should customize the BCMI EXEC get_disk and do_filedef statements to reflectyour library and machine name information.

Customizing StatementsTake the following steps to tailor your BCMI EXEC:

1. Make sure you have access to DCMSYSE LOADLIB, BIM$LDLB LOADLIB,and BIM$TICM MODULE.

2. Link and access the disks (get_disk) where the PDS files reside.

3. Update do_filedef statements for the PDS files.

Sample BCMI EXEC Statements

The following example shows the portion of the EXEC you should change in thesupplied BCMI EXEC. This is the minimum you need to change. Optionally, youcan specify other PDSs--for example, SYS$LOG.

. . . . . . . . .if Mach='TECHVSE' then do call get_disk 'TECHVSE 550 MW MOS' call get_disk 'TECHVSE 350 MW MDOS' call do_filedef 'SYS$VIO' 'SYSVC.V320.PERM.VIO.PDS' call do_filedef 'SYS$MON' 'SYSVC.V320.PERM.MON.PDS' call do_filedef 'SYS$EVT' 'SYSVC.V320.PERM.EVT.PDS' endif Mach='DEVVSE' then do call get_disk 'DEVVSE 550 MW MOS' call get_disk 'DEVVSE 350 MW MDOS' call do_filedef 'SYS$VIO' 'DEVVSE.SYS$VIO.PDS' call do_filedef 'SYS$MON' 'VSE3TST.VSE2TST.SHARED.MON.PDS' call do_filedef 'SYS$EVT' 'DEVVSE.SYS$EVT.PDS' end. . . . . . . .

Tailoring the BCMI EXEC

10–4 BIM-FAQS/PCS

Supplied CMS FilesThe following CMS files are supplied on the BIM-FAQS/PCS installation tapeand are related to using the BCMI interface:

File Function

BCMI EXEC Executes the BCMI utility. This file is a front end toBIM$TICM MODULE.

BIM$TICMMODULE

Manages the screen driver.

DCMSYSELOADLIB

Manages screens, accesses and updates PDSs, and accessesVSE libraries.

Accessing BIM-FAQS/PCS from CMS

The BCMI EXEC enables you to use a CMS interface to access BIM-FAQS/PCSfeatures. From the CMS Online/Editor Interface Screen, you can

• Enter the DCM-Systems editor

• Edit BIM-FAQS/PCS PDS members

• Enter BIM-FAQS/PCS Online

• Edit CMS members


For more information about using the BCIN CMS interface, see the BIM-FAQS/PCS Operations Guide.

Tailoring the PCSCMS EXEC


Tailoring the PCSCMS EXECIntroduction

You should customize the PCSCMS EXEC get_disk and do_filedef statements toreflect your library and machine name information.

Customizing StatementsTake the following steps to tailor the PCSCMS EXEC:

1. Make sure you have access to DCMSYSE LOADLIB and BIM$LDLBLOADLIB. You also must have access to the disk that contains the BIM-FAQS/PCS CMS EXECs and modules.

2. Link and access the disks (get_disk) where the PDS files reside.

3. Update do_filedef statements for the PDS files.

Sample PCSCMS EXEC Statements

The following example shows the portion of the EXEC you should change in thesupplied PCSCMS EXEC:

. . . . . . . . .if Mach='TECHVSE' then do call get_disk 'TECHVSE 550 MW MOS' call get_disk 'TECHVSE 350 MW MDOS' call do_filedef 'SYS$VIO' 'SYSVC.V320.PERM.VIO.PDS' call do_filedef 'SYS$MON' 'SYSVC.V320.PERM.MON.PDS' call do_filedef 'SYS$EVT' 'SYSVC.V320.PERM.EVT.PDS'

endif Mach='DEVVSE' then do call get_disk 'DEVVSE 550 MW MOS' call get_disk 'DEVVSE 350 MW MDOS' call do_filedef 'SYS$VIO' 'DEVVSE.SYS$VIO.PDS' call do_filedef 'SYS$MON' 'VSE3TST.VSE2TST.SHARED.MON.PDS' call do_filedef 'SYS$EVT' 'DEVVSE.SYS$EVT.PDS'

end. . . . . . . .

Tailoring the PCSCMS EXEC

10–6 BIM-FAQS/PCS

Accessing BIM-FAQS/PCS Batch Utilities

BIM-FAQS/PCS supplies the PCSCMS CMS EXEC to perform various BIM-FAQS/PCS functions natively under CMS.The following table lists the BIM-FAQS/PCS batch commands you can executefrom the PCSCMS EXEC:

Command Function

JCLEVNT Maintains events and runs event reports.

JCLMAN Manipulates the BIM-FAQS/PCS PDSs in the native CMSenvironment.

JCLCREF Runs cross-reference reports for the BIM-FAQS/PCS PDS.This command can be executed only after the ./ REPORTparameter of JCLMAN has been executed.

BIM$ADUT Produces reports about the BIM-FAQS/PCS audit file.

BIM$ACUT Produces reports about the BIM-FAQS/PCS account file.

BIM$DSUT Produces reports about BIM-FAQS/PCS dataset logging.

BIM$PUTL Executes DIRLIST and ANALYZE BIM$PUTL functions.

PCSCBAT Executes an BIM-FAQS/PCS REXX procedure under CMS.

PCSCPOST Posts an event from CMS.

PCSERPT Creates the event history summary reports.

PCSEVRP Creates user-definable event reports.

Input Source

The input data is from the IJSYSIN DATA A CMS file.

Output Source

Output is directed to wherever the FILEDEF statements specify IJSYSLS andIJSYSPH.


The BIM-FAQS/PCS batch utilities available under native CMS are described inmore detail in the BIM-FAQS/PCS Operations Guide.

RXPCS: Setting and Retrieving Global Variables


RXPCS: Setting and Retrieving Global VariablesIntroduction

A native CMS REXX EXEC can invoke the RXPCS module to:

• Retrieve BIM-FAQS/PCS global variables into the EXEC

• Set BIM-FAQS/PCS global variables

Format: Setting a Variable

To set an BIM-FAQS/PCS global variable, the EXEC should contain either of thefollowing lines, which use the built-in function PCS to call the RXPCS module.

Use this format to invoke RXPCS as a REXX function:x=PCS('PVAR',var,value)

Use this format to invoke RXPCS as an external call:CALL PCS 'PVAR' var value

In both cases, var is the BIM-FAQS/PCS global variable name, and value is thevalue of the variable.

Format: Retrieving a Variable

To retrieve a global variable, the EXEC should contain either of the followinglines.

Use this format to invoke RXPCS as a REXX function:x=PCS('GVAR',var)

Use this format to invoke RXPCS as an external call:CALL PCS 'GVAR' var

In both cases, var is the BIM-FAQS/PCS global variable name, and x is theparameter in which the value will be returned.

RXPCS: Setting and Retrieving Global Variables

10–8 BIM-FAQS/PCS

Sample RXPCS

The best way to understand RXPCS is to look at an example. The sample CMSEXEC called RXSAMP (shown below) does the following:

• Invokes the RXSETUP EXEC, which must be invoked once in any EXEC thatuses RXPCS, to establish links to the disks where the SYS$MON, SYS$EVT,and SYS$VIO PDS files are located.

• Sets the BIM-FAQS/PCS global variable COUNT to a value of 1.

• Extracts the COUNT variable value and displays it to the user.

/*********************************************************************//* BIM-FAQS/PCS RXSAMP EXEC *//* *//* Name: RXSAMP *//* Function: Sample CMS EXEC to extract/set BIM-FAQS/PCS global *//* variables. *//* Written: 9 FEB 1993 *//*********************************************************************/

call RXSETUP /* establish libraries and links */if result.=0 then exit result

call setvar 'COUNT' '1' /* set BIM-FAQS/PCS variable "COUNT"="1" */

call getvar 'COUNT' /* extract BIM-FAQS/PCS variable COUNT */say 'BIM-FAQS/PCS gvar COUNT='result

exit

setvar:arg var value .x=PCS('PVAR',var,value) /* set BIM-FAQS/PCS global variable */return

getvar:arg var .x=PCS('GVAR',var) /* get variable from BIM-FAQS/PCS */return x

RXSETUP

The CMS REXX EXEC called RXSETUP is needed to establish links to the diskswhere the SYS$MON, SYS$EVT, and SYS$VIO PDS files are located. A sampleRXSETUP EXEC is supplied with your BIM-FAQS/PCS installation and must becustomized for your site, as described earlier in this chapter.

Using CMS Server


Using CMS ServerIntroduction

Before you activate the CMS server machine, make sure the following conditionshave been met:

• The CMS server's user ID is defined. PCSSERV is the default. To change theuser ID, use the CMS Server Options Screen from the Configuration OptionsMenu.

• PCSSERV, or another defined server user ID, must have access to thefollowing CMS files:

• PCSSUB EXEC

• PCSSUB MODULE

• SUBPCS EXEC

• SUBPCS XEDIT

• BIM$LDLB LOADLIB

• DCMSYSE LOADLIB

• Both the PCSSUB and SUBPCS EXECs must be tailored so that the supplied'call do_filedef' and 'call get_disk' statements point at your installation'sMON, EVT, and VIO PDSs. If you have a SUBMIT XEDIT file, tailor it sothat it creates the file ZZARZZ ZZARZZ A3, rather than spooling themember back to the VSE guest. Rename the SUBMIT XEDIT file.

VM Requirements

To use VM, you must:

• Be a class G user

• Have a machine size of 3-4 megabytes

• Have a 191 minidisk with enough room to hold the largest JCL memberbeing submitted

Also, you must be able to link to the volumes where the MON, VIO, EVT, and alluser PDSs exist in MW mode. These are customized in the PCSSUB EXEC.

Using CMS Server

10–10 BIM-FAQS/PCS

Sample VM Directory

The following example shows a VM directory entry:USER PCSSERV PCSSERV 3M 3M GIPL CMS PARM AUTOCRCONSOLE 009 3215LINK MAINT 190 190 RRLINK MAINT 19D 19D RRLINK MAINT 19E 19E RRMDISK 191 3390 0400 0003 VMPK05

Defining CMS Server User IDTo add or change a CMS server user ID, complete the following steps:

1. Access the BIM-FAQS/PCS Online Menu Index.

2. Select option O, Configuration Options.

3. From the Configuration Options Menu Index, select option S, CMS ServerOptions.

4. On the CMS Server Options Screen, define server user IDs and which class tospool the JCL to from the server.

5. Reinitialize the scheduler.

Server Startup Command

The following command, issued from the CMS server machine, activates theCMS server interface:PCSSUB LOG

If you use AUTOLOG, place PCSSUB LOG in the PROFILE EXEC of the servermachine.

If you have BIM-ALERT/VSE installed, add the BIM-ALERT/VSE CMS serveruser ID to the command, using the following command format:PCSSUB LOG ALERT=serveruserid

Ending Server Processing

To stop CMS server processing, enter END on the server.


Chapter 11Using CICS

This chapter explains the requirements for using CICS with BIM-FAQS/PCS.


This chapter explains the CICS table entries required to:

• Start up the scheduler

• Access BIM-FAQS/PCS online

• Communicate to CICS via the JCLRCICS batch program or REXX

CICS to Startup Scheduler

You can run and execute the BIM-FAQS/PCS scheduler as a subtask of CICS.This is not recommended for VSE/ESA 1.3 and above.

CICS Online Interface

You can use a BCIN interface to access BIM-FAQS/PCS online and maintain PDSmembers.

CICS Communications

You can use several CICS functions with BIM-FAQS/PCS, both online and inbatch. With the JCLBCICS utility, you can:

• Open or close CICS files using a batch job or REXX IMOD

• Open or close DL/I databases using a batch job or REXX IMOD

• Pass CEMT commands to CICS

• Initiate CICS transactions

Security: BIM-FAQS/PCS security enables you to restrict use of the JCLBCICSutility completely, or to limit its use to only the OPEN and CLOSE functions.

Scheduler Startup: CICS Table Entries

11–2 BIM-FAQS/PCS

SYS$MON PDS Files

Both JCLRCICS and JCLBCICS use control files that are maintained in theSYS$MON PDS. Do not reformat the SYS$MON PDS while JCLRCICS orJCLBCICS is active.


For more information about using native CICS with BIM-FAQS/PCS, see theBIM-FAQS/PCS Operations Guide.

Scheduler Startup: CICS Table EntriesIntroduction

To subtask the scheduler, JCLSCHED, under CICS, you must add the PCSPLTprogram to the PCT, PPT, and PLT tables. This is not recommended forVSE/ESA 1.3 and above.

CICS PCT Entries

The following statement shows the required PCT entry:DFHPCT TYPE=ENTRY,TRANSID=PCSS,PROGRAM=PCSPLT

CICS PPT Entries

The following statement shows the required PPT entry:DFHPPT TYPE=ENTRY,PROGRAM=PCSPLT,PGMLANG=ASSEMBLER

CICS PLT Entries

The following statement shows the required PLT entry:DFHPLT TYPE=ENTRY,PROGRAM=PCSPLT,PGMLANG=ASSEMBLER

BIM$TICI: CICS Table Entries


BIM$TICI: CICS Table EntriesIntroduction

BIM$TICI is a CICS transaction that enables you to use BIM-FAQS/PCS onlineand edit PDS members.

Partition Storage

BIM$TICI executes BIM$TIDR, which enables the majority of the storage fromthe partition where BIM$TIDR is running, rather than from CICS.

To run BIM$TICI, the following entry is required for CICS PCT:DFHPCT TYPE=ENTRY,TRANSID=BCIN,PROGRAM=BIM$TICI

To run BIM$TICI, the following entry is required for CICS PPT:DFHPPT TYPE=ENTRY,PROGRAM=BIM$TICI,PGMLANG=ASSEMBLER,RES=YES

BIM$TIDR

BIM$TIDR is a program for accessing online applications in a CICS environmentthrough XPCC. Used in conjunction with BIM$TICI, BIM$TIDR enables you toavoid using CICS partition GETVIS. For more information on BIM$TIDR, see theBIM-GSS Installation and Utilities Guide.

Both BIM$TIDR and BIM$TICI require you to be running the FAQSMAINprogram. For information abut FAQSMAIN, see BIM-FAQS/ASO Online User'sGuide.

Defining Transactions Other Than BCIN

You can define transaction IDs other than BCIN to enable direct access to thattransaction's main screen, thus bypassing the BCIN menu.

To enable direct access to the PCS screen, you must enter the following for CICSPCT:DFHPCT TYPE=ENTRY,TRANSID=PCS,PROGRAM=BIM$TICI

To enable direct access to the PCS screen, you must enter the following for CICSPPT:DFHPPT TYPE=ENTRY,PROGRAM=BIM$TICI,PGMLANG=ASSEMBLER,RES=YES

Partition Storage: To run a transaction using primarily partition storage, changethe program name to BIM$TICI in the PCT and PPT entries.

Communications: CICS Table Entries

11–4 BIM-FAQS/PCS

Communications: CICS Table EntriesIntroduction

JCLBCICS requires CICS 1.6 or above. You must add two entries to the PCT andfive to the PPT.

You need to add LIBDEF statements to all partitions when updating table entries.

CICS PCT Entries

The following statements show the required PCT entries:DFHPCT TYPE=ENTRY,TRANSID=JCLR,PROGRAM=JCLRCICSDFHPCT TYPE=ENTRY,TRANSID=JCLS,PROGRAM=JCLSCICSDFHPCT TYPE=ENTRY,TRANSID=JCLX,PROGRAM=JCLXCICS,TWASIZE=0

Note: The TWASIZE for JCLX should correspond with the largest TWASIZE ofthe transactions that will be started via the STARTT function. JCLX is needed forCICS 2.2 and above.

CICS PPT Entries

The following statements show the required PPT requirements:DFHPPT TYPE=ENTRY,PROGRAM=JCLACICS,PGMLANG=ASSEMBLERDFHPPT TYPE=ENTRY,PROGRAM=JCLCCICS,PGMLANG=ASSEMBLERDFHPPT TYPE=ENTRY,PROGRAM=JCLRCICS,PGMLANG=ASSEMBLERDFHPPT TYPE=ENTRY,PROGRAM=JCLSCICS,PGMLANG=ASSEMBLERDFHPPT TYPE=ENTRY,PROGRAM=JCLTCICS,PGMLANG=ASSEMBLERDFHPPT TYPE=ENTRY,PROGRAM=JCLXCICS,PGMLANG=ASSEMBLER

Note: JCLXCICS is needed for CICS 2.2 and above.

Communications: CICS Table Entries


CICS PLT Entries

Starting JCLRCICS: The following PLT entry is required in the startup PLT(PLTPI):DFHPLT TYPE=ENTRY,PROGRAM=JCLACICS

To automatically start JCLRCICS at CICS startup, add the JCLACICS entry to thePPT and PLT. This attaches the JCLRCICS program and eliminates the need toexecute the JCLS transaction. The JCLS transaction enables you to manually startand stop the JCLRCICS program.

Shutting Down JCLRCICS: The following PLT entry can be used in theshutdown PLT (PLTSD):DFHPLT TYPE=ENTRY,PROGRAM=JCLTCICS

JCLTCICS automatically shuts down JCLRCICS when CICS shuts down.However, JCLRCICS detects when CICS shuts down and terminatesautomatically.

Considerations

After installing any of the CICS programs used with JCLRCICS (JCLxCICS), andwhen all the CICS table changes have been made, you should reinitialize CICS.

If using CICS RDO (resource definition online), you can install the definitionsand enable the JCLRCICS programs with the JCLS online transaction. To do this,make sure the BIM-FAQS/PCS library is already in the LIBDEF search chain.

GETVIS Requirements

You must have 40K of CICS partition GETVIS for running JCLRCICS.

JCLRCICS Programs

11–6 BIM-FAQS/PCS

JCLRCICS ProgramsJCLACICS

JCLACICS is the PLT startup program to initiate JCLRCICS. JCLACICS cleansup any files left over from JCLRCICS after a CICS crash or when CICS terminateswith an immediate shutdown.

JCLCCICS

JCLCCICS is the CICS program that issues CEMT commands. This programmust be defined in the PPT.

JCLRCICS

JCLRCICS is a continuous CICS program that is posted by JCLRTASK whencommands are ready to be executed. The JCLRCICS program opens and closesfiles and passes the CEMT commands to JCLCCICS on behalf of JCLBCICS andREXX IMODs.

JCLRCICS writes messages about everything it does to the CSMT transient dataqueue. When CICS shuts down, all JCLRCICS activity can be printed with theCICS shutdown statistics.

JCLRTASK

The JCLRTASK subtask of CICS communicates with JCLBCICS and the REXXportion of JCLRCICS. JCLRTASK performs all I/Os to the BIM-FAQS/PCS PDS.Since JCLRTASK is a subtask of CICS, it competes with CICS resources.

JCLSCICS

JCLSCICS is a CICS program that can manually initiate or terminate theJCLRCICS program. JCLSCICS is designed as a precaution in case JCLACICS isnot included in the PLT. JCLSCICS checks the status of JCLRCICS before it triesto activate or deactivate JCLRCICS.

To determine whether JCLRCICS is active, JCLSCICS checks a file in the PDS.This file is not deleted if CICS abends or CICS SHUTDOWN is performedwithout JCLTCICS being invoked. If JCLSCICS is used to activate JCLRCICSafter either of the two previous circumstances, JCLSCICS responds with themessage that JCLRCICS is already active. At that point, you can tell JCLSCICS todeactivate JCLRCICS. After two minutes JCLSCICS cleans up any existing filesleft by JCLRCICS, and you can use JCLSCICS to activate JCLRCICS.

For More Information: The JCLS transaction is provided to enable you to startand stop JCLRCICS using an online screen. For more information, see the BIM-FAQS/PCS Operations Guide.

JCLRCICS Programs


JCLTCICS

JCLTCICS is the PLT shutdown program that deactivates JCLRCICS and causesJCLRCICS to delete any of its communications files in the PDS. JCLTCICS is notrequired, since JCLRCICS can detect when CICS shuts down.

JCLTCICS is used only if a PLT entry for JCLTCICS was defined. You can alsouse JCLSCICS to terminate JCLRCICS before CICS is shut down. In this instance,JCLSCICS causes JCLRCICS to delete all of its files in the PDS.

JCLXCICS

JCLXCICS is the CICS program that starts a simple-terminal transaction.JCLXCICS is needed for CICS 2.2 and above. This program must be defined inthe PPT.

JCLRCICS Programs

11–8 BIM-FAQS/PCS


Chapter 12Submitting Commands in a BatchJobstream

This chapter explains the JCLXCU utility.


With the JCLXCU utility, you can:

• Issue VSE/POWER, VM CP, and VSE/Operator commands in a batchjobstream

• Use additional commands to control user-specified VSE resources with theDTL, LOCK, and UNLOCK macros

• Enable the BIM-FAQS/PCS system and job exit with JCLXCU JCLcommands

• Read input parameters, pass them to the appropriate system, and reportreturn codes (if any)

If executed from JCL, JCLXCU reads input from SYSIPT. If executed from theoperator console, JCLXCU reads input from SYSLOG.

JCLXCU Control Statements

12–2 BIM-FAQS/PCS

JCLXCU Control StatementsStatement Formats

Statement Format Function of Statement./ ID USER=user ID Specifies the user ID to use for operator commands. If ./ ID is

omitted, the user ID uses the BATUSER value defined inconfiguration.

CP VMcommand Passes statements with CP in columns 1-2 to VM through thediagnose interface. This function is not supported under ICCF.

ENABLELOAD=Y|N,LOG=Y|N,JOBX=$JOBEX0n,DSN=Y|N,DSNLOG=Y|N,DESKTOP=name

Enables the following:

LOAD When BIM-FAQS/PCS is enabled, the event schedulewill be reloaded. The default is Y.

LOG Enables job account logging. The default is Y.

JOBX This only applies to users that have VSE/ESA 1.2 orhigher and that use the JOBEXIT table. This parameteridentifies which of the ten job exits, specified in the JOBEXITtable, BIM-FAQS/PCS will precede. The default is $JOBEX00.

DSN Enables dataset detection and activates $$BOPEN and$$BCLOSE hooks. The default is Y.

DSNLOG Enables dataset logging to the PDS. The default isY.

DESKTOP This applies to users that have CA-Prevail/XP-Manager (PSK) and want BIM-FAQS/PCS event status routedto a remote destination. This parameter identifies the GMFname where event status is routed. The default GMF name isDESKTOP. By default, this statement is not enabled.

DISABLE Disables BIM-FAQS/PCS hooks, $JOBEXIT, $JOBACCT,$$BOPEN, $$BCLOSE, and disables account logging.

LOADSVA pgm Loads the appropriate SVA phases.

LOCK resourcename

UNLOCK resourcename

Controls VSE-named resources. Resources are enqueued withthe LOCK macro and released with the UNLOCK macro.Resources are enqueued past the end of a step and areunconditionally released at the end of VSE JOB (/&).

LOG

LOG OFF

Controls BIM-FAQS/PCS PDS job account logging.

GEN gencommand Passes batch job generation commands to the scheduler.Continued

JCLXCU Control Statements


Continued

Statement Format Function of StatementCANCEL Issues a CANCEL ALL macro.

OP opcommand Passes operator commands to ASYNOC.

A RDR,*SEC,CLASS=A

2 CEMT P SHUT,I

Passes 1-character commands to POWER through CTLSPOOL:A, C, D, H, I, L, R, X. If the full POWER command is supplied,it is passed to ASYNOC and is treated as an operatorcommand. POWER responses are displayed on the console.

SUB cmsmember Submits the specified job to run on the CMS server.

DMAXRC value Sets the default maximum return code used for an event'sWHEN condition. value must be four digits.

DABEND value Sets the default abend code used with job accounting. valuemust be four digits.

DESKTOP ON[,name]

DESKTOP OFF

Controls communications with CA-Prevail/XP-Manager (PSK).name is the GMF name where BIM-FAQS/PCS event status isrouted. The default GMF name is DESKTOP.

Uses of JCLXCU

You can use JCLXCU in one of the following ways:

• To start BIM-FAQS/PCS and the job exit.

• To update a file only after the edit job completes successfully. The C=*parameter runs the update in the current partition.

• To generate DLI batch jobs when CICS is taken down. JCLXCU executionfollows the CICS startup JCL. Use this technique if you want to run a job inanother partition when a step or job in the current partition completes.

If JCLXCU is auto-scheduled, to issue a POWER command that releases allsecond- or third-shift work; or to issue an operator command that shuts downCICS.

If JCLXCU is internal to the user run, to route a printout to a remote site after acritical step has successfully completed.

If JCLXCU is in a user run, to route job output between virtual machines.

To control multiple jobs in multiple partitions released by a single job generationcommand via the VSE lock facility.

JCLXCU Examples

12–4 BIM-FAQS/PCS

JCLXCU ExamplesIntroduction

The following section shows examples of how you can use JCLXCU controlstatements.

JCLXCU GEN Example

Use the batch utility to perform any batch job generation (GEN) command inbatch.

The following example generates the PAYROLL jobstream using the suppliedparameters. The resulting job runs as class 6. // EXEC JCLXCU GEN PAYROLL,C=6,&DAY=MONDAY,&TRIAL=YES /*

POWER Command Example

All POWER commands that are supported for CTLSPOOL are supported forJCLXCU.

The following example shows how to release or route a printout after a criticalsection of a job has completed: // EXEC JCLXCU A LST,PAYROLLX,CLASS=B,DISP=D,COPY=2 R RDR,PAYROLLY /*

The above example changes and releases a printout and also allows the nextportion of a job to start. Use this to control multiprogramming within ajobstream.

Operator Command Example

All operator commands are supported by JCLXCU, which passes the commandsto ASYNOC. You can use an auto-scheduled JCLXCU job to shut down CICS.

The following example passes the command to ASYNOC, and it tells the CICSthat's executing in the F2 partition to shut down: // EXEC JCLXCU ./ ID USER=ADMIN 2 CEMT P SHUT,Y /*

You can secure the OP command with system configuration.

JCLXCU Examples


VM CP Command Example

In a virtual machine environment, it is frequently useful to communicate thecompletion of a job between virtual machines.

The following example sends a message to another virtual machine and links to adisk owned by that system: // EXEC JCLXCU CP MSG PRODVSE 'NOW ACCESSING LIBRARY' CP LINK PRODVSE 150 158 /*

JCLXCU Examples

12–6 BIM-FAQS/PCS

Implementation Guide A–1

Appendix APDSIO: Allowing Application ProgramsAccess to PDS

OverviewThis appendix covers the PDSIO routine.

Introduction

Application programs (including CICS) can use the PDSIO routine provided withBIM-FAQS/PCS to perform various functions on the BIM-FAQS/PCS PDS(partitioned dataset). The application programs can:

• Request that an IMOD be run

• Set or retrieve a PCS global variable

• Read or write to a PDS member

• Determine whether a PDS member exists

• Display the PDS directory

For JCLUPUT Users

PDSIO is an improvement over JCLUPUT, since PDSIO allows you to generatejobs with CICS, while JCLUPUT uses batch processing.

Example: When to Use PDSIO

The PDSIO routine is useful if a system programmer wants to create a CICSapplication program that executes a job, based on input that a user enters from aterminal. For example, if a user enters a request to run a specific IMOD, theapplication program can call PDSIO to execute the IMOD and return a valuefrom the IMOD.

Overview

A–2 BIM-FAQS/PCS

Calling the PDSIO Routine

PDSIO can be called from a user program written in COBOL, PL/I (using theASSEM interface), assembler, or any other language that supports "standard"system 370/390 calling conventions.

The member PDSIO.OBJ is included in the BIM-FAQS/PCS installation libraryand must be linked in with the application program that calls it.

Sample COBOL Application Program Using PDSIO

Following is an example of a COBOL application program that calls the PDSIOroutine to set the global variable COBVAR to 5:CBL APOST,CLIST,SUPMAP,LIB IDENTIFICATION DIVISION. PROGRAM-ID. SAMPLE. ENVIRONMENT DIVISION. DATA DIVISION. WORKING-STORAGE SECTION. * COPY PPDSPARM. * 01 WORKA PIC X(1024). EJECT PROCEDURE DIVISION. PERFORM CREATE-GLOBAL-VARIABLE. STOP RUN.

CREATE-GLOBAL-VARIABLE.

MOVE 'PVAR' TO PPDSFUNC. MOVE 'COBVAR' TO PPDSVARN. MOVE 5 TO PPDSREC. CALL 'PDSIO' USING PPDSFUNC, WORKA. IF PSTATUS NOT EQUAL 'OK' PERFORM PDSIO-ERROR-ROUTINE.

PDSIO-ERROR-ROUTINE. DISPLAY 'PDSIO ERROR; STATUS=', PSTATUS UPON CONSOLE.

PDSIO Parameters


PDSIO ParametersIntroduction

Notice that, before the sample application program could call PDSIO, it had to setup several parameters. Those parameters are described in this section.

Parameter Areas

The application program must pass two parameter areas to PDSIO:

• A 312-byte parameter area mapped out into specific parameters in theformat.

• A 1K work area

If PDSIO is called from an assembler program, register R13 must point to a 9-double-word save area.

PPDSFUNC Parameter Functions

The first parameter passed from the application program to PDSIO is thePPDSFUNC parameter, which describes the function that PDSIO is to perform.The application program passes one of the following function names inPPDSFUNC:

Function Explanation

CLOS Close the interface after reading or writing to a PDS member

DELE Delete a member in the PDS

EXEC Run an IMOD and return result to user

FIND Determine whether a PDS member exists

GEN Submit the member contained in PPDSREC

GVAR Get the value of a PCS global variable

IMOD Tell BIM-FAQS/ASO to run an IMOD. Note that since thisfunction only starts execution of the IMOD, its return code doesnot indicate whether the IMOD completed successfully.

OPEI Open a PDS member for input

OPEO Open a PDS member for output

PVAR Set an BIM-FAQS/PCS global variable

READ Retrieve the next record from a PDS member

WRIT Write a record to a PDS member

PDSIO Parameters

A–4 BIM-FAQS/PCS

Other Parameter Areas

The application program must also set the other parameters required by PDSIOto the following values:

Parameter When Used with Function Contains

PAPDSREC All functions Address of real record(set and usedinternally)

PPDSUSER All functions User ID

PPDSNAME OPEI, OPEO, FIND, DELE,GEN

PDS ID

PPDSMEMB OPEI, OPEO, FIND, DELE,GEN

PDS member name

EXEC, IMOD Name of IMOD

PPDSMEMT OPEI, OPEO, FIND, DELE,GEN

PDS member type

PPDSREC WRIT Record to be writtento the PDS member

EXEC Arguments passed toIMOD

READ, EXEC, IMOD Data passed from PDSor IMOD, or errormessage

GVAR, PVAR Value of globalvariable, or errormessage

PPDSVARN GVAR, PVAR Variable name

PDSBUFF All functions Internal buffers

Note: Not all parameters are required for all PDSIO functions. Most functionsrequire that only a few other parameters be set.

PDSIO Parameters


PPDSPARM Source Member

The PPDSPARM source member is included in the BIM-FAQS/PCS installationlibrary under the names PPDSPARM.A (for assembler) and PPDSPARM.C (forCOBOL).

PPDSPARM shows the format required in your application program whensetting up PDSIO parameters. You can copy the parts of its setup that you needinto your application program source.

PPDSPARM.A Assembler Source

The PPDSPARM.A (assembler) layout is shown below:PPDSFUNC DS CL4 Function to perform* OPEI Open input* opei Open input (any member)* READ Read next card* OPEO Open output* opeo Open output (any member)* FIND Determine if member exists* WRIT Write record* writ Write record from address* CLOS Close member* CLOP Close member FOR OUTPUT AT POST* GEN GENERATE A MEMBER* IMOD Run an IMOD through ASO* EXEC Run an IMOD and get result back* PVAR Set a global variable* GVAR Get a global variablePAPDSREC DS A Address of real recordPPDSUSER DS CL8 User namePPDSNAME DS CL3 Pds namePPDSMEMB DS CL8 Pds member namePPDSMEMT DS CL3 PDS member typePPDSREC DS CL80 Record without control infoPSTATUS DS CL2 Status* C'EF' R15=4 End of file* C'NF' R15=4 Not found* C'OK' R15=0 Function completed successfully* C'SE' R15=8 Security violation* C'TR' R15=2 Record in buffer is truncated* C'PD' R15=X'Dxx' PDS error r15 contains X'Dxx'* C'CD' R15=rc CDLOAD error R15 has rc* C'IF' R15=8 Invalid function call* C'ER' Error from GSAOGEMPPDSVARN DS CL16 PCS variable name ORG PPDSVARN Redefine areaPPDSBUFF DS CL200 Internal buffers and I/O areas ORG ,

PDSIO Parameters

A–6 BIM-FAQS/PCS

PPDSPARM.C COBOL Source

The PPDSPARM.C (COBOL) layout is shown below: 01 PPDSPARM. 05 PPDSFUNC PIC X(4) VALUE SPACES.* OPEI Open input* opei Open input (any member)* READ Read next card* OPEO Open output* opeo Open output (any member)* FIND Determine if member exists* WRIT Write record* writ Write record from address* CLOS Close member* CLOP Close member FOR OUTPUT AT POST* GEN GENERATE A MEMBER* IMOD Run an IMOD through ASO* EXEC Run an IMOD and get result back* PVAR Set a global variable* GVAR Get a global variable 05 PAPDSREC PIC S9(8) COMP VALUE ZERO. 05 PPDSUSER PIC X(8) VALUE SPACES. 05 PPDSNAME PIC X(3) VALUE SPACES. 05 PPDSMEMB PIC X(8) VALUE SPACES. 05 PPDSMEMT PIC X(3) VALUE SPACES. 05 PPDSREC PIC X(80) VALUE SPACES. 05 PSTATUS PIC X(2) VALUE SPACES.* 'EF' R15=4 END OF FILE* 'NF' R15=4 NOT FOUND* 'OK' R15=0 FUNCTION COMPLETED SUCCESSFULLY* 'SE' R15=8 SECURITY VIOLATION* 'TR' R15=2 RECORD IN BUFFER IS TRUNCATED* 'PD' R15=X'DXX' PDS ERROR R15 CONTAINS X'DXX'* 'CD' R15=RC CDLOAD ERROR R15 HAS RC* 'IF' R15=8 INVALID FUNCTION CALL* 'ER' ERROR FROM GSAOGEM 05 PDSBUFF PIC X(200). 05 FILLER REDEFINES PDSBUFF. 10 PPDSVARN PIC X(16). 10 FILLER PIC X(184).

Using PDSIO Functions



Opening a Member for Input: OPEI

Setting ValuesBefore an application can read a PDS member, the member must be opened forinput. Set the following values in your application program; then call PDSIO.

Parameter Must Contain

PPDSFUNC OPEI

PPDSNAME 3-character PDS ID

PPDSMEMB PDS member name, padded on the right with blanks

PPDSMEMT 3-character PDS member type

Return Values in PSTATUS

PDSIO returns one of the following PSTATUS values to your applicationprogram:

Value Explanation

OK The member is found, and PPDSREC contains the first record ofthe member.

TR The member is found, but PPDSREC contains only the first 80bytes of the record.

NF The member is not found.

Other An error occurred.


A–8 BIM-FAQS/PCS

Example

The following example shows how part of an assembler program sets parametersand then calls PDSIO to open a PDS member for input:OPEI DS 0H Open member for input MVC PPDSNAME(3),=C'MON' Access the SYS$MON PDS MVC PPDSMEMB(8),=CL8'memname' Member name MVC PPDSMEMT(3),=CL3'typ' Member type MVC PPDSFUNC,=C'OPEI' Indicate to open member for input CALL PDSIO,(PPDSFUNC,WORKA) CLC PSTATUS(2),=C'OK' Q. did we open O.K BE PROCESS Yes - process record CLC PSTATUS(2),=C'TR' Q. did we open O.K and record truncated BE TRUNC Yes - process truncated record CLC PSTATUS(2),=C'NF' Q. member not found BE NOTFND Yes - indicate member not found B ERROR Otherwise - error



Reading a PDS Member (Get Next Record): READ

Setting ValuesOnce a PDS member has been opened for input, the application program canretrieve subsequent records. Set the following value in your applicationprogram; then call PDSIO.


PPDSFUNC READ


PDSIO returns one of the following values to your application program in theparameter PSTATUS:

PSTATUS Value Explanation

OK The full record has been returned in PPDSREC.

TR PPDSREC contains only the first 80 bytes of the record.

EF There are no more records to be read, and PPDSREChas nothing in it.


Example

The following example shows how part of an assembler program sets parametersand then calls PDSIO to read a PDS record:READ DS 0H Read a PDS member MVC PPDSFUNC,=C'READ' Indicate to read next record CALL PDSIO,(PPDSFUNC,WORKA) CLC PSTATUS(2),=C'OK' Q. did we get record BE PROCESS Yes - do something with it CLC PSTATUS(2),=C'TR' Q. did we get truncated record BE TRUNC Yes - process truncated record CLC PSTATUS(2),=C'EF' Q. end of file BE CLOS Yes - close the interface B ERROR Otherwise - error


A–10 BIM-FAQS/PCS

Closing a PDS Member After Reading: CLOS

Setting ValuesOnce a PDS member has been read, or if the read process should be terminatedprematurely, the application program must close the PDS member. Set thefollowing value in your application program; then call PDSIO.


PPDSFUNC CLOS

Note: The application must issue the close function before accessing anothermember using the same parameter list. Multiple members can be accessed, aslong as each member has its own copy of both work areas.


PDSIO returns one of the following PSTATUS values to your applicationprogram:

Value Explanation

OK The member closed successfully.

Other An error occurred. PDSIO automatically closes the member.



Opening a Member for Output: OPEO

Setting ValuesBefore an application can write to a PDS member, the member must be openedfor output. Set the following values in your application program; then callPDSIO.


PPDSFUNC OPEO







OK The member was opened for output successfully.


Example

The following example shows how part of an assembler program sets parametersand then calls PDSIO to open a member for output:OPEO DS 0H Open member for output MVC PPDSNAME(3),=C'MON' Access the SYS$MON PDS MVC PPDSMEMB(8),=CL8'memname' Member name MVC PPDSMEMT(3),=CL3'typ' Member type MVC PPDSFUNC,=C'OPEO' Indicate to open member for output CALL PDSIO,(PPDSFUNC,WORKA) CLC PSTATUS(2),=C'OK' Q. did we open O.K BE OPENED Yes - continue on with writing B ERROR Otherwise - error


A–12 BIM-FAQS/PCS

Writing to a PDS Member: WRIT

Setting ValuesAfter a PDS member has been opened for output, an application program canadd records to the member. Set the following values in your applicationprogram; then call PDSIO.


PPDSFUNC WRIT

PPDSREC The record to be written, padded on the right withblanks if it is less than 80 bytes long




OK The record was written successfully.


Example

The following example shows how part of an assembler program sets parametersand then calls PDSIO to write records to a PDS member:WRIT DS 0H Write to a PDS member MVC PPDSFUNC,=C'WRIT' Indicate to write record from PPDSREC MVC PPDSREC(80),=CL80'record' Move in record to be written CALL PDSIO,(PPDSFUNC,WORKA) CLC PSTATUS(2),=C'OK' Q. did we write the record BNE WERROR No - exit with error



Closing a PDS Member: CLOS

Setting ValuesAfter an application program writes to a PDS member, the program must set thefollowing value and call PDSIO to actually create the member.


PPDSFUNC CLOS

Note: The close function must be issued before the application program accessesanother member using the same parameter list. The application can accessmultiple members, as long as each member has its own copy of both work areas.




OK The member was closed successfully.

Other An error occurred. PDSIO automatically closes themember.

Example

The following example shows how part of an assembler program sets parametersand then calls PDSIO to close a PDS member:CLOS DS 0H Close a PDS member MVC PPDSFUNC,=C'CLOS' Indicate to close the interface CALL PDSIO,(PPDSFUNC,WORKA) CLC PSTATUS(2),=C'OK' Q. did close go O.K BE DONE Yes - we are done B ERROR Otherwise - error


A–14 BIM-FAQS/PCS

Deleting a PDS Member: DELE

Setting ValuesTo delete a PDS member, set the following values in your application program;then call PDSIO.


PPDSFUNC DELE







OK The member was deleted successfully.

Other An error occurred during delete processing.

Example

The following example shows how part of an assembler program sets parametersand then calls PDSIO to delete a PDS member:DELE DS 0H Delete a PDS member MVC PPDSNAME(3),=C'MON' Access the SYS$MON PDS MVC PPDSMEMB(8),=CL8'memname' Member name MVC PPDSMEMT(3),=CL3'typ' Member type MVC PPDSFUNC,=C'DELE' Indicate to delete the interface CALL PDSIO,(PPDSFUNC,WORKA) CLC PSTATUS(2),=C'OK' Q. did delete go O.K. BE DONE Yes - we are done B ERROR Otherwise - error



Closing PDS Member for Output and Posting DATA= Condition: CLOP

Setting ValuesTo create a PDS member and have the PCS scheduler satisfy all event WHENDATA= conditions for that member, your application program must set thefollowing value and call PDSIO.


PPDSFUNC CLOP

Note: The close function must be issued before the application program accessesanother member using the same parameter list. The application can accessmultiple members, as long as each member has its own copy of both work areas.




OK The member was closed successfully.

Other An error occurred during close processing. PDSIOautomatically closes the member.

Example

The following example shows how part of an assembler program sets parametersand then calls PDSIO to close a PDS member for output and post the DATA=condition:CLOP DS 0H Close member and post MVC PPDSFUNC,=C'CLOP' Indicate to close and satisfy CALL PDSIO,(PPDSFUNC,WORKA) CLC PSTATUS(2),=C'OK' Q. did close go O.K BE DONE Yes - we are done B ERROR Otherwise - error


A–16 BIM-FAQS/PCS

Determining Whether a Member Exists: FIND

Setting ValuesTo check whether a specific PDS member exists, set the following values in yourapplication program; then call PDSIO.


PPDSFUNC FIND







OK The member exists in the PDS.

NF The member does not exist in the PDS.

Example

The following example shows how part of an assembler program sets parametersand then calls PDSIO to determine whether the PDS member exists:FIND DS 0H Determine if member exists MVC PPDSNAME(3),=C'MON' Access the SYS$MON PDS MVC PPDSMEMB(8),=CL8'memname' Member name MVC PPDSMEMT(3),=CL3'typ' Member type MVC PPDSFUNC,=C'FIND' Indicate to find member CALL PDSIO,(PPDSFUNC,WORKA) CLC PSTATUS(2),=C'OK' Q. does member exist BE FOUND Yes - we found it CLC PSTATUS(2),=C'NF' Q. member not found BE NOTFND Yes - indicate member not found B ERROR Otherwise - error



Submitting a Member: GEN

Setting Values

To submit a member to POWER, set the following values in your applicationprogram; then call PDSIO.


PPDSFUNC GEN


PPDSREC BIM-FAQS/PCS format command for schedulingmembers


Note: The GEN function does not need to be preceded by an OPEN call, and itdoes not have to be followed by a CLOS call.




OK The member was submitted successfully to POWER.


Example

The following example shows how part of an assembler program sets parametersand then calls PDSIO to submit a PDS member to POWER:GEN DS 0H Determine if member exists MVC PPDSREC( ),=C'memname,&parm1=val....' MVC PPDSFUNC,=C'GEN ' Indicate to submit the member CALL PDSIO,(PPDSFUNC,WORKA) CLC PSTATUS(2),=C'OK' Q. did we submit it BE OK Yes - continue B ERROR Otherwise - error


A–18 BIM-FAQS/PCS

Getting a Directory List

Introduction

An application program can get a directory list by using the OPEI, READ, andCLOS functions.

Setting Values for OPEI

For the OPEI function, set the following values in your application program; thencall PDSIO.


PPDSFUNC OPEI

PPDSMEMB ........ (8 hexadecimal '4B's)

PPDSMEMT 'DIR'

Setting Values for READ

For the READ function, set the following values in your application program;then call PDSIO.


PPDSFUNC READ

Return Values for READ

After the READ function is complete, PDSIO returns one of the following valuesto your application program in the parameter PSTATUS:


EF End of file.

OK Information has been returned in PPDSREC (seePPDSREC format, below).


The application should continue reading the PDS until it reaches end-of-file (EF).Then the program should use the CLOS function to close the PDS.



Setting Values for CLOS

For the CLOS function, set the following values in your application program;then call PDSIO.


PPDSFUNC CLOS

PPDSREC Format

When the PDS has been read, your application program's PPDSREC field willcontain the directory information, in the following format: MEMNAME DS CL8 member name MEMTYPE DS CL3 member type DS CL1 unused NRECS DS CL5 number of records DS CL1 unused NBLCKS DS CL3 number of blocks


A–20 BIM-FAQS/PCS

Executing an IMOD Synchronously: EXEC

Setting ValuesTo execute an IMOD and to be able to look at what the IMOD returns, set thefollowing values in your application program; then call PDSIO.


PPDSFUNC EXEC.

PPDSMEMB Name of the IMOD.

PPDSREC Any arguments to be passed to the IMOD. If theIMOD returns any data, it will also be in PPDSREC.

Note: The EXEC function does not need to be preceded by an OPEN call, and itdoes not have to be followed by a CLOS call.




OK The member was executed successfully.

Other An error occurred, and PPDSREC may contain anerror message.

Example

The following example shows how part of an assembler program sets parametersand then calls PDSIO to execute an IMOD:EXEC DS 0H Execute an IMOD MVC PPDSMEMB(8),=CL8'imodname' Set IMOD name MVC PPDSREC( ),=C'arg1 arg2 ............' MVC PPDSFUNC,=C'EXEC' Indicate to execute an IMOD CALL PDSIO,(PPDSFUNC,WORKA) CLC PSTATUS(2),=C'OK' Q. did we submit it BE OK Yes - continue possibly get result B ERROR Otherwise - error



Executing an IMOD Through FAQSAO: IMOD

Setting ValuesTo have BIM-FAQS/ASO execute an IMOD, set the following values in yourapplication program; then call PDSIO. In this case, no data is returned from theIMOD.


PPDSFUNC IMOD

PPDSMEMB Name of the IMOD

PPDSREC Any arguments to be passed to the IMOD

Note: The IMOD function does not need to be preceded by an OPEN call, and itdoes not have to be followed by a CLOS call.




OK The member was executed successfully.

Other An error occurred, and PPDSREC may contain an errormessage.

Example

The following example shows how part of an assembler program sets parametersand then calls PDSIO to execute an IMOD:IMOD DS 0H Execute an IMOD MVC PPDSMEMB(8),=CL8'imodname' Set IMOD name MVC PPDSREC( ),=C'arg1 arg2 ............' MVC PPDSFUNC,=C'IMOD' Indicate to execute an IMOD CALL PDSIO,(PPDSFUNC,WORKA) CLC PSTATUS(2),=C'OK' Q. did we submit it BE OK Yes - continue possibly get result B ERROR Otherwise - error


A–22 BIM-FAQS/PCS

Retrieving a PCS Global Variable: GVAR

Setting ValuesTo retrieve the value of an BIM-FAQS/PCS global variable, set the followingvalues in your application program; then call PDSIO.


PPDSFUNC GVAR.

PPDSREC Nothing. After the function completes, PPDSRECcontains the value of the global variable.

PPDSVARN Variable name (without the &).

Note: The GVAR function does not need to be preceded by an OPEN call, and itdoes not have to be followed by a CLOS call.




OK The variable value was retrieved and placed inPPDSREC.

Other An error occurred, and PPDSREC may containan error message.

Example

The following example shows how part of an assembler program sets parametersand then calls PDSIO to retrieve the value of an BIM-FAQS/PCS global variable:GVAR DS 0H Retrieve PCS global variable MVC PPDSVARN(16),=CL16'varname' Set variable name MVC PPDSFUNC,=C'GVAR' Indicate to get global variable CALL PDSIO,(PPDSFUNC,WORKA) CLC PSTATUS(2),=C'OK' Q. did we submit it BE OK Yes - continue possibly get result B ERROR Otherwise - error



Setting a PCS Global Variable: PVAR

Setting ValuesTo set an BIM-FAQS/PCS global variable, set the following values in yourapplication program; then call PDSIO.


PPDSFUNC PVAR

PPDSVARN Variable name (without the &)

PPDSREC Variable value

Note: The PVAR function does not need to be preceded by an OPEN call, and itdoes not have to be followed by a CLOS call.




OK The variable value was set successfully.

Other An error occurred, and PPDSREC may contain anerror message.

Example

The following example shows how part of an assembler program sets parametersand then calls PDSIO to set an BIM-FAQS/PCS global variable:PVAR DS 0H Set a global variable MVC PPDSVARN(16),=CL16'varname' Set variable name MVC PPDSREC( ),=C'variable value' MVC PPDSFUNC,=C'PVAR' Indicate to set global variable CALL PDSIO,(PPDSFUNC,WORKA) CLC PSTATUS(2),=C'OK' Q. did we submit it BE OK Yes - continue possibly get result B ERROR Otherwise - error


A–24 BIM-FAQS/PCS

Implementation Guide B–1

Appendix BUser Exits PCSEX1 and PCSEX2

This appendix explains the user exits PCSEX1 and PCSEX2.

IntroductionYou can invoke the user exits PCSEX1 and PCSEX2 when BIM-FAQS/PCSsubmits JCL. These exits can modify or skip a JCL statement, or they can flushthe entire jobstream.

PCSEX1 is called right after a JCL statement is read from the current inputsource, before BIM-FAQS/PCS resolves any variables or PCL control statements.

PCSEX2 is called after BIM-FAQS/PCS makes changes (resolving variables, etc.),but before the JCL is sent to POWER.

Suggested Uses for PCSEX1 or PCSEX2

You could use one or both of these exits to modify or replace JCL to meet yoursystem's security interface requirements or to make temporary JCL changes.

Sample Exit

A sample assembler-language exit is provided in the installation library underthe name PCSEX1.A. PCSEX2 is similar and uses the same register conventions.However, only PCSEX1 can use the insert function to insert a JCL statement.(You can also use the PCSEX1 sample as an example for coding PCSEX2.)

Introduction

B–2 BIM-FAQS/PCS

Input Registers

When the user exit is invoked, register R0 points to the following parameter list.This information is provided by BIM-FAQS/PCS so that the exit can determinewhat to do with the JCL statement that is passed to it.

Offset in R0 Explanation

+00 User ID of submitter (1-8 characters).

+08 Library origin of JCL. Values are

X'00' - PDS library

C'B' - BIM-EDIT library

C'L' - VSE library

C'l' - CA-LIBRARIAN library

C'W' - CA-DRIVER library

C'P' - CA-PANVALET library

C'D' - ICCF library

C'Y' - User Library Access Method

C'X' - CONDOR library

C'V' - CA-VOLLIE library

C'R' - POWER RDR queue

+09 PDS ID (3 characters) if scheduled from a PDS library.

+12 Member name (1-8 characters).

+20 Member type (3 characters). For CA-VOLLIE, this is theOPIDENT.

+23 Reserved (8 characters).

+31 User ID class (1 character).

+32 Reserved (4 characters).

+36 Event identifier (1-8 characters). If this is not an event, leaveblank. If it is an event, use the value EVENT.

+44 Event name (1-8 characters). Required only if EVTID isEVENT.

+52 Event group name (1-8 characters). Required only if EVTID isEVENT.

Introduction

Implementation Guide B–3

Other Input Registers

Register R1 is a pointer to an 80-byte card image (JCL statement) as it was read.Register R13 is a pointer to a 9D save area.

Return Codes

The user exit can return one of the following values in register R15:

Value Explanation

0 Use the JCL statement in the buffer (it may have been changed).

1 Insert the JCL statement for this run and return the originalstatement next time this JCL is invoked. (Not valid for PCSEX2.)

2 Insert the JCL statement and return the inserted statement next timethis JCL is invoked. (Not valid for PCSEX2.)

4 Skip processing this statement and get the next one.

8 Flush the rest of the JCL.

When to Use PCSEX1

Use PCSEX1 if you want to make changes to a JCL statement and then have BIM-FAQS/PCS update it by resolving variables, calling in a member, and so on,before the JCL is submitted to POWER.

For example, you could modify the ./PROC statement so that, when BIM-FAQS/PCS gets it, BIM-FAQS/PCS calls in a new member.

When to Use PCSEX2

Use the PCSEX2 exit if you want to make changes to JCL that don't require anyaction by BIM-FAQS/PCS before the JCL is submitted to POWER.

For example, use PCSEX2 to make simple changes, such as to a program name ordataset name.

Introduction

B–4 BIM-FAQS/PCS

Example

Suppose you have a user exit that determines, based on user ID or class, whetherthe current user is authorized to access payroll files. If the user is not authorized,the exit modifies the JCL so that the user can access only a test file.

The exit gets the following JCL statement (that is, the statement is pointed to byregister R1 in the exit):// DLBL PAYMAST,'P.PAYROLL.MASTER'

The exit then modifies the JCL to be the following:// DLBL PAYMAST,'T.PAYROLL.MASTER'

Finally, the exit sets register R15 to 0 (which tells BIM-FAQS/PCS to use thestatement in the buffer instead of the statement that was input), and returns.

Implementation Guide Index–1

Index

$

$ prefix (attaching subtasks), 3-20

$$BCLOSE, 3-3

$$BOPEN, 3-3

$DEFAULT, default user ID, 5-12, 5-15, 6-3, 6-11

$JOBACCTactivating, 3-3processing, 3-22

$JOBEXIT, 3-3

&

&ALERTVSE, 3-20

&AO, 3-20

&CMS, 3-21

&COFF, 3-21

&CON, 3-21

&CP, 3-21

&EVIO, 3-18

&EVLDOFF, 3-17

&EVLDON, 3-17

&EVLOAD, 3-15

&EVNAME, 3-18

&EVOFF, 3-18

&EVON, 3-18

&EVRLOAD, 3-15

&EVTEST, 3-19

&FAQSAO, 3-20

&FAQSIUX, 3-20

&LOADMSG, 3-15

&LOADTIME, 3-17

&SECLD, 3-14, 6-2

&TERMINATE, 3-14

&variable= (overriding user variable), 4-21

.

./ PROCaccessing CMS server members, 2-11accessing members, 2-6cross-reference report, 9-7multi-step example, 4-5

./ PROCoverride, 4-12

A

account historyBIM$ACUT (batch), 8-4event summary data, 8-25history archive file, 8-23logging, enabling, 3-3, 5-1viewing online, 8-69

activation$$BCLOSE, 3-3$$BOPEN, 3-3$JOBACCT, 3-3$JOBEXIT, 3-3before POWER startup, 3-4DISABLE statement, 3-4ENABLE statement, 3-3, 8-3, 12-2IPL requirement, 3-4JCLSCHED, 3-7, 11-1JCLXCU, 3-3, 8-3, 12-1multiple CPUs, 3-4sample JCL, 3-4storage requirements, 3-9

application programsaccessing PDS from, A-1directory list, A-18executing IMODs, A-20

ASSGN statement

Index–2 BIM-FAQS/PCS

cross-reference report, 9-9

audit historybatch report, 8-28viewing online, 8-72

B

back upBIM$PUTL BACKUP command (PDS), 2-9PDS, sample JCL, 2-9

batch reportsaccounting (BIM$ACUT), 8-4auditing (BIM$ADUT), 8-28dataset logging (BIM$DSUT), 8-48enabling accounting and dataset logging, 8-3event cross-reference (CREF), 9-11event summary (EVTSUM), 8-25JCL cross-reference (JCLCREF), 9-1

batch submit defaults, 5-21

batch utilitiesaccessing from CMS, 10-6BIM$ACUT (job accounting), 8-4BIM$ADUT (audit history), 8-28BIM$DSUT (dataset log report), 8-48BIM$UTTS (subtasking utilities), 3-8JCLCREF (JCL cross-reference report), 9-1JCLDUMMY (testing), 3-19, 4-20JCLSCHED (event scheduler), 3-7JCLTRACE (review JCL), 4-23JCLXCU, 3-3, 3-6, 12-1PCSEVRP (report writer), 7-1security, 6-28security by user class, 6-31

BATUSER, batch user ID, 5-21

BCINCICS interface, 11-3

BCLASS, default POWER JOB class, 5-21

BCMICMS EXEC, 10-3

BIM$ACUTACTION, 8-8DEFINE, 8-27EVTSUM, 8-25executing from CMS, 10-6MERGE, 8-17OUTPUT, 8-16PRINT, 8-14SELECT, 8-10SORT, 8-12

BIM$ADUTACTION, 8-32DEFINE, 8-45executing from CMS, 10-6MERGE, 8-41OUTPUT, 8-40PRINT, 8-38SELECT, 8-34SORT, 8-36

BIM$DSUTACTION, 8-51DEFINE, 8-68executing from CMS, 10-6MERGE, 8-60OUTPUT, 8-59PRINT, 8-57SELECT, 8-52SORT, 8-55

BIM$GMSRnode IDs, 5-42remote scheduling, 3-5

BIM$OIEI security, 6-31

BIM$PUTLBACKUP command, 2-8executing from CMS, 10-6managing the PDS, 2-8

BIM$TICIaccessing BIM-FAQS/PCS online, 11-3submitting members using, 2-6table entries, 11-3

BIM$TIDR with BIM$TICI, 11-3

BIM$TIDR, submitting members, 2-6

BIM$UTTS, activating JCLSCHED, 3-8

BIM-ALERTCMS server startup, 10-10

BIM-ALERT/VSElogger task, initiating, 3-20

BIM-EDITaccessing JCL members, 2-12JCLBIME phase, 2-12

BIM-FAQS/ASOsubmitting members, 2-6

BIM-FAQS/PCS PDS. see PDS

C

CACONVBL IMOD, 1-12


CACONVEX IMOD, 1-12

CA-DRIVERaccessing JCL members, 2-15JCLDRIV phase, 2-15

CA-LIBRARIANaccessing JCL members, 2-16JCLLIBR phase, 2-16

CA-PANVALETaccessing JCL members, 2-17

CA-SCHEDULER, converting, 1-12

CA-VOLLIEaccessing JCL members, 2-14JCLVOLI phase, 2-14

CICSaccessing BIM-FAQS/PCS online, 11-1interface

JCLRCICS programs, 11-6starting the scheduler, 11-1subtask JCLRTASK, 11-6table entries, 11-2, 11-3, 11-4

Class= (overriding job class), 4-15

CMSaccessing BIM-FAQS/PCS, 10-4accessing global variables from CMS, 10-7BCMI EXEC, 10-3PCSCMS EXEC, 10-5PCSSUB EXEC, 10-9RXSETUP EXEC, 10-8submission defaults, 5-4, 5-11submitting JCL, 12-3suppressing CMS options, 6-9

CMS server./ PROC statements, member access, 2-11BIM-ALERT startup, 10-10defaults, 5-16end processing, 10-10executing commands, 3-21files, 10-9JCL command (SUB), 4-7JCLSCHED command format, 2-11JCLXCU command format, 2-11startup, 10-10user ID, defining, 10-10

columns, variable substitution, 5-19, 5-25

CONDORaccessing JCL members, 2-18JCLPNX phase, 2-18

configurationbatch submit defaults, 5-20CMS server defaults, 5-16

CMS submit defaults, 5-4, 5-11CPU IDs and synonyms, 5-42cycles, 5-34dataset exclusion, 5-44dataset logging suppression, 5-46event defaults, 5-7, 5-14exception date, 5-39global options, 5-17holidays, 5-29JCLCONFG.CTL, 5-1library defaults, 5-27panel defaults, 5-7, 5-14PDS defaults, 5-7, 5-14user calendar, 5-38user classes, 5-24user ID classes, 5-9

console reply, 3-21

conversionCA schedules, jobs

CACONVBL IMOD, 1-12CACONVEX IMOD, 1-12

from JCLMAN, 1-10JCLCONV (conversion utility), 1-6

CP commands, passing to VM, 3-21

CPU IDsynonyms

defining, 5-43NODEID Table, 5-42

CPUs, multiple, 3-9

cross-reference reports. see reports, cross-reference

cua= (override parameter), 4-17

current event fileloading events

at specified time (&LOADTIME), 3-17automatically (&EVLDOFF), 3-17by group mask, 3-16

merging events (&EVLOAD), 3-15replacing events (&EVRLOAD), 3-15scanning (&EVIO), 3-18

cyclesdefaults, 5-36defining, 5-29, 5-34editing, 5-35list by IDs, 5-34

D

DATA=Y (variable substitution), 4-11, 4-22


datasetaudit log, 8-76exclusion

specifying, 5-44storage requirements, 5-45

history, viewing online, 8-75logging

BIM$DSUT, 8-48by partition, 5-47by phase, 5-49by VSE job, 5-50components, 8-3creating a report, 8-48exclude datasets, 5-52history archive file, 8-48, 8-66including datasets, 5-51PCSSRV, 3-10specifying suppression, 5-46

DATATYP, default PDS member datatype, 5-22

DATE= (overriding date value), 4-19

DEBUG (testing JCL), 4-11, 4-20

defaultsabend code (DABEND), 12-3CMS server, 5-16CMS submit, 5-4global batch, 5-20library, 5-27maximum return code (DMAXRC), 12-3online, 5-7, 5-14panel (system), 5-14user ID ($DEFAULT), 5-12, 6-11

Diagnosing problems, 0-6

Diagnostic data, interpreting, 0-7

directory listapplication program (PDSIO), A-18

DISP=default POWER disposition, 5-21overriding job disposition, 4-16

DLBL statement, cross-reference report, 9-8

DRIVER. see CA-DRIVER

DSN. see dataset

DTF statements, cross-reference report, 9-8

E

End= (override parameter), 4-11, 4-13

event command, submitting jobs, 4-9

event processingdisabling (&EVOFF), 3-18display name on console (&EVTEST), 3-18enabling (&EVON), 3-18loading the current file (&EVLOAD), 3-15reloading current file (&EVRLOAD), 3-15testing event scheduling (&EVTEST), 3-19

event report writer (PCSEVRP), 7-1

event securityadministrator, 6-9event access, 6-25file access, controlling, 6-9group security, 6-22

event summary data, collecting, 8-25

eventscross-reference report (CREF), 9-11defaults

configuration, 5-7system configuration, 5-14user ID, 5-9

reportsevent summary, batch, 8-25forecasting, online, 8-77report writer (PCSEVRP), 7-1

exception datedefault, 5-40defining, 5-39editing, 5-41

EXEC statementschanging values at job generation, 4-18cross-reference report, 9-10

Exit. See &TERMINATE

external library memberscopying, 2-3

F

file ID statements, cross-reference report, 9-8

FLEE GSERV, 5-19

forecastingevent report writer (PCSEVRP), 7-22

functions, suppressing, 6-8

G

GEN command (JCLXCU), 2-6


global configurationbatch defaults, 5-21options, 5-17

global variablesretrieving with REXX EXEC, 10-7returning values

to application (PDSIO), A-22setting values

from REXX EXEC, 10-7in application program (PDSIO), A-23

H

history archive file. see audit history, account history,or dataset logging

holidaysdefaults, 5-32defining, 5-29editing, 5-31list by IDs, 5-30

I

ICCFaccessing JCL members, 2-10BIM-FAQS/PCS utility security, 6-31library defaults, 2-5, 5-28using JCLTRACE, 4-24

IMODsexecuting from application program, A-21return data to application (PDSIO), A-20

installation. see BIM-GSS Installation Guide

interfaces, initiatingBIM-FAQS/ASO REXX interface, 3-20IUCV, 3-20

IUCV, initiating, 3-20

J

JCLchanging before submission (user exit), B-3cross-reference report (JCLCREF), 9-1debugging, 4-20definition, 4-2review before submission (JCLTRACE), 4-23substituting variables, 4-21

testing, 4-20user exits, B-1

JCL jobscomponents, 4-3definition, 4-2jobstream example, 4-3multi-step example, 4-4, 4-5one-step job example, 4-3override parameters, 4-20***4-21PROCMNT option, 4-14restart, 4-4, 4-13restart with card retention, 5-22submitting

CMS defaults, 5-4job generation commands, 4-9using JCLXCU, 12-1

user variables example, 4-6

JCL membersaccessing from

BIM-EDIT, 2-12BIM-FAQS/PCS PDS, 2-7CA-DRIVER, 2-15CA-LIBRARIAN, 2-16CA-PANVALET, 2-17CA-VOLLIE, 2-14CMS server, 2-11CONDOR, 2-18ICCF, 2-10PDS, 2-7POWER RDR queue, 2-20VSE library, 2-19

accessing using ./ PROC, 2-6contents, 2-5copying from external libraries, 2-3definition, 4-2moving to BIM-FAQS/PCS PDS, 2-3sources, valid libraries, 2-1submitting using

BIM$TICI, 2-6BIM$TIDR, 2-6BIM-FAQS/ASO, 2-6JCLSCHED, 2-6JCLXCU, 2-6, 12-1

JCLBCICSfunctions, 11-1table entries, 11-4

JCLCONFG.CTL memberconfiguration, 5-1, 5-9security, 6-2security administrator, 6-18

JCLCONV (conversion utility)commands, 1-6sample jobstream, 1-9


JCLCREFASSGN summary, 9-9deleting input file, 9-4DTF summary, 9-8EXEC summary, 9-10executing from CMS, 10-6file ID summary, 9-8JOB summary, 9-7OPT command, 9-3PROC summary, 9-7REPORT command, 9-2required JCL, 9-5

JCLDSERV, maintain PDS members, 2-8

JCLDUMMYDEBUG, 4-20testing event scheduling, 3-19

JCLEVNTCREF (event cross-reference report), 9-11executing from CMS, 10-6

JCLGEN, maintain PDS members, 2-8

JCLMAINTmaintain PDS members, 2-8security, 6-31

JCLMANconverting, 1-10executing from CMS, 10-6managing the PDS

JCLDSERV, 2-8JCLGEN, 2-8JCLMAINT, 2-8JCLSERV, 2-8JCLTRACE, 2-8

JCLMAN, default POWER JOB class, 5-21

JCLRCICSGETVIS requirements, 11-5programs, 11-6security, 6-31starting and shutting down, 11-5

JCLRTASK (CICS subtask), 11-6

JCLSCHEDactivating

CICS subtask, 3-8, 11-1partition, main task, 3-7preactivation considerations, 3-2subtask of a main task, 3-8

activation, 3-3CMS server command format, 2-11disabling, 3-18enabling automatically, 3-18initiating interfaces, 3-20JCLSCHED.CTL member, 3-9

message processor, 3-12overview, 3-7partition, permanent scheduler, 5-21remote scheduling, 3-5schedule history, 8-1scheduler control commands

$phasename, 3-20&ALERTVSE, 3-20&AO, 3-20&CMS, 3-21&COFF, 3-21&CON, 3-21&CP, 3-21&EVIO, 3-18&EVLDOFF, 3-17&EVLDON, 3-17&EVLOAD, 3-15&EVNAME, 3-18&EVON, 3-18&EVRLOAD, 3-15&EVTEST, 3-19&FAQSAO, 3-20&FAQSIUX, 3-20&LOADTIME, 3-17&SECLD, 3-14&TERMINATE, 3-14

startupAUTO commands, 3-9CICS table entries, 11-2JCLSCHED.CTL member, 3-9

storage requirements, 3-9submitting members, 2-6SVA phases, 3-2testing event scheduling, 3-19

JCLSCHED.CTL member&LOADTIME, 3-17AUTO $PCSLOG, 3-5AUTO statements, 3-9

JCLSERV, maintain PDS members, 2-8

JCLTAPE, maintain PDS members, 2-8

JCLTRACE utilitydisabled REXX functions, 4-24reviewing JCL before submission, 4-23with ICCF, 4-24

JCLTRACE, maintain PDS members, 2-8

JCLXCU/ ID USER= statement, 12-2activating

accounting and dataset logging, 8-3scheduler, 3-4

CANCEL statement, 12-3CMS server command format, 2-11CP statement, 12-2


DABEND statement, 12-3DESKTOP statement, 12-3DISABLE statement, 3-4DMAXRC statement, 12-3ENABLE statement, 3-3, 8-3examples of using control statements, 12-4GEN statement, 12-2LOADSVA statement, 12-2LOCK statement, 12-2LOG OFF statement, 12-2LOG statement, 12-2OP statement, 12-3replies statement (A RDR...), 12-3security, 6-30startup options, 3-6SUB statement, 12-3submitting jobs

GEN command, 2-6, 4-7UNLOCK statement, 12-2

JECL, definition, 4-2

job accounting, 8-3

job control language. see JCL

job hooks. see activation

JOB statements, cross-reference report, 9-7

job step, definition, 4-2

jobs. see JCL jobs

jobstream, definition, 4-2

L

LIBRARIAN. see CA-LIBRARIAN

library defaults, 5-27

library members. see also JCL members or PDSmembers

logging optionsdataset, 5-46

M

member-level security, 6-18

members. see JCL members

message tablerebuilding (&LOADMSG), 3-15scanning, BIM-FAQS/ASO, 3-12

messagesdetection (PCSMSG), 3-12

model user ID, 6-12

N

nested call, definition, 4-2

nested membersCMS, 4-8

node IDs, 5-42

O

OCCF considerations, 3-21

online defaults, 5-7, 5-14

online interfaces, submitting JCL membersBIM$TICI, 2-6BIM$TIDR, 2-6BIM-FAQS/ASO, 2-6

online reportsdataset logging, 8-75event forecasting, 8-77event history summary, 8-71job accounting, 8-69job auditing, 8-72

operatorcommands, issuing using JCLXCU, 12-1reply

convert to uppercase, 5-26

outstanding reply IDs, 3-21

override parameters, 4-11

P

panel defaultsconfiguration option, 5-7system configuration, 5-14user ID, 5-9

panel security (suppressing options), 6-8

PANVALETJCLPANV phase, 2-17

partitioned dataset. see PDS


PCSCMS EXECtailoring, 10-5

PCSCPOST, 10-6

PCSERPT utility (event summary)executing from CMS, 10-6

PCSEVRPACTION, 7-19comments, 7-30control statements, 7-2END, 7-20FILE, 7-21FORECAST, 7-22INCLUDE, 7-23PRINT, 7-24print file characteristics, 7-24SELECT, 7-25SORT, 7-28TITLE, 7-29

PCSEX1 user exit, B-1

PCSEX2 user exit, B-1

PCSLOGremote scheduling, 3-5running, 3-22

PCSMSG message processor, 3-12

PCSSERV default CMS server ID, 5-16

PCSSRV (dataset logging)activating, 3-10startup, 3-4

PCSSUB EXEC (CMS), 10-9

PDSadvantages, 2-2back up, BIM$PUTL BACKUP command, 2-9defaults

configuration option, 5-7system options, 5-14user ID, 5-9

definition, 2-2library defaults, 2-5member name format, 2-7members

close and post (PDSIO), A-15closing (PDSIO), A-10, A-13deleting (PDSIO), A-14opening for input (PDSIO), A-7records, reading (PDSIO), A-9searching for (PDSIO), A-16security, 6-18, 6-19submitting to POWER (PDSIO), A-17writing to (PDSIO), A-11, A-12

search string, 2-5, 2-7

search string, 5-28utilities

BIM$PUTL, 2-8JCLMAN, 2-8

PDSIOCLOP, A-15CLOS, A-10, A-13DELE, A-14EXEC, A-20FIND, A-16GEN, A-17GVAR, A-22IMOD function, A-21OPEI, A-7OPEO, A-11parameters, A-3PVAR, A-23READ, A-9sample program, A-2WRIT, A-12

PGM= (override parameter), 4-11, 4-18

POWERchanging values at job generation, 4-15SLI catalog support, enabling/disabling, 5-19SLI support, 4-8submitting PDS members, A-17XPCC support, 4-8

POWER class, overriding, 4-15

POWER disposition, overriding, 4-16

POWER JECLJOB statements, cross-reference report, 9-7saving, job restart, 4-13

POWER JOB default scheduler class, 5-21

POWER priority, overriding, 4-15

POWER RDR queue, submitting jobs, 2-20

POWER SYSID, overriding, 4-15

PPDSPARM source (used with PDSIO), A-5

Prevail/XP-Managercontrolling communications, 12-3routing event status, 12-2

PRI, default POWER priority, 5-22

PRI= (overriding job priority), 4-15

Problems, diagnosing, 0-6

PROC= (override parameter), 4-11, 4-19

PROCMNTrestart comment format, 5-22restarting a job, 4-14


program interface. see PDSIO

Q

Quit. See &TERMINATE

R

remote schedulingconsiderations, 3-5

reply IDs, 3-21

report writer (PCSEVRP), 7-1

reportsbatch

dataset monitoring (BIM$DSUT), 8-48enabling accounting, dataset logging, 8-3event cross-reference (CREF), 9-11event report (PCSEVRP), 7-1event summary (EVTSUM), 8-25JCL cross-reference (JCLCREF), 9-1job accounting (BIM$ACUT), 8-4job auditing (BIM$ADUT), 8-28

cross-referenceevent cross-reference (CREF), 9-11JCL cross-reference (JCLCREF), 9-1

onlinedataset logging, 8-75event forecasting, 8-77event history summary, 8-71job accounting, 8-69job auditing, 8-72

RERUN (override parameter), 4-11

restart, job (configuration), 5-22, 5-25

REXX&FAQSAO command, 3-20functions disabled during trace, 4-24interface, initiating, 3-20

REXX IMODsupdating global variables, 10-7

RXPCS function, 10-7

RXSETUP CMS EXEC, 10-8

S

security$DEFAULT user ID, 6-3administrator, 6-3, 6-10defining, 6-1event, 6-25event administrator, 6-9event groups, 6-22loading to each partition, 6-2model user ID, 6-12multiple partitions, 6-2PDS member access, 6-18user ID, 6-6, 6-13, 6-14user ID classes, 6-15utilities, 6-28utilities, by user class, 6-31

Shutdown. See &TERMINATE

SLI support, 4-8, 5-19

SPAR option, 5-21

Start= (override parameter), 4-14

storage requirementsdataset exclusion, 5-45scheduler, 3-9

subtasks, attaching, 3-20

SVA phases, 3-2

SYSID=default POWER SYSID, 5-22overriding SYSID, 4-15

SYSnnn= (override parameter), 4-11, 4-17

system performance, improving, 3-22

T

Terminate. See &TERMINATE

testingevent schedules (&EVTEST and JCLDUMMY),3-19JCL statements (JCLTRACE), 4-23

TLBL statements, cross-reference report, 9-8

TRACE commanddisabled REXX functions, 4-24format, 4-23


U

UPSI= (overriding UPSI value), 4-11

user calendarslist, 5-38

user classesconfiguration options, 5-20defining, 5-24security, 6-15, 6-16

user exits, B-1

user IDadding/deleting, 6-12default, 6-11default, $DEFAULT, 5-15model, 6-12

user ID classes (configuration), 5-9

user variableschanging, 4-21

substituting in JCL, 4-21substitution, 4-6

utilities. see batch utilities

V

variables. see also global, local, and user variablessubstitution, scan columns, 5-19, 5-25

VOLLIE. see CA-VOLLIE

VSE libraryabbreviated command format, 2-5accessing JCL members, 2-19

X

XPCC interface, 4-8

production control system implementation guide€¦ · production control system implementation...

Documents