I have a flat file in mainframe (not mainframe database), i have to create
XML for each flat file and show the xml on the web using XML and XSL.
Any bright ideas.
Thanks in advance
Printable View
I have a flat file in mainframe (not mainframe database), i have to create
XML for each flat file and show the xml on the web using XML and XSL.
Any bright ideas.
Thanks in advance
"Gee" <grajput@slk.com> wrote:
>
>I have a flat file in mainframe (not mainframe database), i have to create
>XML for each flat file and show the xml on the web using XML and XSL.
>
>Any bright ideas.
>
>Thanks in advance
>
Not sure if this will help, but XML Spy 3.5 includes a text import dialog
(I've used it often - nice feature). You have the capability to identify
the delimiters (comma, semicolon, tab, space) and whether the text was encapsulated
within quotes, apostrophes.
If you are looking for something to automate the process, I am unsure if
XML Spy exposes their technology via an API or not. You could take a look
(XML Spy by Altova).
If I remember correctly Data Junction also provides extensive conversion
capabilities from/to XML. Great tool.
Also, are you considering character encoding/exchange (i.e. is this an EBCDIC
or ASCII file ?). That could add a slight character conversion twist.
I'm doing this with data on As/400. I'm doing this a few different ways but
I will give you a quick run down on how it works.
I'm using a RPG compiler (or Visual Basic) to create a DLL that will connect
to an As/400 and read the files. Using the RPG code I create the XML stream
that I need to recieve as one large string and set it equal to a property
of the dll class. I then access the dll's class property inside my ASP and
ASP.Net pages to get the XML stream. I then use XSL to convert the XML into
my clients viewable web page via VB code in the ASP page.
The method you choose will depend on how your connecting to the mainframe
and how you are passing the XML data back to your web pages. There are a
few ways I could have handled.
Email me if you would like additional information about what I've been able
to do on the As/400.
"Gee" <grajput@slk.com> wrote:
>
>I have a flat file in mainframe (not mainframe database), i have to create
>XML for each flat file and show the xml on the web using XML and XSL.
>
>Any bright ideas.
>
>Thanks in advance
>
Can i read only a particular portion of the flat file, so that i don't have
to get the whole file as a stream.
The reason is the flat files are huge reports and i mean very huge.
The user don't need the whole report he will query a particular part of the
report and i need to show that part in XML.
If i get the whole report it will consume lot of memory on my side.
lemme know how to access mainframe using VB.
Thanks
"Greg Rothlander" <grothlander@austin400.com> wrote:
>
>I'm doing this with data on As/400. I'm doing this a few different ways
but
>I will give you a quick run down on how it works.
>
>I'm using a RPG compiler (or Visual Basic) to create a DLL that will connect
>to an As/400 and read the files. Using the RPG code I create the XML stream
>that I need to recieve as one large string and set it equal to a property
>of the dll class. I then access the dll's class property inside my ASP
and
>ASP.Net pages to get the XML stream. I then use XSL to convert the XML
into
>my clients viewable web page via VB code in the ASP page.
>
>The method you choose will depend on how your connecting to the mainframe
>and how you are passing the XML data back to your web pages. There are
a
>few ways I could have handled.
>
>Email me if you would like additional information about what I've been able
>to do on the As/400.
>
>
>"Gee" <grajput@slk.com> wrote:
>>
>>I have a flat file in mainframe (not mainframe database), i have to create
>>XML for each flat file and show the xml on the web using XML and XSL.
>>
>>Any bright ideas.
>>
>>Thanks in advance
>>
>
Do you know XML Convert from www.unidex.com ? I think that this tool can convert
huge flat files into XML...
"Gee" <grajput@slk.com> wrote:
>
>Can i read only a particular portion of the flat file, so that i don't have
>to get the whole file as a stream.
>The reason is the flat files are huge reports and i mean very huge.
>The user don't need the whole report he will query a particular part of
the
>report and i need to show that part in XML.
>If i get the whole report it will consume lot of memory on my side.
>lemme know how to access mainframe using VB.
>
>Thanks
>
>"Greg Rothlander" <grothlander@austin400.com> wrote:
>>
>>I'm doing this with data on As/400. I'm doing this a few different ways
>but
>>I will give you a quick run down on how it works.
>>
>>I'm using a RPG compiler (or Visual Basic) to create a DLL that will connect
>>to an As/400 and read the files. Using the RPG code I create the XML stream
>>that I need to recieve as one large string and set it equal to a property
>>of the dll class. I then access the dll's class property inside my ASP
>and
>>ASP.Net pages to get the XML stream. I then use XSL to convert the XML
>into
>>my clients viewable web page via VB code in the ASP page.
>>
>>The method you choose will depend on how your connecting to the mainframe
>>and how you are passing the XML data back to your web pages. There are
>a
>>few ways I could have handled.
>>
>>Email me if you would like additional information about what I've been
able
>>to do on the As/400.
>>
>>
>>"Gee" <grajput@slk.com> wrote:
>>>
>>>I have a flat file in mainframe (not mainframe database), i have to create
>>>XML for each flat file and show the xml on the web using XML and XSL.
>>>
>>>Any bright ideas.
>>>
>>>Thanks in advance
>>>
>>
>
If you are looking for a server based solution, check out Whitehill <xml>Transport.
You can download an image of their demo CD at http://www.whitehill.com/products/prod3.html.
They also have a drag and drop XSL generator called Whitehill <xsl>Composer
that may help you will creating your stylesheets. (http://www.whitehill.com/products/prod4.html)
J
"Gee" <grajput@slk.com> wrote:
>
>I have a flat file in mainframe (not mainframe database), i have to create
>XML for each flat file and show the xml on the web using XML and XSL.
>
>Any bright ideas.
>
>Thanks in advance
>
Sorry for the delay. I didn't see your reponse last week.
I'm not sure about what your doing on the mainframe side. As far as what
you pass back in XML would depend on what your doing on the mainframe side.
What I'm doing...
I'm using programs that I write on the As/400 to generate the XML stream.
I'm manually going through the file looking for what I want. Then I build
a large XML stream that I create within my As/400 code. Something like:
xmlstream = "<zipcode>" + CZIPIC + "</zipcode>"
I'm doing this on the As/400 and then sending a string back to my Web Server
and use an ASP/ASPX page to load the XML and XSL and transform it. I'm able
to call the As/400 program via the ASP page, create the XML stream using
code on the mainframe, and then pass back the XML Stream to the ASP page.
This may not be a recommended way to do it but it's the only way I've found
that really works with the mainframe. As far has handling the flat file,
well that would depend on what you are doing to get the data out of the file
and into whatever it is your passing back as a XML stream.
I can do the same thing via VB using a demo OLEDB control I got from Hit
Software. I think the page is www.hit.com. It's can be costly because of
lisencing issues but in my environment I just pass the cost onto the clients.
If you already have a ODBC or OLEDB connection to your mainframe then you
should be able to use it to pass a string between the Web Server and your
mainframe.
There are so many options depending on exactly what you are doing that it's
hard to offer information. This is just one of many, many was to handle
this sort of stuff.
"Gee" <grajput@slk.com> wrote:
>
>Can i read only a particular portion of the flat file, so that i don't have
>to get the whole file as a stream.
>The reason is the flat files are huge reports and i mean very huge.
>The user don't need the whole report he will query a particular part of
the
>report and i need to show that part in XML.
>If i get the whole report it will consume lot of memory on my side.
>lemme know how to access mainframe using VB.
>
>Thanks
>
>"Greg Rothlander" <grothlander@austin400.com> wrote:
>>
>>I'm doing this with data on As/400. I'm doing this a few different ways
>but
>>I will give you a quick run down on how it works.
>>
>>I'm using a RPG compiler (or Visual Basic) to create a DLL that will connect
>>to an As/400 and read the files. Using the RPG code I create the XML stream
>>that I need to recieve as one large string and set it equal to a property
>>of the dll class. I then access the dll's class property inside my ASP
>and
>>ASP.Net pages to get the XML stream. I then use XSL to convert the XML
>into
>>my clients viewable web page via VB code in the ASP page.
>>
>>The method you choose will depend on how your connecting to the mainframe
>>and how you are passing the XML data back to your web pages. There are
>a
>>few ways I could have handled.
>>
>>Email me if you would like additional information about what I've been
able
>>to do on the As/400.
>>
>>
>>"Gee" <grajput@slk.com> wrote:
>>>
>>>I have a flat file in mainframe (not mainframe database), i have to create
>>>XML for each flat file and show the xml on the web using XML and XSL.
>>>
>>>Any bright ideas.
>>>
>>>Thanks in advance
>>>
>>
>
How are u connecting to Mainframe from ASP/VB?
"Greg Rothlander" <grothlander@austin400.com> wrote:
>
>Sorry for the delay. I didn't see your reponse last week.
>
>I'm not sure about what your doing on the mainframe side. As far as what
>you pass back in XML would depend on what your doing on the mainframe side.
>
>
>What I'm doing...
> I'm using programs that I write on the As/400 to generate the XML stream.
> I'm manually going through the file looking for what I want. Then I build
>a large XML stream that I create within my As/400 code. Something like:
> xmlstream = "<zipcode>" + CZIPIC + "</zipcode>"
>
>I'm doing this on the As/400 and then sending a string back to my Web Server
>and use an ASP/ASPX page to load the XML and XSL and transform it. I'm
able
>to call the As/400 program via the ASP page, create the XML stream using
>code on the mainframe, and then pass back the XML Stream to the ASP page.
>
>
>This may not be a recommended way to do it but it's the only way I've found
>that really works with the mainframe. As far has handling the flat file,
>well that would depend on what you are doing to get the data out of the
file
>and into whatever it is your passing back as a XML stream.
>
>I can do the same thing via VB using a demo OLEDB control I got from Hit
>Software. I think the page is www.hit.com. It's can be costly because
of
>lisencing issues but in my environment I just pass the cost onto the clients.
> If you already have a ODBC or OLEDB connection to your mainframe then you
>should be able to use it to pass a string between the Web Server and your
>mainframe.
>
>There are so many options depending on exactly what you are doing that it's
>hard to offer information. This is just one of many, many was to handle
>this sort of stuff.
>
>
>
>
>
>
>"Gee" <grajput@slk.com> wrote:
>>
>>Can i read only a particular portion of the flat file, so that i don't
have
>>to get the whole file as a stream.
>>The reason is the flat files are huge reports and i mean very huge.
>>The user don't need the whole report he will query a particular part of
>the
>>report and i need to show that part in XML.
>>If i get the whole report it will consume lot of memory on my side.
>>lemme know how to access mainframe using VB.
>>
>>Thanks
>>
>>"Greg Rothlander" <grothlander@austin400.com> wrote:
>>>
>>>I'm doing this with data on As/400. I'm doing this a few different ways
>>but
>>>I will give you a quick run down on how it works.
>>>
>>>I'm using a RPG compiler (or Visual Basic) to create a DLL that will connect
>>>to an As/400 and read the files. Using the RPG code I create the XML
stream
>>>that I need to recieve as one large string and set it equal to a property
>>>of the dll class. I then access the dll's class property inside my ASP
>>and
>>>ASP.Net pages to get the XML stream. I then use XSL to convert the XML
>>into
>>>my clients viewable web page via VB code in the ASP page.
>>>
>>>The method you choose will depend on how your connecting to the mainframe
>>>and how you are passing the XML data back to your web pages. There are
>>a
>>>few ways I could have handled.
>>>
>>>Email me if you would like additional information about what I've been
>able
>>>to do on the As/400.
>>>
>>>
>>>"Gee" <grajput@slk.com> wrote:
>>>>
>>>>I have a flat file in mainframe (not mainframe database), i have to create
>>>>XML for each flat file and show the xml on the web using XML and XSL.
>>>>
>>>>Any bright ideas.
>>>>
>>>>Thanks in advance
>>>>
>>>
>>
>
Let me make sure I'm know what you mean by a flat file. I've always referred
to flat files as files that are stand alone, without keys, and without fields.
You have to read the file starting at the beginning and you have to pull
your fields out based on character positions. I think this is what you are
working with because I think you said they were reports. If this is the
case then you are doing something that is a little bit different then what
I was doing with VB/ASP. I think you can still do this but your gonna have
to take a few extra steps that I did not have to. If I need to access a
flat file then I use the AVR-RPG compiler I mentioned in previous posts.
I create a dll using this compiler and call the dll in my VB or ASP applications.
I create and pass an XML Stream from the AVR-RPG compiler to my ASP applications
and then transform it using a XSL file.
But as far as what I'm doing with VB/ASP... I'm actually using either HTML,
ASP, or ASP.Net to transform XML Streams via XSL. I can use any of these
to get the same results depending on what the client wants.
I've been playing around with some OLEDB connections for the As/400 and built
a Systems Administrators Utility using an ActiveX DLL Document. The work
I was doing didn't use a flat file but I was able to use a flat file for
some of my testing and playing with how the control works.
The code I use to pull from As/400 physical and logical files looks like
this:
strSQLString "Select * from tablename"
'set connection to as/400
strConn = "Provider=HitOLEDB400;Password=admin;User ID=sa;Data Source=123.123.123.123;...etc...."
Set Cn = New ADODB.Connection
Set Rs = New ADODB.Recordset
Cn.Open strConn
Rc.CuresorLocation = adUserServer
Rc.Open strSQLString, Cn, adOpenKeyset, adLockOptimistic
SQLConnect = True
This actually returns a recordset from the As/400 and you can update, deleted,
modify, etc... just like you would in SQLServer or Access. I thought it
was pretty neat.
The Hit control does allow you to use command line access to run programs
on the mainframe. Then you can access the results of the run... which in
your case would probably be strings that your program created. I'm not sure
exactly how this should be done using VB but the Hit people can probably
tell you what you need to do.
There are a number of these OLEDB and ODBC controls and the best one that
I've got to work is from Hit Software. The only bad thing about buying these
controls is the cost. For just a single connection then it's pretty cheap,
but if you want thousands of connections via the internet at the same time...
then it gets pretty high.
If your wanting to use VB to access flat files on the mainframe then you
should be able to do this via the Hit Control but I have not played with
this in VB. If you are hitting an As/400 then AVR-RPG can access the flat
file. You can create a dll using the AVR-RPG product that you can call from
an VB or ASP application. Then just pass the data you need through the dll
to the VB/ASP application.
"Gee" <grajput@slk.com> wrote:
>
>How are u connecting to Mainframe from ASP/VB?
>
>"Greg Rothlander" <grothlander@austin400.com> wrote:
>>
>>Sorry for the delay. I didn't see your reponse last week.
>>
>>I'm not sure about what your doing on the mainframe side. As far as what
>>you pass back in XML would depend on what your doing on the mainframe side.
>>
>>
>>What I'm doing...
>> I'm using programs that I write on the As/400 to generate the XML stream.
>> I'm manually going through the file looking for what I want. Then I build
>>a large XML stream that I create within my As/400 code. Something like:
>> xmlstream = "<zipcode>" + CZIPIC + "</zipcode>"
>>
>>I'm doing this on the As/400 and then sending a string back to my Web Server
>>and use an ASP/ASPX page to load the XML and XSL and transform it. I'm
>able
>>to call the As/400 program via the ASP page, create the XML stream using
>>code on the mainframe, and then pass back the XML Stream to the ASP page.
>>
>>
>>This may not be a recommended way to do it but it's the only way I've found
>>that really works with the mainframe. As far has handling the flat file,
>>well that would depend on what you are doing to get the data out of the
>file
>>and into whatever it is your passing back as a XML stream.
>>
>>I can do the same thing via VB using a demo OLEDB control I got from Hit
>>Software. I think the page is www.hit.com. It's can be costly because
>of
>>lisencing issues but in my environment I just pass the cost onto the clients.
>> If you already have a ODBC or OLEDB connection to your mainframe then
you
>>should be able to use it to pass a string between the Web Server and your
>>mainframe.
>>
>>There are so many options depending on exactly what you are doing that
it's
>>hard to offer information. This is just one of many, many was to handle
>>this sort of stuff.
>>
>>
>>
>>
>>
>>
>>"Gee" <grajput@slk.com> wrote:
>>>
>>>Can i read only a particular portion of the flat file, so that i don't
>have
>>>to get the whole file as a stream.
>>>The reason is the flat files are huge reports and i mean very huge.
>>>The user don't need the whole report he will query a particular part of
>>the
>>>report and i need to show that part in XML.
>>>If i get the whole report it will consume lot of memory on my side.
>>>lemme know how to access mainframe using VB.
>>>
>>>Thanks
>>>
>>>"Greg Rothlander" <grothlander@austin400.com> wrote:
>>>>
>>>>I'm doing this with data on As/400. I'm doing this a few different ways
>>>but
>>>>I will give you a quick run down on how it works.
>>>>
>>>>I'm using a RPG compiler (or Visual Basic) to create a DLL that will
connect
>>>>to an As/400 and read the files. Using the RPG code I create the XML
>stream
>>>>that I need to recieve as one large string and set it equal to a property
>>>>of the dll class. I then access the dll's class property inside my ASP
>>>and
>>>>ASP.Net pages to get the XML stream. I then use XSL to convert the XML
>>>into
>>>>my clients viewable web page via VB code in the ASP page.
>>>>
>>>>The method you choose will depend on how your connecting to the mainframe
>>>>and how you are passing the XML data back to your web pages. There are
>>>a
>>>>few ways I could have handled.
>>>>
>>>>Email me if you would like additional information about what I've been
>>able
>>>>to do on the As/400.
>>>>
>>>>
>>>>"Gee" <grajput@slk.com> wrote:
>>>>>
>>>>>I have a flat file in mainframe (not mainframe database), i have to
create
>>>>>XML for each flat file and show the xml on the web using XML and XSL.
>>>>>
>>>>>Any bright ideas.
>>>>>
>>>>>Thanks in advance
>>>>>
>>>>
>>>
>>
>
Thanks for your help.
"Greg Rothlander" <grothlander@austin400.com> wrote:
>
>Let me make sure I'm know what you mean by a flat file. I've always referred
>to flat files as files that are stand alone, without keys, and without fields.
> You have to read the file starting at the beginning and you have to pull
>your fields out based on character positions. I think this is what you
are
>working with because I think you said they were reports. If this is the
>case then you are doing something that is a little bit different then what
>I was doing with VB/ASP. I think you can still do this but your gonna have
>to take a few extra steps that I did not have to. If I need to access a
>flat file then I use the AVR-RPG compiler I mentioned in previous posts.
> I create a dll using this compiler and call the dll in my VB or ASP applications.
> I create and pass an XML Stream from the AVR-RPG compiler to my ASP applications
>and then transform it using a XSL file.
>
>But as far as what I'm doing with VB/ASP... I'm actually using either HTML,
>ASP, or ASP.Net to transform XML Streams via XSL. I can use any of these
>to get the same results depending on what the client wants.
>
>I've been playing around with some OLEDB connections for the As/400 and
built
>a Systems Administrators Utility using an ActiveX DLL Document. The work
>I was doing didn't use a flat file but I was able to use a flat file for
>some of my testing and playing with how the control works.
>
>The code I use to pull from As/400 physical and logical files looks like
>this:
>
> strSQLString "Select * from tablename"
> 'set connection to as/400
> strConn = "Provider=HitOLEDB400;Password=admin;User ID=sa;Data Source=123.123.123.123;...etc...."
>
> Set Cn = New ADODB.Connection
> Set Rs = New ADODB.Recordset
>
> Cn.Open strConn
> Rc.CuresorLocation = adUserServer
> Rc.Open strSQLString, Cn, adOpenKeyset, adLockOptimistic
> SQLConnect = True
>
>This actually returns a recordset from the As/400 and you can update, deleted,
>modify, etc... just like you would in SQLServer or Access. I thought it
>was pretty neat.
>
>The Hit control does allow you to use command line access to run programs
>on the mainframe. Then you can access the results of the run... which in
>your case would probably be strings that your program created. I'm not
sure
>exactly how this should be done using VB but the Hit people can probably
>tell you what you need to do.
>
>There are a number of these OLEDB and ODBC controls and the best one that
>I've got to work is from Hit Software. The only bad thing about buying
these
>controls is the cost. For just a single connection then it's pretty cheap,
>but if you want thousands of connections via the internet at the same time...
>then it gets pretty high.
>
>If your wanting to use VB to access flat files on the mainframe then you
>should be able to do this via the Hit Control but I have not played with
>this in VB. If you are hitting an As/400 then AVR-RPG can access the flat
>file. You can create a dll using the AVR-RPG product that you can call
from
>an VB or ASP application. Then just pass the data you need through the
dll
>to the VB/ASP application.
>
>
>"Gee" <grajput@slk.com> wrote:
>>
>>How are u connecting to Mainframe from ASP/VB?
>>
>>"Greg Rothlander" <grothlander@austin400.com> wrote:
>>>
>>>Sorry for the delay. I didn't see your reponse last week.
>>>
>>>I'm not sure about what your doing on the mainframe side. As far as what
>>>you pass back in XML would depend on what your doing on the mainframe
side.
>>>
>>>
>>>What I'm doing...
>>> I'm using programs that I write on the As/400 to generate the XML
stream.
>>> I'm manually going through the file looking for what I want. Then I
build
>>>a large XML stream that I create within my As/400 code. Something like:
>>> xmlstream = "<zipcode>" + CZIPIC + "</zipcode>"
>>>
>>>I'm doing this on the As/400 and then sending a string back to my Web
Server
>>>and use an ASP/ASPX page to load the XML and XSL and transform it. I'm
>>able
>>>to call the As/400 program via the ASP page, create the XML stream using
>>>code on the mainframe, and then pass back the XML Stream to the ASP page.
>>>
>>>
>>>This may not be a recommended way to do it but it's the only way I've
found
>>>that really works with the mainframe. As far has handling the flat file,
>>>well that would depend on what you are doing to get the data out of the
>>file
>>>and into whatever it is your passing back as a XML stream.
>>>
>>>I can do the same thing via VB using a demo OLEDB control I got from Hit
>>>Software. I think the page is www.hit.com. It's can be costly because
>>of
>>>lisencing issues but in my environment I just pass the cost onto the clients.
>>> If you already have a ODBC or OLEDB connection to your mainframe then
>you
>>>should be able to use it to pass a string between the Web Server and your
>>>mainframe.
>>>
>>>There are so many options depending on exactly what you are doing that
>it's
>>>hard to offer information. This is just one of many, many was to handle
>>>this sort of stuff.
>>>
>>>
>>>
>>>
>>>
>>>
>>>"Gee" <grajput@slk.com> wrote:
>>>>
>>>>Can i read only a particular portion of the flat file, so that i don't
>>have
>>>>to get the whole file as a stream.
>>>>The reason is the flat files are huge reports and i mean very huge.
>>>>The user don't need the whole report he will query a particular part
of
>>>the
>>>>report and i need to show that part in XML.
>>>>If i get the whole report it will consume lot of memory on my side.
>>>>lemme know how to access mainframe using VB.
>>>>
>>>>Thanks
>>>>
>>>>"Greg Rothlander" <grothlander@austin400.com> wrote:
>>>>>
>>>>>I'm doing this with data on As/400. I'm doing this a few different
ways
>>>>but
>>>>>I will give you a quick run down on how it works.
>>>>>
>>>>>I'm using a RPG compiler (or Visual Basic) to create a DLL that will
>connect
>>>>>to an As/400 and read the files. Using the RPG code I create the XML
>>stream
>>>>>that I need to recieve as one large string and set it equal to a property
>>>>>of the dll class. I then access the dll's class property inside my
ASP
>>>>and
>>>>>ASP.Net pages to get the XML stream. I then use XSL to convert the
XML
>>>>into
>>>>>my clients viewable web page via VB code in the ASP page.
>>>>>
>>>>>The method you choose will depend on how your connecting to the mainframe
>>>>>and how you are passing the XML data back to your web pages. There
are
>>>>a
>>>>>few ways I could have handled.
>>>>>
>>>>>Email me if you would like additional information about what I've been
>>>able
>>>>>to do on the As/400.
>>>>>
>>>>>
>>>>>"Gee" <grajput@slk.com> wrote:
>>>>>>
>>>>>>I have a flat file in mainframe (not mainframe database), i have to
>create
>>>>>>XML for each flat file and show the xml on the web using XML and XSL.
>>>>>>
>>>>>>Any bright ideas.
>>>>>>
>>>>>>Thanks in advance
>>>>>>
>>>>>
>>>>
>>>
>>
>
Definitely give Data Junction Integration Suite a try. Visit www.datajunction.com
to investigate. Or www.xmljunction.com
"rdbms" <rdbms@aol.com> wrote:
>
>"Gee" <grajput@slk.com> wrote:
>>
>>I have a flat file in mainframe (not mainframe database), i have to create
>>XML for each flat file and show the xml on the web using XML and XSL.
>>
>>Any bright ideas.
>>
>>Thanks in advance
>>
>
>Not sure if this will help, but XML Spy 3.5 includes a text import dialog
>(I've used it often - nice feature). You have the capability to identify
>the delimiters (comma, semicolon, tab, space) and whether the text was encapsulated
>within quotes, apostrophes.
>
>If you are looking for something to automate the process, I am unsure if
>XML Spy exposes their technology via an API or not. You could take a look
>(XML Spy by Altova).
>
>If I remember correctly Data Junction also provides extensive conversion
>capabilities from/to XML. Great tool.
>
>Also, are you considering character encoding/exchange (i.e. is this an EBCDIC
>or ASCII file ?). That could add a slight character conversion twist.
don't think so!! A bit complicated for this.
"tim frost" <tfrost@datajunction.ocm> wrote:
>
>Definitely give Data Junction Integration Suite a try. Visit www.datajunction.com
>to investigate. Or www.xmljunction.com
>
>
>
>"rdbms" <rdbms@aol.com> wrote:
>>
>>"Gee" <grajput@slk.com> wrote:
>>>
>>>I have a flat file in mainframe (not mainframe database), i have to create
>>>XML for each flat file and show the xml on the web using XML and XSL.
>>>
>>>Any bright ideas.
>>>
>>>Thanks in advance
>>>
>>
>>Not sure if this will help, but XML Spy 3.5 includes a text import dialog
>>(I've used it often - nice feature). You have the capability to identify
>>the delimiters (comma, semicolon, tab, space) and whether the text was
encapsulated
>>within quotes, apostrophes.
>>
>>If you are looking for something to automate the process, I am unsure
if
>>XML Spy exposes their technology via an API or not. You could take a look
>>(XML Spy by Altova).
>>
>>If I remember correctly Data Junction also provides extensive conversion
>>capabilities from/to XML. Great tool.
>>
>>Also, are you considering character encoding/exchange (i.e. is this an
EBCDIC
>>or ASCII file ?). That could add a slight character conversion twist.
>
