52500629 Jobtrac Reference Summ ENU

Unicenter® CA-Jobtrac™ Job Management

Reference Summary r11 SP1

Second Edition

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

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

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

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

EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS 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 THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE.

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

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.

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

Copyright © 2006 CA. All rights reserved.

CA Product References

This document references the following CA products:

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

■ Unicenter® AutoSys® Job Management (Unicenter AutoSys JM)

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

■ Unicenter® CA-MIM Resource Sharing (Unicenter CA-MIM)

■ Unicenter® CA-MII Data Sharing (Unicenter CA-MII)

■ Unicenter® CA-MIA Tape Sharing (Unicenter CA-MIA)

■ Unicenter® CA-MIA Message Sharing (Unicenter CA-MIC)

■ Unicenter® Network and Systems Management Job Management Option(Unicenter NSM JM Option)

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

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

■ Unicenter® CA-Spool™ Print Management (Unicenter CA-Spool)

■ Unicenter® Service Desk (Unicenter Service Desk)

■ Unicenter® CA-SYSVIEW® Realtime Perfomance Management (UnicenterCA-SYSVIEW)

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

■ Unicenter® CA-View® Output Archival and Viewing (Unicenter CA-View)

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

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

■ Advantage™ CA-Datacom®/DB Database (Advantage CA-Datacom/DB)

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

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

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

■ eTrust® CA-Examine™ Auditing (eTrust CA-Examine)

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

Contact Customer Support

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

3

4 Reference Summary

Contents

Chapter 1. Primary Commands . . . . . . . . . . . . . . . . . . . . . . . . . 9Prefix Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10A= Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11ADD Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

ADD parms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12ADDLOC= Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14ADR Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15AMR Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16ARG Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17AUDIT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18AUTH Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19B= Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20BROWSE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21BUSGRP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22CANCEL Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23CC Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24CCPF Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25CPM Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26D Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27D= Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28DATES Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30DATE= Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31DELETE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32DOC or DOCEDIT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . 33DSNQ= Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34DTFMT= Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35EDEP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36EDIT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37EMAIL Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38EMAILLST Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39ENDSAVE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40ENQ Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41ENQN= Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42EXCLUDE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43FIND Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44FORCE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45FSWAP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46GSO Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47HIST Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48HOMELOC= Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49I Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50IPLS Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51ISERVE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52J= Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53JCL Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Contents 5

JCLTRAC Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55JMF Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56JOBQ= Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57JTS Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58K= Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59L= Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61MACT or MANUAL Command . . . . . . . . . . . . . . . . . . . . . . . . . . 62MISSING Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63N= Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64O or OUT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65PARMS Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67PASSWORD Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68PP= Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69PROFILE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70PURGE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71RALL Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72RELEASE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73REMLOC= Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74RESET Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75RESOURCE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76RESV Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77RETRY Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78RSRC Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79RUN Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80S Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82SAR Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83SARDB Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84SAVE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85SCL Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86SCS Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87SHIFT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88SORT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89SPACE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90STATUS Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91SYS CYCS Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92SYS HOLS Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93SYS OPTS Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94SYS USER Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95T= Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96TEMP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97VER Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98VOLUME Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99WAIT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100XNODE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101? or ?EDIT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102@HOLD Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103@INT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104@REL Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105@RES Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

6 Reference Summary

Chapter 2. Line Commands . . . . . . . . . . . . . . . . . . . . . . . . . 107

Chapter 3. SCL (Schedule Control Language) . . . . . . . . . . . . . . 113Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Event Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Holiday Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Event Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Execution Dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Referback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Successor/Predecessor . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Process Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Conditional Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Predecessor Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Data Set Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Maximum Condition Code . . . . . . . . . . . . . . . . . . . . . . . . . 125Location ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Version Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Chapter 4. Process Period Keywords . . . . . . . . . . . . . . . . . . . 127Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Chapter 5. Cyclic Process Period Keywords . . . . . . . . . . . . . . . 135CYCDAY{>|<}nn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136CYCDAY#nnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137CYCDAYMnnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138CYCDAYXnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139CYCLAST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140CYCLEnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141dayCYC#{n|L} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142dayCYCMn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143WEEK#nn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144WEEKX{>|<}nn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145WEEKXnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146XdayCYC#{n|L} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Chapter 6. SCL Global Control Records . . . . . . . . . . . . . . . . . . 149+TODAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150@BUSGRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151@CYCnnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152@CYCnnn= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153@DATEFORM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154@EMAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155@FLOWnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156@HOLnnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157@HOLnnn= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158@INITIMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Contents 7

@PRIORITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160@REPORT= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161@RERUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162@SCHENV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163@SETLOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164@TODAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165@TRACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166@WDnnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167@WORKD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168UDEFn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Chapter 7. Dependency Code Descriptions . . . . . . . . . . . . . . . . 171

8 Reference Summary

Chapter 1. Primary Commands

The following chapter describes the top line (command line) Unicenter®

CA-Jobtrac™ Job Management (Unicenter CA-Jobtrac) commands available onvarious product panels.

Chapter 1. Primary Commands 9

Prefix Command

Prefix Command

The prefix command displays the Scheduled Event Display panel listing allevents beginning with prefix.

This command has the following format:

��─ ──prefix ───────────────────────────────────────────────────────────��

This command is used on the following panels:

■ CA-Jobtrac primary

■ Scheduled Event Display

■ Scheduled Event Network

■ Business Group Status

Example

This example displays all events whose names begin with TESTJ.

TESTJ

Note: All of the primary commands cannot be used as prefixes.

10 Reference Summary

A= Command

A= Command

The A= command displays the Scheduled Event Display panel listing all eventswith specified abend code or catalog checks.


��─ ──A= ──┬ ┬─abend─ ────────────────────────────────────────────────────�� ├ ┤─CC──── ├ ┤─CAT─── ├ ┤─S───── └ ┘─U─────






Examples

This example lists all events with abend code SD37.

A=SD37

This example lists all events with catalog checks.

A=CAT

This example lists all events with condition code checks.

A=CC

This example lists all events with system abends.

A=S

Lists all events with user abends.

A=U


ADD Command

ADD Command

The ADD command displays the Event/Jobstream Addition panel.


��─ ──┬ ┬─A─── ──────────────────────────────────────────────────────────�� └ ┘─ADD─






ADD parms

This command adds event named eventname to the current schedule andassigns manual release dependency (M), current time and date, maximumcondition code value 0000, and process period RQ-userid. If the event is aschedule or Unicenter CA-Jobtrac task, you must include the 0. Optionally,specify a version number (.vv) and/or location ID (,L=nnn).

Specify the event type by using the (,C) (,D) or (,E) options. The event typesare as follows:

,CIndicates that the named event defines a command to be executed at aparticular remote node.

,DIndicates that the named event is a dummy job.

,EIndicates the named event is a REXX IMOD.


ADD Command

Specify the GSS node name (up to 16 characters) of the executing node forthe named event with the ,N=nodename parameter. Depending on the type ofevent, use the REXX IMOD (,E event type), or to specify a command to beexecuted at a particular remote node (,C event type).


��──ADD─ ──┬ ┬───────────────── ──┬ ┬───── ──┬ ┬──────── ──┬ ┬────────── ───────� └ ┘── ──┬ ┬─eventname─ └ ┘──.vv └ ┘──,L=nnn └ ┘──, ──┬ ┬─C─

├ ┤──�sclname ─ ├ ┤─D─└ ┘──�tasknm ── └ ┘─E─

�─ ──┬ ┬───────────── ──┬ ┬────────────────────────────── ─────────────────��└ ┘──,N=nodename └ ┘──,A= ──┬ ┬─command─────────────

├ ┤─imod-arg──────────── └ ┘─shellscriptname.arg─






Examples

This example adds PRODJOB1 to current schedule.

ADD PRODJOB1

This example adds PRODJOB1 to current schedule with location ID 002.

ADD PRODJOB1,L=��2

This example adds Version 5 of PRODJOB1 to current schedule with locationID 002.

ADD PRODJOB1.�5,L=��2


ADDLOC= Command

ADDLOC= Command

The ADDLOC= command adds events (for viewing only) from location specifiedby nnn (any location ID 000-254) to the Scheduled Event Display panel. If thelocation is not defined in the user's TRACAUTH profile, added events can onlybe monitored. If you use the TRACX26 user exit, you cannot use ADDLOC=nnnto add events for viewing.


��─ ──ADDLOC=nnn ───────────────────────────────────────────────────────��






Example

This example adds events (for viewing only) from the location 029 to thedisplay.

ADDLOC=�29

Note: To remove events (for viewing only) from the display, use theREMLOC=029 command.


ADR Command

ADR Command

The ADR command displays the active ADR (Automatic Dataset Recognition)table.






■ Scheduled Event Detail

For editing the ADR tables, see “JTS Command” on page 58.


AMR Command

AMR Command

The AMR command displays the active AMR (Automatic Message Recognition)table.






For editing the AMR tables, see “JTS Command” on page 58.


ARG Command

ARG Command

The ARG command displays the argument to pass based on the event type.The argument is displayed in a pop-up panel.

The Edit Argument pop-up panel is displayed for editing purposes if the ARGcommand is issued from the Scheduled Event Detail panel.

The Argument pop-up panel is displayed for viewing only if the ARG commandis issued from the Event Execution Detail panel.



■ Event Execution Detail


AUDIT Command

AUDIT Command

The AUDIT command displays the Change Audit History panel for events. Thepanel displays information about changes made to an event.








■ Event History Detail

For more information, see “I Command” on page 50.


AUTH Command

AUTH Command

The AUTH command displays the user's location Authorization Profile panel. IfAUTH is entered with no parameter, the Authorization Profile for the userentering the command is displayed. If a user ID is included, the specified userprofile is displayed. If prefix* is specified, the profile displayed is for the group ofusers whose user IDs begin with prefix. If you use the TRACX26 user exit,AUTH has no effect.


��──AUTH─ ──┬ ┬──────────────── ─────────────────────────────────────────�� └ ┘──= ──┬ ┬─userid── └ ┘─prefix�─






■ Authorization Profile

Examples

This example displays the Authorization Profile panel for the user entering thecommand.

AUTH

This example displays the Authorization Profile panel for the user with IDTSOUSR.

AUTH=TSOUSR

This example displays the Authorization Profile panel for all users whose IDbegins with TSO.

AUTH=TSO�


B= Command

B= Command

The B= command displays a Scheduled Event Display panel listing events withthe business group name specified by bgname. Replace prefix with the first fewletters of the bgname of the events you want to display on the Scheduled EventDisplay panel.


��─ ──B= ──┬ ┬─bgname── ──────────────────────────────────────────────────�� └ ┘─prefix�─






Example

This example lists events assigned business group name ACCTING.

B=ACCTING

For more information, see “BUSGRP Command” on page 22.


BROWSE Command

BROWSE Command

The BROWSE command displays either the JCL or the SCL that will be usedfor the event. The JCL can be either temporary-use or production JCL. You canonly view the JCL or SCL, you cannot edit it with this command. Displays theIMOD Facility of CA-GSS (Global SubSystem) if the event is a REXX IMOD.






