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
 

 

Query about /*ROUTE JES2 JECL SYNTAX.

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DB2
View previous topic :: :: View next topic  
Author Message
DB2 Guy

New User


Joined: 28 Oct 2008
Posts: 98
Location: Cubicle

PostPosted: Tue Dec 30, 2008 6:50 pm    Post subject: Query about /*ROUTE JES2 JECL SYNTAX.
Reply with quote

Hi,

Having a DB2 database sitting at one LPAR, what are the possible ways by which this database could be accessed by batch jobs running on other different mainframe machines? Can /*ROUTE be one option ?
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 31, 2008 12:37 am    Post subject:
Reply with quote

Hello and welcome to the forum,

Quote:
Can /*ROUTE be one option
Probably not. /*ROUTE XEQ executes the job on the other lpar, not "this" lpar.

If i understand what you want, you want to remotely connect to the database on the other lpar. Look here:
http://ibmmainframes.com/viewtopic.php?t=35613
Back to top
View user's profile Send private message
DB2 Guy

New User


Joined: 28 Oct 2008
Posts: 98
Location: Cubicle

PostPosted: Fri Jan 02, 2009 10:07 am    Post subject:
Reply with quote

Hi Dick,

Thanks. My concern doesn't seem to get an answer or may be I was not that clear in my previous post to tell what I need to know.

1. First, how do I understand different LAPRs at my shop has got different DB2 sub-systems or not?

2. Second, what I know is - DB2 is an expesive product so they (system programmers) install it at one LPAR. For instance, at my shop I can bind in Test-LPAR but not in production & they (seniors) say that all the JOBs actually are executing at production LPAR because we use /*ROUTE XEQ DB2DSHR in our DB2 JOBs, I actually don't understand this. Please assist.
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 Jan 02, 2009 10:42 am    Post subject:
Reply with quote

Hello,

1. Ask your system support or database administrators.

2. You appear to have confused the difference between a db2 environment and an lpar.

Your system may have many or only 1 lapr. If there is only 1 lpar, testing and production (db2 or otherwise) will happen in that lpar. If there are multiple lpars, some may be for production only or for development only or they may be mixed. An lpar may have zero to many db2 environments.

Most places do not let developers bind in Producton. . . This has nothing to do with the espense of the database software.

The people who support your system can tell you the specifics of your system. You need to build a good working relatonship with them. They have all of the "keys" and you will need things "unlocked". . .
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 -> DB2 All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts JCL to Set Return code based on DB2 S... vinu78 DB2 17 Mon Mar 13, 2017 9:47 pm
No new posts FINDREP Syntax Error seahawk789 DFSORT/ICETOOL 4 Thu Mar 09, 2017 10:11 pm
No new posts Route a product's job to specific lpar vasanthz All Other Mainframe Topics 9 Thu Mar 02, 2017 2:22 am
No new posts SQL query not working in Cobol program. CuriousMainframer COBOL Programming 14 Wed Feb 22, 2017 5:56 pm
No new posts Omegamon for DB2 query ashek15 DB2 0 Wed Feb 15, 2017 11:25 am


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