Problem Reporting

Information specific to SPAZIO MFT/S for z/OS product

To resolve your case, we need some further information. The more information you can provide now, the more rapidly we should be able to respond to your problem.

Configuration files and traces should be sent as an email attachment in a zip file unless this is very large, in which case please inform us and we will provide you with a userid and password which will allow you to put the files onto our FTP server.

Installation type

Please specify whether the installation was:

• an existing TEST environment
• an existing PRODUCTION environment
• a NEW TEST installation
• a NEW PRODUCTION installation

Problem Description

Provide a detailed description (depending on the information you have regarding the problem) by specifying:

• The operation that produces the error (configuration, start-up, transmission, compression, encryption, etc.)
• Error description and reason codes
• Any changes to the system since the last successful run (hardware and software)
• When the problem occurred (date and time)
• Specify if it was the first time, repetition of the occurrence, under which conditions
• Interaction of the product with other applications/products
• Any indication useful for reproducing the error in the lab

Basic Documentation

Provide the files and the result of the following:

• the output of the MXSLD4LD jcl (contained in the INSTALL library)
• Whole file //CONTROL or //THEMCNTL of SPAZIO Monitor
• the sysout of the JOB or STC of the Monitor, including: jes2-job-log, jes2-job-message, SYSUDUMP, TRACE or THEMSNAP (with the TRACE output), etc.
• the sysout of the JOB or STC of the previous Monitor in case of restart in Emergency/Recovery
• the JCL, the script and the sysout of the ROUTER or the ACQUIRER, if it is part of the problem
• from SP10 opt. 8 Log Inquiry, the output of the ROUTER or ACQUIRER session if it is part of the problem with all the details
• from SP10 opt. 3 File Utilities, the summary and any detail of the involved files
• the output of the command DIS ST C ALL (from SPAZIO MASTER terminal)
• the output of the command D A ALL (from SPAZIO MASTER terminal). It must be repeated three times with one minute interval

Dumps

• The DUMPs must be formatted on the system where the problem occurred, but must not be processed by the Abend-Aid product
• The system must have the option PDATA=ALLPDATA for the SYSUDUMPs active

Additional documentation for problems related to...

Connectivity

In general from SPAZIO MASTER terminal: DIS SESS and DIS NODE

• for TCP/IP:
  NETSTAT CONN (MVS)
  TRACE ON ITC* (if IBM)
  TRACE ON KTC* (if Interlink)
• for SNA:
  VTAM LOG and definitions concerning the local and remote Monitor (MVS)
  TRACE ON MXSN*

Transports

Provide the details and the result of the following:

• from SPAZIO MASTER terminal: DIS SESS
• from SP10 opt. 3.3 File Utilities, all the details of the entry that is part of the problem
• from SP10 opt. 7 Transmission Monitoring, summary and detail of the transports that are failing
• from SP10 opt.8 Log Inquiry: the output of the session of the failing ROUTER, ACQUIRER or TRANSPORT with all the details
• TRACE ON TMRBCN* (warning: it can be bulky)
• TRACE ON SPROUTER (for non-Thema transports)

VSAM File

Provide the details and the result of the following:

• for THEMTSTO/VSTO - from SPAZIO MASTER terminal: DIS ST TS
• for OBJ/QUESET - from SPAZIO MASTER terminal: DIS QS
• other files - from SPAZIO MASTER terminal: DIS FILE

RACF

Provide the details and the result of the following:

• TRACE ON RAC*
• Relevant RACF messages

Monitor

In case of Monitor locked, anomalous increase of virtual memory, loop, help desk request, provide the details and the result of the following:

• from SPAZIO MASTER terminal: DIS ST VS
• SVC DUMP with SDUMP=(LSQA,TRT,XESDATA,RGN,SUM,PSA,SWA,GRSQ)