Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

WHAT DOES THIS /*ROUTE XEQ DB2P DO?

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
santoshkumarmanilakkoju

New User


Joined: 24 Nov 2009
Posts: 37
Location: Don't know

PostPosted: Tue Dec 15, 2009 2:21 pm    Post subject: WHAT DOES THIS /*ROUTE XEQ DB2P DO?
Reply with quote

CAN SOME ONE HELP ME WITH MY UNDERSTANDING.

/*ROUTE XEQ DB2P

ONLY RUNS A JOB AT DB2P SUB SYSTEM, BUT THE COMMAND IS USED TO TRANSFER CONTROL TO DIFFERENT LPAR.

IS IT TRUE THAT DB2P IS NOW CONSIDERED AS A DIFFERENT LPAR.
Back to top
View user's profile Send private message

expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Tue Dec 15, 2009 2:38 pm    Post subject:
Reply with quote

DO NOT use all upper case, this is seen as shouting and considered impolite.

There is a JCL reference manual easily available by hitting the "IBM Manuals" button at the top of every page. Please go there, read the relevant section of the manual and then come back if you have any questions.

You will also need to learn to supply more information than you have done. Which LPAR do you submit the job from, and does it always run on the DB2P LPAR.
Back to top
View user's profile Send private message
santoshkumarmanilakkoju

New User


Joined: 24 Nov 2009
Posts: 37
Location: Don't know

PostPosted: Tue Dec 15, 2009 2:45 pm    Post subject:
Reply with quote

Thank you for the valuable tips.
Back to top
View user's profile Send private message
enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10203
Location: italy

PostPosted: Tue Dec 15, 2009 2:49 pm    Post subject: Reply to: WHAT DOES THIS /*ROUTE XEQ DB2P DO?
Reply with quote

Code:
/*ROUTE XEQ DB2P


jes nodenames are a local standards issue
( arbitrary string of up to 8 chars )

the jcl statement will route the job for execution somewhere in Your jes2 (network/shared_spool) complex to a node called DB2P


ask Your support about the naming standards in Your organization
(and, if You are curious, why they were chosen in that way )

probably Your support chose names easy to remember
Back to top
View user's profile Send private message
rexzone1

New User


Joined: 16 Dec 2006
Posts: 14
Location: Halifax, Canada

PostPosted: Tue Dec 15, 2009 8:28 pm    Post subject:
Reply with quote

Hi Santosh,

In my installation this statement in the JCL directs to use the DB2P (Production) subsystem and DB2T (Test) subsystem.
In simple words, this statement tells the COBOL program executed in the job to use Test or Production DB2 subsystem as assigned to DB2T or DB2P.

Hope this helps.
Back to top
View user's profile Send private message
santoshkumarmanilakkoju

New User


Joined: 24 Nov 2009
Posts: 37
Location: Don't know

PostPosted: Wed Dec 16, 2009 9:09 am    Post subject:
Reply with quote

Thanks a lot Ravi,

Its a learning for me and many others.
Back to top
View user's profile Send private message
sanjuhk

New User


Joined: 14 Dec 2009
Posts: 2
Location: India

PostPosted: Wed Dec 16, 2009 10:47 am    Post subject: Reply to: WHAT DOES THIS /*ROUTE XEQ DB2P DO?
Reply with quote

I agree with ravi
Back to top
View user's profile Send private message
enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10203
Location: italy

PostPosted: Wed Dec 16, 2009 11:20 am    Post subject: Reply to: WHAT DOES THIS /*ROUTE XEQ DB2P DO?
Reply with quote

it would be more useful if people would refrain from posting wrong answers...
( based on what seems to be local jargon )
Quote:
this statement tells the COBOL program executed in the job to use Test or Production DB2 subsystem as assigned to DB2T or DB2P.
wrong ... the db2 subsystem to be used is specified on the DSN command

as I said before the JCL statement posted from the TS governs the
JES node under which excution will take place
-- no need to be on the same lpar, just a connected JES2 which could be thousandths miles away

the fact that the node name resembles a db2 susbsystem name is accidental

nobody read my previous post ( seems )

nobody cared to look at the manuals for the explanation of the route statement
to save some of their precious time to the ts and the gentleman who posted a wrong answer here is the link to the manual page
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2B670/27.9?SHELF=IEA2BK81&DT=20070427231644
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Wed Dec 16, 2009 8:13 pm    Post subject:
Reply with quote

Hello Sanjuhk and welcoem to the forum,

Quote:
I agree with ravi
Having multiple "votes" does not make something incomplete/incorrect become valid. If 100 or 1,000 others agreed, it would still be invalid. . .

Quote:
Its a learning for me and many others.
Unfortunately, anyone who "learned" something, learned a wrong thing. . .

Given that many places have multiple lpars and multiple db2 subsystems, it is quite likely they will just happen to have an lpar and a subsystem with the same name. This has nothing to do with the /*ROUTE XEQ that was the original question. It is just a coincidence.
Back to top
View user's profile Send private message
karisurya

New User


Joined: 02 Aug 2007
Posts: 64
Location: Bangalore

PostPosted: Thu Dec 17, 2009 4:44 pm    Post subject:
Reply with quote

Hi Santosh,

I used this command some time back to execute the JOB in different subsystem. lets say if we have 2 mainframe systems or LPAR and if we need to execute job in other sub system from currect system we can acheive it by using Route command. The syntax will be slightly different based on JES2 and JES3.

Do a search on this site using ROUTE string and i am sure you will get lot of posting which discussed this topic.
Back to top
View user's profile Send private message
PeterHolland

Global Moderator


Joined: 27 Oct 2009
Posts: 2422
Location: Netherlands, Amstelveen

PostPosted: Thu Dec 17, 2009 5:06 pm    Post subject:
Reply with quote

As far as i see it the /*ROUTE XEQ means to execute something on another (LPAR, another MF) by means of a SUBSYSTEM (e.g. JESx)
where the target can have any name (but that would be stupid).
On the target a DB2 SUBSYSTEM has to be started, with i guess
DB2P as identifier.
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Fri Dec 18, 2009 2:06 am    Post subject:
Reply with quote

Hello,

Quote:
As far as i see it the /*ROUTE XEQ means to execute something on another (LPAR, another MF) . . .

The nodename might be another lpar or the same one where the statement is issued.

Quote:
On the target a DB2 SUBSYSTEM has to be started, with i guess
DB2P as identifier
If the routed job uses db2, then db2 would have to be started. Many routed jobs to not use db2 at all. There is no direct relationship between the routed nodename and the db2 subsystem to be used when the job is executed.

Also, consider lpar DB2P running several Production DB2 subsystems (i.e. DBP1, DBP2, DBP3). The route statement would not reference any of these, just that the job should run on the DB2P lpar/node.
Back to top
View user's profile Send private message
Terry Heinze

JCL Moderator


Joined: 14 Jul 2008
Posts: 1238
Location: Richfield, MN, USA

PostPosted: Fri Dec 18, 2009 3:27 am    Post subject:
Reply with quote

Reminds me of the confusion injected when developers name an index something like WS-SUBSCRIPT-A or name a subscript something like WS-INDEX-A. icon_mad.gif
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts /*ROUTE in CLIST lvbntapasvi CLIST & REXX 1 Thu Aug 27, 2015 9:33 pm
No new posts Generate a list of data sets and rout... Charles Wolters TSO/ISPF 8 Thu Mar 22, 2012 1:19 am
No new posts Problem with /*ROUTE XEQ vasanthz JCL & VSAM 4 Wed May 19, 2010 4:04 pm
No new posts Route Reports to Printer without prin... akhi007 JCL & VSAM 3 Thu Apr 22, 2010 9:12 pm
No new posts Route the symptom dump to a file. passion_sujesh ABENDS & Debugging 3 Tue Sep 22, 2009 8:57 am


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us