| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ 5.3 on z/os and SSL trace |
« View previous topic :: View next topic » |
| Author |
Message
|
| Guido |
 Posted: Thu Jun 24, 2004 4:27 am Post subject: MQ 5.3 on z/os and SSL trace |
 |
|
Newbie
Joined: 24 Jun 2004
Posts: 4
Location: Suisse
|
Hi !
Well, my first posting here, let's look if somebody can help me... 
I had to setup SSL for channels between mq on z/os and a mq on sun solaris. We strugeled little bit arround but finaly managed to thing to work. One experience at least on my z/os side was, that the messages related to SSL errors are not in a good 'quality' (oh, didnt found the ring ? nice, for which ring were you looking for...?). Therefore I wanted to use the component trace on z/os. Set up the needed jobs as the samples. Component procedure as well as the trace writer run succesfull, start/stop of trace doesn't produce any error message. But I simple dont get any output written to the dataset. When starting the trace (/trace ct,on,...), I reply to the reply with /nnn,jobname(qs1ichin),... QS1ICHIN is the channel initiator address space, where I'm interrested in regarding the SSL calls. Is it a problem as on z/os, the SSL activities are done under seperate tcb's and not the job step one ?
Thanks for all replies
Guido |
|
| Back to top |
|
 |
| frankdk |
| Posted: Mon Jul 19, 2004 7:46 am Post subject: |
|
|
Novice
Joined: 10 Jun 2004
Posts: 20
Location: Copenhagen, Denmark
|
Hi Guido
I believe you are using GTF trace?
The chin will apperantly only trace to DEST(RES) which is the chin trace dataspace.
Try to dump the chin with active trace and DEST(RES) and see if that helps.
_________________
Regards,
Frank |
|
| Back to top |
|
|
| pbmsmit |
| Posted: Tue Jul 20, 2004 7:57 am Post subject: |
|
|
Apprentice
Joined: 11 Jul 2003
Posts: 42
Location: Chicago
|
Guido,
We had also problems with SSL trace: Be aware that most of the SSL calls are done when the CHIN starts. Another (known) problem is that SSL tasks are multitasked and will not be catched by an SSL trace (that's what IBM told me).
Sometimes an OMVS trace might help you.
I agree with you, that there is a challenging task for IBM to enhance the errormessage and include the names or ID's that it's looking for instead of a generic errormesage 'there is something wrong'.
_________________
Peter Smit
LaSalle Bank Corporation, member of ABN AMRO NV Group |
|
| Back to top |
|
|
| Guido |
| Posted: Mon Sep 20, 2004 3:38 am Post subject: |
|
|
Newbie
Joined: 24 Jun 2004
Posts: 4
Location: Suisse
|
Hi
As we finally managed to run the things fine, I forgott my posting here... Therefore a late thanks for your reply...
Regards
Guido |
|
| 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
|
|
|
|