BUSGRP Command

BUSGRP Command

The BUSGRP command displays the Business Group Status panel. The paneldisplays information about each business group. You can select the busgrp andthen go to the Scheduled Event Display panel for those jobs in this busgrp.






For more information, see “B= Command” on page 20.


CANCEL Command

CANCEL Command

The CANCEL command exits from a panel and cancels any changes you havemade. Use this command to exit a panel without saving any changes you havemade.

This command is used on all edit or display panels.


CC Command

CC Command

The CC command displays the Step Condition Code Exceptions panel. TheStep Condition Code Exceptions panel is a pop-up panel that displays thecondition code parameters that have been defined for an event.






CCPF Command

CCPF Command

The CCPF command displays the active CCPF (Condition Code Program Filter)table.






For editing the CCPF tables, see “JTS Command” on page 58.


CPM Command

CPM Command

The CPM command displays the CA Critical Path Monitor panels.





D Command

D Command

The D command defines or executes the default command specified bycommand. The default command is executed automatically when UnicenterCA-Jobtrac is accessed or whenever D is entered.


��──D─ ──┬ ┬───────── ───────────────────────────────────────────────────�� ├ ┤─command─ └ ┘─OFF─────






Examples

This example defines the command K=LAW as the default command. K=LAWis executed automatically when Unicenter CA-Jobtrac is accessed or when D isentered.

D K=LAW

This example executes the default command. If no default command has beendefined, the RALL command is executed. The DEFAULT COMMANDparameter is located in the 'PROFILE' command display in the CA-Jobtrac UserProfile panel.

D

This example resets the default command.

D OFF


D= Command

D= Command

The D= command displays Scheduled Event Display panel listing all events withspecified dependency or dependencies.


��─ ──D= ──┬ ┬─A── ───────────────────────────────────────────────────────�� ├ ┤─D── ├ ┤─E── ├ ┤─H── ├ ┤─I── ├ ┤─J── ├ ┤─JW─ ├ ┤─M── ├ ┤─O── ├ ┤─P── ├ ┤─Q── ├ ┤─R── ├ ┤─T── ├ ┤─X── ├ ┤─?── └ ┘─�──

ADisplays events with the abend bypass dependency code.

DDisplays events with the data set required dependency code.

EDisplays events with the edit JCL dependency code.

IDisplays events with the environmental dependency code.

JDisplays events with the JCL required dependency code.

JWDisplays events with WLM resource dependency.

MDisplays events with the manual release dependency code.

ODisplays events with the output release dependency code.

PDisplays events with the predecessor event dependency code.

QDisplays events with the queued release dependency code.


D= Command

RDisplays events with the resource dependency code.

TDisplays events with time thresholds (the scheduled start time differs fromthe target time).

XDisplays events with the mutual exclusion dependency code.

?Displays events with the view documentation dependency code.

*Displays events submitted using AUTO-SCHD.






Examples

This example displays all events on the current schedule with the dependencycode E.

D=E

This example displays all events on the current schedule with dependencycodes D, P, and/or X.

D=DXP


DATES Command

DATES Command

The DATES command, depending on security authorization, edits the specifiedDATELIB member (the PRODDATE member is the default), which containsAutomatic Date Insertion rules. Optionally, you can add mbrname to display theDATELIB member specified by mbrname. Other members in the DATELIB dataset might be JMFSYM01 and EXCLPARM. If authorized, you can edit themember.


┌ ┐─PRODDATE─��──DATES─ ──┼ ┼────────── ──────────────────────────────────────────────�� ├ ┤─mbrname── ├ ┤─JMFSYM�1─ └ ┘─EXCLPARM─







DATE= Command

DATE= Command

The DATE= command defines the date parameter. Only events whose targetdate matches this parameter are displayed on the Scheduled Event Displaypanel. This parameter remains in effect until you change it or exit UnicenterCA-Jobtrac.


��─ ──DATE= ──┬ ┬─dd──────── ─────────────────────────────────────────────�� ├ ┤─mmdd────── ├ ┤─ddmm────── ├ ┤─mmdd-mmdd─ ├ ┤─ddmm-ddmm─ └ ┘─ALL───────






Examples

This example lists events with target dates on the fourth day of any month.

DATE=�4

This example lists events with target date of April 11 only.

DATE=�411

This example lists events with target dates from April 11 through April 15.

DATE=�411-�415


DELETE Command

DELETE Command

The DELETE command deletes the selected event awaiting submission. Theselected event is deleted from the current schedule and put on the historydatabase with the user ID of the user who deleted the event. If you haveUnicenter CA-11, this command automatically changes the Unicenter CA-11status of the event to PRODUCTION. Any predecessors or successors that arerelated to this event are not released from dependence on this event.





DOC or DOCEDIT Command

DOC or DOCEDIT Command

The DOC command displays documentation members for viewing.

The DOCEDIT command displays documentation members for editing.

If eventname is used, the specified event's documentation member is displayed.If * is used with a prefix (partial event name), a list is displayed listing all thedocumentation members whose names start with the prefix. Use * without aprefix to display a listing of all the documentation members. Select a name fromthe list. Optionally, you can specify a documentation library using the nnnparameter where nnn is the location ID. The location ID parameter (nnn) allowsyou to access multiple documentation libraries. Also see “? or ?EDITCommand” on page 102.

The commands have the following format:

┌ ┐─�─────────��─ ── ──┬ ┬─DOC───── ──┼ ┼─────────── ──┬ ┬───── ────────────────────────────�� └ ┘─DOCEDIT─ ├ ┤─eventname─ └ ┘──nnn └ ┘─prefix�───









■ NJE Execution Detail


DSNQ= Command

DSNQ= Command

The DSNQ= command displays enqueue research for the data set name ordata set name prefix specified by dsname. The resulting display lists all usersof the data set.


��─ ──DSNQ= ──┬ ┬─dsname─ ────────────────────────────────────────────────�� └ ┘─prefix─






■ Enqueue Research


DTFMT= Command

DTFMT= Command

The DTFMT= command changes the date format on Scheduled Event Displaypanels to American or International format. Specify A for a date in the format ofmm/dd. Specify I for a date in the format of dd/mm.


��─ ──DTFMT= ──┬ ┬─A─ ────────────────────────────────────────────────────�� └ ┘─I─






■ Cyclic Calendar

■ Holiday Calendar

This command updates your Unicenter CA-Jobtrac TSO profile.

Note: DTFMT affects only the Unicenter CA-Jobtrac-controlled dates. Thecurrent date in the panel header is controlled by TSO/ISPF and is not affectedby this parameter. Also see the SYS OPTS date format option.


EDEP Command

EDEP Command

The EDEP command displays the Environmental Dependencies panel for aspecific event that shows the environmental dependencies for an event.






EDIT Command

EDIT Command

The EDIT command edits JCL for the selected event or SCL for the selectedschedule. If authorized, you can edit the JCL or SCL. The JCL can be eithertemporary-use or production JCL. Displays the IMOD Facility of CA-GSS if theevent is a REXX IMOD.






EMAIL Command

EMAIL Command

The EMAIL command allows editing of the email location data set to specifyemail template information in the TRACMnnn location data sets. You mustspecify either a member name, a prefix, or an *. You must specify a locationfollowing the comma as either L=nnn or just nnn. If you specify the membername as * or prefix*, the PDS member list displays the requested list ofmembers. You can then select a member to edit. If you specify a membername without an *, edit for the member is invoked directly.


��─ ──EMAIL ──┬ ┬─member── , ──┬ ┬──── nnn ───────────────────────────────────��├ ┤─prefix�─ └ ┘──L=

└ ┘─�───────







EMAILLST Command

EMAILLST Command

The EMAILLST command alters or displays the list of EMAIL template membernames and the events that trigger the email creation for a job on thecheckpoint.


��─ ──EMAILLST ─────────────────────────────────────────────────────────��





ENDSAVE Command

ENDSAVE Command

The ENDSAVE command exits from a panel and saves any changes you havemade.


■ ADR Table (in EDIT mode only)

■ AMR Table (in EDIT mode only)

■ CCPF Table (in EDIT mode only)

■ SCS Table (in EDIT mode only)

■ Cyclic Calendar

■ Holiday Calendar



■ Event/Jobstream Addition

■ GSO panels


ENQ Command

ENQ Command

The ENQ command displays the Enqueue Research panel.








ENQN= Command

ENQN= Command

The ENQN= command displays enqueue activity for the QNAME specified byenqname.


��─ ──ENQN=enqname ─────────────────────────────────────────────────────��








EXCLUDE Command

EXCLUDE Command

The EXCLUDE command excludes certain events from the listed events on thedisplay based on whether those certain events are predecessors or successors.The RESET command refreshes the Missing Events panel.


��─ ──EXCLUDE ──┬ ┬─P──────────── ────────────────────────────────────────�� ├ ┤─PREDECESSORS─ ├ ┤─S──────────── └ ┘─SUCCESSORS───

This command is used on the Missing Events panel.


FIND Command

FIND Command

The FIND command searches the display for character strings. Use single ordouble quotes around string. You can limit the search to a specific column.Specify a column name that is longer than one word incolumnname1-columnname2-columnname3 format. Use the FIND commandwith no parameters to repeat the previous find.


┌ ┐─—─────────────── ┌ ┐─NEXT──��──FIND─ ──'string' ───� ┴┬ ┬─────────────── ──┼ ┼─────── ───────────────────��

└ ┘──'column-name' ├ ┤─ALL─── ├ ┤─FIRST─ └ ┘─LAST──


■ ADR Table and ADR Table List

■ AMR Table and AMR Table List


■ CCPF Table and CCPF Table List

■ Change Audit History and Cross Node Query

■ Event History Display and Event Resource Profile

■ Holiday Calendar and Cyclic Calendar

■ Missing Events

■ IPL History

■ Scheduled Event Display and Network

■ SCS Table and SCS Table List

■ Sysout Capture and Volume Pull List

■ DASD Selection List and VTOC

■ Global Resource Definitions

Example

This example finds all the occurrences of EOM in the Event Name column onthe panel.

FIND EOM EVENT-NAME ALL


FORCE Command

FORCE Command

The FORCE command allows jobs to be released when Unicenter CA-Jobtracis on hold. Issuing this command requires the use of both a line command (*)and a primary command (FORCE).

Place the * on the line next to the job to be forced, and then enter FORCE onthe command line. The job is allowed to run, even if Unicenter CA-Jobtrac is onhold. The job is still subject to any dependencies that it may have. It is onlyreleased when all of its dependencies are removed.

This command does not force jobs to run when the checkpoint is locked.

The * line command, when specified without the FORCE command, displays ahex dump of the checkpoint record for the event. This command is typically notuseful to operators. It is intended for use at the request of Technical Support.


FSWAP Command

FSWAP Command

