Nastel XRay Probes for zOS · 2021. 1. 22. · nastel xray probes for z/os installation and...

Nastel XRay Probes for z/OS Installation and User’s Guide

CONFIDENTIALITY STATEMENT: THE INFORMATION WITHIN THIS MEDIA IS PROPRIETARY IN NATURE AND IS THE SOLE PROPERTY OF

NASTEL TECHNOLOGIES, INC. ALL PRODUCTS AND INFORMATION DEVELOPED BY NASTEL ARE INTENDED FOR LIMITED DISTRIBUTION

TO AUTHORIZED NASTEL EMPLOYEES, LICENSED CLIENTS, AND AUTHORIZED USERS. THIS INFORMATION (INCLUDING SOFTWARE,

ELECTRONIC AND PRINTED MEDIA) IS NOT TO BE COPIED OR DISTRIBUTED IN ANY FORM WITHOUT THE EXPRESSED WRITTEN PERMISSION

FROM NASTEL TECHNOLOGIES, INC.

© 2021 Nastel Technologies, Inc. All rights reserved.

© 2021 Nastel Technologies, Inc. B XR_zOS.004

PUBLISHED BY:

RESEARCH & DEVELOPMENT

NASTEL TECHNOLOGIES, INC.

88 SUNNYSIDE BLVD, SUITE 101

PLAINVIEW, NY 11803

COPYRIGHT © 2021. ALL RIGHTS RESERVED. NO PART OF THE CONTENTS OF THIS DOCUMENT MAY BE

PRODUCED OR TRANSMITTED IN ANY FORM, OR BY ANY MEANS WITHOUT THE WRITTEN PERMISSION OF

NASTEL TECHNOLOGIES.

DOCUMENT TITLE: NASTEL XRAY PROBES FOR Z/OS

DOCUNMENT RELEASE DATE: JANUARY 2021

NASTEL DOCUMENT NUMBER: XR_ZOS.004

CONFIDENTIALITY STATEMENT: THE INFORMATION WITHIN THIS MEDIA IS PROPRIETARY IN NATURE AND IS THE SOLE PROPERTY OF

NASTEL TECHNOLOGIES, INC. ALL PRODUCTS AND INFORMATION DEVELOPED BY NASTEL ARE INTENDED FOR LIMITED DISTRIBUTION

TO AUTHORIZED NASTEL EMPLOYEES, LICENSED CLIENTS, AND AUTHORIZED USERS. THIS INFORMATION (INCLUDING: SOFTWARE,

ELECTRONIC AND PRINTED MEDIA) IS NOT TO BE COPIED OR DISTRIBUTED IN ANY FORM WITHOUT THE EXPRESSED WRITTEN PERMISSION

FROM NASTEL TECHNOLOGIES, INC.

ACKNOWLEDGEMENTS:

THE FOLLOWING TERMS ARE TRADEMARKS OF NASTEL TECHNOLOGIES CORPORATION IN THE UNITED STATES OR OTHER COUNTRIES

OR BOTH: TRANSACTIONWORKS, M6 AUTOPILOT, AUTOPILOT/IT, AUTOPILOT/ENTERPRISE, M6 FOR WMQ, AUTOPILOT/WMQ, M6

WEB SERVER, M6 WEB CONSOLE, AUTOPILOT/WEB, MQCONTROL, MQCONTROL EXPRESS, AUTOPILOT/TRANSACTION ANALYZER,

AUTOPILOT/WAS, AUTOPILOT/TRANSACTION MONITOR, AUTOPILOT/OS MONITOR, NASTEL NAVIGATOR, NASTEL XRAY.

THE FOLLOWING TERMS ARE TRADEMARKS OF THE IBM CORPORATION IN THE UNITED STATES OR OTHER COUNTRIES OR BOTH: IBM,

MQ, MQSERIES, WEBSPHERE, WEBSPHERE MQ WIN-OS/2, AS/400, OS/2, DB2, AND AIX, Z/OS.

THE FOLLOWING TERMS ARE TRADEMARKS OF HEWLETT-PACKARD IN THE UNITED STATES OR OTHER COUNTRIES OR BOTH:

OPENVIEW, HP-UX.

COMPAQ, ETC. ARE TRADEMARKS OF HEWLETT-PACKARD DEVELOPMENT COMPANY.

SNMPC, SNMPC WORKGROUP EDITION AND SNMPC ENTERPRISE EDITION ARE TRADEMARKS OF CASTLE ROCK COMPUTING IN THE

UNITED STATES OR OTHER COUNTRIES, OR BOTH.

SUN, SUN MICROSYSTEMS, THE SUN LOGO, IFORCE, JAVA, NETRA, N1, SOLARIS, SUN FIRE, SUN RAY, SUNSPECTRUM, SUN

STOREDGE, SUNTONE, THE NETWORK IS THE COMPUTER, ALL TRADEMARKS AND LOGOS THAT CONTAIN SUN, SOLARIS, OR JAVA, AND

CERTAIN OTHER TRADEMARKS AND LOGOS ARE TRADEMARKS OR REGISTERED TRADEMARKS OF ORACLE CORPORATION AND/OR ITS

AFFILIATES.

INSTALLANYWHERE IS A REGISTERED TRADEMARK OF ZEROG SOFTWARE IN THE UNITED STATES OR OTHER COUNTRIES, OR BOTH.

