Home > Information > FAQ > Papyrus DocEXEC Application Development > Printer friendly version

 


Frequently Asked Questions about AFP

Questions about the Papyrus System

Papyrus DocEXEC Data Interface

Papyrus DocEXEC Resource Management

Papyrus DocEXEC Application Development

Papyrus DocEXEC Paper Handling Capabilities

Papyrus DocEXEC Statement Formatting Capabilities

Papyrus Designer related questions

Papyrus and SAP related questions

Terms and Abbreviations


Papyrus DocEXEC Application Development

Q: Does the product provide a fully documented and human readable source code?

A: Yes. The DOCDEF is upward compatible to IBM PPFA source code.


Q: Do product specific commands have to be inserted in our applications?

A: No. In difference to products based on markup-controls as the usual {tags}, Papyrus can use any data field as a controlling element. Proprietary control tags in the data mean, that a change to another product would require a huge conversion effort. As long as the control tags can be easily identified, DocEXEC can even use existing tags of other systems as control information.


Q: Are text elements stored in a standard or proprietary format?

A: Standard. ISIS recommends to store text elements in raw ASCII or EBCDIC format. In this manner they are easily maintainable by users and can be simply reused for other systems and applications. Papyrus can be setup to accept any text control escape sequences within the raw text. DCF SGML and other formats can be supported as external text elements.


Q: Is a change in a form, graphic or text element reflected in all documents?

A: Yes. In case this element is reused in this manner, a change will propagate automatically to all documents using this element. This saves time, costs and effort for version control.


Q: Can the product provide a PAGEDEF with white space removal capabilities?

A: Yes. The PAGEDEF is imported and just enhanced. The data is not changed.


Q: Does the product also develop high-performance IBM OGL/PPFA source code?

A: Yes. In this way simple forms/data applications do not need to use the formatter and are just printed by IBM PSF or Papyrus Server.


Q: Can OGL/PPFA source code be imported?

A: Yes. It can be imported and edited and also later used for enhanced DOCDEF statement formatting applications.


Q: Will an OGL/PPFA OR FRM/JDE experienced person understand your coding?

A: Yes. Because it builds on these functions and expands them.


Q: Can the product use the same document description on multiple platforms?

A: Yes. The DOCDEF is used by DocEXEC on all platforms like MVS, UNIX, AIX and OS/2 without change.


Q: How many separate programs are used to generate the document from the data?

A: One. Papyrus DocEXEC provides simple single-step execution.


Q: Are all these programs available across all supported platforms?

A: Yes. MVS, AIX, HP-UX, SUN Solaris, DEC Alpha, SCO-Unix, OS/2, WindowsNT, and Windows95/98.


Q: Has the printer type to be chosen at time of statement formatting?

A: No. As Papyrus does not use the usual 'emitter' or 'converter' technique, the generated AFPDS file can be printed to any IPDS, HP-PCL4/5, Xerox Metacode, and Postscript printers at the operators choice. The same file can be archived or distributed for viewing with the Papyrus Client to PC platforms.


Q: Does the product provide indexing for archiving, i.e. ACIF compatible?

A: Yes. The ACIF index is also used for previewing to locate pages in a large spool file and not just for archiving purposes.


Q: Does the product provide ACIF group indexing?

A: Yes. Papyrus DocEXEC provides fully qualified group index names from variable expressions.

 


ISIS Papyrus Europe
T: +43-2236-27551
F: +43-2236-21081
ISIS Papyrus America
T: 817-416-2345
F: 817-416-1223
ISIS Papyrus Asia-Pacific
T: +65-6339-8719
F: +65-6336-6933
Email: info@isis-papyrus.com
Internet: www.isis-papyrus.com
© 2007 ISIS Marketing GmbH • All rights reserved