The FSWAP command changes the database and token that is being accessedby the Unicenter CA-Jobtrac ISPF interface to access forecast information orswaps back to the production database/token. When swapped to a forecastdatabase, the event related displays will access the forecast data. Tables andcalendars, JCL, SCL related commands continue to access the productiondatabase or be unavailable.


��─ ──FSWAP ──┬ ┬──token ──┬ ┬─────── ──────────────────────────────────────��│ │└ ┘──,dbid

└ ┘─PROD─────────────




Example

This example swaps to the forecast database for token 'A'. The database IDused is the default specified in the FCSTDBID keyword of the PPOPTION(JOBTRA00) member.

FSWAP A

This example swaps to the forecast database for token 5 for forecast database0165.

FSWAP 5,�165

This example swaps to the production database and token defined by theJOBTRACx DD DUMMY.

FSWAP PROD


GSO Command

GSO Command

The GSO command displays the GSO panels for the selected SCL member. Ifmember name is used, the specified schedule is displayed from the specifiedSCL library (nnn). If * is used with or without a partial name (prefix), an ISPFEDIT Member List is displayed listing all the schedules whose names start witha partial schedule name. Select a name from the list.


┌ ┐─�───────��─ ──GSO ──┼ ┼───────── ──┬ ┬───── ────────────────────────────────────────�� ├ ┤─memname─ └ ┘──nnn └ ┘─prefix�─









Example

This example displays the schedule WEEKSCD from your default SCL library.

GSO WEEKSCD


HIST Command

HIST Command

The HIST command displays the Event History Display panel for the selectedevents.

Note: Specifying * causes Unicenter CA-Jobtrac to read the entire historydatabase. The response time for this command depends on the size of thehistory database.


��─ ── ──┬ ┬─H──── ──┬ ┬─eventname─ ────────────────────────────────────────�� └ ┘─HIST─ ├ ┤─prefix�─── └ ┘─�─────────









HOMELOC= Command

HOMELOC= Command

The HOMELOC= command changes or sets your default location where nnn isthe location ID.


��─ ──HOMELOC=nnn ──────────────────────────────────────────────────────��

Note: To change the default location, see “PROFILE Command” on page 70.






This command updates your Unicenter CA-Jobtrac TSO profile.


I Command

I Command

The I command displays the Change Audit History panel for an event. Thepanel displays information about changes made to an event.










IPLS Command

IPLS Command

The IPLS command displays the IPL History panel.







ISERVE Command

ISERVE Command

The ISERVE command displays the IMOD Facility of CA-GSS. This facility isused to create REXX IMODs. Be aware that CA-GSS must be set up for edit.







J= Command

J= Command

The J= command displays the Scheduled Event Display panel listing all eventsbeginning with prefix.


��─ ──J=prefix ─────────────────────────────────────────────────────────��






Example

This example produces a Scheduled Event Display panel listing all eventswhose names begin with TESTJ.

J=TESTJ


JCL Command

JCL Command

The JCL command displays the production JCL for an event for editing. Ifeventname is used, the specified event's production JCL member is displayed.If * is used with a prefix (partial event name), a list is displayed listing all theJCL members whose names start with the prefix. Use * without a prefix todisplay a listing of all the JCL members. Select a name from the list. Optionally,you can specify a production JCL library using the nnn parameter where nnn isthe location ID.


┌ ┐─�─────────��─ ──JCL ──┼ ┼─────────── ──┬ ┬───── ──────────────────────────────────────�� ├ ┤─eventname─ └ ┘ ─nnn─ └ ┘─prefix�───










JCLTRAC Command

JCLTRAC Command

The JCLTRAC command accesses the CA-JCLTrac primary options panel toupdate options and to generate reports.






Or, this command invokes the JCL ANALYZER that syntax checks the JCLmember.


■ Edit Production JCL

■ Edit Temporary JCL

For more information, see “RESET Command” on page 75.


JMF Command

JMF Command

The JMF command invokes EDIT on the JMFSYM01 member of the UnicenterCA-Jobtrac DD DATEFILE library.







JOBQ= Command

JOBQ= Command

The JOBQ= command displays enqueue research for the event specified byeventname or event prefix. The resulting display lists all data sets andresources in use by the event. The specified event must be executing when thiscommand is issued.


��─ ──JOBQ= ──┬ ┬─eventname─ ─────────────────────────────────────────────�� └ ┘─prefix�───







Example

If PRODJOB1 is executing, this example displays enqueue research forPRODJOB1.

JOBQ=PRODJOB1


JTS Command

JTS Command

The JTS command displays the Table Services Selection Menu. You can usethe menu to edit, browse, activate, copy, or print the following tables:

■ ADR tables (perform specified actions when data sets are closed)

■ AMR tables (perform specified actions when console messages are issued)

■ SCS tables (schedule commands for execution)

■ CCPF tables (impose condition code processing on a program, job, jobstep, or procstep)







K= Command

K= Command

The K= command displays a Scheduled Event Display panel listing events withthe specified characteristic or characteristics. Use this command to displayevents currently having the dependency or dependencies you specify.


┌ ┐───────��─ ──K= ───� ┴┬ ┬─── ──────────────────────────────────────────────────────�� ├ ┤─A─ ├ ┤─C─ ├ ┤─D─ ├ ┤─E─ ├ ┤─H─ ├ ┤─L─ ├ ┤─N─ ├ ┤─R─ ├ ┤─S─ ├ ┤─T─ ├ ┤─V─ └ ┘─W─

ADisplays events that terminated abnormally. This includes events thatabended, were purged, ended with an abnormal condition code, or had aJCL error.

CDisplays events that have completed. This includes events that abended,were purged, had a JCL error, or are awaiting output release.

DDisplays events with a dependency code.

EDisplays events that are currently executing.

HDisplays events with no incomplete predecessors.

LDisplays events whose scheduled start time has passed (late) or have alate status.

NDisplays NJE jobs submitted on this node.

RDisplays events that are late awaiting rerun.


K= Command

SDisplays remotely-submitted NJE jobs.

TDisplays events that are awaiting scheduled start time or date.

VDisplays events with Pred Count values that do not match the number ofcurrent predecessors listed.

WDisplays events that have been submitted by Unicenter CA-Jobtrac buthave not begun execution (awaiting an initiator).






Examples

This example lists all events with dependency codes.

K=D

This example lists all events awaiting restart, currently executing, or completed.

K=REC


L= Command

L= Command

The L= command displays a Scheduled Event Display panel listing events withlocation ID specified by the nnn parameter (any location ID 000 to 254).


��─ ──L=nnn ──┬ ┬─────────────── ─────────────────────────────────────────�� └ ┘──, ──┬ ┬─SHIFT1─ ├ ┤─SHIFT2─ └ ┘─SHIFT3─






Example

This example displays all events in location 000 and the times in the SYSUSER panel for SHIFT3 times.

L=��,SHIFT3


MACT or MANUAL Command

MACT or MANUAL Command

The MACT or MANUAL commands display the Manual Action Detail (check list)panel for the selected event (if used). Next, remove the manual action so thatthe event will execute.

This command is used on the Scheduled Event Detail panel.


MISSING Command

MISSING Command

The MISSING command displays the Missing Events panel. Also see“EXCLUDE Command” on page 43.







N= Command

N= Command

The N= command displays a Scheduled Event Display panel listing any eventwith a node parameter, including cross-platform jobs.


��─ ──N=nodename ───────────────────────────────────────────────────────��







O or OUT Command

O or OUT Command

The O or OUT command displays sysout capture facility panels. If O or OUT isentered with no parameter, the Sysout Capture Facility menu is displayed.


��─ ── ──┬ ┬─O─── ──┬ ┬─────────── ─,──D────────────────────────────────────�� └ ┘─OUT─ ├ ┤─eventname─ ├ ┤─prefix�─── ├ ┤─�───────── └ ┘─&─────────

eventname|prefix*Displays a Sysout Capture panel listing all sysouts for the specified eventname or prefix or, if sysouts for only one event match the event name orprefix, displays the event actual sysouts

*Displays a Sysout Capture panel listing all sysouts.

&Displays the sysout archive index.

DDisplays deleted sysout entries.

To display the sysouts online, enter S in the field to the left of the event whosesysouts you want to display. Or to print the sysouts, enter O in the field to theevent whose sysouts you want to print.

Examples

This example displays all sysout entries.

O �

This example displays sysout entries for TESTJOB1.

O TESTJOB1

This example displays deleted sysout entries for any event beginning withTEST.

O TEST,D


O or OUT Command

Restoring Deleted Sysout Entries to the Sysout Capture Panel: After asysout entry is deleted and before the archive task removes the sysouts fromthe online capture database, you can restore the entry to the Sysout Capturepanel. Use the following steps to restore deleted sysouts. You cannot restoresysouts while sysout archival is underway.

1. Redisplay the deleted sysout entry you want to restore to the SysoutCapture panel.

2. Enter U (undelete) in the field to the left of the entry you want to restore.

3. Press Enter to restore the entry to the Sysout Capture panel.











PARMS Command

PARMS Command

The PARMS command Invokes edit capability on the PPOPTION library.Optionally, you can specify memname to invoke edit capability on a particularmember from the TRACPARM DD. Possible member names are JOBTRA00,EXCLPARM, and RESOURCE.


��──PARMS─ ──┬ ┬───────── ───────────────────────────────────────────────�� └ ┘──memname







PASSWORD Command

PASSWORD Command

The PASSWORD command displays the Remote System Credentials panelfrom the Scheduled Event Detail panel. The panel is displayed using the eventname (or alternate member name if allowed) and the event location.

The Remote System Credentials pop-up panel is used with cross-platformevents (event type C) to specify the user ID, domain (used by Windowssecurity), and password to be used for the remote submission.


■ Event Execution Detail (as PASSWORD)

■ Scheduled Event Detail (as PASSWORD)

■ Scheduled Event Display (as PASSWORD eventname)


PP= Command

PP= Command

The PP= command displays a Scheduled Event Display panel listing eventsscheduled for the process period specified by procprd.


��─ ──PP=procprd ───────────────────────────────────────────────────────��






Example

This example lists all events scheduled for process period TUESDAY.

PP=TUESDAY


PROFILE Command

PROFILE Command

The PROFILE command displays the CA-Jobtrac User Profile panel. TheCA-Jobtrac User Profile panel is a pop-up panel that allows the users tocustomize their Unicenter CA-Jobtrac ISPF interface options, such as defaultlocation, enabling prompts, default search command, date format, or theUnicenter CA-View database name.








PURGE Command

PURGE Command

The PURGE command purges the selected event from the current schedule.

If the event is awaiting execution, this issues a $PJnnnn command.

If the event is awaiting submission, all successors are released fromdependence on the event.

It also changes the status of the event to PURGED by userid. If you haveUnicenter CA-11, this command automatically changes the Unicenter CA-11status of the event to PRODUCTION. Also see the P line command inChapter 2, “Line Commands” on page 107.





