Ca 7

CONTROL-M®
for OS/390 and z/OS

CA-7 Conversion Guide
Supporting
CONTROL-M for OS/390 and z/OS Version 6.1.00
January 28, 2004

Contacting BMC Software
You can access the BMC Software Web site at http://www.bmc.com. From this Web site, you can obtain information
about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada Outside United States and Canada
Address BMC Software, Inc. Telephone (01) 713 918 8800
2101 CityWest Blvd.
Houston TX 77042-2827 Fax (01) 713 918 8000
Telephone 713 918 8800 or
800 841 2031
Fax 713 918 8000
Copyright 2004 BMC Software, Inc. All rights reserved.

BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks
or trademarks of BMC Software, Inc.
IBM is a registered trademark of International Business Machines Corporation.
DB2 is a registered trademark of International Business Machines Corporation.
All other trademarks belong to their respective companies.
BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this
information is subject to the terms and conditions of the applicable End User License Agreement for the product and the
proprietary and restricted rights notices included in this documentation.
Restricted Rights Legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE
COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the
U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS
252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is
BMC Software, Inc., 2101 CityWest Blvd., Houston, TX 77042-2827, USA. Any contract notices should be sent to this
address.
Support Web Site
You can obtain technical support from BMC Software 24 hours a day, 7 days a week at
http://www.bmc.com/support_home. From this Web site, you can
■ read overviews about support services and programs that BMC Software offers
■ find the most current information about BMC Software products
■ search a database for problems similar to yours and possible solutions
■ order or download product documentation
■ report a problem or ask a question
■ subscribe to receive e-mail notices when new product versions are released
■ find worldwide BMC Software support center locations and contact information, including e-mail addresses, fax
numbers, and telephone numbers
Support by Telephone or E-mail

In the United States and Canada, if you need technical support and do not have access to the Web, call 800 537 1813.
Outside the United States and Canada, please contact your local support center for assistance. To find telephone and
e-mail contact information for the BMC Software support center that services your location, refer to the Contact Customer
Support section of the Support page on the BMC Software Web site at http://www.bmc.com/support_home.
Before Contacting BMC Software

Before you contact BMC Software, have the following information available so that Customer Support can begin working
on your problem immediately:
■ product information
— product name
— product version (release number)
— license number and password (trial or permanent)
■ operating system and environment information
— machine type
— operating system type, version, and service pack or other maintenance level such as PUT or PTF
— system hardware configuration
— serial numbers
— related software (database, application, and communication) including type, version, and service pack or
maintenance level
■ sequence of events leading to the problem
■ commands and options that you used
■ messages received (and the time and date that you received them)
— product error messages
— messages from the operating system, such as file system full
— messages from related software
3
4 CONTROL-M for OS/390 and z/OS CA-7 Conversion Guide
Contents
About This Guide 11
About the Conversion Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Conventions Used in This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Chapter 1 Conceptual Overview 19

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Application Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Job Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Job Triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Job Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Prose Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Virtual Resource Management (VRM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
CONTROL-M Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
CONTROL-M/Restart Automated Rerun and Restart Processing . . . . . . . . . . . . 26
CONTROL-M Scheduling Table Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Production Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Production Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
New Day Processing and Schedule Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
DEMAND[H] and POST Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Workload Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
JCL Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Special Override Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
CA-DRIVER Procedures and JCL Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Network Communications Facility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
CONTROL-M Event Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Chapter 2 Conversion Process Flow 39

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
JOB0 - Produce the CA-7 LJOB, LSCHD, Base Calendar and Job-to-Resource Reports
42
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
JOB1 - Produce the updated CA-7 LJOB Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Contents 5
Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Input. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
JOB2 - Create the Applications List, Calendar Libraries, and Calendar Names List
Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Input. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
JOB3 - Create CONTROL-M Scheduling Tables and CMEM Rules . . . . . . . . . . . . . . 50
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Input. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
JOB4 - Convert JCL Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Input. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
JOB5 - Convert Virtual Resource Management Components . . . . . . . . . . . . . . . . . . . . 61
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Input. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
JOB6 - Update CONTROL-M Scheduling Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
JOB7 Create CONTROL-M Group Scheduling Tables . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Input. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
JOB8 - Convert CA-DRIVER Procedures and JCL Libraries (Optional). . . . . . . . . . . . 66
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Input. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Chapter 3 Conversion Steps 69

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Pre-Conversion Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Step 1 - Create the Conversion SOURCE and LOAD Libraries . . . . . . . . . . . . . . . . . . 72
Step 2 - Copy CA-7 and CA-11 JCL and CA-DRIVER Libraries and Initdeck . . . . . . 73
Step 3 - Modify and Run the JOB0 Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Step 4 - Modify Parameters in the DEFAULTS Member . . . . . . . . . . . . . . . . . . . . . . . . 75
Step 5 - Modify and Run the ASMLINK Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Step 6 - Modify and Run the JOB1 Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Step 10 - Modify and Run the JOB5 Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Step 12 - Modify and Run the JOB8 Member (Optional) . . . . . . . . . . . . . . . . . . . . . . . . 84
Step 13 - Customize CONTROL-M and Install User Exits . . . . . . . . . . . . . . . . . . . . . . 85
Step 14 - Final Adjustments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Step 15 - Check Conversion Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Step 16 - Customize the New Day Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Chapter 4 Conversion Details 91

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Component Conversion Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Component Conversion Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
1. JOB and MEMBER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
2. JCLID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
3. SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4. JCL-OVRD and # JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
5. VERIFY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
6. MAINT and # MNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
7. HOLD and DEMAND[H] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
8. EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
9. PRTY, # RES and DEMAND[H] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
10. COND-CODE, RO and # SCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
11. TYPE1 and TYPE2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
12. CLASS, # RES and DEMAND[H] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
13. SCAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
14. ROLL, INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
15. SBTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
16. DOTM and LDTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
17. Scheduling Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
18. Job Triggering and # NTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
19. DEP-JOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
20. DEP-JOB=/jobname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
21. DSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
22. NWK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
23. USER REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
24. PROSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
25. Virtual Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
26. # JI, # JO, and # JEND, # XI, # XO, and # XEND Statements . . . . . . . . . . . . . . . 117
27. JCL Job Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
28. DEMAND[H] and POST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
29. CA-11 Non-Restartable Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
30. INSERT-RMS and //*CA-11 Comment Statements . . . . . . . . . . . . . . . . . . . . 122
31. CA-11 U11RMS Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
32. NXTCYC SET-OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
33. RESCHNG and # RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
34. This item number is not currently in use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
35. OWNER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
36. SCHID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
37. JCL Initialization Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
38. SHOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
39. CMEM Rule Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
40. MAINID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
41. INITR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
42. JES ROUTE PRINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Contents 7
43. This item number is not currently in use.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
44. DEP-JOB=? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
45. DONT SCHEDULE BEFORE/AFTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
46. # HLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
47. # NOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
48. # MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
49. # VER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
51. DPROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
52. (D)STEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
53. (D)GOTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
54. (D)SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
55. (D)IF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
56. DATA, DEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
57. (D)NEST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
58. (D)ABORT/DFLUSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
59. Variable Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
60. Date Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
61. Attribute Functions (L’, T’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Unique CONTROL-M Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
CATEGORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
DO SYSOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
MAXWAIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Appendix A Conversion Parameters 143
Appendix B Messages 163
Appendix C Planning The Conversion 183

1: Organize the Conversion Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
2: Analyze Your Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
3: Consider Current Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
4: Read the Conversion Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Appendix D The CTMUTIL Conversion Utility 191
Appendix E Interfaces With Related Products 193
Appendix F Problem Reporting 195
Index 197

Tables
Information in CMEM Rule for DATASET Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Primary Jobs in the Conversion Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
JOB2 Control Statements Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
JOB2 Scheduling Table Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
JOB2 Base Calendar Name List Record Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
JOB3 JCL Job Class Translation Table Record Layout . . . . . . . . . . . . . . . . . . . . . . . . . . 53
JOB3 CPUID Translation Table Record Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Divided LIbraries Produced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Parameters to Be Adjusted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Components of the CA-7 Job Definition Screen (JOB) . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Components of the CA-7 Job Scheduling Screen (SCHD, JOB) . . . . . . . . . . . . . . . . . . 94
Components of the CA-7 Job Triggering Screen (SCHD, JTRG) . . . . . . . . . . . . . . . . . 94
Components of the CA-7 Dataset Triggering Screen (SCHD, DTRG) . . . . . . . . . . . . 94
Components of the CA-7 Job Predecessor/Successor Screens (JOBCONN) . . . . . . . 94
Components of the CA-7 Documentation Screens (PROSE) . . . . . . . . . . . . . . . . . . . . 95
Components of the CA-7 Commands Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Components of the CA-7 Virtual Resource Management Screen (RM/RSRC) . . . . . 95
Components of the CA-7 Modification to Resolved Schedule Dates Screen . . . . . . . 95
Components of the CA-7 or CA-11 JCL Parameter, Statement, or Step . . . . . . . . . . . 96
Components of the CA-7 or CA-11 Initialization File Statement . . . . . . . . . . . . . . . 96
Components of the CA-7 CALENDAR Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Components of CA-7 Workload Balancing Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
CA-DRIVER Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
CA-7 $SCC Conversion Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Scheduling Information Conversion Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Occasions for SHOUT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Supported CA-DRIVER Reserved-Name Variables . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Site Date Format Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Supported CA-DRIVER Date Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Supported CA-DRIVER Attribute Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Conversion Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
CA-DRIVER Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Tables 9
About This Guide
This conversion guide reviews basic concepts relevant to converting from CA-7 and
CA-11 to CONTROL-M and CONTROL-M/Restart, and provides step-by-step
instructions on how to use the CA-7 to CONTROL-M conversion tool.
The guide is divided into the following chapters:
Chapter 1 – Conceptual Overview
Overview of basic concepts relating to conversion from CA-7 and CA-11 to

CONTROL-M, CONTROL-M/Restart, and CMEM, the CONTROL-M Event
Manager
Chapter 2 – Conversion Process Flow
Description and details of the conversion process batch jobs
Chapter 3 – Conversion Steps
Step-by-step procedure for installing and operating the conversion tool
Chapter 4 – Conversion Details
Description of relevant CA-7 and CA-11 fields in relation to corresponding

CONTROL-M parameters
Appendix A – Conversion Parameters
Various parameters for the conversion process
Appendix B – Messages
Messages and codes of the conversion process
Appendix C – Planning the Conversion
Advance planning before carrying out the conversion
About This Guide 11

About the Conversion Tool
Appendix D – Conversion Utility CTMUTIL
Description of the CTMUTIL program, which may be useful during and after the
conversion process
Appendix E – Interfaces With Related Products
List of various product interfaces supported by the conversion
Appendix F – Problem Reporting
Instructions on reporting problems to BMC Software Customer Support
Index
About the Conversion Tool

The conversion consists of a sequence of batch jobs. Although these jobs run
independently of CA-7, CA-11, and CONTROL-M, CONTROL-M must be installed to
perform the conversion.
The conversion tool performs the following functions:
■ builds CONTROL-M scheduling tables based on CA-7 database definitions and

CA-7 and CA-11 JCL override statements
■ builds all necessary CONTROL-M calendars
■ builds CONTROL-M CMEM Rule Table definitions based on CA-7 data set
triggering events
■ converts CA-7 (scheduled) override statements, Batch Terminal Steps, and CA-11
U11RMS Steps in JCL libraries to CONTROL-M format
■ converts CA-DRIVER libraries to CONTROL-M format
■ enables customers to automatically set unique CONTROL-M options in the

scheduling tables
■ provides a set of independent utilities that can be very useful during and after the
conversion process
■ issues messages about problems and errors encountered in the CA-7 definitions

Conventions Used in This Guide
The conversion tool is delivered in source format. If special requirements exist, the
conversion tool can be tailored locally.

Notational conventions that may be used in this guide are explained below.
Standard Keyboard Keys
Keys that appear on the standard keyboard are identified in boldface, for example,
Enter, Shift, Ctrl+S (a key combination), or Ctrl S (a key sequence).
WARNING
The commands, instructions, procedures, and syntax illustrated in this guide
presume that the keyboards at your site are mapped in accordance with the EBCDIC
character set. Certain special characters are referred to in this documentation, and
you must ensure that your keyboard enables you to generate accurate EBCDIC hex
codes. This is particularly true on keyboards that have been adapted to show local or
national symbols. You should verify that
$ is mapped to x'5B'
# is mapped to x'7B'
@ is mapped to x'7C'
If you have any questions about whether your keyboard is properly mapped,
contact your system administrator.
Preconfigured PFKeys
Many commands are preconfigured to specific keys or key combinations. This is

particularly true with regard to numbered PF keys, or pairs of numbered PFKeys. For
example, the END command is preconfigured to, and indicated as, PF03/PF15. To
execute the END command, press either the PF03 key or the PF15 key.
Instructions to enter commands may include
■ only the name of the command, such as, enter the END command
■ only the PF keys, such as, press PF03/PF15
■ or both, such as, press PF03/PF15, or enter the END command
About This Guide 13

Command Lines and Option Fields
Most screens contain a command line, which is primarily used to identify a single
field where commands, or options, or both, are to be entered. These fields are usually
designated COMMAND, but they are occasionally identified as COMMAND/OPT or
COMMAND/OPTION.
Option field headings appear in many screens. These headings sometimes appear in
the screen examples as OPTION, or OPT, or O.
Names of Commands, Fields, Files, Functions, Jobs, Libraries, Members,

Missions, Options, Parameters, Reports, Subparameters, and Users
The names of commands, fields, functions, jobs, libraries, members, missions,

options, parameters, reports, subparameters, users, and most files, are shown in
standard UPPERCASE font.
User Entries
In situations where you are instructed to enter characters using the keyboard, the
specific characters to be entered are shown in this UPPERCASE BOLD text, for
example, type EXITNAME.
Syntax statements
In syntax, the following additional conventions apply:
■ A vertical bar ( | ) separating items indicates that you must choose one item. In the
following example, you would choose a, b, or c:
a | b| c
■ An ellipsis ( . . . ) indicates that you can repeat the preceding item or items as many
times as necessary.
■ Square brackets ( [ ] ) around an item indicate that the item is optional. If square
brackets ( [ ] ) are around a group of items, this indicates that the item is optional,
and you may choose to implement any single item in the group. Square brackets
can open ( [ ) and close ( ] ) on the same line of text, or may begin on one line of text
and end, with the choices being stacked, one or more lines later.
■ Braces ({ }) around a group of items indicates that the item is mandatory, and you
must choose to implement a single item in the group. Braces can open ( { ) and
close ( } ) on the same line of text, or may begin on one line of text and end, with the
choices being stacked, one or more lines later.

Screen Characters
All syntax, operating system terms, and literal examples are

presented in this typeface. This includes JCL calls, code examples, control
statements, and system messages. Examples of this are:
■ calls, such as
CALL ’CBLTDLI’
■ code examples, such as
FOR TABLE owner.name USE option, . . . ;
■ control statements, such as
//PRDSYSIN DD * USERLOAD PRD(2) PRINT
■ system messages, both stand-alone, such as You are not logged on to

database database_name, and those embedded in text, such as the message
You are not logged on to database database_name, are displayed on
the screen.
Variables
Variables are identified with italic text. Examples of this are:
■ In syntax or message text, such as

Specify database database_name
■ In regular text, such as
replace database database_name1 with database database_name2 for the current
session
■ In a version number, such as
EXTENDED BUFFER MANAGER for IMS 4.1.xx
Special elements
This book includes special elements called notes and warnings:
NOTE
Notes provide additional information about the current subject.
About This Guide 15

Related Publications
WARNING
Warnings alert you to situations that can cause problems, such as loss of data, if you
do not follow instructions carefully.
CONTROL-D User Guide
A complete guide to CONTROL-D features, options and implementation.
CONTROL-M for OS/390 and z/OS User Guide
A complete guide to CONTROL-M features, options and implementation.
CONTROL-M/Restart User Guide
A complete guide to the features, options and implementation of

CONTROL-M/Restart.
INCONTROL for OS/390 and z/OS Administrator Guide
Information for system administrators about customizing and maintaining

INCONTROL products.
INCONTROL for OS/390 and z/OS Installation Guide
A step-by-step guide to installing INCONTROL products using the INCONTROL

Installation and Customization Engine (ICE) application.
INCONTROL for OS/390 and z/OS Messages Manual
A comprehensive listing and explanation of all IOA and INCONTROL messages and
codes.
INCONTROL for OS/390 and z/OS Security Guide
A step-by-step guide to implementing security in INCONTROL products using the

ICE application.

INCONTROL for OS/390 and z/OS Utilities Guide
Describes utilities designed to perform specific administrative tasks that are available
to INCONTROL products.
In addition to the foregoing, the following publications may also be of assistance:
■ Computer Associates International publications:
— CA-7 Database Maintenance Guide

— CA-7 Management Reporting Guide
— CA-7 Production User Guide
— CA-7 Systems Programmer Guide
— CA-7 System User Guide
— CA-7/NCF User Guide
— CA-7/RPT User Guide
— CA-11 Systems Programmer Guide
— CA-11 User Guide
■ IBM publications:
— JCL Reference
— System Codes
— System Messages (Volumes 1-5)
— Linkage Editor and Loader
— Using Datasets
— Utilities
— Assembler H Language Reference
— Assembler H Programmers Guide
About This Guide 17


Chapter
1 Conceptual Overview
This chapter includes the following topics:
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Application Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Job Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Job Triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Job Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Prose Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Virtual Resource Management (VRM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
CONTROL-M Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
CONTROL-M/Restart Automated Rerun and Restart Processing . . . . . . . . . . . . 26
CONTROL-M Scheduling Table Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Production Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Production Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
New Day Processing and Schedule Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
DEMAND[H] and POST Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Workload Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
JCL Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Special Override Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
CA-DRIVER Procedures and JCL Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Network Communications Facility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
CONTROL-M Event Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Overview
Overview
This conceptual overview is intended for production control personnel who are
familiar with CA-7 and CONTROL-M terminology.
The CA-7 to CONTROL-M conversion tool is provided by BMC Software to assist in

the creation of the primary product elements for CONTROL-M. It is designed to
expedite the conversion process by automatically translating the most commonly
built CA-7 scheduling elements into functionally equivalent processes in
CONTROL-M.
The following issues are described in this chapter:
■ Application Definition
Logic used by the conversion tool for converting components of CA-7 application
definitions to corresponding CONTROL-M components
■ CONTROL-M Calendar Creation

Logic used by the conversion tool for creating CONTROL-M calendars
■ CONTROL-M/Restart Automated Rerun and Restart Processing

Logic used by the conversion tool for automating rerun and restart processing as
provided by CONTROL-M/Restart
■ CONTROL-M Scheduling Table Creation

Logic used by the conversion tool for creating CONTROL-M scheduling tables
■ Production Control
Issues important to daily production management, such as the New Day
procedure, on-demand and temporary job scheduling, and workload balancing
■ CONTROL-M Event Manager

Logic used by the conversion tool for creating CONTROL-M CMEM rules
■ JCL Processing
Logic used by the conversion tool to convert CA-7 and CA-11 scheduled JCL
override statements and steps, as well as JES statements, to CONTROL-M format.
CONTROL-M support for the CA-7 Special Override library is also described.
■ CA-DRIVER
Logic used by the conversion tool to convert the CA-DRIVER components used to
automate JCL and control card setup
■ Network Communication Facility

Describes CONTROL-M standard and extended NJE job tracking support

Application Definition
■ Customization
Describes additional methods of customizing the conversion
In CA-7, defining an application requires the use of numerous definition screens.
These screens include:
■ the Job Definition (JOB) screen, used to define data related to CPU jobs
■ the Job Scheduling (SCHD, JOB) screen, used to define the scheduling information
of a job
■ the Job Triggering (SCHD, JTRG) screen, used to define jobs that trigger other jobs
■ the Dataset Triggering (SCHD, DTRG) screen, used to define data set events that
trigger jobs
■ the Job Predecessor/Successor Triggering (JOBCONN) screen, used to define job

connections (prerequisites)
■ the CPU Job Documentation (PROSE) screen, used to enter job-level

documentation
■ the Modification To Resolved Schedule Dates screen
■ the Virtual Resource Management (RM) screen
In addition, numerous other components are required to complete the application

definition. These include:
■ a CALENDAR Macro to define CA-7 Base calendars
■ Workload Balancing macros to dynamically balance CPU work based on

user-defined processing objectives
■ the CA-7 Initialization file
■ a User Option Table macro to define CA-11 requirement s

Under CONTROL-M, all comparable definitions are handled using:
■ the Job Scheduling Definition screen (Screen 2)

■ the IOA Conditions/Resources screen (Screen 4)
■ the IOA Calendar facility (Screen 8)
■ the CONTROL-M Event Manager (CMEM) (Screen C)
Each component of the CA-7 application definition is discussed in the following

pages in relation to the management of corresponding components under
CONTROL-M.
Job Definition
In CA-7, job definition is performed using the Job Definition (JOB) screen that
contains information relevant to a specific job. Each job definition is a separate entity
in the CA-7 database. CA-7 job definitions can specify JCL member names that differ
from the name of the job. CA-7 forces the submitted job name to match the name of
the defined job.
In CONTROL-M, job information, such as scheduling criteria, runtime criteria, and so

on, is stored in job scheduling definitions, and in Group Entities for Group scheduled
jobs. Job scheduling definitions and Group Entities are defined using the Job
Scheduling Definition screen, and are stored in partitioned data sets (PDSs) called
scheduling table libraries. In CONTROL-M, job control is independent of the job
name in the JCL JOB statement. CONTROL-M controls the job using the JCL member
name, which is specified in the MEMNAME parameter of the CONTROL-M job
scheduling definition. For more information, see “1. JOB and MEMBER” on page 98
and “2. JCLID” on page 99.
In CONTROL-M, application job grouping is performed by defining, in one Group

scheduling table, all related CA-7 jobs, that is, all jobs that have a triggering
relationship.
Scheduling
In CA-7, after application jobs are defined as described in the preceding section,
scheduling information is specified using the CPU Job Scheduling Parameter Edit
(SCHD,JOB) screen. The schedule is determined by the first job of the application,
referred to as the “head-of-tree” job. The remainder of the application jobs are
associated with the head-of-tree job by means of “triggering,” which is discussed in
the following section.

A CA-7 scheduled job can be defined with a number of different schedule IDs. Each
schedule ID can define different scheduling dates, execution environments, sets of
jobs, JCL statements, and so on.
In CONTROL-M, jobs can be scheduled individually or can be included in a Group

schedule. A job can be defined in several scheduling tables, or several times in the
same scheduling table, with different scheduling criteria in each job scheduling
definition.
The conversion tool creates a Group scheduling table for each CA-7 job grouping.
The Group Entity in the Group scheduling table is used to define sets of basic
scheduling criteria to be applied to a Group of job scheduling definitions. Each set of
basic scheduling criteria in the Group Entity is assigned a unique label, specified in
the SCHEDULE TAG parameter, which is used for referencing that set of criteria. For
more information, including details regarding the SCHEDULE TAG parameter, see
“36. SCHID” on page 125. For more information on Group scheduling, see the
CONTROL-M for OS/390 and z/OS User Guide.
Job Triggering
In CA-7, job triggering is usually performed after the schedule IDs are defined, as
described in the preceding section. Triggering defines the execution sequence of the
application jobs. The CA-7 Job Triggering (SCHD,JTRG) screen is used to define a list
of triggered jobs for a specific job. Job triggering can be limited to a specific
schedule ID. SCHID=000 means that the triggered job is initiated by a job with any
schedule ID. By default, the schedule ID of a job is passed to the triggered job unless
otherwise specified in the TRGID parameter.
In CONTROL-M, the execution sequence is controlled by means of “prerequisite

conditions.” A prerequisite condition is a descriptive name given to a certain
situation, event, or condition. The prerequisite condition is the basic mechanism used
by CONTROL-M to control job execution flow.
In CONTROL-M terminology, an IN condition is specified for a job when the job

must wait for the occurrence of an event. A condition can be added to the IOA
Conditions file when an event occurs, such as job completion. Conditions can be
added or deleted after successful job completion, based on user specification, using
the OUT statement of the job scheduling definition. For more information about
prerequisite condition concepts, see the CONTROL-M for OS/390 and z/OS User Guide.
Conditions are entities in their own right, since they are not related to specific jobs. A
condition exists after it is added, and does not exist after it is deleted. When a
condition is added, that condition is satisfied for all jobs specifying it as an IN
condition. Conditions can be listed, added and deleted using the IOA Conditions
screen (Screen 4).

Each prerequisite condition is associated with a specific scheduling date. This

scheduling date is used to differentiate between different runs of the same job for
different scheduling dates.
CONTROL-M identifies conditions in the system that must be confirmed manually

by operations personnel. These conditions are called manual conditions. Addition
and deletion of manual conditions is performed in the IOA Manual Conditions screen
(Screen 7).
The conversion tool converts CA-7 job triggering, starting from the head-of-tree job,
into CONTROL-M IN and OUT conditions, to establish the same application tree
structure. The conversion tool takes into account the CA-7 schedule ID, as shown in
the SCHID parameter, and the Triggering schedule ID, as shown in the TRGID
parameter, when building an application tree structure that it converts to a
CONTROL-M scheduling table.
Job Connections
In CA-7, the next stage of an application definition is to define specific job
connections, which are prerequisite conditions, using the Job Predecessor/Successor
(JOBCONN) screens. CA-7 distinguishes between various types of job connections.
For example, a JDEP connection is an automatic dependency between one job and the
completion of another job, while a USR connection is a descriptive text connection
that requires manual operator intervention before the connected job can execute.
In CONTROL-M, job connections are implemented using the same IN and OUT
prerequisite condition mechanism discussed in “Job Triggering” on page 23.
Prose Information
In CA-7, documentation is specified in the documentation (PROSE) screens.
In CONTROL-M, documentation is specified in the Job Scheduling Definition screen.
The conversion tool copies CA-7 PROSE information into a member of a

CONTROL-M documentation library, preparing it for viewing and/or updating in
the Job Scheduling Definition screen.

Virtual Resource Management (VRM)

The Virtual Resource Management facility of CA-7 defines job-to-resource
dependencies that control execution of the job based on resource availability at job
submission time. This is implemented in the RM screen (the RSRC screen in CA-7
release 3.0 and earlier). The resource connected to a job can be a real resource, such as
a data set or a started task, or a virtual resource used by multiple jobs to control job
execution in a required cycle.
This facility provides the following features:
■ resource control at the job, system, or step level

■ job submission control for jobs that use shared or exclusive resources
■ job “corequisite requirements”
■ resource control for physical data sets, virtual data sets, or a group of data sets
In CONTROL-M, virtual resource management is implemented using Control

resources, Quantitative resources, and manual IN conditions that are defined in the
Job Scheduling Definition screen.
If Virtual Resource Management is used at your site, the conversion tool converts the
resource information and places it into CONTROL-M scheduling tables. For more
information, see “JOB5 - Convert Virtual Resource Management Components” on
page 61 and “25. Virtual Resource Management” on page 115
CONTROL-M Calendars
In CA-7, Base calendar definitions must be assembled and link-edited into load
modules. In CONTROL-M, calendar definitions are simply created online using the
IOA Calendar facility (Screen 8).
The CA-7 conversion tool automatically creates CONTROL-M calendars in several

situations:
■ when you specify CA-7 Base calendars in JOB1, as discussed in “Step 3 - Modify
and Run the JOB0 Member” on page 74
■ when a CA-7 job has the SCHDMOD CURRENT indicator set in its scheduling
information
■ when CA-7 job schedule parameters cannot be consistently converted to

CONTROL-M basic scheduling parameters
■ when non-standard, periodic, calendars are converted to standard calendars

Each of these situations is described in detail in “13. SCAL” on page 105.
CONTROL-M/Restart Automated Rerun and Restart Processing

In CA-7, automated rerun and restart job processing is accomplished using an
interface to CA-11, if CA-11 has been installed. CA-7 can automatically insert CA-11
JCL steps into jobs scheduled and submitted by CA-7.
CA-11 performs the typical functions of rerun and restart systems. However, to
realize the full functionality of CA-11, manual modification is required for JCL
members that are to be restarted.
For example, specifying that a job is to be rerun after an abend, or specifying a

specific step name from which a job is to be restarted, requires:
■ manual modification of the JCL of the job, by changing the PARM of the U11RMS
step or inserting a //*CA-11 comment statement, or
■ issuance of online commands (PRE)
In contrast, CONTROL-M/Restart is a fully automated rerun and restart system that

is tightly integrated with CONTROL-M. It normally requires no manual intervention,
unless you specify manual confirmation.
Definition of CONTROL-M/Restart processing is performed by means of parameters

defined in the job scheduling definition for the job. This consolidates and simplifies
the job scheduling and restart process. The following fields in the CONTROL-M Job
Scheduling Definition screen determine the processing to be performed by
CONTROL-M/Restart:
■ DO IFRERUN
■ DO RERUN
■ PREVENT-NCT2
■ AUTO-ARCHIVE, SYSDB, MAXDAYS, and MAXRUNS
In addition, it is possible to override the default CONTROL-M/Restart parameters by

using control parameter members in the library allocated to the DACTRCTL
DD statement of the CONTROLR step. For more information, see the
CONTROL-M/Restart User Guide. One option that many CA-7 conversion sites specify
is NORECAPTABEND, which prevents automatic abend code recapture.
For more information on how CA-11 PARM parameters are converted to

CONTROL-M/Restart parameters, see “31. CA-11 U11RMS Step” on page 123

CONTROL-M Scheduling Table Creation
The CONTROL-M/Restart Simulation facility, which corresponds to the CA-11

PSEUDO=YES processing option, enables you to see what actions will be taken by
CONTROL-M/Restart without actually performing a restart.
CONTROL-M/Restart also has an interface with a Tape Management System similar

to the CA-11/CA-1 or the CA-11/CA-DYNAM/CA-TLMS interface. For more
information, see the CONTROL-M/Restart User Guide, and the CTRX001 sample Exit
in the IOA SAMPEXIT library.
CONTROL-M Scheduling Table Creation

The conversion tool builds a CONTROL-M scheduling table for every CA-7 job
grouping, incorporating all the jobs of the application. Each scheduling table contains
all jobs that are triggered by any job from that application and all jobs that are
demanded by the JCL of the application jobs.
The conversion tool searches the CA-7 LJOB report for head-of-tree jobs, and tracks
the triggering data in order to build the entire application job tree. A head-of-tree job
is either
■ a job that is scheduled, that is, a job that contains scheduling information, or
■ a job that is not scheduled or triggered by another job
If a head-of-tree job is scheduled, the tree of this job is called a scheduled tree.
Otherwise, it is called an independent tree, usually defined in CA-7 for special
purpose or on-demand execution. These trees can contain one or more jobs based on
triggering information. All CA-7 job trees are converted to CONTROL-M Group
scheduling tables with the head-of-tree job name assigned to the CONTROL-M
scheduling table.
NOTE
The conversion tool does not necessarily place the converted jobs into the job
scheduling table in alphabetical order. An on-line CONTROL-M SORT command can
be used to sort jobs in scheduling tables if necessary.

Production Control
Production Control
In CA-7, numerous online transactions are required to achieve production control.
These transactions access CA-7 queues in order to assist in tracking and controlling
the daily production environment. Example transaction types include:
■ the LQ transaction and its subsets, used to track production jobs
■ the XQ transaction, used to change production control parameters, such as posting

a prerequisite condition
■ the FSTRUC transaction, used to forecast job flow structures
Under CONTROL-M, production tracking and control is performed using one screen
– the Active Environment screen (Screen 3).
Production Management
CA-7 manages production jobs using a set of queue files. When a production job is to
be executed, it is loaded into the Request Queue where its prerequisites are handled.
After all prerequisite conditions are satisfied, the job is moved to the Ready Queue
where it waits to be submitted for execution based on physical resource availability,
such as initiator, tape drives, and priority. When job execution starts, the job is moved
to the Active Queue where CA-7 monitors its execution. Additional CA-7 queues
manage statistics, JCL decks, and so on.
In CONTROL-M, production tracking and control is managed using a single file, the
Active Jobs file (AJF). When a job is scheduled or FORCEd (demanded),
CONTROL-M loads its definition to the AJF. The AJF is then used to track and control
the life cycle of the job. Access to the AJF is provided using the Active Environment
screen (Screen 3), which enables you to monitor, track, and control the entire life cycle
of a job. Using this screen, you can see the status of the job, “hold” the job in order to
modify its definition, “free” the job for execution, view the sysout of the job, browse
the Log information relating to the job, display predecessor and successor job chains
and network dependencies, perform deadline scheduling tasks, and carry on a
variety of other activities.
New Day Processing and Schedule Scan

CONTROL-M production jobs are scheduled using New Day processing, which is
performed once each day at a predefined time, according to your local site
requirements. CONTROL-M, using New Day processing, presumes that workdays
do not always begin at the start of a calendar day. Instead, CONTROL-M enables you

Production Control
to define a logical workday that begins at a specified time. Other scheduling

products, such as CA-7, begin every workday at the first moment of a new calendar
day. The CA-7 schedule scan process scans the database looking for production jobs
that require scheduling during the next interval. These jobs are then added to the
Request Queue. CA-7 schedules the jobs based on the job scheduling definition and
on the machine date, which changes at midnight. The CONTROL-M CA-7 conversion
tool is designed to convert CA-7 scheduling data so it can be used in CONTROL-M
scheduling.
The following example illustrates how the CA-7 scheduling method is converted to
the CONTROL-M scheduling method.
Figure 1 New Day Processing Example
The above example assumes that your logical business date changes at 8:00 A.M. You
want to take a job scheduled in CA-7 to begin at 4:00 A.M. on March 15th, and convert
it to be run as a CONTROL-M job. The conversion tool converts this CA-7 job to a
CONTROL-M job that begins at 4:00 A.M. on the March 14th logical business day.
NOTE
CONTROL-M enables you to define logical workdays that begin at a time best suited
to the scheduling requirements of your organization, without being subject to the
limits that might be imposed by strict adherence to calendar days.
The conversion tool handles this difference automatically. For more information, see
“Step 13 - Customize CONTROL-M and Install User Exits” on page 85

Production Control
DEMAND[H] and POST Commands

In CA-7, non-recurring jobs are requested using the DEMAND[H] command. The
prerequisites of the job can be manually satisfied using the CA-7 POST command.
Both of these commands are executable in the CA-7 online environment and in batch
mode.
In batch mode, DEMANDs and POSTs are executed in order to control production
flow based on prior step condition codes or any other user requirement. CA-7
provides JCL procedures such as SASSTRLR for this function. The batch mode can
also be executed from within batch jobs or started tasks that are not controlled by
CA-7.
In CONTROL-M, the FORCE (F) line command in Screen 2 operates similarly to the
CA-7 DEMAND command. The CONTROL-M ADD COND command in Screen 4 is
comparable to the CA-7 POST command. These two CONTROL-M commands can be
executed in the CONTROL-M online environment as well as in batch mode. In batch
mode, CONTROL-M provides the CTMJOB and IOACND utilities to order or force
jobs and add conditions for which other jobs are waiting.
The conversion tool converts DEMAND[H] commands differently, based on the

&DEMAND conversion parameter. For more information on choosing an appropriate
demand ‘mode’, see “&DEMAND” on page 148 and for more information on
conversion details, see “28. DEMAND[H] and POST” on page 120.
The conversion tool converts POST commands in a CA-7 Batch Terminal Step to a
CONTROL-M step containing an ADD COND, with a condition name based on the
POST type. For more information, in particular on DEPJOB, NW (network), and USR
type POST condition names, see “19. DEP-JOB” on page 112, “22. NWK” on page 114,
and “23. USER REQUIREMENTS” on page 114.
If the DEMAND[H] command specifies the DEPJOB parameter, which identifies a

single predecessor job that must complete execution before the demanded job can
start, the conversion tool creates an additional IN condition, of the job-connection
type, in the CONTROL-M job scheduling definition created for incorporating the
demanded job.
For more information on the format of IN and OUT conditions related to the
DEMAND[H] and POST commands, see “19. DEP-JOB” on page 112.

Production Control
Workload Balancing
In CA-7, the Workload Balancing facility dynamically balances CPU work based on
user-defined processing objectives. The Workload Balancing facility analyzes jobs
awaiting execution, and sets priorities for jobs submitted based on the following
criteria:
■ job start times

■ CPU usage
■ tape drive usage
■ initiators and job class structure
■ threshold priorities
In CONTROL-M, maximizing throughput is achieved through the specification of

Quantitative resources (using the RESOURCE job definition parameter and the
CONTROL-M Resources file), job priority, and the CTMRELRS utility. In addition,
you can implement the Dynamic Tape Drive Quantity Adjustment feature, using the
AUTOTAPE parameter in the CTMPARM member in the IOA PARM library.
The conversion tool converts the following CA-7 Workload Balancing entities to
CONTROL-M RESOURCE and PRIORITY parameters:
■ initiators
■ class barriers
■ class and priority specified in the CA-7 JCL # RES override statement
■ class and priority specified in the CA-7 DEMAND[H] command
■ tape drives, class, and priority specified in the CA-7 Job Definition screen
Tape drives, class, and priority specifications coded in the CA-7 Job Definition screen
serve as initial Workload Balancing values. These initial values can be overridden by
values specified in
■ the RESCHNG command

■ the # RES JCL override statement
■ the DEMAND[H] command
Tape drives specified in CA-7 JCL batch RESCHNG commands and # RES override
statements are converted to input parameters for the CTMRELRS utility, to change
Quantitative resources.
The RESCHNG command and the # RES JCL override statement are discussed in
“Command RESCHNG and # RES JCL Override Statement” on page 32.

Production Control
Class Barriers
CA-7 Class Barriers establish the maximum number of jobs that can be submitted
concurrently in an associated job class. For more information on how class barriers
are converted to CONTROL-M Resources, see “12. CLASS, # RES and DEMAND[H]”
on page 104.
Command RESCHNG and #RES JCL Override Statement

You can use the CA-7 RESCHNG command and the # RES JCL override statement to
free tape drives that are no longer required. When the Workload Balancing facility
schedules jobs, the high-water mark for tape drives is reserved until job completion,
unless this command is used. Using the RESCHNG command, you can insert the
Trailer Step into the job after the maximum number of tape drives is no longer
needed.
In CONTROL-M, the CTMRELRS utility provides comparable functionality. The

CA-7 # RES JCL override statement and the RESCHNG command step are converted
to a CONTROL-M CTMRELRS step containing a CHANGE RESOURCE
resource-name quantity command. This command changes the number of
resource-name resources allocated to the job to the quantity specified. For
information on the two CA-7 tape drive devices that can be controlled using this
utility, see “&TAPE1” on page 158 and “&TAPE2” on page 158, and for more details
see “33. RESCHNG and # RES” on page 124.
DEMAND[H] Commands
You can also use the DEMAND[H] command to change the high-water Workload
Balancing resource requirements of a job. For more information, see Table 11 on
page 94.
Changing Workload Balancing Objectives

In CA-7, you can establish multiple Workload Balancing Environments to properly
balance processing objectives. This is done by creating multiple load modules
containing the processing objectives defined by the Workload Balancing macros.
The criteria defined by the Workload Balancing macro create a virtual configuration
for CA-7 to manage. A job that executes a specific Workload Balancing module is
then scheduled whenever the corresponding processing objective is required.
In CONTROL-M, the corresponding process of changing the resource environment

configuration is done by simply scheduling a job that executes the IOACND utility,
using the CHANGE RESOURCE statement.
For example, the CA-7 Workload Balancing module contains the following macros:

Production Control
WLBPDEF MODNAME=xxx
TAPE1 NAME=TAPE1,MXTAL=25
TAPE2 NAME=TAPE2,MXTAL=15
INITR TOTAV=10
CLBARR BARA=5,BARB=1,BAR2=3
WLBEND
These correspond to the following CONTROL-M IOACND utility statements:
CHANGE RESOURCE TAPE1 25

CHANGE RESOURCE TAPE2 15
CHANGE RESOURCE INITIATOR 10 (using default &INIT value)
CHANGE RESOURCE CLASS_BAR_A 5
CHANGE RESOURCE CLASS_BAR_B 1
CHANGE RESOURCE CLASS_BAR_2 3
NOTE
You can use CONTROL-M Exit CTMX004 to assign weights to Quantitative
resources, to fine-tune the scheduling algorithm.
All resources referenced by a CHANGE RESOURCE statement must already

exist in the CONTROL-M Resources file.
The CA-7 /WLB command can be similarly converted to a CHANGE

RESOURCE statement.
A summary of available CA-7 resources is provided by the CA-7 LWLB

command.
JCL Considerations
CA-7 provides the capability to specify special scheduled JCL override statements.
These override statements enable you to perform the following functions:
■ modify workload balancing resource requirements

■ define step-level condition code checking criteria
■ set various types of manual requirements
■ make runs non-executable
■ turn off job triggering
■ send messages at job submission time
■ dynamically tailor run-stream contents based on schedule ID, date, and time

Production Control
These functions are specified by the CA-7 JCL # statements and are converted to
CONTROL-M AutoEdit statements, job scheduling definition parameters, or
CONTROL-M batch utilities. For more information on how each of these statements
is converted, see the component conversion summary in Chapter 4, “Conversion
Details.”
In addition, CA-7 commands can also be included in JCL Batch Terminal steps. For
details of how they are converted, see “DEMAND[H] and POST Commands” on
page 30, and “Command RESCHNG and # RES JCL Override Statement” on page 32.
If you are also converting from CA-11, the CA-11 U11RMS JCL steps and comment
statements are analyzed for restart and rerun information. These steps and statements
are incorporated into CONTROL-M/Restart Job Scheduling parameters. For more
information, see “31. CA-11 U11RMS Step” on page 123.
Standard JES JCL statements such as ROUTE PRINT are also processed by the
conversion tool. For more information, see “42. JES ROUTE PRINT” on page 130.
Special Override Library

CA-7 supports a JCL override library that is intended to handle one-time temporary
JCL changes. This library is specified in the CA-7 Initialization file as INDEX=254
(JCLID 254) and its use is indicated by setting the USE-OVRD-LIB field in the DB.1
Job Definition Screen to Y. After the job is successfully executed, the JCL is deleted
from the Special Override library.
You can obtain the same functionality in CONTROL-M using the CTMIMACI REXX
procedure in the IOA CLIST library.
Using the CTMIMAC1 procedure, JCL is dynamically copied from the MEMLIB
library to the CONTROL-M OVERLIB library, if no member by that name already
exists, and is then edited using option J in the CONTROL-M Status screen (Screen 3).
If the rerun of the job ended OK, the JCL member can optionally be deleted from the
OVERLIB library by the DELOVRER CONTROL-M installation parameter, which
performs the function formerly provided by CONTROL-M Exit CTMX015O.
For more information and installation instructions, see the following:
■ the discussion of the OVERLIB parameter in the CONTROL-M for OS/390 and z/OS
User Guide
■ the discussion of the DELOVRER parameter in the CONTROL-M chapter of the

INCONTROL for OS/390 and z/OS Installation Guide
■ the CTMIMACx source members in the IOA CLIST library.

Production Control
CA-DRIVER Procedures and JCL Libraries

CA-DRIVER is an optional component of CA-7 that can be used to automate the JCL.
In CONTROL-M, the JCL Setup and AutoEdit facility is used to automate the changes
to the JCL prior to the job submission. The AutoEdit facility consists of a simple
language that, once included into the job stream, eliminates the need to change the
JCL again.
The conversion tool converts each CA-DRIVER procedure definition into a

CONTROL-M AutoEdit statement. In addition, JCL libraries and date functions are
converted from CA-DRIVER format to CONTROL-M format.
The conversion tool scans CA-7 JCL libraries for members containing either of the
following JCL statements:
// EXEC procname
// EXEC PROC=procname
When these statements are encountered, the conversion tool searches the converted
CA-DRIVER procedure library for a member name matching the procname (procedure
name). If the member name is found in the converted procedure library, the EXEC
card is replaced with CONTROL-M AutoEdit %%INCLIB and %%INCMEM control
statements that copy the converted procedure member to the current job stream.
If the member name is not found in the converted procedure library, the EXEC card
remains unchanged.
For more information, see Table 24 on page 103.
Network Communications Facility

CA-7/NCF, an optional feature of CA-7, enables jobs submitted by CA-7 to execute at
any site within a network of sites as if the site was a local CPU. CA-7/NCF ensures
that the CA-7 that submitted a job receives the necessary SMF feedback data to track
the job, regardless of which site processed the job.
NJE support in CONTROL-M is a standard feature, and involves setting up the

standard JES and VTAM node definitions. CONTROL-M Extended NJE job tracking
provides the ability to detect and display the real-time status of CONTROL-M
controlled NJE jobs, by setting to Y the ENHNJE parameter in the CTMPARM
member in the IOA PARM library.

Production Control
In addition to the previously described standard and extended support provided by

CONTROL-M, the conversion tool converts the CA-7 MAINID parameter. This
parameter is used to specify a CPU from which JES can transmit a job to the proper
remote node. The conversion tool provides a sample exit that inserts one of the
following into the JCL stream of the job:
■ a JES2 /*JOBPARM SYSAFF statement

■ a JES3 //*MAIN SYSTEM statement
For more information, see “40. MAINID” on page 129 and Step 14(5) in Chapter 3,
“Conversion Steps.”
CONTROL-M Event Manager

In CA-7, data set and output activity can be used to trigger jobs. Whenever a data set
is created or updated, jobs can be triggered by the completion of an activity. In
CONTROL-M, the corresponding facility is the CONTROL-M Event Manager
(CMEM) Rule Definition facility that manages external events, which are events
occurring outside the direct control of CONTROL-M. CMEM performs predefined
actions in response to the occurrence of events in the system. Data set triggers are
equivalent to CMEM DATASET events, that is, the setting of data set disposition at
deallocation time during step termination or dynamic deallocation.
When the CA-7 Dataset Triggering screen (DB.2.6) shows that a CA-7 data set trigger
event is occurring, the conversion tool creates a CMEM rule for the DATASET event
with the following information:
Table 1 Information in CMEM Rule for DATASET Event

Item Description
DSN=data_set_name Data set that causes the triggering event.
JOBNAME=* Indication that all jobs and started tasks are to be
monitored for the event.
DISP=ALL Any of the following dispositions of the data set trigger
the event: CATLG, UNCATLG, KEEP, DELETE, RETAIN
(SMS), SCRATCH (SMS).
ACTION=DO COND Upon the occurrence of the event, CONTROL-M adds a
prerequisite condition. The condition name is in the form
@dsn where dsn is the first 19 characters of the data set
name.
DATE=ODAT CONTROL-M working date associated with the added
condition.

Production Control
The action is performed at the end of the step in which the event occurs only if the
step completes successfully.
The conditions added by the CMEM facility correspond to IN conditions created by

the conversion in jobs that require these data sets as prerequisites.
NOTE
For CMEM to monitor DATASET events for a job or started task, the JOB card in the
JCL of the job or started task must contain the MSGLEVEL=(1,1) parameter, and the
IEF403I or IEF125I message must appear in the Job log.
For additional information regarding the CMEM facility, see the CONTROL-M for
OS/390 and z/OS User Guide.
Customization
To customize the way in which the conversion process operates, consider using the
following options:
■ the conversion parameters described in Appendix A, “Conversion Parameters”
■ the CTMTBUPD CONTROL-M utility, which performs post-conversion mass

updates on Job Scheduling Table parameters

Production Control

Chapter
2 Conversion Process Flow

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
42
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
JOB1 - Produce the updated CA-7 LJOB Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
JOB2 - Create the Applications List, Calendar Libraries, and Calendar Names List
Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
JOB3 - Create CONTROL-M Scheduling Tables and CMEM Rules . . . . . . . . . . . . . . 50
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
JOB4 - Convert JCL Members. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
JOB5 - Convert Virtual Resource Management Components . . . . . . . . . . . . . . . . . . . 61
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
JOB6 - Update CONTROL-M Scheduling Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
JOB7. Create CONTROL-M Group Scheduling Tables . . . . . . . . . . . . . . . . . . . . . . . . . 64
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
JOB8 - Convert CA-DRIVER Procedures and JCL Libraries (Optional). . . . . . . . . . . . 66
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Input. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Overview
Overview
This chapter describes in detail the components of the conversion process from the
perspective of jobs, programs, and data sets. A familiarity with the conversion
process will help you understand the conversion logic and the installation and
operation steps discussed in Chapter 3, “Conversion Steps.”
The process is comprised of the following primary jobs:
Table 2 Primary Jobs in the Conversion Process

Job Description
JOB0 Produces the CA-7 LJOB, LSCHD, Base Calendar, and Job-to-Resource
Cross Reference reports
JOB1 Produces the updated CA-7 LJOB report
JOB2 Creates the Applications list, CONTROL-M Calendar library, and
Calendar Names List files
JOB3 Creates intermediate CONTROL-M scheduling table library and CMEM
rules
JOB4 Converts JCL members
JOB5 Converts resource management components
JOB6 Updates the CONTROL-M scheduling tables (optional)
JOB7 Converts the CONTROL-M scheduling tables created in JOB3 to Group
Scheduling format
JOB8 Converts CA-DRIVER procedure and JCL libraries
These jobs are described in detail on the following pages.

JOB0 - Produce the CA-7 LJOB, LSCHD, Base

Calendar and Job-to-Resource Reports
Description
JOB0 produces the CA-7 LJOB, LSCHD, Base Calendar, and Job-to-Resource Cross
Reference reports, and writes the reports to disk for subsequent use.
JOB0 utilizes the CA-7 Batch Terminal mechanism.
This job may require several hours for processing, due to the manner in which CA-7
communicates with Batch Terminals.
Input
The following commands are executed to obtain the information needed by the
conversion tool:
1. The CA-7 command LJOB,JOB=*,LIST=NODD is used to retrieve job and

scheduling information from the CA-7 database.
NOTE
For CA-7 Release 2.9 and earlier, specify LIST=ALL instead of LIST=NODD.
2. The CA-7 command LSCHD,JOB=*,LIST=BYSID is used to retrieve scheduling

information from the CA-7 database. If you set the value of JOB to anything other
than * (Asterisk), the value you choose must exactly match that used in the CA-7
LJOB command (immediately above).
3. The CA-7 PRINT commands are used to retrieve Base calendar information from
the CA-7 database.
Use one PRINT command for each CA-7 Base calendar identified in the CALBLK
statement of the CA-7 Initialization file. The form of the command is
PRINT,YEAR=yy,SCAL=xx

where
■ yy is the year of the calendar

■ xx are the last two characters of the CA-7 calendar name
NOTE
Multiple PRINT statements can be specified for the same calendar, each for a
different year. In addition, CA-7 Base calendars can be non-standard periodic
calendars.
4. For CA-7 Release 3.0 or earlier, if the CA-7 Virtual Resource Management facility is
installed, the LXRSC command must be used to produce the Job-to-Resource Cross
Reference report.
For CA-7 Release 3.1 and later, the commands RM.2 followed by
LIST,RM.2,RSRC=* are used to produce this report.
Output
1. The LJOB report file
Default file name: CTM.CA7.REPORT
File characteristics: sequential; record length 133; block size 23408
2. The LSCHD report file

Default file name: CTM.CA7.SCHED
3. The Base Calendar report file

Default file name: CTM.CA7.BASECAL
4. The Job-to-Resource Cross Reference report file

Default file name: CTM.CA7.RESOURCE

JOB1 - Produce the updated CA-7 LJOB Report
Description
JOB1 produces an updated CA-7 LJOB report and writes the report to disk for
subsequent use.
Parameters
The number of jobs contained in the LJOB report must be specified in the JCL PARM
parameter of the EXEC statement of STEP5 in this job. This value must be equal to, or
greater than, the number of jobs to be processed.
NOTE
The REGION parameter must be set to 0K in the EXEC statement. Because
approximately 1.5 KB of virtual storage above-the-line is required by the program for
each job in the LJOB report, the user must ensure that this job is not limited by the
amount of above-the-line storage available to it (such as when using the IEFUSI SMF
exit).
Input
1. The LJOB report file created by JOB0
2. The CA-7 Initdeck Initialization File statements
The CA-7 Initdeck Initialization File is described on page 51.
NOTE
For performance reasons, any JCL libraries that do not contain DEMAND
commands should be removed from this file for the duration of JOB1 only. For
details of these commands, see “28. DEMAND[H] and POST” on page 120.

Output
1. The updated LJOB report file.
Default file name: CTM.CA7.LJOBO
2. List of the jobs that require auxiliary calendars.

Default file name: CTM.CA7.JOBSCH

JOB2 - Create the Applications List, Calendar Libraries, and Calendar Names List Files
JOB2 - Create the Applications List, Calendar

Libraries, and Calendar Names List Files
Description
JOB2 reads the LJOB report file created by JOB1 and produces a list of all defined
head-of-tree job names that are used as a basis for CONTROL-M scheduling table
names.
JOB2 reads the LSCHD and Base Calendar reports created by JOB1, and produces the
CONTROL-M Calendar library and the Calendar Names List file. For more
information, see “CONTROL-M Calendars” on page 25.
The Calendar Names List file is used in JOB3 to assign calendar names to the
CONTROL-M DCAL scheduling parameter when any of the following events occur:
■ SCHDMOD CURRENT processing is requested

■ inconsistencies exist between CA-7 scheduling definitions and CONTROL-M basic
scheduling parameters
■ non-standard CA-7 calendars are converted to standard CONTROL-M calendars
Input
1. The LJOB report file created by JOB1
2. The LSCHD report file created by JOB0
3. The Base Calendar report file created by JOB0
4. List of jobs requiring an auxiliary calendar created by JOB1
5. The non-standard (Periodic) Base Calendar definitions

This user-defined SYSIN file specifies the beginning and ending days of the
non-standard (periodic) months for each periodic calendar produced in the Base
Calendar report. The format of the control statements is shown in Table 3.

Table 3 JOB2 Control Statements Format

Position Description
01–48 Twelve pairs of 2-digit beginning and ending days for each of
the twelve non-standard months in the calendar.
50–51 Calendar name (that is, the xx portion of SCALyyxx).
Example
For calendar AA, B01=25, E01=23, B02=26, E02=21, B03=23, E03=29, and so on.
Column: ----1----2----3----4----5----6
Code: //SYSIN DD *
252326212329... AA
NOTE
For non-standard calendars, if the gap between the first day of two consecutive,
non-standard calendar months exceeds a regular calendar month, the non-standard
calendars must be manually converted. However, a dummy entry must still be made
in the SYSIN file for this calendar.
Output
1. The Message Report file
2. The Applications List file

This contains a list of CA-7 head-of-tree job names with corresponding
CONTROL-M scheduling table names to be assigned.
Default file name: CTM.CA7.APPLS
Record Layout
Table 4 JOB2 Scheduling Table Layout (Part 1 of 2)

Column Description
01–08 CA-7 head-of-tree job name.
11–13 CA-7 schedule ID. 000 indicates an independent or special
purpose job.
16–23 Intermediate CONTROL-M scheduling table name.

Table 4 JOB2 Scheduling Table Layout (Part 2 of 2)

Column Description
41–48 The CONTROL-M scheduling table name. By default, this is
the head-of-tree job name.
51–58 The CA-7 system name.
61 Indicates whether the head-of-tree is scheduled.
Valid values are:
■ ' ' (Blank) – the head-of-tree is scheduled
■ X – the head-of-tree is not scheduled.

65 Whether SCHDMOD CURRENT calendar processing is
manual or automatic.
The SCHDMOD CURRENT indicator is globally set by the

&SCHDMOD conversion parameter. You can individually
set the SCHDMOD CURRENT indicator for each
scheduled application by editing column 65 of this file.
Valid values are:
■ Y (Yes) – processing is automatic

Some job scheduling information is modified for all jobs in
the application for which a SCHDMOD CURRENT
calendar has been created, as described in “13. SCAL” on
page 105.
■ N (No) – processing is manual

The original job scheduling information is retained in the
job scheduling definition.
An editor can be used to modify only the scheduling table names (columns 41
through 48), and the SCHDMOD CURRENT indicator. When editing, it is
important to ensure that the scheduling table names remain unique, valid PDS
member names.
WARNING
Do not delete any records from this file.

3. The CONTROL-M Calendar library containing the Base calendars and Auxiliary
CONTROL-M calendars, including SCHDMOD CURRENT calendars
Default library name: CTM.V600.CALENDAR
Library characteristics: PDS; record length 80; block size 3120
The format of Auxiliary calendar names is xynnnnnn,
where
■ x is ,T,...,Z
■ y is A-Z
■ nnnnnn is CA-7 DSNBR, the database schedule member number that was
assigned to the schedule when it was added to the CA-7 database
For more information on Auxiliary calendars, see “13. SCAL” on page 105.
4. The Calendar Names List file containing a list of calendar names and related
information, sorted by job name, schedule ID, and system name
Default file name: CTM.V600.CALNAMES
This file is for internal system use only. Do not modify it.
5. The SCHDYONLY and Periodic Base Calendar Name List file

This contains a list of all CA-7 calendar names that were created with OPTION set
to SCHDYONLY, using the CA-7 CALENDAR macro, or that are defined as
nonstandard in the SYSIN file.
Default file name: CTM.V600.DACALS

For more information, see Item 4 in “Input” on page 46.
Record Layout
Table 5 JOB2 Base Calendar Name List Record Layout

Column Description
01–08 CA-7 Base Calendar name.
09 P if a non-standard (Periodic) calendar.
10 Reserved for future use.
This file is automatically created by the conversion tool.

JOB3 - Create CONTROL-M Scheduling Tables and CMEM Rules
JOB3 - Create CONTROL-M Scheduling Tables

and CMEM Rules
Description
JOB3 does the following:
■ reads the LJOB report file created by JOB1
For every CA-7 job, JOB3 extracts all information relevant to the conversion.
The JCL member for each job is read in order to process CA-7 or JCL override
control statements that may affect the scheduling process, such as JCL job class,
DEMAND[H], and # SCC.
■ creates intermediate CONTROL-M scheduling tables
JOB3 also produces a cross-reference file that contains all converted CA-7 job
names and associated CONTROL-M scheduling table names.
■ creates a CMEM rules table for jobs triggered by DATASET events
JOB3 activates the CTMCA702 program. The source code for this program resides
in the conversion SOURCE library, and can be tailored locally.
NOTE
The CTMCA706 program is called to scan the CA-7 JCL members. Local modification
may be required if the DEMAND[H] statement is not used in the standard CA-7
manner.
Parameters
The number of jobs contained in the LJOB report must be specified in the JCL PARM
parameter of the EXEC statement of STEP2 in this job. This value must be equal to, or
greater than, the number of jobs to be processed.

NOTE
The REGION parameter in the EXEC statement must be set to 0K. Because
approximately 1.5 KB of virtual storage above-the-line is required by the program for
each job in the LJOB report, the user must ensure that this job is not limited by the
amount of above-the-line storage available to it (such as when using SMF exit
IEFUSI).
Input
1. The LJOB report file (created by JOB1)
2. The Applications List file (created by JOB2)
3. The SCHDYONLY and Periodic Base Calendar Name file (created by JOB2)
4. CA-7 Initdeck Initialization File statements

These are used for several purposes:
A. The conversion tool determines which JCL libraries to access using the
following Initialization File statement:
JCL,DSN=dsname,INDEX=nnn[,ALT=mmm]
where dsname must reference the data set names of the copies of the JCL
libraries. For more information, see “Step 2 - Copy CA-7 and CA-11 JCL and
CA-DRIVER Libraries and Initdeck” on page 73.
If no JCL library names are found in the CA-7 Initdeck, JCL library processing is
bypassed. The copied JCL libraries must be cataloged.
CA-7 jobs are contained within specific JCL libraries. The library names are used
in specifying the CONTROL-M MEMLIB parameter, as described in “2. JCLID”
on page 99. When converting job definitions of jobs in libraries with many
members, you may be able to improve performance by avoiding mass
allocations and deallocations. You can do so by programming the conversion
tool to specify GENERAL as the value of the MEMLIB parameter, rather than
the CA-7 JCL library name.
To do this, you should change the Initialization File statement in relation to each
of these JCL libraries, by doing the following, in order:
■ Instead of the statement set out at the beginning of this section, use the
following statement:
JCL,DSN=dsname,INDEX=nnn[,ALT=mmm],GENERAL

■ Code a DALIB DD statement in the CONTROL-M procedure.
■ Concatenate all these JCL libraries in the DALIB DD statement.
For information about on-line considerations, see the description of the

MEMLIB parameter in the parameters chapter of the CONTROL-M for OS/390
and z/OS User Guide.
B. The conversion tool determines which job entry subsystem (JES) is in use at the
site using the following Initialization File statement:
CPU, HOST=JESn,...
where n is 2 or 3
C. The conversion tool obtains information on CA-11 using the following

Initialization File statement
RESTART,RMS=xxx,PROCRMS=procname,STEPRMS=stepname,
PARMRMS=parm
For details on how these parameters are utilized, see
■ “31. CA-11 U11RMS Step” on page 123

■ “&PRVNCT2” on page 155
■ “&CTR” on page 144
5. Dynamically allocated CA-7 and CA-11 JCL libraries (derived from the CA-7
Initdeck Initialization File statements), used to process CA-7 and/or CA-11 control
statements
6. Calendar Name List file (created by JOB2)
7. JCL Job Class Translation Table containing a list of all JCL job classes for which
Quantitative resource statements are to be created
This file is only needed if the JCL job classes in the JOB statement are to be
converted into CONTROL-M Quantitative resources. For more information, see
“&JOBCLAS” on page 152.
The table must be a card-image (LRECL=80) or in-stream file.
The layout of each record in the Job Class Translation Table is as set out in Table 6.

Table 6 JOB3 JCL Job Class Translation Table Record Layout

Column Description
01 JCL job class. For more information, see “Table 7JOB3 CPUID
Translation Table Record Layout” on page 53.
02 Generic resource name indicator
Valid values are:
■ ' ' (Blank)
■ $ (Dollar sign)
For more information, see “Table 7JOB3 CPUID Translation

Table Record Layout” on page 53.
03 – 11 User-specified text to be used as the CONTROL-M
Quantitative resource name.
The layout of the CPUID Translation Table is as follows:
■ The first column of the Translation Table must be in ascending alphabetic order.
■ An asterisk (*) in the first position of the first row indicates that the JCL job class
must be used as the resource name for any JCL job class that is not listed in the
table, or for which no user text is specified in the table.
■ A dollar sign ($) in the second position, including after the asterisk in the first
row if desired, indicates that a $ sign is appended to the resource name. For the
significance of the $ mask character, see the description of the RESOURCE
conversion parameter in the CONTROL-M for OS/390 and z/OS User Guide.
8. The CPUID translation table

This contains a list of all the CA-7 MAINIDs and the corresponding system IDs. It
is used by sample Exit 2 to add JES2 (JOBPARM) or JES3 (MAIN) statements into
the converted CA-7 JCL job streams when necessary. This is accomplished using
the SET VAR parameter and the AutoEdit variable %%SYSID in the job scheduling
definition. For more information, see “40. MAINID” on page 129.
The layout of each record in the CPUID Translation Table is shown in Table 7.
Table 7 JOB3 CPUID Translation Table Record Layout

Column Description
1 CA-7 MAINID.
2–5 System ID.

Output
1. The CONTROL-M Intermediate Scheduling Table library
Default library name: CTM.V600.SCHEDULE
2. The CONTROL-M Documentation library

Default library name: CTM.V600.DOCUMENT
3. A global cross-reference file for all jobs and intermediate scheduling tables, which
can be used to determine the names of the scheduling tables in which a specific job
resides
Default file name: CTM.CA7.XREF
NOTE
The CONTROL-M CTMXRF utility can be used to create an updated
cross-reference file on the final scheduling tables created in JOB7.
4. A file containing all conversion exception messages
5. A file containing JCL for the New Day procedure, which must be customized
Default file name: CTM.V600.DAILY
6. An Include library, containing all job names for which the JCL member name
differs from the job name
Default file name: CTM.V600.INCLIB
File characteristics: PDS; record length 80; block size 3120
7. The CONTROL-M CMEM rule table, containing data set triggering events
Default file name: CTM.V600.CMEM
NOTE
This file must be specified as a member within a CONTROL-M CMEM rule table
library. The member contains a CONTROL-M rule table specifying ON
DSNEVENT rules.
8. The JCL Library DSN list

This contains a list of all the modified JCL Library data set names extracted from
the CA-7 Initdeck Initialization file.
Default file name: CTM.V600.JCLIN

9. The Demanded Job Names file

Default file name: CTM.CA7.DMDJOBS
10. A file from which appended scheduling tags are added to job scheduling
definitions when CA-7 basic scheduling criteria are too complex to correspond to a
single CONTROL-M scheduling tag
Default file name: CTM.CA7.DATAG
11. A file containing utility control statements for the CTMBLT utility
These statements are used to create to create the CONTROL-M Intermediate
Scheduling Table library (described earlier in this list of Output files)

JOB4 - Convert JCL Members
Description
JOB4 converts JCL members from CA-7 and CA-11 format to CONTROL-M format.
For details of how the override statements and other CA-7 and CA-11 components in
the JCL member are converted to CONTROL-M equivalents, see Chapter 4,
“Conversion Details.”
JOB4 converts CA-7 JCL Batch Terminal steps to equivalent CONTROL-M JCL steps.
For more information, see the discussion of DEMAND and POST in “DEMAND[H]
and POST Commands” on page 30, and “28. DEMAND[H] and POST” on page 120.
If CONTROL-M/Restart is being implemented, by setting the &CTR conversion

parameter to Y or X, all appropriate rerun and restart parameters of the CA-11 JCL
U11RMS steps are converted to their CONTROL-M/Restart equivalents. The actual
conversion is performed in JOB3. The U11RMS steps are then removed from the JCL
in JOB4. For more information, see “31. CA-11 U11RMS Step” on page 123.
JOB4 activates the CTMCA707 program to modify the copied JCL libraries.
NOTE
The CTMCA709 program is called to perform modifications to the JCL members
containing CA-7 Batch Terminal Steps. Local modification may be required if the
CA-7 Batch Terminal Step is not used in the standard CA-7 manner.
Input
1. Dynamically allocated copies of CA-7 and/or CA-11 JCL libraries
2. The JCL library DSN list, created by JOB3
3. A Batch Terminal Parameter file
The Batch Terminal Parameter file provides information on how the conversion
tool is to convert CA-7 Batch Terminal Steps. The format of the Batch Terminal
Parameter control statements is:
BTERM=batch-terminal-name[,PARM=parm-parameters]

The subparameters must comply with the following rules:
■ They must begin in column 1 and be separated by commas with no intervening

blanks.
■ They must be contained on one line.
■ BTERM is a mandatory subparameter.
■ PARM is an optional subparameter.
One Batch Terminal Parameter control statement is required for each Batch
Terminal PROC used in the CA-7 JCL libraries. A maximum of 10 control
statements is allowed.
The value of the batch-terminal-name subparameter is the program or procedure

(PROC) name of the CA-7 Batch Terminal Step, such as SASSTRLR or U7VSC.
There is no default.
The value of the parm-parameter subparameter can be set by one of the following
methods:
■ Specify the JCL PARM parameter designation used in the CA-7 Batch Terminal
procedure. The default is PARM=PARM
■ Indicate that the CA-7 Batch Terminal procedure is issuing a CA-7 DEMAND or
POST command, use the JCL PARM parameter, and display symbolic variables
for various subparameters of the command.
The type of CA-7 command, and the symbolic variable names, are specified in the
control statement, using the following syntax:
PARM=(command-type[,variable-1][,variable-2])
where
■ command-type is one of the following types of command:
— DE – a DEMAND command
— PU – a POST command with a user-defined requirement
— PJ – a POST command with a predecessor job dependency requirement
■ variable-1 is the symbolic variable name of the JOB parameter value in the
command. The default variable name is JOB.

■ variable-2 is the symbolic variable name of a parameter value, as follows:
— Where the command-type specified is DE, variable-2 is the symbolic variable name
of the SCHID parameter value. The default variable name is SCHID. If the
SCHID variable is not found in the JCL, a symbolic schedule ID of 000 is
assigned.
When Batch Terminal Procedures are specified using DE as the value for
command-type, you must incorporate the demanded jobs into a CONTROL-M
scheduling table, and specify the appropriate IN conditions in their job
scheduling definitions.
— Where the value of command-type is set to PU, variable-2 is the symbolic variable
name of the USR parameter value. The default variable name is USR
— Where the value of command-type is set to PJ, variable-2 is the symbolic variable
name of the DEPJOB parameter value. The default variable name is DEPJOB.
The usage of the parm-parameter subparameter value is further clarified in the

following example.
Example
Suppose a site has six types of Batch Terminal Procedures in the CA-7 JCL
libraries.
A. The BTERM1 procedure specifies all CA-7 Batch Terminal Commands using one
of the following SYSIN DD statements:
//stepx EXEC BTERM1//SYSIN DD *

CA-7 commands
/*
//stepx EXEC BTERM1

//SYSIN DD DISP=SHR,
// DSN=pdsmember_or_seq_file
B. The BTERM2 procedure specifies a CA-7 Batch Terminal command using the
JCL EXEC PARM parameter, as follows:
//stepx EXEC BTERM2,PARM='CA-7 command'
C. The BTERM3 procedure specifies a CA-7 Batch Terminal command using a

symbolic PARM parameter P, as follows:
//stepx EXEC PGM=SASSTRLR,PARM='&P'

D. The BTERM4 procedure specifies symbolic variables for the job name (JOB) and
schedule ID (SCHID) parameters of the CA-7 DEMAND command, as follows:
//stepx EXEC BTERM4,JOBNM=jobname,SCH=schid
where the BTERM4 procedure contains
//stepy EXEC PGM=U7SVC,

// PARM='/logonid;DEMAND,JOB=&JOBNM,SCHID=&SCH'
E. The BTERM5 procedure specifies symbolic variables for the job name (JOB) and
user-defined requirement (USR) parameters of the CA-7 POST command, as
follows:
//stepx EXEC BTERM5,JOBN=jobname,USREQ=usr
//stepy EXEC PGM=U7SVC,

// PARM='/LOGON operid;POST,JOB=&JOBN,USR=&USREQ'
F. The BTERM6 procedure specifies CA-7 Batch Terminal commands using a

SYSIN DD statement, and contains a symbolic parameter (ID) that specifies a
relative batch terminal number, as follows:
//stepx EXEC BTERM6,ID=1

//SYSIN DD *
CA-7 commands
//
//stepy EXEC PGM=SASSBSTR,

// PARM='&ID,...'
The symbolic parameter ID is irrelevant to the proper conversion of the CA-7

commands in the SYSIN file. However, the corresponding CONTROL-M
procedure, CTMUTIL, which is explained in Chapter D, “The CTMUTIL
Conversion Utility,” must take the ID into account to avoid a JCL error when
resolving symbolic parameters. One method of accomplishing this is by having
the CTMUTIL procedure use the symbolic parameter in a “harmless” way.
For example, define the CTMUTIL procedure with the symbolic parameter ID as
follows:

//CTMUTIL PROC ID=1

//step1 EXEC PGM=CTMUTIL,TIME=&ID
The contents of the DABTERM file for the above example must be coded as
follows:
BTERM=BTERM1
BTERM=BTERM2
BTERM=BTERM3,PARM=P
BTERM=BTERM4,PARM=(DE,JOBNM,SCH)
BTERM=BTERM5,PARM=(PU,JOBN,USREQ)
BTERM=BTERM6
NOTE
The conversion tool is delivered with two Batch Terminal programs or
procedures named SASSTRLR and U7SVC. These names can be modified to
conform to local naming conventions at the site.
When the second form of the PARM parameter is specified, both variable-1 and
variable-2 must appear on the same JCL line as the batch-terminal-name.
4. The Demanded Job Names file created by JOB3
Output
1. JCL libraries in CONTROL-M format
2. the JCL conversion report

JOB5 - Convert Virtual Resource Management Components
JOB5 - Convert Virtual Resource Management

Components
Description
JOB5 converts CA-7 virtual job resources into CONTROL-M Control and
Quantitative resources and manual IN conditions. JOB5 reads the Job-to-Resource
Cross Reference report that associates each resource with the jobs that use it.
CONTROL-M Control and Quantitative resources and manual IN conditions are
added to the job scheduling definition of each relevant job.
The following CA-7 virtual resources, and no others, are supported by the
conversion:
■ exclusive
■ shared
■ corequisite
■ resource count
For more information, see Table 17 on page 95 and “25. Virtual Resource
Management” on page 115.
NOTE
Users of CA-7 Release 3.0 and earlier should execute this job only if the CA-7
Resource Management facility and the LXRSC command are installed.
JOB5 activates the CTMCA710 program to convert the CA-7 virtual resources.
Input
1. The file containing the Job-to-Resource Cross Reference report that was created by
JOB0
2. The global cross-reference file that was created by JOB3
3. The CONTROL-M scheduling table library that was created by JOB3

JOB5 - Convert Virtual Resource Management Components
Output
1. Modified CONTROL-M scheduling tables containing Control and Quantitative
resources and manual IN conditions
2. A message file

JOB6 - Update CONTROL-M Scheduling Tables
JOB6 - Update CONTROL-M Scheduling Tables

As of version 6.1.00, JOB6 has been removed from the conversion utility.

JOB7 Create CONTROL-M Group Scheduling Tables
JOB7 Create CONTROL-M Group Scheduling

Tables
Description
JOB7 creates CONTROL-M Group scheduling tables from the Intermediate
Scheduling Tables created in JOB3. The tables are processed by merging tables that
belong to the same application and converting them to CONTROL-M Group
scheduling format. When the &DEMAND conversion parameter is set to CA7, as
discussed in “&DEMAND” on page 148, the resultant library is further divided into
the libraries shown in Table 8.
Table 8 Divided LIbraries Produced

Library Description
CTMNDMD Contains all the Group scheduling tables excluding
■ all demanded jobs
■ the jobs triggered by demanded jobs

CTMDMD Contains standard (non-Group) scheduling tables consisting
of
■ demanded jobs (as head-of-tree)
■ the jobs triggered by the demanded jobs
When the &DEMAND conversion parameter is set to CTM, STEP3 must be deleted
from JOB7.
JOB7 activates the CTMCA7V5 and CTMCA7DM programs to create the

CONTROL-M Group scheduling tables.
Parameters
The expected maximum number of lines in any Group scheduling table must be
specified in the JCL PARM parameter of the EXEC statements in STEP2 and STEP3 in
this job. This number must be approximately 2 to 3 times the maximum number of
lines of the largest scheduling table. The default is 40000.
The REGION parameter must be set to 0K in the EXEC statement.

JOB7 Create CONTROL-M Group Scheduling Tables
Input
1. The Application List file created by JOB2
2. The CONTROL-M intermediate scheduling table library created by JOB3
3. The Appended Scheduling Tags file create by JOB3
Output
1. The CONTROL-M Group Scheduling Table library
Default library name: CTM.V600.NEWSCHED
NOTE
Review the members in this library carefully.
The conversion tool generally attempts to combine like-named jobs in a table with
different scheduling IDs into the same job scheduling definition with multiple
schedule tags. However, in some instances, minor differences in job scheduling
parameters prevent this from being done. In this case, you may want to modify
these job scheduling definitions and combine them using multiple schedule tags.
In addition, a set of schedule tags with different names may have the same Basic
Scheduling parameters. You may choose to retain only one of these tags in the
Group Entity, delete the rest, and rename all occurrences of the deleted tags in the
job scheduling definitions to the name of the retained tag.
2. The CONTROL-M Group scheduling table library without Demanded jobs

Default library name: CTM.V600.SCHED.NDMD
3. The CONTROL-M Demanded jobs scheduling table library

Default library name: CTM.V600.SCHED.DMD
The conversion of demanded jobs, referred to in the two preceding paragraphs,

and in particular setting the &DEMAND conversion parameter to CA7, is
discussed in “&DEMAND” on page 148.

JOB8 - Convert CA-DRIVER Procedures and JCL Libraries (Optional)
JOB8 - Convert CA-DRIVER Procedures and JCL

Libraries (Optional)
Description
JOB8 converts CA-DRIVER procedures and JCL members to CONTROL-M format.
For more information, including details of how the CA-7 components in the
CA-DRIVER and JCL members are converted to CONTROL-M equivalents, see
Chapter 4, “Conversion Details.”
JOB8 activates the CTMDRV01 program to convert the CA-DRIVER procedure

library, and the CTMDRV02 program to modify the copied JCL libraries.
Input
1. A list of all CA-DRIVER procedure library names
2. A list of all CA-7 JCL library names

Each name is entered on a separate line, beginning at column 1
Output
1. The procedure library in CONTROL-M format
Default name: CTM.CA7.PROCLIB
2. JCL libraries in CONTROL-M format
3. The procedure default values library in CONTROL-M format

This library contains in a JCL member the default values assigned to variables by
the EXEC statement.
Default name: CTM.CA7.PARMLIB
4. The Input Statements library in CONTROL-M format

Default name: CTM.CA7.DATALIB
All conversion messages are written to the CTM.CA7.MSG message file.

For more information on the PROCLIB and PARMLIB output files, see “51. DPROC”
on page 133.
For more information on the DATALIB output files, see “56. DATA, DEND” on
page 136.


Chapter
3 Conversion Steps
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Pre-Conversion Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Step 1 - Create the Conversion SOURCE and LOAD Libraries . . . . . . . . . . . . . . . . . . 72
Step 2 - Copy CA-7 and CA-11 JCL and CA-DRIVER Libraries and Initdeck . . . . . . 73
Step 4 - Modify Parameters in the DEFAULTS Member . . . . . . . . . . . . . . . . . . . . . . . . 75
Step 5 - Modify and Run the ASMLINK Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Step 6 - Modify and Run the JOB1 Member. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Step 12 - Modify and Run the JOB8 Member (Optional) . . . . . . . . . . . . . . . . . . . . . . . 84
Step 13 - Customize CONTROL-M and Install User Exits . . . . . . . . . . . . . . . . . . . . . . 85
Step 14 - Final Adjustments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Step 15 - Check Conversion Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Step 16 - Customize the New Day Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Overview
Overview
Installation and operation of the conversion tool consists of a series of steps.
BMC Software recommends that you first review the contents of Appendix C,
“Planning The Conversion” then read through the remainder of this chapter before
performing the steps. It is important to follow the outlined sequence of the steps to
ensure a successful conversion.
The following is a summary of the steps:
Pre-conversion planning
1 Create the conversion SOURCE and LOAD libraries.
2 Copy CA-7 and/or CA-11 JCL and CA-DRIVER Libraries and Initdeck.
3 Modify and run the JOB0 member.
4 Modify parameters in the DEFAULTS member.
5 Modify and run the ASMLINK member.
12 Modify and run the JOB8 member (Optional).
13 Customize CONTROL-M and install user exits.
14 Final adjustments.
15 Check conversion results.
16 Customize the New Day Procedure.

Pre-Conversion Planning
NOTE
For all of the jobs which follow, the IEF283I NOT DELETED 8 message can be
ignored for the first (or only) run of the job.
Pre-Conversion Planning
Before beginning the actual conversion process, the following list must be reviewed
for tasks that may need to be performed in preparation for the conversion:
1. Verify the CA-7 database to ensure its integrity and accuracy.
A. Run the UCC7DBVR program to verify that all logical pointers in the CA-7
database are properly set.
B. Run the following Analyze commands to correct, if necessary, various database

index entries and cross references.
■ RQMT
■ TRIG
■ XREF
■ RESANL
2. Simplify the JCL conversion process by running the CA-7 SASSJCLU utility
against the CA-7 JCL Scheduled Override control statements and the scheduled
JCL itself.
3. Ensure that all calendar-oriented schedules are RESOLVEd against the proper Base
Calendar. Without schedule resolution, job schedules cannot be correctly defined
in the LSCHD report. For more information, see “JOB1 - Produce the updated
CA-7 LJOB Report” on page 44.
4. Review any system, CA-7, or CA-11 exits that perform functions that must be
implemented in the CONTROL-M environment.
5. Ensure that all personnel involved in the conversion process have security access
to all required functions, such as authorized CA-7 LOGON IDs, and that they have
authorization to execute the necessary batch jobs.

Step 1 - Create the Conversion SOURCE and LOAD Libraries
Step 1 - Create the Conversion SOURCE and

LOAD Libraries
1. Run the $$INIT job in the IOA CONV library to create the CA-7 conversion
SOURCE library and allocate the conversion LOAD library.
2. Tailor the following parameters in the member in accordance with your local
conventions.
Table 9 Parameters to Be Adjusted

Parameter Description
Job statement
INLIB IOA CONV library name
OUTLIB CA-7 conversion SOURCE library name
LOADLIB CA-7 conversion LOAD library name
UNIT Unit name of DASD device
VOLSER Volser of DASD device
PRODUCT CA7
3. Submit the job for execution. The job must finish with a completion code of 0.
NOTE
Do not APF-authorize the conversion LOAD library.

Step 2 - Copy CA-7 and CA-11 JCL and CA-DRIVER Libraries and Initdeck
Step 2 - Copy CA-7 and CA-11 JCL and

CA-DRIVER Libraries and Initdeck
To prevent changes to the current production JCL environment, create a copy of the
CA-7 and CA-11 JCL libraries named in the CA-7 Initdeck Initialization file. All
CA-DRIVER libraries, if any, must also be copied.
A sample job for copying the production JCL libraries is provided in the COPYLIBS
member in the conversion SOURCE library.
For CA-LIBRARIAN or CA-PANVALET libraries, use the utilities supplied by

CA-LIBRARIAN or CA-PANVALET to create and copy the production JCL libraries
into PDS libraries for use by the conversion tool.
The new libraries must be sufficiently large to enable update of all the members.
Additional libraries and sequential data sets may need to be copied. For more
information, see “&PNIBTSD” on page 154.
The original CA-7 Initdeck must be copied and the data set names of the JCL libraries
must be modified to reflect the data set names of the copies of the JCL libraries
referred to above.

Step 3 - Modify and Run the JOB0 Member

JOB0 produces the CA-7 LJOB, LSCHD, Base Calendar, and Job-to-Resource Cross
Reference reports.
Edit the JOB0 member in the conversion SOURCE library. Adjust the following
specifications according to your local conventions:
■ the job statement
■ the name and location of the LJOB report, specified in the SYSPRINT DD statement
in STEP1
■ the name and location of the LSCHD report, specified in the SYSPRINT
DD statement in STEP2
■ the name and location of the Base Calendar report, specified in the SYSPRINT
■ the name and location of the Job-to-Resource Cross Reference report, specified in
the SYSPRINT DD statement in STEP4
■ the CA-7 SASSBTRM procedure name, if changed locally, as specified in STEP1,

STEP2, STEP3, and STEP4
This procedure invokes the CA-7 SASSBSTR program.
■ the CA-7 user ID of the /LOGON command, as referred to in STEP1, STEP2,

STEP3, and STEP4
Submit the job and check the sysout for completion code and error messages. The job
must finish with a condition code of 0.
NOTE
Producing the CA-7 LJOB report may take several hours, depending on the size of the
CA-7 database.

Step 4 - Modify Parameters in the DEFAULTS Member
Step 4 - Modify Parameters in the DEFAULTS

Member
Edit the DEFAULTS member in the conversion SOURCE library. Adjust the
CONTROL-M parameters in accordance with your site requirements. For a detailed
description of these conversion parameters, see Appendix A, “Conversion
Parameters”
Step 5 - Modify and Run the ASMLINK Member

The ASMLINK member in the conversion SOURCE library assembles and link-edits
all conversion programs, using the DEFAULTS tailored parameters member from the
previous step.
Edit the ASMLINK member to adjust the following specifications in accordance with
your local conventions:
■ the conversion SOURCE library name, set in the SRCLIB parameter, created in
Step 1
■ the conversion LOAD library name, set in the LOADLIB parameter, allocated in
Step 1
■ the IOA LOAD library name, set in the IOALOAD parameter
■ the IOA SMP/E Distribution LOAD library name, set in the ALOAD parameter
■ the IOA MAC library name, set in the IOAMAC parameter
Submit the job and check the sysout for completion code and error messages. In the
link-edit of Steps M5 and M6, a condition code of 4, caused by unresolved external
references, is acceptable. All other steps must complete with a condition code of 0.
NOTE
This step must be re-executed whenever changes are made to the parameters in the
DEFAULTS member, or a source fix is applied to any module. If necessary, an LLA
REFRESH must also be performed after changes are made.

If the high-level assembler Release 2, HLASMR2, is used for assembly and link
processing, use assembly option USING(WARN(2)) to obtain a clean assembly
and suppress the ASMA303 warning message.

JOB1 creates the updated CA-7 LJOB report.
specifications in accordance with your local conventions:
■ the IOA LOAD library name, specified in the IOALOAD DD statement in STEP0
■ the IOA PARM library name, specified in the IOAPARM DD statement in STEP0
■ the IOA IOAENV library name, specified in the IOAENV DD statement in STEP0
■ the conversion LOAD library name, specified in the CTMLOAD DD statement in

STEP0
■ the CA-7 Initdeck-library and member name, specified in the DAINIT

DD statement STEP0
Use the copy of CA-7 Initdeck made in Step 2 (on page 73).
■ the name of the LJOB report file created by JOB0, specified in the DAREPORT
— Concatenated LJOB reports may be specified. However, verify that the record
indicating the end of the CA-7 Batch Terminal (SLIA-00) is removed from all the
LJOB reports except the last LJOB report in the concatenation.
— Do not concatenate different LJOB reports that may contain jobs of the same
name. Each such LJOB must be converted in a separate conversion process.
— If you want to concatenate multiple LJOB reports, you must first arrange them
in jobname order.
■ the name and location of the updated LJOB report, specified in the DALJOBO
■ the name and location of the file containing the list of jobs that require Auxiliary
Calendars, specified in the DAJOBSCH DD statement in STEP0

■ the name and location of a work library, specified in the WORK DD statement in
STEP0
The same data set name must also be specified in the SYSINLIB DD statement in
STEP5 (but do not delete the member name)
■ the number of jobs that are contained in the LJOB report, specified in STEP5, the
PARM parameter of the EXEC statement. You must also set the REGION
parameter to 0K in the EXEC statement
If you allocate files on SMS-managed volumes, you must pre-allocate files

referenced by the DALJOBO and DAJOBSCH DD statements before executing
JOB1 for the first time. This file must not be placed on volumes that have the SMS
Management Class Partial Release attribute specified.
Submit the job and check the sysout for completion code and messages. Ignore any
informational or warning messages. Errors with a return code of 12 must be corrected
and the job rerun.
Error (E) level messages with a return code of 8 must be investigated and corrected
wherever possible. However, E level messages rarely prevent the creation of the
updated LJOB report. Some E level messages are unavoidable, such as those referring
to missing calendars, because the calendar library has not yet been created. These
types of E level messages can be safely ignored, and you may continue with the
conversion process. For explanations of each message, see Appendix B, “Messages”

JOB2 creates the Applications list, Calendar library, and Calendar Name List files.

STEP0
■ the IOA IOAENV library name, specified in the IOAENV statement in STEP0
■ the name of the LJOB report file created by JOB1, specified in the DAREPORT

■ the name of the LSCHD report file created by JOB1, specified in the DAREPRT2
■ the name of the Base Calendar report file created by JOB1, specified in the
DABASCAL DD statement in STEP0
■ the name and location of the Applications List file, specified in the DAOUT1
■ the name and location of the CONTROL-M Calendar library, specified in the
DACAL DD statement in STEP0
■ the name and location of the Calendar Names List file, specified in the DACALNM
■ the name and location of the SCHDYONLY and Periodic Calendar Name file,
specified in the DACALS DD statement in STEP0
■ the name of the job list report of the jobs requiring an Auxiliary Calendar created
by JOB1, specified in the DAJOBSCH DD statement in STEP0
■ the work unit name, specified in the SORTIN DD statement in STEP0
■ the CA-7 Periodic Base Calendar Control statements, specified in the SYSIN
For details of the record layout and content, see “JOB2 - Create the Applications
List, Calendar Libraries, and Calendar Names List Files” on page 46. Specify this
information only if there are nonstandard, periodic, CA-7 Base Calendars
produced in JOB1 in the Base Calendar report.
NOTE
If you allocate files on SMS-managed volumes, you must preallocate files
referenced by the DAOUT1, DACAL, DAJOBSCH, and DACALNM
DD statements before executing the specified job the first time. These files, if they
are PDSs, must not be placed on volumes that have the SMS Management Class
Partial Release attribute specified.
must finish with a condition code of 0. Error messages are explained in Appendix B,
“Messages”
An editor can be used to modify the Application List file. For more information,
including details of the record layout, see “JOB2 - Create the Applications List,
Calendar Libraries, and Calendar Names List Files” on page 46.


JOB3 creates the CONTROL-M scheduling tables.
NOTE
Before performing this step, be sure to check, and if necessary modify, the
Applications List file created in JOB2.

STEP0
■ the name of the LJOB report file created by JOB1 and used in JOB2, specified in the
DAREPORT DD statement in STEP0
■ the name of the Applications List file created by JOB2, specified in the DASYSN
■ the CA-7 Initdeck library and member name, specified in the DAINIT
Use the copy of CA-7 Initdeck made in Step 2.
■ the name and location of the CONTROL-M Documentation library, specified in the
DADOC DD statement in STEP0
■ the name and location of the intermediate table or jobname Cross-Reference file,
specified in the DAXREF DD statement in STEP0
■ the name and location of the library for JCL INCLUDE members, specified in the
DAINCLIB DD statement in STEP0
■ the name and location of the file containing the JCL for the New Day procedure,
specified in the DADAILY DD statement in STEP0

■ the name and location of the intermediate CONTROL-M scheduling table library,
specified in the DASCHD DD statement in STEP0
■ the name of the SCHDYONLY and Periodic Calendar Name List file created by
JOB2, specified in the DACALS DD statement in STEP0
■ the name of the Calendar Name List file created by JOB2, in the DACALNM
■ the name and location of the CONTROL-M CMEM Rule Table definitions,
specified in the DACMEM DD statement in STEP0
■ the name and location of the JCL library DSN list, specified in the DAJCLIN
■ the name and location of the Demanded Job Names file, specified in the
DADMDJNM DD statement in STEP0
■ the name and location of the control input statements for the CTMBLT utility,
specified in the DABLT DD statement in STEP0
■ the number of jobs that are contained in the LJOB report, in STEP2, the PARM
parameter of the EXEC statement in STEP2
The REGION parameter in the EXEC statement must also be set to 0K.
■ the name of the CA-7 Job Class Translation Table, or the actual table contents,
DD statement DAJOBCL in STEP2
For details of the record layout and content, see “JOB3 - Create CONTROL-M
Scheduling Tables and CMEM Rules” on page 50. This information must only be
specified if the JCL Job Classes (in the Job statement) are to be converted into
CONTROL-M Quantitative resources. For more information, see “&JOBCLAS” on
page 152.
■ the name of the CPUID translation table, or the actual table contents, in the
DACPUID DD statement in STEP2
For details of the record layout and contents, see “JOB3 - Create CONTROL-M
Scheduling Tables and CMEM Rules” on page 50. This table need only be specified
if jobs require specific system affinity, which is specified using the CA-7 MAINID
parameter.
■ the name and location of a WORK library, specified in the WORK DD statement in
STEP0. The same data set name must also be specified in the SYSINLIB
DD statement in Step 2, but do not delete the member name.
■ the name and location of the file that causes the creation of additional scheduling
tags in job scheduling definitions, specified in the DATAG DD statement in STEP0

NOTE
If you allocate files on SMS-managed volumes you must, before executing the
specified job for the first time, pre-allocate files referenced by the DAXREF,
DACMEM, DASCHD, DAINCLIB, DADOC, DADAILY, DABLT, and DATAG
DD statements. If they are PDSs, these files must not be placed on volumes that
have the SMS Management Class Partial Release attribute specified.
Submit the job and check the sysout for completion code and error messages. A
condition code of 12 or above causes the job to stop processing. Error messages are
explained in Appendix B, “Messages”

JOB4 converts JCL members.

STEP0
■ the name of the JCL Library DSN list, created by JOB3, as specified in the DAJCLIN
■ the name of the Demanded Job Names file, created in JOB3, as specified in the
DADMDJNM DD statement in STEP0
■ the name and location of a WORK library, specified in the WORK DD statement in
STEP0
The same data set name must also be specified in the SYSINLIB DD statement in
STEP2, but do not delete the member name.
■ a list of the Batch Terminal parameters control statements, specified in the

DABTERM DD statement in STEP2

For details on how to specify these parameters, see “JOB4 - Convert JCL Members”
on page 56.
WARNING
To prevent changes to the current production environment, use a copy of the CA-7
and/or CA-11 production JCL libraries, and not the actual libraries, as input to this
job. For instructions, see Step 2. JOB4 issues the CTMCA707-00R message, which
requires that the operator confirm that Step 2 has been performed.
“Messages”

JOB5 converts Resource Management Components.
NOTE
For users of CA-7 Release 3.0 or earlier, perform this step only if your site has
implemented the CA-7 Resource Management facility. Otherwise, skip to Step 11.

STEP0
■ the name of the Job-to-Resource Cross Reference report file, specified in the
DAREPIN DD statement in STEP0
■ the name of the table-jobname Cross Reference file created by JOB3, as specified in
the DAXREF DD statement in STEP0
■ the name of the CONTROL-M scheduling table library created by JOB3, as

“Messages”

If an Sx37 abend occurs during the execution of this job, compress and optionally
enlarge the library, then rerun the job. The conversion program does not update
scheduling tables that were updated in the previous run.

JOB7 creates the CONTROL-M Group scheduling table library from the intermediate
scheduling table library created in JOB3, as described in Step 8.
specifications according to your local conventions:

STEP0
■ the name of the Applications List file created by JOB2, specified in the APPLIST
■ the name of the intermediate CONTROL-M job scheduling table library in JOB3,
■ the name of the file that causes the creation of additional schedule tags, created by
JOB3, specified in the DATAG DD statement in STEP0
■ the name and location of the CONTROL-M Group scheduling table library,
specified in the CTMSV5 DD statement in STEP0
■ the maximum number of lines in any Group scheduling table, the PARM
parameter of the EXEC statement in STEP2 and STEP3
When the &DEMAND conversion parameter, which is described in “&DEMAND” on

page 148, is set to CTM, STEP3 in JOB7 must be deleted.
The following specifications are required only if the &DEMAND conversion

parameter is set to CA7:

Step 12 - Modify and Run the JOB8 Member (Optional)
■ the name and location of the CONTROL-M Group scheduling table library
excluding all demanded jobs, specified in the CTMNDMD DD statement in STEP0
■ the name and location of the CONTROL-M (non-Group) scheduling table library
containing all demanded job streams, specified in the CTMDMD DD statement in
STEP0
NOTE
If you allocate files on SMS-managed volumes, you must, before executing the
specified job for the first time, pre-allocate files referenced by the DASCHD,
CTMNDMD, and CTMDMD DD statements. If they are PDSs, these files must not
be placed on volumes that have the SMS Management Class Partial Release
attribute specified.
“Messages”

(Optional)
Submit JOB8 only if your site is using CA-DRIVER (when the //CARPROC
DD statement is present in the CA-7 execution JCL).
Tailor the following specifications in the JOB8 member in the conversion SOURCE
library in accordance with your local conventions:
■ the conversion LOAD library name, in the CTMLOAD DD statement in STEP0
■ the IOA LOAD library name, in the IOALOAD DD statement in STEP0
■ the name and placement of the Procedure library, in the DAPROC DD statement in
STEP0
■ the name and placement of the Procedure Default Values library, in the
DAPARAM DD statement in STEP0
■ the name and placement of the Input Statements library, in the DADATA

Step 13 - Customize CONTROL-M and Install User Exits
■ a list of CA-DRIVER Procedure library names, in the DAPROCIN DD statement in

STEP3
■ a list of CA-7 JCL library names, in the DAJCLIN DD statement in STEP4
WARNING
To prevent changes to the current production environment, use copies of the JCL
libraries, not the CA-7 production JCL libraries, as input to this job. For more
information, see Step 2.
Submit the job for execution, then check the SYSOUT for completion code and error
messages. A condition code of 12 or above causes the job to terminate. Error messages
are explained in Appendix B, “Messages”
If problems or errors are encountered, correct them manually in the CA-7 JCL
libraries, and rerun this job.
Step 13 - Customize CONTROL-M and Install

User Exits
1. Set the SCHPREVD parameter in the CTMPARM member in the IOA.PARM
library to Y.
This parameter operates on jobs scheduled between midnight and the

CONTROL-M New Day time. It moves these jobs to the previous day to avoid date
discrepancies. This parameter is only operative when the SAC CONTROL-M job
scheduling parameter is set. For more information, see “New Day Processing and
Schedule Scan” on page 28.
2. Check the INCLIB library created by JOB3 to see if any INCLUDE members were
created. Skip this adjustment if the library is empty.
If the INCLIB library contains members, or if you want to force the jobname to be
identical to the JCL member name, you can optionally activate CONTROL-M User
Exit 2 (the job submission exit) to imitate CA-7 submission processing. This exit is
supplied in the CTMX002Q member in the IOA SAMPEXIT library. For details
regarding this user exit, see the CTMX002 member in the same library. If Exit 2 is
currently being used, the supplied exit must be incorporated into the current exit.
3. Set the ONSINDMY parameter in the CTMPARM member in the IOA PARM
library to N. This parameter deactivates the validation check of specifying ON
PGMST statements within DUMMY job definitions.

Step 13 - Customize CONTROL-M and Install User Exits
4. If the &CTR conversion parameter, which is described in “&CTR” on page 146,

was set to Y or X, the following applies:
— It may be necessary to set the NFILVS99 parameter (to N).
— It may also be necessary to set the ADDPROC, PROCRC, and NCT2RC

parameters.
— If your JCL contains any referbacks in the COND parameter of the type
COND=(1,NE,UCC7RMS.U11STEP), do the following
■ Set the ADDPROC, PROCRC, and NCT2RC parameters.
■ Change the U11STEP step name to IOATEST. This can be done by one of the
following methods:
— change the step name directly in the JCL members, by means of a utility that
can make multiple updates
— use CONTROL-M User Exit 2 (CTMX002) to search the JCL member for
EXEC statements containing the string COND=(1,NE,UCC7RMS.U11STEP),
and, without physically changing the actual JCL member, change that string
on submission to COND=(1,NE,UCC7RMS.IOATEST).
All these parameters are in the CTRPARM member in the IOA PARM library. For
more information on these parameters, see the section on optional wishes with
data in the CONTROL-M/Restart Customization chapter of the INCONTROL for
OS/390 and z/OS Installation Guide.
5. Install User Exit 2 (the Job Submission exit), which is supplied in the CTMX002R
member in the SAMPEXIT library. The exit inserts JES2 and JES3 statements into
the JCL member of a job in order to route jobs to the required CPU using the
following job scheduling definition parameters
SET VAR=%%SYSID=xxx
where xxx is derived from the CA-7 MAINID parameter and the CPUID
translation table supplied by you.
For more information on the CA-7 MAINID parameter, see “40. MAINID” on
page 129.
This exit can be tailored to local requirements. Read the comments in the
CTMX002R member carefully to determine the desired method of implementation.
For details regarding this user exit, see the CTMX002 member.
If Exit 2 is currently being used, for example, as outlined in paragraph 2 of this

Step, the supplied exit must be incorporated into the current exit.

Step 14 - Final Adjustments
Step 14 - Final Adjustments

The following final adjustments must be performed:
1. If a CMEM Rule table was built in the CMEM file created in JOB3, follow the
instructions in the CONTROL-M for OS/390 and z/OS User Guide.
2. The CTMXRF CONTROL-M utility must be run with the cross reference statement
XRF=RES, to determine if any Quantitative resources were placed in the newly
created job scheduling definitions. If this is the case, these resources must be added
to the CONTROL-M Resources file using the IOACND utility. For more
information on the IOACND utility, see the INCONTROL for OS/390 and z/OS
Utilities Guide.
3. The CTMXRF CONTROL-M utility may be run with the cross reference statement
XRF=CAL, to produce a Calendar Name-Jobname cross reference report. This
report can be used to determine whether the conversion has created any auxiliary
calendars, and if so, the identity of any auxiliary calendars that have been created.
You can replace any of the existing auxiliary calendars with basic scheduling
criteria by means of the CTMTBUPD utility, which is described in the
INCONTROL for OS/390 and z/OS Utilities Guide.
For more information on the creation of auxiliary calendars, see
■ “13. SCAL” on page 105

■ the description of the Calendar Names List file in the output of JOB2 on page 49
In order to minimize the work of maintaining auxiliary calendars, BMC Software

recommends that, wherever possible, you replace them with basic scheduling
parameters and base calendars. To do this, use the CONTROL-M CTMTBUPD
utility. For more information on this utility, see the CONTROL-M chapter of the
INCONTROL for OS/390 and z/OS Utilities Guide.
Example
Suppose the following:
■ The SJ123456 calendar is defined in the DCAL parameter of the TAG1 schedule
tag in the XYZ group scheduling table.
■ The SJ123456 calendar schedules the job every third working day of the month,
which in the CA-7 Q1 base calendar is a Monday.
■ The &CALPREF conversion parameter was set to CTMCAL. The &CALPREF

conversion parameter is described in “AConversion Parameters” on page 143.

Step 15 - Check Conversion Results
■ The SWEEK CONTROL-M installation parameter is set to MON.
Replace the auxiliary calendar by means of the following CTMTBUPD utility

control statements:
SEL TBL XYZ,TAG=TAG1

DCAL=CTMCALQ1
DAYS=D3
RELATION=A
WDAYS=1
ENDSEL
NOTE
Any auxiliary calendars that are not replaced must be extended to multi-year
calendars as soon as possible.
4. If CA-LIBRARIAN or CA-PANVALET libraries were converted to partitioned data

sets in Step 2 above, they may be reconverted back to CA-LIBRARIAN or
CA-PANVALET format at this point.
5. Review all CA-7 and CA-11 system exits (if any), for example, the CA-11 JES2 or
JES3 interfaces, such as the JES2 Exit 6, the JES3 IATUX03, and the CA-11 SMF
IEFUJV exits. Remove or modify such exits as appropriate.
6. Copy the DAYMONTH AutoEdit member, which contains AutoEdit Global

variable definitions. If you utilize CA-DRIVER, you must copy the DAYMONTH
member from the conversion SOURCE library to the library specified in the
DAGLOBAL DD statement, which is defined in the CONTROL-M monitor
procedure.
Step 15 - Check Conversion Results

1. Enter the CONTROL-M environment and order some of the scheduling tables that
were created. You can also use the Graphic Job Flow option (Screen 2.G) to view
the job flow of any CA-7 applications as they appear in CONTROL-M, and the
Plan option (option P in the Job List screen) to show a calendar of the days on
which a job is scheduled.
2. Execute the CONTROL-M utilities CTMRFLW, CTMRPLN, CTMROGR, CTMXRF,

and so on, and compare the reports of the conversion results with the CA-7 job
definitions. These utilities are described in the INCONTROL for OS/390 and z/OS
Utilities Guide.

Step 16 - Customize the New Day Procedure

Specify the new scheduling tables in the DAJOB DD statement of the CONTROL-M
New Day procedure. Use the list of scheduling tables created by JOB3 in the file
pointed to by the DADAILY DD statement.


Chapter
4 Conversion Details
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Component Conversion Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Component Conversion Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
1. JOB and MEMBER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
2. JCLID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
3. SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4. JCL-OVRD and # JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
5. VERIFY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
6. MAINT and # MNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
7. HOLD and DEMAND[H] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
8. EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
9. PRTY, # RES and DEMAND[H] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
10. COND-CODE, RO and # SCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
11. TYPE1 and TYPE2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
12. CLASS, # RES and DEMAND[H] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
13. SCAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
14. ROLL, INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
15. SBTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
16. DOTM and LDTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
17. Scheduling Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
18. Job Triggering and # NTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
19. DEP-JOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
20. DEP-JOB=/jobname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
21. DSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
22. NWK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
23. USER REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
24. PROSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
25. Virtual Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
26. # JI, # JO, and # JEND, # XI, # XO, and # XEND Statements . . . . . . . . . . . . . . . 117
27. JCL Job Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
28. DEMAND[H] and POST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
29. CA-11 Non-Restartable Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
30. INSERT-RMS and //*CA-11 Comment Statements . . . . . . . . . . . . . . . . . . . . 123
31. CA-11 U11RMS Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

32. NXTCYC SET-OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
33. RESCHNG and # RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
35. OWNER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
36. SCHID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
37. JCL Initialization Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
38. SHOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
39. CMEM Rule Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
40. MAINID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
41. INITR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
42. JES ROUTE PRINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
44. DEP-JOB=? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
45. DONT SCHEDULE BEFORE/AFTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
46. # HLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
47. # NOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
48. # MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
49. # VER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
51. DPROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
52. (D)STEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
53. (D)GOTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
54. (D)SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
55. (D)IF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
56. DATA, DEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
57. (D)NEST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
58. (D)ABORT/DFLUSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
59. Variable Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
60. Date Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
61. Attribute Functions (L’, T’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Unique CONTROL-M Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
CATEGORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
DO SYSOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
MAXWAIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Overview
Overview
This chapter details the conversion of relevant CA-7 and CA-11 components into
corresponding CONTROL-M job scheduling definition parameters and AutoEdit
parameters, and describes the unique CONTROL-M conversion parameters that may
be specified.
Component Conversion Summary

The following conversion tables list CA-7 and CA-11 components that are converted
to corresponding CONTROL-M parameters, with cross-references to the topics dealt
with in this chapter.
NOTE
Item number (Item No.) in the following tables refers to the topic number in this
chapter.
Table 10 Components of the CA-7 Job Definition Screen (JOB) (Part 1 of 2)

CONTROL-M Job Scheduling
CA-7 Parameter Definition Parameter Item No.
JOB MEMNAME, OWNER, GROUP, 1, 3,
TABLE name, Group Entity name 35
MEMBER %%INCLIB, %%INCMEM 1
JCLID MEMLIB 2
SYSTEM APPL 3
JCL-OVRD IN condition (manual) 4
VERIFY IN condition (manual) 5
MAINT Ignore DSN connections 6
HOLD IN condition (manual) 7
EXEC=N OVERLIB=DUMMY 8
PRTY PRIORITY 9
COND-CODE and RO ON PGMST 10
TYPE1 and TYPE2 (tape) RESOURCE 11
CLASS RESOURCE 12
INSERT RMS DO IFRERUN, CONTROL-M JCL 30, 31
steps
UID OWNER 35

Table 10 Components of the CA-7 Job Definition Screen (JOB) (Part 2 of 2)

DONT SCHEDULE DEFINITION ACTIVE FROM, 45
BEFORE/AFTER UNTIL
MAINID SET VAR 40
OWNER OWNER 35
PROMPTS SHOUT WHEN LATESUB 38
CLOCK-TIME SHOUT WHEN EXECTIME 38
Table 11 Components of the CA-7 Job Scheduling Screen (SCHD, JOB)

CA-7 Parameters Definition Parameter Item No.
SCAL CONFCAL, DCAL, WCAL 13
SCHID Schedule Tag, SET VAR 36
ROLL, INDEX SHIFT 14
SBTM FROM, SCHEDULE-PREV-DAY 15
DOTM and LDTM DUE OUT 16
SYMETRIC TASKTYPE=CYC, DATES, 17
INTERVAL nnn D FROM TRGT
Scheduling Information Scheduling criteria 17
Table 12 Components of the CA-7 Job Triggering Screen (SCHD, JTRG)

Job Triggering IN and/or OUT conditions 18
Table 13 Components of the CA-7 Dataset Triggering Screen (SCHD, DTRG)

Dataset Triggering CMEM Rule table 39
Table 14 Components of the CA-7 Job Predecessor/Successor Screens (JOBCONN)

(Part 1 of 2)
DEP-JOB IN condition 19
LEADTM=00 IN or OUT conditions, date=**** 19

Table 14 Components of the CA-7 Job Predecessor/Successor Screens (JOBCONN)

(Part 2 of 2)
DEP-JOB=/ CONTROL 20
DEP-JOB=? ‘maybe’ IN condition 44
DSN IN condition 21
NWK IN condition (manual) 22
USER REQUIREMENTS IN condition (manual) 23
Table 15 Components of the CA-7 Documentation Screens (PROSE)

PROSE data DOCMEM and/or DOCLIB 24
Table 16 Components of the CA-7 Commands Screens

CONTROL-M Job Scheduling Item
CA-7 Command Definition Parameter No.
NXTCYC SET=OFF IN condition (manual) 32
Table 17 Components of the CA-7 Virtual Resource Management Screen (RM/RSRC)

CA-7 Resource Type Definition Parameter Item No.
EXC CONTROL 25
SHR CONTROL 25
RCT RESOURCE 25
CRQ IN condition (manual) 25
Table 18 Components of the CA-7 Modification to Resolved Schedule Dates Screen

MODSTAT=CURRENT DCAL 13

Table 19 Components of the CA-7 or CA-11 JCL Parameter, Statement, or Step

CONTROL-M or CONTROL-M/Restart
CA-7 or CA-11 JCL Parameter, Job Scheduling Definition Parameter
Statement, or Step or AutoEdit Parameter Item No.
# HLD IOATEST utility 46
# JCL IN condition (manual) 4
# JI, # JO, # JEND, # X1, # XO, # XEND AutoEdit Statements 26
# MNT Ignore DSN connections 6
# NOX %%GOTO AutoEdit statement 47
# MSG IOANOTE utility 48
# NTR Suppress OUT Conditions 18
# RES PRIORITY, SHOUT WHEN 9,12,
EXECTIME, 33, 38
RESOURCE, CTMRELRS utility
# SCC ONPGMST 10
# VER IOATEST utility 49
CLASS=jobclass RESOURCE 27
USER=userid OWNER 35
GROUP=groupid OWNER 35
NOTIFY=userid OWNER 35
DEMAND[H] CONTROL-M JCL step, 7,9,
IN condition, PRIORITY, 28,12
RESOURCE, DESC
POST CONTROL-M JCL step 28
RESCHNG CONTROL-M JCL step 33
CA-11 non-restartable steps CONTROL-M/Restart CTRNORST 29
DD statement
//*CA-11 comments statement CONTROL-M/Restart parameters 30
CA-11 U11RMS steps CONTROL-M/Restart parameters 31
JES ROUTE PRINT statement SYSOUT 42
Table 20 Components of the CA-7 or CA-11 Initialization File Statement (Part 1 of 2)

CA-7 Initialization File Statement Definition Parameter Item No.
JCL,...DSN=dsname MEMLIB 2
JCL,...ALT=nnn OVERLIB 37

Table 20 Components of the CA-7 or CA-11 Initialization File Statement (Part 2 of 2)

CA-7 Initialization File Statement Definition Parameter Item No.
CPU, ... HOST=JESn JES2 or JES3 Jcl statements 40
RESTART, RMS=xx, CONTROL-M/Restart parameters 31
PROCRMS=procname,
PARMRMS=parm
Table 21 Components of the CA-7 CALENDAR Macro

CA-7 CALENDAR Macro Parameters Definition Parameter Item No.
OPTION=SCHDYONLY DCAL scheduling criteria 17(2)
YEAR, SCAL, MONTHS, CONFCAL 13
SCHDAYS, NOSCHDY
Table 22 Components of CA-7 Workload Balancing Macros

CONTROL-M Job Scheduling Item
CA-7 Workload Balancing Macros Definition Parameter No.
TAPE1 NAME=xxx, MXTAL=nnn RESOURCE 11
TAPE2 NAME=xxx, MXTAL=nnn RESOURCE 11
INITR TOTAV=nnn ... RESOURCE 41
CLBARR BARx=nnn RESOURCE 12
Table 23 CA-DRIVER Components

CA-DRIVER Command CONTROL-M AutoEdit Statement Item No.
DPROC %%SET 51
(D)STEP %%LABEL 52
(D)GOTO %%GOTO 53
(D)SET %%SET 54
(D)IF %%IF 55
DATA, DEND %%INCLIB, %%INCMEM 56
(D)NEST %%INCLIB, %%INCMEM 57
(D)ABORT/DFLUSH %%ABORTED 58
Variable parameters %% variables 59
Date functions date-functions 60
Attribute (L',T') functions %%$LENGTH, %%$TYPE 61

Component Conversion Detail

The items in the following section describe the conversion of CA-7 components in
more detail.
1. JOB and MEMBER

In CA-7, the job name is specified in the JOB parameter of the CA-7 CPU Job
Definition screen and serves as the only job identifier. The JCL member name is
specified in the MEMBER parameter of the CA-7 CPU Job Definition screen.
In CONTROL-M, the job name is determined at time of submission and the JCL
member name is specified in the MEMNAME job scheduling definition parameter.
In CONTROL-M, job grouping is performed by defining all jobs related to one

application in one scheduling table. The CA-7 head-of-tree job names are used by the
conversion tool to name the CONTROL-M scheduling tables.
The CONTROL-M scheduling table name is also specified as part of the

CONTROL-M GROUP parameter. This scheduling table name supplies a common
name to the set of related jobs in a Group scheduling table. The scheduling table
name also acts as the Group entity name.
The conversion tool specifies the CA-7 job name in the CONTROL-M MEMNAME
parameter. If the CA-7 job name differs from the CA-7 MEMBER name, such as when
several CA-7 job definitions use a single JCL member, a special JCL INCLUDE
member, with the same name as the CA-7 job name, is created in the INCLIB library
and in the DAINCLIB DD statement, and a warning message is issued. The member
contains a CONTROL-M AutoEdit control statement (%%INCLIB) that copies the JCL
from the member identified in the CA-7 MEMBER parameter. In addition, you can
install the CONTROL-M job submission exit (Exit 2) to simulate CA-7 processing. For
more information, see the description of Exit 2 in the INCLIB library section of
“Step 13 - Customize CONTROL-M and Install User Exits” on page 85.
The conversion tool also uses the CA-7 job name to convert CA-7 job triggers and
connections into CONTROL-M IN and OUT conditions, as detailed in “18. Job
Triggering and # NTR” on page 111.

2. JCLID
The CA-7 JCLID is a number from 000 through 253 that identifies the JCL library for a
particular job. The library names are contained in the user-modified CA-7 Initdeck in
the DSN parameter of the JCL Initialization statements. For more information on
CA-7 Initdeck, see the discussion of the input to JOB3 in “JOB3 - Create CONTROL-M
Scheduling Tables and CMEM Rules” on page 50.
The conversion tool specifies the CA-7 JCL library name in the MEMLIB
CONTROL-M job scheduling definition parameter. If the JCLID of a job does not
correspond to any JCL initialization statements, the MEMLIB parameter is set to
GENERAL.
The JCLID parameter is not required for non-executable jobs, that is, when EXEC is
set to N in the CA-7 JOB screen.
The CA-7 JCLID value 254 indicates use of the CA-7 Special Override library. For
more information on how to obtain the equivalent functionality in CONTROL-M, see
Chapter 1, “Conceptual Overview.”
3. SYSTEM
The SYSTEM parameter in the CA-7 JOB screen is an optional parameter that
associates the job with an application system name.
The CONTROL-M APPL parameter is used to supply a common descriptive name to

a set of related groups of jobs. The conversion tool creates the CONTROL-M APPL
parameter from the CA-7 SYSTEM name.
4. JCL-OVRD and #JCL

The CA-7 JCL-OVRD job definition parameter indicates whether, before it can be
submitted, the job requires manual JCL overrides, such as specifying a tape serial
number in the JCL of the job. Similarly, the CA-7 # JCL override statement in the JCL
member specifies that the job requires manual JCL overrides.
In CONTROL-M, such modifications are easily performed by the AutoEdit facility.

For more information on the AutoEdit facility, see the CONTROL-M for OS/390 and
z/OS User Guide.
The conversion tool adds a manual IN condition to the CONTROL-M job scheduling
definition to prevent the automatic submission of the job. The format of the condition
is:

JCL_OVERIDE_jobname
where jobname is the CONTROL-M MEMNAME.
5. VERIFY
The CA-7 VERIFY job definition parameter indicates whether the job requires manual
verification before it can be submitted.
is:
VERIFY_JCL_jobname
6. MAINT and #MNT

The CA-7 MAINT job definition parameter indicates whether the job is a maintenance
job that does not require production data sets, such as MVS and JES utilities, backups,
and the like. For such jobs, CA-7 ignores input data sets requirements. Similarly, the
CA-7 # MNT override statement in the JCL member specifies that the job is a
maintenance job.
The conversion tool ignores the DSN connection for MAINT jobs.
7. HOLD and DEMAND[H]

The CA-7 HOLD job definition parameter indicates whether the job is held when it
enters the Request Queue. In addition, the CA-7 DEMANDH command indicates that
the demanded job is to be placed on hold in the Request Queue.

definition to indicate that the job is held. The format of the condition is:
HELD_jobname
Setting the TYPE parameter to RES in the DEMAND command indicates that the job
must be scheduled in restart or rerun status, and that the job is to be placed into the
Request Queue with a restart requirement.
definition to indicate that the job has a restart requirement. The format of the
condition is:
RESTART_jobname
8. EXEC
The CA-7 EXEC job definition parameter indicates whether the job must be executed.
If N is specified, the job does not execute, but CA-7 simulates a normal completion.
In CONTROL-M, set the OVERLIB parameter to DUMMY to prevent the job being
submitted.
If EXEC is set to N in the CA-7 job definition, the conversion tool sets the OVERLIB
parameter of the CONTROL-M job scheduling definition to DUMMY.
NOTE
The CONTROL-M OVERLIB parameter, not the MEMLIB parameter, is set to
DUMMY, in order to preserve the original library specification (if any).
9. PRTY, #RES and DEMAND[H]

The CA-7 PRTY job definition parameter specifies job submission priority. Job
priority can be any value from 0 through 255. A value of 255 indicates an express job.

Similarly, job submission priority is determined by the values of the following

parameters in the JCL member, which override the value in the CA-7 PRTY
parameter:
■ the PRT parameter in the CA-7 # RES override statement

■ the PRTY parameter in the CA-7 DEMAND[H] command
If priority values appear in both the # RES and DEMAND[H] statements, that in the
# RES statement takes precedence.
The CONTROL-M PRIORITY job scheduling definition parameter uses two

alphanumeric characters to set job priority.
The conversion tool transforms the CA-7 numeric value to an alphanumeric value
while maintaining priority order. This is achieved by converting the two high order
digits of the CA-7 PRTY from 00-25 to A-Z, and not converting the low order digit.
The conversion tool supports CA-7 express priority (when PRTY is set to 255), which
is used to bypass Workload Balancing priority scheduling criteria, by defining the job
as a critical path, that is, by specifying *5 in the CONTROL-M PRIORITY parameter.
For more information, see the CONTROL-M for OS/390 and z/OS User Guide.
10. COND-CODE, RO and #SCC

The CA-7 COND-CODE and RO job definition parameters can be used to define
job-level condition code checks to determine whether a job is considered successful or
not. The COND-CODE parameter indicates the value for the comparison, and the RO
parameter specifies the relational operator. The default setting of RO is 0, when no
condition code checking occurs. Similarly, the CA-7 # SCC override statement in the
JCL member specifies step-level condition code checking.
The CONTROL-M job scheduling definition enables the user to set condition code
checking at step level as well as job level, using the ON PGMST CODES
post-processing parameters. By default, CONTROL-M considers a job as ENDED OK
if no step condition code is higher than 4.
The conversion tool converts the COND-CODE and RO values to ON PGMST

post-processing parameters in the CONTROL-M job scheduling definition. These
parameters reflect the same condition code checking as that performed by CA-7. If the
RO value is # S, the condition code checks specified in the # SCC statements are used
and incorporated as ON PGMST post-processing parameters in the CONTROL-M job
scheduling definition.
The following list details the exact # SCC conversion logic:

Table 24 CA-7 $SCC Conversion Logic

CA-7 #SCC JCL Statement CONTROL-M ON PGMST Conversion
COND=(nn,GE,...) CODES >Cnn DO OK
COND=(nn,LE,...) CODES <Cnn DO OK
COND=(nn,GT,...) CODES >C(nn-1) DO OK
COND=(nn,LT,...) CODES <C(nn+1) DO OK
COND=(nn,EQ,...) CODES NCnn, >C0000 DO OK
COND=(nn,NE,...) CODES Cnn DO OK (for nn>4)
CODES >Cnn DO NOTOK (for nn<5)
COND=(nn-mm,EQ,...) CODES <Cnn OR >Cmm DO OK
COND=(nn-mm,NE,...) CODES <C(mm+1) DO OK
>C(nn-1)
COND=(,FL) CODES FLUSH DO OK
COND=(n, oper, *) PGMST +EVERY
In addition to permitting a step name operand following the Relational Operator,

such as GE or LE, the conversion tool also allows specification of the procedure step
name as follows:
# SCC COND=(nn,ro,stephame.procstepname)
where
■ nn is the return code of the step

■ ro is the Relational Operator value
■ stepname is the name of the step which returned nn
■ procstepname is the name of the procedure in the step which caused the step to
return nn
This statement is converted to CONTROL-M as
ON PGMST stepname PROCST procstepname CODES xxxx
as shown in the above table.
For processing step names in the form *-stepname, see “&SCCGLBL” on page 156.
When the CA-7 job definition indicates default checking, unless you set the value of
the MAXCCOK parameter in CTMPARM to 4095, the conversion tool sets the
following CONTROL-M specification:
ON PGMST ANYSTEP PROCST CODES C****

DO OK

11. TYPE1 and TYPE2

The CA-7 TYPE1 and TYPE2 job definition parameters specify the number of tape
drives used by a job. CA-7 manages only two tape drive types by referencing a CA-7
logical device type, not the MVS device types.
CONTROL-M handles tape drive resources, and any other critical computer
resources, as quantitative resources. The CONTROL-M job scheduling definition
RESOURCE parameter specifies the resource name and the quantity used by a job.
The resource names specified in the &TAPE1 and &TAPE2 conversion parameters in
the DEFAULTS member are used by the conversion tool to represent the two CA-7
tape drive types. The CA-7 TYPE1 and TYPE2 C (calculated) amounts are converted
to CONTROL-M job scheduling definition RESOURCE specifications. When a
non-zero tape resource manual override (M) amount is specified, this amount is used
instead of the calculated (C) tape resource amount.
The resources above must be added to the CONTROL-M Resources file with a
quantity corresponding to the MXTAL parameter of the CA-7 workload balancing
TAPE1 and TAPE2 macros.
12. CLASS, #RES and DEMAND[H]

In CA-7, class barriers are workload balancing parameters that establish the
maximum number of jobs that can be submitted concurrently in the associated job
class.
The CONTROL-M job scheduling definition RESOURCE parameter is used to control

all job resource sharing, as well as preventing concurrent runs of jobs.
If the &CLASBAR conversion parameter, which is described in “&CLASBAR” on

page 143, is set to Y, the conversion tool converts the CA-7 CLASS by specifying a
RESOURCE parameter with a quantity of 1, in the format
CLASS_BAR_jobclass
where jobclass is the CA-7 workload balancing job class.
The CA-7 workload balancing job class can also be specified using the value in the
CLASS parameter in the # RES override statement and the value in the CLASS
parameter in the DEMAND[H] command in the JCL member. These override the
value in the CA-7 CLASS parameter.

The above resources must be added to the CONTROL-M Resources file with a
quantity corresponding to the CA-7 class barrier specification, which is defined in the
BARx parameter of the workload balancing CLBARR macro.
13. SCAL
CA-7 calendars are defined for one year only. A CA-7 Base calendar ID has the format
SCALyyxx
where:
■ yy is the target year

■ xx are two unique characters used during initial creation of the calendar
A CONTROL-M calendar definition can contain multiple years, and its name can be
from 1 through 8 characters in length.
The CONTROL-M job scheduling definition has several optional calendar

parameters, namely DCAL, WCAL and CONFCAL. For more information on these
parameters, see the CONTROL-M for OS/390 and z/OS User Guide.
Calendars are automatically created as described in the following situations.
When the user specifies CA-7 Base calendars in JOB1

The CA-7 schedule definition must contain a Base calendar. It may also contain
additional optional calendars for each schedule-ID. These are used to verify, or
resolve, the requested schedule days against the days specified as working days in
the calendar. When a specific day is not a working day, for example, because it is
a holiday or weekend, the ROLL parameter determines the schedule. The conversion
tool uses the CA-7 SCAL Base calendar ID as the CONTROL-M CONFCAL calendar
based on the ROLL specification. For more information on the ROLL parameter, see
the next item, “14. ROLL, INDEX” on page 107.
The following naming convention is used by the conversion tool when converting
CA-7 Base calendars to CONTROL-M calendars:
■ The first six characters are a constant value, as specified in the &CALPREF
conversion parameter. For more information, see “&CALPREF” on page 143.
■ The last two characters are the last two characters of the CA-7 calendar name, that
is, the SCAL=xx that was specified by the PRINT command of JOB1.
Both standard and non-standard (periodic) calendars can be created.

Base calendars created with the CA-7 OPTION=SCHDYONLY are marked as

SCHDYONLY. For more information, see “Step 3 - Modify and Run the JOB0
Member” on page 74.
When a CA-7 job has the SCHDMOD CURRENT indicator set

in its scheduling information
The CA-7 Modification to Resolved Schedule Dates screen (D.B.2.7) enables a user to
permanently modify a resolved schedule for a job or input network without having to
redefine the schedule. This modification is indicated by a status of CURRENT.
A list of all CA-7 job schedule members that have been modified using the
SCHDMOD screen is available in CA7ER789, the CA-EARL CURRENT SCHDMOD
report. For more information, see the CA-7 Management Reporting Guide.
The user can, globally or on an individual application basis, determine whether

SCHDMOD CURRENT processing is to be performed on jobs whose schedules are so
marked. For more information, see “&SCHDMOD” on page 156, and the description
of the Application List file in “JOB2 - Create the Applications List, Calendar Libraries,
and Calendar Names List Files” on page 46. SCHDMOD CURRENT processing is the
same as the processing described below.
When CA-7 job schedule parameters cannot be consistently

converted to CONTROL-M Basic Scheduling parameters
The CA-7 job schedule parameters cannot be consistently converted to CONTROL-M
Basic Scheduling parameters when
■ the conversion tool encounters a CA-7 SYMETRIC parameter, and the calendar
used for the schedule was created with OPTION set to SCHDYONLY, or the CA-7
SPAN parameter is greater than 45
■ it is determined by the conversion tool that the CA-7 scheduling definition for a
particular Schedule ID cannot automatically be converted to CONTROL-M Basic
Scheduling parameters
■ a CA-7 job schedule utilizes a nonstandard (periodic) calendar
■ SCHDMOD CURRENT processing is requested (as described in the preceding

section)
When one of these cases is encountered, the following occurs:

■ JOB2 builds an auxiliary calendar in the CONTROL-M Calendar library (DACAL)

that is based on the CA-7 scheduling definition of the job in the LSCHD report. For
more information on auxiliary calendar naming conventions, see the description of
the CONTROL-M Calendars library among the Output Files under “JOB2 - Create
the Applications List, Calendar Libraries, and Calendar Names List Files” on
page 46.
■ The auxiliary calendar is marked as SCHDMOD-CURRENT if the CA-7 schedule

in the LSCHD report of the corresponding job indicates that at least one
modification made to its schedule ID is still in effect, that is, the modification has a
status of CURRENT. Otherwise, the calendar is marked as AUXILIARY CAL.
■ For all jobs associated with the Schedule ID, the CONTROL-M job scheduling
definitions in the scheduling table are modified as follows:
— the auxiliary calendar name is placed into the DCAL parameter

— the DAYS and MONTHS parameters are set to ALL
— the WDAYS, AND/OR, CONFCAL, WCAL, and SHIFT parameters are cleared
NOTE
Auxiliary calendars placed into the CONTROL-M Calendar library are 1-year
calendars only, spanning January through December or July through June,
depending on when the CA-7 schedules were RESOLVEd. You must extend these
calendars to multiple years as soon as possible.
You can use CONTROL-M utilities to
■ utilize user-defined calendars rather than the auxiliary calendars
■ reduce the number of calendars defined to CONTROL-M by defining your

own CONTROL-M Basic Scheduling parameters, such as DAYS or WDAYS.
For more information, see the discussion of the creation of auxiliary calendars in
the description of the use of the CTMXREF CONTROL-M utility in “Step 14 -
Final Adjustments” on page 87.
14. ROLL, INDEX

The CONTROL-M SHIFT job scheduling definition parameter encompasses both the
CA-7 ROLL parameter and the CA-7 INDEX parameter. The SHIFT parameter has the
format xyyy

where
■ the value of x corresponds to the ROLL parameter value

■ the value of yyy corresponds to the INDEX parameter value
Each of these conversions is described below.
The CA-7 ROLL schedule definition parameter indicates the action CA-7 is to take
when verifying (resolving) schedule parameters against the CA-7 Base calendar.
CA-7 ROLL action values are converted to CONTROL-M as follows:
1. When ROLL is set to D, no action is to be performed and the requested schedule

day is to be skipped. In such a case, the CONTROL-M SHIFT parameter in the
CONTROL-M job scheduling definition is left blank.
2. When ROLL is set to B, the requested schedule day is to be rolled backward to the
previous calendar working day. In such a case, SHIFT is set to < in the
CONTROL-M job scheduling definition.
3. When ROLL is set to F, the requested schedule day is to be rolled forward to the
next calendar working day. In such a case, SHIFT is set to > in the CONTROL-M
job scheduling definition.
4. When ROLL is set to N, the requested schedule day must be kept regardless of the
calendar definition (except for DAILY scheduling). In such a case, SHIFT is set to @
in the CONTROL-M job scheduling definition.
When the CA-7 Base calendar is a non-standard (periodic) calendar, the

CONTROL-M CONFCAL and SHIFT parameters are omitted, regardless of the CA-7
ROLL value.
The CA-7 INDEX schedule definition parameter is used to specify an adjustment to

schedule days. After exercising the ROLL option, the schedule is adjusted forward or
backward by the number of working days specified in INDEX. This value (not
exceeding 62), including sign, is copied to the CONTROL-M SHIFT parameter in the
yyy portion of the value, as described earlier in this item.
15. SBTM
The CA-7 SBTM schedule definition parameter specifies a submission time
prerequisite. CA-7 does not submit the job before this time.
The CONTROL-M FROM job scheduling definition parameter specifies the earliest
time the job can be submitted.

The conversion tool assigns the value of the CA-7 SBTM parameter to the
CONTROL-M FROM parameter. If no value is set in the CA-7 SBTM parameter, the
conversion tool can optionally use the deadline start time, the STARTM parameter on
the LJOB report. For more information, see “&STARTM” on page 158
NOTE
The CONTROL-M SAC parameter is set when the converted FROM time is between
midnight and the CONTROL-M New Day time, as explained in “New Day
Processing and Schedule Scan” on page 28.
16. DOTM and LDTM

The CA-7 DOTM and LDTM schedule definition parameters specify the due-out time
and lead time used by CA-7 for scheduling. DOTM (due-out time) specifies the time
that the job must end. LDTM (lead time) specifies the execution time of the job plus
any additional setup time. CA-7 uses the value of these parameters to calculate the
start time, that is, the time at which the job must be placed on the Request Queue.
The CONTROL-M DUE OUT job scheduling definition parameter, or the DOTM
parameter of a demanded job, specifies a time by which a job must finish execution.
The conversion tool assigns the value of the CA-7 DOTM parameter to the
CONTROL-M DUE OUT parameter that is used in calculating the time at which a job
must be submitted.
17. Scheduling Information

Many of the differences between CONTROL-M and CA-7 schedule definitions are a
matter of terminology only. The conversion tool handles such differences
automatically. For example, CA-7 WEEKLY is WDAYS in CONTROL-M, MONTHLY
is DAYS, and ANNUAL is DATES.
Although the following CA-7 scheduling specifications are converted automatically,

they require additional clarification.
1. MONTHLY, NDAY=ddd, WEEK=xx
This CA-7 schedule specification means “do not run on DAY ddd WEEK xx.” The
conversion tool converts this schedule combination by specifying the weeks to
schedule the job instead of specifying the weeks not to schedule the job, as shown
in the following example:

Table 25 Scheduling Information Conversion Example

CA-7 WEEKLY DAY=THURS
MONTHLY NDAY=THU WEEK=02
NDAY=THU WEEK=03
translates to:
CONTROL-M WDAYS D4W1,D4W1,D4W5,D4W6
If xx is -00, the CONTROL-M DAYS parameter is set to L1, L2, ..., L7 or -L1, -L2, ...,
-L7, depending on whether the week is to be included or excluded; the
CONTROL-M WDAYS parameter is set to the value of the CA-7 DAY.
2. A CA-7 calendar definition can specify OPTION=SCHDYONLY. This calendar

definition parameter changes the representation of the CA-7 MONTHLY RDAY
schedule definition parameter from processing days to calendar (working) days.
This is converted by specifying the calendar in the CONTROL-M DCAL parameter
and the days of the month as working days, in Dn format.
3. SYMETRIC DAY=ddd, SPAN=nnn
SYMETRIC schedules are converted to job definitions with the following

attributes:
■ the SCHEDULE TAG corresponding to the CA-7 SCHEDULE-ID contains
— a DATES value of ddmm (or mmdd) derived from the julian date ddd specified
in the CA-7 START parameter
— a MAXWAIT value of 99, so the job is never removed from the Active Jobs
File
■ the INTERVAL parameter in the job definition is set to nnn D FROM TRGT,
meaning the job must be recycled every nnn days from the date scheduled for
the current job run
SYMETRIC schedules are only converted in this way if
■ the calendar corresponding to the schedule-ID was not created with OPTION
set to SCHDYONLY
and
■ the value in the CA-7 SPAN parameter does not exceed 45

NOTE
When an online P (Plan) command in Screen 2 is issued for a converted SYMETRIC
job, the calendar plan shows the job as being scheduled on only one date, that
specified in the DATES parameter. In most cases, this does not match the CA-7
schedule (LSCHD) for the job. This is because the conversion tool converts the job
as a cyclic job. Reruns of cyclic jobs are not displayed in response to the Plan
command if the INTERVAL parameter is set to span more than one day.
18. Job Triggering and #NTR

In CA-7, the execution sequence of jobs within an application is specified by job
triggering. Job completion with acceptable condition codes triggers the next job or
jobs until the entire application is completed.
In CONTROL-M, job sequence is specified using prerequisite conditions. Each job

that finishes OK according to its specification in the CONTROL-M job scheduling
definition can add a prerequisite condition to the IOA Conditions file. The condition
is specified as an OUT condition in the job scheduling definition.
The conversion tool builds condition names in the format
schedule-table_jobname_OK ODAT
The variable schedule-table is the CONTROL-M scheduling table name. The variable
jobname is the MEMNAME
If there are duplicate job names within the same scheduling table, then the ‘K’ from
‘_OK’ is replaced with the occurrence number of the job, (2 – 9, A – J, L – Z, @).
Every converted job contains an OUT condition of this type, and all triggered jobs
contain this condition as an IN condition. This mechanism ensures that the
CONTROL-M execution flow is the same as in the CA-7 job triggering definitions.
The CA-7 # NTR override statement in the JCL member causes suppression of the job
triggering that is otherwise initiated by successful job completion.
The conversion tool converts # NTR override statements in JCL members by

suppressing the creation of OUT conditions in the relevant job scheduling definitions.
The conversion tool builds CONTROL-M scheduling tables containing all the
application jobs. This means that an entire job tree, based on the CA-7 triggering
information, is contained in one CONTROL-M scheduling table.
For more information, see “CONTROL-M Scheduling Table Creation” on page 27

19. DEP-JOB
The CA-7 DEP-JOB job connection parameter specifies a predecessor job on which the
job specified in the JOB parameter is dependent. This causes the dependent job to
wait until the job specified in the DEP-JOB parameter has completed OK.
The conversion tool builds IN and OUT conditions in the form
dep-jobname_OK ODAT
where dep-jobname is the CONTROL-M MEMNAME of the job on which the job
specified in the JOB parameter is dependent.
For example, if the CA-7 job connection definition of JOBB states that JOBB is
connected to JOBC using the specification DEP-JOB=JOBC, this means that JOBB is
dependent on JOBC.
The conversion tool converts this CA-7 job connection by specifying the IN condition
JOBC_OK in the CONTROL-M job scheduling definition of JOBB, and specifying the
OUT condition JOBC_OK in JOBC. For alternate naming convention considerations,
incorporating both the predecessor and successor job names, see “&DEPJCND” on
page 150.
When incorporating demanded jobs, as well as jobs triggered by demanded jobs, into
a CONTROL-M job scheduling table definition from a Batch Terminal step, such
as SASSTRLR, in the CA-7 JCL, the IN or OUT condition is built in a modified format,
as follows:
jobname_dep-jobname_sched-id ODAT
where
■ dep-jobname is the name of the JCL member containing the CA-7 DEMAND
command
■ jobname is the job name of the demanded job, that is, the name in the CA-7 JOB
parameter
■ sched-id is the SCHID value specified in the CA-7 DEMAND command
If SCHID is not specified in the DEMAND command, a value of 001 is assumed.
When the &DEMAND conversion parameter, which is described in “&DEMAND” on

page 148, is set to CA7, the demanded job itself is created without the above IN
condition. The CONTROL-M CTMJOB batch utility can then force the job into the
Active Jobs File, using the CTMUTIL procedure described in Appendix D, “The
CTMUTIL Conversion Utility”

When the DEMAND command contains a DEPJOB parameter value, an IN condition

is built in the same format as that described above, and is placed in a job that has the
name defined in the CA-7 JOB parameter.
All values of the CA-7 job connection LEADTM (the satisfaction lead time in hours),
including 99, are ignored, except for the value 00. When a LEADTM of 00 is specified,
the IN and OUT conditions created in the job scheduling definition specify ****
instead of ODAT, to make the condition not dependent on the date.
In addition, an OUT statement deletes the condition corresponding to its IN condition

from the IOA Conditions file upon successful completion of the job. For information
regarding the forced deletion of job connection conditions regardless of the value of
the LEADTM parameter, see “&DELCOND” on page 147.
For more information, see “DEMAND[H] and POST Commands” on page 30.
20. DEP-JOB=/jobname
The CA-7 DEP-JOB job connection parameter can specify a job name preceded by “/”
(slash). This type of job connection is referred to as a negative job dependence, in that
CA-7 prevents the connected job and the job specified in the DEP-JOB parameter
from executing concurrently. The job specified in the DEP-JOB parameter runs only
when the connected job ends (or abends), but it is not triggered by the connected job.
The CONTROL-M CONTROL job scheduling definition parameter is used to control

all job resource sharing, as well as preventing concurrent runs of jobs.
The conversion tool converts this CA-7 job connection by specifying the CONTROL
parameter in the format
EXCLUSIVE_jobname
where jobname is the connected CA-7 job name.
This CONTROL resource is specified for the connected job with the Exclusive option,
and for the DEP-JOB job with the Shared option.
21. DSN
The CA-7 DSN job connection parameter specifies an input data set name as a
prerequisite for a job. This type of job connection instructs CA-7 to suspend the
execution of a job until the input data set is created.

For example, if the CA-7 job connection definition states that JOBB has an input data
set connection to DSN.OUTFILE, the job is dependent upon the creation of that data
set.
The conversion tool converts this CA-7 DSN job connection by changing it to a job
connection of the CA-7 DEP-JOB type, which specifies in CONTROL-M IN and OUT
conditions the job name that creates the data set in the DSN parameter. The valid
syntax is:
creating-job_DS
where creating-job is the job that creates the data set.
For other naming convention considerations relating to the names of both creating
and successor jobs, see “&DEPJCND” on page 150.
A DSN connection is ignored when a CA-7 job definition states any of the following:
■ Job is a MAINT job (maintenance job)

■ DSN is marked as “*PERM DSN*”
■ DSN is marked as “PERM FOR JOB”
■ DSN is marked as “CREATED BY **NONE**”
■ DSN is marked as “CREATED BY nnn JOBS”, where nnn is any number
22. NWK
The CA-7 NWK job connection parameter is used to specify the network prerequisites
of a job.
The conversion tool converts this CA-7 job connection to a manual IN condition of the
form
NW_jobname
23. USER REQUIREMENTS

The CA-7 USER REQUIREMENTS job connection parameter specifies user-defined
prerequisites for a job. It contains up to 36 characters of text. CA-7 suspends the
execution of a specific job until this user-defined prerequisite is manually posted.

In CONTROL-M, a manual prerequisite condition prevents the submission of a job

until the condition is added manually to the IOA Conditions file.
The conversion tool converts this CA-7 connection by specifying a long IN condition
in the CONTROL-M job scheduling definition of the connected job. The format of the
string is
jobname_usertext
The variable jobname is the CONTROL-M MEMNAME of the CA-7 connected job.
The variable usertext is at least the first 30 characters of the USER REQUIREMENTS
parameter
24. PROSE
In CA-7, job documentation (PROSE) optionally describes each job. The PROSE data
is stored in the CA-7 database, and is maintained by means of the PROSE on-line
screens.
In CONTROL-M, documentation can be specified for each job. The documentation

data of each job is contained in one library member. This documentation member can
be maintained from the Job Scheduling Definition screen (Screen 2).
The conversion tool converts the CA-7 PROSE data by creating a member in the
CONTROL-M Documentation library for each job that has associated PROSE data.
25. Virtual Resource Management

The Virtual Resource Management facility enables the definition of job-to-resource
dependencies that control execution of the job according to resource availability at job
submission time. For more information on this facility, see “Virtual Resource
Management (VRM)” on page 25.
The types of resources managed by this facility, and the way the conversion tool
converts them to CONTROL-M, are as follows:
■ Shared and Exclusive resources
A Shared resource connection enables multiple jobs to execute at the same time,
even though they may all use the same resource. An Exclusive resource is used to
indicate that the job requires exclusive use of a resource, so that no other job
requiring the resource can execute until the end of the exclusive use job.

In CONTROL-M, a CONTROL parameter is used to control resource sharing, and

is defined with Exclusive or Shared options. For more information on the
CONTROL parameter and its subparameters, see the CONTROL-M for OS/390 and
z/OS User Guide.
■ Corequisite resources
In the case of a Corequisite resource connection, whether a job executes depends

on whether the status of the specified resource is active or inactive.
In CONTROL-M, these resources are converted into manual IN conditions in the

format
status_res-name
where:
— status is either A (Active) or I (Inactive)

— res-name is the name of the resource
You must add or delete these manual conditions from the CONTROL-M Resource
file when the resource becomes active or inactive.
■ Resource Count resources
The availability to a job of a Resource Count resource depends on the count or

number specified for this resource and job. When a job-to-resource connection is
made to a Resource Count resource, the specified number identifies the total
number of occurrences of this resource that are used by this job.
In CONTROL-M, a RESOURCE parameter is used to specify Quantitative

resources and the actual quantity of the resource that the job requires. For more
information on the RESOURCE parameter, see the CONTROL-M for OS/390 and
z/OS User Guide.
■ Address Space resources
These resource types are not supported by the conversion tool.
All CA-7 virtual resources have a FREE option associated with them that determines
the resource availability at job submission and job or step completion. If you want,
you can reflect the FREE option in the format of the converted resource name, by
specifying the &RESFREE conversion parameter, which is described in “&RESFREE”
on page 156.

26. #JI, #JO, and #JEND, #XI, #XO, and #XEND Statements
The CA-7 override statements # JI, # JO, and # JEND, and similarly, # XI, # XO, and
# XEND, indicate JCL statements that are to be included, or omitted, based on
scheduling criteria.
The CONTROL-M AutoEdit %%IF, %%ELSE, %%ENDIF, %%GOTO and %%LABEL

control statements provide a Boolean “IF” logic capability.
The conversion tool converts the # JI, # JO, # JEND, # XI, # XO, and # XEND) statements
to corresponding CONTROL-M AutoEdit statements. Only the CA-7 RPT parameter
is ignored. The CA-7 ID parameter is converted to the AutoEdit variable %%SCHID
which, for scheduled jobs, is derived from the first 3 characters of the CONTROL-M
%%$TAG system variable.
The %%$TAG system variable is the Schedule Tag name of the Schedule Tag that
causes the job to be submitted. All Schedule Tag names are of the form
sched-ID_head-of-tree-jobname
For non-scheduled, independent (single-purpose) jobs, sched-ID is set to 000. For

demanded jobs and jobs triggered by demanded jobs, the CONTROL-M job
scheduling definition contains a SET VAR %%SCHID AutoEdit variable, the value of
which is set from the SCHID parameter in the CA-7 DEMAND statement for
demanded jobs.
The CA-7 BD, ED, OA, OB, BT, and ET parameters are converted to the
system-defined date and time AutoEdit variables %%[O]YEAR, %%[O]JULDAY, and
%%TIME, based on the setting of the CA-7 CV subparameter. %%OYEAR and
%%OJULDAY are the conversion results when CV is set to DO or DL. %%YEAR and
%%JULDAY are the conversion results when CV is set to CU.
NOTE
CA-7 JCL override statements (# NTR, # SCC, and so on) embedded within a # JI or
# JO block are incorporated into the job scheduling definition with a schedule ID
corresponding to the ID parameter of the # JI or # JO statement.
The following examples illustrate how the # JI and # JO override statements are
converted.
Example 1
#JI,ID=(1,5,10,15),BD=97010,ED=97250,OA=0100,OB=1530,
BT=1010,ET=1212

is converted to:
%%IF X%%$TAG NE X
%%SET %%SCHID = %%SUBSTR %%$TAG 1 3
%%ENDIF
%%IF %%SCHID EQ 001
%%GOTO LABEL0001
%%ELSE
%%IF %%SCHID EQ 005
%%GOTO LABEL0001
%%ELSE
%%IF %%SCHID EQ 010
%%GOTO LABEL0001
%%ELSE
%%IF %%SCHID EQ 015
%%GOTO LABEL0001
%%ELSE
%%GOTO LABEL00XX
%%ENDIF
%%ENDIF
%%ENDIF
%%ENDIF
%%LABEL0001
%%IF %%OYEAR.%%OJULDAY GE 97010
%%IF %%OYEAR.%%OJULDAY LE 97250
%%SET %%HHMM = %%SUBSTR %%TIME 1 4
%%IF %%HHMM GE 0100
%%IF %%HHMM LE 1530
%%GOTO LABEL0002
%%ELSE
%%GOTO LABEL00XX
%%ENDIF
%%ELSE
%%GOTO LABEL00XX
%%ENDIF
%%ELSE
%%GOTO LABEL00XX
%%ENDIF
%%ELSE
%%GOTO LABEL00XX
%%ENDIF
%%LABEL LABEL0002
%%IF %%OYEAR.%%OJULDAY EQ 97010
%%IF %%HHMM GE 1010
%%GOTO LABEL0003

%%ELSE
%%GOTO LABEL00XX
%%ENDIF
%%LABEL LABEL0003
%%IF %%OYEAR.%%OJULDAY EQ 97250
%%IF %%HHMM LE 1212
%%GOTO LABEL0004
%%ELSE
%%GOTO LABEL00XX
%%ENDIF
%%LABEL LABEL0004
.
.
<JCL STATEMENTS>
.
.
%%LABEL LABEL00XX
Example 2
Assume the following CA-7 JCL override statement is in the same JCL member as the
statement in Example 1:
#JO,ID=205-250,BD=97010,ED=98010,CV=CU
It is converted to:
%%IF X%%$TAG NE X
%%ENDIF
%%IF %%SCHID GE 205
%%IF %%SCHID LE 250
%%GOTO LABEL01XX
%%ELSE
%%GOTO LABEL0101
%%ENDIF
%%ELSE
%%GOTO LABEL0101
%%ENDIF
%%LABEL0101
%%IF %%YEAR.%%JULDAY GE 98010
%%GOTO LABEL01XX
%%ELSE
%%GOTO LABEL0102
%%ENDIF

%%LABEL0102
.
.
.
<JCL STATEMENTS>
.
.
.
%%LABEL LABEL01XX
27. JCL Job Class

CONTROL-M Quantitative resources based on the JCL job class can optionally be
added to job scheduling definitions. This may be required at sites where the CA-7
CLASS parameter is used for job grouping purposes, for example, to limit the number
of CICS jobs running concurrently.
If you specified a value other than ' ' (Blank) for the &JOBCLAS conversion
parameter, which is described in “&JOBCLAS” on page 152, the conversion tool
builds quantitative resource parameters with a quantity of one in the format
JOBCLASS_resource-name[_$]
where
■ resource-name is either the user text specified in the JCL Job Class Translation Table
or the JCL job class
■ $ is a mask character
The exact format of the quantitative resource depends on specifications in the Job
Class Translation Table. For details, see “Step 8 - Modify and Run the JOB3 Member”
on page 79.
28. DEMAND[H] and POST

The CA-7 DEMAND[H] Batch Terminal command is used to submit special purpose
jobs. The POST command is used to satisfy the prerequisite conditions of jobs.
CONTROL-M IN conditions are used to specify that a job must wait for the
occurrence of an event before being submitted. A CONTROL-M procedure with the
default name IOACND can be used to add such conditions to the IOA Conditions file.

The way the conversion tool operates depends on the mode set by the &DEMAND
conversion parameter, which is described in “&DEMAND” on page 148. The
conversion tool converts CA-7 DEMAND[H] JCL Batch Terminal step operations to
one of the following:
■ CONTROL-M CTMJOB ORDER commands, to force a job into the Active Jobs file
■ IOACND ADD COND commands that add conditions to the IOA Conditions file.
The CA-7 JCL POST Batch Terminal step operation is converted to CONTROL-M
IOACND JCL steps that add conditions to the IOA Conditions file.
For more information, see Appendix D, “The CTMUTIL Conversion Utility,” in

which the utility that corresponds to the CA-7 Batch Terminal step is described.
For an overview on DEMAND and POST processing, see “DEMAND[H] and POST
Commands” on page 30. For the format of the converted conditions, see “19.
DEP-JOB” on page 112.
The CONTROL-M DESC parameter of the demanded job scheduling definition is set
to contain the string “DEMANDED-JOB,” and the DESC parameter in jobs triggered
by the demanded job contains the string “DEMANDED-JOB-BRANCH.” DESC also
contains the schedule-ID.
NOTE
The parameters supported in the DEMAND[H] command are: JOB, SCHID, DEPJOB,
DOTM, PRTY, CLASS, and TYPE set to RES. The parameters supported in the POST
command are: JOB, NW, USR, and DEPJOB.
The only Batch Terminal commands converted are those specified as input to
programs and procedures listed in the Batch Terminal input file. For more
information, see “JOB4 - Convert JCL Members” on page 56.
The only Batch Terminal commands converted are those in non-concatenated SYSIN,
CA7DATA, and UCC7DATA DD statements, with or without a stepname
qualification.
Only one Batch Terminal command is recognized in each line, and the command
must begin in column 1. It can appear in any one of the following positions:
■ in a PDS member
■ in a sequential data set
■ instream, for example, following the statements //SYSIN DD * or //SYSIN
DD DATA, or no SYSIN statement at all
For more information, see “&PNIBTSD” on page 154.

If Batch Terminal commands appear in the CA-7 PARM parameter on the EXEC
statement, only one command is converted, and the whole of that command must be
contained in one JCL line.
Unsupported Batch Terminal commands in SYSIN and extraneous DD statements are

deleted. PARM parameters that contain unsupported commands are nullified, and
EXEC statement parameters that follow the PARM parameter are ignored.
The CTMUTIL utility is the CONTROL-M equivalent of the CA-7 Batch Terminal
procedure. CTMUTIL serves as the umbrella procedure for invoking IOACND,
CTMJOB and CTMRELRS whenever their functionality is required. For more
information on the CTMUTIL utility, see Appendix D, “The CTMUTIL Conversion
Utility,”
29. CA-11 Non-Restartable Steps

If CONTROL-M/Restart is installed, the UCC11NR and CA11NR DD statements in
CA-11 non-restartable steps are converted to CONTROL-M/Restart CTRNORST
DD statements.
NOTE
In rare cases, the non-restartable step feature may work differently in
CONTROL-M/Restart from the way it works in CA-11. CONTROL-M/Restart first
checks the condition codes, and determines whether a step will run.
If CONTROL-M/Restart determines that the step will not run, it does not continue to
check whether the step contains the CTRNORST DD statement. CA-11, however, first
checks whether the UCC11NR or CA11NR DD statement exists in the step, and
performs step adjustment accordingly. This can cause a job to restart at a different
step when CTRNORST DD statements are utilized than it would if UCC11NR or
CA11NR DD statements were in use.
30. INSERT-RMS and //*CA-11 Comment Statements

The CA-7 INSERT-RMS job definition parameter indicates whether the CA-11
U11RMS JCL step is to be automatically inserted at execution time by CA-7.
The CA-11 comment statement //*CA-11 is used to override the setting specified by
the INSERT-RMS parameter. When the &CTR conversion parameter, which is
described in “&CTR” on page 144, is set to either Y or X, and
■ the CA-7 job definition indicates INSERT-RMS=Y
or

■ a CA-11 comment statement in the JCL of a job, before the first EXEC statement,
specifies
//*CA-11 INSERTRMS=YES
the AUTO-ARCHIVE, SYSDB, and PREVENT-NCT2 parameters are set to Y, and a

DO IFRERUN statement is inserted into the CONTROL-M job scheduling definition.
Specifying //*CA-11 PARM=value causes the conversion tool to process the

statement exactly as if a U11RMS step had been encountered. For more information,
see the following item.
31. CA-11 U11RMS Step

The CA-11 U11RMS JCL step (RUN HANDLER) uses PARM (or TYPRUN) values in
the EXEC statement to control the CA-11 processing mode. When the &CTR
conversion parameter is set to Y or X, the conversion tool analyzes these PARM
values and converts them to the appropriate CONTROL-M/Restart parameters, as
detailed in the following paragraphs. For more information, see “&CTR” on page 144.
■ When the value of PARM is set to P (production processing), R (rerun or restart

processing), or F (format processing), the following occurs:
— The following CONTROL-M/Restart parameters are set to Y (Yes)
■ AUTO-ARCHIVE
■ SYSDB
■ PREVENT-NCT2
— A DO IFRERUN statement is inserted into an ON PGMST scheduling definition
■ When the value of PARM is set to P or F, the DO IFRERUN restart step defaults to
$ABEND or $EXERR, depending on whether the &CTR conversion parameter is
set to Y or X.
■ When the value of PARM is set to R, if startprocstep.startstep and endprocstep.endstep

are included in the PARM parameter setting, these are used in the FROM and TO
subparameters of DO IFRERUN. The CC=nnnn statement in the PARM parameter
is ignored.
■ The procedure name to identify the U11RMS step is determined from the
PROCRMS parameter of the RESTART statement in the CA-7 Initialization file.
If this parameter is not set, a default value of UCC11RMS is used. If this does not
agree with the actual CA-11 usage, which is set out in Table 20 on page 96, you
must insert the correct PROCRMS value in the RESTART statement before running
the conversion.

■ When the value of PARM is set to N (null processing), DO IFRERUN is not

inserted into the job scheduling definition and the PREVENT-NCT2 parameter is
set to N (No) even if the job definition contains the statement INSERT-RMS=Y or a
//*CA-11 comment statement is specified earlier in the JCL of the job. For more
information, see “30. INSERT-RMS and //*CA-11 Comment Statements” on
page 122.
NOTE
The &CTRCONF conversion parameter determines whether manual confirmations of
restarts, using DO IFRERUN, are required.
When the U11RMS step contains the statement PARM=‘R, PSEUDO=YES’, you
must set up a CONTROL-M/Restart simulation run. For more information, see the
CONTROL-M/Restart User Guide.
32. NXTCYC SET-OFF

The CA-7 NXTCYC SET=OFF command causes all regularly scheduled processing
cycles to be indefinitely suspended until the scheduling indicator is manually reset to
SET=ON. Locked jobs are also prevented from processing.
is:
SUSPEND_jobname
33. RESCHNG and #RES

The CA-7 RESCHNG Batch Terminal command is used to change tape drive
resources allocated to a job. Similarly, the CA-7 # RES override statement (TP1 and
TP2 values) in the JCL member can be used to change the high-water tape drive
requirements of the job. The CONTROL-M CTMRELRS procedure can be used to
change the quantity of resources allocated to a job.
The conversion tool converts CA-7 RESCHNG JCL Batch Terminal Step operations
and # RES override statements to CONTROL-M JCL steps that change quantitative
resources allocated to a job. For more information, see “11. TYPE1 and TYPE2” on
page 104, and “Workload Balancing” on page 31.

RESOURCE quantities for a job, previously determined by the TYPE1 and TYPE2
parameters in the CA-7 job definition, are overridden by the CTMRELRS step.
The same conversion restrictions that apply to the DEMAND and POST commands,
which are described in “28. DEMAND[H] and POST” on page 120, also apply to the
RESCHNG command.
NOTE
Only RESCHNG commands with JOB subparameters that refer to the member in
which the command resides are converted.
34. This item number is not currently in use.
35. OWNER
Identifies the CONTROL-M user ID in the job scheduling table.
The &USEROPT conversion parameter specifies the source from which the OWNER
parameter is to be taken. For more information, see “&USEROPT” on page 160.
The &USERLEN conversion parameter specifies the number of characters to be used

in the OWNER parameter. For more information, see “&USERLEN” on page 159.
36. SCHID
The CA-7 SCHID parameter provides a method of varying scheduling requirements,
job triggers, JCL overrides, and so on, for the same job.
Within CONTROL-M, a job in a Group scheduling table can be assigned different sets
of basic scheduling criteria by means of Schedule Tags. For each CA-7 SCHID
assigned to a job, the conversion tool creates a Schedule Tag in the Group Entity of
the Group Scheduling table. The name of the Schedule Tag is in the format
schedule-ID_head-of-tree-jobname[_n]
where n is an integer and indicates that a supplemental schedule tag had to be created
for the same CA-7 scheduling criteria.

This occurs when the CA-7 scheduling criteria are so complex that a single
CONTROL-M schedule tag is insufficient, for example, where the conversion of CA-7
scheduling criteria requires
■ both CONTROL-M DAYS and DATES parameters
■ both CONTROL-M periodic and non-periodic parameters
■ more than 12 CONTROL-M DATES parameters
Each Schedule Tag is then placed into the appropriate job scheduling definition.
NOTE
Schedule Tags are sometimes generated in CONTROL-M jobs even though there is no
corresponding CA-7 SCHID with defined scheduling criteria. This can happen
■ when a triggered job within a CA-7 job definition has a SCHID that is not defined
■ in group scheduling tables containing DEMANDed jobs
The CA-7 hierarchical triggering structure must be retained during conversion to

CONTROL-M, and such undefined SCHIDs may have an impact on it. To prevent
unwanted effects, the conversion tool creates a Schedule Tag for each undefined
SCHID when constructing the CONTROL-M scheduling tables. However, if not
otherwise referred to, for example, in CA-7 # JI or # JO statements in JCL, these
Schedule Tags with no scheduling criteria can be ignored and may be manually
deleted.
The CONTROL-M %%$TAG AutoEdit system variable contains the name of the
Schedule Tag that causes the job to be scheduled. When the CA-7 JCL of a job
contains CA-7 JCL override statements in the format
# JI, ID=. . .
the conversion tool converts these statements to CONTROL-M AutoEdit statements,

transforming the ID subparameter into the %%SCHID AutoEdit variable as follows:
This extracts the first three characters of the CA-7 SCHID Schedule Tag. For an
example, see “26. # JI, # JO, and # JEND, # XI, # XO, and # XEND Statements” on
page 117.
In the following instances, the %%$TAG variable is not used to derive a value for
%%SCHID in the converted JCL:

■ For DEMANDed jobs, a SET VAR %%SCHID AutoEdit variable is used to create
DEMANDed job definitions. The SET VAR %%SCHID AutoEdit variable value is
set from the SCHID parameter contained on the DEMAND JCL Batch Terminal
statement. If there is no CA-7 SCHID parameter, the %%SCHID value is taken
from the schedule ID of the job that invokes the DEMANDed job.
■ When the CA-7 SCHID of a job is changed from nnn to mmm by means of the
statement SCHID=nnn/mmm in the TRIGGERED JOBS section of the LJOB report,
the CONTROL-M SET VAR AutoEdit variable %%CHG_SCHID is set to the
changed SCHID (mmm). In the JCL conversion of the corresponding JCL members,
ensure the proper resolution of %%SCHID by using the following code:
%%RESOLVE NO
%%IF %%CHG_SCHID GE 0
%%SET %%SCHID = %%CHG_SCHID
NOTE
Non-scheduled, single-purpose jobs are created with Schedule Tag names in the form
000_jobname.
37. JCL Initialization Statement

The ALT parameter of the CA-7 JCL Initialization Statement enables you to define
alternate libraries to be searched prior to searching the primary JCL library specified
in the DSN parameter. ALT is a number from 000 through 253 that specifies the index
value from another initialization file JCL statement.
The conversion tool specifies the CA-7 Alternate JCL library name using the
CONTROL-M OVERLIB job scheduling definition parameter.
A value of DUMMY overrides the alternate JCL library name specified in the
OVERLIB parameter when EXEC is set to N. For more information, see “8. EXEC” on
page 101.
38. SHOUT
Causes specific messages to be sent by CONTROL-M (“shouted”) to predetermined
destinations on predefined occasions.
The conversion tool supports the following situations:

Table 26 Occasions for SHOUT Messages

Item Description
WHEN NOTOK Send a SHOUT message when a job fails.
WHEN LATESUB Send a SHOUT message when a job has not been submitted by
a specified time and the CA-7 PROMPTS parameter of the Job
Definition screen for the particular job is set to Y (Yes).
The conversion tool uses the start time to set the SHOUT
message to indicate that the job is late when the specified time
has passed. For more details, see the STARTM parameter in
the LJOB report.
Note: If the SHOUT WHEN LATESUB time is equal to the
TIME FROM parameter, which is discussed in “15. SBTM” on
page 108, one minute is added to the SHOUT WHEN
LATESUB time to prevent a “late” SHOUT when the job is
submitted.
WHEN LATE * Send a SHOUT message when a job has not finished executing
by its DUE OUT time, which is discussed in “16. DOTM and
LDTM” on page 109.
WHEN EXECTIME The CA-7 CLOCK-TIME, that is, the weighted average elapsed
> nnn runtime of the job, is used to calculate if a SHOUT WHEN
EXECTIME value, in minutes, has been exceeded.
The CLOCK-TIME of the job is added to the quantity specified
in the &SHOUTX conversion parameter and used in the
CONTROL-M SHOUT WHEN EXECTIME > nnn parameter,
which sends the message %%JOBNAME HAS EXCEEDED
RUN TIME LIMIT.
The CA-7 weighted average elapsed runtime can also be

specified using the # RES override statement (value ELAPTM)
in the JCL member. This overrides the value in the
CLOCK-TIME parameter.
Note: If the CA-7 CLOCK-TIME specifies an elapsed time
greater than 999 minutes, nnn is set to 999.
The &SHOUTT conversion parameter specifies the SHOUT message text for failed
jobs. The default is
%%JOBNAME J%%JOBID ENDED NOTOK!
The &SHOUTL conversion parameter specifies the SHOUT message text for jobs
submitted late. The default is
MEMBER %%$MEMNAME IS LATE!

The &SHOUTE conversion parameter specifies the SHOUT message text for jobs that
are still executing after their DUE OUT time. The default is
%%JOBNAME J%%JOBID STILL EXECUTING AFTER DUE OUT!
In these SHOUT messages
■ %%JOBNAME and %%JOBID are the Auto Edit variables in which the name of the
submitted job and the JES job number are placed
■ %%$MEMNAME is the AutoEdit variable in which the JCL member name of the
job to be submitted is placed
When &SHOUTT or &SHOUTL or &SHOUTE are left blank, the corresponding

SHOUT messages are suppressed. Various computer personnel can be specified as
the CONTROL-M SHOUT destination. For more information, see the CONTROL-M
for OS/390 and z/OS User Guide.
The &SHOUTDT and &SHOUTDL conversion parameters specify the destination of

the SHOUT message texts for failed and late jobs respectively. The conversion tool
accesses the user ID from the &USEROPT conversion parameter, which is discussed
in “&USEROPT” on page 160.
39. CMEM Rule Table

For details on how the conversion tool converts CA-7 data set triggering, see
“CONTROL-M Event Manager” on page 36.
40. MAINID
The CA-7 MAINID parameter specifies on which CPU a job may or may not be
scheduled.
To display a list of all the CA-7 MAINID specifications that are assigned to the CA-7
SUBMIT data sets or internal reader, use the following CA-7 command:
/DISPLAY,CPU=ALL
The user must supply a CPUID translation table (the DACPUID DD statement) that
associates a system ID with each MAINID. For more information, see “JOB3 - Create
CONTROL-M Scheduling Tables and CMEM Rules” on page 50.

The conversion tool converts MAINID in the format SYn or /SYn by using the
system ID associated with n (from the CPU Translation table) to create a %%SYSID
AutoEdit variable in the CONTROL-M SET VAR parameter in the job scheduling
definition.
The JCL of jobs that require system affinity is then modified by Exit 2 (the Job
Submission exit) by inserting one of the following JES statements before the first step:
/*JOBPARM SYSAFF=%%SYSID (for JES2)
//*MAIN SYSTEM=%%SYSID (for JES3)
The %%SYSID AutoEdit variable is resolved from the value supplied by the SET VAR
parameter.
MAINID specifications of the form /SYn, meaning do not schedule on system n, are
only supported for JES3 systems. The %%SYSID AutoEdit variable then takes the
form /system-id.
For additional information, see “Network Communications Facility” on page 35, and
“Step 11 - Modify and Run the JOB7 Member” on page 83.
41. INITR
The total number of initiators available to CA-7 is indicated in the TOTAV parameter
of the CA-7 INITR Workload Balancing macro.
In CONTROL-M, the Initiator resource must be added to the CONTROL-M

Resources file with a quantity corresponding to the CA-7 TOTAV parameter.
The name of the CONTROL-M Initiator resource is specified in the &INIT conversion
parameter, which is described in “&INIT” on page 152.
42. JES ROUTE PRINT

When the &JESRPRT conversion parameter is set to Y, as discussed in “&JESRPRT”
on page 152, the conversion tool searches the JCL member of each job for JES ROUTE
PRINT new-dest statements and converts them to CONTROL-M SYSOUT
post-processing parameters in the format:
SYSOUT OP N new-dest
where

■ N specifies that the held output destination of the job is to be changed to new-dest
■ new-dest is the first eight characters of the destination parameter specified on the
JES ROUTE PRINT statement
The JES ROUTE PRINT statement is deleted from the JCL run stream.
44. DEP-JOB=?
The CA-7 DEP-JOB job connection parameter can be used to specify a job name
preceded by ? (question mark). This type of job name indicates a conditional job
dependency. Conditional job dependencies work as follows.
If Job A is conditionally dependent on Job B, the execution of Job A depends on Job B

only if Job B is in the Request, Ready or Active queue when Job A enters the Request
queue.
The CONTROL-M Maybe Jobs feature can be used to simulate this “conditional
handling” of predecessor prerequisites. For more information, see the discussion of
Maybe Jobs in the CONTROL-M for OS/390 and z/OS User Guide.
The conversion tool facilitates use of the Maybe Jobs feature by creating IN conditions
in the following format:
?jobname-OK ODAT
This format enables the ADDMNCND KSL utility script to use the special character
“?” (hexadecimal 6F) to recognize conditions of this type. For more information on
the ADDMNCND utility script, see the Keystroke Language chapter of the
For more information on job connection dependencies and alternate condition

naming standards, see “19. DEP-JOB” on page 112.
45. DONT SCHEDULE BEFORE/AFTER

CA-7 DONT SCHEDULE BEFORE and DONT SCHEDULE AFTER parameters are
used to set dates and times before and after which a job must not be scheduled.

The conversion tool converts DONT SCHEDULE BEFORE and DONT SCHEDULE
AFTER parameters to CONTROL-M DEFINITION ACTIVE FROM and DEFINITION
ACTIVE UNTIL values in the relevant job scheduling definitions.
Dates are converted into the Gregorian format using a 2-digit year. The precise date
format that is applied depends on the value specified for the IOA DATETYP
installation parameter.
Upon conversion, the values in CA-7 DONT SCHEDULE BEFORE and DONT
SCHEDULE AFTER parameters are inserted into the DEFINITION ACTIVE FROM or
DEFINITION ACTIVE UNTIL parameters respectively of both the job being
converted and any of its dependent jobs which do not already have any values
specified in those parameters.
46. #HLD
The CA-7 JCL # HLD override statement specifies that the job must be held.
The conversion tool converts the # HLD override statement to the following JCL
IOATEST utility step:
// EXEC IOATEST,PARM=’WTOR=JOB %%JOBNAME IS HELD’
This step causes the job to wait for an operator reply until the HOLD can be removed.
47. #NOX
The CA-7 # NOX override statement in the JCL member indicates that the job must
not be executed.
The conversion tool converts the # NOX override statement to the following JCL and
AutoEdit statements:
//#NOX EXEC PGM=IEFBR14

//* %%GOTO END999
and at the end of the member adds the following AutoEdit statement:
//* %%LABEL END999
This has the effect of turning the job into a dummy job.

48. #MSG
The CA-7 # MSG override statement in the JCL member is used to send messages to
the CA-7 Master Station at job submission time.
The conversion tool converts the # MSG override statement to the following JCL
IOANOTE utility step:
// EXEC IOANOTE,PARM=‘message-text’
The first 48 bytes of the message text are placed into the PARM parameter.
49. #VER
The JCL CA-7 # VER override statement specifies that the job requires manual
verification.
The conversion tool converts the # VER override statement to the following JCL
IOATEST utility step:
// EXEC IOATEST,
// PARM=’WTOR=JOB %%JOBNAME REQUIRES MANUAL VERIFICATION’
This causes the job to wait for any operator reply after the manual verification has
been satisfied.
51. DPROC
The CA-DRIVER procedure definition statement DPROC is used to start a procedure
that consists of all the statements following the DPROC statement. A default value
can be optionally defined for each variable.
The conversion tool creates one member for every CA-DRIVER procedure and places
these members in a special CONTROL-M library called PROCLIB.

The CONTROL-M %%SET AutoEdit control statement is used to set values for
user-defined variables. The conversion tool converts each default value that is
assigned to a variable in the DPROC statement into an appropriate CONTROL-M
%%SET AutoEdit control statement.
■ All variable values are treated as character (non-numeric) data.
■ In CA-DRIVER, a variable parameter can be assigned multiple values or array

elements. The conversion tool converts each array element to a CONTROL-M
AutoEdit variable name, consisting of the CA-DRIVER array name with the
element number appended to it.
■ In CA-DRIVER, default values can be specified in the EXEC statement, for the
variables of the procedure. If values are specified in both the DPROC statement
and the EXEC statement, the values on the EXEC statement override the DPROC
default values.
In CONTROL-M, the current %%SET AutoEdit control statement overrides the

previous value of the variable. The conversion tool creates a member in a special
library called PARMLIB. The member contains a CONTROL-M %%SET AutoEdit
statement for each default value assigned to a variable in the EXEC statement. The
name assigned to this member is the job name with a suffix of an ascending number
appended to it. If no default values are specified in the EXEC statement, an empty
member is created in the PARMLIB library.
In order to create a unique member name for every EXEC statement with default
values, the conversion tool uses three CONTROL-M AutoEdit variables:
■ %%MEM# , which is a counter

■ %%JOBNAMX, which is the job name
■ %%MEMNAME, which is a member name consisting of the %%JOBNAMX
AutoEdit variable with the %%MEM# AutoEdit variable appended to it.
The conversion tool establishes the connection between the default values member
and the converted procedure by adding the CONTROL-M %%INCLIB and
%%INCMEM AutoEdit control statements after all the CONTROL-M %%SET
AutoEdit control statements that were created from the CA-DRIVER DPROC
command.
■ The %%INCLIB and %%INCMEM control statements copy the PARMLIB default
values member created from the EXEC statement.
■ The %%INCLIB statement specifies the name of the PARMLIB library.
■ The %%INCMEM statement specifies the %%MEMNAME AutoEdit variable.

52. (D)STEP
The CA-DRIVER procedure (D)STEP command is used to assign a name to a control
statement. Naming a control statement enables branching to the statement from (D)IF
or (D)GOTO commands.
The CONTROL-M %%GOTO and %%LABEL AutoEdit control statements provide

the AutoEdit facility with “GO TO” logic, enabling simple inclusion or exclusion of
job steps, DD statements, input statements, and so on.
The conversion tool converts the CA-DRIVER (D)STEP command to a CONTROL-M

%%LABEL AutoEdit control statement.
53. (D)GOTO
The CA-DRIVER procedure (D)GOTO command is used to stop procedure
expansion, branch forward and backward to another control statement, and continue
expansion from that point.
The CONTROL-M %%GOTO AutoEdit control statement provides the AutoEdit

facility with GO TO logic, enabling simple inclusion or exclusion of job steps,
DD statements, input statements, and so on.
The conversion tool converts the CA-DRIVER (D)GOTO command to a

CONTROL-M %%GOTO AutoEdit control statement.
54. (D)SET
The CA-DRIVER procedure (D)SET commands are used to change the value of a
variable during conditional expansion.
The CONTROL-M %%SET AutoEdit control statement is used to set values to

user-defined variables.
The conversion tool converts the CA-DRIVER (D)SET command to a CONTROL-M

%%SET AutoEdit control statement.
■ Arithmetic operators + and – are converted to CONTROL-M %%PLUS and

%%MINUS operators respectively.
■ Blank characters included in a string are converted to a CONTROL-M

%%BLANKn AutoEdit control statement.

CA-DRIVER predefined functions in (D)SET statements are not supported.
55. (D)IF
The CA-DRIVER (D)IF procedure command is used for conditional forward and
backward branching.
The CONTROL-M %%IF, %%ELSE, and %%ENDIF AutoEdit control statements

provide the AutoEdit facility with a powerful Boolean IF logic capability. These
statements, as well as the %%GOTO and %%LABEL control statements, facilitate
branching based on different runtime criteria.
The conversion tool converts the CA-DRIVER (D)IF command to CONTROL-M

%%IF and %%ENDIF AutoEdit control statements.
56. DATA, DEND

The CA-DRIVER DATA and DEND procedure commands are used to read one or
more records from the JCL job stream. CA-DRIVER replaces the DATA statement
with the statements that follow the EXEC statement in the input job stream, until a
DEND statement is reached.
The conversion tool creates a member in a special library called DATALIB. The
member contains the statements between the EXEC and DEND statements. The name
assigned to this member is the job name, with a suffix of an ascending number
appended to it.
The conversion tool establishes the connection between the statements in the member
and the converted procedure by converting the CA-DRIVER DATA statement to the
CONTROL-M %%INCLIB and %%INCMEM AutoEdit control statements. These
control statements copy the statements in the member. The %%INCLIB statement
specifies the name of the DATALIB library. The %%INCMEM statement specifies the
%%MEMNAME AutoEdit variable.
57. (D)NEST
The CA-DRIVER (D)NEST procedure commands are used to call another
CA-DRIVER procedure, which can, in turn, call another procedure.
The CONTROL-M %%INCLIB and %%INCMEM AutoEdit control statements define

a library and a member that are to be included in the job stream.

The conversion tool converts the CA-DRIVER (D)NEST statement to CONTROL-M

%%INCLIB and %%INCMEM AutoEdit control statements that copy the called
procedure into the job stream.
58. (D)ABORT/DFLUSH
The CA-DRIVER (D)ABORT/DFLUSH procedure commands are used to completely
terminate the procedure expansion.
The conversion tool converts CA-DRIVER (D)ABORT/DFLUSH commands to

invalid CONTROL-M AutoEdit control statements. As a result, the job is not
submitted by CONTROL-M, and a warning message is issued. The format of the
invalid control statement is:
//* %%ABORTED - DELIBERATE SYNTAX ERROR !
59. Variable Parameters

CA-DRIVER variable parameters are converted to CONTROL-M %% AutoEdit
variables. When a CA-DRIVER variable contains a substring reference, it is converted
to a %%SUBSTR AutoEdit function.
Array type CA-DRIVER variables are also supported.
The CA-DRIVER Reserved-Name Variable parameters shown in Table 27 are

supported:
Table 27 Supported CA-DRIVER Reserved-Name Variables

CA-DRIVER Parameter CONTROL-M AutoEdit Variable Notes
&C_DATE or &DATE %%OUTDATE a
&C_JDATE or &JDATE %%YEAR.%%JULDAY b
&C_TIME or &TIME %%TIME b
&C_DAY or &DAY %%OUTDAY%%WDAY b
&C_MONTH or &MONTH %%OUTMON%%MONTH b
&C_L2SID %%SUBSTR %%$TAG 1 3 b
&C_L2JN %%JOBNAME b
&C_L27# %%JOBID b
&C_L2xxx %%C_Lxxx c

The variable date definitions shown in Table 28 depend on the site date format
standard.
Table 28 Site Date Format Standards

Format AutoEdit Variable Definition
yymmdd %%YEAR%%./%%MONTH%%./%%DAY
ddmmyy %%DAY%%./%%MONTH%%./%%YEAR
mmddyy %%MONTH%%./%%DAY%%./%%YEAR
NOTE
These variables are defined in the DAYMONTH AutoEdit Global Definition member.
You must edit this member to choose the proper format. For more information, see
item 6 under “Step 14 - Final Adjustments” on page 3-87.
For more information regarding the support of the remaining &C_L2xxx

CA-DRIVER parameters, see “&L2VARS” on page 153.
60. Date Functions

CA-DRIVER Date functions are converted to CONTROL-M %% AutoEdit functions.
In most cases, a block of AutoEdit variables is necessary to fully convert the

CA-DRIVER date function. The table below lists only the main operative AutoEdit
function involved without listing any secondary AutoEdit functions needed. The
DAYMONTH member, discussed in the preceding item, is also necessary for many of
the functions listed below.
The CA-DRIVER Date functions shown in Table 29 are supported:
Table 29 Supported CA-DRIVER Date Functions (Part 1 of 2)

CA-DRIVER Date
Function Principal CONTROL-M AutoEdit Function
DMY %%$GREG
MDY %%$GREG
YMD %%$GREG
DMYR %%$GREG
MDYR %%$GREG
YRMD %%$GREG
DM3Y %%$GREG

Table 29 Supported CA-DRIVER Date Functions (Part 2 of 2)

CA-DRIVER Date
Function Principal CONTROL-M AutoEdit Function
M3DY %%$GREG
YM3D %%$GREG
DM3YR %%$GREG
M3DYR %%$GREG
YRM3D %%$GREG
DAY %%$WEEKDAY
MONTH %%$GREG
MON %%$GREG
MON# %%$GREG
DOW %%$WEEKDAY
DOW# %%$WEEKDAY
WOY %%$YEARWK#
DTADD %%$GREG, %%$CALCDTE
DTSUB %%$GREG, %%$CALCDTE
JDOM %%$GREG,%%$WCALC,%%$JULIAN
JWDM %%$GREG,%%$WCALC,%%$JULIAN
JADM %%$GREG,%%$WCALC,%%$JULIAN
JRWD %%$GREG,%%$WCALC,%%$JULIAN
JRAD %%$GREG,%%$WCALC,%%$JULIAN
61. Attribute Functions (L’, T’)

CA-DRIVER Attribute functions are converted to CONTROL-M %% AutoEdit
functions when referenced in CA-DRIVER DIF or DSET commands.
The CA-DRIVER Attribute functions that are supported are listed in Table 30:
Table 30 Supported CA-DRIVER Attribute Functions

CA-DRIVER Attribute Function CONTROL-M AutoEdit Function
L’ var_name %%$LENGTH %%var_name
T’ var_name %%$TYPE %%var_name

Unique CONTROL-M Parameters

Several unique CONTROL-M job scheduling definition parameters that do not have
corresponding CA-7 features can be set by the conversion tool during the creation of
the CONTROL-M scheduling tables.
The DEFAULTS parameter member in the conversion SOURCE library contains these
unique parameter settings, and must be reviewed and modified to specify your local
CONTROL-M preferences. For more information about these parameters, see
Appendix A, “Conversion Parameters” and the CONTROL-M for OS/390 and z/OS
User Guide.
CATEGORY
This CONTROL-M parameter specifies the CONTROL-D report decollating mission
category that must be scheduled under CONTROL-D when the job is scheduled
under CONTROL-M. This option is only available if CONTROL-D is installed at your
site. For more information, see the description of the D-CAT parameter in the
If you use the &DCTGRY conversion parameter, which is described in “&DCTGRY”

on page 147, the conversion tool specifies the CATEGORY parameter in the job
scheduling definition of relevant jobs. This specifies the unique character string in the
CA-7 JCL that precedes, and so identifies the existence of, the Mission Category.
When the conversion tool finds this character string in the JCL, the characters
following the string (up to 20) are entered in a CATEGORY basic scheduling
parameter.
For example, if the character string is //*CTDMC=, the following statements in the
CA-7 JCL
//*CTDMC=XYZ
//*CTDMC=DAILY
respectively specify mission categories ‘XYZ’ and ‘DAILY’.
The conversion tool can optionally define an OUT condition, to be used in

CONTROL-D processing, in the job scheduling definition of any job for which a
CATEGORY scheduling parameter is specified. For more information, see
“&CTDCOND” on page 144.
The format of the condition is
jobname-usertext ODAT+

The variable jobname is the CONTROL-M MEMNAME of the job, and the variable
usertext is specified in the &CTDCOND conversion parameter.
For example, if the value specified in &CTDCOND is '-ENDED-OK' and the job
scheduling definition of the ABC job has a CATEGORY parameter, then the OUT
condition
ABC-ENDED-OK ODAT+
is placed in the job scheduling definition of the ABC job.
DO SYSOUT
This CONTROL-M parameter specifies how the job output is to be handled.
At job completion, CONTROL-M analyzes the job output. To enable CONTROL-M to

locate the job output on the system spool, CONTROL-M modifies the MSGCLASS
JCL parameter of the job at time of submission to the automatically held output class
defined during installation, the CONTROL-M HLDCLAS parameter. After analyzing
the sysout, CONTROL-M can be ordered to requeue the sysout. For more information
on DO SYSOUT options, see the CONTROL-M for OS/390 and z/OS User Guide.
The conversion tool can be instructed to specify various actions using the
CONTROL-M DO SYSOUT facility.
The &TOCLASS conversion parameter specifies the output class to which

CONTROL-M requeues the job output. For more information on this parameter, see
“&TOCLASS” on page 159.
The &RELEASE conversion parameter controls whether CONTROL-M releases the

job output for printing on the system spool. The default is Y (Yes). For more
information on this parameter, see “&RELEASE” on page 155
The &FROMC conversion parameter specifies which of the held sysout classes must
be requeued. For more information on this parameter, see “&FROMC” on page 151.
MAXWAIT
This CONTROL-M parameter specifies the number of extra days a job must wait to be
executed in the Active Jobs file until it is disregarded. This 2-digit parameter accepts
values in the range from 00 through 98, or 99, and is specified in the &MAXWAIT
conversion parameter, which is described in “&MAXWAIT” on page 154. The default
value is 03.

However, this does not apply when CA-7 SYMETRIC schedules are being converted.
For more information, see “17. Scheduling Information” on page 109.

Appendix
A Conversion Parameters
CONTROL-M conversion parameters are defined in the DEFAULTS member in the
conversion source library. These conversion options must be modified to fit your
local site requirements, and are described in Table 31 in alphabetical order.
Table 31 Conversion Parameters (Part 1 of 18)

&ALLMSG Specifies whether all messages in the JCL conversion (JOB4)
are to be printed. Valid values are:
■ Y (Yes) – All CA-7 batch terminal commands that are not

supported or are not relevant in a CONTROL-M
environment, such as /LOGON, are printed.
■ N (No) – An error message is issued only when the

conversion encounters problems with the CA-7 Batch
Terminal commands that it attempts to convert, such as
DEMAND, POST, RESCHNG. Default.
&CALPREF Calendar prefix for CONTROL-M calendar names. Must be 6
characters in length. Names in certain forms must not be used,
and these are discussed in “JOB3 - Create CONTROL-M
Scheduling Tables and CMEM Rules” on page 50. Default:
CTMCAL
&CLASBAR Specifies whether CA-7 CLASS Barrier support is to be
implemented. For more information, see “12. CLASS, # RES
and DEMAND[H]” on page 104. Valid values are:
■ Y (Yes) – CA-7 CLASS Barrier support is implemented. The

conversion tool creates CLASS Barrier resources in the
CONTROL-M job scheduling definition.
■ N (No) – CA-7 CLASS Barrier support is not implemented.

Default

&CTDCOND Only applicable at sites where CONTROL-D is installed.
The user-text parts of the OUT conditions are added to job

scheduling definitions when the DCAT basic scheduling
parameter is specified in a job scheduling definition.
Default: Blank, which indicates that no OUT conditions are to

be added to the job scheduling definitions.
For more information, see “CATEGORY” on page 140.

&CTR CONTROL-M/Restart parameter. Valid values are:
■ Y (Yes) – CONTROL-M/Restart is implemented with

CONTROL-M. Default.
■ N (No) – CONTROL-M/Restart is not implemented.

Instructs the conversion tool not to set any
CONTROL-M/Restart statements.
■ X – Same as Y, except that $EXERR is used instead of

$ABEND in the DO IFRERUN statement. For information
about the difference between $ABEND and $EXERR, see
the discussion of the DO IFRERUN post-processing
parameter in the CONTROL-M for OS/390 and z/OS User
Guide.
When Y or X is specified and one of the following occurs
■ the CA-7 job definition indicates INSERT-RMS is set to Y
■ INSERT-RMS is set to YES in the CA-11 JCL comment

statement (//*CA-11)
■ the CA-11 U11RMS step (specifying processing options P,

R, or F) is present in the JCL of the job
a DO IFRERUN statement is inserted in the job scheduling

definition. For more information, see “30. INSERT-RMS and
//*CA-11 Comment Statements” on page 122, and “31. CA-11
U11RMS Step” on page 123.

&CTR In addition, when &CTR is set to Y or X, the following
CONTROL-M/Restart job scheduling parameters are also set:
(continued)
■ AUTO-ARCHIVE is set to Y, to indicate that the three
SYSDATA files of a job are archived for
CONTROL-M/Restart use and for Online Viewing.
Archive parameters, such as retention period or archive
data set types, are determined by CONTROL-M/Restart
installation parameters.
■ SYSDB is set to Y, to indicate that the three SYSDATA files

are to be archived to a common data set (as opposed to a
unique data set).
■ PREVENT-NCT2 is set. The CA-11 U11RMS Run Handler

program, in production processing mode (with PARM set
to 'P') ensures that all output (DISP=NEW) simple data sets
in the job stream are uncataloged and scratched for the
current production run. The CONTROL-M/Restart
PREVENT-NCT2 parameter performs this function.
PREVENT-NCT2 is set by the &PRVNCT2 conversion

parameter, which is described later in this table. When set
to Y, this job scheduling definition specification
automatically prevents NOT CATLGD 2 situations from
occurring in non-restarted jobs, by causing the deletion of
problematic data sets prior to job execution.
Note: The CONTROL-M/Restart PREVENT-NCT2 processing
encompasses data sets with any DISP setting (not just
DISP=NEW). Therefore, CONTROL-M/Restart EXCLUDE
DSN statements may be necessary for some data sets, such as
data sets specifying DISP=(OLD,CATLG), for proper CA-11
emulation.

&CTR In CA-11, the user option module is generated by the
U11OPTBL macro, which codes the default return code value
(continued) issued by CA-11 during rerun (R) processing. If this value is
not 0, you must specify the ADDPROC, PROCRC, and
NCT2RC parameters in the CTRPARM member of the IOA
PARM library. These parameters simulate the action of CA-11
in passing the desired return code to subsequent job steps, and
are described in the INCONTROL for OS/390 and z/OS
Installation Guide. Specify these parameters as follows:
■ Set the ADDPROC parameter to the step name specified in

the STEPRMS parameter of the RESTART statement in the
CA-7 Initialization file, or the default value of CA07RMS.
■ Take PROCRC from the U11OPTBL CA-11 macro.
■ If you want the CONTROL-M/Restart step to simulate a

non-zero return code during the the original run of the job
for NCT2 processing, specify NCT2RC.
If you use the CA-11 U11VOLCX macro (Volume

INCLUDE/EXCLUDE list) or the U11UCSEX exit
(Uncatalog/Scratch exit), you must either specify
corresponding CONTROL-M/Restart EXCLUDE DSN
statements, or Exit 1 (CTRX001) to perform the equivalent
function.
&CTRCONF CONTROL-M/Restart confirmation parameter. If the &CTR
conversion parameter is set to Y, this parameter specifies
whether manual confirmation is required before the job is
scheduled for restart using the DO IFRERUN statement. Valid
values are:
■ Y (Yes) – Manual confirmation is required. Default.

■ N (No) – Manual confirmation is not required.

&DCTGRY Only applicable at sites where CONTROL-D is installed.
A character string to be searched for, starting in column 1, in

the JCL of the job that precedes the CONTROL-D Report
Decollating Mission Category specification and identifies its
position.
Default: Blank, which indicates that no D-CAT basic

scheduling parameters are to be specified in the job scheduling
definitions being set up by the conversion tool.
For more information, see “CATEGORY” on page 140.

&DELCOND Specifies whether any, and if so what type of, conditions must
be deleted from the IOA Conditions file when the job ends
successfully, regardless of the LEADTM. Valid values are:
■ A (All) – delete all IN conditions, including job-triggering

and manual conditions
The job-triggering conditions are deleted as OUT
conditions in the group entity definition.
■ Y (Yes) – delete job connection conditions only
■ N (No) – do not delete conditions

Default.
When many jobs run more than once each day, this parameter
is useful for cleaning “used” conditions from the IOA
Conditions file, so that a condition that triggered a successful
job run does not trigger subsequent job runs.
Warning! Do not set &DELCOND to A or Y if different jobs
wait for the same IN conditions, or these jobs will be
prevented from executing.

&DEMAND The conversion tool converts CA-7 DEMAND[H] commands
differently, depending on the value of the &DEMAND
conversion parameter. Valid values are:
■ CTM. Default.
■ CA7
When &DEMAND is set to CTM (CONTROL-M mode), the

conversion tool converts DEMAND[H] commands by
incorporating the demanded job into a CONTROL-M
scheduling table and specifying a demanded job IN condition
in its job scheduling definition. The DEMAND[H] command
step in the demanding job is converted to a CONTROL-M
IOACND step with an ADD COND command to add the IN
condition.
This method provides increased control over your application

jobs, since the demanded jobs become part of the application
job tree by means of scheduling criteria as well as job
connections. Nested demanded jobs are also incorporated into
the application job tree structure. This enables all relevant
CONTROL-M facilities to treat these jobs as one application.
For example, the CONTROL-M Simulation and Forecasting
facility handles all scheduled jobs, including demanded jobs,
that would otherwise have been ignored, as they are in the
CA-7 forecasting utility.
When &DEMAND is set to CA7 (CA-7 mode), the conversion

tool converts DEMAND[H] commands by creating a new
(non-group) scheduling library in which the job scheduling
members consist of the demanded jobs as head-of-tree jobs.
The remainder of the jobs in each scheduling member are the
jobs that are triggered from the demanded head-of-tree job.
The DEMAND[H] command step in the demanding job is
converted to a CTMUTIL step (which invokes the
CONTROL-M CTMJOB utility) with an ORDER command to
FORCE the job and all its successor jobs into the daily
schedule. For more information on the CTMUTIL utility, see
Appendix D, “The CTMUTIL Conversion Utility.”

&DEMAND This method more closely resembles the way demanded jobs
are processed by CA-7. The jobs are not incorporated into the
(continued) application job tree, as in the CONTROL-M mode. The
advantage to this method is that demanded jobs are ordered
into the Active Jobs file only when they are actually to be
executed. Demanded branches that are only executed in
specific circumstances, such as demanded branches dependent
on a specific prior step condition code, are not ordered into the
Active Jobs file when not needed. This reduces clutter in the
Active Jobs file and possible confusion as to which jobs must
run.
Note: The only demanded jobs that are incorporated into
CONTROL-M scheduling definitions by the conversion tool
are the jobs with JCL members that are referenced by jobs
defined in the CA-7 LJOB report using a DEMAND[H]
statement in the JCL member. These demanded jobs are then
subject to being divided during JOB7, which is discussed in
“JOB7 Create CONTROL-M Group Scheduling Tables” on
page 64. If a job which issues a DEMAND is not defined in the
LJOB report, the job which it demands is not processed by
JOB7 as a demanded job, but as an unscheduled job.

&DEPJCND Specifies the format of the CA-7 job and DSN connection
dependency IN and OUT condition names. Valid values are:
■ N (No) – The condition names are formatted as specified in

“19. DEP-JOB” on page 112 and “21. DSN” on page 113.
Default.
■ J (Job) – The condition names for job connection

dependencies are formatted as follows:
jobname_dep-jobname_OK ODAT
The variable jobname is the CONTROL-M MEMNAME of
the predecessor job, on which dep-jobname is dependent;
this is also referred to as the predecessor job name.
The variable dep-jobname is the CONTROL-M MEMNAME
of the successor job, which is dependent on jobname; this is
also referred to as the successor job name.
■ D (DSN) – The condition names for DSN connection

dependencies are formatted as follows:
creating-jobname_dep-jobname_DS ODAT
The variable creating-job is the CONTROL-M MEMNAME
of the job that creates the data set that defines the DSN
connection dependency.
The variable dep-jobname is the CONTROL-M MEMNAME
of the dependent job.
■ Y (Yes) – The condition names for job dependencies are

formatted as if J was specified, and the condition names for
DSN connection dependencies are formatted as if D was
specified
Notes:
■ When J, D, or Y are specified for &DEPJCND, a separate

OUT condition is created for each job for which a job or
DSN connection exists. This may lead to a much larger
number of OUT conditions being created. If you specify
&DEPJCND=N, only one job connection OUT condition is
created for each job.

■ Specifying J, D, or Y for &DEPJCND provides a
considerable degree of close control for manipulating OUT
conditions. For example, if Job A has three dependent jobs
(B, C, and D), three IN/OUT conditions are created,
B_A_OK, C_A_OK, and D_A_OK, each in the respective
job scheduling definition. If Job A abends, you can
selectively trigger Job B without affecting Jobs C and D by
adding the condition B_A_OK to the IOA Conditions file.
■ If the value of the CA-7 job connection LEADTM

parameter (the satisfaction lead time in hours) is 00, the
conversion tool automatically creates OUT conditions that
delete condition names which have an ODAT of ****. For
more information, see Item 19 in “19. DEP-JOB” on
page 112. If you often use this feature, specifying J, D, or Y
for &DEPJCND will give you close control over the
deletion of job and DSN connections.
■ When you set &DEPJCND to J or Y, conditional job

connections create IN and OUT conditions in the following
format:
?jobname_dep-jobname_OK
&DIRMAX Maximum number of members in a CA-7 JCL library.
The value you set for &DIRMAX must be as small as possible

without going below the actual maximum.
Default: 10000
&FROMC Which of the held sysout classes must be requeued. Specify ‘ ’
(blank) if all held sysouts must be requeued.
Default: ‘ ’ (Blank)
When TOCLASS is ‘ ’ this parameter is ignored.

&HISTORY History Active Jobs file feature. Valid values are:
■ Dnnn – The retention period (nnn), measured in days.

■ Gnn – The retention period (nn), measured in generations.
■ “ “ (Blank) – Do not use the History Active Jobs file
feature. Default.
&INCLIB The CONTROL-M Include library for CA-DRIVER variables.
Default: CTM.DRIVER.INCLIB

&INIT CONTROL-M Quantitative resource name for controlling
initiators that is added, with a quantity of 1, to the job
scheduling definition of each executable job.
To suppress creation of an initiator resource, set &INIT to ' '

(Blank).
Default: INITIATOR
&JESRPRT Specifies whether JES ROUTE PRINT JCL statements are to be
converted to CONTROL-M SYSOUT post-processing
parameters. Valid values are:
■ Y (Yes) – JES ROUTE PRINT JCL statements are converted.

For more information, see “42. JES ROUTE PRINT” on
page 130. Default.
■ N (No) – JES ROUTE PRINT JCL statements are not

converted.
&JOBCLAS CA-7 JCL Job Class conversion. This parameter specifies
whether JCL job classes are converted to CONTROL-M
Quantitative resources. For more information, see “27. JCL Job
Class” on page 120.
Valid values are:
■ ' ' (Blank) – suppress the creation of Quantitative

resources. Default.
■ in cases where the JCL job statement contains no CLASS

parameter, the default job class to be used to create the
resource name.
&JOBMXOC Maximum number of occurrences of a job within a scheduling
table.
This parameter enables the control of application creation by

the conversion tool when CA-7 DEMANDs are encountered in
the JCL, or for recursively-defined jobs.
Valid values are from 1 through 35. Default: 5

&LINMAX Maximum number of lines in a JCL member. Default: 5000.
Ensure that this number is large enough to accommodate the

growth of JCL members due to the insertion of CONTROL-M
AutoEdit statements by the conversion tool.

&L2VARS For users who are running CA-7 release 3.1 or later, and have
implemented CA-DRIVER only.
CA-DRIVER provides various reserved-name variable

parameters specifically for CA-7. These variables can be
referenced in CA-DRIVER procedures, and values are
automatically assigned when the variable is referenced during
procedure expansion. Many of these variables can be
automatically converted by the conversion tool, as follows.
The CA-DRIVER variable is converted to a CONTROL-M

AutoEdit variable, and a CONTROL-M SET VAR statement
for the newly created AutoEdit variable is placed into the job
scheduling definition of the invoking job to provide an initial
value. The initial value is derived from the corresponding
CA-7 job definition. The conversion supports the CA-DRIVER
variables listed in Table 32, “CA-DRIVER Variables,” on
page A-161.
For the definition of CA-DRIVER system variable and other

CA-7 specific variables, such as &C_MONTH, &C_DAY,
&C_DATE, &C_JDATE, &C_TIME, &C_L2SID, &C_L27# , and
&C_L2JN, see the DAYMONTH member in the conversion
source library.
Since not all users utilize all the above variables in their
CA-DRIVER procedures, this conversion parameter enables
you to choose whether to create the corresponding SET VAR
parameters in the job scheduling definitions, thereby
preventing clutter in the job scheduling definitions. The choice
is indicated by coding a positional Y (Yes) or N (No) value in
the &L2VARS parameter.
The position of the Y or N corresponds to the position of the

relevant variable in the list in Table 32, “CA-DRIVER
Variables,” on page A-161. For example,
&L2VARS=NNYYNNNNYN indicates that the only variables
that will be automatically processed by the conversion tool are
&C_L2RO, &C_L2CC, &C_L2DOT.
Default: &L2VARS=NNNNNNNNNN

&MAXGENT The maximum number of lines in a group scheduling entity.
Default: 5000.
In general, the default value of this parameter should not be

changed unless the CTMCA7V5-12S error message is
displayed. In that event, the value of &MAXGENT should be
increased to approximately 5% of the value in the PARM
parameter on the EXEC statement in STEP2 of JOB7.
&MAXCALS Maximum number of calendars contained in the AUXCAL file.
Default: 5000
&MAXDSN Maximum number of data set triggers that create CMEM
events. Default: 1000
&MAXWAIT Number of extra days a job must wait in the Active Jobs file to
be executed, after which the job is deleted.
Format: 2 digits. Leading zeroes are required. Default: 03

&PNIBTSD Process Non-Instream Batch Terminal SYSIN Data indicator.
Whether to convert CA-7 Batch Terminal commands, such as
DEMAND, POST, and RESCHNG, that are not contained
instream in the SYSIN DD statement of a CA-7 Batch Terminal
Step (that is, are pointed to by a sequential file or a member of
a PDS). Valid values are:
■ Y (Yes) – Convert the commands.

■ N (No) – Do not convert the commands. Default.
For sites where references to Batch Terminal commands are

made from within JCL procedures, that is, the SYSIN
DD statement does not appear in the JCL member being
converted, you can run the JCL conversion (JOB4) against the
affected procedure library.
Note: If &PNIBTSD is set to Y, in addition to the JCL libraries
defined in the CA-7 Initdeck, you should copy all PDSs and
sequential data sets containing CA-7 Batch Terminal
command members, to preserve the original PDSs and
sequential data sets. For more information, see “Step 2 - Copy
CA-7 and CA-11 JCL and CA-DRIVER Libraries and Initdeck”
on page 73.
In case of fallback to CA-7, simply delete the original PDSs and

sequential data sets and rename the copies to the original
production names.

&PRVNCT2 Automatic setting of the PREVENT-NCT2 parameter. Valid
values are:
■ Y (Yes) – Sets PREVENT-NCT2 to Y on all jobs.

■ N (No) – Sets PREVENT-NCT2 to N on all jobs.
■ CA7 – Sets PREVENT-NCT2 to either Y or N, based on the
INSERT-RMS definition of CA-7, and whether the JCL of
the job contains the CA-11 U11RMS step, specifying
processing options F, P, R, or N.
If the JCL contains the CA-11 U11RMS step, or the CA-11
JCL comment statement is coded with a PARM parameter,
PREVENT-NCT2 is set to Y, regardless of how the CA-7
INSERT-RMS parameter is set, except when the PARM
parameter is coded as ‘N’ (null processing), or
‘P,PSEUDO=YES’ (pseudo production processing).
If the JCL does not contain the CA-11 U11RMS step, and
the INSERT-RMS parameter is set to Y, or the CA-11 JCL
comment statement is coded as INSERTRMS=YES,
PREVENT-NCT2 is set to Y, except when the PARMRMS
parameter of the RESTART statement in the CA-7
Initialization file is set to PSEUDO.
Default.
This parameter is ignored when &CTR is set to N.
For more information, see PREVENT-NCT2 under the &CTR

conversion parameter in this table.
&REL The release of CA-7 from which you are converting, in the
format x.y (for example, 3.1). Default: 3.0
&RELEASE Sysout release specifies whether the job sysouts are released
for printing after they are analyzed by CONTROL-M, or are
deleted. Valid values are:
■ R – Release sysouts for print. Default.

■ D – Delete the sysouts. This parameter may be useful at
sites that have sysout archival products.
■ ‘ ’ (Blank) – Ignore the &RELEASE parameter.

&RESFREE Whether to include the CA-7 FREE status (A, F, N, or Y) of
resources in the Virtual Resource Management facility as a
prefix to the converted CONTROL-M Resource name.
■ N – Do not include the FREE status. Default.

■ C – Include FREE status for Control resources.
■ Q – Include FREE status for Quantitative Resources.
■ B – Include FREE status for both Control and Quantitative
resources.
&SCCGLBL Provides the ability to treat *-stepname in the stepname
parameter of the # SCC JCL override statement as if * alone had
been specified.
■ N (No) – The CTMCA706-01E message is displayed when

*-stepname is encountered. Default.
■ Y (Yes) – *-stepname is treated like *, that is, the

CONTROL-M ON PGMST parameter is set to +EVERY
when converting the # SCC statement. For more
information, see “10. COND-CODE, RO and # SCC” on
page 102.
■ F – Only the first occurrence of a # SCC JCL statement in

the member containing *-stepname is converted as above.
The CTMCA706-01E message is displayed for all other
occurrences.
The CTMCA706-01E message is described in “CTMCA706-

01E” on page 172.
&SCHDMOD SCHDMOD CURRENT calendar indicator. Enables you to
specify globally whether SCHDMOD CURRENT calendars are
automatically placed into the job scheduling definitions for all
applications. Valid values are:
■ N (No) – SCHDMOD CURRENT calendars are not

automatically placed into the job scheduling definitions for
all applications. Default.
■ Y (Yes) – SCHDMOD CURRENT calendars are

automatically placed into the job scheduling definitions for
all applications.
For more information, see “13. SCAL” on page 105, and “JOB2
- Create the Applications List, Calendar Libraries, and
Calendar Names List Files” on page 46.

&SHOUTDL Destination for SHOUT WHEN LATE and SHOUT WHEN
EXECTIME messages. For more information on valid values
and the default, see &SHOUTDT in this table.
&SHOUTDT Destination for SHOUT messages when a job failed. Valid
values are:
■ SYSUSER – Use the user ID associated with the specific job

or scheduling table. For more information, see &USEROPT
in this table. Default.
■ OPER – Issue the SHOUT message to the console.
■ OPER2 – Issue the SHOUT message to the console, as

highlighted and unrollable.
■ TSO-uid – Issue the SHOUT message to a specific TSO

user ID. The variable uid is a specific user ID of up to
7 characters
For information about additional options, see SHOUT in the

parameter descriptions chapter of the CONTROL-M for OS/390
and z/OS User Guide.
&SHOUTE The text (up to 50 characters) of the SHOUT WHEN LATE *
message that is sent when the job is still executing after its
DUE TIME time has passed. Specify ' ' (blank) to suppress the
message. The default is:
%%JOBNAME J%%JOBID STILL EXECUTING AFTER DUE
OUT!
&SHOUTL The text (up to 50 characters) for the SHOUT WHEN
LATESUB message that is sent when the submission time for
the job has elapsed. Specify ' ' (blank) to suppress the message.
The default is MEMBER %%$MEMNAME IS LATE!
&SHOUTT The text (up to 50 characters) for the SHOUT WHEN NOTOK
message that is sent when a job fails. Specify ' ' (blank) to
suppress the message. The default is:
%%JOBNAME J%%JOBID ENDED NOTOK!
&SHOUTX 2-digit value added to the weighted average elapsed runtime
of the job and used to determine the CONTROL-M SHOUT
WHEN EXECTIME parameter. Specify ' ' (blank) to suppress
this message. Default: 05.
For more information, see “38. SHOUT” on page 127.

&STARTM When an SBTM CA-7 submit time is specified, it is always
used as the CONTROL-M FROM TIME. When the SBTM is not
specified, the value of the &STARTM parameter determines
the FROM TIME, as follows:
■ Y (Yes) – The CA-7 deadline start time (STARTM

parameter on the LJOB report) is always used.
■ N (No) – The deadline start time is used only when the job
has no prerequisite IN conditions, accompanied by a
warning message, CTMCA705-06W; otherwise, the
CONTROL-M FROM TIME is left blank. Default.
&SUPMSG Whether messages are suppressed in JOB3. Valid values are:
■ ' ' (Blank) – Do not suppress any messages.

■ I – Suppress information messages.
■ W – Suppress warning and information messages.
&SWLPROP Whether to propagate the SHOUT WHEN LATESUB message
to all successor jobs of the head-of-tree job. Valid values are:
■ Y (Yes) – Propagate the SHOUT WHEN LATESUB

message to all successor jobs of the head-of-tree job.
Default.
■ N (No) – Do not propagate the SHOUT WHEN LATESUB

message to all successor jobs of the head-of-tree job.
&TAPE1 CONTROL-M Quantitative resource name for the CA-7
TAPE1 resource, corresponding to the value of the NAME
parameter of the CA-7 workload balancing TAPE1 macro.
Default: TAPE1
&TAPE2 CONTROL-M Quantitative resource name for the CA-7
TAPE2 resource, corresponding to the value of the NAME
parameter of the CA-7 workload balancing TAPE2 macro.
Default: TAPE2

&TOCLASS New output class to which CONTROL-M is to requeue the JCL
MSGCLASS sysouts of the job. Valid values are:
■ ' ' (Blank) – Reroute is not required.

■ * (Asterisk) – The MSGCLASS sysouts of the job must be
requeued to the original MSGCLASS after they are
analyzed by CONTROL-M. Default.
In this case, the &FROMC conversion parameter, which is
described in this table, is ignored, and the SYSOUT HELD
class is taken from the HLDCLS parameter in the
CTMPARM member in the IOA PARM library.
&UNTIL Time Until Indicator. The conversion tool does not set the
CONTROL-M TIME UNTIL scheduling parameter unless you
set the &UNTIL conversion parameter to >.
Valid values are:
■ > (Greater) – The TIME UNTIL parameter is set to > in

every job definition. Default.
■ ' ' (Blank) – The TIME UNTIL parameter is not set.
For more information, see the TIME parameter in the

&USERLEN When the &USEROPT conversion parameter is specified as
OWNER, JOB, APPL, JCLUSER, JCLGRP, or NOTIFY, this
parameter specifies how many characters of the specified
parameter are used for the CONTROL-M OWNER parameter.
Default: 8

&USEROPT Source for the CONTROL-M OWNER job scheduling
parameter. The OWNER parameter is useful for implementing
security checking by various CONTROL-M components.
In the following description of values, n is set by the

&USERLEN parameter, which is described elsewhere in this
table.
Valid values for &USEROPT are:
■ JOB – The first n characters of the job name in the

scheduling table. Default.
■ OWNER/xxxxx – The first n characters of the CA-7

OWNER parameter. xxxxxxxx is a fixed default value for
the OWNER parameter when OWNER=*NONE* is
specified.
■ APPL – The first n characters of the CONTROL-M

application name (APPL).
■ =xxxxxxxx – A fixed value of xxxxxxxx (1 through 8

characters) for every CONTROL-M job scheduling
definition.
■ CA7USERID/xxxxx – A fixed value of xxxxx (1 through 5

characters) followed by the CA-7 USR ID parameter of the
job.
The following options create an OWNER parameter derived

from the JCL JOB statement of the job.
■ JCLUSER – The first n characters of the JCL USER=JOB

statement parameter.
■ JCLGRP – The first n characters of the JCL GROUP=JOB

■ NOTIFY – The first n characters of the JCL NOTIFY=JOB

For these options, an OWNER ID of NOUSER, NOGROUP, or

NONOTIFY is specified for jobs whose JCL member cannot be
found and for jobs whose JOB statement does not contain a
USER, GROUP, or NOTIFY parameter, respectively.

Table 32 CA-DRIVER Variables
No. Variable Description
1 &C_L2UID CA-7 user security identification.
2 &C_L2SN Application system name.
3 &C_L2RO Relational operator of the condition code (OR if step level
# SCC statements are being used).
4 &C_L2CC Job level condition codes, used to determine whether a job
executes successfully.
5 &C_L2PRY CA-7 workload-balancing job priority.
6 &C_L2CLS CA-7 workload-balancing job class.
7 &C_L2# T1 TYPE1 tape drives needed for the job.
8 &C_L2# T2 TYPE2 tape drives needed for the job.
9 &C_L2DOT Job due-out time of day, for a particular schedule ID.
10 &C_L2MID Indicates on which CPU a job may or may not be scheduled.

Appendix
B Messages
This list contains only messages produced by the components of the conversion tool.
Messages issued by other CONTROL-M components are described in the
INCONTROL for OS/390 and z/OS Messages Manual.
A message code usually consists of the following parts:
CTMyyyaa-nnx
CTM indicates that the message pertains to CONTROL-M. The variables in the
message are:
Item Explanation
yyy 3-character identifier of the conversion tool component that produced
the message. Examples:
■ CA7—CTMCA7aa-nnx
■ CA-DRIVER—CTMDRyaa-nnx
aa 2-character identifier for the component that produced the message.
nn 2-character numeric identifier for the message.
x 1-character alphabetic identifier for the severity of the message. Valid
values are:
■ R – Action
■ E – Error
■ I – Information
■ S – Severe
■ W – Warning

Message descriptions contain any or all of the following:
Explanation: A description of the cause of the message, and other related information.
System Action: System action when this message is issued.
User Response: Recommended actions to correct the problem.
CTMCA701-01S
LJOB NOT SORTED IN JOBNAME ORDER, JOB jobname
Explanation: Beginning at the jobname job, the CA-7 LJOB report is not sorted in job
name order.
System Action: The step terminates with a return code of 12. The rest of the job is
flushed.
User Response: Do the following:
1. Ensure that all CA-7 LJOB reports are concatenated in sorted job name order, or
that all multiple CA-7 LJOB commands in the CA-7 Batch Terminal program are in
sorted job name order and do not overlap.
2. Recreate the CA-7 LJOB report.
3. Rerun the conversion from JOB1.
CTMCA702-00W
NO JCL LIBRARIES FOUND IN INITDECK. JCL PROCESSING BYPASSED
Explanation: No CA-7 JCL control statements were found in the CA-7 Initdeck file.
System Action: JOB3 bypasses all JCL checking and processing.
CTMCA702-01W
JOB NAME jobname DIFFERENT FROM JCL MEMBER NAME
Explanation: The jobname CA-7 job name differs from its JCL member name.
In CONTROL-M, jobs are identified by their JCL member names, and the conversion
tool uses the JCL member name as the job identifier. When the CA-7 job name differs
from its JCL member name, the conversion tool creates an INCLUDE member in the
library referenced by the DAINCLIB DD statement.
User Response: Consider installing CONTROL-M Exit 2. For more information, see
“Step 12 - Modify and Run the JOB8 Member (Optional)” on page 84.

CTMCA702-03E
CONTROL-M SCHEDULING TABLE NAME tablename NOT UNIQUE
Explanation: The Applications List file (the DASYN DD statement) contains duplicate
occurrences of the tablename CONTROL-M scheduling table name. Since scheduling
table names are also PDS member names, they must be unique.
1. Replace duplicate occurrences of tablename in the Applications List file with unique
scheduling table names
2. Rerun JOB3.
CTMCA702-04E
CONTROL-M SCHEDULING TABLE NAME tablename NOT A VALID PDS MEMBER NAME
Explanation: The Applications List file (the DASYN DD statement) contains an

invalid CONTROL-M scheduling table name, identified by the variable tablename.
1. Replace tablename in the Applications List file with a valid PDS member name.
2. Rerun JOB3.
CTMCA702-05W
JCL FOR CA-7 JOB jobname SET FOR OVERRIDE LIBRARY
Explanation: The CA-7 job definition for the jobname job states that the JCL member of
the Override library must be used for the next run of jobname. However, the
conversion uses the JCL member from the original library (identified by the CA-7
JCL ID).
User Response: Check modifications of the JCL in the Override library. The
CONTROL-M AutoEdit facility can be used to perform JCL modifications.
CTMCA702-06W
TRIGGERING NETWORK network_name IN JOB jobname NOT SUPPORTED
Explanation: Triggering networks are not supported and are not converted.

CTMCA702-07W
APPLICATION LIST FILE EMPTY. PROCESSING STOPS
Explanation: The Application List file contains no data.
The error may be due to one of the following:
■ The DASYSN DD statement in JOB3 does not point to the correct file.
■ An error occurred when JOB2 was creating the Application List file.
■ You may have modified the LJOB command in JOB1 (LJOB,JOB=*) to produce only
a subset of all the CA-7 jobs, which may have been insufficient to produce an
Application List file in JOB2.
1. Check that DASYSN points to the correct file, correct the JCL, and rerun JOB3.
2. Correct any error in JOB2, and rerun JOB2 and JOB3.
3. Specify a more generic JOB parameter in the LJOB command of JOB1 so as to

generate sufficient jobs to produce an Application List file, then rerun JOB1, JOB2,
and JOB3.
CTMCA702-08W
JOB jobname, DSN CONNECTION CREATED BY MULTIPLE JOBS dsn
Explanation: The jobname job contains a DSN-type job connection. The dsn data set
that creates the connection can be created by more than one job.
User Response: You must manually define IN prerequisite conditions, OUT
prerequisite conditions, or both, to connect the creating jobs to the jobname job in the
respective CONTROL-M job scheduling definitions.
System Action: The dsn connection is ignored.
CTMCA702-09E
JOB jobname CONTAINS UNKNOWN CONDITION-CODE RELATION
Explanation: The CA-7 job definition for the jobname job contains a job-level condition
code that uses an unknown relational operator.
System Action: The condition code is ignored by the conversion tool.
User Response: Do either of the following:
■ Correct the relation operator in the RO parameter of the CA-7 database, and rerun
JOB1 and JOB3.

■ Modify the CONTROL-M job scheduling definition.
CTMCA702-10E
ERROR WHILE SCANNING CA-7 INITDECK
Explanation: A problem occurred while the conversion tool was analyzing relevant
lines in the CA-7 Initdeck member. The conversion tool uses the CA-7 Initdeck in
order to extract the CA-7 JCL library names, determine the job entry subsystem to
which JCL is submitted (JES2 or JES3), and so on.
User Response: Correct the specification of the DAINIT DD statement in the JCL of
JOB3 and rerun the job.
CTMCA702-11S
JOB jobname DUPLICATED IN CA-7 LJOB REPORT
Explanation: The conversion tool found the jobname job twice in the LJOB report.
Since job names are unique in the CA-7 database, the error is probably due to a
problem in the DAREPORT DD statement in the JOB3 JCL member.
System Action: The program terminates.

1. Correct the specification of the DAREPORT DD statement in the JCL of JOB3, and
rerun JOB3.
2. Make sure that you have not concatenated multiple LJOB reports that contain jobs
of the same name. If this is the case, each LJOB must be separately converted.
CTMCA702-17S
PARM VALUE SMALLER THAN NUMBER OF JOBS
Explanation: JOB1 and JOB3 contain a parameter that specifies the maximum number
of jobs that can be handled. In the case of JOB1, this parameter is in the PARM
parameter in the EXEC statement of STEP5. In the case of JOB3, it is in the PARM
parameter in the EXEC statement of STEP2. The CA-7 LJOB report contains more jobs
than the value specified in that parameter.
User Response: Increase the relevant PARM value or values, and rerun JOB1, JOB3, or
both JOB1 and JOB3, as appropriate.

CTMCA702-20W
JOB jobname SCHEDULE ID schid CONTAINS DOTM/STARTM BEFORE NEWDAY TIME, AND
SUBTM IS AFTER
Explanation: The jobname CA-7 job definition for schedule ID schid specifies either
DOTM or STARTM between midnight and the CONTROL-M New Day Start time
(that is, the start of the new logical workday), but the SUBTM time is after the New
Day Start time.
Generally, SHOUT WHEN LATE messages are issued at the start time of the job.
However, when the submission time is after the New Day Start time, the SHOUT
WHEN LATE message is only issued after the New Day Start time.
CTMCA705-01W
JCL MEMBER memname NOT FOUND IN lib – WILL NOT BE EXECUTED, RC=nn
Explanation: During the conversion process the JCL member of each job is read in
order to extract additional information. The specified JCL member could not be
found in the lib library, or in its alternate JCL library, if one was specified using the
ALT parameter of the JCL Initialization Statement.
For an explanation of the return code nn, see the CTMCA799-03S message.
System Action: The CONTROL-M job scheduling definition is created, but the job
cannot run if the JCL member cannot be found.
User Response: Determine whether the job is needed. If it is needed, create a JCL
member for the job.
CTMCA705-02S
SYSTEM sysname SCHID schid NOT FOUND IN APPLS TABLE – PROCESSING STOPS
Explanation: While trying to assign the CONTROL-M scheduling table name to a job,
its CA-7 system name and schedule ID could not be located in the Applications List
file. This error indicates that the Applications List file was probably incorrectly
modified manually.
System Action: The job stops processing.
User Response: Correct the Applications List file and rerun JOB3.
CTMCA705-03E
JOB jobname NOT INCLUDED IN LJOB REPORT, TRIGGERING JOB trigjob
Explanation: The conversion tool could not find the jobname job in the LJOB report.
This message may be due to one of the following:

■ The jobname job, which is triggered by the trigjob job that appears in the LJOB
report, does not itself appear in the LJOB report.
■ The jobname job, as specified in a DEMAND command in a CA-7 Batch Terminal

step in the trigjob job, does not appear in the LJOB report.
■ The jobname job, which appears as a dependent (successor) job of the trigjob job in
the LJOB report, does not itself appear in the LJOB report.
System Action: The conversion tool cannot define the jobname job.
User Response: Determine whether the jobname job is needed. If it is needed, do one of
the following:
■ Check and correct the CA-7 database (for the jobname job) and rerun JOB1 and
JOB3.
■ Modify the CONTROL-M scheduling table.
CTMCA705-04I
WRITING SCHEDULE MEMBER memname TO DDNAME ddname
Explanation: Informational message indicating that a CONTROL-M scheduling table

memname is to be written to the scheduling library pointed to by ddname.
CTMCA705-05E
TOO MANY LEVELS FOR JOB TREE STARTING WITH JOB jobname SCHEDULE ID schid
Explanation: As supplied, the conversion tool can handle job trees of up to 255 levels.
The specified job tree contained too many levels.
This usually means that a recursive job tree has been defined in the CA-7 database for
the CA-7 jobs. The recursive job can be defined by triggering, or by a DEMAND from
the JCL.
User Response: Verify that there is no recursive job tree in the CA-7 database.
CTMCA705-06W
JOB jobname SCHEDULE ID schid WILL BE SUBMITTED IMMEDIATELY AFTER NEWDAY
Explanation: The jobname CA-7 job definition for the schid schedule ID contains no
prerequisite conditions.
Since CONTROL-M submits jobs at the earliest possible time, this job is submitted
immediately after the New Day procedure.

User Response: Verify the CONTROL-M job scheduling definition. If required, a
FROM parameter can be added to the job scheduling definition.
CTMCA705-07S
ERROR ACCESSING DDNAME DAINCLIB. %%INCLUDE MEMBERS CANNOT BE CREATED
Explanation: When the CA-7 job name differs from its JCL member name, the
conversion tool creates an INCLUDE member in the library referenced by the
DAINCLIB DD statement. This message indicates that an error occurred when the
program tried to obtain the name of the library.
User Response: Verify that the DAINCLIB DD statement is pointing to a correctly
allocated PDS.
CTMCA705-08I
JCL INCLUDE MEMBER memname CREATED IN LIBRARY DAINCLIB
Explanation: This information message indicates that a JCL INCLUDE member has
been written to the INCLIB library pointed to by the DAINCLIB DD name.
CTMCA705-09E
NUMBER OF OCCURRENCES OF JOB jobname IN SCHEDULING TABLE tbl EXCEEDS THE

MAXIMUM VALUE
Explanation: As a result of CA-7 JCL DEMANDs or recursive TRIGGERED JOBS

definitions (in LJOB), the jobname job has exceeded the maximum number of
occurrences defined by &JOBMXOC in the DEFAULTS member in the tbl scheduling
table.
System Action: The job continues processing, but ignores any further occurrences of
the specified job.
1. Check the JCL DEMANDs or the TRIGGERED JOBS definition within the
application structure. If jobname is a non-recursive JCL DEMAND job, consider
increasing the value of &JOBMXOC.
2. Either manually restructure the application by means of CONTROL-M features

such as ON PGMST or DO FORCEJOB, or increase the value of &JOBMXOC.
3. Rerun the ASMLINK and JOB3 jobs.

CTMCA705-10E
DCAL CALENDAR NOT FOUND FOR JOB jobname
Explanation: The conversion tool could not find a calendar in the Calendar Names
List file (created by JOB2) to supply the proper calendar name in the DCAL
parameter of the CONTROL-M job scheduling definition.
Most likely, the CA-7 job schedule was not RESOLVEd. Therefore, no schedule day
calendar was available for display in the LSCHD report, produced in JOB0, to be used
in the CONTROL-M DCAL parameter. This leads to improper Basic Scheduling
parameters being created in the job scheduling definition.
System Action: JOB3 continues processing.

1. Ensure that all CA-7 scheduling members are RESOLVEd.
2. Rerun STEP2 of JOB0 to recreate the LSCHD report.
3. Rerun JOB2 and JOB3.
Alternatively, you can manually update the CONTROL-M job scheduling definition
to conform to the CA-7 scheduling definition parameters.
CTMCA705-11W
JOB jobname SCHEDULE ID schid IS TRIGGERING/DEMANDING ITSELF. USE CYCLIC JOB
Explanation: The conversion tool found that the jobname job of the schid schedule ID is
either triggering or demanding itself. To prevent such looping, the conversion tool
ignores this recursive definition.
User Response: Use the CONTROL-M TASKTYPE cyclic job scheduling definition to
accomplish this task. To prevent the job from being continually resubmitted, it is
recommended that the cyclic job either delete the prerequisite conditions that
triggered its operation, or set a TIME UNTIL parameter.
CTMCA705-12W
JOB jobname RELATION OPERATOR ‘ro’ NOT SUPPORTED IN #SCC
Explanation: In a CA-7 # SCC JCL override statement in the jobname job, the
conversion tool encountered a relational operator, ro, that is not supported by
CONTROL-M.
System Action: The job continues processing, but the # SCC statement is ignored.

CTMCA705-14I
PHASE 2
Explanation: The CA-7 conversion tool is entering a second phase, converting any
CA-7 jobs that were not processed during the main conversion phase.
Normally, if the CA-7 database (the LJOB report) was maintained as required, you do
not see any further messages after this message. If there are any further messages, the
probable reason is that the CA-7 database contains “orphan” job definitions or
“broken” triggering structures. Conditions of those types are normally indicated by
occurrences of the CTMCA705-O3E message during the main conversion phase.
System Action: Normal processing continues.

1. Examine any scheduling tables written during the second phase.
2. Try to eliminate all occurrences of the CTMCA705-03E message. This will

minimize the number of messages following the CTMCA705-14I message.
CTMCA705-24S
NUMBER OF CALENDARS EXCEEDS MAXCALS VALUE
Explanation: The number of calendars produced in JOB2 exceeds the value specified
in the &MAXCALS conversion parameter.
1. Increase the value of the &MAXCALS conversion parameter in the DEFAULTS

member.
2. Rerun the ASMLINK and JOB3 jobs.
CTMCA706-01E
JOB=jobname ERROR IN FORMAT OF #SCC LINE
Explanation: The conversion tool encountered an invalid or unsupported parameter

when converting a # SCC CA-7 JCL override statement for the jobname job.
System Action: The conversion tool may create a partial ON PGMST post-processing
parameter and continue processing. If the step name is of the format *-stepname, the
# SCC statement is not processed.
User Response: Modify the CONTROL-M ON PGMST parameter in the job
scheduling definition of the jobname job.

CTMCA706-02E
JOB=jobname ERROR IN U11RMS PARM
Explanation: While processing the jobname job in a CA-7 or CA-11 JCL library, the
conversion tool encountered an invalid PARM parameter in a CA-11 U11RMS step.
System Action: The PARM parameter is not converted, but the job continues
processing.
1. Correct the PARM parameter. For more information, refer to the CA-11 User Guide.
2. Rerun JOB3.
CTMCA706-03E
JOB=jobname DEMAND ERROR IN JOB=, SCHID= OR DEPJOB=
conversion tool encountered an invalid JOB or SCHID or DEPJOB parameter in a
CA-7 DEMAND[H] statement.
The JOB or DEPJOB parameter may contain a jobname exceeding eight characters, or
the SCHID may contain a non-numeric schedule-id, or a schedule-id exceeding eight
digits.
System Action: The DEMAND statement is not processed, but the job continues
processing.
User Response: Correct the DEMAND statement and rerun JOB3.
CTMCA707-00R
HAVE YOU ENSURED THAT PROD JCL LIBRARIES WILL NOT BE MODIFIED (SECT3/STEP2)
(Y/N)?
Explanation: This query is always issued by JOB4 to force verification that Step 2
(described in “Step 2 - Copy CA-7 and CA-11 JCL and CA-DRIVER Libraries and
Initdeck” on page 73) has been carefully followed, so that copies of the Production
JCL libraries are converted to CONTROL-M format and not the actual Production
JCL libraries. For more information, see “&PNIBTSD” on page 154.
System Action: If the reply is N, the program terminates without processing the JCL
libraries. If the reply is Y, normal JCL library conversion is performed.
User Response: Reply Y (Yes) or N (No) as appropriate.

CTMCA707-01S
TOO MANY BTERM ENTRIES. MAX IS 10
Explanation: The number of Batch Terminal Parameter Control Statements (the

DABTERM DD statement) may not exceed 10.
System Action: Processing terminates.
User Response: Contact your local INCONTROL representative.
CTMCA709-01E
JOB=jobname, BATCH TERMINAL COMMAND cmd COULD NOT BE CONVERTED
Explanation: A Batch Terminal in-stream command, a Batch Terminal JCL PARM

parameter, or the Batch Terminal SYSIN DD statement could not be processed.
Possible reasons include the following:
■ An in-stream DEMAND command did not specify the JOB parameter.
■ An in-stream POST command did not specify one or more of the following
parameters:
— the JOB parameter

— the DEPJOB parameter
— the USR parameter
■ In trying to convert a DEMAND, POST or RESCHNG command in a JCL PARM

parameter, the equivalent CTMUTIL command overflowed column 71, and could
not be contained on one JCL line.
■ The Batch Terminal SYSIN DD statement does not specify in-stream data, and the
JCL DSN parameter could not be found in the SYSIN DD statement.
■ In a DEMAND or POST command, the JOB or DEPJOB parameters can contain a

job name that exceeds 8 characters, or the SCHID parameter can contain a schd-id
that exceeds 3 digits.
■ An in-stream RQVER command specified UPDATE=YES, which is not supported.
■ An in-stream ADDRQ or D=dsn command was specified, but these are not
supported.
■ For errors involving SYSIN (only), the explanation is contained in the message
immediately preceding this message.
System Action: The cmd command is not converted, or is only partially converted.

User Response: Inspect the indicated JCL member, and manually convert the cmd
command (or commands).
CTMCA709-02W
JOB=jobname, UNSUPPORTED PARM COMMAND
conversion tool encountered an unsupported PARM parameter in a CA-7 Batch
Terminal step.
User Response: Examine the PARM parameter to determine if any manual actions are
necessary to incorporate the unsupported feature in CONTROL-M.
System Action: The PARM parameter is nullified by placing a blank at the end of the
PARM statement.
CTMCA710-01E
JOB jobname NOT FOUND IN XREF FILE OR HAS NO SCHEDULING TABLES
Explanation: According to the CA-7 Job-to-Resource Cross Reference report, the

jobname job uses certain resources. However, this job either does not appear in the
Cross Reference file created by JOB3, or is not contained within any CONTROL-M
scheduling table.
User Response: Check if this job appears in the LJOB report that was used by JOB3.
CTMCA710-03I
SCHEDULING TABLE tbl UPDATED WITH NEW RESOURCES
Explanation: Informational message indicating that the tbl scheduling table in the
scheduling table library has been updated with new resources or conditions.
CTMCA710-04E
SCHEDULING TABLE tbl NOT FOUND IN DASCHD
Explanation: The tbl scheduling table, which requires a resource or condition update,
could not be found in the scheduling libraries pointed to by the DASCHD
DD statement.
The Job-to-Resource Cross Reference report may not agree with the LJOB report.
User Response: Ensure that the Resource Cross Reference report and the LJOB report
are synchronized, and rerun JOB5.

CTMCA710-10S
XREF FILE EMPTY. PROCESSING STOPS
Explanation: The Cross Reference file contains no data. The error may be due to one of
the following:
■ The DAXREF DD statement in JOB5 does not point to the correct file.
■ An error occurred when JOB3 was creating the Cross Reference file.

User Response: Check if the DAXREF DD statement points to the correct file.
If it does not, correct the JCL, and rerun JOB5.
If it does, do the following:
1. Check the Cross Reference file created by JOB3 and make any necessary
corrections.
2. Rerun JOB3.
3. Rerun JOB5.
CTMCA710-12E
DAREPIN FILE EMPTY
Explanation: The CA-7 Resource Management report contains no processable data.
The error may be due to one of the following:
■ The DAREPIN DD statement in JOB5 does not point to the correct file.
■ The &REL conversion parameter in the DEFAULTS member was incorrectly
specified.
■ there are no processable resources contained in the DAREPIN file. Only the
following types of resource are supported:
— exclusive
— shared
— corequisite
— resource count resources.
■ Check if the DAREPIN DD statement points to the correct file.
If it does not, correct the JCL, and rerun JOB5.

If it does, check that the proper CA-7 release number was specified in the &REL
conversion parameter, then correct and rerun ASMLINK and JOB5.
■ If the DAREPIN file contains no processable resources, no further action is

required, unless you want to convert the non-supported resources manually.
CTMCA799-02E
func FAILED FOR BLOCK blockname [MEMBER=memname DDNAME=ddname]
Explanation: The func MVS memory acquisition or freeing function (GETMAIN or

FREEMAIN) failed for the blockname block. The JCL REGION parameter specification
is not large enough.
If the message is issued by JOB1 or JOB3, it is possible that the PARM value on the
EXEC statement is too high. In some cases, the name of the member (memname) and
DD name (ddname) for which the function failed are displayed in the message.
User Response: Increase the value of the REGION parameter.
CTMCA799-03S
CTMMEM FUNCTION func FAILED WITH RC rc [MEMBER memname] [DDNAME ddn|DSNAME

dsn]
Explanation: An error occurred in the func CTMMEM function.
The CONTROL-M CTMMEM routine is used to perform operations on PDS libraries

and members. Return codes that indicate the cause of failure are explained in the list
below.
■ 04 – end of file (in GETLINE operation)

■ 08 – insufficient memory to continue
■ 12 – member not found in library
■ 16 – data set not a library
■ 20 – data set not fixed format
■ 24 – LRECL not 80
■ 28 – data set in use
■ 32 – internal error; for example, there were insufficient directory blocks, or the file
was not allocated
■ 36 – data set not found in catalog
■ 40 – dynamic allocation failed; for example, there were insufficient directory
blocks, or the file was already in use.
■ 44 – invalid request to CTMMEM

■ 48 – maximum number of lines or directory entries exceeded
■ 52 – error opening or processing (or both opening and processing directory; for
example, there were insufficient directory blocks
■ 56 – STAE has intercepted an abend; examples are:
— insufficient REGION
— out-of-space condition
— security violation
— invalid PDS structure
— RLSE coded in the JCL SPACE parameter
— third party vendor product, such as VAM, STOPX37,
HIPER-CACHE, or ULTIMIZER
■ 60 – member does not exist during save
■ 64 – member already exists
■ 68 – format parameter does not match library type
CTMCA799-04E
TOO MANY MEMBERS IN LIBRARY lib
Explanation: JCL Library lib contains more members than are specified in the
&DIRMAX DEFAULTS member parameter.
System Action: The library is not processed.
1. Increase the value of the &DIRMAX parameter.
2. Rerun the ASMLINK job.
3. Rerun the affected job.
CTMCA799-06E
MEMBER memname CONTAINS TOO MANY LINES AND IS SKIPPED. PROCESSING

CONTINUES
Explanation: The memname JCL member contains more lines than are specified in the
&LINMAX DEFAULTS member parameter.
As a result of modifications to the JCL member by the conversion tool, such as

insertion of AutoEdit statements, the number of lines in the member may exceed
&LINMAX.
System Action: The job continues processing, but the specified member is skipped.

1. Increase the value of the &LINMAX parameter.
3. Rerun the affected job.
CTMCA799-08I
PROCESSING ENDED FOR LIBRARY lib
Explanation: This information message indicates the completion of the conversion

from CA-7 format to CONTROL-M format of all members of JCL Library library.
CTMCA799-09I
MODIFICATIONS WERE DONE TO MEMBER memname LIBRARY lib
Explanation: This information message indicates that the memname JCL member, or a
member (memname) pointed to by the SYSIN statement in a JCL member, has been
modified. Note that lines may have been deleted without conversion from the
memname member because their function was not supported by the converted
CONTROL-M utility.
CTMCA799-13S
TOO MANY LIBRARIES IN INPUT. MAX IS 256
Explanation: The input list (the DAJCLIN DD statement) may contain up to 256
library names. This maximum has been exceeded.
User Response: Split the input list into different runs of the job.
CTMCA799-18S
module NOT FOUND
Explanation: The job could not find the CTMMEM CONTROL-M installation
parameters load module.
User Response: Check that the IOA LOAD library is specified in the STEPLIB
DD statement, then rerun the job.

CTMCA7V5-01S
PARM VALUE SMALLER THAN NUMBER OF LINES IN TABLE tblname
Explanation: JOB7 contains a parameter in the PARM parameter of the EXEC

statement of STEP2 that specifies the maximum number of lines it can handle in a job
scheduling table. The job attempted to build a Group Scheduling table (tblname) with
more lines than that value.
User Response: Increase the PARM value, then rerun JOB7.
CTMCA7V5-11E
COND cond_name NOT ADDED TO TABLE tblname
Explanation: When the &DELCOND option in the DEFAULTS member is set to “A”,
the conversion can create a maximum of 600 OUT conditions in a group entity to
delete conditions. This message indicates that this group scheduling table already
contains 600 defined OUT conditions and no additional conditions will be added to
the table.
System Action: The program continues executing.
User Response: Manually split the group scheduling table into multiple tables,
thereby reducing the number of OUT conditions in each table.
CTMCA7V5-12S
MAXIMUM GROUP-ENTITY SIZE EXCEEDED, INCREASE MAXGENT
Explanation: The maximum number of lines in a group entity has been exceeded.
System Action: The program terminates with a return code of 12.
User Response: Increase the value of the &MAXGENT parameter in the DEFAULTS
source member, then rerun the ASMLINK and JOB7 jobs. The value of the
&MAXGENT parameter should be approximately 5% of the number specified in the
PARM of the EXEC statement in STEP2 of JOB7.
CTMDRPRC-05E
UNSUPPORTED/UNKNOWN OPTION memname : text, stmt
Explanation: Either the conversion tool does not support the CA-DRIVER feature
specified (statement), or an error was encountered while attempting to convert a JCL
or CA-DRIVER procedure statement in the memname member in a JCL or
CA-DRIVER procedures library.
The variables in this message are:
■ text – a description of the error

■ stmt – the JCL or CA-DRIVER procedure statement

User Response: Determine whether the procedure is needed. If it is needed, correct the
error and rerun JOB8. If it is an unsupported option, you can manually complete the
JCL member conversion, if required.
CTMDRPRC-06E
UNSUPPORTED OPTION: CA-7 CAJUTIL0/CAICHERL UTILITY. MEMBER memname
Explanation: The conversion tool does not support the CA-7 CAJUTIL0 or
CAICHERL report utilities specified in a JCL or CA-DRIVER procedure member.
System Action: The JCL or CA-DRIVER procedure member (memname) containing the
unsupported option is not converted.
User Response: You can manually complete the procedure member conversion, if
required. For CONTROL-M reporting options, see the discussion of reporting
facilities in the INCONTROL for OS/390 and z/OS Utilities Guide.
CTMDRPRC-07S
MORE THAN MAXIMUM SIZE OF GETMAIN IS REQUIRED
Explanation: An MVS GETMAIN function failed.

1. Increase the value of the AREASIZE parameter, which specifies the maximum
number of bytes for GETMAIN, in the CTMDRPRC program.
3. Rerun JOB8.
CTMDRV01-09I
CA-DRIVER PROCEDURES CONVERSION ENDED
Explanation: This information message indicates that the conversion of the

CA-DRIVER procedure libraries has ended.
CTMDRV02-08I
JCL LIBRARIES CONVERSION ENDED
Explanation: This information message indicates that the conversion of the JCL
procedure libraries has ended.

CTMDRV02-11S
PROCEDURE LIBRARY IS EMPTY
Explanation: The CA-DRIVER procedure library (the DAPROC DD statement) has no

members.
1. Check previous messages of JOB8 in the Conversion messages file (the DAMSG
DD statement).
2. Correct any errors accordingly.
3. Rerun JOB8.
CTMDRV02-12E
MAXIMUM LENGTH OF MEMBER NAME EXCEEDED FOR JOB jobname
Explanation: While trying to convert the jobname job to CONTROL-M format, a

member name length was exceeded.
In CA-DRIVER, default values can be specified for the procedure variables in the
EXEC statement. The conversion tool creates a member that contains a CONTROL-M
Auto-Edit %%SET control statement for each default value. The name assigned to this
member is the job name with a suffix of an ascending number appended to it. For
more information, see Chapter 4, “Conversion Details.”
The member name length exceeded the maximum allowed, which is 8 characters.
System Action: The jobname job is not processed.

User Response: Determine whether the jobname job is needed. If it is needed, a manual
modification is required.
CTMDRV02-13E
UNSUPPORTED/UNKNOWN OPTION memname : text, stmt
Explanation: See message CTMDRPRC-06E on page 181.
CTMDRV02-14E
UNSUPPORTED OPTION: CA-7 CAJUTIL0/CAICHERL UTILITY. MEMBER memname
Explanation: See message CTMDRPRC-05E on page 180.

Appendix
C Planning The Conversion

To assist the smooth running of the conversion process, BMC Software recommends
that you carry out a number of steps before starting the conversion itself. These steps
are set out in this appendix.
This appendix outlines the key Business Integrated Scheduling (BIS) functions and
environmental metrics required to determine the initial level of effort associated with
the migration of business processing to CONTROL-M.
1: Organize the Conversion Team

1. Identify those who will be involved in the conversion process. They should
participate in planning the conversion and implementing the steps in this
appendix before beginning the conversion.
Include in this list those who support the current environment and who require
training or retraining and/or mentoring, such as operators, production control
administrators, product administrators, production analysts, application support
and programming personnel, security administrators, and so on.
2. Ensure that the conversion team has sufficient knowledge of
■ the features and operation of
— CA-7
— CONTROL-M
— the conversion utilities
■ your existing scheduling information and its operation procedures
■ your site rules on data set organization, naming conventions, and so on
■ your expectations from the conversion project

1: Organize the Conversion Team
3. Identify the exact release or version number of CA-7 that you are currently using.
4. Identify the operating system and platforms to be supported by CONTROL-M in

the target environment. In relation to each platform, identify the release level,
number of systems, and physical location.

2: Analyze Your Hardware
2: Analyze Your Hardware

Consider the configuration of the system currently in use at your site, and whether
you are making the best use of your hardware resources.
Obtain sufficient information to respond to the issues raised in this section. Record
the answers carefully, because they will be of importance during and after the
conversion to CONTROL-M.
■ What resources, such as tape drives, initiators, and so on, do you use at your site?
■ What MVS images, that is, CPUs, LPARs, and Sysplexes, will be available to
CONTROL-M when running production jobs?
■ How are your MVS images connected? Is the connection by
— coupling facility
— shared spool
— NJE
— some other method
Are the systems managed separately or collectively? Is there job flow between
systems?
■ Do you currently have multi-system dependencies, either on the same platform

type, or using different platforms? If so,
— how many?
— how are they managed?

3: Consider Current Practices

Consider the current practices at your site. The relevant issues include at least the
questions set out in this section. Do not hesitate to ask others for information they
may be able to provide. Take all software and hardware platforms into account when
answering. Record the answers carefully, because they will be of importance during
and after the conversion to CONTROL-M.
1. How is production scheduling currently handled on your computers?
2. Who currently uses your system?
■ Is there a single production department or are there several?

■ Who are the end users of the system?
3. Consider the typical application flows at your site. The following are useful
questions to ask:
■ Which are the three key applications, in terms of size, complexity, or value to
your business?
■ How are those applications scheduled?
■ How are their internal dependencies managed?
■ Are there currently any performance bottlenecks or constraints in scheduling

implementation?
4. List any products you use to support production scheduling, such as console
automation, job restart products, and so on.
■ What function does each such product perform?

■ Will CONTROL-M replace that function?
If you think that CONTROL-M will not make some product redundant, obtain as
much information as possible about that product, to enable you to decide how the
product will interface with CONTROL-M.
5. List all your applications, interfaces, user or system exits, reports, and similar
material, that
— operators, system programmers, and other third parties have customized, and
— form part of the implementation of your current production scheduling

Include interfaces used to submit jobs from an internal front-end process, as well
as any interface used to issue commands and/or perform tasks using batch utility
programs.
Consider whether you can use CONTROL-M to implement these functions and/or
features.
6. Do you manually schedule any jobs or their logical successors on demand, instead
of allowing the system to schedule jobs? If you do,
■ list each job and record the way you deal with it
■ consider whether CONTROL-M can be used to schedule these jobs
automatically
7. Do your jobs run automatically, on rigid scheduling, or do you frequently modify

job schedules and/or dependencies to meet needs as they arise?
8. Consider your job concurrency requirements, and the way you meet those
requirements. Examples of questions to ask are the following:
■ Do you use job triggering, so that the completion of one job causes another job to
be submitted or ordered?
■ Do you use job dependencies, meaning that one job (the “waiting job”) does not
start until another has finished, even though the waiting job is submitted or
ordered in some other way?
■ Do you use negative job dependencies, meaning that if a job fails, another job
starts?
9. How do you manage such resources as tape drives, initiators, and so on?
10. Consider the following questions about the jobs your systems currently perform:
■ How many jobs do you currently have defined?

■ How many jobs are run on a daily, weekly, or monthly basis?
■ How many jobs run on peak days, for example, end of year processing?
■ How many jobs run “on request”, that is, demand jobs (see Question 6)?
■ Are your existing job definitions satisfactory in every respect?
■ Do you use all your existing job definitions, or are many now obsolete?
■ How many jobs use JCL automation features? Identify the type of automation
used.
■ How many jobs are scheduled using data set triggering?
■ How many jobs require manual intervention prior to submission?

11. How many jobs use JCL automation features? Identify the type of automation
used.
12. How many jobs are scheduled using data set triggering?
13. How many jobs require manual intervention prior to submission?

4: Read the Conversion Guide

Read through this conversion guide. While doing so, consider the following points.
1. Identify any “special” situations. These can arise where
■ the conversion will not be performed automatically

■ your existing system is otherwise incompatible with CONTROL-M, for
example, where calendar generation may serve as a substitute for some
scheduling parameters
Are the proposed solutions acceptable in all cases? If not, identify alternative
solutions, such as the use of the supplied user exits.
2. Is there any aspect of the way you use CA-7 that may not be reflected in the reports
and parameter files used by the conversion program?
3. Prepare the names to be used for libraries, table names, job names, conditions,
resources, and so on, in the output of the conversion, in order to reflect the way
you want the CONTROL-M environment to appear to users.
4. Consider whether at this stage you are converting the entire production
environment, or just one application? If you are only converting one application,
determine
■ how typical it is of the work done at your site

■ what are the principal differences between this application and other
applications
Consider whether you can yet identify any other pitfalls ahead, and if so, how to
avoid the problems they appear to present.


Appendix
D The CTMUTIL Conversion Utility

This appendix details the CTMUTIL utility program, which is available with the
conversion tool. This utility is independent of the conversion tool, and is not required
for a successful conversion to CONTROL-M. However, the utility may be very useful
either during or after the conversion process.
The CTMUTIL utility is used to invoke the IOACND IOA utility, and the CTMJOB,
and CTMRELRS CONTROL-M utilities. For a detailed description of these utilities,
see the INCONTROL for OS/390 and z/OS Utilities Guide.
In JOB4, the CTMUTIL utility replaces the CA-7 Batch Terminal steps in the
converted CA-7 JCL libraries. It provides the equivalent functionality.
■ The CTMUTIL utility invokes the IOACND utility to do the following:
— to add conditions to the IOA Conditions file, using the command ADD COND
condition_name ODAT
— to replace CA-7 POST commands
— when the &DEMAND conversion parameter is set to CTM, to replace CA-7

DEMAND[H] commands.
The &DEMAND conversion parameter is described in “&DEMAND” on page 148.
■ The CTMUTIL utility invokes the CTMJOB utility to do the following:
— to force jobs into the CONTROL-M Active Jobs file, using the command ORDER
DD=DMD MEM=demanded_job FORCE
— to replace CA-7 DEMAND[H] commands when the &DEMAND conversion

parameter is set to CA-7. The CTMUTIL utility does not support the SELECT/
IGNORE TAG feature of CTMJOB. The &DEMAND conversion parameter is
described in “&DEMAND” on page 148.
Appendix D The CTMUTIL Conversion Utility 191

■ The CTMUTIL utility invokes the CTMRELRS utility to change the quantity of
Quantitative resources required by a job to replace CA-7 RESCHNG commands.
The command format is CHANGE RESOURCE resource_name quantity.
You must set up a JCL procedure with the procedure name CTMUTIL for invoking
the CTMUTIL utility program. The procedure must include the following
DD statements:
■ STEPLIB (IOA LOAD library)

■ DAPARM (IOA PARM library)
■ SYSPRINT
■ DAPRINT
■ PRTDBG (dummy)
■ DALOG
■ DACNDF
■ DACKPT
■ DMD
■ SYSIN (optional)
The files to which these DD statements refer can be determined directly from the
existing CONTROL-M IOACND, CTMJOBPR and CTMRELRS procedures, which
can be found in the IOA PROCLIB library.
The DMD DD statement must point to the library containing the tables consisting of
demanded jobs, as head-of-tree, and the jobs triggered by the demanded jobs
produced in JOB7, STEP3.
SYSIN is the file containing the ADD COND, ORDER and CHANGE RESOURCE
commands. It can be coded as DDNAME=SYSIN, or it can be omitted from the
procedure.

Appendix
E Interfaces With Related Products

The CA-7 and CA-11 to CONTROL-M and CONTROL-M/Restart conversion tool
provides interface support for the following products:
Table 0-1 Support of Related Products
Product Conversion
CA-7/NCF CA-7/NCF is totally replaced by native CONTROL-M
support. For more information, see “Network
Communications Facility” on page 35.
CA-7/RPT An automatic conversion tool to convert CA-7/RPT to
CONTROL-D is available. Contact your BMC Software
representative for additional information.
CONTROL-D For details of the support the conversion tool provides in
interfacing existing CONTROL-D (Output Management
System) installations to CONTROL-M, see “CATEGORY” on
page 140, “&DCTGRY” on page 147, and “&CTDCOND” on
page 144.
CA-LIBRARIAN CONTROL-M supports JCL libraries in CA-LIBRARIAN or
and CA-PANVALET format. However, during the conversion
CA-PANVALET process, these libraries must be in partitioned data set format.
For more information, see “Step 2 - Copy CA-7 and CA-11 JCL
and CA-DRIVER Libraries and Initdeck” on page 73, and
“Step 13 - Customize CONTROL-M and Install User Exits” on
page 85.
With the CA-7 and/or CA-11 and CA-7/RPT conversion tools, a complete migration
from all CA-7 related products to INCONTROL products can be accomplished
automatically.
Appendix E Interfaces With Related Products 193

Appendix
F Problem Reporting
Please supply all the information requested below when reporting a problem related
to the conversion tool.
■ Version number of CONTROL-M (for example, 6.1.00) and the OS/390 or z/OS
operating system (for example OS/390 2.10)
■ Release number of CA-7 (for example, 3.1) from which you are converting
■ The latest PTF applied to the conversion tool
■ Copy of the DEFAULTS member
■ The full text of all Job Log messages, in addition to all error messages in the error
files (DAMSG, SYSPRINT, and so on)
■ All changes made to the Application List file (from JOB2)
■ Any source fixes or zaps applied to the conversion tool

Also, check if REFRESH LLA was done after changes were applied.
If an abend has occurred, send the symptom dump to BMC Software Customer
Support, and have a full dump (SYSUDUMP) available for use by BMC Software
Customer Support staff.
Ensure that whenever a change is made to the DEFAULTS member or a source fix is
applied, all the programs are reassembled and relinked.
Appendix F Problem Reporting 195

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Index
Symbols
# HLD JCL Override Statement 100 %%IF Control Statement
# JCL Override Statement 99 IF/DIF Commands 136
# JEND JCL Override Statement 117 %%INCLIB AutoEdit Command 98
#JI Block 117 CA-DRIVER Procedure 35
#JI Override Statement 117 CADRIVER Procedure 136
# JO Block 117 %%INCMEM AutoEdit Command
# JO JCL Override Statement 117 CA-DRIVER Procedure 35
# MNT JCL Override Statement 100 CADRIVER Procedure 136
# NOX 127 %%JOBID AutoEdit Variable 129, 157
# NOX JCL Override Statement 117, 132, 133 %%JOBNAME 157
#NTR JCL Override Statement 111, 117 %%JOBNAME AutoEdit Variable 129, 157
#RES JCL Override Statement 31, 101, 104, 128 %%JOBNAMX AutoEdit Variable
CLASS Field 104 CADRIVER EXEC Statement 134
PRTY Field 101 %%JULDAY AutoEdit Variable 117
Workload Balancing 32 %%LABEL AutoEdit Control Statement 117
#S, RO Value 102 %%LABEL Control Statement
# SCC JCL Override Statement 102, 156 IF/DIF Commands 136
#VER JCL Override Statement 133 STEP Command 135
# XEND JCL Override Statement 117 %%MEM# AutoEdit Variable
#XI JCL Override Statement 117 CADRIVER EXEC Statement 134
# XO JCL Override Statement 117 %%MEMNAME AutoEdit Variable
$ Mask Character 53 CADRIVER EXEC Statement 134
$ABEND Value CADRIVER Procedure 136
DO IFRERUN Parameter 123, 144 %%MINUS Function
$EXERR Value SET/DSET Commands 135
DO IFRERUN Parameter 123, 144 %%MONTH AutoEdit Variable 137, 138
%%$TAG AutoEdit System Variable 126 %%OJULDAY AutoEdit Variable 117
%%$TAG AutoEdit Variable 117 %%OUTDATE AutoEdit Variable 137, 138
%%BLANK Control Statement %%OUTDAY AutoEdit Variable 137, 138
SET/DSET Commands 135 %%OUTMON AutoEdit Variable 137, 138
%%ELSE AutoEdit Control Statement 117 %%OYEAR AutoEdit Variable 117
%%ELSE Control Statement %%PLUS Function
IF/DIF Commands 136 SET/DSET Commands 135
%%ENDIF AutoEdit Control Statement 117 %%SCHID AutoEdit Variable 117, 126
%%ENDIF Control Statement %%SET Control Statement
IF/DIF Commands 136 CADRIVER Procedure 134
%%FROM Variable SET/DSET Command 135
DONT SCHEDULE BEFORE/AFTER Fields 131 %%SYSID AutoEdit Variable 53, 86, 130
%%GOTO AutoEdit Control Statement 117 %%TIME AutoEdit Variable 117
%%GOTO Control Statement %%TO Variable
GOTO/DGOTO Commands 135 DONT SCHEDULE BEFORE/AFTER Fields 131
IF/DIF Commands 136 %%WDAY AutoEdit Variable 137, 138
STEP/DSTEP Commands 135 %%YEAR AutoEdit Variable 117
%%GROUP AutoEdit Variable 137, 139 &ALLMSG Conversion Parameter 143
%%IF AutoEdit Control Statement 117 &C_DATE CADRIVER Parameter 137, 138
&C_DAY CADRIVER Parameter 137, 138
Index 197
&C_JDATE CADRIVER Parameter 137, 138 *stepname 103

&C_MONTH CADRIVER Parameter 137, 138 /* JOBPARM SYSAFF Statement (JES2) 36
&C_SNAME CADRIVER Parameter 137, 139 //*CA11 Comment Statement
&C_TIME CADRIVER Parameter 137, 138 Conversion Details 122
&CALPREF Conversion Parameter 105, 143 //*MAIN SYSTEM Statements (JES3) 36
&CLASBAR Conversion Parameter 104, 143 /LOGON Command 74
&CTDCOND Conversion Parameter 140, 141, 144 /WLB Command 33
&CTR Conversion Parameter 52, 56, 86, 122, 123, 144, 146, Quantitative Resource
155 JOBCLASS_resourcename 120
&CTRCONF Conversion Parameter 124, 146
&DATE CADRIVER Parameter 137, 138
&DAY CADRIVER Parameter 137, 138
&DCTGRY Conversion Parameter 140, 147
A
&DELCOND Conversion Parameter 113, 147 Abend Code Recapture Prevention 26
&DEMAND Conversion Parameter 30, 64, 65, 83, 112, 121, ABORT Command
191 CADRIVER Procedure 137
&DEPJCND Conversion Parameter 112, 114 ACTION= 36
&DIRMAX Conversion Parameter 151 Active Jobs File 28
&FROMC Conversion Parameter 141, 151 Active Queue 28
&INIT Conversion Parameter 130, 152 ADD COND Command 30
&JDATE CADRIVER Parameter 137, 138 ADDMNCND KSL Script
&JESRPRT Conversion Parameter 130, 152 Maybe Jobs 131
&JOBCLAS Conversion Parameter 52, 80, 120, 152 ADDPROC Parameter 86
&JOBMXOC Conversion Parameter 152 Ad-Hoc Jobs 30
&L2VARS Conversion Parameter 138 Execution 27
&LINMAX Conversion Parameter 152 ALL Value
&MAXCALS Conversion Parameter 154 DAYS, MONTHS Parameters 107
&MAXDSN Conversion Parameter 154 ALT Subparameter
&MAXGENT CA 7 JCL Initialization Statement 127
CTMCA7V5-12S 154 Alternate Libraries 127
&MAXWAIT Conversion Parameter 141, 154 Analyze Commands 71
&MONTH CADRIVER Parameter 137, 138 AND/OR Parameter 107
&PNIBTSD Conversion Parameter 73, 121, 154 ANNUAL Field 109
&PRVNCT2 Conversion Parameter 145, 155 ANYSTEP Value
&REL Conversion Parameter 155 ON PGMST Parameter 156
&RELEASE Conversion Parameter 141, 155 APF Authorization 72
&RESFREE Conversion Parameter 116, 156 APPL
&SCCGLBL Conversion Parameter 103, 156 &USEROPT Parameter 159
&SCHDMOD Conversion Parameter 48, 106, 156 Field (CA7) 125
&SHOUTDL Conversion Parameter 129, 157 Parameter 160
&SHOUTDT Conversion Parameter 129, 157 Parameter (CONTROL-M) 99
&SHOUTE Conversion Parameter 129, 157 Value in &USEROPT Parameter 160
&SHOUTL Conversion Parameter 128, 129, 157 Application
&SHOUTT Conversion Parameter 128, 129, 157 Definition Overview 21
&SHOUTX Conversion Parameter 128, 157 Job Grouping 98
&STARTM Conversion Parameter 109, 158 List File 46, 51, 65, 76, 77, 79, 83, 156
&SUPMSG Conversion Parameter 158 Name 160
&SWLPROP Conversion Parameter 158 Names List 46
&TAPE1 Conversion Parameter 32, 104, 158 System Name 99
&TAPE2 Conversion Parameter 32, 104, 158 Tree Structure 24
&TIME CADRIVER Parameter 137, 138 APPLIST DD Statement 83
&TOCLASS Conversion Parameter 141, 159 Archive Parameters 145
&UNTIL Conversion Parameter 159 ASMLINK Member
&USERLEN Conversion Parameter 125, 159, 160 Modify and Run using Conversion Step 5 75
&USEROPT Conversion Parameter 125, 129, 157, 160 ASMMCL Procedure 75
* Mask Character 53 Associated Job Class
*-stepname 156 Maximum Number of Jobs Submitted 104

Authorization 71 CA11NR DD Statements 122

AUTO-ARCHIVE Parameter 26, 145 CA-7
AutoEdit JCL Library 151
Facility 99 JCL Library - Copy Using Conversion Step 2 73
Parameters 93 Production JCL Libraries 82
Statements 117 Queues 28
AutoEdit Facility Release Number 155
CA-DRIVER Procedure 35 System Exits 88
AUTOARCHIVE Parameter 123 User ID 74
AUXCAL CA-7 ID Field 117
DD Statement 80 CA-7/NCF
File 154 Product Interface 193
AUXILIARY CAL 107 CA-7/RPT
auxiliary calendars Product Interface 193
creation 87 CA7DATA DD Statement 121
replacement 87, 88 CA7ER789 106
Average Elapsed Runtime 128 CA7USERID Value
&USEROPT Conversion Parameter 160
CA7USRID Field 125
B CA-DRIVER Procedure
Conversion Overview 35
BARx Field Modifying and Running the JOB8 Member 84
CLBARR Macro 105 CA-DRIVER Variables 161
Basic Scheduling Parameters 106, 125 CALBLK Statement 42
Batch Terminal Calendars 156
Commands 154 Auxiliary Calendar Library 80, 107
DEMAND Command 120 Base Calendar Definitions 25
JCL Batch Terminal Step Operations 121 Base Calendar ID 105
JCL Batch Terminal Steps 56 Base Calendar Report File 42, 44, 74, 78
Mechanism 42 Base Calendars 21, 71, 108
Parameter Control Statement 82 CA-7 Calendars 105
Parameter File 56, 60 Calendar Library File 46, 76, 77
SLIA-00 End Record 76 CALENDAR Macro (CA-7) 21, 49
Steps 30, 34, 112, 154 Calendar Name Change List File 55
SYSIN Calendar Name List File 46, 52, 76, 77, 80, 107, 143
Non-Instream 154 Calendar Name Prefix 143
BD Field 117 CONFCAL Calendar 105
BMC Software, contacting 2 CONTROL-M Calendar Definition 105
BT Field 117 CONTROL-M Calendar Library 78, 107
BTERM 57 CONTROL-M Calendar Overview 25
DSB Calendar Name Prefix 143
IOA Calendar Facility 22, 25
C Non-Standard Periodic Calendars 105, 108
Overview 25
CA 11 Periodic Base Calendar Control Statements 78
Non-Restartable Step Conversion Details 122 Periodic Base Calendar Name List File 49
CA-11 Periodic Calendar Name List File 78, 80
CA-1 Interface 27 Periodic Calendars 25, 105, 108
CA-DYNAM Interface 27 SCAL Base Calendar ID 105
CA-TLMS Interface 27 Standard Calendars 105
Copy JCL Library Using Conversion Step 2 73 CA-LIBRARIAN
JCL Steps 26 Libraries 73, 88
PARM Parameters 26 CA-Librarian
Production JCL Libraries 82 Product Interface 193
Rerun/Restart Processing 26 CA-PANVALET
System Exits 88 Libraries 73, 88
U11RMS Step 52, 56, 144 CA-Panvalet
Index 199
Product Interface 193 Conditions/Resources File 23, 31, 111, 113, 115, 120, 130,
CATEGORY Parameter 144 147
Conversion Details 140 Conditions/Resources Screen 23
CATLG Disposition 36 CONDCODE Field
CA7 Conversion Details 102
Job Name 98 CONFCAL
Job Triggers 98 Calendar 108
MEMBER Name 98 Connected Job 113, 114
Simulation 101 Connection
CADRIVER Procedure DSN 113
%%SUBSTR AutoEdit Function 137 Job 112, 113
ABORT/DABORT Commands 137 JOB REQUIREMENTS 114
DATA/DEND Commands 136 Control Resources 62
DPROC Parameter 133 Overview 25
EXEC Statement 134 CONTROL-D 144, 147
GOTO/DGOTO Commands 135 Product Interface 193
IF/DIF Commands 136 Report Decollating Mission 140
NEST/DNEST Commands 136 CONTROL-M/Restart
SET/DSET Commands 135 &CTR Conversion Parameter 144
STEP/DSTEP Commands 135 CA-11 Conversion 122
Variable Parameters 137 Confirmation 146
CAEARL CURRENT SCHDMOD Report 106 EXCLUDE DSN Statements 146
CHANGE RESOURCE Statement 32 Implementation 56
checking conversion results 88 Installation Parameters 145
CLASS Job Scheduling Parameters 34
Conversion Details 104 Parameter 123
Field 143 PREVENT NCT2 Processing 145
Field (JCL) 120 Rerun/Restart Processing Overview 26
Parameter (JCL) 152 Simulation Facility 27
Class Barriers 31, 104 Simulation Run 124
Resources 143 Statements 144
Support 143 Step 26
Workload Balancing 32 CONTROL-Parameter
CLASS CA-7 parameter 104 EXCLUSIVE_jobname 113
CLBARR Macro 105 Conventions Used in This Guide 13
CLOCKTIME Field 128 Conversion
CMEM CA-DRIVER 66
Conversion 129 Check Results Using Conversion Step 15 88
Events 154 Component Summary 93
File 87 Components 91
Overview 36 Conceptual Overview 19
Rule Creation by Conversion Job3 50 Detail Summary 93
Rule Definition 22, 80 Details 91
Rule Table 80, 87 Job1 42, 44
Codes (Messages) Job2 46
Descriptions 163 Job3 50
CODES Parameter 102 Job4 56
Command Type 57 Job5 61
Concatenating LJOB Reports 76 Job6 63
Concurrent Job Runs 104, 113 Job7 64
COND= JCL Statement 102 LOAD Library 76, 77
Condition Code Checking LOAD Library Name 75, 79, 81, 82, 83
Job Level 102 Parameters 93, 143
Step Level 102 Pre-Conversion Planning 71
Conditional Job Dependency Process Flow 39
DEPJOB=? Field 131 Source Library 140
SRC Source Library Name 75

Step 1 - Create Conversion SOURCE and LOAD &SHOUTX 128, 157

Libraries 72 &STARTM 109, 158
Step 10 - Modify and Run the JOB5 Member 82 &SUPMSG 158
Step 11 - Modify and Run the JOB7 Member 83 &SWLPROP 158
Step 13 - Customize CONTROL-M and Install User &TAPE1 32, 104, 158
Exits 85 &TAPE2 32, 104, 158
Step 14 - Final Adjustments 87 &TOCLASS 141, 159
Step 15 - Check Conversion Results 88 &UNTIL 159
Step 16 - Customize New Day Procedure 89 &USERLEN 125, 159
Step 2 - Copy CA 7 and CA 11 JCL Libraries, Initdeck &USEROPT 125, 129, 160
73 conversion results
Step 3 - Modify and Run the JOB0 Member 74 checking 88
Step 5 - Modify and Run the ASMLINK Member 75 Conversion source library 143
Step 7 - Modify and Run the JOB2 Member 77 CPU Usage 31
Step 8 - Modify and Run the JOB3 Member 79 CPUID Translation Table 53, 80, 86, 129
Step 9 - Modify and Run the JOB4 Member 81 CREATED BY
Steps - General 69 **NONE* 114
Unique Parameters 140 nnn JOBS 114
Utilities 191 Critical Path 102
Conversion Parameters Critical Resources 25
&ALLMSG 143 Cross Reference File 79, 82
&CALPREF 105, 143 CTM.CA7.APPLS File Name 47
&CLASBAR 104, 143 CTM.CA7.BASECAL File Name 43
&CTDCOND 140, 141, 144 CTM.CA7.REPORT File Name 43, 45
&CTR 52, 56, 86, 122, 123, 144, 146 CTM.CA7.RESOURCE File Name 43
&CTRCONF 124, 146 CTM.CA7.SCHED File Name 43
&DCTGRY 140, 147 CTM.CAS.PARMLIB
&DELCOND 113, 147 JOB5 Output 66
&DEMAND 30, 64, 65, 83, 112, 121, 148, 191 CTM.CAS.PROCLIB
&DEPJCND 112, 114, 150 JOB5 Output 66
&DIRMAX 151 CTM.CA7.XREF Library Name 54
&FROMC 141, 151 CTM.V500.Calendar File Name 49
&HISTORY 151 CTM.V500.CALNAMES File Name 49
&INCLIB 151 CTM.V500.CMEM File Name 54
&INIT 130, 152 CTM.V500.DACALS File Name 49
&JESPRT 152 CTM.V500.Daily Name 54
&JESRPRT 130 CTM.V500.DOCUMENT Library Name 54
&JOBCLAS 52, 80, 120, 152 CTM.V500.INCLIB Library Name 54, 55, 56
&JOBMXOC 152 CTM.V500.JCLIN File Name 54
&L2VARS 138, 153 CTM.V500.NEWSCHED Library Name 65
&LINMAX 152 CTM.V500.SCHEDULE Library Name 54
&MAXCALS 154 CTMCA702 Program 50
&MAXDSN 154 CTMCA706 Program 50
&MAXGENT 154 CTMCA706-01E Message 156
&MAXWAIT 141, 154 CTMCA707 Program 56
&PNIBTSD 73, 121, 154 CTMCA707-00R Message 82
&PRVNCT2 155 CTMCA709 Program 56
&REL 155 CTMCA711 Program 46
&RELEASE 141, 155 CTMCA7RL
&RESFREE 116, 156 Procedure 124
&SCCGLBL 103, 156 Utility 32
&SCHDMOD 48, 106, 156 CTMCA7V5 Program 64
&SHOUTDL 129 CTMCAS51 Program
&SHOUTDT 129 CA-DRIVER Conversion 66, 71
&SHOUTE 129 CTMIMAC1 REXX Procedure
&SHOUTL 128, 129, 157 JCL Repository Functionality 34
&SHOUTT 128, 129, 157 CTMJOB Utility 112
Index 201
CTMJTXRF Utility 54 DAJOBCL DD Statement 80

CTMLOAD DD Statement 76, 77, 79, 81, 82, 83 DAOUT1 DD Statement 76, 78
JOB8 84 DAPARM DD Statement
CTMMEM Function 177 JOB8 84
CTMRFLW Utility 88 DAPROC DD Statement
CTMROGR Utility 88 JOB8 84
CTMRPLN Utility 88 DAPROCIN DD Statement
CTMSRTJB Utility 27 JOB5 85
CTMSV5 DD Statement 83, 84 DAREPIN DD Statement 82
CTMTBUPD Utility DAREPORT DD Statement 76, 77, 79
Customization 37 DAREPRT2 DD Statement 78
CTMTBUPD utility 87 DASCHD DD Statement 64, 80
CTMUTIL Procedure 112 DASCHD2 DD Statement 80
CTMX001 Exit DASCHDxx DD Statement 82
Date Range for Job Execution 140 DASYSN DD Statement 79
CTMX002 Exit 85 DATA Command
CTMX002Q Member CADRIVER Procedure 136
IOA SAMPEXIT Library 85 Data Set
CTMX004 Exit 33 Archiving 145
CTMX015O Exit 34 Deletion 145
CTMXRF Utility 87, 88 Event 36, 50
CTMXRF utility 87 Scratched 145
CTR Conversion Parameter 123 Triggering 36, 129, 154
CTRNORST DD Statements 122 Uncataloged 145
CTRPARM Member Database
IOA PARM Library 86 Verification 71
CTRX001 Exit 27, 146 DATALIB Library 136
CURRENT Status 106 Date Format 138
Customer Support 195 Date Range for Job Execution
customer support 3 Exit 1 140
Customization DATE= 36
Overview 37 DATES Parameter 109
CV= Subparameter 117 DATETYP Parameter
%%FROM/%%TO Variables 132
DAXREF DD Statement 79, 82
D DAYMONTH Member
AutoEdit Variables 138
DABASCAL DD Statement 78 DAYS
DABORT Command Parameter 109
CADRIVER Procedure 137 DCAL
DABTERM DD Statement 82 Parameter 46, 110
DACAL DD Statement 78, 107 DE Command Type 57
DACALNM DD Statement 78, 80 Default Job Class 152
DACALS DD Statement 78, 80 DEFAULTS Member 75, 104
DACMEM DD Statement 80 Conversion Source Library 140
DACPUID DD Statement 80, 129 Conversion source Library 143
DACTRCTL DD Statement 26 Modify Using Step 4 75
DADAILY DD Statement 79, 89 DELETE Disposition 36
DADATA DD Statement DELOVRER Parameter 34
JOB5 84 DEMAND Command 31, 112, 125, 154
DADOC DD Statement 79 CLASS/#RES 104
DAILY Scheduling 108 Conversion Details 120
DAINCLIB DD Statement 79, 98 HOLD/# HLD 100
DAINIT DD Statement 79 Overview 30
DAJCLIN DD Statement 80, 81 PRTY/# RES 101
JOB8 85 Workload Balancing 32
DAJOB DD Statement 89 DEMAND Field 152

Demanded Job Execution 27, 148

DEND Command E
CADRIVER Procedure 136 ED Field 117
DEPJOB Editing JCL 34
Value 30 ELAPTM Value
DEPJOB Field # RES Override Statement 128
Conversion Details 112, 113 ENDEDOK Status 102
Job Connection 114 Error Messages
DEPJOB=? Field Descriptions 163
Conditional Job Dependency 131 ET Field 117
DGOTO Command EXCLUDE DSN Statements 146
CADRIVER Procedure 135 Exclusive Resource Control 116
STEP Command 135 EXEC Field
DIF Command Conversion Details 132, 133
CADRIVER Procedure 136 EXEC Statement
STEP/DSTEP Commands 135 CA-DRIVER Procedure 35
DISP= 36 CADRIVER Procedure 134
NEW 145 EXEC=N 127
DNEST Command CA7 Job Definition 101
CADRIVER Procedure 136 JOB Screen 99
DO IFRERUN Parameter 26, 123, 144 Execution Time 109
DO NOTOK Parameter 102 Exit 1
DO OK Parameter 102 Date Range for Job Execution 140
DO RERUN Parameter 26 Exits 71
DO SYSOUT Parameter 141 Exit 1 146
Conversion Details 141 Exit 2 53, 85, 86, 130
Documentation Library (CONTROL-M) 79, 115 exits
Documentation Requirements 24 Exit 2 98
DONT SCHEDULE BEFORE/AFTER Fields Extended NJE Job Tracking 35
%%FROM/%%TO Variables 131
DOTM Field
Conversion Details 109
DPROC Parameter
F
CADRIVER Procedure 133 Failed Job SHOUT Destination 157
DSB Calendar Name Prefix 143 Final Adjustments
DSET Command Conversion Step 14 87
CADRIVER Procedure 135 FORCE Option 30
DSN 36 Forecast Job Flow Structures 28
Connection Dependency Condition Names 150 Format Processing
Connection for MAINT Jobs 100 U11RMS Step 123
Conversion Details 113 FROM Parameter 108, 128
CREATED BY **NONE* 114 FSTRUC Transaction 28
CREATED BY nnn JOBS 114
JCL Initialization Statement 99, 127
PERM 114
PERM FOR JOB 114
G
DSTEP Command General Daily 54
CADRIVER Procedure 135 Global Cross Reference File 54, 61
DTRG Screen 21 GOTO Command
Due Out CADRIVER Procedure 135
DUE OUT Parameter 109 STEP/DSTEP Commands 135
Shout Message 157 Group
Time 109, 128 Entity 23, 125
DUMMY Scheduling Table 23, 98, 125
Value in OVERLIB Parameter 101, 127 Scheduling Table Creation by Conversion Job7 64
Dynamically allocated CA-7/CA-11 JCL Libraries 52 Scheduling Table Library 83
Grouping Application Jobs 98
Index 203
H Step 148
Utility 32, 87
Head-Of-Tree Job 22 IOAENV
Definition 27 Library Name 76
Head-of-Tree Job 24, 158 IOALOAD DD Statement
Held Sysout Classes 151 JOB8 84
High-Water 32
HLDCLASS Parameter 141
HOLD Field
J
Japanese
Date Format 138
I JCL
Automation 35
ID= Subparameter 126 CA-DRIVER Procedure 35
IEF125I Message 37 Considerations Overview 33
IEF403I Message 37 CONTROL-M JCL Steps 56, 124
IF Command Conversion 154
CADRIVER Procedure 136 Conversion of JCL Libraries 66
STEP/DSTEP Commands 135 GROUP= JOB Statement 160
IF Logic Capability 117 INCLUDE Member 98
IN Conditions 23, 37, 98, 111, 120, 147, 148 Include Members 79
creating job data set 114 Initialization Statements 99, 127
depjobname_OK 112 JCL Conversion Report 60
jobname_depjobname_schedid 112 JCL Library DSN List 56, 80, 81
INCLIB Library 85, 98 Job Class 52, 80
Include Library 54 Job Class Conversion Details 120
INCLUDE Members 85 Job Class Parameter 152
Independent Tree 27 Job Class Translation Table 52, 120
Initdeck JOB Statement 160
Copy Using Conversion Step 2 73 Job Stream 53
File (CA-7) 154 Libraries (CONTROL-M) 60
File (CA7) 99 Library 127
Initialization File (CA-7) 51 Library Copy 73
Library Name (CA-7) 79 Library Name 99
Member Name (CA-7) 79 Max Lines in Member 152
Initialization File (CA-7) 21 Member Conversion 56, 81
Initiator Control 152 Member Name 98
Initiators 31, 130 NOTIFY= JOB Statement 160
INITR Macro Override Statement # JI,ID=... 126
Conversion Details 130 Override Statements 33, 50
Input Data Set PARM= Field 44, 50
Creation 113 USER= JOB Statement 160
Name 113 JCL Repository Facility 34
INSERT-RMS JCLGRP
Field 155 &USEROPT Conversion Parameter 160
INSERTRMS Field 125
Conversion Details 122 JCLID Field
Interfacing Other Products 193 Conversion Details 99
Intermediate Scheduling Table JCLUGRP
Library 80 &USEROPT Conversion Parameter 159
IOA LOAD JCLUSER
IOALOAD DD Statement 76, 79, 81, 82, 83 &USEROPT Conversion Parameter 159, 160
IOALOAD Parameter 75 Field 125
Library Name 75, 76, 79, 81, 82, 83 JCLOVRD Field
IOACND Conversion Details 99
Procedure 120 JDEP Connection 24

JES Modify and Run Using Conversion Step 7 77

Definitions 35 Job2
JCL Statements 34 Conversion Process 46
JES ROUTE PRINT Statement Conversion Details 130 JOB3 99, 107, 129, 143
Job Number 129 Modify and Run Using Conversion Step 8 79
ROUTE PRINT JCL Statement 152 Job3
Statement 130 Conversion Process 50
JES2 and JES3 Statements 86 JOB4 120, 154
JES2 JOBPARM Statement 53 Modify and Run Using Conversion Step 9 81
JES3 MAIN Statement 53 Job4
Job Conversion Process 56
Completion 111 JOB5
Connection 98, 113, 114 CA-DRIVER Conversion 66
Connection Conditions 147 Modify and Run Using Conversion Step 10 82
Connection Dependency Condition Names 150 Job5
Connection Overview 24 Conversion Process 61
Definition Overview 22 Job6
Dependency Overview 24 Conversion Process 63
Documentation 115 JOB7
Documentation Overview 24 Modify and Run Using Conversion Step 11 83
Execution Flow 23 Job7
Grouping 120 Conversion Process 64
JOB Field 98, 112, 125 JOB8
JOB Parameter Value 57 Modifying and running 84
JOB Value / &USEROPT Conversion Parameter 159, JOBCONN Screen 21, 24
160 JOBNAME= 36
Name 160 JOBPARM Statement 53
Occurrences 111, 152 JTRG Screen 21, 23
Output Handling 141
Owner 160
Priority 31
Scheduling Overview 22
K
Start Times 31 KEEP Disposition 36
Statement 80
Submission
Time Limit 108
Tracking 28
L
Triggering 22, 36 LDTM Field
Overview 23 Conversion Details 109
Triggering Conversion Details 111 Lead Time 109
Job Class LEADTM Field 113, 147
Conversion 152 LIST=
Conversion Details 120 ALL 42
Structure 31 NODD 42
Translation Table 80 LJOB
Job Scheduling Definition 22, 26 Command 42
Parameters 34, 93 LJOB,JOB=*,LIST=ALL Command 42
Screen 22, 24, 25, 115 Report File 27, 42, 44, 50, 74, 76, 77, 79, 128
JOB Screen 22, 98, 99 LJOB Reports, Concatenating 76
Application Definition Overview 21 LKED Procedure 75
job submission exit (Exit 2) 98 LLA REFRESH 75
JOB=* 42 LOADLIB Parameter 75
JOB1 25, 74 Logical Device Type 104
Modify and Run Using Conversion Step 6 76 LOGON ID 71
Job1 LQ Transaction 28
Conversion Process 42, 44 LSCHD
JOB2 106, 156 Command 42
Index 205
LSCHD,JOB=*,LIST=BYSID Command 42 MEMNAME parameter 98

Report File 71, 74, 78, 107 Message
LSCHED Report File 42, 44 Destination 129
LWLB Command 33 File 47, 62
Shouting 127
Suppression 129
M Messages and Codes
Descriptions 163
M3 Step 75 Mission Category 140
M4 Step 75 Modification To Resolved Schedule Dates Screen 21, 106
M5 Step 75 MONTHLY Field 109
M6 Step 75 MONTHLY RDAY Field 110
Machine Date 29 MONTHS Parameter 107
Macro MSGCLASS
CALENDAR 21 Parameter 141
User Option Table 21 Sysouts 159
Workload Balancing 21 MSGLEVEL=(1,1) Parameter 37
MAIN Statement 53 MXTAL Parameter
MAINID Workload Balancing TAPE1 / TAPE2 Macros 104
CPUID Translation Table 53, 86
Field 36, 80
MAINT
N
Conversion Details 100 NAME Parameter
Job 100, 114 TAPE1 Macro 158
Manual TAPE2 Macro 158
Confirmation 146 NCT2RC Parameter 86
Verification 100 NDAY Value 109
Manual Conditions 24 Negative Job Dependence 113
Screen 24 NEST Command
Manual IN Condition CADRIVER Procedure 136
HELD_jobname 101 Network
JCL_OVERIDE_jobname 99 Communications Facility Overview 35
jobname_NW 114 Prerequisites 114
RESTART_jobname 101 New Day Processing
SUSPEND_jobname 124 Overview 28
VERIFY_JCL_jobname 100 Schedule Scan and 28
Mask Character New Day Time 85
$ 53 New Output Class 159
* 53 NFILVS99 Parameter 86
MAXDAYS Parameter 26 NJE
Maximum Number Jobs 35
Calendars in AUXCAL File 154 Support 86
Dataset Triggers For CMEM Events 154 NOGROUP Value
Job Occurrences In Scheduling Table 152 OWNER ID 160
Lines in JCL Member 152 Non-Instream SYSIN 154
Members in CA-7 JCL Library 151 NONOTIFY Value
MAXRUNS Parameter 26 OWNER ID 160
MAXWAIT Parameter Non-Restartable Steps (CA 11)
Conversion Details 141 Conversion Details 122
Maybe Jobs Non-Restarted Jobs 145
DEPJOB=? Field 131 Non-Standard Periodic Calendars 105, 108
MEMBER Field NORECAPTABEND Option 26
Conversion Details 98 NOT CATLGD 2 Situations 145
MEMLIB Parameter 99, 101 NOTIFY
MEMNAME Parameter 22, 98, 100, 101, 111, 112, 114, 115, Field 125
141 Value in &USEROPT Conversion Parameter 159, 160

NOUSER Value PJ Command Type 57

OWNER ID 160 POST Command 125, 154
NW 30 Conversion Details 120
NWK Field Overview 30
Conversion Details 114 PRE Online Commands 26
NXT CYC SETOFF Command Pre-Conversion Planning
Conversion Details 124 Conversion Steps 71
Predecessor Job 112
Prerequisite Conditions 23, 24, 111, 120
O Overview 23
Prevent Automatic Abend Code Recapture 26
OA Field 117 PREVENT-NCT2 Parameter 26, 52, 145, 155
OB Field 117 PREVENTNCT2 Parameter 123
ON DATASET Rules 54 Primary JCL Library 127
ON PGMST Parameter 102, 123, 156 PRINT Command 42
ON STEP/CODES Parameters 102 JOB1 105
On-Line Viewing Archive Parameters 145 Priority
OPER Value PRIORITY Parameter 31, 102
Shout Destination 157 Problem Reporting 183, 195
OPER2 Value Procedure Library
Shout Destination 157 Conversion to CTM Format 66
OPTION=SCHDYONLY 106, 110 PROCLIB Library
OPTION=SHCDYONLY 106 CADRIVER Procedure 133
Original MSGCLASS 159 PROCRC Parameter 86
OUT Condition 23, 98, 111, 144 PROCRMS Field
creating job data set 114 RESTART Statement 123
depjobname_OK 112 Product Interfaces 193
jobname_depjobname_schedid 112 product support 3
jobnameusertext 140 Production
scheduletable_jobname_OK 111 Control - Overview 28
Output Class 159 Control Parameters 28
OVERLIB Library Data Sets 100
Deleting Members from 34 Management - Overview 28
Editing JCL 34 Parameters 22
OVERLIB Parameter 127 Processing 123
DUMMY value 101 PROMPTS Field 128
OWNER PROSE
Conversion Details 125 Data Conversion 115
Parameter 125, 159, 160 Screen 21, 24
Value in &USEROPT Conversion Parameter 159, 160 Prose
OWNER ID 160 Information Overview 24
PRTY Field
P Pseudo
Production Processing 155
PARM PSEUDO Option 27
Field 77, 80, 83, 122 PSEUDO=YES 155
Parameter 155 PU Command Type 57
Value 123
Value F 123
Value P 123, 145
Value R,PSEUDO=YES 124 Q
PARMLIB Library Quantitative Resource 31, 52, 80, 104, 120, 124, 152
CADRIVER EXEC Statement 134 Resource Name 152, 158
PDS Libraries 73
PERM DSN 114
PERM FOR JOB 114
Index 207
R SCALyyxx 47
SCHD Screen 21, 22, 23
Ready Queue 28 SCHDMOD CURRENT 106
REGION=0K 44, 50, 77, 80 Indicator 25, 156
Relational Operator 102 Processing 46
Release Sysouts 155 SCHDMOD Screen 106
Report Decollating Mission 140 SCHDYONLY 49, 106, 110
Category 147 Periodic Calendar Name File 78, 80
Request Queue 28, 29, 100, 109 Schedule ID 23, 47, 106
Requeue Schedule Scan
Held Sysout Classes 151 New Day Processing and 28
MSGCLASS Sysouts 159 Overview 28
Sysout 141 SCHEDULE TAG Field 23
Reroute MSGCLASS Sysouts 159 SCHEDULE TAG Parameter 117, 125
Rerun scheduleIDheadoftreejobname 117, 125
Processing 26, 123 Scheduled Tree 27
RESANL Analyze Command 71 Scheduling
RESCHNG Command 31 Conversion Details 109
Conversion Details 124 Date 24
Workload Balancing 32 Definition 106
Resource Indicator 124
Availability 28 Overview 22
CLASS 104 Scheduling Table 24, 25, 79, 98, 111, 125
Management 25 Creation by Conversion Job3 50
Management Components - Conversion 61, 82 Creation Overview 27
Management Facility 82, 115 Customize New Day Procedure Using Conversion
Management Overview 25 Step 16 89
Quantity 125 Libraries 61, 82, 83
RESOURCE Parameter 31, 53, 104 List File 79
Sharing 104, 113, 115 Name 46
Restart Scheduling Tables
Confirmation 146 Update Using Conversion Job6 63
Parameters 56 SCHID
Processing 26, 123 =000 Value 23
Requirement 101 DEMAND Command Value 112
RETAIN (SMS) Disposition 36 Field 23, 125
RO Field SCHPREVD parameter 85
Conversion Details 102 SCRATCH (SMS) Disposition 36
ROLL Field 105 Security Access 71
ROUTE PRINT Statement 34 SET Command
RQMT Analyze Command 71 CADRIVER Procedure 135
RSRC Screen 21, 25 SET VAR Parameter 53, 130
RUN HANDLER 123 SET=%%SYSID 86
Setup Time 109
Shared Option 113
S Shared Resource Control 116
SHIFT Parameter 107, 108
SAC Parameter 85 SHOUT
Sample Exit 2 53 Conversion Details 127
SASSBTRM Procedure Name 74 Destination For Failed Jobs 157
SASSJCLU Utility (CA-7) 71 Facility 157
SASSTRLR Procedure Name 60 WHEN EXECTIME 157
Satisfaction Lead Time 113 WHEN LATE 157
SBTM Field WHEN LATESUB 157, 158
Conversion Details 108 WHEN NOTOK 157
SCAL 156 Simulate Job Execution 101
Conversion Details 105 Simulation and Forecasting Facility 148

SLIA-00 End Record 76

SMF Feedback Data 35 T
SMS-Managed Volumes 77, 78, 81, 84 Tape Drive 104
SORTIN DD Statement 78 Usage 31
SPAN Field 106 Tape Management System 27
SRCLIB Parameter 75 TAPE1
Standard Calendars 105 Macro 104, 158
Start Time 109 Resource 158
STARTM Field 128 TAPE2
Status Screen 28 Macro 104, 158
Step 1 72 Resource 158
Step 10 82 technical support 3
Step 11 83 Threshold Priorities 31
Step 13 85 Time Limit
Step 14 87 Job Submission 108
Step 15 88 Time Until Indicator 159
Step 16 89 TIME UNTIL Parameter 159
Step 2 73 TOCLASS 151
Step 3 74 TOTAV Parameter
Step 4 75 INITR Macro 130
Step 5 75 TP1 Value
Step 6 76 # RES Override Statement 124
Step 7 77 TP2 Value
Step 8 79 # RES Override Statement 124
Step 9 81 Track Production Jobs 28
STEP Command Trailer Step 32
CADRIVER Procedure 135 TRGID Field 23
Stepname Field TRIG Analyze Command 71
# SCC JCL Override Statement 156 Triggering 22
Submission Exit (Exit 2) 85, 130 TSO-uid Value
Successor Jobs 158 Shout Destination 157
support, customer 3 TYPE=RES Parameter
Suspend Job Execution 113 DEMAND Command 101
Sx37 Abend 83 TYPE1
SYMETRIC Parameter 106 Fields 125
SYSDATA Files 145 TYPE2
SYSDB Fields 125
Files 145 TYPRUN Value 123
Parameter 26, 123
SYSIN
DD Statement 78, 121, 154
Non-Instream 154
U
SYSINLIB DD Statement 77, 80, 81 U11RMS Step 26, 34, 122, 144, 155
Sysout Conversion Details 123
Handling 141 U11UCSEX Exit 146
Release 155 U11VOLCX Macro (CA-11) 146
SYSOUT Parameter 130, 152 U7SVC Procedure Name 60
System UCC11NR DD Statements 122
Affinity 80, 130 UCC7DATA DD Statement 121
ID 53, 130 UCC7DBVR Program 71
Spool 141 Uncalalog/Scratch Exit 146
SYSTEM Field 99 UNCATLG Disposition 36
SYSUSER Value Unique CONTROL-M Parameters
Shout Destination 157 Conversion Details 140
User Exit 2 (CONTROL-M) 85
User Exits
Install Using Conversion Step 13 85
Index 209
User ID 125
User Option Table Macro 21
USER REQUIREMENTS Field
USERID Parameter 125
USEROPT Conversion Parameter 159
UserDefined Prerequisites 114
USR 30
Connection 24
USR ID Field 160
Utilities
CTMRFLW 88
CTMROGR 88
CTMRPLN 88
CTMXRF 87, 88
General 191
IOACND 87
V
Variable Parameters
CADRIVER Procedure 137
Variable-1 57
VERIFY Field
Volume INCLUDE/EXCLUDE List 146
VTAM Node Definitions 35
W
WDAYS
Parameter 109
WEEKLY Field 109
WLB Command 33
WORK DD Statement 77, 80, 81
Work Library 77, 80, 81
Work Unit Name 78
Workload Balancing
Macro INITR 130
Macro TAPE1 158
Macro TAPE2 158
Macros 21
MXTAL Parameter 104
Overview 31
Priority Scheduling Criteria 102
X
XEQ Statement 34
XQ Transaction 28
XREF Analyze Command 71

END USER LICENSE AGREEMENT
NOTICE
BY OPENING THE PACKAGE, INSTALLING, PRESSING “AGREE” OR “YES” OR USING THE PRODUCT, THE ENTITY OR INDIVIDUAL
ENTERING INTO THIS AGREEMENT AGREES TO BE BOUND BY THE FOLLOWING TERMS. IF YOU DO NOT AGREE WITH ANY OF THESE
TERMS, DO NOT INSTALL OR USE THE PRODUCT, PROMPTLY RETURN THE PRODUCT TO BMC OR YOUR BMC RESELLER, AND IF YOU
ACQUIRED THE LICENSE WITHIN 30 DAYS OF THE DATE OF YOUR ORDER CONTACT BMC OR YOUR BMC RESELLER FOR A REFUND OF
LICENSE FEES PAID. IF YOU REJECT THIS AGREEMENT, YOU WILL NOT ACQUIRE ANY LICENSE TO USE THE PRODUCT.
This Agreement (“Agreement”) is between the entity or individual entering into this Agreement (“You”) and BMC Software Distribution, Inc., a Delaware
corporation located at 2101 CityWest Blvd., Houston, Texas, 77042, USA or its affiliated local licensing entity (“BMC”). “You” includes you and your Affiliates.
“Affiliate” is defined as an entity which controls, is controlled by or shares common control with a party. IF MORE THAN ONE LICENSE AGREEMENT
COULD APPLY TO THE PRODUCT, THE FOLLOWING ORDER OF LICENSE AGREEMENT PRECEDENCE APPLIES: (1) WEB BASED LICENSE
AGREEMENT WITH BMC, (2) WRITTEN LICENSE AGREEMENT WITH BMC, (3) SHRINK-WRAP LICENSE AGREEMENT WITH BMC PROVIDED WITH
THE PRODUCT, AND (4) THIS ELECTRONIC LICENSE AGREEMENT WITH BMC. In addition to the restrictions imposed under this Agreement, any other
usage restrictions contained in the Product installation instructions or release notes shall apply to Your use of the Product.
PRODUCT AND CAPACITY. “Software” means the object code version of the computer programs provided, via delivery or electronic transmission, to You.
Software includes computer files, enhancements, maintenance modifications, upgrades, updates, bug fixes, and error corrections.
“Documentation” means all written or graphical material provided by BMC in any medium, including any technical specifications, relating to the
functionality or operation of the Software.
“Product” means the Software and Documentation.
“License Capacity” means the licensed capacity for the Software with the pricing and other license defining terms, including capacity restrictions, such as tier
limit, total allowed users, gigabyte limit, quantity of Software, and/or other capacity limitations regarding the Software. For licenses based on the power of a
computer, You agree to use BMC's current computer classification scheme, which is available at http://www.bmc.com or can be provided to You upon
request.
ACCEPTANCE. The Product is deemed accepted by You, on the date that You received the Product from BMC.
LICENSE. Subject to the terms of this Agreement, as well as Your payment of applicable fees, BMC grants You a non-exclusive, non-transferable, perpetual
(unless a term license is provided on an order) license for each copy of the Software, up to the License Capacity, to do the following:
A. install the Software on Your owned or leased hardware located at a facility owned or controlled by You in the country where You acquired the license;
B. operate the Software solely for processing Your own data in Your business operations; and
C. make one copy of the Software for backup and archival purposes only (collectively a “License”).
If the Software is designed by BMC to permit you to modify such Software, then you agree to only use such modifications or new software programs for Your
internal purposes or otherwise consistent with the License. BMC grants You a license to use the Documentation solely for Your internal use in Your operations.
LICENSE UPGRADES. You may expand the scope of the License Capacity only pursuant to a separate agreement with BMC for such expanded usage and
Your payment of applicable fees. There is no additional warranty period or free support period for license upgrades.
RESTRICTIONS: You agree to NOT:
A. disassemble, reverse engineer, decompile or otherwise attempt to derive any Software from executable code;
B. distribute or provide the Software to any third party (including without limitation, use in a service bureau, outsourcing environment, or processing the
data of third parties, or for rental, lease, or sublicense); or
C. provide a third party with the results of any functional evaluation or benchmarking or performance tests, without BMC's prior written approval, unless
prohibited by local law.
TRIAL LICENSE. If, as part of the ordering process, the Product is provided on a trial basis, then these terms apply: (i) this license consists solely of a non-
exclusive, non-transferable evaluation license to operate the Software for the period of time specified from BMC or, if not specified, a 30 day time period
(“Trial Period”) only for evaluating whether You desire to acquire a capacity-based license to the Product for a fee; and (ii) Your use of the Product is on an AS
IS basis without any warranty, and BMC, ITS AFFILIATES AND RESELLERS, AND LICENSORS DISCLAIM ANY AND ALL WARRANTIES
(INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NON-INFRINGEMENT) AND HAVE NO LIABILITY WHATSOEVER RESULTING FROM THE USE OF THIS PRODUCT UNDER THIS TRIAL
LICENSE (“Trial License”). BMC may terminate for its convenience a Trial License upon notice to You. When the Trial Period ends, Your right to use this
Product automatically expires. If You want to continue Your use of the Product beyond the Trial Period, contact BMC to acquire a capacity-based license to
the Product for a fee.
TERMINATION. This Agreement shall immediately terminate if You breach any of its terms. Upon termination, for any reason, You must uninstall the
Software, and either certify the destruction of the Product or return it to BMC.
OWNERSHIP OF THE PRODUCT. BMC or its Affiliates or licensors retain all right, title and interest to and in the BMC Product and all intellectual property,
informational, industrial property and proprietary rights therein. BMC neither grants nor otherwise transfers any rights of ownership in the BMC Product to
You. Products are protected by applicable copyright, trade secret, and industrial and intellectual property laws. BMC reserves any rights not expressly granted
to You herein.
CONFIDENTIAL AND PROPRIETARY INFORMATION. The Products are and contain valuable confidential information of BMC (“Confidential
Information”). Confidential Information means non-public technical and non-technical information relating to the Products and Support, including, without
limitation, trade secret and proprietary information, and the structure and organization of the Software. You may not disclose the Confidential Information to
third parties. You agree to use all reasonable efforts to prevent the unauthorized use, copying, publication or dissemination of the Product.
WARRANTY. Except for a Trial License, BMC warrants that the Software will perform in substantial accordance with the Documentation for a period of one
year from the date of the order. This warranty shall not apply to any problems caused by software or hardware not supplied by BMC or to any misuse of the
Software.
EXCLUSIVE REMEDY. BMC’s entire liability, and Your exclusive remedy, for any defect in the Software during the warranty period or breach of the warranty
above shall be limited to the following: BMC shall use reasonable efforts to remedy defects covered by the warranty or replace the defective Software within a
reasonable period of time, or if BMC cannot remedy or replace such defective copy of the Software, then BMC shall refund the amount paid by You for the
License for that Software. BMC's obligations in this section are conditioned upon Your providing BMC prompt access to the affected Software and full
cooperation in resolving the claim.
DISCLAIMER. EXCEPT FOR THE EXPRESS WARRANTIES ABOVE, THE PRODUCT IS PROVIDED “AS IS.” BMC, ITS AFFILIATES AND
LICENSORS SPECIFICALLY DISCLAIM ALL OTHER WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. BMC DOES NOT WARRANT THAT THE
OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR FREE, OR THAT ALL DEFECTS CAN BE CORRECTED.
DISCLAIMER OF DAMAGES. IN NO EVENT IS BMC, ITS AFFILIATES OR LICENSORS LIABLE FOR ANY SPECIAL, INDIRECT, INCIDENTAL,
PUNITIVE OR CONSEQUENTIAL DAMAGES RELATING TO OR ARISING OUT OF THIS AGREEMENT, SUPPORT, AND/OR THE PRODUCT
(INCLUDING, WITHOUT LIMITATION, LOST PROFITS, LOST COMPUTER USAGE TIME, AND DAMAGE OR LOSS OF USE OF DATA), EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND IRRESPECTIVE OF ANY NEGLIGENCE OF BMC OR WHETHER SUCH DAMAGES
RESULT FROM A CLAIM ARISING UNDER TORT OR CONTRACT LAW.
LIMITS ON LIABILITY. BMC’S AGGREGATE LIABILITY FOR DAMAGES IS LIMITED TO THE AMOUNT PAID BY YOU FOR THE LICENSE TO
THE PRODUCT.
SUPPORT. If Your order includes support for the Software, then BMC agrees to provide support (24 hours a day/7 days a week) (“Support”). You will be
automatically re-enrolled in Support on an annual basis unless BMC receives notice of termination from You as provided below. There is a free support period
during the one year warranty period.
A. Support Terms. BMC agrees to make commercially reasonable efforts to provide the following Support: (i) For malfunctions of supported versions of the
Software, BMC provides bug fixes, patches or workarounds in order to cause that copy of the Software to operate in substantial conformity with its then-
current operating specifications; and (ii) BMC provides new releases or versions, so long as such new releases or versions are furnished by BMC to all
other enrolled Support customers without additional charge. BMC may refuse to provide Support for any versions or releases of the Software other than
the most recent version or release of such Software made available by BMC. Either party may terminate Your enrollment in Support upon providing
notice to the other at least 30 days prior to the next applicable Support anniversary date. If You re-enroll in Support, BMC may charge You a reinstatement
fee of 1.5 times what You would have paid if You were enrolled in Support during that time period.
B. Fees. The annual fee for Support is 20% of the Software’s list price less the applicable discount or a flat capacity based annual fee. BMC may change its
prices for the Software and/or Support upon at least 30 days notice prior to Your support anniversary date.
VERIFICATION. If requested by BMC, You agree to deliver to BMC periodic written reports, whether generated manually or electronically, detailing Your use
of the Software in accordance with this Agreement, including, without limitation, the License Capacity. BMC may, at its expense, perform an audit, at your
facilities, of Your use of the Software to confirm Your compliance with the Agreement. If an audit reveals that You have underpaid fees, You agree to pay such
underpaid fees. If the underpaid fees exceed 5% of the fees paid, then You agree to also pay BMC’s reasonable costs of conducting the audit.
EXPORT CONTROLS. You agree not to import, export, re-export, or transfer, directly or indirectly, any part of the Product or any underlying information or
technology except in full compliance with all United States, foreign and other applicable laws and regulations.
GOVERNING LAW. This Agreement is governed by the substantive laws in force, without regard to conflict of laws principles: (a) in the State of New York,
if you acquired the License in the United States, Puerto Rico, or any country in Central or South America; (b) in the Province of Ontario, if you acquired the
License in Canada (subsections (a) and (b) collectively referred to as the “Americas Region”); (c) in Singapore, if you acquired the License in Japan, South
Korea, Peoples Republic of China, Special Administrative Region of Hong Kong, Republic of China, Philippines, Indonesia, Malaysia, Singapore, India,
Australia, New Zealand, or Thailand (collectively, “Asia Pacific Region”); or (d) in the Netherlands, if you acquired the License in any other country not
described above. The United Nations Convention on Contracts for the International Sale of Goods is specifically disclaimed in its entirety.
ARBITRATION. ANY DISPUTE BETWEEN YOU AND BMC ARISING OUT OF THIS AGREEMENT OR THE BREACH OR ALLEGED BREACH,
SHALL BE DETERMINED BY BINDING ARBITRATION CONDUCTED IN ENGLISH. IF THE DISPUTE IS INITIATED IN THE AMERICAS
REGION, THE ARBITRATION SHALL BE HELD IN NEW YORK, U.S.A., UNDER THE CURRENT COMMERCIAL OR INTERNATIONAL, AS
APPLICABLE, RULES OF THE AMERICAN ARBITRATION ASSOCIATION. IF THE DISPUTE IS INITIATED IN A COUNTRY IN THE ASIA PACIFIC
REGION, THE ARBITRATION SHALL BE HELD IN SINGAPORE, SINGAPORE UNDER THE CURRENT UNCITRAL ARBITRATION RULES. IF THE
DISPUTE IS INITIATED IN A COUNTRY OUTSIDE OF THE AMERICAS REGION OR ASIA PACIFIC REGION, THE ARBITRATION SHALL BE
HELD IN AMSTERDAM, NETHERLANDS UNDER THE CURRENT UNCITRAL ARBITRATION RULES. THE COSTS OF THE ARBITRATION
SHALL BE BORNE EQUALLY PENDING THE ARBITRATOR’S AWARD. THE AWARD RENDERED SHALL BE FINAL AND BINDING UPON THE
PARTIES AND SHALL NOT BE SUBJECT TO APPEAL TO ANY COURT, AND MAY BE ENFORCED IN ANY COURT OF COMPETENT
JURISDICTION. NOTHING IN THIS AGREEMENT SHALL BE DEEMED AS PREVENTING EITHER PARTY FROM SEEKING INJUNCTIVE RELIEF
FROM ANY COURT HAVING JURISDICTION OVER THE PARTIES AND THE SUBJECT MATTER OF THE DISPUTE AS NECESSARY TO PROTECT
EITHER PARTY’S CONFIDENTIAL INFORMATION, OWNERSHIP, OR ANY OTHER PROPRIETARY RIGHTS. ALL ARBITRATION PROCEEDINGS
SHALL BE CONDUCTED IN CONFIDENCE, AND THE PARTY PREVAILING IN ARBITRATION SHALL BE ENTITLED TO RECOVER ITS
REASONABLE ATTORNEYS’ FEES AND NECESSARY COSTS INCURRED RELATED THERETO FROM THE OTHER PARTY.
U.S. GOVERNMENT RESTRICTED RIGHTS. The Software under this Agreement is “commercial computer software” as that term is described in 48 C.F.R.
252.227-7014(a)(1). If acquired by or on behalf of a civilian agency, the U.S. Government acquires this commercial computer software and/or commercial
computer software documentation subject to the terms of this Agreement as specified in 48 C.F.R. 12.212 (Computer Software) and 12.211 (Technical Data) of
the Federal Acquisition Regulations (“FAR”) and its successors. If acquired by or on behalf of any agency within the Department of Defense (“DOD”), the U.S.
Government acquires this commercial computer software and/or commercial computer software documentation subject to the terms of this Agreement as
specified in 48 C.F.R. 227.7202 of the DOD FAR Supplement and its successors.
MISCELLANEOUS TERMS. You agree to pay BMC all amounts owed no later than 30 days from the date of the applicable invoice, unless otherwise
provided on the order for the License to the Products. You will pay, or reimburse BMC, for taxes of any kind, including sales, use, duty, tariffs, customs,
withholding, property, value-added (VAT), and other similar federal, state or local taxes (other than taxes based on BMC’s net income) imposed in connection
with the Product and/or the Support. This Agreement constitutes the entire agreement between You and BMC and supersedes any prior or contemporaneous
negotiations or agreements, whether oral, written or displayed electronically, concerning the Product and related subject matter. No modification or waiver of
any provision hereof will be effective unless made in a writing signed by both BMC and You. You may not assign or transfer this Agreement or a License to a
third party without BMC’s prior written consent. Should any provision of this Agreement be invalid or unenforceable, the remainder of the provisions will
remain in effect. The parties have agreed that this Agreement and the documents related thereto be drawn up in the English language. Les parties exigent que
la présente convention ainsi que les documents qui s’y rattachent soient rédigés en anglais.
SW Click EULA 071102

Notes
*43990*
*43990*
*43990*
*43990*
*43990*

Ca 7

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Ca 7

Загружено:

Авторское право:

Доступные форматы

CONTROL-M®

for OS/390 and z/OS

January 28, 2004

Copyright 2004 BMC Software, Inc. All rights reserved.

Restricted Rights Legend

Support by Telephone or E-mail

Before Contacting BMC Software

Chapter 1 Conceptual Overview 19

Chapter 2 Conversion Process Flow 39

Chapter 3 Conversion Steps 69

6 CONTROL-M for OS/390 and z/OS CA-7 Conversion Guide

Chapter 4 Conversion Details 91

Appendix A Conversion Parameters 143

Appendix B Messages 163

Appendix C Planning The Conversion 183

Appendix D The CTMUTIL Conversion Utility 191

Appendix E Interfaces With Related Products 193

Appendix F Problem Reporting 195

8 CONTROL-M for OS/390 and z/OS CA-7 Conversion Guide

The guide is divided into the following chapters:

Chapter 1 – Conceptual Overview

Overview of basic concepts relating to conversion from CA-7 and CA-11 to

Chapter 2 – Conversion Process Flow

Description and details of the conversion process batch jobs

Chapter 3 – Conversion Steps

Step-by-step procedure for installing and operating the conversion tool

Chapter 4 – Conversion Details

Description of relevant CA-7 and CA-11 fields in relation to corresponding

Appendix A – Conversion Parameters

Various parameters for the conversion process

Messages and codes of the conversion process

Appendix C – Planning the Conversion

Advance planning before carrying out the conversion

About This Guide 11

Appendix D – Conversion Utility CTMUTIL

Appendix E – Interfaces With Related Products

List of various product interfaces supported by the conversion

Appendix F – Problem Reporting

Instructions on reporting problems to BMC Software Customer Support

About the Conversion Tool

The conversion tool performs the following functions:

■ builds CONTROL-M scheduling tables based on CA-7 database definitions and

■ builds all necessary CONTROL-M calendars

■ converts CA-DRIVER libraries to CONTROL-M format

■ enables customers to automatically set unique CONTROL-M options in the

12 CONTROL-M for OS/390 and z/OS CA-7 Conversion Guide

Conventions Used in This Guide

Standard Keyboard Keys

Many commands are preconfigured to specific keys or key combinations. This is

Instructions to enter commands may include

About This Guide 13

Command Lines and Option Fields

Names of Commands, Fields, Files, Functions, Jobs, Libraries, Members,

The names of commands, fields, functions, jobs, libraries, members, missions,

In syntax, the following additional conventions apply:

14 CONTROL-M for OS/390 and z/OS CA-7 Conversion Guide

All syntax, operating system terms, and literal examples are

■ code examples, such as

FOR TABLE owner.name USE option, . . . ;

■ control statements, such as

//PRDSYSIN DD * USERLOAD PRD(2) PRINT

■ system messages, both stand-alone, such as You are not logged on to