Author |
Message
|
vmcgloin |
Posted: Wed Apr 29, 2009 3:07 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002 Posts: 560 Location: Scotland
|
Hello!
Not my problem now... I have other things to deal with... but I hope you will be raising the requirement.
Does that response also apply to the ability to set the server directory dynamically via the environment tree using ESQL? I hope you include that in your requirement too since I believe that is a separate issue - and would be most useful.
Cheers,
Vicky |
|
Back to top |
|
 |
mqpaul |
Posted: Fri May 01, 2009 5:47 am Post subject: You can set the server directory in configurable service |
|
|
 Acolyte
Joined: 14 Jan 2008 Posts: 66 Location: Hursley, UK
|
The configurable service definition for the FTP server includes the remoteDirectory property. You can use that instead of a configurable property on the flow to configure the server directory.
It doesn't help with setting the server directory dynamically from LocalEnvironment, of course. _________________ Paul |
|
Back to top |
|
 |
mvs |
Posted: Thu Aug 27, 2009 10:18 am Post subject: |
|
|
Voyager
Joined: 06 Jul 2007 Posts: 85
|
Hi All,
I have the same requirement. to transfer message into the file and placing to the Z/OS (Main Frame).
The broker runs on Aix.
-----------------------------------------------------------------
My flow looks like below
Input Node-------->ComputeNode-----FileoutputNode
In computer node
SET OutputRoot.XML.Test1= 'TestMsg';
[color=green]-- SET outputLocalEnvironment.Destination.File.Directory = ''TSOHRBB.';
SET OutputLocalEnvironment.Destination.File.Name = 'TSOHRBB.E002385.Sample123';
the properties of FileoutputNode
Basic tab: Directory name : wrongDir
File Name : WrongFile
Request tab: defualt properties
Records and Elements Tab: defualt properties
FTP table: RemoteTransfer checked
server or host: mvshost2
security idenetity: mfconn
ServerDirectory: tried different options
transfermode: binary
-----------------------------------------------------------------[/color]
I am doing the below in FTP
-----------
C:\>ftp mvshost2
Connected to mvshost2.btmna.com.
220-FTPD1 IBM FTP CS V1R8 at MVSHOST2.BTMNA.COM, 18:04:00 on 2009-08-27.
220 Connection will close if idle for more than 10 minutes.
User (mvshost2.btmna.com:(none)): e002385
331 Send password please.
Password:
230 E002385 is logged on. Working directory is "E002385.".
ftp> put samy.txt 'TSOHRBB.E002385.samy.txt'
200 Port request OK.
125 Storing data set TSOHRBB.E002385.SAMY.TXT
250 Transfer completed successfully.
ftp: 14 bytes sent in 0.00Seconds 14000.00Kbytes/sec.
ftp>
-----------
I am trying the same way as mentioned MQpaul and vmcgloin in their post.
Server Directory; //TSOHRBB this i am setting Filoutput node directory
SET OutputLocalEnvironment.Destination.File.Directory = '.';
SET OutputLocalEnvironment.Destination.File.Name = 'E002385.Sample123';
i am getting the below exception
-------
2009-08-27 13:09:21.513628 7264 RecoverableException BIP2230E: Error detected whilst processing a message in node 'EGTW_FTP.FileOutput'.
The message broker detected an error whilst processing a message in node 'EGTW_FTP.FileOutput'. An exception has been
thrown to cut short the processing of the message.
See the following messages for details of the error.
2009-08-27 13:09:21.513642 7264 RecoverableException BIP3333E: The File node ''FileOutput'' in message flow ''EGTW_FTP'' cannot resolve the relative f
ile path ''.''.
Relative file paths are resolved by using the absolute directory path in the 'MQSI_FILENODES_ROOT_DIRECTORY' environme
nt variable.
This environment variable is not set correctly and cannot be used to resolve the path.
Either ensure that the 'MQSI_FILENODES_ROOT_DIRECTORY' environment variable contains an absolute directory path and th
at the directory exists and can be accessed by the broker, or change the node configuration to use absolute directory paths.
See the WebSphere Message Brokers online documentation topic "FileInput node" or "FileOutput node" for more informati
on.
-------Another combination
Server Directory; //TSOHRBB this i am setting Filoutput node directory
--SET OutputLocalEnvironment.Destination.File.Directory = '';
SET OutputLocalEnvironment.Destination.File.Name = 'E002385.Sample123';
------------
2009-08-27 13:44:13.936378 3690 RecoverableException BIP3325E: File node ''FileOutput'' in message flow ''EGTW_FTP'' cannot use the directory ''null''
for file name ''TSOHRBB.E002385.Sample123''.
The file node cannot create the directory or cannot move a file into or out of the directory with that name.
Ensure that the file and directory names are correctly specified in the message flow. The names may contain invalid ch
aracters or the directory may be ineligible for use, or the broker may not have the authority to perform the action required. See the WebSphere Message Broke
rs online documentation sections "FileInput node" and "FileOutput node" for more information.
2009
---------
Can u help me where i am doing mistake? |
|
Back to top |
|
 |
