#! /bin/sh
#
# @(#)setERRORFILE	1.3	LPS_UNX_COM	2/19/95
#
# Copyright 1993   Digital Equipment Corporation, Maynard, MA
#
# setERRORFILE
#
# A script that produces a value for attribute ERRORFILE
#
# Parameters:
#    $1 - LPS class identifier, one of {PC, MC, PS, ENV}
#    $2 - Operating system type identifier (eg: SV2, BSD, etc)
#    $3 - Print client type identifier (eg: AIX, BSD, SV3, etc)
#    $4 - PrintServer printer model (eg: LPS17, LPS20)
#    $5 - Default value for the attribute
#    $6 - Path of the output file to receive the final attribute value
#
# Global variables:
#    ECHON
#    FUNCS
#    PAGER
#
# Exit values:
#    0 - Success, output file contains newly set attribute value.
#    1 - Error or interruption occurred, error messages go to stderr,
#	 contents of the output file are undefined.
###

CLASS=$1
OSTYPE=$2
PCTYPE=$3
PSMODEL=$4
DEFVAL=$5
OUTFILE=$6

QUESTION="Error sheet file"

. $FUNCS

showhelp true "
${QUESTION}?

When a Print Client encounters a binary file in the print job, instead
of trying to print the file, a special PostScript(R) file is printed
in its place.  This \"error sheet\" file provides a visual cue to the
user to indicate the fact that a binary file was encountered.

A standard error sheet file is provided with the PrintServer
software, but you are able to specify an alternate file that contains
a custom PostScript(R) program to image the error sheet.

This question asks you to enter the path of the file containing the
PostScript(R) error sheet file.  Most sites choose the default error
sheet file.
"

getpath z "$DEFVAL" "$QUESTION"

if [ -z "$RESPONSE" ]
then
    RESPONSE="$DEFVAL"
fi

echo "$RESPONSE" > $OUTFILE

exit 0
