One thing you might try is redirecting $stdlist to a message file and on
your second terminal session doing fcopy from the message file to your
terminal. I've never tried it this way, but I don't see why it wouldn't
work.

-Lane

on 11/20/00 12:50 PM, Chuck Ryan at [log in to unmask] wrote:

> This is something I have been concerned about since I do debug VPLUS
> applications.
>
> Unless someone knows a way to assign a nailed ldev to a network connection,
> anyone who wishes to debug a VPLUS application must purchase and maintain a
> DTC for that single purpose.
>
> This appears top be another example of HP's development tools not keeping
> pace with the technology of their systems.
>
>
>> -----Original Message-----
>> From: Jerry Fochtman [mailto:[log in to unmask]]
>> Sent: Monday, November 20, 2000 2:38 PM
>> To: [log in to unmask]
>> Subject: Re: [HP3000-L] Capturing error msg when Vplus prgm aborts
>>
>>
>> I can recall debugging program problems with VIEW/VPLUS that
>> involved routing the screens to another terminal device using
>> the file equation:
>>
>>           FILE A264X;DEV=
>>
>> That's when you had 2-window 262X-type terminals and had 2
>> assigned terminal ports.... :-)
>>
>>
>>
>>
>>
>>
>>
>> At 02:04 PM 11/20/00 -0500, Russ Smith wrote:
>>> Jay,
>>>
>>> Are you using ENTRY or do you have custom code scraping the
>> fields.  If the
>>> latter, set a file equation before you run the program such as "FILE
>>> STDLIST=MYSCR;DEV=LP,1;CCTL" and after the program
>> terminates (and you reset
>>> your session [damn block mode]), view the spoolfile.
>>>
>>> If you are using ENTRY, it may get a little fuzzy, because
>> you may not get
>>> the input fields displayed.
>>>
>>> HTH,
>>> Rs~
>>>
>>> Russ Smith, Systems Consultant
>>> Problem Solved, Vacaville, CA
>>> r s m i t h @ c u - h e l p . c o m
>>> h p 3 k - l @ e - 3 0 0 0 . n e t
>>>
>>> ----- Original Message -----
>>> From: "Jay Willis" <[log in to unmask]>
>>> To: <[log in to unmask]>
>>> Sent: Monday, November 20, 2000 9:32 AM
>>> Subject: [HP3000-L] Capturing error msg when Vplus prgm aborts
>>>
>>>
>>>> Greeting, friends.
>>>>
>>>> Can't seem to locate my notes on how to capture and print
>> the error
>>>> message a user gets when he's got a Vplus screen open and
>> his program
>>>> aborts, filling all the field windows with the message.
>> Or I *could*
>>>> learn speed-reading :-)
>>>>
>>>> Thanks,
>>>> Jay
>>>>
>>