CICS ONC RPC setup tasks

There are tasks associated with the CICS® ONC RPC data set, dump formatting, and a warning about migration.

Creating the CICS ONC RCP data set

JCL is provided in the DFHCOMDS job to create the CICS ONC RPC data set. The data set is defined as a VSAM key-sequenced data set by a DEFINE CLUSTER command like the following:

DEFINE CLUSTER (                    -
  NAME( xxxxxxxx.CICSONC.RESOURCE ) -
  CYL ( 2 1  )                      -
  KEYS( 19 0 )                      -
  INDEXED                           -
  VOLUME ( vvvvvv )                 -
  RECORDSIZE( 150 150 )             -
  FREESPACE( 5 5 )                  -
  SHAREOPTIONS( 1 )                 -
  )

The job to define the data set must be run before you start the connection manager for the first time.

JCL entry for dump formatting

To switch dump formatting on for CICS ONC RPC (and for all running features), change the IPCS VERBEXIT control statement as follows:

IPCS VERBEXIT DFHPD640 FT=2

The VERBEXIT provides a formatted dump of CICS ONC RPC control blocks.

Migrating between CICS versions

CICS ONC RPC was a separately-installed feature of CICS/ESA 3.3 and CICS for MVS/ESA 4.1, but is part of the CICS Transaction Server base. None of the IBM-supplied programs for CICS ONC RPC should be moved to CICS Transaction Server from earlier releases.

Modifying TCP/IP for MVS data sets

You can define the CICS TS region to TCP/IP for MVS™ in the tcpip.PROFILE.TCPIP data set to reserve specific ports for ONC RPC applications (described in TCP/IP for MVS: Customization and Administration Guide ).

Related concepts
ONC RPC concepts
Related tasks
Setting up CICS ONC RPC
Defining CICS ONC RPC resources to CICS
[[ Contents Previous Page | Next Page Index ]]