RALL Command

RALL Command

The RALL command displays all events on the current schedule. Also see “DCommand” on page 27.







RELEASE Command

RELEASE Command

The RELEASE command releases dependencies.

If an event is awaiting submission, removes all dependencies except abendbypass (A) and predecessor (P).

If an event is awaiting execution, Unicenter CA-Jobtrac issues the $AJnnnncommand.

If an event is completed, Unicenter CA-Jobtrac removes output release (O)dependency.

Also see the A line command in Chapter 2, “Line Commands” on page 107.





REMLOC= Command

REMLOC= Command

The REMLOC= command removes events for viewing from the locationspecified by nnn (any location ID 000-254) from the Scheduled Event Displaypanel. If you use the TRACX26 user exit, you cannot use REMLOC=nnn toremove events for viewing.


��─ ──REMLOC=nnn ───────────────────────────────────────────────────────��






Example

This example removes events with location 029 for viewing from the panel.

REMLOC=�29

Note: To add events (for viewing only) to the display, use the ADDLOC=029command.


RESET Command

RESET Command

The RESET command refreshes the current panel's display.


��─ ──┬ ┬─R───── ────────────────────────────────────────────────────────�� └ ┘─RESET─





■ ADR Table List

■ AMR Table List

■ CCPF Table List

■ SCS Table List

■ Missing Events




RESOURCE Command

RESOURCE Command

The RESOURCE command displays the Resource Assignments panel for theselected event that is currently using resources. This shows definitions ofresource dependencies for the selected event.


For more information, see “@RES Command” on page 106.


RESV Command

RESV Command

The RESV command displays a list of any current DASD reserves in effect.








RETRY Command

RETRY Command

The RETRY command retries the posting of the completion status informationof an NJE job back to the submitting system from the execution system.

This command is used on the NJE Execution Detail panel.


RSRC Command

RSRC Command

The RSRC command displays the Resource Assignments panel for theselected event. This shows definitions of resource dependencies for theselected event. This command is the same as the RESOURCE command.



RUN Command

RUN Command

The RUN command adds the event named eventname to the current schedulefor immediate submission (no dependencies). Assigns current time and dateand process period RQ-userid. If the event is a schedule or UnicenterCA-Jobtrac task, you must include the 0. Optionally, specify a version number(.vv) and/or location ID (,L=nnn). If a duplicate event exists on the currentschedule, its location will be used as the location for the newly added event.

Specify the event type by using the (,C) (,D) or (,E) options. The event typesare as follows:

,CIndicates that the named event defines a command to be executed at aparticular remote node.

,DIndicates that the named event is a dummy job.

,EIndicates the named event is a REXX IMOD.

Specify the GSS node name (up to 16 characters) of the executing node for thenamed event with the ,N=nodename parameter. Depending on the type ofevent, use the REXX IMOD (,E event type), or to specify a command to beexecuted at a particular remote node (,C event type).


��──RUN─ ──┬ ┬───────────────── ──┬ ┬───── ──┬ ┬──────── ──┬ ┬────────── ───────� └ ┘── ──┬ ┬─eventname─ └ ┘──.vv └ ┘──,L=nnn └ ┘──, ──┬ ┬─C─

├ ┤──�sclname ─ ├ ┤─D─└ ┘──�tasknm ── └ ┘─E─

�─ ──┬ ┬───────────── ──┬ ┬────────────────────────────── ─────────────────��└ ┘──,N=nodename └ ┘──,A= ──┬ ┬─command─────────────

├ ┤─imod-arg──────────── └ ┘─shellscriptname.arg─







RUN Command

Examples

This example adds PRODJOB1 to the current schedule for immediatesubmission.

RUN PRODJOB1

This example adds PRODJOB1 with location ID 002 to the current schedule forimmediate submission.

RUN PRODJOB1,L=��2

This example adds Version 5 of PRODJOB1 with location ID 002 to the currentschedule for immediate submission.

RUN PRODJOB1.�5,L=��2


S Command

S Command

The S command displays a Scheduled Event Detail panel for the eventspecified by eventname. If the event has been submitted, an Event ExecutionDetail panel is displayed instead.


��──S──eventname──────────────────────────────────────────────────────��




Example

This example displays a Scheduled Event Detail panel for PRODJOB1. IfPRODJOB1 has already been submitted, an Event Execution Detail panel.

S PRODJOB1


SAR Command

SAR Command

The SAR command displays the CA-View Primary Selection panel. The firsttime you issue this command, the Unicenter CA-View product prompts you for ahigh-level database name. Enter the high-level index of the Unicenter CA-Viewdatabase you want to access. This name is saved in your Unicenter CA-Jobtracuser profile. The sysout that you selected is displayed, and you can enter anyUnicenter CA-View command you want. For more information about UnicenterCA-View commands, see the Unicenter CA-View documentation.











SARDB Command

SARDB Command

The SARDB command changes the Unicenter CA-View database that UnicenterCA-Jobtrac interfaces with. When you issue this command, Unicenter CA-Viewdisplays the Unicenter CA-View Database Selection panel where you canspecify a different high-level database name. Enter the high-level index of theUnicenter CA-View database you want to access. The new name is saved inyour Unicenter CA-Jobtrac user profile.







SAVE Command

SAVE Command

The SAVE command saves any changes you have made to an event from apanel.







SCL Command

SCL Command

The SCL command displays a schedule from a specified SCL library (nnn). Ifmemname is used, the specified schedule is displayed. If * is used with a prefix(partial schedule name), a list is displayed listing all the schedule memberswhose names start with the prefix. Use * without a prefix to display a listing ofall the schedule members. Select a name from the list. Also see the E linecommand in Chapter 2, “Line Commands” on page 107.


┌ ┐─�────────��──SCL─ ──┼ ┼────────── ──┬ ┬───── ───────────────────────────────────────�� ├ ┤─memname── └ ┘──nnn ├ ┤─�memname─ └ ┘─prefix�──









Example

This example displays the schedule WEEKSCD from your default SCL library.

SCL WEEKSCD


SCS Command

SCS Command

The SCS command displays the active System Command Scheduling table.






For editing the SCS tables, see “JTS Command” on page 58.


SHIFT Command

SHIFT Command

The SHIFT command displays a Scheduled Event Display panel listing eventswith target submission times during the shift specified (1, 2, or 3). The T= andSHIFT primary commands are mutually exclusive.


��─ ──┬ ┬─SHIFT1─ ───────────────────────────────────────────────────────�� ├ ┤─SHIFT2─ └ ┘─SHIFT3─






Note: For more information, see “SYS USER Command” on page 95 to set upSHIFT1, 2, and 3 and “L= Command” on page 61.

Example

This example lists events with target submission times during the second shift.

SHIFT2


SORT Command

SORT Command

The SORT command sorts the display in either ascending or descending orderbased on the values in a specified column. Specify a column name that islonger than one word in columnname1-columnname2-columnname3 format.Use the SORT command without any parameters to put the display back in itsoriginal sequence.


┌ ┐─—───────────────��──SORT─ ───� ┴┬ ┬─────────────── ──┬ ┬─── ─────────────────────────────────�� └ ┘──'column-name' ├ ┤─A─ └ ┘─D─


■ ADR Table and ADR Table List

■ AMR Table and AMR Table List


■ CCPF Table and CCPF Table List

■ Change Audit History and Cross Node Query

■ Event History Display and Event Resource Profile

■ Global Resource Definitions

■ Holiday Calendar and Cyclic Calendar

■ IPL History

■ Scheduled Event Display and Network

■ SCS Table and SCS Table List

■ Sysout Capture

■ Volume Pull List

■ DASD Selection List and VTOC

Example

This example sorts the display in ascending order by the contents of the Statuscolumn.

SORT CURRENT-STATUS


SPACE Command

SPACE Command

The SPACE command displays an analysis of DASD (Direct Access StorageDevice) space.







STATUS Command

STATUS Command

The STATUS command displays an analysis of component resource use on theUnicenter CA-Jobtrac database and sysout capture file. Also displays versionand genlevel, token, and restage options.







SYS CYCS Command

SYS CYCS Command

The SYS CYCS command displays in edit mode the Cyclic Calendars panel,which shows definitions for cyclic periods for each location.

Valid processing cycles span from 2 to 254 days. This panel can hold up to 105different calendar locations. Each location can have up to 14 cycles.







SYS HOLS Command

SYS HOLS Command

The SYS HOLS command displays the Holiday Calendars panel, which showsdefinitions of holidays for each location. Holiday calendars can hold up to 24holidays. The default date for each new holiday calendar is 0230. This is not avalid date.







SYS OPTS Command

SYS OPTS Command

The SYS OPTS command displays the Global Options Menu. Some of thevalues are read-only, and some can be updated. If you make a change andsave the change with PF3, this will update the system options.







SYS USER Command

SYS USER Command

The SYS USER command displays the User Options panel, where you canredefine PF key functions and time ranges for the SHIFT command. This panelalso displays the current display date parameter. Also see “SHIFT Command”on page 88.







T= Command

T= Command

The T= command displays a Scheduled Event Display panel listing events withtarget times during the time period specified. You can specify either a singlehour (hh) or a time range (hhmm-hhmm). The T= and SHIFT primarycommands are mutually exclusive.


��─ ──T=hh ──┬ ┬───────── ────────────────────────────────────────────────�� └ ┘──mm-hhmm






Examples

This example lists events with target times from 12:00 p.m. to 12:59 p.m.

T=12

This example lists events with target times from 1:23 a.m. to 4:11 a.m.

T=�123-�411


TEMP Command

TEMP Command

The TEMP command displays the temporary-use JCL for an event for editing ifthe event has not been submitted or has not completed successfully. If notemporary-use JCL exists for the event, a member containing a copy of theevent's production JCL is created in the temporary-use JCL library for theevent. On the Scheduled Event Detail panel, you see the field JCL source=T.Also see “T= Command” on page 96.



VER Command

VER Command

The VER command displays the version number of your Unicenter CA-Jobtrac.





VOLUME Command

VOLUME Command

The VOLUME command executes CA-JCLTrac to create a Volume Pull Listpanel from a real-time look at the JCL. This command is ignored if issuedagainst schedule members, IMODs, dummy jobs, or jobs in completed status. IfCA-JCLTrac encounters an error, the message JCL PROCESSING ERRORappears on the panel. One or more CA-JCLTrac messages will be written to theconsole describing the problem in more detail. The Volume Pull List Assistpanel includes vaulting and tape creation information supplied throughTRACX25. CA-JCLTrac uses the current setting for the EXIT25 or NOEXIT25option for your TSO session to determine whether to call the exit.



WAIT Command

WAIT Command

The WAIT command displays enqueue conflicts.








XNODE Command

XNODE Command

The XNODE command displays the Cross Node Query-Criteria Selection panel.







? or ?EDIT Command

? or ?EDIT Command

The ? command displays documentation members for viewing.

