Running Your Application


	Corporate Info \| News \| Solutions \| Products \| Partners \| Services \| Events \| Download \| How To Buy
	e-docs.beasys.com \| Site Map \| Search \| PDF Files \| Contact \| Glossary

MessageQ Doc Home \| MVS Client User's Guide \| Previous Topic \| Next Topic \| Contents \| Index

This chapter explains how to run your application under both MVS batch and CICS. It includes the following sections:

Running BEA MessageQ Applications Under MVS Batch

To use the BEA MessageQ MVS Client under MVS batch, the following software requirements must be met:

Your BEA MessageQ Server and Client systems must have a network communication link. Have your TCP/IP network administrator verify the network connection to ensure that the systems are properly configured.
The BEA MessageQ product for a UNIX, Windows NT, or OpenVMS platform must be installed on a BEA MessageQ Server system and a message queuing group must be configured to support the requirements of your messaging application environment. MVS Client applications use messaging resources, including message queues, message buffers, and system resources on the BEA MessageQ Server system. See the Installation and Configuration Guide for your BEA MessageQ Server system and review the system resource requirements for using BEA MessageQ in your environment.

For TCP/IP networking, the host names for the Client and Server systems must be properly identified in the hosts files on both the BEA MessageQ Client and Server systems, as shown in the following table.

System
Location of Hosts File

UNIX

/etc/hosts

Windows NT

c:\winnt\system32\drivers\etc\hosts

OpenVMS

Use the TCP/IP for OpenVMS configuration utilities

MVS

Contact your TCP/IP administrator

System	Location of Hosts File
UNIX	/etc/hosts
Windows NT	c:\winnt\system32\drivers\etc\hosts
OpenVMS	Use the TCP/IP for OpenVMS configuration utilities
MVS	Contact your TCP/IP administrator

For a complete description of BEA MessageQ Server systems and TCP/IP transports supported by the BEA MessageQ MVS Client, see the BEA MessageQ MQSeries Connect and MVS Client Release Notes, Version 5.0.

Several sample JCL execution files are included with the MVS Client software. Listing 4-1 shows sample JCL used to run the X@GET program in batch mode under MVS or OS/390. You can use this JCL to verify that your environment is properly configured.

Listing 4-1 Sample Execution JCL

//DMQRUN      JOB ,DMQ,CLASS=A,
//            MSGCLASS=X,MSGLEVEL=(1,1)
//            TIME=(5,00)
//******************************************
//RUNIT  EXEC PGM=X@GET
//STEPLIB  DD DSN=DMQ.V5R0.PROC,DISP=SHR
//         DD DSN=CEE.V1R5M0.SCEERUN,DISP=SHR
//*
//DMQINI  DD DSN=DMQ.V5R0.INI,DISP=SHR
//DMQELOG DD DSN=DMQ.V5R0.ELOG,DISP=SHR
//DMQLOG  DD DSN=DMQ.V5R0.LOG,DISP=SHR
//DMQSAF  DD DSN=DMQ.V5R0.SAF,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSOUT   DD *
//SYSTCPD  DD DISP=SHR,DSN=TCPIP.DATA

Listing 4-2 includes sample JCL to run the COBOL sample program DMQSAMP1 in batch mode under MVS or OS/390.

Listing 4-2 JCL for Executing COBOL Programs

//DMQSAMP1 EXEC PGM=DMQSAMP1                                    
//STEPLIB  DD DSN=DMQ.V5R0.LINKLIB,DISP=SHR                     
//         DD DSN=CEE.V1R5M0.SCEERUN,DISP=SHR                   
//*                                                             
//DMQINI  DD DSN=DMQ.V5R0.INI,DISP=SHR                          
//DMQELOG DD DSN=DMQ.V5R0.ELOG,DISP=SHR                         
//DMQLOG  DD DSN=DMQ.V5R0.LOG,DISP=SHR                          
//DMQSAF  DD DSN=DMQ.V5R0.SAF,DISP=SHR                          
//SYSPRINT DD SYSOUT=*                                          
//SYSOUT   DD SYSOUT=*                                          
//SYSTCPD  DD DSN=TCPIP.DATA,DISP=SHR                           
//DMQLIST  DD  SYSOUT=*,DCB=RECFM=FBA     (FOR COBOL PROGRAMS)  
//******************************************

Running BEA MessageQ Applications Under CICS

This section describes how to configure your environment to run BEA MessageQ applications under IBM CICS by:

Defining FCT Entries

To run BEA MessageQ applications in the MVS CICS environment, you must define FCT entries as shown in Listing 4-3.

