how to specify USER parameter when Xpediting BATCH DB2 prog

gopinaras · New User Joined: 13 Jan 2010 Posts: 4 Location: Chennai

Hi All,

I have a problem in Xpediting a batch db2 program. In my site, we do not have DB2 Plan access for our IDs. We use a common batch id for test jobs. In my JCL I use USER=BATCHID.

But When I am trying to Xpedit the db2 program, it gives me an error "DSNE106E PLAN DRESI53D NOT AUTHORIZED FOR SUBSYSTEM DB2B AND AUTH ID JZVGBQ "

Is there a way to specify USER parameter in Xpeditor when debugging batch programs?

Thanks in advance.

Anuj Dhawan · Posted: Fri Apr 15, 2011 5:21 pm

Well, the quick answer is -- get in touch with your DBA/DB2-System programmer to get the necesary access.

Other thing which comes to mind is - are you able to execute the program, without using xpeditor? If yes, does the DDIO has the correct load module?

gopinaras · New User Joined: 13 Jan 2010 Posts: 4 Location: Chennai

Hi Anuj,

Thanks for the reply, I am able to execute the program w/o xpeditor in JCL having USER=BATCHID.

I am thinking if there is some way to specify this USER parameter to Xpeditor so that it would use BATCHID to access PLANs

dbzTHEdinosauer · Posted: Fri Apr 15, 2011 8:14 pm

this is a site problem. contact your support, they will tell you how.

Anuj Dhawan · Posted: Mon Apr 18, 2011 3:46 pm

gopinaras · New User Joined: 13 Jan 2010 Posts: 4 Location: Chennai

Hi All,

I am new to Xpeditor, would "Debug programs interactively under batch" be an option here? I am not familiar with this although.

Can someone please advise me on the difference between debug under BATCH vs TSO (interactive) why we need two different options.

Thanks in anticipation.

Robert Sample · Posted: Mon Apr 18, 2011 6:50 pm

The option "Debug programs interactively under batch" allows you, if set up at your site, to submit a batch job and interactively debug it via TSO. It is typically, but not always, set up as part of the Xpediter installation process. You must provide to Xpediter the batch JCL that you submit; Xpediter modifies the JCL to include its libraries and when submitted allows you to connect to the batch job (if you use Interactive debugging on the appropriate screen). The Xpediter commands remain the same, the main difference is that when you set a breakpoint and run until the breakpoint, the execution is in the batch job not your TSO session.

If you try it and cannot get it to work, you must contact your site support group as only they can tell you the specific libraries and settings that are required for your site.