Basics of JOBQ, JOBD, Subsystem in IBM i

Basics of JOBQ, JOBD, Subsystem in IBM i - for Beginners

Рет қаралды 21,123

Yusy4Code

Күн бұрын

Пікірлер: 27

@shaikshabbir7875 4 жыл бұрын

Explanation is good but u r going very fast.... It would be great if explain slowly...

@bhaskerbachi5127 2 жыл бұрын

Hi Yousuf, Your videos are good and very helpful but there is noise in background.

@vsmithz4782 4 жыл бұрын

Thank you man for sharing this...so usefull.

@vivek_modha 6 жыл бұрын

Hi, Can you post some tips or videos on how to create triggers on tables (PF) and on views (LF) Thx

@hikeoganessian1482 6 жыл бұрын

does it matter what sub system a job runs in..can there be different result with output....are there different libraries involved...I just want to know if some jobs must run in certain sub systems depending on the device description..

@poojaagrawal6191 6 жыл бұрын

Hi, The job which is submitted to subsystem QINTER by SBMJOB command will also be the batch Job or it will be considered as interactive job ?

@yusy4code 6 жыл бұрын

It is consider to be batch job only. Just because the subsystem is QINTER it doesn't mean all jobs under this will be interactive job. Interactive jobs are just our user sessions.

@tanujmayank8529 6 жыл бұрын

Hello , I have one requirement where I have to submit a job (say A) only when a Job (say B) finish . What is the best possible way ? Thanks in advance :)

@yusy4code 6 жыл бұрын

We can do this. First if both job A & B are in JS (Job Scheduler) then we can make JOB B dependent on JOB A. But if you say we are submitting both this job manually, then we can check for JOB A completion from JOB B and once completed we can start executing remaining code of JOB B. To make it easier, we can also use some DTAARA and update the data area (may be a particular position) at the end job JOB A for indicating that it is completed. And JOB B will be just looking into that DATA area position and start executing its code after JOB A is completed.

@tanujmayank8529 6 жыл бұрын

Thanks Yusuf , when you say ' then we can check for JOB A completion from JOB B and once completed we can start executing remaining code of JOB B'. How can we check this ?

@ay-by9qs 2 жыл бұрын

So useful.. thanks a lot :)

@bhaskarvepa7367 6 жыл бұрын

Can you please help me with the alternative server for PUB400. becoz some time's it goes to offline for days.

@yusy4code 6 жыл бұрын

Bhaskar Vepa as this is Free server we cannot expect to be online always but there are alternative with payment around 1800 rupees for 3 months . U can check out texas400.com for this

@bhaskarvepa7367 6 жыл бұрын

Thank you.

@sankhasubhrachatterjee5069 4 жыл бұрын

Hi @yusuf the shift + f9 doesn't work if the jobq is empty or if the subsystem is not shown in the workjobq page. Please comment on this.

@yusy4code 4 жыл бұрын

Yes, if the subsystem is not attached to the JOBQ then sfhit+F9 will not work. To see if subsystem is attached or not, you can type WRKJOBQ LIBNAME/JOBQNAME*

@prashantpatil72 6 жыл бұрын

You have changed jobq for job when it was stuck in jobq .... isn't it affect the execution of job? Also is it possible to set jobq which submitting job to other subsystem?

@yusy4code 6 жыл бұрын

If the job is in JOBQ then it has not started to run. When the job is started to run, then we cannot change the jobq. We have something called JOB priority. E.g. If we have a job with priority 2 and changing from queue A to queue B, and there are 3 jobs already in queue B with priority 3. Then this job will sit in first position. If this job also having priority 3 or more then it will be the last job in queue B.

@prashantpatil72 6 жыл бұрын

What if we change jobq from current jobq to other jobq which submit job to other subsystem? Is there any restriction to submit job to specific subsystem? And why we are using different subsystems to submit jobs?