The ?EDIT command displays documentation members for editing.

If eventname is used, the specified event's documentation member is displayed.If * is used with a prefix (partial event name), a list is displayed listing all thedocumentation members whose names start with the prefix. Use * without aprefix to display a listing of all the documentation members. Select a name fromthe list. Optionally, you can specify a documentation library using the nnnparameter where nnn is the location ID. The location ID parameter (nnn) allowsyou to access multiple documentation libraries. Also see “DOC or DOCEDITCommand” on page 33.

The ? or ?EDIT commands have the following format:

��─ ──┬ ┬─?───── ──┬ ┬───────────────── ──┬ ┬───── ──────────────────────────�� └ ┘─?EDIT─ │ │┌ ┐─�───────── └ ┘──nnn └ ┘── ──┼ ┼─eventname─ └ ┘─prefix�───











@HOLD Command

@HOLD Command

The @HOLD command puts Unicenter CA-Jobtrac on hold. Places messageSCHEDULE HELD in upper-right corner of the panel. Issues the TRAC111Iuser HAS PLACED SCHEDULE ON HOLD console message.







@INT Command

@INT Command

The @INT command requests a continuous update of the Scheduled EventDisplay panel. The keyboard is locked while the update is in progress.Depending on the type of terminal you have, you can enter either the PA1 orthe ATTN key to terminate the update session and wait for the panel toreappear. The default is five seconds. Use the nn parameter if you want to setan interval time that differs from the default time. This command is valid onlyafter you enter the RALL command.


��──@INT─ ──┬ ┬─────────── ──────────────────────────────────────────────�� │ │┌ ┐─5── └ ┘──= ──┴ ┴─nn─







@REL Command

@REL Command

The @REL command releases Unicenter CA-Jobtrac if it were put on hold.Issues the TRAC001I user HAS RELEASED SCHEDULE HOLD consolemessage.







@RES Command

@RES Command

The @RES command displays the Global Resource Definitions panel. Also see“RESOURCE Command” on page 76.







Chapter 2. Line Commands

The following describes the line commands available on the Scheduled EventDisplay and Scheduled Event Network panels. Line commands can be disabledin Unicenter CA-Jobtrac with the startup option DISABLE. For more information,see the Planning and Implementation Guide.

0(Zero) Browse sysouts using Unicenter CA-View. The first time youissue this command, Unicenter CA-View prompts you for a UnicenterCA-View high-level database name. Enter the high-level index of theUnicenter CA-View database that you want to access. This name is savedin your Unicenter CA-Jobtrac user profile. The sysout that you selected isdisplayed and you can enter any Unicenter CA-View command you want.For more information about Unicenter CA-View commands, see theUnicenter CA-View documentation.

ARelease dependencies. If an event is awaiting submission, removes alldependencies except abend bypass (A) and predecessor (P). If an event isawaiting execution, issues the $AJnnnn command. If an event is completed,removes output release (O) dependency.

Equivalent to the RELEASE primary command.

BBrowse JCL/SCL/IMOD. Displays either the JCL or the SCL that will besubmitted for the event. The JCL can be either temporary-use or productionJCL. You can only view the JCL or SCL, you cannot edit it with thiscommand. Display the IMOD Facility of CA-GSS if the event is a REXXIMOD.

Equivalent to the BROWSE primary command.

CCondition codes. Displays Condition Code Exceptions panel for theselected event.

Equivalent to the CC primary command.

DDelete event. Deletes the event awaiting submission. The selected eventis deleted from the current schedule and put on the history database withthe user ID of the user who deleted the event. If you have Unicenter CA-11,this command automatically changes the Unicenter CA-11 status of theevent to PRODUCTION. Any predecessors or successors that are relatedto this event are not released from dependence on this event.

Equivalent to the DELETE primary command.

Chapter 2. Line Commands 107

EEdit JCL/SCL/IMOD. Displays JCL for the selected event or SCL for theselected schedule. If authorized, you can edit the JCL or SCL. The JCL canbe either temporary-use or production JCL. Displays the IMOD Facility ofCA-GSS if the event is a REXX IMOD.

Equivalent to the EDIT primary command.

FFile triggers. Displays the ADR Table panel for the selected event. Thisshows the file (data set name) trigger list for the selected name.

Not equivalent to a primary command.

GInvoke GSO. Displays the GSO panels for this schedule.

Equivalent to the GSO primary command.

HHistory. Displays the Event History Display panel of the selected event onthe history database.

Equivalent to the HIST primary command.

IInquiry. Displays the Change Audit History panel for the selected event.

Equivalent to the AUDIT primary command.

JEdit temporary-use JCL. Displays the temporary-use JCL for an event forediting if the event has not been submitted. If no temporary-use JCL existsfor the event, creates a member containing a copy of the event's productionJCL in the temporary-use JCL library for the event.

Equivalent to the TEMP primary command.

LList dependent job stream. Displays the Scheduled Event Network panelfor the selected event. This lists the event's primary predecessor andsuccessor event network in primary execution sequence.


MManual dependency. Displays the Manual Action Detail panel for theselected event (if available).

Equivalent to the MANUAL or MACT primary command.

NEnqueue research. Displays the CA-Jobtrac Enqueue Research panel.Displays resources (data set names) for the selected event. The event mustbe currently executing.

Equivalent to the ENQ primary command.


OOutput. Displays the Sysout Capture panel or the actual sysouts for theselected event.

Equivalent to the OUT primary command.

PPurge event. Purges the selected event from the current schedule. If theevent is awaiting execution, this issues a $PJnnnn command. If the event isawaiting submission, all successors are released from dependence on theevent. If you have Unicenter CA-11, this command automatically changesthe Unicenter CA-11 status of the event to PRODUCTION.

Equivalent to the PURGE primary command.

QDisplay Unicenter CA-SYSVIEW Job Summary panel. Allows you toview a selected event and to issue Unicenter CA-SYSVIEW commands. Toexit from Unicenter CA-SYSVIEW, enter PF03. You are returned to thepanel from which you issued the Q command. This command is only valid ifyou are a licensed Unicenter CA-SYSVIEW user and if your TSO sessionhas access to the Unicenter CA-SYSVIEW ISPF program and its files.


RRerun/Restart interface. With an automated restart system (such asUnicenter CA-11), invokes the event restart interface, and schedules theevent for rerun.

Without a restart system, schedules the event for rerun (completed orhistory entries only). In any case, reassigns predecessor dependencies,output release dependencies, and successor events as in the original run.Removes environmental dependencies.

The REXX IMOD is scheduled for rerun without dependencies, but with aJCL hold. REXX IMOD events use Unicenter CA-Jobtrac rerun/restartfacility. They cannot use an automated restart system.


SSelect for detail display. Displays either the Scheduled Event Detailpanel (if the selected event is waiting submission), the Event ExecutionDetail panel (if the event has been submitted), or the NJE Execution Detailpanel (if it is an NJE job).

Equivalent to the S primary command.


TEdit temporary-use JCL. Displays the temporary-use JCL for an event forediting if the event has not been submitted. If no temporary-use JCL existsfor the event, a member containing a copy of the event's production JCL iscreated in the temporary-use JCL library for the event.

Equivalent to the TEMP primary command.

VVolume Pull List. Executes CA-JCLTrac to create a Volume Pull Listpanel from a real-time look at the JCL.

The V line command is ignored if issued against schedule members,IMODs, dummy jobs, or jobs in completed status.

If CA-JCLTrac encounters an error prior to JCL analysis, the message JCLPROCESSING ERROR appears on the Scheduled Event Display panel. If aJCL error occurs, the message will appear on the Volume Pull List panel.In both cases, one or more CA-JCLTrac messages will be written to theconsole describing the problem in more detail.

The Volume Pull List panel includes vaulting and tape creation informationsupplied through TRACX25. CA-JCLTrac uses the current setting for theEXIT25 or NOEXIT25 option for your TSO session to determine whether tocall the exit.

Equivalent to the VOLUME primary command.

XResource assignments. Displays the Resource Assignments panel for theselected event. This shows definitions of resource dependencies for theselected event.

Equivalent to the RESOURCE primary command.

YCPM Flow Information panel. Displays CPM flownames, start/end times,and SLA.


ZRecapture Sysout. Requests the capture of sysout for an event.


?Documentation. Displays the selected event's documentation member.

Equivalent to the DOC, DOCEDIT, and ?EDIT primary commands.


@Submit command. Clears entry status and reuses entry forresubmissions.

You can do this to any entry regardless of its current status. This does notalter dependency codes.

You should use this command with CAUTION.

Note: You can use the DISABLE startup option to remove this command.

%EMAILLST command. Alters or displays the EMAIL template defined for ajob on the checkpoint.


Chapter 3. SCL (Schedule ControlLanguage)

The following topics explain SCL member's record formats and fields.

Chapter 3. SCL (Schedule Control Language) 113

Record Format

Record Format

The following figure depicts the record format of an SCL member. The followingsections briefly describe the columns of the record. For more information aboutSCL, see the Schedule Creation Guide.

1---+----1�---+----2�---+----3�---+----4�---+----5�---+----6�---+----7�---+----8 �EVENTNM TIME DATE DEPS RELEASE1RELEASE2RELEASE3RELEASE4 PROCESSP OPDCCDELOCVV

Event Name

The following describes the Event Name field:

SCL HeadingEVENTNM

Columns1 - 8

DescriptionSpecifies the name of one of the following to be added to the currentschedule:

■ Job (1-8 characters)

■ Schedule (1-7 character name of the SCL member, preceded byzero, as in 0sclname)

■ Task (0ARCHIVE, 0SYSARCH, 0JOBARCH)

■ REXX IMOD (1-8 characters)

■ Dummy job (1-8 characters)

A + (plus sign) in column one means that the record is acontinuation record.


Record Format

Threshold

The following describes the Threshold SCL field:

SCL Headingblank

Column9

DescriptionSpecifies the action to occur at the time shown in the Time (TIME)field. Possible entries:

blankIndicates both start and target time.

AIndicates abort time.

SIndicates start time only.

TIndicates target time only.

The Threshold field (no heading, column 9) and the Time field (TIME, columns10-13) work together to provide one or more of the following functions:

■ Set a target time (time after which an unsubmitted event is flagged LATE)

■ Set a start time (earliest time an event can be submitted for execution)

■ Set an abort time (latest time an event can be submitted for execution)


Record Format

Time

The following table describes the Time SCL field:

SCL HeadingTIME

Columns10 - 13

DescriptionSpecifies the time at which the action indicated by the Thresholdfield (column 09) is to occur. Possible entries:

hhmmFour-digit number, where hh specifies the hour (00-23)and mm specifies the minute (00-59).

*Sets the time based on the event's historical start time.Depending on the available event history, the time is setdifferently. The use of * is not much recommended.Depending on various combinations of dependencies youspecify, the results might not be what you expected. Formore information, see the creating schedules chapters.

ASAPAs soon as all other dependencies are met.


