home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!lll-winken!news.larc.nasa.gov!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!news.ysu.edu!do-not-reply-to-path
- From: RICK@ysub.ysu.edu (Rick Marsico)
- Newsgroups: bit.listserv.script-l
- Subject: Re: Waterloo Script and INLINE page segments
- Message-ID: <16881BBAE.RICK@ysub.ysu.edu>
- Date: 15 Oct 92 17:20:33 GMT
- References: <1688181A1.RICK@ysub.ysu.edu>
- Sender: news@news.ysu.edu (Usenet News Admin)
- Organization: Youngstown State University
- Lines: 23
- Nntp-Posting-Host: ysub.ysu.edu
-
- In article <1688181A1.RICK@ysub.ysu.edu>
- RICK@ysub.ysu.edu (Rick Marsico) writes:
-
- >
- >I am encountering problems with inline page segments under Waterloo Script
- >90.1 in both the vm/cms and mvs environments. Under cms, the segment
- >will be properly processed by SFCM only when the SEnd option is included
- >on the PSF command. When '.si AAAA inline' is specified in the SCRIPT
- >routine (where AAAA is the name of a page segment with a file type of
- >PSEG3820), the following message is received back from SFCM:
- >APRFFI349S page segment AAAA PSEG38PP was not found.
- >
-
- I think I've discovered the problem. It appears that the release 90.1
- I3820 postprocessor cannot handle images created by the IBM IHF V2.1.2
- utility. The script I3820 processor flags the image as containing
- invalid data and thus forces the NOSEGLIB option. If I edit the
- PSEG3820 graphic segment and remove the comment inserted by IHF on the
- second line (which contains IHF version information), everything
- works fine.
-
- Rick Marsico
- rick@ysu.edu
-