### Creating and modifying Remote DL/I TP profiles

You can use the APPC/MVS administration dialog or the APPC/MVS administration utility (ATBSDFMU) to create, modify, and delete your Remote DL/I TP profiles. For detailed information about maintaining TP profiles on MVS, see MVS/ESA Planning: APPC Management.

The following sections discuss what you need to know to successfully set up a Remote DL/I TP profile.

#### Specifying the MVS message log

When you create your TP profile, you will want to decide how you want to handle the MVS message log. For example, a new message log dataset can be created each time the TP is run. You can set up your message log in a variety of other ways. For example, you could define a message log dataset for each TSO user and have a dataset status of MOD. It is recommended that the KEEP_MESSAGE_LOG be set to ALWAYS. This will ensure that all of the necessary diagnostic information is available if there is a problem that needs to be diagnosed.

#### Specifying the TPNAME

The setting for the TPNAME must match the name you used when setting the TP name in the RMTDLI_PARTNER_TP environment variable.

#### Specifying the schedule type

The setting for the schedule type must be set to TPSCHED_TYPE(STANDARD).

#### Specifying the JCL

In your TP profile definition, you must specify JCL that can be used to run the Remote DL/I server code along with an IMS batch environment.

JOB Statement
  A JOB statement is required in the JCL. If you specify MSGLEVEL, then we recommend specifying MSGLEVEL(1,1) to ensure that the MVS message log output is available.
EXEC Statement
  You must specify an EXEC statement with PGM=IWZRDM01. In addition, you must provide a parameter string with the PARM parameter. The PARM parameter must be a string that can be passed to IMS when starting the IMS batch environment. Remote DL/I will always substitute the first three parameters with its own values, but it will pass the rest of the parameters as specified in the PARM value.
DD Statements
  The DD statements in the TP profile JCL are discussed below. When you set up a TP profile you need to decide which DD statements you want to have set in the TP profile and which ones you want to set using the Remote DL/I Server Environment File. You cannot specify the STEPLIB or JOBLIB DD statements in the Server Environment File. There are limited capabilities when you use the Server Environment File in terms of how a DD can be allocated.
  STEPLIB or JOBLIB
    A STEPLIB or a JOBLIB DD statement is required to specify the dataset names for:
    - The Remote DL/I dataset that has the Remote DL/I load modules.
    - The Language Environment SCEERUN dataset.
    - The IMS RESLIB dataset.

    If any of the above datasets are available in the LNKLST then they do not need to be specified in the STEPLIB or JOBLIB.

  DFSRESLB
    The DFSRESLB DD statement is used to point to an authorized library that contains the IMS SVC modules.
  IMS
    The IMS DD statement points to datasets that contain the PSBs and the DBDs.
  IEFRDER and IEFRDER2
    The IEFRDRER and IEFRDER2 DD statements are used to define the IMS system log datasets.
  DFSVSAMP
    The DFSVSAMP DD statement is used to specify buffer pools. If you need to specify the DFSVSAMP DD statement, you must have it specify a dataset name. Inline values using a DD * approach are not supported in a TP profile.
  Database DD
    The DD statements for the IMS databases you want to access can be specified.
  SYSUDUMP
    The SYSUDUMP DD statement can be specified to obtain a system dump if there is an ABEND.
  IWZRDOUT
    The IWZRDOUT DD statement is used to identify where Remote DL/I will write its messages.

For information about the DD statements used in a IMS batch environment, see IMS/ESA System Definition Reference.

Figure 2 is an example of the JCL used in a Remote DL/I TP profile.