Zeke

What is Zeke?

Zeke is a software tool used to Submit and control the running of production events. It automates our work by scheduling dynamically and dispatching events. Zeke is supported on Z/OS, VSE OS and other distributed systems.

How to log on to Zeke?

We have to type ‘Zeke’ or ‘TSO %ZEKE’ in the ISPF panel and press enter.

Different type of Zeke events

Event Type	Description
JOB	Batch job stream
MSG	Console message
WORK	Work Center
VCOM	VM/CP command
ZCOM	Zeke operator command
SCOM	System command
PCOM	Power command

Zeke Primary Menu:

Event Master record : Zeke contains information for each event in Event Master Record which stores in Zeke database. EMR holds the detailed scheduling information like job name, date and time the event runs, prerequisite conditions and resource requirements. Zeke database contains different records like Schedule Queue record, Calendar, variables etc.

Primary Commands of EMRs Definition :

Command	Description
ACCT	Preserve the Zeke event accounting history
Add	Adding Event definition
Browse	Browsing an event definition
CCode	Contains condition code information for a job
Copy	It inherits the properties(like Occurs and when conditions) of existing event to a new event.
Auto reply	Preserves auto reply elements for an event

Zeke Line commands list:  To repeat the last command we have to give the line command as ‘=’

Zeke Line commands list
Line command	Description	Line command	Description
ADDOK	Set “need operator ok” to the event	PRED	Pathfinder-Show predecessors /View all the predecessors
ALTer	Apply same changes to tagged	REB	Rebuild  the SQR for the selected event.
DEL	To delete  selected job from the schedule	REBH	Rebuild the SQR and place HOLD on the selected event.
DIS	To disable the event ( remove the event from the schedule)	REF	Refresh the SQR
DSN	ASG-Zebb Step/DD Level Info  for the selected event	REL	Release  an operator hold
EMR	Display EMR for the selected event	RESO	Display resources required
EN	Enable  the  selected disabled event	RSTR	ASG-Zebb Job Restart Management
FDEL	Delete with acquired resources and then delete the SQR	RUN	Satisfy conditions and dispatch the event.
FDON	Force the selected event to DONE status	SCAN	Scan the JCL
FFAI	Force the selected event to FAILED status	SUCC	Pathfinder-Show successors /View all the Successors
FREB	Rebuild with acquired resources and then re-add the event to the Schedule.	SYS_	Browse: L job log J JCL M sysmsg
FREF	Refresh with acquired resources and then re-add the event t the schedule.	TOK	Set "time OK"  to the selected event.
FSUC	Force the selected event  to SUCCESS status	WHen	Display "WHEN" conditions for the selected event.
Hold	Hold the selected event	WHY	Display "WAIT" conditions for the selected event.
JCLR	Retrieve JCL for the selected event.	WOK	Set "WHEN OK" to the selected event.
JPRE	Invoke ASG-JCLPREP to scan JCL	WORK	Invoke Work Center (Option 5)
LDSN	ASG-Zebb List DSN Detail Info	ZEBB	ASG-Zebb Job Functions Menu
NOTE	Display note text (if any) for the selected event.	ZOom	Display all the info in one screen
OK	Set "operator OK” to the selected event.	?	Display list of line commands

Schedule View: We can view the jobs in the current day schedule. In schedule information selection criteria we can display the events those in different status using the below options.

ACTV:   Select Y (YES) – View the current executing events in the Queue.

                Select N (NO)   – View the schedule events that are not in active status.

Pend:  Pending  Select Y (YES) – To View the pending jobs in the current schedule

                           Select N (NO)   – Not to view the pending events in the queue.

Sched: Scheduled   Select Y (YES) – To view the scheduled events in the queue.

                                Select N (NO) – Not to view the Scheduled events in the queue.

HOLD:     Select Y (YES) – TO view the jobs those are in hold.

                  Select N (NO) – Not to view jobs that are in hold status.

