| The problem has occurred because the text dataset mechanism in ALL-IN-1
V2.4 and V3.0 recognises more file types.
V2.3 did not have a PostScript text dataset so a file type of .PS, like all
unrecognised file types, caused the text dataset mechanism to default to
ASCII.
A PostScript text dataset was added to V2.4, so files with a file type of
.PS are processed by that new dataset. The PostScript text dataset does
not support record mode operations because PostScript is a final-form
format which cannot be converted to and from the revisable formats
supported by the text dataset mechanism.
There are two ways around the problem:
1. Change the append function to:
APPEND 'TEST.TXT' 'TEST.PS' TXT$DSAB_ASCII TXT$DSAB_ASCII
This overides the normal selection of the text dataset from the file
types and forces the input and output to be performed using the ASCII
text dataset.
2. Change the append function to:
APPEND/FILE 'TEST.TXT' 'TEST.PS'
/FILE is a new qualifier in V3.0 which tells APPEND to perform the
operation directly on the RMS files. It does not use the text dataset
mechanism so will be more efficient that method 1.
> If the APPEND function's destination file extension has a .wpl or
> .txt or even .p there is no error.
There wasn't an error but if you look at the output file it will not
contain the PostScript but instead contain the line:
PostScript document type cannot be displayed.
This is because the PostScript text dataset does not support record mode
oeprations. If you try to do a record mode READ the message above will be
placed into the output stream (similar to the FOREIGN text dataset). If
you try to do a record mode WRITE you get an error because the dataset does
not support such operations.
Richard
|