Skip to main content

Control M: Active Jobs screen AJF


OPTION 3 - ACTIVE JOBS SCREEN 

  • This screen lists all the jobs on the ‘ACTIVE SCHEDULE’. 
  • Jobs are listed in this screen in the order they are forced out. 
  • Jobs are loaded in one of two ways. 
  • Schedule load jobs run after midnight and will load any jobs scheduled to run that day.  Also, many jobs are forced onto the schedule throughout the day, either manually by the OTA’s or prod svcs, via some form of automation such as a Control-O rule, an existing job on the AJF, or SYSD.
  • Jobs will remain on this screen until they meet conditions to be ‘rolled off’. 
  • Jobs that are ENDED OK, will roll off with the next schedule load.  
  • Jobs that are in are in some form of ENDED NOT OK or WAIT SCHEDULE will remain on the schedule for a standard of 3 days. 
  • Jobs that are in a HELD state will never roll off until released, jobs that are active or in an EXECUTING state also will not roll off until they leave that state.
    BREAKDOWN OF FIELDS IN SCREEN 3
    NAME –
    Job/task name
    OWNER –
    Owner id
    Odate –
    CTM date – date job is scheduled for.
    JOBNAME –
    Job/task name
    JobID –
    JES job id number (last run of job, if multiple runs)
    TYP –
    Type of entry
    Status –
    Current status  - listed here are some of the various states the jobs will appear in

    COMMAND LINE COMMANDS

    OP
    toggles help screen at bottom between command line commands and commands performed on schedule entries.
    DI
    (display) used to change display type.
    HI
    (history) will show history (standard 3 days back).
    Sh 
    (show)  brings up show box
    Sh xxx 
    (show filter name – xxx=filter name) brings up pre-defined filter
    RBAL
    (relative balance)  not used
    REF
    (refresh) refreshes net screens
    AUTO nn
    (auto refresh) Initates auto update, with nn being the number of seconds it is set for.
    JOBSTAT xxxxxx y 
    (jobstat) Brings up jobstats for any job, must provide jobname (xxxxxx) and group id (y)

    You can enable two other display options with these keys:

    PF11 – will show GROUP ID at the end of STATUS
    PF12 – will show ORDER ID at the end of STATUS

    WAIT SCHEDULE
    – waiting on requirements, including but solely IN-CONDITIONS, RESOURCE requirement, TIME requirement, schedule CONTROL.
    EXECUTING
    – job is executing.
    WAIT EXECUTION
    – all requirements have been met, job is waiting on requirement external to the scheduler – (common causes – job is waiting on JES init or is on HOLD in JES queue)
    HELD WAIT SCHEDULE
    – job has been held manually, it will need to be freed. (note- a job will show up like this whether or not it held by other requirements (ie IN-CONDITIONS etc.)
    REQUESTED HELD
    – hold has been issued, but has not been completed.
    REQUESTED CHANGE
    – change to jobsetup on AJF has been perfromed, but not yet completed.
    WAIT CONFIRMATION
    – job is setup with a CONFIRM=Y parameter, meaning it requires someone to issue a C next to the job to run.   Like a held job, it may be waiting on other requirements.
    WAIT SUBMISSION
    – all requirements have been met, job is about to execute.
    ENDED OK
    – job has ended ok.
    ENDED OK – FORCED OK
    – indicates the job has been forced ok
    ENDED NOT OK
    – job has ended abnormally.
    ENDED NOT OK
    – JCL ERROR – ended not ok due to jcl error.
    ENDED NOT OK
    – DUE TO CC – ended not ok due to high return codes.
    ENDED NOT OK
    – REASON UNKNOWN – Incomplete sysout, Control-M can find the sysout,but cannot determine how the job ended (system crashes, or if the job was terminated via asid)
    NOT SUBMITTED
    – Control-M attempted to submit the job, but failed (reason can be found in the IOA log – common cause, jcl not found)
    DISAPPEARED
    – Control M could not find the sysout of a job and could not determine it’s result.
    DELETED
    – Entry has been manually deleted.
Labels:

Comments

Post a Comment

Popular posts from this blog

Restarting a abended job in CA7

To restart the job, type xQ command to get into the CA7 Queue Maintenance. Tab down to the job you want to restart, type an 'F' beside it, and hit the Enter key. You will get into restart panel. Options for restarting the job: Resubmit for production: Resubmits the job with no changes.  Force complete: Indicates whether to flag the job as normally completed. If force complete is selected, the previous abnormal status of the job is ignored, and normal job completion processing is performed instead of a restart. CA-11 restart/rerun :Complete the following fields for a CA-11 restart/rerun: Pseudo(Optional) Indicates whether this job uses the CA WA Restart Option pseudo processing feature. Usage(Optional) Indicates an optional CA WA Restart Option usage code, the character to use in the restart/rerun. For values, see the CA WA Restart Option documentation. This option is honored only when CA WA Restart Option is in use and CA Workload Automation CA 7 Ed
Post a Comment
Read more

Control M: Zoom Screen

This section breaks down the various fields you see within a job using the Zoom command.    Many of the fields within the zoom     screen can be altered.   There a few (they will show a different color) that cannot.   To make any changes, a job must be in a HELD     state before zooming, then when in the zoom screen make the changes and type SAVE at the command line.   Remember to FREE     the job when you are satisfied with your change.   Type CANCEL instead of SAVE if you don’t want your changes to be saved. MEMNAME – schedule member name, should be same as jobname. MEMLIB – denotes where CTM will scan for jcl, standard is GENERAL, which will default to the                     predefined concatenation.   An entry of DUMMY indicates a dummy job, or one that will not execute jcl.   These                    are used as schedule placeholders.   OWNER – owner id of job. TASKTYPE – JOB – batch job, STC – started task, GRP – group entry, CYC – cyclical job o
1 comment
Read more

Control M : Commands entered against a job or task

  ? (WHY) Displays what a job is waiting on.    This shows only what a job is currently waiting on at that          time.    It will not show conditions that have already been met, and, certain requirements may change.   ex – you may check a job and it is waiting on a certain job/in-condition one minute.   you check 5 minutes          later and the in/condition may have been met, but it now is waiting on an INIT.       Also, within this screen, you can add an IN-CONDITION.   USE CAUTION when doing this.   It should     only be used when you are ABSOLUTELY SURE that you want to add this condition as it will add it for     any job on the schedule looking for it- and any other job looking for it on that day. L   (log) Displays IOA log entries for that job.   H (hold) Puts job in held status.   A job held will not change states until it is freed.   For example, if a job         is executing is held, even though the job ends, Control M will not change it’s sta
Post a Comment
Read more