Communicating with VM/CMS Virtual Machines › z/OS to z/VM Client/Server Application › Client Message Disposition

Client Message Disposition

Incoming messages from clients are handled by two startup parameters:

• Destination
• Disposition

Specify the disposition as WTO only, Global Variable (GLV) only, or a combination of both. If the GLV option is selected, the destination must specify the GLV name for storing messages.

Consider these several points when using GLV message handling:

• Specify the GLV name as a startup parameter, zosdest, and the name syntax must adhere to CA OPS/MVS Global Variable naming conventions.

  The name may contain a double ampersand (&&), which will be substituted with the client VMuserid and VMnode. For example, if the destination name is 'GLOBALZ.&&.MESSAGES', the derived name may become 'GLOBALZ.CLIENTA.SYSTEMC.MESSAGES'. One GLV name may be sufficient in some cases, but the substitution option allows separate GLV storage for individual clients.

• New messages are added to the end of the existing GLV value.

  The individual messages are similar to WTO output, except they have no message prefix, and a separator character, X'15', is appended to the end. Message separation could be done on the basis of character mask parsing with X'15' as a delimiter.

• The GLV is not reset each time the server comes up.

  It is the responsibility of each site to periodically empty the GLV, and reset it when appropriate.

  Note: A REXX procedure to extract client messages and write to a DASD data set is shown in sample program OPVMGLV.