Record Format

Holiday Action

The following describes the Holiday Action SCL field:

SCL Headingblank

Column14

DescriptionSpecifies the action to occur if the event's target date falls on aholiday. This field cannot be used with the process periodWORKDAYS. Possible entries:

blankIndicates the event is not scheduled at all (unless thetarget date is not the current date).

SIndicates the event is scheduled for the target date, eventhough it is a holiday.

HIndicates the event is scheduled for the target date, eventhough it is a holiday, and is assigned a holiday hold witha manual dependency (MH dependency code).

NIndicates the event is scheduled for the next calendarday after the holiday, even if the next day is not a regularworkday.

WIndicates the event is scheduled for the next workdayfollowing the holiday.

OIndicates the event is scheduled only on holidays. If thetarget date is not a holiday, the event is not scheduled atall.

PIndicates the event is scheduled for the workday previousto the holiday.


Record Format

Date

The following describes the Date SCL field:

SCL HeadingDATE

Columns15 - 18

DescriptionSpecifies the date on which the event is to be submitted (targetdate). Possible entries:

mmddFour-digit number, where mm specifies the month (01-12)and dd specifies the day (01-31).

mm**The event is scheduled any day during the monthspecified (for example, 02** schedules the event any dayduring February).

**ddThe event is scheduled during any month on thespecified day (for example, **10 schedules the event onthe 10th day of any month).

*The event is scheduled for the current date.

*+nThe event is scheduled for n days after the current date(for example, *+3 schedules the event for the currentdate plus three).

ASAPAs soon as all other dependencies are met. ASAP DATErequires ASAP TIME. ASAP DATE jobs never becomelate.


Record Format

Event Type

The following describes the Event Type SCL field:

SCL Headingblank

Column19

DescriptionIdentifies the type of event you are scheduling. Possible entries:

CIndicates the event defines a command to be executed ata particular remote node.

DIndicates the event is a dummy job.

EIndicates the event is a REXX IMOD. For informationabout the use of REXX IMODs in Unicenter CA-Jobtrac,see the Extended Scheduling Services Guide.

blankIndicates the event is any other type of event.


Record Format

Execution Dependency

The following describes the Execution Dependency SCL field:

SCL HeadingDEPS

Columns20 - 24

DescriptionSpecifies execution dependencies to be assigned. Possible entriesinclude the following:

AIndicates an abend bypass.

DIndicates a data set required dependency.

EIndicates an edit JCL dependency.

JIndicates a JCL required dependency.

MIndicates a manual release dependency.

OIndicates an output release.

PIndicates a predecessor event dependency.

QIndicates a queued release dependency.

?Indicates a view documentation dependency.


Record Format

Referback

The following describes the Referback SCL field:

SCL Headingblank

Column25

DescriptionSpecifies conditional requirements. This can be coded on the event'ssecondary record or on referback records to add executiondependencies to the primary record. Possible entries:

A=Indicates that the event listed in theSuccessor/Predecessor (RELEASEn) fields of the samerecord is an alternate member name for the event's JCL.Normally, the event's JCL must be in a member with thesame name as the event, this allows you to use amember with a different name.

I=Defines a time interval at which the event is to besubmitted.

CC=Defines step exceptions to the maximum condition codevalue defined for the event.

R=Defines resource conditions to be satisfied before theevent can be submitted. This version only supports onecharacter resource codes. Use RS= instead.

RS=Defines resource conditions to be satisfied before theevent can be submitted. Resource codes (up to 8) areseparated by commas. Each code can be two characterslong and must be defined in the RESOURCE PPOPTIONmember.

&Allows the argument for the IP= and ED= referback fieldentries to continue to a length of 255 characters.

IP=This entry specifies an argument to pass to the eventnamed in the Event Name (EVENTNM) field.


Record Format

EIndicates that events listed in the Successor/Predecessor(RELEASEn) fields of the same record are environmentaldependencies.

ED=Indicates that the event listed in theSuccessor/Predecessor (RELEASEn) fields is anenvironmental dependency. Unlike the E entry, EDdefines only one environmental dependency, but it alsogives the ability to specify a retry count, retry interval,and an argument to pass to the environmentaldependency.

NODE=Indicates the GSS node name (up to 16 characters) ofthe executing node for the named event.

+Indicates that events listed in the Successor/Predecessor(RELEASEn) fields of the same record are successors.

-Indicates that events listed in the Successor/Predecessor(RELEASEn) fields of the same record are predecessors.

=Defines a conditional predecessor relationship for theevents listed in the Successor/Predecessor (RELEASEn)fields. They become predecessors only if they arealready on the current schedule when the primary event(EVENTNM) is added.

EMAIL=Specifies that this referback replaces completely, for thisjob, any values that are specified on an @EMAIL= globalforward.

EMAIL+Specifies to add the values specified in this keyword tothe values that are specified on the @EMAIL= globalforward. If no @EMAIL= was specified, only the valuesin the EMAIL+ referback are used.

FLOWSTART=Specifies the names of CPM (Critical Path Monitoring)flows for which this event is the starting point.

FLOWEND=Specifies the names of CPM (Critical Path Monitoring)flows for which this event is the ending point.


Record Format

PRIORITY=Specifies the priority for each job submitted. The priorityis used to control job submission by submitting jobs withthe highest priority first. The value specified must be anumeric value between 0 and 100. 0 is the highestpriority, and 100 is the lowest priority. If not specified,the default is 100.

REPORT=Allows the Unicenter Service Desk reporting to be turnedon or off for this job.

SCHENV=This parameter is specified on the job definition andapplies to one specific job. This value takes precedenceover both the global startup parameter and the groupSCL parameter. NO can be specified for this value toindicate no SCHENV= value be inserted on this job'sJOB statement. This parameter has no default. If notfound, the value is obtained from the @SCHENV= SCLparameter or the SCHENV= startup parameter.

Successor/Predecessor

The following describes the Successor/Predecessor SCL field:

SCL HeadingRELEASEn

Columns26 - 57

DescriptionDefines the successors, predecessors, alternate member name, andenvironmental dependencies (see “Referback” on page 121) for theevent.

Process Period

The following describes the Process Period SCL field:

SCL HeadingPROCESSP

Columns59 - 68

DescriptionDefines a finite period during which an event can be added to thecurrent schedule (see the process period keywords and the cyclicprocess period keywords for possible entries later in this guide).


Record Format

Conditional Operators

The following describes the Conditional Operators SCL field:

SCL HeadingO

Column69

DescriptionDefines logical relationships among process periods of different SCLrecords. Possible entries:

+Establishes AND logical relationship within a continuationrecord

/Establishes OR logical relationship within a continuationrecord

XEstablishes EXCEPT logical relationship within acontinuation record

REstablishes REPLACE logical relationship with thefollowing SCL EVENT DEFINITION

Predecessor Count

The Predecessor Count (P) field should not be used or needed. This field isused to support legacy schedules.

Data Set Count

The following describes the Data Set Count SCL field:

SCL HeadingD

Column71

DescriptionDefines the number of data sets that must be created to trigger theevent. The entry must be a single numeral (0-9).


Record Format

Maximum Condition Code

The following describes the Maximum Condition Code SCL field:

SCL HeadingCCDE

Columns72 - 75

DescriptionDefines the maximum condition code value allowed for any step inthe event. The entry must be a four-digit number (0000-4095). Alldummy job events are set to 0000. REXX IMOD events are set tothe code returned by the REXX IMOD.

Location ID

The following describes the Location ID SCL field:

SCL HeadingLOC

Columns76 - 78

DescriptionDefines a location ID to be assigned to the event. The entry must bea three-digit number (000-254).

Version Number

The following describes the Version Number SCL field:

SCL HeadingVV

Columns79 - 80

DescriptionDefines a specific version number to be assigned to the event. Theentry must be a two-digit number (01-99). Default is 01.


Chapter 4. Process Period Keywords

The process period for an event can use these keywords.

Chapter 4. Process Period Keywords 127

Keywords

Keywords

These are the process period keywords.

+!eventnameEligible only if the event specified is not on the current schedule.

+eventnameEligible only if the event specified is on the current schedule.

{mm|**}/{dd|**}/{yy|**}Eligible only on the specified absolute or generic date. Use the formatspecified in your global options--American (mmddyy) or International(ddmmyy).

Replace mm with a two-digit number (01-12) specifying a month. Replacedd with a two-digit number (01-31) specifying a day of the month. Replaceyy with a two-digit number (00-99) specifying a year. Using ** (twoasterisks) in any part of the date creates a generic date.

Examples

�2/2�/�6

(American) Eligible on February 20, 2006, only.

15/��/��

(International) Eligible on the 15th day of any month during any year.

@!eventnameEligible only if the event specified is not on the current schedule in anoncompleted status.

@eventnameEligible only if the event specified is on the current schedule in anoncompleted status (that is, waiting, executing, and so on).

=MTWTFSSEligible for scheduling any day specified by the positional charactersM(onday), T(uesday), W(ednesday), T(hursday), F(riday), S(aturday), andS(unday). Any day on which the event should not be scheduled must bereplaced by a . (period).

Examples

=M.W.F..

Eligible any Monday, Wednesday, or Friday.

=....F..

Eligible on Fridays only.

DAILYEligible for scheduling any day.


Keywords

day#{nn|LAST}Eligible on the nnth occurrence of the specified day during any month.Replace nn with a number 01 through 05 (leading zeros can be omitted), oruse LAST to specify the last occurrence. Replace day with a day of theweek: MON, TUE, WED, THU, FRI, SAT, SUN.

Examples

MON#�1

Eligible on the first Monday of any month.

THU#LAST

Eligible on the last Thursday of any month.

SUN#3

Eligible on the third Sunday of any month.

dayMnEligible on the specified occurrence, calculated from the end of the month,of the specified day. Replace n with a number 1 through 5. Replace daywith a day of the week: MON, TUE, WED, THU, FRI, SAT, SUN.

Examples

MONM2

Eligible the second-to-last Monday of any month.

WEDM3

Eligible the third-to-last Wednesday of any month.

EOMEligible the last workday of any month.

EOYEligible the last workday of the year.

EVnday(x)Eligible every nth weekday (day) of the year, starting with the xthoccurrence of the weekday. Replace n with a numeral 1-9. Replace daywith a day of the week: MON, TUE, WED, THU, FRI. Replace x with anumeral 1-9.

Examples

EV3FRI(1)

Eligible every third Friday starting with the first Friday of the year.

EV5MON(5)

Eligible every fifth Monday starting with the fifth Monday of the year.

Note: You must adjust this process period every year.

FOMEligible the first workday of any month.


Keywords

FRIDAYEligible on Fridays only.

LASTDAYEligible the last physical day of the month (including Saturdays andSundays).

MONDAYEligible on Mondays only.

QTRnEligible the first WORKDAY of the quarter specified by n. Replace n with anumber 1-4, where:

