|
I *think* I posted this question to the list, can't seem to find the
message in my mail....
Resolution: There appears to be a bug appearing when using multiple
FILENAME PIPEs used in a single data step under display manager, in
version 6.11 of SAS on HPUX. This bug is not present in 6.12. Because
6.12 for HPUX has shipped (li'l birdie told me so), the bug will not be
fixed in 6.11. This is a known bug on HPUX, I don't know whether or not
it effects other UNIX platforms.
Synopsis: Using multiple filename pipes in a single data step causes
processing to 'hang'. Selecting 'Interrupt' from the SAS Session
Manager will allow SAS log NOTEs for the data step to be printed to the
log, processing hangs again at this point. A second 'Interrupt' causes
the DM session to close. We maintain an 'altlog' for DMS sessions -- no
log output from the effected data step is written to the file (we
haven't tried using the NOLOGBUF option). SI is aware of the situation,
it appears to be a bug, and it will not be fixed in 6.11 as the bug is
not present in the current release (6.12).
The same code in a batch (non-interactive) session will run
successfully.
Sample code replicating bug:
>* The following code should crash a DM Session
>* but run successfully in batch.
* Use with caution
>* YOU WILL LOSE YOUR UNSAVED WORK IN THE CURRENT SAS SESSION.
;
>filename ls pipe 'ls';
>filename ps pipe 'ps';
>data out;
> length text $200;
>
> infile ls lrecl=200 pad;
> input text $200.;
> output;
>
> infile ps lrecl=200 pad;
> input text $200.;
> output;
>
> run;
| 
