I think its much easier to define yourself a second userid and place the
code to test in SFS, yielding one user to test, the other to XEDIT the
code.  That's how I worked for years.  Can e done without SFS too, but then
the tester would have to reACCESS the code minidisk after each change.

Multitasking is only really usable from C or Assembler programs (and by
MtRexx), anyhow: for service machines.  Special applications could indeed
use dialed screens, but I don't know any.

2010/7/5 <[email protected]>

>  Hi Florian,
>
>
>
> It sounds like you want Yvette from the VM downloads page.
>
>
>
> Peter
>
>
>
> -----Original Message-----
> *From:* The IBM z/VM Operating System [mailto:[email protected]] *On
> Behalf Of *Florian Bilek
> *Sent:* July 5, 2010 13:15
> *To:* [email protected]
> *Subject:* Second screen in a z/VM CMS session
>
>
>
> Dear all,
>
> I am wondering if there is a utility available that would allow to use a
> dialed screen to a VM running CMS?
>
> As I understand, there is the possibility to make multitasking applications
> under CMS. Also full screen is supported nowadays.
> It would be great to have on one screen a REXX procedure edited while on
> the VM console that exec could be tested.
>
> Thank you very much in advance.
>
> --
> Best regards
>
> Florian
>
> ------------------------------
> The information transmitted is intended only for the person or entity to
> which it is addressed and may contain confidential and/or privileged
> material. Any review retransmission dissemination or other use of or taking
> any action in reliance upon this information by persons or entities other
> than the intended recipient or delegate is strictly prohibited. If you
> received this in error please contact the sender and delete the material
> from any computer. The integrity and security of this message cannot be
> guaranteed on the Internet. The sender accepts no liability for the content
> of this e-mail or for the consequences of any actions taken on the basis of
> information provided. The recipient should check this e-mail and any
> attachments for the presence of viruses. The sender accepts no liability for
> any damage caused by any virus transmitted by this e-mail. This disclaimer
> is property of the TTC and must not be altered or circumvented in any
> manner.
>



-- 
Kris Buelens,
IBM Belgium, VM customer support

Reply via email to