Come for answers, stay for best practices. All we're missing is you.
Originally posted by: edi1999
Have several maps that zip files before sending them via ftp to a mainframe where they are then unzipped. Testing on a 64 bit server (8.4.04 launcher) and it appears the files are being zipped as "BIN" instead of "TEXT" as they always have been in the past. Anyone else encounter this? When I look at the zipped file before sending ftp, it looks good to me; the extract is ascii data. But when we unzip it on the mainframe it's junk.
Originally posted by: paul.brett
As far as I am aware, the ZIP adapter has always zipped files 'as-is'. If you find that the ZIP adapter is able to unzip (31 bit) on mainframe and the content is readable (i.e., it has been converted to EBCDIC) then I can only guess that perhaps this is a function of the Typetree object you have used, because I am fairly confident the ZIP adapter did not do this.
Thank-you.
Paul
Follow me on Twitter
My issue is these are the exact same maps, exact same files, exact same jcl as are currently working on our 32-bit servers. Absolutely nothing has changed in them. We just copied them to the 64-bit machine and it doesn't work the same.
Is it the same version of WTX on both machines?
At this point, I recommend you open a Service Request (PMR) with support - and supply a testcase.
Update: There is a difference between the 32 and 64 bit and the zip adapter. As I understand it from IBM the text/binary setting is no longer controlable in the 64 bit zip adapter and will send as text regardless of the ftp setting.