snip
I'm doing an analysis of one of our application programs. As part of this, I'm
seeing the COBOL code generate a lot of PACK/UNPACK instruction pairs.
Does anyone have an idea on the performance impact of all these (potential
millions of executions in a single run)?
/snip
A long time
Cobol will pack before doing a compare for when the operands in the
compare are not the same data type and atleast one operand is numeric.
I am a bit concerned about the phrase pack/unpack pairs.
Cobol will not do a pack/unpack pair for a compare ... is there something
you failed to mention like
I'm doing an analysis of one of our application programs. As part of this, I'm
seeing the COBOL code generate a lot of PACK/UNPACK instruction pairs.
Does anyone have an idea on the performance impact of all these (potential
millions of executions in a single run)?
What's the impact of just
Peter Vander Woude wrote:
I'm doing an analysis of one of our application programs. As part of this, I'm seeing the COBOL code generate a lot of PACK/UNPACK instruction pairs.
Does anyone have an idea on the performance impact of all these (potential
millions of executions in a single run)?
This is very common.
If you know Cobol, you know it handles compares of different variable
types automatically. If a number say called N is defined as USAGE DISPLAY
with a PIC of say 99, and another number M is defined as USAGE
PACKED-DECIMAL with a PIC of say 99, the instruction
IF N EQUAL
5 matches
Mail list logo
