Re: FTP - Problems with non-text variable length files
Looks like TYPE EBCDIC MODE BLOCK did the trick! Thanks! Karl Severson Raytheon Company -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
FTP - Problems with non-text variable length files
We've always had a problem with FTP and non-text files (object files, binary,) that are variable length on our VM/ESA systems. When they get to where they are going they aren't the same as when they left the source system. This can be between two IBM's or between an IBM and any non-IBM system. Now that we are on a new z10 with zVM6.1 I thought that maybe this problem would have been fixed but nothing seems to have changed. Is this a problem or a feature? Using the BINARY switch doesn't help. Thanks! Karl Severson Raytheon Company -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: FTP - Problems with non-text variable length files
'What's a variable length object file? I thought they were always F 80 (filetype TEXT?).' In our case they could be output from a compiler (FORTRAN) or an assembler module. We will try your suggestions and see what happens. Thanks! Karl Severson Raytheon Company -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: What Replaced the DATE command?
Yep, after further snooping around the old system I found a DATE module and a help file describing the function written by some folks who worked here years ago. Hopefully I can get this exec to work if I have that module on the new system. Thanks! Karl Severson Raytheon Company -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: What Replaced the DATE command?
Thanks Mark. I will give this a try if the DATE module I found on the old system doesn't work on the new one. Karl Severson Raytheon Company -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: What Replaced the DATE command?
The DATE module from the VM/ESA 2.3 system worked on the zVM 6.1 system. Thanks for the ideas! Karl Severson Raytheon Company -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
What Replaced the DATE command?
Sorry for this easy question. Going from VM/ESA 2.3 to zVM 6.1 is proving very interesting. It's amazing how many execs don't work on zVM that work fine on the prior OS. I have a REXX exec that gets yesterday's date by 'DATE -1' but that doesn't work in zVM. I've looked through the IBM Collection DVD so far to no avail. Sort of hard to look up something that isn't there to see what replaced it! I found it interesting on my office P/390 system where I'm running zVM 3.1 second level on VM/ESA 2.3 that DATE is still in the HELP files under REXX statements. Doesn't work but it's there! Regards, Karl Severson Raytheon Company -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
