|
View previous topic :: View next topic
|
| Author |
Message |
nallaperumal
New User
Joined: 19 Nov 2007
Posts: 23
Location: Chennai
|
|
|
|
It's a shame that there's no way to display hex values on toy computers
I cant able to get you. |
|
| Back to top |
|
 |
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
| Three damn minutes. It is hex 1A. Do a google for - ftp hex 1a - and you'll come up with a discussion on this site from last year. See where you get then, please. |
|
| Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
| nallaperumal wrote: |
I am getting a Junk EOF character while using PKZIp. Is there any paramenter to avoid such Junck End of File Character after PKZIP - ing .
Aprreciate your help |
To re-state your original request:
I am getting an PC-standard end-of-file character (hex 1a) at the end of the file I have FTP'd from a mainframe to a PC.
Oh, I'm not sure what the question is now.
Since you seem to be doing a lot of FTP'ing to PCs, I suggest you now work out how to look at hex values when they arrive on the PC, as suggested earlier. Think. Search. Let us know. |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
| Akatsukami wrote: |
It's a shame that there's no way to display hex values on toy computers  |
There is. DEBUG.EXE. It's been a part of DOS and Windows since their inception, although it was finally dropped in Windows 7 (see my topic here about that). But, there are other tools (I use HexDump32). |
|
| Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
| Akatsukami wrote: |
| It's a shame that there's no way to display hex values on toy computers |
I couldn't find the "irony" BBcode either.
Normally the 1A is displayed as either right-arrow or Control-Z (^Z). How did it get to be a square. Was it a square where you saw it originally. |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
I posted this in the original topic. It's straight out of the manual. Please take note of what it says:
| Quote: |
In the context of ZIP Archives, a “text file” is one that is stored in the ASCII format. A text file contains records of data, each separated by a delimiter to signify the end of the record.
PKZIP for zSeries uses the default delimiter CRLF (x’0D0A’) at the end of each text record. You may choose to use a different delimiter by using the –DATA_DELIMITER command (or other characters as specified in the command set). At the end of each ZIP’d file is a file terminator. The default file terminator for PKZIP for zSeries is Ctrl-Z (x’1A’). This file terminator can be changed by using the –FILE_TERMINATOR command.
Note: The last record will have the data delimiter followed by the file terminator.
|
|
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
nallaperumal, nowhere, at any time, in either of your PKZIP topics, did you disclose to us what type of system you were preparing the zip file for. Anyone who prepares data for use on a Windows system knows that text data requires a Carriage-Return/Line-Feed ('0D0A'X) for each end-of-line, and a Ctrl-Z ('1A'X) for end-of-file. Unix, Linux, and other ASCII-based systems have their own requirements (usually CR only).
If you didn't know this, then you should have taken a hex dump of a known good file and checked what it uses for EOL and EOF, and then you could've set your PKZIP parameters to the proper settings as needed. Or, you probably could've asked a system admin or developer for that application, and they probably could've told you as well. |
|
| Back to top |
|
|
nallaperumal
New User
Joined: 19 Nov 2007
Posts: 23
Location: Chennai
|
|
|
|
Thanks superk it worked fine for me
Thanks again for all your effort |
|
| Back to top |
|
|
|
|
