CA Workload Automation CA 7® Edition: Command Reference Guide

CA Workload Automation
CA 7® Edition
Command Reference Guide

Version 12.0.00
Second Edition
This Documentation, which includes embedded help systems and electronically distributed materials (hereinafter referred to as
the “Documentation”), is for your informational purposes only and is subject to change or withdrawal by CA at any time. This
Documentation is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or
duplicated, in whole or in part, without the prior written consent of CA.
If you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make
available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with
that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.
The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable
license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to
certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “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 YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE,
DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST
INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE
POSSIBILITY OF SUCH LOSS OR DAMAGE.
The use of any software product referenced in the Documentation is governed by the applicable license agreement and such
license agreement is not modified in any way by the terms of this notice.
The manufacturer of this Documentation is CA.
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-7014(b)(3), as applicable, or
their successors.
Copyright © 2015 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to
their respective companies.
CA Technologies Product References
This document references the following CA Technologies products:
■ CA Workload Automation CA 7® Edition, (CA WA CA 7 Edition), formerly CA
Workload Automation SE and CA 7® Workload Automation
■ CA 1® Tape Management (CA 1)
■ CA Datacom/AD
■ CA Integrated Agent Services (CA IAS)
■ CA JCLCheck™ Workload Automation (CA JCLCheck )
■ CA Librarian®
■ CA OPS/MVS® Event Management and Automation (CA OPS/MVS EMA)
■ CA Panvalet® for z/OS
■ CA Roscoe®
■ CA Service Desk
■ CA Workload Automation Restart Option for z/OS Schedulers (CA WA Restart
Option), formerly CA 11™ Restart and Tracking
Contact CA Technologies
Contact CA Support
For your convenience, CA Technologies provides one site where you can access the
information that you need for your Home Office, Small Business, and Enterprise CA
Technologies products. At http://ca.com/support, you can access the following
resources:
■ Online and telephone contact information for technical assistance and customer
services
■ Information about user communities and forums
■ Product and documentation downloads
■ CA Support policies and guidelines
■ Other helpful resources appropriate for your product
Providing Feedback About Product Documentation
If you have comments or questions about CA Technologies product documentation, you

can send a message to [email protected].
To provide feedback about CA Technologies product documentation, complete our

short customer survey which is available on the CA Support website at
http://ca.com/docs.
Documentation Changes
The following documentation updates have been made since the last release of this
documentation:
■ /ASSIGN Command (see page 57)—Changes to the existing topic.
■ /DISPLAY Command (see page 74)—Changes to the Examples.
■ /OPERIDS Command (see page 124)—Changes to the Examples.
■ LAGENT Command (see page 312)—Changes to the Examples.
■ LJOB Command (see page 370)—Changes to the Examples.
■ PRSQA Command (see page 567)—Changes to the existing topic.
■ PRSQD Command (see page 568)—Changes to the existing topic.
Contents
Chapter 1: Introduction 21
Syntax Diagrams ......................................................................................................................................................... 21
Masking ...................................................................................................................................................................... 22
Commands ................................................................................................................................................................. 24
Long Online Commands ............................................................................................................................................. 24
Example ............................................................................................................................................................... 25
Long Job Names ......................................................................................................................................................... 26
Short Name Generation ...................................................................................................................................... 27
Long Job Name Rules .......................................................................................................................................... 27
General System Commands ....................................................................................................................................... 28
General Inquiry Facility .............................................................................................................................................. 29
Job Flow Control ......................................................................................................................................................... 32
Workstation Network Control .................................................................................................................................... 34
Forecasting ................................................................................................................................................................. 36
Forecast Facility................................................................................................................................................... 36
Forecasting from the Database ........................................................................................................................... 45
Forecasting from Queues .................................................................................................................................... 47
Forecasting Job Flow Structures ......................................................................................................................... 49
Forecasting Resources ........................................................................................................................................ 50
Forecasting Tape Requirements ......................................................................................................................... 51
CPU Job Worksheets ........................................................................................................................................... 53
Chapter 2: Commands 55
/AFM Command ......................................................................................................................................................... 55
/AGENT Command ..................................................................................................................................................... 55
Format 1 .............................................................................................................................................................. 55
Format 2 .............................................................................................................................................................. 56
/ASSIGN Command..................................................................................................................................................... 57
Format 1 .............................................................................................................................................................. 57
Format 2 .............................................................................................................................................................. 57
Format 3 .............................................................................................................................................................. 58
Usage Notes ........................................................................................................................................................ 59
Examples ............................................................................................................................................................. 59
/AUTO Command ....................................................................................................................................................... 59
Usage Notes ........................................................................................................................................................ 60
Examples ............................................................................................................................................................. 60
Contents 7
/BRO Command .......................................................................................................................................................... 61
Examples ............................................................................................................................................................. 62
/CHANGE Command ................................................................................................................................................... 62
Usage Notes ........................................................................................................................................................ 63
Example ............................................................................................................................................................... 63
/CHGOPT Command ................................................................................................................................................... 64
Usage Notes ........................................................................................................................................................ 67
Example ............................................................................................................................................................... 67
/CLOSE Command ...................................................................................................................................................... 67
Examples ............................................................................................................................................................. 68
/COID Commmand ..................................................................................................................................................... 69
Examples ............................................................................................................................................................. 69
/CONT Command ....................................................................................................................................................... 70
Usage Notes ........................................................................................................................................................ 70
Examples ............................................................................................................................................................. 71
/COPY Command ........................................................................................................................................................ 71
Usage Notes ........................................................................................................................................................ 71
Examples ............................................................................................................................................................. 72
/DELAGNT Command ................................................................................................................................................. 72
Example ............................................................................................................................................................... 73
/DISPLAY Command ................................................................................................................................................... 74
Examples ............................................................................................................................................................. 81
/DMP1 Command ..................................................................................................................................................... 100
/DRCLASS Command ................................................................................................................................................ 100
Examples ........................................................................................................................................................... 101
/DRMODE Command................................................................................................................................................ 101
Usage Notes ...................................................................................................................................................... 103
Examples ........................................................................................................................................................... 103
/DUMP Command .................................................................................................................................................... 103
Usage Notes ...................................................................................................................................................... 103
/EADMIN Command ................................................................................................................................................. 104
/ECHO Command ..................................................................................................................................................... 105
Usage Notes ...................................................................................................................................................... 105
Examples ........................................................................................................................................................... 106
/EMAIL Command .................................................................................................................................................... 106
/FETCH Command .................................................................................................................................................... 107
Usage Notes ...................................................................................................................................................... 107
/GVAR Command ..................................................................................................................................................... 108
/IAS Command ......................................................................................................................................................... 110
/JCL Command ......................................................................................................................................................... 112
/LOG Command ........................................................................................................................................................ 115
Usage Notes ...................................................................................................................................................... 115
8 Command Reference Guide

Examples ........................................................................................................................................................... 115
/LOGOFF Command ................................................................................................................................................. 116
/LOGON Command................................................................................................................................................... 116
Usage Notes ...................................................................................................................................................... 117
Example ............................................................................................................................................................. 118
/MSG Command ....................................................................................................................................................... 118
Usage Notes ...................................................................................................................................................... 119
Examples ........................................................................................................................................................... 119
/MVS Command ....................................................................................................................................................... 120
Example ............................................................................................................................................................. 120
Special Considerations ...................................................................................................................................... 120
/NXTMSG Command ................................................................................................................................................ 121
/OPEN Command ..................................................................................................................................................... 121
Format 1 ............................................................................................................................................................ 122
Format 2 ............................................................................................................................................................ 122
Examples ........................................................................................................................................................... 123
/OPERID Command .................................................................................................................................................. 123
Example ............................................................................................................................................................. 124
/OPERIDS Command ................................................................................................................................................ 124
Examples ........................................................................................................................................................... 125
/PAGE Command ...................................................................................................................................................... 126
Usage Notes ...................................................................................................................................................... 127
Examples ........................................................................................................................................................... 127
/PAnn Command ...................................................................................................................................................... 128
Usage Notes ...................................................................................................................................................... 128
Examples ........................................................................................................................................................... 129
/PFnn Command ...................................................................................................................................................... 129
Usage Notes ...................................................................................................................................................... 129
Examples ........................................................................................................................................................... 130
/PROF Command ...................................................................................................................................................... 130
Examples ........................................................................................................................................................... 132
Usage Notes ...................................................................................................................................................... 133
/PROFS Command .................................................................................................................................................... 134
Examples ........................................................................................................................................................... 136
Usage Notes ...................................................................................................................................................... 136
/PURGPG Command ................................................................................................................................................. 137
Usage Notes ...................................................................................................................................................... 137
Examples ........................................................................................................................................................... 137
/REFRESH Command ................................................................................................................................................ 138
/RELINK Command ................................................................................................................................................... 139
Format 1 ............................................................................................................................................................ 139
Format 2 ............................................................................................................................................................ 139
Contents 9
Usage Notes ...................................................................................................................................................... 140
Examples ........................................................................................................................................................... 140
/RESET Command ..................................................................................................................................................... 140
/SDESK Command .................................................................................................................................................... 141
/SHUTDOWN Command ........................................................................................................................................... 141
Usage Notes ...................................................................................................................................................... 142
/START Command .................................................................................................................................................... 143
Usage Notes ...................................................................................................................................................... 144
Examples ........................................................................................................................................................... 144
/STATEMGR Command............................................................................................................................................. 145
/STOP Command ...................................................................................................................................................... 146
Usage Notes ...................................................................................................................................................... 147
Examples ........................................................................................................................................................... 147
/SWAP Command ..................................................................................................................................................... 147
/UID Command......................................................................................................................................................... 147
Format 1 ............................................................................................................................................................ 147
Format 2 ............................................................................................................................................................ 148
Examples ........................................................................................................................................................... 148
/WLB Command ....................................................................................................................................................... 148
Format 1 ............................................................................................................................................................ 148
Format 2 ............................................................................................................................................................ 149
/WTO Command ...................................................................................................................................................... 150
Examples ........................................................................................................................................................... 151
/XCF Command......................................................................................................................................................... 151
Examples ........................................................................................................................................................... 152
/XTASK Command .................................................................................................................................................... 152
Examples ........................................................................................................................................................... 153
ADDRQ Command .................................................................................................................................................... 154
Usage Notes ...................................................................................................................................................... 155
Examples ........................................................................................................................................................... 155
ADDSCH Command .................................................................................................................................................. 155
Usage Notes ...................................................................................................................................................... 157
Examples ........................................................................................................................................................... 157
AGFILE Command ..................................................................................................................................................... 158
Example: AGFILE Command with LIST Option ................................................................................................... 162
Example: AGFILE Command Without LIST Option ............................................................................................ 165
Example: AGFILE Command with TYPE=FILELIST (for job type=AS400_JOB Only) ............................................ 168
AL/ALC Command .................................................................................................................................................... 170
Examples ........................................................................................................................................................... 171
ALLOC Command ...................................................................................................................................................... 171
Examples ........................................................................................................................................................... 172
APA Command ......................................................................................................................................................... 172

APA Menu ......................................................................................................................................................... 173
APA Prompt Panel ............................................................................................................................................. 173
ARFP Command ........................................................................................................................................................ 178
Example ............................................................................................................................................................. 178
ARTS Command ........................................................................................................................................................ 178
AR.3 Command ......................................................................................................................................................... 178
BLDG Command ....................................................................................................................................................... 179
Examples ........................................................................................................................................................... 179
CALMOD Command.................................................................................................................................................. 180
CANCEL Command ................................................................................................................................................... 180
Cancel Input Networks ...................................................................................................................................... 181
Cancel Request, Ready or Active Queue Jobs ................................................................................................... 181
Cancel Output Networks ................................................................................................................................... 182
Usage Notes ...................................................................................................................................................... 183
Examples ........................................................................................................................................................... 184
CAT Command .......................................................................................................................................................... 184
Usage Notes ...................................................................................................................................................... 185
Examples ........................................................................................................................................................... 186
CONN Command ...................................................................................................................................................... 186
Examples ........................................................................................................................................................... 186
CTLG Command ........................................................................................................................................................ 187
Usage Notes ...................................................................................................................................................... 189
Examples ........................................................................................................................................................... 189
Processing for TYPE=ADD .................................................................................................................................. 190
Processing for TYPE=DEL ................................................................................................................................... 190
Processing for TYPE=REPL ................................................................................................................................. 191
Processing for TYPE=COPY ................................................................................................................................ 191
Processing for TYPE=CON .................................................................................................................................. 191
DB Command ........................................................................................................................................................... 192
DCONN Command .................................................................................................................................................... 194
Examples ........................................................................................................................................................... 194
DEALLOC Command ................................................................................................................................................. 194
Examples ........................................................................................................................................................... 194
DEMAND, DEMANDH Command.............................................................................................................................. 195
Usage Notes ...................................................................................................................................................... 203
Examples ........................................................................................................................................................... 205
DIRECT Command .................................................................................................................................................... 205
Usage Notes ...................................................................................................................................................... 206
Examples ........................................................................................................................................................... 206
DLTX Command ........................................................................................................................................................ 207
Usage Notes ...................................................................................................................................................... 207
Examples ........................................................................................................................................................... 207
Contents 11
DMDNW Command .................................................................................................................................................. 208
Usage Notes ...................................................................................................................................................... 209
Examples ........................................................................................................................................................... 209
DMPCAT Command .................................................................................................................................................. 210
Examples ........................................................................................................................................................... 210
DMPDSCB Command ................................................................................................................................................ 211
Examples ........................................................................................................................................................... 211
DMPDSN Command ................................................................................................................................................. 211
Examples ........................................................................................................................................................... 212
FALL Command ......................................................................................................................................................... 213
Examples ........................................................................................................................................................... 215
FIND Command ........................................................................................................................................................ 217
Examples ........................................................................................................................................................... 217
FJOB Command ........................................................................................................................................................ 218
Usage Notes ...................................................................................................................................................... 220
Examples ........................................................................................................................................................... 220
FLOWD Command .................................................................................................................................................... 224
Usage Notes ...................................................................................................................................................... 225
FLOWL Command ..................................................................................................................................................... 225
Examples ........................................................................................................................................................... 226
FPOST Command ...................................................................................................................................................... 227
Examples ........................................................................................................................................................... 228
FPRE Command ........................................................................................................................................................ 229
Examples ........................................................................................................................................................... 229
FQALL Command ...................................................................................................................................................... 231
Examples ........................................................................................................................................................... 232
FQJOB Command...................................................................................................................................................... 234
Examples ........................................................................................................................................................... 237
FQPOST Command ................................................................................................................................................... 238
Examples ........................................................................................................................................................... 239
FQPRE Command ..................................................................................................................................................... 239
Examples ........................................................................................................................................................... 240
FQRES Command ...................................................................................................................................................... 241
Examples ........................................................................................................................................................... 243
FQSTN Command ..................................................................................................................................................... 243
Examples ........................................................................................................................................................... 244
FQTAPE Command ................................................................................................................................................... 245
Examples ........................................................................................................................................................... 246
FRES Command ........................................................................................................................................................ 247
Examples ........................................................................................................................................................... 250
FRJOB Command ...................................................................................................................................................... 252
Examples ........................................................................................................................................................... 254

Usage Notes ...................................................................................................................................................... 254
FRQJOB Command ................................................................................................................................................... 257
Examples ........................................................................................................................................................... 258
Usage Notes ...................................................................................................................................................... 258
FSTN Command ........................................................................................................................................................ 261
Examples ........................................................................................................................................................... 262
FSTRUC Command .................................................................................................................................................... 263
Examples ........................................................................................................................................................... 265
FTAPE Command ...................................................................................................................................................... 265
Examples ........................................................................................................................................................... 268
FWLP Command ....................................................................................................................................................... 269
FWLP Notes ....................................................................................................................................................... 273
FWLP Output ..................................................................................................................................................... 274
GRAPHc Command ................................................................................................................................................... 275
Format 1 ............................................................................................................................................................ 276
Format 2 ............................................................................................................................................................ 276
Examples ........................................................................................................................................................... 278
Usage Notes ...................................................................................................................................................... 279
HELP Command ........................................................................................................................................................ 280
HELP Panel ........................................................................................................................................................ 280
HOLD Command ....................................................................................................................................................... 282
Usage Notes ...................................................................................................................................................... 283
Examples ........................................................................................................................................................... 284
IN Command ............................................................................................................................................................ 284
Input Networks ................................................................................................................................................. 285
Output Networks .............................................................................................................................................. 286
IN Command Response ..................................................................................................................................... 287
Examples ........................................................................................................................................................... 290
IO Command ............................................................................................................................................................ 291
IO Command Response ..................................................................................................................................... 292
Examples ........................................................................................................................................................... 294
JCLOVRD Command.................................................................................................................................................. 294
Usage Notes ...................................................................................................................................................... 295
Examples ........................................................................................................................................................... 296
JOBSTART Command ................................................................................................................................................ 296
Examples ........................................................................................................................................................... 296
JRENAME Command................................................................................................................................................. 297
Usage Notes ...................................................................................................................................................... 298
Example ............................................................................................................................................................. 298
LACT Command ........................................................................................................................................................ 299
Examples ........................................................................................................................................................... 304
LACTR Command ...................................................................................................................................................... 307
Contents 13
Examples ........................................................................................................................................................... 311
LAGENT Command ................................................................................................................................................... 312
Examples ........................................................................................................................................................... 313
LARF Command ........................................................................................................................................................ 319
Examples ........................................................................................................................................................... 320
LARFQ Command ..................................................................................................................................................... 326
Examples ........................................................................................................................................................... 327
LCTLG Command ...................................................................................................................................................... 329
Examples ........................................................................................................................................................... 330
LDSN Command........................................................................................................................................................ 337
Examples ........................................................................................................................................................... 339
LDTM Command ....................................................................................................................................................... 343
Usage Notes ...................................................................................................................................................... 348
Examples ........................................................................................................................................................... 349
LGVAR Command ..................................................................................................................................................... 351
Examples ........................................................................................................................................................... 352
LIST Command .......................................................................................................................................................... 355
Examples ........................................................................................................................................................... 356
LISTDIR Command .................................................................................................................................................... 358
Examples ........................................................................................................................................................... 359
LJCK Command ......................................................................................................................................................... 359
LJCL Command ......................................................................................................................................................... 363
Examples ........................................................................................................................................................... 364
LJES Command ......................................................................................................................................................... 365
Usage Notes ...................................................................................................................................................... 367
Examples ........................................................................................................................................................... 368
LJOB Command ........................................................................................................................................................ 370
Examples ........................................................................................................................................................... 386
LJOBR Command ...................................................................................................................................................... 400
Usage Notes ...................................................................................................................................................... 400
Examples ........................................................................................................................................................... 400
LLIB Command.......................................................................................................................................................... 402
Examples ........................................................................................................................................................... 403
LLOCK Command ...................................................................................................................................................... 404
Required Action for a Locked Job ...................................................................................................................... 405
Suspended Scheduling Messages ...................................................................................................................... 405
Examples ........................................................................................................................................................... 406
LNODE Command ..................................................................................................................................................... 406
Examples ........................................................................................................................................................... 408
LNTWK Command .................................................................................................................................................... 409
Examples ........................................................................................................................................................... 410
LOAD, LOADH Command .......................................................................................................................................... 412

Examples ........................................................................................................................................................... 415
Usage Notes ...................................................................................................................................................... 415
LOC Command .......................................................................................................................................................... 417
Usage Notes ...................................................................................................................................................... 417
Examples ........................................................................................................................................................... 417
LOGIN, LOGOUT Commands .................................................................................................................................... 417
Input Workstation Networks............................................................................................................................. 418
Output Workstation Networks.......................................................................................................................... 419
LPDS Command ........................................................................................................................................................ 421
Examples ........................................................................................................................................................... 422
LPOST Command ...................................................................................................................................................... 423
Examples ........................................................................................................................................................... 426
LPRE Command ........................................................................................................................................................ 428
Examples ........................................................................................................................................................... 431
LPROS Command ...................................................................................................................................................... 433
Usage Notes ...................................................................................................................................................... 436
Examples ........................................................................................................................................................... 436
LPRRN Command ..................................................................................................................................................... 437
Examples ........................................................................................................................................................... 441
LQ Command ............................................................................................................................................................ 443
Examples ........................................................................................................................................................... 450
ARF Information Section Messages................................................................................................................... 460
LQP Command .......................................................................................................................................................... 462
Examples ........................................................................................................................................................... 466
Usage Notes ...................................................................................................................................................... 467
LQR Command.......................................................................................................................................................... 468
Examples ........................................................................................................................................................... 473
LRDY Command ........................................................................................................................................................ 474
Examples ........................................................................................................................................................... 479
LRDYP Command ...................................................................................................................................................... 482
Examples ........................................................................................................................................................... 485
Usage Notes ...................................................................................................................................................... 486
LRDYR Command ...................................................................................................................................................... 487
Examples ........................................................................................................................................................... 491
LREQ Command ........................................................................................................................................................ 492
Examples ........................................................................................................................................................... 498
LREQP Command ...................................................................................................................................................... 503
Examples ........................................................................................................................................................... 506
LREQR Command ..................................................................................................................................................... 507
Examples ........................................................................................................................................................... 511
LRES Command ........................................................................................................................................................ 512
Examples ........................................................................................................................................................... 514
Contents 15
LRLOG Command ..................................................................................................................................................... 515
Examples ........................................................................................................................................................... 521
LRMD Command ...................................................................................................................................................... 526
Examples ........................................................................................................................................................... 527
LSCHD Command...................................................................................................................................................... 528
Examples ........................................................................................................................................................... 531
LSYS Command ......................................................................................................................................................... 536
Examples ........................................................................................................................................................... 537
LWLB Command ....................................................................................................................................................... 539
Examples ........................................................................................................................................................... 540
LXCF Command ........................................................................................................................................................ 545
Examples ........................................................................................................................................................... 545
MAP Command ........................................................................................................................................................ 546
Usage Notes ...................................................................................................................................................... 547
Examples ........................................................................................................................................................... 547
MENU Command ...................................................................................................................................................... 548
NOPRMP Command ................................................................................................................................................. 549
Usage Notes ...................................................................................................................................................... 550
Examples ........................................................................................................................................................... 550
NXTCYC Command ................................................................................................................................................... 550
Usage Notes ...................................................................................................................................................... 552
Examples ........................................................................................................................................................... 553
OUT Command ......................................................................................................................................................... 553
Usage Notes ...................................................................................................................................................... 554
Examples ........................................................................................................................................................... 555
POST Command ........................................................................................................................................................ 555
Usage Notes ...................................................................................................................................................... 557
Examples ........................................................................................................................................................... 558
PRINT Command ...................................................................................................................................................... 559
Usage Notes ...................................................................................................................................................... 560
Example ............................................................................................................................................................. 560
PRMP Command ...................................................................................................................................................... 562
Usage Notes ...................................................................................................................................................... 563
Examples ........................................................................................................................................................... 563
PRRNDEL Command ................................................................................................................................................. 563
Examples ........................................................................................................................................................... 564
PRRNJCL Command .................................................................................................................................................. 565
Examples ........................................................................................................................................................... 565
PRSCF Command ...................................................................................................................................................... 566
Example ............................................................................................................................................................. 567
PRSQA Command ..................................................................................................................................................... 567
Example ............................................................................................................................................................. 568

PRSQD Command ..................................................................................................................................................... 568
Example ............................................................................................................................................................. 569
PS Command ............................................................................................................................................................ 569
QJCL Command ........................................................................................................................................................ 570
Usage Notes ...................................................................................................................................................... 571
QM Command .......................................................................................................................................................... 572
Usage Notes ...................................................................................................................................................... 572
PF Keys .............................................................................................................................................................. 573
QM.1 CPU Jobs Status Prompt Panel ....................................................................................................................... 573
QM.1-X CPU Jobs Status Panel .......................................................................................................................... 577
QM.1-M CPU Job Requirements ....................................................................................................................... 579
QM.1-XC Reason for Cancel Panel .................................................................................................................... 581
QM.2 CPU Job Predecessors Prompt Panel.............................................................................................................. 583
QM.2-X CPU Job Predecessors .......................................................................................................................... 584
QM.3 CPU Job Attributes Prompt Panel................................................................................................................... 587
QM.3-X CPU Job Attributes ............................................................................................................................... 588
QM.3-X XPJOB Job Attributes............................................................................................................................ 592
QM.3-X AGJOB Job Attributes ........................................................................................................................... 594
QM.4 CPU Job In Restart Status Prompt Panel ........................................................................................................ 597
QM.4-X CPU Job In Restart Status ..................................................................................................................... 598
QM.5 Queued JCL Panel ........................................................................................................................................... 601
QM.6 Input Networks Prompt Panel ........................................................................................................................ 603
QM.6-X Input Networks (1-Up Display) ............................................................................................................ 605
QM.6-S Input Networks (2-Up Display) ............................................................................................................. 608
QM.7 Output Networks Prompt Panel ..................................................................................................................... 610
QM.7-X Output Networks (1-Up Display).......................................................................................................... 612
QM.7-S Output Networks (2-Up Display) .......................................................................................................... 615
RELEASE Command .................................................................................................................................................. 617
Usage Notes ...................................................................................................................................................... 618
Examples ........................................................................................................................................................... 619
REMIND Command................................................................................................................................................... 619
Usage Notes ...................................................................................................................................................... 620
Examples ........................................................................................................................................................... 620
RENAME Command .................................................................................................................................................. 621
Examples ........................................................................................................................................................... 621
REPLY Command ...................................................................................................................................................... 622
Examples ........................................................................................................................................................... 622
Usage Notes ...................................................................................................................................................... 622
REQUEUE Command ................................................................................................................................................ 623
Usage Notes ...................................................................................................................................................... 626
Examples ........................................................................................................................................................... 627
RESANL Command .................................................................................................................................................... 627
Contents 17
RESCHNG Command ................................................................................................................................................ 628
Usage Notes ...................................................................................................................................................... 629
Examples ........................................................................................................................................................... 630
RESOLV Command .................................................................................................................................................... 630
Usage Notes ...................................................................................................................................................... 635
Examples ........................................................................................................................................................... 636
RESTART Command .................................................................................................................................................. 637
RM Command........................................................................................................................................................... 641
RQVER Command ..................................................................................................................................................... 642
RSVP Command ........................................................................................................................................................ 643
Usage Notes ...................................................................................................................................................... 645
Examples ........................................................................................................................................................... 645
RUN, RUNH Command ............................................................................................................................................. 645
Usage Notes ...................................................................................................................................................... 650
Examples ........................................................................................................................................................... 651
RUNNW Command ................................................................................................................................................... 651
Usage Notes ...................................................................................................................................................... 652
Examples ........................................................................................................................................................... 653
RUSH Command ....................................................................................................................................................... 653
SCHDMOD Command ............................................................................................................................................... 654
SCRATCH Command ................................................................................................................................................. 655
Usage Notes ...................................................................................................................................................... 655
Examples ........................................................................................................................................................... 656
SPACE Command ...................................................................................................................................................... 656
Examples ........................................................................................................................................................... 657
SSCAN Command ..................................................................................................................................................... 657
Usage Notes ...................................................................................................................................................... 661
Examples ........................................................................................................................................................... 662
START Command ...................................................................................................................................................... 662
Examples ........................................................................................................................................................... 663
STOP Command ........................................................................................................................................................ 663
Usage Notes ...................................................................................................................................................... 663
Examples ........................................................................................................................................................... 664
SUBMIT Command ................................................................................................................................................... 664
Examples ........................................................................................................................................................... 665
SUBSCH Command ................................................................................................................................................... 665
Usage Notes ...................................................................................................................................................... 666
Examples ........................................................................................................................................................... 667
SUBTM Command .................................................................................................................................................... 667
Examples ........................................................................................................................................................... 668
TIQ Command .......................................................................................................................................................... 668
UNC Command ......................................................................................................................................................... 668

Examples ........................................................................................................................................................... 668
UT Command ............................................................................................................................................................ 669
Usage Notes ...................................................................................................................................................... 670
PF Keys .............................................................................................................................................................. 670
UT.1 - Allocate/Catalog Dataset Panel ..................................................................................................................... 671
Usage Notes ...................................................................................................................................................... 673
UT.2 - Catalog Dataset Panel .................................................................................................................................... 673
Usage Notes ...................................................................................................................................................... 675
UT.3 - Rename Dataset Panel ................................................................................................................................... 675
Usage Notes ...................................................................................................................................................... 676
UT.4 - Scratch Dataset Panel .................................................................................................................................... 677
Usage Notes ...................................................................................................................................................... 678
UT.5 - Uncatalog Dataset Panel ................................................................................................................................ 678
Usage Notes ...................................................................................................................................................... 679
UT.6 - Build GDG Index Panel ................................................................................................................................... 680
Usage Notes ...................................................................................................................................................... 681
UT.7 - Delete Index Panel ......................................................................................................................................... 681
Usage Notes ...................................................................................................................................................... 682
UT.8 - Connect a Catalog Panel ................................................................................................................................ 683
Usage Notes ...................................................................................................................................................... 684
UT.9 - Disconnect a Catalog Panel ............................................................................................................................ 685
Usage Notes ...................................................................................................................................................... 686
UT.10 - Find DSN on DASD Panel .............................................................................................................................. 686
Usage Notes ...................................................................................................................................................... 687
UT.11 - Allocate Volume Panel ................................................................................................................................. 688
Usage Notes ...................................................................................................................................................... 689
UT.12 - Deallocate Volume Panel ............................................................................................................................. 690
Usage Notes ...................................................................................................................................................... 691
UT.13 - Display Format 1 DSCB Panel ....................................................................................................................... 691
Usage Notes ...................................................................................................................................................... 692
Examples ........................................................................................................................................................... 693
UT.14 - Display Directory Info Panel ........................................................................................................................ 694
Usage Notes ...................................................................................................................................................... 695
UT.15 - Display Dataset Attributes Map Panel ......................................................................................................... 695
Usage Notes ...................................................................................................................................................... 697
UT.16 - Display Available DASD Space Panel ............................................................................................................ 698
Usage Notes ...................................................................................................................................................... 699
UT.17 - Display Physical Data Records Panel............................................................................................................ 700
Usage Notes ...................................................................................................................................................... 701
UT.18 - Display Catalog Block Panel ......................................................................................................................... 702
Usage Notes ...................................................................................................................................................... 703
UT.19 - Display Catalog Entries Panel....................................................................................................................... 704
Contents 19
Usage Notes ...................................................................................................................................................... 705
VERIFY Command ..................................................................................................................................................... 705
Examples ........................................................................................................................................................... 706
XPOST Command...................................................................................................................................................... 706
Usage Notes ...................................................................................................................................................... 709
Examples ........................................................................................................................................................... 709
XPRE Command ........................................................................................................................................................ 709
Usage Notes ...................................................................................................................................................... 712
Examples ........................................................................................................................................................... 712
XQ, XQJ, XQN, and XQM Commands ........................................................................................................................ 712
Usage Notes ...................................................................................................................................................... 716
Examples ........................................................................................................................................................... 717
XRQ Command ......................................................................................................................................................... 717
Examples ........................................................................................................................................................... 718
XRST Command ........................................................................................................................................................ 718
XSPOST Command ............................................................................................................................................. 719
XSPRE Command ...................................................................................................................................................... 719
XUPD Command ....................................................................................................................................................... 719
Usage Notes ...................................................................................................................................................... 720
Examples ........................................................................................................................................................... 720
XWLB Command ....................................................................................................................................................... 721

Chapter 1: Introduction
The Command Reference Guide is intended as a reference guide for production and
operations personnel. The guide is also intended for users with scheduling and
operations responsibilities using CA Workload Automation CA 7® Edition (CA WA CA 7
Edition). This guide describes the following:
■ General system commands
■ Workstation network commands
■ Workload balancing commands
■ Forecasting
■ General inquiry facilities
■ Work flow control
■ Online system
■ Interface utilities
This section contains the following topics:

Syntax Diagrams (see page 21)
Masking (see page 22)
Commands (see page 24)
Long Online Commands (see page 24)
Long Job Names (see page 26)
General System Commands (see page 28)
General Inquiry Facility (see page 29)
Job Flow Control (see page 32)
Workstation Network Control (see page 34)
Forecasting (see page 36)
Syntax Diagrams
The syntax diagrams in this guide use the following conventions:
Notation Meaning
Quote marks " or ' Must be entered as shown.
Comma , Must be entered as shown.
Ellipsis ... The operand can be repeated. Do not enter ellipsis.
Masking
Notation Meaning
Lowercase italics Substitute an operand. A user-supplied variable or
character string.
Uppercase operand Spell the operand as shown.
OR-bar (|) Indicates an exclusive value on right or left of bar. You
must enter enter one of them. You cannot enter more
than one.
Underline ____________ If you do not enter one of the operands, the system
supplies the underlined operand. This value is the
default.
Parentheses ( ) and special Operand enclosed in parentheses is mandatory and
characters must be entered as shown.
Single operand in square Optional operand. Do not type the brackets.
brackets
[]
Stacked operands in braces Mandatory. You must enter one of the operands. You
{} cannot enter more than one.
{}
Stacked operands in square Optional operand. You can enter one value, or none.
brackets
[]
[]
Operands with OR-bars (|) Optional, mutually exclusive operands. Enter one or
and square brackets none.
[]
[]
Stacked operands in square Mandatory; you must enter one of these operands. You
brackets or within braces can enter more than one.
{[]
[]}
Masking
You use masking when you want to display all records with names that share common
characters. You can include masking characters anywhere in a search string.
Some commands accept a generic mask. The mask can contain one or more asterisks,
one or more question marks, or both all in any position in the mask.
An asterisk matches any number of characters, including zero characters. A question

mark matches only a single nonblank character.

Masking
The following table provides examples of masks, and shows data strings that would
qualify as matches and not matching for each:
Mask Strings that match Strings that do not match

* Everything Nothing
ABC* ABC AB
ABCC ABXC
ABCXYZ
*ABC ABC ABCD
AABC
XYZABC
AB? ABC ABCD
ABD AB
A*B AB ABC
AXXB
*ABC* ABC ABXC
ABCD
XABC
XABCD
A??B AXXB AB
ABBB ABB
A*B*C ABC ACB
AABBCC AC
Wildcard characters can be in any position, including the first. Know that having the first
character a wildcard can slow down the first display. The entire file is sometimes read
before the display starts.
In general, the longer the initial string of characters that are not wildcards, the faster
the initial display is. In other words, ABC* usually displays faster than A*.
Commands
Commands
The next section contains command syntax, optional parameters, command usage, and
panel examples for these commands.
You can restrict some of these commands to particular terminals or operators. Ask the
CA WA CA 7 Edition coordinator within the data center for any command restrictions
that exist.
The cross-platform job types use different terminology for selected items but otherwise
are similar to the CPU job types. Instead of rewriting all commands to support these
differences, the keywords used are the same as CPU jobs unless specifically noted. Thus,
when using cross-platform jobs, PRMLIB is specified as JCLLIB or even JCLID when the
PRMLIB coded for the cross-platform definition is numeric. Some keywords apply only to
CPU jobs. These keywords are noted wherever possible. As you become familiar with
the differences between the job types, it becomes apparent which keywords are valid
and which keywords are invalid.
Long Online Commands

Commands that are entered in a VTAM or TSO/ISPF interface environment are limited to
the top line of the screen by default. In most cases, only 79 characters can be entered
on the top line, which is also known as the command line. A command that has more
than 79 characters is considered a long command.
When it is necessary to enter a long command, enter part of the command followed by
the command continuation character (CCC). The CCC is a plus sign (+). When the CCC is
the last character on the command line, the following happens when you press ENTER:
■ The screen blanks.
■ The command that was entered shows without the CCC.
■ The cursor positions after the last nonblank character.
■ The two top rows, totaling 160 characters, are available for command input.
A plus sign that is not the last character in the command is treated as part of the
command. The maximum length command that can be entered is 160 characters.

Long Online Commands
The CCC is not valid with the following commands:

■ /AUTO
■ /ECHO
■ /FETCH (The command ignores the CCC. The usage notes for /FETCH discuss how it
displays a long command.)
■ /LOGON
The CCC is not available in a batch environment.
Note: For more information about continuation characters in a CAICCI terminal

environment, see the Interface Reference Guide.
More information:
Usage Notes (see page 107)
Example
This example enters a long online DEMAND command.
The example shows the input field as underscored, and a question mark (?) identifies
the cursor position. The example starts with a blank screen.
?______________________________________________________________________________
Enter the DEMAND command followed by the CCC.
DEMAND +?______________________________________________________________________
The system returns the following screen.
DEMAND?_________________________________________________________________________
________________________________________________________________________________
Now, you can enter a long command.
DEMAND,JOB=CA07XX01,SCHID=2,TIME=1445,DOTM=1500,INTERVAL=0100,TYPE=CLOCK,STOP=21
30?_____________________________________________________________________________
Long Job Names
Long Job Names

The following commands have changes for the long job name enhancement. Each
command supports the JOBL keyword.
■ ADDRQ
■ CANCEL
■ DEMAND/DEMANDH
■ FJOB, FQJOB
■ FRJOB, FRQJOB
■ FSTRUC
■ HOLD
■ LACT, LACTR
■ LDTM
■ LIST
■ LJCK
■ LJCL
■ LJOB, LJOBR
■ LPRRN
■ LQ, LQP, LQR
■ LRDY, LRDYP, LRDYR
■ LREQ, LREQP, LREQR
■ LSCHD
■ LSYS
■ POST
■ QJCL
■ RELEASE
■ REQUEUE
■ RESTART
■ RUN/RUNH
■ XQ, XQJ, XQM, XQN
■ XRQ
■ XUPD

Long Job Names
Short Name Generation

The job conversion routine brings some jobs into the system. These jobs are assigned a
regular, eight-character job name, unless the user manually assigns a short name.
The first two characters of the assigned short name match the first two characters of
the original long name that is converted to uppercase. The remaining six characters are
an internal job name assignment.
Example: Job Brought into System and Assigned a Short Name
Long Name – FREDA11#ThisIsALongJobName

Short Name – FRWDGJ6D
If you create a job with a long job name using DB.1, DB.10, or DB.11 panel, you can
select your own short job name.
If the given long name is already eight or fewer characters, it is converted to uppercase.
The name is used as the short name also. If that short name is already taken, the user
must use a new long name for the job. Long job names that are eight or fewer
characters must match their short names, ignoring case.
Example: Job with Eight or Less Characters
Long Name – MyJob1

Short Name – MYJOB1
Long Job Name Rules

The following rules apply to the long job names:
■ Any long job name that is eight or fewer characters in length must match its short
name, ignoring case.
■ The existing jobs do not require a long job name.
■ Long job names that come through the distributed job conversion process must
only contain alphanumerics, underscores, periods, and national characters (@, #, $).
An error is issued when a name does not follow this rule.
■ If you assign a job name, the first character must be an alphabetic or a national
character. The second character must not be a period or an underscore.
■ Jobs that are created in CA WA CA 7 Edition only have a long job name when a user
specifically assigns one.
■ In top line commands, the JOB and JOBL keywords are mutually exclusive.
■ In alternate screens, specify the regular or long job name in the job name fields. CA
WA CA 7 Edition displays the long job names when available using fetched
information (like a LIST function).
General System Commands
General System Commands

General system commands are top line commands used by the CA WA CA 7 Edition
terminal operator to perform various functions.
Function Description Command

General Use these commands to perform various /AFM
operating functions. For those entries that can be /AGENT
commands entered with parameters, place a comma /AUTO
between the command and the first /BRO
parameter. /CLOSE
/COID
/COPY
/DISPLAY
/DRCLASS
/DRMODE
/EADMIN
/ECHO
/EMAIL
/GVAR
/FETCH
/IAS
/LOG
/LOGOFF
/LOGON
/MSG
/NXTMSG
/OPEN
/OPERID
/PA
/PAGE
/PF
/PROF
/PURGPG
/RESET
/START
/STOP
/SDESK
/SWAP
/UID
/WTO

General Inquiry Facility

The general inquiry facility provides information about the system, its various
components and operations. Information available includes reference information
about commands and applications, database contents, queue information, job status,
and schedule information.
The general inquiry commands are also useful in batch mode to obtain hardcopy output
of the information provided.
The status (ST=) keyword for the inquiry commands has many values. All can be entered
with any of the inquiry commands. Many values can return the message: No queue
records match parameters entered because the combination does not exist. An example
is listing the active queues (LACT) with the status of skeleton (ST=SKEL). A job in skeleton
status never reaches the active queue.
HELP tutorials List tutorials. HELP

Agent inquiries Obtain information about LAGENT
agents.
Job inquiries Database Obtain information about LJOB
contents various jobs from the CA WA LJOBR
CA 7 Edition database. LRES
LSYS
Queue contents Obtain information about jobs LACT
from the CA WA CA 7 Edition LJES
queues. LPRRN
LQ
LRDY
LREQ
LRES
LRLOG
ARF queue Obtain information about LARFQ
contents status of recovery for CA WA
CA 7 Edition jobs.
Queue status Obtain information about the LACT
inquiries work residing in CA WA CA 7 LPOST
Edition queues. These LPRE
commands are helpful in LPRRN
locating specific jobs or LQ
networks. They are also LRDY
valuable when monitoring the LREQ
flow of the total workload.
Data set Obtain information about LCTLG

inquiries user application data sets in LDSN
the CA WA CA 7 Edition LPDS
environment. You can review
information from the CA WA
CA 7 Edition database, and
PDS or sequential data set
data, with these commands.
Global variable Obtain information about LGVAR
inquiries global variables.
JCL inquiries Review job JCL or PARM LJCK
statements and members of LJCL
system libraries. These LLIB
commands access the LPDS
designated data set to obtain
the data in its permanent
form. (Compare this
command with the QJCL
command that displays the
JCL in its submit form).
Node inquiries Obtain information about the LNODE
XPJOB destinations.
Schedule Obtain information from the LJOB
inquiries CA WA CA 7 Edition database LLOCK
regarding CA WA CA 7 Edition LSCHD
schedules.
ARFSET inquiries Obtain information from the LARF
CA WA CA 7 Edition ARF
database regarding
automated recovery for CA
WA CA 7 Edition jobs.
Documentation Review any user-defined LPROS
inquiries documentation information
that resides in the CA WA CA
7 Edition database. Many of
the other inquiry commands
can show the documentation
for a particular job, and so
forth, as an optional part of
the display.

Reminder Review free-form reminder LRMD

inquiries information that you defined
for any special purpose.
Workload Provide information related LACTR
balancing to the CA WA CA 7 Edition LJOBR
inquiries workload balancing function. LQP
Through these commands, LQR
you can review those LRDYP
resource and priority issues LRDYR
that are important to LREQP
balancing the workload. LREQR
LRES
LWLB
Workstation Database Provide information about LNTWK
network contents workstation networks from LCTLG
inquiries the database. LSCHD
Queue contents Obtain information about LPRE
workstation networks when LPOST
they reside in the queues. LRLOG
These commands are
presented as they relate to
input and output networks
that use different commands.
XCF Obtain XCF-related LXCF
information.
Job Flow Control
Job Flow Control

After a job is scheduled from the CA WA CA 7 Edition database, job flow control is
accomplished through a group of queues. Typically, CA WA CA 7 Edition performs job
flow control automatically; however, it is sometimes necessary for the user to intervene
manually for unusual situations or on-request scheduling needs.
This table illustrates the top line commands that address manual job flow control
requirements.

Requirement Use the following top line commands and ADDRQ
control panels to monitor and modify the requirements CTLG
of those jobs under CA WA CA 7 Edition JCLOVRD
control. POST
QM.1
QM.2
QM.3
SUBTM
VERIFY
XQ, XQJ, XQM,
and XQN
XRQ
XUPD
Schedule control Sometimes you must alter scheduled jobs. Use ADDSCH
these commands to perform scheduling DEMAND
changes. DIRECT
NXTCYC
RUN
SSCAN
SUBMIT
SUBSCH
Resource Managing resource usage by jobs allows for an LQ
management additional level of job flow control. These PRSCF
commands and panels are used to define, PRSQA
monitor, and control job submission through PRSQD
job resource use. See "Virtual Resource RM.1
Management" in the Database Maintenance RM.2
Guide for more information about the RM RM.3
panels. RM.4
RM.5
RM.6
RM.7

Job Flow Control

Temporary JCL Use these commands to review jobs in the QJCL
changes request or prior-run queues or to modify the QM.5
JCL for jobs in the request queue.
Interrupting and Use these commands to delete jobs from the CANCEL
resuming jobs queues, interrupt the normal scheduling HOLD
progress, resume normal scheduling, move jobs JOBSTART
from the ready or active queue, and display QM.1
jobs in the request, ready, or active queues. RELEASE
REQUEUE
XQ, XQJ, XQM,
and XQN
Job restart Jobs that have failed to terminate successfully LIST
are returned to the request queue for restart QJCL
by the user. Such jobs are given a restart QM.1
requirement until the restart is performed. The QM.4
commands in this group are used to review, QM.5
perform job restart functions, or both. RESTART
XQ, XQJ, XQM,
and XQN
XRST
Prompting CA WA CA 7 Edition provides prompting LRMD
messages for any late work or work in danger NOPRMP
of becoming late. CA WA CA 7 Edition PRMP
continues to issue messages until either the QM.1
task is completed or the user disables the REMIND
prompting. The commands in this group are RSVP
provided for managing prompting messages. RUSH
XQ, XQJ, XQM,
and XQN
Queue control Occasionally, you must halt temporarily the START
flow of jobs through the CA WA CA 7 Edition STOP
queues. For example, you want to shut down HOLD
all processing and apply some maintenance RELEASE
before processing continues. Use these
commands for this purpose.
Recovery control Use commands in this category to cancel any ARFP
automated recovery that is scheduled for a
given run of a production job.
Agent output Use commands in this category to examine AGFILE
various output produced by agent job
execution.
Workstation Network Control

Agent job replies Use this command to send a message to a REPLY
system agent in response to an Intervention
Required condition for an agent job.

Workstation networks define tasks that you must perform manually (a non-CPU
activity). Although such tasks can be any manual tasks, they are typically performed in
support of CPU jobs. They can be performed either before or after 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. Each workstation must have its own
unique station name.
Some examples of preprocessing tasks that are sometimes defined together as an input
network are the following:
■ A control desk logging function
■ Data encoding
■ Encoding verification
■ Control desk task sequence for handling input data required by a CPU job
Some examples of postprocessing tasks that are sometimes defined together as an

output network are the following:
■ Report balancing
■ Decollate/burst/trim
■ Delivery
■ Task sequence for handling printed output produced by a CPU job
Each workstation can have its own terminal; or, multiple workstations can share a single
terminal. Networks are scheduled, either manually or automatically. CA WA CA 7 Edition
interacts with personnel at the appropriate terminals to help ensure that manual
workstation tasks are performed in the correct sequence and at the appropriate time.
CA WA CA 7 Edition messages accomplish this notification. Inquiry commands are also
available for further examining any related data. The data can assist the user in
performing the necessary tasks.
All terminal sessions are performed between /LOGON and /LOGOFF commands that the
terminal user must enter. During terminal sessions, any number of workstation sessions
can occur. Workstation sessions provide CA WA CA 7 Edition with the beginning and
ending time-of-day for each task defined in a network. (The tasks must be performed in
the predefined sequence.)

Task beginning times are entered by logging in to the station (as opposed to logging on
to a terminal). Use a LOGIN, IN, or IO command, or use one of these functions on a
QM.6 or QM.7 panel.
Task ending times are entered by logging out of the station (as opposed to logging off a
terminal). Use a LOGOUT, IO, or OUT command, or use one of these functions on a
QM.6 or QM.7 panel.
As each terminal logs in to the workstation, the work for that specific workstation is
available for viewing. Messages for that workstation are also routed to the terminal.

Logging in Specify starting of a workstation task. IN
IO
LOGIN
QM.6
QM.7
XPOST
XPRE
XSPOST
XSPRE
Logging out Specify ending of a workstation task. IO
LOGOUT
OUT
QM.6
QM.7
XPOST
XPRE
XSPOST
XSPRE
Inquiries These inquiry commands are available for LCTLG
examining any network-related data that can LNTWK
assist you in performing necessary tasks. LPOST
LPRE
LRLOG
LSCHD
On-request Use these commands to force immediate DMDNW
scheduling scheduling of networks. RUNNW
Schedule control Use these commands to adjust schedules of ADDSCH
networks already in the queues. SUBSCH
Forecasting

Prompting Prompting is a function of schedule scan. NOPRMP
Prompting notifies workstations when a task is PRMP
late or about to become late. REMIND
When a deadline time arrives and CA WA CA 7 RSVP
Edition has not received notification that the task RUSH
has been started, the responsible workstation is QM.6
prompted or reminded of the late status of the QM.7
task with a message from CA WA CA 7 Edition. XPOST
Prompting messages continue until the task is XPRE
completed or the operator acknowledges the XSPOST
prompt. XSPRE
Interrupting and If it is necessary to change the normal processing CANCEL

resuming a of a network, use these commands to interrupt a HOLD
network network, resume a network, or both. RELEASE
QM.6
QM.7
XPOST
XPRE
XSPOST
XSPRE
Forecasting
The following topics explain the forecasting feature.
Forecast Facility
The forecast facility projects the scheduled workload for a given time. The projected
workload can be as specific as a single job or as general as the workload for a CPU or
application system. Successor jobs triggered by predecessor jobs, or any jobs triggered
by data sets created in the predecessor jobs, can also be included.
Further, forecast displays the projected workload for successive short time intervals
throughout the forecast time period. This representation can be used to detect
bottlenecks in the system. Workload can be rearranged as needed and resources
scheduled properly.

Forecasting
Forecast also reports jobs involved with tapes, JCL overrides, or both ahead of their
actual submission time in two ways:
■ By preparing a pull list for the tapes. The pull list indicates the volume serial number
of the input tapes, and the approximate number of scratch tapes for the output
data sets.
■ By determining which jobs need JCL overrides. The Forecast report indicates jobs
that need JCL overrides. The override JCL can be stored in a special JCL override
library and retrieved automatically. This process satisfies the JCL override
requirement without any further intervention required. JCL overrides and the JCL
override library are not applicable to cross-platform jobs.
Also, forecast can be used for the following:

■ To show an entire job network, and the ending time of each job in the structure of
the network, based on an arbitrary starting time.
■ To produce a hardcopy report of scheduled tasks in worksheet format. The report
can serve as a manual checklist for recording task completion.
■ To verify newly defined schedules. Forecast can be run for a single job or an entire
application system. Forecasts help ensure that defined schedules cause processing
cycles to occur when required.
Forecast Options
Two options are provided throughout the forecast application. For the first option,
workload is projected only from the CA WA CA 7 Edition database. No existing workload
is projected from the CA WA CA 7 Edition queues. This option requires a beginning time
and is used for nonspecific long range requests.
The second option takes the workload existing in both the database, the CA WA CA 7
Edition queues, or both into account in the forecast. This option uses the current time as
the beginning of the time interval so that current and future workload can be
forecasted. This option is typically used for shorter and more specific requests.
Forecast Commands
A number of different commands are provided to generate specific forecast

information. Even though some of the capabilities overlap, the following table provides
a guide to the basic capabilities of these commands.
Capability Commands
Forecast report for CPU workload with optional FJOB or FQJOB
worksheets
Forecast report for input workstation workload FPRE or FQPRE
Forecast report for output workstation workload FPOST or FQPOST
Forecasting
Capability Commands
Forecast report for input and output workstation workload FSTN or FQSTN
Forecast report for CPU and input/output workstation FALL or FQALL
workload
Graphic display of workload FRES or FQRES
Tape pull list report FTAPE or FQTAPE
Job flow structure FSTRUC
Simulate Workload Planning FWLP
A forecast can be done online or in batch mode for any time interval from one minute to
one year. The forecast can be for all work of the data center, work for a specific CPU, or
work for a specific job or workstation. Selection criteria are provided for flexibility in
tailoring a forecast run to meet specific needs.
Note: Depending on the selection criteria used, Forecast can produce a large volume of
output. For such large volume runs, use a batch terminal rather than an online terminal.
Large volumes can also require that you increase the allocated space for the CA WA CA
7 Edition scratch queue or change the SWFTRK option.
An initialization file option FCMAXLEV governs the maximum levels that a forecast
command shows. If this option is not used, the default maximum level is 99 (for all
forecast commands).

Forecasting
Common Forecast Parameter Descriptions
The following parameters are used throughout the forecast commands and are defined
here and referred to later as needed.
DRMODE
If DRMODE=YES (or Y) is specified, the forecast is limited to jobs with an active
disaster recovery class. The DRCLASS keyword can override the list of active disaster
recovery classes. DRMODE=NO (or N) can be used. If the DRMODE keyword is not
specified, DRMODE=YES is used when CA WA CA 7 Edition is currently running in
disaster recovery mode, or DRMODE=NO if not.
DRCLASS
Overrides the list of active disaster recovery classes for the forecast command. If
DRCLASS is not specified and the forecast command runs in disaster recovery mode,
the list of active disaster recovery classes in CA WA CA 7 Edition is used. If DRCLASS
is specified, only the disaster recovery classes on the DRCLASS keyword are
considered active.
Note: The combination of DRMODE and DRCLASS parameters, with the disaster
recovery initialization settings (DRMODE,TRIGGERS), impact what the forecast
commands display for disaster recovery situations. For example, if the
TRIGGERS=DR is in effect, the forecast commands for a specific job show its job flow
but only include triggers with an active DRCLASS. The flow terminates on the first
trigger with an inactive DRCLASS and does not include that trigger. When
TRIGGERS=NONEXEC or TRIGGERS=ALL in effect, all triggers are included. Be sure to
check your DRMODE, DRCLASS, and DRMODE TRIGGERS settings if your forecast
output is not as expected. The /DISPLAY,ST=DR shows the TRIGGERS setting.
Note: For more information about Disaster Recovery Mode, see the Systems
Programming Guide.
INT
See the RINT keyword.
JOB
(Optional) Defines the jobs to forecast. JOB and JOBL are mutually exclusive.
Note: The job names can be masked with complex masking (? and *).
Default: *
Limits: 1 to 8 alphanumeric characters
Forecasting
*
Indicates to forecast all jobs.
jobname
Defines a specific job name.
jobname*
Defines a generic job name that is terminated with an asterisk.
(jobname1,jobname2,...,jobname10)
Defines up to ten specific job names.
mask
Defines a keyword value mask.
JOBL
(Optional) Defines the jobs to forecast. JOB and JOBL are mutually exclusive.
Note: The job names can be masked with complex masking (? and *).
Default: *
*
Indicates to forecast all jobs.
longjobname
longjobname*
mask
JOBNET
(Optional) Defines the job network field as the selection criteria for the jobs to
forecast.
Default: *

Forecasting
*
Specifies all names.
name
Defines a specific name.
name*
Defines a generic name that is terminated with an asterisk.
mask
Note: If value contains a blank, comma, or quote, it is not possible to specify the
value through batch input.
LVL
(Optional) Defines the number of triggering levels to display. If not defined, the
forecast stops after 100 levels or the value defined in the FCMAXLEV keyword in the
CA WA CA 7 Edition initialization file.
Default: 100 (or CA WA CA 7 Edition initialization file override)
Limits: 1 to 3 numeric (1-999)
MAINID
(Optional) Specifies that only those jobs set to run on the specified MAINID appear
in the forecast.
Limits: 1 numeric character from 1 to 7 preceded by SY
NW
(Optional) Defines the networks as a selection criteria for the stations to forecast. A
combination of STN and NW values governs the final selection of a station to
forecast. If STN=T*,NW=N* is specified, only the stations whose names start with T
and belong to networks whose names start with N are selected for the forecast.
Default: *
*
Specifies all networks to forecast.
network
Defines a specific network name.
network*
Defines a generic network name that is terminated with an asterisk.
mask
Forecasting
NWOPT
(Optional) Specifies whether the forecast includes the output networks and their
individual stations for the jobs. If NWOPT is omitted, no connected networks are
included.
N
Specifies to include output networks, but not to list individual workstations in
the networks.
S
Specifies to include individual workstations in the network.
RINT|INT
(Optional) Defines the interval time for the forecast of resources that are needed
for the workload. The entire forecast span is divided into successive time intervals
of the value specified to forecast the number of jobs running and percent of CPU
use during each interval.
Limits: 4 numeric characters that are specified as hhmm from 0010 (10 minutes) to
2400 (24 hours)
SCHID
Defines the schedule ID value as the selection criteria for jobs to forecast.
Default: 0 (all schedule IDs)
except for FSTRUC the default is 1
Limits: 1 to 3 numeric characters from 0 through 999
except for FSTRUC 1-999
Required: Only if the job has no defined schedule.
SEG
(Optional) Specified only with LIST=WP or LIST=WPS to define which segment and
subsegment of prose to include in the worksheet. If omitted, LIST=WP and
LIST=WPS produce all prose associated with a particular job. If only segment
selection is desired, the parentheses can be omitted.
Limits: 1 to 8 alphanumeric characters segment
1 to 8 alphanumeric characters subsegment
SEQ
(Optional) Specifies the sequence in which forecast reports are presented.
Default: DLDT

Forecasting
DLDT
Specifies the sequence as the ascending order of the deadline or starting date
and time of the job, ending date and time of the job, and job name.
DODT
Specifies the sequence as the ascending order of the due-out or ending date
and time of the job, starting date and time of the job, and job name.
JOB
Specifies the sequence is in the ascending order of the job name, starting date
and time of the job, and ending date and time of the job.
STN
Specifies the sequence is in the ascending order of the station name, starting
date and time of the station, and ending date and time of the station.
STN
(Optional) Defines the workstations to forecast.
Default: *
*
Specifies all workstations are to forecast.
station
Defines a specific workstation name.
station*
Defines a generic workstation name that is terminated with an asterisk.
(station1,...,station10)
Defines up to ten specific workstations names. The workstation name that is
specified by the first positional value can be a specific workstation name or a
generic workstation name.
mask
SYS
(Optional) Defines the systems as a selection criteria for the jobs to forecast. A
combination of JOB and SYS values governs the final selection of a job to forecast. If
JOB=J*,SYS=S* is specified, only the jobs whose names start with J and that belong
to systems whose names start with S are selected for the forecast.
Default: *
Forecasting
*
Specifies all system names.
system
Defines a specific system name.
system*
Defines a generic system name that is terminated with an asterisk.
Note: If value contains a blank, comma, or quote, it is not possible to specify
the value through batch input.
mask
TRIG
(Optional) Specifies whether the forecast includes the job-triggered jobs, the data
set-triggered jobs, or both.
Default: J (except JD for FSTRUC)
J
Specifies to include only the job-triggered jobs.
D
Specifies to include only the data set-triggered jobs.
DJ
Specifies to include both job-triggered and data set-triggered jobs.
JD
Specifies the same as DJ.
N
Does not include job triggers or data set triggers.
Any data set that a forecasted job can create and with a data set trigger defined, is
assumed to be created thus triggering the other job.
TYPE
(Optional) Specifies whether the "dont schedule before/after" criteria that are
defined on the job definition panel is honored when generating a forecast.
Default: ACTUAL

Forecasting
ACTUAL
Specifies honor "dont schedule before/after" criteria.
ALL
Specifies show all jobs as scheduled. Also indicates jobs that have
NXTCYC,SET=OFF and NXTCYC,SET=SKP specified.
More information:
Forecasting from the Database

The following topics explain forecasting from the database.
Commands
This group of forecast commands selects work only from the database according to the
start time. Specify start time either explicitly or imply it by due-out time minus average
elapsed time. Job (data) selection is made when the start time falls within 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 also displayed. As a result, the start
time of these subsequent jobs or workstations can fall beyond the specified time
interval. The group includes the following:
FJOB
Forecasts for jobs
FSTN
Forecasts for workstations
FPRE
Forecasts for input workstations
FPOST
Forecasts for output workstations
FALL
Forecasts for jobs and workstations (in both input and output networks)
Forecasting
A forecast can be done for any time interval, and it can be done in online or batch
mode. However, as the forecast time interval is increased, the response time in online
mode can lengthen, the output volume can become larger, or both. These forecast
functions use the CA WA CA 7 Edition scratch queue. Consider increasing the allocated
space for this file, depending on the size of the database and the time interval of the
forecast.
Forecast selection can be made from the database by job, system, workstation, or
network and indicated by specific or generic names. Specify specific names in up to
eight characters. Specify generic names in up to seven characters and terminate them
with an asterisk (*).
More information:
Commands (see page 55)
Forecast Interval
You can define the forecast interval for these commands using a beginning and ending
date.
The dates have the following format:
FROM=(mmddyy,hhmm),{TO=(mmddyy,hhmm)|SPAN=hhhh}
mmddyy
Defines the date.
mm
Defines the month (01 through 12). Required. Leading zeros are required.
dd
(Optional) Defines the day (01 through 31). If omitted, 01 is assumed for FROM,
last day of month for TO. A leading 0 is required if less than 10.
yy
(Optional) Defines the year. If omitted, the current year is assumed.
hhmm
(Optional) Defines the time. If omitted, 0000 is assumed for FROM, 2359 for TO.
hh
Defines the hour (00 through 23).
mm
Defines the minute (00 through 59).

Forecasting
SPAN=hhhh
As an alternate to specifying an ending date and time (TO), you can request a time
interval using SPAN=hhhh where:
hhhh
Defines the interval span in hours. Minimum value is 1 and maximum value is
8784 (approximately one year).
Note: A job (or network) is only considered by the forecast if the FROM time of the
forecast falls within the job's (or network's) schedule period (January-December or
July-June).
Examples
In these time interval examples, current year is 2013.
FROM=(0307,08) is identical to FROM=(030713,0800)
FROM=0515 is identical to FROM=(051513,0000)
TO=(03,17) is identical to TO=(033113,1700)
TO=01 is identical to TO=(013113,2359)
FROM=01 is identical to FROM=(010113,0000)
Forecasting from Queues

The following topics explain forecasting from the queues.
Commands
These forecasting commands select work from the CA WA CA 7 Edition active workload
(queues) and from the definition database. The selection for work is made from the CA
WA CA 7 Edition queues first. Then, if the forecast time period is large enough, further
selection is made from the database according to the start time. Due-out time minus
average elapsed time either explicitly specifies or implies start time. If the start time
falls within the time interval of the forecast, the data selection is made. The selection
displays any jobs that the selected jobs trigger, or any workstation in the output
networks that is connected to these jobs. As a result, the start time of these subsequent
jobs or workstations can 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 mode can lengthen, the
output volume can increase, or both. These forecast functions use the CA WA CA 7
Edition scratch files. Consider increasing the allocated space for these files, depending
on the size of the database and the forecast time interval.
Forecasting
network and can have specific or generic names. The specific names are specified in up
to eight characters. The generic names are specified in up to seven characters and
terminated by an asterisk (*).
FQJOB
Forecasts for jobs
FQSTN
Forecasts for workstations
FQPRE
Forecasts for input workstations
FQPOST
Forecasts for output workstations
FQALL
Forecasts for jobs and workstations (in both input and output networks)
Forecast Interval
The beginning time for the forecast interval for these functions is always the command
initiation (current) time. The ending time for the forecast interval is optional. If omitted,
selection is based on the CA WA CA 7 Edition queues only. You can specify the ending
time either explicitly by a keyword TO or implicitly by SPAN.
The keyword has the following format:
TO=(mmddyy,hhmm)
mmddyy
Defines the date.
mm
Defines the month (01 through 12). Required. Leading zeros are required.
dd
(Optional) Defines the day (01 through 31). If omitted, last day of month is
assumed. A leading 0 is required if less than 10.
yy
(Optional) Defines the year. If omitted, the current year is assumed.

Forecasting
hhmm
(Optional) Defines the time. If omitted, 2359 is assumed.
hh
mm
The SPAN keyword format has the following format:
SPAN=hhhh
hhhh
Defines hours from 1 to 8784 (one year).
Examples
Forecast interval examples:
TO=(0517,08) is identical to (051709,0800)
TO=06 is identical to (063009,2359)
In these examples, current year is 2009.
Forecasting Job Flow Structures

The following topics explain forecasting job flow structures.
Commands
These forecast commands produce reports that display the structures of job flows
defined in the CA WA CA 7 Edition database. They are used to deal with individual
structures within the database definitions rather than the entire workload.
The FSTRUC command can produce a forward forecast of a job structure from a starting
job with a specific or implied starting date and time.
Forecasting
You can use the FRJOB and FRQJOB commands to produce reverse job structures. They
display the paths of control that cause the delivery of the target job into the system
through job, data set, and network trigger definitions. That is, answer the question
"How does this job get into the system?". The queue variation of this command is
FRQJOB. FRQJOB looks at the status queues to determine whether a job in the trigger
chain currently resides in the queues.
FSTRUC
Reports on an entire CPU job flow structure from the database with starting and
ending times.
FRJOB
Produces a reverse job flow structure from the database to identify trigger chains
and header jobs.
FRQJOB
Produces a reverse job flow structure from the database and the status queues to
identify trigger chains and real-time header jobs.
Forecasting Resources
The following topics explain forecasting resources.
Commands
These forecasting commands display, in reports and graphs, resource forecasts for
successive short time intervals throughout the forecast time period. These resources
include percentage of CPU, number of tapes (for each type), and number of
workstations.
For the FQRES function, the work for resource forecasting is selected from the CA WA
CA 7 Edition queues and from the database. The selection is made from the queues first.
Later, if the forecast time period is large enough, further selection is made from the
database.
For 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. Specify
start time either explicitly or imply by due-out time minus average elapsed time. The
selection is made if the start time falls within the time interval of the forecast.
Optionally, any jobs triggered by the selected jobs or any workstation in the output
networks connected to these jobs are also included.

Forecasting
A forecast can be done for any resolved time interval, and it can be in online or batch
mode. However, as the forecast time interval is increased, the response time in online
mode can lengthen, the output volume can become larger, or both. These forecast
functions use the CA WA CA 7 Edition scratch queue. Consider increasing the allocated
space for this file, depending on the size of the database and the time interval of the
forecast. See SWFTRK parameter on the DAIO initialization file statement.
network and indicated by specific or generic names. Specific names are specified in up
to eight characters, and generic names are specified in up to seven characters and
terminated with an asterisk (*).
FRES
Forecasts for resources needed for CPU and workstation workload.
FQRES
Forecasts for resources needed for CPU and workstation workload including the
existing workload in the CA WA CA 7 Edition queues.
Forecast Interval
The beginning time of the forecast for the FRES command can be any valid time. For
FQRES, it is always the command initiation (current) time. The ending time for the
forecast for FRES must be specified. For FQRES, it is optional. If omitted, the selection is
based on the CA WA CA 7 Edition queues only. Specify the ending time either explicitly
using the keyword TO or implicitly by SPAN. The command descriptions contain the
formats of the FROM and TO keywords.
More information:
FQRES Command (see page 241)

FRES Command (see page 247)
Forecasting Tape Requirements

The following topics explain forecasting tape requirements.
Forecasting
Commands
These forecast commands produce reports indicating the volume serial numbers of the
input tapes that are needed for jobs during the specified forecast time period. The jobs
that are used for FTAPE are selected only from the CA WA CA 7 Edition definitions. For
FQTAPE, the jobs that are used to produce tape pull lists are selected from the CA WA
CA 7 Edition active workload (queues) and from the definition database. Selection is
made from the queues first. Then, if the forecast period is large enough, further
selection is made from the database.
The selection from the database in both cases is done according to the start time.
Specify a start time either explicitly or imply due-out time minus average elapsed time.
The selection is made if the start time falls within the time interval of the forecast. Any
jobs that the selected jobs trigger are also optionally included. Once the job is selected,
the database is searched for any data set residing on tape. CA WA CA 7 Edition 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 or system name.
These names can be specific or generic. The specific names are specified in up to eight
characters, and generic names are specified in up to seven characters and terminated
with an asterisk (*).
Note: The JCL for selected jobs is not examined, only the database information.
Therefore, temporary changes that are made to JCL regarding any VOLSER values are
reflected in the forecast only when the job is reloaded.
The order of the JCL within a step is important to whether a particular tape data set 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 DD statement comes before
the output DD statement, the data set is considered as a requirement and forecasts.
Otherwise, it does not.
FTAPE
Tape pull list for jobs.
FQTAPE
Tape pull list for jobs including those jobs in the CA WA CA 7 Edition queues.
Forecast Interval
The beginning time for the FTAPE command can be any valid time. For FQTAPE,
however, it is always the command initiation (current) time. Specify the ending time for
FTAPE. For FQTAPE it is optional; if omitted, the selection is based on the CA WA CA 7
Edition queues only. You can specify the ending time either explicitly by the keyword TO
or implicitly by SPAN. The commands contain the formats of the FROM and TO
keywords.

Forecasting
More information:
FTAPE Command (see page 265)

FQTAPE Command (see page 245)
CPU Job Worksheets

The worksheet options from forecast provide conveniently formatted checklists for
projected CPU job activities. When requested, production control personnel can use the
output for status, planning, or even recovery documentation.
Worksheets for jobs are requested using the LIST option of the FJOB or FALL command.
This option is most useful when requested through the Batch Terminal Interface facility
because the output is in hardcopy format and can be filed or distributed as desired.
For a sample worksheet, see the LIST option of the FJOB command.
JOB Worksheet, LIST=W
FJOB,FROM=0306yy,TO=0306yy,LIST=W
DATE 02-27-yy PAGE 0002
JOB=DUCCXX01 COMPLETED ________________
SCHEDULE: LATEST STRT=yy065/0759 SCHD MBR=YES

DUEOUT TIME=yy065/0800 SCHED ID=001
SUBMIT TIME=yy065/0000
GENERAL: JCLMBR=DUCCXX01 JCLID=000

SYSTEM=TESTNTWK LTERM=
NBRRUN=007 LSTRUN=yy261/1607
RESOURCE: MAINID=ALL PRTY=000 CLASS=A

ELAPTM=0001 TP1 =00 TP2 =00
EXECUTION: RELOAD=NO EXEC=YES MAINT=NO

RETJCL=NO HOLD=NO
Forecasting
JOB Worksheet, LIST=WP
FJOB,FROM=0306yy,TO=0306yy,LIST=WP
DATE 02-27-yy PAGE 0002
JOB=DUCCXX01 COMPLETED _______________
SCHEDULE: LATEST STRT=yy065/0759 SCHD MBR=YES

DUEOUT TIME=yy065/0800 SCHED ID=001
SUBMIT TIME=yy065/0000

NBRRUN=007 LSTRUN=yy261/1607

ELAPTM=0001 TP1 =00 TP2 =00

RETJCL=NO HOLD=NO
******** 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 DUCCXX01 ******
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 AS
INPUT, CREATES A DATASET U7TEST01 AS OUTPUT AND DEMANDS THE NEXT JOB DUCCXX02
TO BE STARTED AFTER THE SUCCESSFUL COMPLETION OF THE STEP. THE SECOND STEP
RECEIVES ANOTHER SET OF CONTROL CARDS AS INPUT AND CREATES A DATASET U7TEST02
AS OUTPUT. IN TURN, U7TEST02 AUTO-TRIGGERS JOB DUCCXX03.
#QDESC
*** JOB DUCCXX01
*** SCHEDULED JOB, FIRST IN THE NETWORK
*** FIRST STEP
*** INPUT-CONTROL CARDS OUTPUT-U7TEST01
*** SECOND STEP
*** INPUT-CONTROL CARDS OUTPUT-U7TEST02
#END,QDESC
More information:
FJOB Command (see page 218)

Chapter 2: Commands
The user commands are described in alphabetical sequence, with all slash (/) commands
appearing first.
In this section, user commands are shown with command description format, parameter
and option descriptions, examples, and typical terminal display panels.
As with all CA WA CA 7 Edition commands, security must authorize these commands

before a terminal user can perform any of them.
/AFM Command
The /AFM command is a reserved command in support of CA WA Agents.
/AGENT Command
The /AGENT command sends a request to a system agent to perform a specific control
action on that agent or to update an agent configuration setting. You can request the
following functions:
■ Refresh the agent security files.
■ Clear log files.
■ Stop the agent after current work is complete.
■ Update a configuration setting.
■ Verify the communication link to the agent.
This command has the following formats:
Format 1
/AGENT,AGENT=agent,FUNC=function
/AGENT Command
Format 2
/AGENT,AGENT=agent,PROP=name=value[,PERSIST={NO|YES}]
AGENT
Specifies the system agent that is the target of the command.
FUNC
Specifies an action that the agent is to perform.
Note: For HP NonStop agents, only FUNC=PING is supported. FUNC=SHUTDOWN
gives a function complete message but has no actual impact on the agent. All other
FUNC and PROP values are returned with the message AFM2-009 Timed out waiting
on response.
The following values are valid:
CLRFILES
Clears agent log files.
PING
Verifies the communication link to the agent. The return of a RESPONSE
STATUS message indicates success. The return of AFM2-009 Timeout message
indicates failure.
REFRESH
Refreshes the agent security files.
SHUTDOWN
Stops the agent.
Note: The agent sometimes does not send a response in a timely manner to
indicate that the agent is shut down. You can verify the shutdown using the
LAGENT command or by locating the physical computer on which the agent
executes.

/ASSIGN Command
PROP
Specifies a system agent configuration setting for an update. The format is
name=value where name is the configuration property to change and value is the
new setting.
PERSIST
(Optional) Specifies whether the configuration setting changed with the PROP
keyword is a permanent change or the change is in effect for the current session
only. The following values are valid:
NO
Specifies that the configuration change is for current session only. NO is the
default.
YES
Specifies that the configuration change is permanent.
/ASSIGN Command
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 submit data sets.
■ Alters the maximum number of jobs that can be submitted to a CPU.
This command has the following formats:
Format 1
/ASSIGN,{LT|LTERM}=station[,{T|TERM}=terminal]
Format 2
/ASSIGN,{MA|MAINID}={SYn|SY*},CPU=ddname
/ASSIGN Command
Format 3
/ASSIGN,CPU=ddname,BARR=barrier
LTERM
Defines the logical terminal (station) that you want to reassign. Required for Format
1. You can use LT or LTERM interchangeably, but Format 1 requires one or the
other.
TERM
(Optional) Defines the physical terminal to which the logical terminal is being
assigned. You can use T or TERM interchangeably. If TERM is not specified, the
default is the terminal issuing the command.
MAINID
Defines the current MAINID assigned to a submit data set on the CPU statement in
the initialization file. Required for Format 2. You can use MA or MAINID
interchangeably, but Format 2 requires one or the other.
SYn
Defines a single digit number (from 0 to 7 as determined from the initialization
file definitions).
SY*
Specifies that a MAINID is not indicated.
CPU
Defines the submit data set assigned to a CPU. The value is the ddname for the data
set that is defined in the CA WA CA 7 Edition JCL and the initialization file CPU
statement. Required for Formats 2 and 3.
BARR
Defines the maximum number of jobs that can be submitted at one time to a CPU.
The value that is specified can be up to 4 digits. Required for Format 3.

/AUTO Command
Usage Notes
You can use only those forms of the command on the preceding list.
When reassigning a logical terminal, assign it to the same type of physical device as that
originally assigned (3270 to batch, 3270 to browse, and so forth, are not permitted).
If a MAINID is defined as associated with more than one CPU and the MAINID is
reassigned using /ASSIGN, CA WA CA 7 Edition changes only the first occurrence of 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 be requeued and
resubmitted by CA WA CA 7 Edition. If in a shared-spool JES environment, you can
reroute such jobs through JES instead of CA WA CA 7 Edition.
Examples
/ASSIGN,LT=KEYPNCH,TERM=RTERM1
/ASSIGN,MA=SY0,CPU=UCC7SUB1
/ASSIGN,MAINID=SY*,CPU=UCC7SUB2
/ASSIGN,CPU=UCC7SUB1,BARR=50
/AUTO Command
The /AUTO command causes a terminal to reissue a command at a specified interval.
This command is only valid when accessing CA WA CA 7 Edition online through native
VTAM.
This command has the following format:
/AUTO[,INT={5|iii}]
[,COUNT=ccc]
[,{M|MSG}=text]
INT
(Optional) Defines the number of seconds between each time that the command is
issued.
Default: 5
Limits: 1 to 3 numeric characters from 3 to 300
/AUTO Command
COUNT
(Optional) Defines the number of repetitions for the command. This number limits
the number of times that the command is issued.
Default: No limit
MSG
Defines the command text that is issued. Use M and MSG interchangeably, but
specify one or the other. If commas are part of the text, enclose the message in
parentheses.
Usage Notes
To stop a terminal after a /AUTO command, press Enter or enter a new command.
If a new command is being entered when the time interval expires, the terminal is taken
out of /AUTO mode, but the last output is sent to the terminal when Enter is pressed
(not the output from the new command).
The /AUTO command is only valid for online terminals.
The command continuation character (CCC) is not valid with the /AUTO command.
More information:
Examples
/AUTO,INT=3,MSG=(LQ,ST=RSTR)
/AUTO,COUNT=5,INT=120,M=(DEMAND,JOB=XYZ)
/AUTO,M=XWLB

/BRO Command
/BRO Command
The /BRO command broadcasts a message to terminals on the CA WA CA 7 Edition
system. The message is queued until the receiving terminal user requests display.
Note: The /MSG command sends a message to one specific terminal.
For a CA WA CA 7 Edition virtual terminal to receive a broadcast message, specify the

TERM option or connect the terminal.
/BRO,{M|MSG}=text[,{T|TERM}=ALL]
MSG
Defines the text of the broadcast message. MSG and M can be used
interchangeably, but one or the other is required. If commas are included as part of
the text, enclose the entire message text in parentheses.
TERM
(Optional) In general, do not use this parameter. This parameter affects the way a
broadcast message is sent to the VTAM virtual terminals. If not specified, only those
virtual terminals that are connected to CA WA CA 7 Edition get the message. If
specified, all the VTAM virtual terminals get the message. This parameter can cause
excessive space usage of the scratch queue.
Default: Virtual terminals that are connected to CA WA CA 7 Edition only.
Limits: 3 alphabetic characters
More information:
/MSG Command (see page 118)
/CHANGE Command
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
termname
Identifies the broadcasting terminal.
text
Identifies the free-form text that is entered for the MSG or M parameter.
Note: Use the /MSG command to send a message to a specific terminal.
/CHANGE Command
The /CHANGE command modifies the security definition for a given operator by
changing the level of authorization that controls the ability of an operator to use the
commands of CA WA CA 7 Edition applications.
Note: This command is only applicable if CA WA CA 7 Edition native security is being

used for command access.
/CHANGE,{A|APPL}=application,{O|OPERID}=operid,{P|PRTY}=nn,{T|TERM}={term|**ALL**
}
APPL
Defines the CA WA CA 7 Edition application for which you want to assign a different
level of authorization. You can use A and APPL interchangeably but must specify
one or the other. The value must be the driver program suffix specified in the
SECURITY macro (for example, SFC0, SDM0, and others).
OPERID
Defines the operator ID for which you want to change the authorization. You can
use O and OPERID interchangeably but must specify one or the other. The value
must be the operator ID defined in the SECURITY macro.

/CHANGE Command
PRTY
Defines the new level of authorization for the designated CA WA CA 7 Edition
application. You can use P and PRTY interchangeably but must specify one or the
other. The value must be numeric and must be from 0 through 15.
Note: For default authorization values, see the Security Reference Guide.
TERM
Defines the physical terminal at which the change in authorization applies. You can
use T and TERM interchangeably but must specify one or the other.
term
Defines the symbolic terminal name that the NAME parameter on the TERM
statement in the initialization file defines.
**ALL**
Must be specified to change authorization levels for an OPID that is defined in
the Security macro with a TRMD=**ALL**.
Usage Notes
Alterations to a security definition that a /CHANGE command makes are in effect only
for the current execution of CA WA CA 7 Edition. Alterations take effect only after the
next logon of the terminal.
When changing level of authorization, specify the application for which level of
authorization is being changed on the SECURITY macro for the designated operator. The
SECURITY macro must initially authorize access to a CA WA CA 7 Edition application.
Example
/CHANGE,OPERID=OPER0001,TERM=RTERM1,A=SDM0,PRTY=10
/CHGOPT Command
/CHGOPT Command
The /CHGOPT command modifies a specific initialization file option after CA WA CA 7
Edition is already initialized.
/CHGOPT,{LIST=STAT|keyword=value}
LIST=STAT and keyword=value are mutually exclusive. One of them is required.

LIST=STAT
Lists all of the modifiable options with their current values.
Limits: STAT is the accepted value.
Valid keywords and values are as follows:

ATTACH
From the OPTIONS statement, specifies whether to attempt JCL attach processing
for nonexecutable jobs.
ALL
Performs JCL attach processing on all jobs, including nonexecutable jobs.
EXEC
Performs JCL attach processing on executable jobs only.
AUTOREQ
From the OPTIONS statement, specifies whether CA WA CA 7 Edition automatically
requeues jobs found to be active on a specific CPU when a recycle of that CPU
occurs.
NO
Does not automatically requeue jobs.
YES
Requeues the jobs automatically that are in the active queue and shows that
they are running on the CPU that has been recycled.

/CHGOPT Command
CTIMSG
From the OPTIONS statement, determines whether to write multiple messages to
the CA WA CA 7 Edition JES log for each CAICCI terminal session.
YES
Continues to write all messages.
NO
Writes only one log message for each CAICCI terminal session:
CA-7.XTM0 Session ended ...
The other messages are not written.
INITCASE
From the OPTIONS statement, determines character translation mode in the CA 7
Editor. If Full Edit Mode is used, then:
NO
Forces the translation of all data to uppercase.
YES
Controls the translation with the case setting commands in the CA 7 Editor.
Note: For more information about the FEM subcommands MIXED and UPPER, see
the Database Maintenance Guide.
JCLDSST
From the OPTIONS statement, enables the production of a new log record that
contains timing data for JCL data set accesses. CA Earl and CA Easytrieve report 038
can be used to report on this activity. Using JCLDSST=YES can create many extra log
records and can affect your overall performance. Thus, use caution with this option.
NO
Does not write extra log records.
YES
Writes the extra log records.
LOADCLASS
From the OPTIONS statement, specifies the default Workload Balancing (WLB) class
for jobs that are brought into the system by the LOAD/H command. The value must
be a single alphanumeric character.
ROUTCDE
From the RESTART statement, specifies a route code for the job and step
termination WTOs when the WTO, WTOSTEP, or both keywords are specified. The
WTOs are CA-7.SMF3 and CA-7.SMF4. The value must be a number from 1 through
16.
/CHGOPT Command
RUNCLASS
From the OPTIONS statement, specifies the default WLB class for jobs that are
brought into the system by the RUN/H command. The value must be a single
alphanumeric character.
WTO
From the RESTART statement, specifies whether to issue a WTO when a CA WA CA
7 Edition submitted job terminates unsuccessfully. See the Message Reference
Guide for message CA-7.SMF3.
NO
Does not issue a WTO at unsuccessful job completions.
YES
Issues a WTO.
HI
Issues a highlighted and nonscrollable WTO.
WTOSTEP
From the RESTART statement, specifies whether to issue a WTO for job steps that
CA WA CA 7 Edition tracks.
NO
Does not issue a step fail WTO.
YES
Issues a WTO for bad step terminations.
HI
Issues a highlighted and nonscrollable WTO for bad step terminations.
ALL
Issues a WTO for every step completion for every tracked job regardless of the
termination condition except for LOAD only jobs.
ALLHI
Issues a WTO for every step completion for every tracked job regardless of the
termination condition except for LOAD only jobs. Also, WTOs are highlighted
and nonscrollable.
Note: If ALL or ALLHI is used, many WTOs are issued depending on the number
of tracked jobs and the number of steps in each job.

/CLOSE Command
XSUBMIT
From the XPDEF statement, specifies whether this CA 7 instance can send jobs to
another platform through XPJOB facilities.
YES
Enables the XPJOB facilities.
NO
Disables the XPJOB facilities.
Note: XSUBMIT=YES can only be specified if the CA 7 instance was originally
initialized with XSUBMIT=YES specified on the XPDEF statement.
Usage Notes
You can specify all of the YES and NO values as Y or N.
The alterations to the initialization options that a /CHGOPT command makes are in
effect only for the current execution of CA WA CA 7 Edition.
If you want permanent changes, update the same options in the initialization file.
Note: For more information about the keywords, see the Systems Programming Guide.
Example
The following example changes the default LOADCLASS value to B for this execution of
the product:
/CHGOPT,LOADCLASS=B
/CLOSE Command
The /CLOSE command closes VTAM terminals.
A /CLOSE command with no parameters disconnects the issuing terminal from CA WA

CA 7 Edition.
Important! Production users must use the command with no parameters. The
parameters are only for system users.
/CLOSE[,GROUP=group][,{T|TERM}={terminal|TCP/IP}]
/CLOSE Command
GROUP
(Optional) Defines a line group to close and identifies which group. Value must be
the group name that the NAME parameter on the GROUP statement in the
initialization file defines. If GROUP specifies a VTAM group, all CA WA CA 7 Edition
connected VTAM terminals are disconnected, not just the identified group.
Both CAICCI and TCP/IP share the group that is defined as DEVICE=CCI. If /CLOSE is
used with a group defined as DEVICE=CCI and there is no TERM=TCP/IP parameter,
it forces termination of the CA WA CA 7 Edition CAICCI terminal session that is
active on that group. This should not be needed in normal operation.
If /CLOSE is used with any group defined as DEVICE=CCI and there is a TERM=TCP/IP
parameter, it forces termination of all TCP/IP sessions that are connected to the
port defined for the active CA WA CA 7 Edition instance.
TERM
(Optional) Defines the VTAM terminal to disconnect from CA WA CA 7 Edition or
specifies to terminate TCP/IP. T and TERM can be used interchangeably.
terminal
Specifies the VTAM terminal to disconnect from CA WA CA 7 Edition. The value
must be the NAME value on the TERM statement in the initialization file for the
VTAM terminal to disconnect.
TCP/IP
Specifies to terminate all TCP/IP sessions that are connected to the port
defined for the active CA WA CA 7 Edition instance when the GROUP
parameter is specified with any group defined as DEVICE=CCI.
Examples
/CLOSE,GROUP=CCIGRP1,TERM=TCP/IP
/CLOSE,GROUP=BGROUP1
/CLOSE,T=VTERM1
/CLOSE

/COID Commmand
/COID Commmand
The /COID command displays internal user IDs (UID, ranges from 1 through 999) and the
associated correspondence IDs (COIDS). The UID information comes from the active
USERID module, as defined on the SECURITY statement of the initialization file. You can
limit the display by coding a single ID. The default is to list all UIDs except 255.
/COID[,ID={*|nnn}]
ID
(Optional) Specifies the user ID for which to display the COIDs. You can enter one of
the following values:
*
Displays the COIDs for all currently defined user IDs that have a COID. This
value is the default.
nnn
Displays the definitions for a single user ID. Valid values are from 1 through 254
and from 256 through 999.
Examples
This example lists all user IDs that have corresponding COIDs.
/COID
*** CORRESPONDENCE ID DISPLAY *** PAGE 0001

USERID #COIDS --------------------------COIDS--------------------------
001 001 002

005 003 007, 009, 011
010 017 021, 022, 023, 024, 025, 070, 071, 072, 073, 074, 075, 076,
077, 078, 079, 080, 110
011 017 021, 022, 023, 024, 025, 070, 071, 072, 073, 074, 075, 076,
077, 078, 079, 080, 110
012 017 021, 022, 023, 024, 025, 070, 071, 072, 073, 074, 075, 076,
077, 078, 079, 080, 110
013 017 021, 022, 023, 024, 025, 070, 071, 072, 073, 074, 075, 076,
077, 078, 079, 080, 110
014 017 021, 022, 023, 024, 025, 070, 071, 072, 073, 074, 075, 076,
077, 078, 079, 080, 110
015 017 021, 022, 023, 024, 025, 070, 071, 072, 073, 074, 075, 076,
077, 078, 079, 080, 110
016 017 021, 022, 023, 024, 025, 070, 071, 072, 073, 074, 075, 076,
077, 078, 079, 080, 110
017 017 021, 022, 023, 024, 025, 070, 071, 072, 073, 074, 075, 076,
077, 078, 079, 080, 110
/CONT Command
This example lists a single UID.
/COID,ID=20
*** CORRESPONDENCE ID DISPLAY *** PAGE 0001

USERID #COIDS --------------------------COIDS--------------------------
020 017 021, 022, 023, 024, 025, 070, 071, 072, 073, 074, 075, 076,
077, 078, 079, 080, 110
SCM0-00 COMMAND COMPLETED AT hh:mm:ss ON yyddd
/CONT Command
The /CONT command formats a 3270-type terminal with constant data so that you can
enter additional data to complete a long input command. The /CONT command returns
a blank screen with two lines available for command input, allowing a command that is
160 characters long.
The command has the following format:
/CONT,{M|MSG}=text
M
Defines a character string to echo back to the terminal as part of a long command
containing more than 79 characters. If commas are included as part of the text,
enclose the entire message text in parentheses.
Usage Notes
The /CONT command is available only for VTAM and TSO/ISPF terminals.
Sometimes a command does not fit on the top line of the terminal. In this case, we
recommend that customers enter a partial command with a command continuation
character (CCC) following it on the top line instead of using the /CONT command.
CA WA CA 7 Edition generates the /CONT command internally when a CCC is entered.

The command is reported on the appropriate SASSHIS8 reports.
Note: For more information, see the Report Reference Guide.

/COPY Command
More information:
Examples
/CONT,M=FJOB
/CONT,M=(DEMAND,JOB=CA07XX01)
/COPY Command
The /COPY command sends a currently displayed page of output to another logical
terminal (station) in the CA WA CA 7 Edition terminal network. The STANIDS parameter
of the STATIONS statement in the initialization file identifies logical terminals.
/COPY[,{LT|LTERM}=station]
LTERM
(Optional) Defines a specific logical terminal (station) to which you want to copy the
currently displayed page of output. You can use LTERM and LT interchangeably. The
value must be a logical terminal name that is the same device type as the terminal
issuing the command. If omitted, the output is routed to the first hardcopy printer
(if one is defined) in the same LINE as the sending terminal.
Usage Notes
Use of /COPY without specifying a logical terminal name sends the output to the first
hardcopy printer if one is defined on the same line group as the sending terminal.
After the page of output has been copied, the next page of output is shown on the
requesting terminal.
If any of the following situations occur, the sending terminal receives an error message:
■ The specified logical terminal does not exist.
■ /COPY is used without a logical terminal being specified and no hardcopy device is
on the line.
/DELAGNT Command
■ The sending and receiving terminals are not the same device type.
A /COPY,LT=MASTER command is not valid when the MASTER is a browse data set.
Examples
/COPY,LT=KEYPUNCH
/COPY,LTERM=MAILROOM
/COPY,LTERM=PRINT1
/COPY
/DELAGNT Command
The /DELAGNT command scans the CA7AGNT file and compares each record creation
date to the current date minus AGENTDAY. One line of information is listed from each
record that is older than the AGENTDAY retention period. If UPDATE=YES is specified,
these records are also deleted from the CA7AGNT file. This maintenance command
removes historical records for space recovery.
/DELAGNT[,AGENTDAY=nn][,UPDATE={NO|YES}]
AGENTDAY
(Optional) Records in the CA7AGNT file older than this number of days are selected
for display and optional deletion. Specify a 1- or 2-digit value from 1 to 35.
If not specified, this value defaults to the AGENTDAY value specified in the
initialization file XPDEF statement. If not specified on the XPDEF statement, the
default is 15 days.
UPDATE
Determines whether to display records or to display and delete records.
NO
Lists records that are created earlier than AGENTDAY days before today. NO
the default.
All records remain in the CA7AGNT VSAM file.
YES
Lists records that are created earlier than AGENTDAY days before today.
All listed records are deleted from the CA7AGNT file.

/DELAGNT Command
Example
/DELAGNT,AGENTDAY=7
CA 7 WORKLOAD AUTOMATION - AGENT RECORDS OLDER THAN 07 DAYS PAGE 0001
Jobname Job# SCHID Q-Entry Agent Keyword Partial Content

AGNTCOM6 0002 001 D092151731 STATUS Lost control
USRESP01 0487 001 D092170613 USERO23ESP JNO 2908
USRI5000 0490 001 D092170722 STATUS ended in a norma
USRI5000 0490 001 D092170722 ESPAGENT113 JNO 248191
USRI5001 0492 001 D092171401 STATUS ended due to the
SCM4-00 REQUEST COMPLETED AT hh:mm:ss ON yy.ddd
This panel contains the following fields:

Jobname
Lists the job name that CA WA CA 7 Edition submitted.
Job#
Lists the CA 7 job number.
SCHID
Lists the schedule ID for this job.
Q-Entry
Specifies the date and time when the job was submitted.
Agent
Specifies the name of the agent where the job was submitted.
Keyword
Identifies the type of information in this record.
Partial Content
Provides a printout of the first 16 bytes of information in the record.
/DISPLAY Command
/DISPLAY Command
The /DISPLAY command obtains internal information, status of various components of
CA WA CA 7 Edition, or both. As an information command, it has a large group of
keywords available to designate specific information for display. You can specify certain
combinations of keywords on a single /DISPLAY command but must select at least one.
/DISPLAY[,{A|APPL}=programname]
[,CPU={ALL|UCC7IRDn|UCC7SUBn}]
[,DB={DATACOM|LOG]}
[,{FM|FMTBLK}=module]
[,{L|LINE}={line|mask|ALL}]
[,{LT|LTERM}={station|mask|ALL}]
[,PERF={ALL|DATACOM|JES|SCT|SUBSEL|VRM|ZOS|ZIIP}]
[,{PL|POOLS}=pools]
[,{PR|PRINT}={ALL|SCH}]
[,Q=queue]
[,{ST|STATUS}=status]
[,{T|TERM}={terminal|mask|ALL|*|?}]
APPL
(Optional) Defines the CA WA CA 7 Edition application programs whose status you
want to display. You can use A and APPL interchangeably.
SASSxxxx
Displays a specific CA WA CA 7 Edition module. The xxxx must be the last four
characters of the module suffix (for example, SLI0).
SASSxxx|SASSxx|SASSx
Displays a generic group of modules belonging to the same CA WA CA 7 Edition
application. All modules beginning with the characters specified are shown (for
example, SASSSLI displays all general listing modules).
ALL
Displays all CA WA CA 7 Edition modules that are defined in the initialization
file.
CPU
(Optional) Defines the submit data set or internal reader that is associated with the
CPUs for which to show status.
UCC7SUBn|UCC7IRDn
Defines the ddname that defines the desired submit data set.
ALL
Defines to show all submit data sets and their related MAINIDS.

/DISPLAY Command
DB
(Optional) Specifies information for which to display status.
DATACOM
Displays information about the CA Datacom/AD MUF in use and the trigger and
requirement display order.
LOG
Displays status of the log data set currently in use.
FMTBLK
(Optional) Defines the CA WA CA 7 Edition format or calendar blocks whose status
is shown. FM and FMTBLK can be used interchangeably.
SFMxyyyy|SFMxyyy|SFMxyy
Displays a generic group of format blocks belonging to the same CA WA CA 7
Edition application. The x portion of the name must be A for batch format
blocks, H for 3270 format blocks or X for both. The yyyy portion of the name
must be the four-character module suffix (for example, SLI0). All format blocks
beginning with the characters specified are shown.
SCALyyzz|SCALyyz|SCALyy
Displays a generic group of base calendar blocks. The yy portion of the name
represents the calendar year (that is, 13 for 2013). The zz portion of the name
represents the unique calendar identifier. All calendar blocks beginning with
the characters specified are shown. (Remember that you can use
LISTDIR,DSN=*SCAL* to display all the members in the Calendar PDS.)
ALL
Displays all format and base calendar blocks that are defined in the
initialization file with an FMTBLK or CALBLK statement.
LINE
(Optional) Defines the lines for which status is shown. L and LINE can be used
interchangeably.
line
Defines a single-line name.
mask
Defines a line name mask.
ALL
Displays all lines in the CA WA CA 7 Edition network. (The NAME parameter on
the LINE statement in the initialization file defines the line name.)
/DISPLAY Command
LTERM
(Optional) Defines the logical terminals for which status is shown. LT and LTERM can
be used interchangeably.
station
Defines a single logical terminal name.
mask
Defines a logical terminal name mask.
ALL
Displays status for all logical terminals in the CA WA CA 7 Edition network. (The
STANIDS or LTERM parameter on the STATIONS statement in the initialization
file defines the logical terminal name.)
PERF
(Optional) Indicates the type of performance-related data to collect and display as
one of the following values:
ALL
Collects all of the following types of performance data.
DATACOM
Collects CA Datacom/AD performance data.
JES
Collects JES performance data.
SCT
Collects SCT performance data.
SUBSEL
Collects enhanced submission selection performance data.
VRM
Collects VRM performance data.
ZIIP
Collects zIIP processing performance data.
Note: The PERF=ZIIP version of the command uses the same resources as other
critical processing areas. Frequent use can result in some slight performance
degradation.

/DISPLAY Command
ZOS
Collects z/OS performance data.
Note: The data that is collected is intended for use by the system programmer and
administrator who maintain the CA WA CA 7 Edition system. We do not recommend
this keyword for general use.
POOLS|PL
(Optional) Specifies the main memory storage pools for which status is shown. PL
and POOLS can be used interchangeably. Value must be one of the following values:
APG
Displays the CA WA CA 7 Edition application pool that provides main memory
for storing nonresident and nonpermanent programs while they are in use.
DSN
Displays the buffer pool that provides main memory for activity involving the
data sets.
G64
Displays the 64-bit memory pool that provides storage for scratch files and
other functions.
JOB
Displays the buffer pool that provides main memory for activity involving the
jobs.
MSG
Displays the message pool that provides main memory for CA WA CA 7 Edition
format blocks and their input/output activity. Values that are shown are the
same as those values for NSP because they are a shared pool.
NSP
Displays the nonspecific pool that provides main memory for all requests that
are not directed to one of the other pools. Values that are shown are the same
as those values for MSG because they are a shared pool.
N31
Displays the storage pool of areas residing in 31-bit addressability (areas that
are obtained above the 16-MB line).
RES
Displays the resident pool that contains the CA WA CA 7 Edition control blocks
and all resident CA WA CA 7 Edition programs.
ALL
Displays all storage pools previously listed.
/DISPLAY Command
PRINT
(Optional) Specifies a display of schedule scan control values. PR and PRINT can be
used interchangeably. If used, value can be either SCH or ALL.
Q
(Optional) Specifies the queue area for which status is shown. For the SCR and DQT
areas the values that are shown are DASD tracks allocated and currently available.
For all other areas, the values shown are 64-bit memory that is allocated and
currently available for in-core tables that are related to the queue area.
DQT
Displays the disk queue table that is used to control output messages for CA
WA CA 7 Edition terminals.
JCQ
Displays the 64-bit memory usage for the JCL Queue Table. This table contains
the JCL, PARMLIB data, and network reminder text for active jobs and
networks.
MSQ
Displays the 64-bit memory usage for the Miscellaneous Queue Table. This
table contains input requirements, output trailers, #SCC data, LOAD data, and
network stations for all jobs and networks in the status queues.
QHD
Displays the 64-bit memory usage for the Queue Header Table. This table
contains queue header data for all jobs and networks in the status queues.
SCR
Displays the scratch queue that provides a temporary workspace for the CA WA
CA 7 Edition applications and messages for the terminals.
STQ
Displays the 64-bit memory usage for the Status Queue Table. This table
contains information about active jobs and networks in each of the status
queues (PRE, REQ, RDY, ACT, and PST).
ALL
Displays all queue areas previously listed.

/DISPLAY Command
STATUS
(Optional) Specifies which status is shown. STATUS and ST can be used
interchangeably.
CA7
Displays information about the CA WA CA 7 Edition system such as
■ Local SMF ID
■ VTAM application ID
■ Instance name
■ SVC number
■ Status of the interfaces to external system state monitoring systems ARM,
CA OPS/MVS EMA SSM, and IBM Health Checker for z/OS
■ Time zone offset from UCT
■ Current settings for initialization file statements that relate to time zones
DPROC
Displays the CA Driver procedure libraries that are associated with CA WA CA 7
Edition JCL libraries. CA Driver procedure libraries are associated with JCL
libraries by adding DPROC= on the JCL statement in the initialization file or with
the /JCL command.
DR
Displays information about CA WA CA 7 Edition current disaster recovery mode
options and the currently active disaster recovery classes.
EMAIL
Displays information about the CA WA CA 7 Edition email interface.
HIJOB|HIJBNUM
Displays CA WA CA 7 Edition high job number statistics. HIJOB and HIJBNUM
can be used interchangeably.
JCL
Displays the data sets containing CA WA CA 7 Edition submitted JCL and their
associated numeric index values. Data sets that a symbolic index reference
display numeric index 255.
JCLVAR
Displays the data sets containing CA WA CA 7 Edition submitted JCL and their
associated numeric or symbolic index values.
/DISPLAY Command
KEY
Displays the program function and program access key settings.
Note: If key information is desired on a specific terminal, a combination of
STATUS=KEY and the TERM parameter can be used.
SDESK
Displays information about the CA Service Desk interface, including the current
SERVDESK rules that have been loaded.
SEC
Displays the current CA WA CA 7 Edition security environment.
Note: For more information, see the Security Reference Guide.
SUB
Displays information about CA WA CA 7 Edition job submission. The display
includes information about the number and type of submission output threads
that are currently active in CA WA CA 7 Edition.
XPS
Displays cross-platform scheduling options.
TERM
(Optional) Specifies the physical terminals for which status is shown. T and TERM
can be used interchangeably. (The NAME parameter on the TERM statement in the
initialization file defines the symbolic terminal name.)
terminal
Defines a terminal name.
mask
Defines a physical terminal name mask.
ALL
Specifies all physical terminals.
*
Specifies a condensed form of the ALL display.
?
Specifies an interpreted display for the issuing terminal.
More information:

/DISPLAY Command
Examples
/DISPLAY,CPU=ALL Command
/DISPLAY,CPU=ALL
*** CPU DISPLAY *** PAGE 0001

DDNAME BARRIER SUBMIT-COUNT MAINID
UCC7IRD1 020 000 SY1

SY3
SY0
SY*
UCC7SUB2 025 001 SY2

DDNAME
Identifies the name of the DD statement in the CA WA CA 7 Edition JCL that defines
this submit data set or internal reader.
BARRIER
Identifies the maximum number of CA WA CA 7 Edition jobs to submit to the host
system job queue at any one time.
SUBMIT-COUNT
Identifies the current number of jobs that are submitted to the host system job
queue at this time.
MAINID
Identifies the CA WA CA 7 Edition main IDs that are assigned to this submit data set
or internal reader.
/DISPLAY,DB=DATACOM Command
/DISPLAY,DB=DATACOM
*** DB DISPLAY *** PAGE 0001
Logical DB name: LOGICALDBNAME

CA Datacom rel : 14.0 MUF rel: 14.0
MUF name : DCOMAD14 STC43933 running on SYS1 connected locally
CA Datacom dataset names

CUSLIB : hlq.CUSLIB
CAAXLOAD : hlq.CAAXLOAD
DBPARMS : hlq.JCLLIB(DBPARMS)
/DISPLAY Command
/DISPLAY,DB=LOG Command
/DISPLAY,DB=LOG
*** DB DISPLAY *** PAGE 0001

DS TRACKS AVAIL
LOG 000150 000139 PRIMARY

DSN=cai.LOGP
SECNDRY
DSN=cai.LOGS
/DISPLAY,L=ALL Command
/DISPLAY,L=ALL
*** LINE DISPLAY *** PAGE 0001

I/O COUNTS FLAGS
LINE TYPE READS WRITES ERRORS 0 1 STATUS
HLINE1 3270R 00108 00124 00000 20 50

TLINE TRAILR 00000 00000 00000 20 50
CLINE CONSOL 00000 00001 00000 20 50
BLINE1 BATCH 00000 00000 00000 00 40 STOPPED.
/DISPLAY,LT=ALL Command
/DISPLAY,LT=ALL
*** LTERM DISPLAY *** PAGE 0001

WORKHOURS DISP FLAGS
LTERM TERM CALENDAR FROM TO #MSGS CUR NEXT 1 2 3 STATUS
HTERM1 HTERM1 SCALyy01 0800 1700 001 0328 0328 A0 00 00 OUTPUT,
CONTROL1 HTERM1 SCALyy01 0800 1700 000 0000 0000 00 00 00
CONTROL2 HTERM1 SCALyy01 0800 1700 000 0000 0000 00 00 00
CONTROL3 HTERM1 *NONE* 0000 2400 000 0000 0000 00 00 00
HTERM2 HTERM2 SCALyyPE 0600 1800 000 0328 0328 00 00 00
RECOVER1 HTERM2 SCALyyPE 0600 1800 000 0000 0000 00 00 00

LTERM
Identifies the logical terminal or workstation name. This name is either the value
that is entered on the STATIONS statement in the initialization file (keyword
STANIDS=) or a system-generated name for virtual terminals.
TERM
Identifies the terminal name, either specified on the TERM statement in the
initialization file (keyword NAME=), or a system-generated name for virtual
terminals.

/DISPLAY Command
CALENDAR
Identifies the calendar that is specified on the STNCAL statement in the initialization
file (keyword CAL=) for this workstation.
WORKHOURS
Identifies the FROM= and TO= values entered on the STNCAL statement in the
initialization file for this workstation.
#MSGS
Identifies the number of currently queued messages for this workstation.
DISP
Identifies the relative displacement into the scratch queue where current messages
reside.
FLAGS
Identifies the bit settings that relate to LTFLAG1, LTFLAG2, and LTFLAG3 as defined
in the DSECT SASSTBLK.
STATUS
Indicates a one-word description of the flag settings.
/DISPLAY Command
/DISPLAY,PERF=ALL Command
/DISPLAY,PERF=ALL
*** System Performance Information *** PAGE 0001
CA 7 start date/time: 20yy.262/10:54:54 Up time: 0:06:47:39

Collecting Metrics: Yes
*** MVS Performance Information ***
Task time: 0:00:00.12272 Dispatching priority: EE

Job task time: 0:00:03.81585 WLM service class: ONLTEST
SRB time: 0:00:00.20135
Preemptable SRB time: 0:00:00.27433
-------------
Total CPU time: 0:00:04.41427
I/O count: 9,522
Private storage:
<16M: 5,748K HWM: 5,748K Date/time: 20yy.262/10:56:02
>16M: 33,808K HWM: 33,808K Date/time: 20yy.262/10:57:02

CA 7 start date/time
Displays the time when the CA WA CA 7 Edition Online address space started on
this system.
Up time
Displays the number of days, hours, minutes, and seconds (d:hh:mm:ss) CA WA CA
7 Edition Online has been active.
Collecting Metrics
Displays whether CA WA CA 7 Edition metrics records are written to the log file.
Task Time
Displays the task time as recorded in the address space control block (ASCBEATT).
Dispatching Priority
Displays the current dispatching priority for the CA WA CA 7 Edition address space
from the address space control block (ASCBDP).
Job task time
Displays the job task time as recorded in the address space control block
(ASCBEJST).

/DISPLAY Command
WLM service class

Displays the currently assigned WLM service class when applicable (RASDSCL).
SRB time
Displays the SRB time as recorded in the address space control block (ASCBSRBT).
Preemptable SRB time
Displays the Preemptable SRB time as recorded in the address space secondary
block (ASSBPHTM).
Total CPU time
Displays the total of the preceding time fields (rounded).
I/O count
Displays the total I/O count CA WA CA 7 Edition has incurred after initiation
(ASCBIOSX).
Private storage:
<16M
Displays the current amount of storage that is used below the 16M line (LDALOAL).
HWM
Displays the highest amount of storage used (High-Water Mark) below the 16M
line.
Date/time
Displays the date and time that the high-water mark storage was used.
>16M
Displays the current amount of storage that is used above the 16M line (LDAELOAL).
HWM
Displays the highest amount of storage used (High-Water Mark) above the 16M
line.
Date/time
Displays the date and time that the high-water mark storage was used.
/DISPLAY Command
/DISPLAY,PERF=ALL
*** JES Information *** PAGE 0002
Subsystem Name: JES2
System Version Min DORM Max DORM Hold Status

*CA31 z/OS1.12 50 500 50 ACTIVE
CA11 z/OS1.12 50 500 50 ACTIVE

Asterisk (*)
Displays when this system is the local JES system in the JESPLEX.
System
Displays the system (member) name belonging to the JESPLEX.
Version
Displays the current version of the JES system.
Min DORM
Displays the minimum dormancy time for this system (JPX2MIND).
Max DORM
Displays the maximum dormancy time for this system (JPX2MAXD).
Hold
Displays the hold for this system (JPX2HOLD).
Status
Displays the status of the system.

/DISPLAY Command
/DISPLAY,PERF=ALL
** CA 7 SCT Performance Information ** PAGE 0003
SCT Name CPU Time Percent Description

SASSDAIO 0:00:00.00005 0.00 Queue I/O
SASSCHDO 0:00:00.00098 0.05 Output Msg Scheduler
SASSLMGR 0:00:00.06262 3.23 Line Manager
SASSHALT 0:00:00.00000 0.00 Shutdown Processor
SASSLOGM 0:00:00.27555 14.25 Log Manager
SASSCCIL 0:00:00.01068 0.55 XPS (CCI) Server Manager
SASSBTMG 0:00:00.00000 0.00 Subtask Manager
SASSCMGR 0:00:00.86956 44.97 Communications Manager
SASSSMF0 0:00:00.00000 0.00 SMF Processor
SASSSCNC 0:00:00.00025 0.01 Scan completed jobs mgr

SCT Name
Displays the name of the System Control Task (SCT) performing CA WA CA 7 Edition
tasks.
CPU Time
Displays the CPU time that is used after the start of CA WA CA 7 Edition by this SCT.
Percent
Displays the current percentage of the CPU time of the SCT compared to the total.
Note: This value is not the total CPU of the operating system, but only of the CA WA
CA 7 Edition address space. CA WA CA 7 Edition also has several subtasks that are
not displayed or accounted for here.
Description
Displays a short description of items that the SCT manages or processes.
/DISPLAY Command
/DISPLAY,PERF=ALL
*** CA 7 VRM/WLB/IAS Information *** PAGE 000n
Total number of jobs in Queues: 5

# jobs waiting for submission: 1
Current # jobs waiting on VRM: 1

VRM rejects for waiting jobs: 1
Current # jobs waiting on WLB: 0

WLB rejects for waiting jobs: 0
Current # jobs waiting on IAS: 0

IAS rejects for waiting jobs: 0

Total number of jobs in Queues
Displays the total number of jobs active in the request, ready, and active queues.
# jobs waiting for submission
Displays the number of jobs waiting on VRM, WLB, or IAS for submission.
Current # jobs waiting on VRM
Displays the total number of jobs currently waiting on one or more Virtual Resource
Management (VRM) resources.
VRM rejects for waiting jobs
Displays the accumulated number of times after CA WA CA 7 Edition initialization
jobs waiting for submission have been rejected due to waiting on VRM resources.
The higher the number here represents the total number of times the jobs could
have been submitted if not waiting on VRM.
Current # jobs waiting on WLB
Displays the total number of jobs currently waiting on WLB resources.

/DISPLAY Command
WLB rejects for waiting jobs

jobs waiting for submission have been rejected due to waiting on WLB resources.
The higher the number here represents the total number of times the jobs could
have been submitted if not waiting on WLB.
Current # jobs waiting on IAS
Displays the total number of jobs currently waiting on CA Integrated Agent Services
(CA IAS) activation.
IAS rejects for waiting jobs
jobs waiting for submission have been rejected due to CA IAS being unavailable. The
higher the number here represents the total number of times the jobs could have
been submitted if not waiting on CA IAS.
/DISPLAY,PERF=ALL
*** zIIP Processing Information *** PAGE 000n
*Agent Job Feedback Subtask

Total CPU used : 0.000501
TCB CPU : 0.000445
SRB CPU : 0.000055 SRB% : 10.97
CPU eligible zIIP: 0.000046
CPU on normal CP : 0.000000
CPU on zIIP : 0.000046 zIIP%: 100.00
# SRB starts : 1
Switches TCB->SRB: 2 SRB->TCB: 1

Total CPU used
Displays the total amount of CPU used by the subtask.
TCB CPU
Displays the amount of CPU used by the subtask while in TCB mode.
SRB CPU
Displays the amount of CPU used by the subtask while in SRB mode.
SRB%
Displays the percentage of CPU that is run in SRB mode.
CPU eligible zIIP
Displays the amount of CPU that can be run on a zIIP processor.
/DISPLAY Command
CPU on normal CP
Displays the amount of zIIP eligible CPU that has been run on a normal processor.
CPU on zIIP
Displays the amount of zIIP eligible CPU that has been run on a zIIP processor.
ZIIP%
Displays the percentage of zIIP eligible CPU that was run on a zIIP processor.
# SRB starts
Displays the number of times the SRB has been started.
Switches TCB->SRB
Displays the number of times that processing switched from TCB to SRB mode.
SRB -> TCB
Displays the number of times that processing switched from SRB to TCB mode.
/DISPLAY,PERF=ALL
*** Submission Selection Information *** PAGE 0011

Elapsed Time CPU Usage
*Overview 0:00:00.007384 0:00:00.000533
Task invocations : 3
Jobs selected : 0
*Workload Balancing 0:00:00.000000 0:00:00.000000
Environment model count : 0
*Candidate Selection 0:00:00.005608 0:00:00.000418
Database queries : 3
Jobs retrieved : 0
Jobs considered : 0
*Negative Requirements 0:00:00.000000 0:00:00.000000
Jobs with negative rqmts: 0
Negative rqmts read : 0
RDY/ACT Q jobs checked : 0
Neg rqmts not satisfied : 0
*ASX Virtual Resources 0:00:00.000000 0:00:00.000000
ASX resources checked : 0
Resources not satisfied : 0
*Virtual Resources 0:00:00.000000 0:00:00.000000
Resources not satisfied : 0

Task invocations
Displays the number of times within the interval that the enhanced submission
selection process has started.
Jobs selected
Displays the number of jobs that were successfully selected to be submitted within
the interval.

/DISPLAY Command
Environment modeling count

Displays the number of times that the WLB environment was constructed as part of
the submission selection process during the interval.
Database queries
Displays the number of calls to the database to gather jobs for submission
consideration.
Jobs retrieved
Displays the number of jobs that the database queries returned.
Jobs considered
Displays the number of jobs returned that the submission selection process
considered.
Jobs with negative rqmts
Displays the number of jobs that the candidate selection portion considered with
negative requirements.
Negative rqmts read
Displays the number of negative requirements, from all jobs considered, evaluated
by the submission selection process.
RDY/ACT Q jobs checked
Displays the number of jobs in the ready or active queues that were evaluated for a
negative requirement.
Neg rqmts not satisfied
Displays the number of negative requirements that were evaluated and found
currently unsatisfied. Jobs possessing these requirements are removed from the
selection consideration.
ASX resources checked
Displays the number of ASX resources, from all jobs considered, evaluated by the
submission selection process.
Resources not satisfied (ASX)
Displays the number of ASX resources that were evaluated and found currently
unavailable. Jobs requiring these resources are removed from the selection
consideration.
Resources not satisfied (VRM)
Displays the number of VRM resources that were evaluated and found currently
unavailable. Jobs requiring these resources are removed from the selection
consideration.
/DISPLAY Command
/DISPLAY,PERF=ALL
*** CA Datacom Information *** PAGE 0012
Area Name Total Blocks Used Blocks Percent Full

--------- ------------ ----------- ------------
AWH 24,300 3 0.01%
AWL 45,900 2 0.00%
AWS 105,300 48 0.04%
DFS 144,000 7,530 5.22%
HIL 24,300 1,613 6.63%
HIS 44,100 14,980 33.96%
IXX 208,800 48,397 23.17%
JOB 53,100 5,684 10.70%
MIN 6 3 50.00%

Area Name
Displays the name of the CA Datacom/AD area that CA 7 uses.
Total Blocks
Displays the total number of blocks that are allocated to this area.
Used Blocks
Displays the current number of blocks in use by this area.
Percent Full
Displays the percentage of blocks in use out of the total blocks that are allocated to
this area.
/DISPLAY,PL=ALL Command
/DISPLAY,PL=ALL
*** POOL DISPLAY *** PAGE 0001

POOL SIZE AVAIL. START
NSP 1754624 1681792 00087480

JOB 0000000 0000000 00054480
DSN 0004096 0004096 00054480
MSG 1754624 1678464 00087480
APG 0204800 0176064 00055480
RES 0131712 0000000 00034080
N31 2097088 2095936 22801040
G64 102400MB 102381MB 00000048_80000000

/DISPLAY Command
/DISPLAY,PR=SCH Command
/DISPLAY,PR=SCH
*** SCHEDULE SCAN DISPLAY *** PAGE 0001

-------------MINUTES-------------- ---STATUS----
NEXT SCAN SPAN INCR QDWL REPR LDTM RTRY XTRY REQ/Q RDY/Q ABR HOLD
99.999 AT 0000 0240 0120 0030 0010 0000 0005 0040 ACTIVE ACTIVE NO NO

NEXT SCAN
Identifies the date and time of the next scheduled wake-up for schedule scan.
SPAN
Identifies the value in minutes of how far ahead to look for calendar scheduled jobs
and networks with a deadline date and time that correspond to the time frame
being scanned.
INCR
Identifies the number of minutes between wake-ups of schedule scan.
QDWL
Identifies the number of minutes added to the SPAN value to help ensure timely
scheduling of work into the queues.
REPR
Identifies the number of minutes between prompt cycles for late tasks or jobs, or
jobs awaiting restart.
LDTM
Identifies a global value to add to the lead time of all jobs.
RTRY
Identifies the number of minutes between the retry of attachment of JCL after a
dynamic allocation failure.
XTRY
Identifies the number of minutes between the retry of attachment for XPJOB jobs
that have encountered a node failure.
STATUS
Identifies whether the request and ready queues are ACTIVE or STOPPED (see the
STOP and START commands).
/DISPLAY Command
ABR
Identifies whether to issue the initial queue entry message in abbreviated form (see
the SSCAN command SCAN=ABR).
HOLD
Identifies whether jobs enter the request queue with an initial hold requirement
(see the SSCAN command SCAN=HLD).
/DISPLAY,Q=ALL Command
/DISPLAY,Q=ALL
*** Queue Display *** Page 0001

Queue Tracks Avail.
SCR 000500 000498
DQT 000050 000048
Queue Size Avail. Start

QHD 000021MB Fixed 0000004B_C3400000
STQ 000008MB Fixed 0000004B_C4900000
JCQ 000200MB 000199MB 0000004B_C5100000
MSQ 000002MB 000001MB 0000004B_D1900000
SCM6-00 /DISPLAY COMPLETED AT hh:mm:ss ON yyddd
/DISPLAY,ST=CA7 Command
/DISPLAY,ST=CA7
*** CA 7 System Information *** Level: r12.0 DATE=yy.ddd TIME=13:16:44
Host System SMFID : CA01 ARM : Disabled --------

CA 7 VTAM Appl ID : A01IL24 OPS/MVS SSM : Disabled --------
CA 7 Instance Name: CA74 Health Checker : Enabled Intv(15)
CA 7 SVC Number : 167 CA 7 TZ Offset : -05:00
CCI Local SYSID : A01SENF TZDISPLAY Value: EXEC
CA 7 CTI Suffix : CA74 TZPREDS Value : EXEC
TCP/IP Host Name : USILCA01 TCP Port: 4074
TCP/IP Host Addr : 141.202.99.255
JFM Port : 14811
CA 7 Started : 2015-01-05 10:34 ENF Started : 2015-01-15 12:34

/DISPLAY Command
/DISPLAY,ST=EMAIL Command
/DISPLAY,ST=EMAIL
DATE = yy.ddd TIME = 15:12:03
CURRENT EMAIL SETTINGS

----------------------
INITIALIZED : YES
ENABLED : YES
GLOBAL TRACE : NO
TCP/IP TIMEOUT: 10 SECONDS
SMTP PORT # : 00025
FROM NAME :
CA-7
REPLY ADDRESS :
[email protected]
TOTAL REQUESTS: 00000000
ADDRESS DSN : cai.ADDRLIB
TEMPLATE DSN : cai.EMAILLIB
/DISPLAY,ST=HIJOB Command
/DISPLAY,ST=HIJOB
*** CA 7 High Job Number Statistics *** DATE=yy.mmm TIME=12:15:38
Highest allowed number : 1,000

Last number assigned : 299
Highest number assigned : 996
Currently assigned count: 15
Percent currently used : 1.50%
/DISPLAY,ST=JCL Command
/DISPLAY,ST=JCL
*** JCL DISPLAY *** PAGE 0001

DATASET NAME INDEX ALT DSORG VOLSER LTERM
D463RV1.PROC.CLIST 250 N/A PDS M80T82 MASTER

CA007.JCLDS1 000 250 PDS M80008 MASTER
SYS2.PROCLIB 200 N/A PDS M80PP1 MASTER
CAI.CA7.CAIHELP 255 N/A PDS M80008 MASTER
/DISPLAY Command
/DISPLAY,ST=JCLVAR Command
/DISPLAY,ST=JCLVAR
*** SYMBOLICALLY INDEXED LIBRARY DEFS FROM DATABASE *** PAGE 0001
VARIABLE/INDEX DATASET NAME ALT DSORG VOLSER LTERM
000 CA007.JCLDS1
250 PDS M80008 MASTER
200 SYS2.PROCLIB
N/A PDS M80PP1 MASTER
250 D463RV1.PROC.CLIST
N/A PDS M80T82 MASTER
&HELP CAI.CA7.CAIHELP
N/A PDS M80008 MASTER
&PAYROLL CA007.PAYROLL
&PAYABLE CA007.ACCTS.PAYABLE
&RECEIVABLE CA007.ACCTS.RECEIVBL
/DISPLAY,ST=KEY Command
/DISPLAY,ST=KEY
*** KEY DISPLAY *** (VTERM1) PAGE 0001

KEY FUNCTION
--- INITIALIZATION ---

PF12 VTAM LOGOFF KEY
--- DEFAULT ---
PF01 /PURGPG
PF02 /FETCH
PF03 /NXTMSG (FORMATTED SCREENS USE PF3 TO RETURN TO MENU)
PA01 /PAGE+1 (FORMATTED SCREENS USE PF8 FOR /PAGE+1)
PA02 /PAGE-1 (FORMATTED SCREENS USE PF7 FOR /PAGE-1)
/DISPLAY,ST=SUB Command
/DISPLAY,ST=SUB
*** SUBMISSION OUTPUT THREAD STATUS *** PAGE 0001
*THREAD* **ADDR** S1 S2 S3 S4 JOBNAME CA-7# JSTA PRE PRC PST #JOB #BSY
SASSSO01 0023A508 00 00 00 00 00000 0000 0000 0000 0000 0000 0000

SASSSO02 0023A978 00 00 00 00 00000 0000 0000 0000 0000 0000 0000
SASSSO03 0023ADE8 00 00 00 00 00000 0000 0000 0000 0000 0000 0000
SASSSO04 0023B258 00 00 00 00 00000 0000 0000 0000 0000 0000 0000
SASSSO05 0023B6C8 00 00 00 00 00000 0000 0000 0000 0000 0000 0000
**ALL** 0000 0000

/DISPLAY Command
/DISPLAY,ST=XPS Command
/DISPLAY,ST=XPS
*** Cross-Platform Scheduling Options *** DATE=yy.mmm TIME=12:13:18
CCI Local SYSID : A31SENF Host System SMFID : CA31

CA 7 Monitor Name : CA7CA75 CA 7 VTAM Appl ID : A31IL25
CA 7 HAO Primary : CA75PRIME CA 7 Instance Name: CA76
XPJOB Submit : Yes

XPJOB PSWD Location: (DATABASE,OWNER,USER,NODE)
XPJOB Submit ROOT : Yes
XPJOB Kill : Yes
XPJOB Tracker Task : Yes - Active Tracker Initial Trace : 11
XPS Router Task : No - Inactive Router Initial Trace : 11

XPS Server : Yes Server Initial Trace : No
XPS Default Mode : RUNREF
XPS Default ID : **NONE**
Agent Jobs Enabled : Yes

Agent Information Days: 15
Agent IAS Interface : Active
/DISPLAY,T=* Command
/DISPLAY,T=*
*** TERM DISPLAY *** PAGE 0001

--I/O COUNTS--- OUT TIM MON
NAME ID/TYPE READS WRITE ERR Q'D LIM LIM STATUS
HTERM A46L6016 00049 00048 000 000 030 002 MSTR,SKIP,CONN,

OLC001 OLC001 00003 00003 000 000 030 002 LOFF,ALT,STOP
/DISPLAY Command
/DISPLAY,T=? Command
/DISPLAY,T=?
TIM MON SIM
TERM--- ID------ TYPE---- ADDR READS WRITE ERR MSGS LIM LIM LOG LOGGED
HTERM A46L6016 3270V 0000 00050 00049 000 000 030 002 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 OR TCP/IP SESSION NOT ACTIVE
/DISPLAY,T=ALL Command
/DISPLAY,T=ALL
*** TERM DISPLAY *** PAGE 0001

--I/O COUNTS--- OUT -LIMIT- ---FLAGS---
TERM TYPE ADDR READS WRITE ERR Q'D TIM MON 0 1 2 V STATUS/(VTAMID)
HTERM1 3270R 0004 00041 00042 000 001 020 020 D0 28 02 04 MSTR,
HTERM2 3270R 0004 00075 00075 000 000 020 020 D4 30 02 04 ALT,SKIP,
PTERM1 3270R 0004 00000 00015 000 000 030 002 54 24 02 04 LOFF,SKIP,
TTERM1 TRAILR 0004 00000 00000 000 000 030 002 D0 20 00 04 LOFF,
CTERM1 CONSOL 0004 00000 00001 000 000 030 002 D0 20 00 04 LOFF,
BTERM1 BATCH 0004 00000 00000 000 000 030 002 00 20 00 04 LOFF,STOP

TERM
Identifies the terminal name from the initialization file TERM statement (keyword
NAME=). For virtual terminals, this value is a system-generated name.
TYPE
Identifies the device type for this terminal defined by the DEVICE= on the TERM
statement in the initialization file.
ADDR
Identifies the relative address for local BTAM terminals.

/DISPLAY Command
READS
Identifies the number of reads for this terminal during this session of CA WA CA 7
Edition.
WRITE
Identifies the number of writes for this terminal during this session of CA WA CA 7
Edition.
ERR
Identifies the number of errors during this session of CA WA CA 7 Edition. Typically
messages are produced as WTOs (for example, CA-7.V001 messages) to explain the
errors.
Q'D
Identifies the number of messages currently queued for this terminal.
TIM
Identifies the number of minutes of inactivity before the terminal is automatically
disconnected from CA WA CA 7 Edition.
MON
Identifies the number of minutes of inactivity in the interface of CA 1 or CA 11
before the terminal is automatically returned to CA WA CA 7 Edition.
FLAGS
Identifies the flag settings used by the terminal.
STATUS
Indicates the following:
ALT
Indicates the TERM statement uses CONS=ALTRN.
CONN
Indicates the terminal is connected (VTAM).
LOFF
Indicates the terminal is logged off.
MSTR
Indicates the TERM statement uses CONS=MASTR.
SKIP
Indicates the terminal is busy processing a command.
STOP
Indicates the terminal has been stopped.
/DMP1 Command
/DMP1 Command
The /DMP1 command is the same as the /DUMP command, except that it does not
generate a storage dump. The command also causes a user 444 (U0444) abend.
/DMP1
More information:
/DUMP Command (see page 103)
/DRCLASS Command
The /DRCLASS command adds or removes a disaster recovery class from the list of active
disaster recovery classes. Disaster recovery classes have no impact on CA WA CA 7
Edition processing unless CA WA CA 7 Edition is running in disaster recovery mode.
Changes to the active disaster recovery class list are not saved across restarts of CA WA
CA 7 Edition. To make a disaster recovery class active when CA WA CA 7 Edition starts,
add the class to the DRCLASS initialization file statement.
Use /DISPLAY,ST=DR to display the list of active disaster recovery classes.
/DRCLASS,CLASS=(xx1,...,xx8)[,ACT={ADD|DEL}]

/DRMODE Command
CLASS
Defines one to eight disaster recovery classes to add or remove from the list of
active disaster recovery classes. Each disaster recovery class can be one to eight
characters long. Separate the disaster recovery classes with commas and enclose
them in parentheses. If you specify a single disaster recovery class, you can omit the
parentheses.
ACT
(Optional) Defines the action to perform on the disaster recovery classes that are
specified on the CLASS keyword.
ADD
Adds the classes to the list of active disaster recovery classes. ADD is the
default value.
DEL
Removes the classes from the list.
Examples
/DRCLASS,CLASS=TIER1
/DRCLASS,CLASS=(TIER2,TIER3),ACT=ADD
/DRCLASS,CLASS=TIER3,ACT=DEL
/DRMODE Command
The /DRMODE command turns on or off disaster recovery mode and changes the
disaster recovery mode options.
/DRMODE[,DEFCLASS={@SYSTEM|value}]
[,MODE= {DR|NORM}]
[,RQMTS={DR|ALL}]
[,TRIGGERS={DR|ALL|NONEXEC}]

/DRMODE Command
DEFCLASS
(Optional) Defines a rule for CA WA CA 7 Edition to determine a disaster recovery
class for a job when a disaster recovery class has not been assigned to the job. If
DEFCLASS=@SYSTEM, the SYSTEM value of the job is used as the disaster recovery
class. Any other value of DEFCLASS is used as the disaster recovery class of the job.
MODE
(Optional) Specifies the CA WA CA 7 Edition mode.
DR
Specifies disaster recovery mode.
NORM
Specifies normal mode.
For cautions about turning on disaster recovery mode, see the usage notes that
follow.
RQMTS
(Optional) Determines how CA WA CA 7 Edition handles unsatisfied job
requirements.
DR
Specifies CA WA CA 7 Edition satisfies the job requirement when the
predecessor job has an inactive disaster recovery class.
ALL
Specifies CA WA CA 7 Edition leaves the requirement unsatisfied (as if CA WA
CA 7 Edition were not running in disaster recovery mode).
TRIGGERS
(Optional) Specifies whether CA WA CA 7 Edition triggers jobs with an inactive
disaster recovery class when CA WA CA 7 Edition is running in disaster recovery
mode.
DR
Specifies CA WA CA 7 Edition does not trigger jobs with an inactive disaster
recovery class.
ALL
Specifies CA WA CA 7 Edition triggers jobs normally (as if CA WA CA 7 Edition
were not running in disaster recovery mode).
NONEXEC
Specifies CA WA CA 7 Edition triggers, but marks as nonexecutable, jobs with
an inactive disaster recovery class.
Note: For more information about nonexecutable jobs, see the EXEC field
description on the job definition panel in the Database Maintenance Guide.

/DUMP Command
Usage Notes
Important! Read the topic about the Disaster Recovery Mode in the Systems
Programming Guide before running CA WA CA 7 Edition in disaster recovery mode.
Because CA WA CA 7 Edition does not provide any default active disaster recovery
classes, schedule scan running in disaster recovery mode does not bring any jobs into
the request queue.
We recommend making one or more disaster recovery classes active (either with the
DRCLASS initialization file statement or the /DRCLASS command) before starting disaster
recovery mode.
Examples
/DRMODE,MODE=DR
/DRMODE,TRIGGERS=ALL,RQMTS=ALL
/DRMODE,DEFCLASS=@SYSTEM
/DUMP Command
The /DUMP command causes an abnormal termination of CA WA CA 7 Edition. A user
444 abend results and a storage dump is generated.
Important! We advise extreme CAUTION before using this command because a loss of
data can result.
/DUMP
Usage Notes
Under normal circumstances, using this command (or /DMP1) is not necessary. If it is
necessary to terminate CA WA CA 7 Edition execution with the option to reactivate CA
WA CA 7 Edition with a WARM start, use the /SHUTDOWN command.
More Information:
/SHUTDOWN Command (see page 141)

/EADMIN Command
/EADMIN Command
The /EADMIN command modifies selected settings of the CA WA CA 7 Edition email
interface. Changes that are made using the /EADMIN command are not saved across
starts of CA WA CA 7 Edition. For permanent changes, update the EMAIL initialization
file statement.
/EADMIN[,EFROM=xxx...x]
[,ENABLE={Y|N}]
[,EREPLY=xxx...x]
[,ETIMEOUT=nn]
[,TRC={Y|N}]
EFROM
(Optional) Specifies a new name to display in the "From" field of emails. The value
can be up to 70 characters long and can contain special characters (other than
commas). CA WA CA 7 Edition converts all lowercase letters to uppercase when
processing the command.
ENABLE
(Optional) Specifies whether to use the email interface. All emails can be
suppressed by specifying ENABLE=N. All emails currently waiting to be sent are
discarded with no indication of any error. Any new emails that are requested with
the /EMAIL command are also discarded, and an error message (SCMR-07) is issued
to the terminal in response to the command. Specify /EADMIN,ENABLE=Y to permit
the sending of emails again. /EADMIN,ENABLE=Y can also be used to redrive a
connection to TCP/IP if one was not successfully established at initialization.
EREPLY
(Optional) Specifies a new default email reply address to use when email recipients
reply to emails from CA WA CA 7 Edition. The value can be up to 70 characters long
and can contain special characters (other than commas). CA WA CA 7 Edition
converts all lowercase letters to uppercase when processing the command. The
email address member "reply:" line can override the reply address.

/ECHO Command
ETIMEOUT
(Optional) Specifies the maximum number of seconds CA WA CA 7 Edition waits for
responses from TCP/IP and the SMTP (email) server. Values can range from 5 to 20
seconds.
TRC
(Optional) Specifies whether to turn on or off the email trace globally. The email
trace is written to SYSOUT data set ETRACE in the CA WA CA 7 Edition task and
contains information about the connection between CA WA CA 7 Edition and TCP/IP
and the conversation with the SMTP (email) server. The trace can produce 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=Y on the /EMAIL command.
/ECHO Command
The /ECHO command either echoes input data back to the sending terminal or formats a
3270-type terminal with constant data so that additional data can then be entered to
complete an input command. This command is especially useful in combination with the
/PF and /PA commands to allow a lengthy command format to be called up onto a
terminal with a single keystroke.
/ECHO,{M|MSG}=text
MSG
Defines a character string to echo back to the terminal. MSG and M can be used
If the last character of the MSG text is a # sign, the cursor is moved to that location
when the command is echoed to the terminal. This method is provided to allow
preformatting of command input.
Usage Notes
The command continuation character (CCC) is not valid with the /ECHO command.
More Information:

/EMAIL Command
Examples
/ECHO,M=THIS IS AN ECHO BACK
/ECHO,M=(LJOB,JOB=#)
/ECHO,MSG=PUT THIS ON THE PANEL #
/EMAIL Command
The /EMAIL command creates and queues an email request to the CA WA CA 7 Edition
email interface.
Note: The first time this command is issued, it also attempts a connection to TCP/IP if
one was not successfully established at initialization.
/EMAIL,TO=member,TXT=member
[,JOB={jobname|jobnumber}]
[,TRC={N|Y}]
[,VAR=(value1,...value8)]
TO
Defines the member in the EADDRLIB PDS that contains the email addresses of the
recipients for this email. Up to 100 email addresses can be specified in the member,
each starting in column 1 and each up to 70 characters long. The email address
member can also contain an override of the email reply address.
Note: For more information about the format of the email address member, see the
Interface Reference Guide.
TXT
Defines the member in the EMAILLIB PDS that contains the email template for this
email. The template defines the contents of the subject and body of the email.
Note: For more information about the format of the email template member, see
the Interface Reference Guide.
JOB
(Optional) Defines a job in the CA WA CA 7 Edition queues. If specified, the queue
information of the job is used to populate variables that can be substituted in the
email template. Either a job name or a CA 7 job number can be specified. If a job
name is entered, and multiple jobs with that name exist in the database, then the
first job that is found is used. The queues are searched in the order REQ, RDY, and
ACT.

/FETCH Command
TRC
(Optional) Specifies whether to trace this email request. The email trace is written
to SYSOUT data set ETRACE in the CA WA CA 7 Edition task and contains
information about the connection between CA WA CA 7 Edition and TCP/IP and the
conversation with the SMTP (email) server.
VAR
(Optional) Defines one to eight values for email template variables &VAR1 to
&VAR8. Each value can be up to eight characters long. CA WA CA 7 Edition converts
lowercase letters to uppercase when processing the command.
Note: For more information about using variables in email, see the Interface
Reference Guide.
/FETCH Command
The /FETCH command retrieves top line commands that are entered since the last
/LOGON.
Commands that are entered on the top line are stored in a buffer that is known as a
command ring. The command ring can hold up to five top line commands. When you
enter the sixth command, the oldest command in the ring is erased to store the new
one. In this way, the five most recent commands are saved.
You can override the default number of commands stored in the command ring buffer
using the MAXRINGSZ= keyword on the OPTIONS statement in the initialization file.
Note: For more information, see the Systems Programming Guide.
Repeated executions of /FETCH retrieve commands in the order that they are 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
Usage Notes
When displaying a long command in an online environment, the /FETCH command first
blanks out the screen. Subsequent /FETCH commands do not redisplay the screen data
that was blanked.
If a command continuation character (CCC) is entered, it is ignored.

/GVAR Command
More Information:
/GVAR Command
The /GVAR command adds, updates, or deletes a global variable referenced by a
user-defined symbolic name that may be used in a JCL or PARM statement. Global
variables are prefixed by a one- to four-character prefix defined by the GVARSUB
assignment in the OPTIONS statement.
Global variables reside in the CA WA CA 7 Edition database and remain in effect when
CA WA CA 7 Edition is reinitialized. Variable names are user-defined but may not match
the list of reserved variables described in the Interface Reference Guide.
The command has the following format:
/GVAR,OPT={ADD|DEL|MOD|UPD},NAME=variable
[,JOB={jobname|mask|*}]
[,SCHID={0|nnn|*}]
[,SYS={systemid|mask|*}]
[,{VAL|VALUE}=string]
OPT
Specifies the type of operation to be performed.
ADD
Specifies to add a global variable.
DEL
Specifies to delete a global variable. This option will delete multiple matching
table entries if one or more JOB, SYS, or SCHID parameters is set to *. Only
JOB=*, SYS=*, or SCHID=* will cause multiple deletes to occur with one
command. That is, the following command deletes only a single entry with the
"specific" generic JOB value of JOB* and not delete TEST variables with
JOB=JOBA, JOBB, and so forth:
/GVAR,OPT=DEL,NAME=TEST,JOB=JOB*

/GVAR Command
MOD
Performs one of the following actions:
■ If the variable exists, this option functions like UPD, and the variable is
updated.
■ If the variable does not exist, this option functions like ADD, and the
variable is added.
UPD
Specifies to change the value of a global variable.
NAME
Defines the name of a global variable. This is a 1- to 32-character alphanumeric field
with no embedded blanks. If more than 32 characters are entered, they are
truncated to 32 characters. Special characters are limited to #, $, @, _ and %.
Multiple assignments can be made to the same variable name for each combination
of JOB, SYSTEM, and SCHID. Lowercase characters are translated to uppercase. Only
a specific name is supported for multi-delete. A generic NAME, such as NAME=* is
not accepted.
JOB
(Optional) Specifies a job name or mask.
Default: blank
jobname
Defines the job name or mask for job names that will use this specified value of
this global variable. If no job name or mask is specified, the VALue is the default
substitution value for all jobs. Lowercase characters are translated to
uppercase. If more than 8 characters are entered, they are truncated to 8
characters.
*
For OPT=ADD|UPD|MOD, is equivalent to blank. For OPT=DEL, allows multiple
deletions of the same NAME with any JOB setting.
SCHID
(Optional) Specifies a schedule ID.
nnn
Defines the CA WA CA 7 Edition schedule ID that will use this specified value of
this global variable. If no SCHID is specified, this is the default substitution value
for all schedule IDs. The default is 0.
*
For OPT=ADD|UPD|MOD, * is equivalent to 0. For OPT=DEL, * allows multiple
deletions of the same NAME with any SCHID setting.

/IAS Command
SYS
(Optional) Specifies a system name or mask.
Default: blank
systemid
Defines the system name or mask for system names that will use this specified
value of this global variable. If no system name or mask is specified, the VALue
is the default substitution value for all systems. Lowercase characters are
translated to uppercase. systemid can include leading and embedded blanks
without parentheses. Trailing blanks are not significant. If more than 8
characters are entered, they are truncated to 8 characters. Parentheses can be
used and are not retained if ( is the first character and ) is the delimiter.
*
For OPT=ADD|UPD|MOD, * is equivalent to blank. For OPT=DEL, * allows
multiple deletions of the same NAME with any SYS setting.
VAL|VALUE
(Optional) Specifies the character string to replace the global variable. It is a 1- to
44-character field that can include any printable characters. If more than 44
characters are entered, they are truncated to 44 characters. Embedded and trailing
blanks can be included when the entire string is enclosed by parentheses. The
system removes the parentheses, which do not count towards the value length. val
can include leading and embedded blanks without parentheses, but trailing blanks
are counted in the length only if ( is the first character and ) is the delimiter. The
keyword can be included for OPT=DEL but is ignored.
Limits: Required when OPT=ADD|UPD|MOD
More Information:
/IAS Command
The /IAS command requests CA Integrated Agent Services (CA IAS) to perform a specific
function. These functions fall into the following two broad categories:
■ Agent administration functions
■ Log administration functions
Agent administration functions act on agents. These functions can add, delete, or
change agent and agent manager definitions. These functions can also shut down all
communications to agents and restart those communications.

/IAS Command
Log administration functions act on the CA IAS log or the internal CA WA CA 7 Edition
logging abilities. The CA IAS log is a wraparound log of messages in storage. The /IAS
functions that start with LOG control this storage. Each log message has a log type that
is associated with it. Log types are turned on and off to control which messages are
stored in the CA IAS log area. The internal logging abilities cause CA WA CA 7 Edition to
create a log record containing the AFM that is being sent or received. These records are
written to the LOGP/LOGS data sets and can create many log records and therefore
should remain off unless CA Support directs. The /IAS functions beginning with AGLOG
control this option.
/IAS,FUNC=function[,LOGDD=ddname][,LOGTYPE=nnn]
FUNC
Specifies the specific function that CA IAS is to perform. Valid values are the
following items:
AGLOGOFF
Turns off the internal CA WA CA 7 Edition AFM tracing facility.
AGLOGON
Turns on the internal CA WA CA 7 Edition AFM tracing facility.
LOGCLEAR
Clears the CA IAS log file.
LOGPRINT
Prints the CA IAS log file to the ddname that the LOGDD value indicates.
LOGRESET
Turns off a CA IAS log type. The LOGTYPE value indicates the log type.
LOGSET
Turns on a CA IAS log type. The LOGTYPE value indicates the log type.
LOGSTART
Starts or resumes logging.
LOGSTOP
Suspends the logging function.

/JCL Command
RECONFIG
Activates additions, deletions, and changes made to agents in the IASAGENT
DD statement.
STARTCOM
Initializes communications between agents and CA WA CA 7 Edition. This
function is used after the STOPCOM function is executed.
STOPCOM
Stops communications between agents and CA WA CA 7 Edition. This function
is typically used to stop sending all jobs to agents for execution.
LOGDD
(Optional) Specifies the ddname to contain the printed log file. This parameter is
required for the LOGPRINT function and ignored on all other functions. CA IAS
dynamically allocates a sysout file to this ddname, writes the current log records to
it, and then dynamically frees the ddname. The LOGDD value must follow IBM
naming standards for ddnames.
LOGTYPE
(Optional) Specifies the CA IAS message log type to turn on or off. This parameter is
required for the LOGSET and LOGRESET functions and ignored for all other
functions. Valid values are 1 through 127.
/JCL Command
The /JCL command adds, updates, or deletes a JCL statement that a symbolic index
references.
Note: The /JCL command can manipulate the PRMLIB data sets because these data sets
are considered "JCL" libraries. PARM data members can occupy the same libraries as JCL
members because the data is 80-byte records in a PDS.
Changes made to JCL statements with the /JCL command are stored in the CA WA CA 7
Edition database and remain in effect when CA WA CA 7 Edition is reinitialized if
JCLDEFS=VSAM is specified on the RESIDENT statement in the initialization file.
Note:
■ For more information about using symbolic indexes to refer to JCL data sets, see the
Systems Programming Guide.
■ Any changes to JCL library definitions are LOST when CA WA CA 7 Edition is recycled
unless JCLDEFS=VSAM is specified on the RESIDENT statement in the initialization
file. See the discussion of this keyword on the RESIDENT statement in the Systems
Programming Guide.

/JCL Command
/JCL,OPT={ADD|UPD|DEL},INDEX=jcllib,DSN=dsname
[,ALT={nnn|xx...x|NO}]
[,DPROC={dsname|NO|*NONE*}]
[,LTERM={MASTER|xxxxxxxx}]
OPT
Specifies the type of JCL statement change to perform.
ADD
Specifies to add a symbolic JCL data statement reference.
UPD
Specifies to update a symbolic JCL data statement reference.
DEL
Specifies to delete a symbolic JCL data statement reference.
INDEX
Defines the symbolic index that is associated with the JCL statement. A symbolic
index is referred to as a JCLLIB on the DB.1 panel. A symbolic index consists of an
ampersand (&) followed by up to 15 alphanumeric characters. Symbolic value
&HELP is reserved for the HELP data set.
DSN
Defines the fully qualified name of a data set containing execution JCL for CA WA CA
7 Edition to submit. The data set must be a PDS. A data set name cannot be
specified with OPT=DEL.
Note: JCL libraries added with the /JCL command are automatically assigned an
attribute of DYN=2.
TSO packed data is not supported.

/JCL Command
ALT
(Optional) Specifies JCL library destination.
nnn
xx...x
Defines the INDEX value from a previously defined JCL library that is searched
before this one. This method works exactly like DD statement concatenation
where the ALT is first in the sequence, but is supported for only one level.
Because validation of this parameter is done during the building of the internal
table of JCL libraries, the alternate library must be defined in the initialization
file before the statement that references it as an alternate. ALT and INDEX
values cannot be equal in any one JCL statement.
Note: For more information about alternate JCL libraries, see the Database
Maintenance Guide.
NO
Specifies to remove an ALT destination from an existing JCL library destination,
as in the following example:
/JCL,INDEX=index,OPT=UPD,ALT=NO
DPROC
(Optional) Specifies CA Driver JCL libraries.
dsname
Defines the name of the PDS to concatenate above the libraries in the
CARPROC DD allocation whenever CA Driver is invoked for JCL in the associated
JCL library.
NO
Specifies to remove a DPROC association from an existing definition, as in the
following example:
/JCL,INDEX=index,OPT=UPD,DPROC=NO
*NONE*
Specifies not to invoke CA Driver for JCL using this INDEX.
LTERM
(Optional) Specifies the logical terminal to which to route prompt messages for jobs
using JCL from this library. The default is MASTER.
Note: If the logical terminal name is defined as a virtual terminal, a CAICCI terminal,
or CONSOLE, the messages are dynamically rerouted to the MASTER terminal.
Messages that are routed to the MASTER terminal are written to the BROWSE DD
file.
Note: For more information about the LTERM keyword or the JCL initialization file
statement, see the Systems Programming Guide.

/LOG Command
/LOG Command
The /LOG command adds free-form text to the CA WA CA 7 Edition log data set. Use
these entries to document situations occurring during production, such as why a job is
late or canceled. You can review this text later through the batch report CA7xx032.
/LOG,{D|DATA}=data
DATA
Defines data to log to the log data set. DATA and D can be used interchangeably,
but one or the other is required. If commas are included as part of the data, enclose
the entire data text in parentheses.
Usage Notes
The data is written to the log data set and is stamped with the following items:
■ Current date and time-of-day
■ Terminal ID
■ Operator ID (depending on your installation options)
See report request ID CA7xx032 in the Report Reference Guide for a report that reflects
/LOG information.
Examples
/LOG,D=(PAYROLL SOURCE INPUT RECD, 45 MIN LATE)
/LOG,DATA=CA07JOB1 CANCELED
Note: Current date and time are added to the text when the log record is written.

/LOGOFF Command
/LOGOFF Command
The /LOGOFF command informs the CA WA CA 7 Edition system that a terminal is going
inactive. Whenever a terminal is to be inactive for some time, it is best to issue a
/LOGOFF. This process does not return to VTAM (see /CLOSE). The command causes CA
WA CA 7 Edition to return the terminal to the Logon panel.
/LOGOFF with no terminal specification causes the logoff of the issuing terminal from CA
WA CA 7 Edition.
/LOGOFF[,{T|TERM}=term]
TERM
(Optional) Defines the terminal to log off. Value must be a terminal name, up to
seven characters. The T option could be used from the master terminal to log off a
terminal to allow completion of the shutdown process.
More information:
/SHUTDOWN Command (see page 141)
/LOGON Command
The /LOGON command initiates a CA WA CA 7 Edition terminal session. Information that
is supplied on the /LOGON command is used to validate user access to CA WA CA 7
Edition.
/LOGON userid
[,password]
[,NPW=password]
[,UID=resource]
[,PRM=parameter]
userid
Defines the user ID. The preceding parameters are valid for batch users of CA WA
CA 7 Edition (for example, console users, batch terminal users, and others). For
online users, these parameters are considered invalid unless RESLOGON=NO is
specified on the SECURITY statement in the initialization file. If RESLOGON=NO is
not specified, the /LOGON command causes the display of the LOGON panel with
an error message.

/LOGON Command
password
(Optional) Defines the password. This parameter can be entered as PSW=password.
NPW
(Optional unless external security requires it) Defines the new password. This
parameter can be used to change the current password of the user if using external
security.
UID
(Optional) Defines the UID resource name. The data that is entered is not shown.
Note: For more information about UID resources, see the Security Reference Guide.
PRM
(Optional unless the user exit requires it) Defines free-form text to pass to the
SASSXXLX user exit.
Usage Notes
If DISPLAY=NO is specified on the SECURITY statement in the initialization file, data
entered in the USERID field of the LOGON panel is not shown.
The command continuation character (CCC) is not valid with the /LOGON command.
More information:

/MSG Command
Example
/LOGON MYUSER
The screen displays the following.
MENU
------------------------*** CA71 PRODUCTION INSTANCE ***---------------------
CA-7.023 LOGON ACCEPTED, PRESS ENTER FOR MENU OR ENTER COMMAND
USERID : MYUSER TERMINAL NAME : TRM001 DATE : yy.131

VTAM APPLID : CAW TIME : 09:01:24
LUNAME : A99L100 LEVEL : r12
C A W O R K L O A D A U T O M A T I O N
C A 7 E D I T I O N
Copyright (C) 2013 CA.

All rights reserved.
/MSG Command
The /MSG command sends a free-form message to another logical terminal.
/MSG[,{LT|LTERM}=station][,ID=userid],{M|MSG}=text
LTERM
(Optional) Defines the logical terminal (station) to receive the message. LTERM and
LT can be used interchangeably, but cannot be used with ID. Value must be a single,
logical station name.

/MSG Command
ID
(Optional) Defines the user ID to receive the message. The message is queued to
the logical terminal associated with the user ID. If the user ID is logged on multiple
times, only the first logical terminal receives the message. ID cannot be used with
LT or LTERM.
MSG
Defines the message text to send. MSG and M can be used interchangeably, but
one or the other is required. If commas are included as part of the text, enclose the
entire message text in parentheses.
Usage Notes
The message is queued behind other queued output, if any. The sending logical terminal
name is shown with the message text.
If the receiving terminal logs off before displaying the message, the message remains
queued to that logical terminal.
CA WA CA 7 Edition displays the sending logical terminal name with the message text.
This command is allowed from a CA WA CA 7 Edition 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 10:00

/MVS Command
/MVS Command
The /MVS command can issue MVS operator commands.
/MVS,{M|MSG}=(operator command)
MSG
Defines the MVS system console operator command to issue. If commas are
included as part of the MVS command text, enclose the entire command text in
parentheses.
Example
/MVS,M=(D A,L)
Special Considerations
The command text is sent to MVS exactly as it appears on the MSG keyword. CA WA CA
7 Edition does not verify that the text is a valid MVS command.
The MSG keyword provides no output specific to the command. CA WA CA 7 Edition

does not report the status of the command in MVS. In most cases, command output
only appears on the MVS console.
Note: For more information about security and the /MVS command, see the Security
Reference Guide.

/NXTMSG Command
/NXTMSG Command
The /NXTMSG command displays messages that were queued for a terminal. Messages
can originate manually from a user at a terminal or automatically from CA WA CA 7
Edition. Users are alerted to the presence of messages at /LOGON time and by the
MSGS indicator at the bottom of preformatted panels or 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
No keywords are associated with this command. The next queued message for this
terminal is shown. If there are no more messages, a message is produced. The message
indicates that there are no queued messages.
/OPEN Command
The /OPEN command restores access to terminals or line groups by the CA WA CA 7
Edition system after a /CLOSE command.
Use this command to start manually the following interfaces:

■ The CA WA CA 7 Edition CAICCI terminal interface
■ The CA WA CA 7 Edition TCP/IP terminal interface
You sometimes must start the CAICCI terminal interface manually for one of the
following reasons:
■ CAICCI is not active when CA WA CA 7 Edition initializes.
■ CAICCI terminates after the interface has initialized.

/OPEN Command
To initialize the CA WA CA 7 Edition CAICCI terminal interface without recycling CA WA

CA 7 Edition, use the /OPEN command specifying a GROUP that is defined as
DEVICE=CCI. You do not need to issue the /OPEN for each group that is defined with
DEVICE=CCI. One /OPEN issued for any such group suffices.
Do not use this command after a /CLOSE has been issued for a GROUP defined as
DEVICE=CCI.
If one of the following situations occurs, you sometimes must start the TCP/IP terminal
interface manually:
■ TCP/IP was not active when CA WA CA 7 Edition was initialized.
■ TCP/IP has crashed.
■ The TCP/IP terminal interface was shut down with a /CLOSE command.
You can initialize the TCP/IP terminal interface without recycling CA WA CA 7 Edition.
Use the /OPEN command specifying any GROUP that is defined as DEVICE=CCI and the
TERM=TCP/IP parameter. You do not need to issue the /OPEN for each group that is
defined with DEVICE=CCI. One /OPEN issued for any such group suffices.
Format 1
/OPEN,{GROUP=group|{T|TERM}=term}
Format 2
/OPEN,GROUP=group,{T|TERM}=TCP/IP
GROUP
Defines a line group to open and identifies which group. The value must be the
group name. When GROUP specifies a VTAM group, logons are accepted.
Required: Format 1: Yes (unless TERM is used). Format 2: Yes.

/OPERID Command
TERM
Specifies either the name of a VTAM terminal that is to have its logon simulated
(SIMLOGON) or TCP/IP.
term
Specifies the name of the terminal. This value establishes a connection to the
terminal from CA WA CA 7 Edition to VTAM.
TCP/IP
Specifies initialization of the CA WA CA 7 Edition TCP/IP terminal interface.
Required: Format 1: Yes (unless GROUP is used). Format 2: Yes.
Examples
/OPEN,GROUP=CCIGRP1,TERM=TCP/IP
/OPEN,GROUP=VGROUP
/OPEN,T=VPRNTR
/OPEN,GROUP=CCI01
/OPERID Command
The /OPERID command obtains the current internal security definitions for the issuing
user.
/OPERID
No keywords are associated with this command.

/OPERIDS Command
Example
/OPERID Command
/OPERID
*** OPERATOR DISPLAY *** PAGE 0001

OPERATOR-ID TERMINAL USERID ----------------APPL,PRTY-------------
MASTER HTERM1 255 SYS0,15 SDM0,15 SCO0,15 SLI0,15 SCM0,15

MLR0,15 FOR0,15 SRC0,15 TRA0,15 SPO0,15
UTL0,15 SAN0,15 SJR0,15 SQM0,15 SFC0,15
MASTER TTERM1 255 SPO0,15
MASTER CTERM1 255 SCO0,15 SLI0,15 SPO0,15
MASTER BTERM1 255 SCO0,15 SLI0,15 SPO0,15
These fields are described in the /OPERIDS examples.
/OPERIDS Command
The /OPERIDS command displays current internal security definitions for an operator ID
other than your own or for all operator IDs. You can also use the /OPERIDS command to
display all active users that are logged on to CA WA CA 7 Edition.
/OPERIDS,ID={userid|ALL|*ACT*}
ID
Specifies the operator ID for which to display the internal security definitions. You
can enter one of the following values:
userid
Displays the definitions for a single operator ID.
ALL
Displays the definitions for all currently defined operator IDs.
*ACT*
Displays all active terminal users that are logged on to CA WA CA 7 Edition.
Once the trailer terminal has been used after CA WA CA 7 Edition startup, it
always shows active.

/OPERIDS Command
Examples
/OPERIDS Command
/OPERIDS,ID=MASTER
*** OPERATOR DISPLAY *** PAGE 0001

OPERATOR-ID TERMINAL USERID ----------------APPL,PRTY-------------

MASTER TTERM1 255 SPO0,15
MASTER CTERM1 255 SCO0,15 SLI0,15 SPO0,15
MASTER BTERM1 255 SCO0,15 SLI0,15 SPO0,15

OPERATOR-ID
Identifies the CA WA CA 7 Edition operator ID as defined in the CA WA CA 7 Edition
internal security matrix.
TERMINAL
Identifies the CA WA CA 7 Edition terminal name as defined in the initialization file.
USERID
Identifies the internal security UID level that is associated with the operator ID
listed.
APPL,PRTY
Identifies the CA WA CA 7 Edition application IDs and the associated security level
for this user for each application. (Example: SDM0,15 where SDM0 is the database
maintenance application, and the user has a security level of 15 for this
application.)
/OPERIDS Command
/OPERIDS,ID=*ACT*
*** DISPLAY ACTIVE USERS ***

PAGE 0001
TERMINAL LUNAME USERID UID LAST INPUT
LC A78L909 PROD06 000 15:02:10 (W)

X78001 A78L906 SCHED4 100 15:02:12 (A)
X78002 A78L907 OPERID1 255 15:02:14 (A)

/PAGE Command

TERMINAL
Identifies the CA WA CA 7 Edition terminal name as defined in the initialization file.
LUNAME
Identifies the VTAM logical unit name that is associated with this terminal.
USERID
Identifies the user ID associated with the terminal. If internal security is being used,
this name is the CA WA CA 7 Edition operator ID. For external security, this name is
the ID of the user that was used during logon to CA WA CA 7 Edition.
UID
Identifies the internal security UID level that is associated with the user.
LAST INPUT
Identifies the time when the last command was entered on this terminal.
W
Indicates that the terminal is in an input wait (waiting for a command to be
entered).
A
Indicates that the terminal is processing a command.
I
Indicates that the terminal has been interrupted (for example, an attention)
while processing a command. The terminal is not available again until the
command is complete.
/PAGE Command
The /PAGE command can selectively review an output message or command response.
You can also review previous pages (panels) and succeeding pages of a current display.
/PAGE{=nnn|+nnn|-nnn}
=nnn
Defines the exact page number to show.

/PAGE Command
+nnn
Defines a relative number of pages to skip forward within the message.
-nnn
Defines a relative number of pages to skip backward within the message.
Limits: 1 to 3 numeric characters
Usage Notes
The default values for PA1 (3270 program access key 1) or Enter with no text has the
same effect as entering /PAGE+1.
To see the last page in a message, request a specific page (/PAGE=nnn) and supply a
high value for nnn (for example, 255).
Online menus and their related formatted and display panels temporarily override PF7
and PF8 to /PAGE-1 and /PAGE+1 respectively. For other displays, PA1 and PA2 default
to these same values if they have not been set to some other value during initialization
or by a /PA command.
Examples
This example goes to page four.
/PAGE=4
This example skips forward two pages from current page.
/PAGE+2
This example skips backward three pages from current page.
/PAGE-3

/PAnn Command
/PAnn Command
The /PAnn command reassigns PA keys. This command can serve as a shortcut for doing
repetitive commands at the terminal (3270-type). Each terminal can have unique
information that is associated with a program access (PA) key, or certain basic
commands can be assigned to PA keys during initialization of CA WA CA 7 Edition. An
individual at a terminal can reassign PA keys that are set during initialization.
/PAnn[,{M|MSG}=text]
nn
Defines the PA key to assign.
Limits: 2 numeric characters from 01 to 03
Leading zero is required
MSG
(Optional) Defines the character string that is assigned to the key. MSG and M can
be used interchangeably. If commas are included as part of the text, enclose the
Usage Notes
If entered with no parameters (for example, /PA01), the character string that is assigned
to the key by a previous /PA command is removed. (The assignments in the initialization
file are not removed.) /PF99 cancels all /PF and /PA command assignments on that
terminal for both PF and PA keys. (The assignments in the initialization file are not
removed.)
All /PA command assignments are carried across /LOGOFF and /LOGON command
sequences, but not across initializations of CA WA CA 7 Edition. Default values for PA
keys, if not overridden during initialization or by a /PA command, are:
PA1 key - /PAGE+1

PA2 key - /PAGE-1
Note: The PA keys are not supported under the CA WA CA 7 Edition TSO-ISPF interface.
You can view assigned values by entering a /DISPLAY,ST=KEY command.

/PFnn Command
Examples
/PA03,M=(/COPY,LT=TERMABC)
/PA01,M=LQUE
/PFnn Command
The /PFnn command provides a shortcut method for doing repetitive commands at a
3270-type terminal. Each terminal can have unique information that is associated with a
program function (PF) key, or certain basic commands can be assigned to PF keys during
initialization of CA WA CA 7 Edition. Using the /PF command, an individual at a terminal
can reassign PF keys that are set during the initialization.
/PFnn[,{M|MSG}=text]
nn
Defines the PF key to assign. The value 99 cancels all assignments that are made
with previous /PF and /PA commands.
Leading zero is required
MSG
(Optional) Defines the character string that is assigned to the key. MSG and M can
be used interchangeably. If commas are included as part of the text, enclose the
Usage Notes
Online menus and their related formatted and display panels temporarily override PF3.
PF3 is used there as a quit function to return to the menu. Any value that the user
defines is ignored until PF3 is used once or the user enters a top line command.
A CA WA CA 7 Edition PF key assignment is honored in the CA WA CA 7 Edition TSO-ISPF

environment when PASSTHRU is the ISPF application command table value that is
associated with the ISPF command that is assigned to the PF key in question.

/PROF Command
You can view assigned values by entering a /DISPLAY,ST=KEY command.
/PF99 cancels all /PF and /PA command assignments on that terminal for both PA and
PF keys. (The assignments in the initialization file are not removed.) If entered with a
null MSG value (for example,/PF01,MSG=) the character string that is assigned to the
key by a previous /PF command is removed. (The assignments in the initialization file
are not removed.)
All /PF command assignments are carried across /LOGOFF and /LOGON command
sequences, but not across initializations of CA WA CA 7 Edition. Remember that /PF
command assignments are associated with terminals. This assignment is an important
consideration if virtual terminals are used.
Default values for PF keys, if not overridden during initialization or by a /PF command,
are the following values:
PF1 - /PURGPG
PF2 - /FETCH
PF3 - /NXTMSG
In a VTAM environment, a PF key is normally assigned as the VTAM logoff key in 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
/PF04,M=LQ
/PF09,M=(/ECHO,M=(LJOB,JOB=#))
/PF06,MSG=(/FETCH)
/PROF Command
The /PROF command lists and manages your CA WA CA 7 Edition user profile. The user
profile is stored in the CA WA CA 7 Edition database and contains personal PA/PF key
settings and an external UID resource name (see the /UID command and the Security
Reference Guide). When you log on to CA WA CA 7 Edition, the PA/PF key settings from
your user profile are set up for your terminal session automatically. Also, if you do not
specify an external UID resource name on the CA WA CA 7 Edition Logon panel, it is
taken from the user profile when it is defined there.
Note: User profile PA/PF key settings override terminal and default PA/PF key settings
from the initialization file with one exception. The user profile settings do not override
the PA/PF key that is defined as the VLOGOFF key.

/PROF Command
If you issue the /PROF command without any operands, the current values in your user
profile are listed.
/PROF[,EXRSLV={NO|YES}]
[,{K|KEYS}={CLEAR|PROFILE|SAVE}]
[,R=uidname]
[,{ST|STATUS}=DELETE]
EXRSLV
(Optional) Specifies whether to produce extended RESOLV messages when you
issue a RESOLV command. These messages (SRC1-137) can be produced when a
job/network is scheduled on the same day by two or more schedule IDs.
Required: No. The extended RESOLV message option can be overridden using the
DUPDATE= keyword on the RESOLV command itself.
KEYS
(Optional) Specifies the action to take with PA/PF keys.
SAVE
Specifies to save your current terminal PA/PF key settings in your user profile.
The current terminal key settings are defined by using the /PAnn and /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 key settings under the headings Initialization and
Defaults are not saved. If you already have PA/PF key settings in your user
profile, they are NOT merged with the new settings.
PROFILE
Specifies to replace your current terminal PA/PF key settings with the
definitions in your user profile. PROF and PROFILE can be used interchangeably.
If you have made temporary changes to your current settings with the /PAnn
and/or /PFnn commands, you can return to your profile definitions by using
KEYS=PROFILE.
CLEAR
Specifies to clear the PA/PF key settings in your user profile. Once cleared,
these settings cannot be recovered. Define new settings to your current session
using the /PAnn and/or /PFnn commands, and then save them using
KEYS=SAVE. If you want to clear only the settings for your current terminal
session, use the /PF99 command.

/PROF Command
R
(Optional) Defines the resource name defined in the UID resource table to be used
as your default at logon time. If you explicitly specify a resource name on the CA
WA CA 7 Edition Logon panel, it overrides the value in your user profile.
Note: The resource name that is specified is not validated against the current UID
resource table, nor is it checked against external security at the time it is placed in
the profile record. These checks are made if the resource name is used at logon
time.
STATUS=DELETE
(Optional) Specifies to delete the entire user profile record from the database. If
used, this keyword must be the only one coded. ST and STATUS can be used
interchangeably.
More information:
/UID Command (see page 147)
Examples
This example lists your user profile settings.
/PROF
This example saves current PA/PF keys into your profile.
/PROF,KEYS=SAVE
This example sets default UID resource name in the profile.
/PROF,R=CA70122
This example sets up the user profile PA/PF keys in your current terminal session.
/PROF,K=PROFILE
This example deletes the profile record from the database.
/PROF,ST=DELETE

/PROF Command
Usage Notes
To set up your own personal PA/PF key settings, first define them for your current
terminal session using the /PA and/or /PF commands. After they are set to your
satisfaction, use the /PROF command with the KEYS=SAVE parameter to save them into
your profile.
For example:
/PF99 Deletes any current settings

/PF01,MSG=...command.... Defines PF01
.... other keys ........ Define as many as you want
/DISPLAY,ST=KEY Displays your current PA/PF key
settings. You current session keys
are listed under the heading
'---- TERMINAL ----'.
/PROF,KEYS=SAVE Saves the current session keys into
your 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
PF01 /ECHO,M=(/DISPLAY,ST=KEY)
PF02 /ECHO,M=(/DISPLAY,ST=ALL)
PF06 /NXTMSG
PF19 /PAGE-1
PF20 /PAGE+1
PF23 /ECHO,M=(/PURGPG)
SCMP-00 DISPLAY COMPLETE AT hh:mm:ss ON yy.ddd.

ID
Identifies the CA WA CA 7 Edition user ID whose profile is being shown.
R
Identifies the external UID resource name to be used as a default at logon.
MAINT
Identifies the date and time of the last update to the profile record and the CA WA
CA 7 Edition user ID who caused the update.

/PROFS Command
OPTS
Identifies user option defaults:
■ EXRSLV - Produce extended RESOLV messages (SRC1-137).
PFnn or PAnn
Identifies the PA or PF key defined.
commands
Identifies the command that is associated with the PA/PF key on the same line.
/PROFS Command
The /PROFS command lists and manages CA WA CA 7 Edition user profiles of other
users. The user profile is stored in the CA WA CA 7 Edition database and contains
personal PA/PF key settings and a UID resource name (see the /UID command). When
you log on to CA WA CA 7 Edition, the PA/PF key settings from your user profile are set
up for your terminal session automatically. Also, assume that you did not specify an
external UID resource name on the CA WA CA 7 Edition Logon panel. In this case, the
name is taken from the user profile when it is defined there.
Note: User profile PA/PF key settings override terminal and default PA/PF key settings
from the initialization file with one exception. The user profile settings do not override
the PA/PF key that is defined as the VLOGOFF key.
If you issue the /PROFS command with only the ID= operand, the current settings in the
profile of that user are listed.
/PROFS,ID=opid
[,EXRSLV={NO|YES}]
[,{K|KEYS}={CLEAR|PROFILE|SAVE}]
[,R=resname]
[,{ST|STATUS}=DELETE]
ID
Defines the operator ID (one- to eight-character user ID) for the user profile you
want to display or update.
EXRSLV
(Optional) Specifies whether to produce extended RESOLV messages when the
target user issues a RESOLV command. These messages (SRC1-137) can be
produced when a job/network is scheduled on the same day by two or more
schedule IDs.
Limits: The extended RESOLV message option can be overridden using the
DUPDATE= keyword on the RESOLV command itself.

/PROFS Command
KEYS
(Optional) Specifies the action to take with PA/PF keys.
SAVE
Specifies to save your current terminal PA/PF key settings in the user profile for
the ID= user. The current terminal key settings are defined by using the /PAnn
and /PFnn commands. To determine your current settings, issue
/DISPLAY,ST=KEY. The definitions under the heading ---- TERMINAL ---- are the
settings that are saved into the profile. Other PA/PF key settings under the
headings Initialization and Defaults are NOT saved. If there are already PA/PF
key settings in the user profile, they are NOT merged with the new settings.
PROFILE
Specifies to replace your current terminal PA/PF key settings with the
definitions in the ID= user's profile. PROF and PROFILE can be used
interchangeably. You can return to your own profile settings by issuing
/PROF,KEYS=PROFILE.
CLEAR
Specifies to clear the PA/PF key settings in the ID= user's user profile. Once
cleared, these settings cannot be recovered.
R
(Optional) Defines the resource name defined in the UID resource table that the ID=
user uses as the default at logon time. If they explicitly specify a resource name on
the CA WA CA 7 Edition Logon panel, it overrides the value in their user profile.
Note: The resource name that is specified is not validated against the current UID
resource table, nor is it checked against external security at the time it is placed in
the profile record. These checks are made if the resource name is used at logon
time.
STATUS=DELETE
(Optional) Specifies to delete the entire user profile record from the database. ST
and STATUS can be used interchangeably. If used, this keyword must be the only
one coded.
More information:
/UID Command (see page 147)

/PROFS Command
Examples
This example lists the user profile settings for Joe.
/PROFS,ID=JOE
This example sets resource name CA70022 in the profile of Bob.
/PROFS,ID=BOB,R=CA70022
This example saves YOUR current PA/PF key settings into the profile of Ted.
/PROFS,ID=TED,K=SAVE
This example deletes the profile settings for Joe.
/PROFS,ID=JOE,ST=DELETE
Usage Notes
The most important thing to remember about dealing with other users' profiles is that
your current terminal session definitions affect or are affected by actions regarding
others' profiles.
For example, to set up default PA/PF keys for other users, first define them to your
current terminal session using the /PA and/or /PF commands. You can then save these
definitions into their profile (/PROFS,ID=userid,KEYS=SAVE).
Another way to accomplish this process is to fetch the PA/PF key settings from an
existing profile into your current terminal session. Next, then save them into the profile
of another user profile. Finally, 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 in batch using
the BTI facility. So you can set up a batch command deck that defines all the PA/PF keys
and SAVES them into one or more user profiles. For example:
/LOGON adminid Logon the administrator userid

/PF99 Delete any current settings
/PROFS,ID=USER1,KEYS=SAVE,R=resname Set up defaults for USER1
/LOGOFF

/PURGPG Command
/PURGPG Command
The /PURGPG command deletes additional pages of an output message that are
queued. Using a form of this command can also delete all queued output for a logical
terminal.
/PURGPG[,{LT|LTERM}=station]
LTERM
(Optional) Defines the logical terminal (station) from which you want to purge
queued output. LTERM and LT can be used interchangeably. If you omit LTERM,
only the pages of the currently displayed message are purged.
Usage Notes
The default value for PF1 (3270 program function key 1) has the same effect as entering
/PURGPG.
Use of /PURGPG is not necessary if:

■ The next entry is /NXTMSG.
■ The next entry is another command.
■ The next entry is a /LOGON.
■ The terminal is logging off.
Examples
/PURGPG
/PURGPG,LTERM=INPUT

/REFRESH Command
/REFRESH Command
The /REFRESH command refreshes the UID resource table that was loaded during CA
WA CA 7 Edition initialization without cycling CA WA CA 7 Edition.
/REFRESH,MOD={membername|MSGRCNTL}
MOD=membername
Defines a UID resource table in load module format that was built using the
CA7RTBL macro. This name must be the member name of the UID resource table
and it must reside in a load library accessible to CA WA CA 7 Edition. The name
MSGRCNTL is reserved.
If MOD=SERVDESK is specified, the CA Service Desk filter rules are reread from the
SERVDESK DD statement.
Note: For more information about the CA WA CA 7 Edition UID resource table, see
the Security Reference Guide.
MOD=MSGRCNTL
Specifies to refresh control options dynamically for CA WA CA 7 Edition Master
Station Message Routing (MSMR). These options are set in the CA WA CA 7 Edition
MSMR Control File (MSGRCNTL DD statement in the CA WA CA 7 Edition JCL).
Use /REFRESH,MOD=MSGRCNTL for the following situations:
■ You want to update the list of message recipients.
■ You want to alter message selection or customization criteria without having to
recycle the CA WA CA 7 Edition started task.
Note: During the brief interval that is required for processing
/REFRESH,MOD=MSGRCNTL, messages occasionally appear to be improperly
selected or excluded. Most users tolerate such behavior to avoid the overhead of
recycling CA WA CA 7 Edition.
If this exposure is considered unacceptable, users should issue the command at a
time when few messages are being generated or attempt to quiesce activities that
produce messages before issuing the command.
Note: For more information about CA WA CA 7 Edition Master Station Message Routing
(MSMR), see the Systems Programming Guide.

/RELINK Command
/RELINK Command
The /RELINK command dynamically loads a new copy of a CA WA CA 7 Edition module
without having to shut down the product.
Format 1
/RELINK,{A|APPL}=SASSxxxx[,{U|USERID}=xx]
Format 2
/RELINK,{FM|FMTBLK}={SFMxyyyy|SCALyyyy}[,{U|USERID}=xx]
APPL
Defines the CA WA CA 7 Edition program module to relink. Use A and APPL
interchangeably but specify one or the other to relink a program module. The value
must be the module name in the format SASSxxxx where xxxx is the last four
characters of a module name.
Limits: 8 alphanumeric characters
Required: Yes (Format 1 only)
FMTBLK
Defines the CA WA CA 7 Edition format block/calendar block to relink. Use FM and
FMTBLK interchangeably but specify one or the other to relink a format block of a
calendar module.
SFMxyyyy
Defines format block name where x is A for batch, H for online, and yyyy is the
last four characters of a module name.
SCALyyyy
Defines calendar block name where yyyy is the last four characters of a module
name.

/RESET Command
USERID
Defines a prefix to replace the first two characters of the standard module name. U
and USERID can be used interchangeably. Value, if used, can be any two characters
with the first character being alphabetic.
Usage Notes
You can only issue /RELINK on modules that are defined with an APPLCTN statement in
the initialization file or those modules in SASSPROG. The relinking of a module occurs
only 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 longer required. You cannot use
/RELINK for a PERM or RESD module, the logon exit module, or a module included in the
link edit of UCC7.
Examples
/RELINK,APPL=SASSSCM5
/RELINK,A=SASSSP03,USERID=XX
/RELINK,FMTBLK=SFMASDM0,U=ZZ
/RELINK,FM=SFMHSCRJ
/RELINK,FM=SCAL09XX
/RESET Command
The /RESET command resets the CA WA CA 7 Edition assigned job numbers to begin
again with job number 1. Numbers in use at the time of the command are skipped.
/RESET
No keywords are associated with this command.

/SDESK Command
/SDESK Command
The /SDESK command opens a request in CA Service Desk. The SERVICEDESK
initialization file statement must be present for the command to work.
/SDESK,EVENT=xxxxxx[,JOB=xxxxxxxx]
EVENT
Defines the six-character event name to use when building the request for CA
Service Desk. The event name must be exactly six characters long and previously
defined to the CAISDI/els event library (the event library is defined on the
CAISDI/els utility CSDECNTL command DEFINE). EVENT is required and has no
default.
JOB
(Optional) Defines a job name or CA 7 job number of a job in the request, ready, or
active queues. If JOB is specified, the job information is used to fill in variables in
the CAISDI/els event. If a job name is entered, the queues are searched in the order
of request, ready, then active.
/SHUTDOWN Command
The /SHUTDOWN command causes a normal termination of CA WA CA 7 Edition
execution. Due to the impact of shutting down CA WA CA 7 Edition, use the
/SHUTDOWN command with caution.
Only a terminal that is specified as the Master or Alternate Master can use the
/SHUTDOWN command. Those terminals are defined as CONS=MASTR or CONS=ALTRN
on the TERM statement in the initialization file.
You can set default /SHUTDOWN options on the OPTIONS statement in the initialization
file. These options take effect when you enter /SHUTDOWN with no parameters.
/SHUTDOWN[,Zn]

/SHUTDOWN Command
Zn
(Optional) Specifies the method of shutdown as follows:
Z1
Specifies a "fast" shutdown of CA WA CA 7 Edition. Messages are not sent to
the individual terminals. CA WA CA 7 Edition does not wait for them to log out
but waits for batch type terminals to complete (this process includes CAICCI
terminals).
Z2
Specifies that shutdown is to occur even if batch type terminals are still active,
but the shutdown waits for online terminals to log out.
Z3
Specifies that shutdown is to occur even if online terminals, batch type
terminals, or both are active.
Note: If you do not specify a form of Zn, CA WA CA 7 Edition terminates after
all terminals have logged off. No batch type terminals can be active.
If a BTI is active when a shutdown is done with a "fast" option that includes not waiting
for batch type terminals, CA WA CA 7 Edition can possibly abend (S002, for example).
This abend can result from IO control blocks that are changing status (OPEN/CLOSE)
during an IO operation.
Usage Notes
Shutdown is normally issued from an online terminal. You can issue the command from
a batch terminal, if necessary. Shutdown is not supported from a trailer terminal
(SASSTRLR or U7SVC) or by the TSO/ISPF interface.
For online terminals, a verification process is required before shutdown can occur. After
the /SHUTDOWN command is entered, CA WA CA 7 Edition is put in a shutdown status.
The terminal that entered the shutdown receives a message indicating the options that
are entered for the shutdown. If the displayed options are correct, press Enter for the
shutdown to occur. If the options are not correct, the /SHUTDOWN command can be
changed and reentered. When two /SHUTDOWN commands with the same options are
entered consecutively, CA WA CA 7 Edition shuts down.

/START Command
If you specified a default shutdown type in the initialization file, you can enter the
/SHUTDOWN command without any parameters. The default option is selected for
normal termination of CA WA CA 7 Edition.
If a batch terminal requested the shutdown, only one SHUTDOWN command is required
to shut down the system.
If a console (DEVICE=CONSL) enters the /SHUTDOWN command, the operator must

enter the command a second time for verification for the shutdown to occur.
While in the shutdown mode (and until Enter is pressed or two /SHUTDOWN commands
with the same options are entered), other terminals entering commands receive the
following message:
CA-7.010 UNIDENTIFIED COMMAND
The terminal that entered the /SHUTDOWN command is allowed to enter certain slash
(/) commands (/LOGOFF, /DISPLAY, and so on) between the "consecutive" /SHUTDOWN
commands. If an invalid command is entered while CA WA CA 7 Edition is in shutdown
mode, the terminal receives an error message stating that the command must be
/SHUTDOWN. CA WA CA 7 Edition can be shut down without terminating ICOM when
CA WA CA 7 Edition controlled jobs are still active in OS. However, if CA WA CA 7 Edition
is to be down for a long time, we recommend that you stop ICOM.
/START Command
The /START command restarts line groups and terminals following correction of an I/O
error or after the line or terminal has been stopped with a /STOP command.
/START[,{L|LINE}=line]
[,{LT|LTERM}=station]
[,{M|MSG}=PROMPTS]
[,{T|TERM}={terminal|ALL}]

/START Command
LINE
(Optional) Defines the line to start. L and LINE can be used interchangeably. One or
the other is required when starting an entire line. When starting a terminal, LINE or
L can also be given to qualify the terminal name. Omit both when you specify
LTERM (or LT).
LTERM
(Optional) Defines a logical terminal (station) for which activities involving output
are to start. LT and LTERM can be used interchangeably. One or the other is
required when the command is to impact a logical terminal. Omit both when you
specify LINE (or L) or TERM (or T).
MSG
Specifies prompting for a specific logical terminal is to start. MSG is required to
invoke this function. However, it can only be used with LTERM (or LT). Value if used
must be MSG=PROMPTS.
Required: Yes - for the LTERM option
TERM
Specifies a real terminal is to start. Use TERM or T interchangeably. Use one or the
other to start a terminal.
terminal
Defines the terminal name.
ALL
Specifies 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

/STATEMGR Command
/STATEMGR Command
The /STATEMGR command enables or disables the interface to ARM (the IBM Automatic
Restart Management) and to CA OPS/MVS EMA SSM (System State Manager).
/STATEMGR[,ARM={NO|YES}][,OPSSSM={NO|YES}]
ARM
(Optional) Specifies the status of the interface to the IBM Automatic Restart
Management.
NO
Disables the interface. An ARM DEREGISTER is performed. NO is the default.
YES
Enables the interface. An ARM REGISTER and READY are performed. If the
interface is already enabled, an ARM DEREGISTER is performed before the
REGISTER and READY.
OPSSSM
(Optional) Specifies the status of the interface to CA OPS/MVS EMA System State
Manager (SSM).
NO
Disables the interface. No further state changes are sent from CA WA CA 7
Edition. CA OPS/MVS EMA continues to detect CA WA CA 7 Edition state
changes through its own internal means. NO is the default.
YES
Enables the interface. An UP state is sent to CA OPS/MVS EMA SSM.

/STOP Command
/STOP Command
The /STOP command stops line groups and terminals that the /START command started.
You can use it to stop a terminal having I/O errors.
/STOP[,{L|LINE}=line]
[,{LT|LTERM}=station]
[,{M|MSG}=PROMPTS]
[,{T|TERM}={terminal|ALL}]
LINE
(Optional) Defines the line to stop. Use L and LINE interchangeably. One or the
other is required when stopping an entire line. When stopping a terminal, LINE (or
L) can also be given to qualify the terminal name. Omit both when you specify
LTERM (or LT). The value for either usage must be the line name, up to seven
characters.
LTERM
(Optional) Defines a logical terminal (station) for which activities involving output
are to stop. Use LT and LTERM interchangeably. One or the other is required when
the command is to impact a logical terminal. Omit both when you specify LINE (or L)
or TERM (or T) is specified.
MSG
Specifies prompting for a specific logical terminal is to stop. MSG is required to
invoke this function. However, it can only be used with LTERM (or LT). The value if
used must be MSG=PROMPTS.
Required: Yes - for the LTERM option
TERM
(Optional) Defines a real or batch terminal is to stop. Use TERM (or T)
interchangeably. Use one or the other to stop a terminal.
terminal
Defines the real or batch terminal name.
ALL
Specifies to stop all terminals that the /START command started.
Limits: The LINE parameter is also required when you specify TERM=ALL.

/SWAP Command
Usage Notes
When a /STOP command is issued for a logical terminal, any output currently queued is
not sent to the physical terminal to which the logical terminal is assigned. 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 Command
The /SWAP command causes CA WA CA 7 Edition to switch log record recording to an
alternate log file. This switching in turn causes the closing of the current log file and the
automatic submission of the log dump job.
You must have defined alternating DASD log files with ALOG1 and ALOG2 statements in
the initialization file for this command to be useful.
/SWAP
No keywords are associated with the /SWAP command.
/UID Command
The /UID command alters the UID security level of the current user. The /UID command
is valid only in environments where external security controls CA WA CA 7 Edition
logons.
Format 1
UID,R=resname

/WLB Command
Format 2
/UID,LIST
R
Defines the resource name defined in the UID resource table.
LIST
Specifies the UID resource table that is loaded during CA WA CA 7 Edition
initialization.
Examples
Example 1
/UID,R=CA70255
SCM9-21 UID VALUE UPDATED.
Example 2
/UID,R=R990BAD
SCM9-17 RESOURCE (R990BAD) NOT FOUND IN CA-7 RESOURCE TABLE.
/WLB Command
The /WLB command changes the workload balancing function of the CA WA CA 7
Edition system.
Format 1
/WLB,SET={ON|OFF}

/WLB Command
Format 2
/WLB,SET={CLASSx},BARR=count/+count/-count
{INITS}
{MINJOB}
{T1TAV}
{T1MAX}
{T2TAV}
{T2MAX}
SET
Specifies whether to activate or deactivate the workload balancing function.
ON
Specifies to activate the workload balancing function.
OFF
Specifies to deactivate the workload balancing function. Workload balancing
remains off until the system is brought down or until it is reactivated manually
with SET=ON.
SET
Specifies the selection parameter to adjust. Use one of the following values:
CLASSx
Specifies class barrier x, where x is A-Z or 0-9.
INITS
Specifies total initiators.
MINJOB
Specifies minimum jobs to schedule (ignored when the enhanced submission
selection is active).
T1TAV
Specifies available type 1 tapes.
T1MAX
Specifies maximum allowable type 1 tapes (ignored when the enhanced
submission selection is active).

/WTO Command
T2TAV
Specifies total available type 2 tapes.
T2MAX
Specifies maximum allowable type 2 tapes (ignored when the enhanced
submission selection is active).
BARR
Defines the number to replace or adjust the current value. An unsigned value
replaces the current value. Signed values indicate an amount by which the current
value is adjusted. Any value that causes a barrier to exceed its maximum (255)
causes the setting of the barrier to its maximum.
/WTO Command
The /WTO command sends a free-form message to the OS master console. This
command is allowed from a CA WA CA 7 Edition trailer step.
/WTO[,HI={No|Yes}],{M|MSG}=text
HI
(Optional) Specifies whether to highlight the message on the console.
No
Indicates do not highlight the message. No is the default.
Yes
Indicates to highlight the message.
MSG
Defines the message that is sent to the OS master console. MSG and M can be used

/XCF Command
Examples
/WTO,MSG=BILLING EDIT RUN NEEDS PRIORITY
/WTO,HI=YES,M=RELEASE THE PAYROLL JOB RIGHT NOW!
/WTO,M=(CANCEL BILLING CYCLE, INPUT NOT RECEIVED)
The first example would appear on the CA WA CA 7 Edition job or JES log listing as
follows:
CA-7.WTO ttttttt - BILLING EDIT RUN NEEDS PRIORITY
ttttttt
Identifies the terminal from which the message originated.
/XCF Command
The /XCF command provides a mechanism to delete obsolete records in the XCF
checkpoint data set.
The /XCF command uses XCF messaging to perform this function. If the command is
entered and XCF is turned off, a message is issued. The message states that CA WA CA 7
Edition is not using XCF.
Note: The record is not deleted. The record is only flagged as being deleted. The
LXCF,LIST=SMF command does not display records that are flagged as deleted. To delete
the record physically, reformat the XCF checkpoint data set with the program SASSXKPI.
(See the N707 install job.)
/XCF,OPT={D|DEL},SMF=xxxx,INST=xxxx
OPT
Specifies the option. The only option available is delete.
D|DEL
Specifies to delete an ICOM record from the XCF checkpoint data set.
SMF
Specifies the SMF ID of the system on which the ICOM was running.
xxxx
Identifies the SMF ID in the record to delete.

/XTASK Command
INST
Specifies the CA WA CA 7 Edition instance with which the ICOM was
communicating.
xxxx
Identifies the CA WA CA 7 Edition instance in the record to delete.
Examples
This example deletes the record of the CA71 instance on SYS1.
/XCF,OPT=D,SMF=SYS1,INST=CA71
This example deletes the record of the CA74 instance on SYS2.
/XCF,OPT=DEL,SMF=SYS2,INST=CA74
/XTASK Command
The /XTASK command can control the Cross-Platform Scheduling Router (Router) and
the CA WA CA 7 Edition Cross-Platform Tracking System (Tracker).
Note: /XTASK can be used with the CA WA CA 7 Edition Cross-Platform Tracking System
only if that system runs in the CA WA CA 7 Edition address space.
The router and the tracker (if it runs in the CA WA CA 7 Edition address space) are
started automatically when CA WA CA 7 Edition initializes. You can manually stop and
restart these tasks using /XTASK.
To stop an active cross-platform scheduling task, use the CMD function to send a STOP
command to the task. You can use the ADD function to restart the task if necessary.
The CA WA CA 7 Edition cross-platform tracking system recognizes other commands

besides STOP. These commands are documented in the Interface Reference Guide. STOP
is the only command that the cross-platform scheduling router recognizes.
The router and the tracker run as subtasks when they run in the CA WA CA 7 Edition
address space. CA WA CA 7 Edition does not wait for the subtask to return the results of
the command but continues to perform its primary task of scheduling jobs. To see the
output from the /XTASK command, browse the CA WA CA 7 Edition job log because the
output does not appear online. For Tracker commands, the results are also written to
the XPRINT DD statement.

/XTASK Command
/XTASK,{M|MSG}=(function-name,task-name[,command-text])
MSG
Identifies the input for a cross-platform task. The value of MSG must be a
comma-delimited sublist enclosed in parentheses.
function-name
Indicates that the first element in the sublist is the name of the function. This value
is a required element. Valid function names are the following values:
ADD
Uses this value to start a cross-platform scheduling task.
CMD
Uses this value to send a command to a cross-platform scheduling task.
task-name
Indicates that the second element in the sublist is the name of the task that is the
target of the function. This value is a required element. Valid task names include
the following values:
ROUTER
Indicates the cross-platform scheduling router.
TRACKER
Indicates the CA WA CA 7 Edition cross-platform tracking system.
command-text
(Optional) Indicates that the third element in the sublist is the text of the command
to send to the task. This value is required only when the function name is CMD.
Valid values include the following values:
STOP
Terminates a cross-platform scheduling task.
The CA WA CA 7 Edition cross platform tracking system (XTRK) sometimes
recognizes other values. These values are documented in the Interface Reference
Guide.
Examples
The following are examples of the /XTASK command:
/XTASK,M=(CMD,TRACKER,STOP)
/XTASK,M=(ADD,TRACKER)

ADDRQ Command
ADDRQ Command
The ADDRQ command manually adds temporary, one-time, preexecution user or
predecessor job requirements. These requirements must be added to the job while it is
in the CA WA CA 7 Edition request queue. These added requirements apply only to the
current run of the job. You must manually satisfy user requirements with the QM.2
panel (POST) or XRQ command before the job executes. Predecessor job requirements
are satisfied automatically when the predecessor job completes successfully.
ADDRQ,{JOB={jobname|jobnumber}|JOBL=longjobname},{DEPJOB=depjob|USR=text}
JOB
Defines the job to which you want to add the job requirement. The job must be in
the request queue. JOB and JOBL are mutually exclusive.
jobname
Defines the job name to which you want to add the requirement for this run of
the job.
jobnumber
Defines the CA 7 job number to which you want to add the requirement for this
run of the job.
JOBL
(Optional) Defines the long job name to which you want to add the job
requirement. The job must be in the request queue. JOB and JOBL are mutually
exclusive. You cannot enter a job number on the JOBL keyword.
Limits: 1 to 64 characters
DEPJOB
Defines a temporary one-time job dependency requirement. The DEPJOB value
specifies the job name that must complete execution or be manually posted
complete before the job identified by JOB is eligible for submission. DEPJOB is
required unless USR is used, in which case, omit DEPJOB. This requirement is
satisfied automatically when the predecessor job completes. Only in unusual
situations would this requirement need to be satisfied manually. That is, any time
that a normal completion did not occur.
Required: Yes, unless USR is used.

ADDSCH Command
USR
Defines the description of a temporary, one-time user requirement. This
requirement must be manually satisfied before the job identified by JOB is eligible
for submission. If any commas are included as part of the text, enclose the entire
requirements text in parentheses. USR is required unless DEPJOB is used, in which
case, omit USR.
Required: Yes, unless DEPJOB is used.
Usage Notes
Use of this command does not affect the normal requirements as defined in the
database. Once defined, this functions as if it had been defined on the DB.3.6 panel. If
either requirement type is to apply to every run of the job, update the database 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 A in the E column.
The ADDRQ command no longer permits duplicates for dependent jobs or user
requirements. If the requirement is satisfied and you want to add it again, you can use
up
the ADDRQ command to re-add it or use the XRQ screen to unpost it.
Examples
ADDRQ,JOB=17,DEPJOB=PAYJOB1
ADDRQ,JOB=XYZ,DEPJOB=ABC
ADDRQ,JOB=2,USR=USER WILL CALL TO RELEASE
ADDSCH Command
The ADDSCH command delays scheduled start and due-out times for up to 24 hours.
After a job has entered a queue, it is sometimes necessary to delay the scheduled start
time or due-out time. It is sometimes necessary to delay the entire workload already in
a queue to react to a major unexpected and unscheduled change in the environment.
ADDSCH,{JOB={nnnn|ALL|ALLP}|REF=nnnnrrs},TIME=mmmm

ADDSCH Command
JOB
Specifies the jobs whose schedule times you want to delay.
Required: Yes unless REF is used (in which case, omit JOB).
nnnn
Defines the job number of a single job that CA WA CA 7 Edition assigns.
ALL
Specifies all jobs and workstation entries in the request, ready, active, and
postprocess queues.
ALLP
Specifies all jobs and workstation entries including the ones in the preprocess
queue.
REF
Defines a particular workstation task within a network (and all subsequent stations)
whose schedules you want to delay. REF is required when JOB is not used.
Required: Yes unless JOB is used (in which case, omit REF).
nnnnrrs
Defines a workstation task reference number that CA WA CA 7 Edition assigns.
nnnn
Defines the CA 7 job number. You can omit leading zeros.
rr
Defines the relative sequence of the network in relation to other networks
associated with the job. For input networks, the value is 00. You cannot
omit leading zeros.
s
Defines the position of the station within the network. The first station
would be position 1.
TIME
Defines the amount of time to add to the start time and due-out time of the jobs or
workstations indicated. Value must be in minutes.

ADDSCH Command
Usage Notes
Delaying a single job or stream of jobs is sometimes necessary for the following reasons:
■ The input is not available on time.
■ An abend is causing a rerun that must complete before subsequent processing can
continue.
Sometimes you find it necessary to delay the entire workload in the event of a CPU
failure.
Note: If the job scheduled time is adjusted over a midnight boundary, the run of the job
for the next day is not always brought in because of duplicate checking performed. For
more information about duplicate checking, see the PERFORM option of the INIT
statement in the initialization file.
When schedules are delayed using the ADDSCH command, prompting is based on the
adjusted start time and due-out time.
To provide earlier schedule times, use the SUBSCH command.
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-time of a job,
which in turn affects when the job or task is late. If job submission is not to occur, add a
requirement to a job.
More information:
SUBSCH Command (see page 665)
Examples
ADDSCH,JOB=143,TIME=120
ADDSCH,JOB=ALLP,TIME=1440
ADDSCH,REF=12001,TIME=600

AGFILE Command
AGFILE Command
The AGFILE command displays agent job output data and performs other functions that
are related to agent jobs and their executions. This command can also display a
historical list of job executions for a specific agent job. The list can be built from the CA
WA CA 7 Edition status queues, the CA7AGNT VSAM file, or both. You can then select a
job from the list using a function code to perform the requested function on the
selected job.
Note: Not all agent job types support all function types.
AGFILE,{JOB=jobname|OBJECT=object-name}
[,LIST={NO|ALL|HIS|Q}]
[,NAME=file name]
[,NUMBER={1|file number}]
[,OFFSET={0|nnnnnnnn}]
[,STEPNUM=step number]
[,TYPE=function type]
JOB
Defines a specific agent job name. Masking characters are not permitted.
Size/Type: 1 to 8 characters
Limits: Mutually exclusive with OBJECT. Specify either JOB or OBJECT.
OBJECT
Defines the agent object for processing.
Limits: Mutually exclusive with JOB. Specify either JOB or OBJECT.
The object name has the following format:
jobname.Nnnnnn/system.SsssssDyydddhhmm
jobname
Identifies the CA 7 job name.
nnnnn
Identifies the five-digit CA 7 job number.

AGFILE Command
system
Identifies the CA WA CA 7 Edition system name or SYSTEM, if none.
sssss
Identifies the five-digit CA WA CA 7 Edition schedule ID.
yydddhhmm
Identifies the queue entry date and time.
The following name is an example of an object name:
PAYROLL1.N00123/PAYSYS.S00001D092151430
LIST
(Optional) Indicates whether to display the requested information for the specified
job or to display a historical list of job executions for the specified job or object. The
following values are valid:
NO
Does not display a list of job executions. NO is the default.
When a job name is specified through the JOB keyword, the information that is
listed is for the latest job execution in the REQ or PRN status queues.
When an object name is specified through the OBJECT keyword, the listed
information is for the job execution that the subfields in the object name
define.
ALL
Displays a list of job executions. Builds the list from both the CA WA CA 7
Edition status queues (ACT, RDY, REQ, and PRN) and the CA7AGNT VSAM file.
Specify JOB=jobname.
HIS
Displays a list of job executions. Builds the list from the CA7AGNT VSAM file.
Specify JOB=jobname.
Q
Displays a list of job executions. Builds the list from the CA WA CA 7 Edition
status queues (ACT, RDY, REQ, and PRN). Specify JOB=jobname.
Note: When retrieving a spool file, if you take the default of LIST=NO or explicitly
code LIST=NO and the job is actively executing at an agent, the spool data retrieved
is for the previous execution of the job. Spool data for the current job is not
retrieved before the job completes execution. This process applies to all AGFILE
functions.
Spool file retrieval can take longer for PROXY_JOB than retrievals for other job
types.

AGFILE Command
NAME
(Optional) Defines the file name for a spool file. Applies only to jobs with a job type
of AS400_JOB. When used with NUMBER, provides a direct way to retrieve an
AS400_JOB spool file without first retrieving a list of spool files using the
TYPE=FILELIST parameter.
NUMBER
(Optional) Defines the file number for a spool file. Applies only to jobs with a job
type of AS400_JOB. When used with NAME, provides a direct way to retrieve an
AS400_JOB spool file without first retrieving a list of spool files using the
TYPE=FILELIST parameter.
Default: 1
Limits: 1 to 6 digits
OFFSET
(Optional) Defines the starting offset when requesting display of a related output
file for an agent job execution.
Default: 0
STEPNUM
(Optional) Defines the step number for a job. Applies only to SAP_JOB.
Default: 1
TYPE
(Optional) Defines the type of function to perform. Use this field in combination
with LIST=NO and either JOB or OBJECT to act as a shortcut to perform the
requested function immediately without going through an intermediate menu. If
JOB is specified, the latest job in the REQ or PRN status queues is processed. If
OBJECT is specified, the selected job is the one that the subfields define in the
object name. The following values are valid:
SPOOL
Displays the spool file of the job. SPOOL is the default.
CHLOG
Displays the log file of a process chain. Applies only to BWPC_JOB.
CHPROC
Displays a list of chain processes. Applies only to BWPC_JOB.

AGFILE Command
CHSTART
Displays status for a process chain. Applies only to BWPC_JOB.
DELETE
Deletes a job from the scheduling database of the agent. Applies only to
PS_JOB, SAP_JOB and SAPA_JOB.
DELETE1
Deletes phase 1 of a job from the scheduling database of the agent. Applies
only to BDC_JOB.
DELETE2
Deletes phase2 of a job from the scheduling database of the agent. Applies only
to BDC_JOB.
DELETEB
Deletes phase1 and phase2 of a job from the scheduling database of the agent.
Applies only to BDC_JOB.
DUMP
Displays the dump file of a job. Applies only to SAP_JOB.
ERROR
Displays the job’s error file. The original job definition must have specified the
error file location. Applies only to NONSTOP_JOB.
FILELIST
Displays a list of available spool files for a job. Applies only to jobs executed on
the i5/OS (AS400) platform, such as an AS400_JOB or an FTP_JOB.
INFO
Displays information about the job from the CA7AGNT VSAM file.
JOBLIST
Returns ABAP step output. Applies only to SAP_JOB.

AGFILE Command
LOG
Displays the log file of the job. Applies only to NONSTOP_JOB, OA_JOB,
OAC_JOB, and PROXY_JOB.
OUTPUT
Displays the job’s output file. The original job definition must have specified the
output file location. Applies only to NONSTOP_JOB.
SPOOLREF
Displays the spool file location of the job. Applies only to PROXY_JOB.
TRACE
Displays the trace file of the job. Applies only to PS_JOB.
Example: AGFILE Command with LIST Option

The AGFILE command displays this List of Agent Job Executions panel when entered with
a LIST option of Q, HIS, or ALL. The panel contains a historical list of job executions for a
specific agent job name. There is no equivalent batch function.
Job executions are listed below their column headings. A page can display up to 15 job
executions. If the output is more than 15 job executions, use PF7/PF8 to scroll back and
forward through the data. PF3 returns to the Queue Maintenance (QM) menu.
To request a function be performed on any of the listed job executions, enter a

two-character value in the F column just in front of the job execution you want to
process. Only one job execution is processed. If you select multiple job executions, only
the first is processed.

AGFILE Command
When the requested function is processed, the system displays a new panel containing
the data associated with the request.
---------------- CA-7 List of Agent Job Executions for Job AGQSAP01 -----------
Spool Offset: 0 Step Number: 1
F Src CA7# System Sch Q-Date/Time Agent Job Type

__ REQ 0545 SYSTEM 001 yy268 1444 WA_AGENT SAP_JOB
__ VSM 0499 SYSTEM 001 yy251 0914 WA_AGENT SAP_JOB
PROGRAM: QM81 MSG-INDX: 00 -- QM.8.1 -- yy.275 / 14:24:20

MESSAGE: Enter desired function for a line entry or a command on the top line

Job
Specifies the CA 7 job name.
Spool Offset
Specifies the spool offset for display of an output file.
Step number
Specifies the step number for the job. Displays only for SAP_JOB.
F
Specifies the function field.
CL
Retrieve process chain log (BWPC_JOB).
Retrieve list of chain processes (BWPC_JOB).
CS
Retrieve process chain status (BWPC_JOB).
DL
Delete a job from the agent's scheduler database (PS_JOB, SAP_JOB,
SAPA_JOB).

AGFILE Command
D1
Delete phase1 of a job from the agent's scheduler database (BDC_JOB).
D2
Delete phase2 of a job from the agent's scheduler database (BDC_JOB).
DB
Delete both phases of a job from the agent's scheduler database (BDC_JOB).
GD
Retrieve a dump file (SAP_JOB).
GE
Retrieve an error file (NONSTOP_JOB).
GF
Retrieves a list of available spool files (i5/OS platforms).
GL
Retrieve a log file (NONSTOP_JOB, OA_JOB, OAC_JOB, PROXY_JOB).
GO
Retrieve an output file (NONSTOP_JOB).
GR
Retrieve a spool file reference (PROXY_JOB).
GS
Retrieve a spool file.
GT
Retrieve a trace file (PS_JOB).
IN
Display job information from the CA7AGNT VSAM file.
JS
Display ABAP output (SAP_JOB).
Src
Specifies the source for this job execution. REQ, RDY, ACT, PRN, and PRQ indicate
CA WA CA 7 Edition status queues. VSM indicates the CA7AGNT VSAM file.
CA7#
Specifies the CA 7 job number.

AGFILE Command
System
Specifies the CA 7 system name.
Sch
Specifies the CA 7 schedule ID.
Q-Date/Time
Specifies the CA 7 queue entry date.
Agent
Specifies the system agent where the job executes.
Job Type
Specifies the CA 7 agent job type.
Example: AGFILE Command Without LIST Option

The AGFILE command displays this panel when entered or defaulted with a LIST=NO
option or a job execution has been selected from the AGFILE List of Job Executions
panel. The panel displays output data from the selected function.
Job execution data is presented. Up to 15 data lines per page can be presented. If the
output is more than 15 lines, use PF7/PF8 to scroll back and forward through the data.
PF3 returns to the previous AGFILE selection panel or, if none, to the Queue
Maintenance (QM) menu.
When displaying an output file, limits may exist related to the amount of data retrieved
and presented at one time. Larger output files are presented in multiple chunks. For
these larger files, the Spool Offset field contains the starting offset for the current chunk
of data, and the Next Offset field contains the starting offset for the next chunk of data.
When you are finished viewing the current chunk of data, you can request the next
chunk of data by keying either of the following values into the Spool Offset field:
■ An N (for Next)
■ The Next Offset value
You can also key any valid numeric offset for the file to start the display at the specified
offset.
Note: If the Next Offset field contains EOF, the last chunk of data is already displayed,
and keying an N in Spool Offset redisplays the same data.
When displaying output data that does not support data limits, all data is listed, and the
Spool Offset and Next Offset fields do not exist.

AGFILE Command
----------------- CA-7 Job SPOOL For Agent ESPAGENT7 ---------

Jobname: CA7I5OS CA7#: 0066 System: SchId: 0001 Q-DtTm: yy225 1439
Job Type: AS400_JOB Start Offset: 0 Next Offset: EOF
5722SS1 V5R4M0 060210 Job Log +

USABCD99 08/13/yy 14:39:35 Page 1
Job name . . . . . . . . . . : NOOP User . . . . . . : ESPAG+

ENT Number . . . . . . . . . . . : 254556
Job description . . . . . . : CYBESPJOBS Library . . . . . : ESPAG+
ENT7
MSGID TYPE SEV DATE TIME FROM PGM +

LIBRARY INST TO PGM LIBRARY INST
CPC1163 Completion 00 08/13/yy 14:39:34.770592 QWTCCRLJ +

QSYS 0088 *EXT *N
Message . . . . : Job 254556/ESPAGENT/N+
PROGRAM: QM82 MSG-INDX: 00 -- QM.8.2 -- yy.ddd / 14:55:27

MESSAGE: Enter Start Offset or a command on the top line
(Use 'PF7/PF8 to scroll thru data' )

Job
Specifies the function type of the output that is displayed.
Agent
Jobname
CA7#
System
SchID
Q-DtTm
Job Type

AGFILE Command
Spool Offset
Specifies the starting offset for the current display of the output data. This field is
not present when displaying output data that does not support data limits.
Next Offset
Specifies the starting offset for the next sequential chunk of this output file. If the
last or only chunk of the data is presented, it contains EOF. This field is not present
when displaying output data that does not support data limits.
Detail line
Specifies the data from the related output file or CA7AGNT VSAM file.

AGFILE Command
Example: AGFILE Command with TYPE=FILELIST (for job

type=AS400_JOB Only)
The AGFILE command displays this panel when entered with TYPE=FILELIST or when a
job execution has been selected with a function code of GF from the AGFILE List of Job
Executions panel. This panel displays a list of available spool files for a job. This panel
applies to jobs with a job type of AS400_JOB only.
Spool files are listed below their column headings. A page can display up to 15 spool
files. If the output is more than 15 spool files, use PF7/PF8 to scroll backward and
forward through the data. PF3 returns to the Queue Maintenance (QM) menu.
To display one of the available spool files, enter an S in the F column just in front of the
spool file that you want to display. Only one spool file is processed. If multiple spool files
are selected, only the first is processed. When the selection is processed, the system
displays a new panel similar to the previous example, AGFILE Command Without List
Option.
--------------------- CA-7 Job FILELIST For Agent ESPAGENT7 -----------

Jobname: USER5OS CA7#: 0066 System: SchId: 0001 Q-DtTm: yy225 1439
Job Type: AS400_JOB Spool Offset: 0
F Fname F-Num Status Siz-Kb Time UserData Q-Name Q-Lib
_ QPRINT 1 *READY 16 1439 "" QPRINT QGPL
_ QPJOBLOG 2 *READY 24 1439 NOOP QEZJOBLOG QUSRSYS
PROGRAM: QM82 MSG-INDX: 00 -- QM.8.3 -- yy.225 / 14:58:02

MESSAGE:

Job
Specifies the function type of the output that is displayed.
Agent
Jobname

AGFILE Command
CA7#
System
SchId
Q-DtTm
Job Type
Spool Offset
Defines the starting offset for display of output data.
F
Specifies the function field.
Fname
Specifies the spool file name.
F-Num
Specifies the spool file number.
Status
Specifies the spool file status.
Siz-Kb
Specifies the spool file size in kilobytes.
Time
Specifies the spool file creation time.
UserData
Specifies any user data associated with the spool file.
Q-Name
Specifies the spool file queue name.
Q-Lib
Specifies the spool file queue library.

AL/ALC Command
AL/ALC Command
The AL command allocates a DASD data set. The ALC command allocates and catalogs a
DASD data set. This function is available on the UT Menu panel as FUNCTION value 1 or
on any other menu or formatted panel as FUNCTION value UT.1.
{AL|ALC},DSN=dsname,VOL=volume,SP=(type,primary,[secondary],[directory-blks])
,DCB=(recfm,lrecl,blksize)
DSN
Defines the fully qualified name of the data set.
VOL
Defines the volume serial number on which the data set is to be allocated. The
volume must have been made available to CA WA CA 7 Edition with a U7volser type
of DD statement as discussed in the Systems Programming Guide, or the ALLOC
command.
SP
Specifies space allocation. For each of the following parameters, a comma must be
coded for each parameter that is omitted, or the default value is assumed.
Parameters used must be enclosed in parentheses.
type
(Optional) Specifies either T for tracks or C for cylinders.
Default: T
primary
Defines primary space allocation amount.
secondary
(Optional) Defines an optional secondary space allocation amount.
directory-blks
(Optional) Defines the number of directory blocks to be allocated for a PDS
data set. If the number of directory blocks is zero, DSORG=PS is assumed. If
nonzero, DSORG=PO is assumed.
Default: 0

ALLOC Command
DCB
Defines the data control block (DCB) attributes. Parameters must be in parentheses.
recfm
Specifies the record format. Value must be F, FB, V, VB, VBS, VS, U, FA, FBA,
FM, FBM, VA, VBA, VM, or VBM.
lrecl
Defines the logical record length.
Default: 0
blksize
Defines the block size of the data set.
Default: 0
More information:
ALLOC Command (see page 171)
Examples
AL,DSN=USER.FILE1,VOL=VOLMO1,SP=(T,2),DCB=(F,80,80)
ALC,DSN=USER.TEMP,VOL=VOLMO1,SP=(T,5),DCB=(FB,64,640)
ALLOC Command
The ALLOC command dynamically allocates a volume that a DD statement in the
execution JCL for CA WA CA 7 Edition does not define. The dynamically allocated
ddname is U7, and the volume serial number follows. The SCRATCH command has an
example of the ddname format. This function is available on the UT Menu panel as
FUNCTION value 11 or on any other menu or formatted panel as FUNCTION value UT.11.
ALLOC,VOL=volume,UNIT=unit
VOL
Defines the volume that you want to allocate.

APA Command
UNIT
Defines the unit name for the type of DASD device you want (for example, 3390,
DISK, SYSDA).
More information:
SCRATCH Command (see page 655)
Examples
ALLOC,VOL=DISK01,UNIT=3390
APA Command
The APA command displays a menu panel for online access to graphing facilities for each
of the available categories of graphs. It has no equivalent in batch 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 Command
APA Menu
----------------- CA-7 AUTOMATED PERFORMANCE ANALYSIS MENU -----------------

FUNCTION ===>
DISPLAY PERFORMANCE FOR:

1 - CPU JOBS
2 - CA-7 SYSTEM ACTIVITY
3 - CA-7 DATA BASE ACTIVITY
4 - INPUT/OUTPUT NETWORKS
PROGRAM: MLR0 MSG-INDX: nn -- APA -- yy.ddd / hh:mm:ss

MESSAGE:
Usage Notes
To select a function, enter the appropriate number in the FUNCTION field and press
Enter. The APA Prompt panel is returned. You can request specific graphing options with
that panel.
Note: You can find more information about APA graphs and their descriptions in the
Report Reference Guide.
APA Prompt Panel

Use this formatted panel to specify online APA graphing options. It has no equivalent in
batch mode. The top line GRAPHc commands can be used in batch mode to provide
hardcopy graphs.
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.

APA Command
This panel also displays when an error occurs on an online top line GRAPHc command.
---------------- 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 ID10: nnnn
FROM: MM: mm DD: dd YY: yy DEFAULT IS TODAY;

MM WITHOUT DD DEFAULT IS DD = 01
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:
More information:
GRAPHc Command (see page 275)
Usage Notes
The CATEGORY field can be changed and is blank if command GRAPH is entered.
This panel appears with CATEGORY filled in if one of the APA commands is entered
without other keywords; that is, GRAPHS would produce this panel with CATEGORY of S.

FUNCTION
(Optional) Specifies the function that you want. The following are the possible
values:
G
Displays graphs specified by the CATEGORY and ID fields on this panel. This is
the default.
C
Displays contents of current counters for every graph specified by the
CATEGORY field. Same as LIST=ALL option on equivalent top line command.

APA Command
D
Displays graph format parameter definitions for every graph specified by the
CATEGORY field. Same as LIST=DETL option on equivalent top line command.
H
Displays directory list of every ID and title specified by the CATEGORY field.
Same as LIST=HELP option on equivalent top line command.
The name of any other formatted panel can be entered.
CATEGORY
Specifies a graph category. Required field. If accessed from the APA Menu panel,
with a DB.n command or FUNCTION, or with a top line GRAPHc command without
any other keywords, this is completed for you. You can change this if you want. If
accessed through the GRAPH command (or function), this must be entered.
Descriptive name of the category is enclosed in parentheses following the value.
Categories and their descriptive names are as follows:
D
DATABASE
J
JOBS
N
NETWORKS
S
SYSTEM
???????
indicates a category value is needed.
The following fields are ignored unless FUNCTION is G or blank.

DESIRED GRAPHS
ID 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 to four digits.
Leading zeros not required. Function H or the equivalent top line command with
LIST=HELP lists the available graph ID numbers. The Report Reference Guide also
provides a brief discussion of each graph.
FROM
Specifies 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.

APA Command
MM
Specifies a month portion of FROM date. Optional. Default is current month. MM
format. Leading zero not required. Must be at least 1 and not more than 12.
DD
Specifies 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.
YY
Specifies a year portion of FROM date. Optional. Default is current year. YY format.
Leading zero not required. Must be numeric.
THRU
Specifies a last date for which data is to be displayed. Optional. Default is today's
date. Any date beyond today's date is automatically changed to current date. Same
as keyword TO on equivalent top line command.
MM
Specifies a month portion of THRU date. Optional. Default is current month. MM
DD
Specifies 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 is current date. DD
YY
Specifies a year portion of THRU date. Optional. Default is current year. YY format.
Leading zero not required. Must be numeric.
TEMPORARY OVERRIDES
Specifies 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 value under the heading
SCALE. The value used is shown as part of the graph heading. When provided, each
graph specified in the ID fields uses this override value.
DIV1
Specifies a temporary override to division factor for the primary counter. Up to
seven digits. Optional field. Same as keyword DIV1 on equivalent top line command.
Function D or top line command with LIST=DETL lists the predefined value under
the heading DIV1. When provided, each graph specified in the ID fields uses this
override value.

APA Command
DIV2
Specifies a temporary override to division factor for the secondary counter for each
graph requested. Up to seven digits. Optional field. Same as keyword DIV2 on
equivalent top line command. Function D or top line command with LIST=DETL lists
the predefined value under the heading DIV2 if one exists. Only valid if a value is
shown there. When used, each graph defined in the ID fields must be the type that
has a predefined DIV2 value.
GLINE
Specifies 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 predefined values. If that list indicates PRIM
under the GRAPH heading for a graph, PRIM is the only valid option for that graph.
When used, each graph defined in the ID fields must be compatible with the value
entered here.
Enter the value you want and press Enter. The entered values are converted into the
equivalent top line command and processed accordingly. That top line command is
echoed at the top of the resulting displays. It can be modified to perform another
display or any other top line command can be entered in its place.
Note: For more information about the keywords used with that top line command
technique, see the discussion of the GRAPHc command.
This panel allows data to be entered that could require more than the maximum of 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 into the available space for the
command echo are dropped completely from the echo even though they are being
processed. Fields are placed in the echo area in 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 a message at
the bottom indicating "request completed."
PF7 and PF8 are temporarily overridden to page backward/forward for ease in browsing
any multipage display that may occur. If PF7 or PF8 were set to some other values by
the user, those values are temporarily ignored. They revert back to the values defined
by the user whenever PF3 or a top line command is entered.
PF3 is also temporarily overridden to return to the APA menu panel.
More information:
GRAPHc Command (see page 275)

ARFP Command
ARFP Command
The ARFP command purges the ARF requirement for a job in the request, ready, or
active queue.
ARFP,JOB=jobnumber[,FORCE=YES]
JOB
Defines the unique CA 7 job number (leading zeros not required) for the job whose
ARF requirements you want to purge.
FORCE
(Optional) Specifies to force the purging of the ARF requirement for a job even if it
does not exist in the request, ready, or active queue.
Example
ARFP,JOB=23
ARTS Command
The ARTS command interfaces directly with CA WA Restart Option (CA 11) when you
have installed the interface with CA Restart Option.
Note: For more information about the interface with CA WA Restart Option and the
ARTS command, see the Interface Reference Guide.
AR.3 Command
Note: For more information about defining ARF conditions using the AR.3 command, see
the Database Maintenance Guide.

BLDG Command
BLDG Command
The BLDG command builds a generation data group (GDG) index. This command is valid
only for CVOL catalogs.
Note: The BLDG command is not valid for VSAM or ICF catalogs.
This function is available on the UT Menu panel as FUNCTION value 6 or on any other
menu or formatted panel as FUNCTION value UT.6.
BLDG,INDX=index,ENTRIES=nnn[,FULL={DELETE|EMPTY}
INDX
Defines the name of the GDG index.
ENTRIES
Defines the number of entries to be contained in the GDG index.
FULL
Specifies action to be taken once the ENTRIES value is exceeded.
DELETE
Specifies the oldest entry is to be removed. DELETE is the default.
EMPTY
Specifies all entries are to be removed.
Examples
BLDG,INDX=USER.FILE.MONTHLY,ENTRIES=2
BLDG,INDX=USER.FILE.DAILY,ENTRIES=7,FULL=EMPTY
BLDG,INDX=USER.DAILY.FILE1,ENTRIES=30,FULL=DELETE
Note: For more information about restrictions and guidelines on the use of BLDG, see
Message UTL5-14 in the Message Reference Guide.

CALMOD Command
CALMOD Command
The CALMOD command displays the DB.2.8 Base Calendar Maintenance panel.
Note: For more information about this panel, see the Database Maintenance Guide.
CALMOD
No keywords are associated with the CALMOD command.
CANCEL Command
The CANCEL command deletes jobs from the CA WA CA 7 Edition queues.
■ For CPU jobs, the CANCEL command only removes the job from the CA WA CA 7
Edition queues. Cancellation of a job in the CA WA CA 7 Edition active queue or
ready queue (if it has been submitted) does not cause termination of the job's
execution. CPU jobs that can be executing have to be canceled from the operating
system separately. Execution must be terminated from an OS system console.
■ For XPJOB jobs, the CANCEL command removes the job from the CA WA CA 7
Edition queues. If the initialization option XPDEF, XPKILL is set to YES, and the XPJOB
job has been submitted to the target node but is still in the ready queue or the
active queue, a cancel request is created and sent to the target node. Some remote
CA Scheduling Agents support the cancel request, and the request cancels or "kills"
the process execution. It is not the responsibility of CA WA CA 7 Edition to verify
that the target platform supports the kill facility. If the cancel request was not
transmitted, an error message appears in the browse and log data.
■ For agent definition jobs (AGJOBs), the CANCEL command sends a request to the
agent and removes the job from the CA WA CA 7 Edition queues. If the agent is not
active at the time of the CANCEL request, the message is queued and sent when the
agent becomes active.
If the initialization option XPDEF, XPKILL is set to NO, the XPJOB is canceled from the CA
WA CA 7 Edition queues, and no cancel request is sent to the target platform. To view
the XPKILL option, enter the command /DISPLAY,ST=XPS.
This function is available on the QM.1, QM.6, and QM.7 panels as option C. The CANCEL
command has three formats, depending on the queues in which the task resides.

CANCEL Command
Cancel Input Networks

The CANCEL command has the following format for input networks:
CANCEL,JOB=jobnumber
JOB
Defines the unique CA 7 job number (leading zeros not required) for the
workstation network to be canceled.
Cancel Request, Ready or Active Queue Jobs

The CANCEL command has the following format for request, ready or active queue jobs:
CANCEL,{JOB={jobname|jobnumber}|JOBL=longjobname}
[,FORCE=YES]
[,KILL={NO|YES}]
[,REASON=text]
JOB
Defines the job to cancel. JOB and JOBL are mutually exclusive.
jobnumber
Defines the unique CA 7 job number (leading zeros are not required) for the job
to cancel.
jobname
Lets you cancel a job by job name when only one job with that name is present
in the request queue.
JOBL
Defines the job to cancel. JOB and JOBL are mutually exclusive.
longjobname
Lets you cancel a job by long job name when only one job with that name is
present in the request queue.

CANCEL Command
FORCE
(Optional) Specifies to force the cancellation of the job. If you want to cancel the
job to dump the log data set, specify FORCE=YES to prevent the job from being
resubmitted. Use FORCE=YES when a job to be canceled shows a status of
SKELETON or RETRY. Use FORCE=YES to cancel a job with connected resources.
Important! Use of this option can potentially cause CA WA CA 7 Edition to abend;
therefore, only use it as a last resort.
KILL
(Optional) Specifies to stop the job immediately, rather than letting the canceled
job terminate typically.
REASON
(Optional) Defines the reason for the job cancellation. Depending on the
initialization file CANCEL statement value, this reason can be required or optional. If
it is required but not given, a message prompts the user to provide it. The text is
entered into the run log entry for this occurrence of this job and is displayed on any
subsequent LRLOG inquiries.
Required: No (depending on initialization options)
Cancel Output Networks

The CANCEL command has the following format for output networks:
CANCEL,JOB=jobnumber[,NW={network|ALL}][,SUBID={subid|ALL}]
JOB
Defines the unique CA 7 job number (leading zeros not required) of the job whose
postprocess work is to be canceled.
NW
(Optional) Defines the networks to cancel.
network
Defines the network name as previously defined in the database.
ALL
Specifies to cancel all networks for the associated job.

CANCEL Command
SUBID
(Optional) Defines a further qualification of the network to be acted upon. SUBID is
optional unless it was specified when the network was demanded or is part of the
database definition of a regularly scheduled network. Since a single output
workstation network can be associated with a job multiple times and assigned
unique SUBIDs for differentiation, it is important to specify correct SUBIDs when
canceling work.
subid
Defines the sub-ID value.
ALL
Specifies to cancel network entries for the NW value specified no matter what
sub-ID value was used.
Usage Notes
The record for the specified job is deleted from the appropriate queue, and if CA WA
Restart Option is used, an attempt is made to clear the CMT.
Note: For more information about CA WA Restart Option, see the Interface Reference
Guide.
Obviously, canceling a job stops all triggering by the canceled job and does not satisfy
requirements for other jobs that may be dependent on the canceled job.
The job does not go through normal job completion; therefore, job triggering and
requirement posting are not performed.
All output workstation networks for the canceled job are notified and their records are
deleted from the postprocess queue.
The QM.1 panel can also be used to cancel jobs.
For XPJOB jobs, the XPDEF, XPKILL initialization keyword can be set to send a cancel
request to a target platform. To ensure the job (or process) has been canceled from the
target node, monitor that platform as necessary because CA WA CA 7 Edition does not
ensure that the cancel has taken effect. If the cancel request was not sent to the target
platform, the browse and log data reflects the returned information from the send
request. Possible causes include a CAICCI issue or the unavailability of the target system.
Note: For more information about the XPKILL keyword in the XPDEF initialiation file
statement, see the Systems Programming Guide.

CAT Command
Examples
This example illustrates a network in the preprocess queue:
CANCEL,JOB=17
This example illustrates a job in the request, ready, or active queue:
CANCEL,JOB=163
These examples illustrate networks in the postprocess queue:
CANCEL,JOB=163
CANCEL,JOB=163,NW=ALL,SUBID=ALL
CANCEL,JOB=163,NW=REPTS,SUBID=ALL
CANCEL,JOB=163,NW=REPTS,SUBID=CA7HIST3
This example wihtout a SUBID cancels all occurrences of the specified network with this
job number and a SUBID of spaces:
CANCEL,JOB=163,NW=REPTS
CAT Command
The CAT command catalogs a data set. This function is available on the UT Menu panel
as FUNCTION value 2 or on any other menu or formatted panel as FUNCTION value
UT.2.
CAT,DSN=dsname,VOL={volume|(volume,...)}
[,{DVC=xxxxxxxx|UNIT=unit}]
[,SEQ=n]
[,CVOL=cvolume]
DSN
Defines the fully qualified name of the data set to be cataloged.

CAT Command
VOL
Defines from one to five volumes on which the data set resides.
volume
Defines the volume on which the data set resides.
(volume,...,volume)
Specifies from one to five volumes as a list. If more than one volume is
specified, they must be enclosed in parentheses.
DVC
(Optional) Defines a hexadecimal device code. This field must be omitted if UNIT is
specified.
UNIT
(Optional) Defines the unit name of the type of device that you want (generic
equivalent of a device code found in SASSUTBL (for example, 3350, DISK)). This field
must be omitted if DVC is specified.
SEQ
(Optional) Defines the label sequence number.
Default: 0 for disk data sets, or 1 for tape data sets
Limits: 1 numeric character
CVOL
(Optional) Defines the volume containing the catalog. This option is only valid for
CVOL catalog structures. If the catalog structure is ICF, it defaults to the IPL catalog.
Default: SYSRES (for CVOL catalog structures)
Usage Notes
If VOL specifies a DASD volume available to CA WA CA 7 Edition, you can omit both DVC
and UNIT.
Update the module SASSUTBL to contain all user-defined generic names.
You can use a +1 generation number to catalog a new version of a generation data set.

CONN Command
Examples
CAT,DSN=USER.FILE1,VOL=DA3330
CAT,DSN=USER.FILE2,VOL=DA3330,DVC=30502009
CAT,DSN=USER.FILE3,VOL=DA3330,UNIT=3330
CAT,DSN=USER.TAPE,VOL=T10001,SEQ=3,DVC=34008003
CAT,DSN=USER.TAPE1,VOL=(T10002,T10003),UNIT=3400-3
CAT,DSN=USER.FILEX,VOL=DA0001,CVOL=ALTRES
CONN Command
The CONN command connects high-level indexes from the SYSRES catalog to another
catalog.
Note: The CONN command is not valid for VSAM or ICF catalogs.
CONN,INDX=index[,VOL=volume]
INDX
Defines the name to be entered as a high-level index in the SYSRES catalog.
VOL
(Optional) Defines the volume serial number of the connected volume. You can
omit this field to display the connected volume for the specified index. The
connected volume must be available to CA WA CA 7 Edition.
Default: SYSRES (for CVOL catalog structures)
Examples
CONN,INDX=USER,VOL=ALTCAT
CONN,INDX=USER

CTLG Command
CTLG Command
The CTLG command maintains and modifies the CA WA CA 7 Edition index entries. The
primary use of data set entries is to determine the availability of input requirements for
job scheduling. The three most current creations of each data set (by CA WA CA 7
Edition submitted jobs) are recorded in the database, regardless of whether the data set
is a GDG. The volume serial data is informational only, because the system catalog
remains the source for locating data sets during job processing.
CTLG,DSN=dataset,TYPE={ADD|CON|COPY|DEL|REPL},VOL={volser|(volser,....)}
[,DVC=nnnnnnnn]
[,ENTRY=n]
[,SEQ=nnn]
DSN
Defines the data set name to be modified.
TYPE
Specifies the CTLG function to be performed. Function must be one of the
following:
ADD
Specifies to add new entries for a data set already defined in the CA WA CA 7
Edition database.
CON
Specifies to consolidate system and database entries.
COPY
Specifies to copy system catalog entries.
DEL
Specifies to delete existing entries.
REPL
Specifies to replace existing entries.
Processing for these CTLG functions is described on the following pages.

CTLG Command
VOL
Defines the volume serial numbers on which the data set resides.
volser
Defines a single volume.
(volser,...,volser)
Defines up to ten volumes enclosed in parentheses and separated by commas.
(Processing for TYPE=REPL discusses replacing entries with more than ten
volumes.)
DVC
(Optional) Defines the device type code for the data set.
Default: Device code of current entry
Limits: 8 digits - hexadecimal
ENTRY
Defines the entry to delete or replace. ENTRY is required when TYPE=DEL or
TYPE=REPL. ENTRY=1 is the most recent.
Limits: 1 numeric character from 1 to 3
SEQ
(Optional) Defines a label sequence.
Default: Label sequence of current entry
More information:
Processing for TYPE=REPL (see page 191)

CTLG Command
Usage Notes
The database can require some 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 restarts or
reruns.
The CTLG command lets you perform the following tasks:

■ ADD new entries.
■ REPLACE existing entries.
■ DELETE entries.
■ COPY information from the OS system catalog.
■ CONSOLIDATE the database and system catalog to ensure the two are synchronous.
Examples
These examples add entries.
CTLG,DSN=CA7.DSN1,TYPE=ADD,VOL=DASD07
CTLG,DSN=CA7.TAPEDS,TYPE=ADD,VOL=(000001,000003)
CTLG,DSN=CA7.DSN2,TYPE=ADD,VOL=DASD-7,DVC=30502009,SEQ=1
These examples delete entries.
CTLG,DSN=CA7.DSN,TYPE=DEL,ENTRY=1
These examples replace entries.
CTLG,DSN=CA7.DSN1,TYPE=REPL,VOL=DASD08,ENTRY=1
CTLG,DSN=CA7.DSN2,TYPE=REPL,VOL=TAPE01,SEQ=3,ENTRY=2
This example consolidates entries.
CTLG,DSN=CA7.DSN1,TYPE=CON

CTLG Command
Processing for TYPE=ADD

CA WA CA 7 Edition automatically stores the current date and time in the new entry as
creation date and time.
You can find hexadecimal values to be specified if DVC is used in an IBM Data Areas
Manual under UCBTYP field.
You cannot use the ADD function if a data set to be added resides on more than ten
volumes. Catalog the data set on the system catalog, and then use the COPY function of
the CTLG facility.
When adding GDGs, consider these items with respect to how the DSN is specified:
■ Relative generation numbers cannot be used.
■ If an absolute generation number (for example, GnnnnVnn) is specified, that
number is used.
■ If no generation number is given and an entry currently exists, the current
generation number is incremented by 1 and used for the new entry.
■ If no generation number is given and no entry currently exists, G0001V00 is
assumed.
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 is scheduled, the
external requirement is automatically satisfied by initial requirements scan when the job
is scheduled. If the entry is added after scheduling of the user job, the external
requirement must be manually posted as satisfied.
Processing for TYPE=DEL

When deleting a GDG entry, if the absolute generation is given in the DSN, the entry
corresponding to that generation is deleted even if the ENTRY=value indicates a
different entry.

CTLG Command
Processing for TYPE=REPL

CA WA CA 7 Edition automatically stores current date and time in the replacement entry
as creation date and time.
You can find hexadecimal values to be specified if DVC is used in an IBM Data Areas
Manual under UCBTYP field.
You cannot use the REPL function if the data set entry to be replaced contains more
than ten volumes. Use the COPY function to obtain the replacement from the system
catalog.
When replacing GDG entries, no generation number is needed. The generation of the
entry being replaced is used instead.
Processing for TYPE=COPY

CA WA CA 7 Edition automatically stores current date and time as creation date and
time for the newly copied entry.
When copying GDGs, the most current generation in the system catalog is used.
Processing for TYPE=CON

Only the most recent entry (for the data set) in each catalog is reviewed. If the entries
agree, no action is taken.
If the entries disagree, the database entry is updated and the current date and time are
stored as creation date and time.

DB Command
DB Command
The following table gives a brief description of the DB commands.
Note: For more information, see the Database Maintenance Guide where they are fully
described.
Although CPU is referenced in many panel titles, these panels also apply to the internal
cross-platform job types unless mentioned otherwise.
Command Panel Title Description

DB CA-7 Database Maintenance Menu Select from various database maintenance
functions.
DB.1 CPU Job Definition Enter or review data related to CPU jobs.
DB.10 XP Job Definition Enter or review data related to XPJOB jobs.
DB.11 Agent Job Definition Enter or review data related to agent jobs.
DB.2 Scheduling Menu Access the scheduling definition formatted
panels.
DB.2.1 Job Scheduling Define or review options taken for jobs with
date/time schedules.
DB.2.2 Input Network Scheduling Define or review scheduling options for input
networks.
DB.2.3 Output Network Scheduling Define or review options taken for output
network schedules.
DB.2.4 Job Triggering Review or define jobs that trigger scheduling of
other jobs when they successfully complete.
DB.2.5 Input Network Triggering Define or review input networks that trigger job
scheduling when their last workstation is
logged out.
DB.2.6 Data Set Triggering Define or review data sets that trigger job
scheduling when either their creating jobs
complete successfully or when the
created/updated data set is closed.
DB.2.7 Modification to Resolved Schedule Dates Provides a rapid and direct method of
permanently altering the resolved schedule
information for either a job or input network
without having to totally redefine the schedule.
DB.2.8 Base Calendar Maintenance List, define and update base calendars residing
in the CA WA CA 7 Edition Calendar PDS.

DB Command
Command Panel Title Description

DB.3 Job Predecessor/Successor Menu Select various panels for defining "connections"
(predecessor requirements) to jobs.
DB.3.1 Data Set Predecessors Allows you to modify requirements or to add
data set requirements for data sets that 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 requirements (or connections) for
workstation networks.
DB.3.6 User Memo-Form Predecessors Enable a user requirement of free-form text to
display on a CA WA CA 7 Edition terminal and
that require an operator response before the
connected job can execute.
DB.4 Workload Documentation Menu Select various documentation functions.
DB.4.1 CPU Job Documentation Defining free-form job level documentation.
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 which
manual tasks are performed.
DB.6 Data Set Definition Define a user data set to CA WA CA 7 Edition.
DB.7 JCL Library Maintenance Enter or review JCL or PARM statements in PDS
or sequential JCL libraries. It can also be used to
review CA Librarian or CA Panvalet for z/OS JCL.
DB.8 None Begin text editor functions.
DB.9 None Clear the text editor active area.

DCONN Command
DCONN Command
The DCONN command disconnects high-level indexes previously connected to the
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,INDX=index
INDX
Defines the name of the index to delete from the SYSRES catalog.
Examples
DCONN,INDX=USER
DCONN,INDX=USERNODE
DEALLOC Command
The DEALLOC command releases volumes that were previously allocated with the ALLOC
command or function 11 of the UT Menu panel. This function is available on the UT
Menu panel as FUNCTION value 12 or on any other menu or formatted panel as
FUNCTION value UT.12.
DEALLOC,VOL=volume
VOL
Defines the volume whose allocation you want to release.
Examples
DEALLOC,VOL=DISK01

DEMAND, DEMANDH Command

The DEMAND command forces immediate scheduling of a job into the CA WA CA 7
Edition request queue. Jobs that do not have definable processing cycles can be
scheduled in this manner. Demand scheduling can also be used to force an early
execution of jobs that have defined processing cycles or to schedule jobs for the first
time, before they have been defined in the database.
The DEMANDH command indicates that the demanded job is placed on hold in the
request queue.
{DEMAND|DEMANDH},{JOB=jobname|JOBL=longjobname}
[,ARFSET={arfsetname|**NONE**}]
[,CC=nnnn]
[,CLASS=x]
[,COUNT=nnnn]
[,DATE={+nn|yyddd}]
[,DEPJOB=jobname2]
[,DOTM=hhmm]
[,EXEC={NO|YES}]
[,FROMNODE]
[,INTERVAL=hhmm]
[,{JCLID=nnn|JCLLIB=&x...x}]
[,LATE={NO|YES}]
[,LEADTM={0100|hhmm}]
[,MAINID={ALL|SYn|/SYn|-SYn}]
[,PRTY=nnn]
[,RMS={NO|YES}]
[,RO={EQ|LT|GT|GE|LE|NE|#S|IG|0}]
[,SCHID={1|nnn}]
[,SET={NDB|NTR|SKP}]
[,STOP=hhmm]
[,TIME={hhmm|+hhmm}]
[,TYPE={CLOCK|END|RES|START}]
CC and RO are invalid with agent jobs.
You cannot specify the FROMNODE keyword.
JCLID, JCLLIB, MAINID, and RMS are invalid with internal cross-platform jobs.

JOB
Defines the name of the job being demanded. The demanded jobs are placed in the
request queue and assigned a unique CA 7 job number. JOB and JOBL are mutually
exclusive.
JOBL
(Optional) Defines the long name of the job being demanded. The demanded jobs
are placed in the request queue and assigned a unique CA 7 job number. JOB and
JOBL are mutually exclusive.
ARFSET
(Optional) Defines the ARF set name that is 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**
CC
(Optional) Defines, with RO (relational operator), the job-level condition codes that
are used to determine whether a job executes successfully. If specified, this value
overrides the RO defined for the job in the CA WA CA 7 Edition database. RO is
required when CC is specified.
Default: The job definition panel COND-CODE value when the job is defined to CA
WA CA 7 Edition; otherwise 0.
Limits: 1 to 4 numeric characters from 0 to 4095. Invalid with agent jobs.
CLASS
(Optional) Defines the workload balancing class for resource checking.
Limits: 1 alphanumeric character
COUNT
(Optional) Defines the maximum number of times to repeat the job. COUNT is
ignored if INTERVAL is not specified. If both COUNT and STOP are specified, the job
stops repeating when the COUNT reaches zero or the STOP time is 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. The leading zeros can be
discarded.

DATE
(Optional) Defines due-out and submit dates.
Limits: If used, specify DOTM or TIME.
+nn
Defines the number of days after the current date.
yyddd
Defines the Julian date to run the job.
DEPJOB
(Optional) Defines a single predecessor job that must complete while the
demanded job is waiting.
DOTM
(Optional) Defines 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 the lead
time is assumed.
If DOTM is specified on the DEMAND/DEMANDH command and the value that is
given is earlier than the current time, the due-out day is assumed to be the
following day.
If DOTM and LEADTM are both omitted, then deadline start time is assumed to be
the current time plus the LEADTM.
Default: Current time
Limits: hh= 1 through 2 numeric characters from 0 to 24
mm= 2 numeric characters from 00 to 59
Required: No (unless DATE is used, if so, DOTM or TIME must be specified)
EXEC
(Optional) Specifies whether to execute the job (YES/NO). If NO (N) is used, the job
does not run but shows a normal completion as if it did run. The value that is
specified here overrides the value that is coded on the job definition EXEC field.
Default: The job definition panel EXEC value if the job is defined to CA WA CA 7
Edition; otherwise YES.

INTERVAL
(Optional) Identifies that the job should be repeated (executed more than once)
and defines the amount of time between each iteration. If INTERVAL is specified,
the TIME and TYPE keywords are required. If both INTERVAL and COUNT are
specified, the INTERVAL value times the COUNT value must total less than 24 hours.
For information about how the 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 through 2 numeric characters from 0 to 23
mm=2 numeric characters from 00 to 59
JCLID
(Optional) Defines the JCL data set that contains the execution JCL to be submitted.
If used, the value must be a numeric INDEX associated with the wanted JCL data set
(on the JCL statement in the initialization file). If the job is defined in the database,
the value must be the same as the value on the DB.1 panel or the Optional
PARMLIB/Parmlib value on the DB.10 and DB.11 panels. (For more information
about the initialization file, see the Systems Programming Guide.) This field or the
JCLLIB field is required if the job is not defined in the database. JCLID and JCLLIB are
mutually exclusive.
Note: Attempts to run cross-platform jobs that are not defined to the database fail
because they are treated as regular CPU jobs when processed.
Limits: 1 to 3 numeric characters from 0 through 254 and from 256 through 999.
255 is reserved.
Required: No, unless job is not defined in database
JCLLIB
If used, the value must be a symbolic INDEX associated with the wanted JCL data set
JCLID field is required if the job is not defined 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 JCLLIB causes the
job to enter the request queue in SKELETON status.

LATE
(Optional) Specifies whether a notification occurs when the job becomes late.
Specify YES (Y) to make the job eligible to be marked LATE. If NO (N) is used, the job
is never marked LATE. The value that is specified here overrides the value that is
coded on the job definition PROMPTS field.
LEADTM
(Optional) Defines the amount of elapsed time that is required to process the job.
Indicates in hours (hh) and minutes (mm) the elapsed time. The maximum value
that you can specify is 2400.
Default: 1 hour
Limits: hh= 1 through 2 numeric characters from 0 to 24
MAINID
(Optional) Specifies the MAINID, as defined in the initialization file CPU statement,
to which you want to redirect the job. The value that is specified here overrides the
value that is coded on the job definition MAINID field. Also, the SASSXX05 user exit
does not override this value.
The name must be one of the following values:
ALL
Specifies all CPUs are acceptable for executing the job.
SYn
n defines the CPU to which the job is being redirected. The value of n can range
from 1 to 7.
/SYn
n defines a CPU to which the job cannot be submitted. The value of n can range
from 1 to 7.
-SYn
from 1 to 7.
Limits: Invalid for internal cross-platform jobs.

PRTY
(Optional) Defines the initial workload balancing priority.
RMS
(Optional) Specifies whether CA WA CA 7 Edition inserts the CA 11 RMS step.
Specify YES (Y) to insert the step with the CA 11 processing code of P. Enter NO (N)
to indicate do not insert of the RMS step. The value that is specified here overrides
the value that is coded on the job definition INSERT-RMS field.
Default: The job definition panel INSERT-RMS value if job defined to CA WA CA 7
Edition; otherwise NO.
Limits: Invalid for internal cross-platform jobs.
Note: For more information, see the Interface Reference Guide.
RO
(Optional) Specifies the relational operator of the condition code (CC) or if the step
level #SCC statements are being used in the job's JCL. If specified, this RO overrides
the RO defined for the job in the CA WA CA 7 Edition database. The following values
are valid:
EQ
Equal to
LT
Less than
GT
Greater than
GE
Greater than or equal to
LE
Less than or equal to
NE
Not equal to
#S
Step condition code tests to be made based on #SCC statement.
Note: For more information, see the #SCC statement in the Database
Maintenance Guide.

IG
No evaluation of the job is done. CA WA CA 7 Edition always assumes the job
completes successfully, regardless of condition codes, abend codes, or run-time
JCL errors.
0
No condition code test is made.
Default: The job definition panel RO value if the job is defined to CA WA CA 7
Edition; otherwise 0
Limits: Invalid with agent jobs.
SCHID
Defines the schedule ID within the job's total schedule definition to use for this run.
If omitted, SCHID=1 is assumed unless the job exists in the CA WA CA 7 Edition
database and has an associated schedule. In this case, the first SCHID defined in the
schedule member is assumed.
Default: 1
Limits: 1 to 3 numeric characters from 1 to 255 (See Note)
Note: If the SCHEDULE statement in the initialization file specifies SCHID=YES, this
parameter is required.
SET
(Optional) Specifies skip the next scheduled cycle for the job (SKP), disable
triggering (NTR), or bypass the database updating at the job completion.
SKP
Specifies this run of the job takes the place of the next scheduled run. This
value has the same effect as entering NXTCYC,SET=SKP. It is reflected on output
from LJOB and LLOCK commands as if NXTCYC,SET=SKP was used. This
parameter is invalid if the job has no schedule. SET=SKP has no impact on
repeating jobs that are already in the CA WA CA 7 Edition queues.
NTR
Specifies normal triggering is disabled only for this run of the job.
NDB
Allows a job to bypass all load processing at the job completion, but allows
other processing to proceed typically.
Note: Data set triggering is still in effect.

STOP
(Optional) Defines the clock time after which the job is not repeated. STOP is
ignored if INTERVAL is not specified. If both COUNT and STOP are specified, the job
stops repeating when either the COUNT reaches zero or the STOP time is reached,
whichever comes first.
If the STOP time is less than the submit time, the stop date is assumed to be the
following day.
Default: 1439 minutes (24 hours minus 1 minute) after the submit time
Limits: hh=1 through 2 numeric characters from 0 to 23
mm=2 numeric characters from 00 to 59
TIME
(Optional) Defines a submit time-of-day requirement for the job. If the format is
used with a +, the submit time is calculated from the current time, adding the
specified number of hours and minutes. If the + is used, the DATE keyword must be
omitted.
Limits: + is optional
hh= 1 through 2 numeric characters from 0 to 23
Required: No (unless DATE is used, if so, specify DOTM or TIME (hhmm format).
Also required if TYPE=CLOCK is specified.
TYPE
(Optional) TYPE=RES specifies the job is being scheduled in restart/rerun status.
TYPE=CLOCK, START, or END controls how the submit time requirement is
calculated for repeating jobs.
When TYPE=RES the job is put into the request queue with a restart requirement.
The job is not submitted before the CA WA CA 7 Edition restart is done. The output
networks are scheduled, but input requirements checking is bypassed.
TYPE=CLOCK, START, or END is ignored if INTERVAL is not specified. With
TYPE=CLOCK, the interval is added to the previous iteration's submit time
requirement to determine the new submit time requirement. With TYPE=START
and END the interval is added to the previous iteration's last (most recent) start and
end time, respectively, to determine the new submit time requirement. TYPE is
required when INTERVAL is specified.
Limits: RES, CLOCK, START, or END

Usage Notes
Demanding a job into the request queue does not automatically result in immediate
submission for execution. When a DEMAND is issued for a job, that job is placed in the
request queue where the availability of its input requirements is determined. (To
request immediate scheduling without requirements checking, use the RUN and RUNH
commands.) The same process occurs when a job is automatically scheduled into the
queues.
Using SET=NDB can allow a job not defined to CA WA CA 7 Edition to be run under the
CA WA CA 7 Edition control and not be added to the database when it completes.
Input workstation networks must be demanded separately from jobs. If a demanded job
requires input workstation activity, the network responsible for that activity must be
requested separately using the DMDNW command.
Preprocessing work can be demanded well in advance of the job for which it is a
requirement. This can be necessary if the preprocessing activity requires several hours
or days of lead time, or if the work is available and is requested to be done early during
a slack period.
Output workstation networks associated with a job are automatically placed in the
postprocess queue when the CPU job is demanded.
Output networks can be demanded separately from their associated CPU jobs by a
DMDNW command.
Demanded work is assigned the UID of the operator issuing the DEMAND command 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 unless generated
by CA WA CA 7 Edition internally. This keyword cannot be coded on online, batch, or
trailer terminal transactions. It is reserved to indicate that the DEMAND is issued in
response to a scheduling request from an XPS client.
All internal cross-platform jobs must be defined in the CA WA CA 7 Edition database

because selected information for each job is contained in the internal cross-platform job
definition. Attempts to add them using the DEMAND(H) command will fail.

Repeating Jobs
A job can be brought into the request queue using the DEMAND command and
executed more than once. Each iteration must successfully complete (or be forced
complete) before the next iteration is added to the request queue.
The following keywords are used with repeating jobs:

INTERVAL
Required. Defines the amount of time between each iteration of the job.
TYPE
Required. Specifies how the submit time requirement of each iteration is
calculated—by adding the INTERVAL to the previous iteration's submit time
requirement (CLOCK), START, or END time.
COUNT
Optional. Defines the maximum number of times the job will be repeated.
STOP
Optional. Defines the clock time after which the job is not to be repeated. If not
specified, the stop time is 1439 minutes (24 hours minus 1 minute) after the submit
time requirement of the first iteration.
TIME
Required. Defines the submit time requirement of the first iteration.
LEADTM
Optional. Defines the amount of time required to process the job. If not specified,
0100 (1 hour) is used.
DOTM
Optional. Defines the due-out time (expected completion time) of the first iteration.
If not specified, the current time plus the LEADTM is used.
As each iteration successfully completes (or is forced complete), CA WA CA 7 Edition

adds the INTERVAL to the submit time requirement, start time, or end time based on
the TYPE setting. This value becomes the next iteration's submit time requirement.
The new submit time requirement is then compared to the STOP time. If either the new
submit time requirement or the current time are greater than the STOP time, the job is
not repeated.
The new job's due-out time is calculated as the new submit time requirement plus the
difference between the original due-out time and the original submit time requirement.

DIRECT Command
The new job's deadline time is calculated as the new due-out time minus the original
lead time (LEADTM).
The start and end times of the job are local to the system where the job executed, not
local to the system where CA WA CA 7 Edition is executing. TYPE=START and END should
be used with care for NJE and cross-platform jobs.
Examples
DEMANDH,JOB=CA7JOB1
DEMAND,JOB=CA7JOB1,DOTM=1600,LEADTM=0045
DEMAND,JOB=CA7JOB3,JCLID=7,SCHID=14
DEMAND,JOB=CA7JOB2,TYPE=RES
DEMAND,JOB=CA7JOB4,SET=NTR
DIRECT Command
The DIRECT command alters any defined MAINID for a CPU job in the request or ready
queue before the job is submitted for processing.
Note: You cannot use the DIRECT command with internal cross-platform jobs.
DIRECT,JOB=jobnumber,MAINID={ALL|SYn|/SYn}
JOB
Defines the unique CA 7 job number of the job whose MAINID is to be changed. The
job must be in the request or ready queue and not already submitted.

DIRECT Command
MAINID
Specifies the MAINID, as defined in the initialization file CPU statement, to which
the job is to be redirected. The name must be one of the following:
ALL
SYn
from 1 to 7.
/SYn
from 1 to 7.
Usage Notes
Changing a MAINID with the DIRECT command does not cause a change to the 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 spool environment
unless a user-supplied submit exit inserts appropriate JES control statements.
You can use the QM.3-X CPU Job Attributes panel as an alternative for this purpose.
If a job has already been submitted and the DIRECT command is to be used because a
CPU is down, the job must be requeued before this command takes effect.
The DIRECT command is not valid for internal cross-platform jobs because these jobs
execute on other platforms. To change the destination node, use the XUPD or QM.3
screen.
More information:
XQ, XQJ, XQN, and XQM Commands (see page 712)

REQUEUE Command (see page 623)
Examples
DIRECT,JOB=15,MAINID=SY3
DIRECT,JOB=73,MAINID=/SY1

DLTX Command
DLTX Command
The DLTX command deletes inactive indexes in the catalog.
Note: This command is not valid for VSAM or ICF catalogs.
DLTX,INDX=index[,CVOL=volume]
INDX
Defines the fully qualified name of the index to be removed.
CVOL
(Optional) Defines the volume containing the catalog. If this field is omitted, the
search begins with the system residence volume, and a standard catalog search is
employed.
Usage Notes
CA WA CA 7 Edition attempts to delete as many index levels as possible. One request
could result in the removal of multiple index levels.
Examples
DLTX,INDX=USER.LEV1.LEV2.LEV3
DLTX,INDX=USER.LEV1.LEV2,CVOL=ALTCAT
DLTX,INDX=USER.GDG.FILE1

DMDNW Command
DMDNW Command
The DMDNW command schedules on-request input and output networks into the
queues.
DMDNW,NW=network
[,DESC=desc]
[,JOB=name]
[,LEADTM={0100|hhmm}]
[,SCHID={1|nnn}]
[,SUBID=subid]
NW
Defines the network to be demanded. Value must be the network name that is used
when the network was defined in the database.
DESC
(Optional) Defines an optional description. This value is displayed on the QM.6,
QM.7, LPRE, and LPOST panels.
JOB
(Optional) Defines a name to assign to the network.
Default: DMD#nnnn, if you do not specify JOB or SUBID (where nnnn is the CA WA
CA 7 Edition number).
LEADTM
(Optional) Defines an elapsed (lead) time for calculating the deadline start
time-of-day of the first station in the network.
Default: 1 hour
Limits: hh= 1 to 2 numeric characters from 0 to 99
mm= 1 to 2 numeric characters from 0 to 59

DMDNW Command
SCHID
(Optional) Defines which schedule ID of the network's scheduling definition is to
use.
Default: 1
SUBID
(Optional) Defines an optional ID to use to identify the network further network
when it enters the queue.
Usage Notes
When a network is requested, CA WA CA 7 Edition determines whether the network
should be placed in the preprocess or postprocess queue based on the definition of the
network in the database.
All networks can be demanded independently from jobs.
Even though networks can be demanded with this command, all networks must have a
schedule.
The DMDNW command must be used, instead of the job DEMAND command for input
networks. It can be used to demand output networks independently of their jobs.
The RUNNW command can be used instead of DMDNW to prevent requirement posting.
Examples
DMDNW,NW=RECPTS
DMDNW,NW=REPTS,SUBID=PAYR1234,DESC=PAYDATA
DMDNW,NW=REPTS,SCHID=270,LEADTM=0125

DMPCAT Command
DMPCAT Command
The DMPCAT command displays the first block of catalog information for a specified
data set. This function is available on the UT Menu panel as FUNCTION value 18 or on
any other menu or formatted panel as FUNCTION value UT.18.
DMPCAT,DSN=dsname[,CVOL=volume]
DSN
Defines the fully qualified name of the data set whose first catalog block is to be
displayed.
CVOL
(Optional) Defines the volume where the catalog search is to begin. If omitted, the
catalog is searched to determine the volume.
Examples
DMPCAT,DSN=CA7.LOADLIB
DMPCAT,DSN=CA7.COMDS,CVOL=LIB103

DMPDSCB Command
DMPDSCB Command
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 as FUNCTION value 13
or on any other menu or formatted panel as FUNCTION value UT.13.
DMPDSCB,DSN=dsname[,VOL=volume]
DSN
Defines the fully qualified name of the data set whose data set control block (DSCB)
is to be displayed.
VOL
(Optional) Defines the volume on which the data set resides. If omitted, the catalog
is searched to determine the volume.
Examples
DMPDSCB,DSN=CA7.LOADLIB,VOL=LIB102
DMPDSCB,DSN=CA7.COMDS
DMPDSN Command
The DMPDSN command displays physical records of a given data set or directory. The
command supports DSORG of PS, DA, or PO and RECFM of F, V, or U. This function is
available on the UT Menu panel as FUNCTION value 17 or on any other menu or
formatted panel as FUNCTION value UT.17.
DMPDSN,DSN=dsname
[,MEM=member]
[,REC={1|nnnn}]
[,VOL=volume]
DSN

DMPDSN Command
MEM
(Optional) Defines a PDS member to display. Specify this name for partitioned data
sets (PDSs) only. If omitted for a PDS, the directory is displayed.
REC
(Optional) Defines a relative physical record to display.
Default: 1 - first record in data set
VOL
(Optional) Defines the volume on which the data set resides. If omitted, the catalog
is searched to determine the volume.
Examples
DMPDSN,DSN=CA7.LOADLIB,MEM=SASSUTLX
DMPDSN,DSN=CA7.COMMDS,VOL=LIB102,REC=3
DMPDSN,DSN=CA7.LOADLIB,REC=5

FALL Command
FALL Command
The FALL command provides forecasting for jobs and network workstations. Only the
database is used for this forecast.
FALL,FROM=(mmddyy,hhmm),{TO=(mmddyy,hhmm)|SPAN=hhhh}
[,DRMODE={YES|NO}]
[,DRCLASS=(class1,...,class8)]
[,JOB={*|jobname|(jobname1,...jobname10)|mask}]
[,JOBNET={*|name|mask}]
[,LIST={ALL|#JOB|CPU|GRPH|JOB|STN|TAPE}]
[,LVL={100|nnn}]
[,MAINID=SYn]
[,NW={*|network|network*}]
[,RINT=hhmm]
[,SCHID={1|nnn}]
[,SEQ={DLDT|DODT|JOB}]
[,STN={*|station|station*|(station1,...station10)}]
[,SYS={*|system|mask}]
[,TRIG={J|D|{JD|DJ}|N}]
[,TYPE={ACTUAL|ALL}]
FROM
Defines the beginning date and time for the forecast time interval. FROM is
required.
TO
Defines the ending date and time for the time interval to be forecast. Either TO or
SPAN is required. If TO is specified, SPAN must be omitted.
SPAN
Defines the length of the time interval to be forecast. This value is added to the
FROM date and time-of-day to determine the ending date and time of the forecast
time interval.
Limits: 1 to 4 numeric characters specified as hhhh where the minimum value is 1
hour and maximum value is 8784 hours
Required: Yes, unless TO is used

FALL Command
LIST
(Optional) Specifies the options for resource forecasting. If you code the LIST
option, you must also specify the RINT option.
ALL
Produces all of the following choices. With this option, TAPE1 displays
separately from TAPE2. ALL is the default.
#JOB
Graphically displays number of jobs running during each time interval specified.
CPU
Graphically displays percent of CPU usage during each time interval specified.
GRPH
Graphically displays number of jobs running, percent of CPU used, and tape
usage during each time interval specified.
JOB
Produces resource forecast report for CPU workload.
STN
Produces resource forecast report for workstation workload.
TAPE
Graphically displays the number of tapes (both TAPE1 and TAPE2) forecasted
for each time interval specified.
SCHID
(Optional) Defines the schedule ID as a value from 1 through 999 to use in the
forecast. Required only if the job being forecasted does not have a schedule.
More information:
Forecast Interval (see page 46)

Common Forecast Parameter Descriptions (see page 39)

FALL Command
Examples
FALL,FROM=(0305yy,0800),TO=(0316,17),TYPE=ALL
FALL,FROM=03,TO=03,SYS=PACKBACK
FALL,FROM=(03,08),SPAN=8,SEQ=JOB
FALL,FROM=(03,08),SPAN=8,JOB=G401*,SYS=ACCTPY,NW=RPTPREP,STN=(PRNT,BURST,DISTR)
FALL,FROM=(1002),SPAN=24,RINT=0100,LIST=GRPH
NOEX in the RQMT column on the output identifies nonexecutable jobs (for example,
EXEC:N on the job definition 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=0306yy,TO=0306yy
FALL DATE 02-27-yy PAGE 0001
FORECAST FOR CA-7 JOBS AND STATIONS
PERIOD : 03-06-yy AT 0000 HRS TO 03-06-yy AT 2359 HRS
JOBS(S) : ALL
SYSTEMS : ALL JOBNET(S) : ALL
STATIONS(S) : ALL
NETWORK(S) : ALL
OPTIONS : JOB-TRIGGERED JOBS INCLUDED

DSN-TRIGGERED JOBS NOT INCLUDED
DETAILED STATION RECORDS PROVIDED
HIGHEST JOB DATE AND TIME : yy065/2359

HIGHEST JOB NAME : PATOM
HIGHEST STATION DATE AND TIME : yy066/0330

HIGHEST STATION NAME : BINS

FALL Command
FALL Panel - Forecast for CA-7 Jobs
FORECAST FOR CA-7 JOBS
START DTTM END DTTM JOB SYS SCHED SID TRIGGERING JOB/DSN RQMT
yy065/0759 yy065/0800 DUCCXX01 TESTNTWK YES 001
yy065/0900 yy065/0900 JCO150D CO YES 001 NOEX
yy065/0090 yy065/0090 JCO620D CO LEV001 001 JCO150D
yy065/1100 yy065/1100 PAT1 CHICAGO YES 002 JCLO
yy065/1200 yy065/1200 JCO150D CO YES 002 NOEX
yy065/1200 yy065/1200 PATM1 YES 001
yy065/1210 yy065/1210 JCO501D CO LEV001 002 JCO150D
yy065/2000 yy065/2000 ALLNET1 DEMO YES 001 JCLO
yy065/2359 yy065/2359 PATOM PAT YES 001
FALL Panel - Forecast for CA-7 Stations
FORECAST FOR CA-7 STATIONS
START DTTM END DTTM STN #/NAME NETWORK SUBID SCHED SID CONNJOB/S
yy065/0900 yy065/1100 1 BURST TESTONWK RPT1205 YES 001 DUCCXX01:005
yy065/1200 yy065/1300 2 TRIM TESTONWK RPT1205 YES 001 DUCCXX01:001
yy065/1500 yy065/1530 3 BINS TESTONWK RPT1205 YES 001 DUCCXX01:001
yy065/1900 yy065/1930 3 BINS TESTONWK RPT1205 YES 001
yy065/2000 yy065/2100 2 TRIM TESTONWK RPT1205 YES 001
yy065/2100 yy065/2300 1 BURST TESTONWK RPT1205 YES 001
yy066/0000 yy066/0100 2 TRIM TESTONWK RPT1205 YES 001

FIND Command
FIND Command
The FIND command searches DASD volumes for copies of a given data set name. Volume
serial number and creation date are displayed for each DASD volume on which the data
set is found. This function is available on the UT Menu panel as FUNCTION value 10 or
on any other menu or formatted panel as FUNCTION value UT.10.
FIND,DSN=dsname,VOL={ALL|volume|(volume,...)}
DSN
VOL
Defines the volumes to search.
ALL
Specifies all volumes available to CA WA CA 7 Edition. SPACE,VOL=ALL can be
used to determine which volumes are available to CA WA CA 7 Edition by way
of:
■ //U7nnnnnn DD statements in the JCL
■ Function 11 on the Utilities Menu panel
■ Top line ALLOC command
volume
Defines a single volume.
(volume,...,volume)
Defines up to five volumes enclosed in parentheses and separated by commas.
Examples
FIND,DSN=SYSCTLG,VOL=ALL
FIND,DSN=USER.FILE1,VOL=(VOLM01,VOLM02,VOLM03)
FIND,DSN=USER.FILE2,VOL=VOLM02
CA WA CA 7 Edition displays the volser and creation date for each DASD volume where
the data set is found.

FJOB Command
FJOB Command
The FJOB command provides forecasting for jobs. The command includes an option to
include output workstation networks in the forecast. Only the database is used for this
forecast.
FJOB,FROM=(mmddyy,hhmm),{TO=(mmddyy,hhmm)|SPAN=hhhh}
[,DRMODE={YES|NO}]
[,{JOB={*|jobname|(jobname1,...jobname10)|mask}|JOBL={*|longjobname|mask}}]
[,LIST={ALL|#JOB|CPU|GRPH|JOB|TAPE|W|WP|WPS|WS}]
[,LVL={100|nnn}]
[,MAINID=SYn]
[,NWOPT={N|S}]
[,RINT=hhmm]
[,SCHID={0|nnn}]
[,SEG=(segment,subsegment)]
FROM
Defines the beginning date and time for the time interval to be forecast. FROM is
required.
TO
SPAN
time interval.
Limits: 1 to 4 numeric characters that are specified as hhhh where the minimum
value is 1 hour and maximum value is 8784 hours.
Required: Yes, unless TO is used.

FJOB Command
LIST
(Optional) Specifies the options for either resource forecasting or the worksheet. If
you code LIST for resource forecasting, also specify the RINT option.
ALL
#JOB
Graphically displays the number of jobs running during each time interval
specified.
CPU
Graphically displays the percent of CPU usage during each time interval
specified.
GRPH
Graphically displays the number of jobs running, percent of CPU used and tape
JOB
Produces a resource forecast report for the CPU workload.
TAPE
For worksheet requests, RINT and NWOPT must be omitted and LIST can have
one of the following values:
W
Produces a schedule worksheet, without prose from the forecast report.
WP
Produces prose information with the specified forecast worksheet.
WPS
Produces the same information as WP except skips to the top of the page
for each job.
WS
Produces the same information as W except skips to the top of the page
for each job.

FJOB Command
More information:

Usage Notes
You can forecast jobs without RESOLVed schedules by requesting the individual job. The
FROM date and time are used as the start time for the job unless omitted, in which case
current date and time are used.
Examples
FJOB,FROM=(0305yy,0800),TO=(0316,17)
FJOB,FROM=02,TO=03,SYS=PAYROLL,TRIG=DJ
FJOB,FROM=03,SPAN=24,SEQ=JOB,JOB=G401*
FJOB,FROM=(03,08),SPAN=8,JOB=(JOB1,JOB2,JOB3)
FJOB,FROM=0302,SPAN=24
FJOB,FROM=02,SPAN=24
FJOB,FROM=(yy15,0800),SPAN=48,SYS=PAYROLL,RINT=0030,LIST=CPU
FJOB,FROM=(0314,1030),SPAN=24,LIST=WPS,TYPE=ALL
EXEC:N on the job definition panel). These jobs have both the start and end times set to
the DOTM of the job.
JCLO in the RQMT column on the output identifies jobs that require JCL overrides (for
Jobs for which the NXTCYC,SET=OFF or NXTCYC,SET=SKP command has been 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 Command
FJOB Panel - Forecast for CA-7 Jobs (Summary)
Jobs with repeat information scheduled to run during the forecast period are marked
with "(REPEATING JOB)" in the TRIGGERING JOB/DSN column. Subsequent iterations of
these jobs are treated as if they were triggered by the previous iteration but will have a
RPT (repeat) number instead of a LEV (level) number in the SCHED column.
FJOB,FROM=0306yy,TO=0306yy
FJOB DATE mm-dd-yy PAGE 0001
PERIOD : mm-dd-yy AT 0000 HRS TO mm-dd-yy AT 2359 HRS
JOB(S) : ALL

CONNECTED OUTPUT NETWORKS NOT INCLUDED

HIGHEST JOB NAME : DUCCXX01
FJOB,FROM=0306yy,TO=0306yy
yy065/1600 yy065/1600 DUCCXX02 TESTNTWK YES 001 NOEX
yy065/1959 yy065/2000 DUCCXX03 TESTNTWK YES 001 JCLO

FJOB Command
FJOB Panel - Forecast for CA-7 Jobs and Stations (Summary)
FJOB,FROM=0306yy,TO=0306yy,NWOPT=S
FORECAST FOR CA-7 JOBS AND STATIONS
JOB(S) : ALL
STATION(S) : ALL
NETWORK(S) : ALL


HIGHEST JOB NAME : DUCCXX01

HIGHEST STATION NAME : TESTONWK
FJOB Panel - Forecast for CA-7 Stations
FJOB,FROM=0306yy,TO=0306yy,NWOPT=S
START DTTM END DTTM STN #/NAME NETWORK SUBID SCHED SID CONNJOB/SID
yy065/0900 yy065/1530 1 PRINT TESTONWK RPT1205 YES 001 DUCCXX01:001
yy065/1700 yy065/2330 3 DELIVER TESTONWK RPT1205 YES 001 DUCCXX01:003
yy065/2100 yy066/0330 4 MAIL TESTONWK RPT1205 YES 001 DUCCXX01:004
SFC1-00 REQUEST COMPLETED AT 18:11:23 on yy.058

FJOB Command
FJOB Panel - Worksheet
FJOB,FROM=0306yy,TO=0306yy,LIST=WP
DATE mm-dd-yy PAGE 0002
JOB=DUCCXX01 COMPLETED _________________
SCHEDULE: LATEST STRT=yyddd/0759

DUEOUT TIME=yyddd/0800 SCHED ID=001
SUBMIT TIME=yyddd/0000

NBRRUN=007 LSTRUN=yyddd/1607

ELAPTM=0001 TP1 =00 TP2 =00

RETJCL=NO HOLD=NO
******** 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=0330yy,TO=0330yy,TRIG=J,JOB=WHIDO95*,TYPE=ALL
yy089/1107 yy089/1200 WHIDO953 YES 001 OFF

yy089/1108 yy089/1200 WHIDO952 YES 001 SKP
yy089/1109 yy089/1200 WHIDO951 YES 001 NOEX
yy090/1107 yy090/1200 *WHIDO531 LEV001 001 WHIDO953 OFF
yy090/1108 yy090/1200 *WHIDO521 LEV001 001 WHIDO952 SKP?
yy090/1109 yy090/1200 *WHIDO511 LEV001 001 WHIDO951 NOEX
An asterisk (*) in front of a job name indicates the START DTTM has been adjusted to
allow for triggered due-out time conflicts. This usually indicates multiple jobs in a trigger
stream have the same DOTM value.
For jobs flagged with NXTCYC,SET=OFF or NXTCYC,SET=SKP the RQMT field shows SKP?
or OFF. These jobs appear only when TYPE=ALL is requested. The ? indicates that the job
may be skipped.

FLOWD Command
FLOWD Command
The FLOWD command manually deletes active Critical Path Management (CPM) flow
elements. FLOWD cannot be used with the option CPM=JFMLOAD.
Note: For information about the CPM facility, see the Interface Reference Guide.
FLOWD,FLOW=flowname
[,DATE=yyddd]
[,JOBCNT=0]
[,TIME=hhmm]
FLOW
Defines the fully qualified name of the CPM flow to be deleted. To delete all active
flows, specify *ALL*. If there are multiple occurrences of the flow active, all of them
will be deleted unless the DATE and TIME keywords are used to qualify the
selection.
DATE
(Optional) Defines a specific flow date. If the same flow has multiple occurrences,
you can use the DATE (and optionally TIME) keywords to select which flows to
delete. The value is matched against the flow start date (available using the FLOWL
command).
Limits: 5 numeric digits (yyddd)
JOBCNT
(Optional) If used, the only valid form of this option is JOBCNT=0.
Specifies to delete only flows that no longer have any jobs attached to them. These
flows can become stranded if a job in the critical path of the flow is canceled in CA
WA CA 7 Edition.
Limits: 0
TIME
Defines a specific flow time. If the same flow has multiple occurrences of the same
flow, you can use the DATE (and optionally TIME) keywords to select which flows to
delete. The value is matched against the flow start time (available using the FLOWL
command).
Limits: 4 numeric digits (hhmm)

FLOWL Command
More information:
FLOWL Command (see page 225)
Usage Notes
Note: For information about the Critical Path Monitor (CPM) facility, see the Interface
Reference Guide.
Use the FLOWL command to display active flows.
If a flow is deleted by the FLOWD command, no signal is sent to CA OPS/MVS EMA. You
may need to manually delete the flow there as well.
To delete all stranded CPM flows (flows with no jobs attached), issue the command:
FLOWD,FLOW=*ALL*,JOBCNT=0
FLOWL Command
The FLOWL command displays information about active Critical Path Management
(CPM) flows. FLOWL cannot be used with the option CPM=JFMLOAD.
Note: For information about the CPM facility, see the Interface Reference Guide.
FLOWL[,FLOW={*|flowname|flowname*}][,LIST={FLOW|JOBS}]
FLOW
(Optional) Defines the fully or partially qualified flow name for which to display
information.
Default: * (all flows)

FLOWL Command
LIST
(Optional) Specifies the amount of flow information to display.
FLOW
Specifies to display a single line of information for each active flow selected.
FLOW is the default.
JOBS
Specifies to display a line of information for each active flow that is selected
and also lists the CA 7 job numbers of the jobs that are currently connected to
each flow.
Examples
FLOWL,LIST=JOBS
PAGE 0001
FLOWNAME START-DATE/TIME START-JOB/SID/NUM END-JOB/SID SLA-TARGET JOBCNT
FLOWA yy098/10:19:33 JOBA /001/0001 JOBX /001 yy098/23:30 1

-------------------------- CONNECTED JOBS ---------------------
0003
SLIL-00 REQUEST COMPLETED AT hh:mm:ss ON yy.ddd
FLOWNAME
Identifies the name of the active flow.
START-DATE/TIME
Identifies the date (yyddd) and time (hh:mm:ss) when the active flow element was
created.
START-JOB/SID/NUM
Identifies the job name, schedule ID, and CA 7 job number of the job that caused
the creation of the active flow element.
END-JOB/SID
Identifies the job name and schedule ID of the job that is considered the end of the
critical path that the flow represents.
SLA-TARGET
Identifies the target completion date and time for the flow (Service Level
Agreement target).

FPOST Command
JOBCNT
Identifies the number of CA WA CA 7 Edition jobs that are currently connected to
this flow.
CONNECTED JOBS
Identifies the job numbers of the CA WA CA 7 Edition jobs that are currently
connected to this flow (only displayed if LIST=JOBS).
FPOST Command
The FPOST command provides forecasting for output network workstations. Only the
FPOST,FROM=(mmddyy,hhmm),{TO=(mmddyy,hhmm)|SPAN=hhhh}
[,RINT=hhmm]
[,SEQ={DLDT|DODT|STN}]
FROM
required.
TO
SPAN
time interval.

FPOST Command
Examples
FPOST,FROM=(0305yy,0800),TO=(0316,17)
FPOST,FROM=03,TO=03,STN=KEYPUNCH
FPOST,FROM=(03,17),SPAN=8,NW=RPT,STN=(BURST,DISTR)
FPOST,FROM=02,SPAN=24,RINT=0045
FPOST Panel - Forecast for CA-7 Stations (Output Networks - Summary)
FPOST,FROM=0306yy,TO=0306yy
FPOST DATE 03-06-yy PAGE 0001
STATIONS(S) : ALL
NETWORK(S) : ALL


FPOST Panel - Forecast for CA-7 Stations (Output Networks)
FPOST,FROM=0306yy,TO=0306yy
FPOST DATE 02-27-yy PAGE 0001


FPRE Command
FPRE Command
The FPRE command provides forecasting for input network workstations. Only the
FPRE,FROM=(mmddyy,hhmm),{TO=(mmddyy,hhmm)|SPAN=hhhh}
[,RINT=hhmm]
FROM
required.
TO
SPAN
time interval.
More information:

Examples
FPRE,FROM=(0305yy,0800),TO=(0316,17)
FPRE,FROM=03,TO=03,STN=KEYPUNCH
FPRE,FROM=(03,17),SPAN=24,NW=DATAPREP,SEQ=STN
FPRE,FROM=(03,0800),SPAN=8,STN=(KEYPUNCH,VERIFY)
FPRE,FROM=(yy15,0800),SPAN=8,RINT=0200,

FPRE Command
FPRE Panel - Preprocessing (Summary)
FPRE,FROM=0306yy,TO=0306yy,SPAN=12
FPRE DATE 02-27-yy PAGE 0001

STATION(S) : ALL
NETWORK(S) : ALL
OPTIONS : NEITHER JOB- NOR DSN-TRIGGERED JOBS INCLUDED

HIGHEST STATION DATE AND TIME : *NONE*

HIGHEST STATION NAME : *NONE*
Note: This panel is not the summary for the next panel.
FPRE Panel - Preprocessing
FPRE,FROM=0306yy,TO=0306yy,SPAN=12
FPRE DATE 03-01-yy PAGE 0002

yy065/0600 yy065/0630 1 INPUTLOG TIMECARD PAY001-D YES 001
yy065/0630 yy065/0645 2 KEYENTRY TIMECARD PAY001-D YES 001
yy065/0645 yy065/0700 1 INPUTLOG SHIPPING WHS020-D YES 003
yy065/0700 yy065/0715 1 INPUTLOG APPROVAL ACP001-W YES 001
yy065/0715 yy065/0730 2 KEYENTRY SHIPPING WHS010-D YES 003
yy065/0715 yy065/0730 3 VERIFY TIMECARD PAY001-D YES 001
yy065/0730 yy065/0745 3 VERIFY SHIPPING WHS020-D YES 003
yy065/0745 yy065/0800 2 KEYENTRY APPROVAL ACP001-W YES 001
yy065/0800 yy065/0815 4 LOGOUT TIMECARD PAY001-D YES 001
yy065/0815 yy065/0830 3 VERIFY APPROVAL ACP001-W YES 001
yy065/0815 yy065/0830 4 LOGOUT SHIPPING WHS020-D YES 003
yy065/0830 yy065/0845 4 LOGOUT APPROVAL ACP001-W YES 001
yy065/0845 yy065/0900 5 TRANSMIT TIMECARD PAY001-D YES 001
yy065/0900 yy065/0915 5 TRANSMIT SHIPPING WHS010-D YES 003

FQALL Command
FQALL Command
The FQALL command provides forecasting for both jobs and workstation networks. It
includes work in the request, ready, active, preprocess, and postprocess queues.
FQALL[,{TO=(mmddyy,hhmm)|SPAN=hhhh}]
[,DRMODE={YES|NO}]
[,LVL={100|nnn}]
[,MAINID=SYn]
[,RINT=hhmm]
TO
Defines the ending date and time for the time interval to be forecast. If TO is
specified, SPAN must be omitted. If neither is specified, only work in the queues is
considered.
SPAN
current date and time-of-day to determine the ending date and time of the forecast
time interval.
LIST
(Optional) Specifies the options for resource forecasting. If you code the LIST
option, you must also specify the RINT option.
ALL
#JOB

FQALL Command
CPU
GRPH
Graphically displays number of jobs running, percent of CPU used and tape
JOB
STN
TAPE
More information:

Examples
FQALL
FQALL,SPAN=8
FQALL,TO=1021
FQALL,JOB=G401*,SYS=ACC*,NW=RPT*,STN=(PRNT,BURST,DISTR)
FQALL,RINT=0100,LIST=STN,SPAN=4
FQALL Panel - Jobs
with "(REPEATING JOB)" in the TRIGGERING JOB/DSN column. Subsequent iterations of
these jobs are treated as if the previous iteration triggered them but have a RPT (repeat)
number instead of a LEV (level) number in the SCHED column.

FQALL Command
FQALL,SPAN=24
FQALL DATE 05-07-yy PAGE 0002
FORECAST FOR CA-7 JOBS (INCLUDING THOSE IN CURRENT QUEUES)

yy128/1610 yy128/1610 DUSARS02 PAYABLES RDY-Q 001
yy128/1610 yy128/1610 DUSARS03 PAYABLES RDY-Q 001
yy128/1610 yy128/1610 DUSAXX01 AUDITORS REQ-Q 001
yy128/1610 yy128/1610 DUSAXX03 BILLING REQ-Q 001
yy128/1611 yy128/1611 DUSAZZ01 SHIPPING REQ-Q 001 NOEX
yy128/1621 yy128/1721 DUSAZZ12 SHIPPING LEV001 001 DUSAZZ01
yy128/1710 yy128/1711 DUSAXX05 BILLING LEV001 001 DUSAXX03
yy128/1711 yy128/1091 DUSAZZ13 SHIPPING LEV001 001 DUSAZZ01 JCLO
yy128/2011 yy128/2101 DUSAZZ23 SHIPPING LEV002 001 DUSAZZ13 JCLO
An * before the job name in the FQALL output indicates a date/time adjustment. The
following are some of the situations that can cause an adjustment in the FQALL
date/time output:
■ Jobs in the active queue where the start time is greater than the deadline time (as
seen with the LQ command).
The FQALL output shows the job marked with an asterisk. This situation is typically
seen where XPJOBs have time zone differences. That is, the CA WA CA 7 Edition
instance runs on a machine on Central Standard time, but the agent executing the
job is on Eastern Standard time.
■ Jobs in the ready queue and jobs in the request queue that have not completed
normally (as seen with the LQ command).
If the deadline date/time is less than the current date/time, the FQALL output
shows the job marked with an asterisk.
■ Completed jobs still in the request queue.
If the end time is greater than the due-out time (for example, the job is late), the
job is marked with an asterisk.
■ Jobs that are triggered.
If the due-out time for the triggered job is less than the due-out time of the
triggering job, a date/time adjustment is made. The job is marked with an asterisk.

FQJOB Command
FQALL Panel - Stations
FQALL
FQALL DATE 05-07-yy PAGE 002
FORECAST FOR CA-7 JOBS AND STATIONS (INCLUDING THOSE IN CURRENT QUEUES)
yy127/1519 yy127/1521 1 TRIGST01 TRIGINNW HEMANT PRE-Q 001
yy127/1519 yy127/1531 1 KEYPUNCH LAMBINWK TEST PRE-Q 001
yy127/1711 yy128/0611 1 HTERM2 TESTNET1 TESTSID0 POST-Q 001 DUSAZZ01
yy128/0800 yy128/0900 1 HTERM1 TEST0TNW RPT1205 POST-Q 001 DUSAXX01
yy128/0800 yy128/0900 2 LHTERM1 TESTNET1 TESTSIDO POST-Q 001 DUSAZZ01
yy128/0900 yy128/1000 3 DATACNTL TESTNET1 TESTSIDO POST-Q 001 DUSAZZ01
yy128/1000 yy128/1100 4 HTERM1 TESTNET1 TESTSIDO POST-Q 001 DUSAZZ01
yy128/1100 yy128/1200 5 HTERM2 TESTNET1 TESTSIDO POST-Q 001 DUSAZZ01
yy128/1300 yy128/1400 7 DATACNTL TESTNET1 TESTSIDO POST-Q 001 DUSAZZ01
yy128/1711 yy128/1721 2 TRIGSTO2 TRIGINNW HEMANT PRE-Q 001
yy129/0600 yy129/0700 2 HTERM2 TESTOTNW RPT1205 POST-Q 001 DUSAXX01
yy129/1200 yy129/1300 3 HTERM1 TESTOTNW RPT1205 POST-Q 001 DUSAXX01
FQJOB Command
The FQJOB command provides forecasting by job name including those jobs in the
request, ready, and active queues.
FQJOB[,{TO=(mmddyy,hhmm)|SPAN=hhhh}]
[,DRMODE={YES|NO}]
[,LIST={ALL|#JOB|CPU|GRPH|JOB|TAPE|W|WP|WPS|WS}]
[,LVL={100|nnn}]
[,MAINID=SYn]
[,NWOPT={N|S}]
[,RINT=hhmm]
[,SEG=(segment,subsegment)]

FQJOB Command
TO
specified, SPAN must be omitted. If neither is specified, selection is based on only
those jobs in the queues.
SPAN
time interval.
Limits: 1 to 4 numeric characters that are specified as hhhh where the minimum
value is 1 hour and maximum value is 8784 hours.
Required: Yes, unless TO is used.
LIST
Specifies the options for resource forecasting. If you code the LIST option, also
specify the RINT option.
ALL
#JOB
Graphically displays the number of jobs running during each time interval
specified.
CPU
Graphically displays the percent of the CPU usage during each time interval
specified.
GRPH
Graphically displays the number of jobs running, percent of CPU used and tape
JOB
Produces a resource forecast report for the CPU workload.

FQJOB Command
TAPE
For worksheet requests, RINT must be omitted and LIST can have one of the
following values:
W
Produces a schedule worksheet, without prose from the forecast report.
WP
Produces prose information with the specified forecast worksheet.
WPS
Produces the same information as WP except skips to the top of the page for
each job.
WS
Produces the same information as W except skips to the top of the page for
each job.
More information:


FQJOB Command
Examples
FQJOB,TO=(0603yy)
FQJOB,SPAN=8
FQJOB,SPAN=24,SYS=INVENTRY
FQJOB,RINT=0010
FQJOB,TO=(0630yy,1600),RINT=0100,LIST=GRPH
FQJOB Panel - Jobs Including Queues
with "(REPEATING JOB)" in the TRIGGERING JOB/DSN column. The subsequent iterations
of these jobs are treated as if the previous iteration triggered them but have an RPT
(repeat) number instead of a LEV (level) number in the SCHED column.
FQJOB,SPAN=24
FQJOB DATE 05-07-yy PAGE 0002
FORECAST FOR CA-7 JOBS (INCLUDING THOSE IN CURRENT QUEUES)

yy127/1610 yy127/1610 ACRAA01W RECEVABL RDY-Q 001
yy127/1610 yy127/1610 ACRAA02W RECEVABL RDY-Q 001
yy127/1610 yy127/1610 ACPED01W PAYABLES REQ-Q 001
yy127/1610 yy127/1610 CNPAC01M PAYROLL REQ-Q 001 NOEX
yy127/1611 yy127/1611 WHSAB01D SHIPPING REQ-Q 001 JCLO
yy127/1621 yy127/1721 WHSAC01D SHIPPING LEV001 001 WHSAB01D
yy127/1621 yy128/0314 WHSAD01D SHIPPING LEV001 001 WHSAB01D
yy127/1710 yy127/1711 CNPAD01M PAYROLL LEV001 001 CNPAC01M
yy127/1711 yy127/1051 WHSAE01D SHIPPING LEV002 001 WHSAD01D JCLO
yy127/1821 yy127/1721 WHSAF01D SHIPPING LEV003 001 WHSAE01D
yy127/2011 yy127/2101 WHSAG01D SHIPPING LEV004 001 WHSAF01D JCLO
yy128/0414 yy128/1414 WHSAH01D SHIPPING LEV005 001 WHSAG01D
An * before the job name in the FQJOB output indicates a date/time adjustment. The
following are some of the situations that can cause an adjustment in the FQJOB
date/time output:
■ Jobs in the active queue where the start time is greater than the deadline time (as
seen with the LQ command).

FQPOST Command
The FQJOB output shows the job marked with an asterisk. This situation is typically
seen where XPJOBs have time zone differences. That is, the CA WA CA 7 Edition
instance runs on a machine on Central Standard time, but the agent executing the
job is on Eastern Standard time.
■ Jobs in the ready queue and jobs in the request queue that have not completed
normally (as seen with the LQ command).
If the deadline date/time is less than the current date/time, the FQJOB output
shows the job marked with an asterisk.
■ Completed jobs still in the request queue.
If the end time is greater than the due-out time (for example, the job is late), the
job is marked with an asterisk.
■ Jobs that are triggered.
If the due-out time for the triggered job is less than the due-out time of the
triggering job, a date/time adjustment is made. The job is marked with an asterisk.
FQPOST Command
The FQPOST command provides forecasting for output network workstation activity
including the postprocess queue.
FQPOST[,{TO=(mmddyy,hhmm)|SPAN=hhhh}]
[,RINT=hhmm]
TO
specified, omit SPAN.
SPAN
time interval.

FQPRE Command
More information:

Examples
FQPOST,TO=(0603yy)
FQPOST,SPAN=8
FQPOST,TO=(1121yy,1700)
FQPOST,SPAN=8,NW=RPT
FQPOST Panel - Output Networks Including Queues
FQPOST,SPAN=10
FQPOST DATE 05-07-yy PAGE 0001
FORECAST FOR CA-7 STATIONS (INCLUDING THOSE IN CURRENT QUEUES)

yy128/0800 yy128/0900 1 PRINTERS BILLING MONTHLY POST-Q 001 CHGBL01M
yy128/0800 yy128/0900 2 QUALITY BENEFITS PER004-A POST-Q 001 PERAC01A
yy128/0900 yy128/1000 3 DECOLLAT BENEFITS PER004-A POST-Q 001 PERAC01A
yy128/1000 yy128/1100 4 BURSTING BENEFITS PER004-A POST-Q 001 PERAC01A
yy128/1100 yy128/1200 5 MICRFILM BENEFITS PER004-A POST-Q 001 PERAC01A
yy128/1300 yy128/1400 7 COPIES BENEFITS PER004-A POST-Q 001 PERAC01A
yy128/1500 yy128/1600 9 DELIVERY BENEFITS PER004-A POST-Q 001 PERAC01A
yy129/0600 yy129/0700 2 DECOLLAT BILLING MONTHLY POST-Q 001 CHGBL01M
yy129/1200 yy129/1300 3 DELIVERY BILLING MONTHLY POST-Q 001 CHGBL01M
FQPRE Command
The FQPRE command provides forecasting for input network workstations including the
preprocess queue.
FQPRE[,{TO=(mmddyy,hhmm)|SPAN=hhhh}]
[,RINT=hhmm]

FQPRE Command
TO
specified, SPAN must be omitted.
SPAN
time interval.
More information:

Examples
FQPRE,TO=(0210yy,0800)
FQPRE,SPAN=8
FQPRE,TO=(0617,1700),STN=KEYPUNCH
FQPRE,SPAN=24
FQPRE DATE 05-07-yy PAGE 0002

yy128/1511 yy128/1521 1 CONSOLE SYSTSAVE KEYSTATS PRE-Q 001
yy128/1521 yy128/1531 1 CONSOLE ENGINEER WEEKLY PRE-Q 001
yy128/1711 yy128/1721 2 PRINTER SYSTSAVE KEYSTATS PRE-Q 001

FQRES Command
FQRES Command
The FQRES command provides forecasting, including the queues, for the following
resources:
■ Job 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,INT=hhmm,{TO=(mmddyy,hhmm)|SPAN=hhhh}
[,DRMODE={YES|NO}]
[,LVL={100|nnn}]
TO
specified, SPAN must be omitted. Both are optional. If neither is specified, the
selection is based on the queues only, and current date and time are assumed.
mmddyy
Defines the date. Optional.
mm
Defines the month (01 through 12). If TO is specified, mm is required.
Leading zero is required.
dd
Defines the day (01 through 31). Optional. If omitted and TO is specified,
last day of month is assumed.
yy
Defines the year. Optional. If TO is specified and yy is omitted, the current
year is assumed.

FQRES Command
hhmm
Defines the time. Optional. If TO is specified and hhmm omitted, 2359 is
assumed.
hh
mm
SPAN
time interval.
LIST
(Optional) Specifies the options for resource forecasting.
ALL
Produces all of the following choices.
#JOB
CPU
GRPH
JOB
STN
TAPE
Graphically displays total number of tapes during each time interval specified.
More information:

FQSTN Command
Examples
FQRES,INT=0010,TO=06
FQRES,SPAN=8,INT=0015,LIST=JOB
FQRES,SPAN=720,INT=2400,LIST=CPU
FQRES,INT=0010,JOB=PAYR*,TO=06
The panels produced by the FQRES command are identical to those produced by the
FRES command.
More information:
FRES Command (see page 247)
FQSTN Command
The FQSTN command provides forecasting for input and output network workstations
including the preprocess and postprocess queues.
FQSTN[,{TO=(mmddyy,hhmm)|SPAN=hhhh}]
[,RINT=hhmm]
TO
specified, SPAN must be omitted. If neither is specified, selection is based on only
those workstations in the preprocess or postprocess queues.
SPAN
time interval.

FQSTN Command
More information:

Examples
FQSTN
FQSTN,SPAN=8
FQSTN,STN=KEYPUNCH
FQSTN,TO=(0630yy,1700),RINT=0200
FQSTN,NW=RPT,STN=(BURST,DISTR)
FQSTN Panel - Stations Including Queues
FQSTN
FQSTN DATE 05-07-yy PAGE 0002

yy127/1519 yy127/1521 1 CONSOLE SYSTSAVE KEYSTATS PRE-Q 001 DMD#0006
yy127/1519 yy127/1531 1 CONSOLE ENGINEER WEEKLY PRE-Q 001 DND#0007
yy127/1711 yy128/0611 1 PRINTERS BENEFITS PER004-A POST-Q 001 PERAC01A
yy128/0800 yy128/0900 1 PRINTERS BILLING MONTHLY POST-Q 001 CHGBL01M
yy128/0900 yy128/1000 3 DECOLLAT BENEFITS PER004-A POST-Q 001 PERAC01A
yy128/1000 yy128/1100 4 BURSTING BENEFITS PER004-A POST-Q 001 PERAC01A
yy128/1100 yy128/1200 5 MICRFILM BENEFITS PER004-A POST-Q 001 PERAC01A
yy128/1300 yy128/1400 7 COPIES BENEFITS PER004-A POST-Q 001 PERAC01A
yy128/1500 yy128/1600 9 DELIVERY BENEFITS PER004-A POST-Q 001 PERAC01A
yy128/1711 yy128/1721 2 PRINTER SYSTSAVE KEYSTATS PRE-Q 001 DMD#0006
yy129/0600 yy129/0700 2 DECOLLAT BILLING MONTHLY POST-Q 001 CHGBL01M
yy129/1200 yy129/1300 3 DELIVERY BILLING MONTHLY POST-Q 001 CHGBL01M

FQTAPE Command
FQTAPE Command
The FQTAPE command provides a tape pull list for CPU jobs including those in the CA
WA CA 7 Edition queues.
FQTAPE[,{TO=(mmddyy,hhmm)|SPAN=hhhh}]
[,DRMODE={YES|NO}]
TO
specified, SPAN must be omitted. If neither is specified, selection is from the queues
only and current date and time are assumed.
mmddyy
Defines the date.
mm
Defines the month (01 through 12). Required. Leading zero is required.
dd
Defines the day (01 through 31). Optional. If omitted, current day is
assumed. Leading zero is required.
yy
Defines the year. Optional. If omitted, the current year is assumed.
hhmm
Defines the time. Optional. If omitted, current time is assumed.
hh
mm

FQTAPE Command
SPAN
time interval.
More information:
Examples
FQTAPE
FQTAPE,SPAN=24
FQTAPE,SPAN=8,JOB=GL*,TRIG=JD
FQTAPE Panel - Tapes Including Queues
FQTAPE
FQTAPE DATE 05-07-yy PAGE 0002
TAPE PULL LIST FOR CA-7 JOBS (INCLUDING THOSE IN CURRENT QUEUES)
VOLSER -------------- DATASET NAME -------------- CREATED-ON DEV-CODE SEQ

JOBNAME SYSTEM START DTTM END DTTM SCHED SID TRIGGERING JOB/DSN
123456 CA-7.TAPE yy242/1041 34008003 001

DUSAZZ23 TESTGFRC yy128/2011 yy128/2101 LEV002 001 DUSAZZ13
987650 CA-7.TTAPE yy242/1041 34008003 001

SCRATCH ... APPROXIMATELY 00004 TAPES REQUIRED FOR OUTPUT DATASETS.

FRES Command
FRES Command
The FRES command provides forecasting, from the database only, for the following
resources:
■ Job workload
– Individual job resources
– Number of jobs running 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,FROM=(mmddyy,hhmm),INT=hhmm,{TO=(mmddyy,hhmm)|SPAN=hhhh}
[,DRMODE={YES|NO}]
[,LIST=list]
[,LVL={100|nnn}]
[,SCHID={0|nnn}]

FRES Command
FROM
required.
mmddyy
Defines the date.
mm
dd
Defines the day (01 through 31). Optional. If omitted, 01 is assumed.
yy
Defines the year. Optional. If omitted, current year is assumed.
hhmm
Defines the time. Optional. If omitted, 0000 is assumed.
hh
mm
TO
Defines the ending date and time for the time interval to be forecast. TO is optional.
If TO is specified, SPAN must be omitted. Either TO or SPAN must be specified.
mmddyy
Defines the date.
mm
dd
Defines the day (01 through 31). Optional. If omitted, last day of month is
yy

FRES Command
hhmm
hh
mm
SPAN
time interval.
LIST
(Optional) Specifies the options for resource forecasting.
ALL
Produces all of the following choices. ALL is the default.
#JOB
CPU
GRPH
JOB
STN
TAPE
Graphically displays total number of tapes during each time interval specified.
More information:

FRES Command
Examples
FRES,FROM=(0305yy,0800),TO=(0316,17),INT=0030
FRES,FROM=03,SPAN=24,SYS=GLACTG,INT=0100
FRES,FROM=11,TO=21,INT=2400,LIST=CPU
FRES Panel - Resource Forecast for CA-7 Jobs
FRES,FROM=(0306,0700),SPAN=4,JOB=DUSAZZ01,INT=0100
FRES DATE 02-27-yy PAGE 0002
RESOURCE FORECAST FOR CA-7 JOBS
TIME INTERVAL #JOBS JOB SID CL %CPU CORE TP1 TP2

065/0700-0800 DUSAZZ01 001 A 0000.222 00040K 001 000
065/0700-0800 ***001 0000.222 00040K 001 000
065/0800-0900 DUSAZZ11 001 A 0000.078 09999K 001 001

DUSAZZ12 001 H 0000.392 01000K 002 000
065/0800-0900 ***002 0000.470 10999K 003 001
065/0900-1000 DUSAZZ11 001 A 0000.094 09999K 000 002

DUSAZZ12 001 H 0000.080 01000K 001 000
DUSAZZ13 001 Z 0000.486 08888K 003 001
065/0900-1000 ***003 0000.660 19887K 004 003
065/1000-1100 DUSAZZ11 001 A 0000.094 09999K 000 002

DUSAZZ13 001 Z 0000.486 08888K 001 000
DUSAZZ22 001 Z 0000.417 08888K 004 000
065/1000-1100 ***003 0000.997 27775K 005 002
FRES Panel - Resource Forecast for CA-7 Jobs - Number of Jobs
FRES,INT=0100,FROM=(0508yy,1600),TO=(0509yy,0500)
TIME INTERVAL NUMBER OF JOBS #JOBS %CPU #TAPE

1 1 2 2 3 3 4
0....5....0....5....0....5....0....5....0
128/1600-1700 ******** 007 002.210% 038
128/1700-1800 ***** 004 000.609% 015
128/1800-1900 **** 003 000.907% 011
128/1900-2000 **** 003 000.684% 016
128/2000-2100 **** 003 008.523% 014
128/2100-2200 **** 003 000.790% 010
128/2200-2300 *** 002 000.597% 017
128/2300-2400 *** 002 000.597% 021
128/2400-0100 *** 002 000.597% 019
129/0100-0200 *** 002 000.597% 014
129/0200-0300 *** 002 000.597% 009
129/0300-0400 *** 002 000.525% 016
129/0400-0500 *** 002 000.704% 022

FRES Command
FRES Panel - Resource Forecast for CA-7 Jobs - Percent of CPU Utilization
FRES,INT=0100,FROM=(0508yy,1600),TO=(0509yy,0500)
TIME INTERVAL PER CENT CPU UTILIZATION %CPU #JOBS #TAPES

1 2 3 4 5 6 7 8 9 1
0..0..0..0..0..0..0..0..0..0..00
128/1600-1700 ** 002.210% 07 038
128/1700-1800 * 000.609% 04 015
128/1800-1900 * 000.907% 03 011
128/1900-2000 * 000.684% 03 016
128/2000-2100 **** 008.523% 03 014
128/2100-2200 * 000.790% 03 010
128/2200-2300 * 000.597% 02 017
128/2300-2400 * 000.597% 02 021
128/2400-0100 * 000.597% 02 019
129/0100-0200 * 000.597% 02 014
129/0200-0300 * 000.597% 02 009
129/0300-0400 * 000.525% 02 016
129/0400-0500 * 000.704% 02 022
FRES Panel - Resource Forecast for CA-7 Jobs - Number of TAPE1
FRES,FROM=0306yy,TO=0306yy,INT=0100
TIME INTERVAL NUMBER OF TAPE1 #TAPES #JOBS %CPU

1 2 3 4 5 6 7 8
0...0...0...0...0...0...0...0...0
065/0700-0800 **************** 038 007 002.210%
065/0800-0900 ******* 015 004 000.609%
065/0900-1000 ****** 011 003 000.907%
065/1000-1100 ******* 016 003 000.684%
065/1100-1200 ****** 014 003 008.523%
065/1200-1300 ***** 010 003 000.790%
065/1300-1400 ******** 017 002 000.597%
065/1400-1500 ********** 021 002 000.597%
065/1500-1600 ******** 019 002 000.597%
065/1600-1700 ****** 014 002 000.597%
065/1700-1800 **** 009 002 000.597%
065/1800-1900 ******* 016 002 000.525%
065/1900-2000 ********* 022 002 000.704%

FRJOB Command
FRES Panel - Resource Forecast for CA-7 Jobs - Number of TAPE2
TIME INTERVAL NUMBER OF TAPE2 #TAPES #JOBS %CPU

1 2 3 4 5 6 7 8
0....0....0....0....0....0....0....0....0
065/0700-0800 ******************* 038 007 002.210%
065/0800-0900 ******** 015 004 000.609%
065/0900-1000 ******* 011 003 000.907%
065/1000-1100 ********* 016 003 000.684%
065/1100-1200 ******** 014 003 008.523%
065/1200-1300 ****** 010 003 000.790%
065/1300-1400 ********* 017 002 000.597%
065/1400-1500 *********** 021 002 000.597%
065/1500-1600 ********** 019 002 000.597%
065/1600-1700 ********* 014 002 000.597%
065/1700-1800 ***** 009 002 000.597%
065/1800-1900 ********* 016 002 000.525%
065/1900-2000 ************ 022 002 000.704%
FRES Panel - Resource Forecast for CA-7 Stations (Summary)
RESOURCE FORECAST FOR CA-7 STATIONS
TIME INTERVAL #STNS STATION NETWORK SUBID

065/0100-0200 BALANCE ACCT0001 PAYMENTS
DECOLLAT ACCT0001 PAYMENTS
LOGDESK ACCT0001 PAYMENTS
DELIVERY ACCT0001 PAYMENTS
065/0100-0200 *** 004
FRJOB Command
The FRJOB command answers the question, "How does this job get into the system?"
The command presents a reverse job flow (reverse trigger flow) based on information in
the database. The purpose is to identify how the target job can be brought into the
active scheduling system. It tracks backward through triggers from the target job to one
or more header jobs. A header job is one that has one or more defined date/time
schedules, or, that has no job/data set/network triggers defined. That is, a job, network,
or data set that starts the trigger flow that eventually results in the target job being
brought into the active scheduling system. FRJOB uses only information in the database.

FRJOB Command
FRJOB,{JOB={jobname|(jobname1,...jobname10)}|JOBL=longjobname}
[,DRMODE={YES|NO}]
[,LIST={ALL|HDRS|LAST}]
[,LVL={100|nnn}]
[,SCHID={0|nnn}]
JOB
Defines the specific jobs from which the reverse flows are started. The value can be
one specific job name or a substring of 1 to 10 specific job names. JOB and JOBL are
mutually exclusive.
JOBL
Defines the specific jobs from which the reverse flows are started. The value can
only be one specific long job name. JOB and JOBL are mutually exclusive.
SCHID
(Optional) Defines the schedule ID of the starting jobs (JOB=) used to start the
reverse flow. The value can be from 0 through 999. The default is 0, which means
the next level contains elements that can cause ANY schedule ID of the starting job
to be triggered/scheduled.
LIST
(Optional) Specifies the option of listing the entire structure or only the first and last
jobs.
ALL
Lists the entire structure. ALL is the default.
HDRS
Lists only those elements that are identified as headers and the starting job.
LAST
Lists only the first and last elements.
More information:

FRJOB Command
Examples
FRJOB,JOB=PAY0090,SCHID=1
FRJOB,JOB=AR#0030,SCHID=0,LIST=LAST
FRJOB,JOB=ORD0088,LVL=10
Usage Notes
The FRJOB command is useful when you are creating or modifying the schedules and
triggers for a workload flow. If you need to determine all of the paths that schedules,
triggers, or both can take to result in a given job being run, FRJOB can be most helpful.
For example, your operations staff informs you that a second copy of job PAY0090 is
being brought into the system whenever the PAYROLL application is run, even though it
had already run earlier in the cycle. You can use FRJOB to determine not only the
possible triggers for PAY0090, but also the path of control that leads up to each of those
triggers. With this information you can more easily diagnose the problem, and also
check the results after you have made changes to the structure.
The FRJOB display does not include any dates or times for elements in the structure.
This is because the flow is being generated backwards through logical control paths.
Also, the display can include jobs with a schedule ID of zero (000) that indicates it
represents any occurrence of the job rather than a specific occurrence of the job. Once
you have determined the origin points for the target job you can use one of the other
forecasting commands to retrace a particular control path from the origin point to the
target job with dates and times provided.
FRJOB,JOB=BBD07
FRJOB DATE 04-01-yy PAGE 0001
REVERSE STRUCTURE FOR CA-7 JOBS
JOB(S) : BBD07
SYSTEM(S) : ALL JOBNET(S) : ALL
OPTIONS : BOTH JOB- AND DSN-TRIGGERED JOBS INCLUDED

HEADER JOB/NETWORK NAME : BBD06I AND OTHERS

FRJOB Command
The forecasting summary page for FRJOB follows the general format of all forecasting
commands with the following exceptions:
HEADER JOB/NETWORK NAME
This field shows the name of the first (or only) origination point (header) for the
control flow that eventually results in the target job.
AND OTHERS
If there are multiple possible origin points in the reverse job flow, this area contains
the text AND OTHERS. If there is only one origination point (header) for the flow,
this area is blank.
FRJOB,JOB=BBD07
FRJOB DATE 04-01-yy PAGE 0001
REVERSE STRUCTURE FOR CA-7 JOBS
HDR LEV# JOB NAME SYSTEM SID TYPE TRIGGERS /DSNBR /SCHEDULED
--- BBD07 ............ 000
**** -001 BBD06I .......... 001 INWK BBD07 :**SCHD**
-001 BBD06 .......... 006 JOB BBD07
-002 BBD05 ........ 005 JOB BBD06
**** -003 BBD04B ...... 005 DSET BBD05 :DS00000058
-003 BBD04 ...... 004 JOB BBD05
-004 BBD03 .... 003 JOB BBD04
-005 BBD02 .. 002 JOB BBD03
**** -006 BBD01 BBDSYS 001 JOB BBD02 :**SCHD**

HDR
Header Indicator. Displays asterisks (*) if the element on that line is considered a
header (origination point). Otherwise, it is blank.
LEV#
Level. Identifies the logical level of the element on that line. The starting point
(target job) is at level zero, which is represented by three hyphens (---). The
elements that can trigger the target job have a level of negative one (-001). The
elements that can trigger the negative one level have a level of negative two (-002),
and so forth.

FRJOB Command
JOB NAME
Identifies the name of the job or network that triggers an element on the next
higher level. The name is offset to the right for each level up to the sixth level
(-006). This makes it easier to see what level a given element is on. Elements that
are six or more levels deep all appear starting at the same column as the sixth level.
SYSTEM
Identifies the application system name of the job on this line.
SID
Schedule ID. Identifies the schedule ID of the job or network on this line. A generic
schedule ID of zero (000) can appear in the flow. Such an entry represents ANY
occurrence of the job or network.
TYPE
Type of element. Identifies a literal that describes the type of element and trigger
the line represents.
The following are the possible values:
JOB
Indicates the element in the Job Name field is a job that triggers the job in the
Triggers field through a job trigger.
DSET
Indicates the element in the Job Name field is a job that updates or creates a
data set (DSNBR field) that triggers the job in the Triggers field through a data
set trigger.
INWK
Indicates the element in the Job Name field is an input network that triggers
the job in the Triggers field through a network trigger.
TRIGGERS
Identifies the name of the job on the next higher level that this element triggers.
For example, the last line of the preceding example means that job BBD01 (level
-006) triggers job BBD02 on the next higher level (level -005).
DSNBR
Data Set Number. Identifies the CA WA CA 7 Edition data set number of the data set
created or updated by the job shown in the Job Name that causes a data set trigger
to bring in the job shown in Triggers. The DSNBR is only displayed if a data set
trigger is involved, otherwise it is blank.
SCHEDULED
Schedule Indicator. Identifies the literal **SCHD** if the element on this line has
one or more date/time schedules defined to CA WA CA 7 Edition. Otherwise it is
blank.

FRQJOB Command
FRQJOB Command
The FRQJOB command is useful to answer the question, "How does this job get into the
system today?" The command presents a reverse job flow (reverse trigger flow) based
on information in the database. The command also examines the status queues
(request, ready, and active) for the presence of each job in the structure as it is being
built.
The purpose is to identify how the target job is brought into the active scheduling
system taking into account jobs that are already in the queues. The process tracks
backward through triggers from the target job to one or more header jobs. A header job
is defined as one of the following types:
■ One that is already in the request, ready, or active queue.
■ One that has one or more defined date/time schedules.
■ One that has no job/data set/network triggers defined.
The difference between the FRQJOB command and FRJOB is that a check is made in the
status queues for each job present in the structure. If it is found in one of the queues,
that job is considered a header job even though it may have been triggered by
something else. This process identifies the shortest possible control path that results in
the execution of the target job.
FRJOB,{JOB={jobname|(jobname1,...jobname10)}|JOBL=longjobname}
[,DRMODE={YES|NO}]
[,LIST={ALL|HDRS|LAST}]
[,LVL={100|nnn}]
[,SCHID={0|nnn}]
JOB
Defines the specific jobs from which the reverse flows are started. The value can be
one specific job name, or a substring of 1 to 10 specific job names. JOB and JOBL are
mutually exclusive.
JOBL
Defines the specific jobs from which the reverse flows are started. The value can
only be one specific long job name. JOB and JOBL are mutually exclusive.

FRQJOB Command
SCHID
(Optional) Defines the schedule ID of the starting jobs (JOB=) used to start the
reverse flow. It can be a value from 0 through 999. The default is 0, which means
the next level contains elements that can cause ANY schedule ID of the starting job
to be triggered/scheduled.
LIST
(Optional) Specifies the option of listing the entire structure or the first and last
jobs.
ALL
Specifies to list the entire structure. ALL is the default.
HDRS
Specifies to list that only those elements that are identified as headers and the
starting job.
LAST
Specifies to list only the first and last elements.
More information:
Examples
FRQJOB,JOB=PAY0090,SCHID=1
FRQJOB,JOB=AR#0030,SCHID=0,LIST=LAST
FRQJOB,JOB=ORD0088,LVL=10
Usage Notes
The FRQJOB command is useful when you are trying to determine how a job is going to
get into the scheduling system in the near future. You would first use the FRQJOB
command to see if there is anything currently in the queues that eventually results in
triggering of the target job.
For example, a vice president of your company calls and asks if job XYZ is going to run
before the end of the day. You issue an FRQJOB command for XYZ and learn that job X is
currently in the request queue, and it triggers job Y that in turn triggers job XYZ. You can
then issue an FQJOB command for job X that gives you an estimate of the time that job
XYZ executes. Without the FRQJOB command, you would have had to manually analyze
the situation with a series of LJOB,LIST=TRIG and LQ commands.

FRQJOB Command
The FRQJOB display does not include any dates or times for elements in the structure.
This is because the flow is being generated backwards through logical control paths.
Also, the display can include jobs with a schedule ID of zero (000) that indicates it
represents any occurrence of the job rather than a specific occurrence of the job. Once
you have determined the origin points for the target job, you can use one of the other
forecasting commands to retrace a particular control path from the origin point to the
target job with dates and times provided.
FRQJOB,JOB=FLOW4H
FRQJOB DATE 03-20-yy PAGE 0001
REVERSE STRUCTURE FOR CA-7 JOBS (INCLUDING QUEUES)
JOB(S) : FLOW4H
SYSTEM(S) : ALL JOBNET(S) : ALL
OPTIONS : BOTH JOB- AND DSN-TRIGGERED JOBS INCLUDED

HEADER JOB/NETWORK NAME : FLOW1A (0842)
The forecasting summary page for FRQJOB follows the general format of all forecasting
commands with the following exceptions:
FLOW1A… (in the sample)
This field shows the name of the first (or only) origination point (header) for the
control flow that eventually results in the target job. If the job is currently in one of
the status queues the CA 7 job number is displayed also (0842).
(blank space right of (0842))
If multiple possible origin points are in the reverse job flow, this area contains the
text AND OTHERS. If the flow has only one origination point (header), this area is
blank.
FRQJOB,JOB=FLOW4H
FRQJOB DATE 03-20-yy PAGE 0001
REVERSE STRUCTURE FOR CA-7 JOBS (INCLUDING QUEUES)
HDR LEV# JOB NAME SYSTEM SID TYPE TRIGGERS /DSNBR /SCHEDULED
--- FLOW4H ............ FLOWSYS 000
-001 FLOW3D .......... FLOWSYS 001 JOB FLOW4H
-002 FLOW2C ........ FLOWSYS 000 DSET FLOW3D :DS00000040
0842 -003 FLOW1A ...... FLOWSYS 001 JOB FLOW2C

FRQJOB Command

HDR
Header Indicator. Displays nonblanks if the element on that line is considered a
header (origination point). If the header job currently resides in the request, ready,
or active queue, the field contains the four-digit CA 7 job number. If the header job
does not currently reside in queues, the field contains asterisks.
LEV#
Level. Identifies the logical level of the element on that line. The starting point
(target job) is at level zero, which is represented by three hyphens (---). The
elements that can trigger the target job have a level of negative one (-001). The
elements that can trigger the negative one level have a level of negative two (-002),
and so forth.
JOB NAME
Identifies the name of the job or network that triggers an element on the next
higher level. The name is offset to the right for each level up to the sixth level
(-006). This makes it easier to see what level a given element is on. Elements that
are six or more levels deep all appear starting at the same column as the sixth level.
SYSTEM
System Name. Identifies the application system name of the job on this line.
SID
Schedule ID. Identifies the schedule ID of the job or network on this line. A generic
schedule ID of zero (000) can appear in the flow. Such an entry represents ANY
occurrence of the job or network.
TYPE
Type of element. Identifies a literal that describes the type of element and trigger
the line represents.
JOB
Indicates the element in the Job Name field is a job that triggers the job in the
Triggers field through a job trigger.
DSET
Indicates the element in the Job Name field is a job that updates or creates a
data set (DSNBR field) that triggers the job in the Triggers field through a data
set trigger.
INWK
Indicates the element in the Job Name field is an input network that triggers
the job in the Triggers field through a network trigger.

FSTN Command
TRIGGERS
Identifies the name of the job on the next higher level that this element triggers.
For example, the last line of the preceding example means that job FLOW1A (level
-003) triggers job FLOW2C on the next higher level (level -002).
DSNBR
Data Set Number. Identifies the CA WA CA 7 Edition data set number of the data set
created or updated by the job shown in the Job Name, which causes a data set
trigger to bring in the job shown in Triggers. The DSNBR is only displayed if a data
set trigger is involved; otherwise, it is blank.
SCHEDULED
Schedule Indicator. Identifies the literal **SCHD** if the element on this line has
one or more date/time schedules defined to CA WA CA 7 Edition. Otherwise it is
blank.
FSTN Command
The FSTN command provides forecasting of output and input network workstations.
Only the database is used for this forecast.
FSTN,FROM=(mmddyy,hhmm),{TO=(mmddyy,hhmm)|SPAN=hhhh}
[,RINT=hhmm]
FROM
required.
TO
SPAN must be specified. If TO is used, SPAN must be omitted.
SPAN
time interval.

FSTN Command
More information:

Examples
FSTN,FROM=(0305yy,0800),TO=(0316,17)
FSTN,FROM=03,TO=03,STN=KEYPUNCH
FSTN,FROM=(03,17),SPAN=8,NW=RPT,STN=(BURST,DISTR)
FSTN,FROM=02,SPAN=24,RINT=0045
FSTN Panel - Forecast for CA-7 Stations (Summary)
FSTN,FROM=0306yy,TO=0306yy
FSTN DATE 02-27-yy PAGE 0001

STATIONS(S) : ALL
NETWORK(S) : ALL



FSTRUC Command
FSTN Panel - Forecast for CA-7 Stations
FSTN,FROM=0306yy,TO=0306yy
FSTN DATE 02-27-yy PAGE 0002

FSTRUC Command
The FSTRUC command produces a report displaying an entire job flow structure with the
starting and ending times. The principal emphasis is on the job flow structure and the
elapsed time of each job. The start time of the first job can be any arbitrary time. Only
the database is used for this forecast.
FSTRUC[,DRMODE={YES|NO}]
[,FROM=(mmddyy,hhmm)]
[,LIST={ALL|LAST}]
[,LVL={100|nnn}]
[,SCHID={1|nnn}]
[,TRIG={J|D{JD|DJ}}]

FSTRUC Command
FROM
(Optional) Defines the beginning date and time for the time interval to be forecast.
Default: The current date and time
mmddyy
Defines the date.
mm
Defines the month (01 through 12). The leading zeros are required.
dd
Defines the day (01 through 31). A leading zero is required if less than 10.
yy
Defines the year.
hhmm
Defines the time.
hh
mm
LIST
(Optional) Specifies the option of listing the entire structure of the jobs or the first
and last jobs.
ALL
Lists the whole structure of the job. ALL is the default.
LAST
Lists only the first and last jobs.
More information:

FTAPE Command
Examples
FSTRUC,FROM=01,SYS=PAYROLL,LIST=LAST
FSTRUC,FROM=03,JOB=G401*,SCHID=2
Note: When using a generic job name, only those jobs meeting the criteria entered and
also having a schedule (or not triggered) are included.
FSTRUC Panel
FSTRUC,FROM=0518yy
FSTRUC DATE 05-15-yy PAGE 0002
NETWORK STRUCTURE FOR CA-7 JOBS

START TIME : 05-18-yy AT 1528 HRS
LEV# JOB NAME SYS START DTTM END DTTM TRIGGERING JOB/DSN/SID
--- T2LIB111............ SYSTBKUP yy260/1528 yy260/1548 :001
001 T2TSOPAK.......... SYSTBKUP yy261/0343 yy261/0400 T2LIB111 :001
002 T2SYSTEM........ SYSTBKUP yy261/0340 yy261/0400 T2TSOPAK :001
003 T2LIB114...... SYSTBKUP yy261/0340 yy261/0400 T2SYSTEM :001
004 T2CATLG2.... SYSTBKUP yy261/0334 yy261/0400 T2LIB114 :001
005 T2LIB115.. SYSTBKUP yy261/0340 yy261/0400 T2CATLG2 :001
006 T2LIB119 SYSTBKUP yy261/0342 yy261/0400 T2LIB115 :001
001 T2LIB118.......... SYSTBKUP yy262/0340 yy262/0400 T2LIB112 :001
002 T2LIB113........ SYSTBKUP yy262/0345 yy262/0400 T2LIB118 :001
003 T2TMSBK1...... SYSTBKUP yy262/0350 yy262/0400 T2LIB113 :001
004 ROBDAILY.... SYSTBKUP yy262/0233 yy262/0400 T2TMSBK1 :001
001 T2LIB116.......... SYSTBKUP yy262/0341 yy262/0400 T2LIB117 :001
--- T2MVSPG2............ SYSTBKUP yy262/1528 yy262/1552 :001
FTAPE Command
The FTAPE command provides a tape pull list for CPU jobs. Only the database is used for
this forecast.
FTAPE,FROM=(mmddyy,hhmm),{TO=(mmddyy,hhmm)|SPAN=hhhh}
[,DRMODE={YES|NO}]
[,SCHID={0|nnn}]
[,TRIG={J|D{JD|DJ}|N}]

FTAPE Command
FROM
required.
mmddyy
Defines the date.
mm
dd
Defines the day (01 through 31). Optional. If omitted, 01 is assumed.
yy
hhmm
hh
mm

FTAPE Command
TO
SPAN is required. If TO is omitted, SPAN must be specified.
mmddyy
Defines the date.
mm
dd
Defines the day (01 through 31). Optional. If omitted, last day of month is
yy
hhmm
hh
mm
SPAN
time interval.
More information:

FTAPE Command
Examples
FTAPE,FROM=02,TO=(0202,1700)
FTAPE,FROM=(0705yy,0800),SPAN=48,SYS=PAYROLL
FTAPE,FROM=05,SPAN=72,TRIG=JD
FTAPE Panel - Magnetic Tape Requirements
FTAPE,FROM=(0306,0000),SPAN=8
FTAPE DATE 02-27-yy PAGE 0002
TAPE PULL LIST FOR CA-7 JOBS
VOLSER ------------- DATASET NAME -------------- CREATED-ON DEV-CODE SEQ

JOBNAME SYSTEM START DTTM END DTTM SCHED SID TRIGGERING JOB/DSN
071049 CA-7.LOGHIST.G0239V00 00000/0000 32008003 001

DUSARS01 SYSTEMA yy065/2400 yy066/0100 YES 001
074684 CA-7.LOGARCH.G0004V00 00000/0000 32008003 001

DUSARS01 SYSTEMA yy065/2400 yy066/0100 YES 001
123456 CA-7.TAPE yy242/1041 34008003 001

987650 CA-7.TTAPE yy242/1041 34008003 001

SCRATCH ... APPROXIMATELY 00012 TAPES REQUIRED FOR OUTPUT DATASETS.

FWLP Command
FWLP Command
The FWLP command selects information from the database and queues for use as input
for the CA WA CA 7 Edition WLP simulator and PROJECTION reports. This input supplies
all critical information about the resource configurations and jobs scheduled for a
specified time frame. The file created by FWLP consists of card-image, fixed format
records to facilitate additions, deletions, and updates for possible resource and job
specification changes through a standard text editor (CA WA CA 7 Edition, TSO, CA
Roscoe, and so on).
FWLP[,DRMODE={YES|NO}]
[,FROM=(mmddyy,hhmm)]
[,TO=(mmddyy,hhmm)]
[,DDNAME={NONE|ddname}]
[,DEMAND={00|nn}]
[,MAINID={ALL|SYn|/SYn}]
[,{RESA|RESP}={*|UCC7Rxxx}]
[,SCHID={0|nnn}]
[,SPAN={8|hhhh}]
[,TRIG={J|N}]
[,TYPE= {ACTUAL|ALL}]
FROM=(mmddyy,hhmm)
(Optional) Defines the beginning date and time for the time frame to be generated
for the simulation. FROM is optional. If omitted, the default is current date and
time, and all current jobs are generated, including jobs currently in the request,
ready, and active queues. If the current date but not the current time is to be used,
the format can be specified as (,hhmm). If FROM is specified, the queue information
is not included.
TO=(mmddyy,hhmm)
(Optional) Defines the ending date and time for the time frame to be generated. TO
is optional. If omitted, SPAN data is added to FROM data to calculate TO. The FWLP
notes contain more information. If the current date but not the current time is to
be used, the format can be specified as (,hhmm).

FWLP Command
DDNAME
(Optional) Specifies the ddname in the CA WA CA 7 Edition execution JCL that
defines the data set that contains the data cards written as a result of the FWLP
command.
NONE
Specifies no data is to be written to a WLP data set. In this case, only the online
portion of WLP is executed and only a Workload Planning Summary report is
generated. NONE is the default.
ddname
Defines the ddname to which WLP information is written. (This name must
correspond to a DD statement in the CA WA CA 7 Edition online execution JCL.
It points to the same data set that is referenced as input by the batch
simulation execution of WLP. It must not reference a U7xxxxxx DD statement
that is used to allocate a volume.)
DEMAND
(Optional) Defines the percentage of DEMAND work to be generated. This causes
dummy job data to be generated on the output file (specified by DDNAME). Each
dummy JOB statement has attributes representing average values of the actual JOB
data statements created. The due-out times of these dummy jobs are spaced at
equal intervals throughout the specified time frame. DEMAND is optional. If
omitted, the default is 0. The value can be derived from APA averages (see Job
category graphs 20, 900, 1240, and so forth).
JOB
(Optional) Defines the jobs to be selected for simulation.
*
Specifies all jobs are to be considered. This value is the default.
jobname
Defines the job names to be considered for simulation. Job name may be
specific or generic.
(jobname1,jobname2,...,jobname10)
Defines a list of job names. Up to 10 specific job names can be specified.
mask
Defines a job name mask.

FWLP Command
JOBNET
Defines the job network field as the selection criteria for the jobs to be forecast.
*
Specifies all names. This value is the default.
name
Defines a specific name.
mask
Defines a JOBNET mask.
Note: If value contains blank, comma, or quote, it may not be possible to specify
the value through batch input.
MAINID
Specifies the CPU as selection criteria for the jobs to be included in the WLP input
data. If jobs input to the simulation impose CPU restrictions as specified by MAINID,
these jobs are included or excluded as indicated. MAINID is optional, but if used,
one of the following is required.
ALL
Specifies MAINID is to be disregarded as a basis for job selection. ALL is the
default.
SYn
Defines the CPU where n is the CA WA CA 7 Edition system number.
/SYn
Specifies not this CPU.
Note: The MAINID keyword is ignored for cross-platform jobs.

FWLP Command
RESA
(Optional) Specifies the initial resource picture module name to be used. Using
RESA instead of RESP causes FWLP to produce a resource (RES) data statement each
time it encounters scheduled changes in the WLB processing objectives criteria in
the specified time frame. (The A indicates ascending.)
*
Specifies that the initial resource picture for the simulation process is the one
currently in use within CA WA CA 7 Edition. This value is the default.
UCC7Rxxx
Specifies a CA WA CA 7 Edition WLB processing objectives definition module,
that exists on the Load library, to be referenced by a WLP batch execution. (See
Workload Balancing and Performance Management in the Systems
Programming Guide.) This module is loaded during batch simulation processing
to supply resource specifications. This module overrides the current module on
the first RES statement that is generated.
RESP
(Optional) Specifies one resource picture module name to be used to generate a
RES statement in the data file. If RESP is specified instead of RESA, the module or
default defined here is to be used throughout the simulation process. (The P
indicates permanent.) Values are the same as described for RESA.
SCHID
(Optional) Defines the schedule ID value as the selection criteria for jobs to be
forecast.
Required: Only when job has no defined schedule
SPAN
(Optional) Defines the time interval in hours, with a minimum value of 1 and a
maximum value of 8784 (approximately one year). This value is added to the 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. The FWLP notes contain
more information.
SYS
(Optional) Defines system names as a selection criteria for the jobs to be selected
for simulation.
*
Specifies all systems are to be considered. This value is the default.

FWLP Command
system
Defines a system to be considered for simulation. System can be specific or
generic. If JOB=J*,SYS=S* is specified, only those jobs whose names start with J
and which belong to systems with names starting with S are selected for the
simulation.
mask
Defines a system name mask.
TRIG
(Optional) Specifies whether the WLP simulator input data generated is to include
job-triggered jobs.
J
Specifies job-triggered jobs are to be included. J is the default.
N
Specifies no job-triggered jobs are to be included.
TYPE
(Optional) Specifies whether the "don't schedule before/after" criteria defined on
the job definition panel is to be honored when generating the data statements. The
FWLP notes contain more information.
ACTUAL
Specifies to honor "don't schedule before/after" criteria. ACTUAL is the default.
ALL
Specifies to ignore the "don't schedule before/after" criteria.
FWLP Notes
■ The TYPE parameter is particularly useful in bringing a new system into operation.
Jobs and tentative schedules can be entered into the CA WA CA 7 Edition database,
before they are brought into a production scheduling status, by specifying a "don't
schedule before" value. WLP can then be used to simulate their impact on currently
scheduled jobs by using the TYPE=ALL parameter. When the jobs are ready for
production, they need not be reentered on the database. Rather, the "don't
schedule before" value merely has to be prior to the production date.
■ Depending on the number of accesses to the CA WA CA 7 Edition database and the
requested time span, the FWLP command can affect the performance of CA WA CA
7 Edition. Large time span requests on FWLP should be done at slack time or in
smaller intervals to be concatenated as input to the batch WLP run. (Reference the
FROM, TO, and SPAN fields.)

FWLP Command
FWLP Output
The output resulting from the online FWLP command consists of the following items:
■ Online Workload Planning Summary panel
■ Data Card file
The online Workload Planning Summary report provides a summary of the data that the
FWLP command generates.
Workload Planning Summary Report
FWLP DATE 01-01-yy PAGE 0001
** W O R K L O A D P L A N N I N G S U M M A R Y **
PERIOD . 01-01-yy AT 0000 HRS

01-01-yy AT 0800 HRS
TOT INIT TP1 TP2 CPU

JOB HRS HRS HRS MIN
WLP 0702 0025.10 0000.00 0000.00 0068.10
RESTART ACTIVITY 0001 0000.10 0000.00 0000.00 0000.50
DEMAND ACTIVITY 0000 0000.00 0000.00 0000.00 0000.00
* T O T A L S * 00703 00025.20 00000.00 00000.00 00068.60

PERIOD
Identifies the starting and ending date and time of the time frame that this FWLP
transaction covers.
Identifies summary figures for this FWLP transaction, as follows:
TOT JOB
Identifies the total number of jobs that are scheduled during the timespan.
INIT HRS
Identifies the total hours of initiator time.

GRAPHc Command
TP1 HRS
Identifies the total hours of TYPE1 tape drive usage for the timespan.
TP2 HRS
Identifies the total hours of TYPE2 tape drive usage for the timespan.
CPU MIN
Identifies the total minutes of CPU time that is required for the jobs, taken
from the weighted average that is kept for each job in the CA WA CA 7 Edition
database.
WLP
Identifies summary figures for regularly scheduled jobs for the timespan requested.
RESTART ACTIVITY
Identifies estimated resource requirements calculated from individual job rerun
rate frequencies and average run requirements. These values represent the
statistical average amount of restart activity to be expected. They do not
necessarily represent the amount of restart activity reflected in the batch WLP
Projection reports, however, since batch WLP allows the user to specify alternate
ways of estimating the restart requirements.
DEMAND ACTIVITY
Identifies estimated percent requirements for DEMAND jobs. Values are a
percentage of the total WLP jobs for this FWLP command. The percentage
corresponds with the value of the DEMAND parameter of FWLP.
TOTALS
Identifies summary figures for this FWLP command, including regularly scheduled
jobs, restarts, and demanded jobs.
GRAPHc Command
The GRAPHc line command requests graphs. It is available as an alternative to the APA
Menu and prompt panels of the APA command. The graphs are divided into five
categories. Each category can be invoked independently through use of one of the two
following top line command formats:

GRAPHc Command
Format 1
GRAPHc,ID={nnnn|(nnnn,...)}
[,DIV1=nnnnnnnn]
[,DIV2=nnnnnnnn]
[,FROM=mmddyy]
[,GLINE={PRIM|SCND|CALC}]
[,SCALE=nnnnnnnn]
[,TO=mmddyy]
Format 2
GRAPHc[,LIST={HELP|DETL|ALL}]
c
Specifies the graph category. Use one of the following values:
D
Database statistics
J
Job statistics
N
Network statistics
S
System statistics
ID=nnnn|(nnnn,nnnn,...,nnnn)
Specifies the graphs to display where nnnn is the four-digit graph identification
number as listed in the graph directory. Leading zeros are not required. Up to 10
such numbers can be specified. Each graph identification number must be defined
in the appropriate graph definition table. This parameter is required unless Format
2 is used.
DIV1=nnnnnnn
(Optional) Temporarily overrides the default division factor for the primary counter
of the graph being displayed (seven digits maximum).

GRAPHc Command
DIV2=nnnnnnn
(Optional) Temporarily overrides the default division factor for the secondary
counter of the graph being displayed. This parameter is valid only for comparison
graphs (seven digits maximum).
FROM=mmddyy
(Optional) Defines the beginning date to start displaying statistical data. Value must
not be less than the current date minus two years, nor greater than the current
date. When only the month is entered, the default is the first of the month specified
and the current year. If omitted, the current date is assumed.
GLINE
(Optional) Temporarily overrides the predefined counter used on the graph line.
PRIM
Specifies to use the primary counter.
SCND
Specifies to use the secondary counter (comparison graphs only).
CALC
Specifies to use the calculated value (comparison graphs only).
LIST
(Optional) If specified, must be the only parameter listed. The following are the
possible values:
HELP
Displays the graph directory.
DETL
Displays the values chosen for all parameters used in defining each graph in the
category specified. The examples contain a sample of the LIST=DETL function.
For the available values of these parameters, see Changing Graph Definitions in
the Systems Programming Guide. For a complete listing of the graphs available
through the Automated Performance Analysis (APA) facility, see the Report
Reference Guide
ALL
Displays the current counters of all graphs in the category specified for that
particular moment. Each graph is listed separately with individual totals and
complete totals. The examples contain a partial listing of the LIST=ALL function.

GRAPHc Command
SCALE=nnnnnnn
(Optional) Temporarily overrides the default scale value defined for the graph ID
being displayed. This value contains up to seven digits and does not affect the
actual numbers to be displayed, only the scale numbers and the length of the graph
line.
TO=mmddyy
(Optional) Defines the ending date, in the format mmddyy, to end displaying
statistical data. Value must be greater than or equal to the date specified in FROM
and not greater than the current date. When only the month is entered, the default
is the last day of the month specified and the current year. If omitted, the current
date is assumed.
More information:
APA Command (see page 172)
Examples
LIST=DETL Function
GRAPHS,LIST=DETL
...GRAPH DETAIL DEFINITION SCREEN... PAGE 0001

DESCRIPTION / ID TYPE TOTALS SCALE GRAPH CALCULATION DIV1 DIV2
CA-7 ACTIVE TIME IN MINUTES

0010 SINGLE NO 00030 PRIM RUNNING TOTAL 006000
CA-7 UP TIME VS. OS WAIT TIME IN SECONDS

0020 COMPARISON YES 00002 CALC PERCENTAGE 000100 000100
TOTAL OS WAIT TIME IN MINUTES

NUMBER OF WRITES TO STATISTICS FILE

COMM. TASK WAIT TIME IN MINUTES


GRAPHc Command
LIST=ALL Function
GRAPHS,LIST=ALL
.....CURRENT STATUS - 09/09/yy..... PAGE 0001
0010 CA-7 ACTIVE TIME IN MINUTES 836 836
0020 CA-7 UP TIME VS. OS WAIT TIME IN SECONDS 50186 49847 99.32
0030 TOTAL OS WAIT TIME IN MINUTES 831 831
0040 NUMBER OF WRITES TO STATISTICS FILE 835 835
0050 COMM. TASK WAIT TIME IN MINUTES 826 826
0060 CA-7 UP TIME VS. COMM. TASK ACTIVE TIME IN SE 50186 630 1.25
0070 NUMBER OF LOGONS 4 4
0080 SECURITY EXCEPTIONS 0 0
0090 TERMINAL ERRORS 0 0
Usage Notes
The graph number with the category requests specific reports. To request JOB category
0370, for example, a command is entered in this format:
GRAPHJ,ID=370,FROM=mmddyy
Where mmddyy is the beginning of the time period to report in month, day, and year
format. Current time is the default period ending time for the graph. This method gives
up-to-the-second information.
Up to 10 graphs can be requested with a single command. Whenever multiples are

requested, the graph selection numbers are separated by commas with the entire
sequence of numbers enclosed in parentheses. If current time is not the desired period
ending time, a TO=mmddyy option can be specified.
Example: Display specific System graphs
This example displays System graphs 0010, 0020, 0070, 0130, and 0150 with statistics
captured from 01/01/yy to 01/31/yy.
GRAPHS,ID=(10,20,70,130,150),FROM=0101yy,TO=0131yy
Note: For more information about graph definitions, see the Report Reference Guide.

HELP Command
HELP Command
The HELP facility provides a quick means of obtaining tutorials about the CA WA CA 7
Edition applications and commands.
This facility is informational only with no direct effect on the CA WA CA 7 Edition system
or its operation.
HELP Panel
Online HELP tutorial information is available through the HELP panel.
--------------------------- 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 GRAPHS
2 - QUEUE MAINT 7 - DATA BASE MAINT 12 - PERSONAL SCHED
3 - QUEUE MGMT/POSTING 8 - DATA BASE ANALYZE 13 - VRM MAINT
4 - SYSTEM COMMANDS 9 - SCHED RESOLUTION 14 - ARF
5 - UTILITIES 10 - 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: 00 -- HELP -- yy.137 / 09:51:38

MESSAGE: 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.

HELP Command

FUNCTION
This field is only used to transfer to some other menu or some other formatted
panel function that is only offered on some other menu. To transfer to some other
panel, enter the name of the desired panel.
INDEX
Enter 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 if APPLICATION or
COMMAND are used.
APPLICATION
This field is used to display information about a specific CA WA CA 7 Edition
application.
Numeric value from the list on the panel can be entered or, if already known, the
specific four character application name can be entered.
If used, the remaining fields on the panel are ignored. Leave blank if INDEX or
COMMAND are used.
The display includes:
■ General discussion of the application
■ List of all available commands in the application with a short description of
each command
■ Example of the format of each command
COMMAND
This 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 following fields blank.
The display includes all of the parts that can be individually selected with the
following fields. Use the following fields to display only selected portions of HELP
information. Y in all of them displays the same information as if none of them were
selected.

HOLD Command
FORMAT
Enter Y to display a sample format for the command.
EXAMPLE
Enter Y to display examples of the command.
GENERAL
Enter Y to display a general discussion of the command and its purpose.
DETAIL
Enter 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 the command for
which HELP is needed.
HOLD Command
The HOLD command interrupts the normal scheduling progress by holding the forward
movement of a job. The command can also hold the contents of an entire queue. This
function is available on the QM.1, QM.6, and QM.7 panels with a FILL value of H.
Depending on the timing and whether there are any other predecessor situations, this
process can sometimes be accomplished with the QM.3 panel.
HOLD,{JOB={jobname|jobnumber|refnumber}|JOBL=longjobname|Q={REQ|RDY}}
JOB
Defines the individual job or workstation network to hold. If JOBL or Q is specified,
omit JOB.
Required: Yes (unless the JOBL or Q parameters are used).
jobname
Defines the job name of the job to hold.
jobnumber
Defines the job number of the job to hold.

HOLD Command
refnumber
Defines the value for a workstation network task. Enter the value as the CA WA
CA 7 Edition assigned reference number in the format nnnnrrs.
nnnn
Defines the CA 7 job number.
rr
associated with the job. For input workstation networks, the value is 00.
s
Defines the position of the station within the network. The first station
would be position 1.
JOBL
Defines the individual job to hold. If JOB or Q is specified, omit JOBL.
Required: Yes (unless the JOB or Q parameters are used)
longjobname
Defines the long job name of the job to hold.
Q
Specifies to hold the contents of an entire queue. If JOB or JOBL is specified, omit Q.
Required: Yes (unless the JOB or JOBL parameters are used).
REQ
Specifies to hold all jobs currently in the request queue.
RDY
Specifies 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 with that name
are held. There can be multiple jobs with the same name.
A specific input workstation network can be held in the preprocess queue. All output
workstation networks associated with a specific job name or 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 logged out.

IN Command
A HOLD command issued for an entire queue affects only those jobs in the queue at the
time the command is processed. Jobs entering the queue after the HOLD are not placed
in hold status unless done individually.
Jobs can also be moved into the request queue in HOLD status when the DEMANDH,
RUNH, or LOADH commands are used.
Examples
HOLD,JOB=CA7JOB9
HOLD,JOB=163
HOLD,Q=REQ
HOLD,JOB=0078012
IN Command
The IN command indicates the beginning of a workstation task.
Each workstation task has a unique reference number. CA WA CA 7 Edition generates

this reference number each time the network that is associated with the workstation
enters a CA WA CA 7 Edition queue. This number can be obtained by using the LPRE or
LPOST commands. The number is then used to log in the start of the workstation tasks.
This indicates that the task is in-process and automatically logs the start time for the
task being performed.
This function is available as the LOGIN or FORCE LOGIN options on the QM.6 and QM.7
panels.
IN,REF={nnnnrrs|(nnnnrrs,...)}[,FORCE=YES]

IN Command
REF
Defines the workstation tasks to log in.
nnnnrrs
Defines a single workstation task reference number.
Note: Workstation task reference numbers can be obtained by using an LPRE or
LPOST command.
nnnn
Defines the CA 7 job number. (Leading zeros can be omitted.)
rr
(Leading zeros cannot be omitted.)
s
Defines the relative position of the station within the network. The first
station is position 1.
(nnnnrrs,...,nnnnrrs)
Defines up to ten workstation task reference numbers. Enclose the values in
parentheses.
FORCE
(Optional) Allows the logging in of an output network before completion of the job
to which it is associated. If used, enter the value as shown. FORCE=YES only has
meaning for output networks.
Input Networks
All input network activities are placed in the preprocess queue for control and tracking.
Either of two events can cause the scheduling of workstation activity:
■ The normal, scheduled processing time arrived and schedule scan automatically
placed the network in the preprocess queue, or
■ The input network was manually demanded (using the DMDNW command).
Each workstation task and its associated network are assigned a unique CA WA CA 7
Edition reference number when the network is placed in the preprocess queue. The
unique reference number must be used by each workstation, except the first in the
network, to log the start and completion of work.

IN Command
Workstations within a network must log in and log out in the workstation sequence
defined to CA WA CA 7 Edition. Only one workstation at a time can be logged in for a
given network. A single workstation can be logged in for more than 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 has logged out.
A workstation can be prompted for an activity that has already completed if CA WA CA 7

Edition was not properly notified of the completion. In response to the prompt, LOGIN
and LOGOUT commands should be used to notify CA WA CA 7 Edition of task
completion. You can use the IN command instead of LOGIN. You can use the IO
command to log in and log out with a single command.
If the same station is defined in the network more than once, the LOGIN and LOGOUT
commands should not be used.
More information:
DMDNW Command (see page 208)

IO Command (see page 291)
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 placed in the
postprocess queue.
All output networks connected to the job (through DB.3.4 panel) are assigned the same
CA 7 job number used to identify the job in the request queue. This job number must be
used by each workstation, except the first, to log the start and completion of its activity.
Since multiple output networks can exist 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 defined sequence. 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 same time. Each workstation must log in
before it can log out. A workstation cannot log in until the preceding workstation in the
network has logged out (for that activity).

IN Command
A workstation can be prompted for an activity that has already been completed if CA
WA CA 7 Edition was not properly notified of the completion. LOGIN and LOGOUT
commands should be used in response to the prompt to notify CA WA CA 7 Edition of
task completion. You can use the IN Command Response in place of LOGIN. The IN top
line command is used to indicate the beginning of a workstation task. The IO command
in this section can be used to log in and log out with a single command.
If the same station is defined in a network more than once, LOGIN and LOGOUT should
not be used.
More information:
IN Command Response (see page 287)
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=0001001
REF JOB NETWORK SUBID STATION -------------REMARKS------ -------
0001001 DMD#0001 TESTNET STATION1 DOTM=90089/1532
SPOC-00 REQUEST COMPLETED AT 14:57:57 on YY.DDD.

IN Command
Remarks
Following is a list of possible IN command remarks. Each is described in detail, followed

by the required action to be taken where applicable. 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. If not,
correct and reenter the IN request.
DOTM=*RUSH*
Reason:
The first station has been successfully logged in. The due-out time for the station
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 that station is
printed. yyddd is a variable of five characters representing the due-out date. hhmm the
due-out time-of-day.
Action:
None.
FROM xxx...x,DOTM=*RUSH*
Reason:
The next station has been successfully logged in for work that was last handled by
station xxx...x. The due-out time for the station 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.

IN Command
FROM xxx...x,DOTM=yyddd/hhmm
Reason:
The next station has been successfully logged in for work that was last handled by
station xxx...x. The preceding station and the due-out time for the current station 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 the request.
JOB NOT COMPLETE
Reason:
An attempt was made to log in a postprocess station before the job completed.
Action:
Reenter the IN request after job execution has completed or specify FORCE=YES on the
IN transaction.
PREV STATION NOT COMPLETE
Reason:
An attempt was made to log in a station when the preceding station in the network was
not logged out.
Action:
If the IN request is valid, determine why the previous station is not logged out. If work at
that station is complete, log it out and then reenter the IN request.

IN Command
Q ANALYSIS INCOMPLETE
Reason:
CA WA CA 7 Edition is not finished with a previous activity using the requested
reference number's queue record.
Action:
Wait a few moments then reenter the request. If the message persists, contact the CA
WA CA 7 Edition coordinator in your data center.
REF NUMBER NOT FOUND
Reason:
The requested reference number was not found in the queue. CA WA CA 7 Edition
attempts to fill in the job, network and SUBID information if possible.
Action:
Determine the correct reference number and reenter the IN request.
Examples
This example logs in workstation task 0011011 referenced by CA WA CA 7 Edition job
0011, network sequence 01 and station position 1.
IN,REF=0011011
This example does the same as the preceding example, only omits leading zeros of the
job number.
IN,REF=11011
This example logs in workstation task 0009032 and 0011012.
IN,REF=(9032,11012)
This example logs in workstation task 0011011 even if the job to which it is associated
has not completed.
IN,REF=11011,FORCE=YES

IO Command
IO Command
The IO command can be used in place of and as a combination of the IN and OUT
commands. The IO command results in a simultaneous log in and log out of one or more
workstation tasks. The IO command uses reference numbers to identify each
workstation.
IO,REF={nnnnrrs|(nnnnrrs,...)}[,FORCE=YES]
REF
Defines the workstation tasks to be both logged in and logged out.
nnnnrrs
Defines a single workstation task reference number.
Note: Workstation task reference numbers can be obtained by using an LPRE or
LPOST command.
nnnn
Defines the CA 7 job number (leading zeros can be omitted).
rr
Leading zeros cannot be omitted.
s
Defines the relative position of the station within the network. The first
station is position 1.
Defines up to ten workstation task reference numbers. Must be enclosed in
parentheses.
FORCE
(Optional) Allows the logging of an output network before completion of the job to
which it is associated. If used, enter the value as shown. FORCE=YES only has
meaning for output networks.

IO Command
IO Command Response
CA WA CA 7 Edition responds to each IO command by providing the following
information:
■ Original IO command
■ Network name
■ SUBID
■ Station name
■ Remarks indicating the disposition taken for the IO command
IO Command Response Example
IO,REF=0001001
REF JOB NETWORK SUBID STATION -------------REMARKS------ -------
0001001 DMD#0001 TESTNET STATION1 NETWORK COMPLETE
SPOC-00 REQUEST COMPLETED AT 15:07:30 on YY.DDD.
Remarks
Following is a list of possible IO command remarks in addition to those discussed under

the IN command response. Each is described in detail, followed by the required action
to be taken where applicable. 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.

IO Command
JOB PURGED
Reason:
The last station in the postprocess queue was successfully logged out. All other output
networks for the job are complete. Therefore, job processing is considered to be
complete.
Action:
For information only.
NETWORK COMPLETE
Reason:
The station has been successfully logged out. This was the last station defined in the
network.
Action:
For information only.
SEND TO xxx...x,DLTM=*RUSH*
Reason:
The station has been successfully logged out. The work has been flagged as critical and
should be sent to the next station (xxx...x) as soon as possible. (Not returned for 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 last station in
network.)
Action:
Make sure the work is forwarded to the next station.
More information:
IN Command (see page 284)

JCLOVRD Command
Examples
IO,REF=0011011
IO,REF=(9032,11012)
IO,REF=11011,FORCE=YES
JCLOVRD Command
The JCLOVRD command establishes or satisfies JCL override requirements. This
command is primarily used when the CPU job does not have a permanent JCL override
requirement assigned. The CPU job for which the JCL override is being established (or
satisfied) must be in the request queue.
If you are using CA WA CA 7 Edition to insert IBM WLM scheduling environment

keywords on JOB statements, you can use the JCLOVRD command to suppress or allow
SCHENV= keyword insertion.
This function is available as the J value for FILL FUNCTION on the QM.1 panel. The
function can also be accomplished with the QM.2 and QM.3 panels.
JCLOVRD,JOB=jobnumber,SET={ON|OFF|WLM|NOWLM}
JOB
Defines the CA 7 job number of the job in the request queue for which to establish
or remover the override requirement.

JCLOVRD Command
SET
Specifies to establish or satisfy JCL override requirements. When a job fails with a
JCL error, the JCL override requirement is automatically set to ON when the job
returns to the request queue. The JCL override must be set to OFF before the job
can be submitted again.
ON
Establishes a JCL override requirement for the specified job. The SET=ON
option is used for jobs in the request queue to indicate that an override is
needed before execution is to occur.
OFF
Satisfies a JCL override requirement for the specified job. The SET=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 no longer appears on a
requirements list for the job. When a REPL is done from the QM.5 panel, the
JCL override requirement is automatically set to OFF.
WLM
Sets job to allow insertion of SCHENV= keyword on the JOB statement at
submission time if the scheduling environment insertion feature is activated
and there is a scheduling Environment VRM definition attached to the job (or
SCHENV global default).
NOWLM
Sets job to suppress the insertion of a SCHENV= keyword on the JOB statement
at submission time even if one would normally be associated with the job.
This option can be used if the validation of an associated IBM WLM scheduling
environment has failed causing the job to be requeued (see Browse message
SSM0-42). Setting the NOWLM option will allow the job to be submitted
without SCHENV= keyword insertion.
Note: This option will not suppress user-coded SCHENV= keywords in the JCL.
Such keywords must be manually removed from the QJCL prior to releasing the
job for submission.
Usage Notes
When REPL is done from the QM.5 panel, the JCL override requirement is set to 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) control statements, the QM.5
panel REPL function, and the CA WA CA 7 Edition Editor SAVE command.

JOBSTART Command
Examples
JCLOVRD,JOB=163,SET=ON
JCLOVRD,JOB=163,SET=OFF
JOBSTART Command
The JOBSTART command sends a request to an SAP agent to start a job that was
previously submitted with STARTMODE=N. This command is only valid for BDC_JOB and
SAP_JOB job types that are in the ACT queue.
JOBSTART,JOB=jobnumber,MODE={A|I}
JOB
Specifies the specific CA 7 job number for the agent job needing the STARTMODE
change.
MODE
Specifies the STARTMODE.
A
Releases the job as soon as possible.
I
Releases the job immediately.
Examples
JOBSTART,JOB=1234,MODE=I
JOBSTART,JOB=1234,MODE=A

JRENAME Command
JRENAME Command
The JRENAME command changes the name of a job in all associated database elements.
If changing multiple jobs through a batch terminal interface, we recommend that you do
so during a slow processing period.
JRENAME,oooooooo,NEWJOB=nnnnnnnn[,QCHK=YES|NO][,UPDATE=YES|NO][,LIST=YES|NO]
oooooooo
Specifies the job name to change.
Limits: 1 to 8 characters valid for a job name.
NEWJOB=nnnnnnnn
Specifies the new job name.
Limits: 1 to 8 characters valid for a job name.
QCHK
Specifies whether to check the active workload.
YES
Specifies to check the active workload. If the old job name is found, an error
message is issued. No updates occur. YES is the default.
NO
Specifies do not check the active workload.
UPDATE
Specifies whether to change the database.
YES
Specifies to change the job and all associated database elements to reflect the
new job name. YES is the default.
NO
Specifies do not change the database.
LIST
Specifies whether to create a report of changes.
YES
Specifies to create a report of what was changed. YES is the default.
NO
Specifies do not create the report.

JRENAME Command
Usage Notes
You can enter JRENAME at any time, but we recommend entering it during a low
processing time. Many updates can be performed against the database during this
process.
Assume that the job is active in the queues and a rename occurs. When the job
completes processing, the definition updates are not updated. The definition updates
include last run date and time. The triggered jobs do not come in for processing. Any
process that would look for the JOB that was changed would not find the JOB in the
database.
JRENAME does not scan and change text in prose data.
JRENAME does not change a JCL PDS member. The member name field is not updated.
JRENAME does not change any references to the target job in CA 7 Output Network
definitions (DB.5).
Example
The following example renames OLDJOB1 as OLDJOB2 and updates all associated
database elements:
JRENAME,OLDJOB1,NEWJOB=OLDJOB2,UPDATE=YES

LACT Command
LACT Command
The LACT command provides general status information about jobs in the active queue.
Parameters let you indicate which job or group of jobs is desired, what information to
review, and the sequence of displayed data. The active queue only contains information
about jobs that have started executing. Other commands are also available to display
other types of data for CPU jobs that reside in the active queue.
LACT[,AGENT={*|agent|mask}]
[,CLS=x]
[,CPUID={*|smfid|mask}]
[,DRCLASS={*|@ANY|@NONE|drclass|mask}]
[,DRMODE={*|YES|NO}]
[,{JOB={*|jobname|mask|nnnn}|JOBL={*|longjobname|mask}}]
[,LIST=option]
[,NODE={*|nodename|mask}]
[,SCHID={0|nnn}]
[,SEG={xxxxxxxx|(xxxxxxxx,yyyyyyyy)}]
[,SEQ={NATV|sequence}]
[,ST=option]
[,SYS={*|systemname|mask}]
AGENT
(Optional) Indicates an agent name or mask that an agent name must match before
its information is selected for display.
Default: * (all agent names)
CLS
(Optional) Specifies the CA WA CA 7 Edition Workload Balancing class of jobs to
select. If omitted or CLS=*, all classes are selected for display.
CPUID
(Optional) Defines the CPU ID name or mask that a CPU ID must match before its
information is selected for display. For agent jobs, use AGJ. For XPJOBs use 7XPJ.
Note: The CPU ID is not filled in until CA WA CA 7 Edition has processed a job
initiation record.
Default: * (all CPU IDs)

LACT Command
DRCLASS
(Optional) Defines the disaster recovery class name, a reserved name, or mask that
a disaster recovery class name must match before its information is selected for
display.
Default: * (all disaster recovery class names)
@ANY
Specifies to select jobs with any DRCLASS.
@NONE
Specifies to select jobs with no DRCLASS.
DRMODE
(Optional) Specifies the class of jobs to select.
*
Specifies all jobs. This value is the default.
YES
Specifies to select only jobs that entered the request queue while CA WA CA 7
Edition was in Disaster Recovery mode.
NO
Edition was not in Disaster Recovery mode.
JOB
(Optional) Defines the job number, job name, or mask that a job name must match
before its information is selected for display. JOB and JOBL are mutually exclusive.
Default: * (all jobs)
JOBL
(Optional) Defines the long job name or mask that a long job name must match

LACT Command
LIST
(Optional) Specifies the amount of active queue information to display.
AGJOB
Indicates agent information only.
ALL
Specifies all data that is related to the jobs being displayed.
CPU
Specifies CPU jobs only.
JCL
Specifies JCL information only.
Depending on the security options that are selected for your installation, the
following values are sometimes concealed in the display:
■ JOB statement USER keyword
■ JOB statement GROUP keyword
■ JOB statement PASSWORD keyword
■ //*LOGONID statement
■ //*PASSWORD statement
■ //*JOBFROM statement
JOBL
Indicates long job name information only.
PRM
Indicates internal cross-platform PARMLIB information only.
PROS
Specifies documentation information only.
Q
Specifies job data only.
RQMT
Specifies all requirements information only.
STATUS
Specifies VRM and ARF information only.

LACT Command
XPJOB
Specifies internal cross-platform information only.
When LIST is not specified, a default display consisting of a single description line
for each queue record is listed. However, when the JOB parameter requests a
specific job, the default is LIST=STATUS. VRM and ARF information for the job are
also listed. If SEG is specified, the default is LIST=PROS.
NODE
(Optional) Defines the node name or mask that a node name must match before its
information is selected for display.
Default: * (all node names)
SCHID
(Optional) Defines the schedule ID to select information for.
SEG
(Optional) Defines a segment and subsegment of documentation to be listed. If a
subsegment, use the form (xxxxxxxx,yyyyyyyy). SEG and subsegments are both
optional.
xxxxxxxx
Defines 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 and separated by a comma.
SEQ
(Optional) Specifies the display sequence of the selected information.
NATV
Indicates native sequence (the order in which it is in the queue). NATV is the
default.
AGENT
Indicates agent name sequence.
CA7
Indicates CA 7 job number sequence.

LACT Command
DLTM
Indicates deadline time sequence.
DOTM
Indicates due-out time sequence.
JOB
Indicates job name sequence.
NODE
Indicates node name sequence.
ST
(Optional) Indicates a selection option that is used to determine which jobs are
listed.
ABND
Indicates only the jobs that are in abend status.
ARF
Indicates only jobs that ARF tracks.
ARFH
Indicates only jobs that are in ARF recovery status.
ARFJ
Indicates only ARF recovery jobs (entry mode=ARFJ).
LATE
Indicates late jobs.
REPLY
Indicates only agent jobs that are waiting for a reply to an Intervention
Required message.
SYS
(Optional) Defines the system name or mask that a system name must match
before its information is selected for display.
Default: * (all system names)
More information:

LACT Command
Examples
LACT,SEQ=JOB
LACT,JOB=G401*,SEQ=JOB
LACT
DATE=YY.DDD PAGE 0001
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
CA7BTI01 ACT 0025 203/1245 *NONE* 203/1245 ALL-IPO1 001 DEMD 000
SLIF-00 REQUEST COMPLETED AT 11:59:18 on yy.ddd

JOB NAME
Identifies the name of the job as defined in the database. See NAME field on the job
definition panel.
QUEUE NAME
Identifies the queue where this job record currently resides. Values are REQ for
request queue, RDY for ready queue, and ACT for active queue.
CA-7 NUM
Identifies the CA WA CA 7 Edition assigned job number.
DEADLINE DAY AND TIME
Identifies a calculated time by which this job should be active on the CPU to be
completed by the due-out time.
SUB START DAY AND TIME
For 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 the JCL was
written to the submit data set or internal reader. Until the first SMF step
termination record is received, this field is *NONE* for a job in the active queue.
DUE OUT DAY AND TIME
Identifies the due-out time for this job.
CPU SPEC/RUN
The SPEC value is what CPU this job should be submitted to (see MAINID field on
DB.1 panel). The RUN value is what CPU the job has been submitted to.
For XPJOB jobs this field displays XPJ for SPEC. When the job begins execution, the
RUN field displays 7XPJ.
For agent jobs, this field displays the agent job type for SPEC. When the job begins
execution, the RUN field displays AGJ.

LACT Command
SCH ID
Identifies the schedule ID assigned when this job was brought into the request
queue.
ENTRY MODE
Identifies how the job was brought into the queue. The possible values are the
following:
ARFJ
Identifies a ARF recovery job.
AUTO
Identifies a triggered job.
DEMD
Identifies a demanded job.
EXTL
Identifies a job submitted external to CA WA CA 7 Edition.
LOAD
Identifies a job record to be loaded (brought in by LOAD command).
PS
Identifies a job submitted by Personal Scheduling System.
RPET
Identifies a repeated job.
RUN
Identifies a job brought in by the RUN command.
SSCN
Identifies a job record brought in by schedule scan.
XDEM
Identifies a job brought in by the DEMAND command from an XPS client.
XPS
Identifies a job brought in from an XPS client using the RUN command with the
REF option.
XRUN
Identifies a job brought in from an XPS client using the RUN command.
Note: If ARF detects an exception condition for the job, the last character of this
field has an asterisk as in the following: DEM*

LACT Command
MSTR REQ
Identifies the number of outstanding master requirements for a job record.
JOB STATUS
Identifies the job's current disposition. Values and their meanings are:
A-Snnn
Indicates the job has failed with a system abend.
A-Unnnn
Indicates the job has failed with a user abend.
C-Cnnnn
Indicates the job has completed successfully and is going through completion
processing.
LATE
Indicates the job has not either started by the DEADLINE DAY/TIME or has not
completed by its DUE-OUT DAY/TIME.
R-#nnnn
Indicates the job has failed a condition code test made at the step level.
R-Cnnnn
Indicates the job has failed a condition code test made at the job level.
R-JCLERR
If the job is in the request queue with this status, then there was either a
runtime JCL error (for example, data set not found) or an IEFUJV exit canceled
the job. If the job is in the ready queue with this status, then a job purge record
was received before a job initialization record. For cross-platforms, JCL errors
occur for invalid parameter data or executable not found at execution time.
R-NOUID
During submission, if no valid USERID is available, a check of the SUBNOID
parameter is done to determine if a job can be submitted without an ID. With
SUBNOID set to NO, the job is moved back to the request queue with a status
of R-NOUID.
R-TRLFUL
At the time the job was active, CA WA CA 7 Edition required another track to be
obtained from the trailer queue to hold outputs. At the time that CA WA CA 7
Edition tried to get another track, either an out of space condition or an I/O
error occurred.

LACTR Command
RETRY
Indicates a dynamic allocation error occurred during the attach of JCL for this
job. At a user-specified time interval, a retry of the JCL attach occurs.
RQMT-INC
Indicates a job record is in the queue without its requirements attached.
RUSH
Indicates the RUSH command was entered for this job.
SKELETON
Indicates a job record is in the queue without JCL attached.
LACTR Command
The LACTR command provides resource requirement information about jobs in the
active queue. This command lets you review the resource requirements of the currently
active workload. This command is similar to the LQR command.
Note: The LACTR command works with cross-platform jobs, but remember that
cross-platform jobs ignore the MAINID parameter.
LACTR[,AGENT={*|agent|mask}]
[,CLS=x]
[,{JOB={*|jobname|mask|nnnn}|JOBL={*|longjobname|mask}}]
[,LIST=CPU]
[,SCHID={0|nnn}]
[,ST=option]
AGENT

LACTR Command
CLS
CPUID
initiation record.
JOB
JOBL
LIST=CPU
(Optional) Specifies whether to list only the CPU jobs. LIST=CPU is the only valid
option.
MAINID
(Optional) Specifies to list only those jobs with this MAINID (as defined on the DB.1
panel). Jobs that are defined with MAINID of ALL are selected regardless of MAINID
entered.
ALL
Specifies all MAINIDS. ALL is the default.

LACTR Command
SYn
Where n specifies a CPU associated number for which to list information as
defined in the initialization file CPU statement. The value of n can range from 1
to 7. If a slash (/) precedes the SYn, the only jobs that are denoted to execute
on /SYn selected are selected.
-SYn
Where n specifies a CPU associated number for which no information is listed.
The value of n can range from 1 to 7.
NODE
SCHID
(Optional) Specifies the schedule ID for which information is selected.
SEQ
NATV
Indicates a native sequence (the order in which it is in the queue). NATV is the
default.
AGENT
Indicates an agent name sequence.
CA7
Indicates a CA 7 job number sequence.
DLTM
Indicates a deadline time sequence.
DOTM
Indicates a due-out time sequence.
JOB
Indicates a job name sequence.
NODE
Indicates a node name sequence.

LACTR Command
ST
(Optional) Indicates a selection option that is used to determine which jobs are
listed.
ABND
ARF
ARFH
ARFJ
LATE
REPLY
Required message.
SYS
More information:

LACTR Command
Examples
LACTR,MAINID=SY2
LACTR,JOB=FXABA02M
LACTR
JOB=FXABA02M DATE=YY.DDD PAGE 0001
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
FXABA02M FIXASSET ALL A/120 SYSA 0017 00043/0028 000 003 02.56 00000/0000

JOB NAME
definition panel.
SYSTEM NAME
Identifies the system name as defined on the DB.1 panel.
MAIN ID
Identifies one of the following:
■ For regular jobs, displays the value from the MAINID field on the DB.1 panel.
■ For XPJOBs, displays the value XPJ.
■ For agent jobs, displays the 3 or 4 character alias of the agent job type.
JOB C/PRT
Identifies the workload balancing class and priority for this job.
CPU ID
■ For regular jobs, displays the CPU where the job is currently executing. The ID is
not filled in until CA WA CA 7 Edition processes the job initiation record.
■ For agent jobs, displays AGJ.
■ For XPJOBs displays 7XPJ.

LAGENT Command
CA-7# NUMBR
CPU/ELAPS TIME
Identifies the CPU and CLOCK TIME from the DB.1 panel.
TOTAL TAPES TP1 TP2
Identifies the number of TAPE1 devices, TAPE2 devices, or both that this job
requires.
CPU% UTIL
Identifies the calculated CPU use (using CLOCK-TIME and CPU-TIME from the DB.1
panel).
SUBMIT DATE/TIME
Identifies the Julian date and time this job was submitted.
LAGENT Command
The LAGENT command displays agents to which this CA WA CA 7 Edition can
communicate when communication paths are available. To send agent jobs, each agent
must be defined to CA WA CA 7 Edition, and this CA WA CA 7 Edition instance must be
defined to each agent.
Using the LAGENT command provides general information about the agent status. The
Scheduling Manager (CA 7/IAS) does not stay connected to the agent on an ongoing
basis but only when there is data to send or receive from the agent. Thus, the status can
show active or inactive when no messages are sent to or from the agent. To ensure
latest status available for an agent, use the /AGENT,FUNC=PING,AGENT=agentname
command to force a communication to the agent.
Note: For more information about defining agents, see the CA Integrated Agent Services
Implementation Guide.
LAGENT[,AGENT={*|name|mask}][,LIST={SHORT|ACCUM|ALL|STATS}]
AGENT
(Optional) Specifies the agent name or mask to select agent information for display.
Default: * (all agents)

LAGENT Command
LIST
(Optional) Specifies the amount of agent information to provide.
SHORT
Lists the agent name, active status, and host name. SHORT is the default.
ACCUM
Lists the accumulated statistics for each agent requested. These statistics are
reset to zero when the CA IAS checkpoint file is initialized. This information can
be useful to detect whether any agent jobs are being sent to a particular agent.
This option also lists communication handshake information that is captured
when the agent last initiated a handshake. If the agent has not initiated
communications after the IASCKPT file was initialized, this data displays as N/A.
ALL
Lists the definition that is associated with the agents requested. This
information includes platform, code (ASCII or EBCIDC), host information, and
more.
STATS
Lists the current statistics for each agent. These statistics are reset to zero each
time CA WA CA 7 Edition is initialized. This information can be useful to detect
the last time that a message was sent or received and agent activity. This
option also lists communication handshake information that is captured when
the agent last initiated a handshake. If the agent has not initiated
communications after the IASCKPT file was initialized, this data displays as N/A.
More information:
Examples
LAGENT
LAGENT
AGENT=* PAGE 0001
AGENT Name Active Host
EROCAGENT YES 142.232.183.213

USERO23AGT YES 142.232.190.72
planor12 YES PLANOR12.CA.COM
USERO01AGT YES 139.42.4.212
SAP1 YES sapagent.ca.com
SLI2-00 REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

LAGENT Command
Agent Name
Specifies an agent defined to CA WA CA 7 Edition.
Active
Specifies whether the agent is active.
YES
Specifies that agent contact is established.
NO
Specifies that the agent is not available.
NO_CON
Specifies that we could not connect with the agent. Check:
1) The address field in the IASAGENT DD file.
2) Is the agent down?
3) Is the port in use or incorrect?
NO_DNS
Specifies that we cannot resolve the domain name and cannot connect with
the agent. Check:
1) Address field in the IASAGENT DD file?
2) Do you run multiple IP stacks and is CA 7 pointing to the correct stack?
NO_MSG
Specifies that the agent received the message, but the message was bad. Check
the agent receiver.log file:
1) Is this encryption incorrect (bad padding message)?
2) Is the message bad?
NO_SOC
Specifies that we cannot get an IP socket and cannot connect with the agent.
NO_256
Specifies a problem using 256-bit encryption occurred when connecting with
the agent.

LAGENT Command
Host
Specifies the host name or IP address where the agent is located.
Note: If the host name is greater than 50 bytes, a plus sign (+) appears at the
end of the host name to keep the display short. If the full host name is needed,
the LAGENT,LIST=ALL displays the full host name.
LAGENT,AGENT=*AGT,LIST=ALL
AGENT=*ESP LIST=ALL PAGE 0001
AGENT Name: USERO23AGT Platform: NT Active: YES

Host: 142.232.190.72
Port: 7520 Charset: ASCII

Encryption Name: TEST1 Sleep time: 300 seconds
Retry time: 4000 mseconds Retry count: 5
AGENT Name: USERO01AGT Platform: NT Active: YES

Host: 139.42.4.212
Port: 7520 Charset: ASCII

Encryption Name: TEST1 Sleep time: 300 seconds
Retry time: 4000 mseconds Retry count: 5
Agent Name
Specifies an agent defined to CA WA CA 7 Edition.
Platform
Specifies the operating system where the agent is running.

LAGENT Command
Active
Specifies whether the agent is active.
YES
Specifies that agent contact is established.
NO
Specifies that the agent is not available.
NO_CON
Specifies that we could not connect with the agent. Check:
1) The address field in the IASAGENT DD file.
2) Is the agent down?
3) Is the port in use or incorrect?
NO_DNS
Specifies that we cannot resolve the domain name and cannot connect with
the agent. Check:
1) Address field in the IASAGENT DD file?
2) Do you run multiple IP stacks and is CA 7 pointing to the correct stack?
NO_MSG
Specifies that the agent received the message, but the message was bad. Check
the agent receiver.log file:
1) Is this encryption incorrect (bad padding message)?
2) Is the message bad?
NO_SOC
Specifies that we cannot get an IP socket and cannot connect with the agent.
NO_256
Specifies a problem using 256-bit encryption occurred when connecting with
the agent.

LAGENT Command
Host
Specifies the host name or IP address where the agent is located.
Note: If the host name is greater than 50 bytes, a plus sign (+) appears at the end of
the host name to keep the display short. If the full host name is needed, the
LAGENT,LIST=ALL displays the full host name.
Port
Specifies the port number where the agent is listening.
Charset
Specifies the code set, ASCII or EBCDIC, that the agent uses.
Encryption Name
Specifies the name of encryption scheme for communication with this agent.
Sleep time
Specifies the amount of time to wait in seconds after the last retry before retrying
the connection.
Retry time
Specifies the the amount of time in milliseconds between connection retries.
Retry count
Specifies the number of connection retries before sleeping.
LAGENT,LIST=STATS,AGENT=SCH*
AGENT=SCH* LIST=STATS PAGE 0001
AGENT Name: USERO23ESP Release: Rvv.n Build: nnn

HostName: USERO23-XP
OSText: Windows XP for x86
Last Outbound: yy.187 15:04:19 Last Inbound: yy.187 15:04:19
Outbound Attempts: 1 Succeeded: 1 Failed: 0
Inbound Attempts: 2 Succeeded: 0 Failed: 0
Outbound Messages: 1 Queued: 1 Purged: 0
Inbound Messages: 2 Queued: 2
Outbound Bytes: 135 Inbound Bytes: 374

LAGENT Command
Release
Specifies the software release for this agent.
Build
Specifies the software build information for this agent.
HostName
Specifies the host on which this agent is running.
OSText
Specifies the operating system on which this agent is running.
Note: Fields Release, Build, HostName, and OSText are captured only when the agent
initiates the communication handshake with CA WA CA 7 Edition. The fields contain N/A
if this agent has not initiated a handshake since the IASCKPT DIV file was initialized.
Because CA WA CA 7 Edition initiates the communication handshake during its start-up,
the agent must have started after CA WA CA 7 Edition is active to display data other
than N/A.
Last Outbound
Specifies the date and time of last contact out to the agent.
Last Inbound
Specifies the date and time of last connection from the agent.
Outbound Attempts
Specifies the number of connections tried from CA WA CA 7 Edition to this agent.
Succeeded
Specifies the number of successful connections.
Failed
Specifies the number of failed connections.
Inbound Attempts
Specifies the number of connections detected from the agent to CA WA CA 7
Edition.
Succeeded
Specifies the number of successful connections.
Failed
Specifies the number of failed connections.
Outbound Messages
Specifies the number of messages built to send to the agent.

LARF Command
Queued
Specifies the number of messages queued for output to the agent.
Purged
Specifies the number of messages deleted from the queue.
Inbound Messages
Specifies the number of messages received from the agent.
Queued
Specifies the number of messages queued from the agent.
Outbound Bytes
Specifies the number of total bytes in outbound messages.
Inbound Bytes
Specifies the number of total bytes in received messages.
LARF Command
The LARF command lists ARFSETs in summary or in detail. The ARFSETs are stored in
alphabetical order by ARFSET name. Each ARFSET contains one or more ARFSET
definitions. Each ARFSET definition defines a specific job processing condition that may
arise during the job's execution, such as a system D37 abend. Associated with each test
is a list of ARF responses that ARF carries out when the designated condition arises. This
response set can include directives for issuing CA WA CA 7 Edition commands or
submitting other jobs on behalf of the CA WA CA 7 Edition job that met the ARF test
conditions.
LARF[,ARFSET={*|arfset|arfset*}][,LIST=listopt]
ARFSET
(Optional) Defines the ARFSET name.
*
Specifies all ARFSETs. This value is the default.
arfset
Defines a specific ARFSET name.

LARF Command
arfset*
Defines a generic ARFSET name.
Limits: 1 to 7 alphanumeric characters that are terminated with an asterisk
LIST
Overrides the default list option. The possible values are the following:
DEFS
Forces the detail listing of the ARFSET definitions.
NODEFS
Forces 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.
Example: List all ARFSETS and details
This example lists all definition details for all ARFSETs in the ARF database:
LARF,ARFSET=*,LIST=DEFS
Examples
The following are LARF examples.

LARF Command
Example 1. Output: LARF With Generic ARFSET
LARF
ARFSET=* LIST=NODEFS DATE=yy.064 PAGE 0001
ARF SET ARF LAST CHANGE NBR EC EE JC LA LB LE LS SC IS
NAME UID DATE TIME DEF # # # # # # # # #
ALL 000 02/22/yyyy 18:20 4 1 . . . . 1 1 1 .

BEC 000 02/28/yyyy 14:10 1 1 . . . . . . . .
BEE 000 02/28/yyyy 14:14 1 . 1 . . . . . . .
BLA 000 02/28/yyyy 13:39 2 . . 1 . . . . 1 .
EC 000 02/21/yyyy 14:25 1 1 . . . . . . . .
JC1 000 02/12/yyyy 13:15 1 . . 1 . . . . . .
JJJ 000 02/27/yyyy 15:35 2 . . 1 1 . . . . .
LA 000 02/14/yyyy 15:35 1 . . . 1 . . . . .
LE 000 02/16/yyyy 14:21 1 . . . . . 1 . . .
LS 000 02/22/yyyy 14:24 1 . . . . . . 1 . .
MSGS 000 02/28/yyyy 16:56 2 . . 1 . . . . 1 .
MULTI 000 02/08/yyyy 14:09 3 . . 3 . . . . . .
NEW 000 02/29/yyyy 10:01 1 . . . 1 . . . . .
SCWTO 000 02/15/yyyy 18:52 1 . . . . . . . 1 .
TESTJC 000 02/14/yyyy 15:00 1 . . 1 . . . . . .
TESTJC2 000 03/01/yyyy 17:30 1 . . 1 . . . . . .
SLIW-00 REQUEST COMPLETED AT 10:48:09 on yy.ddd

ARFSET LIST
Identifies the options that are in effect for this command.
ARF SET NAME
Identifies the name of the ARFSET.
ARF UID
Identifies the CA WA CA 7 Edition UID associated with the ARFSET.
LAST CHANGE DATE
Identifies the date when this ARFSET was last changed.
LAST CHANGE TIME
Identifies the time of day when this ARFSET was last changed.
NBR DEF
Identifies the total number of ARF definitions within this ARFSET.

LARF Command
EC
Identifies the number of elapsed time completion tests within this ARFSET.
EE
Identifies the number of elapsed execution-time tests within this ARFSET.
JC
Identifies the number of job completion tests within this ARFSET.
LA
Identifies the number of late tests within this ARFSET.
LB
Identifies the number of late begin time tests within this ARFSET.
LE
Identifies the number of late end time tests within this ARFSET.
LS
Identifies the number of late at submit time tests within this ARFSET.
SC
Identifies the number of step completion tests within this ARFSET.
IS
Identifies the number of interrupt submission tests within this ARFSET.
Example 2. Output: LARF With Specific ARFSET
LARF,ARFSET=MULTI
ARFSET=MULTI LIST=DEFS DATE=yy.064 PAGE 0003
ARFSET: MULTI UID: 000 CHG: 02/08/20yy-14:09 DEFS: 3/ 3 RSPID: MASTER
INTERCEPT TYPE: JC INDEX: 3

APPLICABILITY TESTS:
SYS EQ * SID EQ 0 RSTC GE 0 EM EQ ANY
FROM: 01/01/1975 00:01 TO: 12/31/2074 23:59
TESTS RUN DURING INTERCEPT PROCESSING:
STEP EQ * PROC EQ * PGM EQ *
SYS EQ 00C5 OR SYS EQ 00C6 OR CC GE 0016
RESPONSE SET:
AM,CM=T,USER=C495MM1,M=THIS IS AN 0C5 OR AN 0C6!!!
AM,CM=T,USER=TOM,M=HI
AW,TIME=0002
AC,M=/WTO,M=HOWDY
AJ,RETRY=001,DELAY=002,ACTION=3,JOB=G
DISP=R CA-11=N BYPGDG=N USAGE= PROCESS= CC=
STEPS: START= END=
SLIW-00 REQUEST COMPLETED AT 10:48:31 on yy.ddd

LARF Command

ARFSET LIST
ARFSET:
Identifies the name of the ARFSET.
UID
Identifies the CA WA CA 7 Edition UID associated with the ARFSET.
CHG
Identifies the date and time when this ARFSET was last changed.
DEFS
Identifies the number of the current ARF definition within this ARFSET and total
number of ARF definitions within this ARFSET.
RSPID
Identifies the ID that is used during ARF recovery.
INTERCEPT TYPE
Identifies the CA WA CA 7 Edition or ARF intercept where this test definition is
applied.
INDEX
Identifies the ARF definition index number that is assigned to this test definition.
APPLICABILITY TESTS
Identifies the applicability tests. These tests are applied when the job is being
placed into the request queue. They can pertain to the context in which the job
runs and can be evaluated before the job begins.
EM
Identifies the entry node under which the job is running for this test to apply.
RSTC
Identifies the restart count condition where this test is to apply.
SID
Identifies the CA WA CA 7 Edition schedule ID under which the job must run for
this test to apply.
SYS
Identifies the SMF system ID where the job must run for this test to apply.

LARF Command
FROM TO
Identifies the From and To dates defining the time frame within which the tests are
to apply.
TESTS RUN
Identifies the ARF tests that are run at the time of the intercept. These vary greatly
depending upon the intercept. In this example, the job completion intercept tests
are shown.
CC
Identifies a completion code condition.
FLSH
Identifies a flush condition.
HRC
Identifies a high job return code condition.
JCL
Identifies a JCL error condition.
PGM
Identifies the program name to which the tests apply.
PROC
Identifies the proc step name where to apply the tests.
STEP
Identifies the step name where to apply the tests.
SYS
Identifies a system abend condition.
USER
Identifies a user abend condition.

LARF Command
RESPONSE SET
Identifies the set of responses for ARF to attempt when the test conditions are met.
In the example, several possible ARF responses are illustrated:
M=
Identifies an example ARF Message response. ARF sends a message to the
designated target and then moves to the next response.
TIME=
Identifies an example ARF Wait response. ARF waits the designated number of
minutes and then moves to the next response.
AC
Identifies an example ARF Command response. ARF issues the designated CA
WA CA 7 Edition command and then moves to the next response.
AJ
Identifies an example ARF Job response. ARF submits another job, waits for
that job to complete, and then moves to the next response.
DISP
Identifies the final disposition to assign to the job if all ARF responses complete
typically.
M1
Identifies the final disposition control detail line 1.
DISP
Identifies the disposition directive: R - Restart; C - Cancel; F - Force Complete.
CA-11
Identifies whether to use CA WA Restart Option for the restart.
BYPGDG
Instructs CA WA Restart Option in the handling of GDGs during the restart.
USAGE
Identifies the CA WA Restart Option usage code to use in restart.
PROCESS
Identifies the CA WA Restart Option process code to use in restart.

LARFQ Command
CC
Identifies the condition code value to use in CA WA Restart Option.
START
Identifies the first step in the job where CA WA Restart Option starts restart
processing.
END
Identifies the last step in the job to process when CA WA Restart Option is
controlling the restart.
LARFQ Command
The LARFQ command lists the ARF queue. The ARF queue identifies all pending and
in-process response activities that were initiated by CA WA CA 7 Edition jobs being
tracked by ARF where the designated ARF test conditions were met. Each queue entry
defines the presence of an ARF response set for a single job. The ARF queue is ordered
in a first-in, first-out sequence. A given job can only have one queue entry active at a
time. If a given CA WA CA 7 Edition job has met multiple ARFSET tests, the subsequent
response sets are queued up "behind" the one active response set for that job. The
active response set for a given job is referred to as that job's "current" response set.
When a job's current response set comes to a conclusion, ARF "promotes" the next
response set that was queued up behind the current one. The promotion process
deletes the previous current response set and sets up a new current response set for a
given job. When all response sets for a given job have been completed, the job's ARF
queue entry is deleted altogether.
LARFQ[,JOB={*|jobname|jobnumber|mask}]
JOB
(Optional) Specifies the jobs whose ARF queue resource information you want to
list.
*
jobname

LARFQ Command
mask
Defines a generic job name.
Limits: 1 to 7 alphanumeric characters terminated with an asterisk
jobnumber
Defines a specific CA 7 job number.
Examples
LARFQ
JOB=* DATE=yy.043 PAGE 0001
JOB JOB ARF SET SET EVENT RSP RSP RSP RESPONSE
NAME NBR NAME IX STATUS CD # TOT TYPE STATUS
ARRPT12 0291 SPACECK 1 IN-PROC JC 1 FINAL

PRMTH20 0312 SPACECK 1 IN-PROC JC 1 FINAL
APRST15 0317 ABNDHLD 1 IN-PROC JC 1 FINAL*
APRST15 0317 ABNDHLD 1 IN-PROC JC 1 ERROR* 01000016 (0003)
SLIY-00 REQUEST COMPLETED AT 10:29:04 on yy.ddd

JOB
JOB NAME
Identifies the name of the job on whose behalf ARF is processing.
JOB NBR
Identifies the CA 7 job number of this job.
ARF SET NAME
Identifies the ARFSET name defining the responses that are being processed.
IX
Identifies the ARFSET definition index identifying the response set being processed.
SET STATUS
Identifies the status of ARF processing for this job.

LARFQ Command
EVENT CD
Identifies the type of intercept (event) where the ARF test conditions were met.
RSP #
Identifies the relative response number in the ARF response set where ARF is
currently processing.
RSP TOT
Identifies the total number of responses in the current response set.
RSP TYPE
Identifies the type of ARF response currently being processed, or indicates that an
error has occurred. If the value is ERROR, ARF processing is suspended for the job.
The codes (01000016 (0003) in this example) provide additional information about
the error. Because the job is still under ARF control, use the ARFP command to
continue with manual recovery.
RESPONSE STATUS
Indicates the current status of the current response being processed by ARF.
0100000C on the panel example
The value of @ARFQ_RETCODE is displayed in the event of an error condition. The
possible values are the following:
0100000C
A CA WA CA 7 Edition violation was detected for a command issued by ARF. A
CA-7.012 message is produced at the MASTER station. A security violation
occurred or an unidentified command was detected.
01000016
A CA WA CA 7 Edition security violation was detected for a terminal signon
attempted by ARF. A CA-7.022 message is produced at the MASTER station.
00000001
An error occurred while processing a RESTART command issued by ARF. SJRx
messages are produced at the MASTER station indicating the nature of the
error.
0200xxyy
An error occurred while processing a DEMAND or RUN command issued by
ARF. SPO7 messages are produced at the MASTER station indicating the nature
of the error. (If the value of xx is 0D or 0E, yy contains the return code from
SASSSCSR.)

LCTLG Command
(003) on the panel example

The value of @ARFQ_RSPERR is displayed in the event of an error condition. The
possible values are the following:
0001
An error occurred while trying to process a final disposition.
0002
ACTION = E was encountered on an AJ action statement.
0003
An error occurred while trying to process a command.
LCTLG Command
The LCTLG command primarily lists data set information from the CA WA CA 7 Edition
database. You can also use it to list special entries such as documentation, networks,
triggers, or requirements from the database. When LCTLG is used to list data sets, the
following information is displayed: volume information, creation dates and times, and
device information. Also, use this command to list information from a specific CVOL
catalog.
LCTLG,{DSN=dsname[,VOLSER=volser]|MASK=mask}
[,TZ={CA7|EXEC}]
DSN
Defines the fully qualified name of the data set. For partial qualification, the name
can end with a period or can be delimited with an asterisk (*) after the first node.
DSN cannot be specified with MASK.
VOLSER
(Optional) Defines the volume serial number of a catalog, instead of the CA WA CA
7 Edition database, from which information is listed. The value must be the volume
serial of the pack on which the desired catalog data set resides. VOLSER is not used
when listing information from the database; only when listing from a catalog on
some other volume. VOLSER cannot be specified with MASK.

LCTLG Command
MASK
Defines the fully qualified name or mask pattern of the data set. MASK can only be
used for data set names. MASK does not return prose, network, trigger, or
requirement information. MASK cannot be specified with DSN.
Limits: 1 to 44 alphanumeric characters plus * and ?
TZ
(Optional) Controls whether the date/times of a data set's creation or last update is
normalized to the time zone of the running CA WA CA 7 Edition.
Default: Specified by the TZDISPLAY keyword on the SMF initialization file
statement.
CA7
Defines that the creation or update date/time is normalized to the running CA
WA CA 7 Edition time zone.
EXEC
Defines that the creation or update date/time is in the execution time zone.
Examples
LCTLG,DSN=CA7.DSN1
LCTLG,DSN=CA7.
LCTLG,DSN=CA7.,VOLSER=CATLG
LCTLG,DSN=AUTO.
LCTLG,DSN=JDEP.,TZ=CA7
LCTLG,DSN=TRGD.,TZ=EXEC
LCTLG,MASK=CA7.???.*.DSN1
LCTLG,MASK=CA7*
LCTLG,MASK=*

LCTLG Command
LCTLG,DSN=JDEP.
DSN=JDEP. DATE=YY.DDD PAGE 0002
DATASET NAME TRIGGERED JOB SCHID QTM/DOTM LEADTM SUBMTM
JDEP.DUSABDDM DUSAFC32 002 0100Q 0100 0000

DUSAFC33 002 0100Q 0100 0000
JDEP.DEPO01A0 TPRE01A0 001/001 1600D 0100 0000
JDEP.DUMBDL08 DUHNLAMB 001/002 0800D 0010 0000
DUHNLAMB 002/003 0830D 0020 0000
JDEP.DUSABCLP DUSAGEN4 000 1000D 0100 0900
DUSAGEN8 000 1000D 0100 0900

DATASET NAME
Identifies a job name (prefixed by JDEP.) of a job that triggers jobs.
TRIGGERED JOB
Identifies the name of the job that is triggered.
SCHID
Identifies the schedule ID that the triggering job must run under for the trigger to
occur; optionally, followed by a different schedule ID that the triggered job runs
under.
QTM/DOTM
Identifies either the queue time or the due-out time (defined on the DB.2.4 panel)
for this trigger entry in hhmm format.
LEADTM
Identifies the lead time for this trigger entry as defined through the DB.2.4 panel in
hhmm format.
SUBMTM
Identifies the submit time as defined on the DB.2.4 panel in hhmm format.
LCTLG,DSN=AUTO.
DSN=AUTO. DATE=YY.DDD PAGE 0001
DATASET NAME TRIGGERED JOB SCHID QTM/DOTM LEADTM SUBMTM
AUTO.DS000005 (CA7.TRNG1)
TESTJOB1 000 1200D 0100 0000
AUTO.DS000009 (CA7.TEST9)
DUSAXX10 000 0100Q 0030 0000
AUTO.DS000011 (CA7.TRNG2)
DUTSXX04 000 0020Q 0030 0000
DUSGXX05 001/002 0030Q 0030 0000

LCTLG Command

DATASET NAME
Identifies the DSNBR (prefixed by AUTO.) followed by the data set name enclosed in
parentheses of the data set whose creation triggers a job or jobs, or AUTO.NW
followed by the input network name whose completion triggers a job or jobs.
TRIGGERED JOB
Identifies the name of the job that is triggered.
SCHID
Identifies the data set must be created or updated or the input network completed
under this schedule ID for the trigger to occur; optionally, followed by a different
schedule ID that the triggered job runs under.
QTM/DOTM
Identifies either the queue time or the due-out time (defined on the appropriate
panel) for this trigger entry in hhmm format.
LEADTM
Identifies the lead time for this trigger entry as defined through the appropriate
panel in hhmm format.
SUBMTM
Identifies the submit time as defined on the appropriate panel in hhmm format.
LCTLG,DSN=PP.
DSN=PP. DATE=YY.DDD PAGE 0001
--------------- DATASET NAME --------------- DSNBR POSTTM TYPE
PP.SOCCXX01.JOB ............................ PP00000012 JTERM JOB

SLID-00 REQUEST COMPLETED AT 18:42 on yy.ddd

DATASET NAME
Identifies the data set name for documentation entries is determined as follows:
■ For job documentation, the name is PP.jobname.JOB
■ For data set documentation, the name is PP.data set name
■ For system documentation, the name is PP.system name.SYS

LCTLG Command
■ For user documentation, the name is PP.user name

■ For network documentation, the name is PP.network name.NW
■ For dd documentation, the name is PP.job name.step name.ddname.
DSNBR
Identifies a CA WA CA 7 Edition assigned number (with the prefix of PP) by which
this entry is known.
POSTTM
Identifies when the posting of this data set creation occurs. Values are JTERM for
job completion processing time or DSCRT for posting at data set creation time.
TYPE
Identifies the type of documentation as job, data set, system, user, network, or
job/step/dd.
LCTLG,DSN=TRGD.
DSN=TRGD. DATE=YY.DDD PAGE 0001
DATASET NAME TRIGGERED BY JOB/DSN SCHID QTM/DOTM LEADTM SUBMTM
TRGD.ADDRQ TRAILER 000 0010Q 0010 0000

TRGD.BRO ADDRQ 000 0010Q 0010 0000
TRGD.CA7FRCST SCHDDUMY 000 0030Q 0010 0000
TRGD.CA7LJOBA CA7LRLOG 000 0010Q 0010 0000
TRGD.CA7LJOBB CA7LJOBA 000 0010Q 0010 0000
SLID-00 REQUEST COMPLETED AT 11:59:32 on yy.ddd

DATASET NAME
Identifies a job name (prefixed by TRGD.) of a job that is triggered either by another
job's completion or a data set creation.
TRIGGERED BY JOB/DSN
Identifies the job name of the job that triggers this job, the DSNBR of a data set
whose creation triggers this job, or the DSNBR of an input network whose
completion triggers this job.
SCHID
Identifies the schedule ID that the job must run under, that a data set must be
created under or that the input network must be brought into the preprocess
queue under for the trigger to occur; optionally, followed by a different schedule ID
that the triggered job runs under.
QTM/DOTM
Identifies either the queue time or the due-out time defined on the appropriate
trigger panel in hhmm format.

LCTLG Command
LEADTM
Identifies the lead time for this trigger entry as defined on the appropriate trigger
panel in hhmm format.
SUBMTM
Identifies the submit time as defined on the appropriate trigger panel in hhmm
format.
LCTLG,DSN=PRED.
DSN=PRED. DATE=YY.DDD PAGE 0001
DATASET NAME SUCCESSOR JOB SCHID
PRED.CA07LOGP CA07LOGH 000

PRED.CA07LOGS CA07LOGH 000
PRED.D463XX02 D463XX05 000
PRED.D463XX03 D463XX05 000
PRED.D463XX04 D463XX06 000
SLID-00 REQUEST COMPLETED AT 11:59:33 on yy.ddd

DATASET NAME
Identifies a job name (that PRED. prefixes) of a job that is a requirement for another
job or jobs.
SUCCESSOR JOB
Identifies the name of the dependent job.
SCHID
Identifies the schedule ID of the dependent job with the requirement. Optionally, a
different schedule ID follows when the successor job is a triggered job that runs
under a different schedule ID.
LCTLG,DSN=ABC.
DSN=ABC. DATE=YY.DDD PAGE 0001

TZO DATE TIME GDG# #VOL VOLSER DEV-TYPE SEQ
ABC.NAME.INPUT ............................. DS00000054 JTERM PERM

-06:00 YYDDD 152506 0003 001 LIB114 3050200E 0005
YYDDD 151658 0002 001 LIB114 3050200E 0005
YYDDD 115744 0001 001 LIB114 3050200E 0005
ABC.NAME.INPUT2 ............................ DS00000082 JTERM
-05:00 YYDDD 080025+ 0018 001 LIB114 3030200E 0001
YYDDD 073903+ 0017 001 LIB114 3030200E 0001
YYDDD 102406+ 0016 001 LIB114 3030200E 0001
ABC.NAME.OUTPUT ....... .................... DS00000055 JTERM

LCTLG Command

DATASET NAME
Identifies the fully qualified data set name as defined in the CA WA CA 7 Edition
database.
DSNBR
Identifies a CA WA CA 7 Edition assigned number by which this entry is also known.
POSTTM
TYPE
Values 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 CA WA CA 7
Edition.
■ INTL for a data set created and used by jobs defined to CA WA CA 7 Edition.
■ PERM for a data set defined as permanent.
TZO
Identifies the time zone offset from UCT of the site where a creation or update of
this data set occurred.
DATE
Identifies the last three Julian dates that a creation or update of this data set
occurred through a CA WA CA 7 Edition submitted job.
TIME
Identifies the last three times that a creation or update of this data set occurred
through a CA WA CA 7 Edition submitted job in hhmmss format. A plus sign that is
displayed immediately after the field value indicates that the date/time is
GDG#
Identifies the generation data group number for a GDG data set.
VOL
Identifies the number of volumes that this data set spans.

LCTLG Command
VOLSER
Identifies the volume where this data set was created.
DEV-TYPE
Identifies the hexadecimal device code for the device where this data set was
created.
SEQ
Identifies the sequence number of this data set.
LCTLG,MASK=ABC.????.*
DSN=ABC.????.* DATE=YY.DDD PAGE 0001

TZO DATE TIME GDG# #VOL VOLSER DEV-TYPE SEQ
ABC.NAME.INPUT ............................. DS00000054 JTERM

ABC.NAME.OUTPUT ............................ DS00000055 JTERM

DATASET NAME
database.
DSNBR
Identifies a CA WA CA 7 Edition assigned number by which this entry is also known.
POSTTM
TYPE
Specifies one of the following values:
■ EXTL for a data set either created or used by jobs defined to CA WA CA 7
Edition.
■ INTL for a data set created and used by jobs defined to CA WA CA 7 Edition.
■ PERM for a data set that is defined as permanent.

LDSN Command
LDSN Command
The LDSN command lists data set information from the database including data set
attributes, device and volume information, and information about which jobs use the
data set or are trigger scheduled as a result of its creation.
LDSN,{DSN=dsname|DSNBR={DSnnnnnnnn|DS0nnnnnn*|DS*}}
[,LIST={DSN|option}]
[,USERS={0,32767|(minimum,maximum)}]
DSN
Defines the fully qualified name of the data set. For partial qualification, the name
can end at a period or can be delimited with an asterisk (*).
Required: Yes (unless DSNBR is used)
DSNBR
Defines a single or generic CA WA CA 7 Edition data set number identifying the
members whose records are to be listed. Must be entered with the DS prefix. With
this option, the major sequence of the output listed is by data set number.
Required: Yes (unless DSN is used)
DSnnnnnnnn
Defines the value for a single CA WA CA 7 Edition assigned data set number in
up to eight digits with a prefix of DS. Leading zeros can be omitted.
DS0nnnnnn*
Defines a generic data set number in up to seven digits preceded with DS and
terminated with an asterisk. The leading zero must not be omitted. For
example, to list all DSNBRs in the range 7000-7999, use DSNBR=DS00007*.
DS*
Specifies all data set records.
LIST
(Optional) Specifies list options for data set information.
DSN
Specifies data set information only. DSN is the default.
ALL
Specifies data set information, "using-jobs" and documentation entries.

LDSN Command
EXTL
Specifies data sets that are classified external to CA WA CA 7 Edition.
INTL
Specifies data sets that are classified internal to CA WA CA 7 Edition.
NORM
Specifies data sets shown as NORM on the DB.6 panel. Includes internal and
external data sets.
NOUSER
Specifies data sets that have no "using-jobs."
PERM
Specifies data sets shown as PERM on the DB.6 panel.
TRIG
Specifies all the jobs that the data set triggers.
USERS
Specifies all users of a data set. These are jobs that reference the data set in
their JCL. Jobs with large JCL may not show in the list (for example, over 100
steps and 500 DDs).
Note: LIST=TRIG and LIST=ALL cannot be used for generic requests by DSN or
DSNBR.
USERS
(Optional) Specifies selecting data sets meeting minimum and maximum number of
using jobs.
minimum
Specifies 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.

LDSN Command
Examples
LDSN,DSN=CA7.DSN1
LDSN,DSN=CA7.DSN1,LIST=USERS
LDSN,DSN=DS50,LIST=ALL
LDSN,DSNBR=DS*,LIST=NOUSER
LDSN,DSNBR=DS00003*
LDSN,DSNBR=DS*,LIST=PERM

LDSN Command
LDSN Panel
LDSN,DSN=SSDDEV.CA07.BATCHO,LIST=ALL
LIST=ALL DSN=SSDDEV.CA07.BATCHO DATE YY.DDD PAGE 0001
--------------- DATASET NAME --------------- DSNBR PPNBR POSTTM DSTYPE

DSORG RECFM LRECL BLKSZ DEVTYP J-USE J-CRT #RQ MDATE/TIME MTYPE
SSDDEV.CA07.BATCHO ......................... 00000020 *NONE* JTERM PERM

PS VB 00137 04114 DASD 00020 00000 0000 YYDDD/0931 DBM
. LAST MAINTENANCE ON yy.ddd AT hh:mm:ss VIA DBM BY OPERATOR: yyyyyyyy

. LAST CREATED D/T: YY.DDD 03:10:43
--------------------- DATASET/JOB CROSS REFERENCE ---------------------
JOB=D463BTI STEP-NUMBER=001 DISP=SHR
JOB=CA7LJESX STEP-NUMBER=001 DISP=SHR
JOB=CA7LJOBX STEP-NUMBER=001 DISP=SHR
SLIB-00 REQUEST COMPLETED AT 10:18:26 ON yy.ddd.
LDSN,DSN=SSDDEV.CA07.BATCHC,LIST=ALL
LIST=ALL DSN=SSDDEV.CA07.BATCHC DATE YY.DDD PAGE 0001

SSDDEV.CA07.BATCHC ......................... 00000023 *NONE* JTERM PERM

PS F 00080 00080 DASD 00020 00000 0000 YYDDD/0422 DBM
. LAST MAINTENANCE ON yy.ddd AT hh:mm:ss VIA DBM BY OPERATOR: yyyyyyyy

. LAST CREATED:CA 7=YY.DDD 03:10:42 EXEC=YY.DDD 04:10:42 EXEC TZO=-05:00
--------------------- DATASET/JOB CROSS REFERENCE ---------------------
JOB=CA7LRLOG STEP-NUMBER=001 DISP=SHR
JOB=CA7IDRNG STEP-NUMBER=001 DISP=SHR
JOB=CA7PND03 STEP-NUMBER=001 DISP=SHR
SLIB-00 REQUEST COMPLETED AT 10:18:26 ON yy.ddd.
LDSN,DSN=SYS2.PROCLIB
LIST=DSN DSN=SYS2.PROCLIB DATE YY.DDD PAGE 0001

SYS2.PROCLIB ............................... 00000190 *NONE* JTERM PERM

00000 00000 DASD 00000 00000 0000 YYDDD/1033 LOAD
SLIB-00 REQUEST COMPLETED AT 17:01:15 on yy.ddd.

LDSN Command
LDSN,DSNBR=DS* Panel
LDSN,DSNBR=DS*
LIST=DSN DSNBR=DS* DATE YY.DDD PAGE 0001

SSDECS.CA07.VM.LOADLIB ..................... 00000001 PP000070 JTERM PERM
PO U 04096 04096 DASD 00001 00000 0000 YYDDD/1451 DBM
SSDECS.CA07.VM.U7TEST02 .................... 00000002 PP000060 JTERM INTL,AUTO

PS F 00080 00080 DASD 00003 00001 0000 YYDDD/1632 SMF
SSDECS.CA07.VM.U7TEST09 .................... 00000003 *NONE* JTERM INTL,AUTO

PS F 00080 00080 DASD 00001 00001 0000 YYDDD/0737 SMF
SSDDEV.CA07.LOADLIB ........................ 00000004 *NONE* JTERM PERM

00000 00000 UNKNOWN 00000 00000 0000 YYDDD/1648 DBM
SSDDEV.CA07.U7TEST02 ...................... 00000005 *NONE* JTERM EXTL,AUTO

00000 00000 UNKNOWN 00000 00000 0000 YYDDD/1648 DBM

DATASET NAME
database.
DSNBR
Identifies a CA WA CA 7 Edition assigned number that this entry is also known by.
PPNBR
Identifies the documentation DSNBR for this data set.
POSTTM
DSTYPE
Identifies one of the following values:
■ EXTL for a data set that is either created or used by jobs defined to CA WA CA 7
Edition.
■ INTL for a data set that is created and used by jobs defined to CA WA CA 7
Edition.
■ PERM for a data set defined as permanent.

LDSN Command
DSORG
Identifies the data set organization.
RECFM
Identifies the record format for this data set.
LRECL
Identifies the record size.
BLKSZ
Identifies the blocksize for this data set.
DEVTYP
Identifies the device type (DASD or TAPE) for this data set. (UNKNOWN indicates
that the data set was added using the DSN panel without specifying the device.)
J-USE
Identifies the number of jobs that use this data set as input.
J-CRT
Identifies the number of jobs that created or updated this data set.
#RQ
Identifies the number of jobs that have had a manual connection made on the
DB.3.1 panel for this data set.
MDATE/TIME
Identifies the date and time of the last maintenance performed on this data set
entry.
MTYPE
Identifies the method used for the last maintenance performed on this data set.
■ 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.
LAST CREATED D/T
Identifies the last date and time that a creation or update of this data set occurred
through a CA WA CA 7 Edition submitted job. This line is generated only if data set
EXEC time is equal to CA7 time.
DATASET/JOB CROSS REFERENCE
Identifies the jobs that reference this data set, the step that it is referenced in and
the disposition.

LDTM Command
LAST CREATED
Identifies the last date and time that a creation or update of this data set occurred
through a CA WA CA 7 Edition submitted job. This line is generated only if data set
EXEC time is different from CA7 time.
LAST CREATED. CA 7
Indicates the date/time is normalized to the time zone of the running CA WA
CA 7 Edition.
LAST CREATED. EXEC
Indicates the execution time zone date/time.
LAST CREATED. EXEC TZO
Indicates time zone offset (TZO) from UCT of the site where the job ran. To
determine the TZO of the local CA WA CA 7 Edition, issue a /DISPLAY,ST=CA7
command.
LDTM Command
The LDTM command displays an analysis of outstanding requirements for jobs in the
request queue that involve fixed satisfaction lead times. These requirements are job,
data set, and network requirements where a fixed satisfaction lead time has been
specified either on the requirement definition itself or on the job definition panel.
The LDTM command can be used to determine which outstanding requirements to post
manually after an application or system outage has disrupted the normal flow of the
production workload.
LDTM[,AGENT={*|agent|mask}]
[,CLS=x]
[,{JOB={*|jobname|jobnumber|mask}|JOBL={*|longjobname|mask}}]
[,LIST={ALL|CPU}]
[,OUTAGE={duration}
{(startdate,starttime,duration)}
{(startdate,starttime,enddate,endtime)}]
[,ST=option]

LDTM Command
AGENT
CLS
JOB
JOBL
LIST
(Optional) Can be used in combination with the OUTAGE keyword. If the OUTAGE
keyword is specified and the LIST keyword is not specified, only requirements that
match the outage window are listed. If LIST=ALL is specified, all outstanding
requirements with fixed satisfaction lead times are listed regardless of whether
they match the outage window. If LIST=CPU is specified, only CPU jobs are listed.
NODE

LDTM Command
OUTAGE
(Optional) Specifies the duration, time frame, or both of the application or system
outage that has occurred. If an outage is specified, the outstanding requirements
with fixed satisfaction lead times are subjected to further analysis to determine if
the requirement might have been satisfied if the outage had not occurred. For
more information, see the Usage Notes.
duration
Use this format to specify an outage duration without any date/time reference.
The duration can be expressed as a number of hours (one to three digits), or as
hours and minutes (four digits).
OUTAGE=8 An 8 hour outage.
OUTAGE=0130 A 1 hour 30 minute outage.
(start date, start time, duration)

Use this format to express an outage with a starting point and a fixed amount
of time forward from that point (duration).
The starting date/time is specified on the keyword. The ending time is
calculated as the starting date/time plus the duration. The starting date can be
expressed as a Julian date (five digits) or Gregorian date (six digits). The starting
time can be expressed as hhmm (4 digits) where hh is the hour (00-24) and mm
is the minutes (00-59). If no time is specified, the default is the beginning of the
day (0000).
The duration can be expressed as a number of hours (one to three digits), or as
hours and minutes (four digits). If no duration is specified, the default is the
remainder of the day from the start time (2400 - start).
OUTAGE=(13001,1300,8) Jan 1, 2013 (1:00 pm - 9:00 pm)
OUTAGE=(010213,1200,24) Jan 2, 2013 (noon) - Jan 3, 2013 (noon)
(start date, start time, end date, end time)

Use this format to express both a starting and ending point for the outage
window.
The dates can be expressed as Julian dates (five digits) or Gregorian dates (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 the default is the
beginning of the day (0000). If no end time is specified the default is the end of
the day (2400).
OUTAGE=(13001,1200,13002,0800) Jan 1 (noon) - Jan 2 (8 am)
OUTAGE=(010213,,010313) All of Jan 2 and Jan 3, 2013

LDTM Command
ST
(Optional) Specifies the display criteria for the queue information. If omitted,
displays all jobs in the request queue.
ABND
AGENT
Indicates only agent jobs that encountered a problem with the agent.
ARAE
Indicates only jobs that encountered an ARF attach error.
ARF
Indicates only jobs that are being tracked by ARF.
ARFH
ARFJ
CBAD
Indicates only the jobs that are in bad completion code status.
COMP
Indicates jobs that have completed successfully and are waiting for CA WA CA 7
Edition completion processing.
HELD
Indicates jobs in hold status.
JCLO
Indicates jobs requiring JCL or PARM overrides.
JCLR
Indicates jobs that are in JCL or PARM error status.
LATE

LDTM Command
MANV
Indicates jobs requiring manual verification.
MJOB
Indicates only jobs requeued because of multiple JOB statements.
NODE
Indicates only internal cross platform jobs that encountered a node problem.
NOID
Indicates only the jobs that are in security error status.
REQU
Indicates only the jobs that are in requeue status.
RSTR
Indicates jobs requiring restart.
RTRY
Indicates only the jobs that are in retry status.
SKEL
Indicates only the jobs that are in skeleton status.
SYS
More informmation:

LDTM Command
Usage Notes
The purpose of the LDTM command is not to tell you what requirements to post
manually. Its purpose is to streamline that process by eliminating requirements that
obviously do not fit the outage criteria that you provided it. The final determination of
whether a requirement should be manually posted or not depends on the type of
outage that occurred, how you have built your production workload, and the reasons
why a fixed satisfaction lead time was specified for the requirement in the first place.
The LDTM command attempts to analyze the processes that occurred when the job first
came into the queue and the determination was made whether to satisfy a requirement
initially, or leave it outstanding. When an outage duration or an outage window is
supplied, the process can panel out requirements that obviously do not match the
outage criteria. This leaves you with fewer requirements to be manually evaluated
based on the type of outage that occurred and your knowledge of the workload you are
running.
The command selects outstanding requirements for jobs in the request queue that is
based on the following criteria:
■ Outstanding job, data set, and input network requirements with a fixed satisfaction
lead time are selected.
■ The difference between the look back point and the last run point is compared with
the outage duration. If the difference is greater than the outage, then the
requirement is not marked as matching the outage. If the requirement is for a job,
the last run date/time used during initial requirement satisfaction process is carried
in the requirement segment itself. For data sets and networks, this information is
obtained from the appropriate database record.
■ The following qualifications are made only if the outage is specified as a specific
date/time range (an outage window). If the outage was specified as a simple
duration, further checks cannot be made because there is no specific outage
date/time range to reference.
■ If the deadline date and time is less than the beginning of the outage window, the
requirement is not marked as matching the outage. If the job entered the system
before the outage occurred, then it had no effect on the initial requirement
satisfaction calculations.
■ If the required element has no last run date/time, the requirement is not marked as
matching the outage. This is because now there is no date/time reference to
compare with the outage window.
■ If the look back point minus the outage duration does not reach back to some part
of the outage window, the requirement is not marked as matching the outage.

LDTM Command
Examples
This example evaluates all fixed LDTM requirements with no outage.
LDTM
This example evaluates all fixed LDTM requirements with a nonspecific eight hour
outage.
LDTM,OUTAGE=8
This example evaluates fixed LDTM requirements for jobs beginning with PAY. The
example uses an Outage window from January 16, 20yy at noon to January 18, 20yy at
2:00 p.m. as a reference.
LDTM,JOB=PAY*,OUTAGE=(0116yy,1200,0118yy,1400)
LDTM,JOB=P*,OUTAGE=5
DATE=yy.080 PAGE 0001
NAME NAME JOB# DEADLINE SUB/START DUE-OUT SPEC/RUN ID MODE REQ STATUS
P3 REQ 0792 023/1731 *NONE* 023/1731 ALL- 001 DEMD 003 LATE
-------- ------------- SATISFACTION LEAD TIME ANALYSIS ----------------------

JOB=P2 LKBK=yy019/22:31 LRUN=yy019/17:59 DIFF=000/04:32 *OUTAGE*
DSN=D463BD8.BDTEST04
DS00000004 LKBK=yy080/04:11 LRUN=yy307/11:39 DIFF=502/16:32
CREATED BY BDTEST04
Job detail line (Starts with P3)

Contains general information about the listed job. For more information about the
fields on this line, see the LQ command.
Type of requirement (JOB=)
Indicates the type of requirement.
The possible values are the following:
JOB
Job requirement
DSN
Internal data set requirement
XDSN
External data set requirement
NWK
Network requirement

LDTM Command
Name of requirement (P2)

Name of Requirement. This is the job or network name that is a requirement. For
data sets, it is the data set name that is required.
Look Back (LKBK)
Represents the point in time where CA WA CA 7 Edition stopped looking for the last
run of the required job. Requiring job queue entry date/time minus satisfaction
lead time. It is presented as YYDDD/HHMM where: YYDDD = Julian date, and hours
(HH) and minutes (MM).
Last Run (LRUN)
Represents the time when the required job last completed, or the required data set
was updated or created. It is presented as YYDDD/HHMM where: YYDDD = Julian
date, and hours (HH) and minutes (MM). If the job has never run (or data set never
created) it is presented as periods (.).
Difference (DIFF)
Provides the difference between the look back and last run times. This value
represents how much the requirement "missed" being satisfied when the job came
into the request queue. It is presented as DDD/HHMM where: DDD = number of
days (up to 999), and hours (HH) and minutes (MM). If the required job has never
run, no valid calculation can be made; therefore, the difference is presented as
periods.
*OUTAGE*
Provides an outage factor indicator. If an outage is specified on the command and
the requirement 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 NOT specified, then
ONLY requirements that match the outage criteria are listed.
DS00...
Provides a data set number. If the requirement is for a data set, the CA WA CA 7
Edition data set number is displayed.
CREATED BY
Provides a creation job. If the requirement is for an internal data set, the name of
the job that updates or creates the data set is displayed.
More information:
LQ Command (see page 443)

LGVAR Command
LGVAR Command
The LGVAR command lists information about global variables.
LGVAR[,JOB={*|jobname|mask}]
[,LIST=ALL]
[,NAME={*|variable|mask]
[,SCHID={0|nnn]
[,SYS={*|systemid|mask]
JOB
(Optional) Specifies the job name or mask.
*
Specifies all job values. This value is the default.
jobname
Defines the job name or mask for job names that uses this specified value of
this global variable.
LIST=ALL
Specifies to display the date and time the global variable was last modified and the
user ID of the one who modified it. If SECURITY,HIDEUPD=YES is specified on the CA
WA CA 7 Edition initialization start-up parameters, the user ID is not displayed, and
the field remains blank.
NAME
(Optional) Defines the global variable for which the list is intended.
*
Specifies all global variables. This value is the default.
variable
Specifies the global variable name or mask.
SCHID
(Optional) Specifies a CA WA CA 7 Edition schedule ID. The keyword has no default.
If the keyword is omitted, all schedule ID values are displayed.
0
Specifies a schedule ID value of 0 or no schedule ID value.
nnn
Defines the CA WA CA 7 Edition schedule ID that uses this specified value of
this global variable.

LGVAR Command
SYS
(Optional) Specifies the system name or mask.
*
Specifies all system values. This value is the default.
systemid
Defines the system name or mask for system names that uses this specified
value of this global variable.
More information:
Examples
The following example, with a blank keyed in, lists only variables with no JOB assigned.
LGVAR,JOB=
The following example works the same for online or batch.
LGVAR,JOB= ,NAME=*
The following example lists only variables with a JOB assigned.
LGVAR,JOB=?*
The following example lists only variables with a SYS assigned.
LGVAR,SYS=*?
The following example lists only variables with no SYS (8 blanks).
LGVAR,SYS= ,NAME=*
The following example lists all variables with no SCHID number assigned.
LGVAR,SCHID=0

LGVAR Command
LGVAR,NAME=RBJB0#
LGVAR,NAME=RBJB0#*
*** Global JCL Variables *** Assigned Prefix is &: PAGE 0001
Variable / Substitution Value Job System Schid / Val_Len
RBJB0# CA75V?0? 301

JOB?BAD31 09
RBJB0# CA75V?0?
JOB?BAD 07
RBJB0# CA7?V?0? 001
JOB?1 05
RBJB0# CA7?V?0? 301
JOB?31 06
RBJB0# CA7?V?0?
JOB? 04
SLIX-00 REQUEST COMPLETED AT 10:09:57 ON yy.ddd

Assigned Prefix is
Identifies the one- to four-character global variable prefix.
Variable
Identifies the global variable name.
Job
Identifies the job name or mask associated with the global variable name.
System
Identifies the system name or mask associated with the global variable name.
Schid
Identifies the schedule ID associated with the global variable name.
Substitution Value
Identifies the value to be substituted for the global variable name, job name,
system name, schedule ID combination.
Val_Len
Identifies the length of the substitution value.

LGVAR Command
LGVAR,NAME=RBJB0#,LIST=ALL
LGVAR,NAME=RBJB0#*,LIST=ALL
*** Global JCL Variables *** Assigned Prefix is &: PAGE 0001
Variable / Substitution Value Job System Schid / Len DateTime/User
RBJB0# CA75V?0? 301 06/13/yy 16:07

JOB?BAD31 09 CA7USER
RBJB0# CA75V?0? 06/13/yy 16:08
JOB?BAD 07 CA7USER
RBJB0# CA7?V?0? 001 06/13/yy 17:12
JOB?1 05 CA7USER
RBJB0# CA7?V?0? 301 06/14/yy 09:21
JOB?31 06 CA7MNGR
RBJB0# CA7?V?0? 06/13/yy 16:09
JOB? 04 CA7USER
SLIX-00 REQUEST COMPLETED AT 10:11:38 ON yy.ddd
This panel contains the same fields as the previous panel with the following additions.
Len
Identifies the length of the substitution value. Same as the Val_Len field in the
previous panel.
DateTime
Identifies the date and time the global variable was last modified.
User
Identifies the user ID who last modified the global variable.

LIST Command
LIST Command
The LIST command lists information about jobs in the request queue that are waiting for
a restart.
LIST[,{JOB={*|jobname|jobnumber|mask}|JOBL={*|longjobname|mask}}]
[,PROSE={NO|YES}]
JOB
(Optional) Defines the jobs in the request queue, flagged for a restart, that you
want to list. JOB and JOBL are mutually exclusive.
*
Specifies all jobs that are flagged for a restart. This value is the default.
jobname
Defines a specific job name in up to eight characters.
mask
Limits: 1 to 7 alphanumeric characters that are terminated with an asterisk.
jobnumber
Defines a specific CA 7 job number.
JOBL
(Optional) Defines the jobs in the request queue, flagged for a restart, that you
want to list. JOB and JOBL are mutually exclusive.
*
Specifies that all jobs are flagged for a restart.
longjobname
Defines a specific long job name in up to 64 characters.
mask
Defines a generic long job name.

LIST Command
PROSE
(Optional) Specifies whether to list the restart documentation (the #RESTART
segment). PROSE requires a specific job name. If multiple jobs are returned, PROSE
lists only the first job in the list. NO is the default.
Examples
LIST,JOB=*,PROSE=NO
C A - 7 J O B R E S T A R T PAGE 0001
SJR3-10 RESTART JOB SCAN.
JOBNAME CA7# LASTSTEP COMP ---DUE-OUT-- RC PROSE# COMMENTS

ACPBA01W 0025 S0000 YY.DDD/16:54 07 00000295 JCLERR RSTBL
ACPCA01W 0026 ACPCA050 C0064 YY.DDD/16:54 00 00000000 COND-CD
FXABA02M 0371 FXABA010 U0021 YY.DDD/17:00 02 00005849 RSTBL
PERAF03M 1724 PERAF200 S0013 YY.DDD/17:10 35 00019784 RSTBL
WHSAA01D 7359 WHSAA340 C0000 YY.DDD/17:30 14 00000000 REQUE RSTBL
FXAAC05D 2946 FXAAC170 C0032 YY.DDD/17:30 01 00014956 COND-CD RSTBL
SJR0-00 REQUEST COMPLETED AT 15:55:08 on yy.ddd

JOBNAME
Identifies the name of the job as defined in the database.
CA7#
LASTSTEP
Identifies the name of the last successfully executed step.
COMP
Identifies the completion code the job ended with.
DUE-OUT
Identifies the due-out date and time for this job queue record.
RC
Identifies the current restart count for this job queue record.

LIST Command
PROSE#
Identifies the DSNBR for the documentation member for this job.
COMMENTS
Identifies the reason for job failure and indicates if this job is restartable at job or
step level. Values that can appear in the COMMENTS column of LIST output are:
#STEPCC
Indicates failed step-level condition code tests based on #SCC statements
included in the JCL.
COND-CD
Indicates failed job-level condition code tests based on job definition panel
fields COND-CODE and RO.
For agent jobs (AGJOBs), the COND-CD is the condition code returned from the
agent, which is why the job failed. The executing program or the agent itself
can set this code. Check the status field returned by the agent using the
AGFILE,TYPE=INFO command.
JCLERR
Indicates terminated due to JCL error.
N-FAIL
Indicates CCI transmit failed.
N-OFFL
Indicates the node is offline.
N-STOP
Indicates node is stopped (using XNODE).
N-XTRK
Indicates CA WA CA 7 Edition tracker is not active in the CA WA CA 7 Edition job
or started task.
R-MJOB
Indicates the job was requeued because of multiple JOB statements.
REQUE
Indicates manually requeued by the user.
RSTBL
Indicates CA WA CA 7 Edition is inserting a CA WA Restart Option restart step.

LISTDIR Command
LISTDIR Command
The LISTDIR command lists the member names of any PDS accessible by CA WA CA 7
Edition. Date, time, and version of the creation or last update are shown for members
that were saved through the JCL function of DBM. This function is also offered on the UT
Menu panel as function 14.
LISTDIR,DSN=dsname[,VOL=volume][,MEM=member]
DSN
Defines the fully qualified name of the PDS data set for which you want to list
directory information.
If you are using online Base Calendar Maintenance, you can specify DSN=*SCAL* to
list calendar names residing on the CA WA CA 7 Edition calendar PDS.
If you are using the perpetual calendar feature, you can specify DSN=*PCAL* to list
the perpetual calendar data set contents residing on the CA WA CA 7 Edition
perpetual calendar PDS.
VOL
(Optional) Defines the volume on which the PDS data set resides. If omitted, the
system catalog is used to locate the PDS data set.
Default: System catalog
MEM
(Optional) Defines the starting PDS member name at which listing is to begin. If
omitted, the entire directory is listed.
Default: Entire directory

LJCK Command
Examples
LISTDIR,DSN=CA7.JCLDS1
LISTDIR,DSN=SYS1.MACLIB,MEM=OPEN
LISTDIR,DSN=CA7.JCLDS12,VOL=DSK005
LISTDIR,DSN=CAI.CA7.LOADLIB,MEM=ICMDSECT
PAGE 0001
NAME TTR SIZE ALIAS-OF AC --------- ATTRIBUTES --------
ICMDSECT 00FE20 000180 00 FO RN RU

IGCSTXXX 010017 000250 00 FO RN RU
IGCS0XXX 01001F 000EF0 00 FO RN RU
IGCS3XXX 010028 0010B8 00 FO RN RU
IGG019X7 002626 0000A0 00 FO
L2ADDON 00270F 000238 00 FO
L2B0INIT 010221 003048 01 FO
L2B0SVC 010031 000008 00 FO RN RU
L2B0SVCT 010107 000008 00 FO RN RU
L2CCICB 00CE37 000F80 00 FO
L2CCICSD 00CF09 000200 00 FO
L2CCIIN 00CF12 0003A8 00 FO
L2CCIIS 00CF1B 000560 00 FO
L2CCILET 00CF24 000240 00 FO
L2CCIRCV 00CF2D 000860 00 FO
LJCK Command
For the CPU jobs, the LJCK command lists JCL for a CA WA CA 7 Edition job. JCL is fetched
from the source indicated on the DB.1 panel. If no member name is provided on the
DB.1 panel, then the member name is assumed to be the same as the job name. 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 LJCK attempts to locate the JCL on the
override library (JCLID=254). The RMS step is inserted if necessary.
You can also use the LJCK command to validate JCL for a CPU job that is not defined on
the CA WA CA 7 Edition database. However, the JCL must reside on a CA WA CA 7
Edition JCL library. LJCK can invoke CA JCLCheck to validate the JCL.
For cross-platform jobs, the LJCK command lists information that is gathered for building
the message that is sent to the remote node or agent. Instead of listing JCL, it lists the
following kinds of information:
■ The job definition panel information
■ The destination information
■ The data that are obtained from the PARMLIB data set when one is defined for the
job.

LJCK Command
LJCK keyword values for DATE, TIME, and SCHID can affect the display when scheduled
overrides such as #JI and #JO are used. If the CA WA CA 7 Edition interface with CA
Driver is active, LJCK displays the CA Driver modifications. Calls to CA Driver are made
after scheduled overrides are applied and the RMS step is inserted. Defaults for
run-time specific reserved-name variables such as the job number are used when CA
Driver is invoked through LJCK.
LJCK displays modifications that global variables make. If CA Driver is active, the CA
Driver modifications are made before global variable modifications.
Note: For more information about the use of CA Driver, see the Interface Reference
Guide.
LJCK,{JOB=jobname|JOBL=longjobname|MEM=xxxxxxxx}
[,DATE=yyddd]
[,JCLLIB={nnn|&xxxxxxxxxxxxxx}]
[,LIST={MERGE|DEBUG|ERRORS|ONLY}]
[,SCHID={001|nnn}]
[,TIME=hhmm]
JOB
Defines the job whose JCL or cross-platform related information you want to list.
Required: Yes, unless JOBL or MEM is specified.
Limits: This keyword is mutually exclusive with the JOBL and MEM keywords.
JOBL
Defines the job whose JCL or cross-platform related information you want to list.
Required: Yes, unless MEM or JOB is specified.
Limits: This keyword is mutually exclusive with the MEM and JOB keywords.
MEM
Specifies the member whose JCL is to be listed if the CPU job is not defined to CA
WA CA 7 Edition or if the database definition is to be ignored. If no JCLLIB value is
specified, LJCK attempts to locate JCL on the JCL library defined with ID=0. If this
keyword is used, the job type is always a CPU job.
This option is not valid for internal cross-platform jobs.
Required: Yes, unless JOB or JOBL is specified.
Limits: This keyword is mutually exclusive with the JOB and JOBL keywords.

LJCK Command
DATE
(Optional) Specifies the Julian date for evaluating scheduled overrides (for example,
#JI and #JO statements).
Default: Current system date
JCLLIB
(Optional) Overrides or specifies the library where the JCL resides. JCLLIB can
override the JCLID/JCLLIB value on the DB.1 panel for this display if the JOB keyword
is used. For example, if the JCLLIB for the library where the JCL for job X resides is
&A but test JCL to be evaluated for the job resides on the library defined as
JCLLIB=&ABC, the following command can be used:
LJCK,JOB=X,JCLLIB=&ABC
If a numeric index is indicated, use from 1 to 3 numeric characters to specify a

number from 0 through 999.
If a symbolic index is indicated, specify from 1 to 15 alphanumeric characters
prefixed by an ampersand.
For internal cross-platform jobs, JCLLIB specifies the PARMLIB where cross-platform
information resides. JCLLIB can override the PARMLIB value from the job definition
panel for this display if the JOB keyword is used.
LIST
(Optional) Specifies the options used in listing JCL or cross-platform information.
MERGE
Specifies that the execution JCL for the specified job is to be evaluated by CA
JCLCheck. MERGE is the default.
If the full CA JCLCheck interface is used, then JCL substitutions, procedure
expansions, errors, and other messages returned by CA JCLCheck are displayed
inline following the relevant execution JCL statements. The display is similar to
CA JCLCheck REPORT 2. For more information about REPORT 2, see the CA
JCLCheck User Guide. If the default CA JCLCheck interface (common
component) is used, a report is produced listing only those statements in error.
This output is the same as the output generated for LIST=ERRORS.
For internal cross-platform jobs, specifies to evaluate cross-platform
information for errors. Error messages are presented inline following the
relevant cross-platform statement. If present, logon information and
miscellaneous notes are also listed for internal cross-platform jobs.

LJCK Command
DEBUG
Displays a dump of the AFM that would be sent to the remote agent during job
submission. Any passwords always display as 'SIMULATE'. The MFUser field
contains the user ID of the person executing the LJCK command. The MFUser
for an actual job submission would be determined at job submission time.
Limits: This keyword value applies to agent jobs only.
ERRORS
Specifies that the execution JCL for the specified job is to be evaluated by CA
JCLCheck, and that only those JCL statements flagged in error with the
associated diagnostic messages are to be displayed.
For internal cross-platform jobs, specifies to evaluate cross-platform
information for errors and to display only those statements flagged in error
with an associated diagnostic message.
ONLY
Specifies that the execution JCL for the specified job is to be listed. CA JCLCheck
is not invoked to evaluate the JCL. If the CA JCLCheck interface is not available,
this value is the only valid LIST option.
For internal cross-platform jobs, specifies listing cross-platform information.
The statements are not evaluated for errors.
SCHID
(Optional) Specifies the schedule ID to be used in evaluating scheduled overrides
(for example, #JI and #JO statements).
Default: 001
TIME
(Optional) Specifies the time-of-day to be used in evaluating scheduled overrides
(for example, #JI and #JO statements).
Default: Current system time
Concealed Values
Depending on the security options that are selected for your installation, the following
values are sometimes concealed in the display:

LJCL Command
LJCL Command
The LJCL command lists the JCL or PARM data for any CA WA CA 7 Edition job when the
job name is supplied. The command can access any PDS, CA Panvalet for z/OS, or CA
Librarian data sets defined to CA WA CA 7 Edition. This command lists the data set name
and the member name specified (or defaulted) on the DB.1 or DB.10 panel for each job.
Note: Any undisplayable hexadecimal characters in the JCL are shown as periods (.) in
the output from the LJCL command.
LJCL,{JOB={jobname|mask|*}|JOBL={longjobname|mask|*}}
JOB
Defines the jobs whose JCL you want to list. JOB and JOBL are mutually exclusive.
jobname
Defines a job name.
mask
*
Specifies all jobs that are defined in the database. The output from this
specification can be lengthy and is preferably done using a batch terminal.
JOBL
Defines the jobs whose JCL you want to list. JOB and JOBL are mutually exclusive.
longjobname
Defines a long job name.
mask
*
Specifies all jobs that are defined in the database. The output from this
specification can be lengthy and is preferably done using a batch terminal.

LJCL Command
Examples
This example lists JCL for job CA7JOB4.
LJCL,JOB=CA7JOB4
This example lists JCL for all jobs whose name begins with CA7.
LJCL,JOB=CA7*
This example lists JCL for all jobs.
LJCL,JOB=*
Concealed Values
Depending on the security options selected for your installation, the following values
may be concealed in the display:
LJCL Panel
LJCL,JOB=ROSDAILY
DSN=CSDCA7.JCLLIB(ROSDAILY) PAGE 0001
JOB=ROSDAILY
//ROSDAILY JOB HE67YFBH,SYSTEMS,CLASS=2,REGION=1024K,TIME=1439 00000001

//*JOBPARM LINES=9999,FORMS=DPLX 00000002
//*LOGONID @@@@@@@@ 00000003
//*PASSWORD @@@@@@@@ 00000004
//BACKUP EXEC PGM=LIBUTIL, 00000005
// PARM=BACKUP 00000006
//STEPLIB DD DSN=ROS1.ROSLIB,DISP=SHR 00000007
//SYSPRINT DD SYSOUT=A 00000008
//ROSLIB00 DD DSN=ROS1.ROSLIB00,DISP=OLD 00000009
//ROSLIB01 DD DSN=ROS1.ROSLIB01,DISP=OLD,DCB=BUFNO=56 00000010
//BACKUP DD DSN=ROS1.DAILY.BACKUP(+1),DISP=(,CATLG,UNCATLG), 00000013
// UNIT=TAPE,DCB=(CTI00.GDG,BLKSIZE=20000), 00000014
// LABEL=EXPDT=99000 00000015
// EXEC PGM=IEFBR14,COND=(6,GT,BACKUP) 00000016
//BACKUPTP DD DSN=ROS1.DAILY.BACKUP(+1),DISP=(OLD,DELETE) 00000017
/* 00000018

LJES Command
LJES Command
The LJES command displays the JES job number for all jobs submitted by CA WA CA 7
Edition that reside in the active or prior-run queues. The active queue contains
information about jobs that are currently executing, while the prior-run queue contains
information about the last successful completion of each job. For jobs that are
executing, the name of the most recently completed job step is provided. It also shows
the CPU (local or remote) on which execution occurred, start time, and other
execution-related information.
LJES[,AGENT={*|agent|mask}]
[,CLS=x]
[,JOB={*|jobname|mask|nnnn}]
[,LIST=CPU]
[,Q={ACT|PRN|*}]
[,ST=option]
AGENT
CLS

LJES Command
CPUID
Defines the CPU ID name or mask that a CPU ID must match before its information
is selected for display. For agent jobs, use AGJ. For XPJOBs use 7XPJ.
initiation record.
JOB
LIST
(Optional) Specifies to list only CPU jobs. If specified, must be LIST=CPU.
NODE
Q
(Optional) Specifies the queues from which the jobs should be listed.
ACT
Specifies only active queue job information. ACT is the default.
PRN
Specifies only prior-run queue job information. You must supply a job name or
job name mask. Jobs in the prior-run queue show a condition code value
instead of the name of the last step executed.
*
Specifies both active and prior-run queue job information. You must supply a
job name or job name mask.

LJES Command
ST
(Optional) Indicates a selection option used to determine which jobs are listed.
ABND
ARF
ARFH
ARFJ
LATE
SYS
More information:
Usage Notes
Jobs must execute on a JES system to show a JES number. For example, XPS jobs that
run on a UNIX operating system do not have a JES number.
If CA WA CA 7 Edition NCF is installed, another column, CPU LOCATION appears on the

display. The CPU LOCATION column indicates the location name in the node table for
where the job executes.

LJES Command
Examples
LJES
LJES,JOB=372
LJES,CPUID=8102
LJES,JOB=DUSAZZ01,Q=PRN
LJES
JOB=*,Q=ACT,CPUID=* DATE=yy.ddd PAGE 0001
CA-7 JES SCH CA-7 START COMPLETE ENDING/ CPU CPU

JOBNAME JOB# JOB# ID QUE DDD/HHMM DDD/HHMM LASTSTEP SPEC RUN
U7BATCH1 0080 12190 001 ACT 019/1005 019/1053 U11STEP ALL IPO1
SLIS-00 REQUEST COMPLETED AT 08:51:58 ON yy.ddd

JOBNAME
Identifies the name of the job as defined in the database. See the NAME field on the
job definition panel.
CA-7 JOB#
JES JOB#
Identifies the job number assigned by JES for this run of the job.
SCHID
queue.
CA-7 QUE
Identifies the queue name that contains the job information listed. This value is
either ACT for active queue or PRN for prior-run queue.
START
Identifies the start day (in Julian format) and the time of day that the job became
active.

LJES Command
COMPLETE
Identifies for a job in the prior-run queue, the Julian date and time of day that the
job completed on OS. For a job in the active queue, this is the time that the last step
record was recorded.
ENDING/LASTSTEP
Identifies the last step successfully executed by this job.
CPU SPEC
Identifies the specified submit data set SY number to use for job submission. ALL
indicates that this job can be submitted to any CPU. For XPJOBs, this field displays
XPJ. For agent jobs, this field displays the agent job type.
CPU RUN
Identifies the SMF identifier of the CPU that the job executed or is executing. For
XPJOBs, this field displays 7XPJ when the job begins execution. For agent jobs, this
field displays AGJ when the job begins execution.

LJOB Command
LJOB Command
The LJOB command lists job information from the database. Optional keywords and
values are used to provide such job selection criteria as the Julian date, time-of-day,
number of DD statements, and job names. Information that is displayed can include job
characteristics, scheduling parameters, interdependencies with other work, JCL,
documentation, and so forth.
Use the LJOB command to list information about jobs. If scheduling has been
intentionally suspended with a DEMAND,SET=SKP or NXTCYC command, the JOB
INFORMATION section of the list indicates NXTCYC=SKP or NXTCYC=OFF.
LJOB[,keyword=value,...][,LIST={JOB|option}]
Optional keywords and values are used to provide job selection criteria. They can be
used in any combination to list the desired jobs. LIST specifies format of display.
Keywords and acceptable values are as follows. Unless indicated, these keywords have
no defaults. If a keyword is not entered, jobs are listed regardless of that keyword's
corresponding value in the database. If no keywords are provided, all jobs in the
database are listed.
Note: For more information about most of the following keywords, see the DB.1, DB.10,
or DB.11 panels in the Database Maintenance Guide.
Generic requests can generate too many pages of output for online terminals. If so, the
message CA-7.020 results. To correct this problem, indicate a specific request.
Alternatively, use the Batch Terminal Interface.
ADATE
(Optional) Specifies to select jobs meeting minimum or (minimum,maximum) Julian
date range in the date portion of the job definition panel field DONT SCHEDULE
AFTER (YYDDD format).
minimum
Specifies to select jobs meeting minimum Julian date range.
(minimum,maximum)
Specifies to select jobs meeting minimum,maximum Julian date range.

LJOB Command
AGENT
(Optional) Specifies to select jobs with this value in the DB.11 panel field Agent.
Limits: 1 to 16 alphanumeric characters including ?, *, or both mask characters
*
Specifies all agent names. This value is the default.
agent
Defines a specific agent name.
mask pattern
Specifies all agent names matching the mask pattern.
ARFSET
(Optional) Specifies the ARFSET names to select. See the job definition panel field
ARFSET.
*
Specifies all ARFSET names. This value is the default.
arfset
Defines a specific ARFSET name.
mask pattern
Specifies all ARFSET names matching the mask pattern.
@ANY
Selects jobs with any ARFSETs defined.
@NONE
Selects jobs with no ARFSETs defined.
ATIME
(Optional) Specifies to select jobs meeting minimum or (minimum,maximum)
time-of-day range in the time portion of the job definition panel field DONT
SCHEDULE AFTER (hhmm format).
minimum
Specifies to select jobs meeting minimum time-of-day range.
(minimum,maximum)
Specifies to select jobs meeting minimum,maximum time-of-day range.

LJOB Command
BDATE
date range in the date portion of the job definition panel field DONT SCHEDULE
BEFORE (YYDDD format).
minimum
(minimum,maximum)
BTIME
time-of-day range in the time portion of the job definition panel field DONT
SCHEDULE BEFORE (hhmm format).
minimum
(minimum,maximum)
CLS
(Optional) Specifies to select jobs with this value in the job definition panel field
CLASS/WLBClass.
Limits: 1 alphanumeric character from A to Z or 0 through 9
x
Specifies the class value of the job to select.
COND
numeric value range in the job definition panel field COND-CODE (nnnn format).
minimum
Specifies to select jobs meeting minimum numeric value range.
(minimum,maximum)
Specifies to select jobs meeting minimum,maximum numeric value range.

LJOB Command
CPU
numeric percentage value range for CPU time as a percentage of elapsed time (nn
format).
minimum
Specifies to select jobs meeting minimum numeric percentage value range.
(minimum,maximum)
Specifies to select jobs meeting minimum,maximum numeric percentage value
range.
CPUTIME
numeric value range in the job definition panel field CPU-TIME.
Limits: 5 numeric characters specified as mmmss, where mmm is minutes and ss is
seconds
minimum
(minimum,maximum)
DDS
numeric value range for number of DD statements in its JCL (nnn format).
minimum
(minimum,maximum)
DRCLASS
(Optional) Specifies the DRCLASS names to select. See the job definition panel field
DRCLASS.
*
Specifies all DRCLASS names. This value is the default.
drclass
Defines a specific DRCLASS name.

LJOB Command
mask pattern
Specifies all DRCLASS names matching the mask pattern.
@ANY
Selects jobs with any DRCLASS.
@NONE
Selects jobs with no DRCLASS.
DSNLEAD
numeric value range in the job definition panel field LEAD-TIME DSN (nn format).
minimum
(minimum,maximum)
DSNMSG
(Optional) Specifies to select jobs with this value if the job definition panel field DSN
NOT FOUND. The value must be N or Y.
ELT
numeric value range in the job definition panel field CLOCK-TIME (hhmm format).
minimum
(minimum,maximum)
EXEC
(Optional) Selects jobs with this value in the job definition panel field EXEC. The
value must be N or Y.
HOLD
(Optional) Selects jobs with this value in the job definition panel field HOLD. The
JCLID
(Optional) Selects jobs with this value in the job definition panel field JCL ID.
Limits: 1 to 3 numeric characters. The valid range is from 0 through 999.

LJOB Command
JCLLIB
JCLLIB.
Limits: 2 to 16 alphanumeric characters beginning with an ampersand (&)
JCLOVRD
JCL-OVRD. The value must be N or Y.
JOB
(Optional) Specifies job names to select. See the job definition panel field JOB. JOB
and JOBL are mutually exclusive.
*
Specifies all job names. This value is the default.
jobname
mask pattern
Specifies all job names matching the mask pattern.
JOBL
(Optional) Specifies long job names to select. See the job definition panel field JOBL.
JOB and JOBL are mutually exclusive.
*
Specifies all job names. This value is the default.
jobname
Defines a specific long job name.
mask pattern
Specifies all long job names matching the mask pattern.
Note: You can use a mask pattern of JOBL=?* to list all of the jobs with a long job
name.

LJOB Command
JOBLEAD
numeric value range in the DB.1 panel field LEAD-TIME JOB (nn format).
minimum
(minimum,maximum)
JOBNET
(Optional) Specifies the JOBNET names to select. See the job definition panel field
JOBNET.
Limits: 1 to 8 alphanumeric characters including , *, or both mask characters
*
Specifies all JOBNET names.
jobnet
Defines a specific JOBNET name.
mask pattern
Specifies all JOBNET names matching the mask pattern.
LATES
numeric value range of the number of times the job completed later than
scheduled due-out time (nnn format).
minimum
(minimum,maximum)

LJOB Command
LIST
(Optional) Specifies the information to listed for each job that the other keywords
select. If LIST is not specified on a generic request, a single line describing each job
is output.
JOB
Specifies the job data only. JOB is the default.
AGJOB
Specifies the agent information only.
ALL
Specifies all data related to the job (for example, schedules, documentation,
steps, DDs, requirements, networks).
DEPJ
Specifies the jobs that are dependent on the job.
NODD
Specifies like ALL but excludes STEPDD information.
PROS
Specifies the documentation information only.
RQDSN
Specifies the data set requirement information only.
RQEXCP
Specifies the exception requirements only (NEXT-RUN=SKIP or ONLY).
RQJOB
Specifies the job requirement information only.
RQMT
Specifies the input requirements and output network information only.
RQNWK
Specifies the input network requirements only.
RQUSR
Specifies the user requirements only.
RQVRM
Specifies the virtual resource requirements only.
SCHD
Specifies the schedule information only.

LJOB Command
STEPDD
Specifies the job, step, and DD statement information.
TRIG
Specifies all jobs, data sets, and networks that trigger the job, and all jobs that
the job triggers.
XPJOB
Specifies XPJOB information only.
LMNTDATE
(Optional) Selects jobs meeting minimum or (minimum,maximum) Julian date range
for the date of last maintenance update to the database (YYDDD format).
minimum
(minimum,maximum)
Selects jobs meeting minimum,maximum Julian date range.
LMNTTIME
(Optional) Selects jobs meeting minimum or (minimum,maximum) time-of-day
range for time-of-day of last maintenance update to the database (hhmm format).
minimum
Selects jobs meeting minimum time-of-day range.
(minimum,maximum)
Selects jobs meeting minimum,maximum time-of-day range.
LMNTTYPE
(Optional) Selects jobs depending on the type of last database maintenance
performed on them. The possible values are the following:
ANLZ
Specifies last maintenance by CA WA CA 7 Edition analyze commands.
DBM
Specifies last maintenance by CA WA CA 7 Edition database maintenance
facilities.
LOAD
Specifies last maintenance by CA WA CA 7 Edition LOAD process.
SMF
Specifies last maintenance by System Management Facility feedback.

LJOB Command
LRUNDATE
date range for date of the last run of the job (YYDDD format).
minimum
(minimum,maximum)
LRUNTIME
time-of-day range for time-of-day of the last run of the job (hhmm format).
minimum
(minimum,maximum)
LTERM
LTERM. The value is a logical terminal name.
MAINID
(Optional) Specifies to select the CPU jobs with this value in the job definition panel
field MAINID or internal cross platform jobs according to the job type.
AGJ
Select all the agent jobs.
ALL
Select the CPU jobs with MAINID=ALL.
SYn
Select the CPU jobs with MAINID=SYn (n is 1 through 7).
/SYn
Select the CPU jobs with MAINID=/SYn (not MAINID SYn, n is 1 through 7).
XPJ
Select all the XPJOB jobs.
xxxx
Select all agent jobs with the job type xxxx.

LJOB Command
MAINT
(Optional) Specifies to select jobs with this value in the DB.1 panel field MAINT. The
MEMBER
(Optional) Specifies member names to select. See the job definition panel field
Member.
*
Specifies all member names. This value is the default.
member
Defines a specific member name.
mask pattern
Specifies all member names matching the mask pattern.
MSGCLASS
(Optional) Specifies to select jobs with this value in the DB.1 panel field MSGCLASS.
The value must be a 1 alphanumeric character message class.
NODE
(Optional) Specifies node names to select. See the DB.10 panel field XP Node.
*
Specifies all node names. This value is the default.
member
Defines a specific node name.
mask pattern
Specifies all node names matching the mask pattern.
NXTCYC
(Optional) Specifies to select jobs with DEMAND,SET=SKP or NXTCYC command
functions active.
OFF
Specifies that scheduling has been discontinued.
SKP
Specifies skip only the next scheduled run.

LJOB Command
OVRDLIB
(Optional) Specifies to select jobs with this value in the DB.1 panel field
USE-OVRD-LIB. The value must be N or Y.
OWNER
(Optional) Specifies owner values to select. See the job definition panel field
OWNER.
*
Specifies all owner values. This value is the default.
owner
Defines a specific owner value.
mask pattern
Specifies all owner names matching the mask pattern.
PARMLIB
(Optional) Specifies to select jobs with this value in the DB.10 or DB.11 panel field
PARMLIB.
Limits: PARMLIB can be one of the following values:
1 to 3 numeric characters. The valid range is from 0 to 999.
2 to 16 alphanumeric characters beginning with an ampersand (&)
PROMPTS
PROMPTS. The value must be N or Y.
PROSE
(Optional) Specifies to select jobs that have documentation that is defined through
the DB.4.1 panel. The value must be N or Y.
PRTY
numeric value range (nnn format) in the job definition panel field PRTY/WLBPRTY.
minimum
(minimum,maximum)

LJOB Command
REGION
numeric value range in the DB.1 panel field REGION (nnnn format).
minimum
(minimum,maximum)
RELOAD
(Optional) Specifies to select jobs with this value in the DB.1 panel field RELOAD.
The value must be N, Y, or X.
RESTARTS
numeric value range of the number of times the job has been restarted (nnn
format).
minimum
(minimum,maximum)
RETAIN
RETAIN-JCL. of the job definition panel field The value must be N or Y.
RMS
(Optional) Specifies to select jobs with this value in the DB.1 panel field
INSERT-RMS. The value must be N or Y.
RO
(Optional) Specifies to select jobs with this value in the job definition panel field RO.
The value must be one to two alphanumeric characters.
RQLIST
REQUIREMENT-LIST. The value must be N or Y.
RQMTMSG
RQMTS NOT USED. The value must be N or Y.

LJOB Command
RUNS
numeric value range of the number of times the job has been executed (nnnn
format).
minimum
(minimum,maximum)
SCHEDULE
(Optional) Specifies to select jobs that have a calendar schedule defined. The value
must be N or Y.
STEPREST
(Optional) Specifies to select jobs that can be restarted at the step level. The value
must be N or Y.
STEPS
numeric value range of the number of job steps in its JCL (nnn format).
minimum
(minimum,maximum)
SYS
(Optional) Specifies system names to select. See the job definition panel field
SYSTEM.
*
Specifies all system names. This value is the default.
system
Defines a specific system name.
mask pattern
Specifies all systems matching the mask pattern.

LJOB Command
TP1
numeric value range for the number of TYPE1 tape drives (nnn format). See the
DB.1 panel field TAPE DRIVES. Selection is based on TYPE1 M value unless TYPE1 M
is zero or less than for the specified TP1 minimum value; selection is then based on
TYPE1 C value.
minimum
(minimum,maximum)
TP1C
numeric value range in the DB.1 panel field TYPE1 C (nnn format).
minimum
(minimum,maximum)
TP1M
(Optional) Same as TP1C keywords except values are for the field TYPE1 M.
minimum
(minimum,maximum)
TP2
(Optional) Same as TP1 keywords except values are for TYPE2 tape drives.
minimum
(minimum,maximum)

LJOB Command
TP2C
(Optional) Same as TP1C keywords except values are for the field TYPE2 C.
minimum
(minimum,maximum)
TP2M
(Optional) Same as TP1M keywords except values are for the field TYPE2 M.
minimum
(minimum,maximum)
TZ
(Optional) Controls whether to normalize a job's last run date/time to the time zone
of the running CA WA CA 7 Edition.
statement.
CA7
Defines that the last run date/time should be normalized to the running CA WA
CA 7 Edition time zone.
EXEC
Defines that the last run date/time should be in the execution time zone.
USERID
UID.
VERIFY
(Optional) Used to select jobs with this value in the job definition panel field VERIFY.
The value must be N or Y.
More information:

LJOB Command
Examples
This example lists all information about a single job.
LJOB,JOB=CA7JOB1,LIST=ALL
This example lists all jobs in network WEEKLYS with system PAYROLL.
LJOB,JOBNET=WEEKLYS,SYS=PAYROLL
This example lists all jobs with names beginning with CA7. Even though only one line per
job is listed for any generic job name request, the output from this type of request could
be quite lengthy and should be done using a batch terminal.
LJOB,JOB=CA7*
This example lists all jobs with output network information and input requirements.
Even though only one line per job is listed for any generic job name request, the output
from this type of request could be quite lengthy and should be done using a batch
terminal.
LJOB,JOB=*,LIST=RQMT
LJOB,JOB=*
JOB=* DATE=YY.DDD PAGE 0001
JOB ----JCL---- SYSTEM USR MAIN PROSE SCHED --NUMBER OF- LAST-RUN
NAME ID MEMBER -NAME- -ID -ID- DSNBR STP DDS RUNS DATE/TIME
DUSAXX01 000 DUSAXX01 PAYROLL 000 ALL 000026 YES 004 012 0001 YYDDD/1430
PERAA01A 000 PERAA01A PERSONEL 000 ALL *NONE* NO 003 010 0000 00000/0000
PERAB01A 000 PERAB01A PERSONEL 000 ALL *NONE* NO 001 004 0000 00000/0000
PERAC01A 000 PERAC01A PERSONEL 000 ALL *NONE* YES 005 017 0001 YYDDD/1410
ACPBA01W 001 ACPBA01W PAYABLES 000 ALL *NONE* NO 004 012 0001 YYDDD/1411
ACPCA01W 001 ACPCA01W PAYABLES 000 ALL *NONE* NO 003 009 0001 YYDDD/1411
ACPCA0XW 001 ACPCA0XW PAYABLES 000 ALL *NONE* NO 002 008 0107 YYDDD/1415+

LJOB Command
LJOB,LIST=JOB Panel
LJOB,JOB=DUSAXX01,LIST=JOB
JOB=DUSAXX01 LIST=JOB DATE=YY.DDD PAGE 0001
DUSAXX01 000 DUSAXX01 PAYROLL 100 /SY3 000009 YES 003 012 0073 YYDDD/1330+
(LongDUSAXX01)
--------------------------- JOB INFORMATION ---------------------------

N -- SCHD RESOLUTION REQUIRED Y -- LOAD STEP TO BE EXECUTED
N -- OVERRIDE OF JCL REQUIRED N -- JOB MARKED AS MAINT ONLY
N -- MANUAL VERIFICATION REQD N -- JOB SET FOR HOLD IN REQQ
Y -- REQUIREMNTS TO BE LISTED N -- COMP TRIGGERS OTHER JOBS
Y -- AUTO-GENERATION OF 7 RMS Y -- JOB ELIGIBLE FOR PROMPTS
Y -- ERRORS FOR RQMT NOT USED Y -- JOB SET FOR EXEC on MAIN
Y -- ERRORS FOR DSN NOT FOUND N -- JCL TO BE KEPT IN PRRN/Q
. LAST RUN: CA 7=YY.DDD 13:30:24 EXEC=YY.DDD 14:30:24 EXEC TZO=-05:00
. OWNER= USERID JCLLIB= *NUMERIC JCLID* ARFSET= *NONE*
. LAST MAINTENANCE on YY.DDD AT HH:MM:SS VIA DBM BY OPERATOR:USERID
. JCL SET FOR RETRIEVAL FROM OVERRIDE LIB FOR NEXT RUN
. CLASS=,MSGCLASS=B,REGION=040K,PRTY=02,CPUTM=00001,ELAPTM=0009
. TAPE1: CALC=000,MANL=000,TAPE2: CALC=000,MANL=000,DRCLASS= *NONE*
. LTERM=CONTROL,JOBNET=PAYWEEK1,NXTCYC=SKP
. DONT SCHEDULE BEFORE YYDDD AT 0800 AND AFTER YYDDD AT 2300
. CONSIDER ABNORMAL END IF ..text..
. SATISFACTION LEAD TIME (HRS): JOB=01 DSN=00
. # OF TIMES LATE = 0000 # OF TIMES RESTARTED = 0000
Note: All lines may not display, and a page break may occur between the lines.

JOB NAME
Identifies the name defined in the database for this job.
JCL ID
Identifies the numeric INDEX assigned to the JCL statement that defines the data
set in which this member resides. ID=255 indicates that a symbolic INDEX is
assigned to the JCL statement that defines the data set in which this member
resides.
JCL MEMBER
Identifies the member name of the JCL that is executed by this job.

LJOB Command
SYSTEM NAME
Identifies the value from the SYSTEM field on the DB.1 panel.
USR ID
Identifies the value from the UID field on the DB.1 panel.
MAIN ID
Identifies the value from the MAINID field on the DB.1 panel.
PROSE DSNBR
Identifies the CA WA CA 7 Edition generated DSNBR for the job documentation
defined for this job.
SCHD
Identifies whether the job has any schedules.
NUMBER OF STP
Identifies the number of steps executed within this job.
NUMBER OF DDS
Identifies the number of DDs referenced by this job.
NUMBER OF RUNS
Identifies the number of times this job has successfully executed under CA WA CA 7
Edition.
LAST RUN DATE/TIME
Identifies the last date/time (start date/time) that the job ran successfully under CA
WA CA 7 Edition. A plus sign displayed immediately after the field indicates that
job's last run date/time is normalized to the time zone of the running CA WA CA 7
Edition.
Note: If a job has a long job name, that name appears immediately before the Job
Information line. If not, the line is empty.

LJOB Command
JOB INFORMATION
All job information values are either Y or N.
SCHD RESOLUTION REQUIRED
Identifies whether this job's schedule information entered through the DB.2.1
panel needs to be RESOLVed.
OVERRIDE OF JCL REQUIRED
Identifies whether the QJCL requires modifying before job submission (see
JCL-OVRD field on the DB.1 panel).
MANUAL VERIFICATION REQD
Identifies whether this job has an initial requirement in the request queue for
verification (see VERIFY field on the DB.1 panel).
REQUIREMENTS TO BE LISTED
Identifies whether this job's requirements should be written to the LTERM
indicated on the DB.1 panel upon initial queue entry.
AUTO-GENERATION OF 7 RMS
Identifies whether CA WA CA 7 Edition is to insert the RMS step (see
INSERT-RMS field on the DB.1 panel).
ERRORS FOR RQMT NOT USED
Identifies whether an error message should be produced and sent to the
LTERM specified on the DB.1 panel if this job shows to use a data set, but while
the job was executing, CA WA CA 7 Edition did not receive SMF data indicating
its use (see RQMTS NOT USED field on the DB.1 panel).
ERRORS FOR DSN NOT FOUND
LTERM specified on the DB.1 panel if CA WA CA 7 Edition receives SMF data
from this job's execution for a data set that is not referenced by the job's
database record (see DSN NOT FOUND field on the DB.1 panel).
LOAD STEP TO BE EXECUTED
Identifies whether this job should go through load processing the next time it is
to be executed.
JOB MARKED AS MAINT ONLY
Identifies whether this job is to run as a maintenance job (see MAINT field on
the DB.1 panel).

LJOB Command
JOB SET FOR HOLD IN REQQ

Identifies whether the job should enter the request queue with an initial hold
requirement (see HOLD field on the DB.1 panel).
COMP TRIGGERS OTHER JOBS
Identifies whether this job's successful completion triggers other jobs into CA
WA CA 7 Edition.
JOB ELIGIBLE FOR PROMPTS
Identifies whether the LTERM (from the DB.1 panel) is notified on a timer basis
should this job become late or need restarting (see PROMPTS field on the DB.1
panel).
JOB SET FOR EXEC on MAIN
Identifies whether this is an executable job (see EXEC field on the DB.1 panel).
JCL TO BE KEPT IN PRRN/Q
Identifies whether on successful completion should a copy of the JCL that was
submitted for this job be kept (see RETAIN-JCL field on the DB.1 panel).
LAST RUN.
Last date/time (start time) the job ran successfully under CA WA CA 7 Edition. This
line is generated only if job EXEC time is different from CA7 time.
LAST RUN. CA 7.
The date/time is normalized to the time zone of the running CA WA CA 7 Edition.
LAST RUN. EXEC.
The execution time zone date/time.
EXEC TZO.
Time zone offset (TZO) from UCT of the site where the job ran. To determine the
TZO of the local CA WA CA 7 Edition, issue a /DISPLAY,ST=CA7 command.
Note: Agent jobs are always normalized to the CA WA CA 7 Edition time zone
through the CA Integrated Agent Services (CA IAS) interface.
OWNER
The security user ID associated with this job (see OWNER field on the DB.1 panel).
JCLLIB.
The symbolic INDEX assigned to the JCL statement that defines the data set in which
this member resides. JCLLIB= *NUMERIC JCLID* indicates that a numeric INDEX is
resides.

LJOB Command
ARFSET.
The name of the ARFSET used on this job.
LAST MAINTENANCE ON…
The date and time of the last maintenance performed on this job through CA WA
CA 7 Edition and the mode for this maintenance. Mode is indicated after VIA as one
of the following:
■ DBM - for updating of this record through the DBM panel.
■ LOAD - for updating of this record by the load of a job.
JCL SET FOR…
The job's JCL is obtained from the override library for the next scheduled (or
triggered) run.
CLASS.
Workload balancing class to be used for job submission (see CLASS 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 upon initial queue
entry.
CPUTM.
CPU time (weighted average) for this job.
ELAPTM.
Time (weighted average) between job submission and job termination.
TAPE1. CALC
High-water mark number of TYPE1 tape drives used by any step within this job as
calculated by CA WA CA 7 Edition.
TAPE1. MANL.
Override of the CA WA CA 7 Edition calculated number of TYPE1 tape drives used by
this job (see TAPE DRIVES TYPE1 M field on DB.1 panel).
TAPE2. CALC.
High-water mark number of TYPE2 tape drives used by any step within this job as
calculated by CA WA CA 7 Edition.

LJOB Command
TAPE2. MANL.
Override of the CA WA CA 7 Edition calculated number of TYPE2 tape drives used by
this job (see TAPE DRIVES TYPE2 M field on DB.1 panel).
DRCLASS.
The disaster recovery class assigned to this job.
LTERM.
The logical terminal (STATION) that is to receive various messages 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 been suspended by the
NXTCYC command, this value is SKP (for single cycle) or OFF (for all cycles until reset
by the NXTCYC command).
DONT SCHEDULE BEFORE...
Dates and times to be resolved at the time a job record is to be brought into the
request queue by schedule scan or a trigger (see the DONT SCHEDULE -- BEFORE
and AFTER fields on the DB.1 panel). A job is not brought in automatically if it is a
true condition.
CONSIDER ABNORMAL END IF...
Condition code tests to be performed to determine if the job has completed
successfully.
SATISFACTION LEAD TIME...
Initial satisfaction lead time values for job and data set requirements. (See the
SATISFACTION LEAD TIME field on the DB.1 panel.)
# OF TIMES LATE…
Number of times the job has been considered late, and the number of times the job
has been restarted.

LJOB Command
LJOB,LIST=SCHD Panel
LJOB,JOB=DUSAXX01,LIST=SCHD
JOB=DUSAXX01 LIST=SCHD DATE=YY.DDD PAGE 0001
DUSAXX01 000 DUSAXX01 PAYROLL 000 /SY3 000009 YES 003 012 0073 YYDDD/0826
------------------------------ SCHEDULES ------------------------------

LAST RESOLV ON yy.ddd AT 16:42
CALENDAR SCALyy03
ID=001 ROLL=D INDEX=+000
SCAL= DOTM=0800 LEADTM=0130 STARTM=0630
WEEKLY DAY=MON,FRI
SCAL=7D DOTM=1200 LEADTM=0100 STARTM=1100
DAILY
SLIA-00 REQUEST COMPLETED AT 16:00:05 on yy.ddd
LJOB,LIST=PROS Panel
LJOB,JOB=DUSAXX01,LIST=PROS
JOB=DUSAXX01 LIST=PROS DATE=YY.DDD PAGE 0001
---------------------------------- PROSE -------------------------------

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 AS INPUT, CREATES A DATASET CA7.TEST1 AS
OUTPUT AND DEMANDS THE NEXT JOB DUSAXX02 TO BE STARTED.
LJOB,LIST=TRIG Panel
LJOB,JOB=DUSATAPE,LIST=TRIG
JOB=DUSAXX01 LIST=TRIG DATE=YY.DDD PAGE 0001
----------------- TRIGGERED BY JOBS/DATASETS/NETWORKS -----------------

JOB=DUSATPRM SCHID=000 QTM=0100 LEADTM=0010 SUBMTM=0000
------------------------- TRIGGERED JOBS ------------------------------

JOB=DUSATGDG SCHID=000 QTM=0100 LEADTM=0010 SUBMTM=0000

LJOB Command
LJOB,LIST=STEPDD Panel
LJOB,JOB=DUSAXX01,LIST=STEPDD
JOB=DUSAXX01 LIST=STEPDD DATE=YY.DDD PAGE 0001
------------------------- STEP AND DD INFORMATION----------------------

01 STEP1 PGM=IEBGENER REGION=000K TIME=1439,00 PSTEP=S1 **RST**
001 SYSIN TYPE=DUMMY
002 SYSPRINT TYPE=SYSOUT
LJOB,LIST=RQMT Panel
LJOB,JOB=DUSAXX01,LIST=RQMT
JOB=DUSAXX01 LIST=RQMT DATE=YY.DDD PAGE 0001
------------------ REQUIREMENTS AND NETWORK CONNECTIONS -----------------

NWK=TESTOTNW SCHID=000 NWKSCHID=001 LEADTM=0100
SUBID=RPT1205 DESC=BENEFITS ** OUTPUT **
DSN=CA7.LOADLIB **** PERM DSN ****
DSNBR=DS00000004 SCHID=000 VRSN=YY135/1940
CREATED BY **NONE**
USR=SAMPLE USER REQUIREMENT
SCHID=000

LJOB Command
LJOB,SYS=A/P,LIST=DEPJ Panel
LJOB,SYS=A/P,LIST=DEPJ
JOB=* LIST=DEPJ DATE=YY.DDD PAGE 0002
JOB01 000 JOB01 A/P 000 ALL 000000 NO 000 000 0000 00000/0000
JOB02 000 JOB02 A/P 000 ALL 000000 NO 000 000 0000 00000/0000
JOB03 000 JOB03 A/P 000 ALL 000000 NO 000 000 0000 00000/0000
-------------------------- SUCCESSOR JOBS ------------------------

JOB=JOB05 SCHID=001
JOB=JOB08 SCHID=002
JOB05 000 JOB05 A/P 000 ALL 000000 NO 000 000 0000 00000/0000
JOB06 000 JOB06 A/P 000 ALL 000000 NO 000 000 0000 00000/0000
-------------------------- SUCCESSOR JOBS ------------------------

JOB=JOB13 SCHID=000
LJOB,LIST=ALL Panel for an XPJOB Job
LJOB,JOB=CA07XPQ1,LIST=ALL
JOB=CA07XPQ1 LIST=ALL DATE=YY.DDD PAGE 0001
CA07XPQ1 255 CA07XPQ1 QAXPSYS 000 XPJ *NONE* NO 000 000 0005 06289/0949
--------------------------- JOB INFORMATION ---------------------------

N -- SCHD RESOLUTION REQUIRED N -- JOB SET FOR HOLD IN REQQ
N -- MANUAL VERIFICATION REQD Y -- COMP TRIGGERS OTHER JOBS
Y -- REQUIREMNTS TO BE LISTED Y -- JOB ELIGIBLE FOR PROMPTS
Y -- ERRORS FOR RQMT NOT USED Y -- JOB SET FOR EXEC ON MAIN
Y -- PRM TO BE KEPT IN PRRN/Q Y -- UNIX SWITCH USER CMD SU-
. OWNER= *NONE* PRMLIB=&EROCJCL ARFSET= *NONE*

. LAST MAINTENANCE ON yy.278 AT 12:36:05 VIA DBM BY OPERATOR: MASTER
. CLASS=A,PRTY=000,CPUTM=00001,ELAPTM=0004,DRCLASS= *NONE*
. LTERM=MASTER
. # OF TIMES LATE = 0000 # OF TIMES RESTARTED = 0000
SLIA-00 REQUEST COMPLETED AT 14:07:08 ON yy.ddd

LJOB Command

JOB NAME
JCL ID
Identifies the numeric INDEX assigned to the JCL statement that defines the data
set in which this member resides. ID=255 indicates that a symbolic INDEX is
resides.
JCL MEMBER
Identifies the member name of the JCL that is executed by this job.
SYSTEM NAME
Identifies the value from the SYSTEM field on the DB.10 panel.
USR ID
Identifies the value from the UID field on the DB.10 panel.
MAIN ID
Specifies the value XPJ to represent an XPJOB.
PROSE DSNBR
SCHD
NUMBER OF STP
NUMBER OF DDS
NUMBER OF RUNS
Edition.
LAST RUN DATE/TIME
Identifies the last date/time (start date/time) that the job ran successfully under CA
WA CA 7 Edition. A plus sign displayed immediately after the field indicates that
job's last run date/time is normalized to the time zone of the running CA WA CA 7
Edition.

LJOB Command
JOB INFORMATION
All job information values are either Y or N.
SCHD RESOLUTION REQUIRED
Identifies whether this job's schedule information entered through the DB.2.1
panel needs to be RESOLVed.
MANUAL VERIFICATION REQD
Identifies whether this job has an initial requirement in the request queue for
verification (see VERIFY field on the DB.10 panel).
REQUIREMNTS TO BE LISTED
Identifies whether this job's requirements should be written to the LTERM
indicated on the DB.10 panel upon initial queue entry.
ERRORS FOR RQMT NOT USED
LTERM specified on the DB.10 panel if this job shows to use a data set, but
while the job was executing, CA WA CA 7 Edition did not receive SMF data
indicating its use (see RQMTS NOT USED field on the DB.10 panel).
PRM TO BE KEPT IN PRRN/Q
Identifies whether on successful completion to keep a copy of the data sent to
the destination node (see RETAIN on the DB.10 panel).
JOB SET FOR HOLD IN REQQ
Identifies whether the job should enter the request queue with an initial hold
requirement (see HOLD field on the DB.10 panel).
COMP TRIGGERS OTHER JOBS
Identifies whether this job's successful completion triggers other jobs into CA
WA CA 7 Edition.
JOB ELIGIBLE FOR PROMPTS
Identifies whether the LTERM (from the DB.10 panel) is notified on a timer
basis should this job become late or need restarting (see PROMPTS field on the
DB.10 panel).
JOB SET FOR EXEC on MAIN
Identifies whether this is an executable job (see EXEC field on the DB.10 panel).
UNIX SWITCH USER CMD SU-
Identifies whether to execute the UNIX Switch User command (see SUTYPE on
the DB.10 panel).

LJOB Command
OWNER.
Identifies the security user ID associated with this job (see OWNER on the DB.10
panel).
PRMLIB.
Identifies the data set identifier, either numeric or symbolic, in which the member
associated with this job resides. If *NONE*, the XPJOB job has no external
parameters.
ARFSET.
Identifies the name of the ARFSET used on this job.
LAST MAINTENANCE ON...
Identifies the date and time of the last maintenance performed on this job through
CA WA CA 7 Edition and the mode for this maintenance. Mode is indicated after VIA
as one of the following:
■ DBM - for updating of this record through the DBM panel.
■ SMF - for updating that occurred through SMF data.
CLASS.
Identifies the workload balancing class to be used for job submission (see CLASS
field on the DB.10 panel).
PRTY.
Identifies the initial workload balancing priority that is assigned to this job upon
initial queue entry.
CPUTM.
Identifies the CPU time (weighted average) for this job.
ELAPTM.
Identifies the time (weighted average) between job submission and job
termination.
DRCLASS.
The disaster recovery class assigned to this job.
LTERM.
Identifies the logical terminal (STATION) that is to receive various messages
regarding this job.
# OF TIMES…
Identifies the number of times the job has been considered late, and the number of
times the job has been restarted.

LJOB Command
LJOB,LIST=XPJOB Panel
LJOB,JOB=CA07XPQ2,LIST=XPJOB
JOB=CA07XPQ2 LIST=XPJOB DATE=YY.DDD PAGE 0001
CA07XPQ2 000 QAXPSYS 000 XPJ *NONE* NO 000 000 0004 yy289/0955
------------------------- XPJOB INFORMATION -------------------------

Node: EROCTST
Exec: cau9test
PARM: t=60
Trace: N
LJOB,LIST=AGJOB Panel
LJOB,JOB=CA7ESP01,LIST=AGJOB
JOB=CA7ESP01 LIST=AGJOB DATE=YY.DDD PAGE 0001
CA7ESP01 200 CA7ESP01 CA7SYS01 000 WIN *NONE* NO 000 000 0001 yy043/1217
------------------------- AGENT INFORMATION -------------------------

Job Type: NT_JOB
Agent : USER023ESP
Userid : usero23

LJOBR Command
LJOBR Command
The LJOBR command lists computer resource requirement information about jobs. This
command is similar to the LQR command, except that it lists resource information about
any job in the database.
LJOBR[,keyword=value,...]
Optional keywords and values are used to specify the jobs to list. Only the jobs meeting
all selection criteria that is specified are shown. LJOBR uses the same selection
keywords and values as the LJOB command.
LJOBR has no LIST option.
More information:
LJOB Command (see page 370)
Usage Notes
This command can also be used to determine all jobs that have specific resource
requirements or ranges of requirements. Resource parameters can be specified in any
combination to obtain the selected information. This makes the command very useful in
analyzing profiles of the CA WA CA 7 Edition workload.
Examples
LJOBR,TP1=(05,10),SYS=BL*
LJOBR,TP1=(05,10),TP2=3,CPU=50
LJOBR,CLS=A,ELT=(0050,0101)
LJOBR,JOBNET=WEEKLYS,SYS=PAYROLL,TP1=(02,05)
LJOBR,JOB=D463XX01
JOB=D463XX01 DATE=YY.DDD PAGE 0001
JOB SYSTEM MAIN JOB CPU/ELAPS TAPE1 TAPE2 NBR REGN CPU% LAST-RUN
NAME -NAME- -ID- C/PRT --TIME--- M/CAL M/CAL RUNS SIZE UTIL DATE/TIME
D463XX01 TESTNTWK ALL A/002 00001/0001 00/00 00/00 0002 0040K 01.67 09234/1416

LJOBR Command

JOB NAME
SYSTEM NAME
Identifies the value from the SYSTEM field on the job definition panel.
MAIN ID
■ For CPU jobs, identifies the value from the MAINID field on the DB.1 panel.
■ For internal cross platform jobs, displays the job type for agent jobs or XPJ for
XPJOB jobs.
JOB C/PRT
CPU/ELAPS TIME
Identifies the CPU time for the job in mmmss format and the elapsed run time
(CLOCK-TIME from the job definition panel) in hhmm format.
TAPE1 M/CAL
Identifies the number of tape drives used under TAPE1. The M field represents a
manual override made on the DB.1 panel. The CAL field is the number of tape drives
used that was calculated either by LOAD processing or a RESANL command. Both
the M and CAL fields can contain up to three digits. Space limitations on the line
only permit us to display the rightmost two digits.
TAPE2 M/CAL
Identifies the number of tape drives used under TAPE2. The M field represents a
manual override made on the DB.1 panel. The CAL field is the number of tape drives
used that was calculated either by LOAD processing or a RESANL command. Both
the M and CAL fields can contain up to three digits. Space limitations on the line
only permit us to display the rightmost two digits.
NBR RUNS
Edition.

LLIB Command
REGN SIZE
Identifies the region required for this job.
CPU% UTIL
Identifies the percentage of the time that a job was getting actual CPU time during
execution.
LAST RUN DATE/TIME
Identifies the last time (start time) that the job ran successfully under CA WA CA 7
Edition.
LLIB Command
The LLIB command lists a member of a CA Panvalet for z/OS or CA Librarian data set.
Although intended to be used for reviewing JCL, any card-image data can be displayed
from either of the two types of data sets.
Note: Any undisplayable hexadecimal characters in the member are shown as periods (.)
in the output from the LLIB command.
LLIB,DSN=dsname,MEM=member[,LIST=N]
DSN
Defines the fully qualified data set name of the CA Panvalet for z/OS or CA Librarian
library that contains the member (MEM) to be listed.
MEM
Defines which member of the named library (DSN) to list.
LIST
(Optional) Specifies not to expand "includes." The only permitted value is N for no
expansion.

LLIB Command
Examples
This example expands "includes".
LLIB,DSN=PROD1.JCL,MEM=XXXXXXXX
This example does not expand "includes".
LLIB,DSN=PROD1.JCL,MEM=XXXXXXXX,LIST=N
Concealed Values
LLIB Panel
LLIB,DSN=PROD1.JCL,MEM=ROSDAILY
DSN=PROD1.JCL PAGE 0001
//ROSDAILY JOB HE67YFBH,SYSTEMS,CLASS=2,REGION=1024K,TIME=1439 00000001

//*JOBPARM LINES=9999,FORMS=DPLX 00000002
//*LOGONID @@@@@@@ 00000003
//*PASSWORD @@@@@@@@ 00000004
//BACKUP EXEC PGM=LIBUTIL, 00000005
// PARM=BACKUP 00000006
//STEPLIB DD DSN=ROS1.ROSLIB,DISP=SHR 00000007
//SYSPRINT DD SYSOUT=A 00000008
//ROSLIB00 DD DSN=ROS1.ROSLIB00,DISP=OLD 00000009
//BACKUP DD DSN=ROS1.DAILY.BACKUP(+1),DISP=(,CATLG,UNCATLG), 00000013
// UNIT=TAPE,DCB=(CTI00.GDG,BLKSIZE=20000), 00000014
// LABEL=EXPDT=99000 00000015
// EXEC PGM=IEFBR14,COND=(6,GT,BACKUP) 00000016
//BACKUPTP DD DSN=ROS1.DAILY.BACKUP(+1),DISP=(OLD,DELETE) 00000017
/* 00000018

LLOCK Command
LLOCK Command
The LLOCK command lists the database elements that are locked. Locked means CA WA
CA 7 Edition has detected some element that is in error or that has not been defined to
the CA WA CA 7 Edition database. The locked elements prevent the processing of a job,
network, or data set.
In addition to lock conditions, the list also indicates if scheduling of a job has been
intentionally suspended with a DEMAND,SET=SKP or NXTCYC command.
LLOCK[,{JOB={*|jobname|mask}|DSN=NW.networkname}]
[,LIST=NXTCYC]
[,SYS=systemname]
JOB or DSN is required when SYS is omitted.

JOB
Defines the jobs that you want to list. If SYS is used, JOB is optional. If omitted,
JOB=* is assumed.
Required: Yes (unless DSN is specified).
*
Specifies to consider all jobs are based on the SYS parameter. This value is the
default only if SYS= is provided. systemname must be a specific application
name; it cannot be generic. This value is the default.
jobname
mask
DSN
Defines the networks that you want to list. Enter either a specific network or only
the three characters NW. to list all networks. DSN is required unless JOB or SYS is
used, in which case it must be omitted.
Limits: 1 to 8 alphanumeric characters following NW. prefix
Required: Yes (unless JOB or SYS is specified).

LLOCK Command
LIST
(Optional) Specifies to list only those schedules that are modified with an NXTCYC
or DEMAND,SET=SKP command. NXTCYC is the only valid entry.
SYS
(Optional) Specifies an application system name whose locked jobs you want to list.
The value must be the specific application system name as defined for each job on
the DB.1 or DB.10 panel. If SYS is used with JOB, the jobs that are specified must
have a system name matching the SYS value to be listed. If SYS is used, DSN must be
omitted.
Required Action for a Locked Job

If the display shows the job is LOCKED IN LOAD, this message indicates that the last
attempt to load or reload the job failed. To correct this problem, reissue the LOAD
command. If the LOAD is successful, it unlocks the job. If the LOAD is unsuccessful, CA
WA CA 7 Edition 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 the LLOCK
command.
If the display shows SCHEDULE INFORMATION IS LOCKED, this message indicates that
the job or network schedule needs resolution. Issue the RESOLV command 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=OFF command.
If the display shows IS TO BE SKIPPED ON NEXT SCHEDULED CYCLE, the job is not locked.
However, scheduling of the job has been suspended with a DEMAND,SET=SKP or
NXTCYC,SET=SKP command.

LNODE Command
Examples
LLOCK,DSN=NW.
LLOCK,JOB=CA7JOB1
LLOCK,JOB=CA7*,SYS=CA7
LLOCK,JOB=DUSAXX01
JOB=DUSAXX01 DATE=YY.DDD PAGE 0001
JOB=DUSAXX01 SYSTEM=PAYROLL
.IS LOCKED FOR THE FOLLOWING REASON(S):
THE JOB SCHEDULE INFORMATION IS LOCKED
SLIJ-00 COMPLETED AT 16:07:41 on YY.DDD
LNODE Command
The LNODE command displays entries from the in-storage node table that the XPJOB
function (cross platform scheduling internalization) uses.
LNODE[,NODE={*|nodename|mask}]
[,LIST={SHORT|ALL}]
[,SEQ={NATV|ALT1|ALT2|NODE|STATE}]
[,STATE={FAIL|OFFline|ONline|STOP}]
NODE
(Optional) Specifies the node name or mask that a node name must match before
Default: * (all nodes)
LIST
(Optional) Specifies the amount of node table information requested.
SHORT
Lists only the node name and its current state. SHORT is the default.
ALL
Lists all data that is associated with the nodes requested.

LNODE Command
SEQ
NATV
Indicates native sequence. NATV is the default.
ALT1
Indicates alternative node #1 sequence. This value is not valid for LIST=SHORT.
ALT2
Indicates alternative node #2 sequence. This value is not valid for LIST=SHORT.
NODE
STATE
Indicates node state sequence.
STATE
(Optional) Limits the display to nodes with a particular state. If omitted, displays all
states.
FAIL
Lists only nodes in a failed state because of a communications failure.
OFFline
Lists only nodes manually placed in an offline state.
ONline
Lists only nodes in the online state.
STOP
Lists only nodes manually placed in a stopped state.
More information:

LNODE Command
Examples
LNODE
LNODE,NODE=UNIX001
LNODE,NODE=UNIX??1*,LIST=ALL
LNODE,STATE=FAIL
LNODE,SEQ=STATE
LNODE,NODE=XP63N01,LIST=ALL
---------------------- XPJOB NODE TABLE LISTING ----------------------PAGE 0001
XP63N01 State: ONLINE

DESC: Unix node #63
Alt1: AL6301
Alt2: AL6302
Last Send Prim: 0000.000 00:00:00 #Jobs: 00000000 Job Waits: N Temp: N
Last Send Alt : 0000.000 00:00:00 Last Upd: 2006.240 04:07:40 By MASTER
SLI2-00 REQUEST COMPLETED AT 13:51:17 ON yy.ddd

Node name
Identifies the name of the node contained in the in-storage table.
State
Specifies the current state of the displayed node.
Desc
Specifies a user-entered description of the displayed node.
Alt1
Specifies the first alternate node to try if the primary node is unavailable.
Alt2
Specifies the second alternate node to try if the primary node is unavailable.
Last Send Prim
Specifies the last time data was sent to the primary node.

LNTWK Command
#Jobs
Specifies the total number of jobs sent to this node since CA WA CA 7 Edition
startup.
Job Waits
Specifies whether a job is waiting to be sent to this node.
Temp
Specifies whether this node is a temporary node.
Last Send Alt
Specifies the last time data was sent to any of the alternate nodes.
Last Upd
Specifies the date and time of the last update to this node table entry.
By
Specifies the user ID under which the last update to this node table entry was
performed.
LNTWK Command
The LNTWK command lists workstation network information from the database.
Optional keywords and values control the amount of data that is presented and the
format of the data.
LNTWK,{NW=network|DSN={NW.|NW.networkname}
[,LIST={ALL|DSN|PROS|SCHD|STN|USERS}]
NW
Specifies the network name. Use NW. for generic network requests.
Required: Yes (unless DSN is specified).

LNTWK Command
DSN
Specifies the CA WA CA 7 Edition database entry name.
Required: Yes (unless NW is specified).
NW.
When coded by itself, lists all networks.
NW.network
Defines a specific network name, in up to eight characters (following the NW.
prefix), to list.
LIST
(Optional) Specifies the options for the amount of database information to list.
ALL
Specifies all network data, including documentation and schedules. This option
is not valid for a generic request.
DSN
Specifies network data.
PROS
Specifies all documentation and network data. This option is not valid for a
generic request.
SCHD
Specifies all schedules and network data. This option is not valid for a generic
request.
STN
Specifies all station names and network data.
USERS
Specifies all jobs that are connected to the network and network data.
Examples
LNTWK,NW=DATASET1
LNTWK,NW=NW.DATASET1,LIST=USERS
LNTWK,NW=NW.DATASET1,LIST=ALL
LNTWK,DSN=NW.,LIST=USERS

LNTWK Command
LNTWK,LIST=ALL Panel
LNTWK,DSN=NW.TESTINNW,LIST=ALL
LIST=ALL DSN=NW.TESTINNW DATE=YY.DDD PAGE 0001
*------- NETWORK ------* SCHED PROSE NUMBER LAST MAINTENANCE NETWORK

NAME DSNBR TYPE DSNBR ST JOB YYDDD/HHMMSS TYPE- SUBID
TESTINNW N/A INPUT YES PP000021 02 000 yyddd/000044 DBM INSTALL
. LAST MAINTENANCE ON yy.ddd AT 00:00:44 VIA DBM BY OPERATOR: nnnnnnn
---------------------------- STATION NAMES ----------------------------

BDSTA01 BDSTA02
------------------------------ SCHEDULES ------------------------------

CALENDAR SCALyyPE
SCAL= WKSTA=(01,DOTM=1200,LEADTM=0030,DAY=000)
WKSTA=(02,DOTM=1400,LEADTM=0030,DAY=000)
WEEKLY DAY=MON
LNTWK,DSN=NW.
LIST=DSN DSN=NW. DATE=YY.DDD PAGE 0001
*------- NETWORK ------* SCHED PROSE NUMBER LAST MAINTENANCE NETWORK

NAME DSNBR TYPE DSNBR ST JOB YYDDD/HHMMSS TYPE- SUBID
TIMECARD N/A INPUT YES *NONE* 09 000 yyddd/120336 DBM PAY001-W

PAYCHEKS N/A OUTPT NO *NONE* 09 000 yyddd/115208 DBM PAY020-W
CHKRGSTR N/A OUTPT NO *NONE* 09 000 yyddd/114445 DBM PAY022-W
LABRDIST N/A INPUT YES PP000035 04 000 yyddd/142306 DBM PAY021-W
BENEFITS N/A OUTPT NO PP000036 04 000 yyddd/151331 DBM PAY019-W
ACCRUALS N/A INPUT YES *NONE* 02 000 yyddd/173233 DBM PAY031-W

NETWORK NAME
Identifies the network name as defined in the database.
NETWORK DSNBR
N/A. Networks no longer have numbers.
NETWORK TYPE
Identifies the type of entry:
INPUT
Preprocessing
OUTPT
Postprocessing

LOAD, LOADH Command
SCHED
Identifies whether the network has any schedules.
PROSE DSNBR
Identifies a number that is automatically assigned to the documentation entry of a
network when it is added to the database.
NUMBER ST
Identifies the number of workstation entries within this network.
NUMBER JOB
Identifies the number of jobs that are connected to this network.
LAST MAINTENANCE DATE TIME
Identifies the last date and time an update changed the network definition.
LAST MAINTENANCE TYPE
Identifies the means of the update:
ANLZ
Identifies XREF analyze command.
DBM
Identifies database maintenance.
NETWORK SUBID
Identifies the sub-ID of the network.
LOAD, LOADH Command

The LOAD/LOADH commands create or recreate CPU job profile data in the database.
CPU job profiles should agree with the current JCL. Therefore, any changes to the JCL
must be resynchronized with the database by loading the job. See the RELOAD field in
the DB.1 panel as an alternative to this command.
Use the LOADH command to indicate that the job is to be entered into the queue in CA
WA CA 7 Edition hold status to allow for manual release at a future time.
Use of this command causes the flushing of the rest of the job's JCL. The job returns to
the request queue with a JCL error.
Note: The LOAD/LOADH commands cannot be used with internal cross-platform jobs.

LOAD, LOADH Command
{LOAD|LOADH},JOB=jobname
[,CLASS=x]
[,DOTM=hhmm]
[,LATE={NO|YES}]
[,LEADTM={hhmm|mm}]
[,SCHID={1|nnn}]
[,TIME=hhmm]
JOB
Defines the job name of the job to load. Value is the job name defined in the
database or the member name in a JCL library where the JCL for the job resides. See
JCLID that follows.
CLASS
(Optional) Specifies the workload balancing class for resource checking.
DOTM
(Optional) Defines a due-out time-of-day for load processing.
Default: Assumes current time plus lead time
Limits: 3 to 4 numeric characters specified as hhmm where hh can be hours 0
through 24 and mm can be minutes 00 through 59
JCLID
If used, the value must be a numeric INDEX associated with the desired JCL data set
(on the JCL statement in the initialization file). This field or the JCLLIB field is
required if the job is not defined in the database. JCLID and JCLLIB are mutually
exclusive.
255 is reserved.
Note: For more information about the initialization file, see the Systems
Programming Guide.

LOAD, LOADH Command
JCLLIB
If used, the value must be a symbolic INDEX associated with the desired JCL data set
(on the JCL statement in the initialization file). For more information about the
initialization file, see the Systems Programming Guide. This field or the JCLID field is
required if the job is not defined in the database. JCLID and JCLLIB are mutually
exclusive.
LATE
(Optional) Specifies whether notification should occur if the job becomes late.
will never be marked LATE. The value specified here overrides the value coded on
the job definition PROMPTS field.
LEADTM
(Optional) Defines an elapsed lead time for load processing.
Default: 1 hour (if omitted)
Limits: 2 to 4 numeric characters specified as hhmm or mm where hh can be hours
0 through 24 and mm can be minutes 00 through 59
MAINID
to which the job is to be redirected. The value specified here overrides the value
coded on the job definition MAINID field.
The name must be one of the following:
ALL
SYn
from 1 to 7.
/SYn
from 1 to 7.
-SYn
from 1 to 7.

LOAD, LOADH Command
SCHID
(Optional) Defines the job schedule ID to be used for this job.
Default: 1
Limits: 1 to 3 numeric characters 1 through 999
Note: If the SCHEDULE statement in the initialization file specifies SCHID=YES, this
parameter is required.
TIME
(Optional) Establishes a submit time requirement for the job.
Limits: 3 to 4 numeric characters specified as hhmm where hh can be hours 0
through 23 and mm can be minutes 00 through 59
Examples
LOAD,JOB=USERJOB1,SCHID=14
LOADH,JOB=USERJOB2,JCLID=3
LOADH,JOB=USERJOB9,DOTM=1400,LEADTM=20
Usage Notes
The LOAD command and its process do not support internal cross-platform jobs because
these jobs do not refer to data sets and are executed on other platforms than where the
job ID defined.
■ The LOAD process builds the database profile for a new job or rebuilds the profile
for a job whose JCL was changed. This profile can also be built by a
DEMAND/DEMANDH (for a new job that is not defined to CA WA CA 7 Edition) 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 normal execution after the load step
is executed.
■ When using LOAD/LOADH, if the job was not previously defined to CA WA CA 7
Edition, the job name value for JOB must be the same as the JCL member name that
contains the job's JCL. In addition, the JCLID parameter must be specified to point
CA WA CA 7 Edition to the proper JCL data set.
■ The corresponding DB.1 panel option RELOAD=Y performs the LOAD process as the
first step of the job whenever it is run the next time. This field is automatically set
to Y when a REPL is done through the CA WA CA 7 Edition JCL facility. The indicator
is set back to RELOAD=N when load processing successfully completes.

LOAD, LOADH Command
■ Each LOAD command results in the execution of a batch job with the same job
name as the production job, or if specified in the initialization file DBASE statement,
a job name derived from the LDJOBNM parameter. If using the LDJOBNM
parameter, the JCL JOB statement must provide room for an eight-character job
name.
■ Normal data set availability checking is performed by the operating system based
on DISP parameters on DD statements in the JCL. This could be a problem when
LOAD is requested for a job that references a data set currently in use, such as
online database files. It may be more convenient to 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 command have the
same data set, device, and volume setup characteristics as the subject job whose
profile data is being created or updated. It may be more desirable, in the JES3
environment, to use the DB.1 panel RELOAD option to avoid unnecessary mount
requests for data sets not required for just the LOAD process.
■ If there are any scheduled JCL overrides in the JCL, the resulting profile in the
database reflects the net effect of these overrides based on the current date, time
of day, and SCHID values.
■ If workload balancing is being used, the job being loaded is scheduled using the
default WLB job class for LOAD if the CLASS= keyword is not specified.
Note: For more information about the LOADCLASS parameter of the OPTIONS
statement in the initialization file, see the Systems Programming Guide.
■ The LOAD command cannot be used for a job that has been marked as
nonexecutable (for example, EXEC=N) on the DB.1 panel.
■ If the LOADDSNS keyword is used on the DBASE statement in the initialization file,
then the LOAD process does not build any DD or data set information 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 keyword specifying a
step for the job to begin execution, the LOAD step does not execute. To LOAD this
job, omit the RESTART keyword.
■ If VRMDD=DEF or VRMDD=YES is coded on the OPTIONS statement in the CA WA
CA 7 Edition initialization file, then VRM resource definitions for this job are
dynamically modified when the job is LOADed.
Note: For more information about VRM Device Control, see the Database
Maintenance Guide.

LOC Command
LOC Command
The LOC command lists catalog contents for one or more data sets. This function is
available on the UT Menu panel as FUNCTION value 19 or on any other menu or
formatted panel as FUNCTION value UT.19.
LOC,DSN=dsname[,VOLSER=volser]
DSN
Defines the data set whose catalog contents you want to list. The name can be a
fully qualified name, a generic request, or a relative request for a generation data
set. A generic request is specified by the desired index levels followed by a period.
VOLSER
(Optional) Defines the volume serial number that contains the CVOL catalog to be
listed. If the high-level node is defined in the master catalog, this parameter is not
needed. Otherwise, code it.
Usage Notes
A generic request for data sets whose catalog entries are in the master catalog receive
the message that the data set is not found. This is a restriction of SVC 26 that is used to
process this command.
Examples
LOC,DSN=USER.
LOC,DSN=USER.FILE1,VOLSER=12B345
LOC,DSN=USER.GDG.FILE(-1)
LOGIN, LOGOUT Commands

The LOGIN command logs the start of workstation tasks for both networks.
The LOGOUT command logs the completion of workstation tasks for both networks.

Input Workstation Networks

This function is available on the QM.6 panel.
This command has the following format for input workstation networks:
{LOGIN|LOGOUT},JOB={jobname|jobnumber},STATION=station[,INITS=xxxxxxxx]
JOB
Defines the unique CA 7 job name or the job number that was assigned when the
network was placed in the preprocess queue. The job name can be used to log the
first station only and the job number must be used thereafter.
jobname
Defines the job name.
jobnumber
Defines the job number.
STATION
Defines the name of the workstation that is to be logged in or out.
Required: Yes (unless first station in the network)
INITS
Defines any user information to be posted to the workstation record.
Note: This could be used to let users enter their names or initials with the
command. This information is placed in the log and appears on inquiries.
Examples
This example logs in workstation KEYPUNCH that is part of the network referenced by
CA 7 job number 17. No user information to be posted.
LOGIN,JOB=17,STATION=KEYPUNCH
This example logs out workstation KEYPUNCH that is part of the network referenced by
CA 7 job number 17. CLERK1 is the user information to be posted to the workstation and
logged.
LOGOUT,JOB=17,STATION=KEYPUNCH,INITS=CLERK1

Output Workstation Networks

This function is available on the QM.7 panel.
This command has the following format for output workstation networks:
{LOGIN|LOGOUT},JOB={jobname|jobnumber},NW=network,STATION=station
[,FORCE=YES]
[,INITS=xxxxxxxx]
[,SUBID=subid]
JOB
Defines the unique CA 7 job name or the job number assigned to the job and its
output workstation networks. Job name can be used only for the first station in a
network and the job number must be used thereafter.
jobname
Defines the job name.
jobnumber
Defines the job number.
NW
Defines the name of the network to which the station belongs. The value must be
the network name defined in the database.
Required: Yes (for first station unless SUBID is used)
STATION
Defines the station to be logged in or out. Value must be the station name.
Required: Yes (unless first station in the network)

FORCE
(Optional) Specifies to allow the logging in of an output workstation network prior
to completion of the CPU job to which it is associated. If used the value must be
entered as shown.
INITS
(Optional) Defines any user information to be posted to the workstation record.
Note: This could be used to let users enter their names or initials with the
command. This information is placed in the log and appears on inquiries.
SUBID
(Optional) Defines additional information to identify the station and network to be
logged in or out. If used, the value is as defined in the database (or specified when
the network was demanded). SUBID can be used instead of NW for the first station
in a network. When substituting for NW, SUBID is required.
Default: Spaces
Examples
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=RPTN01,INITS=DIST

LPDS Command
LPDS Command
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 any PDS or
sequential data set. Other commands are also available to review JCL or PARM
statements.
Note: Any undisplayable hexadecimal characters in the member are shown as periods (.)
in the output from the LPDS command.
LPDS,DSN=dsname[,MEM=member][,VOLSER=volume]
DSN
Defines the fully qualified data set name of either a sequential data set or the name
of a PDS containing a member (MEM) to be listed.
Note: You can specify DSN=*INIT* as a special value to see the active initialization
file (online member) that CA 7 is currently using. This value is helpful with
troubleshooting.
MEM
Specifies that you want to list this member of a named PDS (DSN).
Required: Yes, if listing from a PDS
VOLSER
(Optional) Specifies the DASD volume on which the data set (DSN) resides. If
VOLSER is omitted, the data set must be a cataloged data set.
More information:
General Inquiry Facility (see page 29)

LPDS Command
Examples
LPDS,DSN=CA7.DSN1,MEM=M123,VOLSER=DBS101
LPDS,DSN=CA7.DSN2,MEM=M456
LPDS,DSN=CA7.SEQ.DATASET
Concealed Values
LPDS Panel
LPDS,DSN=CA7.MACLIB,MEM=SASSSWKD
DSN=CA7.MACLIB(SASSSWKD) PAGE 0001
MACRO 00000100
SASSSWKD 00000200
SPACE 5 00000300
*--------------------------------------------------------------------* 00000400
* DSECT FOR THE SCHEDULE ELEMENT TO PRINT ROUTINE 'SASSCISE' 00000500
*--------------------------------------------------------------------* 00000600
SPACE 2 00000700
SWKDSECT DSECT 00000800
SWKLEN DS H - LENGTH OF THIS WORK AREA 00000900
SWKISE# DS H - NUMBER OF ISE'S LEFT TO PRINT 00001000
SPACE 00001100
SWKSRADR DS F - ADDRESS OF SCHEDULE RECORD 00001200
SPACE 00001300
SWKDBL DS D - DOUBLE WORD WORK AREA 00001400
SPACE 00001500
SWKISEAD DS F - ADDR OF CURRENT ISE ENTRY 00001600
SPACE 00001700
SWKSAVE DS 16F - SAVE AREA FOR CALLER'S REG'S 00001800

LPOST Command
LPOST Command
The LPOST command lists output network information from the postprocess queue. This
information includes the status of all networks and whether they are late. Information,
including documentation, can be listed in various sequences.
LPOST[,JOB={*|jobname|mask}]
[,LIST=Q]
[,NW={*|networkname|mask}]
[,ST={*|LATE|HELD}]
[,STN={*|stationname|mask}]
[,SUBID={*|subid|mask}]
JOB
LIST
(Optional) Specifies the amount of queue information requested. When specified,
the value must be Q to list station data only. When LIST is not specified, the display
consists of a single description line for each queue record.

LPOST Command
NW
(Optional) Defines the network name or mask that a network name must match
Default: * (all network names)
SEG
(Optional) Defines a segment and subsegment of documentation to be listed. If a
subsegment, use the form (xxxxxxxx,yyyyyyyy).
xxxxxxxx
Defines 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
SEQ
NATV
default.
CA7
Indicates CA WA CA 7 Edition assigned job number sequence.
DLTM
DOTM
JOB
NW
Indicates network name sequence.
STA
Indicates station name sequence.
SUBID
Indicates sub-ID name sequence.

LPOST Command
ST
(Optional) Limits the display to postprocess queue tasks with a particular status.
*
All tasks. This value is the default.
HELD
Indicates only jobs in hold status.
LATE
Indicates only the late tasks.
STN
(Optional) Defines the station name or mask that a station name must match before
Default: * (all station names)
SUBID
(Optional) Defines the subid name or mask that a subid must match before its
Default: * (all subid names)
subid*
Specifies multiple sub-IDs represented by a generic sub-ID name.
More information:

LPOST Command
Examples
LPOST
LPOST,SEQ=SUBID,SUBID=RPT*
LPOST,ST=LATE,STATION=OUTDEST
LPOST Panel
LPOST
LIST= DATE=YY.DDD PAGE 0001
CA-7 NETWORK NETWORK STATION JOB *-----DAY(DDD) AND TIME(HHMM)-----*

REF# SUBID DESC NAME NAME DEADLINE LOGIN DUE-OUT NW/LGOUT
0011011 OVERHERE DMD#0011 171/1753 *NONE* 171/1803 WATCHME

0011012 OVERTHER DMD#0011 171/1953 *NONE* 171/2003 WATCHME
0012011 HTERM1 DMD#0012 171/1753 *NONE* 171/1953 TESTOTNW
LPOST,LIST=Q Panel
LPOST,LIST=Q
LIST=Q DATE=YY.DDD PAGE 0001
CA-7 NETWORK NETWORK STATION JOB *----DAY(DDD) AND TIME(HHMM)-----*

0001011 RPT1205 ACCTRPT PRINTER DUSAXX01 129/0800 *NONE* 129/0900 ACCRUALS

-------------------------STATION INFORMATION --------------------------
. NETWORK=TESTOTNW,DESTINATION=DELIVERY
. SCHEDULE ID = 001
. JOB DEMANDED
0001012 RPT1205 ACCTRPT DELIVERY DUSAXX01 130/0600 *NONE* 130/0700 ACCRUALS

-------------------------STATION INFORMATION --------------------------
. NETWORK=TESTOTNW,ORIGIN=PRINTER,DESTINATION=HTERM1
. SCHEDULE ID = 001
. JOB DEMANDED

LPOST Command

CA-7 REF#
Identifies a system-generated number consisting of job number for the first four
digits, the next two digits being the number of times the output network is
connected to the same job, and the last digit being the sequence number of the
workstation entry within the network.
NETWORK SUBID
Identifies either the value from the JOBCONN,NWK (DB.3.4) panel, the SUBID
entered on a DMDNW command, or blank if the network was brought into the
postprocess queue with the DMDNW command with no SUBID= keyword.
NETWORK DESC
Identifies the value from either the DB.3.4 panel, the DESC entered on the DMDNW
command, or blank if no DESC keyword was entered on the DMDNW command.
STATION NAME
Identifies the LTERM name defined as a workstation within this network.
JOB NAME
Identifies either the job whose connection on the DB.3.4 panel caused the network
to be brought into the postprocess queue, the JOB entered on a DMDNW
command, or a system-generated name of DMD#nnnn for a network demanded
with the DMDNW command with no JOB= keyword (the nnnn being the job
number).
DEADLINE
Identifies the date and time that this workstation entry should be logged in to be
LOGIN
Identifies the date and time that this workstation entry was logged in. If a login has
not been done, this field is *NONE*.
DUE-OUT
Identifies the date and time that this workstation entry should be logged out.
NW/LGOUT
Identifies either the date and time that this workstation entry was logged out or the
network name if a logout has not been done for this workstation entry.
STATION INFORMATION
Identifies 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 of this network. If the output
network was brought in by a connection to a job and the job was demanded or
triggered in, then that is reflected here also.

LPRE Command
LPRE Command
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[,JOB={*|jobname|jobnumber|mask}]
[,LIST=Q]
[,NW={*|networkname|mask}]
[,ST={*|LATE|HELD}]
[,STN={*|stationname|mask}]
JOB
LIST
(Optional) Specifies the amount of queue information requested. When specified,
the value must be Q to list station data only. When LIST is not specified, the display
consists of a single description line for each queue record.
NW

LPRE Command
SEG
(Optional) Specifies a segment and subsegment of documentation to be listed. If a
xxxxxxxx
(xxxxxxxx,yyyyyyyy)
Defines the name of a segment (xxxxxxxx) and subsegment (yyyyyyyy) enclosed
in parentheses and separated by a comma.
SEQ
NATV
default.
CA7
DLTM
DOTM
JOB
NW
Indicates network name sequence.
STA
Indicates station name sequence.
SUBID
Indicates sub-ID name sequence.

LPRE Command
ST
(Optional) Limits the display to preprocess queue tasks with a particular status.
*
Displays all tasks. This value is the default.
HELD
Indicates only tasks in hold status.
LATE
Indicates only late tasks.
STN
SUBID
More information:

LPRE Command
Examples
LPRE
LPRE,ST=LATE,SEQ=NW
LPRE,STATION=KEYPUNCH
LPRE Panel
LPRE

0006001 KEYSTATS SYSTSAVE CONSOLE DMD#0006 128/1511 *NONE* 128/1521 SYSTSAVE

0006002 KEYSTATS SYSTSAVE PRINTER DMD#0006 129/1711 *NONE* 129/1721 SYSTSAVE
0007001 WEEKLY ENGINEER CONSOLE DMD#0007 128/1511 *NONE* 128/1521 ENGINEER
SLIF-00 REQUEST COMPLETED AT 16:09:00 on YY.DDD
LPRE,LIST=ALL Panel
LPRE,LIST=ALL
LIST=ALL DATE=YY.DDD PAGE 0001

0006001 KEYSTATS SYSTSAVE CONSOLE DMD#0006 128/1511 *NONE* 128/1521 SYSTSAVE

--------------------------STATION INFORMATION ------------------------
. NETWORK=TRIGINNW,DESTINATION=PRINTER
. NETWORK TRIGGERS JOB(S)
. SCHEDULE ID = 001
. JOB DEMANDED
0006002 KEYSTATS SYSTSAVE PRINTER DMD#0006 129/1711 *NONE* 129/1721 SYSTSAVE

--------------------------STATION INFORMATION ------------------------
. NETWORK=TRIGINNW,ORIGIN=CONSOLE
. NETWORK TRIGGERS JOB(S)
. SCHEDULE ID = 001
. STATION LAST IN NETWORK
. JOB DEMANDED

LPRE Command

CA-7 REF#
Identifies a system-generated number consisting of job number for the first four
digits. The next two digits are zeros. The last digit is the sequence number of the
workstation entry within the network.
NETWORK SUBID
Identifies a value from either the NETWORK (DB.5) panel or the SUBID entered on a
DMDNW command.
NETWORK DESC
Identifies either the network name or the DESC entered on a DMDNW command.
STATION NAME
Identifies the LTERM name defined as a workstation within this network.
JOB NAME
Identifies either the job name from the DB.5 panel, the JOB= value on a DMDNW
command or a system-generated name of DMD#nnnn for a network demanded
with the DMDNW command and no JOB= keyword (the nnnn being the job
number).
DEADLINE
Identifies the date and time that this workstation entry should be logged in to be
LOGIN
Identifies the date and time that this workstation entry was logged in. If a login has
not been done, this field shows *NONE*.
DUE-OUT
Identifies the date and time that this workstation entry should be logged out.
NW/LGOUT
Identifies either the date and time that this workstation entry was logged out or the
network name if a logout has not been done for this workstation entry.
STATION INFORMATION
Identifies 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 of this network. If the network was
brought in by the DMDNW command, then this is reflected here also.

LPROS Command
LPROS Command
The LPROS command lists documentation.
You can define documentation for each portion of the production workload through the
CA WA CA 7 Edition documentation facility. You can define documentation in the
database for each individual network. Network documentation can be very helpful at
the time a network is being processed. The Database Maintenance Guide describes how
this information is entered into the database.
Once defined, this documentation is available at any level, from the general description
of a network to the specific operating instructions for a workstation task.
Documentation can be listed by using the LPROS top line command or the DB.4 panel.
Either can be used in batch or online. It is your responsibility to keep documentation
accurate, current, and consistent with data center standards using the database
maintenance documentation facilities.
LPROS,{UID=user}
{DSN=dsname}
{DSNBR={PP*|PPnnnnnn|PP00nnnnn*}}
{JOB=jobname[,STEP=stepname][,DD=ddname]}
{SYS=system}
{NW=network}
[,LIST={ALL|NOLINK}]
UID
Specifies a user-defined name for which the user ID level documentation data is to
be listed.
Limits: 1 to 32 alphanumeric characters (using OS data set standards)
Required: No (at least one keyword is required)
DSN
Specifies the data set names of the data set level documentation members to be
listed. Can be entered either with or without the PP. prefix that is used in the CA
WA CA 7 Edition index entry for the documentation data. Value can be specified as
a specific or generic data set name. A generic name is indicated by coding the
required levels of index (nodes) terminated by a period. At least one index level is
required.

LPROS Command
DSNBR
Specifies a single or generic CA WA CA 7 Edition database documentation member
number to be listed.
PP*
Specifies all documentation members in the database.
PPnnnnnn
Specifies a specific database documentation member number where PP is
constant and nnnnnn is the CA WA CA 7 Edition database documentation
member number. Leading zeros can be omitted.
PP00nnnnn*
Defines a generic database documentation member number specified in the
PP00nnnnnn format, up to seven digits, and terminated with an asterisk after
the last significant digit. Leading zeros cannot be omitted.
JOB
Specifies a specific job name for which the job level documentation data is to be
listed. Used by itself to list job level documentation.
STEP
(Optional) Used only with JOB and DD keywords to list DD level documentation.
DD
(Optional) Used with JOB and STEP keywords to list the documentation data for the
DD in the STEP of the JOB.
SYS
Specifies a specific application system name for which the system level
documentation data is to be listed.

LPROS Command
NW
Specifies a specific network name for which the network level documentation data
is to be listed.
LIST
(Optional) Specifies the desired options for listing documentation text. If omitted on
a generic member request, one line giving member level information is listed for
each member. If omitted on a specific member request, information is listed as if
ALL had been specified.
ALL
Can be used with specific or generic member request to cause documentation
text to be listed. For specific member request, any documentation members
linked to the requested member are listed following text for the primary
member. For generic member request, text from each member is listed as the
member is read.
Note: Documentation members are linked to a member through the LINK field
on the CA WA CA 7 Edition Database Maintenance DB.4 panels.
NOLINK
Can be used with specific or generic member request to indicate that linked
documentation is not to be listed with primary text.
SEG
xxxxxxxx
(xxxxxxxx,yyyyyyyy)
More information:

LPROS Command
Usage Notes
Including documentation in the CA WA CA 7 Edition database is entirely optional. The
documentation capability is provided only to assist the user. Documentation is not
required to properly control work defined to CA WA CA 7 Edition.
The LPROS command is used to display database documentation member information,

as well as the actual documentation itself. By following some user-defined standard
naming conventions for documentation, any questions regarding production workload
components or considerations can be answered very quickly with this command.
Note: For more information about defining documentation to the CA WA CA 7 Edition

database, see the Database Maintenance Guide.
Examples
LPROS,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=PP0000003*
LPROS,JOB=DUSAXX01
DSN=PP.DUSAXX01.JOB DATE=YY.DDD PAGE 0001
------------- PROSE DATASET NAME ------------ PPNBR PROS-TYPE
PP.DUSAXX01.JOB .............................. PP00000009 JOB
. PROSE-TYPE=JOB,JOB=DUSAXX01,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 A

SCHEDULED JOB. IT CONSISTS OF TWO STEPS.

LPRRN Command
LPROS,DSN=PP.
DSN=PP. DATE YY.DDD PAGE 0001
------------- PROSE DATASET NAME ------------ PPNBR PROS-TYPE
PP.(BLANKS).SYS ............................ PP00000026 SYSTEM
PP.AC001V10.JOB ............................ PP00000026 JOB

PP.ALICIA .................................. PP00000010 USER
PP.ART.SYS ................................. PP00000016 SYSTEM
PP.DANS.SYS ................................ PP00000018 SYSTEM
PP.DLMINWK1.NW ............................. PP00000027 NETWORK
PP.DUDLXX01.JOB ............................ PP00000028 JOB
PP.DUSAHE01.JOB ............................ PP00000029 JOB
LPRRN Command
The LPRRN command lists job information from the prior-run queue. The prior-run
queue contains information about the last successful completion of each job.
Parameters allow the user to indicate which job or group of jobs is desired, what
information is to be reviewed, and the sequence of the displayed data.
LPRRN[,CLS=x]
[,{JOB={*|jobname|mask}|JOBL={*|longjobname|mask}}]
[,LIST={STATUS|option}]
[,SEQ={NATV|DLTM|DOTM|JOB}]
[,TZ={CA7|EXEC}]
CLS
CPUID
initiation record.

LPRRN Command
JOB
JOBL
LIST
(Optional) Specifies the amount of information to list.
STATUS
Specifies a single description line for each queue record. STATUS is the default.
ALL
Specifies all data relative to the queue.
CPU
Specifies only CPU jobs.
JCL
Specifies JCL information from the last good run of the job only. The JCL is listed
only for jobs marked RETAIN-JCL=Y on the DB.1 panel. No JCL is listed for
non-executable jobs.
Depending on the security options that are selected for your installation, the
following values are sometimes concealed in the display:

LPRRN Command
PROS
Specifies documentation data as it currently resides in the database only.
Q
Specifies job data only.
XPJOB
Indicates internal cross-platform (XPJOB) information only. This information is
only listed for XPJOBs marked Retain=Y on the DB.10 panel. No XPJOB
information is listed for non-executable jobs.
SEG
(Optional) Specifies a segment and subsegment of documentation that you want to
list. If a subsegment, use the form (xxxxxxxx,yyyyyyyy).
xxxxxxxx
(xxxxxxxx,yyyyyyyy)
Specifies the name of a segment (xxxxxxxx) and subsegment (yyyyyyyy)
enclosed in parentheses and separated by a comma.
SEQ
(Optional) Specifies the display sequence of the requested information.
NATV
default.
DLTM
DOTM
JOB
SYS

LPRRN Command
TZ
(Optional) Controls whether to normalize a job's start and completion date/times to
the time zone of the running CA WA CA 7 Edition.
statement.
CA7
Normalizes the start and completion date/times to the running CA WA CA 7
Edition time zone.
EXEC
Defines that the start and completion date/times should be in the execution
time zone.
More information:

LPRRN Command
Examples
LPRRN
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 0001
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 0015 034/1512 034/1415 034/1512 YYDDD/1415 ALL-IPO1 001 SSCN C-C0000
D463XX08 0017 034/1513 034/1416 034/1513 YYDDD/1416 ALL-IPO1 001 SSCN C-C0000
D463XX01 0016 034/1513 034/1416 034/1513 YYDDD/1416 ALL-IPO1 001 AUTO C-C0000
D463XX10 0020 034/1517 034/1419 034/1523 YYDDD/1419 ALL-IPO1 001 AUTO C-C0000
D463XX07 0025 034/1519 034/1422 034/1524 YYDDD/1422 ALL-IPO1 001 DEMD C-C0000
D463LIST 0005 343/1527 343/1430 343/1527 YYDDD/1430 ALL-IPO1 001 DEMD C-C0000
D4638VCT 0001 345/1818 345/1723 345/1818 YYDDD/1733 ALL-IPO1 001 AUTO C-C0000
D463BTI 0002 317/1213 317/1113 317/1213 YYDDD/1113 ALL-IPO1 001 AUTO C-C0000
D463LOGP 0002 055/1232 055/1137 055/1232 YYDDD/1138 ALL-IPO1 001 DEMD C-C0000
D463ICOM 0002 044/1439 044/1339 044/1439 YYDDD/1339 ALL-IPO1 001 AUTO C-C0000
D463EXTR 0027 034/1530 023/1432+034/1530 YYDDD/1433+ALL-IPO2 001 DEMD C-C0000
SLIF-00 REQUEST COMPLETED AT 13:42:47 on YY DDD

JOB NAME
definition panel.
CA-7 JOB#
Identifies the CA 7 job number that was assigned on initial queue entry.
DEADLINE
Identifies a calculated time by which this job should have started to have been

LPRRN Command
START
Identifies the time that the job actually started. A plus sign displayed immediately
after the field indicates that job's start time is normalized to the time zone of the
running CA WA CA 7 Edition.
DUE-OUT
Identifies the original due-out time for this job.
COMPLETE
Identifies the date/time that this job actually completed. A plus sign displayed
immediately after the field indicates that job's completion date/time is normalized
to the time zone of the running CA WA CA 7 Edition.
CPU SPEC/RUN
Identifies the MAINID specified for this job to be submitted to and the system
where it ran.
For XPJOB jobs, this field displays XPJ for SPEC. When the job begins execution, the
SCHID
Identifies the schedule ID that this job was brought into the request queue and ran
under.
ENTRY MODE
Identifies how the job was brought into the queue. Values are the following:
AUTO
Indicates a triggered job.
DEMD
Indicates a demanded job.
EXTL
Indicates a job submitted external to CA WA CA 7 Edition.
PS
Indicates a job submitted by Personal Scheduling System.
RPET
Indicates a repeated job.

LQ Command
SSCN
Indicates a job record brought in by schedule scan.
XDEM
Indicates a job brought in by the DEMAND command from an XPS client.
JOB STATUS
Identifies the highest condition code passed by any step within this job.
LQ Command
The LQ command lists information about jobs from the request, ready, and active
queues. The queue information that is provided shows the status on all production
activity known to CA WA CA 7 Edition. This command is helpful in determining the
queue in which a job currently resides.
{LQ|LQUE}[,AGENT={*|agent|mask}]
[,CLS=x]
[,DRCLASS={*|@ANY|@NONE|drclass|mask|}]
[,DRMODE={*|NO|YES}]
[,LIST=option]
[,SCHID={0|nnn}]
[,ST=option]
[,TZ={CA7|EXEC}]
AGENT
CLS

LQ Command
CPUID
initiation record.
DRCLASS
display.
@ANY
Specifies that jobs with any DRCLASS should be selected.
@NONE
Specifies that jobs with no DRCLASS should be selected.
DRMODE
(Optional) Indicates the class of jobs to select.
*
YES
NO

LQ Command
JOB
JOBL
LIST
(Optional) Specifies the amount of queue information requested.
AGJOB
Indicates internal cross-platform agent information only.
ALL
Indicates all data related to the jobs.
CPU
Specifies only CPU jobs.
JCL
Indicates JCL information or internal cross-platform parameter data for
cross-platform job types.
Depending on the security options that your installation selected, the following
JCL values are sometimes concealed in the display:

LQ Command
JOBL
PRM
Indicates internal cross-platform PARMLIB information or JCL information for
CPU jobs. For more information, see the JCL parameter.
PROS
Indicates a documentation information only.
Q
Indicates a job data only.
RQMT
Indicates all requirements information only. This information can include a
possible ARF message.
STATUS
Indicates unsatisfied requirements information only.
XPJOB
Indicates internal cross-platform XPJOB information only.
When a specific job is requested through the JOB parameter, the default is
LIST=STATUS and all unsatisfied job requirements are listed. When JOB and LIST are
not specified, a default display consisting of one description line for each queue
record is listed. If SEG is specified, the default is LIST=PROS.
Note: If RQMT or STATUS is specified, the VRM requirements are listed for jobs in
the ready queue with a status of W-RSRC.
NODE
SCHID
(Optional) Specifies the schedule ID for which you want to select information.

LQ Command
SEG
xxxxxxxx
(xxxxxxxx,yyyyyyyy)
SEQ
(Optional) Controls the display sequence of the selected information.
NATV
default.
AGENT
Indicates an agent name sequence.
CA7
Indicates a CA 7 job number sequence.
DLTM
Indicates a deadline time sequence.
DOTM
Indicates a due-out time sequence.
JOB
NODE
Indicates a node name sequence.

LQ Command
ST
displays all jobs in the request, ready, and active queues.
Default: All jobs in the request, ready, and active queues
ABND
AGENT
ARAE
ARF
ARFH
ARFJ
CBAD
COMP
HELD
JCLO
JCLR
Indicates jobs are in JCL or PARM error status.
LATE
MANV
MJOB
Indicates jobs that are requeued because of multiple JOB statements.

LQ Command
NODE
NOID
REPLY
Required message.
REQU
RSTR
RTRY
SKEL
SUBM
Indicates jobs that are submitted to the host system for execution.
WRSC
Indicates jobs that are waiting for VRM resources.
SYS
TZ
(Optional) Controls whether a job's start date/time should be normalized to the
time zone of the running CA WA CA 7 Edition.
statement.
CA7
Defines that the start date/time should be normalized to the running CA WA CA
7 Edition time zone.
EXEC
Defines that the start date/time should be in the execution time zone.

LQ Command
More information:

ARF Information Section Messages (see page 460)
Examples
LQ
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 Command
LQ Command
LQ
HISTORY REQ 0105 098/1025 *NONE* 098/1025 ALL- 001 DEMD 002
CA7LJESX REQ 0102 098/1024 098/1000 098/1030 ALL- 001 SSCN 001
C7TST001 REQ 0106 098/1025 *NONE* 098/1025 ALL- 001 DEMD 001
C7TST002 REQ 0107 098/1025 *NONE* 098/1025 ALL- 001 DEMD 001
C7TST003 ACT 0110 098/1029 098/0929+098/1029 ALL-XE79 001 DEMD 000
LQ,JOB=DUSAZZ01,LIST=RQMT Command
LQ,JOB=DUSAZZ01,LIST=RQMT
LIST=RQMT JOB=DUSAZZ01 DATE=YY.DDD PAGE 0001
DUSAZZ01 REQ 0005 128/1611 *NONE* 128/1611 /SY2- 001 DEMD 003 LATE
---------------------------REQUIREMENTS STATUS ---------------------
_ _ _ _ JCL OVERRIDES REQUIRED
_ _ _ _ INTERNAL JOB=DUSAZZ13 DATE/TIME=YYDDD/HHMM
LQ,JOB=DUSAZZ01,LIST=JCL
LQ,JOB=DUSAZZ01,LIST=JCL
LIST=JCL JOB=DUSAZZ01 DATE=YY.DDD PAGE 0001
DUSAZZ01 REQ 0005 128/1611 *NONE* 128/1611 /SY2- 001 DEMD 004 R-REQUE
---------------------------- JCL INFORMATION -----------------------
//DUSAZZ01 JOB HE67YFSH,PAYROLL,REGION=40K,TIME=0003,CLASS=B 0010
/*ROUTE PRINT RMT2 0020
/*JOBPARM ROOM=543 0030
//*UCC7RESTART UCC7

LQ Command
LQ,JOB=215,SEG=QDESC Command
LQ,JOB=215,SEG=QDESC
LIST=PROS CA-7#=0215 DATE=YY.DDD PAGE 0001
SEG=(QDESC)
CA07XX01 REQ 0215 173/1943 *NONE* 173/1943 ALL- 001 DEMD 001
-------------------------- PROSE INFORMATION --------------------------
*** JOB CA07XX01
*** SCHEDULED JOB, FIRST IN THE NETWORK
*** FIRST STEP
LQ,LIST= Command
LQ,LIST=
JOEJOB1 RDY 0002 288/1135 *NONE* 288/1135 ALL- 001 DEMD 000 W-RSRC
JOEJOB15 RDY 0008 288/1327 *NONE* 288/1327 ALL- 001 DEMD 000 W-RSRC
SCA1003D RDY 0021 295/0954 295/0919 295/1000 ALL- 099 SSCN 000 LATE
TESTJOBA RDY 0024 295/1116 *NONE* 295/1116 ALL- 001 DEMD 000 W-RSRC
SLIF-00 REQUEST COMPLETED AT 13:35:53 on 09.295

JOB NAME
definition panel.
QUEUE NAME
Identifies the queue where this job record currently resides. Values are REQ for
CA-7 JOB#

LQ Command
DEADLINE
Identifies a calculated time by which this job should be active on the CPU to be
SUB/START
For a job in the request queue, this is the time of a submit time requirement. (The
requirement can be manually posted, leaving a date/time value with no
outstanding submit time requirement.) If there is a value for a job in the ready
queue, this is the time that the JCL was written to the submit data set or internal
reader. Until the first SMF step termination record is received, this field is *NONE*
for a job in the active queue. A plus sign displayed immediately after the field
indicates that the job's start time is normalized to the time zone of the running CA
WA CA 7 Edition.
DUE-OUT
Identifies the due-out time for this job.
CPU SPEC/RUN
Identifies the SPEC value is what CPU this job should be submitted to (see MAINID
field on DB.1 panel). The RUN value is what CPU the job has been submitted to. For
7UNI jobs, the RUN value can be 7UWT, which indicates that the process has not
started on the submitted to platform.
SCHID
queue.
ENTRY MODE
Identifies how the job was brought into the queue. Values are the following:
ARFJ
Indicates an ARF recovery job.
AUTO
Indicates a triggered job.
DEMD
Indicates a demanded job.

LQ Command
EXTL
Indicates a job submitted external to CA WA CA 7 Edition.
LOAD
Indicates a job record to be loaded (brought in by the LOAD command).
PS
Indicates a job submitted by Personal Scheduling System.
RPET
Indicates a repeated job.
RUN
Indicates a job brought in by the RUN command.
SSCN
Indicates a job record brought in by schedule scan.
XDEM
Indicates a job brought in by the DEMAND command from an XPS client.
XPS
Indicates a job brought in from an XPS client using the RUN command with the
REF option.
XRUN
Indicates a job brought in from an XPS client using the RUN command.
MSTR REQ
Indicates the number of outstanding master requirements for a job record.
JOB STATUS
Indicates the indication of the job's current disposition. Values and their meanings
are the following:
A-Snnnn
A-Unnnn

LQ Command
C-Cnnnn
processing.
E-ARFATT
Indicates an error occurred during the attempt to attach ARF definitions. This
can result if the ARFSET specified is not defined. A diagnostic message may
have been written to the CA WA CA 7 Edition log, the OS console, or to the
trailer queue for the job (in which case you can view it using
LQ,JOB=x,LIST=ALL).
E-ARFERR
Indicates the job encountered an error in the ARF processing. Issue a LARFQ
command for the job to get more specific information.
E-SEGERR
Indicates the job has been requeued to the request queue because the CA WA
CA 7 Edition job submission task was unable to read a security segment for the
job.
LATE
LOADING
Indicates the job completed execution of a LOAD-only run and is completing
the LOAD process. This status is for jobs in the request queue.
N-FAIL
For XPJOB jobs, indicates that the node to which this job should be directed
could not be contacted through CAICCI Services. For agent jobs, indicates that a
problem occurred contacting the agent.
N-IAS
For agent jobs, indicates a problem exists with component CA IAS (Integrated
Agent Services) or that AGENTJOB=NO is specified or defaulted in the
initialization file.
N-OFFL
Indicates the node is in an offline status in the CA WA CA 7 Edition internal
node table. There are no alternate nodes defined, or if there are, those
alternates are also in an offline status or could not be contacted through CAICCI
Services.

LQ Command
N-STOP
Indicates the node is in a STOP status in the CA WA CA 7 Edition internal node
table.
N-XTRK
Indicates the CA WA CA 7 Edition Tracker is not defined or active in this CA WA
CA 7 Edition such that cross-platform tracking may occur. Instead of submitting
the job when no tracking facility is available, CA WA CA 7 Edition places the job
in this status.
QJCL
Indicates this job is in the request queue with zero master requirements. At the
time the command was issued, CA WA CA 7 Edition was processing a SAVE or
REPL function on the QM.5 (QJCL) panel for this job.
R-#nnnn
R-Cnnnn
R-JCLERR
was received before a job initialization record.
R-MJOB
Indicates the job has been requeued because multiple JOB statements were
found within the job's JCL while the current security settings prevent this.
R-NOUID
Indicates during submission, if no valid USERID is available, a check of the
SUBNOID parameter is done to determine if a job can be submitted without an
ID. With SUBNOID set to NO, the job moves back to the request queue with a
status of R-NOUID.
R-REQUE
Indicates the job has been requeued to the request queue using the REQUEUE
command or the Q function on the QM.1 panel.

LQ Command
R-TRLFUL
Indicates at the time the job was active, CA WA CA 7 Edition required another
track to be obtained from the trailer queue to hold outputs. At the time that CA
WA CA 7 Edition tried to get another track, either an out of space condition or
an I/O error occurred.
RETRY
Indicates a dynamic allocation error occurred during attach of JCL for this job.
At a user-specified time interval, a retry of the JCL attach occurs.
RQMT-INC
RUSH
SKELETON
W-AGENT
Indicates a job that CA WA CA 7 Edition submitted and queued for submission
to an agent that is not active currently.
Note: This status is sometimes seen even when the CA IAS interface is not
active. The difference is that CA IAS received the job request. If a job reflects
status N-IAS, this status indicates that the job has not been sent to CA IAS for
processing.
W-RSRC
Indicates a job is in the ready queue waiting on a resource that is unavailable.
LQ,LIST=XPJOB Panel
LQ,JOB=CA7XPJOB,LIST=XPJOB
LIST=XPJOB JOB=CA7XPJOB DATE=YY.DDD PAGE 0001
C7TST003 ACT 0110 098/1029 098/0929+098/1029 ALL-XE79 001 DEMD 000
------------------------- XPJOB INFORMATION -------------------------

P Node: UNIX001 State: Fail
A Node:
SU Type: Y Trace: N Entry#:
Userid: Domain:
Exec : calc.exe

LQ Command
This panel contains the following fields under XPJOB INFORMATION:

P Node
Identifies the primary node for this job. The job is routed to this node if the node is
available.
State
Identifies the state of the primary node following the latest attempt to route the
job to the indicated node. Values are the following:
Online
Specifies that the node is available and data can be sent.
Offline
Specifies that the node is unavailable due to a manual command. Data can be
sent to alternate nodes if defined.
Stop
Specifies that the node and its alternates are not available due to a manual
command. No attempts are made to send data to this node or its alternate
nodes.
Fail
Specifies that the node is unavailable due to a communications failure. Data
can be sent to alternate nodes if defined.
Unknown
Specifies that no attempts have been made to send data to this node. For
example, the job was submitted with an initial HOLD and has not been
released.
A Node
Identifies the alternate node that has been used by this job. If present, it indicates
that the primary node was not available and that the job has been routed to the
indicated alternate node.
SU Type
Identifies the type of switch user (SU) option to use on the target node.
Trace
Identifies whether activity for this job is being traced.

LQ Command
Entry#
Identifies a CA WA CA 7 Edition generated value used to uniquely identify this job
submission.
Userid
Identifies the user ID under which the executable runs.
Domain
Identifies the domain ID under which the executable runs.
Exec
Identifies the executable that is run on the target node.
LQ,LIST=AGJOB Panel
LQ,JOB=CA7AGJOB,LIST=AGJOB
LIST=AGJOB CA-7#=0005 DATE=YY.DDD PAGE 0001
CA7AGJOB REQ 0005 317/0708 317/0608 317/0708 WIN-AGJ 001 DEMD 002 R-JCLERR
-------------------------- AGENT INFORMATION --------------------------

Job Type: NT_JOB JobNo: 8612
Agent: UNIXAGT01 Status: SUBERROR Logon failure: unknown user name
User: user01
This panel contains the following fields under AGENT INFORMATION:

Job Type
Identifies the type of agent job.
JobNo
Identifies the job number assigned at the agent. Certain job types are not assigned
job numbers:
■ Monitors
■ Failed jobs due to invalid parameters
■ Security exceptions (status begins with SUBERROR)

LQ Command
Agent
Identifies the distributed platform where the job runs.
Status
Identifies the last reported status of the agent job.
User
Identifies the user ID under which the executable is to run.
ARF Information Section Messages

The following messages sometimes appear under the ARF Information section of the
LQ,LIST=ALL command. These messages further describe the cause of the E-ARFATT
status condition.
#ARFJI ERROR FOR nnnnnnnn ERR=xxxx/yyyy/zzzz
Reason:
An ARF internal error occurred. Issued by SASSARFA.
ARF ATTACH COMPLETE - nnnnnnnn
Reason:
ARF will begin monitoring exceptions defined for this run of the job. Issued by
SASSARFA.
ARF ENVIRONMENT ERROR
Reason:
One or more modules needed by ARF could not be located. Severe error. Issued by
SASSARFA.
ARHT ERR R15=xxxxxxxx, R0=yyyyyyyy, R1=zzzzzzzz
Reason:
An ARF internal error occurred. Issued by SASSAIIS, SASSAILE, SASSAILS, SASSAISC.

LQ Command
ARQM ERR R15=xxxxxxxx, R0=yyyyyyyy, R1=zzzzzzzz
Reason:
An ARF internal error occurred. Issued by SASSAIJC.
NO ARF TESTS FOR nnnnnnnn
Reason:
Although an ARFSET is associated with the job, no ARF definitions applied to this run of
the job. For example, if the only ARFSET definition specifies SID EQ 3 but the job 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.
UNABLE TO LOCATE ARF TRAILER
Reason:
The ARF segment in the trailer queue could not be located. ARF will not be able to
monitor this run of the job. Cancel the job and DEMAND it again. Issued by SASSARFA.

LQP Command
LQP Command
The LQP command lists current job VRM and WLB information for jobs in the request
and ready queues. The display shows the current resources and priorities that are
assigned to each job in the queue. You can also use this command when either VRM or
WLB is not active.
LQP[,AGENT={*|agent|mask}]
[,CLS=x]
[,LIST={CPU|STATUS}]
[,SCHID={0|nnn}]
[,SEQ={PRTY|JOB}]
[,ST=option]
AGENT
CLS
CPUID
information is selected for display. For agent jobs, use AGJ.
initiation record.

LQP Command
JOB
JOBL
LIST
(Optional) Specifies the options for the amount of information to list.
Default: Displays a single line for each job when omitted.
CPU
Lists the CPU jobs only.
NSUB
Serves as an alias for STATUS.
STATUS
Lists itemized status information messages about the jobs in the queues.
NODE
SCHID
(Optional) Specifies the schedule ID for which you want to select information.
SEQ
(Optional) Indicates the display sequence of the selected information.
PRTY
Indicates a descending job priority sequence. The workload balancing system
determines the current priority. PRTY is the default.
JOB

LQP Command
ST
(Optional) Specifies the display criteria for the queue information. If omitted, all
jobs in the request and ready queues are displayed.
Default: All jobs in the request and ready queues
ABND
AGENT
ARAE
ARF
ARFH
ARFJ
CBAD
COMP
HELD
JCLO
JCLR
Indicates that are in JCL or PARM error status.
LATE

LQP Command
MANV
MJOB
Indicates only jobs requeued because of multiple JOB statements.
NODE
NOID
REQU
RSTR
RTRY
SKEL
SUBM
WRSC
SYS
More information:

LQP Command
Examples
LQP,JOB=DUS*,SYS=*,LIST=STATUS
LQP,SEQ=PRTY
LQP,JOB=DUSAXX01
LQP Panel
LQP
SEQ=PRTY DATE=YY.DDD PAGE 0001
JOB QUE CA-7 JOB TAPE1 TAPE2 CPU START TIME PRIORITY
NAME NAME NMBR CLS NBR/PRTY NBR/PRTY %UTIL/PRTY MINS/PRTY ORIG/NEW
A REQ 0003 A 000/000 000/000 001.667/001 E046/001- 100/0100

CA07LOGX REQ 0007 A 000/000 000/000 001.667/001 E050/001- 100/0100
U7TST001 REQ 0005 A 000/000 000/000 001.667/001 E050/001- 100/0100
CA7PND01 REQ 0004 A 000/000 000/000 000.556/009- E046/001- 100/0090
LQP,LIST=STATUS Panel
LQP,LIST=STATUS
LIST=NSUB SEQ=PRTY DATE=YY.DDD PAGE 0001
BATCH002 REQ 0118 A 000/000 000/000 000.556/000 E052/001- 100/0099

. JOB IS IN REQUEST QUEUE
CA7FRCST REQ 0115 A 000/000 000/000 000.417/005- E045/001- 100/0094

. JOB IS ON HOLD
LQP,SEQ=JOB Panel
LQP,SEQ=JOB
SEQ=JOB DATE=YY.DDD PAGE 0001
A REQ 0003 A 000/000 000/000 001.667/001 E043/001- 100/0100

CA07LOGH REQ 0006 A 001/000 000/000 000.111/018- E031/001- 100/0081
CA07LOGX REQ 0007 A 000/000 000/000 001.667/001 E047/001- 100/0100
CA7PND01 REQ 0004 A 000/000 000/000 000.556/010- E043/001- 100/0089
U7TST001 RDY 0005 ? ..... JOB IS ALREADY SUBMITTED .....

LQP Command

JOB NAME
Indicates the name of the job as defined in the database. See NAME field on the job
definition panel.
QUE NAME
Indicates the queue where this job record currently resides. Values are REQ for
CA-7 NMBR
Indicates the CA WA CA 7 Edition assigned job number.
JOB CLS
Indicates the workload balancing class indication for this job. See CLASS field on the
DB.1 panel or WLBCLASS on the DB.10 panel.
TAPE1
Indicates the number of tape drives this job requires and the amount the original
priority of the job is adjusted due to tape drive use.
TAPE2
CPU %UTIL/PRTY
Indicates the calculated CPU use (using CLOCK-TIME and CPU-TIME from the DB.1
panel) and the amount that the original priority of the job is adjusted due to this
use.
START TIME
Indicates how early or late this job is and the amount that the original priority is
adjusted due to the start time factor.
PRIORITY
Indicates the original priority (priority when this command was entered) and the
new priority based on the rewards or penalties from the previous fields.
Usage Notes
For more information about possible nonsubmitted reasons when LIST=STATUS is
entered, see the usage notes for LRDYP command.
More information:
Usage Notes (see page 486)

LQR Command
LQR Command
The LQR command lists workload balancing information about all job resource
requirements from the CA WA CA 7 Edition queues. The queue information provided
shows current resource requirements for each job.
LQR[,AGENT={*|agent|mask}]
[,CLS=x]
[,LIST=CPU]
[,SCHID={0|nnn}]
[,ST=option]
AGENT
CLS
CPUID
initiation record.

LQR Command
JOB
JOBL
LIST=CPU
Default: blank
MAINID
(Optional) Specifies that only those jobs with this MAINID (as defined on the DB.1
panel) are to be listed. Jobs defined with MAINID of ALL are selected regardless of
MAINID entered.
Limits: MAINID is ignored for XPJOB jobs.
ALL
Specifies all MAINIDs. ALL is the default.
SYn
Where n indicates a CPU assigned number as defined in the initialization file
CPU statement for which information is to be listed. (For more information
about the initialization file, see the Systems Programming 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 to execute on CPUs other than SYn.
-SYn
Where n indicates a CPU assigned number for which information is not to be
listed. The value of n can range from 1 to 7.
NODE

LQR Command
SCHID
(Optional) Specifies the schedule ID for which information is to be selected.
SEQ
NATV
default.
AGENT
CA7
DLTM
DOTM
JOB
NODE
ST
jobs in the request, ready, and active queues are displayed.
Default: All jobs in the request, ready, and active queues
ABND
AGENT

LQR Command
ARAE
ARF
ARFH
ARFJ
CBAD
COMP
HELD
JCLO
JCLR
LATE
MANV
NODE
NOID

LQR Command
REPLY
Required message.
REQU
RSTR
RTRY
SKEL
SUBM
WRSC
SYS
More information:

LQR Command
Examples
LQR,JOB=DUS*,MAINID=SY3
LQR,MAINID=SY1
LQR
ACPBA01W PAYABLES ALL B/150 0010 00134/0026 003 001 06.03 *NONE*
ACPCA01W PAYABLES ALL B/100 0014 00238/0031 002 000 09.49 *NONE*
FXABA02M FIXASSET ALL A/120 0017 00043/0028 000 003 02.56 *NONE*
PERAB02M PERSONEL SY2 D/100 0018 00421/0121 004 000 05.37 *NONE*

JOB NAME
definition panel.
SYSTEM NAME
Indicates the system name as defined on the DB.1 panel.
MAINID
JOB C/PRT
Indicates the workload balancing class and priority for this job.
CPUID
■ For regular jobs, displays the CPU where the job is currently executing. The ID is
not filled in until CA WA CA 7 Edition processes the job initiation record.
■ For agent jobs, displays AGJ.
■ For XPJOBs displays 7XPJ.

LRDY Command
CA-7# NUMBR
CPU/ELAPS TIME
Indicates the CPU and CLOCK TIME from the DB.1 panel.
TOTAL TAPES
Indicates the number of TAPE1 devices, TAPE2 devices, or both that this job
requires.
CPU% UTIL
panel).
SUBMIT DATE/TIME
Indicates the Julian date and time this job was submitted.
LRDY Command
The LRDY command lists job information from the ready queue. This information
provides details on jobs that have all preexecution requirements satisfied and are only
waiting to be submitted to the host system. Jobs that have been submitted but have not
yet begun to execute remain in this queue until execution does begin and show a submit
time. Status, documentation, and JCL are among the information that can be displayed.
LRDY[,AGENT={*|agent|mask}]
[,CLS=x]
[,DRMODE={*|NO|YES}]
[,LIST=option]
[,SCHID={0|nnn}]
[,ST=option]
AGENT

LRDY Command
CLS
CPUID
initiation record.
DRCLASS
display.
@ANY
Specifies that jobs with any DRCLASS should be selected.
@NONE
Specifies that jobs with no DRCLASS should be selected.
DRMODE
*
YES
Indicates to select only jobs that entered the request queue while CA WA CA 7
NO

LRDY Command
JOB
JOBL
LIST
AGJOB
ALL
Indicates all data related to the job.
CPU
Indicates only CPU jobs.
JCL
Indicates JCL information only.
Depending on the security options selected for your installation, the following
values may be concealed in the display:
JOBL
Indicates the long job name information only.
PRM
PROS
Indicates documentation information only.

LRDY Command
Q
Indicates job data only.
RQMT
Indicates all requirements information only.
STATUS
Indicates requirements information only.
XPJOB
Indicates internal cross-platform information only.
for each queue record is listed. However, when a specific job is requested by the
JOB parameter, the default is LIST=STATUS and all job requirements are listed. If
SEG is specified, the default is LIST=PROS.
Note: If RQMT or STATUS is specified, VRM requirements are listed for jobs in the
ready queue with a status of W-RSRC.
NODE
SCHID
SEG
xxxxxxxx
(xxxxxxxx,yyyyyyyy)
Limits: 1 to 8 alphanumeric characters for each segment

LRDY Command
SEQ
NATV
default.
AGENT
CA7
Indicates CA WA CA 7 Edition assigned job number sequence.
DLTM
DOTM
JOB
NODE
ST
jobs in the ready queue are displayed.
ARF
ARFH
ARFJ
HELD

LRDY Command
LATE
SUBM
WRSC
SYS
More information:
Examples
LRDY
LRDY,JOB=G401
LRDY
PERAC01D RDY 0016 084/1649 084/1549 084/1649 SY2- 001 DEMD 000 LATE
WHSAA01D RDY 0019 084/1730 *NONE* 084/1800 ALL- 005 AUTO 000 RUSH

LRDY Command

JOB NAME
definition panel.
QUEUE NAME
RDY indicates that only the ready queue is listed.
CA-7 NUM
DEADLINE
Indicates a calculated time by which this job should be active on the CPU to be
SUB/START
Indicates the time that the job was written either to a submit data set or to the
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-OUT
Indicates the due-out time for the job.
CPU SPEC/RUN
Indicates two values. The SPEC value is what CPU this job should be submitted to
(see MAINID field on DB.1 panel). The RUN value is the system where it ran.
SCHID
Indicates the schedule ID assigned when this job was brought into the request
queue.
ENTRY MODE
Indicates how the job was brought into the queue. Values are the following:
ARFJ
ARF recovery job.
AUTO
Indicates triggered job.

LRDY Command
DEMD
Demanded job.
EXTL
Job submitted external to CA WA CA 7 Edition.
LOAD
Job record to be loaded (brought in by the LOAD command).
PS
Job submitted by Personal Scheduling System.
RPET
Repeated job.
RUN
Job brought in by the RUN command.
SSCN
Job record brought in by schedule scan.
XDEM
Job brought in by the DEMAND command from an XPS client.
XPS
Job brought in from an XPS client using the RUN command with the REF option.
XRUN
Job brought in from an XPS client using the RUN command.
MSTR REQ
Indicates the master requirement count. This field is zero for a job in the ready
queue.
JOB STATUS
Indicates a condition on this job record. Possible values are the following:
LATE
Indicates the job has not started by the DEADLINE DAY/TIME.

LRDYP Command
R-JCLERR
If the job is in the ready queue with this status, then a job purge record was
received before a job initiation record.
RUSH
LRDYP Command
The LRDYP command lists VRM or WLB information for jobs in the ready queue waiting
to be submitted. This command is similar to the LQP command. You can also use this
command when either VRM or WLB is not active.
LRDYP[,AGENT={*|agent|mask}]
[,CLS=x]
[,SCHID={0|nnn}]
[,SEQ={PRTY|sequence}]
[,ST=option]
AGENT
CLS
CPUID
initiation record.

LRDYP Command
JOB
JOBL
LIST
(Optional) Specifies the options for the amount of information to display.
Default: A single line for each job when omitted.
CPU
Lists CPU information only.
STATUS
Lists status information about the jobs in the queue.
NODE
SCHID
(Optional) Specifies the schedule ID for which to select information.
SEQ
PRTY
Information appears in descending job priority sequence. The workload
balancing system determines the current priority. PRTY is the default.
JOB
Information appears in job name sequence.

LRDYP Command
ST
ARF
ARFH
ARFJ
HELD
LATE
SUBM
WRSC
SYS
More information:

LQP Command (see page 462)

LRDYP Command
Examples
LRDYP
LRDYP,LIST=STATUS,SEQ=PRTY
LRDYP
SEQ=PRTY DATE=YY.DDD PAGE 0001
FXABA02M RDY 0371 A 000/000 003/050 008.000/010 E052/001- 100/0159

PERAC01D RDY 0016 ..... JOB IS ALREADY SUBMITTED .....

JOB NAME
definition panel.
QUE NAME
RDY indicates listing only the ready queue.
CA-7 NMBR
JOB CLS
Indicates the workload balancing class indication for this job. See CLASS field on the
DB.1 panel or WLBCLASS on the DB.10 panel.
TAPE1
TAPE2

LRDYP Command
CPU %UTIL/PRTY
panel) and the amount that the original priority of the job is adjusted due to this
use.
START TIME
Indicates how early or late this job is and the amount that the original priority is
adjusted due to the start time factor.
PRIORITY
Indicates the original priority (priority when this command was entered) and the
new priority based on the rewards or penalties from the previous fields.
Usage Notes
When LIST=STATUS is entered, the following non submittal reasons can display:
CA IAS Interface is not active
CA-11 IS NOT ACTIVE
CLASS BARRIER REACHED
CPU BARRIER REACHED
JOB IS IN REQUEST QUEUE
JOB IS LOCKED
JOB IS ON HOLD
JOB IS WAITING FOR VRM RESOURCES
JOB PRIORITY LESS THAN THRESHOLD VALUE
JOB SUBMITTED, AGENT NOT RESPONDING
JOB WILL EXCEED MAX AVAILABLE TAPE1 DRIVES
JOB WILL EXCEED MAX AVAILABLE TAPE2 DRIVES

LRDYR Command
NO INITIATORS AVAILABLE
SUBMIT DATASET BUSY OR ERROR
TYPE1 TAPE DRIVES LESS THAN ALLOWED PER JOB
TYPE1 TAPE DRIVES MORE THAN ALLOWED PER JOB
TYPE2 TAPE DRIVES LESS THAN ALLOWED PER JOB
TYPE2 TAPE DRIVES MORE THAN ALLOWED PER JOB
LRDYR Command
The LRDYR command lists outstanding (unsatisfied) job resource requirement
information about jobs in the ready queue. This command is similar to the LQR
command.
LRDYR[,AGENT={*|agent|mask}]
[,CLS=x]
[,LIST=CPU]
[,SCHID={0|nnn}]
[,ST=option]
AGENT
CLS

LRDYR Command
CPUID
initiation record.
JOB
JOBL
LIST=CPU
(Optional) Specifies to list only CPU jobs. LIST=CPU is the only valid option.
Default: blank
MAINID
(Optional) Indicates that only those jobs with this MAINID (as defined on the DB.1
panel) are to be listed. Jobs that are defined with MAINID of ALL are selected
regardless of MAINID entered.
ALL
Specifies all MAINIDs. ALL is the default.
SYn
Where n indicates a CPU for which information is to be listed. 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 to execute on CPUs other than SYn.
-SYn

LRDYR Command
NODE
SCHID
SEQ
NATV
default.
AGENT
CA7
Indicates information appears in CA 7 job number sequence.
DLTM
Indicates information appears in deadline time sequence.
DOTM
Indicates information appears in due-out time sequence.
JOB
Indicates information appears in job name sequence.
NODE

LRDYR Command
ST
ARF
ARFH
ARFJ
HELD
LATE
SUBM
WRSC
SYS
More information:

LQR Command (see page 468)

LRDYR Command
Examples
LRDYR
LRDYR,MAINID=SY2
LRDYR
JOB=FXABA02M DATE=YY.DDD PAGE 0001
FXABA02M FIXASSET ALL A/120 0017 00043/0028 000 003 02.56 00000/0000

JOB NAME
definition panel.
SYSTEM NAME
Indicates the system name as defined on the job definition panel.
MAINID
JOB C/PRT
Indicates the workload balancing class and priority for this job.
CPU ID
Not applicable.
CA-7# NUMBR
CPU/ELAPS TIME
Indicates the CPU and CLOCK TIME from the DB.1 panel.
TOTAL TAPES
Indicates the number of TAPE1 devices, TAPE2 devices, or both that this job
requires.

LREQ Command
CPU% UTIL
panel).
SUBMIT DATE/TIME
Indicates the Julian date and time this job was submitted.
LREQ Command
The LREQ command lists job information from the request queue for jobs that have
been scheduled into the queue, but still have preexecution requirements that must be
satisfied before the job can execute. Jobs that have completed successfully return
temporarily to the request queue for job completion processing. Jobs that run and
abnormally terminate are also returned to this queue to await restart by the user.
The LIST command has more information about displaying jobs waiting for a restart.
LREQ[,AGENT={*|agent|mask}]
[,CLS=x]
[,DRMODE={*|YES|NO}]
[,LIST=option]
[,SCHID={0|nnn}]
[,ST=option]
AGENT
CLS

LREQ Command
CPUID
initiation record.
DRCLASS
display.
@ANY
Specifies to select jobs with any DRCLASS.
@NONE
Specifies to select jobs with no DRCLASS.
DRMODE
*
YES
NO

LREQ Command
JOB
JOBL
LIST
AGJOB
ALL
Indicates all data that is related to the jobs.
CPU
Indicates only CPU jobs.
JCL
Indicates JCL information only.
Depending on certain security options that are selected for your installation,
the following values can be concealed in the display:
JOBL
PRM

LREQ Command
PROS
Indicates documentation information only.
Q
Indicates job data only.
RQMT
Indicates all requirement information only.
STATUS
Indicates unsatisfied requirement information only.
XPJOB
Indicates internal cross-platform information only.
for each queue record is listed. However, when a specific job is requested by the
JOB parameter, the default is LIST=STATUS and all unsatisfied job requirements are
listed. If SEG is specified, the default is LIST=PROS.
NODE
SCHID
SEG
xxxxxxxx
Defines the name of a segment.
(xxxxxxxx,yyyyyyyy)
The names of a segment (xxxxxxxx) and subsegment (yyyyyyyy) enclosed in
parentheses and separated by a comma.

LREQ Command
SEQ
NATV
default.
AGENT
CA7
DLTM
DOTM
JOB
NODE
ST
ABND
AGENT
ARAE
ARF
ARFH
ARFJ

LREQ Command
CBAD
COMP
HELD
JCLO
JCLR
LATE
MANV
MJOB
Indicates jobs containing multiple JOB statements status.
NODE
NOID
REQU
RSTR
RTRY
SKEL

LREQ Command
SYS
More information:

LIST Command (see page 355)
Examples
LREQ,ST=HELD,SEQ=JOB
LREQ
JOB=ACPBA01W DATE=YY.DDD PAGE 0001
ACPBA01W REQ 0016 084/1649 084/1549 084/1649 SY2- 001 DEMD 000 LATE

JOB NAME
definition panel.
QUEUE NAME
Indicates the queue where this job record currently resides. Values are REQ for
CA-7 NUM

LREQ Command
DEADLINE
Indicates a calculated time by which this job should be active on the CPU to be
SUB/START
For 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 the JCL was
written to the submit data set or internal reader. Until the first SMF step
termination record is received, this field shows *NONE* for a job in the active
queue.
DUE-OUT
Indicates the due-out time for the job.
CPU SPEC/RUN
Indicates two values. The SPEC value is what CPU this job should be submitted to
(see MAINID field on DB.1 panel). The RUN value is the system where it ran.
SCHID
Indicates the schedule ID assigned when this job was brought into the request
queue.
ENTRY MODE
Indicates how the job was brought into the queue. Values are the following:
ARFJ
ARF recovery job.
AUTO
Triggered job.
DEMD
Demanded job.
EXTL
Job submitted external to CA WA CA 7 Edition.
LOAD
Job record to be loaded (brought in by the LOAD command).
PS
Job submitted by Personal Scheduling System.

LREQ Command
RPET
Repeated job.
RUN
Job brought in by the RUN command.
SSCN
Job record brought in by schedule scan.
XDEM
Job brought in by the DEMAND command from an XPS client.
XPS
Job brought in from an XPS client using the RUN command with the REF option.
XRUN
Job brought in from an XPS client using the RUN command.
MSTR REQ
Indicates the number of outstanding master requirements for a job record.
JOB STATUS
Indicates the job's current disposition. Values are the following:
A-Snnnn
A-Unnnn
C-Cnnnn
processing.
E-ARFATT
Indicates an error occurred during the attempt to attach ARF definitions. This
can result if the ARFSET specified is not defined. A diagnostic message may
have been written to the CA WA CA 7 Edition log, the OS console, or to the
trailer queue for the job (in which case you can view it using
LQ,JOB=x,LIST=ALL).

LREQ Command
E-SEGERR
Indicates the job has been requeued to the request queue because the CA WA
CA 7 Edition job submission task was unable to read a security segment for the
job.
LATE
LOADING
Indicates the job completed execution of a LOAD-only run and is completing
the LOAD process. This status is for jobs in the request queue.
N-FAIL
For XPJOB jobs, indicates that the node to which this job should be directed
could not be contacted through CAICCI Services. For agent jobs, indicates that a
problem occurred contacting the agent.
N-IAS
For agent jobs, indicates a problem exists with component CA IAS (Integrated
Agent Services) or that AGENTJOB=NO is specified or defaulted in the
initialization file.
N-OFFL
Indicates the node is in an offline status in the CA WA CA 7 Edition internal
node table. There are no alternate nodes defined, or if there are, those
alternates are also in an offline status or could not be contacted through CAICCI
Services.
N-STOP
Indicates the node is in a STOP status in the CA WA CA 7 Edition internal node
table.
N-XTRK
Indicates the CA WA CA 7 Edition Tracker is not defined or active in this CA WA
CA 7 Edition such that cross-platform tracking may occur. Instead of submitting
the job when no tracking facility is available, CA WA CA 7 Edition places the job
in this status.
QJCL
Indicates this job is in the request queue with zero master requirements. At the
time the command was issued, CA WA CA 7 Edition was processing a SAVE or
REPL function on the QM.5 (QJCL) panel for this job.

LREQ Command
R-#nnnn
R-Cnnnn
R-JCLERR
was received before a job initialization record.
R-MJOB
Indicates the job has been requeued because multiple JOB statements were
found within job's JCL while the current security settings prevent this.
R-NOUID
During submission, if no valid USERID is available, a check of the SUBNOID
parameter is done to determine if a job can be submitted without an ID. With
SUBNOID set to NO, the job is moved back to the request queue with a status
of R-NOUID.
R-REQUE
Indicates the job has been requeued to the request queue using the REQUEUE
command or the Q function on the QM.1 panel.
R-TRLFUL
At the time the job was active, CA WA CA 7 Edition required another track to be
obtained from the trailer queue to hold outputs. At the time that CA WA CA 7
Edition tried to get another track, either an out of space condition or an I/O
error occurred.
RETRY
Indicates a dynamic allocation error occurred during attach of JCL for this job.
At a user-specified time interval, a retry of the JCL attach occurs.
RQMT-INC
RUSH
SKELETON

LREQP Command
LREQP Command
The LREQP command lists current job priority information about each job in the request
queue. This command is similar to the LQP command.
LREQP[,AGENT={*|agent|mask}]
[,CLS=x]
[,SCHID={0|nnn}]
[,SEQ={PRTY|JOB}]
[,ST=option]
AGENT
CLS
CPUID
initiation record.

LREQP Command
JOB
JOBL
LIST
(Optional) Specifies options for the amount of information to display.
Default: A single line for each job when omitted.
CPU
Lists CPU information only.
STATUS
Lists status information about the jobs in the queue.
NODE
SCHID
(Optional) Specifies the schedule ID for which to select information.
\
SEQ
PRTY
Descending workload balancing job priority sequence. Workload balancing
determines the priority. PRTY is the default.
JOB
Job name sequence.

LREQP Command
ST
ABND
AGENT
ARAE
ARF
ARFH
ARFJ
CBAD
COMP
HELD
JCLO
JCLR
LATE

LREQP Command
MANV
NODE
NOID
REQU
RSTR
RTRY
SKEL
SYS
More information:
Examples
LREQP,JOB=DUSA*,SEQ=PRTY,SYS=SYS1
For panel samples, see the LQP command panel examples.
More information:
LQP Command (see page 462)

LREQR Command
LREQR Command
The LREQR command lists resource requirement information for jobs in the request
queue. This command is similar to the LQR command.
LREQR[,AGENT={*|agent|mask}]
[,CLS=x]
[,LIST=CPU]
[,SCHID={0|nnn}]
[,SEQ={NATV|AGENT|CA7|DLTM|DOTM|JOB|NODE}]
[,ST=option]
AGENT
CLS
CPUID
initiation record.

LREQR Command
JOB
JOBL
LIST=CPU
MAINID
(Optional) Indicates that only those jobs with this MAINID (as defined on the DB.1
panel) are to be listed. Jobs defined with MAINID of ALL are selected regardless of
MAINID entered.
Limits: MAINID is ignored for cross-platform jobs.
ALL
Specifies all MAINIDs.
SYn
CPU statement for which information is to be listed. (For more information
about the initialization file, see the Systems Programming 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 to execute on CPUs other than SYn.
-SYn
NODE
SCHID
(Optional) Specifies the schedule ID for which to select information is to be
selected.

LREQR Command
SEQ
NATV
default.
AGENT
CA7
DLTM
DOTM
JOB
NODE
ST
ABND
AGENT
ARAE
ARF
ARFH

LREQR Command
ARFJ
CBAD
COMP
HELD
JCLO
JCLR
LATE
MANV
NODE
NOID
REQU
RSTR
RTRY
SKEL

LREQR Command
SYS
More information:

LQR Command (see page 468)
Examples
LREQR,MAINID=SY1
LREQR
FXABA02M FIXASSET ALL A/120 0017 00043/0028 000 003 02.56 00000/0000
PERAF03M PERSONEL SY2 D/100 0018 00421/0121 004 000 05.37 00000/0000
WHSAA01D WAREHOUS ALL C/100 0019 00149/0046 000 003 03.95 00000/0000
WHSAB03W WAREHOUS ALL C/100 0012 00351/0057 000 000 06.75 09084/1549

JOB NAME
definition panel.
SYSTEM NAME
Identifies the system name as defined on the job definition panel.
MAINID
Identifies the value from the MAINID field on the DB.1 panel.

LRES Command
JOB C/PRT
CPUID
Identifies the CPU where the job executed if the job is in restart status. The ID is not
filled in until CA WA CA 7 Edition processes the job initiation record. For agent jobs,
displays AGJ. For XPJOBs displays 7XPJ.
CA-7# NUMBR
CPU/ELAPS TIME
Identifies the CPU and CLOCK TIME from the job definition panel.
TOTAL TAPES
Identifies the number of TAPE1 devices, TAPE2 devices, or both that this job
requires.
CPU% UTIL
Identifies the calculated CPU use (using CLOCK-TIME and CPU-TIME from the DB.1
panel).
SUBMIT DATE/TIME
Identifies the Julian date and time this job was submitted.
LRES Command
The LRES command lists the resources that jobs in the database or queues require.
Magnetic tape, memory, and CPU time requirements are shown for any job or group of
jobs that the user specified.
Note: Cross-platform jobs are listed, but because they execute on other platforms, their
resource usage reflects 0 (zero).
LRES,{Q=queue|SYS=system|JOB={jobname|NO}}
Q
Specifies the resource information desired. If Q is specified, omit SYS.
ACT
Active queue
ALL
All queues

LRES Command
RDY
Ready queue
RDYACT
Ready and active queues
REQ
Request queue
REQACT
Request and active queues
REQRDY
Request and ready queues
SYS
Specifies that resource information is desired about all jobs in the database for this
application system. The option must be a system name. If SYS is specified, omit Q.
Required: Yes, unless Q is specified.
JOB
Specifies the job about which resource information is desired. If you omit JOB,
resource information about all jobs is given based on whether you specified SYS or
Q.
Required: Yes, unless SYS or Q was specified.
jobname
Defines a specific job in the database. The JOB value is a specific job name. If
specified, omit SYS and Q.
NO
When JOB=NO is specified, either SYS or Q must be used. JOB=NO causes the
job detail lines of resource information (system or queue) to be suppressed and
only the summary lines are listed.

LRES Command
Examples
LRES,JOB=T2TSOPAK
LRES,Q=ACT
LRES,SYS=S168 Panel
LRES,SYS=S168
SYS=S168 DATE=YY.DDD PAGE 0004
JOB CPUTM *-CORE USAGE-* *----TAPE USAGE----*

NAME MM.SS HIGH USING-STP HIGH USING-STP TOTAL
T2TSOPAK 01.16 256K *ALL* 1 DUMP 1

T2TSOPK3 00.34 256K *ALL* 1 DUMP 1
T2WKLY1 01.42 512K *ALL* 0 *NONE* 0
T210USLB 00.01 90K *ALL* 0 *NONE* 0
T211BKUP 00.10 256K *ALL* 1 CMTBKUP 2
*SYS 69.58 5825K 44 65
SLIU-00 REQUEST COMPLETED AT 17:14:52 on YY.DDD

JOB NAME
definition panel.
CPUTM
Identifies the historical CPU time for this job. See CPU-TIME on the DB.1 panel.
CORE USAGE
Identifies the core requirement and the name of the step with the highest usage.
TAPE USAGE
Identifies the tape drive usage for this job showing the step name of the step that
uses the high-water mark for tape drives and the total number of tape drives used
by this job.

LRLOG Command
LRLOG Command
The LRLOG command lists information from the CA WA CA 7 Edition run log. The run log
contains the information about certain events that occur during CA WA CA 7 Edition
processing. These events include job and network completions and exception events
such as restarts, force completes, and cancels.
The run log maintains data for the previous n number of days. The default is to retain
five days of run log data. That is the current date, up to the moment, and the four
previous calendar days.
An option in the CA WA CA 7 Edition initialization file controls the number of days

retained.
Note: For more information, see the RLOGDAYS keyword on the DBASE statement in the
Systems Programming Guide.
LRLOG[,DATE={*|*yyddd}]
[,JOB={*|jobname|mask}]
[,LIST={ALL|option}]
[,NW={*|network|mask}]
[,OPT={0|1}]
[,SCHID={0|nnn}]
[,SEQ={DATE|sequence}]
[,SPAN={current date}]
{*}
{scope}
{date}
{(start date,start time,scope)}
{(start date,start time,end date,end time)}
[,ST={*|option}]
[,TZ={CA7|EXEC}]
DATE
(Optional) Specifies the dates of the information requested.
*
Specifies all days in the run log. As supplied, the system contains five days of
data.
*YYDDD
Defines 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 be within the last five
calendar days.

LRLOG Command
JOB
(Optional) Defines the job name or mask that a job name must match before its
LIST
(Optional) Controls what types of objects are selected.
ALL
Selects all types of objects (all jobs and networks). ALL is the default.
AGJOB
Selects only agent jobs.
CPU
Selects only CPU jobs.
INW
Selects only input network related events.
JOB
Selects only job related events.
NW
Selects only network related events.
ONW
Selects only output network related events.
XJOB
Selects only external job related events. An external job is one that is tracked
by CA WA CA 7 Edition even though CA WA CA 7 Edition did not submit it.
XPJOB
Selects only internal cross-platform information.
Note: The old option RSTR is still accepted. It is processed as if ST=RSTR were
entered.

LRLOG Command
NW
OPT
(Optional) Controls the output format of the data displayed. This keyword allows
you to have the run log data displayed in the pre-Release 3.2 format. If you want to
see run log data in the same manner it was presented in previous versions, specify
OPT=1 on the LRLOG command.
0
Displays run log data in the Release 3.2 and above format. This value is the
default.
1
Displays run log data in the pre-Release 3.2 format.
Note: If you have Batch Terminal (BTI) jobs that extract run log data for further
processing and it is expecting the pre-Release 3.2 format, you can specify a
default Batch LRLOG format in the CA WA CA 7 Edition initialization file. See the
RLOGBDEF keyword on the OPTIONS statement in the Systems Programming
Guide.
SCHID
(Optional) Indicates to only select events with a specific schedule ID.
Limits: 1 to 3 numeric from 1 through 999
SEQ
(Optional) Controls the display sequence of the selected run log data.
DATE
Date and time sequence. DATE is the default.
JOB
Job name, and date/time sequence within jobs with the same name.
NW
Network name, and date/time sequence within networks with the same name.

LRLOG Command
REV
Reverse date and time sequence.
SUBID
Sub-ID, and date/time sequence within networks with the same Sub-ID.
Note: The old option NATV is still accepted. However, it is processed the same
as the DATE option.
SPAN
(Optional) Run log records are searched for the time period specified or implied by
this keyword. It can be expressed as a scope, a starting date/time and scope, or as a
date and time range. This keyword is mutually exclusive with the DATE= keyword.
Default: Current date
*
Searches all run log data.
scope
Use this format to search most current information in the run log for a fixed
period. The starting time is calculated as the current time minus the scope. The
ending time is the current time. The scope can be expressed as a number of
hours (one to three digits), or as hours and minutes (four digits).
SPAN=8 Search the last 8 hours.
SPAN=0130 Search the last 1 hour and 30 minutes.

LRLOG Command
date
Use this format to search the run log data for a specific date. The date can be
expressed as a five-digit Julian date (YYDDD), or as a six-digit Gregorian date
(MMDDYY).
SPAN=09001 Search Jan 1, 2009 (entire day).
SPAN=010209 Search Jan 2, 2009 (entire day).
(start date, start time, scope)

Use this format to express a starting point and a fixed amount of time forward
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) or Gregorian
date (six digits).
The starting time can be expressed as hhmm (4 digits) where hh is the hour
(00-24) and mm is the minutes (00-59). If no time is specified the default is the
beginning of the day (0000).
The scope can be expressed as a number of hours (one to three digits), or as
hours and minutes (four digits).
SPAN=(09001,1300,8) Jan 1, 2009 (1:00 pm - 9:00 pm)
SPAN=(010209,1200,24) Jan 2, 2009 (noon) - Jan 3, 2009 (noon)
(start date, start time, end date, end time)

Use this format to express both a starting and ending point for the selection
window.
The dates can be expressed as Julian dates (five digits) or Gregorian dates (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 the default is the
beginning of the day (0000). If no end time is specified the default is the end of
the day (2400).
SPAN=(09001,1200,09002,0800) Jan 1 (noon) - Jan 2 (8 am)
SPAN=(010209,,010309) All of Jan 2 and Jan 3, 2009

LRLOG Command
ST
(Optional) Controls what types of events are selected.
*
Selects all types of events. This value is the default.
CANCEL
Selects only job and network cancel events.
COMP
Selects only job and network completion events.
EXCP
Selects only exception events. That is, only non-completion events are selected
(cancel, force complete, requeue, and restart).
FORCE
Selects only force complete events.
LATE
Selects only job and network completion events where the completion was
considered late by CA WA CA 7 Edition.
RSTR
Selects only restart events.
Note: The old option CANC is still accepted. It is processed the same as the
CANCEL option.
SUBID
SYS

LRLOG Command
TZ
(Optional) Controls whether a job's start and completion date/times should be
statement.
CA7
Defines that the start and completion date/times should be normalized to the
running CA WA CA 7 Edition time zone.
EXEC
Defines that the start and completion date/times should be in the execution
time zone.
More information:
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=0030 Previous 30 minutes.
LRLOG,SPAN=yy001 January 1, 20yy (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 a
system name of PAYROLL. Select only
exception events (cancel, force, restart).

LRLOG Command
LRLOG Panel
LRLOG
EVENT OBJECT ENTRY TRGR LATE

TYPE TIME TYPE NAME CA7# SCH SYSTEM STATUS MODE CA7# START END
C yy061/0759 J CA07LOGP 0017 001 COMP DMND 0000 yy061/0759 yy061/0759

C yy061/0907 I TESTINNW 0018 001 DMD#0018 DMND 0000 00000/0000 yy061/0907L
SUBID= DESC=TESTINNW INITS=BDWASHE
C yy061/0917 O TESTOTNW 0020 001 DMD#0020 COMP DMND 0000 00000/0000 yy061/0917L
R yy061/1432 J FSTAT009 0997 001 FSTATUS JCLER AUTO 0993
REASON= RESTARTED TO GENERATE RLOG REC
X yy061/1434 J P4 0798 001 DMND 0000
F yy061/1435 J FSTAT009 0997 001 FSTATUS JCLER AUTO 0993 L
REASON= FINALLY FORCE IT
C yy061/1435 J FSTAT009 0997 001 FSTATUS FCOMP AUTO 0993 yy061/1435 yy061/1435L
C yy061/1437 J CA07TZ01 0019 001 FSTATUS COMP DMND 0000 yy061/1436+yy024/1437

EVENT TYPE
Identifies the type of event.
C
Completion
F
Force Complete
R
Restart
X
Cancel (CA WA CA 7 Edition)
EVENT TIME
Identifies a date and time that the event was written to the run log. The date is in
Julian format and the time is in hours (HH) and minutes (MM).
OBJECT TYPE
Identifies a type of object that was involved with this event.
J
Specifies a job.
J+
Specifies an internal cross-platform job.

LRLOG Command
J-
Specifies an external job.
I
Specifies an input network.
O
Specifies an output network.
OBJECT NAME
Identifies the name of the job or network that the event relates to. If it is a
network-related event, this field reflects the actual network name.
CA-7#
Identifies the CA WA CA 7 Edition assigned job or network reference number.
SCH
Identifies the CA WA CA 7 Edition schedule ID.
SYSTEM
For job entries, the system name. For network entries, the generated job name for
this execution of the network.
STATUS
Identifies the status of the network or system status of the job.
#nnnn
Step level condition code.
CANCL
Cancel (See RLOGCAN in the OPTIONS statement of the initialization file in the
Systems Programming Guide.)
Cnnnn
Job level condition code.
COMP
Normal Completion.
FAIL
Special job UCC7Rxx failed.
FCOMP
Force Complete.
JCLER
JCL Error.

LRLOG Command
MJOB
Requeued because of multiple JOB statements.
N-xxx
Unsuccessful completion due to node status (xxx is the node status).
REQUE
Requeued.
Snnn
Abnormal System Completion (nnn = abend code).
Unnnn
Abnormal User Completion (nnnn = completion code).
ENTRY MODE
Identifies the entry mode of the job or network.
ARFJ
ARF recovery job.
AUTO
Trigger.
DMND
DEMAND command.
LOAD
LOAD command. (LOAD jobs that are successful do not have a runlog entry.
Only those LOAD jobs that fail, and are then canceled, have an entry.)
PS
Personal Scheduling.
RPET
Repeated job.
RUN
RUN command.
SSCN
Schedule scan.
XDEM
DEMAND command from an XPS client.

LRLOG Command
XPS
XPS client using the RUN command with the REF option.
XRUN
XPS client using the RUN command.
TRGR CA7#
If the object was brought into the system through a trigger, or as an ARF recovery
job, this field contains the CA 7 job number of the triggering object. Otherwise, it is
zero. For U7SVC D=dsname data sets and externally tracked data sets that trigger a
job, this value is built from the time when the data set record was created. The
value must be unique to prevent possible duplicate triggers. This value uses the
seconds and hundredths of seconds in the building of this field.
START
Starting date and time for event type of C (and other event types as available). A
plus sign displayed immediately after the field indicates that the job's start and
completion dates/times are normalized to the time zone of the running CA WA CA 7
Edition.
END
Completion date and time for event type of C (and other event types as available).
LATE
An L at the end of the completion time indicates that the job or network was
considered late by CA WA CA 7 Edition.
Note: Differences between clocks on multiple CPUs may distort the determination
of a job's LATE status.
SUBID=
For input and output network events, an additional line is displayed showing the
network sub-ID, description, and any initials supplied during the logout of the last
workstation.
REASON=
For force complete, restart, and cancel events, an additional line displays the
reason text when a reason is supplied for the action.

LRMD Command
LRMD Command
The LRMD command lists reminder (prompting) information from the CA WA CA 7
Edition preprocess queue. Such information is first defined into an active area using the
CA WA CA 7 Edition editor, and scheduled for display at a workstation with the REMIND
command. A free-form message can be defined to communicate anything to a
workstation at a predetermined time. The workstation operator is prompted,
repeatedly if necessary, to review the defined text. The REMIND command schedules
these free-form messages.
LRMD[,JOB={*|jobname|jobnumber|mask}]
[,SEQ={NATV|CA7|DLTM|DOTM|JOB|STA}]
[,ST={*|LATE}]
[,STN={*|station|mask}]
JOB
SEQ
(Optional) Controls the display sequence of the remind messages.
NATV
Native sequence (the order in which it is in the queue). NATV is the default.
CA7
CA WA CA 7 Edition assigned number sequence.
DLTM
Deadline time sequence.
DOTM
Due-out time sequence.
JOB
Job name sequence.
STA
Station name sequence.

LRMD Command
ST
(Optional) Specifies the display criteria of the remind messages.
*
All of the reminder text. This value is the default.
LATE
Only the late reminder text.
STN
More information:

REMIND Command (see page 619)
Examples
LRMD
LRMD,ST=LATE,STATION=KEYPUNCH
LRMD,JOB=RMD#0004
LRMD,ST=LATE,SEQ=STA

LSCHD Command
LRMD Panel
LRMD
LIST=JCL DATE=YY.DDD PAGE 0001

0009001 SUPVISOR CONTROL RMD#0009 121/1000 121/1640 121/1000 CONTROL

------------------------ REMINDER INFORMATION -------------------------
*
* DON'T FORGET !!!!!!!!!!!!!!!!
*
* THERE WILL BE A MEETING JULY 10, 20yy AT 10:30 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.
*
LSCHD Command
The LSCHD command lists schedule information from the database for jobs or networks.
You can limit this display to certain systems or stations. You can review schedules for
networks and stations as well as processing calendars for input networks. Information
provided includes scheduling parameters, variations by schedule ID, and
month-by-month calendars.
LSCHD,{JOB={*|jobname|jobname*}|JOBL=[longjobname|mask|*}|NW={*|network}}
[,LIST={BYSID|CALS|SCHD|SIDnnn}]
[,SCAL=xx]
[,ST={EXP|JAN|JUL|MOD|NRV|REPEAT|REPT|RPET}]
JOB
Specifies the jobs whose schedule members are to be listed. JOB can be used with
SYS. We recommend that online LSCHD commands limit the number of jobs
displayed.
Required: Yes, unless JOBL or NW is used
*
Specifies all job schedules. This value is the default.

LSCHD Command
jobname
jobname*
JOBL
Specifies the jobs whose schedule members are to be listed. JOBL can be used with
SYS. We recommend that online LSCHD commands limit the number of jobs
displayed.
Required: Yes, unless JOB or NW is used
longjobname
Defines a specific long job name.
longjobname*
*
Specifies all job schedules.
NW
Specifies the networks whose schedule members are to be listed. If JOB, JOBL, or
SYS is used, NW must be omitted.
Required: Yes, unless JOB, JOBL, or SYS is used
*
Specifies all networks. This value is the default.
network
Defines the network name.

LSCHD Command
LIST
(Optional) Specifies list options for the schedule data to print. If omitted, only
information that is used to define selected schedules is displayed. For unresolved
schedule members, no schedule day calendars are available for display. This
keyword is mutually exclusive with ST.
BYSID
A month-by-month schedule day calendar for each schedule ID in the selected
members. Valid only for RESOLVed schedules.
CALS
A month-by-month schedule day calendar using the schedule data selected.
This calendar is a composite calendar reflecting all selected schedule IDs. If
used with JOB=*, the display could be lengthy. Use a batch terminal for this
combination. Valid only for RESOLVed schedules.
Note: Output workstation network schedule members do not have composite
calendars. Therefore, no calendar is printed for output workstation network
schedules.
SCHD
All schedules. Where jobs are involved (through keywords JOB or SYS)
information about all the jobs, data sets, or both that trigger the job under
consideration is listed as well as all jobs triggered by the job under
consideration.
SIDnnn
A month-by-month schedule day calendar for one schedule ID that the nnn
value specifies (leading zeros are required). Valid only for RESOLVed schedules.
SCAL
(Optional) Designates a specific base calendar identifier. Used for selecting only
schedules that reference this calendar.
ST
(Optional) Specifies a type of schedule to select. Primarily for generic requests. If
omitted, all types are listed according to other selection criteria. This keyword is
mutually exclusive with LIST.
EXP
Schedules that have expired.
JAN
January through December schedules.

LSCHD Command
JUL
July through June schedules.
MOD
Schedules that have been changed through the DB.2.7 panel.
NRV
Schedules that have never been resolved.
REPEAT|REPT|RPET
Schedules that have at least one schedule ID with a repeat definition.
SYS
(Optional) Specifies an application system name as defined on the job definition
panel for each job, for which the display is desired. If JOB is also used, only those
jobs meeting both the JOB and SYS criteria are displayed. (The SYS=systemname
parameter is not valid when a specific job name is specified.)
*
Specifies all application system names. This value is the default.
systemname
Defines a specific application system name.
mask
Defines a generic application system name.
Limits: 1 to 7 alphanumeric characters, terminated with an asterisk
More information:
Examples
LSCHD,LIST=CALS,NW=*
LSCHD,NW=JOBNET6
LSCHD,JOB=CA7JOB1,LIST=BYSID
The COMMENTS field on the display always contains values similar to the ST options,
even if ST was not requested, to indicate type of schedule and its current status.

LSCHD Command
LSCHD,JOB=DUSAXX01,LIST=BYSID Panel
LSCHD,JOB=DUSAXX01,LIST=BYSID
LIST=BYSID JOB=DUSAXX01 DATE=YY.DDD PAGE 0001
JOB SYSTEM SCHEDULE #SCH -BASE CALENDAR- PROSE COMMENTS

NAME NAME IDS USERID B-DATE NUM
DUSAXX01 PAYABLES YES 002 SCAL12PE yyddd PP000865

JANUARY SCHEDULE
SCHDMOD CURRENT
. LAST MAINTENANCE ON yy.ddd AT hh:mm:ss VIA DBM BY OPERATOR: nnnnnnn
. LAST RESOLV ON yy.ddd AT hh:mm
------------------------------ SCHEDULES ------------------------------
CALENDAR SCAL12PE
SCAL=PE DOTM=0800 LEADTM=0010 STARTM=0750
DAILY
SCAL= DOTM=0800 LEADTM=0010 STARTM=0750
WEEKLY DAY=MON
SLIG-00 REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

JOB NAME
Identifies the name of the job as defined in the database.
SYSTEM NAME
Identifies the value defined in the SYSTEM field on the job definition panel.
SCHEDULE
#SCH IDS
Identifies the number of variations (SCHIDs) for this job's schedule.
BASE CALENDAR USERID
Identifies the name of the base calendar used in RESOLVing this schedule.
BASE CALENDAR B-DATE
Identifies the assembly date of the base calendar used in RESOLVing this schedule.

LSCHD Command
PROSE NUM
Identifies the DSNBR assigned to the documentation for this job.
COMMENTS
Under this heading one or more of the following values can appear:
JANUARY SCHEDULE|JULY SCHEDULE
A schedule resolved between January 1 and June 30 has a January (JAN)
schedule, and one resolved between July 1 and December 31 has a July (JUL)
schedule.
NXTCYC=OFF
The schedule is suspended from execution until it is reset by an NXTCYC=ON
command.
NXTCYC=SKP
The next execution of this scheduled job is skipped, but subsequent cycles are
scheduled.
SCHDMOD CURRENT
The schedule member has been updated through the SCHDMOD panel.
SCHDMOD OVERLAID
The schedule member received a modification through the DB.2.7 panel, and a
top line RESOLV command was issued that caused the schedule to revert to the
original schedule information.
SCHED BEG mmm yy
The schedule will begin in the month mmm (JAN or JUL) of the year yy.
SCHED IS EXPIRED
The schedule needs to be re-resolved because it has been over a year since the
last RESOLV.
SCHED NEEDS RESOL
The schedule has been changed through the DB.2.1-E panel and saved to the
database but not resolved.

LSCHD Command
LSCHD,NW=INPUTNWK,LIST=BYSID Panel
LSCHD,NW=INPUTNWK,LIST=BYSID
LIST=BYSID NW=INPUTNWK DATE=YY.DDD PAGE 0001
NETWORK #OF NETWORK SCHEDULE #SCH -BASE CALENDAR- COMMENTS

NAME STNS NBR IDS USERID B-DATE
INPUTNWK 01 N/A YES 002 SCAL11PE yyddd JULY SCHEDULE

. LAST MAINTENANCE ON 00.000 AT 00:00:00 VIA DBM BY OPERATOR:
. LAST RESOLV ON yy.ddd AT 16:49
------------------------------ SCHEDULES ------------------------------
CALENDAR SCAL11PE
DAILY
DAILY

NETWORK NAME
Identifies the name of the network as defined in the database. See NAME on the
DB.2.2 panel.
# OF STNS
Identifies the number of stations (LTERMs) defined for this network.
NETWORK NBR
N/A. Networks no longer have numbers.
SCHEDULE
#SCH IDS
Identifies the number of variations (SCHIDs) for this network's schedule.
BASE CALENDAR USERID
Identifies the name of the base calendar used in resolving this schedule.

LSCHD Command
BASE CALENDAR B-DATE

Identifies the assembly date of the base calendar used in resolving this schedule.
COMMENTS
Under this heading one or more of the following values can appear:
JANUARY SCHEDULE|JULY SCHEDULE
A schedule RESOLVed between January 1 and June 30 has a January (JAN)
schedule, and one RESOLVed between July 1 and December 31 has a July (JUL)
schedule.
SCHDMOD CURRENT
Indicates the schedule member has been updated through the DB.2.7 panel.
SCHDMOD OVERLAID
Indicates that the schedule member received a modification through the
DB.2.7 panel, and a top line RESOLV command was issued that caused the
schedule to revert to the original schedule information.
SCHED BEG mmm yy
Indicates that the schedule begins in the month mmm (JAN or JUL) of the year
yy.
SCHED NEEDS RESOLUTION
Indicates that the schedule has been changed through the DB.2.1-E panel and
saved to the database but not RESOLVed.
SCHEDULE IS EXPIRED
Indicates that the schedule needs to be re-RESOLVed because it has been over
a year since the last RESOLV.

LSYS Command
LSYS Command
The LSYS command lists database information for all jobs that are defined in a specific
application system. This information includes input/output data set cross references for
each job. The information is similar to that included with the LJOB command. The
command lets you review all jobs within an application system with one command.
Note: To get the job information that is based on a generic or a masked job name, use
the LJOB command.
LSYS,{SYS=system|JOB=jobname|JOBL=longjobname}[,LIST=option]
SYS
Identifies an application system for which you want to list information. The value is
a specific application system name. If SYS is specified, omit JOB or JOBL.
Required: Yes, unless JOB or JOBL is used.
JOB
Identifies a particular job name for which you want to list information. If JOB is
specified, omit JOBL and SYS.
Required: Yes, unless JOBL or SYS is used.
JOBL
Identifies a particular long job name for which you want to list information. If JOBL
is specified, omit JOB and SYS.
Required: Yes, unless JOB or SYS are used.
LIST
(Optional) Specifies the options for the printed information. If SYS is specified and
LIST is not specified, a single line describing each job is output.
AGJOB
Lists the agent information for the application systems specified. This value is
the default for agent jobs.
ALL
Lists the jobs, schedules, and data set dependencies, and internal
cross-platform information for the application system specified.

LSYS Command
DEP
Lists the jobs and data set dependencies for the application systems specified.
This value is the default for the JOB option for CPU jobs.
JOBS
Lists the job data only for jobs in the application systems specified.
SCHD
Lists the jobs within the application systems that are specified with their
schedules.
XPJOB
Lists the XPJOB information for the application systems specified. This value is
the default for the XPJOB jobs.
Examples
LSYS,SYS=CA7JOBS
LSYS,SYS=CA7JOBS,LIST=JOBS
LSYS,SYS=CA7JOBS,LIST=SCHD
LSYS,SYS=TESTNTWK
SYS=TESTNTWK DATE YY.DDD PAGE 0002
ANAJFM01 007 CA75LG31 TESTNTWK 000 /SY2 *NONE* NO 000 000 0000 00000/0000
ANAJFM03 007 CA75LG31 TESTNTWK 000 /SY2 *NONE* NO 000 000 0000 00000/0000
CA07CLEN 200 CA07CLEN TESTNTWK 000 ALL *NONE* NO 002 007 0042 yyddd/0944
CA07RB01 200 CA07RB01 TESTNTWK 000 ALL *NONE* YES 000 000 0000 00000/0000
CA07XX01 200 CA07XX01 TESTNTWK 000 ALL 000041 YES 003 012 0028 yyddd/0945
CA07XX02 200 CA07XX02 TESTNTWK 000 ALL 000001 YES 001 004 0019 yyddd/0946
CA07XX03 200 CA07XX03 TESTNTWK 000 ALL 000002 NO 001 004 0019 yyddd/1025
CA07XX04 200 CA07XX04 TESTNTWK 000 ALL 000003 NO 001 004 0015 yyddd/1025

JOB NAME
JCL ID
Identifies the index of the data set (defined in the initialization file, JCL statement)
where this member resides.
JCL MEMBER
Identifies the member name of the JCL that this job executes.

LSYS Command
SYSTEM NAME
Identifies the value from the SYSTEM field on the job definition panel.
USR ID
Identifies the value from the UID field on the job definition panel.
MAINID
Displays one of the following:
■ For CPU jobs, identifies the value from the MAINID field on the DB.1 panel.
■ For internal cross platform jobs, displays the job type for agent jobs or XPJ for
XPJOB jobs.
PROSE DSNBR
SCHED
NUMBER OF STP
NUMBER OF DDS
NUMBER OF RUNS
Edition.
LAST-RUN DATE/TIME
Identifies the last time (start time) that the job ran successfully under CA WA CA 7
Edition.

LWLB Command
LWLB Command
The LWLB command lists currently active workload balancing processing objective
information. If the CA WA CA 7 Edition system has loaded the resource criteria, actual or
in-use values are displayed. Default Resource Balancing criteria are displayed following
CA WA CA 7 Edition cold type of startups and until any user-defined criteria are loaded.
Display options that are provided permit the review of available, in-use, or both
workload balancing values, and definitions that are on the database but not currently in
use.
The output of LWLB varies based on whether the enhanced submission selection
(SUBSEL=ENH) is active.
LWLB[,MOD=modname][,LIST={ALL|AVL|USE}]
MOD
(Optional) Identifies the module whose processing objective criteria you want to
list. The value can be specified as a single module name. If MOD is not specified, the
default processing objective criteria are of the module presently in effect.
Limits: 1 to 8 alphanumeric characters beginning with UCC7R
LIST
(Optional) Specifies the balancing criteria to be listed.
ALL
Processing objective criteria and the values that are currently being used. ALL is
the default.
AVL
Processing objective criteria values from the current UCC7R module.
USE
Values that are currently being used.

LWLB Command
Examples
LWLB
LWLB,MOD=UCC7R100
LWLB,MOD=UCC7R100,LIST=USE
LWLB,LIST=ALL
LWLB Panel (Page 1 of 2) Without Enhanced Submission Selection
LWLB
MOD=UCC7R100 DATE YY.DDD PAGE 0001
**** CURRENT RESOURCES IN USE ****
-------INITIATORS-------- ----TAPE DRIVES---- ---CPU UTILIZATION---

TOTAL JOBS SUBMITTED 000 NAME - TAPEDR1 000 UTIL PER JOB 000.000%
NAME - TAPEDR2 000
-----------------------------------JOB CLASS----------------------------------
A 000 D 000 G 000 J 000 M 000 P 000 S 000 V 000 Y 000 1 000 4 000 7 000
B 000 E 000 H 000 K 000 N 000 Q 000 T 000 W 000 Z 000 2 000 5 000 8 000
C 000 F 000 I 000 L 000 O 000 R 000 U 000 X 000 0 000 3 000 6 000 9 000

INITIATORS
Identifies the total number of jobs submitted to JES by CA WA CA 7 Edition and
therefore the number of initiators that should be in use by CA WA CA 7 Edition
submitted jobs.
TAPE DRIVES
For each type of tape drive, the sum of the numbers from the DB.1 panel for the
jobs that CA WA CA 7 Edition has submitted to JES.
CPU UTILIZATION
Identifies the average CPU use of the CA WA CA 7 Edition submitted jobs.
JOB CLASS
Identifies the number of jobs submitted by CA WA CA 7 Edition in each of the 36 job
classes as entered on the job definition panel.

LWLB Command
LWLB Panel (Page 2 of 2) Without Enhanced Submission Selection
LWLB
MOD=UCC7R100,LAST CHG-DATE 05/12/09 DATE YY.DDD PAGE 0002
**** AVAILABLE RESOURCES ****

-------------INITIATORS------------ ------------CPU TIME-----------
TOTAL AVAILABLE 014 IDEAL UTIL PER JOB 010%
MIN JOBS MUST EXEC 001 MAX REWARD 100
THRESHOLD PRTY 200 MAX PENALTY 100
----------------TAPE DRIVES------------ -----------START TIME----------

NAME: TAPEDR1 TAPEDR2 MAX REWARD/PENALTY 100/050
TOT NUMBER AVAILABLE 008 016 MAX HOURS EARLY/LATE 012/012
TOT MAX ALLOWABLE 012 020 RUN TIME FACTOR 010
MAX DTS BOOST 050 030 -------SPECIAL CLS/PRTY--------
MAX REWARD/PENALTY 100/050 060/040 SPECIAL CL #1 CL PRTY 255
MIN/MAX DIFF-TO-SCHED 005/007 004/006 SPECIAL CL #2 CL PRTY 255
MIN/MAX ALLOWABLE/JOB 000/007 000/005 SPECIAL CL #3 CL PRTY 255
-----------------------------------JOB CLASS----------------------------------
A 004 D 005 G 001 J 001 M 001 P 001 S 001 V 001 Y 001 1 000 4 000 7 000
B 004 E 001 H 001 K 001 N 001 Q 001 T 001 W 001 Z 001 2 000 5 000 8 000
C 002 F 001 I 001 L 001 O 001 R 001 U 001 X 001 0 001 3 000 6 000 9 000
SLIT-00 REQUEST COMPLETED AT 09:37:46 on YY.DDD

--INITIATORS--
Identifies job totals.
TOTAL AVAILABLE
Identifies the maximum number of system initiators that can be scheduled and
therefore the number of OS initiators that must be dedicated to CA WA CA 7 Edition
controlled jobs. A value of 255 indicates there is not a limit.
MIN JOBS MUST EXEC
Identifies the number of jobs that must be submitted before workload balancing is
in effect.
THRESHOLD PRTY
Identifies the lowest priority job that is submitted when the number of jobs CA WA
CA 7 Edition is running is greater than or equal to the MIN JOBS MUST EXEC
number.
--CPU TIME--
Identifies CPU statistics.
IDEAL UTIL PER JOB
Identifies a full percentage of CPU that workload balancing should strive for as an
average across all submitted jobs.

LWLB Command
MAX REWARD
Identifies the maximum number of priority points that a job can earn in the ready
queue if it is a perfect CPU fit.
MAX PENALTY
Identifies the maximum number of priority points that a job can lose in the ready
queue if it is the worst possible CPU fit.
--TAPE DRIVES--
Identifies tape drive statistics.
NAME
Identifies the type of tape drive.
TOT NUMBER AVAILABLE
Identifies the total number of actual tape drives available to CA WA CA 7 Edition.
TOT MAX ALLOWABLE
Identifies the maximum number of tape drives that CA WA CA 7 Edition controlled
jobs can use at any point in time.
MAX DTS BOOST
Identifies the maximum number of priority points to be added to a job's job
definition panel priority in the ready queue if you have defined MIN/MAX
DIFF-TO-SCHED jobs in terms of tape drive usage.
MAX REWARD/PENALTY
Identifies the maximum number of priority points that can be earned and the
maximum number of priority points that can be lost by a job in the ready queue
because it uses tape drives.
MIN/MAX DIFF-TO-SCHED
Identifies the minimum and maximum number of tape drives that a job must
allocate at one time for that job to be considered difficult to schedule.
MIN/MAX ALLOWABLE/JOB
Identifies the minimum and maximum number of tape drives that a job must
allocate at one time to be submitted to run.
--START TIME--
Identifies time statistics.
MAX REWARD/PENALTY
Identifies the maximum number of priority points a job can be awarded/penalized
for being late.

LWLB Command
MAX HOURS EARLY/LATE

Identifies the number of hours early over which the maximum penalty/award is
given.
RUN TIME FACTOR
Identifies a buffer (stated as a percentage) where a job is neither early or late.
--SPECIAL CLS/PRTY--
Identifies special class values.
--JOB CLASS--
For each of 36 possible scheduling job classes, the maximum number of jobs of that
class that CA WA CA 7 Edition can run concurrently. A value of 255 indicates there is
not a limit.
LWLB Panel (Page 1 of 2) With Enhanced Submission Selection
LWLB
MOD=UCC7R100 DATE YY.DDD PAGE 0001
**** CURRENT RESOURCES IN USE ****
-------INITIATORS-------- ----TAPE DRIVES----

TOTAL JOBS SUBMITTED 000 NAME - TAPEDR1 000
NAME - TAPEDR2 000
-----------------------------------JOB CLASS----------------------------------
A 000 D 000 G 000 J 000 M 000 P 000 S 000 V 000 Y 000 1 000 4 000 7 000
B 000 E 000 H 000 K 000 N 000 Q 000 T 000 W 000 Z 000 2 000 5 000 8 000
C 000 F 000 I 000 L 000 O 000 R 000 U 000 X 000 0 000 3 000 6 000 9 000

INITIATORS
Identifies the total number of jobs submitted to JES by CA WA CA 7 Edition and
therefore the number of initiators that should be in use by CA WA CA 7 Edition
submitted jobs.
TAPE DRIVES
For each type of tape drive, the sum of the numbers from the DB.1 panel for the
jobs that CA WA CA 7 Edition has submitted to JES.
JOB CLASS
Identifies the number of jobs submitted by CA WA CA 7 Edition in each of the 36 job
classes as entered on the job definition panel.

LWLB Command
LWLB Panel (Page 2 of 2) With Enhanced Submission Selection
LWLB
MOD=UCC7R100,LAST CHG-DATE 05/12/yy DATE YY.DDD PAGE 0002
**** AVAILABLE RESOURCES ****

-------------INITIATORS------------
TOTAL AVAILABLE 014
----------------TAPE DRIVES------------
NAME: TAPEDR1 TAPEDR2
TOT NUMBER AVAILABLE 008 016
-----------------------------------JOB CLASS----------------------------------
A 004 D 005 G 001 J 001 M 001 P 001 S 001 V 001 Y 001 1 000 4 000 7 000
B 004 E 001 H 001 K 001 N 001 Q 001 T 001 W 001 Z 001 2 000 5 000 8 000
C 002 F 001 I 001 L 001 O 001 R 001 U 001 X 001 0 001 3 000 6 000 9 000
SLIT-00 REQUEST COMPLETED AT 09:37:46 on YY.DDD

--INITIATORS--
Identifies job totals.
TOTAL AVAILABLE
Identifies the maximum number of system initiators that can be scheduled and
therefore the number of OS initiators that must be dedicated to CA WA CA 7 Edition
controlled jobs. A value of 255 indicates there is not a limit.
--TAPE DRIVES--
Identifies tape drive statistics.
NAME
Identifies the type of tape drive.
TOT NUMBER AVAILABLE
Identifies the total number of actual tape drives available to CA WA CA 7 Edition.
--JOB CLASS--
For each of 36 possible scheduling job classes, the maximum number of jobs of that
class that CA WA CA 7 Edition can run concurrently. A value of 255 indicates there is
not a limit.

LXCF Command
LXCF Command
The LXCF command lists the XCF group name and group member name of the running
CA WA CA 7 Edition. When CA WA CA 7 Edition is not using XCF, **NONE** is shown in
both the group and member name fields.
The optional LIST=SMF keyword lists the records in the XCF checkpoint data set
(XCFCKPT). The data set contains one record for each ICOM that communicates with this
CA WA CA 7 Edition. The time that is shown is the last time an XCF buffer was processed
from that ICOM.
Occasionally, an execution of the LXCF,LIST=SMF command shows that a record in the

XCFCKPT file is obsolete. For example, ICOM on SYSX may no longer be in use. If this is
the case, the record for that ICOM can be deleted by using the /XCF command, which is
security restricted.
LXCF[,LIST=SMF]
LIST
(Optional) Specifies the information to list from the XCFCKPT data set. At this time,
the only information available is SMF. If this option is specified when XCF is turned
off, a message is displayed stating that CA WA CA 7 Edition is not using XCF.
SMF
Displays each ICOM's SMF record.
Examples
This example lists the XCF group name and group member name of the running CA WA
CA 7 Edition.
LXCF
LXCF
GROUP=CA7#CA74 MEMBER=CA7#CA74SYS3 DATE=YY.DDD PAGE 0001
SLI7-00 REQUEST COMPLETED AT 16:57:28 ON YY.DDD
This example lists the records in the XCF checkpoint data set (XCFCKPT).
LXCF,LIST=SMF

MAP Command
LXCF,LIST=SMF
GROUP=CA7#CA74 MEMBER=CA7#CA74SYS3 DATE=YY.DDD PAGE 0001
SMFID INSTANCE DATE TIME BUFNO
SYS1 CA74 yy349 16:49:14.09 00000233

SYS3 CA74 yy349 16:55:15.05 0000005F
SLI7-00 REQUEST COMPLETED AT 16:56:05 ON YY.DDD
MAP Command
The MAP command lists the attributes of DASD data sets. This function is available on
the UT Menu panel as FUNCTION value 15 or any other menu or formatted panel as
FUNCTION value UT.15.
MAP,DSN=dsname[,VOL=volume][,LIST={DSN|ALL}]
DSN
Identifies the data set to be mapped. The name can be a fully qualified name or a
generic request. The latter is indicated with an asterisk (*) following the last
significant character. (VOL is required for a generic request.) A relative generation
request can be made for a cataloged generation data set if the VOL parameter is
omitted. DSN=* lists all data sets on a volume.
VOL
Indicates the volume on which the data set resides.
Required: Yes - unless a request is made for a fully qualified, cataloged data set
name

MAP Command
LIST
(Optional) Indicates the type of data to list.
DSN
Lists the dsname, number of extents, tracks allocated, tracks used, secondary
allocation quantity, DSORG, record format (RECFM), logical record length
(LRECL), and block size (BLKSIZE). DSN is the default.
ALL
In addition to information noted under the preceding DSN, lists the creation
date, expiration date, absolute DASD address, type allocation, option code
(OPTCD), key length, key position, password indicators, and unmovable
indicators.
Usage Notes
Tracks used and secondary allocation do not apply for ISAM data sets.
There must be a U7volser DD statement that is allocated to CA WA CA 7 Edition

execution JCL for the volume containing the data set being mapped or the allocation
values are zeros. If a DD statement is not included in the JCL, you can use an ALLOC
command to allocate a U7volser DD.
Examples
MAP,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 Command
MENU Command
The top line MENU command transfers to the CA-7 Function Menu at any time.
MENU
---------------------------- CA-7 FUNCTION MENU ------------------------------

FUNCTION ===>
APA - AUTOMATED PERFORMANCE ANALYSIS

AR - AUTOMATED RECOVERY FACILITY
DB - DATA BASE MAINTENANCE
QM - QUEUE MAINTENANCE
RM - VIRTUAL RESOURCE MANAGEMENT
UT - UTILITIES
PS - PERSONAL SCHEDULING
HELP - TUTORIAL
PROGRAM: MNU0 MSG-INDX: 00 -- MENU -- YY.DDD / HH:MM:SS

MESSAGE: SPECIFY DESIRED FUNCTION OR ENTER A COMMAND ON THE TOP LINE

NOPRMP Command
NOPRMP Command
The NOPRMP top line command suspends reminder prompting for particular jobs.
Unlike RSVP, which is for a single job, this command is used to suspend all prompting.
NOPRMP can be directed at specific jobs, or all jobs in the queues. This function is
available for jobs through the QM.3 panel. Workstation networks must use the NOPRMP
command.
NOPRMP,{JOB={nnnn|ALL|ALLP}|REF=nnnnrrs}
JOB
Identifies the jobs for which to suspend prompting.
Required: Yes (in which case, omit REF).
nnnn
Indicates the CA 7 job number of a specific job.
ALL
Indicates all jobs in the request, ready, and postprocess queues.
ALLP
Indicates all jobs including those jobs in the preprocess queue.
REF
Specifies a particular workstation network task (and all subsequent workstation
tasks for that network) for which to suspend prompting. The LPRE or LPOST
commands display reference numbers.
Required: Yes (in which case, omit JOB).
nnnnrrs
Indicates the workstation task reference number that CA WA CA 7
Editionassigns.
nnnn
CA 7 job number. You can omit leading zeros.
rr
Relative sequence of the network in relation to other networks associated
with the job. For input workstation networks, the value is 00. You cannot
omit leading zeros.
s
Relative position of the station within the network. The first station is
position 1.

NXTCYC Command
Usage Notes
Prompting suspended by a NOPRMP command can only be reinstated by a PRMP
request.
A NOPRMP request issued on a global basis (for example, JOB=ALL or JOB=ALLP) only
affects those jobs in the queue at the time the request is processed.
An alternative to using the NOPRMP function for suppressing prompts is available

through the SSCAN command. This allows total suppression of reprompting after the
initial prompt message is issued.
You may also use the XUPD panel to suppress prompts for a selected job.
Examples
NOPRMP,JOB=17
NOPRMP,JOB=ALL
NOPRMP,REF=1802021
NXTCYC Command
The NXTCYC top line command bypasses one or more regularly scheduled processing
cycles of a job. A regularly scheduled processing cycle is where the schedule scan brings
the job into the request queue. This bypass can be for a single cycle or for all
subsequent cycles until further notice is provided with another option of the command.
You can also use the NXTCYC command to update the last run date and time manually.
With this updating, future workload requirements that depend on this job are satisfied
without any manual intervention. Improper updates to last run date and time for a job
could adversely affect job serialization. Updates to the last run date and time do not
affect requirements for jobs that have already entered the queues.
The NXTCYC command affects only jobs that schedule scan selects. NXTCYC does not
prevent jobs from being triggered or repeated.
The next time that the job is scheduled to run, a message is written to the CA WA CA 7
Edition master station indicating the job was not scheduled.
Note: For more information about these messages, see the Message Reference Guide.

NXTCYC Command
NXTCYC,JOB=jobname
,SET={OFF}
{ON}
{SKP}
{RUN,LRDATE=yyddd,LRTIME={hhmm|hhmmss|hhmmssth}[,FORCE={NO|YES}]}
JOB
Identifies the job for which you want to alter scheduling. The value must be a job
name.
SET
Indicates which of the options for skipping processing cycles that you want to use.
OFF
Causes all regularly scheduled processing cycles to be skipped, and is so
indicated on LJOB and LLOCK displays, until the scheduling indicator is again
reset (SET=ON). When you use SET=OFF to bypass scheduling indefinitely, you
must enter SET=ON to reinstate the normal scheduling activity. SET=OFF
indicates jobs that have been specified on a job forecast.
ON
Reinstates normal scheduling that a SET=SKP or SET=OFF command previously
altered. SET=ON can reinstate scheduling before one cycle is skipped (where
SET=SKP has been used).
SKP
Causes only the next regularly scheduled processing cycle to be skipped. You
can use SET=SKP to skip a processing cycle for a job that was demanded to run
ahead of its schedule. If SET=SKP is used, the schedule indicator automatically
resets to restore its normal scheduling activity after skipping one cycle. Jobs
with SET=SKP specified appear on forecast panel displays and are indicated on
LJOB and LLOCK displays.

NXTCYC Command
RUN
Resets the last run date and time for the job in the job record of the database.
This command does not affect requirements for jobs that are already in the
queues.
Note: Any improper updates to the last run date and time can cause an
incorrect evaluation of job requirements.
The following keywords apply only to the RUN keyword.
LRDATE
Identifies the new last run date (yyddd).
Limits: 5 digits
LRTIME
Identifies the new last run time. The following formats are valid:
hhmm
hhmmss
hhmmssth
where hh is hours (00-23), mm is minutes (00-59), ss is seconds (00-59) and
th is tenths and hundredths of seconds (00-99).
Limits: 4, 6, or 8 digits
FORCE
(Optional) Use FORCE=YES to update last run date and time even in the
following situations:
• The new value is older than the current database setting.
• The new value sets the database to a date in the future.
Default: NO
Limits: NO or N, YES or Y
Usage Notes
The NXTCYC command has no effect on jobs that are triggered by AUTO schedules.
An option to skip the next processing cycle is also available with the DEMAND
command.
The NXTCYC command has no impact on repeating jobs that are already in the CA WA
CA 7 Edition queues. However, if the NXTCYC setting suppresses the first job in a
repeating set, the entire set is skipped.

OUT Command
Examples
NXTCYC,JOB=CA7JOB1,SET=SKP
NXTCYC,JOB=CA7JOB2,SET=OFF
NXTCYC,JOB=CA7JOB2,SET=ON
OUT Command
The OUT top line command indicates the completion of a workstation task. The OUT
command, which is used after an IN command, uses a reference number for identifying
each station. CA WA CA 7 Edition generates the reference number each time the
network enters the queue. This number can be obtained by doing an LPRE or LPOST
command. This function is available as the O option on the QM.6 and QM.7 panels.
OUT,REF={nnnnrrs|(nnnnrrs,...)}
REF
Identifies the workstation network tasks to log out.
nnnnrrs
Identifies a single workstation reference number.
Note: Reference numbers can be obtained by using the LPRE or LPOST
commands.
nnnn
rr
omit leading zeros.
s
position 1.
Identifies up to ten reference numbers. Must be enclosed in parentheses.

OUT Command
Usage Notes
You can use the LOGOUT command in place of OUT. You can use the IO command to
both log in and log out with a single command.
The XPRE, XPOST, XSPRE, and XSPOST online formatted panels can be used when
working with 3270 terminals.
CA WA CA 7 Edition 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 response besides those discussed under the IN
command. This appears on the 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 an oversight,
log the station IN and reenter the OUT request, or use the IO command to log in and log
out together.
More information:
IN Command Response (see page 287)

LOGIN, LOGOUT Commands (see page 417)

POST Command
Examples
This example logs out workstation 0011011 referenced by CA WA CA 7 Edition job 0011,
network sequence 01 and station position 1.
OUT,REF=0011011
This example is the same as the preceding except for omitting the leading zeros.
OUT,REF=110011
POST Command
The POST command indicates to the CA WA CA 7 Edition system that a preexecution
requirement for a job in the request queue has been satisfied. Two categories of
requirements can be satisfied, internal and external. The internal requirements are
known within the CA WA CA 7 Edition database and CA WA CA 7 Edition controls them.
An example of an internal requirement would be the completion of another job that CA
WA CA 7 Edition controls whose completion satisfies a requirement for a dependent job.
The external requirements are defined in the CA WA CA 7 Edition database but not
controlled by CA WA CA 7 Edition. A manual post must satisfy external requirements
unless the requirement is cataloged in the CA WA CA 7 Edition catalog before the using
job is scheduled into the request queue. This function is available through the QM.2 CPU
Job Predecessors Prompt panel.
POST,{JOB={jobname|jobnumber}|JOBL=longjobname},{NW=network}
{USR=text}
{DEPJOB=jobname}
{DSN=dataset}[,INTERNAL=YES][,PREQ=(numbers,...)]
JOB
Indicates the unique job name in up to eight characters, or the job number in up to
four digits, for which requirements are posted. If the job name is used and multiple
jobs with the same name are found in the request queue, the POST is rejected. An
error message is issued. In this case, reenter the POST command using the job
number. JOB and JOBL are mutually exclusive.
jobname
Indicates a specific job name.
jobnumber
Indicates a specific CA 7 job number.

POST Command
JOBL
Indicates the unique long job name in up to 64 characters for which you want to
post requirements. If the long job name is used and multiple jobs with the same
long name are found in the request queue, the POST is rejected. An error message
is issued. The POST command must then be reentered using the JOB keyword and
the job number. JOB and JOBL are mutually exclusive.
longjobname
Indicates a specific long job name.
NW
(Optional) Identifies an input workstation network requirement to post as satisfied.
Mutually exclusive with DEPJOB, DSN, and USR. In normal situations, CA WA CA 7
Edition posts this type of requirement automatically when the network is logged
complete with a LOGOUT, OUT, or IO command to the last workstation within this
input network.
USR
(Optional) Identifies a user-defined description of a requirement to post as
satisfied. Mutually exclusive with DEPJOB, DSN, and NW. When used, must match
the text that is used to define the requirement on the DB.6 panel or with the
ADDRQ command.
Note: If the user requirement text contains commas, it cannot be satisfied with the
POST command. Post the text online with the QM.2 panel. USR MEMOs can be
entered in mixed case; however, the POST command is case insensitive. You do not
need to POST USR MEMOs with the exact case used when they were initially added.
DEPJOB
(Optional) Identifies a predecessor job dependency requirement to post as satisfied.
Value must be a specific job name. Mutually exclusive with DSN, NW, and USR. In
normal situations, CA WA CA 7 Edition automatically posts this type of requirement
when the predecessor job completes its execution successfully. A manual posting is
only necessary if a job defined as a requirement was not to be run, or ran
unsuccessfully and a successor job is to be run.
The DEPJOB must be posted if it is not currently defined to CA WA CA 7 Edition (an
external job).

POST Command
DSN
(Optional) Identifies a data set requirement to post as satisfied. Value can be a
specific data set name or a CA WA CA 7 Edition data set number. If using a number,
only the number can be specified without the DS prefix. Mutually exclusive with
DEPJOB, NW, and USR.
dsname
Indicates a specific data set name.
dsnumber
Indicates a specific CA WA CA 7 Edition data set number.
INTERNAL
(Optional) Valid only with DSN to indicate that the data set being posted is internal
to the CA WA CA 7 Edition workload. YES is the only acceptable value. Mutually
exclusive with NW, USR, DEPJOB, and PREQ. In normal situations, CA WA CA 7
Edition automatically posts requirements for internal data sets.
PREQ
(Optional) Valid only with DSN to identify up to 11 numeric values to include with
other CA WA CA 7 Edition log data logged as a result of the POST command being
issued. Mutually exclusive with NW, USR, DEPJOB, and INTERNAL. Code values in
sublist form, within parentheses. You can code up to 11 values that are separated
by commas between the parentheses. Each value cannot exceed 4 numeric digits.
This optional field can be useful for logging any meaningful numbers, such as batch
numbers, and so on, which can later be reviewed in the log data set.
Usage Notes
The Batch Card Load Program (BCLP) or U7SVC can be used to automatically handle
posting of external card-image input data sets.
Internal requirements are generally satisfied automatically by CA WA CA 7 Edition.

However, it is necessary to POST an internal requirement manually if any of the
following 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 an override.
■ A job using a data set is being run multiple times using the same version of the data
set for input to each run.

POST Command
■ 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 a successor
job is to be run.
■ An input network defined as a job requirement is not complete, but the job is to
run.
If the completion of a requirement is not noted in the CA WA CA 7 Edition database,

requirements must be satisfied by a manual POST after the using job is scheduled into
the request queue. When dependencies and requirements for resources and other CA
WA CA 7 Edition jobs or networks have been defined in the database, CA WA CA 7
Edition handles satisfaction automatically upon the completion of the requirement.
Manual posting of any requirement is not possible until the using job is in the request
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,20,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

PRINT Command
For user requirements
POST,JOB=CA7,USR=USER WILL CALL TO RELEASE
POST,JOB=12,USR=CHECK WITH JOE BEFORE RUNNING
PRINT Command
The PRINT command produces a month-by-month listing of indicated base calendars.
PRINT produces output that reflects the beginning and ending days of each month,
holidays, or any other nonprocessing days that were defined when the calendar was
produced.
PRINT,SCAL=xx[,YEAR=yy]
SCAL
Specifies user-supplied unique characters that identify the base calendar to print.
Value is the two unique characters that are used during initial creation of the
calendar. These characters provide the xx portion of the base calendar name,
SCALyyxx.
YEAR
(Optional) Specifies the year of the base calendar to print. Value is the last two
digits of the base calendar year (14 = 2014). The year also provides the yy portion of
the base calendar name, SCALyyxx. This year must be the same year that is specified
when the calendar was initially created.
Default: Current year
Limits: 2 numeric characters

PRINT Command
Usage Notes
When the beginning and ending days of the month fall on available processing days,
they are specifically indicated. Periods are used to bracket these days (for example,
.B01. or .E12.). They are enclosed in parentheses when beginning/ending days of the
month fall on nonavailable processing days.
The PRINT command is useful for generating and verifying perpetual calendars. When
the command is issued for a base calendar that does not exist, but has a criteria
member in the PCALDSN data set, the calendar is generated and displayed. For example,
assume that you issue the following command:
PRINT,SCAL=WK,YEAR=14
If the base calendar SCAL14WK does not exist and the member PCALYYWK is in the
perpetual calendar PDS, SCAL14WK is generated from the criteria in PCALYYWK. That
generated calendar displays as the PRINT command output.
Example
PRINT,YEAR=14,SCAL=PE
Causes a month-by-month printout of base calendar SCAL14PE.
The following figure presents a portion of the output from a PRINT command for a base
calendar with a holiday list.
*******************************************************************************
* CA-7 BASE CALENDAR SCAL14PE *
* YEAR 2014 GEN DATE yy.ddd *
* SCHD DAY ONLY = Y *
*******************************************************************************
** MONTH 01 JAN **
** SUN MON TUE WED THU FRI SAT **
** .B01. 02 03 04 *
** 05 06 07 08 09 10 11 *
** 12 13 14 15 16 17 18 *
** 19 20 21 22 23 24 25 *
** 26 27 28 29 30 .E01. *
*******************************************************************************

PRINT Command
*******************************************************************************
* YEAR 2014 GEN DATE 13.221 *
*******************************************************************************
** MONTH 02 FEB **
** .B02. *
** 02 03 04 05 06 07 08 *
** 09 10 11 12 13 14 15 *
** 16 17 18 19 20 21 22 *
** 23 24 25 26 27 .E02. *
*******************************************************************************
*******************************************************************************
* YEAR 2014 GEN DATE 13.221 *
*******************************************************************************
** MONTH 03 MAR **
** .B03. *
** 02 03 04 05 06 07 08 *
** 09 10 11 12 13 14 15 *
** 16 17 18 19 20 21 22 *
** 23 24 25 26 27 28 29 *
** 30 .E03. *
*******************************************************************************

PRMP Command
PRMP Command
The PRMP top line command reinstates prompting after a previous NOPRMP command
suspended it. PRMP can be used for an individual network, more than one network, or
an entire queue. This function is available for jobs through the QM.3 CPU Job Attributes
Prompt panel. Workstation networks must use the PRMP command.
PRMP,{JOB={nnnn|ALL|ALLP}|REF=nnnnrrs}
JOB
Identifies the jobs for which to reinstate prompting.
Required: Yes, unless REF is used (in which case omit JOB).
nnnn
Indicates CA 7 job number.
ALL
ALLP
Indicates all jobs including those jobs in the preprocess queue.
REF
Specifies a particular workstation network task (and all subsequent workstation
tasks for that network) for which t reinstate prompting. Reference numbers can be
obtained by using the LPRE or LPOST commands.
Required: Yes, unless JOB is used (in which case omit REF).
nnnnrrs
Is the workstation task reference number that CA WA CA 7 Edition assigns.
nnnn
rr
omit leading zeros.
s
position 1.

PRRNDEL Command
More information:
QM.3 CPU Job Attributes Prompt Panel (see page 587)
Usage Notes
The NOPRMP command is used to suspend prompting.
When PRMP is used with a reference number, all subsequent stations are affected.
More information:
NOPRMP Command (see page 549)
Examples
PRMP,JOB=17
PRMP,JOB=ALL
PRMP,REF=1802022
PRRNDEL Command
The PRRNDEL command deletes jobs from the prior-run queue based on age. If the job
was defined with RETAIN=YES, the JCL or XP PARM data that was retained is also
deleted.
PRRNDEL,DAYS=nnn[,JOB={*|jobname|mask}][,UPDATE={NO|YES}]
DAYS
Specifies the age of a job in number of days. Any jobs that are this age or older are
eligible for selection. A value of one (1) indicates select all matching jobs that ran
before today. A value of zero (0) indicates to select all matching jobs regardless of
when they ran. Use this value with caution since DAYS=0 with JOB=* specified or
defaulted would select all jobs.
Limits: 0 to 999

PRRNDEL Command
JOB
(Optional) Indicates the job name or mask that a job name must match before it is
eligible for selection.
UPDATE
(Optional) Specifies whether to delete or list the selected jobs and any retained JCL
or XP PARM data from the prior-run queue.
NO
Specifies that the selected jobs are listed only. NO is the default.
YES
Specifies that the selected jobs and any retained JCL or XP PARM data are
deleted in addition to being listed.
More information:
Examples
PRRNDEL,DAYS=3
PRRNDEL,DAYS=3,JOB=ABC??1*,UPDATE=NO
PRRNDEL,DAYS=3,JOB=ABC??1*,UPDATE=YES
PRRNDEL Panel
PRRNDEL,DAYS=140,UPDATE=YES
DATE=yy.295 CA-7 DELETE PRIOR-RUN ANALYZE REPORT PAGE NO. 0001
JOB CA-7# STARTING ENDING SYSTEM COMMENTS

NAME DATE TIME DATE TIME NAME
XPSIJOB1 0096 yy/150 1634 yy/150 1634 TESTNTWK XPJOB DELETED.
XPSIBD9 0109 yy/151 0904 yy/151 0905 TESTNTWK XPJOB DELETED.
XPSICOM7 0118 yy/151 1303 yy/151 1303 TESTNRWK XPJOB DELETED.
BOBCPU04 0135 yy/152 0647 yy/152 0647 JOB DELETED.
BOBSCC04 0162 yy/152 1152 yy/152 1152 JOB DELETED.
EROCCLEN 0157 yy/152 1046 yy/152 1046 JOB DELETED.
SAN0-00 ANALYZE REQUEST COMPLETED AT 08:52:20 yy.295.

PRRNJCL Command
PRRNJCL Command
The PRRNJCL command lists and optionally deletes JCL or PARM data for all jobs in the
prior-run queue that have JCL or PARM data retained.
PRRNJCL[,UPDATE={NO|YES}]
UPDATE
(Optional) Specifies whether to delete JCL or PARM data for the prior-run queue
entries that are listed to release that space.
NO
Specifies that the prior-run queue entries with JCL or PARM data retained is
listed only. NO is the default.
YES
Specifies to delete JCL and PARM data in addition to entries being listed.
Examples
PRRNJCL
DATE=YY.DDD CA-7 PRIOR-RUN JCL ANALYZE REPORT PAGE NO. 0004
JOB CA-7# STARTING ENDING SYSTEM COMMENTS

NAME DATE TIME DATE TIME NAME
CA07XPQ0 0760 yy/291 1331 yy/291 1332 QAXPSYS XPARM RETAINED.
CA07XPQA 0761 yy/291 1334 yy/291 1336 QAXPSYS XPARM RETAINED.
CA07XPQ1 0762 yy/291 1335 yy/291 1338 QAXPSYS XPARM RETAINED.
CA07XPQB 0769 yy/291 1337 yy/291 1339 QAXPSYS XPARM RETAINED.
CA07XPQC 0734 yy/291 1331 yy/291 1332 QAXPSYS XPARM RETAINED.
CA75XX01 0763 yy/291 1335 yy/291 1335 TESTNTWK JCL RETAINED.
SAN0-00 ANALYZE REQUEST COMPLETED AT 16:23:39 YY.DDD.

PRSCF Command
PRSCF Command
The PRSCF command frees a shared, exclusive, or RCT resource that is connected to a
job that:
■ Is currently executing
■ Is in ABEND status in the request queue
■ Has already executed and purged from the request queue
PRSCF can also remove a virtual resource from consideration of a job currently in the
active workload and waiting to execute.
PRSCF,JOB={jobname|jobnumber},RSRC=resource[,FORCE=YES]
JOB
Specifies the name or CA WA CA 7 Edition number of the job to which the resource
is attached.
jobname
jobnumber
RSRC
Specifies the fully qualified resource name to free. You can optionally specify * to
indicate to free all resources that are connected to the job.
FORCE
(Optional) FORCE=YES indicates that CA WA CA 7 Edition is not to evaluate the
availability of the named resources for this run of the job only. This run of the job
does not use the named resources. This keyword can be used on an exception basis
to let a job in a W-RSRC status bypass VRM checking for one or more resources
defined for it on the RM.1 panel.

PRSQA Command
Example
PRSRF,RSRC=RESOURCE.TYPE2.EXEC,JOB=TESTJOBB
SPOR-35 PRSRCF SUCCESSFUL
RESOURCE : RESOURCE.TYPE2.EXEC
FREED FOR JOB : TESTJOBB
SPO4-00 REQUEST COMPLETED AT 13:25:53 ON YY.DDD.
PRSQA Command
The PRSQA command activates a corequisite resource. When a job is connected to a
corequisite resource and the resource usage type is active, use the PRSQA command to
activate the corequisite resource.
■ If VRM corequisite propagation is enabled and the resource name matches the
propagation prefix, the command is forwarded to the CA 7 instances that are
specified in the initialization file options unless INTERNAL=YES is specified.
■ Command propagation is honored even if the resource is already active.
PRSQA,RSRC=resource [,INTERNAL={NO|YES}]
RSRC
Specifies a fully qualified corequisite resource name.
INTERNAL
(Optional) If YES or Y is specified, the command is not forwarded to other CA 7
instances even if VRM Corequisite Propagation is enabled and the resource name
matches the selection criteria.
Default: NO

PRSQD Command
Example
PRSQA,RSRC=CICSREG8
SPOR-39 PRSQA SUCCESSFUL
COREQUISITE RESOURCE: CICSREG8
ACTIVATED.
PRSQD Command
The PRSQD command deactivates a corequisite resource that a PRSQA command
activated. This command is the only way to deactivate a corequisite resource.
■ If VRM corequisite propagation is enabled and the resource name matches the
propagation prefix, the command is forwarded to the CA 7 instances that are
specified in the initialization file options unless INTERNAL=YES is specified.
■ Command propagation is honored even if the resource is already active.
PRSQD,RSRC=resource[,INTERNAL={NO|YES}]
RSRC
Specifies a fully qualified corequisite resource name.
INTERNAL
(Optional) If YES or Y is specified, the command is not forwarded to other CA 7
instances even if VRM Corequisite Propagation is enabled and the resource name
matches the selection criteria.
Default: NO

PS Command
Example
PRSQD,RSRC=CICSREG8
SPOR-37 PRSQD SUCCESSFUL
COREQUISITE RESOURCE: CICSREG8
DEACTIVATED.
PS Command
The PS command displays the Personal Scheduling panel. Enter PS as the FUNCTION
value on any other menu or formatted input panel or as a top line command.
Note: Personal Scheduling is valid only for CPU job types and invalid for cross-platform
job types.
PS
The PS command has no associated keywords.
Note: For more information about this command and its functions, see the Database
Maintenance Guide.

QJCL Command
Personal Scheduling Panel
--------------------------- CA-7 / PERSONAL SCHEDULING ------ yy.ddd / 13:59:30
FUNCTION==> (ADD,LIST,UPD,DEL,SUBMIT,STATUS,QUIT)
JOBNAME =>
JCL ID => JCL LIB =>
WHEN TO SCHEDULE:
PATTERN =>
TIME TO RUN => (0001-2400)
JOB RUNS AFTER => (JOBNAME - SUBMIT ONLY)
- - - - - - - STATUS INFORMATION (DISPLAY ONLY) - - - - - - -
MESSAGE: PS00-00 ENTER THE DESIRED FUNCTION AND JOB INFORMATION.
QJCL Command
The QJCL command either reviews JCL or PARM statements for jobs in the request or
prior-run queues, or modifies JCL for jobs in the request queue. For the CPU jobs, use
this facility to make overrides to JCL even if the override library or scheduled overrides
are used. This facility also accomplishes reusing JCL from CPU jobs in the prior-run
queue. The cross-platform jobs do not have any parameter data that are saved in the
prior-run queue. If data is saved, it is only the transmitted data. Therefore,
cross-platform job statements cannot be retrieved from the prior-run queue. This
function is available on the QM Command panel as FUNCTION value 5 or on any other
menu or formatted panel as FUNCTION value QM.5.
QJCL,{jobname|longjobname|jobnumber}
jobname
Identifies the unique job name of the job in the request queue whose statements
you want to update.
longjobname
Identifies the unique long job name of the job in the request queue whose
statements you want to update.

QJCL Command
jobnumber
Identifies the unique job number of the job in the request queue whose statements
you want to update.
Usage Notes
In restart situations, this command can be used to fetch a request or prior-run queue
job's JCL into an active area. Temporary changes can be made as necessary to correct
the problem that occurred. For assistance in performing any data set cleanup that can
be required, see also the QM command.
Note: For more information about overriding JCL, see the JCLOVRD command in this
section, and the JCL-OVRD and USE-OVRD-LIB fields on the DB.1 panel in the Database
Maintenance Guide. Also see the discussion of the "Edit Facilities" in the Database
Maintenance Guide.
JCL saved for jobs in the prior-run queue can also be brought into the active area and,
through a series of commands, be saved to a JCL library or stored for jobs in the request
queue to be used for the current execution of the job.
This command returns a QM.5 Queued JCL panel.
This command should only be done online.
Parameter statements for cross-platform jobs cannot be retrieved from the prior-run
queue using the QJCL command. You can use the JCL command to see the PARM
statements associated with a cross-platform job.
More information:
QM Command (see page 572)

QM.5 Queued JCL Panel (see page 601)

QM Command
QM Command
The QM panel accesses fill-in-the-blank function panels for queue maintenance
functions.
----------------------- CA-7 QUEUE MAINTENANCE MENU ------------------------

FUNCTION ===>
MAINTENANCE TO BE PERFORMED ON:

1 - CPU JOBS STATUS
2 - CPU JOB PREDECESSORS
3 - CPU JOB ATTRIBUTES
4 - CPU JOB IN RESTART STATUS
5 - QUEUED JCL
6 - INPUT NETWORKS
7 - OUTPUT NETWORKS
PROGRAM: QM00 MSG-INDX: 00 -- 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 CA WA CA 7 Edition command.
■ Provide the name of some other menu or formatted input panel in the FUNCTION
field.
Usage Notes
Although the QM panels use the word CPU and JCL in the panel titles, the panels are
valid with cross-platform jobs. Any exceptions are specifically stated in the command
and panel descriptions.
Functions are identified on the panel with their numeric value and a brief description.
To select a formatted input panel, provide the appropriate number in the FUNCTION
field and press Enter. The selected panel then appears.

QM.1 CPU Jobs Status Prompt Panel
PF Keys
Once a function has been selected on the menu and the function panel is displayed,
program function key 3 (PF3) is temporarily set to return to the QM menu panel. In
native CA WA CA 7 Edition VTAM mode, any value that was previously assigned to PF3,
by either the user or CA WA CA 7 Edition, is temporarily ignored as long as the function
panel is being used and reverts back to the original 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+1 respectively
until PF3 is pressed or a top line command is issued.
Special considerations apply when using CA WA CA 7 Edition under TSO-ISPF.

■ PF key interrupts are not processed by CA WA CA 7 Edition, unless PASSTHRU is the
ISPF application command table value associated with the ISPF command that is
assigned to the PF key in question.
■ If PF3 is assigned the END command in ISPF, PF3 ends the CA WA CA 7 Edition
TSO-ISPF session unless END is assigned a value of PASSTHRU in the ISPF application
command table.

The QM.1 panel lists jobs from the queues for purposes of updating the status of the
jobs. No equivalent batch function exists.
------------- CA-7 QUEUE MAINTENANCE - CPU JOBS STATUS PROMPT -------------

DESIRED JOB(S) => SPECIFIC, MASK OR CA-7# (DEFAULT ALL)

CA-7 SYSTEM => SPECIFIC OR MASK (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 STATUS
F = GO TO RESTART SCREEN S = SATISFY SUBMIT TIME RQMT
H = PLACE IN HOLD U = GO TO ATTRIBUTE UPDATE SCREEN
J = REVERSE JCL OVERRIDE RQMT V = REVERSE VERIFY RQMT STATUS
P = RESPOND TO PROMPTING X = GO TO JOB PREDECESSOR SCREEN
Q = REQUEUE FOR A RESTART E = FETCH QUEUED JCL AND EDIT
PROGRAM: QM2F MSG-INDX: 00 -- 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.
■ Use a PF key.

FUNCTION
Leave blank to list jobs. Otherwise, specify the name of some other panel to which a
transfer is desired.
DESIRED JOB(S)
Jobs to be listed. May be a specific job name, job number, or a job name mask
pattern. Default is all jobs. Same as JOB keyword for top line XQ commands.
CA-7 SYSTEM
List jobs associated to CA WA CA 7 Edition system. Can be a specific system or all
systems matching a mask pattern.
LIST SEQUENCE
Sequence of output desired. Default is queue entry sequence. J indicates job name
sequence. N indicates job number sequence. J and N are only allowed values.
CA-7 QUEUE ID
Queue to be searched. Same as Q keyword parameter for top line commands.
Default is REQ for request queue. Only allowable values are REQ, RDY, and ACT.
DISPLAY RQMTS
Displays requirement information. (Specify YES to get the XQM display format.)
RQMT CRITERIA
Specifies the information to display.
ALL
List all jobs regardless of outstanding requirements. This is the default.
ANY
List only those jobs with at least one requirement.

BINT
List only those jobs that have internal data set requirements, but no unsatisfied
job requirements.
EXT
List only those jobs with external data set requirements.
HLD
List only those jobs with a hold requirement.
INT
List only those jobs with internal data set requirements.
JCLO
List only those jobs with a JCL override requirement.
JOB
List only those jobs with job requirements.
NWK
List only those jobs with network requirements.
REST
List only those jobs in restart status.
SKEL
List only those jobs in skeleton status.
SUB
List only those jobs with submit-time requirements.
USR
List only those jobs with user requirements.
VER
List only those jobs with a verify requirement.

FILL FUNCTION
Same as FILL keyword parameter for top line command. When used, the display has
this value already entered in the F function field for all jobs. Default is none. The
following are the available values:
C
Cancel the job. Depending on the initialization file CANCEL statement value, a
transfer to the REASON FOR CANCEL panel may occur for each job given this
value. For more information, see the REASON FOR CANCEL panel.
E
Fetch queued JCL or PARM statements, transfer to the edit facility (similar to
QM.5) and return to this panel when finished there.
F
Transfer to the CPU JOB IN RESTART STATUS panel (QM.4) for this job and
return to this panel when finished there.
H
Put the job in hold status.
J
Reverse the JCL override requirement: if there is one, satisfy it; otherwise,
establish one.
P
Respond to a deadline prompt.
Q
Requeue the job for a restart.
R
Release the job from hold status.
S
Satisfy a submit time requirement.
U
Transfer to the appropriate JOB ATTRIBUTES panel (QM.3) for this job and
return to this panel when finished there.
V
Reverse VERIFY requirement: if there is one, satisfy it, otherwise, establish one.
X
Transfer to the CPU JOB PREDECESSORS panel (QM.2) for this job and return to
this panel when finished there.

More information:
PF Keys (see page 573)
QM.1-X CPU Jobs Status Panel

The following panel is displayed after the desired values have been entered on the
QM.1 panel with DISPLAY RQMTS=NO.
----------------- CA-7 QUEUE MAINTENANCE - CPU JOBS STATUS -----------------

F-JOBNAME--CA7#
BDTEST03 0001 JOB: *
BDTEST01 0002 SEQ: ENTRY
BDTEST02 0003 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: QM20 MSG-INDX: 00 -- QM.1-X -- YY.DDD / HH:MM:SS
MESSAGE: ENTER FUNCTION IN 'F' FIELD OR ENTER A COMMAND ON THE TOP LINE

F
Indicates the function field.
JOBNAME
Indicates the CA 7 job name.
CA7#
Indicates the CA 7 job number.

JOB
Indicates the job name selection criteria.
SEQ
Indicates the display sequence.
QUEUE
Indicates the queue that was searched: request, ready, or active.
LIST
Indicates the display selection criteria.
FUNCTIONS
Indicates the possible line functions.
Usage Notes
Job names and numbers are listed below their column heading. Up to four columns of
up to 18 jobs each can appear on each page. Up to 72 jobs per page can appear. Display
sequence and queue values are shown on the right just above a legend of available F
column function values.
To perform an update on any of the listed jobs, enter the desired value from the legend
in the F column just in front of the job you want to update. Multiple jobs can be selected
before pressing Enter. (If a FILL FUNCTION value was entered on the QM.1 panel, that
value appears in this column for each entry.)
When requested functions are completed, the panel is returned with a message at the
bottom in the MESSAGE area. Functions that were performed without an error show an
* in the F field. Functions that encountered errors show ? in the F 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 initial request. It is
not refreshed after each update. After several updates, it may be desirable to repeat the
initial QM.1 function.
After an update is made, the scrolling capability is disabled. Repeat the initial QM.1
function to establish the scrolling capability.

QM.1-M CPU Job Requirements

This panel is displayed after you entered your values on the QM.1 panel 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
BDTEST01 . . . . . H XXTEST10 . . 1 . . J JOB: *
BDTEST02 1 . 1 2 . XXTEST11 . 1 . . . SEQ: JOBNAME
BDTEST03 . 2 . . . V XXTEST12 . . 1 . . QUEUE: REQ
BDTEST04 . . . . . *SKL LIST: ALL
BDTEST05 . . . . . S
BDTEST06 1 . . . . J FUNCTIONS:
BDTEST07 . . . . . C=CANCEL
BDTEST08 . . . . . S F=RESTART
BDTEST09 . . . . . V H=HOLD
XXTEST01 1 . . . . J=JCLOVRD
XXTEST02 . 3 . 2 . H P=RSVP
XXTEST03 . . 1 . . Q=REQUEUE
XXTEST04 . 1 . . . R=RELEASE
XXTEST05 . . . 1 . J S=SUBTM OFF
XXTEST06 1 . . . . U=UPDATE
XXTEST07 . 1 . . . S V=VERIFY
XXTEST08 2 . . . . X=RQMT POST
XXTEST09 . . 1 . . E=EDIT QJCL
PROGRAM: QM20 MSG-INDX: 00 -- QM.1-M -- YY.DDD / HH:MM:SS
MESSAGE: ENTER FUNCTION IN 'F' FIELD OR ENTER A COMMAND ON THE TOP LINE

F
Indicates the function name.
JOBNAME
Indicates the CA 7 job name.
J
Indicates the number of outstanding job requirements.
I
Indicates the number of outstanding internal data set requirements.
E
Indicates the number of outstanding external data set requirements.
U
Indicates the number of outstanding user requirements.

N
Indicates the number of outstanding network requirements.
S
Indicates an outstanding submit time requirement.
Special character settings beginning with an asterisk can appear under the SHJV
heading to indicate special situations. These include the following:
*CMP
Indicates job is in completed status.
*ERR
Indicates an error occurred attempting to collect the requirement information.
*NOF
Indicates job not found in requested queue. (This normally happens when you
post the last requirement for a job, and it moves from the request to the ready
queue.)
*RST
Indicates job is in restart status.
*SKL
Indicates job is in skeleton status.
H
Indicates an outstanding hold requirement.
J
Indicates an outstanding JCL override requirement.
V
Indicates an outstanding verify requirement.
JOB:
Indicates job name selection criteria.
SEQ:
Indicates display sequence.
QUEUE:
Indicates the queue that was searched: request, ready, or active.

LIST:
Indicates the display selection criteria.
FUNCTIONS:
Indicates the possible line functions.
Usage Notes
The jobs are listed in job name sequence. Line functions can be issued for any job in the
same way as the QM.1-X panel. For security purposes, line functions entered on the
QM.1-M panel are considered to have come from the QM.1-X panel.
The outstanding requirements for each job listed are reflected to the right of the job
name. Categories that can have more than one requirement are two-digit numeric
fields. If the value is zero, a period is displayed. If the value exceeds 99, two asterisks are
displayed to represent an overflow situation (by using the Requirement Post line
command 'X', you can see the total master requirement count). Categories that are
yes/no situations (such as Hold) are represented by the 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 if REASON=OPTIONAL or
REASON=REQUIRED is specified on the initialization file CANCEL statement.
-------------- CA-7 QUEUE MAINTENANCE - REASON FOR CANCEL ------------------
JOB NAME: SARWKY01

JOB NUMBER: 1482
REASON:
(MAXIMUM OF 40 CHARACTERS)
PROGRAM: QM70 MSG-INDX: 00 -- QM.1-XC -- YY.DDD / HH:MM:SS

MESSAGE: GIVE THE REASON FOR CANCELING THE JOB


JOB NAME
Specifies the name of the job to be canceled.
JOB NUMBER
Specifies the job number of the job to be canceled.
REASON
Specifies the reason for the cancellation. The cursor is positioned here when the
panel is first displayed. Any text entered is displayed on subsequent LRLOG
inquiries.
Usage Notes
If the installation does not require a reason, pressing Enter without providing a reason
cancels the job without logging any descriptive text. If the installation requires a reason,
the cancellation does not occur until some text is provided.
Note: For more information about the installation's options for this panel, see the
initialization file CANCEL statement.
CA WA Restart Option restart reasons are not expanded here as they are on the QM.4
panel for restarts. Any value entered here is assumed to be descriptive text and is
logged as entered.

QM.2 CPU Job Predecessors Prompt Panel

The QM.2 panel lists the predecessors of jobs in the request queue and allows posting
those jobs as being complete or not. No equivalent batch function exists.
----------- CA-7 QUEUE MAINTENANCE - CPU JOB PREDECESSORS PROMPT -----------

JOB TO BE UPDATED =====> SPECIFIC NAME OR CA-7 JOB#
LIST ALL PREDECESSORS => N Y=YES (DEFAULT IS LIST ONLY THE

UNSATISFIED ONES)
PROGRAM: QM30 MSG-INDX: 00 -- QM.2 -- YY.DDD / HH:MM:SS

MESSAGE:
To display, enter:
■ If an error is encountered with a top line XRQ command, this panel is returned for
ease of correction and reentry.
To exit:
■ Use a PF key.


FUNCTION
Leave blank to list a job. Otherwise, specify the name of some other panel to which
you want to transfer or position the cursor to the top line and enter a top line
command.
JOB TO BE UPDATED
Job name or CA 7 job number of the desired job. Required, there is no default.
LIST ALL PREDECESSORS
Enter Y to list even satisfied predecessors. Default is to list only unsatisfied ones (N).
More information:
QM.2-X CPU Job Predecessors

After entering the desired values on the QM.2 panel, press Enter. A panel similar to this
then displays.
-------------- CA-7 QUEUE MAINTENANCE - CPU JOB PREDECESSORS ---------------

JOB: D463XX03 CA-7#: 0002 MCNT: 004
F-TYP--NUMBER--E-DESCRIPTION
HLD JOB HELD IN REQUEST QUEUE
JOB A D463XX01
USR O SAMPLE NEXT-RUN ONLY PREDECESSOR
NWK 00000008 D40218ED

MESSAGE:


JOB
Specifies the job name.
CA-7#
Specifies the job number.
MCNT
Specifies the number of unsatisfied predecessors. The unsatisfied predecessors are
listed below a column heading.
F
Indicates the function column in which updates are requested. An X satisfies the
requirement, and a U UNPOSTs or causes that requirement to be unsatisfied.
TYP
Indicates the type of predecessor.
EXT
An external data set. An external data set is one that is created or used by CA
HLD
Hold status (see the HOLD command and HOLD field on the Job Definition
panel).
INT
An internal data set. An internal data set is one that is created and used by CA
JCL
JCL modification (see the JCLOVRD command and JCL-OVRD field on the Job
Definition panel).
JOB
CPU job.
NWK
Input network.
SUB
Specific submit time (see the SUBTM command and the SBTM field on the CPU
Job Scheduling Parameter Edit panel function of DB.2.1).

USR
User memo-form.
VER
Verification (see the VERIFY command and VERIFY field on the Job Definition
panel).
NUMBER
Appears for data sets and input networks and indicates the DSNBR assigned in the
CA WA CA 7 Edition database.
E
Indicates exceptions to normal requirements of this job.
A
Added through ADDRQ command (after the job entered the queues)
O
Defined for this run only (through NEXT-RUN ONLY facility)
DESCRIPTION
Displays a brief description of the predecessor.
More information:
VERIFY Command (see page 705)

SUBTM Command (see page 667)
HOLD Command (see page 282)
JCLOVRD Command (see page 294)
Usage Notes
To post a predecessor complete, enter X in the F column in front of the appropriate 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, you return to
that panel after any updates are done.

QM.3 CPU Job Attributes Prompt Panel

The QM.3 panel lists the current attributes of a job in the request, ready, or active
queue and allows them to be changed. There is no equivalent batch function.
------------ CA-7 QUEUE MAINTENANCE - CPU JOB ATTRIBUTES PROMPT ------------

JOB TO BE UPDATED =====> SPECIFIC NAME OR CA-7 JOB#

MESSAGE:
To display, enter:
■ If an error is encountered with a top line XUPD command, this panel is returned for
To exit:
■ Use a PF key.


FUNCTION
command.
JOB TO BE UPDATED
Job name or job number of the desired job. Required, there is no default.
More information:
QM.3-X CPU Job Attributes

After entering your values on the QM.3 panel, press Enter. You see a panel similar to
this one.
--------------- CA-7 QUEUE MAINTENANCE - CPU JOB ATTRIBUTES ----------------

JOB: D463XX03 CA-7#: 0002 MCNT: 004 QUEUE: REQ
---------SCHEDULING--------- ------MANUAL REQUIREMENTS-------

DEADLINE TIME.... 09058 1304 JOB HELD...................... Y
DUE-OUT TIME..... 09058 1304 MANUAL VERIFICATION REQUIRED.. N
SUBMIT TIME...... 09058 1300 JCL OVERRIDES REQUIRED........ N
MAINID........... ALL
REPEAT INTERVAL.. 0015 TYPE.. CLOCK COUNT.. 0098 STOP.. 05059 1000
----------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.......... 100
ELAPSED TIME (HHMM)... 0001 TAPE DRIVES OF TYPE1.. 000
CPU TIME (MMMSS)...... 00001 TAPE DRIVES OF TYPE2.. 000

MESSAGE:

To update the values on the panel, position the cursor at a value and key the desired
value over the old value. Multiple fields can be updated if so desired.

DEADLINE TIME
Lists two fields in the format yyddd and hhmm respectively, the date and time that
a job must start or the job is flagged as LATE.
DUE-OUT TIME
a job must complete or the job is flagged as LATE.
SUBMIT TIME
Lists two fields in the format yyddd and hhmm respectively. Null values indicate the
job has no submit time-of-day requirement. To establish a requirement, enter
appropriate data. To remove an existing submit time-of-day requirement, set this
value to precede the current date and time-of-day. Changes to this field are only
honored if the job is in the request queue.
MAINID
Indicates ALL, SYn, or /SYn. MAINID indicates to which CPU the job is submitted.
(See MAINID on the DB.1 panel for the job.) For example, SY1 means CPU #1 and
/SY1 means NOT CPU #1, as follows:
SYn
Use CPU number.
/SYn
Do not use CPU number n.
ALL
Use any CPU. This field cannot be modified after a job has been submitted.
JOB HELD
Indicates (Y or N) hold status. This applies only to jobs in the request queue or the
ready queue if not already submitted to OS.
MANUAL VERIFICATION REQUIRED
Indicates (Y or N) manual verification requirement status. This status applies only to
jobs in the request queue.
JCL OVERRIDES REQUIRED
Indicates (Y or N) JCL override verification status. This status applies only to jobs in
the request queue.

REPEAT
Displays only if the job is to repeat.
INTERVAL
Determines the amount of time (in hhmm format) between iterations of the job.
The value is from 00 to 23 for hh and from 00 to 59 for mm. Set this field to zero to
stop repeating the job.
TYPE
Determines the submit time of the next iteration. If the value is CLOCK, the interval
is added to the previous iteration's submit time requirement. If the value is START
or END, the interval is added to the previous iteration's start or end time,
respectively. TYPE can be CLOCK, START, or END. Only the first letter need be typed.
COUNT
Determines how many more times to repeat the job. If the field is zero, the job is
repeated until the stop time is reached.
STOP
Determines (two field values) the clock time when the job can no longer be
repeated. The maximum value is 1439 minutes (24 hours minus 1 minute) after the
submit time requirement of the first job in the repeating cycle.
GENERATE CA-11 STEP
Indicates (Y or N) whether to generate a CA WA Restart Option step. This field
cannot be modified after job submission.
FORMAT CA-11 CMT
Indicates (Y or N) whether the generated step is to perform F processing. This field
cannot be modified after job submission.
RETAIN JCL IN PRRN QUEUE
Indicates (Y or N) whether to retain the JCL in the PRRN queue. (See RETAIN-JCL on
the DB.1 panel for the job.)
ELIGIBLE FOR PROMPTS
Indicates (Y or N) whether to prompt the job if late. (See PROMPTS on the DB.1
panel for the job.)
PROMPT ACKNOWLEDGED
Indicates (Y or N) whether the prompt has been acknowledged. Any attempt to
acknowledge a prompt when one has not been received is ignored.

LTERM FOR MESSAGES

Identifies the logical terminal to receive status and prompting messages for this job.
(See LTERM on the DB.1 panel for the job.) Value is a maximum of eight characters.
JOB CLASS
Displays any single alphanumeric character, the CA WA CA 7 Edition job class. (See
CLASS on the DB.1 panel for the job.) Changes to this field after the job is submitted
have no effect.
ELAPSED TIME
Indicates the average elapsed time for the job in hhmm format. The value is from 0
to 23 for hh and from 0 to 59 for mm. Changes to this field after the job is
submitted have no effect.
CPU TIME
Indicates the average CPU time use for the job in mmmss format. The value is from
0 to 999 for mmm and from 0 to 59 for ss. This value applies only to jobs in the
request queue.
JOB PRIORITY
Indicates the original CA WA CA 7 Edition workload balancing current job priority.
The value is from 0 to 255.
TAPE DRIVES OF TYPE 1
Indicates the number of tape drives of Type 1 needed for the job. The value is from
0 to 255.
TAPE DRIVES OF TYPE 2
Indicates the number of tape drives of Type 2 needed for the job. The value is from
0 to 255.
Usage Notes
After all values have been entered, press Enter and the updates are made. A message
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 is to that
panel after any updates are done.

QM.3-X XPJOB Job Attributes

After entering your values on the QM.3 panel, press Enter. If the job type is for an
XPJOB, you see a panel similar to this one.
----------------- CA-7 Queue Maintenance - XPJOB Attributes ----------------

Job: CA07XPQ7 CA-7#: 0661 MCNT: 002 Queue: REQ
---------Scheduling--------- ------Manual Requirements-------

Deadline Time.... 06290 1714 Job Held...................... Y
Due-Out Time..... 06290 1714 Manual Verification Required.. N
Submit Time...... 06290 1619
Repeat Interval.. 0010 Type.. CLOCK Count.. 0005 Stop.. 06291 1618
XP Node... EROCTST
XP EXEC... calc.exe
----Resources----- ---------Prompting--------- ---Misc----

WLBClass..... A Eligible for Prompts.. Y Retain.... Y
WLBPRTY...... 100 Prompt Acknowledged... N SUTYPE.... Y
Clock Time... 0015 LTERM for Messages.... MASTER
To update the values on the panel, position the cursor at a value and key the intended
value over the old value. Multiple fields can be updated if you want.

Deadline Time
Due-Out Time
Submit Time
Job Held
Indicates (Y or N) hold status. This status applies only to jobs in the request queue
or the ready queue if not already submitted to OS.
Manual Verification Required

Repeat
Displays only when the job is to repeat.
Interval
Type
Count
Stop
XP Node
Indicates the primary target node to which this job should be sent. If this primary
node has alternate nodes defined in its definition, and the primary node is not
available at the time of transmission, the data may be sent to an alternate node.
XP EXEC
Indicates the executable file or script that executes at the target destination.
WLBClass
Indicates any single alphanumeric character, the CA WA CA 7 Edition job class. (See
WLBCLASS on the DB.10 panel for the job.) Changes to this field after the job is
WLBPRTY
Clock Time
Eligible for Prompts
Indicates (Y or N) whether to prompt the job. (See PROMPTS on the DB.10 panel for
the job.)

Prompt Acknowledged
Indicates (Y or N) whether a late prompt has been acknowledged. Any attempt to
LTERM for Messages
Identifies the logical terminal to receive status and prompting messages for this job.
(See LTERM on the job definition panel for the job.) Value is a maximum of eight
characters.
Retain
Indicates (Y or N) whether to retain the PARM data in the PRRN queue. (See RETAIN
on the DB.10 panel for the job.)
SUTYPE
Indicates whether to perform the Switch User (SU) profile at the targeted UNIX
system when the process executes.
QM.3-X AGJOB Job Attributes

After entering your values on the QM.3 panel, press Enter. If the job type is for an
AGJOB, you see a panel similar to this one.
----------------- CA-7 Queue Maintenance - Agent Attributes -----------------

Job: AGNTCOM1 CA-7#: 0079 MCNT: 001 Queue: REQ
Status:
---------Scheduling--------- ------Manual Requirements-------

Deadline Time.... 09035 1837 Job Held...................... Y
Due-Out Time..... 09035 1837 Manual Verification Required.. N
Submit Time......
Repeat Interval.. 0010 Type.. CLOCK Count.. 0005 Stop.. 06291 1618
Agent..... USERO01ESP
User ID... main-a01\usero01
----Resources----- ---------Prompting---------
WLBClass..... A Eligible for Prompts.. Y
WLBPRTY...... 100 Prompt Acknowledged... N
Clock Time... 0004
PROGRAM: QM42 MSG-INDX: 00 -- QM.3-X -- yy.ddd / hh:mm:ss

MESSAGE: Change desired fields or enter a command on the top line

To update the values on the panel, position the cursor at a value and key the intended
value over the old value. Multiple fields can be updated if you want.

Status
Lists the last status received for an agent job. This field is limited to 40 bytes and
cannot be updated. The field can contain blanks when the job has not been sent to
the CA Workload Automation Agent or the job has no status reported for the job
from the agent.
Deadline Time
Due-Out Time
Submit Time
Job Held
Indicates (Y or N) hold status. This status applies only to jobs in the request queue
or the ready queue if not already submitted to OS.
Manual Verification Required
Repeat
Displays only if the job is to repeat.
Interval

Type
Count
Stop
Agent
Identifies the explicit distributed platform where the job is to run.
User ID
Defines the user ID that is passed to the distributed platform where the job is to
run.
WLBClass
Indicates any single alphanumeric character, the CA WA CA 7 Edition job class. (See
WLBCLASS on the DB.10 panel for the job.) Changes to this field after the job is
WLBPRTY
Clock Time
Eligible for Prompts
Indicates (Y or N) whether to prompt the job. (See PROMPTS on the DB.10 panel for
the job.)
Prompt Acknowledged
Indicates (Y or N) whether a late prompt has been acknowledged. Any attempt to

QM.4 CPU Job In Restart Status Prompt Panel

The QM.4 panel lists jobs and allows them to be restarted. The equivalent batch
command is RESTART.
Cross-platform jobs never use CA WA Restart Option services for restart functions.
-------- CA-7 QUEUE MAINTENANCE - CPU JOB IN RESTART STATUS PROMPT ---------
JOB TO BE RESTARTED =====> SPECIFIC NAME OR CA-7 JOB#

MESSAGE:
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 is returned for
To exit:
■ Use a PF key.


FUNCTION
command.
JOB TO BE RESTARTED
Job name or CA 7 job number of the intended job. Required, there is no default.
More information:
QM.4-X CPU Job In Restart Status

After entering the intended values on the QM.4 panel, press Enter. A panel is returned
with which restart options can be taken.
If CA WA Restart Option is available to assist with a restart, the panel returned is similar
to this.
CA WA Restart Option Installed
------------ CA-7 QUEUE MAINTENANCE - CPU JOB IN RESTART STATUS ------------

JOB: D463XX03 CODE: JCLERR LAST-STEP: MCNT: 001 CA-11:
CA-7#: 0002 JES#: 17349 NODE-NAME: LOCAL JNODE:
REASON:
-- -- RESUBMIT FOR PRODUCTION
-- -- FORCE COMPLETE
-- -- CA-11 RESTART/RERUN PSEUDO:

START: END:
CC: BYPGDG: USAGE: LRTCD: = 0
CMT STATUS: CMT SHOWS JOB IS SET FOR RESTART
-- -- SET PARM DATA FOR RMS AND RESUBMIT

PARM: #
-- -- DO NOT INSERT RMS PROC BUT RESUBMIT

MESSAGE: 'X' THE DESIRED FUNCTION OR ENTER A COMMAND ON THE TOP LINE

Request the proper functions by placing an X in the space provided and pressing Enter.

REASON
Always appears on the panel. This is a required entry field if REASON=YES is
specified in the CA WA CA 7 Edition initialization file RESTART statement or if CA
WA Restart Option requires a reason for restarts. the CA WA Restart Option
reason-for-rerun table is available, an attempt is made to expand any code of up to
four characters that is entered. If the CMT member is found, the reason entered is
moved to the CMT.
Note: For more information about the initialization file, see the Systems
Programming Guide.
RESUBMIT FOR PRODUCTION
Always appears on the panel. Used by itself to simply resubmit the job with no
changes. When CA WA Restart Option is installed and the job is found on the CMT
data set, this function clears restart fields in the CMT.
FORCE COMPLETE
Always appears on the panel. If used, the job is processed as if a good end-of-job
had occurred. This causes triggering and requirement posting for other dependent
jobs. Job triggering and posting occur. If CA WA Restart Option is installed and the
CMT member is found, this also clears the CMT flags.
CA-11 RESTART/RERUN
If the CMT member is found, information specified in these fields update the CMT
member. If the RMS step has not executed, RESUBMIT should be used instead of
RESTART.
CMT STATUS
Used to provide a message describing the job status as found in the CMT. Also used
to report that the CA WA Restart Option interface is not available and why.
SET PARM DATA FOR RMS AND RESUBMIT
Can be used only if CA WA CA 7 Edition inserted the RMS procedure. Used to define
new CA WA Restart Option PARM data for the rerun. No edits are performed on this
field. The CA WA Restart Option CMT is not updated.
DO NOT INSERT RMS PROC BUT RESUBMIT
Can be used only if CA WA CA 7 Edition inserted the RMS procedure. Causes
resubmittal without the RMS procedure being inserted. Overrides DB.1 panel
option. The CA WA Restart Option CMT is not updated. This option should only be
used for the first resubmission of a job. RESUBMIT FOR PRODUCTION should be
used for any subsequent resubmissions.

CA WA Restart Option Not Installed
If CA WA Restart Option is not installed, the following is an example of the panel.
------------ CA-7 QUEUE MAINTENANCE - CPU JOB IN RESTART STATUS ------------

JOB: D463XX03 CODE: JCLERR LAST-STEP: MCNT: 001
CA-7#: 0002 JES#: 17349 NODE-NAME: LOCAL
REASON:
-- -- RESUBMIT FOR PRODUCTION
-- -- FORCE COMPLETE

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 two lines
below the panel title line.

QM.5 Queued JCL Panel

The QM.5 panel lists queued JCL or PARM statements for update purposes. There is no
equivalent batch function.
------------------- CA-7 QUEUE MAINTENANCE - QUEUED JCL --------------------

FUNCTION: (APPEND,APPENDP,CLEAR,EDIT,FE,FETCH,
FETCHP,FPE,REPL,SAVE)
JOB:
ACTIVE SIZE: 00000
NOTE: REPL WILL RESET THE JCLOVRD REQUIREMENT
PROGRAM: SM90 MSG-INDX: 00 -- 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 is returned for
To exit:
■ Use a PF key.

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.

FUNCTION
Indicates the activity to be performed. Must be one of the following:
APPEND
Attaches request queue JCL or PARM statements to the end of any existing
lines in the terminal's active area.
APPENDP
Attaches prior-run queue JCL statements to the end of any existing lines in the
terminal's active area. This function is not valid with cross-platform jobs.
CLEAR
Clears the panel input data fields and the terminal's active area.
EDIT
Transfers the user to the edit facility and allows text processing. If editing a
CA7TOUNI or cross-platform job, we recommend the FE function to ensure a
mixed case editing environment.
FE
Combination of FETCH and EDIT. If job name or job number is entered with the
top line QJCL command, the FE function is assumed.
FETCH
Retrieves request queue JCL or parameter statements into the terminal's active
area. If editing a CA7TOUNI or cross-platform job, we recommend the FE
function to ensure a mixed case editing environment.
FETCHP
Retrieves prior-run queue JCL statements into the terminal's active area. This
function is not valid with cross-platform jobs.
FPE
Combination of FETCHP and EDIT.
REPL
Replaces the JCL or parameter statements in the request queue and turns off
the JCL override requirement if one exists. This decrements the master
requirement count by one.
SAVE
Saves the JCL or parameter statements in the request queue and does not turn
off the JCL override requirement if one exists.

QM.6 Input Networks Prompt Panel
JOB
If the user is doing a FETCH, APPEND, REPL or SAVE for JCL in the request queue,
this can be the assigned CA 7 job number, or the job 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 specific job name in up to eight characters.
Reminder text can be fetched or replaced by using RMD#nnnn in the JOB field,
where nnnn is the CA WA CA 7 Edition preprocess queue job number.
ACTIVE SIZE
A system generated field that displays how many lines of text exist in the active
area for the current terminal session.
More information:

The QM.6 panel lists input network tasks that are to be updated. There is no equivalent
batch function.
-------------- CA-7 QUEUE MAINTENANCE - INPUT NETWORKS PROMPT --------------

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 THE

STATIONS 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

MESSAGE:

To display, enter:
■ If an error is encountered with top line XPRE or XSPRE commands, this panel is
returned for ease of correction and reentry.
To exit:
■ Use a PF key.

FUNCTION
Leave blank to list entries. Otherwise, specify name of some other panel to which
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 all jobs.
STATION(S)
Specific station name, generic station name, or * to indicate all station names
defined to CA WA CA 7 Edition. Default is only the station names defined to this
terminal.
2-UP ?
Y indicates 2-up format display is wanted. Default is N, for 1-up format.

FILL WITH
C
Cancel the task.
H
Put the task in hold status.
I
Do LOGIN function for this task.
O
Do LOGOUT function for this task.
P
Respond to a deadline prompt (RSVP).
R
Release the task from hold status.
More information:
QM.6-X Input Networks (1-Up Display)

The following panel is displayed if a 1-up display was requested in the previous panel. (A
2-up display, QM.6-S Input Networks (2-Up Display), is also available.)
Function values can be entered in the FL. portion of the panel to assign the same
function for all records. It can also be entered in front of an individual entry to perform
the function for only that entry.
Function values can be mixed on the same panel. For example, after the panel is first
displayed, you can enter function values, in the field that precedes each line on the
panel, to log in to one entry, log out another, and cancel yet another with a single panel
command.

After a station has been logged out or canceled, it continues to be displayed for this
request. It may be necessary to reissue the command for an updated display. 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--------------*
0002001 D463XX03 D40218ED CONTROL PAY01 WEEK1

MESSAGE:
Once the QM.6-X update panel has been displayed, the POS, FL, and INITS fields on the
panel can be used to perform certain functions. The use of these fields and their
acceptable values are as follows:
POS:
Indicates the position of the panel. The following are the available values:
NOP
No processing - clears panel of input values.
PF
Page forward.
TOP
Position to the top of the panel.
ONE
Display in 1-up format (one record per line); return from TWO.
TWO
Display in 2-up format (two records per line).

FL:
Indicates a fill character for processing the records. See the FILL parameter for
allowable options.
INITS:
This performs the same function as the INITS parameter of the LOGIN and LOGOUT
commands discussed elsewhere in this section. The initials of the operator
processing network records could be entered here.
F
Indicates the function column in which updates are requested. See the FILL WITH
values on the QM.6 panel for values allowed here.
REF
Indicates the CA WA CA 7 Edition assigned number for this task.
JOBNAME
Indicates the JOB keyword value given when the network was initiated with a
DMDNW command.
NETWORK
Indicates the name of this network in the database.
STATION
Indicates the station at which this task is to be performed.
SUBID
Indicates the value given when the network was initiated with a DMDNW
command.
DESC
Indicates the DESC keyword value given when the network was initiated with a
DMDNW command.
REMARKS
Indicates 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 the entry 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 took place.
When finished, you can enter a command on the top line to transfer to some other
function.
More information:
QM.6-S Input Networks (2-Up Display)

If a 2-up display was requested on the QM.6 panel, a panel similar to the following
appears. If more than 17 tasks are listed, tasks 18-34 appear as a second column just to
the right of the one shown here.
----------------- CA-7 QUEUE MAINTENANCE - INPUT NETWORKS ------------------

POS: FL: INITS:
F---REF---SUBID----DESC-----EC
0002001 PAY01 WEEK1
PROGRAM: QM10 MSG-INDX: 00 -- QM.6-S -- YY.DDD / HH:MM:SS

MESSAGE:

The F, REF, SUBID, and DESC fields have the same meaning as on the 1-up display.
The EC field provides a 2-digit number corresponding to the REMARKS field on the 1-up
display as follows:
01
INVALID CODE - the F value given is unknown
02
REF# NOT FOUND - could not locate the REF number requested
03
ALREADY LOGGED IN - can only log in a task once
05
NOT IN PROCESS - can only log out an active task
06
NOT HELD - can only release a 'held' task
07
NOT PROMPTED - can only respond if the task was prompted
08
HELD - the task is now in 'hold' status
09
ALREADY LOGGED OUT - can only log out a task once
10
ALREADY HELD - can only 'hold' a non-held task
11
ALREADY ACKNOWLEDGED - can only respond to a prompt once
Usage Notes
After all values have been entered, press Enter and the updates are made. EC fields and
MESSAGE field at the bottom indicate what action took place.

QM.7 Output Networks Prompt Panel

The QM.7 panel lists output network tasks that are to be updated. There is no
equivalent batch function.
------------- CA-7 QUEUE MAINTENANCE - OUTPUT NETWORKS PROMPT --------------

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 THE

STATIONS 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
F = FORCE LOGIN

MESSAGE:
To display, enter:
■ If an error is encountered with top line XPOST or XSPOST commands, this panel is
returned for ease of correction and reentry.
To exit:
■ Use a PF key.


FUNCTION
Leave blank to list entries. Otherwise, specify name of some other panel to which
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 all jobs.
STATION(S)
Specific station name, generic station name, or * to indicate all station names
defined to CA WA CA 7 Edition. Default is only the station names defined to this
terminal.
2-UP ?
Y indicates 2-up format display is wanted. Default is N for 1-up format.
FILL WITH
C
Cancel the task.
H
Put the task in hold status.
I
Do LOGIN function for this task.
F
Do LOGIN function even if the connected job is not complete.
O
Do LOGOUT function for this task.

P
Respond to a deadline prompt (RSVP).
R
Release the task from hold status.
More information:
QM.7-X Output Networks (1-Up Display)

The following panel is displayed if a 1-up display was requested on QM.7 panel. (A 2-up
display, QM.7-S Output Networks (2-Up Display), is also available.)
Function values can be mixed on the same panel. For example, after the panel is first
displayed; you can enter function values in the blank field that precedes each line on the
panel, to log in to one entry, log out another, and cancel yet another with a single panel
command.
After a station has been logged out or canceled, it continues to be displayed until a new
display is requested. However, no function value can be input for that entry.
----------------- CA-7 QUEUE MAINTENANCE - OUTPUT NETWORKS -----------------

POS: FL: INITS:
F --REF-- JOBNAME- NETWORK- STATION- SUBID--- DESC---- REMARKS--------------*
0003011

MESSAGE:

Once the QM.7 update panel has been displayed, the POS, FL, and INITS fields on the
panel can be used to perform certain functions. The use of these fields and their
acceptable values are as follows:
POS:
This indicates position of the panel. The following are the available values:
NOP
No processing - clears panel of input values.
PF
Page forward.
TOP
Position to the top of the panel.
ONE
Display in 1-up format (one record per line); return from TWO.
TWO
Display in 2-up format (two records per line).
FL:
Indicates a fill character for processing the records. See the previous discussion of
the FILL parameter for allowable options.
INITS:
This performs the same function as the INITS parameter of the LOGIN and LOGOUT
commands. You can enter the initials for the operator processing network records
here.
F
Indicates the function column in which updates are requested. See the FILL WITH
values on the QM.7 panel for values allowed here.
REF
Indicates the CA WA CA 7 Edition assigned number for this task.
JOBNAME
Indicates one of the following:
■ JOB keyword value given when the network was initiated with a DMDNW
command.
■ Name of the job predecessor if the network was initiated as a result of the
predecessor job being initiated.

NETWORK
Indicates the name of this network in the database.
STATION
Indicates the station at which this task is to be performed.
SUBID
Indicates one of the following:
■ SUBID keyword value given when the network was initiated with a DMDNW
command.
■ SUBID value for the SUB-ID field on the DB.3.4 panel.
DESC
Indicates the DESC keyword value given when the network was initiated with a
DMDNW command.
REMARKS
Indicates 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 output task 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
More information:
LOGIN, LOGOUT Commands (see page 417)

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 took place.
QM.7-S Output Networks (2-Up Display)

If a 2-up display was requested, a panel similar to the following appears. If more than 17
tasks are listed, tasks 18-34 appear as a second column just to the right of the one
shown here.
----------------- CA-7 QUEUE MAINTENANCE - OUTPUT NETWORKS -----------------

POS: FL: INITS:
F---REF---SUBID----DESC-----EC
0003011
PROGRAM: QM10 MSG-INDX: 00 -- QM.7-S -- YY.DDD / HH:MM:SS

MESSAGE:
The F, REF, SUBID, and DESC fields have the same meaning as on the 1-up display in the
QM.7-X Output Networks (1-Up Display).
The EC field provides a 2-digit number corresponding to the REMARKS field on the 1-up
display as follows:
01
INVALID CODE - the F value given is unknown
02
REF# NOT FOUND - could not locate the REF number requested

03
ALREADY LOGGED IN - can only log in a task once
05
NOT IN PROCESS - can only log out an active task
06
NOT HELD - can only release a held task
07
NOT PROMPTED - can only respond if the task was prompted
08
HELD - the task is now in hold status
09
ALREADY LOGGED OUT - can only log out a task once
10
ALREADY HELD - can only hold a nonheld task
11
ALREADY ACKNOWLEDGED - can only respond to a prompt once
Usage Notes
After all values have been entered, press Enter and the updates are made. EC fields and
MESSAGE field at the bottom indicate what action took place.

RELEASE Command
RELEASE Command
The RELEASE top line command indicates that normal scheduling activities can now be
resumed for jobs or queues on HOLD. This function is available for jobs on the QM.1,
QM.2, and QM.3 panels. RELEASE is available for workstation networks on the QM.6 and
QM.7 panels.
RELEASE,{JOB={jobname|jobnumber|refnumber}|JOBL=longjobname|Q={REQ|RDY}}
JOB
Indicates the individual job or workstation network to release. JOB is required to
release a specific job. Omit JOB when JOBL or Q is specified. The value for a job can
be entered as the specific job name or the CA 7 job number.
Required: Yes, unless JOBL or Q is used.
jobname
jobnumber
Indicates a specific job number.
refnumber
Enter the value for a workstation network task as the CA WA CA 7 Edition
assigned reference number in the nnnnrrs format.
nnnn
Specifies the CA 7 job number. You can omit leading zeros.
rr
Specifies the relative sequence of the network in relation to other
networks associated with the job. For input workstation networks, the
value is 00. You cannot omit leading zeros.
s
Specifies the relative position of the station within the network. The first
station would be position 1.

RELEASE Command
JOBL
Indicates the individual job to release. JOBL is required to release a specific job. It
must be omitted if JOB or Q are specified.
Required: Yes, unless JOB or Q is used.
longjobname
Q
Indicates to release the contents of an entire queue. Omit Q when JOB or JOBL is
specified.
Required: Yes, unless JOB or JOBL is used.
REQ
Release the contents of the request queue.
RDY
Release the contents of the ready queue.
More information:
HOLD Command (see page 282)
Usage Notes
A request to release an individual job takes precedence over a hold placed on an entire
queue (that is, an entire queue can be held and then jobs released individually to
control the work flow manually).
A job can be in hold status due to a previous request by a HOLD command or the hold
can be permanently defined in the database. In either case, the RELEASE can be used.
A release request by job name causes all jobs, workstation networks, or both with that
name to be released. There can be multiple jobs with the same name.

REMIND Command
Examples
RELEASE,JOB=CA7JOB9
RELEASE,JOB=163
RELEASE,Q=REQ
RELEASE,JOB=0078012
REMIND Command
The REMIND top line command schedules free-form reminder messages, generated
separately through the edit facility, to workstations at a predetermined time. A
free-form message can be defined to communicate anything to a workstation. The
workstation operator is prompted, repeatedly if necessary, to review the defined text.
REMIND,STATION=station,TIME=hhmm[,DATE=yyddd][,SUBID=subid]
STATION
Specifies the logical terminal name (station) to which reminder text in the active
area is directed.
TIME
Indicates the time-of-day at which reminder text in the active area is sent to the
STATION.
hh
Indicates the hour (0 through 23).
mm
Indicates the minutes (00 through 59).
DATE
(Optional) Specifies the Julian date when reminder text in the active area is sent to
the STATION. If DATE is not specified, the current date is used. If the time-of-day
(TIME value) is past and no date is specified, the next day is used.
yy
Indicates the year.
ddd
Indicates the Julian day.

REMIND Command
SUBID
(Optional) Specifies a SUB-ID to further qualify the STATION.
More information:
LRMD Command (see page 526)
Usage Notes
You must place the reminder message to be sent in the CA WA CA 7 Edition active area
before entering the REMIND command. You can accomplish this through the EDIT
command using the INSERT subcommand. After entering the text, the SAVE
subcommand places the text in the active area. Then you can enter the REMIND top line
command. If you enter a REMIND command with a date and time 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 CA WA CA 7 Edition preprocess queue, with a job name in
the format RMD#nnnn, until a LOGOUT or CANCEL is entered. When the reminder is
issued at the specified time-of-day (or immediately as just described), it is reissued for
each reprompt cycle until a LOGOUT or CANCEL is done.
Examples
REMIND,STATION=INPUT,TIME=0800
REMIND,STATION=MAIL,TIME=1630,DATE=09287

RENAME Command
RENAME Command
The RENAME command renames a DASD data set. This function is available on the UT
Menu panel as FUNCTION value 3 or on any other menu or formatted panel as
FUNCTION value UT.3. This command does not rename PDS members or CA WA CA 7
Edition database data sets.
RENAME,DSN=dsname,NEWNAME=newname[,VOL=volume]
DSN
Indicates the old fully qualified name of the data set.
NEWNAME
Indicates the new fully qualified name to assign to the data set.
VOL
Indicates the volume on which the data set resides. The volume on which the data
set resides must be available to CA WA CA 7 Edition.
Required: No, if data set is cataloged.
Examples
RENAME,DSN=USER.FILE1,NEWNAME=USER.FILEX,VOL=VOLM01
RENAME,DSN=USER.FILE1,NEWNAME=USER.FILE2

REPLY Command
REPLY Command
The REPLY top line command sends a message to a system agent in response to an
Intervention Required condition for an agent job. This command is valid only for an
agent job type of AS400_JOB.
REPLY,JOB=jobnumber,{M|MSG}=text
JOB
Defines the specific CA 7 job number for the agent job that requires a reply.
Limits: 1 to 4 numeric digits
MSG
Defines the message text to send. MSG and M can be used interchangeably, but
one or the other is required. If commas are included as part of the text, enclose the
Examples
REPLY,JOB=1234,MSG=I
REPLY,JOB=1711,MSG='THIS IS THE REPLY, PERIOD'
Usage Notes
The agent job requiring the response displays a status of W-REPLY for the queue inquiry
commands. To see the message that requires a reply, use the AGFILE command to
display information about the job from the CA7AGNT VSAM file.
More information:
AGFILE Command (see page 158)

REQUEUE Command
REQUEUE Command
The REQUEUE top line command moves jobs from the ready or active queues back to
the request queue. This command allows the use of the CA WA CA 7 Edition job restart
facilities after certain JCL, CPU, or node/agent failures, or job cancellation out of a CPU
through the OS console. This function is available as the Q option in the QM.1 CPU Jobs
Status Prompt panel.
REQUEUE[,AGENT={*|agentname|mask}]
[,CPU=smfid]
[,FORCE=CMP]
[,MAINID={ALL|SYn|/SYn}]
[,Q={ACT|RDY}]
[,TYPE=JCL]
AGENT
(Optional) Indicates the agent name or mask that an agent name must match for an
agent job before it is moved back to the request queue, given a restart
requirement, and flagged as having been requeued. AGENT cannot be used with
CPU, MAINID, or NODE.
For any agent job that is requeued, a cancel request is sent to the agent running the
job. The status of the agent or the machine on which the agent is running
determines whether the request is honored.
CPU
(Optional) Used with JOB to specify the CPU ID of active queue jobs that are to be
requeued. The value identifies the CPU and corresponds to the CPU field displayed
on the LQ command (the SMF identifier). CPU cannot be used with MAINID, NODE,
or AGENT. The CPU parameter is ignored if used with a JOB parameter that
references a specific job name or job number, but not if a job mask is specified.

REQUEUE Command
FORCE=CMP
(Optional) Resumes job completion for stranded jobs. When a job finishes
executing, it must move to the request queue so that CA WA CA 7 Edition can
process the database and queue updates required for job completion. But, if a job
cannot be moved because of an I/O error or an out-of-space condition on the
request queue, the job may be stranded in the ready or active queue, unable to
complete.
Once the request queue error is corrected, you can use REQUEUE with FORCE=CMP
to resume job completion for these jobs.
JOB
(Optional) Indicates the job number, job name, or mask that a job name must
match before it is moved back to the request queue, given a restart requirement,
and flagged as having been requeued. If JOB is used alone, both the active and
ready queues are searched for the specified JOB. If JOB is used with Q, the search is
restricted to the indicated queue. JOB and JOBL are mutually exclusive.
JOBL
(Optional) Indicates the long job name or mask that a long job name must match
before it is moved back to the request queue, given a restart requirement, and
flagged as having been requeued. If JOBL is used alone, both the active and ready
queues are searched for the specified JOBL. If JOBL is used with Q, the search is
restricted to the indicated queue. JOB and JOBL are mutually exclusive.

REQUEUE Command
MAINID
(Optional) Used with JOB to indicate that only those jobs in the ready queue with
this MAINID are to be requeued. Value must be specified as a single MAINID name.
MAINID cannot be used with CPU, NODE, or AGENT. The MAINID parameter is
ignored if used with a JOB parameter that references a specific job name or job
number, but not if a job mask is specified.
ALL
Indicates that all MAINIDs are considered.
SYn
CPU statement. For more information about the initialization file, see the
Systems Programming Guide. The value of n can range from 1 to 7.
/SYn
Where n indicates a CPU assigned number. The / indicates "not this MAINID."
The value of n can range from 1 to 7.
NODE
(Optional) Indicates the node name or mask that a node name must match for an
XPJOB job, before it is moved back to the request queue, given a restart
requirement, and flagged as having been requeued. NODE cannot be used with
CPU, MAINID, or AGENT.
For any XPJOB that is requeued, a cancel request is sent to the node where the job
is running (assuming the XPDEF file initialization parameter XPKILL=NO is not set).
The status of the node or the machine the node points to, determines whether the
request is honored.
Q
(Optional) Used with JOB to indicate in which queue the job search is to occur.
ACT
Indicates the active queue.
RDY
Indicates the ready queue.
TYPE
(Optional) Indicates to flag the job once it returns to the request queue with a
status of JCLERR instead of REQUE. If not coded, the status reflects REQUE.

REQUEUE Command
More information:
Usage Notes
Exercise care when using the REQUEUE command. Specific times when it may be
necessary to use this command include the following:
■ Certain JCL failures
■ System crashes
■ Node failures
■ Agent failures
■ Alternate platform failures where the platform is pointed to by a node or agent
■ Out-of space conditions on the request queue (FORCE=CMP)
Use of the REQUEUE command causes the jobs to be moved back to the request queue,
given a restart requirement, and flagged as having been requeued. Subsequent inquiries
show a job status of R-REQUE. Then you can use the CA WA CA 7 Edition restart
facilities, QM.4, XRST, or RESTART, to resubmit the job for processing.
Certain VRM resources acquired by the job can be freed when the REQUEUE command
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 is freed when the job is
requeued.
If JOB is not specified, CA WA CA 7 Edition requeues all jobs that meet the Q, MAINID,
CPU, NODE, or AGENT criteria, but at least one keyword must be specified.
In the event of a system failure that strands jobs in the CA WA CA 7 Edition active
queue, 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.

RESANL Command
Examples
REQUEUE,JOB=1234
REQUEUE,JOB=9999,Q=RDY
REQUEUE,JOB=ABC*,CPU=CPU1
REQUEUE,JOB=ABC*,MAINID=SY2
REQUEUE,CPU=CPU1
RESANL Command
The RESANL command causes an analysis of all specified jobs in the specified systems
against the correct number of tape drives needed based on job profiles in the CA WA CA
7 Edition database.
Note: Because cross-platform jobs do not use any tapes drives or data sets, this
command has no effect for cross-platform jobs.
RESANL[,JOB={*|jobname|jobname*}]
[,SYS={*|systemname|systemname*}]
[,TYPE=DS]
[,UPDATE={NO|YES}]
JOB
(Optional) Specifies the job names for which an analysis is performed.
*
Causes the analysis of all jobs. This value is the default.
jobname
Defines a single job name.
jobname*

RESCHNG Command
SYS
(Optional) Specifies the system names for which an analysis is performed.
*
Causes the analysis of all systems. This value is the default.
systemname
Defines a system name.
systemname*
TYPE
(Optional) Specifies data set information. When CA WA CA 7 Edition is analyzing a
data set, an attempt is made to examine the data set's catalog entry. If a data set is
not cataloged, CA WA CA 7 Edition uses the information about the data set that is
stored in the database. When TYPE=DS is specified, CA WA CA 7 Edition uses the
data set information instead of the job information when a catalog entry is not
available.
UPDATE
(Optional) Specifies whether those jobs being analyzed have their WLB tape drive
requirements updated to match their job profiles. The profiles agree with the last
LOAD function performed.
NO
Indicates to make no updates to the database. NO is the default.
YES
Indicates to make updates to the database in addition to providing a list.
RESCHNG Command
Use the RESCHNG command to reduce the number of tape drive requirements for a job
in the active queue.
Tape drives are held by a job until the job is complete. Holding tape drives can pose
contention problems if you are using workload balancing to control the use of tape
drives. A job can continue to hold the tape drives even though it no longer needs them.
You can use RESCHNG to free the tape drives when they are no longer needed.

RESCHNG[,JOB=jobname]{,TP1=nnn}
{,TP2=nnn}
{,TP1=nnn,TP2=nnn}

RESCHNG Command
JOB
Indicates the name of the job to which the change applies. The job must be in the
active queue. JOB is required unless the command is entered from SASSTRLR (trailer
step).
Required: Yes, unless the command is from SASSTRLR
You must specify one or both of the following keywords:

TP1
Changes the TAPE1 requirements for the job.
Limits: 1 to 3 numeric characters from 0 to 255. The value must not exceed TAPE1
number that is assigned to the job.
TP2
Changes the TAPE2 requirements for the job.
Limits: 1 to 3 numeric characters from 0 to 255. The value must not exceed TAPE2
number that is assigned to the job.
Usage Notes
You can insert a trailer step in the job to issue RESCHNG when the tape drives are no
longer needed. This method assumes that the target of the RESCHNG is the job that is
executing and the JOB= keyword is not used.
If the job issues a message that signals that the tape drives are no longer needed, you
can use automation to issue RESCHNG. In this case, JOB= must be specified.
An alternative to RESCHNG is the #RES statement. #RES overrides established resource

requirement values for a job.
Note: For more information about #RES, see the Database Maintenance Guide.

RESOLV Command
Examples
In the following examples, RESCHNG is issued from a trailer step.
This example changes number of TYPE1 tape drives in use to 10. This example frees all
but ten tape drives (used by the previous steps) for scheduling other jobs.
RESCHNG,TP1=10
This example changes number of TYPE1 and TYPE2 tape drives in use to 0. This example
frees all tape drives (used by the previous steps) for scheduling other jobs.
RESCHNG,TP1=000,TP2=000
RESOLV Command
The RESOLV top line command creates or modifies processing schedules for jobs 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 or RUN has no direct
relationship to a base calendar and therefore does not require the use of this function.
You can also request the RESOLV command from the DB.2.1 and DB.2.2 panels. Those
panels are used to define schedule criteria and the name of the default base calendar to
which the schedules apply. The RESOLV command is then used to perform a resolution
process using the specified schedule criteria and the base calendars. Processing
schedules are thus completed, defining the specific dates on which the processing is to
be performed. Scheduling begins automatically when the first date in the RESOLVed
schedule arrives. (These schedules can be further modified using the DB.2.7 function.
Other temporary or onetime changes can also be accomplished through other
commands such as NXTCYC and so forth.)
The RESOLV command selects the schedule members to be processed before actual
schedule resolution activity begins. The JOB and NW parameters are used to identify the
job and network candidates for resolution of schedules. If JOB and NW are omitted, all
jobs and input networks are considered candidates. Two criteria are used for selecting
the schedules to be resolved for those candidates identified:
■ The SCAL value specified in the RESOLV command is matched with the base
calendar references in the schedule data.
■ The OLDYR value specified in the RESOLV command is matched with the base
calendar year in the schedule data.

RESOLV Command
Schedules can be RESOLVed for January through December of the current year, or for
July of the current year through June of the next year. See the YEAR parameter in the
syntax descriptions.
Before CA WA CA 7 Edition can automatically schedule a job, it needs to know the exact
dates the job is to be processed. The RESOLV command takes the specified scheduling
information and compares it to the processing days defined in the base calendars to
calculate the exact processing days. When doing a schedule resolution, CA WA CA 7
Edition looks at the scheduling information in 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 that is based on calendar definition)
4. INDEX field. (process that is based on calendar definition)
RESOLV[,{JOB={*|jobname|jobname*}|NW={NW.network|NW.}}]
[,DUPDATE={YES|NO}]
[,OLDYR={*|yy}]
[,PRINT={NO}YES]
[,SCAL={*|xx}]
[,TEST={YES|NO}]
[,YEAR=yy]
JOB
(Optional) Limits selection for resolution to the jobs specified. When JOB is
specified, omit NW. If both are omitted, all job and input network schedules are
candidates for resolution. Value can be either a specific job name or a generic name
that identifies multiple jobs beginning with the specified characters. An asterisk (*)
must be used to delimit the generic job name. It can appear in any of the 8
positions but must immediately follow the 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.
Limits: Cannot be used with NW.
*
Select all job schedules for resolution.
jobname
Select a specific job name.
jobname*
Select a generic job name (with * used to delimit).

RESOLV Command
NW
(Optional) Limits selection for resolution to the input networks specified. When NW
is specified, omit JOB. If both are omitted, all job and input network schedules are
candidates for selection. When used, value must be one of the following:
Limits: Cannot be used with JOB.
NW.network
Identifies a specific network name to select.
NW.
Indicates that all input networks are considered for resolution. Terminate this
value with a period.
DUPDATE
(Optional) Indicates whether to produce specific duplicate day messages (SRC1-137)
each time a given day is scheduled by two or more schedule IDs for the same
job/network.
The default is NO unless the extended resolve message option has been set in the
user profile by the /PROF command.
OLDYR
(Optional) Specifies the year currently defined in the schedule member data (the
value supplied by YEAR in the previous resolution that updated the schedule
member). Only those candidate schedule members whose year data matches the
OLDYR value are selected for resolution. If used, value must be one of the following:
Default: If omitted, only those schedule members that have not previously been
resolved or whose schedules have expired are selected.
yy
Indicates a specific year.
*
Indicates all years and all schedules.

RESOLV Command
PRINT
(Optional) Specifies whether a month-by-month schedule day calendar is to be
displayed after resolution of the defined member is complete. If used, value must
be either PRINT=YES or PRINT=NO. NO is the default.
SCAL
(Optional) Value is the xx portion of the base calendar name, SCALyyxx. The SCAL
value must also match the base calendar identifier (SCAL) specified in any SCHID of
the schedule definition for the individual jobs or networks. This value is used during
the selection process of resolution to determine which schedule members are to be
resolved.
Required: No (unless JOB and NW are omitted)
*
Indicates all SCALs.
xx
Indicates a specific SCAL.
TEST
(Optional) Indicates whether schedule members are to be updated as a result of the
resolution process. TEST=YES and TEST=NO are the only allowable values.
YES
Normal resolution occurs and all messages are printed, but no updating of the
database occurs. This option can be used at year-end or whenever a base
calendar is changed to see the results of the resolution activity, without
actually changing the schedule mask or affecting the current schedule process.
YES is the default.
NO
Normal resolution occurs and all messages are printed, and updating of the
database occurs.

RESOLV Command
YEAR
(Optional) Identifies the year of the base calendars against which the schedule is
resolved. Value is the number that is specified by the yy portion of the base
calendar name, SCALyyxx. When a schedule is successfully updated, the YEAR value
becomes part of the schedule data (see OLDYR). If the YEAR parameter is not
specified, the current year is assumed to be the year from the system internal date
and time.
Also, if YEAR is not coded on the RESOLV, a check is made to see if the RESOLV is
made within the period January 1 through June 30 as determined from system date
and time. If so, the schedule is resolved against January through December of the
current year. If a RESOLV is done within the period July 1 through December 31, the
schedule is resolved against July 1 through December 31 of the current year and
January 1 through June 30 of the next year. This requires the existence of base
calendars for both calendar years involved. If a required base calendar is not
available, an error message is issued, and the schedule member is not resolved,
unless a perpetual calendar is defined for this SCALyyXX. In that case, the calendar
is generated from the PCALYYXX member in the perpetual calendar data set.
YEAR is optional. If YEAR is specified, the resolution is made against January through
December of the year specified.
Default: Current year
Limits: 2 numeric characters
Note: If year= is specified, use only the current year.
More information:
/PROF Command (see page 130)

RESOLV Command
Usage Notes
Always check the RESOLV output for message SRC1-117 ID MULTIPLE SCHEDULES AT
LEAST ONE DAY. This message indicates two or more schedule IDs are scheduled to
process on the same day. This message can indicate a scheduling error was made. You
need to determine if the job should process multiple times on the same day. If it should,
this is an informational message. If not, the schedule should be corrected.
Assume the following:

■ You receive the following error message:
SRC1-134 JOB jobname NOT RESOLVED - CALENDAR SCALyyss NOT AVAILABLE
■ A perpetual calendar generates SCALyyss
The calendar is not available because an error occurred while generating it from the
perpetual calendar criteria. Use the PRINT command or the LIST function of the
CALMOD command to display the specific error.
When the RESOLV command is entered in the FUNCTION field, a resolution is performed
for a 12-month period. The current year is divided into 6-month intervals. 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 a RESOLV is entered between July 1 and December
31, the resolution attempts to look at July 1 through June 30 of the next year. If next
year's base calendar is not defined, you get error message SRC2-02 BASE CALENDAR
SCALyyxx NOT FOUND, unless a perpetual calendar is defined for this SCALyyXX. In that
case, the calendar is generated from the PCALYYXX member in the perpetual calendar
data set. If no perpetual calendar is defined, add subparameter YEAR=yy to the top line
RESOLV command already displayed, where yy is the current year.
If JOB=* or NW=NW. is specified, all job or input network schedule definitions are
resolved based on the other RESOLV parameters. This command can run for a long time
and generate a large amount of output. The long-running RESOLV commands should be
issued using the batch terminal interface.

RESOLV Command
Examples
This example causes all schedule members that reference base calendar SCAL1301 to be
selected. TEST=NO indicates the schedule members are actually updated. A printout of
the schedule day calendar is also requested.
RESOLV,YEAR=13,SCAL=01,TEST=NO,PRINT=YES
This example causes selection of the schedule member for input network INNET1 if 2012
is the year currently defined in the schedule member. The schedule selected is resolved
for 2013 (SCAL13PR) and the resulting schedule day calendar is printed. Due to the
absence of TEST=NO, the TEST=YES default takes effect, and the schedule member is not
updated in the database.
RESOLV,YEAR=13,SCAL=PR,NW=NW.INNET1,PRINT=YES,OLDYR=08
This example causes all schedule members that reference base calendar SCAL13AC to be
selected for resolution. Previous resolution year data is not considered (OLDYR=*). The
schedule members are updated but calendars are not printed.
RESOLV,YEAR=13,SCAL=AC,OLDYR=*,TEST=NO
This example causes all schedule members that reference base calendar 02, and that
have never been previously resolved, to be selected. Resolution would be for the
current calendar year unless the command is issued from July 1 through December 31. It
would then use the last six months of the current calendar year and the first six months
of the following year to cover a 12-month period. All other RESOLV function parameters
assume default values in this example.
RESOLV,SCAL=02
This example causes all job schedules to be resolved for the current 12-month period.
The schedule members are updated with the results of this RESOLV command. All
calendars referenced by job schedules are used to process this RESOLV.
RESOLV,JOB=*,OLDYR=*,TEST=NO

RESTART Command
RESTART Command
The RESTART top line command restarts a job awaiting restart in the request queue.
This function is available as the F option on the QM.1 CPU Jobs Status Prompt panel.
You can also use QM.4 CPU Job in the Restart Status Prompt panel to accomplish a job
restart. If CA 11 is used, the CMT is updated with the appropriate restart data.
Note: For more information about CA 11, see the Interface Reference Guide.
If CA 11 is not installed, the starting and ending steps, USAGE, PROCESS, CONDCD, or
SUP11STP have no significance.
Note: The cross-platform jobs never use CA 11 services for restart functions.
RESTART,{JOB={jobname|jobnumber}|JOBL=longjobname}
[,BYPGDG={NO|YES|VER|CAT}]
[,CONDCD=nnnn]
[,FORCECOMP={NO|YES}]
[,LCC=nnnn]
[,LSTP=stepname]
[,LPSTP=procname]
[,PROCSTRT=procname]
[,PROCEND=procname]
[,PROCESS=code]
[,REASON=text]
[,STPEND=stepname]
[,STPSTRT={stepname|*CMT*|*RERUN*|*RESUBP*}]
[,SUP11STP={NO|YES}]
[,USAGE=code]
JOB
Indicates the unique CA 7 job name or job number of the job to restart. The job
must be in the request queue. JOB and JOBL are mutually exclusive.
jobname
jobnumber

RESTART Command
JOBL
Indicates the unique CA 7 job name or job number of the job to restart. The job
must be in the request queue. JOB and JOBL are mutually exclusive.
longjobname
BYPGDG
(Optional) Indicates whether CA 11 bypasses GDG logic on a restart/rerun. Value
can be NO, YES, VER, or CAT.
Default: CA 11 default value
CONDCD
(Optional) Indicates an optional CA 11 condition code that the CA 11 step sets when
the rerun is executed. This option is honored only if CA 11 is in use and CA WA CA 7
Edition is inserting the RMS step. See the INSERT-RMS field on the DB.1 panel.
FORCECOMP
(Optional) Indicates whether to flag the job as normally completed. If
FORCECOMP=YES, the job's previous abnormal status is ignored, and normal job
completion processing is performed instead of a restart. Value can be NO or YES.
NO is the default.
LCC
(Optional) Indicates an optional condition code value that replaces the last
condition code value for the step that the LSTP references and, optionally, LPSTP
keywords. This option is honored only if CA 11 is in use.
Default: 0
LSTP
(Optional) Indicates an optional step name that has its last condition code value
reset in the CA 11 CMT. Code LSTP and LCC when LPSTP is specified. LSTP requires
that an STPSTRT value is specified and that the LSTP step name occurs in the job's
JCL before the STPSTRT step name. This option is honored only if CA 11 is in use.
LPSTP
(Optional) Indicates an optional step name referencing a procedure that has its last
condition code value reset in the CA 11 CMT. If LPSTP is used, also code LSTP and
LCC. This option is honored only if CA 11 is in use.

RESTART Command
PROCSTRT
(Optional) Indicates an optional step name referencing a procedure where
processing is to start. If PROCESS=R and PROCSTRT are used, also code STPSTRT.
This option is honored only if CA 11 is in use.
PROCEND
(Optional) Indicates an optional step name referencing a procedure where
processing is to end. If PROCESS=R and PROCEND are used, code STPEND. This
option is honored only if CA 11 is in use.
PROCESS
(Optional) Indicates an optional CA 11 processing function code character to use in
the restart/rerun. This option is honored only if CA 11 is in use and CA WA CA 7
Edition is inserting the RMS step. See the INSERT-RMS field on the DB.1 panel. Value
can be F, P, S, N, O, or R.
Default: P
Limits: 1 alphabetic character
REASON
(Optional) Specifies a reason for the restart. If the CA 11 Reason-for-Rerun module
is available, a code of up to four characters can be input and it is expanded. Any
reason input or expanded is copied to the run log. This field is optional unless CA 11
requires a reason or REASON=YES was specified in the RESTART statement in the
initialization file. For more information about the initialization file, see the Systems
Programming Guide.
STPEND
(Optional) Indicates an optional step name or number at which processing is to end.
If not specified, the last step of the job is assumed to be the ending step. Code
STPEND when PROCEND is specified. This option is honored only if CA 11 is in use.

RESTART Command
STPSTRT
(Optional) Indicates an optional step name or number at which processing is to
start. If STPSTRT is not coded, the first step of the job is assigned to be the starting
step. Code STPSTRT when PROCSTRT is specified. This option is honored only if CA
11 is in use.
stepname
Specifies the step name or number at which processing is to start.
*CMT*
Indicates that the job is to restart with the step values currently on the CMT
record.
*RERUN*
Indicates to rerun t the total job. If there are no restartable steps, specify
*RERUN*.
*RESUBP*
Indicates that the CMT record of the job is set to production, and then the job
is submitted.
SUP11STP
(Optional) Indicates whether to suppress the insertion of the CA 11 RMS step. If the
job is resubmitted with SUP11STP=YES, the CA 11 step is not inserted. Only valid if
CA WA CA 7 Edition is inserting the CA 11 step. See the INSERT-RMS field on the
DB.1 panel. Value can be NO or YES. NO is the default.
USAGE
(Optional) Indicates an optional CA 11 usage code of the character to use in the
restart/rerun. For the values, see the CA 11 documentation. This option is honored
only if CA WA Restart OptionCA 11 is in use and CA WA CA 7 Edition is inserting the
RMS step. See the INSERT-RMS field on the DB.1 panel.
More information:
QM.1 CPU Jobs Status Prompt Panel (see page 573)

QM.4 CPU Job In Restart Status Prompt Panel (see page 597)

RM Command
RM Command
The following is a brief description of the RM commands.
Note: For more information about the commands, see the Database Maintenance
Guide.
RM
Selects the virtual resource management functions.
RM.1 Job Resource Management
Lists, adds, updates, or deletes resource connections by job. The command
generates the VRM static type J and R records maintained on the VRM database
component.
RM.2 Job Resource Cross-Reference
Lists jobs using resources. The jobs can be listed by a fully qualified resource name
or by a generic key.
RM.3 Active Job Resources Display
Displays active resources by job. The jobs can be listed generically or with fully
qualified job names.
RM.4 Pending Resources Job Display
Displays all pending resources with an associated job name. A pending resource is a
nonfreed resource connected to a job that has already executed and has been
purged from the request queue. This resource can only be freed by using the PRSCF
command. The pending resources can be listed using a generic or fully qualified
resource name.
RM.5 Jobs Waiting on Resources
Displays jobs waiting for resources. The command can show the resources that a
job is waiting for when the job shows a status of W-RSRC on the List Queue (LQ)
display.
RM.6 Corequisite Resources List
Lists active corequisite resources.
RM.7 Resource Count Resource Management
Lists, adds, updates, or deletes a resource count type resource.

RQVER Command
RQVER Command
The RQVER command reviews internal JOB/DSN requirements for request queue jobs
that have not been satisfied and optionally posts outstanding requirements when
UPDATE=YES is used.
RQVER[,JOB={*|jobname|jobname*}]
[,MAXJOBS={0300|nnnn}]
[,SYS={*|systemname|systemname*}]
[,UPDATE={NO|YES}]
JOB
(Optional) Specifies the job names for which an analysis is performed.
*
Causes the analysis of all jobs. This value is the default.
jobname
Defines a single job name.
jobname*
MAXJOBS
(Optional) Indicates 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
Note: If the number of jobs in the request queue exceeds the MAXJOBS value, then
no updating (satisfying) of requirements occurs.
SYS
(Optional) Specifies the system names for which an analysis is performed.
*
Causes the analysis of all systems. This value is the default.
systemname
Defines a system name.
systemname*

RSVP Command
UPDATE
(Optional) Specifies whether to update (satisfy) missing JOB/DSN requirements and
adjust master requirements counts in the queue records for jobs reviewed.
NO
Specifies no updating. NO is the default.
YES
Specifies updating.
RSVP Command
The RSVP top line command acknowledges receipt of a prompt and suspends further
prompting for that deadline. Both input and output workstations can use this command.
This function is available as the P option on the following panels:
■ QM.1 CPU Jobs Status Prompt panel
■ QM.6 Input Networks Prompt panel
■ QM.7 Output Networks Prompt panel
When CA WA CA 7 Edition detects a workstation activity that has not been logged in or
out by the scheduled time, a message is issued. This message notifies the workstation of
the late status of the activity specified. If the activity for which the station is being
prompted is on schedule, the response should be a LOGIN or LOGOUT. If the activity is
late and the workstation is aware of the late status but unable to do anything new to
correct it, the repetitive prompting can be suspended by acknowledging receipt of the
message with the RSVP command.
RSVP,{JOB=jobnumber|REF=nnnnrrs}
[,NW=network]
[,STATION=station]
[,SUBID=subid]

RSVP Command
JOB
Specifies the unique CA 7 job number that is assigned to the task when it entered
the queue.
Required: Yes, unless REF is used.
REF
Specifies workstation network task reference number of the station to which the
RSVP applies. When REF is specified, other operands are ignored.
Required: Yes, if JOB is not used.
nnnn
rr
Relative sequence of the network in relation to other networks associated with
the job. Leading zeros cannot be omitted.
s
Relative position of the station within the network. The first station is position
1.
NW
Identifies the network for which the RSVP is being entered. If used, the value must
be the workstation network name in up to eight characters. NW is required if JOB is
used for an output workstation network. Omit NW when REF is used instead of JOB.
Required: Yes, if JOB is used.
STATION
Specifies the station to which the RSVP applies. If used, the value must be the
station name. STATION is required if JOB is used for an output workstation network.
Omit STATION when REF is used.
Required: Yes, if JOB is used.
SUBID
(Optional) Further identifies the network to which the RSVP applies. If used, the
value must be a SUBID name. Omit SUBID when REF is used. If omitted, spaces are
assumed.

RUN, RUNH Command
Usage Notes
Responding to a prompt with RSVP causes further prompting to be suspended for the
specified workstation activity until the next scheduled deadline time occurs.
The XPRE, XSPRE, XSPOST, and XPOST panels can also be used to perform this function
when working with 3270 terminals.
The RSVP top line command is used to respond to or acknowledge late status prompts
for a single job. It suspends further prompting for the job until the next scheduled
deadline. This is different from NOPRMP, which suspends prompting for all remaining
deadlines for that task.
RSVP can also be used to suspend prompting when a job has unsatisfied requirements.
RSVP also suspends prompting of the abnormal completion messages for jobs that fail.
Examples
RSVP,JOB=17,STATION=KEYPNCH
RSVP,JOB=163,NW=REPTDSTR,SUBID=PAYR1234,STATION=BURSTRM
RSVP,REF=11011
RUN, RUNH Command

The RUN top line command forces immediate scheduling of a job without verifying the
availability of any input requirements or performing the updates that normally follow
successful job completion. The RUN command is similar to the DEMAND command.
When DEMAND is used, input requirement checking is performed and database
updating is done upon completion of the job. When RUN is used, no requirement
posting or job triggering occurs.
The RUNH command indicates to place the job in CA WA CA 7 Edition hold status.

RUN, RUNH Command
{RUN|RUNH},{JOB=jobname|JOBL=longjobname}
[,ARFSET={arfsetname|**NONE**}]
[,CLASS=x]
[,DOTM=hhmm]
[,EXEC={NO|YES}]
[,FROMNODE]
[,LATE={NO|YES}]
[,LEADTM={hhmm]
[,REF]
[,RMS={NO|YES}]
[,SCHID={1|nnn}]
[,TIME=hhmm]
[,TYPE=RES]
You cannot specify FROMNODE or REF. See the Usage Notes (see page 650).
JCLID, JCLLIB, MAINID, and RMS are invalid with internal cross-platform jobs.
JOB
Identifies the job to submit. The value must be a job name. If the job has not been
defined in the database, this name must also match the member name for the JCL
unless the job is defined in the database. See also JCLID. JOB and JOBL are mutually
exclusive.
JOBL
Identifies the job to submit. The value must be a long job name. If the job has not
been defined in the database, use JOB instead. See also JCLID. JOB and JOBL are
mutually exclusive.
longjobname
ARFSET
(Optional) Identifies 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**
CLASS
(Optional) Specifies the workload balancing class for resource checking.

RUN, RUNH Command
DOTM
(Optional) Specifies a due-out time-of-day for the job. If omitted, the current time
(when command is processed) plus the lead time is used.
hhmm
Defines the time-of-day where hh is the hours (0 to 24) and mm is minutes (00
to 59). You can omit leading zeros.
EXEC
(Optional) Specifies whether to execute the job (YES/NO). If NO (N) is used, the job
does not run but shows a normal completion as if it did run. The value specified
here overrides the value coded on the job definition EXEC field.
Default: The job definition panel EXEC value if job defined to CA WA CA 7 Edition;
otherwise YES.
JCLID
If used, the value must be a numeric INDEX associated with the wanted JCL data set
JCLLIB field is required if the job is not defined in the database. JCLID and JCLLIB are
mutually exclusive.
255 is reserved.

RUN, RUNH Command
JCLLIB
If used, the value must be a symbolic INDEX associated with the wanted JCL data set
JCLID field is required if the job is not defined in the database. JCLID and JCLLIB are
mutually exclusive.
LATE
(Optional) Specifies whether notification should occur if the job becomes late.
will never be marked LATE. The value specified here overrides the value coded on
the job definition PROMPTS field.
LEADTM
(Optional) Specifies the lead (processing) time required for the job to run. If
omitted, 1 hour is used.
hhmm
Defines the time where hh is hours (0 to 23) and mm is minutes (00 to 59). You
can omit leading zeros.
MAINID
to which the job is to be redirected. The value specified here overrides the value
coded on the job definition MAINID field.
The name must be one of the following:
ALL
SYn
from 1 to 7.

RUN, RUNH Command
/SYn
from 1 to 7.
-SYn
from 1 to 7.
Limits: Invalid with cross-platform jobs
RMS
(Optional) Specifies whether CA WA CA 7 Edition inserts the CA WA Restart Option
RMS step. Specify YES (Y) to insert the step with the CA WA Restart Option
processing code of P. Enter NO (N) to indicate the RMS step is not to be inserted.
The value specified here overrides the value coded on the job definition
INSERT-RMS field.
Default: The job definition panel INSERT-RMS value if job defined to CA WA CA 7
Edition; otherwise NO.
Limits: Invalid for cross-platform jobs.
Note: For more information, see the Interface Reference Guide.
SCHID
(Optional) Indicates the schedule ID to be used for evaluating JCL overrides that are
scheduled with the #Jx or #Xx commands. If used, the value must be a schedule ID
number.
Default: 1
Required: No (unless the SCHEDULE statement in the initialization file specifies
SCHID=YES, then this parameter is required)
TIME
(Optional) Establishes a submit time-of-day requirement for the job.
hhmm
Defines the time-of-day where hh is hours (0 to 23) and mm is minutes (00 to
59). Leading zeros are not required.
TYPE
(Optional) Indicates the job is being scheduled for rerun. The value must be
specified as shown. TYPE=RES is optional. If used, a restart requirement is placed on
the job, and the job has to be manually restarted.

RUN, RUNH Command
More information:
QM Command (see page 572)

XRST Command (see page 718)
RESTART Command (see page 637)
Usage Notes
The following normal scheduling activities of CA WA CA 7 Edition 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 posting includes mutually exclusive
job dependencies.
■ Scheduling of job or data set triggered (AUTO) jobs.
■ #JCL statement in JCL. The statement is taken out, but the override indication is not
done.
The following normal scheduling activities occur:

■ If the job becomes late, the appropriate LTERM is prompted.
■ 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 CA WA CA 7 Edition restart facilities,

QM.4 panel, or RESTART command can be used to restart or rerun the job.
If workload balancing is used, the job is run under the default WLB class for RUN if the
CLASS= keyword is not specified.
Note: For more information about the RUNCLASS parameter on the OPTIONS statement
in the initialization file, see the Systems Programming Guide.

RUNNW Command
REF and FROMNODE are reserved keywords that are not considered valid input unless
generated by CA WA CA 7 Edition internally. These keywords cannot be coded on online,
batch, or trailer terminal transactions. They are reserved for special functions but are
described here because they can occur in master station messages.
If REF is specified, the job does not wait for restart in the request queue following
abnormal job completion.
All cross-platform jobs must be defined in the CA WA CA 7 Edition database, because

selected information for each job is contained in the cross-platform job definition. As a
result, cross-platform jobs cannot be added to the database through the RUN(H)
command.
Examples
RUN,JOB=CA7JOB5
RUN,JOB=CA7JOB1,TYPE=RES
RUNH,JOB=CA7JOB4,DOTM=1530,LEADTM=35,SCHID=270
RUNNW Command
The RUNNW top line command is used in place of the DMDNW command to force the
initiation of input or output networks. When used for input networks, no requirement
posting or job triggering occurs. When used for output networks, no association is made
to the job.
RUNNW,NW=network
[,DESC=text]
[,JOB=name]
[,LEADTM=hhmm]
[,SCHID={1|nnn}]
[,SUBID=subid]
NW
Specifies the network name to schedule. The value must be the network name that
is used when the network was defined in the database.

RUNNW Command
DESC
(Optional) Supplies more identifying free-form information up to eight characters.
This value is displayed on the QM.6, QM.7, LPRE, and LPOST panels.
JOB
(Optional) Supplies a name to assign to the network. If you do not specify SUBID or
JOB, JOB defaults to DMD#nnnn, where nnnn is the CA WA CA 7 Edition assigned
job number.
Default: SUBID
LEADTM
(Optional) Specifies a lead (processing) time for calculating a deadline start time of
the first station in the network.
hhmm
Defines the time where hh specifies hours (0 through 99) and mm specifies
minutes (00 through 59). The leading zeros are not required.
SCHID
(Optional) Identifies which network schedule ID that you want to use.
Default: 1
SUBID
(Optional) Supplies another identifying name for the network when it enters the
queue.
Usage Notes
When a network is scheduled, CA WA CA 7 Edition determines whether the network
should be placed in the preprocess or postprocess queue based on the definition of the
network in the database.
All networks can be requested independently from jobs.
A job name is assigned to the network when it enters the queue.

RUSH Command
Examples
RUNNW,NW=RECPTS
RUNNW,NW=REPTS,SUBID=PAYR1234,DESC=PAYDATA
RUNNW,NW=REPTS,SCHID=270,LEADTM=0125
RUSH Command
The RUSH top line command flags jobs in the queues as being needed as soon as
possible. The flag is for subsequent display information only, displaying the 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 the STATUS
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 if any error is awaiting
resolution.
RUSH,{JOB={jobnumber|ALL|ALLP}|REF=nnnnrrss}
JOB
Indicates the jobs to be flagged as critical.
Required: Yes, unless REF is used (in which case omit JOB).
jobnumber
Indicates a job number to select.
ALL
ALLP
Indicates same as ALL but includes all networks in the preprocess queue as
well.

SCHDMOD Command
REF
Specifies workstation task reference number of the station to which the command
applies.
Required: Yes, unless JOB is used (in which case omit REF).
nnnn
CA 7 job number. You can omit leading zeros. Reference numbers can be
rr
Relative sequence of the network in relation to other networks associated with
the job. You cannot omit leading zeros.
s
Relative position of the station within the network. The first station is position
1.
SCHDMOD Command
The SCHDMOD command displays the DB.2.7 - Modification to Resolved Schedule Dates
panel.
Note: For more information about this panel, see the Database Maintenance Guide.
SCHDMOD
The SCHDMOD command has no associated keywords.

SCRATCH Command
SCRATCH Command
The SCRATCH command scratches an expired DASD data set. The SCRATCHP command
scratches a data set even if it is date protected. This function is also offered on the UT
Menu panel as function 4.
{SCRATCH|SCRATCHP},DSN=dsname[,VOL=volume]
DSN
Indicates the fully qualified name of the data set. A relative generation request can
be made for a cataloged generation data set. This command does not scratch PDS
members.
VOL
(Optional) Indicates the volume on which the data set resides. The volume must be
available to CA WA CA 7 Edition. If the catalog is used, the data set is uncataloged if
the scratch is successful.
Default: System catalog
Usage Notes
CA WA CA 7 Edition provides a user exit to control the use of this command.
This command does not remove data sets from the CA WA CA 7 Edition database.
A DD statement of the following form must exist in the CA WA CA 7 Edition JCL for each
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 ALLOC command
or function 11 on the UT Menu panel can be used if the needed DD statement was not
included in the JCL.

SPACE Command
Examples
SCRATCH,DSN=USER.FILE1
SCRATCH,DSN=USER.FILE2,VOL=VOLMO1
SCRATCHP,DSN=USER.DATE.PROT,VOL=VOLMO2
SCRATCH,DSN=USER.GDG(0)
SPACE Command
The SPACE command lists information about available space on DASD volumes available
to CA WA CA 7 Edition. This function is available on the UT Menu panel as FUNCTION
value 16 or on any other menu or formatted panel as FUNCTION value UT.16.
SPACE,VOL={ALL|volume|(volume,...volume)}
VOL
Indicates the volumes for which to display space information.
ALL
Specifies all volumes available to CA WA CA 7 Edition by way of //U7nnnnnn DD
statements.
volume
Identifies a specific volume.
(volume,...,volume)
Identifies up to five volumes and enclosed in parentheses.

SSCAN Command
Examples
SPACE,VOL=ALL
SPACE,VOL=VOLMO1
SPACE,VOL=(VOLMO1,VOLMO2,VOLMO4,VOLMO7)
Displayed for each volume are unit name, UCB address, device code, user count, reserve
count, number of free cylinders, number of free tracks, and the largest contiguous
extent.
Use SPACE,VOL=ALL to determine which volumes are available to CA WA CA 7 Edition by

way of //U7nnnnnn DD statements.
SSCAN Command
The SSCAN top line command reviews schedule scan options or alters the way in which
schedule scan performs its scheduling functions. Schedule scan is an automatic
scheduling facility and can be altered as follows:
■ Schedule scan can be forced to run ahead of schedule, either to bring more work
into the queues, or to reissue prompts for overdue jobs or workstation activities.
■ The time parameters that govern schedule scan execution can be modified online.
■ The format of initial requirements scan output and prompt messages can be
abbreviated. Jobs are scanned as they enter the request queue to see if any
requirements are satisfied. This is the initial requirements scan.
■ The due-out time of all newly scheduled work can be delayed as it enters the
queue.
■ Schedule scan can cause all new work to enter the queue in CA WA CA 7 Edition
hold status.
■ Schedule scan can cause posting of the ARF dispatcher.
Any change made to parameters controlling schedule scan execution does not take
effect until the appropriate schedule scan activity runs.

SSCAN Command
SSCAN[,DATE=yyddd]
[,INCR=hh]
[,LEADTM={0|mmmm}]
[,PEREND=hhmm]
[,PERSTART=hhmm]
[,QDWELL=mm]
[,REPRMPT=mm]
[,RETRY=mm]
[,SCAN=function]
[,SPAN=hh]
[,TIME=hhmm]
[,XPRETRY=mm]
DATE
(Optional) Used with PERSTART to cause schedule scan to go back and repeat
functions that were performed on a previous date. This parameter is useful in a
recovery situation to cause work that may have been lost to again be brought into
the queues. A system clock error that caused work to be skipped can also be
handled in this manner. DATE is optional but, when specified, must be the
beginning Julian date for which schedule scan functions are to be performed.
Note: If the date needs to be set forward (future), an SSCAN command with
TIME=0, must be entered followed by another SSCAN command with DATE=00000,
PERSTART=hhmm before the SSCAN command with the future date.
Limits: 5 numeric characters in yyddd format
INCR
(Optional) Changes the time interval to elapse between schedule scan wake-ups.
The INCR value must not be greater than the SPAN value.
Limits: 1 to 2 numeric characters from 1 to 24 hours
LEADTM
(Optional) Specifies a number of minutes to be added globally to the schedule times
of all the work entering the queue. If 0 is specified, no change is made to the
scheduled times for the work.
Default: 0
Note: Does not apply to preprocessing work or demanded jobs.

SSCAN Command
PEREND
(Optional) Used with PERSTART and DATE to set an ending time for schedule scan
functions. Must be the time-of-day desired in the hhmm format. When PEREND is
used, the automatic wake-up of schedule scan is disabled. The SSCAN,SCAN=SCH
command or a startup of CA WA CA 7 Edition must be used to force schedule scan
to run. After schedule scan is complete, automatic wake-up is still disabled. This
allows another PEREND time to be entered, if necessary. To resume automatic
wake-up of schedule scan, use SSCAN,TIME= specifying a time when schedule scan
is to wake-up. A new field appears under NEXT SCAN PERIOD START TIME when this
parameter is in effect.
When using PEREND, we recommend that the CA WA CA 7 Edition initialization file
INIT statement PERFORM option of 5 (duplicate checking) not be used. This lessens
the possibliity of a "duplicate" job being scheduled.
PERSTART
(Optional) Used with DATE to set schedule scan functions back to a previous time.
Must be the time-of-day desired in hhmm format.
QDWELL
(Optional) Specifies an additional number of minutes to be added to the span time,
as an additional safety factor, to ensure that scheduling requirements can be met
between the queue entry and deadline times.
Limits: 1 to 2 numeric characters from 1 to 59 minutes
REPRMPT
(Optional) Specifies a number of minutes to elapse between a prompt message and
each subsequent reprompt. If REPRMPT=0, the reprompt function of schedule scan
is suspended.
RETRY
(Optional) Specifies a number of minutes between wake-ups for reattempting to
attach JCL and requirements for jobs in RETRY status. Jobs are in RETRY status when
a dynamic allocation (SVC99) failure occurs during scheduling (that is, date
schedules, triggers or DEMAND commands). If 0 (zero) is specified, the RETRY
function is suspended.

SSCAN Command
SCAN
(Optional) Indicates the type of schedule scan function to perform.
ABR
Abbreviates the format of initial requirements scan output and prompt
messages.
ARF
Causes posting of the ARF dispatcher.
COM
Forces a completion processing cycle to run and check for completed jobs.
HLD
Forces all jobs to be placed in CA WA CA 7 Edition hold status as they enter the
queue. Jobs must then be released on a job-by-job basis. The effect of
SCAN=HLD can be disabled by SCAN=REL.
LNG
Restores the normal format of initial requirements scan output and prompt
messages.
REL
Disables the effect of a previous SCAN=HLD.
REP
Forces immediate reprompting for jobs and workstation activities that are late.
RET
Forces a skeleton retry cycle. See the RETRY parameter for more information
about RETRY.
SCH
Forces schedule scan to run and add more work to the queues. This function
activates schedule scan if it is not active.

SSCAN Command
SPAN
(Optional) Changes the number of hours that schedule scan is to look forward,
during each wake-up, for jobs that must be added to the queue. The SPAN value
must not be less than the INCR value.
Limits: 1 to 2 numeric characters from 1 to 24 hours
TIME
(Optional) Specifies the next wake-up time-of-day for schedule scan to bring jobs
into the queues. This value is normally determined by adding the INCR value to the
previous scan. If 0 is specified for TIME, this function of schedule scan is disabled. If
the time specified is less than the current time, the next day is assumed.
hhmm
Defines the time-of-day where hh represents hours (0 to 24) and mm
represents minutes (00 to 59).
XPRETRY
(Optional) Specifies a number of minutes between attempts to send data to the
targeted node or its alternates for XPJOB jobs waiting in the request queue in some
type of node status. Even if a non-zero XPRETRY value is coded, attempts to resend
data are determined on a job-by-job basis based on node states. An attempt to
resend data is not made if there is no chance for success. An attempt to resend data
is made for the following node state values:
■ The primary node is in state ONLINE or FAIL.
■ The primary node is in state OFFLINE, Alternate node1 is defined and in state
ONLINE or FAIL.
■ The primary node is in state OFFLINE, Alternate node 1 is defined and in state
OFFLINE, Alternate node 2 is defined and in state ONLINE or FAIL.
Default: 0 (no retry)
Limits: 1 to 2 characters from 0 to 60
Usage Notes
A job is selected for scheduling if its queue entry time falls within the time window
(current time plus span) currently being scanned. Queue entry time is determined by
adding the queue dwell time factor to the lead time defined in a job'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 no

parameters.

START Command
Examples
SSCAN,SCAN=REP,REPRMPT=5
SSCAN,QDWELL=30
SSCAN,SPAN=3,INCR=2
SSCAN,TIME=1900
SSCAN
CURRENT SCHEDULE SCAN VALUES

----------------------------
SPAN = 240 INCREMENT = 120
QUEUE DWELL = 30 SKELETON RETRY = 5

REPROMPT = 10 XP RETRY = 40
LEAD TIME = 0
STATUS: REQQ IS ACTIVE ABR MSGS = NO

RDYQ IS ACTIVE HOLD JOBS = NO
NEXT SCAN WAKE-UP = 99999 AT 3679
NEXT SCAN PERIOD START TIME = 00000 AT 0000
START Command
The START top line command resumes normal job flow in the request and ready queues
after a previous STOP command was issued to halt job flow. A START command is
required to reestablish normal queue activity following a STOP command.
START,Q={ALL|RDY|REQ}
Q
Identifies the queues to restart after a previous STOP command was issued.
ALL
Causes the restart of both the request and ready queues.
RDY
Causes the restart of the ready queue.
REQ
Causes the restart of the request queue.

STOP Command
Examples
START,Q=REQ
START,Q=RDY
START,Q=ALL
STOP Command
The STOP top line command temporarily suspends normal job movement in either the
request or ready queues, or both.
STOP,Q={ALL|RDY|REQ}
Q
Identifies the queues to suspend. Queues can be restarted with the START
command.
ALL
Causes both the request and ready queues to be suspended.
RDY
Causes the ready queue to be suspended.
REQ
Causes the request queue to be suspended.
Usage Notes
Stopping the request queue halts all movement of jobs to the ready queue until a START
is issued for the request queue. All other functions that relate to jobs in the request
queue continue normally and outstanding requirements are posted as they are satisfied.
JCL overrides can be entered and manual posting done, prompts are issued for jobs that
are late, and so forth.
Stopping the ready queue prevents submission of any jobs for execution on the CPUs.
Movement of jobs into the ready queue continues normally unless the request queue is
also stopped.

SUBMIT Command
Examples
STOP,Q=REQ
STOP,Q=RDY
STOP,Q=ALL
SUBMIT Command
The SUBMIT top line command modifies and expedites the process of job submission for
jobs that already reside in the queues. This processing can be accomplished in two ways:
■ All outstanding input requirements for the specified jobs can be posted as satisfied.
■ Optionally, by specifying EXPRESS=YES, a priority can be set for a specific job,
ensuring that the job is submitted ahead of other jobs also ready for submission.
Note: EXPRESS=YES has no effect when workload balancing is being used.
SUBMIT[,JOB=jobnumber][,EXPRESS=YES]
JOB
Specifies the CA 7 job number of the job whose requirements you want to post as
satisfied.
EXPRESS
(Optional) Indicates to place the job ahead of all other jobs (those jobs without
EXPRESS=YES) for submission. Must be coded as shown. Not valid if workload
balancing is being used. Use of EXPRESS=YES does not establish an increased
execution priority for a job. Rather, it ensures that nonexpress jobs are not
submitted ahead of a job that is flagged as an express job.
Note: If you specify no keywords, CA WA CA 7 Edition job submission is activated. If you

use CA WA Restart Option, it verifies whether the interface is still active. If the interface
is not active, then a WTOR is issued. CA WA CA 7 Edition is in a wait state until the
operator replies.

SUBSCH Command
Examples
SUBMIT,JOB=163
SUBMIT,JOB=163,EXPRESS=YES
SUBMIT
SUBSCH Command
The SUBSCH top line command adjusts schedules to advance the overall processing of
the system. A user-supplied increment of up to 24 hours can be subtracted from the
scheduled start and due-out times. This command can establish earlier deadlines for the
start and due-out times of one or all jobs in a queue. This adjustment is only possible
after the job or workstation activity has entered the queue.
SUBSCH,{JOB={nnnn|ALL|ALLP}|REF=nnnnrrs},TIME=mmmm
JOB
Identifies the jobs for which an adjustment to schedule times is necessary.
Required: Yes, unless REF is used (in which case, omit JOB).
nnnn
CA 7 job number.
ALL
All jobs in the request, ready, and postprocess queues.
ALLP
All jobs including those jobs in the preprocess queue.

SUBSCH Command
REF
Specifies a particular workstation network task within a network and all subsequent
stations for which schedules an adjustment is necessary. Reference numbers can be
Required: Yes, unless JOB is used (in which case, omit REF).
nnnnrrs
Defines the workstation reference number that CA WA CA 7 Edition assigned.
nnnn
rr
Relative network sequence for this job number. You cannot omit leading zeros.
s
Relative station position within the network. The first station is position 1.
TIME
Specifies the amount of time to subtract from the deadline start and due-out times
of the jobs or workstations indicated.
Usage Notes
It may be desirable to improve on established schedules if a block of work is canceled, if
a resource is made available that is normally dedicated to another function, or if other
work has completed well ahead of schedule.
When SUBSCH is used to adjust schedules, prompting is based on the adjusted deadline
start and due-out times.
To delay schedule times, use the ADDSCH command. The XUPD panel can also 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 a job show as
"late" earlier.
More information:
ADDSCH Command (see page 155)

SUBTM Command
Examples
SUBSCH,JOB=143,TIME=120
SUBSCH,JOB=ALLP,TIME=720
SUBSCH,REF=12011,TIME=600
SUBTM Command
Note: This function is available through the QM.3 CPU Job Attributes Prompt panel and
can be satisfied through the QM.1 CPU Jobs Status Prompt panel.
The SUBTM command modifies the required submit time-of-day for a job in 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 than defined.
SUBTM,JOB=jobnumber[,TIME=hhmm]
JOB
Specifies the CA WA CA 7 Edition assigned job number of the job for which you
want to add, modify, or remove a submit time-of-day requirement.
TIME
(Optional) Specifies the new submit time-of-day in hours and minutes. TIME is
required to add a submit time-of-day requirement if none exists or to change an
existing requirement. If TIME is omitted, an existing submit time-of-day restriction
is removed.
hhmm
Defines the time-of-day where hh is hours (0 through 24) and mm is minutes
(00 through 59). Maximum is 2400.
If the value given is less than the current time (when the command is processed),
the submit day is incremented by one.

TIQ Command
Examples
SUBTM,JOB=163
SUBTM,JOB=163,TIME=1830
TIQ Command
If you have CA 1 installed on your system, you can use the TIQ command to directly
interact with CA 1.
Note: For more information about the CA WA CA 7 Edition/CA 1 interface and the TIQ
command, see the Interface Reference Guide.
UNC Command
The UNC command uncatalogs a data set. This function is available on the UT Menu
panel as FUNCTION value 5 or on any other menu or formatted panel as FUNCTION
value UT.5.
UNC,DSN=dsname[,CVOL=volume]
DSN
Defines the fully qualified name of the data set that you want to uncatalog. A
relative generation request can be made for a generation data set. After you
uncatalog the data set, its index is deleted if other data sets no longer use it.
CVOL
(Optional) Defines the volume containing the catalog.
Default: SYSRES volume
Examples
UNC,DSN=USER.FILE1
UNC,DSN=USER.GDG(+0)
UNC,DSN=USER.FILE2,CVOL=ALTCAT

UT Command
UT Command
The CA-7 Utilities Menu panel displays the online menu of available utility functions.
--------------------------- CA-7 UTILITIES MENU -----------------------------

FUNCTION ===>
DATASET MAINTENANCE: VOLUME ACCESS:

1 - ALLOCATE/CATALOG 11 - ALLOCATE
2 - CATALOG 12 - DEALLOCATE
3 - RENAME
4 - SCRATCH DISPLAY DASD INFO:
5 - UNCATALOG 13 - FORMAT 1 DSCB
14 - DIRECTORY INFO
CATALOG/INDEX MAINTENANCE: 15 - DATASET ATTRIBUTES MAP
6 - BUILD GDG INDEX 16 - AVAILABLE DASD SPACE
7 - DELETE INDEX 17 - PHYSICAL DATA RECORDS
8 - CONNECT A CATALOG 18 - CATALOG BLOCK
9 - DISCONNECT A CATALOG 19 - CATALOG ENTRIES
DATASET SEARCH:
10 - FIND DSN ON DASD
PROGRAM: UTL0 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:
field.

UT Command
Usage Notes
The UT menu is not available in batch mode.
Each function on the panel has an equivalent top line command. Each selection on the
menu panel receives the same security validation as its equivalent top line command.
Menu functions and their equivalent CA WA CA 7 Edition top line commands are as
follows:
1 - AL/ALC 11 - ALLOC
2 - CAT 12 - DEALLOC
3 - RENAME 13 - DMPDSCB
4 - SCRATCH/SCRATCHP 14 - LISTDIR
5 - UNC 15 - MAP
6 - BLDG 16 - SPACE
7 - DLTX 17 - DMPDSN
8 - CONN 18 - DMPCAT
9 - DCONN 19 - LOC
10 - FIND
A formatted function panel is returned for each function by entering the appropriate
FUNCTION value and pressing Enter. Details of those panels are given in the following
discussions.
PF Keys
Once a function has been selected on the menu and the function panel is displayed,
program function key 3, PF3 is temporarily set to return to the UT menu panel. In native
CA WA CA 7 Edition VTAM mode, any value that was previously assigned to PF3, by
either the user or CA WA CA 7 Edition, is temporarily ignored as long as the function
panel is being used and reverts back to the original 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+1 respectively
until PF3 is pressed or a top line command is issued.
Special considerations apply when using CA WA CA 7 Edition under TSO-ISPF.

■ PF key interrupts are not processed by CA WA CA 7 Edition, unless PASSTHRU is the
ISPF application command table value associated with the ISPF command that is
assigned to the PF key in question.
■ If PF3 is assigned the END command in ISPF, PF3 ends the CA WA CA 7 Edition
TSO-ISPF session unless END is assigned a value of PASSTHRU in the ISPF application
command table.

UT.1 - Allocate/Catalog Dataset Panel

The UT.1 panel allocates and optionally catalogs a DASD data set.
-------------------- CA-7 UTILITIES - ALLOCATE DATASET ----------------------

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 is returned.
To exit:
field.
■ Use a PF key.


FUNCTION
Used only to transfer to another menu or some other formatted panel function that
is only offered on another menu. Enter the name of the desired panel.
DSNAME
Fully qualified name of the data set to be allocated.
VOLSER
Defines a volume serial number on which the data set is to be allocated. The
volume must have been made available to CA WA CA 7 Edition with a U7volser type
of DD statement, (as discussed in the Systems Programming Guide), with a top line
ALLOC command or through function 11 of the UT Menu panel.
ALSO CATALOG
(Optional) Enter Y to also catalog the data set after it is allocated.
Default: N
SPACE ALLOCATION
Panel title line only.
TYPE
(Optional) Defines a type of allocation desired. C indicates allocation in units of
cylinders. T, the default, indicates allocation in units of tracks.
PRIMARY
Defines a primary space allocation amount.
SECONDARY
(Optional) Defines a secondary space allocation amount.
DIR BLOCKS
(Optional) Defines a number of directory blocks to be allocated for a PDS. Zero, the
default, indicates DSORG of PS. Nonzero indicates DSORG of PO.
Default: 0
DCB INFORMATION
Panel title line only.
RECFM
Record format. Format must be F, FB, V, VB, VBS, VS, U, FA, FBA, FM, FBM, VA, VBA,
VM, or VBM.

UT.2 - Catalog Dataset Panel
LRECL
(Optional) Logical record length.
BLKSIZE
Block size.
More information:
Usage Notes
Press Enter when the fields have been completed. The panel returns with the MESSAGE
field indicating what action was taken or any errors that occurred.

The UT.1 panel catalogs a data set.
--------------------- CA-7 UTILITIES - CATALOG DATASET -----------------------

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 is returned.
To exit:
field.
■ Use a PF key.

FUNCTION
DSNAME
Fully qualified name of the data set to be cataloged.
VOLSER 1
VOLSER 2
VOLSER 3
VOLSER 4
VOLSER 5
Up to 5 volumes on which the data set resides. At least one VOLSER is required.
UNIT NAME
Unit name of the type of device on which the data set resides. The unit name must
be defined in SASSUTBL. (For example, 3350, DISK, SYSDA.) This field must be
omitted if DEVICE field is used; otherwise, it is required.
DEVICE
Hexadecimal device code similar to those defined in SASSUTBL. This field must be
omitted if UNIT NAME field is used; otherwise, it is required.
FILE SEQ
(Optional) Label sequence number. If omitted, 0 (zero) is assumed for DASD and 1 is
assumed for tape data sets.
CVOL
(Optional) VOLSER containing the catalog. The default is SYSRES.

UT.3 - Rename Dataset Panel
More information:
Usage Notes

The UT.3 panel renames a DASD data set.
--------------------- CA-7 UTILITIES - RENAME DATASET -----------------------

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 is returned.

To exit:
field.
■ Use a PF key.

FUNCTION
DSNAME
Fully qualified name of the data set to be renamed. Required field.
VOLSER
Volume serial number on which the data set resides. Required if not cataloged. The
volume on which the data set resides must be available to CA WA CA 7 Edition
through U7volser DD statement, top line ALLOC command or function 11 on the UT
Menu panel.
NEW DSNAME
Fully qualified new name desired for the data set. Required field.
More information:
Usage Notes

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

The UT.4 panel scratches a DASD data set.
--------------------- CA-7 UTILITIES - SCRATCH DATASET -----------------------

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 panel is
returned.
To exit:
field.
■ Use a PF key.

FUNCTION
DSNAME
Fully qualified name of the data set to be scratched. Required field.

UT.5 - Uncatalog Dataset Panel
VOLSER
VOLSER on which the data set resides. Required if not cataloged. If omitted, data
set is uncataloged if the scratch is successful. The volume on which the data set
resides must be available to CA WA CA 7 Edition through U7volser DD statement,
top line ALLOC command, or function 11 on the UT Menu panel.
PURGE
Enter Y if data set is to be scratched even though the expiration date has not been
reached. Optional. Default is to scratch only if the expiration date has been
reached.
More information:
Usage Notes

The UT.5 panel uncatalogs a data set.
-------------------- CA-7 UTILITIES - UNCATALOG DATASET ----------------------

DSNAME:
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 is returned.
To exit:
field.
■ Use a PF key.

FUNCTION
DSNAME
Fully qualified data set name or name and relative GDG of the data set to be
uncataloged. Required field. If relative GDG, the index is also deleted if it is no
longer needed for other versions of the data set.
CVOL
(Optional) VOLSER containing the catalog. The default is SYSRES.
More information:
Usage Notes

UT.6 - Build GDG Index Panel
UT.6 - Build GDG Index Panel

The UT.6 panel builds an index for a generation data group (GDG).
--------------------- CA-7 UTILITIES - BUILD GDG INDEX ----------------------

INDEX:
(REQUIRED, FULL INDEX NAME)
NUMBER OF
ENTRIES: (CATALOG ENTRIES, REQUIRED, UP TO 3 DIGITS, MAX 255)
DELETE
WHEN 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 is returned.
To exit:
field.
■ Use a PF key.

FUNCTION
INDEX
Name of the GDG index. Required field.

UT.7 - Delete Index Panel
NUMBER OF ENTRIES
Number of entries to be kept in the GDG index. Required field. Numeric with
maximum of 255.
DELETE WHEN FULL
Action to be taken once ENTRIES value is exceeded. Enter A to delete all entries.
Default is to delete only the oldest entry.
More information:
Usage Notes
This panel does not support VSAM or ICF catalogs because the IEHPROGM-type function
uses an older form of catalog interface. Only CVOL catalogs are supported at this time.

The UT.7 panel deletes inactive indexes from the catalog.
---------------------- CA-7 UTILITIES - DELETE INDEX ------------------------

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 is returned.
To exit:
field.
■ Use a PF key.

FUNCTION
INDEX
Fully qualified name of the index to be deleted. Required field.
CVOL
VOLSER of the catalog. If omitted, a standard catalog search, beginning with SYSRES,
is employed.
More information:
Usage Notes

UT.8 - Connect a Catalog Panel

The UT.8 panel connects high-level indexes from the SYSRES catalog to another catalog.
-------------------- CA-7 UTILITIES - CONNECT A CATALOG ---------------------

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 is returned.
To exit:
field.
■ Use a PF key.


FUNCTION
INDEX
High-level index name to be connected to SYSRES. Required.
VOLSER
VOLSER of the connected volume. Connected volume must be available to CA WA
CA 7 Edition through U7volser DD statement, top line ALLOC command or function
11 on the UT Menu panel. Required.
More information:
Usage Notes

UT.9 - Disconnect a Catalog Panel
UT.9 - Disconnect a Catalog Panel

The UT.8 panel disconnects high-level indexes from the SYSRES catalog.
------------------ CA-7 UTILITIES - DISCONNECT A CATALOG --------------------

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 is returned.
To exit:
field.
■ Use a PF key.

FUNCTION
INDEX
High-level index name to be disconnected from SYSRES. Required.

UT.10 - Find DSN on DASD Panel
More information:
Usage Notes

The UT.10 panel searches DASD volumes for copies of a given data set.
-------------------- CA-7 UTILITIES - FIND DSN ON DASD -----------------------

DSNAME:
VOL1: VOL2: VOL3: VOL4: VOL5:

('ALL' = ALL AVAILABLE VOLUMES; REQUIRED)
PROGRAM: UTFL MSG-INDX: -- UT.10 -- YY.DDD / HH:MM:SS

MESSAGE:
To display, enter:
■ If an error is encountered with a top line FIND command, this panel is returned.

To exit:
field.
■ Use a PF key.

FUNCTION
DSNAME
Fully qualified name of the data set. Required field.
VOL1
VOL2
VOL3
VOL4
VOL5
Volume serial numbers that are to be searched for the data set. Enter ALL for VOL1
to search all volumes. Each volume searched must be available to CA WA CA 7
Edition through a U7volser DD statement, top line ALLOC command or function 11
on the UT Menu panel. Required.
More information:
Usage Notes
Up to 40 occurrences of the data set are shown in the body of the panel in
VOLSER/YY.DDD format. The YY.DDD indicates the Julian date the data set was 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 as a top line FIND
command. A different display is returned listing each occurrence.

UT.11 - Allocate Volume Panel

The UT.11 panel allocates a DASD volume not defined by a U7xxxxxx DD statement in
the CA WA CA 7 Edition JCL.
-------------------- CA-7 UTILITIES - ALLOCATE VOLUME ------------------------

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 is returned.
To exit:
field.
■ Use a PF key.


FUNCTION
VOLSER
Volume serial number. Required field.
UNIT NAME
Unit name of the DASD device on which the volume resides. Similar to the generic
equivalent of a device code in the SASSUTBL table. For example, 3390 or SYSDA.
Required field.
More information:
Usage Notes

UT.12 - Deallocate Volume Panel
UT.12 - Deallocate Volume Panel

The UT.12 panel deallocates a DASD volume previously allocated with function 11 on
the UT Menu panel or with a top line ALLOC command.
-------------------- CA-7 UTILITIES - DEALLOCATE VOLUME ---------------------

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 is returned.
To exit:
field.
■ Use a PF key.

FUNCTION
VOLSER
Volume serial number. Required field.

UT.13 - Display Format 1 DSCB Panel
More information:
Usage Notes

The UT.13 panel displays the Format 1 data set control block (DSCB) for a given data set.
------------------ CA-7 UTILITIES - DISPLAY FORMAT 1 DSCB --------------------

DSNAME:
(REQUIRED)
PROGRAM: UTFJ 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 is
returned.

To exit:
field.
■ Use a PF key.

FUNCTION
DSNAME
VOLSER
Volume serial number on which the data set resides. Required if not cataloged.
More information:
Usage Notes
field indicating what action was taken or any errors that occurred. If found, the DSCB is
displayed in the body of the panel in hexadecimal and character dump format.

Examples
The following display shows the VOLSER value even if it was not entered originally.
Below the two heading lines, the 101 bytes beginning at offset hex '2C' in the DSCB are
shown in both hexadecimal and character form. The PROGRAM value at the bottom of
the panel indicates UTL1 because that module accessed and formatted the DSCB
information.
------------------ CA-7 UTILITIES - DISPLAY FORMAT 1 DSCB --------------------

DSNAME: SYS2.PROCLIB
(REQUIRED)
VOLSER: 123456 (REQUIRED IF NOT CATALOGED)
DATASET CONTROL BLOCK INFORMATION:

OFFSET -------------- H E X -------------- --- CHARACTER ----
00002C F1000004 5900A500 01560144 00000001 *1...............*
00003C 0000E2E3 D6C2C9F0 F140FF91 40164D5A *..STOBI01 .. ...*
00004C 00021100 54460200 90000C30 00500000 *................*
00005C 0080C000 0000007E 06888000 00810001 *................*
00006C 91000001 9A000E00 00000000 00000000 *................*
00007C 00000000 00000000 00000000 00000000 *................*
00008C 00000002 01 *..... *
PROGRAM: UTL1 MSG-INDX: -- UT.13 -- YY.DDD / HH:MM:SS

MESSAGE:

UT.14 - Display Directory Info Panel
UT.14 - Display Directory Info Panel

The UT.14 panel displays information from a PDS directory block.
----------------- CA-7 UTILITIES - DISPLAY DIRECTORY INFO --------------------

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 is returned.
To exit:
field.
■ Use a PF key.

FUNCTION
DSNAME

UT.15 - Display Dataset Attributes Map Panel
MEMBER
Member name with which to begin. If omitted, the entire directory is listed.
VOLSER
More information:
Usage Notes
If no errors occur, a different display is returned showing the desired information.

The UT.15 panel displays attributes of a DASD data set.
------------- CA-7 UTILITIES - DISPLAY DATASET ATTRIBUTES MAP ---------------

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 is returned.
To exit:
field.
■ Use a PF key.

FUNCTION
DSNAME
Fully 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 asterisk after the last
significant character in the name. VOLSER is also required for a generic request.
Required.
VOLSER
Volume serial number containing the data sets. Required for generic data set names
or if not cataloged.
LIST
Enter A to list all information.
The following are default lists:
■ Data set name
■ Number of extents
■ Tracks allocated
■ Tracks used
■ Secondary allocation quantity
■ DSORG
■ RECFM
■ LRECL
■ BLKSIZE

The value of A also lists the following:

■ Creation date
■ Expiration date
■ Absolute DASD address
■ Type of allocation
■ Option code (OPTCD)
■ Key length
■ Key position
■ Password indicators
■ Unmovable indicators
More information:
Usage Notes

UT.16 - Display Available DASD Space Panel

The UT.16 panel displays available space information for volumes available to CA WA CA
7 Edition.
-------------- CA-7 UTILITIES - DISPLAY AVAILABLE DASD SPACE -----------------

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 is returned.
To exit:
field.
■ Use a PF key.


FUNCTION
VOL1
VOL2
VOL3
VOL4
VOL5
Volume serial numbers for which available space is to be listed. Enter ALL for VOL1
to search all volumes. Each volume searched must be available to CA WA CA 7
Edition through a U7volser DD statement, top line ALLOC command or function 11
on the UT Menu panel. Required.
More information:
Usage Notes

UT.17 - Display Physical Data Records Panel

The UT.17 panel displays physical records from a given data set or a PDS directory.
-------------- CA-7 UTILITIES - DISPLAY PHYSICAL DATA RECORDS ---------------

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 is returned.
To exit:
field.
■ Use a PF key.

FUNCTION
DSNAME

MEMBER
Name of a PDS member to be listed. Only valid for PDS. If omitted for a PDS, the
directory is displayed.
VOLSER
RELATIVE RECORD NUMBER
Relative record to be displayed. Default is 1 to indicate the first record in the data
set. Can be incremented on subsequent displays to progress through a complete
data set.
More information:
Usage Notes

UT.18 - Display Catalog Block Panel

The UT.18 panel displays the first catalog block for a given data set.
------------------ CA-7 UTILITIES - DISPLAY CATALOG BLOCK --------------------

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 is returned.
To exit:
field.
■ Use a PF key.


FUNCTION
DSNAME
Fully qualified name of the data set.
CVOL
VOLSER of the catalog. Default is SYSRES.
More information:
Usage Notes

UT.19 - Display Catalog Entries Panel
UT.19 - Display Catalog Entries Panel

The UT.19 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 is returned.
To exit:
field.
■ Use a PF key.

VERIFY Command

FUNCTION
DSNAME
Fully qualified name of a data set, a generic data set or a relative GDG. A generic
request is specified by the desired index levels followed by a period. Required.
CVOL
If high-level node is defined in the master catalog, this field should be omitted.
Otherwise, use the volume serial number of the desired catalog.
More information:
Usage Notes
A generic request for data sets whose catalog entries are in the master catalog receive
the message that the data set is not found. This is a restriction of SVC 26, which is used
to process this command.
VERIFY Command
The VERIFY command establishes or satisfies a manual verification requirement for a
currently scheduled run of the job in the request queue before its execution. A
verification requirement is established for the currently scheduled run to help ensure
completion of some unusual activity before job submission. Under ordinary
circumstances, the database maintenance job definition panel 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 following panels:

■ QM.1 CPU Jobs Status Prompt panel
■ QM.2 CPU Job Predecessors Prompt panel
■ QM.3 CPU Job Attributes Prompt panel

XPOST Command
VERIFY,JOB=jobnumber,SET={ON|OFF}
JOB
Specifies the CA WA CA 7 Edition assigned job number of the job for which a
verification requirement is established or satisfied.
SET
Sets the verification requirement.
ON
Establishes a manual verification requirement that did not previously exist.
OFF
Indicates that a previously established manual verification requirement is
satisfied and can be removed. A verification requirement no longer appears on
the requirements list in the request queue.
Examples
VERIFY,JOB=163,SET=ON
VERIFY,JOB=163,SET=OFF
XPOST Command
The XPOST top line command returns a panel that lists output network entries from the
postprocess queue. The panel that is returned allows you to update the panel
information. Perform logging in by entering a function code for the appropriate panel
entry and pressing Enter. Also, the XSPOST command displays the same (but
abbreviated) information in a two-up format.
This function is available through the QM.7 Output Networks Prompt panel.
{XPOST|XSPOST}[,FILL=function]
[,JOB={*|jobname|jobname*|jobnumber}]
[,STN={*|station|station*}]
[,SUBID={*|subid|subid*}]

XPOST Command
XPOST
Lists output workstation network entries.
XSPOST
Same as XPOST, but abbreviates and lists twice as many entries on the panel.
FILL
Identifies a character to insert in the function field that precedes each entry on the
formatted panel when the panel is initially formatted for display. This value
facilitates performing the same function for many networks. For more information
about the available values and how they are used, see the QM.7 Output Networks
Prompt panel.
JOB
(Optional) Indicates the jobs for which the list of postprocess queue records is
desired. Up to 17 entries are listed per panel for the XPOST command.
*
Indicates all job names. This value is the default.
jobname
jobname*
Indicates a generic job name.
jobnumber
Indicates a specific CA 7 job number or a range of job numbers that are
specified as nnnn-nnnn.

XPOST Command
NW
(Optional) Identifies the networks for which to list records.
*
Indicates all networks. This value is the default.
network
Indicates a specific network name.
network*
Indicates a generic type request.
STN
(Optional) Identifies the stations for which to list records. The default is all logical
terminal names that are connected to the physical terminal that issued the request.
For example, logical terminals BALANCE and DECOLLAT are assigned to physical
terminal HTERM1. If XPOST was entered from HTERM1, all postprocess queue
records for stations BALANCE and DECOLLAT would be displayed.
*
Indicates all logical terminal names that are connected to the physical terminal
where the XPOST command is entered. This value is the default.
station
Indicates a specific station name.
station*
SUBID
(Optional) Identifies the sub-IDs for which to list records.
*
Indicates all sub-IDs. This value is the default.
subid
Indicates a specific sub-ID.
subid*

XPRE Command
More information:
XSPOST Command (see page 719)

QM.7 Output Networks Prompt Panel (see page 610)
Usage Notes
Entries are not displayed if the previous station has not logged out or the work for this
station is complete.
The display continues to reflect the queue entries at the time of the initial request. It
may be necessary to reissue the original request to get an updated display.
Examples
XPOST,STN=*
XSPOST,JOB=DUSAX*
XPOST,JOB=DUSAMRUN,FILL=I
XPRE Command
The XPRE top line command returns a panel that lists Input Network entries from the
preprocess queue and allow the user to update that network information. Logging in or
logging out can be performed by entering a function code for the appropriate panel
entry and pressing Enter. This command can also be used for prompting workstations
and interrupting and resuming a network. Also, the XSPRE command displays the same
(but abbreviated) information in a two-up format.
This function is available through the QM.6 Input Networks Prompt panel.
{XPRE|XSPRE}[,FILL=function]
[,JOB={*|jobname|jobname*|jobnumber}]
[,STN={*|station|station*}]
[,SUBID={*|subid|subid*}]

XPRE Command
XPRE
Lists input workstation network entries.
XSPRE
Same as XPRE, but abbreviates and lists twice as many entries on the panel.
FILL
(Optional) Identifies a character to insert in the function field that precedes each
entry on the formatted panel when the panel is initially formatted for display. This
value facilitates performing the same function for many networks. For more
information about the available values for FILL and how they are used, see the
QM.6 Input Networks Prompt panel.
JOB
(Optional) Indicates the jobs for which the list of preprocess queue records is
desired. Up to 17 entries are listed per panel for the XPRE panel.
*
Indicates all job names in the preprocess queue. This value is the default.
jobname
jobname*
Indicates a generic job name.
jobnumber
Indicates a specific CA 7 job number or a range of job numbers that are
specified as nnnn-nnnn.

XPRE Command
NW
(Optional) Identifies the networks for which to list records.
*
Indicates all networks. This value is the default.
network
Indicates a specific network name.
network*
STN
(Optional) Identifies the stations for which to list records. The default is all logical
terminal names that are connected to the physical terminal that issued the request.
For example, logical terminals KEYPUNCH and VERIFY are assigned to physical
terminal HTERM1. If XPRE was entered from HTERM1, all preprocess queue records
for stations KEYPUNCH and VERIFY would be displayed.
*
Indicates all logical terminal names. This value is the default.
station
Indicates a specific station name.
station*
SUBID
(Optional) Identifies the sub-IDs for which to list records.
*
Indicates all sub-IDs. This value is the default.
subid
Indicates a specific sub-ID.
subid*

XQ, XQJ, XQN, and XQM Commands
More information:
QM.6 Input Networks Prompt Panel (see page 603)
Usage Notes
Entries are not displayed if the previous station has not logged out or the work for this
station is complete.
The display continues to reflect the queue entries at the time of the initial request. It
may be necessary to reissue the original request to get an updated display.
Examples
XPRE,NW=KEYP*,FILL=C
XSPRE,JOB=TEST*

The XQ, XQJ, XQN, and XQM commands result in the display of jobs in the request,
ready or active queues and lets you update the status of those jobs. 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 single function character. You
can also transfer from any of these panels to the XRST panel when a job requires a
restart. These commands are valid only from online 3270 type terminals. Each command
provides a different display sequence as follows:
XQ
Lists the jobs in the order in which they occur in the queue.
XQJ
Lists the jobs in a job name sequence.

XQN
Lists the jobs in a CA 7 job number sequence.
XQM
Lists the jobs in a job name sequence with a requirements summary. LIST=ANY is
the default for XQM. This value is different from the other XQ panels where
LIST=ALL is the default.
Some requirements can be satisfied directly on these panels. Control can also be passed
to other panels such as XRQ and XUPD, from which control functions can be performed.
This function is available through the QM.1 CPU Jobs Status Prompt panel.
{XQ|XQJ|XQN|XQM}[,FILL=function]
[,LIST=options]
[,Q={REQ|RDY|ACT}]
[,SEQ={ENTRY|NUMBER|JOBNAME}]
XQ
XQJ
XQN
Lists the jobs in a job number sequence.
XQM
Lists the jobs in a job name sequence with a requirements summary.
FILL
(Optional) Identifies the character to insert in the function fields when the
formatted panel is initially displayed. This option facilitates performing the same
function for many jobs. For more information about the available values for FILL
and how they are used, see the QM.1 CPU Jobs Status Prompt Panel.

JOB
(Optional) Indicates the jobs for which you want to list information from the
request, ready, and active queues. JOB and JOBL are mutually exclusive.
*
Indicates all jobs. This value is the default.
jobname
jobnumber
Indicates a specific job number or a range of job numbers that are specified as
nnnn-nnnn.
mask
Specifies all job names matching the mask pattern.
JOBL
(Optional) Indicates the jobs for which you want to list information from the
request, ready, and active queues.
*
Indicates all jobs.
longjobname
mask
Specifies all long job names matching the mask pattern.
Note: Listing by job name using the JOBL keyword returns and displays the regular,
eight-character job names in alphabetic order of the long job name. This process
sometimes causes the listed job names to appear as out of order.
LIST
(Optional) Specifies the outstanding requirements selection criteria.
ALL
List all jobs regardless of outstanding requirements. This value is the default for
XQ, XQJ, and XQN.
ANY
List only those jobs with at least one requirement. This value is the default for
XQM.

BINT
List only those jobs that have internal data set requirements, but no unsatisfied
job requirements.
EXT
List only those jobs with external data set requirements.
HLD
List only those jobs with a hold requirement.
INT
List only those jobs with internal data set requirements.
JCLO
List only those jobs with a JCL override requirement.
JOB
List only those jobs with job requirements.
NWK
List only those jobs with network requirements.
REST
List only those jobs in restart status.
SKEL
List only those jobs in skeleton status.
SUB
List only those jobs with submit-time requirements.
USR
List only those jobs with user requirements.
VER
List only those jobs with a verify requirement.
Q
(Optional) Identifies the queue for which to list jobs.
REQ
Specifies the request queue. This value is the default.
ACT
Specifies the active queue.
RDY
Specifies the ready queue.

SEQ
(Optional) Indicates the sequence in which to list the jobs. You can use this option
to change the default sequence for the XQM command (default is the job name
sequence).
ENTRY
JOBNAME
NUMBER
Lists the jobs in a CA 7 job number sequence.
SYS
(Optional) Specifies to list jobs that are associated to a system.
*
Indicates all jobs regardless of the system name. This value is the default.
system
Indicates only list jobs having this system name.
mask
Indicates only list jobs whose system matches the mask pattern entered.
More information:

QM.1 CPU Jobs Status Prompt Panel (see page 573)
Usage Notes
The XQ, XQJ, and XQN commands result in the QM.1-X panel display with the job name
and CA 7 job number listed for each job.
The XQM command results in the QM.1-M panel display with the job name and a
summary of the outstanding requirements for each job.
More information:
QM.1-X CPU Jobs Status Panel (see page 577)

QM.1-M CPU Job Requirements (see page 579)

XRQ Command
Examples
XQ
XQ,JOB=DUSA*
XQJ
XQJ,Q=ACT
XQN
XQN,JOB=12-17,FILL=C
XQM,LIST=INT
XRQ Command
The XRQ command displays the requirements of a job in the request queue for possible
updating. This command is valid online only. The job requirements that have 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 the QM.2 CPU Job Predecessors Prompt panel.
XRQ,{JOB={jobname|jobnumber}|JOBL=longjobname}[,LIST=ALL]
JOB
Identifies a request queue job for which to list requirements. JOB and JOBL are
mutually exclusive.
jobname
Specifies a specific job name.
jobnumber
Specifies a CA 7 job number.

XRST Command
JOBL
Identifies a request queue job for which you want to list requirements. JOB and
longjobname
LIST
(Optional) If specified, all requirements are listed. An X prefixes satisfied
requirements.
Default: List only requirements not satisfied
Examples
XRQ,JOB=DUSAXX01
XRQ,JOB=5,LIST=ALL
XRST Command
The XRST top line command displays the restart (QM.4) panel for a particular job. A job
must be in restart status to use this panel. The user can initially schedule a job for
restart processing using TYPE=RES on the DEMAND command.
The QM.4 panel can also be accessed from the XQ, XQJ, XQN, or XQM panel.
This function is available through the QM.4 CPU Job in the Restart Status Prompt panel
where the available functions are discussed.
XRST,JOB={jobname|jobnumber}
JOB
Identifies the job to display.
jobname
jobnumber

XSPRE Command
More information:
QM.4 CPU Job In Restart Status Prompt Panel (see page 597)
XSPOST Command
The XSPOST command has the same function as the QM.7 panel and the XPOST
command. However, it lists up to 34 postprocess queue entries per panel in "2-up"
format.
More information:
QM.7 Output Networks Prompt Panel (see page 610)
XSPRE Command
The XSPRE command has the same function as the QM.6 panel and the XPRE command.
However, it lists up to 34 preprocess queue entries per panel in "2-up" format.
More information:
QM.6 Input Networks Prompt Panel (see page 603)

XPRE Command (see page 709)
XUPD Command
The XUPD command displays job type queue records for jobs in the request queue. This
command is valid only from an online 3270 type terminal. You can modify any of the job
characteristics appearing on the panel by positioning the cursor at the appropriate field
and entering a new value. Updates are for one run only. They do not change
information in the CA WA CA 7 Edition database. The characteristics that are displayed
can be reviewed, permanently changed, or both, with the DB.1 panel.
This function is available through the QM.3 CPU Job Attributes Prompt panel.
XUPD,{JOB={jobname|jobnumber}|JOBL=longjobname}

XUPD Command
JOB
Identifies a request queue job for which to list requirements. JOB and JOBL are
mutually exclusive.
jobname
jobnumber
JOBL
Identifies a request queue job for which you want to list requirements. JOB and
longjobname
Usage Notes
After the XUPD command is entered, a panel is returned showing the current values for
the job requested.
More information:
QM.3 CPU Job Attributes Prompt Panel (see page 587)
Examples
XUPD,JOB=DUSAXX01
XUPD,JOB=12

XWLB Command
XWLB Command
The XWLB command, included in the workload balancing facility, makes temporary
changes in selection parameters. You can view existing workload balancing values with
the LWLB panel.
XWLB
The XWLB command has no keywords.
A formatted panel results from this command, displaying the current parameters.
Position the cursor to the desired field to make changes. These changes are only
temporary. They remain in effect until either another load module is called or they are
changed again using this panel. Any permanent changes to selection parameters require
a regeneration of the macros.
The XWLB display differs based on whether the enhanced submission selection
(SUBSEL=ENH) is active.
XWLB Panel (Defaults) Without Enhanced Submission Selection
XWLB
MOD: UCC7RDFL --CLASS BAR AND USE--
CL BAR USE CL BAR USE
----- INITIATORS ----- --------- TAPE DRIVES -------- A: 255 000 S: 255 000
TOT JOBS SUBMITTED 000 NAME: TAPEDR1 TAPEDR2 B: 255 000 T: 255 000
TOT JOBS ACTIVE... 000 CURR IN-USE...... 000 000 C: 255 000 U: 255 000
TOT INITS AVAL.... 010 TOTAL AVAILABLE.. 010 010 D: 255 000 V: 255 000
MIN JOBS MUST RUN. 255 MAX REWARD....... 020 020 E: 255 000 W: 255 000
MAX PENALTY...... 020 020 F: 255 000 X: 255 000
--------- CPU -------- MIN DIFF-TO-SCHED 000 000 G: 255 000 Y: 255 000
CURR %UTL/JOB 000.000 MAX DIFF-TO-SCHED 000 000 H: 255 000 Z: 255 000
IDEAL %UTL/JOB 008 MAX BOOST FOR DTS 000 000 I: 255 000 0: 255 000
MAX REWARD........ 020 MIN ALLOWABLE/JOB 000 000 J: 255 000 1: 255 000
MAX PENALTY....... 020 MAN ALLOWABLE/JOB 255 255 K: 255 000 2: 255 000
TOT MAX ALLOWABLE 012 012 L: 255 000 3: 255 000
----- START TIME ----- M: 255 000 4: 255 000
MAX REWARD........ 020 ----- THRESHOLD PRIORITY ----- N: 255 000 5: 255 000
MAX PENALTY....... 020 DEFAULT THRESHOLD JOB PRTY 100 O: 255 000 6: 255 000
MAX LATE (HRS).... 012 SPECIAL CLASS #1 CL PRT P: 255 000 7: 255 000
MAX EARLY(HRS).... 012 SPECIAL CLASS #2 CL PRT Q: 255 000 8: 255 000
RUN TIME FACTOR... 010 SPECIAL CLASS #3 CL PRT R: 255 000 9: 255 000
PROGRAM: QM60 MSG-INDEX: 00 -- WB.X -- yy.003 / 16:26:14
MESSAGE: CHANGE VALUES OR ENTER A COMMAND ON THE TOP LINE

XWLB Command
XWLB Panel (Defaults) With Enhanced Submission Selection
XWLB
MOD: UCC7RDFL --CLASS BAR AND USE--
CL BAR USE CL BAR USE
----- INITIATORS ----- --------- TAPE DRIVES -------- A: 255 000 S: 255 000
TOT JOBS SUBMITTED 000 NAME: TAPEDR1 TAPEDR2 B: 255 000 T: 255 000
TOT JOBS ACTIVE... 000 CURR IN-USE...... 000 000 C: 255 000 U: 255 000
TOT INITS AVAL.... 010 TOTAL AVAILABLE.. 010 010 D: 255 000 V: 255 000
E: 255 000 W: 255 000
F: 255 000 X: 255 000
G: 255 000 Y: 255 000
H: 255 000 Z: 255 000
I: 255 000 0: 255 000
J: 255 000 1: 255 000
K: 255 000 2: 255 000
L: 255 000 3: 255 000
M: 255 000 4: 255 000
N: 255 000 5: 255 000
O: 255 000 6: 255 000
P: 255 000 7: 255 000
Q: 255 000 8: 255 000
R: 255 000 9: 255 000
PROGRAM: QM60 MSG-INDEX: 00 -- WB.X -- yy.102 / 15:12:06
MESSAGE: CHANGE VALUES OR ENTER A COMMAND ON THE TOP LINE
The panels contain the following fields:

MOD
Displays the load module (definition) name. If changes have been made after the
module is loaded it displays a message, CHANGED SINCE LOADED, after the module
name. No input is allowed for this field.
INITIATORS
Indicates that the lines following this contain information about the initiators. No
input is allowed for this field.
TOT JOBS SUBMITTED
Identifies the total jobs that are submitted to the CPU then. For information only
and no input is allowed. Always the same as TOT JOBS ACTIVE.

XWLB Command
TOT JOBS ACTIVE

Identifies the total jobs running on the CPU. For information only and no input is
allowed. Always the same as TOT JOBS SUBMITTED.
TOT INITS AVAL
Identifies the total initiators available for CA WA CA 7 Edition to submit jobs. This
value corresponds to the TOTAV specification on the INITR macro. Value must be
numeric and from 0 through 255. (See IDEAL %UTL/JOB.) A value of 255 indicates
no limit.
MIN JOBS MUST RUN
Identifies the minimum number of jobs that CA WA CA 7 Edition submits without
examining the threshold priority. This value corresponds to the MNJOB specification
on the INITR macro. Must be numeric and from 0 through 255.
CPU
Indicates that the lines following this contain information about CPU use. No input
is allowed for this field.
CURR %UTL/JOB
Identifies the current percent of CPU use per job. For information only and no input
is allowed.
IDEAL %UTL/JOB
Identifies the ideal percent of CPU use per job. Must be numeric and from 0
through 10. The product of this value and the TOT INITS AVAL value must not be
greater than 100. Corresponds to IDLUT specification on the CPU macro.
MAX REWARD
Identifies the maximum reward for CPU use. Corresponds to MXREW on the CPU
macro. Must be numeric and from 0 through 255.
MAX PENALTY
Indicates the maximum penalty for CPU use. Corresponds to MXPEN on the CPU
START TIME
Indicates that the following lines contain information about the start time. No input
is allowed for this field.

XWLB Command
MAX REWARD
Indicates the maximum reward for being late. Must be numeric and from 0 through
255. Corresponds to MXREW on the STARTIME macro.
MAX PENALTY
Indicates the maximum penalty for being early. Corresponds to MXPEN on the
STARTIME macro. Must be numeric and from 0 through 255.
MAX LATE (HRS)
Indicates the number of hours the job has to be late to gain the maximum reward.
Corresponds to MXLAT on the STARTIME macro. Must be numeric and from 0
through 255.
MAX EARLY (HRS)
Indicates the number of hours the job has to be early to gain the maximum penalty.
Corresponds to MXERL on the STARTIME macro. Must be numeric and from 0
through 255.
RUN TIME FACTOR
Indicates the value of the factor to apply to the runtime of the job to determine
whether to consider the job late or early. Corresponds to RUNTF on the STARTIME
TAPE DRIVES
Indicates the lines following this contain information about TYPE1 and TYPE2 of
tape drives. The first value is for TYPE1 and the second for TYPE2. The input fields
under this heading relate to the specifications for the TAPE1 and TAPE2 macros. No
input is allowed for this field.
NAME
Indicates the names of the two types of tape drives. Corresponds to NAME
specification. Must be alphanumeric, up to 8 characters.
CURR IN-USE
Indicates the number of tape drives in use. This value is for information only and no
input is allowed.
TOTAL AVAILABLE
Indicates the actual number of tape drives available to CA WA CA 7 Edition
controlled jobs. Corresponds to TOTAV. Must be numeric and from 0 through 255.

XWLB Command
MAX REWARD
Indicates the maximum reward for tape drive use. Corresponds to MXREW. Must be
numeric and from 0 through 255.
MAX PENALTY
Indicates the maximum penalty for drive use. Corresponds to MXPEN. Must be
numeric and from 0 through 255.
MIN DIFF-TO-SCHED
Indicates the minimum number of tape drives considered difficult to schedule.
Corresponds to MNDTS. Must be numeric and from 0 through 255.
MAX DIFF-TO-SCHED
Indicates the maximum number of tape drives considered difficult to schedule.
Corresponds to MXDTS. Must be numeric and from 0 through 255.
MAX BOOST FOR DTS
Indicates the maximum boost (additional reward) for difficult to schedule number
of tape drives. Corresponds to MXBST. Must be numeric and from 0 through 255.
MIN ALLOWABLE/JOB
Indicates the minimum number of tape drives a job must have for submission.
Corresponds to MNJAL. Must be numeric and from 0 through 255.
MAX ALLOWABLE/JOB
Indicates the maximum number of tape drives a job can have for submission.
Corresponds to MXJAL. Must be numeric and from 0 through 255.
TOT MAX ALLOWABLE
Indicates the number of tape drives CA WA CA 7 Edition is allowed to use for
scheduling jobs. Corresponds to MXTAL. Must be numeric and from 0 through 255.
THRESHOLD PRIORITY
Indicates the lines following this contain information about the threshold job
priority. No input is allowed for this field.
DEFAULT THRESHOLD JOB PRTY
Indicates the threshold job priority for all classes that are specified later.
Corresponds to JPTHR on the INITR macro. Must be numeric and from 0 through
255.
SPECIAL CLASS #1
Indicates that this line of the panel contains information about special class #1 and
corresponds to the SPCLS1 macro specification. No input is allowed for this field.
SPECIAL CLASS # 2

XWLB Command
SPECIAL CLASS # 3
CL
Indicates the special class name. Must be a 1 character, alphanumeric value.
PRT
Indicates the threshold job priority for the special class. Must be numeric and from
0 through 255.
CLASS BAR AND USE
A title line. No input is allowed for this field.
CL BAR USE
A title line. No input is allowed for this field.
A
Indicates two values.
The first value indicates the number of jobs that can run simultaneously under class
A. This value corresponds to the BARA specification for the CLBARR macro. This
value can be changed on the panel. Value must be from 0 through 255. A value of
255 indicates no limit.
The second value is the number of jobs currently running in this class. You cannot
change this value.
B thru Z and 0 thru 9
Same as the preceding except for classes B through 9.

CA Workload Automation CA 7® Edition: Command Reference Guide

Uploaded by

Copyright:

Available Formats

CA Workload Automation CA 7® Edition: Command Reference Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CA Workload Automation CA 7® Edition: Command Reference Guide

Uploaded by

Copyright:

Available Formats

CA Workload Automation

Command Reference Guide

Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you

To provide feedback about CA Technologies product documentation, complete our

8 Command Reference Guide

10 Command Reference Guide

12 Command Reference Guide

14 Command Reference Guide

16 Command Reference Guide

18 Command Reference Guide

20 Command Reference Guide

This section contains the following topics:

An asterisk matches any number of characters, including zero characters. A question

22 Command Reference Guide

Mask Strings that match Strings that do not match

Long Online Commands

24 Command Reference Guide

The CCC is not valid with the following commands:

The CCC is not available in a batch environment.

Note: For more information about continuation characters in a CAICCI terminal

Usage Notes (see page 107)

Enter the DEMAND command followed by the CCC.

The system returns the following screen.

Now, you can enter a long command.

Long Job Names

26 Command Reference Guide

Short Name Generation

Example: Job Brought into System and Assigned a Short Name

Long Name – FREDA11#ThisIsALongJobName

Example: Job with Eight or Less Characters

Long Name – MyJob1

Long Job Name Rules

General System Commands

Function Description Command

28 Command Reference Guide

General Inquiry Facility

Function Description Command

HELP tutorials List tutorials. HELP

Function Description Command

Data set Obtain information about LCTLG

30 Command Reference Guide

Function Description Command

Reminder Review free-form reminder LRMD

Job Flow Control

Function Description Command

32 Command Reference Guide

Function Description Command

Function Description Command

Workstation Network Control

Some examples of postprocessing tasks that are sometimes defined together as an

34 Command Reference Guide

Function Description Command

Function Description Command

Interrupting and If it is necessary to change the normal processing CANCEL

36 Command Reference Guide

Also, forecast can be used for the following:

A number of different commands are provided to generate specific forecast

38 Command Reference Guide

** JOB EXECUTION REQUIREMENTS *

** JOB PROSE DESC=THIS IS JOB INFORMATION FOR DUCCXX01