unicenter ca-7 job management

Unicenter®

CA-7™ Job Management

Commands Guide r11 SP2

Third Edition

This documentation (the “Documentation”) and related computer software program (the “Software”) (hereinafter collectively referred to as the “Product”) is for the end user’s informational purposes only and is subject to change or withdrawal by CA at any time.

This Product may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Product is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of the Documentation for their own internal use, and may make one copy of the Software as reasonably required for back-up and disaster recovery purposes, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the provisions of the license for the Software are permitted to have access to such copies.

The right to print copies of the Documentation and to make a copy of the Software is limited to the period during which the license for the Product remains in full force and effect. Should the license terminate for any reason, it shall be the user’s responsibility to certify in writing to CA that all copies and partial copies of the Product have been returned to CA or destroyed.

EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS PRODUCT “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS PRODUCT, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE.

The use of this Product and any product referenced in the Documentation is governed by the end user’s applicable license agreement.

The manufacturer of this Product is CA.

This Product is provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7013(c)(1)(ii), as applicable, or their successors.

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Copyright © 2005 CA. All rights reserved.

Contents

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1CA Product References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Contact Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Reading Syntax Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11General System Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 12General Inquiry Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Job Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Workstation Network Control . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Forecasting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Forecast Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Forecast Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Forecast Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Common Forecast Parameter Descriptions . . . . . . . . . . . . . . . . 24

Forecasting from the Database . . . . . . . . . . . . . . . . . . . . . . . 29Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Forecast Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Forecasting from Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Forecast Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Forecasting Job Flow Structures . . . . . . . . . . . . . . . . . . . . . . 35Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Forecasting Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Forecast Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Forecasting Tape Requirements . . . . . . . . . . . . . . . . . . . . . . . 38Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Forecast Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39CPU Job Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 2. Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41/ASSIGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Format 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Format 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Format 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

/AUTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

/BRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

/CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Contents iii

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

/CLOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

/COPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

/DISPLAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

/DMP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72/DRCLASS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73/DRMODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

/DUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

/EADMIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77/ECHO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79/EMAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80/FETCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81/JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82/LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84


/LOGOFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85/LOGON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

/MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

/MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Special Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

/NXTMSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91/OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93/OPERID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94/OPERIDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96/PAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98


/PAnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

iv Commands Guide

/PFnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

/PROF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

/PROFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

/PURGPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

/REFRESH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112/RELINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

/RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115/SDESK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116/SHUTDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119/START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120


/STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

/SWAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124/UID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125/WLB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126/WTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128ADDRQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129


ADDSCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

AL/ALC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

ALLOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

APA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136APA Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136APA Prompt Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137ARFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Contents v

ARTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143AR.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144BLDG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146CALMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147CANCEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Input Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Request, Ready or Active Queue Jobs . . . . . . . . . . . . . . . . . . 149Output Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

CAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

CONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

CTLG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Processing for TYPE=ADD . . . . . . . . . . . . . . . . . . . . . . . . . 158Processing for TYPE=DEL . . . . . . . . . . . . . . . . . . . . . . . . . 158Processing for TYPE=REPL . . . . . . . . . . . . . . . . . . . . . . . . 159Processing for TYPE=COPY . . . . . . . . . . . . . . . . . . . . . . . . 159Processing for TYPE=CON . . . . . . . . . . . . . . . . . . . . . . . . . 159

DB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160DCONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162DEALLOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163DEMAND, DEMANDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164


DIRECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

DLTX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

DMDNW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

DMPCAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

DMPDSCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

DMPDSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

FALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

vi Commands Guide

FIND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

FJOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

FLOWD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

FLOWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

FPOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

FPRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

FQALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

FQJOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

FQPOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

FQPRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

FQRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

FQSTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

FQTAPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

FRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

FRJOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

FRQJOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

FSTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

FSTRUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

FTAPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

FWLP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248FWLP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252FWLP Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

GRAPHc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260HELP Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Contents vii

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262HOLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263


IN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265Input Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266Output Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267IN Command Response . . . . . . . . . . . . . . . . . . . . . . . . . . 268

IN Command Response Example . . . . . . . . . . . . . . . . . . . . 268Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

IO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271IO Command Response . . . . . . . . . . . . . . . . . . . . . . . . . . 272

IO Command Response Example . . . . . . . . . . . . . . . . . . . . 272Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

JCLOVRD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

LACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

LACTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

LARF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Example 1. Output: LARF With Generic ARFSET . . . . . . . . . . 290Example 2. Output: LARF With Specific ARFSET . . . . . . . . . . . 292

LARFQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

LCTLG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

LDSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

LDTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

LISTDIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

LJCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321LJCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325LJES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326


LJOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

LJOBR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

viii Commands Guide

LLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

LLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355Required Action for a Locked Job . . . . . . . . . . . . . . . . . . . . . 357Suspended Scheduling Messages . . . . . . . . . . . . . . . . . . . . . 357Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

LNTWK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

LOAD, LOADH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

LOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

LOGIN/LOGOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368Input Workstation Networks . . . . . . . . . . . . . . . . . . . . . . . . 368

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369Output Workstation Networks . . . . . . . . . . . . . . . . . . . . . . . 369

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370LPDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372LPOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376LPRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382LPROS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384


LPRRN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

LQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399ARF Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405

LQP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410

LQR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

LRDY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420

LRDYP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

LRDYR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430

LREQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436

LREQP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441

Contents ix

LREQR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445

LRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448

LRLOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455

LRMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461

LSCHD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466

LSYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471

LWLB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474

MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479

MENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480NOPRMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481


NXTCYC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484

OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486

POST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490

PRINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492

PRMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494

PRRNJCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495

PRSCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497

PRSQA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498

PRSQD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499

PS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500QJCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502QM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503

x Commands Guide

PF Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504QM.1 CPU Jobs Status Prompt Panel . . . . . . . . . . . . . . . . . . . . . 505

QM.1-X CPU Jobs Status Panel . . . . . . . . . . . . . . . . . . . . . . 509Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510

QM.1-M CPU Job Requirements . . . . . . . . . . . . . . . . . . . . . 511Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513

QM.1-XC Reason for Cancel Panel . . . . . . . . . . . . . . . . . . . . 514Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515

QM.2 CPU Job Predecessors Prompt Panel . . . . . . . . . . . . . . . . . 516QM.2-X CPU Job Predecessors . . . . . . . . . . . . . . . . . . . . . . 518

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520QM.3 CPU Job Attributes Prompt Panel . . . . . . . . . . . . . . . . . . . 521

QM.3-X CPU Job Attributes . . . . . . . . . . . . . . . . . . . . . . . . 523Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526

QM.4 CPU Job In Restart Status Prompt Panel . . . . . . . . . . . . . . . 527QM.4-X CPU Job In Restart Status . . . . . . . . . . . . . . . . . . . . 528

QM.5 Queued JCL Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531QM.6 Input Networks Prompt Panel . . . . . . . . . . . . . . . . . . . . . . 533

QM.6-X Input Networks (1-Up Display) . . . . . . . . . . . . . . . . . . 535Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538

QM.6-S Input Networks (2-Up Display) . . . . . . . . . . . . . . . . . . 538Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539

QM.7 Output Networks Prompt Panel . . . . . . . . . . . . . . . . . . . . . 540QM.7-X Output Networks (1-Up Display) . . . . . . . . . . . . . . . . . 542

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544QM.7-S Output Networks (2-Up Display) . . . . . . . . . . . . . . . . . 544

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545RELEASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546


REMIND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549

RENAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550

REQUEUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553

RESANL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554RESCHNG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556


RESOLV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562

RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568RQMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569

Contents xi

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569RQVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570RSVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572


RUN, RUNH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579

RUNNW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581

RUSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582SCHDMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583SCRATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584


SPACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586

SSCAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591

START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592

STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593

SUBMIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595

SUBSCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597

SUBTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599

TIQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600TRIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601


UNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603

UT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605PF Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605

UT.1 - Allocate/Catalog Dataset Panel . . . . . . . . . . . . . . . . . . . . 606Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608

UT.2 - Catalog Dataset Panel . . . . . . . . . . . . . . . . . . . . . . . . . 609Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610

UT.3 - Rename Dataset Panel . . . . . . . . . . . . . . . . . . . . . . . . . 611Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612

UT.4 - Scratch Dataset Panel . . . . . . . . . . . . . . . . . . . . . . . . . . 613

xii Commands Guide

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614UT.5 - Uncatalog Dataset Panel . . . . . . . . . . . . . . . . . . . . . . . . 615

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616UT.6 - Build GDG Index Panel . . . . . . . . . . . . . . . . . . . . . . . . . 617

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618UT.7 - Delete Index Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620UT.8 - Connect a Catalog Panel . . . . . . . . . . . . . . . . . . . . . . . . 621

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622UT.9 - Disconnect a Catalog Panel . . . . . . . . . . . . . . . . . . . . . . 623

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624UT.10 - Find DSN on DASD Panel . . . . . . . . . . . . . . . . . . . . . . 625

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626UT.11 - Allocate Volume Panel . . . . . . . . . . . . . . . . . . . . . . . . . 627

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628UT.12 - Deallocate Volume Panel . . . . . . . . . . . . . . . . . . . . . . . 629

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630UT.13 - Display Format 1 DSCB Panel . . . . . . . . . . . . . . . . . . . . 631

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633UT.14 - Display Directory Info Panel . . . . . . . . . . . . . . . . . . . . . . 634

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635UT.15 - Display Dataset Attributes Map Panel . . . . . . . . . . . . . . . . 636

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637UT.16 - Display Available DASD Space Panel . . . . . . . . . . . . . . . . 638

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639UT.17 - Display Physical Data Records Panel . . . . . . . . . . . . . . . . 640

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641UT.18 - Display Catalog Block Panel . . . . . . . . . . . . . . . . . . . . . 642

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643UT.19 - Display Catalog Entries Panel . . . . . . . . . . . . . . . . . . . . 644

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645VERIFY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647XPOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648


XPRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654

XQ, XQJ, XQN, and XQM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658

XREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659XRQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660XRST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661XSPOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662XSPRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663

Contents xiii

XUPD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664

XWLB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671

xiv Commands Guide

Chapter 1. Introduction

This section contains the following topics:

CA Product References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Contact Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Reading Syntax Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11General System Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 12General Inquiry Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Job Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Workstation Network Control . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Forecasting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

The Commands Guide is intended as a reference guide for production andoperations personnel and for users with scheduling and operationsresponsibilities using Unicenter® CA-7™ Job Management (Unicenter CA-7).This guide describes general system commands, workstation networkcommands, workload balancing commands, forecasting, general inquiryfacilities, work flow control, online and interface utilities.

Chapter 1. Introduction 1

CA Product References


This document references the following CA products:

■ Advantage™ CA-Roscoe® Interactive Environment (Advantage CA-Roscoe)

■ AllFusion® Endevor® Change Management (AllFusion Endevor)

■ AllFusion® CA-Librarian® (AllFusion CA-Librarian)

■ AllFusion® CA-Panvalet® (AllFusion CA-Panvalet)

■ BrightStor® CA-ASM2® Backup and Restore (BrightStor CA-ASM2)

■ BrightStor® CA-Dynam®/TLMS Tape Management (BrightStorCA-Dynam/TLMS)

■ BrightStor® CA-1® Tape Management (BrightStor CA-1)

■ eTrust® CA-ACF2™ Security (eTrust CA-ACF2)

■ eTrust® CA-Top Secret® Security (eTrust CA-Top Secret)

■ Unicenter® CA-APCDDS™ Automated Report Balancing (UnicenterCA-APCDDS)

■ Unicenter® AutoSys® Job Management (Unicenter AutoSys)

■ Unicenter® CA-Dispatch™ Output Management (Unicenter CA-Dispatch)

■ Unicenter® CA-Easytrieve® Report Generator (CA-Easytrieve)

■ Unicenter® CA-JCLCheck™ Utility (Unicenter CA-JCLCheck)

■ Unicenter® CA-Jobtrac™ Job Management (Unicenter CA-Jobtrac)

■ Unicenter® CA-Netman® (Unicenter CA-Netman)

■ Unicenter® Network and Systems Management (Unicenter NSM)

■ Unicenter® NSM Job Management Option (Unicenter NSM JM Option)

■ Unicenter® CA-Opera™ (Unicenter CA-Opera)

■ Unicenter® CA-OPS/MVS® Event Management and Automation (UnicenterCA-OPS/MVS)

■ Unicenter® CA-Scheduler® Job Management (Unicenter CA-Scheduler)

■ Unicenter® Enterprise Job Manager (Unicenter EJM)

■ Unicenter® Service Desk (Unicenter Service Desk)

■ Unicenter® Universal Job Management Agent (Unicenter Universal JobManagement Agent)

■ Unicenter® Workload Control Center (Unicenter WCC)

■ Unicenter® CA-7™ Job Management (Unicenter CA-7)

■ Unicenter® CA-7™ Job Management Smart Console Option (Unicenter CA-7Smart Console Option)

2 Commands Guide


■ Unicenter® CA-7™ Job Management Webstation Option (Unicenter CA-7Job Management Webstation Option)

■ Unicenter® CA-7™ Job Management Workstation Option (Unicenter CA-7Job Management Workstation Option)

■ Unicenter® CA-11™ Restart and Tracking (Unicenter CA-11)


Contact Technical Support

Contact Technical Support

For online technical assistance and a complete list of locations, primary servicehours, and telephone numbers, contact Technical Support athttp://ca.com/support.

4 Commands Guide

Reading Syntax Diagrams


The formats of all statements and some basic language elements are illustratedusing syntax diagrams. Read syntax diagrams from left to right and top tobottom.

The following terminology, symbols, and concepts are used in syntax diagrams.

Keywords: Appear in uppercase letters, for example, COMMAND or PARM.These words must be entered exactly as shown.

Variables: Appear in italicized lowercase letters, for example, variable.

Required Keywords and Variables: Appear on a main line.

Optional Keywords and Variables: Appear below a main line.

Default Keywords and Variables: Appear above a main line.

Double Arrowheads Pointing to the Right: Indicate the beginning of astatement.

Double Arrowheads Pointing to Each Other: Indicate the end of astatement.

Single Arrowheads Pointing to the Right: Indicate a portion of a statement,or that the statement continues in another diagram.

Punctuation Marks or Arithmetic Symbols: If punctuation marks orarithmetic symbols are shown with a keyword or variable, they must be enteredas part of the statement or command. Punctuation marks and arithmeticsymbols can include:

, comma > greater than symbol

. period < less than symbol

( open parenthesis = equal sign

) close parenthesis ¬ not sign

+ addition − subtraction

* multiplication / division



The following is an example of a statement without parameters.

Statement Without Parameters

��──COMMAND─────────────────────────────────────────────────────��

You must write:

COMMAND

Required parameters appear on the same horizontal line (the main path of thediagram) as the command or statement. The parameters must be separated byone or more blanks.

Statement with Required Parameters

��──COMMAND──PARM1──PARM2───────────────────────────────────────��

You must write:

COMMAND PARM1 PARM2

Delimiters such as parentheses around parameters or clauses must beincluded.

Delimiters Around Parameters

��──COMMAND─ ──(PARM1) ──PARM2='variable' ─────────────────────────��

If the word variable is a valid entry, you must write:

COMMAND (PARM1) PARM2='variable'

Where you see a vertical list of parameters as shown in the following example,you must choose one of the parameters. This indicates that one entry isrequired and only one of the displayed parameters is allowed in the statement.

Choice of Required Parameters

��──COMMAND─ ──┬ ┬─PARM1─ ─────────────────────────────────────────�� ├ ┤─PARM2─ └ ┘─PARM3─

You can choose one of the parameters from the vertical list, such as in thefollowing examples:

COMMAND PARM1 COMMAND PARM2 COMMAND PARM3

6 Commands Guide


When a required parameter in a syntax diagram has a default value, it indicatesthe value for the parameter if the command is not specified. If you specify thecommand, you must code the parameter and specify one of the displayedvalues.

Default Value for a Required Parameter

┌ ┐─YES─��──COMMAND─ ──PARM1= ──┴ ┴─NO── ─PARM2─────────────────────────────��

If you specify the command, you must write one of the following:

COMMAND PARM1=NO PARM2COMMAND PARM1=YES PARM2

A single optional parameter appears below the horizontal line that marks themain path.

Optional Parameter

��──COMMAND─ ──┬ ┬─────────── ─────────────────────────────────────�� └ ┘─PARAMETER─

You can choose (or not) to use the optional parameter, as shown in thefollowing examples:

COMMAND COMMAND PARAMETER

If you have a choice of more than one optional parameter, the parametersappear in a vertical list below the main path.

Choice of Optional Parameters

��──COMMAND─ ──┬ ┬─────── ─────────────────────────────────────────�� ├ ┤─PARM1─ └ ┘─PARM2─

You can choose any of the parameters from the vertical list, or you can writethe statement without an optional parameter, such as in the following examples:

COMMAND COMMAND PARM1 COMMAND PARM2



For some statements, you can specify a single parameter more than once. Arepeat symbol indicates that you can specify multiple parameters. Thefollowing examples include the repeat symbol.

Repeatable Variable Parameter

┌ ┐────────────��──COMMAND─ ───� ┴─variable─ ──────────────────────────────────────��

In the preceding example, the word variable is in lowercase italics, indicatingthat it is a value you supply, but it is also on the main path, which means thatyou are required to specify at least one entry. The repeat symbol indicates thatyou can specify a parameter more than once. Assume that you have threevalues named VALUEX, VALUEY, and VALUEZ for the variable. Some of yourchoices are:

COMMAND VALUEXCOMMAND VALUEX VALUEYCOMMAND VALUEX VALUEX VALUEZ

If the repeat symbol contains punctuation such as a comma, you must separatemultiple parameters with the punctuation. The following example includes therepeat symbol, a comma, and parentheses.

Separator with Repeatable Variable and Delimiter

┌ ┐─,────────��──COMMAND──(─ ───� ┴─variable─ ─)─────────────────────────────────��

In the preceding example, the word variable is in lowercase italics, indicatingthat it is a value you supply. It is also on the main path, which means that youmust specify at least one entry. The repeat symbol indicates that you canspecify more than one variable and that you must separate the entries withcommas. The parentheses indicate that the group of entries must be enclosedwithin parentheses. Assume that you have three values named VALUEA,VALUEB, and VALUEC for the variable. Some of your choices are:

COMMAND (VALUEC) COMMAND (VALUEB,VALUEC) COMMAND (VALUEB,VALUEA) COMMAND (VALUEA,VALUEB,VALUEC)

The following example shows a list of parameters with the repeat symbol.

Optional Repeatable Parameters

┌ ┐─────────── ┌ ┐─────────── ┌ ┐───────────��──COMMAND─ ───� ┴┬ ┬─────── ───� ┴┬ ┬─────── ───� ┴┬ ┬─────── ─────────────�� └ ┘─PARM1─ └ ┘─PARM2─ └ ┘─PARM3─

8 Commands Guide


Some choices you can make include:

COMMAND PARM1COMMAND PARM1 PARM2 PARM3COMMAND PARM1 PARM1 PARM3

For example, YES in the following diagram, its special treatment indicates it isthe default value for the parameter. If you do not include the parameter whenyou write the statement, the result is the same as if you had actually specifiedthe parameter with the default value.

Default Value for a Parameter

��──COMMAND─ ──┬ ┬───────────────── ─PARM2─────────────────────────�� │ │┌ ┐─YES─

└ ┘──PARM1= ──┴ ┴─NO──

Because YES is the default in the example preceding, if you write:

COMMAND PARM2

you have written the equivalent of:

COMMAND PARM1=YES PARM2

In some syntax diagrams, a set of several parameters is represented by asingle reference, as in this example:

Variables Representing Several Parameters

��──COMMAND─ ──┬ ┬───────────────────── ───────────────────────────�� ├ ┤─PARM1───────────────

└ ┘─┤ parameter-block ├─

parameter-block:├─ ──┬ ┬────────────────── ─────────────────────────────────────────┤

├ ┤─PARM2──────────── └ ┘──PARM3 ──┬ ┬───────

├ ┤─PARM4─ └ ┘─PARM5─

The parameter-block can be displayed in a separate syntax diagram.



Choices you can make from this syntax diagram therefore include (but are notlimited to) the following:

COMMAND PARM1 COMMAND PARM3

COMMAND PARM3 PARM4

Note: Before you can specify PARM4 or PARM5 in this command, you mustspecify PARM3.

A note in a syntax diagram is similar to a footnote except that the note appearsat the bottom of the diagram box.

��──COMMAND─ ──┬ ┬───────── ───────────────────────────────────────�� └ ┘ ─PARM1───(1)

Note:1 This is a note about the item.

10 Commands Guide

Commands

Commands

For command syntax, optional parameters, command usage, and panelexamples for these commands, see Chapter 2, “Commands.”

You may restrict some of these commands to particular terminals or operators.Check with the Unicenter CA-7 coordinator within the data center for anycommand restrictions that may exist.


General System Commands

General System Commands

General system commands are top line commands used by the Unicenter CA-7terminal operator to perform various functions.

Function Description Command

Generaloperatingcommands

Use these commands to performvarious functions. For those entriesthat can be entered withoutparameters, omit the comma.

/BRO/CLOSE/COPY/DISPLAY/ECHO/FETCH/JCL/LOG/LOGOFF/LOGON/MSG/MVS/NXTMSG/PA/PAGE/PF/PROF/PURGPG/WTO

12 Commands Guide

General Inquiry Facility


The general inquiry facility provides information about the system, its variouscomponents and operations. Information available includes referenceinformation about commands and applications, database contents, queueinformation, job status, and schedule information.

The general inquiry commands are also useful in batch mode to obtainhardcopy output of the information provided.


HELP tutorials List tutorials. HELP

Job inquiries Databasecontents

Obtain information aboutvarious jobs from theUnicenter CA-7database.

LJOBLJOBRLRESLSYS

Queuecontents

Obtain information aboutjobs from the UnicenterCA-7 queues.

LACTLJESLPRRNLQLRDYLREQLRESLRLOG

ARF queuecontents

Obtain information aboutstatus of recovery forUnicenter CA-7 jobs.

LARFQ

Queue statusinquiries

Obtain information aboutthe work residing inUnicenter CA-7 queues.These commands arehelpful in locatingspecific jobs ornetworks. They are alsovaluable whenmonitoring the flow ofthe total workload.

LACTLPOSTLPRELPRRNLQLRDYLREQ




Data setinquiries

Obtain information aboutuser application datasets in the UnicenterCA-7 environment. Youcan review informationfrom the Unicenter CA-7database, as well asPDS or sequential dataset data, with thesecommands.

LCTLGLDSNLPDS

JCL inquiries Review job JCL andmembers of systemlibraries. Thesecommands access thedesignated data set toobtain the data in itspermanent form (asopposed to the QJCLcommand that displaysthe JCL in its submitform).

LJCKLJCLLLIBLPDS

Scheduleinquiries

Obtain information fromthe Unicenter CA-7database regardingUnicenter CA-7schedules.

LJOBLLOCKLSCHD

ARFSETinquiries

Obtain information fromthe Unicenter CA-7 ARFdatabase regardingautomated recovery forUnicenter CA-7 jobs.

LARF

Documentationinquiries

Review anyuser-defineddocumentationinformation that residesin the Unicenter CA-7database. Many of theother inquiry commandscan show thedocumentation for aparticular job, and soforth, as an optional partof the display.

LPROS

14 Commands Guide



Reminderinquiries

Review free-formreminder informationthat you defined for anyspecial purpose.

LRMD

Workloadbalancinginquiries

Provide informationrelated to the UnicenterCA-7 workloadbalancing function.Through thesecommands, thoseresource and priorityconsiderations that areimportant to balancingthe workload can bereviewed.

LACTRLJOBRLQPLQRLRDYPLRDYRLREQPLREQRLRESLWLB

Workstationnetworkinquiries

Databasecontents

Provide informationabout workstationnetworks from thedatabase.

LNTWKLCTLGLSCHD

Queuecontents

Obtain information aboutworkstation networkswhen they reside in thequeues. Thesecommands arepresented as they relateto input and outputnetworks that usedifferent commands.

LPRELPOSTLRLOG


Job Flow Control

Job Flow Control

Once a job has been scheduled from the Unicenter CA-7 database, job flowcontrol is accomplished through a group of queues. Normally, job flow control isperformed automatically by Unicenter CA-7; however, it is sometimes necessaryfor the user to manually intervene for unusual situations or on-requestscheduling needs.

This table illustrates the top line commands that address manual job flowcontrol requirements.


Requirementcontrol

Use the following top line commandsand panels to monitor and modify therequirements of those jobs underUnicenter CA-7 control.

ADDRQCTLGJCLOVRDPOSTQM.1QM.2QM.3SUBTMVERIFYXQ, XQJ,XQM, andXQNXRQXUPD

Schedulecontrol

It is sometimes necessary to alterscheduled jobs. Use these commandsto perform scheduling changes.

ADDSCHDEMANDDIRECTNXTCYCRUNSSCANSUBMITSUBSCH

Resourcemanagement

Managing resource usage by jobsallows for an additional level of job flowcontrol. These commands and panelsare used to define, monitor, and controljob submission through job resourceuse. See "Virtual ResourceManagement" in the DatabaseMaintenance Guide for more informationabout the RM panels.

LQPRSCFPRSQAPRSQDRM.1RM.2RM.3RM.4RM.5RM.6RM.7

16 Commands Guide

Job Flow Control


Temporary JCLchanges

Use these commands to review jobs inthe request or prior-run queues or tomodify the JCL for jobs in the requestqueue.

QJCLQM.5

Interrupting andresuming jobs

Use these commands to delete jobsfrom the queues, interrupt the normalscheduling progress, resume normalscheduling, move jobs from the ready oractive queue, and display jobs in therequest, ready, or active queues.

CANCELHOLDQM.1RELEASEREQUEUEXQ, XQJ,XQM, andXQN

Job restart Jobs that have failed to terminatesuccessfully are returned to the requestqueue for restart by the user. Such jobsare given a restart requirement until therestart is performed. The commands inthis group are used to review and/orperform job restart functions.

LISTQJCLQM.1QM.4QM.5RESTARTXQ, XQJ,XQM, andXQNXRST

Prompting Unicenter CA-7 provides promptingmessages for any late work or work indanger of becoming late. UnicenterCA-7 continues to issue messages untileither the task is completed or the userdisables the prompting. The commandsin this group are provided for managingprompting messages.

LRMDNOPRMPPRMPQM.1REMINDRSVPRUSHXQ, XQJ,XQM, andXQN

Queue control Occasionally you may want or need totemporarily halt the flow of jobs throughthe Unicenter CA-7 queues. An exampleof this need would be the necessity toshut down all processing to apply somemaintenance before processing is tocontinue. Use these commands for thispurpose.

STARTSTOPHOLDRELEASE

Recoverycontrol

Use commands in this category tocancel any automated recovery that isscheduled for a given run of aproduction job.

ARFP


Workstation Network Control


Workstation networks define tasks that you must perform manually (a non-CPUactivity). Although such tasks may be any manual tasks, they are normallyperformed in support of CPU jobs. They may be performed either before orafter the job is run. These manual tasks are termed input or output networks.Each task in the network is performed at what is known as a workstation. Eachworkstation must have its own unique station name.

Some examples of preprocessing tasks that might be defined together as aninput network are:

A control desk logging functionData encodingEncoding verificationControl desk task sequence for handling input data required by a CPU job

Some examples of postprocessing tasks that might be defined together as anoutput network are:

Report balancingDecollate/burst/trimDeliveryTask sequence for handling printed output produced by a CPU job

Each workstation may have its own terminal; or, multiple workstations mayshare a single terminal. When networks are scheduled, either manually orautomatically, Unicenter CA-7 interacts with personnel at the appropriateterminals to ensure that manual workstation tasks are performed in the correctsequence and at the proper time. Besides the Unicenter CA-7 messages usedto accomplish this, inquiry commands are also available for further examiningany related data that may assist the user in performing the necessary tasks.

All terminal sessions are performed between /LOGON and /LOGOFFcommands that must be entered by the terminal user. During terminal sessions,any number of workstation sessions may occur. Workstation sessions provideUnicenter CA-7 with the beginning and ending time-of-day for each task definedin a network. (The tasks must be performed in the predefined sequence.)

Task beginning times are entered by logging into the station (as opposed tologging onto a terminal) with a LOGIN, IN, or IO command or using one ofthese functions on a QM.6 or QM.7 panel.

Task ending times are entered by logging out of the station (as opposed tologging off of a terminal) with a LOGOUT, IO, or OUT command or using one ofthese functions on a QM.6 or QM.7 panel.

18 Commands Guide


As each terminal logs into the workstation, the work for that specific workstationis available for viewing. Messages for that workstation are also routed to theterminal.


Logging in Specify starting of a workstation task. INIOLOGINQM.6QM.7XPOSTXPREXSPOSTXSPRE

Logging out Specify ending of a workstation task. IOLOGOUTOUTQM.6QM.7XPOSTXPREXSPOSTXSPRE

Inquiries These inquiry commands are available forexamining any network related data thatmay assist you in performing necessarytasks.

LCTLGLNTWKLPOSTLPRELRLOGLSCHD

On-requestscheduling

Use these commands to force immediatescheduling of networks.

DMDNWRUNNW

Schedulecontrol

Use these commands to adjust schedulesof networks already in the queues.

ADDSCHSUBSCH




Prompting Prompting is a function of schedule scan.It notifies workstations when a task is lateor about to become late.

When a deadline time arrives andUnicenter CA-7 has not receivednotification that the task has been started,the responsible workstation is prompted orreminded of the late status of the task witha message from Unicenter CA-7.Prompting messages continue until thetask is completed or the operatoracknowledges the prompt.

NOPRMPPRMPREMINDRSVPRUSHQM.6QM.7XPOSTXPREXSPOSTXSPRE

Interruptingand resuminga network

If it is necessary to change the normalprocessing of a network, use thesecommands to interrupt and/or resume anetwork.

CANCELHOLDRELEASEQM.6QM.7XPOSTXPREXSPOSTXSPRE

20 Commands Guide

Forecasting

Forecasting

Forecast Facility

The forecast facility projects the scheduled workload for a given period of time.The projected workload may be as specific as a single job or as general as theworkload for a CPU or application system. Successor jobs triggered bypredecessor jobs, or any jobs triggered by data sets created in the predecessorjobs, may also be included.

Further, forecast displays the projected workload for successive short timeintervals throughout the forecast time period. This representation can be usedto detect bottlenecks in the system. Workload can be rearranged if needed andresources scheduled properly.

Forecast also reports jobs involved with tapes and/or JCL overrides well aheadof their actual submission time in two ways:

■ By preparing a pull list for the tapes indicating the volume serial number ofthe input tapes, and the approximate number of scratch tapes for the outputdata sets.

■ By determining which jobs need JCL overrides. The Forecast reportindicates jobs that need JCL overrides. The override JCL can be stored in aspecial JCL override library and retrieved automatically. This satisfies theJCL override requirement without any further intervention required.

Also, forecast can be used for the following:

■ To show an entire job network, and the ending time of each job in thenetwork's structure, based on an arbitrary starting time.

■ To produce a hardcopy report of scheduled tasks in worksheet format thatcan be used as a manual checklist for recording task completion.

■ To verify newly defined schedules. Forecast can be run for a single job oran entire application system to ensure that defined schedules causeprocessing cycles to occur when required.


Forecasting

Forecast Options

Basically, two options are provided throughout the forecast application. For thefirst option, workload is projected only from the Unicenter CA-7 database. Noexisting workload is projected from the Unicenter CA-7 queues. This optionrequires a beginning time and is generally used for non-specific long rangerequests.

The second option takes the workload existing in both the database and/or theUnicenter CA-7 queues into account in the forecast. This option uses thecurrent time as the beginning of the time interval so that current and futureworkload can be forecasted. It is generally used for shorter and more specificrequests.

22 Commands Guide

Forecasting

Forecast Commands

A number of different commands are provided to generate specific forecastinformation. Even though some of the capabilities overlap, the following tableprovides a guide to the basic capabilities of these commands.

A forecast can be done online or in batch mode for any time interval from oneminute to one year. It can be for all of the data center's work, work for aspecific CPU, or work for a specific job or workstation. Selection criteria areprovided for flexibility in tailoring a forecast run to meet specific needs.

Note: Depending on the selection criteria used, Forecast may produce a largevolume of output. For such large volume runs, it is advisable to use a batchterminal rather than an online terminal. It may also be necessary to increasethe allocated space for the Unicenter CA-7 scratch queue or change theSWFTRK option.

The maximum levels that a forecast command shows is governed by aninitialization file option FCMAXLEV. If this option is not used, the defaultmaximum levels is 99 (for all forecast commands).

Capability Commands

Forecast report for CPU workload with optionalworksheets

FJOB or FQJOB

Forecast report for input workstation workload FPRE or FQPRE

Forecast report for output workstation workload FPOST or FQPOST

Forecast report for input and output workstationworkload

FSTN or FQSTN

Forecast report for CPU and input/output workstationworkload

FALL or FQALL

Graphic display of workload FRES or FQRES

Tape pull list report FTAPE or FQTAPE

Job flow structure FSTRUC


Forecasting

Common Forecast Parameter Descriptions

The following parameters are used throughout the forecast commands and aredefined here and referred to later as needed.

DRMODEIf DRMODE=YES (or Y) is specified, the forecast is limited to jobs with anactive disaster recovery class. The list of active disaster recovery classescan be overridden by the DRCLASS keyword. DRMODE=NO (or N) can beused. If the DRMODE keyword is not specified, DRMODE=YES will beused if Unicenter CA-7 is currently running in disaster recovery mode, orDRMODE=NO if not.

DRCLASSOverrides the list of active disaster recovery classes for the forecastcommand. If DRCLASS is not specified and the forecast command runs indisaster recovery mode, the list of active disaster recovery classes inUnicenter CA-7 is used. If DRCLASS is specified, only the disaster recoveryclasses on the DRCLASS keyword are considered active.

INTSee RINT

JOBDefines the jobs to be forecast.

Default: *

Limits: 1 to 8 alphanumeric characters

Required: No

*Defines all jobs are to be forecast.

jobnameDefines a specific job name.

jobname*Defines a generic job name terminated with an asterisk.

(jobname1,jobname2,...,jobname10)Defines up to 10 specific job names.

JOBNETDefines the job network field as the selection criteria for the jobs to beforecast.

Default: *


Required: No

*Specifies all names.

24 Commands Guide

Forecasting

nameDefines a specific name.

name*Defines a generic name terminated with an asterisk.

Note: If value contains a blank, comma, or quote, it is not possible tospecify the value through batch input.

LVLDefines the number of triggering levels to display. If not defined, theforecast stops after 100 levels or the value defined in the FCMAXLEVkeyword in the Unicenter CA-7 initialization file.

Default: 100 (or Unicenter CA-7 initialization file override)

Limits: 1 to 3 numeric (from 1-999)

Required: No

MAINIDSpecifies that only those jobs set to run on the specified MAINID appear inthe forecast.

Limits: 1 numeric character from 1 to 7 preceded by SY

Required: No

NWDefines the networks as a selection criteria for the stations to be forecast.A combination of STN and NW values governs the final selection of astation to be forecast. If STN=T*,NW=N* is specified, only the stationswhose names start with T and belong to networks whose names start withN are selected for the forecast.

Default: *


Required: No

*Specifies all networks to be forecast.

networkDefines a specific network name.

network*Defines a generic network name terminated with an asterisk.

NWOPTSpecifies whether the forecast should include the output networks and theirindividual stations for the jobs. If NWOPT is omitted, no connectednetworks are included.

Required: No


Forecasting

NSpecifies to include output networks, but not to list individualworkstations in the networks.

SSpecifies to include individual workstations in the network.

RINT|INTDefines the interval time for the forecast of resources needed for theworkload. The entire forecast span is divided into successive time intervalsof the value specified to forecast the number of jobs running and percent ofCPU use during each interval.

Limits: 4 numeric characters specified as hhmm from 0010 (10 minutes) to2400 (24 hours)

Required: No

SCHIDDefines the schedule ID value as the selection criteria for jobs to beforecast.

Default: 0 (all schedule IDs)except for FSTRUC the default is 1

Limits: 1 to 3 numeric characters from 0 to 255except for FSTRUC 1-255

Required: Only if job has no defined schedule

SEGIs specified only with LIST=WP or LIST=WPS to define which segment andsubsegment of prose is to be included in the worksheet. If omitted,LIST=WP and LIST=WPS produce all prose associated with a particularjob. If only segment selection is desired, the parentheses may be omitted.

Limits: 1 to 8 alphanumeric characters segment1 to 8 alphanumeric characters subsegment

Required: No

SEQSpecifies the sequence in which forecast reports are presented.

Default: DLDT

Required: No

DLDTSpecifies the sequence is in the ascending order of deadline or startingdate and time of job, ending date and time of job, and job name.

DODTSpecifies the sequence is in the ascending order of due-out or endingdate and time of job, starting date and time of job, and job name.

26 Commands Guide

Forecasting

JOBSpecifies the sequence is in the ascending order of job name, startingdate and time of job, and ending date and time of job.

STNSpecifies the sequence is in the ascending order of station name,starting date and time of station, and ending date and time of station.

STNDefines the workstations to be forecast.

Default: *


Required: No

*Specifies all workstations are to be forecast.

stationDefines a specific workstation name.

station*Defines a generic workstation name terminated with an asterisk.

(station1,...,station10)Defines up to 10 specific workstations names. The workstation namespecified by the first positional value can be a specific workstationname or a generic workstation name.

SYSDefines the systems as a selection criteria for the jobs to be forecast. Acombination of JOB and SYS values governs the final selection of a job tobe forecast. If JOB=J*,SYS=S* is specified, only the jobs whose namesstart with J and that belong to systems whose names start with S areselected for the forecast.

Default: *


Required: No

*Specifies all system names.

systemDefines a specific system name.

system*Defines a generic system name terminated with an asterisk.

Note: If value contains a blank, comma, or quote, it is not possible tospecify the value through batch input.


Forecasting

TRIGSpecifies whether the forecast should include the job-triggered and/or dataset-triggered jobs.

Default: J (except JD for FSTRUC)

Required: No

JSpecifies to include only the job-triggered jobs.

DSpecifies to include only the data set-triggered jobs.

DJSpecifies to include both job-triggered and data set-triggered jobs.

JDSpecifies the same as DJ.

NSpecifies to include neither job triggers nor data set triggers.

Any data set that can be created by a forecasted job and that has a dataset trigger defined, is assumed to be created thus triggering the other job.

TYPESpecifies whether the "dont schedule before/after" criteria defined on theDB.1 panel is to be honored when generating a forecast.

Default: ACTUAL

Required: No

ACTUALSpecifies honor "dont schedule before/after" criteria.

ALLSpecifies show all jobs as scheduled. Also indicates jobs that haveNXTCYC,SET=OFF and NXTCYC,SET=SKP specified.

28 Commands Guide

Forecasting

Forecasting from the Database

Commands

This group of commands selects work only from the database according to thestart time. Start time is either explicitly specified or implied by due-out timeminus average elapsed time. Job (data) selection is made if the start time fallswithin the time interval of the forecast. Any jobs triggered by the selected jobs,or any workstation in the output networks connected to these jobs, are alsodisplayed. As a result, the start time of these subsequent jobs or workstationsmay fall beyond the specified time interval. The group includes:

FJOBForecasts for jobs

FSTNForecasts for workstations

FPREForecasts for input workstations

FPOSTForecasts for output workstations

FALLForecasts for jobs and workstations (in both input and output networks)

These commands are described in the "Commands" chapter.

A forecast can be done for any time interval and it may be done in online orbatch mode. However, as the forecast time interval is increased, the responsetime in online mode may lengthen and/or the output volume may becomelarger. These forecast functions use the Unicenter CA-7 scratch queue. Theallocated space for this file may have to be increased, depending on the size ofthe database and the forecast's time interval.

Forecast selection can be made from the database by job, system, workstation,or network and can be indicated by specific or generic names. Specific namesmust be specified in up to 8 characters, and generic names must be specifiedin up to seven characters and terminated with an asterisk (*).


Forecasting

Forecast Interval

You can define the forecast interval for these commands using a beginning andending date.

The dates have the following format:

��─ ──FROM=(mmddyy,hhmm) ──, ──┬ ┬──TO=(mmddyy,hhmm) ────────────────��└ ┘──SPAN=hhhh ───────

mmddyyDefines the date.

mmDefines the month (01 through 12). Required. Leading zeros arerequired.

ddDefines the day (01 through 31). Optional. If omitted, 01 is assumed forFROM, last day of month for TO. A leading 0 is required if less than10.

yyDefines the year. Optional. If omitted, the current year is assumed.

hhmmDefines the time. Optional. If omitted, 0000 is assumed for FROM, 2359 forTO.

hhDefines the hour (00 through 23).

mmDefines the minute (00 through 59).

SPAN=hhhhAs an alternate to specifying an ending date and time (TO), you canrequest a time interval using SPAN=hhhh where:

hhhhDefines the interval span in hours. Minimum value is 1 and maximumvalue is 8784 (approximately one year).

Note: A job (or network) is only considered by the forecast if the FROM timeof the forecast falls within the job's (or network's) schedule period(January-December or July-June).

30 Commands Guide

Forecasting

Examples

In these time interval examples, current year is 2005.

FROM=(�3�7,�8) is identical to FROM=(�3�7�5,�8��)

FROM=�515 is identical to FROM=(�515�5,��)

TO=(�3,17) is identical to TO=(�331�5,17��)

TO=�1 is identical to TO=(�131�5,2359)

FROM=�1 is identical to FROM=(�1�1�5,��)

Forecasting from Queues

Commands

FQJOBForecasts for jobs

FQSTNForecasts for workstations

FQPREForecasts for input workstations

FQPOSTForecasts for output workstations

FQALLForecasts for jobs and workstations (in both input and output networks)

These commands select work from the Unicenter CA-7 queues and from thedatabase. The selection for work is made from the Unicenter CA-7 queues first.Then, if the forecast time period is large enough, further selection is made fromthe database according to the start time. Start time is either explicitly specifiedor implied by due-out time minus average elapsed time. The data selection ismade if the start time falls within the time interval of the forecast. Any jobstriggered by selected jobs, or any workstation in the output networks connectedto these jobs, are also displayed. As a result, the start time of these subsequentjobs or workstations may fall beyond the specified time interval.

A forecast can be done for any time interval in online or batch mode. However,as the forecast time interval is increased, the response time in online modemay lengthen and/or the output volume may become larger. These forecastfunctions use the Unicenter CA-7 scratch files. The allocated space for thesefiles may have to be increased, depending on the size of the database and theforecast time interval.


Forecasting

Forecast selection can be made from the database by job, system, workstation,or network and can be indicated by specific or generic names. Specific namesare specified in up to 8 characters, and generic names are specified in up to 7characters and terminated by an asterisk (*).

32 Commands Guide

Forecasting

Forecast Interval

The beginning time for the forecast interval for these functions is always thecommand initiation (current) time. The ending time for the forecast interval isoptional. If omitted, selection is based on the Unicenter CA-7 queues only. Youcan specify the ending time either explicitly by a keyword TO or implicitly bySPAN.

The keyword has the following format:

��─ ── ─── ───TO=(mmddyy,hhmm) ─────────────────────────────────────��


mmDefines the month (01 through 12). Required. Leading zeros arerequired.

ddDefines the day (01 through 31). Optional. If omitted, last day of monthis assumed. A leading 0 is required if less than 10.


hhmmDefines the time. Optional. If omitted, 2359 is assumed.




Forecasting

The keyword SPAN format is:

��─ ──SPAN=hhhh ──────────────────────────────────────────────────��

hhhhDefines hours from 1 to 8784 (1 year).

Examples: Forecast interval examples:

TO=(�517,�8) is identical to (�517�5,�8��)

TO=�6 is identical to (�63��5,2359)

In these examples, current year is 2005.

34 Commands Guide

Forecasting

Forecasting Job Flow Structures

Commands

FSTRUCReports on an entire CPU job flow structure from the database along withstarting and ending times.

FRJOBProduces a reverse job flow structure from the database to identify triggerchains and header jobs.

FRQJOBProduces a reverse job flow structure from the database and the statusqueues to identify trigger chains and realtime header jobs.

These commands produce reports that display the structures of job flowsdefined in the Unicenter CA-7 database. They are used to deal with individualstructures within the database definitions rather than the entire workload.

The FSTRUC command can be used to produce a forward forecast of a jobstructure from a starting job with a specific or implied starting date and time.

You can use the FRJOB and FRQJOB commands to produce reverse jobstructures that display the paths of control that cause the target job to bebrought into the system through job, data set, and network trigger definitions.That is, answer the question "How does this job get into the system?". Thequeue variation of this command (FRQJOB) checks the status queues todetermine if a job in the trigger chain currently resides in the queues.


Forecasting

Forecasting Resources

Commands

FRESForecasts for resources needed for CPU and workstation workload.

FQRESForecasts for resources needed for CPU and workstation workload includingthe existing workload in the Unicenter CA-7 queues.

These commands display, in reports and graphs, resource forecasts forsuccessive short time intervals throughout the forecast time period. Theseresources include percentage of CPU, number of tapes (for each type), andnumber of workstations.

In the case of the FQRES function, the work for resource forecasting isselected from the Unicenter CA-7 queues and from the database. Theselection is made from the queues first. Subsequently, if the forecast timeperiod is large enough, further selection is made from the database.

In the case of the FRES function, the work is selected only from the database.

In both cases, selection from the database is done according to the start time.Start time is either explicitly specified or implied by due-out time minus averageelapsed time. The selection is made if the start time falls within the time intervalof the forecast. Any jobs triggered by the selected jobs or any workstation in theoutput networks connected to these jobs are also included at the user's option.

A forecast can be done for any resolved time interval and it may be in online orbatch mode. However, as the forecast time interval is increased, the responsetime in online mode may lengthen and/or the output volume may becomelarger. These forecast functions use the Unicenter CA-7 scratch queue. Theallocated space for this file may have to be increased, depending on the size ofthe database and the forecast's time interval. See SWFTRK parameter on theDAIO initialization file statement.

Forecast selection can be made from the database by job, system, workstation,or network and can be indicated by specific or generic names. Specific namesare specified in up to 8 characters, and generic names are specified in up to 7characters and terminated with an asterisk (*).

36 Commands Guide

Forecasting

Forecast Interval

The beginning time of the forecast for the FRES command can be any validtime. For FQRES, it is always the command initiation (current) time. The endingtime for the forecast for FRES must be specified. For FQRES it is optional. Ifomitted, the selection is based on the Unicenter CA-7 queues only. The endingtime can be specified either explicitly by the keyword TO or implicitly by SPAN.For the formats of the FROM and TO keywords, see “FQRES” on page 215and “FRES” on page 223.


Forecasting

Forecasting Tape Requirements

Commands

FTAPETape pull list for jobs.

FQTAPETape pull list for jobs including those in the Unicenter CA-7 queues.

These commands produce reports indicating the volume serial numbers of theinput tapes needed for jobs during the specified forecast time period. The jobsused for FTAPE are selected only from the Unicenter CA-7 database. In thecase of the FQTAPE, the jobs used to produce tape pull lists are selected fromthe Unicenter CA-7 queues and from the database, but selection is made fromthe queues first. Then, if the forecast period is large enough, further selection ismade from the database.

The selection from the database in both cases is done according to the starttime. Start time is either explicitly specified or implied by due-out time minusaverage elapsed time. The selection is made if the start time falls within thetime interval of the forecast. Any jobs triggered by the selected jobs are alsooptionally included. Once the job is selected, the database is searched for anydata set residing on tape. Unicenter CA-7 entries, and system catalog entries,are searched to find the appropriate volume serial numbers of the tapes.

Forecast selection can be made from the database by either job name orsystem name. These can be specific or generic. Specific names are specified inup to 8 characters, and generic names are specified in up to 7 characters andterminated with an asterisk (*).

Note: The JCL for selected jobs is not examined, only the databaseinformation. Therefore, temporary changes made to JCL regarding VOLSERvalues are not reflected in the forecast unless the job is reloaded.

The order of the JCL within a step is important to whether a particular tape dataset is forecasted. Consider two DD statements referring to the same data set(for example, a GDG), one for input and the other for output. If the input DDstatement comes before the output DD statement, the data set is considered asa requirement and does forecast. Otherwise, it does not.

38 Commands Guide

Forecasting

Forecast Interval

The beginning time for the FTAPE command can be any valid time. ForFQTAPE, however, it is always the command initiation (current) time. You mustspecify the ending time for FTAPE. For FQTAPE it is optional; if omitted, theselection is based on the Unicenter CA-7 queues only. You can specify theending time either explicitly by the keyword TO or implicitly by SPAN. For theformats of the FROM and TO keywords, see “FQTAPE” on page 221 and“FTAPE” on page 245.

Worksheets

The worksheet options from forecast provide conveniently formatted checklistsfor projected CPU job activities. When requested, the output can be used byproduction control personnel as status, planning, or even recoverydocumentation.

CPU Job Worksheets

Worksheets for jobs are requested using the LIST option of the FJOB or FALLcommand. This option is most useful when requested through the BatchTerminal Interface facility because the output is in hardcopy format and can befiled or distributed as desired.

For a sample worksheet, see the LIST option of the FJOB command in FJOBon page 190 and to FJOB Panel on page 194.

JOB Worksheet, LIST=W

� � FJOB,FROM=�3�6�5,TO=�3�6�5,LIST=W DATE �2-27-�5 PAGE ��2

JOB=DUCCXX�1 COMPLETED ________________

SCHEDULE: LATEST STRT=�5�65/�759 SCHD MBR=SJ��1 DUEOUT TIME=�5�65/�8�� SCHED ID=��1 SUBMIT TIME=�5�65/��

GENERAL: JCLMBR=DUCCXX�1 JCLID=�� SYSTEM=TESTNTWK LTERM= NBRRUN=��7 LSTRUN=�5261/16�7

RESOURCE: MAINID=ALL PRTY=�� CLASS=A ELAPTM=��1 TP1 =�� TP2 =��

EXECUTION: RELOAD=NO EXEC=YES MAINT=NO RETJCL=NO HOLD=NO

� �


Forecasting

JOB Worksheet, LIST=WP

� � FJOB,FROM=�3�6�5,TO=�3�6�5,LIST=WP DATE �2-27-�5 PAGE ��2

JOB=DUCCXX�1 COMPLETED _______________

SCHEDULE: LATEST STRT=�5�65/�759 SCHD MBR=SJ��1 DUEOUT TIME=�5�65/�8�� SCHED ID=��1 SUBMIT TIME=�5�65/��




�� JOB EXECUTION REQUIREMENTS ��

________ EXTERNAL USR=THIS IS THE FIRST JOB IN THE TEST________ EXTERNAL USR=SYSTEM, IF YOU WISH TO BEGIN YOU________ EXTERNAL USR=SATISFY THESE REQUIREMENTS!

�� JOB PROSE DESC=THIS IS JOB INFORMATION FOR DUCCXX�1 ��

THIS IS THE FIRST JOB IN THE TESTNTWK TO BE EXECUTED AND IS A SCHEDULED JOB.IT CONSISTS OF TWO STEPS. THE FIRST STEP RECEIVES A SET OF CONTROL CARDS ASINPUT, CREATES A DATASET U7TEST�1 AS OUTPUT AND DEMANDS THE NEXT JOB DUCCXX�2TO BE STARTED AFTER THE SUCCESSFUL COMPLETION OF THE STEP. THE SECOND STEPRECEIVES ANOTHER SET OF CONTROL CARDS AS INPUT AND CREATES A DATASET U7TEST�2AS OUTPUT. IN TURN, U7TEST�2 AUTO-TRIGGERS JOB DUCCXX�3.

#QDESC�� JOB DUCCXX�1�� SCHEDULED JOB, FIRST IN THE NETWORK�� FIRST STEP�� INPUT-CONTROL CARDS OUTPUT-U7TEST�1�� SECOND STEP�� INPUT-CONTROL CARDS OUTPUT-U7TEST�2

#END,QDESC� �

40 Commands Guide

Chapter 2. Commands

This section contains the following topics:

/ASSIGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46/AUTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48/BRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50/CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52/CLOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54/COPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55/DISPLAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57/DMP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72/DRCLASS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73/DRMODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74/DUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76/EADMIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77/ECHO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79/EMAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80/FETCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81/JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82/LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84/LOGOFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85/LOGON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86/MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88/MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90/NXTMSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91/OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92/OPERID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94/OPERIDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95/PAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98/PAnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100/PFnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102/PROF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104/PROFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108/PURGPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111/REFRESH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112/RELINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113/RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115/SDESK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116/SHUTDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117/START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120/STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122/SWAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124/UID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125/WLB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126/WTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128ADDRQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Chapter 2. Commands 41

ADDSCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131AL/ALC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133ALLOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135APA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136ARFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142ARTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143AR.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144BLDG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145CALMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147CANCEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148CAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152CONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154CTLG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155DB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160DCONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162DEALLOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163DEMAND, DEMANDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164DIRECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174DLTX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176DMDNW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177DMPCAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179DMPDSCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180DMPDSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181FALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183FIND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187FJOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189FLOWD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195FLOWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197FPOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199FPRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201FQALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204FQJOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208FQPOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211FQPRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213FQRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215FQSTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219FQTAPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221FRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223FRJOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230FRQJOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235FSTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240FSTRUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242FTAPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245FWLP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248GRAPHc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260HOLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263IN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265IO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

42 Commands Guide

JCLOVRD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274LACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276LACTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285LARF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289LARFQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295LCTLG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298LDSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305LDTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316LISTDIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319LJCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321LJCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324LJES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326LJOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331LJOBR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351LLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353LLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355LNTWK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359LOAD, LOADH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363LOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367LOGIN/LOGOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368LPDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371LPOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373LPRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379LPROS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384LPRRN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389LQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394LQP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406LQR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411LRDY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416LRDYP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423LRDYR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427LREQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431LREQP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440LREQR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442LRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446LRLOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449LRMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459LSCHD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462LSYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470LWLB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478MENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480NOPRMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481NXTCYC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485POST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487PRINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491PRMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493


PRRNJCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495PRSCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496PRSQA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498PRSQD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499PS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500QJCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501QM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503QM.1 CPU Jobs Status Prompt Panel . . . . . . . . . . . . . . . . . . . . . 505QM.2 CPU Job Predecessors Prompt Panel . . . . . . . . . . . . . . . . . 516QM.3 CPU Job Attributes Prompt Panel . . . . . . . . . . . . . . . . . . . 521QM.4 CPU Job In Restart Status Prompt Panel . . . . . . . . . . . . . . . 527QM.5 Queued JCL Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531QM.6 Input Networks Prompt Panel . . . . . . . . . . . . . . . . . . . . . . 533QM.7 Output Networks Prompt Panel . . . . . . . . . . . . . . . . . . . . . 540RELEASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546REMIND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548RENAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550REQUEUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551RESANL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554RESCHNG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556RESOLV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568RQMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569RQVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570RSVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572RUN, RUNH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575RUNNW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580RUSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582SCHDMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583SCRATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584SPACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586SSCAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593SUBMIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594SUBSCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596SUBTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598TIQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600TRIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601UNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603UT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604UT.1 - Allocate/Catalog Dataset Panel . . . . . . . . . . . . . . . . . . . . 606UT.2 - Catalog Dataset Panel . . . . . . . . . . . . . . . . . . . . . . . . . 609UT.3 - Rename Dataset Panel . . . . . . . . . . . . . . . . . . . . . . . . . 611UT.4 - Scratch Dataset Panel . . . . . . . . . . . . . . . . . . . . . . . . . . 613UT.5 - Uncatalog Dataset Panel . . . . . . . . . . . . . . . . . . . . . . . . 615UT.6 - Build GDG Index Panel . . . . . . . . . . . . . . . . . . . . . . . . . 617UT.7 - Delete Index Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619

44 Commands Guide

UT.8 - Connect a Catalog Panel . . . . . . . . . . . . . . . . . . . . . . . . 621UT.9 - Disconnect a Catalog Panel . . . . . . . . . . . . . . . . . . . . . . 623UT.10 - Find DSN on DASD Panel . . . . . . . . . . . . . . . . . . . . . . 625UT.11 - Allocate Volume Panel . . . . . . . . . . . . . . . . . . . . . . . . . 627UT.12 - Deallocate Volume Panel . . . . . . . . . . . . . . . . . . . . . . . 629UT.13 - Display Format 1 DSCB Panel . . . . . . . . . . . . . . . . . . . . 631UT.14 - Display Directory Info Panel . . . . . . . . . . . . . . . . . . . . . . 634UT.15 - Display Dataset Attributes Map Panel . . . . . . . . . . . . . . . . 636UT.16 - Display Available DASD Space Panel . . . . . . . . . . . . . . . . 638UT.17 - Display Physical Data Records Panel . . . . . . . . . . . . . . . . 640UT.18 - Display Catalog Block Panel . . . . . . . . . . . . . . . . . . . . . 642UT.19 - Display Catalog Entries Panel . . . . . . . . . . . . . . . . . . . . 644VERIFY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646XPOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648XPRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652XQ, XQJ, XQN, and XQM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655XREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659XRQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660XRST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661XSPOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662XSPRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663XUPD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664XWLB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665

The user commands are described in alphabetical sequence, with all slash (/)commands appearing first.

In this chapter, user commands are shown with command description format,parameter and option descriptions, examples, and typical terminal displaypanels.

As with all Unicenter CA-7 commands, these must be authorized by securitybefore a terminal user can perform any of them.


/ASSIGN

/ASSIGN

The /ASSIGN command performs any of these functions:

■ Reassigns a logical terminal to a different physical terminal.

■ Reassigns a MAINID to another CPU to redirect jobs when using submitdata sets.

■ Alters the maximum number of jobs that can be submitted to a CPU.

This command has the following formats:

Format 1

/ASSIGN

��──/ASSIGN─ ──, ──┬ ┬─LT──── =station ──, ──┬ ┬─T──── =terminal ────────�� └ ┘─LTERM─ └ ┘─TERM─

Format 2

/ASSIGN

��──/ASSIGN─ ──, ──┬ ┬─MA───── = ──┬ ┬──SYn ──,CPU=ddname ──────────────�� └ ┘─MAINID─ └ ┘─SY�─

Format 3

/ASSIGN

��──/ASSIGN─ ──,CPU=ddname ──,BARR=barrier ────────────────────────��

LTERMDefines the logical terminal (station) that is to be reassigned. Required forFormat 1. You can use LT or LTERM interchangeably, but Format 1requires one or the other.

TERMDefines the physical terminal to which the logical terminal is beingassigned. You can use T or TERM interchangeably, but Format 1 requiresone or the other.

46 Commands Guide

/ASSIGN

MAINIDDefines the current MAINID assigned to a submit data set on the CPUstatement in the initialization file. Required for Format 2. You can use MAor MAINID interchangeably, but Format 2 requires one or the other.

SYnDefines a single digit number (from 0 to 7 as determined from theinitialization file definitions).

SY*Specifies that a MAINID is not indicated.

CPUDefines the submit data set assigned to a CPU. The value is the ddnamefor the data set that is defined in the Unicenter CA-7 JCL and theinitialization file CPU statement. Required for Formats 2 and 3.

BARRDefines the maximum number of jobs that can be submitted at one time toa CPU. The value specified can be up to 4 digits. Required for Format 3.

Usage Notes

You can use only those forms of the command on the preceding list.

When reassigning a logical terminal, you must assign it to the same type ofphysical device as that originally assigned (3270 to batch, 3270 to browse, andso forth, are not allowed).

If a MAINID is defined as associated with more than one CPU and the MAINIDis reassigned using /ASSIGN, Unicenter CA-7 changes only the first occurrenceof the MAINID to the new CPU.

If a CPU goes down (fails) and the MAINIDs associated with it are reassigned,jobs that were already submitted and active on the failed CPU must berequeued and resubmitted by Unicenter CA-7. If in a shared-spool JESenvironment, you can reroute such jobs through JES instead of Unicenter CA-7.

Examples/ASSIGN,LT=KEYPNCH,TERM=RTERM1

/ASSIGN,MA=SY�,CPU=UCC7SUB1

/ASSIGN,MAINID=SY�,CPU=UCC7SUB2

/ASSIGN,CPU=UCC7SUB1,BARR=5�


/AUTO

/AUTO

The /AUTO command causes a terminal to reissue a command at a specifiedinterval. This is only valid when accessing Unicenter CA-7 online through nativeVTAM.

This command has the following format:

/AUTO

��──/AUTO─ ──┬ ┬──────────────── ──┬ ┬──────────── ──, ──┬ ┬─M─── =text ─��│ │┌ ┐─5─── └ ┘──,COUNT=ccc └ ┘─MSG─└ ┘──,INT= ──┴ ┴─iii─

INTDefines the number of seconds between each time the command is to beissued.

Default: 5

Limits: 1 to 3 numeric characters from 3 to 300

Required: No

COUNTDefines the number of repetitions for the command. This limits the numberof times that the command is issued.

Default: No limit


Required: No

MSGDefines the command text that is issued. M and MSG can be usedinterchangeably, but one or the other must be specified. If commas are partof the text, enclose the message in parentheses.


Required: Yes

48 Commands Guide

/AUTO

Usage Notes

To stop a terminal after a /AUTO command, press Enter or enter a newcommand.

If a new command is being entered when the time interval expires, the terminalis taken out of /AUTO mode, but the last output is sent to the terminal whenEnter is pressed (not the output from the new command).

The /AUTO command is only valid for online terminals.

Examples/AUTO,INT=3,MSG=(LQ,ST=RSTR)

/AUTO,COUNT=5,INT=12�,M=(DEMAND,JOB=XYZ)

/AUTO,M=XWLB


/BRO

/BRO

The /BRO command broadcasts a message to terminals on the Unicenter CA-7system. The message is queued until the receiving terminal user requestsdisplay. For sending a message to one specific terminal, see “/MSG” onpage 88.

For a Unicenter CA-7 virtual terminal to receive a broadcast message, theTERM option must be specified or the terminal must be connected.


/BRO

��──/BRO─ ──, ──┬ ┬─M─── =text ──┬ ┬───────────────── ─────────────────�� └ ┘─MSG─ └ ┘──, ──┬ ┬─T──── =ALL └ ┘─TERM─

MSGDefines the text of the broadcast message. MSG and M can be usedinterchangeably, but one or the other is required. If commas are included aspart of the text, enclose the entire message text in parentheses.


Required: Yes

TERMIn general this parameter should not be used. This parameter affects theway a broadcast message is sent to the VTAM virtual terminals. If notspecified, then only those virtual terminals that are connected to UnicenterCA-7 get the message. If specified, then all the VTAM virtual terminals getthe message. This can cause excessive space usage of the scratch queue.

Default: Virtual terminals that are connected to Unicenter CA-7 only

Limits: 3 alphabetic characters

Required: No

50 Commands Guide

/BRO

Examples/BRO,MSG=ONE HOUR DELAY IN JOB PROCESSING

/BRO,M=ACCTS PAYABLE RUN CANCELLED FOR TODAY

The message appears on each receiving terminal in this format:

CA-7.BRO termname text

termnameIdentifies the broadcasting terminal.

textIdentifies the free-form text entered for the MSG or M parameter.

Note: Use the /MSG command to send a message to a specific terminal.


/CHANGE

/CHANGE

The /CHANGE command modifies the security definition for a given operator bychanging the level of authorization that controls an operator's ability to use thecommands of Unicenter CA-7 applications.

Note: This command is only applicable if Unicenter CA-7 native security isbeing used for command access.


/CHANGE

��──/CHANGE─ ──, ──┬ ┬─A──── =application ──, ──┬ ┬─O────── =operid ──────� └ ┘─APPL─ └ ┘─OPERID─

�─ ──, ──┬ ┬─P──── =nn ──, ──┬ ┬─T──── = ──┬ ┬─term──── ───────────────────�� └ ┘─PRTY─ └ ┘─TERM─ └ ┘─��ALL��─

APPLDefines the Unicenter CA-7 application for which a different level ofauthorization is to be assigned. A and APPL can be used interchangeably,but one or the other must be specified. The value must be the driverprogram suffix specified in the SECURITY macro (for example, SFC0,SDM0, and so forth).


Required: Yes

OPERIDDefines the operator ID for which the authorization is to be changed. O andOPERID can be used interchangeably, but one or the other must bespecified. The value must be the operator ID defined in the SECURITYmacro.

PRTYDefines the new level of authorization for the designated Unicenter CA-7application. P and PRTY can be used interchangeably, but one or the othermust be specified. The value must be numeric and must be between 0 and15. (For default authorization values, see the Security Guide.)

52 Commands Guide

/CHANGE

TERMDefines the physical terminal at which the change in authorization applies.T and TERM can be used interchangeably, but one or the other must bespecified.

termDefines the symbolic terminal name defined by the NAME parameter onthe TERM statement in the initialization file.

**ALL**Must be specified to change authorization levels for an OPID that isdefined in the Security macro with a TRMD=**ALL**.

Usage Notes

Alterations to a security definition that are made by a /CHANGE command arein effect only for the current execution of Unicenter CA-7 and only after the nextlogon of the terminal.

When changing level of authorization, the application for which level ofauthorization is being changed must be specified on the SECURITY macro forthe designated operator. Access to a Unicenter CA-7 application must beinitially authorized by the SECURITY macro.

Example/CHANGE,OPERID=OPER��1,TERM=RTERM1,A=SDM�,PRTY=1�


/CLOSE

/CLOSE

The /CLOSE command closes VTAM terminals.

A /CLOSE command with no parameters disconnects the issuing terminal fromUnicenter CA-7.

Important! Production users should use the command with no parameters.Only system users should use the parameters.


/CLOSE

��──/CLOSE─ ──┬ ┬────────────── ──┬ ┬────────────────────── ─────────��└ ┘──,GROUP=group └ ┘──, ──┬ ┬─T──── =terminal

└ ┘─TERM─

GROUPDefines a line group to close and identifies which group. Value must be thegroup name defined by the NAME parameter on the GROUP statement inthe initialization file. If GROUP specifies a VTAM group, all Unicenter CA-7connected VTAM terminals are disconnected, not just the identified group.

If /CLOSE is used with a group defined as DEVICE=CCI it will forcetermination of the Unicenter CA-7 CAICCI terminal session that is active onthat group. This should not be needed in normal operation.


Required: No

TERMDefines the VTAM terminal to disconnect from Unicenter CA-7. The valuemust be the NAME value on the TERM statement in the initialization file forthe VTAM terminal to be disconnected. T and TERM can be usedinterchangeably.


Required: No

Examples/CLOSE,GROUP=BGROUP1

/CLOSE,T=VTERM1

/CLOSE

54 Commands Guide

/COPY

/COPY

The /COPY command sends a currently displayed page of output to anotherlogical terminal (station) in the Unicenter CA-7 terminal network. (Logicalterminals are identified by the STANIDS= parameter of the STATIONSstatement in the initialization file.)


/COPY

��──/COPY─ ──┬ ┬────────────────────── ────────────────────────────�� └ ┘──, ──┬ ┬─LT──── =station └ ┘─LTERM─

LTERMDefines a specific logical terminal (station) to which the currently displayedpage of output is to be copied. LTERM and LT can be usedinterchangeably. Value must be a logical terminal name that is the samedevice type as the terminal issuing the command. If omitted, the output isrouted to the first hardcopy printer (if one is defined) in the same LINE asthe sending terminal.


Required: No


/COPY

Usage Notes

Use of /COPY without specifying a logical terminal name causes the output tobe sent to the first hardcopy printer if one is defined on the same line group asthe sending terminal.

After the page of output has been copied, the next page of output is displayedon the requesting terminal.

The sending terminal receives an error message if any of the following occurs:

■ If the specified logical terminal does not exist.

■ If /COPY is used without a logical terminal being specified and there is nohardcopy device on the line.

■ If the sending and receiving terminals are not the same device type.

A /COPY,LT=MASTER command is not valid if the MASTER is a browse dataset.

If the specified logical terminal does not exist or if /COPY was used and thereis no hardcopy device on the line, the sending terminal receives a messageindicating this situation.

Examples/COPY,LT=KEYPUNCH

/COPY,LTERM=MAILROOM

/COPY,LTERM=PRINT1

/COPY

56 Commands Guide

/DISPLAY

/DISPLAY

The /DISPLAY command obtains internal information, status of variouscomponents of Unicenter CA-7, or both. As an information command, it has alarge group of keywords available to designate specific information for display.You can specify certain combinations of keywords on a single /DISPLAYcommand, but at least one must be selected.


/DISPLAY

��──/DISPLAY─ ──┬ ┬───────────────────────── ───────────────────────� └ ┘──, ──┬ ┬─A──── =programname └ ┘─APPL─

�─ ──┬ ┬───────────────────── ──┬ ┬──────────────── ──────────────────�└ ┘──,CPU= ──┬ ┬─ALL────── └ ┘──,DB= ──┬ ┬─LOG──

├ ┤──UCC7IRDn └ ┘─VSAM─└ ┘──UCC7SUBn

�─ ──┬ ┬────────────────────── ──┬ ┬──────────────────────── ─────────� └ ┘──, ──┬ ┬─FM───── =module └ ┘──, ──┬ ┬─L──── = ──┬ ┬─line─

└ ┘─FMTBLK─ └ ┘─LINE─ └ ┘─ALL──

�─ ──┬ ┬──────────────────────────── ──┬ ┬──────────────────── ───────� └ ┘──, ──┬ ┬─LT──── = ──┬ ┬─station─ └ ┘──, ──┬ ┬─PL──── =pools

└ ┘─LTERM─ └ ┘─ALL───── └ ┘─POOLS─

�─ ──┬ ┬─────────────────── ──┬ ┬────────── ──────────────────────────�└ ┘──, ──┬ ┬─PR──── =scan └ ┘──,Q=queue

└ ┘─PRINT─

�─ ──┬ ┬────────────────────── ──┬ ┬──────────────────────────── ────�� └ ┘──, ──┬ ┬─ST───── =status └ ┘──, ──┬ ┬─T──── = ──┬ ┬─terminal─

└ ┘─STATUS─ └ ┘─TERM─ ├ ┤─ALL────── ├ ┤─�──────── └ ┘─?────────

APPLDefines the Unicenter CA-7 application programs whose status is to bedisplayed. A and APPL can be used interchangeably.

SASSxxxxDisplays a specific Unicenter CA-7 module. The xxxx must be the lastfour characters of the module suffix (for example, SLI0).

SASSxxx|SASSxx|SASSxDisplays a generic group of modules belonging to the same UnicenterCA-7 application. All modules beginning with the characters specifiedare displayed (for example, SASSSLI displays all general listingmodules).

ALLDisplays all Unicenter CA-7 modules that are defined in the initializationfile.


/DISPLAY

CPUDefines the submit data set or internal reader associated with the CPUs forwhich status is to be displayed.

UCC7SUBn|UCC7IRDnDefines the ddname that defines the desired submit data set.

ALLDefines all submit data sets and their related MAINIDS are to bedisplayed.

DBSpecifies the data sets for which status is to be displayed.

LOGDisplays status of the log data set currently in use.

VSAMDisplays VSAM database values in effect.

FMTBLKDefines the Unicenter CA-7 format or calendar blocks whose status is to bedisplayed. FM and FMTBLK can be used interchangeably.

SFMxyyyy|SFMxyyy|SFMxyyDisplays a generic group of format blocks belonging to the sameUnicenter CA-7 application. The x portion of the name must be A forbatch format blocks, H for 3270 format blocks or X for both. The yyyyportion of the name must be the four-character module suffix (forexample, SLI0). All format blocks beginning with the charactersspecified are displayed.

SCALyyzz|SCALyyz|SCALyyDisplays a generic group of base calendar blocks. The yy portion of thename represents the calendar year (that is, 05 for 2005). The zz portionof the name represents the unique calendar identifier. All calendarblocks beginning with the characters specified are displayed.(Remember that you can use LISTDIR,DSN=*SCAL* to list all themembers in the Unicenter CA-7 Calendar PDS.)

ALLDisplays all format and base calendar blocks that are defined in theinitialization file with a FMTBLK or CALBLK statement.

LINEDefines the lines for which status is to be displayed. L and LINE can beused interchangeably.

Required: No

lineDefines a single line name.


58 Commands Guide

/DISPLAY

ALLDisplays all lines in the Unicenter CA-7 network. (The line name isdefined by the NAME parameter on the LINE statement in theinitialization file.)

LTERMDefines the logical terminals for which status is to be displayed. LT andLTERM can be used interchangeably.

stationDefines a single logical terminal name.


ALLDisplays status for all logical terminals in the Unicenter CA-7 network.(The logical terminal name is defined by the STANIDS or LTERMparameter on the STATIONS statement in the initialization file.)

POOLS|PLSpecifies the main memory storage pools for which status is to bedisplayed. PL and POOLS can be used interchangeably. Value must beone of the following:

APGSpecifies to display the Unicenter CA-7 application pool that providesmain memory for storing nonresident and nonpermanent programswhile they are in use.

DSNSpecifies to display the dataset data set buffer pool that provides mainmemory for activity involving the dataset data set.

JOBSpecifies to display the job data set buffer pool that provides mainmemory for activity involving the job data set.

MSGSpecifies to display the message pool that provides main memory forUnicenter CA-7 format blocks and their input/output activity. Valuesdisplayed are the same as those for NSP because they are a sharedpool.

NSPSpecifies to display the non-specific pool that provides main memory forall requests not specifically directed to one of the other pools. Valuesdisplayed are the same as those for MSG because they are a sharedpool.

RESSpecifies to display the resident pool that contains the Unicenter CA-7control blocks and all resident Unicenter CA-7 programs.

ALLSpecifies to display all storage pools previously listed.


/DISPLAY

PRINTSpecifies a display of schedule scan control values. PR and PRINT can beused interchangeably. If used, value can be either SCH or ALL.

QSpecifies the queue data sets for which status is to be displayed. Thedisplay includes initialization file FORMAT statement INDEX options takenand device types for the queue data sets. The count shown as tracksavailable for status queues (REQ, RDY, ACT, PRN, PST, and PRE)indicates an amount never used since the last COLD start of UnicenterCA-7 (COLD, FORM, MOVQ). For the SCR, DQT, and TRL queues, thevalues shown are current levels and fluctuate up and down based on actualusage. The INDEX options for the SCR and DQT are set to a dash (-)because the INDEX keyword in the initialization file has no effect on thesequeues. The TRL entry is set dynamically based on the environment whereUnicenter CA-7 is executing.

ACTSpecifies to display the active queue.

DQTSpecifies to display the disk queue table that is used to control outputmessages for Unicenter CA-7 terminals.

PRESpecifies to display the preprocess queue.

PRNSpecifies to display the prior-run queue.

PSTSpecifies to display the postprocess queue.

REQSpecifies to display the request queue.

RDYSpecifies to display the ready queue.

SCRSpecifies to display the scratch queue that provides temporary workspace for the Unicenter CA-7 applications and messages for theterminals.

TRLSpecifies to display the trailer queue that is used to store JCL andrequirement data for jobs in the request, ready, active, and prior-runqueues.

ALLSpecifies to display the all of the queue data sets previously listed.

60 Commands Guide

/DISPLAY

STATUSSpecifies which status is to be displayed. STATUS and ST can be usedinterchangeably.

CA7Specifies to display information about the Unicenter CA-7 system suchas local SMF ID, Unicenter CA-7 VTAM application ID, Unicenter CA-7instance name, and Unicenter CA-7 SVC number.

DPROCSpecifies to display the CA-Driver procedure libraries associated withUnicenter CA-7 JCL libraries.

DRSpecifies to display information about Unicenter CA-7 current disasterrecovery mode options and the currently active disaster recoveryclasses.

EMAILSpecifies to display information about the Unicenter CA-7 emailinterface.

JCLSpecifies to display the data sets containing Unicenter CA-7 submittedJCL and their associated numeric index values. Data sets referenced bya symbolic index display numeric index 255.

JCLVARSpecifies to display the data sets containing Unicenter CA-7 submittedJCL and their associated numeric or symbolic index values.

KEYSpecifies to display the program function and program access keysettings.

Note: If key information is desired on a specific terminal, acombination of STATUS=KEY and the TERM parameter can be used.

SDESKSpecifies to display information about the Unicenter Service Deskinterface, including the current SERVDESK rules that have beenloaded.

SECSpecifies to display the current Unicenter CA-7 security environment.For more information, see the Security Guide.


/DISPLAY

TERMSpecifies the physical terminals for which status is to be displayed. T andTERM can be used interchangeably. (The symbolic terminal name isdefined by the NAME parameter on the TERM statement in the initializationfile.)

terminalDefines a terminal name.

ALLSpecifies all physical terminals.

*Specifies a condensed form of the ALL display.

?Specifies an interpreted display for the issuing terminal.

62 Commands Guide

/DISPLAY

Examples

/DISPLAY Command CPU=ALL Panel

� � /DISPLAY,CPU=ALL

�� CPU DISPLAY �� PAGE ��1 DDNAME BARRIER SUBMIT-COUNT MAINID

UCC7IRD1 �2� �� SY1 SY3 SY� SY� UCC7SUB2 �25 ��1 SY2

� �

This panel contains the following fields:

DDNAMEIdentifies the name of the DD statement in the Unicenter CA-7 JCL thatdefines this submit data set or internal reader.

BARRIERIdentifies the maximum number of Unicenter CA-7 jobs to be submitted tothe host system job queue at any one time.

SUBMIT-COUNTIdentifies the current number of jobs submitted to the host system jobqueue at this time.

MAINIDIdentifies the Unicenter CA-7 main IDs that are assigned to this submit dataset or internal reader.

� � /DISPLAY,LT=ALL

�� LTERM DISPLAY �� PAGE ��1 WORKHOURS DISP FLAGS LTERM TERM CALENDAR FROM TO #MSGS CUR NEXT 1 2 3 STATUS

HTERM1 HTERM1 SCALyy�1 �8�� 17�� 1 �328 �328 A� �� OUTPUT, CONTROL1 HTERM1 SCALyy�1 �8�� 17�� CONTROL2 HTERM1 SCALyy�1 �8�� 17��

CONTROL3 HTERM1 �NONE� �� 24�� HTERM2 HTERM2 SCALyyPE �6�� 18�� 328 �328 �� RECOVER1 HTERM2 SCALyyPE �6�� 18��


LTERMIdentifies the logical terminal or workstation name. This is either the valueentered on the STATIONS statement in the initialization file (keywordSTANIDS=) or a system-generated name for virtual terminals.


/DISPLAY

TERMIdentifies the terminal name, either specified on the TERM statement in theinitialization file (keyword NAME=), or a system-generated name for virtualterminals.

CALENDARIdentifies the calendar specified on the STNCAL statement in theinitialization file (keyword CAL=) for this workstation.

WORKHOURSIdentifies the FROM= and TO= values entered on the STNCAL statement inthe initialization file for this workstation.

#MSGSIdentifies the number of currently queued messages for this workstation.

DISPIdentifies the relative displacement into the scratch queue where currentmessages reside.

FLAGSIdentifies the bit settings that relate to LTFLAG1, LTFLAG2, and LTFLAG3as defined in the DSECT SASSTBLK.

STATUSIndicates a one-word description of the flag settings.

� � /DISPLAY,PR=SCH

�� SCHEDULE SCAN DISPLAY �� PAGE ��1 ----------MINUTES----------- ---STATUS----

NEXT SCAN SPAN INCR QDWL REPR LDTM RTRY REQ/Q RDY/Q ABR HOLDyy.163 AT 16�� 24� �12� ��3� �� 2 ACTIVE STOPPED NO NO

� �


NEXT SCANIdentifies the date and time of the next scheduled wake up for schedulescan.

SPANIdentifies the value in minutes of how far ahead to look for calendarscheduled jobs and networks with a deadline date and time that correspondto the time frame being scanned.

INCRIdentifies the number of minutes between wake-ups of schedule scan.

QDWLIdentifies the number of minutes added to the SPAN value to ensure timelyscheduling of work into the queues.

64 Commands Guide

/DISPLAY

REPRIdentifies the number of minutes between prompt cycles for late tasks orjobs, or jobs awaiting restart.

LDTMIdentifies a global value to be added to all jobs' lead time.

RTRYIdentifies the number of minutes between the retry of attachment of JCLafter a dynamic allocation failure.

STATUSIdentifies whether the request and ready queues are ACTIVE or STOPPED(see the STOP and START commands).

ABRIdentifies whether the initial queue entry message is to be issued inabbreviated form (see the SSCAN command SCAN=ABR).

HOLDIdentifies whether jobs enter the request queue with an initial holdrequirement (see the SSCAN command SCAN=HLD).

� � /DISPLAY,T=ALL

�� TERM DISPLAY �� PAGE ��1--I/O COUNTS--- OUT -LIMIT- ---FLAGS---

TERM TYPE ADDR READS WRITE ERR Q'D TIM MON � 1 2 V STATUS/(VTAMID) HTERM1 327�R ��4 ��41 ��42 �� 1 �2� �2� D� 28 �2 �4 MSTR, HTERM2 327�R ��4 ��75 ��75 �� 2� �2� D4 3� �2 �4 ALT,SKIP, PTERM1 327�R ��4 �� 15 �� 3� ��2 54 24 �2 �4 LOFF,SKIP, TTERM1 TRAILR ��4 �� 3� ��2 D� 2� �� 4 LOFF, CTERM1 CONSOL ��4 �� 1 �� 3� ��2 D� 2� �� 4 LOFF, BTERM1 BATCH ��4 �� 3� ��2 �� 2� �� 4 LOFF,STOP� �


TERMIdentifies the terminal name from the initialization file TERM statement(keyword NAME=). For virtual terminals this is a system-generated name.

TYPEIdentifies the device type for this terminal defined by the DEVICE= on theTERM statement in the initialization file.

ADDRIdentifies the relative address for local BTAM terminals.

READSIdentifies the number of reads for this terminal during this session ofUnicenter CA-7.

WRITEIdentifies the number of writes for this terminal during this session ofUnicenter CA-7.


/DISPLAY

ERRIdentifies the number of errors during this session of Unicenter CA-7. Thereshould be messages produced as WTOs (for example, CA-7.V001messages) to explain the errors.

Q'DIdentifies the number of messages currently queued for this terminal.

TIMIdentifies the number of minutes of inactivity before the terminal isautomatically disconnected from Unicenter CA-7.

MONIdentifies the number of minutes of inactivity in the interface of BrightStorCA-1 or Unicenter CA-11 before the terminal is automatically returned toUnicenter CA-7.

FLAGSIdentifies the flag settings used by the terminal.

STATUSIndicates one of the following:

ALTIndicates the TERM statement uses CONS=ALTRN.

CONNIndicates the terminal is connected (VTAM).

LOFFIndicates the terminal is logged off.

MSTRIndicates the TERM statement uses CONS=MASTR.

SKIPIndicates the terminal is busy processing a command.

STOPIndicates the terminal has been stopped.

66 Commands Guide

/DISPLAY

/DISPLAY,DB=ALL

� � /DISPLAY,DB=VSAM

DDNAME=CA7JLIB DSNAME=USER.CA7.JOBLIBDSORG=VSAM BUFND=99 BUFNI=99 ALLOCJCL=YES ALLOCDYN=NO

TYPE/STRINGS VALUES: JBD/�3 JBM/�3

DDNAME=CA7DLIB DSNAME=USER.CA7.DSLIBDSORG=VSAM BYFND=99 BUFNI=99 ALLOCJCL=YES ALLOCDYN=NO

TYPE/STRINGS VALUES:DSD/�3 DSM/�3 NWD/�12 NWM/�2 PPD/�3 PPM/�3 SID/�2 SIM/�2SJD/�3 SJM/�3 SOD/�2 SOM/�2

DDNAME=CA7IDS DSNAME=USER.CA7.INDEXDSDSORG=VSAM BUFND=99 BUFNI=99 ALLOCJCL=YES ALLOCDYN=NO

TYPE/STRINGS VALUES: I /�3

PROGRAM: SCMD MSG-INDX: �� --��1�-- yyddd/1�:35:�� MESSAGE: REQUEST COMPLETED

� �

� � /DISPLAY,L=ALL

�� LINE DISPLAY �� PAGE ��1 I/O COUNTS FLAGS LINE TYPE READS WRITES ERRORS � 1 STATUS

HLINE1 327�R ��1�8 ��124 �� 2� 5�TLINE TRAILR �� 2� 5�CLINE CONSOL �� 1 �� 2� 5�BLINE1 BATCH �� 4� STOPPED.

� �

� �/DISPLAY,T=�

�� TERM DISPLAY �� PAGE ��1--I/O COUNTS--- OUT TIM MON

NAME ID/TYPE READS WRITE ERR Q'D LIM LIM STATUS

HTERM A46L6�16 ��49 ��48 �� 3� ��2 MSTR,SKIP,CONN, OLC��1 OLC��1 ��3 ��3 �� 3� ��2 LOFF,ALT,STOP OLC��2 OLC��2 ��13 ��13 �� 3� ��2 LOFF,ALT,STOP OLC��3 OLC��3 �� 3� ��2 LOFF,ALT,STOP OLC��4 OLC��4 �� 3� ��2 LOFF,ALT,STOP OLC��5 OLC��5 �� 3� ��2 LOFF,ALT,STOP

� �


/DISPLAY

/DISPLAY,T=?

� �/DISPLAY,T=?

TIM MON SIM TERM--- ID------ TYPE---- ADDR READS WRITE ERR MSGS LIM LIM LOG LOGGED HTERM A46L6�16 327�V �� 5� ��49 �� 3� ��2 YES ON

N - TERMINAL DOWN/STOPPED Y - CONNECTED TO VTAM Y - TERMINAL OPEN N - CONNECT IN PROCESS Y - SKIP TERMINAL N - DISCONNECT REQUESTED N - SEND IN EFFECT N - INTERVENTION REQUIRED N - ALTERNATE CA-7 CONSOLE Y - MASTER CA-7 CONSOLE N - VTAM VIRTUAL TERMINAL Y - AT LEAST 1 INPUT RECEIVED N - IN FORMAT MODE N - PRINTER DEVICE Y - READ REQUESTED N - SHORT ENTERED Y - WRITE REQUESTED N - REQUEST WRITE TR N - FORCED LOGOFF REQUESTED N - LOCAL SNA (3274-1A) N - AWAITING CA-7 SHUTDOWN N - SHUTDOWN MSG TO BE SENT Y - USE BRACKET MODE Y - BRACKET MODE BEGUN N - RECEIVED BRACKET ERROR N - SEND TERMINAL BUSY MSG Y - RELEASE IF RELREQ N - NEED READ FOR STATUS/SENSE N - EOD ON BATCH TERMINAL N - BATCH TERM OVERFLOW N - SEND RPL HAS SGETM BUFFER N - CCI SESSION NOT ACTIVE

� �

/DISPLAY,Q=ALL Command

� � /DISPLAY,Q=ALL�� QUEUE DISPLAY �� (338�) PAGE ��1

QUEUE TRACKS AVAIL. INDEX ENTRIES AVAIL..

SCR ��3�� 296 - ACT ��4 ��3 A DQT ��3� ��27 - PRE ��4 ��3 N PRN ��1� ��6 N PST ��4 ��3 N RDY ��4 ��3 A REQ ��6 ��4 Y TRL ��9� ��81 N

SCM6-�� /DISPLAY COMPLETED AT hh:mm:ss ON yyddd� �

68 Commands Guide

/DISPLAY

� � /DISPLAY,ST=JCL

�� JCL DISPLAY �� PAGE ��1 DATASET NAME INDEX ALT DSORG VOLSER LTERM

D463RV1.PROC.CLIST 25� N/A PDS M8�T82 MASTERCA��7.JCLDS1 �� 25� PDS M8��8 MASTERSYS2.PROCLIB 2�� N/A PDS M8�PP1 MASTERCAI.CA7.CAIHELP 255 N/A PDS M8��8 MASTER

� �


/DISPLAY

/DISPLAY,ST=JCLVAR Command

� �/DISPLAY,ST=JCLVAR

�� SYMBOLICALLY INDEXED LIBRARY DEFS FROM VSAM FILE �� PAGE ��1 VARIABLE/INDEX DATASET NAME ALT DSORG VOLSER LTERM

�� CA��7.JCLDS1 25� PDS M8��8 MASTER2�� SYS2.PROCLIB N/A PDS M8�PP1 MASTER25� D463RV1.PROC.CLIST N/A PDS M8�T82 MASTER&HELP CAI.CA7.CAIHELP N/A PDS M8��8 MASTER&PAYROLL CA��7.PAYROLL N/A PDS M8��8 MASTER&PAYABLE CA��7.ACCTS.PAYABLE N/A PDS M8��8 MASTER&RECEIVABLE CA��7.ACCTS.RECEIVBL N/A PDS M8��8 MASTER

� �

� � /DISPLAY,ST=KEY�� KEY DISPLAY �� (VTERM1) PAGE ��1

KEY FUNCTION

--- INITIALIZATION --- PF24 VTAM LOGOFF KEY

--- DEFAULT --- PF�1 /PURGPG PF�2 /COPY PF�3 /NXTMSG PA�1 /PAGE+1 PA�2 /PAGE-1� �

� � /DISPLAY,PL=ALL�� POOL DISPLAY �� PAGE ��1

POOL SIZE AVAIL.

NSP 1289792 127328� JOB ��8192 ��8192 DSN ��6144 ��6144 MSG 1289792 1271424 APG ��8192� ��14�8� RES �13�88� ��

70 Commands Guide

/DISPLAY

/DISPLAY,ST=EMAIL Command

� �/DISPLAY,ST=EMAIL

DATE = yy.ddd TIME = 15:12:�3

CURRENT EMAIL SETTINGS ---------------------- INITIALIZED : YES ENABLED : YES GLOBAL TRACE : NO TCP/IP TIMEOUT: 1� SECONDS SMTP PORT # : ��25 FROM NAME : Unicenter CA-7 REPLY ADDRESS : [email protected] TOTAL REQUESTS: �� ADDRESS DSN : cai.ADDRLIB TEMPLATE DSN : cai.EMAILLIB

� �


/DMP1

/DMP1

The /DMP1 command is the same as the “/DUMP” on page 76, except that itdoes not generate a storage dump. It also causes a user 444 (U0444) abend.


/DMP1

��──/DMP1───────────────────────────────────────────────────────��

72 Commands Guide

/DRCLASS

/DRCLASS

The /DRCLASS command adds or removes a disaster recovery class from thelist of active disaster recovery classes. Disaster recovery classes have noimpact on Unicenter CA-7 processing unless Unicenter CA-7 is running indisaster recovery mode.

Changes to the active disaster recovery class list are not saved across restartsof Unicenter CA-7. To make a disaster recovery class active when UnicenterCA-7 starts, add the class to the DRCLASS initialization file statement.

Use /DISPLAY,ST=DR to display the list of active disaster recovery classes.


/DRCLASS

��──/DRCLASS─ ──,CLASS=(xx1,...,xx8) ──┬ ┬──────────────── ─────────��└ ┘──,ACT= ──┬ ┬─ADD─

└ ┘─DEL─

CLASSDefines one to eight disaster recovery classes to be added to or removedfrom the list of active disaster recovery classes. Each disaster recoveryclass can be one to eight characters long. The disaster recovery classesmust be separated by commas and enclosed in parentheses. If a singledisaster recovery class is specified, the parentheses can be omitted.CLASS is required.

ACTDefines what action should be performed on the disaster recovery classesspecified on the CLASS keyword. ACT=ADD adds the classes to the list ofactive disaster recovery classes. ACT=DEL removes the classes from thelist. If ACT is not specified, the classes are added to the active disasterrecovery list.

Examples/DRCLASS,CLASS=TIER1

/DRCLASS,CLASS=(TIER2,TIER3),ACT=ADD

/DRCLASS,CLASS=TIER3,ACT=DEL


/DRMODE

/DRMODE

The /DRMODE command turns disaster recovery mode on or off and changesthe disaster recovery mode options.


/DRMODE

��──/DRMODE─ ──┬ ┬───────────────────────── ──┬ ┬────────────────── ──�└ ┘──,DEFCLASS= ──┬ ┬─@SYSTEM─ └ ┘──,MODE= ──┬ ┬─DR───

└ ┘─value─── └ ┘─NORM─

�─ ──┬ ┬────────────────── ──┬ ┬───────────────────── ───────────────��└ ┘──,RQMTS= ──┬ ┬─DR── └ ┘──,TRIGGERS= ──┬ ┬─DR──

└ ┘─ALL─ └ ┘─ALL─

DEFCLASSDefines a rule for Unicenter CA-7 to determine a disaster recovery class fora job if a disaster recovery class has not been assigned to the job. IfDEFCLASS=@SYSTEM, the job's SYSTEM value is used as the disasterrecovery class. Any other value of DEFCLASS is used as the job's disasterrecovery class.

MODESpecifies the Unicenter CA-7 mode. The following are the possible values:

DRSpecifies disaster recovery mode.

NORMSpecifies normal mode.

For cautions on turning on disaster recovery mode, see the usage notesthat follow.

RQMTSDetermines how Unicenter CA-7 will handle unsatisfied job requirements.The following are the possible values:

DRSpecifies Unicenter CA-7 to satisfy the job requirement if thepredecessor job has an inactive disaster recovery class.

ALLSpecifies Unicenter CA-7 to leave the requirement unsatisfied (as ifUnicenter CA-7 were not running in disaster recovery mode).

74 Commands Guide

/DRMODE

TRIGGERSSpecifies whether Unicenter CA-7 triggers jobs with an inactive disasterrecovery class when Unicenter CA-7 is running in disaster recovery mode.

DRSpecifies Unicenter CA-7 not to trigger jobs with an inactive disasterrecovery class.

ALLSpecifies Unicenter CA-7 to trigger jobs normally (as if Unicenter CA-7 werenot running in disaster recovery mode).

Usage Notes

Warning!

Read the topic about the Disaster Recovery Mode in the SystemsProgrammer Guide before running Unicenter CA-7 in disaster recoverymode.

Since Unicenter CA-7 does not provide any default active disaster recoveryclasses, schedule scan running in disaster recovery mode will not bring anyjobs into the request queue.

We recommend that one or more disaster recovery classes be made active(either with the DRCLASS initialization file statement or the /DRCLASScommand) before starting disaster recovery mode.

Examples/DRMODE,MODE=DR

/DRMODE,TRIGGERS=ALL,RQMTS=ALL

/DRMODE,DEFCLASS=@SYSTEM


/DUMP

/DUMP

The /DUMP command causes an abnormal termination of Unicenter CA-7. Auser 444 abend results and a storage dump is generated.

Note: Extreme CAUTION is advised before using this command because aloss of data can result.


/DUMP

��──/DUMP───────────────────────────────────────────────────────��

Usage Notes

Under normal circumstances it should not be necessary to use this command(or /DMP1). If it is necessary to terminate Unicenter CA-7 execution with theoption to reactivate Unicenter CA-7 with a WARM start, you should use the/SHUTDOWN command. For more information, see “/SHUTDOWN” onpage 117.

76 Commands Guide

/EADMIN

/EADMIN

The /EADMIN command modifies selected settings of the Unicenter CA-7 emailinterface. Changes made using the /EADMIN command are not saved acrossstarts of Unicenter CA-7. To make a change permanently, you must update theEMAIL initialization file statement.


/EADMIN

��──/EADMIN─ ──┬ ┬──────────────── ──┬ ┬───────────────── ────────────�└ ┘──,EFROM=xxx...x └ ┘──,ENABLE= ──┬ ┬─Y─

└ ┘─N─

�─ ──┬ ┬───────────────── ──┬ ┬────────────── ──┬ ┬────────────── ─────��└ ┘──,EREPLY=xxx...x └ ┘──,ETIMEOUT=nn └ ┘──,TRC= ──┬ ┬─Y─

└ ┘─N─

EFROMSpecifies a new name to display in the "From" field of emails. The valuecan be up to 70 characters long and can contain special characters (otherthan commas). Unicenter CA-7 converts all lowercase letters to uppercasewhen processing the command.

ENABLESpecifies whether to use the email interface. All emails can be suppressedby specifying ENABLE=N. All emails currently waiting to be sent arediscarded with no indication of any error. Any new emails requested withthe /EMAIL command are also discarded, and an error message(SCMR-07) is issued to the terminal in response to the command./EADMIN,ENABLE=Y must be specified to allow emails to be sent again.

EREPLYSpecifies a new default email reply address to be used when emailrecipients reply to emails from Unicenter CA-7. The value can be up to 70characters long and can contain special characters (other than commas).Unicenter CA-7 converts all lowercase letters to uppercase whenprocessing the command. The reply address can also be overridden by theemail address member "reply:" line.


/EADMIN

ETIMEOUTSpecifies the maximum number of seconds Unicenter CA-7 will wait forresponses from TCP/IP and the SMTP (email) server. Values can rangefrom 5 to 20 seconds.

TRCSpecifies if the email trace should be turned on or off globally. The emailtrace is written to SYSOUT data set ETRACE in the Unicenter CA-7 taskand contains information about the connection between Unicenter CA-7 andTCP/IP and the conversation with the SMTP (email) server. The trace canproduce many lines of output, so it should be turned off when not in use.The email trace can be requested for a specific email by specifying TRC=Yon the /EMAIL command.

78 Commands Guide

/ECHO

/ECHO

The /ECHO command either echoes input data back to the sending terminal orformats a 3270-type terminal with constant data so that additional data can thenbe entered to complete an input command. This command is especially usefulin combination with the /PF and /PA commands to allow a lengthy commandformat to be called up onto a terminal with a single keystroke.


/ECHO

��──/ECHO─ ──, ──┬ ┬─M─── =text ─────────────────────────────────────�� └ ┘─MSG─

MSGDefines a character string to be echoed back to the terminal. MSG and Mcan be used interchangeably, but one or the other is required. If commasare included as part of the text, enclose the entire message text inparentheses.

If the last character of the MSG text is a # sign, the cursor is moved to thatlocation when the command is echoed to the terminal. This is provided toallow preformatting of command input.


Required: Yes

Examples/ECHO,M=THIS IS AN ECHO BACK

/ECHO,M=(LJOB,JOB=#)

/ECHO,MSG=PUT THIS ON THE PANEL #


/EMAIL

/EMAIL

The /EMAIL command creates and queues an email request to the UnicenterCA-7 email interface.


/EMAIL

��──/EMAIL─ ──,TO=member ──,TXT=member ──┬ ┬────────────────────── ───�└ ┘──,JOB= ──┬ ┬─jobname───

└ ┘─jobnumber─

�─ ──┬ ┬────────────── ──┬ ┬───────────────────────── ───────────────��│ │┌ ┐─N─ └ ┘──,VAR=(value1,...value8)└ ┘──,TRC= ──┴ ┴─Y─

TODefines the member in the EADDRLIB PDS that contains the emailaddresses of the recipients for this email. Up to 100 email addresses canbe specified in the member, each starting in column 1 and each up to 70characters long. The email address member can also contain an override ofthe email reply address. For more information about the format of the emailaddress member, see the Interfaces Guide.

TXTDefines the member in the EMAILLIB PDS that contains the email templatefor this email. The template defines the contents of the subject and body ofthe email. For more information about the format of the email templatemember, see the Interfaces Guide.

JOBDefines a job in the Unicenter CA-7 queues. If specified, the job's queueinformation will be used to populate variables that can be substituted in theemail template. Either a job name or a Unicenter CA-7 job number can bespecified. If a job name is entered, and multiple jobs with that name exist inthe Unicenter CA-7 queues, then the first job found is used. The queuesare searched in the order REQ, RDY, and ACT.

TRCSpecifies whether to trace this email request. The email trace trace iswritten to SYSOUT data set ETRACE in the Unicenter CA-7 task andcontains information about the connection between Unicenter CA-7 andTCP/IP and the conversation with the SMTP (email) server.

VARDefines one to eight values for email template variables &VAR1 to &VAR8.Each value can be up to eight characters long. Unicenter CA-7 convertslowercase letters to uppercase when processing the command. For moreinformation about using variables in email, see the Interfaces Guide.

80 Commands Guide

/FETCH

/FETCH

The /FETCH command retrieves top line commands entered since the last/LOGON.

Commands entered on the top line are stored in a buffer known as a commandring. The command ring can hold up to five top line commands. When the sixthcommand is entered, the oldest command in the ring is erased so that the newone can be stored. In this way, the five most recent commands are saved.

You can override the default number of commands stored in the command ringbuffer using the MAXRINGSZ= keyword on the OPTIONS statement in theinitialization file. For more information, see the Systems Programmer Guide.

Repeated executions of /FETCH will retrieve commands in the order that theyare stored in the ring, from most recent to the oldest.

Use /PF to assign this command to a PF key for ease of use. Also, by default,PF2 is set to perform the /FETCH command.


/FETCH

��──/FETCH──────────────────────────────────────────────────────��


/JCL

/JCL

The /JCL command adds, updates, or deletes a JCL statement referenced by asymbolic index.

Changes made to JCL statements with the /JCL command are stored in theUnicenter CA-7 database and remain in effect when Unicenter CA-7 isreinitialized if JCLDEFS=VSAM is specified on the RESIDENT statement in theinitialization file.

For more information about using symbolic indexes to refer to JCL data sets,see the Systems Programmer Guide.

Note: Any changes to JCL library definitions are LOST when Unicenter CA-7is recycled unless JCLDEFS=VSAM is specified on the RESIDENT statement inthe initialization file. See the discussion of this keyword on the RESIDENTstatement in the Systems Programmer Guide.


/JCL

��──/JCL─ ──,OPT= ──┬ ┬─ADD─ ,INDEX=jcllib ──,DSN=dsname ──────────────� ├ ┤─UPD─ └ ┘─DEL─

�─ ──┬ ┬─────────────────── ──┬ ┬───────────────────── ───────────────�└ ┘──,ALT= ──┬ ┬─nnn──── └ ┘──,DPROC= ──┬ ┬─dsname─

├ ┤─xx...x─ ├ ┤─NO───── └ ┘─NO───── └ ┘─�NONE�─

�─ ──┬ ┬─────────────────────── ───────────────────────────────────�� │ │┌ ┐─MASTER───

└ ┘──,LTERM= ──┴ ┴─xxxxxxxx─

OPTSpecifies the type of JCL statement change to be performed.

ADDSpecifies to add a symbolic JCL data statement reference.

UPDSpecifies to update a symbolic JCL data statement reference.

DELSpecifies to delete a symbolic JCL data statement reference.

INDEXDefines the symbolic index associated with the JCL statement. A symbolicindex is referred to as a JCLLIB on the DB.1 panel. A symbolic indexconsists of an ampersand (&) followed by up to 15 alphanumericcharacters. Symbolic value &HELP is reserved for the HELP data set.

82 Commands Guide

/JCL

DSNDefines the fully qualified name of a data set containing execution JCL tobe submitted by Unicenter CA-7. The data set must be a PDS. A data setname cannot be specified with OPT=DEL.

Note: JCL libraries added with the /JCL command are automaticallyassigned an attribute of DYN=2.

TSO packed data is not supported.

ALTSpecifies JCL library destination.

nnn

xx...xDefines the INDEX value from a previously defined JCL library that issearched prior to this one. This works exactly like DD statementconcatenation where the ALT is first in the sequence, but is supportedfor only one level. Since validation of this parameter is done while theinternal table of JCL libraries is being built, the alternate library must bedefined in the initialization file prior to the statement that references itas an alternate. ALT and INDEX values cannot be equal in any oneJCL statement. For a discussion of how this option can be used, seeAlternate JCL Libraries in the Database Maintenance Guide. ALT isoptional.

NOSpecifies that an ALT destination is to be removed from an existing JCLlibrary destination, as in the following:

/JCL,INDEX=index,OPT=UPD,ALT=NO

DPROCSpecifies CA-Driver JCL libraries.

dsnameDefines the name of the PDS that is to be concatenated above thelibraries in the CARPROC DD allocation whenever CA-Driver is invokedfor JCL in the associated JCL library.

NOSpecifies that a DPROC association is to be removed from an existingdefinition, as in the following:

/JCL,INDEX=index,OPT=UPD,DPROC=NO

*NONE*Specifies that CA-Driver is not to be invoked for JCL using this INDEX.

LTERMSpecifies the logical terminal to which prompt messages should be routedfor jobs using JCL from this library. The default is MASTER. For moreinformation about the the LTERM keyword or the JCL initialization filestatement, see the Systems Programmer Guide.


/LOG

/LOG

The /LOG command adds free-form text to the Unicenter CA-7 log data set.Use these entries to document situations occurring during production, such aswhy a job is late or canceled. You can review this text later through batchreport CA7xx032.


/LOG

��──/LOG─ ──, ──┬ ┬─D──── =data ─────────────────────────────────────�� └ ┘─DATA─

DATADefines data to be logged to the log data set. DATA and D can be usedinterchangeably, but one or the other is required. If commas are included aspart of the data, enclose the entire data text in parentheses.


Required: Yes

Usage Notes

The data is written to the log data set and is stamped with the current date andtime-of-day, terminal ID and depending on installation option, operator ID.

See report request ID CA7xx032 in the Reports Guide for a report that reflects/LOG information.

Examples/LOG,D=(PAYROLL SOURCE INPUT RECD, 45 MIN LATE)

/LOG,DATA=CA�7JOB1 CANCELED

Note: Current date and time are added to the text when the log record iswritten.

84 Commands Guide

/LOGOFF

/LOGOFF

The /LOGOFF command informs the Unicenter CA-7 system that a terminal isgoing inactive. Whenever a terminal is to be inactive for some time, it is best toissue a /LOGOFF. This does not return to VTAM (see /CLOSE). It causesUnicenter CA-7 to return the terminal to the Logon panel.

/LOGOFF with no terminal specification causes the issuing terminal to belogged off from Unicenter CA-7.


/LOGOFF

��──/LOGOFF─ ──┬ ┬────────────────── ──────────────────────────────�� └ ┘──, ──┬ ┬─T──── =term └ ┘─TERM─

TERMDefines the terminal to be logged off. Value must be a terminal name, up toseven characters. The T option could be used from the master terminal tolog off a terminal to allow completion of the shutdown process. See thedescription of /SHUTDOWN on “/SHUTDOWN” on page 117.


/LOGON

/LOGON

The /LOGON command initiates a Unicenter CA-7 terminal session. Informationsupplied on the /LOGON command is used to validate user access to UnicenterCA-7.


/LOGON

��──/LOGON──userid─ ──┬ ┬─────────── ──┬ ┬─────────────── ────────────�└ ┘──,password └ ┘──,NPW=password

�─ ──┬ ┬─────────────── ──┬ ┬──────────────── ───────────────────────��└ ┘──,UID=resource └ ┘──,PRM=parameter

useridDefines the user ID. The parameters described above are valid for batchusers of Unicenter CA-7 (for example, console users, batch terminal users,and so on). For online users, these parameters are not considered validunless RESLOGON=NO is specified on the SECURITY statement in theinitialization file. If RESLOGON=NO is not specified, the /LOGON commandcauses the LOGON panel to be displayed with an error message.


Required: Yes

passwordDefines the password. This parameter can be entered as PSW=password.


Required: No

NPWDefines the new password. This parameter can be used to change theuser's current password if using external security.


Required: No, unless required by external security

UIDDefines the UID resource name. The data entered is not displayed. Formore information about UID resources, see the Security Guide.


Required: No

86 Commands Guide

/LOGON

PRMDefines free-form text to be passed to the SASSXXLX user exit.


Required: No, unless required by user exit

Usage Notes

If DISPLAY=NO is specified on the SECURITY statement in the initializationfile, data entered in the USERID field of the LOGON panel is not displayed. Formore information, see the Systems Programmer Guide.

Example

The following is an example of the /LOGON command.

/LOGON Command

� �PLEASE ENTER LOGON DATA OR PRESS PF3 TO DISCONNECT

USERID : TERMINAL NAME : xxxxxxx DATE : yy.dddPASSWORD : VTAM APPLID : xxxxxxx TIME : 11:27:26NEW PASSWORD : LUNAME : xxxxxxxx LEVEL : r11 (yymm)UID RESOURCE :PARMS : CCCCCCCCCCC AAAAAAAAAA 77777777777 CCCCCCCCCCC AAAAAAAAAA 77777777777 CCC AAA AAA 7777 CCC AAAAAAAAAA �� 7777 CCC AAAAAAAAAA �� 7777 CCC AAA AAA 7777 CCCCCCCCCCC AAA AAA 7777 CCCCCCCCCCC AAA AAA 7777

COPYRIGHT (C) 1988, 2��5COMPUTER ASSOCIATES INTERNATIONAL, INC.

� �


/MSG

/MSG

The /MSG command sends a free-form message to another logical terminal.


/MSG

��──/MSG─ ──┬ ┬────────────────────── ──┬ ┬──────────── ──────────────�└ ┘──, ──┬ ┬─LT──── =station └ ┘──,ID=userid

└ ┘─LTERM─

�─ ──, ──┬ ┬─M─── =text ─────────────────────────────────────────────�� └ ┘─MSG─

LTERMDefines the logical terminal (station) to which the message is to be sent.LTERM and LT can be used interchangeably, but cannot be used with ID.Value must be a single, logical station name.


Required: No

IDDefines the user ID to which the message is to be sent. The message isqueued to the logical terminal associated with the user ID. If the user ID islogged on multiple times, only the first logical terminal receives themessage. ID cannot be used with LT or LTERM.


Required: No

MSGDefines the message text to send. MSG and M can be usedinterchangeably, but one or the other is required. If commas are included aspart of the text, enclose the entire message text in parentheses.


Required: Yes

88 Commands Guide

/MSG

Usage Notes

The message is queued behind other queued output, if any. The sending logicalterminal name is displayed with the message text.

If the receiving terminal logs off before displaying the message, the messageremains queued to that logical terminal.

Unicenter CA-7 displays the sending logical terminal name with the messagetext.

This command is allowed from a Unicenter CA-7 trailer step.

Examples/MSG,LT=DATAENTR,MSG=NEED PAYROLL INPUT IN 15 MIN

/MSG,LTERM=MASTER,M=EXPEDITE JOB 7

/MSG,LT=MASTER,M=(THIS NEEDS,PARENTHESES)

/MSG,ID=CA7USR,M=PLEASE LOGOFF BEFORE 1�:��


/MVS

/MVS

The /MVS command isuues MVS operator commands.


/MVS

��──/MVS─ ──, ──┬ ┬─M─── =(operator command) ────────────────────────�� └ ┘─MSG─

MSGDefines the MVS system console operator command to be issued. Ifcommas are included as part of the MVS command text, enclose the entirecommand text in parentheses.


Required: Yes

Example/MVS,M=(D A,L)

Special Considerations

The command text is sent to MVS exactly as it appears on the MSG keyword.Unicenter CA-7 does not verify that the text is a valid MVS command.

There is no output specific to the command provided on the MSG keyword.Unicenter CA-7 does not report the status of the command in MVS. In mostcases, command output only appears on the MVS console.

For information about security considerations with the /MVS command, see theSecurity Guide.

90 Commands Guide

/NXTMSG

/NXTMSG

The /NXTMSG command displays messages that were queued for a terminal.Messages can originate manually from a user at a terminal or automaticallyfrom Unicenter CA-7. Users are alerted to the presence of messages at/LOGON time and by the MSGS indicator at the bottom of preformatted panelsor below the page number on general inquiry command displays.

Each command displays the next message in the sequence received; that is,the message that has been queued the longest amount of time.


/NXTMSG

��──/NXTMSG─────────────────────────────────────────────────────��

No keywords are associated with this command. The next queued message forthis terminal is displayed. If there are no more messages, a message isproduced that indicates there are no queued messages.


/OPEN

/OPEN

The /OPEN command restores access to terminals or line groups by theUnicenter CA-7 system, after a /CLOSE command.

Use this command to start manually the Unicenter CA-7 CAICCI Terminalinterface. You may need to start this interface manually if CAICCI is not activewhen Unicenter CA-7 initializes or if CAICCI terminates after the interface hasbeen initialized.

To initialize the Unicenter CA-7 CAICCI Terminal Interface without recyclingUnicenter CA-7, use the /OPEN command specifying a GROUP that is definedas DEVICE=CCI.

There is no need to issue the /OPEN for each group defined with DEVICE=CCI,the first /OPEN issued for such a group will suffice.

This command should NOT be used after a /CLOSE has been issued for aGROUP defined as DEVICE=CCI.


/OPEN

��──/OPEN─ ──, ──┬ ┬──GROUP=group ──── ──────────────────────────────�� └ ┘── ──┬ ┬─T──── =term └ ┘─TERM─

GROUPDefines a line group to be opened and identifies which group. Value mustbe the group name. When GROUP specifies a VTAM group, logons areaccepted.


Required: Yes (unless TERM is used)

TERMDefines the name of a VTAM terminal that is to have its logon simulated(SIMLOGON). This establishes a connect to the terminal from UnicenterCA-7 to VTAM.


Required: Yes (unless GROUP is used)

92 Commands Guide

/OPEN

Examples/OPEN,GROUP=VGROUP

/OPEN,T=VPRNTR

/OPEN,GROUP=CCI�1


/OPERID

/OPERID

The OPERID command obtains the current internal security definitions for theissuing user.


/OPERID

��──/OPERID─────────────────────────────────────────────────────��

No keywords are associated with this command.

Example

/OPERID Command

� � /OPERID

�� OPERATOR DISPLAY �� PAGE ��1 OPERATOR-ID TERMINAL USERID ----------------APPL,PRTY-------------

MASTER HTERM1 255 SYS�,15 SDM�,15 SCO�,15 SLI�,15 SCM�,15MLR�,15 FOR�,15 SRC�,15 TRA�,15 SPO�,15UTL�,15 SAN�,15 SJR�,15 SQM�,15 SFC�,15


MASTER TTERM1 255 SPO�,15MASTER CTERM1 255 SCO�,15 SLI�,15 SPO�,15MASTER BTERM1 255 SCO�,15 SLI�,15 SPO�,15

� �

These fields are described in the /OPERIDS examples.

94 Commands Guide

/OPERIDS

/OPERIDS

The /OPERIDS command displays current internal security definitions for anoperator ID other than your own or for all operator IDs. You can also use the/OPERIDS command to display all active users logged on to Unicenter CA-7.


/OPERIDS

��──/OPERIDS─ ──,ID= ──┬ ┬─userid─ ─────────────────────────────────�� ├ ┤─ALL──── └ ┘─�ACT�──

IDSpecifies the operator ID for which the internal security definitions are to bedisplayed. You can enter one of the following:

useridSpecifies to display the definitions for a single operator ID.

ALLSpecifies to display the definitions for all currently defined operator IDs.

*ACT*Specifies to display all active terminal users logged on to UnicenterCA-7. Once the trailer terminal has been used after Unicenter CA-7startup, it always shows active.


/OPERIDS

Examples

/OPERIDS Command

� � /OPERIDS,ID=MASTER

�� OPERATOR DISPLAY �� PAGE ��1 OPERATOR-ID TERMINAL USERID ----------------APPL,PRTY-------------



MASTER TTERM1 255 SPO�,15MASTER CTERM1 255 SCO�,15 SLI�,15 SPO�,15MASTER BTERM1 255 SCO�,15 SLI�,15 SPO�,15

� �


OPERATOR-IDIdentifies the Unicenter CA-7 operator ID as defined in the Unicenter CA-7internal security matrix.

TERMINALIdentifies the Unicenter CA-7 terminal name as defined in the initializationfile.

USERIDIdentifies the internal security UID level associated with the operator IDlisted.

APPL,PRTYIdentifies the Unicenter CA-7 application IDs and the associated securitylevel for this user for each application. (Example: SDM0,15 where SDM0 isthe database maintenance application, and the user has a security level of15 for this application.)

96 Commands Guide

/OPERIDS

/OPERIDS Command

� �/OPERIDS,ID=�ACT�

�� DISPLAY ACTIVE USERS �� PAGE ��1TERMINAL LUNAME USERID UID

LC A78L9�9 PROD�6 �� X78��1 A78L9�6 SCHED4 1��

X78��2 A78L9�7 OPERID1 255

� �


TERMINALIdentifies the Unicenter CA-7 terminal name as defined in the initializationfile.

LUNAMEIdentifies the VTAM logical unit name associated with this terminal.

USERIDIdentifies the user ID associated with the terminal. If Unicenter CA-7 internalsecurity is being used, this is the Unicenter CA-7 operator ID. For externalsecurity, this is the ID of the user that was used during logon to UnicenterCA-7.

UIDIdentifies the internal security UID level associated with the user.


/PAGE

/PAGE

The /PAGE command can selectively review an output message or commandresponse. Previous pages (panels) and succeeding pages of a current displaycan also be reviewed.


/PAGE

��──/PAGE─ ──┬ ┬─=nnn─ ────────────────────────────────────────────�� ├ ┤─+nnn─ └ ┘─-nnn─

=nnnDefines the exact page number to be displayed.

+nnnDefines a relative number of pages to skip forward within the message.

-nnnDefines a relative number of pages to skip backward within the message.

Limits: 1 to 3 numeric characters

Required: Yes

Usage Notes

The default values for PA1 (3270 program access key 1) or Enter with no texthas the same effect as entering /PAGE+1.

The last page in a message can be displayed by requesting a specific page(/PAGE=nnn) and giving a high value for nnn (for example, 255).

PF7 and PF8 are temporarily overridden by online menus and their relatedformatted and display panels to /PAGE-1 and /PAGE+1 respectively. For otherdisplays, PA1 and PA2 default to these same values if they have not been setto some other value during initialization or by a /PA command.

98 Commands Guide

/PAGE

Examples /PAGE=4

Go to page four.

/PAGE+2

Skip forward two pages from current page.

/PAGE-3

Skip backward three pages from current page.


/PAnn

/PAnn

The /PAnn command reassigns PA keys. This can serve as a shortcut for doingrepetitive commands at the terminal (3270-type). Each terminal can haveunique information associated with a program access (PA) key, or certain basiccommands can be assigned to PA keys during initialization of Unicenter CA-7.An individual at a terminal can reassign PA keys set during initialization.


/PAnn

��─ ──/PAnn ──┬ ┬───────────────── ─────────────────────────────────�� └ ┘──, ──┬ ┬─M─── =text └ ┘─MSG─

nnDefines the PA key to be assigned.

Limits: 2 numeric characters from 01 to 03Leading zero is required

Required: Yes

MSGDefines the character string assigned to the key. MSG and M can be usedinterchangeably. If commas are included as part of the text, enclose theentire message text in parentheses.


Required: No

100 Commands Guide

/PAnn

Usage Notes

If entered with no parameters (for example, /PA01), the character stringassigned to the key by a previous /PA command is removed. (The assignmentsin the initialization file are not removed.) /PF99 cancels all /PF and /PAcommand assignments on that terminal for both PF and PA keys. (Theassignments in the initialization file are not removed.)

All /PA command assignments are carried across /LOGOFF and /LOGONcommand sequences, but not across initializations of Unicenter CA-7. Defaultvalues for PA keys, if not overridden during initialization or by a /PA command,are:

PA1 key - /PAGE+1PA2 key - /PAGE-1

Note: The PA keys are not supported under the Unicenter CA-7 TSO-ISPFinterface.

You can view assigned values by entering a /DISPLAY,ST=KEY command.

Examples/PA�3,M=(/COPY,LT=TERMABC)

/PA�1,M=LQUE


/PFnn

/PFnn

The /PFnn command provides a shortcut method for doing repetitive commandsat a 3270-type terminal. Each terminal can have unique information associatedwith a program function (PF) key, or certain basic commands can be assignedto PF keys during initialization of Unicenter CA-7. Using the /PF command, anindividual at a terminal can reassign PF keys set during the initialization.


/PFnn

��─ ──/PFnn ──┬ ┬───────────────── ─────────────────────────────────�� └ ┘──, ──┬ ┬─M─── =text └ ┘─MSG─

nnDefines the PF key to be assigned. Value is 99 to cancel all assignmentsmade with previous /PF and /PA commands.

Limits: 2 numeric characters from 01 to 24Leading zero is required

Required: Yes

MSGDefines the character string assigned to the key. MSG and M can be usedinterchangeably. If commas are included as part of the text, enclose theentire message text in parentheses.


Required: No

102 Commands Guide

/PFnn

Usage Notes

PF3 is temporarily overridden by online menus and their related formatted anddisplay panels. It is used there as a quit function to return to the menu. Anyvalue defined by the user is ignored until PF3 is used once or a top linecommand is entered by the user.

A Unicenter CA-7 PF key assignment is honored in the Unicenter CA-7TSO-ISPF environment when PASSTHRU is the ISPF application commandtable value associated with the ISPF command that is assigned to the PF keyin question.

Assigned values can be viewed by entering a /DISPLAY,ST=KEY command.

/PF99 cancels all /PF and /PA command assignments on that terminal for bothPA and PF keys. (The assignments in the initialization file are not removed.) Ifentered with a null MSG value (for example,/PF01,MSG=) the character stringassigned to the key by a previous /PF command is removed. (The assignmentsin the initialization file are not removed.)

All /PF command assignments are carried across /LOGOFF and /LOGONcommand sequences, but not across initializations of Unicenter CA-7. It shouldbe emphasized that /PF command assignments are associated with terminals.This is an important consideration if virtual terminals are used.

Default values for PF keys, if not overridden during initialization or by a /PFcommand, are:

PF1 - /PURGPGPF2 - /COPYPF3 - /NXTMSG

In a VTAM environment, a PF key is normally assigned as the VTAM logoff keyin the initialization file. If this assignment is not made to one of the keys and a/PF or /PA command has not been used to define a /CLOSE command, the/CLOSE top line command must be used for that purpose.

Examples/PF�4,M=LQ

/PF�9,M=(/ECHO,M=(LJOB,JOB=#))

/PF�6,MSG=(/FETCH)


/PROF

/PROF

The /PROF command lists and manages your Unicenter CA-7 user profile. Theuser profile is stored in the Unicenter CA-7 database and contains personalPA/PF key settings and an external UID resource name (see “/UID” onpage 125 and the Security Guide). When you log on to Unicenter CA-7, thePA/PF key settings from your user profile are set up for your terminal sessionautomatically. Also, if you do not specify an external UID resource name on theCA-7 Logon panel, it is taken from the user profile if it has been defined there.

Note: User profile PA/PF key settings override terminal and default PA/PF keysettings from the initialization file with one exception. The PA/PF key that isdefined as the VLOGOFF key is NOT overridden by the user profile settings.

If you issue the /PROF command without any operands, the current values inyour user profile are listed.


/PROF

��──/PROF─ ──┬ ┬─────────────────── ────────────────────────────────�└ ┘──,EXRSLV= ──┬ ┬─NO──

└ ┘─YES─

�─ ──┬ ┬─────────────────────────── ──┬ ┬──────────── ────────────────�└ ┘──, ──┬ ┬─K──── = ──┬ ┬─CLEAR─── └ ┘──,R=uidname

└ ┘─KEYS─ ├ ┤─PROFILE─ └ ┘─SAVE────

�─ ──┬ ┬────────────────────── ────────────────────────────────────�� └ ┘──, ──┬ ┬─ST───── =DELETE

└ ┘─STATUS─

EXRSLVSpecifies whether extended RESOLV messages should be produced whenyou issue a RESOLV command. These messages (SRC1-137) can beproduced when a job/network is scheduled on the same day by two or moreschedule IDs.

Required: No. The extended RESOLV message option can be overriddenusing the DUPDATE= keyword on the RESOLV command itself.

104 Commands Guide

/PROF

KEYSSpecifies the action to take with PA/PF keys.

SAVESpecifies to save your current terminal PA/PF key settings in your userprofile. The current terminal key settings are defined by using the /PAnnand /PFnn commands. To determine your current settings, issue/DISPLAY,ST=KEY. The definitions under the heading ---- TERMINAL---- are the settings that are saved to your profile. Other PA/PF keysettings under the headings Initialization and Defaults are NOT saved.If you already have PA/PF key settings in your user profile, they areNOT merged with the new settings.

PROFILESpecifies to replace your current terminal PA/PF key settings with thethe definitions in your user profile. PROF and PROFILE can be usedinterchangeably. If you have made temporary changes to your currentsettings with the /PAnn and/or /PFnn commands, you can return to yourprofile definitions by using KEYS=PROFILE.

CLEARSpecifies to clear the PA/PF key settings in your user profile. Oncecleared, these settings cannot be recovered. You have to define newsettings to your current session using the /PAnn and/or /PFnncommands and then save them using KEYS=SAVE. If you want to clearonly the settings for your current terminal session, use the /PF99command.

RDefines the resource name defined in the UID resource table to be used asyour default at logon time. If you explicitly specify a resource name on theCA-7 Logon panel, it overrides the value in your user profile.

Note: The resource name specified is NOT validated against the currentUID resource table, nor is it checked against external security at the time itis placed in the profile record. These checks are made if the resource nameis used at logon time.

STATUS=DELETESpecifies the entire user profile record should be deleted from thedatabase. If used, this keyword must be the only one coded. ST andSTATUS can be used interchangeably.


/PROF

Examples/PROF (Lists your user profile settings)/PROF,KEYS=SAVE (Saves current PA/PF keys into your profile)/PROF,R=CA7�122 (Sets default UID resource name in profile)/PROF,K=PROFILE (Sets up the user profile PA/PF keys in

your current terminal session)/PROF,ST=DELETE (Deletes the profile record from the database)

Usage Notes

To set up your own personal PA/PF key settings, you first need to define themfor your current terminal session using the /PA and/or /PF commands. Oncethey are set to your satisfaction, use the /PROF command with theKEYS=SAVE parameter to save them into your profile.

For example:

/PF99 Deletes any current settings /PF�1,MSG=...command.... Defines PF�1 /PF�2,MSG=...command.... Defines PF�2 .... other keys ........ Define as many as you want /DISPLAY,ST=KEY Displays your current PA/PF key

settings. You current session keysare listed under the heading'---- TERMINAL ----'.

/PROF,KEYS=SAVE Saves the current session keys intoyour profile record in the database.

/PROF Displays the contents of your profile record.

� �� CA-7 PROFILE: ID=userid R=resname MAINT=yy.ddd/hh:mm BY userid PAGE xxxx OPTS=EXRSLV

PF�1 /ECHO,M=(/DISPLAY,ST=KEY) PF�2 /ECHO,M=(/DISPLAY,ST=ALL) PF�6 /NXTMSG PF19 /PAGE-1 PF2� /PAGE+1 PF23 /ECHO,M=(/PURGPG)

SCMP-�� DISPLAY COMPLETE AT hh:mm:ss ON yy.ddd.� �

106 Commands Guide

/PROF


IDIdentifies the Unicenter CA-7 user ID whose profile is being displayed.

RIdentifies the external UID resource name to be used as a default at logon.

MAINTIdentifies the date and time of the last update to the profile record and theUnicenter CA-7 user ID who caused the update.

OPTSIdentifies user option defaults:

EXRSLV - Produce extended RESOLV messages (SRC1-137).

PFnn or PAnnIdentifies the PA or PF key defined.

commandsIdentifies the command associated with the PA/PF key on the same line.


/PROFS

/PROFS

The /PROFS command lists and manages other users' Unicenter CA-7 userprofiles. The user profile is stored in the Unicenter CA-7 database and containspersonal PA/PF key settings and a UID resource name (see “/UID” onpage 125). When you log on to Unicenter CA-7, the PA/PF key settings fromyour user profile are set up for your terminal session automatically. Also, if youdo not specify an external UID resource name on the CA-7 Logon panel, it istaken from the user profile if it has been defined there.

Note: User profile PA/PF key settings override terminal and default PA/PF keysettings from the initialization file with one exception. The PA/PF key that isdefined as the VLOGOFF key is not overridden by the user profile settings.

If you issue the /PROFS command with only the ID= operand, the currentsettings in that user's profile are listed.


/PROFS

��──/PROFS─ ──,ID=opid ──┬ ┬─────────────────── ─────────────────────�└ ┘──,EXRSLV= ──┬ ┬─NO──

└ ┘─YES─

�─ ──┬ ┬─────────────────────────── ──┬ ┬──────────── ────────────────�└ ┘──, ──┬ ┬─K──── = ──┬ ┬─CLEAR─── └ ┘──,R=resname

└ ┘─KEYS─ ├ ┤─PROFILE─ └ ┘─SAVE────

�─ ──┬ ┬────────────────────── ────────────────────────────────────�� └ ┘──, ──┬ ┬─ST───── =DELETE

└ ┘─STATUS─

IDDefines the operator ID (one- to eight-character user ID) for the user profileyou want to display or update.

EXRSLVSpecifies whether extended RESOLV messages should be produced whenthe target user issues a RESOLV command. These messages (SRC1-137)can be produced when a job/network is scheduled on the same day by twoor more schedule IDs.

Required: No. The extended RESOLV message option can be overriddenusing the DUPDATE= keyword on the RESOLV command itself.

108 Commands Guide

/PROFS

KEYSSpecifies the action to take with PA/PF keys.

SAVESpecifies to save your current terminal PA/PF key settings in the userprofile for the ID= user. The current terminal key settings are defined byusing the /PAnn and /PFnn commands. To determine your currentsettings, issue /DISPLAY,ST=KEY. The definitions under the heading---- TERMINAL ---- are the settings that are saved into the profile. OtherPA/PF key settings under the headings Initialization and Defaults areNOT saved. If there are already PA/PF key settings in the user profile,they are NOT merged with the new settings.

PROFILESpecifies to replace your current terminal PA/PF key settings with thedefinitions in the ID= user's profile. PROF and PROFILE can be usedinterchangeably. You can return to your own profile settings by issuing/PROF,KEYS=PROFILE.

CLEARSpecifies to clear the PA/PF key settings in the ID= user's user profile.Once cleared, these settings cannot be recovered.

RDefines the resource name defined in the UID resource table to be used bythe ID= user as his/her default at logon time. If they explicitly specify aresource name on the CA-7 Logon panel, it overrides the value in their userprofile.

Note: The resource name specified is NOT validated against the currentUID resource table, nor is it checked against external security at the time itis placed in the profile record. These checks are made if the resource nameis used at logon time.

STATUS=DELETESpecifies the entire user profile record should be deleted from thedatabase. ST and STATUS can be used interchangeably. If used, thiskeyword must be the only one coded.


/PROFS

Examples/PROFS,ID=JOE

Lists Joe's user profile settings.

/PROFS,ID=BOB,R=CA7��22

Sets resource name CA70022 in Bob's profile.

/PROFS,ID=TED,K=SAVE

Saves YOUR current PA/PF key settings into Ted's profile.

/PROFS,ID=JOE,ST=DELETE

Deletes Joe's profile settings.

Usage Notes

The most important thing to remember about dealing with other users' profiles isthat YOUR current terminal session definitions will affect or be affected byactions regarding others' profiles.

For example, to set up default PA/PF keys for other users, you must first definethem to your current terminal session using the /PA and/or /PF commands. Youcan then save these definitions into their profile(/PROFS,ID=userid,KEYS=SAVE).

Another way to accomplish this is to fetch the PA/PF key settings from anexisting profile into your current terminal session; then save them into anotheruser's profile; then return to your own profile settings. For example:

/PROFS,ID=USERA,KEYS=PROFILE Fetch USERA's key settings/PROFS,ID=USERB,KEYS=SAVE Save them to USERB's profile/PROF,KEYS=PROFILE Restore your own key settings

Note: The /PROF, /PROFS, /PA, and /PF commands can all be executed inbatch using the BTI facility. So you can set up a batch command deck thatdefines all the PA/PF keys and SAVES them into one or more user profiles. Forexample:

/LOGON adminid Logon the administrator userid/PF99 Delete any current settings/PF�1,MSG=...command.... Defines PF�1/PF�2,MSG=...command.... Defines PF�2other keys ........ Define as many as you want/PROFS,ID=USER1,KEYS=SAVE,R=resname Set up defaults for USER1/PROFS,ID=USER2,KEYS=SAVE,R=resname Set up defaults for USER2/PROFS,ID=USER3,KEYS=SAVE,R=resname Set up defaults for USER3/LOGOFF

110 Commands Guide

/PURGPG

/PURGPG

The /PURGPG command deletes additional pages of an output message thatare queued. All queued output for a logical terminal can also be deleted using aform of this command.


/PURGPG

��──/PURGPG─ ──┬ ┬────────────────────── ──────────────────────────�� └ ┘──, ──┬ ┬─LT──── =station └ ┘─LTERM─

LTERMDefines the logical terminal (station) from which queued output is to bepurged. LTERM and LT can be used interchangeably. If no logical terminalis specified (that is, LTERM is omitted), only the pages of the currentlydisplayed message are purged.


Required: No

Usage Notes

The default value for PF1 (3270 program function key 1) has the same effect asentering /PURGPG.

Use of /PURGPG is not necessary if:

■ /NXTMSG is to be the next entry.

■ Another command is to be the next entry.

■ A /LOGON is to be the next entry.

■ The terminal is to be logged off.

Examples/PURGPG

/PURGPG,LTERM=INPUT


/REFRESH

/REFRESH

The /REFRESH command refreshes the UID resource table that was loadedduring Unicenter CA-7 initialization without cycling Unicenter CA-7.


/REFRESH

��──/REFRESH─ ──,MOD= ──┬ ┬─membername─ ────────────────────────────�� └ ┘─MSGRCNTL───

MOD=membernameDefines a UID resource table in load module format that was built using theCA7RTBL macro. This must be the member name of the UID resourcetable and it must reside in a load library accessible to Unicenter CA-7. Thename MSGRCNTL is reserved.

If MOD=SERVDESK is specified, the Unicenter Service Desk filter rules arereread from the SERVDESK DD statement.

For a discussion of the Unicenter CA-7 UID resource table, see the SecurityGuide.

MOD=MSGRCNTLSpecifies to dynamically refresh control options for Unicenter CA-7 MasterStation Message Routing (MSMR). These options are set in the UnicenterCA-7 MSMR Control File (MSGRCNTL DD statement in the Unicenter CA-7JCL).

Use /REFRESH,MOD=MSGRCNTL when you want to update the list ofmessage recipients or when you want to alter message selection orcustomization criteria without having to recycle the Unicenter CA-7 startedtask.


Required: Yes

Note: During the brief interval required for processing/REFRESH,MOD=MSGRCNTL, messages may occasionally appear to beimproperly selected or excluded. Most users will tolerate such behavior toavoid the overhead of recycling Unicenter CA-7.

If this exposure is considered unacceptable, users should issue thecommand at a time when few messages are being generated or attempt toquiesce activities that produce messages prior to issuing the command.

For more information about Unicenter CA-7 Master Station MessageRouting (MSMR), see the chapter "Execution" in the Systems ProgrammerGuide.

112 Commands Guide

/RELINK

/RELINK

The /RELINK command dynamically loads a new copy of a Unicenter CA-7module without having to shut down the product.


/RELINK

��──/RELINK─ ──, ──┬ ┬─A──── = SASSxxxx ──┬ ┬────────────────── ────────�� └ ┘─APPL─ └ ┘──, ──┬ ┬─U────── =xx └ ┘─USERID─

OR

/RELINK

��──/RELINK─ ──, ──┬ ┬─FM───── = ──┬ ┬──SFMxyyyy ───────────────────────�└ ┘─FMTBLK─ └ ┘──SCALyyyy

�─ ──┬ ┬────────────────── ────────────────────────────────────────�� └ ┘──, ──┬ ┬─U────── =xx

└ ┘─USERID─

APPLDefines the Unicenter CA-7 program module to be relinked. A and APPLcan be used interchangeably, but one or the other must be specified torelink a program module. Both must be omitted if FM or FMTBLK is to beused. Value must be the module name in the format SASSxxxx where xxxxis the last four characters of a module name.

Limits: 8 alphanumeric characters

Required: Yes

FMTBLKDefines the Unicenter CA-7 format block/calendar block to be relinked. FMand FMTBLK can be used interchangeably, but one or the other must bespecified to relink a format block of a calendar module. Both must beomitted if A or APPL is to be used.


Required: Yes

SFMxyyyyDefines format block name where x is A for batch, H for online, andyyyy is the last four characters of a module name.

SCALyyyyDefines calendar block name where yyyy is the last four characters of amodule name.


/RELINK

USERIDDefines a prefix to replace the first two characters of the standard modulename. U and USERID can be used interchangeably. Value, if used, can beany two characters with the first character being alphabetic.


Required: No

Usage Notes

You can only issue /RELINK on modules defined with an APPLCTN statementin the initialization file or those in SASSPROG. The relink of a module occursonly when it is not in use. The use count must be 0 on the /DISPLAY(A=module name command) that indicates that the current version is no longerrequired. You cannot use /RELINK for a PERM or RESD module, the logon exitmodule, or a module included in the link-edit of UCC7.

Examples/RELINK,APPL=SASSSCM5

/RELINK,A=SASSSP�3,USERID=XX

/RELINK,FMTBLK=SFMASDM�,U=ZZ

/RELINK,FM=SFMHSCRJ

/RELINK,FM=SCAL�5XX

114 Commands Guide

/RESET

/RESET

The /RESET command resets the Unicenter CA-7 assigned job numbers tobegin again with job number 1. Numbers in use at the time of the command areskipped.


/RESET

��──/RESET──────────────────────────────────────────────────────��

No keywords are associated with this command.


/SDESK

/SDESK

The /SDESK command opens a request in Unicenter Service Desk. TheSERVICEDESK initialization file statement must be present for the command tobe honored.


/SDESK

��──/SDESK─ ──,EVENT=xxxxxx ──┬ ┬─────────────── ───────────────────��└ ┘──,JOB=xxxxxxxx

EVENTDefines the six-character event name to use when building the request forUnicenter Service Desk. The event name must be exactly six characterslong and must be predefined to the CAISDI/els event library (the eventlibrary is defined on the CAISDI/els utility CSDECNTL command DEFINE).EVENT is required and has no default.

JOBDefines a job name or Unicenter CA-7 job number of a job in the request,ready, or active queues. If JOB is specified, the job information is used tofill in variables in the CAISDI/els event. If a job name is entered, the queuesare searched in the order of request, ready, then active. JOB is optional.

116 Commands Guide

/SHUTDOWN

/SHUTDOWN

The /SHUTDOWN command causes a normal termination of Unicenter CA-7execution. Due to the impact of shutting down Unicenter CA-7, you should usethe /SHUTDOWN command with caution.

The /SHUTDOWN command can only be used by a terminal specified as theMaster or Alternate Master (CONS=MASTR or CONS=ALTRN on the TERMstatement in the initialization file).

You can set default /SHUTDOWN options on the OPTIONS statement in theinitialization file. These options take effect if you enter /SHUTDOWN with noparameters.


/SHUTDOWN

��──/SHUTDOWN──,─ ──┬ ┬────── ─────────────────────────────────────�� ├ ┤─DMPQ─

└ ┘ ─ ─Zn ──

DMPQSpecifies that the Unicenter CA-7 queues, except the SCRQ and DQTQ areto be unloaded during the shutdown process. These queues are unloadedto the Unicenter CA-7 queue dump file. The data in the queues is notdeleted, only read. If only DMPQ is specified, Unicenter CA-7 does notterminate until all batch terminal processing is completed and all onlineterminals are logged off.

Note: The VRM database component contains "active" resource recordsthat relate to jobs currently in the Unicenter CA-7 queues. These activerecords are dumped to the VRM dump queue file ddname CA7VDMP andare date/time stamped to match the queue records to ensuresynchronization during MOVQ processing.

Required: No


/SHUTDOWN

ZnSpecifies the method of shutdown as follows:

Z1Specifies a "fast" shutdown of Unicenter CA-7. Messages are not sentto the individual terminals, and Unicenter CA-7 does not wait for themto log off but waits for batch type terminals to complete (this includesCAICCI terminals).

Z2Specifies that shutdown is to occur even if batch type terminals are stillactive but waits for online terminals to log off.

Z3Specifies that shutdown is to occur even if online and/or batch typeterminals are active.

Z4Specifies a combination of Z1 and DMPQ.

Z5Specifies a combination of Z3 and DMPQ.

Note: If a form of Zn is not specified, Unicenter CA-7 does notterminate until all terminals have logged off. No batch type terminalscan be active.

If a BTI is active when a shutdown is done with a "fast" option thatincludes not waiting for batch type terminals, Unicenter CA-7 canpossibly abend (S002, for example). This is because of IO controlblocks that can be changing status (OPEN/CLOSE) during an IOoperation.

118 Commands Guide

/SHUTDOWN

Usage Notes

Shutdown is normally issued from an online terminal. It is possible to issue thecommand from a batch terminal, if necessary. Shutdown is not supported froma trailer terminal (SASSTRLR or U7SVC) or by the TSO/ISPF interface.

For online terminals, a verification process is required before shutdown canoccur. After the /SHUTDOWN command is entered, Unicenter CA-7 is put in ashutdown status. The terminal that entered the shutdown receives a messageindicating the options entered for the shutdown. If the displayed options arecorrect, then shutdown occurs when Enter is pressed. If the options are notcorrect, the /SHUTDOWN command can be changed and reentered. When two/SHUTDOWN commands with the same options are entered consecutively,Unicenter CA-7 shuts down.

If you specified a default shutdown type in the initialization file, you can enterthe /SHUTDOWN command without any parameters, and the default option isselected for normal termination of Unicenter CA-7.

If a batch terminal requested the shutdown, only one SHUTDOWN command isrequired to shut down the system.

If a console (DEVICE=CONSL) enters the /SHUTDOWN command, theoperator must enter the command a second time for verification for theshutdown to occur.

While in the shutdown mode (and until Enter is pressed or two /SHUTDOWNcommands with the same options are entered), other terminals enteringcommands receive the following message:

CA-7.�1� UNIDENTIFIED COMMAND

The terminal that entered the /SHUTDOWN command is allowed to entercertain slash (/) commands (/LOGOFF, /DISPLAY, and so on) between the"consecutive" /SHUTDOWN commands. If an invalid command is entered whileUnicenter CA-7 is in shutdown mode, the terminal receives an error messagestating that the command must be /SHUTDOWN. Unicenter CA-7 can be shutdown without terminating ICOM if Unicenter CA-7 controlled jobs are still activein OS. However, if Unicenter CA-7 is to be down for a long period of time, werecommend that ICOM be stopped.


/START

/START

The /START command restarts line groups and terminals following correction ofan I/O error or after the line or terminal has been stopped with a /STOPcommand.


/START

��──/START─ ──┬ ┬────────────────── ──┬ ┬────────────────────── ──────� └ ┘──, ──┬ ┬─L──── =line └ ┘──, ──┬ ┬─LT──── =station └ ┘─LINE─ └ ┘─LTERM─

�─ ──┬ ┬──────────────────── ──┬ ┬──────────────────────────── ──────�� └ ┘──, ──┬ ┬─M─── =PROMPTS └ ┘──, ──┬ ┬─T──── = ──┬ ┬─terminal─

└ ┘─MSG─ └ ┘─TERM─ └ ┘─ALL──────

LINEDefines the line to be started. L and LINE can be used interchangeably.One or the other is required when starting an entire line. When starting aterminal, LINE or L can also be given to qualify the terminal name. Bothmust be omitted if LTERM (or LT) is specified.


Required: No

LTERMDefines a logical terminal (station) for which activities involving output are tobe started. LT and LTERM can be used interchangeably. One or the otheris required when the command is to impact a logical terminal. Both must beomitted if LINE (or L) or TERM (or T) is specified.


Required: No

MSGSpecifies prompting for a specific logical terminal is to be started. MSG isrequired to invoke this function. However, it can only be used with LTERM(or LT). Value if used must be MSG=PROMPTS.

Required: Yes - for LTERM option

120 Commands Guide

/START

TERMSpecifies a real terminal is to be started. TERM or T can be usedinterchangeably. One or the other must be used to start a terminal.

terminalDefines the terminal name.


ALLSpecifies restart all terminals.

Usage Notes

A /START command is not a valid command for a batch terminal.

Examples/START,T=RTERM1

/START,LTERM=KEYPUNCH

/START,L=VLINE,T=ALL


/STOP

/STOP

The /STOP command stops line groups and terminals started by the /STARTcommand. You can use it to stop a terminal having I/O errors.


/STOP

��──/STOP─ ──┬ ┬────────────────── ──┬ ┬────────────────────── ───────� └ ┘──, ──┬ ┬─L──── =line └ ┘──, ──┬ ┬─LT──── =station └ ┘─LINE─ └ ┘─LTERM─

�─ ──┬ ┬──────────────────── ──┬ ┬──────────────────────────── ──────�� └ ┘──, ──┬ ┬─M─── =PROMPTS └ ┘──, ──┬ ┬─T──── = ──┬ ┬─terminal─

└ ┘─MSG─ └ ┘─TERM─ └ ┘─ALL──────

LINEDefines the line to be stopped. L and LINE can be used interchangeably.One or the other is required when stopping an entire line. When stopping aterminal, LINE (or L) can also be given to qualify the terminal name. Bothmust be omitted if LTERM (or LT) is specified. Value for either usage mustbe the line name, up to seven characters.


Required: No

LTERMDefines a logical terminal (station) for which activities involving output are tobe stopped. LT and LTERM can be used interchangeably. One or the otheris required when the command is to impact a logical terminal. Both must beomitted if LINE (or L) or TERM (or T) is specified.


Required: No

MSGSpecifies prompting for a specific logical terminal is to be stopped. MSG isrequired to invoke this function. However, it can only be used with LTERM(or LT). Value if used must be MSG=PROMPTS.

Required: Yes - for LTERM option

122 Commands Guide

/STOP

TERMDefines a real or batch terminal is to be stopped. TERM (or T) can be usedinterchangeably. One or the other must be used to stop a terminal.

terminalDefines the real or batch terminal name.


ALLSpecifies to stop all terminals started by the /START command.

Usage Notes

When a /STOP command is issued for a logical terminal, any output currentlyqueued is not sent to the physical terminal to which the logical terminal isassigned. New output for a stopped logical terminal is queued but not sent.Queued output is available when the logical terminal is restarted.

Examples/STOP,L=VLINE

/STOP,LINE=RLINE1,TERM=ALL

/STOP,LTERM=DATACNTL,MSG=PROMPTS


/SWAP

/SWAP

The /SWAP command causes Unicenter CA-7 to switch log record recording toan alternate log file. This in turn causes the current log file to be closed and thelog dump job to be automatically submitted.

Alternating DASD log files must have been defined with ALOG1 and ALOG2statements in the initialization file for this command to be useful.


/SWAP

��──/SWAP───────────────────────────────────────────────────────��

No keywords are associated with the /SWAP command.

124 Commands Guide

/UID

/UID

The /UID command alters the current user's UID security level. The /UIDcommand is valid only in environments where external security controlsUnicenter CA-7 logons.


/UID

��──/UID─ ──,R=resname ───────────────────────────────────────────��

or

/UID

��──/UID─ ──,LIST ────────────────────────────────────────────────��

RDefines the resource name defined in the UID resource table.


Required: Yes

LISTSpecifies the UID resource table loaded during Unicenter CA-7 initialization.

Examples

Example 1:

/UID,R=CA7�255

SCM9-21 UID VALUE UPDATED.

Example 2:

/UID,R=R99�BAD

SCM9-17 RESOURCE (R99�BAD) NOT FOUND IN CA-7 RESOURCE TABLE.


/WLB

/WLB

The /WLB command changes the workload balancing function of the UnicenterCA-7 system. For more information, see the Systems Programmer Guide.


/WLB

��──/WLB─ ──,SET= ──┬ ┬─ON── ───────────────────────────────────────�� └ ┘─OFF─

or

/WLB

��──/WLB─ ──,SET= ──┬ ┬──CLASSx ──,BARR= count/+count/-count ─────────�� ├ ┤─INITS── ├ ┤─MINJOB─ ├ ┤─T1TAV── ├ ┤─T1MAX── ├ ┤─T2TAV── └ ┘─T2MAX──

SETSpecifies whether to activate or deactivate the workload balancing function.

ONSpecifies to activate the workload balancing function.

OFFSpecifies to deactivate the workload balancing function. Workloadbalancing remains off until the system is brought down or until it isreactivated manually with SET=ON.

SETSpecifies the selection parameter to be adjusted. Use one of the followingvalues:

CLASSxSpecifies class barrier x, where x is A-Z or 0-9

INITSSpecifies total initiators

MINJOBSpecifies minimum jobs to schedule

T1TAVSpecifies available type 1 tapes

T1MAXSpecifies maximum allowable type 1 tapes

126 Commands Guide

/WLB

T2TAVSpecifies total available type 2 tapes

T2MAXSpecifies maximum allowable type 2 tapes

BARRDefines the number to replace or adjust the current value. An unsignedvalue replaces the current value. Signed values indicate an amount bywhich the current value is to be adjusted. Any value that causes a barrier toexceed its maximum (255) causes the barrier to be set to its maximum.


Required: Yes, unless SET=ON or OFF


/WTO

/WTO

The /WTO command sends a free-form message to the OS master console.This command is allowed from a Unicenter CA-7 trailer step.


/WTO

��──/WTO─ ──, ──┬ ┬─M─── =text ──────────────────────────────────────�� └ ┘─MSG─

MSGDefines the message that is sent to the OS master console. MSG and Mcan be used interchangeably, but one or the other is required. If commasare included as part of the text, enclose the entire message text inparentheses.


Required: Yes

Examples/WTO,MSG=BILLING EDIT RUN NEEDS PRIORITY

/WTO,M=(CANCEL BILLING CYCLE, INPUT NOT RECEIVED)

The first example would appear on the Unicenter CA-7 job or JES log listing as:

CA-7.WTO ttttttt - BILLING EDIT RUN NEEDS PRIORITY

where:

tttttttIs the terminal from which the message originated.

128 Commands Guide

ADDRQ

ADDRQ

The ADDRQ command manually adds temporary, one-time, preexecution useror predecessor job requirements. These requirements must be added to the jobwhile it is in the Unicenter CA-7 request queue. These added requirementsapply only to the current run of the job. User requirements must be manuallysatisfied with the QM.2 panel (POST) or XRQ command before the jobexecutes. Predecessor job requirements are satisfied automatically when thepredecessor job completes successfully.


ADDRQ

��──ADDRQ─ ──,JOB= ──┬ ┬─jobname─── ──, ──┬ ┬──DEPJOB=depjob ──────────��└ ┘─jobnumber─ └ ┘──USR=text ─────

JOBDefines the job to which the job requirement is to be added. The job mustbe in the request queue.

Required: Yes

jobnameDefines the job name to which the requirement is to be added for thisrun of the job.


jobnumberDefines the Unicenter CA-7 job number to which the requirement is tobe added for this run of the job.


DEPJOBDefines a temporary onetime job dependency requirement. The DEPJOBvalue specifies the job name that must complete execution or be manuallyposted complete before the job identified by JOB is eligible for submission.DEPJOB is required unless USR is used, in which case DEPJOB must beomitted. This requirement is satisfied automatically when the predecessorjob completes. Only in unusual situations would this requirement need to besatisfied manually. That is, any time that a normal completion did not occur.


Required: Yes, unless USR is used


ADDRQ

USRDefines the description of a temporary, onetime user requirement. Thisrequirement must be manually satisfied before the job identified by JOB iseligible for submission. If commas are included as part of the text, enclosethe entire requirements text in parentheses. USR is required unlessDEPJOB is used, in which case USR must be omitted.


Required: Yes, unless DEPJOB is used

Usage Notes

Use of this command does not affect the normal requirements as defined in thedatabase. Once defined, this functions just as if it had been defined on theDB.3.6 panel. If either requirement type is to apply to every run of the job, thedatabase should be so updated using the DB.3.2 or DB.3.6 panels.

The ADDRQ command only updates the record of the job in the request queue,not the database. These requirements are flagged on QM.2 displays with an Ain the E column.

ExamplesADDRQ,JOB=17,DEPJOB=PAYJOB1

ADDRQ,JOB=XYZ,DEPJOB=ABC

ADDRQ,JOB=2,USR=USER WILL CALL TO RELEASE

130 Commands Guide

ADDSCH

ADDSCH

The ADDSCH command delays scheduled start and due-out times for up to 24hours.

After a job has entered a queue, it is sometimes necessary to delay thescheduled start time or due-out time. It may even be necessary to delay theentire workload already in a queue to react to a major unexpected andunscheduled change in the environment.


ADDSCH

��──ADDSCH──,─ ──┬ ┬──JOB= ──┬ ┬─nnnn─ ──,TIME=mmmm ──────────────────�� │ │├ ┤─ALL── │ │└ ┘─ALLP─

└ ┘──REF=nnnnrrss ──

JOBSpecifies the jobs whose schedule times should be delayed. JOB isrequired unless REF is used, in which case JOB must be omitted.

Required: Yes

nnnnDefines the job number of a single job assigned by Unicenter CA-7.


ALLSpecifies all jobs and workstation entries in the request, ready, active,and postprocess queues.

ALLPSpecifies all jobs and workstation entries including those in thepreprocess queue.

REFDefines a particular workstation task within a network (and all subsequentstations) whose schedules should be delayed. REF is required if JOB is notused.

nnnnrrsDefines a workstation task reference number assigned by UnicenterCA-7.


Required: Yes

nnnnDefines the Unicenter CA-7 job number.


ADDSCH

rrDefines the relative sequence of the network in relation to othernetworks associated with the job. For input networks, the value is00.

sDefines the position of the station within the network. The firststation would be position 1.

TIMEDefines the amount of time to be added to the start time and due-out timeof the jobs or workstations indicated. Value must be in minutes.


Required: Yes

Usage Notes

Delaying a single job or stream of jobs might be necessary if input is notavailable on time or if an abend is causing a rerun that must complete beforesubsequent processing can continue. It might be necessary to delay the entireworkload in the event of a CPU failure.

Note: If the job scheduled time is adjusted over a midnight boundary, the nextday's run of the job may not be brought in because of duplicate checkingperformed. See the PERFORM option of the INIT statement in the initializationfile for more information about duplicate checking.

When schedules are delayed using the ADDSCH command, prompting is basedon the adjusted start time and due-out time.

To provide earlier schedule times, see “SUBSCH” on page 596.

The QM.3 panel can be used to adjust individual job schedules.

The use of this command only affects the due-out-time and deadline start-timeof a job, which in turn affects when the job or task is late. If job submission isnot to occur, a requirement needs to be added to a job.

ExamplesADDSCH,JOB=143,TIME=12�

ADDSCH,JOB=ALLP,TIME=144�

ADDSCH,REF=12��1,TIME=6��

132 Commands Guide

AL/ALC

AL/ALC

The AL command allocates a DASD data set. The ALC command allocates andcatalogs a DASD data set. This function is available on the UT Menu panel asFUNCTION value 1 or on any other menu or formatted panel as FUNCTIONvalue UT.1.


AL ALC

��─ ──┬ ┬─AL── ──,DSN=dsname ──,VOL=volume ───────────────────────────� └ ┘─ALC─

�─ ──,SP= ( type,primary, ──┬ ┬─────────── , ──┬ ┬──────────────── ) ──────� └ ┘ ─secondary─ └ ┘ ─directory-blks─

�─ ──,DCB=(recfm,lrecl,blksize) ──────────────────────────────────��

DSNDefines the fully qualified name of the data set.


Required: Yes

VOLDefines the volume serial number on which the data set is to be allocated.The volume must have been made available to Unicenter CA-7 with aU7volser type of DD statement as discussed in the Systems ProgrammerGuide, or “ALLOC” on page 135.


Required: Yes

SPSpecifies space allocation. For each of the following parameters, a commamust be coded for each parameter that is omitted, or the default value isassumed. Parameters used must be enclosed in parentheses.

typeSpecifies either T for tracks or C for cylinders.

Default: T

primaryDefines primary space allocation amount.


Required: Yes


AL/ALC

secondaryDefines an optional secondary space allocation amount.


Required: No

directory-blksDefines the number of directory blocks to be allocated for a PDS dataset. If the number of directory blocks is zero, DSORG=PS is assumed.If nonzero, DSORG=PO is assumed.

Default: 0


DCBDefines the data control block (DCB) attributes. Parameters must be inparentheses.

recfmSpecifies the record format. Value must be F, FB, V, VB, VBS, VS, U,FA, FBA, FM, FBM, VA, VBA, VM, or VBM.

Required: Yes

lreclDefines the logical record length.

Default: 0


blksizeDefines the block size of the data set.

Default: 0


ExamplesAL,DSN=USER.FILE1,VOL=VOLMO1,SP=(T,2),DCB=(F,8�,8�)

ALC,DSN=USER.TEMP,VOL=VOLMO1,SP=(T,5),DCB=(FB,64,64�)

134 Commands Guide

ALLOC

ALLOC

The ALLOC command dynamically allocates a volume not defined by a DDstatement in the execution JCL for Unicenter CA-7. The dynamically allocatedddname is U7 followed by the volume serial number. For an example of theddname format, see “SCRATCH” on page 584. This function is available onthe UT Menu panel as FUNCTION value 11 or on any other menu or formattedpanel as FUNCTION value UT.11.


ALLOC

��──ALLOC─ ──,VOL=volume ──,UNIT=unit ─────────────────────────────��

VOLDefines the volume you want to allocate.


Required: Yes

UNITDefines the unit name for the type of DASD device you want (for example,3380, DISK, SYSDA).


Required: Yes

ExamplesALLOC,VOL=DISK�1,UNIT=338�


APA

APA

The APA command displays a menu panel for online access to graphingfacilities for each of the available categories of graphs. It has no equivalent inbatch mode.

To display, enter:

■ APA as a top line command.

■ APA as the function value on any other menu or formatted input panel.

To exit, enter:

■ A command on the top line.

■ The name of any other formatted panel as the FUNCTION.

APA Menu

� � ----------------- CA-7 AUTOMATED PERFORMANCE ANALYSIS MENU ----------------- FUNCTION ===>

DISPLAY PERFORMANCE FOR: 1 - CPU JOBS

2 - CA-7 SYSTEM ACTIVITY3 - CA-7 DATA BASE ACTIVITY

4 - INPUT/OUTPUT NETWORKS

PROGRAM: MLR� MSG-INDX: nn -- APA -- yy.ddd / hh:mm:ss MESSAGE:

� �

Usage Notes

To select a function, enter the appropriate number in the FUNCTION field andpress Enter. The “APA Prompt Panel” on page 137 is returned. You canrequest specific graphing options with that panel.

You can find more information about APA graphs and their descriptions in theReports Guide.

136 Commands Guide

APA

APA Prompt Panel

Use this formatted panel to specify online APA graphing options. It has noequivalent in batch mode. The top line GRAPHc commands discussed on“GRAPHc” on page 255 can be used in batch mode to provide hardcopygraphs.

To display, enter:

■ An option on the APA menu panel.

■ AP.n as a top line command where n is one of the menu options.

■ AP.n as a FUNCTION value on another formatted panel.

■ GRAPH as a top line command.

■ GRAPH as the function value on any other formatted panel.

■ One of the GRAPHc top line commands without any other keywords.

This panel also displays when an error occurs on an online top line GRAPHccommand.

� � ---------------- CA-7 AUTOMATED PERFORMANCE ANALYSIS PROMPT ---------------- FUNCTION ===> xxxxxxxx CATEGORY: x (xxxxxxxx)

G - GRAPH(S) BELOW (DEFAULT) D - PARAMETER DEFINITIONS H - HELP LIST OF GRAPH IDS C - COUNTER CONTENTS

DESIRED GRAPHS: ID1: nnnn ID2: nnnn ID3: nnnn ID4: nnnn ID5: nnnn ID6: nnnn ID7: nnnn ID8: nnnn ID9: nnnn ID1�: nnnn

FROM: MM: mm DD: dd YY: yy DEFAULT IS TODAY;MM WITHOUT DD DEFAULT IS DD = �1

THRU: MM: mm DD: dd YY: yy DEFAULT IS TODAY;MM WITHOUT DD DEFAULT IS DD = LAST DAY

TEMPORARY OVERRIDES:SCALE: nnnnnnn DIV1: nnnnnn DIV2: nnnnnnn (UP TO 7 DIGITS EACH)GLINE: x (P = PRIM, S = SCND, C = CALC)

PROGRAM: MLRF MSG-INDX: nn -- AP.n -- yy.ddd / hh:mm:ss MESSAGE:

� �

Usage Notes

The CATEGORY field can be changed and is blank if command GRAPH isentered.

This panel appears with CATEGORY filled in if one of the APA commands isentered without other keywords; that is, GRAPHS would produce this panel withCATEGORY of S.


APA


FUNCTIONSpecifies the function that you want. Optional. The following are thepossible values:

GDisplays graphs specified by the CATEGORY and ID fields on thispanel. This is the default.

CDisplays contents of current counters for every graph specified by theCATEGORY field. Same as LIST=ALL option on equivalent top linecommand.

DDisplays graph format parameter definitions for every graph specified bythe CATEGORY field. Same as LIST=DETL option on equivalent topline command.

HDisplays directory list of every ID and title specified by the CATEGORYfield. Same as LIST=HELP option on equivalent top line command.

The name of any other formatted panel can be entered.

CATEGORYSpecifies a graph category. Required field. If accessed from the APA Menupanel, with a DB.n command or FUNCTION, or with a top line GRAPHccommand without any other keywords, this is completed for you. You canchange this if you want. If accessed through the GRAPH command (orfunction), this must be entered. Descriptive name of the category isenclosed in parentheses following the value. Categories and theirdescriptive names are as follows:

DDATABASE

JJOBS

NNETWORKS

SSYSTEM

???????indicates a category value is needed.

138 Commands Guide

APA

The following fields are ignored unless FUNCTION is G or blank.

DESIRED GRAPHSID values of up to 10 individual graphs to be displayed one after the other.Same as ID keyword on equivalent top line command. Numeric ID in up tofour digits. Leading zeros not required. Function H or the equivalent top linecommand with LIST=HELP lists the available graph ID numbers. TheReports Guide also provides a brief discussion of each graph.

FROMSpecifies a beginning date for which data is to be displayed. Optional.Cannot be older than 2 years prior to today's date. Default is today's date.Same as keyword FROM on equivalent top line command.

MMSpecifies a month portion of FROM date. Optional. Default is current month.MM format. Leading zero not required. Must be at least 1 and not morethan 12.

DDSpecifies a day portion of FROM date. Optional. If MM value was given,default is 01. If MM value was not given, default is current date. DD format.Leading zero not required. Must be at least 1 and not more than 31.

YYSpecifies a year portion of FROM date. Optional. Default is current year. YYformat. Leading zero not required. Must be numeric.

THRUSpecifies a last date for which data is to be displayed. Optional. Default istoday's date. Any date beyond today's date is automatically changed tocurrent date. Same as keyword TO on equivalent top line command.

MMSpecifies a month portion of THRU date. Optional. Default is current month.MM format. Leading zero not required. Must be at least 1 and not morethan 12.

DDSpecifies a day portion of THRU date. Optional. If MM value was given,default is last day of that month. If MM value was not given, default iscurrent date. DD format. Leading zero not required. Must be at least 1 andnot more than 31.

YYSpecifies a year portion of THRU date. Optional. Default is current year. YYformat. Leading zero not required. Must be numeric.


APA

TEMPORARY OVERRIDESSpecifies a temporary override to graph scale increment. Up to seven digits.Optional field. Same as keyword SCALE on equivalent top line command.Function D or top line command with LIST=DETL lists the predefined valueunder the heading SCALE. The value used is shown as part of the graphheading. When provided, each graph specified in the ID fields uses thisoverride value.

DIV1Specifies a temporary override to division factor for the primary counter. Upto seven digits. Optional field. Same as keyword DIV1 on equivalent top linecommand. Function D or top line command with LIST=DETL lists thepredefined value under the heading DIV1. When provided, each graphspecified in the ID fields uses this override value.

DIV2Specifies a temporary override to division factor for the secondary counterfor each graph requested. Up to seven digits. Optional field. Same askeyword DIV2 on equivalent top line command. Function D or top linecommand with LIST=DETL lists the predefined value under the headingDIV2 if one exists. Only valid if a value is shown there. When used, eachgraph defined in the ID fields must be the type that has a predefined DIV2value.

GLINESpecifies a temporary override to which value is used on the graph line.Optional field. Similar to keyword GLINE on equivalent top line command.Function D or top line command with LIST=DETL lists the predefinedvalues. If that list indicates PRIM under the GRAPH heading for a graph,PRIM is the only valid option for that graph. When used, each graphdefined in the ID fields must be compatible with the value entered here.

Enter the value you want and press Enter. The entered values are convertedinto the equivalent top line command and processed accordingly. That top linecommand is echoed at the top of the resulting displays. It can be modified toperform another display or any other top line command can be entered in itsplace. For more information about the keywords used with that top linecommand technique, see the discussion of “GRAPHc” on page 255.

This panel allows data to be entered that could require more than the maximumof 80 characters to be echoed on the top line of the resulting display panels.Functions H, D, and C require less than 80. Fields that cannot entirely fit intothe available space for the command echo are dropped completely from theecho even though they are being processed. Fields are placed in the echo areain the sequence in which they appear on the panel. If no value was entered,nothing is echoed.

The display may require multiple panels to complete. The last panel has amessage at the bottom indicating "request completed."

140 Commands Guide

APA

PF7 and PF8 are temporarily overridden to page backward/forward for ease inbrowsing any multipage display that may occur. If PF7 or PF8 were set to someother values by the user, those values are temporarily ignored. They revertback to the values defined by the user whenever PF3 or a top line command isentered.

PF3 is also temporarily overridden to return to the APA menu panel.


ARFP

ARFP

The ARFP command purges the ARF requirement for a job in the request,ready, or active queue.


ARFP

��──ARFP─ ──,JOB=jobnumber ──┬ ┬──────────── ───────────────────────��└ ┘──,FORCE=YES

JOBDefines the unique Unicenter CA-7 job number (leading zeros not required)for the job whose ARF requirements are to be purged.

FORCESpecifies to force the purging of the ARF requirement for a job even if itdoes not exist in the request, ready, or active queue.

ExampleARFP,JOB=23

142 Commands Guide

ARTS

ARTS

If you have installed the Unicenter CA-7 Unicenter CA-11 interface, the ARTScommand can interface directly with Unicenter CA-11. For more informationabout the Unicenter CA-7 Unicenter CA-11 interface and the ARTS command,see the Interfaces Guide.


AR.3

AR.3

You can find more information about defining ARF conditions using the AR.3command in the Database Maintenance Guide.

144 Commands Guide

BLDG

BLDG

The BLDG command builds a generation data group (GDG) index. Thiscommand is valid only for CVOL catalogs.

Note: It is not valid for VSAM or ICF catalogs.

This function is available on the UT Menu panel as FUNCTION value 6 or onany other menu or formatted panel as FUNCTION value UT.6.


BLDG

��──BLDG─ ──,INDX=index ──,ENTRIES=nnn ──┬ ┬──────────────────── ────�� │ │┌ ┐─DELETE─

└ ┘──,FULL= ──┴ ┴─EMPTY──

INDXDefines the name of the GDG index.


Required: Yes

ENTRIESDefines the number of entries to be contained in the GDG index.


Required: Yes

FULLSpecifies action to be taken once the ENTRIES value is exceeded.

Default: DELETE

Required: No

DELETESpecifies the oldest entry is to be removed.

EMPTYSpecifies all entries are to be removed.


BLDG

ExamplesBLDG,INDX=USER.FILE.MONTHLY,ENTRIES=2

BLDG,INDX=USER.FILE.DAILY,ENTRIES=7,FULL=EMPTY

BLDG,INDX=USER.DAILY.FILE1,ENTRIES=3�,FULL=DELETE

For more informatin about restrictions and guidelines on the use of BLDG, seemessage UTL5-14 in the Message Guide.

146 Commands Guide

CALMOD

CALMOD

The CALMOD command displays the DB.2.8 Base Calendar Maintenancepanel. You can find more information about this panel in the DatabaseMaintenance Guide.


CALMOD

��──CALMOD──────────────────────────────────────────────────────��

No keywords are associated with the CALMOD command.


CANCEL

CANCEL

The CANCEL command deletes jobs from the Unicenter CA-7 queues. Thiscommand only removes the job from the Unicenter CA-7 queues. Cancellationof a job in the Unicenter CA-7 active queue or ready queue (if it has beensubmitted) does not cause termination of the job's execution. CPU jobs that canbe executing have to be canceled from the operating system separately.Execution must be terminated from an OS system console. This function isavailable on the QM.1, QM.6, and QM.7 panels as option C. The CANCELcommand has three formats, depending on the queues in which the taskresides.

Input Networks

This command has the following format for input networks:

CANCEL

��──CANCEL─ ──,JOB=jobnumber ─────────────────────────────────────��

JOBDefines the unique Unicenter CA-7 job number (leading zeros not required)for the workstation network to be canceled.


Required: Yes

148 Commands Guide

CANCEL

Request, Ready or Active Queue Jobs

This command has the following format for request, ready or active queue jobs:

CANCEL

��──CANCEL─ ──,JOB= ──┬ ┬─jobname─── ──┬ ┬──────────── ────────────────�└ ┘─jobnumber─ └ ┘──,FORCE=YES

�─ ──┬ ┬────────────── ────────────────────────────────────────────��└ ┘──,REASON=text

JOBDefines the job to be canceled.

Required: Yes

jobnumberDefines the unique Unicenter CA-7 job number (leading zeros notrequired) for the job to be canceled.


jobnameAllows canceling a job by job name if only one job with that name ispresent in the request queue.


FORCESpecifies to force the cancellation of the job. If the job to dump the log dataset is to be canceled, FORCE=YES must be specified to prevent the jobfrom being resubmitted. FORCE=YES must be used when a job to becanceled shows a status of SKELETON or RETRY. FORCE=YES must beused to cancel a job with connected resources.

Important! Use of this option can potentially cause Unicenter CA-7 toabend; therefore, it should only be used as a last resort.

Required: No

REASONDefines the reason for the job cancellation. Depending on the initializationfile CANCEL statement value, this can be required or optional. If it isrequired but not given, a message prompts the user to provide it. The textis entered into the run log entry for this occurrence of this job and isdisplayed on any subsequent LRLOG inquiries.


Required: No (depending on initialization options)


CANCEL

Output Networks

This command has the following format for output networks:

CANCEL

��──CANCEL─ ──,JOB=jobnumber ──┬ ┬─────────────────── ───────────────�└ ┘──,NW= ──┬ ┬─network─

└ ┘─ALL─────

�─ ──┬ ┬──────────────────── ──────────────────────────────────────��└ ┘──,SUBID= ──┬ ┬─subid─

└ ┘─ALL───

JOBDefines the unique Unicenter CA-7 job number (leading zeros not required)of the job whose postprocess work is to be canceled.


Required: Yes

NWDefines the networks to be canceled.

Required: No

networkDefines the network name as previously defined in the database.


ALLSpecifies to cancel all networks for the associated job.

SUBIDDefines a further qualification of the network to be acted upon. SUBID isoptional unless it was specified when the network was demanded or is partof the database definition of a regularly scheduled network. Since a singleoutput workstation network can be associated with a job multiple times andassigned unique SUBIDs for differentiation, it is important to specify correctSUBIDs when canceling work.

Required: No

subidDefines the sub-ID value.


ALLSpecifies to cancel network entries for the NW value specified nomatter what sub-ID value was used.

150 Commands Guide

CANCEL

Usage Notes

The record for the specified job is deleted from the appropriate queue, and ifUnicenter CA-11 is used, an attempt is made to clear the CMT. For moreinformation about Unicenter CA-11, see the Interfaces Guide.

Obviously, canceling a job stops all triggering by the canceled job and does notsatisfy requirements for other jobs that may be dependent on the canceled job.

The job does not go through normal job completion; therefore, job triggeringand requirement posting are not performed.

All output workstation networks for the canceled job are notified and theirrecords are deleted from the postprocess queue.

The QM.1 panel can also be used to cancel jobs.

Examples

Example 1: For a network in the preprocess queue:

CANCEL,JOB=17

Example 2: For a job in the request, ready, or active queue:

CANCEL,JOB=163,FORCE=YES

Example 3: For networks in the postprocess queue:

CANCEL,JOB=163

CANCEL,JOB=163,NW=ALL,SUBID=ALL

CANCEL,JOB=163,NW=REPTS

CANCEL,JOB=163,NW=REPTS,SUBID=ALL

CANCEL,JOB=163,NW=REPTS,SUBID=CA7HIST3


CAT

CAT

The CAT command catalogs a data set. This function is available on the UTMenu panel as FUNCTION value 2 or on any other menu or formatted panel asFUNCTION value UT.2.


CAT

��──CAT─ ──,DSN=dsname ──,VOL= ──┬ ┬─volume───────── ─────────────────� │ │┌ ┐─,────── └ ┘──( ───� ┴─volume─ )

�─ ──┬ ┬───────────────────── ──┬ ┬──────── ──┬ ┬─────────────── ──────��└ ┘──, ──┬ ┬──DVC=xxxxxxxx └ ┘──,SEQ=n └ ┘──,CVOL=cvolume

└ ┘──UNIT=unit ───

DSNDefines the fully qualified name of the data set to be cataloged.


Required: Yes

VOLDefines from one to five volumes on which the data set resides.

Required: Yes

volumeDefines the volume on which the data set resides.

(volume,...,volume)Specifies from one to five volumes as a list. If more than one volume isspecified, they must be enclosed in parentheses.


Required: Yes

DVCDefines a hexadecimal device code. This field must be omitted if UNIT isspecified.


Required: No

152 Commands Guide

CAT

UNITDefines the unit name of the type of device that you want (genericequivalent of a device code found in SASSUTBL (for example, 3350,DISK)). This field must be omitted if DVC is specified.


Required: No

SEQDefines the label sequence number.

Default: 0 for disk data sets, or1 for tape data sets

Limits: 1 numeric character

Required: No

CVOLDefines the volume containing the catalog. This option is only valid forCVOL catalog structures. If the catalog structure is ICF, it defaults to theIPL catalog.

Default: SYSRES (for CVOL catalog structures)


Required: No

Usage Notes

You can omit both DVC and UNIT if VOL specifies a DASD volume available toUnicenter CA-7.

You should update the module SASSUTBL to contain all user-defined genericnames.

You can use a +1 generation number to catalog a new version of a generationdata set.

ExamplesCAT,DSN=USER.FILE1,VOL=DA333�

CAT,DSN=USER.FILE2,VOL=DA333�,DVC=3�5�2��9

CAT,DSN=USER.FILE3,VOL=DA333�,UNIT=333�

CAT,DSN=USER.TAPE,VOL=T1��1,SEQ=3,DVC=34��8��3

CAT,DSN=USER.TAPE1,VOL=(T1��2,T1��3),UNIT=34��-3

CAT,DSN=USER.FILEX,VOL=DA��1,CVOL=ALTRES


CONN

CONN

The CONN command connects high-level indexes from the SYSRES catalog toanother catalog.

Note: It is not valid for VSAM or ICF catalogs.



CONN

��──CONN─ ──,INDX=index ──┬ ┬───────────── ─────────────────────────��└ ┘──,VOL=volume

INDXDefines the name to be entered as a high-level index in the SYSREScatalog.


Required: Yes

VOLDefines the volume serial number of the connected volume. You can omitthis field to display the connected volume for the specified index. Theconnected volume must be available to Unicenter CA-7.

Default: SYSRES (for CVOL catalog structures)


Required: No

ExamplesCONN,INDX=USER,VOL=ALTCAT

CONN,INDX=USER

154 Commands Guide

CTLG

CTLG

The CTLG command maintains and modifies the Unicenter CA-7 index data setentries. The primary use of data set entries in the index data set is to determinethe availability of input requirements for job scheduling. The three most currentcreations of each data set (by Unicenter CA-7 submitted jobs) are recorded inthe index data set, regardless of whether the data set is a GDG or not. Thevolume serial data in the index data set is informational only, since the systemcatalog remains the source for locating data sets during job processing.


CTLG

��──CTLG─ ──,DSN=dataset ──,TYPE= ──┬ ┬─ADD── ──,VOL=volser ───────────� ├ ┤─CON── ├ ┤─COPY─ ├ ┤─DEL── └ ┘─REPL─

�─ ──┬ ┬─────────────── ──┬ ┬────────── ──┬ ┬────────── ───────────────��└ ┘──,DVC=nnnnnnnn └ ┘──,ENTRY=n └ ┘──,SEQ=nnn

DSNDefines the data set name to be modified.


Required: Yes

TYPESpecifies the CTLG function to be performed. Function must be one of thefollowing:

Required: Yes

ADDSpecifies to add new entries for a data set already defined in theUnicenter CA-7 database.

CONSpecifies to consolidate system and index data set entries.

COPYSpecifies to copy system catalog entries.

DELSpecifies to delete existing entries.

REPLSpecifies to replace existing entries.

Processing for these CTLG functions is described on the following pages.


CTLG

VOLDefines up to ten volume serial numbers on which the data set resides.(See “Processing for TYPE=REPL” on page 159 for replacing entries withmore than ten volumes.) When more than one volume serial number iscoded, it must be enclosed in parentheses.


Required: Yes

DVCDefines the device type code for the data set.

Default: Device code of current entry

Limits: 8 digits - hexadecimal

Required: No

ENTRYDefines the entry to delete or replace. ENTRY is required when TYPE=DELor TYPE=REPL. ENTRY=1 is the most recent.

Limits: 1 numeric character from 1 to 3

Required: No

SEQDefines a label sequence.

Default: Label sequence of current entry


Required: No

Usage Notes

The index data set can require maintenance as follows:

■ To add an entry for a newly created data set.

■ To correct erroneous entries that are the result (or the cause) of job restartsor reruns.

The CTLG command provides the ability to:

■ ADD new entries.

■ REPLACE existing entries.

■ DELETE entries.

■ COPY information from the OS system catalog.

■ CONSOLIDATE the Unicenter CA-7 index data set and system catalog toensure the two are synchronous.

156 Commands Guide

CTLG

Examples

Example 1: For adding entries:

CTLG,DSN=CA7.DSN1,TYPE=ADD,VOL=DASD�7

CTLG,DSN=CA7.TAPEDS,TYPE=ADD,VOL=(��1,��3)

CTLG,DSN=CA7.DSN2,TYPE=ADD,VOL=DASD-7,DVC=3�5�2��9,SEQ=1

Example 2: For deleting an entry:

CTLG,DSN=CA7.DSN,TYPE=DEL,ENTRY=1

Example 3: For replacing entries:

CTLG,DSN=CA7.DSN1,TYPE=REPL,VOL=DASD�8,ENTRY=1

CTLG,DSN=CA7.DSN2,TYPE=REPL,VOL=TAPE�1,SEQ=3,ENTRY=2

Example 4: For consolidating entries:

CTLG,DSN=CA7.DSN1,TYPE=CON


CTLG

Processing for TYPE=ADD

Unicenter CA-7 automatically stores the current date and time in the new entryas creation date and time.

You can find hexadecimal values to be specified if DVC is used in an IBM DataAreas Manual under UCBTYP field.

You cannot use the ADD function if a data set to be added resides on morethan ten volumes. Catalog the data set on the system catalog, and then use theCOPY function of the CTLG facility.

When adding GDGs, consider these items with respect to how the DSN isspecified:

■ Relative generation numbers cannot be used.

■ If an absolute generation number (for example, GnnnnVnn) is specified, thatnumber is used.

■ If no generation number is given and an entry currently exists, the currentgeneration number is incremented by 1 and used for the new entry.

■ If no generation number is given and no entry currently exists, G0001V00 isassumed.

Adding an entry to record creation of an external data set is not required.However, if the new version of the data set is cataloged before the using job isscheduled, the external requirement is automatically satisfied by initialrequirements scan when the job is scheduled. If the entry is added afterscheduling of the user job, the external requirement must be manually postedas satisfied.

Processing for TYPE=DEL

When deleting a GDG entry, if the absolute generation is given in the DSN, theentry corresponding to that generation is deleted even if the ENTRY=valueindicates a different entry.

158 Commands Guide

CTLG

Processing for TYPE=REPL

Unicenter CA-7 automatically stores current date and time in the replacemententry as creation date and time.

You can find hexadecimal values to be specified if DVC is used in an IBM DataAreas Manual under UCBTYP field.

You cannot use the REPL function if the data set entry to be replaced containsmore than ten volumes. Use the COPY function to obtain the replacement fromthe system catalog.

When replacing GDG entries, no generation number is needed. The generationof the entry being replaced is used instead.

Processing for TYPE=COPY

Unicenter CA-7 automatically stores current date and time as creation date andtime for the newly copied entry.

When copying GDGs, the most current generation in the system catalog isused.

Processing for TYPE=CON

Only the most recent entry (for the data set) in each catalog is reviewed. If theentries agree, no action is taken.

If the entries disagree, the index data set entry is updated and the current dateand time are stored as creation date and time.


DB

DB

The following table gives a brief description of the DB commands. For moreinformation, see the Database Maintenance Guide where they are fullydescribed.

Command Panel Title Description

DB CA-7 Database Maintenance Menu Select from various databasemaintenance functions.

DB.1 CPU Job Definition Enter or review data related to CPU jobs.

DB.2 Scheduling Menu Access the scheduling definition formattedpanels.

DB.2.1 CPU Job Scheduling Define or review options taken for CPUjobs with date/time schedules.

DB.2.2 Input Network Scheduling Define or review scheduling options forinput networks.

DB.2.3 Output Network Scheduling Define or review options taken for outputnetwork schedules.

DB.2.4 Job Triggering Review or define jobs that triggerscheduling of other jobs when theysuccessfully complete.

DB.2.5 Input Network Triggering Define or review input networks thattrigger job scheduling when their lastworkstation is logged out.

DB.2.6 Data Set Triggering Define or review data sets that trigger jobscheduling when either their creating jobscomplete successfully or when thecreated/updated data set is closed.

DB.2.7 Modification to Resolved ScheduleDates

Provides a rapid and direct method ofpermanently altering the resolvedschedule information for either a job orinput network without having to totallyredefine the schedule.

DB.2.8 Base Calendar Maintenance List, define and update base calendarsresiding in the Unicenter CA-7 CalendarPDS.

DB.3 Job Predecessor/Successor Menu Select various panels for defining"connections" (predecessor requirements)to CPU jobs.

160 Commands Guide

DB

Command Panel Title Description

DB.3.1 Data Set Predecessors Allows you to modify requirements or toadd data set requirements for data setsthat are not used as input for the job.

DB.3.2 CPU Job Predecessors Establish predecessor job requirements.

DB.3.4 Input/Output Network Tasks Define a CPU job's requirements (orconnections) for workstation networks.

DB.3.6 User Memo-Form Predecessors Allows for user requirement of free-formtext that can be displayed on a UnicenterCA-7 terminal and that requires anoperator response before the connectedjob can execute.

DB.3.7 Report IDs Created Record information in the databaseregarding reports that are produced byCPU jobs. The information is optional andserves only as reference material foranyone wanting to review the informationat a terminal.

DB.4 Workload Documentation Menu Select various documentation functions.

DB.4.1 CPU Job Documentation Defining free-form job leveldocumentation.

DB.4.2 Input/Output Network Documentation Define network level documentation.

DB.4.3 User Defined Item Documentation Define user level documentation.

DB.4.4 Dataset Documentation Define data set level documentation.

DB.4.5 DD Statement Documentation Define DD level documentation.

DB.4.6 Application System Documentation Define system level documentation.

DB.5 Input/Output Network Definition Define networks of workstations at whichmanual tasks are performed.

DB.6 Data Set Definition Define a user data set to Unicenter CA-7.

DB.7 JCL Library Maintenance Enter or review JCL statements in PDS orsequential JCL libraries. It can also beused to review AllFusion CA-Librarian orAllFusion CA-Panvalet JCL.


DCONN

DCONN

The DCONN command disconnects high-level indexes previously connected tothe SYSRES catalog with the CONN command or function 8 of UT Menu panel.

Note: This command is not valid for VSAM or ICF catalogs.



DCONN

��──DCONN─ ──,INDX=index ─────────────────────────────────────────��

INDXDefines the name of the index to delete from the SYSRES catalog.


Required: Yes

ExamplesDCONN,INDX=USER

DCONN,INDX=USERNODE

162 Commands Guide

DEALLOC

DEALLOC

The DEALLOC command releases volumes previously allocated with theALLOC command or function 11 of the UT Menu panel. This function isavailable on the UT Menu panel as FUNCTION value 12 or on any other menuor formatted panel as FUNCTION value UT.12.


DEALLOC

��──DEALLOC─ ──,VOL=volume ───────────────────────────────────────��

VOLDefines the volume whose allocation is to be released.


Required: Yes

ExamplesDEALLOC,VOL=DISK�1


DEMAND, DEMANDH

DEMAND, DEMANDH

The DEMAND command forces immediate scheduling of a job into theUnicenter CA-7 request queue. Jobs that do not have definable processingcycles can be scheduled in this manner. Demand scheduling can also be usedto force early execution of jobs that have defined processing cycles or toschedule jobs for the first time, before they have been defined in the UnicenterCA-7 database.

The DEMANDH command indicates that the demanded job is to be placed onhold in the request queue.


DEMAND DEMANDH

��─ ──┬ ┬─DEMAND── ──,JOB=jobname ──┬ ┬────────────────────────── ─────�└ ┘─DEMANDH─ └ ┘──,ARFSET= ──┬ ┬─arfsetname─

└ ┘─��NONE��───

�─ ──┬ ┬────────── ──┬ ┬────────── ──┬ ┬───────────── ──────────────────�└ ┘──,CC=nnnn └ ┘──,CLASS=x └ ┘──,COUNT=nnnn

�─ ──┬ ┬─────────────────── ──┬ ┬────────────────── ──────────────────�└ ┘──,DATE= ──┬ ┬─+nn─── └ ┘──,DEPJOB=jobname2

└ ┘─yyddd─

�─ ──┬ ┬──────────── ──┬ ┬───────────── ──┬ ┬──────────────── ──────────�└ ┘──,DOTM=hhmm └ ┘──,FROMNODE──(1) └ ┘──,INTERVAL=hhmm

�─ ──┬ ┬────────────────────── ──┬ ┬──────────────────── ─────────────�└ ┘──, ──┬ ┬──JCLID=nnn ──── │ │┌ ┐─�1��─

└ ┘──JCLLIB=&x...x └ ┘──,LEADTM= ──┴ ┴─hhmm─

�─ ──┬ ┬──────────────────── ──┬ ┬─────────── ──┬ ┬────────────── ──────�└ ┘──,MAINID= ──┬ ┬─ALL── └ ┘──,PRTY=nnn └ ┘──,RO= ──┬ ┬─EQ─

├ ┤──SYn ─ ├ ┤─LT─├ ┤──/SYn ├ ┤─GT─└ ┘──-SYn ├ ┤─GE─

├ ┤─LE─ ├ ┤─NE─ ├ ┤─#S─ ├ ┤─IG─ └ ┘─�──

�─ ──┬ ┬────────────────── ──┬ ┬──────────────── ──┬ ┬──────────── ─────�│ │┌ ┐─1─── └ ┘──,SET= ──┬ ┬─NDB─ └ ┘──,STOP=hhmm└ ┘──,SCHID= ──┴ ┴─nnn─ ├ ┤─NTR─

└ ┘─SKP─

�─ ──┬ ┬─────────────────── ──┬ ┬─────────────────── ────────────────��└ ┘──,TIME= ──┬ ┬─hhmm── └ ┘──,TYPE= ──┬ ┬─CLOCK─

└ ┘─+hhmm─ ├ ┤─END─── ├ ┤─RES─── └ ┘─START─Note:1 You cannot specify this keyword. See “Usage Notes” on page 171.

164 Commands Guide

DEMAND, DEMANDH

JOBDefines the name of the job being demanded. Demanded jobs are placed inthe request queue and assigned a unique Unicenter CA-7 job number.

ARFSETDefines the ARF set name used for this run of the job. If you specify**NONE**, no ARF processing is performed for this run of the job.

Limits 1 to 8 alphanumeric characters or **NONE**

Required: No

CCDefines, with RO (relational operator), the job-level condition codes used todetermine whether a job executes successfully. If If specified, this overridesthe RO defined for the job in the Unicenter CA-7 database.

Default: DB.1 panel COND-CODE value if job defined to Unicenter CA-7;otherwise 0.

Limits 1 to 4 numeric characters from 0 to 4095

Required: No

CLASSDefines the workload balancing class for resource checking.

Limits: 1 alphanumeric character

Required: No

COUNTDefines the maximum number of times to repeat the job. COUNT is ignoredif INTERVAL is not specified. If both COUNT and STOP are specified, thejob stops repeating when either the COUNT reaches zero or the STOP timeis reached, whichever comes first.

Default: None. The job continues repeating until the STOP time is reached.

Limits: 1 to 4 numeric characters from 0 to 1439. Leading zeros can bediscarded.

Required: No

DATEDefines due-out and submit dates.

Required: No, but if used, DOTM or TIME must be specified.

+nnDefines the number of days after the current date.


yydddDefines the Julian date to run the job.


DEMAND, DEMANDH

DEPJOBDefines a single predecessor job that must complete while demanded job iswaiting.


Required: No

DOTMDefines the due-out time-of-day for the job in hours (hh) and minutes (mm).If omitted, the current time (when the DEMAND was processed) plus thelead time is assumed.

If DOTM is specified on the DEMAND/DEMANDH command and the valuegiven is earlier than the current time, the due-out day is assumed to be thefollowing day.

If DOTM and LEADTM are both omitted, then deadline start time isassumed to be the current time plus the LEADTM.

Default: Current time

Limits: hh= 1 to 2 numeric characters from 0 to 24mm= 2 numeric characters from 00 to 59

Required: No (unless DATE is used, if so, DOTM or TIME must bespecified)

INTERVALIdentifies that the job should be repeated (executed more than once) anddefines the amount of time between each iteration. If INTERVAL isspecified, the TIME and TYPE keywords are required. If both INTERVALand COUNT are specified, the INTERVAL value times the COUNT valuemust total less than 24 hours. For information about how deadline, due-out,and submit times are calculated for repeating jobs, see the Usage Notes.

Default: None. The job is not repeated.

Limits: hh=1 to 2 numeric characters from 0 to 23mm=2 numeric characters from 00 to 59

Required: No

JCLIDDefines the JCL data set that contains the execution JCL to be submitted. Ifused, the value must be a numeric INDEX associated with the wanted JCLdata set (on the JCL statement in the initialization file). If the job is definedin the database, the value must be the same as the value on the DB.1panel. (For more information about the initialization file, see the SystemsProgrammer Guide.) This field or the JCLLIB field is required if the job isnot defined in the database. JCLID and JCLLIB are mutually exclusive.


Required: No, unless job is not defined in database

166 Commands Guide

DEMAND, DEMANDH

JCLLIBDefines the JCL data set that contains the execution JCL to be submitted. Ifused, the value must be a symbolic INDEX associated with the wanted JCLdata set (on the JCL statement in the initialization file). If the job is definedin the database, the value must be the same as the value on the DB.1panel. (For more information about the initialization file, see the SystemsProgrammer Guide.) This field or the JCLID field is required if the job is notdefined in the database. JCLID and JCLLIB are mutually exclusive.

Limits: 2 to 16 alphanumeric characters beginning with ampersand (&)


Note: A dynamic allocation failure on a JCL data set specified by JCLLIBcauses the job to enter the request queue in SKELETON status.

LEADTMDefines the amount of elapsed time required to process the job. Indicatesin hours (hh) and minutes (mm) the elapsed time. The maximum value youcan specify is 2400.

Default: 1 hour

Limits: hh= 1 to 2 numeric characters from 0 to 24mm= 2 numeric characters from 00 to 59

Required: No

MAINIDSpecifies the MAINID, as defined in the initialization file CPU statement, towhich the job is to be redirected. The value specified here overrides thevalue coded on the job definition MAINID field. The name must be one ofthe following:

Required: No

ALLSpecifies all CPUs are acceptable for executing the job.

SYnn defines the CPU to which the job is being redirected. The value of ncan range from 1 to 7.

/SYnn defines a CPU to which the job cannot be submitted. The value of ncan range from 1 to 7.

-SYnn defines a CPU to which the job cannot be submitted. The value of ncan range from 1 to 7.

PRTYDefines the initial workload balancing priority.


Required: No


DEMAND, DEMANDH

ROSpecifies the relational operator of the condition code (CC) or if the steplevel #SCC statements are being used in the job's JCL. If specified, thisoverrides the RO defined for the job in the Unicenter CA-7 database. Thefollowing are the possible values:

EQEqual to

LTLess than

GTGreater than

GEGreater than or equal to

LELess than or equal to

NENot equal to

#SStep condition code tests to be made based on #SCC statement. See#SCC statement discusssion in the Database Maintenance Guide formore information.

IGNo evaluation of the job is done. Unicenter CA-7 always assumes thejob completes successfully, regardless of condition codes, abend codes,or run-time JCL errors.

0No condition code test is to be made.

Default: DB.1 panel RO value if job defined to Unicenter CA-7; otherwise 0

Required: No

SCHIDDefines the schedule ID within the job's total schedule definition to be usedfor this run. If omitted, SCHID=1 is assumed unless the job exists in theUnicenter CA-7 database and has an associated schedule. In this case, thefirst SCHID defined in the schedule member is assumed.

Default: 1


Required: No (See Note)

Note: If the SCHEDULE statement in the initialization file specifiesSCHID=YES, this parameter is required.

168 Commands Guide

DEMAND, DEMANDH

SETSpecifies whether to skip the next scheduled cycle for the job (SKP), todisable triggering (NTR), or to bypass database updating at job completion.

Required: No

SKPSpecifies this run of the job takes the place of the next scheduled run.This has the same effect as entering NXTCYC,SET=SKP. It is reflectedon output from LJOB and LLOCK commands as if NXTCYC,SET=SKPwas used. This parameter is invalid if the job has no schedule.SET=SKP has no impact on repeating jobs that are already in theUnicenter CA-7 queues.

NTRSpecifies normal triggering is disabled only for this run of the job.

NDBAllows a job to bypass all load processing at job completion, but allowsother processing to proceed normally.

Note: Data set triggering is still in effect.

STOPDefines the clock time after which the job should not be repeated. STOP isignored if INTERVAL is not specified. If both COUNT and STOP arespecified, the job stops repeating when either the COUNT reaches zero orthe STOP time is reached, whichever comes first.

If the STOP time is less than the submit time, the stop date is assumed tobe the following day.

Default: 1439 minutes (24 hours minus 1 minute) after the submit time

Limits: hh=1 to 2 numeric characters from 0 to 23mm=2 numeric characters from 00 to 59

Required: No

TIMEDefines a submit time-of-day requirement for the job. If the format is usedwith a +, the submit time is calculated from the current time, adding thespecified number of hours and minutes. If the + is used, the DATE keywordmust be omitted.

Limits: + is optionalhh= 1 to 2 numeric characters from 0 to 23mm= 2 numeric characters from 00 to 59

Required: No (unless DATE is used, if so, DOTM or TIME (hhmm format)must be specified)


DEMAND, DEMANDH

TYPETYPE=RES specifies the job is being scheduled in restart/rerun status.

TYPE=CLOCK, START, or END controls how the submit time requirementis calculated for repeating jobs.

When TYPE=RES the job is put into the request queue with a restartrequirement and is not submitted until the Unicenter CA-7 restart is done.Output networks are scheduled, but input requirements checking isbypassed.

TYPE=CLOCK, START, or END is ignored if INTERVAL is not specified.With TYPE=CLOCK, the interval is added to the previous iteration's submittime requirement to determine the new submit time requirement. WithTYPE=START and END the interval is added to the previous iteration's last(most recent) start and end time, respectively, to determine the new submittime requirement. TYPE is required if INTERVAL is specified.

Limits: RES, CLOCK, START, or END

Required: No

170 Commands Guide

DEMAND, DEMANDH

Usage Notes

Demanding a job into the request queue does not automatically result inimmediate submission for execution. When a DEMAND is issued for a job, thatjob is placed in the request queue where the availability of its inputrequirements is determined. (To request immediate scheduling withoutrequirements checking, see “RUN, RUNH” on page 575.) The same processoccurs when a job is automatically scheduled into the queues.

Using SET=NDB can allow a job not defined to Unicenter CA-7 to be run underthe Unicenter CA-7 control and not be added to the database when itcompletes.

Input workstation networks must be demanded separately from jobs. If ademanded job requires input workstation activity, the network responsible forthat activity must be requested separately using the DMDNW command.

Preprocessing work can be demanded well in advance of the job for which it isa requirement. This can be necessary if the preprocessing activity requiresseveral hours or days of lead time, or if the work is available and is requestedto be done early during a slack period.

Output workstation networks associated with a job are automatically placed inthe postprocess queue when the CPU job is demanded.

Output networks can be demanded separately from their associated CPU jobsby a DMDNW command.

Demanded work is assigned the UID of the operator issuing the DEMANDcommand if the job is not defined in the database.

If TYPE=RES is specified on the DEMAND command, the QM.4-X panel,XRST, or RESTART commands can be used to restart or rerun the job.

FROMNODE is a reserved keyword that is not considered valid input unlessgenerated by Unicenter CA-7 internally. This keyword can not be coded ononline, batch, or trailer terminal transactions. It is reserved to indicate that theDEMAND is issued in response to a scheduling request from an XPS client.


DEMAND, DEMANDH

Repeating Jobs: A job can be brought into the request queue using theDEMAND command and executed more than once. Each iteration mustsuccessfully complete (or be forced complete) before the next iteration is addedto the request queue.

The following keywords are used with repeating jobs:

As each iteration successfully completes (or is forced complete), UnicenterCA-7 adds the INTERVAL to the submit time requirement, start time, or endtime based on the TYPE setting. This value becomes the next iteration's submittime requirement.

The new submit time requirement is then compared to the STOP time. If eitherthe new submit time requirement or the current time are greater than the STOPtime, the job is not repeated.

The new job's due-out time is calculated as the new submit time requirementplus the difference between the original due-out time and the original submittime requirement.

The new job's deadline time is calculated as the new due-out time minus theoriginal lead time (LEADTM).

Keyword Explanation

INTERVAL Required. Defines the amount of time between eachiteration of the job.

TYPE Required. Specifies how the submit time requirement ofeach iteration is calculated—by adding the INTERVAL tothe previous iteration's submit time requirement(CLOCK), START, or END time.

COUNT Optional. Defines the maximum number of times the jobwill be repeated.

STOP Optional. Defines the clock time after which the job is notto be repeated. If not specified, the stop time is 1439minutes (24 hours minus 1 minute) after the submit timerequirement of the first iteration.

TIME Required. Defines the submit time requirement of the firstiteration.

LEADTM Optional. Defines the amount of time required to processthe job. If not specified, 0100 (1 hour) is used.

DOTM Optional. Defines the due-out time (expected completiontime) of the first iteration. If not specified, the current timeplus the LEADTM is used.

172 Commands Guide

DEMAND, DEMANDH

The start and end times of the job are local to the system where the jobexecuted, not local to the system where Unicenter CA-7 is executing.TYPE=START and END should be used with care for NJE and cross-platformjobs.

ExamplesDEMANDH,JOB=CA7JOB1

DEMAND,JOB=CA7JOB1,DOTM=16��,LEADTM=��45

DEMAND,JOB=CA7JOB3,JCLID=7,SCHID=14

DEMAND,JOB=CA7JOB2,TYPE=RES

DEMAND,JOB=CA7JOB4,SET=NTR


DIRECT

DIRECT

The DIRECT command alters any defined MAINID for a job in the request orready queue before the job is submitted for processing.


DIRECT

��──DIRECT─ ──,JOB=jobnumber ──,MAINID= ──┬ ┬─ALL── ─────────────────��├ ┤──SYn ─└ ┘──/SYn

JOBDefines the unique Unicenter CA-7 job number of the job whose MAINID isto be changed. The job must be in the request or ready queue and notalready submitted.


Required: Yes

MAINIDSpecifies the MAINID, as defined in the initialization file CPU statement, towhich the job is to be redirected. The name must be one of the following:

Required: Yes




174 Commands Guide

DIRECT

Usage Notes

Changing a MAINID with the DIRECT command does not cause a change tothe MAINID specification as defined for the job in the database.

Use of a MAINID has no effect on the routing of jobs in a shared spoolenvironment unless a user-supplied submit exit inserts appropriate JES controlstatements.

You can use “QM.3-X CPU Job Attributes” on page 523 as an alternative forthis purpose.

If a job has already been submitted and the DIRECT command is to be usedbecause a CPU is down, the job must be requeued before this command takeseffect. See “REQUEUE” on page 551 and “XQ, XQJ, XQN, and XQM” onpage 655.

ExamplesDIRECT,JOB=15,MAINID=SY3

DIRECT,JOB=73,MAINID=/SY1


DLTX

DLTX

The DLTX command deletes inactive indexes in the catalog.

Note: This command is not valid for VSAM or ICF catalogs.



DLTX

��──DLTX─ ──,INDX=index ──┬ ┬────────────── ────────────────────────��└ ┘──,CVOL=volume

INDXDefines the fully qualified name of the index to be removed.


Required: Yes

CVOLDefines the volume containing the catalog. If this field is omitted, the searchbegins with the system residence volume, and a standard catalog search isemployed.


Required: No

Usage Notes

Unicenter CA-7 attempts to delete as many index levels as possible. Onerequest could result in the removal of multiple index levels.

ExamplesDLTX,INDX=USER.LEV1.LEV2.LEV3

DLTX,INDX=USER.LEV1.LEV2,CVOL=ALTCAT

DLTX,INDX=USER.GDG.FILE1

176 Commands Guide

DMDNW

DMDNW

The DMDNW command schedules on-request input and output networks intothe queues.


DMDNW

��──DMDNW─ ──,NW=network ──┬ ┬──────────── ──┬ ┬─────────── ───────────�└ ┘──,DESC=desc └ ┘──,JOB=name

�─ ──┬ ┬──────────────────── ──┬ ┬────────────────── ─────────────────� │ │┌ ┐─�1��─ │ │┌ ┐─1───

└ ┘──,LEADTM= ──┴ ┴─hhmm─ └ ┘──,SCHID= ──┴ ┴─nnn─

�─ ──┬ ┬────────────── ────────────────────────────────────────────��└ ┘──,SUBID=subid

NWDefines the network to be demanded. Value must be the network nameused when the network was defined in the database.


Required: Yes

DESCDefines an optional description. This value is displayed on the QM.6, QM.7,LPRE, and LPOST panels.


Required: No

JOBDefines a name to assign to the network.

Default: DMD#nnnn, if neither SUBID nor JOB is specified (where nnnn isthe Unicenter CA-7 number).


Required: No

LEADTMDefines an elapsed (lead) time for calculating deadline start time-of-day ofthe first station in the network.

Default: 1 hour

Limits: hh= 1 to 2 numeric characters from 0 to 99mm= 1 to 2 numeric characters from 0 to 59

Required: No


DMDNW

SCHIDDefines which schedule ID of the network's scheduling definition is to beused.

Default: 1


Required: No

SUBIDDefines an optional ID to be used to further identify the network when itenters the queue.


Required: No

Usage Notes

When a network is requested, Unicenter CA-7 determines whether the networkshould be placed in the preprocess or postprocess queue based on thedefinition of the network in the database.

All networks can be demanded independently from CPU jobs.

Even though networks can be demanded with this command, all networks musthave a schedule.

The DMDNW command must be used, instead of the CPU job DEMANDcommand for input networks. It can be used to demand output networksindependently of their CPU jobs.

The RUNNW command can be used instead of DMDNW to preventrequirement posting.

ExamplesDMDNW,NW=RECPTS

DMDNW,NW=REPTS,SUBID=PAYR1234,DESC=PAYDATA

DMDNW,NW=REPTS,SCHID=27,LEADTM=�125

178 Commands Guide

DMPCAT

DMPCAT

The DMPCAT command displays the first block of catalog information for aspecified data set. This function is available on the UT Menu panel asFUNCTION value 18 or on any other menu or formatted panel as FUNCTIONvalue UT.18.


DMPCAT

��──DMPCAT─ ──,DSN=dsname ──┬ ┬────────────── ──────────────────────��└ ┘──,CVOL=volume

DSNDefines the fully qualified name of the data set whose first catalog block isto be displayed.


Required: Yes

CVOLDefines the volume where the catalog search is to begin. If omitted, thecatalog is searched to determine the volume.


Required: No

ExamplesDMPCAT,DSN=CA7.LOADLIB

DMPCAT,DSN=CA7.COMDS,CVOL=LIB1�3


DMPDSCB

DMPDSCB

The DMPDSCB command displays the Format 1 data set control block (DSCB)for a specific data set. This function is available on the UT Menu panel asFUNCTION value 13 or on any other menu or formatted panel as FUNCTIONvalue UT.13.


DMPDSCB

��──DMPDSCB─ ──,DSN=dsname ──┬ ┬───────────── ──────────────────────��└ ┘──,VOL=volume

DSNDefines the fully qualified name of the data set whose data set control block(DSCB) is to be displayed.


Required: Yes

VOLDefines the volume on which the data set resides. If omitted, the catalog issearched to determine the volume.


Required: No

ExamplesDMPDSCB,DSN=CA7.LOADLIB,VOL=LIB1�2

DMPDSCB,DSN=CA7.COMDS

180 Commands Guide

DMPDSN

DMPDSN

The DMPDSN command displays physical records of a given data set ordirectory. It supports DSORG of PS, DA, or PO and RECFM of F, V, or U. Thisfunction is available on the UT Menu panel as FUNCTION value 17 or on anyother menu or formatted panel as FUNCTION value UT.17.


DMPDSN

��──DMPDSN─ ──,DSN=dsname ──┬ ┬───────────── ──┬ ┬───────────────── ───�└ ┘──,MEM=member │ │┌ ┐─1────

└ ┘──,REC= ──┴ ┴─nnnn─

�─ ──┬ ┬───────────── ─────────────────────────────────────────────��└ ┘──,VOL=volume



Required: Yes

MEMDefines a PDS member to display. This should be specified for partitioneddata sets (PDSs) only. If omitted for a PDS, the directory is displayed.


Required: No

RECDefines a relative physical record is to be displayed.

Default: 1 - first record in data set


Required: No

VOLDefines the volume on which the data set resides. If omitted, the catalog issearched to determine the volume.


Required: No


DMPDSN

ExamplesDMPDSN,DSN=CA7.LOADLIB,MEM=SASSUTLX

DMPDSN,DSN=CA7.COMMDS,VOL=LIB1�2,REC=3

DMPDSN,DSN=CA7.LOADLIB,REC=5

182 Commands Guide

FALL

FALL

The FALL command provides forecasting for CPU jobs and networkworkstations. Only the database is used for this forecast.


FALL

��──FALL─ ──,FROM=(mmddyy,hhmm) ──, ──┬ ┬──TO=(mmddyy,hhmm) ──────────�└ ┘──SPAN=hhhh ───────

�─ ──┬ ┬─────────────────── ──┬ ┬────────────────────────────── ──────�└ ┘──,DRMODE= ──┬ ┬─YES─ └ ┘──,DRCLASS=(class1,...,class8)

└ ┘─NO──

�─ ──┬ ┬──────────────────────────────────── ───────────────────────� │ │┌ ┐─�───────────────────────

└ ┘──,JOB= ──┼ ┼─jobname───────────────── ├ ┤─jobname�────────────────

└ ┘──(jobname1,...jobname1�)

�─ ──┬ ┬───────────────────── ──┬ ┬────────────────── ────────────────� │ │┌ ┐─�───── │ │┌ ┐─ALL──

└ ┘──,JOBNET= ──┼ ┼─name── └ ┘──,LIST= ──┼ ┼─#JOB─ └ ┘─name�─ ├ ┤─CPU── ├ ┤─GRPH─ ├ ┤─JOB── └ ┘─STN──

�─ ──┬ ┬──────────────── ──┬ ┬───────────── ──────────────────────────�│ │┌ ┐─1��─ └ ┘──,MAINID= SYn└ ┘──,LVL= ──┴ ┴─nnn─

�─ ──┬ ┬──────────────────── ──┬ ┬──────────── ───────────────────────�│ │┌ ┐─�──────── └ ┘──,RINT=hhmm└ ┘──,NW= ──┼ ┼─network──

└ ┘─network�─

�─ ──┬ ┬────────────────── ──┬ ┬───────────────── ────────────────────� │ │┌ ┐─1─── │ │┌ ┐─DLDT─

└ ┘──,SCHID= ──┴ ┴─nnn─ └ ┘──,SEQ= ──┼ ┼─DODT─ └ ┘─JOB──

�─ ──┬ ┬──────────────────────────────────── ───────────────────────� │ │┌ ┐─�───────────────────────

└ ┘──,STN= ──┼ ┼─station───────────────── ├ ┤─station�────────────────

└ ┘──(station1,...station1�)

�─ ──┬ ┬──────────────────── ──┬ ┬──────────────────── ───────────────� │ │┌ ┐─�─────── │ │┌ ┐─J──────

└ ┘──,SYS= ──┼ ┼─system── └ ┘──,TRIG= ──┼ ┼─D────── └ ┘─system�─ ├ ┤──┬ ┬─JD─ │ │└ ┘─DJ─ └ ┘─N──────

�─ ──┬ ┬──────────────────── ──────────────────────────────────────�� │ │┌ ┐─ACTUAL─

└ ┘──,TYPE= ──┴ ┴─ALL────


FALL

You can find more information about any parameters not listed here in“Common Forecast Parameter Descriptions” on page 24.

FROMDefines the beginning date and time for the forecast time interval. FROM isrequired. For more information, see “Forecast Interval” on page 30.

TODefines the ending date and time for the time interval to be forecast. EitherTO or SPAN is required. If TO is specified, SPAN must be omitted. Formore information, see “Forecast Interval” on page 30.

SPANDefines the length of the time interval to be forecast. This value is added tothe FROM date and time-of-day to determine the ending date and time ofthe forecast time interval.

Limits: 1 to 4 numeric characters specified as hhhh where the minimumvalue is 1 hour and maximum value is 8784 hours

Required: Yes, unless TO is used

LISTSpecifies the options for resource forecasting.

Default: ALL

Required: No

ALLProduces all of the following choices.

#JOBGraphically displays number of jobs running during each time intervalspecified.

CPUGraphically displays percent of CPU usage during each time intervalspecified.

GRPHGraphically displays number of jobs running, percent of CPU used, andtape usage during each time interval specified.

JOBProduces resource forecast report for CPU workload.

STNProduces resource forecast report.

Note: You must omit LIST if RINT is not specified.

SCHIDDefines the schedule ID as a value 1-255 to be used in the forecast.Required only if the job being forecasted does not have a schedule.

184 Commands Guide

FALL

ExamplesFALL,FROM=(�3�5�5,�8��),TO=(�316,17),TYPE=ALL

FALL,FROM=�3,TO=�3,SYS=PACKBACK

FALL,FROM=(�3,�8),SPAN=8,SEQ=JOB

FALL,FROM=(�3,�8),SPAN=8,JOB=G4�1�,SYS=ACCTPY,NW=RPTPREP,STN=(PRNT,BURST,DISTR)

FALL,FROM=(1��2),SPAN=24,RINT=�1��,LIST=GRPH

NOEX in the RQMT column on the output identifies nonexecutable jobs (forexample, EXEC:N on the DB.1 panel).

JCLO in the RQMT column on the output identifies jobs requiring JCL overrides(for example, JCL-OVRD:Y on the DB.1 panel).

FALL Panel - Forecast for CA-7 Jobs and Stations (Summary)

� � FALL,FROM=�3�6�5,TO=�3�6�5

FALL DATE �2-27-�5 PAGE ��1FORECAST FOR CA-7 JOBS AND STATIONS

PERIOD : �3-�6-�5 AT �� HRS TO �3-�6-�5 AT 2359 HRS

JOBS(S) : ALL

SYSTEMS : ALL JOBNET(S) : ALL

STATIONS(S) : ALL

NETWORK(S) : ALL

OPTIONS : JOB-TRIGGERED JOBS INCLUDEDDSN-TRIGGERED JOBS NOT INCLUDEDDETAILED STATION RECORDS PROVIDED

HIGHEST JOB DATE AND TIME : �5�65/2359HIGHEST JOB NAME : PATOM

HIGHEST STATION DATE AND TIME : �5�66/�33�HIGHEST STATION NAME : BINS

� �


FALL

FALL Panel - Forecast for CA-7 Jobs

� � FALL,FROM=�3�6�5,TO=�3�6�5

FALL DATE �2-27-�5 PAGE ��2FORECAST FOR CA-7 JOBS


START DTTM END DTTM JOB SYS SCHED# SID TRIGGERING JOB/DSN RQMT �5�65/�759 �5�65/�8�� DUCCXX�1 TESTNTWK SJ��1 ��1 �5�65/�759 �5�65/�8�� DUCCXX�8 TESTNTWK SJ��2 ��1 �5�65/�9�� 5�65/�9�� JCO15�D CO SJ��12 ��1 NOEX �5�65/��5� �5�65/��5� JCO62�D CO LEV��1 ��1 JCO15�D �5�65/11�� 5�65/11�� PAT1 CHICAGO SJ��16 ��2 JCLO �5�65/1159 �5�65/12�� DUCCXX�1 TESTNTWK SJ��1 ��2 �5�65/1159 �5�65/12�� DUCCXX�8 TESTNTWK SJ��2 ��2 �5�65/12�� 5�65/12�� JCO15�D CO SJ��12 ��2 NOEX �5�65/12�� 5�65/12�� PATM1 SJ��14 ��1 �5�65/121� �5�65/121� JCO5�1D CO LEV��1 ��2 JCO15�D �5�65/1559 �5�65/16�� DUCCXX�1 TESTNTWK SJ��1 ��3 �5�65/1559 �5�65/16�� DUCCXX�8 TESTNTWK SJ��2 ��3 �5�65/1959 �5�65/2�� DUCCXX�1 TESTNTWK SJ��1 ��4 �5�65/1959 �5�65/2�� DUCCXX�8 TESTNTWK SJ��2 ��4 �5�65/2�� 5�65/2�� ALLNET1 DEMO SJ��5 ��1 JCLO �5�65/2359 �5�65/2359 PATOM PAT SJ��15 ��1� �

FALL Panel - Forecast for CA-7 Stations

� � FALL,FROM=�3�6�5,TO=�3�6�5

FALL DATE �2-27-�5 PAGE ��3FORECAST FOR CA-7 STATIONS


START DTTM END DTTM STN #/NAME NETWORK SUBID SCHED# SID CONNJOB/S �5�65/�9�� 5�65/11�� 1 BURST TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��5 �5�65/12�� 5�65/13�� 2 TRIM TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��1 �5�65/13�� 5�65/15�� 1 BURST TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��2 �5�65/15�� 5�65/153� 3 BINS TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��1 �5�65/16�� 5�65/17�� 2 TRIM TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��2 �5�65/17�� 5�65/19�� 1 BURST TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��3 �5�65/19�� 5�65/193� 3 BINS TESTONWK RPT12�5 SI��1 ��1 �5�65/2�� 5�65/21�� 2 TRIM TESTONWK RPT12�5 SI��1 ��1 �5�65/21�� 5�65/23�� 1 BURST TESTONWK RPT12�5 SI��1 ��1 �5�65/23�� 5�65/233� 3 BINS TESTONWK RPT12�5 SI��1 ��1 �5�66/�� 5�66/�1�� 2 TRIM TESTONWK RPT12�5 SI��1 ��1 �5�66/�3�� 5�66/�33� 3 BINS TESTONWK RPT12�5 SI��1 ��1

� �

186 Commands Guide

FIND

FIND

The FIND command searches DASD volumes for copies of a given data setname. Volume serial number and creation date are displayed for each DASDvolume on which the data set is found. This function is available on the UTMenu panel as FUNCTION value 10 or on any other menu or formatted panelas FUNCTION value UT.10.


FIND

��──FIND─ ──,DSN=dsname ──,VOL= ──┬ ┬─ALL──────────── ───────────────�� ├ ┤─volume───────── │ │┌ ┐─,────── └ ┘──( ───� ┴─volume─ )



Required: Yes

VOLDefines the volumes to be searched.

Required: Yes

ALLSpecifies all volumes available to Unicenter CA-7. SPACE,VOL=ALLcan be used to determine which volumes are available to UnicenterCA-7 by way of:

■ //U7nnnnnn DD statements in the JCL

■ Function 11 on the Utilities Menu panel

■ Top line ALLOC command

volumeDefines a single volume.


(volume,...,volume)Defines up to five volumes enclosed in parentheses and separated bycommas.


FIND

ExamplesFIND,DSN=SYSCTLG,VOL=ALL

FIND,DSN=USER.FILE1,VOL=(VOLM�1,VOLM�2,VOLM�3)

FIND,DSN=USER.FILE2,VOL=VOLM�2

Unicenter CA-7 displays the volser and creation date for each DASD volumewhere the data set is found.

188 Commands Guide

FJOB

FJOB

The FJOB command provides forecasting for CPU jobs. It includes an option toinclude output workstation networks in the forecast. Only the database is usedfor this forecast.


FJOB

��──FJOB─ ──,FROM=(mmddyy,hhmm) ──, ──┬ ┬──TO=(mmddyy,hhmm) ──────────�└ ┘──SPAN=hhhh ───────


└ ┘─NO──

�─ ──┬ ┬──────────────────────────────────── ───────────────────────� │ │┌ ┐─�───────────────────────



�─ ──┬ ┬───────────────────── ──┬ ┬────────────────── ────────────────� │ │┌ ┐─�───── │ │┌ ┐─ALL──

└ ┘──,JOBNET= ──┼ ┼─name── └ ┘──,LIST= ──┼ ┼─#JOB─ └ ┘─name�─ ├ ┤─CPU── ├ ┤─GRPH─ ├ ┤─JOB── ├ ┤─W──── ├ ┤─WP─── ├ ┤─WPS── └ ┘─WS───

�─ ──┬ ┬──────────────── ──┬ ┬───────────── ──┬ ┬──────────────── ──────�│ │┌ ┐─1��─ └ ┘──,MAINID=SYn └ ┘──,NWOPT= ──┬ ┬─N─└ ┘──,LVL= ──┴ ┴─nnn─ └ ┘─S─

�─ ──┬ ┬──────────── ──┬ ┬────────────────── ─────────────────────────�└ ┘──,RINT=hhmm │ │┌ ┐─�───

└ ┘──,SCHID= ──┴ ┴─nnn─

�─ ──┬ ┬─────────────────────────── ──┬ ┬───────────────── ───────────�└ ┘──,SEG=(segment,subsegment) │ │┌ ┐─DLDT─

└ ┘──,SEQ= ──┼ ┼─DODT─ └ ┘─JOB──

�─ ──┬ ┬──────────────────── ──┬ ┬──────────────────── ───────────────� │ │┌ ┐─�─────── │ │┌ ┐─J──────


�─ ──┬ ┬──────────────────── ──────────────────────────────────────�� │ │┌ ┐─ACTUAL─

└ ┘──,TYPE= ──┴ ┴─ALL────


FJOB


FROMDefines the beginning date and time for the time interval to be forecast.FROM is required. For more information, see “Forecast Interval” onpage 30.





LISTSpecifies the options for either resource forecasting or the worksheet. Whenused for resource forecasting, LIST must be omitted if RINT is notspecified.

Default: ALL

Required: No


#JOBGraphically displays the number of jobs running during each timeinterval specified.

CPUGraphically displays the percent of CPU usage during each time intervalspecified.

GRPHGraphically displays the number of jobs running, percent of CPU usedand tape usage during each time interval specified.


For worksheet requests, RINT and NWOPT must be omitted and LISTcan have one of the following values:

190 Commands Guide

FJOB

WProduces a schedule worksheet, without prose from the forecast report.

WPProduces prose information with the specified forecast worksheet.

WPSSame as WP except skip to top of page for each job.

WSSame as W except skip to top of page for each job.

Usage Notes

You can forecast jobs without RESOLVed schedules by requesting theindividual job. The FROM date and time are used as the start time for the jobunless omitted, in which case current date and time are used.


FJOB

ExamplesFJOB,FROM=(�3�5�5,�8��),TO=(�316,17)

FJOB,FROM=�2,TO=�3,SYS=PAYROLL,TRIG=DJ

FJOB,FROM=�3,SPAN=24,SEQ=JOB,JOB=G4�1�

FJOB,FROM=(�3,�8),SPAN=8,JOB=(JOB1,JOB2,JOB3)

FJOB,FROM=�3�2,SPAN=24

FJOB,FROM=�2,SPAN=24

FJOB,FROM=(�915,�8��),SPAN=48,SYS=PAYROLL,RINT=��3�,LIST=CPU

FJOB,FROM=(�314,1�3�),SPAN=24,LIST=WPS,TYPE=ALL

NOEX in the RQMT column on the output identifies nonexecutable jobs (forexample, EXEC:N on the DB.1 panel). These jobs have both the start and endtimes set to the DOTM of the job.

JCLO in the RQMT column on the output identifies jobs that require JCLoverrides (for example, JCL-OVRD:Y on the DB.1 panel).

Jobs for which the NXTCYC,SET=OFF or NXTCYC,SET=SKP command hasbeen issued do not appear on the forecast unless TYPE=ALL is specified.

The asterisk preceding the job name indicates the time had to be adjusted.

FJOB Panel - Forecast for CA-7 Jobs (Summary): Jobs with repeatinformation scheduled to run during the forecast period are marked with"(REPEATING JOB)" in the TRIGGERING JOB/DSN column. Subsequentiterations of these jobs are treated as if they were triggered by the previousiteration but will have a RPT (repeat) number instead of a LEV (level) numberin the SCHED# column.

� � FJOB,FROM=�3�6�5,TO=�3�6�5

FJOB DATE �2-27-�5 PAGE ��1FORECAST FOR CA-7 JOBS


JOB(S) : ALL


OPTIONS : JOB-TRIGGERED JOBS INCLUDEDDSN-TRIGGERED JOBS NOT INCLUDEDCONNECTED OUTPUT NETWORKS NOT INCLUDED

HIGHEST JOB DATE AND TIME : �5�65/2��HIGHEST JOB NAME : DUCCXX�1

� �

192 Commands Guide

FJOB

� � FJOB,FROM=�3�6�5,TO=�3�6�5

FJOB DATE �2-27-�5 PAGE ��2FORECAST FOR CA-7 JOBS


START DTTM END DTTM JOB SYS SCHED# SID TRIGGERING JOB/DSN RQMT�5�65/�759 �5�65/�8�� DUCCXX�1 TESTNTWK SJ��1 ��1�5�65/1159 �5�65/12�� DUCCXX�1 TESTNTWK SJ��1 ��2�5�65/16�� 5�65/16�� DUCCXX�2 TESTNTWK SJ��2 ��1 NOEX�5�65/1959 �5�65/2�� DUCCXX�3 TESTNTWK SJ��3 ��1 JCLO

� �

FJOB Panel - Forecast for CA-7 Jobs and Stations (Summary)

� � FJOB,FROM=�3�6�5,TO=�3�6�5,NWOPT=S

FJOB DATE �2-27-�5 PAGE ��1FORECAST FOR CA-7 JOBS AND STATIONS


JOB(S) : ALL


STATION(S) : ALL

NETWORK(S) : ALL


HIGHEST JOB DATE AND TIME : �5�65/2��HIGHEST JOB NAME : DUCCXX�1

HIGHEST STATION DATE AND TIME : �5�66/�33�HIGHEST STATION NAME : TESTONWK

� �

FJOB Panel - Forecast for CA-7 Stations

� � FJOB,FROM=�3�6�5,TO=�3�6�5,NWOPT=S

FJOB DATE �2-27-�5 PAGE ��2FORECAST FOR CA-7 STATIONS


START DTTM END DTTM STN #/NAME NETWORK SUBID SCHED# SID CONNJOB/SID�5�65/�9�� 5�65/153� 1 PRINT TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��1�5�65/13�� 5�65/193� 2 BURST TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��2�5�65/17�� 5�65/233� 3 DELIVER TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��3�5�65/21�� 5�66/�33� 4 MAIL TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��4

SFC1-�� REQUEST COMPLETED AT 18:11:23 on �5.�58

� �


FJOB

FJOB Panel - Worksheet

� � FJOB,FROM=�3�6�5,TO=�3�6�5,LIST=WP DATE �2-27-�5 PAGE ��2

JOB=DUCCXX�1 COMPLETED _________________

SCHEDULE: LATEST STRT=�5�65/�759 SCHD MBR=SJ��1 DUEOUT TIME=�5�65/�8�� SCHED ID=��1 SUBMIT TIME=�5�65/�� ALL-CYCL-OFF=YES




�� JOB EXECUTION REQUIREMENTS ��

________ EXTERNAL USR=THIS IS THE FIRST JOB IN THE TEST________ EXTERNAL USR=SYSTEM, IF YOU WISH TO BEGIN YOU________ EXTERNAL USR=SATISFY THESE REQUIREMENTS!

� �

FJOB Panel - Forecast Using TYPE=ALL

� �FJOB,FROM=�33��5,TO=�33��5,TRIG=J,JOB=WHIDO95�,TYPE=ALLFJOB DATE 12-13-�5 PAGE ��1

FORECAST FOR CA-7 JOBSPERIOD : �3-3�-�5 AT �� HRS TO �3-3�-�5 AT 2359 HRS

START DTTM END DTTM JOB SYS SCHED# SID TRIGGERING JOB/DSN RQMT

�5�89/11�7 �5�89/12�� WHIDO953 SJ��26 ��1 OFF�5�89/11�8 �5�89/12�� WHIDO952 SJ��25 ��1 SKP�5�89/11�9 �5�89/12�� WHIDO951 SJ��2 ��1 NOEX�5�9�/11�7 �5�9�/12�� WHIDO531 LEV��1 ��1 WHIDO953 OFF�5�9�/11�8 �5�9�/12�� WHIDO521 LEV��1 ��1 WHIDO952 SKP�5�9�/11�9 �5�9�/12�� WHIDO511 LEV��1 ��1 WHIDO951 NOEX

SFC1-�� REQUEST COMPLETED AT 14:32:26 on �5.347� �

An asterisk (*) in front of a job name indicates the START DTTM has beenadjusted to allow for triggered due-out time conflicts. This usually indicatesmultiple jobs in a trigger stream have the same DOTM value.

For jobs flagged with NXTCYC,SET=OFF or NXTCYC,SET=SKP the RQMTfield shows SKP or OFF. These jobs appear only when TYPE=ALL isrequested.

194 Commands Guide

FLOWD

FLOWD

The FLOWD command manually deletes active Critical Path Management(CPM) flow elements.


FLOWD

��──FLOWD─ ──,FLOW=flowname ──┬ ┬───────────── ──┬ ┬─────────── ───────�└ ┘──,DATE=yyddd └ ┘──,JOBCNT=�

�─ ──┬ ┬──────────── ──────────────────────────────────────────────��└ ┘──,TIME=hhmm

FLOWDefines the fully qualified name of the CPM flow to be deleted. To delete allactive flows, specify *ALL*. If there are multiple occurrences of the flowactive, all of them will be deleted unless the DATE and TIME keywords areused to qualify the selection.


Required: Yes

DATEDefines a specific flow date. If the same flow has multiple occurrences, youcan use the DATE (and optionally TIME) keywords to select which flows todelete. The value is matched against the flow start date (see “FLOWL” onpage 197).

Limits: 5 numeric digits (yyddd)

Required: No

JOBCNTIf used, the only valid form of this option is JOBCNT=0.

Specifies to delete only flows that no longer have any jobs attached tothem. These flows can become stranded if a job in the critical path of theflow is canceled in Unicenter CA-7.

Default: None

Limits: 0

Required: No


FLOWD

TIMEDefines a specific flow time. If the same flow has multiple occurrences ofthe same flow, you can use the DATE (and optionally TIME) keywords toselect which flows to delete. The value is matched against the flow starttime (see “FLOWL” on page 197).

Limits: 4 numeric digits (hhmm)

Required: No

Usage Notes

Note: For information about the Critical Path Monitor (CPM) facility, see theInterfaces Guide.

Use the FLOWL command to display active flows.

If a flow is deleted by the FLOWD command, no signal is sent to UnicenterCA-OPS/MVS. You may need to manually delete the flow there as well.

To delete all stranded CPM flows (flows with no jobs attached), issue thecommand:

FLOWD,FLOW=�ALL�,JOBCNT=�

196 Commands Guide

FLOWL

FLOWL

The FLOWL command displays information about active Critical PathManagement (CPM) flows. For information about the CPM facility, see theInterfaces Guide.


FLOWL

��──FLOWL─ ──┬ ┬─────────────────────── ──┬ ┬────────────────── ─────��│ │┌ ┐─�───────── └ ┘──,LIST= ──┬ ┬─FLOW─└ ┘──,FLOW= ──┼ ┼─flowname── └ ┘─JOBS─

└ ┘─flowname�─

FLOWDefines the fully or partially qualified flow name for which information is tobe displayed.

Default: * (all flows)


Required: No

LISTSpecifies the amount of flow information to be displayed.

Default: FLOW

Required: No

FLOWSpecifies to display a single line of information for each active flowselected.

JOBSSpecifies to display a line of information for each active flow selectedand also lists the Unicenter CA-7 job numbers of the jobs that arecurrently connected to each flow.


FLOWL

Examples

� � FLOWL,LIST=JOBS PAGE ��1

FLOWNAME START-DATE/TIME START-JOB/SID/NUM END-JOB/SID SLA-TARGET JOBCNT

FLOWA 99�98/1�:19:33 JOBA /��1/��1 JOBX /��1 99�98/23:3� 1 -------------------------- CONNECTED JOBS --------------------- ��3

SLIL-�� REQUEST COMPLETED AT hh:mm:ss ON yy.ddd� �

FLOWNAMEIdentifies the name of the active flow.

START-DATE/TIMEIdentifies the date (yyddd) and time (hh:mm:ss) when the active flowelement was created.

START-JOB/SID/NUMIdentifies the job name, schedule ID, and Unicenter CA-7 job number of thejob that caused the active flow element to be created.

END-JOB/SIDIdentifies the job name and schedule ID of the job that will be consideredthe end of the Critical Path represented by the flow.

SLA-TARGETIdentifies the target completion date and time for the flow (service levelagreement target).

JOBCNTIdentifies the number of Unicenter CA-7 jobs currently connected to thisflow.

CONNECTED JOBSIdentifies the job numbers of the Unicenter CA-7 jobs currently connected tothis flow (only displayed if LIST=JOBS).

198 Commands Guide

FPOST

FPOST

The FPOST command provides forecasting for output network workstations.Only the database is used for this forecast.


FPOST

��──FPOST─ ──,FROM=(mmddyy,hhmm) ──, ──┬ ┬──TO=(mmddyy,hhmm) ─────────�└ ┘──SPAN=hhhh ───────



�─ ──┬ ┬───────────────── ──────────────────────────────────────────� │ │┌ ┐─DLDT─

└ ┘──,SEQ= ──┼ ┼─DODT─ └ ┘─STN──

�─ ──┬ ┬──────────────────────────────────── ──────────────────────�� │ │┌ ┐─�───────────────────────










FPOST

ExamplesFPOST,FROM=(�3�5�5,�8��),TO=(�316,17)

FPOST,FROM=�3,TO=�3,STN=KEYPUNCH

FPOST,FROM=(�3,17),SPAN=8,NW=RPT,STN=(BURST,DISTR)

FPOST,FROM=�2,SPAN=24,RINT=��45

FPOST Panel - Forecast for CA-7 Stations (Output Networks - Summary)

� � FPOST,FROM=�3�6�5,TO=�3�6�5

FPOST DATE �3-�6-�5 PAGE ��1FORECAST FOR CA-7 STATIONS


STATIONS(S) : ALL

NETWORK(S) : ALL



� �

FPOST Panel - Forecast for CA-7 Stations (Output Networks)

� � FPOST,FROM=�3�6�5,TO=�3�6�5

FPOST DATE �2-27-�5 PAGE ��1

FORECAST FOR CA-7 STATIONSPERIOD : �3-�6-�5 AT �� HRS TO �3-�6-�5 AT 2359 HRS

START DTTM END DTTM STN #/NAME NETWORK SUBID SCHED# SID CONNJOB/SID �5�65/�9�� 5�65/11�� 1 BURST TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��1 �5�65/12�� 5�65/13�� 2 TRIM TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��1 �5�65/13�� 5�65/15�� 1 BURST TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��2 �5�65/15�� 5�65/153� 3 BINS TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��1 �5�65/16�� 5�65/17�� 2 TRIM TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��2 �5�65/17�� 5�65/19�� 1 BURST TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��3 �5�65/19�� 5�65/193� 3 BINS TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��2 �5�65/2�� 5�65/21�� 2 TRIM TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��3 �5�65/21�� 5�65/23�� 1 BURST TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��4 �5�65/23�� 5�65/233� 3 BINS TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��3 �5�66/�� 5�66/�1�� 2 TRIM TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��4 �5�66/�3�� 5�66/�33� 3 BINS TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��4

SFC1-�� REQUEST COMPLETED AT 18:11:29 on �5.�58� �

200 Commands Guide

FPRE

FPRE

The FPRE command provides forecasting for input network workstations. Onlythe database is used for this forecast.


FPRE

��──FPRE─ ──,FROM=(mmddyy,hhmm) ──, ──┬ ┬──TO=(mmddyy,hhmm) ──────────�└ ┘──SPAN=hhhh ───────



�─ ──┬ ┬───────────────── ──────────────────────────────────────────� │ │┌ ┐─DLDT─

└ ┘──,SEQ= ──┼ ┼─DODT─ └ ┘─STN──

�─ ──┬ ┬──────────────────────────────────── ──────────────────────�� │ │┌ ┐─�───────────────────────










FPRE

ExamplesFPRE,FROM=(�3�5�5,�8��),TO=(�316,17)

FPRE,FROM=�3,TO=�3,STN=KEYPUNCH

FPRE,FROM=(�3,17),SPAN=24,NW=DATAPREP,SEQ=STN

FPRE,FROM=(�3,�8��),SPAN=8,STN=(KEYPUNCH,VERIFY)

FPRE,FROM=(�915,�8��),SPAN=8,RINT=�2��,

FPRE Panel - Preprocessing (Summary)

� � FPRE,FROM=�3�6�5,TO=�3�6�5,SPAN=12 FPRE DATE �2-27-�5 PAGE ��1

FORECAST FOR CA-7 STATIONSPERIOD : �3-�6-�5 AT �� HRS TO �3-�6-�5 AT 12�� HRS

STATION(S) : ALL

NETWORK(S) : ALL

OPTIONS : NEITHER JOB- NOR DSN-TRIGGERED JOBS INCLUDEDDETAILED STATION RECORDS PROVIDED

HIGHEST STATION DATE AND TIME : �NONE�HIGHEST STATION NAME : �NONE�

� �

Note: This is not the summary for the next panel.

202 Commands Guide

FPRE

FPRE Panel - Preprocessing

� � FPRE,FROM=�3�6�5,TO=�3�6�5,SPAN=12 FPRE DATE �3-�1-�5 PAGE ��2

FORECAST FOR CA-7 STATIONSPERIOD : �3-�6-�5 AT �� HRS TO �3-�6-�5 AT 12�� HRS

START DTTM END DTTM STN #/NAME NETWORK SUBID SCHED# SID CONNJOB/SID �5�65/�6�� 5�65/�63� 1 INPUTLOG TIMECARD PAY��1-D SI��32 ��1 �5�65/�63� �5�65/�645 2 KEYENTRY TIMECARD PAY��1-D SI��32 ��1 �5�65/�645 �5�65/�7�� 1 INPUTLOG SHIPPING WHS�2�-D SI��36 ��3 �5�65/�7�� 5�65/�715 1 INPUTLOG APPROVAL ACP��1-W SI��28 ��1 �5�65/�715 �5�65/�73� 2 KEYENTRY SHIPPING WHS�1�-D SI��36 ��3 �5�65/�715 �5�65/�73� 3 VERIFY TIMECARD PAY��1-D SI��32 ��1 �5�65/�73� �5�65/�745 3 VERIFY SHIPPING WHS�2�-D SI��36 ��3 �5�65/�745 �5�65/�8�� 2 KEYENTRY APPROVAL ACP��1-W SI��28 ��1 �5�65/�8�� 5�65/�815 4 LOGOUT TIMECARD PAY��1-D SI��32 ��1 �5�65/�815 �5�65/�83� 3 VERIFY APPROVAL ACP��1-W SI��28 ��1 �5�65/�815 �5�65/�83� 4 LOGOUT SHIPPING WHS�2�-D SI��36 ��3 �5�65/�83� �5�65/�845 4 LOGOUT APPROVAL ACP��1-W SI��28 ��1 �5�65/�845 �5�65/�9�� 5 TRANSMIT TIMECARD PAY��1-D SI��32 ��1 �5�65/�9�� 5�65/�915 5 TRANSMIT SHIPPING WHS�1�-D SI��36 ��3

� �


FQALL

FQALL

The FQALL command provides forecasting for both CPU jobs and workstationnetworks. It includes work in the request, ready, active, preprocess, andpostprocess queues.


FQALL

��──FQALL─ ──┬ ┬───────────────────────── ──┬ ┬─────────────────── ───�└ ┘──, ──┬ ┬──TO=(mmddyy,hhmm) └ ┘──,DRMODE= ──┬ ┬─YES─

└ ┘──SPAN=hhhh ─────── └ ┘─NO──

�─ ──┬ ┬────────────────────────────── ─────────────────────────────�└ ┘──,DRCLASS=(class1,...,class8)

�─ ──┬ ┬──────────────────────────────────── ───────────────────────� │ │┌ ┐─�───────────────────────



�─ ──┬ ┬───────────────────── ──┬ ┬────────────────── ────────────────� │ │┌ ┐─�───── │ │┌ ┐─ALL──

└ ┘──,JOBNET= ──┼ ┼─name── └ ┘──,LIST= ──┼ ┼─#JOB─ └ ┘─name�─ ├ ┤─CPU── ├ ┤─GRPH─ ├ ┤─JOB── └ ┘─STN──

�─ ──┬ ┬──────────────── ──┬ ┬───────────── ──────────────────────────�│ │┌ ┐─1��─ └ ┘──,MAINID= SYn└ ┘──,LVL= ──┴ ┴─nnn─



�─ ──┬ ┬───────────────── ──────────────────────────────────────────� │ │┌ ┐─DLDT─

└ ┘──,SEQ= ──┼ ┼─DODT─ └ ┘─JOB──

�─ ──┬ ┬──────────────────────────────────── ───────────────────────� │ │┌ ┐─�───────────────────────



(continued)

204 Commands Guide

FQALL

FQALL

�─ ──┬ ┬──────────────────── ──┬ ┬──────────────────── ───────────────� │ │┌ ┐─�─────── │ │┌ ┐─J──────


�─ ──┬ ┬──────────────────── ──────────────────────────────────────�� │ │┌ ┐─ACTUAL─

└ ┘──,TYPE= ──┴ ┴─ALL────


TODefines the ending date and time for the time interval to be forecast. If TOis specified, SPAN must be omitted. If neither is specified, only work in thequeues is considered. For more information, see “Forecast Interval” onpage 33.

SPANDefines the length of the time interval to be forecast. This value is added tothe current date and time-of-day to determine the ending date and time ofthe forecast time interval.




Default: ALL

Required: No




GRPHGraphically displays number of jobs running, percent of CPU used andtape usage during each time interval specified.



FQALL

STNProduces resource forecast report. List must be omitted if RINT is notspecified.

ExamplesFQALL

FQALL,SPAN=8

FQALL,TO=1�21

FQALL,JOB=G4�1�,SYS=ACC�,NW=RPT�,STN=(PRNT,BURST,DISTR)

FQALL,RINT=�1��,LIST=STN,SPAN=4



FQALL Panel - Jobs

� � FQALL,SPAN=24

FQALL DATE �5-�7-�5 PAGE ��2

FORECAST FOR CA-7 JOBS (INCLUDING THOSE IN CURRENT QUEUES)PERIOD : �5-�7-�5 AT 1519 HRS TO �5-�8-�5 AT 1519 HRS

START DTTM END DTTM JOB SYS SCHED# SID TRIGGERING JOB/DSN RQMT �5128/161� �5128/161� DUSARS�2 PAYABLES RDY-Q ��1 �5128/161� �5128/161� DUSARS�3 PAYABLES RDY-Q ��1 �5128/161� �5128/161� DUSAXX�1 AUDITORS REQ-Q ��1 �5128/161� �5128/161� DUSAXX�3 BILLING REQ-Q ��1 �5128/1611 �5128/1611 DUSAZZ�1 SHIPPING REQ-Q ��1 NOEX �5128/1621 �5128/1721 DUSAZZ12 SHIPPING LEV��1 ��1 DUSAZZ�1 �5128/1621 �5129/�314 DUSAZZ11 SHIPPING LEV��1 ��1 DUSAZZ�1 �5128/171� �5128/1711 DUSAXX�5 BILLING LEV��1 ��1 DUSAXX�3 �5128/1711 �5128/1�51 DUSAZZ13 SHIPPING LEV��1 ��1 DUSAZZ�1 JCLO �5128/1821 �5129/1721 DUSAZZ22 SHIPPING LEV��2 ��1 DUSAZZ12 �5128/2�11 �5128/21�1 DUSAZZ23 SHIPPING LEV��2 ��1 DUSAZZ13 JCLO �5129/�414 �5129/1414 DUSAZZ21 SHIPPING LEV��2 ��1 DUSAZZ11� �

206 Commands Guide

FQALL

FQALL Panel - Stations

� � FQALLFQALL DATE �5-�7-�5 PAGE ��2

FORECAST FOR CA-7 JOBS AND STATIONS (INCLUDING THOSE IN CURRENT QUEUES)PERIOD : �5-�7-�5 AT 1519 HRS TO �5-�9-�5 AT 1519 HRS

START DTTM END DTTM STN #/NAME NETWORK SUBID SCHED# SID CONNJOB/SID �5127/1519 �5127/1521 1 TRIGST�1 TRIGINNW HEMANT PRE-Q ��1 �5127/1519 �5127/1531 1 KEYPUNCH LAMBINWK TEST PRE-Q ��1 �5127/1711 �5128/�611 1 HTERM2 TESTNET1 TESTSID� POST-Q ��1 DUSAZZ�1 �5128/�8�� 5128/�9�� 1 HTERM1 TEST�TNW RPT12�5 POST-Q ��1 DUSAXX�1 �5128/�8�� 5128/�9�� 2 LHTERM1 TESTNET1 TESTSIDO POST-Q ��1 DUSAZZ�1 �5128/�9�� 5128/1�� 3 DATACNTL TESTNET1 TESTSIDO POST-Q ��1 DUSAZZ�1 �5128/1�� 5128/11�� 4 HTERM1 TESTNET1 TESTSIDO POST-Q ��1 DUSAZZ�1 �5128/11�� 5128/12�� 5 HTERM2 TESTNET1 TESTSIDO POST-Q ��1 DUSAZZ�1 �5128/12�� 5128/13�� 6 LHTERM2 TESTNET1 TESTSIDO POST-Q ��1 DUSAZZ�1 �5128/13�� 5128/14�� 7 DATACNTL TESTNET1 TESTSIDO POST-Q ��1 DUSAZZ�1 �5128/14�� 5128/15�� 8 LHTERM2 TESTNET1 TESTSIDO POST-Q ��1 DUSAZZ�1 �5128/15�� 5128/16�� 9 LHTERM1 TESTNET1 TESTSIDO POST-Q ��1 DUSAZZ�1 �5128/1711 �5128/1721 2 TRIGSTO2 TRIGINNW HEMANT PRE-Q ��1 �5129/�6�� 5129/�7�� 2 HTERM2 TESTOTNW RPT12�5 POST-Q ��1 DUSAXX�1 �5129/12�� 5129/13�� 3 HTERM1 TESTOTNW RPT12�5 POST-Q ��1 DUSAXX�1



FQJOB

FQJOB

The FQJOB command provides forecasting by job name including those CPUjobs in the request, ready, and active queues.


FQJOB

��──FQJOB─ ──┬ ┬───────────────────────── ──┬ ┬─────────────────── ───�└ ┘──, ──┬ ┬──TO=(mmddyy,hhmm) └ ┘──,DRMODE= ──┬ ┬─YES─

└ ┘──SPAN=hhhh ─────── └ ┘─NO──


�─ ──┬ ┬──────────────────────────────────── ───────────────────────� │ │┌ ┐─�───────────────────────



�─ ──┬ ┬───────────────────── ──┬ ┬────────────────── ────────────────� │ │┌ ┐─�───── │ │┌ ┐─ALL──

└ ┘──,JOBNET= ──┼ ┼─name── └ ┘──,LIST= ──┼ ┼─#JOB─ └ ┘─name�─ ├ ┤─CPU── ├ ┤─GRPH─ ├ ┤─JOB── ├ ┤─W──── ├ ┤─WP─── ├ ┤─WPS── └ ┘─WS───

�─ ──┬ ┬──────────────── ──┬ ┬───────────── ──┬ ┬──────────────── ──────�│ │┌ ┐─1��─ └ ┘──,MAINID=SYn └ ┘──,NWOPT= ──┬ ┬─N─└ ┘──,LVL= ──┴ ┴─nnn─ └ ┘─S─

�─ ──┬ ┬──────────── ──┬ ┬─────────────────────────── ────────────────�└ ┘──,RINT=hhmm └ ┘──,SEG=(segment,subsegment)

�─ ──┬ ┬───────────────── ──┬ ┬──────────────────── ──────────────────� │ │┌ ┐─DLDT─ │ │┌ ┐─�───────

└ ┘──,SEQ= ──┼ ┼─DODT─ └ ┘──,SYS= ──┼ ┼─system── └ ┘─JOB── └ ┘─system�─

�─ ──┬ ┬──────────────────── ──┬ ┬──────────────────── ──────────────�� │ │┌ ┐─J────── │ │┌ ┐─ACTUAL─

└ ┘──,TRIG= ──┼ ┼─D────── └ ┘──,TYPE= ──┴ ┴─ALL──── ├ ┤──┬ ┬─JD─ │ │└ ┘─DJ─ └ ┘─N──────


208 Commands Guide

FQJOB

TODefines the ending date and time for the time interval to be forecast. If TOis specified, SPAN must be omitted. If neither is specified, selection isbased on only those jobs in the queues. For more information, see“Forecast Interval” on page 33.




LISTSpecifies the options for resource forecasting. LIST must be omitted if RINTis not specified.

Default: ALL

Required: No






For worksheet requests, RINT must be omitted and LIST can have oneof the following values:

WProduces a schedule worksheet, without prose from the forecast report.

WPProduces prose information with the specified forecast worksheet.

WPSThe same as WP except skip to top page for each job.

WSThe same as W except skip to top of page for each job.


FQJOB

ExamplesFQJOB,TO=(�6�3�5)

FQJOB,SPAN=8

FQJOB,SPAN=24,SYS=INVENTRY

FQJOB,RINT=��1�

FQJOB,TO=(�63��5,16��),RINT=�1��,LIST=GRPH



FQJOB Panel - Jobs Including Queues: Jobs with repeat informationscheduled to run during the forecast period are marked with "(REPEATINGJOB)" in the TRIGGERING JOB/DSN column. Subsequent iterations of thesejobs are treated as if they were triggered by the previous iteration but will havea RPT (repeat) number instead of a LEV (level) number in the SCHED#column.

� � FQJOB,SPAN=24

FQJOB DATE �5-�7-�5 PAGE ��2

FORECAST FOR CA-7 JOBS (INCLUDING THOSE IN CURRENT QUEUES)PERIOD : �5-�7-�5 AT 1518 HRS TO �5-�8-�5 AT 1518 HRS

START DTTM END DTTM JOB SYS SCHED# SID TRIGGERING JOB/DSN RQMT�5127/161� �5127/161� ACRAA�1W RECEVABL RDY-Q ��1�5127/161� �5127/161� ACRAA�2W RECEVABL RDY-Q ��1�5127/161� �5127/161� ACPED�1W PAYABLES REQ-Q ��1�5127/161� �5127/161� CNPAC�1M PAYROLL REQ-Q ��1 NOEX�5127/1611 �5127/1611 WHSAB�1D SHIPPING REQ-Q ��1 JCLO�5127/1621 �5127/1721 WHSAC�1D SHIPPING LEV��1 ��1 WHSAB�1D�5127/1621 �5128/�314 WHSAD�1D SHIPPING LEV��1 ��1 WHSAB�1D�5127/171� �5127/1711 CNPAD�1M PAYROLL LEV��1 ��1 CNPAC�1M�5127/1711 �5127/1�51 WHSAE�1D SHIPPING LEV��2 ��1 WHSAD�1D JCLO�5127/1821 �5127/1721 WHSAF�1D SHIPPING LEV��3 ��1 WHSAE�1D�5127/2�11 �5127/21�1 WHSAG�1D SHIPPING LEV��4 ��1 WHSAF�1D JCLO�5128/�414 �5128/1414 WHSAH�1D SHIPPING LEV��5 ��1 WHSAG�1D

� �

An asterisk (*) in front of a job name indicates the START DTTM has beenadjusted to allow for triggered due-out time conflicts. This usually indicatesmultiple jobs in a trigger stream have the same DOTM value.

210 Commands Guide

FQPOST

FQPOST

The FQPOST command provides forecasting for output network workstationactivity including the postprocess queue.


FQPOST

��──FQPOST─ ──┬ ┬───────────────────────── ─────────────────────────�└ ┘──, ──┬ ┬──TO=(mmddyy,hhmm)

└ ┘──SPAN=hhhh ───────



�─ ──┬ ┬───────────────── ──────────────────────────────────────────� │ │┌ ┐─DLDT─

└ ┘──,SEQ= ──┼ ┼─DODT─ └ ┘─STN──

�─ ──┬ ┬──────────────────────────────────── ──────────────────────�� │ │┌ ┐─�───────────────────────




TODefines the ending date and time for the time interval to be forecast. If TOis specified, SPAN must be omitted. For more information, see “ForecastInterval” on page 33.





FQPOST

ExamplesFQPOST,TO=(�6�3�5)

FQPOST,SPAN=8

FQPOST,TO=(1121�5,17��)

FQPOST,SPAN=8,NW=RPT

FQPOST Panel - Output Networks Including Queues

� � FQPOST,SPAN=1�

FQPOST DATE �5-�7-�5 PAGE ��1

FORECAST FOR CA-7 STATIONS (INCLUDING THOSE IN CURRENT QUEUES)PERIOD : �5-�7-�5 AT 1519 HRS TO �5-�8-�5 AT �119 HRS

START DTTM END DTTM STN #/NAME NETWORK SUBID SCHED# SID CONNJOB/SID �5128/�8�� 5128/�9�� 1 PRINTERS BILLING MONTHLY POST-Q ��1 CHGBL�1M �5128/�8�� 5128/�9�� 2 QUALITY BENEFITS PER��4-A POST-Q ��1 PERAC�1A �5128/�9�� 5128/1�� 3 DECOLLAT BENEFITS PER��4-A POST-Q ��1 PERAC�1A �5128/1�� 5128/11�� 4 BURSTING BENEFITS PER��4-A POST-Q ��1 PERAC�1A �5128/11�� 5128/12�� 5 MICRFILM BENEFITS PER��4-A POST-Q ��1 PERAC�1A �5128/12�� 5128/13�� 6 QUALITY BENEFITS PER��4-A POST-Q ��1 PERAC�1A �5128/13�� 5128/14�� 7 COPIES BENEFITS PER��4-A POST-Q ��1 PERAC�1A �5128/14�� 5128/15�� 8 QUALITY BENEFITS PER��4-A POST-Q ��1 PERAC�1A �5128/15�� 5128/16�� 9 DELIVERY BENEFITS PER��4-A POST-Q ��1 PERAC�1A �5129/�6�� 5129/�7�� 2 DECOLLAT BILLING MONTHLY POST-Q ��1 CHGBL�1M �5129/12�� 5129/13�� 3 DELIVERY BILLING MONTHLY POST-Q ��1 CHGBL�1M� �

212 Commands Guide

FQPRE

FQPRE

The FQPRE command provides forecasting for input network workstationsincluding the preprocess queue.


FQPRE

��──FQPRE─ ──┬ ┬───────────────────────── ──┬ ┬──────────────────── ──�└ ┘──, ──┬ ┬──TO=(mmddyy,hhmm) │ │┌ ┐─�────────

└ ┘──SPAN=hhhh ─────── └ ┘──,NW= ──┼ ┼─network── └ ┘─network�─

�─ ──┬ ┬──────────── ──┬ ┬───────────────── ──────────────────────────�└ ┘──,RINT=hhmm │ │┌ ┐─DLDT─

└ ┘──,SEQ= ──┼ ┼─DODT─ └ ┘─STN──

�─ ──┬ ┬──────────────────────────────────── ──────────────────────�� │ │┌ ┐─�───────────────────────




TODefines the ending date and time for the time interval to be forecast. If TOis specified, SPAN must be omitted. For more information, see “ForecastInterval” on page 33.





FQPRE

ExamplesFQPRE,TO=(�21��5,�8��)

FQPRE,SPAN=8

FQPRE,TO=(�617,17��),STN=KEYPUNCH

� � FQPRE,SPAN=24

FQPRE DATE �5-�7-�5 PAGE ��2

FORECAST FOR CA-7 STATIONS (INCLUDING THOSE IN CURRENT QUEUES)PERIOD : �5-�7-�5 AT 1519 HRS TO �5-�8-�5 AT 1519 HRS

START DTTM END DTTM STN #/NAME NETWORK SUBID SCHED# SID CONNJOB/SID �5128/1511 �5128/1521 1 CONSOLE SYSTSAVE KEYSTATS PRE-Q ��1 �5128/1521 �5128/1531 1 CONSOLE ENGINEER WEEKLY PRE-Q ��1 �5128/1711 �5128/1721 2 PRINTER SYSTSAVE KEYSTATS PRE-Q ��1� �

214 Commands Guide

FQRES

FQRES

The FQRES command provides forecasting, including the queues, for thefollowing resources:

■ CPU workload

– Individual job resources

– Number of jobs running within a time interval

– Percent of CPU usage within a time interval

– Number of tapes required within a time interval

– Amount of memory required within a time interval

■ Number of workstations involved


FQRES


FQRES

��──FQRES─ ──,INT=hhmm ──, ──┬ ┬──TO=(mmddyy,hhmm) ───────────────────�└ ┘──SPAN=hhhh ───────


└ ┘─NO──

�─ ──┬ ┬──────────────────────────────────── ───────────────────────� │ │┌ ┐─�───────────────────────



�─ ──┬ ┬───────────────────── ──┬ ┬────────────────── ────────────────� │ │┌ ┐─�───── │ │┌ ┐─ALL──

└ ┘──,JOBNET= ──┼ ┼─name── └ ┘──,LIST= ──┼ ┼─#JOB─ └ ┘─name�─ ├ ┤─CPU── ├ ┤─GRPH─ ├ ┤─JOB── ├ ┤─STN── └ ┘─TAPE─

�─ ──┬ ┬──────────────── ──┬ ┬──────────────────── ───────────────────� │ │┌ ┐─1��─ │ │┌ ┐─�────────

└ ┘──,LVL= ──┴ ┴─nnn─ └ ┘──,NW= ──┼ ┼─network── └ ┘─network�─

�─ ──┬ ┬──────────────────────────────────── ───────────────────────� │ │┌ ┐─�───────────────────────



�─ ──┬ ┬──────────────────── ──┬ ┬──────────────────── ──────────────�� │ │┌ ┐─�─────── │ │┌ ┐─J──────



TODefines the ending date and time for the time interval to be forecast. If TOis specified, SPAN must be omitted. Both are optional. If neither isspecified, the selection is based on the queues only, and current date andtime are assumed.

mmddyyDefines the date. Optional.

mmDefines the month (01 through 12). If TO is specified, mm isrequired. Leading zero is required.

216 Commands Guide

FQRES

ddDefines the day (01 through 31). Optional. If omitted and TO isspecified, last day of month is assumed.

yyDefines the year. Optional. If TO is specified and yy is omitted, thecurrent year is assumed.

hhmmDefines the time. Optional. If TO is specified and hhmm omitted, 2359is assumed.







Default: ALL

Required: No






STNProduces resource forecast report for workstation workload.


FQRES

TAPEGraphically displays total number of tapes during each time intervalspecified.

ExamplesFQRES,INT=��1�,TO=�6

FQRES,SPAN=8,INT=��15,LIST=JOB

FQRES,SPAN=72�,INT=24��,LIST=CPU

FQRES,INT=��1�,JOB=PAYR�,TO=�6

The panels produced by the FQRES command are identical to those producedby the FRES command. For examples of the panels, see FRES panel onpage 227 through FRES panel on page 229.

218 Commands Guide

FQSTN

FQSTN

The FQSTN command provides forecasting for input and output networkworkstations including the preprocess and postprocess queues.


FQSTN

��──FQSTN─ ──┬ ┬───────────────────────── ──┬ ┬──────────────────── ──�└ ┘──, ──┬ ┬──TO=(mmddyy,hhmm) │ │┌ ┐─�────────

└ ┘──SPAN=hhhh ─────── └ ┘──,NW= ──┼ ┼─network── └ ┘─network�─

�─ ──┬ ┬──────────── ──┬ ┬───────────────── ──────────────────────────�└ ┘──,RINT=hhmm │ │┌ ┐─DLDT─

└ ┘──,SEQ= ──┼ ┼─DODT─ └ ┘─STN──

�─ ──┬ ┬──────────────────────────────────── ──────────────────────�� │ │┌ ┐─�───────────────────────




TODefines the ending date and time for the time interval to be forecast. If TOis specified, SPAN must be omitted. If neither is specified, selection isbased on only those workstations in the preprocess or postprocess queues.For more information, see “Forecast Interval” on page 33.





FQSTN

ExamplesFQSTN

FQSTN,SPAN=8

FQSTN,STN=KEYPUNCH

FQSTN,TO=(�63��5,17��),RINT=�2��

FQSTN,NW=RPT,STN=(BURST,DISTR)

FQSTN Panel - Stations Including Queues

� � FQSTN

FQSTN DATE �5-�7-�5 PAGE ��2

FORECAST FOR CA-7 STATIONS (INCLUDING THOSE IN CURRENT QUEUES)PERIOD : �5-�7-�5 AT 1519 HRS TO �5-�9-�5 AT 1519 HRS

START DTTM END DTTM STN #/NAME NETWORK SUBID SCHED# SID CONNJOB/SID �5127/1519 �5127/1521 1 CONSOLE SYSTSAVE KEYSTATS PRE-Q ��1 DMD#��6 �5127/1519 �5127/1531 1 CONSOLE ENGINEER WEEKLY PRE-Q ��1 DND#��7 �5127/1711 �5128/�611 1 PRINTERS BENEFITS PER��4-A POST-Q ��1 PERAC�1A �5128/�8�� 5128/�9�� 1 PRINTERS BILLING MONTHLY POST-Q ��1 CHGBL�1M �5128/�8�� 5128/�9�� 2 QUALITY BENEFITS PER��4-A POST-Q ��1 PERAC�1A �5128/�9�� 5128/1�� 3 DECOLLAT BENEFITS PER��4-A POST-Q ��1 PERAC�1A �5128/1�� 5128/11�� 4 BURSTING BENEFITS PER��4-A POST-Q ��1 PERAC�1A �5128/11�� 5128/12�� 5 MICRFILM BENEFITS PER��4-A POST-Q ��1 PERAC�1A �5128/12�� 5128/13�� 6 QUALITY BENEFITS PER��4-A POST-Q ��1 PERAC�1A �5128/13�� 5128/14�� 7 COPIES BENEFITS PER��4-A POST-Q ��1 PERAC�1A �5128/14�� 5128/15�� 8 QUALITY BENEFITS PER��4-A POST-Q ��1 PERAC�1A �5128/15�� 5128/16�� 9 DELIVERY BENEFITS PER��4-A POST-Q ��1 PERAC�1A �5128/1711 �5128/1721 2 PRINTER SYSTSAVE KEYSTATS PRE-Q ��1 DMD#��6 �5129/�6�� 5129/�7�� 2 DECOLLAT BILLING MONTHLY POST-Q ��1 CHGBL�1M �5129/12�� 5129/13�� 3 DELIVERY BILLING MONTHLY POST-Q ��1 CHGBL�1M� �

220 Commands Guide

FQTAPE

FQTAPE

The FQTAPE command provides a tape pull list for CPU jobs including those inthe Unicenter CA-7 queues.


FQTAPE

��──FQTAPE─ ──┬ ┬───────────────────────── ──┬ ┬─────────────────── ──�└ ┘──, ──┬ ┬──TO=(mmddyy,hhmm) └ ┘──,DRMODE= ──┬ ┬─YES─

└ ┘──SPAN=hhhh ─────── └ ┘─NO──


�─ ──┬ ┬──────────────────────────────────── ───────────────────────� │ │┌ ┐─�───────────────────────



�─ ──┬ ┬───────────────────── ──┬ ┬──────────────────── ──────────────� │ │┌ ┐─�───── │ │┌ ┐─�───────

└ ┘──,JOBNET= ──┼ ┼─name── └ ┘──,SYS= ──┼ ┼─system── └ ┘─name�─ └ ┘─system�─

�─ ──┬ ┬──────────────────── ──────────────────────────────────────�� │ │┌ ┐─J──────

└ ┘──,TRIG= ──┼ ┼─D────── ├ ┤──┬ ┬─JD─ │ │└ ┘─DJ─ └ ┘─N──────


TODefines the ending date and time for the time interval to be forecast. If TOis specified, SPAN must be omitted. If neither is specified, selection is fromthe queues only and current date and time are assumed.


mmDefines the month (01 through 12). Required. Leading zero isrequired.

ddDefines the day (01 through 31). Optional. If omitted, current day isassumed. Leading zero is required.



FQTAPE

hhmmDefines the time. Optional. If omitted, current time is assumed.






ExamplesFQTAPE

FQTAPE,SPAN=24

FQTAPE,SPAN=8,JOB=GL�,TRIG=JD

FQTAPE Panel - Tapes Including Queues

� � FQTAPE FQTAPE DATE �5-�7-�5 PAGE ��2

TAPE PULL LIST FOR CA-7 JOBS (INCLUDING THOSE IN CURRENT QUEUES)PERIOD : �5-�7-�5 AT 1528 HRS TO �5-�7-�5 AT 1528 HRS

VOLSER -------------- DATASET NAME -------------- CREATED-ON DEV-CODE SEQJOBNAME SYSTEM START DTTM END DTTM SCHED# SID TRIGGERING JOB/DSN

123456 CA-7.TAPE �5242/1�41 34��8��3 ��1DUSAZZ23 TESTGFRC �5128/2�11 �5128/21�1 LEV��2 ��1 DUSAZZ13

98765� CA-7.TTAPE �5242/1�41 34��8��3 ��1DUSAZZ23 TESTGFRC �5128/2�11 �5128/21�1 LEV��2 ��1 DUSAZZ13

SCRATCH ... APPROXIMATELY ��4 TAPES REQUIRED FOR OUTPUT DATASETS.


222 Commands Guide

FRES

FRES

The FRES command provides forecasting, from the database only, for thefollowing resources:

■ CPU workload

– Individual job resources

– Number of jobs running within a time interval

– Percent of CPU usage within a time interval

– Number of tapes required within a time interval

– Amount of memory required within a time interval

■ Number of workstations involved


FRES

��──FRES─ ──,FROM=(mmddyy,hhmm) ──,INT=hhmm ────────────────────────�

�─ ──, ──┬ ┬──TO=(mmddyy,hhmm) ──┬ ┬─────────────────── ───────────────�└ ┘──SPAN=hhhh ─────── └ ┘──,DRMODE= ──┬ ┬─YES─

└ ┘─NO──


�─ ──┬ ┬──────────────────────────────────── ───────────────────────� │ │┌ ┐─�───────────────────────



�─ ──┬ ┬───────────────────── ──┬ ┬──────────── ──────────────────────�│ │┌ ┐─�───── └ ┘──,LIST=list└ ┘──,JOBNET= ──┼ ┼─name──

└ ┘─name�─

�─ ──┬ ┬──────────────── ──┬ ┬──────────────────── ───────────────────� │ │┌ ┐─1��─ │ │┌ ┐─�────────

└ ┘──,LVL= ──┴ ┴─nnn─ └ ┘──,NW= ──┼ ┼─network── └ ┘─network�─

�─ ──┬ ┬────────────────── ─────────────────────────────────────────� │ │┌ ┐─�───

└ ┘──,SCHID= ──┴ ┴─nnn─

(continued)


FRES

FRES

�─ ──┬ ┬──────────────────────────────────── ───────────────────────� │ │┌ ┐─�───────────────────────



�─ ──┬ ┬──────────────────── ──┬ ┬──────────────────── ──────────────�� │ │┌ ┐─�─────── │ │┌ ┐─J──────



FROMDefines the beginning date and time for the time interval to be forecast.FROM is required.



ddDefines the day (01 through 31). Optional. If omitted, 01 isassumed. Leading zero is required.

yyDefines the year. Optional. If omitted, current year is assumed.




224 Commands Guide

FRES

TODefines the ending date and time for the time interval to be forecast. TO isoptional. If TO is specified, SPAN must be omitted. Either TO or SPANmust be specified.



ddDefines the day (01 through 31). Optional. If omitted, last day ofmonth is assumed. Leading zero is required.









FRES


Default: ALL

Required: No






STNProduces resource forecast report for workstation workload.

TAPEGraphically displays total number of tapes during each time intervalspecified.

ExamplesFRES,FROM=(�3�5�5,�8��),TO=(�316,17),INT=��3�

FRES,FROM=�3,SPAN=24,SYS=GLACTG,INT=�1��

FRES,FROM=11,TO=21,INT=24��,LIST=CPU

226 Commands Guide

FRES

FRES Panel - Resource Forecast for CA-7 Jobs

� � FRES,FROM=(�3�6,�7��),SPAN=4,JOB=DUSAZZ�1,INT=�1��

FRES DATE �2-27-�5 PAGE ��2RESOURCE FORECAST FOR CA-7 JOBS

PERIOD : �3-�6-�5 AT �7�� HRS TO �3-�6-�5 AT 11�� HRS

TIME INTERVAL #JOBS JOB SID CL %CPU CORE TP1 TP2 �65/�7��-�8�� DUSAZZ�1 ��1 A ��.222 ��4�K ��1 �� 65/�7��-�8�� 1 ��.222 ��4�K ��1 ��

�65/�8��-�9�� DUSAZZ11 ��1 A ��.�78 �9999K ��1 ��1 DUSAZZ12 ��1 H ��.392 �1��K ��2 ��

�65/�8��-�9�� 2 ��.47� 1�999K ��3 ��1

�65/�9��-1�� DUSAZZ11 ��1 A ��.�94 �9999K �� 2 DUSAZZ12 ��1 H ��.�8� �1��K ��1 �� DUSAZZ13 ��1 Z ��.486 �8888K ��3 ��1

�65/�9��-1�� 3 ��.66� 19887K ��4 ��3

�65/1��-11�� DUSAZZ11 ��1 A ��.�94 �9999K �� 2 DUSAZZ13 ��1 Z ��.486 �8888K ��1 �� DUSAZZ22 ��1 Z ��.417 �8888K ��4 ��

�65/1��-11�� 3 ��.997 27775K ��5 ��2� �

FRES Panel - Resource Forecast for CA-7 Jobs - Number of Jobs

� � FRES,INT=�1��,FROM=(�5�8�5,16��),TO=(�5�9�5,�5��)

FRES DATE �5-�7-�5 PAGE ��2RESOURCE FORECAST FOR CA-7 JOBS

PERIOD : �5-�8-�5 AT 16�� HRS TO �5-�9-�5 AT �5�� HRS

TIME INTERVAL NUMBER OF JOBS #JOBS %CPU #TAPE1 1 2 2 3 3 4

�....5....�....5....�....5....�....5....� 128/16��-17�� 7 ��2.21�% �38 128/17��-18�� 4 ��.6�5% �15 128/18��-19�� 3 ��.9�7% �11 128/19��-2�� 3 ��.684% �16 128/2��-21�� 3 ��8.523% �14 128/21��-22�� 3 ��.79�% �1� 128/22��-23�� 2 ��.597% �17 128/23��-24�� 2 ��.597% �21 128/24��-�1�� 2 ��.597% �19 129/�1��-�2�� 2 ��.597% �14 129/�2��-�3�� 2 ��.597% ��9 129/�3��-�4�� 2 ��.525% �16 129/�4��-�5�� 2 ��.7�4% �22� �


FRES

FRES Panel - Resource Forecast for CA-7 Jobs - Percent of CPU Utilization

� � FRES,INT=�1��,FROM=(�5�8�5,16��),TO=(�5�9�5,�5��)

FRES DATE �5-�7-�5 PAGE ��7RESOURCE FORECAST FOR CA-7 JOBS

PERIOD : �5-�8-�5 AT 16�� HRS TO �5-�9-�5 AT �5�� HRS

TIME INTERVAL PER CENT CPU UTILIZATION %CPU #JOBS #TAPES 1 2 3 4 5 6 7 8 9 1 �..�..�..�..�..�..�..�..�..�..��

128/16��-17�� 2.21�% �7 �38 128/17��-18�� .6�5% �4 �15 128/18��-19�� .9�7% �3 �11 128/19��-2�� .684% �3 �16 128/2��-21�� 8.523% �3 �14 128/21��-22�� .79�% �3 �1� 128/22��-23�� .597% �2 �17 128/23��-24�� .597% �2 �21 128/24��-�1�� .597% �2 �19 129/�1��-�2�� .597% �2 �14 129/�2��-�3�� .597% �2 ��9 129/�3��-�4�� .525% �2 �16 129/�4��-�5�� .7�4% �2 �22� �

FRES Panel - Resource Forecast for CA-7 Jobs - Number of TAPE1

� � FRES,FROM=�3�6�5,TO=�3�6�5,INT=�1��



TIME INTERVAL NUMBER OF TAPE1 #TAPES #JOBS %CPU1 2 3 4 5 6 7 8

�...�...�...�...�...�...�...�...� �65/�7��-�8�� 38 ��7 ��2.21�% �65/�8��-�9�� 15 ��4 ��.6�5% �65/�9��-1�� 11 ��3 ��.9�7% �65/1��-11�� 16 ��3 ��.684% �65/11��-12�� 14 ��3 ��8.523% �65/12��-13�� 1� ��3 ��.79�% �65/13��-14�� 17 ��2 ��.597% �65/14��-15�� 21 ��2 ��.597% �65/15��-16�� 19 ��2 ��.597% �65/16��-17�� 14 ��2 ��.597% �65/17��-18�� 9 ��2 ��.597% �65/18��-19�� 16 ��2 ��.525% �65/19��-2�� 22 ��2 ��.7�4%� �

228 Commands Guide

FRES

FRES Panel - Resource Forecast for CA-7 Jobs - Number of TAPE2

� � FRES,FROM=�3�6�5,TO=�3�6�5,INT=�1��



TIME INTERVAL NUMBER OF TAPE2 #TAPES #JOBS %CPU1 2 3 4 5 6 7 8

�....�....�....�....�....�....�....�....� �65/�7��-�8�� 38 ��7 ��2.21�% �65/�8��-�9�� 15 ��4 ��.6�5% �65/�9��-1�� 11 ��3 ��.9�7% �65/1��-11�� 16 ��3 ��.684% �65/11��-12�� 14 ��3 ��8.523% �65/12��-13�� 1� ��3 ��.79�% �65/13��-14�� 17 ��2 ��.597% �65/14��-15�� 21 ��2 ��.597% �65/15��-16�� 19 ��2 ��.597% �65/16��-17�� 14 ��2 ��.597% �65/17��-18�� 9 ��2 ��.597% �65/18��-19�� 16 ��2 ��.525% �65/19��-2�� 22 ��2 ��.7�4%� �

FRES Panel - Resource Forecast for CA-7 Stations (Summary)

� � FRES,FROM=�3�6�5,TO=�3�6�5,INT=�1��

FRES DATE �2-27-�5 PAGE ��1RESOURCE FORECAST FOR CA-7 STATIONS


TIME INTERVAL #STNS STATION NETWORK SUBID �65/�1��-�2�� BALANCE ACCT��1 PAYMENTS

DECOLLAT ACCT��1 PAYMENTS LOGDESK ACCT��1 PAYMENTS

DELIVERY ACCT��1 PAYMENTS

�65/�1��-�2�� 4



FRJOB

FRJOB

The FRJOB command answers the question, "How does this job get into thesystem?" It presents a reverse job flow (reverse trigger flow) based uponinformation in the database. The purpose is to identify how the target job canbe brought into the active scheduling system. It tracks backward throughtriggers from the target job to one or more header jobs. A header job is onethat has one or more defined date/time schedules, or, that has no job/dataset/network triggers defined. That is, a job, network, or data set that starts thetrigger flow that eventually results in the target job being brought into the activescheduling system. FRJOB uses only information in the Unicenter CA-7database.


FRJOB

��──FRJOB─ ──,JOB= ──┬ ┬─jobname───────────────── ───────────────────�└ ┘──(jobname1,...jobname1�)


└ ┘─NO──

�─ ──┬ ┬───────────────────── ──┬ ┬────────────────── ────────────────� │ │┌ ┐─�───── │ │┌ ┐─ALL──

└ ┘──,JOBNET= ──┼ ┼─name── └ ┘──,LIST= ──┼ ┼─HDRS─ └ ┘─name�─ └ ┘─LAST─

�─ ──┬ ┬──────────────── ──┬ ┬────────────────── ─────────────────────� │ │┌ ┐─1��─ │ │┌ ┐─�───

└ ┘──,LVL= ──┴ ┴─nnn─ └ ┘──,SCHID= ──┴ ┴─nnn─

�─ ──┬ ┬──────────────────── ──┬ ┬──────────────────── ──────────────�� │ │┌ ┐─�─────── │ │┌ ┐─ACTUAL─

└ ┘──,SYS= ──┼ ┼─system── └ ┘──,TYPE= ──┴ ┴─ALL──── └ ┘─system�─


JOBDefines the specific jobs from which the reverse flows are started. Thevalue can be one specific job name or a substring of 1 to 10 specific jobnames.

SCHIDDefines the schedule ID of the starting jobs (JOB=) used to start thereverse flow. It can be a value from 0 to 255. The default is 0, which meansthe next level contains elements that can cause ANY schedule ID of thestarting job to be triggered/scheduled.

230 Commands Guide

FRJOB

LISTSpecifies the option of listing the entire structure or just the first and lastjobs.

Default: ALL

Required: No

ALLSpecifies the entire structure is to be listed.

HDRSSpecifies that only those elements identified as 'headers' and thestarting job should be listed.

LASTSpecifies only the first and last elements are to be listed.

ExamplesFRJOB,JOB=PAY��9�,SCHID=1

FRJOB,JOB=AR#��3�,SCHID=�,LIST=LAST

FRJOB,JOB=ORD��88,LVL=1�


FRJOB

Usage Notes

The FRJOB command is useful when you are creating or modifying theschedules and triggers for a workload flow. If you need to determine all of thepaths that schedules, triggers, or both can take to result in a given job beingrun, FRJOB can be most helpful.

For example, your operations staff informs you that a second copy of jobPAY0090 is being brought into the system whenever the PAYROLL applicationis run, even though it had already run earlier in the cycle. You can use FRJOBto determine not only the possible triggers for PAY0090, but also the path ofcontrol that leads up to each of those triggers. With this information you canmore easily diagnose the problem, and also check the results after you havemade changes to the structure.

The FRJOB display does not include any dates or times for elements in thestructure. This is because the flow is being generated backwards throughlogical control paths. Also, the display can include jobs with a schedule ID ofzero (000) that indicates it represents any occurrence of the job rather than aspecific occurrence of the job. Once you have determined the origin points forthe target job you can use one of the other forecasting commands to retrace aparticular control path from the origin point to the target job with dates andtimes provided.

� � FRJOB,JOB=BBD�7 FRJOB DATE �4-�1-yy PAGE ��1

REVERSE STRUCTURE FOR CA-7 JOBS

JOB(S) : BBD�7

SYSTEM(S) : ALL JOBNET(S) : ALL

OPTIONS : BOTH JOB- AND DSN-TRIGGERED JOBS INCLUDEDCONNECTED OUTPUT NETWORKS NOT INCLUDED

HEADER JOB/NETWORK NAME : BBD�6I AND OTHERS� �

232 Commands Guide

FRJOB

The forecasting summary page for FRJOB follows the general format of allforecasting commands with the following exceptions:

HEADER JOB/NETWORK NAMEThis field shows the name of the first (or only) origination point (header) forthe control flow that eventually results in the target job.

AND OTHERSIf there are multiple possible origin points in the reverse job flow, this areacontains the text AND OTHERS. If there is only one origination point(header) for the flow, this area is blank.

� � FRJOB,JOB=BBD�7

FRJOB DATE �4-�1-yy PAGE ��1REVERSE STRUCTURE FOR CA-7 JOBS

HDR LEV# JOB NAME SYSTEM SID TYPE TRIGGERS /DSNBR /SCHEDULED --- BBD�7 ............ �� -��1 BBD�6I .......... ��1 INWK BBD�7 :��SCHD��

-��1 BBD�6 .......... ��6 JOB BBD�7 -��2 BBD�5 ........ ��5 JOB BBD�6�� -��3 BBD�4B ...... ��5 DSET BBD�5 :DS��58

-��3 BBD�4 ...... ��4 JOB BBD�5 -��4 BBD�3 .... ��3 JOB BBD�4 -��5 BBD�2 .. ��2 JOB BBD�3

�� -��6 BBD�1 BBDSYS ��1 JOB BBD�2 :��SCHD��

SFC1-�� REQUEST COMPLETED AT 12:55:18 on yy.�92� �


HDRHeader Indicator. Displays asterisks (*) if the element on that line isconsidered a header (origination point). Otherwise, it is blank.

LEV#Level. Identifies the logical level of the element on that line. The startingpoint (target job) is at level zero, which is represented by three hyphens(---). The elements that can trigger the target job have a level of negativeone (-001). The elements that can trigger the negative one level have alevel of negative two (-002), and so forth.

JOB NAMEIdentifies the name of the job or network that triggers an element on thenext higher level. The name is offset to the right for each level up to thesixth level (-006). This makes it easier to see what level a given element ison. Elements that are six or more levels deep all appear starting at thesame column as the sixth level.

SYSTEMIdentifies the application system name of the job on this line.


FRJOB

SIDSchedule ID. Identifies the schedule ID of the job or network on this line. Ageneric schedule ID of zero (000) can appear in the flow. Such an entryrepresents ANY occurrence of the job or network.

TYPEType of element. Identifies a literal that describes the type of element andtrigger the line represents.

The following are the possible values:

JOBIndicates the element in the Job Name field is a job that triggers the jobin the Triggers field through a job trigger.

DSETIndicates the element in the Job Name field is a job that updates orcreates a data set (DSNBR field) that triggers the job in the Triggersfield through a data set trigger.

INWKIndicates the element in the Job Name field is an input network thattriggers the job in the Triggers field through a network trigger.

TRIGGERSIdentifies the name of the job on the next higher level that this elementtriggers. For example, the last line of the preceding example means that jobBBD01 (level -006) triggers job BBD02 on the next higher level (level -005).

DSNBRData Set Number. Identifies the Unicenter CA-7 data set number of thedata set created or updated by the job shown in the Job Name that causesa data set trigger to bring in the job shown in Triggers. The DSNBR is onlydisplayed if a data set trigger is involved, otherwise it is blank.

SCHEDULEDSchedule Indicator. Identifies the literal **SCHD** if the element on this linehas one or more date/time schedules defined to Unicenter CA-7. Otherwiseit is blank.

234 Commands Guide

FRQJOB

FRQJOB

The FRQJOB command is useful to answer the question, "How does this jobget into the system today?" It presents a reverse job flow (reverse trigger flow)based on information in the database. It also checks the status queues(request, ready, and active) for the presence of each job in the structure as it isbeing built.

The purpose is to identify how the target job is brought into the activescheduling system taking into account jobs that are already in the queues. Ittracks backward through triggers from the target job to one or more headerjobs. A header job is one that is already in the request, ready, or active queueor one that has one or more defined date/time schedules, or one that has nojob/data set/network triggers defined.

The difference between the FRQJOB command and FRJOB is that a check ismade in the status queues for each job present in the structure. If it is found inone of the queues, that job is considered a header job even though it may havebeen triggered by something else. This identifies the shortest possible controlpath that results in execution of the target job.


FRQJOB

��──FRQJOB─ ──,JOB= ──┬ ┬─jobname───────────────── ──────────────────�└ ┘──(jobname1,...jobname1�)


└ ┘─NO──

�─ ──┬ ┬───────────────────── ──┬ ┬────────────────── ────────────────� │ │┌ ┐─�───── │ │┌ ┐─ALL──

└ ┘──,JOBNET= ──┼ ┼─name── └ ┘──,LIST= ──┼ ┼─HDRS─ └ ┘─name�─ └ ┘─LAST─

�─ ──┬ ┬──────────────── ──┬ ┬────────────────── ─────────────────────� │ │┌ ┐─1��─ │ │┌ ┐─�───

└ ┘──,LVL= ──┴ ┴─nnn─ └ ┘──,SCHID= ──┴ ┴─nnn─

�─ ──┬ ┬──────────────────── ──┬ ┬──────────────────── ──────────────�� │ │┌ ┐─�─────── │ │┌ ┐─ACTUAL─

└ ┘──,SYS= ──┼ ┼─system── └ ┘──,TYPE= ──┴ ┴─ALL──── └ ┘─system�─


FRQJOB


JOBDefines the specific jobs from which the reverse flows is started. The valuecan be one specific job name, or a substring of 1 to 10 specific job names.

SCHIDDefines the schedule ID of the starting jobs (JOB=) used to start thereverse flow. It can be a value from 0 to 255. The default is 0, which meansthe next level contains elements that can cause ANY schedule ID of thestarting job to be triggered/scheduled.

LISTSpecifies the option of listing the entire structure or just the first and lastjobs.

Default: ALL

Required: No

ALLSpecifies to list the entire structure.

HDRSSpecifies to list that only those elements identified as 'headers' and thestarting job.

LASTSpecifies to list only the first and last elements.

ExamplesFRQJOB,JOB=PAY��9�,SCHID=1

FRQJOB,JOB=AR#��3�,SCHID=�,LIST=LAST

FRQJOB,JOB=ORD��88,LVL=1�

236 Commands Guide

FRQJOB

Usage Notes

The FRQJOB command is useful when you are trying to determine how a job isgoing to get into the scheduling system in the near future. You would first usethe FRQJOB command to see if there is anything currently in the queues thateventually results in triggering of the target job.

For example, a vice president of your company calls and asks if job XYZ isgoing to run before the end of the day. You issue an FRQJOB command forXYZ and learn that job X is currently in the request queue, and it triggers job Ythat in turn triggers job XYZ. You can then issue an FQJOB command for job Xthat gives you an estimate of the time that job XYZ executes. Without theFRQJOB command, you would have had to manually analyze the situation witha series of LJOB,LIST=TRIG and LQ commands.

The FRQJOB display does not include any dates or times for elements in thestructure. This is because the flow is being generated backwards throughlogical control paths. Also, the display can include jobs with a schedule ID ofzero (000) that indicates it represents any occurrence of the job rather than aspecific occurrence of the job. Once you have determined the origin points forthe target job, you can use one of the other forecasting commands to retrace aparticular control path from the origin point to the target job with dates andtimes provided.

� � FRQJOB,JOB=FLOW4H FRQJOB DATE �3-2�-yy PAGE ��1

REVERSE STRUCTURE FOR CA-7 JOBS (INCLUDING QUEUES)

JOB(S) : FLOW4H

SYSTEM(S) : ALL JOBNET(S) : ALL

OPTIONS : BOTH JOB- AND DSN-TRIGGERED JOBS INCLUDEDCONNECTED OUTPUT NETWORKS NOT INCLUDED

�A� �B�HEADER JOB/NETWORK NAME : FLOW1A (�842)

� �

The forecasting summary page for FRQJOB follows the general format of allforecasting commands with the following exceptions:

�A�This field shows the name of the first (or only) origination point (header) forthe control flow that eventually results in the target job. If the job is currentlyin one of the status queues the Unicenter CA-7 job number is displayed also(0842).

�B�If there are multiple possible origin points in the reverse job flow, this areacontains the text AND OTHERS. If there is only one origination point(header) for the flow, this area is blank.


FRQJOB

� � FRQJOB,JOB=FLOW4H

FRQJOB DATE �3-2�-yy PAGE ��1REVERSE STRUCTURE FOR CA-7 JOBS (INCLUDING QUEUES)

HDR LEV# JOB NAME SYSTEM SID TYPE TRIGGERS /DSNBR /SCHEDULED --- FLOW4H ............ FLOWSYS �� -��1 FLOW3D .......... FLOWSYS ��1 JOB FLOW4H

-��2 FLOW2C ........ FLOWSYS �� DSET FLOW3D :DS��4� �842 -��3 FLOW1A ...... FLOWSYS ��1 JOB FLOW2C

SFC1-�� REQUEST COMPLETED AT 17:35:19 on yy.�8��


HDRHeader Indicator. Displays nonblanks if the element on that line isconsidered a header (origination point). If the header job currently resides inthe request, ready, or active queue, the field contains the four-digitUnicenter CA-7 job number. If the header job does not currently reside inqueues, the field contains asterisks.

LEV#Level. Identifies the logical level of the element on that line. The startingpoint (target job) is at level zero, which is represented by three hyphens(---). The elements that can trigger the target job have a level of negativeone (-001). The elements that can trigger the negative one level have alevel of negative two (-002), and so forth.

JOB NAMEIdentifies the name of the job or network that triggers an element on thenext higher level. The name is offset to the right for each level up to thesixth level (-006). This makes it easier to see what level a given element ison. Elements that are six or more levels deep all appear starting at thesame column as the sixth level.

SYSTEMSystem Name. Identifies the application system name of the job on this line.

SIDSchedule ID. Identifies the schedule ID of the job or network on this line. Ageneric schedule ID of zero (000) can appear in the flow. Such an entryrepresents ANY occurrence of the job or network.

238 Commands Guide

FRQJOB

TYPEType of element. Identifies a literal that describes the type of element andtrigger the line represents.

The following are the possible values:

JOBIndicates the element in the Job Name field is a job that triggers the jobin the Triggers field through a job trigger.

DSETIndicates the element in the Job Name field is a job that updates orcreates a data set (DSNBR field) that triggers the job in the Triggersfield through a data set trigger.

INWKIndicates the element in the Job Name field is an input network thattriggers the job in the Triggers field through a network trigger.

TRIGGERSIdentifies the name of the job on the next higher level that this elementtriggers. For example, the last line of the preceding example means that jobFLOW1A (level -003) triggers job FLOW2C on the next higher level (level-002).

DSNBRData Set Number. Identifies the Unicenter CA-7 data set number of thedata set created or updated by the job shown in the Job Name, whichcauses a data set trigger to bring in the job shown in Triggers. The DSNBRis only displayed if a data set trigger is involved; otherwise, it is blank.

SCHEDULEDSchedule Indicator. Identifies the literal **SCHD** if the element on this linehas one or more date/time schedules defined to Unicenter CA-7. Otherwiseit is blank.


FSTN

FSTN

The FSTN command provides forecasting of output and input networkworkstations. Only the database is used for this forecast.


FSTN

��──FSTN─ ──,FROM=(mmddyy,hhmm) ──, ──┬ ┬──TO=(mmddyy,hhmm) ──────────�└ ┘──SPAN=hhhh ───────



�─ ──┬ ┬───────────────── ──────────────────────────────────────────� │ │┌ ┐─DLDT─

└ ┘──,SEQ= ──┼ ┼─DODT─ └ ┘─STN──

�─ ──┬ ┬──────────────────────────────────── ──────────────────────�� │ │┌ ┐─�───────────────────────





TODefines the ending date and time for the time interval to be forecast. EitherTO or SPAN must be specified. If TO is used, SPAN must be omitted. Formore information, see “Forecast Interval” on page 30.




240 Commands Guide

FSTN

ExamplesFSTN,FROM=(�3�5�5,�8��),TO=(�316,17)

FSTN,FROM=�3,TO=�3,STN=KEYPUNCH

FSTN,FROM=(�3,17),SPAN=8,NW=RPT,STN=(BURST,DISTR)

FSTN,FROM=�2,SPAN=24,RINT=��45

FSTN Panel - Forecast for CA-7 Stations (Summary)

� � FSTN,FROM=�3�6�5,TO=�3�6�5

FSTN DATE �2-27-�5 PAGE ��1


STATIONS(S) : ALL

NETWORK(S) : ALL



� �

FSTN Panel - Forecast for CA-7 Stations

� � FSTN,FROM=�3�6�5,TO=�3�6�5

FSTN DATE �2-27-�5 PAGE ��2


START DTTM END DTTM STN #/NAME NETWORK SUBID SCHED# SID CONNJOB/SID �5�65/�9�� 5�65/11�� 1 BURST TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��1 �5�65/12�� 5�65/13�� 2 TRIM TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��1 �5�65/13�� 5�65/15�� 1 BURST TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��2 �5�65/15�� 5�65/153� 3 BINS TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��1 �5�65/16�� 5�65/17�� 2 TRIM TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��2 �5�65/17�� 5�65/19�� 1 BURST TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��3 �5�65/19�� 5�65/193� 3 BINS TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��2 �5�65/2�� 5�65/21�� 2 TRIM TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��3 �5�65/21�� 5�65/23�� 1 BURST TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��4 �5�65/23�� 5�65/233� 3 BINS TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��3 �5�66/�� 5�66/�1�� 2 TRIM TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��4 �5�66/�3�� 5�66/�33� 3 BINS TESTONWK RPT12�5 SO��1 ��1 DUCCXX�1:��4



FSTRUC

FSTRUC

Use this command to produce a report displaying an entire CPU job flowstructure with the starting and ending times. The principal emphasis is on thejob flow structure and the elapsed time of each job. The start time of the firstjob can be any arbitrary time. Only the database is used for this forecast.


FSTRUC

��──FSTRUC─ ──┬ ┬─────────────────── ───────────────────────────────�└ ┘──,DRMODE= ──┬ ┬─YES─

└ ┘─NO──

�─ ──┬ ┬────────────────────────────── ──┬ ┬───────────────────── ────�└ ┘──,DRCLASS=(class1,...,class8) └ ┘──,FROM=(mmddyy,hhmm)

�─ ──┬ ┬──────────────────────────────────── ───────────────────────� │ │┌ ┐─�───────────────────────



�─ ──┬ ┬───────────────────── ──┬ ┬────────────────── ────────────────� │ │┌ ┐─�───── │ │┌ ┐─ALL──

└ ┘──,JOBNET= ──┼ ┼─name── └ ┘──,LIST= ──┴ ┴─LAST─ └ ┘─name�─

�─ ──┬ ┬──────────────── ──┬ ┬────────────────── ─────────────────────� │ │┌ ┐─1��─ │ │┌ ┐─1───

└ ┘──,LVL= ──┴ ┴─nnn─ └ ┘──,SCHID= ──┴ ┴─nnn─

�─ ──┬ ┬──────────────────── ──┬ ┬──────────────────── ───────────────� │ │┌ ┐─�─────── │ │┌ ┐─J──────


�─ ──┬ ┬──────────────────── ──────────────────────────────────────�� │ │┌ ┐─ACTUAL─

└ ┘──,TYPE= ──┴ ┴─ALL────

242 Commands Guide

FSTRUC


FROMDefines the beginning date and time for the time interval to be forecast.

Default: Current date and time

Required: No


mmDefines the month (01 through 12). Leading zeros are required.

ddDefines the day (01 through 31). A leading zero is required if lessthan 10.

yyDefines the year.

hhmmDefines the time.



LISTSpecifies the option of listing the entire structure of the jobs or just the firstand last jobs.

Default: ALL

Required: No

ALLSpecifies the whole structure of the job is to be listed.

LASTSpecifies only the first and last jobs are to be listed.


FSTRUC

ExamplesFSTRUC,FROM=�1,SYS=PAYROLL,LIST=LAST

FSTRUC,FROM=�3,JOB=G4�1�,SCHID=2

Note: When using a generic job name, only those jobs meeting the criteriaentered and also having a schedule (or not triggered) are included.

FSTRUC Panel

� � FSTRUC,FROM=�518�5 FSTRUC DATE �5-15-�5 PAGE ��2

NETWORK STRUCTURE FOR CA-7 JOBSSTART TIME : �5-18-�5 AT 1528 HRS

LEV# JOB NAME SYS START DTTM END DTTM TRIGGERING JOB/DSN/SID --- T2LIB111............ SYSTBKUP �526�/1528 �526�/1548 :��1 ��1 T2TSOPAK.......... SYSTBKUP �5261/�343 �5261/�4�� T2LIB111 :��1 ��2 T2SYSTEM........ SYSTBKUP �5261/�34� �5261/�4�� T2TSOPAK :��1 ��3 T2LIB114...... SYSTBKUP �5261/�34� �5261/�4�� T2SYSTEM :��1 ��4 T2CATLG2.... SYSTBKUP �5261/�334 �5261/�4�� T2LIB114 :��1 ��5 T2LIB115.. SYSTBKUP �5261/�34� �5261/�4�� T2CATLG2 :��1 ��6 T2LIB119 SYSTBKUP �5261/�342 �5261/�4�� T2LIB115 :��1 --- T2LIB112............ SYSTBKUP �5261/1528 �5261/1549 :��1 ��1 T2LIB118.......... SYSTBKUP �5262/�34� �5262/�4�� T2LIB112 :��1 ��2 T2LIB113........ SYSTBKUP �5262/�345 �5262/�4�� T2LIB118 :��1 ��3 T2TMSBK1...... SYSTBKUP �5262/�35� �5262/�4�� T2LIB113 :��1 ��4 ROBDAILY.... SYSTBKUP �5262/�233 �5262/�4�� T2TMSBK1 :��1 --- T2LIB117............ SYSTBKUP �5262/1528 �5262/1549 :��1 ��1 T2LIB116.......... SYSTBKUP �5262/�341 �5262/�4�� T2LIB117 :��1 --- T2MVSPG2............ SYSTBKUP �5262/1528 �5262/1552 :��1

� �

244 Commands Guide

FTAPE

FTAPE

The FTAPE command provides a tape pull list for CPU jobs. Only the databaseis used for this forecast.


FTAPE

��──FTAPE─ ──,FROM=(mmddyy,hhmm) ──, ──┬ ┬──TO=(mmddyy,hhmm) ─────────�└ ┘──SPAN=hhhh ───────


└ ┘─NO──

�─ ──┬ ┬──────────────────────────────────── ───────────────────────� │ │┌ ┐─�───────────────────────



�─ ──┬ ┬───────────────────── ──┬ ┬────────────────── ────────────────� │ │┌ ┐─�───── │ │┌ ┐─�───

└ ┘──,JOBNET= ──┼ ┼─name── └ ┘──,SCHID= ──┴ ┴─nnn─ └ ┘─name�─

�─ ──┬ ┬──────────────────── ──┬ ┬──────────────────── ──────────────�� │ │┌ ┐─�─────── │ │┌ ┐─J──────



FROMDefines the beginning date and time for the time interval to be forecast.FROM is required.



ddDefines the day (01 through 31). Optional. If omitted, 01 isassumed. Leading zero is required.



FTAPE




TODefines the ending date and time for the time interval to be forecast. EitherTO or SPAN is required. If TO is omitted, SPAN must be specified.



ddDefines the day (01 through 31). Optional. If omitted, last day ofmonth is assumed. Leading zero is required.





SPANDefines the length of the time interval to be forecast. This value is addedto the FROM date and time-of-day to determine the ending date and time ofthe forecast time interval.



246 Commands Guide

FTAPE

ExamplesFTAPE,FROM=�2,TO=(�2�2,17��)

FTAPE,FROM=(�7�5�5,�8��),SPAN=48,SYS=PAYROLL

FTAPE,FROM=�5,SPAN=72,TRIG=JD

FTAPE Panel - Magnetic Tape Requirements

� � FTAPE,FROM=(�3�6,��),SPAN=8 FTAPE DATE �2-27-�5 PAGE ��2

TAPE PULL LIST FOR CA-7 JOBSPERIOD : �3-�6-�5 AT �� HRS TO �3-�6-�5 AT �8�� HRS

VOLSER ------------- DATASET NAME -------------- CREATED-ON DEV-CODE SEQJOBNAME SYSTEM START DTTM END DTTM SCHED# SID TRIGGERING JOB/DSN

�71�49 CA-7.LOGHIST.G�239V�� /�� 32��8��3 ��1DUSARS�1 SYSTEMA �5�65/24�� 5�66/�1�� SJ��44 ��1

�74684 CA-7.LOGARCH.G��4V�� /�� 32��8��3 ��1DUSARS�1 SYSTEMA �5�65/24�� 5�66/�1�� SJ��44 ��1

123456 CA-7.TAPE �5242/1�41 34��8��3 ��1DUSAZZ23 TESTGFRC �5�66/12�� 5�66/125� LEV��2 ��1 DUSAZZ13

98765� CA-7.TTAPE �5242/1�41 34��8��3 ��1DUSAZZ23 TESTGFRC �5�66/12�� 5�66/125� LEV��2 ��1 DUSAZZ13

SCRATCH ... APPROXIMATELY ��12 TAPES REQUIRED FOR OUTPUT DATASETS.

SFC1-�� REQUEST COMPLETED AT 15:28:�� on �5.�58� �


FWLP

FWLP

The FWLP command selects information from the Unicenter CA-7 databaseand queues for use as input for the Unicenter CA-7 WLP simulator andPROJECTION reports. This input supplies all critical information about theresource configurations and jobs scheduled for a specified time frame. The filecreated by FWLP consists of card-image, fixed format records to facilitateadditions, deletions, and updates for possible resource and job specificationchanges through a standard text editor (Unicenter CA-7, TSO, AdvantageCA-Roscoe, and so on).


FWLP

��──FWLP─ ──┬ ┬─────────────────── ─────────────────────────────────�└ ┘──,DRMODE= ──┬ ┬─YES─

└ ┘─NO──

�─ ──┬ ┬────────────────────────────── ──┬ ┬───────────────────── ────�└ ┘──,DRCLASS=(class1,...,class8) └ ┘──,FROM=(mmddyy,hhmm)

�─ ──┬ ┬─────────────────── ──┬ ┬────────────────────── ──────────────� └ ┘──, TO=(mmddyy,hhmm) │ │┌ ┐─NONE───

└ ┘──,DDNAME= ──┴ ┴─ddname─

�─ ──┬ ┬────────────────── ─────────────────────────────────────────� │ │┌ ┐─��─

└ ┘──,DEMAND= ──┴ ┴─nn─

�─ ──┬ ┬──────────────────────────────────── ───────────────────────� │ │┌ ┐─�───────────────────────



�─ ──┬ ┬───────────────────── ──┬ ┬──────────────────── ──────────────� │ │┌ ┐─�───── │ │┌ ┐─ALL──

└ ┘──,JOBNET= ──┼ ┼─name── └ ┘──,MAINID= ──┼ ┼──SYn ─└ ┘─name�─ └ ┘──/SYn

�─ ──┬ ┬──────────────────────────── ──┬ ┬────────────────── ─────────� │ │┌ ┐─�──────── │ │┌ ┐─�───

└ ┘──, ──┬ ┬──RESA= ──┴ ┴──UCC7Rxxx └ ┘──,SCHID= ──┴ ┴─nnn─ │ │┌ ┐─�────────

└ ┘──RESP= ──┴ ┴──UCC7Rxxx

�─ ──┬ ┬────────────────── ──┬ ┬─────────────────── ──────────────────� │ │┌ ┐─8──── │ │┌ ┐─�──────

└ ┘──,SPAN= ──┴ ┴─hhhh─ └ ┘──,SYS= ──┴ ┴─system─

�─ ──┬ ┬─────────────── ──┬ ┬──────────────────── ───────────────────�� │ │┌ ┐─J─ │ │┌ ┐─ACTUAL─

└ ┘──,TRIG= ──┴ ┴─N─ └ ┘──,TYPE= ──┴ ┴─ALL────

248 Commands Guide

FWLP

FROM=(mmddyy,hhmm)Defines the beginning date and time for the time frame to be generated forthe simulation. FROM is optional. If omitted, the default is current date andtime, and all current jobs are generated, including jobs currently in therequest, ready, and active queues. If the current date but not the currenttime is to be used, the format can be specified as (,hhmm). If FROM isspecified, the queue information is not included.

TO=(mmddyy,hhmm)Defines the ending date and time for the time frame to be generated. TO isoptional. If omitted, SPAN data is added to FROM data to calculate TO.(See “FWLP Notes” on page 252.) If the current date but not the currenttime is to be used, the format can be specified as (,hhmm).

DDNAMESpecifies the ddname in the Unicenter CA-7 execution JCL that defines thedata set that contains the data cards written as a result of the FWLPcommand.

Default: NONE

Required: No

NONESpecifies no data is to be written to a WLP data set. In this case, onlythe online portion of WLP is executed and only a Workload PlanningSummary report is generated.

ddnameDefines the ddname to which WLP information is written. (This namemust correspond to a DD statement in the Unicenter CA-7 onlineexecution JCL. It points to the same data set that is referenced as inputby the batch simulation execution of WLP. It must not reference aU7xxxxxx DD statement that is used to allocate a volume.)

DEMANDDefines the percentage of DEMAND work to be generated. This causesdummy job data to be generated on the output file (specified by DDNAME).Each dummy JOB statement has attributes representing average values ofthe actual JOB data statements created. The due-out times of these dummyjobs are spaced at equal intervals throughout the specified time frame.DEMAND is optional. If omitted, the default is 0. The value can be derivedfrom APA averages (see Job category graphs 20, 900, 1240, and so forth).

JOBDefines the jobs to be selected for simulation.

Default: *

Required: No

*Specifies all jobs are to be considered.


FWLP

jobnameDefines the job names to be considered for simulation. Job name maybe specific or generic.

(jobname1,jobname2,...,jobname10)Defines a list of job names. Up to 10 specific job names can bespecified.

JOBNETDefines the job network field as the selection criteria for the jobs to beforecast.

Default: *


Required: No

*Specifies all names.

nameDefines a specific name.

name*Defines a generic name terminated with an asterisk.

Note: If value contains blank, comma, or quote, it may not be possible tospecify the value through batch input.

MAINIDSpecifies the CPU as selection criteria for the jobs to be included in theWLP input data. If jobs input to the simulation impose CPU restrictions asspecified by MAINID, these jobs are included or excluded as indicated.MAINID is optional, but if used, one of the following is required.

ALLSpecifies MAINID is to be disregarded as a basis for job selection. Thisis the default.

SYnDefines the CPU where n is the Unicenter CA-7 system number.

/SYnSpecifies not this CPU.

RESASpecifies the initial resource picture module name to be used. Using RESAinstead of RESP causes FWLP to produce a resource (RES) datastatement each time it encounters scheduled changes in the WLBprocessing objectives criteria in the specified time frame. (The A indicatesascending.)

Default: *

Required: No

250 Commands Guide

FWLP

*Specifies that the initial resource picture for the simulation process isthe one currently in use within Unicenter CA-7.

UCC7RxxxSpecifies a Unicenter CA-7 WLB processing objectives definitionmodule, that exists on the Load library, to be referenced by a WLPbatch execution. (See Workload Balancing and PerformanceManagement in the Systems Programmer Guide.) This module isloaded during batch simulation processing to supply resourcespecifications. This module overrides the current module on the firstRES statement that is generated.

RESPSpecifies one resource picture module name to be used to generate a RESstatement in the data file. If RESP is specified instead of RESA, the moduleor default defined here is to be used throughout the simulation process.(The P indicates permanent.) Values are the same as described for RESA.

SCHIDDefines the schedule ID value as the selection criteria for jobs to beforecast.

Default: 0 (all schedule IDs)


Required: Only if job has no defined schedule

SPANDefines the time interval in hours, with a minimum value of 1 and amaximum value of 8784 (approximately one year). This value is added tothe FROM value to determine the ending date and time for the interval.SPAN is optional. If omitted and TO is also omitted, the default is 8 hours.(See “FWLP Notes” on page 252.)

SYSDefines system names as a selection criteria for the jobs to be selected forsimulation.

Default: *

Required: No

*Specifies all systems are to be considered.

systemDefines a system to be considered for simulation. System can bespecific or generic. If JOB=J*,SYS=S* is specified, only those jobswhose names start with J and which belong to systems with namesstarting with S are selected for the simulation.


FWLP

TRIGSpecifies whether the WLP simulator input data generated is to includejob-triggered jobs.

Default: J

Required: No

JSpecifies job-triggered jobs are to be included.

NSpecifies no job-triggered jobs are to be included.

TYPESpecifies whether the "don't schedule before/after" criteria defined on theDB.1 panel is to be honored when generating the data statements. (See“FWLP Notes” on page 252.)

Default: ACTUAL

Required: No

ACTUALSpecifies to honor "don't schedule before/after" criteria.

ALLSpecifies to ignore the "don't schedule before/after" criteria.

FWLP Notes

■ The TYPE parameter is particularly useful in bringing a new system intooperation. Jobs and tentative schedules can be entered into the UnicenterCA-7 database, before they are brought into a production scheduling status,by specifying a "don't schedule before" value. WLP can then be used tosimulate their impact on currently scheduled jobs by using the TYPE=ALLparameter. When the jobs are ready for production, they need not bereentered on the database. Rather, the "don't schedule before" value merelyhas to be prior to the production date.

■ Depending on the number of accesses to the Unicenter CA-7 database andthe requested time span, the FWLP command can affect the performance ofUnicenter CA-7. Large time span requests on FWLP should be done atslack time or in smaller intervals to be concatenated as input to the batchWLP run. (Reference the FROM, TO, and SPAN fields.)

252 Commands Guide

FWLP

FWLP Output

The output resulting from the online FWLP command consists of the following:

■ Online Workload Planning Summary panel

■ Data Card file

The online Workload Planning Summary report provides a summary of the datagenerated by the FWLP command.

Workload Planning Summary Report

� �FWLP DATE �1-�1-�5 PAGE ��1

�� W O R K L O A D P L A N N I N G S U M M A R Y ��

PERIOD . �1-�1-�5 AT �� HRS �1-�1-�5 AT �8�� HRS

TOT INIT TP1 TP2 CPUJOB HRS HRS HRS MIN

WLP �7�2 ��25.1� ��.�� .�� 68.1�

RESTART ACTIVITY ��1 ��.1� ��.�� .�� .5�

DEMAND ACTIVITY �� .�� .�� .�� .��

� T O T A L S � ��7�3 ��25.2� ��.�� .�� 68.6��


PERIODIdentifies the starting and ending date and time of the time frame coveredby this FWLP transaction.

Identifies summary figures for this FWLP transaction, as follows:

TOT JOBIdentifies the total number of jobs scheduled during the time span.

INIT HRSIdentifies the total hours of initiator time.

TP1 HRSIdentifies the total hours of TYPE1 tape drive usage for the time span.

TP2 HRSIdentifies the total hours of TYPE2 tape drive usage for the time span.

CPU MINIdentifies the total minutes of CPU time required for the jobs, taken from theweighted average kept for each job in the Unicenter CA-7 database.


FWLP

WLPIdentifies summary figures for regularly scheduled jobs for the time spanrequested.

RESTART ACTIVITYIdentifies estimated resource requirements calculated from individual jobrerun rate frequencies and average run requirements. These valuesrepresent the statistical average amount of restart activity to be expected.They do not necessarily represent the amount of restart activity reflected inthe batch WLP Projection reports, however, since batch WLP allows theuser to specify alternate ways of estimating the restart requirements.

DEMAND ACTIVITYIdentifies estimated percent requirements for DEMAND jobs. Values are apercentage of the total WLP jobs for this FWLP command. The percentagecorresponds with the value of the DEMAND parameter of FWLP.

TOTALSIdentifies summary figures for this FWLP command, including regularlyscheduled jobs, restarts and demanded jobs.

254 Commands Guide

GRAPHc

GRAPHc

The GRAPHc line command requests graphs. It is available as an alternativeto the APA Menu and prompt panels on “APA” on page 136. The graphs aredivided into five categories. Each category can be invoked independentlythrough use of one of the two following top line command formats:

This command has the following formats:

GRAPHc

��─ ──GRAPHc ──,ID= ──┬ ┬─nnnn─────── ──┬ ┬─────────────────────── ─────�│ │┌ ┐─,── └ ┘──, ──┬ ┬──FROM=mmddyy ───└ ┘──( ───� ┴nnnn ) ├ ┤──TO=mmddyy ─────

├ ┤──SCALE=nnnnnnnn├ ┤──DIV1=nnnnnnnn ─└ ┘──DIV2=nnnnnnnn ─

�─ ──┬ ┬─────────────────── ───────────────────────────────────────��└ ┘──,GLINE= ──┬ ┬─PRIM─

├ ┤─SCND─ └ ┘─CALC─

or

GRAPHc

��─ ──GRAPHc ──,LIST= ──┬ ┬─HELP─ ───────────────────────────────────�� ├ ┤─DETL─ └ ┘─ALL──

cSpecifies the graph category. Value can be one of the following:

DDatabase statistics

JJob statistics

NNetwork statistics

RReport statistics

SSystem statistics


GRAPHc

ID=nnnn|(nnnn,nnnn,...,nnnn)Specifies the graphs to be displayed where nnnn is the four-digit graphidentification number as listed in the graph directory. Leading zeros are notrequired. Up to 10 such numbers can be specified. Each graph identificationnumber must be defined in the appropriate graph definition table. Thisparameter is required unless the LIST format of the command is used.

FROM=mmddyyDefines the beginning date to start displaying statistical data. Value mustnot be less than the current date minus two years, nor greater than thecurrent date. When only the month is entered, the default is the first of themonth specified and the current year. Optional; if omitted, the current dateis assumed.

TO=mmddyyDefines the ending date, in the format mmddyy, to end displaying statisticaldata. Value must be greater than or equal to the date specified in FROMand not greater than the current date. When only the month is entered, thedefault is the last day of the month specified and the current year. Optional;if omitted, the current date is assumed.

SCALE=nnnnnnnTemporarily overrides the default scale value defined for the graph ID beingdisplayed. This value contains up to seven digits and does not affect theactual numbers to be displayed, only the scale numbers and the length ofthe graph line. This parameter is optional.

DIV1=nnnnnnnTemporarily overrides the default division factor for the primary counter ofthe graph being displayed (seven digits maximum). This parameter isoptional.

DIV2=nnnnnnnTemporarily overrides the default division factor for the secondary counterof the graph being displayed. This keyword is valid only for comparisongraphs (seven digits maximum). This parameter is optional.

GLINEThis keyword is optional. It temporarily overrides the predefined counterused on the graph line. The following are the possible values:

PRIMSpecifies to use the primary counter.

SCNDSpecifies to use the secondary counter (comparison graphs only).

CALCSpecifies to use the calculated value (comparison graphs only).

256 Commands Guide

GRAPHc

LISTThis keyword is optional, and if specified, must be the only parameter listed.The following are the possible values:

HELPDisplays the graph directory.

DETLDisplays the values chosen for all parameters used in defining eachgraph in the category specified. For an example of the LIST=DETLfunction, see LIST=DETL Function Example on page 258. (For theavailable values of these parameters, see Changing Graph Definitionsin the Systems Programmer Guide. For a complete listing of thegraphs available through the Automated Performance Analysis (APA)facility, see the Reports Guide

ALLDisplays the current counters of all graphs in the category specified forthat particular moment. Each graph is listed separately with individualtotals and complete totals. For an example of a partial listing of theLIST=ALL function, see LIST=ALL Function Example on page 258.


GRAPHc

Examples

LIST=DETL Function

� �GRAPHS,LIST=DETL

�� COMPUTER ASSOCIATES INTERNATIONAL, INC. ��...GRAPH DETAIL DEFINITION SCREEN... PAGE ��1

DESCRIPTION / ID TYPE TOTALS SCALE GRAPH CALCULATION DIV1 DIV2

CA-7 ACTIVE TIME IN MINUTES ��1� SINGLE NO ��3� PRIM RUNNING TOTAL ��6��

CA-7 UP TIME VS. OS WAIT TIME IN SECONDS��2� COMPARISON YES ��2 CALC PERCENTAGE ��1�� 1��

TOTAL OS WAIT TIME IN MINUTES ��3� SINGLE NO ��3� PRIM RUNNING TOTAL ��6��

NUMBER OF WRITES TO STATISTICS FILE ��4� SINGLE NO ��25 PRIM RUNNING TOTAL ��1

COMM. TASK WAIT TIME IN MINUTES ��5� SINGLE NO ��3� PRIM RUNNING TOTAL ��6��

� �

LIST=ALL Function

� �GRAPHS,LIST=ALL

�� COMPUTER ASSOCIATES INTERNATIONAL, INC. ��.....CURRENT STATUS - 12/22/yy..... PAGE ��1

��1� CA-7 ACTIVE TIME IN MINUTES 748 748��2� CA-7 UP TIME VS. OS WAIT TIME IN SECONDS 44883 4483� 99.88��3� TOTAL OS WAIT TIME IN MINUTES 747 747��4� NUMBER OF WRITES TO STATISTICS FILE 744 744��5� COMM. TASK WAIT TIME IN MINUTES 745 745��6� CA-7 UP TIME VS. COMM. TASK ACTIVE TIME IN SE 44883 2�3 �.45��7� NUMBER OF LOGONS 13 13��8� SECURITY VIOLATIONS � ��9� TERMINAL ERRORS � ��1�� NUMBER OF RESPONSES GREATER THAN 1� MINUTES � ��11� NUMBER OF RESPONSES GREATER THAN 6� SECONDS � ��12� ACCUMULATED RESPONSE TIME IN MINUTES 3 3�13� TOTAL NO. OF TRANSACTIONS PROCESSED 91 91�14� AVERAGE RESPONSE TIME PER TRANSACTION IN 1/1� SECO 1831 91 21.�4�15� AVERAGE NUMBER OF TRANSACTIONS PER LOGON 91 13 6.69�16� NUMBER OF RESPONSES LESS THAN 3 SECONDS 64 64�17� PERCENTAGE OF TRANSACTIONS WITH RESPONSE TIME LESS 91 64 73.56

� �

258 Commands Guide

GRAPHc

Usage Notes

The graph number with the category request specific reports. To request JOBcategory 0370, for example, a command is entered in this format:

GRAPHJ,ID=37�,FROM=mmddyy

Where mmddyy is the beginning of the time period to be reported in month, dayand year format. Current time is the default period ending time for the graph.This gives up-to-the-second information.

Up to 10 graphs can be requested with a single command. Whenever multiplesare requested, the graph selection numbers are separated by commas with theentire sequence of numbers enclosed in parentheses. If current time is not thedesired period ending time, a TO=mmddyy option can be specified.

For example:

GRAPHS,ID=(1�,2�,7�,13�,15�),FROM=�1�1�5,TO=�131�5

would display System graphs 0010, 0020, 0070, 0130, and 0150 with statisticscaptured from 01/01/05 to 01/31/05.

You can find graph definitions in the Reports Guide.


HELP

HELP

The HELP facility provides a quick means of obtaining tutorials about theUnicenter CA-7 applications and commands.

This facility is informational only with no direct effect on the Unicenter CA-7system or its operation.

HELP Panel

Online HELP tutorial information is available through the HELP panel.

CA-7 Online Tutorial

� � --------------------------- CA-7 ONLINE TUTORIAL ---------------------------FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

INDEX: (Y = INDEX OF ALL COMMANDS)

APPLICATION: (VALUE FROM FOLLOWING LIST OR SPECIFIC 4 CHAR NAME)1 - GENERAL INQUIRY 6 - RESTARTING A JOB 11 - MGMT GRAPHS2 - QUEUE MAINT 7 - DATA BASE MAINT 12 - PERSONAL SCHED3 - QUEUE MGMT/POSTING 8 - DATABASE ANALYZE 13 - VRM MAINT4 - SYSTEM COMMANDS 9 - SCHED RESOLUTION 14 - ARF5 - UTILITIES 1� - FORECASTING

COMMAND: (SPECIFIC COMMAND NAME, UP TO 8 CHARACTERS)FORMAT: (Y = SAMPLE FORMAT)EXAMPLE: (Y = COMMAND EXAMPLE)GENERAL: (Y = GENERAL DISCUSSION)DETAIL: (Y = DETAILED EXPLANATION)

PROGRAM: HLPM MSG-INDX: �� -- HELP -- yy.137 / �9:51:38MESSAGE: ENTER VALUES, TRANSFER OR ENTER A COMMAND on THE TOP LINE

� �

To display, enter:

■ HELP as a top line command.

■ HELP as the FUNCTION value on any other menu or formatted input panel.

To exit:

■ Press PF3 to return to the HELP panel.

■ Enter a top line command.

■ Change the command shown to any other batch format HELP option.

■ Replace the command shown with EXIT to return to the HELP panel.

260 Commands Guide

HELP


FUNCTIONThis field is only used to transfer to some other menu or some otherformatted panel function that is only offered on some other menu. Totransfer to some other panel, enter the name of the desired panel.

INDEXEnter Y to display an index listing of all commands. The display includes:

■ Names of all commands

■ Application name to which each command belongs

■ Brief description of each command's purpose

If used, remaining fields on this panel are ignored. Leave blank ifAPPLICATION or COMMAND are used.

APPLICATIONThis field is used to display information about a specific Unicenter CA-7application.

Numeric value from the list on the panel can be entered or, if alreadyknown, the specific four character application name can be entered.

If used, the remaining fields on the panel are ignored. Leave blank if INDEXor COMMAND are used.

The display includes:

■ General discussion of the application

■ List of all available commands in the application with a short descriptionof each command

■ Example of the format of each command

COMMANDThis field is used to display information about a specific command. To use,enter the name of the command just as it would be entered on the top line(for example, LJOB, /MSG).

This field is ignored if INDEX or APPLICATION are used.

If all HELP information for that command is wanted, leave the followingfields blank. The display includes all of the parts that can be individuallyselected with the following fields. Use the following fields to display onlyselected portions of HELP information. Y in all of them displays the sameinformation as if none of them were selected.


HELP

FORMATEnter Y to display a sample format for the command.

EXAMPLEEnter Y to display examples of the command.

GENERALEnter Y to display a general discussion of the command and its purpose.

DETAILEnter Y to display a detailed discussion of each command keyword.

Usage Notes

To access HELP through batch processing:

■ Issue the HELP command or

■ Issue 'INDEX', an application name (FOR0, SDM0, and so on), or thecommand for which HELP is needed.

262 Commands Guide

HOLD

HOLD

The HOLD command interrupts the normal scheduling progress by holding theforward movement of a job. It can also be used to hold the contents of an entirequeue. This function is available on the QM.1, QM.6, and QM.7 panels with aFILL value of H. Depending on the timing and whether there are any otherpredecessor situations, this can sometimes be accomplished with the QM.3panel.


HOLD

��──HOLD─ ──┬ ┬──────────────────────────── ───────────────────────��└ ┘──, ──┬ ┬──JOB= ──┬ ┬─jobname───

│ │├ ┤─jobnumber─ │ │└ ┘─refnumber─

└ ┘──Q= ──┬ ┬─REQ─ ──────── └ ┘─RDY─

JOBDefines the individual job or workstation network to be held. JOB must beomitted if Q is specified.

Required: Yes (unless the Q parameter is used)

jobnameDefines the job name of the CPU job to be held.


jobnumberDefines the job number of the CPU job to be held.

refnumberDefines the value for a workstation network task. It must be entered asthe Unicenter CA-7 assigned reference number in the format nnnnrrs.

nnnnDefines the Unicenter CA-7 job number.

rrDefines the relative sequence of the network in relation to othernetworks associated with the job. For input workstation networks,the value is 00.

sDefines the position of the station within the network. The firststation would be position 1.


HOLD

QSpecifies the contents of an entire queue are to be held. Q must be omittedif JOB is specified.

Required: Yes (unless the JOB parameter is used)

REQSpecifies to hold all jobs currently in the request queue.

RDYSpecifies to hold all jobs currently in the ready queue.

Usage Notes

Jobs can be held individually in the request or ready queues.

When a HOLD is issued by job name, all jobs and workstation networks withthat name are held. There can be multiple jobs with the same name.

A specific input workstation network can be held in the preprocess queue. Alloutput workstation networks associated with a specific (CPU) job name orUnicenter CA-7 job number can be held in the postprocess queue.

Workstation networks are held only if a station is found logged in but not loggedout.

A HOLD command issued for an entire queue affects only those jobs in thequeue at the time the command is processed. Jobs entering the queue after theHOLD are not placed in hold status unless done individually.

Jobs can also be moved into the request queue in HOLD status when theDEMANDH, RUNH, or LOADH commands are used.

ExamplesHOLD,JOB=CA7JOB9

HOLD,JOB=163

HOLD,Q=REQ

HOLD,JOB=��78�12

264 Commands Guide

IN

IN

The IN command indicates the beginning of a workstation task.

Each workstation task has a unique reference number. Unicenter CA-7generates this reference number each time the network associated with theworkstation enters a Unicenter CA-7 queue. This number can be obtained byusing the LPRE or LPOST commands. The number is then used to log in thestart of the workstation tasks. This indicates that the task is in-process andautomatically logs the start time for the task being performed.

This function is available as the LOGIN or FORCE LOGIN options on the QM.6and QM.7 panels.


IN

��──IN─ ──,REF= ──┬ ┬─nnnnrrs────── ──┬ ┬──────────── ────────────────�� │ │┌ ┐─,──── └ ┘──,FORCE=YES └ ┘──( ───� ┴nnnrrs )

REFDefines the workstation tasks to be logged in.

Required: Yes

nnnnrrsDefines a single workstation task reference number.

Note: Workstation task reference numbers can be obtained by usingan LPRE or LPOST command.

nnnnDefines the Unicenter CA-7 job number. (Leading zeros can beomitted.)

rrDefines the relative sequence of the network in relation to othernetworks associated with the job. For input workstation networks,the value is 00. (Leading zeros cannot be omitted.)

sDefines the relative position of the station within the network. Thefirst station is position 1.


IN

(nnnnrrs,...,nnnnrrs)Defines up to 10 workstation task reference numbers. Must be enclosedby parentheses.


FORCEAllows the logging in of an output network prior to completion of the CPUjob to which it is associated. If used, the value must be entered as shown.FORCE=YES only has meaning for output networks.

Required: No

Input Networks

All input network activities are placed in the preprocess queue for control andtracking. Either of two events can cause the scheduling of workstation activity:

■ The normal, scheduled processing time arrived and schedule scanautomatically placed the network in the preprocess queue, or

■ The input network was manually demanded (see “DMDNW” on page 177).

Each workstation task and its associated network are assigned a uniqueUnicenter CA-7 reference number when the network is placed in the preprocessqueue. The unique reference number must be used by each workstation,except the first in the network, to log the start and completion of work.

Workstations within a network must log in and log out in the workstationsequence defined to Unicenter CA-7. Only one workstation at a time can belogged in for a given network. A single workstation can be logged in for morethan one network at a time. Each workstation must log in before it can log out.A workstation can not log in until the preceding workstation in the network haslogged out.

A workstation can be prompted for an activity that has already completed ifUnicenter CA-7 was not properly notified of the completion. In response to theprompt, LOGIN and LOGOUT commands should be used to notify UnicenterCA-7 of task completion. You can use the IN command instead of LOGIN. Youcan use the IO command to log in and log out with a single command. Formore information, see “IO” on page 271.

If the same station is defined in the network more than once, the LOGIN andLOGOUT commands should not be used.

266 Commands Guide

IN

Output Networks

When a job is placed in the request queue (by demand or automatic schedule),all output networks defined for that job's output (using DB.3.4 panel) are placedin the postprocess queue.

All output networks connected to the job (through DB.3.4 panel) are assignedthe same Unicenter CA-7 job number used to identify the job in the requestqueue. This job number must be used by each workstation, except the first, tolog the start and completion of its activity. Since multiple output networks canexist for a single job (and job number), network information, SUBID information,or both must also be used when logging starts or an activity completes.

Workstations within a network must log in and log out in their definedsequence. Only one workstation at a time can be logged in for a given network.A single workstation can be logged in to more than one network at the sametime. Each workstation must log in before it can log out. A workstation cannotlog in until the preceding workstation in the network has logged out (for thatactivity).

A workstation can be prompted for an activity that has already been completedif Unicenter CA-7 was not properly notified of the completion. LOGIN andLOGOUT commands should be used in response to the prompt to notifyUnicenter CA-7 of task completion. You can use the IN Command Response inplace of LOGIN. For more information, see “IN Command Response” onpage 268. The IN top line command is used to indicate the beginning of aworkstation task. The IO command in this chapter can be used to log in and logout with a single command.

If the same station is defined in a network more than once, LOGIN andLOGOUT should not be used.


IN

IN Command Response

The following information is provided in response to the IN command:

■ Original IN command

■ Associated job name

■ Network name

■ SUBID

■ Station name

■ Remarks indicating disposition taken for the IN command

IN Command Response Example

� �IN,REF=��1��1REF JOB NETWORK SUBID STATION -------------REMARKS------ -------

��1��1 DMD#��1 TESTNET STATION1 DOTM=9��89/1532

SPOC-�� REQUEST COMPLETED AT 14:57:57 on YY.DDD.

� �

Remarks: Following is a list of possible IN command remarks. Each isdescribed in detail, followed by the required action to be taken whereapplicable. These appear on the panel under the heading REMARKS.

ALREADY LOGGED IN

Reason: The station specified by the reference number is already logged in.

Action: If the reference number on the original input is correct, no action is required. Ifnot, correct and reenter the IN request.

DOTM=*RUSH*

Reason: The first station has been successfully logged in. The due-out time for thestation indicates the work is critical and should be done as soon as possible.

Action: Process the work as soon as possible, and then log out.

DOTM=yyddd/hhmm

Reason: The first station has been successfully logged in and the due-out time for thatstation is printed. yyddd is a variable of five characters representing the due-out date.hhmm the due-out time-of-day.

Action: None.

268 Commands Guide

IN

FROM xxx...x,DOTM=*RUSH*

Reason: The next stations has been successfully logged in for work that was lasthandled by station xxx...x. The due-out time for the stations indicates the work is criticaland should be done as soon as possible.

Action: Process the work as soon as possible, and then log out.

FROM xxx...x,DOTM=yyddd/hhmm

Reason: The next stations has been successfully logged in for work that was lasthandled by station xxx...x. The preceding station and the due-out time for the currentstation are indicated.

Action: Perform the task as scheduled.

JOB HELD

Reason: The task specified by the reference number is in hold status.

Action: Determine why the task is being held. After the task is released, reenter therequest.

JOB NOT COMPLETE

Reason: An attempt was made to log in a postprocess station before the CPU jobcompleted.

Action: Reenter the IN request after CPU execution has completed or specifyFORCE=YES on the IN transaction.

PREV STATION NOT COMPLETE

Reason: An attempt was made to log in a station when the preceding station in thenetwork was not logged out.

Action: If the IN request is valid, determine why the previous station is not logged out. Ifwork at that station is complete, log it out and then reenter the IN request.

Q ANALYSIS INCOMPLETE

Reason: Unicenter CA-7 is not finished with a previous activity using the requestedreference number's queue record.

Action: Wait a few moments then reenter the request. If the message persists, contactthe Unicenter CA-7 coordinator in your data center.

REF NUMBER NOT FOUND

Reason: The requested reference number was not found in the queue. Unicenter CA-7attempts to fill in the job, network and SUBID information if possible.

Action: Determine the correct reference number and reenter the IN request.


IN

ExamplesIN,REF=��11�11

Login workstation task 0011011 referenced by Unicenter CA-7 job 0011,network sequence 01 and station position 1.

IN,REF=11�11

Same as above, only leading zeros of job number have been omitted.

IN,REF=(9�32,11�12)

Login workstation task 0009032 and 0011012.

IN,REF=11�11,FORCE=YES

Login workstation task 0011011 even if the CPU job to which it is associatedhas not completed.

270 Commands Guide

IO

IO

The IO command can be used in place of and as a combination of the IN andOUT commands. It results in simultaneous log in and log out of one or moreworkstation tasks. The IO command uses reference numbers to identify eachworkstation.


IO

��──IO─ ──,REF= ──┬ ┬─nnnnrrs────── ──┬ ┬──────────── ────────────────�� │ │┌ ┐─,──── └ ┘──,FORCE=YES └ ┘──( ───� ┴nnnrrs )

REFDefines the workstation tasks to be both logged in and logged out.

Required: Yes

nnnnrrsDefines a single workstation task reference number.


Note: Workstation task reference numbers can be obtained by usingan LPRE or LPOST command.

nnnnDefines the Unicenter CA-7 job number (leading zeros can beomitted).

rrDefines the relative sequence of the network in relation to othernetworks associated with the job. For input workstation networks,the value is 00. Leading zeros cannot be omitted.

sDefines the relative position of the station within the network. Thefirst station is position 1.

(nnnnrrs,...,nnnnrrs)Defines up to 10 workstation task reference numbers. Must be enclosedin parentheses.

FORCEAllows the logging of an output network prior to completion of the CPU jobto which it is associated. If used, the value must be entered as shown.FORCE=YES only has meaning for output networks.

Required: No


IO

IO Command Response

Unicenter CA-7 responds to each IO command by providing the followinginformation:

■ Original IO command


■ Network name

■ SUBID

■ Station name

■ Remarks indicating the disposition taken for the IO command

IO Command Response Example

� �IO,REF=��1��1REF JOB NETWORK SUBID STATION -------------REMARKS------ -------

��1��1 DMD#��1 TESTNET STATION1 NETWORK COMPLETE

SPOC-�� REQUEST COMPLETED AT 15:�7:3� on YY.DDD.� �

Remarks: Following is a list of possible IO command remarks in addition tothose discussed under “IN Command Response” on page 268. Each isdescribed in detail, followed by the required action to be taken whereapplicable. These appear on the panel under the heading REMARKS.

ALREADY LOGGED OUT

Reason: The station specified by the reference number has already been logged out.

Action: If the reference number was specified incorrectly, correct and reenter. If correct,no further action should be necessary.

JOB PURGED

Reason: The last station in the postprocess queue was successfully logged out. All otheroutput networks for the job are complete. Therefore, job processing is considered to becomplete.

Action: For information only.

NETWORK COMPLETE

Reason: The station has been successfully logged out. This was the last station definedin the network.

Action: For information only.

272 Commands Guide

IO

SEND TO xxx...x,DLTM=*RUSH*

Reason: The station has been successfully logged out. The work has been flagged ascritical and should be sent to the next station (xxx...x) as soon as possible. (Not returnedfor last station in network.)

Action: Forward the work to the indicated station as soon as possible.

SEND TO xxx...x,DLTM=yyddd/hhmm

Reason: The specified station has been successfully logged out. The deadline (start)time-of-day for the next station in the network (xxx...x) is indicated. (Not returned for laststation in network.)

Action: Make sure the work is forwarded to the next station.

ExamplesIO,REF=��11�11

IO,REF=(9�32,11�12)

IO,REF=11�11,FORCE=YES


JCLOVRD

JCLOVRD

The JCLOVRD command establishes or satisfies JCL override requirements.This command is primarily used when the job does not have a permanent JCLoverride requirement assigned. The job for which the JCL override is beingestablished (or satisfied) must be in the request queue.

If you are using Unicenter CA-7 to insert IBM WLM scheduling environmentkeywords on JOB statements, you can use the JCLOVRD command tosuppress or allow SCHENV= keyword insertion.

This function is available as the J value for FILL FUNCTION on the QM.1panel. It can also be accomplished with the QM.2 and QM.3 panels.


JCLOVRD

��──JCLOVRD─ ──,JOB=jobnumber ──,SET= ──┬ ┬─ON──── ──────────────────�� ├ ┤─OFF─── ├ ┤─WLM─── └ ┘─NOWLM─

JOBDefines the Unicenter CA-7 job number of the job in the request queue forwhich the override requirement is to be established or removed.


Required: Yes

SETSpecifies to Establish or satisfy JCL override requirements. When a job failswith a JCL error, the JCL override requirement is automatically set to ONwhen the job returns to the request queue. The JCL override must be set toOFF before the job can be submitted again.

Required: Yes

ONEstablishes a JCL override requirement for the specified job. TheSET=ON option is used for jobs in the request queue to indicate that anoverride is needed before execution is to occur.

OFFSatisfies a JCL override requirement for the specified job. TheSET=OFF option indicates that a previously defined need (requirement)for overrides has been satisfied and execution can be safely attempted.When a JCL override requirement is set to OFF, that requirement nolonger appears on a requirements list for the job. When a REPL is donefrom the QM.5 panel, the JCL override requirement is automatically setto OFF.

274 Commands Guide

JCLOVRD

WLMSets job to allow insertion of SCHENV= keyword on the JOB statementat submission time if the scheduling environment insertion feature isactivated and there is a scheduling Environment VRM definitionattached to the job (or SCHENV global default).

NOWLMSets job to suppress the insertion of a SCHENV= keyword on the JOBstatement at submission time even if one would normally be associatedwith the job.

This option can be used if the validation of an associated IBM WLMscheduling environment has failed causing the job to be requeued (seeBrowse message SSM0-42). Setting the NOWLM option will allow thejob to be submitted without SCHENV= keyword insertion.

Note: This option will not suppress user-coded SCHENV= keywords inthe JCL. Such keywords must be manually removed from the QJCLprior to releasing the job for submission.

Usage Notes

When REPL is done from the QM.5 panel, the JCL override requirement is setto OFF.

For other related override functions, see the DB.1 panel JCL-OVRD field, the#JCL control statement, scheduled override (#JI, #JO, #XI and #XO) controlstatements, the QM.5 panel REPL function, and the Unicenter CA-7 EditorSAVE command.

ExamplesJCLOVRD,JOB=163,SET=ON

JCLOVRD,JOB=163,SET=OFF


LACT

LACT

The LACT command provides general status information about CPU jobs in theactive queue. Parameters allow you to indicate which job or group of jobs isdesired, what information is to be reviewed, and the sequence of displayeddata. The active queue only contains information about jobs that have startedexecuting on a CPU. Other commands are also available to display other typesof data for CPU jobs that reside in the active queue.


LACT

��──LACT─ ──┬ ┬────────────────────── ──┬ ┬─────────────────── ───────� │ │┌ ┐─�───── │ │┌ ┐─�───

└ ┘──,DRCLASS= ──┼ ┼─@ANY── └ ┘──,DRMODE= ──┼ ┼─YES─ └ ┘─@NONE─ └ ┘─NO──

�─ ──┬ ┬──────────────────────────── ──┬ ┬────────────── ─────────────�│ │┌ ┐─�───────── └ ┘──,LIST=option└ ┘── ─── ───,JOB= ──┼ ┼─jobname───

├ ┤─jobname�── └ ┘─jobnumber─

�─ ──┬ ┬────────────────── ──┬ ┬──────────────────────────────── ─────�│ │┌ ┐─��─ └ ┘──,SEG= ──┬ ┬─xxxxxxxx────────────└ ┘──,SCHID= ──┴ ┴─nnn─ └ ┘──(xxxxxxxx,yyyyyyyy)

�─ ──┬ ┬───────────────────── ──┬ ┬──────────── ──────────────────────�│ │┌ ┐─NATV───── └ ┘──,ST=option└ ┘──,SEQ= ──┴ ┴─sequence─

�─ ──┬ ┬──────────────────────── ──────────────────────────────────�� │ │┌ ┐─�───────────

└ ┘──,SYS= ──┼ ┼─systemname── └ ┘─systemname�─

276 Commands Guide

LACT

DRCLASSSpecifies to select only jobs with the specified disaster recovery class. Thevalue must be a specific DRCLASS or one of the following reserved names.

Default: *

Required: No

*Specifies all jobs.

@ANYSpecifies that jobs with any DRCLASS should be selected.

@NONESpecifies that jobs with no DRCLASS should be selected.

DRMODESpecifies the class of jobs to select.

Default: *

Required: No


YESSpecifies to select only jobs that entered the request queue whileUnicenter CA-7 was in Disaster Recovery mode.

NOSpecifies to select only jobs that entered the request queue whileUnicenter CA-7 was not in Disaster Recovery mode.

JOBDefines the jobs whose active queue information is to be listed.

Default: *

Required: No




jobname*Defines a generic job name.

Limits: 1 to 7 alphanumeric characters terminated with an asterisk


LACT

jobnumberDefines a specific Unicenter CA-7 job number.


LISTSpecifies options for the amount of active queue information to bedisplayed.

Required: No

ALLSpecifies all data related to the jobs being displayed.

JCLSpecifies JCL information only.

Depending on the security options selected for your installation, thefollowing values may be concealed in the display:

JOB statement USER keywordJOB statement GROUP keywordJOB statement PASSWORD keyword

//*LOGONID statement //*PASSWORD statement //*JOBFROM statement

PROSSpecifies documentation information only.

QSpecifies job data only.

RQMTSpecifies all requirements information only.

STATUSSpecifies VRM and ARF information only.

When LIST is not specified, a default display consisting of a singledescription line for each queue record is listed. However, when a specificjob is requested by the JOB parameter, the default is LIST=STATUS andVRM and ARF information for the job are listed. If SEG is specified, thedefault is LIST=PROS.

SCHIDDefines the schedule ID for which information is to be selected.


Required: No

278 Commands Guide

LACT

SEGDefines a segment and subsegment of documentation to be listed. If asubsegment, use the form (xxxxxxxx,yyyyyyyy). SEG and subsegments areboth optional.


Required: No

xxxxxxxxDefines the name of the segment.

(xxxxxxxx,yyyyyyyy)Defines the names of a segment (xxxxxxxx) and subsegment(yyyyyyyy) in up to eight characters each, enclosed in parentheses andseparated by a comma.

SEQSpecifiies the display sequence of the desired information.

Default: NATV

Required: No

NATVSpecifies native sequence (the order in which it is in the queue).

CA7Specifies Unicenter CA-7 job number sequence.

DLTMSpecifies deadline time sequence.

DOTMSpecifies due-out time sequence.

JOBSpecifies job name sequence.


LACT

STIndicates a selection option used to determine which jobs are listed.

Required: No

ABNDIndicates jobs abnormally terminated due to abend, condition codefailure, or JCL error.

CBADIndicates jobs that are flagged due to condition code failure.

HELDIndicates jobs in HOLD status.

JCLOIndicates jobs with an outstanding JCL override or verificationrequirement.

JCLRIndicates jobs that have failed due to JCL error.

LATEIndicates jobs that are late.

MANVIndicates jobs with an outstanding manual verification requirement.

NOIDIndicates jobs flagged due to undetermined or invalid security ID duringsubmission.

REQUIndicates jobs that have been requeued manually.

RSTRIndicates jobs in restart status.

RTRYIndicates jobs flagged for retry due to JCL attach failures related todynamic allocation.

SKELIndicates jobs in skeleton status due to JCL attach failures.

SUBMIndicates jobs that have been submitted to a host CPU.

280 Commands Guide

LACT

SYSIdentifies the application system names whose active queue information isto be listed.

Default: *

Required: No

*Specifies all application system names.

systemnameDefines a specific application system name.


systemname*Defines a generic application system name.



LACT

ExamplesLACT,SEQ=JOB

LACT,JOB=G4�1�,SEQ=JOB

� � LACT DATE=YY.DDD PAGE ��1

JOB QUEUE CA-7 -DAY(DDD) AND TIME(HHMM)-- CPU SCH ENTRY MSTR JOBNAME NAME NUM DEADLINE SUB/START DUE-OUT SPEC/RUN ID MODE REQ STATUS

CA7BTI�1 ACT ��25 2�3/1245 �NONE� 2�3/1245 ALL-IPO1 ��1 DEMD ��

SLIF-�� REQUEST COMPLETED AT 11:59:18 on YY.DDD� �


JOB NAMEIdentifies the name of the job as defined in the database. See NAME fieldon the DB.1 panel.

QUEUE NAMEIdentifies the queue where this job record currently resides. Values areREQ for request queue, RDY for ready queue, and ACT for active queue.

CA-7 NUMIdentifies the Unicenter CA-7 assigned job number.

DEADLINE DAY AND TIMEIdentifies a calculated time by which this job should be active on the CPUto be completed by the due-out time.

SUB START DAY AND TIMEFor a job in the request queue this is the time of a submit time requirement.If there is a value for a job in the ready queue, then this is the time that theJCL was written to the submit data set or internal reader. Until the first SMFstep termination record is received, this field is *NONE* for a job in theactive queue.

DUE OUT DAY AND TIMEIdentifies the due-out time for this job.

CPU SPEC RUNThe SPEC value is what CPU this job should be submitted to (see MAINIDfield on DB.1 panel). The RUN value is what CPU the job has beensubmitted to.

SCH IDIdentifies the schedule ID assigned when this job was brought into therequest queue.

282 Commands Guide

LACT

ENTRY MODEIdentifies how the job was brought into the queue. The possible values arethe following:

ARFJIdentifies a ARF recovery job.

AUTOIdentifies a triggered job.

DEMDIdentifies a demanded job.

EXTLIdentifies a job submitted external to Unicenter CA-7.

LOADIdentifies a job record to be loaded (brought in by LOAD command).

PSIdentifies a job submitted by Personal Scheduling System.

RPETIdentifies a repeated job.

RUNIdentifies a job brought in by the RUN command.

SSCNIdentifies a job record brought in by schedule scan.

XDEMIdentifies a job brought in by the DEMAND command from an XPSclient.

XPSIdentifies a job brought in from an XPS client using the RUN commandwith the REF option.

XRUNIdentifies a job brought in from an XPS client using the RUN command.

Note: If ARF detects an exception condition for the job, the last characterof this field has an asterisk as in the following: DEM*

MSTR REQIdentifies the number of outstanding master requirements for a job record.


LACT

JOB STATUSIdentifies the job's current disposition. Values and their meanings are:

A-SnnnnIndicates the job has failed with a system abend.

A-UnnnnIndicates the job has failed with a user abend.

C-CnnnnIndicates the job has completed successfully and is going throughcompletion processing.

LATEIndicates the job has not either started by the DEADLINE DAY/TIME orhas not completed by its DUE-OUT DAY/TIME.

R-#nnnnIndicates the job has failed a condition code test made at the step level.

R-CnnnnIndicates the job has failed a condition code test made at the job level.

R-JCLERRIf the job is in the request queue with this status, then there was eithera runtime JCL error (for example, data set not found) or an IEFUJV exitcanceled the job. If the job is in the ready queue with this status, then ajob purge record was received before a job initialization record.

R-NOUIDDuring submission, if no valid USERID is available, a check of theSUBNOID parameter is done to determine if a job can be submittedwithout an ID. With SUBNOID set to NO, the job is moved back to therequest queue with a status of R-NOUID.

R-TRLFULAt the time the job was active, Unicenter CA-7 required another track tobe obtained from the trailer queue to hold outputs. At the time thatUnicenter CA-7 tried to get another track, either an out of spacecondition or an I/O error occurred.

RETRYIndicates a dynamic allocation error occurred during the attach of JCLfor this job. At a user-specified time interval, a retry of the JCL attachoccurs.

RQMT-INCIndicates a job record is in the queue without its requirements attached.

RUSHIndicates the RUSH command was entered for this job.

SKELETONIndicates a job record is in the queue without JCL attached.

284 Commands Guide

LACTR

LACTR

The LACTR command provides resource requirement information about jobs inthe active queue. This lets you review the resource requirements of thecurrently active CPU workload. This command is similar to the LQR command.


LACTR

��──LACTR─ ──┬ ┬──────────────────── ───────────────────────────────� │ │┌ ┐─�─────

└ ┘──,CPUID= ──┴ ┴─smfid─

�─ ──┬ ┬──────────────────────────── ──┬ ┬──────────────────── ───────� │ │┌ ┐─�───────── │ │┌ ┐─ALL──

└ ┘── ─── ───,JOB= ──┼ ┼─jobname─── └ ┘──,MAINID= ──┼ ┼──SYn ─├ ┤─jobname�── ├ ┤──/SYn└ ┘─jobnumber─ └ ┘──-SYn

�─ ──┬ ┬────────────────── ──┬ ┬───────────────────── ────────────────� │ │┌ ┐─��─ │ │┌ ┐─NATV─────

└ ┘──,SCHID= ──┴ ┴─nnn─ └ ┘──,SEQ= ──┴ ┴─sequence─

�─ ──┬ ┬──────────────────────── ──────────────────────────────────�� │ │┌ ┐─�───────────


CPUIDDefines the CPU IDs for which jobs are to be listed.

Default: *

Required: No

*Specifies all CPU IDs.

smfidDefines only jobs with this specific CPU ID. The value is the SMFsystem ID. CPUID as a search argument in the inquiry command, mustmatch the SMF system identifier as defined to the OS system by theuser and received by Unicenter CA-7 in the SMF records.


LACTR

JOBDefines the jobs whose active queue resource information is to be listed.

Default: *

Required: No








MAINIDSpecifies that only those jobs with this MAINID (as defined on the DB.1panel) are to be listed. Jobs defined with MAINID of ALL are selectedregardless of MAINID entered.

Default: ALL

Required: No

ALLSpecifies all MAINIDS.

SYnWhere n specifies a CPU associated number for which information is tobe listed as defined in the initialization file CPU statement. The value ofn can range from 1 to 7. If a slash (/) precedes the SYn, the only jobsselected are those that are denoted to execute on /SYn.

-SYnWhere n specifies a CPU associated number for which information isnot to be listed. The value of n can range from 1 to 7.

286 Commands Guide

LACTR

SCHIDSpecifies the schedule ID for which information is to be selected.


Required: No

SEQSpecifies the display sequence of the desired information.

Default: NATV

Required: No

NATVSpecifies native sequence (the order in which it is in the queue).

CA7Specifies Unicenter CA-7 job number sequence.

DLTMSpecifies deadline time sequence.

DOTMSpecifies due-out time sequence.

JOBSpecifies job name sequence.

SYSDefines the application system names whose active queue resourceinformation is to be listed.

Default: *

Required: No







LACTR

ExamplesLACTR,MAINID=SY2

LACTR,JOB=FXABA�2M

� � LACTR

JOB=FXABA�2M DATE=YY.DDD PAGE ��1 JOB SYSTEM MAIN JOB CPU CA-7# CPU/ELAPS TOTAL TAPES CPU% SUBMIT

NAME -NAME- -ID- C/PRT -ID NUMBR --TIME--- TP1 TP2 UTIL DATE/TIME

FXABA�2M FIXASSET ALL A/12� SYSA ��17 ��43/��28 �� 3 �2.56 ��/��




SYSTEM NAMEIdentifies the system name as defined on the DB.1 panel.

MAIN IDIdentifies the value from the MAINID field on the DB.1 panel.

JOB C PRTIdentifies the workload balancing class and priority for this job.

CPU IDIdentifies the CPU where the job is currently executing. The ID is not filledin until the job initiation record is processed by Unicenter CA-7.

CA-7 #Identifies the Unicenter CA-7 assigned job number.

TIMEIdentifies the CPU and CLOCK TIME from the DB.1 panel.

TOTAL TAPESIdentifies the number of TAPE1 devices, TAPE2 devices, or both that thisjob requires.

CPU % UTILIdentifies the calculated CPU use (using CLOCK-TIME and CPU-TIME fromthe DB.1 panel).

SUBMIT DATE TIMEIdentifies the Julian date and time this job was submitted.

288 Commands Guide

LARF

LARF

The LARF command lists ARFSETs in summary or in detail. The ARFSETs arestored in alphabetical order by ARFSEThis name. Each ARFSET contains oneor more ARFSET definitions. Each ARFSET definition defines a specific jobprocessing condition that may arise during the course of the job's execution,such as a system D37 abend. Associated with each test is a list of ARFresponses that is carried out by ARF if the designated condition should arise.This response set can include directives for issuing Unicenter CA-7 commandsor submitting other jobs on behalf of the Unicenter CA-7 job that met the ARFtest conditions.


LARF

��──LARF─ ──┬ ┬─────────────────────── ──┬ ┬─────────────── ─────────��│ │┌ ┐─�─────── └ ┘──,LIST=listopt└ ┘──,ARFSET= ──┼ ┼─arfset──

└ ┘─arfset�─

ARFSETDefines the ARFSET name.

Default: *

Required: No

*Specifies all ARFSETs.

arfsetDefines a specific ARFSET name.


arfset*Defines a generic ARFSET name.


LISTOverrides the default list option. The possible values are the following:

DEFSForces the detail listing of the ARFSET definitions.

NODEFSForces the summary listing of the ARFSET definitions.

When ARFSET= identifies a specific ARFSET, LIST=DEFS is the default.

When ARFSET= is a generic indication, LIST=NODEFS is the default.


LARF

For example, the command LARF,ARFSET=*,LIST=DEFS would list alldefinition details for all ARFSETs in the ARF database.

Examples

Example 1. Output: LARF With Generic ARFSET

� �LARFARFSET=� LIST=NODEFS DATE=yy.�64 PAGE ��1

ARF SET ARF LAST CHANGE NBR EC EE JC LA LB LE LS SC ISNAME UID DATE TIME DEF # # # # # # # # #

ALL �� 2/22/yyyy 18:2� 4 1 . . . . 1 1 1 .BEC �� 2/28/yyyy 14:1� 1 1 . . . . . . . .BEE �� 2/28/yyyy 14:14 1 . 1 . . . . . . .BLA �� 2/28/yyyy 13:39 2 . . 1 . . . . 1 .EC �� 2/21/yyyy 14:25 1 1 . . . . . . . .JC1 �� 2/12/yyyy 13:15 1 . . 1 . . . . . .JJJ �� 2/27/yyyy 15:35 2 . . 1 1 . . . . .LA �� 2/14/yyyy 15:35 1 . . . 1 . . . . .LE �� 2/16/yyyy 14:21 1 . . . . . 1 . . .LS �� 2/22/yyyy 14:24 1 . . . . . . 1 . .MSGS �� 2/28/yyyy 16:56 2 . . 1 . . . . 1 .MULTI �� 2/�8/yyyy 14:�9 3 . . 3 . . . . . .NEW �� 2/29/yyyy 1�:�1 1 . . . 1 . . . . .SCWTO �� 2/15/yyyy 18:52 1 . . . . . . . 1 .TESTJC �� 2/14/yyyy 15:�� 1 . . 1 . . . . . .TESTJC2 �� 3/�1/yyyy 17:3� 1 . . 1 . . . . . .

SLIW-�� REQUEST COMPLETED AT 1�:48:�9 on yy.�64� �


ARFSET LISTIdentifies the options that are in effect for this command.

ARF SET NAMEIdentifies the name of the ARFSET.

ARF UIDIdentifies the Unicenter CA-7 UID associated with the ARFSET.

LAST CHANGE DATEIdentifies the date when this ARFSET was last changed.

LAST CHANGE TIMEIdentifies the time of day when this ARFSET was last changed.

NBR DEFIdentifies the total number of ARF definitions within this ARFSET.

ECIdentifies the number of elapsed time completion tests within this ARFSET.

EEIdentifies the number of elapsed execution time tests within this ARFSET.

290 Commands Guide

LARF

JCIdentifies the number of job completion tests within this ARFSET.

LAIdentifies the number of late tests within this ARFSET.

LBIdentifies the number of late begin time tests within this ARFSET.

LEIdentifies the number of late end time tests within this ARFSET.

LSIdentifies the number of late at submit time tests within this ARFSET.

SCIdentifies the number of step completion tests within this ARFSET.

ISIdentifies the number of interrupt submission tests within this ARFSET.


LARF

Example 2. Output: LARF With Specific ARFSET

� �LARF,ARFSET=MULTIARFSET=MULTI LIST=DEFS DATE=yy.�64 PAGE ��3

ARFSET: MULTI UID: �� CHG: �2/�8/2��-14:�9 DEFS: 3/ 3 RPSID: MASTER

INTERCEPT TYPE: JC INDEX: 3 APPLICABILITY TESTS:

SYS EQ � SID EQ � RSTC GE � EM EQ ANYFROM: �1/�1/1975 ��:�1 TO: 12/31/2�74 23:59

TESTS RUN DURING INTERCEPT PROCESSING:STEP EQ � PROC EQ � PGM EQ �SYS EQ ��C5 OR SYS EQ ��C6 OR CC GE ��16

RESPONSE SET:AM,CM=T,USER=C495MM1,M=THIS IS AN �C5 OR AN �C6!!!

AM,CM=T,USER=BOB,M=HI AW,TIME=��2 AC,M=/WTO,M=HOWDY AJ,RETRY=��1,DELAY=��2,ACTION=3,JOB=G

DISP=R CA-11=N BYPGDG=N USAGE= PROCESS= CC= STEPS: START= END=

SLIW-�� REQUEST COMPLETED AT 1�:48:31 on yy.�64� �


ARFSET LISTIdentifies the options that are in effect for this command.

ARFSET:Identifies the name of the ARFSET.

UIDIdentifies the Unicenter CA-7 UID associated with the ARFSET.

CHGIdentifies the date and time when this ARFSET was last changed.

DEFSIdentifies the number of the current ARF definition within this ARFSET andtotal number of ARF definitions within this ARFSET.

RSPIDIdentifies the ID that will be used during ARF recovery.

INTERCEPT TYPEIdentifies the Unicenter CA-7 or ARF intercept where this test definition isapplied.

INDEXIdentifies the ARF definition index number assigned to this test definition.

APPLICABILITY TESTIdentifies the applicability tests. These tests are applied when the job isbeing placed into the request queue. They can pertain to the context inwhich the job runs and can be evaluated before the job begins.

292 Commands Guide

LARF

SYSIdentifies the SMF system ID where the job must run for this test to apply.

SIDIdentifies the Unicenter CA-7 schedule ID under which the job must run forthis test to apply.

RSTCIdentifies the restart count condition where this test is to apply.

EMIdentifies the entry Mode under which the job is running for this test toapply.

FROM TOIdentifies the From and To dates defining the time frame within which thetests are to apply.

TESTS RUNIdentifies the ARF tests that are run at the time of the intercept. These varygreatly depending upon the intercept. In this example, the job completionintercept tests are shown.

STEPIdentifies the step name where the tests are to be applied.

PROCIdentifies the PROC step name where the tests are to be applied.

PGMIdentifies the program name to which the tests apply.

SYSIdentifies a system abend condition.

CCIdentifies a completion code condition.

USERIdentifies a user abend condition.

FLSHIdentifies a flush condition.

JCLIdentifies a JCL error condition.

RESPONSE SETIdentifies the set of responses to be attempted by ARF when the testconditions are met. In the example, several possible ARF responses areillustrated:

M=Identifies an example ARF Message response. ARF sends a message tothe designated target and then moves to the next response.


LARF

TIME=Identifies an example ARF Wait response. ARF waits the designatednumber of minutes and then moves to the next response.

ACIdentifies an example ARF Command response. ARF issues thedesignated Unicenter CA-7 command and then moves to the nextresponse.

AJIdentifies an example ARF Job response. ARF submits another job, waitsfor that job to complete, and then moves to the next response.

DISPIdentifies the final disposition to assign to the job if all ARF responsescomplete normally.

M1Identifies the final disposition control detail line 1.

DISPIdentifies the disposition directive: R - Restart; C - Cancel; F - ForceComplete.

CA-11Identifies whether Unicenter CA-11 should be used for the restart.

BYPGDGInstructs Unicenter CA-11 in the handling of GDGs during the restart.

USAGEIdentifies the Unicenter CA-11 usage code to be used in restart.

PROCESSIdentifies the Unicenter CA-11 process code to be used in restart.

CCIdentifies the condition code value to be used in Unicenter CA-11.

STARTIdentifies the first step in the job where Unicenter CA-11 should be restartprocessing.

ENDIdentifies the last step in the job that should be processed when UnicenterCA-11 is controlling the restart.

COMPLETED ATIdentifies the completion message indicating all processing for thiscommand has completed.

294 Commands Guide

LARFQ

LARFQ

The LARFQ command lists the ARF queue. The ARF queue identifies allpending and in-process response activities that were initiated by UnicenterCA-7 jobs being tracked by ARF where the designated ARF test conditionswere met. Each queue entry defines the presence of an ARF response set for asingle job. The ARF queue is ordered in a first-in, first-out sequence. A givenjob can only have one queue entry active at a time. If a given Unicenter CA-7job has met multiple ARFSET tests, the subsequent response sets are queuedup "behind" the one active response set for that job. The active response setfor a given job is referred to as that job's "current" response set. When a job'scurrent response set comes to a conclusion, ARF "promotes" the next responseset that was queued up behind the current one. The promotion process deletesthe previous current response set and sets up a new current response set for agiven job. When all response sets for a given job have been completed, thejob's ARF queue entry is deleted altogether.


LARFQ

��──LARFQ─ ──┬ ┬──────────────────────────── ──────────────────────�� │ │┌ ┐─�─────────

└ ┘── ─── ───,JOB= ──┼ ┼─jobname─── ├ ┤─jobname�── └ ┘─jobnumber─

JOBSpecifies the jobs whose ARF queue resource information is to be listed.

Default: *

Required: No









LARFQ

Examples

� �LARFQJOB=� DATE=yy.�43 PAGE ��1

JOB JOB ARF SET SET EVENT RSP RSP RSP RESPONSENAME NBR NAME IX STATUS CD # TOT TYPE STATUS

ARRPT12 �291 SPACECK 1 IN-PROC JC 1 FINAL PRMTH2� �312 SPACECK 1 IN-PROC JC 1 FINAL APRST15 �317 ABNDHLD 1 IN-PROC JC 1 FINAL� �A� �B� APRST15 �317 ABNDHLD 1 IN-PROC JC 1 ERROR� �1��16 (��3)

SLIY-�� REQUEST COMPLETED AT 1�:29:�4 on yy.�43� �


JOBIdentifies the options that are in effect for this command.

JOB NAMEIdentifies the name of the job on whose behalf ARF is processing.

JOB NBRIdentifies the Unicenter CA-7 job number of this job.

ARF SET NAMEIdentifies the ARFSET name defining the responses that are beingprocessed.

IXIdentifies the ARFSET definition index identifying the response set beingprocessed.

SET STATUSIdentifies the status of ARF processing for this job.

EVENT CDIdentifies the type of intercept (event) where the ARF test conditions weremet.

RSP #Identifies the relative response number in the ARF response set where ARFis currently processing.

RSP TOTIdentifies the total number of responses in the current response set.

RSP TYPEIdentifies the type of ARF response currently being processed, or indicatesthat an error has occurred. If the value is ERROR, ARF processing issuspended for the job. The codes at �A� and �B� provide additionalinformation about the error. Because the job is still under ARF control, usethe ARFP command to continue with manual recovery.

296 Commands Guide

LARFQ

RESPONSE STATUSIndicates the current status of the current response being processed byARF.

COMPLETED ATIdentifies the completion message indicating all processing for thiscommand has completed.

�A�The value of @ARFQ_RETCODE is displayed in the event of an errorcondition. The possible values are the following:

0100000CA Unicenter CA-7 violation was detected for a command issued byARF. A CA-7.012 message is produced at the MASTER station. Asecurity violation occurred or an unidentified command was detected.

01000016A Unicenter CA-7 security violation was detected for a terminal signonattempted by ARF. A CA-7.022 message is produced at the MASTERstation.

00000001An error occurred while processing a RESTART command issued byARF. SJRx messages are produced at the MASTER station indicatingthe nature of the error.

0200xxyyAn error occurred while processing a DEMAND or RUN commandissued by ARF. SPO7 messages are produced at the MASTER stationindicating the nature of the error. (If the value of xx is 0D or 0E, yycontains the return code from SASSSCSR.)

�B�The value of @ARFQ_RSPERR is displayed in the event of an errorcondition. The possible values are the following:

0001An error occurred while trying to process a final disposition.

0002ACTION = E was encountered on an AJ action statement.

0003An error occurred while trying to process a command.


LCTLG

LCTLG

The LCTLG command primarily lists data set information from the UnicenterCA-7 index data set. You can also use it to list special entries such asdocumentation, networks, triggers, or requirements from the Unicenter CA-7database. When LCTLG is used to list data sets, the following information isdisplayed: volume information, creation dates and times, and deviceinformation. Also, use this command to list information from a specific CVOLcatalog.


LCTLG

��──LCTLG─ ──,DSN=dsname ──┬ ┬──────────────── ─────────────────────��└ ┘──,VOLSER=volser

DSNDefines the fully qualified name of the data set. For partial qualification, thename can end with a period or can be delimited with an asterisk (*) afterthe first node.


Required: Yes

VOLSERDefines the volume serial number of a catalog, instead of the UnicenterCA-7 database index data set, from which information is to be listed. Thevalue must be the volume serial of the pack on which the desired catalogdata set resides. VOLSER is not used when listing information from theUnicenter CA-7 database; only when listing from a catalog on some othervolume.


Required: No

298 Commands Guide

LCTLG

ExamplesLCTLG,DSN=CA7.DSN1

LCTLG,DSN=CA7.

LCTLG,DSN=CA7.,VOLSER=CATLG

LCTLG,DSN=NW.STATION1.NETWK1

LCTLG,DSN=AUTO.

LCTLG,DSN=JDEP.

LCTLG,DSN=TRGD.

� � LCTLG,DSN=JDEP.

DSN=JDEP. DATE=YY.DDD PAGE ��2

DATASET NAME TRIGGERED JOB SCHID QTM/DOTM LEADTM SUBMTM

JDEP.DUSABDDM DUSAFC32 ��2 �1��Q �1�� DUSAFC33 ��2 �1��Q �1��

JDEP.DEPO�1A� TPRE�1A� ��1/��1 16��D �1�� JDEP.DUMBDL�8 DUHNLAMB ��1/��2 �8��D ��1� ��

DUHNLAMB ��2/��3 �83�D ��2� ��JDEP.DUSABCLP DUSAGEN4 �� 1��D �1�� 9��

DUSAGEN8 �� 1��D �1�� 9��


DATASET NAMEIdentifies a job name (prefixed by JDEP.) of a job that triggers jobs.

TRIGGERED JOBIdentifies the name of the job that is triggered.

SCHIDIdentifies the schedule ID that the triggering job must run under for thetrigger to occur; optionally, followed by a different schedule ID that thetriggered job runs under.

QTM/DOTMIdentifies either the queue time or the due-out time (defined on the DB.2.4panel) for this trigger entry in hhmm format.

LEADTMIdentifies the lead time for this trigger entry as defined through the DB.2.4panel in hhmm format.

SUBMTMIdentifies the submit time as defined on the DB.2.4 panel in hhmm format.


LCTLG

� � LCTLG,DSN=AUTO.

DSN=AUTO. DATE=YY.DDD PAGE ��1

DATASET NAME TRIGGERED JOB SCHID QTM/DOTM LEADTM SUBMTM

AUTO.DS��5 (CA7.TRNG1)TESTJOB1 �� 12��D �1��

AUTO.DS��9 (CA7.TEST9)DUSAXX1� �� 1��Q ��3� ��

AUTO.DS��11 (CA7.TRNG2)DUTSXX�4 �� 2�Q ��3� ��DUSGXX�5 ��1/��2 ��3�Q ��3� ��

� �


DATASET NAMEIdentifies the DSNBR (prefixed by AUTO.) followed by the data set nameenclosed in parentheses of the data set whose creation triggers a job orjobs, or the DSNBR (prefixed by AUTO.) followed by the input networkname enclosed in parentheses of an input network whose completiontriggers a job or jobs.

TRIGGERED JOBIdentifies the name of the job that is triggered.

SCHIDIdentifies the data set must be created or updated or the input networkcompleted under this schedule ID for the trigger to occur; optionally,followed by a different schedule ID that the triggered job runs under.

QTM/DOTMIdentifies either the queue time or the due-out time (defined on theappropriate panel) for this trigger entry in hhmm format.

LEADTMIdentifies the lead time for this trigger entry as defined through theappropriate panel in hhmm format.

SUBMTMIdentifies the submit time as defined on the appropriate panel in hhmmformat.

300 Commands Guide

LCTLG

� � LCTLG,DSN=PP.

DSN=PP. DATE=YY.DDD PAGE ��1

-----------------DATASET NAME---------------DSNBR POSTTM TYPE

PP.SOCCXX�1.JOB PP��12 JTERM JOB PP.SOCCXX�2.JOB PP��11 JTERM JOB PP.SOCCXX�3.JOB PP��1� JTERM JOB PP.SOCCXX�4.JOB PP��9 JTERM JOB PP.SOCCXX�5.JOB PP��8 JTERM JOB

SLID-�� REQUEST COMPLETED AT 18:42 on YY.DDD� �


DATASET NAMEIdentifies the data set name for documentation entries is determined asfollows:

■ For job documentation it is PP.jobname.JOB

■ For data set documentation it is PP.data set name

■ For system documentation it is PP.system name.SYS

■ For user documentation it is PP.user name

■ For network documentation it is PP.network name.NW

■ For dd documentation it is PP.job name.step name.ddname.

DSNBRIdentifies a Unicenter CA-7 assigned number (with the prefix of PP) bywhich this entry is known.

TYPEIdentifies whether this is job, data set, system, user, network, or job/step/dddocumentation.


LCTLG

� � LCTLG,DSN=TRGD.

DSN=TRGD. DATE YY.DDD PAGE ��1

DATASET NAME TRIGGERED BY JOB/DSN SCHID QTM/DOTM LEADTM SUBMTM

TRGD.ADDRQ TRAILER �� 1�Q ��1� ��TRGD.BRO ADDRQ �� 1�Q ��1� ��TRGD.CA7FRCST SCHDDUMY �� 3�Q ��1� ��TRGD.CA7LJOBA CA7LRLOG �� 1�Q ��1� ��TRGD.CA7LJOBB CA7LJOBA �� 1�Q ��1� ��

SLID-�� REQUEST COMPLETED AT 11:59:32 on YY.DDD� �


DATASET NAMEIdentifies a job name (prefixed by TRGD.) of a job that is triggered eitherby another job's completion or a data set creation.

TRIGGERED BYIdentifies the job name of the job that triggers this job, the DSNBR of a dataset whose creation triggers this job, or the DSNBR of an input networkwhose completion triggers this job.

SCHIDIdentifies the schedule ID that the job must run under, that a data set mustbe created under or that the input network must be brought into thepreprocess queue under for the trigger to occur; optionally, followed by adifferent schedule ID that the triggered job runs under.

QTM/DOTMIdentifies either the queue time or the due-out time defined on theappropriate trigger panel in hhmm format.

LEADTMIdentifies the lead time for this trigger entry as defined on the appropriatetrigger panel in hhmm format.

SUBMTMIdentifies the submit time as defined on the appropriate trigger panel inhhmm format.

302 Commands Guide

LCTLG

� � LCTLG,DSN=PRED.

DSN=PRED. DATE YY.DDD PAGE ��1

DATASET NAME SUCCESSOR JOB SCHID

PRED.CA�7LOGP CA�7LOGH �� PRED.CA�7LOGS CA�7LOGH �� PRED.D463XX�2 D463XX�5 �� PRED.D463XX�3 D463XX�5 �� PRED.D463XX�4 D463XX�6 ��

SLID-�� REQUEST COMPLETED AT 11:59:33 on YY.DDD� �


DATASET NAMEIdentifies a job name (prefixed by PRED.) of a job that is a requirement foranother job or jobs.

SUCCESSOR JOBIdentifies the name of the dependent job.

SCHIDIdentifies the schedule ID of the dependent job that has the requirement.

� � LCTLG,DSN=ABC.

DSN=ABC. DATE=YY.DDD PAGE ��1

--------------- DATASET NAME --------------- DSNBR POSTTM TYPEDATE TIME GDG# #VOL VOLSER DEV-TYPE SEQ

ABC.NAME.INPUT ........................... ��54 JTERM PERMYYDDD 1525 ��3 ��1 LIB114 3�5�2��B ��5YYDDD 1516 ��2 ��1 LIB114 3�5�2��B ��5YYDDD 1157 ��1 ��1 LIB114 3�5�2��B ��

ABC.NAME.OUTPUT .......................... ��55 JTERM� �


DATASET NAMEIdentifies the fully qualified data set name as defined in the Unicenter CA-7database.

DSNBRIdentifies a Unicenter CA-7 assigned number by which this entry is alsoknown.

POSTTMIdentifies when the posting of this data set creation occurs. Values areJTERM for job completion processing time or DSCRT for posting at dataset creation time.


LCTLG

TYPEValues for this field can be:

■ AUTO for a data set that triggers a job or jobs upon its creation.

■ EXTL for a data set either created or used by jobs defined to UnicenterCA-7.

■ INTL for a data set created and used by jobs defined to UnicenterCA-7.

■ PERM for a data set defined as permanent.

DATEIdentifies the last three Julian dates that a creation or update of this dataset occurred through a Unicenter CA-7 submitted job.

TIMEIdentifies the last three times that a creation or update of this data setoccurred through a Unicenter CA-7 submitted job in hhmm format.

GDGIdentifies the generation data group number for a GDG data set.

VOLIdentifies the number of volumes that this data set spans.

VOLSERIdentifies the volume where this data set resides.

DEV-TYPEIdentifies the hexadecimal device code for the device where this data setwas created.

SEQIdentifies the sequence number of this data set.

304 Commands Guide

LDSN

LDSN

The LDSN command lists data set information from the database including dataset attributes, device and volume information, and information about which jobsuse the data set or are trigger scheduled as a result of its creation.


LDSN

��──LDSN──,─ ──┬ ┬──DSN=dsname ──────────── ─────────────────────────�└ ┘──DSNBR= ──┬ ┬──DSnnnnnnnn

├ ┤──DS�nnnnnn� └ ┘─DS�────────

�─ ──┬ ┬──────────────────── ──┬ ┬──────────────────────────────── ──�� │ │┌ ┐─DSN──── │ │┌ ┐─�,32��───────────

└ ┘──,LIST= ──┴ ┴─option─ └ ┘──,USERS= ──┴ ┴──(minimum,maximum)

DSNDefines the fully qualified name of the data set. For partial qualification, thename can end at a period or can be delimited with an asterisk (*).


Required: Yes (unless DSNBR is used)

DSNBRDefines a single or generic Unicenter CA-7 data set number identifying themembers whose records are to be listed. Must be entered with the DSprefix. With this option, the major sequence of the output listed is by dataset number.

Required: Yes (unless DSN is used)

DSnnnnnnnnDefines the value for a single Unicenter CA-7 assigned data setnumber in up to eight digits with a prefix of DS. Leading zeros can beomitted.

DS0nnnnnn*Defines a generic data set number in up to seven digits preceded withDS and terminated with an asterisk. The leading zero must not beomitted. For example, to list all DSNBRs in the range 7000-7999, useDSNBR=DS00007*.

DS*Specifies all data set records.


LDSN

LISTSpecifies list options for data set information.

Default: DSN

Required: No

DSNSpecifies data set information only.

ALLSpecifies data set information, "using-jobs" and documentation entries.

EXTLSpecifies data sets that are classified external to Unicenter CA-7.

INTLSpecifies data sets that are classified internal to Unicenter CA-7.

NORMSpecifies data sets shown as NORM on the DB.6 panel. Includesinternal and external data sets.

NOUSERSpecifies data sets that have no "using-jobs."

PERMSpecifies data sets shown as PERM on the DB.6 panel.

TRIGSpecifies all the jobs that are triggered by the data set.

USERSSpecifies all users of a data set. These are jobs that reference the dataset in their JCL. Jobs with large JCL may not show in the list (forexample, over 100 steps and 500 DDs).

Note: LIST=TRIG and LIST=ALL cannot be used for generic requests byDSN or DSNBR.

USERSSpecifies selecting data sets meeting minimum and maximum number ofusing jobs.

Limits: 5 numeric characters from 00000 to 32767

Required: No

minimumSpecifies to select data sets with the specified minimum of using jobs.

(minimum,maximum)Specifies to select data sets in the specified range of using jobs.

306 Commands Guide

LDSN

ExamplesLDSN,DSN=CA7.DSN1

LDSN,DSN=CA7.DSN1,LIST=USERS

LDSN,DSN=DS5�,LIST=ALL

LDSN,DSNBR=DS�,LIST=NOUSER

LDSN,DSNBR=DS��3�

LDSN,DSNBR=DS�,LIST=PERM

LDSN Panel

� � LDSN,DSN=SSDDEV.CA�7.BATCHO,LIST=ALL

LIST=ALL DSN=SSDDEV.CA�7.BATCHO DATE YY.DDD PAGE ��1

-------------- DATASET NAME --------------- DSNBR PPNBR POSTTM DSTYPEDSORG RECFM LRECL BLKSZ DEVTYP J-USE J-CRT #RQ MDATE/TIME MTYPE

SSDDEV.CA�7.BATCHO ........................ ��2� �NONE� JTERM PERMPS VB ��137 �4114 DASD ��2� �� YYDDD/�931 DBM

� LAST MAINTENANCE ON yy.ddd AT hh:mm:ss VIA xxx BY OPERATOR:yyyyyyyy�A� --------------------- DATASET/JOB CROSS REFERENCE ---------------------

JOB=D463BTI STEP-NUMBER=��1 DISP=SHR JOB=CA7LJESX STEP-NUMBER=��1 DISP=SHR JOB=CA7LJOBX STEP-NUMBER=��1 DISP=SHR JOB=CA7LRLOG STEP-NUMBER=��1 DISP=SHR JOB=CA7IDRNG STEP-NUMBER=��1 DISP=SHR JOB=CA7PND�3 STEP-NUMBER=��1 DISP=SHR

SLIB-�� REQUEST COMPLETED AT 1�:18:26 on YY.DDD.� �

� �LDSN,DSN=SYS2.PROCLIBLIST=DSN DSN=SYS2.PROCLIB DATE YY.DDD PAGE ��1

--------------- DATASET NAME --------------- DSNBR PPNBR POSTTM DSTYPEDSORG RECFM LRECL BLKSZ DEVTYP J-USE J-CRT #RQ MDATE/TIME MTYPE

SYS2.PROCLIB ............................... ��19� �NONE� JTERM PERM �� DASD �� YYDDD/1�33 LOAD

SLIB-�� REQUEST COMPLETED AT 17:�1:15 on YY.DDD.� �


LDSN

LDSN,DSNBR=DS* Panel

� �LDSN,DSNBR=DS�LIST=DSN DSNBR=DS� DATE YY.DDD PAGE ��1

--------------- DATASET NAME --------------- DSNBR PPNBR POSTTM DSTYPEDSORG RECFM LRECL BLKSZ DEVTYP J-USE J-CRT #RQ MDATE/TIME MTYPE

SSDECS.CA�7.VM.LOADLIB ..................... ��1 PP��7� JTERM PERM PO U �4�96 �4�96 DASD ��1 �� YYDDD/1451 DBM

SSDECS.CA�7.VM.U7TEST�2 .................... ��2 PP��6� JTERM INTL,AUTO PS F ��8� ��8� DASD ��3 ��1 �� YYDDD/1632 SMF

SSDECS.CA�7.VM.U7TEST�9 .................... ��3 �NONE� JTERM INTL,AUTO PS F ��8� ��8� DASD ��1 ��1 �� YYDDD/�737 SMF

SSDDEV.CA�7.LOADLIB ........................ ��4 �NONE� JTERM PERM �� UNKNOWN �� YYDDD/1648 DBM

SSDDEV.CA�7.U7TEST�2 ...................... ��5 �NONE� JTERM EXTL,AUTO �� UNKNOWN �� YYDDD/1648 DBM� �


�A� - DATASET/JOB CROSS REFERENCEIdentifies the jobs that reference this data set, the step that it is referencedin and the disposition.

DATASET NAMEIdentifies the fully qualified data set name as defined in the Unicenter CA-7database.

DSNBRIdentifies a Unicenter CA-7 assigned number that this entry is also knownby.

PPNBRIdentifies the documentation DSNBR for this data set.

POSTTMIdentifies when the posting of this data set creation occurs. Values areJTERM for job completion processing time or DSCRT for posting at dataset creation time.

DSTYPEIdentifies one of the following values:

■ AUTO for a data set that triggers a job or jobs upon its creation.

■ EXTL for a data set that is either created or used by jobs defined toUnicenter CA-7.

■ INTL for a data set that is created and used by jobs defined toUnicenter CA-7.

■ PERM for a data set defined as permanent.

308 Commands Guide

LDSN

DSORGIdentifies the data set organization.

RECFMIdentifies the record format for this data set.

LRECLIdentifies the record size.

BLKSZIdentifies the blocksize for this data set.

DEVTYPIdentifies the device type (DASD or TAPE) for this data set. (UNKNOWNindicates that the data set was added using the DSN panel withoutspecifying the device.)

J-USEIdentifies the number of jobs that use this data set as input.

J-CRTIdentifies the number of jobs that created or updated this data set.

#RQIdentifies the number of jobs that have had a manual connection made onthe DB.3.1 panel for this data set.

MDATE/TIMEIdentifies the date and time of the last maintenance performed on this dataset entry.

MTYPEIdentifies the method used for the last maintenance performed on this dataset.

■ ANLZ - for updating that occurred through the RESANL command.

■ DBM - for updating of this record through the DSN panel.

■ LOAD - for updating of this record by the load of a job.

■ SMF - for updating that occurred through SMF data.


LDTM

LDTM

The LDTM command displays an analysis of outstanding requirements for jobsin the request queue that involve fixed satisfaction lead times. These are job,data set, and network requirements where a fixed satisfaction lead time hasbeen specified either on the requirement definition itself or on the Job definitionpanel (DB.1).

The LDTM command can be used to determine which outstanding requirementsshould be manually posted after an application or system outage has disruptedthe normal flow of the production workload.


LDTM

��──LDTM─ ──┬ ┬──────────────────────────── ──┬ ┬─────────── ─────────�│ │┌ ┐─�───────── └ ┘──,LIST=ALL└ ┘── ─── ───,JOB= ──┼ ┼─jobname───


�─ ──┬ ┬───────────────────────────────────────────────────── ──────�└ ┘──,OUTAGE= ──┬ ┬─duration──────────────────────────────

├ ┤──(startdate,starttime,duration) ───────└ ┘──(startdate,starttime,enddate,endtime)

�─ ──┬ ┬──────────────────── ──────────────────────────────────────�� │ │┌ ┐─�───────

└ ┘──,SYS= ──┼ ┼─system── └ ┘─system�─

JOBSpecifies the job names for which information is to be selected.

Default: *

Required: No

*Specifies all jobs in the request queue.



310 Commands Guide

LDTM

jobname*Defines multiple jobs specified by a generic job name.




LISTCan be used in combination with the OUTAGE keyword. If the OUTAGEkeyword is specified and the LIST keyword is not specified, onlyrequirements that match the outage window are listed. If LIST=ALL isspecified, all outstanding requirements with fixed satisfaction lead times arelisted regardless of whether they match the outage window.

Required: No

OUTAGESpecifies the duration, time frame, or both of the application or systemoutage that has occurred. If an outage is specified, the outstandingrequirements with fixed satisfaction lead times are subjected to furtheranalysis to determine if the requirement might have been satisfied if theoutage had not occurred. For more information, see “Usage Notes” onpage 313.

Required: No

durationUse this format to specify an outage duration without any date/timereference. The duration can be expressed as a number of hours (one tothree digits), or as hours and minutes (four digits).

OUTAGE=8 An 8 hour outage.OUTAGE=�13� A 1 hour 3� minute outage.

(start date, start time, duration)Use this format to express an outage with a starting point and a fixedamount of time forward from that point (duration).

The starting date/time is specified on the keyword. The ending time iscalculated as the starting date/time plus the duration. The starting datecan be expressed as a Julian date (five digits) or Gregorian date (sixdigits). The starting time can be expressed as mm (4 digits) where hh isthe hour (00-24) and mm is the minutes (00-59). If no time is specifiedthe default is the beginning of the day (0000).

The duration can be expressed as a number of hours (one to threedigits), or as hours and minutes (four digits).

OUTAGE=(�5��1,13��,8) Jan. 1, 2��5 (1:��pm - 9:��pm)OUTAGE=(�1�2�5,12��,24) Jan.2,2��5(noon) - Jan.3,2��5 (noon)


LDTM

(start date, start time, end date, end time)Use this format to express both a starting and ending point for theoutage window.

The dates can be expressed as Julian dates (five digits) or Gregoriandates (six digits).

The times can be expressed as mm (4 digits) where hh is the hour(00-24) and mm is the minutes (00-59). If no start time is specified thedefault is the beginning of the day (0000). If no end time is specifiedthe default is the end of the day (2400).

OUTAGE=(�5��1,12��,�5��2,�8��) Jan 1 (noon) - Jan 2 (8 am)OUTAGE=(�1�2�5,,�1�3�5) All of Jan 2. and Jan 3, 2��5

SYSSpecifies an application system names to be matched by the system ID inthe job data in order for the job to be listed.

Default: *

Required: No


systemDefines a specific application system name.


system*Defines a generic application system name.


312 Commands Guide

LDTM

Usage Notes

The purpose of the LDTM command is not to tell you what requirements shouldbe manually posted. Its purpose is to streamline that process by eliminatingrequirements that obviously do not fit the outage criteria you provided it. Thefinal determination of whether a requirement should be manually posted or notdepends on the type of outage that occurred, how you have built yourproduction workload, and the reasons why a fixed satisfaction lead time wasspecified for the requirement in the first place.

The LDTM command attempts to analyze the processes that occurred when thejob first came into the queue and the determination was made whether toinitially satisfy a requirement, or leave it outstanding. When an outage durationor an outage window is supplied, the process can panel out requirements thatobviously do not match the outage criteria. This leaves you with fewerrequirements to be manually evaluated based on the type of outage thatoccurred and your knowledge of the workload you are running.

The command selects outstanding requirements for jobs in the request queuebased upon the following criteria:

■ Outstanding job, data set, and input network requirements with a fixedsatisfaction lead time are selected.

■ The difference between the look back point and the last run point iscompared with the outage duration. If the difference is greater than theoutage, then the requirement is not marked as matching the outage. If therequirement is for a job, the last run date/time used during initialrequirement satisfaction process is carried in the requirement segment itself.For data sets and networks, this information is obtained from theappropriate database record.

■ The following qualifications are made only if the outage is specified as anspecific date/time range (an outage window). If the outage was specified asa simple duration, further checks cannot be made since there is no specificoutage date/time range to reference.

■ If the deadline date and time is less than the beginning of the outagewindow, the requirement is not marked as matching the outage. If the jobentered the system before the outage occurred, then it had no effect on theinitial requirement satisfaction calculations.

■ If the required element has no last run date/time the requirement is notmarked as matching the outage. This is because now there is no date/timereference to compare with the outage window.

■ If the look back point minus the outage duration does not reach back tosome part of the outage window, the requirement is not marked asmatching the outage.


LDTM

ExamplesLDTM

Evaluate all fixed LDTM requirements with no outage.

LDTM,OUTAGE=8

Evaluate all fixed LDTM requirements with a nonspecific eight hour outage.

LDTM,JOB=PAY�,OUTAGE=(�116�5,12��,�118�5,14��)

Evaluate fixed LDTM requirements for jobs beginning with PAY. Use an Outagewindow from January 16, 2005 at noon to January 18, 2005 at 2:00 p.m. as areference.

� � LDTM,JOB=P�,OUTAGE=5 DATE=yy.�8� PAGE ��1

JOB QUEUE CA-7 -DAY(DDD) AND TIME(HHMM)-- CPU SCH ENTRY MSTR JOBNAME NAME JOB# DEADLINE SUB/START DUE-OUT SPEC/RUN ID MODE REQ STATUS

�A�P3 REQ �792 �23/1731 �NONE� �23/1731 ALL- ��1 DEMD ��3 LATE

-------- ------------- SATISFACTION LEAD TIME ANALYSIS ---------------------- �B� �C� �D� �E� �F� �G�

JOB=P2 LKBK=yy�19/22:31 LRUN=yy�19/17:59 DIFF=��/�4:32 �OUTAGE� DSN=D463BD8.BDTEST�4

�H� DS��4 LKBK=yy�8�/�4:11 LRUN=yy3�7/11:39 DIFF=5�2/16:32�I� CREATED BY BDTEST�4

� �

�A�Job Detail line. This line contains general information about the listed job.For a detailed explanation of the fields on this line, see the LQ(UE)command.

�B�Type of Requirement. This field indicates the type of requirement.

The possible values are the following:

JOBJob requirement

DSNInternal data set requirement

XDSNExternal data set requirement

NWKNetwork requirement

314 Commands Guide

LDTM

�C�Name of Requirement. This is the job or network name that is arequirement. For data sets, it is the data set name that is required.

�D�Look Back (LKBK). Represents the point in time where Unicenter CA-7stopped looking for the last run of the required job. Requiring job queueentry date/time minus satisfaction lead time. It is presented asYYDDD/HHMM where: YYDDD = Julian date, and hours (HH) and minutes(MM).

�E�Last Run (LRUN). Represents the time when the required job lastcompleted, or the required data set was updated or created. It is presentedas YYDDD/HHMM where: YYDDD = Julian date, and hours (HH) andminutes (MM). If the job has never run (or data set never created) it ispresented as periods (.).

�F�Difference between the look back and last run times (DIFF). This representshow much the requirement "missed" being satisfied when the job came intothe request queue. It is presented as DDD/HHMM where: DDD = number ofdays (up to 999), and hours (HH) and minutes (MM). If the required job hasnever run, no valid calculation can be made; therefore, the difference ispresented as periods.

�G�Outage Factor Indicator. If an outage is specified on the command and therequirement fits the parameters of that outage, the character string*OUTAGE* is displayed. Otherwise, it is blank.

Note: If an outage is specified on the command and LIST=ALL is NOTspecified, then ONLY requirements that match the outage criteria are listed.

�H�Data Set Number. If the requirement is for a data set, the Unicenter CA-7data set number is displayed.

�I�Creation Job. If the requirement is for an internal data set, the name of thejob that updates or creates the data set is displayed.


LIST

LIST

The LIST command lists information about jobs in the request queue that arewaiting for a restart.


LIST

��──LIST─ ──┬ ┬──────────────────────────── ──┬ ┬───────────────── ──�� │ │┌ ┐─�───────── │ │┌ ┐─NO──

└ ┘── ─── ───,JOB= ──┼ ┼─jobname─── └ ┘──,PROSE ──┴ ┴─YES─ ├ ┤─jobname�── └ ┘─jobnumber─

JOBDefines the jobs in the request queue, flagged for restart, for which the listis desired.

Default: *

Required: Yes

*Specifies all jobs that are flagged for restart.

jobnameDefines a specific Unicenter CA-7 job name in up to eight characters.






PROSESpecifies whether restart documentation (#RESTART segment) is to belisted.

Default: NO

Required: No

316 Commands Guide

LIST

ExamplesLIST,JOB=�,PROSE=NO

� �C A - 7 J O B R E S T A R T PAGE ��1

SJR3-1� RESTART JOB SCAN.

JOBNAME CA7# LASTSTEP COMP ---DUE-OUT-- RC PROSE# COMMENTSACPBA�1W ��25 S�� YY.DDD/16:54 �7 ��295 JCLERR RSTBLACPCA�1W ��26 ACPCA�5� C��64 YY.DDD/16:54 �� COND-CDFXABA�2M �371 FXABA�1� U��21 YY.DDD/17:�� 2 ��5849 RSTBLPERAF�3M 1724 PERAF2�� S��13 YY.DDD/17:1� 35 ��19784 RSTBLWHSAA�1D 7359 WHSAA34� C�� YY.DDD/17:3� 14 �� REQUE RSTBLFXAAC�5D 2946 FXAAC17� C��32 YY.DDD/17:3� �1 ��14956 COND-CD RSTBL

SJR�-�� REQUEST COMPLETED AT 15:55:�8 on YY.DDD� �


JOBNAMEIdentifies the name of the job as defined in the database. See NAME fieldon the DB.1 panel.

CA7#Identifies the Unicenter CA-7 assigned job number.

LASTSTEPIdentifies the name of the last successfully executed step.

COMPIdentifies the completion code the job ended with.

DUE-OUTIdentifies the due-out date and time for this job queue record.

RCIdentifies the current restart count for this job queue record.

PROSE#Identifies the DSNBR for the documentation member for this job.

COMMENTSIdentifies the reason for job failure and indicates if this job is restartable atjob or step level. Values that can appear in the COMMENTS column ofLIST output are:

#STEPCCFailed step-level condition code tests based on #SCC statementsincluded in the JCL.

COND-CDFailed job-level condition code tests based on DB.1 panel fieldsCOND-CODE and RO.


LIST

JCLERRTerminated due to JCL error.

REQUEWas manually requeued by the user.

RSTBLA Unicenter CA-11 restart step is being inserted by Unicenter CA-7.

318 Commands Guide

LISTDIR

LISTDIR

The LISTDIR command lists the member names of any PDS accessible byUnicenter CA-7. Date, time, and version of the creation or last update areshown for members that were saved through the JCL function of DBM. Thisfunction is also offered on the UT Menu panel as function 14.


LISTDIR

��──LISTDIR─ ──,DSN=dsname ──┬ ┬───────────── ──┬ ┬───────────── ─────��└ ┘──,VOL=volume └ ┘──,MEM=member

DSNDefines the fully qualified name of the PDS data set for which directoryinformation is to be listed. If you are using online Base CalendarMaintenance, you can specify DSN=*SCAL* to list calendar names residingon the Unicenter CA-7 Calendar PDS.


Required: Yes

VOLDefines the volume on which the PDS data set resides. If omitted, thesystem catalog is used to locate the PDS data set.


Default: System catalog

Required: No

MEMDefines the starting PDS member name at which listing is to begin. Ifomitted, the entire directory is listed.

Default: Entire directory


Required: No


LISTDIR

ExamplesLISTDIR,DSN=CA7.JCLDS1

LISTDIR,DSN=SYS1.MACLIB,MEM=OPEN

LISTDIR,DSN=CA7.JCLDS12,VOL=DSK��5

� �LISTDIR,DSN=CAI.CA7.LOADLIB,MEM=ICMDSECT PAGE ��1

NAME TTR SIZE ALIAS-OF AC --------- ATTRIBUTES --------

ICMDSECT ��FE2� ��18� �� FO RN RU IGCSTXXX �1��17 ��25� �� FO RN RU IGCS�XXX �1��1F ��EF� �� FO RN RU IGCS3XXX �1��28 ��1�B8 �� FO RN RU IGG�19X7 ��2626 ��A� �� FOL2ADDON ��27�F ��238 �� FO

L2B�INIT �1�221 ��3�48 �1 FOL2B�SVC �1��31 ��8 �� FO RN RU

L2B�SVCT �1�1�7 ��8 �� FO RN RUL2CCICB ��CE37 ��F8� �� FO

L2CCICSD ��CF�9 ��2�� FOL2CCIIN ��CF12 ��3A8 �� FOL2CCIIS ��CF1B ��56� �� FO

L2CCILET ��CF24 ��24� �� FO L2CCIRCV ��CF2D ��86� �� FO

� �

320 Commands Guide

LJCK

LJCK

The LJCK command lists JCL for a Unicenter CA-7 job. JCL is fetched from thesource indicated on the DB.1 panel. If no member name is provided on theDB.1 panel, then the member name is assumed to be the same as the jobname. JCL is fetched from the library indicated by the JCL ID (or its alternate)on the DB.1 panel unless the USE-OVRD-LIB value is Y, in which case LJCKattempts to locate the JCL on the override library (JCLID=254). LJCK keywordvalues for DATE, TIME, and SCHID can affect the display if scheduledoverrides such as #JI and #JO are used. The RMS step is inserted if required.If the Unicenter CA-7 interface with CA-Driver is active, LJCK displaysCA-Driver JCL modifications. Calls to CA-Driver are made after scheduledoverrides are applied and the RMS step is inserted. Defaults for run-timespecific Unicenter CA-7 reserved-name variables such as Unicenter CA-7 jobnumber are used when CA-Driver is invoked through LJCK. For additionalinformation about the use of CA-Driver, see the Interfaces Guide.

You can also use the LJCK command to validate JCL for a job that is notdefined on the Unicenter CA-7 database. However, the JCL must reside on aUnicenter CA-7 JCL library.

LJCK can be used to invoke Unicenter CA-JCLCheck to validate the JCL.


LJCK

��──LJCK─ ──,JOB=jobname ──┬ ┬───────────── ─────────────────────────�└ ┘──,DATE=yyddd

┌ ┐─MERGE──�─ ──┬ ┬─────────────────────────────── ──,LIST= ──┼ ┼─ERRORS─ ────────�

└ ┘──, JCLLIB= ──┬ ┬─nnn───────────── └ ┘─ONLY─── └ ┘─&xxxxxxxxxxxxxx─

�─ ──┬ ┬─────────────── ──┬ ┬────────────────── ──┬ ┬──────────── ─────��└ ┘──,MEM=xxxxxxxx │ │┌ ┐─��1─ └ ┘──,TIME=hhmm

└ ┘──,SCHID= ──┴ ┴─nnn─

JOBDefines the job whose JCL is to be listed.

Required: Yes


LJCK

DATESpecifies the Julian date to be used in evaluating scheduled overrides (forexample, #JI and #JO statements).

Default: Current system date

Required: No

JCLLIBOverrides or specifies the library where the JCL resides. It can be used tooverride the JCLID/JCLLIB value on the DB.1 panel for this display if theJOB keyword is used. For example, if the JCLLIB for the library where theJCL for job X resides is &A but test JCL to be evaluated for the job resideson the library defined as JCLLIB=&ABC, then the following command canbe used:

LJCK,JOB=X,JCLLIB=&ABC

If a numeric index is indicated, use from 1 to 3 numeric characters tospecify a number between 000 and 255.

If a symbolic index is indicated, specify from 1 to 15 alphanumericcharacters prefixed by an ampersand.

LISTSpecifies the options used in listing JCL information.

Default: MERGE

Required: No

MERGESpecifies that the execution JCL for the specified job is to be evaluatedby Unicenter CA-JCLCheck. This is the default. If the full UnicenterCA-JCLCheck interface is used, then JCL substitutions, procedureexpansions, errors, and other messages returned by UnicenterCA-JCLCheck are displayed inline following the relevant execution JCLstatements. The display is similar to Unicenter CA-JCLCheck REPORT2. For more information about REPORT 2, see the UnicenterCA-JCLCheck User Guide . If the default Unicenter CA-JCLCheckinterface (common component) is used, a report is produced listing onlythose statements in error. This output is the same as the outputgenerated for LIST=ERRORS.

ERRORSSpecifies that the execution JCL for the specified job is to be evaluatedby Unicenter CA-JCLCheck, and that only those JCL statementsflagged in error with the associated diagnostic messages are to bedisplayed.

ONLYSpecifies that the execution JCL for the specified job is to be listed.Unicenter CA-JCLCheck is not invoked to evaluate the JCL. If theUnicenter CA-JCLCheck interface is not available, this is the only validLIST option.

322 Commands Guide

LJCK

MEMSpecifies the member whose JCL is to be listed if the job is not defined toUnicenter CA-7 or if the database definition is to be ignored. If no JCLLIBvalue is specified, LJCK attempts to locate JCL on the JCL library definedwith ID=0.

SCHIDSpecifies the schedule ID to be used in evaluating scheduled overrides (forexample, #JI and #JO statements).

Default: 001

Required: No

TIMESpecifies the time-of-day to be used in evaluating scheduled overrides (forexample, #JI and #JO statements).

Default: Current system time

Required: No

Concealed Values: Depending on the security options selected for yourinstallation, the following values may be concealed in the display:




LJCL

LJCL

The LJCL command lists the JCL for any Unicenter CA-7 job when the jobname is supplied. It can access any PDS, AllFusion CA-Panvalet, or AllFusionCA-Librarian data sets defined to Unicenter CA-7. This command lists the dataset name and the member name specified (or defaulted) on the DB.1 panel foreach job.

Note: Any undisplayable hexadecimal characters in the JCL are shown asperiods (.) in the output from the LJCL command.


LJCL

��──LJCL─ ──,JOB= ──┬ ┬─jobname── ──────────────────────────────────�� ├ ┤─jobname�─ └ ┘─�────────

JOBDefines the jobs whose JCL is to be listed.

Required: Yes

jobnameDefines a job name.




*Specifies all jobs defined in the database. The output from thisspecification can be quite lengthy and should be done using a batchterminal.

324 Commands Guide

LJCL

ExamplesLJCL,JOB=CA7JOB4

List JCL for job CA7JOB4.

LJCL,JOB=CA7�

List JCL for all jobs whose name begins with CA7.

LJCL,JOB=�

List JCL for all jobs.




LJCL Panel

� � LJCL,JOB=ROSDAILY

DSN=CSDCA7.JCLLIB(ROSDAILY) PAGE ��1 JOB=ROSDAILY

//ROSDAILY JOB HE67YFBH,SYSTEMS,CLASS=2,REGION=1�24K,TIME=1439 ��1 //�JOBPARM LINES=9999,FORMS=DPLX ��2 //�LOGONID @@@@@@@@ ��3 //�PASSWORD @@@@@@@@ ��4 //BACKUP EXEC PGM=LIBUTIL, ��5 // PARM=BACKUP ��6 //STEPLIB DD DSN=ROS1.ROSLIB,DISP=SHR ��7 //SYSPRINT DD SYSOUT=A ��8 //ROSLIB�� DD DSN=ROS1.ROSLIB��,DISP=OLD ��9 //ROSLIB�1 DD DSN=ROS1.ROSLIB�1,DISP=OLD,DCB=BUFNO=56 ��1� //ROSLIB�2 DD DSN=ROS1.ROSLIB�2,DISP=OLD,DCB=BUFNO=56 ��11 //ROSLIB�3 DD DSN=ROS1.ROSLIB�3,DISP=OLD,DCB=BUFNO=56 ��12 //BACKUP DD DSN=ROS1.DAILY.BACKUP(+1),DISP=(,CATLG,UNCATLG), ��13 // UNIT=TAPE,DCB=(CTI��.GDG,BLKSIZE=2��), ��14 // LABEL=EXPDT=99�� 15 // EXEC PGM=IEFBR14,COND=(6,GT,BACKUP) ��16

//BACKUPTP DD DSN=ROS1.DAILY.BACKUP(+1),DISP=(OLD,DELETE) ��17 /� ��18� �


LJES

LJES

The LJES command displays the JES job number for all CPU jobs submitted byUnicenter CA-7 that reside in the active or prior-run queues. The active queuecontains information about jobs that are currently executing, while the prior-runqueue contains information about the last successful completion of each job.For jobs that are executing, the name of the most recently completed job stepis provided. It also shows the CPU (local or remote) on which executionoccurred, start time, and other execution-related information.


LJES

��──LJES─ ──┬ ┬───────────────────── ──┬ ┬────────────── ─────────────� │ │┌ ┐─�──────── │ │┌ ┐─ACT─

└ ┘──,JOB= ──┼ ┼─jobname── └ ┘──,Q= ──┼ ┼─PRN─ ├ ┤─jobname�─ └ ┘─�─── └ ┘─nnnn─────

�─ ──┬ ┬──────────────────── ──┬ ┬──────────────────────── ──────────�� │ │┌ ┐─�───── │ │┌ ┐─�───────────

└ ┘──,CPUID= ──┴ ┴─smfid─ └ ┘──,SYS= ──┼ ┼─systemname── └ ┘─systemname�─

JOBDefines the jobs to be listed.

Default: *

Required: No






nnnnDefines a JES job number that is to be displayed (active queue only).Multiple JES systems (nonshared spools) may create duplicate JES jobnumbers; however, depending upon timing, duplicates may or may notoccur in a single display.

326 Commands Guide

LJES

QSpecifies the queues from which the jobs should be listed.

Default: ACT

Required: No

ACTSpecifies only active queue job information.

PRNSpecifies only prior-run queue job information. Valid only when aspecific job name is supplied. Jobs in the prior-run queue show acondition code value instead of the name of the last step executed.

*Specifies both active and prior-run queue data for the job namespecified. This is valid only when a specific job name is supplied.

CPUIDSpecifies the CPU IDs for which jobs are to be listed.

Default: *

Required: No


smfidDefines only this specific CPU ID. The value is the SMF system ID.CPUID, as a search argument in the inquiry command, must match theSMF system identifier as defined to the OS system by the user andreceived by Unicenter CA-7 in the SMF records.


SYSSpecifies the application system names whose active queue information isto be listed.

Default: *

Required: No





LJES

Usage Notes

Jobs must execute on a JES system to show a JES number. For example, XPSjobs that run on a UNIX box do not have a JES number.

Unicenter CA-7 provides the JES number only if Unicenter CA-7 uses SMFtype-30 records; otherwise, the field states *NA*.

If Unicenter CA-7 NCF is installed, another column, CPU LOCATION appearson the display. The CPU LOCATION column indicates the location name in thenode table for where the job executes.

328 Commands Guide

LJES

ExamplesLJES

LJES,JOB=372

LJES,CPUID=81�2

LJES,JOB=DUSAZZ�1,Q=PRN

� � LJES JOB=�,Q=ACT,CPUID=� DATE=YY.DDD PAGE ��1

CA-7 JES SCH CA-7 START COMPLETE ENDING/ CPU CPUJOBNAME JOB# JOB# ID QUE DDD/HHMM DDD/HHMM LASTSTEP SPEC RUN

U7BATCH1 ��8� 219� ��1 ACT �19/1��5 �19/1�53 U11STEP ALL IPO1

SLIS-�� REQUEST COMPLETED AT 1�:�5:58 on YY.DDD� �


JOBNAMEIdentifies the name of the job as defined in the database. See NAME fieldon the DB.1 panel.

CA-7 JOB#Identifies the Unicenter CA-7 assigned job number.

JES JOB#Identifies the job number assigned by JES for this run of the job.

SCHIDIdentifies the schedule ID assigned when this job was brought into therequest queue.

CA-7 QUEIdentifies the queue name that contains the job information listed. This iseither ACT for active queue or PRN for prior-run queue.

STARTIdentifies the start day (in Julian format) and the time of day that the jobbecame active.

COMPLETEIdentifies for a job in the prior-run queue, the Julian date and time of daythat the job completed on OS. For a job in the active queue, this is the timethat the last step record was recorded.

ENDING/LASTSTEPIdentifies the last step successfully executed by this job.


LJES

CPU SPECIdentifies the specified submit data set SY number that is to be used for jobsubmission. ALL indicates that this job can be submitted to any CPU.

CPU RUNIdentifies the SMF identifier of the CPU that the job executed or isexecuting.

330 Commands Guide

LJOB

LJOB

The LJOB command lists job information from the Unicenter CA-7 database.Optional keywords and values are used to provide such job selection criteria asJulian date, time-of-day, number of DD statements, and job names. Informationdisplayed can include job characteristics, scheduling parameters,interdependencies with other work, JCL, documentation, and so forth.

Use the LJOB command to list information about CPU jobs. If scheduling hasbeen intentionally suspended with a DEMAND,SET=SKP or NXTCYCcommand, the JOB INFORMATION section of the list indicates NXTCYC=SKPor NXTCYC=OFF.


LJOB

┌ ┐─,───────────────��──LJOB──,─ ───� ┴┬ ┬─────────────── ──┬ ┬──────────────────── ───────��

└ ┘──keyword=value │ │┌ ┐─JOB────└ ┘──,LIST= ──┴ ┴─option─

Optional keywords and values are used to provide job selection criteria. Theycan be used in any combination to list the desired jobs. LIST specifies format ofdisplay.

Keywords and acceptable values are as follows. Unless specifically indicated,there are no defaults for these keywords. If a keyword is not entered, jobs arelisted regardless of that keyword's corresponding value in the database. If nokeywords are provided, all jobs in the database are listed. See the DB.1 panelin the Database Maintenance Guide for more information about most of thefollowing keywords.

Note: Generic requests may cause too many pages of output for onlineterminals. If so, the message CA-7.020 results. To correct this problem, indicatea specific request. Alternatively, use the Batch Terminal Interface.

ADATESpecifies to select jobs meeting minimum or (minimum,maximum) Juliandate range in the date portion of DB.1 panel field DONT SCHEDULEAFTER (YYDDD format).


minimumSpecifies to select jobs meeting minimum Julian date range.

(minimum,maximum)Specifies to select jobs meeting minimum,maximum Julian date range.


LJOB

ARFSETSpecifies to select jobs with this value in DB.1 panel field ARFSET.


*Specifies all ARFSET names.

arfsetDefines a specific ARFSET name.

arfset*Defines a generic ARFSET name.

ATIMESpecifies to select jobs meeting minimum or (minimum,maximum)time-of-day range in the time portion of DB.1 panel field DONT SCHEDULEAFTER (hhmm format).


minimumSpecifies to select jobs meeting minimum time-of-day range.

(minimum,maximum)Specifies to select jobs meeting minimum,maximum time-of-day range.

BDATESpecifies to select jobs meeting minimum or (minimum,maximum) Juliandate range in the date portion of DB.1 panel field DONT SCHEDULEBEFORE (YYDDD format).




BTIMESpecifies to select jobs meeting minimum or (minimum,maximum)time-of-day range in the time portion of DB.1 panel field DONT SCHEDULEBEFORE (hhmm format).




332 Commands Guide

LJOB

CLSSpecifies to select jobs with this value in DB.1 panel field CLASS.

Limits: 1 alphanumeric character from A to Z or 0 to 9

xSpecifies the class value of the job to select.

CONDSpecifies to select jobs meeting minimum or (minimum,maximum) numericvalue range in DB.1 panel field COND-CODE (nnnn format).


minimumSpecifies to select jobs meeting minimum numeric value range.

(minimum,maximum)Specifies to select jobs meeting minimum,maximum numeric valuerange.

CPUSpecifies to select jobs meeting minimum or (minimum,maximum) numericpercentage value range for CPU time as a percentage of elapsed time (nnformat).


minimumSpecifies to select jobs meeting minimum numeric percentage valuerange.

(minimum,maximum)Specifies to select jobs meeting minimum,maximum numericpercentage value range.

CPUTIMESpecifies to select jobs meeting minimum or (minimum,maximum) numericvalue range in DB.1 panel field CPU-TIME.

Limits: 5 numeric characters specified as mmmss, where mmm is minutesand ss is seconds



DDSSpecifies to select jobs meeting minimum or (minimum,maximum) numericvalue range for number of DD statements in its JCL (nnn format).



LJOB


DRCLASSSpecifies to select job with this value in DB.2 panel field DRCLASS.

DSNLEADSpecifies to select jobs meeting minimum or (minimum,maximum) numericvalue range in DB.1 panel field LEAD-TIME DSN (nn format).



DSNMSGSpecifies to select jobs with this value in DB.1 panel field DSN NOTFOUND. The value must be N or Y.

ELTSpecifies to select jobs meeting minimum or (minimum,maximum) numericvalue range in DB.1 panel field CLOCK-TIME (hhmm format).



EXECSpecifies to select jobs with this value in DB.1 panel field EXEC. The valuemust be N or Y.

HOLDSpecifies to select jobs with this value in DB.1 panel field HOLD. The valuemust be N or Y.

JCLIDSpecifies to select jobs with this value in DB.1 panel field JCL ID.

Limits: 1 to 3 numeric characters. The valid range is 0 to 254

JCLLIBSpecifies to select jobs with this value in DB.1 panel field JCLLIB.

Limits: 2 to 16 alphanumeric characters beginning with an ampersand (&)

JCLOVRDSpecifies to select jobs with this value in DB.1 panel field JCL-OVRD. Thevalue must be N or Y.

334 Commands Guide

LJOB

JOBSpecifies job names to be selected. See the DB.1 panel field JOB.


Default: *

*Specifies all job names.



JOBLEADSpecifies to select jobs meeting minimum or (minimum,maximum) numericvalue range in DB.1 panel field LEAD-TIME JOB (nn format).



JOBNETSpecifies JOBNET names to be selected. See DB.1 panel field JOBNET.

Default: *


*Specifies all JOBNET names.

jobnetDefines a specific JOBNET name.


jobnet*Defines a generic JOBNET name.


LATESSpecifies to select jobs meeting minimum or (minimum,maximum) numericvalue range of the number of times the job completed later than scheduleddue-out time (nnn format).




LJOB

LISTSpecifies the information to be listed for each job selected by the otherkeywords. If LIST is not specified on a generic request, a single linedescribing each job is output.

Default: JOB

JOBSpecifies Job data only.

ALLSpecifies all data related to the job (for example, schedules,documentation, steps, DDs, requirements, networks).

DEPJSpecifies jobs that are dependent on the job.

NODDSpecifies like ALL but excludes STEPDD information.

PROSSpecifies documentation information only.

RPTIDSpecifies report IDs associated with the job.

RQDSNSpecifies data set requirement information only.

RQEXCPSpecifies exception requirements only (NEXT-RUN=SKIP or ONLY).

RQJOBSpecifies job requirement information only.

RQMTSpecifies input requirements and output network information only.

RQNWKSpecifies input network requirements only.

RQUSRSpecifies user requirements only.

RQVRMSpecifies virtual resource requirements only.

SCHDSpecifies schedule information only.

STEPDDSpecifies job, step, and DD statement information.

TRIGSpecifies all jobs, data sets, and networks that trigger the job, as wellas all jobs that are triggered by the job.

336 Commands Guide

LJOB

LMNTDATESpecifies to select jobs meeting minimum or (minimum,maximum) Juliandate range for date of last maintenance update to the database (YYDDDformat).



LMNTTIMESpecifies to select jobs meeting minimum or (minimum,maximum)time-of-day range for time-of-day of last maintenance update to thedatabase (hhmm format).



LMNTTYPESpecifies to select jobs depending on type of last database maintenanceperformed on them. The possible values are the following:

ANLZSpecifies last maintenance by Unicenter CA-7 analyze commands.

DBMSpecifies last maintenance by Unicenter CA-7 database maintenancefacilities.

LOADSpecifies last maintenance by Unicenter CA-7 LOAD process.

SMFSpecifies last maintenance by System Management Facility feedback.

LRUNDATESpecifies to select jobs meeting minimum or (minimum,maximum) Juliandate range for date of the last run of the job (YYDDD format).



LRUNTIMESpecifies to select jobs meeting minimum or (minimum,maximum)time-of-day range for time-of-day of the last run of the job (hhmm format).



LJOB


LTERMSpecifies to select jobs with this value in DB.1 panel field LTERM. Thevalue is a logical terminal name.


MAINIDSpecifies to select jobs with this value in DB.1 panel field MAINID.

ALLSpecifies all main IDs.

SYnSpecifies main ID n.

/SYnSpecifies not main ID n.

MAINTSpecifies to select jobs with this value in DB.1 panel field MAINT. The valuemust be N or Y.

MEMBERSpecifies JCL member names to be selected.

Default: *

*Specifies all JCL member names.

memberDefines a specific JCL member name.


member*Defines a generic JCL member name.


MSGCLASSSpecifies to select jobs with this value in DB.1 panel field MSGCLASS. Thevalue must be a 1 alphanumeric character message class.

NXTCYCSpecifies to select jobs with DEMAND,SET=SKP or NXTCYC commandfunctions active.

OFFSpecifies scheduling has been discontinued.

SKPSpecifies skip only the next scheduled run.

338 Commands Guide

LJOB

OVRDLIBSpecifies to select jobs with this value in DB.1 panel field USE-OVRD-LIB.The value must be N or Y.

OWNERSpecifies owner value to be selected. See the DB.1 panel field OWNER.

Default: *

*Specifies all owner values.

ownerDefines a specific owner value.


owner*Defines a generic owner value.


PROMPTSSpecifies to select jobs with this value in DB.1 panel field PROMPTS. Thevalue must be N or Y.

PROSESpecifies to select jobs that have documentation defined through DB.4.1panel. The value must be N or Y.

PRTYSpecifies to select jobs meeting minimum or (minimum,maximum) numericvalue range in DB.1 panel field PRTY (nnn format).



REGIONSpecifies to select jobs meeting minimum or (minimum,maximum) numericvalue range in DB.1 panel field REGION (nnnn format).



RELOADSpecifies to select jobs with this value in DB.1 panel field RELOAD. Thevalue must be N, Y, or X.


LJOB

RESTARTSSpecifies to select jobs meeting minimum or (minimum,maximum) numericvalue range of the number of times the job has been restarted (nnn format).



RETAINSpecifies to select jobs with this value in DB.1 panel field RETAIN-JCL.The value must be N or Y.

RMSSpecifies to select jobs with this value in DB.1 panel field INSERT-RMS.The value must be N or Y.

ROSpecifies to select jobs with this value in DB.1 panel field RO. The valuemust be one to two alphanumeric characters.

RQLISTSpecifies to select jobs with this value in DB.1 panel fieldREQUIREMENT-LIST. The value must be N or Y.

RQMTMSGSpecifies to select jobs with this value in DB.1 panel field RQMTS NOTUSED. The value must be N or Y.

RUNSSpecifies to select jobs meeting minimum or (minimum,maximum) numericvalue range of the number of times the job has been executed (nnnnformat).



SCHEDULESpecifies to select jobs that have a calendar schedule defined. The valuemust be N or Y.

STEPRESTSpecifies to select jobs that can be restarted at step level. The value mustbe N or Y.

340 Commands Guide

LJOB

STEPSSpecifies to select jobs meeting minimum or (minimum,maximum) numericvalue range of the number of job steps in its JCL (nnn format).



SYSSpecifies system names to be selected. See the DB.1 panel field SYSTEM.

Default: *


*Specifies all system names.

systemDefines a specific system name.


system*Defines a generic system name.


TP1Specifies to select jobs meeting minimum or (minimum,maximum) numericvalue range for the number of TYPE1 tape drives (nnn format). See theDB.1 panel field TAPE DRIVES. Selection is based on TYPE1 M valueunless TYPE1 M is zero or less than for the specified TP1 minimum value;selection is then based on TYPE1 C value.



TP1CSpecifies to select jobs meeting minimum or (minimum,maximum) numericvalue range in DB.1 panel field TYPE1 C (nnn format).




LJOB

TP1MSame as TP1C keyword except values are for field TYPE1 M.



TP2Same as TP1 keyword except values are for TYPE2 tape drives.



TP2CSame as TP1C keyword except values are for field TYPE2 C.



TP2MSame as TP1M keyword except values are for field TYPE2 M.



USERIDSpecifies to select jobs with this value in DB.1 panel field UID.


VERIFYUsed to select jobs with this value in DB.1 panel field VERIFY. The valuemust be N or Y.

342 Commands Guide

LJOB

ExamplesLJOB,JOB=CA7JOB1,LIST=ALL

List all information about a single job.

LJOB,JOBNET=WEEKLYS,SYS=PAYROLL

List all jobs in network WEEKLYS with system PAYROLL.

LJOB,JOB=CA7�

List all jobs with names beginning with CA7. Even though only one line per jobis listed for any generic job name request, the output from this type of requestcould be quite lengthy and should be done using a batch terminal.

LJOB,JOB=�,LIST=RQMT

List all jobs with output network information and input requirements. Eventhough only one line per job is listed for any generic job name request, theoutput from this type of request could be quite lengthy and should be doneusing a batch terminal.


LJOB

� � LJOB,JOB=�

JOB=� DATE=YY.DDD PAGE ��1

JOB ----JCL---- SYSTEM USR MAIN PROSE SCHED --NUMBER OF- LAST-RUN NAME ID MEMBER -NAME- -ID -ID- DSNBR DSNBR STP DDS RUNS DATE/TIME

DUSAXX�1 �� DUSAXX�1 PAYROLL �� ALL ��26 ��14 ��4 �12 ��1 YYDDD/143� PERAA�1A �� PERAA�1A PERSONEL �� ALL �NONE� �NONE� ��3 �1� �� /�� PERAB�1A �� PERAB�1A PERSONEL �� ALL �NONE� �NONE� ��1 ��4 �� /�� PERAC�1A �� PERAC�1A PERSONEL �� ALL �NONE� ��27 ��5 �17 ��1 YYDDD/141� ACPBA�1W ��1 ACPBA�1W PAYABLES �� ALL �NONE� �NONE� ��4 �12 ��1 YYDDD/1411 ACPCA�1W ��1 ACPCA�1W PAYABLES �� ALL �NONE� �NONE� ��3 ��9 ��1 YYDDD/1411� �

LJOB,LIST=JOB Panel

� � LJOB,JOB=DUSAXX�1,LIST=JOB

JOB=DUSAXX�1 LIST=JOB DATE=YY.DDD PAGE ��1


DUSAXX�1 �� DUSAXX�1 PAYROLL 1�� /SY3 ��9 ��3 ��3 �12 ��73 YYDDD/133�

----------------------------- JOB INFORMATION -------------------------N -- SCHD RESOLUTION REQUIRED Y -- LOAD STEP TO BE EXECUTEDN -- OVERRIDE OF JCL REQUIRED N -- JOB MARKED AS MAINT ONLYN -- MANUAL VERIFICATION REQD N -- JOB SET FOR HOLD IN REQQY -- REQUIREMNTS TO BE LISTED N -- COMP TRIGGERS OTHER JOBSY -- AUTO-GENERATION OF 7 RMS Y -- JOB ELIGIBLE FOR PROMPTSY -- ERRORS FOR RQMT NOT USED Y -- JOB SET FOR EXEC on MAINY -- ERRORS FOR DSN NOT FOUND N -- JCL TO BE KEPT IN PRRN/Q

�A� . OWNER= USERID JCLLIB= �NUMERIC JCLID� ARFSET= �NONE��B� . LAST MAINTENANCE on YY.DDD AT HH:MM:SS VIA DBM BY OPERATOR:USERID�C� . JCL SET FOR RETRIEVAL FROM OVERRIDE LIB FOR NEXT RUN

�D� . CLASS=,MSGCLASS=B,REGION=�4�K,PRTY=�2,CPUTM=��1,ELAPTM=��9�E� . TAPE1: CALC=��,MANL=��,TAPE2: CALC=��,MANL=��,DRCLASS= �NONE�

�F� . LTERM=CONTROL,JOBNET=PAYWEEK1,NXTCYC=SKP�G� . DONT SCHEDULE BEFORE YYDDD AT �8�� AND AFTER YYDDD AT 23��H� . CONSIDER ABNORMAL END IF ..text..�I� . SATISFACTION LEAD TIME (HRS): JOB=�1 DSN=��J� . # OF TIMES LATE = nnn # OF TIMES RESTARTED = nnn

� �

Note: All lines A-J may not display, and a page break may occur between thelines.


JOB NAMEIdentifies the name defined in the database for this job.

JCL IDIdentifies the numeric INDEX assigned to the JCL statement that definesthe data set in which this member resides. ID=255 indicates that a symbolicINDEX is assigned to the JCL statement that defines the data set in whichthis member resides.

344 Commands Guide

LJOB

JCL MEMBERIdentifies the member name of the JCL that is executed by this job.

SYSTEM NAMEIdentifies the value from the SYSTEM field on the DB.1 panel.

USR IDIdentifies the value from the UID field on the DB.1 panel.


PROSE DSNBRIdentifies the Unicenter CA-7 generated DSNBR for the job documentationdefined for this job.

SCHD DSNBRIdentifies the Unicenter CA-7 generated DSNBR for the schedule memberdefined for this job.

NUMBER OF STPIdentifies the number of steps executed within this job.

NUMBER OF DDSIdentifies the number of DDs referenced by this job.

NUMBER OF RUNSIdentifies the number of times this job has successfully executed underUnicenter CA-7.

LAST RUN DATE/TIMEIdentifies the last time (start time) that the job ran successfully underUnicenter CA-7.

JOB INFORMATIONAll job information values are either Y or N.

SCHD RESOLUTION REQUIREDIdentifies whether this job's schedule information entered through theDB.2.1 panel needs to be RESOLVed.

OVERRIDE OF JCL REQUIREDIdentifies whether the QJCL requires modifying before job submission(see JCL-OVRD field on the DB.1 panel).

MANUAL VERIFICATION REQUIREDIdentifies whether this job has an initial requirement in the requestqueue for verification (see VERIFY field on the DB.1 panel).

REQUIREMENTS TO BE LISTEDIdentifies whether this job's requirements should be written to theLTERM indicated on the DB.1 panel upon initial queue entry.

AUTO-GENERATION OF 7 RMSIdentifies whether Unicenter CA-7 is to insert the RMS step (seeINSERT-RMS field on the DB.1 panel).


LJOB

ERRORS FOR RQMT NOT USEDIdentifies whether an error message should be produced and sent tothe LTERM specified on the DB.1 panel if this job shows to use a dataset, but while the job was executing, Unicenter CA-7 did not receiveSMF data indicating its use (see RQMTS NOT USED field on the DB.1panel).

ERRORS FOR DSN NOT FOUNDIdentifies whether an error message should be produced and sent tothe LTERM specified on the DB.1 panel if Unicenter CA-7 receivesSMF data from this job's execution for a data set that is not referencedby the job's database record (see DSN NOT FOUND field on the DB.1panel).

LOAD STEP TO BE EXECUTEDIdentifies whether this job should go through load processing the nexttime it is to be executed.

JOB MARKED AS MAINT ONLYIdentifies whether this job is to run as a maintenance job (see MAINTfield on the DB.1 panel).

JOB SET FOR HOLD IN REQQIdentifies whether the job should enter the request queue with an initialhold requirement (see HOLD field on the DB.1 panel).

COMP TRIGGERS OTHER JOBSIdentifies whether this job's successful completion triggers other jobsinto Unicenter CA-7.

JOB ELIGIBLE FOR PROMPTSIdentifies whether the LTERM (from the DB.1 panel) is notified on atimer basis should this job become late or need restarting (seePROMPTS field on the DB.1 panel).

JOB SET FOR EXEC on MAINIdentifies whether this is an executable job (see EXEC field on the DB.1panel).

JCL TO BE KEPT IN PRRN/QIdentifies whether on successful completion should a copy of the JCLthat was submitted for this job be kept (see RETAIN-JCL field on theDB.1 panel).

346 Commands Guide

LJOB

�A�OWNER. The security user ID associated with this job (see OWNER fieldon the DB.1 panel).

JCLLIB. The symbolic INDEX assigned to the JCL statement that definesthe data set in which this member resides. JCLLIB= *NUMERIC JCLID*indicates that a numeric INDEX is assigned to the JCL statement thatdefines the data set in which this member resides.

ARFSET. The name of the ARFSET used on this job.

�B�The date and time of the last maintenance performed on this job throughUnicenter CA-7 and the mode for this maintenance. Mode is indicated afterVIA as one of the following:

■ ANLZ - for updating that occurred through the RESANL command.

■ DBM - for updating of this record through the DSN panel.

■ LOAD - for updating of this record by the load of a job.

�C�The job's JCL is obtained from the override library for the next scheduled(or triggered) run.

�D�CLASS. Workload balancing class to be used for job submission (seeCLASS field on the DB.1 panel).

MSGCLASS. JES class that is used by this job (information only).

REGION. Region used by this job (information only).

PRTY. Initial workload balancing priority that is assigned to this job uponinitial queue entry.

CPUTM. CPU time (weighted average) for this job.

ELAPTM. Time (weighted average) between job submission and jobtermination.

�E�TAPE1. CALC. High-water mark number of TYPE1 tape drives used by anystep within this job as calculated by Unicenter CA-7.

TAPE1. MANL. Override of the Unicenter CA-7 calculated number ofTYPE1 tape drives used by this job (see TAPE DRIVES TYPE1 M field onDB.1 panel).

TAPE2. CALC. High-water mark number of TYPE2 tape drives used by anystep within this job as calculated by Unicenter CA-7.

TAPE2. MANL. Override of the Unicenter CA-7 calculated number ofTYPE2 tape drives used by this job (see TAPE DRIVES TYPE2 M field onDB.1 panel).

DRCLASS. The disaster recovery class assigned to this job.


LJOB

�F�LTERM. The logical terminal (STATION) that is to receive variousmessages regarding this job.

JOBNET. Value entered in the JOBNET field on the DB.1 panel.

NXTCYC. If the normally scheduled processing cycles of the job have beensuspended by the NXTCYC command, this value is SKP (for single cycle)or OFF (for all cycles until reset by the NXTCYC command).

�G�Dates and times to be resolved at the time a job record is to be broughtinto the request queue by schedule scan or a trigger (see the DONTSCHEDULE -- BEFORE and AFTER fields on the DB.1 panel). A job is notbrought in automatically if it is a true condition.

�H�Condition code tests to be performed to determine if the job has completedsuccessfully.

�I�Initial satisfaction lead time values for job and data set requirements. (Seethe SATISFACTION LEAD TIME field on the DB.1 panel.)

�J�Number of times the job has been considered late, and the number of timesthe job has been restarted.

LJOB,LIST=SCHD Panel

� � LJOB,JOB=DUSAXX�1,LIST=SCHD

JOB=DUSAXX�1 LIST=SCHD DATE=YY.DDD PAGE ��1

JOB ----JCL---- SYSTEM USR MAIN PROSE SCHED --NUMBER OF- LAST-RUNNAME ID MEMBER -NAME- -ID -ID- DSNBR DSNBR STP DDS RUNS DATE/TIME

DUSAXX�1 �� DUSAXX�1 PAYROLL 1�� /SY3 ��9 ��3 ��3 �12 ��73 YYDDD/133�-------------------------------- SCHEDULES -----------------------------------

CALENDAR SCALyy�3 ID=��1 ROLL=D INDEX=+��

SCAL= DOTM=�8�� LEADTM=�13� STARTM=�63� WEEKLY DAY=MON,FRI ID=��2 ROLL=D INDEX=+��

SCAL=7D DOTM=12�� LEADTM=�1�� STARTM=11�� DAILY

SLIA-�� REQUEST COMPLETED AT 16:��:�5 on YY.DDD� �

348 Commands Guide

LJOB

� � LJOB,JOB=DUSAXX�1,LIST=PROS

JOB=DUSAXX�1 LIST=PROS DATE=YY.DDD PAGE ��1


DUSAXX�1 �� DUSAXX�1 PAYROLL 1�� /SY3 ��9 ��3 ��3 �12 ��73 YYDDD/133�---------------------------------- PROSE -------------------------------THIS IS THE FIRST JOB IN THE TESTNTWK TO BE EXECUTED AND IS ASCHEDULED JOB. IT CONSISTS OF TWO STEPS. THE FIRST STEP RECEIVESA SET OF CONTROL CARDS AS INPUT, CREATES A DATASET CA7.TEST1 ASOUTPUT AND DEMANDS THE NEXT JOB DUSAXX�2 TO BE STARTED.

� �

LJOB,LIST=TRIG Panel

� � LJOB,JOB=DUSATAPE,LIST=TRIG

JOB=DUSATAPE LIST=TRIG DATE=YY.DDD PAGE ��1


DUSATAPE �� DUSATEST PAYROLL 1�� /SY3 ��9 ��3 ��3 �12 ��73 YYDDD/133�

----------------- TRIGGERED BY JOBS/DATASETS/NETWORKS -----------------JOB=DUSATPRM SCHID=�� QTM=�1�� LEADTM=��1� SUBMTM=��

------------------------- TRIGGERED JOBS ------------------------------JOB=DUSATGDG SCHID=�� QTM=�1�� LEADTM=��1� SUBMTM=��

SLIA-�� REQUEST COMPLETED AT 13:55:�8 on YY.DDD� �

� � LJOB,JOB=DUSAXX�1,LIST=STEPDD

JOB=DUSAXX�1 LIST=STEPDD DATE=YY.DDD PAGE ��1



------------------------- STEP AND DD INFORMATION----------------------�1 STEP1 PGM=IEBGENER REGION=��K TIME=1439,�� PSTEP=S1 ��RST��

��1 SYSIN TYPE=DUMMY ��2 SYSPRINT TYPE=SYSOUT

� �


LJOB

LJOB,LIST=RQMT Panel

� � LJOB,JOB=DUSAXX�1,LIST=RQMT

JOB=DUSAXX�1 LIST=RQMT DATE=YY.DDD PAGE ��1



------------------ REQUIREMENTS AND NETWORK CONNECTIONS --------------- NWK=TESTOTNW SCHID=�� NWKSCHID=��1 LEADTM=�1��

NWNBR=NW��3 SUBID=RPT12�5 DESC=BENEFITS �� OUTPUT ��DSN=CA7.LOADLIB �� PERM DSN ��

DSNBR=DS��4 SCHID=�� VRSN=�5135/194�CREATED BY ��NONE��

USR=SAMPLE USER REQUIREMENT SCHID=��

SLIA-�� REQUEST COMPLETED AT 15:59:49 on YY.DDD� �

LJOB,SYS=A/P,LIST=DEPJ Panel

� � LJOB,SYS=A/P,LIST=DEPJ

JOB=� LIST=DEPJ DATE=YY.DDD PAGE ��2

JOB ----JCL--- SYSTEM USR MAIN PROSE SCHED --NUMBER OF- LAST-RUNNAME ID MEMBER -NAME- -ID -ID- DSNBR DSNBR STP DDS RUNS DATE/TIME

JOB�1 �� JOB�1 A/P �� ALL �� nnnnnn �� /��

JOB�2 �� JOB�2 A/P �� ALL �� /��

JOB�3 �� JOB�3 A/P �� ALL �� /��

-------------------------- SUCCESSOR JOBS ------------------------ JOB=JOB�5 SCHID=��1 JOB=JOB�8 SCHID=��2

JOB�5 �� JOB�5 A/P �� ALL �� /��

JOB�6 �� JOB�6 A/P �� ALL �� /��

-------------------------- SUCCESSOR JOBS ------------------------ JOB=JOB13 SCHID=��

� �

350 Commands Guide

LJOBR

LJOBR

The LJOBR command lists computer resource requirement information aboutjobs. This command is similar to the LQR command, except that it listsresource information about any job in the database.


LJOBR

┌ ┐─,───────────────��──LJOBR──,─ ───� ┴┬ ┬─────────────── ──────────────────────────────�� └ ┘──keyword=value

Optional keywords and values are used to specify the jobs to be displayed.Only the jobs meeting all selection criteria specified are displayed. Forselection keywords and values available to both the LJOB and LJOBRcommands, see “LJOB” on page 331.

LJOBR has no LIST option.

Usage Notes

This command can also be used to determine all jobs that have specificresource requirements or ranges of requirements. Resource parameters can bespecified in any combination to obtain the desired information. This makes thecommand very useful in analyzing profiles of the Unicenter CA-7 workload.

ExamplesLJOBR,TP1=(�5,1�),SYS=BL�

LJOBR,TP1=(�5,1�),TP2=3,CPU=5�

LJOBR,CLS=A,ELT=(��5�,�1�1)

LJOBR,JOBNET=WEEKLYS,SYS=PAYROLL,TP1=(�2,�5)


LJOBR

� � LJOBR,JOB=D463XX�1 JOB=D463XX�1 DATE=YY.DDD PAGE ��1

JOB SYSTEM MAIN JOB CPU/ELAPS TAPE1 TAPE2 NBR REGN CPU% LAST-RUNNAME -NAME- -ID- C/PRT --TIME--- M/CAL M/CAL RUNS SIZE UTIL DATE/TIME

D463XX�1 TESTNTWK ALL A/��2 ��1/��1 ��/�� /�� 2 ��4�K �1.67 �5234/1416

SLIA-�� REQUEST COMPLETED AT �8:�1:13 on YY.DDD� �





JOB C/PRTIdentifies the workload balancing class and priority for this job.

CPU/ELAPS TIMEIdentifies the CPU time for the job in mmmss format and the elapsed runtime (CLOCK-TIME from the DB.1 panel) in hhmm format.

TAPE1Identifies the number of tape drives used under TAPE1. The M fieldrepresents a manual override made on the DB.1 panel. The CAL field is thenumber of tape drives used that was calculated either by LOAD processingor a RESANL command.

TAPE2Identifies the number of tape drives used under TAPE2. The M fieldrepresents a manual override made on the DB.1 panel. The CAL field is thenumber of tape drives used that was calculated either by LOAD processingor a RESANL command.

NBR RUNSIdentifies the number of times this job has successfully executed underUnicenter CA-7.

REGN SIZEIdentifies the region required for this job.

CPU% UTILIdentifies the percentage of the time that a job was getting actual CPU timeduring execution.

LAST RUN DATE/TIMEIdentifies the last time (start time) that the job ran successfully underUnicenter CA-7.

352 Commands Guide

LLIB

LLIB

The LLIB command lists a member of a AllFusion CA-Panvalet or AllFusionCA-Librarian data set. Although intended to be used for reviewing JCL, anycard-image data can be displayed from either of the two types of data sets.

Note: Any undisplayable hexadecimal characters in the member are shown asperiods (.) in the output from the LLIB command.


LLIB

��──LLIB─ ──,DSN=dsname ──,MEM=member ──┬ ┬───────── ────────────────��└ ┘──,LIST=N

DSNDefines the fully qualified data set name of the AllFusion CA-Panvalet orAllFusion CA-Librarian library that contains the member (MEM) to be listed.


Required: Yes

MEMDefines which member of the named library (DSN) to list.


Required: Yes

LISTSpecifies not to expand "includes." This is an optional keyword, and theonly value allowed is N for no expansion.


LLIB

ExamplesLLIB,DSN=PROD1.JCL,MEM=XXXXXXXX

"includes" expanded.

LLIB,DSN=PROD1.JCL,MEM=XXXXXXXX,LIST=N

"includes" not expanded.




LLIB Panel

� � LLIB,DSN=PROD1.JCL,MEM=ROSDAILY

DSN=PROD1.JCL PAGE ��1

//ROSDAILY JOB HE67YFBH,SYSTEMS,CLASS=2,REGION=1�24K,TIME=1439 ��1 //�JOBPARM LINES=9999,FORMS=DPLX ��2 //�LOGONID @@@@@@@ ��3 //�PASSWORD @@@@@@@@ ��4 //BACKUP EXEC PGM=LIBUTIL, ��5 // PARM=BACKUP ��6 //STEPLIB DD DSN=ROS1.ROSLIB,DISP=SHR ��7 //SYSPRINT DD SYSOUT=A ��8 //ROSLIB�� DD DSN=ROS1.ROSLIB��,DISP=OLD ��9 //ROSLIB�1 DD DSN=ROS1.ROSLIB�1,DISP=OLD,DCB=BUFNO=56 ��1� //ROSLIB�2 DD DSN=ROS1.ROSLIB�2,DISP=OLD,DCB=BUFNO=56 ��11 //ROSLIB�3 DD DSN=ROS1.ROSLIB�3,DISP=OLD,DCB=BUFNO=56 ��12 //BACKUP DD DSN=ROS1.DAILY.BACKUP(+1),DISP=(,CATLG,UNCATLG), ��13 // UNIT=TAPE,DCB=(CTI��.GDG,BLKSIZE=2��), ��14 // LABEL=EXPDT=99�� 15 // EXEC PGM=IEFBR14,COND=(6,GT,BACKUP) ��16

//BACKUPTP DD DSN=ROS1.DAILY.BACKUP(+1),DISP=(OLD,DELETE) ��17 /� ��18� �

354 Commands Guide

LLOCK

LLOCK

The LLOCK command lists the database elements that are locked. Lockedmeans Unicenter CA-7 has detected some element that is in error or that hasnot been defined to the Unicenter CA-7 database, and therefore is preventingthe processing of a job, network, or data set.

In addition to lock conditions, the list also indicates if scheduling of a CPU jobhas been intentionally suspended with a DEMAND,SET=SKP or NXTCYCcommand.


LLOCK

��──LLOCK──,─ ──┬ ┬──────────────────────── ──┬ ┬────────────── ──────�│ │┌ ┐─�──────── └ ┘──,LIST=NXTCYC├ ┤──JOB──(1) = ──┼ ┼─jobname── ──

│ │└ ┘─jobname�─├ ┤──DSN= NW.networkname ────└ ┘──DSNBR= ──┬ ┬─xxnnnnnn───

└ ┘─xx��nnnnn�─

�─ ──┬ ┬───────────────── ─────────────────────────────────────────��└ ┘──,SYS=systemname

Note:1 JOB, DSN, or DSNBR is required if SYS is omitted.

JOBDefines the jobs that are to be listed. If SYS is used, JOB is optional and ifomitted, JOB=* is assumed.

Default: *

Required: Yes (unless DSN OR DSNBR is specified)





*Specifies all jobs are to be considered based on the SYS parameter.This is the default only if SYS= is provided. systemname must be aspecific application name; it cannot be generic.


LLOCK

DSNDefines a database index entry for networks to be listed. Enter either aspecific network or just the three characters NW. to list all networks. DSN isrequired unless DSNBR, JOB, or SYS is used, in which case it must beomitted.

Limits: 1 to 8 alphanumeric characters following NW. prefix

Required: Yes (unless JOB, SYS, or DSNBR is specified)

DSNBRDefines a specific or generic Unicenter CA-7 assigned network or schedulenumber identifying the elements to be listed.

Required: Yes (unless JOB, SYS, or DSN is specified)

xxnnnnnnDefines a specific network or schedule number where xx is the prefixdenoting the type of entry desired, and nnnnnn is the Unicenter CA-7assigned number (leading zeros can be omitted). Valid prefix values areNW, SI, SJ, or SO.

xx00nnnnn*Defines a generic network or schedule number where xx is the prefixdenoting the type of entry desired and nn...* is the generic UnicenterCA-7 assigned number (maximum of seven digits). An asterisk appearsafter the last significant digit. Do not omit leading zeros from thenumber value specified. Valid prefix values are NW, SI, SJ, or SO. Usea value of S* to list all SI, SJ, and SO schedules.

LISTSpecifies that only those schedules modified with a NXTCYC orDEMAND,SET=SKP command are to be listed. NXTCYC is the only validentry.

Required: No

SYSSpecifies an application system name whose locked jobs are to be listed.The value must be the specific application system name as defined foreach job on the DB.1 panel. If SYS is used with JOB, the jobs specifiedmust have a system name matching the SYS value to be listed. If SYS isused, DSN and DSNBR must be omitted.


Required: No

356 Commands Guide

LLOCK

Required Action for a Locked Job

If the display shows the job is LOCKED IN LOAD, this indicates that the lastattempt to load or reload the job failed. To correct this problem, reissue theLOAD command. If the LOAD is successful, it unlocks the job. If the LOAD isunsuccessful, Unicenter CA-7 produces error messages at the master station(LTERM=MASTER) indicating why the job is locked.

If this job is currently loading, wait for the load to complete then reissue theLLOCK command.

If the display shows SCHEDULE INFORMATION IS LOCKED, this indicatesthat the job or network schedule needs resolution. Issue the RESOLVcommand for the job or network to correct the problem.

Suspended Scheduling Messages

If the display shows IS NOT TO BE SCHEDULED, the job is not locked.However, scheduling of the job has been suspended with a NXTCYC,SET=OFFcommand.

If the display shows IS TO BE SKIPPED ON NEXT SCHEDULED CYCLE, thejob is not locked. However, scheduling of the job has been suspended with aDEMAND,SET=SKP or NXTCYC,SET=SKP command.


LLOCK

ExamplesLLOCK,DSN=NW.

LLOCK,JOB=CA7JOB1

LLOCK,JOB=CA7�,SYS=CA7

LLOCK,DSNBR=SJ�

LLOCK,DSNBR=SJ��2�

Lists schedule numbers from SJ000020 through SJ000029.

LLOCK,DSNBR=SJ��2�

Lists schedule numbers from SJ000200 through SJ000299.

� � LLOCK,JOB=DUSAXX�1

JOB=DUSAXX�1 DATE=YY.DDD PAGE ��1

JOB=DUSAXX�1 SYSTEM=PAYROLL.IS LOCKED FOR THE FOLLOWING REASON(S):

THE JOB SCHEDULE INFORMATION IS LOCKED

SLIJ-�� COMPLETED AT 16:�7:41 on YY.DDD� �

358 Commands Guide

LNTWK

LNTWK

The LNTWK command lists workstation network information from the UnicenterCA-7 database. Optional keywords and values control the amount of datapresented and the format of the data.


LNTWK

��──LNTWK──,─ ──┬ ┬──NW=network ────────────── ──────────────────────�├ ┤──DSN= ──┬ ┬─NW.────────────│ │└ ┘──NW.networkname└ ┘──DSNBR= ──┬ ┬──NWnnnnnn ── ──

├ ┤──NW��nnnnn� └ ┘─NW�────────

�─ ──┬ ┬─────────────────── ───────────────────────────────────────�� │ │┌ ┐─DSN───

└ ┘──,LIST= ──┼ ┼─ALL─── ├ ┤─PROS── ├ ┤─SCHD── ├ ┤─STN─── └ ┘─USERS─

NWSpecifies the network name. Use NW. for generic network requests.


Required: Yes (unless DSN or DSNBR is specified)

DSNSpecifies the Unicenter CA-7 index data set entry name for the networkinformation to be listed.

Required: Yes (unless NW or DSNBR is specified)

NW.When coded by itself, causes all networks to be listed in network namesequence.

NW.networkDefines a specific network name, in up to eight characters (following theNW. prefix), to be listed.

DSNBRDefines the Unicenter CA-7 assigned database network number for thenetwork whose information is to be listed.

Required: Yes (unless NW or DSN is specified)

NWnnnnnnDefines the Unicenter CA-7 assigned network number in up to sixcharacters with a prefix of NW. Leading zeros can be omitted.


LNTWK

NW00nnnnn*Defines a Unicenter CA-7 generic network number in up to seven digitspreceded with NW and terminated with an asterisk. Leading zerosMUST NOT be omitted.

NW*Causes all networks to be listed in network number sequence.

LISTSpecifies the options for the amount of database information to be listed.

Default: DSN

Required: No

DSNSpecifies network data.

ALLSpecifies all network data, including documentation and schedules. Thisoption is not valid for a generic request.

PROSSpecifies all documentation and network data. This option is not validfor a generic request.

SCHDSpecifies all schedules and network data. This option is not valid for ageneric request.

STNSpecifies all station names and network data.

USERSSpecifies all jobs connected to the network and network data.

ExamplesLNTWK,NW=DATASET1

LNTWK,NW=NW.DATASET1,LIST=USERS

LNTWK,NW=NW.DATASET1,LIST=ALL

LNTWK,DSNBR=NW6

LNTWK,DSNBR=NW6,LIST=USERS

LNTWK,DSNBR=NW�

LNTWK,DSN=NW.,LIST=USERS

360 Commands Guide

LNTWK

LNTWK,LIST=ALL Panel

� � LNTWK,DSNBR=NW2,LIST=ALL

LIST=ALL DSNBR=NW2 DATE=YY.DDD PAGE ��1

�------- NETWORK ------� SCHED PROSE NUMBER LAST MAINTENANCE NETWORK NAME DSNBR TYPE DSNBR DSNBR ST JOB -DATE/TIME TYPE- SUBID

TESTONWK NW��2 OUTPT SO��1 PP��12 �3 ��1 �5�19/1245 DBM INSTALL

LAST MAINTENANCE on yy.ddd AT hh:mm:ss VIA xxx BY OPERATOR:yyyyyyyy

------------------------------ STATION NAMES --------------------------BURST TRIM BINS

-------------------------------- SCHEDULES ---------------------------- ID=��1 INDEX=+�� WKSTA=(�1,DOTM=11��,LEADTM=�2��,DAY=��) WKSTA=(�2,DOTM=13��,LEADTM=�1��,DAY=��) WKSTA=(�3,DOTM=153�,LEADTM=��3�,DAY=��)

--------------------- NETWORK/JOB CROSS REFERENCE --------------------

JOB=DUCCXX�1 NUMBER OF TIMES USED=�1

� �

� � LNTWK,DSNBR=NW�

LIST=DSN DSNBR=NW� DATE=YY.DDD PAGE ��1

�------- NETWORK ------� SCHED PROSE NUMBER LAST MAINTENANCE NETWORK NAME DSNBR TYPE DSNBR DSNBR ST JOB -DATE/TIME TYPE- SUBID

TIMECARD NW��3 INPUT SI��17 PP��8 �3 ��6 YYDDD/1628 DBM PAY��1-WPAYCHEKS NW��4 OUTPT �NONE� �NONE� �1 �� YYDDD/1223 DBM PAY�2�-WCHKRGSTR NW��5 OUTPT �NONE� �NONE� �3 �� YYDDD/125� DBM PAY�22-W

LABRDIST NW��6 OUTPT SO��39 �NONE� �1 �� YYDDD/�932 DBM PAY�21-W BENEFITS NW��7 OUTPT SO��1 �NONE� �2 ��9 YYDDD/1127 DBM PAY�19-W

ACCRUALS NW��8 OUTPT �NONE� �NONE� �4 ��1 YYDDD/1�14 DBM PAY�31-W� �


NETWORK NAMEIdentifies the network name as defined in the database.

NETWORK DSNBRIdentifies a number automatically assigned to a network when it is added tothe database.

NETWORK TYPEIdentifies the type of entry:

INPUTPreprocessing

OUTPUTPostprocessing


LNTWK

SCHD DSNBRIdentifies a number automatically assigned to a network schedule when it isadded to the database.

PROSE DSNBRIdentifies a number automatically assigned to a network's documentationentry when it is added to the database.

NUMBER STIdentifies the number of workstation entries within this network.

NUMBER JOBIdentifies the number of jobs connected to this network.

LAST MAINTENANCE DATE TIMEIdentifies the last date and time an update was made to the networkdefinition.

LAST MAINTENANCE TYPEIdentifies the means of the update:

ANLZIdentifies XREF analyze command.

DBMIdentifies database maintenance.

NETWORK SUBIDIdentifies the sub-ID of the network.

362 Commands Guide

LOAD, LOADH

LOAD, LOADH

The LOAD/LOADH commands create or recreate job profile data in thedatabase. Job profiles should agree with the current JCL. Therefore, anychanges to the JCL must be resynchronized with the database by loading thejob. See the RELOAD field in the DB.1 panel as an alternative to thiscommand.

Use the LOADH command to indicate that the job is to be entered into thequeue in Unicenter CA-7 hold status to allow for manual release at a futuretime.

Use of this command causes the rest of the job's JCL to be flushed. The jobreturns to the request queue with a JCL error.


LOAD LOADH

��─ ──┬ ┬─LOAD── ──,JOB=jobname ──┬ ┬────────── ──┬ ┬──────────── ───────�└ ┘─LOADH─ └ ┘──,CLASS=x └ ┘──,DOTM=hhmm

�─ ──┬ ┬────────────────────── ──┬ ┬────────────── ───────────────────�└ ┘──, ──┬ ┬──JCLID=nnn ──── └ ┘──,LEADTM=hhmm

└ ┘──JCLLIB=&x...x

�─ ──┬ ┬──────────────────── ──┬ ┬────────────────── ─────────────────�└ ┘──,MAINID= ──┬ ┬─ALL── │ │┌ ┐─1───

├ ┤──SYn ─ └ ┘──,SCHID= ──┴ ┴─nnn─├ ┤──/SYn└ ┘──-SYn

�─ ──┬ ┬──────────── ──────────────────────────────────────────────��└ ┘──,TIME=hhmm

JOBDefines the job name of the job to be loaded. Value is the job name definedin the database or the member name in a JCL library where the JCL for thejob resides. See JCLID below.


Required: Yes

CLASSSpecifies the workload balancing class for resource checking.


Required: No

DOTMDefines a due-out time-of-day for load processing.

Default: Assumes current time plus lead time


LOAD, LOADH

Limits: 2 to 4 numeric characters specified as mm where hh can be hours0 through 24 and mm can be minutes 0 through 59

Required: No

JCLIDDefines the JCL data set that contains the execution JCL to be submitted. Ifused, the value must be a numeric INDEX associated with the desired JCLdata set (on the JCL statement in the initialization file). For moreinformation about the initialization file, see the Systems Programmer Guide.This field or the JCLLIB field is required if the job is not defined in thedatabase. JCLID and JCLLIB are mutually exclusive.



JCLLIBDefines the JCL data set that contains the execution JCL to be submitted. Ifused, the value must be a symbolic INDEX associated with the desired JCLdata set (on the JCL statement in the initialization file). For moreinformation about the initialization file, see the Systems Programmer Guide.This field or the JCLID field is required if the job is not defined in thedatabase. JCLID and JCLLIB are mutually exclusive.




LEADTMDefines an elapsed lead time for load processing.

Default: 1 hour (if omitted)


Required: No


Required: No



364 Commands Guide

LOAD, LOADH



SCHIDDefines the job schedule ID to be used for this job.

Default: 1

Limits: 1 to 3 numeric characters 1 through 255

Required: No (See Note)

Note: If the SCHEDULE statement in the initialization file specifiesSCHID=YES, this parameter is required.

TIMEEstablishes a submit time requirement for the job.


Required: No

Examples LOAD,JOB=USERJOB1,SCHID=14

LOADH,JOB=USERJOB2,JCLID=3

LOADH,JOB=USERJOB9,DOTM=14��,LEADTM=2�

Usage Notes

■ The LOAD process builds the database profile for a new job or rebuilds theprofile for a job whose JCL was changed. This profile can also be built by aDEMAND/DEMANDH (for a new job that is not defined to Unicenter CA-7)or by any other run of the job if the DB.1 panel RELOAD indicator is on.However, when DEMANDed or RELOADed, the job proceeds to normalexecution after the load step is executed.

■ When using LOAD/LOADH, if the job was not previously defined toUnicenter CA-7, the job name value for JOB must be the same as the JCLmember name that contains the job's JCL. In addition, the JCLID parametermust be specified to point Unicenter CA-7 to the proper JCL data set.

■ The corresponding DB.1 panel option RELOAD=Y performs the LOADprocess as the first step of the job whenever it is run the next time. Thisfield is automatically set to Y when a REPL is done through the UnicenterCA-7 JCL facility. The indicator is set back to RELOAD=N when loadprocessing successfully completes.


LOAD, LOADH

■ Each LOAD command results in the execution of a batch job with the samejob name as the production job, or if specified in the initialization file DBASEstatement, a job name derived from the LDJOBNM parameter. If using theLDJOBNM parameter, the JCL JOB statement must provide room for aneight-character job name.

■ Normal data set availability checking is performed by the operating systembased on DISP parameters on DD statements in the JCL. This could be aproblem when LOAD is requested for a job that references a data setcurrently in use, such as online database files. It may be more convenientto set RELOAD to Y on the DB.1 panel for this type of job.

■ In a JES3 environment, jobs that are submitted by the LOAD commandhave the same data set, device, and volume setup characteristics as thesubject job whose profile data is being created or updated. It may be moredesirable, in the JES3 environment, to use the DB.1 panel RELOAD optionto avoid unnecessary mount requests for data sets not required for just theLOAD process.

■ If there are any scheduled JCL overrides in the JCL, the resulting profile inthe database reflects the net effect of these overrides based on the currentdate, time of day, and SCHID values.

■ If workload balancing is being used, the job being loaded is scheduled usingthe default WLB job class for LOAD if the CLASS= keyword is not specified.(See the description of the LOADCLASS parameter on the OPTIONSstatement in the initialization file in the Systems Programmer Guide.)

■ The LOAD command cannot be used for a job that has been marked asnonexecutable (for example, EXEC=N) on the DB.1 panel.

■ If the LOADDSNS keyword is used on the DBASE statement in theinitialization file, then the LOAD process does not build any DD or data setinformation for jobs that are marked MAINT=Y on the DB.1 (JOB) panel.

■ If the JOB statement of a job being loaded has the RESTART keywordspecifying a step for the job to begin execution, the LOAD step does notexecute. To LOAD this job, the RESTART keyword should be omitted.

■ If VRMDD=DEF or VRMDD=YES is coded on the OPTIONS statement inthe Unicenter CA-7 initialization file, then VRM resource definitions for thisjob are dynamically modified when the job is LOADed. For more informationabout VRM Device Control, see the Database Maintenance Guide.

366 Commands Guide

LOC

LOC

The LOC command lists catalog contents for one or more data sets. Thisfunction is available on the UT Menu panel as FUNCTION value 19 or on anyother menu or formatted panel as FUNCTION value UT.19.


LOC

��──LOC─ ──,DSN=dsname ──┬ ┬──────────────── ───────────────────────��└ ┘──,VOLSER=volser

DSNDefines the data set whose catalog contents are to be listed. The name canbe a fully qualified name, a generic request, or a relative request for ageneration data set. A generic request is specified by the desired indexlevels followed by a period.


Required: Yes

VOLSERDefines the volume serial number that contains the CVOL catalog to belisted. If the high-level node is defined in the master catalog, this parameteris not needed. Otherwise, it should be coded.


Required: No

Usage Notes

A generic request for data sets whose catalog entries are in the master catalogreceive the message that the data set is not found. This is a restriction of SVC26 that is used to process this command.

ExamplesLOC,DSN=USER.

LOC,DSN=USER.FILE1,VOLSER=12B345

LOC,DSN=USER.GDG.FILE(-1)


LOGIN/LOGOUT

LOGIN/LOGOUT

The LOGIN command logs the start of workstation tasks for both networks.

The LOGOUT command logs the completion of workstation tasks for bothnetworks.

Input Workstation Networks

This function is available on the QM.6 panel.

This command has the following format for input workstation networks:

LOGIN LOGOUT

��─ ──┬ ┬─LOGIN── ──,JOB= ──┬ ┬─jobname─── ──,STATION=station ──────────� └ ┘─LOGOUT─ └ ┘─jobnumber─

�─ ──┬ ┬───────────────── ─────────────────────────────────────────��└ ┘──,INITS=xxxxxxxx

JOBDefines the unique Unicenter CA-7 job name or the job number that wasassigned when the network was placed in the preprocess queue. The jobname can be used to log the first station only and the job number must beused thereafter.

Required: Yes

jobnameDefines the job name.


jobnumberDefines the job number.


STATIONDefines the name of the workstation that is to be logged in or out.


Required: Yes (unless first station in the network)

INITSDefines any user information to be posted to the workstation record.


Required: No

368 Commands Guide

LOGIN/LOGOUT

Note: This could be used to allow users to enter their names or initialswith the command. This information is placed in the log and appears oninquiries.

Examples

Input Workstation Networks:

LOGIN,JOB=17,STATION=KEYPUNCH

Log in workstation KEYPUNCH that is part of the network referenced byUnicenter CA-7 job number 17. No user information to be posted.

LOGOUT,JOB=17,STATION=KEYPUNCH,INITS=CLERK1

Log out workstation KEYPUNCH that is part of the network referenced byUnicenter CA-7 job number 17. CLERK1 is the user information to be posted tothe workstation and logged.

Output Workstation Networks

This function is available on the QM.7 panel.

This command has the following format for output workstation networks:

LOGIN LOGOUT

��─ ──┬ ┬─LOGIN── ──,JOB= ──┬ ┬─jobname─── ──,NW=network ───────────────� └ ┘─LOGOUT─ └ ┘─jobnumber─

�─ ──,STATION=station ──┬ ┬──────────── ──┬ ┬───────────────── ────────�└ ┘──,FORCE=YES └ ┘──,INITS=xxxxxxxx

�─ ──┬ ┬────────────── ────────────────────────────────────────────��└ ┘──,SUBID=subid

JOBDefines the unique Unicenter CA-7 job name or the job number assigned tothe job and its output workstation networks. Job name can be used only forthe first station in a network and the job number must be used thereafter.

Required: Yes

jobnameDefines the job name.


jobnumberDefines the job number.



LOGIN/LOGOUT

NWDefines the name of the network to which the station belongs. The valuemust be the network name defined in the database.


Required: Yes (for first station unless SUBID is used)

STATIONDefines the station to be logged in or out. Value must be the station name.


Required: Yes (unless first station in the network)

FORCESpecifies to allow the logging in of an output workstation network prior tocompletion of the CPU job to which it is associated. If used the value mustbe entered as shown.

Required: No

INITSDefines any user information to be posted to the workstation record.


Required: No

Note: This could be used to allow users to enter their names or initialswith the command. This information is placed in the log and appears oninquiries.

SUBIDDefines additional information to identify the station and network to belogged in or out. If used, the value is as defined in the database (orspecified when the network was demanded). SUBID can be used instead ofNW for the first station in a network. When substituting for NW, SUBID isrequired.

Default: Spaces


Required: No

Examples

Output workstation networks:

LOGIN,JOB=163,NW=REPTS,STATION=STAT1,INITS=ABC

LOGIN,JOB=294,NW=REPTS,STATION=STAT1,SUBID=PAYR1234

LOGOUT,JOB=163,NW=REPTS,STATION=STAT1

LOGOUT,JOB=WORKNET,SUBID=RPTN�1,INITS=DIST

370 Commands Guide

LPDS

LPDS

The LPDS command lists a card-image member of a partitioned data set (PDS)or a sequential data set. This command enables the user to review data in anyPDS or sequential data set. For other commands that can be used to reviewJCL, see JCL Inquiries on page 14.

Note: Any undisplayable hexadecimal characters in the member are shown asperiods (.) in the output from the LPDS command.


LPDS

��──LPDS─ ──,DSN=dsname ──┬ ┬───────────── ──┬ ┬──────────────── ─────��└ ┘──,MEM=member └ ┘──,VOLSER=volume

DSNDefines the fully qualified data set name of either a sequential data set orthe name of a PDS containing a member (MEM) to be listed.


Required: Yes

MEMSpecifies that member of a named PDS (DSN) is to be listed.


Required: Yes, if listing from a PDS

VOLSERSpecifies the DASD volume on which the data set (DSN) resides. IfVOLSER is omitted, the data set must be a cataloged data set.

Required: No


LPDS

ExamplesLPDS,DSN=CA7.DSN1,MEM=M123,VOLSER=DBS1�1

LPDS,DSN=CA7.DSN2,MEM=M456

LPDS,DSN=CA7.SEQ.DATASET




LPDS Panel

� � LPDS,DSN=CA7.MACLIB,MEM=SASSSWKD DSN=CA7.MACLIB(SASSSWKD) PAGE ��1

MACRO ��1�� SASSSWKD ��2�� SPACE 5 ��3�� --------------------------------------------------------------------� ��4�� DSECT FOR THE SCHEDULE ELEMENT TO PRINT ROUTINE 'SASSCISE' ��5�� --------------------------------------------------------------------� ��6�� SPACE 2 ��7�� SWKDSECT DSECT ��8�� SWKLEN DS H - LENGTH OF THIS WORK AREA ��9�� SWKISE# DS H - NUMBER OF ISE'S LEFT TO PRINT ��1�� SPACE ��11�� SWKSRADR DS F - ADDRESS OF SCHEDULE RECORD ��12�� SPACE ��13�� SWKDBL DS D - DOUBLE WORD WORK AREA ��14�� SPACE ��15�� SWKISEAD DS F - ADDR OF CURRENT ISE ENTRY ��16�� SPACE ��17�� SWKSAVE DS 16F - SAVE AREA FOR CALLER'S REG'S ��18��

� �

372 Commands Guide

LPOST

LPOST

The LPOST command lists output network information from the postprocessqueue. This includes the status of all networks and whether they are late.Information, including documentation, can be listed in a variety of sequences.


LPOST

��──LPOST─ ──┬ ┬─────────────────────────── ──┬ ┬───────── ───────────�└ ┘── ─── ───,JOB= ──┬ ┬─�──────── └ ┘──,LIST=Q

├ ┤─jobname── └ ┘─jobname�─

�─ ──┬ ┬────────────────────────────── ─────────────────────────────�└ ┘── ─── ───,NW= ──┬ ┬─�────────────

├ ┤─networkname── └ ┘─networkname�─

�─ ──┬ ┬──────────────────────────────── ───────────────────────────�└ ┘──,SEG= ──┬ ┬─xxxxxxxx────────────

└ ┘──(xxxxxxxx,yyyyyyyy)

�─ ──┬ ┬───────────────────── ──┬ ┬──────────────── ──────────────────� │ │┌ ┐─NATV───── │ │┌ ┐─�────

└ ┘──,SEQ= ──┴ ┴─sequence─ └ ┘──,ST= ──┼ ┼─LATE─ └ ┘─HELD─

�─ ──┬ ┬─────────────────────────────── ──┬ ┬───────────────────── ──��└ ┘── ─── ───,STN= ──┬ ┬─�──────────── └ ┘──,SUBID= ──┬ ┬─�──────

├ ┤─stationname── ├ ┤─subid── └ ┘─stationname�─ └ ┘─subid�─


Required: No







LPOST

LISTSpecifies the amount of queue information requested. When specified, thevalue must be Q to list station data only. When LIST is not specified, thedisplay consists of a single description line for each queue record.

Required: No

NWSpecifies the network names for which information is to be selected.

Required: No

*Specifies all networks.

networknameDefines a specific network name.


networkname*Defines multiple networks represented by a generic network name.


SEGDefines a segment and subsegment of documentation to be listed. If asubsegment, use the form (xxxxxxxx,yyyyyyyy).

Required: No

xxxxxxxxDefines the name of a segment.


(xxxxxxxx,yyyyyyyy)Defines the names of a segment (xxxxxxxx) and subsegment(yyyyyyyy) enclosed in parentheses and separated by a comma.

Limits: 1 to 8 alphanumeric characters each


Default: NATV

Required: No

NATVIndicates native sequence (the order in which it is in the queue).

CA7Indicates Unicenter CA-7 assigned job number sequence.

DLTMIndicates deadline time sequence.

374 Commands Guide

LPOST

DOTMIndicates due-out time sequence.

JOBIndicates job name sequence.

NWIndicates network name sequence.

STAIndicates station name sequence.

SUBIDIndicates sub-ID name sequence.

STLimits the display to postprocess queue tasks with a particular status.

Default: *

Required: No

*All tasks.

HELDIndicates only jobs in hold status.

LATEIndicates only the late tasks.

STNSpecifies the station names for which information is desired.

Required: No

*Specifies all stations.

stationnameDefines a specific station name.


stationname*Specifies multiple stations represented by a generic station name.



LPOST

SUBIDSpecifies the sub-IDs of the network for which information is to be selected.

Required: No

*Specifies all sub-IDs.

subidDefines a specific sub-ID.


subid*Specifies multiple sub-IDs represented by a generic sub-ID name.


ExamplesLPOST

LPOST,SEQ=SUBID,SUBID=RPT�

LPOST,ST=LATE,STATION=OUTDEST

LPOST,LIST=Q Panel

� � LPOST,LIST=Q

LIST=Q DATE=YY.DDD PAGE ��1

CA-7 NETWORK NETWORK STATION JOB �----DAY(DDD) AND TIME(HHMM)-----� REF# SUBID DESC NAME NAME DEADLINE LOGIN DUE-OUT NW/LGOUT

��1�11 RPT12�5 ACCTRPT PRINTER DUSAXX�1 129/�8�� NONE� 129/�9�� ACCRUALS-------------------------STATION INFORMATION --------------------------

. NETWORK=TESTOTNW,DESTINATION=DELIVERY. SCHEDULE ID = ��1

. JOB DEMANDED

��1�12 RPT12�5 ACCTRPT DELIVERY DUSAXX�1 13�/�6�� NONE� 13�/�7�� ACCRUALS-------------------------STATION INFORMATION --------------------------

. NETWORK=TESTOTNW,ORIGIN=PRINTER,DESTINATION=HTERM1. SCHEDULE ID = ��1

. JOB DEMANDED� �


CA-7 REF#Identifies a system-generated number consisting of job number for the firstfour digits, the next two digits being the number of times the output networkis connected to the same job, and the last digit being the sequence numberof the workstation entry within the network.

376 Commands Guide

LPOST

NETWORK SUBIDIdentifies either the value from the JOBCONN,NWK (DB.3.4) panel, theSUBID entered on a DMDNW command, or blank if the network wasbrought into the postprocess queue with the DMDNW command with noSUBID= keyword.

NETWORK DESCIdentifies the value from either the DB.3.4 panel, the DESC entered on theDMDNW command, or blank if no DESC keyword was entered on theDMDNW command.

STATION NAMEIdentifies the LTERM name defined as a workstation within this network.

JOB NAMEIdentifies either the job whose connection on the DB.3.4 panel caused thenetwork to be brought into the postprocess queue, the JOB entered on aDMDNW command, or a system-generated name of DMD#nnnn for anetwork demanded with the DMDNW command with no JOB= keyword (thennnn being the job number).

DEADLINEIdentifies the date and time that this workstation entry should be logged into be completed by the due-out time.

LOGINIdentifies the date and time that this workstation entry was logged in. If alogin has not been done, this field is *NONE*.

DUE-OUTIdentifies the date and time that this workstation entry should be logged out.

NW/LGOUTIdentifies either the date and time that this workstation entry was logged outor the network name if a logout has not been done for this workstationentry.

STATION INFORMATIONIdentifies the network name, the name of the previous workstation (ORIGIN)if it is not the first workstation, the name of the next workstation(DESTINATION) if it is not the last workstation, and the SCHEDULE ID ofthis network. If the output network was brought in by a connection to a joband the job was demanded or triggered in, then that is reflected here also.


LPOST

LPOST Panel

� �LPOSTLIST= DATE=YY.DDD PAGE ��1

CA-7 NETWORK NETWORK STATION JOB �-----DAY(DDD) AND TIME(HHMM)-----�REF# SUBID DESC NAME NAME DEADLINE LOGIN DUE-OUT NW/LGOUT

��11�11 OVERHERE DMD#��11 171/1753 �NONE� 171/18�3 WATCHME��11�12 OVERTHER DMD#��11 171/1953 �NONE� 171/2��3 WATCHME

��12�11 HTERM1 DMD#��12 171/1753 �NONE� 171/1953 TESTOTNW

SLIF-�� REQUEST COMPLETED AT 17:54:�3 on YY.DDD� �

378 Commands Guide

LPRE

LPRE

The LPRE command lists input network information from the preprocess queue.This includes the status of all networks and whether they are late. Information,including documentation, can be listed in a variety of sequences.


LPRE

��──LPRE─ ──┬ ┬─────────────────────────── ──┬ ┬───────── ────────────�└ ┘── ─── ───,JOB= ──┬ ┬─�──────── └ ┘──,LIST=Q

├ ┤─jobname── └ ┘─jobname�─

�─ ──┬ ┬────────────────────────────── ─────────────────────────────�└ ┘── ─── ───,NW= ──┬ ┬─�────────────

├ ┤─networkname── └ ┘─networkname�─

�─ ──┬ ┬──────────────────────────────── ───────────────────────────�└ ┘──,SEG= ──┬ ┬─xxxxxxxx────────────

└ ┘──(xxxxxxxx,yyyyyyyy)

�─ ──┬ ┬───────────────────── ──┬ ┬──────────────── ──────────────────� │ │┌ ┐─NATV───── │ │┌ ┐─�────

└ ┘──,SEQ= ──┴ ┴─sequence─ └ ┘──,ST= ──┼ ┼─LATE─ └ ┘─HELD─

�─ ──┬ ┬─────────────────────────────── ──┬ ┬───────────────────── ──��└ ┘── ─── ───,STN= ──┬ ┬─�──────────── └ ┘──,SUBID= ──┬ ┬─�──────

├ ┤─stationname── ├ ┤─subid── └ ┘─stationname�─ └ ┘─subid�─

JOBSpecifies the job names for which information is to be listed.

Required: No







LPRE

LISTSpecifies the amount of queue information requested. When specified, thevalue must be Q to list station data only. When LIST is not specified, thedisplay consists of a single description line for each queue record.

Limits: 1 alpha character

Required: No

NWSpecifies the network names for which information is to be listed.

Required: No


networknameDefines a specific network name.


networkname*Defines multiple networks represented by a generic network name.


SEGSpecifies a segment and subsegment of documentation to be listed. If asubsegment, use the form (xxxxxxxx,yyyyyyyy).

Required: No



(xxxxxxxx,yyyyyyyy)Defines the name of a segment (xxxxxxxx) and subsegment (yyyyyyyy)enclosed in parentheses and separated by a comma.



Default: NATV

Required: No


CA7Indicates Unicenter CA-7 job number sequence.


380 Commands Guide

LPRE



NWIndicates network name sequence.

STAIndicates station name sequence.

SUBIDIndicates sub-ID name sequence.

STLimits the display to preprocess queue tasks with a particular status.

Default: *

Required: No

*All tasks.

HELDIndicates only tasks in hold status.

LATEIndicates only late tasks.

STNSpecifies the station names for which information is desired.

Required: No


stationnameDefines a specific station name.


stationname*Defines multiple stations represented by a generic station name.


SUBIDSpecifies the sub-IDs of the network for which information is to be selected.

Required: No



LPRE



subid*Defines multiple sub-IDs represented by a generic sub-ID name.


ExamplesLPRE

LPRE,ST=LATE,SEQ=NW

LPRE,STATION=KEYPUNCH

LPRE,LIST=ALL Panel

� � LPRE,LIST=ALL

LIST=ALL DATE=YY.DDD PAGE ��1


��6��1 KEYSTATS SYSTSAVE CONSOLE DMD#��6 128/1511 �NONE� 128/1521 SYSTSAVE--------------------------STATION INFORMATION ------------------------

. NETWORK=TRIGINNW,DESTINATION=PRINTER. NETWORK TRIGGERS JOB(S). SCHEDULE ID = ��1

. JOB DEMANDED

��6��2 KEYSTATS SYSTSAVE PRINTER DMD#��6 129/1711 �NONE� 129/1721 SYSTSAVE--------------------------STATION INFORMATION ------------------------

. NETWORK=TRIGINNW,ORIGIN=CONSOLE. NETWORK TRIGGERS JOB(S). SCHEDULE ID = ��1. STATION LAST IN NETWORK

. JOB DEMANDED� �

� � LPRE

LIST= DATE=YY.DDD PAGE ��1


��6��1 KEYSTATS SYSTSAVE CONSOLE DMD#��6 128/1511 �NONE� 128/1521 SYSTSAVE��6��2 KEYSTATS SYSTSAVE PRINTER DMD#��6 129/1711 �NONE� 129/1721 SYSTSAVE��7��1 WEEKLY ENGINEER CONSOLE DMD#��7 128/1511 �NONE� 128/1521 ENGINEER

SLIF-�� REQUEST COMPLETED AT 16:�9:�� on YY.DDD� �

382 Commands Guide

LPRE


CA-7 REF#Identifies a system-generated number consisting of job number for the firstfour digits. The next two digits are zeros. The last digit is the sequencenumber of the workstation entry within the network.

NETWORK SUBIDIdentifies a value from either the NETWORK (DB.5) panel or the SUBIDentered on a DMDNW command.

NETWORK DESCIdentifies either the network name or the DESC entered on a DMDNWcommand.

STATION NAMEIdentifies the LTERM name defined as a workstation within this network.

JOB NAMEIdentifies either the job name from the DB.5 panel, the JOB= value on aDMDNW command or a system-generated name of DMD#nnnn for anetwork demanded with the DMDNW command and no JOB= keyword (thennnn being the job number).

DEADLINEIdentifies the date and time that this workstation entry should be logged into be completed by the due-out time.

LOGINIdentifies the date and time that this workstation entry was logged in. If alogin has not been done, this field shows *NONE*.

DUE-OUTIdentifies the date and time that this workstation entry should be logged out.

NW/LGOUTIdentifies either the date and time that this workstation entry was logged outor the network name if a logout has not been done for this workstationentry.

STATION INFORMATIONIdentifies the network name, the name of the previous workstation (ORIGIN)if it is not the first workstation, the name of the next workstation(DESTINATION) if it is not the last workstation, and the SCHEDULE ID ofthis network. If the network was brought in by the DMDNW command, thenthis is reflected here also.


LPROS

LPROS

The LPROS command lists documentation.

Unicenter CA-7 allows you to define documentation for each portion of theproduction workload through the Unicenter CA-7 documentation facility. Youcan define documentation in the Unicenter CA-7 database for each individualnetwork. Network documentation can be very helpful at the time a network isbeing processed. The Database Maintenance Guide describes how thisinformation is entered into the database.

Once defined, this documentation is available at any level, from the generaldescription of a network to the specific operating instructions for a workstationtask. Documentation can be listed by using the LPROS top line command orthe DB.4 panel. Either can be used in batch or online. It is your responsibility tokeep documentation accurate, current, and consistent with data centerstandards using the Unicenter CA-7 database maintenance documentationfacilities.


LPROS

��──LPROS────────────────────────────────────────────────────────�

�─ ──, ──┬ ┬──UID=user ─────────────────────────────────────── ───────�├ ┤──DSN=dsname ─────────────────────────────────────├ ┤──DSNBR= ──┬ ┬─PP�──────── ─────────────────────────│ │├ ┤──PPnnnnnn ──│ │└ ┘──PP��nnnnn�├ ┤──JOB=jobname ──┬ ┬──────────────── ──┬ ┬────────────│ │└ ┘──,STEP=stepname └ ┘──,DD=ddname├ ┤──SYS=system ─────────────────────────────────────└ ┘──NW=network ─────────────────────────────────────

�─ ──┬ ┬──────────────────── ──┬ ┬──────────────────────────────── ──��└ ┘──,LIST= ──┬ ┬─ALL──── └ ┘──,SEG= ──┬ ┬─xxxxxxxx────────────

└ ┘─NOLINK─ └ ┘──(xxxxxxxx,yyyyyyyy)

UIDSpecifies a user-defined name for which the user ID level documentationdata is to be listed.

Limits: 1 to 32 alphanumeric characters (using OS data set standards)

Required: No (at least one keyword is required)

384 Commands Guide

LPROS

DSNSpecifies the data set names of the data set level documentation membersto be listed. Can be entered either with or without the PP. prefix that isused in the Unicenter CA-7 index entry for the documentation data. Valuecan be specified as a specific or generic data set name. A generic name isindicated by coding the required levels of index (nodes) terminated by aperiod. At least one index level is required.


DSNBRSpecifies a single or generic Unicenter CA-7 database documentationmember number to be listed.


PP*Specifies all documentation members in the database.

PPnnnnnnSpecifies a specific database documentation member number wherePP is constant and nnnnnn is the Unicenter CA-7 databasedocumentation member number. Leading zeros can be omitted.

PP00nnnnn*Defines a generic database documentation member number specified inthe PP00nnnnnn format, up to seven digits, and terminated with anasterisk after the last significant digit. Leading zeros cannot be omitted.

JOBSpecifies a specific job name for which the job level documentation data isto be listed. Used by itself to list job level documentation.



STEPUsed only with JOB and DD keywords to list DD level documentation.


Required: No

DDUsed with JOB and STEP keywords to list the documentation data for theDD in the STEP of the JOB.


Required: No


LPROS

SYSSpecifies a specific application system name for which the system leveldocumentation data is to be listed.



NWSpecifies a specific network name for which the network leveldocumentation data is to be listed.



LISTSpecifies the desired options for listing documentation text. If omitted on ageneric member request, one line giving member level information is listedfor each member. If omitted on a specific member request, information islisted as if ALL had been specified.

Required: No

ALLCan be used with specific or generic member request to causedocumentation text to be listed. For specific member request, anydocumentation members linked to the requested member are listedfollowing text for the primary member. For generic member request, textfrom each member is listed as the member is read.

Note: Documentation members are linked to a member through theLINK field on the Unicenter CA-7 Database Maintenance DB.4 panels.

NOLINKCan be used with specific or generic member request to indicate thatlinked documentation is not to be listed with primary text.


Required: No





386 Commands Guide

LPROS

Usage Notes

Including documentation in the Unicenter CA-7 database is entirely optional.The documentation capability is provided only to assist the user. Documentationis not required to properly control work defined to Unicenter CA-7.

The LPROS command is used to display database documentation memberinformation, as well as the actual documentation itself. By following someuser-defined standard naming conventions for documentation, any questionsregarding production workload components or considerations can be answeredvery quickly with this command. For more information about definingdocumentation to the Unicenter CA-7 database, see the Database MaintenanceGuide.


LPROS

ExamplesLPROS,DSN=CA7.DSN1

LPROS,DSN=PP.CA7.

LPROS,DSN=PP.CA7,SEG=QDESC

LPROS,JOB=CA7JOB1,LIST=NOLINK

LPROS,DSNBR=PP29,SEG=(HTERM,QDESC)

LPROS,DSNBR=PP��3�

� � LPROS,JOB=DUSAXX�1

DSN=PP.DUSAXX�1.JOB DATE=YY.DDD PAGE ��1

------------- PROSE DATA SET NAME ------------- PPNBR PROS-TYPE

PP.DUSAXX�1.JOB .............................. PP��9 JOB

. PROSE-TYPE=JOB,JOB=DUSAXX�1,SYS=PAYROLL . DESC=

. LAST MAINTENANCE ON yy.ddd AT hh:mm:ss VIA xxx BY OPERATOR: yyyyyyy

THIS IS THE FIRST JOB IN THE TESTNTWK TO BE EXECUTED AND IS ASCHEDULED JOB. IT CONSISTS OF TWO STEPS.

� �

� � LPROS,DSN=PP.

DSN=PP. DATE YY.DDD PAGE ��1

------------- PROSE DATA SET NAME ------------- PPNBR PROS-TYPE

PP.AC��1V1�.JOB .............................. PP��26 JOB PP.ALICIA .................................... PP��1� USER PP.ART.SYS ................................... PP��16 SYSTEM PP.DANS.SYS .................................. PP��18 SYSTEM PP.DLMINWK1.NW ............................... PP��27 NETWORK PP.DUDLXX�1.JOB .............................. PP��28 JOB PP.DUSAHE�1.JOB .............................. PP��29 JOB� �

388 Commands Guide

LPRRN

LPRRN

The LPRRN command lists job information from the prior-run queue. Theprior-run queue contains information about the last successful completion ofeach job. Parameters allow the user to indicate which job or group of jobs isdesired, what information is to be reviewed, and the sequence of the displayeddata.


LPRRN

��──LPRRN─ ──┬ ┬───────────────────── ──┬ ┬──────────────────── ──────� │ │┌ ┐─�──────── │ │┌ ┐─STATUS─ └ ┘──,JOB= ──┼ ┼─jobname── └ ┘──,LIST= ──┴ ┴─option─ └ ┘─jobname�─

�─ ──┬ ┬──────────────────────────────── ──┬ ┬───────────────── ──────�| └ ┘──,SEG= ──┬ ┬─xxxxxxxx──────────── │ │┌ ┐─NATV─| └ ┘──(xxxxxxxx,yyyyyyyy) └ ┘──,SEQ= ──┼ ┼─DOTM─| └ ┘─JOB──

�─ ──┬ ┬────────────────────────────── ────────────────────────────�� │ │┌ ┐─�───────────

└ ┘── ─── ───,SYS= ──┼ ┼─systemname── └ ┘─systemname�─

JOBSpecifies the jobs to be listed.

Default: *

Required: No






LISTSpecifies the amount of information desired.

Default: STATUS

Required: No

STATUSSpecifies a single description line for each queue record. This is thedefault.


LPRRN

ALLSpecifies all data relative to the queue.

JCLSpecifies JCL information from the last good run of the job only. TheJCL is listed only for jobs marked RETAIN-JCL=Y on DB.1 panel. NoJCL is listed for non-executable jobs.




PROSSpecifies documentation data as it currently resides in the databaseonly.

QSpecifies job data only.

SEGSpecifies a segment and subsegment of documentation are to be listed. If asubsegment, use the form (xxxxxxxx,yyyyyyyy).

Required: No



(xxxxxxxx,yyyyyyyy)Specifies the name of a segment (xxxxxxxx) and subsegment(yyyyyyyy) enclosed in parentheses and separated by a comma.


390 Commands Guide

LPRRN

SEQSpecifies the display sequence of the requested information.

Default: NATV

Required: No


| DOTM| Indicates due-out time sequence.



Default: *

Required: No







LPRRN

ExamplesLPRRN

LPRRN,JOB=PAYROLL

LPRRN,SEQ=JOB,LIST=Q

LPRRN,JOB=PAYROLL,LIST=JCL

LPRRN Panel

� � LPRRN,JOB=D463� LIST=STATUS JOB=D463� DATE=YY.DDD PAGE ��1

JOB CA-7 DEADLINE START DUE-OUT COMPLETE CPU SCH ENTRY JOB NAME JOB# DDD/HHMM DDD/HHMM DDD/HHMM YYDDD/HHMM SPEC/RUN ID MODE STATUS

D463CLEN ��15 �34/1512 �34/1415 �34/1512 YYDDD/1415 ALL-IPO1 ��1 SSCN C-C�� D463XX�8 ��17 �34/1513 �34/1416 �34/1513 YYDDD/1416 ALL-IPO1 ��1 SSCN C-C�� D463XX�9 ��22 �34/1517 �34/1418 �34/1517 YYDDD/1418 ALL-IPO1 ��1 SSCN C-C�� D463XX�1 ��16 �34/1513 �34/1416 �34/1513 YYDDD/1416 ALL-IPO1 ��1 AUTO C-C�� D463XX1� ��2� �34/1517 �34/1419 �34/1523 YYDDD/1419 ALL-IPO1 ��1 AUTO C-C�� D463XX�7 ��25 �34/1519 �34/1422 �34/1524 YYDDD/1422 ALL-IPO1 ��1 DEMD C-C�� D463LIST ��5 343/1527 343/143� 343/1527 YYDDD/143� ALL-IPO1 ��1 DEMD C-C�� D4638VCT ��1 345/1818 345/1723 345/1818 YYDDD/1733 ALL-IPO1 ��1 AUTO C-C��

D463BTI ��2 317/1213 317/1113 317/1213 YYDDD/1113 ALL-IPO1 ��1 AUTO C-C�� D463LOGP ��2 �55/1232 �55/1137 �55/1232 YYDDD/1138 ALL-IPO1 ��1 DEMD C-C�� D463ICOM ��2 �44/1439 �44/1339 �44/1439 YYDDD/1339 ALL-IPO1 ��1 AUTO C-C�� D463XX�3 ��18 �34/1517 �34/1418 �34/1523 YYDDD/1418 ALL-IPO1 ��1 SSCN C-C�� D463XX�4 ��19 �34/1517 �34/1418 �34/1522 YYDDD/1418 ALL-IPO1 ��1 SSCN C-C�� D463XX�2 ��21 �34/1517 �34/1418 �34/1517 YYDDD/1418 ALL-IPO1 ��1 SSCN C-C�� D463XX�5 ��23 �34/1518 �34/1419 �34/1523 YYDDD/1419 ALL-IPO1 ��1 SSCN C-C�� D463XX�6 ��24 �34/1518 �34/1421 �34/1523 YYDDD/1421 ALL-IPO1 ��1 SSCN C-C��

SLIF-�� REQUEST COMPLETED AT 13:42:47 on YY DDD� �



CA-7 JOB#Identifies the Unicenter CA-7 job number that was assigned on initial queueentry.

DEADLINEIdentifies a calculated time by which this job should have started to havebeen completed by the due-out time.

STARTIdentifies the time that the job actually started.

DUE-OUTIdentifies the original due-out time for this job.

392 Commands Guide

LPRRN

COMPLETE YYDDDIdentifies the date that this job actually completed.

COMPLETE HHMMIdentifies the time that this job actually completed.

CPU SPEC/RUNIdentifies the MAINID specified for this job to be submitted to/and thesystem that it ran on.

SCHIDIdentifies the schedule ID that this job was brought into the request queueand ran under.

ENTRY MODEIdentifies how the job was brought into the queue. Values are:

ARFJIndicates an ARF job.

AUTOIndicates a triggered job.

DEMDIndicates a demanded job.

EXTLIndicates a job submitted external to Unicenter CA-7.

PSIndicates a job submitted by Personal Scheduling System.

RPETIndicates a repeated job.

SSCNIndicates a job record brought in by schedule scan.

XDEMIndicates a job brought in by the DEMAND command from an XPSclient.


JOB STATUSIdentifies the highest condition code passed by any step within this job.


LQ

LQ

The LQ command lists information about CPU jobs from the request, ready,and active queues. The queue information provided shows the status on allproduction activity known to Unicenter CA-7. This command is helpful indetermining the queue in which a job currently resides.


LQ LQUE

��─ ──┬ ┬─LQ─── ──┬ ┬────────────────────── ──┬ ┬─────────────────── ───� └ ┘─LQUE─ │ │┌ ┐─�───── │ │┌ ┐─�───


�─ ──┬ ┬────────────────────── ──┬ ┬────────────── ───────────────────�│ │┌ ┐─�───────── └ ┘──,LIST=option

└ ┘──,JOB= ──┼ ┼─jobname─── ├ ┤─jobname�── └ ┘─jobnumber─


�─ ──┬ ┬───────────────────── ──┬ ┬───────────── ─────────────────────�│ │┌ ┐─NATV───── └ ┘──,ST=display└ ┘──,SEQ= ──┴ ┴─sequence─

�─ ──┬ ┬────────────────────────────── ────────────────────────────�� │ │┌ ┐─�───────────



Default: *

Required: No


@ANYSpecifies to select jobs with any DRCLASS.

@NONESpecifies to select jobs with no DRCLASS.

394 Commands Guide

LQ

DRMODEIndicates the class of jobs to select.

Default: *

Required: No


YESSpecifies to select only jobs that entered the request queue whileUnicenter CA-7 was in Disaster Recovery mode.

NOSpecifies to select only jobs that entered the request queue whileUnicenter CA-7 was not in Disaster Recovery mode.


Default: *

Required: No









LQ

LISTSpecifies the amount of queue information requested.

Required: No

ALLIndicates all data related to the jobs.

JCLIndicates a JCL information only.

Depending on the security options your installation selected, thefollowing values may be concealed in the display:



PROSIndicates a documentation information only.

QIndicates a job data only.

RQMTIndicates all requirements information only. This can include a possibleARF error message as described in “ARF Error Messages” onpage 405.

STATUSIndicates unsatisfied requirements information only.

When a specific job is requested through the JOB parameter, the default isLIST=STATUS and all unsatisfied job requirements are listed. When JOBand LIST are not specified, a default display consisting of one descriptionline for each queue record is listed. If SEG is specified, the default isLIST=PROS.

Note: If RQMT or STATUS is specified, VRM requirements are listed forjobs in the ready queue with a status of W-RSRC.



Required: No

396 Commands Guide

LQ


Required: No





SEQControls the display sequence of the desired information.

Default: NATV

Required: No






STSpecifies the display criteria for the queue information. If omitted, all jobs inthe request, ready, and active queues are displayed.

Default: All jobs in the request, ready, and active queues

Required: No

ABNDIndicates only the jobs in the request queue or active queue that are inABEND status.

ARAEIndicates only jobs that encountered an ARF attach error.

ARFIndicates only jobs that are being tracked by ARF.


LQ

ARFHIndicates only jobs that are in ARF recovery status.

ARFJIndicates only ARF recovery jobs (entry mode=ARFJ).

CBADIndicates only the jobs in the request queue or active queue that are inBAD COMPLETION CODE status.

COMPIndicates jobs in the request queue that have completed successfullyand are waiting for Unicenter CA-7 completion processing.

HELDIndicates jobs in hold status.

JCLOIndicates jobs requiring JCL overrides.

JCLRIndicates only the jobs in the request queue, ready queue, or activequeue that are in JCL ERROR status.

LATEIndicates late jobs.

MANVIndicates jobs requiring manual verification.

NOIDIndicates only the jobs in the request queue, ready queue, or activequeue that are in SECURITY ERROR status.

REQUIndicates only the jobs in the request queue that are in REQUEUEstatus.

RSTRIndicates jobs in the request queue requiring restart.

RTRYIndicates only the jobs in the request queue that are in RETRY status.

SKELIndicates only the jobs in the request queue that are in SKELETONstatus.

SUBMIndicates jobs in the ready queue that have been submitted to the hostsystem for execution.

WRSCIndicates jobs in the ready queue that are waiting for resources.

398 Commands Guide

LQ







ExamplesLQ

LQUE,ST=LATE,SEQ=JOB

LQUE,LIST=STATUS,JOB=15

LQ,JOB=MYJOB1,LIST=ALL

LQ,JOB=MY�

LQ,ST=HELD,SEQ=CA7

LQ,SEQ=CA7

� � LQ DATE=YY.DDD PAGE ��1


HISTORY REQ �1�5 �98/1�25 �NONE� �98/1�25 ALL- ��1 DEMD ��2CA7LJESX REQ �1�2 �98/1�24 �98/1�� 98/1�3� ALL- ��1 SSCN ��1C7TST��1 REQ �1�6 �98/1�25 �NONE� �98/1�25 ALL- ��1 DEMD ��1C7TST��2 REQ �1�7 �98/1�25 �NONE� �98/1�25 ALL- ��1 DEMD ��1

SLIF-�� REQUEST COMPLETED AT �9:29:�3 on YY.DDD� �


LQ

� � LQ,JOB=DUSAZZ�1,LIST=RQMT

LIST=RQMT JOB=DUSAZZ�1 DATE=YY.DDD PAGE ��1


DUSAZZ�1 REQ ��5 128/1611 �NONE� 128/1611 /SY2- ��1 DEMD ��3 LATE---------------------------REQUIREMENTS STATUS ---------------------_ _ _ _ JCL OVERRIDES REQUIRED_ _ _ _ INTERNAL JOB=DUSAZZ13 DATE/TIME=YYDDD/HHMM


� � LQ,JOB=DUSAZZ�1,LIST=JCL

LIST=JCL JOB=DUSAZZ�1 DATE=YY.DDD PAGE ��1


DUSAZZ�1 REQ ��5 128/1611 �NONE� 128/1611 /SY2- ��1 DEMD ��4 R-REQUE---------------------------- JCL INFORMATION -----------------------

//DUSAZZ�1 JOB HE67YFSH,PAYROLL,REGION=4�K,TIME=��3,CLASS=B ��1�/�ROUTE PRINT RMT2 ��2�

/�JOBPARM ROOM=543 ��3� //�UCC7RESTART UCC7� �

� �LQ,JOB=215,SEG=QDESCLIST=PROS CA-7#=�215 DATE=YY.DDD PAGE ��1SEG=(QDESC)

JOB QUEUE CA-7 -DAY(DDD) AND TIME(HHMM)-- CPU SCH ENTRY MSTR JOB NAME NAME NUM DEADLINE SUB/START DUE-OUT SPEC/RUN ID MODE REQ STATUS

CA�7XX�1 REQ �215 173/1943 �NONE� 173/1943 ALL- ��1 DEMD ��1-------------------------- PROSE INFORMATION --------------------------�� JOB CA�7XX�1�� SCHEDULED JOB, FIRST IN THE NETWORK�� FIRST STEP

� �

400 Commands Guide

LQ

LQ,LIST= Panel

� �LQLIST= DATE=�5.295 PAGE ��1

JOB QUEUE CA-7 -DAY(DDD) AND TIME(HHMM)-- CPU SCH ENTRY MSTR JOB NAME NAME JOB# DEADLINE SUB/START DUE-OUT SPEC/RUN ID MODE REQ STATUS

JOEJOB1 RDY ��2 288/1135 �NONE� 288/1135 ALL- ��1 DEMD �� W-RSRCJOEJOB15 RDY ��8 288/1327 �NONE� 288/1327 ALL- ��1 DEMD �� W-RSRCSCA1��3D RDY ��21 295/�954 295/�919 295/1�� ALL- �99 SSCN �� LATETESTJOBA RDY ��24 295/1116 �NONE� 295/1116 ALL- ��1 DEMD �� W-RSRC

SLIF-�� REQUEST COMPLETED AT 13:35:53 on �5.295

� �



QUEUE NAMEIdentifies the queue where this job record currently resides. Values areREQ for request queue, RDY for ready queue, and ACT for active queue.

CA-7 JOB#Identifies the Unicenter CA-7 assigned job number.

DEADLINEIdentifies a calculated time by which this job should be active on the CPUto be completed by the due-out time.

SUB/STARTFor a job in the request queue, this is the time of a submit timerequirement. (The requirement can be manually posted, leaving a date/timevalue with no outstanding submit time requirement.) If there is a value for ajob in the ready queue, then this is the time that the JCL was written to thesubmit data set or internal reader. Until the first SMF step terminationrecord is received, this field is *NONE* for a job in the active queue.

DUE-OUTIdentifies the due-out time for this job.

CPU SPEC/RUNIdentifies the SPEC value is what CPU this job should be submitted to (seeMAINID field on DB.1 panel). The RUN value is what CPU the job has beensubmitted to. For 7UNI jobs, the RUN value can be 7UWT, which indicatesthat the process has not started on the submitted to platform.

SCHIDIdentifies the schedule ID assigned when this job was brought into therequest queue.


LQ

ENTRY MODEIdentifies how the job was brought into the queue. Values are:

ARFJIndicates an ARF recovery job.

AUTOIndicates a triggered job.

DEMDIndicates a demanded job.

EXTLIndicates a job submitted external to Unicenter CA-7.

LOADIndicates a job record to be loaded (brought in by the LOAD command).

PSIndicates a job submitted by Personal Scheduling System.

RPETIndicates a repeated job.

RUNIndicates a job brought in by the RUN command.

SSCNIndicates a job record brought in by schedule scan.

XDEMIndicates a job brought in by the DEMAND command from an XPSclient.

XPSIndicates a job brought in from an XPS client using the RUN commandwith the REF option.

XRUNIndicates a job brought in from an XPS client using the RUN command.


MSTR REQIndicates the number of outstanding master requirements for a job record.

JOB STATUSIndicates the indication of the job's current disposition. Values and theirmeanings are:



402 Commands Guide

LQ


E-ARFATTIndicates an error occurred during the attempt to attach ARF definitions.This can result if the ARFSET specified is not defined. A diagnosticmessage may have been written to the Unicenter CA-7 log, the OSconsole, or to the trailer queue for the job (in which case it can bedisplayed using LQ,JOB=x,LIST=ALL).

E-ARFERRIndicates the job encountered an error in the ARF processing. Do aLARFQ command for the job to get more specific information.

E-SEGERRIndicates the job has been requeued to the request queue because the Unicenter CA-7 job submission task was unable to read a securitysegment for the job.


LOADINGIndicates the job completed execution of a LOAD-only run and iscompleting the LOAD process. This status is for jobs in the requestqueue.

QJCLIndicates this job is in the request queue with zero masterrequirements. At the time the command was issued, Unicenter CA-7was processing a SAVE or REPL function on the QM.5 (QJCL) panelfor this job.




R-NOUIDIndicates during submission, if no valid USERID is available, a check ofthe SUBNOID parameter is done to determine if a job can be submittedwithout an ID. With SUBNOID set to NO, the job moves back to therequest queue with a status of R-NOUID.


LQ

R-REQUEIndicates the job has been requeued to the request queue using theREQUEUE command or the Q function on the QM.1 panel.

R-TRLFULIndicates at the time the job was active, Unicenter CA-7 requiredanother track to be obtained from the trailer queue to hold outputs. Atthe time that Unicenter CA-7 tried to get another track, either an out ofspace condition or an I/O error occurred.

RETRYIndicates a dynamic allocation error occurred during attach of JCL forthis job. At a user-specified time interval, a retry of the JCL attachoccurs.




W-RSRCIndicates a job is in the ready queue waiting on a resource that isunavailable.

404 Commands Guide

LQ

ARF Error Messages

ARHT ERR R15=xxxxxxxx, R0=yyyyyyyy, R1=zzzzzzzz

Reason: An ARF internal error occurred. Issued by SASSAIIS, SASSAILE, SASSAILS,SASSAISC.

ARQM ERR R15=xxxxxxxx, R0=yyyyyyyy, R1=zzzzzzzz

Reason: An ARF internal error occurred. Issued by SASSAIJC.

UNABLE TO LOCATE ARF TRAILER

Reason: The ARF segment in the trailer queue could not be located. ARF will not beable to monitor this run of the job. Cancel the job and DEMAND it again. Issued bySASSARFA.

ARF ENVIRONMENT ERROR

Reason: One or more modules needed by ARF could not be located. Severe error.Issued by SASSARFA.

ARF ATTACH COMPLETE - nnnnnnnn

Reason: ARF will begin monitoring exceptions defined for this run of the job. Issued bySASSARFA.

NO ARF TESTS FOR nnnnnnnn

Reason: Although an ARFSET is associated with the job, no ARF definitions applied tothis run of the job. For example, if the only ARFSET definition specifies SID EQ 3 but thejob is running under SCHID=5, this message would be issued. Issued by SASSARFA.

SQ ERROR AT hhhh ERR=xxxx

Reason: An ARF internal error occurred. Issued by SASSARFA.

#ARFJI ERROR FOR nnnnnnnn ERR=xxxx/yyyy/zzzz

Reason: An ARF internal error occurred. Issued by SASSARFA.


LQP

LQP

The LQP command lists current job VRM and WLB information for jobs in therequest and ready queues. The display shows the current resources andpriorities assigned to each job in the queue. You can also use this commandwhen either VRM or WLB is not active.


LQP

��─ ──┬ ┬─LQP─── ──┬ ┬────────────────────── ──┬ ┬────────────── ───────�└ ┘─LQUEP─ │ │┌ ┐─�───────── └ ┘──,LIST=STATUS


�─ ──┬ ┬────────────────── ──┬ ┬───────────────── ────────────────────� │ │┌ ┐─��─ │ │┌ ┐─PRTY─

└ ┘──,SCHID= ──┴ ┴─nnn─ └ ┘──,SEQ= ──┴ ┴─JOB──

�─ ──┬ ┬────────────────────────────── ────────────────────────────�� │ │┌ ┐─�───────────


JOBSpecifies the jobs whose queue information is to be listed.

Default: *

Required: No








406 Commands Guide

LQP

LISTIndicates itemized status information messages about the jobs in thequeues. When specified, the value must be LIST=STATUS. If omitted,displays a single line for each job.

Required: No



Required: No

SEQIndicates the display sequence of the desired information.

Default: PRTY

Required: No

PRTYIndicates descending job priority sequence. The current priority isdetermined by the workload balancing system.


SYSIdentifies the application system names whose queue information is to belisted.

Default: *

Required: No







LQP

ExamplesLQP,JOB=DUS�,SYS=�,LIST=STATUS

LQP,SEQ=PRTY

LQUEP,JOB=DUSAXX�1

� � LQP

SEQ=PRTY DATE=YY.DDD PAGE ��1

JOB QUE CA-7 JOB TAPE1 TAPE2 CPU START TIME PRIORITYNAME NAME NMBR CLS NBR/PRTY NBR/PRTY %UTLIL/PRTY MINS/PRTY ORIG/NEW

A REQ ��3 A ��/�� /�� 1.667/��1 E�46/��1- 1��/�1�� CA�7LOGX REQ ��7 A ��/�� /�� 1.667/��1 E�5�/��1- 1��/�1�� U7TST��1 REQ ��5 A ��/�� /�� 1.667/��1 E�5�/��1- 1��/�1�� CA7PND�1 REQ ��4 A ��/�� /�� .556/��9- E�46/��1- 1��/��9�

SLIF-�� REQUEST COMPLETED AT �9:52:22 on YY.DDD� �

LQP,LIST=STATUS Panel

� � LQP,LIST=STATUS LIST=NSUB SEQ=PRTY DATE=YY.DDD PAGE ��1


BATCH��2 REQ �118 A ��/�� /�� .556/�� E�52/��1- 1��/��99. JOB IS IN REQUEST QUEUE

CA7FRCST REQ �115 A ��/�� /�� .417/��5- E�45/��1- 1��/��94. JOB IS ON HOLD

SLIF-�� REQUEST COMPLETED AT �9:38:29 on YY.DDD

� �

408 Commands Guide

LQP

LQP,SEQ=JOB Panel

� � LQP,SEQ=JOB

SEQ=JOB DATE=YY.DDD PAGE ��1


A REQ ��3 A ��/�� /�� 1.667/��1 E�43/��1- 1��/�1�� CA�7LOGH REQ ��6 A �1/�� /�� .111/�18- E�31/��1- 1��/��81 CA�7LOGX REQ ��7 A ��/�� /�� 1.667/��1 E�47/��1- 1��/�1�� CA7PND�1 REQ ��4 A ��/�� /�� .556/�1�- E�43/��1- 1��/��89 U7TST��1 RDY ��5 ? ..... JOB IS ALREADY SUBMITTED .....

SLIF-�� REQUEST COMPLETED AT �9:55:59 on YY.DDD� �


JOB NAMEIndicates the name of the job as defined in the database. See NAME fieldon the DB.1 panel.

QUE NAMEIndicates the queue where this job record currently resides. Values areREQ for request queue, RDY for ready queue, and ACT for active queue.

CA-7 NMBRIndicates the Unicenter CA-7 assigned job number.

JOB CLSIndicates the workload balancing class indication for this job. See CLASSfield on the DB.1 panel.

TAPE1Indicates the number of tape drives this job requires and the amount theoriginal priority of the job is adjusted due to tape drive use.


CPU %UTIL/PRTYIndicates the calculated CPU use (using CLOCK-TIME and CPU-TIME fromthe DB.1 panel) and the amount that the original priority of the job isadjusted due to this use.

START TIMEIndicates how early or late this job is and the amount that the originalpriority is adjusted due to the start time factor.

PRIORITYIndicates the original priority (priority when this command was entered) andthe new priority based on the rewards or penalties from the previous fields.


LQP

Usage Notes

For more information about possible non submitted reasons whenLIST=STATUS is entered, see “Usage Notes” on page 426.

410 Commands Guide

LQR

LQR

The LQR command lists workload balancing information about all job resourcerequirements from the Unicenter CA-7 queues. The queue information providedshows current resource requirements for each job.


LQR

��─ ──┬ ┬─LQR─── ──┬ ┬──────────────────── ───────────────────────────� └ ┘─LQUER─ │ │┌ ┐─�─────

└ ┘──,CPUID= ──┴ ┴─smfid─

�─ ──┬ ┬────────────────────── ──┬ ┬──────────────────── ─────────────� │ │┌ ┐─�───────── │ │┌ ┐─ALL── └ ┘──,JOB= ──┼ ┼─jobname─── └ ┘──,MAINID= ──┼ ┼──SYn ─

├ ┤─jobname�── ├ ┤──/SYn └ ┘─jobnumber─ └ ┘──-SYn

�─ ──┬ ┬────────────────── ──┬ ┬───────────────────── ────────────────� │ │┌ ┐─��─ │ │┌ ┐─NATV─────


�─ ──┬ ┬────────────────────────────── ────────────────────────────�� │ │┌ ┐─�───────────


CPUIDSpecifies the CPU IDs for which jobs are to be listed.

Default: *

Required: No


smfidDefines only jobs with this specific CPU ID. The value is the SMFsystem ID. CPUID as a search argument in the inquiry command, mustmatch the SMF system identifier as defined to the OS system by theuser and received by Unicenter CA-7 in the SMF records.


LQR

JOBIdentifies the jobs whose queue information is to be listed.

Default: *

Required: No








MAINIDSpecifies that only those jobs with this MAINID (as defined on the DB.1panel) are to be listed. Jobs defined with MAINID of ALL are selectedregardless of MAINID entered.

Default: ALL

Required: No

ALLSpecifies all MAINIDs.

SYnWhere n indicates a CPU assigned number as defined in theinitialization file CPU statement for which information is to be listed. (Formore information about the initialization file, see the SystemsProgrammer Guide.) The value of n can range from 1 to 7. If a slash (/)precedes the SYn, the only jobs selected are those that are denoted toexecute on /SYn.

-SYnWhere n indicates a CPU assigned number for which information is notto be listed. The value of n can range from 1 to 7.



Required: No

412 Commands Guide

LQR


Default: NATV

Required: No







Default: *

Required: No







LQR

ExamplesLQR,JOB=DUS�,MAINID=SY3

LQUER,MAINID=SY1

� � LQR DATE=YY.DDD PAGE ��1

JOB SYSTEM MAIN JOB CPU CA-7# CPU/ELAPS TOTAL TAPES CPU% SUBMITNAME -NAME- -ID- C/PRT -ID NUMBR --TIME--- TP1 TP2 UTIL DATE/TIME

ACPBA�1W PAYABLES ALL B/15� ��1� ��134/��26 �3 �1 �6.�3 �NONE�ACPCA�1W PAYABLES ALL B/1�� 14 ��238/��31 �2 �� 9.49 �NONE�FXABA�2M FIXASSET ALL A/12� ��17 ��43/��28 �� 3 �2.56 �NONE�PERAB�2M PERSONEL SY2 D/1�� 18 ��421/�121 �4 �� 5.37 �NONE�




SYSTEM NAMEIndicates the system name as defined on the DB.1 panel.

MAINIDIndicates the value from the MAINID field on the DB.1 panel.

JOB C/PRTIndicates the workload balancing class and priority for this job.

CPUIDIndicates the CPU where the job is currently executing or has executed.The ID is not filled in until the job initiation record is processed by UnicenterCA-7.

CA-7# NUMBRIndicates the Unicenter CA-7 assigned job number.

CPU/ELAPS TIMEIndicates the CPU and CLOCK TIME from the DB.1 panel.

TOTAL TAPESIndicates the number of TAPE1 devices, TAPE2 devices, or both that thisjob requires.

CPU% UTILIndicates the calculated CPU use (using CLOCK-TIME and CPU-TIME fromthe DB.1 panel).

414 Commands Guide

LQR

SUBMIT DATE/TIMEIndicates the Julian date and time this job was submitted.


LRDY

LRDY

The LRDY command lists job information from the ready queue. Thisinformation provides details on jobs that have all preexecution requirementssatisfied and are only waiting to be submitted to the host system. Jobs thathave been submitted but have not yet begun to execute remain in this queueuntil execution does begin and show a submit time. Status, documentation, andJCL are among the information that can be displayed.


LRDY

��──LRDY─ ──┬ ┬────────────────────── ──┬ ┬─────────────────── ───────� │ │┌ ┐─�───── │ │┌ ┐─�───


�─ ──┬ ┬────────────────────── ──┬ ┬────────────── ───────────────────�│ │┌ ┐─�───────── └ ┘──,LIST=option




�─ ──┬ ┬────────────────────────────── ────────────────────────────�� │ │┌ ┐─�───────────



Default: *

Required: No


@ANYIndicates to select jobs with any DRCLASS.

@NONEIndicates to select jobs with no DRCLASS.

416 Commands Guide

LRDY


Default: *

Required: No


YESIndicates to select only jobs that entered the request queue whileUnicenter CA-7 was in Disaster Recovery mode.

NOIndicates to select only jobs that entered the request queue whileUnicenter CA-7 was not in Disaster Recovery mode.


Default: *

Required: No









LRDY


Required: No

ALLAll data related to the job.

JCLJCL information only.




PROSDocumentation information only.

QJob data only.

RQMTAll requirements information only.

STATUSRequirements information only.

When LIST is not specified, a default display consisting of a singledescription line for each queue record is listed. However, when a specificjob is requested by the JOB parameter, the default is LIST=STATUS and alljob requirements are listed. If SEG is specified, the default is LIST=PROS.

Note: If RQMT or STATUS is specified, VRM requirements are listed forjobs in the ready queue with a status of W-RSRC.



Required: No

418 Commands Guide

LRDY


Required: No




Limits: 1 to 8 alphanumeric characters for each segment


Default: NATV

Required: No

NATVNative sequence (the order in which it is in the queue).

CA7Unicenter CA-7 assigned job number sequence.

DLTMDeadline time sequence.

DOTMDue-out time sequence.

JOBJob name sequence.

STSpecifies the display criteria for the queue information. If omitted, all jobs inthe ready queue are displayed.

Required: No

HELDJobs in hold status.

JCLRJobs with a JCL error status.

LATELate jobs.

SUBMJobs submitted to the host system for execution.


LRDY


Default: *

Required: No






ExamplesLRDY

LRDY,JOB=G4�1

� � LRDY

LIST= DATE=YY.DDD PAGE ��1


PERAC�1D RDY ��16 �84/1649 �84/1549 �84/1649 SY2- ��1 DEMD �� LATE WHSAA�1D RDY ��19 �84/173� �NONE� �84/18�� ALL- ��5 AUTO �� RUSH




QUEUE NAMERDY indicates that only the ready queue is listed.

CA-7 NUMIndicates the Unicenter CA-7 assigned job number.

DEADLINEIndicates a calculated time by which this job should be active on the CPUto be completed by the due-out time.

420 Commands Guide

LRDY

SUB/STARTIndicates the time that the job was written either to a submit data set or tothe internal reader if there is a date and time value here. A value of*NONE* denotes that this job has not yet been submitted.

DUE-OUTIndicates the due-out time for the job.

CPU SPEC/RUNIndicates the SPEC value is what CPU this job should be submitted to (seeMAINID field on DB.1 panel). The RUN value is what CPU the job has beensubmitted to.

SCHIDIndicates the schedule ID assigned when this job was brought into therequest queue.

ENTRY MODEIndicates how the job was brought into the queue. Values are:

ARFJARF recovery job.

AUTOIndicates triggered job.

DEMDDemanded job.

EXTLJob submitted external to Unicenter CA-7.

LOADJob record to be loaded (brought in by the LOAD command).

PSJob submitted by Personal Scheduling System.

RPETRepeated job.

RUNJob brought in by the RUN command.

SSCNJob record brought in by schedule scan.

XDEMJob brought in by the DEMAND command from an XPS client.

XPSJob brought in from an XPS client using the RUN command with theREF option.


LRDY

XRUNJob brought in from an XPS client using the RUN command.


MSTR REQIndicates the master requirement count. This field is zero for a job in theready queue.

JOB STATUSIndicates a condition on this job record. Possible values are:

LATEIndicates the job has not started by the DEADLINE DAY/TIME.

R-JCLERRIf the job is in the ready queue with this status, then a job purge recordwas received before a job initiation record.


422 Commands Guide

LRDYP

LRDYP

The LRDYP lists VRM or WLB information for jobs in the ready queue waitingto be submitted. This command is similar to the “LQP” on page 406. You canalso use this command when either VRM or WLB is not active.


LRDYP

��──LRDYP─ ──┬ ┬────────────────────── ──┬ ┬────────────── ───────────�│ │┌ ┐─�───────── └ ┘──,LIST=STATUS


�─ ──┬ ┬────────────────── ──┬ ┬───────────────── ────────────────────� │ │┌ ┐─��─ │ │┌ ┐─PRTY─

└ ┘──,SCHID= ──┴ ┴─nnn─ └ ┘──,SEQ= ──┴ ┴─JOB──

�─ ──┬ ┬────────────────────────────── ────────────────────────────�� │ │┌ ┐─�───────────



Default: *

Required: No








LISTDisplays status information about the jobs in the queue. When specified,the value must be LIST=STATUS. When omitted, lists only a single line foreach job.


LRDYP



Required: No


Default: PRTY

Required: No

PRTYInformation appears in descending job priority sequence. The currentpriority is determined by the workload balancing system.

JOBInformation appears in job name sequence.


Default: *

Required: No






ExamplesLRDYP

LRDYP,LIST=STATUS,SEQ=PRTY

424 Commands Guide

LRDYP

� � LRDYP

SEQ=PRTY DATE=YY.DDD PAGE ��1

JOB QUE CA-7 JOB TAPE1 TAPE2 CPU START TIME PRIORITY NAME NAME NMBR CLS NBR/PRTY NBR/PRTY %UTLIL/PRTY MINS/PRTY ORIG/NEW

FXABA�2M RDY �371 A ��/�� 3/�5� ��8.��/�1� E�52/��1- 1��/�159PERAC�1D RDY ��16 ..... JOB IS ALREADY SUBMITTED .....




QUE NAMERDY indicates listing only the ready queue.

CA-7 NMBRIndicates the Unicenter CA-7 assigned job number.

JOB CLSIndicates the workload balancing class indication for this job. See CLASSfield on the DB.1 panel.



CPU %UTIL/PRTYIndicates the calculated CPU use (using CLOCK-TIME and CPU-TIME fromthe DB.1 panel) and the amount that the original priority of the job isadjusted due to this use.

START TIMEIndicates how early or late this job is and the amount that the originalpriority is adjusted due to the start time factor.

PRIORITYIndicates the original priority (priority when this command was entered) andthe new priority based on the rewards or penalties from the previous fields.


LRDYP

Usage Notes

When LIST=STATUS is entered, the following non submittal reasons candisplay:

TYPE1 TAPE DRIVES MORE THAN ALLOWED PER JOB

TYPE1 TAPE DRIVES LESS THAN ALLOWED PER JOB

TYPE2 TAPE DRIVES MORE THAN ALLOWED PER JOB

TYPE2 TAPE DRIVES LESS THAN ALLOWED PER JOB

CLASS BARRIER REACHED

NO INITIATORS AVAILABLE

JOB IS LOCKED

JOB IS ON HOLD

JOB WILL EXCEED MAX AVAILABLE TAPE1 DRIVES

JOB WILL EXCEED MAX AVAILABLE TAPE2 DRIVES

JOB IS IN REQUEST QUEUE

CA-11 IS NOT ACTIVE

JOB PRIORITY LESS THAN THRESHOLD VALUE

CPU BARRIER REACHED

SUBMIT DATASET BUSY OR ERROR

JOB IS WAITING FOR VRM RESOURCES

426 Commands Guide

LRDYR

LRDYR

The LRDYR lists outstanding (unsatisfied) job resource requirement informationabout CPU jobs in the ready queue. This command is similar to “LQR” onpage 411.


LRDYR

��──LRDYR─ ──┬ ┬──────────────────── ──┬ ┬────────────────────── ─────� │ │┌ ┐─�───── │ │┌ ┐─�─────────

└ ┘──,CPUID= ──┴ ┴─smfid─ └ ┘──,JOB= ──┼ ┼─jobname─── ├ ┤─jobname�── └ ┘─jobnumber─

�─ ──┬ ┬──────────────────── ──┬ ┬────────────────── ─────────────────� │ │┌ ┐─ALL── │ │┌ ┐─��─

└ ┘──,MAINID= ──┼ ┼──SYn ─ └ ┘──,SCHID= ──┴ ┴─nnn─├ ┤──/SYn└ ┘──-SYn

�─ ──┬ ┬───────────────────── ──┬ ┬────────────────────────────── ───�� │ │┌ ┐─NATV───── │ │┌ ┐─�───────────

└ ┘──,SEQ= ──┴ ┴─sequence─ └ ┘── ─── ───,SYS= ──┼ ┼─systemname── └ ┘─systemname�─

CPUIDIndicates the CPU IDs for which jobs are to be listed.

Default: *

Required: No


smfidIndicates only jobs with this specific CPU ID. The value is the SMFsystem ID. CPUID as a search argument in the inquiry command, mustmatch the SMF system identifier as defined to the operating system bythe user and received by Unicenter CA-7 in the SMF records.


LRDYR


Default: *

Required: No








MAINIDIndicates that only those jobs with this MAINID (as defined on the DB.1panel) are to be listed. Jobs defined with MAINID of ALL are selectedregardless of MAINID entered.

Default: ALL

Required: No


SYnWhere n indicates a CPU for which information is to be listed. Thevalue of n can range from 1 to 7. If a slash (/) precedes the SYn, theonly jobs selected are those that are denoted to execute on /SYn.




Required: No

428 Commands Guide

LRDYR


Default: NATV

Required: No


CA7Information appears in Unicenter CA-7 job number sequence.

DLTMInformation appears in deadline time sequence.

DOTMInformation appears in due-out time sequence.

JOBInformation appears in job name sequence.


Default: *

Required: No







LRDYR

ExamplesLRDYR

LRDYR,MAINID=SY2

� � LRDYR

JOB=FXABA�2M DATE=YY.DDD PAGE ��1


FXABA�2M FIXASSET ALL A/12� ��17 ��43/��28 �� 3 �2.56 ��/��




SYSTEM NAMEIndicates the system name as defined on the DB.1 panel.

MAINIDIndicates the value from the MAINID field on the DB.1 panel.

JOB C/PRTIndicates the workload balancing class and priority for this job.

CPU IDNot applicable.

CA-7# NUMBRIndicates the Unicenter CA-7 assigned job number.

CPU/ELAPS TIMEIndicates the CPU and CLOCK TIME from the DB.1 panel.

TOTAL TAPESIndicates the number of TAPE1 devices, TAPE2 devices, or both that thisjob requires.

CPU% UTILIndicates the calculated CPU use (using CLOCK-TIME and CPU-TIME fromthe DB.1 panel).

SUBMIT DATE/TIMEIndicates the Julian date and time this job was submitted.

430 Commands Guide

LREQ

LREQ

The LREQ lists job information from the request queue for jobs that have beenscheduled into the queue, but still have preexecution requirements that must besatisfied before the job can execute. Jobs that have completed successfullyreturn temporarily to the request queue for job completion processing. Jobs thatrun and abnormally terminate are also returned to this queue to await restart bythe user. For information about how to display information on jobs waiting for arestart, see “LIST” on page 316.


LREQ

��──LREQ─ ──┬ ┬────────────────────── ──┬ ┬─────────────────── ───────� │ │┌ ┐─�───── │ │┌ ┐─�───


�─ ──┬ ┬────────────────────── ──┬ ┬──────────────────── ─────────────�│ │┌ ┐─�───────── └ ┘──,LIST= ──┬ ┬─ALL────└ ┘──,JOB= ──┼ ┼─jobname─── ├ ┤─JCL────

├ ┤─jobname�── ├ ┤─PROS─── └ ┘─jobnumber─ ├ ┤─Q────── ├ ┤─RQMT─── └ ┘─STATUS─



�─ ──┬ ┬────────────────────────────── ────────────────────────────�� │ │┌ ┐─�───────────



Default: *

Required: No


@ANYIndicates that jobs with any DRCLASS should be selected.

@NONEIndicates that jobs with no DRCLASS should be selected.


LREQ


Default: *

Required: No


YESIndicates to select only jobs that entered the request queue whileUnicenter CA-7 was in Disaster Recovery mode.

NOIndicates to select only jobs that entered the request queue whileUnicenter CA-7 was not in Disaster Recovery mode.


Default: *

Required: No








432 Commands Guide

LREQ


Required: No

ALLAll data related to the jobs.

JCLJCL information only.

Depending on certain security options selected for your installation, thefollowing values may be concealed in the display:



PROSDocumentation information only.

QJob data only.

RQMTAll requirement information only.

STATUSUnsatisfied requirement information only.

When LIST is not specified, a default display consisting of a singledescription line for each queue record is listed. However, when a specificjob is requested by the JOB parameter, the default is LIST=STATUS and allunsatisfied job requirements are listed. If SEG is specified, the default isLIST=PROS.



Required: No


LREQ


xxxxxxxxDefines the name of a segment.


(xxxxxxxx,yyyyyyyy)The names of a segment (xxxxxxxx) and subsegment (yyyyyyyy)enclosed in parentheses and separated by a comma.



Default: NATV

Required: No


CA7Unicenter CA-7 job number sequence.




STSpecifies the display criteria for the queue information. If omitted, displaysall jobs in the request queue.

Required: No

ABNDDisplays only the jobs that are in ABEND status.

CBADDisplays only the jobs that are in BAD COMPLETION CODE status.

COMPDisplays jobs in the request queue that have completed successfullyand are waiting for Unicenter CA-7 completion processing.

HELDDisplays jobs in hold status.

JCLODisplays jobs requiring JCL overrides.

434 Commands Guide

LREQ

JCLRDisplays only the jobs that are in JCL ERROR status.

LATEDisplays late jobs.

MANVDisplays jobs requiring manual verification.

NOIDDisplays only the jobs that are in SECURITY ERROR status.

REQUDisplays only the jobs that are in REQUEUE status.

RSTRDisplays jobs requiring restart.

RTRYDisplays only the jobs that are in RETRY status.

SKELDisplays only the jobs that are in SKELETON status.


Default: *

Required: No







LREQ

ExamplesLREQ,ST=HELD,SEQ=JOB

� � LREQ

JOB=ACPBA�1W DATE=YY.DDD PAGE ��1


ACPBA�1W REQ ��16 �84/1649 �84/1549 �84/1649 SY2- ��1 DEMD �� LATE




QUEUE NAMEIndicates the queue where this job record currently resides. Values areREQ for request queue, RDY for ready queue, and ACT for active queue.

CA-7 NUMIndicates the Unicenter CA-7 assigned job number.

DEADLINEIndicates a calculated time by which this job should be active on the CPUto be completed by the due-out time.

SUB/STARTFor a job in the request queue, this is the time of a submit timerequirement. If there is a value for a job in the ready queue, then this is thetime that the JCL was written to the submit data set or internal reader. Untilthe first SMF step termination record is received, this field shows *NONE*for a job in the active queue.

DUE-OUTIndicates the due-out time for the job.

CPU SPEC/RUNThe SPEC value is what CPU this job should be submitted to (see MAINIDfield on DB.1 panel). The RUN value is what CPU the job has beensubmitted to.

SCHIDIndicates the schedule ID assigned when this job was brought into therequest queue.

436 Commands Guide

LREQ

ENTRY MODEIndicates how the job was brought into the queue. Values are:


AUTOTriggered job.

DEMDDemanded job.

EXTLJob submitted external to Unicenter CA-7.

LOADJob record to be loaded (brought in by the LOAD command).

PSJob submitted by Personal Scheduling System.

RPETRepeated job.

RUNJob brought in by the RUN command.

SSCNJob record brought in by schedule scan.

XDEMJob brought in by the DEMAND command from an XPS client.

XPSJob brought in from an XPS client using the RUN command with theREF option.

XRUNJob brought in from an XPS client using the RUN command.


MSTR REQIndicates the number of outstanding master requirements for a job record.

JOB STATUSIndicates the job's current disposition. Values are:





LREQ

E-ARFATTIndicates an error occurred during the attempt to attach ARF definitions.This can result if the ARFSET specified is not defined. A diagnosticmessage may have been written to the Unicenter CA-7 log, the OSconsole, or to the trailer queue for the job (in which case it can bedisplayed using LQ,JOB=x,LIST=ALL).

E-SEGERRIndicates the job has been requeued to the request queue because theUnicenter CA-7 job submission task was unable to read a securitysegment for the job.


LOADINGIndicates the job completed execution of a LOAD-only run and iscompleting the LOAD process. This status is for jobs in the requestqueue.

QJCLIndicates this job is in the request queue with zero masterrequirements. At the time the command was issued, Unicenter CA-7was processing a SAVE or REPL function on the QM.5 (QJCL) panelfor this job.




R-NOUIDDuring submission, if no valid USERID is available, a check of theSUBNOID parameter is done to determine if a job can be submittedwithout an ID. With SUBNOID set to NO, the job is moved back to therequest queue with a status of R-NOUID.

R-REQUEIndicates the job has been requeued to the request queue using theREQUEUE command or the Q function on the QM.1 panel.

R-TRLFULAt the time the job was active, Unicenter CA-7 required another track tobe obtained from the trailer queue to hold outputs. At the time thatUnicenter CA-7 tried to get another track, either an out of spacecondition or an I/O error occurred.

438 Commands Guide

LREQ

RETRYIndicates a dynamic allocation error occurred during attach of JCL forthis job. At a user-specified time interval, a retry of the JCL attachoccurs.





LREQP

LREQP

The LREQP lists current job priority information about each job in the requestqueue. This command is similar to “LQP” on page 406.


LREQP

��──LREQP─ ──┬ ┬────────────────────── ──┬ ┬────────────── ───────────�│ │┌ ┐─�───────── └ ┘──,LIST=STATUS└ ┘──,JOB= ──┼ ┼─jobname───


�─ ──┬ ┬────────────────── ──┬ ┬───────────────── ────────────────────� │ │┌ ┐─��─ │ │┌ ┐─PRTY─

└ ┘──,SCHID= ──┴ ┴─nnn─ └ ┘──,SEQ= ──┴ ┴─JOB──

�─ ──┬ ┬────────────────────────────── ────────────────────────────�� │ │┌ ┐─�───────────



Default: *

Required: No








440 Commands Guide

LREQP

LISTDisplays status information about the jobs in the queue. When specified,the option must be LIST=STATUS. When omitted, only one line is listed foreach job.

Required: No



Required: No


Default: PRTY

Required: No

PRTYDescending workload balancing job priority sequence. The priority isdetermined by workload balancing.



Default: *

Required: No






ExamplesLREQP,JOB=DUSA�,SEQ=PRTY,SYS=SYS1

For panel samples, see the LQP panel on page 408.


LREQR

LREQR

The LREQR lists CPU resource requirement information for jobs in the requestqueue. This command is similar to “LQR” on page 411.


LREQR

��──LREQR─ ──┬ ┬──────────────────── ──┬ ┬────────────────────── ─────� │ │┌ ┐─�───── │ │┌ ┐─�─────────

└ ┘──,CPUID= ──┴ ┴─smfid─ └ ┘──,JOB= ──┼ ┼─jobname─── ├ ┤─jobname�── └ ┘─jobnumber─

�─ ──┬ ┬──────────────────── ──┬ ┬────────────────── ─────────────────�└ ┘──,MAINID= ──┬ ┬─ALL── │ │┌ ┐─��─


�─ ──┬ ┬───────────────── ──┬ ┬────────────────────────────── ───────�� │ │┌ ┐─NATV─ │ │┌ ┐─�───────────

└ ┘──,SEQ= ──┼ ┼─CA7── └ ┘── ─── ───,SYS= ──┼ ┼─systemname── ├ ┤─DLTM─ └ ┘─systemname�─ ├ ┤─DOTM─ └ ┘─JOB──

CPUIDIndicates the CPU IDs for which jobs are to be listed.

Default: *

Required: No


smfidIndicates only jobs with this specific CPU ID. The value is the SMFsystem ID. CPUID as a search argument in the inquiry command, mustmatch the SMF system identifier as defined to the operating system bythe user and received by Unicenter CA-7 in the SMF records.

442 Commands Guide

LREQR


Default: *

Required: No








MAINIDIndicates that only those jobs with this MAINID (as defined on the DB.1panel) are to be listed. Jobs defined with MAINID of ALL are selectedregardless of MAINID entered.

Required: No


SYnWhere n indicates a CPU assigned number as defined in theinitialization file CPU statement for which information is to be listed. (Formore information about the initialization file, see the SystemsProgrammer Guide.) The value of n can range from 1 to 7. If a slash (/)precedes the SYn, the only jobs selected are those that are denoted toexecute on /SYn.




Required: No


LREQR


Default: NATV

Required: No


CA7Unicenter CA-7 job number sequence.





Default: *

Required: No






444 Commands Guide

LREQR

ExamplesLREQR,MAINID=SY1

� � LREQR DATE=YY.DDD PAGE ��1


FXABA�2M FIXASSET ALL A/12� ��17 ��43/��28 �� 3 �2.56 ��/��PERAF�3M PERSONEL SY2 D/1�� 18 ��421/�121 �4 �� 5.37 ��/��WHSAA�1D WAREHOUS ALL C/1�� 19 ��149/��46 �� 3 �3.95 ��/��WHSAB�3W WAREHOUS ALL C/1�� 12 ��351/��57 �� 6.75 �5�84/1549

SLIF-�� REQUEST COMPLETED AT 16:�1:39 on YY.DDD� �



SYSTEM NAMEIdentifies the system name as defined on the DB.1 panel.

MAINIDIdentifies the value from the MAINID field on the DB.1 panel.

JOB C/PRTIdentifies the workload balancing class and priority for this job.

CPUIDIdentifies the CPU where the job executed if the job is in restart status. TheID is not filled in until the job initiation record is processed by UnicenterCA-7.

CA-7# NUMBRIdentifies the Unicenter CA-7 assigned job number.

CPU/ELAPS TIMEIdentifies the CPU and CLOCK TIME from the DB.1 panel.

TOTAL TAPESIdentifies the number of TAPE1 devices, TAPE2 devices, or both that thisjob requires.

CPU% UTILIdentifies the calculated CPU use (using CLOCK-TIME and CPU-TIME fromthe DB.1 panel).

SUBMIT DATE/TIMEIdentifies the Julian date and time this job was submitted.


LRES

LRES

The LRES lists the resources needed for jobs in the database or queues.Magnetic tape, memory and CPU time requirements are shown for any job orgroup of jobs specified by the user.


LRES

��──LRES──,─ ── ──┬ ┬──Q=queue ────────── ───────────────────────────��├ ┤──SYS=system ───────└ ┘──JOB= ──┬ ┬─jobname─

└ ┘─NO──────

QSpecifies the resource information desired. If Q is specified, SYS must beomitted.

ACTActive queue

ALLAll queues

RDYReady queue

RDYACTReady and active queues

REQRequest queue

REQACTRequest and active queues

REQRDYRequest and ready queues

SYSSpecifies that resource information is desired about all jobs in the databasefor this application system. The option must be a system name. If SYS isspecified, Q must be omitted.


Required: Yes, unless Q is specified

446 Commands Guide

LRES

JOBSpecifies the job about which resource information is desired. If JOB isomitted, resource information about all jobs is given based on whether SYSor Q was specified.

Required: Yes, unless SYS or Q was specified

jobnameDefines a specific job in the database. The JOB value is a specific jobname. If specified, SYS and Q must be omitted.


NOWhen JOB=NO is specified, either SYS or Q must be used. JOB=NOcauses the job detail lines of resource information (system or queue) tobe suppressed and only the summary lines are listed.


LRES

ExamplesLRES,SYS=BL�

LRES,Q=ACT

LRES,SYS=S168 Panel

� � LRES,SYS=S168

SYS=S168 DATE=YY.DDD PAGE ��4

JOB CPUTM �-CORE USAGE-� �----TAPE USAGE----�NAME MM.SS HIGH USING-STP HIGH USING-STP TOTAL

T2TSOPAK �1.16 256K �ALL� 1 DUMP 1 T2TSOPK3 ��.34 256K �ALL� 1 DUMP 1

T2WKLY1 �1.42 512K �ALL� � �NONE� � T21�USLB ��.�1 9�K �ALL� � �NONE� � T211BKUP ��.1� 256K �ALL� 1 CMTBKUP 2

�SYS 69.58 5825K 44 65

SLIU-�� REQUEST COMPLETED AT 17:14:52 on YY.DDD� �



CPUTMIdentifies the historical CPU time for this job. See CPU-TIME on the DB.1panel.

CORE USAGEIdentifies the core requirement and the name of the step with the highestusage.

TAPE USAGEIdentifies the tape drive usage for this job showing the step name of thestep that uses the high-water mark for tape drives and the total number oftape drives used by this job.

448 Commands Guide

LRLOG

LRLOG

The LRLOG lists information from the Unicenter CA-7 run log. The run logcontains the information about certain events that occur during Unicenter CA-7processing. These events include job and network completions and exceptionevents such as restarts, force completes, and cancels.

The run log maintains data for the previous n number of days. The default is toretain five days of run log data. That is the current date, up to the moment, andthe four previous calendar days.

An option in the Unicenter CA-7 initialization file controls the number of daysretained. See the RLOGDAYS keyword on the DBASE statement in theSystems Programmer Guide.


LRLOG

��──LRLOG─ ──┬ ┬──────────────────── ───────────────────────────────� │ │┌ ┐─�──────

└ ┘──,DATE= ──┴ ┴─�yyddd─

�─ ──┬ ┬─────────────────────────── ──┬ ┬──────────────────── ────────� │ │┌ ┐─�──────── │ │┌ ┐─ALL────

└ ┘── ─── ───,JOB= ──┼ ┼─jobname── └ ┘──,LIST= ──┴ ┴─option─ └ ┘─jobname�─

�─ ──┬ ┬──────────────────── ──┬ ┬────────────── ─────────────────────� │ │┌ ┐─�──────── │ │┌ ┐─�─

└ ┘──,NW= ──┼ ┼─network── └ ┘──,OPT= ──┴ ┴─1─ └ ┘─network�─

�─ ──┬ ┬────────────────── ──┬ ┬───────────────────── ────────────────� │ │┌ ┐─��─ │ │┌ ┐─DATE─────


�─ ──┬ ┬─────────────────────────────────────────────────────── ────� │ │┌ ┐─current date──────────────────────────────

└ ┘──,SPAN= ──┼ ┼─�───────────────────────────────────────── ├ ┤─scope───────────────────────────────────── ├ ┤─date──────────────────────────────────────

├ ┤──(start date,start time,scope) ────────────└ ┘──(start date,start time,end date,end time)

�─ ──┬ ┬────────────────── ──┬ ┬───────────────────── ────────────────� │ │┌ ┐─�────── │ │┌ ┐─�──────

└ ┘──,ST= ──┴ ┴─option─ └ ┘──,SUBID= ──┼ ┼─subid── └ ┘─subid�─

�─ ──┬ ┬──────────────────── ──────────────────────────────────────�� │ │┌ ┐─�───────

└ ┘──,SYS= ──┼ ┼─system── └ ┘─system�─


LRLOG

DATESpecifies the dates of the information requested.

Required: No

*Specifies all days in the run log. As supplied, the system contains fivedays of data.

*YYDDDDefines a specific date. If specified, the date must be in the form*YYDDD, where yy is the year and ddd is the Julian day and must bewithin the last five calendar days.

JOBIdentifies the jobs to be displayed from the run log.

Default: *

Required: No






LISTControls what types of objects are selected.

Default: ALL

Required: No

ALLSelects all types of objects (all jobs and networks).

JOBSelects only job related events.

XJOBSelects only external job related events. An external job is one that istracked by Unicenter CA-7 even though Unicenter CA-7 did not submitit.

NWSelects only network related events.

INWSelects only input network related events.

450 Commands Guide

LRLOG

ONWSelects only output network related events.

Note: The old option RSTR is still accepted. It is processed as ifST=RSTR were entered.

NWSpecifies the networks to be displayed.

Default: *

Required: No


networkDefines a specific network.


network*Defines a generic network.


OPTControls the output format of the data displayed. This keyword allows youto have the run log data displayed in the pre-Release 3.2 format. If youwant to see run log data in the same manner it was presented in previousversions, specify OPT=1 on the LRLOG command.

Default: 0

Required: No

0Displays run log data in the Release 3.2 and above format.

1Displays run log data in the pre-Release 3.2 format.

Note: If you have Batch Terminal (BTI) jobs that extract run log datafor further processing and it is expecting the pre-Release 3.2 format,you can specify a default Batch LRLOG format in the Unicenter CA-7initialization file. See the RLOGBDEF keyword on the OPTIONSstatement in the Systems Programmer Guide.

SCHIDIndicates to only select events with a specific schedule ID.


Limits: 1 to 3 numeric from 1 to 255

Required: No


LRLOG

SEQControls the display sequence of the selected run log data.

Default: DATE

Required: No

DATEDate and time sequence.

JOBJob name, and date/time sequence within jobs with the same name.

NWNetwork name, and date/time sequence within networks with the samename.

REVReverse date and time sequence.

SUBIDSub-ID, and date/time sequence within networks with the same Sub-ID.

Note: The old option NATV is still accepted. However, it is processedthe same as the DATE option.

SPANRun log records are searched for the time period specified or implied bythis keyword. It can be expressed as a scope, a starting date/time andscope, or as a date and time range. This keyword is mutually exclusive withthe DATE= keyword.

Default: Current date

Required: No

*Specifies all run log data should be searched.

scopeUse this format to search most current information in the run log for afixed period. The starting time is calculated as the current time minusthe scope. The ending time is the current time. The scope can beexpressed as a number of hours (one to three digits), or as hours andminutes (four digits).

SPAN=8 Search the last 8 hours.SPAN=�13� Search the last 1 hour and 3� minutes.

dateUse this format to search the run log data for a specific date. The datecan be expressed as a five-digit Julian date (YYDDD), or as a six-digitGregorian date (MMDDYY).

SPAN=�5��1 Search Jan. 1, 2��5 (entire day).SPAN=�1�2�5 Search Jan. 2, 2��5 (entire day).

452 Commands Guide

LRLOG

(start date, start time, scope)Use this format to express a starting point and a fixed amount of timeforward from that point (scope).

The starting date/time is specified on the keyword.

The ending time is calculated as the starting date/time plus the scope.

The starting date can be expressed as a Julian date (five digits) orGregorian date (six digits).

The starting time can be expressed as hhmm (4 digits) where hh is thehour (00-24) and mm is the minutes (00-59). If no time is specified thedefault is the beginning of the day (0000).

The scope can be expressed as a number of hours (one to threedigits), or as hours and minutes (four digits).

SPAN=(�5��1,13��,8) Jan. 1, 2��5 (1:��pm - 9:��pm)SPAN=(�1�2�5,12��,24) Jan.2,2��5(noon) - Jan.3,2��5 (noon)

(start date, start time, end date, end time)Use this format to express both a starting and ending point for theselection window.

The dates can be expressed as Julian dates (five digits) or Gregoriandates (six digits).

The times can be expressed as hhmm (4 digits) where hh is the hour(00-24) and mm is the minutes (00-59). If no start time is specified thedefault is the beginning of the day (0000). If no end time is specifiedthe default is the end of the day (2400).

SPAN=(�5��1,12��,�5��2,�8��) Jan 1 (noon) - Jan 2 (8 am)SPAN=(�1�2�5,,�1�3�5) All of Jan 2. and Jan 3, 2��5

STControls what types of events are selected.

Default: *

Required: No

*Selects all types of events.

COMPSelects only job and network completion events.

LATESelects only job and network completion events where the completionwas considered late by Unicenter CA-7.

CANCELSelects only job and network cancel events.

FORCESelects only force complete events.


LRLOG

RSTRSelects only restart events.

EXCPSelects only exception events. That is, only non-completion events areselected (cancel, force complete, requeue, and restart).

Note: The old option CANC is still accepted. It is processed the sameas the CANCEL option.

SUBIDSpecifies the sub-IDs to be displayed.

Default: *

Required: No




subid*Defines a generic sub-ID.


SYSIdentifies the systems to be selected from the run log.

Default: *

Required: No

*Specifies all systems.

systemIndicates to select only jobs with a specific system name.

Limits : 1 to 8 alphanumeric characters

system*Specifies to select only jobs whose system name begins with thegeneric system name.

Limits : 1 to 7 alphanumeric characters terminated with an asterisk

454 Commands Guide

LRLOG

Examples

LRLOG Current day (up to present time).LRLOG,SPAN=8 Previous 8 hours.LRLOG,SPAN=168,LIST=JOB Previous week, only Job related events.LRLOG,SPAN=��3� Previous 3� minutes.LRLOG,SPAN=�5��1 January 1, 2��5 (entire day).LRLOG,SPAN=�,JOB=PAY� Search all run log data for job names

that begin with PAY.LRLOG,SPAN=�,SYS=PAYROLL,ST=EXCP

Search all run log data for jobs with asystem name of PAYROLL. Select onlyexception events (cancel, force, restart).

LRLOG Panel

� �LRLOG DATE=YY.�61 PAGE ��1

EVENT OBJECT ENTRY TRGR LATETYPE TIME TYPE NAME CA7# SCH SYSTEM STATUS MODE CA7# START END

C yy�61/�759 J CA�7LOGP ��17 �� COMP DMND �� yy�61/�759 yy�61/�759C yy�61/�9�7 I TESTINNW ��18 ��1 DMD#��18 DMND �� /�� yy�61/�9�7L SUBID= DESC=TESTINNW INITS=BDWASHEC yy�61/�917 O TESTOTNW ��2� ��1 DMD#��2� COMP DMND �� /�� yy�61/�917LR yy�61/1432 J FSTAT��9 �997 ��1 FSTATUS JCLER AUTO �993

REASON= RESTARTED TO GENERATE RLOG RECX yy�61/1434 J P4 �798 ��1 DMND ��F yy�61/1435 J FSTAT��9 �997 ��1 FSTATUS JCLER AUTO �993 L

REASON= FINALLY FORCE ITC yy�61/1435 J FSTAT��9 �997 ��1 FSTATUS FCOMP AUTO �993 yy�61/1435 yy�61/1435L

� �


EVENT TYPEIdentifies the type of event.

CCompletion

FForce Complete

RRestart

XCancel (Unicenter CA-7)

EVENT TIMEIdentifies a date and time that the event was written to the run log. Thedate is in Julian format and the time is in hours (HH) and minutes (MM).


LRLOG

OBJECT TYPEIdentifies a type of object that was involved with this event.

JJob

J-External Job

IInput Network

OOutput Network

OBJECT NAMEIdentifies the name of the job or network that the event relates to. If it is anetwork related event, this field reflects the actual network name.

CA-7#Identifies the Unicenter CA-7 assigned job or network reference number.

SCHIdentifies the Unicenter CA-7 schedule ID.

SYSTEMFor job entries, the system name. For network entries, the generated jobname for this execution of the network.

STATUSIdentifies the status of the network or system status of the job.

COMPNormal Completion.

SnnnAbnormal System Completion (nnn = abend code).

UnnnnAbnormal User Completion (nnnn = completion code).

CnnnnJob level condition code.

#nnnnStep level condition code.

JCLERJCL Error.

CANCLCancel (See RLOGCAN in the OPTIONS statement of the initializationfile in the Systems Programmer Guide.)

FCOMPForce Complete.

456 Commands Guide

LRLOG

REQUERequeued.

FAILSpecial job UCC7Rxx failed.

ENTRY MODEIdentifies the entry mode of the job or network.


AUTOTrigger.

DMNDDEMAND command.

LOADLOAD command. (LOAD jobs that are successful do not have a runlogentry. Only those LOAD jobs that fail, and are then canceled, have anentry.)

PSPersonal Scheduling.

RPETRepeated job.

RUNRUN command.

SSCNSchedule scan.

XDEMDEMAND command from an XPS client.

XPSXPS client using the RUN command with the REF option.

XRUNXPS client using the RUN command.

TRGR CA7#If the object was brought into the system through a trigger, or as an ARFrecovery job, this field contains the Unicenter CA-7 job number of thetriggering object. Otherwise, it is zero.

STARTStarting date and time for event type of C (and other event types asavailable).

ENDCompletion date and time for event type of C (and other event types asavailable).


LRLOG

LATEAn L at the end of the completion time indicates that the job or network wasconsidered late by Unicenter CA-7.

SUBID=For input and output network events, an additional line is displayed showingthe network sub-ID, description and any initials supplied during the logout ofthe last workstation.

REASON=For force complete, restart, and cancel events, if a reason was supplied forthe action an additional line is displayed containing the reason text.

458 Commands Guide

LRMD

LRMD

The LRMD lists reminder (prompting) information from the Unicenter CA-7preprocess queue. Such information is first defined into an active area using theUnicenter CA-7 editor, and scheduled for display at a workstation with theREMIND command. A free-form message can be defined to communicateanything to a workstation at a predetermined time. The workstation operator isprompted, repeatedly if necessary, to review the defined text. For a discussionof how to schedule these free-form messages, see “REMIND” on page 548.


LRMD

��──LRMD─ ──┬ ┬────────────────────── ──┬ ┬───────────────── ─────────� │ │┌ ┐─�───────── │ │┌ ┐─NATV─

└ ┘──,JOB= ──┼ ┼─jobname─── └ ┘──,SEQ= ──┼ ┼─CA7── ├ ┤─jobname�── ├ ┤─DLTM─ └ ┘─jobnumber─ ├ ┤─DOTM─ ├ ┤─JOB── └ ┘─STA──

�─ ──┬ ┬──────────────── ──┬ ┬───────────────────── ─────────────────�� │ │┌ ┐─�──── │ │┌ ┐─�────────

└ ┘──,ST= ──┴ ┴─LATE─ └ ┘──,STN= ──┼ ┼─station── └ ┘─station�─










LRMD

SEQControls the display sequence of the remind messages.

Default: NATV

Required: No


CA7Unicenter CA-7 assigned number sequence.




STAStation name sequence.

STSpecifies the display criteria of the remind messages.

Default: *

Required: No

*All of the reminder text.

LATEOnly the late reminder text.

STNSpecifies the station names for which information is to be selected.

Default: *

Required: No


stationDefines a specific station name.


station*Defines a generic station name.


460 Commands Guide

LRMD

ExamplesLRMD

LRMD,ST=LATE,STATION=KEYPUNCH

LRMD,JOB=RMD#��4

LRMD,ST=LATE,SEQ=STA

LRMD Panel

� � LRMD

LIST=JCL DATE=YY.DDD PAGE ��1

CA-7 NETWORK NETWORK STATION JOB �----DAY(DDD) AND TIME(HHMM)-----�REF# SUBID DESC NAME NAME DEADLINE LOGIN DUE-OUT NW/LGOUT

��9��1 SUPVISOR CONTROL RMD#��9 121/1�� 121/164� 121/1�� CONTROL------------------------ REMINDER INFORMATION -------------------------

�� DON'T FORGET !!!!!!!!!!!!!!!!

�� THERE WILL BE A MEETING JULY 1�, 2��5 AT 1�:3� AM,� IN THE 5TH FLOOR CONFERENCE ROOM,� TO REVIEW THE DISASTER CONTINGENCY PLAN FOR THE DATA CENTER.

�� ALL COMPUTER OPERATIONS DEPT. SUPERVISORY PERSONNEL MUST ATTEND.

�

SLIF-�� REQUEST COMPLETED AT 16:4�:21 on YY.DDD� �


LSCHD

LSCHD

The LSCHD lists schedule information from the database for jobs or networks.You can limit this display to certain systems or stations. You can reviewschedules for networks and stations as well as processing calendars for inputnetworks. Information provided includes scheduling parameters, variations byschedule ID, and month-by-month calendars.


LSCHD

��──LSCHD──,─ ──┬ ┬──DSNBR= ──┬ ┬─Sxnnnnnn─── ────────────────────────� │ │├ ┤─Sx��nnnnn�─ │ │└ ┘─Sx�──────── │ │┌ ┐─�────────

├ ┤──JOB= ──┼ ┼─jobname── ──── │ │└ ┘─jobname�─

├ ┤──NW=network ──────────── │ │┌ ┐─�───────

└ ┘──STN= ──┴ ┴─station─ ─────

�─ ──┬ ┬──────────────────── ──┬ ┬────────── ──┬ ┬────────────────── ───�└ ┘──,LIST= ──┬ ┬─BYSID── └ ┘──,SCAL=xx └ ┘──,ST= ──┬ ┬─EXP────

├ ┤─CALS─── ├ ┤─JAN──── ├ ┤─SCHD─── ├ ┤─JUL────

└ ┘──SIDnnn ├ ┤─MOD──── ├ ┤─NRV──── ├ ┤─REPEAT─ ├ ┤─REPT─── └ ┘─RPET───

�─ ──┬ ┬──────────────────────── ──────────────────────────────────�� │ │┌ ┐─�───────────


DSNBRSpecifies a single or generic database schedule member number.

Required: Yes, unless NW, JOB, STN, or SYS is used

SxnnnnnnSpecifies a single database member number.

xIs either I, J, or O for input workstation network, CPU job, andoutput workstation network schedules, respectively.

nnnnnnIs a database schedule member number assigned by UnicenterCA-7. Leading zeros can be omitted.

462 Commands Guide

LSCHD

Sx00nnnnn*Is a generic schedule database member number. Leading zeros cannotbe omitted.

Limits: 1 to 7 numeric characters terminated with an asterisk

Sx*Causes listing of all schedule members. You can list all members of aspecific schedule type by using one of the following:

DSNBR=SI*All input network schedule members are listed.

DSNBR=SJ*All job schedule members are listed.

DSNBR=SO*All output network schedule members are listed.

JOBSpecifies the jobs whose schedule members are to be listed. JOB can beused with SYS. We recommend that online LSCHD commands limit thenumber of jobs displayed.

Default: *

Required: Yes, unless DSNBR, NW, or STN is used

*Specifies all job schedules.





NWSpecifies the networks whose schedule members are to be listed. IfDSNBR, JOB, or SYS is used, both NW and STN must be omitted.

Required: Yes, unless DSNBR, JOB, STN, or SYS is used


LSCHD

STNSpecifies the stations within a network whose schedule members are to belisted. The information displayed depends on the value of STN keyword.Otherwise, information pertaining only to the station name specified isdisplayed. STN must be omitted if DSNBR, JOB, or SYS is specified.

Default: *

Required: Yes, unless DSNBR, JOB, NW, or SYS is used


stationDefines a specific station name.


LISTSpecifies list options for the schedule data to be printed. If omitted, onlyinformation used to define selected schedules is displayed. If a genericDSNBR is coded, LIST is invalid. For schedule members that have notbeen resolved, no schedule day calendars are available for display. Thiskeyword is mutually exclusive with ST.

Required: No

BYSIDA month-by-month schedule day calendar for each schedule ID in theselected members. Valid only for RESOLVed schedules.

CALSA month-by-month schedule day calendar using the schedule dataselected. This is a composite calendar reflecting all selected scheduleIDs. If used with JOB=*, the display could be very lengthy. A batchterminal should be used for this combination. Valid only for RESOLVedschedules.

Note: Output workstation network schedule members do not havecomposite calendars. Therefore, no calendar is printed for outputworkstation network schedules.

SCHDAll schedules. Where jobs are involved (through keywords JOB, SYS orDSNBR=SJnnnnnn) information about all the jobs, data sets, or boththat trigger the job under consideration is listed as well as all jobstriggered by the job under consideration.

SIDnnnA month-by-month schedule day calendar for one schedule ID specifiedby the nnn value (leading zeros are required). Valid only for RESOLVedschedules.

SCALDesignates a specific base calendar identifier. Used for selecting onlyschedules that reference this calendar.

464 Commands Guide

LSCHD

STSpecifies a type of schedule to be selected. Primarily for generic requests.If omitted, all types are listed according to other selection criteria. Thiskeyword is mutually exclusive with LIST.

Required: No

EXPSchedules that have expired.

JANJanuary through December schedules.

JULJuly through June schedules.

MODSchedules that have been changed through DB.2.7 panel.

NRVSchedules that have never been resolved.

REPEAT|REPT|RPETSchedules that have at least one schedule ID with a repeat definition.

SYSSpecifies an application system name as defined on the DB.1 panel foreach job, for which the display is desired. If JOB is also used, only thosejobs meeting both the JOB and SYS criteria are displayed. (TheSYS=systemname parameter is not valid when a specific job name isspecified.)

Default: All systems

Required: No





Limits: 1 to 7 alphanumeric characters, terminated with an asterisk


LSCHD

ExamplesLSCHD,DSNBR=SJ13,LIST=CALS

LSCHD,DSNBR=SO�

LSCHD,LIST=CALS,NW=�

LSCHD,NW=JOBNET6

LSCHD,NW=JOBNETA,STN=STATION

LSCHD,JOB=CA7JOB1,LIST=BYSID

The COMMENTS field on the display always contains values similar to the SToptions, even if ST was not requested, to indicate type of schedule and itscurrent status.

LSCHD,JOB=DUSAXX01,LIST=BYSID Panel

� � LSCHD,JOB=DUSAXX�1,LIST=BYSID

LIST=BYSID JOB=DUSAXX�1 DATE=YY.DDD PAGE ��1

JOB SYSTEM SCHEDULE #SCH -BASE CALENDAR- PROSE COMMENTS NAME NAME NUMBER IDS USERID B-DATE NUM

DUSAXX�1 PAYABLES SJ��3 ��2 SCAL�5�3 �5��2 PP��9 SCHDMOD CURRENT. LAST MAINTENANCE ON yy.ddd AT hh:mm:ss VIA xxx BY OPERATOR: yyyyyyy------------------------------ SCHEDULES ------------------------------

CALENDAR SCAL99�3 ID=��1 ROLL=D INDEX=+��

SCAL= DOTM=�8�� LEADTM=�13� STARTM=�63� WEEKLY DAY=MON,FRI ID=��2 ROLL=D INDEX=+��

SCAL=7D DOTM=12�� LEADTM=�1�� STARTM=11�� DAILY

� �


JOB NAMEIdentifies the name of the job as defined in the database.

SYSTEM NAMEIdentifies the value defined in the SYSTEM field on the DB.1 panel.

SCHEDULE NUMBERIdentifies the DSNBR assigned to the schedule when it was added to thedatabase.

#SCH IDSIdentifies the number of variations (SCHIDs) for this job's schedule.

BASE CALENDAR USERIDIdentifies the name of the base calendar used in RESOLVing this schedule.

466 Commands Guide

LSCHD

BASE CALENDAR B-DATEIdentifies the assembly date of the base calendar used in RESOLVing thisschedule.

PROS NUMIdentifies the DSNBR assigned to the documentation for this job.

COMMENTSUnder this heading one or more of the following can appear:

JANUARY SCHEDULE|JULY SCHEDULEA schedule resolved between January 1 and June 30 has a January(JAN) schedule, and one resolved between July 1 and December 31has a July (JUL) schedule.

NXTCYC=OFFThe schedule is suspended from execution until it is reset by aNXTCYC=ON command.

NXTCYC=SKPThe next execution of this scheduled job is skipped, but subsequentcycles are scheduled.

SCHDMOD CURRENTThe schedule member has been updated through the SCHDMODpanel.

SCHDMOD OVERLAIDThe schedule member had received a modification through the DB.2.7panel, and a top line RESOLV command was issued that caused theschedule to revert to the original schedule information.

SCHED BEG mmm yyThe schedule will begin in the month mmm (JAN or JUL) of the year yy.

SCHED IS EXPIREDThe schedule needs to be re-resolved because it has been over a yearsince the last RESOLV.

SCHED NEEDS RESOLThe schedule has been changed through the DB.2.1-E panel and savedto the database but not resolved.


LSCHD

LSCHD,NW=INPUTNWK,LIST=BYSID Panel

� � LSCHD,NW=INPUTNWK,LIST=BYSID

LIST=BYSID NW=INPUTNWK DATE=YY.DDD PAGE ��1

NETWORK #OF NETWORK SCHEDULE #SCH -BASE CALENDAR- COMMENTS NAME STNS NBR NUMBER IDS USERID B-DATE

INPUTNWK �9 NW��16 SI��8 ��1 SCAL�5ED �� JANUARY SCHEDULE. LAST MAINTENANCE ON yy.ddd AT hh:mm:ss VIA xxx BY OPERATOR: yyyyyyy-------------------------- SCHEDULES --------------------------------

CALENDAR SCAL99EDID=��7 ROLL=D INDEX=+��

SCAL= WKSTA=(�1,DOTM=�8��,LEADTM=��5,DAY=��) WKSTA=(�2,DOTM=�8�5,LEADTM=��5,DAY=��) WKSTA=(�3,DOTM=�81�,LEADTM=��5,DAY=��) WKSTA=(�4,DOTM=�815,LEADTM=��5,DAY=��) WKSTA=(�5,DOTM=�82�,LEADTM=��5,DAY=��) WKSTA=(�6,DOTM=�825,LEADTM=��5,DAY=��) WKSTA=(�7,DOTM=�83�,LEADTM=��5,DAY=��) WKSTA=(�8,DOTM=�835,LEADTM=��5,DAY=��) WKSTA=(�9,DOTM=�845,LEADTM=��1�,DAY=��) DAILY

� �


NETWORK NAMEIdentifies the name of the network as defined in the database. See NAMEon the DB.2.2 panel.

# OF STNSIdentifies the number of stations (LTERMs) defined for this network.

NETWORK NBRIdentifies the DSNBR assigned to this network when it was added to thedatabase.

SCHEDULE NUMBERIdentifies the DSNBR assigned to the schedule when it was added to thedatabase.

#SCH IDSIdentifies the number of variations (SCHIDs) for this network's schedule.

BASE CALENDAR USERIDIdentifies the name of the base calendar used in resolving this schedule.

BASE CALENDAR B-DATEIdentifies the assembly date of the base calendar used in resolving thisschedule.

468 Commands Guide

LSCHD

COMMENTSUnder this heading one or more of the following can appear:

JANUARY SCHEDULE|JULY SCHEDULEA schedule RESOLVed between January 1 and June 30 has a January(JAN) schedule, and one RESOLVed between July 1 and December 31has a July (JUL) schedule.

SCHDMOD CURRENTIndicates the schedule member has been updated through the DB.2.7panel.

SCHDMOD OVERLAIDIndicates the schedule member had received a modification through theDB.2.7 panel, and a top line RESOLV command was issued thatcaused the schedule to revert to the original schedule information.

SCHED BEG mmm yyIndicates the schedule will begin in the month mmm (JAN or JUL) ofthe year yy.

SCHED NEEDS RESOLUTIONIndicates the schedule has been changed through the DB.2.1-E paneland SAVEd to the database but not RESOLVed.

SCHEDULE IS EXPIREDIndicates the schedule needs to be re-RESOLVed because it has beenover a year since the last RESOLV.

� � LSCHD,DSNBR=SJ�

LIST=DSNBR=SJ� DATE=YY.DDD PAGE ��1

JOB SYSTEM SCHEDULE #SCH -BASE CALENDAR- PROSE COMMENTSNAME NAME NUMBER IDS USERID B-DATE NUM

DUSAXX�1 OVERHEAD SJ��1 ��4 SCAL�5�3 �5��2 PP��4 DB.2.7 DUSAXX�2 OVERHEAD SJ��2 ��1 SCAL�5�1 �5��2 PP��28 JANUARY SCHEDULE DUSAXX�5 OVERHEAD SJ��3 ��4 SCAL�5�3 �5��2 PP��9 JANUARY SCHEDULE DUSAXX�8 OVERHEAD SJ��4 ��1 SCAL�5PE �5��4 �NONE� JANUARY SCHEDULE ACPAA�1W PAYABLES SJ��5 ��1 SCAL�5PE �5��4 �NONE� JANUARY SCHEDULE ACPAB�1W PAYABLES SJ��7 ��1 SCAL�5ED �5�32 �NONE� NXTCYC=OFF� �


LSYS

LSYS

The LSYS lists database information for all jobs defined in a specific applicationsystem. This includes input/output data set cross references for each job. Theinformation is similar to that included with the LJOB command. It allows you toreview all jobs within an application system with just one command.


LSYS

��──LSYS──,─ ──┬ ┬──SYS=system ─ ──┬ ┬────────────── ─────────────────�� └ ┘──JOB=jobname └ ┘──,LIST=option

SYSIdentifies an application system for which information is to be listed. Thevalue is a specific application system name. If SYS is specified, JOB mustbe omitted.


Required: Yes, unless JOB is used

JOBIdentifies a particular job name for which information is to be listed. If JOBis specified, SYS must be omitted.


Required: Yes, unless SYS is used

LISTSpecifies list options for the information to be printed. If LIST is notspecified, a single line describing each job is output.

Required: No

ALLJobs, schedules, steps, and data set dependencies for the applicationsystem specified.

DEPJobs, steps, and data set dependencies for the application systemsspecified. This is the default for the JOB option.

JOBSJob data only for jobs in the application systems specified.

SCHDJobs within the application systems specified along with their schedules.

470 Commands Guide

LSYS

ExamplesLSYS,SYS=CA7JOBS

LSYS,SYS=CA7JOBS,LIST=JOBS

LSYS,SYS=CA7JOBS,LIST=SCHD

� � LSYS,SYS=TESTNTWK

SYS=TESTNTWK DATE YY.DDD PAGE ��1


CUSAXX�1 �� DUSAXX�1 TESTNTWK �� ALL �NONE� �NONE� �� /��DUSAXX�2 �� DUSAXX�2 TESTNTWK �� /SY2 ��12 �NONE� ��1 ��4 �118 �5126/1331DUSAXX�3 �� DUSAXX�3 TESTNTWK �� /SY1 ��11 �NONE� ��1 ��4 �112 �5126/133�DUSAXX�4 �� DUSAXX�4 TESTNTWK �� ALL ��13 �NONE� ��1 ��4 �1�3 �5126/1331DUSAXX�5 �� DUSAXX�5 TESTNTWK �� ALL ��1 �NONE� ��2 ��8 ��93 �5126/1331DUSAXX�6 �� DUSAXX�6 TESTNTWK �� ALL ��2 �NONE� ��1 ��6 ��82 �5126/1332

� �



JCL IDIdentifies the index of the data set (defined in the initialization file, JCLstatement) where this member resides.

JCL MEMBERIdentifies the member name of the JCL that this job executes.


USR IDIdentifies the value from the UID field on the DB.1 panel.

MAINIDIdentifies the value from the MAINID field on the DB.1 panel.


LSYS

PROSE DSNBRIdentifies the Unicenter CA-7 generated DSNBR for the job documentationdefined for this job.

SCHED DSNBRIdentifies the Unicenter CA-7 generated DSNBR for the schedule memberdefined for this job.

NUMBER OF STPIdentifies the number of steps executed within this job.

NUMBER OF DDSIdentifies the number of DDs referenced by this job.

NUMBER OF RUNSIdentifies the number of times this job has successfully executed underUnicenter CA-7.

LAST-RUN DATE/TIMEIdentifies the last time (start time) that the job ran successfully underUnicenter CA-7.

472 Commands Guide

LWLB

LWLB

The LWLB lists currently active workload balancing processing objectiveinformation. If the resource criteria have been loaded by the Unicenter CA-7system, then actual or in-use values are displayed. Default Resource Balancingcriteria are displayed following Unicenter CA-7 cold type of startups and untilany user-defined criteria are loaded. Display options are provided that permitthe review of available and/or in-use workload balancing values, as well asdefinitions that are on the database but not currently in use.


LWLB

��──LWLB─ ──┬ ┬────────────── ──┬ ┬───────────────── ────────────────��└ ┘──,MOD=modname │ │┌ ┐─ALL─

└ ┘──,LIST= ──┼ ┼─AVL─ └ ┘─USE─

MODIdentifies the module whose processing objective criteria are to be listed.The value can be specified as a single module name. If MOD is notspecified, the default processing objective criteria are of the modulepresently in effect.

Limits: 1 to 8 alphanumeric characters beginning with UCC7R

Required: No

LISTSpecifies the balancing criteria to be listed.

Default: ALL

Required: No

ALLProcessing objective criteria and the values that are currently beingused.

AVLProcessing objective criteria values from the current UCC7R module.

USEValues that are currently being used.


LWLB

ExamplesLWLB

LWLB,MOD=UCC7R1��

LWLB,MOD=UCC7R1��,LIST=USE

LWLB,LIST=ALL

LWLB Panel (Page 1 of 2)

� � LWLB

MOD=UCC7R1�� DATE YY.DDD PAGE ��1

�� CURRENT RESOURCES IN USE ��

-------INITIATORS-------- ----TAPE DRIVES---- ---CPU UTILIZATION---TOTAL JOBS SUBMITTED �� NAME - TAPEDR1 �� UTIL PER JOB ��.��%

NAME - TAPEDR2 ��

-----------------------------------JOB CLASS----------------------------------

A �� D �� G �� J �� M �� P �� S �� V �� Y �� 1 �� 4 �� 7 ��B �� E �� H �� K �� N �� Q �� T �� W �� Z �� 2 �� 5 �� 8 ��C �� F �� I �� L �� O �� R �� U �� X �� 3 �� 6 �� 9 ��

� �


INITIATORSIdentifies the total number of jobs submitted to JES by Unicenter CA-7 andtherefore the number of initiators that should be in use by Unicenter CA-7submitted jobs.

TAPE DRIVESFor each type of tape drive, the sum of the numbers from the DB.1 panelfor the jobs that Unicenter CA-7 has submitted to JES.

CPU UTILIZATIONIdentifies the average CPU use of the Unicenter CA-7 submitted jobs.

JOB CLASSIdentifies the number of jobs submitted by Unicenter CA-7 in each of the 36job classes as entered on the DB.1 panel.

474 Commands Guide

LWLB

LWLB Panel (Page 2 of 2)

� � LWLBMOD=UCC7R1��,LAST CHG-DATE �5/12/�5 DATE YY.DDD PAGE ��2

�� AVAILABLE RESOURCES �� -------------INITIATORS------------ ------------CPU TIME-----------

TOTAL AVAILABLE �14 IDEAL UTILIZATION PER JOB �1�%MIN JOBS MUST EXEC ��1 MAX REWARD 1��

THRESHOLD PRTY 2�� MAX PENALTY 1��

----------------TAPE DRIVES------------ -----------START TIME---------- NAME. 652�BPI 16��BPI MAX REWARD/PENALTY 1��/�5�

TOT NUMBER AVAILABLE ��8 �16 MAX HOURS EARLY/LATE �12/�12TOT MAX ALLOWABLE �12 �2� RUN TIME FACTOR �1�MAX DTS BOOST �5� �3� -------SPECIAL CLS/PRTY--------MAX REWARD/PENALTY 1��/�5� �6�/�4� SPECIAL CL #1 CL PRTY 255MIN/MAX DIFF-TO-SCHED ��5/��7 ��4/��6 SPECIAL CL #2 CL PRTY 255MIN/MAX ALLOWABLE/JOB ��/��7 ��/��5 SPECIAL CL #3 CL PRTY 255

-----------------------------------JOB CLASS-----------------------------------A ��4 D ��5 G ��1 J ��1 M ��1 P ��1 S ��1 V ��1 Y ��1 1 �� 4 �� 7 ��B ��4 E ��1 H ��1 K ��1 N ��1 Q ��1 T ��1 W ��1 Z ��1 2 �� 5 �� 8 ��C ��2 F ��1 I ��1 L ��1 O ��1 R ��1 U ��1 X ��1 � ��1 3 �� 6 �� 9 ��

SLI�-�� REQUEST COMPLETED AT �9:37:46 on YY.DDD� �


--INITIATORS--Identifies job totals.

TOTAL AVAILABLEIdentifies the maximum number of system initiators that can be scheduledand therefore the number of OS initiators that must be dedicated toUnicenter CA-7 controlled jobs. A value of 255 indicates there is not a limit.

MIN JOBS MUST EXECIdentifies the number of jobs that must be submitted before workloadbalancing is in effect.

THRESHOLD PRTYIdentifies the lowest priority job that is submitted when the number of jobsUnicenter CA-7 is running is greater than or equal to the MIN JOBS MUSTEXEC number.

--CPU TIME--Identifies CPU statistics.

IDEAL UTILIZATION PER JOBIdentifies a full percentage of CPU that workload balancing should strive foras an average across all submitted jobs.

MAX REWARDIdentifies the maximum number of priority points that a job can earn in theready queue if it is a perfect CPU fit.


LWLB

MAX PENALTYIdentifies the maximum number of priority points that a job can lose in theready queue if it is the worst possible CPU fit.

--TAPE DRIVES--Identifies tape drive statistics.

NAMEIdentifies the type of tape drive.

TOT NUMBER AVAILABLEIdentifies the total number of actual tape drives available to Unicenter CA-7.

TOT MAX ALLOWABLEIdentifies the maximum number of tape drives that Unicenter CA-7controlled jobs can use at any point in time.

MAX DTS BOOSTIdentifies the maximum number of priority points to be added to a job'sDB.1 (Job) panel priority in the ready queue if you have defined MIN/MAXDIFF-TO-SCHED jobs in terms of tape drive usage.

MAX REWARD/PENALTYIdentifies the maximum number of priority points that can be earned and themaximum number of priority points that can be lost by a job in the readyqueue because it uses tape drives.

MIN/MAX DIFF-TO-SCHEDIdentifies the minimum and maximum number of tape drives that a job mustallocate at one time for that job to be considered difficult to schedule.

MIN/MAX ALLOWABLE/JOBIdentifies the minimum and maximum number of tape drives that a job mustallocate at one time to be submitted to run.

--START TIME--Identifies time statistics.

MAX REWARD/PENALTYIdentifies the maximum number of priority points a job can beawarded/penalized for being late.

MAX HOURS EARLY/LATEIdentifies the number of hours early over which the maximum penalty/awardis given.

RUN TIME FACTORIdentifies a buffer (stated as a percentage) where a job is neither early orlate.

--SPECIAL CLS/PRTY--Identifies special class values.

476 Commands Guide

LWLB

--JOB CLASS--For each of 36 possible scheduling job classes, the maximum number ofjobs of that class that Unicenter CA-7 can run concurrently. A value of 255indicates there is not a limit.


MAP

MAP

The MAP command lists the attributes of DASD data sets. This function isavailable on the UT Menu panel as FUNCTION value 15 or any other menu orformatted panel as FUNCTION value UT.15.


MAP

��──MAP─ ──,DSN=dsname ──┬ ┬───────────── ──┬ ┬───────────────── ─────��└ ┘──,VOL=volume │ │┌ ┐─DSN─

└ ┘──,LIST= ──┴ ┴─ALL─

DSNIdentifies the data set to be mapped. The name can be a fully qualifiedname or a generic request. The latter is indicated with an asterisk (*)following the last significant character. (VOL is required for a genericrequest.) A relative generation request can be made for a catalogedgeneration data set if the VOL parameter is omitted. DSN=* lists all datasets on a volume.


Required: Yes

VOLIndicates the volume on which the data set resides.


Required: Yes - unless a request is made for a fully qualified, catalogeddata set name

LISTIndicates the type of data to be listed.

Default: DSN

Required: No

DSNLists the dsname, number of extents, tracks allocated, tracks used,secondary allocation quantity, DSORG, record format (RECFM), logicalrecord length (LRECL), and block size (BLKSIZE).

ALLIn addition to information noted under DSN above, lists the creationdate, expiration date, absolute DASD address, type allocation, optioncode (OPTCD), key length, key position, password indicators, andunmovable indicators.

478 Commands Guide

MAP

Usage Notes

Tracks used and secondary allocation do not apply for ISAM data sets.

There must be a U7volser DD statement in Unicenter CA-7 execution JCL forthe volume containing the data set being mapped or the allocation values arezeros.

ExamplesMAP,DSN=SYS1.PROCLIB

MAP,DSN=USER.FILE,VOL=VOLMO1,LIST=ALL

MAP,DSN=SYS1�,VOL=SYSRES

MAP,DSN=USER.INDX1,VOL=VOLMO2,LIST=ALL

MAP,DSN=USER.GDG(-1),LIST=ALL


MENU

MENU

The top line MENU command transfers to the Unicenter CA-7 Function Menu atany time.

MENU

��──MENU────────────────────────────────────────────────────────��

CA-7 Function Menu Panel:

� � ---------------------------- CA-7 FUNCTION MENU ------------------------------ FUNCTION ===>

APA - AUTOMATED PERFORMANCE ANALYSISDB - DATA BASE MAINTENANCEQM - QUEUE MAINTENANCERM - VIRTUAL RESOURCE MANAGEMENT

UT - UTILITIESPS - PERSONAL SCHEDULING

HELP - TUTORIAL

PROGRAM: MNU� MSG-INDX: �� -- MENU -- YY.DDD / HH:MM:SS MESSAGE: SPECIFY DESIRED FUNCTION OR ENTER A COMMAND ON THE TOP LINE

� �

480 Commands Guide

NOPRMP

NOPRMP

The NOPRMP top line command suspends reminder prompting for particularjobs. Unlike RSVP, which is for a single job, this command is used to suspendall prompting. NOPRMP can be directed at specific jobs, or all jobs in thequeues. This function is available for CPU jobs through the QM.3 panel.Workstation networks must use the NOPRMP command.


NOPRMP

��──NOPRMP──,─ ──┬ ┬──JOB= ──┬ ┬─nnnn─ ──────────────────────────────�� │ │├ ┤─ALL── │ │└ ┘─ALLP─

└ ┘──REF=nnnnrrs ───

JOBIdentifies the jobs for which prompting is to be suspended.

Required: Yes, unless REF is used

nnnnIndicates the Unicenter CA-7 job number of a specific job.

ALLIndicates all jobs in the request, ready, and postprocess queues.

ALLPIndicates all jobs including those in the preprocess queue.


NOPRMP

REFSpecifies a particular workstation network task (and all subsequentworkstation tasks for that network) for which prompting is to be suspended.The LPRE or LPOST commands display reference numbers.


nnnnrrsIs the workstation task reference number assigned by Unicenter CA-7.

nnnnUnicenter CA-7 job number.

rrRelative sequence of the network in relation to other networksassociated with the job. For input workstation networks, the value is00. Leading zeros cannot be omitted.

sRelative position of the station within the network. The first stationis position 1.

Usage Notes

Prompting suspended by a NOPRMP command can only be reinstated by aPRMP request.

A NOPRMP request issued on a global basis (for example, JOB=ALL orJOB=ALLP) only affects those jobs in the queue at the time the request isprocessed.

An alternative to using the NOPRMP function for suppressing prompts isavailable through the SSCAN command. This allows total suppression ofreprompting after the initial prompt message is issued.

You may also use the XUPD panel to suppress prompts for a selected job.

ExamplesNOPRMP,JOB=17

NOPRMP,JOB=ALL

NOPRMP,REF=18�2�21

482 Commands Guide

NXTCYC

NXTCYC

The NXTCYC top line command bypasses one or more normally scheduledprocessing cycles of a CPU job. A normally scheduled processing cycle iswhere schedule scan brings the job into the request queue. This bypass can befor a single cycle or for all subsequent cycles until further notice is providedwith another option of the command.

The NXTCYC command only affects jobs selected by schedule scan. It doesnot prevent jobs from being triggered or repeated.

The next time the job is scheduled to run, a message is written to the UnicenterCA-7 master station indicating it was not scheduled. For an explanation ofthese messages, see the Message Guide.


NXTCYC

��──NXTCYC─ ──,JOB=jobname ──,SET= ──┬ ┬─OFF─ ───────────────────────�� ├ ┤─ON── └ ┘─SKP─

JOBIdentifies the job for which scheduling is to be altered. The option must be ajob name.


Required: Yes

SETIndicates which of the options for skipping processing cycles is to be used.

Required: Yes

OFFCauses all regularly scheduled processing cycles to be skipped, and isso indicated on LJOB and LLOCK displays, until the schedulingindicator is again reset (SET=ON). When SET=OFF is used to bypassscheduling indefinitely, SET=ON must be entered to reinstate normalscheduling activity. SET=OFF indicates jobs that have been specifiedon a job forecast.

ONReinstates normal scheduling previously altered by a SET=SKP orSET=OFF command. SET=ON can be used to reinstate schedulingbefore one cycle is skipped (where SET=SKP has been used).


NXTCYC

SKPCauses only the next regularly scheduled processing cycle to beskipped. SET=SKP can be used to skip a processing cycle for a jobthat was demanded to run ahead of schedule. If SET=SKP is used, theschedule indicator automatically resets to restore normal schedulingactivity when one cycle has been skipped. Jobs with SET=SKPspecified appear on forecast panel displays and are indicated on LJOBand LLOCK displays.

Usage Notes

The NXTCYC command has no effect on jobs that are triggered by AUTOschedules.

An option to skip the next processing cycle is also available with the DEMANDcommand.

The NXTCYC command has no impact on repeating jobs that are already in theUnicenter CA-7 queues. However, if the NXTCYC setting suppresses the firstjob in a repeating set, the entire set is skipped.

ExamplesNXTCYC,JOB=CA7JOB1,SET=SKP

NXTCYC,JOB=CA7JOB2,SET=OFF

NXTCYC,JOB=CA7JOB2,SET=ON

484 Commands Guide

OUT

OUT

The OUT top line command indicates the completion of a workstation task. TheOUT command, used after an IN command, uses a reference number foridentifying each station. The reference number is generated by Unicenter CA-7each time the network enters the queue. This number can be obtained by doingan LPRE or LPOST command. This function is available as the O option on theQM.6 and QM.7 panels.


OUT

��──OUT─ ──,REF= ──┬ ┬─nnnnrrs─────── ──────────────────────────────�� │ │┌ ┐─,───── └ ┘──( ───� ┴nnnnrrs )

REFIdentifies the workstation network tasks to be logged out.

Required: Yes

nnnnrrsIdentifies a single workstation reference number.

Note: Reference numbers can be obtained by using the LPRE orLPOST commands.

nnnnUnicenter CA-7 job number. Leading zeros can be omitted.



(nnnnrrs,...,nnnnrrs)Identifies up to 10 reference numbers. Must be enclosed inparentheses.


OUT

Usage Notes

You can use the LOGOUT command on page 368 in place of OUT. You canuse the “IO” on page 271 to both log in and log out with a single command.

The XPRE, XPOST, XSPRE, and XSPOST online formatted panels can beused when working with 3270 terminals.

Unicenter CA-7 responds to each OUT command with the following information:

■ Original OUT command


■ Network name

■ SUBID

■ Station name

■ Remarks indicating the disposition of the OUT command

Following is a possible OUT command remark besides those discussed underthe IN command in “IO Command Response” on page 272. This appears onthe panel under the heading REMARKS.

NOT LOGGED IN

Reason: The station identified by the reference number has not been logged in.

Action: Determine why the station has not been logged in. If the missing login was anoversight, log the station IN and reenter the OUT request, or use the IO command to login and log out together.

ExamplesOUT,REF=��11�11

Logout workstation 0011011 referenced by Unicenter CA-7 job 0011, networksequence 01 and station position 1.

OUT,REF=11��11

Same as above, only leading zeros of job number have been omitted.

486 Commands Guide

POST

POST

The POST command indicates to the Unicenter CA-7 system that apreexecution requirement for a job in the request queue has been satisfied.Two categories of requirements can be satisfied, internal and external. Internalrequirements are known within the Unicenter CA-7 database and controlled byUnicenter CA-7. An example of an internal requirement would be thecompletion of another job controlled by Unicenter CA-7 whose completionsatisfies a requirement for a dependent job. External requirements are definedin the Unicenter CA-7 database but not controlled by Unicenter CA-7. Externalrequirements must be satisfied by a manual post unless the requirement iscataloged in the Unicenter CA-7 catalog before the using job is scheduled intothe request queue. This function is available through the “QM.2 CPU JobPredecessors Prompt Panel” on page 516.


POST

��──POST─ ──,JOB= ──┬ ┬─jobname─── ──────────────────────────────────� └ ┘─jobnumber─

�─ ──, ──┬ ┬──NW=network ──────────────────────────────── ───────────��├ ┤──USR=text ──────────────────────────────────├ ┤──DEPJOB=jobname ────────────────────────────

└ ┘──DSN=dataset ──┬ ┬───────────────────────────└ ┘──, ──┬ ┬──INTERNAL=YES ──────

│ │┌ ┐─,─────└ ┘──PREQ=( ───� ┴numbers )

JOBIndicates the unique Unicenter CA-7 job name in up to eight characters, orthe job number in up to four digits, for which requirements are to be posted.If job name is used and multiple jobs with the same name are found in therequest queue, the POST is rejected and an error message is issued. ThePOST command must then be reentered using the Unicenter CA-7 jobnumber.

jobnameIndicates a specific job name.


jobnumberIndicates a specific Unicenter CA-7 job number.



POST

NWIdentifies an input workstation network requirement to be posted assatisfied. Mutually exclusive with DEPJOB, DSN, and USR. In normalsituations, this type of requirement is posted automatically by UnicenterCA-7 when the network is logged complete with a LOGOUT, OUT, or IOcommand to the last workstation within this input network.


Required: No

USRIdentifies a user-defined description of a requirement to be posted assatisfied. Mutually exclusive with DEPJOB, DSN, and NW. When used,must match the text used to define the requirement on the DB.6 panel orwith the ADDRQ command.

Note: If the user requirement text contains commas, it cannot be satisfiedwith the POST command. It must be posted online with the QM.2 panel.


Required: No

DEPJOBIdentifies a predecessor job dependency requirement to be posted assatisfied. Value must be a specific job name. Mutually exclusive with DSN,NW, and USR. In normal situations, this type of requirement is postedautomatically by Unicenter CA-7 when the predecessor job completes itsexecution successfully. Manual posting would only be necessary if a jobdefined as a requirement was not to be run, or ran unsuccessfully and asuccessor job is to be run.

The DEPJOB must be posted if it is not currently defined to Unicenter CA-7(an external job).


Required: No

DSNIdentifies a data set requirement to be posted as satisfied. Value can be aspecific data set name or a Unicenter CA-7 data set number. If using anumber, only the number can be specified without the DS prefix. Mutuallyexclusive with DEPJOB, NW, and USR.

dsnameIndicates a specific data set name.


dsnumberIndicates a specific Unicenter CA-7 data set number.


488 Commands Guide

POST

INTERNALValid only in combination with DSN to indicate when the data set beingposted is internal to the Unicenter CA-7 workload. YES is the onlyacceptable value. Mutually exclusive with NW, USR, DEPJOB, and PREQ.In normal situations, requirements for internal data sets are postedautomatically by Unicenter CA-7.

Required: No

PREQValid only in combination with DSN to identify up to 11 numeric values tobe included with other Unicenter CA-7 log data logged as a result of thePOST command being issued. Mutually exclusive with NW, USR, DEPJOB,and INTERNAL. Values must be coded in sublist form, within parentheses.Up to 11 values separated by commas can be coded between theparentheses. Each value cannot exceed 4 numeric digits. This optional fieldcan be useful for logging any meaningful numbers, such as batch numbers,and so forth, which can later be reviewed in the log data set.

Required: No

Usage Notes

The Batch Card Load Program (BCLP) or U7SVC can be used to automaticallyhandle posting of external card-image input data sets.

Internal requirements are generally satisfied automatically by Unicenter CA-7.However, it is necessary to POST an internal requirement manually if any of thefollowing situations exist:

■ A data set was not created for the currently scheduled run.

■ A data set was not to be used in the currently scheduled run due to anoverride.

■ A job using a data set is being run multiple times using the same version ofthe data set for input to each run.

■ A job is being rerun using the same versions of input as in the original run.

■ A job defined as a requirement was not run, or ran unsuccessfully, and asuccessor job is to be run.

■ An input network defined as a job requirement is not complete, but the jobis to run.

If the completion of a requirement is not noted in the Unicenter CA-7 database,requirements must be satisfied by a manual POST after the using job isscheduled into the request queue. When dependencies and requirements forresources and other Unicenter CA-7 jobs or networks have been defined in thedatabase, Unicenter CA-7 handles satisfaction automatically upon thecompletion of the requirement.


POST

Manual posting of any requirement is not possible until the using job is in therequest queue.

Examples

For internal data set requirements

POST,JOB=163,DSN=CA7.DSN1,INTERNAL=YES

POST,JOB=12,DSN=15,INTERNAL=YES

POST,JOB=CA7JOB1,DSN=CA7.DSN1,INTERNAL=YES

For external data set requirements

POST,JOB=163,DSN=CA7.EXTRNL.DSN1

POST,JOB=12,DSN=15

POST,JOB=CA7JOB1,DSN=CA7.BATCH.INPUT1,PREQ=(17,19,2�,32)

For job dependency requirements

POST,JOB=CA7JOB3,DEPJOB=CA7JOB1

POST,JOB=19,DEPJOB=CA7JOB1

For input network requirements

POST,JOB=CA7JOB3,NW=PAYNTWK

POST,JOB=193,NW=CA7JOB2

For user requirements

POST,JOB=CA7,USR=USER WILL CALL TO RELEASE

POST,JOB=12,USR=CHECK WITH JOE BEFORE RUNNING

490 Commands Guide

PRINT

PRINT

The PRINT command produces a month-by-month listing of indicated basecalendars. PRINT produces output that reflects the beginning and ending daysof each month, holidays, or any other nonprocessing days that were definedwhen the calendar was produced.


PRINT

��──PRINT─ ──,SCAL=xx ──┬ ┬────────── ──────────────────────────────��└ ┘──,YEAR=yy

SCALUsed to specify the user-supplied unique characters that identify the basecalendar to be printed. Value is the two unique characters used duringinitial creation of the calendar. These characters provide the xx portion ofthe base calendar name, SCALyyxx.


Required: Yes

YEARUsed to specify the year of the base calendar to be printed. Value is thelast two digits of the base calendar year (05 = 2005). It also provides the yyportion of the base calendar name, SCALyyxx. This must be the same yearspecified when the calendar was initially created.

Default: Current year

Limits: 2 numeric characters

Required: No

Usage Notes

When the beginning and ending days of the month fall on available processingdays, they are specifically indicated. Periods are used to bracket these days(for example, .B01. or .E12.). They are enclosed in parentheses whenbeginning/ending days of the month fall on nonavailable processing days.


PRINT

ExamplePRINT,YEAR=�5,SCAL=5D

Causes a month-by-month printout of base calendar SCAL055D.

The following figure presents a portion of the output from a PRINT commandfor a base calendar with a holiday list.

129+�,�� 13�+�,�� 131+�,�� CA-7 BASE CALENDAR SCAL�7WD �� 132+�,�� FOR YEAR 2��7 �� 133+�,�� DATE �5�64 �� 134+�,�� 135+�,��

137+�,�� 138+�,�� 139+�,�� MONTH 1 JAN �� 14�+�,�� 141+�,�� SUN MON TUE WED THU FRI SAT �� 142+�,�� 143+�,�� (B1) 2 3 4 5 ��144+�,�� 8 9 1� 11 12 ��145+�,�� 11 12 13 14 15 ��146+�,�� 15 16 17 18 19 ��147+�,�� 22 23 24 25 26 �� 148+�,�� 29 3� (E1) �� 149+�,�� 15�+�,��

152+�,�� 153+�,�� 154+�,�� MONTH 2 FEB �� 155+�,�� 156+�,�� SUN MON TUE WED THU FRI SAT �� 157+�,�� 158+�,�� (B1) 2 ��159+�,�� 5 6 7 8 9 ��16�+�,�� 12 13 14 15 16 ��161+�,�� 19 2� 21 22 23 �� 162+�,�� 26 27 (E2) �� 163+�,�� 164+�,��

166+�,�� 167+�,�� 168+�,�� MONTH 3 MAR �� 169+�,�� 17�+�,�� SUN MON TUE WED THU FRI SAT �� 171+�,�� 172+�,�� (B3) 2 ��173+�,�� 5 6 7 8 9 ��174+�,�� 12 13 14 15 16 ��175+�,�� 19 2� 21 22 23 ��176+�,�� 26 27 28 29 3� (E3) �� 177+�,�� 178+�,��

492 Commands Guide

PRMP

PRMP

The PRMP top line command reinstates prompting after a previous NOPRMPcommand suspended it. PRMP can be used for an individual network, morethan one network, or an entire queue. This function is available for CPU jobsthrough the “QM.3 CPU Job Attributes Prompt Panel” on page 521.Workstation networks must use the PRMP command.


PRMP

��──PRMP──,─ ──┬ ┬──JOB= ──┬ ┬─nnnn─ ────────────────────────────────�� │ │├ ┤─ALL── │ │└ ┘─ALLP─


JOBIdentifies the jobs for which prompting is to be reinstated.

Required: Yes, unless REF is used (in which case JOB must be omitted)

nnnnIndicates Unicenter CA-7 job number.


ALLPIndicates all jobs including those in the preprocess queue.


PRMP

REFSpecifies a particular workstation network task (and all subsequentworkstation tasks for that network) for which prompting is to be reinstated.Reference numbers can be obtained by using the LPRE or LPOSTcommands.

Required: Yes, unless JOB is used (in which case REF must be omitted)

nnnnrrsIs the workstation task reference number assigned by Unicenter CA-7.




Usage Notes

For information about the command used to suspend prompting, see“NOPRMP” on page 481.

When PRMP is used with a reference number, all subsequent stations areaffected.

ExamplesPRMP,JOB=17

PRMP,JOB=ALL

PRMP,REF=18�2�22

494 Commands Guide

PRRNJCL

PRRNJCL

The PRRNJCL command lists and optionally deletes JCL for all jobs in theprior-run queue that have JCL retained.


PRRNJCL

��──PRRNJCL─ ──┬ ┬─────────────────── ─────────────────────────────�� │ │┌ ┐─NO──

└ ┘──,UPDATE= ──┴ ┴─YES─

UPDATESpecifies whether JCL for the prior-run queue entries listed is to be deletedto release that space.

Default: NO

Required: No

NOSpecifies that the prior-run queue entries with JCL retained be listedonly.

YESSpecifies JCL is to be deleted in addition to entries being listed.

Examples

� �PRRNJCL

DATE=YY.DDD CA-7 PRIOR-RUN JCL ANALYZE REPORT PAGE NO. ��4

JOB CA-7# STARTING ENDING SYSTEM COMMENTS NAME DATE TIME DATE TIME NAMEIFCS2��M �757 yy/ddd 1931 yy/ddd 1942 CAIFCS JCL RETAINED.IFCS2��C �1yy yy/ddd 2355 yy/ddd ��31 CAIFCS JCL RETAINED.IFNASH �3�9 yy/ddd �53� yy/ddd �534 CAIFCS JCL RETAINED.IFC537�� 8 yy/ddd �559 yy/ddd �652 CAIFCS JCL RETAINED.IFCS63� ��29 yy/ddd 1216 yy/ddd 1221 CAIFCS JCL RETAINED.IFCS63�2 ��3� yy/ddd 1222 yy/ddd 1229 CAIFCS JCL RETAINED.T2TSOPK3 ��61 yy/ddd �131 yy/ddd �14� S168 JCL RETAINED.T2SYSTM2 ��63 yy/ddd �14� yy/ddd �2�� S168 JCL RETAINED.T2LIB121 ��65 yy/ddd �2�3 yy/ddd �22� S168 JCL RETAINED.T2LIB122 ��66 yy/ddd �221 yy/ddd �238 S168 JCL RETAINED.

SAN�-�� ANALYZE REQUEST COMPLETED AT 16:23:39 YY.DDD.� �


PRSCF

PRSCF

The PRSCF command frees a shared, exclusive, or RCT resource connected toa job that:

■ Is currently executing

■ Is in ABEND status in the request queue

■ Has already executed and purged from the request queue


PRSCF

��──PRSCF─ ──,JOB= ──┬ ┬─jobname─── ──,RSRC=resource ─────────────────� └ ┘─jobnumber─

�─ ──┬ ┬──────────── ──────────────────────────────────────────────��└ ┘──,FORCE=YES

JOBSpecifies the name or Unicenter CA-7 number of the job to which theresource is attached.

Limits: 1 to 8 alphanumeric characters1 to 4 numeric characters

Required: Yes

RSRCSpecifies the fully qualified resource name to free. You can optionallyspecify * to indicate all resources connected to the job are to be freed.


Required: Yes

FORCEFORCE=YES indicates that Unicenter CA-7 is not to evaluate theavailability of the named resources for this run of the job only. The namedresources are NOT used by this run of the job. This keyword can be usedon an exception basis to allow a job in W-RSRC status to bypass VRMchecking for one or more resources defined for it on the RM.1 panel.

Required: No

496 Commands Guide

PRSCF

Example

� �PRSRF,RSRC=RESOURCE.TYPE2.EXEC,JOB=TESTJOBB SPOR-35 PRSRCF SUCCESSFUL

RESOURCE : RESOUCE.TYPE2.EXEC FREED FOR JOB : TESTJOBB

SPO4-�� REQUEST COMPLETED AT 13:25:53 ON YY.DDD.� �


PRSQA

PRSQA

The PRSQA command activates a corequisite resource. When a job isconnected to a corequisite resource and the resource usage type is N or active,the corequisite resource must be activated using the PRSQA command.


PRSQA

��──PRSQA─ ──,RSRC=resource ──────────────────────────────────────��

RSRCSpecifies a fully qualified corequisite resource name.


Required: Yes

Example

� �PRSQA,RSRC=CICSREG8 SPOR-39 PRSQA SUCCESSFUL

COREQUISITE RESOURCE: CICSREG8

ACTIVATED.

SPO4-�� REQUEST COMPLETED AT 15:48:46 ON YY.DDD.

� �

498 Commands Guide

PRSQD

PRSQD

The PRSQD command deactivates a corequisite resource activated by aPRSQA command. This command is the only way to deactivate a corequisiteresource.


PRSQD

��──PRSQD─ ──,RSRC=resource ──────────────────────────────────────��

RSRCSpecifies a fully qualified corequisite resource name.


Required: Yes

Example

� �PRSQD,RSRC=CICSREG8 SPOR-37 PRSQD SUCCESSFUL

COREQUISITE RESOURCE: CICSREG8

DEACTIVATED.

SPO4-�� REQUEST COMPLETED AT 16:56:54 ON YY.DDD.

� �


PS

PS

The PS command displays the Personal Scheduling panel. Enter PS as theFUNCTION value on any other menu or formatted input panel or as a top linecommand.


PS

��──PS──────────────────────────────────────────────────────────��

It has no associated keywords.

For a detailed discussion of this command and its functions, see the DatabaseMaintenance Guide.

Unicenter CA-7/Personal Scheduling Panel

� � FUNCTION===> (ADD,LIST,UPD,DEL,SUBMIT,STATUS,QUIT)

JOBNAME =>JCL ID => JCL LIB =>

WHEN TO SCHEDULE: PATTERN =>

TIME TO RUN => (��1-24��)

JOB RUNS AFTER => (JOBNAME - SUBMIT ONLY)

- - - - - - - STATUS INFORMATION (DISPLAY ONLY) - - - - - - -

MESSAGE: PS��-�� ENTER THE DESIRED FUNCTION AND JOB INFORMATION� �

500 Commands Guide

QJCL

QJCL

The QJCL command either reviews JCL for jobs in the request or prior-runqueues, or modifies JCL for jobs in the request queue. Use this facility to makeoverrides to JCL even if the override library or scheduled overrides are used.This facilty also accomplishes reusing JCL from jobs in the prior-run queue.This function is available on the “QM” on page 503 as FUNCTION value 5 oron any other menu or formatted panel as FUNCTION value QM.5.


QJCL

��──QJCL─ ──, ──┬ ┬─jobname─── ─────────────────────────────────────�� └ ┘─jobnumber─

jobnameIdentifies the unique Unicenter CA-7 job name of the job in the requestqueue whose JCL is to be updated.


jobnumberIdentifies the unique Unicenter CA-7 job number of the job in the requestqueue whose JCL is to be updated.



QJCL

Usage Notes

In restart situations, this command can be used to fetch a request or prior-runqueue job's JCL into an active area. Temporary changes can be made asnecessary to correct the problem that occurred. For assistance in performingany data set cleanup that can be required, see also “QM” on page 503.

For more information about overriding JCL, see the JCLOVRD command in thischapter, and the JCL-OVRD and USE-OVRD-LIB fields on the DB.1 panel inthe Database Maintenance Guide. Also see the discussion of the "EditFacilities" in the Database Maintenance Guide.

JCL saved for jobs in the prior-run queue can also be brought into the activearea and, through a series of commands, be saved to a JCL library or storedfor jobs in the request queue to be used for the current execution of the job.

This command results in a panel being returned. For more information aboutthat panel, see “QM.5 Queued JCL Panel” on page 531.

This command should only be done online.

502 Commands Guide

QM

QM

This panel accesses fill-in-the-blank function panels for queue maintenancefunctions.

� � ----------------------- CA-7 QUEUE MAINTENANCE MENU ------------------------ FUNCTION ===>

MAINTENANCE TO BE PERFORMED ON:1 - CPU JOBS STATUS2 - CPU JOB PREDECESSORS3 - CPU JOB ATTRIBUTES4 - CPU JOB IN RESTART STATUS5 - QUEUED JCL6 - INPUT NETWORKS7 - OUTPUT NETWORKS

PROGRAM: QM�� MSG-INDX: �� -- QM -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:

■ QM as a top line command.

■ QM as the FUNCTION value on any other menu or formatted input panel.

To exit:

■ Position the cursor to the top line and enter a Unicenter CA-7 command.

■ Provide the name of some other menu or formatted input panel in theFUNCTION field.

Usage Notes

Functions are identified on the panel with their numeric value and a briefdescription.

To select a formatted input panel, provide the appropriate number in theFUNCTION field and press Enter. The selected panel then appears.


QM

PF Keys

Once a function has been selected on the menu and the function panel isdisplayed, program function key 3 (PF3) is temporarily set to return to the QMmenu panel. In native Unicenter CA-7 VTAM mode, any value that waspreviously assigned to PF3, by either the user or Unicenter CA-7, is temporarilyignored as long as the function panel is being used and reverts back to theoriginal value after it is used once or after a top line command is entered.

PF7 and PF8 are similarly temporarily overridden to /PAGE-1 and /PAGE+1respectively until PF3 is pressed or a top line command is issued.

Special considerations apply when using Unicenter CA-7 under TSO-ISPF.

■ PF key interrupts are not processed by Unicenter CA-7, unless PASSTHRUis the ISPF application command table value associated with the ISPFcommand that is assigned to the PF key in question.

■ If PF3 is assigned the END command in ISPF, PF3 ends the UnicenterCA-7 TSO-ISPF session unless END is assigned a value of PASSTHRU inthe ISPF application command table.

504 Commands Guide

QM.1 CPU Jobs Status Prompt Panel


This panel lists jobs from the queues for purposes of updating the status of thejobs. There is no equivalent batch function.

� � ------------- CA-7 QUEUE MAINTENANCE - CPU JOBS STATUS PROMPT ------------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

DESIRED JOB(S) => SPECIFIC, GENERIC OR CA-7# (DEFAULT ALL) LIST SEQUENCE => J=JOBNAME, N=JOB#, E=QUEUE ENTRY (DEFAULT) CA-7 QUEUE ID => REQ RDY OR ACT (DEFAULT IS REQ)

DISPLAY RQMTS => NO (DISPLAY REQUIREMENT INFORMATION) RQMT CRITERIA => (ALL,ANY,JOB,INT,EXT,USR,NWK,SUB,HLD,JCLO, VER,SKEL,REST,BINT)

FILL FUNCTION => (OPTIONAL)C = CANCEL R = RELEASE FROM HOLD STATUSF = GO TO RESTART SCREEN S = SATISFY SUBMIT TIME RQMTH = PLACE IN HOLD U = GO TO ATTRIBUTE UPDATE SCREENJ = REVERSE JCL OVERRIDE RQMT V = REVERSE VERIFY RQMT STATUSP = RESPOND TO PROMPTING X = GO TO JOB PREDECESSOR SCREENQ = REQUEUE FOR A RESTART E = FETCH QUEUED JCL AND EDIT

PROGRAM: QM2F MSG-INDX: �� -- QM.1 -- YY.DDD / HH:MM:SS MESSAGE: ENTER VALUES, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

� �

To display, enter:

■ 1 as the FUNCTION on the QM panel.

■ QM.1 as the FUNCTION on any other menu or formatted panel.

■ QM.1 as a top line command.

■ If an error is encountered with XQ, XQJ, XQM, or XQN top line commands,this panel is returned for ease of correction and reentry.

To exit:


■ Provide the name of some other panel in the FUNCTION field.

■ For other options, see “PF Keys” on page 504.




FUNCTIONLeave blank to list jobs. Otherwise, specify the name of some other panelto which a transfer is desired.

DESIRED JOB(S)Jobs to be listed. May be a specific job name, job number or generic jobname. Default is all jobs. Same as JOB keyword for top line XQ commands.

LIST SEQUENCESequence of output desired. Default is queue entry sequence. J indicatesjob name sequence. N indicates job number sequence. J and N are onlyallowed values.

CA-7 QUEUE IDQueue to be searched. Same as Q keyword parameter for top linecommands. Default is REQ for request queue. Only allowable values areREQ, RDY, and ACT.

DISPLAY RQMTSDisplays requirement information. (Specify YES to get the XQM displayformat.)

RQMT CRITERIASpecifies the information to be displayed.

ALLList all jobs regardless of outstanding requirements. This is the default.

ANYList only those jobs with at least one requirement.

BINTList only those jobs that have internal data set requirements, but nounsatisfied job requirements.

EXTList only those jobs with external data set requirements.

HLDList only those jobs with a hold requirement.

INTList only those jobs with internal data set requirements.

JCLOList only those jobs with a JCL override requirement.

JOBList only those jobs with job requirements.

506 Commands Guide


NWKList only those jobs with network requirements.

RESTList only those jobs in restart status.

SKELList only those jobs in skeleton status.

SUBList only those jobs with submit-time requirements.

USRList only those jobs with user requirements.

VERList only those jobs with a verify requirement.

FILL FUNCTIONSame as FILL keyword parameter for top line command. When used, thedisplay has this value already entered in the F function field for all jobs.Default is none. Allowable values are:

CCancel the job. Depending on the initialization file CANCEL statementvalue, a transfer to the REASON FOR CANCEL panel may occur foreach job given this value. For more information, see the REASONFOR CANCEL panel.

EFetch queued JCL, transfer to the edit facility (similar to QM.5) andreturn to this panel when finished there.

FTransfer to the CPU JOB IN RESTART STATUS panel (QM.4) for thisjob and return to this panel when finished there.

HPut the job in hold status.

JReverse the JCL override requirement: if there is one, satisfy it;otherwise, establish one.

PRespond to a deadline prompt.

QRequeue the job for a restart.



RRelease the job from hold status.

SSatisfy a submit time requirement.

UTransfer to the CPU JOB ATTRIBUTES panel (QM.3) for this job andreturn to this panel when finished there.

VReverse VERIFY requirement: if there is one, satisfy it, otherwise,establish one.

XTransfer to the CPU JOB PREDECESSORS panel (QM.2) for this joband return to this panel when finished there.

508 Commands Guide


QM.1-X CPU Jobs Status Panel

The following panel is displayed after the desired values have been entered onthe QM.1 panel with DISPLAY RQMTS=NO.

� � ----------------- CA-7 QUEUE MAINTENANCE - CPU JOBS STATUS ----------------- F-JOBNAME--CA7# BDTEST�3 ��1 JOB: � BDTEST�1 ��2 SEQ: ENTRY BDTEST�2 ��3 QUEUE: REQ LIST: ALL

FUNCTIONS: C=CANCEL F=RESTART H=HOLD J=JCLOVRD P=RSVP Q=REQUEUE R=RELEASE S=SUBTM OFF U=UPDATE V=VERIFY X=RQMT POST E=EDIT QJCL PROGRAM: QM2� MSG-INDX: �� -- QM.1-X -- YY.DDD / HH:MM:SS MESSAGE: ENTER FUNCTION IN 'F' FIELD OR ENTER A COMMAND ON THE TOP LINE

� �


FFunction field

JOBNAMEUnicenter CA-7 job name

CA7#Unicenter CA-7 job number

JOB:Job name selection criteria

SEQ:Display sequence

QUEUE:Queue that was searched: request, ready, or active

LIST:Display selection criteria

FUNCTIONS:Possible line functions



Usage Notes

Job names and numbers are listed below their column heading. Up to fourcolumns of up to 18 jobs each can appear on each page. Up to 72 jobs perpage can appear. Display sequence and queue values are shown on the rightjust above a legend of available F column function values.

To perform an update on any of the listed jobs, enter the desired value from thelegend in the F column just in front of the job you want to update. Multiple jobscan be selected before pressing Enter. (If a FILL FUNCTION value was enteredon the QM.1 panel, that value appears in this column for each entry.)

When requested functions are completed, the panel is returned with a messageat the bottom in the MESSAGE area. Functions that were performed without anerror show an * in the F field. Functions that encountered errors show ? in theF field. To simplify correction of any errors, both * and ? are ignored for input.Only entries with other F values are processed.

The display continues to reflect the queue status at the time of the initialrequest. It is not refreshed after each update. After several updates, it may bedesirable to repeat the initial QM.1 function.

After an update is made, the scrolling capability is disabled. Repeat the initialQM.1 function to establish the scrolling capability.

510 Commands Guide


QM.1-M CPU Job Requirements

This panel is displayed after the desired values have been entered on the QM.1panel with DISPLAY RQMTS=YES.

� � -------------- CA-7 QUEUE MAINTENANCE - CPU JOBS STATUS (RQMTS) -------------- F-JOBNAME---J--I--E--U--N-SHJV F-JOBNAME---J--I--E--U--N-SHJV

BDTEST�1 . . . . . H XXTEST1� . . 1 . . J JOB: � BDTEST�2 1 . 1 2 . XXTEST11 . 1 . . . SEQ: JOBNAME BDTEST�3 . 2 . . . V XXTEST12 . . 1 . . QUEUE: REQ BDTEST�4 . . . . . �SKL LIST: ALL BDTEST�5 . . . . . S BDTEST�6 1 . . . . J FUNCTIONS: BDTEST�7 . . . . . C=CANCEL BDTEST�8 . . . . . S F=RESTART BDTEST�9 . . . . . V H=HOLD XXTEST�1 1 . . . . J=JCLOVRD XXTEST�2 . 3 . 2 . H P=RSVP XXTEST�3 . . 1 . . Q=REQUEUE XXTEST�4 . 1 . . . R=RELEASE XXTEST�5 . . . 1 . J S=SUBTM OFF XXTEST�6 1 . . . . U=UPDATE XXTEST�7 . 1 . . . S V=VERIFY XXTEST�8 2 . . . . X=RQMT POST XXTEST�9 . . 1 . . E=EDIT QJCL PROGRAM: QM2� MSG-INDX: �� -- QM.1-M -- YY.DDD / HH:MM:SS MESSAGE: ENTER FUNCTION IN 'F' FIELD OR ENTER A COMMAND ON THE TOP LINE

� �


FFunction name

JOBNAMEUnicenter CA-7 job name

JNumber of outstanding job requirements

INumber of outstanding internal data set requirements

ENumber of outstanding external data set requirements

UNumber of outstanding user requirements

NNumber of outstanding network requirements



SIndicates an outstanding submit time requirement

Special character settings beginning with an asterisk can appear under theSHJV heading to indicate special situations. These are:

*CMPIndicates job is in completed status

*ERRIndicates an error occurred attempting to collect the requirementinformation

*NOFIndicates job not found in requested queue. (This normally happenswhen you post the last requirement for a job, and it moves from therequest to the ready queue.)

*RSTIndicates job is in restart status

*SKLIndicates job is in skeleton status

HIndicates an outstanding hold requirement

JIndicates an outstanding JCL override requirement

VIndicates an outstanding verify requirement

JOB:Job name selection criteria

SEQ:Display sequence

QUEUE:Queue that was searched: request, ready, or active

LIST:Display selection criteria

FUNCTIONS:Possible line functions

512 Commands Guide


Usage Notes

The jobs are listed in job name sequence. Line functions can be issued for anyjob in the same way as the QM.1-X panel. For security purposes, line functionsentered on the QM.1-M panel are considered to have come from the QM.1-Xpanel.

The outstanding requirements for each job listed are reflected to the right of thejob name. Categories that can have more than one requirement are two-digitnumeric fields. If the value is zero, a period is displayed. If the value exceeds99, two asterisks are displayed to represent an overflow situation (by using theRequirement Post line command 'X', you can see the total master requirementcount). Categories that are yes/no situations (such as Hold) are represented bythe appropriate character for yes or a period for no.



QM.1-XC Reason for Cancel Panel

This panel provides an explanation of why a job is being manually canceled.

It is displayed for each C function on the QM.1 panel but only ifREASON=OPTIONAL or REASON=REQUIRED is specified on the initializationfile CANCEL statement.

� � -------------- CA-7 QUEUE MAINTENANCE - REASON FOR CANCEL ------------------

JOB NAME: SARWKY�1 JOB NUMBER: 1482

REASON:

(MAXIMUM OF 4� CHARACTERS)

PROGRAM: QM7� MSG-INDX: �� -- QM.1-XC -- YY.DDD / HH:MM:SS MESSAGE: GIVE THE REASON FOR CANCELING THE JOB

� �


JOB NAMESpecifies the name of the job to be canceled.

JOB NUMBERSpecifies the job number of the job to be canceled.

REASONSpecifies the reason for the cancellation. The cursor is positioned herewhen the panel is first displayed. Any text entered is displayed onsubsequent LRLOG inquiries.

514 Commands Guide


Usage Notes

If the installation does not require a reason, pressing Enter without providing areason cancels the job without logging any descriptive text. If the installationrequires a reason, the cancellation does not occur until some text is provided.For more informatin about the installation's options for this panel, see theinitialization file CANCEL statement.

Unicenter CA-11 restart reasons are not expanded here as they are on theQM.4 panel for restarts. Any value entered here is assumed to be descriptivetext and is logged as entered.


QM.2 CPU Job Predecessors Prompt Panel


This panel lists the predecessors of jobs and allows posting those jobs as beingcomplete or not. No equivalent batch function exists.

� � ----------- CA-7 QUEUE MAINTENANCE - CPU JOB PREDECESSORS PROMPT ----------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

JOB TO BE UPDATED =====> SPECIFIC NAME OR CA-7 JOB#

LIST ALL PREDECESSORS => N Y=YES (DEFAULT IS LIST ONLY THE UNSATISFIED ONES)

PROGRAM: QM3� MSG-INDX: �� -- QM.2 -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:




■ If an error is encountered with a top line XRQ command, this panel isreturned for ease of correction and reentry.

To exit:




516 Commands Guide



FUNCTIONLeave blank to list a job. Otherwise, specify the name of some other panelto which you want to transfer or position the cursor to the top line and entera top line command.

JOB TO BE UPDATEDJob name or Unicenter CA-7 job number of the desired job. Required, thereis no default.

LIST ALL PREDECESSORSEnter Y to list even satisfied predecessors. Default is to list only unsatisfiedones (N).



QM.2-X CPU Job Predecessors

After entering the desired values on the QM.2 panel, press Enter. A panelsimilar to this then displays.

� � -------------- CA-7 QUEUE MAINTENANCE - CPU JOB PREDECESSORS --------------- JOB: D463XX�3 CA-7#: ��2 MCNT: ��4 F-TYP--NUMBER--E-DESCRIPTION

HLD JOB HELD IN REQUEST QUEUE JOB A D463XX�1

USR O SAMPLE NEXT-RUN ONLY PREDECESSOR NWK ��8 D4�218ED

PROGRAM: QM3� MSG-INDX: �� -- QM.2-X -- YY.DDD / HH:MM:SS MESSAGE:

� �


JOBSpecifies the job name.

CA-7#Specifies the job number.

MCNTSpecifies the number of unsatisfied predecessors. The unsatisfiedpredecessors are listed below a column heading.

FIndicates the function column in which updates are requested. An Xsatisfies the requirement, and a U UNPOSTs or causes that requirement tobe unsatisfied.

518 Commands Guide


TYPIndicates the type of predecessor.

EXTAn external data set. An external data set is one that is created or usedby Unicenter CA-7 jobs.

HLDHold status (see HOLD command and HOLD field on the CPU JobDefinition (DB.1) panel).

INTAn internal data set. An internal data set is one that is created andused by Unicenter CA-7 jobs.

JCLJCL modification (see JCLOVRD command and JCL-OVRD field on theCPU Job Definition (DB.1) panel).

JOBCPU job.

NWKInput network.

SUBSpecific submit time (see SUBTM command and the SBTM field on theCPU Job Scheduling Parameter Edit panel function of DB.2.1).

USRUser memo-form.

VERVerification (see VERIFY command and VERIFY field on the CPU JobDefinition (DB.1) panel).

NUMBERAppears for data sets and input networks and indicates the DSNBRassigned in the Unicenter CA-7 database.

EIndicates exceptions to normal requirements of this job.

AAdded through ADDRQ command (after the job entered the queues)

ODefined for this run only (through NEXT-RUN ONLY facility)

DESCRIPTIONDisplays a brief description of the predecessor.



Usage Notes

To post a predecessor complete, enter X in the F column in front of theappropriate line and press Enter. To unsatisfy an already satisfied predecessor,change the existing X to U.

This panel can also be displayed by the X function of the QM.1 panel.

If this panel was displayed as a result of entering an X on the QM.1 panel, youreturn to that panel after any updates are done.

520 Commands Guide

QM.3 CPU Job Attributes Prompt Panel


This panel lists the current attributes of a job and allows them to be changed.There is no equivalent batch function.

� � ------------ CA-7 QUEUE MAINTENANCE - CPU JOB ATTRIBUTES PROMPT ------------ FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

JOB TO BE UPDATED =====> SPECIFIC NAME OR CA-7 JOB#


� �

To display, enter:




■ If an error is encountered with a top line XUPD command, this panel isreturned for ease of correction and reentry.

To exit:







FUNCTIONLeave blank to list a job. Otherwise, specify the name of some other panelto which you want to transfer or position the cursor to the top line and entera top line command.

JOB TO BE UPDATEDJob name or job number of the desired job. Required, there is no default.

522 Commands Guide


QM.3-X CPU Job Attributes

After entering the desired values on the QM.3 panel, press Enter. A panelsimilar to this displays.

� � --------------- CA-7 QUEUE MAINTENANCE - CPU JOB ATTRIBUTES ---------------- JOB: D463XX�3 CA-7#: ��2 MCNT: ��4 QUEUE: REQ

---------SCHEDULING--------- ------MANUAL REQUIREMENTS------- DEADLINE TIME.... �5�58 13�4 JOB HELD...................... Y DUE-OUT TIME..... �5�58 13�4 MANUAL VERIFICATION REQUIRED.. N SUBMIT TIME...... �5�58 13�� JCL OVERRIDES REQUIRED........ N MAINID........... ALL REPEAT INTERVAL.. ��15 TYPE.. CLOCK COUNT.. ��98 STOP.. �5�59 1�� ----------RESTART----------- ------------PROMPTING------------ GENERATE CA-11 STEP....... N ELIGIBLE FOR PROMPTS... Y FORMAT CA-11 CMT.......... N PROMPT ACKNOWLEDGED.... N RETAIN JCL IN PRRN QUEUE.. N LTERM FOR MESSAGES..... MASTER

----------------------------RESOURCES----------------------------- JOB CLASS............. A JOB PRIORITY.......... 1�� ELAPSED TIME (HHMM)... ��1 TAPE DRIVES OF TYPE1.. �� CPU TIME (MMMSS)...... ��1 TAPE DRIVES OF TYPE2.. ��


� �

To update the values on the panel, position the cursor at a value and key thedesired value over the old value. Multiple fields can be updated if so desired.


DEADLINE TIMEThis value is composed of two fields in the format yyddd and hhmmrespectively, and is the date and time that a job must start or the job isflagged as LATE.

DUE-OUT TIMEThis value is composed of two fields in the format yyddd and hhmmrespectively, and is the date and time that a job must complete or the job isflagged as LATE.

SUBMIT TIMEThis value is composed of two fields in the format yyddd and hhmmrespectively. Null values indicate the job has no submit time-of-dayrequirement. To establish a requirement, enter appropriate data. To removean existing submit time-of-day requirement, set this value to precede thecurrent date and time-of-day.



MAINIDThis value should be of the form ALL, SYn, or /SYn. It indicates to whichCPU the job is submitted. (See MAINID on the DB.1 panel for the job.) Forexample, SY1 means CPU #1 and /SY1 means NOT CPU #1, as follows:

SYnCPU number to be used.

/SYnCPU number of CPU not to be used.

ALLAny CPU can be used. This field cannot be modified after a job hasbeen submitted.

JOB HELDThis value is Y or N and indicates hold status. This applies only to jobs inthe request queue or the ready queue if not already submitted to OS.

MANUAL VERIFICATION REQUIREDThis value is Y or N and indicates manual verification requirement status.This applies only to jobs in the request queue.

JCL OVERRIDES REQUIREDThis value is Y or N and indicates a JCL override verification status. Thisapplies only to jobs in the request queue.

REPEATThis line only appears if the job is to be repeated.

INTERVALThis numeric field determines the amount of time (in hhmm format) betweeniterations of the job. The value is from 00 to 23 for hh and from 00 to 59for mm. Set this field to zero to stop repeating the job.

TYPEThis field determines how to determine the submit time of the next iteration.If the value is CLOCK, the interval is added to the previous iteration'ssubmit time requirement. If the value is START or END, the interval isadded to the previous iteration's start or end time, respectively. TYPE canbe CLOCK, START, or END. Only the first letter need be typed.

COUNTThis field determines how many more times to repeat the job. If the field iszero, the job is repeated until the stop time is reached.

STOPThis two field value determines the clock time when the job can no longerbe repeated. The maximum value is 1439 minutes (24 hours minus 1minute) after the submit time requirement of the first job in the repeatingcycle.

GENERATE CA-11 STEPThis value is Y or N and identifies whether a Unicenter CA-11 step shouldbe generated. This field cannot be modified after a job has been submitted.

524 Commands Guide


FORMAT CA-11 CMTThis value is Y or N and identifies if F processing is to be done by thegenerated Unicenter CA-11 step. This field cannot be modified after a jobhas been submitted.

RETAIN JCL IN PRRN QUEUEThis value is Y or N and indicates whether the JCL is to be retained in thePRRN queue. (See RETAIN-JCL on the DB.1 panel for the job.)

ELIGIBLE FOR PROMPTSThis value is Y or N and indicates if the job should be prompted if late.(See PROMPTS on the DB.1 panel for the job.)

PROMPT ACKNOWLEDGEDThis value is Y or N and indicates if a late prompt has been acknowledged.Any attempt to acknowledge a prompt when one has not been received isignored.

LTERM FOR MESSAGESThis field identifies the logical terminal to receive status and promptingmessages for this job. (See LTERM on the DB.1 panel for the job.) Value isa maximum of eight characters.

JOB CLASSThe value is any single alphanumeric character. It indicates the UnicenterCA-7 job class. (See CLASS on the DB.1 panel for the job.) This fieldcannot be modified after a job has been submitted.

ELAPSED TIMEThis numeric field indicates the average elapsed time for the job in hhmmformat. The value is from 0 to 23 for hh and from 0 to 59 for mm. This fieldcannot be modified after a job has been submitted.

CPU TIMEThis numeric field indicates the average CPU time use for the job inmmmss format. The value is from 0 to 999 for mmm and from 0 to 59 forss. This applies only to jobs in the request queue.

JOB PRIORITYThis numeric field indicates the original Unicenter CA-7 workload balancingcurrent job priority. The value is from 0 to 255.

TAPE DRIVES OF TYPE 1This numeric field indicates the number of tape drives of Type 1 needed forthe job. The value is from 0 to 255.

TAPE DRIVES OF TYPE 2This numeric field indicates the number of tape drives of Type 2 needed forthe job. The value is from 0 to 255.



Usage Notes

After all values have been entered, press Enter and the updates are made. Amessage indicates what action was taken.

You can also display this panel using the U function of the QM.1 panel.

If this panel is displayed as a result of entering a U on the QM.1 panel, return isto that panel after any updates are done.

526 Commands Guide

QM.4 CPU Job In Restart Status Prompt Panel


This panel lists jobs and allows them to be restarted. The equivalent batchcommand is RESTART.

� � -------- CA-7 QUEUE MAINTENANCE - CPU JOB IN RESTART STATUS PROMPT --------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

JOB TO BE RESTARTED =====> SPECIFIC NAME OR CA-7 JOB#


� �

To display, enter:




■ F as the function on the QM.1 panel.

■ If an error is encountered with a top line XRST command, this panel isreturned for ease of correction and reentry.

To exit:







FUNCTIONLeave blank to list a job. Otherwise, specify the name of some other panelto which you want to transfer or position the cursor to the top line and entera top line command. For other options, see “PF Keys” on page 504.

JOB TO BE RESTARTEDJob name or Unicenter CA-7 job number of the desired job. Required, thereis no default.

QM.4-X CPU Job In Restart Status

After entering the desired values on the QM.4 panel, press Enter. A panel isreturned with which restart options can be taken.

If Unicenter CA-11 is available to assist with a restart, the panel returned issimilar to this.

Unicenter CA-11 Installed

� � ------------ CA-7 QUEUE MAINTENANCE - CPU JOB IN RESTART STATUS ------------ JOB: D463XX�3 CODE: JCLERR LAST-STEP: MCNT: ��1 CA-7#: ��2 JES#: 17349 NODE-NAME: LOCAL

REASON:

-- -- RESUBMIT FOR PRODUCTION

-- -- FORCE COMPLETE

-- -- CA-11 RESTART/RERUN PSEUDO: START: END:

CC: BYPGDG: USAGE: LRTCD: = �CMT STATUS: CMT SHOWS JOB IS SET FOR RESTART

-- -- SET PARM DATA FOR RMS AND RESUBMIT PARM:

-- -- DO NOT INSERT RMS PROC BUT RESUBMIT

PROGRAM: QM5� MSG-INDX: �� -- QM.4-X -- YY.DDD / HH:MM:SS MESSAGE: 'X' THE DESIRED FUNCTION OR ENTER A COMMAND ON THE TOP LINE

� �

528 Commands Guide


Request the proper functions by placing an X in the space provided andpressing Enter.


REASONAlways appears on the panel. This is a required entry field ifREASON=YES is specified in the Unicenter CA-7 initialization fileRESTART statement or if Unicenter CA-11 requires a reason for restarts.For more information about the initialization file, see the SystemsProgrammer Guide. If the Unicenter CA-11 reason-for-rerun table isavailable, an attempt is made to expand any code of up to four charactersthat is entered. If the CMT member is found, the reason entered is movedto the CMT.

RESUBMIT FOR PRODUCTIONAlways appears on the panel. Used by itself to simply resubmit the job withno changes. When Unicenter CA-11 is installed and the job is found on theCMT data set, this function clears restart fields in the CMT.

FORCE COMPLETEAlways appears on the panel. If used, the job is processed as if a goodend-of-job had occurred. This causes triggering and requirement posting forother dependent jobs. Job triggering and posting occur. If Unicenter CA-11is installed and the CMT member is found, this also clears the CMT flags.

CA-11 RESTART/RERUNIf the CMT member is found, information specified in these fields update theCMT member. If the RMS step has not executed, RESUBMIT should beused instead of RESTART.

CMT STATUSUsed to provide a message describing the job status as found in the CMT.Also used to report that the Unicenter CA-11 interface is not available andwhy.

SET PARM DATA FOR RMS AND RESUBMITCan be used only if Unicenter CA-7 inserted the RMS procedure. Used todefine new Unicenter CA-11 PARM data for the rerun. No edits areperformed on this field. The Unicenter CA-11 CMT is not updated.

DO NOT INSERT RMS PROC BUT RESUBMITCan be used only if Unicenter CA-7 inserted the RMS procedure. Causesresubmittal without the RMS procedure being inserted. Overrides DB.1panel option. The Unicenter CA-11 CMT is not updated. This option shouldonly be used for the first resubmission of a job. RESUBMIT FORPRODUCTION should be used for any subsequent resubmissions.



Unicenter CA-11 Not Installed: If Unicenter CA-11 is not installed, thefollowing is an example of the panel.

� � ------------ CA-7 QUEUE MAINTENANCE - CPU JOB IN RESTART STATUS ------------ JOB: D463XX�3 CODE: JCLERR LAST-STEP: MCNT: ��1 CA-7#: ��2 JES#: 17349 NODE-NAME: LOCAL

REASON:

-- -- RESUBMIT FOR PRODUCTION

-- -- FORCE COMPLETE

PROGRAM: QM5� MSG-INDX: �� -- QM.4-X -- YY.DDD / HH:MM:SS MESSAGE: 'X' THE DESIRED FUNCTION OR ENTER A COMMAND ON THE TOP LINE

� �

With either format of the panel, information about the job is given in the twolines below the panel title line.

530 Commands Guide

QM.5 Queued JCL Panel


This panel lists queued JCL so that it can be updated. There is no equivalentbatch function.

� � ------------------- CA-7 QUEUE MAINTENANCE - QUEUED JCL -------------------- FUNCTION: (APPEND,APPENDP,CLEAR,EDIT,FE,FETCH, FETCHP,FPE,REPL,SAVE) JOB:

ACTIVE SIZE: ��

NOTE: REPL WILL RESET THE JCLOVRD REQUIREMENT

PROGRAM: SM9� MSG-INDX: �� -- QM.5 -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:




■ QJCL as a top line command.

■ E for a job on the QM.1 panel.

■ If an error is encountered with a top line QJCL command, this panel isreturned for ease of correction and reentry.

To exit:




If this panel was displayed as a result of entering an E on the QM.1 panel,return is to that panel after any updates are done.




FUNCTIONIndicates the activity to be performed. Must be one of these:

APPENDAttaches request queue JCL to the end of any existing lines in theterminal's active area.

APPENDPAttaches prior-run queue JCL to the end of any existing lines in theterminal's active area.

CLEARClears the panel input data fields and the terminal's active area.

EDITTransfers the user to the edit facility and allows text processing.

FECombination of FETCH and EDIT. If job name or job number is enteredwith the top line QJCL command, the FE function is assumed.

FETCHRetrieves request queue JCL into the terminal's active area.

FETCHPRetrieves prior-run queue JCL into the terminal's active area.

FPECombination of FETCHP and EDIT.

REPLReplaces the JCL in the request queue and turns off the JCL overriderequirement if one exists. This decrements the master requirementcount by one.

SAVESaves the JCL in the request queue and does not turn off the JCLoverride requirement if one exists.

JOBIf the user is doing a FETCH, APPEND, REPL or SAVE for JCL in therequest queue, this can be the assigned Unicenter CA-7 job number or thejob name of the job in the request queue. If the user is doing a FETCHP,FPE, or APPENDP for JCL in the prior-run queue, this must be a specificjob name in up to eight characters.

Reminder text can be fetched or replaced by using RMD#nnnn in the JOBfield, where nnnn is the Unicenter CA-7 preprocess queue job number.

ACTIVE SIZEA system generated field that displays how many lines of text exist in theactive area for the current terminal session.

532 Commands Guide

QM.6 Input Networks Prompt Panel


This panel lists input network tasks that are to be updated. There is noequivalent batch function.

� � -------------- CA-7 QUEUE MAINTENANCE - INPUT NETWORKS PROMPT -------------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

NETWORK(S) => SPECIFIC OR GENERIC (DEFAULT ALL)

SUBID(S) ===> SPECIFIC OR GENERIC (DEFAULT ALL)

JOB(S) =====> � SPECIFIC, GENERIC OR CA-7# (DEFAULT ALL)

STATION(S) => SPECIFIC, GENERIC OR � (DEFAULT IS ALL THESTATIONS ASSIGNED TO THIS TERMINAL)

2-UP ? =====> N Y = 2-UP (DEFAULT IS 1-UP)

FILL WITH ==> C = CANCEL O = LOGOUT(OPTIONAL) H = HOLD P = RESPOND TO PROMPTING

I = LOGIN R = RELEASE FROM HOLD


� �

To display, enter:




■ If an error is encountered with top line XPRE or XSPRE commands, thispanel is returned for ease of correction and reentry.

To exit:







FUNCTIONLeave blank to list entries. Otherwise, specify name of some other panel towhich you want to transfer or position the cursor to the top line and enter atop line command.

NETWORK(S)Specific or generic network name. Default is all networks.

SUBID(S)Specific or generic SUBID name. Default is all SUBIDs.

JOB(s)Specific job name, generic job name, or a specific job number. Default is alljobs.

STATION(S)Specific station name, generic station name, or * to indicate all stationnames defined to Unicenter CA-7. Default is only the station names definedto this terminal.

2-UP ?Y indicates 2-up format display is wanted. Default is N, for 1-up format.

FILL WITHSame as FILL keyword parameter for top line command. When used, thedisplay has this value already entered in the F function field for all jobs.Default is none. Allowable values are:

CCancel the task.

HPut the task in hold status.

IDo LOGIN function for this task.

ODo LOGOUT function for this task.

PRespond to a deadline prompt (RSVP).

RRelease the task from hold status.

534 Commands Guide


QM.6-X Input Networks (1-Up Display)

The following panel is displayed if a 1-up display was requested in the previouspanel. (A 2-up display is discussed in “QM.6-S Input Networks (2-Up Display)”on page 538.)

Function values can be entered in the FL. portion of the panel to assign thesame function for all records. It can also be entered in front of an individualentry to perform the function for only that entry.

Function values can be mixed on the same panel. For example, after the panelis first displayed, you can enter function values, in the field that precedes eachline on the panel, to log in to one entry, log out another, and cancel yet anotherwith a single panel command.

After a station has been logged out or canceled, it continues to be displayed forthis request. It may be necessary to reissue the command for an updateddisplay. However, no function value can be input for that entry.

� � ----------------- CA-7 QUEUE MAINTENANCE - INPUT NETWORKS ------------------ POS: FL: INITS: F --REF-- JOBNAME- NETWORK- STATION- SUBID--- DESC---- REMARKS--------------�

��2��1 D463XX�3 D4�218ED CONTROL PAY�1 WEEK1


� �


Once the QM.6 update panel has been displayed, the POS, FL, and INITSfields on the panel can be used to perform certain functions. The use of thesefields and their acceptable values are as follows:

POS:This indicates position of the panel. Available values are:

NOPNo processing - clears panel of input values.



PFPage forward.

TOPPosition to the top of the panel.

ONEDisplay in 1-up format (one record per line); return from TWO.

TWODisplay in 2-up format (two records per line).

FL:Indicates a fill character for processing the records. See the FILL parameterfor allowable options.

INITS:This performs the same function as the INITS parameter of the LOGIN andLOGOUT commands discussed elsewhere in this chapter. The initials of theoperator processing network records could be entered here.

FIndicates the function column in which updates are requested. See the FILLWITH values on the QM.6 panel for values allowed here.

REFIndicates the Unicenter CA-7 assigned number for this task.

JOBNAMEIndicates the JOB keyword value given when the network was initiated witha DMDNW command.

NETWORKIndicates the name of this network in the database.

STATIONIndicates the station at which this task is to be performed.

SUBIDIndicates the value given when the network was initiated with a DMDNWcommand.

DESCIndicates the DESC keyword value given when the network was initiatedwith a DMDNW command.

536 Commands Guide


REMARKSIndicates any of the following:

■ ALREADY ACKNOWLEDGED - can only respond to a prompt once

■ ALREADY HELD - can only 'hold' a nonheld task

■ ALREADY LOGGED IN - can only log in a task once

■ ALREADY LOGGED OUT - can only log out a task once

■ HELD - the task is now in 'hold' status

■ INVALID CODE - the F value given is unknown

■ NOT HELD - can only release a 'held' task

■ NOT IN PROCESS - can only log out an active task

■ NOT PROMPTED - can only respond if the task was prompted

■ REF# NOT FOUND - could not locate the REF number requested



Usage Notes

Request updates by entering the value you want in the F field in front of theentry you want. You can update multiple tasks if you want.

After all values have been entered, press Enter and the updates are made.REMARKS fields and MESSAGE field at the bottom indicate what action tookplace.

When finished, you can enter a command on the top line to transfer to someother function. For other options, see “PF Keys” on page 504.

QM.6-S Input Networks (2-Up Display)

If a 2-up display was requested on the QM.6 panel, a panel similar to thefollowing appears. If more than 17 tasks are listed, tasks 18-34 appear as asecond column just to the right of the one shown here.

� � ----------------- CA-7 QUEUE MAINTENANCE - INPUT NETWORKS ------------------ POS: FL: INITS: F---REF---SUBID----DESC-----EC ��2��1 PAY�1 WEEK1

PROGRAM: QM1� MSG-INDX: �� -- QM.6-S -- YY.DDD / HH:MM:SS MESSAGE:

� �

538 Commands Guide



The F, REF, SUBID, and DESC fields have the same meaning as on the 1-updisplay.

The EC field provides a 2-digit number corresponding to the REMARKS field onthe 1-up display as follows:

01INVALID CODE - the F value given is unknown

02REF# NOT FOUND - could not locate the REF number requested

03ALREADY LOGGED IN - can only log in a task once

05NOT IN PROCESS - can only log out an active task

06NOT HELD - can only release a 'held' task

07NOT PROMPTED - can only respond if the task was prompted

08HELD - the task is now in 'hold' status

09ALREADY LOGGED OUT - can only log out a task once

10ALREADY HELD - can only 'hold' a non-held task

11ALREADY ACKNOWLEDGED - can only respond to a prompt once

Usage Notes


After all values have been entered, press Enter and the updates are made. ECfields and MESSAGE field at the bottom indicate what action took place.


QM.7 Output Networks Prompt Panel


This panel lists output network tasks that are to be updated. There is noequivalent batch function.

� � ------------- CA-7 QUEUE MAINTENANCE - OUTPUT NETWORKS PROMPT -------------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

NETWORK(S) => SPECIFIC OR GENERIC (DEFAULT ALL)

SUBID(S) ===> SPECIFIC OR GENERIC (DEFAULT ALL)

JOB(S) =====> � SPECIFIC, GENERIC OR CA-7# (DEFAULT ALL)

STATION(S) => SPECIFIC, GENERIC OR � (DEFAULT IS ALL THESTATIONS ASSIGNED TO THIS TERMINAL)

2-UP ? =====> N Y = 2-UP (DEFAULT IS 1-UP)

FILL WITH ==> C = CANCEL O = LOGOUT(OPTIONAL) H = HOLD P = RESPOND TO PROMPTING

I = LOGIN R = RELEASE FROM HOLDF = FORCE LOGIN


� �

To display, enter:




■ If an error is encountered with top line XPOST or XSPOST commands, thispanel is returned for ease of correction and reentry.

To exit:




540 Commands Guide



FUNCTIONLeave blank to list entries. Otherwise, specify name of some other panel towhich you want to transfer or position the cursor to the top line and enter atop line command.

NETWORK(S)Specific or generic network name. Default is all networks.

SUBID(S)Specific or generic SUBID name. Default is all SUBIDs.

JOB(s)Specific job name, generic job name, or a specific job number. Default is alljobs.

STATION(S)Specific station name, generic station name, or * to indicate all stationnames defined to Unicenter CA-7. Default is only the station names definedto this terminal.

2-UP ?Y indicates 2-up format display is wanted. Default is N for 1-up format.

FILL WITHSame as FILL keyword parameter for top line command. When used, thedisplay has this value already entered in the F function field for all jobs.Default is none. Allowable values are:

CCancel the task.

HPut the task in hold status.

IDo LOGIN function for this task.

FDo LOGIN function even if the connected job is not complete.

ODo LOGOUT function for this task.

PRespond to a deadline prompt (RSVP).

RRelease the task from hold status.



QM.7-X Output Networks (1-Up Display)

The following panel is displayed if a 1-up display was requested on QM.7panel. (A 2-up display is discussed on “QM.7-S Output Networks (2-UpDisplay)” on page 544.)

Function values can be mixed on the same panel. For example, after the panelis first displayed; you can enter function values in the blank field that precedeseach line on the panel, to log in to one entry, log out another, and cancel yetanother with a single panel command.

After a station has been logged out or canceled, it continues to be displayeduntil a new display is requested. However, no function value can be input forthat entry.

� � ----------------- CA-7 QUEUE MAINTENANCE - OUTPUT NETWORKS ----------------- POS: FL: INITS: F --REF-- JOBNAME- NETWORK- STATION- SUBID--- DESC---- REMARKS--------------� ��3�11


� �


Once the QM.7 update panel has been displayed, the POS, FL, and INITSfields on the panel can be used to perform certain functions. The use of thesefields and their acceptable values are as follows:

POS:This indicates position of the panel. Allowable values are:

NOPNo processing - clears panel of input values.

PFPage forward.

542 Commands Guide


TOPPosition to the top of the panel.

ONEDisplay in 1-up format (one record per line); return from TWO.

TWODisplay in 2-up format (two records per line).

FL:Indicates a fill character for processing the records. See the previousdiscussion of the FILL parameter for allowable options.

INITS:This performs the same function as the INITS parameter of the LOGIN andLOGOUT commands discussed in “LOGIN/LOGOUT” on page 368. Youcan enter the initials for the operator processing network records here.

FIndicates the function column in which updates are requested. See the FILLWITH values on the QM.7 panel for values allowed here.

REFIndicates the Unicenter CA-7 assigned number for this task.

JOBNAMEIndicates either:

■ JOB keyword value given when the network was initiated with aDMDNW command.

■ Name of the CPU job predecessor if the network was initiated as aresult of the predecessor job being initiated.

NETWORKIndicates the name of this network in the database.

STATIONIndicates the station at which this task is to be performed.

SUBIDIndicates either:

■ SUBID keyword value given when the network was initiated with aDMDNW command.

■ SUBID value for the SUB-ID field on the DB.3.4 panel.

DESCIndicates the DESC keyword value given when the network was initiatedwith a DMDNW command.

REMARKSIndicates any of the following:

■ ALREADY ACKNOWLEDGED - can only respond to a prompt once

■ ALREADY HELD - can only 'hold' a nonheld task



■ ALREADY LOGGED IN - can only log in a task once

■ ALREADY LOGGED OUT - can only log out a task once

■ HELD - the task is now in 'hold' status

■ INVALID CODE - the F value given is unknown

■ JOB NOT COMPLETE - must specify FORCE to log in to an outputtask if the predecessor job has not completed

■ NOT HELD - can only release a 'held' task

■ NOT IN PROCESS - can only log out an active task

■ NOT PROMPTED - can only respond if the task was prompted

■ REF# NOT FOUND - could not locate the REF number requested

Usage Notes


After all values have been entered, press Enter and the updates are made.REMARKS fields and MESSAGE field at the bottom indicate what action tookplace.

QM.7-S Output Networks (2-Up Display)

If a 2-up display was requested, a panel similar to the following appears. Ifmore than 17 tasks are listed, tasks 18-34 appear as a second column just tothe right of the one shown here.

� � ----------------- CA-7 QUEUE MAINTENANCE - OUTPUT NETWORKS ----------------- POS: FL: INITS: F---REF---SUBID----DESC-----EC ��3�11

PROGRAM: QM1� MSG-INDX: �� -- QM.7-S -- YY.DDD / HH:MM:SS MESSAGE:

� �

544 Commands Guide



The F, REF, SUBID, and DESC fields have the same meaning as on the 1-updisplay in “QM.7-X Output Networks (1-Up Display)” on page 542.

The EC field provides a 2-digit number corresponding to the REMARKS field onthe 1-up display as follows:

01INVALID CODE - the F value given is unknown

02REF# NOT FOUND - could not locate the REF number requested

03ALREADY LOGGED IN - can only log in a task once

05NOT IN PROCESS - can only log out an active task

06NOT HELD - can only release a held task

07NOT PROMPTED - can only respond if the task was prompted

08HELD - the task is now in hold status

09ALREADY LOGGED OUT - can only log out a task once

10ALREADY HELD - can only hold a nonheld task

11ALREADY ACKNOWLEDGED - can only respond to a prompt once

Usage Notes


After all values have been entered, press Enter and the updates are made. ECfields and MESSAGE field at the bottom indicate what action took place.


RELEASE

RELEASE

The RELEASE top line command indicates that normal scheduling activities cannow be resumed for jobs or queues on HOLD. See “HOLD” on page 263. Thisfunction is available for CPU jobs on the QM.1, QM.2, and QM.3 panels. It isavailable for workstation networks on the QM.6 and QM.7 panels.


RELEASE

��──RELEASE──,─ ──┬ ┬──JOB= ──┬ ┬─jobname─── ────────────────────────�� │ │├ ┤─jobnumber─ │ │└ ┘─refnumber─

└ ┘──Q= ──┬ ┬─REQ─ ──────── └ ┘─RDY─

JOBIndicates the individual job or workstation network to be released. JOB isrequired to release a specific job. It must be omitted if Q is specified. Thevalue for a CPU job can be entered as the specific job name or theUnicenter CA-7 job number.

Required: Yes, unless Q is used





refnumberThe value for a workstation network task must be entered as theUnicenter CA-7 assigned reference number in the format nnnnrrswhere:


rrRelative sequence of the network in relation to other networksassociated with the job. For input workstation networks, the value is00.

sRelative position of the station within the network. The first stationwould be position 1.

546 Commands Guide

RELEASE

QIndicates the contents of an entire queue are to be released. Q must beomitted if JOB is specified.


REQRequest queue hold status.

RDYReady queue hold status.

Usage Notes

A request to release an individual job takes precedence over a hold placed onan entire queue (that is, an entire queue can be held and then jobs releasedindividually to control the work flow manually).

A job can be in hold status due to a previous request by a HOLD command orthe hold can be permanently defined in the database. In either case, theRELEASE can be used.

A release request by job name causes all jobs, workstation networks, or bothwith that name to be released. There can be multiple jobs with the same name.

ExamplesRELEASE,JOB=CA7JOB9

RELEASE,JOB=163

RELEASE,Q=REQ

RELEASE,JOB=��78�12


REMIND

REMIND

The REMIND top line command schedules free-form reminder messages,generated separately through the edit facility, to workstations at apredetermined time. For more information, see “LRMD” on page 459. Afree-form message can be defined to communicate anything to a workstation.The workstation operator is prompted, repeatedly if necessary, to review thedefined text.


REMIND

��──REMIND─ ──,STATION=station ──,TIME=hhmm ──┬ ┬───────────── ───────�└ ┘──,DATE=yyddd

�─ ──┬ ┬────────────── ────────────────────────────────────────────��└ ┘──,SUBID=subid

STATIONSpecifies the logical terminal name (station) to which reminder text in theactive area is to be directed.


Required: Yes

TIMEIndicates the time-of-day at which reminder text in the active area is to besent to the STATION.

Required: Yes

hhIndicates the hour (0 through 23).

mmIndicates the minutes (0 through 59).

DATESpecifies the Julian date when reminder text in the active area is to be sentto the STATION. If DATE is not specified, the current date is used. If thetime-of-day (TIME value) is past and no date is specified, the next day isused.

Required: No

yyIndicates the year.

dddIndicates the Julian day.

548 Commands Guide

REMIND

SUBIDSpecifies a SUB-ID to further qualify the STATION.


Required: No

Usage Notes

You must place the reminder message to be sent in the Unicenter CA-7 activearea before entering the REMIND command. You can accomplish this throughthe EDIT command using the INSERT subcommand. After entering the text, theSAVE subcommand places the text in the active area. Then you can enter theREMIND top line command. If you enter a REMIND command with a date andtime that has already passed, the reminder message is issued immediately.Also, you can review the message with the LRMD command.

The reminder remains in the Unicenter CA-7 preprocess queue, with a jobname in the format RMD#nnnn, until a LOGOUT or CANCEL is entered. Whenthe reminder is issued at the specified time-of-day (or immediately as justdescribed), it is reissued for each reprompt cycle until a LOGOUT or CANCELis done.

ExamplesREMIND,STATION=INPUT,TIME=�8��

REMIND,STATION=MAIL,TIME=163�,DATE=�5287


RENAME

RENAME

The RENAME command renames a DASD data set. This function is availableon the UT Menu panel as FUNCTION value 3 or on any other menu orformatted panel as FUNCTION value UT.3. This command neither renamesPDS members nor Unicenter CA-7 database data sets.


RENAME

��──RENAME─ ──,DSN=dsname ──,NEWNAME=newname ──┬ ┬───────────── ─────��└ ┘──,VOL=volume

DSNIndicates the old fully qualified name of the data set.


Required: Yes

NEWNAMEIndicates the new fully qualified name to be assigned to the data set.


Required: Yes

VOLIndicates the volume on which the data set resides. The volume on whichthe data set resides must be available to Unicenter CA-7.


Required: No, if data set is cataloged

ExamplesRENAME,DSN=USER.FILE1,NEWNAME=USER.FILEX,VOL=VOLM�1

RENAME,DSN=USER.FILE1,NEWNAME=USER.FILE2

550 Commands Guide

REQUEUE

REQUEUE

The REQUEUE top line command moves jobs from the ready or active queuesback to the request queue. This allows the use of the Unicenter CA-7 jobrestart facilities after certain JCL or CPU failures, or job cancellation out of aCPU through the OS console. This function is available as the Q option in“QM.1 CPU Jobs Status Prompt Panel” on page 505.


REQUEUE

��──REQUEUE─ ──┬ ┬──────────── ──┬ ┬────────────────────── ───────────�└ ┘──,CPU=smfid └ ┘──,JOB= ──┬ ┬─jobname───

└ ┘─jobnumber─

�─ ──┬ ┬──────────────────── ──┬ ┬────────────── ──┬ ┬─────────── ─────��└ ┘──,MAINID= ──┬ ┬─ALL── └ ┘──,Q= ──┬ ┬─ACT─ └ ┘──,TYPE=JCL

├ ┤──SYn ─ └ ┘─RDY─└ ┘──/SYn

CPUUsed with JOB to specify the CPU ID of active queue jobs that are to berequeued. The value identifies the CPU and corresponds to the CPU fielddisplayed on the LQ command (the SMF identifier). CPU cannot be usedwith MAINID.


Required: No

JOBSpecifies the job to be moved back to the request queue, given a restartrequirement, and flagged as having been requeued. If JOB is used alone,both the active and ready queues are searched for the specified job. If JOBis used with Q, the search is restricted to the indicated queue.

Required: No






REQUEUE

MAINIDUsed with JOB to indicate that only those jobs in the ready queue with thisMAINID are to be requeued. Value must be specified as a single MAINIDname. MAINID cannot be used with CPU.


Required: No

ALLIndicates all MAINIDs are to be considered.

SYnWhere n indicates a CPU assigned number as defined in theinitialization file CPU statement. For more information about theinitialization file, see the Systems Programmer Guide. The value of ncan range from 1 to 7.

/SYnWhere n indicates a CPU assigned number. The / indicates "not thisMAINID." The value of n can range from 1 to 7.

QUsed with JOB to indicate in which queue the job search is to occur.

Required: No

ACTIndicates the active queue.

RDYIndicates the ready queue.

TYPEIndicates the job should be flagged, once it returns to the request queuewith a status of JCLERR instead of REQUE. If not coded, the status reflectsREQUE.

552 Commands Guide

REQUEUE

Usage Notes

Use of the REQUEUE command causes the jobs to be moved back to therequest queue, given a restart requirement, and flagged as having beenrequeued. Subsequent inquiries show a job status of R-REQUE. Then you canuse the Unicenter CA-7 restart facilities, QM.4, XRST, or RESTART, toresubmit the job for processing.

Certain VRM resources acquired by the job can be freed when the REQUEUEcommand is issued. If the resource is defined on the RM.1 panel as SHR, EXC,or RCT and if it is to be freed at abnormal termination (A or F), the resource isfreed when the job is requeued.

If JOB is not specified, Unicenter CA-7 requeues all jobs that meet the Q,MAINID, or CPU criteria.

In the event of a system failure that strands jobs in the Unicenter CA-7 activequeue, the requeue function must be used to place the jobs in restart status.

The Q option of the QM.1 panel is an alternative to the REQUEUE command.

ExamplesREQUEUE,JOB=1234

REQUEUE,JOB=9999,Q=RDY

REQUEUE,JOB=9999,CPU=CPU1

REQUEUE,JOB=9999,MAINID=SY2

REQUEUE,CPU=CPU1


RESANL

RESANL

The RESANL command causes an analysis of all specified jobs in the specifiedsystems against the correct number of tape drives needed based on job profilesin the Unicenter CA-7 database.


RESANL

��──RESANL─ ──┬ ┬───────────────────── ─────────────────────────────� │ │┌ ┐─�────────

└ ┘──,JOB= ──┼ ┼─jobname── └ ┘─jobname�─

�─ ──┬ ┬──────────────────────── ──┬ ┬────────── ─────────────────────�│ │┌ ┐─�─────────── └ ┘──,TYPE=DS└ ┘──,SYS= ──┼ ┼─systemname──

└ ┘─systemname�─

�─ ──┬ ┬─────────────────── ───────────────────────────────────────�� │ │┌ ┐─NO──

└ ┘──,UPDATE= ──┴ ┴─YES─

JOBSpecifies the job names for which an analysis is to be performed.

Default: *

Limits 1 to 8 alphanumeric characters

Required: No

*Causes all jobs to be analyzed.

jobnameDefines a single job name.


554 Commands Guide

RESANL

SYSSpecifies the system names for which an analysis is to be performed.

Limits 1 to 8 alphanumeric characters

Default: *

Required: No

*Causes all systems to be analyzed.

systemnameDefines a system name.

systemname*Defines a generic system name terminated with an asterisk.

TYPESpecifies data set information. When Unicenter CA-7 is analyzing a dataset, an attempt is made to examine the data set's catalog entry. If a dataset is not cataloged, Unicenter CA-7 uses the information about the dataset that is stored in the job data set. When TYPE=DS is specified,Unicenter CA-7 uses the dataset data set information instead of the jobdata set information when a catalog entry is not available.

Required: No

UPDATESpecifies whether those jobs being analyzed should have their WLB tapedrive requirements updated to match their job profiles. The profiles agreewith the last LOAD function performed.

Default: NO

Required: No

NOIndicates no updates are to be made to the database.

YESIndicates updates are to be made to the database in addition toproviding a list.


RESCHNG

RESCHNG

The RESCHNG command in a Unicenter CA-7 trailer step frees tape drives thatare no longer needed. When workload balancing is scheduling jobs, thehigh-water mark for tape drives is reserved until job completion, unless thiscommand is used. Using this command, the trailer step can be inserted in thejob anytime after the maximum number of tape drives is no longer needed.


RESCHNG

��──RESCHNG─ ──┬ ┬────────────── ──┬ ┬────────── ──┬ ┬────────── ──────��└ ┘──,JOB=jobname └ ┘──,TP1=nnn └ ┘──,TP2=nnn

JOBIndicates the name of the job to which the change applies. The job must bein the active queue. JOB is required unless the command is entered fromSASSTRLR (trailer step).


Required: Yes, unless command is from SASSTRLR

TP1Indicates the maximum TAPE1 requirements for the remainder of the job.


Required: No

TP2Indicates the maximum TAPE2 requirements for the remainder of the job.


Required: No

Usage Notes

You can also use the #RES statement to override established resourcerequirement values for a job. For information about #RES, see the chapter"JCL Management" in the Database Maintenance Guide.

556 Commands Guide

RESCHNG

ExamplesRESCHNG,TP1=1�

Changes number of TYPE1 tape drives in use to 10. Frees all but 10 tapedrives (used by the previous steps) for scheduling other jobs.

RESCHNG,TP1=��,TP2=��

Changes number of TYPE1 and TYPE2 tape drives in use to 0. Frees all tapedrives (used by the previous steps) for scheduling other jobs.


RESOLV

RESOLV

The RESOLV top line command creates or modifies processing schedules forjobs or workstation networks that are to be scheduled on a date/time basis.Work that is scheduled by a trigger or on-request work that is DEMANDed orRUN has no direct relationship to a base calendar and therefore does notrequire the use of this function.

You can also request the RESOLV command from the DB.2.1 and DB.2.2panels. Those panels are used to define schedule criteria and the name of thedefault base calendar to which the schedules apply. The RESOLV command isthen used to perform a resolution process using the specified schedule criteriaand the base calendars. Processing schedules are thus completed, defining thespecific dates on which the processing is to be performed. Scheduling beginsautomatically when the first date in the RESOLVed schedule arrives. (Theseschedules can be further modified using the DB.2.7 function. Other temporaryor onetime changes can also be accomplished through other commands suchas NXTCYC and so forth.)

The RESOLV command selects the schedule members to be processed beforeactual schedule resolution activity begins. The JOB and NW parameters areused to identify the job and network candidates for resolution of schedules. IfJOB and NW are omitted, all jobs and input networks are consideredcandidates. Two criteria are used for selecting the schedules to be resolved forthose candidates identified:

■ The SCAL value specified in the RESOLV command is matched with thebase calendar references in the schedule data.

■ The OLDYR value specified in the RESOLV command is matched with thebase calendar year in the schedule data.

Schedules can be RESOLVed for January through December of the currentyear, or for July of the current year through June of the next year. See theYEAR parameter in the syntax descriptions.

Before Unicenter CA-7 can automatically schedule a job, it needs to know theexact dates the job is to be processed. The RESOLV command takes thespecified scheduling information and compares it to the processing daysdefined in the base calendars to calculate the exact processing days. Whendoing a schedule resolution, Unicenter CA-7 looks at the scheduling informationin the following sequence:

1. All positive schedule values for DAILY, WEEKLY, MONTHLY, ANNUAL,and SYMETRIC.

2. All negative schedule values for WEEKLY, MONTHLY, and ANNUAL.

3. ROLL option. (process based on calendar definition)

4. INDEX field. (process based on calendar definition)

558 Commands Guide

RESOLV


RESOLV

��──RESOLV─ ──┬ ┬──────────────────────────── ──────────────────────�└ ┘──, ──┬ ┬──JOB= ──┬ ┬─�──────── ─

│ │├ ┤─jobname── │ │└ ┘─jobname�─

└ ┘──NW= ──┬ ┬──NW.network └ ┘─NW.────────

�─ ──┬ ┬──────────────────── ──┬ ┬───────────────── ──────────────────�└ ┘──,DUPDATE= ──┬ ┬─YES─ └ ┘──,OLDYR= ──┬ ┬─�──

└ ┘─NO── └ ┘─yy─

�─ ──┬ ┬────────────────── ──┬ ┬──────────────── ─────────────────────�│ │┌ ┐─NO── └ ┘──,SCAL= ──┬ ┬─�──└ ┘──,PRINT= ──┴ ┴─YES─ └ ┘─xx─

�─ ──┬ ┬───────────────── ──┬ ┬────────── ───────────────────────────��│ │┌ ┐─YES─ └ ┘──,YEAR=yy└ ┘──,TEST= ──┴ ┴─NO──

JOBLimits selection for resolution to the jobs specified. When JOB is specified,NW must be omitted. If both are omitted, all job and input networkschedules are candidates for resolution. Value can be either a specific jobname or a generic name that identifies multiple jobs beginning with thespecified characters. An asterisk (*) must be used to delimit the generic jobname. It can appear in any of the 8 positions but must immediately followthe last significant character of the job name requested. For example, AB*causes all jobs beginning with AB to be selected for resolution. JOB=*causes all job schedules to be selected for resolution.

Required: No (cannot be used with NW)

*Select all job schedules for resolution.

jobnameSelect a specific job name.

jobname*Select a generic job name (with * used to delimit).

NWLimits selection for resolution to the input networks specified. If used, JOBmust be omitted. If both are omitted, all job and input network schedulesare candidates for selection. When used, value must be one of thefollowing:

Required: No (cannot be used with JOB)

NW.networkIdentifies a specific network name to be selected.


RESOLV

NW.Indicates all input networks are to be considered for resolution. Thisvalue must be terminated with a period.

DUPDATEIndicates whether specific duplicate day messages (SRC1-137) should beproduced each time a given day is scheduled by two or more schedule IDsfor the same job/network.

Required: No. The default is NO unless the extended resolve messageoption has been set in the user profile (see “/PROF” on page 104).

OLDYRSpecifies the year currently defined in the schedule member data (the valuesupplied by YEAR in the previous resolution that updated the schedulemember). Only those candidate schedule members whose year datamatches the OLDYR value are selected for resolution. If used, value mustbe one of the following:

Default: If omitted, only those schedule members that have not previouslybeen resolved or whose schedules have expired are selected.

Required: No

yyIndicates a specific year.

*Indicates all years and all schedules.

PRINTSpecifies whether a month-by-month schedule day calendar is to bedisplayed after resolution of the defined member is complete. If used, valuemust be either PRINT=YES or PRINT=NO.

Default: NO

Required: No

SCALValue is the xx portion of the base calendar name, SCALyyxx. The SCALvalue must also match the base calendar identifier (SCAL) specified in anySCHID of the schedule definition for the individual jobs or networks. Thisvalue is used during the selection process of resolution to determine whichschedule members are to be resolved.

Required: No (unless JOB and NW are omitted)

*Indicates all SCALs.

xxIndicates a specific SCAL.

560 Commands Guide

RESOLV

TESTIndicates whether schedule members are to be updated as a result of theresolution process. TEST=YES and TEST=NO are the only allowablevalues.

Default: YES

Required: No

YESNormal resolution occurs and all messages are printed, but no updatingof the database occurs. This option can be used at year-end orwhenever a base calendar is changed to see the results of theresolution activity, without actually changing the schedule mask oraffecting the current schedule process.

NONormal resolution occurs and all messages are printed, and updating ofthe database occurs.

YEARIdentifies the year of the base calendars against which the schedule isresolved. Value is the number that is specified by the yy portion of the basecalendar name, SCALyyxx. When a schedule is successfully updated, theYEAR value becomes part of the schedule data (see OLDYR). If the YEARparameter is not specified, the current year is assumed to be the year fromthe system internal date and time.

Also, if YEAR is not coded on the RESOLV, a check is made to see if theRESOLV is made within the period January 1 through June 30 asdetermined from system date and time. If so, the schedule is resolvedagainst January through December of the current year. If a RESOLV isdone within the period July 1 through December 31, the schedule isresolved against July 1 through December 31 of the current year andJanuary 1 through June 30 of the next year. This requires the existence ofbase calendars for both calendar years involved. If a required basecalendar is not available, an error message is issued, and the schedulemember is not resolved.

YEAR is optional. If YEAR is specified, the resolution is made againstJanuary through December of the year specified.

Default: Current year

Limits: 2 numeric characters

Required: No

Note: If year= is specified, only the current year should be used.


RESOLV

Usage Notes

Always check the RESOLV output for message SRC1-117 ID MULTIPLESCHEDULES AT LEAST ONE DAY. This message indicates two or moreschedule IDs are scheduled to process on the same day. This message canindicate a scheduling error was made. You need to determine if the job shouldprocess multiple times on the same day. If it should, this is an informationalmessage. If not, the schedule should be corrected.

When the RESOLV command is entered in the FUNCTION field, a resolution isperformed for a 12-month period. The current year is divided into 6-monthintervals. This means if a RESOLV is entered between January 1 and June 30,the resolution looks at the period January 1 through December 31. If aRESOLV is entered between July 1 and December 31, the resolution attemptsto look at July 1 through June 30 of the next year. If next year's base calendaris not defined, you get error message SRC2-02 BASE CALENDAR SCALyyxxNOT FOUND. At this time, add subparameter YEAR=yy to the top line RESOLVcommand already displayed, where yy is the current year.

If JOB=* or NW=NW. is specified, all job or input network schedule definitionsare resolved based on the other RESOLV parameters. This command can runfor a long time and generate a large amount of output. The long-runningRESOLV commands should be issued using the batch terminal interface.

Examples

Example 1

RESOLV,YEAR=�5,SCAL=�1,TEST=NO,PRINT=YES

Causes all schedule members that reference base calendar SCAL0501 to beselected. TEST=NO indicates the schedule members are actually updated. Aprintout of the schedule day calendar is also requested.

Example 2

RESOLV,YEAR=�5,SCAL=PR,NW=NW.INNET1,PRINT=YES,OLDYR=�4

Causes selection of the schedule member for input network INNET1 if 2004 isthe year currently defined in the schedule member. The schedule selected isresolved for 2005 (SCAL05PR) and the resulting schedule day calendar isprinted. Due to the absence of TEST=NO, the TEST=YES default takes effect,and the schedule member is not updated in the database.

562 Commands Guide

RESOLV

Example 3

RESOLV,YEAR=�5,SCAL=AC,OLDYR=�,TEST=NO

Causes all schedule members that reference base calendar SCAL05AC to beselected for resolution. Previous resolution year data is not considered(OLDYR=*). The schedule members are updated but calendars are not printed.

Example 4

RESOLV,SCAL=�2

Causes all schedule members that reference base calendar 02, and that havenever been previously resolved, to be selected. Resolution would be for thecurrent calendar year unless the command is issued from July 1 throughDecember 31. It would then use the last six months of the current calendar yearand the first six months of the following year to cover a 12-month period. Allother RESOLV function parameters assume default values in this example.

Example 5

RESOLV,JOB=�,OLDYR=�,TEST=NO

Causes all job schedules to be resolved for the current 12-month period. Theschedule members are updated with the results of this RESOLV command. Allcalendars referenced by job schedules are used to process this RESOLV.


RESTART

RESTART

The RESTART top line command restarts a job awaiting restart in the requestqueue. This function is available as the F option on “QM.1 CPU Jobs StatusPrompt Panel” on page 505. You can also use “QM.4 CPU Job In RestartStatus Prompt Panel” on page 527 to accomplish a job restart. If UnicenterCA-11 is used, the CMT is updated with the appropriate restart data. For morediscussion related to Unicenter CA-11, see the Interfaces Guide.

If Unicenter CA-11 is not installed, the starting and ending steps have nosignificance, nor does USAGE, PROCESS, CONDCD, or SUP11STP.


RESTART

��──RESTART─ ──,JOB= ──┬ ┬─jobname─── ──┬ ┬─────────────────── ────────� └ ┘─jobnumber─ │ │┌ ┐─NO──

└ ┘──,BYPGDG= ──┼ ┼─YES─ ├ ┤─VER─ └ ┘─CAT─

�─ ──┬ ┬────────────── ──┬ ┬────────────────────── ──┬ ┬─────────── ────�└ ┘──,CONDCD=nnnn │ │┌ ┐─NO── └ ┘──,LCC=nnnn

└ ┘──,FORCECOMP= ──┴ ┴─YES─

�─ ──┬ ┬──────────────── ──┬ ┬───────────────── ──────────────────────�└ ┘──,LSTP=stepname └ ┘──,LPSTP=procname

�─ ──┬ ┬──────────────────── ──┬ ┬─────────────────── ────────────────�└ ┘──,PROCSTRT=procname └ ┘──,PROCEND=procname

�─ ──┬ ┬─────────────── ──┬ ┬────────────── ──┬ ┬────────────────── ────�└ ┘──,PROCESS=code └ ┘──,REASON=text └ ┘──,STPEND=stepname

�─ ──┬ ┬───────────────────────── ──┬ ┬───────────────────── ─────────�└ ┘──,STPSTRT= ──┬ ┬─stepname─ │ │┌ ┐─NO──

├ ┤─�RERUN�── └ ┘──,SUP11STP= ──┴ ┴─YES─ ├ ┤─�CMT�──── └ ┘─�RESUBP�─

�─ ──┬ ┬───────────── ─────────────────────────────────────────────��└ ┘──,USAGE=code

JOBIndicates the unique Unicenter CA-7 job name or job number of the job tobe restarted. The job must be in the request queue.

Required: Yes



564 Commands Guide

RESTART



BYPGDGIndicates whether Unicenter CA-11 should bypass GDG logic on arestart/rerun. Value can be NO, YES, VER, or CAT.

Default: Unicenter CA-11 default value

Required: No

CONDCDIndicates an optional Unicenter CA-11 condition code to be set by theUnicenter CA-11 step when the rerun is executed. This option is honoredonly if Unicenter CA-11 is in use and Unicenter CA-7 is inserting the RMSstep. See the INSERT-RMS field on the DB.1 panel.


Required: No

FORCECOMPIndicates if the job is to be flagged as normally completed. IfFORCECOMP=YES, the job's previous abnormal status is ignored, andnormal job completion processing is performed instead of a restart. Valuecan be NO or YES.

Default: NO

Required: No

LCCIndicates an optional condition code value that replaces the last conditioncode value for the step referenced by the LSTP and, optionally, LPSTPkeywords. This option is honored only if Unicenter CA-11 is in use.

Default: 0


Required: No

LSTPIndicates an optional step name that has its last condition code value resetin the Unicenter CA-11 CMT. LSTP and LCC must be coded if LPSTP isspecified. LSTP requires that a STPSTRT value be specified and that theLSTP step name occurs in the job's JCL prior to the STPSTRT step name.This option is honored only if Unicenter CA-11 is in use.


Required: No


RESTART

LPSTPIndicates an optional step name referencing a procedure that has its lastcondition code value reset in the Unicenter CA-11 CMT. If LPSTP is used,LSTP and LCC must also be coded. This option is honored only ifUnicenter CA-11 is in use.


Required: No

PROCSTRTIndicates an optional step name referencing a procedure where processingis to start. If PROCESS=R and PROCSTRT are used, STPSTRT must alsobe coded. This option is honored only if Unicenter CA-11 is in use.


Required: No

PROCENDIndicates an optional step name referencing a procedure where processingis to end. If PROCESS=R and PROCEND are used, STPEND must becoded. This option is honored only if Unicenter CA-11 is in use.


Required: No

PROCESSIndicates an optional Unicenter CA-11 processing function code characterto be used in the restart/rerun. This option is honored only if UnicenterCA-11 is in use and Unicenter CA-7 is inserting the RMS step. See theINSERT-RMS field on the DB.1 panel. Value can be F, P, S, N, O or R.

Default: P

Limits: 1 alpha character

Required: No

REASONSpecifies a reason for the restart. If the Unicenter CA-11 Reason-for-Rerunmodule is available, a code of up to four characters can be input and it isexpanded. Any reason input or expanded is copied to the run log. This fieldis optional unless Unicenter CA-11 requires a reason or REASON=YESwas specified in the RESTART statement in the initialization file. For moreinformation about the initialization file, see the Systems Programmer Guide.


Required: No

566 Commands Guide

RESTART

STPENDIndicates an optional step name or number at which processing is to end. Ifnot specified, the last step of the job is assumed to be the ending step.STPEND must be coded if PROCEND is specified. This option is honoredonly if Unicenter CA-11 is in use.


Required: No

STPSTRTIndicates an optional step name or number at which processing is to start. IfSTPSTRT is not coded, the first step of the job is assigned to be thestarting step. STPSTRT must be coded if PROCSTRT is specified. Thisoption is honored only if Unicenter CA-11 is in use.

Required: No

stepnameSpecifies the step name or number at which processing is to start.

*CMT*Indicates the job is to restart with the step values currently on the CMTrecord.

*RERUN*Indicates the total job is to be rerun. If there are no restartable steps,*RERUN* must be specified.

*RESUBP*Indicates the job's CMT record is set to production, and then the job issubmitted.

SUP11STPIndicates if insertion of the Unicenter CA-11 RMS step is to be suppressed.If the job is resubmitted with SUP11STP=YES, the Unicenter CA-11 step isnot inserted. Only valid if Unicenter CA-7 is inserting the Unicenter CA-11step. See the INSERT-RMS field on the DB.1 panel. Value can be NO orYES.

Default: NO

Required: No

USAGEIndicates an optional Unicenter CA-11 usage code of the character to beused in the restart/rerun. For values, see the Unicenter CA-11documentation. This option is honored only if Unicenter CA-11 is in use andUnicenter CA-7 is inserting the RMS step. See the INSERT-RMS field onthe DB.1 panel.


Required: No


RM

RM

The following table gives a brief description of the RM commands. For moreinformation, see the Database Maintenance Guide where they are fullydescribed.

Panel Purpose

RM Select the virtual resource management functions.

RM.1 Job Resource Management List, add, update, or delete resource connectionsby job. It generates the VRM static type J and Rrecords maintained on the VRM databasecomponent.

RM.2 Job Resource Cross-Reference List jobs using resources. The jobs can be listedby a fully qualified resource name or by a generickey.

RM.3 Active Job Resources Display Display active resources by job. The jobs can belisted generically or with fully qualified job names.

RM.4 Pending Resources Job Display Display all pending resources with an associatedjob name. A pending resource is a nonfreedresource connected to a job that has alreadyexecuted and has been purged from the requestqueue. This resource can only be freed by usingthe PRSCF command. The pending resourcescan be listed using a generic or fully qualifiedresource name.

RM.5 Jobs Waiting on Resources Display jobs waiting for resources. It can be usedto show the resources that a job is waiting forwhen the job shows a status of W-RSRC on theList Queue (LQ) display.

RM.6 Corequisite Resources List List active corequisite resources.

RM.7 Resource Count Resource Management List, add, update, or delete a resource count typeresource.

568 Commands Guide

RQMT

RQMT

The RQMT command causes all index entries for PRED nodes to be reviewedfor cross-reference. The second node of the names are jobs identified asrequirements for other jobs by DB.3 commands. The dependent andpredecessor jobs exist as database entries with applicable schedule IDs andlead times.

If necessary, PRED index entries are created, modified, or deleted according toexisting requirements for the jobs defined in the database.


RQMT

��──RQMT────────────────────────────────────────────────────────��

This command has no keywords.

Usage Notes

Because all existing PRED index entries are rewritten (even if there are nochanges), they are listed in the output from the RQMT command. Jobs that arelisted as having been modified may or may not have had their cross-referenceinformation changed.

Examples

� �RQMT

DATE=yy.ddd CA-7 RQMT ANALYZE REPORT PAGE NO. ��1

THE PRED INDEX ENTRIES FOR THE FOLLOWING JOBS ARE NEWLY CREATED:HEGENER1 HEUNIVD T2LIB12� T2TMSBK1 T21USLIB

THE PRED INDEX ENTRIES FOR THE FOLLOWING JOBS ARE MODIFIED: BZPR1�1 HEBACPRT HEBACSMF HEBACTAB HEDASDPR HEDETASD HEDETASM

HEDETASM HEFRYMAN HEFRYMNW HEKOMDDS HEKOMDMS HEKOMDWS HERECAPR HES��2�1 HETAPEDS HEWEKSAS IFCS2��E PCMOUNTM PCMOUNTT PCNPRIME

PCPRIME PCRPDAY PCTMSSCR PRUCC��1 PRUCC��3 ROSDAILY T2DASDWK T2LIB116 T2LIB119 T2MVSPG1 T2SMAILS T2TMSLS1 T2TSOPK2 WLPR1�1

THE PRED INDEX ENTRIES FOR THE FOLLOWING JOBS ARE DELETED: PCEREPD TGAD TGAE TGAX TGAY

SANA-�� ANALYZE REQUEST COMPLETED AT 16:22:56 yy.ddd� �


RQVER

RQVER

The RQVER command reviews internal JOB/DSN requirements for requestqueue jobs that have not been satisfied.


RQVER

��──RQVER─ ──┬ ┬───────────────────── ──┬ ┬───────────────────── ─────� │ │┌ ┐─�──────── │ │┌ ┐─�3��─

└ ┘──,JOB= ──┼ ┼─jobname── └ ┘──,MAXJOBS= ──┴ ┴─nnnn─ └ ┘─jobname�─

�─ ──┬ ┬──────────────────────── ──┬ ┬─────────────────── ───────────�� │ │┌ ┐─�─────────── │ │┌ ┐─NO──

└ ┘──,SYS= ──┼ ┼─systemname── └ ┘──,UPDATE= ──┴ ┴─YES─ └ ┘─systemname�─

JOBSpecifies the job names for which an analysis is to be performed.

Default: *


Required: No

*Causes all jobs to be analyzed.

jobnameDefines a single job name.


MAXJOBSIndicates the maximum number of jobs that can be in the request, ready,and active queues when this function is executed.

Default: 300

Limits: 1 to 4 numeric characters with a maximum value of 4000

Required: NO

Note: If the number of jobs in the request queue exceeds the MAXJOBSvalue, then no updating (satisfying) of requirements occurs.

570 Commands Guide

RQVER

SYSSpecifies the system names for which an analysis is to be performed.

Default: *


Required: No

*Causes all systems to be analyzed.

systemnameDefines a system name.

systemname*Defines a generic system name terminated with an asterisk.

UPDATESpecifies whether to update (satisfy) missing JOB/DSN requirements andadjust master requirements counts in the queue records for jobs reviewed.

Default: NO

Required: No

NOSpecifies no updating.

YESSpecifies updating.


RSVP

RSVP

The RSVP top line command acknowledges receipt of a prompt and suspendsfurther prompting for that deadline. Both input and output workstations can usethis command. This function is available as the P option on the

■ “QM.1 CPU Jobs Status Prompt Panel” on page 505,

■ “QM.6 Input Networks Prompt Panel” on page 533, and

■ “QM.7 Output Networks Prompt Panel” on page 540.

When Unicenter CA-7 detects a workstation activity that has not been logged inor out by the scheduled time, a message is issued. This message notifies theworkstation of the late status of the activity specified. If the activity for which thestation is being prompted is on schedule, the response should be a LOGIN orLOGOUT. If the activity is late and the workstation is aware of the late statusbut unable to do anything new to correct it, the repetitive prompting can besuspended by acknowledging receipt of the message with the RSVP command.


RSVP

��──RSVP─ ──, ──┬ ┬──JOB=jobnumber ──┬ ┬───────────── ─────────────────�└ ┘──REF=nnnnrrs ── └ ┘──,NW=network

�─ ──┬ ┬────────────────── ──┬ ┬────────────── ──────────────────────��└ ┘──,STATION=station └ ┘──,SUBID=subid

JOBSpecifies the unique Unicenter CA-7 job number assigned to the task whenit entered the queue.



572 Commands Guide

RSVP

REFSpecifies workstation network task reference number of the station to whichthe RSVP applies. When REF is specified, other operands are ignored.

Required: Yes, if JOB is not used


rrRelative sequence of the network in relation to other networksassociated with the job. Leading zeros cannot be omitted.

sRelative position of the station within the network. The first station isposition 1.

NWIdentifies the network for which the RSVP is being entered. If used, thevalue must be the workstation network name in up to eight characters. NWis required if JOB is used for an output workstation network. NW must beomitted if REF is used instead of JOB.


Required: Yes, if JOB is used

STATIONSpecifies the station to which the RSVP applies. If used, the value must bethe station name. STATION is required if JOB is used for an outputworkstation network. It must be omitted if REF is used.


Required: Yes, if JOB is used

SUBIDFurther identifies the network to which the RSVP applies. If used, the valuemust be a SUBID name. It cannot be used with REF. If omitted, spaces areassumed.


Required: No


RSVP

Usage Notes

Responding to a prompt with RSVP causes further prompting to be suspendedfor the specified workstation activity until the next scheduled deadline timeoccurs.

The XPRE, XSPRE, XSPOST, and XPOST panels can also be used to performthis function when working with 3270 terminals.

The RSVP top line command is used to respond to or acknowledge late statusprompts for a single job. It suspends further prompting for the job until the nextscheduled deadline. This is different from NOPRMP, which suspends promptingfor all remaining deadlines for that task.

RSVP can also be used to suspend prompting when a job has unsatisfiedrequirements.

RSVP also suspends prompting of the abnormal completion messages for jobsthat fail.

ExamplesRSVP,JOB=17,STATION=KEYPNCH

RSVP,JOB=163,NW=REPTDSTR,SUBID=PAYR1234,STATION=BURSTRM

RSVP,REF=11�11

574 Commands Guide

RUN, RUNH

RUN, RUNH

The RUN top line command forces immediate scheduling of a job withoutverifying the availability of any input requirements or performing the updatesthat normally follow successful job completion. The RUN command is similar tothe DEMAND command except that DEMAND is normally used to run a job outof turn on a onetime basis. When DEMAND is used, input requirement checkingis performed and database updating is done upon completion of the job. WhenRUN is used, no requirement posting or job triggering occurs.

The RUNH command indicates the job is to be placed in Unicenter CA-7 holdstatus.


RUN RUNH

��─ ──┬ ┬─RUN── ──,JOB=jobname ──┬ ┬────────────────────────── ────────�└ ┘─RUNH─ └ ┘──,ARFSET= ──┬ ┬─arfsetname─

└ ┘─��NONE��───

�─ ──┬ ┬────────── ──┬ ┬──────────── ──┬ ┬───────────── ────────────────�└ ┘──,CLASS=x └ ┘──,DOTM=hhmm └ ┘──,FROMNODE──(1)

�─ ──┬ ┬────────────────────── ──┬ ┬────────────── ───────────────────�└ ┘──, ──┬ ┬──JCLID=nnn ──── └ ┘──,LEADTM=hhmm

└ ┘──JCLLIB=&x...x

�─ ──┬ ┬──────────────────── ──┬ ┬──────── ──┬ ┬────────────────── ─────�└ ┘──,MAINID= ──┬ ┬─ALL── └ ┘──,REF──(1) │ │┌ ┐─1───


�─ ──┬ ┬──────────── ──┬ ┬─────────── ───────────────────────────────��└ ┘──,TIME=hhmm └ ┘──,TYPE=RES

Note:1 You cannot specify this keyword. See “Usage Notes” on page 578.

JOBIdentifies the job to be submitted. The value must be a job name. If the jobhas not been defined in the Unicenter CA-7 database, this name must alsomatch the member name for the JCL unless the job is defined in thedatabase. See also JCLID.


Required: Yes

ARFSETIdentifies the ARF set name that is used for this run of the job. If **NONE**is specified, no ARF processing is performed for this run of the job.

Limits 1 to 8 alphanumeric characters or **NONE**


RUN, RUNH

Required: No

CLASSSpecifies the workload balancing class for resource checking.

Limits 1 alphanumeric character

Required: No

DOTMSpecifies a due-out time-of-day for the job. If omitted, the current time(when command is processed) plus the lead time is used.

Required: No

hhmmDefines the time-of-day where hh is the hours (0 to 24) and mm isminutes (0 to 59). Leading zeros are not required.

JCLIDIdentifies the JCL data set that contains the execution JCL to be submitted.If used, the value must be a numeric INDEX associated with the desiredJCL data set (on the JCL statement in the initialization file). For moreinformation about the initialization file, see the Systems Programmer Guide.This field or the JCLLIB field is required if the job is not defined in thedatabase. JCLID and JCLLIB are mutually exclusive.



JCLLIBIdentifies the JCL data set that contains the execution JCL to be submitted.If used, the value must be a symbolic INDEX associated with the desiredJCL data set (on the JCL statement in the initialization file). For moreinformation about the initialization file, see the Systems Programmer Guide.This field or the JCLID field is required if the job is not defined in thedatabase. JCLID and JCLLIB are mutually exclusive.




LEADTMSpecifies the lead (processing) time required for the job to run. If omitted, 1hour is used.

Required: No

hhmmDefines the time where hh is hours (0 to 23) and mm is minutes (0 to59). Leading zeros are not required.

576 Commands Guide

RUN, RUNH


Required: No





SCHIDIndicates the schedule ID to be used for evaluating JCL overrides that arescheduled with the #Jx or #Xx commands. If used, the value must be aschedule ID number.

Default: 1


Required: No (unless the SCHEDULE statement in the initialization filespecifies SCHID=YES, then this parameter is required)

TIMEEstablishes a submit time-of-day requirement for the job.

Required: No

hhmmDefines the time-of-day where hh is hours (0 to 23) and mm is minutes(0 to 59). Leading zeros are not required.

TYPEIndicates the job is being scheduled for rerun. The value must be specifiedas shown. TYPE=RES is optional. If used, a restart requirement is placedon the job, and the job has to be manually restarted. (See “QM” onpage 503, “XRST” on page 661, and “RESTART” on page 564.)

Required: No


RUN, RUNH

Usage Notes

The following normal scheduling activities of Unicenter CA-7 are bypassed:

■ Verification of input requirement availability.

■ The JCL-OVRD and VERIFY (from the JOB panel) are ignored.

■ Scheduling of output workstation networks.

■ Database index entry updates for newly created output data sets.

■ Prior-run queue updates.

■ Posting of job and data set dependencies. This includes mutually exclusivejob dependencies.

■ Scheduling of job or data set triggered (AUTO) jobs.

■ #JCL statement in JCL. The statement is taken out, but the overrideindication is not done.

The following normal scheduling activities occur:

■ The appropriate LTERM is prompted if the job becomes late.

■ The appropriate LTERM is notified when the job completes.

■ Run log is updated when the job completes or is restarted after a failure.

If TYPE=RES is specified in the RUN command, the Unicenter CA-7 restartfacilities, QM.4 panel, or RESTART command can be used to restart or rerunthe job.

If workload balancing is used, the job is run under the default WLB class forRUN if the CLASS= keyword is not specified. (See the description of theRUNCLASS parameter on the OPTIONS statement in the initialization file in theSystems Programmer Guide.)

REF and FROMNODE are reserved keywords that are not considered validinput unless generated by Unicenter CA-7 internally. These keywords cannot becoded on online, batch, or trailer terminal transactions. They are reserved forspecial functions but are described here because they can occur in masterstation messages.

If REF is specified, the job does not wait for restart in the request queuefollowing abnormal job completion.

578 Commands Guide

RUN, RUNH

ExamplesRUN,JOB=CA7JOB5

RUN,JOB=CA7JOB1,TYPE=RES

RUNH,JOB=CA7JOB4,DOTM=153�,LEADTM=35,SCHID=27


RUNNW

RUNNW

The RUNNW top line command is used in place of the DMDNW command toforce initiation of input or output networks. When used for input networks, norequirement posting or job triggering occurs. When used for output networks, noassociation is made to the CPU job.


RUNNW

��──RUNNW─ ──,NW=network ──┬ ┬──────────── ──┬ ┬─────────── ───────────�└ ┘──,DESC=text └ ┘──,JOB=name

�─ ──┬ ┬────────────── ──┬ ┬────────────────── ──┬ ┬────────────── ────��└ ┘──,LEADTM=hhmm │ │┌ ┐─1─── └ ┘──,SUBID=subid

└ ┘──,SCHID= ──┴ ┴─nnn─

NWSpecifies the network name to be scheduled. The value must be thenetwork name used when the network was defined in the database.


Required: Yes

DESCSupplies additional identifying free-form information up to eight characters.This value is displayed on the QM.6, QM.7, LPRE, and LPOST panels.


Required: No

JOBSupplies a name to be assigned to the network. If neither SUBID nor JOBis specified, JOB defaults to DMD#nnnn, where nnnn is the Unicenter CA-7assigned job number.

Default: SUBID


Required: No

LEADTMSpecifies a lead (processing) time for calculating deadline start time of thefirst station in the network.

Required: No

hhmmDefines the time where hh specifies hours (0 to 99) and mm specifiesminutes (0 to 59). Leading zeros not required.

580 Commands Guide

RUNNW

SCHIDIdentifies which network schedule ID is to be used.

Default: 1


Required: No

SUBIDSupplies an additional identifying name for the network when it enters thequeue.


Required: No

Usage Notes

When a network is scheduled, Unicenter CA-7 determines whether the networkshould be placed in the preprocess or postprocess queue based on thedefinition of the network in the database.

All networks can be requested independently from CPU jobs.

A job name is assigned to the network when it enters the queue.

ExamplesRUNNW,NW=RECPTS

RUNNW,NW=REPTS,SUBID=PAYR1234,DESC=PAYDATA

RUNNW,NW=REPTS,SCHID=27,LEADTM=�125


RUSH

RUSH

The RUSH top line command flags jobs in the queues as being needed assoon as possible. The flag is for subsequent display information only, displayingthe word RUSH on displays, and has no direct effect on the processing cycle.

Once a job is flagged with the RUSH command, the job indicates RUSH in theSTATUS field on LQ type displays as long as it is ready to run and it is not late.Should it become late, the STATUS field shows LATE. Other values appear ifany error is awaiting resolution.


RUSH

��──RUSH──,─ ──┬ ┬──JOB= ──┬ ┬─jobnumber─ ───────────────────────────�� │ │├ ┤─ALL─────── │ │└ ┘─ALLP──────

└ ┘──REF=nnnnrrs ────────

JOBIndicates the jobs to be flagged as critical.


jobnumberIndicates a job number to be selected.



ALLPIndicates same as ALL but includes all networks in the preprocessqueue as well.

REFSpecifies workstation task reference number of the station to which thecommand applies.


nnnnUnicenter CA-7 job number. Leading zeros can be omitted. Referencenumbers can be obtained by using the LPRE or LPOST commands.

rrRelative sequence of the network in relation to other networksassociated with the job. Leading zeros cannot be omitted.

sRelative position of the station within the network. The first station isposition 1.

582 Commands Guide

SCHDMOD

SCHDMOD

The SCHDMOD command displays the DB.2.7 - Modification to ResolvedSchedule Dates panel. You can find more information about this panel in theDatabase Maintenance Guide.


SCHDMOD

��──SCHDMOD─────────────────────────────────────────────────────��

The SCHDMOD command has no associated keywords.


SCRATCH

SCRATCH

The SCRATCH command scratches an expired DASD data set. TheSCRATCHP command scratches a data set even if it is date protected. Thisfunction is also offered on the UT Menu panel as function 4.


SCRATCH SCRATCHP

��─ ──┬ ┬─SCRATCH── ──,DSN=dsname ──┬ ┬───────────── ─────────────────��└ ┘─SCRATCHP─ └ ┘──,VOL=volume

DSNIndicates the fully qualified name of the data set. A relative generationrequest can be made for a cataloged generation data set. This commanddoes not scratch PDS members.


Required: Yes

VOLIndicates the volume on which the data set resides. The volume must beavailable to Unicenter CA-7. If the catalog is used, the data set isuncataloged if the scratch is successful.

Default: System catalog


Required: No

584 Commands Guide

SCRATCH

Usage Notes

Unicenter CA-7 provides a user exit to control the use of this command.

This command does not remove data sets from the Unicenter CA-7 database.

A DD statement of the following form must exist in the Unicenter CA-7 JCL foreach volume to be accessed:

//U7volser DD UNIT=uuuuuuuu,DISP=SHR,VOL=SER=xxxxxx

The ddname is U7 followed by the volume serial number (volser). An ALLOCcommand or function 11 on the UT Menu panel can be used if the needed DDstatement was not included in the JCL.

ExamplesSCRATCH,DSN=USER.FILE1

SCRATCH,DSN=USER.FILE2,VOL=VOLMO1

SCRATCHP,DSN=USER.DATE.PROT,VOL=VOLMO2

SCRATCH,DSN=USER.GDG(�)


SPACE

SPACE

The SPACE command lists information about available space on DASDvolumes available to Unicenter CA-7. This function is available on the UT Menupanel as FUNCTION value 16 or on any other menu or formatted panel asFUNCTION value UT.16.


SPACE

��──SPACE─ ──,VOL= ──┬ ┬─ALL────────── ─────────────────────────────�� ├ ┤─volume─────── │ │┌ ┐─,──── └ ┘──( ───� ┴volume )

VOLIndicates the volumes for which space information is to be displayed.


Required: Yes

ALLSpecifies all volumes available to Unicenter CA-7 by way of //U7nnnnnnDD statements.

volumeIdentifies a specific volume.

(volume,...,volume)Identifies up to five volumes and must be enclosed in parentheses.

ExamplesSPACE,VOL=ALL

SPACE,VOL=VOLMO1

SPACE,VOL=(VOLMO1,VOLMO2,VOLMO4,VOLMO7)

Displayed for each volume are unit name, UCB address, device code, usercount, reserve count, number of free cylinders, number of free tracks, and thelargest contiguous extent.

SPACE,VOL=ALL can be used to determine which volumes are available toUnicenter CA-7 by way of //U7nnnnnn DD statements.

586 Commands Guide

SSCAN

SSCAN

The SSCAN top line command reviews schedule scan options or alters the wayin which schedule scan performs its scheduling functions. Schedule scan is anautomatic scheduling facility and can be altered as follows:

■ Schedule scan can be forced to run ahead of schedule, either to bring morework into the queues, or to reissue prompts for overdue jobs or workstationactivities.

■ The time parameters that govern schedule scan execution can be modifiedonline.

■ The format of initial requirements scan output and prompt messages can beabbreviated. Jobs are scanned as they enter the request queue to see ifany requirements are satisfied. This is the initial requirements scan.

■ The due-out time of all newly scheduled work can be delayed as it entersthe queue.

■ Schedule scan can cause all new work to enter the queue in UnicenterCA-7 hold status.

■ Schedule scan can cause posting of the ARF dispatcher.

Any change made to parameters controlling schedule scan execution does nottake effect until the appropriate schedule scan activity runs.


SSCAN

��──SSCAN─ ──┬ ┬───────────── ──┬ ┬────────── ────────────────────────�└ ┘──,DATE=yyddd └ ┘──,INCR=hh

�─ ──┬ ┬──────────────────── ──┬ ┬────────────── ─────────────────────�│ │┌ ┐─�──── └ ┘──,PEREND=hhmm└ ┘──,LEADTM= ──┴ ┴─mmmm─

�─ ──┬ ┬──────────────── ──┬ ┬──────────── ──┬ ┬───────────── ──────────�└ ┘──,PERSTART=hhmm └ ┘──,QDWELL=mm └ ┘──,REPRMPT=mm

�─ ──┬ ┬─────────── ──┬ ┬──────────────── ──┬ ┬────────── ──────────────�└ ┘──,RETRY=mm └ ┘──,SCAN=function └ ┘──,SPAN=hh

�─ ──┬ ┬──────────── ──────────────────────────────────────────────��└ ┘──,TIME=hhmm


SSCAN

DATEUsed with PERSTART to cause schedule scan to go back and repeatfunctions that were performed on a previous date. This is useful in arecovery situation to cause work that may have been lost to again bebrought into the queues. A system clock error that caused work to beskipped can also be handled in this manner. DATE is optional but, whenspecified, must be the beginning Julian date for which schedule scanfunctions are to be performed.

Note: If the date needs to be set forward (future), an SSCAN commandwith TIME=0, must be entered followed by another SSCAN command withDATE=00000, PERSTART=hhmm before the SSCAN command with thefuture date.

Limits: 5 numeric characters in yyddd format

Required: No

INCRChanges the time interval to elapse between schedule scan wake-ups. TheINCR value must not be greater than the SPAN value.

Limits: 1 to 2 numeric characters from 1 to 24 hours

Required: No

LEADTMSpecifies a number of minutes to be added globally to the schedule timesof all the work entering the queue. If 0 is specified, no change is made tothe scheduled times for the work.

Default: 0


Required: No

Note: Does not apply to preprocessing work or demanded jobs.

PERENDUsed with PERSTART and DATE to set an ending time for schedule scanfunctions. Must be the time-of-day desired in the hhmm format. WhenPEREND is used, the automatic wake-up of schedule scan is disabled. TheSSCAN,SCAN=SCH command or a startup of Unicenter CA-7 must beused to force schedule scan to run. After schedule scan is complete,automatic wake-up is still disabled. This allows another PEREND time to beentered, if necessary. To resume automatic wake-up of schedule scan, useSSCAN,TIME= specifying a time when schedule scan is to wake-up. A newfield appears under NEXT SCAN PERIOD START TIME when thisparameter is in effect.

When using PEREND, we recommend that the Unicenter CA-7 initializationfile INIT statement PERFORM option of 5 (duplicate checking) not be used.This lessens the possibliity of a "duplicate" job being scheduled.

588 Commands Guide

SSCAN

PERSTARTUsed with DATE to set schedule scan functions back to a previous time.Must be the time-of-day desired in hhmm format.

QDWELLSpecifies an additional number of minutes to be added to the span time, asan additional safety factor, to ensure that scheduling requirements can bemet between the queue entry and deadline times.

Limits: 1 to 2 numeric characters from 1 to 59 minutes

Required: No

REPRMPTSpecifies a number of minutes to elapse between a prompt message andeach subsequent reprompt. If REPRMPT=0, the reprompt function ofschedule scan is suspended.


Required: No

RETRYSpecifies a number of minutes between wake-ups for reattempting to attachJCL and requirements for jobs in RETRY status. Jobs are in RETRY statuswhen a dynamic allocation (SVC99) failure occurs during scheduling (thatis, date schedules, triggers or DEMAND commands). If 0 (zero) is specified,the RETRY function is suspended.


Required: No

SCANIndicates the type of schedule scan function to be performed.

Required: No

ABRAbbreviates the format of initial requirements scan output and promptmessages.

ARFCauses posting of the ARF dispatcher.

COMForces a completion processing cycle to run and check for completedjobs.

HLDForces all jobs to be placed in Unicenter CA-7 hold status as they enterthe queue. Jobs must then be released on a job-by-job basis. Theeffect of SCAN=HLD can be disabled by SCAN=REL.

LNGRestores the normal format of initial requirements scan output andprompt messages.


SSCAN

RELDisables the effect of a previous SCAN=HLD.

REPForces immediate reprompting for jobs and workstation activities thatare late.

RETForces a skeleton retry cycle. See the RETRY parameter for moreinformation about RETRY.

SCHForces schedule scan to run and add more work to the queues. Thisfunction activates schedule scan if it is not active.

SPANChanges the number of hours that schedule scan is to look forward, duringeach wake-up, for jobs that must be added to the queue. The SPAN valuemust not be less than the INCR value.

Limits: 1 to 2 numeric characters from 1 to 24 hours

Required: No

TIMESpecifies the next wake-up time-of-day for schedule scan to bring jobs intothe queues. This value is normally determined by adding the INCR value tothe previous scan. If 0 is specified for TIME, this function of schedule scanis disabled. If the time specified is less than the current time, the next dayis assumed.

Required: No

hhmmDefines the time-of-day where hh represents hours (0 to 24) and mmrepresents minutes (0 to 59).

Usage Notes

A job is selected for scheduling if its queue entry time falls within the timewindow (current time plus span) currently being scanned. Queue entry time isdetermined by adding the queue dwell time factor to the lead time defined in ajob's schedule entry, and then subtracting the result from the job's due-out time.

All values identified by keywords can be reviewed by entering SSCAN with noparameters.

590 Commands Guide

SSCAN

ExamplesSSCAN,SCAN=REP,REPRMPT=5

SSCAN,QDWELL=3�

SSCAN,SPAN=3,INCR=2

SSCAN,TIME=19��

� � SSCAN

CURRENT SCHEDULE SCAN VALUES ----------------------------

SPAN = 24� INCREMENT = 12�

QUEUE DWELL = 3� SKELETON RETRY = 15 REPROMPT = 1� LEAD TIME = �

STATUS: REQQ IS ACTIVE ABR MSGS = NORDYQ IS ACTIVE HOLD JOBS = NO

NEXT SCAN WAKE-UP = YYDDD AT 16��

NEXT SCAN PERIOD START TIME = YYDDD AT 163�

SPO�-�� REQUEST COMPLETED AT 15:58:49 ON YY.DDD.

� �


START

START

The START top line command resumes normal job flow in the request andready queues after a previous STOP command was issued to halt job flow. ASTART command is required to reestablish normal queue activity following aSTOP command.


START

��──START─ ──, Q= ──┬ ┬─ALL─ ────────────────────────────────────────�� ├ ┤─RDY─ └ ┘─REQ─

QIdentifies the queues to be restarted after a previous STOP command wasissued.

Required: Yes

ALLCauses both the request and ready queues to be restarted.

RDYCauses the ready queue to be restarted.

REQCauses the request queue to be restarted.

ExamplesSTART,Q=REQ

START,Q=RDY

START,Q=ALL

592 Commands Guide

STOP

STOP

The STOP top line command temporarily suspends normal job movement ineither the request or ready queues, or both.


STOP

��──STOP─ ──, Q= ──┬ ┬─ALL─ ─────────────────────────────────────────�� ├ ┤─RDY─ └ ┘─REQ─

QIdentifies the queues to be suspended. Queues can be restarted with theSTART command.

Required: Yes

ALLCauses both the request and ready queues to be suspended.

RDYCauses the ready queue to be suspended.

REQCauses the request queue to be suspended.

Usage Notes

Stopping the request queue halts all movement of jobs to the ready queue untila START is issued for the request queue. All other functions that relate to jobsin the request queue continue normally and outstanding requirements areposted as they are satisfied. JCL overrides can be entered and manual postingdone, prompts are issued for jobs that are late, and so forth.

Stopping the ready queue prevents submission of any jobs for execution on theCPUs. Movement of jobs into the ready queue continues normally unless therequest queue is also stopped.

ExamplesSTOP,Q=REQ

STOP,Q=RDY

STOP,Q=ALL


SUBMIT

SUBMIT

The SUBMIT top line command modifies and expedites the process of jobsubmission for jobs that already reside in the queues. This can beaccomplished in two ways:

■ All outstanding input requirements for the specified jobs can be posted assatisfied.

■ Optionally, by specifying EXPRESS=YES, a priority can be set for a specificjob, ensuring that the job is submitted ahead of other jobs also ready forsubmission.

Note: EXPRESS=YES has no effect if workload balancing is being used.


SUBMIT

��──SUBMIT─ ──┬ ┬──────────────── ──┬ ┬────────────── ───────────────��└ ┘──,JOB=jobnumber └ ┘──,EXPRESS=YES

JOBSpecifies the Unicenter CA-7 job number of the job whose requirements areto be posted as satisfied.


Required: No

EXPRESSIndicates the job is to be placed ahead of all other jobs (those withoutEXPRESS=YES) for submission. Must be coded as shown. Not valid ifworkload balancing is being used. Use of EXPRESS=YES does notestablish an increased execution priority for a job. Rather, it ensures thatnonexpress jobs are not submitted ahead of a job flagged as an expressjob.

Required: No

Note: If no keywords are specified, Unicenter CA-7 job submission isactivated, and if Unicenter CA-11 is used, it verifies that the interface is stillactive. If the interface is not active, then a WTOR is issued. Unicenter CA-7 isin a wait state until the operator replies.

594 Commands Guide

SUBMIT

ExamplesSUBMIT,JOB=163

SUBMIT,JOB=163,EXPRESS=YES

SUBMIT


SUBSCH

SUBSCH

The SUBSCH top line command adjusts schedules to advance the overallprocessing of the system. A user-supplied increment of up to 24 hours can besubtracted from the scheduled start and due-out times. This command canestablish earlier deadlines for the start and due-out times of one or all jobs in aqueue. This is only possible after the job or workstation activity has entered thequeue.


SUBSCH

��──SUBSCH──,─ ──┬ ┬──JOB= ──┬ ┬─nnnn─ ──,TIME=mmmm ──────────────────�� │ │├ ┤─ALL── │ │└ ┘─ALLP─


JOBIdentifies the jobs for which schedule times are to be adjusted.




ALLAll jobs in the request, ready, and postprocess queues.

ALLPAll jobs including those in the preprocess queue.

596 Commands Guide

SUBSCH

REFSpecifies a particular workstation network task within a network and allsubsequent stations for which schedules are to be adjusted. Referencenumbers can be obtained by using the LPRE or LPOST commands.


nnnnrrsDefines the workstation reference number assigned by Unicenter CA-7.


rrRelative network sequence for this job number. Leading zeros cannotbe omitted.

sRelative station position within the network. The first station is position1.

TIMEThe amount of time to be subtracted from the deadline start and due-outtimes of the jobs or workstations indicated.


Required: Yes

Usage Notes

It may be desirable to improve on established schedules if a block of work iscanceled, if a resource is made available that is normally dedicated to anotherfunction, or if other work has completed well ahead of schedule.

When SUBSCH is used to adjust schedules, prompting is based on theadjusted deadline start and due-out times.

To delay schedule times, see “ADDSCH” on page 131. The XUPD panel canalso be used to perform this function for individual jobs from a 3270 terminal.

The use of SUBSCH has no effect on when a job is submitted but can make ajob show as "late" earlier.

ExamplesSUBSCH,JOB=143,TIME=12�

SUBSCH,JOB=ALLP,TIME=72�

SUBSCH,REF=12�11,TIME=6��


SUBTM

SUBTM

This function is available through the “QM.3 CPU Job Attributes Prompt Panel”on page 521 and can be satisfied through the “QM.1 CPU Jobs Status PromptPanel” on page 505.

The SUBTM command modifies the required submit time-of-day for a CPU jobin the request queue. These modifications are permitted:

■ Add a specific submit time requirement where none was previously defined.

■ Remove a defined submit time requirement.

■ Change an existing submit time requirement to either earlier or later thandefined.


SUBTM

��──SUBTM─ ──,JOB=jobnumber ──┬ ┬──────────── ──────────────────────��└ ┘──,TIME=hhmm

JOBSpecifies the Unicenter CA-7 assigned job number of the job for which asubmit time-of-day requirement is to be added, modified, or removed.


Required: Yes

TIMESpecifies the new submit time-of-day in hours and minutes. TIME isrequired to add a submit time-of-day requirement if none exists or tochange an existing requirement. If TIME is omitted, an existing submittime-of-day restriction is removed.

Required: No

hhmmDefines the time-of-day where hh is hours (0 to 24) and mm is minutes(0 to 59). Maximum is 2400.

If the value given is less than the current time (when the command isprocessed), the submit day is incremented by one.

598 Commands Guide

SUBTM

ExamplesSUBTM,JOB=163

SUBTM,JOB=163,TIME=183�


TIQ

TIQ

If you have BrightStor CA-1 installed on your system, you can use the TIQcommand to directly interact with BrightStor CA-1. For more information aboutthe Unicenter CA-7/BrightStor CA-1 interface and the TIQ command, see theInterfaces Guide.

600 Commands Guide

TRIG

TRIG

The TRIG command causes index entries to be reviewed and, if needed,updates cross-reference pointers to the following database elements:

JDEPEntries for jobs that trigger other jobs.

AUTOEntries for data sets and input networks that trigger jobs.

TRGDEntries for jobs that are triggered by other jobs, networks, or data sets.

If necessary, TRGD entries are created, modified, or deleted according toexisting JDEP and AUTO entries.


TRIG

��──TRIG────────────────────────────────────────────────────────��

The TRIG command has no keywords.

Usage Notes

Because all existing TRGD index entries are rewritten (even if there are nochanges), they are listed in the output from the TRIG command. Jobs that arelisted as having been modified may or may not have had their cross-referenceinformation changed.


TRIG

Examples

� �TRIG

DATE=yy.ddd CA-7 TRIG ANALYZE REPORT PAGE NO. ��1

THE TRGD INDEX ENTRIES FOR THE FOLLOWING JOBS ARE NEWLY CREATED: NONE

THE TRGD INDEX ENTRIES FOR THE FOLLOWING JOBS ARE MODIFIED:APJ2�� APJ3�� APJ3�1 APJ3�2 APJ35� APJ4�� APJ41�APJ411 APJ412 APJ413 APJ5�� APJ5�1 APJ5�2 APJ6��

BRCOMM�3 BRCOMM�4 BZPR3�1 BZPR4�1 BZPR5�1 DEAMREST HEGENER1 HEGENER2 HEGENER5 HEGENER6 IFACTVTY IFCSBKP1 IFCSFLMO IFCSTSTM

IFCS3�� IFCS3��H IFCS3��L IFCS355 IFCS36� IFCS37� IFCS37�QIFCS514 IFCS514H IFCS61� IFCS63� IFCS63�2 IFCS64� IFCS66�C

UDENSPEC UDENSUSP UDEN18� UDEN92� UDEN921 UDEN928 UDEN929UDEN931 UDEN933 UDJOEM WLPR3�1 WLPR4�1 WLPR5�1

THE TRGD INDEX ENTRIES FOR THE FOLLOWING JOBS ARE DELETED: TGAB TGAC TGAD TGAE TGAF

SAN7-�� ANALYZE REQUEST COMPLETED AT 16:21:�5 yy.ddd� �

602 Commands Guide

UNC

UNC

The UNC command uncatalogs a data set. This function is available on the UTMenu panel as FUNCTION value 5 or on any other menu or formatted panel asFUNCTION value UT.5.


UNC

��──UNC─ ──,DSN=dsname ──┬ ┬────────────── ─────────────────────────��└ ┘──,CVOL=volume

DSNDefines the fully qualified name of the data set that is to be uncataloged. Arelative generation request can be made for a generation data set. Afteruncataloging the data set, its index is deleted if it is no longer being usedby other data sets.


Required: Yes

CVOLDefines the volume containing the catalog.

Default: SYSRES volume


Required: No

ExamplesUNC,DSN=USER.FILE1

UNC,DSN=USER.GDG(+�)

UNC,DSN=USER.FILE2,CVOL=ALTCAT


UT

UT

The CA-7 Utilities Menu panel displays the online menu of available utilityfunctions.

� � --------------------------- CA-7 UTILITIES MENU ----------------------------- FUNCTION ===>

DATASET MAINTENANCE: VOLUME ACCESS:1 - ALLOCATE/CATALOG 11 - ALLOCATE2 - CATALOG 12 - DEALLOCATE3 - RENAME4 - SCRATCH DISPLAY DASD INFO:5 - UNCATALOG 13 - FORMAT 1 DSCB

14 - DIRECTORY INFOCATALOG/INDEX MAINTENANCE: 15 - DATASET ATTRIBUTES MAP6 - BUILD GDG INDEX 16 - AVAILABLE DASD SPACE7 - DELETE INDEX 17 - PHYSICAL DATA RECORDS8 - CONNECT A CATALOG 18 - CATALOG BLOCK9 - DISCONNECT A CATALOG 19 - CATALOG ENTRIES

DATASET SEARCH:1� - FIND DSN ON DASD

PROGRAM: UTL� MSG-INDX: -- UT -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:

■ UT as a top line command.

■ UT as the FUNCTION on any other menu or formatted input panel.

To exit:



604 Commands Guide

UT

Usage Notes

The UT menu is not available in batch mode.

Each function on the panel has an equivalent top line command. Each selectionon the menu panel receives the same security validation as its equivalent topline command. Menu functions and their equivalent Unicenter CA-7 top linecommands are as follows:

1 - AL/ALC 11 - ALLOC2 - CAT 12 - DEALLOC3 - RENAME 13 - DMPDSCB4 - SCRATCH/SCRATCHP 14 - LISTDIR5 - UNC 15 - MAP6 - BLDG 16 - SPACE7 - DLTX 17 - DMPDSN8 - CONN 18 - DMPCAT9 - DCONN 19 - LOC

1� - FIND

A formatted function panel is returned for each function by entering theappropriate FUNCTION value and pressing Enter. Details of those panels aregiven in the following discussions.

PF Keys

Once a function has been selected on the menu and the function panel isdisplayed, program function key 3, PF3 is temporarily set to return to the UTmenu panel. In native Unicenter CA-7 VTAM mode, any value that waspreviously assigned to PF3, by either the user or Unicenter CA-7, is temporarilyignored as long as the function panel is being used and reverts back to theoriginal value after it is used once or after a top line command is entered.

PF7 and PF8 are similarly temporarily overridden to /PAGE-1 and /PAGE+1respectively until PF3 is pressed or a top line command is issued.

Special considerations apply when using Unicenter CA-7 under TSO-ISPF.

■ PF key interrupts are not processed by Unicenter CA-7, unless PASSTHRUis the ISPF application command table value associated with the ISPFcommand that is assigned to the PF key in question.

■ If PF3 is assigned the END command in ISPF, PF3 ends the UnicenterCA-7 TSO-ISPF session unless END is assigned a value of PASSTHRU inthe ISPF application command table.


UT.1 - Allocate/Catalog Dataset Panel


This panel allocates and optionally catalogs a DASD data set.

� � -------------------- CA-7 UTILITIES - ALLOCATE DATASET ---------------------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

DSNAME: VOLSER: (BOTH DSNAME AND VOLSER ARE REQUIRED)

ALSO CATALOG: (Y = ALLOCATE AND CATALOG)

SPACE ALLOCATION:TYPE: (C=CYL, DEFAULT IS T=TRK)PRIMARY: (REQUIRED, UP TO 5 DIGITS)SECONDARY: (OPTIONAL, UP TO 4 DIGITS)DIR BLOCKS: (FOR PDS ONLY, UP TO 4 DIGITS)

DCB INFORMATION:RECFM: (REQUIRED, E.G., FB, ETC.)LRECL: (REQUIRED, UP TO 5 DIGITS)BLKSIZE: (REQUIRED, UP TO 5 DIGITS)

PROGRAM: UTFA MSG-INDX: -- UT.1 -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:

■ 1 as the FUNCTION on the UT panel.

■ UT.1 as the FUNCTION on any other menu or formatted input panel.

■ UT.1 as a top line command.

■ If an error is encountered with a top line AL/ALC command, this panel isreturned.

To exit:




606 Commands Guide



FUNCTIONUsed only to transfer to another menu or some other formatted panelfunction that is only offered on another menu. Enter the name of thedesired panel.

DSNAMEFully qualified name of the data set to be allocated.

Required: Yes

VOLSERDefines a volume serial number on which the data set is to be allocated.The volume must have been made available to Unicenter CA-7 with aU7volser type of DD statement, (as discussed in the Systems ProgrammerGuide), with a top line ALLOC command or through function 11 of the UTMenu panel.

Required: Yes

ALSO CATALOGEnter Y to also catalog the data set after it is allocated.

Default: N

Required: No

SPACE ALLOCATIONPanel title line only.

TYPEDefines a type of allocation desired. C indicates allocation in units ofcylinders. T, the default, indicates allocation in units of tracks.

PRIMARYDefines a primary space allocation amount.

Required: Yes

SECONDARYDefines a secondary space allocation amount.

Required: No

DIR BLOCKSDefines a number of directory blocks to be allocated for a PDS. Zero, thedefault, indicates DSORG of PS. Nonzero indicates DSORG of PO.

Default: 0

Required: No

DCB INFORMATIONPanel title line only.



RECFMRecord format. Format must be F, FB, V, VB, VBS, VS, U, FA, FBA, FM,FBM, VA, VBA, VM, or VBM.

Required: Yes

LRECLLogical record length.

Required: Yes

BLKSIZEBlock size.

Default: 0

Required: No

Usage Notes

Press Enter when the fields have been completed. The panel returns with theMESSAGE field indicating what action was taken or any errors that occurred.

608 Commands Guide

UT.2 - Catalog Dataset Panel


This panel catalogs a data set.

� � --------------------- CA-7 UTILITIES - CATALOG DATASET ----------------------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

DSNAME: (REQUIRED)

VOLSER 1: (AT LEAST 1 REQUIRED) VOLSER 2: VOLSER 3: VOLSER 4: VOLSER 5:

UNIT NAME: (UP TO 8 CHARACTERS) OR OR DEVICE: (8 HEX CHARACTERS)

FILE SEQ: (TAPE ONLY, UP TO 3 DIGITS)

CVOL: (VOLSER OF CATALOG, DEFAULT IS SYSRES)

PROGRAM: UTFD MSG-INDX: -- UT.2 -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:




■ If an error is encountered with a top line CAT command, this panel isreturned.

To exit:








DSNAMEFully qualified name of the data set to be cataloged.

Required: Yes

VOLSER 1

VOLSER 2

VOLSER 3

VOLSER 4

VOLSER 5Up to 5 volumes on which the data set resides. At least one VOLSER isrequired.

UNIT NAMEUnit name of the type of device on which the data set resides. The unitname must be defined in SASSUTBL. (For example, 3350, DISK, SYSDA.)This field must be omitted if DEVICE field is used; otherwise, it is required.

DEVICEHexadecimal device code similar to those defined in SASSUTBL. This fieldmust be omitted if UNIT NAME field is used; otherwise, it is required.

FILE SEQLabel sequence number. If omitted, 0 (zero) is assumed for DASD and 1 isassumed for tape data sets.

Required: No

CVOLVOLSER containing the catalog.

Default: SYSRES

Usage Notes


610 Commands Guide

UT.3 - Rename Dataset Panel


This panel renames a DASD data set.

� � --------------------- CA-7 UTILITIES - RENAME DATASET ----------------------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

DSNAME: (REQUIRED)

VOLSER: (REQUIRED IF NOT CATALOGED)

NEW DSNAME: (REQUIRED)

PROGRAM: UTFO MSG-INDX: -- UT.3 -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:




■ If an error is encountered with a top line RENAME command, this panel isreturned.

To exit:








DSNAMEFully qualified name of the data set to be renamed. Required field.

VOLSERVolume serial number on which the data set resides. Required if notcataloged. The volume on which the data set resides must be available toUnicenter CA-7 through U7volser DD statement, top line ALLOC commandor function 11 on the UT Menu panel.

NEW DSNAMEFully qualified new name desired for the data set. Required field.

Usage Notes


612 Commands Guide

UT.4 - Scratch Dataset Panel


This panel scratches a DASD data set.

� � --------------------- CA-7 UTILITIES - SCRATCH DATASET ----------------------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

DSNAME:(FULLY-QUALIFIED SPECIFIC NAME)


PURGE: (Y = SCRATCH EVEN IF NOT EXPIRED)

PROGRAM: UTFP MSG-INDX: -- UT.4 -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:




■ If an error is encountered with top line SCRATCH or SCRATCHP this panelis returned.

To exit:








DSNAMEFully qualified name of the data set to be scratched. Required field.

VOLSERVOLSER on which the data set resides. Required if not cataloged. Ifomitted, data set is uncataloged if the scratch is successful. The volume onwhich the data set resides must be available to Unicenter CA-7 throughU7volser DD statement, top line ALLOC command, or function 11 on theUT Menu panel.

PURGEEnter Y if data set is to be scratched even though the expiration date hasnot been reached. Optional. Default is to scratch only if the expiration datehas been reached.

Usage Notes


614 Commands Guide

UT.5 - Uncatalog Dataset Panel


This panel uncatalogs a data set.

� � -------------------- CA-7 UTILITIES - UNCATALOG DATASET ---------------------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)



PROGRAM: UTFR MSG-INDX: -- UT.5 -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:




■ If an error is encountered with a top line UNC command, this panel isreturned.

To exit:








DSNAMEFully qualified data set name or name and relative GDG of the data set tobe uncataloged. Required field. If relative GDG, the index is also deleted ifit is no longer needed for other versions of the data set.

CVOLVOLSER containing the catalog. Default is SYSRES.

Usage Notes


616 Commands Guide

UT.6 - Build GDG Index Panel


This panel builds an index for a generation data group (GDG).

� � --------------------- CA-7 UTILITIES - BUILD GDG INDEX ---------------------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

INDEX:(REQUIRED, FULL INDEX NAME)

NUMBER OFENTRIES: (CATALOG ENTRIES, REQUIRED, UP TO 3 DIGITS, MAX 255)

DELETEWHEN FULL: (A = ALL ENTRIES, DEFAULT = ONLY OLDEST ENTRY)

PROGRAM: UTFC MSG-INDX: -- UT.6 -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:




■ If an error is encountered with a top line BLDG command, this panel isreturned.

To exit:








INDEXName of the GDG index. Required field.

NUMBER OF ENTRIESNumber of entries to be kept in the GDG index. Required field. Numericwith maximum of 255.

DELETE WHEN FULLAction to be taken once ENTRIES value is exceeded. Enter A to delete allentries. Default is to delete only the oldest entry.

Usage Notes


This panel does not support VSAM or ICF catalogs because theIEHPROGM-type function uses an older form of catalog interface. Only CVOLcatalogs are supported at this time.

618 Commands Guide

UT.7 - Delete Index Panel


This panel deletes inactive indexes from the catalog.

� � ---------------------- CA-7 UTILITIES - DELETE INDEX ------------------------ FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

INDEX:(REQUIRED, FULL INDEX NAME)


PROGRAM: UTFH MSG-INDX: -- UT.7 -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:




■ If an error is encountered with a top line DLTX command, this panel isreturned.

To exit:








INDEXFully qualified name of the index to be deleted. Required field.

CVOLVOLSER of the catalog. If omitted, a standard catalog search, beginningwith SYSRES, is employed.

Usage Notes



620 Commands Guide

UT.8 - Connect a Catalog Panel


This panel connects high-level indexes from the SYSRES catalog to anothercatalog.

� � -------------------- CA-7 UTILITIES - CONNECT A CATALOG --------------------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

INDEX: (REQUIRED, HIGH LEVEL INDEX NAME IN UP TO 8 CHARACTERS)

VOLSER: (OPTIONAL, LEAVE BLANK TO DISPLAY EXISTING VOLSER)

PROGRAM: UTFE MSG-INDX: -- UT.8 -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:




■ If an error is encountered with a top line CONN command, this panel isreturned.

To exit:








INDEXHigh-level index name to be connected to SYSRES. Required.

VOLSERVOLSER of the connected volume. Connected volume must be available toUnicenter CA-7 through U7volser DD statement, top line ALLOC commandor function 11 on the UT Menu panel. Required.

Usage Notes



622 Commands Guide

UT.9 - Disconnect a Catalog Panel


This panel disconnects high-level indexes from the SYSRES catalog.

� � ------------------ CA-7 UTILITIES - DISCONNECT A CATALOG -------------------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

INDEX: (REQUIRED, HIGH LEVEL INDEX NAME IN UP TO 8 CHARACTERS)

PROGRAM: UTFF MSG-INDX: -- UT.9 -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:




■ If an error is encountered with a top line DCONN command, this panel isreturned.

To exit:








INDEXHigh-level index name to be disconnected from SYSRES. Required.

Usage Notes



624 Commands Guide

UT.10 - Find DSN on DASD Panel


This panel searches DASD volumes for copies of a given data set.

� � -------------------- CA-7 UTILITIES - FIND DSN ON DASD ----------------------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)


VOL1: VOL2: VOL3: VOL4: VOL5:( ALL = ALL AVAILABLE VOLUMES; REQUIRED)

PROGRAM: UTFL MSG-INDX: -- UT.1� -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:




■ If an error is encountered with a top line FIND command, this panel isreturned.

To exit:








DSNAMEFully qualified name of the data set. Required field.

VOL1

VOL2

VOL3

VOL4

VOL5Volume serial numbers that are to be searched for the data set. Enter ALLfor VOL1 to search all volumes. Each volume searched must be availableto Unicenter CA-7 through a U7volser DD statement, top line ALLOCcommand or function 11 on the UT Menu panel. Required.

Usage Notes


Up to 40 occurrences of the data set are shown in the body of the panel inVOLSER/YY.DDD format. The YY.DDD indicates the Julian date the data setwas created on for that particular VOLSER.

If more than 40 occurrences are found, a message indicates that is the case.To see more than the 40 occurrences listed on the panel, enter the request asa top line FIND command. A different display is returned listing eachoccurrence.

626 Commands Guide

UT.11 - Allocate Volume Panel


This panel allocates a DASD volume not defined by a U7xxxxxx DD statementin the Unicenter CA-7 JCL.

� � -------------------- CA-7 UTILITIES - ALLOCATE VOLUME ------------------------ FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

VOLSER: (REQUIRED)

UNIT NAME: (REQUIRED)

PROGRAM: UTFB MSG-INDX: -- UT.11 -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:




■ If an error is encountered with a top line ALLOC command, this panel isreturned.

To exit:








VOLSERVolume serial number. Required field.

UNIT NAMEUnit name of the DASD device on which the volume resides. Similar to thegeneric equivalent of a device code in the SASSUTBL table. For example,3350 or SYSDA. Required field.

Usage Notes


628 Commands Guide

UT.12 - Deallocate Volume Panel


This panel deallocates a DASD volume previously allocated with function 11 onthe UT Menu panel or with a top line ALLOC command.

� � -------------------- CA-7 UTILITIES - DEALLOCATE VOLUME --------------------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

VOLSER: (REQUIRED)

PROGRAM: UTFG MSG-INDX: -- UT.12 -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:




■ If an error is encountered with a top line DEALLOC command, this panel isreturned.

To exit:








VOLSERVolume serial number. Required field.

Usage Notes


630 Commands Guide

UT.13 - Display Format 1 DSCB Panel


This panel displays the Format 1 data set control block (DSCB) for a given dataset.

� � ------------------ CA-7 UTILITIES - DISPLAY FORMAT 1 DSCB -------------------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

DSNAME: (REQUIRED)


PROGRAM: UTFJ MSG-INDX: -- UT.13 -- YY.DDD / HH:MM:SS MESSAGE:

� �

The following display shows the VOLSER value even if it was not enteredoriginally. Below the two heading lines, the 101 bytes beginning at offset hex'2C' in the DSCB are shown in both hexadecimal and character form. ThePROGRAM value at the bottom of the panel indicates UTL1 since that moduleaccessed and formatted the DSCB information.



� � ------------------ CA-7 UTILITIES - DISPLAY FORMAT 1 DSCB -------------------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

DSNAME: SYS2.PROCLIB (REQUIRED)

VOLSER: 123456 (REQUIRED IF NOT CATALOGED)

DATASET CONTROL BLOCK INFORMATION:OFFSET -------------- H E X -------------- --- CHARACTER ----��2C F1��4 59��A5�� 156�144 ��1 �1...............��3C ��E2E3 D6C2C9F� F14�FF91 4�164D5A �..STOBI�1 .. ...��4C ��211�� 5446�2�� 9��C3� ��5�� ................��5C ��8�C�� 7E �6888�� 81��1 �................��6C 91��1 9A��E�� ................��7C �� ................�

��8C ��2 �1 �..... �

PROGRAM: UTL1 MSG-INDX: -- UT.13 -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:




■ If an error is encountered with a top line DMPDSCB command, this panel isreturned.

To exit:




632 Commands Guide





VOLSERVolume serial number on which the data set resides. Required if notcataloged.

Usage Notes

Press Enter when the fields have been completed. The panel returns with theMESSAGE field indicating what action was taken or any errors that occurred. Iffound, the DSCB is displayed in the body of the panel in hexadecimal andcharacter dump format.


UT.14 - Display Directory Info Panel


This panel displays information from a PDS directory block.

� � ----------------- CA-7 UTILITIES - DISPLAY DIRECTORY INFO -------------------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

DSNAME: (REQUIRED)

MEMBER: (OPTIONAL, START WITH THIS MEMBER)


PROGRAM: UTFM MSG-INDX: -- UT.14 -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:




■ If an error is encountered with a top line LISTDIR command, this panel isreturned.

To exit:




634 Commands Guide





MEMBERMember name with which to begin. If omitted, the entire directory is listed.


Usage Notes


If no errors occur, a different display is returned showing the desiredinformation.


UT.15 - Display Dataset Attributes Map Panel


This panel displays attributes of a DASD data set.

� � ------------- CA-7 UTILITIES - DISPLAY DATASET ATTRIBUTES MAP --------------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

DSNAME:(REQUIRED; SPECIFIC NAME, GENERIC NAME, RELATIVE GDG OR �)

VOLSER: (REQUIRED IF NOT CATALOGED, OMIT FOR RELATIVE GDG)

LIST: (A = ALL INFO, DEFAULT IS TERSE)

PROGRAM: UTFN MSG-INDX: -- UT.15 -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:




■ If an error is encountered with a top line MAP command, this panel isreturned.

To exit:




636 Commands Guide




DSNAMEFully qualified name of a data set, a generic data set name, a relative GDG,or * to indicate all data sets. A generic request is specified by an asteriskafter the last significant character in the name. VOLSER is also required fora generic request. Required.

VOLSERVolume serial number containing the data sets. Required for generic dataset names or if not cataloged.

LISTEnter A to list all information.

Default lists:

■ Data set name■ Number of extents■ Tracks allocated■ Tracks used■ Secondary allocation quantity■ DSORG■ RECFM■ LRECL■ BLKSIZE

Value of A also lists:

■ Creation date■ Expiration date■ Absolute DASD address■ Type of allocation■ Option code (OPTCD)■ Key length■ Key position■ Password indicators■ Unmovable indicators

Usage Notes




UT.16 - Display Available DASD Space Panel


This panel displays available space information for volumes available toUnicenter CA-7.

� � -------------- CA-7 UTILITIES - DISPLAY AVAILABLE DASD SPACE ----------------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

VOL1: VOL2: VOL3: VOL4: VOL5: (REQUIRED, ALL = ALL AVAILABLE VOLUMES)

PROGRAM: UTFQ MSG-INDX: -- UT.16 -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:




■ If an error is encountered with a top line SPACE command, this panel isreturned.

To exit:




638 Commands Guide




VOL1

VOL2

VOL3

VOL4

VOL5Volume serial numbers for which available space is to be listed. Enter ALLfor VOL1 to search all volumes. Each volume searched must be availableto Unicenter CA-7 through a U7volser DD statement, top line ALLOCcommand or function 11 on the UT Menu panel. Required.

Usage Notes




UT.17 - Display Physical Data Records Panel


This panel displays physical records from a given data set or a PDS directory.

� � -------------- CA-7 UTILITIES - DISPLAY PHYSICAL DATA RECORDS --------------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

DSNAME: (REQUIRED)

MEMBER: (PDS ONLY, DEFAULT IS TO LIST DIRECTORY)


RELATIVE RECORD NUMBER: (UP TO 4 DIGITS)

PROGRAM: UTFK MSG-INDX: -- UT.17 -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:




■ If an error is encountered with a top line DMPDSN command, this panel isreturned.

To exit:




640 Commands Guide





MEMBERName of a PDS member to be listed. Only valid for PDS. If omitted for aPDS, the directory is displayed.


RELATIVE RECORD NUMBERRelative record to be displayed. Default is 1 to indicate the first record inthe data set. Can be incremented on subsequent displays to progressthrough a complete data set.

Usage Notes




UT.18 - Display Catalog Block Panel


This panel displays the first catalog block for a given data set.

� � ------------------ CA-7 UTILITIES - DISPLAY CATALOG BLOCK -------------------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER)

DSNAME: (REQUIRED)


PROGRAM: UTFI MSG-INDX: -- UT.18 -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:




■ If an error is encountered with a top line DMPCAT command, this panel isreturned.

To exit:




642 Commands Guide




DSNAMEFully qualified name of the data set.

CVOLVOLSER of the catalog. Default is SYSRES.

Usage Notes




UT.19 - Display Catalog Entries Panel


This panel displays catalog entries for one or more data sets.

� � ----------------- CA-7 UTILITIES - DISPLAY CATALOG ENTRIES ------------------ FUNCTION ===> (LEAVE BLANK TO EXCEPT TO TRANSFER)

DSNAME:(REQUIRED; SPECIFIC NAME, GENERIC NAME OR RELATIVE GDG)

CVOL: (VOLSER OF CATALOG FROM WHICH TO DISPLAY;NOT NEEDED IF HIGH LEVEL IS IN MASTER)

PROGRAM: SLFA MSG-INDX: -- UT.19 -- YY.DDD / HH:MM:SS MESSAGE:

� �

To display, enter:




■ If an error is encountered with a top line LOC command, this panel isreturned.

To exit:




644 Commands Guide




DSNAMEFully qualified name of a data set, a generic data set or a relative GDG. Ageneric request is specified by the desired index levels followed by aperiod. Required.

CVOLIf high-level node is defined in the master catalog, this field should beomitted. Otherwise, use the volume serial number of the desired catalog.

Usage Notes



A generic request for data sets whose catalog entries are in the master catalogreceive the message that the data set is not found. This is a restriction of SVC26, which is used to process this command.


VERIFY

VERIFY

The VERIFY command establishes or satisfies a manual verificationrequirement for a currently scheduled run of the job in the request queue priorto its execution. A verification requirement is established for the currentlyscheduled run to ensure completion of some unusual activity prior to jobsubmission. Under ordinary circumstances, the database maintenance DB.1panel is used to establish a verification requirement through the VERIFY field.The #VER control statement can also be used for this purpose.

This function is available on the

■ “QM.1 CPU Jobs Status Prompt Panel” on page 505,

■ “QM.2 CPU Job Predecessors Prompt Panel” on page 516, and

■ “QM.3 CPU Job Attributes Prompt Panel” on page 521.


VERIFY

��──VERIFY─ ──,JOB=jobnumber ──,SET= ──┬ ┬─ON── ─────────────────────�� └ ┘─OFF─

JOBSpecifies the Unicenter CA-7 assigned job number of the job for which averification requirement is to be established or satisfied.


Required: Yes

SETSets the verification requirement.

Required: Yes

ONEstablishes a manual verification requirement that did not previouslyexist.

OFFIndicates a previously established manual verification requirement issatisfied and can be removed. A verification requirement no longerappears on the requirements list in the request queue.

646 Commands Guide

VERIFY

ExamplesVERIFY,JOB=163,SET=ON

VERIFY,JOB=163,SET=OFF


XPOST

XPOST

The XPOST top line command returns a panel that lists output network entriesfrom the postprocess queue. The panel that is returned allows you to updatethe panel information. Perform logging in by entering a function code for theappropriate panel entry and pressing Enter. See also “XSPOST” on page 662.

This function is available through “QM.7 Output Networks Prompt Panel” onpage 540.


XPOST XSPOST

��─ ──┬ ┬─XPOST── ──┬ ┬──────────────── ──┬ ┬────────────────────── ────�└ ┘─XSPOST─ └ ┘──,FILL=function │ │┌ ┐─�─────────


�─ ──┬ ┬──────────────────── ──┬ ┬───────────────────── ──────────────� │ │┌ ┐─�──────── │ │┌ ┐─�────────

└ ┘──,NW= ──┼ ┼─network── └ ┘──,STN= ──┼ ┼─station── └ ┘─network�─ └ ┘─station�─

�─ ──┬ ┬───────────────────── ─────────────────────────────────────�� │ │┌ ┐─�──────

└ ┘──,SUBID= ──┼ ┼─subid── └ ┘─subid�─

XPOSTLists output workstation network entries.

XSPOSTSame as XPOST, but abbreviates and lists twice as many entries on thepanel.

FILLIdentifies a character that is to be inserted in the function field thatprecedes each entry on the formatted panel when the panel is initiallyformatted for display. This facilitates performing the same function for manynetworks. For a discussion of the available values and how they are used,see “QM.7 Output Networks Prompt Panel” on page 540.

648 Commands Guide

XPOST

JOBIndicates the jobs for which the list of postprocess queue records is desired.Up to 17 entries are listed per panel for the XPOST command.

Default: *

Required: No

*Indicates all job names.



jobname*Indicates a generic job name.


jobnumberIndicates a specific Unicenter CA-7 job number or a range of jobnumbers specified as nnnn-nnnn.


NWIdentifies the networks for which records are to be listed.

Default: *

Required: No

*Indicates all networks.

networkIndicates a specific network name.


network*Indicates a generic type request.



XPOST

STNIdentifies the stations for which records are to be listed. The default is alllogical terminal names connected to the physical terminal that issued therequest. For example, logical terminals BALANCE and DECOLLAT areassigned to physical terminal HTERM1. If XPOST was entered fromHTERM1, all postprocess queue records for stations BALANCE andDECOLLAT would be displayed.

Default: *

Required: No

*Indicates all logical terminal names connected to the physical terminalwhere the XPOST command is entered.

stationIndicates a specific station name.


station*Indicates a generic type request.

SUBIDIdentifies the sub-IDs for which records are to be listed.

Default: *

Required: No

*Indicates all sub-IDs.

subidIndicates a specific sub-ID.


subid*Indicates a generic type request.


Usage Notes

Entries are not displayed if the previous station has not logged out or the workfor this station is complete.

The display continues to reflect the queue entries at the time of the initialrequest. It may be necessary to reissue the original request to get an updateddisplay.

650 Commands Guide

XPOST

ExamplesXPOST,STN=�

XSPOST,JOB=DUSAX�

XPOST,JOB=DUSAMRUN,FILL=I


XPRE

XPRE

The XPRE top line command returns a panel that lists Input Network entriesfrom the preprocess queue and allow the user to update that networkinformation. Logging in or logging out can be performed by entering a functioncode for the appropriate panel entry and pressing Enter. This command canalso be used for prompting workstations and interrupting and resuming anetwork. See also “XSPRE” on page 663.

This function is available through “QM.6 Input Networks Prompt Panel” onpage 533.


XPRE XSPRE

��─ ──┬ ┬─XPRE── ──┬ ┬──────────────── ──┬ ┬────────────────────── ─────�└ ┘─XSPRE─ └ ┘──,FILL=function │ │┌ ┐─�─────────


�─ ──┬ ┬──────────────────── ──┬ ┬───────────────────── ──────────────� │ │┌ ┐─�──────── │ │┌ ┐─�────────

└ ┘──,NW= ──┼ ┼─network── └ ┘──,STN= ──┼ ┼─station── └ ┘─network�─ └ ┘─station�─

�─ ──┬ ┬───────────────────── ─────────────────────────────────────�� │ │┌ ┐─�──────

└ ┘──,SUBID= ──┼ ┼─subid── └ ┘─subid�─

XPRELists input workstation network entries.

XSPRESame as XPRE, but abbreviates and lists twice as many entries on thepanel.

FILLIdentifies a character to be inserted in the function field that precedes eachentry on the formatted panel when the panel is initially formatted for display.This facilitates performing the same function for many networks. For adiscussion of the available values for FILL and how they are used, see“QM.6 Input Networks Prompt Panel” on page 533.

JOBIndicates the jobs for which the list of preprocess queue records is desired.Up to 17 entries are listed per panel for the XPRE panel.

Default: *

Required: No

652 Commands Guide

XPRE

*Indicates all job names in the preprocess queue.







NWIdentifies the networks for which records are to be listed.

Default: *

Required: No

*Indicates all networks.

networkIndicates a specific network name.


network*Indicates a generic type request.


STNIdentifies the stations for which records are to be listed. The default is alllogical terminal names connected to the physical terminal that issued therequest. For example, logical terminals KEYPUNCH and VERIFY areassigned to physical terminal HTERM1. If XPRE was entered fromHTERM1, all preprocess queue records for stations KEYPUNCH andVERIFY would be displayed.

Default: *

Required: No

*Indicates all logical terminal names.

stationIndicates a specific station name.



XPRE

station*Indicates a generic type request.


SUBIDIdentifies the sub-IDs for which records are to be listed.

Default: *

Required: No

*Indicates all sub-IDs.

subidIndicates a specific sub-ID.


subid*Indicates a generic type request.


Usage Notes

Entries are not displayed if the previous station has not logged out or the workfor this station is complete.

The display continues to reflect the queue entries at the time of the initialrequest. It may be necessary to reissue the original request to get an updateddisplay.

ExamplesXPRE,NW=KEYP�,FILL=C

XSPRE,JOB=TEST�

654 Commands Guide

XQ, XQJ, XQN, and XQM


The XQ, XQJ, XQN, and XQM commands display jobs in the request, ready oractive queues and allow the status of those jobs to be updated. The CANCEL,HOLD, RELEASE, and REQUEUE command functions, in addition to others,can also be performed on the XQ, XQJ, XQN, and XQM panels with a singlefunction character. It is also possible to transfer from any of these panels to theXRST panel if a job requires a restart. These commands are valid only fromonline 3270 type terminals. Each command provides a different displaysequence as follows:

XQLists the jobs in the order in which they occur in the queue.

XQJLists the jobs in job name sequence.

XQNLists the jobs in Unicenter CA-7 job number sequence.

XQMLists the jobs in job name sequence with a requirements summary.(LIST=ANY is the default for XQM. This is different from the other XQpanels where LIST=ALL is the default.)

Some requirements can be satisfied directly on these panels. Control can alsobe passed to other panels such as XRQ and XUPD, from which controlfunctions can be performed.

This function is available through “QM.1 CPU Jobs Status Prompt Panel” onpage 505.


XQ XQJ XQN XQM

��─ ──┬ ┬─XQ── ──┬ ┬──────────────── ──┬ ┬────────────────────── ───────�├ ┤─XQJ─ └ ┘──,FILL=function │ │┌ ┐─�─────────├ ┤─XQN─ └ ┘──,JOB= ──┼ ┼─jobname───

└ ┘─XQM─ ├ ┤─jobname�── └ ┘─jobnumber─

�─ ──┬ ┬─────────────── ──┬ ┬────────────── ──────────────────────────�└ ┘──,LIST=options │ │┌ ┐─REQ─

└ ┘──,Q= ──┼ ┼─RDY─ └ ┘─ACT─

�─ ──┬ ┬──────────────────── ──────────────────────────────────────��└ ┘──,SEQ= ──┬ ┬─ENTRY───

├ ┤─NUMBER── └ ┘─JOBNAME─



XQLists the jobs in the order in which they occur in the queue.

XQJLists the jobs in job name sequence.

XQNLists the jobs in Unicenter CA-7 job number sequence.

XQMLists the jobs in job name sequence with a requirements summary.

FILLIdentifies the character to be inserted in the function fields when theformatted panel is initially displayed. This option facilitates performing thesame function for many jobs. See “QM.1 CPU Jobs Status Prompt Panel”on page 505 for a discussion of the available values for FILL and how theyare used.

JOBIndicates the jobs for which information is to be listed from the request,ready, and active queues.

Default: *

Required: No

*Indicates all jobs.







LISTSpecifies the outstanding requirements selection criteria.

ALLList all jobs regardless of outstanding requirements. This is the defaultfor XQ, XQJ, and XQN.

ANYList only those jobs with at least one requirement. This is the default forXQM.

656 Commands Guide


BINTList only those jobs that have internal data set requirements, but nounsatisfied job requirements.

EXTList only those jobs with external data set requirements.

HLDList only those jobs with a hold requirement.

INTList only those jobs with internal data set requirements.

JCLOList only those jobs with a JCL override requirement.

JOBList only those jobs with job requirements.

NWKList only those jobs with network requirements.

RESTList only those jobs in restart status.

SKELList only those jobs in skeleton status.

SUBList only those jobs with submit-time requirements.

USRList only those jobs with user requirements.

VERList only those jobs with a verify requirement.

QIdentifies the queue for which jobs are to be listed.

Default: REQ

Required: No

ACTSpecifies the active queue.

RDYSpecifies the ready queue.

REQSpecifies the request queue.

SEQIndicates the sequence that the jobs should be listed in. You can use thisoption to change the default sequence for the XQM command (default is jobname sequence).



ENTRYLists jobs in the order in which they occur in the queue.

JOBNAMELists jobs in job name sequence.

NUMBERLists jobs in Unicenter CA-7 job number sequence.

Usage Notes

The XQ, XQJ, XQN, and XQM commands result in the QM.1-X panel displaywith the job name and Unicenter CA-7 job number listed for each job. See“QM.1-X CPU Jobs Status Panel” on page 509 for an example.

The XQM command results in the QM.1-M panel display with the job name anda summary of the outstanding requirements for each job. See “QM.1-M CPUJob Requirements” on page 511 for an example.

ExamplesXQ

XQ,JOB=DUSA�

XQJ

XQJ,Q=ACT

XQN

XQN,JOB=12-17,FILL=C

XQM,LIST=INT

658 Commands Guide

XREF

XREF

The XREF command indicates that all data set entries, network entries, or bothare to be analyzed for incomplete using-job references.


XREF

��──XREF─ ──┬ ┬──────────────── ──┬ ┬─────────────────── ────────────�� │ │┌ ┐─AL─ │ │┌ ┐─NO──

└ ┘──,TYPE= ──┼ ┼─DS─ └ ┘──,UPDATE= ──┴ ┴─YES─ └ ┘─NW─

TYPESpecifies the type of entries to be reviewed.

Default: AL

Required: No

ALIndicates both network and data set entries (ALL) are to be reviewed.

DSIndicates data set entries.

NWIndicates network entries.

UPDATESpecifies whether any updates are to be made to the database forincomplete references.

Default: NO

Required: No

NOSpecifies no updates are to be made to the database.

YESSpecifies updates are to be made to the database in addition to beinglisted.

Note: UPDATE=YES is valid only with TYPE=NW or TYPE=AL.


XRQ

XRQ

The XRQ command displays the requirements of a job in the request queue forpossible updating. This command is valid online only. Job requirements thathave been satisfied are shown with a prefix of X on the returned XRQ panel.Requirements can be posted or unposted with the panel.

The XRQ panel can be accessed from the XQ, XQJ, XQN, or XQM panels.

This function is available through “QM.2 CPU Job Predecessors Prompt Panel”on page 516.


XRQ

��──XRQ─ ──,JOB= ──┬ ┬─jobname─── ──┬ ┬─────────── ───────────────────��└ ┘─jobnumber─ └ ┘──,LIST=ALL

JOBIdentifies a request queue job for which requirements are to be listed.

Required: Yes

jobnameSpecifies a specific job name.


jobnumberSpecifies a Unicenter CA-7 job number.


LISTIf specified, all requirements are listed. Those that are satisfied are prefixedby an X.

Default: List only requirements not satisfied

Required: No

ExamplesXRQ,JOB=DUSAXX�1

XRQ,JOB=5,LIST=ALL

660 Commands Guide

XRST

XRST

The XRST top line command displays the restart (QM.4) panel for a particularjob. A job must be in restart status to use this panel. The user can initiallyschedule a job for restart processing using TYPE=RES on the DEMANDcommand.

The QM.4 panel can also be accessed from the XQ, XQJ, XQN, or XQM panel.

This function is available through “QM.4 CPU Job In Restart Status PromptPanel” on page 527 where the available functions are discussed.


XRST

��──XRST─ ──,JOB= ──┬ ┬─jobname─── ─────────────────────────────────�� └ ┘─jobnumber─

JOBIdentifies the job to be displayed.

Required: Yes





Usage Notes

When a job submitted by Unicenter CA-7 abends or terminates withunacceptable condition codes, it is automatically moved back to the requestqueue and flagged for restart. A RESTART requirement is placed on the job sothat this situation is acknowledged. All corrective actions such as catalogcleanup, JCL overrides, and so forth, should be done before the job isresubmitted. Many of the corrective actions can be handled by UnicenterCA-11, if the Unicenter CA-11 RMS step is in the job or inserted by UnicenterCA-7.

When Unicenter CA-11 is installed and the interface for automatic CMTupdating is installed, Unicenter CA-7 attempts to use the QM.4 panel fields toupdate the CMT directly before submitting the job. For information aboutinstalling the interface for Unicenter CA-11 and for more information aboutUnicenter CA-11, see the Interfaces Guide.


XSPOST

XSPOST

The XSPOST command has the same function as the QM.7 panel and theXPOST command. However, it lists up to 34 postprocess queue entries perpanel in "2-up" format. See “QM.7 Output Networks Prompt Panel” onpage 540 and the “XPOST” on page 648 for discussions of options and format.

662 Commands Guide

XSPRE

XSPRE

The XSPRE command has the same function as the QM.6 panel and the XPREcommand. However, it lists up to 34 preprocess queue entries per panel in"2-up" format. See “QM.6 Input Networks Prompt Panel” on page 533 and the“XPRE” on page 652 for discussions of options and format.


XUPD

XUPD

The XUPD command displays job type queue records for jobs in the requestqueue. This command is valid only from an online 3270 type terminal. Any ofthe job characteristics appearing on the panel can be modified by positioningthe cursor at the appropriate field and entering a new value. Updates are forone run only. They do not change information in the Unicenter CA-7 database.The characteristics displayed can be reviewed and/or permanently changedwith the DB.1 panel.

This function is available through “QM.3 CPU Job Attributes Prompt Panel” onpage 521.


XUPD

��──XUPD─ ──,JOB= ──┬ ┬─jobname─── ─────────────────────────────────�� └ ┘─jobnumber─

JOBIndicates the job to be listed from the request queue.

Required: Yes





Usage Notes

After the XUPD command is entered, a panel is returned showing the currentvalues for the job requested. See “QM.3 CPU Job Attributes Prompt Panel” onpage 521 for discussions of how to update the attributes for a job.

ExamplesXUPD,JOB=DUSAXX�1

XUPD,JOB=12

664 Commands Guide

XWLB

XWLB

The XWLB command, included in the workload balancing facility, makestemporary changes in selection parameters. You can view existing workloadbalancing values with the LWLB panel.


XWLB

��──XWLB────────────────────────────────────────────────────────��

The XWLB command has no keywords.

A formatted panel results from this command, displaying the currentparameters. Changes can be made by positioning the cursor to the desiredfield. These changes are only temporary. They remain in effect until eitheranother load module is called or they are changed again using this panel.Permanent changes to selection parameters require regeneration of themacros.

XWLB Panel (Defaults)

� � XWLB MOD: UCC7RDFL --CLASS BAR AND USE--

CL BAR USE CL BAR USE ----- INITIATORS ----- --------- TAPE DRIVES -------- A: 255 �� S: 255 �� TOT JOBS SUBMITTED �� NAME: TAPEDR1 TAPEDR2 B: 255 �� T: 255 �� TOT JOBS ACTIVE... �� CURR IN-USE...... �� C: 255 �� U: 255 �� TOT INITS AVAL.... �1� TOTAL AVAILABLE.. �1� �1� D: 255 �� V: 255 �� MIN JOBS MUST RUN. 255 MAX REWARD....... �2� �2� E: 255 �� W: 255 ��

MAX PENALTY...... �2� �2� F: 255 �� X: 255 �� --------- CPU -------- MIN DIFF-TO-SCHED �� G: 255 �� Y: 255 ��CURR %UTL/JOB ��.�� MAX DIFF-TO-SCHED �� H: 255 �� Z: 255 �� IDEAL %UTL/JOB ��8 MAX BOOST FOR DTS �� I: 255 �� : 255 �� MAX REWARD........ �2� MIN ALLOWABLE/JOB �� J: 255 �� 1: 255 �� MAX PENALTY....... �2� MAN ALLOWABLE/JOB 255 255 K: 255 �� 2: 255 ��

TOT MAX ALLOWABLE �12 �12 L: 255 �� 3: 255 �� ----- START TIME ----- M: 255 �� 4: 255 �� MAX REWARD........ �2� ----- THRESHOLD PRIORITY ----- N: 255 �� 5: 255 �� MAX PENALTY....... �2� DEFAULT THRESHOLD JOB PRTY 1�� O: 255 �� 6: 255 �� MAX LATE (HRS).... �12 SPECIAL CLASS #1 CL PRT P: 255 �� 7: 255 �� MAX EARLY(HRS).... �12 SPECIAL CLASS #2 CL PRT Q: 255 �� 8: 255 �� RUN TIME FACTOR... �1� SPECIAL CLASS #3 CL PRT R: 255 �� 9: 255 �� PROGRAM: QM6� MSG-INDEX: �� -- WB.X -- �5.��3 / 16:26:14 MESSAGE: CHANGE VALUES OR ENTER A COMMAND ON THE TOP LINE

� �


XWLB


MODDisplays the load module (definition) name. If changes have been madeafter the module is loaded it displays a message, CHANGED SINCELOADED, after the module name. No input is allowed for this field.

INITIATORSIndicates that the lines following this contain information about the initiators.No input is allowed for this field.

TOT JOBS SUBMITTEDIdentifies the total jobs submitted to the CPU at that time. For informationonly and no input is allowed. Always the same as TOT JOBS ACTIVE.

TOT JOBS ACTIVEIdentifies the total jobs running on the CPU. For information only and noinput is allowed. Always the same as TOT JOBS SUBMITTED.

TOT INITS AVALIdentifies the total initiators available for Unicenter CA-7 to submit jobs. Thisvalue corresponds to the TOTAV specification on the INITR macro. Valuemust be numeric and between 0 and 255. (See IDEAL %UTL/JOB.) A valueof 255 indicates there is not a limit.

MIN JOBS MUST RUNIdentifies the minimum number of jobs that Unicenter CA-7 submits withoutchecking the threshold priority. This value corresponds to the MNJOBspecification on the INITR macro. Must be numeric and between 0 and 255.

CPUIndicates that the lines following this contain information about CPU use. Noinput is allowed for this field.

CURR %UTL/JOBIdentifies the current percent of CPU use per job. For information only andno input is allowed.

IDEAL %UTL/JOBIdentifies the ideal percent of CPU use per job. Must be numeric andbetween 0 and 10. The product of this value and the value specified byTOT INITS AVAL must not be greater than 100. Corresponds to IDLUTspecification on CPU macro.

MAX REWARDIdentifies the maximum reward for CPU use. Corresponds to MXREW onCPU macro. Must be numeric and between 0 and 255.

MAX PENALTYIndicates the maximum penalty for CPU use. Corresponds to MXPEN onCPU macro. Must be numeric and between 0 and 255.

START TIMEIndicates the following lines contain information about the start time. Noinput is allowed for this field.

666 Commands Guide

XWLB

MAX REWARDIndicates the maximum reward for being late. Must be numeric andbetween 0 and 255. Corresponds to MXREW on STARTIME macro.

MAX PENALTYIndicates the maximum penalty for being early. Corresponds to MXPEN onSTARTIME macro. Must be numeric and between 0 and 255.

MAX LATE (HRS)Indicates the number of hours the job has to be late to gain the maximumreward. Corresponds to MXLAT on STARTIME macro. Must be numericand between 0 and 255.

MAX EARLY (HRS)Indicates the number of hours the job has to be early to gain the maximumpenalty. Corresponds to MXERL on STARTIME macro. Must be numericand between 0 and 255.

RUN TIME FACTORIndicates the value of the factor to be applied to the runtime of the job todetermine whether the job is to be considered late or early. Corresponds toRUNTF on STARTIME macro. Must be numeric and between 0 and 100.

TAPE DRIVESIndicates the lines following this contain information about TYPE1 andTYPE2 of tape drives. The first value is for TYPE1 and the second forTYPE2. The input fields under this heading relate to the specifications forthe TAPE1 and TAPE2 macros. No input is allowed for this field.

NAMEIndicates the names of the two types of tape drives. Corresponds to NAMEspecification. Must be alphanumeric, up to 8 characters.

CURR IN-USEIndicates the number of tape drives in use. This is for information only andno input is allowed.

TOTAL AVAILABLEIndicates the actual number of tape drives available to Unicenter CA-7controlled jobs. Corresponds to TOTAV. Must be numeric and between 0and 255.

MAX REWARDIndicates the maximum reward for tape drive use. Corresponds to MXREW.Must be numeric and between 0 and 255.

MAX PENALTYIndicates the maximum penalty for drive use. Corresponds to MXPEN. Mustbe numeric and between 0 and 255.

MIN DIFF-TO-SCHEDIndicates the minimum number of tape drives considered difficult toschedule. Corresponds to MNDTS. Must be numeric and between 0 and255.


XWLB

MAX DIFF-TO-SCHEDIndicates the maximum number of tape drives considered difficult toschedule. Corresponds to MXDTS. Must be numeric and between 0 and255.

MAX BOOST FOR DTSIndicates the maximum boost (additional reward) for difficult to schedulenumber of tape drives. Corresponds to MXBST. Must be numeric andbetween 0 and 255.

MIN ALLOWABLE/JOBIndicates the minimum number of tape drives a job must have to besubmitted. Corresponds to MNJAL. Must be numeric and between 0 and255.

MAX ALLOWABLE/JOBIndicates the maximum number of tape drives a job can have to besubmitted. Corresponds to MXJAL. Must be numeric and between 0 and255.

TOT MAX ALLOWABLEIndicates the number of tape drives Unicenter CA-7 is allowed to use forscheduling jobs. Corresponds to MXTAL. Must be numeric and between 0and 255.

THRESHOLD PRIORITYIndicates the lines following this contain information about the threshold jobpriority. No input is allowed for this field.

DEFAULT THRESHOLD JOB PRTYIndicates the threshold job priority for all classes given below. Correspondsto JPTHR on INITR macro. Must be numeric and between 0 and 255.

SPECIAL CLASS #1Indicates that this line of the panel contains information about special class#1 and corresponds to the SPCLS1 macro specification. No input is allowedfor this field.

SPECIAL CLASS # 2Indicates that this line of the panel contains information about special class#2 and corresponds to the SPCLS2 macro specification. No input is allowedfor this field.

SPECIAL CLASS # 3Indicates that this line of the panel contains information about special class#3 and corresponds to the SPCLS3 macro specification. No input is allowedfor this field.

CLIndicates the special class name. Must be a 1 character, alphanumericvalue.

PRTIndicates the threshold job priority for the special class. Must be numericand between 0 and 255.

668 Commands Guide

XWLB

CLASS BAR AND USEA title line. No input allowed for this field.

CL BAR USEA title line. No input allowed for this field.

AIndicates two values.

The first value indicates the number of jobs that can run simultaneouslyunder class A. This value corresponds to the BARA specification for theCLBARR macro. This value can be changed on the panel. Value must bebetween 0 and 255. A value of 255 indicates there is not a limit.

The second value is the number of jobs currently running in this class. Youcannot change this value.

B thru Z and 0 thru 9Same as above except for classes B through 9.


XWLB

670 Commands Guide

Index

Special Characters/commands

See alphabetical listing#statements

See alphabetical listing

Aacknowledging prompt 17, 20, 572activating

a terminal with Unicenter CA-7 86corequisite resources 16, 498

activating/deactivating workload balancingchanging selection parameters 665

active queuelisting with LACT command 276

active resources 16adding

entries to catalog 16, 155job requirements 16, 129text to log data set 12, 84to scheduled time 16, 19, 131

ADDRQ command 16, 129ADDSCH command 16, 19, 131adjusting schedules to advance processing 16, 596advance processing 16, 19, 596AL command 133, 606ALC command 133, 606ALLOC command 135, 627allocate

Dataset panel 606Volume panel 627

allocatingDASD data set 133volume 135

already loggedIn comment 268Out comment 272

alteringMAINID of job in queue 16, 174scheduling functions 16, 587security definition, CHANGE 52

APAgraph parameters 255menu panel 136top line command format 259

APG (Application Pool) 70application pool, display of 59AR.3 command 144ARF (Automated Recovery Facility)

defining ARF conditions 144dispatcher 587LARF Command, SASSSLIW 289LARFQ command 295

ARFP command 142Arithmetic symbols (syntax diagrams) 5ARTS command 143ASSIGN command 46AUTO command 48AUTO field 401Automated Recovery Facility

See ARF (Automated Recovery Facility)

Bbase calendars

identifier (SCAL) 560notational conventions 491

Batch Terminal Interface 39beginning workstation task 17, 265BLDG command 145, 617BRO command 50broadcast message 12, 50Build GDG Index panel 617building

database profile for new job 365Generation Data Group (GDG) index 145

bypassingnormal scheduling activities 578, 587scheduled processing cycles 16, 483

CCAICCI terminal interface 92calendars

CALMOD command 147listing 57PRINT command 491

CALMOD command 147CANCEL command 17, 20, 148CAT command 152, 609

Index 671

catalogDASD data set 133data set 16, 152, 155Dataset panel 609

CHANGE command 52changing

CPUs 174, 523MAINID of job in queue 16, 174, 523user's UID security level 125

changing selection parametersRESCHNG 556WLB 126XWLB 665

CLOSE command 54CMT updating 661Comma

repeat symbol, use in 8command

examples, keywords 45format 45

commandsADDRQ 16, 129ADDSCH 16, 19, 131AL 133, 606ALC 133, 606ALLOC 135, 627APA 136AR.3 144ARFP 142ARTS 143ASSIGN 46AUTO 48BLDG 145BRO 12, 50CALMOD 147CANCEL 17, 20, 148CAT 152, 609CHANGE 52CLOSE 12

function 12setting PF or PA key 102syntax and examples 54

CONN 154, 621COPY 12, 55CTLG 16, 155DB 160DCONN 162, 623DEALLOC 163, 629DEMAND

controlling schedules 16overview, syntax, and examples 164

commands (continued)DEMANDH 164DIRECT 16, 174DISPLAY 12, 57DLTX 176, 619DMDNW

and input network activities 266function 19syntax and examples 177

DMP1 72DMPCAT 179, 642DMPDSCB 180, 632DMPDSN 181, 640DRCLASS 73DRMODE 74DUMP 76EADMIN 77ECHO 12, 79EMAIL 80FALL 183FETCH 81FIND 187, 625FJOB 189FLOWD 195FLOWL 197FPOST 199FPRE 201FQALL 204FQJOB 208FQPOST 211FQPRE 213FQRES 215FQSTN 219FQTAPE 221FRES 223FRJOB 230FRQJOB 235FSTN 240FSTRUC 242FTAPE 245FWLP 248GRAPHc 255HELP 260HOLD

interrupting and resuming jobs 17interrupting and resuming networks 20syntax and examples 263

IN 17, 265IO 17, 19, 271JCL 82JCLOVRD 16, 274

672 Commands Guide

commands (continued)LACT 13, 276LACTR 15, 285LARF, List ARFSETs 289LARFQ, List ARF queue 295LCTLG 14, 19, 298LDSN 14, 305LDTM 310LIST 17, 316LISTDIR 319, 634LJCK 14, 321LJCL 14, 324LJES 13, 326LJOB

database contents inquiry 13syntax and examples 331

LJOBR 13, 15, 351LLIB 14, 353LLOCK 14, 355LNTWK 19, 359LOAD 363LOADH 363LOC 367, 644LOG 12, 84LOGIN 18, 368LOGOFF 12, 85, 101LOGON 12, 86, 101LOGOUT 19LPDS 14, 371LPOST 13, 19, 373LPRE 13, 19, 379LPROS

function 14syntax and examples 384

LPRRN 13, 389LQ 13, 16, 394LQP 15, 406LQR 15, 411LQUE 13, 394LQUEP 15, 406LQUER 15, 411LRDY 13, 416LRDYP 15, 423LRDYR 15, 427LREQ

queue inquiry 13syntax and examples 431

LREQP 15, 440LREQR 15, 442LRES 13, 446LRLOG 13, 19, 449

commands (continued)LRMD 15, 459LSCHD 14, 19, 462LSYS 13, 470LWLB 15, 473MAP 478, 636MENU 480MSG 12, 88MVS 90NOPRMP 17, 20, 481NXTCYC 16, 483NXTMSG 12, 91OPEN 92OPERID 94OPERIDS 95OUT 19, 485PA 12PAGE 12, 98PAnn 100PF 12PFnn 102POST 16, 487PRINT 491PRMP 17, 20, 493PROF 104PROFS 108PRRNJCL 495PRSCF 16, 496PRSQA 16, 498PRSQD 16, 499PS 500PURGPG 12, 111QJCL 16, 17, 501QM 503REFRESH 112RELEASE 17, 20, 546RELINK 113REMIND 17, 20, 548RENAME 550, 611REQUEUE 17, 551RESANL 554RESCHNG 556RESET 115RESOLV 558RESTART 17, 564RM 568RQMT 569RQVER 570RSVP 17, 20, 572RUN 16, 575

controlling schedules 16syntax and examples 575

Index 673

commands (continued)RUNH 16, 575RUNNW 19, 580RUSH 17, 20, 582SCHDMOD 583SCRATCH 584, 613SCRATCHP 584, 613SDESK 116SHUTDOWN 117SPACE 586, 638SSCAN 16, 587START 17, 120, 592STOP 17, 122, 593SUBMIT 16, 594SUBSCH 16, 19, 596SUBTM 16, 598SWAP 124TIQ 600TRIG 601UID 125UNC 603, 615UT 604VERIFY 16, 646WLB 126WTO 128XPOST 18, 648XPRE 18, 652XQ 16, 655XQJ 16, 655XQM 16, 655XQN 16, 655XREF 659XRQ 16, 660XRST 17, 661XSPOST 18, 662XSPRE 19, 663XUPD 16, 664XWLB 665

completion of workstation task 19, 368, 485component status 12, 57CONN command 154, 621connect a Catalog panel 621connecting high-level index 154consolidate entries in catalog 16, 155control statements

"#JCL" 274"#JI" 274"#JO" 274"#VER" 646"#XI" 274"#XO" 274

controlling job submission 16controlling schedules 16COPY command 55copying entries in catalog 155corequisite resources 16, 498CPU

changing with DIRECT command 174Job Attributes Prompt panel 521Job In Restart Status panel 528Job Predecessors Prompt panel 516Job Restart Status Prompt panel 527Job Status Prompt panel 505Jobs Status panel 509

creating processing schedules 558Critical Path Management (CPM)

FLOWD command 195FLOWL command 197

CTLG command 16, 155

DDASD

allocating with AL command 133dislaying attributes with UT.15 636listing attributes with MAP command 478log files 124

data set inquiries 14data sets

AllFusion CA-Librarian 353AllFusion CA-Panvalet 353listing with LCTLG command 298listing with LDSN command 305

database contents inquiry 13DB command 160DB.1 panel and VERIFY command 646DB.2.1 panel and RESOLV command 558DB.2.2 panel and RESOLV command 558DB.3.4 panel

and ADDRQ command 129and DMDW command 267

DCONN command 162, 623deactivating corequisite resources 16, 499deactivating workload balancing 126DEALLOC command 163, 629Deallocate Volume panel 629Default values (syntax diagrams) 9defining

ARF conditions 144postprocessing tasks 19preprocessing tasks 19

674 Commands Guide

delaying scheduled times 16, 19, 131Delete Index panel 619deleting

entries from catalog 16, 155flow elements 195index 176index from SYSRES catalog 162job from queue 17, 148output message pages 111scheduled workstation network from queue 20,

148Delimiters

syntax diagrams, use in 6DEMAND command

and database profiles 365and restart processing 661controlling schedules 16syntax and examples 164

DEMANDH commandand LOAD process 365moving from HOLD status 263syntax and examples 164

demandingjobs 164networks 177

DEMD field 401dependent jobs 569DIRECT command 16, 174disaster recovery class 73Disconnect a Catalog panel 623disconnecting high-level indexes 162dispatcher, ARF 587display

Available DASD Space panel 638Catalog Block panel 642Catalog Entries panel 644Dataset Attributes Map panel 636Directory Info panel 634Format 1 DSCB panel 631Physical Data Records panel 640

DISPLAY command 57displaying

active corequisite resources 16active resources 16catalog block 179CPU submit data set 57DASD space information 586data set

control block (DSCB) 180information 305record 181

displaying (continued)database documentation member

information 14, 384, 387database information 57directory record 181documentation 14, 387flows 197general status information 13, 276JES job number 13, 326job

requirements 16, 660restart panel 17, 661

jobsLSCHD command 462waiting on resources 16

jobs inactive queue 16, 17, 655ready queue 16, 17, 655request queue 16, 17, 655

logical terminal status 57networks 359, 379PF/PA key settings 57physical

record 181terminal status 57

records of job in request queue 16, 664schedule scan control values 57Unicenter CA-7 component status 12, 57

displays, sample 45DLTM comment 271, 273DLTX command 176, 619DMDNW command

and input network activities 266on-request scheduling 19syntax and examples 177

DMP1 command 72DMPCAT command 179, 642DMPDSCB command 180, 632DMPDSN command 181, 640DMPQ shutdown 117documentation

defining 384inquiries 14

DOTM comment 268, 269DRCLASS command 73DRMODE command 74due-out time for load processing 363DUMP command 76dynamic allocation 135

Index 675

EEADMIN command 77ECHO command 79echo input data 12, 79, 82EMAIL command 80email interface 77, 80email requests 80example commands, panels 45expediting job submission 16, 594

FFALL command 183FETCH command 81FETCH function, QM.5 panel 17, 502FETCHP function, QM.5 panel 532FIND command 187, 625Find DSN on DASD panel 625finding copies of data set 187FJOB command 189flag rush job 17, 20, 582FLOWD command 195FLOWL command 197forcing

immediate scheduling of CPU job 16, 164initiation of network 19, 580

forecast commandsSee also forecastingFALL 183FJOB 189FPOST 199FPRE 201FQALL 204FQJOB 208FQPOST 211FQPRE 213FQRES 215FQSTN 219FQTAPE 221FRES 223FRJOB 230FRQJOB 235FSTN 240FSTRUC 242FTAPE 245

forecastingSee also forecast commandsfrom the database 29job flow structures 35options 22

forecasting (continued)resources 36using FJOB command 189using FSTN command 240worksheets 39

format3270-type terminal 12blocks, RELINKing 58of commands 45

FORMAT statement 60FPOST command 199FPRE command 201FQALL command 204FQJOB command 208FQPOST command 211FQPRE command 213FQRES command 215FQSTN command 219FQTAPE command 221freeing

a resource 16shared or exclusive resource 496

FRES command 223FRJOB command 230FRQJOB command 235FSTN command 240FSTRUC command 242FTAPE command 245Function Menu panel 480FWLP command

format 248notes 252output 253

GGDG

adding 158BLDG command 145copying 159deleting 158index 145replacing 159UT.6 panel 617

generaloperating commands 12, 45status information 13, 276system commands 12

GRAPHc command 255GROUP statement

using with /CLOSE 54

676 Commands Guide

GROUP statement, initialization file 54

Hhalting movement of jobs to ready queue 593HELP

command 260tutorials 13, 260

HELP, graph directory 257high-level indexes in SYSRES catalog 154HOLD command

interrupting and resuming jobs 17interrupting and resuming networks 20syntax and examples 263

IIN command 18, 19, 265Incomplete using-job references

(see XREF command) 659index data set 16initialization file

/LOGON command 86LINE statement 58STATIONS statement 60

initiation of network, forced 19, 580Input Networks Prompt panel 533inquiry facility

Data set inquiries 14documentation inquiry 14HELP tutorials 13JCL inquiries 14JOB inquiries 13network data 19queue status inquiries 13reminder inquiries 14schedule inquiries 14Workload balancing inquiries 15workstation network inquiries 15

interfacesBrightStor CA-1 66CA-Driver 321Unicenter CA-11 529Unicenter CA-JCLCheck 321, 322

internal security definitions 94, 95interrupting

jobs 17networks 20scheduling activity 17, 263scheduling progress 17, 263

IO commandand task beginning time 18logging in and logging out 17, 19syntax and examples 271using with OUT command 486

issuing MVS operator commands 90

JJCL

command 82control statements 175inquiries 14override requirements 16, 274statements 82

JCLIDdemand processing 166load processing 364run processing 576

JCLLIBdemand processing 167load processing 364run processing 576

JCLOVRD command 16, 274JES3 environment, LOAD in 366JI statement 274JO statement 274Job

dependency, predecessor job requirements 569flow controlHeld comment 269inquiries 13Not Complete comment 269Purged comment 272requirement analysis, predecessor jobs 569requirements 16, 17, 487resource requirements 13, 15restart commands 17restart panel 17, 661submission process 16, 594

jobsalready run 389demanding 164displaying

LJOB command 331LQ command 394

forecasting 189on request 164restarting 527running 164

Index 677

KKEY parameter 57Keywords (syntax diagrams) 5

LLACT command

database contents inquiry 13queue contents inquiry 13syntax and examples 276

LACTR command 15, 285LARF command 289LARFQ command 295LCTLG command 14, 19, 298LDSN command 14, 305LDTM command 310LIST command 17, 316LISTDIR command 319, 634listing

active queue 276attributes of DASD data set 478base calendars 491catalog contents 367completed

job information 13, 19, 449workstation network information 13, 19, 449

data setelements that are locked 14, 355information 14, 298, 305

database information for application 13, 470JCL

for job 14, 324information for job 321

job informationfrom active queue 13, 276, 394from prior-run queue 13, 389from ready queue 13, 394, 416from request queue 13, 394, 431from run log 13, 449from the database 13, 331

job priority information 15, 431jobs waiting for restart 17, 316member of

AllFusion CA-Librarian data set 14, 353AllFusion CA-Panvalet data set 14, 353PDS 14, 371

output network informationfrom postprocess queue 13, 18, 20from preprocess queue 13, 18, 20from run log 19, 449from the database 19, 359

listing (continued)PDS

directory information 319member names 319

performance management information 15, 473postprocess queue 373preprocess queue 379reminder information 15, 17, 459resource requirements for jobs

in active queue 15, 285in database 13, 15, 351in queues 15, 411in queues or database 13, 15, 446in ready queue 15, 427in request queue 15, 442

resources and connected jobs 16schedule information 14, 19, 462sequential data set records 14, 305, 371user application data set information 14user profile 104, 108workload balancing information 15

LJCK command 14, 321LJCL command 14, 324LJES command 13, 326LJOB command, syntax and examples 331LJOBR command 13, 15, 351LLIB command 14, 353LLOCK command 14, 355LNTWK command

function 19syntax and examples 359

LOAD command 363LOAD process usage considerations 365LOADH command 363LOC command 367, 644LOG command 84log data set 84log data sets

swapping 124log data sets, adding to 12logging

in 19, 265out 19

logical terminals 46LOGIN command

and IN command 266and RSVP command 572function 18syntax and examples 368

LOGOFF commandlogging off Unicenter CA-7 85

678 Commands Guide

LOGOFF command (continued)return to VTAM 54

LOGON command 86LOGOUT command

and OUT command 266, 486and RSVP command 572and task ending times 18function 19syntax and examples 368

LPDS command 14, 371LPOST command

database contents inquiry 13obtaining reference number 265syntax and examples 373

LPRE commanddatabase contents inquiry 13obtaining reference number 265syntax and examples 379

LPROS command 14, 384displaying documentation 14

LPRRN commanddatabase contents inquiry 13queue contents inquiry 13syntax and examples 389

LQ commandfunction 16queue contents inquiry 13queue status inquiry 13syntax and examples 394

LQP command 15, 406LQR command 15, 411LQUE command 13, 394LQUEP command 15, 406LQUER command 15, 411LRDY command

queue contents inquiry 13queue status inquiry 13syntax and examples 416

LRDYP command 15, 423LRDYR command 15, 427LREQ command

queue contents inquiry 13queue status inquiry 13syntax and examples 431

LREQP command 15, 440LREQR command 15, 442LRES command 13, 15, 446LRLOG command

network inquiry 19queue contents inquiry 13syntax and examples 449

LRMD command 15, 459LSCHD command

network inquiry 19schedule inquiry 14syntax and examples 462

LSYS command 13, 470LWLB command 15, 473

Mmaintaining Unicenter CA-7 index data set 16, 155managing user profile 104, 108manual verification requirement 16, 646MAP command 478, 636menu

DB (database maintenance) 160function 480QM (queue maintenance) 503RM (resource management) 568UT (utilities) 604

MENU command 480Menu, APA 136modifying

email settings 77JCL in request queue 16, 17, 501job submission process 16, 594processing schedules 558records of job in request queue 16, 664schedule scan 16, 587scheduling activity 20, 263submit time-of-day 16, 598Unicenter CA-7 index data set 16, 155

month-by-month listing of base calendars 491moving jobs from ready or active queues to request

queue 17, 551MSG command 88MVS command 90

Nnetwork

Complete comment 272demanding 177displaying 379forced initiation of 19, 580processing 19, 177

nonprocessing days, base calendar 491NOPRMP command 17, 20, 481Not Logged In comment 486notifying system that

JCL override requirement satisfied 16, 274

Index 679

notifying system that (continued)job requirement satisfied 16, 487manual verification requirement satisfied 16, 646preexecution requirement satisfied 16, 487

NXTCYC command 16, 483NXTMSG command 91

Oon-request scheduling 19online utility panels

UT 604UT.1 606UT.10 625UT.11 627UT.12 629UT.13 631UT.14 634UT.15 636UT.16 638UT.17 640UT.18 642UT.19 644UT.2 609UT.3 611UT.4 613UT.5 615UT.6 617UT.7 619UT.8 621UT.9 623

OPEN command 92opening service desk requests 116OPERID command 94OPERIDS command 95OUT command 18, 19, 485Output Networks Prompt panel 540

PPA key

assignment 12, 100defaults 101listing 70

PAGE command 98panels, sample 45

sample of commands 45PAnn command 100Parameters, APA graph 255parameters, keywords 45

Parenthesessyntax diagrams, use in 6

password 86Personal Scheduling 500PF key

assignment 12, 102defaults 103listing 70

PFnn command 102placing job in request queue 16, 164POST command 16, 487posting ARF dispatcher with schedule scan 587posting satisfied job requirement 16, 487postprocess queue, listing 373postprocessing tasks 19predecessor requirements

dependency 569preexecution requirements

listing 416posting 16, 487

preprocess queue 379preprocessing tasks 19Prev Station Not Complete comment 269Preventing submission of jobs 593PRINT command 491prior-run JCL report 495prior-run queue

listing with LPRRN command 389PRRNJCL command 495

PRMP command 17, 20, 493processing days, base calendar 491producing month-by-month listing of base

calendars 491production control 19PROF command 104PROFS command 108Programs

commarepeat symbol, use in 8

parenthesessyntax diagrams, use in 6

punctuationsyntax diagrams, use in 5

SASSSLIW (LARF) 289SASSSLIY (LARFQ) 295

prompt response 17, 20, 572prompting commands 17, 19PRRNJCL command 495PRSCF command 16, 496PRSQA command 16, 498

680 Commands Guide

PRSQD command 16, 499PS command 500PS panel 500Punctuation marks (syntax diagrams) 5Purging output from logical terminal 111PURGPG command 111

QQ Analysis Incomplete comment 269QJCL command 16, 17, 501QJCL panel 17, 501QM panel 503QM.1 panel

and RSVP command 574and XQ, XQJ, XQN, and XQM commands 655sample and field descriptions 505

QM.2 paneland XRQ command 660panel and field descriptions 516posting user requirements with quotes,

parentheses, or commas 488QM.3 panel 481, 521QM.4 panel 527, 661QM.5 panel 17, 275, 531QM.6 panel 533, 652, 663QM.7 panel 540, 648, 662queue

See also queue maintenancecontents 13control commands 17QM panel 503status inquiries 13

queue maintenanceQM.1 panel 505QM.2 panel 516QM.3 panel 521QM.4 panel 527QM.5 panel 531QM.6 panel 533QM.7 panel 540

Queued JCL panel 531

Rready queue 416reassigning terminals and MAINIDs 46rebuilding profile for job whose JCL changed 365redirecting job 16, 174Ref Number Not Found comment 269

reference numberSee workstation network control

REFRESH command 112reinstating prompting 17, 20, 493reissue a command 48RELEASE command 17, 20, 546release volume 163RELINK command 113REMIND command 17, 20, 548reminder

inquiries 14messages 17, 20, 548

RENAMEcommand 550, 611Dataset panel 611

renaming a DASD data set 550repeating jobs 164, 172replacing entries in catalog 16, 155reporting

prior-run JCL (PRRNJCL) 495requirements (RQMT) 569trigger (TRIG) 601

request queue 431REQUEUE command 17, 551requirement control commands 16requirements

analysis, predecessor jobs 569report 569

RESANL command 554RESCHNG command 556RESET command 115resetting assigned job numbers 115RESOLV command 558Resource

management 16requirements 13, 15table, listing with /UID 125

resource analysis (tape drive) 554resource table 112

table, refreshing with /REFRESH 112responding to late status prompt 17, 572RESTART

command 17, 564facilities 551job awaiting restart in request queue 17, 564panel 17, 661

restoring access to terminals 92resuming

commandsinterrupting and resuming jobs 17

jobs 17

Index 681

resuming (continued)networks 20normal job flow 17, 592prompting 17, 20, 493scheduling activities 17, 546

returning to VTAM from Unicenter CA-7 12, 54reviewing

JCL in request or prior-run queues 16, 17, 501schedule scan options 16, 587

RM command 568ROLL field

resolving schedules 558RQMT command 569RQVER command 570RSVP command 17, 20, 572RUN command 16

controlling schedules 16syntax and examples 575

RUNH command 16, 263, 575controlling schedules 16syntax and examples 575

RUNNW command 19, 580RUSH command 17, 20, 582

Ssample commands, panels 45

panel results of commands 45SASSSLIW, LARF Command 289SASSSLIY, LARFQ Command 295satisfying

JCL override requirement 16, 274job requirements 16, 487manual verification requirement 16, 646preexecution job requirement 16, 487

SAVE command, text editor 274SCAL parameter 560

parameter 560SCHDMOD command 583schedule

control commands 16, 19immediate

job processing 16, 164network processing 19, 177

inquiries 14job without verifying requirements or performing

updates 16, 575reminder messages 17, 20, 548

schedule scancontrolling schedules with SSCAN 16posting ARF dispatcher 587

schedule scan (continued)SSCAN syntax and examples 587

scheduling activitiesinterrupting 17, 263modifying 20, 263resuming 17, 20, 546

SCRATCH command 584, 613Scratch Dataset panel 613Scratching DASD data set 584SCRATCHP command 584, 613SDESK command 116search DASD volumes for copies 187security

/LOGON command 86modifying operator 52

sendingdisplayed page 12, 56message to logical terminal 12, 88message to OS master console 128

service desk requests 116SHUTDOWN command 117simultaneous log in and log out 271SPACE command 586, 638SSCAN command 16, 587SSCN field 401START command 17, 120, 592start of workstation task 18, 368STOP command 17, 122, 593Submission process, modify 16, 594SUBMIT command 16, 594submit time-of-day, modify 16, 598SUBSCH command 16, 19, 596SUBTM command 16, 598subtract from scheduled time 16, 19, 596suspend

normal job flow 17, 593prompting 17, 481, 572

SWAP command 124Syntax diagrams

reading (how to) 5—10

Ttape drive resource analysis 554temporary JCL change commands 16, 501terminals

closing 54reassigning 46

TEST parameter 559text editor 274

682 Commands Guide

TIQ command 600top line

command format, APA 259commands 45graph commands 255

TRIG command 601trigger

See TRIG command

UUID

command 125resource table 112

UNC command 603, 615Uncatalog Dataset panel 615uncataloging data set 603Unicenter CA-11

and CANCEL command 151and RESTART command 564and XRST command 661

Unicenter Service Desk 112, 116updating records of job in request queue 16, 664user

commands 45profile listing 104, 108

UT command 604UT.1 panel 606UT.10 panel 625UT.11 panel 627UT.12 panel 629UT.13 panel 631UT.14 panel 634UT.15 panel 636UT.16 panel 638UT.17 panel 640UT.18 panel 642UT.19 panel 644UT.2 panel 609UT.3 panel 611UT.4 panel 613UT.5 panel 615UT.6 panel 617UT.7 panel 619UT.8 panel 621UT.9 panel 623Utilities Menu panel 604utility commands

AL 606ALC 606ALLOC 627

utility commands (continued)BLDG 617CAT 609CONN 621DCONN 623DEALLOC 629DLTX 619DMPCAT 642DMPDSCB 632DMPDSN 640FIND 625LISTDIR 634LOC 644MAP 636RENAME 611SCRATCH 613SCRATCHP 613SPACE 638UNC 615VERIFY 646

VVariables (syntax diagrams) 5VER statement 646verification requirement, manual 16, 646VERIFY command 16, 646verifying

JOB/DSN requirements for request queuejobs 570

pointer entries for triggers 601

WWLB command 126work flow control commands

functions 16job restart commands 17LOAD 363LOADH 363prompting commands 17queue control commands 17requirement control commands 16schedule control commands 16temporary JCL change commands 16, 501

workload balancing/WLB command 126inquiry commands 15

worksheets, forecasting 39workstation

network controlinquiries 19

Index 683

workstation (continued)network control (continued)

interrupting and resuming a network 20logging in 19logging out 19on-request scheduling 19prompting commands 20reference number 265, 271, 485schedule control commands 19

network inquiries 15tasks 18, 368, 485

workstation network controlWriting data to log data set 12, 84WTO command 128

XXI statement 274XO statement 274XPOST command 18, 648XPRE command 18, 20, 652XQ command 16, 655XQJ command 16, 655XQM command 16, 655XQN command 16, 655XREF command 659XRQ command 16, 660XRST command 17, 661XSPOST command 18, 20, 662XSPRE command 18, 20, 663XUPD command 16, 664XWLB command 665

YYEAR parameter 561

684 Commands Guide

unicenter ca-7 job management

Documents