QTR1 is the quarter beginning the first WORKDAY in January

QTR2 is the quarter beginning the first WORKDAY in April

QTR3 is the quarter beginning the first WORKDAY in July

QTR4 is the quarter beginning the first WORKDAY in October

QTRnAEligible any day during the quarter specified by n. Replace n with a number1-4, where:

QTR1A is the quarter beginning January 1.

QTR2A is the quarter beginning April 1.

QTR3A is the quarter beginning July 1.

QTR4A is the quarter beginning October 1.

SATURDAYEligible on Saturdays only.

SUNDAYEligible on Sundays only.

THURSDAYEligible on Thursdays only.

TUESDAYEligible on Tuesdays only.

UDEFxEligible on dates specified by the matching UDEFx parameter in the sameSCL member (where the character x in the process period keywordmatches the x in the parameter).

WEDNESDAYEligible on Wednesdays only.


Keywords

WEEKDAY#LEligible the last workday of the week that is not a holiday. This processperiod considers a workweek to be Monday through Friday. For workweeksthat include Saturday or Sunday, see the WEEKDAY#LW process period.

Usually this is going to be Friday. If Friday is a holiday, however, the lastworkday of the week would be Thursday.

WEEKDAY#LWEligible the last workday of the week that is not a holiday. This processperiod considers a workweek to be Monday through Sunday. Forworkweeks that do not include Saturday or Sunday, see the WEEKDAY#Lprocess period.

Usually this is Sunday. If Sunday is a holiday, however, the last workday ofthe week would be Saturday.

Note: If SAT and SUN are holidays (specified in SYS CYCS), SAT isweekday 6, and SUN is weekday 7.

WEEKDAY#nEligible on the workday of the week specified by n (1-7). During a weekwith no holidays, weekday 1 is Monday, 2 is Tuesday, 3 is Wednesday, 4 isThursday, 5 is Friday, 6 is Saturday, 7 is Sunday. During a week with aholiday, weekday 1 is the first day that is not a holiday, 2 is the second daythat is not a holiday, and so on.

Example

WEEKDAY#4

Eligible any Thursday.


WEEKDAYXnEligible all workdays of the week except the numeric day of the weekspecified by n (1-7). During a week with no holidays, weekday 1 is Monday,2 is Tuesday, 3 is Wednesday, 4 is Thursday, 5 is Friday, 6 is Saturday, 7is Sunday. During a week with a holiday, weekday 1 is the first day that isnot a holiday, 2 is the second day that is not a holiday, and so on.

Example

WEEKDAYX4

Eligible any day except weekday number 4. If no holidays occur during theweek, weekday 4 is Thursday and the event is eligible Monday, Tuesday,Wednesday, and Friday. If, however, Tuesday were a holiday, weekdaynumber 4 would be Friday and the event would be eligible Monday,Wednesday, and Thursday.



Keywords

WEEKYR{>|<}nnEligible any day of any week of the year after (>) or before (<) the weekspecified by nn (01-54). You can omit leading zeros.

Example

WEEKYR>5�

Eligible any day of the last two weeks of the year starting on either JAN 1or DEC 31.

WEEKYR#nnEligible any day during the week of the year specified by nn (01-54) startingon JAN 1. You can omit leading zeros.

Example

WEEKYR#�3

Eligible any day during the 3rd week of the year.

WEEKYRXnnEligible any day except during the week of the year specified by nn (01-54).You can omit leading zeros.

Example

WEEKYRX�2

Eligible any day of the year except during the 2nd week of the year startingon JAN 1.

WORKDAY{>|<}nnEligible on any workday of the month after (>) or before (<) the workdayspecified by nn (where nn is a two-digit number 01-31).

Example

WORKDAY>15

Eligible any workday after the 15th workday of the month.

WORKDAY#nnEligible on the nnth workday of any month (where nn is a two-digit number01-31).

Examples

WORKDAY#2�

Eligible on the 20th workday of any month (not the 20th day of the month,since Saturdays, Sundays, and holidays are not workdays).

WORKDAY#�3

Eligible on the third workday of any month.


Keywords

WORKDAYMnnEligible on the nnth workday of the month, calculated from the end of themonth (where nn is a two-digit number 01-31).

Example

WORKDAYM�5

Eligible the fifth-to-last workday of any month.

WORKDAYSEligible on any workday, excluding Saturdays, Sundays, and holidays.

WORKDAYXnnEligible on any workday (Monday through Friday, excluding holidays) exceptthe nnth workday of any month (where nn is a two-digit number 01-31).

Examples

WORKDAYX2�

Eligible any day except the 20th workday of any month.

WORKDAYX�3

Eligible any day except the third workday of any month.

Xday#{nn|LAST}Eligible on any occurrence of the specified day during any month, exceptfor the nnth occurrence of the specified day. Replace nn with a number 01through 05 for the weeks of the month, or use LAST to specify the lastoccurrence. Replace day with a day of the week: MON, TUE, WED, THU,FRI, SAT, SUN. You can omit leading zeros.

Examples

XMON#1

Eligible any Monday except the first Monday of any month.

XTHU#LAST

Eligible any Thursday except the last Thursday of any month.

XEOMEligible every workday except the last workday of any month.

XEOYEligible every workday except the last workday of the year.

XUDEFxNot eligible on dates specified by the matching UDEFx parameter in thesame SCL member (where the character x in the process period keywordmatches the x in the parameter).


Chapter 5. Cyclic Process PeriodKeywords

This chapter discusses the cyclic process period keywords. For moreinformation on how to set up dates, see the chapter "Preparing to Create aSchedule" in the Schedule Creation Guide.

Valid processing cycles span from 2-254 days.

The SYS CYCS panel can hold a maximum of 105 cyclic calendars.

Each location can have a minimum of 2 dates spanning 254 days and amaximum of 14 spanning a minimum of 2 days.

Chapter 5. Cyclic Process Period Keywords 135

CYCDAY{>|<}nn

CYCDAY{>|<}nn

Eligible any workday of the cycle after (>) or before (<) the workday specifiedby nn where nn is 01 to 99. You can omit leading zeros.


CYCDAY#nnn

CYCDAY#nnn

Eligible on the nnnth workday of any processing cycle (where nnn is athree-digit number 001-254).

Examples

This example displays what is eligible on the 10th day of processing cycles.

CYCDAY#�1�

This example displays what is eligible on the 150th day of processing cycles.

CYCDAY#15�


CYCDAYMnnn

CYCDAYMnnn

Eligible on the nnnth workday of the month, calculated from the end of the cycle(where nnn is a three-digit number 001 through 254).

Examples

This example displays what is eligible on the 15th-to-last workday of processingcycles.

CYCDAYM�15

This example displays what is eligible on the second-to-last workday ofprocessing cycles.

CYCDAYM��2


CYCDAYXnn

CYCDAYXnn

Eligible on any workday except the nnth workday of any processing cycle(where nn is a two-digit number 01-99). You can omit leading zeros.

Examples

This example displays what is eligible any workday except the first workday ofprocessing cycles.

CYCDAYX��1

This example displays what is eligible any workday except the 99th workday ofprocessing cycles.

CYCDAYX99


CYCLAST

CYCLAST

Eligible on the last day of any cycle.


CYCLEnn

CYCLEnn

Eligible in the nnth cycle period. If nn has a leading zero, it can be omitted.CYCLE01 through CYCLE14 or CYCLE1 through CYCLE14.

Example

Suppose you have the following cycle periods (cycles 5 to 12 are not shown).

CYCLE1 - 1/3 through 2/16CYCLE2 - 2/17 through 3/9CYCLE3 - 3/1� through 4/21CYCLE4 - 4/22 through 5/4CYCLE13 - 11/�1 through 12/21CYCLE14 - 12/22 through 1/2

March 12 falls in the third cycle period. If today is March 12 and you schedulean event with a process period of CYCLE03 or CYCLE3, it would be scheduledfor today. CYCLE04 would not schedule for today.


dayCYC#{n|L}

dayCYC#{n|L}

Eligible on the nth occurrence of the specified day during any processing cycle.Replace n with a number 1-5 (5 week cycle maximum), or use L to specify thelast occurrence. Replace day with a day of the week: MON, TUE, WED, THU,FRI, SAT, SUN.

Examples

This example displays what is eligible on the third Monday of any processingcycle.

MONCYC#3

This example displays what is eligible on the last Friday of any processingcycle.

FRICYC#L


dayCYCMn

dayCYCMn

Eligible on the nth occurrence, calculated from the end of the cycle, of thespecified day. Replace n with a number 1-5 (5 week cycle maximum). Replaceday with a day of the week: MON, TUE, WED, THU, FRI, SAT, SUN.

Examples

This example displays what is eligible on the third-to-last Tuesday of anyprocessing cycle.

TUECYCM3

This example displays what is eligible on the second-to-last Thursday of anyprocessing cycle.

THUCYCM2


WEEK#nn

WEEK#nn

Eligible any day during the week of a cycle specified by nn (01-37). You canomit leading zeros.

Example

This example displays what is eligible any day during the 3rd week of thecurrent cycle.

WEEK#�3 or WEEK#3


WEEKX{>|<}nn

WEEKX{>|<}nn

Eligible any day of any week of a cycle following (>) or preceding (<) the weekspecified by nn (01-37). You can omit leading zeros.

Example

This example displays what is eligible any day of the last two weeks of thecycle.

WEEK>35


WEEKXnn

WEEKXnn

Eligible any day except during the week of a cycle specified by nn (01-37). Youcan omit leading zeros.

Example

This example displays what is eligible any day of the year except during the2nd week of the current cycle.

WEEKX�2 or WEEKX2


XdayCYC#{n|L}

XdayCYC#{n|L}

Eligible on any occurrence of the specified day during any processing period,except for the nth occurrence of the specified day. Replace n with a number 1-5(5 week cycle maximum), or use L to specify the last occurrence. Replace daywith a day of the week: MON, TUE, WED, THU, FRI, SAT, SUN.

Examples

This example displays what is eligible any Monday except the fourth Monday ofany processing cycle.

XMONCYC#4

This example displays what is eligible any Wednesday except the firstWednesday of any processing cycle.

XWEDCYC#1


Chapter 6. SCL Global Control Records

This chapter discusses SCL global control records.

Chapter 6. SCL Global Control Records 149

+TODAY

+TODAY

The +TODAY global control record initiates a test run of the schedule using thespecified date (Julian date, where yy is the year and ddd is the day of the year)as the current date. An asterisk (*) in the Date (DATE) field indicates that youwant to use the current date for the test run. The test run allows scheduletesting and projections of scheduling action for the specified date. No physicalupdates of the current schedule are made. Look at the output of the SCL to seehow the test worked.

This record has the following format:

��─ ──+TODAY= ──┬ ┬─yyddd─ ───────────────────────────────────────────────�� └ ┘─�─────


@BUSGRP

@BUSGRP

