IBM Support

PL38967: POSTSCRIPT PO %%BOUNDINGBOX IMAGE FILE 256 BYTES UPLOAD BINARY

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • THIS APAR ADDS NEW FUNCTION TO THE POSTSCRIPT (.PO) CONTROL
    WORD.  THE NEW FUNCTION WILL ALLOW THE USE OF REAL VALUES ON
    THE %%BOUNDINGBOX COMMENT OF AN IMAGE FILE, ALLOW IMAGE FILES
    TO CONTAIN RECORDS OF UP TO AND EXCEEDING 256 BYTES, AND TO
    ALLOW THE USER TO UPLOAD STRAIGHT BINARY FILES.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: ALL DCF USERS                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: POSTSCRIPT PO %%BOUNDINGBOX IMAGE FILE  *
    *                      256 BYTES                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    WHEN  SCRIPTING  A  DOCUMENT  THAT  USES  THE  POSTSCRIPT (.PO)
    CONTROL WORD TO INCLUDE A  POSTSCRIPT  FILE  THAT  SUCCESSFULLY
    PRINTS  ON A POSTSCRIPT PRINTER, MESSAGE 655E MAY BE ISSUED AND
    THE IMAGE NOT INCLUDED IN THE FILE.  THIS WILL OCCUR  WHEN  THE
    %%BOUNDINGBOX  COMMENT  WITHIN  THE  IMAGE  FILE  CONTAINS REAL
    NUMBERS RATHER THAT INTEGERS.   ALTHOUGH  REAL  VALUES  ON  THE
    %%BOUNDINGBOX  COMMENT  DO  NOT  CONFORM  TO  ADOBE'S  DOCUMENT
    STRUCTURING CONVENTION, DCF DEVELOPMENT HAS  DECIDED  TO  ALLOW
    THEM.    WITH  THIS  APAR,  WHEN REAL NUMBERS ARE USED WITH THE
    BOUNDINGBOX COMMENT, ERROR MESSAGE 660W WILL BE ISSUED AND  THE
    REAL NUMBERS ARE TRUNCATED.
    
    ALSO,  IF  A POSTSCRIPT IMAGE IS UPLOADED AND CONTAINS 'NEWLINE
    CHARACTERS' (X'0D' OR X'0A) OR CONTAINS RECORDS LONGER THAN 254
    BYTES, DCF WILL  FORMAT  THE  DOCUMENT  WITHOUT  ERROR  BUT  AN
    'UNDEFINED' ERROR WILL BE RECEIVED WHEN ATTEMPTING TO PRINT THE
    DOCUMENT  ON A POSTSCRIPT PRINTER.  DCF DEVELOPMENT HAS DECIDED
    TO ALLOW THE USER THE OPTION OF INCLUDING OR REMOVING  'NEWLINE
    CHARACTERS'  WHEN  UPLOADING  POSTSCRIPT  IMAGES  AND  TO ALLOW
    RECORD LENGTHS OF UP TO 256 BYTES  (EXCLUSIVE  OF  THE  NEWLINE
    CHARACTERS).    RECORDS  LONGER THAN 256 BYTES WILL RESULT IN A
    WARNING MESSAGE BUT WILL BE INCLUDED IN THE OUTPUT.    HOWEVER,
    RECORDS EXCEEDING 256 BYTES IN A COMMENT SECTION (THE HEADER OR
    TRAILER), MAY RESULT IN UNEXPECTED OUTPUT.  THIS PROBLEM SHOULD
    BE   CORRECTED   BY   FOLLOWING  ADOBE'S  DOCUMENT  STRUCTURING
    CONVENTION.
    

