RE: Standards issue - Comments please.

["Fisher, Don" <Dfisher@xxxxxxxxxxxxxxxxx>]

O-specs are simpler to code and easier to maintain?  Huh?

Let's see now, with a printer file, I can use RLU or CODE/400 to see the
report layout and actually see the results of my changes.  With O-specs I
must perform many calculations of field length to determine the beginning
and end point of a field to ensure no overlap occurs.  I must also
constantly refer back to other O-specs to ensure the columns line up with
the headings.

Of course, all of the above doesn't matter much if you have detailed
specifications that include a report layout and character position ruler.

O-specs do have a couple of advantages over the printer file.  First, you
can use array fields with a variable subscript such as ARR,A as fields in
the specifications.  They also provide automatic line, heading, and total
printing tied to the logic cycle (NOTE: I HAVE OFFERED NO OPINION ON THE
CYCLE) and to whether the overflow line has been reached.

Personally, I think a report program being self-contained and having fewer
members to check out are rather specious arguments.  Do these people also
use internally defined display files and not the DSPF objects?

In the end, it may come down to personal preference, but if you want to
establish a shop standard, you might as well go with printer files.  They
offer more features such as advanced function printing, bar codes, IPDS
functions, and other stuff that cannot be done with O-specs.  That is, of
course, just my opinion.

Hope that helps.

Donald R. Fisher, III
Project Manager
The Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@roomstoreeast.com

<clip>
(The group that favors O-spec)
"O-specs are simpler to code and easier to maintain"
"Report programs are self contained"
"Fewer members to check out"

(Now the PRTF group)
"PRTF is simpler to code and easier to maintain"
"Separation of presentation attributes from report logic makes report layout
changes easier"
"PRTF can support advanced features such as barcoding, font control,
embedded images/graphics, etc."

<clip>