Defining, saving, modifying, and deleting 4-tuples

The first panel for defining, saving, modifying, and deleting 4-tuples is DFHRP03. (See Figure 45.) This panel is shown as soon as you have enabled CICS® ONC RPC, or if you choose option 2 on panel DFHRP10.

Figure 45. Panel DFHRP03
CRPC                        CICS ONC RPC for MVS/ESA                   DFHRP03
                          Remote Procedure Registration
 
Select one of the following. Then press Enter.
 
_  1. Register procedures from the data set
   2. List procedures sequentially
   3. Register a new procedure
   4. Retrieve a specified procedure from the data set (Enter required data)
           Program Number      ===> ________   0-FFFFFFFF
           Version Number      ===> ________   0-FFFFFFFF
           Procedure Number    ===> ________   1-FFFFFFFF
           Protocol            ===> UDP        Udp | Tcp
 
 
 
 
 
 
Current Status: Enabled
 
 
                                                  SYSID= CI41  APPLID= IYK1ZFL1
PF1=Help   PF3=Exit   PF9=Messages   PF12=Return
 

If you wish to select option 4, you must first supply the following information:

Program Number
The program number of the 4-tuple whose definition is to be retrieved.
Version Number
The version number of the 4-tuple whose definition is to be retrieved.
Procedure Number
The procedure number of the 4-tuple whose definition is to be retrieved.
Protocol
The protocol of the 4-tuple whose definition is to be retrieved.

Select an option, then press Enter.

Option
For more information see:
1
See below.
2
Defining the attributes of a 4-tuple
3
Unregistering 4-tuples
4
See below.

If you select option 1, the 4-tuples in the CICS ONC RPC data set that have YES for their Register from Data Set attribute are all registered.

If you specify a 4-tuple for which there is no definition in the CICS ONC RPC data set, a message is issued when you press Enter, and panel DFHRP03 remains on the screen.

Defining the attributes of a 4-tuple

When you select option 3 or option 4 on panel DFHRP03, panel DFHRP5 is shown. (See Figure 46.) If you chose option 3, some of the fields are empty, but if you chose option 4, the details of the selected 4-tuple are shown. You have to supply more information on panel DFHRP5B.

Figure 46. Panels DFHRP5 and DFHRP5B
CRPC      CICS ONC RPC for MVS/ESA Remote Procedure Registration       DFHRP5
 
Overtype to Modify. Then press Enter to Validate
 
  ONC RPC ATTRIBUTES
   ONC RPC Program Number   ===>  ________         0-FFFFFFFF
   ONC RPC Version Number   ===>  ________         0-FFFFFFFF
   ONC RPC Procedure Number ===>  ________         1-FFFFFFFF
   Protocol                 ===>  UDP              Udp | Tcp
   RPC Call Type            ===>  BLOCKING         Blocking | Nonblocking
   Inbound XDR Routine      ===>  ______________
   Outbound XDR Routine     ===>  ______________
  CICS ATTRIBUTES
   ALIAS Transaction ID     ===>  CRPA
   EDF Terminal ID          ===>  ____
+  Program Name             ===>  ________
 
 
 
Current Status: Enabled
 
 
                                                  SYSID= CI41  APPLID= IYK1ZFL1
PF1=Help   PF3=Exit   PF4=Save   PF8=Forward   PF9=Messages   PF12=Return
 
CRPC      CICS ONC RPC for MVS/ESA Remote Procedure Registration       DFHRP5B
 
Overtype to Modify. Then press Enter to Validate
 
+ CICS ONC RPC ATTRIBUTES
   Converter Program Name   ===>  ________
   Encode                   ===>  NO               Yes | No
   Decode                   ===>  YES              Yes | No
   Getlengths               ===>  YES              Yes | No
     Server Input Length    ===>  _____            0 - 32767 Bytes
     Server Output Length   ===>  _____            0 - 32767 Bytes
     Server Data Format     ===>  CONTIGUOUS       Contiguous | Overlaid
   Register from Data set   ===>  YES              Yes | No
 
 
 
 
 
 
Current Status: Enabled
 
 
                                                  SYSID= CI41  APPLID= IYK1ZFL1
PF1=Help   PF3=Exit   PF4=Save   PF7=Back   PF9=Messages   PF12=Return
 

After you have made your modifications to panel DFHRP5, you should press PF8 to move to panel DFHRP5B. From panel DFHRP5B you can press PF7 if you wish to go back to panel DFHRP5. After you have made your modifications to the panels, you press Enter to get all the modifications validated.

The attributes of a 4-tuple are divided into three categories:

ONC RPC attributes

The first four options establish the 4-tuple whose attributes are being defined.