Problem conclusion

  • MODULES DSMLPKPO, DSMTFWPS, DSMTFPWG, DSMTFWRB,  DSMCSMDM  WILL
    BE MODIFIED TO ADD THIS SUPPORT.
    
    THE FOLLOWING CHANGES WILL BE MADE TO THE DCF MANUALS:
    
    THE  FOLLOWING  CHANGES  WILL  BE  MADE  TO  THE DCF: SCRIPT/VS
    LANGUAGE REFERENCE MANUAL (SH35-0070-05):
    
    UNDER THE .PO WRITEUP NOTE 3 WILL BE CHANGED TO "THE POSTSCRIPT
    FILE SPECIFIED MUST BE IN ASCII AND  CANNOT  EXCEED  A  LOGICAL
    RECORD LENGTH OF 256 BYTES."  REFERENCE TO CARRIAGE RETURN LINE
    FEED CHARACTERS WILL BE REMOVED.
    
    UNDER THE .PO WRITEUP NOTE 4 WILL BE CHANGED TO READ:
    
       THE  POSTSCRIPT  FILE MUST FOLLOW ADOBE DOCUMENT STRUCTURING
       CONVENTIONS VERSION 2 AND THE FIRST LINE OF THE FILE MUST BE
       A COMMENT THAT BEGINS WITH THE CHARACTERS %!.
    
       THE FILE MUST ALSO BE "WELL-BEHAVED"  AS  DEFINED  IN  ADOBE
       SYSTEMS'   RULES   FOR   CREATING   ENCAPSULATED  POSTSCRIPT
       DOCUMENT, "ENCAPSULATED  POSTSCRIPT  FILE  FORMAT".    FILES
       WHICH DON'T FOLLOW THESE RULES MAY PRINT ALONE BUT MAY CAUSE
       PRINTER ERRORS WHEN INCLUDED IN DCF'S OUTPUT.
    
       POSTSCRIPT  FILES  WHICH  CLAIM  TO  FOLLOW  ADOBE  DOCUMENT
       STRUCTURING CONVENTIONS VERSION 2 WILL  INCLUDE  "ADOBE-2.0"
       IN  THE  FIRST COMMENT IN THE FILE.  A POSTSCRIPT FILE WHICH
       ALSO CLAIMS TO BE  ENCAPSULATED  (AN  EPS  FILE)  WILL  ALSO
       INCLUDE "EPSF-" IN THE FIRST COMMENT.
    
    THE  FOLLOWING  NOTE WILL BE ADDED:  "IF WARNING MESSAGE 660 IS
    ISSUED INDICATING THE POSTSCRIPT FILE'S BOUNDINGBOX:    COMMENT
    CONTAINED  REAL NUMBERS AND THEY HAVE BEEN TRUNCATED, THE SPACE
    RESERVED AND/OR THE POSITIONING OF THE IMAGE MAY  BE  AFFECTED.
    YOU  MAY  USE  .IS  (INLINE  SPACE) AND .SB (SHIFT BASELINE) TO
    REPOSITION THE IMAGE.  THE SPACE RESERVED CAN BE  INCREASED  OR
    DECREASED DIRECTLY BY USING THE DEPTH AND WIDTH PARAMETERS.
    
    THE FOLLOWING CHANGES WILL BE MADE TO THE DCF: SCRIPT/VS USER'S
    GUIDE (S544-3191-00):
    
    THE  UPLOADING SUB-SECTION IN THE TRANSFERRING POSTSCRIPT FILES
    SECTION IN APPENDIX A. USING SCRIPT/VS WITH POSTSCRIPT  DEVICES
    WILL  BE  MODIFIED  TO  CONTAIN  TWO  OPTIONS.    THE FOLLOWING
    INFORMATION WILL BE ADDED:
    
       FILES  THAT  DO  NOT  VIOLATE  ADOBE  DOCUMENT   STRUCTURING
       CONVENTIONS  VERSION  2  FOR  LINE  LENGTHS  (256 BYTES) AND
       CONTAIN CARRIAGE RETURN LINE FEED CHARACTERS  RECOGNIZED  BY
       THE  UPLOAD  UTILITY  BEING  USED,  CAN  BE UPLOADED BINARY,
       VARIABLE RECORD LENGTH OF 256 BYTES OR  LESS,  REMOVING  THE
       CARRIAGE  RETURN  AND  LINE FEED CHARACTERS AND PUTTING EACH
       LINE IN A SEPARATE RECORD.
    
       FILES THAT CONTAIN RECORDS LONGER THAN 256 BYTES OR  NEWLINE
       CHARACTERS  NOT  RECOGNIZED BY THE UPLOAD UTILITY BEING USED
       MUST BE UPLOADED BINARY WITH AN LRECL OF 256 OR  LESS.    DO
       NOT  SPECIFY  THE  CRLF  OPTION.   NOTE:   USING THIS UPLOAD
       METHOD MAY INCREASE DCF EXECUTION TIME.
    
    THE FOLLOWING CHANGES WILL BE MADE TO THE  DCF  MESSAGE  MANUAL
    (SH35-0048-05):
    
    THE EXPLANATION AND USER RESPONSE FOR ERROR MESSAGE 655 WILL BE
    MODIFIED TO REMOVE ALL REFERENCES TO "INTEGERS".
    
    ERROR MESSAGE 657 WILL BE REMOVED.
    
    THE FOLLOWING WILL BE ADDED FOR NEW WARNING MESSAGE 660:
    
       660  W      POSTSCRIPT  FILE'S  (%%BOUNDINGBOX|LINE  LENGTH)
       VIOLATES ADOBE STRUCTURING CONVENTIONS
    
       EXPLANATION:  A POSTSCRIPT FILE WAS SPECIFIED ON  .PO  WHICH
       HAD RECORD LENGTHS GREATER THAN THE MAXIMUM ALLOWED BY ADOBE
       STRUCTURING   CONVENTIONS   OR   HAD  REAL  NUMBERS  ON  THE
       BOUNDINGBOX COMMENT.
    
       SYSTEM ACTION:  REAL NUMBERS ARE TRUNCATED.  LONG LINES  ARE
       INCLUDED  BUT COULD PREVENT DCF FROM FINDING NEEDED COMMENTS
       IN THE POSTSCRIPT FILE.  PROCESSING CONTINUES.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PL38967

  • Reported component name

    5748 DOC COMP F

  • Reported component ID

    5748XX900

  • Reported release

    136

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1989-02-13

  • Closed date

    1989-02-24

  • Last modified date

    1989-07-21

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UL47158 UL47159 UL47160

Modules/Macros

  •    DSMCS    DSMCSMDM DSMLPKPO DSMPSWA  DSMTFPWG
    DSMTFWPS DSMTFWRB
    

Fix information

  • Fixed component name

    5748 DOC COMP F

  • Fixed component ID

    5748XX900

Applicable component levels

  • RA32 PSY UL47158

       UP89/03/04 I 096G

  • R132 PSY UL47159

       UP89/03/02 P F903

  • R136 PSY UL47160

       UP89/03/02 P 8902

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU050","label":"BU NOT IDENTIFIED"},"Product":{"code":"SRNQ2D","label":"Document Composition Facility"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"136"}]

Document Information

Modified date:
26 September 2024