4. Operation › 4.3 Operations Reference › 4.3.4 Operational Status and Tracking › 4.3.4.4 Operational Status and Tracking Commands

4.3.4.4 Operational Status and Tracking Commands

 You will use Operational Status and Tracking commands to
 request CA MICS operations and processing status services.
 
 You can enter Operational Status and Tracking commands as
 line commands or as primary commands.
 
   o Line commands are entered in the Cmd column and apply
     ONLY to the corresponding CA MICS unit database.
 
   o Primary commands are entered in the Command area at the
     top of the panel and can apply to one or more unit
     databases, with the exception of the INCRUPDT and
     SPLITSMF commands.  The INCRUPDT and SPLITSMF commands
     require the component as well as the database ID and
     therefore only support one component/database ID
     combination per execution of the command.
 
 Detailed online tutorials document each command and the
 panels the command displays.  The online tutorials describe
 display content, usage considerations, and data entry
 instructions.
 
 Each command refreshes the Operational Status and Tracking
 display.
 
 You can also use standard CA MICS commands to subset the
 Operational Status and Tracking display (SHOW command), find
 a specific value in the display (FIND command), or position
 to a row of the display (LOCATE).  

 Note: For more information about primary command considerations and
 syntax, see the online tutorials.
 
 The Operational Status and Tracking commands are documented
 in the sections that follow.  Command syntax is documented
 below.
 
 
 COMMAND SYNTAX
 
 Enter Operational Status and Tracking commands in the Cmd
 column (line commands) to request processing for a specific
 unit database.  There are no line command parameters; simply
 enter the command name.
 
 Enter Operational Status and Tracking commands in the Command
 area as follows:
 
 command UNIT(S) dbidlist/ALL BACKUP/NOBACKUP EDIT/NOEDIT
 
 where:
 
   o command  - The Operational Status and Tracking command
                name (for example, SCHEDULE).
 
   o UNIT(S)  - Optional keyword UNIT or UNITS to indicate
                that you are specifying one or more CA MICS
                unit database (DB) IDs for the command.
 
   o dbidlist - One or more CA MICS unit database (DB) IDs
                separated by blanks.  Command will be
                performed for each DB ID in the list.
 
     or
 
   o ALL      - Specify ALL instead of dbidlist if you want to
                perform the command for each production unit
                database.  ALL does NOT apply to TEST or
                SPECIAL unit databases.
 
                For example, enter SCHEDULE ALL to submit
                today's scheduled processing for all
                production unit databases.
 
                ALL will honor the display subset you define
                with the SHOW command.  For example, if
                several unit database updates failed
                overnight, you can use ALL to RESTART each of
                the failing processes.
                 - Enter SHOW FAILED to subset the display.
                 - Enter RESTART ALL to restart processing for
                   just the unit database updates that
                   failed.
 
   o BACKUP/NOBACKUP - Optional parameter for the SCHEDULE,
                       DAILY, WEEKLY, MONTHLY, and YEARLY
                       commands.
 
                Specify BACKUP with the SCHEDULE command to
                override the processing schedule and include a
                backup in the requested processing, even if no
                backup is currently scheduled.
 
                Specify NOBACKUP to omit backup processing
                even if normally included in the requested
                processing.  DAILY, WEEKLY, MONTHLY, and
                YEARLY will always include a backup unless you
                specify NOBACKUP.
 
                You can also specify NOBACKUP on the RESTORE
                command to override your
                prefix.MICS.PARMS(JCLDEF) specification of
                RESTORE BACKUP YES.  CA MICS will restore the
                database without a pre-restore unit database
                backup.
 
                Note:  You cannot override a RESTORE BACKUP NO
                specification in JCLDEF.  Do not specify
                BACKUP on the RESTORE command.
 
   o EDIT/NOEDIT - Optional parameter for the SCHEDULE, DAILY,
                   WEEKLY, MONTHLY, YEARLY, BACKUP, RESTORE,
                   RESTART, and RSTATUS commands.
 
                Specify EDIT to override your specification
                in the Edit JCL column and display each
                generated job under PDF Edit before submitting
                the job for batch execution.
 
                Specify NOEDIT to submit generated jobs
                without a pre-submit Edit, even if you
                specified YES in the Edit JCL column.
 
 The operational status and tracking commands are documented
 in the sections that follow:
 
  1 - AUDIT Command
  2 - BACKUP Command
  3 - CHECKPT Command
  4 - CYCLES Command
  5 - DAILY Command
  6 - FORCE Command
  7 - HISTM Command
  8 - HISTORY Command
  9 - HISTW Command
 10 - INCRUPDT Command
 11 - JOBLOG Command
 12 - MONTHLY Command
 13 - REFRESH Command
 14 - RESTART Command
 15 - RESTORE Command
 16 - RESUME Command
 17 - RSTATUS Command
 18 - SCHEDULE Command
 19 - SPLITSMF Command
 20 - STATUS Command
 21 - SUSPEND Command
 22 - WEEKLY Command
 23 - YEARLY Command