These options specify the types of objects that can be processed
on behalf of the batch request utility if the object is not defined
in the CICS® region control file. To select an object type,
turn on its checkbox:
- Files
- TDQueues
- Transaction IDs
- Programs
You can also specify what action should be taken by the batch request
utility if CICS does not allow an undefined object to be processed:
- Ignore request. CICS BAC
will ignore the request for the object and continue with the next
request.
- Terminate with return code. CICS BAC will terminate the job step with the return code entered
in this text field.
- Abend with abend code. CICS BAC
will abend the job step and use the abend code entered in this text
field.
Finally, you can specify whether a record should be created in
the control file for an undefined object that is processed as a result
of the settings above (e.g., the batch request utility job step is
not terminated or abended). Select either of the following choices:
- Yes. This causes an object to be created using the default values
for the object type for the CICS region
and added to the control file.
- No. The request will be processed (e.g., the state change will
be performed), but the object's record will not be created or written
to the control file.