Version 9.6	SEARCH   CONTENTS   |   PDF BOOKS   |   HOME   UP   PREV   NEXT

A server mapping file (SVM) enables the RPC server to correctly support special COBOL syntax such as REDEFINEs, JUSTIFIED, SYNCHRONIZE and OCCURS DEPENDING ON clauses, LEVEL-88 fields, etc. If one of these elements is used, the EntireX Workbench automatically extracts an SVM file in addition to the IDL (interface definition language), or an SVM file is generated by the COBOL Wrapper for a server skeleton. The SVM file is used at runtime to marshal and unmarshal the RPC data stream.

To make an SVM file available at runtime for the RPC server used, it has to be deployed. See Handling SVM Files in the RPC server documentation for z/OS (CICS, Batch, IMS) | Micro Focus | CICS ECI | IMS Connect | BS2000/OSD | z/VSE (CICS, Batch) or the EntireX Adapter documentation. As another prerequisite, the RPC server or EntireX Adapter must support the interface type of the COBOL server. This document covers the following topics:

• Compatibility between Interface Type and RPC Server

• Deploying a Server Mapping File

Compatibility between Interface Type and RPC Server

To call a server successfully, the RPC server used must support the interface type of the COBOL server. In this context, there are two scenarios, where you need to select an appropriate interface type:

• Scenario Calling an Existing COBOL Server under z/OS (CICS, Batch, IMS) | Micro Focus | BS2000/OSD | z/VSE (CICS, Batch)

  within extraction stettings, see Step 4: Define the Extraction Settings and Start Extraction.

• Scenario Writing a New COBOL Server under z/OS (CICS, Batch, IMS) | Micro Focus RPC Server | BS2000/OSD | z/VSE (CICS, Batch)

  within the COBOL Wrapper IDL properties, see Server Interface Types under Generating COBOL Source Files from Software AG IDL Files.

The table below gives an overview of possible combinations of an interface type and a supporting RPC server:

Deploying a Server Mapping File

To deploy a server mapping, you can either use a wizard or copy the file manually to a target container. The approach depends on the RPC server used. For instance, not all RPC servers support both deployment by using a wizard and manual deployment. The table below gives an overview of supported approaches for available RPC servers and the webMethods EntireX Adapter for Integration Server, and provides further instructions for various forms of manual deployment:

The remainder of this section focuses on the major approaches:

• Server Mapping Deployment Wizard

• Server Mapping Deployment Wizard Preferences

• Server Mapping Deployment in Command-line Mode

• Server Mapping Deployment using FTP and IDCAMS

Server Mapping Deployment Wizard

Deploying with the wizard requires an active RPC server. Also, the Deployment Service of the RPC server must be properly configured. See the platform-specific documentation for more information:

• z/OS, see Deployment Service for CICS | Batch | IMS.

• UNIX or Windows for Micro Focus COBOL, see Deployment Service in the Micro Focus RPC Server documentation.

• BS2000/OSD, see Deployment Service in the BS2000/OSD Batch RPC Server documentation.

• z/VSE, see Deployment Service for CICS | Batch.

Caution:
The codepage (locale string) of the RPC server used during deployment must be the same as the one used with running RPC clients issuing RPC requests.

To deploy a server mapping with the wizard, follow the steps below:

• Step 1: Start the Wizard
• Step 2a: Create a New Deployment Environment
• Step 2b: Define the Connection to the Deployment Service and Deploy
• Step 3: Select an Existing Deployment Environment and Deploy

Step 1: Start the Wizard

To start the server mapping deployment wizard, select an SVM file and choose Deploy/Synchronize Server Mapping... from the context menu.

To continue, press Next together with one of the following choices:

• If you enter the server mapping deployment wizard the first time with no predefined deployment environment preferences (see IDL Extractor for COBOL Preferences), continue with Step 2a: Create a New Deployment Environment below.

• If deployment environments are already defined, you may also continue with Step 3: Select an Existing Deployment Environment and Deploy below.

Step 2a: Create a New Deployment Environment

If no deployment environments are defined, you only have the option to create a new deployment environment.

To proceed:

1. Select Create a new deployment environment.

2. Press Next and continue with Step 2b: Define the Connection to the Deployment Service and Deploy.

Step 2b: Define the Connection to the Deployment Service and Deploy

Use this page to define a connection to the deployment service of the RPC server.

Enter the required fields:

1. Broker Parameters Broker ID and Server Address, which will have the default format. The last part (broker service) of the server address must always be "DEPLOYMENT".

