|
View previous topic :: View next topic
|
| Author |
Message |
sijayapal
New User
.jpg)
Joined: 23 Dec 2008
Posts: 69
Location: India
|
|
|
|
Hi,
I am new to CICS. I am facing a problem while browsing/Editing data using MAPS. There are 29,190 records in the VSAM file. When i browse them via MAPS, i am able to read only 9999 records. I verified the programs and i see that the vairables are declared as below.
| Code: |
05 WS-TSQ-FIRST-ITEM PIC 9(4).
05 WS-TSQ-LAST-ITEM PIC 9(4).
05 WS-TSQ-ITEM PIC 9(4).
05 WS-TSQ-ITEMNUM PIC 9(4).
01 WS-NUMITEM PIC S9(4) COMP.
01 TSQ-ITEM PIC S9(4) COMP.
|
I increased the ITEM lengths to 9(6) and it didn't help.
Please let me know exactly what i needs to be done to increase the size to 999999. |
|
| Back to top |
|
 |
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008
Posts: 2501
Location: Atlanta, Georgia, USA
|
|
|
|
Check your compile option for TRUNC. If it's set to OPT then you need to re-compile with TRUNC(BIN).
If your compiler supports COMP-5, then change COMP to COMP-5 and you don't need to adjust the TRUNC option.
Both NUMITEM and TSQ-ITEM must remain as binary halfwords.
You are experiencing high-order truncation on the halfwords, due to TRUNC(OPT).
Bill |
|
| Back to top |
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007
Posts: 2146
Location: At my coffee table
|
|
|
|
What is 'MAPS'?
What is the compiler option TRUNC set to? |
|
| Back to top |
|
|
sijayapal
New User
Joined: 23 Dec 2008
Posts: 69
Location: India
|
|
|
|
Bill O'Boyle
Thanks a lot. It worked. I couldn't exactly figure out how to find the compiler option. I changed the comp to comp-5 and it worked fine as expected.. thanks a lot.
 |
|
| Back to top |
|
|
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008
Posts: 2501
Location: Atlanta, Georgia, USA
|
|
|
|
COMP-5 was introduced with the OS390 COBOL compiler, version 2.2.1, about 10-12 years ago.
It is known as "Native Binary" and the TRUNC option does not affect it, whatsoever.
Unlike TRUNC(OPT) which truncates high-order, based upon the picture clause in BINARY fields, COMP-5 values are guaranteed to be correct and are never truncated.
This is the reason why you could not have a value greater than 9999 in your COMP fields. Without COMP-5, you would have to specify TRUNC(BIN), which also guarantees values to be correct, but is brutally inefficient.
Glad it worked out for you....
Bill |
|
| Back to top |
|
|
sijayapal
New User
Joined: 23 Dec 2008
Posts: 69
Location: India
|
|
|
|
Thanks for the information Bill 
Thanks
Siva. |
|
| Back to top |
|
|
|
|
