Shell Programming and Scripting

Can you confirm that if the record layout for EVENT-TYPE = 1 can be written as:

Code:

CURR-MAINT-DATE USAGE DISPLAY    PIC S9(7) SIGN IS LEADING SEPARATE CHARACTER. .
 PREV-MAINT-DATE USAGE DISPLAY    PIC S9(7) sign as above. 
PREV-CNCY-CODE            PIC X(03).
 CNCY-CONV-DATE  USAGE DISPLAY    PIC S9(07) sign as above.
 CNCY-CONV-TIME                  PIC  9(07). 
FILLER             PIC X(416)

That is, there is no valid data in the filler.
Also, for EVENT-TYPES 3 through 900, are there other layouts that include packed decimal?
I am puzzled by the date and time fields as they are signed and also that sizes of 8 and 6 respectively would be more appropriate,and require the same amount of disk space. Is there a possibility that they are negative, and if so should these also be changed to leading separate character?

Hi,

Filler contains only spaces and this is just to make sure the length of the record is same irrespective of the EVENT_TYPE.

Date and TIME are packed decimals and there is nothing that we need to round off and all.Just need to pass what we get from source.

Thanks alot for your reply..

I meant CDATE-EVENT and TIME-EVENT, not the sub fields in EVENT-DATA.

Yes the CDATE-EVENT and TIME-EVENT, are the sub fields in EVENT-DATA.

Do you know the file recording mode? Probable modes are fixed record length, no record separator; or fixed record length with record separator.
What operating environment does the file reside in?
If I leave the signed fields without a leading separate character, negative numbers will end in a lower case letter in the units column, so depending upon what you intend to do with the file, you may still have to do more conversion.
Approximately how many records are in the file?

The file is a fixed width without any filed seperator.
The file is not huge approximatly 20k records.
From packed to normal format should be proper ie., we should not remove any signs..