Middleware News

2110 0x0000083e MQRC_FORMAT_ERROR Problem(Abstract) You attempt to get a message from your queue. The getting application fails with a data conversion format error. Symptom 2110 0x0000083e MQRC_FORMAT_ERROR Cause The most common reason for 2110 is an incorrect message format in the message descriptor. Resolving the problem Specify the correct MQMD Format for your message. The format 'MQSTR ' is what most applications use to convert string data (non numeric data). 2092 MQRC XMIT Q USAGE ERROR Problem(Abstract) You put a message to your queue remote and you expect that it will go to the transmission queue and flow across your sender channel. The putting application fails with the following symptom. Symptom 2092 0x0000082c MQRC_XMIT_Q_USAGE_ERROR Cause 2092 is returned because the transmission queue definition did not specify the xmitq parameter. Resolving the problem Alter the transmission queue and specify usage(xmitq) parameter. Example: al

Channel SSL Error

WebSphere MQ client connection failures due to resource shortages Technote (troubleshooting) - Middleware News Problem(Abstract) Your WebSphere MQ client suddenly fails when attempting to connect to your MQ server. Symptom You receive many FDCs for the AMQRMPPA and RUNMQLSR processes. The FDCs indicate a shortage of system resources. xecP_E_NO_RESOURCE rrcE_CREATE_THREAD_ERROR xecL_E_TOO_MANY_HANDLES rc 1450 (NO_SYSTEM_RESOURCES) from WriteFile rc 12 (ENOMEM = insufficient system resources) Cause Recent changes to your Security Exit program caused the resource problem. Diagnosing the problem The following errors were reported in FDC files on the server: Probe Id :- XC035007 Component :- xcsCreateThread Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqzlaa0.exe Major Errorcode :- xecP_E_NO_RESOURCE Comment1 :- Not enough space Probe Id :- ZT049001 Component :- zutPreReadMachineIniFile Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqmsrvn.ex

WebSphere MQ File Transfer Edition Two Minute Introduction - Middleware News

ITIL Essentials Study Guide Introduction Service Support Functions: • Service Desk • Incident Management • Problem Management • Change Management • Configuration Management • Release Management Service Delivery Functions: • Availability Management • IT Services Continuity Management • Capacity Management • Financial Management • Service Level Management Configuration Management Objectives: • Providing information on the IT infrastructure o To all other processes o IT Management • Enabling control of the infrastructure by monitoring and maintaining information on: o All the resources needed to deliver services o Configuration Item (CI) status and history o Configuration Item relationships Tasks: • Identification and naming • Management information • Verification • Control • Status Accounting Asset: Component of a business process like people, accommodation, computer systems, paper records, fax machines, etc. Configuration Management Database: A

PCF commands The purpose of WebSphere MQ programmable command format (PCF) commands is to allow administration tasks to be programmed into an administration program. In this way you can create queues, process definitions, channels, and namelists, and change queue managers, from a program. PCF commands cover the same range of functions provided by MQSC commands. You can write a program to issue PCF commands to any queue manager in the network from a single node. In this way, you can both centralize and automate administration tasks. Each PCF command is a data structure that is embedded in the application data part of a WebSphere MQ message. Each command is sent to the target queue manager using the MQI function MQPUT in the same way as any other message. The command server on the queue manager receiving the message interprets it as a command message and runs the command. To get the replies, the application issues an MQGET call and the reply data is returned in another data struc

z/OS Basic Skills: The mainframe’s physical environment - The mainframe’s internal structure - The mainframe’s processors - Middleware News

TCP/IP Commands Quick Reference - Middleware News TCP/IP Commands for TSO/E Note: The following TCP/IP commands should be done from the TSO command panel or the READY prompt. Note: hostname may be the IP address of the host, or the host name of the host. • FTP hostname {port} - Connect to remote host to get/put files. Defaults to port 21. • HOMETEST - Validate TCP/IP configuration. • NETSTAT option {TCP procname} - Display network status of local host. Use ? for list of options. • NETSTAT ALLCON|CONN - Display port connections for the TCP/IP stack. • NETSTAT ARP ALL|ipaddress - Display ARP cache for the TCP/IP stack. • NETSTAT DEV - Display the status of the device(s) and link(s) for the TCP/IP stack. • NETSTAT GATE|ROUTE - Display routing information for the TCP/IP stack. (Different views) • NETSTAT HOME - Display IP address(es) for the stack. • PING hostname - Sends an echo request to a host name or address to determine if the computer is accessible. Use ? for list

