How to set up RMF XP

To start the GPM4CIM server from the console, RMF™ provides procedure GPM4CIM as a member in SYS1.PROCLIB, which you must modify according to your needs:

Figure 1. RMF XP startup member in SYS1.PROCLIB(GPM4CIM)

//GPM4CIM PROC  OS=A 
//********************************************************************
//*  STEP 1 - Execute GPM4CIM                                        *
//********************************************************************/
//STEP1    EXEC PGM=BPXBATCH,TIME=NOLIMIT,REGION=0M,
//       PARM='PGM /usr/lpp/gpm/bin/gpm4cim  cfg =/etc/gpm/gpm4 &OS. .cfg'
//STDENV   DD   PATH='/etc/gpm/ gpm4cim.env '
//STDOUT   DD   PATH='/var/gpm/logs/gpm4cim&OS..out',
//         PATHOPTS=(OWRONLY,OCREAT,OTRUNC),
//         PATHMODE=(SIRUSR,SIWUSR,SIRGRP)
//STDERR   DD   PATH='/var/gpm/logs/gpm4cim&OS..trc',
//         PATHOPTS=(OWRONLY,OCREAT,OTRUNC),
//         PATHMODE=(SIRUSR,SIWUSR,SIRGRP)
//********************************************************************
//*  STEP 2 - Copy stdout back to joblog                             *
//********************************************************************/
//STEP2    EXEC PGM=BPXBATCH,
//         PARM='PGM /bin/cat /var/gpm/logs/gpm4cim&OS..out'
//STDOUT   DD   SYSOUT=*
//STDERR   DD   SYSOUT=*
//********************************************************************
//*  STEP 3 - Copy stderr back to joblog                             *
//********************************************************************/
//STEP3    EXEC PGM=BPXBATCH,
//         PARM='PGM /bin/cat /var/gpm/logs/gpm4cim&OS..trc'
//STDOUT   DD   SYSOUT=*
//STDERR   DD   SYSOUT=*
//********************************************************************
//         PEND

The procedure invokes the IBM-supplied BPXBATCH utility which passes control to the gpm4cim load module. This module is located in the HFS directory /usr/lpp/gpm/bin.

The cfg parameter in the PARM statement points to the GPM4CIM configuration file. Since one instance of GPM4CIM is needed per platform, no unique configuration file is used. You can supply different configuration files using the OS variable to denote the target platform:

A: AIX® on System p® (as shown in the example from Figure 1)
X: Linux on System x®
Z: Linux on System z®
W: Windows on System x

For the GPM4CIM procedure, the environment variables are kept in file gpm4cim.env which is specified with the STDENV ddname. Log and trace output is written to the files specified with the STDOUT and STDERR ddnames. If multiple instances of GPM4CIM are running simultaneously, you can specify individual output files by altering the file names in the PATH parameter.