Re: swap QTEMPs

[Francesco Scafi <fscafi@xxxxxx>]

Hi Peter,
how sndbrkmsg acquire video and visualizes the message, so he 
could also be called a program? 

Francesco.

At 13.56 16/12/99 -0800, you wrote:
>Hi Francesco,
>
>I'm not sure what your comment was about, but if you meant that the target
>job has to create the message queue and set the break handling program, yes,
>that's true. It also appears to be the case in Gary's method that the target
>job is the one that has to stuff the address of the permanent context
>(library) into it's PCO before another job can use that library to access
>the target job's QTEMP.
>
>Peter Dow
>Dow Software Services, Inc.
>909 425-0194 voice
>909 425-0196 fax
>
>From: Francesco Scafi <fscafi@tin.it>
>> In this case it is necessary a target job...
>>
>> At 14.15 13/12/99 -0800, you wrote:
>> >You can do something similar with a message queue without using MI. In
>the
>> >job you want to look at, create a message queue with a break handling
>> >program that will use received messages' text as an AS/400 command, and
>set
>> >the message queue's delivery to break. Then from any other job, simply
>send
>> >a break message to that queue with a command as the text.
>>
>> >From: Gary Guthrie <GaryGuthrie@home.com>
>> >> Or how about storing a pointer to a permanent context (library) as a
>> >> pointer to QTEMP. I've done that before, too. That can be interesting.
>> >> It's handy for testing things done with another job's QTEMP objects.
>For
>> >> instance, you might have a job that's creating things in QTEMP and
>> >> things aren't going as expected. Create a permanent context, stuff it's
>> >> address in the PCO as if it's QTEMP, and let the job continue. Now from
>> >> another job you can perform all the normal OS/400 commands against the
>> >> job's QTEMP, because it's a permanent context with a normal library
>name
>> >> you can use in the commands.
>> >
>>
>> +---
>> | This is the MI Programmers Mailing List!
>> | To submit a new message, send your mail to MI400@midrange.com.
>> | To subscribe to this list send email to MI400-SUB@midrange.com.
>> | To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
>> | Questions should be directed to the list owner/operator:
>dr2@cssas400.com
>> +---
>>
>
>+---
>| This is the MI Programmers Mailing List!
>| To submit a new message, send your mail to MI400@midrange.com.
>| To subscribe to this list send email to MI400-SUB@midrange.com.
>| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
>| Questions should be directed to the list owner/operator: dr2@cssas400.com
>+---
>
+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---