Information specific to Data Secure products
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 DSMQ 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
Operating System type and version
In order to provide the Operating System information, specify the result of the following commands:
- on UNIX: uname -a
- on Windows (from command prompt): ver
- on z/OS (from TSO): D IPLINFO
- on OS/400 (from tn3250, locate the "Operating System/400" row): wrklicinf
IBM WebSphere MQ version information
In order to provide WebSphere MQ version information, specify the result of the following commands:
- on UNIX and Windows:
dspmqver (for WMQ 6.x queue managers)
mqver (for WMQ 5.x queue managers)
- on z/OS: check WMQ JOBLOG contents
- on OS/400 (from tn3250, locate the "Operating System/400" row):
CALL QMQM/DSPMQVER (for WMQ 6.x queue managers)
CALL QMQM/MQVER (for WMQ 5.x queue managers)
DSMQ/DSTK version information
In order verify the DSMQ/DSTK release, specify the result of the following commands (where DSMQROOT is the product installation directory):
- on UNIX:
DSMQROOT/bin/dsver (when available)
cat DSMQROOT/bin/dsmqver.dat (when available)
what DSMQROOT/bin/*
ls -l DSMQROOT/bin/*
what DSMQROOT/lib/*
ls -l DSMQROOT/lib/*
- on Windows:
DSMQROOT\bin\dsver (when available)
type DSMQROOT\bin\dsmqver.dat (when available)
dir DSMQROOT\bin\*
dir DSMQROOT\lib\*
dir %windir%\system32\cryptoki*
dir %windir%\system32\smime*
- on z/OS: provide the DSTK Monitor JOBLOG
- on OS/400:
- from QShell: dsver
- from 5250 (locate the 8PDSTK1 package from the command output): DSPSFWRSC
IBM WMQ configuration information
Please provide the definition of each channel that fails; this can be extracted with the following MQSC command (substitute MYCHANNEL with actual channel name):
DISPLAY CHANNEL(MYCHANNEL) ALL
DSMQ/DSTK configuration information
Please provide the following information:
DSMQ/DSTK ver. 1.7/1.9/1.10 (Windows)
- Export the following Windows Registry subtrees:
[HKEY_LOCAL_MACHINE\SOFTWARE\Primeur]
[HKEY_CURRENT_USER\SOFTWARE\Primeur]
- Open a command prompt (cmd.exe) and get the output of the command: set
DSMQ/DSTK ver. 1.7/1.9/1.10 (UNIX and Windows)
Provide all the configuration files located in the directory DSMQVARROOT/cfg (DSMQVARROOT is the product data installation directory).
DSMQ/DSTK ver. 1.7/1.9/1.10 (OS/400)
From the QShell of the user running DSTK, get the /IDS/dstk/cfg/dstk.ini configuration file. Configuration files must be sent in BINARY form and specifying which File-Type and Code-Page number is associated with that file in OS/400.
DSMQ/DSTK ver. 2.0 (z/OS)
- Get the complete JES JOBLOG (containing the MSGLOG output file) produced by DSTK monitor A.S.
- If the DSMQ/DSTK monitor abended, the associated SVC-DUMP and/or SYSUDUMP must be provided. If it is too big to fit in an e-mail message, contact the HelpDesk call center to obtain an FTP account to upload the dump file.
- The DD DSTKINI and DSTKCFG members of the DSTK.CNTL library must be provided.
IBM WMQ diagnostic information
- on z/OS: provide WMQ JOBLOG
- on Windows, UNIX, i5/OS, HP-NSK and OpenVMS:
Please provide the following files (where MQVARROOT is the WMQ data installation directory and MQVARROOT is the name of the failing queue manager):
MQVARROOT/errors/AMQERR*.LOG
MQVARROOT/errors/*.FDC
MQVARROOT/qmgrs/MQVARROOT/errors/AMQERR*.LOG
DSMQ/DSTK LOGs and Traces
These are the instructions for enabling traces on DSMQ/DSTK. The bold file names (which may be different from the ones shown on your installation) must be compressed in ZIP format and sent to the PRIMEUR HelpDesk. DSMQVARROOT is the product data installation directory.
DSTK ver. 1.7/1.9/1.10 (UNIX)
- Enable DSTK traces by entering the following text in the DSMQVARROOT/cfg/dstk.ini file:
[Trace]
TraceLevel=5
TraceFile=DSMQVARROOT/trc/dstk.trc
- Enable DSMQ channel exits traces by entering the following text in the DSMQVARROOT/cfg/mqppsx.ini file:
[Default]
LogFile /log/$.log
TrcLevel=2
TrcFile=DSMQVARROOT/trc/$.trc
- Enable DSMQ channel autodefinition exit traces by entering the following text in the DSMQVARROOT/cfg/dsmqchd.ini file (this step is required only when using WMQ Cluster Channel):
[Global] (or [Default] depending on your version)
TraceFile=DSMQVARROOT/trc/dsmqchd.trc
TraceLevel=1
All the contents of the following directories must be provided: DSMQVARROOT/log, DSMQVARROOT/trc/$.trc.
DSTK ver. 1.7/1.9/1.10 (OS/400)
- Enable DSTK traces by entering the following text in the DSMQVARROOT/cfg/dstk.ini file:
[Trace]
TraceLevel=5
TraceFile=DSMQVARROOT/trc/dstk.trc
- Enable DSMQ channel exits traces by entering the following text in the DSMQVARROOT/cfg/mqppsx.ini file:
[Default]
LogFile /log/$.log
TrcLevel=2
TrcFile=DSMQVARROOT/trc/$.trc
- Enable DSMQ channel autodefinition exit traces by entering the following text in the DSMQVARROOT/cfg/dsmqchd.ini file (this step is required only when using WMQ Cluster Channel):
[Global] (or [Default] depending on your version)
TraceFile=DSMQVARROOT/trc/dsmqchd.trc
TraceLevel=1
All the contents of the following directories must be provided: DSMQVARROOT/log, DSMQVARROOT/trc/$.trc.
DSTK ver. 1.7/1.9/1.10 (Windows)
- Create a directory accessible in CREATE/READ/WRITE mode for the all the WMQ users (f.i. C:\Documents and Settings\All Users\Application Data\Primeur\DSMQ\log).
- Enable DSTK traces by adding the following entries in the Windows registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Primeur\DSTK\Trace]
"TraceLevel"="5"
"TraceFile"="DSMQVARROOT\trc\dstk.trc"
- Enable DSMQ channel exit traces by entering the following text in the Windows registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Primeur\dsmqpps\mqppsx\ default]
"TrcLevel"="2"
"TraceFile"="DSMQVARROOT\trc\$.trc"
- Enable DSMQ channel autodefinition exit traces by entering the following text in the Windows registry (this step is required only when using WMQ Cluster Channel):
[HKEY_LOCAL_MACHINE\SOFTWARE\Primeur\dsmqchd\default] or (depending on your version)
[HKEY_LOCAL_MACHINE\SOFTWARE\Primeur\dsmqchd\global]
"TraceLevel"="1"
"TraceFile"="DSMQVARROOT\trc\dsmqchd.trc"
All the contents of the following directories must be provided: DSMQVARROOT/log, DSMQVARROOT/trc/$.trc. Repeat the last operation to reproduce the error and compress the generated trace file.
DSTK ver. 2.0 (z/OS)
- Enable DSTK traces by going to the DSTK.CNTL library and editing the DD DSTKCFG member:
[Global]
TraceLevel=4
...
...
[ICSF]
Trace=1
...
- Enable DSMQ channel exit traces by going to the DSTK.CNTL library and editing the DD CHCFIG
[Default]
TrcLevel=2
- Enable DSMQ channel exit traces by going to the DSTK.CNTL library and editing the DD DSMQCHD member (this step is required only when using WMQ Cluster Channel):
[Global] (or [Default] depending on your version)
TraceLevel=1
Traces are displayed in the DSTK Monitor JOBLOG
|
