backup & recovery manager suite user guide:...

Mainstar®: Backup & Recovery Manager™ Suite User Guide

ASAP

Product Version 6, Release 01

SC23-6059-00 November 2006

Mainstar Software Corporation P.O. Box 4132 Bellevue, WA 98009 USA

Tel 1-425-455-3589 Fax 1-425-455-1992 Web: www.mainstar.com Technical Support: Mainstar Technical Support

Copyright ©2006 Mainstar Software Corporation. All rights reserved. Mainstar Software Corporation is a wholly owned subsidiary of Rocket Software, Inc.

http://www.mainstar.com/

http://www.mainstar.com/services/support/problem/index.asp

Backup & Recovery Manager Suite: ASAP User Guide

Twenty-Seventh Edition (November 2006)

This edition of the Mainstar: Backup & Recovery Manager Suite User Guide for ASAP applies to Version 6, Release 01 of the Mainstar: ASAP product.

Restricted Materials

This manual contains restricted materials proprietary to Mainstar Software Corporation. Use and possession of this manual is pursuant to the user obtaining a license for the ASAP product from Mainstar Software Corporation.

Trademarks

'Mainstar' is a registered trademark of Mainstar Software Corporation in the United States and/or other countries.

The following terms used in this publication have been adopted by Mainstar Software Corporation as trademarks in the United States and/or other countries:

ABARS Manager Aggregate LoadBalancer All/Star ASAP Backup & Recovery Manager Suite CATSCRUB

The following terms used in this publication are registered trademarks of the IBM Corporation in the United States and/or other countries:

IBM Tivoli z/OS

The following terms used in this publication have been adopted by IBM as trademarks in the United States and/or other countries:

DFSMSdss DFSMShsm MVS/ESA

The following terms used in this publication have been adopted by other corporations as trademarks in the United States and/or other countries:

TRADEMARK COMPANY

ASG-Zeke™ Allen Systems Group

BMC® CONTROL-M for z/OS BMC Software, Inc.

Brightstor® CA-Disk™ Backup and Computer Associates International, Inc. Restore Cybermation ESP® Cybermation Inc.

Unicenter® CA-Jobtrac® Job Management Computer Associates International, Inc.

Unicenter® CA-7® Job Management Computer Associates International, Inc.

Quick-Ref™ Chicago-Soft

©1992–2006 by Mainstar Software Corporation All Rights Reserved

November 2006 SC23-6059-00 Twenty-Seventh Edition

Mainstar Software Corporation ©2006 i Contents SC23-6059-00

PROPRIETARY: Unauthorized use, reproduction, or distribution prohibited.

User Guide Backup & Recovery Manager Suite: ASAP

Summary of Changes

SC23-6059-00 This version of the ASAP User Guide applies to Version 6, Release 01 of November 2006 the ASAP product. Twenty-Seventh Edition

Product Enhancements See Fixlist included with release distribution for details.

Document Changes • Convert user guide to BRM Suite product document • Update third-party product names throughout document (CA-7, Jobtrac,

CONTROL-M, Zeke, ESP, CA-Disk) (24095) • Remove Auditing • Update Chapter 1, ASAP Overview, to: − remove 'Use SIZE For INC/ACCompny Tapes' and 'Max Tape

INCLUDE Size' fields from Current Verification Options panel − remove Help for GDG Options field from Verification GDG Options

section − add BRM Main Menu to processes for accessing ASAP for Forward

and Rerun Recovery − add Task 8, Verify the Data Sets Identified by ASAP Were Backed

Up, to Simple Steps to Get Started Using ASAP − remove Auditing Options table from the Enter the Application Setup

Options for Forward and Rerun Recovery sections (25573) • Update Chapter 2, Overview of the ASAP Main Menu, to: − add the BRM Main Menu − remove Option 4, Auditing from the ASAP Main Menu and the

Application AutoBuild Options menu (25573) • Update Chapter 3, SETUP – Defining an Application to ASAP to: − remove 'Use SIZE For INC/ACCompny Tapes' and 'Max Tape

INCLUDE Size' fields from Current Verification Options panel − change default of Collection Mode on Job Collection Options panel to

REPLACE − remove Help for GDG Options field from Verification GDG Options

section − remove Option 5, Auditing from the Application AutoBuild Options

menu (25573) • Update Chapter 4, JOB COLLECT – Collecting Application Job

Structure: − remove topic "Differences in Batch Auditing of Job Collection Types"

(25573) − remove Option 12, Display Last Auditing Results from ASAP

Application Display Selections menu (25573) • Update Chapter 7, Real-time Selection Process (RSP), to: − add RSP note to the Applend Program (23084)

• Remove Chapter 8, Batch AUDIT – Monitoring Application Changes (25573)

• Update Chapter 9, Using Filters and Controls to: − add INCL_EXTJOB filter (21559) − add note regarding SMF filters without a volser (23147) − add new DSORG filter (22041)

• Move Appendix A, Messages, into Chapter 1

Contents ii Mainstar Software Corporation ©2006 SC23-6059-00



• Appendix A (re- numbered from Appendix B), Batch JCL and Control Statement Reference: − remove APLDBUPD – Database Update Control Statements and

AUDITSCH – Audit Scheduling Control Statements (25537) • Update Appendix C (now numbered Appendix B), ASAP Reports and

Utilities to: − add example for ASPMNT01, Rename an ASAP Application (22941)

Document 064-0201-24 This version of the ASAP User Guide applies to Version 5, Release 4.01 of June 2005 the ASAP product. Twenty-Sixth Edition


Document Changes • Updates throughout to: − move the application filters from option 0 – Setup to the main ASAP

Application menu (19166) • Update Chapter 1, ASAP Overview to: − add BACKUP OPTIONS section to Step-by-Step Setup Options

(20225) − add cross-reference to Backup & Recovery Manager Suite: All/Star

• Update Chapter 2, Overview of the Main ASAP Menu, to: − remove the Application Status Line (17991)

• Update Chapter 3, Defining an Application to ASAP - SETUP to: − add BACKUP OPTIONS section to Application Setup Options panel

(20225) • Update Chapter 4, JOB COLLECT – Collecting Application Job

Structure, to: − add documentation for ESP Job Scheduler product. (ETR9574)

• Update Chapter 7, Real-time Selection Process (RSP), to: − remove dataspace information command F RSP, DSPC(INFO) and F

RSP,DSPC. (16983) − clarify RSP documentation (20495) − add RSP note to the Applend program (23084)

• Update Chapter 6, VERIFICATION – Creating the Selection Data Set, and Chapter 9, Obtaining Application Information, to: − update the Application List Panel to replace REXX with assembler

modules (17990) − change Application List processing to use the scroller (20327)

• Update Chapter 10, Using Filters and Controls to: − add EXCL_BUT_CRITICAL filter information (20226)add

INCL_EXTJOB filter (21559) − add note regarding SMF filters without a volser (23147) − add new DSORG filter (22041)

• Update Appendix C, ASAP Reports and Utilities to: − add example for ASPMNT01, Rename an ASAP Application (22941)

Mainstar Software Corporation ©2006 iii Contents SC23-6059-00



Document 064-0201-23 This version of the ASAP User Guide applies to Version 5, Release 3.01 of May 2004 the ASAP product. Twenty-Fifth Edition


Document Changes • Update Ch. 1, ASAP Overview to: − highlight ASAP setup options with Forward Recovery (10130)

• Update Ch. 2, Overview of the ASAP Main Menu to: − document PFSHOW to turn off PF key display (PMR16947)

• Update Ch. 4, JOB COLLECT– Collecting Application Job Structure to: − update figure 4.15 (ETRD16813) − update examples of job collection and batch reports (PMR15625) − display number of successor jobs for each anchor (ETR17409)

• Update Ch. 5, SMF Scan Setup to: − note that APPLEND does not process batch SMF data (17457)

• Update Chapter 6, VERIFICATION – Creating the Selection Data Set to: − note APPLEND must run before ASAP VERIFY (ETRD16513)

• Update Ch. 7, Real-Time Selection Process (RSP): − exclude OpenTech’s VDR tape list during APPLEND (ETR16123) − document 2 new overflow messages (ETR17571) − remove obsolete RSP command (ETR16983)

• Update Ch. 9, Obtaining Application Information to: − update list of jobs collected

• Update Ch. 10, Using Filters and Controls to: − clarify comments in filter overview (ETR17282)

• Update Appendix B, Batch JCL and Control Statement Reference to: − delete ASAPOPC Job Collection Procedure (ETR16900) − APPLEND doc change (DCR17066)

• Update Appendix C, ASAP Reports and Utilities to: − change SYSIN DD to XYXIN DD (ETRD16647) − add ASPFLTRP and ASPCHKDB reports (ETR15417-15083)

• Updates throughout document: − change 'OPC' references to 'TWS' (ETR16900) − changes to CA7 job collection (PMR15625) − remove job collection for JCS/Matrix (ETR16311) − exclude data set not on panels any longer (ETR17485) − eliminate ABARS Manager references (ETR10130) − remove ALT libraries (ETR14313) − remove notebook entries (ETR14484) − update obsolete screens (ETR17593) − add option for error messages to main menu (ETR16765) − add interface between ASAP and VDR (ETR16123) − change OPC job collection (PMR17184) − add documentation for APPLEND keyword DELETEDETAIL

Contents iv Mainstar Software Corporation ©2006 SC23-6059-00



Twenty-Fourth Edition: November 2003 Document 064-0201-22 for V5R201 Service Pack 1 Twenty-third Edition: February 2003 Document 064-0201-21 for V5R2 Twenty-second Edition: October 2002 Document 064-0201-20 for V5R1 Service Pack F Twenty-first Edition: June 2002 Document 064-0201-19 for V5R1 Service Pack E Twentieth Edition: January 2002 Document 064-0201-18 for V5R1 Service Pack D Nineteenth Edition: December 2001 Document 064-0201-17 for V5R1 Service Pack C Eighteenth Edition: September 1999 Document 064-0201-16 for V5R1 Seventeenth Edition: January 1999 Document 064-0201-15 for V4R4 Sixteenth Edition: December 1998 Document 064-0201-14 for V4R3 Fifteenth Edition: October 1998 Document 064-0201-13 for v4R3 Fourteenth Edition: July 1998 Document 064-0201-12 for V4R2 Thirteenth Edition: June 1998 Document 064-0201-11 for V4R2 Twelfth Edition: March 1998 Document 064-0201-10 for V4R1 (Y2K) Eleventh Edition: January 1998 Document 064-0201-09 for V2R4 Tenth Edition: October 1997 Document 064-0201-08 for V2R4 Ninth Edition: September 1997 Document 064-0201-07 (TNL) for V2R4 Eighth Edition: unpublished Seventh Edition: May 1997 Document 064-0201-07 for V2R4 Sixth Edition: unpublished Fifth Edition: March 1996

Mainstar Software Corporation ©2006 v Contents SC23-6059-00



Contents Preface.1 About This Book ............................................................................................................................ 1

Preface.2 Where to Find More Information................................................................................................... 3

1 ASAP Overview .................................................................................................................................. 1-11.1 About Backup and Recovery Manager Suite ..................................................................................... 1-21.2 What Is ASAP? .................................................................................................................................. 1-21.3 What Does ASAP Do? ....................................................................................................................... 1-41.4 ASAP Cross-Reference to Backup & Recovery Manager Suite: All/Star .......................................... 1-41.5 ASAP Functions, Methods, and Support ........................................................................................... 1-5

1.5.1 Mirroring Support ...................................................................................................................... 1-51.5.2 Forward vs. Rerun Recovery .................................................................................................... 1-61.5.3 Selection Data Set Output Formats.......................................................................................... 1-61.5.4 The ASAP Database................................................................................................................. 1-61.5.5 Interfaces to Job Scheduling Products ..................................................................................... 1-71.5.6 Job Name Masks ...................................................................................................................... 1-71.5.7 Critical Data Set Identification .................................................................................................. 1-71.5.8 ASAP Real-time Selection Process (RSP) ............................................................................... 1-8

1.6 How Does ASAP Work?..................................................................................................................... 1-91.7 Preparing for ASAP.......................................................................................................................... 1-10

1.7.1 Identify a Contact Person for Each Application ...................................................................... 1-101.7.2 Identify the Applications/Job Streams to Be Analyzed by ASAP ........................................... 1-101.7.3 Using Scheduler Interfaces .................................................................................................... 1-111.7.4 ASAP Application Checklist .................................................................................................... 1-12

1.8 Simple Steps to Get Started Using ASAP........................................................................................ 1-131.8.1 Step 1: Complete ASAP SETUP for Application ................................................................... 1-131.8.2 Step 2: Perform a Job Collection........................................................................................... 1-141.8.3 Step 3: Refresh the Job Table............................................................................................... 1-151.8.4 Step 4: Identify the Application's Data Sets........................................................................... 1-151.8.5 Step 5: Run the Application ................................................................................................... 1-171.8.6 Step 6: Create the Selection Data Set................................................................................... 1-171.8.7 Step 7: Create Filters – Optional ........................................................................................... 1-171.8.8 Step 8: Verify the Data Sets Identified by ASAP Were Backed Up....................................... 1-20

1.9 Step-by-Step ASAP Setup Options – For Forward Recovery.......................................................... 1-211.9.1 Enter the Application Setup Options for Forward Recovery................................................... 1-221.9.2 Submit Job Collection ............................................................................................................. 1-26

1.10 Step-by-Step ASAP Setup Options – For Rerun Recovery ............................................................. 1-271.10.1 Enter the Application Setup Options for Rerun Recovery ...................................................... 1-281.10.2 Submit Job Collection ............................................................................................................. 1-32

1.11 Monitoring Application Changes ...................................................................................................... 1-331.12 ASAP Batch Job Submission Sequence.......................................................................................... 1-341.13 Viewing Product Messages.............................................................................................................. 1-35

1.13.1 Message Identifier Naming Convention.................................................................................. 1-351.13.2 Determine Which MESSAGES Member Contains the Message Description ........................ 1-351.13.3 View Messages Using ISPF Interface .................................................................................... 1-361.13.4 View Messages in MESSAGES Library ................................................................................. 1-361.13.5 View Messages Using Quick-Ref ........................................................................................... 1-36

2 Overview of the ASAP Main Menu.................................................................................................... 2-12.1 Backup & Recovery Manager Suite Main Menu ................................................................................ 2-2

Mainstar Software Corporation ©2006 vii Contents SC23-6059-00



2.2 ASAP Main Menu Options.................................................................................................................. 2-22.3 LIST APPLICATIONS – Option 1 ....................................................................................................... 2-42.4 SELECT/CREATE APPLICATION – Option 2 ................................................................................... 2-5

2.4.1 Supply an Application Name to ASAP ...................................................................................... 2-52.4.2 Application AutoBuild Options Menu ........................................................................................ 2-6

2.5 RSP MONITOR – Option 3 ................................................................................................................ 2-92.6 N/A – Option 4.................................................................................................................................... 2-92.7 SMF SCAN SETUP – Option 5 .......................................................................................................... 2-92.8 N/A – Option 6.................................................................................................................................... 2-92.9 N/A – Option 7.................................................................................................................................... 2-92.10 ERROR MESSAGES – Option 8 .......................................................................................................2-9 2.11 FILTERS/CONTROLS – Option 9....................................................................................................2-10

3 SETUP – Defining an Application to ASAP...................................................................................... 3-13.1 Set Up an Application – Application AutoBuild Options Menu Option 0 ............................................ 3-2

3.1.1 The APPLICATION Field .......................................................................................................... 3-53.2 Application General Setup Section .................................................................................................... 3-6

3.2.1 Application General Setup Field Descriptions .......................................................................... 3-63.3 Job Collection Options Section .......................................................................................................... 3-8

3.3.1 Job Collection Options Field Descriptions ................................................................................ 3-83.4 Collection Options Section ............................................................................................................... 3-10

3.4.1 Collection Options Field Description....................................................................................... 3-103.5 RSP Options Section........................................................................................................................ 3-11

3.5.1 RSP Options Field Descriptions ............................................................................................. 3-113.6 JCL Options Section......................................................................................................................... 3-12

3.6.1 JCL Options Field Descriptions .............................................................................................. 3-123.7 Batch SMF Scan Options Section.................................................................................................... 3-13

3.7.1 Batch SMF Scan Options Field Descriptions.......................................................................... 3-133.8 Current Verification Options Section ................................................................................................ 3-14

3.8.1 Current Verification Options Field Descriptions ...................................................................... 3-153.9 Verification GDG Options Section.................................................................................................... 3-21

3.9.1 Verification GDG Options Field Descriptions.......................................................................... 3-233.10 Backup Options Section ................................................................................................................... 3-29

3.10.1 Backup Options Field Description........................................................................................... 3-293.11 Selection Data Sets Section............................................................................................................. 3-30

3.11.1 Selection Data Sets Field Descriptions................................................................................... 3-30

4 JOB COLLECT – Collecting Application Job Structure ................................................................. 4-14.1 Overview of the Job Collection Process............................................................................................. 4-2

4.1.1 Application Job Entries ............................................................................................................. 4-34.1.2 Job Lists vs. Job Structures ...................................................................................................... 4-44.1.3 Determine the Job Collection Point .......................................................................................... 4-54.1.4 About the Application Job Collection Method Panel................................................................. 4-6

4.2 Job Collection with Unicenter CA-7 Job Management..................................................................... 4-104.2.1 Steps to Schedule Initial Unicenter CA-7 Job Collection........................................................ 4-104.2.2 Step 1: Set Configuration Values for Unicenter CA-7 in BRMINI PARMLIB Member ............ 4-114.2.3 Step 2: Optional – Set Up Unicenter CA-7 Job Name Filtering .............................................. 4-114.2.4 Step 3: Review/Update Unicenter CA-7 Input Entry Panel..................................................... 4-114.2.5 Step 4: Edit/Submit Unicenter CA7 Job Collection ................................................................. 4-144.2.6 Step 5: View Results of Unicenter CA-7 Job Collection ......................................................... 4-15

4.3 Job Collection with CONTROL-M .................................................................................................... 4-164.3.1 Steps to Schedule Initial CONTROL-M Job Collection........................................................... 4-174.3.2 Step 1: Set Configuration Values for CONTROL-M in BRMINI PARMLIB Member............... 4-174.3.3 Step 2: Optional – Set Up Job Name Filtering........................................................................ 4-17

Contents viii Mainstar Software Corporation ©2006 SC23-6059-00



4.3.4 Step 3: Review/Update CONTROL-M Input Entry Panel ....................................................... 4-184.3.5 Step 4: Edit/Submit the CONTROL-M Job Collection ............................................................ 4-204.3.6 Step 5: View Results of CONTROL-M Job Collection............................................................ 4-21

4.4 Job Collection with Cybermation ESP ............................................................................................. 4-27 4.4.1 Steps to Initiate Cybermation ESP Job Collection ................................................................. 4-274.4.2 Step 1: Set Configuration Values for Cybermation ESP in BRMINI PARMLIB Member........ 4-274.4.3 Step 2: Optional - Set Up Job Name Filtering for Cybermation ESP ..................................... 4-274.4.4 Step 3: Cybermation ESP Input Entry Panel .......................................................................... 4-274.4.5 Step 4: Edit/Submit Cybermation ESP Job Collection ........................................................... 4-284.4.6 Step 5: View Results of Cybermation ESP Job Collection ..................................................... 4-30

4.5 Job Collection with Unicenter CA-Jobtrac........................................................................................ 4-31 4.5.1 Steps to Schedule Initial Unicenter CA-Jobtrac Job Collection.............................................. 4-314.5.2 Step 1: Set Configuration Values for Unicenter CA-Jobtrac in BRMINI PARMLIB Member .. 4-314.5.3 Step 2: Optional – Set up Job Name Filtering for Unicenter CA-Jobtrac ............................... 4-314.5.4 Step 3: Review/Update Unicenter CA-Jobtrac Input Entry Panel .......................................... 4-314.5.5 Step 4: Edit/Submit Unicenter CA-Jobtrac Job Collection...................................................... 4-354.5.6 Loading an Alternate Forecast Schedule for Your Application............................................... 4-364.5.7 Using the Unicenter CA-Jobtrac Output Schedule Option (JOBTRACSCHEDOUT)............. 4-394.5.8 Step 5: View Results of Unicenter CA-Jobtrac Job Collection ............................................... 4-40

4.6 Job Collection with TWS .................................................................................................................. 4-414.6.1 Steps to Schedule Initial TWS Job Collection ........................................................................ 4-414.6.2 Step 1: Set Configuration Values for TWS in BRMINI PARMLIB Member ............................ 4-414.6.3 Step 2: Review/Edit TWS Input Entry Panel........................................................................... 4-414.6.4 Step 3: Edit/Submit TWS Job Collection ................................................................................ 4-424.6.5 Step 4: View Results of TWS Job Collection.......................................................................... 4-43

4.7 Job Collection with ASG-Zeke ......................................................................................................... 4-444.7.1 Steps to Initiate ASG-Zeke Job Collection ............................................................................. 4-444.7.2 Step 1: Set Configuration Values for ASG-Zeke in BRMINI PARMLIB Member.................... 4-444.7.3 Step 2: Optional - Set Up Job Name Filtering for ASG-Zeke ................................................. 4-444.7.4 Step 3: Review/Update ASG-Zeke Input Entry Panel ............................................................ 4-454.7.5 Step 4: Edit/Submit ASG-Zeke Job Collection ....................................................................... 4-464.7.6 Step 5: View Results of ASG-Zeke Job Collection ................................................................. 4-48

4.8 Job Collection with ISPF Edit ........................................................................................................... 4-494.8.1 Steps to Collect or Edit Job Entries Using ISPF Edit ............................................................. 4-494.8.2 Step 1: Create/Edit Job Entries List and Job Structure Using ISPF Edit ............................... 4-504.8.3 Step 2: View Results of ISPF Edit Data Set Job Collection ................................................... 4-50

4.9 Job Collection with Pre-Staged Data Set......................................................................................... 4-51 4.9.1 Steps to Initiate Pre-Staged Data Set Job Collection............................................................. 4-524.9.2 Step 1: Set Pre-Staged Data Set Configuration Options in BRMINI PARMLIB Member ....... 4-524.9.3 Step 2: Create Your Pre-Staged Data Set.............................................................................. 4-524.9.4 Step 3: Review/Update Pre-Staged Data Set Input Entry Panel............................................ 4-534.9.5 Step 4: Edit/Submit Pre-Staged Data Set Job Collection....................................................... 4-544.9.6 Step 5: Review Results of Pre-Staged Data Set Job Collection ............................................ 4-55

4.10 Job Collection with a User-Supplied Data Set ................................................................................. 4-564.10.1 Step 1: Create Your User-Supplied Data Set ......................................................................... 4-564.10.2 Step 2: Review/Update Fields for User-Supplied Data Set Option ........................................ 4-564.10.3 Step 3: Submit User-Supplied Data Set Batch Job Collection ............................................... 4-564.10.4 Step 4: Review Results of User-Supplied Data Set Job Collection........................................ 4-56

4.11 Using Edit to Modify Job Scheduling Product's Job List/Structure .................................................. 4-574.12 Assigning Job Structure for Input Data Set Job Entries with the :STRUC Statement ..................... 4-57

4.12.1 Creating the Job Structure...................................................................................................... 4-58 4.12.2 Default Job Structure .............................................................................................................. 4-60

4.13 Batch Job Scan Command .............................................................................................................. 4-61

Mainstar Software Corporation ©2006 ix Contents SC23-6059-00



4.14 Using Job Name Filtering During Job Collection ............................................................................. 4-614.15 Reviewing Results of Job Collection ................................................................................................ 4-62

4.15.1 View Job Elements/Job Anchor Structures............................................................................. 4-63

5 SMF SCAN SETUP – Identifying Application Data Sets through Batch SMF............................... 5-15.1 About Batch SMF ............................................................................................................................... 5-25.2 Collecting Data Using Batch SMF SCAN........................................................................................... 5-3

5.2.1 SMF Record Requirements ...................................................................................................... 5-35.2.2 Batch SMF Data Set Requirements.......................................................................................... 5-45.2.3 Batch SMF Scan Process Overview......................................................................................... 5-55.2.4 Batch SMF Scan Procedure ..................................................................................................... 5-55.2.5 Run Batch SMF Scan to Collect SMF Data .............................................................................. 5-65.2.6 Run Verification to Build Selection Data Set............................................................................. 5-75.2.7 View the Results of Your SMF Collection ................................................................................. 5-85.2.8 Job Submission Sequence ..................................................................................................... 5-115.2.9 Reviewing the Results of the Batch SMF Scan ...................................................................... 5-12

6 VERIFICATION – Creating the Selection Data Set .......................................................................... 6-16.1 Overview of the Verification Process ................................................................................................. 6-26.2 About Selection Data Sets and Output Formats ................................................................................ 6-3

6.2.1 Selection Data Set Contents – ABARS .................................................................................... 6-36.2.2 Selection Data Set Contents – Non-ABARS............................................................................. 6-46.2.3 Data Set Types and Output Selection Formats ........................................................................ 6-4

6.3 Invoking Selection Data Set Verification ............................................................................................ 6-56.3.1 Building the Selection Data Set in Foreground......................................................................... 6-56.3.2 Building the Selection Data Set in Batch .................................................................................. 6-7

6.4 Scheduling Application Backups ........................................................................................................ 6-86.5 Adding Data Sets to the Application Selection Data Set During Verification ..................................... 6-86.6 Verification Output Selection Data Set Formats ................................................................................ 6-9

6.6.1 Output Formats & Supported Data Set Types .......................................................................... 6-96.6.2 Guidelines for ABARS Data Set Output Formats ................................................................... 6-12

6.7 Reviewing the Results of Verification............................................................................................... 6-136.7.1 Using STATUS (Option 6) from the Application AutoBuild Options Menu ............................. 6-13

6.8 Verification Global Options in BRMINI Member ............................................................................... 6-14

7 Real-time Selection Process (RSP) .................................................................................................. 7-17.1 Real-time Selection Process (RSP) Overview ................................................................................... 7-2

7.1.1 Choosing How to Set Up RSP for an Application ..................................................................... 7-27.1.2 Collection of SMF and JCL Records......................................................................................... 7-37.1.3 Processing Captured SMF and JCL Records........................................................................... 7-37.1.4 Viewing Captured SMF and JCL Records ................................................................................ 7-3

7.2 Performance & Usage Notes ............................................................................................................. 7-47.2.1 Reducing Data to Be Processed by RSP ................................................................................. 7-47.2.2 Avoiding Trouble with the RSP Cycles ..................................................................................... 7-4

7.3 Preparing an Application for RSP Data Collection ............................................................................. 7-57.4 System Configuration Modes and RSP Tasks ................................................................................... 7-67.5 RSP Job Reference Table: Use of RSPBLDJB & RSPJRFSH......................................................... 7-67.6 The APPLEND Program (End-of-Application)....................................................................................7-7

7.6.1 Coding the APPLEND Program................................................................................................ 7-87.6.2 APPLEND Errors .................................................................................................................... 7-107.6.3 Using Optional OpenTech VDR Filter Lists ............................................................................ 7-10

7.7 Summary of RSP Job JCL Members ............................................................................................... 7-107.8 RSP Message Log ........................................................................................................................... 7-117.9 RSP Monitor ..................................................................................................................................... 7-12

7.9.1 Display RSP Status – Option 1 ............................................................................................... 7-12

Contents x Mainstar Software Corporation ©2006 SC23-6059-00



7.9.2 Display RSP Statistics – Option 2 .......................................................................................... 7-137.9.3 Display Current Job Table – Option 3 .................................................................................... 7-167.9.4 Display Current Filter Table – Option 4 .................................................................................. 7-167.9.5 RSP Commands – Option 5 ................................................................................................... 7-17

7.10 RSPSMFTK (RSP) Operator Commands ........................................................................................ 7-187.10.1 Start the ASAP Started Task (RSP) and Individual Subtasks ................................................ 7-187.10.2 Start the ASAP Started Task by Jobname (RSP) and Individual Subtasks ........................... 7-197.10.3 Start the RSP Started Task without the Individual Subtasks.................................................. 7-197.10.4 Stop the RSP Structure .......................................................................................................... 7-19 7.10.5 Manipulate the IEFU83 Exit .................................................................................................... 7-207.10.6 Manipulate the IEFUJI Exit ..................................................................................................... 7-217.10.7 Manipulate the VSAM/ASAPUPDT Task................................................................................ 7-227.10.8 Manipulate the Overflow Tasks and RSP Monitor Task......................................................... 7-22

7.11 Real-time Selection Process – Operational Considerations ............................................................ 7-237.11.1 Back Up or Reorganize the ASAP Database While Leaving RSP Up ................................... 7-237.11.2 Selection Data Sets Must Be Physical Sequential (PS) ......................................................... 7-237.11.3 Normal IPL .............................................................................................................................. 7-237.11.4 RSP IPL Considerations – Shutdown..................................................................................... 7-237.11.5 RSP IPL Considerations – Startup ......................................................................................... 7-237.11.6 Surviving a System Outage .................................................................................................... 7-247.11.7 Surviving a System Outage (using Record Level Sharing) .................................................... 7-247.11.8 How RSPJRFSH and the Internal Job Table Works .............................................................. 7-24

7.12 What to Do If the Overflow Data Set Fills Up – B37 ........................................................................ 7-247.12.1 Monitoring the Overflow.......................................................................................................... 7-25

7.13 Increasing the RSP Buffer Size ....................................................................................................... 7-25

8 Obtaining Application Information ................................................................................................... 8-18.1 LIST APPLICATIONS – Option 1....................................................................................................... 8-2

8.1.1 Using the Application List Panels ............................................................................................. 8-28.1.2 Create Application List Panel ................................................................................................... 8-3 8.1.3 Using the Application List Panels ............................................................................................. 8-48.1.4 Application List Panel Primary Command Values .................................................................... 8-58.1.5 Application List Panel Column Commands .............................................................................. 8-58.1.6 Application List Panel Line Commands .................................................................................... 8-6

8.2 Application STATUS Display – Option 6............................................................................................ 8-78.2.1 Option 1 is N/A.......................................................................................................................... 8-88.2.2 Display Current JOB List .......................................................................................................... 8-88.2.3 Display Current Job Anchor Chains ......................................................................................... 8-98.2.4 Display Data Set Detail Records (RSP JCL, RSP, Batch SMF)............................................. 8-108.2.5 Display Current JCL/SMF DSN Entries .................................................................................. 8-128.2.6 Display Current JCL/SMF DSN Entries with URD Information............................................... 8-158.2.7 Display Summary of Last RSP Selection Data Set ................................................................ 8-168.2.8 Browse Selection Data Set Contents ..................................................................................... 8-16

9 FILTERS – Using Filters and Controls ............................................................................................. 9-19.1 Filters and Controls Overview ............................................................................................................ 9-2

9.1.1 Types of Information Filtered .................................................................................................... 9-29.1.2 Levels of Filtering...................................................................................................................... 9-29.1.3 Types of Filters ......................................................................................................................... 9-39.1.4 Categories of Filters.................................................................................................................. 9-3

9.2 Types of Filters................................................................................................................................... 9-49.2.1 Job Collection Filters Used with Job Scheduling Products ...................................................... 9-49.2.2 Data Set Retention Filters......................................................................................................... 9-49.2.3 Data Set Evaluation Filters ....................................................................................................... 9-6

Mainstar Software Corporation ©2006 xi Contents SC23-6059-00



9.2.4 How to Accomplish 'KEEP Only' or 'EVAL Only'....................................................................... 9-79.2.5 Data Set Include Filters............................................................................................................. 9-9

9.3 Levels of Filters ................................................................................................................................ 9-119.3.1 Universal Filters ...................................................................................................................... 9-119.3.2 Global Filters ........................................................................................................................... 9-129.3.3 Local Filters............................................................................................................................. 9-12

9.4 Creating and Displaying Filters ........................................................................................................ 9-139.4.1 Defining Filters When RSP Is Not Up .....................................................................................9-139.4.2 Defining Filters to Identify Data Outside 'Mirrored' Volumes .................................................. 9-139.4.3 Including or Excluding Migrated Data ..................................................................................... 9-139.4.4 Creating Universal and Global Filters ..................................................................................... 9-139.4.5 Modifying Local Application Filters: Retention and Evaluation Filters ................................... 9-169.4.6 Modifying Local Application Filters: Job Collection................................................................ 9-23

9.5 Mainstar Extended ACS Filtering Pattern Masks ............................................................................. 9-279.6 Your EBCDIC Code Tables – Specification and Display of EBCDIC Characters............................ 9-289.7 Reviewing the Results of Application Filtering .................................................................................9-289.8 Filtering Tips ..................................................................................................................................... 9-299.9 Using Optional OpenTech VDR Filter Lists...................................................................................... 9-29

A Batch JCL and Control Statement Reference ................................................................................ A-1A.1 APPLEND – RSP Application-End Control Statements.....................................................................A-2

A.1.1 APPLEND Errors ......................................................................................................................A-4A.1.2 Selection Data Set Output ........................................................................................................A-4

A.2 ASPC7JOB – Unicenter CA-7 Job Collection Procedure ..................................................................A-5A.3 ASPCM606 – CONTROL-M Job Collection Procedure .....................................................................A-6A.4 ASPESPEX – Cybermation ESP Job Collection Procedure ..............................................................A-7A.5 ASPJBTCV – Unicenter CA-Jobtrac Job Collection Procedure.........................................................A-8A.6 ASPTWJOB – TWS Job Collection Procedure ..................................................................................A-9A.7 ASPJOBZK – ASG-Zeke Job Collection Procedure ....................................................................... A-10A.8 ASPPRECV – Pre-Staged Data Set Job Collection Procedure ...................................................... A-11

B ASAP Reports and Utilities .............................................................................................................. B-1B.1 ASAPDSRS – Data Set Name Report ...............................................................................................B-2B.2 ASAPOVLP – ASAP Overlap Report .................................................................................................B-6B.3 ASPFLTRP – Filter Report .................................................................................................................B-9B.4 ASPCHKDB – DSD Record Count Report...................................................................................... B-10B.5 ASPMNT01 – Rename an ASAP Application ................................................................................. B-11B.6 ASPAPPCP – Copy an ASAP Application ...................................................................................... B-12B.7 ASPFILTR – Batch Filter Processing .............................................................................................. B-14 B.8 ASPDELAP – Delete Application .................................................................................................... B-20

Contents xii Mainstar Software Corporation ©2006 SC23-6059-00



Figures Figure 1-1: Major ASAP Components and Sequence for Creating an ASAP Application .................... 1-9Figure 1-2: APPLEND – Creating an Application's Selection Data Set .............................................. 1-18Figure 1-3: VERIFICATION – Creating an Application's Selection Data Set...................................... 1-19Figure 1-4: ASAP Batch or Real-time Monitoring and Updating......................................................... 1-33Figure 2-1: Backup & Recovery Manager Suite Main Menu................................................................. 2-2Figure 2-2: ASAP Main Menu ............................................................................................................... 2-2Figure 2-3: Application AutoBuild Options Menu .................................................................................. 2-6Figure 3-1: Application SETUP Options panel...................................................................................... 3-3Figure 3-2: How to Display Your Current SMS Aggregate Entries ....................................................... 3-7Figure 3-3: Job Collection Structure ..................................................................................................... 3-9Figure 4-1: Overview of the job collection process ............................................................................... 4-2Figure 4-2: Overview of the job structure concept showing multiple anchor jobs................................. 4-4Figure 4-3: Application Job Collection Method Panel ........................................................................... 4-6Figure 4-4: Unicenter CA-7 Input Entry Panel .................................................................................... 4-11Figure 4-5: Overview of CONTROL-M Job Collection Process .......................................................... 4-16Figure 4-6: CONTROL-M input entry panel ........................................................................................ 4-18Figure 4-7: Overview of CONTROL-M Batch Collection Job.............................................................. 4-21Figure 4-8: Application Job List........................................................................................................... 4-22Figure 4-9: Application Anchor Job Structures ................................................................................... 4-22Figure 4-10: Cybermation ESP input entry panel ................................................................................. 4-28Figure 4-11: Unicenter CA-Jobtrac input entry panel............................................................................ 4-32Figure 4-12: Example of modified forecast JCL using &SCHMEM symbolic ....................................... 4-38Figure 4-13: Unicenter CA-Jobtrac Collection Information panel for Output Schedule option ............. 4-39Figure 4-14: TWS input entry panel ...................................................................................................... 4-41Figure 4-15: ASG-Zeke input entry panel ............................................................................................. 4-45Figure 4-16: Overview of Pre-Stage Facility ......................................................................................... 4-51Figure 4-17: Display Current JOB Anchor Chains Panel ......................................................................4-59Figure 4-18: Anchor Job Structure ........................................................................................................ 4-60Figure 4-19: :STRUC Continuation Example ........................................................................................ 4-60Figure 4-20: ASAP Application Display Selections ............................................................................... 4-63Figure 4-21: Application/JOB List Elements ......................................................................................... 4-64Figure 4-22: Application ANCHOR Job Structures ............................................................................... 4-64Figure 5-1: Overview of the Batch SMF Scan Process ........................................................................ 5-5Figure 6-1: Selection Data Set Build Panel........................................................................................... 6-5Figure 6-2: Selection Data Set Build Foreground Options Panel ......................................................... 6-5Figure 6-3: ABARS Format ................................................................................................................. 6-10Figure 6-4: DFSMSdss (DSS) Format ................................................................................................ 6-11Figure 6-5: ASAP Application Display Selections ............................................................................... 6-13Figure 6-6: Browse Selection Data Set............................................................................................... 6-14Figure 8-1: Application Information Display .......................................................................................... 8-6Figure 8-2: Application Anchor Job Structures ..................................................................................... 8-9Figure A-1: APPLEND JCL Procedure ..................................................................................................A-2Figure A-2: ASPC7JOB JCL Procedure ................................................................................................A-5Figure A-3: ASPCM606 JCL Procedure ................................................................................................A-6Figure A-4: ASPESPEX JCL Procedure ...............................................................................................A-7Figure A-5: ASPJBTCV JCL Procedure ................................................................................................A-8Figure A-6: ASPTWJOB JCL Procedure ...............................................................................................A-9Figure A-7: ASPJOBZK JCL Procedure ............................................................................................. A-10Figure A-8: ASPPRECV JCL Procedure ............................................................................................ A-11

Mainstar Software Corporation ©2006 xiii Contents SC23-6059-00



Preface Preface.1 About This Book

Who Should Use This Manual

This manual is primarily designed for storage administrators and/or application programmers who use, manage, and perform monitoring of application backup functions within the DFSMShsm, FDR, DFSMSdss, and Brightstor CA-Disk system releases.

Organization of This Manual

This manual describes:

• General information and background about ASAP and its use for application backup and storage management

• Major services provided by ASAP are: – Application job identification – SMF data collection, either using batch SMF Scan, or dynamically using RSP SMF

Capture – JCL data collection using RSP JCL Capture – Data set filtering – Final data set element Verification (building the application selection data set)

• The Dialog facility of ASAP used to review current application status information and tape backup changes

• How to access error handling and messages

Reader’s Comments

We want to receive your comments about this manual. Your suggestions about the accuracy, clarity, and format of this document will be appreciated.

Please document your observations and email to [email protected] or provide to Mainstar Technical Support via our website.

Let us know if you would like a reply, and provide your contact information.

Mainstar Software Corporation ©2006 1 Preface SC23-6059-00 ASAP Overview


mailto:[email protected]






Acronyms

BRM Backup & Recovery Manager Suite

CUA Common User Architecture

ESA Enterprise Systems Architecture/370

MVS/ESA MVS/SP Version 3

MVS/DFP MVS/DFP Version 3

DFSMS The Data Facility Storage Management Subsystem consists of:

DFSMS/MVS DFSMSdss DFSMSdfp RACF DFSMShsm DFSORT ABARS

RSP Real-time Selection Process

Preface 2 Mainstar Software Corporation ©2006 ASAP Overview SC23-6059-00



Preface.2 Where to Find More Information

Publications in the Backup & Recovery Manager Suite Document Set

• Backup & Recovery Manager Suite Installation & Maintenance Guide (document GC23-6062)

• Backup & Recovery Manager Suite User Guide for ABARS Manager (document SC23-6060) • Backup & Recovery Manager Suite User Guide for All/Star (document SC23-6061) • Backup & Recovery Manager Suite User Guide for ASAP (document SC23-6059)

How to Contact Us for Technical Support:

• Mainstar Technical Support • Phone: 1-425-455-3589 • Fax: 1-425-455-1992

How to Contact Us for Product Information:

• Send an email to

[email protected]

• In North and South America

Mainstar Software Corporation Worldwide Headquarters P.O. Box 4132 Bellevue, WA 98009 U.S.A. Tel: 1-425-455-3589 or 1-800-233-6838 Fax: 1-425-455-1992

• In Europe

Mainstar Software Corporation Ltd. Sanderum House Oakley Road Chinnor Oxon OX39 4TW England Tel: +44-(0)1844-347173Fax: +44-(0)1844-346627

• In Asia Pacific

Mainstar International Ltd. P.O. Box 1624 Macquarie Centre North Ryde, NSW 2113 Australia Tel: +61-(0)2-9888-1777 Fax: +61-(0)2-9888-1588

Mainstar Software Corporation ©2006 3 Preface SC23-6059-00 ASAP Overview


http://www.mainstar.com/services/support/techsupport/index.asp



Visit Our Web Site – www.mainstar.com

• Current release information • Product information • Interesting and informative White Papers and articles • Online presentations • Sign up for an online seminar

Preface 4 Mainstar Software Corporation ©2006 ASAP Overview SC23-6059-00



Chapter 1 1 ASAP Overview

This chapter presents an overview of the concepts of ASAP processing, and a high level explanation of how to use the product.

Contents:

• About Backup and Recovery Manager Suite – page 1-2

• What Is ASAP? – page 1-2

• What Does ASAP Do? – page 1-4

• ASAP Cross-Reference to Backup & Recovery Manager Suite: All/Star – page 1-4

• ASAP Functions, Methods, and Support – page 1-5

• How Does ASAP Work? – page 1-9

• Preparing for ASAP – page 1-10

• Simple Steps to Get Started Using ASAP – page 1-13

• Step-by-Step ASAP Setup Options – For Forward Recovery – page 1-21

• Step-by-Step ASAP Setup Options – For Rerun Recovery – page 1-27

• Monitoring Application Changes – page 1-33

• ASAP Batch Job Submission Sequence – page 1-34

Mainstar Software Corporation ©2006 1-1 Chapter 1 SC23-6059-00 ASAP Overview



1.1 About Backup and Recovery Manager Suite ASAP is one of three selectable products in the Backup and Recovery Manager Suite of products. Backup and Recovery Manager Suite consists of one common install, common panels, three selectable products, a common inventory data set used by ABARS Manager and All/Star, and a separate database for ASAP. Backup & Recovery Manager Suite is designed to meet your company's business resiliency needs either locally, or in the event of a disaster, from the minor to catastrophic. Backup and Recovery Manager Suite offers the following products and features:

• ABARS Manager: – enhances and extends ABARS functionality – centralizes management of ABARS to make ABARS easy to use – consolidates and manages essential tracking, status, and resource information – adds functionality not included in native ABARS – provides selectable feature Incremental ABARS for true ABARS incremental support

Selectable features for ABARS Manager:

– CATSCRUB, designed for full volume restore, enables you to quickly synchronize one or more BCS catalogs with associated DASD volumes at your disaster recovery site.

– Incremental ABARS enables you to perform ABARS backups on an incremental basis. • All/Star:

– centralizes and inventories z/OS backups so you can recover anywhere, anytime – identifies what isn’t backed up at your site

Selectable features for All/Star:

– CATSCRUB, designed for full volume restore, enables you to quickly synchronize one or more BCS catalogs with associated DASD volumes at your disaster recovery site.

• ASAP: – identifies critical business data as the application executes – identifies the data that needs to be backed up for business resiliency, either onsite,

offsite, or both, and builds the list as input to a backup utility • ASAP and All/Star, when used together:

– use the list created by ASAP to compare to what was actually backed up – provide documented evidence that critical assets have a backup – provide proof that critical business data is offsite if required – alert on critical assets that don’t have a backup

Backup & Recovery Manager Suite panels provide access to functionality common to all three products, ABARS Manager, All/Star, and ASAP, and are named either Backup & Recovery Manager Suite or BRM. ABARS Manager panels are named either ABARS Manager or ABM, All/Star panels are named either All/Star or AST, and ASAP panels are named either ASAP or ASP.

ABARS Manager and All/Star share the same Backup & Recovery Manager Suite Inventory Data Set, and ASAP has its own ASAP Database.

1.2 What Is ASAP? ASAP is a sophisticated systems software product that provides a set of tools for storage administrators to use to implement and manage an installation's application backup strategy for business resiliency, either disaster recovery or local recovery.

Companies continue to back up unnecessary data sets daily by mask or by manual lists that are often not maintained because identifying data is a daunting, nearly impossible task without ASAP.

ASAP automates the task of identifying the critical data that needs to be backed up or compared to what was backed up to find missing data sets. ASAP saves resources by discovering the data as it

Chapter 1 1-2 Mainstar Software Corporation ©2006 ASAP Overview SC23-6059-00



executes and providing a current list, instead of by backing up data daily by mask or manual lists that contain more data than is required.

Using information from an array of OS/390 or z/OS sources, ASAP automatically constructs a list of the data sets used by the application each and every time the application is executed. The list of critical data sets is immediately available as input to a backup, or to compare to what was backed up, or as an analysis tool.

• ASAP constructs a picture of an application, using information from several different sources, such as job scheduling products, JCL libraries, and SMF records, which allows the storage administrator or ASAP implementer to determine which data sets should be included as part of an application backup, and which ones could be excluded.

• ASAP ensures that all critical data is included. ASAP will also reduce the total amount of backup data by identifying it as it is used instead of identifying it by mask, which would include daily, weekly, monthly, and quarterly backups. Backing up only the data required reduces the cost of backup and recovery.

• ASAP includes facilities to automatically detect application changes that may require changes to the backup selection criteria.

• ASAP provides reporting capabilities. • ASAP provides an easy-to-use ISPF interface. • ASAP supports remote mirroring to track tape data or data that should be mirrored, but isn't. • ASAP is a companion product to Backup & Recovery Manager Suite: ABARS Manager and

All/Star.

ABARS Manager is Mainstar's advanced system for providing improved capabilities to users of IBM's Aggregate Backup and Recovery Support (ABARS) and DFSMShsm Incremental backup display and HRECOVER. ABARS Manager provides complete aggregate backup and recovery tracking, recovery of individual data sets from an aggregate backup, enhanced aggregate backup data set selection criteria, and many other extensions to the ABARS environment.

All/Star is Mainstar’s advanced system for intercepting and centralizing all other z/OS backups (DFSMSdss, FDR, IEBCOPY, IDCAMS, IEBGENER, SORT, etc.), including the ability to find out what isn’t backed up.

Used together, ASAP, ABARS Manager, and All/Star provide a complete system for creating, implementing, tracking, and managing backup and recovery activity.




1.3 What Does ASAP Do? Before an application backup can be performed, the data sets associated with the application must be identified. This is the single most important task in implementing application backup, and without ASAP, it is also often the most tedious and error-prone task in application backup.

Through the use of various methodologies, functionality, and support capabilities (overviews of these are provided in the next topic), ASAP provides System Administrators the tools they need to complete data set identification in even the most complex processing environments.

ASAP begins by pulling together information about an application's jobs and job structure from sources such as job schedulers, job name masks, or user created lists. And then, using available information from the application's JCL libraries, system SMF records, and user-supplied data, ASAP automates the task of determining which data sets belong to an application and how critical they are to the application's successful backup and recovery. This information is stored in the ASAP Database and used to create the list of data sets to back up, or the selection data set just before the application backup. ASAP supports the list of data sets to be backed up in the following output formats: ABARS, DFSMSdss, FDR/ABR, Brightstor CA-Disk, or generic list format.

After the initial list or selection data set has been created, ASAP monitors changes to an application's data set usage, and automatically maintains a current selection data set for use in backing up the application for disaster recovery or local recovery.

1.4 ASAP Cross-Reference to Backup & Recovery Manager Suite: All/Star If both ASAP and All/Star are licensed, additional optional features are available in the Application Backup and Restore feature of All/Star:

• Ability to compare ASAP critical data set list against All/Star discovered backups. • Ability to restore data sets for ASAP applications and specific cycles within an application. • Reports to compare to TMS to ensure that tapes are offsite if required. • Provide confidence and proof that critical data is backed up. • Provide alerts for those data sets that aren’t backed up.

The following options in ASAP support these features:

• Setup Option: BACKUP CYCLES TO RETAIN • Filter: EXCL_BUT_CRITICAL

For more information about BACKUP CYCLES TO RETAIN, see the topic 'BACKUP OPTIONS' (page 1-24). For more information about the EXCL_BUT_CRITICAL filter, see the topic 'Data Set Evaluation Filters' (page 9-6).

For more information about these features, see Chapter 12, All/Star: Application Backup and Restore of the Backup & Recovery Manager Suite User Guide: All/Star.




1.5 ASAP Functions, Methods, and Support

1.5.1 Mirroring Support ASAP mirroring support:

• Helps verify you are mirroring all of the correct data sets.

If the data sets (for example on volumes, PROD*) are being mirrored and you need to identify any data sets for those applications that were allocated on volumes outside that pool (outside of the mirrored volumes), you can define to ASAP all applications on the PROD* volumes. ASAP will in turn track the applications as they execute.

Normally at the end of an application, you would execute the ASAP APPLEND program that builds a list of data sets to back up. The APPLEND is then followed by a backup. However, in the case of identifying data sets on volumes that fall outside the mirrored volumes, you can exclude any data sets in the PROD* pool because you already know these data sets are being mirrored, and instead, run APPLEND for each application without following it by a backup. APPLEND will build a list of data sets and corresponding VOLSERs for those data sets allocated on volumes other than PROD*. ASAP will help verify you are mirroring the correct data sets if you identify all the applications to it that reside in that pool, let ASAP track them, and review the selection data set (or list of data sets) on a daily basis to identify those data sets not on mirrored volumes.

• Identifies data sets on specific volumes.

The selection data set (or list of data sets) built by ASAP displays the data set name, and the VOLSER. You can visually see which pool or volume each data set is in. If it is supposed to be on a PROD* volume and it is on a TEST volume, or another volume that is not mirrored, you need to take action.

• Identifies tape data sets.

ASAP identifies data that is on tape. Again, the applications need to be tracked by ASAP. By excluding all data on volumes other than TAPE, ASAP will provide a list of tape data that you can verify is duplicated through another method. ASAP does not determine tape sizing, only that the data set is on TAPE.

• Identifies migration level 2 tape data sets.

ASAP identifies data and distinguishes between ML1 and ML2. Again, the applications need to be tracked by ASAP. By excluding all data on volumes other than TAPE and MIGRAT2, ASAP will provide a list of the tape data that you can verify is duplicated through another method.

• Identifies data required for point-in-time backups.

Even though you are mirroring data, if you are mirroring batch data, you still need a point-in-time backup. If an error occurs in batch, and is duplicated to the mirrored DASD, you may not be able to back out of the error because it was also duplicated at your remote site and there was no point-in-time backup.




1.5.2 Forward vs. Rerun Recovery Determining which data sets are critical can be a complex task without ASAP. Detailed decisions depend largely on the planned recovery methodology. Each organization needs to make specific decisions about each application as to whether forward recovery (sometimes called forward resumption) or rerun recovery will be used.

Forward Recovery – assumes the backup is taken at the end of an application cycle, or at various points within an application. At the disaster site, the application is restored and then continues forward with the next processing cycle. This methodology requires that any output data sets needed as input for the next cycle are included in the application backup. Forward recovery is the simplest method of implementation.

Rerun Recovery – assumes the input data sets are backed up before the beginning of application cycle processing. At the recovery site, the application is restored and the last cycle is rerun. Output data sets are recreated during the rerun of the application. This methodology requires that only critical data sets (inputs to the application) are included in the application backup. Non-critical data sets (outputs) are not included, as they consume backup time and resources. Rerun Recovery is generally more difficult to implement but cheaper to create because less data is backed up.

ASAP provides automated support of Rerun Recovery and substantial support for forward recovery. Override and option settings are available either globally or at the application level to assist the analyst in configuring ASAP to operate in the mode desired. Determining the recovery methodology, performing the analysis on the necessary settings, and overrides to ASAP operation, are important responsibilities of the using organization.

Once ASAP is configured for an application's recovery objectives, the application can be tracked and backed up in an automated fashion. ASAP will routinely analyze the data sets in use, and create selection data sets just before the backup process is performed. This routine re-analysis of the application will identify and track a variety of time-related issues, such as application maintenance, varying application cycle behavior, and unusual data set naming techniques.

1.5.3 Selection Data Set Output Formats ASAP writes the list of data sets to back up in the following output formats, ABARS, DFSMSdss, FDR/ABR, Brightstor CA-Disk (DMS) and list format.

Companion products ABARS Manager and All/Star, products in the Backup & Recovery Manager Suite, are recommended to provide z/OS-wide backup tracking, management reporting.

1.5.4 The ASAP Database The ASAP Database, a VSAM KSDS file structure, is used to maintain and track application information. The ASAP Database is the long-term memory of the process, providing a repository for user overrides, application level selection and analysis options, and details of job and data set collection and data set activity. ASAP uses application information from the ASAP Database to create selection data sets in the various supported formats.




1.5.5 Interfaces to Job Scheduling Products Information about an application's jobs and job dependencies are collected by ASAP using multiple methods to gather information from a variety of sources. One method uses interfaces to a variety of job scheduling products:

• ASG-Zeke for z/OS • BMC CONTROL-M for z/OS • Cybermation ESP • Tivoli Workload Scheduler (TWS) • Unicenter CA-7 Job Management • Unicenter CA-Jobtrac Job Management

1.5.6 Job Name Masks Job name masks are another method that can be used to gather information about an application's jobs. Job name masks can be used when creating job lists using the ISPF panels.

1.5.7 Critical Data Set Identification The information gathered by either the job scheduling product interfaces or other job collection methods is stored in the ASAP Database. The RSPJRFSH JCL (in the product JCL library), is run next to update the started task, RSP, with the jobs collected so it knows which jobs to track. This job can either be executed manually, or it can be automated. When an application runs, the RSP started task records JCL and batch SMF and/or real-time SMF data for the jobs that ran that day to complete the evolving picture of data set criticality. JCL provides data set names that may be missed by SMF because they were never opened or closed. SMF data provides detailed information about data set usage (input, output, etc.), and identifies dynamically allocated data sets, and dynamically generated JCL statements that are otherwise not apparent. By marrying this information together when using the APPLEND JCL (in the product JCL library), you will have a complete picture of your application to support either forward recovery or Rerun Recovery.

ASAP optionally scans your installation's history SMF data to find data sets that belong to jobs associated with an application run in the past. Various SMF record types are used by ASAP during its SMF analysis. Before starting ASAP, ensure that your installation is collecting the necessary record types. The same record types are also used by RSP (Real-time Selection Process). If batch SMF processing is to be used, the names of the SMF data sets that ASAP is to examine can be specified in the BRMINI member of the PARMLIB.




1.5.8 ASAP Real-time Selection Process (RSP) Once an application is placed under ASAP administration, the ASAP Real-time Selection Process (RSP) should be used to continuously monitor the activity of the application to ensure that the application selection data sets are always current and accurate.

Using a powerful tool like RSP is important because most application programmers:

• Have not worked with the application since its inception, so they do not know all the files in the application.

• Work on a subset of an application, not the whole application. • Can't know every single data set and, being human, can forget a data set.

Without ASAP, ensuring that the application selection data sets are always current and accurate is almost impossible.

• Applications can be large, making it easy to miss data sets. • Even if data is identified, do you build one list and back it up every day? • Who maintains changes over time to ensure new data is backed up? • What if an important data set is missed?

RSP is a key component of an effective ASAP deployment. In extremely simple and static environments, the initial setup of an ASAP application may remain current and valid for some time, and RSP may appear to be an unnecessary degree of sophistication. However, in the general environment, there is a strong need for the application visibility, and the immediate activity information that RSP provides. The importance of this facility to the establishment and maintenance of an effective disaster recovery capability can not be overstated.

Because of the continuous, real-time nature of RSP, application changes are immediately recognized, and the next backup will automatically reflect the changes, ensuring that you have all the data required for backup.

• RSP SMF Capture – uses a standard IEFU83 SMF exit facility to collect SMF data in real time, which it then uses to re-analyze the criticality of data sets in the application.

• RSP JCL Capture – uses a standard IEFUJI SMF exit facility to collect interpreted JCL information in real time.

In addition, a variety of typical but troublesome processing modes can be effectively handled, such as applications that run overlapping cycles, and applications that create or use pseudo-GDG data sets (data sets whose names change in some systematic but non-standard manner). RSP uses an added job step, the application end step, to signal the completion of a processing cycle. There can be one, or many, application end steps in an application job stream, depending on the complexity of job relationships. The application end step signals RSP that a full cycle has been completed, permitting a thorough (and immediate) re-evaluation of the data set criticality matrix for the application, and the re-creation of the selection data set.




1.6 How Does ASAP Work? ASAP automatically generates selection data sets used for ABARS, DFSMSdss, FDR/ABR or Brightstor CA-Disk backups, and monitors the application to ensure that they are correct.

Overviews of the ASAP functions are provided below. Each function is covered in detail in separate chapters of this user guide. The chapters are presented in the sequence that the function is used for creating and monitoring an ASAP application. Figure 1-1 shows the components of ASAP.

Figure 1-1: Major ASAP Components and Sequence for Creating an ASAP Application

RSP

ASAP Database

ASAP Identifying Critical Application Data Sets for DR

Application Setup Job Collection

APPLEND or VERIFICATION: Critical Data Set

Entries

Monitor Application

Changes -SMF Capture -JCL Capture

CA-7 Recovery Forward

CONTROL-M -or- ESP Rerun CA-Jobtrac Recovery TWS

ZEKE-or-Manual Input

Critical Critical

Real-time Collection of

Data Sets

Data Set List Data Set List

Updates Selection Data Set

RSP JCL Capture RSP SMF Capture Batch ASAP Audit




1.7 Preparing for ASAP A checklist is provided at the end of this topic to help you track the information gathered during this task for each application defined to ASAP.

Preparing for ASAP begins with the installation and configuration of ASAP (and Backup & Recovery Manager Suite if it will be used to provide automated management of application backups).

During ASAP configuration:

• The ASAP Database is created. • Installation default values are set. • The RSP environment is defined and initialized.

See the Backup & Recovery Manager Suite Installation & Maintenance Guide for details about configuring your environment.

Once ASAP is configured, you must gather some information for ASAP to use to create the selection data sets for an application.

• Define to ASAP the names of the jobs that make up the application, and their sequence or structure.

• Either the started task Real-time Selection Process (RSP) or Batch SMF Scan must be used by ASAP. If you plan to use Batch SMF (not recommended; see the considerations in Chapter 5, SMF SCAN SETUP – Identifying Application Data Sets through Batch SMF), then the names of the SMF data sets must be specified.

1.7.1 Identify a Contact Person for Each Application When converting an application to a managed backup, questions will arise as to which jobs and data sets make up the application, their size, usage patterns, and importance. The application owners are the ones who know their data best. Even if the ASAP process will be performed by a central Storage Administration group, it will be necessary to have available someone who knows the application well and can answer questions and resolve problems that will inevitably occur.

1.7.2 Identify the Applications/Job Streams to Be Analyzed by ASAP Before beginning the ASAP process, decide which applications are to be processed. ASAP considers an application to be a group of related jobs. The data sets created and accessed by these jobs are the ones that ASAP will include in the selection data set for backup.

An ASAP application need not include all jobs that make up an application. For example, the Finance application may consist of several separate job streams, such as one for Accounts Payable, another for Accounts Receivable, and so on. Each of these smaller applications can be defined to ASAP separately if needed. The important point is that the user, who is to perform the ASAP analysis, knows which jobs create/update critical data sets necessary for disaster recovery of the application.




1.7.3 Using Scheduler Interfaces If you use the Unicenter CA-7 scheduler interface, ASAP needs to know the name of the Anchor job for the application in order to identify the jobs related to an application. This job is typically (though not necessarily) the first job in the application job stream, and provides a reference point for the application.

If you are using a scheduler interface such as CONTROL-M, you will be using tables instead of Anchor jobs.

By examining the JCL and SMF records from one reference point to the next, ASAP can accurately determine which data sets are critical for application backup and which are optional.

Some applications are comprised of several job streams. ASAP needs the name of the Anchor job or tables for each job stream.

Information about which jobs are Anchor jobs or tables can usually be obtained from whomever has been identified as the contact person for the application. However, if job names are specified using a job name mask, ASAP can determine from the job scheduling system which jobs are Anchor jobs.




1.7.4 ASAP Application Checklist Complete the tasks identified in the topic 'Preparing for ASAP' (page 1-10), and 'Application General Setup Section' (page 3-6), before using ASAP to generate the selection criteria for input to a backup.

Use this checklist to help you keep track of the information you gather for each application to be defined to ASAP.

APPLICATION CHECKLIST FOR ASAP

Application Name:

Application Description:

Contact Person:

Anchor Job Names Job Tables or Job Name Masks:

Selection DSNs:

ASAP Database:

Does the User or Batch ID that will be used to run ASAP have READ access to the PROCLIBs, job scheduling product files and SMF data sets?

Does the User or Batch ID that will be used to run ASAP have WRITE access to the ASAP Database and selection data sets?

Have all appropriate SAF authorities been assigned? See the Backup & Recovery Manager Suite Installation & Maintenance Guide, Appendix A, Authority Requirements.




1.8 Simple Steps to Get Started Using ASAP Each of the steps in the step table below is discussed in separate topics below. This is only an overview. The functions are described in detail in separate chapters, which are referenced within the topics.

STEP

1

STEP DESCRIPTION

Complete ASAP SETUP for Application. Completing SETUP tells ASAP how the application is to be managed.

2 Perform a Job Collection. via: • scheduler interface or • ISPF Edit – job name mask or • user defined data set. Collecting the application's job structure tells ASAP which jobs belong to the application, and any job scheduling product used to run the application.

3 Refresh the Job Table. Run RSPJRFSH each time a job collection is run through a scheduler, through ISPF Edit with job name masks, or a user defined pre-staged data set, so the started task or Batch SMF knows which jobs to track.

4 Identify the Application's Data Sets. Use JCL and SMF data to determine which data sets are used by the application, and of these, which are required for application recovery.

5 Run the Application. Run the application and record the data set information in the ASAP Database.

6 Create the Selection Data Set. For RSP, issue the APPLEND program. APPLEND signals the end of the application and builds the selection data set. For Batch SMF, issue the VERIFICATION program. VERIFICATION takes the records from the database and builds the selection data set.

7 Create Filters – Optional.

8 Verify the Data Sets Identified by ASAP Were Backed Up. Run All/Star BKUPEND program (requires All/Star product).

1.8.1 Step 1: Complete ASAP SETUP for Application Defining an application to ASAP describes which job collection method will be used, and whether the application is set up for Forward or Rerun Recovery. The SETUP option is where you will define, for each application, information such as Forward or Rerun Recovery methods, and GDG support options. This information is used by ASAP to determine which data sets belong to the application and their criticality for backup. See Chapter 3, SETUP – Defining an Application to ASAP.




1.8.2 Step 2: Perform a Job Collection A job collection is required to identify the jobs that belong to an application. Once identified, ASAP can track them by application. This is the starting point for ASAP. Without knowing which jobs belong to an application, ASAP can not collect data for them.

Job collection can be performed through a job scheduling interface, using the ISPF Edit option via job name or job name masks, or through a pre-staged data set. The information gathered by either of these methods is then placed in the ASAP Database for later use by other steps in the data gathering process.

If you use a job scheduling interface, ASAP automatically invokes the scheduling interface program and reads the output contents of a scheduling report to obtain the application information required. The advantage of this feature is to automatically identify job names for an application.

If you use ISPF Edit, you must know the job name naming conventions. The advantage of this feature is that by providing a mask that matches the job name convention, you do not need to run additional job collections when new jobs are added to the schedule. By using a mask, they will be automatically captured. An example of the masking capability is shown in the example below.

Mask Description

* Used in front and/or at the end of the name, as a 'wild-card' character mask.

< Used to represent a single alpha-only character.

> Used to represent a single numeric-only character.

% Designates a single character (any type) placeholder value.

! Designates a single national character placeholder value. (i.e., @ # $)

Example:

JOBNAME INClude(s) => PET%%34* PEFFR* PROD76* *CSRD*

When you define an application to ASAP, you must indicate which job collection method your installation is using.

For additional information about using the supported job scheduling products or Job Name Masks with ASAP, see Chapter 4, JOB COLLECT – Collecting Application Job Structure.




1.8.3 Step 3: Refresh the Job Table This step updates the Job Table with the jobs collected. When a job collection is done, the jobs are stored in the ASAP Database. The Job Table (a separate file) is not automatically updated because you may want to review the jobs first, before collecting data for them.

Before an application can be tracked by the started task (RSP), or Batch SMF, the Job Table needs to be refreshed from the ASAP Database. All data collection methods read the Job Table. RSPJRFSH, a member of the ASAP product JCL library, should be executed each time a job collection is run, to populate the Job Table with the new jobs to track.

1.8.4 Step 4: Identify the Application's Data Sets Before an application backup can be performed, the data sets associated with the application must be identified, and analyzed for how they are used. Identifying the data sets associated with an application is the single most important task in implementing application backup.

An important part of ASAP analysis is the use of the started task (RSP) to identify all JCL and SMF data to determine which data sets are used by the application, which are required for backup and recovery, and which are considered optional. You can also use Batch SMF to identify only SMF data.

• JCL data is obtained real-time using the IEFUJI exit. JCL data is not available for Batch SMF processes.

• SMF data is obtained either real-time by using RSP to identify current data through the IEFU83 exit, or by using Batch SMF to identify historical data.

Real-time Selection Process (RSP) – JCL Capture

• Identifies all data sets in the JCL, even data sets in steps not executed or data sets not opened, including concatenated libraries.

Real-time Selection Process (RSP) – SMF Capture

• Identifies all data sets that have been opened & closed, deleted, renamed or allocated. • Identifies dynamically allocated data sets.




Optional – Batch SMF

Batch SMF is intended for trials when the customer site isn't prepared to have RSP up, or for historical analysis of an application. Note however that there are inherent limitations with a BATCH SMF process.

• Batch SMF data may be unreliable for 'Rerun Recovery' because it may be difficult to pinpoint the exact start of the application. Rerun Recovery relies on the first reference of a data set, but what Batch SMF sees as the first reference may not be the first reference at all, completely skewing the results.

• Batch SMF data is more reliable for 'Forward Recovery' – using 'All Data Sets are Critical' because both inputs and outputs are considered critical. But again, it may be difficult to pinpoint the exact start of the application and the issues described below also make it unreliable.

• Because JCL data can not be collected in addition to Batch SMF data, steps that are skipped within a job will be excluded completely from the Batch SMF process.

• Most likely, the GDGs referenced in Batch SMF will either no longer be on the system, or they will be out of date.

• Most likely, a great number of non-GDG data sets will have been deleted.

While Batch SMF will give you an idea of what has been used, it is not foolproof data for monthly, quarterly, etc. analysis.

Any batch SMF data collected should reflect at least one complete processing cycle for the application. For example, if the application runs weekly, then at least a week's worth of SMF data should be collected. If the application runs monthly, then a month's worth of SMF data will be needed. Be aware that if a sample includes more than one cycle of an application, incorrect analysis may result. Control of the sample is the user's responsibility.

Various SMF record types are used by ASAP during its SMF analysis. Before starting ASAP, you should ensure that your installation is collecting the necessary record types. The same record types are also used by RSP (Real-time Selection Process). The names of the SMF data sets that ASAP is to examine can be specified in the BRMINI member of the PARMLIB.

Refer to Chapter 5, SMF SCAN SETUP – Identifying Application Data Sets through Batch SMF and Chapter 7, Real-time Selection Process (RSP).




1.8.5 Step 5: Run the Application Using RSP, each job submitted to the system is scanned by the IEFUJI exit to identify each data set in the JCL, even the PROCLIBs. As jobs execute, system SMF records are created for each data set that records whether a data set has been read, updated, renamed, or deleted. RSP intercepts each SMF record before the record is written to the system SMF MANX and MANY data sets. These JCL and SMF records are written to the ASAP Database as 'raw' records, or data set detail records (DSD) and can be found by bringing up ASAP through the ISPF interface, selecting the given ASAP application, selecting option 6 (STATUS), then option 4 (Display Data Set Detail Records (JCL, RSP, Batch SMF)).

If you are viewing the raw records and no records are displayed, it is because they are still resident in the dataspace buffers, or overflow file. A buffer flush can be requested by using the RSP Monitor described in Chapter 7, Real-time Selection Process (RSP).

Using Batch SMF, the SMF records are written to the ASAP Database but no JCL entries are recorded.

1.8.6 Step 6: Create the Selection Data Set Now that the application has run, and the data has been collected and stored in the ASAP Database, the selection data set (list of data sets to back up) can be created in two ways:

1. If the started task, Real-time Selection Process (RSP) collected the data, the data is now in the ASAP Database. To build the selection data set, execute the 'application end' program (APPLEND) found in the product JCL library. Modify the JCL with the correct application name. APPLEND marries the SMF and JCL records by date and time stamp that is necessary if the application has run on more than one system. APPLEND then analyzes the data sets as either critical or non-critical based on each application's settings in Option 0 (SETUP) from the Application AutoBuild Options Menu. Option 0 is the setup option for the application that has settings for either Forward Recovery, or Rerun Recovery and Filters. APPLEND converts the data set detail records (DSD – raw records) to data set records (DSR – analyzed records), and writes the selection data set.

2. If Batch SMF collected the data, the data is now in the database. To build the selection data set, execute 'VERIFICATION'. Verification evaluates the data sets and builds the selection data set.

1.8.7 Step 7: Create Filters – Optional Optional filters can be defined. See Chapter 9, FILTERS – Using Filters and Controls. Filters can be created before you collect any data so the analysis includes them upon APPLEND, or Verification, or can be done after the data collection and re-analyzed by using Verification to rebuild the selection data set with the new filters.

Verification uses the DSD records for the last successful cycle and can be used over and over to determine the results that will be achieved by adding new filters without affecting the current cycle.



CriticalDataset List

Application Datasets

APPLEND


A Selection Data Set Created by APPLEND

A selection data set is created by APPLEND if the application is tracked using real-time JCL and SMF entries collected by RSP. The APPLEND (application end) started task is issued at the end of the application cycle, and ASAP automatically builds the selection data set. The selection data set is then immediately available to the backup.

Before creating the selection data set, the ASAP user may modify the selection criteria being used by ASAP. Any changes made are saved in the ASAP Database for later reference and reporting. See Chapter 7, Real-time Selection Process (RSP). Figure 1-2 shows how the APPLEND process creates an application's selection data set.

Figure 1-2: APPLEND – Creating an Application's Selection Data Set

ASAP Database

Selection Data Set Formats

Updates Selection Dataset

ABARS DFSMSdss/DFDSS DMS/OS/CA-DISK FDR LIST

ASAPDatabase

UpdatesSelectionData Set

Critical Data Set List

Application Data Sets

A P P L E N D




A Selection Data Set Created by Verification

If the selection data set is created by Verification, information is stored in the ASAP Database by executing Batch SMF, and the selection data set is built by running a VERIFICATION. Verification extracts the records from the ASAP Database, processes any filters and builds the selection data set. See Chapter 9, FILTERS – Using Filters and Controls. Figure 1-3 shows how the Verification process creates an application's selection data set.

Figure 1-3: VERIFICATION – Creating an Application's Selection Data Set

ASAP Database




ABARS DFSMSdss/DFDSS DMS/OS/CA-DISK FDR LIST

Application Data Sets

V E R I F I C A T I O N

Verification can also be used to re-evaluate data from either Batch SMF or RSP. For example, let's say you ran an APPLEND and the selection data set is built. Now you want to add some filters or change some settings, but first you want to know the effects of your changes. Simply make your changes and run Verification to see the results.

Verification uses the last cycle of data to rebuild your selection data set. The original data sets from the APPLEND will be analyzed based on Forward Recovery, or Rerun Recovery and any new filters. Verification extracts the records from the database, processes the filters, and builds the selection data set. The filters can be modified and another Verification run, until you achieve the results you are looking for. The filters will remain in ASAP and will be used each time APPLEND or VERIFICATION is executed.

See Chapter 6, VERIFICATION – Creating the Selection Data Set and Chapter 9, FILTERS – Using Filters and Controls.




1.8.8 Step 8: Verify the Data Sets Identified by ASAP Were Backed Up If both ASAP and All/Star are licensed, an optional feature is available to ensure that the data sets identified by ASAP have in fact been backed up, and that none were missed. This is especially helpful if you already have your backups in place and are not using the list from ASAP as input to a backup, but you are using it to compare to what was backed up. More information can be found in the Application Backup and Restore feature of All/Star:

• Ability to compare ASAP critical data set list against All/Star discovered backups. • Ability to restore data sets for ASAP applications and specific cycles within an application. • Reports to compare to TMS to ensure that the tapes are offsite if required. • Provide confidence and proof that critical data is backed up. • Provide alerts for those data sets that aren’t backed up.

The following options in ASAP support these features:

• Setup Option: BACKUP CYCLES TO RETAIN • Filter: EXCL_BUT_CRITICAL

For more information about BACKUP CYCLES TO RETAIN, see the topic 'BACKUP OPTIONS' (page 1-24). For more information about the EXCL_BUT_CRITICAL filter, see the topic 'Data Set Evaluation Filters' (page 9-6).

For more information about these features, see Chapter 12, All/Star: Application Backup and Restore of the Backup & Recovery Manager Suite User Guide: All/Star.




1.9 Step-by-Step ASAP Setup Options – For Forward Recovery

STEP

1

STEP DESCRIPTION

Access ASAP in one of two ways: 1. From the Backup & Recovery Manager Suite Main Menu, choose Option 3,

ASAP. 2. Type 'xxx' from the command line, where xxx = your product file PARMLIB

name. Type EX next to member ABRMGR.

2 From the ASAP Main Menu, choose Option 2, SELECT/CREATE APPL, and press Enter.

3 To define a new application, specify the application name in the 'Specify NEW Application Name' field. If an application name is already specified in the 'use current/OLD Application Name' field, overwrite it. Press Enter. Pressing Enter automatically puts you into Option 0 (SETUP) for the specific ASAP application you are defining. If you are using ABARS, notice the aggregate name at the top of the screen.

4 Enter the Application Setup Options as specified in the topic 'Enter the Application Setup Options for Forward Recovery' (page 1-22).

5 Submit job collection as described in the topic 'Submit Job Collection' (page 1-26).

If you are defining an application to use Rerun Recovery, use the procedure in the topic 'Step-by-Step ASAP Setup Options – For Rerun Recovery' (page 1-27).




1.9.1 Enter the Application Setup Options for Forward Recovery

Application General Setup

SETUP OPTIONS FOR APPLICATION ==> Application name you specified in the topic above.

Appl DESC => Enter descriptive text for the application.

Associate With ABARS Aggregate If you are using ABARS, and the aggregate already exists, the aggregate name will automatically be put here if it is the same name that is in ISMF. The ABARS aggregate name should generally be created first. For non-ABARS, the ASAP application name will be put here.

:

DATA SETS. panel.

One note of caution If you are using ABARS, and the aggregate already exists, ASAP will automatically put in the selection data set name below under a section called SELECTION

If you do not want to write to this selection data set, just change the name on this

JOB COLLECTION OPTIONS

Collection Mode REPLACE

Collection Structure ALL

COLLECTION OPTIONS

Collect data via SMF or JCL M

RSP OPTIONS

Next RSP cycle number: 0000000001 Displays the current RSP cycle number.

Number of RSP cycles to retain 1

Automatically delete old cycles Y

JCL OPTIONS

Next JCL cycle number: 0000000001 Displays the current JCL cycle number.

Number of JCL cycles to retain 1





BATCH SMF SCAN OPTIONS

Next SMF cycle number: 0000000001 Displays the current SMF Batch cycle number.

Number of SMF cycles to retain 1


CURRENT VERIFICATION OPTIONS

** denotes option settings required for the ASAP Forward Recovery process.

Apply FILTERING During VERification Y

Re-evaluate Data Set Entries Y

User Tape Data Sets as ACCOMPANY N ABARS option only. By specifying N, this option puts tape data sets in the Include list.

Category if 1st ref. DELETE E **

Category if 1st ref. RENAME OLD DSN E **

Category if 1st ref. RENAME NEW DSN E **

Use SMF data in selection data set Y

Use JCL data in selection data set Y

SELECTION Dsn Format ABARS, DSS, XSS LIST, DMS, FDR

RSP cycles to include in Sel. DS 0001

Evaluate all data sets as critical N ** This parameter indicates either Forward Recovery if Y, or Rerun Recovery if N.

Detailed comments in Sel. Data Set N




VERIFICATION GDG OPTIONS

** denotes option settings required for the ASAP Forward Recovery process.

GDS names in selection data set B

Evaluate GDG entries from JCL Scan Y

Evaluate GDG entries from SMF data Y

Expand Base only references N

Add entries for missing GDSes F **

CATEGORY FOR NEW GDS IF NEW GDS IS I ** ONLY REFERENCE TO GDG (FOR FORWARD RECOVERY ONLY)

ABARS category for missing GDSes I **

ABARS category for new generations I **

BACKUP OPTIONS

BACKUP CYCLES TO RETAIN Optional. Ignore if not using the Application Backup and Restore feature of All/Star. This field defines how many All/Star application cycles will be tracked by All/Star in the Backup & Recovery Manager Suite Inventory Data Set. Whereas the ASAP option (as defined by: Number of RSP cycles to Retain and Number of JCL cycles to Retain – found in Option 0 – Setup) allows nn cycles to be tracked, All/Star tracks cycles including the backup information found for each critical data set discovered by ASAP, hence allowing restoration of the data sets peculiar to a given application cycle. For more information on the Application Backup and Restore feature of All/Star, see Chapter 12, All/Star: Application Backup and Restore of the Backup & Recovery Manager Suite User Guide: All/Star.

NOTE: ASAP’s option to track more than one cycle only affects how many cycles' worth of raw input (i.e. SMF and JCL information) are saved. These records are called Data Set Detail records (DSD). If in the ASAP Application AutoBuild Options menu, Option 0 – Setup, the cycles ("Number of RSP cycles to retain" "Number of JCL cycles to retain"), are set higher than one (in general 1 is used and is not the number of application backup cycles tracked by All/Star), the DSD records for the various cycles are combined, and analyzed, and the result is the creation of Data Set Records (DSR). These records are built for the last cycle completed, and reflect the results of Option 0 – Setup Options, and filters. They are used to generate a selection data set (list of data sets). At any time, only one version of the DSR records exist.




SELECTION DATA SETS

VERIFY=> If using ABARS, the ABARS selection data set will be put here. If you are not using ABARS, or no aggregate exists, a default name will be used.

RSP/BATCH => If using ABARS, the ABARS selection data set will be put here. If you are not using ABARS, or no aggregate exists, a default name will be used.

Press Enter to save changes. You will now be brought to the Main Application Menu. The application name will be displayed on the top of the panel. You were just in Option 0 (Setup).




1.9.2 Submit Job Collection

STEP

1

STEP DESCRIPTION

From the ASAP Application AutoBuild Options menu, select Option 1 for JOB COLLECT and press Enter.

2 From command == > Select the option from ISPF Edit. (or the appropriate scheduler) • If using a job name mask, see Step 3. • If using a scheduler interface, see the topic 'Interfaces to Job Scheduling

Products' (page 1-7).

3 Leave in the comments. Type each job name in column 1 (unless using the scheduler). Press Enter and End when finished. If using ISPF Edit, there are numerous masking characters: * Used in front and/or at the end of the name, as a 'wild card' character mask. < Used to represent a single alpha-only character. > Used to represent a single numeric-only character. % Designates a single character (any type) placeholder value. ! Designates a single national character placeholder value.

(i.e. @, #, $)

4 Ensure the job card is correct and press Enter. Note: This step can be skipped if you use ISPF Edit.

5 Type S next to '__SUBMIT JOB For Execution' and press Enter. Note: This step can be skipped if you use ISPF Edit.

Refresh the RSP Job Table

Submit job 'RSPJRFSH' from 'your.product.JCL'. This enables RSP to update the job table and begin collecting online SMF data for the application.

Run the Production Application Cycle / Create the Selection Data Set

Run your production application. Signal the end of the production application cycle to ASAP by: Edit 'your.product.JCL(APPLEND)'

Type the name of the application in the parm. For example; PARM='APPL(PAYROLL)'. The APPLEND job analyzes the RSP/JCL records and builds the selection data set (list of data sets) that is input to a backup. The list of data sets is written in the format specified in the SETUP options.




1.10 Step-by-Step ASAP Setup Options – For Rerun Recovery

STEP

1

STEP DESCRIPTION

Access ASAP in one of two ways: 1. From the Backup & Recovery Manager Suite Main Menu, choose Option 3,

ASAP. 2. Type 'xxx' from the command line, where xxx = your product file PARMLIB

name. Type EX next to member ABRMGR.

2 From the ASAP Main Menu, choose Option 2, SELECT/CREATE APPL, and press Enter.

3 To define a new application, specify the application name in the 'Specify NEW Application Name' field. If an application name is already specified in the 'use current/OLD Application Name' field, overwrite it. Press Enter. Pressing Enter automatically puts you into Option 0 (SETUP) for the specific ASAP application you are defining. If you are using ABARS, notice the aggregate name at the top of the screen.

4 Enter the Application Setup Options as specified in the topic 'Enter the Application Setup Options for Rerun Recovery' (page 1-28).

5 Submit job collection as described in the topic 'Submit Job Collection' (page 1-32).

If you are defining an application to use Forward Recovery, use the procedure in the topic 'Step-by-Step ASAP Setup Options – For Forward Recovery' (page 1-21).




1.10.1 Enter the Application Setup Options for Rerun Recovery

Application General Setup

SETUP OPTIONS FOR APPLICATION ==> Application name you specified in the topic above.

Appl DESC => Enter descriptive text for the application.

Associate With ABARS Aggregate If you are using ABARS, and the aggregate already exists, the aggregate name will automatically be put here if it is the same name that is in ISMF. The ABARS aggregate name should generally be created first. For non-ABARS, the ASAP application name will be put here.

DATA SETS. panel.

One note of caution: If you are using ABARS and the aggregate already exists, ASAP will automatically put in the selection data set name below under a section called SELECTION

If you do not want to write to this selection data set, just change the name on this

JOB COLLECTION OPTIONS

Collection Mode REPLACE

Collection Structure ALL

COLLECTION OPTIONS

Collect data via SMF or JCL M

RSP OPTIONS

Next RSP cycle number: 0000000001 Displays the current RSP cycle number.

Number of RSP cycles to retain 1





JCL OPTIONS

Next JCL cycle number: 0000000001 Displays the current JCL cycle number.

Number of JCL cycles to retain 1


BATCH SMF SCAN OPTIONS

Next SMF cycle number: 0000000001 Displays the current SMF Batch cycle number.

Number of SMF cycles to retain 1


CURRENT VERIFICATION OPTIONS

Apply FILTERING During VERification Y

Re-evaluate Data Set Entries Y

User Tape Data Sets as ACCOMPANY N ABARS option only. By specifying N, this option puts tape data sets in the Include list.

Category if 1st ref. DELETE E

Category if 1st ref. RENAME OLD DSN E

Category if 1st ref. RENAME NEW DSN E

Use SMF data in selection data set Y

Use JCL data in selection data set Y

SELECTION Dsn Format ABARS, DSS, XSS LIST, DMS, FDR

RSP cycles to include in Sel. DS 0001

Evaluate all data sets as critical N This parameter indicates either Forward Recovery if Y, or Rerun Recovery if N.

Detailed comments in Sel. Data Set N




VERIFICATION GDG OPTIONS

GDS names in selection data set B

Evaluate GDG entries from JCL Scan Y

Evaluate GDG entries from SMF data Y

Expand Base only references N

Add entries for missing GDSs M

CATEGORY FOR NEW GDS IF NEW GDS IS ONLY REFERENCE TO GDG (FOR FORWARD RECOVERY ONLY)

ABARS category for missing GDSs I

ABARS category for new generations E

BACKUP OPTIONS

BACKUP CYCLES TO RETAIN: Optional. Ignore if not using the Application Backup and Restore feature of All/Star. This field defines how many All/Star application cycles will be tracked by All/Star in the Backup & Recovery Manager Suite Inventory Data Set. Whereas the ASAP option (as defined by: Number of RSP cycles to Retain and Number of JCL cycles to Retain – found in Option 0 – Setup) allows nn cycles to be tracked, All/Star tracks cycles including the backup information found for each critical data set discovered by ASAP, hence allowing restoration of the data sets peculiar to a given application cycle. For more information on the Application Backup and Restore feature of All/Star, see Chapter 12, All/Star: Application Backup and Restore of the Backup & Recovery Manager Suite User Guide: All/Star.

NOTE: ASAP’s option to track more than one cycle only affects how many cycles' worth of raw input (i.e. SMF and JCL information) are saved. These records are called Data Set Detail records (DSD). If in the ASAP Application AutoBuild Options menu, Option 0 – Setup, the following cycles are set higher than one (in general 1 is used and is not the number of application backup cycles tracked by All/Star), "Number of RSP cycles to retain:" "Number of JCL cycles to retain:", the DSD records for the various cycles are combined, and analyzed, and the result is the creation of Data Set Records (DSR). These records are built for the last cycle completed, and reflect the results of Option 0 – Setup Options, filters, and are used to generate a selection data set (list of data sets). At any time, only one version of the DSR records exist.




SELECTION DATA SETS

VERIFY => If using ABARS, the ABARS selection data set will be put here. If you are not using ABARS, or no aggregate exists, a default name will be used.

RSP/BATCH => If using ABARS, the ABARS selection data set will be put here. If you are not using ABARS, or no aggregate exists, a default name will be used.

Press Enter to save changes. You will now be brought to the Main Application Menu. The application name will be displayed on the top of the panel. You were just in Option 0 (Setup).




1.10.2 Submit Job Collection

STEP

1

STEP DESCRIPTION

From the ASAP Application AutoBuild Options menu, select Option 1 for JOB COLLECT and press Enter.

2 From command == > Select the option from ISPF Edit. (or the appropriate scheduler) • If using a job name mask, see Step 3. • If using a scheduler interface, see the topic 'Interfaces to Job Scheduling Products'

(page 1-7).

3 Leave in the comments. Type each job name in column 1 (unless using the scheduler). Press Enter and End when finished. If using ISPF Edit, there are numerous masking characters: * Used in front and/or at the end of the name, as a 'wild card' character mask. < Used to represent a single alpha-only character. > Used to represent a single numeric-only character. % Designates a single character (any type) placeholder value. ! Designates a single national character placeholder value. (i.e. @, #, $)

4 Ensure the job card is correct and press Enter. Note: This step can be skipped if you use ISPF Edit.

5 Type S next to '__SUBMIT JOB For Execution' and press Enter. Note: This step can be skipped if you use ISPF Edit.

Refresh the RSP Job Table

Submit job 'RSPJRFSH' from 'your.product.JCL'. This enables RSP to update the job table and begin collecting online SMF data for the application.

Run the Production Application Cycle

Run your production application. Signal the end of the production application cycle to ASAP by: Edit 'your.product.JCL(APPLEND)'

Type the name of the application in the parm. For example; PARM='APPL(PAYROLL)'. The APPLEND job analyzes the RSP/JCL records and builds the selection data set (list of data sets) that is input to a backup. The list of data sets is written in the format specified in the SETUP options.




1.11 Monitoring Application Changes Monitoring application changes ensures that any changes made to the application are reflected in the selection data set and the ASAP Database.

After the job collection and JCL/SMF, real-time tracking is complete for an application, and the selection data set has been created, both real-time and batch mechanisms are provided by ASAP for collecting and monitoring data set changes for any application. Figure 1-4 shows the processes involved in monitoring and updating an application's selection data set.

Figure 1-4: ASAP Batch or Real-time Monitoring and Updating

(RSP)

Real-time Selection Process

APPLEND or VERIFICATION: Critical Data Set

Entries

ASAP Database

ASAP Real-time Selection Process / Batch ASAP Monitoring and Selection Data Set Update

Data Set

( )

--

/FDR


References

Continuous Monitoring of Executing Applications

in Multi-Image - SYSPLEX Modes



Image-1 Image-2

Applications


ABARS DFSMSdss/DFDSS DMS OS/CA-DISK

LIST




Real-time Selection Process (RSP) Facility

The Real-time Selection Process (RSP) facility of ASAP allows continuous application monitoring and collection of data set entries using RSP SMF Capture and RSP JCL Capture.

The RSP facility can monitor and track an application in both single and multi-image environments (or SYSPLEX). At the completion of an application's processing, its data set entries are updated and its selection data set list is reconstructed, ensuring that the subsequent backup contains the most current critical application data sets.

See Chapter 7, Real-time Selection Process (RSP).

1.12 ASAP Batch Job Submission Sequence Job collection and batch SMF functions are performed by submitting batch jobs. At an appropriate point during these data collection steps, the user specifies that ASAP is to submit the batch job. ASAP then displays a series of panels that allow the user to modify the batch job using ISPF Edit before submission.

The first panel displayed during batch job submission is a Job Statement Verification panel. The initial information on this panel is obtained from the TSO user's ISPF 0.2 option, which defines a default job statement for batch jobs. If necessary, change the fields on this panel to match your installation's requirements for batch jobs.

The Job Statement Verification panel is shown below.

REVIEW and/or CHANGE JOB/JCL Statements as Required:Use ENTER To Submit JOB; or PF3 To Abort

Randomize Job Name to Eight Characters ? ==> YES ( YES / NO )

//MSIS04TZ JOB (,101),'I. M. USER',CLASS=Z,REGION=0M,// NOTIFY=MSIS04T,MSGLEVEL=(1,0),MSGCLASS=X//* NEW BATCH JOB//*

The next panel, displayed after the job card information has been provided, is the ASAP Job Submission Preferences panel. This panel allows the user to either immediately submit a batch job, or to edit the generated JCL prior to submission. Like the preceding panel, this pop-up panel is displayed over the existing panel.

The Job Submission Preferences panel is shown below.

Command ==>

Current Application: CA7MAXJB ASAP AUTOBUILD Phase: JOB COLLECTION

SELECT All The Options You Wish.

_ EDIT JCL Prior To Job Submit _ SUBMIT JOB For Execution

Make Selections and ENTER ; Use PF3 To Terminate.




The fields on the Job Submission Preferences panel are described below.

Field Description

Current Application The name of the application for which data collection is being performed.

ASAP AUTOBUILD Phase The name of the ASAP primary data collection step (i.e., job collection, or SMF SCAN).

EDIT JCL Prior To Submit ISPF Edit displays the JCL that has been generated for the batch job. This JCL is automatically submitted after the JCL has been edited and you press Enter. Select this option by keying an S in the entry field.

SUBMIT JOB For Execution The job is submitted immediately. Select this option by keying an S in the entry field.

When the batch job has completed, the number of pending messages will be sent to the ASAP user. This message may be displayed via option 6 (STATUS) or by pressing PF12 on the Application AutoBuild Options menu.

1.13 Viewing Product Messages Product messages are distributed with the product in MESSAGES library members. The messages can be viewed directly from the MESSAGES members; via an ISPF option; or using Chicago-Soft's®

Quick-Ref™, if it is installed in your environment.

1.13.1 Message Identifier Naming Convention Product message identifiers are in the form pppmmmnnx

Where: ppp is the 3 alpha character product code –

BRM for code shared by ABARS Manager, All/Star, and ASAP ASP for ASAP

mmm is the module identifier nn is the message number x is the message type indicator – E=error, I=information, W=warning.

Example 1: The message identifier BRM02056I would be a message from module BRM020, message number of 56, and is an Information only message.

Example 2: The message identifier BRMVSE11E would be a message from module BRMVSE, message number of 11, and is an Error type message.

1.13.2 Determine Which MESSAGES Member Contains the Message Description Messages are in the MESSAGES library in a member name that matches the first six characters of the message identifier (ID).

Example 1: With the first six characters of message identifier BRM02056I being BRM020, the description would be found in MESSAGES member BRM020.

Example 2: With the first six characters of message identifier BRMVSE11E being BRMVSE, the description would be found in MESSAGES member BRMVSE.




1.13.3 View Messages Using ISPF Interface Product messages can be viewed using the ISPF interface. In the ISPF interface, the Action Bar (at the top of the screen) has an option labeled “Menu”. Choose “Menu” to display a Pull-Down menu; option 1 is messages. Choosing option 1 will start a Browse session of product messages.

You can also view the product messages by choosing Option 8 on the ASAP Main Menu.

1.13.4 View Messages in MESSAGES Library Be sure you always refer to the most current MESSAGES members, as the members may be updated and distributed with a release of the product, cumulative maintenance, and sometimes for PTFs as well.

Use Browse FIND Command to Locate Messages Within a MESSAGES Member:

Within a message member, use the Browse FIND command to locate a specific message identifier (ID) explanation. Message IDs begin in column one. Include the column information in your FIND command to go directly to the main descriptions for the specified message.

F msgid 1

Where: msgid is the specific product message ID.

To Obtain a Hardcopy of Messages in the MESSAGES Members:

Print the MESSAGES members (but remember to print new ones after product releases, cumulative maintenance, or PTFs have been applied).

1.13.5 View Messages Using Quick-Ref You can access messages via Chicago-Soft's Quick-Ref if it is installed in your environmenr. Request the latest updates from Chicago-Soft if neded.




Chapter 2 2 Overview of the ASAP Main Menu

This chapter contains an overview of the menu options available on the ASAP Main Menu. A brief description is provided for each option in an Option/Description table; with more detailed explanations, either in separate sections of this chapter, or in other chapters of this user guide. More information about each option is provided in the chapter references included in the Option/Description table.

Contents:

• Backup & Recovery Manager Suite Main Menu – page 2-2

• ASAP Main Menu Options – page 2-2

• LIST APPLICATIONS – Option 1 – page 2-4

• SELECT/CREATE APPLICATIONS – Option 2 – page 2-5

• RSP MONITOR – Option 3 – page 2-9

• SMF SCAN SETUP – Option 5 – page 2-9

• N/A – Option 6 – page 2-9

• N/A – Option 7 – page 2-9

• ERROR MESSAGES – Option 8 – page 2-9

• FILTERS/CONTROLS – Option 9 – Option 9 – page 2-10

Mainstar Software Corporation ©2006 2-1 Chapter 2 SC23-6059-00 Overview of the ASAP Main Menu



2.1 Backup & Recovery Manager Suite Main Menu To access the ASAP Main Menu, select Option 3, ASAP, from the Backup & Recovery Manager Suite Main Menu, shown below.

Figure 2-1: Backup & Recovery Manager Suite Main Menu

Menu Diagnostics Preferences Utilities Admin -----------------------------------------------------------------------------Vvv.rr Backup & Recovery Manager Suite - Main MenuCommand ==>

Enter an option from the list below:

1 Setup and Configuration2 Backup and Recovery Management3 ASAP 4 Features

Miscellaneous Functions 5 Search for Dataset 6 Reports7 Monitor 8 History

X Exit

Copyright (C) 2006 Mainstar Software CorporationAll Rights Reserved

2.2 ASAP Main Menu Options The options available in the ASAP Main Menu are shown below.

Figure 2-2: ASAP Main Menu

<Vvv.rr> --- A S A P Main Menu ---

OPTION ==>

W E L C O M E To:

ASAP(c): Main Menu Services

1 - LIST APPLICATIONS : Display Current ASAP/Application List2 - SELECT/CREATE APPL : Application Management: Create New or Select

Existing Applications3 - RSP MONITOR : Monitor RSP Processing of SMF Records4 - N/A : 5 - SMF SCAN SETUP : Set Up and Submit SMF Scan Job6 - N/A : 7 - N/A : 8 - ERROR MESSAGES : ASAP Error Messages9 - FILTERS/CONTROLS : Display/Edit Global Configuration DataX - EXIT : Exit ASAP

Your Last Active Application: EMTEST9

Copyright (C) 1997-2006 by Mainstar Software Corporation; All Rights Reserved

Chapter 2 2-2 Mainstar Software Corporation ©2006 Overview of the ASAP Main Menu SC23-6059-00



Before beginning the steps of collecting and analyzing job and SMF data:

• Global installation defaults must be initialized by providing keyword values in the BRMINI PARMLIB member.

• Application defaults must be specified by selecting SELECT/CREATE APPL (Option 2) from the ASAP Main Menu, then SETUP (Option 0) from the ASAP AutoBuild Options menu. The Application SETUP panel will be displayed to allow the setting of default values for the current TSO Userid.

The options available on the ASAP Main Menu are shown below.

Main Menu Option Description

LIST APPLICATIONS Option 1

This option will display a table of all the applications that are currently defined to ASAP, and information about those applications, such as their names, descriptions, and current status. You may select a particular application from the displayed list for further processing. If no applications have been defined to ASAP yet, an empty table is displayed. You must use the next option, CREATE/SEL APPLICATION, to define an application to ASAP. See the topic ‘LIST APPLICATIONS – Option 1’ (page 2-4) for an overview of this option. Additional detail is provided in Chapter 8, Obtaining Application Information.

SELECT/CREATE APPL Option 2

When this option is selected, a panel is displayed where a new or existing application name may be entered. You also have the option of selecting an existing application from a list. The Application AutoBuild Options menu will be displayed, containing the options you will use to define the application to ASAP, and to create and maintain the application's backup selection data set. If you enter an application name that is new to ASAP, the Application SETUP Options panel will be displayed where you can setup/configure the application. If no application is specified, information for the most recently used application is displayed. See the topic ‘SELECT/CREATE APPLICATION – Option 2’ (page 2-5) for an overview of the options available on the Application AutoBuild Options menu, including references to the chapters containing detailed descriptions of each option.

RSP MONITOR Option 3

This option provides information about RSP processing and lets the user perform some of the RSP operator commands. See the topic ‘RSP MONITOR – Option 3’ (page 2-9) for an overview of this option. Additional detail is provided in Chapter 7, Real-time Selection Process (RSP).

N/A Option 4

SMF SCAN SETUP Option 5

This option allows you to set up and submit batch SMF Scan jobs. See the topic ‘SMF SCAN SETUP – Option 5’ (page 2-9) for an overview of this option. Additional detail is provided in Chapter 5, SMF SCAN SETUP – Identifying Application Data Sets through Batch SMF.




Main Menu Option Description

N/A Option 6

N/A Option 7

ERROR MESSAGES Option 8

This option allows you to view ASAP error messages directly from the screen. See the topic ‘ERROR MESSAGES – Option 8’ (page 2-9) for an overview of this option.

FILTERS/CONTROLS Option 9

This option allows filters to be created and enabled/disabled globally for all applications. The filters control which data sets will be saved in the application's ASAP Database and eventually selected for the selection data set. See the topic ‘FILTERS/CONTROLS – Option 9’ (page 2-10) for an overview of this option. Additional detail is provided in Chapter 9, FILTERS – Using Filters and Controls.

2.3 LIST APPLICATIONS – Option 1 To display a set of panels that contain categories of information, such as job collection, Batch SMF Scan, Verification, etc., for all current applications in the ASAP Database, select Option 1 (LIST APPLICATIONS) from the ASAP Main Menu. The set of panels provide Commands and line commands that allow you to use the data interactively and to customize use of the information for your userid.

Categories of information that can be displayed by either scrolling or selecting:

• General Information • Recent Events • Last Job Collection Information • User's Current Preferences for using List Application

For more information about LIST APPLICATIONS and examples of the category panels, see Chapter 8, Obtaining Application Information.

Note: Some ASAP panels require PFSHOW be turned off. If you cannot see part of a panel because the PF Keys are displayed, go to the ISPF command line and type PFSHOW. PFSHOW is a toggle switch that turns off the display of PF Keys.




2.4 SELECT/CREATE APPLICATION – Option 2

2.4.1 Supply an Application Name to ASAP To identify and configure an application to ASAP, select Option 2 (SELECT/CREATE APPL) from the ASAP Main Menu.

Enter an application name in either the Old or New fields.

• If the application name you enter is new to ASAP, the Application SETUP Options panel will be displayed. The use of the Application SETUP Options panel is described in Chapter 3, SETUP – Defining an Application to ASAP.

• If the application you specify is old (has already been identified to ASAP), information about that application's status will be displayed, and you may perform actions for the application, such as job collection and Batch SMF Scan.

• If no application is specified, status for the most recently used application will be displayed.

To select from a list of existing application names, enter Y next to Select From Application List. A pop-up list of current names will be displayed, as shown below.

+----- APPL LIST ------+ ¦ ROW 1 TO 8 OF 8 ¦¦ Cmd ==> ¦¦ Use 'S' To Select ¦¦ ¦¦ -Opr- ---NAME--- ¦¦ ¦¦ _ HRPDAILY ¦¦ _ MONAPPLN ¦¦ _ NEW11 ¦¦ _ NEW44 ¦¦ _ PRODAILY ¦¦ **END** ¦+----------------------+



--- --


2.4.2 Application AutoBuild Options Menu After an existing (old) application name has been entered or selected from the pop-up list, the ASAP Application AutoBuild Options menu will be displayed.

Figure 2-3: Application AutoBuild Options Menu

<Vvv.rr> A S A P Application AutoBuild Options -

Option ==>

SPECIFY Application Name ==> PAYROLL

Event -- PRIMARY COLLECTION SEQUENCE (PCS) ---- --- STATUS ---

0 -1 -2 -

SETUP JOB COLLECT FILTERS

: Setup Application Options.: Collect Application JOB Structure.: Application Filters.

2000353/1116

-- APPLICATION POST-PROCESSING OPTIONS ----

4 - VERIFICATION : Determine Final SEL Data Set Entries. 2001027/09345 - N/A6 - STATUS : Display Current Application's Status.

( PAYROLL APPLICATION CREATED ON 01/10/2004 )

Application AutoBuild Options Menu – Fields

SPECIFY Application Name

The Application AutoBuild Options menu is the primary place from which ASAP functions are performed on an application. The application name in this field is the new application that is to be defined, or the name of an existing application that will be affected by any ASAP operations executed during the session, until you alter the application name here or on the previous panel.

If you enter an application name that does not exist, ASAP will display the Application SETUP Options panel. SETUP is described in Chapter 3, SETUP – Defining an Application to ASAP.

Application Event STATUS

The current status of each ASAP function is shown in the 'Event STATUS' field.

For example, if job collection has been performed for an application, but SMF analysis has not yet been submitted, then the values of the STATUS field will be the date/time of when the event completed (JOB COLLECT), and blank for SCAN SMF RECS.

If SCAN SMF RECS has been submitted, but has not yet finished, the STATUS field will be empty if this is the first time the ASAP batch job to perform SMF analysis has been run, or will show the date/time from the last successful execution.




Application AutoBuild Options Menu – Option Overviews

An overview of each option available on the Application AutoBuild Options menu is provided below. Detailed information about the use of each option is provided in the referenced chapters.

Option

SETUP Option 0

Option 0

/

to ASAP.

The

AutoBuild Options menu.

Option 1 Option 1

FILTERS Option 2

Option 2

the ASAP Database.

Description

displays the Application SETUP Options panel. From this panel, the application is defined to ASAP and global setup options are displayed specified for the application. SETUP is described in Chapter 3, SETUP – Defining an Application

Note: Application SETUP Options panel is also displayed when the name of a new, not yet defined application is entered in the 'SPECIFY Application Name' field of the Application

JOB COLLECT displays the panels that allow ASAP to collect information about which jobs make up the application. This step is essential and must be performed before SMF collection (either RSP SMF/JCL Capture or Batch SMF Scan) is begun. If you use the scheduler interface, ASAP will submit a batch job to obtain information about which jobs are associated with the application, and which additional jobs are triggered by those jobs. JOB COLLECT is described in Chapter 4, JOB COLLECT – Collecting Application Job Structure.

displays the Application FILTER panel that can be used to control application local and global filters. The default is to include all eligible data sets from jobs tracked for an application into

For more information about filtering, see Chapter 9, FILTERS – Using Filters and Controls.




Option Description

VERIFICATOption 4

ION Option 4 displays a series of panels that cause ASAP to generate a selection data set. ASAP uses the information about the application that has been recorded in the ASAP Database to determine which data sets are required for inclusion in the backup. For each data set associated with the application, ASAP automatically determines what the data set's status in the selection data set should be based on the setup options to support either Forward or Rerun recovery. If you are using ABARS, each data set is classified as an INCLUDE, EXCLUDE, ALLOCATE, or ACCOMPANY data set. Panels are displayed with ASAP recommendations for each data set, and the user can override these recommendations if desired. Verification is used: After a Batch SMF collection to extract the records from the database, process the filters, and build the selection data set. Re-evaluate data. For example, let's say you run an APPLEND. Now you want to create some filters or change some settings but you want to know the effects of your changes. Simply make your changes and run Verification to see the results. Verification uses the last cycle of data to rebuild your selection data set. VERIFICATION is described in Chapter 6, VERIFICATION – Creating the Selection Data Set.

N/A Option 5

STATUS Option 6

Option 6 allows you to make inquiries about the status of the current application as it is recorded in the ASAP Database. A pop-up panel allows you to select information about the status of the data collection process for the application, (e.g., the jobs or data sets associated with the application), or to display pending messages from batch jobs submitted by ASAP. The application STATUS option is described in Chapter 8, Obtaining Application Information.




2.5 RSP MONITOR – Option 3 When Option 3 is selected from the ASAP Main Menu, the RSP Monitor menu appears. The options available on the RSP Monitor menu are shown below. For more information about RSP Monitor, see Chapter 7, Real-time Selection Process (RSP).

RSP MONITOR CMD:

1 2 3 4 5

Display RSP StatusDisplay RSP StatisticsDisplay Current Job TableDisplay Current Filter TableRSP Commands

H Help

2.6 N/A – Option 4

2.7 SMF SCAN SETUP – Option 5 When Option 5 is selected from the ASAP Main Menu, a series of panels is displayed that allow ASAP to submit a Batch SMF Scan job to analyze SMF data. SMF analysis allows ASAP to obtain additional data about the applications included in the SMF Scan job. For more information, see Chapter 5, SMF SCAN SETUP – Identifying Application Data Sets through Batch SMF.



2.10 ERROR MESSAGES – Option 8 When Option 8 is selected from the ASAP Main Menu, the Error Message ID pop-up panel appears. Enter the error message ID and press Enter.

An example of the Error Message ID pop-up panel is shown below. .---------------------- ERROR MESSAGE ID------------------------------. | COMMAND ==> || || ENTER ERROR MESSAGE ID (8 OR 9 CHARACTERS): || || || ENTER TO CONTINUE; PF3(END) TO TERMINATE |. --------------------------------------------------------------------.




2.11 FILTERS/CONTROLS – Option 9 When Option 9 is selected from the ASAP Main Menu, the Global Filtering/Controls Selection panel appears. The Filters and Controls option allows you to create or display Global and Universal selection filters. Standard ISPF Edit or Browse is used to perform the chosen function.

An example of the Global Filtering/Controls Selection panel is shown below.

.----------------- Global Filtering/Controls Selection -----------------.| || || Supply Input; Use ENTER To Change Entries. || Use PF1 For HELP ; Use PF3 To Return. || || || || Global DSN Retention Filters => (E)dit/(B)rowse || Global VOLUME Retention Filters => (E)dit/(B)rowse || Global UNIT Retention Filters => (E)dit/(B)rowse || Global SYSID Retention Filters => (E)dit/(B)rowse || Global JOB Retention Filters => (E)dit/(B)rowse || || Global DSN Evaluation Filters => (E)dit/(B)rowse || Global VOLUME Evaluation Filters => (E)dit/(B)rowse || Global UNIT Evaluation Filters => (E)dit/(B)rowse || Global SYSID Evaluation Filters => (E)dit/(B)rowse || Global JOB Evaluation Filters => (E)dit/(B)rowse || || Universal Retention Filters => (E)dit/(B)rowse || Universal Evaluation Filters => (E)dit/(B)rowse || || Command ==> |'-----------------------------------------------------------------------'

Filters are created using keywords, and values that may be explicit or use Mainstar extended ACS pattern masking. For detailed information about Filters and Controls and pattern masking, see Chapter 9, FILTERS – Using Filters and Controls.




Chapter 3 3 SETUP – Defining an Application to ASAP

This chapter explains how to define an application to ASAP using the Application SETUP Options panel.

Note: Option values set for an application will not be effective if the option is disabled globally in the BRMINI member of PARMLIB.

Contents:

• Set Up an Application – Application AutoBuild Options Menu Option 0 – page 3-2

• Application General Setup Section – page 3-6

• Job Collection Options Section – page 3-8

• Collection Options Section – page 3-10

• RSP Options Section – page 3-11

• JCL Options Section – page 3-12

• Batch SMF Scan Options Section – page 3-13

• Current Verification Options Section – page 3-14

• Verification GDG Options Section – page 3-21

• Selection Data Sets Section – page 3-29

Mainstar Software Corporation ©2006 3-1 Chapter 3 SC23-6059-00 SETUP – Defining an Application to ASAP


--- --


3.1 Set Up an Application – Application AutoBuild Options Menu Option 0 Applications are set up using the Application SETUP Options panel. To display the Application SETUP Options panel:

• From the ASAP Main Menu – select Option 2 (SELECT/CREATE APPL), and specify a new Application Name. See the topic 'SELECT/CREATE APPLICATION – Option 2' (page 2-5).

• If it is the first time the application is created, it will automatically put you in Option 0 (Setup). • From the Application AutoBuild Options panel:

– Enter a new Application Name – Or, select Option 0 (SETUP).

<Vvv.rr> A S A P Application AutoBuild Options -

Option ==>

SPECIFY Application Name ==> APPL0001


0 -1 -2 -

SETUP JOB COLLECT FILTERS

: Setup Application Options.: Collect Application JOB Structure.: Application Filters.

2000306/1404


4 - VERIFICATION : Determine Final SEL Data Set Entries. 2001157/19155 - N/A6 - STATUS : Display Current Application's Status.

( APPLICATION CREATED BY: XYZ ON 01/10/2004 )

All of the input fields on the Application SETUP Options panel are optional. The panel is divided into several setup/configuration sections, as shown in the display on the next page. Each section is described in separate topics in this chapter.

How to Use the Application SETUP Options Panel

• To view the different sections of the panel, Scroll Up/Scroll Down. • To update the fields that have been changed, use the Enter key. • The End command creates an application record in the ASAP Database and makes the

application known to ASAP.

If the CANCEL, EXIT, or RETURN commands are issued, the data is not saved, or in the event of a new application, the application is not created.

Chapter 3 3-2 Mainstar Software Corporation ©2006 SETUP – Defining an Application to ASAP SC23-6059-00



The Application SETUP Options panel is displayed below. Do not randomly use the settings displayed here without determining if you require Rerun or Forward Recovery and understand all the options.

Figure 3-1: Application SETUP Options panel

SETUP OPTIONS FOR APPLICATION ==> APPL0001 Command ==> SCROLL==> CSR

Use PF3/Save to Save and End, or Cancel to return without SavingMore: +

--- APPLICATION General Setup ---Appl DESC => APPLICATION CREATED BY: XYZ ON 01/10/2004 <=

Associate With ABARS Aggregate: APPL0001 <= ( ABARS Usage )

--- JOB COLLECTION Options ---Collection Mode: REPLACE <= ( REPlace,MERge )

Collection Structure: ALL <= ( ALL, ANChor )

--- Collection Options ---Collect data via SMF or JCL: M <= ( M = Minimum)

( A = Future Release)( N = No)

--- RSP Options ---Next RSP cycle number: 0000000006

Number of RSP cycles to retain: 0001Automatically delete old cycles: Y <= ( Y/N )

--- JCL Options ---Next JCL cycle number: 0000000006

Number of JCL cycles to retain: 0001Automatically delete old cycles: Y <= ( Y/N )

--- Batch SMF Scan Options ---Next SMF cycle number: 0000000001

Number of SMF cycles to retain: 0001Automatically delete old cycles: Y <= ( Y/N )

Application SETUP Options panel - continued on next page




Application SETUP Options panel - continued from previous page

--- Current VERIFICATION Options ---Apply FILTERING During VERIFICATION: Y <= ( Y/N )

Re-evaluate Data Set Entries: Y <= ( Y/N )User Tape Data Sets as ACCOMPANY: N <= ( Y/N )

Category if 1st ref. DELETE: E <= ( Include/Exclude )Category if 1st ref. RENAME OLD DSN: E <= ( Include/Exclude )Category if 1st ref. RENAME NEW DSN: E <= ( Include/Exclude )Use SMF data in selection data set: Y <= ( Yes/No )Use JCL data in selection data set: Y <= ( Yes/No )

SELECTION Dsn Format: ABARS <= ( ABARS, DSS, XSS )( LIST, DMS, FDR )

RSP cycles to include in Sel. DS: 0001Evaluate all data sets as critical: N <= ( Y/N )Detailed comments in Sel. Data Set: Y <= ( Y/N )

----- VERIFICATION GDG Options -----GDS names in Selection Data Set: B <= ( R = Relative

A = Absolute B = Both )

Evaluate GDG entries from JCL data: Y <= ( Y/N )Evaluate GDG entries from SMF data: Y <= ( Y/N )

Expand Base only references: N <= ( Y/N )Add entries for missing GDSes: M <= ( N = No

M = Min for rerun F = Forward recovery

For forward recovery ONLY A = All cataloged )

Category for new GDS if new GDSis only reference to GDG: I <= ( I = Include

E = Exclude )

ABARS category for missing GDSes: I <= ( I = IncludeA = Allocate )

ABARS category for new generations: I <= ( E = ExcludeI = Include A = Allocate )

--- BACKUP OPTIONS ---BACKUP CYCLES TO RETAIN: 001

--- SELECTION DATASETS ---VERIFY => BK.TEST.BK000001.SELECT RSP/BATCH => BK.TEST2.BK000001.SELECT




3.1.1 The APPLICATION Field For a new application, SETUP must be invoked at least once. ASAP primes the selection data set name field.

• If using ABARS, ASAP checks to see if an aggregate has been associated with the application, and if so, establishes the selection data set name from the ISMF data supplied when the aggregate was defined,

or

• Generates a name to be used if no ISMF aggregate name can be identified to be used with non-ABARS formats, or you can define your own in advance as an 80-byte sequential file.

Note: You must press Enter and then End the SETUP panel for the selection data set name to be established.




3.2 Application General Setup Section The figure below shows the APPLICATION General Setup section of the Application SETUP Options panel.

More: + --- APPLICATION General Setup ---

Appl DESC => APPLICATION CREATED BY: XYZ ON 11/15/01 <= Associate With ABARS Aggregate: APPL0001 <= ( ABARS Usage )

3.2.1 Application General Setup Field Descriptions The following fields are shown in the APPLICATION General Setup section.

Field Description

Appl DESC A free-format text field that may be used to describe the application. The content can be overtyped if desired. This field is optional.

Associate with ABARS Aggregate

If using ABARS, the name of an ABARS aggregate that the ASAP application is to be associated with. If specified, the selection data set specified in the ABARS aggregate group definition is used when ASAP generates the aggregate selection control statements (INCLUDE, EXCLUDE, ACCOMPANY, and ALLOCATE). If the ASAP application is not associated with an ABARS aggregate, ASAP generates a name to use as the selection data set. This name can be changed at any time. By using the ? character in the first position of the field entry, you can display a pop-up list of your current ABARS aggregates (within your current SMS configuration). This allows you to quickly determine which aggregates can be associated with your current ASAP application name. If you are not using ABARS, leave this field blank.




Display Your Current SMS Aggregate Entries

Figure 3-2 shows how to use the ? character to display a pop-up list of your current ABARS aggregates (within your current SMS configuration). This allows you to quickly determine which aggregates are associated with your current ASAP application name.

Figure 3-2: How to Display Your Current SMS Aggregate Entries

Global Application Setup Options

Command ==> APPLICATION ==> AC

Change Fields as Necessary; Use ENTER To Activate; Use PF3 To ReturnMore: +

--- APPLICATION General Setup --Appl DESC => AIR CARGO CREATED BY XYZ 11/15/01 <= Associate With ABARS Aggregate: => ?ACXXALL <= ( ABARS Usage

Use '?' in the first position to display a current aggregate list of names.

Use 'S' in the Line Opr field to select and associate this aggregate to the application.

AGG LIST CMD ==> Use 'S' To

X' To Expand

-Opr- ---NAME---

_ ANSWRDB _ APPC _ ASCH _ ASCHINT x AUTOMATE _ BBMCAS _ BOBTEST _ CATALOG _ CA11 _ CA7 _ CICMPRD1 _ CICMPRD2 _ CICMTRM _ CICSMGR

Aggregate Expansion For: AUTOMATE--- GENERAL Information --

Last Update User: M70659TUpdate Date: 2001/10/11 Update Time: 14:15Desc: DR BACKUP FOR AUTOMATE (DFP) DEST Name:

--- OPTIONS / Control Information ---(SMS) MgmtClass: ZABARV2 Tol ENQFail: NRETPD Used: N EXPDT/RETPD Value: 0000COPIES Valid: Y No COPIES: 0001 Backup DSN Prefix: PSSXZ.ABAR.AUTOMATE

--- DATA SET Information ---INSTR Dsn: SELECT Dsn(s):

SSXSP.MVSSYS.ABAR.SELECT.AUTOMATE

Selection Data Set Name: This will be the default selection data set name for the Application during Verification, if the ABARS format is used.

In the above sequence, using S will select the aggregate for the ASAP application association.




3.3 Job Collection Options Section The Job Collection Options section of the Application SETUP Options panel is shown below.

--- JOB COLLECTION Options ---Collection Mode: REPLACE <= ( REPlace,MERge )

Collection Structure: ALL <= ( ALL, ANChor )

3.3.1 Job Collection Options Field Descriptions The following fields are shown in the Job Collection Options section.

Field Description

Collection Mode This field specifies whether ASAP Database records that are created during the job collection phase are to replace existing database records (REPLACE) or the new information is to be added to the existing records (MERGE). If REPLACE is specified, the old job information is removed from the ASAP Database and replaced. If MERGE is specified, new jobs found by the most recent job scan are added to the existing records in the ASAP Database. The default is REPLACE.

Collection Structure This field indicates whether ASAP should save any lower level succeeding job entries and structures during the collection event. Either ALL or ANCHOR can be used. ANCHOR – Indicates that only the specified starting point structure(s) be collected and retained. ALL – Indicates that all lower level job elements and structures be automatically saved during the collection event. The default is ALL. See the example structure sequence shown in Figure 3-3.



- - -


Example Job Structure Sequence

In Figure 3-3:

• If 'ALL' is specified for the Collection Structure field and 'JOB1' is the primary collection starting point, then all of the lower level entries and structures for JOB21, JOB31 and JOB41 will be automatically saved in the application. If 'JOB21' is used as the starting point, then only JOB21 and JOB31 entries will be saved.

• If 'ANCHOR' is specified for the Collection Structure field and 'JOB1' is the primary collection point, then only JOB1 -to- JOB4 entries would be saved. Entries for other succeeding structures (JOB21, 31 and 41) would not be saved, unless they are explicitly specified.

Figure 3-3: Job Collection Structure

JOB1 Anchor Job

Anchor JobJOB21

JOB22

JOB30 JOB31

JOB32

JOB33

JOB4

JOB2

JOB3

JOB41 Anchor Job

JOB42

JOB43




3.4 Collection Options Section The Collection Options section is where you specify whether you want to collect file usage data from SMF or JCL.

--- Collection Options ---Collect data via SMF or JCL: M <= ( M = Minimum)

( A = Future Release)( N = No)

3.4.1 Collection Options Field Description The following field is shown in the Collection Options section. This field controls data collection.

Field Description

M = Minimum. Only the first reference to each data set and the first URD (Update/Rename/Delete) will be recorded.

Collect data via SMF or JCL

A = All. Reserved for future use. N = No. RSP will not record SMF records for this application and JCL information will not be recorded. This can be used when you want to set up ASAP applications but not collect data yet. When RSPJRFSH is executed, it will not update the JOBFLAT for the application. The default is M.




3.5 RSP Options Section These fields are control options used by RSP (Real-time Selection Process).

--- RSP Options ---Next RSP cycle number: 0000000001

Number of RSP cycles to retain: 0001Automatically delete old cycles: Y <= ( Y/N )

3.5.1 RSP Options Field Descriptions The following fields are shown in the RSP Options section. For more information about RSP, see Chapter 7, Real-time Selection Process (RSP).

Field Description

Next RSP cycle number Display only field. Indicates the next cycle number to be used for RSP recording. The cycle number is incremented by APPLEND unless suppressed by the CYCLENOINC parameter. Cycle numbers increment forever.

Number of RSP cycles to retain Specify the number of cycles' worth of RSP SMF data to retain in the ASAP Database. Even though more than 1 cycle may be in the database, the cycles to be included in the selection data set is controlled by the 'RSP cycles to include in Sel. DS.' (See the topic 'Current Verification Options Section', page 3-14.) If you set the number of cycles to be included in the selection data set to more than 1 (see the topic 'Current Verification Options Section', page 3-14), retain cycles must be set to at least the same number. The ASAP Database size may need to be reviewed if you wish to retain an unusually large number of cycles. The default is 1.

Automatically delete old cycles Y – means cycles' worth of data beyond the number of cycles to retain will be deleted when APPLEND increments the cycle number – unless the CYCLENOINC parameter is specified for APPLEND. N – means do not delete cycles' worth of data beyond the retain cycles value. If N is specified, it may be changed to Y at a later time and excessive cycles will be deleted at the next execution of APPLEND. The default is Y.




3.6 JCL Options Section These fields control options if RSP JCL Capture is used to collect data set information for an application via the IEFUJI exit. For more information about RSP JCL Capture, see Chapter 7, Real-time Selection Process (RSP).

--- JCL Options ---Next JCL cycle number: 0000000050

Number of JCL cycles to retain: 0001Automatically delete old cycles: Y <= ( Y/N )

3.6.1 JCL Options Field Descriptions The following fields are shown in the JCL Options section.

Field Description

Next JCL cycle number Display only field. Same as RSP cycle.

Number of JCL cycles to retain Specify the number of cycles' worth of JCL data to retain in the ASAP Database. Even though more than 1 cycle may be in the database, the cycles to be included in the selection data set is controlled by the 'RSP cycles to include in Sel. DS.' (See the topic 'Current Verification Options Section', page 3-14.) The ASAP Database size may need to be reviewed if you wish to retain an unusually large number of cycles. The default is 1.

Automatically delete old cycles Y – means cycles' worth of data beyond the number of cycles to retain will be deleted when APPLEND increments the cycle number. N – means do not delete cycles' worth of data beyond the retain cycles value. If N is specified, it may be changed to Y at a later time and excessive cycles will be deleted at the next execution of APPLEND. The default is Y.




3.7 Batch SMF Scan Options Section These fields control options if Batch SMF Scan is used to collect data set information. For more information about Batch SMF Scan, see Chapter 5, SMF SCAN SETUP – Identifying Application Data Sets through Batch SMF.

--- Batch SMF Scan Options ---Next SMF cycle number: 0000000002

Number of SMF cycles to retain: 0001Automatically delete old cycles: Y <= ( Y/N )

3.7.1 Batch SMF Scan Options Field Descriptions The following fields are shown in the Batch SMF Scan Options section.

Field Description

Next SMF cycle number Display only field. Indicates the next cycle number to be used by Batch SMF Scan. The cycle number is incremented each time Batch SMF Scan is run. If the last cycle of Batch SMF Scan data is deleted, the cycle number is decremented by 1. Cycle numbers increment forever.

Number of SMF cycles to retain Specify the number of cycles' worth of Batch SMF data to retain in the ASAP Database. The ASAP Database size may need to be reviewed if you wish to retain an unusually large number of cycles. The default is 1.

Automatically delete old cycles Y – means cycles' worth of data beyond the number of cycles to retain will be deleted when Batch SMF Scan increments the cycle number. N – means do not delete cycles' worth of data beyond the retain cycles value. If N is specified, it may be changed to Y at a later time and excessive cycles will be deleted at the next execution of Batch SMF Scan. The default is Y.




3.8 Current Verification Options Section These options control the display of data during the generation of the list of data sets in the Verification phase. For more information about Verification, see Chapter 6, VERIFICATION – Creating the Selection Data Set.

--- Current VERIFICATION Options ---Apply FILTERING During VERIFICATION: Y

Re-evaluate Data Set Entries: Y User Tape Data Sets as ACCOMPANY: N

Category if 1st ref. DELETE: ECategory if 1st ref. RENAME OLD DSN: ECategory if 1st ref. RENAME NEW DSN: EUse SMF data in selection data set: Y Use JCL data in selection data set: Y

SELECTION Dsn Format: ABARS

RSP cycles to include in Sel. DS: 0001Evaluate all data sets as critical: N Detailed comments in Sel. Data Set: N

<= ( Y/N )<= ( Y/N )<= ( Y/N )<= ( Include/Exclude )<= ( Include/Exclude )<= ( Include/Exclude )<= ( Yes/No )<= ( Yes/No )<= ( ABARS, DSS, XSS )

( LIST, DMS, FDR )

<= ( Y/N )<= ( Y/N )




3.8.1 Current Verification Options Field Descriptions The following fields are shown in the Current VERIFICATION Options section.

Field Description

Apply FILTERING During Verification

Indicates whether the filter criteria specified in Option 2 (FILTERS) of the ASAP Application AutoBuild Options panel is to be applied during ASAP Verification. During Verification, ASAP generates the selection statements in ABARS, DSS, LIST, DMS, or FDR format and places them in the selection data set. Before generating the backup control statements, the user may override (verify) the choices made by ASAP. If this field is set to Y, the filter criteria is applied before the selection data set is displayed to the user. Data filtered out during Verification remains in the ASAP Database and may later be included in the selection data set if the filter criteria is changed and the Verification process performed again. The default is Y.

Re-evaluate Data Set Entries Indicates whether ASAP should re-evaluate each data set entry within the application for classification as INCLUDE, ALLOCATE, ACCOMPANY, or EXCLUDE in the selection data set. Y – the data set entry will be re-evaluated to determine its status regardless of previous status. The only exceptions are external data sets added by filters and data sets that have had their status determined by filters. N – the data set entry will not be re-evaluated. The default is Y. CAUTION: If N is specified, the first presence of an entry for a data set will determine the status regardless of subsequent usage gathered from JCL or SMF data. It is unusual to specify N for this option.

User Tape Data Sets as ACCOMPANY

ABARS option only. Specifies whether data sets which reside on tape at the time of ASAP analysis are to be placed in the ACCOMPANY list or the INCLUDE list when generating aggregate selection control statements. Y – indicates that tape data sets are to be placed on the ACCOMPANY list in the selection data set. N – indicates that tape data sets are to be placed in the INCLUDE list in the selection data set. During ABACKUP processing, tape data sets in the INCLUDE list are mounted and the data is copied to the ABARS output tape(s). It is often beneficial to specify 'Y', at least the first time a selection data set is created, so that all tape files are in a concise list for ease of review. The default is N.




Field Description

Category if 1st ref. DELETE Allows, by application, the option to INCLUDE a data set if the 1st

reference is DELETE. ASAP looks at the 1st reference of each data set and determines criticality based on the data set's disposition, data set access, setup options, and filters in the database. Data sets with a disposition of DELETE can be Included (I) or Excluded (E) from the selection data set using this option. Most deleted data sets do not need to be included because they are no longer cataloged at the end of the application, however, it is not uncommon for applications to DELETE a data set and in the same step or a subsequent step CREATE the data set again as NEW. You may want to use Include if deleted data sets resurface during the application, such as may result after a reorganization or rebuilding of the data set. Whether the data set after reinstatement has the same contents as at the beginning of the application is not known to ASAP. Deleted data sets will be in the URD (Updated, Renamed, or Deleted) display regardless of the setting. If the data set is uncataloged when the selection data set is built, the data set is excluded regardless of how this option is set.

Note: JES2 – if the data set isn't there, it doesn't fail the job. IDCAMS – gets an RC 8. IEFBR14 – gets an RC 8. JES3 – requires a data set in the JCL to be allocated or the job will fail. IDCAMS – gets an RC 8. That is an issue if RC checking is done. IEFBR14 – fails the job.

I – Include the data set. E – Exclude the data set. Switch IGNORED if 'Evaluate all data sets as critical' is set to Y. The default is E. The associated BRMINI token is 'SDS_DELETED_DATASETS'.

Note: If the first reference of the data set is DISP=(MOD,DELETE) and the file exists, the data set is opened for INPUT. Therefore, the first reference is INPUT, not DELETE and the data set will be put on the INCLUDE list. A data set with DISP=(OLD,DELETE) where the file does not get opened is in fact a DELETE.




Field Description

Allows, by application, the option to INCLUDE a data set if the 1stCategory if 1st ref. RENAME OLD reference is RENAME for the existing (OLD) data set. DSN ASAP looks at the 1st reference of each data set and determines criticality based on the data set's disposition, data set access, setup options, and filters in the database. Most renamed data sets do not need to be included, unless you are using the RERUN options, because they are no longer cataloged at the end of the application. However, it is not uncommon for applications to RENAME a data set, and in the same step or a subsequent step, CREATE the data set again as NEW. You may want to use Include if renamed data sets resurface during the application, such as may result after a reorganization or rebuilding of the data set. Whether the data set after reinstatement has the same contents as at the beginning of the application is not known to ASAP. Data sets with a disposition of OLD that are RENAMED to a new name can be Included (I) or Excluded (E) from the selection data set using this option. Renamed data sets will be in the URD (Updated, Renamed, or Deleted) display regardless of the setting. If the data set is uncataloged when the selection data set is built, the data set is excluded regardless of how this option is set. I – Include the data set. E – Exclude the data set. Switch IGNORED if 'Evaluate all data sets as critical' is set to Y. The default is E.




Field Description

Category if 1st ref. RENAME NEW DSN

Allows, by application, the option to INCLUDE a data set if the 1st

reference is RENAME for the new (NEW) data set. ASAP looks at the 1st reference of each data set and determines criticality based on the data set's disposition, data set access, setup options, and filters in the database. Most renamed data sets do not need to be included, unless you are using the Forward Recovery 'All data sets are critical' option, because they are no longer cataloged at the end of the application, however, it is not uncommon for applications to RENAME a data set and in the same step or a subsequent step CREATE the data set again as NEW. You may want to use Include if renamed data sets resurface during the application, such as may result after a reorganization or rebuilding of the data set. Whether the data set after reinstatement has the same contents as at the beginning of the application is not known to ASAP. Renamed data sets will be in the URD (Updated, Renamed, or Deleted) display regardless of the setting. Data sets with a disposition of NEW that are RENAMED to a new name can be Included (I) or Excluded (E) from the selection data set using this option. If the data set is uncataloged when the selection data set is built, the data set is excluded regardless of how this option is set. I – Include the data set. E – Exclude the data set. Switch IGNORED if 'Evaluate all data sets as critical' is set to Y. The default is E.

Use SMF data in selection data set

Specifies if data collected by the RSP IEFU83 (SMF record collection) exit or by batch SMF Scan will be considered and evaluated when the selection data set is built. Y – indicates the data will be used. N – indicates the data will not be used. The INI default is Y. The default is Y.

Use JCL data in selection data set

Specifies if data collected by the RSP IEFUJI (RSP JCL Capture) exit will be considered and evaluated when the selection data set is built. Y – indicates the data will be used. N – indicates the data will not be used. The default is Y.




Field Description

SELECTION Dsn Format This field specifies the format of the statements generated by ASAP. ABARS, the default, writes the records to a selection data set as INCLUDE, EXCLUDE, ALLOCATE, and ACCOMPANY statements. The selection data set is input to ABACKUP. DSS causes ASAP to write the records to a data set using DFSMSdss logical DUMP control statements. Data sets in the ACCOMPANY or ALLOCATE lists are not supported by DSS and therefore are ignored. The DMS option causes ASAP to generate Brightstor CA-Disk logical DUMP control statements for data sets in the INCLUDE list. Data sets in the ACCOMPANY and ALLOCATE lists are ignored. The FDR option causes ASAP to generate FDR logical DUMP control statements for data sets in the INCLUDE list. Data sets in the ACCOMPANY and ALLOCATE lists are ignored. The LIST option causes a list of data set names to be generated, including all data sets which meet the INCLUDE, ACCOMPANY, and ALLOCATE criteria. The default is ABARS.

RSP cycles to include in Sel. DS. Specify how many cycles' worth of RSP data are to be included in building the selection data set. Multiple cycles of RSP data can be included in the selection data set built by APPLEND or VERIFICATION processing. Indicate the number of RSP cycles to include. If multiple cycles of RSP data are required, the 'Number of RSP cycles to retain' option in the RSP section must be at least the number specified in this option. When a data set is referenced in more than one cycle, ASAP uses the first reference from the first cycle to determine criticality. The default is 1.




Field Description

Evaluate all data sets as critical This option specifies whether an application will be set up for 'Forward Recovery' or 'Rerun Recovery'. Y – the Forward Recovery Option. All input and output data sets are classified as critical (minus what you exclude with filters) and are written to the selection data set as INCLUDE or ACCOMPANY. You may override the critical classification using Universal, Global, or Local filtering. This feature may be used in combination with the following features: • Add entries for missing GDSs option – F (Forward Recovery). • Category for new GDS if new GDS is only reference to GDG: I • ABARS category for new generations: I

Exception to all data sets considered critical: When using the ABARS format for the selection data set, normally the selection data set category written by ASAP 'Excluded due to Normal Evaluation' is for the Rerun Recovery option. When 'All Data Sets are Critical' option is set to support Forward Recovery and GDG base names are read (not generation data sets), the base names are put in the 'Excluded due to Normal Evaluation' category because ABARS won't allow GDG base names in the INCLUDE list, only the ALLOCATE list.

N – the Rerun Recovery option. Only data sets used as input to the application (existed before the application execution started) are considered critical. The default is N.

Detailed Comments in Sel. Data Set

This option generates additional comments in the selection data set to help determine why a data set was classified in a given category. Y – generate additional comments in the selection data set. N – do not generate additional comments in the selection data set. The default is N.




3.9 Verification GDG Options Section The following options control generation data sets (GDSs) at the end of the application (APPLEND) or during Verification before they are written to the selection data set. For more information on Verification, see Chapter 6, VERIFICATION – Creating the Selection Data Set.

----- VERIFICATION GDG Options -----GDS names in Selection Data Set: B

Evaluate GDG entries from JCL data: Y Evaluate GDG entries from SMF data: Y

Expand Base only references: NAdd entries for missing GDSes: M

For forward recovery ONLYCategory for new GDS if new GDS

is only reference to GDG: I

ABARS category for missing GDSes: I

ABARS category for new generations: E

<= ( R = RelativeA = Absolute B = Both )

<= ( Y/N )<= ( Y/N )<= ( Y/N )<= ( N = No

M = Min for rerun F = Forward recoveryA = All cataloged )

<= ( I = IncludeE = Exclude )A = Allocate )

<= ( I = IncludeA = Allocate )

<= ( E = ExcludeI = Include A = Allocate )




How Generation Data Sets Are Added to the ASAP Database

Generation data sets are added to the ASAP Database from RSP's JCL Capture and SMF Capture or batch SMF Scan.

GDSs added from RSP JCL Capture are added using relative names (GDGbase(nn)). The relative name is adjusted based on the catalog entries when APPLEND or Verification is run and a catalog lookup occurs.

Example:

Job Name Relative GDG in JCL Relative GDG in Database when APPLEND or Verification is run

JA001 PROD.DAILY.PARM(-2) PROD.DAILY.PARM(-3)

JA001 PROD.DAILY.PARM(-1) PROD.DAILY.PARM(-2)

JA001 PROD.DAILY.PARM(0) PROD.DAILY.PARM(-1)

JA001 PROD.DAILY.PARM(+1) PROD.DAILY.PARM(0)

GDSs added from RSP SMF Capture or Batch SMF Scan are added using absolute names – gdgbase.GnnnnVnn.

Example:

PROD.DAILY.PARM.G0004V00




When both RSP JCL Capture and RSP SMF Capture (or batch SMF scan) are used to collect database records, both the relative and absolute names are stored in the database. The option 'GDS names in Selection Data Set' determines if the relative name, absolute name, or both is used in the selection data set and which entries shall be used in making decisions.




3.9.1 Verification GDG Options Field Descriptions The following fields are shown in the VERIFICATION GDG Options section.

Field Description

GDS names in Selection Data Set This option determines whether generation data set names in the selection data set should be ABSOLUTE (.G0000V00s), RELATIVE (0, -1, etc) or BOTH. R = Relative names (PROD.DAILY.PARM(0)). A = Absolute names (G0000V00s). B = Relative and Absolute. Names are derived from database entries obtained from RSP JCL capture, RSP SMF capture records, or both – providing the evaluation of JCL and/or RSP entries is selected (next option). If database entries exist from JCL and SMF (relative and absolute names), and this option is set to A or R, the undesired names are excluded. Absolute GDS names generated from relative database entries are refreshed from the catalog each time RSP APPLEND rebuilds the selection data set or Verification is run. APPLEND processing should be executed as soon as the application has ended to ensure correct resolution based on catalog entries at the end of the application (and before additional processing alters the status of a GDG). For a correct resolution of absolute to relative, building the selection data set must complete before any GDG activity alters the status of the GDG at the time the current cycle completed. The default is Relative and Absolute (B).

Evaluate GDG entries from JCL Whether GDG entries from JCL will be evaluated. data Y – GDG entries from JCL will be evaluated.

GDG entries from JCL are added to ASAP's database using the relative name. Use the 'GDG names in Selection Data Set' option to determine how GDGs are written to the selection data set. For more detailed information on adding GDGs, refer back to the previous topic, 'How Generation Data Sets Are Added to ASAP's Database'. N – bypasses evaluation of GDG entries from JCL data. The default is Y.

Note: If 'Use JCL data in Selection Data Set', described above, is set to N, it will override this option.




Field Description

Whether GDG entries from RSP SMF or (Batch SMF) will be Evaluate GDG entries from SMF evaluated.data Y – GDG entries from SMF will be evaluated. GDG entries from RSP or Batch SMF Scan are added to ASAP's database using the absolute name. Use the 'GDG names in Selection Data Set' option to determine how GDGs are written to the selection data set. For more detailed information on adding GDGs, refer back to the previous topic, 'How Generation Data Sets Are Added to ASAP's Database'. N – Bypasses evaluation of GDG entries from SMF data. The default is Y.

Note: If 'Use SMF data in Selection Data Set', described above, is set to N, it will override this option.

This option determines if GDG base-only entries from JCL or INCLUDE external filters should be expanded to absolute GDS names.

Expand Base only references

RSP SMF generates absolute names from a base name in the JCL. The base name itself is always excluded. Y – Converts the base name to absolute names. N – Causes the base-only reference to be excluded because base only references are not supported by ABARS. The default is N.




Field Description

This option determines if GDS entries not already present in the database at the time APPLEND is executed should be added. Use of this option prevents gaps in the GDS for GDGs referenced by the application.

Add entries for missing GDSes

For example: if generations '0' and '-2' are referenced by the application, when restored the '-2' generation becomes '-1' because the 'missing generation, '-1' was not referenced and therefore not included in the backup. N – Means that no additional GDS names will be added to the database. This option will produce a backup which when restored may cause the application to fail or produce unexpected results if there are any gaps in the GDSs for a GDG referenced by the application. (E.g., if the only relative generations referenced by the application are '0' and '-2', backing up just these two generations will cause the '-2' generation to be '-1' after recovery, assuming that the original '-1' generation is not recovered from another source.) M (Minimum for Rerun) – Causes all generations from the oldest referenced through the current generation ('0' before the application has run) at APPLEND execution to be added to the database if they were not already present. This option is called Minimum for Rerun because if any 'gaps' exist in the range of generations referenced, the relative generations will not be correct after a restore.

Note: The default evaluation of new generations (+1) is 'EXCLUDE' (consistent with Rerun Recovery). With Rerun Recovery, only input data sets are evaluated as critical and included in the selection data set. If during a rerun, an application is sensitive to the knowledge that new generations were indeed created; it may be necessary for these new generations to be restored. Refer to the option 'ABARS category for new generations' to force the inclusion of new GDSs on the Include or Allocate list of the selection data set.

MORE Î




Field Description

F (Forward Recovery) – Causes all generations required for forward recovery to be added to the database if they were not already

Add entries for missing GDSes cont

present at APPLEND. Forward Recovery positions the application for processing (forward) into the next cycle after recovery. It will cause the same number of oldest generations referenced, as there are new generations to be Excluded. It forces the choice for new generations to Include. It also forces 'ABARS category for missing GDSes = ALLOCATE' to INCLUDE but only for certain generations. This option applies to generation data sets only and does not ensure that all data sets required for forward recovery are included in the selection data set. Note: 'Forward Recovery' only applies to GDGs. It does not infer that all data sets needed for a Forward Recovery will be captured. Forward Recovery, in theory, is only dependable for generation data sets. If the switch 'Evaluate all data sets as critical' is set, both inputs and outputs are automatically included. However, using the rerun methodology where only inputs are included may provide forward recovery if you use mostly generation data sets. If, however, output files are not generation data sets but are required for Forward Recovery, the 'Evaluate all data sets as critical' switch should be set to include those output data sets. A (All Cataloged) – Causes all generations found in the catalog to be added to the database if not already present at APPLEND. The generations could still be excluded by a filter.

Note: Use caution when selecting this option for an application. It is common to drastically overstate the 'LIMIT' of the base catalog entry. This option is not necessary to force all generations into the selection data set. If the base name only was used in the JCL, and JCL data is being used, then the 'Expand Base Only References = Y' is specified, it will automatically occur.

MORE Î




Field Description

Add entries for missing GDSes cont

When data sets are added to the database using the 'Add entries for missing GDSes' option, this option provides the ability to place the added entries on the Include or Allocate list of the selection data set. I (Include) – Places the added entries on the INCLUDE list in the selection data set. A (Allocate) – Places the added entries on the ALLOCATE list in the selection data set. The default is I. Example 1: An application references '-2', '-1', '0' and (creates) '+1'. The '-2' generation will be excluded (actually '-3' after the job creating '+1' ends). When the next cycle runs, assuming the same JCL, the input generations '-2', '-1', and '0' will be the previous cycle's '-1', '0', and '+1'.

Example 2: Applications references '-5', '-4', '-3', '-2', '-1', '0', '+1', '+1' (two new generations). The '-5' and '-4' generations will be dropped. The same number of oldest generations as there are new generations created will be excluded.

Category for new GDS if new GDS is only reference to GDG:

This option applies only if 'Add entries for missing GDSes' is set to 'F' (Forward Recovery). It applies to new GDSs. I (Include) – Causes new GDSs to be included in the selection data set. Include is the default. E (Exclude) – Indicates that a new GDS will be excluded if no existing GDS for that GDG is referenced. A (Allocate) – indicates that a new GDS will be put on the ALLOCATE list in the selection data set. By default, new data sets are excluded (unless the option 'Evaluate all data sets as critical' is set to Yes (Y)'. This option is used to force new GDSs to be added to the database and included in either the Include list (I), Allocate list (A), or Exclude (E) list in the selection data set. Switch IGNORED if 'Evaluate all data sets as critical' is set to Y. Both input and output data sets will automatically be included. Forward Recovery in theory is only dependable for generation data sets. If the switch 'Evaluate all data sets as critical' is set, both inputs and outputs are automatically included. However, using the rerun methodology where only inputs are included may provide forward recovery if you use mostly generation data sets. If, however, output files are not generation data sets but are required for Forward Recovery, the 'Evaluate all data sets as critical' switch should be set to include those output data sets. The default is I (Include).




Field Description

ABARS category for missing GDSes

This option applies to data sets added from the 'Add Missing GDSes' option and is used to determine the ABARS selection data set category. I = Include A = Allocate If, after a restore, the application is to be rerun exactly as it was run originally, you may save backup time by only Allocating the unreferenced GDSs. The default is I (Include).

ABARS category for new generations

This option applies to GDSs found to be new and is used to determine the ABARS selection data set category. I = Include A = Allocate E = Exclude New data sets are normally excluded. This option may be used to force the category for new GDSs to Include or Allocate. The default is E (Exclude).




3.10 Backup Options Section The Backup Options section is provided if both ASAP and Backup & Recovery Manager Suite selectable product All/Star are licensed, and you wish to use the optional features available in the Application Backup and Restore feature of All/Star.

The optional features are:

• Ability to compare ASAP critical data set list against All/Star discovered backups. • Ability to restore data sets for ASAP applications and specific cycles within an application. • Prove that critical data is backed up.

For more information on the Application Backup and Restore feature of All/Star, see Chapter 12, All/Star: Application Backup and Restore of the Backup & Recovery Manager Suite User Guide: All/Star.

--- BACKUP OPTIONS ---BACKUP CYCLES TO RETAIN: 001

3.10.1 Backup Options Field Description The following field is shown in the Backup Options section.

Option Description

Optional. Ignore if not using the Application Backup and Restore feature of All/Star.

BACKUP CYCLES TO RETAIN

This field defines how many application cycles will be tracked by All/Star in the Backup & Recovery Manager Suite Inventory Data Set. Whereas the ASAP option allows nn cycles to be tracked, All/Star tracks cycles including the backup information found for each critical data set discovered by ASAP, hence allowing restoration of the data sets peculiar to a given application cycle. For more information on the Application Backup and Restore feature of All/Star, see Chapter 12, All/Star: Application Backup and Restore of the Backup & Recovery Manager Suite User Guide: All/Star The default is 001.

NOTE: ASAP’s option to track more than one cycle only affects how many cycles' worth of raw input (i.e. SMF and JCL information) are saved. These records are called Data Set Detail records (DSD). If in the ASAP Application AutoBuild Options menu, Option 0 – Setup, the cycles ("Number of RSP cycles to retain" "Number of JCL cycles to retain"), are set higher than one (in general 1 is used and is not the number of application backup cycles tracked by All/Star), the DSD records for the various cycles are combined, and analyzed, and the result is the creation of Data Set Records (DSR). These records are built for the last cycle completed, and reflect the results of Option 0 – Setup Options, and filters. They are used to generate a selection data set (list of data sets). At any time, only one version of the DSR records exist.




3.11 Selection Data Sets Section For a new application, SETUP must be invoked at least once. If you have not chosen a name previously, or if this is the first time in the Application SETUP Options panel for a new application, default names will appear in these fields. For more information about the selection data set, see Chapter 6, VERIFICATION – Creating the Selection Data Set.

--- SELECTION DATA SETS ---VERIFY => XYZ.APPL0001.SDS RSP/BATCH => XYZ.APPL0001.RSP.SDS

ASAP determines the selection data set name to be used by:

• If using ABARS, checks to see if an aggregate has been associated with the application, and if so, establishes the selection data set name from the ISMF data supplied when the aggregate was defined,

or

• Generates a name to be used if no ISMF aggregate name can be identified to be used with non-ABARS formats, or you can create your own 80-byte sequential data set.

Note: You must exit the SETUP panel (press Enter and then End) for the selection data set name to be created.

Two selection data set names are stored for each application. One is for RSP use, the other for ISPF Verifications. The same name can be used for both fields. By default, these two selection data set names will be the same. Via these SETUP options, you may change the names such that a different selection data set will be built by RSP versus Verification. Additionally, when Verification is selected in ISPF, a third selection data set name may be entered for a one-time build.

Note: PDSs and PDSEs are not a good choice for selection data sets used by ASAP. Because ASAP updates the selection data set, and due to the nature of PDSs and PDSEs, two or more members can't be written to at the same time. Sequential files are recommended.

3.11.1 Selection Data Sets Field Descriptions The following fields are shown in the SELECTION DATA SETS section.

Option Description

VERIFY Choose the selection data set names you want to use for foreground processing.

RSP/BATCH Choose the selection data set names you want to use for RSP or batch processing.




Chapter 4 4 JOB COLLECT – Collecting Application Job Structure

This chapter explains how to use ASAP job collection to identify the jobs that compose the application. Instructions are provided for interfacing with each job scheduling product supported by ASAP, in addition to several other methods to collect application job lists and define the application structure.

Contents:

• Overview of the Job Collection Process – page 4-2

• Job Collection with Unicenter CA-7 – page 4-10

• Job Collection with CONTROL-M – page 4-16

• Job Collection with Cybermation ESP – page 4-27

• Job Collection with Unicenter CA-Jobtrac – page 4-31

• Job Collection with TWS – page 4-41

• Job Collection with ASG-Zeke – page 4-44

• Job Collection with ISPF Edit – page 4-49

• Job Collection with Pre-Staged Data Set – page 4-51

• Job Collection with a User-Supplied Data Set – page 4-56

• Using Edit to Modify Job Scheduling Product's Job List/Structure – page 4-57

• Assigning Job Structure for Input Data Set Job Entries with the :STRUC Statement – page 4-57

• Batch Job Scan Command – page 4-61

• Using Job Name Filtering During Job Collection – page 4-61

• Reviewing Results of Job Collection – page 4-62

Mainstar Software Corporation ©2006 4-1 Chapter 4 SC23-6059-00 JOB COLLECT – Collecting Application Job Structure


- - -- - -

- - -


4.1 Overview of the Job Collection Process After the application has been defined to ASAP, the data-gathering process can begin.

Job collection identifies to ASAP which jobs belong to the application. This information is then placed in the ASAP Database for later use by other steps in the data-gathering process.

For each initial job collection event (except when using job name masks that are stored directly in the ASAP Database), ASAP submits a batch job task to interface with a specified job scheduling product or an input data set containing a list of job names. The actual collection of job elements (job entries and job structures) and saving them in the ASAP Database is accomplished by this batch job.

Figure 4-1: Overview of the job collection process

C O L L E C T I O N

)

Screen/

Batch JOB

Active Schedule Job Entries

Job Structures

Job Scheduling Products

Job Scheduling Database

Application (Job Setup

Information

ASAP Database

Job Entries Job Structures

Job Collection

Setup

Dialog Session

Unicenter CA-7 CONTROL-M Cybermation ESP Unicenter CA-Jobtrac TWS ASG-Zeke

User Supplied

The supported job scheduling products are listed below. Topics later in this chapter provide specific requirements for using each job scheduling product.

• Unicenter CA-7 • BMC CONTROL-M for z/OS • Cybermation ESP • Unicenter CA-Jobtrac • Tivoli Workload Scheduler (TWS) • ASG-Zeke

Job elements may also be defined outside of a job scheduling product using the input data set options listed below. They are discussed in separate topics in this chapter.

• ISPF Edit Mode • Job Pre-Staged Data Set • User-Supplied Data Set

When the job elements are saved to the ASAP Database, the current application's SETUP options (Option 0, SETUP), including job filtering masks are applied. The job collection event can be submitted at any time to modify job entries. Also, job elements previously collected using a job scheduling product or a Pre-Staged data set can be modified using the ISPF Edit Mode.

Chapter 4 4-2 Mainstar Software Corporation ©2006 JOB COLLECT – Collecting Application Job Structure SC23-6059-00



4.1.1 Application Job Entries The first task in defining an application to ASAP is to identify the job elements that make up the application. An application may consist of a single job entry, multiple job entries, or a series of many job entries with job structures controlling complex scheduling requirements.

In any case, ASAP needs to know what the job names are so that it can analyze the SMF data (SMF Scan) to find the data sets associated with the application.

The job elements used by different ASAP collection events are identified below.

Job Element Used By Description

Job Entries RSP JCL Capture (via UJI For RSP Monitoring and SMF Collection: exit) The individual job names are used for SMF RSP SMF Capture (via record matching purposes during the initial U83 exit) collection. Data sets referenced are Batch SMF Scan automatically saved in the ASAP Database.




4.1.2 Job Lists vs. Job Structures In any application, multiple job entries can be part of a simple job list or a job structure, controlled by a job scheduling product (Unicenter CA-7, Unicenter CA-Jobtrac, etc.).

Job List

A job list is a set of job names, associated with an application, that do not have predecessor/successor relationships. ASAP can automatically obtain the job names from the job scheduling product specified for the application, or from a job name list supplied to ASAP as an input data set.

Job Structure

A job structure is a set of job names, associated with an application, that have a prescribed order of predecessor/successor dependencies. A job structure has an initial job, called the Anchor, that is used to control the scheduling sequence of the succeeding jobs.

Inside of a job structure, any one of the succeeding jobs can be another Anchor job for a lower level job structure forming a complete application schedule.

Figure 4-2: Overview of the job structure concept showing multiple anchor jobs

JOB3 Anchor JobJOB21

JOB22

JOB30

Anchor Job

JOB4 - - -

JOB1

JOB2

JOB41

JOB42

JOB43

Anchor Job

S T R U C T U R E S

Typical Application Schedule

JOB31

JOB32

JOB33

In the example shown in Figure 4-2, the application consists of four total job structures, each having its own specific anchor job points (JOB1, JOB21, JOB31 and JOB41). Using the JOB1 structure as an example, its successor jobs are JOB2 to JOB4. JOB41's predecessor is JOB4 (in the initial JOB1 structure).

The application may be a set of PAYROLL jobs that have both daily and weekly cycle executions. If a daily cycle is used, then only job structures JOB1, JOB21 and JOB31 are executed. If a weekly cycle is used, then only JOB1 and JOB41 structures are executed. Therefore, the JOB1 structure is common to both execution cycles.




4.1.3 Determine the Job Collection Point ASAP job collection using a job scheduling product allows the specification of one or more job structure names (or anchor names).

Referring to the example job structure in Figure 4-2, if the JOB1 name was used as the starting collection point, then the resulting application job structure would consist of the four total structures and their job names as the job entries. If JOB41 was used as the starting anchor point, then only one structure would be collected for the application (the JOB41 elements).

l

(1)

Key Point: Referring to the example in Figure 4-2, ASAP allows the PAYROLL application schedule to be separated into two applications, Daily Payroll and Weekly Payroll, by using their unique anchor job name for the starting collection point. Any potentially large application can be separated into smaller sub-applications by using this technique during the job col ection event. The advantages of this approach are:

Backup of the application can be scheduled independently and concurrently with any other application backups. You have the capability to back up only that portion of the major application as necessary, (e.g., daily application vs. weekly application backups).




4.1.4 About the Application Job Collection Method Panel From the Application AutoBuild Options menu, select Option 1 (JOB COLLECT). The Application Job Collection Method panel (shown below) will be displayed. Specify the source of job name information for job collection. Choose from a supported job scheduling product, ISPF Edit or a user-supplied or Pre-Staged data set. You may also use ISPF Edit to modify job lists previously collected by a job scheduling product.

Figure 4-3: Application Job Collection Method Panel

.------------- ASAP Application JOB Collection Options -------------.| || Command ==> APPLICATION Name => XJCSM || || Select Application JOB Collection Method: || || 1 - CA7 || 2 - CONTROL-M || 3 – ESP || 4 - JobTRAC || 5 – TWS (OPC) || 6 - ZEKE || -- or -- || A - ISPF Edit Mode. || B - JOB Pre-Staged Dataset (Batch Mode). || C - User Supplied Dataset (Specify Name Below). || || Data set:=> ___________________________________________ <= || |'-------------------------------------------------------------------'

Dialog Input Options – Choose either normal ISPF Edit input or Data set containing job names.

When you choose any of the listed job scheduling products, a second set of screens, unique to the specific job scheduling product, will 'pop up' for you to use to supply selection criteria.




Fields on the Application Job Collection Method Panel

Select an option by entering the number or letter of the option. If the job names will be input from a user-supplied data set, specify the data set name. Press Enter to activate the selections. Press PF3 to return to the previous panel with no action taken.

Detailed information about each job scheduling product and input data set option is provided in a separate section in this chapter.

Field Description

APPLICATION Name This is the application name that was entered when Option 2 (SELECT/CREATE) was selected. This field cannot be altered on this panel. To select a different application for job collection, go back to the Application AutoBuild Options panel.

Select Application Job Collection Method: ASAP can collect information about the job structure for an application from a supported job scheduling product or from an input data set. Choose one of the following options to indicate where you want ASAP to obtain job data.

CA7 Select this option if you want ASAP to submit a batch job that will query Unicenter CA-7 about jobs that are associated with the application. To use this option, your installation must have Unicenter CA-7 installed, and the jobs that make up the application run must be under the control of Unicenter CA-7. The CA7 Job Structure Information pop-up panel will be displayed to allow you to enter the Unicenter CA-7 anchor job names and/or job name masks and the Unicenter CA-7 batch terminal identification. The requirements for using this method are described in the topic 'Job Collection with Unicenter CA-7' (page 4-10).

CONTROL-M Select this option if you want ASAP to submit a batch job that will query CONTROL-M about jobs that are associated with the application. To use this option, your installation must have CONTROL-M installed and the jobs that make up the application must run under the control of CONTROL-M. The CTL/M Collection Information pop-up panel will be displayed to allow you to enter the CTL/M scheduling file names and table member names. The requirements for using this method are described in the topic 'Job Collection with CONTROL-M' (page 4-16).




Field Description

ESP Select this option if you want ASAP to submit a batch job that will use the ESP SADGEN file to determine jobs associated with the application. To use this option, your installation must have Cybermation ESP installed and the jobs that make up the application must run under the control of Cybermation ESP. The Cybermation ESP input entry panel will be displayed to allow you to enter the Cybermation ESP job collection criteria for the application. The requirements for using this method are described in the topic 'Job Collection with Cybermation ESP' (page 4-27).

Jobtrac Select this option if you want ASAP to submit a batch job that will query Unicenter CA-Jobtrac about jobs that are associated with the application. To use this option, your installation must have Unicenter CA-Jobtrac installed and the jobs that make up the application must run under the control of Unicenter CA-Jobtrac. The Jobtrac Job Collection Information pop-up panel will be displayed to allow you to enter the Unicenter CA-Jobtrac anchor job names and job name masks and the Unicenter CA-Jobtrac input, output and history file data set names. The requirements for using this method are described in the topic 'Job Collection with Unicenter CA-Jobtrac' (page 4-31).

TWS (OPC) Select this option if you want ASAP to submit a batch job that will query TWS about jobs that are associated with the application. To use this option, your installation must have TWS installed and the jobs that make up the application must run under the control of TWS. The Specify TWS Application Names pop-up panel will be displayed to allow you to enter the TWS application name(s). The requirements for using this method are described in the topic, 'Job Collection with TWS' (page 4-41).

Zeke Selecting this option causes an ISPF Edit panel to be displayed. Select this option if you want ASAP to submit a batch job that will collect jobs from ASG-Zeke. To use this option, your installation must have ASG-Zeke installed and the jobs that make up the application must run under the control of ASG-Zeke. The requirements for using this method are described in the topic 'Job Collection with ASG-Zeke' (page 4-44).




Field Description

ISPF Edit Mode Select this option if you want to use an ISPF Edit session to enter the job names and job structure associated with an application. Select this option if your installation does not run under a job scheduling system and/or there are only a few job names or job name masks to enter. ISPF Edit may also be used to add, change, or delete entries previously collected using a job scheduling product. The requirements for using this method are described in the topic 'Job Collection with ISPF Edit' (page 4-49).

Job Pre-Staged Data Set

Select this option if you want ASAP to locate and validate job pre-staging data sets and submit a batch job for the job collection event. The Job Pre-Staging facility uses an input data set, supplied by the installation and defined to the BRMINI member of the PARMLIB, as input to the batch job collection event. The requirements for using this method are described in the topic 'Job Collection with Pre-Staged Data Set' (page 4-51).

User Supplied Data Set

Select this option if you want ASAP to submit a batch job with a data set supplied by the user as input for the job collection event. The user-supplied data set is created by the user and identified to ASAP as the input to the batch job collection event. Select this option if your installation does not run under a Job scheduling system and/or there are a large number of jobs associated with the application, it may be easier to provide the job names in a data set. The requirements for specifying job names are described in the topic 'Job Collection with a User-Supplied Data Set' (page 4-56).

Data Set This field is ignored unless the 'FROM User Supplied Data Set' option is selected. The name of the user-supplied 80-character fixed block sequential data set or PDS member that contains the list of job names associated with the application.




4.2 Job Collection with Unicenter CA-7 Job Management At installations that use Computer Associates' Unicenter CA-7 job scheduling product to control their production jobs, ASAP can obtain information about the structure of an application from CA-7. ASAP does this by submitting a batch job that logs onto the CA-7 batch terminal processor to issue the CA7 FSTRUC (Forecast Structure) command and LJOB command.

4.2.1 Steps to Schedule Initial Unicenter CA-7 Job Collection Use the ASAP Dialog job collection panels to schedule the initial job collection batch event. This builds a two-step batch job, which can then be scheduled as needed at any future time. For a detailed description of each procedure step, go to the page referenced in the table.

STEP

1

STEP DESCRIPTION

Set configuration values for Unicenter CA-7 in BRMINI PARMLIB member.

PAGE

4-11

2 Optional

Set up job name filtering for Unicenter CA-7. 4-11

3 Review/update Unicenter CA-7 input entry panel. 4-11

4 Edit/submit Unicenter CA-7 batch job collection. 4-14

5 Review Unicenter CA-7 job collection results. 4-15




4.2.2 Step 1: Set Configuration Values for Unicenter CA-7 in BRMINI PARMLIB Member The PARMLIB member BRMINI contains configuration and global options used by ASAP during the Unicenter CA-7 job collection event, and other interfaces to the Unicenter CA-7 job scheduling product. For information about coding the Unicenter CA-7 keywords, see the Backup & Recovery Manager Suite Installation & Maintenance Guide, Appendix B, BRMINI Configuration Values.

To change any Unicenter CA-7 related option, the normal dialog ISPF Edit service can be used against the member in the PARMLIB data set. Any changes made will take effect during the next dialog Unicenter CA-7 job collection request.

4.2.3 Step 2: Optional – Set Up Unicenter CA-7 Job Name Filtering If used, filtering must be set up before submitting the job collection. For more information about job name filtering, see 'Using Job Name Filtering During Job Collection' (page 4-61), and Chapter 9, FILTERS – Using Filters and Controls.

4.2.4 Step 3: Review/Update Unicenter CA-7 Input Entry Panel From the Application AutoBuild Options menu, select Option 1 (JOB COLLECTION). From the Application Job Collection Method panel, choose the CA-7 option. The Unicenter CA-7 input entry panel is displayed.

Figure 4-4: Unicenter CA-7 Input Entry Panel

Command ==>

SPECIFY CA7 Job Structure Information:

Current Application Name: PET <= Job Collection Mode ==> REPLACE <=

Current (Default) SCHID ==> 1 <= Add/Display Multiple SCHIDs ==> NO <=

CA7 UserID Name ==> UCC7JOBS <= CA7 Password ==> UCC7JOB <=

Supply ANCHOR Job Names Below:==> PET* ==> PAB* ==> ==> ==> ==> ==> ==> ==> ==> ==> ==> ==> ==> ==>

Supply Input; Use ENTER To ContinueUse PF1 For HELP ; Use PF3 To Terminate

The following fields are shown on the Unicenter CA-7 input entry panel.

Field Description

Current Application Name: This is the name of the application for which data is to be collected. This field is for information purposes only and cannot be changed on this panel.

Job Collection Mode Indicates the collection mode. MERGE – will combine any new job entries collected with existing job entries. MERGE is the default. REPLACE – will totally replace the existing job entries for the application with the new job entries collected.




Field Description

Current (Default) SCHID Indicates the default Unicenter CA-7 Scheduling ID value for this collection event. The default is 1. You may change this value to match your application's Unicenter CA-7 scheduling value. If multiple scheduling values are used for your application, then use the Add/Display Multiple SCHIDs option from the panel instead.

Add/Display Multiple SCHIDs This option allows a range of Unicenter CA-7 Scheduling ID values to be assigned for the job collection event instead of the Default SCHID value described above. To display and change the values, use YES next to this option. Instructions are provided in the topic 'Assign Alternate Unicenter CA-7 SCHID Values for Job Collections' (page 4-13).

CA7 UserID Name The userid to be used by ASAP when logging on to the Unicenter CA-7 batch terminal processor. This field is required. This field is saved in an ISPF variable if the DISPLAYCA7USERINFO field on the Global ASAP Setup Requirements panel is set to YES. If not, the Unicenter CA-7 UserID Name must be entered each time this panel is displayed.

CA7 Password The password to be used by ASAP when logging on to the Unicenter CA-7 batch terminal processor. This field is required. This field is saved in an ISPF variable if the DISPLAYCA7USERINFO field on the Global ASAP Setup Requirements panel is set to YES. If not, the Unicenter CA-7 Userid name must be entered each time this panel is displayed.

Supply ANCHOR Job Names Below:

Up to 15 job names or job name masks may be specified in these fields. These are the job names for which Unicenter CA-7 is to return the job structure to ASAP. Information is obtained only for jobs controlled by Unicenter CA-7. For Unicenter CA-7 jobs that run 'on-demand' (jobs that are not regularly-scheduled jobs and that are not triggered by other jobs) the entire job name must be specified. Via the Unicenter CA-7 FSTRUC command, ASAP will determine the order in which the specified jobs execute for each Anchor job name. Once the Unicenter CA-7 batch job submitted by ASAP completes, ASAP will place the information in its database. At least one job name or job name mask must be entered in these fields.




Assign Alternate Unicenter CA-7 SCHID Values for Job Collections

If your application uses a different SCHID value than the default, you may assign multiple alternate Unicenter CA-7 SCHID values to be used for the ASAP job collection event.

Any alternate Unicenter CA-7 SCHID values supplied will be included during the current and any future job collection events.

Note: The default SCHID value, specified in the BRMINI token CA7ALTSCHID, will be added to the alternate values if the BRMINI token CA7_INCLUDE_ALTSCHID is set to YES.

To assign alternate SCHID values and retain them for future job collection events, follow the steps below.

1. On the SPECIFY CA7 Job Structure Information panel shown below, specify YES for the 'Add/Display Multiple SCHIDs' field.

Command ==>

SPECIFY CA7 Job Structure Information:

Current Application Name: PET <= Job Collection Mode ==> REPLACE <=

Current (Default) SCHID ==> 1 <= Add/Display Multiple SCHIDs ==> YES <=

CA7 UserID Name ==> UCC7JOBS <= CA7 Password ==> UCC7JOB <=

Supply ANCHOR Job Names Below:==> PET* ==> PAB* ==> ==> ==> ==> ==> ==> ==> ==> ==> ==> ==> ==> ==>

Supply Input; Use ENTER To ContinueUse PF1 For HELP ; Use PF3 To Terminate

The Alternate CA7 SCHID Entries panel is displayed, as shown below.

Command ==>

Change Fields as Necessary;Use ENTER To Activate; Use PF3 To Cancel

--- Alternate CA7 SCHID Entries ---More: +

=> 1 34 57 88 106 109 115 129 130 134 <= => 145 147 150 160 200 <= => <= => <= => <= => <= => <=

continued on next page




continued from previous page

2. Make your changes to the panel: • Supply multiple blank delimited SCHID values or change existing entries. The SCHID

values entered must be between 1 and 255 and should be separated by at least one blank. The screen can be scrolled Up/Down to include additional entries.

• To reset or delete any or all existing SCHID values, use your cursor to clear each line value.

3. To cancel changes and return to previous panel, use PF3. Use Enter to activate (save) your changes. Any saved changes or additions will be retained within the application and used during the next job collection event.

After saving changes, the SPECIFY CA7 Job Structure Information panel will then display as:

Current (Default) SCHID ==> MULTIPLE <=

4.2.5 Step 4: Edit/Submit Unicenter CA7 Job Collection The panels below will be displayed to allow you to submit the batch job and, if necessary, to edit the JCL before the job is submitted. A job statement verification panel will be displayed, followed by a job submission panel.

Job statement verification panel:

REVIEW and/or Change JOB/JCL Statements as Required:Use ENTER To Submit JOB; or PF3 to Abort

Randomize JOB Name to Eight Characters ? ==> YES ( YES / NO )

//MSIS04TZ JOB (,101),'I. M. USER' ,CLASS=Z,REGION=0M,// NOTIFY=MSIS04T,MSGLEVEL=(1,0) ,MSGCLASS=X//* NEW BATCH JOB//*

Job submission panel:

Command ==> Current Application: PAYROLLMASAP AUTOBUILD Phase: JOB COLLECTION


EDIT JCL Prior to Submit. S SUBMIT JOB For Execution


Job submission panel options:

• To edit the JCL prior to submitting the event, key an S next to EDIT and press Enter. Any changes you make will be retained for the final submit request into JES.

• To submit the batch event, key an S next to SUBMIT and press Enter. • If you do not want to submit the batch job at this time, issue the End command or press PF3

to exit without submitting the batch job.




4.2.6 Step 5: View Results of Unicenter CA-7 Job Collection You can review the results of job collection events using these methods:

• Dialog display using option 6 (STATUS) from the Application AutoBuild Options menu. • Dialog display using Option 1 (LIST APPLICATIONS) from the ASAP Main Menu. • Examine the Batch job collection output reports.

For more information about reviewing job collection information, see the topic 'Reviewing Results of Job Collection' (page 4-62), and Chapter 8, Obtaining Application Information.

Unicenter CA-7 Batch Report

The following screen is an example of a batch JOBRPT output produced from a Unicenter CA-7 job collection event.

ORIGINAL JOBS FOR APPLICATION: ABTEST1 2004/12/15 08:50:28

JOBNAME PREDECESSOR -------- -----------

ABCDAILY ABCD1000 ABCD1100 ABCD1150 ABCD2000 ABCD2200 ABCD2400

ABCDAILY HAS

ABCDAILY ABCD1000 ABCD1100 ABCD1150 ABCD2000 ABCD2200

6 SUCCESSOR JOBS

ABCREQ1ABCREQ1 HAS NO SUCCESSOR JOBS

ABCREQ2ABCREQ2 HAS NO SUCCESSOR JOBS




4.3 Job Collection with CONTROL-M At installations that use the CONTROL-M job scheduling product to control their production jobs, ASAP can obtain information about the structure of an application from CONTROL-M. The CONTROL-M job scheduling product requires the installation to submit an ASAP constructed job, which will produce the CONTROL-M Job Flow report. The output of the job flow report is then used as input to the second ASAP step to save the job entries in the ASAP Database.

Figure 4-5: Overview of CONTROL-M Job Collection Process

LVL

CTMRFLW

CONTROL-M Job Flow Report Output 1PRODUCTED BY CONTROL-M 4.0.0 JOBS FLOW REPORT - BY GROUP 4TH DIMENSION SOFTWARE, LTD. ===========================

MEMBER DEPEND ON ODATE OF JOB (AND TIME) --------------------------------------------------------------- 1 HLPCO041 ODATE 010421 TIME FROM 0040 UNTIL 0500 1 HLPCO041 ODATE 010421 TIME FROM 0040 UNTIL 0500 1 SWTOM13 ODATE 010723 TIME FROM 0700 UNTIL 1 SWTOM14 ODATE 010723 TIME FROM 0700 UNTIL 1 LMCS ODATE 010725 TIME FROM 1100 UNTIL 1 CCRF ODATE 010725 TIME FROM 1130 UNTIL 1 CASCHED ODATE 010725 1 CDSCHED ODATE 010725

CONTROL-M Utility JCL

JOB Entries Input to ASAP

/ASAP DB FILE

ASAP Job Collection

Batch Processing

The CTMRFLW CONTROL-M utility EXEC is used to create the job flow report based upon input scheduling files and table member names, supplied on the Application SETUP Options panel. ASAP will automatically construct the proper two-step job to complete the job collection event.

The scheduling files and their table member names are defined by the installation's CONTROL-M product coordinator and can be supplied via the ASAP Dialog mode. They may contain multiple scheduling files (as input) for any ASAP application. The installation may also define standard scheduling files through definitions in the BRMINI PARMLIB member.




4.3.1 Steps to Schedule Initial CONTROL-M Job Collection Use the ASAP Dialog job collection panels to schedule the initial job collection batch event. This builds the two-step batch job, which can then be scheduled as needed at any future time. For a detailed description of each procedure step, go to the page referenced in the table.

STEP

1

STEP DESCRIPTION

Set configuration values for CONTROL-M in BRMINI PARMLIB member.

PAGE

4-17

2 Optional

Set up job name filtering for CONTROL-M. 4-17

3 Review/Update CONTROL-M input entry panel. 4-18

4 Edit/Submit CONTROL-M job collection. 4-21

5 Review CONTROL-M job collection results. 4-18

4.3.2 Step 1: Set Configuration Values for CONTROL-M in BRMINI PARMLIB Member The PARMLIB member BRMINI contains configuration and global options used by ASAP during the CONTROL-M job collection event, and other interfaces to the CONTROL-M job scheduling product. For information about coding the CONTROL-M keywords, see the Backup & Recovery Manager Suite Installation & Maintenance Guide, Appendix B, BRMINI Configuration Values.

To change any CONTROL-M related option, the normal dialog ISPF Edit service can be used against the BRMINI member in the PARMLIB data set. Any changes made will take effect during the next dialog CONTROL-M job collection request.

4.3.3 Step 2: Optional – Set Up Job Name Filtering If used, filtering must be set up before submitting the job collection. For more information about job name filtering, see 'Using Job Name Filtering During Job Collection' (page 4-61), and Chapter 9, FILTERS – Using Filters and Controls.



--------------


4.3.4 Step 3: Review/Update CONTROL-M Input Entry Panel From the Application AutoBuild Options menu, select Option 1 (JOB COLLECTION). From the Application Job Collection Method panel, choose the CONTROL-M option. The CONTROL-M input entry panel is displayed.

Figure 4-6: CONTROL-M input entry panel

Command ==> Application Name: CTLMAPPL

CTL/M Collection Information:Change Fields as Necessary; Use ENTER To Activate; Use PF3 To Return

More: + Job Collection Mode: REPLACE <= ( REPlace,MERge )

Table CTL/M Scheduling File Names:

--------------------------------------Member Names

=> XZ.SCHED.FILE1 <= => CLMEMBER <= => XZ.SCHED.FILE2 <= => NAME2 <= => XZ.SCHED.FILE3 <= => NAME3 <= => <= => <= => <= => <= => <= => <= => <= => <= => <= => <= => <= => <=

The values shown represent the default collection mode and any previous scheduling file information for the application. Change the field values as necessary.




The following fields are shown on the CONTROL-M input entry panel.

Field Description

Merge – Takes the new user input entries and merges them into your existing job elements and structures. The Merge option also allows you to combine any number of user input entries with previous job scheduling entries for the current application.

Job Collection Mode

Replace – Will replace any existing job elements and structures with your new user input entries. ASAP will completely rewrite any old (existing) entries, regardless of the previous Job Collection mode or type.

CTL/M Scheduling File Names Enter the names of the specific scheduling files and table members that correspond to the CONTROL-M job entries you wish to collect. Table Member Names The job entries shown for each table member will be saved and included in the final job entries for the ASAP application. Multiple scheduling files and table members can be used. Scroll Up/Down to extend the CTL-M input screen area to accommodate up to 15 input scheduling files and their table members.

Note: If this is the first job collection event, then no job entries have been collected previously. Therefore, the scheduling file names will either be blank or contain the names of the data set(s) defined in CTLM_SCHEDFILES in the BRMINI PARMLIB member. If this event is a re-collection of application job entries, then the scheduling file names and table members displayed will be the current/previous values for the application.




4.3.5 Step 4: Edit/Submit the CONTROL-M Job Collection When you are satisfied with the changes made to the CONTROL-M input entry panel, press Enter to activate (save) your entries, or press PF3 to return to the previous panel.

The panels below will be displayed to allow you to submit the batch job and, if necessary, to edit the JCL before the job is submitted. A job statement verification panel will be displayed, followed by a job submission panel.














The final JCL control statements are constructed by ASAP in a two-step batch job.

• STEP1 – Executes the CTMRFLW CONTROL-M collection utility. The scheduling file names and table members supplied from the input dialog screen are concatenated as input under the DAJOB DD name. The output file is pre-allocated and supplied as the DAREPORT DD name value.

• STEP2 – Executes the CONTROL-M ASAP job collection routine.




Figure 4-7: Overview of CONTROL-M Batch Collection Job

CONTROL-M Batch Collection Job ile inal Job

Pre-Allocated output fused to receive fFlow Report output. DAREPORT DD name used.

Scheduling File (and Table members) names are substituted and passed to EXEC as DAJOB DD name. //

+

/*

//

////

STEP2 EXEC ASAP - - -

//SYSIN DD * AMPCMD JOBSCAN

COLLTYPE(CTLM) + INFILE(KD.CLMOUTPT)

//JOBNAME JOB , ...... Job Statement Information

//STEP1 EXEC CTMRFLW //DAREPORT DD DISP=SHR,DSN=KD.CLMOUTPT //DAJOB DD DISP=SHR,DSN=KD.SCHED.FILE1(NAME1)

DD DISP=SHR,DSN=KD.SCHED.FILE2(NAME2) DD DISP=SHR,DSN=KD.SCHED.FILE3(NAME3)

--- ---

Output Job Flow Report

In the example in Figure 4-7, three scheduling files and their table members have been concatenated as the DAJOB DDname. The pre-allocated output file is assigned to the DAREPORT DDname.

Note: The CTMRFLW utility JCL used should not contain the DAREPORT and DAJOB DDname statements. If they exist, they will be overridden by the above ASAP constructed statements.

4.3.6 Step 5: View Results of CONTROL-M Job Collection

Results for JOBCOLL_CTLM_VERSION = C400

You can review the results of job collection events using these methods:

• Dialog display using option 6 (STATUS) from the Application AutoBuild Options menu. • Dialog display using Option 1 (LIST APPLICATIONS) from the ASAP Main Menu. • Examine the batch job collection output reports.


Status Dialog Display

To display the job names and the job anchor structures use option 6 (STATUS) from the Application AutoBuild Options menu and select display options from the Display Selections pop-up menu.




Figure 4-8: Application Job List

Row 1 to 14 of 582 Command ==> Application ==> CTLMAPPL

Collection Method ==> CONTROL-M Table Entries Valid Commands => NOte, SAVE and SORT(c)

-- Job Name -- -- Misc Descriptive Info ------------

ADABKUAT 1 ADABKUAT ODATE 010725 TIME FROM 1900 UNTIL ADABKUCJ 1 ADABKUCJ ODATE 010725 TIME FROM 0400 UNTIL ADABKUHS 1 ADABKUHS ODATE 010725 TIME FROM 0200 UNTIL BACKUPM 1 BACK UPM ODATE 010723 BECIDOWN 3 BECIDOWN BECISHUT ODATE 010725 BECIJRN4 2 BECIJRN4 BECISHUT ODATE 010725 BECISHUT 1 BECISHUT ODATE 010725 TIME FROM 2209 UNTIL BECIUP 1 BECIUP ODATE 010725 TIME FROM 0601 UNTIL BELLAS01 1 BELLAS01 ODATE 010725 TIME FROM 0130 UNTIL BELLAT00 1 BELLAT00 ODATE 010725 TIME FROM 0745 UNTIL BEMASSCT 2 BEMASSCT BECISHUT ODATE 010725 BEMASSS1 1 BEMASSS1 ODATE 010725 TIME FROM 0159 UNTIL BEMASS1T 1 BEMASS1T ODATE 010722 TIME FROM 0603 UNTIL

The Misc Descriptive Info field shows the contents of the CONTROL-M Table Job Flow report output as extracted by ASAP for each job entry listed on the left. The job name entries in the first column are the current contents of the scheduling files and table members used as input and generated from the CTMRFLW utility program.

Figure 4-9: Application Anchor Job Structures

Command ==> Row 183 to 196 of 625 Valid Commands => NOte, SAVE and SORT(c) APPLICATION ==> CTLMAPPL

(1) (2) (3)- JOB/Anchor - - Type - -- JOB Structure Elements -----------------

FINETD CTL/MFIPANBKP CTL/MFIPAYCD CTL/MFIPAYEXC CTL/MFIPDTANK CTL/MFIREOLED CTL/MFISCHED CTL/MFISHOUT CTL/MFISTD CTL/MFIVERIFY CTL/M

FIVERIF1 CTL/MFIVERIF2 CTL/MFIVP8J02 CTL/M

FINETD FIPANBKP FIPAYCD FIPAYEXC FIPDTANK GFSBGNDF FISCHED FISHOUT FISTD FIBKUPD2 FIBKUPD3 FIBKUPD4 FIBKUPD5 FIBKUPD6 FIBKUPD7 FIBKUPD0 FIBKUPD1 XIBKUPD1 FIBKUPI0 FIBKUPI1 FILISTD2

The field Job Structure Elements lists the successor jobs for the job named in the JOB/Anchor field. This information is extracted from the CTMRFLW output report using the DEPEND ON descriptive field.

Job entries that have the same name as a successor are assigned a name by ASAP.




Batch SYSPRINT Report

An example of the job entries in the batch SYSPRINT file from the last collection job is shown below. Information contained in the file has been extracted from the CTMRFLW output report.

CURRENT DATE = 11/15/01 CURRENT TIME = 09:46:32 PAGE = 2

J O B S C A N Output Summary:

Locating JOB List For Application: CTLMAPPL Job Collection Type: REPLACE

Options: NONEJob Entries Saved: By ALL JobsFiltering Status: ENABLED

Initial Anchor Job: CDINV04

JOB NAMES REMOVED BY FILTERING: WEU00617 WEU00301 WEU00461 WEU0461Y

Job Name: CONTROL-M Scheduling ( Job Flow Report ) Data:--------- ---------------------------------------------

HLPCO041 1 HLPCO041 ODATE 010421 TIME FROM 0040 UNTIL 0500 SWTOM13 1 SWTOM13 ODATE 010723 TIME FROM 0700 UNTIL SWTOM14 1 SWTOM14 ODATE 010723 TIME FROM 0700 UNTIL LMCS 1 LMCS ODATE 010725 TIME FROM 1100 UNTIL CCRF 1 CCRF ODATE 010725 TIME FROM 1130 UNTIL CASCHED 1 CASCHED ODATE 010725 CDSCHED 1 CDSCHED ODATE 010725 CELSCHED 1 CELSCHED ODATE 010725 CRSCHED 1 CRSCHED ODATE 010725 BESCHED 1 BESCHED ODATE 010725 DBSCHED 1 DBSCHED ODATE 010725 DPACFSCH 1 DPACFSCH ODATE 010725 DPCOTSCD 1 DPCOTSCD ODATE 010725 DPJSCHED 1 DPJSCHED ODATE 010725 FICTMSCH 1 FICTMSCH ODATE 010725 SWSCHED 1 SWSCHED ODATE 010725 DPJHABND 1 DPJHABND ODATE 010725 TESTJOB2 1 TESTJOB2 ODATE 010725 TIME FROM 1000 UNTIL SMSBKLRG 1 SMSBKLRG ODATE 010725 TIME FROM 0300 UNTIL WEDB2WEP 1 WEDB2WEP ODATE 010725 TESTJOB3 1 TESTJOB3 ODATE 010725 TIME FROM 1105 UNTIL SMSBKSTD 1 SMSBKSTD ODATE 010725 TIME FROM 0300 UNTIL



----------------------------------------------


An example of the Anchor Structure entries in the batch SYSPRINT file from the last collection job is shown below. Information contained in the file has been extracted from the CTMRFLW output report.

J O B SCHEDULING - Anchor/DEP Job List

DEP Job: ---------

Successor Job/Member Name List:

CDINV04 CDLOC03 DPPM2CAT DPPM2DLY HLPNITLY HLPCS007 BYSERIAL SORTSERL SORTSERL SER#LIST SER#LIST FTPJCLT FTPJCLT EISEDIT BECISHUT BEMASSCT

BECIJRN4 BE14RQPO BE22R2BA BEMASSCT BECIDOWNBECIDOWN

CDCICSCL CDDAILY CDDAILY CDCICSOP COTMSDLY VAULT KMDVAL KMDUJIGF CIMSDCO2 CIMSBULK CIMSDISK KMDADST9 KMDADSTM KMDADSTM KMDADSTG KMDLZR KMDDAMS KMDCCIR KMDBKUPW KMDBKUPW KMDWKRPT ADAROLL KICKOFF FIREOLED STARTUP XIMIS XISHOUT XILDPAJV XILDEMP XILDVINT XILDERIS XIGS8JW0

XFSEPNY XFSINDR XFSLEAV XFSSHOP XFSNCPR XIAD1JIC XIADVSM XIADCGM XFSIN91

XFSFADP XFSINF3

XFSX002 XFSINRP

XFSFALS XFSX003 XIBKUPI2 XFSEQPTXIBKUPMB XFSMBILL XFSRBILL XFSSR50

XFSSR51 XIBKUPFB XFSFBILL XFSFHWT XFSSR52 XFSSR54 XFSAM82 XFSA656 XFSA601 XFSIN40 XFSIN70 XIIATADD FIBKUPD1 FIMIS FISHOUT FILDSUSF FILDPAJV FILDEMP FILDVINT FILDERIS FIIATADD FIGS8JW0 GFSINR2 GFSEPNY GFSINDR GFSLEAV GFSSHOP GFSRECJ GFSARCH GFSNCP GFSNCPR FIAD1JIC FIADVSM FIADCGM GFSFADP GFSX002 GFSIN91

GFSFALS GFSINF3

GFSX003 GFSINRP

FIBKUPI2 GFSEQPT GFSRESJ GFSINB2 FIBKUPMB GFSMBILL GFSRBILL GFSSR50

GFSSR51 FIBKUPFB GFSFBILL GFSFHWT GFSSR52 GFSSR54 GFSAM82 GFSA656 GFSA601 GFSIN40 GFSIN70

FIREOLED GFSBGNDF




Results for JOBCOLL_CTLM_VERSION = C606

You can review the results of job collection events using these methods:



CONTROL-M Job Collection Reports

An example of the CONTROL-M job collection report displaying the structure of the jobs is provided below.

ORIGINAL JOBS FOR APPLICATION: CONTROLM1 2004/05/13 08:31:18

JOBNAME CTLM GROUP PREDECESSOR ------- ---------- -----------

ABCJOB03 XXXDMN1 ABCJOB02 XXXDMN1 ABCJOB03 ABCJOB04 XXXDMN1 ABCJOB02 ABCJOB01 XXXDMN1 ABCJOB04

ABCJOB03 HAS 3 SUCCESSOR JOBS

ABJOB13 XXXDMN2 ABCJOB14 XXXDMN2 ABCJOB13

ABJOB13 HAS 1 SUCCESSOR JOBS



In the above example, ABCJOB03 is succeeded by ABCJOB02, ABCJOB04, and ABCJOB01. Jobs ABCJOB13 and ABCJOB23 are independent from ABCJOB03 and have successor jobs.




If job filters exist for the ASAP application, the following report will also be created.

JOBS AFTER FILTERING FOR APPLICATION: CONTROLM1 2004/05/13 08:31:18

JOBNAME CTLM GROUP PREDECESSOR ------- ---------- -----------

ABCJOB03 XXXDMN1 ABCJOB02 XXXDMN1 ABCJOB03 ABCJOB04 XXXDMN1 ABCJOB02

ABCJOB03 HAS 2 SUCCESSOR JOBS



ABJOB23 XXXDMN3

ABCJOB24 XXXDMN3 ABCJOB23 ABJOB23 HAS 1 SUCCESSOR JOBS




4.4 Job Collection with Cybermation ESP ASAP uses the ESP SADGEN file to obtain job names from Cybermation ESP. ASAP does not initiate the ESP SADGEN; the ASP extraction uses the SADGEN file to create a job extract file which may be used for multiple application job collections.

4.4.1 Steps to Initiate Cybermation ESP Job Collection Use the ASAP Dialog job collection panels to schedule an ESP job collection batch event. For a detailed description of each procedure step, go to the page referenced in the table.

STEP

1

STEP DESCRIPTION

Set configuration values for Cybermation ESP in BRMINI PARMLIB member.

PAGE

4-27

2 Optional

Set up job name filtering for Cybermation ESP. 4-27

3 Review/Update the Cybermation ESP input entry panel. 4-27

4 Edit/Submit Cybermation ESP batch job collection. 4-28

5 View results of Cybermation ESP job collection. 4-30

4.4.2 Step 1: Set Configuration Values for Cybermation ESP in BRMINI PARMLIB Member Ensure that appropriate values have been set for Cybermation ESP keywords in the BRMINI PARMLIB member:

Section :JCL_Defaults

ESPJOBS ESPSADGN

For additional information, see the Backup & Recovery Manager Installation & Maintenance Guide, Appendix B, BRMINI Configuration Values.

4.4.3 Step 2: Optional - Set Up Job Name Filtering for Cybermation ESP If you wish to use job name filtering, set it up before submitting the job collection. For more information about job name filtering, see 'Using Job Name Filtering During Job Collection' (page 461) and Chapter 9, FILTERS – Using Filters and Controls.

4.4.4 Step 3: Cybermation ESP Input Entry Panel From the Application AutoBuild Options menu, select Option 1 (JOB COLLECTION). From the Application Job Collection Method panel, choose the Cybermation ESP option. The following Cybermation ESP input entry screen is displayed.

Supply the Cybermation ESP selection criteria, and then press End (PF3) to save.




Figure 4-10: Cybermation ESP input entry panel

File Help . ------------------------------------------------------------------------------EDIT SYS04184.T131424.RA000.PB.R0118086 Columns 00001 00080 Command ===> Scroll ===> PAGE ****** ***************************** Top of Data *****************************=NOTE= ENTER ESP JOB COLLECTION CRITERIA =NOTE= ESP_PREFIX EVENT PREFIX OR MASK =NOTE= ESP_EVENT ESP EVENT OR MASK =NOTE= ESP_APL ESP APPLICATION OR MASK =NOTE= ESP_SUBAPL ESP SUBAPPLICATION OR MASK =NOTE= JOB JOBNAME OR MASK =NOTE= =NOTE= EXAMPLE: =NOTE= ESP_PREFIX PFX1 PFX2 =NOTE= ESP_EVENT EVENT_001 EVENT_002 EVENT_1* =NOTE= ESP_APL AP* =NOTE= JOB AC1*E* AC1*F* AC1*G* =NOTE= JOB AC2 '''''' '''''' ****** *************************** Bottom of Data ****************************

The ESP Extraction File panel will be displayed with the file's data set name, creation date, and time. .-------------------------------------------------------------------. | ESP Extraction File || CMD: || ESP extraction data available || || Data set name Creation date, time || ASAP.EXTRACT.JOBS 2004/07/22 10:22:15 || || || Press ENTER to use existing file for application jobs. || Press END (PF3) to re-extract from current SADGEN file. || |'-------------------------------------------------------------------'

• Press Enter to use existing extraction file. • Press End (PF3) to run the Cybermation ESP interface to extract Cybermation ESP jobs only if

updates have been made for the ASAP application since the last time the extraction was run, or if the Cybermation ESP interface has not been run for the current version of Cybermation ESP.

4.4.5 Step 4: Edit/Submit Cybermation ESP Job Collection The panels below will be displayed to allow you to submit the batch job and, if necessary, to edit the JCL before the job is submitted. A job statement verification panel will be displayed, followed by a job submission panel.







---------- ------------ -----------


4.4.6 Step 5: View Results of Cybermation ESP Job Collection You can review the results of job collection events using these methods:



Sample Cybermation ESP Job Collection Report

ORIGINAL JOBS FOR APPLICATION: ABJOBS 2004/07/01 20:17:34 PAGE: 1

JOB NAME ESP PREFIX ESP EVENT PREDECESSOR -------

ABJOB03 ABJOBS AB0_DAILY ABJOB02 ABJOBS AB0_DAILY ABJOB03 ABJOB04 ABJOBS AB0_DAILY ABJOB02 ABJOB01 ABJOBS AB0_DAILY ABJOB04


ABJOB13 ABJOBS AB1_WEEKLY ABJOB12 ABJOBS AB1_WEEKLY ABJOB13 ABJOB11 ABJOBS AB1_WEEKLY ABJOB12


ABJOB23 ABJOBS AB2_DAILY ABJOB22 ABJOBS AB2_DAILY ABJOB23 ABJOB21 ABJOBS AB2_DAILY ABJOB22


The report above indicates the structure of the jobs. In this example, ABJOB03 is succeeded, in order, by ABJOB02, ABJOB04 and ABJOB01. ABJOB13 and ABJOB23 are independent from ABJOB03 and have succeeding jobs.


JOBS AFTER FILTERING FOR APPLICATION: ABJOBS 2004/07/01 20:17:34 PAGE: 1

JOB NAME ESP PREFIX ESP EVENT PREDECESSOR ------- ---------- ---------------- -----------

ABJOB03 ABJOBS AB0_DAILY ABJOB02 ABJOBS AB0_DAILY ABJOB03 ABJOB01 ABJOBS AB0_DAILY ABJOB02


ABJOB13 ABJOBS AB1_WEEKLY ABJOB12 ABJOBS AB1_WEEKLY ABJOB13 ABJOB11 ABJOBS AB1_WEEKLY ABJOB12


ABJOB23 ABJOBS AB2_DAILY ABJOB21 ABJOBS AB2_DAILY ABJOB23 ABJOB23 HAS 1 SUCCESSOR JOBS




4.5 Job Collection with Unicenter CA-Jobtrac ASAP can obtain information about the structure of an application from the Unicenter CA-Jobtrac job scheduling product. ASAP does this by submitting a batch job which queries the Unicenter CA-Jobtrac history file for applications scheduled for the current day.

4.5.1 Steps to Schedule Initial Unicenter CA-Jobtrac Job Collection Use the ASAP Dialog job collection panels to schedule the initial job collection batch event. This builds a two-step batch job, which can then be scheduled as needed at any future time. For a detailed description of each procedure step go to the page referenced in the table.

STEP STEP DESCRIPTION PAGE

1 Set configuration values for Unicenter CA-Jobtrac in BRMINI PARMLIB 4-31 member.

2 Set up job name filtering for Unicenter CA-Jobtrac. 4-31 Optional

3 Review/Update Unicenter CA-Jobtrac input entry panel. 4-31

Note: There are alternative options you may wish to use that require additional tasks to be performed. Instructions for the use of these options are documented in topics 'Loading an Alternate Forecast Schedule for Your Application' (page 4-36) and 'Using the Unicenter CA-Jobtrac Output Schedule Option (JOBTRACSCHEDOUT)' (page 4-39).

4 Edit/Submit Unicenter CA-Jobtrac batch job collection. 4-34

5 View results of Unicenter CA-Jobtrac job collection. 4-40

4.5.2 Step 1: Set Configuration Values for Unicenter CA-Jobtrac in BRMINI PARMLIB Member

The PARMLIB member BRMINI contains configuration and global options used by ASAP during the Unicenter CA-Jobtrac job collection event, and other interfaces to the Unicenter CA-Jobtrac job scheduling product. For information about coding the Unicenter CA-Jobtrac keywords, see the Backup & Recovery Manager Suite Installation & Maintenance Guide, Appendix B, BRMINI Configuration Values.

To change any Unicenter CA-Jobtrac related option, the normal dialog ISPF Edit service can be used against the BRMINI member in the PARMLIB data set. Any changes made will take effect during the next dialog Unicenter CA-Jobtrac job collection request.

4.5.3 Step 2: Optional – Set up Job Name Filtering for Unicenter CA-Jobtrac If you wish to use job name filtering, set it up before submitting the job collection. For more information about job name filtering, see the topic 'Using Job Name Filtering During Job Collection' (page 4-61), and Chapter 9, FILTERS – Using Filters and Controls.

4.5.4 Step 3: Review/Update Unicenter CA-Jobtrac Input Entry Panel From the Application AutoBuild Options menu, select Option 1 (JOB COLLECTION). From the Application Job Collection Method panel, choose the Jobtrac option. The Unicenter CA-Jobtrac input entry panel (JobTRAC Collection Information) is shown below.

Please note that there are alternative options you may wish to use that require additional tasks to be performed. Instructions for these tasks are documented in topics for these options: Loading an




Alternate Forecast Schedule for Your Application' (page 4-36) and 'Using the Unicenter CA-Jobtrac Output Schedule Option (JOBTRACSCHEDOUT)' (page 4-39).

Figure 4-11: Unicenter CA-Jobtrac input entry panel

Command ==> Application Name: NEWTEST1JobTRAC Collection Information:

JobTRAC PROC Name ==> PGM=GJTRMAIV <= Job Collection Mode ==> MERGE <= JobTRAC Input DDname ==> JOBHISTX <= ----- Alternate JCL Usage -----JobTRAC Output DDname ==> SYSPRINT <=JobTRAC CHKPTA DDname ==> JOBTRACP <= Use Alt SCHED JCL ==> NO

JobTRAC Alt SCL Member ==> NONE JobTRAC Input History Data Set Name:

=> 'JOBTR.HISTORY.FILE' <= JobTRAC Input CHKPOINT Data Set Name:

=> 'JOBTR.CHKPTA.FILE' <=

Supply JobTRAC ANCHOR Job Names Below:==> DSC* ==> JOB1 ==> JOB2 ==> JOB3 ==> ==> JOB5 ==> JOB6 ==> ==> JOB9

Supply Input; Use ENTER To ContinueUse PF1 For HELP Information ; Or Use PF3 To Terminate

When you press Enter your entries will be validated and syntax checked. To exit from the panel without submitting the batch job, issue an End command or press the PF3 key.

The following fields are shown on the Unicenter CA-Jobtrac input entry panel.

Field Description

Application Name This is the name of the application for which data is to be collected. This field can not be changed on this panel.

Jobtrac PROC Name The name of the cataloged procedure used for Unicenter CA-Jobtrac batch collection of application jobs from your current schedule. The default name is GJTRMAIV.

Job Collection Mode Indicates the collection mode. MERGE – (the default) will combine any new job entries collected with existing job entries. REPLACE – will totally replace the existing job entries for the application with the new job entries collected.

Jobtrac Input DDname The DD name to be used in the generated JCL for the input DD for Unicenter CA-Jobtrac control statements. The default is JOBHISTX.

Jobtrac Output DDname The DD name to be used in the generated JCL for output from Unicenter CA-Jobtrac. The default name is SYSPRINT.




Field Description

Jobtrac CHKPTA DDname The DD name for the Unicenter CA-Jobtrac Checkpoint DDname statement to be used in the final JCL submitted for the job collection event, if the checkpoint file is supplied. See the Backup & Recovery Manager Suite Installation & Maintenance Guide, Appendix B, BRMINI Configuration Values, for additional information.

Use Alt SCHED JCL This field enables or disables the use of the optional JCL member entered into the 'Jobtrac Alt SCL Member' field. You may assign a data set name value to the BRMINI keyword JOBTRAC_ALTSCHEDJCL and use the 'Jobtrac Alternate Schedule JCL' option with certain applications, then use this field to disable its use for other applications. If YES, the content of your JOBTRAC_ALTSCHEDJCL data set will be used. If YES is used and there is no value entered in the BRMINI for the JOBTRAC_ALTSCHEDJCL keyword, then the default GJTRMAIV utility JCL will be used for the initial job collection step. If NO, then an alternate schedule will not be used, even though a JOBTRAC_ALTSCHEDJCL value is assigned.

Jobtrac Alt SCL Member Optional field. Member name of the application's schedule in your installation's SCL library. This field is only valid when used in combination with the BRMINI value for keyword JOBTRAC_ALTSCHEDJCL, to load a temporary schedule for the application desired. If the JOBTRAC_ALTSCHEDJCL value is omitted or defaulted, then this value will show NONE on the input panel and an alternate forecast schedule JCL sequence will not be used. The member name used will be saved with the application's job collection information in the ASAP Database. For more information about this feature, see topic 'Loading an Alternate Forecast Schedule for Your Application' (page 4-36).

Jobtrac Input History Data Set Name

The name of the Unicenter CA-Jobtrac history data set that will be used to obtain information on job names. This is a required field. This value can be permanently assigned using the BRMINI value JOBTRACHISTDB. The value you supply on the panel will override the data set name value supplied in the BRMINI PARMLIB member.

Jobtrac Input CHKPOINT Data Set Name

The name of the Unicenter CA-Jobtrac checkpoint data set that will be used in the final JCL submitted for the job collection event. See the Backup & Recovery Manager Suite Installation & Maintenance Guide, Appendix B, BRMINI Configuration Values, for additional information.




Field Description

Up to 9 job names or job name masks may be specified in these Supply Jobtrac ANCHOR Job fields. These are the job names for which Unicenter CA-Jobtrac is to return the job structure to ASAP. Information is obtained only for jobs controlled by Unicenter CA-Jobtrac. Once the Unicenter CA-Jobtrac batch job submitted by ASAP completes, ASAP will place the information in its database. At least one job name or job name mask must be entered in these fields.

Names Below

See the next topic 'Supplying Unicenter CA-Jobtrac Anchor Job Names' for information about supplying acceptable anchor job names.

Supplying Unicenter CA-Jobtrac Anchor Job Names

The following example shows acceptable job name values:

Supply ANCHOR Job Names Below:==> ZRFED93 ==> CRFB* ==> BVCPA* ==> ==> ==> ==> ==> ==>

Use of the '*' character at the end of a job name value allows any job structure to be collected whose first characters match the job name mask supplied.




4.5.5 Step 4: Edit/Submit Unicenter CA-Jobtrac Job Collection After updating the Unicenter CA-Jobtrac input panel to your satisfaction and pressing Enter, if your panel entries passed syntax checking, the panels below will be displayed to allow you to submit the batch job and, if necessary, to edit the JCL before the job is submitted. A job statement verification panel will be displayed, followed by a job submission panel.

















4.5.6 Loading an Alternate Forecast Schedule for Your Application The Alternate Forecast Schedule option is available for Unicenter CA-Jobtrac job collections.

This option is controlled by a JCL member you create using the sample FORECAST JCL member, the JOBTRAC_ALTSCHEDJCL keyword in the BRMINI PARMLIB member and, alternatively, use of the panel field 'Jobtrac Alt SCL Member' and an ASAP symbolic parameter &SCHMEM.

By default, normal ASAP processing will build the necessary batch JCL to execute the GJTRMAIV Unicenter CA-Jobtrac utility program to produce an output SYSPRINT file. This SYSPRINT file represents all applications that are ready and scheduled (loaded) for the current date. In the second job step, ASAP processes the output SYSPRINT file looking for the supplied input job names. If your Unicenter CA-Jobtrac application is not scheduled for the current day or is unavailable, then ASAP will be unable to locate the application job names supplied. This situation could occur for any application schedule that is not loaded.

In the situation described above, an alternative to using the GJTRMAIV against the current Unicenter CA-Jobtrac History file, is to force a temporary alternate forecast schedule to be loaded for the application and then allow ASAP to analyze (via GJTRMAIV) the temporary schedule.

The FORECAST JCL member in the Unicenter CA-Jobtrac sample data set contains temporary forecast checkpoint JCL. Follow the steps described in the procedure table below to set up and run the alternate schedule JCL to load your alternate forecast schedule. The FORECAST JCL will run the following three Unicenter CA-Jobtrac programs:

• The FORMAT step executes GCJFFMT to clear the temporary forecast data set. • The LOAD step executes GTRVSCH to load and create a temporary forecast data set for the

application supplied in your SCL library used as SYSIN input. • The LIST step executes GJTRMAIV to list the schedule from the temporary forecast data

set.

An example of a modified forecast JCL member is shown after this procedure table.

STEP STEP DESCRIPTION

1 Copy the FORECAST member found in the Unicenter CA-Jobtrac sample data set to another data set and member and make the changes described in step 2 of this procedure to the copy.

Make the following changes to your new forecast JCL member. 2 • Strip off any job card statement information. • In each of the steps (FORMAT, LOAD, and LIST) of the forecast JCL change the

output data set name to a temporary forecast data set name that is different than your current installation production data set name.

• In the second step (LOAD step) of the forecast JCL supply the correct SCL data set and schedule member names to indicate which application schedule is to be created. The following two alternative approaches can be used to provide the correct SCL data set and schedule member names in your alternate forecast JCL. Please consult your Unicenter CA-Jobtrac product administrator if necessary.

Either:

Modify the second step (LOAD step) of the JCL to include the necessary SCL library names and members in the SYSIN file for the desired application schedules to be loaded. You will need to obtain the correct application SCL member name for your installation.

Or:

Modify the second step (LOAD step) of the JCL to include the necessary SCL library




name, but for the member name use the symbolic value 'SCHMEM. Now supply a member name in the Unicenter CA-Jobtrac input entry panel field 'Jobtrac Alt SCL Member'. When the JCL is submitted for execution, ASAP will substitute for &SCHMEM the name supplied for 'Jobtrac Alt SCL Member'. Once specified, the value entered for 'Jobtrac Alt SCL Member' will be retained and re-displayed for any future job collections against the ASAP application name. Its use is disabled when you specify NO for the optional panel field 'Use Alt SCHED JCL'. An example of a modified forecast JCL member using the &SCHMEM symbolic is shown after this procedure table.

Update the JOBTRAC_ALTSCHEDJCL keyword in the BRMINI PARMLIB member to the data set and member name where your alternate forecast JCL is located. This allows ASAP to locate the alternate schedule JCL to run to construct the proper batch jobstream statements.

3

Example: JOBTRAC_ALTSCHEDJCL = My.Forcast(Fmember)

For more information, see the Backup & Recovery Manager Suite Installation & Maintenance Guide, Appendix B, BRMINI Configuration Values.




An example of a modified forecast JCL member, using the &SCHMEM symbolic technique is shown below. The Unicenter CA-Jobtrac data set names will reflect your current installation naming convention.

Figure 4-12: Example of modified forecast JCL using &SCHMEM symbolic

//**************************************************//* JobTRAC V3R2M0 (C) LEGENT SOFTWARE, INC//* JobTRAC SCHEDULE FORCAST JCL //**************************************************//* CLEAR THE FORCAST CHECKPOINT DATA SET //**************************************************//*//FORMAT EXEC PGM=GCJFFMT //JCHECKPT DD DSN=NEW.JOBTRAC.FORCAST,DISP=OLD//*//**************************************************//* LOAD THE SCHEDULE(S) TO BE FORCASTED//**************************************************//*//LOAD EXEC PGM=GJTRVSCH //SYSPRINT SYSOUT=*//JOBTRAC4 DD DSN=NEW.JOBTRAC.FORCAST,DISP=SHR//JOBHIST4 DD DSN=SYS2.JOBTRAC.JOBHIST,DISP=SHR//TRACD000 DD DSN SYS2.PAS.DOCLIB,DISP=SHR//TRACD001 DD DSN=SYS2.PAS.GPCA.DOCLIB,DISP=SHR//WORK DD DSN=&&WORK,UNIT=SYSDA,DISP=(,PASS),// DCB=BLKSIZE=6080,SPACE=(CYL,20),//SYSIN DD *,DCB=BLKSIZE=6160@FCAST=95230// DD DISP=SHR,DSN=SYS2.JOBTRAC.SCL(&SCHMEM)//*//**************************************************//* LIST THE SCHEDULE(S) TO BE FORCAST//**************************************************//*//LIST EXEC PGM=GJTRMAIV,PARM='LIST,ALL'//SYSPRINT DD SYSOUT=* //IPLPRINT DD SYSOUT=* //SYSTERM DD SYSOUT=* //JOBTRAC4 DD DSN=NEW.JOBTRAC.FORCAST,DISP=SHR//JOBHIST4 DD DSN=SYS2.JOBTRAC.JOBHIST,DISP=SHR//*

In the above example: • The data set NEW.JOBTRAC.FORCAST is the temporary forecast name, used in the

FORMAT, LOAD, and LIST steps. • The data set SYS2.JOBTRAC.SCL is the current schedule library data set used in the LOAD

step. The member containing your application's temporary schedule, the name of which you entered in the panel field 'Jobtrac Alt SCL Member', will be substituted in place of the &SCHMEM ASAP symbolic.

• The LIST step (the GJTRMAIV utility) will produce an output report into the SYSPRINT file, which will be analyzed by ASAP. The SYSPRINT DD statement will be changed by ASAP in storage to reflect a previously allocated data set name before batch job submission.




4.5.7 Using the Unicenter CA-Jobtrac Output Schedule Option (JOBTRACSCHEDOUT) The Output Schedule option is available for Unicenter CA-Jobtrac job collections.

This option is controlled by the JOBTRACSCHEDOUT BRMINI keyword value and its contents. It allows the installation the flexibility of executing the GJTRMAIV utility program (to collect the current Jobtrac schedule) before the ASAP job collection and directing ASAP to process this file in lieu of generating the normal GJTRMAIV utility statements.

When this option is used (via its specification in BRMINI), the following alternate panel is displayed.

Figure 4-13: Unicenter CA-Jobtrac Collection Information panel for Output Schedule option

Command ==> JobTRAC Collection Information:

Application Name ==> NEWTEST1Pre-Defined Output File ==> XZ.JOBTRAC.SYSPRINT

Input Fields:Job Collection Mode ==> MERGE <=

==> DSC*Supply JobTRAC ANCHOR Job Names Below:

==> JOB1 ==> JOB2 ==> JOB3 ==> ==> JOB5 ==> JOB6 ==> ==> JOB9

Supply Input; Use ENTER To ContinueUse PF1 For HELP Information ; Or Use PF3 To Terminate

In the above panel example, the file XZ.JOBTRAC.SYSPRINT was defined as the JOBTRACSCHEDOUT value in the BRMINI member. This file will be used as input for all applications requiring the Unicenter CA-Jobtrac job collection event.

fields to be Note: Because the JOBTRACSCHEDOUT output was defined in the BRMINI, the above panel display only requires the Job Collection Mode and the Jobtrac Anchor Job Name supplied.

For additional information regarding the JOBTRACSCHEDOUT usage, see the Backup & Recovery Manager Suite Installation & Maintenance Guide, Appendix B, BRMINI Configuration Values.




4.5.8 Step 5: View Results of Unicenter CA-Jobtrac Job Collection You can review the results of job collection events using these methods:



The following output is an example of a batch SYSPRINT file from a successful Unicenter CA-Jobtrac job collection event. Based upon the input Anchor jobs supplied, the output listing displays both the anchor structures and any non-succeeding job structures.

Entries Displayed By Collection Order:

Sched Run -Job Name- -Status-SYSID---Bus Group-- -Time/Date- -Time/Date- --- Successors ---

CA3050AP WAIT N/A ALACA 08/11 21:45 N/A N/A CAXTRTAP CAXTR45 CA4000AP CA4100AP CA1500AP CABDF56I MI4000AP MI2000AP

CA4100AP CA4600AP CAXTRTAP CA3070AP CA3065AP CA3100AP CA3850AP CA4000AP CA4475AP CA6590AP CA6620AP MI2000AP SB1600AP CA1500AP CA9701AP

WAIT N/AWAIT N/AWAIT N/AWAIT N/AWAIT N/AWAIT N/AWAIT N/AWAIT N/AWAIT N/AWAIT N/AWAIT N/AWAIT N/AWAIT N/ACOMPLETE MVSC WAIT N/A

ALACA ALACA ALACA ALACA ALACA ALACA ALACA ALACA ALACA ALACA ALACA ALACA1 ALACA1 ALACA ALACA

08/11 22:15 N/A N/A CA4151AP 08/11 22:00 N/A N/A CA4410AP CA3075AP 08/11 23:06 N/A N/A CA4100AP CA456M 08/11 22:25 N/A N/A CA3075AP CA6620AP 08/11 22:45 N/A N/A CA3066AP 08/11 22:30 N/A N/A ***NONE*** 08/11 22:38 N/A N/A CA3853AP CA6620AP 08/11 22:20 N/A N/A CA4008AP 08/11 22:30 N/A N/A CAOC40AP CA3070AP 08/11 22:10 N/A N/A ***NONE*** 08/11 22:15 N/A N/A ***NONE*** 08/11 23:00 N/A N/A MI2005AP MI45BB0 08/11 22:07 N/A N/A CICA10AP 08/11 22:50 08/12 23:45 CAMRBDAP CA3066AP08/11 22:47 N/A N/A ***NONE***

Where possible, the SYSPRINT output will include the current status, the SYSID values and the list of all succeeding job structures, if any for the Anchor jobs. If the job has been successfully executed, then the last Run Date/Time values will also be included.

The same job list display, as well as any job structure entries collected, can be viewed using the ASAP Dialog option 6 (STATUS) from the Application AutoBuild Options menu for the application. When job collection is complete, the Unicenter CA-Jobtrac job entries and job structures are retained in the ASAP Database.




4.6 Job Collection with TWS At installations that use the TWS job scheduling product to control their production jobs, ASAP can obtain information about the structure of an application from TWS. ASAP does this by analyzing the report output of the job scheduling product. ASAP uses the TWS batch reporting utility, EQQBATCH, to obtain the jobnames associated with a TWS application name.

4.6.1 Steps to Schedule Initial TWS Job Collection Use the ASAP Dialog job collection panels to schedule the initial job collection batch event. This builds a batch job. For a detailed description of each procedure step go to the page referenced in the table.

STEP

1

STEP DESCRIPTION

Set configuration values for TWS in BRMINI PARMLIB member.

PAGE

4-41

2 Review/Update the TWS input entry panel. 4-41

3 Edit/Submit TWS batch job collection. 4-42

4 View results of TWS job collection. 4-43

4.6.2 Step 1: Set Configuration Values for TWS in BRMINI PARMLIB Member The BRMINI PARMLIB member contains configuration and global options used by ASAP during the TWS job collection event, and other interfaces to the TWS job scheduling product. For information about coding the TWS keywords, see the Backup & Recovery Manager Suite Installation & Maintenance Guide, Appendix B, BRMINI Configuration Values. The :ASAPOPC_PARMS section in Appendix B is relevant to the job collection.

To change any TWS-related option, the normal dialog ISPF Edit service can be used against the BRMINI member in the PARMLIB data set. Any changes made will take effect during the next dialog TWS job collection request.

4.6.3 Step 2: Review/Edit TWS Input Entry Panel From the Application AutoBuild Options menu, select Option 1 (JOB COLLECTION). From the Application Job Collection Method panel, choose the TWS option. Fill in the fields on the TWS input entry panel. Press Enter to validate the entries.

Figure 4-14: TWS input entry panel

Command ==>

ASAP Application Name: EMTEST2 <=

SPECIFY TWS Valid Date > 03/05/2004 <=MM/DD/YYYY

Use ENTER To Continue Use END Key(PF3) To Terminate




An ISPF Edit panel will be displayed. Supply the TWS application names or masks in the edit panel and press (PF3) to save.

=NOTE= ENTER TWS JOB COLLECTION VALUES =NOTE= TAPL TWS APPLICATION OR MASK =NOTE= =NOTE= EXAMPLE: =NOTE= TAPL APPL1* APPL2* APPL3 000001 TAPL SMFDAILY* OTHER*

4.6.4 Step 3: Edit/Submit TWS Job Collection After updating the TWS input entry panel to your satisfaction, press Enter to submit a batch job collection.


















4.6.5 Step 4: View Results of TWS Job Collection You can review the results of job collection events using these methods:



Sample TWS Batch Report

The following panel is an example of a batch JOBRPT output produced from a TWS job collection event.

ORIGINAL JOBS FOR APPLICATION: TWTEST1 2004/02/03 08:50:28

JOBNAME PREDECESSOR -------- -----------

SMFDAILY SMFD1000 SMFD1100 SMFD1150 SMFD2000 SMFD2200 SMFD2400

SMFDAILY HAS

SMFDAILY SMFD1000 SMFD1100 SMFD1150 SMFD2000 SMFD2200

6 SUCCESSOR JOBS

SMFREQ1SMFREQ1 HAS NO SUCCESSOR JOBS

SMFREQ2SMFREQ2 HAS NO SUCCESSOR JOBS

ASAPOPC parameters can be found in Appendix B, BRMINI Configuration Values, of the Backup & Recovery Manager Suite Installation & Maintenance Guide.




4.7 Job Collection with ASG-Zeke ASAP uses the ZEKEUTL utility to obtain job names from ASG-Zeke.

4.7.1 Steps to Initiate ASG-Zeke Job Collection Use the ASAP Dialog job collection panels to schedule an ASG-Zeke job collection batch event. For a detailed description of each procedure step go to the page referenced in the table.

STEP

1

STEP DESCRIPTION

Set configuration values for ASG-Zeke in BRMINI PARMLIB member.

PAGE

4-44

2 Optional

Set up ASG-Zeke job name filtering. 4-44

3 Review/Update the ASG-Zeke input entry panel. 4-45

4 Edit/Submit the ASG-Zeke batch job collection. 4-46

5 View results of the ASG-Zeke job collection. 4-48

4.7.2 Step 1: Set Configuration Values for ASG-Zeke in BRMINI PARMLIB Member Ensure that appropriate values have been set for the following ASG-Zeke keywords in the BRMINI PARMLIB member. For additional information, see the Backup & Recovery Manager Suite Installation & Maintenance Guide, Appendix B, BRMINI Configuration Values.

In the :ASAP section:

JOBCOLL_ZEKE_JCLLIB JOBCOLL_ZEKE_JCLLIB02 JOBCOLL_ZEKE_JCLLIB03 JOBCOLL_ZEKE_VERSION JOBCOLL_ZEKE_ZEKEUTL JOBCOLL_ZEKE_ZEKEUTL02 JOBCOLL_ZEKE_ZEKEUTL03

In the :JCL_DEFAULTS section:

JOBSSPCEZEKEOUTF ZEKEOUTPZEKEJOBS ZEKESPCE

4.7.3 Step 2: Optional - Set Up Job Name Filtering for ASG-Zeke If you wish to use job name filtering, set up a job name filtering scheme before submitting the job collection. For more information about job name filtering, see 'Using Job Name Filtering During Job Collection' (page 4-61) and Chapter 9, FILTERS – Using Filters and Controls.




4.7.4 Step 3: Review/Update ASG-Zeke Input Entry Panel From the Application AutoBuild Options menu, select Option 1 (JOB COLLECTION). From the Application Job Collection Method panel, choose the Zeke option. The following ASG-Zeke input entry panel is displayed. Supply the ASG-Zeke selection criteria, and then press End (PF3) to save.

Figure 4-15: ASG-Zeke input entry panel

File Help . ------------------------------------------------------------------------------EDIT SYS98342.T131424.RA000.PB.R0118086 Columns 00001 00080 Command ===> Scroll ===> PAGE ****** ***************************** Top of Data *****************************=NOTE= ENTER ZEKE JOB COLLECTION VALUES =NOTE= JOB JOB NAME OR MASK =NOTE= ENAME =NOTE= ZAPL

EVENTNAME OR MASK (MAX LEN IS 12)ZEKE APPLICATION OR MASK

=NOTE= =NOTE= =NOTE= GROUP =NOTE=

ZEKE 4.20 (MAX LEN IS 3)ZEKE 4.22 & HIGHER (MAX LEN IS 8)GROUP ID OR MASK (MAX LEN IS 3)

=NOTE= EXAMPLE: =NOTE= JOB AC1*E* AC1*F* AC1*G* =NOTE= JOB AC2* =NOTE= ENAME DLYAC* =NOTE= ZAPL AP* =NOTE= GROUP GP1 ==MSG> -Warning- The UNDO command is not available until you change==MSG> your edit profile using the command RECOVERY ON.'''''' '''''' ****** *************************** Bottom of Data ****************************

An ASAP Application Job Collection Options pop-up panel will be displayed. It notifies you if ASG-Zeke interface data is already available from a previous extraction and the date the data was created.

.------------- ASAP Application Job Collection Options -------------.| Zeke Extraction File || CMD: || Zeke Interface Data AVAILABLE || || Data was created on yyyy/mm/dd || || || Press ENTER to use existing file for application jobs. || Press END (PF3) to re-extract all Zeke jobs. || |'-------------------------------------------------------------------'

If you wish to use this existing extraction file, press Enter.

If updates have been made for the ASAP application since the last time the extraction was run, or if the ASG-Zeke interface has not been run for the current version of ASG-Zeke, press End (PF3) to run the ASG-Zeke interface to extract ASG-Zeke jobs.




4.7.5 Step 4: Edit/Submit ASG-Zeke Job Collection The panels below will be displayed to allow you to submit the batch job and, if necessary, to edit the JCL before the job is submitted. A job statement verification panel will be displayed, followed by a job submission panel.





If multiple JOBCOLL_ZEKE_JCLLIB token values were specified, a ZEKE Execution Option panel will be displayed. Enter the number associated with your choice for the JCL library to be used.

ASAP Application Job Collection OptionsZEKE Execution Option Row 1 of 2

Scroll ===> PAGE Command ===> ________________________________________________

Enter choice => for JCL LIBRARY

-----------------------------------------------------------------1 USER.PROCLIB 2 JCL.LIB.#2 ************************ Bottom of data *************************

If multiple JOBCOLL_ZEKE_ZEKEUTL token values were specified, a ZEKE Execution Option panel will be displayed. Enter the number associated with your choice for the utility procedure to be used.

ASAP Application Job Collection OptionsZEKE Execution Option Row 1 of 3

Scroll ===> PAGE Command ===> ________________________________________________

Enter choice => for ZEKEUTL PROCEDURE

-----------------------------------------------------------------1 ZEKEUTL 2 ZEKEUT2 3 ZEKEUT3 ************************ Bottom of data *************************



---------------- ------------ ---------------


4.7.6 Step 5: View Results of ASG-Zeke Job Collection You can review the results of job collection events using these methods:



Sample ASG-Zeke Job Collection Reports

ORIGINAL JOBS FOR APPLICATION: ABJOBS 2001/10/26 20:17:34 PAGE: 1

JOB NAME ZEKE APPLICATION ZEKE GROUPID ZEKE EVENT NAME ------- ---------------- ------------ ---------------

ABJOB03 ABJOBS1 AB1 AB1 ABJOB03 ABJOB02 ABJOBS1 AB1 AB1 ABJOB02 ABJOB04 ABJOBS1 AB1 AB1 ABJOB04 ABJOB01 ABJOBS1 AB1 AB1 ABJOB01


ABJOB13 ABJOBS1 AB2 AB1 ABJOB13 ABJOB12 ABJOBS1 AB2 AB1 ABJOB12 ABJOB11 ABJOBS1 AB2 AB1 ABJOB11


ABJOB23 AB2 AB2 AB2 ABJOB23 ABJOB22 AB2 AB2 AB2 ABJOB22 ABJOB21 AB2 AB2 AB2 ABJOB21


The report above indicates the structure of the jobs. In this example, ABJOB03 is succeeded, in order, by ABJOB02, ABJOB04 and ABJOB01. ABJOB13 and ABJOB23 are independent from ABJOB03 and have succeeding jobs.


JOBS AFTER FILTERING FOR APPLICATION: ABJOBS 2001/10/26 20:17:34 PAGE: 1

JOB NAME ZEKE APPLICATION ZEKE GROUPID ZEKE EVENT NAME -------

ABJOB03 ABJOBS1 AB1 AB1 ABJOB03 ABJOB02 ABJOBS1 AB1 AB1 ABJOB02 ABJOB01 ABJOBS1 AB1 AB1 ABJOB01


ABJOB23 AB2 AB2 AB2 ABJOB23 ABJOB22 AB2 AB2 AB2 ABJOB22 ABJOB21 AB2 AB2 AB2 ABJOB21


ABJOB12 ABJOBS1 AB2 AB1 ABJOB12 ABJOB11 ABJOBS1 AB2 AB1 ABJOB11 ABJOB12 HAS 1 SUCCESSOR JOBS




4.8 Job Collection with ISPF Edit You may use ISPF Edit Mode to make changes to an application's job collection previously completed using either ISPF Edit or a job scheduling product, or if no job collection has been performed for the application, you may use this process to create the application's job entries list.

An example of an Edit session to input job names is shown below.

EDIT ----- SSXST.XYZ.AMPASAP.CA7MAXJB.ENTRIES(JOBINPUT) - 01. COLUMNS 001 072COMMAND ===> SCROLL ===> CSR ******************************* TOP OF DATA ******************************

* Supply Input Job Names as the First item in each Line. You may* include any optional descriptive text information following the* Job Name value separated by one or more blanks. You may add any* additional lines as necessary.* When completed, you may use PF3 to save your additions or changes.

* JOB346TR Anchor Structure JOB - Normal Payroll Execution.JOBA1 Payroll Job-1 (Daily)JOBA2 Payroll Job-2 ( ... )JOBA3 Payroll Job-3 ( ... )JOB999T Anchor Structure JOB- Special Payroll Execution.JOB341 Payroll Job-4 (Weekly)JOB342 Payroll Job-5 ( ... )JOB343 Payroll Job-6 ( ... )

****************************** BOTTOM OF DATA ****************************

In the above example, eight (8) job names were defined for an ASAP application. Each job name supplied has an optional comment string for description purposes, which will be saved with the job entries.

4.8.1 Steps to Collect or Edit Job Entries Using ISPF Edit Follow these steps to collect job entries using an ISPF Edit session. For a detailed description of each procedure step, go to the page referenced in the table.

STEP STEP DESCRIPTION PAGE

1 Create/Edit job entries list and job structure using ISPF Edit. 4-49

2 View results of ISPF Edit job collection. 4-50




4.8.2 Step 1: Create/Edit Job Entries List and Job Structure Using ISPF Edit From the Application AutoBuild Options menu, select Option 1 (JOB COLLECTION). From the Application Job Collection Method panel, choose the FROM ISPF Edit option. An ISPF Edit screen will be displayed.

If you have previously completed job collection for the application, using either ISPF Edit or a job scheduling product, then ASAP creates an Edit data set using the jobs previously collected and builds the :STRUC, displaying the existing job anchor structure and job entries. You may add, change, or delete the jobs/structures. If no job collection has been performed for the application, then a blank Edit screen will be presented. You can cancel out of Edit and any changes will be ignored, or, to save your entries press PF3.

Formatting Your Job Entries

When keying your job entries into the ISPF Edit data set, the following rules apply:

• A line can be no longer than 80 characters. • Lines beginning with an asterisk are ignored and may be used as comment statements. • Job names specified may be any valid job name up to eight characters in length. • A trailing asterisk (*) indicates a job name mask. All job names that match the characters

before the asterisk are selected. • Each job name or job name mask must be placed on a separate line. • Job names need not begin in the first column. However, they are blank delimited. That is,

ASAP considers the first non-blank field to be the job name and ignores any characters after the next blank.

Defining the Job Structure

If you create an application's jobs with ISPF (no other job collection was done), a default structure is created when the edited data set is saved.

If you enter the jobs in the order:

• JOB2 • JOB4 • JOB1

and do not use the :STRUC keyword, it will create the structure: JOB2 JOB4 JOB1

The first job becomes the predecessor for all the subsequent jobs.

To use the :STRUC statement to define the job structure, see the topic 'Assigning Job Structure for Input Data Set Job Entries with the :STRUC Statement' (page 4-57). Also, see other topics, 'Overview of the Job Collection Process' (page 4-2), and Chapter 1, ASAP Overview.

4.8.3 Step 2: View Results of ISPF Edit Data Set Job Collection You can review the results of job collection events using these methods:

• Dialog display using option 6 (STATUS) from the Application AutoBuild Options menu. • Dialog display using Option 1 (LIST APPLICATIONS) from the ASAP Main Menu.




- - -


4.9 Job Collection with Pre-Staged Data Set ASAP pre-staged data sets allow the user to supply an alternate input file to the ASAP job collection function outside of the normal ASAP job scheduling product support. ASAP will use the contents of the pre-staged data set as input to the job collection event.

Figure 4-16: Overview of Pre-Stage Facility

Anchor JobJOB21

JOB22

JOB30 JOB31

JOB32

JOB33

Anchor Job

JOB4

JOB1

JOB2

JOB3

JOB41

JOB42

JOB43

Anchor Job

The term pre-staged means that the user has created an input by placing job names into an external file. A pre-staged input file can be used either as the sole job collection input source, or merged with job input from either job scheduling products or input data set job entries.




4.9.1 Steps to Initiate Pre-Staged Data Set Job Collection Follow these steps to collect job entries using job pre-staged data sets. For a detailed description of each procedure step, go to the page referenced in the table.

STEP

1

STEP DESCRIPTION

Set configuration values for Pre-Staged Data Set job collection in BRMINI PARMLIB member.

PAGE

4-52

2 Create your Pre-Staged data set. 4-52

3 Review/Update Pre-Staged Data Set input entry panel. 4-53

4 Edit/Submit Pre-Staged Data Set batch job collection. 4-54

5 View results of Pre-Staged Data Set job collection. 4-55

4.9.2 Step 1: Set Pre-Staged Data Set Configuration Options in BRMINI PARMLIB Member The PARMLIB member BRMINI contains configuration and global options used by ASAP during the Job Pre-Staged job collection event and other interfaces to the Job Pre-Staged job scheduling product. Before invoking the ASAP Job Pre-Staging facility, you must define the pre-staging data set to ASAP. This input file can be either a PDS member or a sequential file. The unique pre-staged input file for each application must be specified in the BRMINI PARMLIB member so ASAP can locate and allocate the data set.

To change any Job Pre-Staged related option, the normal dialog ISPF Edit service can be used against the BRMINI member in the PARMLIB data set. Any changes made will take effect during the next dialog Job Pre-Staged job collection request.

For additional information, see the Backup & Recovery Manager Suite Installation & Maintenance Guide, Appendix B, BRMINI Configuration Values.

4.9.3 Step 2: Create Your Pre-Staged Data Set Create your user-supplied data set containing job entries and define the job structure.


When keying your job entries, the following rules apply:

The job name entries must be input and saved in the pre-staging data set. The file may be created using ISPF Edit or some other file creation method, using the same formatting rules as those used for user-supplied job entries. They are listed below.





To use the :STRUC statement to define the job structure, see the topic 'Assigning Job Structure for Input Data Set Job Entries with the :STRUC Statement' (page 4-57).




4.9.4 Step 3: Review/Update Pre-Staged Data Set Input Entry Panel From the Application AutoBuild Options menu, select Option 1 (JOB COLLECTION). From the Application Job Collection Method panel, choose the Pre-Staged Data Set option. A Pre-Staged Data Set input entry panel will be displayed. Review the field values and make any necessary changes.

Command ==>

Application Name: PRESTG2

Job Collection Mode: MERGE <= ( REPlace,MERge )JOB Pre-Stage DSN: 'XZ.TEST.PRESTAGE(PRESTG2)'

Change Fields as NecessaryUse ENTER To Activate; Use PF3 To Return

The Pre-Staged Data Set input entry panel fields are described below.

Field Description

Collection MODE MERGE – The default collection mode. Takes the new user input entries and merges them into your existing job elements and structures. The Merge option also allows you to combine any number of user input entries with previous job scheduling entries for the current application. REPLACE – Will replace any existing job elements and structures with your new user input entries. ASAP will completely re-write any old (existing) entries, regardless of the previous Job Collection mode or type.

Job Pre-Stage DSN The pre-staged data set and the member name developed from the BRMINI values.




4.9.5 Step 4: Edit/Submit Pre-Staged Data Set Job Collection After updating the Pre-Staged Data Set input panel to your satisfaction, press Enter to submit a batch job collection.












• To edit the JCL (using ISPF Edit) prior to submitting the event, select EDIT and press Enter. Any changes you make will be retained for the final submit request into JES.

• To submit the batch event, select SUBMIT and press Enter. • If you do not want to submit the batch job at this time, issue the End command or press PF3





4.9.6 Step 5: Review Results of Pre-Staged Data Set Job Collection You can review the results of job collection events using these methods:






4.10 Job Collection with a User-Supplied Data Set Follow these steps to collect job entries and job structure by providing a user-supplied data set. For a detailed description of each procedure step, go to the page referenced in the table.

STEP

1

STEP DESCRIPTION

Create your User-Supplied data set.

PAGE

4-56

2 Review/Update the User-Supplied Data Set input entry panel . 4-56

3 Submit User-Supplied Data Set batch job collection. 4-56

4 Review results of User-Supplied Data Set job collection. 4-56

4.10.1 Step 1: Create Your User-Supplied Data Set Create your user-supplied data set containing your job entries and define the job structure.


When keying your job entries, the following rules apply:





To use the :STRUC statement to define the job structure, see the topic 'Assigning Job Structure for Input Data Set Job Entries with the :STRUC Statement' (page 4-57).

4.10.2 Step 2: Review/Update Fields for User-Supplied Data Set Option From the Application AutoBuild Options menu, select Option 1 (JOB COLLECTION). From the Application Job Collection Method panel, choose the 'User Supplied Data Set' option. Specify the name of the user-supplied data set in the 'Data Set' field.

4.10.3 Step 3: Submit User-Supplied Data Set Batch Job Collection After updating the User-Supplied Data Set input entry panel to your satisfaction, press Enter to submit a batch job collection.

4.10.4 Step 4: Review Results of User-Supplied Data Set Job Collection You can review the results of job collection events using these methods:

• Dialog display using option 6 (STATUS) from the Application AutoBuild Options menu. • Dialog display using option 1 (LIST APPLICATIONS) from the ASAP Main Menu.





4.11 Using Edit to Modify Job Scheduling Product's Job List/Structure If you collect an application's jobs with a job scheduling product, then subsequently choose the ISPF Edit Mode for Job Collection for that application, ASAP creates an Edit data set using the jobs previously collected and builds the :STRUC. You can then add, change, or delete the jobs/structures. You can cancel out of Edit and any changes will be ignored. For more information about job structures, see the topics 'Overview of the Job Collection Process' (page 4-2), 'Assigning Job Structure for Input Data Set Job Entries with the :STRUC Statement' (page 4-57) and Chapter 1, ASAP Overview.

4.12 Assigning Job Structure for Input Data Set Job Entries with the :STRUC Statement To assign unique job anchor structures for the supplied job names, you can use the optional keyword :STRUC within the ISPF Edit screen. By using this technique, you can inform ASAP that unique jobs have a successor relationship to a previous job (i.e., the Anchor job), even though they are not part of a job scheduling system.

When the :STRUC statement is used, ASAP will save the Anchor job entries according to your structure specification. :STRUC is necessary to keep the entries in the correct processing order. Otherwise, ASAP will put them in alphanumeric order. You may include multiple job structure statements to completely define each structure.

For more information about job lists and job structures, see Chapter 1, ASAP Overview, and the topic 'Overview of the Job Collection Process' (page 4-2).




4.12.1 Creating the Job Structure Example 1:

In this example, all of the job names supplied were assigned as one job anchor structure, using the job JOB346TR as its anchor starting point. This is automatically assigned by ASAP, even though the subsequent jobs may have no relationship to the job name JOB346TR. This is done so the ASAP SMF Scan function can locate all of the job names supplied.

EDIT ----- SSXST.XYZ.AMPASAP.CA7MAXJB.ENTRIES(JOBINPUT)COMMAND ===> SCROLL ===> CSR ****** ************************ TOP OF DATA ****************************** * * Supply Input JOB Names as the First item in each Line. You may* include any optional descriptive text information following the* JOB Name value separated by one or more blanks. You may add any* additional lines as necessary.* When completed, you may use PF3 to save your additions or changes.* * JOB346TR Anchor Structure JOB - Normal Payroll Execution.JOBA1 Payroll Job-1 (Daily)JOBA2 Payroll Job-2 ( ... )JOBA3 Payroll Job-3 ( ... )JOB999T Anchor Structure JOB- SpecialJOB341 Payroll Job-4 (Weekly)JOB342 Payroll Job-5 ( ... )JOB343 Payroll Job-6 ( ... )

JOB346TR :STRUC JOB346TR JOBA1 JOBA2 JOBA3 JOB999T JOB341 JOB342 JOB343

****** ************************* BOTTOM OF DATA*****************************

The 1st Anchor

The 2nd

.

Anchor Structure Statements: job name represents the

name to be assigned. and subsequent job names in

the blank delimited string are its successor job entries

Notice the job name (JOB346TR) included at the top of the example before the :STRUC statement. In order for :STRUC to work, it is necessary to include a job name before the :STRUC statement. Any job name will work.




The resulting application Anchor job Structure is shown below.

Figure 4-17: Display Current JOB Anchor Chains Panel

Command ==> Valid Commands => FIND APPLICATION ==> CA7MAXJB


JOB346TR USR JOBA1 JOBA2 JOBA3 JOB999T USR JOB341 JOB342 JOB343

** END OF LIST **

Example 2:

In this example, the application has only a few jobs that are dependent on an Anchor job. The remaining jobs have no structure (are not triggered by anything).

EDIT ----- SSXST.XYZ.AMPASAP.CA7MAXJB.ENTRIES(JOBINPUT)COMMAND ===> SCROLL ===> CSR ****** ************************ TOP OF DATA ****************************** * * Supply Input Job Names as the First item in each Line. You may* include any optional descriptive text information following the* Job Name value separated by one or more blanks. You may add any* additional lines as necessary.* When completed, you may use PF3 to save your additions or changes.* * JOBA Quarterly Reconciliation Job AJOBB Quarterly Reconciliation Job BJOBC Quarterly Reconciliation Job C

JOB1 :STRUC JOB1 JOB2 JOB3 JOBX JOBY JOBZ

****** ************************* BOTTOM OF DATA*****************************

If there is a job entry listed before the :STRUC statement that isn't in the :STRUC list, ASAP creates a job anchor structure record for it. Also, if there is a job in the :STRUC list that isn't in the job entries before the :STRUC, ASAP builds a job entry record for it.




The resulting application Anchor job Structure is shown below.

Figure 4-18: Anchor Job Structure

Command ==> Valid Commands => FIND APPLICATION ==> CA7MAXJB


JOBA USR JOBA JOBB USR JOBB JOBC USR JOBC JOB1 USR JOB2 JOB3 JOBX USR JOBX JOBY USR JOBY JOBZ USR JOBZ

** END OF LIST **

Continuing :STRUC Statement Entries

If multiple successor job names are needed within :STRUC entries, you may continue defining the entries by using a '+' character to denote continuation to the next line(s).

An example of a continued :STRUC statement is shown below.

Figure 4-19: :STRUC Continuation Example

JOB346TR :STRUC JOB346TR JOBA1 JOBA2 JOBA3 JOBA4 JOBWEEK2 JOB341 JOB342 JOB343 JOB344 +

JOBWEEK3 JOBWEEK4 JOBEND JOB999T JOB661 JOB662

****************************** BOTTOM OF DATA ****************************

In the above example, the Anchor job: JOBWEEK2 will contain seven (7) succeeding job entries (JOB341, JOB342, JOB343, JOB344, JOBWEEK3, JOBWEEK4 and JOBEND).

4.12.2 Default Job Structure If you create an application's jobs with ISPF (no other job collection was done), a default structure is created when the edited data set is saved.

For example, if you enter the jobs in the order:

• JOB2 • JOB4 • JOB1

and do not use the :STRUC keyword, it will create the structure: JOB2 JOB4 JOB1

The first job becomes the predecessor for all the subsequent jobs.




4.13 Batch Job Scan Command The batch JCL submitted from Dialog mode for a Job Scan event varies for the job schedulers involved.

4.14 Using Job Name Filtering During Job Collection If you are using a job scheduling product, job name filtering is available for your ASAP job collection events (not available for OPC).

This is only an overview. For more information about job name filtering, see the topic 'Job Collection Filters Used with Job Scheduling Products' (page 9-4). You can limit the scope of jobs collected by establishing a job filtering pattern to INCLUDE and/or EXCLUDE job entries that are not required.

For example, if an application uses a single Anchor job name, which in turn returns both a daily and a weekly set of job entries, you can still separate the daily and weekly entries into two applications.

To use job name filtering, you must set up the filtering patterns before submitting the job collection event. To set up a filtering pattern:

1. Select Option 2 (FILTERS) from the Application AutoBuild Options menu.

2. Select MODIFY JOB COLLECTION FILTERS/CONTROLS => Y ( Y/N )

Job Name Filtering Mask Guidelines

• INClude Entries – Only the job names or masks supplied will be included in the final job collection list. Included names or masks are always processed first, before any Exclude type entries.

• EXClude Entries – The job names or masks supplied will be Excluded from the final job collection list. Excluded names or masks are processed after any Include type entries.

• Both Include and Exclude filtering entries – If multiple job names or masks are supplied, they must be blank delimited.

• Both Include and Exclude filtering entries – Must use acceptable masking characters and patterns. See the table of acceptable mask characters and patterns below.

Use the following masking characters and patterns.

Mask Description

* Used in front and/or at the end of the name, as a 'wild-card' character mask.

< Used to represent a single alpha-only character.

> Used to represent a single numeric-only character.

% Designates a single character (any type) placeholder value.

! Designates a single national character placeholder value. (e.g., @ # $)




Example:

JOBNAME INClude(s) => PET%%34* PEFFR* PROD76* *CSRD* <= JOBNAME EXClude(s) => PEFFR%7* PROD%%45 <=

Using the example above, only those job names that meet any of the following mask criteria will be included on the final job collection list.

• Start with PET, have two characters preceding a '34' and can end with any character. • Start with PEFFR and end with any characters. • Start with PROD76 and have any ending character. • Have the character string CSRD in any position in their name.

Using the example above, the following jobs will be excluded from the job collection list if they meet any of the following mask criteria:

• Start with the string PEFFR, plus a single character, plus a numeric 7, plus any ending character in that sequence.

• Start with string PROD, plus have two characters following of any type and end with a numeric 45.

Note: If you exclude a job that triggers subsequent jobs, those later jobs may also be excluded. For example, JOB1 is the anchor and it triggers JOB2 and JOB3. JOB3 triggers JOB4 that in turn triggers JOB5. If you exclude JOB3, JOB4 and JOB5 may also be excluded. The INI token JOBCOLL_EXCLUDE_DEP controls whether JOB3’s exclusion will exclude its dependent jobs or not.

4.15 Reviewing Results of Job Collection You can review the results of job collection events using these methods:


For more information about reviewing job collection information in Dialog see Chapter 8, Obtaining Application Information.




4.15.1 View Job Elements/Job Anchor Structures To view the job elements and/or the job anchor structures for the application using the Dialog facility, select STATUS (option 6) from the Application AutoBuild Menu.

A Display Selections pop-up window will open for the current application.

Figure 4-20: ASAP Application Display Selections

<VvRr.xx> --- A S A P Application AutoBuild Options -- -ASAP APPLICATION Display Selections

=> BK000001 Use S For Selections; Use PF1 For HELP

_ 1) N/A _ 2) Display Current JOB List _ 3) Display Current JOB Anchor Chains _ 4) Display Data Set Detail Records (JCL,RSP,Batch SMF) _ 5) Display Current JCL/SMF DSN Entries _ 6) Display Current JCL/SMF DSN Entries with URD Information _ 8) Display Summary of Last VERIFY Selection Data Set _ 9) Browse Selection Data Set Contents (Choose A,B or C )

A)VERIFY(One time build):BK.SDSTEST7

B)VERIFY(Database):BK.SDSTEST7

C)RSP:BK.SDSTEST6

_ 10) N/A_ 11) N/A




To Display the Current JOB List

To display the current job collection List entries, select Option 2 from the ASAP Application Display Selections panel, Display Current JOB List.

An example of a typical display is shown below.

Figure 4-21: Application/JOB List Elements

Command ==> APPLICATION ==> CA7MAXJB

Jobname Misc Descriptive InfoPFF001M COLLECTED 2004/12/15 07:24:13 PFF002M COLLECTED 2004/12/15 07:24:13 PFF003M COLLECTED 2004/12/15 07:24:13

To Display the Current Job Structures

To display the current job structures (or Anchor chains), select Option 3 from the ASAP Application Display Selections panel, Display Current JOB Anchor Chains.

An example of a typical display is shown below.

Figure 4-22: Application ANCHOR Job Structures

Valid Commands => FIND APPLICATION ==> CA7MAXJB

- JOB/Anchor - - Type - -- JOB Structure Elements -----------------

PFF001M CA7 PFF001M PFF002M CA7 PFF002M PFF003M CA7 PFF013M PFF030M PFF033M PFF036M PFF047M

PFF056M PFF051M PFF058M PFF059M PFF060M PFF064M PFF200M PFF070M PFF078M

PFF004M CA7 PFF004M PFF005M CA7 PFF005M PFF006M CA7 PFF006M PFF009M CA7 PFF009M PFF010M CA7 PFF010M PFF012M CA7 PFF012M PFF013M CA7 PFF030M PF033

PFF059M PF060 PFF078M

Job Structure Type Field:

Values can be:

CA7 = Unicenter CA-7 job collection CTL/M = CONTROL-M job collection ESP = Cybermation ESP job collection JBT = Unicenter CA-Jobtrac job collection TWS = TWS job collection ZEKE = ASG-Zeke job collection ISPF = ISPF Edit job collection PRESTG = Pre-Staged job collection UDSN = User Supplied Data Set




Chapter 5 5 SMF SCAN SETUP – Identifying Application Data Sets through Batch

SMF

The previous chapter described the process of collecting the jobs that make up an application, either from user-supplied information, or from a job scheduling product. This chapter describes the batch SMF Scan method.

Contents:

• Collecting Data Using Batch SMF SCAN – page 5-3

• SMF Record Requirements – page 5-3

• Batch SMF Data Set Requirements – page 5-4

• Batch SMF Scan Process Overview – page 5-5

• Batch SMF Scan Procedure – page 5-5

• Run Batch SMF Scan to Collect SMF Data – page 5-6

• Run Verification to Build Selection Data Set – page 5-7

• View the Results of Your SMF Collection – page 5-8

• Job Submission Sequence – page 5-11

• Reviewing the Results of the Batch SMF Scan – page 5-12

Mainstar Software Corporation ©2006 5-1 Chapter 5 SC23-6059-00 SMF SCAN SETUP – Identifying Application Data Sets through Batch SMF



5.1 About Batch SMF SMF data may be collected in batch, using SMF Scan, or dynamically, using RSP SMF Capture (which is recommended). For information about RSP SMF Capture, see Chapter 7, Real-time Selection Process (RSP). Identifying application data sets through batch SMF is an optional step after job collection. Batch SMF is intended for trials when the customer site isn't prepared to have RSP up, or for historical analysis of an application.

Note however that there are inherent limitations with a batch SMF process.

• Batch SMF data may be unreliable for Rerun Recovery because it may be difficult to pinpoint the exact start of the application. Rerun Recovery relies on the first reference of a data set, but what batch SMF sees as the first reference may not be the first reference at all, completely skewing the results.

• Batch SMF data is more reliable for Forward Recovery – using 'All Data Sets are Critical' setting because both inputs and outputs are considered 'critical'. But again, it may be difficult to pinpoint the exact start of the application and the issues described below also make it unreliable.

• Because JCL data can not be collected in addition to batch SMF data, steps that are skipped within a job will be excluded completely from the batch SMF process.

• Most likely, the GDGs referenced in batch SMF will no longer be on the system, or out of date.

• Most likely, a great number of non-GDG data sets will have been deleted.

While batch SMF will give you an idea of what has been used, it is not foolproof data for monthly, quarterly, etc., analysis.

Any batch SMF data collected should reflect at least one complete processing cycle for the application. For example, if the application runs weekly, then at least a week's worth of SMF data should be collected. If the application runs monthly, then a month's worth of SMF data will be needed. Be aware that if a sample includes more than one cycle of an application, incorrect analysis may result. Control of the sample is the user's responsibility.

Various SMF record types are used by ASAP during its SMF analysis. Before starting ASAP, you should ensure that your installation is collecting the necessary record types. The same record types are also used by RSP (Real-time Selection Process). The names of the SMF data sets that ASAP is to examine can be specified in the BRMINI member of the PARMLIB.

Chapter 5 5-2 Mainstar Software Corporation ©2006 SMF SCAN SETUP – Identifying Application Data Sets through Batch SMF SC23-6059-00



5.2 Collecting Data Using Batch SMF SCAN While it is possible to identify most of the data related to an application by examining the JCL used to run the application, the data collected by RSP JCL Capture (via the UJI exit) does not provide complete information about the application. For instance, dynamically allocated data sets can not be found in the JCL. Also, while the JCL data provides information on the disposition of data sets (OLD, NEW, SHR, etc.), it does not indicate whether the data sets were used for input or output, and does not provide good information on the actual size of the data set. In order to generate an accurate selection data set, ASAP needs to obtain this information from the system SMF records. (SMF records may also be scanned dynamically using RSP SMF capture.)

5.2.1 SMF Record Requirements ASAP uses SMF records to determine whether a data set belongs to an application, what its size is, and whether it is a critical data set required for backup. If no SMF records are available for a data set, ASAP must depend upon information gathered from RSP JCL Capture alone, which is less accurate. You should therefore try to insure that SMF records covering at least one full cycle of the application are available for ASAP to process.

The following list shows the types of SMF records that should be collected.

Record Type Description

14 INPUT/RDBACK Activity

15 OUTPUT Activity

30 End of Step/End of Job

61 ICF Define Activity

64 VSAM Component/Cluster Status

65 ICF Delete Activity

66 RENAME (alter)

IBM's IFASMFDP program or the system sort can be used to extract the desired records from the SYS1.MANx SMF data sets.

Although processing will be faster if the data sets specified for the scan contain only SMF record type 14, 15, 30, 61, 64, 65 and 66, they may contain any SMF data. ASAP will ignore any records that are not of the correct SMF type, or which can not be used due to invalid span bits or invalid record lengths.




The following JCL example shows how to use IFASMFDP to collect the SMF records required for ASAP Batch SMF Scan.

//STEP1 EXECPGM=IFASMFDP //INDD1 DD DSN=SYS1.MANX,DISP=SHR//OUTDD1 DD DSN=SMF.RECS.FOR.ASAP,DISP=SHR//SYSPRINT DD SYSOUT=* //SYSIN DD * INDD(INDD1,OPTIONS(DUMP))OUTDD(OUTDD1,TYPE(14,15,30,61,64,65))

5.2.2 Batch SMF Data Set Requirements If you have decided not to bring RSP up on your system at this time, you must allocate the following files for batch SMF use and you must ensure the ASAP LOAD library is authorized.

your.product.RSP.MSGLOGyour.product.RSP.JOBFLAT

To create the required batch SMF data sets:

1. Make sure the LOAD library has been APF authorized.

2. Edit 'your.product.JCL' member (RSPSETUP).

3. Delete the last step RSPMQBLD. This last step is not required for batch SMF.

4. Submit the job.



- - -- - -


5.2.3 Batch SMF Scan Process Overview To initiate a batch SMF Scan, a Dialog Setup screen is used, from which the SMF history files can be entered, and any filtering options reviewed. A batch job is then submitted to examine SMF record information. Data set information is saved in the ASAP Database.

Figure 5-1: Overview of the Batch SMF Scan Process

SMF Scan Even Initiation:

S M F / S C A N

Batch JOB

Current Weekly and/or Monthly

SMF Files (GDGs) SMF

History Files

Application (SMF&

Filtering Setup

Information) ASAP

Database

Merged Data Set References

SMF Scan Setup

Screen

Dialog Session

Processing: Examine SMF Records Analyze Data Set Usage (within Job Structures) Save Data Set Elements

Batch SYSPRINT

Output

5.2.4 Batch SMF Scan Procedure You may re-submit the batch SMF Scan at any time, because ASAP data set information will be merged with existing entries for the application.

STEP

1

STEP DESCRIPTION

Create the application in ASAP. For instruction, see Chapter 3, SETUP – Defining an Application to ASAP.

2 Run a Job Collection through a scheduler, or enter the jobs manually through the ISPF Edit option. For instructions, see Chapter 4, JOB COLLECT – Collecting Application Job Structure.

3 Refresh the RSP Job Table. Even though RSP is not up, the batch SMF process reads the jobflat file for a list of eligible jobs. Submit job RSPJRFSH from 'your.product.JCL'. This enables RSP to update the job table and begin collecting online SMF data for the application. Ensure the ASAP LOAD library is authorized.

4 Now you can submit Batch SMF Scan to collect SMF data. Follow the step-by-step instructions in the next topics.




5.2.5 Run Batch SMF Scan to Collect SMF Data 1. From the ASAP Main Menu choose Option 5 (SMF SCAN SETUP). Press Enter.

2. Fill in the following two underlined fields and press Enter. (NOTE: do not select any of the other options below at this time.)

SMF DSN: => YOUR.SMF.BATCH.FILE.NAME => => =>

APPLICATION: YOURAPPL (ENTER TO LOAD APPLICATION)OPTIONAL PARAMETERS: N

_ DISPLAY LIST OF PREVIOUSLY ENTERED APPLICATIONS _ DISPLAY CURRENT JOBS COLLECTED _ SCHEDULE SMF SCAN JOB

3. After you press Enter, you should see the following at the top left corner of your screen. SMF SCAN PARAMETERS FOR APPLICATION YOURAPPL ADDED

4. Now type S next to 'Schedule SMF SCAN JOB' and press Enter. (The fields on the SMF SCAN SETUP panel are described in a separate topic on page 6-10.)

SMF SCAN SETUP COMMAND: SMF SCAN PARAMETERS FOR APPLICATION YOURAPPL ADDED

SMF DSN: => XYZ.SMF.DVLP.BKUP2 => => =>

APPLICATION: OPTIONAL PARAMETERS: N

(ENTER TO LOAD APPLICATION)

_ DISPLAY LIST OF PREVIOUSLY ENTERED APPLICATIONS _ DISPLAY CURRENT JOBS COLLECTEDs SCHEDULE SMF SCAN JOB

5. The JOBCARD will be displayed. Modify if necessary, then press Enter. continued on next page




continued from previous page

6. On the panel that pops up, key S to submit one of the selections:

_ EDIT JCL Prior To Job Submit _ SUBMIT Job For Execution

Note: If you are reading in a lot of SMF tapes, you may want to select EDIT and change the JCL to use 'UNIT=AFF=SMFFILE' on the tape files so you only use one drive at a time. This parameter is not automatically included because the SMF file(s) may be on disk.

7. Ensure the job completes with return code 0 and the message at the bottom of the SYSOUT indicates that records have been added to the database.

Example: ASAPDB RECORDS ADDED/UPDATED 37

5.2.6 Run Verification to Build Selection Data Set Verification will take the data from the database, analyze it and build the ABARS selection data set.

Note: APPLEND cannot be used to build an SDS from batch SMF data. You must use Foreground or Batch Verify.

1. From the ASAP Main Menu, choose Option 2 (SELECT/CREATE APPL). Ensure your application is specified and press Enter.

2. Choose Option 4 (VERIFICATION) and press Enter.

3. Select B for batch processing (recommended for 1500 or greater records), or F for Foreground processing.

4. For the field 'SMF DATA FROM RSP OR BATCH SMF SCAN?', key S (for SMF Data) and press Enter.

If you chose B (for batch Verification processing) in Step 3 above, continue with steps 5–7, otherwise go to the topic 'View the Results of Your SMF Collection' (page 5-8).

5. The JOBCARD will be displayed. Modify if necessary, then press Enter.

6. Key S for either of the two selections below:

_ EDIT JCL Prior To Job Submit _ SUBMIT Job For Execution

7. Ensure the job completes with a return code 0.




5.2.7 View the Results of Your SMF Collection 1. To view the results of the SMF Scan, choose option 6 (STATUS), and key S next to Option

5.

2. Choose from the following sub-options:

Option 4 – Raw SMF / JCL data (not analyzed in any way).

Option 5 – Contains the analysis, based on forward recovery or rerun recovery.

Option 9 – Key B next to Option 9 to browse the ASAP Built selection data set.

The following fields are shown on the SMF SCAN SETUP panel.

Field Description

SMF DSN The names of the SMF data sets to be examined by the ASAP batch SMF Scan job. Up to four data set names may be specified. The data sets may be any valid SMF data sets, including generation data sets. All requests are supported (i.e., all generations of a GDG may be specified by entering the GDG base name without a relative generation number). SMF data should be available for a period that covers a complete application cycle. At least one data set name must be entered.

APPLICATION Enter application names in this field. ASAP will only examine SMF records with job names that match those belonging to the application, as determined during the job name collection step (Option 1 (JOB COLLECT) on the ASAP Main Menu Services panel). After entering the application, press Enter to have that application added to the application list. You may enter as many applications as you want.

OPTIONAL PARAMETERS Placing a Y in this field displays a panel that can be used to input the optional parameters: start date, end date, start time, end time, start job and end job.

DISPLAY LIST OF PREVIOUSLY ENTERED APPLICATIONS

Key S in this field to display the list of previously entered applications and their optional parameters.

DISPLAY CURRENT JOBS COLLECTED

Placing an S in this field displays the list of jobs associated with the application. These are the job names for the application that ASAP will use when analyzing SMF data.

SCHEDULE SMF SCAN JOB Placing an S in this field will cause a series of panels to be displayed that will allow ASAP to submit a batch job to perform the SMF analysis. You may also use ISPF to edit the JCL for the batch job before it is submitted.




Specifying Y for the Optional Parameters field on the SMF SCAN SETUP panel will display the SMF SCAN OPTIONAL PARAMETERS panel shown below.

SMF SCAN OPTIONAL PARAMETERS COMMAND: APPLICATION: BKTEST01

STARTING DATE: ENDING DATE:

(YYYYDDD)(YYYYDDD)

STARTING TIME: ENDING TIME:

(HH.MM)(HH.MM)

STARTING JOBS 1: 2: 3: 4: 5: 6: 7: 8:

ENDING JOBS 1: 2: 3: 4: 5: 6: 7: 8:

USE ENTER TO ADD/UPDATE; USE HELP KEY FOR HELP; END KEY TO RETURN

The fields on the SMF SCAN OPTIONAL PARAMETERS panel are described below.

Field Description

STARTING DATE The starting date (YYYYDDD) of the initial record to be examined. SMF records written before this date will not be analyzed.

STARTING TIME The starting time (HH.MM) of the initial record to be examined. You can not use starting time without using a starting date.

ENDING DATE The date (YYYYDDD) of the last SMF record to be analyzed. Records written after this date will not be used. You can not use ending time without using an ending date.

ENDING TIME The ending time (HH.MM) of the last SMF record to be analyzed.

STARTING JOBS A list of jobs that will initiate SMF analysis if any SMF record matches any of the jobs. Once a match is found, SMF records are analyzed for that job until that job's type 30 record is read.

ENDING JOBS A list of jobs that will stop SMF analysis when any record matches any of the jobs and a type 30 record is read for that job. The first job that matches is used.

The starting date and ending date parameters have precedence over the starting job and ending job parameters.

For example: If starting date and starting job are used, but the first record that matches the starting job was created before the date in the starting date parameter, then that record and any others that have dates before the starting date will not be analyzed.




The SMF SCAN APPLICATION LIST panel allows the user to view previously entered applications (see SMF SCAN SETUP panel on the previous page).

SMF SCAN APPLICATION LIST Row 1 of 2 COMMAND: SCROLL==> PAGE

USE S TO SELECT LINE AND VIEW START/END JOBS END KEY TO RETURN

START END START END APPLICATION DATE TIME DATE TIME JOBS JOBS

_ BKTEST01 N N PEREGO 2001222 02.54 Y N_

******************************* Bottom of data *****************************

To view the start jobs and/or end jobs, select an application with S. The panel below will appear if any start or end jobs were entered.

SMF SCAN START/END JOBSCOMMAND: APPLICATION: PEREGO

STARTING JOBS 1: ASPTST01 2: 3: 4: 5: 6: 7: 8:

ENDING JOBS 1: 2: 3: 4: 5: 6: 7: 8:




5.2.8 Job Submission Sequence After providing the SMF data set names and selecting the SMF Scan option on the ASAP SMF Scanning Requirements panel, two job submission panels will be displayed in sequence.

The Job Statement Verification panel is shown below.

REVIEW and/or CHANGE JOB/JCL Statements as Required:Use ENTER To Submit JOB; or PF3 To Abort

Randomize Job Name to Eight Characters ? ==> YES ( YES / NO )

//MSIS04TZ JOB (,101),'I. M. USER',CLASS=Z,REGION=0M,// NOTIFY=MSIS04T,MSGLEVEL=(1,0),MSGCLASS=X//* NEW BATCH JOB//*

The Job Submission Preferences panel is shown below.

Command ==>

Current Application: CA7MAXJB ASAP AUTOBUILD Phase: JOB COLLECTION


_ EDIT JCL Prior To Job Submit _ SUBMIT JOB For Execution









5.2.9 Reviewing the Results of the Batch SMF Scan The results may be viewed using the:

• SYSPRINT file • ASAP Dialog interface

View SYSPRINT Batch SMF Scan Results

The SYSPRINT file contains summary information about the processing of each application.

The following example is an extract of the SYSPRINT file contents.

TOTAL SMF RECORDS READ 168

DROPPED RECORDS UNWANTED RECTYPE 2

RECORDS DROPPED PRIOR COLLECT START

SMF TYPE 30 RECORDS DROPPED 30

RECORDS DROPPED NO JOB/APP MATCH 38

RECORDS DROPPED MISSING/BAD DATA 3

RECORDS DROPPED CACHE MATCH 67

RECORDS DROPPED DISCARD FILTER

ASAPDB RECORDS ADDED/UPDATED 28




View ASAP Dialog Interface SMF Scan Results

To review the data sets collected using the ASAP Dialog interface, use option 6 (STATUS) from the Application AutoBuild Options menu. From the Display Selections pop-up menu, select Display Data Set Detail Records (JCL, RSP, Batch SMF).

The Combined Data Set List will be displayed.

DATA SET DETAIL RECORDS ROW 34 TO 63 OF 63 CMD: SCROLL: CSR

MORE > APPL: APPL0001 CURRENT CYCLES:RSP 49 JCL 6 SMF 10

REC CYCLE C JCL JCL JCL CM DATA SET NAME TYP *=CURRENT C SDP NDP ADP __ ____________________________________________ ___ __________ _ ___ ___ ___

XYZ.A032.DATA SMF 10 * *** *** *** XYZ.A033.DATA SMF 10 * *** *** *** XYZ.A034.DATA SMF 10 * *** *** *** XYZ.A035.DATA SMF 10 * *** *** *** XYZ.A036.DATA SMF 10 * *** *** ***

Rows indicating a REC TYP of 'SMF' are records created from Batch SMF Scan. Each time SMF Scan is run, the SMF cycle number increments. If more than one cycle is retained (see Setup options), the current cycle is indicated by both a cycle number and an asterisk in the CC (current cycle) column.

To view all the data collected for a data set, either scroll right for additional fields or key an S in the CM (command) column.




Chapter 6 6 VERIFICATION – Creating the Selection Data Set

After ASAP has determined which jobs and data sets are associated with an application, the information is stored in the ASAP Database. Now the 'criticality' of the identified data sets needs to be accessed and the selection data set created. Criticality is based on settings for either Rerun Recovery or Forward Recovery, and on filters that may have been added. Either ASAP's APPLEND program or ASAP's VERIFICATION facility are used to determine the 'critical' selection data set entries for the application and create the selection data set. An application's selection data set determines which data sets will be backed up.

Contents:

• Overview of the Verification Process – page 6-2

• About Selection Data Sets and Output Formats – page 6-3

• Invoking Selection Data Set Verification – page 6-5

• Scheduling Application Backups – page 6-8

• Adding Data Sets to the Application Selection Data Set During Verification – page 6-8

• Verification Output Selection Data Set Formats – page 6-9

• Reviewing the Results of Verification – page 6-13

• Verification Global Options in BRMINI Member – page 6-14

Mainstar Software Corporation ©2006 6-1 Chapter 6 SC23-6059-00 VERIFICATION – Creating the Selection Data Set



6.1 Overview of the Verification Process A selection data set can be built:

• From ISPF by selecting 'VERIFICATION'. Verification is used when: – Batch SMF Scan has been used to gather data. – Verification can also be used to re-evaluate data. For example, let's say you run an

APPLEND. Now you want to create some filters or change some settings but you want to know the effects of your changes. Simply make your changes and run VERIFICATION to see the results. Verification uses the last cycle of data to rebuild your selection data set.

• By running an RSP 'APPLEND' step. The APPLEND program is normally used with the Real-time Selection Process (RSP) started task.

• By invoking a batch job.

Regardless of how the process is invoked, the following functions are accomplished:

• Data set detail records (DSDs), created from RSP JCL Capture, RSP SMF Capture and Batch SMF Scan, are combined into a single record for each data set.

• Data sets are evaluated for criticality. This step also inserts arbitrary data sets (external filters).

• The selection data set is created.

The selection data set entries are built from the DSD application entries in the ASAP Database. These entries may have been generated/added to the ASAP Database by:

• Data collected by RSP SMF Capture. • Data collected by RSP JCL Capture. • Batch SMF Scan. • 'EXT' (external) type filters. • Custom programs that add data set entries to the ASAP Database.

RSP JCL and SMF data collection (by either/both RSP SMF Capture or optional batch SMF) require a list of job names defining the application. Therefore, if RSP JCL or SMF collection is to be employed, the application job list must first be built (job collection).

External filters (INCL_EXTDSN, ALLOC_EXTDSN, and ACCOMP_EXTDSN) can be used to enter data set names in the database that JCL or SMF data collection may not have captured. See Chapter 9, FILTERS – Using Filters and Controls, for more information on filters.

Whether all of the listed sources (from previous page) of data set names are employed depends on the application. RSP JCL Capture (UJI exit) is not necessary if the preference is to use only data set names captured by RSP SMF Capture (U83 exit). Batch SMF Scan alone may be used for capturing runs, such as year-end cycles, before RSP has a chance to 'watch' the application run. An application could also be comprised of only data set names specified with external filters.

The

Selection Data Set Built in Error

iCheck the

Note: ABARS will reject a selection data set that does not have at least one INCLUDE. selection data set build program will produce the error:

This could be caused by all data sets be ng filtered out (Excluded), or all data sets being assigned to a category other than INCLUDE (i.e., ALLOCATE or ACCOMPANY). comments at the end of the selection data set. The INCL_EXTDSN filter could be used to force an INCLUDE for a dummy data set.

Chapter 6 6-2 Mainstar Software Corporation ©2006 VERIFICATION – Creating the Selection Data Set SC23-6059-00



6.2 About Selection Data Sets and Output Formats Each application has a unique selection data set file. The selection data set is defined at application SETUP time with an output format compatible with the backup product used (i.e., ABARS, FDR, DFDSS, Brightstor CA-Disk etc.). This selection data set is used by ASAP Verification to contain the most recent critical data set entries to be backed up.

Note: PDSs and PDSEs are not a good choice for selection data sets used by ASAP because ASAP updates the selection data set and due to the nature of PDSs and PDSEs, two or more members can't be written to at the same time. Sequential files are recommended.

6.2.1 Selection Data Set Contents – ABARS For ABARS, an aggregate's selection data set is simply an 80-character fixed-length file that indicates which data sets are to be processed during ABARS aggregate backup. The aggregate's selection data set provides the selection criteria to be used by ABACKUP.

The selection statements that can be contained in an aggregate's selection data set as criteria for how data sets are processed during ABACKUP are described below.

Selection Criteria Description

INCLUDE Specifies data sets which are to be included during any backup processing. These are part of the critical data set list and are placed in the selection data set. A selection data set must contain at least one INCLUDE.

EXCLUDE Specifies data sets that are to be excluded from any backup processing. These are maintained in the ASAP Database for the application but not placed in the selection data set.

ACCOMPANY Specifies user tape data sets which are to be considered as included in the application backup, and which will be cataloged at recovery time. Used by ABARS only.

ALLOCATE Specifies DASD only data sets which are to be included in the backup critical list, but do not contain data. At recovery time, these data sets will be created, but no data is restored into them. Used by ABARS only.

selection criteria

Note: The use of ACCOMPANY and ALLOCATE selection statements is unique to the ABARS backup platform. If not supported by other backup products, data sets assigned with these

may not be placed in the selection data set list.

ASAP uses all the information available to it to determine, for each data set, whether the data set should be placed in the INCLUDE, EXCLUDE, ALLOCATE, or ACCOMPANY lists. ASAP knows the complete name of each data set, so data set name masks are not used in these lists. The entire data set name for each data set is placed in the INCLUDE, EXCLUDE, ALLOCATE, or ACCOMPANY lists.

The ACCOMPANYEXCLUDE and ALLOCATEEXCLUDE lists are empty because no data set name masking is used. An example of an aggregate's ABARS selection data set created by ASAP is shown under Selection Data Set Output Formats.

Defining SMS Aggregate Groups for ABARS Selection Data Sets

In order for ABARS to use a selection data set, the name of the data set must be specified when the SMS aggregate group is defined. The ISMF application is used to define or update SMS aggregate group definitions.




6.2.2 Selection Data Set Contents – Non-ABARS For non-ABARS formats (DFDSS, FDR, DMS (Brightstor CA-Disk), etc.), the contents of the entries would be unique to the backup product to be used. ASAP creates these entries in the proper format based upon the selection data format specified during application setup.

Note: ASAP identifies 'critical' data for an application. If ASAP identifies data that at some point during the batch execution is either migrated or archived, non-ABARS formats will cause the backup to fail because they can't back up migrated or archived data. If you are not using ABARS, you must ensure filters are set up to exclude migrated or archived data.

6.2.3 Data Set Types and Output Selection Formats ASAP supports six output selection formats for backup purposes. The format type is specified or changed using application SETUP (Option 0) from the Application AutoBuild Options menu or from the Dialog Verification Setup panel before invoking ASAP Verification processing.

ASAP Verification separates an application's selection data set entries into three lists, based on their data set type.

• INCLUDES – For primary DASD data sets. • ALLOCATES – For primary DASD data set catalog information only (data sets with no data). • ACCOMPANY – For user tape data sets.

Not all data set types are supported by all output selection formats. The following table summarizes the data set entries that will be automatically constructed based upon the output format specified for a selection data set.

Output Selection Format Supported Data Set Types

DFSMShsm (ABARS) Primary DASD, ML1, and ML2. Allocate and User Tapes as Accompanies are all supported.

DMS/OS (CA-Disk) Only primary DASD data sets are supported. User tape data sets or Allocates are not supported.

DFSMSdss (DSS) Only primary DASD data set are supported. Any Allocate type entries will be processed and placed in the INCLUDE list for full backup.

FDR Both primary DASD data sets and Allocate entries are supported. Any user tape data set entries will be eliminated.

LIST No distinct separation is made for data set entries. All data sets are listed using the same format.




6.3 Invoking Selection Data Set Verification Select Option 4 (VERIFICATION) from the ASAP Application AutoBuild Options menu to begin the process of creating the aggregate's selection data set.

The Selection Data Set Build panel will be displayed. On this panel, you may choose to build the selection data set in the foreground or have a batch job submitted. If this is the first time a Verification has been run for the application, use the foreground option.

Note: You must build a Selection Data Set for an application at least once using the APPLEND process before building it with the Foreground or Batch Verify processes.

Figure 6-1: Selection Data Set Build Panel

SELECTION DATA SET BUILD CMD:

CHOOSE PROCESSING OPTION

F FOREGROUND B BATCH

6.3.1 Building the Selection Data Set in Foreground If Foreground is selected, then the Selection Data Set Build Foreground Options panel will be displayed.

Figure 6-2: Selection Data Set Build Foreground Options Panel

SELECTION DATA SET BUILD FOREGROUND OPTIONS CMD: APPLICATION ==> TESTZ

SYSID ==> DVLP RE-EVALUATE: ENABLED FILTERING: ENABLED USER TAPES: AS INCLUDES

USE MAX-INC SIZE: DISABLED MAX-INC SIZE: NONE

FINAL CATALOG CHECK: ENABLED BASE GDG(S):

SELECT DSN FORMAT: NOT INCLUDED ABARS

SMF DATA FROM RSP OR BATCH SMF SCAN? => R (R=RSP,S=SMF SCAN)

CHANGE APPLICATION SETUP OPTIONS? => N (Y/N)

SELECTION DATA SET NAME FOR THIS BUILD => XYZ.AMPASAP.TESTK.SELECT

VERIFY SELECTION DATA SET NAME IN DATABASE => XYZ.AMPASAP.TESTK.SELECT

Press Enter to continue selection data set evaluation.




The following fields are shown on the Selection Data Set Build Foreground Options panel.

Field Description

RE-EVALUATE Indicates whether ASAP should re-evaluate each data set entry within the application for INCLUDE -vs.- EXCLUDE status. If ENABLED; the data set entry will be re-evaluated to determine its status regardless of previous status. If DISABLED; the data set entry will not be re-evaluated.

FILTERING If ENABLED; all data set entries will be matched against the filtering criteria previously set up. The filter evaluation occurs before any other options. No other evaluation is done on a data set excluded because of filtering. If DISABLED; no filtering criteria are checked.

USER TAPES Only used for ABARS output selection data set formats. If set as ACCOMPANY; each user tape data set entry will be treated as an ACCOMPANY. The catalog entry is copied, but the file itself is not backed up. The tape must be physically moved. If set as INCLUDE; the user tape data set(s) will be placed in the INCLUDE list, and therefore backed up on an output tape.

Use MAX-INC SIZE

MAX-INC SIZE: nnn (MEGS)

Used only for ABARS output selection data set formats. If ENABLED; the evaluation software will determine whether a user tape data set entry should be placed in either the INCLUDE or ACCOMPANY list based upon its current size. The size value used as the compare value (nnnnn) can be changed.

FINAL CATALOG CHECK If ENABLED; will check each data set entry in the catalog before putting it in the selection data set for the application.

BASE GDG(S) If ENABLED; the evaluation software will place in the INCLUDE list those normally excluded base GDG entries. When enabled, this option assures that all base GDG definitions will be on the backup tape set and available during recovery.

SELECTION DSN FORMAT (ABARS, DMS, DSS, FDR, DMS, or LIST) previously chosen during Option 0 (SETUP) for this application.

SMF DATA FROM RSP or BATCH Select VERIFICATION for either: SMF SCAN R = RSP data.

S = Batch SMF data.

CHANGE APPLICATION SETUP The Selection Data Set Build Foreground Options panel allows you OPTIONS to change any application setup options before building the

selection data set. Enter Y to put you into the application Option 0 (SETUP).

SELECTION DATA SET NAME If you enter a valid name in this field, the selection data set will be FOR THIS BUILD built using this name, otherwise the RSP/BATCH name defined in

Option 0 (SETUP) will be used. The change is only in effect for this one execution.

VERIFY SELECTION Shows the selection data set name defined to ASAP. DATA SET NAME IN DATABASE




If you entered a Y in the CHANGE APPLICATION SETUP OPTIONS field, the Application SETUP Options panel will be displayed. This is the same panel that is displayed for Option 0 (SETUP) from the ASAP Application AutoBuild Options menu. Make any filtering or verification changes on this panel. After you press Enter or End (PF3) processing will continue.

6.3.2 Building the Selection Data Set in Batch If Batch is selected on the Selection Data Set Build panel, then the Selection Data Set Build Batch Options panel will be displayed.

SELECTION DATA SET BUILD BATCH OPTIONS CMD: APPLICATION ==> BK1

SYSID ==> P390 RE-EVALUATE: ENABLED FILTERING: ENABLED USER TAPES: AS ACCOMPANY

USE MAX-INC SIZE: DISABLED MAX-INC SIZE: NONE

FINAL CATALOG CHECK: ENABLED BASE GDG(S):

SELECT DSN FORMAT: NOT INCLUDED ABARS

SMF DATA FROM RSP OR BATCH SMF SCAN? => R (R=RSP, S=SMF SCAN)

CHANGE SELECTION DATA SET OPTIONS? => N (Y/N)

RSP/BATCH SELECTION DATA SET NAME=> BK.SDS.PO(BK1)

This Selection Data Set Build Batch Options panel allows you to change any application configuration settings before submitting a job that builds the selection data set. The options on the panel are identical to the foreground options. To change options, put a Y in the CHANGE SELECTION DATA SET OPTIONS field.

There is a difference in the way you change a selection data set name. In batch processing, you cannot change the selection data set name on the option panel. However, if you put a Y in the CHANGE SELECTION DATA SET OPTIONS field, you can change the selection data set names in the database when the Application SETUP Options panel is displayed.

Before the job is submitted, a panel appears that lets you change the Job Card, and you will have the opportunity to do a final edit of the batch JCL.




6.4 Scheduling Application Backups Once ASAP Verification is complete and the selection data set has been built, the application is ready to be backed up. The selection data set can be used as the input to the backup, or preprocessed by the installation before the backup.

The selection data set will always be in the correct output format based upon the current output option for the application.

For example, if the ABARS format is the current output option for the application, you can now use Backup & Recovery Manager Suite to schedule the ABACKUP through DFSMShsm.

For non-ABARS formats, the installation must create and schedule the backup, using any data mover utility (DSS, FDR, etc.) for the selection data set format created.

6.5 Adding Data Sets to the Application Selection Data Set During Verification You may add additional data set entries to your application selection data set not seen by JCL or SMF capture. (Example: tool box data sets, etc.) This can be accomplished by using the INCL_EXTDSN, the ACCOMP_EXTDSN and ALLOC_EXTDSN filters. See Chapter 9, FILTERS – Using Filters and Controls for more information. If these filters have been added, Verification will evaluate them as well.

Data set entries that are added via the above process will be evaluated the same as all other data set entries. The one exception is that these data set entries are not affected by the re-evaluate option.

The


i )Check the


This could be caused by all data sets be ng filtered out (excluded , or all data sets being assigned to a category other than INCLUDE (i.e., ALLOCATE or ACCOMPANY). comments at the end of the selection data set. The INCL_EXTDSN filter could be used to force an INCLUDE for a dummy data set.




6.6 Verification Output Selection Data Set Formats ASAP supports five selection data set output formats for backup purposes. The output format type can be indicated or changed using SETUP (Option 0) from the Application AutoBuild Options menu, or from the Dialog Verification Setup panel before invoking ASAP Verification processing.

The supported output formats are:

Format Description

ABARS Uses the standard INCLUDE, ALLOCATE and/or ACCOMPANY type entries. The ABARS format is the default.

DMS/OS (CA-Disk) Uses primary data set entries.

DFSMSdss Uses the logical dump data set format.

FDR Uses primary and allocate type data set entries.

LIST Standard simple LIST.

6.6.1 Output Formats & Supported Data Set Types ASAP Verification separates an application's selection data set entries into three lists, based on their data set type.

• INCLUDES – For primary DASD data sets. • ALLOCATES – For primary DASD data set catalog information only (data sets with no data). • ACCOMPANY – For user tape data sets.

Not all data set types are supported by all output selection formats. The following table summarizes the data set entries that will be automatically constructed based upon the output format specified for a selection data set.

Output Selection Format Supported Data Set Types

DFSMShsm (ABARS) Primary DASD, ML1, and ML2. ALLOCATE and User Tapes as ACCOMPANY are all supported.

DMS/OS (CA-Disk) Only primary DASD data sets are supported. User tape data sets or ALLOCATE is not supported.

DFSMSdss (DSS) Only primary DASD data sets are supported. Any ALLOCATE type entries will be processed and placed in the INCLUDE list for full backup.

FDR Both primary DASD data sets and ALLOCATE entries are both supported. Any user tape data set entries will be eliminated.

LIST No distinct separation is made for data set entries. All data sets are listed using the same format.




Output Format Examples

Examples of the ABARS and DSS output formats are provided below.

Figure 6-3: ABARS Format

/* *//* LAST UPDATE: USER1 01/10/2004 09:34:45 *//* SELECTION DATA SET UPDATE VIA ASAP(C) FACILITY: *//* COPYRIGHT 1997-2004 MAINSTAR SOFTWARE CORPORATION *//* *//* APPL NAME: CA7 *//* DESC: CA7 APPLICATION CREATED ON 01/10/2004 *//* *//* DSN FORMAT: ABARS *//* SYSID: **** *//* EXEC MODE: DIALOG (OPTION-4) *//* RE-EVALUATE DATASET ENTRIES: YES *//* DATASETS EVALUATED FROM: SMF AND JCL *//* TAPE DATASETS AS ACCOMPANY: NO *//* USE SIZE FOR INC/ACC TAPES: NO *//* CTLG CHK: ENABLED *//* PROCESS FILTERS: YES *//* NAME TYPE FOR GDSES: ABSOLUTE *//* GDSES EVALUATED FROM: SMF AND JCL *//* EXPAND BASE GDG REFERENCE: NO *//* ADD MISSING GDSES: MIN FOR FWD RECOVRY *//* CATEGORY FOR MISSING GDSES: INCLUDE *//* CATEGORY FOR NEW GDSES: INCLUDE *//* VDR FILTERS: ACTIVE=NO */

INCLUDE(USER1.ABARSMGR.JCLPROF /*DASD(SMS004) 2001.325*/ +AMP.ASAPDB /*DASD(TSO002) 2001.325*/ +CA7.TESTGDG.G0004V00 /*DASD(SMS003) *********/ +CA7.TESTGDG.G0005V00 /*DASD(SMS003) *********/ +

)/*

ALLOCATE( */

CA7.ZOUT.LIST /*DASD(TSO002) */ +)

/* ACCOMPANY(

*/

CA7.ZTAPE /*TAPE(021212) 2001.267*/ +)

/* EXCLUDED DUE TO NORMAL EVALUATION: *//* *//* DSN=USER1.LEAVE.THIS.OUT DASD */




Figure 6-4: DFSMSdss (DSS) Format

/* *//* LAST UPDATE: USER1 01/10/2004 09:34:45 *//* SELECTION DATA SET UPDATE VIA ASAP(C) FACILITY: *//* COPYRIGHT 1997-2004 MAINSTAR SOFTWARE CORPORATION */

/* APPL Name:BELLALT *//* Desc:APPLICATION CREATED BY:MSIS04T ON 01/10/04 *//* *//* DSN FORMAT: DSS *//* SYSID: **** *//* EXEC MODE: DIALOG (OPTION-4) *//* RE-EVALUATE DATASET ENTRIES: YES *//* DATASETS EVALUATED FROM: SMF AND JCL *//* TAPE DATASETS AS ACCOMPANY: NO *//* USE SIZE FOR INC/ACC TAPES: NO *//* CTLG CHK: ENABLED *//* PROCESS FILTERS: YES *//* NAME TYPE FOR GDSES: ABSOLUTE *//* GDSES EVALUATED FROM: SMF AND JCL *//* EXPAND BASE GDG REFERENCE: NO *//* ADD MISSING GDSES: MIN FOR FWD RECOVRY *//* CATEGORY FOR MISSING GDSES: INCLUDE *//* CATEGORY FOR NEW GDSES: INCLUDE *//* */

DUMP DATA SET(INCLUDE( -PBACR.CR932M.PTP1006 /* DASD (A4PRAB) */ -PCRAB.AB3906M.REPORT /* DASD (A4PRAB) */ +PCRAB.AB3907M.REPORT /* DASD (A4PRAE) */ +PCRAB.AB3908M.REPORT /* DASD (A4PRAE) */ +SUFYP.SEND.BFTCNTL /* DASD (A4SUAL) */ -SUOPP.PROD.DMSSLLB /* DASD (A4SUAY) */ -SUOPP.PROD.LLBWK1 /* DASD (A4SUBH) */ -SUOPP.PROD.PROC /* DASD (S1SYP3) */ -

)) -INDYNAM((......)) -OUTDD(TAPE)




6.6.2 Guidelines for ABARS Data Set Output Formats ASAP supports ABARS as a default for the final output format of the application's selection data set. Unless you change the default, ABARS will be used.

Because this format require that an ABARS aggregate be defined, the information in the following two topics should be reviewed and considered before using Verification.

For ABARS Formats

During application setup (Option 0, SETUP), you can associate the ASAP application to an existing ABARS aggregate definition contained in your active SMS configuration.

When the application is finally Verified to create the output selection data set critical list, ASAP will use the following look-up process:

1. ASAP will first attempt to locate the associated aggregate name in your SMS configuration.

2. If the associated aggregate name is found, then its defined selection data set name (and/or member) will be used as the final selection container data set.

3. If the associated aggregate name does not currently exist, then ASAP will construct a default selection data set name. This default name can then be used when the final aggregate entry is constructed via the ISMF panel service.

For ABARS output formats, ASAP does not require that the final aggregate name exist when Verification is used. However, you must define the aggregate to SMS before any ABARS ABACKUP scheduling.

In this way, you can create future ABARS applications using ASAP, and then define the aggregate definition at a later time. If you change the output format of the application's selection data set (using Option 0, SETUP), you must re-verify your ASAP application to assure the correct format and selection data set name will be assigned.




6.7 Reviewing the Results of Verification To review the results of the most recent ASAP Verification of the application's selection data set contents, any one of the following methods can be used in ASAP Dialog mode:

Method 1: Use application STATUS (option 6) from the Application AutoBuild Options menu.

Method 2: Browse the selection data set.

6.7.1 Using STATUS (Option 6) from the Application AutoBuild Options Menu Select STATUS (option 6) from the Application AutoBuild Options menu. The Display Selections pop-up menu will be displayed for the current application.

Figure 6-5: ASAP Application Display Selections

ASAP APPLICATION Display Selections => TESTZ

Use S For Selections; Use PF1 For HELP

_ 1) N/A _ 2) Display Current JOB List _ 3) Display Current JOB Anchor Chains _ 4) Display Data Set Detail Records (JCL,RSP,Batch SMF) _ 5) Display Current JCL/SMF DSN Entries _ 6) Display Current JCL/SMF DSN Entries with URD Information _ 8) Display Summary of Last VERIFY Selection Data Set _ 9) Browse Selection Data Set Contents (Choose A,B or C )

A)VERIFY(One time build):N/A

B)VERIFY(Database):XYZ.AMPASAP.TESTK.SELECT

C)RSP:XYZ.AMPASAP.TESTK.SELECT

_ 10) N/A_ 11) N/A

To display information for the last Verification, select the following options:

9) Browse Selection Data Set Contents (Choose A, B or C)

then select

B) VERIFY (Database).




The Browse Selection Data Set option will invoke an ISPF Browse to display the current selection data set.

An example is shown below.

Figure 6-6: Browse Selection Data Set

BROWSE AMP.AMPASAP.CA7.SDS Line 00000000 Col 001 080 Command ===> Scroll ===> CSR ******************************* Top of Data ********************************/* *//* LAST UPDATE: USER1 01/10/2004 09:34:45 *//* SELECTION DATA SET UPDATE VIA ASAP(C) FACILITY: *//* COPYRIGHT 2006 MAINSTAR SOFTWARE CORPORATION *//* *//* APPL NAME: CA7 *//* DESC: CA7 APPLICATION CREATED ON 01/10/2004 *//* *//* DSN FORMAT: ABARS *//* SYSID: **** *//* EXEC MODE: DIALOG (OPTION-4) *//* RE-EVALUATE DATASET ENTRIES: YES *//* DATASETS EVALUATED FROM: SMF AND JCL *//* TAPE DATASETS AS ACCOMPANY: NO *//* USE SIZE FOR INC/ACC TAPES: NO *//* CTLG CHK: ENABLED *//* PROCESS FILTERS: YES *//* NAME TYPE FOR GDSES: ABSOLUTE *//* GDSES EVALUATED FROM: SMF AND JCL *//* EXPAND BASE GDG REFERENCE: NO *//* ADD MISSING GDSES: MIN FOR FWD RECOVRY *//* CATEGORY FOR MISSING GDSES: INCLUDE *//* CATEGORY FOR NEW GDSES: INCLUDE *//* VDR FILTERS: ACTIVE=NO *//* */


)/* */

ALLOCATE(CA7.ZOUT.LIST /*DASD(TSO002) */ +

)

6.8 Verification Global Options in BRMINI Member Verification processing is in part controlled by global options and settings contained in the ASAP BRMINI PARMLIB member. You can use values in the BRMINI member to force or alter Verification options for any/all applications currently defined. For more information about these keywords and how to code them, see Appendix B, BRMINI Configuration Values of the Backup & Recovery Manager Suite Installation & Maintenance Guide.




Chapter 7 7 Real-time Selection Process (RSP)

The Real-time Selection Process (RSP) captures and analyzes SMF and/or JCL data for applications defined to ASAP as they are executing, and updates the ASAP Database with any changes found for the application. RSP will then automatically reconstruct the application's (aggregate's) selection data set with the most current critical data set entries through the use of an end-of-application step (APPLEND).

Contents:

• Real-time Selection Process (RSP) Overview – page 7-2

• Performance & Usage Notes – page 7-4

• Preparing an Application for RSP Data Collection – page 7-5

• System Configuration Modes and RSP Tasks – page 7-6

• RSP Job Reference Table: Use of RSPBLDJB & RSPJRFSH –page 7-6

• The APPLEND Program (End-of-Application) – page 7-7

• Summary of RSP Job – page 7-10

• RSP Message Log – page 7-11

• RSP Monitor – page 7-12

• RSPSMFTK (RSP) Operator Commands – page 7-18

• Real-time Selection Process – Operational Considerations – page 7-23

• What to Do If the Overflow Data Set Fills Up – B37 – page 7-24

• Increasing the RSP Buffer Size – page 7-25

Mainstar Software Corporation ©2006 7-1 Chapter 7 SC23-6059-00 Real-time Selection Process (RSP)



7.1 Real-time Selection Process (RSP) Overview The Real-time Selection Process (RSP) dynamically collects and analyzes SMF and/or JCL data for applications defined to ASAP as they are executing in real-time mode, and continuously updates/saves them to the ASAP Database, keeping it current with the collected application critical data set information.

When the application completes, the APPLEND step will update and rebuild the application's selection data set entries. This allows the applications defined to ASAP to be backed up at any time subsequent to processing completion.

RSP consists of these collection mechanisms to detect and save changes to an application's data sets:

• RSP SMF Capture – the dynamic capture of SMF records using an IEFU83 exit. • RSP JCL Capture – the dynamic capture of interpreted JCL using an IEFUJI exit. • A database update task on each image from which you wish to collect data.

7.1.1 Choosing How to Set Up RSP for an Application For each application, you may choose:

• How many cycles of RSP data you want to save. Records are stored by 'cycle'. The APPLEND step denotes the end of a cycle.

• How many cycles of RSP data you want to include in a selection data set. • Which SMF and/or JCL records you want to capture.

RSP SMF Capture collects SMF record types 14, 15, 61, 64, 65, and 66. These records supply data to RSP for data sets that are opened and closed, deleted, renamed, and allocated.

RSP SMF Capture captures the first reference of a data set. It does not matter if the reference is an open or a close (or a URD – updated, renamed, or deleted). RSP SMF capture will not collect SMF data for data sets that have no references before APPLEND is executed. The classic case is CICS. If it starts before RSP is started and if the data sets are not closed before APPLEND is executed, RSP will not know they existed.

To set up RSP options for an application, use the Application SETUP Options panel. See Chapter 3, SETUP – Defining an Application to ASAP. In addition, Chapter 1, ASAP Overview, provides step-by-step setup options.

Chapter 7 7-2 Mainstar Software Corporation ©2006 Real-time Selection Process (RSP) SC23-6059-00



7.1.2 Collection of SMF and JCL Records Using RSP, each job submitted to the system is scanned by the IEFUJI exit to identify each data set in the JCL. As jobs execute, system SMF records are created for each data set that records whether a data set has been read, updated, renamed or deleted. RSP intercepts each SMF record before the record is written to the system SMF MANX and MANY data sets. These JCL and SMF records are written to the ASAP Database as 'raw' records, or data set detail records (DSD) and can be found by bringing up ASAP through the ISPF interface, selecting the given ASAP application, selecting option 6 (STATUS) then option 4 (Display Data Set Detail Records (JCL, RSP, Batch SMF)).

7.1.3 Processing Captured SMF and JCL Records The records intercepted by the U83 and UJI exits are stored temporarily in buffers created in a dataspace. The database update task unloads the dataspace buffers and updates the ASAP Database. The dataspace buffers are not unloaded immediately. The database update task waits until the number of loaded buffers reaches a threshold that will maximize I/O efficiency.

If the database update task gets behind because of the volume of data being processed and fills most of the buffers in the dataspace, the task will enlarge the dataspace. The dataspace can be enlarged to twice its initial size. If still more room is required, the export task will unload the dataspace to a sequential data set, the overflow file. When buffers are available again, the import task will reload the dataspace buffers. The export task will also unload the dataspace if the database update task is down and the buffers are full. The unloaded records will not be reloaded until the database update task is processing normally again.

7.1.4 Viewing Captured SMF and JCL Records To view the records created for an application as the application runs, select Option 6 (STATUS) from the Application AutoBuild Options menu, then Option 4 (Display Data Set Detail Records). If no records are displayed, it is because they are still resident in the dataspace buffers, or overflow file. A buffer flush can be requested by using the RSP monitor via RSP Commands (Option 5) of the RSP Monitor. See the topic 'RSP Monitor' (page 7-12).




7.2 Performance & Usage Notes

7.2.1 Reducing Data to Be Processed by RSP 1. Use Discard retention filters instead of Exclude evaluation filters. This will eliminate records

at RSP collection time with the result being fewer records for APPLEND to process.

2. Be careful when using data sets collected via the RSP JCL Capture UJI exit. Data sets may be included in the APPLEND processing that are not used during execution. An easy way to see this is to display the detail records.

(SELECT/CREATE APPL) from the ASAP Main Menu (STATUS) from the menu, then

To use the STATUS option, select Option 2, specify an application, select Option 6 Application AutoBuild Options

Display Data Set Detail from the pop-up menu.

If a data set is captured by both the RSP SMF Capture U83 exit and the RSP JCL Capture UJI exit, the two entries will be together. Hence, it is easy to see records from the UJI exits that were not used during the last execution.

7.2.2 Avoiding Trouble with the RSP Cycles APPLEND causes the RSP cycle to be incremented unless the parameters passed to APPLEND are invalid or the CYCLENOINC parameter is passed. If errors occur building the selection data set, the cycle will have been bumped.

This is important to understand: If the selection data set is to be rebuilt, do not rerun APPLEND unless CYCLENOINC is specified. Another way to do this is to build the selection data set from the ISPF Verification panel in either foreground or background. If APPLEND is rerun without specifying CYCLENOINC, the cycle will increment and you will get either nothing or data set records from the current execution of the application.

It is helpful to set up JCL ahead of time to use if APPLEND has a failure. If the normal APPLEND JCL is a job containing APPLEND followed by the backup, you might set up a 'rerun' PROC that is a batch verification followed by the backup. Because a failing APPLEND will probably take some work to figure and solve the problem, you might as well rebuild the selection data set from the panels and then launch the backup. Again, don't rerun the backup job if it also contains the APPLEND step.

You might want to set the RSP retain cycles to more than 1 even though you set the Cycles to be Included in the selection data set to only 1. This way if you accidentally run APPLEND twice, resulting in the current cycle containing nothing, you can then set the cycles to be included in the selection data set to 2 and pick up the correct data.

Currently, if APPLEND is run again in error, and there are new records in the database because the application is currently running, there is no way to build the selection data set from just the '-1 generation' of RSP cycles.

It may be handy to keep multiple RSP cycles around for comparing cycle executions but don't overdo it without considering the room needed in the database.




7.3 Preparing an Application for RSP Data Collection Follow these steps to prepare an application for RSP:

STEP DESCRIPTION

Create/Define the application.1 Select Option 2 (SELECT/CREATE APPL) from the ASAP Main Menu, to create the application name. Select Option 0 (SETUP) from the Application AutoBuild Options menu, to define the application to ASAP by assigning special requirements or options, (e.g., backup type format, filtering patterns, SMF and/or JCL data capture, etc).

2 Job Collect – Collect the Job Entries and Structures. Use Option 1 (JOB COLLECTION) from the Application AutoBuild Options menu, to define and collect the initial job elements and job structures required for the application, either from a supported job scheduling product and/or manually supplied from the ISPD dialog.

Note: You can re-collect and merge new job element information into the application at any time. RSP will automatically detect the new jobs and job structures.

3 Create the application's selection data set – optional. (Initial selection data set build only.) Use Option 4 (VERIFICATION) from the Application AutoBuild Options menu to create the application's selection data set you defined in Option 0 (SETUP). The selection data set name and type must be defined before using RSP for the application. This process only needs to be completed the first time. Optionally, you can create the selection data set without a Verification.

Note: During Verification, make sure you select any/all options desired. These same options will be used during the RSP process of reconstructing the application selection data set entries. If desired, you can change any options for an application at a later time, which will then be used the next time its selection data set is reconstructed.

Complete either step 4A or 4B, then continue.

4A If the RSP started task has not yet been started for the first time: RSPBLDJB must be run once before RSP is started for the first time. 4A. Run RSPBLDJB to perform the database extract and create the initial Job Flat file. Then, issue start command RSPSMFTK to start RSP.

Note: These actions are part of the RSP install procedure in the BRM Suite: Installation & Maintenance Guide and may have been performed at the time of the initial product install.

4B If the RSP started task has already been started for the first time: 4B. Run RSPJRFSH to rebuild the Job Flat file and refresh the Job Reference Table.

5 Run the application.




STEP DESCRIPTION

7 Define the Application-End (APPLEND) step or job. Determine the last or end job in the application. Insert a job or job step to execute the APPLEND program (provided by ASAP) to notify RSP of the end-of-application point, or an abnormal exit termination. The execution of the APPLEND program can be either an additional job step or a separately scheduled job. For more information about coding APPLEND, see the topic 'The APPLEND Program (End-of-Application)' (page 7-7).

7.4 System Configuration Modes and RSP Tasks The RSP facility can collect data for applications defined to ASAP in either single image or multi-image (SYSPLEX) modes. This capability allows installations to schedule and execute applications, or unique application jobs, on any processor image and still maintain continuous collection of application file usage.

The main control program RSPSMFTK controls the RSP tasks. There is one RSPSMFTK task for each image. The RSPSMFTK task is started with a job name of RSP. The RSP operator commands are documented in the topic 'RSPSMFTK (RSP) Operator Commands' (page 7-18).

7.5 RSP Job Reference Table: Use of RSPBLDJB & RSPJRFSH In each image, RSP builds an internal dataspace table (Job Reference Table) containing the job names defined to each application. During application processing, the RSP IEFU83 exit captures SMF record types 14, 15, 61, 64, 65 and 66. The job name in the SMF records is compared to the internal Job Reference Table, looking for a job name match defined for an application in the table. If the job name is found in the Job Reference Table, the SMF record is saved in the ASAP Database for the appropriate application(s).

The Job Reference Tables are created from a sequential file, called the job flat file, which is extracted from the ASAP Database. RSPBLDJB is the distributed JCL member used to perform the database extract and create the initial job flat file. RSPBLDJB must be run once before RSP is started for the first time.

After the initial creation of the job flat file using RSPBLDJB, whenever any application's job list changes, run RSPJRFSH to rebuild the extract file (job flat file), and notify RSP on each image that a new Job Reference Table is to be loaded. RSPJRFSH can be run on any image of a complex – all associated images will be automatically updated. You may wish to schedule the execution of RSPJRFSH at some time interval (e.g., once a day) to ensure that application job list changes are reflected in the tables of each image running RSP.




7.6 The APPLEND Program (End-of-Application) When the application cycle completes, the APPLEND job or job step signals the 'End-of-Application' to the RSPSMFTK task to process any remaining SMF records, update the ASAP Database, and to rebuild the application's selection data set for the next backup event. The RSP started task, RSPSMFTK, must be active for APPLEND to process successfully.

The selection data set entries are built from the application entries in the ASAP Database. These entries may have been generated/added to the ASAP Database by:

• Batch SMF Scan data collection • RSP SMF Capture data collection • RSP JCL Capture data collection • 'EXT' (external) type filters • Custom programs which add data set entries to the ASAP Database

SMF and JCL data are merged into a single database record for a given data set name.

External filters (INCL_EXTDSN, ALLOC_EXTDSN, and ACCOMP_EXTDSN) can be used to enter data set names in the database that JCL or SMF data collection may not have captured.

Which of the sources of data set names listed above are employed depends on the application. RSP JCL Capture via the UJI exit is not necessary if the preference is to use only data set namescaptured by the RSP SMF Capture U83 exit. An application may also be comprised of only data set names specified with External filters.

No matter whether you choose to use RSP UJI, or SMF data collection (by Batch SMF Scan or RSP U83 or both) to capture data set information, the application job list must first be built (job collection).

The current verification options in effect for the application will be used in the reconstruction of its selection data set entries (i.e., selection data set format, backup type, base-GDGs, filtering, etc.).

Building of the selection data set is a two stage process.

First, the data set entries from the database are 'Evaluated' for criticality. This process utilizesthe 'Evaluation' filters.

Second, after Evaluation, the selection data set is built in the chosen format.

The


i )


This could be caused by all data sets be ng filtered out (excluded or all data sets being assigned to a category other than INCLUDE (ALLOCATE or ACCOMPANY). Check the comments at the end of the selection data set. The INCL_EXTDSN filter could be used to force an INCLUDE for a dummy data set.




7.6.1 Coding the APPLEND Program Because application cycles are inherently variable, ASAP RSP requires a reliable notification of when an application has completed, so it knows when to rebuild that application's selection data set. The APPLEND program provides this notification to RSP. Insert the APPLEND program into the application either as the last job, or as a step within the last job.

The necessity of using the APPLEND step depends on how the job stream is designed, and the application's backup plan:

• If the exit point of a job stream varies, due to run-time parameter options and/or conditional execution based on program return codes, you can use APPLEND to explicitly tell RSP where the application ends.

• If a backup step will be included right after the application completes execution, RSP requires that you place the APPLEND step before the backup step.

APPLEND Job JCL

The APPLEND member of the ASAP JCL library contains sample APPLEND Job JCL.

//JOBCARD JOB ,'APPLEND',CLASS=?,MSGCLASS=?*---------------------------------------------------------------* //* THIS JOB, PLACED AT THE END OF AN APPLICATION JOB STREAM, * //* TRIGGERS THE UPDATE OF THE ASAP DATABASE AND THE BUILDING OF * //* OF A SELECTION DATASET FOR A SUBSEQUENT BACKUP VIA ABARS ETC. *//* MAKE SURE THE APPLNAME PASSED AS A PARM IS CORRECT. * //* IF THIS PROGRAM COMPLETES WITH A ZERO RETURN CODE, THE ASAP * //* UPDATE AND SELECTION DATASET BUILD PROCESS WAS SUCCESSFUL. * //*---------------------------------------------------------------*//APPLEND PROC //APPLEND EXEC PGM=APPLEND,PARM=APPL(APPLNAME)//* SELREBUILD(DEFAULT)/NOSELREBUILD//* CYCLEINC(DEFAULT)/CYCLENOINC//* DELETEDETAIL/NODELETEDETAIL(DEFAULT)//STEPLIB DD DISP=SHR,DSN=&LOAD//SISLOAD DD DISP=SHR,DSN=&LOAD//ASPINVDB DD DISP=SHR,DSN=&ASAPDB//MSGLOG DD DISP=SHR,DSN=&LOG//SISPARM DD DISP=SHR,DSN=&PARMLIB(BRMINI)//SYSPRINT DD SYSOUT=&SOUT//SYSOUT DD SYSOUT=&SOUT // PEND //APPLEND EXEC APPLEND




To edit the APPLEND JCL:

• Specify the application name in the PARM field of the EXEC statement. The command syntax and parameter descriptions are shown below.

• Specify the ASAP LOAD library name. 'APPL(applname),[SELREBUILD | NOSELREBUILD, CYCLEINC | CYCLENOINC,

DELETEDETAIL | NODELETEDETAIL]'

APPL= ( ),

[ |

|

DELETEDETAIL |]

applname –

keyword(

l

| (s) for

same. |

data will not be available if the verification feature is desired.

default.

REQUIRED KEYWORDS DESCRIPTION

applname

SELREBUILD NOSELREBUILD, CYCLEINC CYCLENOINC,

NODELETEDETAIL

The ASAP application name. SELREBUILD | NOSELREBUILD – Optional parameter

s) for rebuilding an application's selection data set entries. Using the SELREBUILD keyword (which is the default if omitted) will rebuild the application's se ection data set after the ASAP Database update process has been completed. Using the NOSELREBUILD keyword will bypass rebuilding the application's selection data set entries. CYCLEINC CYCLENOINC – Optional parameter keywordincreasing the cycle number. Using the CYCLEINC keyword (which is the default if omitted) will increase the cycle number by 1. This option should be chosen for most applications. Using the CYCLENOINC keyword will keep the cycle number the

DELETEDETAIL NODELETEDETAIL – The DELETEDETAIL keyword causes the DSD records for the application to be deleted after the selection data set has been successfully created and the APPLEND ended with a return code zero. If the APPLEND return code is greater than zero, the DSD records will not be deleted. If the DSD records are removed, a full cycle of

The NODELETEDETAIL keyword does not delete the DSD after the selection data set is created. NODELETEDETAIL is the

Example 1: In this example, application APPL0001 will have its cycle number increased by one and also have its current selection data set rebuilt with the current entries.

//APPLEND EXEC PGM=APPLEND,

// PARM='APPL(APPL0001),CYCLEINC'

Example 2: In this example, application PRODPAY will have its cycle increased by one, but its selection data set will not be rebuilt.

//APPLEND EXEC PGM=APPLEND,

// PARM='APPL(PRODPAY),NOSELREBUILD'




7.6.2 APPLEND Errors If RSP APPLEND produces a non-zero return code, the associated errors are written to the console log and to the SYSPRINT DD.

If a specific SMF record was not captured by RSP, the reason could be that the data set was opened but not closed before APPLEND was encountered. SMF record types 14 and 15 are generated when a data set is closed.

7.6.3 Using Optional OpenTech VDR Filter Lists ASAP allows you to use the OpenTech Virtual Data Recovery (VDR) filter list to exclude selected tape data sets. That exclusion list will be processed after the normal ASAP filters.

If you have VDR, and wish to invoke the VDR filters during the APPLEND processing, simply add a DD statement to the APPLEND job or PROC similar to the following: //VDRPATT DD DISP=SHR,DSN=VDR filter DSN

There is no ASAP setup option for this optional filter. It can only be invoked with the DD statement above. Additionally, the VDR filters cannot be invoked in ASAP Foreground or Background Verify.

7.7 Summary of RSP Job JCL Members The JCL members used by the RSP facility are described below:

JCL Member Description

RSPSETUP RSP file allocation job. Used to allocate and initialize the message log and job flat data sets used by the RSP facility.

RSPSMFTK Started task that installs the IEFU83 exit and starts the subtask that writes records to the ASAP Database.

RSPJSWAP Signals RSP(s) to refresh their job tables from the job flat file. Only needs to be run from one image of a complex. The program executed is also the second step of RSPJRFSH. Normally this function is accomplished by running RSPJRFSH as it also rebuilds the job flat file.

RSPBLDJB Builds the job flat file from the ASAP Database. Only needs to be run once before RSP is started for the first time. Only needs to be run on one image of a complex. For subsequent changes to application job lists, this function is normally accomplished by running RSPJRFSH.

RSPJRFSH Used to rebuild the job flat file, and then initiate a refresh of the internal RSP Job Reference Table on each image from the job flat file. This is a combination of RSPBLDJB and RSPJSWAP. Only needs to be run on one image of a complex. See the topic 'RSP Job Reference Table: Use of RSPBLDJB & RSPJRFSH' (page 76).




7.8 RSP Message Log RSP maintains and continuously updates a message log file with event and diagnostic information for each application on every processor image. The message log file is a required file that is allocated via supplied JCL members.

To view the RSP message log, use ISPF Browse. The first header record contains a LAST and NEXT block pointer (or line number) value, which can be used to locate the last series of recorded RSP messages.

In the example below, the NEXT scheduled recording line of 248 can be used to scroll to the last series of RSP messages.

BROWSE XYZ.ASAPSMF.MSGLOG Line 00000000 Col 001 132 Command ===> Scroll ===> PAGE ********************************* Top of Data ***********************************FORMATTED BY SISFE15D LAST BLOCK:00000309 NEXT BLOCK:00000248 01/02/2001 09.12.43 3476 ASP00903I 06/12/2001 09.49.24 ADR:062CD000 DATE:2001/06/09 TIME:14.18.09477 ASP00518I 06/12/2001 09.49.24 SECONDARY EXIT DATASPACE VSAM SUBTASK 478 ASP00518I 06/12/2001 09.49.24 ACTIVE EXISTS RUNNING 479 ASP00521I 06/12/2001 09.49.29 SMF COOLING COMPLETE FOR: SYS.IEFU83 480 ASP00517E 06/12/2001 09.49.29 SECONDARY EXIT DEACTIVATED481 ASP00732E 06/12/2001 09.49.32 VSAM SUBTASK STOPPED.482 ASP00604I 06/12/2001 09.49.32 DATASPACE REMOVED483 ASP00521I 06/12/2001 09.49.33 SMF SEPARATION COMPLETE FOR: SYS.IEFU83 484 ASP00511I 06/12/2001 09.49.33 EXIT AREA REMOVED485 ASP00800I 06/12/2001 09.49.33 SHUT DOWN COMPLETE486 ASP00912I 06/12/2001 09.52.47 RSPSMFTK: BUILD 20010604 14.06487 ASP00503I 06/12/2001 09.52.48 X-CSA LOCATED AT:062CD000 LENGTH:00006000488 ASP00506I 06/12/2001 09.52.48 X-CSA BUILT AND IDENTIFIED489 ASP00521I 06/12/2001 09.52.49 SMF INTEGRATION COMPLETE FOR: SYS.IEFU83490 ASP00508I 06/12/2001 09.52.49 SECONDARY EXIT LOADED SUCCESSFULLY491 ASP00603I 06/12/2001 09.52.49 DATASPACE BUF COUNT ORIGIN SIZE 492 ASP00603I 06/12/2001 09.52.49 CREATED 104 00000000 36K 493 ASP00521I 06/12/2001 09.52.50 SMF EXCITATION COMPLETE FOR: SYS.IEFU83 494 ASP00515E 06/12/2001 09.52.50 SECONDARY EXIT ACTIVE495 ASP00722I 06/12/2001 09.52.50 VSAM SUBTASK STARTED; USING AMP.QABETA.ASAPDB496 ASP00903I 06/12/2001 09.52.51 ADR:062CD000 DATE: 2001/06/12 TIME:9.52.48497 ASP00518I 06/12/2001 09.52.51 SECONDARY EXIT DATASPACE VSAM SUBTASK 498 ASP00518I 06/12/2001 09.52.51 ACTIVE EXISTS RUNNING 499 ASP00802I 06/12/2001 09.52.51 AUTOSTART COMPLETE




7.9 RSP Monitor RSP Monitor, an ASAP Main Menu option, provides information about RSP processing, and allows the user to perform some RSP operator commands.

To display the RSP Monitor panel, select Option 3 (RSP Monitor) from the ASAP Main Menu. The RSP Monitor provides information about RSP processing and allows the user to perform some of the RSP operator commands. See the topic 'RSPSMFTK (RSP) Operator Commands' (page 7-18).

RSP MONITOR CMD:

1 Display RSP Status2 Display RSP Statistics3 Display Current Job Table4 Display Current Filter Table5 RSP Commands H Help

7.9.1 Display RSP Status – Option 1 Option 1 will display the status of all RSP tasks on the image you are logged onto. To see the reason a task has a status of 'DOWN', select the task using line command S.

RSP TASK STATUS BY SYSID CMD: _____________________________________________________ SYSID ==> P390

TO VIEW TASK STATUS FOR OTHER IMAGES CHANGE SYSID AND PRESS ENTER

TO GET ADDITIONAL INFORMATION ON DOWN TASK SELECT WITH S

STATUS TASK _ UP RSP MONITOR COMMAND PROCESSOR _ UP RSP ASAP DATABASE UPDATE _ UP RSP OVERFLOW EXPORT _ UP RSP OVERFLOW IMPORT _ _

UP UP

RSP U83 EXIT (XXXX MEANS NOT IN USE)RSP UJI EXIT (XXXX MEANS NOT IN USE)

When a 'DOWN' task is selected, the Error Message Detail panel will be displayed.

ERROR MESSAGE DETAIL CMD: SYSID ==> P390

MESSAGE ASP00501E: CAN NOT OPEN EXITLIB

DESCRIPTION A PROBLEM WITH THE LOAD LIBRARIES DEFINED IN THE BRMINI PARMLIB MEMBER.

ACTION/EXPLANATION




7.9.2 Display RSP Statistics – Option 2 Option 2 allows you to review statistics for a specified SYSID and date. You may use the defaults provided on the panel, or enter a date and/or SYSID, then press Enter.

SELECT SYSID AND DATE

COMMAND ==>

ENTER SYSID DEFAULT IS CURRENT SYSID:P390

CHANGE DATE TO VIEW MONITOR STATISTICS FROM PREVIOUS DAYS DEFAULT IS TODAY'S DATE :11/15/01

ENTER TO CONTINUE; PF3(END) TO TERMINATE

The RSP Processing Statistics panel will display information for the specified SYSID and date.

RSP PROCESSING STATISTICS CMD: SYSID ==> P390

ENTER FOR NEW QUERY (UPDATED EVERY 22 SECONDS); END(PF3) TO RETURN

DATA COLLECTED SINCE

More: + U83/UJI EXIT RECORD PROCESSING:

130 U83/UJI RECORDS MOVED TO RSP DATASPACE42 U83/UJI RECORDS DROPPED - NO MATCH IN JOB TABLE0 U83/UJI RECORDS CURRENTLY IN BUFFER OVERFLOW DATA SET0 U83/UJI RECORDS LOST - OVERFLOW DATA SET NOT AVAILABLE0 NUMBER OF TIMES LOSSES OCCURRED N ARE LOSSES OCCURRING NOW?

RSP DATASPACE BUFFERS: 2502 TOTAL BUFFERS 2502 AVAILABLE BUFFERS

7 HIGHEST NUMBER OF BUFFERS USED 0 LONGEST TIME OF CONTINUOUS BUFFER USE IN MINUTES 0 NUMBER OF TIMES 80 TO 99 PERCENT OF BUFFERS IN USE 0 NUMBER OF TIMES 50 TO 79 PERCENT OF BUFFERS IN USE 0 NUMBER OF TIMES 20 TO 49 PERCENT OF BUFFERS IN USE

404 NUMBER OF TIMES 00 TO 19 PERCENT OF BUFFERS IN USE

RSP DATABASE PROCESSING: 120 NUMBER DSD RECORDS WITH NO HITS IN FILTER TABLE 10 NUMBER DSD RECORDS WITH FILTER TABLE HITS 0 NUMBER OF HITS ON KEEP FILTER 10 NUMBER OF HITS ON DISCARD FILTER 200 MAXIMUM NUMBER OF ENTRIES IN DATABASE CACHE 0 NUMBER OF CACHE ENTRIES REUSED WHEN FULL 75 NUMBER OF DSD RECORDS THAT MATCHED CACHE ENTRIES 0 NUMBER OF CACHE MATCHES WITH DATABASE I/O60 NUMBER OF CACHE MATCHES THAT AVOIDED DATABASE I/O15 NUMBER OF DATABASE READS 5 NUMBER OF DATABASE ADDS AND UPDATES

RSP DATABASE TASK TUNING: 50 BUFFER QUEUE THRESHOLD62 AVERAGE NUMBER OF BUFFERS PROCESSED 108 AVERAGE NUMBER OF RECORDS PROCESSED 37 AVERAGE NUMBER OF DATABASE I/O'S8 AVERAGE TIME IN SECONDS TO PROCESS BUFFERS




The fields on the RSP Processing Statistics panel are described below.

Field Description

U83/UJI RECORDS MOVED TO RSP DATASPACE

The number of exit records that matched the selection criteria in the U83 exit program (RSP9254R) or the UJI exit program (RSPUJISE). These records are reformatted and stored in the RSP dataspace. The database task (RSP9254S) will remove them from the dataspace and update the ASAP Database.

U83/UJI RECORDS DROPPED - The number of records that were not moved to the RSP dataspace NO MATCH IN JOB TABLE because the job name associated with these records did not match

a job name in the job table.

U83/UJI RECORDS CURRENTLY The number of records that were moved to the overflow data set IN BUFFER OVERFLOW DATA because there were no available buffers in the RSP dataspace. SET When space becomes available, these records will be moved back

to the RSP dataspace.

U83/UJI RECORDS LOST - The number of records that were lost because the overflow data set OVERFLOW DATA SET NOT was not available or not usable. AVAILABLE

NUMBER OF TIMES LOSSES The number of times that all the buffers in the RSP dataspace were OCCURRED filled and new records could not be moved to the overflow data set.

ARE LOSSES OCCURRING NOW?

The current buffer overrun status. Y (Yes) means that record losses are occurring right now. N (No) means no current record loss, but if the loss fields above are not zero, then previous losses have occurred. NOTE: If you see 'LOSSES', increase the buffers only on the system you see 'losses' on. Also, ensure your overflow file is large enough to accommodate the moves from the dataspace to overflow file.

TOTAL BUFFERS The total number of buffers created when RSP was started.

AVAILABLE BUFFERS The number of buffers not in use.

HIGHEST NUMBER OF BUFFERS The greatest number of buffers in use at one time. USED

LONGEST TIME OF The longest amount of time, in minutes, that the database task CONTINUOUS BUFFER USE IN (RSP9254S) was processing data from the buffers in the RSP MINUTES dataspace, without clearing all the buffers before the U83 exit task

or UJI exit task added a new record.

NUMBER OF TIMES 80 TO 99 These fields are counts of the times the buffer use percentage was PERCENT OF BUFFERS IN USE within the stated ranges. When the statistics record is updated NUMBER OF TIMES 50 TO 79 (every 30 seconds), the database task computes the 'buffers in use' PERCENT OF BUFFERS IN USE percentage and adds 1 to the appropriate bucket.

NUMBER OF TIMES 20 TO 49 PERCENT OF BUFFERS IN USE NUMBER OF TIMES 00 TO 19 PERCENT OF BUFFERS IN USE

NUMBER DSD RECORDS WITH The number of DSD records that did not get any hits against the NO HITS IN FILTER TABLE filter table.




Field Description

NUMBER DSD RECORDS WITH The number of DSD records that got hits against the filter table. FILTER TABLE HITS

NUMBER OF HITS ON KEEP The number of DSD records that got hits on a keep filter. FILTER

NUMBER OF HITS ON DISCARD The number of DSD records that got hits on a discard filter. FILTER

MAXIMUM NUMBER OF ENTRIES The number of entries the database cache can hold. IN DATABASE CACHE

NUMBER OF CACHE ENTRIES When the cache is full, the oldest entry is replaced by the new REUSED WHEN FULL entry. This number is a count of how often this happened.

NUMBER OF DSD RECORDS The number of DSD records from the RSP dataspace that matched THAT MATCHED CACHE a cache entry. ENTRIES

NUMBER OF CACHE MATCHES The number of DSD records that matched cache entries but ASAP WITH DATABASE I/O Database I/O was still required.

NUMBER OF CACHE MATCHES The number of DSD records that matched cache entries and ASAP THAT AVOIDED DATABASE I/O Database I/O was not necessary.

NUMBER OF ASAP DATABASE The number of DSD records read for update. If a record does not READS exist, it is added. It may be updated depending on its contents (see

help on following field).

NUMBER OF ASAP DATABASE The number of DSD records actually updated or added to the ASAP ADDS AND UPDATES Database. If the record does not exist, it is added. An existing

record is only updated if the timestamp for new data is earlier.

BUFFER QUEUE THRESHOLD The database update task will not process buffers until there are at least this number waiting, unless an APPLEND is in progress or a user has requested a flush. The database task optimizes its processing so that it maximizes efficiency when updating the ASAP Database.

AVERAGE NUMBER OF The average number of buffers processed for each database BUFFERS PROCESSED access request when the threshold is set at current value.

AVERAGE NUMBER OF The average number of DSD records created in processing the RECORDS PROCESSED average number of buffers.

AVERAGE NUMBER OF The average number of database I/Os required to process the DATABASE I/O'S average number of records.

AVERAGE TIME IN SECONDS TO Each time the database update task requests database access, it PROCESS BUFFERS will have 30 seconds to do I/O. The task tries to accumulate the

number of buffers it can process in 30 seconds before requesting database I/O.




7.9.3 Display Current Job Table – Option 3 Option 3 displays the members of the Job Table that RSP is currently using.

CURRENT RSP JOB TABLE ROW 1 TO 18 OF 1899 CMD: SCROLL:PAGE

JOB APPLNAME ________ ________ @CSD300V PWOPC1@CSD300V PWOPC2@CSSD300 PWOPC1@CSSD300 PWOPC2ACMD PRESTG2 ADABKUAT CTLMAPPL ADABKUCJ CTLMAPPL ADABKUHS CTLMAPPL ADAROLL CTLMAPPL AE10 XJCSM AE11 XJCSM AI19 XJCSM AI20 XJCSM AI40 XJCSM AI41 XJCSM AI50 XJCSM

7.9.4 Display Current Filter Table – Option 4 Option 4 displays the members of the retention Filter Table that RSP is currently using.

CURRENT RSP RETENTION FILTER TABLE ROW 1 TO 14 OF 14 CMD: SCROLL:PAGE

FILTER FILTER FILTER APPLNAME ACTION TYPE SCOPE FILTER ________ _______ ______ _________ ____________________________________________ UNIVERSE KEEP VOLUME UNIVERSAL TSO003 GLOBAL DISCARD DSN GLOBAL BK.ASAPTEST.GDG5** APPL0001 KEEP VOLUME LOCAL TSO004 APPL0001 KEEP VOLUME LOCAL TSO005 APPL0001 GLOBAL DSN GLOBAL APPL0001 GLOBAL VOLUME GLOBAL BK000001 GLOBAL DSN GLOBAL EMTEST1 DISCARD DSN LOCAL SYS1.LINKLIB EMTEST1 DISCARD DSN LOCAL EM.U.LOAD EMTEST5 DISCARD DSN LOCAL AMP.** EMTEST5 DISCARD DSN LOCAL ABARS.** EMTEST5 DISCARD DSN LOCAL EM.Z.** EMTEST5 DISCARD DSN LOCAL EM.AMPASAP.** EMTEST5 GLOBAL DSN GLOBAL




7.9.5 RSP Commands – Option 5 Option 5 lists the Operator Commands to stop/start the RSP tasks that can be issued from this panel. The user must have SAF authority to issue these commands. Key the number of a listed RSP command in the Command field and press Enter.

RSP COMMANDS CMD:

1 2

FLUSH BUFFERS SYSID:P390 (DEFAULT IS CURRENT SYSID)STOP RSP ASAPDB UPDATE TASK

3 START RSP ASAPDB UPDATE TASK 4 5

KILL RSP ASAPDB UPDATE TASK (USE ONLY WHEN STOP FAILS)STOP RSP DATASPACE OVERFLOW EXPORT TASK

6 START RSP DATASPACE OVERFLOW EXPORT TASK 7 STOP RSP DATASPACE OVERFLOW IMPORT TASK 8 START RSP DATASPACE OVERFLOW IMPORT TASK 9 SUBMIT JOB TO UPDATE RSP JOB TABLE

The command options on the RSP Commands panel are described below. For detailed descriptions of the actual RSP commands that are issued, see the topic 'RSPSMFTK (RSP) Operator Commands' (page 7-18).

Option Description

FLUSH BUFFERS The RSP dataspace buffers will be immediately flushed.

STOP RSP ASAPDB UPDATE F RSP,ASAPUPDT(STOP) TASK

START RSP ASAPDB UPDATE F RSP,ASAPUPDT(START) TASK

KILL RSP ASAPDB UPDATE F RSP,ASAPUPDT(KILL) TASK

STOP RSP DATASPACE F RSP,OVFEXTSK(STOP) OVERFLOW EXPORT TASK

START RSP DATASPACE F RSP,OVFEXTSK(START) OVERFLOW EXPORT TASK

STOP RSP DATASPACE F RSP,OVFIMTSK(STOP) OVERFLOW IMPORT TASK

START RSP DATASPACE F RSP,OVFIMTSK(START) OVERFLOW IMPORT TASK

SUBMIT JOB TO UPDATE RSP Submits job RSPJRFSH directly from the panel. JOB TABLE




7.10 RSPSMFTK (RSP) Operator Commands RSPSMFTK (RSP) collects information about application data set usage, via standard system exits. SMF data is captured using IEFU83 and JCL data is captured using IEFUJI.

7.10.1 Start the ASAP Started Task (RSP) and Individual Subtasks If you want to start RSP now, issue console command:

F RSP,AUTOSTART

This command starts the RSP started task and all individual subtasks shown below that are required for RSP to track job names. In general, AUTOSTART is the only command needed to start RSPSMFTK. See member RSPSMFTK in the ASAP JCL library. The member/procedure name is RSPSMFTK and the started task name is 'RSP'. All modify commands are based on the identifier 'RSP'.

Note: If you stop and start RSP and get an ABEND 201, it means the previous shutdown wasn’t normal. Just restart RSP again.

The only variable within the structure is the dataspace size. The number of buffers is controlled by the DSPC_BUFFERS token in the :ASAPRSP section of the BRMINI member. The DSPC_BUFFERS token is the maximum number of buffers RSP is to use. If the DSPC_BUFFERS token is set to a number less than 5000 or not present, RSP will default to 5000 buffers. RSP will use half of the buffer space (about 2500 buffers) immediately, and then save the remaining space for buffer space increases.

AUTOSTART issues the following commands: F RSP,INI(REFRESH)

F RSP,U83(LOAD)

F RSP,UJI(LOAD)

F RSP,DSPC(CREATE)

F RSP,U83(TURNON)

F RSP,UJI(TURNON)

F RSP,ASAPUPDT(START)

F RSP,OVFIMTSK(START)

F RSP,OVFEXTSK(START)

F RSP,RSPMTASK(START)




7.10.2 Start the ASAP Started Task by Jobname (RSP) and Individual Subtasks The started task can also be started using the JOBNAME= parameter. When starting the RSPSMFTK, the target PROCLIB member name must be specified on the start command. See member RSPSMFTK in the JCL distribution library. The member/procedure name is RSPSMFTK and the started task name is RSP. All modify commands are based on the identifier RSP.

To start the SMF collection main task and associated subtasks at the same time, use the command: S RSPSMFTK,JOBNAME=RSP,PARM=AUTOSTART or S RSPSMFTK,JOBNAME=RSP,PARM=A

Also, if the AutoStart token in the :ASAPRSP section of the BRMINI member is set to YES, the command S RSPSMFTK,JOBNAME=RSP will automatically perform an AUTOSTART.

7.10.3 Start the RSP Started Task without the Individual Subtasks S RSPSMFTK,JOBNAME=RSP

Starts only the started task. Each individual subtask is NOT started or loaded and will need to be done so separately. See member RSPSMFTK in the ASAP JCL library. The member/procedure name is RSPSMFTK and the started task name is 'RSP'. All modify commands are based on the identifier 'RSP.

We recommend the started task RSP and associated subtasks are started at the same time using the autostart functionality.

7.10.4 Stop the RSP Structure P RSP

Stops the RSP structure and terminates the RSPSMFTK via the following commands: F RSP,ASAPUPDT(STOP)

F RSP,OVFIMTSK(STOP)

F RSP,OVFEXMTSK(STOP)

F RSP,RSPMTASK(STOP)

F RSP,U83(TURNOFF)

F RSP,DSPC(DELETE)

F RSP,U83(UNLOAD)




7.10.5 Manipulate the IEFU83 Exit These commands should be entered only at the direction of Mainstar Technical Support. F RSP,U83(...)

Examples F RSP,U83(LOAD)

Acquires ECSA space, loads the primary and secondary exits, and places 'RSP9254Z' in the SYS.IEFU83 exit lists.

Errors include not getting ECSA space, unauthorized LOAD libraries, I/O errors during LOAD SVCs and problems with the dynamic exit processor.

The installation must have IEFU83 defined as an exit within the SMFPRMxx member of SYS1.PARMLIB. IEFU83 can be added without an IPL. F RSP,U83(UNLOAD)

Removes 'RSP9254Z' from the SYS.IEFU83 exit lists and deletes the ECSA space.

There are interlocks preventing the UNLOAD when the VSAM/ASAPUPDT sub task is active and when the dataspace still exits. F RSP,U83(TURNON)

Activates the exit in the SYS.IEFU83 exit lists and modifies the primary exit to call the secondary exit. This starts the SMF data collection. The installation must be collecting SMF 14, 15, 61, 64, 65, and 66 records. An additional general purpose IEFU83 exit is available for users who wish to suppress the actual logging of these record types, or in fact, record types needed by any other IEFU83 exits.

If the primary or secondary exit ABENDs twice, MVS will disable the exit. F RSP,U83(TURNOFF)

Deactivates the exit in the SYS.IEFU83 exit list, and modifies the primary exit to not call the secondary exit. F RSP,U83

Displays some information about the state of the exits. The information also shows the creation date of the ECSA. F RSP,U83(NEWSECONDARY)

Under some circumstances, it may be necessary to load a new secondary exit without deleting the dataspace (and its buffers). There are interlocks to prevent this command from working while the exits are active.

STEP

1

STEP DESCRIPTION

Copy a new exit (RSP9254R) to the LOAD library.

2 Quiesce the exits using the TURNOFF command.

3 Refresh the code with the F RSPAMPI,U83(NEWSECONDARY) command.

4 Activate the exits with a TURNON command.




7.10.6 Manipulate the IEFUJI Exit These commands should be entered only at the direction of Mainstar Technical Support. F RSP,UJI(...)

Examples F RSP,UJI(LOAD)

Acquires ECSA space, loads the primary and secondary exits, and places 'RSPUJIPE' in the SYS.IEFUJI exit lists.

Errors include not getting ECSA space, unauthorized LOAD libraries, I/O errors during LOAD SVCs and problems with the dynamic exit processor.

The installation must have IEFUJI defined as an exit within the SMFPRMxx member of SYS1.PARMLIB. IEFUJI can be added without an IPL. F RSP,UJI(UNLOAD)

Removes 'RSPUJIPE' from the SYS.IEFUJI exit lists and deletes the ECSA space.

There are interlocks preventing the UNLOAD when the VSAM/ASAPUPDT task is active and when the dataspace still exits. F RSP,UJI(TURNON)

Activates the exit in the SYS.IEFUJI exit lists and modifies the primary exit to call the secondary exit. This starts the JCL data collection. If the primary or secondary exit ABENDs twice, MVS will disable the exit. F RSP,UJI(TURNOFF)

Deactivates the exit in the SYS.IEFUJI exit list, and modifies the primary exit to not call the secondary exit. F RSP,UJI(NEWSECONDARY)

Under some circumstances, it may be necessary to load a new secondary exit without deleting the dataspace (and its buffers). There are interlocks to prevent this command from working while the exits are active.

STEP

1

STEP DESCRIPTION

Copy a new exit (RSPUJISE) to the LOAD library.

2 Quiesce the exits using the TURNOFF command.

3 Refresh the code with the F RSP,UJI(NEWSECONDARY) command.

4 Activate the exits with a TURNON command.




7.10.7 Manipulate the VSAM/ASAPUPDT Task F RSP,ASAPUPDT(...)

Examples F RSP,ASAPUPDT(START)

Starts the VSAM/ASAPUPDT task.

Errors include ATTACH SVC problems or VSAM data set problems. ATTACH SVC problems will appear on the console while VSAM errors will appear in the RSPSMFTK SYSLOG file. F RSP,ASAPUPDT(STOP)

Stops the VSAM/ASAPUPDT task.

Not much wrong could occur unless the task ABENDed. If so, RSPSMFTK will issue a 'task not responding' message. In this case, the task will have to be forced out with a '...KILL...' command. F RSP,ASAPUPDT(KILL)

If the task will not stop, and a new one can not be started, the existing task must be destroyed with the KILL command. RSPSMFTK will ask the operator to confirm the forced removal of the task before performing the operation.

7.10.8 Manipulate the Overflow Tasks and RSP Monitor Task F RSP,OVFEXTSK(...)

F RSP,OVFIMTSK(...)

F RSP,RSPMTASK(...)

Examples F RSP,OVFEXTSK(START)

Starts the overflow export task. F RSP,OVFIMTSK(START)

Starts the overflow import task. F RSP,RSPIMTASK(START)

Starts the RSP monitor task. F RSP,OVFEXTSK(STOP)

Stops the overflow export task. F RSP,OVFIMTSK(STOP)

Stops the overflow import task. F RSP,RSPIMTASK(STOP)

Stops the RSP monitor task.




7.11 Real-time Selection Process – Operational Considerations

7.11.1 Back Up or Reorganize the ASAP Database While Leaving RSP Up The ASAP Database should be backed up, and reorganized as the database grows. Schedule the backup (or backup and reorganization) at a slow time of data collection. During this time, ASAP continues to collect data in the dataspace and overflow file. To back up or reorganize the ASAP Database without bringing RSP down, follow the steps listed below.

STEP

1

STEP DESCRIPTION

Ensure no APPLENDs are or will be executing

2 Stop the update subtask on all systems: F RSP,ASAPUPDT(STOP). ASAP will use the overflow file during this process.

3 Back up the ASAP Database.

4 Reorganize the ASAP Database.

5 Start the subtask on all systems: F RSP,ASAPUPDT(START).

6 The best way to back it up is with Concurrent Copy or Mirroring.

7.11.2 Selection Data Sets Must Be Physical Sequential (PS) PDSs and PDSEs are not a good choice for selection data sets used by ASAP because ASAP updates the selection data set and due to the nature of PDSs and PDSEs, two or more members can't be written to at the same time. Sequential files are recommended.

7.11.3 Normal IPL If RSP is shut down normally, it flushes the dataspace to the overflow file and the records stay in the overflow file until RSP is brought back up at which time they are written to the database.

7.11.4 RSP IPL Considerations – Shutdown While RSP is up, the possibility exists that it is collecting necessary data. Therefore, the process for a scheduled IPL is to:

• Drain the initiators • Shut down the job scheduler • Bring RSP down

7.11.5 RSP IPL Considerations – Startup RSP data collection is critical to ensure you collect all possible data, therefore, RSP should be one of the first products started as soon as the system comes up.




7.11.6 Surviving a System Outage If the system crashes, you will lose all RSP data in the DATASPACE. RSP, however, is never that far behind in either updating the ASAP Database, or writing the records to the overflow file – generally, less than 30 seconds. Steps that represent that portion of data will most likely get rerun (regenerated) to put the application back to a good starting point. If STEPA completes just before the crash and the application continues with STEPB, then those records are lost.

7.11.7 Surviving a System Outage (using Record Level Sharing) If the system crashes and you are using Record Level Sharing, the records could be backed up in the coupling facility. There is a fail-over mechanism; if one coupling facility fails, it switches to another.

7.11.8 How RSPJRFSH and the Internal Job Table Works When RSPJRFSH is executed, it updates the job table (JOBFLAT) then notifies the images by setting a switch in each image's message record in the message queue (RSPMSGQ) data set. The message queue has a record in it for each SYSID. The database update task running on each image checks its own message record so it knows when to rebuild its internal table. The system console then says "Job Table Loaded into area". The RSP Monitor gets the information from its own job table maintained on each image – not the JOBFLAT file.

7.12 What to Do If the Overflow Data Set Fills Up – B37 As stated in the topic 'Processing Captured SMF and JCL Records' (page 7-3), the records intercepted by RSP are stored temporarily in buffers created in a dataspace. The database update task unloads the dataspace buffers and updates the ASAP Database. If the database update task gets behind because of a large number of records, the buffers will expand. If still more room is required, the records will overflow to the overflow data set. There is a fine line between the number of buffers specified and the size of the overflow data set.

For performance reasons, buffer sizes must be monitored and enlarged from time to time if ASAP is collecting more data. Performance is lost if just the overflow data set is increased. For more information, see the topic 'Display RSP Statistics – Option 2' (page 7-13), specifically the field 'Are Losses Occurring now?' on the RSP Processing Statistics panel.

A B37 could occur for several reasons:

• Your buffers and overflow data set are not large enough to accommodate the amount of data you are collecting.

Action: Increase your buffer size by 5000 only on the system where the problem is occurring, and use the ASAP Monitor to ensure this amount is large enough to support the data collected.

• It is possible that your RSP update task, ASAPUPDT is down. This can occur if you have the update task down to reorganize your ASAP Database. In this case, ASAP continues to collect and write data to the buffer space and then to the overflow data set.

Action: You may need to increase both buffer size and overflow size to support a regular reorganization.

• It is possible that your RSP update task, ASAPUPDT, is down for another reason.

If the overflow data set already got a B37, you have already lost data. If the ASAPUPDT task is down, bring it back up. If you determine you need to increase the size of the overflow data set, bring RSP down and increase the overflow data set space in the following parameter found in the product PARMLIB member (BRMINI). Overflow_Parms = BLKSIZE(0) UNIT(SYSALLDA) SPACE(x) CYLINDERS +

RACCHECK(YES)




To prevent this from happening again:

1. If the ASAPUPDT task was down, determine why it was down.

2. If the ASAPUPDT task was up, check the RSP Monitor. It is possible that the data space buffers are no longer large enough to support the amount of data you are collecting. Check today's and previous day's information to see if data has been lost.

Check the RSP Processing Statistics panel (see the topic 'Display RSP Statistics – Option 2', page 7-13) and review the following items:

• ARE LOSSES OCCURRING NOW? – Is a Y next to it? • NUMBER OF TIMES LOSSES OCCURRED – Is this greater than 0? • RSP DATA SPACE BUFFERS – Note the number of buffers. • HIGHEST NUMBER OF BUFFERS USED – Does the number equal the TOTAL

buffers?

7.12.1 Monitoring the Overflow The overflow file is used when the buffers fill up either as part of normal processes during busy times, when the buffers are too small, or when the RSP update task has been shut down to do an ASAP Database reorganization.

Data written to the overflow may signal a problem if the overflow is not large enough to accommodate the data collected during a reorganization, during a busy period, or because the buffers have not been increased when they should be, causing data to spill over to the overflow more often. If you want to monitor when data goes to the overflow, signaling a possible overflow file out-of-space condition, two new messages have been added to signal this event:

• Message ASP03810I OVERFLOW DATASET LOAD STARTED will appear when the buffers are about to be unloaded and written to the overflow data set.

• Message ASP03811I OVERFLOW DATASET LOAD FINISHED will appear when all the buffer data has been written to the overflow data set.

7.13 Increasing the RSP Buffer Size If a system is losing records, you will need to increase the number of buffers.

1. Stop RSP.

2. Increase the buffers by 5000 (only on the system losing records).

3. Restart RSP.




Chapter 8 8 Obtaining Application Information

This chapter explains how to obtain application-related information from ASAP using dialog functions and batch operations.

Contents:

• LIST APPLICATIONS (Option 1) – page 8-2

• Application STATUS Display (Option 6) – page 8-7

Mainstar Software Corporation ©2006 8-1 Chapter 8 SC23-6059-00 Obtaining Application Information



8.1 LIST APPLICATIONS – Option 1 LIST APPLICATIONS is a set of panels accessed from the ASAP Main Menu that displays categories of information, such as job collection, Batch SMF Scan, Verification, etc., for all current applications in the ASAP Database. The panel commands and line commands provide interactive options for using the data, and allow you to customize your use of the information.

Categories of information can be displayed by either scrolling left or right such as:

• Recent Events • Last job collection Information • User's Current Preferences for Using List Application

Note: Some ASAP panels require PFSHOW be turned off. If you cannot see part of a panel because the PF Keys are displayed, go to the ISPF command line and type PFSHOW. PFSHOW is a toggle switch that turns off the display of PF Keys.

8.1.1 Using the Application List Panels From the ASAP Main Menu, select Option 1 (LIST APPLICATIONS). The Create Application List pop-up panel will be displayed.


OPTION ==>

W E L C O M E To:




Your Last Active Application: EMTEST9Copyright (C) 1997-2006 by Mainstar Software Corporation; All Rights Reserved

Chapter 8 8-2 Mainstar Software Corporation ©2006 Obtaining Application Information SC23-6059-00



8.1.2 Create Application List Panel The Create Application List panel is a pop-up that allows you to choose all or only a portion of the applications.

CREATE APPLICATION LIST

COMMAND ==>

ENTER APPLICATION OR MASK:

ENTER TO CONTINUE; PF3(END) TO TERMINATE

If the user presses Enter, all applications will be displayed. All applications will also be displayed if the user enters an “*”. Any mask that conforms to the Mainstar extended ACS masking character set is valid (see the topic 'Mainstar Extended ACS Filtering Pattern Masks' on page 9-27).



_________ _______ _____ __________________________________________


8.1.3 Using the Application List Panels The initial panel shows application names, creating user and a description field. This is the default panel.

<VvRr.xx> ASAP APPLICATION LIST ROW 1 TO 7 OF 7

CMD: SCROLL: PAGE

MORE > USE PF1 FOR HELP PRIMARY COMMANDS => FIND, SHOWXCOLUMN COMMANDS => >, <, X, I, F, R, S, M, A AND BLINE COMMANDS => D, S AND V

CM ASAP

APPL Name UpdatedBy Usr

Last Event Application Description/Title

_ _ _ _ _ _ _ _

CA7 CONTROLM ISPF JOBTRAC PRESTAGE USERDSN ZEKE

USR USR USR USR USR USR USR

VER JOB AUD JOB JOB JCL ...

CA7 APPLICATION CONTROLM APPLICATION ISPF APPLICATION JOBTRAC APPLICATION PRESTAGE APPLICATION USERDSN APPLICATION ZEKE APPLICATION

CREATED ON 12/03/2001CREATED ON 12/01/2001CREATED ON 12/13/2001CREATED ON 08/28/2001CREATED ON 11/05/2001CREATED ON 08/28/2001CREATED ON 09/04/2001

Scrolling – The display can be scrolled Up/Down and Left/Right.

Scroll Right, for additional displays of major categories of application information.

Primary Commands – Primary commands are entered on the command line. Available commands are described in the topic 'Application List Panel Primary Command Values' (page 8-5).

Column Commands – Column commands are entered above the columns. Available commands are described in the topic ‘Application List Panel Column Commands’ (page 8-5).

Line Commands – Line commands are associated with application names (left side of display). Scroll Right, for additional category displays. Available line commands are described in the topic 'Application List Panel Line Commands' (page 8-6).




8.1.4 Application List Panel Primary Command Values The following commands are available on the Application List panel.

Command Description

FIND The FIND command will search for the string in all columns. The found data will be highlighted in red, and the first row that contains the found data will become the top row.

SHOWX The SHOWX command is used with the column command X. If the SHOWX command is on (SHOWX ON) then a column marker will appear where the excluded column was. If the SHOWX command is off (SHOWX OFF), then no marker will appear for the excluded column. The default is SHOWX ON.

8.1.5 Application List Panel Column Commands The following Column Commands are available on the Application List panel. The Column Commands are one character. Sort is 'S', not 'SORT'.

Column Command Description

< Reduces the size of the column to the size of the longest item in the column. The column header may be affected, if the column is no longer wide enough.

> Restores the column to its original size.

X Excludes the column from the display. Please see the SHOWX command for additional explanation.

I Restores a fixed column to its original position in the display.

F Causes a column of data to appear in every scroll right or left in a fixed left-hand position after the application. Before using the fix command, the column must be moved to the proper position using the M, B, and A column commands that are described below.

R Resets the excluded column, causing it to reappear in the display.

S Sorts the rows by data in the column selected.

M Designates the column to be moved.

A Indicates that the designated move column is to be moved after this column.

B Indicates that the designated move column is to be moved before this column.




8.1.6 Application List Panel Line Commands The following line commands are available on the Application List panel.

Line Command Description

D Deletes an application. A prompt will be issued to verify the Delete operation.

S Selects the application by going directly to the Application AutoBuild Menu.

V View the Application Information display of the application. See the next topic.

The Application Information Display

Use the V line command to view a single application in a vertical display. Scroll Up/Down to review the information desired. All of the categories of information for a single application are displayed.

Figure 8-1: Application Information Display

.---------------------- APPLICATION INFORMATION -----------------------_. | Command ==> <=) || || --- APPLICATION General Information --- || Appl DESC => CA7 APPLICATION CREATED ON 01/10/2004 <= || Last Event: => VER || Last User Update: => USR || Associated AGGREGATE: => CA7 || || --- EVENT Information --- || Last Event Info: => VER-SELDSN || Last Job Collection: => 2000353/1116 || Last SMF Scan: => 2000325/1854 || Last VER Event: => 2001008/1714 || || --- Job Collection Information --- || Job Collection Method: => CA7 || Job Collection Type: => REPLACE || Total JOBs: => 19 || Total ANCHORs: => 5 || First ANCHOR Element: => CA7600 || |




8.2 Application STATUS Display – Option 6 To use the STATUS option from the Application AutoBuild Options panel, you must start at the ASAP Main Menu, select Option 2 (SELECT/CREATE APPL) specify or select an application, and then select Option 6 (STATUS) from the Application AutoBuild Options menu.

The Display Selections pop-up menu will be displayed for the current application. Each display option is described in a separate topic below.

.------------------- ASAP APPLICATION Display Selections --------------------.| => BKTEST03 || Use S For Selections; Use PF1 For HELP || || _ 1) N/A || _ 2) Display Current JOB List || _ 3) Display Current JOB Anchor Chains || _ 4) Display Data Set Detail Records (JCL,RSP,Batch SMF) || _ 5) Display Current JCL/SMF DSN Entries || _ 6) Display Current JCL/SMF DSN Entries with URD Information || _ 8) Display Summary of Last RSP Selection Data Set || _ 9) Browse Selection Data Set Contents (Choose A,B or C ) || A)VERIFY(One time build): || N/A || B)VERIFY(Database): || BK.AMPASAP.BKTEST03.SELECT || C)RSP: || BK.AMPASAP.BKTEST03.SELECT || _ 10) N/A || _ 11) N/A || || |'----------------------------------------------------------------------------'




8.2.1 Option 1 is N/A

8.2.2 Display Current JOB List Select Option 2, Display Current JOB List, from the Display Selections pop-up menu to display an ISPF table that lists all jobs identified as belonging to this application. This information is obtained during the first step in the data collection sequence – job collection. The display lists only the individual job element names for the application, in alphanumeric sequence order.

Depending upon the job scheduling product used for collection, the display columns and headings may appear different for your installation.

ROW 1 TO 4 OF 4 Command ==> APPLICATION ==> NEWAPL5

Job Name Misc Descriptive Info

PBE0001M COLLECTED 2004/12/15 07:24:13 PBE0002M COLLECTED 2004/12/15 07:24:13 PBE0003M COLLECTED 2004/12/15 07:24:13 PBE0004M COLLECTED 2004/12/15 07:24:13




8.2.3 Display Current Job Anchor Chains Select Option 3, Display Current JOB Anchor Chains, from the Display Selections pop-up menu to display a job anchor structure display for all jobs collected previously. The job anchor structure list contains each application Anchor job (or anchor synchronization point) along with its associated (succeeding) job structure entries.

Depending upon the job scheduling product used for collection, the display columns and headings may appear different for your installation. In the example shown, Unicenter CA-7 was used.

Figure 8-2: Application Anchor Job Structures

Command ==> Valid Commands => FIND

ROW 16 TO 29 OF 146 APPLICATION ==> NEWAPL5

JOB/Anchor Type

PBE0029M CA7 PBE0030M CA7 PBE0031M CA7 PBE0032M CA7 PBE0035M CA7 PBE0038M CA7

PBE0039M CA7

JOB Structure Elements

PBE0029M PBE0030M PBE0031M PBE0032M PBE0035M PBE0040M PBE0041M PBE0042M PBE0043M PBE0044M PBE0045M PBE0046M PBE0047M PBE0048M PBE0049M PBE0050M PBE0051M PBE0052M PBE0053M PBE0054M PBE0055M PBE0056M PBE0057M PBE0058M PBE0059M PBE0060M PBE0061M PBE0062M PBE0068M PBE0041M PBE0042M PBE0043M PBE0044M PBE0045M PBE0046M PBE0047M PBE0048M PBE0049M PBE0050M PBE0051M PBE0052M PBE0053M PBE0054M PBE0055M PBE0056M PBE0057M PBE0058M PBE0059M PBE0060M




8.2.4 Display Data Set Detail Records (RSP JCL, RSP, Batch SMF) Select Option 4, Display Data Set Detail Records, from the Display Selections pop-up menu to display a combination display containing information about the data sets identified with this application during RSP JCL Capture, RSP SMF Capture and/or Batch SMF Scan. The panel shows all data set detail records currently in the database.

The display can be scrolled Left/Right to obtain additional information.

DATA SET DETAIL RECORDS ROW 40 TO 63 OF 63 CMD: SCROLL:CSR

MORE > APPL:APPL0001 CURRENT CYCLES:RSP 49 JCL 49 SMF 1

REC CYCLE C JCL JCL JCL CM DATA SET NAME TYP *=CURRENT C SDP NDP ADP __ ____________________________________________ ___ __________ _ ___ ___ ___

XYZ.A038.DATA XYZ.A039.DATA XYZ.A040.DATA XYZ.A041.DATA XYZ.A042.DATA XYZ.A043.DATA XYZ.A044.DATA XYZ.A045.DATA XYZ.A046.DATA XYZ.A047.DATA XYZ.A048.DATA XYZ.A049.DATA XYZ.GDG1.G0017V00 XYZ.GDG1.G0018V00 XYZ.GDG1(-1)XYZ.GDG1(-2)XYZ.GDG1(0)XYZ.GDG3.G0017V00 XYZ.GDG3.G0018V00 XYZ.GDG3(-1)XYZ.GDG3(-2)XYZ.GDG3(-3)XYZ.GDG3(0)

RSP 49 * *** *** *** RSP 49 * *** *** *** RSP 49 * *** *** *** RSP 49 * *** *** *** RSP 49 * *** *** *** RSP 49 * *** *** *** RSP 49 * *** *** *** RSP 49 * *** *** *** RSP 49 * *** *** *** RSP 49 * *** *** *** RSP 49 * *** *** *** RSP 49 * *** *** *** RSP 49 * *** *** *** RSP 49 * *** *** *** JCL 49 * MOD CAT DEL JCL 49 * NEW CAT DEL JCL 49 * NEW CAT DEL RSP 49 * *** *** *** RSP 49 * *** *** *** JCL 49 * NEW CAT DEL JCL 49 * NEW CAT DEL JCL 49 * SHR *** *** JCL 49 * NEW CAT DEL

Note that records captured by RSP may show a cycle number one (1) greater than the current cycle. If this is the case, RSP has written a record for the next cycle but the APPLEND to 'close out' the cycle has not occurred yet. Current cycle records are those that will be used in creating a selection data set. For records captured by RSP, note that from the Setup panel you may choose to include more than one cycle's worth of data in the selection data set.

Note that RSP SMF Capture, RSP JCL Capture or Batch SMF Scan records information for the first reference to a data set within the job stream. RSP JCL or SMF Capture also records the first URD of a data set. For URD information, select Option 6, Display Current JCL/SMF DSN Entries with URD Information, from the Display Selections pop-up menu.




The fields on the Display Data Set Detail Records display are described below.

Field Description

APPL The application for which data is displayed.

CURRENT CYCLES This field in the header line shows the current cycle number for RSP (RSP SMF Capture-IEFU83), JCL (RSP JCL Capture-IEFUJI exit) and SMF (Batch SMF Scan).

CM (command) Enter an S for a full screen display of the selected data set.

DATA SET NAME Data Set name collected from RSP SMF Capture, RSP JCL Capture or Batch SMF Scan.

REC TYP Source of record. The field may contain: • RSP (SMF records captured by RSP SMF Capture using

IEFU83) • JCL (interpreted JCL captured by RSP JCL Capture using

IEFUJI) SMF (records collected by Batch SMF Scan)

Cycle Cycle number of RSP SMF Capture, RSP JCL Capture or Batch SMF Scan.

CC An '*' indicates that the record is in the current cycle.

JCL SDP JCL scheduler disposition 1st subparm of JCL DISP parm.

JCL NDP JCL normal disposition 2nd subparm of JCL DISP parm.

JCL ADP JCL abnormal disposition 3rd subparm of JCL DISP parm.

JCL JOB NAME Job name from RSP JCL Capture.

JCL DDNAME DD name from RSP JCL Capture.

JCL DATE Date of from RSP JCL Capture.

JCL TIME Time of from RSP JCL Capture.

SYS ID System ID collected from.

SMF TYP SMF record type.

SMF DATE Date from SMF record.

SMF TIME Time from SMF record.

SMF JOB NAME Job name from SMF record.

SMF DDNAME DD name from SMF record.

SMF UNIT Device UNIT from SMF record.

SMF VOLUME Volume from SMF record.

SMF ACCESS Type of data set access from SMF record.

SMF DSP Disposition from SMF record.

SMF DSORG Data set organization from SMF record.

SMF DSN-SIZE Size of data set in K-bytes.




8.2.5 Display Current JCL/SMF DSN Entries Select Option 5, Display Current JCL/SMF DSN Entries, from the Display Selections pop-up menu to display a combined data set list containing information about the data sets identified with this application from RSP SMF Capture, RSP JCL Capture and/or Batch SMF Scan.

The display can be scrolled Left/Right to view additional information.

DATA SET RECORDS FOR INCLUSION IN SDS ROW 538 TO 573 OF 573 CMD: SCROLL:CSR

MORE > APPL:APPL0001

SDS SMF SMF JCL JCL CM DATA SET NAME STAT UNIT VOLSER SDP NDP __ ____________________________________________ _________ ____ ______ ___ ___

XYZ.GDG1(-77)XYZ.GDG1(-78)XYZ.GDG1(-79)XYZ.GDG1(-8)XYZ.GDG1(-80)XYZ.GDG1(-81)XYZ.GDG1(-82)XYZ.GDG1(-83)XYZ.GDG1(-84)XYZ.GDG1(-85)XYZ.GDG1(-86)XYZ.GDG1(-87)XYZ.GDG1(-88)XYZ.GDG1(-89)XYZ.GDG1(-9)XYZ.GDG1(-90)XYZ.GDG1(-91)XYZ.GDG1(-92)XYZ.GDG1(-93)XYZ.GDG1(-94)XYZ.GDG1(-95)XYZ.GDG1(-96)XYZ.GDG1(-97)XYZ.GDG1(-98)XYZ.GDG1(-99)XYZ.GDG1 XYZ.GDG3.G0017V00 XYZ.GDG3.G0018V00 XYZ.GDG3.G0019V00 XYZ.GDG3.G0020V00 XYZ.GDG3.G0021V00 XYZ.GDG3(-1)XYZ.GDG3(-2)XYZ.GDG3(-3)XYZ.GDG3(0)XYZ.JUNK.DATA

INCLUDE DASD TSO002 *** *** INCLUDE DASD TSO002 *** *** INCLUDE DASD TSO002 *** *** INCLUDE DASD TSO003 *** *** INCLUDE DASD TSO002 *** *** INCLUDE DASD TSO002 *** *** INCLUDE DASD TSO002 *** *** INCLUDE DASD TSO002 *** *** INCLUDE DASD TSO002 *** *** INCLUDE DASD TSO003 *** *** INCLUDE DASD TSO003 *** *** INCLUDE DASD TSO003 *** *** INCLUDE DASD TSO003 *** *** INCLUDE DASD TSO003 *** *** INCLUDE DASD TSO003 *** *** INCLUDE DASD TSO003 *** *** INCLUDE DASD TSO003 *** *** INCLUDE DASD TSO003 *** *** INCLUDE DASD TSO003 *** *** INCLUDE DASD TSO003 *** *** INCLUDE DASD TSO003 *** *** INCLUDE DASD TSO003 *** *** INCLUDE DASD TSO003 *** *** INCLUDE DASD TSO003 *** *** INCLUDE DASD TSO003 *** *** GDGBASE DASD TSO002 OLD SHR INCLUDE DASD TSO002 *** *** INCLUDE DASD TSO003 *** *** EXCLUDE DASD MIGRAT *** *** EXCLUDE DASD MIGRAT *** *** EXCLUDE DASD MIGRAT *** *** EXCLUDE DASD MIGRAT NEW CAT EXCLUDE DASD MIGRAT NEW CAT INCLUDE **** ****** SHR *** EXCLUDE DASD MIGRAT NEW CAT INCLUDE DASD TSO003 SHR ***

The panel displays records created as a result of running 'Verification' either from ISPF or from an RSP APPLEND step. The first step of Verification selects data set detail records based on cycles, and combines information from RSP SMF Capture, RSP JCL Capture and/or Batch SMF Scan into a single record per data set. Data set records in this display may have been created from filters, and also from GDG rules (i.e., additional generations may have been added).

The selection data set category is shown, determined by evaluating the data set information, and from filter overrides. Important in this display is the filter, which may have influenced which selection data set category a data set is placed in. Use this display for more information as to why a data set was placed in a given selection data set category.

The fields on the Display Current JCL/SMF DSN Entries are described below.




Field Description

APPL The application for which data is displayed.

CM (command) Enter an S for a full screen display of the selected data set. See below for more information about using the Select command.

DATA SET NAME Data set name collected from RSP SMF Capture, RSP JCL Capture, Batch SMF Scan, or added from filters or GDG rules.

SDS STAT Selection data set status. This indicates the category chosen for the selection data set.

SMF UNIT Device UNIT from SMF record.

SMF VOLUME Volume from SMF record.

JCL SDP JCL scheduler disposition – 1st subparm of JCL DISP parm.

JCL NDP JCL normal disposition – 2nd subparm of JCL DISP parm.

JCL ADP JCL abnormal disposition – 3rd subparm of JCL DISP parm.

JCL JOB NAME RSP JCL Capture job name.

JCL CYCLE Cycle of RSP JCL Capture.

SMF SYID SMF system ID.

SMF RTY SMF record type.

SMF CYCLE Cycle of SMF data (RSP SMF Capture or Batch SMF Scan).

SMF JOB NAME Job name from SMF record.

SMF DDNAME DD name from SMF record.

SMF ACCESS Type of data set access from SMF record.

SMF DSP Disposition from SMF record.

SMF ORG Data set organization from SMF record.

SMF DSN-SIZE Size of data set in K-bytes.




To view a full screen display for a selected data set, enter an S in the CM (command) field on the Display Selections pop-up menu. An example is shown below.

DSR DATA Command ==> APPLICATION ==> APPL0001

DATA SET NAME: XYZ.GDG3.G0017V00 STATUS: INCLUDE REASON: EVALUATION FILTER HIT: NO HIT FILTER SCOPE: FILTER TYPE: FILTER: GDS:

SMF DATA RECORD TYPE: 14 SYSID CYCLE NUMBER DATE TIME P390 0000000049 2001.133 09.06.33.17 JOB NAME DDNAME PROGRAM ACCESS DISP UNIT VOLSER ORG SIZE/KXYZTST1 SYSUT1 ******** INPUT OLD DASD TSO002 PS 00000056 JCL DATA CYCLE NUMBER 0000000000 JOB NAME DDNAME PROGRAM DISP DISP DISP ******** ******** *** *** *** URD DATA RECORD TYPE: 00 SYSID CYCLE NUMBER DATE TIME P390 0000000000 0000.000 00.00.00.00 JOB NAME DDNAME PROGRAM ACCESS DISP UNIT VOLSER ORG SIZE/KXYZTST1 ******** ******** ******** *** **** ****** ** 00000000

Note that this display includes filter information and Update, Rename, and Delete (URD) information. If the reason for the STATUS is not EVALUATION, a filter caused the selection data set category to be other than what normal evaluation may have produced.

GDS DSR Record Action

The comments below provide some explanation for the eventual status of GDS DSR records when an 'S' is placed to the left of a data set in the CM (command) field. However, because the comment cannot be more than 44 characters, it cannot be detailed. The user must still understand how the setting of GDG switches will affect the eventual status.

The comments listed on the following page are possible GDS actions.




Comment Explanation

ADDED TO SATISFY MISSING GDSs added because of switch setting for missing GDS. GDS OPTION

ONLYNEW GDS REQUESTED AS When forward recovery and new GDS only reference switch set to INCLUDE include.

ONLYNEW GDS REQUESTED AS When forward recovery and new GDS only reference switch set to EXCLUDE exclude.

NEW GDS REQUESTED AS When no forward recovery and new GDS switch set to include. INCLUDE

NEW GDS REQUESTED AS When no forward recovery and new GDS switch set to allocate. ALLOCATE

REPLACED BY NEW GDS When forward recovery all not new GDSs excluded when new (ADDMISS=F) GDSs exist.

REL GDS IGNORED BY GDG Relative GDS created using SMF data but no JCL info in DSR RULES record.

ABS GDS IGNORED BY GDG Absolute GDS created using JCL data but no SMF info in DSR RULES record.

RELATIVE GDS NAMES NOT Only absolute GDSs wanted. SELECTED

ABSOLUTE GDS NAMES NOT Only relative GDSs wanted. SELECTED

8.2.6 Display Current JCL/SMF DSN Entries with URD Information Select Option 6, Display Current JCL/SMF DSN Entries with URD Information, from the Display Selections pop-up menu to display only those data sets that were found by RSP to have been updated, renamed, or deleted.

URD information is important because if a data set is updated, renamed, or deleted during application processing, a backup must be performed before the job causing the update, rename, or delete if you wish to rerun the application from the beginning.




8.2.7 Display Summary of Last RSP Selection Data Set Select Option 8, Display Summary of Last RSP Selection Data Set, from the Display Selections popup menu to display summary information for the last selection data set for the current application. Please note that the last selection data set built by both Verify and RSP may be selected from the panel.

The summary will be displayed as shown below.

.-------- Current INCLUDE Status ---------. | || APPLICATION => BK000001 || || SUMMARY: || || Current SIZE => 00009016 MB || Total Datasets => 0012 || Est Tape USAGE => 0003 || Est Elapsed Time => 0010 MINS || || DETAIL (DSN Types): || || DASD Prime => 0007 || ACCOMPNY => 0001 || ALLOCATE => 0004 |'-----------------------------------------'

8.2.8 Browse Selection Data Set Contents Select Option 9, Browse Selection Data Set Contents, from the Display Selections pop-up menu. Choose which data set you would like to browse (A, B or C). If an N/A appears after A, B or C, there is no cataloged selection data set for that category.

• Selection Data Set A – the one-time-build data set from foreground VERIFICATION (Option 4 on the Application Autobuild Options menu).

• Selection Data Set B – the Verify data set in the database that was chosen in SETUP (Option 0 on the Application Autobuild Options menu).

• Selection Data Set C – the RSP data set in the database that was chosen in SETUP (Option 0 on the Application Autobuild Options menu).

Each option causes an ISPF Browse screen to be displayed which lists the data sets associated with the application and their selection criteria status: INCLUDE, EXCLUDE, ACCOMPANY, or ALLOCATE. The contents and format of the application's selection data set will be specific to the application's output format.




In this example, the ABARS format was used.

BROWSE AMP.AMPASAP.CA7.SDS Line 00000000 Col 001 080 Command ===> Scroll ===> CSR ******************************* Top of Data *********************************/* *//* LAST UPDATE: USER1 01/10/2004 09:34:45 *//* SELECTION DATA SET UPDATE VIA ASAP(C) FACILITY: *//* COPYRIGHT 2006 MAINSTAR SOFTWARE CORPORATION *//* *//* APPL NAME: CA7 *//* DESC: CA7 APPLICATION CREATED ON 01/10/2004 *//* *//* DSN FORMAT: ABARS *//* SYSID: **** *//* EXEC MODE: DIALOG (OPTION-4) *//* RE-EVALUATE DATASET ENTRIES: YES *//* DATASETS EVALUATED FROM: SMF AND JCL *//* TAPE DATASETS AS ACCOMPANY: NO *//* USE SIZE FOR INC/ACC TAPES: NO *//* CTLG CHK: ENABLED *//* PROCESS FILTERS: YES *//* NAME TYPE FOR GDSES: ABSOLUTE *//* GDSES EVALUATED FROM: SMF AND JCL *//* EXPAND BASE GDG REFERENCE: NO *//* ADD MISSING GDSES: MIN FOR FWD RECOVRY *//* CATEGORY FOR MISSING GDSES: INCLUDE *//* CATEGORY FOR NEW GDSES: INCLUDE *//* VDR FILTERS: ACTIVE=NO *//* */


)

Each output selection data set will contain both the active entries and commented entries.

• The active entries and keywords will be specific to the application's output format (i.e. ABARS, XSS, FDR, etc.).

• The commented entries, listed below the active entries, represent data set names excluded by Verification due to either filtering, non-critical and/or other conditions.




Chapter 9 9 FILTERS – Using Filters and Controls

This chapter explains how to use Filters and Controls to limit the job name and data set entries in the application's selection data set and the ASAP Database.

Contents:

• Filters and Controls Overview – page 9-2

• Types of Filters – page 9-4

• Levels of Filters – page 9-11

• Creating and Displaying Filters – page 9-13

• Mainstar Extended ACS Filtering Pattern Masks – page 9-27

• Reviewing the Results of Application Filtering – page 9-28

• Filtering Tips – page 9-29

• Using Optional OpenTech VDR Filter Lists – page 9-29

The


i )


This could be caused by all data sets be ng filtered out (excluded or all data sets being assigned to a category other than INCLUDE (ALLOCATE or ACCOMPANY). Check the comments at the end of the selection data set. Note that the INCL_EXTDSN filter could be used to force an INCLUDE for a dummy data set.

Mainstar Software Corporation ©2006 9-1 Chapter 9 SC23-6059-00 FILTERS – Using Filters and Controls



9.1 Filters and Controls Overview

9.1.1 Types of Information Filtered For each ASAP application, two types of information are collected and saved:

• Job Entries/Job Anchor Structures • Data Set Entries

9.1.2 Levels of Filtering There are three levels of filtering. Data set filtering is controlled by all three – Universal, Global, and Local filters. Job filtering is controlled only by Local filters.

The three levels of filters are:

• Universal – Universal filters override any ASAP application. Once Universal filters are defined, they are automatically processed first for absolute control. Universal filters are defined from the main ASAP menu because they pertain to all ASAP applications. Universal filters can be used for any data sets but good examples are: SYS1 data sets, any data sets backed up by full volume dump, or any data set you don't want any ASAP application to back up.

• Global – Global filters are defined and then have to be turned on to an ASAP application for them to take effect. For example, let's say you have files such as PROD.PROCLIB and PROD.JCLLIB. You want most of your ASAP applications to exclude these, but you want one of them to back up these files. By creating a Global Filter from the main ASAP menu, you can turn on the Global filters to all ASAP applications but the one you want to back them up. Other examples might be databases, etc.

• Local – Local filters apply to a specific application only and are defined using Option 2 (FILTERS) on the ASAP Application AutoBuild Options panel.

Universal Filters automatically occur for each ASAP application. Although global filters are defined through the ASAP Main Menu, they must be enabled or disabled for each application. This can be accomplished within each application using Option 2 (FILTERS) on the ASAP Application AutoBuild Options panel. This is also where Local filters are defined.

Chapter 9 9-2 Mainstar Software Corporation ©2006 FILTERS – Using Filters and Controls SC23-6059-00



9.1.3 Types of Filters The ASAP filtering options allow you to limit the scope of both the job entries/job anchor structures and the data set entries saved in the ASAP Database. As long as the filters are in the ASAP Database, data set names will be included/excluded in the selection data set each time the selection data set is built.

Within the Universal, Global and Local filter types, three additional filter types control the contents of the ASAP Database and the selection data set. These are important to understand because they determine whether data is entered into the ASAP Database or not. These filters are:

• Job COLLECTION filters – Alter job list making up an application. • Data set RETENTION filters – Determine whether data set names are added to the ASAP

Database. In other words, don't add any entries matching data sets in the Retention filter to the ASAP Database. It means each APPLEND for each application will not have to sort out additional records to exclude for data sets you know you don't want an ASAP application to back up. Adding records you don't want will prolong the APPLEND process. For instance, if you have SYS1 data sets and you know you don't want any ASAP application to back them up, put them in the 'Universal Retention Filters'. Doing so will lessen the APPLEND time and keep your ASAP Database at a maintainable size. If on the other hand, you want the entries to be written to the ASAP Database but just excluded from the ASAP applications, use the 'Evaluation Filters' described below. Using Retention for Global Filters is similar to Universal. You decide what you want ASAP to write to the ASAP Database. Local Retention filters are more risky. Remember that any data set name put in a Local Retention filter will not be added to the ASAP Database for that application and therefore can not be analyzed for criticality.

Note: For certain new data sets, SMF records do not have the volume serial number, and thus volume retention filters have no volume to match. Volume evaluation filters will work in those cases.

• Data set EVALUATION filters – Determine whether data set names in the ASAP Database will be evaluated for criticality. In other words, add all entries matching data sets in the Evaluation filter to the ASAP Database and when APPLEND or Verification is executed, put them in the correct category based on the filter you used. For example, you put an exclude data set statement in the local evaluation filter for 'PAYB.**' which belongs to ASAP application PAYROLL. All 'PAYB.**' data sets found during the Payroll cycle will be written to the ASAP Database for application Payroll but will be excluded in the selection data set. By using the evaluation filter and writing them to the ASAP Database, you have an audit of what you excluded and you can verify that you didn't exclude something by accident.

9.1.4 Categories of Filters For each application, a filtering pattern can be established using Option 2 (FILTERS) on the ASAP Application AutoBuild Options panel. The filtering pattern is made up of seven categories of filtering keyword statements as follows:

• Job Names • Data Set Names • External Data Set Names • Volume Names • Unit Names • SYSID Names • DSORG (Data Set Organization) Types




9.2 Types of Filters As stated earlier, three types of filters affect ASAP processing:

• Job Collection Filters – Alter job list making up an application. • Data Set Retention Filters – Determine whether data set names are added to the ASAP

Database. • Data Set Evaluation Filters – Determine whether data set names in the ASAP Database

should be evaluated for criticality.

9.2.1 Job Collection Filters Used with Job Scheduling Products Currently, the only job collection filter is the job name filter. INCL and EXCL filters affect which job names are added to the ASAP Database from job collection. These filters only apply to job names collected from a job scheduling product. The INCL_EXTJOB filter adds job names or masks directly to the ASAP Database, bypassing any job collect processing or filtering.

Note: Job Name Filters do not apply if job names are collected manually using the ISPF Edit option.

Control statement syntax: {INCL | EXCL}_JOB(jobname or mask)

INCL_EXTJOB(jobname or mask)

Where: jobname or mask can be either explicitly stated job names or a Mainstar extended ACS filter mask. See the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 9-27).

Excludes are processed after Includes and take precedence. Job name filters are only local to the application. Global and Universal filter options do not exist for job name filtering.

Jobname filters can be set up by selecting Option 2 (FILTERS) from the ASAP Application AutoBuild Options menu.

Additional job name selection criteria may also be specified depending on the job scheduling product interface.

For example: Unicenter CA-7 'Sched Ids' may affect which job names are selected from the job scheduling product data.

9.2.2 Data Set Retention Filters KEEP and DISCARD filters affect which records are added to the ASAP Database from RSP JCL Capture, RSP SMF Capture or Batch SMF Scan. Retention filters do not apply to job collection.

Control statement syntax: {KEEP | DISCARD}_{DSN | VOL | SYSID | UNIT | JOB}(value)

Where: value can be explicitly stated for the category of filter specified or a Mainstar extended ACS filter mask. See the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 9-27).

Normally, all data set records associated with an application are included in the ASAP Database (KEEP being the default). Therefore, DISCARD will be used almost exclusively to limit records written to the ASAP Database. Placing KEEP keywords before DISCARD keywords is equal to the expression 'DISCARD except for'.

Keywords are evaluated in the order entered. The first match terminates the filtering for a specific SMF record.




Example 1: KEEP_DSN(PAYR.**)DISCARD_VOL(SYS*)

In the example above, any data sets from volumes matching 'SYS*' will not be included in the database except for data sets matching 'PAYR.**'.

Example 2: DISCARD_JOB(JOBA)

In the example above, any data sets found in 'JOBA' will not be included in the database.

•

•

JOB(

Caution using KEEP | DISCARD with JOB.

There is a possibility that you may, or may not, KEEP or DISCARD data you intend to by using the KEEP | DISCARD command with the JOB statement. For example, you have two jobs, JOBA and JOBB. The first reference to a data set is in JOBA, and JOBA is the job you DISCARD. You will not see a data set that was referenced in JOBA later on in JOBB because JOBA was the first reference to the data set, and therefore, discarded by the DISCARD_JOB(JOBA) statement. You may also have a data set show up in the database by another job if that job was the first reference. For example, the first reference to a data set is in JOBA. The data set is also referenced in JOBB, but because ASAP identifies the first reference of a data set, if you DISCARD

JOBB) and think the data set was excluded, it would not be. The first reference was in JOBA, and therefore, written to the ASAP Database for JOBA.

The DISCARD option will limit the number of data set records added to the ASAP Database. This may be desirable if unnecessary data sets will be a burden on the database. However, data sets never added can not then be evaluated for inclusion as selection data set entries. Nor will they be included in various reports, losing visibility when researching why data set names do not appear in the ASAP Database.

An alternative is to let data set entries be created in the ASAP Database by using the KEEP option, but exclude them from evaluation with the EVAL/EXCL filters. (See the next topic 'Data Set Evaluation Filters'.)

For new applications, you might start by using Evaluation/Exclude statements to first see which data sets will be excluded using various EXCLude masks. When assured that EXCLude masks will not 'catch' data sets intended to be backed up, change the EXCL filters to DISCARD filters. Filters are entered via Edit panels where you can easily cut, paste, and change all EXCLudes to DISCARDs.




9.2.3 Data Set Evaluation Filters EVAL, EXCL, and EXCL_BUT_CRITICAL filters affect whether data set records that have been collected are to be evaluated for possible inclusion in a selection data set.

Note: Filters take precedence over GDG options.

Control statement syntax: {EVAL | EXCL}_{DSN | VOL | SYSID | UNIT | JOB | DSORG }(value)

{EXCL_BUT_CRITICAL} {DSN | DSN mask}


The valid values for DSORG are:

• IS (ISAM) • DA (direct) • PO (partition) • PS (physical sequential) • VE (VSAM ESDS) • VK (VSAM KSDS) • VL (VSAM LDS) • VR (VSAM RRDS) • VS (VSAM undetermined) • V*, where V* means any VSAM data set

EVALuate Keyword

Once data set names are in the ASAP Database, the default is that they will be evaluated for criticality (determining whether they will be included in the backup selection data set).

Evaluation doesn't imply that a data set will end up becoming an INCLUDE, ALLOCATE, or ACCOMPANY in a selection data set. It merely means that a data set is to be considered by the controls governing the selection of a data set into an application's selection data set.

EXCLude Keyword

EXCL will be primarily used. EVAL is used to force exceptions to EXCL by placing an EVAL before an EXCL.

Rather than DISCARDing data sets from the ASAP Database, you may choose to let data set names from RSP JCL Capture, RSP SMF Capture, or Batch SMF Scan enter the database using KEEP. Then EXCLude them from the selection data set so that an audit trail is available if there are questions about data sets that were not included.

EXCL_VOL Note: An EXCLUDE, or an INCLUDE, VOL filter will be matched against all volumes for a data set. If a data set is multivolume, and a volume matches the VOL statement, the filter action will take place.

EXCL_BUT_CRITICAL Keyword

The EXCL_BUT_CRITICAL filter is provided if both ASAP and Backup & Recovery Manager Suite: All/Star are licensed, and you wish to use the optional features available in the Application Backup and Restore feature of All/Star.




The optional features are:

• Ability to compare ASAP critical data set list against All/Star discovered backups • Ability to restore data sets for ASAP applications and specific cycles within an application • Prove that critical data is backed up

When ASAP is used to create a selection data set in order to drive a post-application backup, it is typical to use EXCLUDE filters to exclude data sets from the backup because the backups are accomplished elsewhere, such as when they are imbedded in the application or another application is backing up the data set.

However, when the All/Star program BKUPEND is run, one of the program's valuable features is to discover and display any critical data sets that are not backed up. For this comparison to encompass all critical data sets, including those you don’t want in a post-application backup, it will be necessary to use EXCL_BUT_CRITICAL to exclude data sets from the selection data set, yet allow them to be compared to All/Star’s discovery of data set backups, and/or if you wish to use the All/Star restore by application feature.

Note: For users with existing ASAP applications, change any EXCLUDE filters to EXCL_BUT_CRITICAL filters if the BKUPEND exception report is desired, and/or if you wish to use the All/Star restore by application feature. This step won’t be necessary if you already solved the problem by excluding your backup jobs from the ASAP job list.

For more information on the Application Backup and Restore feature of All/Star, see Chapter 12, All/Star: Application Backup and Restore of the Backup & Recovery Manager Suite User Guide: All/Star.

9.2.4 How to Accomplish 'KEEP Only' or 'EVAL Only' Sometimes it may prove easier to specify a list of exactly what is desired, rather than of what is not desired using an 'exclusion list'.

This can be accomplished by using a DISCARD or EXCL statement, specifying all data sets, at the end of the filter list.

Example 1: KEEP_DSN(INV*.**)KEEP_DSN(PAYR.**)DISCARD_DSN(**)

In the example above, the KEEP statements identify specific criteria for which data sets are to be added to the ASAP Database. The sequence of the KEEP statements before the DISCARD statement ensures that the desired data sets will be added. All other data sets, signified by DSN(**) on the DISCARD statement, will not be added to the database.




Example 2: EVAL_DSN(INV*.**)EVAL_DSN(PAYR.**)EXCL_DSN(**)

In the example above, the EVAL statements identify specific criteria for which data sets are to be evaluated for possible inclusion in a selection data set. The sequence of the EVAL statements before the EXCL statement ensures that the desired data sets will be evaluated. All other data sets, signified by 'DSN(**)' on the EXCL statement, will not be evaluated for inclusion in a selection data set.

Example 3: EXCL_JOB(JOBA)

In the example above, any data sets found in 'JOBA' will be written to the ASAP Database but EXCLUDED from the application.

•

•

JOB(

Caution using KEEP | DISCARD with JOB There is a possibility that you may, or may not, KEEP or DISCARD data you intend to by using the KEEP | DISCARD command with the JOB statement. For example, you have two jobs, JOBA and JOBB. The first reference to a data set is in JOBA, and JOBA is the job you DISCARD. You will not see a data set that was referenced in JOBA later on in JOBB because JOBA was the first reference to the data set, and therefore, discarded by the DISCARD_JOB(JOBA) statement. You may also have a data set show up in the database by another job if that job was the first reference. For example, the first reference to a data set is in JOBA. The data set is also referenced in JOBB, but because ASAP identifies the first reference of a data set, if you DISCARD

JOBB) and think the data set was excluded, it would not be. The first reference was in JOBA, and therefore, written to the ASAP Database for JOBA.




9.2.5 Data Set Include Filters

INCLude, ACCOMPany, and ALLOCate Keywords

Use these filters when you want to force a data set to be considered critical, or if you want to add other data sets to the selection data set.

Control statement syntax: {INCL | ACCOMP | ALLOC}_{DSN} (value)

{INCL | ACCOMP | ALLOC}_{EXTDSN} (value)

{INCL}_{VOL | SYSID | UNIT | JOB | DSORG}(value)


DSN, VOL, SYSID, UNIT, DSORG, and JOB Categories

Using the INCL (also ACCOMP or ALLOC for DSN) keyword within these categories will make all data sets that match these filters critical. The matching data sets will end up becoming an INCLUDE, ACCOMPANY, or ALLOCATE in a selection data set unless they are not cataloged.

INCL_VOL Note: An INCLUDE, or an EXCLUDE, VOL filter will be matched against all volumes for a data set. If a data set is multivolume, and a volume matches the VOL statement, the filter action will take place.

EXTDSN Category

The EXTDSN category is for including data sets not being evaluated for this application.

• If the data set is not in the ASAP Database, it will be added. • If it exists in the ASAP Database already, the data set is ignored.

Any external data set added to the ASAP Database will be processed like the regular data sets in the database. It can still be excluded if it matches an exclude filter or if it is not cataloged.

Note that the Selection Data Set Build Options (Option 4, Verification) apply to INCL_EXTDSN and ACCOMP_EXTDSN.

For example: An INCL_EXTDSN will be converted to Accompany if the data set is indeed tape and the Build Option 'USER TAPES' is set to 'AS ACCOMPANY'.

How Filters/Controls Work for GDSs & Verification GDG Rules

Following are the rules for how filters/controls work for generation data sets (GDS) in conjunction with Verification GDG rules.

Review of filter types:

• INCL_EXTDSN, ALLOC_EXTDSN and ACCOMP_EXTDSN controls are used to add entries to the ASAP Database for data sets not captured by RSP JCL Capture, RSP SMF Capture or Batch SMF Scan.

• Filters such as INCL_DSN, EXCL_DSN, etc., are used to override normal evaluation, including GDG evaluations.

Rules:

1. Filters may be specified for absolute (G0000V00s) or relative generations (nn). However, a filter for an absolute GDS makes no sense because it would need to be constantly changed, so the following examples assume that filters for specific generations would be specified as relative names.

For example: EXCL_DSN(SAMPLE.GDG(0)).




2. Relative generations must be specified as either 0 or -n with no leading zeros.

For example: Do not specify +0 or -03.

For example: SAMPLE.**(0) is valid.

3. You can use a mask with a relative generation. Relative generation dataset (GDS) filters can only be used as evaluation filters because the match of absolute and relative GDS names cannot be done until all the application jobs are completed. APPLEND processing matches relative and absolute GDS names.

4. Relative filter data set names are matched to both relative and absolute names in the ASAP Database.

For example: The ASAP Database contains SAMPLE.GDG.G0010V00, which is generation 0. A filter of SAMPLE.GDG(0) will match SAMPLE.GDG.G0010V00.

5. A filter can override a GDG rule but can not change the type of GDG name to be used in the selection data set.

For example: If the GDG rule states that new generations are to be excluded, a filter of INCL_DSN(SAMPLE.GDG(0)), assuming that generation zero was a new generation, will force the generation zero data set name to be included. The actual GDG name type (absolute or relative) is still determined by the GDG rules.

6. EXTernal adds of GDSs are subject to the GDG rules – they do not take precedence.

For example: With an INCL_EXTDSN(SAMPLE.GDG(0)) control where generation 0 is a new generation and Setup Option 'ABARS category for new generations' is set to E (exclude), the externally included data set will be excluded because of the GDG rules in effect.

However, non-EXT filters still apply to GDSs so the data set may still be forced to INCLUDE status with an INCL_DSN filter.

For example: INCL_EXTDSN(SAMPLE.GDG(0))

INCL_DSN(SAMPLE.GDG(0))

Whether an INCL_EXTDSN is needed depends on whether the desired generation will be present in the ASAP Database from either RSP JCL Capture or RSP SMF Capture.

Again, the rule for EXT type filters is that they are merely used to add an entry to the ASAP Database. You may need another filter to force the desired category.

Summary of precedence:

1. Non-EXT filters (first filter match takes precedence) 2. GDG rules 3. EXT include category

:

Note: The exception to filters overriding GDG rules is that the name type to be used in the selection data set is fixed by the GDG option (absolute or relative). For example If a filter of INCL_EXTDSN(TEST.GDG(0)) is specified but the GDG option for type of GDS to be used in the selection data set is Absolute, the Include External filter will cause the absolute equivalent data set name to be placed in the ASAP Database.




9.3 Levels of Filters There are three levels of filtering. Data set filtering is controlled by all three – Universal, Global, and Local filters. Job filtering is controlled only by Local filters.

The three levels of filters are:

• Universal – Processed first for absolute control • Global – Applied across all applications • Local – Applied to a specific application

Additionally, even though filters may exist, processing of filters for each collection process may be enabled or disabled for each application via Option 2 (FILTERS) from the ASAP Application AutoBuild Options menu.

9.3.1 Universal Filters Universal filters are always processed, and always processed first. These are intended for absolute control.

For example, those in charge of backing up systems libraries and third-party product libraries, etc., may want to insure that no application can inadvertently back up a data set of this nature and subsequently restore it on top of the version restored by the system backup.

If you are mysteriously missing a data set, check the Universal filters for a match.

Universal filters are DSN, JOB, VOL, UNIT, SYSID, and DSORG.

Note: In post 2.4.01 releases, SAF controls are allowed for Universal filters.

Rules:

1. An ASAP application name of UNIVERSAL is not allowed.




9.3.2 Global Filters Global filters are processed only if desired, and in a relative sequence to application filters as desired. Global filters, being such, are defined in a single place. There is a single list for each category (SYSID, DSN, VOL, UNIT, DSORG, or JOB) and each is either 'on' or 'off' for a specific application.

In the Local application filters, the GLOBAL_xxx keywords are used without values to indicate where global filtering is to occur relative to Local application filters.

Typically, all Global Filters will be specified first.

Example: In this example, any Global KEEPs or DISCARDs will be honored first. If the data set being filtered matches a Global KEEP or DISCARD, the test is terminated with the disposition of the data set determined by which Global filter matched. If no Global filters match, then a data set will be kept unless it matches the local DISCARD filter (a name with REPORT in any qualifier). GLOBAL_SYSIDGLOBAL_DSNGLOBAL_VOLGLOBAL_UNITGLOBAL_JOBDISCARD_(**.*report*.**)

Global filters may be overridden by including the Global filter(s) after a local filter.

Example: In this example, data sets with a low level qualifier of DATA will be EVALuated regardless of whether a GLOBAL filter might have otherwise excluded the data sets from evaluation. EVAL_DSN(**.DATA)GLOBAL_SYSIDGLOBAL_DSNGLOBAL_VOLGLOBAL_UNITGLOBAL_JOB

Rules:

1. An ASAP application name of GLOBAL is not allowed.

9.3.3 Local Filters Local filters are created for individual applications. Local filters are typically processed after any Universal and Global filters. However, to override a Global filter, place it after the Local filter. An example of overriding a Global filter is shown in the previous section. Universal filters can not be overridden.

Note: Universal and Global exclude filters are usually masks that identify groups of data sets not to be included in an application's selection data set. Be sure when you are adding new applications to review the current Universal and Global filters.




9.4 Creating and Displaying Filters

9.4.1 Defining Filters When RSP Is Not Up If you are using Batch SMF, or do not have RSP up, you will receive a notification that RSP is not running:

"RSP not RUNNING"

This notification is a normal message. The filters are in fact saved. However, when RSP is up, the save of the filters propagates them to every image.

9.4.2 Defining Filters to Identify Data Outside 'Mirrored' Volumes To identify data that strayed outside the 'mirrored' volumes, put the mirrored volumes in an EXCL_VOL(volsers) filter. The data ASAP identifies after filtering out the mirrored volumes are the 'exceptions' that you need to take care of.

9.4.3 Including or Excluding Migrated Data You can include or exclude data that is currently migrated.

Control statement syntax:

{ INCL | EXCL }_VOL( MIGRA1 | MIGRA2 )

9.4.4 Creating Universal and Global Filters Universal and Global filters are modified using the following sequence of steps:

STEP

1

DESCRIPTION

Select Option 9 (FILTERS/CONTROLS) from the ASAP Main Menu.

2 Choose Edit or Browse for the desired category from the Global Filtering/Controls Selection panel: • Global Retention or Evaluation section

(for DSN, VOLUME, UNIT, SYSID) • Universal Retention or Evaluation section

3 On the Edit panel that will be displayed, you can either enter the desired keywords with appropriate values or type 'MD' over the '=NOTE=' section to make the note section a data line you can type over. See the example below. mdOTE= DISCARD_DSN(SYS1.COB*) Once the line is a data line, type the data set name you want over the example name.

4 Use PF3 to Save and Return to the Global Filtering/Controls Selection panel or CANCEL to cancel changes.

The steps are shown with sample screen displays on the next page.




Step 1: Select Option 9 (FILTERS/CONTROLS) from the ASAP Main Menu, as shown below.


OPTION ==>

W E L C O M E To:






Step 2: Choose Edit or Browse for the desired category from the Global Filtering/Controls Selection panel, as shown below.

<Vvv.rr> --- A S A P Main Menu ---.----------------- Global Filtering/Controls Selection -----------------.| || Command ==> || || Supply Input; Use ENTER To Change Entries. || Use PF1 For HELP ; Use PF3 To Return. || || || || Global DSN Retention Filters => E (E)dit/(B)rowse || Global VOLUME Retention Filters => (E)dit/(B)rowse || Global UNIT Retention Filters => (E)dit/(B)rowse || Global SYSID Retention Filters => (E)dit/(B)rowse || Global JOB Retention Filters => (E)dit/(B)rowse || || Global DSN Evaluation Filters => (E)dit/(B)rowse || Global VOLUME Evaluation Filters => (E)dit/(B)rowse || Global UNIT Evaluation Filters => (E)dit/(B)rowse || Global SYSID Evaluation Filters => (E)dit/(B)rowse || Global JOB Evaluation Filters => (E)dit/(B)rowse || Global DSORG Evaluation Filters => (E)dit/(B)rowse || || Universal Retention Filters => (E)dit/(B)rowse |96| Universal Evaluation Filters => (E)dit/(B)rowse || |'-----------------------------------------------------------------------'




Global filters are separated into categories (DSN, JOB, VOL, UNIT, DSORG, and SYSID) because within an application you can select Global filters by category for their applicability to the application.

Universal filters are always processed. Valid Universal filters are DSN, JOB, VOL, UNIT, DSORG, and SYSID.

Step 3: On the Edit panel that is displayed, enter the desired keywords with appropriate values or 'MD' over the '=NOTE=' example you want to make the line a data line that you can type over.

In the example below, Edit for Global DSN Retention Filters was selected from the previous panel display.

File Edit Confirm Menu Utilities Compilers Test Help-----------------------------------------------------------------------------EDIT SYS97056.T124127.RA000.XYZ3.R0110328 Columns 00001 00072 Command ===> Scroll ===> CSR ****** ***************************** Top of Data ****************************=NOTE= EDIT GLOBAL RETENTION DSN FILTERS =NOTE= =NOTE= GLOBAL RETENTION FILTERS ARE OF THE FORM: =NOTE= VERB_TYPE(VALUE)=NOTE= WHERE VERB IS: KEEP OR DISCARD =NOTE= WHERE TYPE IS: DSN =NOTE= AND VALUE IS: THE ITEM NAME OR A MASK =NOTE= =NOTE= EXAMPLES: =NOTE= KEEP_DSN(PAYROLL.LIST)=NOTE= DISCARD_DSN(SYS1.COB*)000001 DISCARD_DSN(SYS1.**)****** **************************** Bottom of Data **************************

Values in parentheses may be a complete name, volume etc., or a Mainstar extended ACS filter mask. See the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 9-27).

Notes on Universal and Global filters: Take great care using Universal and Global filters, especially with Retention filters. Make sure that ACS masks are not 'catching' more than intended. Also note that it is an application's option as to whether Global filters are even processed, and if so, whether they are honored before or after local filters.




9.4.5 Modifying Local Application Filters: Retention and Evaluation Filters Local (application level) filters for DSN, EXTDSN, VOLUME, UNIT, SYSID, JOB, or DSORG may be changed or displayed by following these steps:

STEP

1

DESCRIPTION

Select Option 1 (LIST APPLICATIONS), or Option 2 (SELECT/CREATE APPL), from the ASAP Main Menu.

2 From the pop-up panel that is displayed, select or enter an application name.

3 From the Application Menu that will be displayed, Select Option 0 (SETUP).

4 From the Global Applications Setup Options panel that is displayed, enter Y for the Change/Display FILTERING Entries option.

5 From the Application Filter Edit/Browse panel that is displayed, select Evaluation or Retention filters, and specify Edit, Browse, or Overview. E – Edit will display an ISPF Edit panel for the specified filters. B – Browse will display an ISPF Browse panel for the specified filters. O – Overview will present a single view of all Universal, Global and Local Retention/Evaluation filters in effect for the application.

6 If Browse or Overview was specified on the previous panel, then review the entries. If Edit was specified on the previous panel, enter the desired keywords with appropriate values on the Edit panel that is displayed.

7 Use PF3 to Save and Return to the Global Filtering/Controls Selection panel or CANCEL to cancel changes.

The steps are shown with sample screen displays on the next page.




Step 1: Select Option 1 (LIST APPLICATIONS) or Option 2 (SELECT/CREATE APPL) from the ASAP Main Menu.

In the example below, Option 2 (SELECT/CREATE APPL) was selected.


OPTION ==>

W E L C O M E To:






The Select Current/New Application Name panel is displayed.

Step 2: From the pop-up panel that is displayed, select or enter an application name.


OPTION ==> 2 .-------- SELECT Current/NEW Application Name --------.| || Command ==> |

AUT | | ices| SPECIFY Application Name Selection: |

1 - | | ist.2 - | Use Current/OLD Application Name: APPL0001 <= | or Select

| |4 - | -Or- Specify NEW Application Name: <= | tries.6 - | -Or- Select From Application List: N ( Y=List ) |7 - | | s.8 - | Supply Input; Use ENTER To Continue | les.9 - | Use PF1 For HELP ; Use PF3 To Terminate | data.X - '------------------------------------------------------'

Your Last Active Application: APPL0001



--- --


The Application Menu will be displayed.

Step 3: Select Option 2 (FILTERS).

<VvRr.xx> A S A P Application AutoBuild Options -

Option ==>



0 -1 -2 -

SETUP : JOB COLLECT : FILTERS :

Setup Application Options.Collect Application JOB Structure.Application Filters.

2000353/1116


4 - VERIFICATION: Determine Final SEL Data Set Entries. 2001027/09345 - N/A6 - STATUS : Display Current Application's Status.





The Application Filter Edit/Browse panel is displayed.

Step 4: From the Application Filter Edit/Browse panel that is displayed, select Evaluation or Retention filters, and specify Edit, Browse, or Overview.

• E – Edit will display an ISPF Edit panel for the specified filters. • B – Browse will display an ISPF Browse panel for the specified filters. • O – Overview will present a single view of all Universal, Global and Local

Retention/Evaluation filters in effect for the application.

In this example, Edit was selected for the Application EVALUATION Filters.

| || .------------------- APPLICATION FILTER EDIT/BROWSE ------------------.| | || | Command ==> || | Application: APPL0001 || | || | Supply Input; Use ENTER To Change Entries. || | Use PF1 For HELP ; Use PF3 To Return. || | || | Modify JOB Filters/Controls => N ( Y/N ) || | || | Application EVALUATION filters(s) => E (E)dit/(B)rowse/(O)verview || | || | Application RETENTION filters(s) => (E)dit/(B)rowse/(O)verview || | || | || | Current Filter status: || | Global DSN Retentions?=> N Global DSN Evaluations?=> N || | Global VOL Retentions?=> N Global VOL Evaluations?=> N |'--| Global UNIT Retentions?=> N Global UNIT Evaluations?=> N |

| Global SYSID Retentions?=> N Global SYSID Evaluations?=> N || Global JOB Retentions?=> N Global JOB Evaluations?=> N || Global DSORG Evaluations?=> N || |'---------------------------------------------------------------------'




Depending on the action specified on the previous panel, an ISPF Edit or Browse panel, or an Overview panel will be displayed. In the example shown below, Edit was requested on the previous panel, so an ISPF Edit panel is displayed.

Step 5:

• If Browse or Overview was specified on the previous panel, then review the entries. • If Edit was specified on the previous panel, enter the desired keywords with appropriate

values on the Edit panel that is displayed.

EDIT SYS01354.T182311.RA000.BK.R0106861 Columns 00001 00072 Command ===> Scroll ===> PAGE *********************************** Top of Data ******************************=NOTE= ENTER KEYWORDS AND VALUES, FIRST MATCH TAKES PRECEDENCE=NOTE= EVAL_DSN|VOL|SYSID|UNIT|JOB(DISCRETE NAME OR MASK)=NOTE= FORCES EVALUATION IF OTHERWISE WOULD HAVE BEEN EXCLUDED =NOTE= EXCL_DSN|VOL|SYSID|UNIT|JOB|DSORG(DISCRETE NAME OR MASK)=NOTE= FORCES EXCLUSION OF DATA SET FROM ANY SDS CATEGORY =NOTE= EXCL_BUT_CRITICAL(DISCRETE NAME OR MASK)=NOTE= FORCES EXCLUSION OF DATA SET BUT HAS a SPECIAL STATUS =NOTE= INCL_DSN|VOL|SYSID|UNIT|JOB|DSORG (DISCRETE NAME OR MASK)=NOTE= FORCES CATEGORY TO ABARS INCLUDE =NOTE= ALLOC_DSN(DISCRETE NAME OR MASK)=NOTE= FORCES CATEGORY TO ABARS ALLOCATE =NOTE= ACCOMP_DSN(DISCRETE NAME OR MASK)=NOTE= FORCES CATEGORY TO ABARS ACCOMPANY =NOTE= GLOBAL_SYSID =NOTE= GLOBAL_DSN =NOTE= GLOBAL_VOL =NOTE= GLOBAL_UNIT =NOTE= GLOBAL_JOB =NOTE= GLOBAL_DSORG =NOTE= GLOBAL KEYWORDS SPECIFY GLOBALS WILL BE PROCESSED AND =NOTE= ORDER OF PRECEDENCE RELATIVE TO OTHER KEYWORDS =NOTE= FOLLOWING KEYWORDS ALWAYS PROCESSED FIRST =NOTE= INCL_EXTDSN(DISCRETE NAME OR MASK)=NOTE= INCLUDE A DSN NOT NECCESSARILY FOUND IN APPLICATION =NOTE= ALLOC_EXTDSN(DISCRETE NAME OR MASK)=NOTE= ALLOCATE A DSN NOT NECCESSARILY FOUND IN APPLICATION =NOTE= ACCOMP_EXTDSN(DISCRETE NAME OR MASK)=NOTE= ACCOMPANY A DSN NOT NECCESSARILY FOUND IN APPLICATION =NOTE= EXAMPLES: =NOTE= GLOBAL_DSN =NOTE= EXCL_VOL(TSO*)=NOTE= EXCL_DSN(SYS1.**)=NOTE= ALLOC_DSN(**.*EMPTY*.**)=NOTE= INCL_DSN(**.MUSTHAVE.**)=NOTE= INCL_EXTDSN(ABC.ADDTO.DATABASE)




E – Edit Activity

• Values in parentheses may be a complete name or a Mainstar extended ACS filter mask. See the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 9-27).

• Arrangement of keywords is critical. During filter processing, the first match terminates filter processing for a given data set.

• The 'GLOBAL_xxxxx' keywords do not have values. GLOBAL keywords indicate where, if at all, you want GLOBAL filters by category to be evaluated in relation to local filters. It is typical for Global filters to be honored, and processed first.

• '=NOTE=' lines are provided for Global filters. Use the ISPF Edit MD line command to convert these notes into data lines. 'MDMD' is the block command.

O – Overview Activity

Selection O, for Overview, presents a single view of all retention and evaluation filters that are currently in effect for the application.

Again, the first filter match terminates filter processing. Use this display to verify that Universal, Global and Local filters will achieve the desired result.




<Vvv.rr> --- A S A P Application AutoBuild Options -- -

Option ==> 0 .------------------ Application SETUP Options --------------------------.

| Menu Utilities Compilers Help | | -------------------------------------------------------------------- - || BROWSE SYS97056.T125612.RA000.XYZ3.R0110337 Line 00000000 Co || Command ===> Scroll || ******************************** Top of Data ************************ | | || 1 FILTERS || 2 APPL(BK000001) || 3 OVERVIEW || || ASAP FILTERS FOR BK000001 || DISCARD_DSN(BS.ASAPTEST.XYZ) << UNIVERSAL || DISCARD_DSN(RXP.ASAPTEST.**) << UNIVERSAL || DISCARD_DSN(BK.HF*.**) << UNIVERSAL || DISCARD_JOB(TESTJOBS) << UNIVERSAL || || LOCAL RETENTION FILTERS || DISCARD_DSN(BK.TEST.DATA1) << LOCAL || DISCARD_DSN(BK.TEST.DATA3) << LOCAL || DISCARD_DSN(BK.TEST.DATA2) << LOCAL || KEEP_DSN(BK.TEST.DATA0) << LOCAL || DISCARD_DSN(BK.TEST.DATA4) << LOCAL || DISCARD_JOB(PNF*) << GLOBAL || KEEP_SYSID(TRW9) << LOCAL || DISCARD_DSN(BK.HFDG.XFTRTEST) << LOCAL || KEEP_DSN(BK.TRTPTEST.**) << LOCAL || DISCARD_DSN(BP.**) << LOCAL || DISCARD_VOL(TXO*) << GLOBAL || KEEP_VOL(PROD01) << GLOBAL || || LOCAL EVALUATION FILTERS || EXCL_VOL(ZZZZ>>) << GLOBAL || INCL_JOB(*MUST*) << LOCAL || INCL_DSN(**.MUSTHAVE.**) << LOCAL || EXCL_SYSID(MVS*) << GLOBAL || EXCL_DSN(BK.ASAPTEST.GDG7(-1)) << LOCAL || ALLOC_DSN(BK.ASAPTEST.**(-2)) << LOCAL || INCL_VOL(MUST**) << LOCAL || INCL_UNIT(CART) << LOCAL || EXCL_DSN(SYS1.COB*) << GLOBAL || || ******************************* Bottom of Data ********************** | | |

'----------------------------------------------------------------------'

Step 7: Use Enter to submit any change entries. Use PF1 for HELP. Use PF3 to Return to the Application Filter Edit/Browse panel.




9.4.6 Modifying Local Application Filters: Job Collection Local (application level) filters for job collection may be changed or displayed by following these steps:

STEP

1

DESCRIPTION

Select Option 1 (LIST APPLICATIONS) or Option 2 (SELECT/CREATE APPL) from the ASAP Main Menu.

2 From the pop-up panel that is displayed, select or enter an application name.

3 From the Application AutoBuild Options Menu, select Option 2 (FILTERS).

4 From the Application Filter Edit/Browse panel that is displayed, enter Y for Modify Job Collection Filters/Controls. An ISPF Edit panel will be displayed for Job Collection Filters/Controls.

5 On the Edit panel that is displayed, enter INCL_JOB and/or EXCL_JOB entries. INCL_EXTJOB entries may be entered also.

The steps are shown with sample screen displays below.

Job names will be added to the ASAP Database as a result of job collection.

Note: These Local job name filters do not take effect when user-supplied job collection is used.




Step 1: Select Option 1 (LIST APPLICATIONS) or Option 2, (SELECT/CREATE APPL) from the ASAP Main Menu.

In the example below, Option 2 (SELECT/CREATE APPL) was selected.


OPTION ==>

W E L C O M E To:






The Select Current/New Application Name panel is displayed.

Step 2: From the pop-up panel that is displayed, select or enter an application name.


OPTION ==> 2 .-------- SELECT Current/NEW Application Name --------.| || Command ==> |

AUT | | ices| SPECIFY Application Name Selection: |

1 - | | ist.2 - | Use Current/OLD Application Name: APPL0001 <= | or Select

| |4 - | -Or- Specify NEW Application Name: <= | tries.6 - | -Or- Select From Application List: N ( Y=List ) |7 - | | s.8 - | Supply Input; Use ENTER To Continue | les9 - | Use PF1 For HELP ; Use PF3 To Terminate | dataX - '------------------------------------------------------'

Your Last Active Application: APPL0001



--- --


The Application AutoBuild Options Menu will be displayed.

Step 3: Select Option 2 (FILTERS).

<VvRr.xx> A S A P Application AutoBuild Options -

Option ==>



0 -1 -2 -

SETUP : JOB COLLECT : FILTERS :

Setup Application Options.Collect Application JOB Structure.Application Filters.

2000353/1116


4 - VERIFICATION: Determine Final SEL Data Set Entries. 2001027/09345 - N/A6 - STATUS : Display Current Application's Status.


The Application Filter Edit/Browse panel is displayed.

Step 4: From the Application Filter Edit/Browse panel that is displayed, specify Y for Modify JOB Filters/Control.

| | .------------------- APPLICATION FILTER EDIT/BROWSE ------------------.| | || | Command ==> || | Application: APPL0001 || | || | Supply Input; Use ENTER To Change Entries. || | Use PF1 For HELP ; Use PF3 To Return. || | || | Modify JOB COLLECTION Filters/Controls => Y ( Y/N ) || | || | Application EVALUATION filters(s) => (E)dit/(B)rowse/(O)verview || | || | Application RETENTION filters(s) => (E)dit/(B)rowse/(O)verview || | || | || | Current Filter status: || | Global DSN Retentions?=> N Global DSN Evaluations?=> N || | Global VOL Retentions?=> N Global VOL Evaluations?=> N |'__| Global UNIT Retentions?=> N Global UNIT Evaluations?=> N |

| Global SYSID Retentions?=> N Global SYSID Evaluations?=> N || Global JOB Retentions?=> N Global JOB Evaluations?=> N || Global DSORG Evaluations?=> N || |'---------------------------------------------------------------------'




An ISPF Edit panel will be displayed for job filters.

Step 5: On the Edit panel that is displayed, enter INCL_JOB and/or EXCL_JOB entries.

EDIT SYS97132.T165750.RA000.XYZ3.R0105203 Command ===> Scroll ===> CSR ****** ***************************** Top of Data ***************************=NOTE= EDIT JOB FILTERS =NOTE= =NOTE= JOB FILTERS ARE OF THE FORM: =NOTE= =NOTE= =NOTE=

VERB_TYPE(VALUE)WHERE VERB IS: INCL, EXCLWHERE TYPE IS: JOB

=NOTE= AND VALUE IS: THE JOB NAME OR MASK =NOTE= =NOTE= EXAMPLES: =NOTE= =NOTE= =NOTE+

INCL_JOB(PAYR*)EXCL_JOB(PACCTW)

=NOTE= INCLUDE EXTERNAL JOBS ARE OF THE FORM: =NOTE= =NOTE=

INCL_EXTJOB(DISCRETE NAME OR MASK)THIS JOB OR MASK WILL BE INCLUDED IN THE JOB FLAT FILE

=NOTE= IN ADDITION TO JOBS COLLECTED BY OTHER JOB COLLECTION =NOTE= PROCEDURES. =NOTE= =NOTE= EXAMPLES: =NOTE= =NOTE=

INCL_EXTJOB(DISCRJTS)INCL_EXTJOB(TST*)

000001 INCL_JOB(ABC*)****** **************************** Bottom of Data *************************

Modifying the Job Filters

• Values in parentheses may be a complete name or a Mainstar extended ACS filter mask. See the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 9-27).

• Arrangement of keywords is critical. During filter processing, the first match terminates filter processing for a given job name. The INCL_EXTJOB filter is not affected by filter processing. Also, the INCL_EXTJOB filters can be placed anywhere in the filter list.

• Job name filtering is controlled only by Local (application) filters.




9.5 Mainstar Extended ACS Filtering Pattern Masks Many commands allow specification of powerful filtering masks. These filtering pattern masks can be specified with Mainstar extended ACS masking characters, as specified below.

Mask Hex

* (Single)

5C n

wild-card *%

In the example:

PROD* (i.e. *ZREM*

ZREM in its name.

% 6C l % In the example:

are ER6. values

< 4C Similar to the % value, the <

. In the example:

CR, the 3rd and 4th

th and 6th ERallowed.

> 6E only

. In the example:

CR, the 3rd and 4th

th th ERallowed.

** ACS and Only used

for The * or **wild-card

In the example:

st qualifiernd

Description

Represents 0– characters. Can be used before and/or after an item to designate a character position. You can not use an in the middle portion of a single

item (except for data set names). Use the character (see below) for that purpose.

*PROD an item is selected if the last four characters are regardless of the starting characters. Using the character before and after an item ) means that item is to be selected if any character string matches

Denotes a single character placeholder value, which can be alpha-numeric or any specia character. The character can be used in any position order.

CRM%%ER6 an item is to be selected if it is 8-characters in length and the first three characters

CRM and the last three characters are The two middle placeholdercan be any characters.

character denotes a placeholder value for only alpha characters The < character can be used in any position order.

CR<<ER* an item is to be selected if the first two characters are characters must be alpha, the 5 characters are , and any remaining characters

Similar to the % value, the > character denotes a placeholder value fornumeric characters The > character can be used in any position order.

CR>>ER* an item is to be selected if the first two characters are characters must be numeric, the 5 and 6 characters are , with any remaining characters

(Double) 5C5C

Allows compatibility with standard DFSMSdss filtering masks. partially qualified data set names. characters can be used in any

qualifier position to denote a node.

CRFM*.*VER.** a data set entry is to be selected if it has at least two qualifiers and the 1starts with CRFM, the 2 qualifier must end with VER, and any remaining qualifiers.

Note: As with common data set name masking, any combination of *, **, %, < and/or > characters can be used for the item mask value.




Mask Hex

! 5A Similar to the % !

The !

@ # $

Description

value, the character denotes a placeholder value for only national characters (based on the U.S.A. EBCDIC code set, see topic 'Your EBCDIC Code Tables – Specification and Display of EBCDIC Characters', page 9-28). character can be used in any position order. National characters (based on the U.S.A. EBCDIC code set) are:

9.6 Your EBCDIC Code Tables – Specification and Display of EBCDIC Characters

Data supplied as input to batch programs or input to ISPF panels:

For Mainstar product code shipped in binary, when specifying input where the product takes special action based on specific characters, the user is responsible for entering the EBCDIC character peculiar to their code tables that results in the binary value for the EBCDIC character shown in this document according to the U.S.A. EBCDIC code set.

For instance, if an exclamation mark ( ! ) is called for, and your code tables do not translate the ! character to a hexadecimal 5A, you must enter the character that will translate to a 5A.

Do not change Mainstar distributed ISPF panels:

Mainstar programs may reference ISPF panel attribute bytes. A panel change involving an attribute byte will not be consistent with the program code.

Product output:

Depictions of product output shown in the product manuals are based on the U.S.A. EBCDIC code set. Actual output may vary if your EBCDIC code tables are different.

9.7 Reviewing the Results of Application Filtering You can review the results of filtering activities for an application using one of the following screen displays:

• LIST APPLICATIONS, Option 1 from the ASAP Main Menu • Application STATUS, Option 6 from the Application AutoBuild Options menu • The active VERIFICATION event, Option 4 from the Application AutoBuild Options menu




9.8 Filtering Tips

Tip Tip Description

1 There are three levels of filters, Universal, Global, and Local. Universal are processed first and Global normally second, although it depends on placement within the Local filters when it was enabled. Local filters (for individual applications) are processed after any Universal filters and typically after Global Filters. Filters are processed using drop-through logic; the first 'hit' of a filter that matches a data set's name is the one used.

2 Global Filters are optional and processed in a relative sequence to local application filters. If the GLOBAL_DSN is enabled and is in the Local filter list before any local filters, then Global Filters take precedence. Exceptions to Global Filters should be placed in front of GLOBAL_DSN.

3 Job name filters do not apply if job names are entered manually via job collection using the ISPF Edit option. Job name filters have no affect on INCL_EXTJOB filters.

4 KEEP and DISCARD filters affect which records are added to the ASAP Database.

5 EVAL and EXCL filters affect whether a data set record collected is to be evaluated for possible inclusion in the selection data set.

6 INCL_DSN, ACCOMP_DSN and ALLOC_DSN keywords are used to FORCE a data set into the selection data set that would otherwise be in another category.

7 EXTDSN causes an external data set to be brought into the database for evaluation, NOT automatic inclusion into the selection data set. To FORCE the data set into a selection data set, you must either use an INCL_DSN, ACCOMP_DSN or ALLOC_DSN filter statement.

8 Filters for generation data sets can be either absolute (g0000v00) or relative(nn). However, a filter for an absolute GDS makes no sense because it would need to be constantly changed.

9.9 Using Optional OpenTech VDR Filter Lists ASAP allows you to use the OpenTech Virtual Data Recovery (VDR) filter list to exclude selected tape data sets. That exclusion list will be processed after the normal ASAP filters.

If you have VDR and wish to invoke the VDR filters during the APPLEND processing, simply add a DD statement to the APPLEND job or PROC similar to the following: //VDRPATT DD DISP=SHR,DSN=VDR filter DSN

There is no ASAP setup option for this optional filter. It can only be invoked with the DD statement above. Additionally, the VDR filter list is not invoked during ASAP Foreground or Background Verify.




Appendix A A Batch JCL and Control Statement Reference

This quick reference describes the control statement keywords and cataloged procedure JCL parameters used to direct and initiate various collection and auditing events in ASAP.

Contents:

• APPLEND – RSP Application-End Control Statements – page A-2

• ASPC7JOB – Unicenter CA-7 Job Collection Procedure – page A-5

• ASPCM606 – CONTROL-M Job Collection Procedure – page A-6

• ASPESPEX – Cybermation ESP Job Collection Procedure – page A-7

• ASPJBTCV – Unicenter CA-Jobtrac Job Collection Procedure – page A-8

• ASPTWJOB – TWS Job Collection Procedure – page A-9

• ASPJOBZK – ASG-Zeke Job Collection Procedure – page A-10

• ASPPRECV – Pre-Staged Data Set Job Collection Procedure – page A-11

Mainstar Software Corporation ©2006 A-1 Appendix A SC23-6059-00 Batch JCL and Control Statement Reference



A.1 APPLEND – RSP Application-End Control Statements APPLEND informs the Real-time Selection Process (RSP) when an application is completed. Insert APPLEND either as the last job or as a step of the last job.

APPLEND is a member of the ASAP JCL library.

Figure A-1: APPLEND JCL Procedure

//JOBCARD JOB ,'APPLEND',CLASS=?,MSGCLASS=?*---------------------------------------------------------------* //* THIS JOB, PLACED AT THE END OF AN APPLICATION JOB STREAM, * //* TRIGGERS THE UPDATE OF THE ASAP DATABASE AND THE BUILDING OF * //* OF A SELECTION DATASET FOR A SUBSEQUENT BACKUP VIA ABARS ETC. *//* MAKE SURE THE APPLNAME PASSED AS A PARM IS CORRECT. * //* IF THIS PROGRAM COMPLETES WITH A ZERO RETURN CODE, THE ASAP * //* UPDATE AND SELECTION DATASET BUILD PROCESS WAS SUCCESSFUL. * //*---------------------------------------------------------------*//APPLEND PROC //APPLEND EXEC PGM=APPLEND,PARM=APPL(APPLNAME)//* SELREBUILD(DEFAULT)/NOSELREBUILD//* CYCLEINC(DEFAULT)/CYCLENOINC//* DELETEDETAIL/NODELETEDETAIL(DEFAULT)//STEPLIB DD DISP=SHR,DSN=&LOAD//SISLOAD DD DISP=SHR,DSN=&LOAD//ASPINVDB DD DISP=SHR,DSN=&ASAPDB//MSGLOG DD DISP=SHR,DSN=&LOG//SISPARM DD DISP=SHR,DSN=&PARMLIB(BRMINI)//SYSPRINT DD SYSOUT=&SOUT//SYSOUT DD SYSOUT=&SOUT // PEND //APPLEND EXEC APPLEND

To edit the APPLEND JCL:

• Specify the application name in the PARM field of the EXEC statement. The command syntax and parameter descriptions are shown below.

• Specify the ASAP LOAD library name. 'APPL(applname),[SELREBUILD | NOSELREBUILD, CYCLEINC | CYCLENOINC,

DELETEDETAIL | NODELETEDETAIL]'

Appendix A A-2 Mainstar Software Corporation ©2006 Batch JCL and Control Statement Reference SC23-6059-00



APPL= ( ),

[ |

|

DELETEDETAIL |]

applname – |

l

(s) for

same.

data will not be available if the verification feature is desired.

default.

PARAMETER DESCRIPTION

applname

SELREBUILD NOSELREBUILD, CYCLEINC CYCLENOINC,

NODELETEDETAIL

The ASAP application name. SELREBUILD NOSELREBUILD – Optional parameter keyword(s) for rebuilding an application's selection data set entries. Using the SELREBUILD keyword (which is the default if omitted) will rebuild the application's se ection data set after the ASAP Database update process has been completed. Using the NOSELREBUILD keyword will bypass rebuilding the application's selection data set entries. CYCLEINC | CYCLENOINC – Optional parameter keywordincreasing the cycle number. Using the CYCLEINC keyword (which is the default if omitted) will increase the cycle number by 1. This option should be chosen for most applications. Using the CYCLENOINC keyword will keep the cycle number the

DELETEDETAIL | NODELETEDETAIL – The DELETEDETAIL keyword causes the DSD records for the application to be deleted after the selection data set has been successfully created and the APPLEND ended with a return code zero. If the APPLEND return code is greater than zero, the DSD records will not be deleted. If the DSD records are removed, a full cycle of

The NODELETEDETAIL keyword does not delete the DSD after the selection data set is created. NODELETEDETAIL is the

Example 1: //APPLEND EXEC PGM=APPLEND,

// PARM='APPL(APPL0001),CYCLEINC'

In Example 1, application APPL0001 will have its cycle number increased by one and also have its current selection data set re-built with the current entries.

Example 2: //APPLEND EXEC PGM=APPLEND,

// PARM='APPL(PRODPAY),NOSELREBUILD'

In Example 2, application PRODPAY will have its cycle increased by one, but its selection data set will not be re-built.




A.1.1 APPLEND Errors If RSP APPLEND produces a non-zero return code, the associated errors are written to the console log and to the SYSPRINT DD.

If a specific SMF record was not captured by RSP SMF Capture, the reason could be that the data set was opened but not closed before APPLEND was encountered. SMF type 14/15 records are generated when a data set is closed.

A.1.2 Selection Data Set Output When using the ABARS format for the selection data set, normally the selection data set category written by ASAP 'Excluded due to Normal Evaluation' is for the rerun option.

Exception: When 'All Data Sets are Critical' option is set to support forward recovery and GDG base names are read (not generation data set), the base names are put in the 'Excluded due to Normal Evaluation' category because ABARS won't allow GDG base names in the INCLUDE list, only the ALLOCATE list.




A.2 ASPC7JOB – Unicenter CA-7 Job Collection Procedure A listing of the ASPC7JOB cataloged procedure JCL member for Unicenter CA-7 job collection is provided in this section.

( ), applname – the ASAP application name.


PARM= applname

Symbolic parameters in the ASPC7JOB cataloged procedure are automatically resolved with values provided in the BRMINI PARMLIB member.

This JCL can be found and copied by going into the ISPF panels for this job scheduler. See the topic 'Job Collection with Unicenter CA-7 Job Management' (page 4-10), for information on the ISPF panels.

Below is a JCL example for the ASPC7JOB procedure.

Figure A-2: ASPC7JOB JCL Procedure

//MSJOBCA7 JOB ,'CA7 JOB COLLECT',CLASS=A,MSGCLASS=X//*//*//*//JCLL JCLLIB ORDER=(BRM0601.TEST.JCL)// EXEC CA73BTI //BTERM.SYSPRINT DD DISP=OLD,DSN=MS.EMTEST9.CA7OUTPT,// DCB=BLKSIZE=1330 //BTERM.SYSIN DD */LOGON ICNAME,ICPASSFSTRUC,JOB=(MSTEST),LIST=ALL,TYPE=ALL,SCHID=1LJOB,JOB=MSTEST//*//* APPL NAME = EMTEST9 //* JOB TYPE = CA7 JOB COLLECTION //* SUBMIT = BY MS ON 10/11/2006 09:03:19//*// IF (RC < 5 ) THEN//JOBCA7 EXEC ASPC7JOB,APPL=EMTEST9,// RPT=MS.EMTEST9.CA7OUTPT// ENDIF// IF (RC < 5 ) THEN//JOBCOLL EXEC ASPJOBSQ// ENDIF




A.3 ASPCM606 – CONTROL-M Job Collection Procedure A listing of the ASPCM606 cataloged procedure JCL member for CONTROL-M is provided in this section.



PARM= applname

Symbolic parameters in the ASPCM606 cataloged procedure are automatically resolved with values provided in the BRMINI PARMLIB member.

This JCL can be found and copied by going into the ISPF panels for this job scheduler. See the topic 'Job Collection with CONTROL-M' (page 4-16) for information on the ISPF panels.

Below is a JCL example for the ASPCM606 procedure.

Figure A-3: ASPCM606 JCL Procedure

//MSJOBWGJ JOB ,'ASAP',CLASS=A,MSGCLASS=X//*//*//*//JCLL JCLLIB ORDER=(BRM0601X.TEST.JCL)//CTLM PROC DISK=SYSDA,// SOUT='*' //S1 EXEC PGM=IEFBR14 //DD01 DD DSN=&&TEMP,UNIT=&DISK,SPACE=(0,0)//SYSUDUMP DD SYSOUT=&SOUT //DAJOB DD DSN=USER.PROCLIB,DISP=SHR//DAREPORT DD SYSOUT=&SOUT // PEND// EXEC CTLM//DAREPORT DD DISP=SHR,DSN=MS.EMTEST9.CLMOUTPT//DAJOB DD DISP=SHR,DSN=FILE1(NAME1)// DD DISP=SHR,DSN=FILE4(NAME4)//*//* APPL NAME = EMTEST9 //* JOB TYPE = CLM JOB COLLECTION //* SUBMIT = BY MS ON 10/12/2006 09:51:19//*// IF (RC < 5 ) THEN//JOBCM EXEC ASPCM606,APPL=EMTEST9,// MPGMI=ASPCM500,// RPT=MS.EMTEST9.CLMOUTPT// ENDIF// IF (RC < 5 ) THEN//JOBCOLL EXEC ASPJOBSQ// ENDIF




A.4 ASPESPEX – Cybermation ESP Job Collection Procedure A listing of the ASPESPEX cataloged procedure JCL member for Cybermation ESP is provided in this section.



PARM= applname

Symbolic parameters in the ASPESPEX cataloged procedure are automatically resolved with values provided in the BRMINI PARMLIB member.

This JCL can be found and copied by going into the ISPF panels for this job scheduler. See the topic 'Job Collection with Cybermation ESP' (page 4-27) for information on the ISPF panels.

Below is a JCL example for the ASPESPEX procedure.

Figure A-4: ASPESPEX JCL Procedure

//MSJOB JOB ,'ASAP',CLASS=A,MSGCLASS=X//*//*//*//JCLL JCLLIB ORDER=BRM0601X.TEST.JCL //STEP1 EXEC ASPESPEX,EPGMI=ASPEI530// IF (RC < 5 ) THEN//ESPJB EXEC ASPESJOB,APPL=EMTEST9// ENDIF// IF (RC < 5 ) THEN//JOBCOLL EXEC ASPJOBSQ// ENDIF




A.5 ASPJBTCV – Unicenter CA-Jobtrac Job Collection Procedure

A listing of the ASPJBTCV cataloged procedure JCL member for Unicenter CA-Jobtrac is provided in this section.



PARM= applname

Symbolic parameters in the ASPJBTCV cataloged procedure are automatically resolved with values provided in the BRMINI PARMLIB member.

This JCL can be found and copied by going into the ISPF panels for this job scheduler. See the topic 'Job Collection with Unicenter CA-Jobtrac' (page 4-31) for information on the ISPF panels.

Below is a JCL example for the ASPJBTCV procedure.

Figure A-5: ASPJBTCV JCL Procedure

//MSJOBBQV JOB ,'ASAP',CLASS=A,MSGCLASS=X//*//*//*//JCLL JCLLIB ORDER=(BRM0601X.TEST.JCL)//ASPJBT EXEC ASPJBTCV,APPL=EMTEST9,// SELJOBS=MS.ASAP.EMTEST9.JOBTRAC,// JBTJOBS=MS.JOBTRAC.FILE1// IF (RC < 5 ) THEN//JOBCOLL EXEC ASPJOBSQ// ENDIF




A.6 ASPTWJOB – TWS Job Collection Procedure

A listing of the ASPTWJOB cataloged procedure JCL member for TWS Job Collection is provided in this section.



PARM= applname

Symbolic parameters in the ASPTWJOB cataloged procedure are automatically resolved with values provided in the BRMINI PARMLIB member.

This JCL can be found and copied by going into the ISPF panels for this job scheduler. See the topic 'Job Collection with TWS' (page 4-41) for information on the ISPF panels.

Below is a JCL example for the ASPTWJOB procedure.

Figure A-6: ASPTWJOB JCL Procedure

//MSJOB7BH JOB ,'ASAP',CLASS=A,MSGCLASS=X//*//*//*//JCLL JCLLIB ORDER=(BRM0601X.TEST.JCL)//ASPTWS EXEC ASPTWJOB,// APPL=EMTEST9,// TWSDATE=10/12/2006// IF (RC < 5 ) THEN//JOBCOLL EXEC ASPJOBSQ// ENDIF




A.7 ASPJOBZK – ASG-Zeke Job Collection Procedure A listing of the ASPJOBZK cataloged procedure JCL member for ASG-Zeke Job Collection is provided in this section.



PARM= applname

Symbolic parameters in the ASPJOBZK cataloged procedure are automatically resolved with values provided in the BRMINI PARMLIB member.

This JCL can be found and copied by going into the ISPF panels for this job scheduler. See the topic 'Job Collection with ASG-Zeke' (page 4-44) for information on the ISPF panels.

Below is a JCL example for the ASPJOBZK procedure.

Figure A-7: ASPJOBZK JCL Procedure

//MSJOBERD JOB ,'ASAP',CLASS=A,MSGCLASS=X//*//*//*//JCLL JCLLIB ORDER=(BRM0601X.TEST.JCL)//STEP1 EXEC PGM=IEFBR14 //DD02 DD DSN=ZEKEUTL.AMPZEKE.FILE,// DISP=(MOD,DELETE),// UNIT=SYSALLDA,SPACE=(0,0)//STEP1 EXEC ZEKEUTL //SYSIN DD DISP=SHR,// DSN=PARM_ZEKE(ZEKEUTIL)//AMPZEKE DD DSN=ZEKEUTL.AMPZEKE.FILE,// DISP=(,CATLG),// UNIT=SYSALLDA,SPACE=(CYL,(10,10),RLSE)//STEP2 EXEC ASPZI450,ZPGMI=ASPZI510// IF (RC < 5 ) THEN//JOBZK EXEC ASPJOBZK,ZPGM=ASPZK450,APPL=EMTEST9// ENDIF// IF (RC < 5 ) THEN//JOBCOLL EXEC ASPJOBSQ// ENDIF




A.8 ASPPRECV – Pre-Staged Data Set Job Collection Procedure

A listing of the ASPPRECV cataloged procedure JCL member for Pre-Staged Data Set job collection is provided in this section.



PARM= applname

Symbolic parameters in the ASPPRECV cataloged procedure are automatically resolved with values provided in the BRMINI PARMLIB member.

This JCL can be found and copied by going into the ISPF panels for this job scheduler. See the topic 'Job Collection with Pre-Staged Data Set' (page 4-51) for information on the ISPF panels.

Below is a JCL example for the ASPPRECV procedure.

Figure A-8: ASPPRECV JCL Procedure

//MSJOBNO5 JOB ,'ASAP',CLASS=A,MSGCLASS=X//*//*//*//JCLL JCLLIB ORDER=(BRM0601X.TEST.JCL)//ASPPRE EXEC ASPPRECV,APPL=EMTEST9,// PRESTAGE=BK.TEST.PRESTAGE.PDS(EMTEST9)// IF (RC < 5 ) THEN//JOBCOLL EXEC ASPJOBSQ// ENDIF




Appendix B B ASAP Reports and Utilities

The JCL for these ASAP reports and utilities programs is located in the product JCL library.

Contents:

• ASAPDSRS – Data Set Name Report – page B-2

• ASAPOVLP – ASAP Overlap Report – page B-6

• ASPFLTRP – Filter Report – page B-9

• ASPCHKDB – DSD Record Count Report – page B-10

• ASPMNT01 – Rename an ASAP Application – page B-11

• ASPAPPCP – Copy an ASAP Application – page B-12

• ASPFILTR – Batch Filter Processing – page B-14

• ASPDELAP – Delete Application – page B-20

Mainstar Software Corporation ©2006 B-1 Appendix B SC23-6059-00 ASAP Reports and Utilities



B.1 ASAPDSRS – Data Set Name Report The ASAPDSRS report provides data set name and inclusion / exclusion information from the last successful cycle.

When ASAP collects JCL and RSP SMF data, it stores that raw data in the Data Set Detail Records (DSD). As part of the application end (APPLEND), these records are analyzed and Data Set Records (DSR) are created. These records can be found by running the ASAPDSRS report, or by selecting an ASAP application, selecting Option 6 (STATUS), followed by Option 5 (Display Current JCL/SMF DSN Entries). New DSR records are created only during the next APPLEND.

ASAPDSRS creates a flat file data set that can be browsed through ISPF. You cannot print this report because each data line is greater than 237 characters in length, which won't fit on most printers, even as landscape. The files do not have 'page' breaks or 'page' headers. There is a single header at the top of each file, which is not repeated for each page.

Member ASAPDSRS can be found in the product JCL library.

Modify symbolic parameter ASAPDSRS to an output data set name of your choice where the report will be written.


applname – The ASAP application name. PARM= (applname), Using the 'PARM=applname', you get entries just for that

application. If PARM=applname is not specified, the report will contain all DSRs for all applications.

To use this parameter, you must type it in the JCL. See the example below.

JCL Example:

********************************* Top of Data *********************************//JOB NAME JOB ,'...',CLASS=?,MSGCLASS=?//ASAPDSRS PROC ASAPDB=AMP.QABETA.ASAPDB,// DISK=SYSALLDA,// ASAPDSRS=ASAP.DSN.OUTFILE,// LOAD=AMP.QABETA.LOAD,// PARMLIB=AMP.QABETA.PARMLIB,// SOUT='*' //S1 EXEC PGM=IEFBR14 //DD01 DD DSN=&ASAPDSRS,UNIT=&DISK,DISP=(MOD,DELETE),SPACE=(0,0)//S2 EXEC PGM=ASAPDSRS,PARM=applname//STEPLIB DD DSN=&LOAD,DISP=SHR//ASAPDB DD DSN=&ASAPDB,DISP=SHR//DSRS DD DSN=&ASAPDSRS,UNIT=&DISK,DISP=(,CATLG),// SPACE=(CYL,(10,10),RLSE)//SISPARM DD DSN=&PARMLIB(BRMINI),DISP=SHR//SYSOUT DD SYSOUT=&SOUT //SORTMSG DD SYSOUT=&SOUT //SYSUDUMP DD SYSOUT=&SOUT // PEND //ASAPDSRS EXEC ASAPDSRS******************************** Bottom of Data *******************************

Appendix B B-2 Mainstar Software Corporation ©2006 SC23-6059-00 ASAP Reports and Utilities


____________________________________________ ________ _____________ ____________

1


Report Example:

********************************* TOP OF DATA ********************************** ASAP DSNAMES FROM AMP.QAVvRrxx.ASAPDB 01/10/2004DSNAME APPLNAME ASAP STATUS EVALUATION S

ABARS.EM.ISPPLIB EMTEST3 EXC ALWAYS EXC-FILTERED ABARS.EM.LOAD EMTEST3 EXC ALWAYS EXC-FILTERED ABARS.EM.PACKED EMTEST3 EXC ALWAYS EXC-FILTERED ABARS.EM.TRANS EMTEST3 EXC ALWAYS EXC-FILTERED ABARS.XYZ.LOAD APPL0001 INC CRITICAL INC

APPL0002 UNKNOWN -NOT EVAL APPL0004 UNKNOWN -NOT EVAL

AMP.ABARSMGR.IVP.A003.DATA IVP INC CRITICAL INC AMP.ABARSMGR.IVP.A004.DATA IVP INC CRITICAL INC AMP.ABARSMGR.IVP.A005.DATA IVP EXC NON-CRIT EXC AMP.ABARSMGR.IVP.A005.NEWNAME IVP EXC NON-CRIT EXC AMP.ABARSMGR.IVP.A006.DATA IVP EXC NON-CRIT EXC AMP.ABARSMGR.IVP.A007.DATA IVP INC CRITICAL INC AMP.ABARSMGR.IVP.A100.DATA IVP INC ALLOC INC AMP.ABARSMGR.IVP.GDG.G0002V00 IVP EXC NON-CRIT EXC-UNCATLG AMP.ABARSMGR.IVP.GDG.G0003V00 IVP EXC NON-CRIT EXC



______ __________ ______________ ____________________________________________ __


Scrolling to the right:

********************************* TOP OF DATA ********************************** 0:28:54 TATUS FLTR SCOPE FLTR TYPE FILTER LA

LOCAL EXCL DSN ABARS.** 19 LOCAL EXCL DSN ABARS.** 19 LOCAL EXCL DSN ABARS.** 19 LOCAL EXCL DSN ABARS.** 19

19 UATED 19 UATED 19

19 19 19 19 19 19 19 19 19

Scrolling to the right again:

********************************* TOP OF DATA ********************************** LAST UPDATE JCL SMF SMF ACCS JOB NAME SMF JOBN SMF DATE SYSID UNIT VOLSER _________________ ___ ___ ________ ________ ________ ________ _____ ____ ______ 2001.016 19:22:05 *** OLD INPUT ******** EMABKP 2001.004 P390 DASD TSO001 2001.016 19:22:05 *** OLD INPUT ******** EMABKP 2001.004 P390 DASD TSO001 2001.016 19:22:05 *** OLD INPUT ******** EMALC 2001.004 P390 DASD PROD01 2001.016 19:22:05 *** OLD INPUT ******** EMABKP 2001.004 P390 DASD TSO002 2000.302 16.15.17 *** OLD INPUT ASPTST02 2000.302 P390 DASD TSO001 2001.041 14:57:06 SHR *** ******** XYZTST2* ******** ******** P390 DASD TSO001 2001.054 15:56:22 SHR *** ******** XYZTST2* ******** ******** P390 DASD TSO001 2001.071 15.47.18 SHR OLD INPUT TSTJOB02 TSTJOB02 2001.071 P390 DASD TSO001 2001.071 15.47.19 SHR OLD INPUT TSTJOB02 TSTJOB02 2001.071 P390 DASD TSO001 2001.067 12.53.03 *** OLD RENAME TSTJOB02 2001.067 P390 DASD TSO001 2001.067 12.53.03 *** NEW RENAME TSTJOB02 2001.067 P390 DASD ****** 2001.067 12.53.55 OLD OLD DELETE TSTJOB02 TSTJOB02 2001.067 P390 DASD TSO001 2001.071 15.47.26 NEW OLD DELETE TSTJOB03 TSTJOB02 2001.071 P390 DASD TSO001 2001.071 15.47.19 OLD OLD OUTPUT TSTJOB02 TSTJOB02 2001.071 P390 DASD TSO001 2001.067 12.47.11 *** OLD INPUT TSTJOB01 2001.067 P390 **** ****** 2001.067 12.48.15 *** NEW OUTPUT TSTJOB01 2001.067 P390 DASD TSO001




ASAP STATUS / EVALUATION STATUS Descriptions for ASAPDSRS Report

ASAP STATUS / DESCRIPTION EVALUATION STATUS

ADD NEW Data set added by user. May be matched with any ASAP status.

INC Include (critical). Matched with ASAP status of INC CRITICAL or GDG BASE NAME.

INC ALWAYS Data set included (critical) regardless of normal evaluation process. GDG data sets and filtered data sets may fall into this category.

INC ACCOM Critical Tape data set (user choice whether Tape data sets are includes or accompany).

INC-ADD NEW Data set added by user. May be matched with any include (critical) ASAP status.

INC ALLOC Critical data sets that must be present for recovery but are not backed up.

INC CRITICAL Critical data set to be backed up.

INC CRITICAL INC - Add New Setup for Rerun Recovery but 'FR if new GDS' was set to Y.

INC - INC-FORCE Included regardless of normal evaluation process (GDG data set processing or hit on include filter). Matched with INC ALWAYS.

EXC Excluded. Matched with EXC NON-CRIT.

EXC ALWAYS Data set excluded by other than normal evaluation process. This could result from a filter hit, the data set is uncataloged, relative GDGs when absolute are requested, and vice versa.

EXC-FILTERED Hit on exclude filter. Matched with ASAP status of EXC ALWAYS.

EXC-FORCE Excluded regardless of normal evaluation process (GDG data set processing). Matched with EXC ALWAYS.

EXC NON-CRIT Non-critical data set. It is not critical from 'normal evaluation'. For Rerun Recovery, these would be output files.

EXC-UNCATLG Excluded not cataloged. Matched with EXC NON-CRIT.

GDG BASE NAME GDG BASE data set must be present for recovery.

UNKNOWN - NOT EVALUATED This could occur from records built but not yet evaluated.



____________________________________________ ________ _____________ ____________


B.2 ASAPOVLP – ASAP Overlap Report The ASAPOVLP report shows data set overlaps within the ASAP Database. ASAPOVLP creates a flat file data set that can be browsed through ISPF. It is not a report you can print because each data line is greater than 237 characters in length, which won't fit on most printers, even as landscape. The files do not have 'page' breaks or 'page' headers. There is a single header at the top of each file, which is not repeated.

Member ASAPOVLP can be found in the product JCL library.

Modify symbolic parameter 'ASAPOVLP' to an output data set name of your choice where the report will be written.

The overlap report uses data set records (DSRs) for input. Data set records are those that have already been analyzed and created by APPLEND or VERIFICATION. The currently running cycle creates data set detail (DSD) records. Running cycles are not contained in the Overlap report.

Important Note: RSPJRFSH should be run any time you make changes to the job names or create new applications.

Report Example:

********************************* TOP OF DATA ********************************** ASAP OVERLAPPING DSNAMES FROM AMP.QAVvRrxx.ASAPDB 01/10/2004DSNAME APPLNAME ASAP STATUS EVALUATION S

ABARS.XYZ.LOAD APPL0001 INC CRITICAL INC APPL0002 UNKNOWN -NOT

EVAL APPL0004 UNKNOWN -NOT

EVAL

AMP.QABETA.LOADEVAL

DSTEST UNKNOWN -NOT

DS5 UNKNOWN -NOT EVAL

DS6 INC CRITICAL INC

AMP.QAVvRrxx.RSP.MESSAGEQEVAL

APPL0002 UNKNOWN -NOT

APPL0004 UNKNOWN -NOT EVAL



1

______ __________ ______________ ____________________________________________ __


Scrolling to the right:

********************************* TOP OF DATA ********************************** 0:02:03 TATUS FLTR SCOPE FLTR TYPE FILTER LA

19 UATED 19 UATED 19

UATED 19 UATED 19 UATED 19

LOCAL EXCL DSN AMP.** 19 19

UATED 19 UATED 19

19

UATED 19 UATED 19

Scrolling to the right again:

********************************* TOP OF DATA ********************************** LAST UPDATE JCL SMF SMF ACCS JOB NAME SMF JOBN SMF DATE SYSID UNIT VOLSER _________________ ___ ___ ________ ________ ________ ________ _____ ____ ______ 2000.302 16.15.17 *** OLD INPUT ASPTST02 2000.302 P390 DASD TSO001 2001.041 14:57:06 SHR *** ******** XYZTST2* ******** ******** P390 DASD TSO001 2001.054 15:56:22 SHR *** ******** XYZTST2* ******** ******** P390 DASD TSO001

2001.041 14:57:06 SHR *** ******** XYZTST2* ******** ******** P390 DASD TSO002 2001.054 15:56:22 SHR *** ******** XYZTST2* ******** ******** P390 DASD TSO002 2001.037 11:44:57 SHR *** ******** TSTJOB00 ******** ******** P390 DASD TSO002 2001.036 06.19.42 SHR OLD INPUT TSTJOB10 TSTJOB10 2001.036 P390 DASD TSO002 2001.085 09:48:41 SHR *** ******** TSTJOB10 ******** ******** P390 DASD SCPMV5

2001.037 11:44:57 SHR *** ******** TSTJOB00 ******** ******** P390 DASD PROD01 2001.037 14:21:21 SHR *** ******** TSTJOB10 ******** ******** P390 DASD PROD01 2001.085 09:48:41 SHR *** ******** TSTJOB10 ******** ******** P390 DASD TSO001

2001.041 14:57:06 SHR *** ******** XYZTST2* ******** ******** P390 DASD P390DX 2001.054 15:56:22 SHR *** ******** XYZTST2* ******** ******** P390 DASD P390DX




ASAP STATUS / EVALUATION STATUS Descriptions for ASAPOVLP Report

ASAP STATUS / DESCRIPTION EVALUATION STATUS

ADD NEW Data set added by user. May be matched with any ASAP status.

INC Include (critical). Matched with ASAP status of INC CRITICAL or GDG BASE NAME.

INC ALWAYS Data set included (critical) regardless of normal evaluation process. GDG data sets and filtered data sets may fall into this category.

INC ACCOM Critical tape data set (user choice whether tape data sets are includes or accompany).

INC-ADD NEW Data set added by user. May be matched with any include (critical) ASAP status.

INC ALLOC Critical data sets that must be present for recovery but are not backed up.

INC CRITICAL Critical data set to be backed up.

INC CRITICAL INC - Add New Setup for Rerun Recovery but 'FR if new GDS' was set to Y.

INC - INC-FORCE Included regardless of normal evaluation process (GDG data set processing or hit on include filter). Matched with INC ALWAYS.

EXC Excluded. Matched with EXC NON-CRIT.

EXC ALWAYS Data set excluded by other than normal evaluation process. This could result from a filter hit, the data set is uncataloged, relative GDGs when absolute are requested, and vice versa.

EXC-FILTERED Hit on exclude filter. Matched with ASAP status of EXC ALWAYS.

EXC-FORCE Excluded regardless of normal evaluation process (GDG data set processing). Matched with EXC ALWAYS.

EXC NON-CRIT Non-critical data set. It is not critical from 'normal evaluation'. For Rerun Recovery, these would be output files.

EXC-UNCATLG Excluded not cataloged. Matched with EXC NON-CRIT.

GDG BASE NAME GDG BASE data set must be present for recovery.

UNKNOWN - NOT EVALUATED This could occur from records built but not yet evaluated.




B.3 ASPFLTRP – Filter Report The ASPFLTRP report lists the filters for all applications in the ASAP Database.

Member ASPFLTRP can be found in the product JCL library.

JCL Example:

//ASPFLTRP JOB ,'ASAP FILTERS',CLASS=A,MSGCLASS=X,// NOTIFY=&SYSUID,REGION=0M//JOBNAME JOB ,'...',CLASS=?,MSGCLASS=?//ASPFLTRP PROC ASAPDB=AMP.QABETA.ASAPDB,// LOAD=AMP.QABETA.LOAD,// PARMLIB=AMP.QABETA.PARMLIB,// SOUT='*' //* CREATES a REPORT BY APPLICATION OF ALL ASAP FILTERS//S1 EXEC PGM=ASPFLTRP //STEPLIB DD DISP=SHR,DSN=&LOAD//ASPINVDB DD DISP=SHR,DSN=&ASAPDB//SISPARM DD DISP=SHR,DSN=&PARMLIB.(BRMINI)//SYSPRINT DD SYSOUT=&SOUT //SYSUDUMP DD SYSOUT=&SOUT //ASPFLTRP EXEC ASPFLTRP// PEND //FILTERS EXEC ASPFLTRP

Report Example:

APPL0001 RETENTION FILTERS

DISCARD_DSN(SYS1.COB*)DISCARD_DSN(RMP.CNTL)

EVALUATION FILTERS EXCL_JOB(RMP<*)EXCL_DSN(RMP.**)

EXTERNAL FILTERS INCL_EXTDSN(P390#2.BACKUP.EH0002.G0192V00)

DS6 RETENTION FILTERS

DISCARD_DSN(AMP.QABETA.**)

EXXAPL01 EVALUATION FILTERS

GLOBAL_DSN




B.4 ASPCHKDB – DSD Record Count Report The ASPCHKDB utility reports the number of Data Set Detail (DSD) records in each application. This utility does not report on records captured via Batch SMF.

Member ASPCHKDB can be found in the product JCL library.

Modify the SYSIN statement for the application(s) you are interested in. If you do not specify an application, ASPCHKDB will give you a list of all applications found in the ASAP Database.

JCL Example:

********************************* Top of Data **********************************//ASPCHKDB PROC//* ASPCHKDB CAN BE USED TO CHECK THE NUMBER OF DSD RECORDS//* ASSOCIATED WITH AN ASAP APPLICATION.//*//STEP1 EXEC PGM=ASPCHKDB //STEPLIB DD DISP=SHR,DSN=&LOAD//ASAPDB DD DISP=SHR,DSN=&ASAPDB//SISPARM DD DISP=SHR,DSN=&PARMLIB(BRMINI)//SYSPRINT DD SYSOUT=&SOUT //SYSUDUMP DD SYSOUT=&SOUT //SYSIN DD * DSD -

APPL(APPLNAME)******************************** Bottom of Data ********************************

Other SYSIN examples:

DSD APPL(A*,R*) DATE(2000140)

Report example:

APPLICATION DSD RECORD COUNTS RUN DATE: 2003.133

APPL0001 CURRENT CYCLE: 454 EARLIEST: 2000.045 LATEST: 2000.132 PRIOR CYCLES: 766

APPL0002 CURRENT CYCLE: 84 EARLIEST: 2000.079 LATEST: 2000.133 PRIOR CYCLES: 0




B.5 ASPMNT01 – Rename an ASAP Application The ASPMNT01 program renames an ASAP application to another name.

Member ASPMNT01 can be found in the product JCL library.

Follow the Control Card instructions within the ASPMNT01 JCL to rename an application.

Steps to Rename an ASAP Application:

STEP

1

STEP DESCRIPTION

Ensure the application you are renaming to does not exist.

2 Run ASPMNT01 to rename the ASAP application.

3 Go into Option 0 (Setup) for the new application and change the ABARS aggregate name (if applicable) and selection data sets.

4 Run RSPJRFSH to update the job table.

Note: After ASPMNT01 has completed, run RSPJRFSH to update the job table. Otherwise, RSP will generate messages about the old application name. RSPJRFSH should be run any time you make changes to the job names or create new applications.

JCL Example:

The following is an example of a job from the ASAP JCL library to rename an application from APPL0001 to APPL0002.

//JOBNAME JOB ,'...',CLASS=?,MSGCLASS=?//ASPMNT01 PROC SOUT='*',// ASAPDB=??,// LOAD=??,// PARMLIB=?? //S1 EXEC PGM=ASPMNT01 //STEPLIB DD DISP=SHR,DSN=&LOAD//ASAPDB DD DISP=SHR,DSN=&ASAPDB//SISPARM DD DISP=SHR,DSN=&PARMLIB(BRMINI)//SYSPRINT DD SYSOUT=&SOUT //SYSIN DD DUMMY // PEND //ASPMNT01 EXEC ASPMNT01//S1.SYSIN DD * // RENAME (APP(APPL0001) NEWNAME(APPL0002))




B.6 ASPAPPCP – Copy an ASAP Application The ASPAPPCP program copies or clones ASAP application setup information from a source application to one or more target applications. Only Option 0 (Setup) application information is copied. Job collection and filter information are not copied from the source application.

Member ASPAPPCP can be found in the product JCL library.

|APP(target3...)


COPY APPLICATION APPL| source target1 target2

Copies a source application setup options to one or more target applications. Multiple copy commands can be in one job. The 'source' specifies the setup options you will be copying from. The 'target' is the new application that will be created using the source application setup option data.

To use this parameter, you must type it in the JCL. An example of the JCL is provided on the following page.




JCL Example:

********************************* Top of Data *********************************//JOBNAME JOB ,'...',CLASS=?,MSGCLASS=?//ASPAPPCP PROC//S1 EXEC PGM=ASPAPPCP //STEPLIB DD DSN=&LOAD,DISP=SHR//ASPINVDB DD DSN=&ASAPDB,DISP=SHR//SYSPRINT DD SYSOUT=&SOUT //SYSOUT DD SYSOUT=&SOUT //SYSIN DD DUMMY // PEND //S1 EXEC ASPAPPCP //S1.SYSIN DD * COPY APPL -

( -APPL0001 - SOURCE APPLICATION APPL0002 - TARGET APPLICATION APPL0003 - TARGET APPLICATION )

******************************** Bottom of Data *******************************

Rules:

1. ABARS users – an ABARS aggregate definition must be created and active in SMS for the new or copied target aggregate before executing the ASPAPPCP copy program. This provides ASAP with the capability to find the new selection data set name in the SMS address space and automatically place it into the new or copied target ASAP application so it doesn't need to be manually changed later.

2. The ASPAPPCP program only supports using the same selection data set name for both RSP and VERIFY.

3. Non-ABARS users – at this time there is no way to insert a new selection data set name during the copying process.

Note: After ASPAPPCP has completed and the setup options have been copied, perform the normal steps including job collection, RSPJRFSH, APPLEND, and optional filters.




B.7 ASPFILTR – Batch Filter Processing Batch filter processing uses commands and keywords to update ASAP filters.

Member ASPFILTR can be found in the product JCL library.

FILTERS Command Keyword Summary:

Scope: keyword. following will be for Universal filters.

Scope: keyword. following will be for Global filters.

) ASAP application name All parameters following will be for Local filters.

(retention filters) (filter)

i

(filter)

).

and External.

Note: All filter actions must begin with FILTERS in the command. For examples of the syntax, see the topic 'Syntax Examples', later in this appendix.

FILTERS COMMAND KEYWORD KEYWORD VALUES KEYWORD DESCRIPTION

UNIVERSAL None All parameters

Mutually exclusive with Global and Application.

GLOBAL None All parameters

Mutually exclusive with Universal and Application.

APPLICATION(applname Scope: keyword.

Mutually exclusive with Universal and Global.

RETENTION Retention filters: Discard_DSNDiscard_Job(filter) Discard_Vol(filter) Discard_Unit(filter) Discard_Sys d(filter) Keep_DSN(filter) Keep_JobKeep_Vol(filter) Keep_Unit(filter) Keep_Sysid(filter)

Filter type (see Chapter 9, FILTERS – Using Filters and ControlsMutually exclusive with Evaluation

These values may be used with Universal, Global, or Application keywords.

Global_DSN Global_Job Global_Vol Global_Unit Global_Sysid

These values may only be used with the Application keyword. They 'turn on' the specified global retention filter set for the application.





EVALUATION(evaluation filters) Evaluation filters: Eval_DSN(filter) Eval_Job(filter) Eval_Vol(filter) Eval_Unit(filter) Eval_Sysid(filter) Incl_DSN(filter) Incl_Job(filter) Incl_Vol(filter) Incl_Unit(filter) Incl_Sysid(filter) Excl_DSN(filter) Excl_Job(filter) Excl_Vol(filter) Excl_Unit(filter) Excl_Sysid(filter)

Filter type (see Chapter 9, FILTERS – Using Filters and Controls). Mutually exclusive with Retention and External. These values may be used with the Universal, Global, or Application keywords.

Alloc_DSN(filter) Accomp_DSN(filter) Global_DSN Global_Job Global_Vol Global_Unit Global_Sysid

These values may only be used with the Application keyword. Alloc or Accomp values are added to the application’s evaluation filter set. The Global values 'turn on' the specified set of global filters for the application.

EXTERNAL(external filters) External filters: Incl_EXTDSN(filter) Alloc_EXTDSN(filter) Accomp_EXTDSN(filter)

Filter type (see Chapter 9, FILTERS – Using Filters and Controls). This keyword and its values can only be used with the Application keyword.

JOB_COLLECT(job collection filters)

Job collection filters: Incl_Job(filter) Excl_Job(filter)

Filter type (see Chapter 9, FILTERS – Using Filters and Controls). This keyword and its values can only be used with the Application keyword. Job collection filters are only used in job collection processing (see Chapter 9, FILTERS – Using Filters and Controls).

RETENTION_DSN(dataset name) RETENTION_DDN(ddname)

Data set name of filter list DD name of filter list

Filter lists can be stored in a data set. The data set LRECL must be 80 and the filters must start in column 2.

EVALUATION_DSN(dataset name) EVALUATION_DDN(ddname)







EXTERNAL_DSN(dataset name) EXTERNAL_DDN(ddname)



JOB_COLLECT_DSN(dataset name) JOB_COLLECT_DDN(ddname)



RETENTION_DEL(parm value) All, DSN, Job, Vol, Unit and Sysid

Delete retention filters. DSN, Job, Vol, Unit, and Sysid are only valid for Global filters. For all other deletes, the value All is required.

EVALUATION_DEL(parm value) All, DSN, Job, Vol, Unit and Sysid

Delete evaluation filters. DSN, Job, Vol, Unit, and Sysid are only valid for Global filters. For all other deletes, the value All is required.

EXTERNAL_DEL(parm value) All Delete External filters. All is only valid value. This keyword may only be used with the Application keyword.

JOB_COLLECT_DEL(parm value) All Delete External filters. All is only valid value. This keyword may only be used with the Application keyword.

OVERVIEW None Report shows all the filters in ASAP Database that apply to a specified ASAP application. Universal filters are shown and Global filters are shown for the Global types enabled for that application.

REPLACE None When REPLACE is specified, the new filter list replaces existing filters in ASAP Database. Mutually exclusive with Add_First and Add_Last.

ADD_FIRST ADD_LAST

None When Add_First keyword is specified, the new filters are added before existing filters. When Add_Last keyword is specified, the new filters are added after existing filters. Mutually exclusive with Replace.




JCL Example:

//JOBNAME JOB ,’…’,CLASS=?,MSGCLASS=?//ASPFILTR PROC//FILTERS EXEC PGM=ASPFILTR //STEPLIB DD DISP=SHR,DSN=&LOAD//XYXPRINK DD SYSOUT=* //SYSOUT DD SYSOUT=* //ASPINVDB DD DISP=SHR,DSN=&ASAPDB//FILTERDD DD DSN=&&FILTWORK,// DISP=NEW,// UNIT=&DISK,// DCB=(LRECL=80,BLKSIZE=14400,RECFM=FB),// SPACE=(TRK,(10,1),RLSE)//XYXIN DD DUMMY // PEND //FILTERS EXEC ASPFILTR//FILTERS.XYXIN DD *

Syntax Examples:

Delete Universal Retention Filters – Example 1

This example deletes all existing Universal Retention filters.

//FILTERS.XYXIN DD *

FILTERS -

UNIVERSAL -

RETENTION_DEL( -

ALL -

)

Delete Global DSN Evaluation Filters – Example 2

This example deletes all existing Global_DSN filters.


FILTERS -

GLOBAL -

EVALUATION_DEL( -

DSN -

)




Update Local (Application) Evaluation Filters – Example 3

This example replaces any Local (application level) filters, with the Include, Exclude, and Eval filters shown, and turns on the Global_DSN list of filters – all for ASAP application Test42.


FILTERS -

APPLICATION(Test42) -

EVALUATION( -

INCL_JOB(TESTJOB1) -

EXCL_JOB(TESTJOB*) -

GLOBAL_DSN -

EVAL_DSN(LOCAL.**.TEST) -

) -

REPLACE

Update Global DSN and Job Evaluation Filters – Example 4

The first part of this example replaces any GLOBAL_JOB evaluation filters with the three filters shown. The second part inserts the two GLOBAL_DSN filters ahead of any existing Global Evaluation DSN filters.


FILTERS -

GLOBAL -

EVALUATION( -

INCL_JOB(TESTJOB1) -

EXCL_JOB(TESTJOB*) -

EVAL_JOB(PRODJOB) -

) -

REPLACE

FILTERS -

GLOBAL -

EVALUATION( -

INCL_DSN(PROD.DATASET.X1) -

EXCL_DSN(PROD.DATASET.**) -

) -

ADD_FIRST




Update Universal Retention Filters (Using DATASET) – Example 5

This example adds a Universal Retention DSN filter after any current Universal Retention DSN filters.


FILTERS -

UNIVERSAL -

RETENTION_DSN( -

UNIV.FILTER.DATASET -

) -

ADD_LAST

Update Local (Application) Retention Filters (Using DDNAME) and External Filters and Do Overview – Example 6

The first part of this example replaces any Application (local) Retention filters with the filters found in the specified data set. The second FILTERS command replaces any external DSN references for application TEST42 with the filter shown. The final command generates a filter overview report for that application.

//RFILTER DD DSN= TEST.FILTER.DATASET,DISP=SHR


FILTERS -

APPLICATION(TEST42) -

RETENTION_DDN( -

RFILTER -

) -

REPLACE

FILTERS -


EXTERNAL( -

INCL_EXTDSN(PROD.TEST42.XTA(0) -

) -

REPLACE

FILTERS -


OVERVIEW




B.8 ASPDELAP – Delete Application The ASPDELAP utility deletes an application and all its related records in the ASAP Database including filter entries.

Member ASPDELAP can be found in the product JCL library.

WARNING: If you have a large number of deletions (more than a few applications) ASPDELAP should be executed at a low activity time.



PARM= applname Using the 'PARM=applname', data is deleted just for that

application.

To use this parameter, you must type it in the JCL. See the example below.

JCL Example:

//JOBNAME JOB ,'...',CLASS=?,MSGCLASS=?//ASPDELAP PROC ASAPDB=AMP.QABETA.ASAPDB,// LOAD=AMP.QABETA.LOAD,// PARMLIB=AMP.QABETA.PARMLIB,// SOUT='*'//* ASPDELAP WILL DELETE AN ASAP APPLICATION FROM THE ASAP DB.//* THE APPLICATION'S FILTERS WILL BE DELETED.//*//S1 EXEC PGM=ASPDELAP,PARM=applname//STEPLIB DD DISP=SHR,DSN=&LOAD//ASPINVDB DD DISP=SHR,DSN=&ASAPDB//SISPARM DD DISP=SHR,DSN=&PARMLIB.(BRMINI)//SYSPRINT DD SYSOUT=&SOUT//SYSUDUMP DD SYSOUT=&SOUT//ASPDELAP EXEC ASPDELAP// PEND//DELETE EXEC ASPDELAP

Note: After ASPDELAP has completed, run RSPJRFSH to update the job table. Otherwise, RSP may generate messages about the deleted application name. RSPJRFSH should be run any time you make changes to the job names or create new applications.




Index

A ABARS

selection criteria ............................................... 8-16 ACCOMPANY ...2-8, 3-6, 3-15, 3-19, 6-3, 6-9, 7-7, 9-6 All/Star

application backup and restore........................... 9-6 using ASAP with................................................. 9-6

ALLOCATE .......2-8, 3-6, 3-15, 3-19, 6-3, 6-9, 7-7, 9-6 anchor jobs ...........................................................1-11 APPLEND ................................................ 7-6, 7-7, 7-8

non-zero return code ................................. 7-10, A-4 application

backup and restore............................................. 9-6 backup selection criteria ..................................... 1-3 batch SMF scan ................................................. 5-3 checklist usage................................................. 1-12 contact person.................................................. 1-10 identify reference points ................................... 1-11 information (dialog / batch) ................................. 8-1 job collection process

overview ..........................................................4-2 using ASG-Zeke ............................................4-44 using CONTROL-M .......................................4-16 using Cybermation ESP.................................4-27 using ISPF Edit ..............................................4-49 using pre-staged data set ..............................4-51 using TWS .....................................................4-41 using Unicenter CA-7.....................................4-10 using Unicenter CA-Jobtrac...........................4-31 using user-supplied data set..........................4-56

listing by name (Option 1 displays).............. 2-4, 8-2 processing cycles, identification ................ 1-16, 5-2 setup, application description ............................. 3-6

Application AutoBuild Options menu Option 0 - SETUP........................................ 2-7, 3-1 Option 1 - JOB COLLECT ........................... 2-7, 4-2 Option 2 - FILTERS ............................................ 2-7 Option 4 - VERIFICATION........................... 2-8, 6-2 Option 6 - STATUS ..................................... 2-8, 8-7

application copyASPAPPCP ...................................................... B-12

Application SETUP Options panel Application General Setup section ..................... 3-6 Batch SMF Scan Options section..................... 3-13 Collection Options section ................................ 3-10 Current Verifications Options section ............... 3-14 JCL Options section ......................................... 3-12 Job Collection Options section ........................... 3-8 RSP Options section ........................................ 3-11 Selection Data Sets section.............................. 3-30

ASAP main menu.......................................................... 2-2 overview ...................................................... 1-1, 1-3 preparation ....................................................... 1-10 preparation checklist ........................................ 1-12

ASAP database.......................................................1-6

backing up ........................................................ 7-23 reorganizing...................................................... 7-23

ASAP Main Menu ....................................................2-2 Option 1 - LIST APPLICATIONS .......... 2-3, 2-4, 8-2 Option 2 - SELECT/CREATE APPL ............ 2-3, 2-5 Option 3 - RSP MONITOR ................................. 2-3 Option 5 - SMF SCAN SETUP .................... 2-3, 2-9 Option 8 - ERROR MESSAGES.................. 2-4, 2-9 Option 9 - FILTERS/CONTROLS .............. 2-4, 2-10

ASAPDSRS data set name report .......................................... B-2

ASAPOVLP overlap report .....................................................B-6

ASPAPPCP utilitycopy application................................................ B-12

ASPC7JOB ............................................................ A-5 ASPCHKDB report

DSD record count ............................................. B-10 ASPDELAP utility

delete application.............................................. B-20 ASPFILTR

batch filter processing....................................... B-14 ASPFLTRP

filter report ..........................................................B-9 ASPMNT01 utility

rename application ........................................... B-11 assign alternate CA-7 SCHID values ....................4-13 auditing

auditing application changes ............................ 1-33 Real-time Selection Process (RSP).................... 7-2

B backing up the ASAP database.............................7-23 Backup & Recovery Manager................................1-10 BACKUP CYCLES TO RETAIN ............................3-29 Backup Options section.........................................3-29 batch application copy

ASPAPPCP ...................................................... B-12 batch filter processing

ASPFILTR ........................................................ B-14 batch job submission

batch control statements .................................... A-1 JCL members ..................................................... A-1 JCL review screen ............................................ 1-34 overview ........................................................... 1-34

binary value for EBCDIC character .......................9-28

C CA-7 job schedulers ..............................................4-10 CONTROL-M job scheduling product....................4-16 copy application

ASPAPPCP ...................................................... B-12 copy process

new selection data set name ............................ B-13 count DSD records

ASPCHKDB...................................................... B-10 Cybermation ESP job scheduling product .............4-27

Mainstar Software Corporation ©2006 i Index SC23-6059-00


16


D data set name report

ASAPDSRS ....................................................... B-2 data sets

adding data set entries to an application.............6-8 audit using RSP JCL Capture .............................7-2 audit using RSP SMF Capture ............................7-2 identify using batch SMF scan ............................5-3

define an application to ASAP ................................ 3-1 delete application

ASPDELAP ...................................................... B-20 dialog screens

Application Information (Application List) ............8-6 Application List

Application Information type ............................ 8-6 Browse Selection Data Set Contents ................8-16 display Current JOB Anchor Chains....................8-9 display Current JOB List .....................................8-8 display Data Set Detail Records........................8-10 display Summary of Last RSP Selection Data Set 8

filters & controls (by application) .......................2-10 JCL review screen.............................................1-34

display PF keys ........................................................2-4, 8-2

DSD record count ASPCHKDB ..................................................... B-10

E EBCDIC code tables ............................................. 9-28 email address ............................................................ 3 end-of-application (APPLEND) ............................... 7-8 ESP job scheduling product.................................. 4-27 EVALuate keyword ................................................. 9-6 EXCL filter............................................................... 9-4 EXCL_BUT_CRITICAL keyword............................. 9-6 EXCLUDE.............................. 2-8, 3-6, 3-15, 4-61, 6-3 EXCLude keyword .................................................. 9-6

F filter keywords

data set evaluation EVAL ............................................................... 9-6

data set retention KEEP, DISCARD............................................. 9-4

Jobname INCLude, EXCLude ......................................... 9-4

filter report ASPFLTRP ........................................................ B-9

filters batch filter processing ...................................... B-14 categories ...........................................................9-3 create & display local (application) filters ..........9-16 create & display local jobname filters ................9-23 create & display universal & global filters..........9-13 data set retention ................................................9-4 DSN ....................................................................9-4 EXCL...................................................................9-4 EXTDSN, External Data Set Name .....................9-9 filter processing in batch .................................. B-14 GDSs and verification GDG rules........................9-9 global level ........................................................9-12

INCL ....................................................................9-4 jobname ..............................................................9-4 'KEEP only' & 'EVAL only' ...................................9-7 levels of .............................................................9-11 local (application) level ......................................9-12 masks for pattern filtering ..................................9-27 overview ..............................................................9-2 review the results of ..........................................9-28 SYSID .................................................................9-4 types of................................................................9-4 UNIT....................................................................9-4 universal level ...................................................9-11 VDR......................................................... 7-10, 9-29 VOL .....................................................................9-4

forward recovery .....................................................1-6 step-by-step setup.............................................1-21

G GDG data sets

set up for an application ....................................3-21

IIEFUJI ...................................... See RSP JCL Capture INCL

filter .....................................................................9-4 INCLUDE 2-8, 3-6, 3-14, 3-15, 4-61, 6-2, 6-3, 6-8, 6-9,

7-7, 9-6 Internet address ......................................................... 4 ISPF interface .........................................................1-3

view messages..................................................1-36 view product messages.....................................1-36

J JCL capture............................... See RSP JCL capture JCL collection........................... See RSP JCL Capture

display Data Set Detail Records........................8-10 set up for an application ....................................3-12 using RSP IEFUJI exit.........................................7-2

JCL members......................................................... B-1 APPLEND ................................................... 7-8, A-2 ASAPDSRS........................................................ B-2 ASAPOPC.................A-6, A-7, A-8, A-9, A-10, A-11 ASAPOVLP ........................................................ B-6 ASPAPPCP...................................................... B-12 ASPC7JOB ........................................................ A-5 ASPCHKDB ..................................................... B-10 ASPDELAP ...................................................... B-20 ASPFILTR ........................................................ B-14 ASPFLTRP......................................................... B-9 ASPMNT01 ...................................................... B-11 RSP members ...................................................7-10 RSPBLDJB........................................................7-10 RSPJRFSH .......................................................7-10 RSPJSWAP ......................................................7-10 RSPSETUP.......................................................7-10 RSPSMFTK.......................................................7-10

job collection assign alternate CA-7 SCHID values ................4-13 filtering

mask values...................................................4-61 identify anchor jobs and structures....................1-10 identify job entries .............................................1-10 job collection options pop-up panel .....................4-6

Index ii Mainstar Software Corporation ©2006 SC23-6059-00



job entry input using ISPF Edit ..............................................4-49 using pre-staged data set ..............................4-51 using user-supplied data set..........................4-56

job name filtering during ................................... 4-61 Options section in SETUP .................................. 3-8 overview .................................................... 1-14, 4-2 preparing for ..................................................... 1-10 RSP requirement................................................ 7-5 supported job scheduling products..................... 4-2 Unicenter CA-Jobtrac

loading an alternate forecast .........................4-33 user-supplied job entries .................................... 4-2 with ASG-Zeke job scheduler product .............. 4-44 with CONTROL-M job scheduler product ......... 4-16 with ESP job scheduler product........................ 4-27 with Jobtrac job scheduler product ................... 4-31 with TWS ................................................. 4-41, 4-43 with Unicenter CA-7 job scheduler ................... 4-10

job entry input using ISPF Edit................................................. 4-49 using pre-staged data set ................................. 4-51 using user-supplied data set............................. 4-56

job name filtering during job collection.......................................... 4-61

Job Statement Verification panel..................1-34, 5-11 Job Submission Preferences panel..............1-34, 5-11

K keywords

ASPFILTR ........................................................ B-14 Keywords, AMPINI

ASAPOPC ........................................................ A-11 keywords, BRMINI

application libraries LOAD1...........................................................7-12 LOAD2...........................................................7-12

ASG-Zeke job scheduling product configuration and global options ....................4-44

ESP job scheduling product configuration and global options ....................4-27

Job Pre-Stagedconfiguration and global options ....................4-52

RSP AutoStart........................................................7-19 Dspc_Buffers .................................................7-18

verification, global options ................................ 6-14 keywords, job collection

STRUC ............................................................. 4-58

L log files

RSP message log file ....................................... 7-11

M main menu ..............................................................2-2 Mainstar

how to contact us ...................................................3 message log file ....................................................7-11 messages

view from MESSAGES message text members1-36 view using ISPF interface ................................. 1-36

MESSAGES

view messages ................................................. 1-36 mirroring support .....................................................1-5 monitor overflow....................................................7-25 monitor RSP processing........................................7-12 monitoring application changes.............................1-33 multi-image..............................................................7-6

O OPC/ESA

cataloged procedure, ASAPOPC A-6, A-7, A-8, A-9, A-10, A-11

OpenTech VDR filters ...........................................7-10 operational considerations

back up or reorg ASAP database w/RSP up .... 7-23 normal IPL ........................................................ 7-23 RSP IPL considerations - shutdown ................. 7-23 RSP IPL considerations - startup...................... 7-23 RSPJRFSH and the internal job table .............. 7-24 selection data sets must be physical sequential (PS)

...................................................................... 7-23 surviving a system outage ................................ 7-24

using Record Level Sharing)..........................7-24 overflow

monitoring......................................................... 7-25 overlap report

ASAPOVLP ........................................................ B-6

P panel attribute bytes ..............................................9-28 PFSHOW

turn off ......................................................... 2-4, 8-2 phone numbers ..........................................................3

R Real-time Selection Process (RSP)

APPLEND....................................................7-8, A-2 avoiding trouble w/RSP cycles.........................7-4

JCL members ................................................... 7-10 job reference table.............................................. 7-6

refresh (RSPJRFSH) .......................................7-6 message log ..................................................... 7-11

viewing...........................................................7-11 operational considerations

back up or reorg ASAP database w/RSP up..7-23 normal IPL .....................................................7-23 RSP IPL considerations - shutdown ..............7-23 RSP IPL considerations - startup...................7-23 RSPJRFSH and the internal job table............7-24 selection data sets must be physical sequential

(PS)............................................................7-23 surviving a system outage .............................7-24

using Record Level Sharing ....................7-24 overview ............................................................. 7-2 performance & usage notes ............................... 7-4 preparing for RSP data collection ....................... 7-5

rename application ASPMNT01....................................................... B-11

reorganizing the ASAP database ..........................7-23 reports .................................................................... B-1

data set name report ASAPDSRS, ................................................... B-2

DSD record count ASPCHKDB .................................................. B-10

Mainstar Software Corporation ©2006 iii Index SC23-6059-00



filter report ASPFLTRP......................................................B-9

online status displays ..........................................8-7 overlap report

ASAPOVLP .....................................................B-6 rerun recovery......................................................... 1-6

step-by-step setup.............................................1-27 RSP

overview..............................................................1-8 See Real-time Selection Process (RSP) .............7-2

RSP JCL Capture ................................................... 2-9 overview..............................................................7-2 records processing..............................................7-3 set up for an application ....................................3-12 setting up the application ....................................7-2 viewing captured records ....................................7-3

RSP monitor ......................................................... 7-12 RSP SMF Capture

overview..............................................................7-2 records processing..............................................7-3 setting up the application ....................................7-2

RSP tasks RSPSMFTK ........................................................7-6

RSPBLDJB ........................................................... 7-10 RSPJRFSH........................................................... 7-10 RSPJSWAP .......................................................... 7-10 RSPSETUP .......................................................... 7-10 RSPSMFTK ...................................................7-6, 7-10

operator commands ..........................................7-18

S selection criteria (ABARS)

ACCOMPANY .....................................................6-3 ALLOCATE .........................................................6-3 EXCLUDE ...........................................................6-3 INCLUDE ............................................................6-3

selection data sets allocation...........................................................3-30 create (verification)..............................................6-1 create in foreground ............................................6-5 generate entries ..................................................6-2 identify to ABARS SMS aggregate group............6-3 naming ..............................................................3-30 output formats .....................................................6-9 output selection formats ......................................6-4 review results of verification ..............................6-13 selection criteria (ABARS)...................................6-3 set up for an application ....................................3-14

SETUP ....................................................................3-1 single image............................................................7-6 SMF capture ........................... See RSP SMF Capture SMF collection

collection overview ............................................1-15 display Data Set Detail Records........................8-10 dynamically using RSP IEFU83 exit ....................7-2 required SMF record types..................................5-3 review results of batch SMF scan .....................5-12 RSP SMF Capture...............................................7-2 set up for an application, batch .........................3-13

status displays ........................................................8-7 submit ASAP batch jobs .........................................3-1

T Tivoli Workload Scheduler (TWS) .........................4-41

batch report .......................................................4-43

U U.S.A. EBCDIC code set ......................................9-28 UJI ........................................... See RSP JCL Capture Unicenter CA-7

cataloged procedure, ASPC7JOB ...................... A-5 Unicenter CA-7 job scheduling product.................4-10 utilities .................................................................... B-1

copy application ASPAPPCP .................................................. B-12

delete application ASPDELAP................................................... B-20

rename application ASPMNT01................................................... B-11

V

VDR filters....................................................7-10, 9-29 verification

adding data set entries to an application .............6-8 create the selection data set .............................1-18 global options in BRMINI...................................6-14 options used during RSP.....................................7-5 output selection data set formats ........................6-9 reviewing results

list screens.....................................................6-13 scheduling application backups...........................6-8

W web site address ........................................................ 4

Index iv Mainstar Software Corporation ©2006 SC23-6059-00


Technical Support Mainstar Technical Support

Product Information [email protected]

Visit Our Web Site

www.mainstar.com

Worldwide Headquarters and North and South America Sales Mainstar Software Corporation P.O. Box 4132 Bellevue, WA 98009 U.S.A. Tel: 1-425-455-3589 or 1-800-233-6838 Fax: 1-425-455-1992

European Sales Mainstar Software Corporation Ltd. Sanderum House Oakley Road Chinnor Oxon OX39 4TW England Tel: +44-(0)1844-347173 Fax: +44-(0)1844-346627

Asia Pacific Sales Mainstar International Ltd. P.O. Box 1624 Macquarie Centre North Ryde, NSW 2113 Australia Tel: +61-(0)2-9888-1777 Fax: +61-(0)2-9888-1588

http://www.mainstar.com/services/support/techsupport/index.asp


http://www.mainstar.com/

backup & recovery manager suite user guide:...

Documents