Waterloo Script and INLINE page segments

Thread View: bit.listserv.script-l

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Rick Marsico Thu, 15 Oct 1992 13:13

#22

Author: Rick Marsico
Date: Thu, 15 Oct 1992 13:13

14 lines
1207 bytes

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.
 
In editing the output generated by script with the I3820 option, the
requested segment is inline, however, SFCM is not recognizing its
existence.  Anyone encounter this problem?
 
Rick Marsico
rick@ysu.edu

Re: Waterloo Script and INLINE page segments

#25

Author: Rick Marsico
Date: Thu, 15 Oct 1992 16:00

25 lines
1595 bytes

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.
>
>In editing the output generated by script with the I3820 option, the
>requested segment is inline, however, SFCM is not recognizing its
>existence.  Anyone encounter this problem?
>

Further investigation shows that the graphic segment is not being
processed properly by the I3820 post processor.  It is generating
message i38-027W 'graphic segment contains invalid data'.  This
causes I3820 to process as if the NOSEGLIB option was specified.

The segment was created using the IBM IHF V2.1.2 utility.

rick@ysu.edu

Re: Waterloo Script and INLINE page segments

#23

Author: Rick Marsico
Date: Thu, 15 Oct 1992 17:20

23 lines
1618 bytes

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

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads