CA7 SHUTDOWN with Batch Terminal interfaces running

Products

• CA Workload Automation CA 7 Edition

Issue/Introduction

Performed CA7 SHUTDOWN, Z1 . But failed (see messages below) because there were multiple batch terminal interfaces running.
Had to cancel CA7 started task.

/SHUTDOWN,Z1                                              
SCM2-11 BATCH RUN IN PROGRESS.        /SHUTDOWN IGNORED.
  
Should we change our automated shutdown procedure from a SHUTDOWN,Z1 to a SHUTDOWN,Z3 and if so,
what happens to the batch runs in progress in CA7. 

Environment

Release:
Component: 7

Resolution

If you change your shutdown procedure for CA7 from a SHUTDOWN,Z1 to a SHUTDOWN,Z3.  Z3 will cause CA7 to shutdown immediately even if online and/or batch type terminals are active and in use, it will terminate with a rc=8.  Basically, Z3 shutdown kills batch terminals in use.  Full list of options of shutdown are as follows:  Z1  Specifies a "fast" shutdown of CA Workload Automation SE. Messages are not sent to the individual terminals, and CA Workload Automation SE does not wait for them to log off but waits for batch type terminals to complete (this includes CAICCI terminals).  Z2  Specifies that shutdown is to occur even if batch type terminals are still active but waits for online terminals to log off.  Z3  Specifies that shutdown is to occur even if online and/or batch type terminals are active.  Z4  Specifies a combination of Z1 and DMPQ.  Z5  Specifies a combination of Z3 and DMPQ.

Case Reason

Answer - Available