Listing 4-3 FCT Entries to Define for a CICS Environment

DEFINE FILE(DMQINI) GROUP(DMQFILES)
  DSNAME(DMQ.V5R0.INI) LSRPOOL(1)
  DSNSHARING(ALLREQS) STRINGS(1)
  STATUS(ENABLED) OPENTIME(FIRSTREF) DISPOSITION(SHARE)
  DATABUFFERS(2) INDEXBUFFERS(1) RECORDFORMAT(V)
  ADD(YES) BROWSE(YES) DELETE(YES) READ(YES) UPDATE(YES)
 
DEFINE FILE(DMQELOG) GROUP(DMQFILES)
   DSNAME(DMQ.V5R0.ERR) LSRPOOLID(1)
   DSNSHARING(ALLREQS) STRINGS(1)
   STATUS(ENABLED) OPENTIME(FIRSTREF) DISPOSITION(SHARE)
   DATABUFFERS(2) INDEXBUFFERS(1) RECORDFORMAT(V)
   ADD(YES) BROWSE(YES) DELETE(YES) READ(YES) UPDATE(YES)
 
DEFINE FILE(DMQLOG) GROUP(DMQFILES)
  DSNAME(DMQ.V5R0.LOG) LSRPOOL(1)
  DSNSHARING(ALLREQS) STRINGS(1)
  STATUS(ENABLED) OPENTIME(FIRSTREF) DISPOSITION(SHARE)
  DATABUFFERS(2) INDEXBUFFERS(1) RECORDFORMAT(V)
  ADD(YES) BROWSE(YES) DELETE(YES) READ(YES) UPDATE(YES)
 
DEFINE FILE(DMQSAF) GROUP(DMQFILES)
  DSNAME(DMQ.V5R0.SAF) LSRPOOL(1)
  DSNSHARING(ALLREQS) STRINGS(1)
  STATUS(ENABLED) OPENTIME(FIRSTREF) DISPOSITION(SHARE)
  DATABUFFERS(2) INDEXBUFFERS(1) RECORDFORMAT(V)
  ADD(YES) BROWSE(YES) DELETE(YES) READ(YES) UPDATE(YES)

Defining PCT Entries

To run BEA MessageQ applications in the MVS CICS environment, you must define, to CICS, the PCT entries, the CICS transaction code, and the CICS BEA MessageQ program, as shown in Listing 4-4.

Listing 4-4 PCT Entries to Define for CICS Environment

DEFINE PROGRAM(X@GET) GROUP(DMQ)
  LANGUAGE(LE370) RELOAD(YES)
DEFINE TRANSACTION(XDMQ) GROUP(DMQ)
  PROGRAM(XDMQPROG) TWASIZE(1024) PROFILE(DFHCICST)
  TASKDATALOC(ANY)

Using Message Tracing Under CICS

If the trace options SENTCICSMESSAGES or RECEIVEDCICSMESSAGES are selected in the DMQ initialization file, messages are written to the transient data queue named DMQTLOG. The messages in this queue can be viewed using the CICS transaction CEBR. All records written to this queue are prefixed with the terminal ID, transaction code, date, and time.

Linkediting C Programs for CICS

The BEA MessageQ MVS Client contains a JCL sample for linkediting C programs in the CICS environment, as shown in Listing 4-5.

Listing 4-5 Sample Linkedit JCL for CICS C Programs

//DMQCICS JOB ,DMQ,CLASS=A, 
//             MSGCLASS=X,MSGLEVEL=(1,1), 
//             TIME=(5,00) 
//*********************************************************
//PLINK   EXEC EDCPL, 
//       INFILE='DMQ.USEROBJ(X@GET)', 
//       OUTFILE='SYS2.USERLINK(XDMQPROG),DISP=(SHR,KEEP)', 
//       PLIB='DSN=DMQ.V5R0.LIB,DISP=SHR', 
//       PPARM='NONCAL', 
//       LPARM='LET,AMODE(31),RMODE(ANY),XREF,LIST'     
//LKED.SYSLIB  DD DSN=CEE.SCEELKED,DISP=SHR                    
//             DD DSN=TCPIP.V3R2.SEZATCP,DISP=SHR   
//             DD DSN=TCPIP.V3R2.SEZACMTX,DISP=SHR    
//             DD DSN=CICS410.SDFHLOAD,DISP=SHR  
//LKED.SYSIN DD *                                 
 INCLUDE SYSLIB(DFHELII)   REQUIRED BY CICS        
 INCLUDE SYSLIB(EZACIC07)  REQUIRED BY CICS       
//