PMFJI, but your rant caught my attention. Can you point me to further info on precisely how they differ (as I am in the business of mediating mainframe-style email exchange between IBM's mainframes and the intra/Internets and I ought to be up to speed on this issue. We tend to use the translation tables shipped with the VM TCP/IP product (which themselves are derived from tables supplied by IBM's Globalization Center of Competency) rather than the native ones built into PIPE (mostly because we need to do translations between a lot more codepages/charsets than PIPE supports). I am wondering if those tables agree with zOS or PIPE. -- bc
On Fri, Feb 26, 2010 at 11:19 AM, Paul Gilmartin <[email protected]>wrote: > On Feb 26, 2010, at 06:53, Rob van der Heij wrote: > > > On Fri, Feb 26, 2010 at 12:47 PM, Paul Gilmartin <[email protected]> > wrote: > > > >> The key word here is "collection". VMFPLC, like VMARC will handle > >> envelopes containing multiple files with different attributes. > >> I don't believe netdata will do this. > > > > Since netdata wraps each file such that you see where it ends, you can > > stack them in a single file. > > > Then I must provide a tool to unstack them. Yah, I know, "One can > design a pipe to do that." I think the least overhead for the > recipient is VMFPLC2 wrapped with COPYFILE (PACK). > > > I was reading into your original post a way to transport between alike > > systems over hostile roads. > > > That was my immediate objective: > > o Developers on CMS. > o Unix (or perhaps windows) webserver. > o Customer on CMS. > > ... but I rambled. Techniques to transport between unlike > systems without loss of information can be adapted to transport > between alike systems over hostile roads. > > > If you're looking for something to exchange data between unlike > > systems in a way that makes sense, options get exponentially less > > attractive with the number of systems you involve. ZIP tried things > > like EBCDIC to ASCII conversion (which ones?) but it is rather alien > > for CMS environments. > > > <RANT> > CMS Pipelines implemented ISO8859-1 <--> IBM-1047 conversion > "by the book". z/OS added a tweak to accommodate the historic > behavior of C compilers, 3215 printers, and CP command separators, > so CMS and z/OS differ. Dammit, if they differ in even one > [pair of] codepoints, z/OS should have defined a different > code page, not added a footnote to the doc. > </RANT> > > Thanks, > gil >