LATE:  Select Y (YES) – To view the jobs those are in late status.

               Select N (NO) – Not to view the jobs those are in late queue.

Oper ok: Operator ok  Select Y (YES) – To view the events with user requirement.
                                      Select N (NO) – Not to view the events with user requirement. 

Note: If yes need approval from the operator.

                                          

Time ok:   Select Y (YES) – To view the time dependent events in the queue.

                   Select N (NO) – Not to view the time dependent jobs in the queue.

Done:   Select Y (YES) – To view the successfully completed jobs in the schedule.

             Select N (NO) – Not to view the events those are in Success status.

FSucc:   Select Y (YES) – To view the force completed jobs.          

               Select N (NO) – Not to view the purged jobs in the queue.

When ok:  Select Y (YES) – To view the events whose when conditions are satisfied.  

                   Select N (NO) – Not to view events whose when conditions are satisfied

Note: When ok status indicates Event met Job dependency but waiting for time requirement.

ABok:  Select Y (YES) – To view the successful jobs that are failed once.

             Select N (NO) – Not to view the successful jobs that are failed once.

FBok:   Select Y (YES) – To view the failed jobs that are force completed.

              Select N (NO) – Not to view the failed jobs that are force completed.

Schedule Queue Record : In Zeke when we run the Schedule Function, it retrieves EMR information from the database and creates Schedule Queue record. We can modify these records without affecting EMR for that particular run. Here schedule function clears the previous completed schedule and add a new schedule for the current day.


Calendar:  We are defining WORKDAYS, WEEKENDS and Holidays to the events in Zeke. We can run particular event on all workdays and also specified days through the command OCCURS.

Different Status in Zeke: There are different job statuses in Zeke

STATUS	EXPLANATION
SUCCESS	Job successfully completed in ZEKE
ACTIVE	Job is currently executing
SUCCESS FAILED ONCE	Job ran successfully after restarting from failed status
SUCCESS FORCED FAILED ONCE	Force completed the failed job
SCHEDULED	Job scheduled for today’s run but waiting on time or job dependency
SCHEDULED TIME OK	Time requirement is satisfied  or time is not defined
SCHEDULED WHEN OK	Job dependency is met but job is waiting for scheduled time
SCHEDULED OPERATOR HOLD	Job is on hold and also waiting for time/job requirements.
QUEUED OPERATOR HOLD	All dependencies are met but the job is on hold

Event Master Definition fields explanation:

DESC: Description of the job

Event name: this field specifies the name of the event.

APP: This field specified the name of application of particular event.

Sched: This field specifies the scheduled time of particular job

Early: Earliest time that the zeke dispatch the event if all dependencies are satisfied and if an initiator available.

Mustend:  If the system time and avgduration time is greater than mustend time then zeke removes the event from the queue automatically.

Notafter:  This field specifies the latest time that Zeke can dispatch the event and also if notafter time is less than the system time then zeke removes the event from the current schedule.

Lateend:  This field specifies that the event must finish its execution.

Avgdur: Actual run time of particular job

Job :  This field specifies  the job name

Operok : This field specifies the operator approval required for execution or not

Class: Assigning a class to the job.

Schenv:  This field specifies the environment which the job should run.

Platform: This field specifies the platform like MVS, UNIX etc

Times:  specifies number of times the job executes per day

Note: Initiator:  Initiator is a special address space to which batch jobs are mapped during execution

Class: Assigning a class to the job which provides a less explicit way to specify the input priority.

Different conditions in Zeke:

NOTDURING CONDITION: This condition specifies that the event ‘B’ should not run while event ‘A’ is executing.

EOJ (End of job): This condition specifies that the event ‘B’ will execute only when the event ‘A' completes.

*EOJ (END of Job): This specifies that the job is completed.

#EOJ (END of Job): This specifies that the job is not scheduled for the current day.

OCCHIT:  This command can help us to view the calendar.

                                                                        THE  END