Thanks Joe,
I picked up the dataset record layout from Amisys itself.. And added 2 new
fields to it.. It perfectly matches the layout from ACPCRCT.COBBUFF provided
by Amisys, except for the 2 additional fields. I dont think I am having any
trouble in data movement or any other related problems because my data in
the first field and last field are being stored perfectly as expected. Its
only happening in this COMP field. And pretty surprising because Amisys
stores it the same way and it gets populated perfectly without any problem.
Just in my case, it creates a problem.. Still working on it..
Thanks for your kind hints..
Regards
Raghu.
-----Original Message-----
From: joe andress [mailto:[log in to unmask]]
Sent: Thursday, October 24, 2002 11:10 AM
To: Rao, Raghu
Subject: Re: Re: [HP3000-L] COBOL : Trailing zeroes this time........
hi
since this is an AMISYS dataset from the ACCTNG database, have u looked at
the AMISYS supplied $INCLUDE files for this data set to match up the PIC
clauses with your working storage areas.
i have seen some client get them mixed up before.
Joe Andress
Thoughts are mine and not my employer
----- Original Message -----
From: "Rao, Raghu" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Thursday, October 24, 2002 8:29 AM
Subject: Re: [HP3000-L] COBOL : Trailing zeroes this time........
> I went through the compiler listing this time... All working storage
fields
> referencing moves to this variable are defined as 9(09) and all database
> fields defining this field are referenced as S9(09) COMP.. Still the data
> gets stored in this COMP field as trailing zeroes for some reason.
>
> I am sending the dataset record layout and 1 record for reference. As you
> can see below that both CHECK# and PROCESSED-BY fields are I2 fields and
> defined as S9(09) COMP. I am moving 0 to PROCESSED-BY field and valid
check
> number 8282 and you can see the difference on how the data gets stored in
> each of those 2 fields.. I am moving proper numeric amount fields (those
are
> also I2) and they are defined as S9(07)V99 COMP and there is no problem at
> all in them.
>
>
> PREMCASH-RECEIPT Detail Set# 5
> Entry: Offset
> PREM# X12 1 (!PREMIUM-A)
> ACCT-ID# X10 13 (ACCOUNT-A)
> MONTH X6 23 (MONTH-A)
> RECEIPT# X12 29 (RECEIPT-A)
> AMOUNT I2 41
> AMTARCHBAL I2 45
> APPLIED-FLAG X2 49
> BATCH# X8 51
> BILL-TO X2 59
> CHECK# I2 61
> EFT-INFO X2 65
> INVOICE# X12 67
> NAME X20 79
> OP# X4 99
> POSTED1 X2 103
> POSTED2 X2 105
> PROCESSED-BY I2 107
> TRANS# X12 111
> TRANSCODE X2 123
> TRANS-POSTED X2 125
> TYPE X2 127
> YMDDUE X8 129
> YMDPAIDTHRU X8 137
> YMDPROCESS X8 145
> YMDRCVD X8 153
> YMDTRANS X8 161
> Capacity: 19999 (1) Entries: 30 Highwater: 30 Bytes: 168
> ------------------
> PREM# = XFCE00000447 ACCT-ID# = A070000010
> MONTH = 200210 RECEIPT# = XFCE00000963
> AMOUNT = 1000 AMTARCHBAL = 1000
> APPLIED-FLAG = NO BATCH# = D01234LP
> BILL-TO = D CHECK# = 828200000
> EFT-INFO = INVOICE# = DF0500000058
> NAME =
> OP# = RZR POSTED1 = YE
> POSTED2 = NO PROCESSED-BY = 0
> TRANS# = TRANSCODE = AD
> TRANS-POSTED = NO TYPE =
> YMDDUE = 0 YMDPAIDTHRU = 20021031
> YMDPROCESS = 20021024 YMDRCVD = 20021212
> YMDTRANS = 20021024
> ------------------
>
> Thanks again
> Raghu.
>
>
> -----Original Message-----
> From: Ken Hirsch [mailto:[log in to unmask]]
> Sent: Thursday, October 24, 2002 9:04 AM
> To: Rao, Raghu; [log in to unmask]
> Subject: Re: [HP3000-L] COBOL : Trailing zeroes this time........
>
>
> From: "Rao, Raghu" <[log in to unmask]>
> > Hi,
> >
> > I am trying to store records into detail dataset. The particular field
> that
> > is giving trouble to me is a I2 field {defined as S9(09) COMP}. If I
move
> > zeroes to this field and perform a DBPUT, everything works out fine.. Bu
t
> > when I have a valid numeric number in this field, it stores it with
> trailing
> > zeroes..
> >
> > For ex., I am moving value 1298 into this field and it gets stored as
> > 129800000.
>
> There can't literally be stored trailing zeros because it is a binary
field,
> not a decimal field, although the binary equivalent of 129800000 might be
> stored there. Are you sure your field isn't defined as S9(4)v9(5) in your
> program? You might want to read through the compiler listing to make sure
> you are compiling what you think you're compiling.
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
