| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| User ID used by broker to connect to databases on z/OS. |
« View previous topic :: View next topic » |
| Author |
Message
|
| Cogito-Ergo-Sum |
 Posted: Thu May 17, 2012 2:19 am Post subject: User ID used by broker to connect to databases on z/OS. |
 |
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
I want to know the user ID being used by broker to connect to DB2.
As I understand from this link, the user ID is either the broker started task ID or the user ID set via the mqsisetdbparms for the datasource command. I submitted a batch job to run the mqsireportproperties command as documented here. But, the job keeps failing with a message as the supplied broker name being an unknown component - even though it is the right one. 
Can you please advise me how to find the user ID ?
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu May 17, 2012 5:00 am Post subject: Re: User ID used by broker to connect to databases on z/OS. |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Cogito-Ergo-Sum wrote: |
| But, the job keeps failing with a message as the supplied broker name being an unknown component - even though it is the right one. |
You may know it's the right one. The environment in which you're running your script begs to differ, and has a really good tactical position. Which of the possible methods are you using to supply the broker name?
| Cogito-Ergo-Sum wrote: |
| Can you please advise me how to find the user ID ? |
It's exactly what you said it is; the service id or the id supplied via mqsisetdbparms. I wasn't aware it was one of the configurables that mqsireportproperties listed, but I'll take your word for it & it has nothing to do with why your script is failing.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Cogito-Ergo-Sum |
| Posted: Thu May 17, 2012 5:30 am Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
| Quote: |
| You may know it's the right one. The environment in which you're running your script begs to differ, and has a really good tactical position. |
Yes, I looked high and low; but couldn't get any hint. Will check with the system programmers.
| Quote: |
| Which of the possible methods are you using to supply the broker name? |
Just as described in the syntax here.
| Code: |
//BIPRPPR EXEC PGM=IKJEFT01,REGION=0M
//STEPLIB DD DISP=SHR,DSN=SYS1.MQM.SCSQANLE
// DD DISP=SHR,DSN=SYS1.MQM.SCSQAUTH
// DD DISP=SHR,DSN=SYS1.MQM.SCSQLOAD
//STDENV DD PATHOPTS=(ORDONLY),
// PATH='/u/brkr01/ENVFILE'
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
BPXBATSL PGM -
/usr/lpp/mqsi/V6R1M0/bin/mqsireportproperties BRKR01 -
-c AllTypes -o AllReportableEntityNames -r
/*
|
| Quote: |
It's exactly what you said it is; the service id or the id supplied via mqsisetdbparms.
|
Yes, but, which one exactly ?
| Quote: |
| I wasn't aware it was one of the configurables that mqsireportproperties listed. |
The documentation does not mention that it would, either. But, I am out of ideas as to where do I look for.
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu May 17, 2012 5:45 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
There still doesn't appear to be a reasonable way to list mqsisetdbparms ids, or to determine if one exists.
Except for listing the directory contents that holds the actual ids... this is in the registry/<broker>/CurrentVersion/DSN
And, again, the way you tell whether broker is going to use the started task ID or the mqsisetdbparms ID is whether or not the mqsisetdbparms has been run to create an ID for the DSN. If it hasn't, it will use the started task id. If it has, it will use the configured ID instead. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu May 17, 2012 5:51 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Cogito-Ergo-Sum wrote: |
| Quote: |
| You may know it's the right one. The environment in which you're running your script begs to differ, and has a really good tactical position. |
Yes, I looked high and low; but couldn't get any hint. Will check with the system programmers. |
Ok, your cunning plan of not posting this in the mainframe section succeeded wonderfully; I completely missed the "z/OS" on the end of your subject line! 
Fiend.
You've also missed the section in the InfoCenter which identifies BISDBP as the job which sets this on z/OS. You can refer to this job (or the last output of this job) to determine the id.
I trust you're sufficiently ashamed (on behalf of the site in question) that you need to ask WMB what id it's using rather than looking it up in the site documentation.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Cogito-Ergo-Sum |
| Posted: Thu May 17, 2012 6:07 am Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
| Quote: |
| And, again, the way you tell whether broker is going to use the started task ID or the mqsisetdbparms ID is whether or not the mqsisetdbparms has been run to create an ID for the DSN. If it hasn't, it will use the started task id. If it has, it will use the configured ID instead. |
The trouble is I (or anyone else) do not know if that job was ever run. If there was an ounce of discipline in this site, then things would be in better order. Anyway, that discussion is for some other day.
Thanks for your time !
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu May 17, 2012 6:17 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Cogito-Ergo-Sum wrote: |
| Quote: |
| And, again, the way you tell whether broker is going to use the started task ID or the mqsisetdbparms ID is whether or not the mqsisetdbparms has been run to create an ID for the DSN. If it hasn't, it will use the started task id. If it has, it will use the configured ID instead. |
The trouble is I (or anyone else) do not know if that job was ever run |
Yeah, so looking at the file system contents is the only way to determine this.
I don't know where zOS would hide these files, but the relative path I gave is for the /var/mqm location on unix. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