2. The EntireX Authentication parameters describe the settings for the broker. These parameters apply if the broker is running with EntireX Security. See Which EntireX Security Solution.

3. The RPC Server Authentication parameters describe the settings for the RPC server. These parameters apply if the RPC server is running with security, for example a Natural RPC Server running with Natural Security.

4. The given Timeout value must be in the range from 1 to 9999 seconds (default: 60).

Press Finish to deploy. Deployment of the server mapping is successful if the wizard ends. No confirmation message is given.

Step 3: Select an Existing Deployment Environment and Deploy

Use this page to select the deployment environment (i.e. the RPC server) to which you want to deploy.

Check the option Choose an existing deployment environment and select a deployment environment from the list. Press Finish to deploy. Deployment is successful if the wizard ends. No confirmation message is given.

Server Mapping Deployment Wizard Preferences

In the preferences for the server mapping deployment wizard you define deployment environments, a connection to the Deployment Service of the RPC server. See Deployment Service in the RPC server documentation for z/OS (CICS, Batch, IMS) | Micro Focus | BS2000/OSD | z/VSE (CICS, Batch). The following sections are offered:

• Create a new Deployment Environment
• Edit an Existing Deployment Environment
• Remove an Existing Deployment Environment

The deployment environment is managed from the deployment environment Preferences page. The deployment environments can be created, edited and removed. The deployment environment will be used for the selection lists in the Server Mapping Deployment Wizard. To manage these deployment environments, open the Preferences page:

Create a new Deployment Environment

To create a new deployment environment

• Press Insert.

Edit an Existing Deployment Environment

To edit an existing deployment environment

• Select the table row and press Edit. If multiple entries are selected, the first entry is used.

For more information on the input fields on this page, see Step 2b: Define the Connection to the Deployment Service and Deploy under Server Mapping Deployment Wizard.

Remove an Existing Deployment Environment

To remove an existing deployment environment

• Select the table row and press Remove. Multiple selections are possible.

Server Mapping Deployment in Command-line Mode

The command -deploy:cobol is provided to deploy server mapping files (SVMs) using the EntireX Workbench in command-line mode. See Using the EntireX Workbench in Command-line Mode for general information.

To undeploy previously deployed server mapping entries on the server side, remove the SVM file and execute the command -deploy:cobol with the IDL file only.

Command-line Options

Note:
Run the command from the directory containing the IDL file and the corresponding SVM file. If no SVM file is found, the previously deployed server mapping entries related to the IDL file will be removed on the server side (undeployed).

Example

-deploy:cobol /SVMDeployTests/idls/basicodo.idl  /SVMDeployTests/idls/basicdt.idl /SVMDeployTests/idls/basicarr.idl 
 -environment ibm2:3980@RPC/RPCALL/DEPLOYMENT
 -brokeruser EXXUSR1 
 -brokerpassword EXX$PWD1

Server Mapping Deployment using FTP and IDCAMS

This approach is available for z/OS and z/VSE only.

To deploy a server mapping using FTP and IDCAMS

1. Allocate a target sequential file on your mainframe.

2. Allow write access to the VSAM file mentioned above and usage of IDCAMS tools.

3. Transfer the SVM file to the target host, using FTP. You have to switch to text mode and the codepage of the FTP service must be the same as the codepage (locale string) of the RPC server used.

4. Install the server mapping into the VSAM SVM cluster with the IDCAMS job below. The following example applies to z/OS.

   //EXPSVMR  JOB (,,,999),ENTIREX,NOTIFY=&SYSUID,MSGLEVEL=(1,1),
   //             CLASS=K,MSGCLASS=X,REGION=0M,COND=(0,LT)
   //*-----------------------------------------------------* 
   //* FILL THE SVM VSAM CLUSTER                           *
   //*-----------------------------------------------------*
   //IMPORT   EXEC PGM=IDCAMS
   //RECORDS  DD DISP=SHR,DSN=EXP.SVM.TARGET.SEQ.RECORDS
   //SVM      DD DISP=SHR,DSN=EXP.SVM.KSDS
   //SYSPRINT DD SYSOUT=*
   //SYSIN    DD *
     REPRO - 
       REPLACE -
       INFILE(RECORDS) -
       OUTFILE(SVM)

   Note:
   If you omit the keyword REPLACE or define NOREPLACE in the SYSIN data stream instead, existing server mappings are not overwritten. This protects SVM records from being overwritten by duplicates.

www.softwareag.com

Copyright © 1997-2014 Software AG, Darmstadt, Germany.

SEARCH   CONTENTS   |   PDF BOOKS   |   HOME   UP   PREV   NEXT