| Author |
Message
|
| stanko |
 Posted: Thu May 22, 2008 4:32 am Post subject: Force user identifier to upper case. |
 |
|
Newbie
Joined: 22 May 2008
Posts: 5
|
Greetings!
I need user identifier to be sent on a remote queue in upper case, how can I achieve that? If I sent it on a queue which is not remote (local), I will get user in any case I want, but if it is queue remote, than MQ will transfer user identifier to lower case.
TIA!
Stanko. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu May 22, 2008 5:59 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
I'm guessing that you mean the userid field in the message descriptor (MQMD). It is taken from the logged-on user supplied by the o/s, unless your application program sets this field.
z/OS (mainframe) userids are in upper-case; Win and UNIX userids allow mixed-case.
What o/s is the sending platform? What o/s is the receiving platform?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| stanko |
| Posted: Thu May 22, 2008 6:36 am Post subject: |
|
|
Newbie
Joined: 22 May 2008
Posts: 5
|
It is windows 2003 server, receiving platform is Unix.
| Quote: |
I'm guessing that you mean the userid field in the message descriptor (MQMD)
|
Yes, my program set that field, and everything is ok except that it is in lower case  |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu May 22, 2008 6:53 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| stanko wrote: |
It is windows 2003 server, receiving platform is Unix.
....
Yes, my program set that field, and everything is ok except that it is in lower case |
What kind of Unix system has upper case ids? 
Well upper case anything really. What's the requirement here?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu May 22, 2008 7:14 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| Yes, my program set that field, and everything is ok except that it is in lower case |
Most popular programming languages have the facility for converting lowercase to uppercase, and uppercase to lowercase. If that is what your application requires, then your application program needs to convert the userid to uppercase before it MQPUTs the message to the queue.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| stanko |
| Posted: Thu May 22, 2008 7:25 am Post subject: |
|
|
Newbie
Joined: 22 May 2008
Posts: 5
|
Thank you all for answering!
In my program I put user identifier in upper case, but the oter side claim that they received it in lower case. Also, we tested it in our enviroment, on windows MQ we also get user identifier in COA (confirmation of arrival) messages in lower case.
All I know, on the other side they said they can't send COD (confirmation of delivery or delete, i am not sure any more) because user identifier can't log in... What that actually mean, I don't know...
So, I need to be able to receive COA of my messages with user identifier with upper case... |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu May 22, 2008 7:30 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| stanko wrote: |
All I know, on the other side they said they can't send COD (confirmation of delivery or delete, i am not sure any more) because user identifier can't log in... What that actually mean, I don't know...
|
I still think you've got an odd setup with Windoze (and especially Unix) with upper case ids. It's not a usual position.
There has been a lot of discussion recently about sending COA & COD messages, and the user ids that need to be authorised to do it. Use the search facility to dig these out - you may need more setmqaut than you think.
You might also want to search for my usual rant about how pointless COA & COD messages are at best, and how destructive they can be at worst. Be very, very sure you need them before you start using them.
And by "need", I mean a technical need not some project manager needing reassurance.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu May 22, 2008 7:36 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| In my program I put user identifier in upper case, but the other side claim that they received it in lower case |
Please amqsbcg or similar utility to print one of the messages in question. Cut and paste the entire message descriptor (MQMD) here.
Ask the folks at the receiving end to do the same.
Are both sending and receiving queue managers using the same CCSID (coded character set id)?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| stanko |
| Posted: Mon May 26, 2008 4:55 am Post subject: |
|
|
Newbie
Joined: 22 May 2008
Posts: 5
|
Sorry for bothering you people again, but I don't have any idea what is happening.
So, as bruce suggested, I am sending you message printed with amqsbcg utility. I am testing it in our test enviroment, so OS's are Windows 2003 on both side CodedCharacterSetID is 852, on both side.
I could use amqsbcg utility only on a side which is receiving messages, since I am sending messages from a remote queue, on the side, from which I am sending message I get following messages:
AMQSBCG0 - starts here
**********************
MQOPEN - 'PROD'
MQOPEN failed with CompCode:2, Reason:2045
MQDISC
And on the side which is receiving messages, I received message:
AMQSBCG0 - starts here
**********************
MQOPEN - 'PROD'
MQGET of message number 1
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 6912 MsgType : 8
Expiry : -1 Feedback : 519
Encoding : 546 CodedCharSetId : 852
Format : 'MQSTR '
Priority : 0 Persistence : 0
MsgId : X'414D5120514D5F5452494E4554202020413DE94526E22002'
CorrelId : X'000000000000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : 'PROD '
ReplyToQMgr : 'TRINET '
** Identity Context
UserIdentifier : 'AMQSBCG0 - starts here
**********************
MQOPEN - 'PROD'
MQGET of message number 1
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 6912 MsgType : 8
Expiry : -1 Feedback : 519
Encoding : 546 CodedCharSetId : 852
Format : 'MQSTR '
Priority : 0 Persistence : 0
MsgId : X'414D5120514D5F5452494E4554202020413DE94526E22002'
CorrelId : X'000000000000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : 'PROD '
ReplyToQMgr : 'TRINET '
** Identity Context
UserIdentifier : 'mqzup002 '
AccountingToken :
X'0000000000000000000000000000000000000000000000000000000000000000'
ApplIdentityData : ' '
** Origin Context
PutApplType : '11'
PutApplName : 'here_Stanko\MQ\WebSphere.exe'
PutDate : '20070808' PutTime : '12401083'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 614 bytes
00000000: 3C3F 786D 6C20 7665 7273 696F 6E3D 2231 '<?xml version="1'
00000010: 2E30 2220 656E 636F 6469 6E67 3D22 7574 '.0" encoding="ut'
00000020: 662D 3822 3F3E 0D0A 3C4D 6573 7361 6765 'f-8"?>..<Message'
00000030: 3E0D 0A20 203C 4865 6164 6572 3E0D 0A20 '>.. <Header>.. '
00000040: 2020 203C 5265 6665 7265 6E63 613E 4145 ' <Referenca>AE'
00000050: 532D 3935 3731 3C2F 5265 6665 7265 6E63 'S-9571</Referenc'
00000060: 613E 0D0A 2020 2020 3C44 5350 7265 6A44 'a>.. <DSPrejD'
00000070: 727A 3E53 493C 2F44 5350 7265 6A44 727A 'rz>SI</DSPrejDrz'
00000080: 3E0D 0A20 2020 203C 4453 5072 656A 3E34 '>.. <DSPrej>4'
00000090: 3737 3330 3831 313C 2F44 5350 7265 6A3E '7730811</DSPrej>'
000000A0: 0D0A 2020 2020 3C4F 456E 5072 656A 3E31 '.. <OEnPrej>1'
000000B0: 3030 3C2F 4F45 6E50 7265 6A3E 0D0A 2020 '00</OEnPrej>.. '
000000C0: 2020 3C44 5350 6F73 4472 7A3E 5349 3C2F ' <DSPosDrz>SI</'
000000D0: 4453 506F 7344 727A 3E0D 0A20 2020 203C 'DSPosDrz>.. <'
000000E0: 4453 506F 733E 3531 3435 3433 3433 3C2F 'DSPos>51454343</'
000000F0: 4453 506F 733E 0D0A 2020 2020 3C4F 456E 'DSPos>.. <OEn'
00000100: 506F 733E 3630 303C 2F4F 456E 506F 733E 'Pos>600</OEnPos>'
00000110: 0D0A 2020 2020 3C54 6573 7449 6E64 696B '.. <TestIndik'
00000120: 6174 6F72 3E31 3C2F 5465 7374 496E 6469 'ator>1</TestIndi'
00000130: 6B61 746F 723E 0D0A 2020 2020 3C54 6970 'kator>.. <Tip'
00000140: 5370 3E58 4D4C 3C2F 5469 7053 703E 0D0A 'Sp>XML</TipSp>..'
00000150: 2020 2020 3C4F 7A44 6F6B 3E49 4535 3133 ' <OzDok>IE513'
00000160: 3C2F 4F7A 446F 6B3E 0D0A 2020 2020 3C44 '</OzDok>.. <D'
00000170: 6174 756D 3E32 3030 382D 3034 2D31 3454 'atum>2008-04-14T'
00000180: 3137 3A30 303A 3030 2E30 3030 2B30 323A '17:00:00.000+02:'
00000190: 3030 3C2F 4461 7475 6D3E 0D0A 2020 2020 '00</Datum>.. '
000001A0: 3C4B 7269 7074 6972 616E 6F3E 313C 2F4B '<Kriptirano>1</K'
000001B0: 7269 7074 6972 616E 6F3E 0D0A 2020 2020 'riptirano>.. '
000001C0: 3C42 7265 7A70 6170 6972 6E6F 3E31 3C2F '<Brezpapirno>1</'
000001D0: 4272 657A 7061 7069 726E 6F3E 0D0A 2020 'Brezpapirno>.. '
000001E0: 2020 3C50 7265 6A65 6D6E 696B 3E0D 0A20 ' <Prejemnik>.. '
000001F0: 2020 2020 203C 506F 7372 6564 6E69 6B3E ' <Posrednik>'
00000200: 5030 3032 3C2F 506F 7372 6564 6E69 6B3E 'P002</Posrednik>'
00000210: 0D0A 2020 2020 2020 3C4E 6173 6C6F 766E '.. <contact admin'
00000220: 696B 3E54 5249 4E45 5443 4152 3630 303C 'ik>TRINETCAR600<'
00000230: 2F4E 6173 6C6F 766E 696B 3E0D 0A20 2020 '/contact admin>.. '
00000240: 203C 2F50 7265 6A65 6D6E 696B 3E0D 0A20 ' </Prejemnik>.. '
00000250: 203C 2F48 6561 6465 723E 0D0A 3C2F 4D65 ' </Header>..</Me'
00000260: 7373 6167 653E 'ssage> '
MQGET of message number 2
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 4
Expiry : -1 Feedback : 259
Encoding : 546 CodedCharSetId : 852
Format : 'MQSTR '
Priority : 0 Persistence : 0
MsgId : X'414D51205452494E45542020202020205D151748217DC505'
CorrelId : X'414D5120514D5F5452494E4554202020413DE94526E22002'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'TRINET '
** Identity Context
UserIdentifier : 'mqzup002 '
AccountingToken :
X'0000000000000000000000000000000000000000000000000000000000000000'
ApplIdentityData : ' '
** Origin Context
PutApplType : '7'
PutApplName : 'TRINET '
PutDate : '20080526' PutTime : '12480570'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 100 bytes
00000000: 3C3F 786D 6C20 7665 7273 696F 6E3D 2231 '<?xml version="1'
00000010: 2E30 2220 656E 636F 6469 6E67 3D22 7574 '.0" encoding="ut'
00000020: 662D 3822 3F3E 0D0A 3C4D 6573 7361 6765 'f-8"?>..<Message'
00000030: 3E0D 0A20 203C 4865 6164 6572 3E0D 0A20 '>.. <Header>.. '
00000040: 2020 203C 5265 6665 7265 6E63 613E 4145 ' <Referenca>AE'
00000050: 532D 3935 3731 3C2F 5265 6665 7265 6E63 'S-9571</Referenc'
00000060: 613E 0D0A 'a>.. '
No more messages
MQCLOSE
MQDISC'
AccountingToken :
X'0000000000000000000000000000000000000000000000000000000000000000'
ApplIdentityData : ' '
** Origin Context
PutApplType : '11'
PutApplName : 'here_Stanko\MQ\WebSphere.exe'
PutDate : '20070808' PutTime : '12401083'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 614 bytes
00000000: 3C3F 786D 6C20 7665 7273 696F 6E3D 2231 '<?xml version="1'
00000010: 2E30 2220 656E 636F 6469 6E67 3D22 7574 '.0" encoding="ut'
00000020: 662D 3822 3F3E 0D0A 3C4D 6573 7361 6765 'f-8"?>..<Message'
00000030: 3E0D 0A20 203C 4865 6164 6572 3E0D 0A20 '>.. <Header>.. '
00000040: 2020 203C 5265 6665 7265 6E63 613E 4145 ' <Referenca>AE'
00000050: 532D 3935 3731 3C2F 5265 6665 7265 6E63 'S-9571</Referenc'
00000060: 613E 0D0A 2020 2020 3C44 5350 7265 6A44 'a>.. <DSPrejD'
00000070: 727A 3E53 493C 2F44 5350 7265 6A44 727A 'rz>SI</DSPrejDrz'
00000080: 3E0D 0A20 2020 203C 4453 5072 656A 3E34 '>.. <DSPrej>4'
00000090: 3737 3330 3831 313C 2F44 5350 7265 6A3E '7730811</DSPrej>'
000000A0: 0D0A 2020 2020 3C4F 456E 5072 656A 3E31 '.. <OEnPrej>1'
000000B0: 3030 3C2F 4F45 6E50 7265 6A3E 0D0A 2020 '00</OEnPrej>.. '
000000C0: 2020 3C44 5350 6F73 4472 7A3E 5349 3C2F ' <DSPosDrz>SI</'
000000D0: 4453 506F 7344 727A 3E0D 0A20 2020 203C 'DSPosDrz>.. <'
000000E0: 4453 506F 733E 3531 3435 3433 3433 3C2F 'DSPos>51454343</'
000000F0: 4453 506F 733E 0D0A 2020 2020 3C4F 456E 'DSPos>.. <OEn'
00000100: 506F 733E 3630 303C 2F4F 456E 506F 733E 'Pos>600</OEnPos>'
00000110: 0D0A 2020 2020 3C54 6573 7449 6E64 696B '.. <TestIndik'
00000120: 6174 6F72 3E31 3C2F 5465 7374 496E 6469 'ator>1</TestIndi'
00000130: 6B61 746F 723E 0D0A 2020 2020 3C54 6970 'kator>.. <Tip'
00000140: 5370 3E58 4D4C 3C2F 5469 7053 703E 0D0A 'Sp>XML</TipSp>..'
00000150: 2020 2020 3C4F 7A44 6F6B 3E49 4535 3133 ' <OzDok>IE513'
00000160: 3C2F 4F7A 446F 6B3E 0D0A 2020 2020 3C44 '</OzDok>.. <D'
00000170: 6174 756D 3E32 3030 382D 3034 2D31 3454 'atum>2008-04-14T'
00000180: 3137 3A30 303A 3030 2E30 3030 2B30 323A '17:00:00.000+02:'
00000190: 3030 3C2F 4461 7475 6D3E 0D0A 2020 2020 '00</Datum>.. '
000001A0: 3C4B 7269 7074 6972 616E 6F3E 313C 2F4B '<Kriptirano>1</K'
000001B0: 7269 7074 6972 616E 6F3E 0D0A 2020 2020 'riptirano>.. '
000001C0: 3C42 7265 7A70 6170 6972 6E6F 3E31 3C2F '<Brezpapirno>1</'
000001D0: 4272 657A 7061 7069 726E 6F3E 0D0A 2020 'Brezpapirno>.. '
000001E0: 2020 3C50 7265 6A65 6D6E 696B 3E0D 0A20 ' <Prejemnik>.. '
000001F0: 2020 2020 203C 506F 7372 6564 6E69 6B3E ' <Posrednik>'
00000200: 5030 3032 3C2F 506F 7372 6564 6E69 6B3E 'P002</Posrednik>'
00000210: 0D0A 2020 2020 2020 3C4E 6173 6C6F 766E '.. <contact admin'
00000220: 696B 3E54 5249 4E45 5443 4152 3630 303C 'ik>TRINETCAR600<'
00000230: 2F4E 6173 6C6F 766E 696B 3E0D 0A20 2020 '/contact admin>.. '
00000240: 203C 2F50 7265 6A65 6D6E 696B 3E0D 0A20 ' </Prejemnik>.. '
00000250: 203C 2F48 6561 6465 723E 0D0A 3C2F 4D65 ' </Header>..</Me'
00000260: 7373 6167 653E 'ssage> '
MQGET of message number 2
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 4
Expiry : -1 Feedback : 259
Encoding : 546 CodedCharSetId : 852
Format : 'MQSTR '
Priority : 0 Persistence : 0
MsgId : X'414D51205452494E45542020202020205D151748217DC505'
CorrelId : X'414D5120514D5F5452494E4554202020413DE94526E22002'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'TRINET '
** Identity Context
UserIdentifier : 'mqzup002 '
AccountingToken :
X'0000000000000000000000000000000000000000000000000000000000000000'
ApplIdentityData : ' '
** Origin Context
PutApplType : '7'
PutApplName : 'TRINET '
PutDate : '20080526' PutTime : '12480570'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 100 bytes
00000000: 3C3F 786D 6C20 7665 7273 696F 6E3D 2231 '<?xml version="1'
00000010: 2E30 2220 656E 636F 6469 6E67 3D22 7574 '.0" encoding="ut'
00000020: 662D 3822 3F3E 0D0A 3C4D 6573 7361 6765 'f-8"?>..<Message'
00000030: 3E0D 0A20 203C 4865 6164 6572 3E0D 0A20 '>.. <Header>.. '
00000040: 2020 203C 5265 6665 7265 6E63 613E 4145 ' <Referenca>AE'
00000050: 532D 3935 3731 3C2F 5265 6665 7265 6E63 'S-9571</Referenc'
00000060: 613E 0D0A 'a>.. '
No more messages
MQCLOSE
MQDISC
mqzup002 - this is user name which should be in upper case. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon May 26, 2008 6:12 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| UserIdentifier : 'mqzup002 ' |
The userid is in lower-case. If your application needs it to be in upper-case, the application programmer must convert it to upper-case - either on the sending side OR the receiving side. This is easily done programatically.
Recall that the userid is taken from the operating system's security manager. So, I'd guess that mqzup002 is your Windows username. Try creating an upper-case Windows username; then do the same test again.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon May 26, 2008 6:25 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
|
| Back to top |
|
|
| stanko |
| Posted: Mon May 26, 2008 6:52 am Post subject: |
|
|
Newbie
Joined: 22 May 2008
Posts: 5
|
Thank you.
 |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon May 26, 2008 7:44 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| I could use amqsbcg utility only on a side which is receiving messages, since I am sending messages ... |