ONC RPC Program Number
Specifies the program number of the 4-tuple as a hexadecimal string of 1 through 8 characters. You are advised not to use numbers in the range 0 through 1FFFFFFF, as these numbers are reserved for public network services and are allocated by Sun Microsystems.
ONC RPC Version Number
Specifies the version number of the 4-tuple as a hexadecimal string of 1 through 8 characters.
ONC RPC Procedure Number
Specifies the procedure number of the 4-tuple as a hexadecimal string of 1 through 8 characters. Procedure 0 is reserved by TCP/IP for MVS™ for a procedure with no parameters and no processing that returns an empty reply.
Protocol
Specifies the protocol of the 4-tuple. UDP (U) for UDP, or TCP (T) for TCP.

The remaining options specify the attributes of the 4-tuple.

RPC Call Type
Specifies whether CICS ONC RPC is to treat calls from clients as BLOCKING (B) or NONBLOCKING (N). If NONBLOCKING is specified, the outbound XDR routine cannot be specified, and no reply is sent to the client. The default is BLOCKING.
Inbound XDR Routine
Specifies the name of the inbound XDR routine. If an XDR library function is used, its full name is specified. See Table 26 to find out which library routines can be specified here. If a user-defined routine is used, its name (maximum 8 characters) is specified.
Outbound XDR Routine
Specifies the name of the outbound XDR routine, if RPC Call Type is BLOCKING. If an XDR library function is used, its full name is specified. See Table 26 to find out which library routines can be specified here. If a user-defined routine is used, its name (maximum 8 characters) is specified. A blank input is valid only if RPC Call Type is NONBLOCKING.

CICS attributes

ALIAS Transaction ID
Specifies the transaction ID to be used for the alias. If this is omitted, and not provided by the Decode function, the alias transaction ID is CRPA. For reasons why you might want a different name from CRPA, see Transaction definitions for extra alias transactions.
EDF Terminal ID
Specifies the terminal ID to be used for the alias. You need a terminal ID only if you want to use execution diagnostic facility (EDF) to debug the resource checker, CICS program, or Encode function of the converter. A blank means that you cannot use EDF. EDF setup is described in Using EDF.
Program Name
Specifies the name of the CICS program that is to be called to service a request for this 4-tuple.

CICS ONC RPC attributes

Converter Program Name
Specifies the name of the converter program. This name must be specified.
Encode
YES (Y) means that CICS ONC RPC must call the Encode function of the converter when servicing a client request for this 4-tuple; NO (N) means that it must not. The default is NO.
Decode
YES (Y) means that CICS ONC RPC must call the Decode function of the converter when servicing a client request for this 4-tuple; NO (N) means that it must not. The default is YES.
Getlengths
YES (Y) means that the connection manager must call the Getlengths function of the converter before registering this 4-tuple. NO (N) means that it must not. If you specify YES here, you should ignore the next two attributes, but you can set Server Data Format. If you specify NO here, you must specify the next three attributes. The default is YES.
Server Input Length
For the use of this option, see the description of Server Data Format.

If you specified YES for the Getlengths option, leave this field blank.

Server Output Length
For the use of this option, see the description of Server Data Format.

If you specified YES for the Getlengths option, leave this field blank.

Server Data Format
A value that controls:

The values you can specify are as follows:

CONTIGUOUS
The value of the data pointer that will be passed to Encode, or to the outbound XDR routine if Encode is not used for this 4-tuple, is the address of the CICS program communication area plus the value of Server Input Length, though Decode can modify this offset.

The connection manager calculates a communication area length by adding the values of Server Input Length and Server Output Length. If this length exceeds 32 767 bytes, message DFHRP1965 is issued. If this length is different from the actual length of the communication area passed from Decode to the CICS program, errors might occur in the processing of client requests.

OVERLAID
The value of the data pointer that will be passed to Encode, or to the outbound XDR routine if Encode is not used for this 4-tuple, is the address of the CICS program communication area.

The connection manager calculates a communication area length by taking the larger of the output values of Server Input Length and Server Output Length. If this length is different from the actual length of the communication area passed to the CICS program, errors might occur in the processing of client requests.

If you specified YES for the Getlengths option, the value in this field is used as an input to the Getlengths function of the converter.

Register from Data Set
YES (Y) means that the 4-tuple is to be registered: NO (N) means that it is not. The default is YES. Entries specified as NO can be stored in the CICS ONC RPC data set and you can register them at any time when CICS ONC RPC is enabled.

Saving new 4-tuple definitions

There are five ways of doing this:

Modifying existing 4-tuple definitions

To change some of the attributes of a 4-tuple that already has a definition in the CICS ONC RPC data set, select option 4 on panel DFHRP03 or panel DFHRP20. Change the attributes and validate your input as described in Defining the attributes of a 4-tuple, and press PF4, or Enter, to save the definition in the data set.

Deleting existing 4-tuple definitions

You can delete existing 4-tuple definitions from the CICS ONC RPC data set in either of the following ways:

Related concepts
ONC RPC concepts
Related tasks
Starting the connection manager
Updating CICS ONC RPC status
Enabling CICS ONC RPC
Registering the 4-tuples
Unregistering 4-tuples
Disabling CICS ONC RPC
Updating the CICS ONC RPC data set
Processing the alias list
[[ Contents Previous Page | Next Page Index ]]