Configuring the IMS Base Primitive Environment for IMS Connect

The IMS Connect address space is built on top of the Base Primitive Environment (BPE).

Changing the BPE configuration parameter member of the IMS PROCLIB data set

The BPE configuration parameter member of the IMS PROCLIB data set defines BPE execution environment settings for the IMS Connect address space. You specify the IMS PROCLIB data set member name by coding BPECFG=member_name on the EXEC PARM= statement in the IMS Connect address space startup JCL, as shown in the following example: 

EXEC HWSHWS00,PARM='BPECFG=BPECFGHW'

You can use the BPE configuration parameter member of the IMS PROCLIB data set to specify the following items:

  • The language used for BPE and IMS Connect messages
  • The trace level settings for BPE and IMS Connect internal trace tables

The keywords that are available for the BPE configuration parameter member of the IMS PROCLIB data set are LANG= and TRCLEV=.

Avoid coding statements in the BPE configuration member that specify definitions for the same resources more than one time. For example, do not specify multiple TRCLEV statements for the same trace table type, or multiple EXITMBR statements for the same IMS Connect. BPE uses the last statement it encounters in the member. Any values that are specified on earlier duplicate statements are ignored. A message BPE0017I is issued for each duplicate found.

The IMS Connect Recorder trace table, RCTR, requires explicit commands, and therefore, is not processed if a default TRCLEV statement, TRCLEV=(*, ,HWS), is defined for IMS Connect. Recorder trace table configuration must be explicitly specified with a separate, additional TRCLEV statement. For example: TRCLEV=(RCTR,MEDIUM,HWS).
Recommendation: Enable the RCTR trace by issuing the BPE UPDATE TRACETABLE command. Use the BPE configuration member only if you must capture the trace before the BPE UPDATE TRACETABLE command can be issued.

Formatting incore trace tables

IMS Connect trace tables are incore tables, which can be formatted from a dump of an IMS Connect address space using the IMS Connect dump formatter. The traces are formatted by the standard BPE formatting services.

Example of a configuration file for BPE

A sample BPE configuration data set is shown in the following figure.

********************************************************************
* CONFIGURATION FILE FOR BPE                                       *
********************************************************************
 
LANG=ENU                             /* LANGUAGE FOR MESSAGES     */
                                     /* (ENU = U.S. ENGLISH)      */
 
#
# DEFINITIONS FOR BPE SYSTEM TRACES
#
 
TRCLEV=(*,LOW,BPE)                   /* DEFAULT TRACES TO LOW     */
TRCLEV=(AWE,HIGH,BPE)                /* AWE SERVER TRACE ON HIGH  */
TRCLEV=(CBS,MEDIUM,BPE)              /* CTRL BLK SRVCS TRC ON MED */
TRCLEV=(DISP,HIGH,BPE,PAGES=12)      /* DISPATCHER TRACE ON HIGH  */
                                     /* WITH 12 PAGES (48K BYTES) */
#
# DEFINITIONS FOR IMS CONNECT TRACES
#
 
TRCLEV=(*,HIGH,HWS)      /* DEFAULT ALL IMS CONNECT TRACES TO HIGH     */
TRCLEV=(HWSI,MEDIUM,HWS) /* BUT RUN IMS CONNECT TO IMS OTMA TRACE...   */
TRCLEV=(HWSW,MEDIUM,HWS) /* AND SERVER TO IMS CONNECT TRACE AT MEDIUM  */
TRCLEV=(RCTR,MEDIUM,HWS) /* AND SET RECORDER TRACE TO MEDIUM BECAUSE   */
                         /* IT IS NOT PROCESSED WITH THE ALL DEFAULT   */