MVS Client User's Guide

 

This document describes the BEA MessageQ MVS Client product and provides the information you need to configure and develop BEA MessageQ applications that run in an IBM MVS environment. BEA MessageQ MVS applications fully support BEA MessageQ features using the BEA MessageQ Client Library Server software running on a BEA MessageQ Server system.

 

Introduction

What Is the MVS Client?

Benefits of Using the MVS Client

Architectural Overview

What Is the Client Library Server?

How Do the MVS Client and CLS Work Together?

How the MVS Client Uses BEA MessageQ Function Calls

Store-and-Forward Journaling

 

Configuring the BEA MessageQ MVS Client

Verifying Your Installation

Creating MVS Client Datasets

Required Datasets

Configuring the Server Connection

Configuring the Default Server

Configuring the Automatic Failover Server

Configuring Logging

Configuring Message Recovery Services

Configuring Tracing

Verifying the Configuration

Testing the Configuration

 

Building Your Application

BEA MessageQ API Support

Sample Programs

MVS Client-specific Return Codes

Include Files for C and COBOL

Compiling and Linking C Programs

Compiling and Linking COBOL Programs

Byte Order

ASCII to EBCDIC Translation

putilae

putilea

 

Running Your Application

Running BEA MessageQ Applications Under MVS Batch

Running BEA MessageQ Applications Under CICS

Defining FCT Entries

Defining PCT Entries

Using Message Tracing Under CICS

Linkediting C Programs for CICS

 

Troubleshooting

Run-time Errors

Error Logging

Failing to Connect to the CLS

Network Errors

TCP/IP Error Codes

Tracing PAMS API Activity

Tracing Client Library Activity

Recovering from Client Crashes