THIS PRODUCT INCLUDES SOFTWARE DEVELOPED BY THE APACHE SOFTWARE FOUNDATION (HTTP://WWW.APACHE.ORG/). THE

JAKARTA PROJECT" AND "TOMCAT" AND THE ASSOCIATED LOGOS ARE REGISTERED TRADEMARKS OF THE APACHE SOFTWARE

FOUNDATION.

INTEL, PENTIUM AND INTEL486 ARE TRADEMARKS OR REGISTERED TRADEMARKS OF INTEL CORPORATION IN THE UNITED STATES, OR

OTHER COUNTRIES, OR BOTH.

MICROSOFT, WINDOWS, WINDOWS NT, WINDOWS XP, .NET, .NET FRAMEWORK AND THE WINDOWS LOGOS ARE REGISTERED

TRADEMARKS OF THE MICROSOFT CORPORATION.

UNIX IS A REGISTERED TRADEMARK IN THE UNITED STATES AND OTHER COUNTRIES LICENSED EXCLUSIVELY THROUGH X/OPEN

COMPANY LIMITED.

"LINUX" AND THE LINUX LOGOS ARE REGISTERED TRADEMARKS OF LINUS TORVALDS, THE ORIGINAL AUTHOR OF THE LINUX KERNEL.

ALL OTHER TITLES, APPLICATIONS, PRODUCTS, AND SO FORTH ARE COPYRIGHTED AND/OR TRADEMARKED BY THEIR RESPECTIVE

AUTHORS.

SCO CUSA, SCO DOCTOR, SCO DOCTOR FOR NETWORKS, SCO DOCTOR LITE, SCO GLOBAL ACCESS, SCO MPX, SCO

MULTIVIEW, SCO NIHONGO OPENSERVER, SCO OK, THE SCO OK LOGO, SCO OPENSERVER, SCO OPEN SERVER, SCO PORTFOLIO,

SCO POS SYSTEM, SCO TOOLWARE, AND THE WORLD NEVER STOPS ARE TRADEMARKS OR REGISTERED TRADEMARKS OF CALDERA

INTERNATIONAL, INC. IN THE U.S.A. AND OTHER COUNTRIES, ALL RIGHTS RESERVED.

ORACLE® IS A REGISTERED TRADEMARK OF ORACLE CORPORATION AND/OR ITS AFFILIATES.

TIBCO IS A REGISTERED TRADEMARK OF TIBCO SOFTWARE INC. IN THE UNITED STATES AND/OR OTHER COUNTRIES.

OTHER COMPANY, PRODUCT, AND SERVICE NAMES, MAY BE TRADEMARKS OR SERVICE MARKS OF OTHERS.

Nastel XRay Probes for z/OS Table of Contents

XR_zOS.004 iii © 2021 Nastel Technologies, Inc.

Table of Contents

CHAPTER 1: INTRODUCTION .............................................................................................................................. 7

1.1 HOW THIS GUIDE IS ORGANIZED .................................................................................................................. 7 1.2 HISTORY OF THIS DOCUMENT ...................................................................................................................... 8

1.2.1 User Feedback ........................................................................................................................................ 8 1.3 RELATED DOCUMENTS ................................................................................................................................. 8 1.4 RELEASE NOTES ........................................................................................................................................... 8 1.5 INTENDED AUDIENCE ................................................................................................................................... 8 1.6 SYSTEM REQUIREMENTS............................................................................................................................... 8 1.7 TERMS AND ABBREVIATIONS ...................................................................................................................... 10 1.8 TECHNICAL SUPPORT .................................................................................................................................. 10 1.9 CONVENTIONS ............................................................................................................................................ 10

CHAPTER 2: ABOUT NASTEL XRAY ................................................................................................................. 11

2.1 NASTEL XRAY FEATURES .......................................................................................................................... 11 2.2 NASTEL XRAY COMPONENTS ..................................................................................................................... 11

CHAPTER 3: INSTALLING PROBE COMPONENTS ....................................................................................... 13

3.1 TRANSFERRING DATA SETS TO Z/OS .......................................................................................................... 13 3.2 RESTORING FILES ....................................................................................................................................... 14 3.3 INSTALLING THE PROBE .............................................................................................................................. 14

3.3.1 Creating Nastel Front-end Modules ..................................................................................................... 14 3.3.2 Authorized Program Facility Authorization ......................................................................................... 16 3.3.3 Setup Additional LX Resources............................................................................................................. 16 3.3.4 Tailoring JCLs ...................................................................................................................................... 16

3.3.4.1 Transaction Interceptor JCL .......................................................................................................................... 16 3.3.5 Configuring the Probe .......................................................................................................................... 17

3.3.5.1 Message Prefix .............................................................................................................................................. 17 3.3.5.2 Probe Configuration File ............................................................................................................................... 17

3.3.6 Running Multiple Transaction Interceptor Probes ............................................................................... 22 3.3.7 Change ProdId Parameter Considerations .......................................................................................... 22 3.3.8 Queue Manager Definition File ................................................................................................................. 23 3.3.9 External Security Definitions ..................................................................................................................... 23 3.3.10 Activating Batch MQ Monitoring ...................................................................................................... 24

3.4 CHANNEL INITIATOR (CHINIT) MONITORING ............................................................................................ 24 3.4.1 Activate CHINIT Monitoring ................................................................................................................ 24 3.4.2 Deactivate CHINIT Monitoring ............................................................................................................ 24

3.5 UNINSTALLING NASTEL XRAY Z/OS PROBE .............................................................................................. 25 3.5.1 Deactivating Batch MQ Monitoring ..................................................................................................... 25 3.5.2 Uninstall Batch MQ Monitoring ........................................................................................................... 25

CHAPTER 4: USING THE PROBE........................................................................................................................ 27

4.1 STARTING API TRANSACTION INTERCEPTOR .............................................................................................. 27 4.2 STOPPING API TRANSACTION INTERCEPTOR .............................................................................................. 27 4.3 PROBE MESSAGES ....................................................................................................................................... 27 4.4 VERIFYING INSTALLATION ......................................................................................................................... 28 4.5 MESSAGE AUTOMATION ............................................................................................................................. 31 4.6 DISABLING IBM MQ COLLECTION ............................................................................................................. 32 4.7 QMON (QUEUE MONITOR SUBTASK) ........................................................................................................ 32 4.8 DATASPACE MANAGEMENT ........................................................................................................................ 33

4.8.1 Dataspace Switching ............................................................................................................................ 33 4.8.2 Configuring Dataspace Settings ........................................................................................................ 33 4.8.3 Dataspace Size Limits ................................................................................................................................ 34 4.8.4 Auxiliary Storage Usage ............................................................................................................................ 34

4.9 TRANSMITTER SUBTASKS ........................................................................................................................... 34 4.9.1 Tuning ................................................................................................................................................... 34

4.10 TIMERS ...................................................................................................................................................... 36

CHAPTER 5: INSTALLING THE PROBE FOR CICS ....................................................................................... 37

Table of Contents Nastel XRay Probes for z/OS

© 2021 Nastel Technologies, Inc. iv XR_zOS.004

5.1 INSTALLATION FILES ...................................................................................................................................37 5.2 MQ CICS DATA COLLECTION............................................................................................................................37

5.2.1 Activate CICS Resource Manager Interface ..............................................................................................37 5.3 MODIFYING CICS STARTUP JCL ................................................................................................................37 5.4 CICS DEFINITIONS ......................................................................................................................................37 5.5 CICS PROGRAM LIST TABLES .....................................................................................................................38

5.5.1 PLTPI Table ...............................................................................................................................................38 5.5.2 PLTSD Table ..............................................................................................................................................38

5.6 SYSTEM INITIALIZATION PARAMETERS INPUT VALUES ...............................................................................39 5.7 STARTING CICS REGION .............................................................................................................................40 5.8 VERIFYING INSTALLATION ..........................................................................................................................40 5.9 CICSPLEX AND FAILOVER .......................................................................................................................42 5.10 EXEC CICS, EXEC SQL, AND CALL EZASOKET COMMAND FEATURE................................................42

5.10.1 Setup of NSQGLUEX (GLUE), NSQDBRMI (GLUE), and NSQTRUES (TRUE) .............................43 5.10.2 EXEC CICS Command Collection.....................................................................................................43 5.10.3 CICS Transaction Filters ...................................................................................................................43 5.10.4 EXEC CICS Command Filters...........................................................................................................44 5.10.5 DB2 Plan Filters ................................................................................................................................45 5.10.6 DB2 SQL Command Filters ...............................................................................................................45 5.10.7 TCP Command Filters .......................................................................................................................45

5.11 NSTM TRANSACTION COMMANDS .............................................................................................................45 5.11.1 Stopping the CICS/MQ Capture ........................................................................................................48 5.11.2 Stopping the CICS/SQL Capture .......................................................................................................49 5.11.3 Stopping the IP CICS Sockets (TCP) Capture ...................................................................................49

5.12 STOPPING NASTEL INTERFACE TRANSACTION NSTS .................................................................................50 5.13 RESTARTING NASTEL INTERFACE TRANSACTION NSTS ............................................................................50 5.14 DEACTIVATING CICS INTERFACE ...............................................................................................................51

5.14.1 Uninstalling CICS MQ Monitoring ..........................................................................................................51

CHAPTER 6: COMMANDS ....................................................................................................................................53

6.1 START .......................................................................................................................................................53 6.2 STOP ..........................................................................................................................................................53 6.3 DISPLAY ...................................................................................................................................................53

6.3.1 DISPLAY DATASPACE ........................................................................................................................53 6.3.2 DISPLAY COUNTS ...............................................................................................................................54 6.3.3 DISPLAY QMON ..................................................................................................................................54

6.4 RESET .......................................................................................................................................................54 6.4.1 RESET DATASPACE ............................................................................................................................54 6.4.2 RESET COUNTS ...................................................................................................................................55

6.5 STATUS .....................................................................................................................................................55 6.6 CHANGE ...................................................................................................................................................55 6.7 UPDATE ....................................................................................................................................................55

CHAPTER 7: UTILITIES ........................................................................................................................................57

7.1 DUMPCOM ...............................................................................................................................................57 7.2 FREECOM .................................................................................................................................................58 7.3 DELETENT ...............................................................................................................................................59

CHAPTER 8: DIAGNOSTIC MESSAGES ............................................................................................................61

APPENDIX A: REFERENCES ..............................................................................................................................139

A.1 NASTEL DOCUMENTATION ........................................................................................................................139 A.2 NASTEL SAMP LIBRARY CROSS REFERENCE ...........................................................................................139 A.3 NASTEL JCL LIBRARY CROSS REFERENCE ...............................................................................................140

APPENDIX B: CONVENTIONS ...........................................................................................................................141

B.1 TYPOGRAPHICAL CONVENTIONS ...............................................................................................................141

APPENDIX C: EXEC CICS GROUPS AND COMMANDS...............................................................................143

C.1 EXEC CICS GROUPS ................................................................................................................................143 C.2 EXEC CICS COMMANDS (CURRENTLY API ONLY COMMANDS) .............................................................144

Nastel XRay Probes for z/OS Table of Contents

XR_zOS.004 v © 2021 Nastel Technologies, Inc.

APPENDIX D: EXEC SQL GROUPS AND COMMANDS ................................................................................ 151

D.1 EXEC SQL GROUPS ................................................................................................................................. 151 D.2 EXEC SQL API ....................................................................................................................................... 152

APPENDIX E: IP CICS SOCKETS API COMMANDS ..................................................................................... 157

E.1 IP CICS SOCKETS API ............................................................................................................................. 157 E.2 TCP API GROUP COMMANDS .................................................................................................................. 158

GLOSSARY ............................................................................................................................................................. 161

Table of Contents Nastel XRay Probes for z/OS

© 2021 Nastel Technologies, Inc. vi XR_zOS.004

This Page Intentionally Left Blank

Nastel XRay Probes for z/OS Chapter 1: Introduction

XR_zOS.004 7 © 2021 Nastel Technologies, Inc.

Chapter 1: Introduction This manual describes the installation and use of Nastel XRay probes for z/OS. There is also a section

describing the diagnostic messages produced by Nastel XRay.

• This product is compatible with any version/release of z/OS.

• Any version of IBM MQ that runs on z/OS is supported up to version 9.x

Check the README.txt file for this package for any last minute changes.

1.1 How This Guide is Organized

Chapter 1: Identifies the history of the document, its intended audience, and a listing of additional

related documents. System requirements are outlined, alongside with technical support

and reference information.

Chapter 2: Contains a brief functional description of Nastel XRay and the probe.

Chapter 3: Provides instructions for new installations of Nastel XRay probe components.

Chapter 4: Provides post installation instructions for using the probe.

Chapter 5: Provides instructions for installing the probe for CICS.

Chapter 6: Provides probe commands and their definitions.

Chapter 7: Describes probe utilities.

Chapter 8: Describes planning of the IBM MQ Log environment.

Appendix A: Provides a detailed list of reference information required for installation of the probe.

Appendix B: Contains conventions used in this document.

Appendix C: Provides EXEC CICS groups and commands.

Appendix D: Provides EXEC SQL groups and commands.

Appendix E: Provides IP CICS Sockets API commands.

Glossary: Definitions of unique and common acronyms and terms.

Index: Contains an alphanumeric cross reference of topics and subjects of importance.

Chapter 1: Introduction Nastel XRay Probes for z/OS

© 2021 Nastel Technologies, Inc. 8 XR_zOS.004

1.2 History of This Document

Release Date Document Number Summary

May 2020 XR_zOS.001 Initial release

June 2020 XR_zOS.002 Updates to PTO information in section 5.6. Update table

4-1.

September 2020 XR_zOS.003 Updates to Table 4-1. Add Tables 4-2 and 4-3. Move

section QMON (Queue Monitor Subtask), it is now 4.7.

Updates in section 4.8 (Dataspace Management) and 4.9

(Transmitter Subtasks). Update section 1.6.

January 2021 XR_zOS.004 Update section 5.5, add sections 5.5.1 and 5.5.2.

1.2.1 User Feedback

Nastel encourages all users and administrators to submit comments, suggestions, corrections, and

recommendations for improvement for Nastel documentation. Please send your comments via e-mail:

[email protected]. You will receive a written response, along with status of any proposed change,

update, or correction.

1.3 Related Documents

The complete listing of related and referenced documents is listed in Appendix A of this guide.

1.4 Release Notes

See README.txt files on installation media. Release notes and updates are also available through the

Resource Center at: https://customers.nastel.com

1.5 Intended Audience

This document is intended for personnel installing and customizing Nastel’s products. The installer

should be familiar with z/OS system programming.

NOTE: The installer may need administrative privileges for the target platform.

1.6 System Requirements

The Probes must be individually installed on each location required. Each probe selected based on

system requirements.

Supported environments:

• Operating Systems:

o z/OS (all releases supported by IBM in GA Status)

• IBM MQ version 8.0, 9.0 and 9.1

• IBM z10 Server and newer

• CICS (CICS MQ Adapter)

o CICS5.3

o CICS5.4

https://customers.nastel.com/

Nastel XRay Probes for z/OS Chapter 1: Introduction


Workload Manager (WLM)

NSQTI address space requires a service class or dispatching priority equal to CICS. The primary reason

is to allow this address space time to process intercepted messages at the rate in which CICS is operating

in. Otherwise, dataspaces and/or the Nastel local queue would fill up and future intercepted messages

would have to be discarded. If assistance is needed, consult your system programmer or Nastel technical

support.

Data Spaces

The probe creates dataspaces using the scope level, SCOPE=ALL. The probe creates ALETs on the

PASN-AL access list for the dataspaces allowing all the subtasks to have access to them. Batch Jobs and

TSO users create one ALET at a time on the DU-AL access list. When switching to another dataspace the

current ALET is deleted from the DU-AL access list and a new ALET is created for the next dataspace.

For CICS, the ALETs are created using the PASN-AL access list. Similar to batch, these ALETs are

recreated by the CICS Nastel subtask whenever the probe is restarted.

Common Storage

The probe uses one persistent global name/token pair token. The token holds the address to our Common

Storage area. The size will vary based on the NumOfProbes option specified in the first probe started

following an initial Program Load (IPL). It will allocate approximately (256 * n_probes) + 350 bytes in

subpool 228. This storage will remain allocated until the next IPL. The DELETENT utility may be used

to remove the global name/token pair and cleanup the Nastel common storage area without an IPL.

Additionally, each dataspace is mapped to a control block that is 96 bytes of common storage in subpool

228. This area varies based on the “DspNumber” parameter specified in the Dataspaces section of the

configuration file.

There is also a small common storage area created by the supervisor of the transmitter subtasks in subpool

241. It contains the ecbs used to post the active transmitter task when messages are placed on the

dataspace by batch jobs, started tasks, TSO users, or CICS regions. This area varies based on the

“DspNumber” parameter in the Dataspaces section in the configuration file.

Table 1-2. Common Storage

Area Subpool Minimum Bytes Maximum Bytes Released

Probe area 228 2416 25968 N

DDB blocks 228 288 1920 Y

CICS stub 245 440 440 N

XECB area 241 28 96 Y

Fixed Storage

The probe loads modules totaling approximately 28K into fixed storage. The storage area associated with

each module is released when the probe is stopped.

Spool Requirements

The probe uses very little spool space when the trace facility is not turned on. When the trace is active

and there is MQ activity, log messages are written to the probe’s log sysout file. Spool usage size may

vary depending on volume of MQ intercepted messages.

Disk Storage Requirements

The probe installation requires approximately 5 cylinders of disk space.

Chapter 1: Introduction Nastel XRay Probes for z/OS


LX Resources

Nastel uses 2 PC routines per probe. The NSYSLX parameter in the IEASYSxx parmlib member must be

increased by 2 on each OS to support the additional LX resources.

Nastel Token Name\Pair

The Nastel token name used for the token name\pair is NastelTechV4R5.

The probe creates a global persistent token name\pair that is associated with the Probe area identified in

the Common Storage table above. The token is used at the system level. All probe address spaces use

this area to provide the resources needed for the batch and CICS collection processes.

The CICS interface transaction uses the same token name, but it is created using a non-persistent token at

the address space level. The token is removed when the CICS region is shutdown. This token name is

used to identify the local environment when the CICS MQ Crossing Exit is processing MQ messages.

1.7 Terms and Abbreviations

A list of terms and abbreviation used in this document is located in the Glossary.

1.8 Technical Support

If you need additional technical support, you can contact Nastel by telephone or by e-mail.

To contact Nastel technical support by telephone, call (800) 963-9822 ext. 1. If you are calling from

outside the United States, dial 001-516-801-2100.

To contact Nastel technical support by e-mail, send a message to [email protected]. You can also

contact Nastel support via the support website.

To access the Nastel automated support system (user ID and Password required), go to:

http://support.nastel.com/, or visit the Nastel Resource Center at www.nastel.com/resources/. Contact

your local Nastel Administrator for further information.

1.9 Conventions

Refer to Appendix B for typographical and naming conventions.

mailto:[email protected]

http://support.nastel.com/

http://www.nastel.com/resources/

Nastel XRay Probes for z/OS Chapter 2: About Nastel XRay


Chapter 2: About Nastel XRay

Nastel XRay detects, gathers, and then analyzes transactions and message data in real time, on demand,

and then summarizes the collective data. The transaction and message data are obtained from transaction

probes for transaction process applications.

2.1 Nastel XRay Features • Tracks transaction paths end-to-end.

• Detects delayed and incomplete transactions.

• Analyzes transaction throughput and message volume in real-time.

• Identifies performance bottlenecks.

• Detects transactions with monetary value using rules set in the user-configured transaction probe.

• Compiles built-in reports about transaction activity on a daily, weekly, and monthly basis.

• Includes user-defined, rule-based policies for real-time monitoring of all message exchanges.

• Provides proactive notification and automated actions based on user-defined criteria.

2.2 Nastel XRay Components

The three major components of Nastel XRay:

• Probes

• Nastel XRay server

• Nastel XRay web interface

The probe provides the code that front-ends IBM MQ applications for the purpose of collecting

transaction-related data. The probe intercepts the transaction message data and send this information

remotely to the Nastel XRay stream over IBM MQ.

You can write any application in C/C++, Java, COBOL or other shell scripts that use the MQI

interface and have the probe intercept the calls.

Summary of Reports:

• Complete Transactions: Messages that have been received and read. Where all transaction

message writes have been matched with message reads.

• Incomplete Transactions: Transactions where a matching message read is missing for a message

write.

• Message Statistics: Inbound/outbound message volume, sizes (average, maximum, minimum), by

date, application, resource (queues etc), or host.

• Message Latency: Delays between message write and read on a resource.

• Transaction Trace: End-to-end trace of one, or all transactions in a given time, optionally,

including transaction details.

• API Call Statistics: By date, application, and resource.

Chapter 2: About Nastel XRay Nastel XRay Probes for z/OS



Nastel XRay Probes for z/OS Chapter 3: Installing Probe Components


Chapter 3: Installing Probe Components

3.1 Transferring Data Sets to z/OS

The XMIT files provided from Nastel Technologies can be uploaded to the z/OS operating system using

FTP. If you desire to preallocate the datasets on z/OS before using FTP, create the files using the

attributes shown in the chart below.

It is not necessary to preallocate the target datasets on z/OS if you use the QUOTE SITE command with

FTP. Ensure your source and target directories are correct.

For example:

ftp <host>

Enter: user <id>

Enter: password <******>

Enter: bin

Enter: quote site lrecl=80 recfm=fb blksize=3120 primary=10 blocks secondary=5 blocks

put JCLxx.XMI


put LOADxx.XMI


put SAMPxx.XMI

The required file allocations on the mainframe are listed below.

Table 3-1. Minimum z/OS File Allocations for Data Sets

DSORG RECFM LRECL BLKSIZE Blks

JCLxx.XMI PS FB 80 3120 10

LOADxx.XMI PS FB 80 3120 950

SAMPxx.XMI PS FB 80 3120 30

JCLxx.XMI represents the name of the file on the mainframe. It could be USERID.JCLxx.XMI where

USERID is your TSO logon ID. The same applies for the other two files (LOAD, SAMP). These files can

be allocated using 3.2 in Interactive System Productivity Facility (ISPF) if you use the preallocation

method. These are temporary files and may be deleted once the installation is successful.

Chapter 3: Installing Probe Components Nastel XRay Probes for z/OS


3.2 Restoring Files

Once transferred to the mainframe these files must be RECEIVED into PDS files. The RECEIVE

command will extract the files and dynamically create the proper space when used as follows. HLQ

represents the high-level qualifier for each dataset. MLQ is the middle-level qualifier. These are the

names that are to be substituted in Job Control Language (JCL) streams. The block sizes for the FB files

may be changed to conform to site standards. The load library should remain the same as in Table 3-2.

Receive indsn(JCLxx.XMI)

The response to the prompt should be: dsn(‘HLQ.MLQxx.JCL’)

Receive indsn(LOADxx.XMI)

The response to the prompt should be: dsn(‘HLQ.MLQxx.LOAD’)

Receive indsn(SAMPxx.XMI)

The response to the prompt should be: dsn(‘HLQ.MLQxx.SAMP’)

The following table shows the dataset attributes that will be created when they are received. The space

may vary at different installations.

Table 3-2. Minimum z/OS File Allocations

DSORG RECFM LRECL BLKSIZE BLKS

HLQ.MLQxx.JCL PO FB 80 8000 4

HLQ.MLQxx.LOAD PO U 0 27998 76

HLQ.MLQxx.SAMP PO FB 320 27840 6

The current release of IBM's Mutli-Tasking Facility (MTF) only supports load modules stored in a PDS

and Nastel XRay for z/OS Probes using MTF to manage subtasks. If you are planning to copy the load

modules in HLQ.MLQxx.LOAD to another runtime dataset, please make sure that the target dataset is a

PDS and not a PDSE(LIBRARY).

There are now three installed target libraries:

• MLQxx.JCL: This library contains JCL for the probe’s started tasks. The library also contains

JCL for the JOBs that can be used to configure and verify the installation.

• MLQxx.LOAD: This library contains the load modules for the probe’s started tasks. This library

contains the agents used to support Batch IBM MQ calls, and MQ calls invoked wothin CICS.

Also, the modules for the jobs used to verify the installation reside in this library.

• MLQxx.SAMP: This library contains the load modules for the probe’s started tasks. This library

contains the agents used to intercept MQ calls within your Batch jobs, Channel Initiator

(CHINIT) and CICS transactions. Also, the modules for the jobs used to verify the installation

reside in this library.

3.3 Installing the Probe

3.3.1 Creating Nastel Front-end Modules

The JCL member ALOCAUTH must be tailored and run to create the front-end modules that are used

with the Nastel interceptor environment. This step must be run after creating the runtime library.

Edit the member replacing the HLQ for the Nastel libraries to match installation. Remove any steps for

versions of MQ not installed locally, and run it.



//ALOCAUTH JOB (0000,NASTEL),'ALOCAUTH',MSGCLASS=X,REGION=0M,

// CLASS=A,NOTIFY=&SYSUID

//*--------------------------------------------------------------------

//*

//* Create the Nastel MQSeries front-end modules

//*

//* Replace the ++ variables with your naming standards

//* Delete any steps referenceing versions you will not be using

//*

//* ++hlq++ - Nastel high level qualifier

//* ++mqserxx++ - WebsphereMQ high level qualifier where 'xx' is

//* Version Modification Level

//*

//*--------------------------------------------------------------------

//*

//*

//*--------------------------------------------------------------------

//*

//* WMQ Version 8.0.x

//WMQV80X EXEC PGM=IEBCOPY

//SYSUT1 DD DSN=++mqser80++.SCSQAUTH,DISP=SHR

//SYSUT2 DD DSN=++hlq++.LOAD,DISP=SHR

//SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,1)


//SYSPRINT DD SYSOUT=*

//SYSIN DD *

COPY INDD=SYSUT1,OUTDD=SYSUT2

SELECT MEMBER=((CSQBCON,N80BCON),(CSQBDSC,N80BDSC))

SELECT MEMBER=((CSQXSRVA,N80XSRVA))

/*

//*

//*--------------------------------------------------------------------

//*


//WMQ90X EXEC PGM=IEBCOPY






//SYSIN DD *




/*

//*

//*--------------------------------------------------------------------

//*


//WMQ91X EXEC PGM=IEBCOPY






//SYSIN DD *






/*

//

3.3.2 Authorized Program Facility Authorization

The Nastel load library HLQ.MLQxx.LOAD must be APF (Authorized Program Facility) authorized as

required. Add the following statement(s) to the appropriate PROG member in PARMLIB:

APF ADD DSNAME (HLQ.MLQxx.LOAD) VOLUME (volser)

Determine the volumes on which the load libraries above resided on and use these volumes on their

respective APF ADD statements shown above.

HLQ.MLQxx.LOAD library contain modules that provide channnel initiator activity data capture for IBM

MQ. This load library must be concatenated ahead of any IBM MQ libraries in their respective Channel

Initiator PROC.STEPLIB.

For Batch MQ data capture, HLQ.MLQxx.LOAD must be concatenated ahead of any IBM MQ library in

STEPLIB. Even though HLQ.MLQxx.LOAD is APF-authorized, Batch STEPLIB remains not APF-

authorized. APF-authorization is not required for Batch MQ data capture. However, under MQ Channel

Initiator, all libraries within STEPLIB must be APF-authorized.

3.3.3 Setup Additional LX Resources

Nastel uses 2 PC routines per probe.

• Space switch PC routine that runs in the probe’s address space that performs service routines for

user applications.

• cp-PC routine allowing authorized functions to be called from the user applications. These

address spaces do not need to be APF authorized. The main functions performed in these

routines allow the applications to obtain and delete ALETs when accessing our dataspaces.

The NSYSLX parameter in the IEASYSxx parmlib member must be increased by 2 to allow the number

of LX resources used by our PC routines per OS.

3.3.4 Tailoring JCLs

Before submitting the sample JCL, configuration is required. Refer to the section, Configuring the Probe.

3.3.4.1 Transaction Interceptor JCL

The JCL needed to create an instance of the probe’s started task is found in the JCL library. The member

name is called NSQTI and is shown below:

//NSQTI PROC

//********************************************************************

//*

//* Transaction probe started task

//*

//* +instload++ - Installation loadlib created from TSO Receive

//* ++mqser++ - WebsphereMQ high level qualifier

//* ++instsamp++ - Installation samplib created from TSO Receive

//*

//********************************************************************

//RUN EXEC PGM=NTI00001,REGION=0M,

// TIME=1440

//STEPLIB DD DSN=++instload,DISP=SHR



// DD DSN=++mqser++.SCSQAUTH,DISP=SHR


//SYSIN DD DSN=++instsamp++(TICONFIG),DISP=SHR

++hlq++ are set as defined above.

++mqser++ are the high level qualifier(s) of the authorized MQ library to which the probe’s started task

will connect to a queue manager. Note that this is not necessarily the same queue manager to which batch

JOBs, TSO users, and CICS regions are connecting.

TICONFIG is a member in the SAMP file that contains the configuration parameters for the probe’s

started task. Each copy of the probe must have its own configuration file. The SYSIN file must point to a

sequential dataset or a member of a partitioned dataset that is allocated with an LRECL of 320. Copy

TICONFIG into this dataset or member of the partition dataset and modify it accordingly. The JCL

shown above must be placed in a PROCLIB defined to JES2 or JES3. Refer to the section, Probe

Configuration File (TICONFIG), for a breakdown of each parameter in TICONFIG file. Adjust these

parameters to suit your processing needs prior to submitting NSQTI JCL.

3.3.5 Configuring the Probe

This section provides the information necessary to configure the probe.

3.3.5.1 Message Prefix

The Nastel message prefix used to identify the Nastel messages on the IBM mainframe platforms

(OS/390 or z/OS) owns the characters ‘NSQ’ associated with all messages. In the event it is necessary for

some reason to change the prefix, a user may at their discretion override the message prefix using the

PARM parameter in the probe’s started task JCL as follows.

EXEC PGM=NTI00001,PARM=’pre’

All messages issued will be identified with the 3 character prefix specified on the PARM statement.

If the PARM parameter is not coded, the default is NSQ.

3.3.5.2 Probe Configuration File

Each probe must have its own configuration file (TICONFIG). The file is read-only and is not modified

by the probe. The file is divided into different sections. Each section begins with a name that stands

alone on a line. A section ends with a semi-colon that also stands alone on the line. An ‘*’ in column 1 is

a comment card. Comments within a line begin with // and anything to the right is considered a comment.

The parameters within a section must be coded on one line. The area names (General, IBM MQ, etc.) and

parameter names such as ProdId are case sensitive. The assigned parameter values for ProdId=test are not

the same as ProdId=TEST. If blanks are required within a character parameter, enclose it in double

quotes.

Following is a sample configuration file:

*----------------------------------------------------------------------

Product : API Interceptor

* Member : TICONFIG

* Description : This member contains the configuration settings

* for the API Interceptor that is pointed to by

* the DDNAME SYSIN in the JCL.

*

*

* Notes: The following parameters contain default values. Refer to

* AutoPilot M6/Transaction Monitor Probe for Websphere MQ (z/OS)

* for an explanation on each parameter. Default value may not be

* sufficient for your needs.



*----------------------------------------------------------------------

General //

ProdId=++prodId++ // Product id

CustName=++customer name++ // Customer Name

NumOfProbes=8 // # of Probes

MSG2Queue=DSPC // Deliver intercepted msgs to

// Nastel queue via dataspaces

Transmitter //

xmitInterval=60 // Dispatch interval in seconds

WebSphereMQarea //

Qmgr=++qmgr++ // Queue manager name

Expiry=30 // 30 seconds on Nastel queue

QueueName=NASTEL.APTM.MESSAGE // APTM local or alias queue

ConnectRetry=60 // Nbr of seconds between

// MQCONN calls

MsgSize=1024 // Max MQ data to capture for

// GET, PUT and PUT1

PutEnableTime=10 // Interval in seconds to check

// Nastel queue for PUT enable

MsgcntlInhibitQ=keep // Keep msgs when Que inhibited

MsgcntlTaconDown=keep // Keep msgs when TACON down

Dataspaces //

DspNumber=3 // # of dataspaces created

DspSize=256 // 524 * 4k = 1m each dataspace

Filters // Filter area

General Area

These parameters are for the general operation of the Transaction Interceptor.

ProdId – Used to distinguish one API Interceptor probe from another. If more than one

probe is running, each must have a unique value. This is a required parameter.

CustName – This is the client’s name. This is a required parameter.

NumOfProbes – Defines the limit of number of probes allowed to run on an OS. The first

probe started following an IPL, sets the limit and creates the probe static area in

ECSA. The default is 8.

Msg2Queue - Defines the method in which intercepted message is delivered to

NASTEL.APTM.MESSAGE queue. The default is DSPC for dataspace. Valid options are:

DSPC for dataspace method; MQPUT for MQOPEN/MQPUT method; and MQPUT1 method.

Transmitter area

These parameters are used for the transmitter subtasks.

XmitInterval – This is the transmitter’s dispatch interval in seconds for the Active

transmitter subtask. The Active transmitter checks the state of the connection to the

QMGR for quiescing state if the Queue Manager is terminated. The Active transmitter

subtask will also process the MESSAGE queue attempting to retrieve as many messages

from the Active dataspace before the Queue Manager ends. The default value is 60

seconds.

WebSphereMQarea

These parameters relate to the queue manager to which each transmitter subtask

connects. These fields will depend on the definitions in Nastel’s Local Queue Manager.

Qmgr – List of Queue managers, separated by commas, you want monitored by this NSQTI

task. This NSQTI task will connect to the first queue manager. All intercepted

messages from queue managers in the list will be written to a local queue named

NASTEL.APTM.MESSAGE which must exist on the Queue Manager connected to by this NSQTI

task.



For example: You have a MQ shop of 12 Queue Managers, PM01 thru PM06, TM01 thru TM06

and you want six of them monitored by this NSQTI started task. You can specify QMGR=

parameter in the following ways:

QMGR=PM01,PM02,PM03,PM04,PM05,PM06

NSQTI task connects to PM01. Batch MQ and CHIN activity to queue managers PM01 thru

PM06 will be intercepted by this NSQTI task.

==OR==

QMGR=PM01,PM

NSQTI task connects to PM01. Batch MQ and CHIN activity to queue manager names that

begin with “PM” will be intercepted by this NSQTI Task.

Expiry – This is the expiry time for messages in seconds. MQ will purge messages on

the Nastel message queue specified by the QueueName once this value is exceeded. The

default value is 30 seconds. This is an optional parameter.

QueueName – This is the name of the queue into which all intercepted messages will be

put. These messages contain a copy of the real contextual MQ data or portion thereof

based on the MsgSize parameter. The name of the local queue is NASTEL.APTM.MESSAGE and

must exist in the Queue Manager.

Queue Alias names can be defined referencing the target queue name NASTEL.APTM.MESSAGE

and used for the QueueName parameter. A queue alias name, NASTEL.APTM.APIEXIT may be

created using sample member TAMQSC in the SAMP library. The default value is the local

queue name, NASTEL.APTM.MESSAGE. This is an optional parameter.

ConnectRetry - An MQCONN call will be tried at the specified interval if the

connection to the queue manager fails or if the queue manager was not up when the API

interceptor probe was started. The default value is 60 seconds. This is an optional

parameter.

MsgSize – The number of bytes of MQ contextual message data to be captured on MQPUT,

MQPUT1 and MQGET calls. The default value is 1024 bytes. This is an optional

parameter.

The MsgSize supports an override value outside of the minimum\maximum range, which is

0. If 0 is specified, the user is requesting to send the entire contextual message

with no truncation. There can be higher resource usage when running with the override

value.

PutEnabletime - This is the time interval in seconds in which the transmitter subtask

will check the Nastel MQ Intercept queue (NASTEL.APTM.MESSAGE queue) to determine when

the PUT function is enabled. This time value becomes active when the user sets the PUT

to disable on the Nastel MQ Intercept queue. The default value is 10 seconds. This is

an optional parameter.

Note: When a large interval is used, the MQ intercepted messages are not received

until the PUT is set to enable (from disabled state) and the PutEnableTime expires.

The recommendation is to set this to the default value.

MsgcntlInhibitQ – This option controls whether the messages are retained on the

dataspaces or discarded when the APTM.MESSAGE queue is changed to PUT disabled. The

values supported are KEEP and DISCARD. The default is KEEP.

This option also applies when the APTM.MESSAGE queue is PUT disabled from the QMON

subtask.

MsgcntlTaconDown – This option controls whether the messages are retained on the

dataspaces or discarded when the TACONN task is terminated. The values supported are

KEEP and DISCARD. The default is KEEP.

CurrentDepth – This is the maximum currentdepth threshold value used by the QMON

subtask to compare against the real currentdepth of the APTM.MESSAGE queue. When the

threshold is exceeded, the APTM.MESSAGE queue is set to PUT disabled. This is an

optional parameter. When not specified, the QMON subtask is not activated.

CurrentDepthMin – This is the minimum currentdepth threshold value used by the QMON

subtask to compare against the real currentdepth of the APTM.MESSAGE queue. When

messages are removed from the queue and the currentdepth falls below this currentdepth

value, the APTM.MESSAGE queue is set to PUT enabled. This is an optional parameter.

This option is only valid when the CurrentDepth parameter is specified. The default

value is 0.



CurrentDepthInt – This is the time interval in seconds the QMON subtask will check the

currentdepth level on the APTM.MESSAGE queue. The default is 5 seconds. If the

CurrentDepth option is not specified, this option is ignored.

DataSpaces Area - These parameters relate to dataspaces created by the Transaction

Interceptor.

DspNumber – This is the number of dataspaces that the Transaction Interceptor will create at start-up time. Each dataspace is managed by an associated transmitter

subtask. The default number of dataspaces is 3.

DspSize – This is the number of 4K pages in the dataspace. The default size is 256 (256 * 4096 or 1,048,576 bytes). The maximum size is 524288 (524288 * 4096 or

2,147,483,648 bytes).

Messages area – This area is used for message ids that are routed to the MVS console.

This is an optional area.

Number,[NO] – This value should be a 4-digit number indicating the message number that

is routed to the MVS console. You may enter as many Message numbers as desired in the

Message area section.

Note: For any of the start-up probe messages that are already routed to the console,

these messages can be removed from the console by using the NO option.

Filters Area - This area is related to filters that allow the user to exclude or

include specific API commands, Queue names, Application names, Transaction names, etc.

Each name on a filter command must end with a comma. Currently, all names specified

on a Filter command must fit within a single 80-byte char line. There is no

continuation line support. However, you can repeat the filter command with additional

names.

QUEUES_EXC - Application queue names you want to exclude from intercept

QUEUES_EXC=NONE (Default)

Max queue name size is 48-characters

Ex: QUEUE_EXC=SYSTEM,NASTEL

Exclude all queue names that begin with SYSTEM and NASTEL

QUEUES_INC - Application queue names you want to intercept

QUEUES_INC=ALL (Default)

Max queue name size is 48-characters

EX: QUEUE_INC=XYZ

Include all queue names that begin with XYZ

TOPIC_EXC - Application topic strings you want to exclude from intercept

TOPIC_EXC=NONE (Default)

Put the topic within quote if the string contains spaces.

Topic string is case sensitive.

Ex: TOPIC_EXC=nastel,'California Beachs/Venice Beach'

Exclude all topic strings that begin with nastel or

California Beachs/Venice Beach

TOPIC_INC - Application topic strings you want to include from intercept

TOPIC_INC=ALL (Default)

Put the topic within quote if the string contains spaces.

Topic string is case sensitive.

Ex: TOPIC_INC=Broker,'California Beachs/'

Include all topic strings that begin with Broker or

California Beachs/

APPLS_EXC - Application names you want to exclude from intercept

APPLS_EXC=NONE (Default)

Max program name size is 8-characters

EX: APPLS_EXC=ABC

Exclude all program names that begin with ABC

APPLS_INC - Application names you want to intercept

APPLS_INC=ALL (Default)

Max program name size is 8-characters



EX: APPLS_INC=B,C,D,E,F,G

Include all program names that begin with B, C, D, E, F, and G

API_MASK - Identify MQ APIs you want to intercept

API_MASK=ALL (Default - intercept all MQ API)

Valid MQ API are: MQCONN, MQDISC, MQOPEN, MQCLOSE, MQGET, MQPUT, MQPUT1, MQINQ, MQSET,

MQBACK, and MQCMIT

EX: API_MASK=MQGET,MQPUT,MQPUT1

Intercept only MQGETs, MQPUTs, and MQPUT1s

TRANS_EXC – Transaction names you want to exclude from intercept

TRANS_EXC=NONE (Default)

Max transaction name is 8-characters

EX: TRANS_EXC=NAST

Exclude all transaction names that begin with NAST

TRANS_INC – Transaction names you want to intercept

TRANS_INC=ALL (Default)

Max transaction name is 8-characters

EX: TRANS_INC=NAST

Include all transaction names that begin with NAST only

CICSGRP_EXC – EXEC CICS Group names you want to exclude from intercept

CICSGRP_EXC=ALL (Default)

Refer to Appendix E.1 EXEC CICS Groups for a list of group names.

EX: CICSGRP_EXC=FILE,ALLOCATE,STORAGE

Exclude all EXEC CICS commands in groups FILE, ALLOCATE, and STORAGE

CICSGRP_INC – EXEC CICS Group names you want to intercept

CICSGRP_INC=NONE (Default)

Refer to Appendix E.1 EXEC CICS Groups for a list of group names

EX: CICSGRP_INC=SYNCPOINT

Include only EXEC CICS commands from SYNCPOINT group

SQLGRP_EXC – EXEC SQL Group names you want to exclude from intercept.

SQLGRP_EXC=ALL (Default) which means exclude all EXEC SQL group commands.

Refer to Appendix F.1 EXEC SQL Groups for a list of group names

EX: SQLGRP_EXC=OPEN,CLOSE

Exclude EXEC SQL API commands that fall under OPEN and CLOSE groups.

TCPCMD_EXC – TCP API Group names you want to exclude from intercept.

TCPCMD_EXC=NONE (Default) which means exclude no TCP group commands.

Refer to Appendix F.1 TCP Groups for a list of group names.

EX: TCPCMD_EXC=OPEN,CLOSE

Exclude EXEC SQL API commands that fall under OPEN and CLOSE groups.

APPLS_DIST_LUWS – Program and transaction names depending on Batch or CICS that

require switching of LUW ID for MQ API operations MQGET, MQPUT, and MQPUT1.

APPLS_DIST_LUWS=NONE (Default) which means use standard LUW ID switching based on the

observance of MQCMIT/MQBACK (Batch) or EXEC CICS SYNCPOINT (CICS).

EX: APPLS_DIST_LUWS=NSQMQAPP,XYZ1,ABC2

LUW ID switching occurs for each MQGET, MQPUT, and MQPUT1 executed out of Batch

program NSQMQAPP. All other batch programs use standard LUW ID switching based on the

observance of MQCMIT/MQBACK.

LUW ID switching occurs for each MQGET, MQPUT, and MQPUT1 executed out of CICS

transactions XYZ1 and ABC2. All other CICS transactions use standard LUW ID switching

based on the observance of EXEC CICS SYNCPOINT.



Table 3-3. Configuration File Parameters

Area Parameter Minimum Maximum Length Required Default Override

General

ProdId N/A N/A 4 Y N/A N/A

CustName N/A N/A 32 Y N/A N/A

NumOfProbes 8 100 N/A N 8 N/A

Transmitter XmitInterval 10 60 N/A N 30 N/A

IBM MQ

Qmgr N/A N/A 4 N default

qmgr

N/A

Expiry 0 86400 N/A N 30 N/A

QueueName N/A N/A 48 N N/A N/A

MsgSize 512 4096 N/A N 1024 0

ConnectRetry 10 3600 N/A N 60 N/A

PutEnableTime 5 60 N/A N 10 N/A

CurrentDepth 1000 999999999 N/A N N/A N/A

CurrentDepthMin 0 999998999 N/A N 0 N/A

CurrentDepthInt 1 15 N/A N 5 N/A

MsgcntlInhibitQ N/A N/A 7 N KEEP N/A

MsgcntlTaconDown N/A N/A 7 N KEEP N/A

DataSpaces DspNumber 3 15 N/A N 3 N/A

DspSize 256 524288 N/A N 256 N/A

Messages Number N/A N/A 4 N N/A N/A

3.3.6 Running Multiple Transaction Interceptor Probes

More than one probe may run on the same z/OS operating system. The limit is controlled by the

NumOfProbes parameter in the configuration file. Each probe is connected to a unique ProdID (Probe

ID) and Queue Manager (QMGR). The number of connections to each QMGR varies based on the

number of dataspaces used. This is defined by the DspNumber parameter in the configuration file.

The maximum number of dataspaces allowed per operating system is 15. Therefore, the DspNumber is

restricted to 15, which ensures there can only be a total of 15 transmitter subtasks created along with a

dataspace.

For Batch MQ applications, a probe should be connected to the QMGR that is used by those applications.

When CICS is involved, CICS is connected to a Probe ID specified on NSQINIT= parms. For each CICS

region that is monitored with Nastel XRay, you will run a probe that is connected to the same QMGR.

3.3.7 Change ProdId Parameter Considerations

The ProdId parameter is used to set the probe’s product id once the probe is started. A 256-byte probe

area is created in the name/token pair area in Extended Common Storage Area (ECSA) once a probe is

started. All outside users such as batch type jobs and CICS regions interfacing with IBM MQ will

reference this area that is using either the same QMGR or same ProdId name as the probe. The QMGR

and ProdId parameters together identify the probe’s existence.

It is recommended to set this value to a unique value during the initial installation.



If it is necessary to change the ProdId parameter for a probe after the probe had already been started, it is

recommended to reset the ECSA area for all probes on the OS.

If an existing probe’s jobname is changed and not the ProdId an additional entry is populated in the

Nastel name/token pair area causing duplicate entries to exist referencing the same QMGR. With batch

jobs, it is possible the wrong entry will be referenced and no collection may occur. When CICS regions

start collection on MQ calls, each CICS region relies on the PID name specified on the INITPARM

statement for NSQINIT. (Refer to the section, System Initialization Parameter Input Values.) The

objective is to ensure that when a probe is restarted the initial entry created in the name/token pair area is

reused.

To solve this situation, it is recommended to reset the name/token pair area used in ECSA storage as

follows:

1. Stop all probes on the Operating System.

2. Run the DELETENT utility.

3. Correct the ProdId parameter as desired in the target probe. All probe’s ProdId parameters must be

unique.

4. Restart all probes. Any probe may be started first. The very first probe that is started will create the

name/token pair area size based on the NumOfProbes parameter.

For example, if your Operating System is running 12 probes, there should be 12 entries in the Nastel

token name\pair area populated. The DUMPCOM utility may be run to show these product entries that

reside in ECSA storage.

3.3.8 Queue Manager Definition File

Configure the queue manager that will be used for transaction monitoring. Create the following local

queues:

DEFINE QLOCAL('NASTEL.APTM.MESSAGE') +

DESCR('AutoPilot/TM message queue') +

DEFPSIST(NO) PUT(ENABLED) GET(ENABLED) +

SHARE DEFSOPT(SHARED) +

REPLACE

DEFINE QLOCAL('NASTEL.APTM.TEST.MESSAGE') +

DESCR('AutoPilot/TM CICS queue') +

DEFPSIST(NO) PUT(ENABLED) GET(ENABLED) +

SHARE DEFSOPT(SHARED) +

REPLACE

The object definitions can be found in the TAMQSC file located in the SAMP library. Sample Job

NASTQUES is provided in MLQxx.JCL to create these queues with a batch job.

3.3.9 External Security Definitions

Verify that your security definitions for RACF or OEM software vendor allow the following access:

The probe must be able to execute from the load libraries using STEPLIB or from the linklist.

Additionally, the probe requires the following:

• Have read access to all input files.

- Probe : SYSIN

• Must be allowed to connect to the queue manager, whether it was specified in the configuration

file or it uses the default queue manager.

• Have update access to the following queues:



Task Queue Name Security level

Nastel XRay probe NASTEL.APTM.MESSAGE UPDATE

CICS NASTEL transaction (NSTM) NASTEL.APTM.TEST.MESSAGE UPDATE

If your site requires that the probe proc requires a USERID, have your security administrator define a

userid for the Nastel tasks.

3.3.10 Activating Batch MQ Monitoring

To activate Nastel MQ monitoring for Batch, ensure the dataset created for HLQ.MLQ65.LOAD is

placed in front of all MQ load libraries in your STEPLIB concatenation.

NOTE:

The probe must be running before any batch job or TSO user runs any program that issues any MQ call invocations.

3.4 Channel Initiator (CHINIT) Monitoring

Please consult your security administrator on RACF Program Control and Execute Control features.

Datasets are Program Control and/or Execute Control enabled either by action of your site security

administrator or by product install where load modules are shipped in IBM MQ datasets. If Program

Control enabled, these datasets may have been added to PROGRAM class with READ access to indicate

that IBM MQ applications can run in a safe and controlled environment.

The introduction of HLQ.MLQxx.LOAD to your Channel Initiator startup procedure may cause your

IBM MQ environment to become unstable based on RACF Program Control and/or Execute Control

rules. If access is denied based on these rules, IBM MQ will abort the task with 5C6 abend. Your

Channel Initiator procedure is assigned a User ID at startup. This User ID does not have the proper

authority to access HLQ.MLQxx.LOAD.

You may see a message like the following:

ICH420I PROGRAM CSQXSRVA FROM LIBRARY HLQ.MLQxx.LOAD CAUSED THE

ENVIRONMENT TO BECOME UNCONTROLLED. CSQXJST MQ.SCSQAUTH

If you see a message like this in your Channel Initiator output after failing to start up, it is an indication

that your IBM MQ load library is Program Control enabled. You have a module with an alias of

CSQXSRVA. The User ID assigned to your Channel Initiator started task does not have proper

authorization to access HLQ.MLQxx.LOAD. In this situation, consult your Security Administrator to

allow your Channel Initiator User ID READ access to HLQ.MLQxx.LOAD

Use the following two sections to activate or deactiviate CHINIT monitoring, respectively.

3.4.1 Activate CHINIT Monitoring

To activate Nastel MQ monitoring for your Channel Initiator, ensure the dataset created for

HLQ.MLQxx.LOAD is placed in front of all MQ load libraries in your STEPLIB concatenation.

3.4.2 Deactivate CHINIT Monitoring

To deactivate Nastel MQ monitoring for your Channel Initiator, comment or delete the DD statement that

points to dataset created for HLQ.MLQxx.LOAD in front of all MQ load libraries in your STEPLIB

concatenation.



3.5 Uninstalling Nastel XRay z/OS Probe

3.5.1 Deactivating Batch MQ Monitoring

The Batch MQ interface can be disabled using the following methods.

To deactivate Nastel MQ monitoring from your Batch, comment or delete the DD statement that points to

dataset created for HLQ.MLQxx.LOAD in front of all MQ load libraries in your STEPLIB concatenation.

3.5.2 Uninstall Batch MQ Monitoring

To permanently remove the probe and batch front-end interface, uninstall as follows:

1. Stop all the probe tasks.

2. Run the FREECOM or DELETENT Nastel utility to remove the name/token pair from CSA.

3. If the IBM MQ library SCSQAUTH is not in the linklist, comment out (or remove) the Nastel load

library from the JCL for each batch job, TSO logon proc, and any Started Tasks. Restart your address

spaces and have TSO users logon again. This will ensure that the IBM’s MQ modules are no longer

front ended by the Nastel environment.

4. If the Nastel load library is front ending your batch applications using the linklst, then remove the

Nastel load library from the linklst and run the LLA refresh command as shown below.

F LLA,REFRESH

Nastel XRay Probes for z/OS Chapter 4: Using the Probe


Chapter 4: Using the Probe

4.1 Starting API Transaction Interceptor

The probe is started using the MVS START (/S) operator command. If the tailored Job Control

Language (JCL) for the probe is residing in PROCLIB and called NSQTI, the following command would

start the probe:

S NSQTI

When the message NSQ1400I WMQ z/OS operating is displayed in the JESMSGLG for NSQTI, the

probe is up and running.

If the probe does not come up, refer to Chapter 9: Diagnostic Messages, to determine the best solution to

the problems. If security problems occur, contact your security administrator to resolve those issues. If

you are unable to get the probe running and need assistance, contact Nastel support personnel.

4.2 Stopping API Transaction Interceptor

The probe is stopped using the MVS STOP (P) operator command. The following command stops the

transaction interceptor:

P NSQTI

4.3 Probe Messages

Messages produced by the probe are divided into separate SYSOUT classes in the output display in

Screen Display Search Facility (SDSF). Other important messages are written to the JESMSGLG of the

probe job.

All messages produced are written to an owners task SYSOUT file. Messages can be found in the

following SYSOUT files of the probe’s started task:

JESMSGLG –WTO messages issued by the probe are written here.

MAIN – messages written from the mainline task.

CNFG – messages written from the configuration processor.

LOGR – messages written from the logger subtask manager.

CMDP – messages written from the command subtask manager.

SUPV – messages written from the supervisor subtask manager.

XMITnnnn – messages written from the transmitter subtasks.

QMON – messages written from the queue monitor subtask manager (optional subtask).

Sample messages are shown for the JESMSGLG and MAIN:

The following messages are written to the JES MSG log for the probe:

14.58.33 JOB04681 MAIN NSQ1251I Command processor created. TCB=008D2318.

14.58.33 JOB04681 CMDP NSQ6000I Command processor started.

14.58.33 JOB04681 CMDP NSQ6400I Command processor operating.

14.58.33 JOB04681 MAIN NSQ1261I Supervisor subtask created. TCB=008D20F8.

14.58.33 JOB04681 SUPV NSQ4000I Supervisor started.

14.58.34 JOB04681 XMIT0001 NSQ5000I Transmitter 1 is active.

14.58.34 JOB04681 XMIT0001 NSQ5450I Transmitter 1 is starting.

14.58.34 JOB04681 SUPV NSQ4400I Supervisor operating.

Chapter 4: Using the Probe Nastel XRay Probes for z/OS


14.58.34 JOB04681 XMIT0002 NSQ5400I Transmitter 2 is idle.

14.58.34 JOB04681 XMIT0003 NSQ5400I Transmitter 3 is idle.

14.58.34 JOB04681 MAIN NSQ1400I WMQ z/OS operating.

The following messages are written to the MAIN SYSOUT dataset in the probe:

2005/116 18:58:32.181057 MAIN NSQ1086I DDB at 06EB11A0 created and initialized.

2005/116 18:58:32.183894 MAIN NSQ6201I Logger created. TCB=008D24B0.

2005/116 18:58:32.315479 MAIN NSQ1224I PAB found at 0759c028.

2005/116 18:58:32.315697 MAIN NSQ1226I PTBL found at 072E53B8.

2005/116 18:58:32.315997 MAIN NSQ1231I PTBL entry at 072E53D8 is being reserved

2005/116 18:58:32.316313 MAIN NSQ1232I Initial ddb is at 06EB1260.

2005/116 18:58:32.325727 MAIN NSQ1241I Linkage index 00003100 is being reused

for cp-PC

2005/116 18:58:32.325727 MAIN NSQ1243I Linkage index 00003200 is being reused

for ss-PC

2005/116 18:58:32.328038 MAIN NSQ1251I Command processor created. TCB=008D2318.

2005/116 18:58:32.351051 MAIN NSQ1261I Supervisor created. TCB=008D20F8.

2005/116 18:58:32.755959 MAIN NSQ1400I WMQ z/OS operating.

4.4 Verifying Installation

Once the probe is up and running (NSQTI), tailor the member DRVAP in the JCL library.

//JOBCARD JOB (ACCTG INFO),'NASTEL'

//*--------------------------------------------------------------------

//*

//* NASTEL TRANSACTION MONITOR VALIDATION DRIVER (MQPUT)

//*

//* ++instmq++ - Installation CSQ7 load library created from

//* TSO Receive


//* ++qmgr++ - Queue Manager

//* ++qname++ - Queue Name

//*

//*--------------------------------------------------------------------

//STEP1 EXEC PGM=MQBDRV1

//STEPLIB DD DSN=++instmq++,DISP=SHR



//INPUT DD *

++qmgr++ Queue Manager

++qname++ Queue name

00000512 Minimum message length

00004096 Maximum message length

00000020 # of MQPUTs overall

00000000 # of seconds between each MQPUT, 0 = no timer

00000000 # of MQPUTs before each MQCMIT, 0 = no MQCMITs

/*

Ensure a valid JOB card is available at the beginning of the JCL stream.

The first library in the STEPLIB concatenation should be changed to ++hlq++.LOAD where HLQ has

been determined as mentioned in section 3.3. The second library is the IBM MQ library ++mqser++

.SCSQAUTH. ++qmgr++ in the INPUT DD stream should be changed to the name of the queue manager



that MQBDRV1 will connect to. Note that this queue manager must use the same version of the

SCSQAUTH library as is coded in the second library of the STEPLIB concatenation.

++qname++ in the INPUT DD stream must be replaced by a test queue name. The JOB must have

authority to PUT messages to the queue.

The remaining input parameters should not be changed.

Submit the JOB. Once it has finished, inspect the XMIT0001 SYSOUT file for the NSQTI probe.

Message number NSQ5450I should be seen in this file. This indicates that the transmitter found MQ

contextual data in the dataspace and put the data in the MQ queue defined in the configuration file. If the

message does not appear, verify that the submitted JOB (DRVAP in the JCL library) issued some MQ

calls. The JES message log for this JOB should resemble the following output:

11.51.02 JOB04700 IEF403I DRV1 - STARTED - TIME=11.51.02

11.51.03 JOB04700 +------ CONNECT -----

11.51.04 JOB04700 +------ OPEN -----

11.51.09 JOB04700 +------ CLOSE -----

11.51.09 JOB04700 +------ DISC -----

11.51.09 JOB04700 @Messages PUT = 00000020.

11.51.09 JOB04700 IEF404I DRV1 - ENDED - TIME=11.51.09

If any of the MQ calls fail, the completion and reason codes will be displayed. These must be resolved.

Once fixed, resubmit the JCL. If a PUT count is displayed but the XMIT0001 SYSOUT file does not

contain message NSQ5450I, contact Nastel support.

In order to clear the queue (defined in the configuration file) containing the captured MQ contextual data,

the member DRVAG in HLQ.MLQ.JCL must be configured and run. The DRVAG job will remain

running waiting on the queue even if it is empty. The following message is issued to the joblog. The user

should stop this job using the mvs P command.

MQBDRV2 RUNNING : ISSUE STOP COMMAND TO END TASK


//*--------------------------------------------------------------------

//*

//* NASTEL TRANSACTION MONITOR VALIDATION DRIVER (MQGET)

//*

//* ++instmq++ - Installation CSQ7 load library created from

//* TSO Receive


//* ++qmgr++ - Queue Manager

//* ++qname++ - Queue Name

//*

//*--------------------------------------------------------------------

//STEP1 EXEC PGM=MQBDRV2,TIME=1440

//STEPLIB DD DSN=++instmq++,DISP=SHR



//INPUT DD *

++qmgr++ Queue Manager

++queue++ Queue name

00000001 # in seconds between each MQGET call

00000010 # of MQGET calls between MQCMIT

/*

++hlq++ must be replaced as per section 3.3. The same applies to ++mqser++.



++qmgr++ and ++qname++ must be the same as the values used in the DRVAP job.

Submit the JCL.

The JES message log for the JOB should contain output similar to the following:

2.05.42 JOB04701 IEF403I DRV2 - STARTED - TIME=12.05.42

12.05.43 JOB04701 +------ CONNECT -----

12.05.43 JOB04701 +------ OPEN -----

12.06.08 JOB04701 +------ CLOSE -----

12.06.08 JOB04701 +------ DISC -----

12.06.09 JOB04701 @MQGETs = 00000020.

12.06.09 JOB04701 IEF404I DRV2 - ENDED - TIME=12.06.09

Note that there were 20 messages pulled from the queue. This matches the 20 MQ messages that were

PUT in the prior JOB. The CONN, OPEN, CLOSE and DISC each generate an entry in the dataspace.

These messages can be validated by looking at the MQ ISPF DISPLAY PANELS in TSO to view the

number of messages currently on the NASTEL.APTM.MESSAGE Queue.

The count should be 20 after the DRVAP job is run successfully. It should be reduced to 0 after the

DRVAG job is completed.

Compare this value to the MQ call counts displayed when running the probe command:

F <probe>,DISPLAY COUNTS BATCH

NSQ6435I TOTAL COUNTS

MQCONN : 2

MQDISC : 2

MQOPEN : 2

MQCLOSE : 2

MQGET : 20

MQPUT : 20

MQPUT1 : 0

MQSET : 0

MQINQ : 0

MQBACK : 0

MQCMIT : 0

SKIP : 0

ABEND : 0

If no messages were processed, contact Nastel support. Otherwise, the installation was successful.



4.5 Message Automation

The probe allows the user to control what probe messages are issued on the z/OS console. Any of our

messages can be trapped and processed by any Automation products running on z/OS.

The configuration file supports a “Messages” area section. In this section, you may enter as many

message numbers as desired to either route a message to the console or remove the message from being

written to the console. Use the “number” keyword on each line for each message. The message number

must match a real 4-digit message number in the “Diagnostic” section of this manual.

If you wanted message NSQ5490I to be issued on the console, you would enter this parameter in the

“Messages” area section of the configuration file.

Messages

Number=5490

;

This message would be issued on the MVS console every time a dataspace switch occurs.

NSQ5490I Dataspace is full. Transmitter nnnn switching over to next transmitter.

During the probe startup, the following messages are written to the MVS console by default.

NSQ1050I Nastel z/OS Probe vvvv started

NSQ1226I PTBL found at 1C3C9128.

NSQ1231I PTBL entry at 1C3C9148 is being reserved for id JMS2.

NSQ1232I Initial ddb is at 1C43A118.

NSQ6201I Logger subtask created. TCB=008DFD00.

NSQ1251I Command processor subtask created. TCB=008DFAB0.

NSQ4102I All transmitter subtasks initialized.

NSQ1241I Linkage index 00003400 is being reused for cp-PC.

NSQ1243I Linkage index 00003500 is being reused for ss-PC.

NSQ1400I Nastel z/OS Probe is up and running.

If it is desired to prevent any of these messages from appearing, you can do the following.

Messages

Number=6201,no

Number=1251,no

;

The logger and command processor subtask created messages will not appear on the console when the

probe is started.

All messages are written to the JESMSGLG or a SYSOUT file associated with a subtask.



4.6 Disabling IBM MQ Collection

If it is necessary to stop the interception process without stopping the probe’s started tasks, you may

disable the PUT on the NASTEL.APTM.MESSAGE queue or alias queue (if used). When PUT disabled,

no further messages will be forwarded to the queue. Refer to the section, Probe Configuration File, that

discusses the “PutEnableTime” parameter.

When the NASTEL.APTM.MESSAGE queue is disabled, the probe may retain or discard messages

depending on the setting of the MSGCNTLINHIBITQ option. If this option is set to KEEP, messages are

retained on the active dataspace causing the CurrentDepth of the “Dataspace” to increase. If this option is

set to DISCARD, the messages are not retained on the Dataspaces.

The Display Dataspace command can be used to show Dataspace information.

To disable or enable the PUT on the NASTEL.MESSAGE.QUEUE or alias queue, use any of the MQ

tools of your choice, which allows you to alter the PUT attribute. Make sure you have the proper

authorization. For example, in TSO, you may use the “IBM MQ for z/OS - Main Menu.”

1. List the QLOCAL or QALIAS on the queue manager connected to by the probe.

2. Alter the NASTEL.APTM.MESSAGE or alias queue, whichever is being used.

3. On the Put Enabled column, change the value to “N” and click enter. The queue is now disabled.

4. On the Put Enabled column, change the value to “Y” and click enter. The queue is now enabled.

4.7 QMON (Queue Monitor Subtask)

The QMON subtask is an optional feature that can be used to protect the pageset space configured with

our NASTEL.APTM.MESSAGE queue in the QMGR. If the probe is configured using an alias queue,

the same protection can be applied to the base queue.

The QMON subtask is started when the CurrentDepth value is specified in the configuration file. If it is

not specified, the QMON subtask is not created. When it is initially active, the subtask can be stopped

and restarted dynamically. The configuration settings, CurrentDepth threshold, CurrentDepthMin

threshold and CurrentDepthInt values can be changed dynamically without having to restart the probe.

The Start and Stop QMON subcommands and Change commands can only be used if the QMON subtask

is active.

The QMON’s subtask purpose is to disable the PUT activity on the NASTEL.APTM.MESSAGE queue

when the currentdepth of the queue exceeds the currentdepth threshold running in the QMON subtask.

The MESSAGE queue is checked using the timer value specified on the CurrentDepthInt interval.

When the QMON subtask discovers that the currentdepth of the queue falls below the minimum

monitoring threshold, the NASTEL.APTM.MESSAGE queue is reenabled for PUT activity.

The minimum CurrentDepth threshold controlled by the CurrentDepthMin option can be set to any

number including 0. The only restriction when setting this value in the configuration file or changing it

using the CHANGE command is that the difference between the CurrentDepth and CurrentDepthMin

values must be greater than 1000.

When the MESSAGE queue is PUT disabled, streaming can continue to process all the messages on the

queue bringing the currentdepth to 0. This gives streaming time to catch up and relieves space concerns

in the QMGR. While in this state, the probe’s active dataspace may continue to receive messages. It is

possible during collection that dataspace switching may occur.

The currentdepth of the dataspace can be viewed using the DISPLAY DATASPACE DETAIL command.

When the currentdepth of the MESSAGE queue reaches 0 or falls below the minimum CurrentDepth

threshold, the MESSAGE queue is reset back to PUT enabled automatically by the QMON subtask. This

activity ensures that during high volume collection, the QMGR pageset space is protected.

Use the DISPLAY QMON command to show the state and current values used by the QMON subtask.



4.8 Dataspace Management

Dataspaces are used by the probe as interim storage for all intercepted messages from batch and CICS

user applications running IBM MQ transactions. The messages are picked up from the dataspaces by the

transmitter tasks and are forwarded to the Nastel XRay monitor via the NASTEL.APTM.MESSAGE

queue.

The probe will create n number of dataspaces based on the DspNumber parameter specified in the

Dataspace section in the configuration file. Each dataspace is associated with a transmitter subtask. By

example, if the probe creates 5 dataspaces, it will create 5 transmitter subtasks.

The Dataspace size is based on the DspSize parameter specified in the configuration file. The DspSize

parameter represents the number of 4K blocks in each dataspace. The maximum size of a dataspace is 2

gigabytes, and therefore, the maximum value for dspsiz is 524288.

The Dataspace storage is a contiguous segment of memory that starts at 4K into the dataspace. As each

message is placed on the dataspace, the address is advanced towards the end. The transmitter task

associated with the dataspace wakes periodically based on the xmitInterval specified. It will remove each

message from the dataspace and place them on the NASTEL.APTM.MESSAGE queue. The space

occupied by the message in the dataspace is immediately freed for reuse. The transmitter task will

continue to run until it has removed all messages from its associated dataspace and then enter a wait state

for the xmitInterval before checking for additional messages.

Use the DISPLAY DATASPACE DETAIL command to show information about the transmitter and

dataspace states. See section, Tuning, for some suggestions on tuning the size and number of dataspaces,

and other settings.

4.8.1 Dataspace Switching

When the probe attempts to reserve space in the dataspace and discovers that the message is too big, it

will force a switch to the next dataspace. The Dataspaces are processed in a round-robin type manner.

When the first dataspace is exhausted it will switch to the next dataspace. When the last dataspace is

processed and becomes exhausted, the process starts over using the first dataspace.

How often a dataspace switch occurs is dependent on the size of your dataspaces, the size of the

intercepted messages as limited by MsgSize, and the rate at which messages are intercepted. The

recommendation is to run with very large dataspaces, as this will minimize the dataspace switch activity.

4.8.2 Configuring Dataspace Settings

The probe is designed to collect the intercepted tracking messages for the Nastel XRay monitor as fast as

possible. Copies of intercepted messages are buffered in the dataspaces until they are picked up by the

Transmitter subtasks running under the control of the probe’s address space. The dataspaces act as a

buffer to handle spikes in message interception and possible network delays in message transmission to

the Nastel XRay monitor. Additionally, this provides a means of batching messages for transmission to

the Nastel XRay monitor thereby achieving greater efficiencies in resource utilization. Messages are

never lost unless all dataspaces configured have no available dataspace memory to place new collected

messages. Therefore, it is suggested that you start with an over allocation of dataspace, several large

dataspaces and tune down.

The probe’s dataspace parameters, dataspace size (DspSize) and number of dataspaces (DspNumber), are

used to determine the amount of preallocated memory for message buffering used by the probe address

spaces. The dataspace area should be set to account for the number of messages that you want to retain

on the dataspaces should the transmission of messages to the Nastel XRay monitor get interrupted.

Currentdepth indicates the number of messages being buffered in the dataspace at that point in time. See

section, Tuning, for details on configuring the Database Settings.



4.8.3 Dataspace Size Limits

Refer to your System Programming staff to determine the supported dataspace size limits allowed for

your installation. Your IEFUSI SMF Exit may also control the dataspace size limits.

4.8.4 Auxiliary Storage Usage

Depending on the size of Real memory allocated to your z/OS operating system, paging may or may not

occur to Auxiliary storage when the probe is processing high volume. During low or normal MQ

processing, the QMGR is not likely to page out messages to Auxiliary storage during processing.

In terms of defining what volume activity is high, normal, or low is relative to each site installation.

Nastel recommends that you refer to the following MQ manuals discussing virtual storage and Queue

Manager parameters related to the BUFFPOOL definitions:

MQSeries Planning Guide, GC33-1349

Systems Management Guide, SC34-5374

4.9 Transmitter Subtasks

Each transmitter subtask is associated with one dataspace as described in the “Dataspace Management”

section. There is only one transmitter that is ACTIVE at any one time. The other transmitter subtasks are

IDLE. When in an idle state, the dataspaces are awaiting a dataspace switch. The dataspaces are

processed in a round-robin type manner.

When the next transmitter becomes ACTIVE, the current-ACTIVE dataspace becomes IDLE after

sending all remaining messages to the Nastel XRay monitor. When the last transmitter\dataspace is

processed and becomes exhausted it will become IDLE and the first transmitter\dataspace becomes

ACTIVE.

In a normal environment, running with large dataspaces, dataspace switching will occur but this activity is

minimal. With high volume collection and depending on the dataspace sizes used, it is possible that

dataspace switching can become excessive and multiple Transmitter subtasks are running in an attempt to

empty the associated dataspace.

Use the DISPLAY DATASPACE and DETAIL option in conjunction with the DISPLAY COUNTS

commands to view the activity of the dataspaces.

4.9.1 Tuning

The dspNumber, dspSize, MsgSize, xmitInterval, PutEnableTime, CurrentDepth, CurrentDepthMin, and

CurrentDepthInt values should be looked at closely to determine appropriate values to control the Nastel

XRay environment.

The following examples describe setting the DspSize and DspNumber parameters, with these options:

• Retain 1,000,000 messages if streaming was stopped and the probe continues to intercept

messages.

• Real application message lengths average 50000 bytes.

The dataspace layout: Nastel XRay message context Copy of intercepted msg

Dataspace hdr (4k) TM-MQH (x’5E4’) - 1508 Variable – limited by msgsize

Note that the msgSize parameter defines the requested size of the intercepted copy of the real message

provided from MQPUT, MQPUT1, and MQGET calls. It can be set between 512 and 4096. If you use

Repeated n times in the dataspace,

once per intercepted message



the override value 0, your request is to append the entire length of the message as it represents a copy.

Virtually, you are requesting the intercepted messages to be 1508 + length of the entire message.

The following examples are provided to assist in setting the dataspace values.

Example 1:

1,000,000 msgs X (1508 + 4096) = 5,604,000,000 (5.3G)

You would need to run 3 transmitter tasks, code the following in the dataspace section in the

configuration file.

DspNumber=3

DspSize=456055 //(456055 x 4K pages) = 1,868,000,001 (1.8G) / dataspace

Example 2:

If you want to run 7 transmitter tasks and retain 50000 messages, code the following in the dataspace

section in the configuration file. Assume that you are running with an Msgsize value of 1024 since you

only want to transmit 1k portion of the intercepted message copy.

50000 msgs X (1508 + 1024) = 126,600,000 (126M)

DspNumber=7

DspSize=4416 //(4416 x 4K pages) = 18,087,936 (18M) / dataspace

Nastel recommends inflating the DspSize parameter by 10%.

If the collection remains active and the NASTEL.APTM.MESSAGE queue is not processed, the

currentdepth will increase or each dataspace until all dataspace storage is exhausted. At this point, all

subsequent collection is lost.

The value of xmitInterval determines how long a Transmitter Subtask waits before checking its associated

dataspace for messages to forward on to the Nastel XRay monitor. A longer interval allows for more

messages to accumulate resulting in fewer dispatches of the Transmitter Task and more efficient use of

the processor. It also means that more storage in the dataspace will be in use at any point in time and

there will be an increased delay in sending message to the Nastel XRay monitor. A shorter interval will

reduce the storage utilization in the dataspace, increase the processor utilization, and reduce any delay in

the sending of messages to the Nastel XRay monitor. A balance must be struck avoiding unacceptable

delays in message transmission and achieving an acceptable amount of processor utilization. The amount

of storage available in the dataspaces must be sufficient to hold accumulating messages and also account

for any spike in the message arrival rate.

Using Example #1 above of 1,000,000 messages, and an additional metric of message arrival rate of

4000/second, it would take about 83 seconds to fill one of the three dataspaces or about 250 seconds

(about 4 minutes) to fill all three. An xmitInterval of 15 seconds would allow 60,000 messages to

accumulate (about 18% of the one dataspace or about 6% of all three dataspaces). The Transmitter

Subtask would loop through all 60,000 messages and process any additional messages which accumulated

in the dataspace as it was running before going back into a wait state. It seems reasonable, providing the

delay in delivery to the Nastel XRay Monitor is acceptable and there is sufficient space to deal with a

sudden spike in the message arrival rate and its duration. If the delay is not acceptable, decrease the

xmitInterval. If the delay is acceptable, but the possible spike in the message arrival rate is too high

increase the storage or buy back some storage by decreasing the xmitInterval at the expense of additional

dispatches.

Another consideration is the ability of the Queue Manager which is managing the

NASTEL.APTM.MESSAGE queue to handle the traffic. Any backup in the queue manager will result in

messages staying longer in the dataspaces. If QMon is running, it could delay transmission of messages

due to the settings of PutEnableTime, CurrentDepth, CurrentDepthMin, and CurrentDepthInt. This

would also impact the storage utilization in the dataspaces. When current CurrentDepth is detected, the

Transmitter Subtask will wait for the interval defined in PutEnableTime before checking if the QMon

Subtask has re-enabled the NASTEL.APTM.MESSAGE queue. The QMon Subtask will not check the



NASTEL.APTM.MESSAGE queue for CurrentDepthMin until the CurrentDepthInt has elapsed. Setting

PutEnableTime shorter than CurrentDepthInt simply does not make sense, however, depending on z/OS

dispatching, the delay before resuming transmission by the Transmission Subtask could be nearly the sum

of the two intervals resulting in additional space required to house arriving messages.

As noted, each dataspace has an associated Transmission Subtask. This structure provides for increased

processing power when a spike in message volume occurs or during ‘catch-up’ after a network slowdown.

When a dataspace switch occurs, the ‘switch from dataspace’ Transmission Subtask continues to run until

it empties all remaining messages. At the same time, the ‘switch to dataspace’ Transmission Subtask

begins processing messages from the ‘switch to dataspace’. This structure provides multiprocessing of

messages during high message arrival rates. The CDepth value on the DISPLAY DATAPACE DETAIL

output will show the more than one dataspaces with non-zero values. It is normal to see this after a

switch has occurred, a message rate spike has occurred, or a network delay occured; if it clears rather

quickly, it is not an indication of a problem.

Tuning is not simple and no two enterprises are the same. Therefore it is suggested to over allocate and

then scale back as one gets a feel for the resource and business requirements. With the various tuning

knobs and adjustments, the Nastel XRay Probe should be able to provide the needed data collection with

minimal resource consumption.

4.10 Timers

The following Timers are used in the probe tasks.

Table 4-1. Timers – CICS Interface Transaction

Timer CICS Interface Transaction

Probe Environment not found CICS started and Probe not available

Check every 10 seconds.

INITPARM option Check if probe’s cross memory environment still

exists

PTO (Probe Time Out) Interval to check if a task being monitored has ended

Table 4-2. Timers – Transmitter Subtasks

Timer Transmitter Subtasks

TIConfig Option

ConnectRetry

Interval to retry connecting to the first queue manager

listed in the TIConfig QMgr parameter

TIConfig Option

xmitInterval

Interval to wait before checking the active dataspace

which was empty for new work

TIConfig Option

PutEnableTime

Interval to wait before checking if the queue identified

by the TIConfig Option QueueName has changed

from PutEnable=No to PutEnable=Yes (See section,

QMON (Queue Monitor Subtask)

Table 4-1. Timers – CICS Interface Transaction

Timer QMON Subtask

TIConfig Option

CurrentDepthInt

Interval between checks of the queue depth of the

queue identified by the TIConfig Option QueueName

(See section, QMON (Queue Monitor Subtask)

Nastel XRay Probes for z/OS Chapter 5: Installing the Probe for CICS


Chapter 5: Installing the Probe for CICS

5.1 Installation Files

The installation files for Customer Information Control System (CICS) are the same as those for batch.

5.2 MQ CICS Data Collection

Nastel Technologies no longer rely on MQ CICS Crossing Exit CSQCAPX for MQ data capture. MQ

data capture executed through CICS Resource Manager Interface (RMI).

5.2.1 Activate CICS Resource Manager Interface

By default, CICS Resource Manager Interface actviated at CICS Startup when valid INITPARM

statement specified for Nastel CICS Interface. Refer to the section, System Initialization Parameters

Input Values.

5.3 Modifying CICS Startup JCL

The Nastel load library ++hlq++.APTM60.LOAD created from TSO Receive must be included in the

concatenations of STEPLIB and DFHRPL. It can be included ahead of MQ concatenations. If the library

is missing from either concatenation, the CICS capture will not work.

Sample JCL setup for the CICS region:

//STEPLIB DD

// DD DSN=++HLQ.MLQxx.LOAD++,DISP=SHR

// DD DSN=++mqser++.SCSQANLE,DISP=SHR


//DFHRPL DD

// DD DSN=++HLQ.MLQxx.LOAD++,DISP=SHR

// DD DSN=++mqser++SCSQANLE,DISP=SHR

// DD DSN=++mqser++SCSQCICS,DISP=SHR

// DD DSN=++mqser++SCSQAUTH,DISP=SHR

// DD DSN=++mqser++SCSQLOAD,DISP=SHR

5.4 CICS Definitions

The following definitions are required for the CICS installation:

You may use the CEDA transaction (RDO) or the DFHCSDUP utility to create a NASTEL group to

contain the following CICS definitions. You may name the group to your own naming standards.

DEFINE TRANS(NSTM) PROGRAM(NSQTRANC) TASKDATAKey(CICS)

TASKDATALoc(ANY) GROUP(nastel_group)

DEFINE TRANS(NSTS) PROGRAM(NSQTASK) *TASKDATAKEY(CICS)*

TASKDATALoc(ANY) GROUP(nastel_group)

DEFINE PROG(NSQTRANC) DATALOCATION(ANY) EXECKEY(CICS)

GROUP(nastel_group) CONCURRENCY(THREADSAFE)

DEFINE PROG(NSQINIT) DATALOCATION(ANY) *EXECKEY(CICS)* GROUP(nastel_group)

CONCURRENCY(THREADSAFE)

Chapter 5: Installing the Probe for CICS Nastel XRay Probes for z/OS


DEFINE PROG(NSQTASK) DATALOCATION(ANY) *EXECKEY(CICS)*


DEFINE PROG(NSQTRUES) DATALOCATION(ANY) *EXECKEY(CICS)*


DEFINE PROG(NSQGLUEX) DATALOCATION(ANY) *EXECKEY(CICS)*


DEFINE PROG(NSQDBRMI) DATALOCATION(ANY) *EXECKEY(CICS)*


DEFINE MAPSET(NSTMMAP) GROUP(nastel_group)

ADD GROUP(nastel_group) LIST(cics_list)

ADD GROUP(mq_cics_adapter_group) LIST(cics_list)

Note: CSQCAT1 is the group name used for the mq_cics_adapter_group in the MQ CICS Adapter definitions.

Install the group into your CICS LIST. You may use the sample member NASTDEFS in MLQxx.SAMP

provided to install the Nastel CICS definitions.

5.5 CICS Program List Tables

The Nastel_XRay_Probe for CICS requires a Program List Table Entry for CICS program initialization

and second table for shutdown. These are defined by the PLTPI and PLTSD entries respectively in the

CICS configuration. If the tables already exist, the Nastel_XRay_Probe entries must be merged into the

existing tables. Take note of the order relative to the IBM MQ Entry and the DFHDELIM Entry in the

samples and maintain the relative positioning in the merged tables.

When installing the PLT on CICS Transaction Server Version 5.5 and above, the PLT Source must be

placed in a library which is part of the PARMLIB Concatenation at z/OS IPL time or in a library which is

pointed to by the DDName DFHTABLE defined in the CICS Startup JCL.

When installing the PLT on CICS Transaction Server Version 5.4 and below, the PLT table must be

reassembled and the resulting load module must be replaced in the corresponding dataset in the DFHRPL

concatenation.

5.5.1 PLTPI Table

The CICS installation of the Nastel_XRay_Probe requires an entry in the PLTPI table for module

NSQINIT. A PLTPI table should already exist because IBM MQ has its own PLTPI requirement. Place

the Nastel definition for NSQINIT after the IBM MQ definition.

Below is a sample DFHPLT source module that uses suffix TM.

DFHPLT TYPE=INITIAL,SUFFIX=TM

DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM

DFHPLT TYPE=ENTRY,PROGRAM=DFHMQCOD

DFHPLT TYPE=ENTRY,PROGRAM=NSQINIT

DFHPLT TYPE=FINAL END

A sample PLTPI statement showing PLTPI=TM is shown in sample member INITPARM in

MLQxx.SAMP. This statement is to be placed in the CICS SIP member DFH$SIPx. Additionally,

member DFHPLTTM in MLQxx.SAMP contains the above sample.

5.5.2 PLTSD Table

The CICS installation of the Nastel_XRay_Probe requires an entry in the PLTSD Table for module

NSQTERM. The entry must be before the “DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM” entry.



Below is a sample DFHPLT source module that uses suffix SD.

DFHPLT TYPE=INITIAL,SUFFIX=SD

DFHPLT TYPE=ENTRY,PROGRAM=NSQTERM

DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM

DFHPLT TYPE=FINAL END

A sample PLTSD statement showing PLTSD=SD is shown in sample member INITPARM in

MLQxx.SAMP. This statement is to be placed in the CICS SIP member DFH$SIPx. Additionally,

member DFHPLTSD in MLQxx.SAMP contains the above sample.

5.6 System Initialization Parameters Input Values

The following INITPARM statement is required. It may be added to the SIT or SIP input parameter file if

it is desired to override any of the default values. If the INITPARM statement is not used, the CICS

region will start but the Nastel CICS interface will not initialize. The INITPARM statement requires only

one parameter, which is the QMGR name. All other parameters are optional.

INITPARM=(NSQINIT='PID=++prodID++')

or

INITPARM=(NSQINIT='QM=++qmgr++')

The options on the INITPARM statement are keyword-value pairs.

PID=xxxx - This value is used to match the ProdID= value specified in the API

Interceptor Configuration File. (Refer to the section, API Interceptor Configuration

File, for a description of ProdID.) If your CICS region is not connected to Websphere

QMGR, then use this parameter to enable Nastel CICS code to identify the API

Interceptor address space to use. If PID= is not specified, then QM= parameter is

required. If PID=xxxx is specified , then QM=++qmgr++ is not required. If both PID

and QM are specified, Nastel CICS code matches on PID first, then QM.

QM=++qmgr++ - QMGR name that must match the QMGR name that is used with the CICS MQ

Adapter.

MP=xxx – Override value that should be used in the event it is necessary to override

the message prefix for all of the Nastel messages that are issued on the system

console and the NASTEL sysout file. The default value is NSQ. This is an optional

parameter.

PTO=nn – Nastel CICS subtask dispatch interval in seconds. This timer is used to

check the state of the cross memory interface for the probe. The default value is 10

seconds. This is an optional parameter.

TTO – Nastel timer used to monitor the CICS crossing exit trnq entry table. MQ

transactions that abend or terminate due to a forcepurge (or kill) are likely to never

receive an MQCLOSE call. This timer dispatches a routine that will remove entries from

our trnq table.

CA=[YES|NO] – Option that allows a user to indicate whether MQ interception is allowed

or not thru CSQCAPX. The default is NO. This is an optional parameter.

TR=++tran++ - Option that allows the Nastel interface to run under a different

transaction name. The transaction must be setup in the CSD mapped to program name

NSQTASK. The default transaction name is NSTS.

PR=[0-255] – Option that allows the Nastel transaction to run at a certain priority

level. If it is not specified, the CICS region will use the default priority setting

for the system.

XEI=[Y|N] – Option that enables/disables XEIIN/XEIOUT exit. Default is Y. If set to

N, no EXEC CICS API commands are intercepted.

XRM=[Y|N] – Option that enables/disables XRMIIN/XRMIOUT exit. Default is N. If set

to Y, EXEC SQL, TCP, and MQ API commands are eligible for interception.

SQL=[Y|N] – Option that enables/disables EXEC SQL command collection. Default is N.

If set to Y, EXEC SQL commands are intercepted.



SQLT=[Y|N] – Option that enables/disables SQL Text collection. Default is N. If set

to Y, SQL text collection performed on each EXEC SQL command using DB2’s

Instrumentation Facility Interface.

SPI=[Y|N] – Option that enables/disables use of ABEND recovery routine. Default is Y.

If set to N, no ABEND recovery is established. Use of ABEND recovery is CPU time

consuming. Of course, our goal is not to encounter ABENDs.

TCP=[Y|N] – Option that enables/disables TCP data collection. Default is N. If set

to Y, TCP API commands are intercepted.

MQI=[Y|N] – Option that enables/disables MQ data collection. Default is N. If set to

Y, MQ API commands are intercepted.

Table 5-1. INITPARM Parameters

Parameter Minimum Maximum Length Required Default

PID N/A N/A 4 Y N/A

QM N/A N/A 4 N N/A

QMGR N/A N/A 4 Y N/A

MP N/A N/A 3 N NSQ

PTO 10 60 N/A N 10

TTO 5 86400 N/A N 60

CA N/A N/A 3 N YES

TR N/A N/A 4 N N/A

PR 0 255 N/A N N/A

XEI N/A N/A 1 N Y

XRM N/A N/A 1 N Y

SPI N/A N/A 1 N Y

5.7 Starting CICS Region

The CICS region is started in the usual fashion either with a /S (START) command or by a JOB

scheduling or automation product.

NOTE:

Even if the Nastel CICS feature encounters an error, the CICS region should come up. The issues will have to be resolved to verify MQ interception occurs properly.

5.8 Verifying Installation

When the CICS adapter is installed along with the Nastel environment, the interface will become active

upon startup.

During CICS initialization it will call module NSQINIT during the PLTPI phase and issue the following

message to the JESMSGLG.

NSQ7000I Nastel NSQINIT TM PLTPI program starting.

If this message is not displayed before the following message:

+DFHSI1517 CICS Control is being given to CICS

Nastel’s PLTPI program did not get control. Verify that the DFHPLTPI module DFHPLTxx is in the

DFHRPL concatenation in one of the datasets and that the source for DFHPLTxx has the required line for

NSQINIT.

When NSQINIT has finished executing, it issues the following message to the JESMSGLG:



NSQ7099I Nastel NSQINIT TM PLTPI program ended.

This indicates that the NASTEL PLTPI program ran successfully.

Any errors encountered by NSQINIT will cause a diagnostic message to be displayed in the JESMSGLG

of the CICS region. These errors must be resolved before the MQ capture can occur. Refer to the

Diagnostic Messages section in this manual.

NSQINIT sets up the Nastel local environment in the CICS region. It starts a transaction by the name of

NSTS in the CICS region, which manages communications with the probe’s cross memory environment.

It will create the ALETs on the PASN-AL access list whenever the probe is started. It will also process

any command requests used with the NSTM transaction. Additionally, it will create the sysout file

NASTEL that is used for additional messages. All messages are issued to the console and the NASTEL

sysout file and are documented in the Diagnostic Messages section of this manual.

Sample Nastel sysout file from CICS:

20100825 10:04:10 NSQ7100I NSQTASK subtask starting.

20100825 10:04:10 NSQ7139I TR=NSTS

20100825 10:04:10 NSQ7139I CA=Y

20100825 10:04:10 NSQ7139I PTO=10

20100825 10:04:10 NSQ7139I TTO=00005

20100825 10:04:10 NSQ7139I XEI=Y

20100825 10:04:10 NSQ7139I XRM=Y

20100825 10:04:10 NSQ7139I SPI=N

20100825 10:04:10 NSQ7139I CPX=NONE

20100825 10:04:10 NSQ7151I NSQTASK local environment created. CGA=1918F4A8.

20100825 10:04:10 NSQ7137I NSQTASK probe using qmgr CSQ7 is not running.

20100825 10:04:10 NSQ7162I NSQTASK collection interface is enabled.

20100825 10:04:10 NSQ7152I NSQTASK cross memory environment is found. STCK=C67B77850C877012.

20100825 10:04:10 NSQ7157I NSQTASK CICSTS41 is using qmgr CSQ7.

20100825 10:04:10 NSQ7161I NSQTASK probe is running.

When the above messages are issued in the NASTEL sysout file, the probe interface is active and ready

for MQI message interception from any CICS transaction using IBM MQ.

Logon to the CICS region where the NASTEL environment is installed and run transaction NSTM with

no parameters. A series of MQI calls are made in the CICS region. A message is written to the console

for each MQI call that is made.

In CICS, clear screen and type NSTM STATS. You will see a display showing counts of MQI calls

made.

Sample NSTM STATS screen shot:

NSTM - COUNTERS BY MQ CALL

TOTAL OPEN CLOSE GET PUT PUT1

23 7 6 2 2 2

INQUIRE ROLLBACK COMMIT SET

2 2

On the system console or in SDSF, run the command f <probe>,DISPLAY COUNTS CICS. You will be

shown a display of the CICS MQI calls that were received by the probe.

F <probe>,DISPLAY COUNTS CICS

NSQ6435I TOTAL CICS COUNTS

MQOPEN : 7



MQCLOSE: 6

MQGET : 2

MQPUT : 2

MQPUT1 : 2

MQSET : 2

MQINQ : 2

MQBACK : 0

MQCMIT : 0

SKIP : 0

ABEND : 0

NOTE: Nastel supplies NASTEL.APTM.TEST.QUEUE for testing and verification purposes.

After the NSTM transaction is run with no parameters, you may verify the total count of messages placed

on the NASTEL.APTM.TEST.QUEUE queue by using the IBM MQ ISPF display panels or by any other

tools available. Normally, the current queue depth should show 0. The transaction run will not leave any

messages on the TEST queue.

5.9 CICSPLEX and Failover

If your site installation supports Failover scenarios in a CICSPLEX environment, the Nastel components

fully support this environment.

In order to implement, you must install the probe tasks on the OS systems where failover CICS regions

will run, in advance, and ensure the Nastel tasks are connected to those QMGRs that will be used.

When CICS failover actions occur, the CICS regions will start in the same manner as any other region

using the CICS MQ Adapter. Both INITPARM statements for the MQ adapter and the NASTEL

definitions require that the same QMGR be used. After the CICS region initializes on your failover

system, the Nastel interface transaction will start and enable collection to the probe configured using the

same QMGR as that of the MQ adapter. Your CICS region can now run any MQ application transaction

on this failover system.

5.10 EXEC CICS, EXEC SQL, and CALL EZASOKET

Command Feature

This feature utilizes two CICS exit interface points: Global User Exit (GLUE) and Task Related User Exit

(TRUE). The primary difference between Global and Task Related exits is the event that causes them to

be executed. Global exit programs are executed when an event occurs within CICS (for example, when

an abend occurs), and they run as part of CICS; Task Related exit programs are executed when a task

requests it, and run as part of the task.

Nastel provides three CICS exits:

1. NSQGLUEX - CICS Global User Exit Routine

This routine is setup and enabled by NSQINIT which runs during CICS PLPTI processing. This

GLUE is called by CICS for the following events:

• XEIIN exit point - before each EXEC SQL API and CALL EZASOKET command

• XEIOUT exit point - after each EXEC SQL API and CALL EZASOKET command

2. NSQTRUES - CICS Task Related User Routine


TRUE is called by CICS for the following events:

• When a CICS Transaction starts



o Performs Transaction Filtering

o Allocates working storage block for use by NSQGLUEX

• When a CICS Transaction ends

o Releases working storage used by NSQGLUEX

• When CICS is shutting down

o Performs Nastel housecleaning prior to shutdown

3. NSQDBRMI - CICS Global User Exit Routine


GLUE is called by CICS for the following events:

• XRMIN exit point - before each EXEC SQL API and CALL ZZASOKET command

• XRMIOUT exit point - after each EXEC SQL API and CALL ZZASOKET command

5.10.1 Setup of NSQGLUEX (GLUE), NSQDBRMI (GLUE), and

NSQTRUES (TRUE)

Refer to the section, CICS Definitions. You should see the following definitions for NSQGLUEX and

NSQTRUES in NASTDEFS member of your SAMP library:

DEFINE PROG(NSQTRUES) DATALOCATION(ANY) EXECKEY(CICS)

CONCURRENCY(THREADSAFE) GROUP(NASTELTM)

*

DEFINE PROG(NSQGLUEX) DATALOCATION(ANY) EXECKEY(CICS)


*

DEFINE PROG(NSQDBRMI) DATALOCATION(ANY) EXECKEY(CICS)


Refer to the section, PLTPI Module. Insure Nastel definition for NSQINIT is part of the PLTPI module

used during CICS Startup. NSQINIT module sets up and enables NSQGLUEX, NSQDBRMI, and

NSQTRUES.

5.10.2 EXEC CICS Command Collection

By default, EXEC CICS command collection begins when both NSQTI (NTI00001) and CICS startup.

EXEC CICS Syncpoints are the only commands intercepted unless you specify CICSGRP_INC

parameter to include additional EXEC CICS groups for intercept.

5.10.3 CICS Transaction Filters

Transaction filtering involves the following two parameters in TICONFIG:

1. TRANS_EXC=

This parameter identifies those specific CICS transactions you wish to exclude from intercept,

separated by comma.

For example: TRANS_EXC=C,XY

Transactions beginning with C will not be intercepted.

Transactions beginning with XY will not be intercepted.

By default, no CICS transactions are excluded from intercept.

2. TRANS_INC=



This parameter identifies those specific CICS transactions you wish to intercept.

For example: TRANS_INC=AAAA,B,NS

Transaction AAAA will be intercepted.

Transactions beginning with B will be intercepted.

Transactions beginning with NS will be intercepted.

By default, all CICS transactions are intercepted.

5.10.4 EXEC CICS Command Filters

EXEC CICS Command Filtering involves the following four parameters in TICONFIG:

1. CICSGRP_EXC=

This parameter identifies what groups of EXEC CICS commands to exclude. EXEC CICS command

groups are identified by the first byte of EIBFN.

For example: FILE group (06) would incorporate the following File commands:

0602 READ

0604 WRITE

0606 REWRITE

0608 DELETE

060A UNLOCK

060C STARTBR

060E READNEXT

0610 READPREV

0612 ENDBR

0614 RESETBR

So, CICSGRP_EXC=FILE would exclude all commands with an EIBFN code of 06.

2. CICSGRP_INC=

This parameter identifies what groups of EXEC CICS commands to include. EXEC CICS command

groups are identified by the first byte of EIBFN.

For example: STORAGE group (0C) would incorporate the following Storage commands:

0C02 GETMAIN

0C04 FREEMAIN

So, CICSGRP_INC=STORAGE would include only commands with an EIBFN code of 0C.

3. CICSCMD_EXC=

This parameter identifies what specific EXEC CICS commands to exclude. EXEC CICS command is

identified by the second byte of EIBFN.

For example: EXEC CICS RETURN equates to 0E08.

So, CICSCMD_EXC=RETURN would exclude only EXEC CICS RETURN commands with an

EIBFN code of 0E08.

4. CICSCMD_INC=

This parameter identifies what specific EXEC CICS commands to include. EXEC CICS command

identified by the second byte of EIBFN.



For example: EXEC CICS GETMAIN and EXEC CICS ASKTIME equates to 0C02 and 1002

respectively.

So, CICSCMD_INC=GETMAIN, ASKTIME would include only EXEC CICS GETMAIN (0C02)

and EXEC CICS ASKTIME (1002).

Refer to the section, EXEC CICS Groups and Commands.

5.10.5 DB2 Plan Filters

DB2 plan name filtering involves the following two parameters in TICONFIG:

1. PLAN_EXC=

This parameter identifies what plan names to exclude. The default is NONE which means do not exclude

any plan names from intercept. It is not necessary to specify this parameter in the Filters section of

TICONFIG if you do not wish to exclude any DB2 plan names.

2. PLAN_INC=

This parameter identifies what plan names to include. The default is ALL which means all DB2 plan

names are intercepted. It is not necessary to specify this parameter in the Filters section of TICONFIG if

you do not wish to include all DB2 plan names.

5.10.6 DB2 SQL Command Filters

DB2 SQL Command Filtering involves the following parameter in TICONFIG:

SQLGRP_EXC=

This parameter identifies the EXEC SQL group commands to exclude. Default is NONE which means do

not exclude any EXEC SQL group commands from intercept. It is not necessary to specify this parameter

in the Filters section of TICONFIG if you do not wish to exclude any EXEC SQL group commands.

5.10.7 TCP Command Filters

TCP Command Filtering involves the following parameter in TICONFIG:

TCPCMD_EXC=

This parameter identifies what TCP commands to exclude. Refer to the section, IP CICS Sockets API

Commands. The default is NONE which means do not exclude any TCP command from intercept. It is

not necessary to specify this parameter in the Filters section of TICONFIG if you do not wish to exclude

any TCP command.

5.11 NSTM Transaction Commands

The NSTM transaction is the Nastel transaction provided for CICS support.

NSTM <noparm>

When no parameters are specified, several MQI calls are invoked, which will drive the CICS adapter

MQ crossing exit to intercept each call.

+------ OPEN -----

+------ INQ -----

+------ CLOSE -----

+------ PUT1 -----

+------ OPEN -----

+------ SET -----

@MQSET error: cc=0002 rsn=2067. <this mqi error is intentional>



+------ PUT ----

+------ CLOSE -----

+------ OPEN -----

+------ GET -----

+------ CLOSE -----

When NSTM transaction specified with 24-digit parameter, then you are doing volume testing.

NSTM xxxxxxyyyyyyzzzzzzcccccc

xxxxxx - Loop count

yyyyyy - # of MQPUTs performed for each loop

zzzzzz - time delay between loops in seconds

cccccc - # of requests before commit

For example: Loop count of 20, 500 MQPUTs for each loop, without time delay NSTM

000020000500000000000001 would yield approximately 10,000 messages

Each loop involves the following 12 MQ API calls in addition to MQPUTs:

MQOPEN

MQINQ

MQCLOSE

MQPUT1

MQPUT1

MQPUT1

MQOPEN

MQSET

MQPUTs = yyyyyy

MQCLOSE

MQOPEN

MQGET

MQCLOSE

NSTM STATS

A CICS display is issued showing the mqi call counts and total count on the number of messages

intercepted by the CICS mq-crossing exit.


TOTAL OPEN CLOSE GET PUT PUT1

11 3 3 1 1 1


1 1

NSTM EXEC

Produces messages such as the following which provide counters of EXEC CICS API by group

commands. Refer to section, EXEC CICS Groups and Commands, for a list of EXEC CICS API

Group commands.

NSTM - COUNTERS BY EXEC CICS CALL

TOTAL ===>00000042

ENVIRONME=00000011 TERMINAL =00000002 STORAGE =00000014 PROGRAM =0000007

SYNCPOINT=00000006 DIAGNOSTI=00000001

Message "ZERO EXEC CICS API COLLECTION" is an indicator that no EXEC CICS API

commands collected at this point. If you are expectinig counts, review your TIICONFIG parms read

by z/OS Probe (NSQTI). Take notice of CICSGRP_EXC= and CICSGRP_INC= parms. If neither

parameter specified, then their defaults are in effect. Refer to the section, EXEC CICS Command

Filters. Another possibility of no counts is XEI=N specified on INITPARM statement for NSQINIT=

parameters. Refer to the section, System Initialization Parameters Input Values.



NSTM SQL

Produces messages such as the following which provide counters of EXEC SQL API by group commands.

Refer to section, EXEC SQL API, for a list of EXEC SQL API Group commands.

NSTM - COUNTERS BY EXEC SQL CALL

TOTAL ===>00000037

OPEN =00000002 FETCH =00000017 CLOSE =00000002 UPDATE =00000001

DELETE =00000001 SELECT =00000013 INSERT =00000001

Message "ZERO EXEC SQL API COLLECTION" is an indicator that no EXEC SQL API commands

collected at this point. If you are expectinig counts, review your TIICONFIG parms read by z/OS

Probe (NSQTI). Take notice of SQLGRP_EXC= parm. If not specified, then the default of NONE is

in effect which means do not exclude any EXEC SQL API. Refer to the section, EXEC SQL

Command Filters. Another possibility of no counts is XRM=N specified on INITPARM statement for

NSQINIT= parameters. Refer to the section, System Initialization Parameters Input Values.

NSTM TCP

Produces messages such as the following which provide counters of TCP API by group commands. Refer

to section, TCP API Group Commands.

NSTM - COUNTERS BY TCP CALL

TOTAL ===>00000249

ACCEPT =00000002 BIND =00000001 CLOSE =00000002 GET =00000005

LISTEN =00000001 RECV =00000109 SELECT =00000015 SOCKET =00000001

WRITE =00000108 GIVESOCKE=00000002 TAKESOCKE=00000002 INITAPI =00000001

Message "ZERO TCP API COLLECTION" is an indicator that no TCP API commands collected at

this point. If you are expectinig counts, review your TIICONFIG parms read by z/OS Probe

(NSQTI). Take notice of TCPCMD_EXC= parm. If not specified, then the default of NONE is in

effect which means do not exclude any TCP API. Refer to the section, TCP Command Filters.

Another possibility of no counts is XRM=N specified on INITPARM statement for NSQINIT=

parameters. Refer to the section, System Initialization Parameters Input Values.

NSTM RESET

The counts displayed from NSTM STATS are reset to 0.

NSQ7158I NSQTRANC MQ counts reset.

If the NSTM STATS command is issued, the following display is issued. There are no counts shown.


TOTAL OPEN CLOSE GET PUT .............. PUT1


NSTM STATUS

Messages are displayed showing the state of each Nastel API collection interface.

For example:

CICSTS32 connected to active Probe ID XYZ6.

NSQ7170I CICS API collection enabled.

NSQ7170I RMI API collection enabled.

NSQ7170I SQL collection enabled.

NSQ7170I SQL text collection enabled.



NSQ7170I TCP collection enabled.

NSQ7170I SPIE disabled.

NSQ7170I NSTS transaction active.

Messages in the above example show the following states:

CICS jobname CICSTS32 is connected to NSQTI with Probe ID XYZ6.

XEIIN/XEIOUT exits enabled for EXEC CICS API collection.

XRMIN/XRMIOUT exits enabled for EXEC SQL API collection.

SQL API command collection enabled.

SQL text collection enabled.

TCP API command collection enabled.

MQ API collection enabled.

Nastel's ESPIE for abend recovery disabled.

Nastel's NSTS transaction that monitors NSQTI's XMEM environment is active.

NSTM STATUS [TRNQ]

If MQ transactions are not running, message NSQ7159I is issued on screen:

NSQ7159I NSQTRANC No monitored transactions

If MQ transactions are running, message NSQ7188I is issued on screen:

NSQ7188I NSQTRANC Monitored transactions on QMGR <qmgr>:<count>

Where:

Qmgr = qmgr used by the CICS region

Count = the number of active transactions currently in use by the CICS MQ Crossing exit.

The TRNQ option identifies the number of live MQ transactions actually monitored by the CICS MQ

Crossing exit

5.11.1 Stopping the CICS/MQ Capture

The transaction, NSTM, can be used to stop and start the capture of MQ contextual data.

To stop the capture, enter the following command:

NSTM STOP MQ

The response should be:

7165I MQ API exit stopped.

replaced by

mm/dd/yyyy hh:mm:ss CICS jobname RESET initiated from TERMID=#### TRANID=NSTM

USERID=CICS UserID and is accepted.

The CICS MQ interface will not forward any MQ messages received by the CICS MQ crossing exit.

To start the capture, enter the following command:

NSTM START MQ


7164I MQ API exit started.

DFHMQ0386 I CICS Jobname 744

mm/dd/yyyy hh:mm:ss CICSTS32 RESET initiated from TERMID=####



TRANID=NSTM USERID=CICS UserID and is accepted.

CICS MQ interface is active. It will forward MQ messages received by CICS MQ crossing exit to probe

dataspaces.

5.11.2 Stopping the CICS/SQL Capture

The transaction, NSTM, can be used to stop and start the capture of CICS/SQL contextual data.


NSTM STOP SQL


NSQ7170I SQL collection disabled.

The following message is written to the console:

NSQ7170I SQL collection disabled by User xxxxxxxx on yyyyyyyy

where: xxxxxxxx = CICS UserID

yyyyyyyy = CICS jobname

The Nastel's NSQDBRMI exit will not intercept any SQL API calls received by the CICS's RMI exit.


NSTM START SQL


NSQ7170I SQL collection enabled.

To stop the SQL text capture, enter the following command:

NSTM STOP SQLT


NSQ7170I SQL text collection disabled.


NSQ7170I SQL text collection disabled by User xxxxxxxx on yyyyyyyy



The Nastel's NSQDBRMI exit will not collect the SQL command text for any SQL API calls received by

the CICS's RMI exit.

To start the SQL text capture, enter the following command:

NSTM START SQLT


NSQ7170I SQL text collection enabled.

5.11.3 Stopping the IP CICS Sockets (TCP) Capture

The transaction, NSTM, can be used to stop and start the capture of IP CICS Sockets (TCP) contextual

data.


NSTM STOP TCP




NSQ7170I TCP collection disabled.


NSQ7170I TCP collection disabled by User xxxxxxxx on yyyyyyyy



The Nastel's NSQDBRMI exit will not intercept any IP CICS Sockets extended API calls received by the

CICS's RMI exit.


NSTM START TCP


NSQ7170I TCP collection enabled.

5.12 Stopping Nastel Interface Transaction NSTS

The Nastel CICS interface transaction NSTS can be stopped by either of the following:

• “NSTM STOP TM” command will stop the NSTS interface transaction.

• Use the CEMT SET transaction to Forcepurge the NSTS transaction.

When the interface transaction is terminated, MQ collection is disabled. The transaction must be restarted

to reenable collection.

Any long running CICS MQ transactions that are running will continue to run normally and communicate

with their own message queues. There will be no further message interception.

5.13 Restarting Nastel Interface Transaction NSTS

The Nastel CICS interface transaction NSTS can be restarted without having to restart your CICS region.

The command to dynamically restart the Nastel interface transaction is as follows:

• NSTM START TM QM=qqqq [initparm parameters]

Where:

qqqq – queue manager name

All initparm parameters are supported. Refer to INITPARM parameters section in this manual.

The QM parameter is the only required parameter. When entering any of the optional keywords,

these must be separated with commas.

For example, NSTM START TM QM=CSQ6,PR=10

Transaction NSTS started running under priority level 10 within the CICS region. The interface

will communicate with the probe using queue manager CSQ6. There is no active MQ connection

handle to the queue manager.

When the START TM command is issued, the Nastel PLTPI initialization program NSQINIT is run

attempting to start the interface transaction. Nastel diagnostic messages are written to the log file using

ddname NASTEL and the MVS console.

NOTE:

If the NSTM transaction is restarted while long running MQ transactions are still running, these transactions will continue to run normally but there will be NO MQ collection.



5.14 Deactivating CICS Interface

To deactivate the CICS interface, run transaction NSTM STOP MQ and leave the probe running. This

will disable CICS MQ collection for that region.

5.14.1 Uninstalling CICS MQ Monitoring

To permanently remove the CICS interface:

1. Stop the probe task for each CICS region that will be uninstalled.

2. Remove the Nastel library from the CICS JCL.

3. Remove all Nastel definitions from your CSD environment.

4. Restart the CICS region.

Nastel XRay Probes for z/OS Chapter 6: Commands


Chapter 6: Commands

The probe supports the following commands which are issued on the system console or through TSO

using SDSF:

F <probe>,command <parameters>

6.1 START

START [COLLECT | COLL | QMON | SEND]

The Start command will turn on the collection flag in csa or the send flag used in the transmitter subtasks.

Where:

COLLECT | COLL – Enable collection from a stop state. When collection is active, messages are

received into the dataspace.

QMON – Restart the QMON subtask if it was stopped. The QMON subtask must have been

initially activated during probe startup.

SEND – Enable the send state in the transmitter subtasks. When the send state is active, messages

are forwarded to the queue.

6.2 STOP

STOP [COLLECT | COLL | QMON | SEND]

The Stop command will turn off the collection flag in csa or the send flag used in the transmitter subtasks.

Where:

COLLECT | COLL – Disable collection. No intercepted messages from the batch adapter or the

CICS mq-crossing exit are received.

QMON – Stop the QMON subtask if it is running. The QMON subtask must have been initially

activated during probe startup.

SEND – Disable the send state in the transmitter subtasks. When the send state is inactive,

messages are received in the dataspace but are not forwarded to queue. The current depth in the

active dataspace will increase until the send state becomes active.

6.3 DISPLAY

6.3.1 DISPLAY DATASPACE

D | DISPLAY [DATASPACE | DSPACE] [DETAIL]

Basic information about the active dataspace is displayed.

Where:

TRANSMITTER tttt IS USING DATASPACE dddd

tttt – transmitter number associated with the dataspace name

dddd – The Nastel dataspace name. The first six characters are always NSQDSPnn. nn is a two

character suffix that matches the transmitter number.

MESSAGES RECEIVED – The number of messages received in the active dataspace

MESSAGES SENT – The number of messages placed on the Message queue

Chapter 6: Commands Nastel XRay Probes for z/OS


CURRENT DEPTH – The current depth value of the “Dataspace” should the environment

experience a problem and the probe can continue collection.

When a dataspace switch occurs, additional messages are issued showing the running total of all

messages written to the dataspaces along with the current messages.

When DETAIL is used, the status of all dataspaces is shown as follows.

DATASPACE XSTATE DSTATE CDEPTH

dddd xxxx ssss cccc

Where:

dddd – The Nastel dataspace name.

xxxx – The XSTATE shows the transmitter state that can be ACTIVE or IDLE.

ssss – The DSTATE shows the dataspace state that can be EMPTY, FULL, or NOT FULL.

cccc – The CDEPTH is the current depth of the “DATASPACE”.

6.3.2 DISPLAY COUNTS

D | DISPLAY COUNTS [BATCH | CICS | ALL] The counts are displayed from Batch, CICS, or totals

for all counts processed.

Where: -

COUNTS

BATCH – show counts for messages received from the batch adapter

CICS – show counts for messages received from the CICS mq crossing exit

show counts for EXEC CICS API commands intercepted

show counts for EXEC SQL API commands intercepted

ALL – show total counts for all Batch and CICS activity.

If no parameter is specified the default is ALL.

6.3.3 DISPLAY QMON

D | DISPLAY QMON

The run state of the QMON subtask and values for the QMON options are shown.

Where:

STATE – [Active | Inactive]

CURRENTDEPTH – Current setting of the CurrentDepth threshold value.

CURRENTDEPTHMIN – Current setting of the CurrentDepthMin threshold value.

CURRENTDEPTHINTERVAL – Current timer interval of how often threshold is checked against

real current depth of the NASTEL.APTM.MESSAGE queue.

6.4 RESET

6.4.1 RESET DATASPACE

RES | RESET [DATASPACE | DSPACE]

The counts maintained for the dataspaces are reset to 0.

Nastel XRay Probes for z/OS Chapter 6: Commands


Where:

DATASPACE | DSPACE – The send and receive counts of the messages passed through the

dataspaces are set to 0.

6.4.2 RESET COUNTS

RES | RESET COUNTS

The counts from Batch, CICS, or totals for all counts are reset to 0.

Where:

COUNTS

BATCH – reset the batch adapter counts to 0.

CICS – reset the CICS adaptercounts to 0.

ALL – reset all Batch and CICS counts to 0.

If no parameter is specified the default is ALL.

6.5 STATUS

RES | RESET STATUS

A message is issued showing the collection state of the probe.

If the probe is disabled, a second message is issued identifying the reason. The most common reasons

are:

NAME/TOKEN PAIR IS NOT FOUND

STOP COLLECT COMMAND WAS ISSUED

QMGR IS NOT RUNNING

STOP SEND COMMAND WAS ISSUED

6.6 CHANGE

The change command can be used to change the options used for the QMON subtask.

C | CH | CHANGE [CDEPTH | CDEPTHINT]

Where:

• CDEPTH changes the CurrentDepth threshold startup value

• CEPTHINT changes the CurrentDepthInt (timer) startup value

Change the options used with the QMON subtask without restarting the probe. The values that can be

applied are the same values as the CURRENTDEPTH and CURRENTDEPTHINT values used in the

configuration file.

6.7 UPDATE

This subcommand is used to update probe parameters dynamically, without restarting the probe. Update

support is valid only for MSG2QUEUE parameter.

U | UPDATE | MSG2QUEUE | DSPC - Dataspace Method

MQPUT - MQOPEN/MQPUT method (currently disabled)

MQPUT1 - MQPUT1 method (currently disabled)

Chapter 6: Commands Nastel XRay Probes for z/OS



Nastel XRay Probes for z/OS Chapter 7: Utilities


Chapter 7: Utilities

7.1 DUMPCOM

The DUMPCOM utility is used to dump the static common area maintained by the NASTEL name/token

pair. Nastel Support may ask for this when diagnosing problems. The DUMPCOM JCL can be found in

the MLQxx.JCL library.


//*

//* SAMPLE JOB TO DUMP THE NASTEL CSA AREAS.

//* RESERVED FOR DIAGNOSTIC PURPOSES

//*


//*

//DUMPCOM EXEC PGM=DUMPCOM

//STEPLIB DD DSN=++hlq++.LOAD,DISP=SHR


Sample SYSPRINT Output:

Token name=NastelTechV4R5 Token: 10105138 823CA080 00000000 00000000

pab=10105138 length=320

0000 97818240 00000140 E4000020 00080000

0010 BEB512CD BA818B00 00000000 00000000

0020 00000000 00000000 00000000 00000000

0030 00000000 00000000 00000000 00000000

pabe=10105178 length=32

0000 C9000000 0FE01050 BEB512CD C5BD3000

0010 00000000 00000000 00000000 00000000

pabe=10105198 length=32

0000 00000000 00000000 00000000 00000000

0010 00000000 00000000 00000000 00000000

pabe….

ptbl=0FE01050 length=2048

0000 97A38293 00000800 E4000008 00FC0000

0010 BEB512CD C3E99100 90111F38 00000000

ptble=0FE01070 length=252

0000 D1D4E2F2 BEB512CD 1452C700 008E0E88

0010 10111008 00000000 E3C9D1D4 E2F4F540

0020 E2E3C3F0 F4F8F4F6 000000DC 00000002

0030 80000037 BEB512CD C7AE9700 00000000

0040 00000000 916000F8 8FE03CD0 8FE17BB0

0050 90111068 00000000 00000000 03140000

Chapter 7: Utilities Nastel XRay Probes for z/OS


0060 00DC0000 00020000 0003008E 0E880000

0070 2F000000 9010B0E8 8FE01850 8FE17160

0080 8FE03A50 8FE037D0 00000000 00003000

0090 11609C30 F0F20000 C3E2D8F2 40404040

00A0 40404040 40404040 40404040 40404040

00B0 40404040 40404040 40404040 40404040

00C0 40404040 40404040 00F9A480 00000000

00D0 808DDF98 0FCD6FE0 116093E0 00000000

00E0 00000000 00000000 00000000 00000000

00F0 00000000 00000000 00000000 00000000

ptble=0FE0116C length=252

…..

7.2 FREECOM

The FREECOM utility is used to delete the name/token pair. If any probes are running when this utility

is executed, the name/token pair is not removed. All probes must be stopped before running this utility.

The FREECOM JCL can be found in the MLQxx.JCL library.

The 2400 bytes of storage discussed in the Common Storage section will remain on the system until the

next IPL.


//*

//* SAMPLE JOB TO REMOVE THE NASTEL ENVIRONMENT

//* RESERVED FOR DIAGNOSTIC PURPOSES

//* RECOMMENDED TO USE UNDER ADVISEMENT OF NASTEL SUPPORT

//*


//*

//FREECOM EXEC PGM=FREECOM

//STEPLIB DD DSN=++hlq++.LOAD,DISP=SHR


The following message is issued when run successfully.

NSQ7541I NastelTechV4R5 NAME/TOKEN PAIR DELETED

Nastel XRay Probes for z/OS Chapter 7: Utilities


7.3 DELETENT

The DELETENT utility is used to delete the name/token pair and release fixed storage associated with the

name/token pair. If any probes are running when this utility is executed, the name/token pair is not

removed and any fixed storage associated with the running probe is not released. For all stopped probes,

their respective probe areas are reinitialized along with deletion of any outstanding fixed storage

connected to stopped probe. The DELETENT JCL can be found in the MLQxx.JCL library.


//*--------------------------------------------------------------------

//*

//* SAMPLE JOB TO REMOVE THE NASTEL ENVIRONMENT.

//* RESERVED FOR DIAGNOSTIC PURPOSES:

//* RECOMMENDED TO USE UNDER ADVISEMENT OF NASTEL SUPPORT

//*

//* ++instload++ - Installation load HLQ.MLQxx.LOAD created from

//* TSO Receive


//*

//*

//*

//*

//* By default, that is without PARM='FREE' specified on EXEC

//* statement, this job frees any common storage allocated to

//* inactive Probe IDs only.

//*

//* Following message will show in Job log for each Probe ID

//* where CSA freed:

//* NSQ7559I INACTIVE PROBE USING PID=xxxx RESET

//*

//* xxxx represents Probe ID. Refer to Chapter 3 API Interceptor

//* Configuration FIle in TWORKS Probes for z/OS Installation and

//* User Guide.

//*

//*

//* PARM='FREE', if specified on EXEC statement, performs the function

//* above as well as removing Nastel environment.

//*

//*--------------------------------------------------------------------

//DELETENT EXEC PGM=DELETENT

//STEPLIB DD DSN=++instload++,DISP=SHR


Chapter 7: Utilities Nastel XRay Probes for z/OS


The following messages are issued when run successfully.

NSQ7556I CHECKING FOR ACTIVE PROBES...

NSQ7558I PROBE NSQXYZP7 STC05417 USING PID=XYZ7 IS RUNNING

NSQ7559I INACTIVE PROBE USING PID=ABC6 RESET

NSQ7559I PROBES FOUND RUNNING. ACTIVE PROBE COMMON STORAGE NOT DELETED

Nastel XRay Probes for z/OS Chapter 8: Diagnostic Messages


Chapter 8: Diagnostic Messages

Diagnostic messages are produced by all of the subtasks in the probe. The messages are written to the

JESMSGLG using the following format:

(originating task) (message number) (message text)

If the messages are written to a SYSOUT file, they have the following format:

(date) (time) (originating task) (message number) (message text)

The originating task can be, for example, MAIN or XMIT0001.

The message number has the following format:

(message prefix) (message number) (message type)

The message prefix default is NSQ. It can be changed by coding a PARM= parameter in the EXEC

card of the Started Task (STC) Job Control Language (JCL). Choose from one to four characters.

Message numbers are four digits and begin at 1000. The message types are:

I – Information

W – Warning

E – Error

S – Severe

T – Trace

The messages are shown as they would appear in a SYSOUT file without the date and time fields but with

the default message prefix.

All numeric values in the diagnostic messages are in hexadecimal unless otherwise specified.

NOTES:

1. When error messages are received, refer to IBM’s manual SA22-7609 for error codes and further instructions. If you are unable to resolve the error using the prescribed instructions in the IBM documentation, contact Nastel Support for further assistance. 2. If you contact Nastel Support, ensure you have all the required information about your configuration and environment available.

Chapter 8: Diagnostic Messages Nastel XRay Probes for z/OS


Main Task Messages (1000-1999)

NSQ1010S Error loading module nnnn R01=rrrr R15=ssss.

Explanation: The main task was unable to load the module. This message occurs when loading

utility routines prior to start-up.

nnnn- Name of the module

rrrr- System completion code

ssss- Reason code

System Action: Nastel XRay z/OS probe comes down.

Operator Response: Make sure that the specified load module is in the Nastel library in the

STEPLIB for the STC. The value in R01 is composed as follows: xxsssuuu. Use the sss portion to

locate the corresponding system completion code in the manual ‘MVS System Codes’ (SA22-7626)

and attempt to fix the problem. If the problem can’t be fixed on-site, contact Nastel support and

supply them with this error message.

NSQ1050I Nastel z/OS Probe vvvv started.

Explanation: This is the first message displayed.

vvvv- Version and release of the product

System Action: None

Operator Response: None

NSQ1051I Work area=aaaa length=llll.

Explanation: The address of the main task’s work area and its length are displayed.

aaaa- Address of the work area

llll- Length of the work area

System Action: None


NSQ1052I TCB=aaaa.

Explanation: The address of the main task’s TCB is displayed.

aaaa- Address of the TCB

System Action: None


NSQ1053I Main task TIA=aaaa.

Explanation: The address of the main task’s TIA is displayed in hexadecimal. Each task has a TIA.

This is a Nastel control block.

aaaa- Address of the TIA

System Action: None




NSQ1054I PCA=aaaa length=llll.

Explanation: The address of the PCA, a Nastel control block, and its length are displayed.

aaaa- Address of the TIA

llll- Address of the TIA

System Action: None


NSQ1055S probe is not APF authorized.

Explanation: The Nastel XRay z/OS probe is not authorized.

System Action: Probe comes down.

Operator Response: The Nastel load library in the STEPLIB is probably not APF-authorized.

Verify that the library is in the current PROGxx member in the current PARMLIB. Browse the LOG

in SDSF to see which is the current PARMLIB and which PROGxx member is active.

• If the library is not APF-authorized, create a PROGxx member with the correct APF ADD

command. Be sure to specify the correct volume in the command. Update the APF list by

activating the PROGxx member.

• If the library is APF-authorized, make sure that all other libraries in the STEPLIB are APF-

authorized. Remove the unauthorized libraries.

• If the problem still exists, contact Nastel technical support and supply them with this error

message.

NSQ1056S Foreground mode not allowed.

Explanation: An attempt to run the probe in foreground mode was made.

System Action: The probe comes down.

Operator Response: The probe will only run as an STC or a batch JOB. Do not attempt to execute it

in TSO or ISPF.

NSQ1059I Module mmmm loaded at aaaa.

Explanation: The modules that are loaded into common storage have their addresses displayed.

mmmm- Module name

aaaa- Module address

System Action: None


NSQ1060E Unable to create ESTAE environment R15=rrrr.

Explanation: The main task was unable to create a recovery environment.

rrrr- Decimal contents of R15 are displayed.

System Action: Nastel XRay z/OS probe comes down.

Operator Response: Contact Nastel support with the diagnostic message.



NSQ1061I Operating system: nnnn llll.

Explanation: The operating system name and level are displayed.

nnnn- Name of the operating system (Example: z/OS).

llll- Level of the operating system (Example: 01.06.00).

System Action: None


NSQ1062I Storage subsystem: nnnn llll.

Explanation: The storage sub-system name and level are displayed.

nnnn- Name of the storage sub-system (Example: DFSMS/MVS).

llll- Level of the storage sub-system (Example: 01.06.00).

System Action: None


NSQ1063I Last IPL: dddd tttt.

Explanation: The date and time of the last IPL are displayed.

dddd- Date of the last IPL.

tttt- Time of the last IPL.

System Action: None


NSQ1064I Primary subsystem: nnnn tttt Version: vvvv Node: dddd.

Explanation: Information on the primary sub-system is displayed.

nnnn- Name of the primary sub-system.

tttt- Type of the primary sub-system.

vvvv- Version of the primary sub-system.

dddd-- Primary sub-system node.

System Action: None


NSQ1065I Product level: pppp Service level: ssss.

Explanation: The product and service level of the primary sub-system are displayed.

pppp- Product level of the primary sub-system.

ssss- Service level of the primary sub-system.

System Action: None




NSQ1075I Unable to link to configuration module

Explanation: The main task was unable to LINK to the configuration module NTI00005.


Operator Response: The module NTI00005 must be in the Nastel library in the STEPLIB of the

JCL. If it is not, copy it from the install library.

NSQ1076I Error processing configuration file.

Explanation: The main task determined that the configuration file processor found an error in the

configuration file.


Operator Response: Look at the SYSOUT file CNFG for the started-task (STC). There will be

diagnostic messages produced with numbers in the range 2000-2499. Make the correction to the

configuration file and start the STC again.

NSQ1080I Dataspace created - Name=nnnn Size=ssss Stoken=tttt.

Explanation: A dataspace was successfully created.

nnnn- Name of the dataspace.

ssss- Size of the dataspace in 4K blocks (decimal number).

tttt- Space token.

System Action: None.

Operator Response: None.

NSQ1081E DSPSERV CREATE error - Name=nnnn. R15=rrrr R00=ssss.

Explanation: A dataspace could not be created.


rrrr- Contents of R15.

ssss- Contents of R00.


Operator Response: Refer to IBM’s manual SA22-7609 for additional fault isolation instructions.

NSQ1082E ALESERV ADD error - Name=nnnn R15=rrrr.

Explanation: An error occurred trying to add an ALET to the PASN-AL.







NSQ1083E DSPSERV DELETE error - Name=nnnn R15=rrrr R00=ssss.

Explanation: An error occurred trying to delete a dataspace. This message will only occur after

WMQ1102E.



ssss- Contents of R00.

System Action: The probe is shutting down.

Operator Response: Consult the IBM manual SA22-7609 and attempt to figure out the problem.

Otherwise, contact Nastel support and supply them with this error message.

NSQ1084I Dataspace nnnn deleted.

Explanation: The dataspace was deleted. This message can only occur after NSQ1102E.


System Action: The probe is shutting down.


NSQ1085I ALET aaaa created for dataspace nnnn with STOKEN=tttt.

Explanation: The ALET was added to the PASN-AL of the STC.

aaaa- ALET


tttt- Dataspace token.

System Action: None


NSQ1086I DDB at aaaa created and initialized.

Explanation: DDB memory was obtained from common storage and the area was initialized.

aaaa- Address of the DDB.



NSQ1087I Waiting for subtasks to terminate.

Explanation: The mainline task is in process of shutting down. As soon as all subtasks are

terminated, the mainline task will proceed to shutdown.

System Action: None




NSQ1088I Subtask ssss tcb=aaaa detached

Explanation: The subtask name that is detached.

ssss – Subtask name

aaaa – Tcb address

System Action: None


NSQ1089I All subtasks terminated.

Explanation: The mainline was posted that all subtasks have terminated.

System Action: The probe continues shutdown processing.


NSQ1110E Initial dataspace could not be extended. R15=rrrr R00=ssss.

Explanation: The initial dataspace was created with a default size. Once the configuration

parameters are extracted, the working size of all dataspaces has been determined. The initial

dataspace may have to be extended. An error occurred in trying to extend the initial dataspace to the

working size.

rrrr- Decimal contents of R15.

ssss- Decimal contents of R00.



NSQ1111I Initial dataspace extended to bbbb 4K blocks.

Explanation: The initial dataspace was extended to the number of 4K blocks specified in the

message.

bbbb- New size of the dataspace in 4K blocks (decimal).

System Action: None


NSQ1112I Initial dataspace shortened to bbbb 4K blocks.

Explanation: The initial dataspace was shortened to the number of 4K blocks specified in the

message.

bbbb- New size of the dataspace in 4K blocks (decimal).

System Action: None




NSQ1210E Load error for module nnnn. R01=rrrr R15=ssss.

Explanation: An error occurred loading the module with name nnnn.

nnnn- Name of the module.

rrrr- System completion code.

ssss- Reason code.


Operator Response: Please refer to message NSQ1010S.

NSQ1220I PAB created at aaaa.

Explanation: The PAB (Product Anchor Block) was created at address aaaa.

aaaa- Address of the PAB.

System Action: None


NSQ1221S Unable to load IEANTCR R01=cccc R15=rrrr.

Explanation: The name/token create module was not found.

cccc- System completion code.

rrrr- Reason code.


Operator Response: The module IEANTCR must be in the linklist in SYS1.CSSLIB. Ensure the

library is in the linklst and the module is in the library.

NSQ1222I Global name/token pair created.

Explanation: The global name/token pair was created.

System Action: None


NSQ1223E Name/token create error - RC=rrrr.

Explanation: The IEANTCR call failed with return code rrrr.

rrrr- Return code.


Operator Response: Contact Nastel support and supply them with this error message.

NSQ1224I PAB found at aaaa.

Explanation: The PAB was found at address aaaa.


System Action: None




NSQ1225S PAB table at aaaa full.

Explanation: An attempt was made to add a new product type to the PAB table at address aaaa. The

table was full.



Operator Response: Submit the member in the JCL library called DUMPCOM and forward the

output to Nastel support. Wait for a reply from Nastel.

NSQ1226I PTBL found at aaaa.

Explanation: The PTBL was found at address aaaa.

aaaa- Address of the PTBL.

System Action: None


NSQ1227S PTBL at aaaa is full.

Explanation: An attempt was made to add an entry to the PTBL but the table at address aaaa was

full.



Operator Response: Submit the member in the JCL library called DUMPCOM and forward the

output to Nastel support. Wait for a reply from Nastel.

NSQ1228I New PTBL entry for id nnnn at aaaa is reserved.

Explanation: The probe with id nnnn is added to the PTBL entry. The entry address is at aaaa.

nnnn- Product id from the configuration file.

aaaa- Address of the entry in the PTBL.

System Action: None


NSQ1229E PTBL entry at aaaa with id nnnn is in use by ssss(iiii)

Explanation: The PTBL entry with id nnnn at address aaaa is already being used by another probe.

The STC or JOB name is ssss and it has an id of iiii.



ssss- STC or JOB name.

iiii- STC or JOB id.


Operator Response: Change the ProdId value in the configuration file so that it does not conflict

with any other probe tasks that are running.

NSQ1230I PTBL entry at aaaa with id nnnn is being reused.



Explanation: The PTBL entry with id nnnn at address aaaa is being reused.



System Action: None


NSQ1231I PTBL entry at aaaa is being reserved for id nnnn.

Explanation: The empty PTBL entry at address aaaa is being reserved for id nnnn.



System Action: None


NSQ1232I Initial DDB is at aaaa.

Explanation: The DDB for the initial dataspace is at address aaaa.

aaaa- Address of the DDB.

System Action: None


NSQ1233E Reuse of PTBL entry with id nnnn disallowed. Entry being used by ssss(jjjj).

Explanation: Reuse=Y was specified in the configuration file. There is a probe already running that

is using this ID. It has an STC or JOB name of ssss and an STC or JOB id of jjjj.

nnnn- ProdId from the configuration file.

ssss- STC or JOB name.

jjjj- STC or JOB id.


Operator Response: There may be times when Nastel XRay comes down hard and leaves the PTBL

entry ‘in use’. It is possible to reuse the entry by specifying Reuse=Y in configuration in the main

section. An attempt was made to reuse entry with id nnnn but an executing JOB or STC is using it.

NSQ1234S Unable to load IEANTRT R01=cccc R15=rrrr.

Explanation: The name/token retrieve module was not found.

cccc- System completion code.

rrrr- Reason code.


Operator Response: This module resides in SYS1.CSSLIB. Make sure that SYS1.CSSLIB is in the

LNKLST. Contact your z/OS system programming staff.

NSQ1235S Mismatched PTBLE lengths: PTBL value=vvvv Assembled value=aaaa.

Explanation: The version of the probe that is running is not compatible with the version of the probe

that created the PTBLE. Name/token retrieve module was not found.




Operator Response: Stop all probe instances and submit the member in the JCL library called

DUMPCOM. Forward the output to Nastel support. Then submit the member in the JCL library

called FREECOM. Re-submit or re-start the probe.

NSQ1236S Unable to load IEANTDL R01=cccc R15=rrrr.

Explanation: The name/token delete module was not found.

cccc- System completion code

rrrr- Return code



NSQ1237S Name/token delete error –RC=rrrr.

Explanation: The name/token delete module was not found.

rrrr- Return code in decimal.

System Action: The probe is terminated.


NSQ1238I Name/token deleted.

Explanation: The name/token was deleted.



NSQ1239 PTBL created at aaaa.

Explanation: The PTBL was created at address aaaa.




NSQ1240I Linkage index xxxx is created for cp-PC.

Explanation: The linkage index for the cp-PC routine was successfully created.

xxxx- Linkage index.





NSQ1241I Linkage index xxxx is being reused for cp-PC.

Explanation: The linkage index (cp-PC) created in a prior execution of this probe is being reused.

xxxx- Linkage index



NSQ1242I Linkage index xxxx is created for ss-PC.

Explanation: The linkage index for the ss-PC routine was successfully created.

xxxx- Linkage index



NSQ1243I Linkage index xxxx is being reused for ss-PC.

Explanation: The linkage index (ss-PC) created in a prior execution of this probe is being reused.

xxxx - Linkage index

System Action: None


NSQ1245I pppp is using uid uuuu.

Explanation: The probe started task is receiving messages from user address spaces using the same

uid.

pppp –probe jobname

uuuu - Unique identifier

System Action: None


NSQ1250S Unable to create command processor subtask R15=rrrr.

Explanation: The main task was unable to create the command processor subtask.

rrrr- Return code from the ATTACHX macro.



NSQ1251I Command processor subtask created. TCB= aaaa.

Explanation: The command processor subtask was successfully created.

aaaa- Command processor’s TCB address.

System Action: None




NSQ1252E QMGR qqqq is already in use with id pppp jobname jjjj iiii.

Explanation: The queue manager specified in the configuration is being used with another

Transaction Interceptor task.

qqqq – Queue manager name

pppp – Product id

jjjj –Jobname that is currently using the queue manager

iiii – Jobid that is associated with the jobname

System Action: The probe is terminated

Operator Response: Correct the queue manager name and restart the probe.

NSQ1253E UID uuuu is already in use with id pppp jobname jjjj iiii.

Explanation: The unique identifier specified on the //NASTIDxx ddname is being used with another

Transaction Interceptor task.

uuuu – Unique identifier suffix

pppp – Product id

jjjj – Jobname that is currently using the uid

iiii – Jobid that is associated with the jobname


Operator Response: Correct the UID on the //NASTIDxx ddname and restart the probe’s start task.

If this ddname is not used and this message is issued, you are attempting to start a second Transaction

Interceptor that is using a UID of 00, which is the default.

NSQ1254E Probe exceeded maximum number allowed for OS.

Explanation: The maximum number of probes supported for the OS has been exceeded.


Operator Response: None. The maximum limit may be increased.

NSQ1260S Unable to create supervisor manager subtask R15=rrrr.

Explanation: The main task was unable to create the supervisor subtask.

rrrr- The return code from the ATTACHX macro.



NSQ1261I Supervisor manager subtask created. TCB= aaaa.

Explanation: The supervisor manager subtask was successfully created.

aaaa- Supervisor manager’s TCB address.

System Action: None




NSQ1262S Unable to create queue monitor manager subtask R15=rrrr.

Explanation: The main task was unable to create the queue monitor subtask.

rrrr- The return code from the ATTACHX macro.



NSQ1263I Queue Monitor subtask created. TCB= aaaa.

Explanation: The queue monitor subtask was successfully created.

aaaa- Supervisor manager’s TCB address.



NSQ1300 CICS stub module NTI00300 copied to aaaa.

Explanation: CICS stub module is copied to the address aaaa

aaaa- CSA address of the module.

System Action: None


NSQ1400I Nastel z/OS Probe operating.

Explanation: The probe is up and running.

System Action: None


NSQ1800I Nastel z/OS Probe stopping.

Explanation: A /P command was entered. The probe is stopping.

System Action: None


NSQ1810I PTBL entry at aaaa for id nnnn freed.

Explanation: The PTBL entry is freed.

aaaa- Address of the PTBL entry.

nnnn- ProdId from the configuration file.

System Action: None




NSQ1820I Command processor stopped. TCB=aaaa

Explanation: The command processor was stopped.

aaaa- Command processor’s TCB address.

System Action: None


NSQ1830I Supervisor stopped. TCB=aaaa

Explanation: The supervisor was stopped.

aaaa- Supervisor’s TCB address.

System Action: None


NSQ1899I Nastel z/OS Probe ended.

Explanation: The main task has terminated.

System Action: None


NSQ1900E Unable to delete dataspace ALET aaaa R15=rrrr.

Explanation: The main task was unable to delete the dataspace.

aaaa – ALET

rrrr – Return code

System Action: None. Nastel XRay was shutting down.


NSQ1901E Unable to delete dataspace with STOKEN ssss R15=rrrr R00=xxxx.

Explanation: The main task was unable to delete the dataspace.

ssss – Space token

rrrr – Return code

xxxx –Reason code

System Action: None. Nastel XRay was shutting down.




Configuration File Processor Messages (2400-2499):

NSQ2400I Configuration file processor started.

Explanation: The configuration file processor has started.



NSQ2401E Unable to OPEN SYSIN file.

Explanation: The configuration file processor could not OPEN the configuration file.

System Action: The configuration file processor returns to the main task with a non-zero return code.

This causes the main task to shut down.

Operator Response: Ensure the SYSIN DD card is correctly specified in the STC JCL.

NSQ2402E SYSIN LRECL must be 80.

Explanation: The SYSIN file LRECL (logical record length) must be 80.



Operator Response: Ensure that the SYSIN LRECL is 80.

NSQ2403E SYSIN DSORG is not PS.

Explanation: The DSORG of the SYSIN file is not PS (physical sequential).



Operator Response: Ensure that the SYSIN DSORG is PS.

NSQ2410E Unknown section nnnn in the configuration file.

Explanation: The section nnnn is unknown to the configuration file processor.

nnnn- Invalid section name.



Operator Response: Refer to the Configuring the Probe section in this manual.

NSQ2420E Missing parameter in section ssss.

Explanation: The error was found on a keyword that did not specify any value in section ssss in the

configuration file. Parameters are specified in keyword=value pairs.

ssss- The section area containing the invalid control card in the configuration file.



Operator Response: A parameter specified is missing the equal (=) sign for the keyword. Correct

the card in question.



NSQ2421E Value vvvv specified for parameter pppp in section ssss is invalid.

Explanation: The value specified for the keyword parameter is not a supported parameter.

vvvv – Value for the keyword specified.

pppp – Keyword parameter.

ssss - The section area containing the invalid control card in the configuration file.



Operator Response: Correct the keyword value with the error.

NSQ2422E Storage failure iiii aaaa user message table.

Explanation: A storage failure occurred when obtaining or releasing storage used for the user

message table.

iiii – A number that identifies the storage call issued by the probe when altering the message

table storage.

aaaa – The action that the storage call made [obtaining | releasing].


Operator Response: Increase the region size for the probe’s address space and restart the probe.

Contact Nastel support if you are unable to resolve this problem.

NSQ2423W CURRENTDEPTH parameter is not used. CURRENTDEPTHMIN parameter in section ssss

is ignored.

Explanation: The CURRENTDEPTH option, which enables the QMON subtask, is not specified.

The user specified the CURRENTDEPTHMIN option in the configuration. This option is not used

and will be ignored when the probe is started.

ssss – Section area containing the CURRENTDEPTHMIN control card in the configuration file.

System Action: The probe is started.

Operator Response: None. Determine if you need to enable the QMON subtask interface.

NSQ2424E CURRENTDEPTHMIN=vvvv value in section ssss is greater than the CURRENTDEPTH

value specified.

Explanation: The CURRENTDEPTHMIN value specified exceeds the value specified as the

maximum threshold value used on the CURRENTDEPTH option.

vvvv – The value specified on the CURRENTDEPTHMIN option.

ssss – The section area containing the CURRENTDEPTHMIN control card in the configuration file.


Operator Response: Correct the CURRENTDEPTHMIN value and restart the probe. Ensure the

CURRENTDEPTHMIN value is less than the CURRENTDEPTH value and the difference between

both values must be greater than or equal to 1000.



NSQ2425E CURRENTDEPTHMIN=vvvv value specified relative to the CURRENTDEPTH value must

be greater than 1000.

Explanation: The CURRENTDEPTHMIN value specified requires that this value is less than the

CURRENTDEPTH value and the difference between the two values must be greater than 1000.

vvvv – The value specified on the CURRENTDEPTHMIN option.


Operator Response: Correct the CURRENTDEPTHMIN value and restart the probe. Ensure the

CURRENTDEPTHMIN value is less than the CURRENTDEPTH value and the difference between

both values must be greater than or equal to 1000.

NSQ2430E Parameter pppp is not supported in section ssss.

Explanation: The parameter is not a configurable option for the specified section.

pppp- Parameter.

ssss- Section.



Operator Response: Consult the Installation Guide for the valid parameters for the specified section.

NSQ2440E Value for parameter pppp is to long.

Explanation: The value for parameter pppp exceeds the maximum number of characters allowed. For

a numeric value this is the same as exceeding the maximum value supported.

pppp- Parameter.



Operator Response: Consult Table 3-3, Configuration File Parameters for the maximum number of

characters allowed for parameter pppp. Reduce the number of characters.

NSQ2450I pppp=vvvv used in section ssss.

Explanation: The value vvvv specified for parameter pppp is used.

pppp- Parameter.

vvvv - Value.

ssss- Section.



NSQ2460E Unmatched double quotes for parameter pppp.

Explanation: The value for parameter pppp started with a double quote but did not end with one.

pppp- Parameter.



Operator Response: Add an ending double quote to the parameter value.



NSQ2471I Parameter pppp=vvvv in section ssss using override value.

Explanation: The numeric value vvvv is used for parameter pppp in section ssss even though the

value is outside the minimum and maximum range.

pppp - Parameter

vvvv- Override parameter value.

ssss- Section.

System Action: The parameter specified uses the override value.


NSQ2472I Parameter pppp=vvvv in section ssss using default value.

Explanation: The value vvvv was applied to parameter pppp in section ssss. The parameter was not

specified in the configuration file. The default value is used.

pppp- Parameter.

vvvv – Default parameter value.

ssss- Section.

System Action: The parameter specified uses the default value.


NSQ2473E Parameter pppp is missing is section ssss. This is a required parameter.

Explanation: The parameter pppp was not specified in the configuration file.

pppp- Required parameter.

ssss- Section.


Operator Response: Add the missing parameter and restart the probe.

NSQ2474I Qmgr is not specified in section MQSERIES. Probe will connect to the default queue

manager.

Explanation: The default queue manager specified in the IBM MQ configuration will be used.

System Action: The default queue manager is used.


NSQ2480E Value of parameter pppp is not numeric.

Explanation: The value following the equal sign is not numeric.

pppp- Parameter.



Operator Response: Correct the value following the equal sign.



NSQ2490E Value vvvv is less than the minimum mmmm for parameter pppp in section ssss.

Explanation: The numeric value vvvv is less than the minimum mmmm allowed.

vvvv- Numeric value.

mmmm- Minimum value.

pppp – Parameter

ssss - Section



Operator Response: Make numeric value greater than or equal to minimum value mmmm and restart

probe.

NSQ2491E Value vvvv is greater than the maximum mmmm for parameter pppp in section ssss.

Explanation: The numeric value vvvv is greater than the allowed maximum mmmm.

vvvv- Numeric value.

mmmm- Maximum value.

pppp – Parameter

ssss - Section



Operator Response: Make the numeric value less than or equal to the maximum value mmmm and

restart the probe.

NSQ2492E Value entered exceeds maximum value for parameter pppp in section ssss.

Explanation: The numeric value string length specified causes value to exceed the maximum value.

pppp – Parameter

ssss - Section



Operator Response: Correct the invalid parameter and restart the probe.

NSQ2493E Value missing for parameter pppp in section ssss

Explanation: There is no value specified for parameter pppp in section ssss.

pppp – Parameter

ssss - Section



Operator Response: Correct the invalid parameter and restart the probe task.

NSQ2499I Configuration file processor ended.

Explanation: The configuration file processor has ended.

System Action: None




QMON Subtask Messages (2800-2899)

NSQ2800I Queue message monitor started.

Explanation: The QMON subtask is started.

System Action: None



Explanation: The QMON subtask’s work area is at aaaa for a length of llll.

aaaa- Work area address.

llll- Work area length.

System Action: None


NSQ2802I TCB=aaaa.

Explanation: The QMON subtask TCB address is displayed.

aaaa- TCB address.

System Action: None


NSQ2803I TIA=aaaa length=llll.

Explanation: The QMON subtask’s TIA address and length are displayed.

aaaa- TIA address.

llll- TIA length.

System Action: None


NSQ2804E Queue message monitor MQINQ iiii error on queue qqqq. CC=cccc RC=rrrr.

Explanation: The QMON subtask received an error issuing an MQINQ call.

iiii - A message identifier number

qqqq- The base or alias queue name that is monitored.

cccc- The return code returned from the MQINQ call.

rrrr- The reason code returned from the MQINQ call.

System Action: The MQINQ call is not successful.

Operator Response: Use completion code and reason code to determine cause of the problem. Refer

to IBM manual SC34-6062. If unable to correct problem, contact Nastel support.



NSQ2805E Queue message monitor MQSET iiii error on queue qqqq. CC=cccc RC=rrrr.

Explanation: The QMON subtask received an error issuing an MQSET call to enable or disable the

queue.

iiii - A message identifier number

qqqq- The base or alias queue name that is monitored.

cccc- The return code returned from the MQSET call.

rrrr- The reason code returned from the MQSET call.

System Action: The MQSET call is not successful. The queue inhibit state is not changed.

Operator Response: Use completion code and reason code to determine cause of problem. Refer to

IBM manual SC34-6062. If unable to correct problem, contact Nastel support.

NSQ2810I Queue message monitor operating.

Explanation: The QMON subtask is initialized during probe startup.

System Action: None


NSQ2811I Message queue is disabled. nnnn messages on queue

Explanation: The QMON subtask disabled the message queue because the currentdepth on the

NASTEL.APTM.MESSAGE queue was equal to or exceeded the currentdepth threshold specified for

the QMON subtask monitor value.

nnnn – The currentdepth of the message queue.

System Action: The NASTEL.APTM.MESSAGE queue (or alias queue if used) PUT state is

temporarily disabled.

Operator Response: none. If this message is issued frequently in the QMON subtask log, you may

want to adjust the currentdepth threshold value, currentdepthmin threshold value, currentdepthint

timer, and possibly change the dataspace size.

NSQ28112 Message queue is enabled. nnnn messages on queue

Explanation: The QMON subtask enabled the message queue because the currentdepth on the

NASTEL.APTM.MESSAGE queue is less than or equal to the currentdepthmin threshold value

specified for the QMON subtask monitor value.

nnnn – The currentdepth of the message queue.

System Action: The NASTEL.APTM.MESSAGE queue (or alias queue if used) PUT state is

changed to enabled.

Operator Response: none.

NSQ2820I Queue message monitor stopping.

Explanation: The QMON subtask is terminating because the probe was stopped.

System Action: None




NSQ2814E Unable to establish ESTAE R15=rrrr.

Explanation: The QMON subtask could not establish an ESTAE environment.

rrrr- R15 holds return code from the ESTAE service call.

System Action: The QMON subtask is terminated and the probe is not started.

Operator Response: Contact Nastel support and supply them with the diagnostic message.

NSQ2815I Queue message monitor subtask connected to the default qmgr.

Explanation: The QMON subtask is using the default QMGR

System Action: None


NSQ2816I Queue message monitor subtask connected to QMGR qqqq.

Explanation: The QMON subtask is using the specified QMGR

qqqq – queue manager

System Action: None


NSQ2817I Queue message monitor subtask disconnected from default qmgr.

Explanation: The QMON subtask is no longer connected to the default QMGR

System Action: None


NSQ2818I Queue message monitor subtask disconnected from QMGR qqqq.

Explanation: The QMON subtask is no longer connected to the QMGR specified.

qqqq – The queue manager.

System Action: None


NSQ2821E Queue message monitor MQCONN error CC=cccc RC=rrrr.

Explanation: The QMON subtask received an error connecting to the QMGR

cccc- The return code returned from the MQCONN call.

rrrr- The reason code returned from the MQCONN call.

System Action: The MQCONN call is not successful.





NSQ2822E Queue message monitor MQOPEN error on queue qqqq CC=cccc RC=rrrr.

Explanation: The QMON subtask received an error opening the message queue.

qqqq – The queue name.

cccc- The return code returned from the MQCONN call.

rrrr- The reason code returned from the MQCONN call.

System Action: The MQOPEN call is not successful.



NSQ2823E Queue message monitor MQCLOSE error on queue qqqq CC=cccc RC=rrrr.

Explanation: The QMON subtask received an error issuing an MQCLOSE call.

qqqq- The base or alias queue name.

cccc- The return code returned from the MQCLOSE call.

rrrr- The reason code returned from the MQCLOSE call.

System Action: The MQCLOSE call is not successful.



NSQ2824E Queue message monitor MQDISC error CC=cccc RC=rrrr.

Explanation: The QMON subtask received an error issuing an MQDISC call.

cccc- The return code returned from the MQDISC call.

rrrr- The reason code returned from the MQDISC call.

System Action: The MQDISC call is not successful.



NSQ2825I Queue message subtask is started.

Explanation: The user issued the START QMON command to activate the QMON subtask.

System Action: None


NSQ2826I Queue message subtask is already active.

Explanation: The user issued the START QMON command to activate the QMON subtask, but it is

already running.

System Action: None




NSQ2827I Queue message subtask is stopped.

Explanation: The user issued the STOP QMON command to terminate the QMON subtask.

System Action: None


NSQ2828I Queue message subtask is already stopped.

Explanation: The user issued the STOP QMON command to terminate the QMON subtask but it was

already stopped.

System Action: None


NSQ2899I Queue message monitor terminated.

Explanation: The QMON subtask has ended.

System Action: None




Logger Messages (3400-3499):

NSQ3400I Logger started.

Explanation: The logger subtask has started.

System Action: None



Explanation: The logger’s work area is at aaaa for a length of llll.



System Action: None


NSQ3402I TCB=aaaa.

Explanation: The logger’s TCB address is displayed.

aaaa- TCB address.

System Action: None



Explanation: The logger’s TIA address and length are displayed.

aaaa- TIA address.

llll- TIA length.

System Action: None


NSQ3410I Logger operating

Explanation: The logger is now up and running.

System Action: None


NSQ3420I Logger stopping

Explanation: The logger has been told to stop by the main task. It starts its shutdown process.





NSQ3430E Allocation error for DDname nnnn : Error=eeee Info=iiii

Explanation: The logger tried to dynamically allocate a SYSOUT dataset with the name nnnn.

Dynamic allocation was unable to allocate the dataset.

nnnn- DDNAME

eeee- Dynamic allocation error code.

iiii- Dynamic allocation information code.


Operator Response: Either the DDname has been overlaid or JES2 is unable to allocate the file.

eeee corresponds to S99ERROR and is documented in SA22-7608 (See Appendix) in Chapter 26.

The section is called Interpreting Error Reason Codes from DYNALLOC. iiii corresponds to

S99INFO and is documented in the same chapter in section Interpreting Information Reason Codes

from DYNALLOC. If unable to resolve the problem, contact Nastel support.

NSQ3499I Logger terminated.

Explanation: The logger has terminated.





Supervisor Manager Messages (4000-4999):

NSQ4000I Supervisor subtask started.

Explanation: The supervisor subtask has started.

System Action: None



Explanation: The supervisor’s work area is at aaaa for a length of llll.


llll- Work area length in hexadecimal.

System Action: None


NSQ4002I TCB=aaaa.

Explanation: The supervisor’s TCB address is displayed.

aaaa- TCB address.

System Action: None



Explanation: The supervisor’s TIA address and its length are displayed.

aaaa- TCB address.

llll- TIA length.

System Action: None


NSQ4004I Initial ddb is at aaaa for transmitter 1.

Explanation: The supervisor subtask was passed the address of the DDB block mapping the first

dataspace to be used.

aaaa- DDB address.

System Action: None




NSQ4100I Transmitter nnnn created. TCB=aaaa.

Explanation: The supervisor created transmitter subtask nnnn.

nnnn- Number of the transmitter (1,2,3…).

aaaa- TCB address of the transmitter.

System Action: None


NSQ4101E Unable to create transmitter nnnn R15=rrrr.

Explanation: The supervisor created transmitter subtask nnnn.

nnnn- Number of the transmitter (1,2,3…).

rrrr- Return code from the ATTACHX macro.

System Action: The supervisor subtask aborts and starts its shutdown processing. It tells the main

task to stop. The probe comes down.


NSQ4102I All transmitter subtasks initialized.

Explanation: All transmitter subtasks are initialized. The first transmitter is active and the other

transmitters are idle.

System Action: None


NSQ4400I Supervisor operating

Explanation: The supervisor has successfully attached all the transmitter subtasks and is now up and

operating.

System Action: None


NSQ4500I Current dataspace with DDB aaaa released for transmitter nnnn.

Explanation: The supervisor has released all the storage associated with the dataspace mapped by

DDB at address aaaa used by transmitter nnnn.

aaaa- DDB address.

nnnn – transmitter number





NSQ4501I New dataspace with DDB aaaa is now being processed for transmitter nnnn

Explanation: The supervisor has switched to the dataspace mapped by DDB at address aaaa.

Transmitter nnnn is the transmitter subtask using this dataspace.

aaaa- DDB address.

nnnn – transmitter number



NSQ4800I Supervisor subtask stopping.

Explanation: The supervisor manager subtask shutdown processing started.



NSQ4805E Estaex service failed in the Supervisor subtask.

Explanation: The Estaex service failed to establish the retry routine.



NSQ4900I Transmitter nnnn TCB=aaaa detached.

Explanation: The supervisor manager subtask has successfully detached transmitter nnnn.

nnnn- Transmitter number.

aaaa- Transmitter’s TCB address.



NSQ4999I Supervisor terminated.

Explanation: The supervisor subtask has terminated.





Transmitter Messages (5000-5999):

NSQ5000I Transmitter nnnn started

Explanation: The transmitter subtask nnnn has started.


System Action: None


NSQ5001I Work area=aaaa length=llll

Explanation: The transmitter’s work area is at aaaa for a length of llll.



System Action: None


NSQ5002I TCB=aaaa

Explanation: The transmitter’s TCB address is displayed.

aaaa- TCB address.

System Action: None


NSQ5003I TIA=aaaa length=llll

Explanation: The transmitter’s TIA address and its length are displayed.

aaaa- TCB address.

llll- TIA length.

System Action: None


NSQ5050E Unable to establish ESTAE R15=rrrr.

Explanation: The transmitter could not establish an ESTAE environment.

rrrr- Return code in R15 from the ESTAE macro.

System Action: The transmitter shuts down. This causes the entire system to come down.


NSQ5100I DDB at aaaa

Explanation: This transmitter is associated with the dataspace described by the DDB at aaaa.

aaaa- DDB address.

System Action: None




NSQ5200S Transmitter nnnn MQCONN error Qmgr=mmmm CC=cccc RC=rrrr. [No retry | retry

connection every ssss seconds.]

Explanation: Transmitter nnnn encountered a severe error in trying to connect to queue manager

mmmm. The completion and reason codes are in cccc and rrrr respectively.


mmmm- Queue manager name.

ssss - Retry connect time in seconds

cccc- Condition code in decimal.

rrrr- Reason code in decimal.

System Action: During initialization the transmitter subtask terminates and the probe interceptor will

shut down. If this error is issued after initialization, it will attempt to reconnect to the queue manager

based on the ConnectRetry value specified in the configuration file.

If this message is issued after initialization, the MQ messages are still intercepted and placed in the

active transmitter dataspace. Once the connection is reestablished the messages are forwarded to the

stream task.

Operator Response: Using the completion and reason codes, consult manual SC34-6062 (see

References) and investigate the MQCONN call. Contact your MQ administrator for further help.

NSQ5201W Transmitter nnnn MQCONN error Qmgr=mmmm CC=cccc RC=rrrr. retry connection every

ssss seconds.

Explanation: Transmitter nnnn could not connect to queue manager mmmm. The completion and

reason codes are in cccc and rrrr respectively.



ssss – Retry connect time in seconds

cccc- Condition code in decimal.


System Action: The transmitter sub task is started and will attempt to reconnect to the queue

manager based on the ConnectRetry value specified in the configuration file. The MQ messages are

still intercepted and placed in the active transmitter dataspace. Once the connection is reestablished

the messages are forwarded to the stream task.


References) and investigate the MQCONN call. Contact your MQ administrator for further help. If

you are unable to solve the problem, contact Nastel support and supply them with the diagnostic

message.

NSQ5202I Transmitter nnnn connected to default queue manager.

Explanation: Transmitter nnnn connected to the default queue manager.


System Action: None




NSQ5203I Transmitter nnnn connected to mmmm.

Explanation: Transmitter nnnn connected to queue manager mmmm.





NSQ5204E Transmitter nnnn MQOPEN error on queue qqqq CC=cccc RC=rrrr.

Explanation: An error occurred opening queue qqqq.


qqqq- Queue name.

cccc- Completion code in decimal.


System Action: This brings the transmitter down and then the probe comes down.


References) and investigate the MQOPEN call. Contact your MQ administrator for further help.

NSQ5205I Transmitter nnnn MQDISC CC=cccc RC=rrrr.

Explanation: Transmitter nnnn disconnected. This message only occurs after message 5204.




System Action: The system is on its way down.


NSQ5206E Transmitter nnnn MQOPEN error on alias queue qqqq CC=cccc RC=rrrr.

Explanation: Transmitter nnnn could not open alias queue qqqq.


qqqq – Alias queue name.



System Action: The transmitter comes down and so does the STC.





NSQ5207E Transmitter nnnn MQINQ error on alias queue qqqq CC=cccc RC=rrrr.

Explanation: Transmitter nnnn could not issue an MQINQ on alias queue qqqq.






Operator Response: Use completion code and reason code and determine cause of problem. Refer to


NSQ5208I Transmitter nnnn max message length for tttt queue qqqq is llll.

Explanation: The maximum message length for local or alias queue qqqq is llll.


tttt – Local or target


llll – Maximum message length.



NSQ5209I Transmitter nnnn MQCLOSE on alias queue qqqq.CC=cccc RC=rrrr.

Explanation: The transmitter closed the alias queue qqqq.



cccc – Completion code.

rrrr – Reason code.



NSQ5210I Transmitter nnnn tttt queue qqqq is opened.

Explanation: Transmitter nnnn successfully opened tttt queue qqqq.


tttt – Local or alias

qqqq- Queue name.





NSQ5215E Transmitter nnnn MQINQ error on queue qqqq: CC=cccc RC=rrrr.

Explanation: Transmitter nnnn could not inquire on queue qqqq.


qqqq- Queue name.



System Action: The transmitter subtask is terminated and the probe is not started.

Operator Response: This error should not occur in production. Using the completion and reason

codes, consult manual SC34-6062 (see Appendix A) and investigate the MQINQ call. Contact your

MQ administrator for further help. If you are unable to solve the problem, contact Nastel support and

supply them with the diagnostic message.

NSQ5216I Transmitter nnnn target queue qqqq is opened.

Explanation: The target queue used by the alias queue name is opened.


qqqq- Queue name.



NSQ5217E Transmitter nnnn Queue qqqq is not a local or alias queue. Rejected.

Explanation: The maximum message length for queue qqqq is llll.

nnnn- Transmitter number in decimal.

qqqq- Queue name.

llll- Maximum message length.


Operator Response: Make sure that the queue specified for the transmitters is either a local queue or

an alias queue.

NSQ5218E Transmitter nnnn MQINQ invalid response on queue qqqq.

Explanation: The MQ environment has returned an invalid response on the MQINQ call when the

transmitter task nnnn checks the PUT inhibit indicator on queue qqqq. This response is not

supported.

nnnn- Transmitter number in decimal.

qqqq- Queue name.

System Action: The transmitter task issues the error message and will continue to check the PUT

inhibit indicator using the PutEnableTime value specified in the configuration. Messages are not

received in this state.

Operator Response: Contact Nastel Support if a normal response is never received.



NSQ5219E Transmitter tttt alias queue qqqq is not using base queue NASTEL.APTM.MESSAGE.

Explanation: The transmitter task tttt was started with an alias queue qqqq that is not configured

using our base queue NASTEL.APTM.MESSAGE queue.

tttt – the transmitter subtask number

qqqq – the name of the alias base queue configured in the probe configuration file.

System Action: The transmitter task is terminated and the probe is not started.

Operator Response: Correct the alias queue used in the probe configuration to ensure that the

NASTEL.APTM.MESSAGE queue is the base queue used. Restart the probe.

NSQ5220E Transmitter tttt is using invalid queue qqqq.

Explanation: The transmitter task tttt was started using a queue qqqq that is not an alias queue and is

not configured using the NASTEL.APTM.MESSAGE queue.

tttt – the transmitter subtask number

qqqq – the name of the queue specified.

System Action: The transmitter task is terminated and the probe is not started.

Operator Response: Correct the queue name and restart the probe.

NSQ5400I Transmitter nnnn is ssss.

Explanation: The transmitter that is active is the subtask that is used to process the current dataspace.

The transmitters in the idle state are standby transmitters.


ssss – Active or idle.



NSQ5425I z/OS contextual data transmitted

Explanation: z/OS contextual data has been put to the MQ queue.



NSQ5430I Put is disabled for queue qqqq

Explanation: The user has disabled the PUT function on the NASTEL interceptor queue qqqq.

qqqq – Queue name

System Action: The probe interceptor stops intercepting messages.




NSQ5431I Put is enabled for queue qqqq

Explanation: The user has enabled the PUT function on the NASTEL interceptor queue qqqq.

qqqq – Queue name

System Action: The probe interceptor starts intercepting messages.


NSQ5450I Transmission starting

Explanation: The transmitter has recognized the first MQ message in the dataspace.



NSQ5490I Dataspace is full. Transmitter nnnn switching over to next transmitter

Explanation: The current transmitter nnnn has no more room to add any intercepted messages into

the dataspace. This is likely to occur when the rate of messages received is exceeding the rate at

which messages are placed on the Nastel message queue and the supervisor manager subtask has not

freed enough dataspace storage.


System Action: The current transmitter is placed in the idle state. The next transmitter nnnn

becomes the active transmitter and is used to receive messages on the dataspace.

Operator Response: The dataspace size parameter may be too small. Make the dataspace size

parameter larger and restart the probe.

NSQ5491I Transmitter nnnn sent all messages.

Explanation: The transmitter task sent any messages residing on the respective dataspace to Nastel

XRay following a reconnection to the QMGR. This situation indicates that the probe had collected

messages prior to the QMGR terminating.


System Action: None


NSQ5492I Transmitter nnnn dataspace is empty.

Explanation: The dataspace associated with transmitter nnnn is now empty. There are no messages

residing on the dataspace.


System Action: None




NSQ5700S Transmitter nnnn MQPUT severe error. CC=cccc RC=rrrr. Retry the connection every ssss

seconds.

Explanation: The transmitter encountered a severe error attempting an MQPUT to the local or alias

queue.


ssss – Connect retry interval in seconds.



System Action: The transmitter subtask will disconnect from the queue manager and attempt to

reconnect based on the ConnectRetry value specified in the configuration file. The MQ messages are

still intercepted and placed in the active transmitter dataspace. Once the connection is reestablished,

the messages are forwarded to the stream task.

Operator Response: Using the completion and reason codes, refer to IBM manual SC34-6062 in the

section on MQPUT to determine the cause of the problem. Correct the problem causing the error

codes that were issued. If unable to correct the problem, contact Nastel support.

NSQ5701E Transmitter nnnn MQPUT queue full. CC=cccc RC=rrrr. Retry the connection every ssss

seconds

Explanation: The NASTEL.APTM.MESSAGE queue is full.

nnnn - Transmitter number.



ssss – Connect retry interval in seconds

System Action: The transmitter subtask will retry processing the queue using the ConnectRetry

interval.

Operator Response: Make sure the queue is being emptied by Nastel’s z/OS Probe. Confirm that

the queue is being processed by the stream.

NSQ5702W Transmitter nnnn MQPUT quiescing. CC=cccc RC=rrrr. Retry the connection every ssss

seconds

Explanation: The Queue Manager has been requested to shutdown. The MQPUT call recognized the

quiescent state in which case the transmitter subtask will disconnect from the queue manager.

nnnn - Transmitter number.




System Action: The transmitter sub task will disconnect from the queue manager and attempt to

reconnect based on the ConnectRetry value specified in the configuration file.

Operator Response: Restart the QMGR.



NSQ5703E Transmitter nnnn MQPUT pageset full. CC=cccc RC=rrrr. Retry the connection every ssss

seconds

Explanation: The pageset space associated with the NASTEL.APTM.MESSAGE queue is full.





System Action: The transmitter subtask will retry processing the queue using the ConnectRetry

interval.

Operator Response: Make sure the queue is being emptied by Nastel’s z/OS Probe. Confirm that

the queue is being processed by the stream.

NSQ5800I Transmitter nnnn is stopping

Explanation: The transmitter starts its shutdown process.


System Action: None


NSQ5810E Transmitter nnnn MQCLOSE on queue qqqq.CC=cccc RC=rrrr.

Explanation: The transmitter closes the queue qqqq.


qqqq- Queue name.



System Action: None


NSQ5820E Transmitter nnnn MQDISC CC=cccc RC=rrrr.

Explanation: The transmitter has disconnected from the queue manager.




System Action: None




NSQ5900I First write yyyy/jjj hh:mm:ss.ffffff.

Explanation: This occurs when either a batch or a CICS agent copies the first contextual entry into

the data space.

yyyy – Year

jjj – Julian day

hh – Hour of the day (00-23)

mm – Minute in the hour (00-59)

ss – Seconds in the minute (00-59)

ffffff – Fraction of a second



NSQ5901I Last write yyyy/jjj hh:mm:ss.ffffff.

Explanation: This occurs when either a batch or a CICS agent copies the last contextual entry into

the data space. This happens either when the data space is full or when the STC comes down.

yyyy – Year

jjj – Julian day



ss – Seconds in the minute (00, 59)




NSQ5902I First read yyyy/jjj hh:mm:ss.ffffff.

Explanation: This occurs when the transmitter copies the first contextual entry from the data space

and puts it into an MQ queue.

yyyy – Year

jjj – Julian day



ss – Seconds in the minute (00,59)






NSQ5903I Last read yyyy/jjj hh:mm:ss.ffffff.

Explanation: This occurs when the transmitter copies to the last contextual entry in the data space.

This happens when the data space is full or when the STC comes down.

yyyy – Year

jjj – Julian day



ss – Seconds in the minute (00-59)


System Action: None


NSQ5904I Number of MQPUTs=nnnn.

Explanation: This is the number of MQPUTs issued by the transmitter.

nnnn – Number of MQPUTs.

System Action: None


NSQ5910I Transmitter nnnn reconnected to qqqq.

Explanation: The transmitter subtask nnnn reconnected to the queue manager qqqq.

nnnn – Transmitter number

qqqq – Queue manager

System Action: The probe interceptor will start sending the most recent messages received from the

transmitter dataspaces.


NSQ5911I Transmitter nnnn disconnected from qqqq.

Explanation: The transmitter nnnn disconnected from the queue manager qqqq.

nnnn – Transmitter number


System Action: None


NSQ5999I Transmitter nnnn terminated.

Explanation: The transmitter has disconnected from the queue manager.


System Action: None




Command Processor Messages (6000-6999):

NSQ6000I Command processor started.

Explanation: The command processor subtask has started.

System Action: None



Explanation: The command processor’s work area is at address aaaa and has a length of llll bytes.

aaaa -Work area address.

llll - Work area length.

System Action: None


NSQ6002I TCB=aaaa.

Explanation: The command processor’s address is displayed.

aaaa - TCB address in hexadecimal.

System Action: None



Explanation: The command processor’s TIA address and length are displayed.

aaaa - TIA address.

llll - TIA length.

System Action: None


NSQ6105I All transmitters are dddd.

Explanation: The transmitter’s send state is enabled or disabled. The modify start or stop send

command is used to enable or disable the transmission process. The send state is enabled when the

probe is started.

dddd – Enabled or disabled

System Action: When the send state is enabled, all events are forwarded to the queue. When the

send state is disabled, events are not forwarded but they are received in the active dataspace.

Operator Response: Use the modify start or stop send command to change the send state

NSQ6106S No xmit TIA block found.

Explanation: The transmitter’s subtask information block is not valid.

System Action: None

Operator Response: Contact Nastel support



NSQ6107I [Stopping | Starting] message queue subtask.

Explanation: User issued the STOP or START QMON command to start or terminate the QMON

subtask.

System Action: None


NSQ6108I TM transmitter is already dddd.

Explanation: All the transmitter subtasks are in the send dddd state. The command was previously

issued.


System Action: The send state for the transmitter subtasks is not changed.


NSQ6110I The collection interface is dddd.

Explanation: The probe interface to all outside users is enabled or disabled.


System Action: When enabled, events are received in the active transmitter’s dataspace for

transmission to Nastel XRay. When disabled, events are not received.


NSQ6111S The product id is not found.

Explanation: The PTBL entry block is invalid.

System Action: The command issued is not executed.

Operator Response: Contact Nastel support.

NSQ6112I The collection interface is already dddd.

Explanation: The probe collection state is already dddd. The command was previously issued.


System Action: The collection state is not changed.


NSQ6113I QMON subtask is not active.

Operator Response: The QMON subtask must be active in order to accept QMON command

requests. The user may enable the currentdepth value in the probe configuration and restart the probe

or issue the START QMON command to activate the QMON subtask.



NSQ6114S No TIA block found.

Explanation: The task interface control block does not exist.

System Action: The command is not processed.


NSQ6115I Invalid value specified for vvvv.

Explanation: The user entered an invalid value when attempting the change command to change the

currentdepth or currentdepthint values used for the QMON subtask.

vvvv – currentdepth | currentdepthint

System Action: The requested value is not changed.

Operator Response: Retry the change command using the proper values supported for the

currentdepth or currentdepthint options.

NSQ6117E CDEPTHMIN value specified exceeds the CURRENTDEPTH value.

Explanation: The user entered a CDEPTHMIN value that is greater than the CURRENTDEPTH

value.

System Action: The CURRENTDEPTHMIN value is not changed.

Operator Response: Retry the CHANGE command using a valid CDEPTHMIN value.

NSQ6118E CDEPTHMIN value specified relative to the CURRENTDEPTH value must be greater than

1000.

Explanation: The user entered a CDEPTHMIN value that is less than the CURRENTDEPTH value

but the difference between both values must be greater than 1000.

System Action: The CURRENTDEPTHMIN value is not changed.

Operator Response: Retry the CHANGE command using a valid CDEPTHMIN value.

NSQ6137I QMON Display

STATE: ssss

CURRENTDEPTH: cccc

CURRENTDEPTHINTERVAL: dddd

Explanation: The user entered the Display QMON command.

ssss – Active | Inactive

cccc – currentdepth threshold value used by the QMON subtask

dddd – currentdepthint value in seconds where the QMON subtask checks the currentdepth of the

message queue against the currentdepth threshold value.

System Action: Messages are displayed when the Display QMON command is issued.




NSQ6200S Unable to create the logger subtask R15=rrrr.

Explanation: The ATTACHX macro returned with an error. The logger subtask could not be

created.


System Action: The probe logger subtask did not start.


NSQ6201I Logger subtask created. TCB=aaaa.

Explanation: The logger subtask was successfully created.

aaaa- Logger’s subtask TCB address.

System Action: None


NSQ6400I Command processor operating.

Explanation: The command processor subtask is up and running.

System Action: None


NSQ6405I Tracing for rrrr is already oooo.

Explanation: The trace batch state is already set. The command was previously issued.

rrrr – Batch or CICS

oooo - On or Off

System Action: The trace state is not changed.


NSQ6406S Storage error creating trace break message area.

Explanation: Storage error occurred for the trace break message when running one of the trace on

commands.

System Action: None. There could be a memory problem. The trace command failed.

Operator Response: Increase the region parameter for the probe’s started task. If the storage

problem continues, contact Nastel support. Provide all messages related to this error from the joblog

and system console.

NSQ6407E Cross memory post error for trace break message.

Explanation: The cross memory post failed when one of the trace on commands was issued.

System Action: None. There could be a system problem. The trace command failed.

Operator Response: Contact Nastel support and provide all relevant messages in the joblog and

system console.



NSQ6410I Command "tttt” entered

Explanation: The text of the command tttt is displayed between double quotes.

tttt- Command text.

System Action: None


NSQ6415E Invalid command

Explanation: The command entered is not supported.

System Action: The command is rejected.

Operator Response: Re-enter the command correctly.

NSQ6421I Tracing for rrrr is turned oooo.

Explanation: Tracing for resource type is turned ON or OFF.


oooo- ON or OFF.

System Action: The probe interceptor generates trace messages of the real MQI intercepted messages

in the SYSOUT file specified as follows:

L – SYSOUT prefix

yy – Year

jjj –Julian date

hh - Hour

Operator Response: To view the trace data, place a ‘?’ by the STC name is SDSF and hit enter.

Select the Lyyjjjhh to view the trace messages.

NSQ6424I Trace is oooo for all resources.

Explanation: The trace command issued requested that all resource types be turned on or off.

oooo – On or off

System Action: The trace option is changed for all resource types.




NSQ6430I DISPLAY DATASPACE

TRANSMITTER nnnn IS USING DATASPACE dddd

MESSAGES RECEIVED: rrrr

MESSAGES SENT: ssss

CURRENT DEPTH: cccc

[TOTAL MESSAGES RECEIVED: xxxx]

[TOTAL MESSAGES SENT: yyyy]

Explanation: Information about the events received and processed by the active transmitter is

displayed.

nnnn – Active transmitter number

dddd – Dataspace name

rrrr – Messages received on the active dataspace

ssss – Messages sent from the active dataspace

cccc – Current depth identifies the number of events received in the active dataspace and not sent

when the “stop send” command is issued or the queue manager was force cancelled.

xxxx – Total number of messages received from all dataspaces should dataspace switching occur.

This message is not displayed if dataspace switching does not occur.

yyyy – Total number of messages sent from all dataspaces should dataspace switching occur.

This message is not displayed if dataspace switching does not occur.

System Action: Messages are displayed when the Display Dataspace command is issued.


NSQ6431I DATASPACE COUNTS RESET

Explanation: All messages received and send counters for all dataspaces are reset to 0.

System Action: Message displayed when the Reset Dataspace command is issued.




NSQ6432I PROBE [ID:pppp USING QMGR:qqqq] IS aaaa

Explanation: The current collection state of the probe. If it is inactive, a subsequent message is

issued indicating the reason for the inactive state.

pppp - Product id to identify the probe


aaaa – Active or inactive

Inactive messages:

tttt NAME/TOKEN PAIR IS NOT FOUND

tttt - Name/token pair

STOP COLLECT COMMAND WAS ISSUED

QMGR qqqq IS NOT RUNNING


TACONN USING QMGR qqqq IS NOT RUNNING


STOP SEND COMMAND WAS ISSUED

System Action: Messages are displayed when the STATUS command is issued.


NSQ6433I DISPLAY DATASPACE DETAIL

DATASPACE XSTATE DSTATE CDEPTH

NSQDSPnnnn xxxx dddd cccc

Explanation: Detailed Information about the status of the dataspace associated with the transmitter

subtask.

nnnn – 2 digit suffix number forming the dataspace name

xxxx – transmitter state

The transmitter state can be Active or Idle.

dddd – dataspace state

The dataspace state can be Empty, Full, or Not Full.

cccc – currentdepth value

This value shows the number of messages residing on the dataspace that have not been

processed by the transmitter subtask.

System Action: Messages are displayed when the Display Dataspace detail command is issued.




NSQ6435I TOTAL [rrrr] COUNTS

[MQCONN: nnnn]

[MQDISC: nnnn]

MQOPEN: nnnn

MQCLOSE: nnnn

MQGET: nnnn

MQPUT: nnnn

MQPUT1: nnnn

MQSET: nnnn

MQINQ: nnnn

MQBACK: nnnn

MQCMIT: nnnn

LOST: nnnn

Explanation: The number of MQ intercepted events received.

rrrr – Resource type

nnnn – Number of events per MQI call

NOTE:

MQCONN and MQDISC are not used in CICS. These messages are not displayed when DISPLAY COUNTS CICS is issued.

System Action: The MQ Counters displayed when the DISPLAY COUNTS command is issued.


NSQ6436I rrrr COUNTERS RESET

Explanation: Counters reset to 0 for the selected resource types

rrrr - batch | CICS | all

System Action: The MQ Counters are reset to 0 when the RESET COUNTS command is issued.


NSQ6800I Command processor stopping.

Explanation: The command processor is starting its shutdown processing.



NSQ6999I Command processor terminated.

Explanation: The command processor subtask has terminated.





CICS Front-end Environmental Messages (7000-7499):

NSQ7000I NSQINIT TM PLTPI program starting.

Explanation: Nastel’s PLTPI program (NSQINIT) is starting.

System Action: None


NSQ7001I NSQINIT TM shutdown TRUE exit NSQTRUES is enabled.

Explanation: The Nastel’s shutdown TRUE exit is enabled.

System Action: When CICS is terminated normally, the NSQTRUES exit will initiate termination

processing of the Nastel collector subtask running in CICS.


NSQ7002I NSQINIT XEIOUT GLUE enabled – NSQGLUEX

NSQ7002I NSQINIT XEIIN GLUE enabled – NSQGLUEX

Explanation: The Nastel’s XEIIN and XEIOUT GLUE exit points enabled.

System Action: When CICS starts up, XEIIN and XEIOUT exits points are enabled allowing

NSQGLUEX to interrogate each EXEC CICS API and SPI command.


NSQ7002I NSQINIT XRMIOUT GLUE enabled – NSQDBRMI

NSQ7002I NSQINIT XRMIN GLUE enabled – NSQDBRMI

Explanation: The Nastel’s XRMIN and XRMIOUT GLUE exit points enabled.

System Action: When CICS starts up, XRMIN and XRMIOUT exits points are enabled allowing

NSQDBRMI to interrogate each EXEC SQL command.


NSQ7005E NSQINIT shutdown TRUE exit NSQTRUES is disabled. EIBRCODE=rrrr.

Explanation: The NSQTRUES shutdown exit is not enabled. The EIB return code is provided.

rrrr- Return code from the EXEC CICS ENABLE PROGRAM API call.

System Action: NSQINIT terminates and the Nastel local environment in the CICS region is not

initialized. CICS MQ collection will not occur.

Operator Response: Refer to IBM’s manual SC34-6233 for additional fault isolation instructions. If

unable to solve the problem, contact Nastel support and provide all relevant error messages.



NSQ7006E NSQINIT aaaa call error. RESP=rrrr RESP2=ssss

Explanation: The NSQINIT startup program issued a CICS API call that failed.

aaaa – The name of the CICS API service.

rrrr - The response error code returned.

ssss – The reason code returned known as resp2



Operator Response: Refer to IBM’s manual SC34-6233 for additional fault isolation instructions. If

unable to solve the problem, contact Nastel support and provide all relevant error messages.

NSQ7009E NSQINIT Program pppp found is not the TM subtask.

Explanation: The NSQINIT startup program started the Nastel XRay interface transaction that is not

configured using program NSQTASK.

pppp – The name of the program started.



Operator Response: Change the program name used for the Nastel XRay interface to NSQTASK.

Restart the CICS region. Refer to the CICS installation instructions.

NSQ7010E NSQINIT Invalid transaction specified.

Explanation: The NSQINIT startup program processed an invalid transaction name on the TR

keyword option specified on the INITPARM statement.



Operator Response: Correct the transaction name specified on the TR keyword. Restart the CICS

region.

NSQ7011E NSQINIT Invalid priority specified.

Explanation: The NSQINIT startup program processed an invalid priority value on the PR keyword

option specified on the INITPARM statement.



Operator Response: Correct the priority value specified on the PR keyword. The Priority value

must be between 0 and 255. Restart the CICS region.



NSQ7020E NSQINIT Unable to ATTACH subtask. RC=rrrr.

Explanation: NSQNIT was unable to create the Nastel subtask.

rrrr- Return code from the ATTACH macro.


initialized.

Operator Response: Refer to IBM’s manual SA22-7609 for additional fault isolation instructions. If

unable to solve the problem, contact Nastel support and supply them with the contents of the error

message.

NSQ7021I NSQINIT Shutdown TRUE exit NSQTRUES is disabled. RESP=rrrr RESP2=ssss.

Explanation: The NSQTRUES exit has been set disabled. The response and reason codes are

provided.

rrrr- Response from EXEC CICS DISABLE command.

ssss- Second response from the EXEC CICS DISABLE command.

System Action: NSQINIT issues this message only if it was unable to create the Nastel subtask.

Operator Response: If the RESP field is non-zero, contact Nastel support. Provide all messages

logged with the error codes from the CICS region that issued this error message.

NSQ7025W NSQINIT processed an invalid INITPARM statement. Processing continues.

Explanation: The CICS subtask encountered an incorrect INITPARM statement. The options are

ignored and the subtask will proceed to initialize.

System Action: The CICS region initializes normally. The default values are used for the CICS

subtask.

Operator Response: Correct the INITPARM statement and restart CICS.

NSQ7026W NSQINIT xxxxxxxx value specified is not valid. xxxxxxxx set to yyy.

Explanation: The xxxxxxxx parameter specified on the INITPARM statement is not valid.

“xxxxxxxx” represents MSGPREFIX, PTO, TTO, CAPX, XEI, XRM, SPI or CPX. “yyy” represents

the default value used.

System Action: The CICS region initializes normally. Default values are used for the CICS sbutask.

Operator Response: Correct the “xxxxxxxx” parameter if you want to override the default value. Refer

to the section, System Initialization Parameters Input Values. Restart CICS.

NSQ7027E NSQINIT QMGR name is missing. Nastel subtask is not initialized.

Explanation: The QM parameter was not specified on the INITPARM statement. The qmgr name is

a required parameter.



Operator Response: Add the QM keyword on the INITPARM statement. Restart the CICS region.



NSQ7028E NSQINIT subtask initialization failed. RC=rrrr.

Explanation: The Nastel subtask failed to initialize.

rrrr- Return code from NSQINIT subtask.

System Action: CICS MQ events will not be intercepted.

Operator Response: Refer to the previous NSQ messages leading up to this error message to

determine the cause of the error. If you cannot resolve this problem, contact Nastel support.

NSQ7029E NSQINIT QMGR name is invalid. Nastel subtask is not initialized.

Explanation: The qmgr name specified for the QM keyword on the INITPARM statement is invalid.



Operator Response: Correct the qmgr name on the QM keyword. Restart the CICS region.

NSQ7030I NSQINIT TM subtask is initialized.

Explanation: The Nastel subtask is running.

System Action: None


NSQ7034I NSQINIT Invalid keyword kkkk processed. Keyword ignored.

Explanation: The keyword specified on the INITPARM statement is not supported.

kkkk- Keyword specified

System Action: The keyword is ignored.

Operator Response: Correct the keyword or remove it from the INITPARM statement.

NSQ7040S NSQINIT Unable to load NTUFMT.

Explanation: NSQNIT cannot find utility module NTUFMT.

System Action: NSQINIT terminates and the Nastel environment is not set up. No capture of MQ

calls will occur.

Operator Response: The module NTUFMT is missing from the library HLQ.MLQ.LOAD. Re-install

the load library.

NSQ7099I NSQINIT TM PLTPI program ended.

Explanation: NSQINIT is terminating.



NSQ7100I NSQTASK subtask starting.

Explanation: Nastel’s CICS subtask is starting.





NSQ7102S NSQTASK Unable to load mmmm. Subtask is terminating.

Explanation: The subtask cannot load the target module. This may be the result of an installation

error.

mmmm – Load module name

System Action: The subtask is terminated.

Operator Response: Make sure the target module resides in the Nastel’s load library. Contact Nastel

support if you cannot resolve this issue.

NSQ7104S NSQTASK Error establishing estaex service. RC= rrrr. Subtask is terminating.

Explanation: The Estaex service failed to establish the retry routine.

rrrr - Return code from estaex service.

System Action: The CICS subtask is terminated.


NSQ7105S NSQTASK Unable to allocate SYSOUT file NASTEL. Error=eeee Info=iiii.

Explanation: There was a problem allocating Nastel’s SYSOUT dataset in the CICS region.

eeee- Dynalloc error code.

iiii- Dynalloc information code.

System Action: The subtask comes down and CICS MQ messages will not be intercepted.

Operator Response: Refer to IBM manual SA22-7608. If unable to solve the problem, contact

Nastel support and supply them with the contents of this message.

NSQ7106S NSQTASK Unable to open SYSOUT file NASTEL. RC=rrrr.

Explanation: The subtask could not open the SYSOUT file named NASTEL.

rrrr- Return code from the OPEN call.


Operator Response: Refer to IBM manual SC46-7408. If unable to solve the problem, contact


NSQ7107S NSQTASK Unable to unallocate SYSOUT file NASTEL. Error= eeee Info=iiii.

Explanation: The subtask could not deallocate the SYSOUT dataset named NASTEL.

eeee- Dynalloc error code.

iiii- Dynalloc information code.

System Action: None. The subtask was terminating.

Operator Response: Refer to IBM manual SA22-7608. If unable to solve the problem, contact




NSQ7108S NSQTASK subtask abended with aaaa.

Explanation: The subtask abended with the abend code identified in aaaa.

aaaa- Abend code

System Action: The CICS subtask is terminated.

Operator Response: Refer to the IBM MVS System Codes manual for further information regarding

the identified abend. If unable to solve the problem, contact Nastel support and supply them with the

contents of this message.

NSQ7135I NSQTASK cross memory environment does not exist.

Explanation: The CICS region is started before the Nastel name/token pair is created in CSA.

System Action: The CICS region will initialize. The Nastel CICS subtask will retry every 10

seconds checking for the cross memory environment to be installed.

Operator Response: Refer to message NSQ7138I. Start the probe, which will create the Nastel

name/token pair.

NSQ7136W NSQINIT probe is not running.

Explanation: During CICS startup when the Nastel subtask is initializing, the subtask found the

name/token pair but the probe task was not running.

System Action: No CICS MQ transaction message interception will occur. The Nastel subtask

running in the CICS region will check the cross memory environment using the TIMEOUT value for

the probe to be started. After the probe is started, message collection will become active after the

next TIMEOUT dispatched cycle.

The Nastel subtask will create new alets for each dataspace that is accessible to the CICS region.

Operator Response: Start the probe.

NSQ7137I NSQTASK probe using [qmgr qqqq | pid pppp] is not running.

Explanation: The CICS subtask found the cross memory environment, but there is no probe running

that is using qmgr qqqq or pid pppp.

qqqq - qmgr

pppp – Unique probe identifier

System Action: The CICS subtask will retry using the TIMEOUT value provided on the INITPARM

statement checking for the probe running with the matching qmgr name or pid. If the TIMEOUT

parameter is not used, the default value of 60 seconds is used.

Operator Response: Start the probe configured with the qmgr name or prodid name that the CICS

region is using. (Refer to section, Change ProdID Parameter Consideration.)



NSQ7138I NSQTASK subtask will check for the probe using [qmgr qqqq | pid pppp] every 10 seconds.

Explanation: The CICS subtask will retry every 10 seconds checking for the cross memory

environment using either the qmgr name or probe id.

qqqq – qmgr

pppp – Unique probe identifier

System Action: The CICS subtask will continue retrying every 10 seconds attempting to check for

the probe’s cross memory environment using either a matching qmgr name or proid.

Operator Response: Start the probe. (Refer to message NSQ7137I.)

NSQ7139I NSQTASK kkkk=vvvv.

Explanation: The Nastel XRay subtask was started using the specified keyword value.

kkkk – keyword value

vvvv – The option specified for the keyword.

System Action: None


NSQ7148I NSQTASK no match on PID or QMGR. Please check your NSQINIT= parms.

Explanation: The subtask could not identify a probe with a matching PID or QMGR name.

Sytem Action: The CICS subtask will retry using the TIMEOUT value provided on the INITPARM

statement checking for the probe running with the matching QMGR name or PID. If the TIMEOUT

parameter is not used, the default value of 60 seconds is used.

Operator Response: Refer to operator response for message NSQ7137I.

NSQ7150S NSQTASK Unable to create the local environment. RC=rrrr.

Explanation: The subtask could not create the CICS local environment.

rrrr- Return code from the create token service.

System Action: The subtask is terminated.

Operator Response: Contact Nastel support with the contents of this error message.

NSQ7151I NSQTASK local environment created. CGA= aaaa.

Explanation: The subtask created Nastel’s local environment in the CICS region. The CGA address

displayed points to this environment area.

aaaa- CGA address.

System Action: None




NSQ7152I NSQTASK cross memory environment is found. STCK=ssss.

Explanation: The subtask found the cross-memory environment that was created.

ssss- STCK value when the probe created the cross memory areas.

System Action: None


NSQ7153I NSQTASK trnq entries deleted.

Explanation: The CICS Nastel XRay subtask interface is informing the user that any trnq entries

existing in the queuename table are deleted during termination of the Nastel XRay subtask

transaction.

System Action: None


NSQ7154I NSQTASK aaaa deleted.

Explanation: The CICS Nastel XRay subtask interface was stopped. The control block storage area

is deleted.

aaaa – The identifier of the storage area that is deleted.

System Action: None


NSQ7155I NSQTASK cross memory environment is recreated. STCK=ssss.

Explanation: The subtask found a new cross-memory environment area. The old one was deleted.

ssss- STCK value when the probe recreated the cross memory area.

System Action: None


NSQ7156I NSQTASK cross memory environment deleted.

Explanation: The subtask found that the cross-memory environment was deleted. No capture of

CICS information can occur until a new cross-memory environment is recreated.

System Action: None


NSQ7157I NSQTASK jjjj is using [qmgr qqqq | uid uuuu].

Explanation: The CICS region is sending messages to the probe using the specified uid.

jjjj - CICS jobname

qqqq - qmgr

uuuu - Unique identifier

System Action: None




NSQ7158I NSQTRANC MQ counts reset

Explanation: The user issued the NSTM RESET transaction requesting all the collection counters to

be reset.

System Action: All CICS MQ counters are reset to 0.


NSQ7159I NSQTRANC No monitored transactions

Explanation: The CICS transaction command STATUS TRNQ was issued and found no active

transactions that are currently used by the API crossing exit.

System Action: None


NSQ7160I NSQTASK probe is running.

Explanation: The CICS subtask transaction is running.

System Action: None


NSQ7188I NSQTRANC Monitored transactions on QMGR qqqq: nnnn

Explanation: The CICS transaction command STATUS TRNQ was issued and found active

transactions that are currently used by the API crossing exit.

qqqq – queue manager

nnnn – the number of transactions monitored by the CICS API crossing exit

System Action: None


NSQ7162I NSQTASK collection interface is enabled.

Explanation: The CICS interface to the crossing exit is available for MQ event collection.

System Action: None


NSQ7163I NSQTASK collection interface is disabled.

Explanation: The CICS interface to the crossing exit is not available for MQ event collection.

System Action: None


NSQ7164I NSQTRANC MQ capture [already] started.

Explanation: The user issued the NSTM START transaction in the CICS region.

System Action: The CICS MQ interface is ready to intercept the MQI calls.




NSQ7165I NSQTRANC MQ capture [already] stopped

Explanation: The user issued the NSTM STOP transaction in the CICS region.

System Action: The CICS MQ interface is disabled and will not intercept the MQI calls.


NSQ7166E NSQTRANC Invalid command entered

Explanation: The transaction command entered is not supported.

System Action: The transaction entered is not processed.

Operator Response: Correct the transaction and try it again.

NSQ7167E NSQTRANC Invalid request type for command

Explanation: The request type entered in the transaction is not MQ.

System Action: The transaction entered is not processed.

Operator Response: Correct the transaction and try it again.

NSQ7168I NSQTRANC MQ collection is dddd

Explanation: The user issued the NSTM STATUS transaction in the CICS region.


System Action: This message is issued displaying the current state of the collection interface within

the CICS region.


NSQ7169E NSQTRANC TM-CICS transaction is not active

Explanation: There is no environment established in the CICS region.

System Action: None

Operator Response: Contact Nastel support. Provide the CICS joblog and the Nastel messages

residing in the Nastel sysout file.

NSQ7171I NSQTRANC TM transaction [stopping | already stopped]

Explanation: The user issued the CICS TM STOP command to terminate the Nastel XRay

transaction.

System Action: None


NSQ7180I NSQTASK CSTA at aaaa is created for probe using id iiii

Explanation: A CSTA block was created at address aaaa using probe configured with product id iiii.

aaaa- CSTA address.

iiii- Probe product id.

System Action: None




NSQ7185I NSQTASK ALET aaaa is created for STOKEN ssss for DDB at dddd

Explanation: An ALET was placed in the PASN-AL access list of the CICS region for the dataspace

associated with the DDB.

aaaa- ALET

ssss- STOKEN of the dataspace.

dddd- Address of the DDB for the dataspace.

System Action: None


NSQ7186E NSQTASK ALESERV error on STOKEN ssss for DDB dddd. RC=rrrr

Explanation: The subtask was unable to create an ALET for the dataspace token.

ssss- STOKEN of the dataspace.

dddd- Address of the DDB for the dataspace.

rrrr- Return code from the ALESERV service.


Operator Response: Contact Nastel support with the contents of this error message.

NSQ7190I NSQTASK ALET aaaa deleted. RC=rrrr

Explanation: The ALET was deleted.

aaaa- ALET.

rrrr- Return code from the ALESERV service.

System Action: None


NSQ7295I NSQTASK User issued NSTM TM STOP request received

Explanation: A user issued the TM STOP command to request the Nastel XRay transaction to

terminate.



NSQ7296I NSQTASK FORCEPURGE issued

Explanation: The CICS Nastel XRay transaction was terminated with a forcepurge request in the

CICS region.



NSQ7297I NSQTASK shutdown request received

Explanation: The CICS Nastel XRay transaction is terminating because the CICS region is stopping.





NSQ7298I NSQTASK subtask ended ssss

Explanation: The CICS Nastel XRay transaction ended with a general state ssss.

ssss – normally | abnormally

System Action: None


NSQ7299I NSQTASK subtask ended

Explanation: The CICS subtask is terminated.



Utility Messages (7500-7599)

NSQ7540E DUMPCOM unable to open SYSPRINT

Explanation: The sysprint ddname is not specified in the dumpcom JCL utility.

System Action: The formatted dump messages are written to ddname sysprint. This ddname is

required.

Operator Response: Add the sysprint DD statement to the dumpcom JCL utility and resubmit the job.

NSQ7541I tttt Name/token pair deleted

Explanation: The DUMPCOM or DELETENT utility removed the name/token pair from CSA.

tttt – Name/token pair


Operator Response: None. Restarting the probe will reinstate the name/token pair.

NSQ7542S Unable to delete tttt name/token pair

Explanation: The name/token service failed.


System Action: The name/token pair z/OS service failed.

Operator Response: Contact Nastel support

NSQ7543I tttt name/token pair is not found.

Explanation: The name/token pair is not found when running any of the Nastel system utilities:

DUMPCOM, FREECOM, or DELETENT.


System Action: No action taken by the submitted utility.




NSQ7550I PTBL block removed from CSA.

Explanation: The DELETENT utility successfully removed the PTBL control block.


Operator Response: None. Restarting the probe will recreate the PTBL control block.

NSQ7551I PAB block removed from CSA.

Explanation: The DELETENT utility successfully removed the PAB control block.


Operator Response: None. Restarting the probe will recreate the PAB control block.

NSQ7553E Unable to load IEANTRT module

Explanation: The z/OS token service IEANTRT module is not available. This is a possible system

problem.

System Action: The utility submitted failed.


NSQ7554E Unable to load IEANTDL module

Explanation: The token service IEANTDL module is not available. This is a possible system

problem.

System Action: The utility submitted failed.


NSQ7555I CICS STUB MODULE AT A7F40019 LENGTH=0256 DELETED

Explanation: The DELETENT utility successfully deleted the CICS stub module from (ecsa)

subpool 245.

System Action: None


NSQ7556I CHECKING FOR ACTIVE PROBES

Explanation: The FREECOM or DELETENT utility is checking for any probes that may be running.

System action: None

Operator response: None

NSQ7557I NO ACTIVE PROBES FOUND

Explanation: The FREECOM or DELETENT utility did not find any probes running.

System action: None




NSQ7558I PROBE jjjj iiii USING QMGR=qqqq IS RUNNING

Explanation: The FREECOM or DELETENT utility found the probe associated with jobname jjjj

and job identifier iiii running.

jjjj - Jobname

iiii - Jobid

qqqq - qmgr

System action: None


NSQ7559I PROBES FOUND RUNNING. NASTEL COMMON STORAGE IS NOT DELETED

Explanation: The DELETENT utility found at least one probe running. The DELETENT utility will

not release the Nastel common storage area and name/token pair while any probe is active on the

system.

System action: None

Operator response: Stop all probes that are identified in message NSQ7558I. Rerun the

DELETENT utility.

NSQ7560I PROBES FOUND RUNNING. NASTEL NAME/TOKEN PAIR IS NOT DELETED

Explanation: The FREECOM utility found at least one probe running. The FREECOM utility will

not delete the name/token pair while any probe is active on the system.

System action: none

Operator response: Stop all probes that are identified in message NSQ7558I. Rerun the FREECOM

utility.

Front-end Environmental Messages (8000-8400):

NSQ8000T BATCH CAPTURE STARTING FOR jjjj:iiii

Explanation: The trace message identifying the start of events collected for jobname jjjj running

under jobid iiii.

jjjj – Jobname

iiii - Jobid

System Action: None


NSQ8001E Batch front-end module mmmm could not be loaded.

Explanation: The batch front-end module could not be loaded.

mmmm- Module name

System Action: Batch data capture for MQ messages will not occur.

Operator Response: Make sure that the front-end module mmmm has been properly installed. It is

used as part of the batch collection process.



NSQ8010T rrrr TRACE IS oooo.

Explanation: The trace command was issued requesting to trace the specific resource type.


oooo – On or off

System Action: The trace is enabled or disabled for the specified resource type. When enabled, a

snapshot of the intercept message is written to the trace sysout file.


NSQ8011T TRACE IS oooo FOR ALL RESOURCES

Explanation: The trace all command was issued requesting to turn on or off tracing for all resource

types.

oooo – On or off

System Action: The trace is enabled or disabled for all resource types. When enabled a snapshot of

the message received is written to the trace sysout file.


NSQ8021T B jjjj(iiii) ssss-nnnn XSTK:yyyy

Explanation: The source of the batch MQCONN call is displayed (part 1). This message appears in

the probe sysout file Lyyjjjhh.

B – Batch trace record.

jjjj- Jobname.

iiii- Jobid.

ssss- Step name.

nnnn - Step number.

yyyy - Execution start time in STCK format.

System Action: None

Operator Response: Refer to message NSQ6421I for details on the trace log file.

NSQ8022T CONNECT CONNH:hhhh QMGR:qqqq CC:cccc RSN:rrrr ODSP:oooo.

Explanation: MQCONN information is displayed (part 2). This message appears in the probe sysout

file Lyyjjjhh.

hhhh- Connection handle.

qqqq- Queue manager.



oooo- Offset in hexadecimal in the dataspace of the captured MQ contextual data.

System Action: None





Explanation: The source of the batch MQDISC call is displayed (part 1). This message appears in



jjjj- Jobname.

iiii- Jobid.

ssss- Step name.

nnnn- Step number.

yyyy- Execution start time in STCK format.

System Action: None


NSQ8024T DISCONNECT CONNH:hhhh CC:cccc RSN rrrr ODSP:oooo.

Explanation: MQDISC information is displayed (part 2). This message appears in the probe sysout

file Lyyjjjhh.





System Action: None



Explanation: The source of the batch MQOPEN call is displayed (part 1). This message appears in

the probe sysout file Lyyjjjhh


jjjj- Jobname.

iiii- Jobid.

ssss- Step name.

nnnn - Step number.

yyyy- Execution start time in STCK format.





NSQ8026T OPEN CONNH:hhhh OBJN:nnnn OBJH:bbbb CC:cccc RSN: rrrr ODSP: oooo.

Explanation: MQOPEN information is displayed (part 2). This message appears in the probe sysout

file Lyyjjjhh.


nnnn- Object name.

bbbb- Object handle.







Explanation: The source of the batch MQCLOSE call is displayed (part 1). This message appears in



jjjj- Jobname.

iiii- Jobid.

ssss- Step name.

nnnn - Step number.

yyyy - Execution start time in STCK format.

System Action: None


NSQ8028T CLOSE CONNH:hhhh OBJN:nnnn OBJH:bbbb RC:cccc RSN:rrrr ODSP: oooo.

Explanation: MQCLOSE information is displayed (part 2). This message appears in the probe

sysout file Lyyjjjhh.


nnnn- Object name

bbbb- Object handle

cccc- Completion code in decimal

rrrr- Reason code in decimal


System Action: None





Explanation: The source of the batch MQGET call is displayed (part 1). This message appears in the

probe sysout file Lyyjjjhh.

B – Batch trace record

jjjj- Jobname

iiii- Jobid

ssss- Step name

nnnn - Step number

yyyy - Execution start time in STCK format

System Action: None


NSQ8030T GET CONNH:hhhh OBJH:bbbb LEN:llll [RLEN:mmmm] CC:cccc RSN:rrrr ODSP: oooo.

Explanation: MQGET information is displayed (part 2). This message appears in the probe sysout

file Lyyjjjhh.


bbbb- Object handle

llll – message length of the contextual message received. If truncation occurs, the length

represents the actual size received.

mmmm- If the message received is truncated, this value indicates the returned data length value of

the actual size of the message. If the message is not truncated, this value is not displayed.




System Action: None



Explanation: The source of the batch MQPUT call is displayed (part 1). This message appears in the



jjjj- Jobname

iiii- Jobid

ssss- Step name

nnnn - Step number


System Action: None




NSQ8032T PUT CONNH:hhhh OBJH:bbbb LEN:llll CC:cccc RSN:rrrr ODSP: oooo.

Explanation: MQPUT information is displayed (part 2). This message appears in the probe sysout

file Lyyjjjhh.


bbbb- Object handle

llll – Length of contextual message




System Action: None



Explanation: The source of the batch MQPUT1 call is displayed (part 1). This message appears in



jjjj- Jobname

iiii- Jobid

ssss- Step name

nnnn - Step number

yyyy - Execution start time in stcl format

System Action: None


NSQ8034T PUT1 CONNH:hhhh OBJH:bbbb LEN:llll CC:cccc RSN:rrrr ODSP: oooo.

Explanation: MQPUT1 information is displayed (part 2). This message appears in the probe sysout

file Lyyjjjhh.


bbbb- Object handle

llll – Length of contextual message




System Action: None





Explanation: The source of the batch MQSET call is displayed (part 1). This message appears in the



jjjj- Jobname

iiii- Jobid

ssss- Step name

nnnn - Step number

yyyy - Execution start time in stcl format

System Action: None


NSQ8036T SET CONNH:hhhh OBJH:bbbb RC:cccc RSN:rrrr ODSP: oooo.

Explanation: MQSET information is displayed (part 2). This message appears in the probe sysout

file Lyyjjjhh.


bbbb- Object handle




System Action: None



Explanation: The source of the batch MQINQ call is displayed (part 1). This message appears in the



jjjj- Jobname

iiii- Jobid

ssss- Step name

nnnn - Step number


System Action: None




NSQ8038T INQUIRE CONNH:hhhh OBJH:bbbb RC:cccc RSN:rrrr ODSP: oooo.

Explanation: MQINQ information is displayed (part 2). This message appears in the probe sysout

file Lyyjjjhh.


bbbb- Object handle




System Action: None



Explanation: The source of the batch MQBACK call is displayed (part 1). This message appears in


jjjj- Jobname

iiii- Jobid

ssss- Step name

nnnn - Step number


System Action: None


NSQ8040T ROLLBACK CONNH: hhhh RC:cccc RSN:rrrr ODSP: oooo.

Explanation: MQBACK information is displayed (part 2). This message appears in the probe sysout

file Lyyjjjhh.





System Action: None





Explanation: The source of the batch MQCMIT call is displayed (part 1). This message appears in



jjjj- Jobname

iiii- Jobid

ssss- Step name

nnnn - Step number


System Action: None


NSQ8042T COMMIT CONNH:hhhh RC:cccc RSN:rrrr ODSP: oooo.

Explanation: MQCMIT information is displayed (part 2). This message appears in the probe sysout.





System Action: None


NSQ8100T BATCH CAPTURE TERMINATING FOR jjjj:iiii

Explanation: The last trace message identifying the end of events collected for jobname jjjj running

under jobid iiii.

jjjj – Jobname

iiii - Jobid

System Action: None


NSQ8200T CICS CAPTURE STARTING FOR tttt:iiii

Explanation: The trace message identifying start of the MQ message calls for the CICS transaction.

tttt – Transaction name

iiii – Transaction identifier

System Action: None




NSQ8202T C jjjj(iiii) TRAN:nnnn TRID:tttt XSTK:yyyy

Explanation: The source of the CICS MQOPEN call is displayed (part 1). This message appears in


C – CICS trace record

jjjj- CICS jobname

iiii- CICS jobid

nnnn – Transaction name

tttt – Transaction identifier


System Action: None


NSQ8203T OPEN QMGR:qqqq OBJN:NONE OBJH:bbbb CC:cccc RSN:rrrr ODSP:oooo

Explanation: MQOPEN information is displayed (part 2). This message appears in the probe sysout

file Lyyjjjhh.

qqqq- Queue manager

bbbb – Object handle




System Action: None



Explanation: The source of the CICS MQCLOSE call is displayed (part 1). This message appears in



jjjj- CICS jobname

iiii- CICS jobid




System Action: None




NSQ8205T CLOSE QMGR:qqqq OBJH:bbbb CC:cccc RSN:rrrr ODSP:oooo

Explanation: MQCLOSE information is displayed (part 2). This message appears in the probe

sysout file Lyyjjjhh.

qqqq- Queue manager








Explanation: The source of the CICS MQGET call is displayed (part 1). This message appears in the



jjjj – CICS jobname

iiii – CICS jobid



yyyy – Execution start time in STCK format

System Action: None


NSQ8207T GET QMGR:qqqq OBJN:oooo OBJH:bbbb LEN:llll [RLEN:mmmm] CC:cccc RSN:rrrr

ODSP:oooo

Explanation: MQGET information is displayed (part 2). This message appears in the probe sysout

file Lyyjjjhh.


oooo – Object name


llll – message length of the contextual message received. If truncation occurs, the length represents

the actual size received.

mmmm – If the message received is truncated, this value indicates the returned data length value

of the actual size of the message. If the message is not truncated, this value is not displayed.

cccc – Completion code in decimal

rrrr – Reason code in decimal

oooo – Offset in hexadecimal in the dataspace of the captured MQ contextual data.

System Action: None





Explanation: The source of the CICS MQPUT call is displayed (part 1). This message appears in the




iiii – CICS jobid




System Action: None


NSQ8209T PUT QMGR:qqqq OBJN:oooo OBJH:bbbb LEN:llll CC:cccc RSN:rrrr ODSP:oooo

Explanation: MQPUT information is displayed (part 2). This message appears in the probe sysout

file Lyyjjjhh.




llll – Message length




System Action: None



Explanation: The source of the CICS MQPUT1 call is displayed (part 1). This message appears in




iiii – CICS jobid




System Action: None




NSQ8211T PUT1 OBJN:oooo LEN:llll CC:cccc RSN:rrrr ODSP:oooo

Explanation: MQPUT1 information is displayed (part 2). This message appears in the probe sysout

file Lyyjjjhh.


llll – Message length




System Action: None



Explanation: The source of the CICS MQSET call is displayed (part 1). This message appears in the




iiii – CICS jobid




System Action: None


NSQ8213T SET QMGR:qqqq OBJN:oooo OBJH:bbbb CC:cccc RSN:rrrr ODSP:oooo

Explanation: MQSET information is displayed (part 2). This message appears in the probe sysout

file Lyyjjjhh.







System Action: None





Explanation: The source of the CICS MQINQ call is displayed (part 1). This message appears in the




iiii – CICS jobid




System Action: None


NSQ8215T INQUIRE QMGR:qqqq OBJN:oooo OBJH:bbbb CC:cccc RSN:rrrr ODSP:oooo

Explanation: MQINQ information is displayed (part 2). This message appears in the probe sysout

file Lyyjjjhh.







System Action: None



Explanation: The source of the CICS MQCMIT call is displayed (part 1). This message appears in




iiii – CICS jobid




System Action: None




NSQ8217T COMMIT CC:cccc RSN:rrrr ODSP:oooo

Explanation: MQCMIT information is displayed (part 2). This message appears in the probe sysout

file Lyyjjjhh.




System Action: None



Explanation: The source of the CICS MQBACK call is displayed (part 1). This message appears in




iiii – CICS jobid




System Action: None


NSQ8219T ROLLBACK CC:cccc RSN:rrrr ODSP:oooo

Explanation: MQBACK information is displayed (part 2). This message appears in the probe sysout

file Lyyjjjhh.




System Action: None


NSQ8300T CICS CAPTURE TERMINATING FOR tttt:iiii

Explanation: The trace message identifying end of MQ message calls for the CICS transaction.

tttt – Transaction name

iiii – Transaction identifier

System Action: None




NSQ9999E ppppppp ABENDED IN jjjjjjjj AT OFFSET oooooooo CC cccccccc RSN rrrrrrrr

Explanation: Abnormal termination occurred. This error message appears in the probe sysout file

Lyyjjhh.

pppppppp – Nastel program name

jjjjjjjj – CICS job name

oooooooo – Hexadecimal offset in program of where ABEND occurred

cccccccc – Abend code. Example: S0C4 would show up as CC 00000004

rrrrrrrr – Reason code. Example: S0C4-10 would show up as RSN 00000010

System Action: Nastel handles the abnormal termination and continues normal program operation

without further interruption.

Operator Response: Send NSQ9999E message(s) to your Nastel customer service representative.

Nastel XRay Probes for z/OS Appendix A: References


Appendix A: References

A.1 Nastel Documentation

Table A-1. Nastel Documentation

Document Number (or higher)

Title

XRUG1.05 Nastel XRay User’s Guide

XRIG15.004 Nastel XRay Installation Guide

JKQLUG12.002 jKool Query Language (jKQL) Reference Guide

XR/MQ 100.001 Nastel XRay Express for IBM MQ Tracing - Docker Version

XR/KF 100.002 Nastel XRay Express for Kafka - Docker Version

A.2 Nastel SAMP Library Cross Reference

CSQ4B100 - Nastel template member used for CICS MQ Adapter definitions. Nastel Technologies

does not ship the CICS MQ adapter. The CICS definitions can be found in the MQ

library SCSQPROC.

CSQ4INYG - Nastel definitions used to create the CICS INIT QUEUE.

DFHPLT - The PLT definitions required generating module DFHPLTTM. This is used for

initializing the Nastel-CICS environment during startup.

INITPARM - Provides our sample INITPARM statement for a CICS region.

NASTDEFS - Provides the CICS definitions for the CSD to create the NSTM transaction.

TAMQSC - Nastel Queue definitions

TICONFIG - Probe configuration member.

https://customers.nastel.com/hc/en-us/articles/360033617134-Nastel-XRay-Documentation-Library





Appendix A: References Nastel XRay Probes for z/OS


A.3 Nastel JCL Library Cross Reference

$INST - High level Instructions on installing the Nastel batch support

$CIINST - High level Instructions on installing the Nastel CICS support

ALOCAUTH - Create the Nastel IBM MQ front-end modules

CSQ4B100 - Sample JCL to install the CICS MQ adapter

CSQ4INYG - Sample JCL to create the CICS INIT QUEUE

*DELETENT - Remove the Nastel Environment and delete CSA storage areas

DRVAG - MQGET

DRVAP - MQPUT

DRVAP3 - All API Calls

DUMPCOM - Dump the Nastel CSA Areas

*FREECOM - Remove the Nastel Environment

MQDEFQ - Sample job to create the Nastel MQ Queues

NASTDEFS - Sample JCL to install the Nastel CICS transaction NSTM and bmsmap.

NASTQUES - Sample JCL to create the Nastel MQ Queues.

NSCBRK - Sample Client Broker Application

NSGET - Sample MQGET Application

NSPUT - Sample MQPUT Application

NSQTI - Probe JCL procedure

NSRPL - Sample Reply Application

TRANSGET - Sample Purchase Order Application

TRANSPUT - Sample Put Messages Application

UTLMTQ - Sample JCL to empty a queue

UTLPRTQ - Sample JCL to printout a queue contents

*WAITB - Force a wait whereby a dump can be taken of the address space.

*WAITBM - Force a wait after opening dynamic queues whereby a dump can be taken of the address

space and/or queue manager.

* only use if directed by Nastel Support

Nastel XRay Probes for z/OS Appendix B: Conventions


Appendix B: Conventions

B.1 Typographical Conventions

Table B-1. Typographical Conventions

Convention Description

Blue/Underlined Used to identify links to referenced material or websites.

Example: [email protected]

Bold Print

Used to identify topical headings, glossary entries, and toggles

or buttons used in procedural steps.

Example: Click EXIT.

Italic Print Used to place emphasis on titles, menus, screen names, user

inputs, or other categories.

Monospaced Bold Used to identify keystrokes/data entries, file names, directory

names, etc.

Monospaced Italic

Used to identify variables in an address location.

Example: [AutoPilot_Home]\documents, where the

portion of the address within the brackets [ ] is variable.

Monospaced Text Used to identify addresses, commands, scripts, etc.

Normal Text Typically used for general text throughout the document.

Table Text

Table text is generally a smaller size to conserve space. 10, 9,

and 8 point type are used in tables throughout the AutoPilot

M6 product family of documents.

../../../QA/Documents%20and%20Settings/lclancy/Local%20Settings/Temporary%20Internet%20Files/Local%20Settings/Temporary%20Internet%20Files/Local%20Settings/Documents%20and%20Settings/Documents%20and%20Settings/tmiller/Application%20Data/tmiller/Local%20Settings/Temporary%20Internet%20Files/L

Appendix B: Conventions Nastel XRay Probes for z/OS



Nastel XRay Probes for z/OS Appendix C: EXEC CICS Groups and Commands


Appendix C: EXEC CICS Groups and Commands

C.1 EXEC CICS Groups

Table C-1. EXEC CICS Groups

Group # Group Name

02 ENVIRONMENT

04 TERMINAL

06 FILE

08 TRANSIENT

0A TEMPORARY

0E PROGRAM

0C STORAGE

10 INTERVAL

12 TASK12

14 JOURNALING

16 SYNCPOINT

18 BMS

1C DUMP1C

1E BATCH

20 BTS20

22 BTS22

34 BTS34

36 BTS36

38 WEB

3C DOCUMENT

3E EXTRACT

48 DIAGNOSTIC

4A INTERVAL

56 SPOOL

5E TASK5E

6A SECURITY

6C CONSOLE

74 AUTHENTICATION

7E DUMP7E

Appendix C: EXEC CICS Groups and Commands Nastel XRay Probes for z/OS


C.2 EXEC CICS Commands (Currently API Only

Commands)

Table C-2. EXEC CICS Commands

Command # Command Name

0202 ADDRESS

0200 HANDLE_CONDITION

0206 HANDLE_AID

0208 ASSIGN

020A IGNORE_CONDITION

020C PUSH

020E POP

0210 ADDRESS SET

0402 RECEIVE

0404 SEND

0406 CONVERSE

0408 ISSUE_EODS

040A ISSUE_COPY

040C WAIT_TERMINAL

040E ISSUE_LOAD

0410 WAIT_SIGNAL

0412 ISSUE_RESET

0414 ISSUE_DISCONNECT

0416 ISSUE_ENDOUTPUT

0418 ISSUE_ERASEUP

041A ISSUE_ENDFILE

041C ISSUE_PRINT

041E ISSUE_SIGNAL

0420 ALLOCATE

0422 FREE

0424 POINT

0426 BUILD_ATTACH

0428 EXTRACT_ATTACH

042A EXTRACT_TCT

042C WAIT_CONVID

042E EXTRACT_PROCESS

0430 ISSUE_ABEND

0432 CONNECT_PROCESS





0434 ISSUE_CONFIRMATION

0436 ISSUE_ERROR

0438 ISSUE_PREPARE

043A ISSUE_PASS

043C EXTRACT_LOGONMSG

043E EXTRACT_ATTRIBUTES

0602 READ

0604 WRITE

0606 REWRITE

0608 DELETE

060A UNLOCK

060C STARTBR

060E READNEXT

0610 READPREV

0612 ENDBR

0614 RESETBR

0802 WRITEQ_TD

0804 READQ_TD

0806 DELETEQ_TD

0A02 WRITEQ_TS

0A04 READQ_TS

0A06 DELETEQ_TS

0C02 GETMAIN

0C04 FREEMAIN

0E02 LINK

0E04 XCTL

0E06 LOAD

0E08 RETURN

0E0A RELEASE

0E0C ABEND

0E0E HANDLE_ABEND

1002 ASKTIME

1004 DELAY

1006 POST

1008 START

1008 START_ATTACH

1008 START_BREXIT





100A RETRIEVE

100C CANCEL

1202 WAIT_EVENT

1204 ENQ

1206 DEQ

1208 SUSPEND

1402 WRITE_JOURNAL

1404 WAIT_JOURNAL

1406 WRITE_JOURNALNAME

1408 WAIT_JOURNALNAME

1602 SYNCPOINT

1602 SYNCPOINT_ROLLBACK

1604 RESYNC

1802 RECEIVE_MAP

1804 SEND_MAP

1806 SEND_TEXT

1808 SEND_PAGE

180A PURGE_MESSAGE

180C ROUTE

180E RECEIVE_PARTN

1810 SEND_PARTNSET

1812 SEND_CONTROL

1C02 DUMP

1E02 ISSUE_ADD

1E04 ISSUE_ERASE

1E06 ISSUE_REPLACE

1E08 ISSUE_ABORT

1E0A ISSUE_QUERY

1E0C ISSUE_END

1E0E ISSUE_RECEIVE

1E10 ISSUE_NOTE

1E12 ISSUE_WAIT

1E14 ISSUE_SEND

2002 BIF_DEEDIT

2004 DEFINE_COUNTER

2006 GET_COUNTER

2008 UPDATE_COUNTER





200A DELETE_COUNTER

200C REWIND_COUNTER

200E QUERY_COUNTER

2014 DEFINE_DCOUNTER

2016 GET_DCOUNTER

2018 UPDATE_DCOUNTER

201A DELETE_DCOUNTER

201C REWIND_DCOUNTER

201E QUERY_DCOUNTER

2202 EXIT_ENABLE

2204 EXIT_DISABLE

2206 EXIT_EXTRACT

3402 DEFINE_ACTIVITY

3404 DEFINE_PROCESS

3406 RUN_ACTIVITY

3408 RUN_ACQPROCESS

340E ACQUIRE_PROCESS

3410 ACQUIRE_ACTIVITYID

3412 DELETE_CONTAINER

3414 GET_CONTAINER

3416 PUT_CONTAINER

3418 RESET_ACTIVITY

341A CHECK_ACTIVITY

341C CANCEL_ACTIVITY

341E CANCEL_ACQPROCESS

3420 SUSPEND_ACTIVITY

3422 SUSPEND_ACQPROCESS

3424 RESUME_ACTIVITY

3426 RESUME_ACQPROCESS

3428 DELETE_ACTIVITY

342A LINK_ACQPROCESS

342C LINK_ACTIVITY

342E CANCEL_ACQACTIVITY

3430 RUN_ACQACTIVITY

3432 LINK_ACQACTIVITY

3434 SUSPEND_ACQACTIVITY

3436 RESUME_ACQACTIVITY





3438 CHECK_ACQPROCESS

343A CHECK_ACQACTIVITY

343C RESET_ACQPROCESS

3602 DEFINE_INPUT_EVENT

3602 DEFINE_COMPOSITE

3604 DELETE_EVENT

3608 ADD_EVENT

360A REMOVE_SUBEVENT

360E TEST_EVENT

3610 RETRIEVE_REATTACH

3612 RETRIEVE_SUBEVENT

3614 DEFINE_TIMER

3616 DELETE_TIMER

3618 CHECK_TIMER

361A FORCE_TIMER

3802 WEB_RECEIVE

3804 WEB_SEND

3806 WEB_READ

3808 WEB_STARTBROWSE

380A WEB_READNEXT

380C WEB_ENDBROWSE

380E WEB_WRITE_HTTPHEADER

3810 WEB_EXTRACT

3814 WEB_RETRIEVE

3816 WEB_PARSE_URL

3818 WEB_OPEN

381A WEB_CLOSE

381C WEB_CONVERSE

3C02 DOCUMENT_CREATE

3C04 DOCUMENT_INSERT

3C06 DOCUMENT_RETRIEVE

3C08 DOCUMENT_SET

3E0E EXTRACT_TCPIP

3E10 EXTRACT_CERTIFICATE

4802 ENTER_TRACENUM

4804 MONITOR

4A02 ASKTIME_ABSTIME





4A04 FORMATTIME

4A06 CONVERTTIME

5602 SPOOLOPEN

5604 SPOOLREAD

5606 SPOOLWRITE

5610 SPOOLCLOSE

5E06 CHANGE_TASK

5E22 WAIT_EXTERNAL

5E32 WAITCICS

6A02 QUERY_SECURITY

6C02 WRITE_OPERATOR

6C12 ISSUE_DFHWTO

7402 SIGN_ON

7404 SIGN_OFF

7406 VERIFY_PASSWORD

7408 CHANGE_PASSWORD

7E02 DUMP_TRANSACTION

7E04 DUMP_SYSTEM

Nastel XRay Probes for z/OS Appendix D: EXEC SQL Groups and Commands


Appendix D: EXEC SQL Groups and Commands

D.1 EXEC SQL Groups

Table D-1. EXEC SQL Groups

Group# Group Name

0001 OPEN

0002 FETCH

0003 CLOSE

0004 PREPARE

0005 EXECUTE

0006 DESCRIBE

0007 EXPLAIN

0008 UPDATE

0009 DELETE

0010 TRUNCATE

0012 SET

0013 GRANT

0014 REVOKE

0015 ROLLBACK

0016 LOCK

0017 CREATE

0018 COMMIT

0019 INTOPEN

0020 DROP

0021 ALTER

0022 COMMENT

0023 CONNECT

0024 LABEL

0028 RELEASE

0029 CALL

0030 ALLOCATE

0031 ASSOCIATE

0032 SIGNAL

0033 HOLD

0034 FREE

0035 DECLARE

0036 SAVEPOINT

0037 REFRESH

Appendix D: EXEC SQL Groups and Commands Nastel XRay Probes for z/OS


Table D-1. EXEC SQL Groups

Group# Group Name

0038 GET

0039 MERGE

0040 EXCHANGE

0041 SELECT

0042 INSERT

0043 REMOTE

0044 RENAME

D.2 EXEC SQL API

Table D-2. EXEC SQL API

Command# Command Name Group Name

0003 OPEN OPEN

0004 FETCH FETCH

0005 CLOSE CLOSE

0006 FETCH RELATIVE FETCH

0007 FETCH ABSOLUTE FETCH

0008 FETCH BEFORE FETCH

0009 FETCH AFTER FETCH

0010 FETCH PRIOR FETCH

0011 FETCH CURRENT FETCH

0012 FETCH FIRST FETCH

0013 FETCH LAST FETCH

0014 PREPARE PREPARE

0015 EXECUTE EXECUTE

0016 EXECUTE IMMEDIATE EXECUTE

0017 DESCRIBE DESCRIBE

0018 EXPLAIN EXPLAIN

0035 FETCH ROWSET NEXT FETCH

0036 FETCH ROWSET RELATIVE FETCH

0037 FETCH ROWSET ABSOLUTE FETCH

0038 FETCH ROWSET PRIOR FETCH

0039 FETCH ROWSET CURRENT FETCH

0040 FETCH ROWSET FIRST FETCH

0041 FETCH ROWSET LAST FETCH

0044 UPDATE ROWSET UPDATE

0045 DELETE ROWSET DELETE





0046 FETCH REL ROWSET MRS FETCH

0047 FETCH ABS ROWSET MRS FETCH

0048 FETCH PRIOR ROWSET MRS FETCH

0049 FETCH CURRENT ROWSET MRS FETCH

0050 FETCH FIRST ROWSET MRS FETCH

0051 FETCH LAST ROWSET MRS FETCH

0052 FETCH NEXT ROWSET MRS FETCH

0229 TRUNCATE TRUNCATE

0231 SELECT SELECT

0232 INSERT INSERT

0233 DELETE DELETE

0234 UPDATE UPDATE

0235 INSERT WITHIN SELECT INSERT

0236 MULTIROW INSERT INSERT

0239 SELECT SELECT

0250 MULTIROW DIST. INSERT INSERT

0259 SET CURRENT SQLID SET

0268 GRANT GRANT

0271 REVOKE REVOKE

0276 REMOTE SQL REMOTE

0277 ROLLBACK ROLLBACK

0278 LOCK LOCK

0308 CREATE VIEW CREATE

0310 COMMIT COMMIT

0313 RENAME TABLE RENAME

0666 INTOPEN INTOPEN

0710 CREATE DATABASE CREATE

0716 CREATE TABLESPACE CREATE

0719 CREATE STOGROUP CREATE

0721 CREATE TABLE CREATE

0726 CREATE INDEX CREATE

0728 CREATE SYNONYM CREATE

0745 SET CURRENT PACKAGESET SET

0746 SET HOST VAR SET

0755 CREATE ALIAS CREATE

0729 DROP VIEW DROP

0730 DROP SYNONYM DROP





0731 DROP INDEX DROP

0732 DROP TABLE DROP

0733 DROP TABLESPACE DROP

0734 DROP DATABASE DROP

0735 DROP STOGROUP DROP

0736 ALTER STOGROUP ALTER

0738 ALTER TABLESPACE ALTER

0739 ALTER INDEX ALTER

0740 ALTER TABLE ALTER

0741 COMMENT ON COMMENT

0742 LABEL ON LABEL

0747 CONNECT TO CONNECT

0748 CONNECT RESET, section 0 CONNECT

0748 ALTER VIEW ALTER

0749 CONNECT CONNECT

0750 IMPLICIT CONNECT CONNECT

0751 CONNECT USER/USING TYPE1 CONNECT

0752 CONNECT TO USER/USING TYPE1 CONNECT

0753 CONNECT USER/USING TYPE2 CONNECT

0754 CONNECT TO USER/USING TYPE2 CONNECT

0759 DROP ALIAS DROP

0761 DROP PACKAGE/PROGRAM DROP

0763 ALTER DATABASE ALTER

0768 SET CURRENT DEGREE SET

0769 TYPE2 CONNECT TO section 0 CONNECT

0769 SET OPTIMIZATION HINT SET

0770 TYPE2 CONNECT RESET CONNECT

0771 TYPE2 CONNECT CONNECT

0772 SET CONNECTION SET

0773 RELEASE LOCATION && HV RELEASE

0774 RELEASE CURRENT RELEASE

0775 RELEASE ALL RELEASE

0776 RELEASE ALL SQL RELEASE

0777 RELEASE ALL PRIVATE RELEASE

0780 FETCH RELATIVE MRS FETCH

0781 SET CURRENT RULES SET

0782 CALL STATEMENT CALL





0783 FETCH ABSOLUTE MRS FETCH

0784 FETCH BEFORE MRS FETCH

0785 FETCH AFTER MRS FETCH

0786 FETCH PRIOR MRS FETCH

0787 FETCH CURRENT MRS FETCH

0788 FETCH FIRST MRS FETCH

0789 FETCH LAST MRS FETCH

0795 ALLOCATE CURSOR ALLOCATE

0797 DESCRIBE PROCEDURE DESCRIBE

0798 ASSOCIATE LOCATORS ASSOCIATE

0799 FETCH ALLOC CURSOR FETCH

0800 CLOSE ALLOC CURSOR CLOSE

0801 DESCRIBE ALLOC CURSOR DESCRIBE

0802 CREATE TRIGGER CREATE

0803 DESCRIBE INPUT DESCRIBE

0807 SIGNAL SQLSTATE SIGNAL

0810 HOLD LOCATOR HOLD

0811 FREE LOCATOR FREE

0812 CREATE AUXILIARY TABLE CREATE

0820 CREATE DISTINCT TYPE CREATE

0821 CREATE FUNCTION CREATE

0824 SET CURRENT PATH SET

0825 ALTER FUNCTION ALTER

0827 DROP DISTINCT TYPE DROP

0828 DROP FUNCTION DROP

0829 DROP PROCEDURE DROP

0830 DROP SPECIFIC FUNCTION DROP

0833 DROP TRIGGER DROP

0835 SET Assignment SET

0845 CREATE PROCEDURE CREATE

0846 ALTER PROCEDURE ALTER

0851 DCL TMP TABLE WIHOUT AS DCL

0853 DCL TMP TABLE WITH AS DCL

0854 SAVEPOINT SAVEPOINT

0855 RELEASE RELEASE

0859 CREATE JAR CREATE

0860 DROP JAR DROP





0861 SET CURR APPL EN SCHEME SET

0867 REFRESH TABLE REFRESH

0869 CREATE SEQUENCE CREATE

0870 ALTER SEQUENCE ALTER

0871 DROP SEQUENCE DROP

0875 GET DIAGNOSTICS GET

0893 MERGE MERGE

0900 CREATE TRUSTED CONTEXT CREATE

0901 ALTER TRUSTED CONTEXT ALTER

0902 DROP TRUSTED CONTEXT DROP

0909 CREATE ROLE CREATE

0910 DROP ROLE DROP

0911 ALTER JAR ALTER

0917 EXCHANGE EXCHANGE

Nastel XRay Probes for z/OS Appendix E: IP CICS Sockets API Commands


Appendix E: IP CICS Sockets API Commands

E.1 IP CICS Sockets API

Table E-1. IP CICS Sockets API

Command# Command Name

0001 ACCEPT

0002 BIND

0003 CLOSE

0004 CONNECT

0005 FCNTL

0007 GETHOSTID

0008 GETHOSTNAME

0009 GETPEERNAME

000A GETSOCKNAME

000B GETSOCKOPT

000C IOCTL

000D LISTEN

000E READ

000F READV

0010 RECV

0011 RECVFROM

0012 RECVMSG

0013 SELECT

0014 SEND

0015 SENDMSG

0016 SENDTO

0017 GETSOCKOPT

0018 SHUTDOWN

0019 SOCKET

001A WRITE

001B WRITEV

001E GETCLIENTID

001F GIVESOCKET

0020 TAKESOCKET

0021 GLOBAL

0022 TASK

0023 SYNC

0024 TERMAPI

Appendix E: IP CICS Sockets API Commands Nastel XRay Probes for z/OS


Table E-1. IP CICS Sockets API


0025 SELECTEX

0026 GETIBMOPT

0027 SETIBMOPT

0028 GETHOSTBYNAME

0029 GETHOSTBYADDR

002A CANCEL

002B FREEADDRINFO

002C GETADDRINFO

002D GETNAMEINFO

002E NTOP

002F PTON

E.2 TCP API Group Commands

Table E-2. TCP API Group Commands


1 ACCEPT

2 BIND

3 CLOSE

4 CONNECT

5 FCNTL

6 GET

7 IOCTL

8 LISTEN

9 READ

10 RECV

11 SELECT

12 SEND

13 SHUTDOWN

14 SOCKET

15 WRITE

16 GIVESOCKET

17 TAKESOCKET

18 GLOBAL

19 TASK

20 SYNC

21 INITIAPI

Nastel XRay Probes for z/OS Appendix E: IP CICS Sockets API Commands


Table E-2. TCP API Group Commands


22 SETIBMOPT

23 CANCEL

24 FREEADDRINFO

25 NTOP

Appendix E: IP CICS Sockets API Commands Nastel XRay Probes for z/OS



Nastel XRay Probes for z/OS Glossary


Glossary

This appendix contains a list of terms relevant to Nastel XRay and other related Nastel products.

ALET: Access-List Entry Token

APF: see Authorized Program Facility

Authorized Program Facility (AFS): A facility that permits the identification of programs that are

authorized to use restricted functions.

AutoPilot M6: Nastel Technologies’ Enterprise Application Management Platform. AutoPilot M6 is

designed to monitor and control distributed IT services such as application servers, middleware, user

applications, workflow engines, brokers, Service Oriented Architecture (SOA) and Enterprise Service Bus

(ESB) based applications and their impact on business services.

AutoPilot M6 Web: AutoPilot M6 Web is a browser-based interface that provides monitoring and

operational control over managed resources and applications. It allows users to monitor health, recover

from a failure, view historical performance graphs and visualize impacts of a failure.

BSV: see Business Views

Business View (BSV): A collection of rules that define a desired state of an eBusiness environment.

Business Views can be tailored to present information in the form most suited to a given user, as defined

by the user.

CEP Servers: Containers that are capable of hosting any number of AutoPilot services; such as experts,

managers, policies etc.

CICS: see Customer Information Control System

CICS System Definition Data set: A virtual storage access method key sequenced dataset cluster that

contains a resource definition record for every record defined to CICS using resource definition online.

Client: Any programming component that uses the AutoPilot infrastructure; for example, the AutoPilot

Console.

Common Object Request Broker Architecture (CORBA): A Common Object Request Broker

Architecture (CORBA) object can be invoked from a Web browser using CGI scripts or applets.

Console: The console acts as the graphical interface for AutoPilot.

Contacts: A subordinate to a given Manager or Expert.

CORBA: see Common Object Request Broker Architecture.

CSD: see CICS System Definition Data set.

Customer Information Control System (CICS): an IBM licensed program that provides on-line

transaction processing services and management for business applications.

Data Source Name: A Data Source Name (DSN) is the logical name that is used by Open Database

Connectivity (ODBC) to refer to the drive and other information that is required to access data. The name

is used by Internet Information Services (IIS) for a connection to an ODBC data source - for example:

Microsoft SQL Server database. The ODBC tool in Control Panel is used to set the DSN. When ODBC

DSN entries are used to store the connection string values externally, you simplify the information that is

needed in the connection string. This makes changes to the data source completely transparent to the code

itself.

Data Space: A range of up to two gigabytes of contiguous virtual storage addresses that a program can

directly manipulate. Unlike an address space, a data space can hold only data; it does not contain common

areas or system data or programs.

Deploy: To put to use, to position for use or action.

Glossary Nastel XRay Probes for z/OS


Domain Server: The domain server is a specialized CEP Server that maintains the directory of CEP

servers, experts etc. The domain server is also capable of hosting experts, managers etc

DSN: see Data Source Name

DSS: see Decision Support System

ESTAEX: see Extended Specify Task Abnormal Exit

EVT: Event Log file extension (for example: sample.evt)

Event: An Event is something that happens to an object. Events are logged by AutoPilot and are available

for use by AutoPilot Policies or the user.

Expert: Services that monitor specific applications such as an applications server, web-server or specific

components within the applications (Example, channels in IBM MQ). Experts generate facts.

Extended Specify Task Abnormal Exit (ESTAEX): A z/OS macro that provides recovery capability

and gives control to the user-specified exit routine for processing, diagnosing an abend, or specifying a

retry address.

Fact: Single pieces of data that has a unique name and value. One or more facts are used to determine the

health of the object, application or server.

Graphical User Interface (GUI): A type of environment that represents programs, files, and options by

means of icons, menus, and dialog boxes on the screen. The user can select and activate these options by

pointing and clicking with a mouse or, often, with the keyboard. Because the graphical user interface

provides standard software routines to handle these elements and report the user's actions (such as a

mouse click on a particular icon or at a particular location in text, or a key press); applications call these

routines with specific parameters rather than attempting to reproduce them from scratch.

GUI: see Graphical User Interface.

HAQS: see High Availability Queuing Service

High Availability Queuing Service (HAQS): HAQS is a component of AutoPilot consisting of two

policies that provide automatic queue fail-over for IBM MQ applications, provide high availability of

IBM MQ resources such as queues and channels, and ensure automatic recovery of IBM MQ channels

IBM MQ: IBM’s message queuing product.

IBM_MQ_Manager: A specialized AutoPilot manager capable of hosting one or more IBM MQ specific

policies, apart from the regular policies.

IIS: See Internet Information Services

Independent Software Vendor (ISV): A business term for companies specializing in making or selling

software, usually for niche markets.

Initial Program Load (IPL): The process of loading system programs and preparing a system to run

applications.

Interactive System Productivity Facility (ISPF): An IBM licensed program that serves as a full-screen

editor and dialog manager. Used for writing application programs. It provides a means of generating

standard screen panels and interactive dialogues between the application programmer and terminal user.

Internet Information Services: Microsoft's brand of Web server software, utilizing HTTP to deliver

World Wide Web documents. It incorporates various functions for security, allows CGI programs, and

also provides for Gopher and FTP services

IPL: see Initial Program Load

ISPF: see Interactive System Productivity Facility

ISV: see Independent Software Vendor

Java: A platform-independent, object-oriented programming language developed and made available by

Sun Microsystems



Java Database Connectivity (JDBC): The JDBC API provides universal data access from the Java

programming language. Using the JDBC 2.0 API, you can access virtually any data source, from

relational databases to spreadsheets and flat files. JDBC technology also provides a common base on

which tools and alternate interfaces can be built. The JDBC Test Tool that was developed by Merant and

Sun Microsystems may be used to test drivers, to demonstrate executing queries and getting results, and

to teach programmers about the JDBC API.

Java Developer’s Kit (JDK): A set of software tools developed by Sun Microsystems, Inc., for writing

Java applets or applications. The kit, which is distributed free, includes a Java compiler, interpreter,

debugger, viewer for applets, and documentation.

Java Management Extensions (JMX): The Java Management Extensions (JMX) technology is an open

technology for management and monitoring that can be deployed wherever management and monitoring

are needed. By design, this standard is suitable for adapting legacy systems, implementing new

management and monitoring solutions and plugging into those of the future.

Java Naming and Directory Interface (JNDI): Unified interface to multiple naming and directory

services for applications based on Java technology.

Java Server Pages (JSP): JSP technology enables rapid development of web-based applications that are

platform independent. Java Server Pages technology separates the user interface from content generation

enabling designers to change the overall page layout without altering the underlying dynamic content.

Java Virtual Machine (JVM): The “virtual” operating system that JAVA-written programs run Java

Servlet technology. The JVM is a hardware- and operating system-independent abstract computing

machine and execution environment. Java programs execute in the JVM where they are protected from

malicious programs and have a small compiled footprint.

JCL: see Job Control Language

JDBC: see Java Database Connectivity.

JDK: see Java Developer's Kit.

JMX: see Java Management Extensions

JNDI: see Java Naming and Directory Interface

Job Control Language (JCL): A control language that is used to identify a job to an operating system

and to describe the job’s requirements.

JRE: JAVA Run-time Environment. The minimum core JAVA required to run JAVA Programs

JSP: see Java Server Pages

JVM: see JAVA Virtual Machine.

Manager: Managers are the home or container for policies. All business views must reside on managers,

and manager must be deployed prior to deploying a business view or policy.

Message-Oriented Middleware (MOM): Message-oriented middleware (MOM) is a client/server

infrastructure that increases the interoperability, portability, and flexibility of an application by allowing

the application to be distributed over multiple heterogeneous platforms.

Message Queue Interface (MQI): Part of IBM’s Networking Blueprint. It is a method of program-to-

program communication suitable for connecting independent and potentially non-concurrent distributed

applications.

MOM: see Message-Oriented Middleware.

MQI: see Message Queue Interface

Multiple Virtual Storage (MVS): The primary operating system used on IBM mainframes. Manages

large amounts of memory and disk space.

MVS: see Multiple Virtual Storage

http://www.sei.cmu.edu/str/indexes/glossary/interoperability.html

http://www.sei.cmu.edu/str/indexes/glossary/portability.html

http://www.sei.cmu.edu/str/indexes/glossary/flexibility.html

Glossary Nastel XRay Probes for z/OS


Naming Service: A common server records “names” of objects and associates them with references,

locations and properties.

Object Request Broker (ORB): In object-oriented programming, software that serves as an intermediary

by transparently enabling objects to exchange requests and responses.

ORB: see Object Request Broker.

Orbix: CORBA product distributed by IONA Technologies.

Package Manager: The command line utility that allows users to list, install, uninstall, verify, and update

AutoPilot installation on any CEP Server.

PKGMAN: see Package Manager Utility included in AutoPilot products.

Policy/Business Views: Business views are a collection of one or more sensors. Business views are used

to visually present the health and status of the different systems as well as automatically issue remedial

actions.

SDSF: Screen Display and Search Facility

Sensor: A rule that is used to determine the health of an object or application based on one or more facts.

Actions can then be issued, based on health.

Service Level Agreement (SLA): A formal written agreement made between two parties: the service

provider and the service recipient. The SLA itself defines the basis of understanding between the two

parties for delivery of the service itself. The document can be quite complex, and sometimes underpins a

formal contract. The contents will vary according to the nature of the service itself, but usually includes a

number of core elements, or clauses.

Simple Mail Transfer Protocol (SMTP): A TCP/IP protocol for sending messages from one computer

to another on a network. This protocol is used on the Internet to route e-mail. See also communications

protocol, TCP/IP. Compare CCITT X series, Post Office Protocol.

SIP: System Initialization Parameters

SLA: see Service Level Agreement

SMTP: see Simple Mail Transfer Protocol

Started Task (STC): A process that begins at system start and runs unattended. Started tasks are

generally used for critical applications. The UNIX equivalent of a started task is a daemon.

STC: see Started Task

Task Control Block (TCB): A z/OS control block used to communicate information about tasks within

an address space that are connected to a z/OS subsystem such as IBM MQ for z/OS or CICS.

TCB: Task Control Block

TCP/IP: see Transmission Control Protocol/Internet Protocol.

Time Sharing Option (TSO): An option of the z/OS operating system that provides interactive time

sharing from remote terminals.

Transmission Control Protocol/Internet Protocol (TCP/IP): A protocol developed by the Department

of Defense for communications between computers. It is built into the UNIX system and has become the

de facto standard for data transmission over networks, including the Internet.

TSO: see Time Sharing Option

Virtual Machine: Software that mimics the performance of a hardware device, such as a program that

allows applications written for an Intel processor to be run on a Motorola chip. Also See Java Virtual

Machine.

Wireless Application Protocol (WAP): An open global specification that is used by most mobile

telephone manufacturers. WAP determines how wireless devices utilize Internet content and other

services. WAP enables devices to link diverse systems contents and controls.

http://en.wikipedia.org/wiki/SLA

http://en.wikipedia.org/wiki/Contract



WLM: see Workload Manager

Workload Manager: A component of z/OS that provides the ability to run multiple workloads at the

same time within one z/OS image or across multiple images.

Write to Operator (WTO): An optional user-coded service that allows a message to be written to the

system console operator informing the operator of errors and unusual system conditions that may need to

be corrected.

WTO: see Write to Operator.

Nastel XRay Probes for zOS · 2021. 1. 22. · nastel xray probes for z/os installation and...

Documents

Transcript of Nastel XRay Probes for zOS · 2021. 1. 22. · nastel xray probes for z/os installation and...