ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Using OPT=C in BTI (Batch Terminal Interface) job

book

Article ID: 226806

calendar_today

Updated On:

Products

CA 7 Workload Automation

Issue/Introduction

 

If you have BTI updates specifying OPT=C as shown in the example below:

JOBCONN,USR

UPD,USR,TESTJOB1,USR=CHECK_PAYROLL_FILE,OPT=C,SCHID=0

The option 'C' is not documented. What is this option used for and why is it not documented.

Environment

Release : 11.3, 12.0,12.1

Component : CA-7

Resolution

OPT=C is an old option and has been replace with OPT=A. If you have OPT=C coded in a BTI job, it will be treated as OPT=A (where option A is for add). This changed was put in CA 7 over 20 years ago and would have been documented at the time of the change.