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 nameOWNER –Owner idOdate –CTM date – date job is scheduled for.JOBNAME –Job/task nameJobID –JES job id number (last run of job, if multiple runs)TYP –Type of entryStatus –Current status - listed here are some of the various states the jobs will appear in
COMMAND LINE COMMANDS
OPtoggles 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 boxSh xxx(show filter name – xxx=filter name) brings up pre-defined filterRBAL(relative balance) not usedREF(refresh) refreshes net screensAUTO 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 STATUSPF12 – 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 okENDED 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.
Comments
Post a Comment