Ganesh, I would suggest to use a custom Job Log table which you can write with some standard information to it
Job_Name
Job_Start_Dttm
Job_End_Dttm
Job_Status
This is a sample to jump start. You can make it robust as convinient
Create Custom Functions for
1. Insert new Job
2. Update existing for Status(Success/Failure/Running)
3. Check current status
...
...
...
First you could check for current status, if the current status turns out to be NULL, you can call the INSERT new job CF.
If the Status is Completed, then you can use the Job_End_Dttm as the Start Time for the current job run (only if you will be thinking of doing delta process handling)
If the Status is Failed, then you can use the Job_Start_Dttm as the Start Time for the current job run (only if you will be thinking of doing delta process handling) (Note: When the job fails, the Catch Block of the job should go update the job status to Failed)
If the Status of the job is Running, then you can show a decent message that another instance of the same job is running.
AL_SCHED_INFO is not related to job statuses. It just holds the current schedules created (Active/Inactive) in the Repository
Also, as a Administrator, I wouldn't like to give the access to the repository database.
Cheers
Ganesh Sampath