IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Submit a job using Connect Direct


IBM Mainframe Forums -> All Other Mainframe Topics
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
HappySrinu

Active User


Joined: 22 Jan 2008
Posts: 194
Location: India

PostPosted: Mon Apr 21, 2008 4:39 pm
Reply with quote

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 Cicon_biggrin.gif.

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 Cicon_biggrin.gif statements in last step of in JOB1.

If not clear, let me know
Back to top
View user's profile Send private message
superk

Global Moderator


Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA

PostPosted: Mon Apr 21, 2008 4:41 pm
Reply with quote

Yes. Try a RUN JOB statement within the process. It can be directed to execute on either the PNODE or the SNODE.
Back to top
View user's profile Send private message
HappySrinu

Active User


Joined: 22 Jan 2008
Posts: 194
Location: India

PostPosted: Mon Apr 21, 2008 4:52 pm
Reply with quote

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.
Back to top
View user's profile Send private message
superk

Global Moderator


Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA

PostPosted: Mon Apr 21, 2008 5:08 pm
Reply with quote

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.
Back to top
View user's profile Send private message
HappySrinu

Active User


Joined: 22 Jan 2008
Posts: 194
Location: India

PostPosted: Mon Apr 21, 2008 7:31 pm
Reply with quote

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 Cicon_biggrin.gif command.


any suggestions
Back to top
View user's profile Send private message
superk

Global Moderator


Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA

PostPosted: Mon Apr 21, 2008 7:55 pm
Reply with quote

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:

Code:

MYPROC PROCESS PNODE=pnode_name SNODE=snode_name

COPY010 COPY FROM (DSN=FROM.DATASET -
                         DISP=SHR) -
             TO (SNODE DSN=TO.DATASET -
                         DISP=(RPL,CATLG)) -
             COMPRESS EXTENDED

             IF (COPY010 EQ 0) THEN
STEP020  RUN JOB (DSN=MY.PDS(MEMBER)) SNODE
             EIF

Back to top
View user's profile Send private message
HappySrinu

Active User


Joined: 22 Jan 2008
Posts: 194
Location: India

PostPosted: Tue Apr 22, 2008 11:36 am
Reply with quote

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

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..
Back to top
View user's profile Send private message
superk

Global Moderator


Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA

PostPosted: Tue Apr 22, 2008 6:28 pm
Reply with quote

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:

Quote:

You request Connect:Direct services in the batch environment through the Batch Interface program DMBATCH. When you submit a job stream that contains the Connect:Direct commands as SYSIN input, DMBATCH reads the input stream and processes the requested functions. DMBATCH supports all Connect:Direct commands.

REQUIREMENTS

- You cannot use Process statements in the job stream. Use the SUBMIT command with a preexisting Process that contains the process statements.
- The process you submit resides in the Connect:Direct Public Process Library, allocated to the DMPUBLIB DD statement. If the process does not reside in the Connect:Direct Public Process Library, use the DSN parameter of the SUBMIT command.
- You can specify ESF (Extended Submit Facility) as a SIGNON command parameter. You can only issue SIGNON, SIGNOFF, and SUBMIT commands using ESF.


Review of Connect:Direct Process Statements:

- PROCESS. Required. Defines the process and sets up the environment.
- COPY. Provides the requirements for copying of files from one node to another.
- RUN JOB. Submits the indicated dataset to the JES Internal Reader on the specified node.
- RUN TASK. Submits the indicated program along with it's parameters on the specified node.
- SUBMIT. Submits the indicated process on the specified node.
- SYMBOL. Builds symbolics.
- MODAL STATEMENTS. IF/THEN/ELSE/EIF, GOTO, EXIT.
Back to top
View user's profile Send private message
HappySrinu

Active User


Joined: 22 Jan 2008
Posts: 194
Location: India

PostPosted: Wed Apr 23, 2008 7:07 pm
Reply with quote

Thanks Kevin.
I tried with all the option and at last end up with RC:0 for Cicon_biggrin.gif 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 Cicon_biggrin.gif, but able to fix my problem.
Back to top
View user's profile Send private message
vasanthz

Global Moderator


Joined: 28 Aug 2007
Posts: 1742
Location: Tirupur, India

PostPosted: Tue Oct 14, 2008 9:37 pm
Reply with quote

Hi,

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

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

I tried the below statement, but Cicon_biggrin.gif does not recognise it icon_cry.gif
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
Back to top
View user's profile Send private message
superk

Global Moderator


Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA

PostPosted: Tue Oct 14, 2008 10:43 pm
Reply with quote

That SHOULD be

SIGNON
SUBMIT PROC=SUBJOBS1 -
STARTT=(10/14/08,16:30:00)
SIGNOFF
Back to top
View user's profile Send private message
vasanthz

Global Moderator


Joined: 28 Aug 2007
Posts: 1742
Location: Tirupur, India

PostPosted: Wed Oct 15, 2008 1:59 pm
Reply with quote

Thanks Kevin, That did the trick icon_biggrin.gif icon_biggrin.gif
Back to top
View user's profile Send private message
superk

Global Moderator


Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA

PostPosted: Wed Oct 15, 2008 7:34 pm
Reply with quote

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.
Back to top
View user's profile Send private message
vasanthz

Global Moderator


Joined: 28 Aug 2007
Posts: 1742
Location: Tirupur, India

PostPosted: Thu Oct 16, 2008 1:43 pm
Reply with quote

Just one last question,

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

We are not allowed to schedule user jobs on CA7 icon_evil.gif , 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 icon_smile.gif
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> All Other Mainframe Topics

 


Similar Topics
Topic Forum Replies
No new posts Connect Direct 6.3 for Z/OS All Other Mainframe Topics 20
No new posts Submit multiple jobs from a library t... JCL & VSAM 14
No new posts Getting TWA in CICS program while con... CICS 14
No new posts Unable to connect FTP over TLS from z... All Other Mainframe Topics 5
No new posts Connect:Direct Add yesterday date in ... All Other Mainframe Topics 3
Search our Forums:

Back to Top