|
View previous topic :: View next topic
|
| Author |
Message |
bala.sachin
New User
Joined: 27 Feb 2013
Posts: 9
Location: India
|
|
|
|
Hello All,
When you put HEX ON on a file it shows the file with it's hexadecimal values,What are the situations in which HEX ON will be useful,I have gotten out of touch in mainframes and pls pardon me for this simple question |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
when the file You are looking at contains NON PRINTABLE characters
( for example packed / binary numbers ) |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
And when members here says that they have a "numeric field" but it's not "displayed" correctly... |
|
| Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
What do you mean by "COBOL file"?
Do you mean a member in a PDS/PDSE which happens to contain a Cobol program? If so, the HEX ON/OFF is just there because it is part of the editor.
As an aside, It was an "old" way to get a hexadecimal value in a field. You type VALUE " ".
Then you turn HEX ON. Go down to the hex values and overtype the 40 and 40 to whatever value you require. Put a comment saying what value it contains and, if the hex happens to give a lower-case letter, warn about the dangers of making any change on the line whilst having CAPS on.
These days, you just do this:
| Code: |
| ... VALUE X"with required hex value". |
|
|
| Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009
Posts: 2481
Location: Netherlands, Amstelveen
|
|
|
|
| Quote: |
| and they'll waste a few minutes (or more) trying to work out what has happened (and may come up with assorted dumb theories, for extra fun). |
What the hell is that Bill? Those people will come here on this forum for help. Thank you very much.  |
|
| Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
| Sorry Peter, just for fun. I've edited it out. |
|
| Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009
Posts: 2481
Location: Netherlands, Amstelveen
|
|
|
|
| Ok Bill, just teasing a bit. |
|
| Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
Well, I'm not re-typing it :-)
For those who have missed it, it was one of the "funniest" unattended-terminal weezes of all time. Almost up there with "turning the contrast way down", or "disconnecting the keyboard". Indulge in such trickery entirely at your own peril. |
|
| Back to top |
|
|
bala.sachin
New User
Joined: 27 Feb 2013
Posts: 9
Location: India
|
|
|
|
Hi Bill,
Thank you for the response
The file is a flat file which has records |
|
| Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
Well, it is not a "COBOL file" then. It is just a dataset, or file if you like, which happens to have come from a Cobol program, but which has no different characteristics inherent because of that. If you look at any dataset, there is no way to tell from that itself that it has come from a Cobol program.
Why would you have HEX ON for a file? To see any "non-display" values. To create/amend test data where non-display values exist (like in binary or packed-decimal) fields. |
|
| Back to top |
|
|
bala.sachin
New User
Joined: 27 Feb 2013
Posts: 9
Location: India
|
|
|
|
Hi Bill,
Yep!It's a dataset :-P sorry for confusing u on that part
But I got your answer which is to view non-displayable data
Thanks |
|
| Back to top |
|
|
|
|
