Submit a job using Connect Direct

HappySrinu · Active User Joined: 22 Jan 2008 Posts: 194 Location: India

Hi All,
I have seen couple of old messages but not so clear about it.
So I am posting it again.

Requirement:
I got two jobs JOB1, JOB2
JOB1 sits on one lpar - lets say A1
JOB2 sits on second lpar - lets say A2

Lpars A1 & A2 are two different lpars and can connect only using C

.

I want to run these jobs on their lpars and don't have any dependency between them.

I knew scheduler tools like CA7 can fix this problem very well.
But now I am looking out any way to submit these two jobs from one lpar only like.

I logon to lpar/machine A1 having JOB1 and when I submit JOB1 ..Is there any way to submit JOB2 also using any C

statements in last step of in JOB1.

If not clear, let me know

superk · Posted: Mon Apr 21, 2008 4:41 pm

Yes. Try a RUN JOB statement within the process. It can be directed to execute on either the PNODE or the SNODE.

HappySrinu · Active User Joined: 22 Jan 2008 Posts: 194 Location: India

Thanks much for your quick reply.

Would you mind, If i ask you the complete list of NDM statement to submit from one node to another becoz I got list of statement but unable to use it properly.

superk · Posted: Mon Apr 21, 2008 5:08 pm

It's a simple instruction:

[optional label] RUN JOB (DSN=dsn[(member)]) PNODE|SNODE

Just don't forget that the use of RUN JOB requires that your CONNECT:Direct task have an INTRDR DD statement that points to the JES Internal Reader.

HappySrinu · Active User Joined: 22 Jan 2008 Posts: 194 Location: India

I tried using below cards..

//SYSIN DD *
SIGNON ESF=YES
*
PROCRUN PROCESS -
PNODE=FFF -
SNODE=FFFFFF -
RUN JOB (DSN=AAAAAA.NDVR.JCL(IEBGENER)) -
&DISP=(SHR) -
&JOBNAME=AAAAA -
*
SIGNOFF
/*

but end up with SCIA001I Invalid C

command.

any suggestions

superk · Posted: Mon Apr 21, 2008 7:55 pm

This is a copy of a Connect:Direct process I use to copy a dataset to the SNODE, and then submit a job on the same SNODE if the copy is successful:

HappySrinu · Active User Joined: 22 Jan 2008 Posts: 194 Location: India

Thanks Kevin.
Unfortunately I facing the same error message.
saying" Statement not supported by C

".

previously, using the below commands, i can able to transfer the dataset..
SIGNON ESF=YES
SUB PROC=NNNNNNN -
NEWNAME=Mmmmmm -
PNODE=AAA -
SNODE=BBBBB6 -
&INDSN='SSS.IN' -
&INDISP=(SHR) -
&OUTDSN='SSS.OUT' -
&DISP=(SHR) -
&JOBNAME=vvvvvvv
SIGNOFF

but using the new code of copy, not able to do the same.

any light pls..

superk · Posted: Tue Apr 22, 2008 6:28 pm

Srini, that's twice you've posted data that, from what I can tell, appear to be SYSIN records to a DMBATCH program. What you are doing within a DMBATCH job is irrelevant to your topic. RUN JOB is a process statement.

From the Connect:Direct User's Guide:

HappySrinu · Active User Joined: 22 Jan 2008 Posts: 194 Location: India

Thanks Kevin.
I tried with all the option and at last end up with RC:0 for C

but looks I don't have access to scheduler so it's failing to demand that job.

i tried for detail information but no use.

so tried in different way and using ROUTE command and schedule around 20 jobs in one shot using rexx command. Able to do it successfully.

so even though I am still didn't get on using C

, but able to fix my problem.

vasanthz · Posted: Tue Oct 14, 2008 9:37 pm

Hi,

I am new to NDM,
I tried the above mentioned technique to submit a job and it worked fine

Could you please let me know if there is a parameter to submit the job at particular time?

I tried the below statement, but C

does not recognise it

SIGNON
SUBMIT PROC=SUBJOBS1
STARTT=(10/14/08,16:30:00)
SIGNOFF

The SUBJOBS1 proc has the following,

SUBJOBS1 PROCESS SNODE=NDMCDC PNODE=NDMCDC
STEP020 RUN JOB (DSN=XXXX) PNODE

superk · Posted: Tue Oct 14, 2008 10:43 pm

That SHOULD be

SIGNON
SUBMIT PROC=SUBJOBS1 -
STARTT=(10/14/08,16:30:00)
SIGNOFF

vasanthz · Posted: Wed Oct 15, 2008 1:59 pm

Thanks Kevin, That did the trick

superk · Posted: Wed Oct 15, 2008 7:34 pm

No problem.

Using Connect:Direct to submit batch jobs on a specific schedule is one of the oldest tricks (that I know of anyway) for scheduling jobs on a system that doesn't have a job scheduler available.

vasanthz · Posted: Thu Oct 16, 2008 1:43 pm

Just one last question,

Does NDM have any constraint like the amount of jobs that can be queued?(something like initiators)

We are not allowed to schedule user jobs on CA7

, so I have queued few jobs like this,

SUBMIT PROC=FZAPEDC -
STARTT=(16/10/2008,09:30:00) -
&DSN1=BORED.PROGRAMR(FZAP)
SUBMIT PROC=FZAPEDC -
STARTT=(16/10/2008,10:30:00) -
&DSN1=BORED.PROGRAMR(FZAP)
SUBMIT PROC=FZAPEDC -
STARTT=(16/10/2008,11:30:00) -
&DSN1=BORED.PROGRAMR(FZAP)
SUBMIT PROC=FZAPEDC -
STARTT=(16/10/2008,12:30:00) -
&DSN1=BORED.PROGRAMR(FZAP)
SUBMIT PROC=FZAPEDC -
STARTT=(16/10/2008,13:30:00) -
&DSN1=BORED.PROGRAMR(FZAP)
SUBMIT PROC=FZAPEDC -
STARTT=(16/10/2008,14:30:00) -
&DSN1=BORED.PROGRAMR(FZAP)
SUBMIT PROC=FZAPEDC -
STARTT=(16/10/2008,15:30:00) -
&DSN1=BORED.PROGRAMR(FZAP)
SUBMIT PROC=FZAPEDC -
STARTT=(16/10/2008,16:30:00) -
&DSN1=BORED.PROGRAMR(FZAP)
SIGNOFF

Will scheduling many jobs cause any hinderance to production jobs or transmissions?

Thanks in advance