I am confused.
Is your application sending REQUEST messages? Or is you application sending REPLY messages back to the requesting application?
You posted DATAGRAM message (msgtype: 8 ) and REPORT message (msgtype: 4) .
If your application is creating and sending a REQUEST message, please post it here. If your application is the REPLYing application, I'd expect to see a REPLY (msgtype: 2) and one or more REPORT (msgtype: 4 ) ; but no DATAGRAMs (msgtype: 8 ).
| Quote: |
| It is windows 2003 server, receiving platform is Unix. |
Is the REQUESTing application running on Windows 2003? Is that your end? Is the REPLYing application running on UNIX? Please be specific here.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue May 27, 2008 10:58 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| jefflowrey wrote: |
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/topic/com.ibm.mq.csqzae.doc/ic12640_.htm
 |
That's rather explicit. Yet I have an UPPERCASE MCAUSER defined on one of my SVRCONN channels on a Linux Queue Manager. This was needed a couple of years ago so the messages leaving this QM going to a mainframe QM would arrive at that MF QM with an uppercase ID in the MQMD, to satisfy RACF. The setmqaut commands were run against a lowercase group ID though.
Kinda intersting. Distributed to distributed the lowercase ID is found when the message is on the local queue. But if you send from distributed to mainframe, the lowercase ID is rolled up to uppercase whe the message is placed on the local MF queue.
The reason for the uppercase ID on my Linux QM was related to some bug I think in the early versions of the Linux MQ 6.0 code (6.0.1.0 or early maybe?) that was causing the ID to arrive in lower case on the MF queue.
Wish I could find something in the info center that explains why the lower case IDs are turned into uppercase IDs if the destination queue is a mainframe queue....
All I found was this, and it only talks about is non mainframe scenarios:
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/topic/com.ibm.mq.csqzae.doc/ic12680_.htm?resultof=%22%75%70%70%65%72%63%61%73%65%22%20%22%75%70%70%65%72%63%61%73%22%20
If you read between the lines maybe its implying that a non Unix / Windows RCVR channel will not conver the ID back to lower case?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue May 27, 2008 11:50 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| But if you send from distributed to mainframe, the lowercase ID is rolled up to uppercase ... |
This has not been my experience.
A lower-case userid in the MQMD arrives on WMQ z/OS in lower-case.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
