| home / infca / mq / mq_zos (navigation links) | Sonrie, y serás feliz |
Install |
Top
|
Installable features
System Setup Guide, WS MQ for z/OS, version 6.0, SC34-6853-00, page 3 to 19/321
Customize |
Top
|
Before you perform the customization tasks, there are a number of configuration options that you should consider because they affect the performance and resource requirements of WebSphere MQ for z/OS. These options are discussed in the MQ for z/OS Concepts and Planning Guide. [llibres]
M'agradaria saber la manera de mostrar, visualitzar tots aquestos valors en una instalació ja feta !
Parameters |
Top
|
La tabla de parámetros está compuesta por tres macros. Estas macros establecen los valores operativos del SISTEMA, LOGs y proceso de ARCHIVE. En general, los valores de los parámetros no son críticos y los establecidos por defecto están fijados para un sistema que soportará una gran carga de trabajo.
MQ for z/OS V6.0 System Setup Guide, SC34-6583-00
Use CSQ6SYSP to set SYSTEM parameters.
MQ for z/OS V6.0 System Setup Guide, SC34-6583-00, page 36, 52/321
Use CSQ6LOGP to establish your logging options.
MQ for z/OS V6.0 System Setup Guide, SC34-6583-00, page 45, 62/321
Use CSQ6ARVP to establish your archiving environment.
El primero, segundo y cuarto son muy recomendables, el tercero discutible;
depende de las instalaciones.
MQ for z/OS V6.0 System Setup Guide, SC34-6583-00, page 49, 65/321
Tuning |
Top
|
There are a number of ways in which you can improve the performance of your queue manager, which are controlled by queue manager attributes set by the ALTER QMGR command. MQ SupportPac MP16, Capacity planning and tuning for WebSphere MQ for z/OS, gives more information on performance and tuning.
z/OS Concepts and Planning Guide WS MQ for z/OS, version 6.0, GC34-6852-00, page 44, 61/207
Concepts |
Top
|
System Setup Guide, WS MQ for z/OS, version 6.0, SC34-6853-00, page 32 to 48/321
The print log map utility (CSQJU004) is a batch utility that lists the information stored in the BSDS.
The active log comprises a collection of data sets (up to 31) which are used cyclically.
z/OS Concepts and Planning Guide WS MQ for z/OS, version 6.0, GC34-6852-00, chapter 4
Many aspects of archiving and logging are controlled by parameters set using the CSQ6LOGP, CSQ6ARVP and CSQ6SYSP macros of the system parameter module when the queue manager is customized. See the "WebSphere MQ for z/OS System Setup Guide" for details of these macros.
You can display the settings of all the parameters using the
(a) also returns a report about the status of the logs.
Use DISPLAY USAGE to display information about the current state of a page set, or to display information about the log data sets.
Planning your logging environment
z/OS Concepts and Planning Guide WS MQ for z/OS, version 6.0, GC34-6852-00, chapter 18
Casuística: Estamos en el TERCER fichero de TRES.
Cuando se llena, se conmuta al PRIMERO y ARCHIVE del TERCERO.
Si el proceso de ARCHIVE del PRIMERO no se ha realizado
(problema del hardware
o pereza del operador
o no hay tiempo material para hacer el ARCHIVE),
el MQSeries se para.
Todos esto queda registrado en otro fichero,
el BSDS (BootStrapDataSet):
LOG que está ACTIVO,
ficheros de ARCHIVE,
si una descarga (ARCHIVE) está pendiente, etc.
Recomendación: Un ciclo de LOG debe durar 24 horas. ¿Por qué? Porque diariamente se debe hacer una copia de seguridad y, por razones de rapidez de recuperación, todos los datos de recuperación deberían estar en los LOG.
Nota: Cuando el proceso de ARCHIVE se produce (copia de LOG a CINTA), los datos siguen vivos en los LOG y se usarán antes que los datos de CINTA. Si el ciclo de LOG es de 24 horas, se puede recuperar cualquier cosa sin necesidad de tirar de CINTA, mucho más lenta.
En el Concept and Planning, me parece recordar, vienen unas recomendaciones para sistemas LIGHT, MEDIUM and HEAVY Workload.
Messages and Codes, WS MQ for z/OS, version 6.0, GC34-6602-00, chapter 5, page 47
SYSTEM SETUP GUIDE SC34-6052-xx CONCEPTS AND PLANNING GUIDE SC34-6051-xx SYSTEM ADMINISTRATION GUIDE for Z/OS SC34-6053-xx Part 5 = Recovery & Restart.
z/OS Concepts and Planning Guide WS MQ for z/OS, version 6.0, GC34-6852-00, chapter 6
System Administration Guide, WS MQ for z/OS, version 6.0, SC34-6585-00, part 5, chapter 13-16.
SYSTEM SETUP GUIDE SC34-6052-xx (z/OS, v 5.3) CONCEPTS AND PLANNING GUIDE SC34-6051-xx (z/OS, v 5.3) SECURITY SC34-6079-xx (v 5.3)
System Setup Guide, WS MQ for z/OS, version 6.0, SC34-6853-00, chapter 17
z/OS Concepts and Planning Guide WS MQ for z/OS, version 6.0, GC34-6852-00, chapter 7
Security, WS MQ version 6.0, SC34-6588-01
Useful commands |
Top
|
Que fa al z/OS la comanda DISPLAY DQM ? [MQMONNTP]
These fields correspond to the INHIBTEV, LOCALEV,REMOTEEV, STRSTPEV, PERFMEV and CONFIGEV attributes of the queue manager.
Support Packs |
Top
|
Explorer |
Top
|
Performance Analysis |
Top
|
Performance can be adversely affected by:
System Setup Guide, WS MQ for z/OS, version 6.0, SC34-6853-00, page 120 to 136/321
Auditoria / Diagnosi de MQ |
Top
|
Trigger Monitors |
Top
|
To a queue manager, a trigger monitor is like any other application that serves a queue. However, a trigger monitor serves initiation queues. A trigger monitor is usually a continuously-running program. When a trigger message arrives on an initiation queue, the trigger monitor retrieves that message. It uses information in the message to issue a command to start the application that is to process the messages on the application queue. The trigger monitor must pass sufficient information to the program it is starting so that the program can perform the right actions on the right application queue.
The following trigger monitor
is provided for CICS Transaction Server for z/OS and CICS for MVS/ESA:
CKTI
You need to start one instance of CKTI
for each initiation queue
(see WebSphere MQ for z/OS System Administration Guide
for information on how to do this).
CKTI passes the MQTM structure of the trigger message
to the program it starts by EXEC CICS START TRANSID.
The started program gets this information
by using the EXEC CICS RETRIEVE command.
A program can use the EXEC CICS RETRIEVE command
with the RTRANSID option
to determine how the program was started;
if the value returned is CKTI,
the program was started by "MQ for z/OS".
For an example of how to use CKTI, see the source code supplied for module CSQ4CVB2 in the Credit Check sample application supplied with WebSphere MQ for z/OS. See The Credit Check sample for a full description. URL
The following trigger monitor is provided for IMS/ESA: CSQQTRMN
You need to start one instance of CSQQTRMN
for each initiation queue
(see WebSphere MQ for z/OS System Administration Guide
for information on how to do this).
CSQQTRMN passes the MQTMC2 structure
of the trigger message to the programs it starts.
"Application Programming Guide", WS MQ for z/OS, version 6.0, SC34-6895-01, page 195 [216/601]
The CICS trigger monitor (CKTI) issued a 'EXEC CICS START TRANSID' for the value (CICS tranid) specified in the ApplId parameter of the Process definition. - {Fora}
Start the CKTI trigger monitor (supplied with WebSphere MQ for z/OS) against queue CSQ4SAMP.INITIATION.QUEUE, using the CICS transaction CKQC.
"Application Programming Guide", WS MQ for z/OS, version 6.0, SC34-6895-01, page 467 [487/601]
{Fora} -
1. Use the CKBM transaction
to tell the CKTI transaction what initiation queue to monitor
2. In your PROCESS definition
set APPLTYPE to CICS
and APPLICID to the name of the transaction you want to start.
Why trigger?
Triggering is only really good for very intermittent invocation. It has extra overhead of a PUT and GET to the initiation queue and has to load the application program into the system each time a message arrives.
Just code a long-running CICS transaction with MQGET WAIT on the queue. Process the message, reply to it and repeat the MQGET WAIT in a loop. For a server program that is invoked fairly frequently this is the most efficient way to code it.
The CICS bridge |
Top
|
The WebSphere MQ-CICS bridge is the component of WebSphere MQ for z/OS that allows direct access from WebSphere MQ applications to applications on your CICS system. In bridge applications there are no WebSphere MQ calls within the CICS application (the bridge enables implicit MQI support). This means that you can re-engineer legacy applications that were controlled by 3270-connected terminals to be controlled by WebSphere MQ messages, without having to rewrite, recompile, or re-link them.
Concepts and Planning Guide, WS MQ for z/OS, version 6.0, GC34-6582-00, page 99 [116/207]
You can use the CICS Bridge to run a DPL program or a 3270 transaction.
Application Programming Guide, chapter 17, "Using and writing MQ-CICS Bridge applications for z/OS"
A MQ application can start a CICS application by sending a structured message to the CICS bridge request queue. Any data required by the CICS application can be included in the request message:
Similarly, the CICS application can send data back to the MQ application in a message that is sent to a reply queue:
Application Programming Guide, pg 268 [288/601] "CICS DPL bridge message structure".
Concepts & Planning Guide - esquema maco.
COBOL |
Top
|
Application Programming Guide,
WS MQ for z/OS, version 6.0,
SC34-6595-01,
ch 26 = Building your application on z/OS,
ch 29 = Sample programs fo MQ for z/OS
Supportpac MA12 provides two sample COBOL programs which can be used as MVS-Batch trigger monitors. This can be found here: url
63 KB msg |
Top
|
The size for normal messages was 4 MB at some time
and moved to 100 MB with mq v 6
When ibm started with shared queues,
in the first versions
only non persistent and < 64kb messages where possible
On v531 the Shared Messages is on the CF. On v600 the Shared Messages is on DB2 (for messages larger than 63 KB).
CHINT start |
Top
|
El método más "limpio" de arrancar el chinit es:
En el arranque de la tarea MSTR,
en vuestro caso CSQ1MSTR,
tenemos una DD llamada CSQINP2.
Esta DD se "ALLOCA" con una concatenación de miembros
con definiciones de objeto. La primera vez
del mundo mundial que se arranca la tarea MSTR,
se concatenan varios miembros y a partir de esta primera vez,
se deja uno solo
con comandos que le pueden ser útiles al administrador de sistema.
Personalmente, yo en ese miembros solo dejo un comando,
precisamente el arranque del CHINIT.
Consola segura |
Top
|
Repasar
Shared queues |
Top
|
Rest assured that 'implementing' WebSphere MQ on a z/OS platform is exponentially more involved and difficult than an implementation on one of the distributed platforms.
Unlike the distributed platforms, on z/OS you have to include/involve/negotiate around numerous other technical departments to complete the 'implementation'. Some that come to mind immediately are RACF Authorizations, APF Authorizations, MVS Support, CICS support and it wouldn't hurt to have some indepth SMPE knowledge to boot.
Creating a new QMGR on z/OS is not the simple crtmqm as found on the distributed platforms.
Kutxka |
Top
|
Acc |
Top
|
Uni |
Top
|
Customer is using linear logs. Used rcdmqimg to take backups. Recovered the damaged objects using rcrmqobj command.
The print log utility is CSQ1LOGP. It runs as an MVS batch job. You can print active logs and inactive logs. There are control statements that allow the z/OS admin to pick and choose what to print. The EXTRACT control statement is a good place to start reading.
This is from the System Admin manual about EXTRACT:
Typical uses of the EXTRACT parameter are to:
Print the BSDS log directory to determine which are active and which are inactive (archivable). There is a supplied utility to print the BSDS. Refer to the z/OS WMQ System Admin manual unit on managing the bsds. Use the print log map utility (CSQJU004) to print the contents of the BSDS.
Llibres |
Top
|
De URL
A T42:\MQ\BOOKS\V6\zOS
URLs |
Top
|
|
Updated 20240621
|
