View previous topic :: View next topic
|
Author |
Message |
nankrish
New User
Joined: 11 Nov 2005 Posts: 26
|
|
|
|
hi,
for initializing few variables instead of moving spaces in few places low values or high values are being moved.
is there any specific reason behind this? |
|
Back to top |
|
|
Marso
REXX Moderator
Joined: 13 Mar 2006 Posts: 1353 Location: Israel
|
|
|
|
There may be a few reasons why to use L-V or H-V:
- CICS maps are usually initialized with LOW-VALUES because they contain a mix of DISPLAY and COMP fields (L-V in a COMP field is the same as 0).
- After a sort. L-V always appear at the beginning and H-V at the end. There may be some use for this property.
- If you have a table (with OCCURS) in W-S, move first H-V, then load the data. When you scan the table, reaching an occurs with H-V will indicate the end of data.
- You may want to make the difference between an empty value (SPACES) and no value (LOW-VALUES), just like DB2 NULL.
I'm sure there are more possibilities... |
|
Back to top |
|
|
parikshit123
Active User
Joined: 01 Jul 2005 Posts: 269 Location: India
|
|
|
|
Hi,
Just to add to that,
Low values and lowest values in the collating sequence where as high value is highest values in the collating sequence.
The collating sequence depends on underlying machines to machines. Mainframe's collating sequence is based on data representation in EBCDIC (Extended binary coded decimal ). This is different for numeric and non numeric data types.
It depends on your application logic whether to move low values/high values in a given variable or initialize with some specific values like SPACES. |
|
Back to top |
|
|
|