The @BUSGRP global control record specifies that the business group nameassigned to subsequent events in the schedule is used until the next@BUSGRP is found in the SCL member.

Note: For more information, see “BUSGRP Command” on page 22.


��─ ──@BUSGRP=name ─────────────────────────────────────────────────────��


@CYCnnn

@CYCnnn

The @CYCnnn global control record specifies that the non-default cycliccalendar with ID nnn be used for events in the schedule that have no locationID coded. This is used until the next @CYCnnn is found in the SCL member.


@CYCnnn=

@CYCnnn=

The @CYCnnn= global control record defines each mmdd (date) to be the startdate of a processing cycle for events in the schedule having a location IDmatching the ID nnn. @CYCnnn only affects the selection of cyclic calendars.It overrides, for cyclic calendars only, the location specified in a previous@SETLOC. This location remains the default location for cyclic calendars untilthe end of the SCL member is reached or until another @CYCnnn or@SETLOC is found in the schedule.


┌ ┐─,──��─ ──@CYCnnn= ───� ┴mmdd ─────────────────────────────────────────────────��

Example

The @CYCnnn= overrides the SYS CYC's location cycles if defined.

@CYC��=�1�1,�2�2,�3�3,�4�4,�5�5,�6�6,�7�7,�8�8,�9�9,1�1�,1111,1212,1225,1228

Note: Commas must separate mmdd, and only 14 are allowed per location.


@DATEFORM

@DATEFORM

The @DATEFORM global control record specifies the date format you want touse. American (A) is in the form mmddyy. The International (I) is in the formddmmyy. The default is American (A).


┌ ┐─A─��─ ──@DATEFORM= ──┴ ┴─I─ ────────────────────────────────────────────────��


@EMAIL

@EMAIL

The @EMAIL global control record specifies an email template that applies toall jobs that follow.


┌ ┐─,──────────────��─ ──@EMAIL= member/SCFRL ───� ┴┬ ┬────────────── ──────────────────────────��

└ ┘──member/SCFRL

memberIndicates the email template member name.

SCFRLSpecifies event flags to indicate the events that will generate an email. Youcan specify one or more of the following codes:

SJob submit.

CJob normal completion or purge.

FJob failure due to abend, condition codes, or delete.

RNormal completion of a rerun. Only valid if F is also specified.

LJob is late submitting.

You can define multiple member/SCFRL definitions with comma separation. Asmany as can fit on an 80-character card image are accepted (five or more).

To stop the email information from applying to jobs, specify the following:

@EMAIL=

This prevents the email assignment for those jobs that follow this statement.


@FLOWnn

@FLOWnn

The @FLOWnn global control record associates events in a schedule with aCPM (Critical Path Monitoring) flow name. The @FLOWnn= keywords can bespecified to define the flow name that should be added to the event'scheckpoint records. Events with a flow name have CAIENF events issued toreport the job status to the CPM monitor.


┌ ┐─,──────────��─ ──@FLOWnn= ───� ┴┬ ┬────────── ─────────────────────────────────────────�� └ ┘──flowname


@HOLnnn

@HOLnnn

The @HOLnnn global control record specifies that the non-default holidaycalendar with ID nnn be used for events in the schedule that have no locationID coded. nnn is a three-digit location ID.


@HOLnnn=

@HOLnnn=

The @HOLnnn= global control record defines each mmdd (date) to be aholiday for events in the schedule having a coded location ID matching the IDnnn. @HOLnnn only affects the selection of holiday calendars. It overrides, forholiday calendars only, the location specified in a previous @SETLOC. Thislocation remains the default location for holiday calendars until the end of theSCL member is reached or until another @HOLnnn or @SETLOC is found inthe schedule.


┌ ┐─,──��─ ──@HOLnnn= ───� ┴mmdd ─────────────────────────────────────────────────��

Example

@HOL��=�1�1,�2�2,�3�3,�4�4,�5�5,�6�6,�7�7,�8�8,�9�9,1�1�,1111,1212,1225,1228

Note: Commas must separate mmdd, and only 14 are allowed per location.

The @HOLnnn= overrides the SYS HOL's location holidays if defined.


@INITIMOD

@INITIMOD

The @INITIMOD global control record specifies that subsequent events should(=YES) or should not (=NO) use the global initiation IMOD. To use this feature,see DYNAMLOC in the Planning and Implementation Guide.


┌ ┐─YES─��─ ──@INITIMOD= ──┴ ┴─NO── ──────────────────────────────────────────────��


@PRIORITY

@PRIORITY

The @PRIORITY global control record specifies the priority for each job thatfollows this statement. The priority is used to control job submission bysubmitting jobs with the highest priority first. The value specified must be anumeric value between 0 and 100. 0 is the highest priority, and 100 is thelowest priority.


┌ ┐─1��─��─ ──@PRIORITY= ──┴ ┴─nnn─ ──────────────────────────────────────────────��


@REPORT=

@REPORT=

The @REPORT= global control record allows the Unicenter Service Deskreporting to be turned on or off for the group of jobs that follow this statement.


┌ ┐─NO──��─ ──@REPORT= ──┴ ┴─YES─ ────────────────────────────────────────────────��

To stop the Report option from applying to jobs, specify the following:

@REPORT=

This prevents the assignment for those jobs that follow this statement. If nokeyword is specified, or @REPORT= is specified without a value, the globalinitialization parameter REPORT=YES|NO determines the setting on this option.


@RERUN

@RERUN

The @RERUN global control record defines the date (Julian date, where yy isthe year and ddd is the numerical day of the year) to be used as the currentdate for a rerun of the schedule.


��─ ──@RERUN=yyddd ─────────────────────────────────────────────────────��


@SCHENV

@SCHENV

The @SCHENV global control record specifies the value to be inserted on theSCHENV= JOB statement parameter for a job or a group of jobs and takesprecedence over the SCHENV= startup parameter. The value specified appliesuntil a new value is specified or until a null value is specified. NO can bespecified to disallow insertion of the SCHENV= parameter on the JOBstatement for the job or group of jobs. This parameter has no default. If thisparameter is omitted, the value specified on the SCHENV= startup parameterwill be used. Before using this feature, see the chapter "Using the IBMWorkload Management (WLM) Scheduling" in the Extended SchedulingServices Guide.


@SETLOC

@SETLOC

The @SETLOC global control record specifies that the location ID nnn beassigned to subsequent events in the schedule. @SETLOC sets the locationfor all functions, including calendar selection. An @SETLOC overrides any@HOLnnn or @CYCnnn that precedes it. This location remains the defaultlocation until the end of the SCL member is reached or until another @SETLOCis found in the schedule.


��─ ──@SETLOC=nnn ──────────────────────────────────────────────────────��


@TODAY

@TODAY

The @TODAY global control record forces the calendar resolution to the datedefined by yyddd (Julian date, where yy is the year and ddd is the numericalday of the year). Events are added to the current schedule as if the datespecified were the current date.


��─ ──@TODAY=yyddd ─────────────────────────────────────────────────────��


@TRACE

@TRACE

The @TRACE global control record displays hexadecimal representation ofschedule records from the checkpoint. This record is used for diagnosticpurposes only.


@WDnnn

@WDnnn

The @WDnnn global control record overrides the location zero workdaycalculations. Use it to add Saturday or Sunday or both to locations other thanzero. Replace nnn with the location ID of the location you want to affect.


��─ ──@WDnnn= ──┬ ┬─SAT──── ──────────────────────────────────────────────�� ├ ┤─SUN──── ├ ┤─SATSUN─ └ ┘─MTWTF──


@WORKD

@WORKD

The @WORKD global control record resets the workdays parameter for location000 to include Saturday (@WORKD=SAT), Sunday (@WORKD=SUN), orSaturday and Sunday (@WORKD=SATSUN), or returns the workdaysparameter to Monday through Friday (@WORKD=MTWTF).


��─ ──@WORKD= ──┬ ┬─SAT──── ──────────────────────────────────────────────�� ├ ┤─SUN──── ├ ┤─SATSUN─ └ ┘─MTWTF──


UDEFn

UDEFn

The UDEFn global control record defines unique process period dates forevents having process period keyword UDEFn (where n in the process periodkeyword matches the n in this parameter). Replace mmdd with the date to bedefined as the process period. Replace processp with the name you want toassign to the process period.


┌ ┐─,───────────��─ ──UDEFn= ───� ┴mmdd=processp ──────────────────────────────────────────��


Chapter 7. Dependency CodeDescriptions

The following are the Unicenter CA-Jobtrac dependency code descriptions:

AAbend bypass. If an event with this code abends, the predecessordependency (code P) is removed from successors to the event. This doesnot apply to condition code, catalog, or JCL errors.

DData set required dependency. One or more data sets must be suppliedbefore the event can execute.

EEdit JCL dependency. The job's JCL must be edited before job issubmitted. The code must be removed manually after the JCL is edited.

HAutomatic hold dependency. The event is being held from submissiondue to some type of threshold crossover. The Current Event Stat field onthe Scheduled Event Display panel can indicate the reason for the hold.The code must be removed manually before the event can be submitted.

IEnvironmental dependency. All environmental dependencies mustcomplete normally without abend before the event can be submitted.

JJCL required dependency. JCL must be supplied or altered before theevent can execute. This code must be manually removed or JCL must beexternally submitted using the AUTO-SCHD feature.

JWWLM resource dependency. The WLM resource specified for this eventmust be valid and available before this event can execute. The code mustbe removed manually after the WLM resource is verified and/or activated.

MManual release dependency. The code must be removed manuallybefore the event can be submitted. If the event has manual actions, theymust be performed before the event is submitted.

OOutput release dependency. This code indicates that the event outputshould be checked after the event completes. No successors to the eventcan run until the O code is manually removed.

Chapter 7. Dependency Code Descriptions 171

PPredecessor event dependency. All predecessor events must completenormally without abend and without exceeding the maximum allowable stepcondition code before the event can be submitted.

QQueued release dependency. The event's JCL is to be submitted outsideof Unicenter CA-Jobtrac. Once JCL is submitted, the event is held in theJES queue and released automatically by Unicenter CA-Jobtrac whenremaining dependencies are met. The Q entry is not valid for REXX IMODand dummy job events.

RResource dependency. Indicates that user-defined resource conditionsmust be satisfied before the event can be submitted.

XMutual exclusion dependency. The event is defined to be mutuallyexclusive with an event that is currently executing. When the executingevent completes, the code is removed by Unicenter CA-Jobtrac and theevent is eligible for submission.

*AUTOAUTO-SCHD event. The event was submitted outside the control ofUnicenter CA-Jobtrac and therefore has no dependencies or overrides thatcan be honored by Unicenter CA-Jobtrac.

?View documentation dependency. Prevents submission of the event untilits documentation is viewed. The code must be removed manually after thedocumentation is viewed.


52500629 Jobtrac Reference Summ ENU

Documents

Transcript of 52500629 Jobtrac Reference Summ ENU