II05755: INFO-ONLY APAR CREATED FOR POSTSCRIPT INTERPRETER. CONTAINS TIPS FOR USERS AND SUPPORT REPS.

APAR status

• INTRAN

Error description

• This information applies to Publishing Solutions PostScript
  Interpreter compid 568810401.  This information is for
  release 1.3.1 (retain release 133 for VM and 134 for MVS.
  HPFN134)
  Q. LMCOPY failure trying to run sample job on MVS.
  A. ISPF APAR OY44735 addresses this issue.  Ship PTF to customer
  Q. Errors running with level 2 postscript.
  A. Level 2 PostSCript is not supported by the Interpreter. The
     error will show as:  Error undefined offendingcommand XXXXXX
     where XXX is a level 2 PostSCript operator.
  Q. Using Adobe fonts with OGL.
  A. This is not supported.  OFL requires that specifcations for
     all 4 rotations be included in the character set that is
     uses.  Other applications do not ahve this and can work with
     single rotation character sets.
  Q. IRX0670E execio error while tyring to get or put a record.
  A. The PREFIX.PX.VM data set is empty.
  
  Q. Print wraps around from one row to the next.
  A. Requires new MASTERPS VM and PS MODULE.
  
  Q. PSEG3820 created by screen capture program has 1 inch cut
     off side.
  A. This is caused by the EPS file.  If the input postscript file
     is multiple pages, all of those pages will be overlayed on
     each other and only one page of output will be generated.
     This particular program had two pages, one of screen capture
     and the other with a band of which overlayed some of the
     screen capture.  This won't be noticed on a list3820 because
     the entire second page will be white but it will be noticed
     on a pseg3820 because of the overlay problem.  Delete the
     second page from the input file and the pseg3820 will be ok.
  
  Q. How does a user remove control characters in batch.
  A. This is not supported but the following may work.  Before
     step 2 in the JCL where the Interpreter is called, the fol-
     lowing must be done:
  1. A data set must be allocated like the input data set.  This
     will be the data set that will contain the original input,
     but with the controls removed.
  2. Allocate the ddname psout to the newly-created data set.
  3. Allocate the ddname pslist to the original input data set.
  4. Execute the program ehyzap.
  5. Free the two ddname allocations.
  6. Execute the existing step 2 in the JCL, but on line 32 use
     the name of the new data set that was created with the con-
     trols removed, instead of the original data set name.
  
  Q. When tyring to import a pseg3820 file created by the post-
     script interpreter into the ivu, an abend0c4 occurs in the
     admerooo at offset X'506' on a mvi instruction.  this is
     also referred to as the 'tiling' problem.
  A. Apply the ptf for APAR PL57745 for GDDM-VM version 2.
  
  Q. Operation failed message at the Build list data set options.
  A. Output data set or directory blocks not big enough.
  
  Q. Poor performance caused by ps.vm datasets created fixed,80,80
  A. Restriction caused by the "C" program offering.  PS.VM can be
     re-blocked to a bigger size, e.g. 6160 works ok.
  
  Q. Stack underflow with scale or error in printing landscape
     pages (not rotated) caused by oem pc program.
  A. The error seems to be an omission of an exec operator in the
     fmdocument procedure.  The lines befoe the "/yscale exch
     def" line put a procedure on the operand stack and the pro-
     cedure must be executed before /yscale is defined.
  
  Q. Slow printing on a 3827.
  A. 300 dpi pc-type documents must be converted to 240 dpi 382x
     documents.  This results in the Interpreter output being
     considered "complex" by the printer as opposed to "normal"
     DCF-type documents.  There are no current plans to produce
     IOCA or GOCA outputs.
  
  Q. Error limit check offendingcommand: (#$%^#$% garbage).
  A. File may be EBCDIC format on the host and the first 2 char-
     acters are not %!  The Intepreter can handle either ASCII or
     EBCDIC but uses the %! to determine the file format.
  
  Q. OEM pc software produces strange output/error conditions.
  A. The /yscale exch def is expecting to pull a numeric value
     off the stack.  However, the code prior to this has actually
     left a procedure on the stack which has not been executed.
     The /yscale exch def is actually pulling this procedure off
     the stack instead of the numeric value that is should be
     pulling and this appears to be causing the problems.  The
     input code can be altered as follows:
     {desperatepapersize} if
     exec
     /yscale exch def
  
  Q. How can I tell if input file is using PostScript level 2.
  A. Look for %%languagelevel: 2 in the file.  Other level 2 op-
     erators are defined in the PostSCript Language Ref Manual.
  
  Q. LMCOPY failure.
  A. Per ISPF support:  ISPF maintenance must be applied to the
     ISPLLIB as well as the step lib.
  
  Q. %%BoundingBox error trying to convert EPS to PSEG.
  A. A valid EPS file has to have BoundingBox in it.  Showpage
     must be added for output.
  
  Q. Offending command I/O error.
  A. VM- a disk may be full.  MVS- data set may be full.
  
  Q. Offending command run.
  A. File or data set does not exist.
  
  Q. Offending command file.
  A. Wrong parameters on data set or file.
  
  Q. Error limit check frame device.
  A. VM error- not enough memory.
  
  Q. Error typecheck offending command length.
  A. PostScript file defective.  Try a different PostScript file.
  
  Q. Error undefined offending command XXX.
  A. Input file or data set is processed as ASCII and it is not.
     Make sure first 2 characters in file are %!
  
  Q. %% error typecheck offending command put %%
  A. Installed typefaces or created fonts are corrupted.
  
  Q. Error stack underflow.
  A. Operation being executed can't find values for scale x and y.
  
  Q. Does virtual memory have to be created fixed, 80, 80?
  A. Yes, but it can then be copied to a data set of fixed, 80, X
     where X is a multiple of 80.
  
  Q. Can the Interpreter run without virtual memory & font cache?
  A. No, start3820 and other operators require both.
  
  Q. EHYL3820 & 4250 and EHYP3820 & 4250 missing from 1.3.1 tape.
  A. The above 4 execs have been replaced by EHYPS1 and EHYPS2.
     Running them from the command line is not supported.
  
  Q. Terminal attention interrupt handling not reset properly.
  A. Refer to APAR PL77906.  C program offering restriction.
  
  Q. How to run the Interpreter from the TSO command line.
  A. Here are 2 calls that can be used to create LISTXXXX and
     PSEGXXXX.  These are TSO commands that msut be issued from
     the TSO command line or be preceded by the letters TSO.  The
     commands are case sensitive.
  
     LISTXXXX:
     ps -i 'masterps name' -e "prestart (output name)start3820
     save pop (input ps name)run end3820 bye"
     PSEGXXXX:
     ps -i 'masterps name' -e "prestart/showpage {} def WIDTH in
     72nd of an inch HEIGHT in 72nd of an inch (output name)pseg
     3820 save pop (input ps name) systemdict /showpageget exec
     bye"
  
  Q. Can I use 3820 fonts with PostScript Interpreter in DCF?
  A. The fonts created with the Interpreter can only be used with
     the Interpreter.  The glyph names and hex code points are not
     currently compatible with other AFP applications.
  
  Q. What causes batch font errors when creating fonts?
  A. There is a limit, based on free virtual memory that you have
     available, or have defined at logon, on the number of fonts
     that can be created in "one pass".  When you exceed the limit
     it is recommended that you create multiple fonts containing
     a number of fonts slightly less than your limit and run
     multiple jobs to create all of the fonts you need.
  
  Q. Use default options does not show on build list or pseg panel
  A. Issue the PFSHOWOFF command.  PF keys overlay the line.
  
  Q. MSGBFU203I with prefix 'PRT' indicates printer problems or
     problems with CDPF.  Or, MSGBFU021E data rejected by printer.
  A. Apply 4250 fix files available from Publishing Solutions.
  
  Q. RC=12 from allocation in module EHYPSCOM.
  A. On page 41 of the MVS PSI User's Guide under the heading
     "Customing the Profile" there are 2 members of the EHY.
     PSINTERP.EHYEXC1 data set that have to be edited.  The mem-
     bers are EHYPPROF and EHYMSPS.  The members have to be chang-
     ed to reflect the names of the customer's system font data
     set for 3820 fonts.  We ship the members as AFP.FONTLIBB but
     most customers do not use that name.
  
  Q. Unable to convert fonts.  Get the following error messages:
     font unavailable for conversion, nostringvalue- not found,
     check data set for messages, rangecheck, offending command,
     readline, bad data set format, error, bad file format.
  A. The prefix.FCONVERT.COMMANDS data set has to be allocated
     variable, unblocked, 80.  The customer than has to use this
     as the input for the project, group, type, and member for
     option 2 under the "building a 3820 font from PostScript
     typefaces" panel.
  
  Q. Does the Interpreter support binary PostScript files.
  A. No, this is a level 2 PostScript feature.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

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

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

Fix information

Applicable component levels