Setting up the TRANSMIT and RECEIVE environment

Before people at your installation can use the TRANSMIT and RECEIVE commands, you must:

Specify installation defaults that control TRANSMIT and RECEIVE processing, and system ID-node name associations, in one of the following:
- SYS1.PARMLIB member IKJTSOxx
- CSECT INMXPARM
Setting TRANSMIT and RECEIVE defaults in IKJTSOxx describes how to use IKJTSOxx, and Writing and installing the INMXPARM CSECT describes how to replace the IBM-supplied dummy INMXPARM CSECT with your version. Unless you use IKJTSOxx or replace the dummy CSECT, TRANSMIT and RECEIVE do not work.
Add TRANSMIT, its alias XMIT, and RECEIVE to the table of authorized commands. Specifying authorized commands/programs, and commands not supported in the background describes how to maintain that table either in the IKJTSOxx member of SYS1.PARMLIB, or in the IKJEFTE2 CSECT in load module IKJTABLS, which is in SYS1.LPALIB.
Check and, if necessary, modify JES initialization statements. The JES initialization statements must specify that SYSOUT data is to be written, that the output class is punched, and that the punched card output limit is large enough to transmit data sets. Modifying JES initialization statements lists the initialization statements you need to check.
Unless you are using RACF®, to enable users to issue RECEIVE in the background, ensure that their user IDs are placed in the ASXBUSER field of the ASXB control block. (RACF stores the user ID for you.) If the user ID is not stored in that field, RECEIVE does not work in the background. If you allow users to issue RECEIVE in the background, you might also need to write a RECEIVE pre-processing exit (INMRZ11R or INMRZ11) to respond to the prompts that RECEIVE issues to users.

After making TRANSMIT and RECEIVE available, you can use one or more TSO/E or JES exits to monitor or modify TRANSMIT or RECEIVE processing. Customizing TRANSMIT and RECEIVE describes the exits.