Use the following steps to test a server:

1. Make sure that you have the following data sets available for your MVSSERV session:
   • The server and its initialization/termination program, installed in a STEPLIB in your logon procedure.
   • An input parameter data set, containing the name of the initialization/termination program.
   • A trace data set, to receive MVSSERV messages.

   For information about allocating the data sets, refer to Installing Programs and Data Sets for Use with MVSSERV. You may also want to have the dump data set and the dump suppression data set described in Installing Programs and Data Sets for Use with MVSSERV.

2. To start the MVSSERV session, log on to TSO/E and issue the MVSSERV command.
   MVSSERV has the following syntax, with the default underlined:

   MVSSERV      [ NOTRACE ]
                [ TRACE   ]
                [ IOTRACE ]

   For the test, use the TRACE option. TRACE produces messages in the trace data set about internal MVSSERV events, including server failures.

   Note: The method used to refresh the MVSSERV logo depends on your type of terminal support.
3. Switch to the PC session. (If you are using a PC other than the 3270 PC, issue the appropriate Enhanced Connectivity Facility command for the PC.)
4. Invoke the requester that corresponds to the server you want to test.
5. Respond to any messages from the requester. The requester should issue messages about any non-zero return codes from the server.
6. Verify that the request was satisfied.
7. Switch back to the host session and press the PF3 key to end MVSSERV.
8. Note any messages that appear on your screen. Each message has a message ID, beginning with CHS. In TSO/E, you can obtain online help for MVSSERV messages by typing the message ID in the following command:

   HELP MVSSERV MSG(CHSxxxxxxx)

9. Read the trace data set. Because you used the TRACE option when invoking MVSSERV, the trace data set should have recorded informational and error messages about events in the session and any errors that may have occurred. The trace data set should also contain any messages that the server issued with the default, TRACE, or BOTH options of the CHSTRACE macro.

   For information about reading the trace data set messages, see Diagnosing Servers.

10. When the server works properly, you may want to copy it to a system library such as SYS1.LPALIB to make it available to other users. Make sure that the other users allocate the input parameter data set in their logon procedures, in a CLIST, REXX exec, or ISPF dialog, or in line mode TSO/E. After you copy the server to a system library, be sure to retest it.