|
View previous topic :: View next topic
|
| Author |
Message |
santoshkumarmanilakkoju
New User
.jpg)
Joined: 24 Nov 2009
Posts: 37
Location: Don't know
|
|
|
|
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 |
|
 |
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
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 |
|
|
santoshkumarmanilakkoju
New User
Joined: 24 Nov 2009
Posts: 37
Location: Don't know
|
|
|
|
| Thank you for the valuable tips. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
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 |
|
|
rexzone1
New User
.jpg)
Joined: 16 Dec 2006
Posts: 14
Location: Halifax, Canada
|
|
|
|
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 |
|
|
santoshkumarmanilakkoju
New User
Joined: 24 Nov 2009
Posts: 37
Location: Don't know
|
|
|
|
Thanks a lot Ravi,
Its a learning for me and many others. |
|
| Back to top |
|
|
sanjuhk
New User
Joined: 14 Dec 2009
Posts: 2
Location: India
|
|
|
|
| I agree with ravi |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
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
publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2B670/27.9?SHELF=IEA2BK81&DT=20070427231644 |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello Sanjuhk and welcoem to the forum,
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 |
|
|
karisurya
New User
Joined: 02 Aug 2007
Posts: 64
Location: Bangalore
|
|
|
|
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 |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009
Posts: 2481
Location: Netherlands, Amstelveen
|
|
|
|
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 |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
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 |
|
|
Terry Heinze
JCL Moderator
Joined: 14 Jul 2008
Posts: 1249
Location: Richfield, MN, USA
|
|
|
|
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.  |
|
| Back to top |
|
|
|
|
