John Y, to answer the question you posed below, in a previous job, we
archived our specialized voluminous transaction data from the i to a NAS
server. It was FTP'd using the binary option for reason(s) I can't exactly
recall, except for the possibility that some of the data did not convert
correctly from EBCDIC to ASCII, and the fact that the data was never used
in an ASCII environment. There were occasions where we needed to find data
in these files on the NAS server and, for that, we used Windows-based
editors that could speak EBCDIC.
In my current job, I have not yet run across a need for such an editor.
Again, the purpose for this exercise was to expose a vulnerability for
which the security decision makers here were perhaps unaware, and to refute
the idea that blocking developers from using Windows-based query tools
prevents theft of sensitive data. (As I am rather new here, I am unaware
of how the security policy has come to be what it is currently. There was
a comment made that as of several years ago, all developers here had
*ALLOBJ authority. Apparently, some abuses occurred, and auditors threw out
the baby with the bath water, so to speak. Now, one must go through a
process of discovering what they are unable to do and then ask managers for
permission. Shortly after I installed RDi, I found out that I was
unauthorized to use the STRDBGSVR command! Sheesh.)
- Dan
On Wed, Mar 18, 2015 at 1:22 PM, John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:
Just curious: Did you actually demonstrate viewing/converting EBCDIC
with a hex editor, or was that just something you wanted to have in
your pocket in case you needed it?
John Y.
midrange.com
