Any other type of IUCV external interrupts occurs and the path that it
occurs on is not owned by any activeCMS IUCV programs in the virtual
machine.
In either condition,CMS issues an IUCV SEVER for the path in error. The 16
bytes in theIPUSER field contain binary ones (X'F').
2. If aCMS abend occurs, the CMS lUCY environment is terminated. An IUCV RETRIEVE BUFFER is issued, and any exits set up by the CMSIUCV or
HNDIUCV macros are cancelled.
3.CMS IUCV clean up does not occur at end-of-command processing.
4. A program must be ready to handle any incoming external interrupts as soon as
a HNDIUCV orCMSIUCV macro has finished execution. A program may
even be interrupted before the next sequential instruction after the macro in
the program is executed.
Using CMSIUCV to Communicate Between Two Virtual Machines
Figure 41 on page 366 illustrates the sequence of macro instructions issued when a
virtual machine communicates with another virtual machine usingCMS IUCV. The functions performed by these instructions include:
initializingIUCV communications
connecting to another virtual machine
sending and receiving messages
replying to and waiting for messages
severing connections with the other virtual machine
terminatingIUCV communications. CMS IUCV Support 365
occurs on is not owned by any active
machine.
In either condition,
bytes in the
2. If a
HNDIUCV macros are cancelled.
3.
4. A program must be ready to handle any incoming external interrupts as soon as
a HNDIUCV or
even be interrupted before the next sequential instruction after the macro in
the program is executed.
Using CMS
Figure 41 on page 366 illustrates the sequence of macro instructions issued when a
virtual machine communicates with another virtual machine using
initializing
connecting to another virtual machine
sending and receiving messages
replying to and waiting for messages
severing connections with the other virtual machine
terminating