Application Server Innovations WebSphere Virtual Enterprise Extending SOA into the Public Cloud: Smart SOA Application Infrastructure Part 1 Extending SOA into the Private Cloud WebSphere CloudBurst Appliance and WebSphere Application Server Hypervisor Edition WebSphere Applicaton Server for z/OS Goes to SHARE

PCF reason codes Reason codes might be returned by a broker in response to a command message in PCF format, depending on the parameters used in that message. * 3001 (0BB9) (RC3001): MQRCCF_CFH_TYPE_ERROR * 3002 (0BBA) (RC3002): MQRCCF_CFH_LENGTH_ERROR * 3003 (0BBB) (RC3003): MQRCCF_CFH_VERSION_ERROR * 3004 (0BBC) (RC3004): MQRCCF_CFH_MSG_SEQ_NUMBER_ERR * 3005 (0BBD) (RC3005): MQRCCF_CFH_CONTROL_ERROR * 3006 (0BBE) (RC3006): MQRCCF_CFH_PARM_COUNT_ERROR * 3007 (0BBF) (RC3007): MQRCCF_CFH_COMMAND_ERROR * 3008 (0BC0) (RC3008): MQRCCF_COMMAND_FAILED * 3009 (0BC1) (RC3009): MQRCCF_CFIN_LENGTH_ERROR * 3010 (0BC2) (RC3010): MQRCCF_CFST_LENGTH_ERROR * 3011 (0BC3) (RC3011): MQRCCF_CFST_STRING_LENGTH_ERR * 3012 (0BC4) (RC3012): MQRCCF_FORCE_VALUE_ERROR * 3013 (0BC5) (RC3013): MQRCCF_STRUCTURE_TYPE_ERROR * 3014 (0BC6) (RC3014): MQRCCF_CFIN_PARM_ID_ERROR * 3015 (0BC7) (RC3015): MQRCCF_CFST_PARM_ID_ERROR * 3016 (0BC8) (RC3016): MQRCCF_MSG_LENGTH_ERROR * 3017 (0BC9) (RC3017): MQ

General documentation needed for all problems with WebSphere MQ for z/OS - Middleware News Here is a list of the general documentation you might be asked to submit for a PMR: * Any hardcopy or softcopy illustrating the symptoms of the problem. * The dump of the problem, see Getting a dump. * The appropriate SYS1.LOGREC records, see SYS1.LOGREC information. * The system log. * A portion of the WebSphere® MQ for z/OS® job log. * Trace records, see Using trace for problem determination. * Trace information produced by the CICS® or IMS™ adapter, see The CICS adapter trace. * Buffer pool statistics, see the sections on using SMF and type 115 records in the WebSphere MQ for z/OS System Setup Guide. * Listings of relevant application programs. * A list of PTFs and APARs applied. Use the sample JCL below to produce a list of all the PTFs, APARs, user modifications and product code that has been installed in the global zone specified by SMPCSI: //SMPELIST EXEC PGM=GIMSMP,REGI

Channel Problem determination - When a channel refuses to run - Middleware news When a channel refuses to run If a channel refuses to run: * Check that DQM and the channels have been set up correctly. This is a likely problem source if the channel has never run. Reasons could be: o A mismatch of names between sending and receiving channels (remember that uppercase and lowercase letters are significant) o Incorrect channel types specified o The sequence number queue (if applicable) is not available, or is damaged o The dead-letter queue is not available o The sequence number wrap value is different on the two channel definitions o A queue manager, CICS system, or communication link is not available o Following a restart, the wrong queue manager may have been attached to CICS o A receiver channel might be in STOPPED state o The connection might not be defined correctly o There might be a problem with the communications software (for example, is TCP running?) o In z

IBM WebSphere Message Broker V6 on z/OS / Z OS Terms and Concepts - Middleware News The Value of WebSphere Message Broker V6 on z zOS Specifics wmbintroshort MBBestPractices zOS Terms and Concepts