-------------------------------------------------------------------- | | | MODULE NAME MA1O.ZIP | | | | DESCRIPTIVE NAME Websphere MQ for z/OS | | REXX Application Trigger Monitor | | | | Statement: Licensed Materials - Property of IBM | | | | MA1O SupportPac | | (c) Copyright IBM Corp. 2009 | | | | All rights reserved. | | | | U.S. Government Users Restricted Rights - use, | | duplication or disclosure restricted by GSA | | ADP Schedule Contract with IBM Corp. | | | | Status: Version 1 Release 0 | | | | Author: Willi Jorg | | | | NOTES :- | | DEPENDENCIES = MQSeries for z/OS, SupportPac MA95 | | RESTRICTIONS = None | | MODULE TYPE = INFOZIP compressed | | | -------------------------------------------------------------------- All the files which make up the SupportPac are shipped in the file MA1O.ZIP. This is an archived file which should be uncompressed on a PC using one of INFOZIPs unzip programs. 1. On the PC workstation use the approriate INFOZIP unzip program to unpack the MA1O.ZIP file. The following files should be produced: readme - This introduction MA10doc - Documentation of MA1O as pdf-file MA1Oseq - This is an MVS PDS that has been unloaded to a sequential file then transferred to a PC file 2. MA1Oseq must be transferred to the destination TSO system as a sequential binary file with a record format of FB 80. To send it from a PC running IBM Personal Communications: Use the following SEND command from a command prompt: send MA1Oseq A:MA1Oseq where A: is the TSO session ID. or, use the "Send Files to Host" option under the Transfer menu item to transmit it to TSO: PC File MA1Oseq Host File MA1Oseq Transfer Type loadlib The Transfer type of "loadlib" may need to be correctly setup. To do this, use the "Setup.Define Transfer Types" option under the Transfer menu item and create the "loadlib" type with the Ascii, CRLF and Append checkboxes all unselected, the Fixed radio button selected and the LRECL set to 80. To send it via ftp ensure the BINARY option is set then use the following command: site fixrecfm 80 (optional) put MA1Oseq 3. On TSO, issue the following commands to unload this sequential file into TSO partitioned dataset: receive indsname(MA1Oseq) when prompted for a filename, reply dsn(MA1O.pds) 4. This will create the MVS PDS called MA1O.pds. It should contain the following members: MQMONJOB - The job starts the Trigger Monitor and connects to the Queue-Manager and the Initiation-Queue, which must be customized due to environment definitions. MQMONPID - REXX program which calls the monitor program MQTILITY MQTILITY - The REXX program serves as WMQ-Function Tool for REXX applicatons. It contains all required basics for MQ-Messaging as MqInit, MqOpen, MqPut, MqPut, MqGet, MqDisc, MqTerm and special function MqMonitor. Each REXX program may write a record into a queue and read a record from a queue without any knowledge about MQ-data processing by just calling MQTILITY. DEPLOYER - This REXX program determines the first level qualifier of the mandatory library named &HOME..UTILTY and does various dataset allocations. SAVE2LOG - This REXX program logs the start and end of any program started due to a trigger definition for the monitored initiation queue. The program uses Batchpipes for handling of the log dataset. MQTILITY is delivered using SAVE2LOG, which easily can be replaced by LOG2SAVE if necessary. LOG2SAVE - This REXX program logs the start and end of any program started due to a trigger definition for the monitored initiation queue. It is a clone of SAVE2LOG using EXECIO instead of Batchpipes for handling of the log dataset. 5. Copy the objects in the appropriate libraries &HOME..TRIGMON.SOURCE and &HOME..UTITLTY. 6. Review the MA1Odoc.pdf to understand the operation of the SupportPac.