| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| CDOutput node - SYSOPT Issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| pradeep3j |
 Posted: Mon Feb 11, 2019 6:12 pm Post subject: CDOutput node - SYSOPT Issue |
 |
|
Newbie
Joined: 11 Feb 2019
Posts: 5
|
Hi, I am trying to use CDOutput node in IIB10 to send PDF file from Linux over connect direct to remote Windows machine. The connect direct agent is throwing an error as "Invalid Sysopt". I tried setting up the SYSOPT to "datatype(binary)" as its used for windows but this doesn't seem to be working. I tried as below. Can anyone please help me that how to set SYSOPT option correctly in IIB10?
OutputLocalEnvironment.Destination.CD.Copy.To = 'Datatype(binary)'; |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Feb 12, 2019 6:57 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
What exactly in the issue here? You've posted 3 times today (and welcome aboard by the way) with various variations of a CD problem.
You've claimed that the SYSOPS gets duplicated on a thread talking about distributed to mainframe, which you're not doing.
You've claimed invalid SYSOPS on a thread which couldn't set it
You've claimed invalid SYSOPS in this thread but posted a different ESQL line you claim to be using to set the SYSOPS up.
SO:
- what are you attempting
- what code are you using
- what is the content on the LocalEnvironment when you do this
- what is the error
- why are you shotgunning questions round this forum
Better information, better advice.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Feb 12, 2019 9:17 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Vitor wrote: |
What exactly in the issue here? You've posted 3 times today (and welcome aboard by the way) with various variations of a CD problem.
You've claimed that the SYSOPS gets duplicated on a thread talking about distributed to mainframe, which you're not doing.
You've claimed invalid SYSOPS on a thread which couldn't set it
You've claimed invalid SYSOPS in this thread but posted a different ESQL line you claim to be using to set the SYSOPS up.
SO:
- what are you attempting
- what code are you using
- what is the content on the LocalEnvironment when you do this
- what is the error
- why are you shotgunning questions round this forum
Better information, better advice. |
Should be a lot easier... instead of creating your .cd file on the fly, create a static one that you submit overriding the file parameter. That should work like wonders for you... like
| Code: |
| submit file=/pathtoCDfile.cd inputfile=myinputfile (parm for inputfile) |
So your sysopts can contain all you need and be defined in the .cd file...
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