vmcgloin |
Posted: Mon Aug 31, 2009 3:27 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002 Posts: 560 Location: Scotland
|
Maybe try this?
SET OutputLocalEnvironment.Destination.File.Directory = '//TSOHRBB';
SET OutputLocalEnvironment.Destination.File.Name = 'E002385.Sample123'; |
|
Back to top |
|
 |
mvs |
Posted: Thu Sep 10, 2009 11:09 am Post subject: |
|
|
Voyager
Joined: 06 Jul 2007 Posts: 85
|
All,
I opened PMR with IBM and they suggested below, now its working.
=====================
1. The FileOutputNode writes the file locally, so in this case, to the
unix file system.
The file is written to the location specified by the Basic: Directory
property of the FileOutputNode, or overwritten by the variable,
OutputLocalEnvironment.Destination.File.Directory.
2. The FileOoutputNode FTPs the file from the local system to the remote
FTP site.
The file is transferred to the directory on the FTP server specified by
the FTP: Server directory property of the FileOutputNode.
SET OutputLocalEnvironment.Destination.File.Directory = ''/tmp.';
SET OutputLocalEnvironment.Destination.File.Name = 'E002385.SAMPLE123.TXT'
and set the FileOutputNode FTP: Server directory property = //TSOHRBB
============
I was confused while specifying the Directory of the Basic tab of FileOutput node or OutputLocalEnvironment.Destination.File.Directory. i was giving main frame(or Z/OS) path instead of unix path.
Thanks and Regards
MVS |
|
Back to top |
|
 |
jhurilla |
Posted: Mon Jun 07, 2010 11:21 pm Post subject: |
|
|
Newbie
Joined: 01 Jun 2010 Posts: 1
|
How to change meta title, descriptions and keywords for an FTP? I'm updating the meta data for a website, but need to know how to change it on the ftp. The company that designed the website sent me the ftp file folder for the website they originally designed. Do I have to rewrite the html code, inserting the new meta data, and then upload it?
___________________
affiliateelite ~ affiliateelite.com ~ adgooroo ~ adgooroo.com
Last edited by jhurilla on Fri Jun 11, 2010 1:36 am; edited 1 time in total |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Jun 08, 2010 2:08 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
jhurilla wrote: |
How to change meta title, descriptions and keywords for an FTP? I'm updating the meta data for a website, but need to know how to change it on the ftp. The company that designed the website sent me the ftp file folder for the website they originally designed. Do I have to rewrite the html code, inserting the new meta data, and then upload it? |
The FTP standard includes no definition of "meta data".
Nobody can help you with this problem the way you have described it.
And this problem has *nothing* to do with using Message Broker, nor even with using the FileOutput node in Message Broker to send data over FTP. |
|
Back to top |
|
 |
|