Query about /*ROUTE JES2 JECL SYNTAX.

DB2 Guy · New User Joined: 28 Oct 2008 Posts: 98 Location: Cubicle

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 ?

dick scherrer · Posted: Wed Dec 31, 2008 12:37 am

Hello and welcome to the forum,

DB2 Guy · New User Joined: 28 Oct 2008 Posts: 98 Location: Cubicle

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.

dick scherrer · Posted: Fri Jan 02, 2009 10:42 am

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". . .